Re: F39 Change Proposal: Flatpaks without Modules (System-Wide Change)
On Wed, 2023-05-10 at 09:30 -0400, Owen Taylor wrote: > Does that sound workable? Are there better ways we could do it? Hi, if I recall correctly, using the custom D-Bus prefix is there to match application's D-Bus prefix defined for the flatpak, thus: a) the services run independently from the system, inside the sandbox; b) they can be started without any additional effort on the Flatpak configuration side (because the services share the app's D-Bus prefix). I briefly grepped the evolution-data-server sources and it seems that most of the places in the .c files can be changed in runtime, but there are places where the things can break, like the `evolution-data- server.pc` file or the D-Bus .service files, which both reference the D-Bus name from the compile time and those .service files are also named by the service (otherwise there's a runtime warning in the journal about the file not matching the service name). Those might not be show stoppers, I guess. By the way, when people install Evolution flatpak, they have preinstalled evolution-ews inside it. How will they install it after this change? Bye, Milan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 38 EPEL 9 - python3-pydot-1.4.2-6.el9.noarch python3-soupsieve-2.4.1-1.el9.noarch missing depedecies ...
On 5/14/23 07:33, André verwijs via devel wrote: Fedora 38 EPEL 9 python3-pydot-1.4.2-6.el9.noarch python3-soupsieve-2.4.1-1.el9.noarch missing depedecies ... Issue 1: Unable to install the best update candidate for package python3-pydot-1.4.2-5.fc38.noarch - nothing offers python(abi) = 3.9 which is needed for python3-pydot-1.4.2-6.el9.noarch - nothing offers python3.9dist(pyparsing) >= 2.1.4 which is needed for python3-pydot-1.4.2-6.el9.noarch Issue 2: Unable to install the best update candidate for package python3-soupsieve-2.3.2.post1-8.fc38.noarch - nothing offers python(abi) = 3.9 which is needed for python3-soupsieve-2.4.1-1.el9.noarch Why are you mixing Fedora and EPEL? That's not likely to go well. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Review request for oclock package (orphaned since F35)
Kevin, oclock was not updated, and Beson's email made me realize that I could go an do it myself. I did that by the time you check. slim's was updated and both packages are now in testing. Best, Ranjan On Sunday, May 14, 2023 at 10:49:44 AM CDT, Kevin Fenzi wrote: On Sun, May 14, 2023 at 02:04:57PM +0300, Benson Muite wrote: > Ranjan, > > On 5/14/23 13:46, Globe Trotter via devel wrote: > > Thanks! The package was cleared on BZ some time ago. Is there some > > additional review that is needed? > > > Sorry, that is correct. Usually state is set to post. It seems to have > been unretired: > https://pagure.io/releng/issue/11417 Yep. > Though project ownership has not been updated: > https://src.fedoraproject.org/rpms/oclock It looks updated to me? Did I miss something there? Do let me know in the ticket if so. > It seems Slim has been unretired: > https://pagure.io/releng/issue/11310 > and project ownership updated: > https://src.fedoraproject.org/rpms/slim > Maybe just need to add the new files? Yes, it should be unretired and all ready to push commits to/build/update. kevin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: review swaps
On Sun, May 14, 2023 at 12:17:09AM +0200, Alexander Ploumistos wrote: > Hi Zbigniew, > > > On Sat, May 13, 2023 at 11:55 PM Zbigniew Jędrzejewski-Szmek > wrote: > > > > I have a bunch of nice python packages looking for a reviewer: > > > > #2121902 pyinstrument - Python profiler with colorful output > > I've taken the profiler. Do you think you could take 2180418? I would > really appreciate your input. Thanks. It's definitely an interesting package ;). I left some initial comments. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Flatpaks without Modules (System-Wide Change)
On Fri, May 12, 2023 at 09:04:40PM -0400, Owen Taylor wrote: > > So, why having all those "Fedora Containers" releases in Bodhi which > > follow Fedora branches? Isn't just one Fedora Containers release enough? [...] > The "F38 Flatpaks" release in Bodhi represents Flatpaks built with the F38 > package set against the F8 runtime. But, yes, as you say we handle Flatpaks > as a single stream. Once we release Firefox into "F39 Flatpaks", everybody > on all releases gets that and we never do an update in "F38 Flatpaks" again. > > If updates *do* get pushed on multiple releases, last pushed wins. Might be > useful if we found that we pushed something to early or broken - but isn't > normal. > > But what if we had a single release instead? A few years ago, a design team contributor was working on an animated video extolling our painless upgrade process. But, in the midst of that, they updated to a new Fedora release, and discovered that Inkscape had dropped an obscure export format which they happened to rely on. I'd love it if we could produce both "fast" and "slow" streams. Ideally that's orthogonal to Fedora runtime release, but practically speaking that's what we have now. Maybe in the future we could build a "slow" stream as part of EPEL on a UBI or CentOS Stream runtime? -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Flatpaks without Modules (System-Wide Change)
On Fri, May 12, 2023 at 07:33:56PM +0200, Florian Weimer wrote: > I'm concerned that this is just like Software Collections with a > different path, which I believe where previously banned in Fedora (and > are generally a huge hassle on the releng side, I think). The main sticking point with Software Collections was the complixity it introduced into spec files -- lots of special macros that had to be used just-so. (And of course there were a lot of disagreements about naming things.) -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-05-15 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-05-15 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.libera.chat Greetings testers! It's meeting time again! 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. Toolbox criteria proposal 3. Fedora 39 status 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Review request for oclock package (orphaned since F35)
On Sun, May 14, 2023 at 02:04:57PM +0300, Benson Muite wrote: > Ranjan, > > On 5/14/23 13:46, Globe Trotter via devel wrote: > > Thanks! The package was cleared on BZ some time ago. Is there some > > additional review that is needed? > > > Sorry, that is correct. Usually state is set to post. It seems to have > been unretired: > https://pagure.io/releng/issue/11417 Yep. > Though project ownership has not been updated: > https://src.fedoraproject.org/rpms/oclock It looks updated to me? Did I miss something there? Do let me know in the ticket if so. > It seems Slim has been unretired: > https://pagure.io/releng/issue/11310 > and project ownership updated: > https://src.fedoraproject.org/rpms/slim > Maybe just need to add the new files? Yes, it should be unretired and all ready to push commits to/build/update. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 EPEL 9 - python3-pydot-1.4.2-6.el9.noarch python3-soupsieve-2.4.1-1.el9.noarch missing depedecies ...
Fedora 38 EPEL 9 python3-pydot-1.4.2-6.el9.noarch python3-soupsieve-2.4.1-1.el9.noarch missing depedecies ... Issue 1: Unable to install the best update candidate for package python3-pydot-1.4.2-5.fc38.noarch - nothing offers python(abi) = 3.9 which is needed for python3-pydot-1.4.2-6.el9.noarch - nothing offers python3.9dist(pyparsing) >= 2.1.4 which is needed for python3-pydot-1.4.2-6.el9.noarch Issue 2: Unable to install the best update candidate for package python3-soupsieve-2.3.2.post1-8.fc38.noarch - nothing offers python(abi) = 3.9 which is needed for python3-soupsieve-2.4.1-1.el9.noarch ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230514.n.0 changes
OLD: Fedora-Rawhide-20230513.n.0 NEW: Fedora-Rawhide-20230514.n.0 = SUMMARY = Added images:4 Dropped images: 1 Added packages: 1 Dropped packages:0 Upgraded packages: 15 Downgraded packages: 0 Size of added packages: 2.38 MiB Size of dropped packages:0 B Size of upgraded packages: 1.16 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 1.47 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Python_Classroom raw-xz aarch64 Path: Labs/aarch64/images/Fedora-Python-Classroom-Rawhide-20230514.n.0.aarch64.raw.xz Image: Python_Classroom live x86_64 Path: Labs/x86_64/iso/Fedora-Python-Classroom-Live-x86_64-Rawhide-20230514.n.0.iso Image: Python_Classroom vagrant-virtualbox x86_64 Path: Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-Rawhide-20230514.n.0.x86_64.vagrant-virtualbox.box Image: Python_Classroom vagrant-libvirt x86_64 Path: Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-Rawhide-20230514.n.0.x86_64.vagrant-libvirt.box = DROPPED IMAGES = Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230513.n.0.iso = ADDED PACKAGES = Package: mailman3-3.3.8-1.fc39 Summary: The GNU mailing list manager RPMs:mailman3 Size:2.38 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: fwupd-1.9.1-1.fc39 Old package: fwupd-1.8.15-1.fc39 Summary: Firmware update daemon RPMs: fwupd fwupd-devel fwupd-plugin-flashrom fwupd-plugin-modem-manager fwupd-plugin-uefi-capsule-data fwupd-tests Size: 20.50 MiB Size change: 795.06 KiB Changelog: * Sat May 13 2023 Richard Hughes - 1.9.1-1 - New upstream release Package: google-api-python-client-2:2.86.0-1.fc39 Old package: google-api-python-client-2:2.85.0-1.fc39 Summary: Google APIs Client Library for Python RPMs: python3-google-api-client Size: 4.21 MiB Size change: 7.59 KiB Changelog: * Sat May 13 2023 Mikel Olasagasti Uranga - 2:2.86.0-1 - Update to 2.86.0 - Closes rhbz#2187805 Package: hatch-1.7.0-3.fc39 Old package: hatch-1.7.0-2.fc39 Summary: A modern project, package, and virtual env manager RPMs: hatch Size: 291.70 KiB Size change: 120 B Changelog: * Sat May 13 2023 Benjamin A. Beasley - 1.7.0-3 - Drop lower-bound on pyproject-rpm-macros Package: kicad-1:7.0.3-1.fc39 Old package: kicad-1:7.0.2-1.fc39 Summary: EDA software suite for creation of schematic diagrams and PCBs RPMs: kicad kicad-doc kicad-packages3d Size: 910.88 MiB Size change: 673.17 KiB Changelog: * Sat May 13 2023 Steven A. Falco - 1:7.0.3-1 - Update to 7.0.3 Package: mate-media-1.26.1-1.fc39 Old package: mate-media-1.26.0-7.fc39 Summary: MATE media programs RPMs: mate-media Size: 1.28 MiB Size change: 888 B Changelog: * Sat May 13 2023 Wolfgang Ulbrich - 1.26.1-1 - update to 1.26.1 Package: mate-screensaver-1.26.2-1.fc39 Old package: mate-screensaver-1.26.1-3.fc38 Summary: MATE Screensaver RPMs: mate-screensaver mate-screensaver-devel Size: 23.03 MiB Size change: -10.30 KiB Changelog: * Sat May 13 2023 Wolfgang Ulbrich - 1.26.2-1 - update to 1.26.2 Package: opencv-4.7.0-7.fc39 Old package: opencv-4.7.0-6.fc39 Summary: Collection of algorithms for computer vision RPMs: opencv opencv-contrib opencv-core opencv-devel opencv-doc opencv-java python3-opencv Size: 220.87 MiB Size change: 9.19 KiB Changelog: * Sat May 13 2023 S??rgio Basto - 4.7.0-7 - Install python egg-info - Fix patch warning - Obsolete python2 < 4.7.0 (if someone want use an external python2 version} Package: perl-Sub-Uplevel-1:0.2800-19.fc39 Old package: perl-Sub-Uplevel-1:0.2800-19.fc38 Summary: Apparently run a function in a higher stack frame RPMs: perl-Sub-Uplevel Size: 27.88 KiB Size change: -37 B Package: perl-Taint-Runtime-0.03-48.fc39 Old package: perl-Taint-Runtime-0.03-47.fc38 Summary: Runtime enable taint checking RPMs: perl-Taint-Runtime Size: 97.62 KiB Size change: 435 B Changelog: * Sat May 13 2023 Paul Howarth - 0.03-48 - Spec tidy-up - Use SPDX-format license tag - Use author-independent source URL - Specify all dependencies - Fix permissions verbosely - Simplify find commands using -empty and -delete - Make %files list more explicit Package: plasma-discover-5.27.5-2.fc39 Old package: plasma-discover-5.27.5-1.fc39 Summary: KDE and Plasma resources management GUI RPMs: plasma-discover plasma-discover-flatpak plasma-discover-libs plasma-discover-notifier plasma-discover-offline-updates plasma-discover-packagekit plasma-discover-rpm-ostree plasma-discover-snap Size: 7.18 MiB Size change: 5.71 KiB Changelog: * Sat May 13 2023 Adam Williamson - 5.27.5-2 - Backport
Re: Review request for oclock package (orphaned since F35)
Ranjan, On 5/14/23 13:46, Globe Trotter via devel wrote: > Thanks! The package was cleared on BZ some time ago. Is there some > additional review that is needed? > Sorry, that is correct. Usually state is set to post. It seems to have been unretired: https://pagure.io/releng/issue/11417 Though project ownership has not been updated: https://src.fedoraproject.org/rpms/oclock It seems Slim has been unretired: https://pagure.io/releng/issue/11310 and project ownership updated: https://src.fedoraproject.org/rpms/slim Maybe just need to add the new files? > Best wishes, > Ranjan > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Review request for oclock package (orphaned since F35)
On 14-05-2023 12:40, Benson Muite wrote: It seems it is just the review that is needed: The re-review is done: https://bugzilla.redhat.com/show_bug.cgi?id=2025138 Releng unretiring the package is the next step, really. -- Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Review request for oclock package (orphaned since F35)
Benson, Thanks! The package was cleared on BZ some time ago. Is there some additional review that is needed? Best wishes, Ranjan On Sunday, May 14, 2023 at 05:41:35 AM CDT, Benson Muite wrote: Hi Ranjan, Thanks for contributing to Fedora and maintaining packages. On 5/14/23 03:27, Globe Trotter via devel wrote: > Thanks, Kevin! No problem, no rush, I did not quite know what to expect, > hence the questions. Thanks again! > > It seems it is just the review that is needed: https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_retired_packages/#unorphaning_and_unretiring_packages https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming Generally reviews go faster if the person asking for the review does a review of another package - many people ask for review swaps on this list. For a package with a reviewer you can add NEEDINFO in bugzilla so that if an person has assigned themselves as reviewer does not respond after a while, a new reviewer can take it up. > > > > > On Saturday, May 13, 2023 at 06:12:33 PM CDT, Kevin Fenzi > wrote: > > > > > > On Sat, May 13, 2023 at 02:41:10AM +0200, Sandro wrote: > >> On 11-05-2023 17:57, Globe Trotter via devel wrote: >>> Still no movement on my unretire requests for both slim and oclock, not >>> even a request for additional information. >> >> Tags have been added to the ticket. So, it has come up in one of the >> meetings. Supposedly, no-one has found the time yet to work on it. >> >> Feel free to ping in the ticket or bring it up in one of the meetings. > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Review request for oclock package (orphaned since F35)
On 14-05-2023 00:45, Globe Trotter via devel wrote: Thanks, Sandro! How does one ping in the ticket on paguire? The easiest way is to just leave a comment in the ticket. If you need info from a specific person you would tag that person (@fas_user). That ensures people watching the ticket queue get another notification, bringing the ticket to their attention again. But since Kevin already explained the delay, there's no need for that now. Either Kevin or the person returning from PTO next week will surely pick it up. -- Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Review request for oclock package (orphaned since F35)
Hi Ranjan, Thanks for contributing to Fedora and maintaining packages. On 5/14/23 03:27, Globe Trotter via devel wrote: > Thanks, Kevin! No problem, no rush, I did not quite know what to expect, > hence the questions. Thanks again! > > It seems it is just the review that is needed: https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_retired_packages/#unorphaning_and_unretiring_packages https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming Generally reviews go faster if the person asking for the review does a review of another package - many people ask for review swaps on this list. For a package with a reviewer you can add NEEDINFO in bugzilla so that if an person has assigned themselves as reviewer does not respond after a while, a new reviewer can take it up. > > > > > On Saturday, May 13, 2023 at 06:12:33 PM CDT, Kevin Fenzi > wrote: > > > > > > On Sat, May 13, 2023 at 02:41:10AM +0200, Sandro wrote: > >> On 11-05-2023 17:57, Globe Trotter via devel wrote: >>> Still no movement on my unretire requests for both slim and oclock, not >>> even a request for additional information. >> >> Tags have been added to the ticket. So, it has come up in one of the >> meetings. Supposedly, no-one has found the time yet to work on it. >> >> Feel free to ping in the ticket or bring it up in one of the meetings. > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
