[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-64174e7a0d gtkwave-3.3.118-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-8edcddc48e chromium-120.0.6099.216-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing cekit-4.10.0-1.el7 Details about builds: cekit-4.10.0-1.el7 (FEDORA-EPEL-2024-3601a754a5) Container image creation tool Update Information: CEKit 4.10 ChangeLog: * Fri Jan 12 2024 Nick Cross - 4.10.0-1 - Release 4.10.0 -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2258384] perl-Modern-Perl-1.20240115 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2258384 --- Comment #6 from Fedora Update System --- FEDORA-2024-32f516fb21 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-32f516fb21` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-32f516fb21 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258384 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258384%23c6 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-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 (2024-01-15)
= # #meeting:fedoraproject.org: fesco = Meeting started by @tstellar:fedora.im at 2024-01-15 19:30:47 Meeting summary --- * TOPIC: #3137 Change: Build Fedora Cloud Edition Images Using Kiwi in Koji (@tstellar:fedora.im, 19:37:57) * AGREED: APPROVED (+7, 1, -0) (@tstellar:fedora.im, 19:51:49) * TOPIC: Next week's chair (@tstellar:fedora.im, 19:52:34) * ACTION: Josh Stone will chair next meeting (@tstellar:fedora.im, 19:53:32) * TOPIC: Open Floor (@tstellar:fedora.im, 19:54:13) Meeting ended at 2024-01-15 20:22:01 Action items * Josh Stone will chair next meeting People Present (lines said) --- * @conan_kudo:matrix.org (55) * @sgallagh:fedora.im (39) * @tstellar:fedora.im (26) * @humaton:fedora.im (20) * @nhanlon:beeper.com (11) * @jistone:fedora.im (10) * @zodbot:fedora.im (8) * @dcantrell:fedora.im (6) * @davide:cavalca.name (4) * @nirik:matrix.scrye.com (4) * @meetbot:fedora.im (2) Full Meeting Log: https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-01-15/fesco.2024-01-15-19.30.log.txt -- ___ 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: side-tag with GCC 14.0.1 snapshot for Fedora 40
On Mon, Jan 15, 2024 at 10:37:10PM +0100, Jakub Jelinek wrote: > On Mon, Jan 15, 2024 at 09:33:34PM +, Richard W.M. Jones wrote: > > On Mon, Jan 15, 2024 at 02:01:06PM +0100, Jakub Jelinek wrote: > > > Hi! > > > > > > The f40-build-side-81394 side-tag contains new > > > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be > > > tagged into rawhide shortly before the mass rebuild. > > > > > > If there is anything you'd like to rebuild against it before the mass > > > rebuild (such as packages depending on Ada which like every year bumped > > > sonames of its shared libraries), please do so soon. > > > > I didn't build anything into the side tag, but I did download the > > packages and rebuilt a few virt-related packages like qemu, libvirt, > > virt tools, libguestfs, nbdkit. > > > > One thing I noticed (not virt related) was this PHP bindings failure: > > See https://github.com/php/php-src/pull/12821 That looks like it, thanks :-) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit -- ___ 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: side-tag with GCC 14.0.1 snapshot for Fedora 40
On Mon, Jan 15, 2024 at 09:33:34PM +, Richard W.M. Jones wrote: > On Mon, Jan 15, 2024 at 02:01:06PM +0100, Jakub Jelinek wrote: > > Hi! > > > > The f40-build-side-81394 side-tag contains new > > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be > > tagged into rawhide shortly before the mass rebuild. > > > > If there is anything you'd like to rebuild against it before the mass > > rebuild (such as packages depending on Ada which like every year bumped > > sonames of its shared libraries), please do so soon. > > I didn't build anything into the side tag, but I did download the > packages and rebuilt a few virt-related packages like qemu, libvirt, > virt tools, libguestfs, nbdkit. > > One thing I noticed (not virt related) was this PHP bindings failure: See https://github.com/php/php-src/pull/12821 Jakub -- ___ 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: side-tag with GCC 14.0.1 snapshot for Fedora 40
On Mon, Jan 15, 2024 at 02:01:06PM +0100, Jakub Jelinek wrote: > Hi! > > The f40-build-side-81394 side-tag contains new > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be > tagged into rawhide shortly before the mass rebuild. > > If there is anything you'd like to rebuild against it before the mass > rebuild (such as packages depending on Ada which like every year bumped > sonames of its shared libraries), please do so soon. I didn't build anything into the side tag, but I did download the packages and rebuilt a few virt-related packages like qemu, libvirt, virt tools, libguestfs, nbdkit. One thing I noticed (not virt related) was this PHP bindings failure: In file included from /usr/include/php/Zend/zend_globals.h:30, from /usr/include/php/Zend/zend_compile.h:769, from /usr/include/php/Zend/zend_modules.h:24, from /usr/include/php/Zend/zend_API.h:25, from /usr/include/php/main/php.h:35, from /home/rjones/d/libguestfs/php/extension/guestfs_php.c:44: /usr/include/php/Zend/zend_atomic.h: In function 'zend_atomic_bool_exchange_ex': /usr/include/php/Zend/zend_atomic.h:88:16: error: implicit declaration of function '__c11_atomic_exchange'; did you mean '__atomic_exchange'? [-Wimplicit-function-declaration] 88 | return __c11_atomic_exchange(>value, desired, __ATOMIC_SEQ_CST); |^ |__atomic_exchange /usr/include/php/Zend/zend_atomic.h: In function 'zend_atomic_bool_load_ex': /usr/include/php/Zend/zend_atomic.h:92:16: error: implicit declaration of function '__c11_atomic_load'; did you mean '__atomic_load'? [-Wimplicit-function-declaration] 92 | return __c11_atomic_load(>value, __ATOMIC_SEQ_CST); |^ |__atomic_load /usr/include/php/Zend/zend_atomic.h: In function 'zend_atomic_bool_store_ex': /usr/include/php/Zend/zend_atomic.h:96:9: error: implicit declaration of function '__c11_atomic_store'; did you mean '__atomic_store'? [-Wimplicit-function-declaration] 96 | __c11_atomic_store(>value, desired, __ATOMIC_SEQ_CST); | ^~ | __atomic_store Do you think it's OK to go with the suggestion of replacing the __c11_atomic_* functions with __atomic_* equivalents? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- ___ 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
[Bug 2256992] perl-CGI-Application-Plugin-Authentication-0.24 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2256992 Emmanuel Seyman changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-CGI-Application-Plugin ||-Authentication-0.24-1.fc40 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2024-01-15 20:44:28 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2345399 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256992 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202256992%23c1 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2257383] perl-HTML-TreeBuilder-LibXML-0.27 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2257383 Emmanuel Seyman changed: What|Removed |Added Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Fixed In Version||perl-HTML-TreeBuilder-LibXM ||L-0.27-1.fc40 Status|NEW |CLOSED Last Closed||2024-01-15 20:43:37 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2342874 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257383 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257383%23c1 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2257451] perl-CGI-Ex-2.55 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2257451 Emmanuel Seyman changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Fixed In Version||perl-CGI-Ex-2.55-1.fc40 Resolution|--- |RAWHIDE Status|NEW |CLOSED Last Closed||2024-01-15 20:42:24 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2345381 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257451 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257451%23c1 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 37 is EOL
On 15-01-2024 09:52, Vít Ondruch wrote: Any update? This ticket is still open: https://bugzilla.redhat.com/show_bug.cgi?id=2235331 I believe the script is chugging along. I've seen a few more bugs being closed the last couple of days. -- 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: Orphaned packages looking for new maintainers
On 15-01-2024 18:11, Miro Hrončok wrote:
On 15. 01. 24 16:46, Maxwell G wrote:
Report started at 2024-01-15 15:04:52 UTC
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know
for sure
that the package should be retired, please do so now with a proper
reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
...
Depending on: python-Pympler (64), status change: 2024-01-05 (1 weeks
ago)
...
python-attrs (maintained by: @python-packagers-sig, churchyard,
lbalhar)
python-attrs-23.1.0-4.fc39.src requires python3dist(pympler) =
1.0.1
This seems unused, I've opened:
https://src.fedoraproject.org/rpms/python-attrs/pull-request/19
The rest of the impacted packages pretty much depend on attrs, not pympler.
$ repoquery -q --repo=rawhide{,-source} --whatrequires python3-Pympler
matrix-synapse+cache_memory-0:1.98.0-3.fc40.x86_64
matrix-synapse-0:1.98.0-3.fc40.src
python-attrs-0:23.1.0-4.fc39.src
That is correct and the suggested removal of Pympler from attrs will
solve the problem for the indirectly impacted packages.
On the other hand, Pympler is what shows up on Packager Dashboard for
orphan-impacted packages as "remotely depends on orphaned package".
There, the dependency graph makes it clear that the intermediary package
is python-attrs.
I'm thinking the distinction between directly impacted and remotely
impacted as shown on the dashboard is actually rather helpful (as is the
graph itself). Maybe that is something that could be improved in the
scripts output?
For python-google-crc32c the list of indirectly impacted packages is
rather long. In fact, so long that the script truncates it. When I
looked into it last time, trying to find the connection between
python-plotnine and google-crc32c, I eventually gave up. That was before
I discovered the graph on the dashboard.
Today I ended up with something "horrible" like
fedrq wrsrc -X -F source python-google-crc32c | \
fedrq wrsrc -i -X -F source | \
fedrq wrsrc -i -X -F source | \
fedrq wrsrc -i -X -F source | \
fedrq wrsrc -i -X -F source
to arrive at plotnine.
I have yet to find a simple way of producing an output akin to the
dashboard graph for showing the chain of dependencies between two
packages. I'm open to suggestions.
-- 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: dnsmasq default configuration changed
On Mon, Jan 15, 2024 at 11:32 AM Kevin Kofler via devel wrote: > > Petr Menšík wrote: > > systemd-resolved is unfortunately known to broken. > [snip] > > Dnsmasq does not break DNSSEC, systemd-resolved does. > [snip] > > Unfortunately broken are clients having systemd-resolved enabled. > > How exactly is it broken? If you refer to: > https://github.com/systemd/systemd/issues/25676 > fixes for that are finally coming in now (as of 3 weeks ago). > > > I would recommend having systemd-resolved forwarded to dnsmasq, which can > > then be forwarded further. > > If you think dnsmasq should replace systemd-resolved by default, then please > propose that through the Changes process, which will also ensure the glibc > resolver, NetworkManager, and the like get configured properly for it. > Simply shipping dnsmasq with a default configuration that conflicts with > systemd-resolved is not a productive approach. > > If systemd-resolved is really broken, then it either needs to be fixed or > replaced. The former needs to be handled through systemd upstream, the > latter through the Fedora Changes process. > > > But this change should create conflict with systemd-resolved only in case > > it was improperly configured. > > But the default configuration you ship will conflict. > > > Anyway, dnsmasq will listen by default on 127.0.0.1, as every standard > > resolver does. You can use listen-address=127.0.0.53 if you like, but > > then it will conflict with systemd-resolved. > > You just wrote that you make it listen by default on all interfaces, and > then filter. This means it will conflict over the port 53. That said, > listening on the lo interface only will also conflict with systemd-resolved > or any other local resolver, so you are probably right that your change does > not change much for the default configuration, it just makes it harder (more > settings to change) to set up coexistence. 127.0.0.53 is unfortunately not > an independent interface, it is still the lo interface. > > > On 14. 01. 24 1:57, Kevin Kofler via devel wrote: > >> On a server I administer for work, I have dnsmasq serving the DNS for an > >> ocserv (OpenConnect) VPN, listening only on the VPN interface. Any > >> request for a host not within the VPN network (coming in from clients > >> with no or broken split DNS support, e.g., old GNU/Linux distros without > >> systemd- resolved, or Windows, where the OpenConnect client is still > >> unable to set up split DNS) is forwarded to systemd-resolved, which in > >> turn forwards it to the upstream DNS from the datacenter. Relying instead > >> on the filtering would not have worked exactly for the reason you > >> describe above. But that server is not running Fedora anyway. > > > > I would recommend to skip systemd-resolved stub and using > > resolv-file=/run/systemd/resolve/resolv.conf > > > > in such case. It would use servers configured by systemd-resolved, but > > without using broken port domain at address 127.0.0.53. Alternatively > > use server=127.0.0.54, which should not break incoming queries so much. > > Well, I do not see a good reason to disable systemd-resolved for the > server's own queries (which includes the forwarding queries from dnsmasq, if > the domain is not one it knows). It just works. > > > Consider using unbound as a cache for other VPN clients. dnsmasq is > > great for its integration with DHCP server, but is targeted to use > > minimal resources. Unfortunately at cost of some design issues. Unbound > > is a high quality cache, while still relatively small compared to bind's > > named.service. > > Using minimal resources is exactly what I want here. Which is why I do not > want to use dnsmasq for what systemd-resolved can do, nor unbound for what > dnsmasq can do. > > And sending the server's own queries through dnsmasq is not going to work > (not without a second instance, at least), because the VPN server is not a > VPN client, so I have the server's /etc/hosts resolve its own domain to > 127.0.0.1 (not the public IP, because services listen only on localhost and > the VPN, that is what the VPN is for), which is honored by systemd-resolved, > whereas my dnsmasq configuration overrides this to return the VPN IP to the > VPN clients querying that same domain. Sounds hackish, but works great. > Based on my reading of this thread, this change is going to break the default configuration and needs to be reverted immediately. Petr, please file a Change Proposal for Fedora *41*. You have missed the deadline for F40 System-Wide Changes (Dec. 26th) and this is absolutely NOT a self-contained Change. -- ___ 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:
Re: EncourageI686LeafRemoval Change: Please make sure it's actually a leaf package
On Mon, Jan 15, 2024, at 8:57 AM, Fabio Valentini wrote: > Hi all, > > I've been made aware that there has been a cascade of packages that > dropped i686 support in Rawhide, most of them referencing my > EncourageI686LeafRemoval Change Proposal, but none of which *actually > are* leaf packages: > > https://src.fedoraproject.org/rpms/composefs/c/b95af99 This one should be fixed by https://src.fedoraproject.org/rpms/composefs/c/c840e7496ad9a0a008903a4cfe5d38c22f49fd54?branch=rawhide > https://src.fedoraproject.org/rpms/xdg-desktop-portal/c/93310f7 > https://src.fedoraproject.org/rpms/gdm/c/940885b > https://src.fedoraproject.org/rpms/sssd/c/e0023ec I went ahead and pushed changes to these 3. -- ___ 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 Monday's FESCo Meeting (2024-01-15)
Following is the list of topics that will be discussed in the FESCo meeting Monday at 19:30UTC in #meeting:fedoraproject.org on Matrix. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2024-01-15 19:30 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = This meeting is moving from IRC to #meeting:fedoraproject.org on Matrix. = = Discussed and Voted in the Ticket = Title of issue https://pagure.io/fesco/issue/### DECISION (+X, Y, -Z) #3123 Change: Unified Kernel Support Phase Two https://pagure.io/fesco/issue/3123 APPROVED (+6, 0, 0) #3124 Permanent Update Policy Exception for certbot https://pagure.io/fesco/issue/3124 APPROVED (+7, 0, 0) #3131 Change: Enable IPv4 Address Conflict Detection by default https://pagure.io/fesco/issue/3131 APPROVED (+8, 0, 0) #3132 Change: Golang 1.22 https://pagure.io/fesco/issue/3132 APPROVED (+6, 0, 0) #3133 Change: Haskell GHC 9.6 and Stackage LTS 22 https://pagure.io/fesco/issue/3133 APPROVED (+8, 0, 0) #3134 Change: Rename/Change Firefox desktop file https://pagure.io/fesco/issue/3134 APPROVED (+7, 0, 0) #3135 Change: Unify /usr/bin and /usr/sbin https://pagure.io/fesco/issue/3135 APPROVED (+6, 1, 0) #3136 Change: Assign individual, stable MAC addresses for Wi-Fi connections https://pagure.io/fesco/issue/3136 APPROVED (+6, 1, 0) #3138 Change: Update Kubernetes to v1.29 in Rawhide https://pagure.io/fesco/issue/3138 APPROVED (+5, 0, 0) #3139 Change: LLVM 18 https://pagure.io/fesco/issue/3139 APPROVED (+6, 0, 0) #3140 Change: Remove Python Mock Usage https://pagure.io/fesco/issue/3140 APPROVED (+8, 0, 0) #3141 Change: SPDX License Phase 3 https://pagure.io/fesco/issue/3141 APPROVED (+7, 0, 0) #3142 Change: Move /var/run selinux-policy entries to /run https://pagure.io/fesco/issue/3142 After a week: APPROVED (+8, 0, 0) = New business = #3137 Change: Build Fedora Cloud Edition Images Using Kiwi in Koji https://pagure.io/fesco/issue/3137 = 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: EncourageI686LeafRemoval Change: Please make sure it's actually a leaf package
On Mon, Jan 15, 2024, at 8:57 AM, Fabio Valentini wrote: > Hi all, > > I've been made aware that there has been a cascade of packages that > dropped i686 support in Rawhide, most of them referencing my > EncourageI686LeafRemoval Change Proposal, but none of which *actually > are* leaf packages: > > https://src.fedoraproject.org/rpms/composefs/c/b95af99 Yes, this is what started it and we didn't realize the scope. > It looks like at least some of these changes were mistakenly pushed to > Rawhide while they should only apply to ELN / RHEL>=10? Agree, this is the simplest thing to do for now. -- ___ 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: auditd systemd preset
On Mon, Jan 15, 2024 at 12:01 PM Steve Grubb wrote: > > Hello, > > I have a procedural question. Auditd-4.0 is ready for release. One of the > major changes is splitting rule loading from logging in the service. IOW, it > was one service doing both and now would be two services. Auditd would depend > on the rule loader, but the rule loader would not depend on auditd in case > you wanted to log to journald only. > > Auditd is one of the few programs that has a preset such that if it is > installed, it is automatically enabled. I think we'd need the same thing for > the rule loading service. I have been testing it with an addition to /usr/ > lib/systemd/system-preset/90-default.preset and it seems to work as expected. > > Would this update require just a FESCO ticket asking for the preset or does > this need both a FESCO ticket and a self-contained change notice? > The official docs are here: https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/ There's a link in that doc above to create a Bugzilla ticket with boilerplate questions that gets forwarded to the fedora-release maintainers to review the request. (Usually, me). Based on those questions, I will either go ahead and make the change if it meets the requirements or else raise it to FESCo for approval if it isn't eligible to be auto-approved. -- ___ 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: Orphaned packages looking for new maintainers
On 15. 01. 24 16:46, Maxwell G wrote:
Report started at 2024-01-15 15:04:52 UTC
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
...
Depending on: python-Pympler (64), status change: 2024-01-05 (1 weeks ago)
...
python-attrs (maintained by: @python-packagers-sig, churchyard, lbalhar)
python-attrs-23.1.0-4.fc39.src requires python3dist(pympler) =
1.0.1
This seems unused, I've opened:
https://src.fedoraproject.org/rpms/python-attrs/pull-request/19
The rest of the impacted packages pretty much depend on attrs, not pympler.
$ repoquery -q --repo=rawhide{,-source} --whatrequires python3-Pympler
matrix-synapse+cache_memory-0:1.98.0-3.fc40.x86_64
matrix-synapse-0:1.98.0-3.fc40.src
python-attrs-0:23.1.0-4.fc39.src
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
___
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
auditd systemd preset
Hello, I have a procedural question. Auditd-4.0 is ready for release. One of the major changes is splitting rule loading from logging in the service. IOW, it was one service doing both and now would be two services. Auditd would depend on the rule loader, but the rule loader would not depend on auditd in case you wanted to log to journald only. Auditd is one of the few programs that has a preset such that if it is installed, it is automatically enabled. I think we'd need the same thing for the rule loading service. I have been testing it with an addition to /usr/ lib/systemd/system-preset/90-default.preset and it seems to work as expected. Would this update require just a FESCO ticket asking for the preset or does this need both a FESCO ticket and a self-contained change notice? Thanks, -Steve -- ___ 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: RFC: OpenScanHub Prototype for Fedora
On Tue, 2023-12-12 at 16:30 +0100, Siteshwar Vashisht wrote:
[...snip...]
Hi Siteshwar, thanks for working on this.
It looks like you're got the basic infrastructure of scanning working,
but the prototype seems to be missing some things that IMHO would be
essential to package maintainers actually using this, specifically:
- easy-to-read results (so that a maintainer can easily answer the
questions "what is the tool telling me?", "is this a real problem?",
"what can/should I do about this?")
- result management (e.g. "what issues have we seen in this past with
this package?", "is this a flaky test that keeps coming and going?",
etc)
[FWIW I'm the upstream author/maintainer of the GCC static analyzer;
I'm also on the SARIF technical committee.]
> There are 3 different types of scans supported by OpenScanHub:
>
> -
>
> MockBuild performs a full scan of the package including downstream
> patches. Example[8] mockbuild for `openssl-3.1.1-4.fc39`.
Looking at a result from the GCC static analyzer e.g. this -Wanalyzer-
deref-before-check:
https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/task/6/log/openssl-3.1.1-4.fc39/scan-results.html#def67
...I see that the scan-results.html view quoted the pertinent source
code (which is good), but unfortunately it only shows the summary
message from the diagnostic:
Error: GCC_ANALYZER_WARNING (CWE-465): [#def67]
openssl-3.1.1/crypto/bn/bn_blind.c: scope_hint: In function 'BN_BLINDING_update'
openssl-3.1.1/crypto/bn/bn_blind.c:108:12:
warning[-Wanalyzer-deref-before-check]: check of 'b' for NULL after already
dereferencing it
# 106| !(b->flags & BN_BLINDING_NO_RECREATE)) {
# 107| /* re-create blinding parameters */
# 108|-> if (!BN_BLINDING_create_param(b, NULL, NULL, ctx, NULL, NULL))
# 109| goto err;
# 110| } else if (!(b->flags & BN_BLINDING_NO_UPDATE)) {
But each diagnostic from the GCC analyzer has a list of events
associated with it, which contain essential information for a human to
understand the warning and evaluate it.
For the example above, if I look at the raw log:
https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/task/6/log/openssl-3.1.1-4.fc39/scan.log
...I see:
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c: In function
'BN_BLINDING_update': <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:108:12: warning: check
of 'b' for NULL after already dereferencing it [-Wanalyzer-deref-before-check]
<--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:93:5: note: (1) entry
to 'BN_BLINDING_update' <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:97:11: note: (2)
pointer 'b' is dereferenced here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:97:8: note: (3)
following 'false' branch... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:102:10: note: (4)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:105:8: note: (5)
following 'true' branch... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:108:14: note: (6)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:108:14: note: (7)
calling 'BN_BLINDING_create_param' from 'BN_BLINDING_update' <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:234:14: note: (8)
entry to 'BN_BLINDING_create_param' <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:247:8: note: (9)
following 'false' branch (when 'b' is non-NULL)... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:255:12: note: (10)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:255:8: note: (11)
following 'false' branch... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:257:12: note: (12)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:257:8: note: (13)
following 'false' branch... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:260:8: note: (14)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:260:8: note: (15)
following 'false' branch (when 'e' is NULL)... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:264:12: note: (16)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:264:8: note: (17)
following 'false' branch... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:267:8: note: (18)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:267:8: note: (19)
following 'false' branch (when 'bn_mod_exp' is NULL)... <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:269:8: note: (20)
...to here <--[gcc]
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:269:8: note: (21)
following 'false' branch (when 'm_ctx' is NULL)... <--[gcc]
cc1: note: (22) ...to here
/builddir/build/BUILD/openssl-3.1.1/crypto/bn/bn_blind.c:307:8: note: (23)
following
Re: dnsmasq default configuration changed
Petr Menšík wrote: > systemd-resolved is unfortunately known to broken. [snip] > Dnsmasq does not break DNSSEC, systemd-resolved does. [snip] > Unfortunately broken are clients having systemd-resolved enabled. How exactly is it broken? If you refer to: https://github.com/systemd/systemd/issues/25676 fixes for that are finally coming in now (as of 3 weeks ago). > I would recommend having systemd-resolved forwarded to dnsmasq, which can > then be forwarded further. If you think dnsmasq should replace systemd-resolved by default, then please propose that through the Changes process, which will also ensure the glibc resolver, NetworkManager, and the like get configured properly for it. Simply shipping dnsmasq with a default configuration that conflicts with systemd-resolved is not a productive approach. If systemd-resolved is really broken, then it either needs to be fixed or replaced. The former needs to be handled through systemd upstream, the latter through the Fedora Changes process. > But this change should create conflict with systemd-resolved only in case > it was improperly configured. But the default configuration you ship will conflict. > Anyway, dnsmasq will listen by default on 127.0.0.1, as every standard > resolver does. You can use listen-address=127.0.0.53 if you like, but > then it will conflict with systemd-resolved. You just wrote that you make it listen by default on all interfaces, and then filter. This means it will conflict over the port 53. That said, listening on the lo interface only will also conflict with systemd-resolved or any other local resolver, so you are probably right that your change does not change much for the default configuration, it just makes it harder (more settings to change) to set up coexistence. 127.0.0.53 is unfortunately not an independent interface, it is still the lo interface. > On 14. 01. 24 1:57, Kevin Kofler via devel wrote: >> On a server I administer for work, I have dnsmasq serving the DNS for an >> ocserv (OpenConnect) VPN, listening only on the VPN interface. Any >> request for a host not within the VPN network (coming in from clients >> with no or broken split DNS support, e.g., old GNU/Linux distros without >> systemd- resolved, or Windows, where the OpenConnect client is still >> unable to set up split DNS) is forwarded to systemd-resolved, which in >> turn forwards it to the upstream DNS from the datacenter. Relying instead >> on the filtering would not have worked exactly for the reason you >> describe above. But that server is not running Fedora anyway. > > I would recommend to skip systemd-resolved stub and using > resolv-file=/run/systemd/resolve/resolv.conf > > in such case. It would use servers configured by systemd-resolved, but > without using broken port domain at address 127.0.0.53. Alternatively > use server=127.0.0.54, which should not break incoming queries so much. Well, I do not see a good reason to disable systemd-resolved for the server's own queries (which includes the forwarding queries from dnsmasq, if the domain is not one it knows). It just works. > Consider using unbound as a cache for other VPN clients. dnsmasq is > great for its integration with DHCP server, but is targeted to use > minimal resources. Unfortunately at cost of some design issues. Unbound > is a high quality cache, while still relatively small compared to bind's > named.service. Using minimal resources is exactly what I want here. Which is why I do not want to use dnsmasq for what systemd-resolved can do, nor unbound for what dnsmasq can do. And sending the server's own queries through dnsmasq is not going to work (not without a second instance, at least), because the VPN server is not a VPN client, so I have the server's /etc/hosts resolve its own domain to 127.0.0.1 (not the public IP, because services listen only on localhost and the VPN, that is what the VPN is for), which is honored by systemd-resolved, whereas my dnsmasq configuration overrides this to return the VPN IP to the VPN clients querying that same domain. Sounds hackish, but works great. Kevin Kofler -- ___ 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
Orphaned packages looking for new maintainers
Report started at 2024-01-15 15:04:52 UTC The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/ Full report available at: https://a.gtmx.me/orphans/orphans.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager-dashboard.fedoraproject.org/ For all orphaned packages, see https://packager-dashboard.fedoraproject.org/orphan Package (co)maintainers Status Change 3proxyorphan 1 weeks ago cdsclient @astro-sig, orphan 2 weeks ago cp2k @scitech_sig, jussilehtola, 1 weeks ago lecris, orphan, tomspur csmithorphan 2 weeks ago drumstick0orphan, yanqiyu 2 weeks ago elpa @scitech_sig, orphan 1 weeks ago kf6-karchive @kde-sig, orphan 0 weeks ago kf6-kplotting @kde-sig, orphan 0 weeks ago kf6-networkmanager-qt @kde-sig, orphan 0 weeks ago kf6-syntax-highlighting @kde-sig, orphan 0 weeks ago kio-ftps @kde-sig, orphan, rdieter, 0 weeks ago than kjots @kde-sig, orphan 0 weeks ago kmag @kde-sig, orphan, rdieter, 0 weeks ago than kmetronomeorphan 2 weeks ago koko @kde-sig, orphan 0 weeks ago kongress @kde-sig, orphan,0 weeks ago thunderbirdtr kpipewire5@kde-sig, orphan 0 weeks ago libASLorion, orphan, slaanesh 4 weeks ago mygnuhealth orphan 2 weeks ago obs-service-cargo_vendor orphan 4 weeks ago php-PHP-CSS-Parserorphan 1 weeks ago python-GridDataFormats@scitech_sig, orphan 1 weeks ago python-Pymplerorphan 1 weeks ago python-colorspacious orphan 1 weeks ago python-compressed-rtf orphan 2 weeks ago python-google-cloud-access- @python-packagers-sig, fkolwa, 4 weeks ago approval miyunari, orphan python-google-cloud-access- @python-packagers-sig, fkolwa, 4 weeks ago context-manager miyunari, orphan python-google-cloud-api-gateway @python-packagers-sig, fkolwa, 4 weeks ago miyunari, orphan python-google-cloud-apigee- @python-packagers-sig, fkolwa, 4 weeks ago connect miyunari, orphan python-google-cloud-appengine-@python-packagers-sig, fkolwa, 4 weeks ago admin miyunari, orphan python-google-cloud-asset @python-packagers-sig, fkolwa, 4 weeks ago miyunari, orphan python-google-cloud-automl@python-packagers-sig, fkolwa, 4 weeks ago miyunari, orphan python-google-cloud-bigquery @python-packagers-sig, fkolwa, 4 weeks ago miyunari, orphan python-google-cloud-bigquery- @python-packagers-sig, fkolwa, 4 weeks ago connectionmiyunari, orphan
Re: dnsmasq default configuration changed
systemd-resolved is unfortunately known to broken. I would recommend having systemd-resolved forwarded to dnsmasq, which can then be forwarded further. Dnsmasq does not break DNSSEC, systemd-resolved does. But this change should create conflict with systemd-resolved only in case it was improperly configured. In all other cases, it should work independently on the same machine just fine. Anyway, dnsmasq will listen by default on 127.0.0.1, as every standard resolver does. You can use listen-address=127.0.0.53 if you like, but then it will conflict with systemd-resolved. On 14. 01. 24 1:57, Kevin Kofler via devel wrote: Petr Menšík wrote: That might create a regression in special case. If you are running by default systemd-resolved, it listens already on domain port on address 127.0.0.53 address. But if bind-interfaces or bind-dynamic is not used explicitly, dnsmasq will try to listen on wildcard address 0.0.0.0 and just filter incoming requests, accepting only those arriving on interface eth0. But if any service already listens on port domain, it will fail to listen on it and fail to start. But we run systemd-resolved by default these days, don't we? So making dnsmasq attempt by default to serve the same requests does not sound like a good idea to me. No, dnsmasq will serve addresses 127.0.0.1 and ::1. If you do not want it listening on wildcard address, please configure it explicitly by using bind-interfaces or bind-dynamic options. Otherwise make sure no other program listens on port 53 (domain), be it systemd-resolved, named, unbound or anything similar. On a server I administer for work, I have dnsmasq serving the DNS for an ocserv (OpenConnect) VPN, listening only on the VPN interface. Any request for a host not within the VPN network (coming in from clients with no or broken split DNS support, e.g., old GNU/Linux distros without systemd- resolved, or Windows, where the OpenConnect client is still unable to set up split DNS) is forwarded to systemd-resolved, which in turn forwards it to the upstream DNS from the datacenter. Relying instead on the filtering would not have worked exactly for the reason you describe above. But that server is not running Fedora anyway. Kevin Kofler -- Unfortunately broken are clients having systemd-resolved enabled. I would recommend to skip systemd-resolved stub and using resolv-file=/run/systemd/resolve/resolv.conf in such case. It would use servers configured by systemd-resolved, but without using broken port domain at address 127.0.0.53. Alternatively use server=127.0.0.54, which should not break incoming queries so much. Consider using unbound as a cache for other VPN clients. dnsmasq is great for its integration with DHCP server, but is targeted to use minimal resources. Unfortunately at cost of some design issues. Unbound is a high quality cache, while still relatively small compared to bind's named.service. Cheers, Petr -- Petr Menšík Software Engineer, RHEL Red Hat,http://www.redhat.com/ PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB OpenPGP_0x4931CA5B6C9FC5CB.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital 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
Re: EncourageI686LeafRemoval Change: Please make sure it's actually a leaf package
On 15. 01. 24 15:09, Pavel Březina wrote: Is there anything I should do to stop https://bodhi.fedoraproject.org/updates/FEDORA-2024-287a88fffd from landing in stable or is the negative karma enough? I don't see "Actions" button to revoke it. My experience with Bodhi is that the CLI is quite helpful when there is not a viable action in the web UI. I run: bodhi updates request FEDORA-2024-287a88fffd unpush And it worked. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- ___ 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: EncourageI686LeafRemoval Change: Please make sure it's actually a leaf package
On 1/15/24 14:57, Fabio Valentini wrote: Hi all, I've been made aware that there has been a cascade of packages that dropped i686 support in Rawhide, most of them referencing my EncourageI686LeafRemoval Change Proposal, but none of which *actually are* leaf packages: https://src.fedoraproject.org/rpms/composefs/c/b95af99 https://src.fedoraproject.org/rpms/ostree/c/af0a269 (correctly scoped to RHEL>=10) https://src.fedoraproject.org/rpms/flatpak/c/9e4df49 (correctly scoped to RHEL>=10) https://src.fedoraproject.org/rpms/xdg-desktop-portal/c/93310f7 https://src.fedoraproject.org/rpms/gdm/c/940885b https://src.fedoraproject.org/rpms/sssd/c/e0023ec It looks like at least some of these changes were mistakenly pushed to Rawhide while they should only apply to ELN / RHEL>=10? I suspect that these packages dropping i686 support will cause a ton of build failures during the upcoming mass rebuild. As the author of the EncourageI686LeafRemoval Change Proposal - please **DO NOT DO IT THIS WAY**. The Change Proposal was about dropping i686 builds from packages that are **LEAF PACKAGES**, not packages that are somewhere deep in the distro's dependency tree. Fabio Thank you for checking sssd update. Is there anything I should do to stop https://bodhi.fedoraproject.org/updates/FEDORA-2024-287a88fffd from landing in stable or is the negative karma enough? I don't see "Actions" button to revoke it. Thanks, Pavel. -- ___ 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
EncourageI686LeafRemoval Change: Please make sure it's actually a leaf package
Hi all, I've been made aware that there has been a cascade of packages that dropped i686 support in Rawhide, most of them referencing my EncourageI686LeafRemoval Change Proposal, but none of which *actually are* leaf packages: https://src.fedoraproject.org/rpms/composefs/c/b95af99 https://src.fedoraproject.org/rpms/ostree/c/af0a269 (correctly scoped to RHEL>=10) https://src.fedoraproject.org/rpms/flatpak/c/9e4df49 (correctly scoped to RHEL>=10) https://src.fedoraproject.org/rpms/xdg-desktop-portal/c/93310f7 https://src.fedoraproject.org/rpms/gdm/c/940885b https://src.fedoraproject.org/rpms/sssd/c/e0023ec It looks like at least some of these changes were mistakenly pushed to Rawhide while they should only apply to ELN / RHEL>=10? I suspect that these packages dropping i686 support will cause a ton of build failures during the upcoming mass rebuild. As the author of the EncourageI686LeafRemoval Change Proposal - please **DO NOT DO IT THIS WAY**. The Change Proposal was about dropping i686 builds from packages that are **LEAF PACKAGES**, not packages that are somewhere deep in the distro's dependency tree. 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
Re: side-tag with GCC 14.0.1 snapshot for Fedora 40
On Mon, Jan 15, 2024 at 01:15:12PM +, Sérgio Basto wrote: > On Mon, 2024-01-15 at 14:01 +0100, Jakub Jelinek wrote: > > The f40-build-side-81394 side-tag contains new > > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be > > tagged into rawhide shortly before the mass rebuild. > > > > If there is anything you'd like to rebuild against it before the mass > > rebuild (such as packages depending on Ada which like every year > > bumped > > sonames of its shared libraries), please do so soon. > > > I'd like bump soname of libjxl [1] and opencv > > [1] > https://src.fedoraproject.org/rpms/jpegxl If that soname bump is not GCC 14 related, please do that independently, the side-tag is meant solely for packages which depend on GCC major version. Jakub -- ___ 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] Kernel 6.7 Test Week Invitation
Hey All, I would like to invite all of you to participate in the Kernel 6.7 Test week is happening from 2024-01-21 to 2024-01-28. It's fairly simple, head over to the wiki [0] and read in detail about the test week and simply run the test case mentioned in[1] and enter your results. As usual, the Fedora QA team will hangout at #fedora-test-...@libera.chat for questions and discussion. Happy New Year :) [0] http://fedoraproject.org/wiki/Test_Day:2024-01-21_Kernel_6.7_Test_Week [1] https://testdays.fedoraproject.org/events/173 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ 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: side-tag with GCC 14.0.1 snapshot for Fedora 40
On Mon, Jan 15, 2024 at 2:15 PM Sérgio Basto wrote: > > On Mon, 2024-01-15 at 14:01 +0100, Jakub Jelinek wrote: > > Hi! > > > > The f40-build-side-81394 side-tag contains new > > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be > > tagged into rawhide shortly before the mass rebuild. > > > > If there is anything you'd like to rebuild against it before the mass > > rebuild (such as packages depending on Ada which like every year > > bumped > > sonames of its shared libraries), please do so soon. > > > I'd like bump soname of libjxl [1] and opencv > > [1] > https://src.fedoraproject.org/rpms/jpegxl These are unrelated to gcc, please handle them separately, preferably after the mass rebuild is finished. 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
[Bug 2258459] New: Upgrade perl-XML-RSS to 1.63
https://bugzilla.redhat.com/show_bug.cgi?id=2258459 Bug ID: 2258459 Summary: Upgrade perl-XML-RSS to 1.63 Product: Fedora Version: rawhide URL: https://metacpan.org/release/XML-RSS Status: NEW Component: perl-XML-RSS Assignee: spo...@gmail.com Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: or...@nwra.com, perl-devel@lists.fedoraproject.org, spo...@gmail.com Target Milestone: --- Classification: Fedora Latest Fedora delivers 1.62 version. Upstream released 1.63. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258459 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258459%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2251190] Upgrade perl-V to 0.19
https://bugzilla.redhat.com/show_bug.cgi?id=2251190 Jitka Plesnikova changed: What|Removed |Added Summary|Upgrade perl-V to 0.18 |Upgrade perl-V to 0.19 --- Comment #1 from Jitka Plesnikova --- Latest Fedora delivers 0.17 version. Upstream released 0.19. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2251190 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251190%23c1 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2258457] New: Upgrade perl-POSIX-strftime-Compiler to 0.46
https://bugzilla.redhat.com/show_bug.cgi?id=2258457 Bug ID: 2258457 Summary: Upgrade perl-POSIX-strftime-Compiler to 0.46 Product: Fedora Version: rawhide URL: https://metacpan.org/release/POSIX-strftime-Compiler Status: NEW Component: perl-POSIX-strftime-Compiler Assignee: rc040...@freenet.de Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, rc040...@freenet.de, xav...@bachelot.org Target Milestone: --- Classification: Fedora Latest Fedora delivers 0.45 version. Upstream released 0.46. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258457 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258457%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2258455] New: Upgrade perl-Plack to 1.0051
https://bugzilla.redhat.com/show_bug.cgi?id=2258455 Bug ID: 2258455 Summary: Upgrade perl-Plack to 1.0051 Product: Fedora Version: rawhide URL: https://metacpan.org/release/Plack Status: NEW Component: perl-Plack Assignee: rc040...@freenet.de Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org, ppi...@redhat.com, rc040...@freenet.de, xav...@bachelot.org Target Milestone: --- Classification: Fedora Latest Fedora delivers 1.0050 version. Upstream released 1.0051. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258455 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258455%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: side-tag with GCC 14.0.1 snapshot for Fedora 40
On Mon, 2024-01-15 at 14:01 +0100, Jakub Jelinek wrote: > Hi! > > The f40-build-side-81394 side-tag contains new > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be > tagged into rawhide shortly before the mass rebuild. > > If there is anything you'd like to rebuild against it before the mass > rebuild (such as packages depending on Ada which like every year > bumped > sonames of its shared libraries), please do so soon. I'd like bump soname of libjxl [1] and opencv [1] https://src.fedoraproject.org/rpms/jpegxl > Jakub > -- > ___ > 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 -- Sérgio M. B. -- ___ 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
side-tag with GCC 14.0.1 snapshot for Fedora 40
Hi! The f40-build-side-81394 side-tag contains new gcc, annobin, libtool and redhat-rpm-config for f40, meant to be tagged into rawhide shortly before the mass rebuild. If there is anything you'd like to rebuild against it before the mass rebuild (such as packages depending on Ada which like every year bumped sonames of its shared libraries), please do so soon. Jakub -- ___ 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
[Bug 2258449] New: Upgrade perl-DBIx-SearchBuilder to 1.80
https://bugzilla.redhat.com/show_bug.cgi?id=2258449 Bug ID: 2258449 Summary: Upgrade perl-DBIx-SearchBuilder to 1.80 Product: Fedora Version: rawhide URL: https://metacpan.org/release/DBIx-SearchBuilder Status: NEW Component: perl-DBIx-SearchBuilder Assignee: rc040...@freenet.de Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: lxt...@gmail.com, perl-devel@lists.fedoraproject.org, rc040...@freenet.de Target Milestone: --- Classification: Fedora Latest Fedora delivers 1.79 version. Upstream released 1.80. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258449 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258449%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20240115.n.0 changes
OLD: Fedora-Rawhide-20240114.n.0 NEW: Fedora-Rawhide-20240115.n.0 = SUMMARY = Added images:2 Dropped images: 2 Added packages: 4 Dropped packages:0 Upgraded packages: 61 Downgraded packages: 0 Size of added packages: 2.50 MiB Size of dropped packages:0 B Size of upgraded packages: 371.13 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -1.20 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20240115.n.0.iso Image: Silverblue dvd-ostree aarch64 Path: Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20240115.n.0.iso = DROPPED IMAGES = Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20240114.n.0.iso Image: Xfce raw-xz aarch64 Path: Spins/aarch64/images/Fedora-Xfce-Rawhide-20240114.n.0.aarch64.raw.xz = ADDED PACKAGES = Package: fplus-0.2.22-1.fc40 Summary: Functional Programming Library for C++ RPMs:fplus-devel Size:523.17 KiB Package: libcyaml-1.4.1-1.fc40 Summary: C library for reading and writing YAML RPMs:libcyaml libcyaml-devel Size:232.82 KiB Package: paho-cpp-1.3.2-1.fc40 Summary: Eclipse Paho MQTT C++ Client Library RPMs:paho-cpp paho-cpp-devel paho-cpp-doc Size:1.22 MiB Package: roctracer-6.0.0-2.fc40 Summary: ROCm Tracer Callback/Activity Library for Performance tracing AMD GPUs RPMs:roctracer roctracer-devel roctracer-doc Size:553.94 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: algol68g-3.4.6-1.fc40 Old package: algol68g-3.4.4-1.fc40 Summary: Algol 68 Genie compiler-interpreter RPMs: algol68g Size: 2.47 MiB Size change: 16.87 KiB Changelog: * Sun Jan 14 2024 Oleg Girko - 3.4.6-1 - Update to 3.4.6 Package: bluez-5.72-1.fc40 Old package: bluez-5.71-3.fc40 Summary: Bluetooth utilities RPMs: bluez bluez-cups bluez-deprecated bluez-hid2hci bluez-libs bluez-libs-devel bluez-mesh bluez-obexd Size: 9.83 MiB Size change: 23.99 KiB Changelog: * Sun Jan 14 2024 Peter Robinson - 5.72-1 - Update to 5.72 Package: can-utils-2023.03-1.fc40 Old package: can-utils-2021.08.0-5.fc39 Summary: SocketCAN user space utilities and tools RPMs: can-utils Size: 811.78 KiB Size change: 30.69 KiB Changelog: * Sun Jan 14 2024 Peter Robinson - 2023.03-1 - Update to 2023.03 Package: corectrl-1.3.9-2.fc40 Old package: corectrl-1.3.8-1.fc40 Summary: Friendly hardware control RPMs: corectrl Size: 3.76 MiB Size change: -21.13 KiB Changelog: * Sun Jan 14 2024 Packit - 1.3.9-1 - [packit] 1.3.9 upstream release - Resolves rhbz#2258338 * Sun Jan 14 2024 Artem Polishchuk - 1.3.9-2 - packit: Update config Package: drumstick-2.9.0-1.fc40 Old package: drumstick-2.8.1-1.fc40 Summary: C++/Qt5 wrapper around multiple MIDI interfaces RPMs: drumstick drumstick-devel drumstick-drumgrid drumstick-dumprmi drumstick-examples drumstick-guiplayer drumstick-vpiano Size: 21.87 MiB Size change: -3.27 KiB Changelog: * Sun Jan 14 2024 Yann Collette - 2.9.0-1 - New release 2.9.0 (RHBZ#2255730) Package: dsp-1.9-1.fc40 Old package: dsp-1.6-9.fc39 Summary: An audio processing program with an interactive mode RPMs: dsp ladspa-dsp-plugin Size: 606.38 KiB Size change: -42.62 KiB Changelog: * Sun Jan 14 2024 S??rgio Basto - 1.9-1 - Update dsp to 1.9 - Migrated to SPDX license (noop) Package: fedmsg-1.1.7-4.fc40 Old package: fedmsg-1.1.7-3.fc39 Summary: Tools for Fedora Infrastructure real-time messaging RPMs: fedmsg fedmsg-base fedmsg-doc python3-fedmsg Size: 625.12 KiB Size change: 560 B Changelog: * Fri Jan 12 2024 Maxwell G - 1.1.7-4 - Remove unused python3-mock dependency Package: g4music-3.5.1-1.fc40 Old package: g4music-3.4.1-1.fc40 Summary: Fast fluent lightweight music player written in GTK4 RPMs: g4music Size: 918.39 KiB Size change: 17.47 KiB Changelog: * Sun Jan 14 2024 Jerry James - 3.5.1-1 - Version 3.5.1 Package: gawk-abort-1.0.1-15.fc40 Old package: gawk-abort-1.0.1-14.fc39 Summary: Abort library for gawk RPMs: gawk-abort Size: 99.07 KiB Size change: 415 B Changelog: * Sun Jan 14 2024 Andrew Schorr - 1.0.1-15 - Update BuildRequires gawk(abi) to indicate compatibility with gawk 5.3 major api version 4 Package: gawk-errno-1.1.0-16.fc40 Old package: gawk-errno-1.1.0-15.fc39 Summary: Errno library for gawk RPMs: gawk-errno Size: 112.60 KiB Size change: -1.75 KiB Changelog: * Sun Jan 14 2024 Andrew Schorr - 1.1.0-16 - Update BuildRequires gawk(abi) to indicate compatibility with gawk 5.3 major api version 4 Package: gawk-json-1.0.2-15.fc40 Old package: gawk-json
[Bug 2258448] New: Upgrade perl-Cookie-Baker to 0.12
https://bugzilla.redhat.com/show_bug.cgi?id=2258448 Bug ID: 2258448 Summary: Upgrade perl-Cookie-Baker to 0.12 Product: Fedora Version: rawhide URL: https://metacpan.org/release/Cookie-Baker Status: NEW Component: perl-Cookie-Baker Assignee: rc040...@freenet.de Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, rc040...@freenet.de, xav...@bachelot.org Target Milestone: --- Classification: Fedora Latest Fedora delivers 0.11 version. Upstream released 0.12. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258448 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258448%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2251182] Upgrade perl-Config-Model-TkUI to 1.377
https://bugzilla.redhat.com/show_bug.cgi?id=2251182 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Config-Model-TkUI-1.37 ||9-1.fc40 Resolution|--- |ERRATA Status|MODIFIED|CLOSED Last Closed||2024-01-15 11:54:26 --- Comment #2 from Fedora Update System --- FEDORA-2024-3ddf87931c has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2251182 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251182%23c2 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2251182] Upgrade perl-Config-Model-TkUI to 1.377
https://bugzilla.redhat.com/show_bug.cgi?id=2251182 --- Comment #1 from Fedora Update System --- FEDORA-2024-3ddf87931c has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3ddf87931c -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2251182 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251182%23c1 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
redhat-rpm-config now tied to Changes/GNUToolchainF40
I pushed the changes that enable C type safety level handling once GCC 14 is merged and built it into the GCC 14 side tag (currently f40-build-side-81394). I didn't add any conflicts with GCC 13 because the incompatibility is only present if a package lowers the C type safety level to 0. Thanks, Florian -- ___ 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
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 15 January, 2024 (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 15 January at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix in the Fedora meeting channel: https://matrix.to/#/%23meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240115T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/01/15/next-open-neurofedora-meeting-15-january-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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
Re: libguestfs build failure (on riscv64, but seems general)
libguestfs-1.52.0-4.fc40 uses curl instead of wget{,2}:
https://koji.fedoraproject.org/koji/taskinfo?taskID=111777873
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
--
___
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
[Bug 2258384] perl-Modern-Perl-1.20240115 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2258384 --- Comment #5 from Fedora Update System --- FEDORA-2024-32f516fb21 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-32f516fb21 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258384 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258384%23c5 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2258384] perl-Modern-Perl-1.20240115 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2258384 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In Version||perl-Modern-Perl-1.20240115 ||-1.fc40 Status|MODIFIED|CLOSED Last Closed||2024-01-15 09:09:54 --- Comment #4 from Fedora Update System --- FEDORA-2024-3713e998d7 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258384 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258384%23c4 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2258384] perl-Modern-Perl-1.20240115 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2258384 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #3 from Fedora Update System --- FEDORA-2024-3713e998d7 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3713e998d7 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2258384 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202258384%23c3 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
libguestfs build failure (on riscv64, but seems general)
David, Thanks for notifying me about this build failure that happened while I was on holiday last week: http://fedora.riscv.rocks/koji/getfile?taskID=1594179=DEFAULT=root.log http://fedora.riscv.rocks/koji/getfile?taskID=1594179=DEFAULT=build.log I copied the relevant part from root.log & build.log at the end of the email in case those links go away. What's happening here is we're running this code to determine if this is a local build with the network available or a Koji build: https://src.fedoraproject.org/rpms/libguestfs/blob/rawhide/f/libguestfs.spec#_723 if ping -c 3 -w 20 8.8.8.8 && wget http://libguestfs.org -O /dev/null; then extra=# network is available else # assume no network, ie. Koji case As you can see from build.log we take the first branch, when we should be taking the second (no network / Koji) branch. The problem is that ping fails but wget succeeds, even though as you can see from the log it should be failing. This puzzled me for a while since it doesn't happen when I tested with 'wget' locally. However the problem here is we're using 'wget2' which seems to have broken exit codes. eg: $ wget --version GNU Wget2 2.1.0 - multithreaded metalink/file/website downloader $ wget http://nosuchdomainreallynodomain.abc -O /dev/null Failed to resolve 'nosuchdomainreallynodomain.abc' (Name or service not known) Failed to resolve 'nosuchdomainreallynodomain.abc' (Name or service not known) [...] $ echo $? 0 I think this test will fail to work properly anywhere that we are using wget2. Apparently regular Koji is using wget2 but ping fails there, so Koji acts slightly differently from fedora.riscv.rocks (but this is still a bug in wget2). I filed this bug upstream: https://gitlab.com/gnuwget/wget2/-/issues/652 I'll also look to see if I can adjust the test, maybe use curl instead. Rich. --- Snippets from root.log & build.log below --- DEBUG util.py:446: wget2riscv64 2.1.0-5.fc40 build 249 k DEBUG util.py:446: wget2-libs riscv64 2.1.0-5.fc40 build 223 k + ping -c 3 -w 20 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=42.6 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=42.5 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=42.5 ms --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2016ms rtt min/avg/max/mdev = 42.530/42.570/42.632/0.044 ms + wget http://libguestfs.org -O /dev/null Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to connect: General error Failed to resolve 'libguestfs.org' (Temporary failure in name resolution) + extra= -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler.
