[Bug 2168377] perl-Compress-Raw-Zlib-2.204 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168377

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168377
___
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 2168376] perl-Compress-Raw-Bzip2-2.204 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168376

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168376
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Tenacity

[Brandon Nielsen via devel]

On 2/8/23 9:30 PM, Reon Beon via devel wrote:

wxGTK should have that...


It should, and they fixed it, but the fix never made it to the 3.1.X 
series as far as I can tell. 3.2.1 in F37 at least builds, but for some 
reason liblibnyquist.so is missing. F38 / Rawhide has some lisp issue 
with the libnyquist stuff.

___
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

Request exemption for f38-backgrounds

[Luya Tshimbalanga]

Hello team,

I filed an exemption[1] for f38-backgrounds packaging review[2] as 
suggestion from desktop team on discussion last year. The spec file 
remains virtually unchanged other than an updated default wallpaper.


Thamks.

Ref:

[1] https://pagure.io/releng/fedora-scm-requests/issue/51051

[2] https://bugzilla.redhat.com/show_bug.cgi?id=2168288

--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
___
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: Tenacity

[Reon Beon via devel]

wxGTK should have that...
___
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: List of long term FTBFS packages to be retired next week

[Arun SAG]

On Tue, 31 Jan 2023 at 18:14, Miro Hrončok  wrote:
>
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.
>
> 5 weekly reminders are required, hence the retirement will happen
> approximately in 1 week, i.e. around 2023-02-08.
> Since this is unfortunately after the branching,
> packages will be retired on rawhide and f38.
>

> If you see a package that can be rebuilt, please do so.
>
>  Package(co)maintainers
> ==
> ArpON   fab, sagarun


There has been no activity on this package since 2016. This package
should be retired.

-- 
Arun S A G
http://zer0c00l.in/
___
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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Demi Marie Obenour]

On 2/7/23 07:52, Peter Robinson wrote:
> On Tue, Feb 7, 2023 at 12:36 PM Lokesh Mandvekar  
> wrote:
>>
>> On Tue, Feb 7, 2023 at 5:56 PM Peter Robinson  wrote:
>>
>>> There are still active users of Fedora IoT 36 on armhfp using
>>> containers so I suspect they may be unhappy of they go away before the
>>> F-36 EOL in the late May/early June timeframe.
>>
>> I see. I guess we could leave armhfp be until then. Btw, just curious
>> what happens to IoT on armhfp once f36 goes EOL.
>> Would users have to pick something else?
> 
> Basically yes.

Not sure if Debian supports armhfp, but in the long term the answer is
going to be to find a distro that cross-compiles everything.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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: Retiring Bottles in favor of Flatpak provided by upstream

[Demi Marie Obenour]

On 2/8/23 08:41, Kevin Kofler via devel wrote:
> (*) I know this term ("lowest common denominator") is mathematically 
> nonsense. There is only a least/lowest common multiple and a greatest common 
> denominator in mathematics. :-)

I mean there *is* a lowest common denominator: 1 :)
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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: Tenacity

[Brandon Nielsen via devel]

On 2/8/23 10:59 AM, Jason L Tibbitts III wrote:

stan via devel  writes:



As they say in the BUILDING.md file,
though, fedora lacks wxWidgets 3.1.5 or greater. That stops the
configuration, cmake -G Ninja -S . -B build when it errors out.


That's odd; as far as I can see, F36 has 3.1.5 and F37 has 3.2.1.

  - J<


Both versions make it through the configure step for me, but a build 
with 3.1.5 will ultimately fail with "fatal error: 
wx/filedlgcustomize.h: No such file or directory", (upstream issue 
22516[0]).


[0] - https://github.com/wxWidgets/wxWidgets/issues/22516
___
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 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2023-526d25e3d7 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-526d25e3d7


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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 2168408] New: perl-IO-Compress-2.204 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168408

Bug ID: 2168408
   Summary: perl-IO-Compress-2.204 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-IO-Compress
  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, p...@city-fan.org,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.204
Upstream release that is considered latest: 2.204
Current version/release in rawhide: 2.201-4.fc38
URL: http://search.cpan.org/dist/IO-Compress/

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/2990/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-IO-Compress


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168408
___
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] Re: Proposing incompatible upgrade for libkdumpfile (0.4.1 -> 0.5.1)

[Troy Dawson]

On Wed, Feb 8, 2023 at 1:19 PM Michel Alexandre Salim <
sali...@fedoraproject.org> wrote:

> On Wed, 2023-02-08 at 14:09 -0500, Neal Gompa wrote:
> > On Wed, Feb 8, 2023 at 12:37 PM Troy Dawson 
> > wrote:
> > >
> > > On Wed, Feb 8, 2023 at 9:21 AM Michel Alexandre Salim
> > >  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Per the incompatible upgrade policy[1] I'm proposing upgrading
> > > > libkdumpfile from 0.4.1 to the latest 0.5.1 in both EPEL 8 and 9.
> > > >
> > > > Bugzilla issues:
> > > > - https://bugzilla.redhat.com/show_bug.cgi?id=2162866 (for 0.5.1
> > > > in
> > > > general)
> > > > - https://bugzilla.redhat.com/show_bug.cgi?id=2168301 (for EPEL)
> > > >
> > > > Up to 0.4.1, libkdumpfile was packaged without the test suite
> > > > being
> > > > run, and when I started work on packaging it in Debian I noticed
> > > > a lot
> > > > of test failures on non-x86_64 architectures:
> > > > https://github.com/ptesarik/libkdumpfile/issues/40
> > > >
> > > > This is now fixed (0.5.0 is the first version to pass tests
> > > > cleanly
> > > > without additional patches on Fedora), but prior to its release
> > > > we were
> > > > basically building in Fedora from a post-0.4.1 snapshot
> > > > (
> > > > https://src.fedoraproject.org/rpms/libkdumpfile/blob/8b3b02e83af83
> > > > 26562a155581d77f04f2ae84197/f/libkdumpfile.spec)
> > > > that is likely not ABI compatible with the original 0.4.1 anyway,
> > > > so
> > > > there's no reasonable way to backport the architecture fixes to
> > > > 0.4.1.
> > > >
> > > > Change in sonames:
> > > >
> > > > [michel@f37-packaging ~]$ comm <(rpmdistro-repoquery fedora
> > > > rawhide --
> > > > provides libkdumpfile 2>/dev/null) <(rpmdistro-repoquery centos-
> > > > stream
> > > > 9 --provides libkdumpfile 2>/dev/null)
> > > > libaddrxlat.so.2()(64bit)
> > > > libaddrxlat.so.2(LIBADDRXLAT_0)(64bit)
> > > > libaddrxlat.so.3
> > > > libaddrxlat.so.3()(64bit)
> > > > libaddrxlat.so.3(LIBADDRXLAT_0)
> > > > libaddrxlat.so.3(LIBADDRXLAT_0)(64bit)
> > > > libkdumpfile = 0.4.1-5.el9
> > > > libkdumpfile = 0.5.0-3.fc38
> > > > libkdumpfile(x86-32) = 0.5.0-3.fc38
> > > > libkdumpfile(x86-64) = 0.4.1-5.el9
> > > > libkdumpfile(x86-64) = 0.5.0-3.fc38
> > > > libkdumpfile.so.10
> > > > libkdumpfile.so.10()(64bit)
> > > > libkdumpfile.so.10(LIBKDUMPFILE_0)
> > > > libkdumpfile.so.10(LIBKDUMPFILE_0)(64bit)
> > > > libkdumpfile.so.9()(64bit)
> > > > libkdumpfile.so.9(LIBKDUMPFILE_0)(64bit)
> > > >
> > > > Only drgn currently depends on libkdumpfile, and I plan to
> > > > rebuild it
> > > > in the same updates:
> > > >
> > > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
> > > > whatrequires "libaddrxlat.so.2()(64bit)"
> > > > Last metadata expiration check: 0:12:30 ago on Wed Feb  8
> > > > 11:02:35
> > > > 2023.
> > > > libkdumpfile-devel-0:0.4.1-5.el9.x86_64
> > > > libkdumpfile-util-0:0.4.1-5.el9.x86_64
> > > > python3-libkdumpfile-0:0.4.1-5.el9.x86_64
> > > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
> > > > whatrequires "libkdumpfile.so.9()(64bit)"
> > > > Last metadata expiration check: 0:12:40 ago on Wed Feb  8
> > > > 11:02:35
> > > > 2023.
> > > > drgn-0:0.0.22-1.el9.x86_64
> > > > libkdumpfile-devel-0:0.4.1-5.el9.x86_64
> > > > libkdumpfile-util-0:0.4.1-5.el9.x86_64
> > > > python3-libkdumpfile-0:0.4.1-5.el9.x86_64
> > > >
> > > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-
> > > > legacy 8 --
> > > > whatrequires "libaddrxlat.so.2()(64bit)"
> > > > Last metadata expiration check: 0:00:08 ago on Wed Feb  8
> > > > 11:15:35
> > > > 2023.
> > > > libkdumpfile-devel-0:0.4.1-5.el8.x86_64
> > > > libkdumpfile-util-0:0.4.1-5.el8.x86_64
> > > > python3-libkdumpfile-0:0.4.1-5.el8.x86_64
> > > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-
> > > > legacy 8 --
> > > > whatrequires "libkdumpfile.so.9()(64bit)"
> > > > Last metadata expiration check: 0:00:16 ago on Wed Feb  8
> > > > 11:15:35
> > > > 2023.
> > > > drgn-0:0.0.22-1.el8.x86_64
> > > > libkdumpfile-devel-0:0.4.1-5.el8.x86_64
> > > > libkdumpfile-util-0:0.4.1-5.el8.x86_64
> > > > python3-libkdumpfile-0:0.4.1-5.el8.x86_64
> > > >
> > > > [1]:
> > > >
> https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
> > > >
> > > > Thanks,
> > >
> > >
> > > If I am reading this correctly, the only package affected would be
> > > drgn (from python-drgn).
> > > It should hopefully just need a rebuild.
> > > Is that correct?
> > > Were you planning on rebuilding python-drgn, or contacting the
> > > package maintainer and having them do it?
> > >
> >
> > He's a co-maintainer of python-drgn, so I assume he's going to
> > rebuild it himself.
> >
> Correct to both. Only drgn is affected, and Davide and I maintain it so
> we'll get it rebuilt as a set.
>
> Thanks,
>

Sounds good.
Thank you for announcing it and following the steps.
___
epel-devel mailing 

[Bug 2168401] perl-Dancer-1.3521 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168401



--- Comment #1 from Upstream Release Monitoring 
 ---
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs',
'/var/tmp/thn-7hl2whv9/perl-Dancer.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./Dancer-1.3521.tar.gz: No such file or directory


Traceback:
  File
"/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py",
line 56, in build
result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line
188, in build
raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report
it on the-new-hotness issue tracker:
https://github.com/fedora-infra/the-new-hotness/issues


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168401
___
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 2168401] New: perl-Dancer-1.3521 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168401

Bug ID: 2168401
   Summary: perl-Dancer-1.3521 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Dancer
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.3521
Upstream release that is considered latest: 1.3521
Current version/release in rawhide: 1.3520-2.fc38
URL: https://metacpan.org/release/Dancer

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/2756/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Dancer


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168401
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: MuseScore 4.0

[Jerry James]

I'm finally circling back around to MuseScore 4.0.  The COPR
(https://copr.fedorainfracloud.org/coprs/jjames/MuseScore4/) has been
updated with a new build, of version 4.0.1.

On Mon, Dec 19, 2022 at 4:11 PM Iñaki Ucar  wrote:
> I managed to download the Muse Sounds, and they work. Only the basic
> sounds are broken. It seems that they are not loaded. Just in case
> this rings any bell.

There was a snafu with a symlink to the soundfont.  It should be fixed now.

> Other differences I found with respect to the AppImage: the splash
> screen doesn't show up in the Copr version, and the "Learn" materials
> in the Home tab do not load.

MuseScore sets the translucent background property on the splash
screen, which works fine for the AppImage version.  For the COPR
build, though, that results in the splash screen being fully
transparent.  It is drawn, you just can't see it.  I removed that
property, and now the splash screen shows up ... except it is
displayed for a very small fraction of a second, so you'll miss it if
you blink.  If you step through in a debugger, you can pause and bask
in the glory of the splash screen.  I don't know why the AppImage
version doesn't have either the transparency or the extremely short
display time issues.

The "Learn" materials are accessed via the YouTube API, which means
you need a YouTube API key.  The MuseScore developers have such a key,
which they bake into their AppImage.  I have no such key, so attempts
to use the YouTube API fail.  Suggestions on how to handle this are
welcome.

I have fixed a few other issues that weren't reported by early
testers.  See comments above the patches in the spec file for more
information.  I will submit several of those upstream shortly (those
that are not Fedora-specific).

Remaining issues to address:
- Get back to the makemusic-finale-fonts package review
- Figure out how to make the splash screen display for at least a few seconds
- Figure out what to do about a YouTube API key
- Figure out why MuseScore 4.x exits with "Protocol error" when run in
a Wayland session

I would appreciate help with any of the above.
-- 
Jerry James
http://www.jamezone.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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Daniel Walsh]

On 2/8/23 09:51, Daniel P. Berrangé wrote:

On Wed, Feb 08, 2023 at 09:43:19AM -0500, Stephen Gallagher wrote:

On Wed, Feb 8, 2023 at 9:35 AM Daniel P. Berrangé  wrote:
...

Checked with the team and I'm told 32-bit containers on 64-bit arch
should not be impacted.

More generally podman can run containers of foreign architectures using
qemu-user emulation, albeit with an obvious speed penalty. Still this
has been useful for testing issues on non-x86_64 arches where hardware
access is hard to come by.

Hold up, this is a really useful tip buried in this thread. Is there a
good howto or example of how to do this? This deserves a Fedora
Magazine or CommBlog article!

AFAIR, assuming you have 'qemu-user-static-' RPM installed for the
arch you need (which registers the binfmt handlers at boot), there is
not much more to it than passing '--arch $NAME' to 'podman run'

e.g. on my current x86_64 F37 host I can do

$ podman run -it --arch s390x fedora:rawhide
[root@89b49bd5fefd /]# uname -a
Linux 89b49bd5fefd 6.0.8-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov 11 
15:09:04 UTC 2022 s390x GNU/Linux
[root@89b49bd5fefd /]# uname -m
s390x

one caveat is that if you later run without --arch, I've seen it remember
pick the foreign arch container that's already downloaded, instead of
fetching the native arch container.

Also qemu-user emulation isn't perfect, so if you hit wierd inexplicable
behaviour, QEMU upstream will welcome bug reports...

With regards,
Daniel


Yes Podman picks the latest image of a particular name.  Many debates 
have happened on this, but this is the default.

___
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

[EPEL-devel] Re: Hints for manual upgrading from CentOS 8 Stream to CentOS / Alma / Rockey 9

[Ian Laurie]

On 2/9/23 07:38, Richard Shaw wrote:
I know upgrades are not supported but its for a small home server that 
really only does two things:
For a home server you can use RHEL, the real deal, why mess with 
downstream rebuilds?


Just a thought.

Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: Proposing incompatible upgrade for libkdumpfile (0.4.1 -> 0.5.1)

[Michel Alexandre Salim]

On Wed, 2023-02-08 at 14:09 -0500, Neal Gompa wrote:
> On Wed, Feb 8, 2023 at 12:37 PM Troy Dawson 
> wrote:
> > 
> > On Wed, Feb 8, 2023 at 9:21 AM Michel Alexandre Salim
> >  wrote:
> > > 
> > > Hi all,
> > > 
> > > Per the incompatible upgrade policy[1] I'm proposing upgrading
> > > libkdumpfile from 0.4.1 to the latest 0.5.1 in both EPEL 8 and 9.
> > > 
> > > Bugzilla issues:
> > > - https://bugzilla.redhat.com/show_bug.cgi?id=2162866 (for 0.5.1
> > > in
> > > general)
> > > - https://bugzilla.redhat.com/show_bug.cgi?id=2168301 (for EPEL)
> > > 
> > > Up to 0.4.1, libkdumpfile was packaged without the test suite
> > > being
> > > run, and when I started work on packaging it in Debian I noticed
> > > a lot
> > > of test failures on non-x86_64 architectures:
> > > https://github.com/ptesarik/libkdumpfile/issues/40
> > > 
> > > This is now fixed (0.5.0 is the first version to pass tests
> > > cleanly
> > > without additional patches on Fedora), but prior to its release
> > > we were
> > > basically building in Fedora from a post-0.4.1 snapshot
> > > (
> > > https://src.fedoraproject.org/rpms/libkdumpfile/blob/8b3b02e83af83
> > > 26562a155581d77f04f2ae84197/f/libkdumpfile.spec)
> > > that is likely not ABI compatible with the original 0.4.1 anyway,
> > > so
> > > there's no reasonable way to backport the architecture fixes to
> > > 0.4.1.
> > > 
> > > Change in sonames:
> > > 
> > > [michel@f37-packaging ~]$ comm <(rpmdistro-repoquery fedora
> > > rawhide --
> > > provides libkdumpfile 2>/dev/null) <(rpmdistro-repoquery centos-
> > > stream
> > > 9 --provides libkdumpfile 2>/dev/null)
> > >     libaddrxlat.so.2()(64bit)
> > >     libaddrxlat.so.2(LIBADDRXLAT_0)(64bit)
> > > libaddrxlat.so.3
> > > libaddrxlat.so.3()(64bit)
> > > libaddrxlat.so.3(LIBADDRXLAT_0)
> > > libaddrxlat.so.3(LIBADDRXLAT_0)(64bit)
> > >     libkdumpfile = 0.4.1-5.el9
> > > libkdumpfile = 0.5.0-3.fc38
> > > libkdumpfile(x86-32) = 0.5.0-3.fc38
> > >     libkdumpfile(x86-64) = 0.4.1-5.el9
> > > libkdumpfile(x86-64) = 0.5.0-3.fc38
> > > libkdumpfile.so.10
> > > libkdumpfile.so.10()(64bit)
> > > libkdumpfile.so.10(LIBKDUMPFILE_0)
> > > libkdumpfile.so.10(LIBKDUMPFILE_0)(64bit)
> > >     libkdumpfile.so.9()(64bit)
> > >     libkdumpfile.so.9(LIBKDUMPFILE_0)(64bit)
> > > 
> > > Only drgn currently depends on libkdumpfile, and I plan to
> > > rebuild it
> > > in the same updates:
> > > 
> > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
> > > whatrequires "libaddrxlat.so.2()(64bit)"
> > > Last metadata expiration check: 0:12:30 ago on Wed Feb  8
> > > 11:02:35
> > > 2023.
> > > libkdumpfile-devel-0:0.4.1-5.el9.x86_64
> > > libkdumpfile-util-0:0.4.1-5.el9.x86_64
> > > python3-libkdumpfile-0:0.4.1-5.el9.x86_64
> > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
> > > whatrequires "libkdumpfile.so.9()(64bit)"
> > > Last metadata expiration check: 0:12:40 ago on Wed Feb  8
> > > 11:02:35
> > > 2023.
> > > drgn-0:0.0.22-1.el9.x86_64
> > > libkdumpfile-devel-0:0.4.1-5.el9.x86_64
> > > libkdumpfile-util-0:0.4.1-5.el9.x86_64
> > > python3-libkdumpfile-0:0.4.1-5.el9.x86_64
> > > 
> > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-
> > > legacy 8 --
> > > whatrequires "libaddrxlat.so.2()(64bit)"
> > > Last metadata expiration check: 0:00:08 ago on Wed Feb  8
> > > 11:15:35
> > > 2023.
> > > libkdumpfile-devel-0:0.4.1-5.el8.x86_64
> > > libkdumpfile-util-0:0.4.1-5.el8.x86_64
> > > python3-libkdumpfile-0:0.4.1-5.el8.x86_64
> > > [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-
> > > legacy 8 --
> > > whatrequires "libkdumpfile.so.9()(64bit)"
> > > Last metadata expiration check: 0:00:16 ago on Wed Feb  8
> > > 11:15:35
> > > 2023.
> > > drgn-0:0.0.22-1.el8.x86_64
> > > libkdumpfile-devel-0:0.4.1-5.el8.x86_64
> > > libkdumpfile-util-0:0.4.1-5.el8.x86_64
> > > python3-libkdumpfile-0:0.4.1-5.el8.x86_64
> > > 
> > > [1]:
> > > https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
> > > 
> > > Thanks,
> > 
> > 
> > If I am reading this correctly, the only package affected would be
> > drgn (from python-drgn).
> > It should hopefully just need a rebuild.
> > Is that correct?
> > Were you planning on rebuilding python-drgn, or contacting the
> > package maintainer and having them do it?
> > 
> 
> He's a co-maintainer of python-drgn, so I assume he's going to
> rebuild it himself.
> 
Correct to both. Only drgn is affected, and Davide and I maintain it so
we'll get it rebuilt as a set.

Thanks,

-- 
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: This is a digitally signed message part
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: 

[EPEL-devel] Re: Hints for manual upgrading from CentOS 8 Stream to CentOS / Alma / Rockey 9

[Neal Gompa]

On Wed, Feb 8, 2023 at 3:40 PM Richard Shaw  wrote:
>
> I know upgrades are not supported but its for a small home server that really 
> only does two things:
>
> BackupPC and Unifi (which I both maintain)
>
> Anyone had success doing manual upgrades or did you start with a reinstall?
>

I think AlmaLinux's ELevate thing can help you do in-place upgrades:
https://almalinux.org/elevate

You could also try upgrading to RHEL 9:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/upgrading_from_rhel_8_to_rhel_9/index

(RHEL is available for free for individuals:
https://developers.redhat.com/articles/faqs-no-cost-red-hat-enterprise-linux)



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Hints for manual upgrading from CentOS 8 Stream to CentOS / Alma / Rockey 9

[Richard Shaw]

I know upgrades are not supported but its for a small home server that
really only does two things:

BackupPC and Unifi (which I both maintain)

Anyone had success doing manual upgrades or did you start with a reinstall?

Thanks,
Richard
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2168377] New: perl-Compress-Raw-Zlib-2.204 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168377

Bug ID: 2168377
   Summary: perl-Compress-Raw-Zlib-2.204 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Compress-Raw-Zlib
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.204
Upstream release that is considered latest: 2.204
Current version/release in rawhide: 2.202-5.fc38
URL: http://search.cpan.org/dist/Compress-Raw-Zlib/

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/2712/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Compress-Raw-Zlib


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168377
___
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 2168376] New: perl-Compress-Raw-Bzip2-2.204 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168376

Bug ID: 2168376
   Summary: perl-Compress-Raw-Bzip2-2.204 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Compress-Raw-Bzip2
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.204
Upstream release that is considered latest: 2.204
Current version/release in rawhide: 2.201-3.fc38
URL: http://search.cpan.org/dist/Compress-Raw-Bzip2/

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/2711/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Compress-Raw-Bzip2


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168376
___
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 2168141] Add perl-Cairo to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168141

Tom "spot" Callaway  changed:

   What|Removed |Added

  Flags|needinfo?(spo...@gmail.com) |



--- Comment #3 from Tom "spot" Callaway  ---
^^^


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168141
___
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] Re: Proposing incompatible upgrade for libkdumpfile (0.4.1 -> 0.5.1)

[Neal Gompa]

On Wed, Feb 8, 2023 at 12:37 PM Troy Dawson  wrote:
>
> On Wed, Feb 8, 2023 at 9:21 AM Michel Alexandre Salim 
>  wrote:
>>
>> Hi all,
>>
>> Per the incompatible upgrade policy[1] I'm proposing upgrading
>> libkdumpfile from 0.4.1 to the latest 0.5.1 in both EPEL 8 and 9.
>>
>> Bugzilla issues:
>> - https://bugzilla.redhat.com/show_bug.cgi?id=2162866 (for 0.5.1 in
>> general)
>> - https://bugzilla.redhat.com/show_bug.cgi?id=2168301 (for EPEL)
>>
>> Up to 0.4.1, libkdumpfile was packaged without the test suite being
>> run, and when I started work on packaging it in Debian I noticed a lot
>> of test failures on non-x86_64 architectures:
>> https://github.com/ptesarik/libkdumpfile/issues/40
>>
>> This is now fixed (0.5.0 is the first version to pass tests cleanly
>> without additional patches on Fedora), but prior to its release we were
>> basically building in Fedora from a post-0.4.1 snapshot
>> (https://src.fedoraproject.org/rpms/libkdumpfile/blob/8b3b02e83af8326562a155581d77f04f2ae84197/f/libkdumpfile.spec)
>> that is likely not ABI compatible with the original 0.4.1 anyway, so
>> there's no reasonable way to backport the architecture fixes to 0.4.1.
>>
>> Change in sonames:
>>
>> [michel@f37-packaging ~]$ comm <(rpmdistro-repoquery fedora rawhide --
>> provides libkdumpfile 2>/dev/null) <(rpmdistro-repoquery centos-stream
>> 9 --provides libkdumpfile 2>/dev/null)
>> libaddrxlat.so.2()(64bit)
>> libaddrxlat.so.2(LIBADDRXLAT_0)(64bit)
>> libaddrxlat.so.3
>> libaddrxlat.so.3()(64bit)
>> libaddrxlat.so.3(LIBADDRXLAT_0)
>> libaddrxlat.so.3(LIBADDRXLAT_0)(64bit)
>> libkdumpfile = 0.4.1-5.el9
>> libkdumpfile = 0.5.0-3.fc38
>> libkdumpfile(x86-32) = 0.5.0-3.fc38
>> libkdumpfile(x86-64) = 0.4.1-5.el9
>> libkdumpfile(x86-64) = 0.5.0-3.fc38
>> libkdumpfile.so.10
>> libkdumpfile.so.10()(64bit)
>> libkdumpfile.so.10(LIBKDUMPFILE_0)
>> libkdumpfile.so.10(LIBKDUMPFILE_0)(64bit)
>> libkdumpfile.so.9()(64bit)
>> libkdumpfile.so.9(LIBKDUMPFILE_0)(64bit)
>>
>> Only drgn currently depends on libkdumpfile, and I plan to rebuild it
>> in the same updates:
>>
>> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
>> whatrequires "libaddrxlat.so.2()(64bit)"
>> Last metadata expiration check: 0:12:30 ago on Wed Feb  8 11:02:35
>> 2023.
>> libkdumpfile-devel-0:0.4.1-5.el9.x86_64
>> libkdumpfile-util-0:0.4.1-5.el9.x86_64
>> python3-libkdumpfile-0:0.4.1-5.el9.x86_64
>> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
>> whatrequires "libkdumpfile.so.9()(64bit)"
>> Last metadata expiration check: 0:12:40 ago on Wed Feb  8 11:02:35
>> 2023.
>> drgn-0:0.0.22-1.el9.x86_64
>> libkdumpfile-devel-0:0.4.1-5.el9.x86_64
>> libkdumpfile-util-0:0.4.1-5.el9.x86_64
>> python3-libkdumpfile-0:0.4.1-5.el9.x86_64
>>
>> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-legacy 8 --
>> whatrequires "libaddrxlat.so.2()(64bit)"
>> Last metadata expiration check: 0:00:08 ago on Wed Feb  8 11:15:35
>> 2023.
>> libkdumpfile-devel-0:0.4.1-5.el8.x86_64
>> libkdumpfile-util-0:0.4.1-5.el8.x86_64
>> python3-libkdumpfile-0:0.4.1-5.el8.x86_64
>> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-legacy 8 --
>> whatrequires "libkdumpfile.so.9()(64bit)"
>> Last metadata expiration check: 0:00:16 ago on Wed Feb  8 11:15:35
>> 2023.
>> drgn-0:0.0.22-1.el8.x86_64
>> libkdumpfile-devel-0:0.4.1-5.el8.x86_64
>> libkdumpfile-util-0:0.4.1-5.el8.x86_64
>> python3-libkdumpfile-0:0.4.1-5.el8.x86_64
>>
>> [1]:
>> https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
>>
>> Thanks,
>
>
> If I am reading this correctly, the only package affected would be drgn (from 
> python-drgn).
> It should hopefully just need a rebuild.
> Is that correct?
> Were you planning on rebuilding python-drgn, or contacting the package 
> maintainer and having them do it?
>

He's a co-maintainer of python-drgn, so I assume he's going to
rebuild it himself.




--
真実はいつも一つ！/ Always, there's only one truth!
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2168141] Add perl-Cairo to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168141

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2023-526d25e3d7 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-526d25e3d7


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168141
___
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 2168132] Add perl-Set-IntSpan to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168132

Ralf Corsepius  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|rc040...@freenet.de |ppi...@redhat.com




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168132
___
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 2168132] Add perl-Set-IntSpan to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168132



--- Comment #1 from Ralf Corsepius  ---
Feel free to do it yourself. I am not interested in supporting EPEL.

I made you collaborator and BZ contact for epel*.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168132
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Take 1 minute to help with Infra & Releng Team with a decision

[Chuck Anderson]

On Wed, Feb 08, 2023 at 06:43:02PM +0100, Eike Rathke wrote:
> Hi Michal,
> 
> On Tuesday, 2023-02-07 16:24:16 +0100, Michal Konecny wrote:
> 
> > [0] - https://forms.gle/J2HWDkw1UNuj8HYD8
> 
> Don't be surprised if you don't get the number of answers you hoped for,
> on
> 
> a) a Google form
> b) that requires a Google account
> c) to be logged in

b) and c) are not true.  A private-browsing FF window worked fine for me.



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: Take 1 minute to help with Infra & Releng Team with a decision

[Eike Rathke]

Hi Michal,

On Tuesday, 2023-02-07 16:24:16 +0100, Michal Konecny wrote:

> [0] - https://forms.gle/J2HWDkw1UNuj8HYD8

Don't be surprised if you don't get the number of answers you hoped for,
on

a) a Google form
b) that requires a Google account
c) to be logged in

  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


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

[EPEL-devel] Re: Proposing incompatible upgrade for libkdumpfile (0.4.1 -> 0.5.1)

[Troy Dawson]

On Wed, Feb 8, 2023 at 9:21 AM Michel Alexandre Salim <
sali...@fedoraproject.org> wrote:

> Hi all,
>
> Per the incompatible upgrade policy[1] I'm proposing upgrading
> libkdumpfile from 0.4.1 to the latest 0.5.1 in both EPEL 8 and 9.
>
> Bugzilla issues:
> - https://bugzilla.redhat.com/show_bug.cgi?id=2162866 (for 0.5.1 in
> general)
> - https://bugzilla.redhat.com/show_bug.cgi?id=2168301 (for EPEL)
>
> Up to 0.4.1, libkdumpfile was packaged without the test suite being
> run, and when I started work on packaging it in Debian I noticed a lot
> of test failures on non-x86_64 architectures:
> https://github.com/ptesarik/libkdumpfile/issues/40
>
> This is now fixed (0.5.0 is the first version to pass tests cleanly
> without additional patches on Fedora), but prior to its release we were
> basically building in Fedora from a post-0.4.1 snapshot
> (
> https://src.fedoraproject.org/rpms/libkdumpfile/blob/8b3b02e83af8326562a155581d77f04f2ae84197/f/libkdumpfile.spec
> )
> that is likely not ABI compatible with the original 0.4.1 anyway, so
> there's no reasonable way to backport the architecture fixes to 0.4.1.
>
> Change in sonames:
>
> [michel@f37-packaging ~]$ comm <(rpmdistro-repoquery fedora rawhide --
> provides libkdumpfile 2>/dev/null) <(rpmdistro-repoquery centos-stream
> 9 --provides libkdumpfile 2>/dev/null)
> libaddrxlat.so.2()(64bit)
> libaddrxlat.so.2(LIBADDRXLAT_0)(64bit)
> libaddrxlat.so.3
> libaddrxlat.so.3()(64bit)
> libaddrxlat.so.3(LIBADDRXLAT_0)
> libaddrxlat.so.3(LIBADDRXLAT_0)(64bit)
> libkdumpfile = 0.4.1-5.el9
> libkdumpfile = 0.5.0-3.fc38
> libkdumpfile(x86-32) = 0.5.0-3.fc38
> libkdumpfile(x86-64) = 0.4.1-5.el9
> libkdumpfile(x86-64) = 0.5.0-3.fc38
> libkdumpfile.so.10
> libkdumpfile.so.10()(64bit)
> libkdumpfile.so.10(LIBKDUMPFILE_0)
> libkdumpfile.so.10(LIBKDUMPFILE_0)(64bit)
> libkdumpfile.so.9()(64bit)
> libkdumpfile.so.9(LIBKDUMPFILE_0)(64bit)
>
> Only drgn currently depends on libkdumpfile, and I plan to rebuild it
> in the same updates:
>
> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
> whatrequires "libaddrxlat.so.2()(64bit)"
> Last metadata expiration check: 0:12:30 ago on Wed Feb  8 11:02:35
> 2023.
> libkdumpfile-devel-0:0.4.1-5.el9.x86_64
> libkdumpfile-util-0:0.4.1-5.el9.x86_64
> python3-libkdumpfile-0:0.4.1-5.el9.x86_64
> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
> whatrequires "libkdumpfile.so.9()(64bit)"
> Last metadata expiration check: 0:12:40 ago on Wed Feb  8 11:02:35
> 2023.
> drgn-0:0.0.22-1.el9.x86_64
> libkdumpfile-devel-0:0.4.1-5.el9.x86_64
> libkdumpfile-util-0:0.4.1-5.el9.x86_64
> python3-libkdumpfile-0:0.4.1-5.el9.x86_64
>
> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-legacy 8 --
> whatrequires "libaddrxlat.so.2()(64bit)"
> Last metadata expiration check: 0:00:08 ago on Wed Feb  8 11:15:35
> 2023.
> libkdumpfile-devel-0:0.4.1-5.el8.x86_64
> libkdumpfile-util-0:0.4.1-5.el8.x86_64
> python3-libkdumpfile-0:0.4.1-5.el8.x86_64
> [michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-legacy 8 --
> whatrequires "libkdumpfile.so.9()(64bit)"
> Last metadata expiration check: 0:00:16 ago on Wed Feb  8 11:15:35
> 2023.
> drgn-0:0.0.22-1.el8.x86_64
> libkdumpfile-devel-0:0.4.1-5.el8.x86_64
> libkdumpfile-util-0:0.4.1-5.el8.x86_64
> python3-libkdumpfile-0:0.4.1-5.el8.x86_64
>
> [1]:
>
> https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
>
> Thanks,
>

If I am reading this correctly, the only package affected would be drgn
(from python-drgn).
It should hopefully just need a rebuild.
Is that correct?
Were you planning on rebuilding python-drgn, or contacting the package
maintainer and having them do it?

Troy
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Proposing incompatible upgrade for libkdumpfile (0.4.1 -> 0.5.1)

[Michel Alexandre Salim]

Hi all,

Per the incompatible upgrade policy[1] I'm proposing upgrading
libkdumpfile from 0.4.1 to the latest 0.5.1 in both EPEL 8 and 9.

Bugzilla issues:
- https://bugzilla.redhat.com/show_bug.cgi?id=2162866 (for 0.5.1 in
general)
- https://bugzilla.redhat.com/show_bug.cgi?id=2168301 (for EPEL)

Up to 0.4.1, libkdumpfile was packaged without the test suite being
run, and when I started work on packaging it in Debian I noticed a lot
of test failures on non-x86_64 architectures:
https://github.com/ptesarik/libkdumpfile/issues/40

This is now fixed (0.5.0 is the first version to pass tests cleanly
without additional patches on Fedora), but prior to its release we were
basically building in Fedora from a post-0.4.1 snapshot
(https://src.fedoraproject.org/rpms/libkdumpfile/blob/8b3b02e83af8326562a155581d77f04f2ae84197/f/libkdumpfile.spec)
that is likely not ABI compatible with the original 0.4.1 anyway, so
there's no reasonable way to backport the architecture fixes to 0.4.1.

Change in sonames:

[michel@f37-packaging ~]$ comm <(rpmdistro-repoquery fedora rawhide --
provides libkdumpfile 2>/dev/null) <(rpmdistro-repoquery centos-stream
9 --provides libkdumpfile 2>/dev/null)
libaddrxlat.so.2()(64bit)
libaddrxlat.so.2(LIBADDRXLAT_0)(64bit)
libaddrxlat.so.3
libaddrxlat.so.3()(64bit)
libaddrxlat.so.3(LIBADDRXLAT_0)
libaddrxlat.so.3(LIBADDRXLAT_0)(64bit)
libkdumpfile = 0.4.1-5.el9
libkdumpfile = 0.5.0-3.fc38
libkdumpfile(x86-32) = 0.5.0-3.fc38
libkdumpfile(x86-64) = 0.4.1-5.el9
libkdumpfile(x86-64) = 0.5.0-3.fc38
libkdumpfile.so.10
libkdumpfile.so.10()(64bit)
libkdumpfile.so.10(LIBKDUMPFILE_0)
libkdumpfile.so.10(LIBKDUMPFILE_0)(64bit)
libkdumpfile.so.9()(64bit)
libkdumpfile.so.9(LIBKDUMPFILE_0)(64bit)

Only drgn currently depends on libkdumpfile, and I plan to rebuild it
in the same updates:

[michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
whatrequires "libaddrxlat.so.2()(64bit)"
Last metadata expiration check: 0:12:30 ago on Wed Feb  8 11:02:35
2023.
libkdumpfile-devel-0:0.4.1-5.el9.x86_64
libkdumpfile-util-0:0.4.1-5.el9.x86_64
python3-libkdumpfile-0:0.4.1-5.el9.x86_64
[michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream 9 --
whatrequires "libkdumpfile.so.9()(64bit)"
Last metadata expiration check: 0:12:40 ago on Wed Feb  8 11:02:35
2023.
drgn-0:0.0.22-1.el9.x86_64
libkdumpfile-devel-0:0.4.1-5.el9.x86_64
libkdumpfile-util-0:0.4.1-5.el9.x86_64
python3-libkdumpfile-0:0.4.1-5.el9.x86_64

[michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-legacy 8 --
whatrequires "libaddrxlat.so.2()(64bit)"
Last metadata expiration check: 0:00:08 ago on Wed Feb  8 11:15:35
2023.
libkdumpfile-devel-0:0.4.1-5.el8.x86_64
libkdumpfile-util-0:0.4.1-5.el8.x86_64
python3-libkdumpfile-0:0.4.1-5.el8.x86_64
[michel@f37-packaging ~]$ rpmdistro-repoquery centos-stream-legacy 8 --
whatrequires "libkdumpfile.so.9()(64bit)"
Last metadata expiration check: 0:00:16 ago on Wed Feb  8 11:15:35
2023.
drgn-0:0.0.22-1.el8.x86_64
libkdumpfile-devel-0:0.4.1-5.el8.x86_64
libkdumpfile-util-0:0.4.1-5.el8.x86_64
python3-libkdumpfile-0:0.4.1-5.el8.x86_64

[1]:
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/

Thanks,

-- 
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: This is a digitally signed message part
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2168141] Add perl-Cairo to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168141

Sergio Basto  changed:

   What|Removed |Added

 CC||ser...@serjux.com
 Blocks||2125015
  Flags||needinfo?(spo...@gmail.com)



--- Comment #1 from Sergio Basto  ---

the scratch build went fine 
https://koji.fedoraproject.org/koji/taskinfo?taskID=97277051

If not interested or no time, please add me as co-maintainer my fas is sergiomb



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2125015
[Bug 2125015] perl-Gtk3 EPEL9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168141
___
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 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Sergio Basto  changed:

   What|Removed |Added

 Depends On||2168141





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2168141
[Bug 2168141] Add perl-Cairo to EPEL9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Tenacity

[Jason L Tibbitts III]

> stan via devel  writes:

> As they say in the BUILDING.md file,
> though, fedora lacks wxWidgets 3.1.5 or greater. That stops the
> configuration, cmake -G Ninja -S . -B build when it errors out.

That's odd; as far as I can see, F36 has 3.1.5 and F37 has 3.2.1.

 - J<
___
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: Tenacity

[stan via devel]

On Wed, 8 Feb 2023 09:02:47 -0700
stan  wrote:

> On Wed, 8 Feb 2023 08:44:30 -0700
> stan  wrote:
> 
> > On Wed, 08 Feb 2023 06:25:07 +1100
> > Philip Rhoades via devel  wrote:
> >
> > > Has there been any discussion about getting a Tenacity RPM going
> > > for Fedora? - I would prefer that to having to use the AppImage
> > > version .
> > 
> > I knew about the corporate takeover of audacity, but I didn't know
> > about this fork.  I'm not aware of any effort to package it, but you
> > could build it from source, and install it in /usr/local, probably
> > the default.
> > 
> > If you have development tools installed, that could be as easy as
> > ./configure  (not as root)
> > make  (not as root)
> > make install  (as root)
> > in the directory where you unpack the source code.  I used to build
> > audacity that way from its git repository.  Occasionally there would
> > be a glitch with versions, but it worked pretty consistently.  You
> > will have to have /usr/local/bin in your path (I think that is also
> > a default in Fedora).
> > 
> > https://tenacityaudio.org/
> > 
> > Of course, an rpm would be more convenient, but this *is* an
> > alternative.  
>
> PS
> I see on the devel list that there are potential patent issues because
> of the use of certain codecs.  I finessed that by using the ffmpeg
> version from rpmfusion, and thus installing the free and nonfree
> codecs they are referencing.  If you try the above build without
> them, it will probably still build, but will have reduced
> functionality.  Now that mp3 and mpeg are off patent, I think the use
> of other codecs would be limited unless you are editing commercial
> DVD files using aac, or video files using h264.  Videos using webm
> probably are using open source video and audio encoders.

Disregard my comments.  The process to compile tenacity is completely
different from the process to compile audacity.  A plus is that the
BUILDING.md file gives a command to install the dependencies for
building tenacity in Fedora. As they say in the BUILDING.md file,
though, fedora lacks wxWidgets 3.1.5 or greater. That stops the
configuration,
cmake -G Ninja -S . -B build
when it errors out.
They give a link to the wxWidgets website, so it is possible to
compile it and put it in /usr/local, but that seems to be going down
the rabbit hole.  I might pursue this, even though I don't really do a
lot of (any?) sound editing anymore.  Just for the challenge.  Maybe
not. :-)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 38 mass rebuild is finished

[Dan Horák]

On Wed, 08 Feb 2023 15:24:47 +
Sérgio Basto  wrote:

> On Tue, 2023-01-31 at 12:03 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Mon, Jan 30, 2023 at 04:45:37PM -0800, Kevin Fenzi wrote:  
> > > On Tue, Jan 24, 2023 at 09:42:10AM +, Zbigniew Jędrzejewski-
> > > Szmek wrote:  
> > > > On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote:  
> > > > > On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote:  
> > > > > > 
> > > > > > I found more 5 with
> > > > > > https://koji.fedoraproject.org/koji/tasks?owner=releng=active=tree=all=-id
> > > > > > 
> > > > > > 96481236 build (f38-rebuild,
> > > > > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa)
> > > > > > 
> > > > > > 96474133 build (f38-rebuild, /rpms/trace-
> > > > > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080)
> > > > > > 
> > > > > > 96404064 build (f38-rebuild, /rpms/perl-
> > > > > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967)
> > > > > > 
> > > > > > 96383273 build (f38-rebuild,
> > > > > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d
> > > > > > 
> > > > > > 96368979 build (f38-rebuild,
> > > > > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1f
> > > > > > f)  
> > > > > 
> > > > > Yes, I have canceled all those now.   
> > > > 
> > > > I started builds for all of those now.  
> > > 
> > > All of them have hung again after running since you started them. 
> > > 
> > > I think someone is going to need to try and build them in local
> > > mock and
> > > see where they are getting stuck. 
> > > 
> > > Can you cancel them again? Or would you like me to try and look and
> > > see
> > > what they are hung on?  
> > 
> > I cancelled them now. All five were still hung.
> > It's up to the maintainers to figure out what is going.
> > E.g. yaksa was hanging in tests…  
> 
> Any news about these packages that hang on koji ? we may include opencv
> package on this list.
> 
> Last lines of build opencv on ppc64le are [1] and after we got 55385703
> (55 millions) of lines with "mashing detected" message,  the log file
> have 2,30G ! 
> 
> Also I see "buffer overflow detected ***: terminated cat: /symlink2-
> fakechroot: No such file or directory " on fakechroot

this looks weird, I am trying a local build


Dan
 
> Best regards,
> 
> [1]
> https://koji.fedoraproject.org/koji/taskinfo?taskID=97209133
> 
> /usr/include/c++/13/bits/stl_vector.h:1142: std::vector<_Tp,
> _Alloc>::const_reference std::vector<_Tp,
> _Alloc>::operator[](size_type) const [with _Tp = float; _Alloc =  
> std::allocator; const_reference = const float&; size_type = long
> unsigned int]: Assertion '__n < this->size()' failed.
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** longjmp causes uninitialized stack frame ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> 
> > 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  
> 
> -- 
> 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: 
> 

Re: Tenacity

[stan via devel]

On Wed, 8 Feb 2023 08:44:30 -0700
stan  wrote:

> On Wed, 08 Feb 2023 06:25:07 +1100
> Philip Rhoades via devel  wrote:
>  
> > Has there been any discussion about getting a Tenacity RPM going
> > for Fedora? - I would prefer that to having to use the AppImage
> > version .  
> 
> I knew about the corporate takeover of audacity, but I didn't know
> about this fork.  I'm not aware of any effort to package it, but you
> could build it from source, and install it in /usr/local, probably the
> default.
> 
> If you have development tools installed, that could be as easy as
> ./configure  (not as root)
> make  (not as root)
> make install  (as root)
> in the directory where you unpack the source code.  I used to build
> audacity that way from its git repository.  Occasionally there would
> be a glitch with versions, but it worked pretty consistently.  You
> will have to have /usr/local/bin in your path (I think that is also a
> default in Fedora).
> 
> https://tenacityaudio.org/
> 
> Of course, an rpm would be more convenient, but this *is* an
> alternative.

PS
I see on the devel list that there are potential patent issues because
of the use of certain codecs.  I finessed that by using the ffmpeg
version from rpmfusion, and thus installing the free and nonfree codecs
they are referencing.  If you try the above build without them, it will
probably still build, but will have reduced functionality.  Now that
mp3 and mpeg are off patent, I think the use of other codecs would be
limited unless you are editing commercial DVD files using aac, or video
files using h264.  Videos using webm probably are using open source
video and audio encoders.
___
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: Tenacity

[Neal Gompa]

On Tue, Feb 7, 2023 at 5:22 PM Gary Buhrmaster
 wrote:
>
> On Tue, Feb 7, 2023 at 7:26 PM Philip Rhoades via devel
>  wrote:
> >
> > People,
> >
> > Has there been any discussion about getting a Tenacity RPM going for
> > Fedora? - I would prefer that to having to use the AppImage version . .
> >
>
> As I recall, in the beginning, Tenacity (to perform
> most meaningful operations) required FFmpeg,
> which was not in Fedora, so that was a clear
> show stopper.  Now that FFmpeg is (or at least
> with the codecs without IP encumbrances)
> Tenacity might be able to be packaged as long
> as it does not include any other libraries that are
> IP encumbered.  Someone will need to perform
> that IP review, as codecs are a minefield.

To the best of my knowledge, Tenacity should work fine with Fedora's FFmpeg now.

Tenacity's documentation has already been updated accordingly.




--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Tenacity

[stan via devel]

On Wed, 08 Feb 2023 06:25:07 +1100
Philip Rhoades via devel  wrote:
 
> Has there been any discussion about getting a Tenacity RPM going for 
> Fedora? - I would prefer that to having to use the AppImage version .

I knew about the corporate takeover of audacity, but I didn't know
about this fork.  I'm not aware of any effort to package it, but you
could build it from source, and install it in /usr/local, probably the
default.

If you have development tools installed, that could be as easy as
./configure  (not as root)
make  (not as root)
make install  (as root)
in the directory where you unpack the source code.  I used to build
audacity that way from its git repository.  Occasionally there would be
a glitch with versions, but it worked pretty consistently.  You will
have to have /usr/local/bin in your path (I think that is also a
default in Fedora).

https://tenacityaudio.org/

Of course, an rpm would be more convenient, but this *is* an
alternative.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 38 mass rebuild is finished

[Sérgio Basto]

On Tue, 2023-01-31 at 12:03 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Jan 30, 2023 at 04:45:37PM -0800, Kevin Fenzi wrote:
> > On Tue, Jan 24, 2023 at 09:42:10AM +, Zbigniew Jędrzejewski-
> > Szmek wrote:
> > > On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote:
> > > > On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote:
> > > > > 
> > > > > I found more 5 with
> > > > > https://koji.fedoraproject.org/koji/tasks?owner=releng=active=tree=all=-id
> > > > > 
> > > > > 96481236 build (f38-rebuild,
> > > > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa)
> > > > > 
> > > > > 96474133 build (f38-rebuild, /rpms/trace-
> > > > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080)
> > > > > 
> > > > > 96404064 build (f38-rebuild, /rpms/perl-
> > > > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967)
> > > > > 
> > > > > 96383273 build (f38-rebuild,
> > > > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d
> > > > > 
> > > > > 96368979 build (f38-rebuild,
> > > > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1f
> > > > > f)
> > > > 
> > > > Yes, I have canceled all those now. 
> > > 
> > > I started builds for all of those now.
> > 
> > All of them have hung again after running since you started them. 
> > 
> > I think someone is going to need to try and build them in local
> > mock and
> > see where they are getting stuck. 
> > 
> > Can you cancel them again? Or would you like me to try and look and
> > see
> > what they are hung on?
> 
> I cancelled them now. All five were still hung.
> It's up to the maintainers to figure out what is going.
> E.g. yaksa was hanging in tests…

Any news about these packages that hang on koji ? we may include opencv
package on this list.

Last lines of build opencv on ppc64le are [1] and after we got 55385703
(55 millions) of lines with "mashing detected" message,  the log file
have 2,30G ! 

Also I see "buffer overflow detected ***: terminated cat: /symlink2-
fakechroot: No such file or directory " on fakechroot

Best regards,

[1]
https://koji.fedoraproject.org/koji/taskinfo?taskID=97209133

/usr/include/c++/13/bits/stl_vector.h:1142: std::vector<_Tp,
_Alloc>::const_reference std::vector<_Tp,
_Alloc>::operator[](size_type) const [with _Tp = float; _Alloc =
std::allocator; const_reference = const float&; size_type = long
unsigned int]: Assertion '__n < this->size()' failed.
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated

> 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

-- 
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: reclaim orphaned moarvm package

[Felix Wang]

okay, thanks for your advice.
___
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: reclaim orphaned moarvm package

[Felix Wang]

update: I also plan to claim nqp and rakudo 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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Daniel P . Berrangé]

On Wed, Feb 08, 2023 at 09:43:19AM -0500, Stephen Gallagher wrote:
> On Wed, Feb 8, 2023 at 9:35 AM Daniel P. Berrangé  wrote:
> ...
> > > Checked with the team and I'm told 32-bit containers on 64-bit arch
> > > should not be impacted.
> >
> > More generally podman can run containers of foreign architectures using
> > qemu-user emulation, albeit with an obvious speed penalty. Still this
> > has been useful for testing issues on non-x86_64 arches where hardware
> > access is hard to come by.
> 
> Hold up, this is a really useful tip buried in this thread. Is there a
> good howto or example of how to do this? This deserves a Fedora
> Magazine or CommBlog article!

AFAIR, assuming you have 'qemu-user-static-' RPM installed for the
arch you need (which registers the binfmt handlers at boot), there is
not much more to it than passing '--arch $NAME' to 'podman run'

e.g. on my current x86_64 F37 host I can do

$ podman run -it --arch s390x fedora:rawhide
[root@89b49bd5fefd /]# uname -a
Linux 89b49bd5fefd 6.0.8-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov 11 
15:09:04 UTC 2022 s390x GNU/Linux
[root@89b49bd5fefd /]# uname -m
s390x

one caveat is that if you later run without --arch, I've seen it remember
pick the foreign arch container that's already downloaded, instead of
fetching the native arch container.

Also qemu-user emulation isn't perfect, so if you hit wierd inexplicable
behaviour, QEMU upstream will welcome bug reports...

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

[Bug 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Sergio Basto  changed:

   What|Removed |Added

   Assignee|dd...@cpan.org  |ser...@serjux.com




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Stephen Gallagher]

On Wed, Feb 8, 2023 at 9:35 AM Daniel P. Berrangé  wrote:
...
> > Checked with the team and I'm told 32-bit containers on 64-bit arch
> > should not be impacted.
>
> More generally podman can run containers of foreign architectures using
> qemu-user emulation, albeit with an obvious speed penalty. Still this
> has been useful for testing issues on non-x86_64 arches where hardware
> access is hard to come by.

Hold up, this is a really useful tip buried in this thread. Is there a
good howto or example of how to do this? This deserves a Fedora
Magazine or CommBlog article!
___
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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Daniel P . Berrangé]

On Wed, Feb 08, 2023 at 07:17:16PM +0530, Lokesh Mandvekar wrote:
> On Wed, Feb 8, 2023 at 9:01 AM Kevin Kofler via devel
>  wrote:
> > Does dropping the 32-bit i686 build also imply you cannot use 32-bit
> > containers on a 64-bit architecture? If so, will anybody notice? Since you
> > did not use any special naming tricks (both package naming and file naming)
> > to allow installing both versions (as in, e.g., wine), one has to go out of
> > one's way to install the 32-bit version instead of the 64-bit one, and they
> > cannot both be installed at once.
> 
> Checked with the team and I'm told 32-bit containers on 64-bit arch
> should not be impacted.

More generally podman can run containers of foreign architectures using
qemu-user emulation, albeit with an obvious speed penalty. Still this
has been useful for testing issues on non-x86_64 arches where hardware
access is hard to come by.

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: reclaim orphaned moarvm package

[Petr Pisar]

V Wed, Feb 08, 2023 at 02:09:10PM -, Felix Wang napsal(a):
> I had planned to pick `moarvm` package up when I saw it was already
> orphaned. I am very willing to maintain or comaintain it. My FAS name is
> topazus. 

Great to read it. You can follow this procedure for unretiring a package
.

-- Petr


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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Kevin Kofler via devel]

Lokesh Mandvekar wrote:
> Checked with the team and I'm told 32-bit containers on 64-bit arch
> should not be impacted.

Good to know. Then I think nobody will miss the i686 build or even notice 
its absence (considering that it is not a shared library and that pure i686 
installations of Fedora have not been supported for years now).

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

reclaim orphaned moarvm package

[Felix Wang]

I had planned to pick `moarvm` package up when I saw it was already orphaned. I 
am very willing to maintain or comaintain it. My FAS name is topazus.
___
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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Lokesh Mandvekar]

On Wed, Feb 8, 2023 at 9:01 AM Kevin Kofler via devel
 wrote:
> Does dropping the 32-bit i686 build also imply you cannot use 32-bit
> containers on a 64-bit architecture? If so, will anybody notice? Since you
> did not use any special naming tricks (both package naming and file naming)
> to allow installing both versions (as in, e.g., wine), one has to go out of
> one's way to install the 32-bit version instead of the 64-bit one, and they
> cannot both be installed at once.

Checked with the team and I'm told 32-bit containers on 64-bit arch
should not be impacted.

HTH.

Thanks.
-- 
Lokesh
Libera, GitLab, GitHub, Fedora: lsm5
Matrix: @lsm5:lsm5.ems.host
GPG: 0xC7C3A0DD
https://keybase.io/lsm5
___
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: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Lokesh Mandvekar]

On Tue, Feb 7, 2023 at 11:06 PM Maxwell G via devel
 wrote:

>
> As for i686, you don't need extra paperwork thanks to exclude packages
> thanks to
> https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval.
> You just need to properly handle dependent packages. You cannot
> ExcludeArch a package unless all of its dependents are also excluded.
> It's recommended to exclude Go packages with
> `ExclusiveArch: %{golang_arches_future}`.
> For other packages, a regular `ExcludeArch: %{ix86}` is sufficient.

Great, that makes life a lot easier. I'll go ahead with
ExclusiveArch-ing them (or ExcludeArch if permissible). armhfp on f36
will be left as-is.

Thank you.
-- 
Lokesh
Libera, GitLab, GitHub, Fedora: lsm5
Matrix: @lsm5:lsm5.ems.host
GPG: 0xC7C3A0DD
https://keybase.io/lsm5
___
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: Retiring Bottles in favor of Flatpak provided by upstream

[Kevin Kofler via devel]

Daniel P. Berrangé wrote:
> Looking at Flatpaks with both my upstream author hat and distro maintainer
> hat, the main advantages I see is not the isolation. It is that they have
> the potential to eliminate the massive amount of duplicated work between
> every distro re-packaging the same app, and ensure more timely availablity
> of new releases to end users by de-coupling from the distro release cycle.

But that comes at the cost of "lowest common denominator" (*) packaging with 
bundled dependencies (at least those not included in the runtime), inability 
to use distro-specific compiler flags (e.g., you either always build with or 
always without frame pointers, independently of what the user's distribution 
prefers), less system integration (also due to the isolation), etc.

> As an upstream author, I want the latest releases of my software to be
> available for users to install as quickly as possible. Distros largely
> aren't satisfying that desire as well as I would like. If I rely on
> distro packaging, there can 3-12 month delay before a distro gets my
> new release in front of a user depending on their release cycle.

Users of non-rolling-release distros do not necessarily *want* to get 
upgraded the latest major version of your application (with, e.g., major UI 
changes) at an unexpected point in time at which they just want to get work 
done. (And just not upgrading Flatpaks is also not a good idea because of 
security.)

Where it makes sense, distro-provided opt-in PPA mechanisms such as Copr, 
OBS, Launchpad PPAs, etc. can be used (but sure, it is yet another place 
where the application needs to be packaged, that is the drawback).

> The tragedy would be if every distro ends up re-doing the
> creation and shipping of flatpaks, just as they do today
> with the distros specific packaging formats.

Is that not exactly what Fedora Flatpaks are about?

Kevin Kofler

(*) I know this term ("lowest common denominator") is mathematically 
nonsense. There is only a least/lowest common multiple and a greatest common 
denominator in mathematics. :-)
___
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: Package naming suggestion?

[Sandro]

On 08-02-2023 03:38, Joe Doss wrote:

On 2/7/23 8:28 PM, Chris Adams wrote:

I've got a few useful Nagios monitoring plugins I'd like to add to
Fedora/EPEL.  I'm rather unimaginative at naming, so the Github repo for
them is "nagios-plugins-cmadams"... while I wouldn't mind having a
package with my username in it in Fedora, it seems a little vain. :)

Before I go making a package and submitting a new package ticket, any
suggestions about that?

https://github.com/cmadamsgit/nagios-plugins-cmadams



My two cents. I am a big fan of packages that are very explicit on what
they are in the name. Doing a `dnf search nagios` turns up that most
plugins start with nagios-plugin- so your current repo name follows that
established convention.

I'd say leave it as is and get that package submitted. :)


I would suggest one package per plugin. The GitHub repo appears to 
contain three plugins. There's also some overlap in functionality. E.g. 
in Fedora we already have nagios-plugins-ssl_cert [1], which appears to 
do the same as your check_cert plugin.


The same holds for nagios-plugins-smtp [2].

Probably best to consult the nagios / nagios-plugins maintainers 
regarding naming convention and overlapping functionality. Should they 
not respond on list, then you can get in touch using 
${PACKAGE_NAME}-maintainers@fp.o.


[1] 
https://packages.fedoraproject.org/pkgs/nagios-plugins-ssl_cert/nagios-plugins-ssl_cert/
[2] 
https://packages.fedoraproject.org/pkgs/nagios-plugins/nagios-plugins-smtp/


-- 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

Fedora rawhide compose report: 20230208.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230207.n.0
NEW: Fedora-Rawhide-20230208.n.0

= SUMMARY =
Added images:1
Dropped images:  3
Added packages:  7
Dropped packages:1
Upgraded packages:   129
Downgraded packages: 0

Size of added packages:  1.19 MiB
Size of dropped packages:568.23 KiB
Size of upgraded packages:   16.80 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   101.99 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Phosh raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Phosh-Rawhide-20230208.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230207.n.0.iso
Image: Comp_Neuro live x86_64
Path: Labs/x86_64/iso/Fedora-Comp_Neuro-Live-x86_64-Rawhide-20230207.n.0.iso
Image: Mate live x86_64
Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20230207.n.0.iso

= ADDED PACKAGES =
Package: axc-0.3.7-1.20220526git8e14a66.fc38
Summary: Client library for libsignal-protocol-c
RPMs:axc axc-devel
Size:285.41 KiB

Package: libigloo-0.9.2-1.fc38
Summary: C framework from Icecast
RPMs:libigloo libigloo-devel libigloo-tests
Size:384.86 KiB

Package: libomemo-0.8.1-1.fc38
Summary: OMEMO implementation in plain C
RPMs:libomemo libomemo-devel
Size:203.03 KiB

Package: numberstation-1.2.0-4.fc38
Summary: TOTP Authenticator application
RPMs:numberstation
Size:27.29 KiB

Package: purple-lurch-0.7.0-1.fc38
Summary: OMEMO Encryption plugin for libpurple
RPMs:purple-lurch
Size:201.90 KiB

Package: python-typepy-1.3.0-1.fc38
Summary: Python library for variable type checker/validator/converter at a run 
time
RPMs:python3-typepy
Size:90.37 KiB

Package: rust-nu-test-support-0.74.0-1.fc38
Summary: Support for writing Nushell tests
RPMs:rust-nu-test-support+default-devel rust-nu-test-support-devel
Size:28.28 KiB


= DROPPED PACKAGES =
Package: simdock-1.5.3-10.fc38
Summary: Fast and customizable dockbar
RPMs:simdock
Size:568.23 KiB


= UPGRADED PACKAGES =
Package:  OpenSceneGraph-3.6.5-14.fc38
Old package:  OpenSceneGraph-3.6.5-13.fc38
Summary:  High performance real-time graphics toolkit
RPMs: OpenSceneGraph OpenSceneGraph-Collada OpenSceneGraph-OpenEXR 
OpenSceneGraph-devel OpenSceneGraph-examples OpenSceneGraph-examples-SDL 
OpenSceneGraph-examples-fltk OpenSceneGraph-examples-gtk OpenSceneGraph-gdal 
OpenSceneGraph-gstreamer OpenSceneGraph-libs OpenThreads OpenThreads-devel 
mingw32-OpenSceneGraph mingw32-OpenSceneGraph-tools mingw64-OpenSceneGraph 
mingw64-OpenSceneGraph-tools
Size: 206.32 MiB
Size change:  -9.04 KiB
Changelog:
  * Tue Feb 07 2023 Sandro Mani  - 3.6.5-14
  - Rebuild (mingw-poppler)


Package:  aardvark-dns-1.5.0-3.fc38
Old package:  aardvark-dns-1.5.0-1.fc38
Summary:  Authoritative DNS server for A/ container records
RPMs: aardvark-dns
Size: 3.80 MiB
Size change:  -439.23 KiB
Changelog:
  * Tue Feb 07 2023 Lokesh Mandvekar  - 1.5.0-2
  - Enable debuginfo

  * Tue Feb 07 2023 Lokesh Mandvekar  - 1.5.0-3
  - BR: rust-packaging


Package:  amg4psblas-1.1.0-5.fc38
Old package:  amg4psblas-1.1.0-4.fc38
Summary:  Algebraic Multigrid Package based on PSBLAS
RPMs: amg4psblas-doc amg4psblas-mpich amg4psblas-mpich-devel 
amg4psblas-openmpi amg4psblas-openmpi-devel amg4psblas-serial 
amg4psblas-serial-devel
Size: 1.31 GiB
Size change:  4.90 KiB
Changelog:
  * Tue Feb 07 2023 Antonio Trande  - 1.1.0-5
  - Drop OpenMPI support on i686


Package:  anaconda-38.21-1.fc38
Old package:  anaconda-38.19-1.fc38
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-webui anaconda-widgets anaconda-widgets-devel
Size: 19.47 MiB
Size change:  11.87 KiB
Changelog:
  * Tue Feb 07 2023 Packit  - 38.20-1
  - Add Sericea - ostree based Sway variant (jkonecny)
  - Fix the systemd generator for systemd 253 (#2165433) (awilliam)
  - WebUI: Updated wizard footer buttons (ozobal)
  - Remove the dmraid and nodmraid boot options (vtrefny)
  - Update translations from Weblate

  * Tue Feb 07 2023 Packit  - 38.21-1
  - Sort RPM versions via rpm.labelCompare() and not via
packaging.version.LegacyVersion() (miro)
  - Update translations from Weblate


Package:  awscli-1.27.66-1.fc38
Old package:  awscli-1.27.65-1.fc38
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.28 MiB
Size change:  -83 B
Changelog:
  * Tue Feb 07 2023 Gwyn Ciesla  - 1.27.66-1
  - 1.27.66


Package:  babeld-1.12.2-1.fc38
Old package:  babeld-1.12.1-3.fc38
Summary:  Ad-hoc network routing daemon
RPMs: babeld
Size: 418.78 KiB
Size change:  -466 B
Changelog:
  * Tue Feb 07 2023 Gwyn Ciesla  - 1.12.2-1
  - 1.12.2

jaxb, jaxb-fi, jakarta-activation license change

[Marián Konček]

After my updates to several jaxb packages, some of the licenses changed:

Source package jaxb:
jaxb-rngom: BSD -> (MIT and BSD)
jaxb-xjc: BSD -> (BSD and ASL 2.0)

Source package jaxb-fi:
jaxb-fi-tests (previously known as FastInfosetRoundTripTests): (ASL 2.0 
and BSD and ASL 1.1) -> (ASL 2.0 and BSD)


Source package jakarta-activation:
jakarta-activation: BSD -> (EPL-2.0 or BSD or GPLv2 with exceptions)

--
Marián Konček
___
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: Retiring Bottles in favor of Flatpak provided by upstream

[Daniel P . Berrangé]

On Wed, Jan 25, 2023 at 06:01:17PM +0100, Vít Ondruch wrote:
> 
> Dne 25. 01. 23 v 15:59 Josh Boyer napsal(a):
> > On Wed, Jan 25, 2023 at 5:56 AM Vít Ondruch  wrote:
> > > I am not user of Bottles so I won't complain about this particular case,
> > > but the push towards (upstream) Flatpaks is unfortunate :/
> > Can you elaborate on why you feel that way?
> 
> 
> I don't trust upstream Flatpacks. I don't trust they follow any standard
> except standard of their authors.
> 
> And I don't like Flatpacks, because their main advantage (their isolation)
> is also their biggest disadvantage. There can't be both without making
> compromises. If I am not mistaken, the isolation is also mostly myth,
> because it is disabled in most cases.

Looking at Flatpaks with both my upstream author hat and distro maintainer
hat, the main advantages I see is not the isolation. It is that they have
the potential to eliminate the massive amount of duplicated work between
every distro re-packaging the same app, and ensure more timely availablity
of new releases to end users by de-coupling from the distro release cycle.

As an upstream author, I want the latest releases of my software to be
available for users to install as quickly as possible. Distros largely
aren't satisfying that desire as well as I would like. If I rely on
distro packaging, there can 3-12 month delay before a distro gets my
new release in front of a user depending on their release cycle.
Then there is the problem of distro maintainers not packaging the app
correctly by forgetting to correctly handle/enable new build deps. Or
a distro maintainer ceases to have time to work on it, leaving users
stuck on outdated releases indefinitely. Or any one of the 3rd party
libraries my app relies on may be outdated.

Maintaining a OS distro to a high standard takes alot of resources,
and there are an uncountable number of Linux distros out there which
users may end up using, which just amplifies the amount of resources
needed. The sad thing is that they're essentially doing the same work
over and over again, just with a different package format, all to end
up delivering a user experiance that is largely identical when it
comes to the desktop interface. Except that doesn't end up being 
identical largely due to problems with keeping packaging up2date 
with limited distro resources. No one distro ends up doing it right
for every app, which is frustrating as both a user and upstream app
maintainer. 

So flatpaks have the promise of getting get of a huge amount of
duplicated effort at the application layer, allowing desktop apps
to be packaged once and run anywhere.

This shouldn't be read as saying distros don't add value. They
certainly do. The ability to curate a set of software, such that
users can choose to only install OSS packages is valuable. Users
have greater confidence of quality in the distros, even if that
is sometimes misplaced. The distro maintainers have also frequently
highlighted problems to upstream wrt licensing of code.  The distros
have driven the security response processes to vulnerabilities too,
which is especially valuable for the long tail of pacakges which
don't have a dedicated upstream vulnerability handling process.
There are many things distros have done well, but the amount of
effort spent by distro maintainers to achieve this is enourmous
and inefficient.


When building flatpaks, while an upstream author may be well
placed to build their own app and update it whenever there are
important changes, they may not want to keep track of all the
3rd party library deps they build on top of. The flathub.org
build gives you a base runtime, which for a GNOME app may have
90% of what you need to depend on, but there are usually still
extra libraries to add. It is desirable to be able to re-issue
application flatpaks whenever the base runtime, or any of the
extra libs get updated. The distros should be able to add value
here by providing the base runtimes, and by ensuring all likely
library deps are pre-packaged, and being able to re-issue
flatpaks anytime a dep gets updated.  This should not require
the distros to take on the job of actually writing flatpaks
for the application leaf nodes though.

Flatpaks have the promise of being able to benefit both the
upstream authors and the distro maintainers, if we can figure
out the right tradeoff. Keep the best aspects that distros
provide, while reducing the amount of work distros have to
do by avoiding need to re-package every leaf-application in
distro specific formats.

The tragedy would be if every distro ends up re-doing the
creation and shipping of flatpaks, just as they do today
with the distros specific packaging formats.

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 :|

[Bug 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Petr Pisar  changed:

   What|Removed |Added

 Blocks||2168131





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2168131
[Bug 2168131] Add perl-Gtk3-SimpleList to EPEL9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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 2168014] perl-Sereal-5.003 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168014

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Sereal-5.003-1.fc38
 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
Last Closed||2023-02-08 10:36:15



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-ca31e9deb6 has been pushed to the Fedora 38 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=2168014
___
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 2168014] perl-Sereal-5.003 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168014

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-ca31e9deb6 has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-ca31e9deb6


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168014
___
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 2168016] perl-Sereal-Encoder-5.003 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168016

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Sereal-Encoder-5.003-1
   ||.fc38
Last Closed||2023-02-08 10:18:18



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-d5734d90c9 has been pushed to the Fedora 38 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=2168016
___
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 2168016] perl-Sereal-Encoder-5.003 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168016

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-d5734d90c9 has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-d5734d90c9


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168016
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Retiring Bottles in favor of Flatpak provided by upstream

[Neal Gompa]

On Wed, Feb 8, 2023 at 5:06 AM Matthew Miller  wrote:
>
> On Wed, Jan 25, 2023 at 10:00:22AM -0800, Adam Williamson wrote:
> > No, that's the promise of Fedora Flatpaks, which is an effort with a
> > distinct identity and philosophy (but which is, uh, not being its best
> > possible self so far, I think everyone would agree). It's not the
>
> Joining this discussion late (I plead "FOSDEM"), but I want to chime in on
> this -- I do agree, and think that making that better should be a focus.
>
> Not only will this make things better on Fedora Silverblue (and others), but
> it also is a way we can expand our reach -- we can bring the benefits of
> distro packaging (with, you know, guidelines and policies and transparency
> and so on) to people who might be running a different distro underneath.
>
> (And then hopefully coax them over entirely. I mean, if they want. No
> pressure.)
>

I already know of a couple of distros considering using Fedora
Flatpaks over Flathub for three reasons:

1. All OSS
2. Transparent build
3. Multi-arch



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Retiring Bottles in favor of Flatpak provided by upstream

[Matthew Miller]

On Wed, Jan 25, 2023 at 10:00:22AM -0800, Adam Williamson wrote:
> No, that's the promise of Fedora Flatpaks, which is an effort with a
> distinct identity and philosophy (but which is, uh, not being its best
> possible self so far, I think everyone would agree). It's not the

Joining this discussion late (I plead "FOSDEM"), but I want to chime in on
this -- I do agree, and think that making that better should be a focus.

Not only will this make things better on Fedora Silverblue (and others), but
it also is a way we can expand our reach -- we can bring the benefits of
distro packaging (with, you know, guidelines and policies and transparency
and so on) to people who might be running a different distro underneath.

(And then hopefully coax them over entirely. I mean, if they want. No
pressure.)


-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2168015] perl-Sereal-Decoder-5.003 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168015

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Sereal-Decoder-5.003-1
   ||.fc38
Last Closed||2023-02-08 09:54:24



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-667cfd83e7 has been pushed to the Fedora 38 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=2168015
___
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 2168015] perl-Sereal-Decoder-5.003 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168015

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-667cfd83e7 has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-667cfd83e7


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168015
___
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

[Test-Announce] Fedora 38 Rawhide 20230208.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 38 Rawhide 20230208.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20230205.n.0: anaconda-38.19-1.fc38.src, 20230208.n.0: 
anaconda-38.21-1.fc38.src
parted - 20230205.n.0: parted-3.5-8.fc38.src, 20230208.n.0: 
parted-3.5-10.fc38.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/38

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_38_Rawhide_20230208.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230208.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230208.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230208.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230208.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230208.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Rawhide_20230208.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
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 2168142] New: Add perl-Carp-Always to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168142

Bug ID: 2168142
   Summary: Add perl-Carp-Always to EPEL9
   Product: Fedora EPEL
   Version: epel9
Status: NEW
 Component: perl-Carp-Always
  Assignee: emman...@seyman.fr
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org
Blocks: 2168128
  Target Milestone: ---
Classification: Fedora



Could you please add perl-Carp-Always to EPEL9? I need it there for
perl-Gtk3-ImageView.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2168128
[Bug 2168128] Add perl-Gtk3-ImageView to EPEL9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168142
___
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 2168141] New: Add perl-Cairo to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168141

Bug ID: 2168141
   Summary: Add perl-Cairo to EPEL9
   Product: Fedora EPEL
   Version: epel9
Status: NEW
 Component: perl-Cairo
  Assignee: spo...@gmail.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com,
perl-devel@lists.fedoraproject.org, spo...@gmail.com
Blocks: 2168128
  Target Milestone: ---
Classification: Fedora



Could you please add perl-Cairo to EPEL9? I need it there for
perl-Gtk3-ImageView.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2168128
[Bug 2168128] Add perl-Gtk3-ImageView to EPEL9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168141
___
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 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Petr Pisar  changed:

   What|Removed |Added

 Blocks||2168128





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2168128
[Bug 2168128] Add perl-Gtk3-ImageView to EPEL9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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 2168135] New: perl-URI-Title-1.904 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168135

Bug ID: 2168135
   Summary: perl-URI-Title-1.904 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-URI-Title
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.904
Upstream release that is considered latest: 1.904
Current version/release in rawhide: 1.903-1.fc38
URL: http://search.cpan.org/dist/URI-Title/

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/3487/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-URI-Title


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168135
___
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 2168132] New: Add perl-Set-IntSpan to EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2168132

Bug ID: 2168132
   Summary: Add perl-Set-IntSpan to EPEL9
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Set-IntSpan
  Assignee: rc040...@freenet.de
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
rc040...@freenet.de
Blocks: 2151714
  Target Milestone: ---
Classification: Fedora



I need perl-Set-IntSpan for gscan2pdf in EPEL9. Could you please add it there?



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2151714
[Bug 2151714] Please branch and build gscan2pdf in epel9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2168132
___
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

Inactive provenpackagers to be removed from group

[Ben Cotton]

In accordance with FESCo policy[1], the following provenpackagers will
be submitted for removal in two weeks based on a lack of Koji builds
submitted in the last six months. If you received this directly, you
can reply off-list to indicate you should still be in the
provenpackager group.

Note that removal from this group is not a "punishment" or a lack of
appreciation for the work you have done. The intent of the process is
to ensure contributors with distro-wide package privileges are still
active and responsive. This process is done regularly at the branch
point in each release.

[1] 
https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintaining_provenpackager_status

Checked 134 provenpackagers
The following 15 provenpackagers have not submitted a Koji build since
at least 2022-08-03 00:00:00:
abompard
mohanboddu
jamatos
jwboyer
till
laxathom
torsava
dwmw2
oget
otaylor
jwilson
oliver
wtogami
steve
bruno

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-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

Inactive provenpackagers to be removed from group

[Ben Cotton]

In accordance with FESCo policy[1], the following provenpackagers will
be submitted for removal in two weeks based on a lack of Koji builds
submitted in the last six months. If you received this directly, you
can reply off-list to indicate you should still be in the
provenpackager group.

Note that removal from this group is not a "punishment" or a lack of
appreciation for the work you have done. The intent of the process is
to ensure contributors with distro-wide package privileges are still
active and responsive. This process is done regularly at the branch
point in each release.

[1] 
https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintaining_provenpackager_status

Checked 134 provenpackagers
The following 15 provenpackagers have not submitted a Koji build since
at least 2022-08-03 00:00:00:
abompard
mohanboddu
jamatos
jwboyer
till
laxathom
torsava
dwmw2
oget
otaylor
jwilson
oliver
wtogami
steve
bruno

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015

Petr Pisar  changed:

   What|Removed |Added

 CC||ppi...@redhat.com
 Blocks||2151714
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Petr Pisar  ---
I need this package for gscan2pdf.
Why is this bug assigned to David when EPEL maintainer is Sergio?
I can try to maintain it there, if you are too busy. Just give me (ppisar)
access.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2151714
[Bug 2151714] Please branch and build gscan2pdf in epel9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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