Re: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 at 10:05:42AM +, Daniel P. Berrangé wrote: > On Mon, Mar 18, 2024 at 09:57:58AM +, Richard W.M. Jones wrote: > > > > https://src.fedoraproject.org/rpms/xnvme/adduser > > > > I try to add karlowich (https://accounts.fedoraproject.org/user/karlowich/) > > but his name doesn't appear in the username field even though he's > > in the packager group. Why? > > If they were only recently granted packager status, they might need login > to 'src.fedoraproject.org' to (re)sync group membership perhaps ? Thanks everyone, I'll have him try this. 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
Re: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 at 10:14:38AM +, Richard W.M. Jones wrote: > On Mon, Mar 18, 2024 at 10:05:42AM +, Daniel P. Berrangé wrote: > > On Mon, Mar 18, 2024 at 09:57:58AM +, Richard W.M. Jones wrote: > > > > > > https://src.fedoraproject.org/rpms/xnvme/adduser > > > > > > I try to add karlowich > > > (https://accounts.fedoraproject.org/user/karlowich/) > > > but his name doesn't appear in the username field even though he's > > > in the packager group. Why? > > > > If they were only recently granted packager status, they might need login > > to 'src.fedoraproject.org' to (re)sync group membership perhaps ? > > Thanks everyone, I'll have him try this. No luck. He's apparently tried logging out / in a few times and doesn't appear in the list. Is there something else he needs to try? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- ___ 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
Why can't I add karlowich as co-maintainer of this package?
https://src.fedoraproject.org/rpms/xnvme/adduser I try to add karlowich (https://accounts.fedoraproject.org/user/karlowich/) but his name doesn't appear in the username field even though he's in the packager group. Why? 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: Why can't I add karlowich as co-maintainer of this package?
On Mon, 18 Mar 2024 09:57:58 + "Richard W.M. Jones" wrote: > > https://src.fedoraproject.org/rpms/xnvme/adduser > > I try to add karlowich (https://accounts.fedoraproject.org/user/karlowich/) > but his name doesn't appear in the username field even though he's > in the packager group. Why? they might need to re-login to src.fp.o after being added to the packager group to refresh the permissions Dan -- ___ 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: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 09:57:58 +, Richard W.M. Jones wrote: > > https://src.fedoraproject.org/rpms/xnvme/adduser > > I try to add karlowich (https://accounts.fedoraproject.org/user/karlowich/) > but his name doesn't appear in the username field even though he's > in the packager group. Why? Have they logged out and back into src.fp.o? IIRC that's required for it to sync account info with FAS, so one has to do it once after being added to the packager group in FAS. -- 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: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 at 09:57:58AM +, Richard W.M. Jones wrote: > > https://src.fedoraproject.org/rpms/xnvme/adduser > > I try to add karlowich (https://accounts.fedoraproject.org/user/karlowich/) > but his name doesn't appear in the username field even though he's > in the packager group. Why? If they were only recently granted packager status, they might need login to 'src.fedoraproject.org' to (re)sync group membership perhaps ? With regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| -- ___ 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: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 at 1:51 PM Richard W.M. Jones wrote: > > On Mon, Mar 18, 2024 at 10:14:38AM +, Richard W.M. Jones wrote: > > On Mon, Mar 18, 2024 at 10:05:42AM +, Daniel P. Berrangé wrote: > > > On Mon, Mar 18, 2024 at 09:57:58AM +, Richard W.M. Jones wrote: > > > > > > > > https://src.fedoraproject.org/rpms/xnvme/adduser > > > > > > > > I try to add karlowich > > > > (https://accounts.fedoraproject.org/user/karlowich/) > > > > but his name doesn't appear in the username field even though he's > > > > in the packager group. Why? > > > > > > If they were only recently granted packager status, they might need login > > > to 'src.fedoraproject.org' to (re)sync group membership perhaps ? > > > > Thanks everyone, I'll have him try this. > > No luck. He's apparently tried logging out / in a few times and > doesn't appear in the list. Is there something else he needs to try? It appears that src.fp.o does not know about him *at all*: https://src.fedoraproject.org/user/karlowich Note that the logging out / back in needs to happen on src.fedoraproject.org, not with any other Fedora service. For me, sometimes opening "src.fedoraproject.org" in an incognito browser window and logging in there has helped. 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: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 at 01:55:14PM +0100, Fabio Valentini wrote: > On Mon, Mar 18, 2024 at 1:51 PM Richard W.M. Jones wrote: > > > > On Mon, Mar 18, 2024 at 10:14:38AM +, Richard W.M. Jones wrote: > > > On Mon, Mar 18, 2024 at 10:05:42AM +, Daniel P. Berrangé wrote: > > > > On Mon, Mar 18, 2024 at 09:57:58AM +, Richard W.M. Jones wrote: > > > > > > > > > > https://src.fedoraproject.org/rpms/xnvme/adduser > > > > > > > > > > I try to add karlowich > > > > > (https://accounts.fedoraproject.org/user/karlowich/) > > > > > but his name doesn't appear in the username field even though he's > > > > > in the packager group. Why? > > > > > > > > If they were only recently granted packager status, they might need > > > > login > > > > to 'src.fedoraproject.org' to (re)sync group membership perhaps ? > > > > > > Thanks everyone, I'll have him try this. > > > > No luck. He's apparently tried logging out / in a few times and > > doesn't appear in the list. Is there something else he needs to try? > > It appears that src.fp.o does not know about him *at all*: > https://src.fedoraproject.org/user/karlowich > > Note that the logging out / back in needs to happen on > src.fedoraproject.org, not with any other Fedora service. > For me, sometimes opening "src.fedoraproject.org" in an incognito > browser window and logging in there has helped. Yes that worked, 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: Follow up for bash-completion pkgconfig file packaging change
On 18. 03. 24 16:33, Mamoru TASAKA wrote: Hello, all: After investigating the recent Fedora-Security-Live livespin compose failure on F-41, it is found that this is caused because: - Recently on F-41, bash-completion packaging changed so that pkgconfig file is moved into -devel subpackage: (bash-completion-2.11-15.fc41) https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc68efdd519b78fccca416cad94?branch=rawhide - A package (lynis) installing bash-completion file into the directory $(pkg-config --variable=completionsdir bash-completion), had "BuildRequires: bash-completion", but did not have "BuildRequires: pkgconfig(bash-completion)". - So after the above bash-completion side packaging change, the above command line was expanded to the empty string, so the completion file was installed into the wrong directory, which caused conflict with filesystem rpm. I've commented about his at https://bugzilla.redhat.com/show_bug.cgi?id=1457164#c8 a month ago but so far no response. So on F-41(rawhide), the packages * trying to install bash-completion file using $(pkg-config --variable=completionsdir bash-completion) * which have "BuildRequires: bash-completion", but do NOT have "BuildRequires: pkgconfig(bash-completion)" may be installing completion file into wrong directories after rebuild. (At least, I tried rebuilding cowsay and actually it installs completion file into the wrong directory). The possible packages which may need fixing are: ... 13 python-django/rawhide/python-django.spec bashcompdir=$(pkg-config --variable=completionsdir bash-completion) I opened https://src.fedoraproject.org/rpms/python-django/pull-request/37 5 days ago. -- 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
Schedule for Monday's FESCo Meeting (2024-03-18)
Following is the list of topics that will be discussed in the FESCo meeting Monday at 19:30 UTC 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-03-11 19:30 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = New business = #3178 Consider relegating ARM to non-blocking status https://pagure.io/fesco/issue/3178 #3177 NodeJS packaging guidelines clarification https://pagure.io/fesco/issue/3177 = Followups = = 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. publickey - jednorozec@radioypsilon.eu - 0x8E713EA4.asc Description: application/pgp-keys 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
Follow up for bash-completion pkgconfig file packaging change
Hello, all:
After investigating the recent Fedora-Security-Live livespin compose failure
on F-41, it is found that this is caused because:
- Recently on F-41, bash-completion packaging changed so that pkgconfig file
is moved into -devel subpackage: (bash-completion-2.11-15.fc41)
https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc68efdd519b78fccca416cad94?branch=rawhide
- A package (lynis) installing bash-completion file into the directory
$(pkg-config --variable=completionsdir bash-completion), had "BuildRequires:
bash-completion",
but did not have "BuildRequires: pkgconfig(bash-completion)".
- So after the above bash-completion side packaging change, the above command line was
expanded to the empty string, so the completion file was installed into the
wrong directory,
which caused conflict with filesystem rpm.
So on F-41(rawhide), the packages
* trying to install bash-completion file using $(pkg-config
--variable=completionsdir bash-completion)
* which have "BuildRequires: bash-completion", but do NOT have "BuildRequires:
pkgconfig(bash-completion)"
may be installing completion file into wrong directories after rebuild.
(At least, I tried rebuilding cowsay and actually it installs completion file
into the wrong
directory).
The possible packages which may need fixing are:
1 cowsay/rawhide/cowsay.spec %global compdir %(pkg-config
--variable=completionsdir bash-completion)
2 creds/rawhide/creds.spec%global bashcompdir %(pkg-config
--variable=completionsdir bash-completion)
3 datamash/rawhide/datamash.spec pkg-config --variable=completionsdir
bash-completion ||
4 dracut/rawhide/dracut.spec
--bashcompletiondir=$(pkg-config --variable=completionsdir bash-completion) \
5 eg/rawhide/eg.spec bashcompdir=$(pkg-config
--variable=completionsdir bash-completion || :)
6 fedpkg/rawhide/fedpkg.spec %define compdir %(pkg-config
--variable=completionsdir bash-completion)
7 git-annex/rawhide/git-annex.spec
bash_completion_dir=%{buildroot}$(pkg-config --variable=completionsdir
bash-completion)
8 gromacs/rawhide/gromacs.spec%define compdir %(pkg-config
--variable=completionsdir bash-completion)
9 kim-api/rawhide/kim-api.spec%global b_compdir %(pkg-config
--variable=completionsdir bash-completion)
10 mpc/rawhide/mpc.spec%global compdir %(pkg-config
--variable=completionsdir bash-completion)
11 mt-st/rawhide/mt-st.specCOMPLETIONDIR=%{buildroot}$(pkg-config
--variable=completionsdir bash-completion)
12 pybugz/rawhide/pybugz.spec %global bash_cmpl_dir %(pkg-config
--variable=completionsdir bash-completion)
13 python-django/rawhide/python-django.spec
bashcompdir=$(pkg-config --variable=completionsdir bash-completion)
14 python-vitrageclient/rawhide/python-vitrageclient.spec
bashcompdir=$(pkg-config --variable=completionsdir bash-completion)
15 tig/rawhide/tig.spec%global bash_completion_dir %(pkg-config
--variable=completionsdir bash-completion || echo /etc/bash_completion.d)/
Regards,
Mamoru
--
___
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: Follow up for bash-completion pkgconfig file packaging change
On Mon, Mar 18, 2024 at 4:33 PM Mamoru TASAKA wrote:
>
> Hello, all:
>
> After investigating the recent Fedora-Security-Live livespin compose failure
> on F-41, it is found that this is caused because:
>
> - Recently on F-41, bash-completion packaging changed so that pkgconfig file
>is moved into -devel subpackage: (bash-completion-2.11-15.fc41)
>
> https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc68efdd519b78fccca416cad94?branch=rawhide
>
> - A package (lynis) installing bash-completion file into the directory
>$(pkg-config --variable=completionsdir bash-completion), had
> "BuildRequires: bash-completion",
>but did not have "BuildRequires: pkgconfig(bash-completion)".
>
> - So after the above bash-completion side packaging change, the above command
> line was
>expanded to the empty string, so the completion file was installed into
> the wrong directory,
>which caused conflict with filesystem rpm.
>
>
> So on F-41(rawhide), the packages
>
> * trying to install bash-completion file using $(pkg-config
> --variable=completionsdir bash-completion)
> * which have "BuildRequires: bash-completion", but do NOT have
> "BuildRequires: pkgconfig(bash-completion)"
>
> may be installing completion file into wrong directories after rebuild.
> (At least, I tried rebuilding cowsay and actually it installs completion file
> into the wrong
> directory).
I wonder why these packages rely in pkg-config and don't just install
to `%{bash_completions_dir}`?
This macro is defined in the default buildroot, regardless of
BuildRequires, and always expands to the correct location for
installing bash completions.
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
Fedora 40 compose report: 20240318.n.0 changes
OLD: Fedora-40-20240317.n.0 NEW: Fedora-40-20240318.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-40-20240317.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Follow up for bash-completion pkgconfig file packaging change
On Mon, 18 Mar 2024 17:07:08 +0100
Fabio Valentini wrote:
> On Mon, Mar 18, 2024 at 4:33 PM Mamoru TASAKA
> wrote:
> >
> > Hello, all:
> >
> > After investigating the recent Fedora-Security-Live livespin compose failure
> > on F-41, it is found that this is caused because:
> >
> > - Recently on F-41, bash-completion packaging changed so that pkgconfig file
> >is moved into -devel subpackage: (bash-completion-2.11-15.fc41)
> >
> > https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc68efdd519b78fccca416cad94?branch=rawhide
> >
> > - A package (lynis) installing bash-completion file into the directory
> >$(pkg-config --variable=completionsdir bash-completion), had
> > "BuildRequires: bash-completion",
> >but did not have "BuildRequires: pkgconfig(bash-completion)".
> >
> > - So after the above bash-completion side packaging change, the above
> > command line was
> >expanded to the empty string, so the completion file was installed into
> > the wrong directory,
> >which caused conflict with filesystem rpm.
> >
> >
> > So on F-41(rawhide), the packages
> >
> > * trying to install bash-completion file using $(pkg-config
> > --variable=completionsdir bash-completion)
> > * which have "BuildRequires: bash-completion", but do NOT have
> > "BuildRequires: pkgconfig(bash-completion)"
> >
> > may be installing completion file into wrong directories after rebuild.
> > (At least, I tried rebuilding cowsay and actually it installs completion
> > file into the wrong
> > directory).
>
> I wonder why these packages rely in pkg-config and don't just install
> to `%{bash_completions_dir}`?
because it hasn't always exist? Or it's mentioned in some guidelines?
Dan
> This macro is defined in the default buildroot, regardless of
> BuildRequires, and always expands to the correct location for
> installing bash completions.
>
> 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
--
___
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: Follow up for bash-completion pkgconfig file packaging change
Thanks, lynis is fixed, cowsay will be momentarily.
--
Gwyn Ciesla
she/her/hers
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with Proton Mail secure email.
On Monday, March 18th, 2024 at 10:33 AM, Mamoru TASAKA
wrote:
> Hello, all:
>
> After investigating the recent Fedora-Security-Live livespin compose failure
> on F-41, it is found that this is caused because:
>
> - Recently on F-41, bash-completion packaging changed so that pkgconfig file
> is moved into -devel subpackage: (bash-completion-2.11-15.fc41)
> https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc68efdd519b78fccca416cad94?branch=rawhide
>
> - A package (lynis) installing bash-completion file into the directory
> $(pkg-config --variable=completionsdir bash-completion), had "BuildRequires:
> bash-completion",
> but did not have "BuildRequires: pkgconfig(bash-completion)".
>
> - So after the above bash-completion side packaging change, the above command
> line was
> expanded to the empty string, so the completion file was installed into the
> wrong directory,
> which caused conflict with filesystem rpm.
>
>
> So on F-41(rawhide), the packages
>
> * trying to install bash-completion file using $(pkg-config
> --variable=completionsdir bash-completion)
> * which have "BuildRequires: bash-completion", but do NOT have
> "BuildRequires: pkgconfig(bash-completion)"
>
> may be installing completion file into wrong directories after rebuild.
> (At least, I tried rebuilding cowsay and actually it installs completion file
> into the wrong
> directory).
>
> The possible packages which may need fixing are:
>
> 1 cowsay/rawhide/cowsay.spec %global compdir %(pkg-config
> --variable=completionsdir bash-completion)
> 2 creds/rawhide/creds.spec %global bashcompdir %(pkg-config
> --variable=completionsdir bash-completion)
> 3 datamash/rawhide/datamash.spec pkg-config --variable=completionsdir
> bash-completion ||
> 4 dracut/rawhide/dracut.spec --bashcompletiondir=$(pkg-config
> --variable=completionsdir bash-completion) \
> 5 eg/rawhide/eg.spec bashcompdir=$(pkg-config --variable=completionsdir
> bash-completion || :)
> 6 fedpkg/rawhide/fedpkg.spec %define compdir %(pkg-config
> --variable=completionsdir bash-completion)
> 7 git-annex/rawhide/git-annex.spec
> bash_completion_dir=%{buildroot}$(pkg-config --variable=completionsdir
> bash-completion)
> 8 gromacs/rawhide/gromacs.spec %define compdir %(pkg-config
> --variable=completionsdir bash-completion)
> 9 kim-api/rawhide/kim-api.spec %global b_compdir %(pkg-config
> --variable=completionsdir bash-completion)
> 10 mpc/rawhide/mpc.spec %global compdir %(pkg-config
> --variable=completionsdir bash-completion)
> 11 mt-st/rawhide/mt-st.spec COMPLETIONDIR=%{buildroot}$(pkg-config
> --variable=completionsdir bash-completion)
> 12 pybugz/rawhide/pybugz.spec %global bash_cmpl_dir %(pkg-config
> --variable=completionsdir bash-completion)
> 13 python-django/rawhide/python-django.spec bashcompdir=$(pkg-config
> --variable=completionsdir bash-completion)
> 14 python-vitrageclient/rawhide/python-vitrageclient.spec
> bashcompdir=$(pkg-config --variable=completionsdir bash-completion)
> 15 tig/rawhide/tig.spec %global bash_completion_dir %(pkg-config
> --variable=completionsdir bash-completion || echo /etc/bash_completion.d)/
>
> Regards,
> Mamoru
> --
> ___
> 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
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: Follow up for bash-completion pkgconfig file packaging change
On Mon, Mar 18, 2024 at 5:22 PM Dan Horák wrote:
>
> On Mon, 18 Mar 2024 17:07:08 +0100
> Fabio Valentini wrote:
> > I wonder why these packages rely in pkg-config and don't just install
> > to `%{bash_completions_dir}`?
>
> because it hasn't always exist? Or it's mentioned in some guidelines?
Likely, yes. They've been around for ~2 years.
They are available on all current branches of Fedora and on EPEL 9.
The effort to document them in the packaging guidelines seems to have stalled:
https://pagure.io/packaging-committee/issue/1202
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: Fedora container images no longer include gzip?
Hi, On Sun, Mar 17, 2024, at 10:00 PM, Gary Buhrmaster wrote: > On Sun, Mar 17, 2024 at 11:55 PM Adam Williamson > wrote: >> >> On Sun, 2024-03-17 at 23:12 +, Gary Buhrmaster wrote: >> > >> > Did I miss an announcement (very possible), >> > or did something else change to no longer >> > pull in gzip (also possible)? >> >> Almost certainly. What changed is >> https://fedoraproject.org/wiki/Changes/KiwiBuiltCloudImages - these >> images (all 'Cloud' and 'Container' images) are now built with Kiwi >> instead of ImageFactory/oz. > > I had remembered that the builder was > changing, but, in hind sight, incorrectly > presumed that would not change what > packages ended up in the container. > >> This probably wasn't intentional, and we can probably get it put >> back... > > Thanks for looking into this. I did some diffing of f39 and f40 images and came up with https://pagure.io/fedora-kiwi-descriptions/pull-request/29 as a starting point. The other big package missing I noticed was sudo, but there were a few other things too. - Jeremy -- ___ 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: Follow up for bash-completion pkgconfig file packaging change
On 18. 03. 24 17:07, Fabio Valentini wrote:
I wonder why these packages rely in pkg-config and don't just install
to `%{bash_completions_dir}`?
Because they either predate the macro or the thing was copied from another
package that predates it.
--
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: Follow up for bash-completion pkgconfig file packaging change
On Mon, 18 Mar 2024 15:46:46 +
Gwyn Ciesla via devel wrote:
> Thanks, lynis is fixed, cowsay will be momentarily.
and mt-st is fixed as well
Dan
>
>
>
> --
> Gwyn Ciesla
> she/her/hers
>
> in your fear, seek only peace
> in your fear, seek only love
> -d. bowie
>
>
> Sent with Proton Mail secure email.
>
> On Monday, March 18th, 2024 at 10:33 AM, Mamoru TASAKA
> wrote:
>
> > Hello, all:
> >
>
> > After investigating the recent Fedora-Security-Live livespin compose failure
> > on F-41, it is found that this is caused because:
> >
>
> > - Recently on F-41, bash-completion packaging changed so that pkgconfig file
> > is moved into -devel subpackage: (bash-completion-2.11-15.fc41)
> > https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc68efdd519b78fccca416cad94?branch=rawhide
> >
>
> > - A package (lynis) installing bash-completion file into the directory
> > $(pkg-config --variable=completionsdir bash-completion), had
> > "BuildRequires: bash-completion",
> > but did not have "BuildRequires: pkgconfig(bash-completion)".
> >
>
> > - So after the above bash-completion side packaging change, the above
> > command line was
> > expanded to the empty string, so the completion file was installed into the
> > wrong directory,
> > which caused conflict with filesystem rpm.
> >
>
> >
>
> > So on F-41(rawhide), the packages
> >
>
> > * trying to install bash-completion file using $(pkg-config
> > --variable=completionsdir bash-completion)
> > * which have "BuildRequires: bash-completion", but do NOT have
> > "BuildRequires: pkgconfig(bash-completion)"
> >
>
> > may be installing completion file into wrong directories after rebuild.
> > (At least, I tried rebuilding cowsay and actually it installs completion
> > file into the wrong
> > directory).
> >
>
> > The possible packages which may need fixing are:
> >
>
> > 1 cowsay/rawhide/cowsay.spec %global compdir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 2 creds/rawhide/creds.spec %global bashcompdir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 3 datamash/rawhide/datamash.spec pkg-config --variable=completionsdir
> > bash-completion ||
> > 4 dracut/rawhide/dracut.spec --bashcompletiondir=$(pkg-config
> > --variable=completionsdir bash-completion) \
> > 5 eg/rawhide/eg.spec bashcompdir=$(pkg-config --variable=completionsdir
> > bash-completion || :)
> > 6 fedpkg/rawhide/fedpkg.spec %define compdir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 7 git-annex/rawhide/git-annex.spec
> > bash_completion_dir=%{buildroot}$(pkg-config --variable=completionsdir
> > bash-completion)
> > 8 gromacs/rawhide/gromacs.spec %define compdir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 9 kim-api/rawhide/kim-api.spec %global b_compdir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 10 mpc/rawhide/mpc.spec %global compdir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 11 mt-st/rawhide/mt-st.spec COMPLETIONDIR=%{buildroot}$(pkg-config
> > --variable=completionsdir bash-completion)
> > 12 pybugz/rawhide/pybugz.spec %global bash_cmpl_dir %(pkg-config
> > --variable=completionsdir bash-completion)
> > 13 python-django/rawhide/python-django.spec bashcompdir=$(pkg-config
> > --variable=completionsdir bash-completion)
> > 14 python-vitrageclient/rawhide/python-vitrageclient.spec
> > bashcompdir=$(pkg-config --variable=completionsdir bash-completion)
> > 15 tig/rawhide/tig.spec %global bash_completion_dir %(pkg-config
> > --variable=completionsdir bash-completion || echo /etc/bash_completion.d)/
> >
>
> > Regards,
> > Mamoru
> > --
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Summary/Minutes from today's Fedora Flatpak Packaging SIG Meeting (2024-03-18)
Text Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-03-18/flatpak-sig.2024-03-18-15.30.log.txt HTML Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-03-18/flatpak-sig.2024-03-18-15.30.log.html Text Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-03-18/flatpak-sig.2024-03-18-15.30.txt HTML Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-03-18/flatpak-sig.2024-03-18-15.30.html = # #meeting-1:fedoraproject.org: flatpak-sig = Meeting started by @kalev:fedora.im at 2024-03-18 15:30:41 Meeting summary --- * TOPIC: Init process (@kalev:fedora.im, 15:31:00) * TOPIC: Pushing last F38 flatpak runtime update (@kalev:fedora.im, 15:42:52) * INFO: All flatpaks are now updated to the F39 runtime and the new build infra, and all that remains is EOL'ing the F38 runtime (@kalev:fedora.im, 15:51:11) * TOPIC: Meeting time (@kalev:fedora.im, 16:04:46) * INFO: ~210 flatpaks currently in testing (@yselkowitz:fedora.im, 16:13:20) * LINK: https://bodhi.fedoraproject.org/updates/?search==testing=F39F (@yselkowitz:fedora.im, 16:13:24) * TOPIC: speech-dispatcher in flatpaks (https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/28) (@kalev:fedora.im, 16:15:51) * ACTION: yselkowitz to file PR to split out speech-dispatcher-libs (@yselkowitz:fedora.im, 16:18:01) * TOPIC: flatpak-module-tools PR for building extensions (https://pagure.io/flatpak-module-tools/pull-request/41) (@kalev:fedora.im, 16:19:08) * TOPIC: kicking off F40 flatpaks (@kalev:fedora.im, 16:26:15) * TOPIC: Open Floor (@kalev:fedora.im, 16:36:36) Meeting ended at 2024-03-18 16:40:30 Action items * yselkowitz to file PR to split out speech-dispatcher-libs People Present (lines said) --- * @kalev:fedora.im (65) * @yselkowitz:fedora.im (39) * @otaylor:fedora.im (13) * @nirik:matrix.scrye.com (11) * @meetbot:fedora.im (2) * @zodbot:fedora.im (1) -- ___ 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: Follow up for bash-completion pkgconfig file packaging change
On Tue, Mar 19, 2024 at 12:33:02AM +0900, Mamoru TASAKA wrote:
> 8gromacs/rawhide/gromacs.spec%define compdir %(pkg-config
> --variable=completionsdir bash-completion)
I changed gromacs to use %{bash_completions_dir} now.
Zbyszek
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Heads-up: updating flatbuffers to 24.3.7 in F41/Rawhide
In one week (2024-03-25), or slightly later, I plan to update the flatbuffers package to 24.3.7 in F41/Rawhide[1]. As usual, this includes an SONAME version bump. Upstream follows calendar versioning and does not attempt to keep the ABI stable across releases. Unless a maintainer asks me to do otherwise, I will use provenpackager privileges to rebuild the dependent packages in a side tag: - hyperhdr - onnxruntime - qdigidoc All of these rebuilt successfully in a COPR impact check[2]. I will *not* build this version for F40/Branched (even though there is time before the Final Freeze), because python-torch in F40 depends on an exact version of flatbuffers. This could be fixed by running flatc as part of the python-torch build, but an unrelated FTBFS would have to be fixed first. In F41, python-torch bundles the same version of flatbuffers that upstream used to pre-generate the flatbuffers bindings, and it does not depend on the system flatbuffers package. [1] https://src.fedoraproject.org/rpms/flatbuffers/pull-request/8 [2] https://copr.fedorainfracloud.org/coprs/music/flatbuffers/packages/ -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Join the Rawhide Test Days: Help Shape the Future of Fedora Linux!
Gonna help with this today Den tors 14 mars 2024 kl 05:35 skrev Sumantro Mukherjee : > > Dear Fedorans, > > Are you ready to make a difference in the world of Fedora Linux? We're > thrilled to announce the launch of our brand new test day series: > Rawhide Test Days! These events are your opportunity to play a crucial > role in ensuring the quality and reliability of upcoming Fedora > releases. Rawhide test days will play their unique role in keeping > Fedora Linux releases on time. > > Fedora test days are renowned for their inclusivity – they welcome > participation from both seasoned Fedora contributors and newcomers > alike. If you've been itching to dip your toes into the world of > Fedora Linux contribution, this is your perfect starting point. > > For some time now, we've been dedicated to elevating the quality > standards of Fedora by implementing rigorous testing processes well in > advance. Our Fedora Changes process facilitates the submission of > changesets long before the official release cycle begins. As part of > this effort, we're excited to introduce Rawhide Test Days, an > initiative designed to test these changesets thoroughly and identify > any potential (blocker) bugs early on. > > To kick off this exciting journey, we're focusing our efforts on > testing DNF 5 – a crucial changeset proposed for Fedora Linux 41[0]. > With the introduction of the brand new DNF5 package in Rawhide, we're > organizing a test days to gather initial feedback before it becomes > the default. We'll be rigorously testing DNF5 against its basic > acceptance criteria to ensure a seamless transition. > > Mark your calendars for our Rawhide Test Days, taking place from > Friday, March 15th, through Tuesday, March 19th. Your participation > during this week will be invaluable as we work together to refine > Fedora Linux for its upcoming release. > > Ready to dive in? Visit our test week page [1] to learn more about how > you can contribute and make your mark on the future of Fedora. > > Happy testing, and we can't wait to see you there! > > Best regards, > //sumantro > > [0] https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5 > [1] http://fedoraproject.org/wiki/Test_Day:2024-03-15_Fedora_40_DNF_5 > > > > -- > //sumantro > Fedora QE > TRIED AND PERSONALLY TESTED, ERGO TRUSTED > -- > ___ > users mailing list -- us...@lists.fedoraproject.org > To unsubscribe send an email to users-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/us...@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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Mon, 2024-03-18 at 16:17 -0400, Garry T. Williams wrote: > On Wednesday, February 7, 2024 4:06:46 AM EDT Kevin Kofler via devel > wrote: > > Garry T. Williams wrote: > > > I hope my report can be resolved before I am forced to use > > > Wayland. > > > > You will not be forced to use Wayland. Stay tuned. > > In an effort to test a Wayland bug I reported upstream, I upgraded my > laptop to f40. (I am holding off on upgrading my workstation.) My > reported bug is still there, but here I am without x11. I installed > kwin-x11. My login screen no longer offers to run it instead of > kwin-wayland. Is there a way to run x11 on f40? (There are still > several annoying bugs in Wayland that I would like to avoid.) > "kwin-wayland replaces kwin-x11 , on upgrade" → When upgrading to Fedora 40 you may reinstall the package, it will not be obsoleted anymore. I don't agree with this behavior -- 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
Re: Heads-up: Updating libunibreak to 6.1 in rawhide and F40
On 10-03-2024 18:10, Sandro wrote: On 03-03-2024 21:42, Sandro wrote: I plan to update libunibreak to version 6.1 in rawhide and F40 in about a week. This update comes with an soname bump. The following packages depend on libunibreak: fedrq wrsrc -Xs libunibreak -F name coolreader fbreader krita naev I ran a smoke test in Copr [1] rebuilding those packages against libunibreak-6.1 and all packages built successfully. I added the maintainers in Bcc. Please use the following side tags for rebuilding your package against the updated libunibreak: rawhide: f41-build-side-85041 f40: f40-build-side-85045 [1] https://copr.fedorainfracloud.org/coprs/gui1ty/libunibreak_6/builds/ I will be moving forward with submitting the update to rawhide even though none of the dependent packages have been rebuilt in aforementioned side tags. I can wait a little longer with the F40 update, but I still think it's worth updating the package in F40 as well. Let me know if you think otherwise. Updates for F40 have been pushed now as well. Only fbreader was not rebuilt against updated `libunibreak`. -- 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: openclonk: undefined reference to `zmemcpy'
"Martin Gansser" writes: > Hi, > > when compiling openclonk [1] on rawhide it fails with this error message [2]: > /usr/bin/cmake -E cmake_link_script CMakeFiles/c4group.dir/link.txt > --verbose=1 > /usr/bin/g++ -O2 -flto=auto -ffat-lto-objects -fexceptions -g > -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang > -Wno-error=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 > -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 > -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 > -march=x86-64 -mtune=generic -fasynchronous-unwind-tables > -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -Wall -Wextra -Wredundant-decls -Wendif-labels > -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Winit-self > -Wsign-promo -Wno-reorder -Wno-unused-parameter -Wnon-virtual-dtor > -Woverloaded-virtual -Wformat-security -Werror=delete-incomplete -DNDEBUG > -flto=auto -fno-fat-lto-objects -Wl,-z,relro -Wl,--as-needed > -Wl,-z,pack-relative-relocs -Wl,-z,now > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -W > l,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes > CMakeFiles/c4group.dir/c4group_autogen/mocs_compilation.cpp.o > CMakeFiles/c4group.dir/src/c4group/C4GroupMain.cpp.o -o c4group liblibmisc.a > /usr/lib64/libz.so -lpthread -lrt > make[2]: Leaving directory > '/builddir/build/BUILD/openclonk-701bcf38c9f3c4877e1b4a8651b9ce922b15969e/build' > /usr/bin/ld: /tmp/ccgvFyfu.ltrans1.ltrans.o: in function `c4_gzread': > /builddir/build/BUILD/openclonk-701bcf38c9f3c4877e1b4a8651b9ce922b15969e/src/zlib/gzio.c:450:(.text+0x3fd0): > undefined reference to `zmemcpy' > collect2: error: ld returned 1 exit status > > How can this be fixed ?? The fastest way to work around this issue is by defining HAVE_MEMCPY when building gzio.c. You probably want to guarantee that other C macros are defined as well, e.g. STDC. In the long term, I suggest to work with upstream in order to stop using zutil.h. This is a zlib internal header that provides internal types and functions and is strongly dependent on how zlib was built. I also suggest to stop distributing their own gz* functions and reuse the functions provided by the OS. This will guarantee that openclonk will receive the latest fixes to that code. -- Tulio Magno -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Wednesday, February 7, 2024 4:06:46 AM EDT Kevin Kofler via devel wrote: > Garry T. Williams wrote: > > I hope my report can be resolved before I am forced to use Wayland. > > You will not be forced to use Wayland. Stay tuned. In an effort to test a Wayland bug I reported upstream, I upgraded my laptop to f40. (I am holding off on upgrading my workstation.) My reported bug is still there, but here I am without x11. I installed kwin-x11. My login screen no longer offers to run it instead of kwin-wayland. Is there a way to run x11 on f40? (There are still several annoying bugs in Wayland that I would like to avoid.) -- Garry T. Williams -- ___ 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: Join the Rawhide Test Days: Help Shape the Future of Fedora Linux!
and done with some testing and translations for dnf5 and dnf4 Den tis 19 mars 2024 kl 03:45 skrev Luna Jernberg : > > Gonna help with this today > > Den tors 14 mars 2024 kl 05:35 skrev Sumantro Mukherjee : > > > > Dear Fedorans, > > > > Are you ready to make a difference in the world of Fedora Linux? We're > > thrilled to announce the launch of our brand new test day series: > > Rawhide Test Days! These events are your opportunity to play a crucial > > role in ensuring the quality and reliability of upcoming Fedora > > releases. Rawhide test days will play their unique role in keeping > > Fedora Linux releases on time. > > > > Fedora test days are renowned for their inclusivity – they welcome > > participation from both seasoned Fedora contributors and newcomers > > alike. If you've been itching to dip your toes into the world of > > Fedora Linux contribution, this is your perfect starting point. > > > > For some time now, we've been dedicated to elevating the quality > > standards of Fedora by implementing rigorous testing processes well in > > advance. Our Fedora Changes process facilitates the submission of > > changesets long before the official release cycle begins. As part of > > this effort, we're excited to introduce Rawhide Test Days, an > > initiative designed to test these changesets thoroughly and identify > > any potential (blocker) bugs early on. > > > > To kick off this exciting journey, we're focusing our efforts on > > testing DNF 5 – a crucial changeset proposed for Fedora Linux 41[0]. > > With the introduction of the brand new DNF5 package in Rawhide, we're > > organizing a test days to gather initial feedback before it becomes > > the default. We'll be rigorously testing DNF5 against its basic > > acceptance criteria to ensure a seamless transition. > > > > Mark your calendars for our Rawhide Test Days, taking place from > > Friday, March 15th, through Tuesday, March 19th. Your participation > > during this week will be invaluable as we work together to refine > > Fedora Linux for its upcoming release. > > > > Ready to dive in? Visit our test week page [1] to learn more about how > > you can contribute and make your mark on the future of Fedora. > > > > Happy testing, and we can't wait to see you there! > > > > Best regards, > > //sumantro > > > > [0] https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5 > > [1] http://fedoraproject.org/wiki/Test_Day:2024-03-15_Fedora_40_DNF_5 > > > > > > > > -- > > //sumantro > > Fedora QE > > TRIED AND PERSONALLY TESTED, ERGO TRUSTED > > -- > > ___ > > users mailing list -- us...@lists.fedoraproject.org > > To unsubscribe send an email to users-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/us...@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
[Test-Announce] Fedora 40 Candidate Beta-1.8 Available Now!
According to [the schedule][1], Fedora 40 Candidate Beta-1.8 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/40 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Base https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Server https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.8_Security_Lab All Beta priority test cases for each of these [test pages][2] must pass in order to meet the [Beta Release Criteria][3]. Help is available on [the Fedora Quality chat channel][4], [the Fedora Quality tag on Discourse][5], or on [the test list][6]. Current Blocker and Freeze Exception bugs: https://qa.fedoraproject.org/blockerbugs/current [1]: https://fedorapeople.org/groups/schedule/f-40/f-40-quality-tasks.html [2]: https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3]: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria [4]: https://matrix.to/#/#quality:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org [5]: https://discussion.fedoraproject.org/tags/c/project/7/quality-team [6]: https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/ -- ___ 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
[Bug 2269439] perl-HTML-Parser-3.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269439 --- Comment #2 from Fedora Update System --- FEDORA-2024-f9685bc9ea (perl-HTML-Parser-3.82-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f9685bc9ea -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2269439 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269439%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 2270079] New: perl-CGI-4.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270079 Bug ID: 2270079 Summary: perl-CGI-4.64 is available Product: Fedora Version: rawhide Status: NEW Component: perl-CGI Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mmasl...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 4.64 Upstream release that is considered latest: 4.64 Current version/release in rawhide: 4.63-1.fc41 URL: https://metacpan.org/dist/CGI/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/2687/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-CGI -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270079 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270079%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 2269439] perl-HTML-Parser-3.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269439 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-HTML-Parser-3.82-1.fc4 ||1 Resolution|--- |ERRATA Status|MODIFIED|CLOSED Last Closed||2024-03-18 13:08:17 --- Comment #4 from Fedora Update System --- FEDORA-2024-0f72d07e76 (perl-HTML-Parser-3.82-1.fc41) has been pushed to the Fedora 41 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=2269439 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269439%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 2270060] CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270060 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2024-03-18 12:11:45 --- Comment #2 from Paul Howarth --- This issue is fixed in version 0.22, which is the version available in all Fedora releases since April 2021. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270060 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270060%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 2270059] CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270059 --- Comment #1 from TEJ RATHI --- Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. = # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2270058,2270059 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False == Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270059 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270059%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 2270060] New: CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270060 Bug ID: 2270060 Summary: CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [fedora-all] Product: Fedora Version: 39 Status: NEW Component: perl-Net-CIDR-Lite Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: p...@city-fan.org Reporter: tra...@redhat.com QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org, st...@silug.org Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2270058 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270060 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270060%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 2270060] CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270060 TEJ RATHI changed: What|Removed |Added Blocks||2270058 (CVE-2021-47154) Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2270058 [Bug 2270058] CVE-2021-47154 Perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270060 -- ___ 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 2270059] CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270059 TEJ RATHI changed: What|Removed |Added Blocks||2270058 (CVE-2021-47154) Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2270058 [Bug 2270058] CVE-2021-47154 Perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270059 -- ___ 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 2270060] CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270060 --- Comment #1 from TEJ RATHI --- Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. = # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2270058,2270060 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False == Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270060 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270060%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 2270059] New: CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270059 Bug ID: 2270059 Summary: CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [epel-all] Product: Fedora EPEL Version: epel8 Status: NEW Component: perl-Net-CIDR-Lite Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: p...@city-fan.org Reporter: tra...@redhat.com QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org, st...@silug.org Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2270058 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270059 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270059%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 2270059] CVE-2021-47154 perl-Net-CIDR-Lite: improper handling of extraneous zero characters in an IP address string [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270059 Paul Howarth changed: What|Removed |Added Resolution|--- |CURRENTRELEASE Status|NEW |CLOSED Last Closed||2024-03-18 12:10:43 --- Comment #2 from Paul Howarth --- This issue is fixed in version 0.22, which is the version available in all applicable EPEL releases since April 2021. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270059 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270059%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 2269439] perl-HTML-Parser-3.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269439 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-0f72d07e76 (perl-HTML-Parser-3.82-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0f72d07e76 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2269439 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269439%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 2269706] perl-PAR-Packer-1.063 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269706 Jitka Plesnikova changed: What|Removed |Added CC|anon.am...@gmail.com, | |jples...@redhat.com,| |mmasl...@redhat.com | Status|NEW |ASSIGNED Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2269706 -- ___ 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 2269706] perl-PAR-Packer-1.063 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269706 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-d20352fe74 (perl-PAR-Packer-1.063-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-d20352fe74 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2269706 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269706%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 2270079] perl-CGI-4.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270079 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2024-b669c30bfb (perl-CGI-4.64-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b669c30bfb -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270079 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270079%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
[rpms/perl-Tk] PR #2: Package tests
jplesnik merged a pull-request against the project: `perl-Tk` that you are following. Merged pull-request: `` Package tests `` https://src.fedoraproject.org/rpms/perl-Tk/pull-request/2 -- ___ 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 2270079] perl-CGI-4.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270079 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In Version||perl-CGI-4.64-1.fc41 Status|MODIFIED|CLOSED Last Closed||2024-03-18 16:05:17 --- Comment #3 from Fedora Update System --- FEDORA-2024-b669c30bfb (perl-CGI-4.64-1.fc41) has been pushed to the Fedora 41 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=2270079 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270079%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
[Bug 2269706] perl-PAR-Packer-1.063 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269706 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-PAR-Packer-1.063-1.fc4 ||1 Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2024-03-18 14:29:18 --- Comment #2 from Fedora Update System --- FEDORA-2024-d20352fe74 (perl-PAR-Packer-1.063-1.fc41) has been pushed to the Fedora 41 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=2269706 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269706%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 2270079] perl-CGI-4.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270079 --- Comment #2 from Fedora Update System --- FEDORA-2024-535c7c3d84 (perl-CGI-4.64-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-535c7c3d84 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270079 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270079%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 2270204] New: perl-Variable-Magic-0.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270204 Bug ID: 2270204 Summary: perl-Variable-Magic-0.64 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Variable-Magic Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 0.64 Upstream release that is considered latest: 0.64 Current version/release in rawhide: 0.63-6.fc40 URL: http://search.cpan.org/dist/Variable-Magic/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/7674/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Variable-Magic -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2270204 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270204%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 2270079] perl-CGI-4.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270079 --- Comment #4 from Fedora Update System --- FEDORA-2024-535c7c3d84 has been pushed to the Fedora 40 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-535c7c3d84` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-535c7c3d84 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=2270079 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270079%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 2269439] perl-HTML-Parser-3.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269439 --- Comment #5 from Fedora Update System --- FEDORA-2024-1663894056 has been pushed to the Fedora 40 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-1663894056` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1663894056 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=2269439 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269439%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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d241ea2238 libuev-2.4.1-1.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d7cc38dee9 apptainer-1.3.0-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d521530f6a amavis-2.13.1-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ac18018db8 tcpreplay-4.4.4-5.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing copr-rpmbuild-0.72-1.el8 libgit2_1.7-1.7.2-1.el8 lynis-3.1.1-1.el8 openelp-0.9.3-1.el8 python-copr-common-0.23-1.el8 python-specfile-0.28.0-1.el8 python3.11-pygit2-1.14.0-1.el8 radicale-3.1.9-1.el8 resalloc-5.4-1.el8 w3m-0.5.3-63.git20230121.el8 Details about builds: copr-rpmbuild-0.72-1.el8 (FEDORA-EPEL-2024-50faa01ddb) Run COPR build tasks Update Information: don't clean after builds with user ssh access ChangeLog: * Sat Mar 16 2024 Pavel Raiskup 0.72-1 - don't clean after builds with user ssh access * Fri Mar 1 2024 Pavel Raiskup 0.71-1 - don't set bootstrap_image_ready for rawhide - no Jinja-vars in config_opts keys (mock-core-configs 40.2 compat) - allow user SSH to builders - fix copr-rpmbuild --dump-configs - install copr-distgit-client with copr-rpmbuild libgit2_1.7-1.7.2-1.el8 (FEDORA-EPEL-2024-6395ae2eec) C implementation of the Git core methods as a library with a solid API Update Information: This update introduces a compatibility package for libgit2 version 1.7.x. ChangeLog: * Mon Mar 18 2024 Nils Philippsen - 1.7.2-1 - Import package lynis-3.1.1-1.el8 (FEDORA-EPEL-2024-7a4a8669a9) Security and system auditing tool Update Information: 3.1.1, fix bash-completion issue. 3.1.0 ChangeLog: * Mon Mar 18 2024 Gwyn Ciesla - 3.1.1-1 - 3.1.1 * Tue Mar 12 2024 Gwyn Ciesla - 3.1.0-1 - 3.1.0 * Thu Jan 25 2024 Fedora Release Engineering - 3.0.9-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Sun Jan 21 2024 Fedora Release Engineering - 3.0.9-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Tue Dec 19 2023 Gwyn Ciesla - 3.0.9-5 - Additional egrep patch * Wed Dec 6 2023 Gwyn Ciesla - 3.0.9-4 - pgrep patch * Tue Sep 19 2023 Gwyn Ciesla - 3.0.9-3 - Additional egrep patch * Mon Aug 7 2023 Gwyn Ciesla - 3.0.9-2 - Upstream patch to remove egrep usage References: [ 1 ] Bug #2268997 - lynis-3.1.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=2268997 [ 2 ] Bug #2270013 - File conflict with filesystem https://bugzilla.redhat.com/show_bug.cgi?id=2270013 [ 3 ] Bug #2270108 - lynis-3.1.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=2270108 openelp-0.9.3-1.el8 (FEDORA-EPEL-2024-6d66e8a036) Open Source EchoLink Proxy Update Information: Update to OpenELP 0.9.3 ChangeLog: * Sun Mar 17 2024 Scott K Logan - 0.9.3-1 - Update to 0.9.3 python-copr-common-0.23-1.el8 (FEDORA-EPEL-2024-09ce04b70a) Python code used by Copr Update Information: New resalloc upstream release https://github.com/praiskup/resalloc/releases/tag/v5.4 ChangeLog: * Fri Mar 15 2024 Pavel Raiskup 0.23-1 - make get_redis_connection to accept dict-like 'opts' argument
[Bug 2269439] perl-HTML-Parser-3.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2269439 --- Comment #6 from Fedora Update System --- FEDORA-2024-f9685bc9ea 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-f9685bc9ea` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f9685bc9ea 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=2269439 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202269439%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
[Bug 2267346] Please branch and build perl-Fuse for EPEL9
https://bugzilla.redhat.com/show_bug.cgi?id=2267346 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2024-b9c3804d4d (perl-Fuse-0.16.1-27.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b9c3804d4d -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2267346 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202267346%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
