July 2022 - devel - Fedora Mailing-Lists

Non-responsive Package Maintainer for Cockpit Composer

by Jacob Kozol

Hello all! Does anyone know how to contact Anthony McInerney (bofh80 <https://accounts.fedoraproject.org/user/bofh80/>)? I have tried to reach out via email but have not received a response. https://bugzilla.redhat.com/show_bug.cgi?id=2111630 Thank you, Jacob Kozol https://accounts.fedoraproject.org/user/jkozol/

1 year, 9 months

1
0
0 / 0

Heads-up: ldc soname bump

by Kalev Lember

Hi all, I'm working on updating ldc D compiler to version 1.30. The bumps libphobos and libdruntime sonames, but I've already sorted out all the build issues and I'm going to take care of rebuilding everything that depends on it before merging it into rawhide. -- Kalev

1 year, 9 months

1
0
0 / 0

List of long term FTBFS packages to be retired in August

by Miro Hrončok

Dear maintainers. Based on the current fail to build from source policy, the following packages will be retired from Fedora 37 approximately one week before branching (August 2022). Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... The packages in rawhide were not successfully built at least since Fedora 35. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ft... If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Package (co)maintainers ========================================================================= golang-grpc-go4 eclipseo, go-sig, jchaloup lancer willb php-aws-sdk3 lcts php-pimple lcts recorder ddd rubygem-coffee-rails jaruga, ruby-packagers-sig, vondruch rubygem-minitest-reporters pvalena rubygem-sprockets-rails jaruga, pvalena, ruby-packagers-sig tinygo go-sig, qulogic uom-parent lberk, mgoodwin, nathans xs petersen The following packages require above mentioned packages: Depending on: golang-grpc-go4 (1) golang-x-build (maintained by: eclipseo, go-sig, jchaloup) golang-x-build-0-0.19.20201229git0a4bf69.fc35.src requires golang(grpc.go4.org) = 0-0.9.20180421git11d0a25.fc34, golang(grpc.go4.org/codes) = 0-0.9.20180421git11d0a25.fc34 golang-x-build-devel-0-0.19.20201229git0a4bf69.fc35.noarch requires golang(grpc.go4.org) = 0-0.9.20180421git11d0a25.fc34, golang(grpc.go4.org/codes) = 0-0.9.20180421git11d0a25.fc34 Depending on: rubygem-sprockets-rails (22) rubygem-actionmailbox (maintained by: pvalena) rubygem-actionmailbox-7.0.2.3-2.fc37.src requires rubygem(sprockets-rails) = 3.2.2 rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch) rubygem-activestorage-7.0.2.3-1.fc37.src requires rubygem(sprockets-rails) = 3.2.2 rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch) rubygem-railties-7.0.2.3-2.fc37.src requires rubygem(sprockets-rails) = 3.2.2 rubygem-sassc-rails (maintained by: pvalena) rubygem-sassc-rails-2.1.2-4.fc36.noarch requires rubygem(sprockets-rails) = 3.2.2 rubygem-sassc-rails-2.1.2-4.fc36.src requires rubygem(sprockets-rails) = 3.2.2 rubygem-rails (maintained by: jstribny, kanarip, mmorsi, mtasaka, pvalena, ruby-packagers-sig, sseago, tdawson, vondruch) rubygem-rails-1:7.0.2.3-2.fc37.noarch requires rubygem(actionmailbox) = 7.0.2.3 rubygem-rspec-rails (maintained by: clalance, vondruch) rubygem-rspec-rails-5.1.1-2.fc37.src requires rubygem(actionmailbox) = 7.0.2.3 rubygem-actiontext (maintained by: pvalena) rubygem-actiontext-7.0.2.3-2.fc37.noarch requires rubygem(activestorage) = 7.0.2.3 rubygem-actiontext-7.0.2.3-2.fc37.src requires rubygem(activestorage) = 7.0.2.3 rubygem-actionpack (maintained by: jaruga, jstribny, kanarip, mmorsi, pvalena, ruby-packagers-sig, sseago, vondruch) rubygem-actionpack-1:7.0.2.3-1.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-actionview (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-actionview-7.0.2.3-1.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-activemodel (maintained by: jstribny, mmorsi, pvalena, tdawson, vondruch) rubygem-activemodel-7.0.2.3-2.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-ammeter (maintained by: jstribny, ruby-packagers-sig, vondruch) rubygem-ammeter-1.1.5-3.fc37.noarch requires rubygem(railties) = 7.0.2.3 rubygem-ammeter-1.1.5-3.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-font-awesome-rails (maintained by: abradshaw, ckyriakidou, evgeni, fale, snecker) rubygem-font-awesome-rails-4.7.0.8-2.fc37.noarch requires rubygem(railties) = 7.0.2.3 rubygem-font-awesome-rails-4.7.0.8-2.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-generator_spec (maintained by: ilgrad) rubygem-generator_spec-0.9.4-12.fc37.noarch requires rubygem(railties) = 7.0.2.3 rubygem-generator_spec-0.9.4-12.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-globalid (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-globalid-1.0.0-3.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-haml (maintained by: kanarip, pvalena) rubygem-haml-5.2.2-3.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-importmap-rails (maintained by: pvalena) rubygem-importmap-rails-1.0.3-2.fc37.noarch requires rubygem(railties) = 7.0.2.3 rubygem-jbuilder (maintained by: pvalena, vondruch) rubygem-jbuilder-2.11.5-2.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-jquery-rails (maintained by: jstribny, tdawson, vondruch) rubygem-jquery-rails-4.4.0-3.fc37.noarch requires rubygem(railties) = 7.0.2.3 rubygem-rails-controller-testing (maintained by: valtri) rubygem-rails-controller-testing-1.0.5-6.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-sass-twitter-bootstrap (maintained by: tdawson) rubygem-sass-twitter-bootstrap-2.3.0-16.fc37.noarch requires rubygem(railties) = 7.0.2.3 rubygem-slim (maintained by: vondruch) rubygem-slim-4.1.0-6.fc37.src requires rubygem(railties) = 7.0.2.3 rubygem-web-console (maintained by: jaruga, ruby-packagers-sig, vondruch) rubygem-web-console-4.1.0-4.fc36.noarch requires rubygem(railties) = 7.0.2.3 rubygem-web-console-4.1.0-4.fc36.src requires rubygem(railties) = 7.0.2.3 Too many dependencies for rubygem-sprockets-rails, not all listed here Affected (co)maintainers (directly and indirectly): abradshaw: rubygem-sprockets-rails ckyriakidou: rubygem-sprockets-rails clalance: rubygem-sprockets-rails ddd: recorder eclipseo: golang-grpc-go4 evgeni: rubygem-sprockets-rails fale: rubygem-sprockets-rails go-sig: golang-grpc-go4, tinygo ilgrad: rubygem-sprockets-rails jaruga: rubygem-sprockets-rails, rubygem-coffee-rails jchaloup: golang-grpc-go4 jstribny: rubygem-sprockets-rails kanarip: rubygem-sprockets-rails lberk: uom-parent lcts: php-aws-sdk3, php-pimple mgoodwin: uom-parent mmorsi: rubygem-sprockets-rails mtasaka: rubygem-sprockets-rails nathans: uom-parent petersen: xs pvalena: rubygem-sprockets-rails, rubygem-minitest-reporters qulogic: tinygo ruby-packagers-sig: rubygem-sprockets-rails, rubygem-coffee-rails snecker: rubygem-sprockets-rails sseago: rubygem-sprockets-rails tdawson: rubygem-sprockets-rails valtri: rubygem-sprockets-rails vondruch: rubygem-sprockets-rails, rubygem-coffee-rails willb: lancer -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 year, 9 months

4
6
0 / 0

Upstream Release Monitoring - bug report

by Michal Schorm

Hello, I don't know where to go, so I'm trying here. Package 'mariadb-connector-c' [1] I maintain has upstream release monitoring enabled [2]. The bot opened a BZ [3] for me to notify about a new upstream release - as expected. It tried to come up with a patch and try to scratch-build the package with the patch. However it failed. And now it tries again and again, failing every time. Littering the BZ ticket with more and more comments with zero value. Spamming people in CC every day or two. I want it to stop. Ideally, I would like the bot to stop trying making patches and doing scratch builds on all my packages at all. It's a wasted effort (and computing time; and KOJI resources). Is that possible? How? -- I logged into the https://release-monitoring.org/ , but there doesn't seem to be any setting regarding that. -- In the meanwhile, I've found one more tiny bug: (A) The link to Fedora wiki page about the upstream release monitoring leads to an obsoleted page: https://fedoraproject.org/wiki/Upstream_release_monitoring -- [1] https://src.fedoraproject.org/rpms/mariadb-connector-c [2] https://release-monitoring.org/project/16939/ [3] https://bugzilla.redhat.com/show_bug.cgi?id=2090416 -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat --

1 year, 9 months

6
6
0 / 0

Re: Why is there antlr4-project package?

by Marián Konček

I used a wrong mailing list, I meant to send it here. I still see this approach as wrong. You can change the archfulness of the main package. You can add a -java subpackage which is noarch and provides the main package name for example. In the .spec I see you manually invoke expanded %mvn_install macro. "antlr4-project" is what "antlr4" should be in my opinion. On 25. 7. 2022 16:28, Jerry James wrote: > On Mon, Jul 25, 2022 at 1:07 AM Marián Konček <mkoncek(a)redhat.com> wrote: >> I noticed that the package "antlr4" was retired and another package >> "anrlt4-project" was created some time after that. >> Why was a new package added instead of antlr4 being unretired? > The problem is that the antlr4 package is noarch, and it is not > possible to have an archful subpackage of a noarch main package. The > noarch antlr4 package was retired so that the archful antlr4-project > repo could be created with the various language runtimes. > >> Can we unretire antlr4? > No. Why do you want to? There is an antlr4 package, one of the > subpackages of antlr4-project. -- Marián Konček

1 year, 9 months

3
3
0 / 0

Heads up for Rawhide users of Evolution with Google accounts

by Adam Williamson

Hey folks! If you're running Rawhide and using Evolution - or anything else backed by evolution-data-server - with a Google account, you may have noticed that it doesn't work with evolution-data-server-3.45.1. The GOA and Google support in Evolution was turned off with the 3.45.1 build, I think because of the ongoing libsoup 2->3 migration (no app can use both libsoup2 and libsoup3 at the same time, and this is causing all sorts of inconveniences as we work through moving everything to libsoup3). I've set up a COPR: https://copr.fedorainfracloud.org/coprs/adamwill/evo-gdata-libsoup3/ which has libgdata and gvfs rebuilt against libsoup3, and e-d-s rebuilt against the new libgdata with Google and GOA support turned back on. I don't know how much of that was actually necessary, but it is sufficient - with those builds, Google account support in e-d-s does seem to work again. The builds aren't really suitable to go in Rawhide (a couple of them are git snapshots, and a couple use WIP patches from upstream) but if you really need this to work right away, give it a shot. I've tried to version the builds such that the next official builds will supersede them. I expect mcrha and the rest of the desktop team will be able to fix this up more permanently in Rawhide soonish. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 year, 9 months

1
0
0 / 0

Heads-up: ODE soname bump

by Hedayat Vatankhah

Hi all, As part of building ODE 0.16, ode's soname has been bumped from libode.so.4/libode-double.so.4 to libode.so.8/libode-double.so.8. This package is now built as part of Fedora 37 Mass Rebuild, so we expect all dependent packages to be automatically built again during this process. We do not expect to see compilation failures because of this update. Regards, Hedayat

1 year, 9 months

4
5
0 / 0

Some spins/labs to be dropped from F37

by Ben Cotton

In accordance with FESCo's approved[1] keepalive policy, the following Spins/Labs will be dropped from F37 unless new maintainers step up. ## Maintainer indicated they do not have time to maintain for this release * Robotics Spin — https://fedoraproject.org/wiki/Robotics_Spin ## Maintainer did not respond to pings * Games Spin — https://fedoraproject.org/wiki/Games_Spin * Security Spin — https://fedoraproject.org/wiki/Security_Spin If you'd like to become a maintainer of one of these, please comment on the corresponding ticket in the schedule repo[2]. If you want to know what goes into maintaining a Spin/Lab, see the Releases docs[3]. [1] https://pagure.io/fesco/issue/1972 [2] https://pagure.io/fedora-pgm/schedule/issues?tags=spins+keepalive [3] https://docs.fedoraproject.org/en-US/releases/spins/maintaining/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 year, 9 months

4
3
0 / 0

Fedora 37 mass rebuild started

by Kevin Fenzi

Hi all, Per the Fedora f37 schedule[1] we have started a mass rebuild on 2022-07-20 for Fedora f37. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open&tags=mass+rebuild This mass rebuild will be done in a side tag (f37-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html <https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html> Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html <https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html> FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list[2] or filing an issue in pagure[3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 year, 9 months

12
25
1 / 0

[Test-Announce] 2022-07-25 @ 15:00 UTC - Fedora QA Meeting

by Adam Williamson

# Fedora Quality Assurance Meeting # Date: 2022-07-25 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.libera.chat Greetings testers! We didn't meet for a couple of weeks, so let's get together and check in. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 37 check-in 3. Test Day / community event status 4. Open floor -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorap... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 year, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel July 2022