Schedule for Tuesday's FESCo Meeting (2023-03-07)

[Zbigniew Jędrzejewski-Szmek]

Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
irc.libera.chat.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2023-03-07 17:00 UTC'

Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

#2959 Change: Modernize Thread Building Blocks for Fedora 39
https://pagure.io/fesco/issue/2959
APPROVED (+5,0,-0)

= Followups =

#2960 FESCo blocker bug: Popular third-party RPMs fail to install/update/remove 
in F38 due to security policies verification 
https://pagure.io/fesco/issue/2960

#2958 F38 incomplete changes: 100% complete deadline
https://pagure.io/fesco/issue/2958

#2951 Proposal: policy for resubmitting rejected proposals
https://pagure.io/fesco/issue/2951

= New business =


= Open Floor = 

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Locale-Codes] PR #22: 3.73 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Locale-Codes` that 
you are following:
``
3.73 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Locale-Codes/pull-request/22
___
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 2175955] biber-2.19 is available

[bugzilla]

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

Colin Macdonald  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Colin Macdonald  ---
I poked at this a bit: this bumps `bcfversion` to 3.10, and would need biblatex
bumped to 3.19 for the same.

BTW, thanks @Petr for the `bcfversion` requires/provides: I wouldn't have known
how to do that!  Happy to help out or test where I can.


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

[rpms/perl-Locale-Codes] PR #21: 3.73 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Locale-Codes` that you 
are following.

Merged pull-request:

``
3.73 bump
``

https://src.fedoraproject.org/rpms/perl-Locale-Codes/pull-request/21
___
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: Timeframe for EPEL retirement vs RHEL new package releases

[Carl George]

On Fri, Mar 3, 2023 at 11:57 AM Nick Howitt via epel-devel
 wrote:
>
> On 03/03/2023 15:33, Daniel P. Berrangé wrote:
>
> On Fri, Mar 03, 2023 at 06:55:46AM -0800, Troy Dawson wrote:
>
> We are currently in the middle of changing the workflow of retiring these
> packages.  We are changing it so that the package maintainer doesn't do the
> removing.  It will be automated, or semi-automated, so there is a
> consistent time when all of them are removed.
>
> That's a good idea.
>
> When do you actually remove the packages from the EPEL repository?
> It has been agreed that it will be after both Alma and Rocky have their
> latest release out.
>
> Ok, that's good, and should at least avoid breaking my upstream CI
> use case since our containers should transparently start receiving
> the 9.2 content when Alma releases their rebuilt container iamges.
>
> But how long after?
> Immediately after?  a month? 6 months?
>
> I personally am leaning towards a month after.
> Here is my reasoning.
> At the time a new RHEL release is released, we take a snapshot of the EPEL
> repo and put it in the archives.
> So all the packages that were built, and run on RHEL 9.1 are available in
> that archive.
>
> snip
>
> Anyway, if some users are still doing new installs of RHEL 9.1 (or
> compatible) after that month, then they should probably add the epel 9.1
> archive to their yum repositories.
>
> That's interesting, I didn't know about the y-stream archive
> snapshots.
>
> Is there any mileage in considering a way to make the use of the epel
> 9.1 archive automatic so users don't have risk of breakage needing manual
> reconfiguration to keep working ?
>
> eg perhaps have 2 yum repos provided and enabled by epel-release. One
> repo URL always the latest release and one repo URL always the current
> 9.x release number, with a lower priority number set. The latter repo
> initially empty of packages, but at the start of 9.2 it receives the
> snapshot of 9.1 content, and so becomes dominent over the former repo
> which will henceforth be holding 9.2 content.
>
> With regards,
> Daniel
>
> Is this one of those cases where it would be better not to use an el9 package 
> suffix but something alphanumerically lower than el9, then Redhat's packages 
> would always take priority if they come along?

Changing the disttag to sort lower will only have an effect if the
RHEL package has the exact same version and release digit as the EPEL
package.  This almost never happens in practice.  The RHEL maintainer
is much more likely to select an older version for specific reasons or
choose the same version with a higher release to provide a clean
upgrade path.

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



-- 
Carl George
___
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: Timeframe for EPEL retirement vs RHEL new package releases

[Carl George]

On Fri, Mar 3, 2023 at 9:33 AM Daniel P. Berrangé  wrote:
>
> On Fri, Mar 03, 2023 at 06:55:46AM -0800, Troy Dawson wrote:
> > We are currently in the middle of changing the workflow of retiring these
> > packages.  We are changing it so that the package maintainer doesn't do the
> > removing.  It will be automated, or semi-automated, so there is a
> > consistent time when all of them are removed.
>
> That's a good idea.
>
> > When do you actually remove the packages from the EPEL repository?
> > It has been agreed that it will be after both Alma and Rocky have their
> > latest release out.
>
> Ok, that's good, and should at least avoid breaking my upstream CI
> use case since our containers should transparently start receiving
> the 9.2 content when Alma releases their rebuilt container iamges.
>
> > But how long after?
> > Immediately after?  a month? 6 months?
> >
> > I personally am leaning towards a month after.
> > Here is my reasoning.
> > At the time a new RHEL release is released, we take a snapshot of the EPEL
> > repo and put it in the archives.
> > So all the packages that were built, and run on RHEL 9.1 are available in
> > that archive.
>
> snip
>
> > Anyway, if some users are still doing new installs of RHEL 9.1 (or
> > compatible) after that month, then they should probably add the epel 9.1
> > archive to their yum repositories.
>
> That's interesting, I didn't know about the y-stream archive
> snapshots.
>
> Is there any mileage in considering a way to make the use of the epel
> 9.1 archive automatic so users don't have risk of breakage needing manual
> reconfiguration to keep working ?

The current EPEL snapshot archives are flawed.  They are done manually
when Fedora Releng remembers.  It has happened where packages made it
into a snapshot labeled "EPEL X.Y" that were actually built against
RHEL X.Y+1.

We're actually planning a more robust and holistic approach to solving
this problem for EPEL 10.  The full proposal is over on Fedora
Discussion.  I cross posted it to this list back in November.  Last
month the EPEL Steering Committee approved the general direction of
the plan (without commiting to exact implementation details).  Please
check it out and share your thoughts.

https://discussion.fedoraproject.org/t/epel-10-proposal/44304

>
> eg perhaps have 2 yum repos provided and enabled by epel-release. One
> repo URL always the latest release and one repo URL always the current
> 9.x release number, with a lower priority number set. The latter repo
> initially empty of packages, but at the start of 9.2 it receives the
> snapshot of 9.1 content, and so becomes dominent over the former repo
> which will henceforth be holding 9.2 content.
>
> 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 :|
> ___
> 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



-- 
Carl George
___
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: Timeframe for EPEL retirement vs RHEL new package releases

[Carl George]

On Fri, Mar 3, 2023 at 9:16 AM Stephen Smoogen  wrote:
>
>
>
> On Fri, 3 Mar 2023 at 06:42, Daniel P. Berrangé  wrote:
>>
>> A few weeks back there was a little snafu (since resolved) with the
>> capstone package in EPEL.
>>
>> This package is being introduced to RHEL 9.2, and thus has been added
>> to CentOS 9 Stream repos. A bug was filed against capstone in EPEL
>> to notify that capstone should be retired when RHEL 9.2 is released:
>>
>>   https://bugzilla.redhat.com/show_bug.cgi?id=2124181
>>
>> Unfortunately the package was accidentally retired immediately rather
>> than waiting until 9.2 release. This is an easy mistake for a maintainer
>> to make when they see a bug whose title is "Remove capstone from epel9",
>> so I don't want anyone to blame the maintainer for this accident.
>>
>> Yes the comments make it clear that removal should wait until 9.2
>> release date, but I can totally understand how actions will be guided
>> by the initial bug subject if you're just skimming. It was pointed out
>> that this risk has been identified before:
>>
>>   
>> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/LUWUIN5BRPJZGVB5PIH625PFV6IBD6YO/
>>
>> and now we have a real world example of it going wrong exactly as
>> was predicted.
>>
>>
>> My bigger concern though is what happens when RHEL-9.2 is actually
>> released for real. The bug remains open and targets (immediate)
>> retirement of capstone from EPEL on / near 9.2 release date.
>>
>>
>
> This has been a problem with EPEL since its formation in EL4/EL5 timeframe. 
> The primary reason EPEL was given resources from Fedora was that 
> infrastructure and release engineering needed certain packages to run on 
> EL4/EL5 which weren't in RHEL. The primary reason most Fedora packagers put 
> packages into EPEL is as long as whatever goes on in RHEL doesn't affect what 
> they are doing day to day.
>
> In EL5, EL6 there was not a lot of rebasing and updates between y-streams but 
> packages would move from EPEL in RHEL which would require cleanup after the 
> sub-release was out. In EL7 we started to see more rebasing of the graphics 
> stack which would cause different sorts of breaking in some applications and 
> rebuilds and splits. In EL8, the trend has accelerated and the dot releases 
> may see things move in and out of RHEL breaking EPEL packages. However, 
> consumers of EPEL move at different speeds so we have some who stay on the 
> latest, and others who are way behind. These breaks in 7 and 8 had it that we 
> tried to archive off things in two different ways. After a y-stream was 
> released, EPEL-X.Y would be snapshotted to /pub/archive for people who needed 
> older things without updates. And for people to try and get ahead of the 
> curve we tried first EPEL-playground and then EPEL-next to allow things to 
> build against a newer grouping.
>
> Trying to do more for Enterprise consumers has run into several major 
> impediments.
> 1. Fedora infrastructure (builders, disk space, volunteer mirrors, engineers) 
> has been at or over capacity in trying to deal with the current Fedora 
> package set and regular releases. Most of the changes to enhance EPEL to deal 
> with slower cadences requires more dedicated time, disk space, mirrors and 
> engineer time than has been possible.
> 2. Fedora packagers are at capacity for dealing with EPEL packaging. They are 
> mostly aimed at trying to keep up with the firehose of a regular Fedora 
> release every 6 months. Trying to keep up with slower releases usually causes 
> dropped packages in both EPEL and Fedora. Trying to deal with even more 
> 'branches' than the main one for a release has been problematic.
> 3. Package dependency lists have grown exponentially which require more disk 
> space and volunteer time.
>
> * an x-stream is the major release of an EL operating system. EL9 is the X 
> stream.
> * a y-stream is the dot release which comes out every ~6 months. 9.1 is the 
> current Y stream.
> I guess there may be a 'z' stream for when some older release gets updates 
> over time (The regular mass updates to EL7.9 would be a z-stream)

My understanding is that Y-stream refers to the upcoming minor version
(a.k.a. CentOS Stream), not the current one.  Once a minor version is
publicly released in RHEL, it's referred to as a Z-stream.  The
current RHEL minor versions are the latest Z-streams.  EUS releases
are the previous Z-streams that are selected for additional security
fixes.  So when a RHEL maintainer refers to Z-stream work, they're
talking about public RHEL minor versions that are still maintained.
When they refer to Y-stream work, they're talking about work in CentOS
Stream in preparation for the next RHEL minor version.

>
> Solutions to the problems have to take all three of those impediments into 
> consideration to be done. My attempt with EPEL-playground in 8 broke down on 
> (2) Fedora packagers not having the capacity to deal with different 

[EPEL-devel] Re: Timeframe for EPEL retirement vs RHEL new package releases

[Carl George]

On Fri, Mar 3, 2023 at 5:42 AM Daniel P. Berrangé  wrote:
>
> A few weeks back there was a little snafu (since resolved) with the
> capstone package in EPEL.
>
> This package is being introduced to RHEL 9.2, and thus has been added
> to CentOS 9 Stream repos. A bug was filed against capstone in EPEL
> to notify that capstone should be retired when RHEL 9.2 is released:
>
>   https://bugzilla.redhat.com/show_bug.cgi?id=2124181
>
> Unfortunately the package was accidentally retired immediately rather
> than waiting until 9.2 release. This is an easy mistake for a maintainer
> to make when they see a bug whose title is "Remove capstone from epel9",
> so I don't want anyone to blame the maintainer for this accident.
>
> Yes the comments make it clear that removal should wait until 9.2
> release date, but I can totally understand how actions will be guided
> by the initial bug subject if you're just skimming. It was pointed out
> that this risk has been identified before:
>
>   
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/LUWUIN5BRPJZGVB5PIH625PFV6IBD6YO/
>
> and now we have a real world example of it going wrong exactly as
> was predicted.
>
>
> My bigger concern though is what happens when RHEL-9.2 is actually
> released for real. The bug remains open and targets (immediate)
> retirement of capstone from EPEL on / near 9.2 release date.
>
>
> This doesn't feel like it takes into account the real world usage of
> enterprise distributions. The kind of people/organizations who deploy
> RHEL are rarely going to rush into upgrading their deployment processes
> to use 9.2 immediately. They may have all sorts of review and testing
> processes to go through, integration of 3rd party apps and services,
> validating against hardware, before they consider starting deployment
> of RHEL 9.2.
>
> All this time they will continue deploying machines with 9.1, despite
> 9.2 being available, so won't get access to new 9.2 packages.

The only responsible way to pin to a minor version is with RHEL EUS.
Anything else is just running an outdated OS with unpatched security
vulnerabilities.  EUS is meant as a stop-gap to keep getting security
patches until you can upgrade to the next minor version. My
understanding is that it is not recommended for new deployments.

For everyone else that is pinning their OS version without updates, I
think it's acceptable to have a bit of friction associated with this
anti-pattern.  Users that choose to stay behind have multiple options
to obtain the package.  They can manually download the RPM from CentOS
Stream Koji, Fedora Koji, or the EPEL snapshot archive.  They can also
clone the distgit repo, roll back the retirement commit, and build the
RPM themselves.  Having easier access to the package is a good
incentive to get onto the current minor version of the OS.

>
> If we immediately retire capstone when 9.2 is released, aren't we
> going to break any ability to keep deploying capstone from EPEL on
> existing/new 9.1 installs ?

EPEL has never accommodated older minor versions, EUS or otherwise.
There are many EPEL packages that already do not install on older
minor versions.  When a RHEL minor version library change results in
an EPEL package being uninstallable, the maintainer typically rebuilds
the package quickly to fix installs for users on the current minor
version.  This in turn quickly breaks the installation for users
pinned on an older minor version. The current model does not allow us
to have it both ways.

>
> There is also the case of the RHEL rebuilds whose users consume EPEL
> packages. Depending how quick they are, the rebuild distros might not
> have their 9.2 rebuild ready for some days/weeks/months after RHEL-9.2
> is first available. My projects' upstream CI is all based on AlmaLinux
> and I don't want to see it broken again by premature capstone retirement
> from EPEL.

Historically, when CentOS was a rebuild, many EPEL maintainers would
wait for corresponding CentOS rebuild release before changing their
EPEL packages to work on RHEL.  This was true both for soname rebuilds
and retirements.  CentOS would usually take about a month to catch up
to RHEL minor versions.  The new rebuilds are doing much better in
this area.  Alma is routinely getting their minor versions out 1-2
days after RHEL.  The other rebuilds aren't far behind.  If we were to
delay package retirements, I don't think it's necessary to delay for
more than a few days.

>
> Unless I'm mistaken in some way, it feels like we should *NOT* sync
> the removal of packages from EPEL with their release in RHEL 9.2. It
> needs to be synced with user deployment of 9.2, which might be somewhat
> later.

This "user deployment" is not a concrete thing we can target.  For
every user that delays updating, many more are updating at their first
opportunity in order to stay current.

>
>
>
> The package added to RHEL should (must) have a newer NEVR than the
> existing package in 

[Bug 2175432] perl-Test2-Suite-0.000148 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
FEDORA-2023-7d1dc1739a has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-7d1dc1739a`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7d1dc1739a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2175432
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
FEDORA-2023-4873a45d1e has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-4873a45d1e`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-4873a45d1e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2142502
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
FEDORA-EPEL-2023-2c9039d9a0 has been pushed to the Fedora EPEL 7 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2c9039d9a0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

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

[updates]

The following builds have been pushed to Fedora EPEL 7 updates-testing

perl-Image-ExifTool-12.50-1.el7

Details about builds:



 perl-Image-ExifTool-12.50-1.el7 (FEDORA-EPEL-2023-2c9039d9a0)
 Utility for reading and writing image meta info

Update Information:

Update to 12.50 (latest stable).

ChangeLog:

* Fri Mar  3 2023 Tom Callaway  - 12.50-1
- update to latest stable (12.50)

References:

  [ 1 ] Bug #2142502 - Upgrade perl-Image-ExifTool to 12.50
https://bugzilla.redhat.com/show_bug.cgi?id=2142502


___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
FEDORA-EPEL-2023-525376725d has been pushed to the Fedora EPEL 8 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-525376725d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2142502
___
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 2155156] Please build perl-Devel-REPL for EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2023-88b95affd6 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-88b95affd6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2023-641c41da45 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-641c41da45

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158128
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
FEDORA-EPEL-2023-1f52066011 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1f52066011

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2023-01f6e74c04 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-01f6e74c04

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
FEDORA-2023-e4041fe3de has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-e4041fe3de

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-f802ff5e54 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f802ff5e54

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-0ea83b3e72 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-0ea83b3e72

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2174891
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
FEDORA-2023-cb7c541418 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-cb7c541418

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2142502
___
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 2175585] perl-Class-Method-Modifiers-2.15 is available

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-0ac3058d9c has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-0ac3058d9c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-e1a369bf26 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-e1a369bf26

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2175591
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #7 from Fedora Update System  ---
FEDORA-2023-7d950084d8 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-7d950084d8`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7d950084d8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #6 from Fedora Update System  ---
FEDORA-2023-64b6de55c4 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-64b6de55c4`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-64b6de55c4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Demi Marie Obenour]

On 3/6/23 13:38, Richard W.M. Jones wrote:
> On Sun, Mar 05, 2023 at 12:18:18AM +0100, Kevin Kofler via devel wrote:
>> David Michael wrote:
>>> - Firecracker can be built with Fedora's libc (glibc), but it is
>>> officially unsupported upstream[3].  Functionality would be harmed by
>>> not using musl, e.g. seccomp filters are not used.
>>
>> Upstream's refusal to write seccomp filters that work with glibc should be a 
>> red flag. It is definitely possible to sandbox glibc applications with 
>> seccomp, e.g., Chromium does it. It does need updates/fixes to the seccomp 
>> rules with almost every new version of glibc, but it is possible.
> 
> And since we're talking hypervisors, qemu also manages to use glibc &
> implement a seccomp filter.

Is it an allowlist or a blocklist?

Allowlists are much more secure, but require knowing about *everything* that
a program will ever execute.  Static linking makes this much easier to ensure.

IIUC the main problem with musl is the lack of NSS support, which means that
name lookups won’t work.  One option would be to split Firecracker into two
processes: a launcher that does all name lookups, and a sandboxed process that
does everything else.
-- 
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

[Bug 2175955] New: biber-2.19 is available

[bugzilla]

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

Bug ID: 2175955
   Summary: biber-2.19 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: biber
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: c...@m.fsf.org, c...@musicinmybrain.net,
jn...@redhat.com, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.19
Upstream release that is considered latest: 2.19
Current version/release in rawhide: 2.18-2.fc38
URL: http://biblatex-biber.sourceforge.net/

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


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


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

Orphaned packages looking for new maintainers

[Miro Hrončok]

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets 
retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2023-03-06.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package  (co)maintainers   Status Change

belle-sip orphan, sdgathman6 weeks ago
buildnumber-maven-plugin  orphan   1 weeks ago
coffee-script orphan, patches  2 weeks ago
emelfm2   orphan   2 weeks ago
erlang-cache_tab  bowlofeggs, erlang-maint-sig,0 weeks ago
  jcline, orphan
fbpanel   orphan   2 weeks ago
golang-github-deepmap-oapi-   go-sig, orphan   6 weeks ago
codegen
golang-github-quay-clair-4go-sig, orphan   1 weeks ago
golang-github-quay-claircore  go-sig, orphan   1 weeks ago
gtrayicon orphan   2 weeks ago
gxmessage orphan   2 weeks ago
joni  orphan   2 weeks ago
lilyterm  orphan   2 weeks ago
nim-srpm-macros   orphan   1 weeks ago
nimbusorphan   2 weeks ago
preferences-menus orphan   2 weeks ago
pulseeffects  atim, orphan 2 weeks ago
python-clikit orphan, python-packagers-sig 1 weeks ago
python-managesieveorphan   0 weeks ago
python3-pyPEG2orphan   2 weeks ago
regexxer  orphan   2 weeks ago
rubygem-coffee-script jaruga, orphan, tdawson  2 weeks ago
rubygem-coffee-script-source  orphan, tdawson  2 weeks ago
rubygem-jquery-rails  orphan   4 weeks ago
rubygem-spring-watcher-listen orphan   2 weeks ago
rubygem-uglifier  orphan   3 weeks ago
rust-prettytable-rs   orphan, rust-sig 0 weeks ago
stgit orphan   0 weeks ago
taggleorphan   3 weeks ago
termcolor orphan   1 weeks ago

The following packages require above mentioned packages:
Depending on: buildnumber-maven-plugin (1), status change: 2023-02-22 (1 weeks 
ago)
xmpcore (maintained by: cquad, jjelen)
xmpcore-5.1.2-18.fc36.src requires buildnumber-maven-plugin = 
1.3-24.fc38

Depending on: coffee-script (6), status change: 2023-02-20 (2 weeks ago)
nodejs-diagnostic-language-server (maintained by: asn, pfilipen)
		nodejs-diagnostic-language-server-1.13.0-4.fc38.src requires coffee-script = 
1.10.0-20.fc38


perl-Mojolicious-Plugin-AssetPack (maintained by: eseyman)
		perl-Mojolicious-Plugin-AssetPack-2.14-1.fc38.src requires coffee-script = 
1.10.0-20.fc38


rubygem-coffee-script-source (maintained by: orphan, tdawson)
		rubygem-coffee-script-source-1.10.0-15.fc38.noarch requires js-coffee-script 
= 1.10.0-20.fc38
		rubygem-coffee-script-source-1.10.0-15.fc38.src requires js-coffee-script = 
1.10.0-20.fc38


vim-syntastic (maintained by: mhjacks)
		vim-syntastic-coffee-3.10.0-19.fc39.noarch requires coffee-script = 
1.10.0-20.fc38


openqa (maintained by: adamwill)
		openqa-4.6^20221123gitb93eb7f-4.fc38.noarch requires 
perl(Mojolicious::Plugin::AssetPack) = 2.14
		openqa-4.6^20221123gitb93eb7f-4.fc38.src requires openqa-client = 
4.6^20221123gitb93eb7f-4.fc38, perl(Mojolicious::Plugin::AssetPack) = 2.14
		

Re: Upcoming summer time changes

[Luna Jernberg]

Hi!

Good to know that time will diff between US and EU for 2 weeks, this
email is always helpful every year :)

On 3/6/23, Ben Cotton  wrote:
> As a reminder to the community, we've reached the point in the year
> where jurisdictions around the world begin or end summer time. Be sure
> to check your recurring meetings on Fedocal[1] to make sure you know
> when you're meeting. Some meetings are set to a fixed time UTC and
> others are set to a particular time zone.
>
> A global list of time changes is available by country[2] and by
> date[3], but here are a few highlights:
>
> 13 Mar — summer time begins in Canada, parts of Mexico, and the US
> 27 Mar — summer time begins in the EU and UK
> 3 Apr — summer time begins in most of Mexico, summer time ends in Australia
>
> [1] https://calendar.fedoraproject.org/
> [2] https://www.timeanddate.com/time/dst/2023.html
> [3] https://www.timeanddate.com/time/dst/2023a.html
>
> --
> 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

Upcoming summer time changes

[Ben Cotton]

As a reminder to the community, we've reached the point in the year
where jurisdictions around the world begin or end summer time. Be sure
to check your recurring meetings on Fedocal[1] to make sure you know
when you're meeting. Some meetings are set to a fixed time UTC and
others are set to a particular time zone.

A global list of time changes is available by country[2] and by
date[3], but here are a few highlights:

13 Mar — summer time begins in Canada, parts of Mexico, and the US
27 Mar — summer time begins in the EU and UK
3 Apr — summer time begins in most of Mexico, summer time ends in Australia

[1] https://calendar.fedoraproject.org/
[2] https://www.timeanddate.com/time/dst/2023.html
[3] https://www.timeanddate.com/time/dst/2023a.html

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

Upcoming summer time changes

[Ben Cotton]

As a reminder to the community, we've reached the point in the year
where jurisdictions around the world begin or end summer time. Be sure
to check your recurring meetings on Fedocal[1] to make sure you know
when you're meeting. Some meetings are set to a fixed time UTC and
others are set to a particular time zone.

A global list of time changes is available by country[2] and by
date[3], but here are a few highlights:

13 Mar — summer time begins in Canada, parts of Mexico, and the US
27 Mar — summer time begins in the EU and UK
3 Apr — summer time begins in most of Mexico, summer time ends in Australia

[1] https://calendar.fedoraproject.org/
[2] https://www.timeanddate.com/time/dst/2023.html
[3] https://www.timeanddate.com/time/dst/2023a.html

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

Re: Firecracker microVM manager

[Kevin Kofler via devel]

Richard W.M. Jones wrote:
> And since we're talking hypervisors, qemu also manages to use glibc &
> implement a seccomp filter.

Good to know. I was not aware that qemu has a seccomp filter, that is nice.

   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

[rpms/perl-Locale-Codes] PR #21: 3.73 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Locale-Codes` that 
you are following:
``
3.73 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Locale-Codes/pull-request/21
___
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 2175914] perl-Locale-Codes-3.73 is available

[bugzilla]

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

Michal Josef Spacek  changed:

   What|Removed |Added

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



--- Comment #1 from Michal Josef Spacek  ---
Changes:

3.73  2023-03-06  sbeck
  -  NEW CODE(s)
  -  Fixed a problem with test failing on windows
 Reported in GitHub #15

For Fedora 36, 37, 38 and rawhide


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

[rpms/perl-Sub-Name] PR #1: Update license to SPDX format

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Sub-Name` that you are 
following.

Merged pull-request:

``
Update license to SPDX format
``

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

[rpms/perl-Sub-Name] PR #1: Update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Sub-Name` that you 
are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Sub-Name/pull-request/1
___
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 2175914] New: perl-Locale-Codes-3.73 is available

[bugzilla]

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

Bug ID: 2175914
   Summary: perl-Locale-Codes-3.73 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Locale-Codes
  Keywords: FutureFeature, Triaged
  Assignee: mspa...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 3.73
Upstream release that is considered latest: 3.73
Current version/release in rawhide: 3.72-3.fc38
URL: http://search.cpan.org/dist/Locale-Codes/

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


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


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

[Richard W.M. Jones]

On Sun, Mar 05, 2023 at 12:18:18AM +0100, Kevin Kofler via devel wrote:
> David Michael wrote:
> > - Firecracker can be built with Fedora's libc (glibc), but it is
> > officially unsupported upstream[3].  Functionality would be harmed by
> > not using musl, e.g. seccomp filters are not used.
> 
> Upstream's refusal to write seccomp filters that work with glibc should be a 
> red flag. It is definitely possible to sandbox glibc applications with 
> seccomp, e.g., Chromium does it. It does need updates/fixes to the seccomp 
> rules with almost every new version of glibc, but it is possible.

And since we're talking hypervisors, qemu also manages to use glibc &
implement a seccomp filter.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-SOAP-Lite] PR #2: Update license to SPDX format

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-SOAP-Lite` that you 
are following.

Merged pull-request:

``
Update license to SPDX format
``

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

[rpms/perl-SOAP-Lite] PR #2: Update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-SOAP-Lite` that 
you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-SOAP-Lite/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2175432] perl-Test2-Suite-0.000148 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2023-64b6de55c4 has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-64b6de55c4


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

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-7d1dc1739a has been submitted as an update to Fedora 37.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7d1dc1739a


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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

[rpms/perl-Test2-Suite] PR #26: 0.000148 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Test2-Suite` that you 
are following.

Merged pull-request:

``
0.000148 bump
``

https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/26
___
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

License change: python-versioneer, python-ncclient

[Ben Beasley]

Since python-versioneer was updated to 0.28 in Rawhide, its license changed 
from Public Domain (which really should have been CC0-1.0) to Unlicense. This 
reflects an upstream relicensing decision in version 0.24.

While the comments in versioneer-generated _version.py files mention only that 
they are public-domain, the README.md file in versioneer makes it clear that 
these files should be considered to fall under the same license as the 
versioneer package.

Thus, for those few packages that use the *packaged* python-versioneer to 
generate a _version.py file, that file will change from CC0-1.0 to Unlicense, 
which could affect the package license. For this reason, the license of the 
python-ncclient package changes from Apache-2.0 AND CC0-1.0 to Apache-2.0 AND 
Unlicense.

There are still many packages that contain a _version.py generated by a bundled 
older version of versioneer.py, either during the RPM build process or when 
their upstream produced the source distribution archive to upload to PyPI. 
These may still be technically CC0-1.0 for many years, until their upstreams 
eventually update versioneer and issue new releases. I note this only for 
completeness and clarity; it is, as far as I can tell, not a problem.
___
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

[rpms/perl-Test2-Suite] PR #26: 0.000148 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Test2-Suite` that 
you are following:
``
0.000148 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/26
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Test2-Suite] PR #25: 0.000148 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Test2-Suite` that you 
are following.

Merged pull-request:

``
0.000148 bump
``

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

[rpms/perl-Unicode-Collate] PR #3: Update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Unicode-Collate` 
that you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Unicode-Collate/pull-request/3
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Test2-Suite] PR #25: 0.000148 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Test2-Suite` that 
you are following:
``
0.000148 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/25
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Test2-Suite] PR #24: 0.000148 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Test2-Suite` that you 
are following.

Merged pull-request:

``
0.000148 bump
``

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

Summary/Minutes from today's Fedora Flatpak Packaging SIG Meeting (2023-03-06)

[Kalev Lember]

=
#fedora-meeting: Fedora Flatpak Packaging SIG
=


Meeting started by kalev at 15:00:19 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-03-06/flatpak-sig.2023-03-06-15.00.log.html
.



Meeting summary
---
* Init process  (kalev, 15:00:19)

* Announcements  (kalev, 15:05:25)
  * We have initial KDE 5 and 6 runtimes for KDE apps, thanks to
yselkowitz  (kalev, 15:05:34)
  * On top of that, yselkowitz converted a number of KDE apps that
Kinoite needs and a bunch more  (kalev, 15:05:37)
  * Two long standing issues with the regular (non-KDE) runtime got
fixed and we now include gnome-user-docs that's needed for Help
contents, and hunspell dictionaries  (kalev, 15:05:40)
  * we have
https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues for
tracking issues thanks to Allan  (kalev, 15:09:03)
  * LINK:

https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/a620aa46a8f83b8ed504ecda7b2478580198f340?branch=f37
is how they are synced  (kalev, 15:13:10)
  * per-user icon themes should now be available in the sandbox -

https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/dee5e14609df2f94b2dbdf92321cae126710cdbc?branch=f37
(kalev, 15:14:57)

* Fontconfig issues  (kalev, 15:16:10)
  * LINK: https://github.com/fedora-silverblue/issue-tracker/issues/305
(kalev, 15:16:12)

* KDE apps and runtimes  (kalev, 15:24:28)
  * LINK:
https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/1
(kalev, 15:24:33)
  * LINK:
https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/2
(kalev, 15:24:47)
  * LINK: https://src.fedoraproject.org/group/kde-sig > kde-sig sorry
(travier, 15:36:27)
  * LINK: https://docs.fedoraproject.org/en-US/fesco/SIG_policy/
(kalev, 15:43:46)

Meeting ended at 15:47:18 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kalev (67)
* zodbot (15)
* travier (15)
* smooge (9)
* sberg (5)
* matthiasc[m] (2)
* geraldosimiao (1)
* JanGrulich[m] (1)




Generated by `MeetBot`_ 0.4

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

[Test-Announce] Fedora-IoT 38 RC 20230306.1 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora-IoT 38 RC 20230306.1. 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

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

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-IoT_38_RC_20230306.1_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_38_RC_20230306.1_General

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 2175807] New: perl-Git-Repository-1.325-7.fc39 FTBFS: t/20-simple.t fails EDITOR tests

[bugzilla]

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

Bug ID: 2175807
   Summary: perl-Git-Repository-1.325-7.fc39 FTBFS: t/20-simple.t
fails EDITOR tests
   Product: Fedora
   Version: rawhide
   URL: https://koschei.fedoraproject.org/package/perl-Git-Rep
ository?collection=f39
Status: NEW
 Component: perl-Git-Repository
  Assignee: jpazdzi...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jpazdzi...@redhat.com,
perl-devel@lists.fedoraproject.org
Blocks: 2168842 (F39FTBFS,RAWHIDEFTBFS)
  Target Milestone: ---
Classification: Fedora



perl-Git-Repository-1.325-7.fc39 fails to build in Fedora 39 because
t/20-simple.t test fails:

t/20-simple.t .. 1/54 
#   Failed test 'git var GIT_EDITOR'
#   at t/20-simple.t line 88.
# 

#   Failed test 'Git complains about lack of smarts and editor'
#   at t/20-simple.t line 89.
# 
#   ''
# doesn't match '(?^:^fatal: Terminal is dumb, but EDITOR unset )'
# 
# Looks like you failed 2 tests of 54.
t/20-simple.t .. Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/54 subtests 
t/21-submodule.t ... Cloning into '/tmp/TiMR_SSxRH/sub'...
done. at t/21-submodule.t line 46.

A difference between passing and failing build root is at
. This is probably triggered
by upgrading git from 2.39.2-1.fc39 to 2.40.0-0.1.rc1.fc39.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2168842
[Bug 2168842] Fedora 39 FTBFS Tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2175807
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2142502
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2142502
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



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

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2142502
___
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 2142502] Upgrade perl-Image-ExifTool to 12.50

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-7d950084d8 has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7d950084d8


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

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2174891
___
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: JupyterLab finally in Fedora and the future of Jupyter Notebook

[Zbigniew Jędrzejewski-Szmek]

On Sun, Mar 05, 2023 at 04:19:41PM +0100, Miro Hrončok wrote:
> On 05. 03. 23 12:32, Lumír Balhar wrote:
> > Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to
> > update Jupyter Notebook to 7.0.0 alpha 14.
...
> > Any help testing the prereleases is appreciated.
> 
> Thank you, Lumír, for doing this!

+1

Zbyszek
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: JupyterLab finally in Fedora and the future of Jupyter Notebook

[Zbigniew Jędrzejewski-Szmek]

On Sun, Mar 05, 2023 at 04:19:41PM +0100, Miro Hrončok wrote:
> On 05. 03. 23 12:32, Lumír Balhar wrote:
> > Fedora 39 now contains JupyterLab 4.0.0 alpha 34 which allows me to
> > update Jupyter Notebook to 7.0.0 alpha 14.
...
> > Any help testing the prereleases is appreciated.
> 
> Thank you, Lumír, for doing this!

+1

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

Re: How to depend on a .so.X in RPM specs?

[Vít Ondruch]

Dne 06. 03. 23 v 14:27 Vít Ondruch napsal(a):


Dne 06. 03. 23 v 12:49 Ewoud Kohl van Wijngaarden napsal(a):
While rubygem-openscap is retired in Fedora, the Foreman project 
still packages it.


For context: rubygem-openscap can load libopenscap.so.8 and 
libopenscap.so.25 through FFI. Today we depend on a specific version, 
but every time it's bumped we go through a verification to see if the 
SO version hasn't been bumped.


At first I started with a trivial Requires: libopenscap.so.25 but 
that pulls in both openscap for i686 and x86_64. Directly depending on
libopenscap.so.25()(64bit) feels wrong, so what is the correct 
approach here? Is there some helper macro here?



https://src.fedoraproject.org/rpms/rubygem-ruby-vips/blob/rawhide/f/rubygem-ruby-vips.spec#_29-30 




BTW originaly I have tried the libffi dependency instead:

https://src.fedoraproject.org/rpms/rubygem-ruby-vips/c/79a3abbca7da4767aabdab253ac0b0f0aaac8e9a?branch=rawhide


Vít





Vít




Technically speaking I think it should depend on what rubygem-ffi can 
load, but on x86_64 that's probably 64 bit only. However, this is a 
bit out of my knowledge area.


For completeness, the discussion started in a PR:
https://github.com/theforeman/foreman-packaging/pull/9051
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


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


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

Re: How to depend on a .so.X in RPM specs?

[Vít Ondruch]

Dne 06. 03. 23 v 12:49 Ewoud Kohl van Wijngaarden napsal(a):
While rubygem-openscap is retired in Fedora, the Foreman project still 
packages it.


For context: rubygem-openscap can load libopenscap.so.8 and 
libopenscap.so.25 through FFI. Today we depend on a specific version, 
but every time it's bumped we go through a verification to see if the 
SO version hasn't been bumped.


At first I started with a trivial Requires: libopenscap.so.25 but that 
pulls in both openscap for i686 and x86_64. Directly depending on
libopenscap.so.25()(64bit) feels wrong, so what is the correct 
approach here? Is there some helper macro here?



https://src.fedoraproject.org/rpms/rubygem-ruby-vips/blob/rawhide/f/rubygem-ruby-vips.spec#_29-30


Vít




Technically speaking I think it should depend on what rubygem-ffi can 
load, but on x86_64 that's probably 64 bit only. However, this is a 
bit out of my knowledge area.


For completeness, the discussion started in a PR:
https://github.com/theforeman/foreman-packaging/pull/9051
___
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


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

[Bug 2155156] Please build perl-Devel-REPL for EPEL9

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2155156
___
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 2155156] Please build perl-Devel-REPL for EPEL9

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Devel-REPL-1.003029-5.
   ||el9
 Status|ASSIGNED|MODIFIED




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

Fedora 38 compose report: 20230306.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-38-20230305.n.0
NEW: Fedora-38-20230306.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   2
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   4.69 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -48.46 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230306.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  gdm-1:43.0-7.fc38
Old package:  gdm-1:43.0-4.fc38
Summary:  The GNOME Display Manager
RPMs: gdm gdm-devel gdm-pam-extensions-devel
Size: 4.50 MiB
Size change:  -51.78 KiB
Changelog:
  * Thu Feb 09 2023 Iker Pedrosa  - 1:43.0-5
  - Remove pam_console from service file (#188)

  * Wed Mar 01 2023 Ray Strode  - 1:43.0-6
  - Fix wayland on virt efi setups
Resolves: #2172291

  * Thu Mar 02 2023 Adam Williamson  - 43.0-7
  - Backport MR #199 to fix up a mistake in the virt efi patch


Package:  gnome-shell-extension-dash-to-dock-78-1.fc38
Old package:  gnome-shell-extension-dash-to-dock-74-2.fc38
Summary:  Dock for the Gnome Shell by mic...@gmail.com
RPMs: gnome-shell-extension-dash-to-dock
Size: 193.46 KiB
Size change:  3.32 KiB
Changelog:
  * Sat Feb 25 2023 Pablo Greco  - 76-1
  - dash-to-dock 76 (support for gnome 44)

  * Tue Feb 28 2023 Pablo Greco  - 78-1
  - dash-to-dock 78



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

[Bug 2155156] Please build perl-Devel-REPL for EPEL9

[bugzilla]

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



--- Comment #1 from Petr Pisar  ---
https://pagure.io/releng/fedora-scm-requests/issue/51804


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2155156
___
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: How to depend on a .so.X in RPM specs?

[Ewoud Kohl van Wijngaarden]

On Mon, Mar 06, 2023 at 01:27:18PM +0100, Jarek Prokop wrote:

Interesting situation.

On 3/6/23 12:49, Ewoud Kohl van Wijngaarden wrote:
While rubygem-openscap is retired in Fedora, the Foreman project 
still packages it.


For context: rubygem-openscap can load libopenscap.so.8 and 
libopenscap.so.25 through FFI. Today we depend on a specific 
version, but every time it's bumped we go through a verification to 
see if the SO version hasn't been bumped.


A bit of a tangent first.
This sounds like it could be checked via a "simple" FFI load check in 
%check section, in ruby, something like:


~~~

require 'ffi'

module Check
  extend FFI::Library
  ffi_lib 'libopenscap.so.25'
end
~~~

This will throw an exception if the .so is not available.


This is indeed pretty much how the code looks:
https://github.com/OpenSCAP/ruby-openscap/blob/master/lib/openscap/openscap.rb

So adding a verification step in %check is actually a good idea, though 
I'd also consider including the actual class rather than a mock.




At first I started with a trivial Requires: libopenscap.so.25 but 
that pulls in both openscap for i686 and x86_64. Directly depending 
on
libopenscap.so.25()(64bit) feels wrong, so what is the correct 
approach here? Is there some helper macro here?


There are *some*, but nothing universal it seems. JFTR other packages 
that require libs like this are (and make use of some _isa macros):


cross-gcc.spec
ghdl.spec
glib2.spec
julia.spec
libreoffice.spec
redhat-lsb.spec
systemd.spec
asahi-installer.spec

You can grep through all specfiles using this tar: 
https://pkgs.fedoraproject.org/repo/rpm-specs-latest.tar.xz


I'd recommend reading the systemd and Julia files as inspiration, 
those 2 seem to be doing what you are speaking of.


tl;dr those spec files indicate you need to conditionally depend on 
both, depending on whether it is 32 or 64bit build.


Those look very useful. The __isa_bits part in systemd.spec looks like 
what I've been looking for.


Technically speaking I think it should depend on what rubygem-ffi 
can load, but on x86_64 that's probably 64 bit only. However, this 
is a bit out of my knowledge area.


This could, in theory, be checked in the %check section of the package 
as I indicated above, if you add the same to BuildRequires, even if it 
won't help if openscap changes the .so version.


Will do, this has been very useful.



For completeness, the discussion started in a PR:
https://github.com/theforeman/foreman-packaging/pull/9051

___
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 2175591] perl-DBD-Pg-3.16.1 is available

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2175591
___
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: How to depend on a .so.X in RPM specs?

[Jarek Prokop]

Interesting situation.

On 3/6/23 12:49, Ewoud Kohl van Wijngaarden wrote:
While rubygem-openscap is retired in Fedora, the Foreman project still 
packages it.


For context: rubygem-openscap can load libopenscap.so.8 and 
libopenscap.so.25 through FFI. Today we depend on a specific version, 
but every time it's bumped we go through a verification to see if the 
SO version hasn't been bumped.


A bit of a tangent first.
This sounds like it could be checked via a "simple" FFI load check in 
%check section, in ruby, something like:


~~~

require 'ffi'

module Check
  extend FFI::Library
  ffi_lib 'libopenscap.so.25'
end
~~~

This will throw an exception if the .so is not available.



At first I started with a trivial Requires: libopenscap.so.25 but that 
pulls in both openscap for i686 and x86_64. Directly depending on
libopenscap.so.25()(64bit) feels wrong, so what is the correct 
approach here? Is there some helper macro here?


There are *some*, but nothing universal it seems. JFTR other packages 
that require libs like this are (and make use of some _isa macros):


cross-gcc.spec
ghdl.spec
glib2.spec
julia.spec
libreoffice.spec
redhat-lsb.spec
systemd.spec
asahi-installer.spec

You can grep through all specfiles using this tar: 
https://pkgs.fedoraproject.org/repo/rpm-specs-latest.tar.xz


I'd recommend reading the systemd and Julia files as inspiration, those 
2 seem to be doing what you are speaking of.


tl;dr those spec files indicate you need to conditionally depend on 
both, depending on whether it is 32 or 64bit build.




Technically speaking I think it should depend on what rubygem-ffi can 
load, but on x86_64 that's probably 64 bit only. However, this is a 
bit out of my knowledge area.


This could, in theory, be checked in the %check section of the package 
as I indicated above, if you add the same to BuildRequires, even if it 
won't help if openscap changes the .so version.


Regards,
Jarek



For completeness, the discussion started in a PR:
https://github.com/theforeman/foreman-packaging/pull/9051___
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: How to depend on a .so.X in RPM specs?

[Vitaly Zaitsev via devel]

On 06/03/2023 12:49, Ewoud Kohl van Wijngaarden wrote:

so what is the correct approach here?


Requires: openscap%{?_isa}

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

[Bug 2175591] perl-DBD-Pg-3.16.1 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-DBD-Pg-3.16.1-1.fc39
 Status|ASSIGNED|MODIFIED




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

How to depend on a .so.X in RPM specs?

[Ewoud Kohl van Wijngaarden]

While rubygem-openscap is retired in Fedora, the Foreman project still 
packages it.


For context: rubygem-openscap can load libopenscap.so.8 and 
libopenscap.so.25 through FFI. Today we depend on a specific version, 
but every time it's bumped we go through a verification to see if the SO 
version hasn't been bumped.


At first I started with a trivial Requires: libopenscap.so.25 but that 
pulls in both openscap for i686 and x86_64. Directly depending on
libopenscap.so.25()(64bit) feels wrong, so what is the correct approach 
here? Is there some helper macro here?


Technically speaking I think it should depend on what rubygem-ffi can 
load, but on x86_64 that's probably 64 bit only. However, this is a bit 
out of my knowledge area.


For completeness, the discussion started in a PR:
https://github.com/theforeman/foreman-packaging/pull/9051
___
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

[rpms/perl-Test2-Suite] PR #24: 0.000148 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Test2-Suite` that 
you are following:
``
0.000148 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/24
___
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 2158132] Add perl-Sys-SigAction to EPEL9

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158132
___
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: Packit service not submitting builds or updates for branched / F38

[Tomas Tomecek]

Hello, just a small update. We have verified recently that Packit staging
correctly creates F38 updates now:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-b3613064bf

This will land in production tomorrow, so as of March 7th, Packit will
correctly create F38 dist-git PRs and everything else.

Fabio, thank you for giving us a list of missing updates.

Maintainers in CC, please update your f38 dist-git branches & provide bodhi
updates before the final freeze, Tue 2023-04-04, so that you have up to
date versions in Fedora 38 before the release.

In my former email, I thought that only bodhi updates are missing. That was
incorrect, f38 dist-git branch needs to be updated as well.


Tomas




On Thu, Mar 2, 2023 at 8:23 PM Tomas Tomecek  wrote:

>
>
> On Thu, Mar 2, 2023 at 4:48 PM Miro Hrončok  wrote:
>
>> On 02. 03. 23 16:06, Fabio Valentini wrote:
>> > On Thu, Mar 2, 2023 at 3:47 PM Tomas Tomecek 
>> wrote:
>> >>
>> >> Hi Fabio, answers inline below.
>> >>
>> >> On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini 
>> wrote:
>> >>>
>> >>> On Wed, Mar 1, 2023 at 5:34 PM Matej Focko  wrote:
>> >>>
>> >>> - linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38
>> >>> - osbuild-composer v75: submitted to F39, F37, F36, but not F38
>> >>> - cockpit-composer v44: submitted to F39, F37, F36, but not F38
>> >>> - gpxsee v12.1: submitted to F39, F37, F36, but not F38
>> >>> - osbuild v81: submitted to F37, F36, but not F39 or F38 (?)
>> >>> - mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38
>> >>> - osbuild-composer v76: submitted to F39, F37, F36, but not F38
>> >>
>> >>
>> >> Thank you for the list, once we get guidance on how to proceed (see
>> below), we will create those missing updates.
>> >>
>> >>> Whatever the reason, what should be done about the missing updates?
>> >>> I'll be publishing my "builds + updates missing from Fedora Branched
>> >>> report" soon anyway, so the packages will show up there either way ...
>> >>
>> >>
>> >> We as Packit have honestly the same question: what does this freeze
>> exactly mean? Should we continue creating bodhi updates?
>> >>
>> >> CCing Ben to give us guidance.
>> >
>> > The fact that a release is currently "frozen" should not affect
>> > submission of updates at all.
>> > The only difference there is how updates are pushed from "testing" to
>> > "stable" state:
>> > Updates will not be submitted to "stable" repos automatically after a
>> > few days, but only after the freeze is officially lifted.
>> >
>> > Since packager's cannot "mess this up" (it is enforced by update
>> > infrastructure), there is no reason to not build + submit updates for
>> > releases that are currently in a "freeze", especially if you are also
>> > submitting the updates to stable branches of Fedora.
>>
>> In other words: It depends. Same as with updates to stable releases.
>>
>> I'd say that if you are creating the update in stable releases, you
>> should also
>> create it in frozen/branched. Not doing it creates mess.
>>
>> However, whether or not an update is suitable for a stable release or for
>> a
>> post-Beta branched release must always be decided by the packager and
>> never by
>> a service.
>>
>
> Perfect, thanks for the explanation, Fabio and Miro.
>
> We will create the missing updates.
>
> We have already fixed this and it will be rolled out to production on Tue,
> 7th.
>
>
>>
>>
>>
>> --
>> Miro Hrončok
>> --
>> Phone: +420777974800
>> IRC: mhroncok
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>>
>
___
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

[rpms/perl-Test-Requires] PR #1: Update license to SPDX format

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Test-Requires` that 
you are following.

Merged pull-request:

``
Update license to SPDX format
``

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

[rpms/perl-Test2-Suite] PR #23: 0.000148 bump

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Test2-Suite` that you 
are following.

Merged pull-request:

``
0.000148 bump
``

https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/23
___
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 2158132] Add perl-Sys-SigAction to EPEL9

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Sys-SigAction-0.23-21.
   ||el9
 Status|ASSIGNED|MODIFIED




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

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|andr...@bawue.net   |ppi...@redhat.com



--- Comment #1 from Petr Pisar  ---
https://pagure.io/releng/fedora-scm-requests/issue/51802


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

[rpms/perl-Test-Requires] PR #1: Update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Test-Requires` 
that you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test-Requires/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Test2-Suite] PR #23: 0.000148 bump

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Test2-Suite` that 
you are following:
``
0.000148 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/23
___
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 2175432] perl-Test2-Suite-0.000148 is available

[bugzilla]

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

Michal Josef Spacek  changed:

   What|Removed |Added

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



--- Comment #2 from Michal Josef Spacek  ---
Changes:

0.000148  2023-03-05 14:59:45-08:00 America/Los_Angeles

- Fixes for refcount stuff

0.000147  2023-03-04 11:42:59-08:00 America/Los_Angeles

- Add refcount tools, and include in ::V0

0.000146  2023-03-04 11:08:10-08:00 America/Los_Angeles

- Add T2_AUTO_DUMP and T2_AUTO_DEPARSE env vars

There are API changes:
* Added autodump, which is managed by env variable, so backward compatible
(0.146)
* Added new module Test2::Tools::Refcount, which routines were added to
Test2::V0. so backward compatible (0.147 and 0.148)

I will update all versions of Fedora (36, 37, 38, rawhide) because this kind of
module is base for many others. And seems that could be ok.


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

Fedora rawhide compose report: 20230306.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230304.n.0
NEW: Fedora-Rawhide-20230306.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  12
Dropped packages:1
Upgraded packages:   272
Downgraded packages: 0

Size of added packages:  295.41 MiB
Size of dropped packages:3.93 MiB
Size of upgraded packages:   5.73 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -51.51 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20230306.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230306.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: celestia-data-1.7.0~20230223ffc806d-1.fc39
Summary: Data, models and textures for Celestia
RPMs:celestia-data
Size:280.59 MiB

Package: jupyterlab-4.0.0~a34-1.fc39
Summary: JupyterLab computational environment
RPMs:jupyterlab
Size:5.53 MiB

Package: libgit2_1.5-1.5.2-1.fc39
Summary: C implementation of the Git core methods as a library with a solid API
RPMs:libgit2_1.5 libgit2_1.5-devel
Size:4.03 MiB

Package: libunicode-0.3.0-1.fc39
Summary: Modern C++17 Unicode library
RPMs:libunicode libunicode-devel libunicode-tools
Size:1.19 MiB

Package: rust-memoffset0.7-0.7.1-1.fc39
Summary: Offset_of functionality for Rust structs
RPMs:rust-memoffset0.7+default-devel rust-memoffset0.7+unstable_const-devel 
rust-memoffset0.7-devel
Size:30.00 KiB

Package: rust-pyo3-build-config0.17-0.17.3-1.fc39
Summary: Build configuration for the PyO3 ecosystem
RPMs:rust-pyo3-build-config0.17+abi3-devel 
rust-pyo3-build-config0.17+abi3-py310-devel 
rust-pyo3-build-config0.17+abi3-py37-devel 
rust-pyo3-build-config0.17+abi3-py38-devel 
rust-pyo3-build-config0.17+abi3-py39-devel 
rust-pyo3-build-config0.17+default-devel 
rust-pyo3-build-config0.17+extension-module-devel 
rust-pyo3-build-config0.17+resolve-config-devel rust-pyo3-build-config0.17-devel
Size:92.34 KiB

Package: rust-pyo3-ffi0.17-0.17.3-1.fc39
Summary: Python-API bindings for the PyO3 ecosystem
RPMs:rust-pyo3-ffi0.17+abi3-devel rust-pyo3-ffi0.17+abi3-py310-devel 
rust-pyo3-ffi0.17+abi3-py37-devel rust-pyo3-ffi0.17+abi3-py38-devel 
rust-pyo3-ffi0.17+abi3-py39-devel rust-pyo3-ffi0.17+default-devel 
rust-pyo3-ffi0.17+extension-module-devel rust-pyo3-ffi0.17-devel
Size:134.64 KiB

Package: rust-pyo3-macros-backend0.17-0.17.3-1.fc39
Summary: Code generation for PyO3 package
RPMs:rust-pyo3-macros-backend0.17+abi3-devel 
rust-pyo3-macros-backend0.17+default-devel 
rust-pyo3-macros-backend0.17+pyproto-devel rust-pyo3-macros-backend0.17-devel
Size:77.60 KiB

Package: rust-pyo3-macros0.17-0.17.3-1.fc39
Summary: Proc macros for PyO3 package
RPMs:rust-pyo3-macros0.17+abi3-devel rust-pyo3-macros0.17+default-devel 
rust-pyo3-macros0.17+multiple-pymethods-devel 
rust-pyo3-macros0.17+pyproto-devel rust-pyo3-macros0.17-devel
Size:43.69 KiB

Package: rust-pyo3_0.17-0.17.3-1.fc39
Summary: Bindings to Python interpreter
RPMs:rust-pyo3_0.17+abi3-devel rust-pyo3_0.17+abi3-py310-devel 
rust-pyo3_0.17+abi3-py37-devel rust-pyo3_0.17+abi3-py38-devel 
rust-pyo3_0.17+abi3-py39-devel rust-pyo3_0.17+anyhow-devel 
rust-pyo3_0.17+auto-initialize-devel rust-pyo3_0.17+chrono-devel 
rust-pyo3_0.17+default-devel rust-pyo3_0.17+extension-module-devel 
rust-pyo3_0.17+eyre-devel rust-pyo3_0.17+full-devel 
rust-pyo3_0.17+hashbrown-devel rust-pyo3_0.17+indexmap-devel 
rust-pyo3_0.17+indoc-devel rust-pyo3_0.17+inventory-devel 
rust-pyo3_0.17+macros-devel rust-pyo3_0.17+multiple-pymethods-devel 
rust-pyo3_0.17+nightly-devel rust-pyo3_0.17+num-bigint-devel 
rust-pyo3_0.17+num-complex-devel rust-pyo3_0.17+pyo3-macros-devel 
rust-pyo3_0.17+pyproto-devel rust-pyo3_0.17+serde-devel 
rust-pyo3_0.17+unindent-devel rust-pyo3_0.17-devel
Size:566.12 KiB

Package: whatweb-0.5.5-4.fc39
Summary: Web scanner to identify what are the websites running
RPMs:whatweb
Size:1.36 MiB

Package: workflow-0.10.6-1.fc39
Summary: C++ parallel computing and asynchronous networking engine
RPMs:workflow workflow-devel workflow-docs
Size:1.78 MiB


= DROPPED PACKAGES =
Package: libgit2_1.3-1.3.2-1.fc38
Summary: C implementation of the Git core methods as a library with a solid API
RPMs:libgit2_1.3 libgit2_1.3-devel
Size:3.93 MiB


= UPGRADED PACKAGES =
Package:  ETL-1:1.5.1-4.fc39
Old package:  ETL-1:1.5.1-3.fc38
Summary:  Extended Template Library
RPMs: ETL-devel
Size: 307.20 KiB
Size change:  -250 B
Changelog:
  * Sun Mar 05 2023 Gwyn Ciesla  - 1:1.5.1-4
  - migrated to SPDX license


Package:  QXlsx-1.4.5-3.fc39
Old package:  QXlsx-1.4.5-2.fc38
Summary:  Excel/XLSX file reader/writer library for Qt
RPMs: QXlsx QXlsx-devel
Size: 1.72 MiB
Size change:  509 B
Changelog:
  * Sun Mar 05

[Bug 2175585] perl-Class-Method-Modifiers-2.15 is available

[bugzilla]

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



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


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

[bugzilla]

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



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


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

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 CC|dev...@gunduz.org,  |
   |jples...@redhat.com,|
   |ka...@ucw.cz,   |
   |mspa...@redhat.com, |
   |prais...@redhat.com,|
   |rhug...@redhat.com, |
   |rstr...@redhat.com, |
   |sandm...@redhat.com |
 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2175591
___
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 2175585] perl-Class-Method-Modifiers-2.15 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-Class-Method-Modifiers
   ||-2.15-1.fc39
 Status|MODIFIED|CLOSED
Last Closed||2023-03-06 09:49:37



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-e0dbc63700 has been pushed to the Fedora 39 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=2175585
___
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 2173865] Upgrade perl-Crypt-X509 to 0.55

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Crypt-X509-0.55-1.fc39
   ||perl-Crypt-X509-0.55-1.fc38
 Resolution|--- |RAWHIDE
Last Closed||2023-03-06 09:47:21



--- Comment #1 from Jitka Plesnikova  ---
Built by corsepiu


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2173865
___
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 2175585] perl-Class-Method-Modifiers-2.15 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


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

[bugzilla]

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



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


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

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-App-Nopaste-1.013-12.e
   ||l9
 Status|ASSIGNED|MODIFIED




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

[Ankur Sinha]

On Mon, Mar 06, 2023 09:29:02 +0100, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> - shaneallcroft contacted since January 11th 2023
> shaneallcroft is main admin of rpms/pyplane
> shaneallcroft has a bugzilla override on rpms/pyplane

We've not seen Shane at the Neuro-SIG meetings recently. I've cc'd the
two e-mail addresses I have for them to this one now. So hopefully
they'll get this one.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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

[Bug 2175305] perl-GraphViz-2.26 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-GraphViz-2.26-1.fc39




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

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Clipboard-0.28-7.el9




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

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #1 from Petr Pisar  ---
https://pagure.io/releng/fedora-scm-requests/issue/51801


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

Take 1 minute to help with Infra & Releng Team with a decision - closing tomorrow

[Michal Konecny]

Hi everyone,

this survey will be closed tomorrow, so you have last day to fill it. We 
will share the results once the survey will be closed. Thanks everybody 
for helping us decide.


On behalf of I Team,
Michal

On 07. 02. 23 16:24, Michal Konecny wrote:

Hi everyone,

it came to Infra & Releng Team (sub-team in CPE that is taking care of 
Fedora Infra, Fedora Release Engineering and CentOS Infra) attention 
that there is a confusion about the labels we are using for issues in 
our trackers. Namely fedora-infrastructure, releng and centos-infra. 
There was even a request to change them to something less confusing.


So we want to decide if this is really need to change, so we ask you 
to take this quick survey [0] (this is an anonymous survey, nothing is 
collected by us) to see if the change is really needed or people are 
happy with current labels.


The survey will be closed on 7th March 2023.

On behalf of I Team,
Michal

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

___
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 2172713] F39FailsToInstall: perl-Alien-pkgconf

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
 Status|MODIFIED|CLOSED
Last Closed||2023-03-06 09:08:15




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

Non-responsive packagers: sbluhm, shaneallcroft

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- sbluhm contacted since January 11th 2023
sbluhm is maintainer of rpms/apache-commons-digester
sbluhm has a bugzilla override on rpms/apache-commons-digester
sbluhm is maintainer of rpms/disruptor
sbluhm has a bugzilla override on rpms/disruptor
sbluhm is maintainer of rpms/ecj
sbluhm is maintainer of rpms/jakarta-activation
sbluhm is maintainer of rpms/jakarta-servlet
sbluhm has a bugzilla override on rpms/jakarta-servlet
sbluhm is maintainer of rpms/jaxb-api
sbluhm is maintainer of rpms/jdom
sbluhm is maintainer of rpms/mercurial
sbluhm is maintainer of rpms/mxparser
sbluhm has a bugzilla override on rpms/mxparser
sbluhm is main admin of rpms/nekohtml
  rpms/nekohtml co-maintainers: @fnasser, @mizdebsk
sbluhm has a bugzilla override on rpms/nekohtml
sbluhm is maintainer of rpms/openpgm
sbluhm is maintainer of rpms/perl-Mail-RFC822-Address
sbluhm is maintainer of rpms/python-debian
sbluhm is maintainer of rpms/python-geoip2
sbluhm is maintainer of rpms/python-maxminddb
sbluhm is maintainer of rpms/python-ws4py
sbluhm is maintainer of rpms/snakeyaml
sbluhm has a bugzilla override on rpms/snakeyaml
sbluhm is maintainer of rpms/xmlpull
sbluhm has a bugzilla override on rpms/xmlpull
sbluhm is main admin of rpms/xpp3
  rpms/xpp3 co-maintainers: @jerboaa, @mizdebsk
sbluhm has a bugzilla override on rpms/xpp3
sbluhm is maintainer of rpms/xstream
sbluhm has a bugzilla override on rpms/xstream


- shaneallcroft contacted since January 11th 2023
shaneallcroft is main admin of rpms/pyplane
shaneallcroft has a bugzilla override on rpms/pyplane


Does anyone know how to contact them?


Thanks,

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