Re: Second call for rebuilding powerdevil and call for help from provenpackagers
On Thu, Oct 26, 2023 at 4:57 PM Qiyu Yan wrote: > > Hi all, > > It is nearly a full month since last mail. And seems that koji has recycled > the side tags due to inactivity. I re-created them: > > f40-build-side-76474 > f39-build-side-76476 > f38-build-side-76478 > > Seems that I don't have the permission to push to powerdevil and rebuild it > so maybe any provenpackagers can help? > > Cheers, > Qiyu > > 在 2023/9/29 14:04, Qiyu Yan 写道: > > Hi all, > > I am planning to update package ddcutil to latest upstream release 2.0.0. > This will introduce a soname bump for libddcutil.so from libddcutil.4 to > libddcutil.5. I checked that the only affected package due to this update > will be powerdevil. > > dnf repoquery --whatrequires "libddcutil.so.4()(64bit)" --release=40 > ... > powerdevil-0:5.27.8-1.fc40.x86_64 > > I have built ddcutil in following side-tags: > > * f38-build-side-74742 > * f39-build-side-74740 > * f40-build-side-74738 > > If possible, please built powerdevil in those side-tags that we can push the > update together. > It seems this was going into my spam folder. I've CC'd Marc and Steve who are working on updating Plasma now. They should be able to coordinate with you. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Fwd: [F39 Beta] x86-64 Plymouth causes screen to stay black after boot
Hi, After I upgraded an old netbook of mine to Fedora 39, the screen stays black after the boot into multi-user.target is completed. Now I cannot see anything on the screen, however I can access the machine via SSH. I had a hunch that plymouth might be the reason for this behaviour, so i removed the plymouth packages from the system and rebooted. Now the boot completes and I can see the screen. Now long story short, I need some help to investigate what caused this, so I can file a proper report. I cannot seem to find anything useful, but I am willing to investigate what was the reason for this. Per DNF log I removed these packages: 2023-10-26T22:32:22+0200 DEBUG Removed: plymouth-22.02.122-5.fc39.x86_64 2023-10-26T22:32:22+0200 DEBUG Removed: plymouth-core-libs-22.02.122-5.fc39.x86_64 2023-10-26T22:32:22+0200 DEBUG Removed: plymouth-scripts-22.02.122-5.fc39.x86_64 Thanks, Vinny (evilissimo) ___ 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: Second call for rebuilding powerdevil and call for help from provenpackagers
Hi all, It is nearly a full month since last mail. And seems that koji has recycled the side tags due to inactivity. I re-created them: * f40-build-side-76474 * f39-build-side-76476 * f38-build-side-76478 Seems that I don't have the permission to push to powerdevil and rebuild it so maybe any provenpackagers can help? Cheers, Qiyu 在 2023/9/29 14:04, Qiyu Yan 写道: Hi all, I am planning to update package ddcutil to latest upstream release 2.0.0. This will introduce a soname bump for libddcutil.so from libddcutil.4 to libddcutil.5. I checked that the only affected package due to this update will be powerdevil. dnf repoquery --whatrequires "libddcutil.so.4()(64bit)" --release=40 ... powerdevil-0:5.27.8-1.fc40.x86_64 I have built ddcutil in following side-tags: * f38-build-side-74742 * f39-build-side-74740 * f40-build-side-74738 If possible, please built powerdevil in those side-tags that we can push the update together. Cheers, Qiyu ___ 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
Non-responsive maintainer check for eneville
Hi all, Does anybody know if eneville is still contributing to Fedora and / or how to reach them? c.f. https://bugzilla.redhat.com/show_bug.cgi?id=2246443 I see no activity in dist-git, bodhi, koji, or pagure.io in the last 365 days. Their packages seem to have been unmaintained for a while, and there is now also an open CVE issues against rust-pleaser: CVE-2023-46277 c.f. https://bugzilla.redhat.com/show_bug.cgi?id=2245340 Fabio ___ 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] Fedora Linux 39 Final is NO-GO (#3)
Due to outstanding blocker bugs[1], F39 Final RC-1.2 was declared NO-GO in today's Go/No-GO meeting[2]. The next Fedora Linux 39 Final Go/No-Go meeting[3] will be held at 1700 UTC on Thursday 2 November in #fedora-meeting. We will aim for the "target date #3" milestone of 7 November. The release schedule[4] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/39/final/buglist [2] https://meetbot-raw.fedoraproject.org/fedora-meeting/2023-10-26/f39-final-go_no_go-meeting.2023-10-26-17.00.html [3] https://calendar.fedoraproject.org/meeting/10627/?from_date=2023-10-30 [4] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html -- 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
Summary/Minutes from today's FESCo Meeting (2023-10-26)
= #fedora-meeting-2: FESCO (2023-10-26) = Meeting started by tstellar at 17:00:37 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2023-10-26/fesco.2023-10-26-17.00.log.html . Meeting summary --- * init process (tstellar, 17:00:56) * #3084 Re-evaluate -fno-omit-frame-pointer compile flag for F40 (tstellar, 17:04:16) * AGREED: FESCo indicates that there is nothing that indicates we need to do anything for -fno-omit-frame-pointer change. (+7, 0, -1) (Son_Goku, 17:27:15) * Next week's chair (tstellar, 17:27:50) * ACTION: tstellar will chair next meeting (tstellar, 17:31:45) * Open Floor (tstellar, 17:31:58) Meeting ended at 17:37:38 UTC. Action Items * tstellar will chair next meeting Action Items, by person --- * tstellar * tstellar will chair next meeting * **UNASSIGNED** * (none) People Present (lines said) --- * Son_Goku (40) * tstellar (33) * dcavalca (24) * zodbot (22) * sgallagh_ (21) * decathorpe (13) * zbyszek (11) * nirik (7) * rwmjones (7) * dcantrell (5) * mhayden (4) * michel-slm (1) * sgallagh (0) * mhroncok (0) * Conan_Kudo (0) * Pharaoh_Atem (0) * King_InuYasha (0) * Sir_Gallantmon (0) * Eighth_Doctor (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions ___ 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: looking for a maintainer for package remind
Hi Neil, Thanks a lot, much appreciated. Kurt On Wed, Oct 25, 2023 at 2:04 PM Neil Hanlon wrote: > Hi Kurt, > > I'd be happy to help maintain this with you. I've actually been looking > for something like Remind for a while now! > > Best, > Neil > > > On Wed, Oct 25, 2023, 07:33 Kurt Keller > wrote: > >> Remind (https://dianne.skoll.ca/projects/remind/) is a terminal based >> reminder utility (with optional Tk GUI frontend). It's kind of a >> supercharged version of the calendar utility. >> >> Remind has been in the fedora packages for many years, but the last >> update to it has happened in fc24 and after fc29 it got orphaned and >> disappeared. Installing the fc29 RPM on current fedora versions still works >> flawlessly but is, by now, somewhat out of date. >> >> I'd like to see the package back in the software channels and have >> updated the SPEC file for fc38 and version 04.02.06 of remind and created a >> pull request (https://src.fedoraproject.org/rpms/remind/pull-request/2). >> >> A request to unretire the package has been made ( >> https://pagure.io/releng/issue/11740). Doing so I learnt a bit more >> about the fedora software package world. I'm happy to help and support a >> package maintainer keeping things up to date and learn more along the way, >> but taking on the role as maintainer of the package is over the top of my >> head and my current abilities. So I'd like to ask if somebody was willing >> to take over the role as official maintainer for the remind package. >> >> Thanks, >> >> Kurt >> >> PS: >> An update to the recently released version 04.02.07 is already waiting in >> my fork: >> >> https://src.fedoraproject.org/fork/kkeller/rpms/remind/commits/remind_04.02.07-0.fc38 >> but unless somebody is willing to take over maintainership I don't see much >> use creating another pull request. >> ___ >> 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 > ___ 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
Schedule for Thursday's FESCo Meeting (2023-10-26)
Following is the list of topics that will be discussed in the FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on irc.libera.chat. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2023-10-26 17:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = New business = #3084 Re-evaluate -fno-omit-frame-pointer compile flag for F40 https://pagure.io/fesco/issue/3084 = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. ___ 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: aespipe - AES encrypting or decrypting pipe
On Thu, Oct 26, 2023 at 10:59 AM Jiri Hladky wrote: > > Hi, > > Review Request: aespipe - AES encrypting or decrypting pipe > https://bugzilla.redhat.com/show_bug.cgi?id=2244729 > > Spec URL: https://jhladky.fedorapeople.org/aespipe.spec > SRPM URL: https://jhladky.fedorapeople.org/aespipe-2.4g-1.fc40.src.rpm > > I'm trying to unretire the package. I have worked with upstream developer to > WA issues with compilation. > > Could anybody please help with the review? I've grabbed the review. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Review Request: aespipe - AES encrypting or decrypting pipe
Hi, Review Request: aespipe - AES encrypting or decrypting pipe https://bugzilla.redhat.com/show_bug.cgi?id=2244729 Spec URL: https://jhladky.fedorapeople.org/aespipe.spec SRPM URL: https://jhladky.fedorapeople.org/aespipe-2.4g-1.fc40.src.rpm I'm trying to unretire the package. I have worked with upstream developer to WA issues with compilation. Could anybody please help with the review? Thanks a lot Jirka ___ 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
Heads up: libpeas updated to 2.0 together with new libpeas1 compat package
Hi all, A quick heads up that I built updated libpeas 2.0 for F39 and rawhide and added a new libpeas1 compat package so that existing packages that use libpeas 1.x continue working without needing changes - the libpeas API has had a major revision in version 2.0 and it's not just the matter of rebuilding consumers against the new version. For GNOME 45 we need both APIs - gnome-builder 45 is using libpeas 2.0 but most other things are still on libpeas 1.x. Totem is getting ported upstream and was waiting on Fedora libpeas 2.0 packaging. Dependent package maintainers: I intend to keep libpeas1 around at least as long as it takes to get all of GNOME ported over, so there is no rush to get everything ported, but please poke your upstreams and ask them nicely if they want to switch over to libpeas 2.0 API. After GNOME is ported over I may hand the package over to someone else if there are still other packages using libpeas. -- Kalev ___ 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
Heads-up: python-pyrsistent 0.20.0 coming to Rawhide
In one week, 2023-11-02, or slightly later, I plan to build python-pyrsistent 0.20.0[1] in Rawhide/F40. The list of changes is at [2]. Notably, pyrsistent now freezes defaultdicts, which is considered a backwards-incompatible change. The only dependent package in Rawhide is python-sentry-sdk; it does not upper-bound the version of python-pyrsistent, and I checked compatibility in COPR[3]. [1] https://src.fedoraproject.org/rpms/python-pyrsistent/pull-request/7 [2] https://github.com/tobgu/pyrsistent/blob/v0.20.0/CHANGES.txt [3] https://copr.fedorainfracloud.org/coprs/music/pyrsistent/packages/ ___ 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 39 compose report: 20231026.n.0 changes
OLD: Fedora-39-20231025.n.0 NEW: Fedora-39-20231026.n.0 = SUMMARY = Added images:1 Dropped images: 4 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite dvd-ostree x86_64 Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-39-20231026.n.0.iso = DROPPED IMAGES = Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-39-20231025.n.0.iso Image: i3 live aarch64 Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-39-20231025.n.0.iso Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-39-20231025.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-39-20231025.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ 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: Help running centpkg
Also if there are any instructions somewhere on how to build just point me to them and I'll try to follow those. What I'd like to end up doing in the end is building rpms that I can install/test. Our team is planning to add an insights agent in RHEL and would like to be able to build/test in support of that. On Thu, Oct 26, 2023 at 9:36 AM Michael Dawson wrote: > When on the vpn it fails quickly with > > ⬢[midawson@toolbox nodejs]$ git checkout stream-nodejs-18-rhel-8.9.0 > branch 'stream-nodejs-18-rhel-8.9.0' set up to track > 'origin/stream-nodejs-18-rhel-8.9.0'. > Switched to a new branch 'stream-nodejs-18-rhel-8.9.0' > ⬢[midawson@toolbox nodejs]$ centpkg mockbuild > Downloading node-v18.17.1-stripped.tar.gz > > 100.0% > Downloading icu4c-73_1-src.zip > > 100.0% > Downloading undici-5.22.1.tar.gz > > 100.0% > Downloading cjs-module-lexer-1.2.2.tar.gz > > 100.0% > Downloading wasi-sdk-11.0-linux.tar.gz > > 100.0% > setting SOURCE_DATE_EPOCH=1692748800 > Wrote: /home/midawson/build-rhel/nodejs/nodejs-18.17.1-1.el8.src.rpm > Could not execute mockbuild: HTTPSConnectionPool(host=' > kojihub.stream.rdu2.redhat.com', port=443): Max retries exceeded with > url: /kojihub (Caused by SSLError(SSLCertVerificationError(1, '[SSL: > CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed > certificate in certificate chain (_ssl.c:1006)'))) > ⬢[midawson@toolbox nodejs]$ > > > On Thu, Oct 26, 2023 at 9:18 AM Michael Dawson > wrote: > >> When I ran yesterday it seemed to hang and I think from the error message >> I see today after leaving running it's because I was not on the vpn. I'll >> try on a machine with vpn access to see if that helps. >> >> In terms of --with-bundled Jan suggested I try that. I don't have a good >> understanding of what the difference was, but I'll try without it as well >> and see if I end up with usable rpms >> >> >> On Wed, Oct 25, 2023 at 11:04 PM Stephen Gallagher >> wrote: >> >>> On Wed, Oct 25, 2023 at 4:48 PM Michael Dawson >>> wrote: >>> > >>> > Thanks to the help and suggestions so far. I've gotten farther based >>> on the suggestion to use toolbox. Using the following I can get further >>> > >>> > toolbox create -i >>> quay.io/rhel-devel-tools/rhel-developer-toolbox:latest >>> > toolbox enter rhel-developer-toolbox-latest >>> > git clone https://gitlab.com/redhat/centos-stream/rpms/nodejs >>> > cd ndoejs >>> > centpkg mockbuild --with=bundled >>> > >>> > I'm not as far are getting the rpms built but it has helped me get >>> over the initial issue I was asking for help with. >>> >>> At that point, you're firmly into nodejs-specific packaging issues. In >>> particular, could you talk to why you're using `--with=bundled`? >>> That's a vestigial option that I should probably have excised years >>> ago. I haven't maintained it and it almost certainly doesn't work >>> these days due to bit-rot. If you could walk me through the issues >>> you're having with it, I can try to help. >>> >>> ___ 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: Help running centpkg
When on the vpn it fails quickly with ⬢[midawson@toolbox nodejs]$ git checkout stream-nodejs-18-rhel-8.9.0 branch 'stream-nodejs-18-rhel-8.9.0' set up to track 'origin/stream-nodejs-18-rhel-8.9.0'. Switched to a new branch 'stream-nodejs-18-rhel-8.9.0' ⬢[midawson@toolbox nodejs]$ centpkg mockbuild Downloading node-v18.17.1-stripped.tar.gz 100.0% Downloading icu4c-73_1-src.zip 100.0% Downloading undici-5.22.1.tar.gz 100.0% Downloading cjs-module-lexer-1.2.2.tar.gz 100.0% Downloading wasi-sdk-11.0-linux.tar.gz 100.0% setting SOURCE_DATE_EPOCH=1692748800 Wrote: /home/midawson/build-rhel/nodejs/nodejs-18.17.1-1.el8.src.rpm Could not execute mockbuild: HTTPSConnectionPool(host=' kojihub.stream.rdu2.redhat.com', port=443): Max retries exceeded with url: /kojihub (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)'))) ⬢[midawson@toolbox nodejs]$ On Thu, Oct 26, 2023 at 9:18 AM Michael Dawson wrote: > When I ran yesterday it seemed to hang and I think from the error message > I see today after leaving running it's because I was not on the vpn. I'll > try on a machine with vpn access to see if that helps. > > In terms of --with-bundled Jan suggested I try that. I don't have a good > understanding of what the difference was, but I'll try without it as well > and see if I end up with usable rpms > > > On Wed, Oct 25, 2023 at 11:04 PM Stephen Gallagher > wrote: > >> On Wed, Oct 25, 2023 at 4:48 PM Michael Dawson >> wrote: >> > >> > Thanks to the help and suggestions so far. I've gotten farther based on >> the suggestion to use toolbox. Using the following I can get further >> > >> > toolbox create -i >> quay.io/rhel-devel-tools/rhel-developer-toolbox:latest >> > toolbox enter rhel-developer-toolbox-latest >> > git clone https://gitlab.com/redhat/centos-stream/rpms/nodejs >> > cd ndoejs >> > centpkg mockbuild --with=bundled >> > >> > I'm not as far are getting the rpms built but it has helped me get over >> the initial issue I was asking for help with. >> >> At that point, you're firmly into nodejs-specific packaging issues. In >> particular, could you talk to why you're using `--with=bundled`? >> That's a vestigial option that I should probably have excised years >> ago. I haven't maintained it and it almost certainly doesn't work >> these days due to bit-rot. If you could walk me through the issues >> you're having with it, I can try to help. >> >> ___ 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 candidate composes coming - here's the plan
> Am 26.10.2023 um 03:44 schrieb Adam Williamson : > > On Wed, 2023-10-25 at 11:23 -0700, Adam Williamson wrote: >> Hey folks! Just to keep everyone in the loop regarding F39 plans. >> >> As you may have noticed, we've slipped once or twice already (depending >> on whether you count the "early target date") and are in danger of >> slipping again. The go/no-go meeting is scheduled for tomorrow (2023- >> 10-26). The outstanding blockers are all Raspberry Pi-related, aside >> from the shim one we've been waiving for several releases and intend to >> waive again. >> >> Matthew Miller, Kevin Fenzi and I came up with this plan: we're going >> to run a compose right now without fixes for the two outstanding Pi >> blockers (2241252 and 2244305). If QA can get sufficient testing on >> this done by the go/no-go meeting, we can discuss the possibility of >> shipping it and noting that there are known issues with Raspberry Pi >> that are taking time to resolve, and Pi users should not install or >> upgrade to F39 until they're resolved (or something like that). >> >> If at any point a fix for 2241252 shows up, we'll run another compose >> with the fix included. If that gets sufficient testing by the time of >> the meeting, we can also consider that as a candidate to ship. If ARM >> team decide to attempt a fix for 2244305 we'd also pull that in, but if >> not, we think it's reasonable to consider revoting or waiving that bug, >> as it seems not to happen very commonly or consistently and the >> proposed "fix" apparently comes with tradeoffs of some kind. >> >> So, QA folks, please stand ready to test one or two candidate composes >> soon. If we wind up with two, we will consider most test results to >> apply to both, as the only difference should be uboot-tools; we would >> want to run ARM hardware tests, at least, on both composes if possible. >> The usual announcement mails will be sent for the completed composes. >> >> Thanks folks! > > Update on this: the first candidate without Pi fixes is done and > currently available for testing - see > https://fedoraproject.org/wiki/Test_Results:Fedora_39_RC_1.1_Summary . > The second candidate is running, when it is done, > https://fedoraproject.org/wiki/Test_Results:Fedora_39_RC_1.2_Summary > will be live. > > Most tests of either candidate will be valid for both, but we > especially would like testing of the second candidate (when it's done) > on ARM hardware - obviously on Raspberry Pi, but also on any other ARM > hardware folks have lying around. We ended up having to revert uboot- > tools to an older version to try and address the Pi issues, so we need > to check that hasn't broken anything else important. If you run into > problems, please file a bug, propose it as a release blocker, and maybe > reply here just to be sure :) During the morning (in Europe) I tested F39 RC 1.2. The arm-installer has a serious bug which makes installation for all my SBCs impossible. I posted details on the ARM list. In my opinion we should either not release now or release without the ARM raw SBC images (and w/o arm-installer). We can then release those at a later date in the follow-up. I found a new issue in the Server full installer. After the message: Starting installer, one moment …. There are 10 lines showing the same message: ** (process:2431): Warning **: 13:01:21-525: expected enumeration type void, bit got PyBlockDevPlugin instead The Installation works, but showing error messages before the user, specifically new ones, hadn’t done anything, is a were bad show and is likely to undermine confidence in our (Fedora's) seriousness about quality assurance. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast ___ 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: Help running centpkg
When I ran yesterday it seemed to hang and I think from the error message I see today after leaving running it's because I was not on the vpn. I'll try on a machine with vpn access to see if that helps. In terms of --with-bundled Jan suggested I try that. I don't have a good understanding of what the difference was, but I'll try without it as well and see if I end up with usable rpms On Wed, Oct 25, 2023 at 11:04 PM Stephen Gallagher wrote: > On Wed, Oct 25, 2023 at 4:48 PM Michael Dawson > wrote: > > > > Thanks to the help and suggestions so far. I've gotten farther based on > the suggestion to use toolbox. Using the following I can get further > > > > toolbox create -i quay.io/rhel-devel-tools/rhel-developer-toolbox:latest > > toolbox enter rhel-developer-toolbox-latest > > git clone https://gitlab.com/redhat/centos-stream/rpms/nodejs > > cd ndoejs > > centpkg mockbuild --with=bundled > > > > I'm not as far are getting the rpms built but it has helped me get over > the initial issue I was asking for help with. > > At that point, you're firmly into nodejs-specific packaging issues. In > particular, could you talk to why you're using `--with=bundled`? > That's a vestigial option that I should probably have excised years > ago. I haven't maintained it and it almost certainly doesn't work > these days due to bit-rot. If you could walk me through the issues > you're having with it, I can try to help. > > ___ 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: 20231026.n.0 changes
OLD: Fedora-Rawhide-20231025.n.0 NEW: Fedora-Rawhide-20231026.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 4 Dropped packages:0 Upgraded packages: 99 Downgraded packages: 0 Size of added packages: 653.13 KiB Size of dropped packages:0 B Size of upgraded packages: 13.17 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -10.25 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20231026.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: composefs-1.0.1-2.fc40 Summary: Tools to handle creating and mounting composefs images RPMs:composefs composefs-devel composefs-libs Size:565.55 KiB Package: lsb_release-3.2-1.fc40 Summary: Linux Standard Base Release Tool using os-release(5) RPMs:lsb_release Size:19.63 KiB Package: perl-Authen-U2F-0.003-4.fc40 Summary: FIDO U2F library RPMs:perl-Authen-U2F Size:21.94 KiB Package: perl-Authen-U2F-Tester-0.03-4.fc40 Summary: FIDO/U2F Authentication Test Client RPMs:perl-Authen-U2F-Tester Size:46.02 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: PDAL-2.6.0-4.fc40 Old package: PDAL-2.6.0-3.fc40 Summary: Point Data Abstraction Library RPMs: PDAL PDAL-devel PDAL-doc PDAL-libs Size: 44.99 MiB Size change: 644 B Changelog: * Wed Oct 25 2023 Terje Rosten - 2.6.0-4 - Fix perms on some source and installed files and dirs Package: azure-cli-2.53.1-1.fc40 Old package: azure-cli-2.52.0-1.fc40 Summary: Microsoft Azure Command-Line Tools RPMs: azure-cli python3-azure-cli-core python3-azure-cli-telemetry python3-azure-cli-testsdk Size: 12.24 MiB Size change: 144.09 KiB Changelog: * Tue Sep 12 2023 Major Hayden - 2.52.0-2 - Allow older websocket-client on EL9 * Tue Sep 12 2023 Major Hayden - 2.52.0-3 - Allow older psutil/argcomplete for EL9 * Fri Sep 29 2023 Major Hayden - 2.53.0-1 - Update to 2.53.0 * Wed Oct 25 2023 Major Hayden - 2.53.1-1 - Update to 2.53.1 rhbz#2240840 Package: bdftopcf-1.1.1-1.fc40 Old package: bdftopcf-1.1-7.fc39 Summary: Font compiler for the X server and font server RPMs: bdftopcf Size: 132.92 KiB Size change: 497 B Changelog: * Tue Sep 05 2023 Peter Hutterer - SPDX migration: change to SPDX license identifier * Thu Oct 26 2023 Peter Hutterer - 1.1.1-1 - bdftopcf 1.1.1 Package: blosc2-2.10.5-2.fc40 Old package: blosc2-2.10.0-2.fc39 Summary: High performance compressor optimized for binary data RPMs: blosc2 blosc2-devel Size: 1.22 MiB Size change: 68.54 KiB Changelog: * Sun Aug 06 2023 Zbigniew J??drzejewski-Szmek - 2.10.1-1 - Version 2.10.1 (rhbz#2228597) * Wed Oct 25 2023 Zbigniew J??drzejewski-Szmek - 2.10.1-3 - Add packit config * Wed Oct 25 2023 Packit - 2.10.5-1 - [packit] 2.10.5 upstream release Package: chromium-118.0.5993.117-1.fc40 Old package: chromium-118.0.5993.88-1.fc40 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use RPMs: chromedriver chromium chromium-common chromium-headless Size: 266.13 MiB Size change: 8.54 KiB Changelog: * Wed Oct 25 2023 Than Ngo - 118.0.5993.117-1 - update to 118.0.5993.117 Package: dhcpcd-10.0.4-1.fc40 Old package: dhcpcd-10.0.2-2.fc39 Summary: A minimalistic network configuration daemon with DHCPv4, rdisc and DHCPv6 support RPMs: dhcpcd Size: 936.25 KiB Size change: 1.56 KiB Changelog: * Sun Jul 23 2023 Petr Menk - 10.0.2-3 - RPMAUTOSPEC: unresolvable merge * Sun Jul 23 2023 Petr Menk - 10.0.2-4 - Use /run directory, build test * Sun Jul 23 2023 Petr Menk - 10.0.2-5 - IPv4 tests fixes * Sun Jul 23 2023 Petr Menk - 10.0.2-6 - Fix building on recent epel * Sun Jul 23 2023 Petr Menk - 10.0.2-7 - More attempts to fix testing of ipv6 too * Wed Oct 25 2023 Pavol ??ik - 10.0.4-1 - Update to 10.04 Package: diskimage-builder-3.31.0-1.fc40 Old package: diskimage-builder-3.26.0-1.fc39 Summary: Image building tools for OpenStack RPMs: diskimage-builder Size: 1.09 MiB Size change: 43.73 KiB Changelog: * Wed Jul 19 2023 Fedora Release Engineering - 3.26.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Wed Oct 25 2023 Alfredo Moralejo 3.31.0-1 - Update to upstream version 3.31.0 Package: dotnet6.0-6.0.124-1.fc40 Old package: dotnet6.0-6.0.123-1.fc40 Summary: .NET Runtime and SDK RPMs: aspnetcore-runtime-6.0 aspnetcore-targeting-pack-6.0 dotnet dotnet-apphost-pack-6.0 dotnet-hostfxr-6.0 dotnet-runtime-6.0 dotnet-sdk-6.0 dotnet-sdk-6.0-source-built-artifacts dotnet-targeting-pack-6.0 dotnet-templates-6.0 Size: 7.00 GiB Size change: -2.20 MiB Chan
Bug 2246344 - Non-responsive maintainer check for hno
Hello, Please anyone knows about any other channel to contact hno - Henrik Nordstrom ? I have not heard from him for like a year and I would like to take over the primary admin role for the radare2 package so the bugs get primarily assigned to me. This is part of the non-responsive maintainer check for hno - Bug 2246344 https://bugzilla.redhat.com/show_bug.cgi?id=2246344 https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_ maintainers/ (https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/) Thank you Michal Ambroz ___ 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: Bodhi API does not list f39 in pending releases
On 10/25/23 19:14, Mattia Verga via devel wrote: Il 25/10/23 12:54, Tomas Hrcka ha scritto: This looks like a bug in bodhi. Actually, it was done that way on purpose. The HTML rendered output shows frozen releases in the same table of pending releases by a hack, but for API purposes I just let the output being pedantic about the requested state value. As wrote in another reply, you could query frozen releases with `?state=frozen`. If there is need to have a single query returns both pending and frozen, I suppose we could modify the input argument to accept a comma separated list of values, like `?state=pending,frozen`. I think this may be handy, but I don't need it for our case. It is easy to just combine the results on our side. Thank you, Pavel Mattia ___ 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
