Rust Stack Spring Cleaning - 2024 Edition

2024-04-11 Thread Fabio Valentini
Hello Rust packagers, I'm continuously working on reducing unnecessary accumulation of cruft in the Rust package stack in Fedora, and I have been keeping track of unused library packages for almost three years now. Some of these packages have been unused leaves for over two years! I will again

Fedora 40 compose report: 20240411.n.0 changes

2024-04-11 Thread Fedora Branched Report
OLD: Fedora-40-20240410.n.0 NEW: Fedora-40-20240411.n.0 = SUMMARY = Added images:1 Dropped images: 2 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

Re: convert everything to rpmautospec?

2024-04-11 Thread Pierre-Yves Chibon
On Thu, Apr 11, 2024 at 09:18:09AM +0200, Ondrej Mosnáček wrote: > On Wed, 10 Apr 2024 at 16:30, Pierre-Yves Chibon wrote: > [...] > > Let's look at it in another way: would you say that the people who leaved > > in the > > 14th century were liars for saying that the earth is flat? > > No, they

Merging /usr/sbin to /usr/bin

2024-04-11 Thread Zbigniew Jędrzejewski-Szmek
Hi! I'm trying to get https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin implemented. It was approved for F40, but only a few days before the mass rebuild, so there wasn't time to do much, so it was retargeted to F41. We now have some time before the F41 mass rebuild, so I want to push all

Re: Rust Stack Spring Cleaning - 2024 Edition

2024-04-11 Thread Ben Beasley
The rust-circular-buffer crate was packaged as a dependency for bpftop, https://github.com/Netflix/bpftop. I won’t necessarily be packaging bpftop myself, but I know several parties are interested in doing so, and I expect it will happen soon one way or the other. A few existing

Re: Merging /usr/sbin to /usr/bin

2024-04-11 Thread David Sastre
Not sure if SELinux policy needs to learn about the merge as well. Currently, `sudo semanage fcontext -l | rg bin.*=` shows: ``` /sbin = /usr/sbin /bin = /usr/bin ``` And there are executables in both /usr/bin and /usr/sbin with specific labels, e.g. `sudo semanage fcontext -l | rg bin/.*virt`

soname bump: mupdf 1.24.1 coming to rawhide and F40

2024-04-11 Thread Michael J Gruber
Hi there, 1.24.0 was followed by a mostly bugfix minor release 1.24.1, which bumped soname, though. I have been using this locally (first on F39, then on F40 beta) for a while now so that I'm confident we can bring it to both rawhide and F40. (Also, upstream has slowed down since...). I built

Fedora rawhide compose report: 20240411.n.0 changes

2024-04-11 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20240410.n.0 NEW: Fedora-Rawhide-20240411.n.0 = SUMMARY = Added images:3 Dropped images: 3 Added packages: 9 Dropped packages:19 Upgraded packages: 107 Downgraded packages: 0 Size of added packages: 32.01 MiB Size of dropped packages

Re: Self Introduction: Aditi Mishra

2024-04-11 Thread Dan Horák
Hello Aditi, On Thu, 11 Apr 2024 22:31:41 +0530 Aditi Mishra wrote: > Hello everyone, > > I'm very new to open-source world however I'm willing and passionate > candiate to work with you all. I had worked in the field of linux > scheduler area as an intern. Willing to learn fedora packing

Re: [Test-Announce] Re: Fedora 40 Candidate RC-1.12 Available Now! GRUB ISSUE

2024-04-11 Thread Leslie Satenstein via devel
Yesterday, Nov10, a set of "Final candidate" for Fedora 40 was posted.  Adam  requested that we test it to the ends and make sure all is OK. So, I suppose positively, that tomorrow, Friday, we will know if Fedora 40 is a go/nogo. For me, as a single distro to be installed, it is ready to go.

[Test-Announce] Re: Fedora Linux 40 Go/No-Go Meeting: 2024-11-04

2024-04-11 Thread Aoife Moloney
REMINDER: The Fedora Linux 40 Go/No-Go meeting is scheduled for today, 11th April @ 1700 UTC in in #meeting:fedoraproject.org channel on Matrix. Aoife Moloney Fedora Operations Architect On Mon, Apr 8, 2024, 10:23 PM Aoife Moloney wrote: > Happy Monday folks! > > On Thursday 11th April, the

Self Introduction: Aditi Mishra

2024-04-11 Thread Aditi Mishra
Hello everyone, I'm very new to open-source world however I'm willing and passionate candiate to work with you all. I had worked in the field of linux scheduler area as an intern. Willing to learn fedora packing and wants to contribute my work in future journey of fedora. Looking forward

Re: Merging /usr/sbin to /usr/bin

2024-04-11 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Apr 11, 2024 at 04:29:19PM +0200, David Sastre wrote: > Not sure if SELinux policy needs to learn about the merge as well. > Currently, `sudo semanage fcontext -l | rg bin.*=` shows: > > ``` > /sbin = /usr/sbin > /bin = /usr/bin > ``` > > And there are executables in both /usr/bin and

Re: Rust Stack Spring Cleaning - 2024 Edition

2024-04-11 Thread Fabio Valentini
On Thu, Apr 11, 2024 at 7:45 PM Ben Beasley wrote: > > The rust-circular-buffer crate was packaged as a dependency for bpftop, > https://github.com/Netflix/bpftop. > > I won’t necessarily be packaging bpftop myself, but I know several > parties are interested in doing so, and I expect it will

Re: Three steps we could take to make supply chain attacks a bit harder

2024-04-11 Thread Gary Buhrmaster
On Mon, Apr 1, 2024 at 1:10 AM Kilian Hanich via devel wrote: > 2FA in a lot of cases is just access to a different account (e.g. email > or even SMS) and these normally aren't unique. Sure, there are other > ways like FIDO2, but these are not necessarily used (or liked, quite > frankly I know a

Re: Three steps we could take to make supply chain attacks a bit harder

2024-04-11 Thread Adam Williamson
On Fri, 2024-04-12 at 00:09 +, Gary Buhrmaster wrote: > > What is the best way to formally propose > that 2FA is required for packagers after > some date There is already a FESCo ticket. https://pagure.io/fesco/issue/3186 / Please don't discuss there, discuss here; FESCo will vote in that

Re: Rust Stack Spring Cleaning - 2024 Edition

2024-04-11 Thread Michel Lind
On Thu, Apr 11, 2024 at 01:45:26PM -0400, Ben Beasley wrote: > The rust-circular-buffer crate was packaged as a dependency for bpftop, > https://github.com/Netflix/bpftop. > > I won’t necessarily be packaging bpftop myself, but I know several parties > are interested in doing so, and I expect it

Re: RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Miro Hrončok
On 11. 04. 24 22:41, Michel Lind wrote: The different Django stacks are in the process of being updated so they can be swapped without affecting dependents, by providing and conflicting with the virtual `python-django-impl`; not only will this allow us to swap one Django LTS for another in

Re: Rust Stack Spring Cleaning - 2024 Edition

2024-04-11 Thread Michel Lind
Hi Fabio, On Thu, Apr 11, 2024 at 03:26:13PM +0200, Fabio Valentini wrote: > If you know of a reason why a leaf package where I am the primary > maintainer should not be retired, please let me know, and I will > exclude it from the list. > Thanks for organizing the cleanup! > >

[Test-Announce] Fedora Linux 40 Final NO-GO

2024-04-11 Thread Aoife Moloney
Due to outstanding blocker bugs[1], the Fedora Linux 40 Final RC -1.13 was declared NO-GO in today's meeting[2][3]. The next Fedora Linux 40 Final Go/No-Go meeting[4] will be held at 1700 UTC on Thursday 18th April in #meeting:fedoraproject.org on Matrix. The new target date for the F40 Final

RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Michel Lind
Hi all, With the recent EOL of the Django 3.2 LTS series[^1], and Django being a key component of our mailing list infra for both Fedora and CentOS, I would like to propose the following plan to maintain Django in both Fedora and EPEL: - Fedora: `python-django` maintained as currently, not

Re: Merging /usr/sbin to /usr/bin

2024-04-11 Thread Brian C. Lane
On Thu, Apr 11, 2024 at 01:39:32PM +, Zbigniew Jędrzejewski-Szmek wrote: >https://src.fedoraproject.org/rpms/filesystem/pull-request/11 The commit "Symlink /usr/sbin to /usr/bin if possible" would wipe out any symlinks in /usr/sbin that point someplace other than /usr/bin when everything

Re: [Rust] Re: Rust Stack Spring Cleaning - 2024 Edition

2024-04-11 Thread Fabio Valentini
On Thu, Apr 11, 2024 at 9:09 PM Michel Lind wrote: > > > | rust-atomic-traits | 2022-09-02 | 587 | salimma > >| > Still trying to package mmtk, please keep this one for now Then please follow up, the review request for mmtk was closed due to inactivity:

Re: RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Michel Lind
On Fri, Apr 12, 2024 at 12:53:52AM +0200, Miro Hrončok wrote: > > > On 11. 04. 24 22:41, Michel Lind wrote: > > The different Django stacks are in the process of being updated so they > > can be swapped without affecting dependents, by providing and > > conflicting with the virtual

Re: Three steps we could take to make supply chain attacks a bit harder

2024-04-11 Thread Carlos Rodriguez-Fernandez
I was hesitant to have MFA for a while. Imagine losing a phone with tons of tokens. What a hassle to recover from that. I found it less than ideal for practical reasons. However, I decided instead to buy two Yubikey (primary and backup), and I add the QRs to both of them with the Yubico App.

Re: convert everything to rpmautospec?

2024-04-11 Thread Ondrej Mosnáček
On Wed, 10 Apr 2024 at 16:30, Pierre-Yves Chibon wrote: [...] > Let's look at it in another way: would you say that the people who leaved in > the > 14th century were liars for saying that the earth is flat? > No, they just didn't know. Off-topic and not really affecting the validity of your

Re: convert everything to rpmautospec?

2024-04-11 Thread Fabio Valentini
On Thu, Apr 11, 2024 at 12:39 PM Leon Fauster via devel wrote: > > Am 08.04.24 um 08:01 schrieb Miro Hrončok: > > On 08. 04. 24 6:08, Carlos Rodriguez-Fernandez wrote: > >> > >> Not all commits correspond with a new release downstream, and not all > >> commit messages are relevant to the end user

[SPDX] Mass license change Artistic 2.0 to Artistic-2.0

2024-04-11 Thread Miroslav Suchý
Hi. I am going to do the mass change of the license from Artistic 2.0 to Artistic-2.0 The proposed diff is in attachment. Affected packages: chordpro cleanfeed libkdtree++ R-AnnotationDbi perl-Data-IEEE754 mingw-ftplib nicstat perl-Test-Bits perl-MaxMind-DB-Common perl-MaxMind-DB-Reader-XS

Re: [SPDX] Mass license change Artistic 2.0 to Artistic-2.0

2024-04-11 Thread Petr Pisar
V Thu, Apr 11, 2024 at 01:04:22PM +0200, Miroslav Suchý napsal(a): > perl-Unix-Groups-FFI > perl-Unix-Groups-FFI You can remove perl-Unix-Groups-FFI from your list. I converted both of them. -- Petr signature.asc Description: PGP signature -- ___

Re: convert everything to rpmautospec?

2024-04-11 Thread Leon Fauster via devel
Am 08.04.24 um 08:01 schrieb Miro Hrončok: On 08. 04. 24 6:08, Carlos Rodriguez-Fernandez wrote: Not all commits correspond with a new release downstream, and not all commit messages are relevant to the end user to be part of the change log. For example, commits related with increasing

[Bug 2274529] New: perl-ExtUtils-HasCompiler-0.024 is available

2024-04-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2274529 Bug ID: 2274529 Summary: perl-ExtUtils-HasCompiler-0.024 is available Product: Fedora Version: rawhide Status: NEW Component: perl-ExtUtils-HasCompiler Keywords:

Re: Fedora Linux 40 Go/No-Go Meeting: 2024-11-04

2024-04-11 Thread Aoife Moloney
REMINDER: The Fedora Linux 40 Go/No-Go meeting is scheduled for today, 11th April @ 1700 UTC in in #meeting:fedoraproject.org channel on Matrix. Aoife Moloney Fedora Operations Architect On Mon, Apr 8, 2024, 10:23 PM Aoife Moloney wrote: > Happy Monday folks! > > On Thursday 11th April, the

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Sandro
On 11-04-2024 15:30, Sandro wrote: I see "# Package doesn't provide any tests" in the %check section. That certainly feels a bit dodgy. This successor of a test framework decided to ditch all of the tests it used to have? That is certainly a red flag. More like a chicken and egg story,

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Sandro
On 11-04-2024 15:49, Ben Beasley wrote: For a proposed nose successor, pynose doesn’t seem to have gained much community traction so far: it has seven stars on GitHub[1] (compared to 770 for nose2, which itself was never that widely adopted and has fewer than ten dependent packages in Fedora);

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Miro Hrončok
On 11. 04. 24 15:05, Sandro wrote: On 11-04-2024 13:54, Miro Hrončok wrote: On 11. 04. 24 11:55, Sandro wrote: While I ponder those thoughts some more, moving forward in either direction, the next step would be writing a change proposal? I'd start by: Packaging pynose without hacks (only

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Sandro
On 11-04-2024 15:17, Miro Hrončok wrote: On 11. 04. 24 15:05, Sandro wrote: On 11-04-2024 13:54, Miro Hrončok wrote: On 11. 04. 24 11:55, Sandro wrote: While I ponder those thoughts some more, moving forward in either direction, the next step would be writing a change proposal? I'd start

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Ben Beasley
For a proposed nose successor, pynose doesn’t seem to have gained much community traction so far: it has seven stars on GitHub[1] (compared to 770 for nose2, which itself was never that widely adopted and has fewer than ten dependent packages in Fedora); and the imperfect but fairly useful

[EPEL-devel] RFC: Proposing incompatible upgrade of python-asgiref from 3.4.1 to 3.7.2

2024-04-11 Thread Michel Lind
Dear all, Django 4.2 (the only currently supported LTS series) requires asgiref >= 3.6, so I would like to propose updating python-asgiref in EPEL 9 at least to 3.6.0, but ideally to 3.8.1 for future proofing. The affected packages (maintainers bcc:ed) are python-django3 (which I maintain, and

[Bug 2257224] perl-Clipboard: clipbrowse command execution with multi-line clipboard text including "| sh" [epel-all]

2024-04-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2257224 --- Comment #9 from Fedora Update System --- FEDORA-EPEL-2024-6ebc36e81d has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here:

RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Michel Lind
Hi all, With the recent EOL of the Django 3.2 LTS series[^1], and Django being a key component of our mailing list infra for both Fedora and CentOS, I would like to propose the following plan to maintain Django in both Fedora and EPEL: - Fedora: `python-django` maintained as currently, not

[EPEL-devel] RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Michel Lind
Hi all, With the recent EOL of the Django 3.2 LTS series[^1], and Django being a key component of our mailing list infra for both Fedora and CentOS, I would like to propose the following plan to maintain Django in both Fedora and EPEL: - Fedora: `python-django` maintained as currently, not

Re: RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Miro Hrončok
On 11. 04. 24 22:41, Michel Lind wrote: The different Django stacks are in the process of being updated so they can be swapped without affecting dependents, by providing and conflicting with the virtual `python-django-impl`; not only will this allow us to swap one Django LTS for another in

[EPEL-devel] Re: EPEL-ANNOUNCE Incompatible Upgrade of singularity-ce in EPEL 7 / 8 / 9

2024-04-11 Thread Jonathan Wright via epel-devel
Thank you for the followup. On Thu, Apr 11, 2024 at 7:51 PM David Trudgian via epel-devel < epel-devel@lists.fedoraproject.org> wrote: > The singularity-ce incompatible upgrade has now been pushed to stable. > > This is the final announcement prescribed by the EPEL Incompatible > Upgrades

[EPEL-devel] Re: EPEL-ANNOUNCE Incompatible Upgrade of singularity-ce in EPEL 7 / 8 / 9

2024-04-11 Thread David Trudgian via epel-devel
The singularity-ce incompatible upgrade has now been pushed to stable. This is the final announcement prescribed by the EPEL Incompatible Upgrades Policy: https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ Cheers, DT On 9 Feb 2024, at 10:45, David Trudgian wrote:

[EPEL-devel] Incompatible update of llhttp from 9.1.3 to 9.2.1 in EPEL9

2024-04-11 Thread Ben Beasley
I have just submitted for testing https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ce142428af, which updates llhttp in EPEL9 from 9.1.3 to 9.2.1 and fixes CVE-2024-27982[1], an HTTP request smuggling vulnerability. Version 9.2.0 also included a number of bug fixes[2]. This is an

[EPEL-devel] Fedora EPEL 7 updates-testing report

2024-04-11 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3cb841c5f0 chromium-123.0.6312.105-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a8b1cd8e52 perl-Clipboard-0.29-1.el7 The following

Re: RFC: Django latest vs LTS maintenance plan

2024-04-11 Thread Michel Lind
On Fri, Apr 12, 2024 at 12:53:52AM +0200, Miro Hrončok wrote: > > > On 11. 04. 24 22:41, Michel Lind wrote: > > The different Django stacks are in the process of being updated so they > > can be swapped without affecting dependents, by providing and > > conflicting with the virtual

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Sandro
On 10-04-2024 17:50, Miro Hrončok wrote: On 10. 04. 24 17:30, Sandro wrote: On 10-04-2024 12:04, Miro Hrončok wrote: On 09. 04. 24 19:30, Sandro wrote: Therefore, I'm thinking of introducing pynose as a drop in replacement of deprecated nose. Pynose uses the same namespace as nose, but

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Miro Hrončok
On 11. 04. 24 11:55, Sandro wrote: While I ponder those thoughts some more, moving forward in either direction, the next step would be writing a change proposal? I'd start by: Packaging pynose without hacks (only making it Conflict with nose, no compatibility Provides, Obsoletes or

Re: Idea: pynose as drop-in replacement for nose

2024-04-11 Thread Sandro
On 11-04-2024 13:54, Miro Hrončok wrote: On 11. 04. 24 11:55, Sandro wrote: While I ponder those thoughts some more, moving forward in either direction, the next step would be writing a change proposal? I'd start by: Packaging pynose without hacks (only making it Conflict with nose, no