[Bug 2182563] New: perl-DateTime-TimeZone-2.60 is available

[bugzilla]

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

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



Releases retrieved: 2.60
Upstream release that is considered latest: 2.60
Current version/release in rawhide: 2.59-1.fc39
URL: http://metacpan.org/dist/DateTime-TimeZone/

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


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182563
___
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 2180050] Add perl-DateTime-Format-Natural to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2180050
Bug 2180050 depends on bug 2180059, which changed state.

Bug 2180059 Summary: Add perl-Module-Util to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2180059

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2180050
___
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 2180043] Add perl-DateTime-Format-Flexible to EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-DateTime-Format-Flexib
   ||le-0.34-7.el9
 Status|ON_QA   |CLOSED
Last Closed||2023-03-29 02:29:35



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2023-c4ae467784 has been pushed to the Fedora EPEL 9 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=2180043
___
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 2179977] Add perl-DateTimeX-Easy to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2179977
Bug 2179977 depends on bug 2180043, which changed state.

Bug 2180043 Summary: Add perl-DateTime-Format-Flexible to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2180043

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2179977
___
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 2180059] Add perl-Module-Util to EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
Last Closed||2023-03-29 02:29:43



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2023-a2f4d45b7a has been pushed to the Fedora EPEL 9 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=2180059
___
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 2182227] perl-Test-Compile-3.1.1 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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

[Test-Announce] Fedora 38 Upgrade Test Day 2023-03-28

[Sumantro Mukherjee]

Hey All,

As we come closer to Fedora 38 release dates, it's time to test upgrades.
Fedora 38 has a lot of changesets and it becomes essential that we
test the graphical upgrade methods as well as the command line.
As a part of this test day[0], we will test upgrading from a full
updated, F36 and F37 to the F38 for all architectures(x86_64,ARM,aarch
64) and variants(WS,cloud,server,silverblue,IoT).

The results can be submitted here[1]

As usual, we hang out on the #fedora-test-day, should you have questions.

[0] https://fedoraproject.org/wiki/Test_Day:2023-03-28_F38_Upgrade_Test_Day
[1] https://testdays.fedoraproject.org/events/154


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

[Bug 2179500] perl-Parallel-Pipes-0.200 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Parallel-Pipes-0.200-1 |perl-Parallel-Pipes-0.200-1
   |.fc39   |.fc39
   ||perl-Parallel-Pipes-0.200-1
   ||.fc38
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2023-03-29 00:16:26



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-0b0ecf3023 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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

orphaning golang-github-exoscale-egoscale

[Carl George]

I just orphaned golang-github-exoscale-egoscale.  I'm no longer
interested in maintaining it.  It's up for grabs for any interested
parties.  Do note that currently it fails to install in F39 [0]
because one of its dependencies was retired [1], so that will need to
be sorted out to keep the package around.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=2176050
[1] 
https://src.fedoraproject.org/rpms/golang-github-deepmap-oapi-codegen/c/2792c7c77ff7815f82a942a944ccf48f0401c0a1?branch=rawhide

--
Carl George
___
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: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Kevin Fenzi]

On Mon, Mar 27, 2023 at 03:19:00PM +, Maxwell G wrote:
> On Mon Mar 27, 2023 at 07:27 -0700, Kevin Fenzi wrote:
> > On Mon, Mar 27, 2023 at 11:57:04AM -, Aleš Matěj wrote:
> 
> > > However you are right dnf can't handle that. It looks for deltas in the 
> > > same repo where it finds 
> > > the normal update package. It would require changes in dnf and libdnf.
> >
> > ok. Thanks for the info. 
> >
> > If we want to bring drpms back to useful, I think this would probibly be the
> > best way to go. Then we could have some app that creates them async and
> > dnf could use them if available.
> >
> > kevin
> 
> Can you or someone else more familiar with DRPMs than I file a dnf5 RFE?
> 
> https://github.com/rpm-software-management/dnf5/issues/new

Well, I don't know that I have any time to drive this, 
and I am not sure if it should be on dnf5 or libdnf or librepo or all of
them?

Anyhow, filed https://github.com/rpm-software-management/dnf5/issues/408

kevin


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

Re: F39 proposal: EC2 AMIs default to the gp3 EBS volume type (Self-Contained Change proposal)

[Kevin Fenzi]

On Tue, Mar 28, 2023 at 04:43:43PM -, David Duncan wrote:
> > ...snip...
> > 
> > 
> > I think this is a great idea and we should do it, but I have some
> > questions. :) 
> > 
> > We currently use 'fedimg' to upload ami images, and it currently uploads gp2
> > and 'standard' images. Do we need to then modify fedimg to upload gp3?
> > 
> 
> I am working on replacing the current version of fedimg to move from libcloud 
> to boto3. 
> The plan is to provide the updated version for this release. 

So, this change depends on that being in service?
Might add it to the change as a dependency?

kevin


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

Summary/Minutes from today's FESCo Meeting (2023-03-28)

[Zbigniew Jędrzejewski-Szmek]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting/2023-03-28/fesco.2023-03-28-17.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting/2023-03-28/fesco.2023-03-28-17.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting/2023-03-28/fesco.2023-03-28-17.00.log.html

Meeting summary
---
* init process  (zbyszek, 17:00:04)

* #2966 request new group aiven-and-friends  (zbyszek, 17:02:19)
  * The idea is approved in general and we'll try to figure out the text
of the rule outside of the meeting.  (zbyszek, 17:21:39)
  * ACTION: nirik to make a proposal  (zbyszek, 17:22:30)
  * ACTION: davide to help also  (zbyszek, 17:22:44)

* #2951 Proposal: policy for resubmitting rejected proposals  (zbyszek,
  17:23:11)
  * there is not enough support for mhroncok's amendment  (mhroncok,
17:38:42)

* Next week's chair  (zbyszek, 17:39:07)
  * ACTION: nirik will chair the next meeting  (zbyszek, 17:42:40)

* Open Floor  (zbyszek, 17:42:49)

We discussed
#2965 packit bot granted extended privileges in bodhi without FESCo approval,
but decided to close it without taking any action.

Meeting ended at 17:50:27 UTC.


Action Items

* nirik to make a proposal
* davide to help also
* nirik will chair the next 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

[EPEL-devel] From the Peanut Gallery: EPEL and Stream strategic de-dup? -- WAS: EPEL2RHEL

[Bryan Smith]

As a lurker of no note (feel free to ignore this rest of this post) I have
resisted commenting since the thread started last fall. And I'm sure
anything I post might come off as 'from the peanut gallery,' as it probably
should. I'm going 'off-topic,' but I feel it's related. And I don't envy
the EPEL maintainers, and their pains are something that most others will
never understand well.

But given the EPEL2RHEL aspect, I figured this was as good of a thread to
tangent from.

With the success of and major account buy-in of CentOS Stream, despite the
negative press due to the messaging problems (not unlike Fedora 20 years
ago), I'm really at the point I think Red Hat needs to step in,
strategically, and address this in a greater way, by support EPEL
maintainers more directly... possibly via Stream steering?

Not-so-differently than how Fedora Extras and Fedora Core were addressed
within 5 years... but, I'm probably over simplifying things.

Because even today, like I started a dozen years ago, as a RHEL consumer,
even for development systems**, I've pretty much continued to only use EPEL
on RHEL via 'includepkgs=' in YUM, now DNF, previously updated by Puppet,
now Ansible (and definitely after seeing Ansible itself upgraded to a newer
version in EPEL years ago). And so with every new RHEL Update, I ensure any
changes in those whitelists, including via Stream and Next, along with the
Update Betas.

Maybe I'm ignorant, and some of this is already in progress or at least
under consideration, but I think it would address a lot of things if CentOS
Stream and EPEL steering was more integrated, if not during the
Stream/RHEL9 lifecycle, but for 10.  I haven't been able to get away from
whitelists (includepkgs=) completely, not even with Modular (although that
has helped immensely, like with Ansible itself too).

E.g., I for one, just have to 'shake my head' when I see all the various
CentOS Stream 'repositories,' and have to ask myself... what if that effort
by Red Hat engineers was put into assisting EPEL as well, even finally
integrating them, via Modularity?

Just an observation, from the 'peanut gallery,' and I could be quite
ignorant. That and I know nothing changes overnight, but the segmentation
with EPEL doesn't have to be like CentOS was before Stream in 2019.

- bjs

**P.S. even though I still advocate everyone get a free RHEL Developer
Entitlement, and argued for it to become free even before 2014, when I was
on the inside of Red Hat (and love the recent move to 16 entitlements), so
professionals and enthusiasts alike can run actual RHEL... I'm still loving
the fact that Stream is now public, and we have standardized on Stream for
container development.

E.g., although ultimately we do deliver for RHEL, we don't let UBI limit
our considerations, and it becomes more of a 'develop what's possible' and
then evaluate whether the deliverable can run on the UBI (possibly with
library alternatives), or if a full entitlement is required (we just need
stuff not in the UBI).


-- 
Sent from my phone, apologies for any brevity as well as autocorrect
Bryan J Smith - http://linkedin.com/in/bjsmith

On Tue, Mar 28, 2023, 11:14 Carl George  wrote:

> I'm also late to the party with this feedback, but just in case it's
> not too late to include, can we include something about not updating
> the package further?  Beyond just "you do not need to take any
> action", we should advise against making any changes at that point, as
> often the RHEL package will be exactly one release higher than the
> current EPEL package, and updating the EPEL package further (either
> release or version) will screw up the upgrade path.
>
> On Mon, Mar 27, 2023 at 7:22 PM Troy Dawson  wrote:
> >
> > On Sat, Mar 25, 2023 at 12:51 PM Miro Hrončok 
> wrote:
> >>
> >> On 20. 03. 23 12:20, Neal Gompa wrote:
> >> >> I could think of other reasons as well. E.g. it's not important for
> customers
> >> >> but it's important for Red Hat. Or maybe it is a not-so-important
> dependency of
> >> >> something else.
> >> >>
> >> > Does Red Hat have any other motivation with RHEL other than a customer
> >> > needing the functionality? Those other reasons are generally driven by
> >> > someone needing it.
> >>
> >> See e.g. https://bugzilla.redhat.com/2175213
> >
> >
> > I see your point.  It sometimes also happens when the EPEL package is a
> dependency of the important package, the customers aren't actually asking
> for the EPEL package.
> > It looks like this change still hasn't been merged in so I'll see if I
> can get a change in.  How about this?
> >
> > Subject:
> > Notice:  will be automatically retired from EPEL  when
> RHEL . is released
> >
> > Comment:
> >
> > This issue is purely informational, you do not need to take any action.
> Thank you for your work maintaining  in EPEL .  Red Hat
> considers this package important enough to promote it to official RHEL.  It
> will be part of RHEL ..  When that is released, EPEL
> automation will remove  from 

Re: Anyone interested in packaging nim-lang?

[Ben Beasley]

This is just a note that nim was packaged in Fedora at one point[1], but was 
orphaned and eventually retired. There is a process[2] for reviving such a 
package; it will be similar to the process for adding a new package.

[1] https://src.fedoraproject.org/rpms/nim

[2] 
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

On Tue, Mar 28, 2023, at 7:53 AM, Ankur Sinha wrote:
> On Tue, Mar 28, 2023 17:11:06 +0530, Riya Bisht wrote:
>> Hello,
>
> Hi Riya,
>
>> I'm interested to package and maintain nim-lang. I've never used nim before 
>> but
>> i would like to start packaging for fedora. I can learn nim in the process.
>> Could you please help me to get started with this?
>
> That's great to hear!
>
> The starting point for package maintainers is here:
> https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/
>
> Language stacks can be complex to build and package, and can also be
> quite a bit of work to maintain. So, if you don't have any packaging
> experience, I'd perhaps work on a few other packages to gain a good
> understanding of the packaging pipeline before taking this on.
>
> -- 
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) | 
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London
>
> ___
> 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
>
> Attachments:
> * signature.asc
___
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: openldap: gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0

[Jun Aruga (he / him)]

All right.
Thank you for your clear answer!

Jun

On Tue, Mar 28, 2023 at 4:20 PM Dmitry Belyavskiy  wrote:
>
> Dear Jun,
>
> No, it's not a Fedora-specific issue. You try to provide a replacement
> to a system library, and this change may affect all the binaries built
> with the system area.
> You shouldn't replace or shadow the system library with your own one,
> otherwise you get PROBLEMS.
>
> On Tue, Mar 28, 2023 at 3:06 PM Jun Aruga (he / him)  
> wrote:
> >
> > Dear Dmitry,
> >
> > Thanks! The workaround worked!
> >
> > Is this issue Fedora specific?
> > Can we fix the case:
> > `LD_LIBRARY_PATH=/home/jaruga/.local/openssl-3.0.8/lib/ gdb` to work
> > by modifying the gdb or openldap patches?
> > Which is better to fix the gdb or openldap?
> >
> > Jun
> >
> > On Mon, Mar 27, 2023 at 5:45 PM Dmitry Belyavskiy  
> > wrote:
> > >
> > > Dear Jan,
> > >
> > > Yes. gdb expects system openssl (providing this function)
> > >
> > > To workaround it, you have to provide the LD_SET_LIBRARY inside gdb, via
> > > (gdb) set environment LD_LIBRARY_PATH 
> > > /home/jaruga/.local/openssl-3.0.8/lib/
> > >
> > > On Mon, Mar 27, 2023 at 5:39 PM Jun Aruga (he / him)  
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I opened this issue's ticket for openldap on Bugzilla.
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=2181668
> > > >
> > > > But let me ask on the devel@ mailing list too, as I want to debug a
> > > > program with gdb and the source-compiled openssl soon.
> > > > I am using Fedora 37. I built the openssl 3.0.8 from the source
> > > > downloading the source from https://www.openssl.org/source/ .
> > > >
> > > > ```
> > > > $ ./Configure --prefix=$HOME/.local/openssl-3.0.8 --libdir=lib shared
> > > > linux-x86_64
> > > > $ make -j4
> > > > $ make install
> > > > ```
> > > >
> > > > Then the gdb fails with the error below. Do you know why this error
> > > > happens? And is there a workaround to avoid this error?
> > > >
> > > > ```
> > > > $ rpm -qf /lib64/libldap.so.2
> > > > openldap-2.6.4-1.fc37.x86_64
> > > >
> > > > $ rpm -q gdb
> > > > gdb-13.1-1.fc37.x86_64
> > > >
> > > > $ ldd /bin/gdb | grep ldap
> > > > libldap.so.2 => /lib64/libldap.so.2 (0x7f147899a000)
> > > >
> > > > $ LD_LIBRARY_PATH=/home/jaruga/.local/openssl-3.0.8/lib/ gdb
> > > > gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol:
> > > > EVP_md2, version OPENSSL_3.0.0
> > > >
> > > > $ echo $?
> > > > 127
> > > > ```
> > > >
> > > > Thanks!
> > > >
> > > > --
> > > > Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
> > > > See  for
> > > > the timezone.
> > > > ___
> > > > 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
> > >
> > >
> > >
> > > --
> > > Dmitry Belyavskiy
> > > ___
> > > 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
> >
> >
> >
> > --
> > Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
> > See  for
> > the timezone.
> > ___
> > 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
>
>
>
> --
> Dmitry Belyavskiy
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> 

Re: F39 proposal: EC2 AMIs default to the gp3 EBS volume type (Self-Contained Change proposal)

[David Duncan]

> ...snip...
> 
> 
> I think this is a great idea and we should do it, but I have some
> questions. :) 
> 
> We currently use 'fedimg' to upload ami images, and it currently uploads gp2
> and 'standard' images. Do we need to then modify fedimg to upload gp3?
> 

I am working on replacing the current version of fedimg to move from libcloud 
to boto3. 
The plan is to provide the updated version for this release. 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?

[Carl George]

I'm also late to the party with this feedback, but just in case it's
not too late to include, can we include something about not updating
the package further?  Beyond just "you do not need to take any
action", we should advise against making any changes at that point, as
often the RHEL package will be exactly one release higher than the
current EPEL package, and updating the EPEL package further (either
release or version) will screw up the upgrade path.

On Mon, Mar 27, 2023 at 7:22 PM Troy Dawson  wrote:
>
> On Sat, Mar 25, 2023 at 12:51 PM Miro Hrončok  wrote:
>>
>> On 20. 03. 23 12:20, Neal Gompa wrote:
>> >> I could think of other reasons as well. E.g. it's not important for 
>> >> customers
>> >> but it's important for Red Hat. Or maybe it is a not-so-important 
>> >> dependency of
>> >> something else.
>> >>
>> > Does Red Hat have any other motivation with RHEL other than a customer
>> > needing the functionality? Those other reasons are generally driven by
>> > someone needing it.
>>
>> See e.g. https://bugzilla.redhat.com/2175213
>
>
> I see your point.  It sometimes also happens when the EPEL package is a 
> dependency of the important package, the customers aren't actually asking for 
> the EPEL package.
> It looks like this change still hasn't been merged in so I'll see if I can 
> get a change in.  How about this?
>
> Subject:
> Notice:  will be automatically retired from EPEL  when RHEL 
> . is released
>
> Comment:
>
> This issue is purely informational, you do not need to take any action.  
> Thank you for your work maintaining  in EPEL .  Red Hat 
> considers this package important enough to promote it to official RHEL.  It 
> will be part of RHEL ..  When that is released, EPEL automation 
> will remove  from EPEL  and close this bug.
>
> ___
> 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

[Bug 2182319] Perl YAML parser chokes on inconsistent indentation where Python does just fine.

[bugzilla]

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



--- Comment #4 from Paul Howarth  ---
So here's the problematic snippet:

  hid: [
0x05, 0x01, 0x09, 0x06, 0xa1, 0x01, 0x05, 0x07, 0x19, 0xe0, 0x29, 0xe7,
0x15, 0x00, 0x25, 0x01,
0x75, 0x01, 0x95, 0x08, 0x81, 0x02, 0x95, 0x01, 0x75, 0x08, 0x81, 0x01,
0x95, 0x05, 0x75, 0x01,
0x05, 0x08, 0x19, 0x01, 0x29, 0x05, 0x91, 0x02, 0x95, 0x01, 0x75, 0x03,
0x91, 0x01, 0x95, 0x06,
0x75, 0x08, 0x15, 0x00, 0x26, 0xff, 0x00, 0x05, 0x07, 0x19, 0x00, 0x2a,
0x97, 0x00, 0x81, 0x00,
0xc0
  ]

The closing bracket of this flow sequence is aligned with the first character
of the parent item ("hid:").

Looking here: https://www.yaml.info/learn/flowstyle.html
I see this:

=
If the line gets too long, you can wrap it:

---
perl: [5.8, 5.10, 5.12, 5.14, 5.16, 5.18, 5.20, 5.22,
  5.24, 5.26, 5.28, 5.30]

You can also put the brackets on their own lines:

---
perl: [
5.8, 5.10, 5.12, 5.14, 5.16, 5.18, 5.20, 5.22,
5.24, 5.26, 5.28, 5.30
  ]

Note that even the last closing bracket must be indented (more than the parent
block style item), so the following would be invalid:

---
perl: [
  5.8, 5.10, 5.12, 5.14, 5.16, 5.18, 5.20, 5.22,
  5.24, 5.26, 5.28, 5.30
]

You might notice that many YAML parsers accept it, though. To be compatible
with all parsers, you should indent it.
=

I also tried pasting the YAML here: https://yamlchecker.com/

It reported "deficient indentation (197:3)", again pointing to the closing
bracket.

So it would seem to me that TAML isn't being unreasonable about this, though it
could be more forgiving. Given that the upstream author suggests using YAML::XS
(see https://github.com/ingydotnet/yaml-pm), which is packaged as
perl-YAML-LibYAML by the way, I think that might be the better option for you.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182319
___
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] [Fedocal] Reminder meeting : EPEL Steering Committee

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2023-03-29 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:
This is the weekly EPEL Steering Committee Meeting.

A general agenda is the following:

#topic aloha

#topic EPEL Issues https://pagure.io/epel/issues
* https://pagure.io/epel/issues?tags=meeting=Open

#topic Old Business (if needed)

#topic General Issues / Open Floor




Source: https://calendar.fedoraproject.org//meeting/9854/

___
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

Re: SPDX migration and BSD-4-Clause

[Richard Hughes]

Ok, thanks, much appreciated!

Richard.

On Tue, 28 Mar 2023 at 15:57, Miro Hrončok  wrote:
>
> On 28. 03. 23 16:53, Richard Hughes wrote:
> > Hi all,
> >
> > I've got a package that's a mixture of BSD-3-Clause and BSD-4-Clause
> > (the original, old licence), and is current labelled "License: BSD" --
> > but I get the following:
> >
> > license-fedora2spdx BSD
> > Warning: more options on how to interpret BSD. Possible options:
> > ['BSD-1-Clause', 'BSD-2-Clause-FreeBSD', 'BSD-2-Clause-Views',
> > 'BSD-2-Clause', 'BSD-3-Clause-Modification', 'BSD-3-Clause']
> > {{pick BSD choice}}
> >
> > Is BSD-4-Clause not a valid option? Any advice welcome. Thanks!
>
> The BSD-4-Clause license was called "BSD with advertising" in Fedora, not
> "BSD", that's why license-fedora2spdx does not offer it.
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: SPDX migration and BSD-4-Clause

[Miro Hrončok]

On 28. 03. 23 16:53, Richard Hughes wrote:

Hi all,

I've got a package that's a mixture of BSD-3-Clause and BSD-4-Clause
(the original, old licence), and is current labelled "License: BSD" --
but I get the following:

license-fedora2spdx BSD
Warning: more options on how to interpret BSD. Possible options:
['BSD-1-Clause', 'BSD-2-Clause-FreeBSD', 'BSD-2-Clause-Views',
'BSD-2-Clause', 'BSD-3-Clause-Modification', 'BSD-3-Clause']
{{pick BSD choice}}

Is BSD-4-Clause not a valid option? Any advice welcome. Thanks!


The BSD-4-Clause license was called "BSD with advertising" in Fedora, not 
"BSD", that's why license-fedora2spdx does not offer it.


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

SPDX migration and BSD-4-Clause

[Richard Hughes]

Hi all,

I've got a package that's a mixture of BSD-3-Clause and BSD-4-Clause
(the original, old licence), and is current labelled "License: BSD" --
but I get the following:

license-fedora2spdx BSD
Warning: more options on how to interpret BSD. Possible options:
['BSD-1-Clause', 'BSD-2-Clause-FreeBSD', 'BSD-2-Clause-Views',
'BSD-2-Clause', 'BSD-3-Clause-Modification', 'BSD-3-Clause']
{{pick BSD choice}}

Is BSD-4-Clause not a valid option? Any advice welcome. Thanks!

Richard.
___
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 2182319] Perl YAML parser chokes on inconsistent indentation where Python does just fine.

[bugzilla]

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



--- Comment #3 from Jitka Plesnikova  ---
YAML supports only YAML 1.0.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182319
___
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: openldap: gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0

[Dmitry Belyavskiy]

Dear Jun,

No, it's not a Fedora-specific issue. You try to provide a replacement
to a system library, and this change may affect all the binaries built
with the system area.
You shouldn't replace or shadow the system library with your own one,
otherwise you get PROBLEMS.

On Tue, Mar 28, 2023 at 3:06 PM Jun Aruga (he / him)  wrote:
>
> Dear Dmitry,
>
> Thanks! The workaround worked!
>
> Is this issue Fedora specific?
> Can we fix the case:
> `LD_LIBRARY_PATH=/home/jaruga/.local/openssl-3.0.8/lib/ gdb` to work
> by modifying the gdb or openldap patches?
> Which is better to fix the gdb or openldap?
>
> Jun
>
> On Mon, Mar 27, 2023 at 5:45 PM Dmitry Belyavskiy  wrote:
> >
> > Dear Jan,
> >
> > Yes. gdb expects system openssl (providing this function)
> >
> > To workaround it, you have to provide the LD_SET_LIBRARY inside gdb, via
> > (gdb) set environment LD_LIBRARY_PATH /home/jaruga/.local/openssl-3.0.8/lib/
> >
> > On Mon, Mar 27, 2023 at 5:39 PM Jun Aruga (he / him)  
> > wrote:
> > >
> > > Hi,
> > >
> > > I opened this issue's ticket for openldap on Bugzilla.
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2181668
> > >
> > > But let me ask on the devel@ mailing list too, as I want to debug a
> > > program with gdb and the source-compiled openssl soon.
> > > I am using Fedora 37. I built the openssl 3.0.8 from the source
> > > downloading the source from https://www.openssl.org/source/ .
> > >
> > > ```
> > > $ ./Configure --prefix=$HOME/.local/openssl-3.0.8 --libdir=lib shared
> > > linux-x86_64
> > > $ make -j4
> > > $ make install
> > > ```
> > >
> > > Then the gdb fails with the error below. Do you know why this error
> > > happens? And is there a workaround to avoid this error?
> > >
> > > ```
> > > $ rpm -qf /lib64/libldap.so.2
> > > openldap-2.6.4-1.fc37.x86_64
> > >
> > > $ rpm -q gdb
> > > gdb-13.1-1.fc37.x86_64
> > >
> > > $ ldd /bin/gdb | grep ldap
> > > libldap.so.2 => /lib64/libldap.so.2 (0x7f147899a000)
> > >
> > > $ LD_LIBRARY_PATH=/home/jaruga/.local/openssl-3.0.8/lib/ gdb
> > > gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol:
> > > EVP_md2, version OPENSSL_3.0.0
> > >
> > > $ echo $?
> > > 127
> > > ```
> > >
> > > Thanks!
> > >
> > > --
> > > Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
> > > See  for
> > > the timezone.
> > > ___
> > > 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
> >
> >
> >
> > --
> > Dmitry Belyavskiy
> > ___
> > 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
>
>
>
> --
> Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
> See  for
> the timezone.
> ___
> 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



-- 
Dmitry Belyavskiy
___
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 2182319] Perl YAML parser chokes on inconsistent indentation where Python does just fine.

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 QA Contact||extras...@fedoraproject.org
   Assignee|jples...@redhat.com |p...@city-fan.org
  Component|perl-YAML-Parser|perl-YAML
 CC||mspa...@redhat.com,
   ||p...@city-fan.org,
   ||perl-devel@lists.fedoraproj
   ||ect.org, ppi...@redhat.com,
   ||st...@silug.org




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

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

[Zbigniew Jędrzejewski-Szmek]

We didn't hold a meeting for a few weeks. Let's do one today to push
some stalled subjects. Sorry for sending this out so late.

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

#2968 Change: FontAwesome 6
https://pagure.io/fesco/issue/2968
APPROVED (+7,0,-0)

= Followups =

#2966 request new group aiven-and-friends
https://pagure.io/fesco/issue/2966
https://pagure.io/fesco/issue/2929

#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

Re: Certbot 2.2.0 Update

[Jonathan Wright via devel]

2.2.0 will hit F37 and F38 stable repos tonight.

I'm holding EPEL9 back a little bit longer.

On Tue, Mar 21, 2023 at 9:21 AM Alexander Bokovoy 
wrote:

> On ti, 21 maalis 2023, Jonathan Wright via devel wrote:
> >Hi,
> >
> >I've updated Certbot to 2.2.0 in rawhide, f38, f37, and epel9.  I wanted
> to
> >email devel and seek more testing than usual for this release as I've also
> >converted the 10-15 packages to be built from a single spec instead of all
> >broken up as they were prior (ref
> >https://bugzilla.redhat.com/show_bug.cgi?id=2132123)
> >
> >If people could please update their certbot-related packages from
> >epel-testing and provide feedback here and/or karma or comments on the
> >updates in bodhi I'd be extremely grateful.
>
> Thanks. We have certbot tests in FreeIPA upstream. We run them against
> Rawhide weekly.
>
> Here is the one that was run on March 18th:
>
> http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/47908126-c5d5-11ed-84b2-fa163e02831a/report.html
>
> This one ran against certbot 2.1.0, but we'll see this Saturday how the
> tests will behave against 2.2.0.
>
> --
> / Alexander Bokovoy
> Sr. Principal Software Engineer
> Security / Identity Management Engineering
> Red Hat Limited, Finland
>
>

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: F39 proposal: SPDX License Phase 2 (System-Wide Change proposal)

[Zbigniew Jędrzejewski-Szmek]

On Thu, Mar 16, 2023 at 03:16:29PM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_2
> 
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only be implemented if approved
> by the Fedora Engineering Steering Committee.
> 
> 
> == Summary ==
> 
> Second phase of transition from using Fedora's short names for
> licenses to [https://spdx.org/licenses/ SPDX identifiers] in the
> License: field of Fedora package spec files. This phase addresses how
> to update the License: field for existing packages, including
> documenting more specific guidance on how to find licenses in a
> package.
> 
> == Owner ==
> 
> * Name: [[User:msuchy| Miroslav Suchý]], [[User:jlovejoy| Jilayne
> Lovejoy]], [[User:ngompa| Neal Gompa]], [[User:dcantrell| David
> Cantrell]], [[User:ref| Richard Fontana]], [[User:mattdm| Matthew
> Miller]]
> * Email: msu...@redhat.com, dcantr...@redhat.com, jlove...@redhat.com,
> ngomp...@gmail.com, rfont...@redhat.com
> 
> 
> == Detailed Description ==
> This is follow-up of [[Changes/SPDX_Licenses_Phase_1|Phase 1]]. During
> this phase, all remaining packages should be migrated to use SPDX
> license identifiers in the License: field of the package spec file.
> 
> So far, package maintainers have been updating their packages in
> accordance with the guidance provided at
> https://docs.fedoraproject.org/en-US/legal/update-existing-packages/
> and filing issues in the
> [https://gitlab.com/fedora/legal/fedora-license-data
> fedora-license-data repo]. Miroslav has been tracking how many
> packages that have been updated. Given the large number of packages in
> Fedora, this progress is good, but slow.
> 
> We are considering options for how to more quickly migrate, in terms
> of how much automation can be applied as opposed to taking this as an
> opportunity as a more thorough license review. Automated updating of
> Fedora legacy abbreviations to SPDX expressions is only possible to a
> limited extent due to different criteria used in each system, most
> notably the use of
> [https://docs.fedoraproject.org/en-US/legal/update-existing-packages/#_updating_existing_packages_callaway_short_name_categories
> "category" short names in the Fedora legacy system]. Also, the
> [https://docs.fedoraproject.org/en-US/legal/license-field/ policy for
> populating the License: field] has been clarified with a view to
> eliminating inconsistent guidance in past documentation, which may
> mean that a determination made in the past would be different today.
> Nonetheless, automated updates for a curated set of Fedora legacy
> abbreviations can help speed up the migration and serve as a reminder
> and helping hand to package maintainers who may have not started this
> process. If the automatic migration is not possible (e.g., needs
> clarification from legal), then a Bugzilla issue has to be created.
> 
> Plan:
> * Hold a hackfest focusing on a limited set of Fedora packages.
> Feedback from the hackfest can then be used to improve documentation
> related to updating existing packages.
> * Review of licenses for which there seems to be a one-to-one mapping
> from Fedora legacy abbreviations to SPDX identifiers to ensure
> reliable mapping. license-fedora2spdx will then be updated to use that
> curated set of mappings.
> * Packages using legacy license expressions will be automatically
> converted

You have my strong support for doing the automatic conversion wherever
possible. Thank you for working on this.

> ** The conversion will be done in waves to minimize errors in
> automation (e.g., 100 packages in the first week, 200 packages in
> another week, ...).  A pull request for the package spec file will be
> created as part of the conversion. If the maintainer does not respond
> to the pull-request within 14 days, the pull request will be merged by
> Change owners.

Hmm, that'd mean thousands of pull requests… I think if we agree to
this, it would make sense to just push a fix directly. Each pull request
ticket is a few mails, and with 8096 expected pull requests, that is
quite a lot of churn.

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

Fedora 38 compose report: 20230328.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-38-20230327.n.0
NEW: Fedora-38-20230328.n.0

= SUMMARY =
Added images:3
Dropped images:  0
Added packages:  3
Dropped packages:0
Upgraded packages:   68
Downgraded packages: 0

Size of added packages:  271.70 KiB
Size of dropped packages:0 B
Size of upgraded packages:   1.13 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   2.84 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-38-20230328.n.0.iso
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230328.n.0.iso
Image: LXQt raw-xz aarch64
Path: Spins/aarch64/images/Fedora-LXQt-38-20230328.n.0.aarch64.raw.xz

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: python-sphinx-mdinclude-0.5.3-1.fc38
Summary: Markdown extension for Sphinx
RPMs:python3-sphinx-mdinclude
Size:45.76 KiB

Package: python-trailrunner-1.3.0-2.fc38
Summary: Walk paths and run things
RPMs:python-trailrunner-doc python3-trailrunner
Size:204.10 KiB

Package: rust-timerfd-1.4.0-5.fc38
Summary: Rust interface to the Linux kernel's timerfd API
RPMs:rust-timerfd+default-devel rust-timerfd-devel
Size:21.84 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  ImageMagick-1:7.1.1.4-2.fc38
Old package:  ImageMagick-1:7.1.0.62-2.fc38
Summary:  An X application for displaying and manipulating images
RPMs: ImageMagick ImageMagick-c++ ImageMagick-c++-devel 
ImageMagick-devel ImageMagick-djvu ImageMagick-doc ImageMagick-heic 
ImageMagick-libs ImageMagick-perl
Added RPMs:   ImageMagick-heic
Size: 38.56 MiB
Size change:  166.74 KiB
Changelog:
  * Wed Mar 22 2023 S??rgio Basto  - 1:7.1.1.4-1
  - Update ImageMagick to 7.1.1.4 (#2176749)
  - Add support to libheif and add html docs

  * Thu Mar 23 2023 Kalev Lember  - 1:7.1.1.4-2
  - Fix missing epoch in ImageMagick-heic requires (#2181176)


Package:  ams-2.2.1-1.fc38
Old package:  ams-2.1.2-12.fc38
Summary:  Alsa Modular Synth, a realtime modular synthesizer
RPMs: ams
Size: 1.67 MiB
Size change:  -235.19 KiB
Changelog:
  * Sun Mar 19 2023 Guido Aulisi  - 2.2.1-1
  - Update to 2.2.1


Package:  annobin-11.14-1.fc38
Old package:  annobin-11.11-1.fc38
Summary:  Annotate and examine compiled binary files
RPMs: annobin-annocheck annobin-docs annobin-libannocheck 
annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm
Size: 4.95 MiB
Size change:  709 B
Changelog:
  * Tue Mar 21 2023 Yara Ahmad  - 11.14-1
  - Annocheck: Update message for LTO tests.  (#2177140)
  - Annocheck: Add even more code to handle another glibc function built 
without LTO.
  - Annocheck: Add code to handle another glibc function built without LTO.


Package:  awscli-1.27.88-1.fc38
Old package:  awscli-1.27.66-1.fc38
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.29 MiB
Size change:  10.04 KiB
Changelog:
  * Thu Feb 09 2023 Gwyn Ciesla  - 1.27.67-1
  - 1.27.67

  * Thu Feb 09 2023 Gwyn Ciesla  - 1.27.68-1
  - 1.27.68

  * Fri Feb 10 2023 Gwyn Ciesla  - 1.27.69-1
  - 1.27.69

  * Mon Feb 13 2023 Gwyn Ciesla  - 1.27.70-1
  - 1.27.70

  * Tue Feb 14 2023 Gwyn Ciesla  - 1.27.71-1
  - 1.27.71

  * Wed Feb 15 2023 Gwyn Ciesla  - 1.27.72-1
  - 1.27.72

  * Thu Feb 16 2023 Gwyn Ciesla  - 1.27.73-1
  - 1.27.73

  * Fri Feb 17 2023 Gwyn Ciesla  - 1.27.74-1
  - 1.27.74

  * Tue Feb 21 2023 Gwyn Ciesla  - 1.27.75-1
  - 1.27.75

  * Tue Feb 21 2023 Gwyn Ciesla  - 1.27.76-1
  - 1.27.76

  * Wed Feb 22 2023 Gwyn Ciesla  - 1.27.77-1
  - 1.27.77

  * Thu Feb 23 2023 Gwyn Ciesla  - 1.27.78-1
  - 1.27.78

  * Fri Feb 24 2023 Gwyn Ciesla  - 1.27.79-1
  - 1.27.79

  * Mon Feb 27 2023 Gwyn Ciesla  - 1.27.80-1
  - 1.27.80

  * Tue Feb 28 2023 Gwyn Ciesla  - 1.27.81-1
  - 1.27.81

  * Wed Mar 01 2023 Gwyn Ciesla  - 1.27.82-1
  - 1.27.82

  * Thu Mar 02 2023 Gwyn Ciesla  - 1.27.82-2
  - migrate to SPX license

  * Thu Mar 02 2023 Gwyn Ciesla  - 1.27.83-1
  - 1.27.83

  * Fri Mar 03 2023 Gwyn Ciesla  - 1.27.84-1
  - 1.27.84

  * Tue Mar 07 2023 Gwyn Ciesla  - 1.27.85-1
  - 1.27.85

  * Tue Mar 07 2023 Gwyn Ciesla  - 1.27.86-1
  - 1.27.86

  * Wed Mar 08 2023 Gwyn Ciesla  - 1.27.87-1
  - 1.27.87

  * Thu Mar 09 2023 Gwyn Ciesla  - 1.27.88-1
  - 1.27.88


Package:  chkconfig-1.22-1.fc38
Old package:  chkconfig-1.21-2.fc38
Summary:  A system tool for maintaining the /etc/rc*.d hierarchy
RPMs: alternatives chkconfig ntsysv
Size: 969.60 KiB
Size change:  917 B
Changelog:
  * Thu Mar 23 2023 Jan Macku  - 1.22-1
  - 1.22


Package:  cockpit-composer-45-1.fc38
Old package:  cockpit-composer-44-1.fc38
Summary:  Composer GUI for use with Cockpit
RPMs: cockpit-composer
Size: 1.93 MiB
Size change:  8.14 KiB
Changelog:
  * Wed Mar 15 2023 Packit  - 45-1
  - Update

Re: Strange hook in cloned package repositories

[Michael J Gruber]

Alternatively, rpkg could ship the hook in a more central location (which has 
exec). This would allow you to set `core.hooksPath` for your fedpkg repos, 
maybe even automatically by using something like `git config 
includeif.gitdir:~/fedora/.path ~/.config/git/config.fedora` and putting the 
hook path config there.
___
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: openldap: gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0

[Jun Aruga (he / him)]

Dear Dmitry,

Thanks! The workaround worked!

Is this issue Fedora specific?
Can we fix the case:
`LD_LIBRARY_PATH=/home/jaruga/.local/openssl-3.0.8/lib/ gdb` to work
by modifying the gdb or openldap patches?
Which is better to fix the gdb or openldap?

Jun

On Mon, Mar 27, 2023 at 5:45 PM Dmitry Belyavskiy  wrote:
>
> Dear Jan,
>
> Yes. gdb expects system openssl (providing this function)
>
> To workaround it, you have to provide the LD_SET_LIBRARY inside gdb, via
> (gdb) set environment LD_LIBRARY_PATH /home/jaruga/.local/openssl-3.0.8/lib/
>
> On Mon, Mar 27, 2023 at 5:39 PM Jun Aruga (he / him)  
> wrote:
> >
> > Hi,
> >
> > I opened this issue's ticket for openldap on Bugzilla.
> > https://bugzilla.redhat.com/show_bug.cgi?id=2181668
> >
> > But let me ask on the devel@ mailing list too, as I want to debug a
> > program with gdb and the source-compiled openssl soon.
> > I am using Fedora 37. I built the openssl 3.0.8 from the source
> > downloading the source from https://www.openssl.org/source/ .
> >
> > ```
> > $ ./Configure --prefix=$HOME/.local/openssl-3.0.8 --libdir=lib shared
> > linux-x86_64
> > $ make -j4
> > $ make install
> > ```
> >
> > Then the gdb fails with the error below. Do you know why this error
> > happens? And is there a workaround to avoid this error?
> >
> > ```
> > $ rpm -qf /lib64/libldap.so.2
> > openldap-2.6.4-1.fc37.x86_64
> >
> > $ rpm -q gdb
> > gdb-13.1-1.fc37.x86_64
> >
> > $ ldd /bin/gdb | grep ldap
> > libldap.so.2 => /lib64/libldap.so.2 (0x7f147899a000)
> >
> > $ LD_LIBRARY_PATH=/home/jaruga/.local/openssl-3.0.8/lib/ gdb
> > gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol:
> > EVP_md2, version OPENSSL_3.0.0
> >
> > $ echo $?
> > 127
> > ```
> >
> > Thanks!
> >
> > --
> > Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
> > See  for
> > the timezone.
> > ___
> > 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
>
>
>
> --
> Dmitry Belyavskiy
> ___
> 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



-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20230328.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230327.n.0
NEW: Fedora-Rawhide-20230328.n.0

= SUMMARY =
Added images:0
Dropped images:  1
Added packages:  6
Dropped packages:0
Upgraded packages:   193
Downgraded packages: 0

Size of added packages:  6.41 MiB
Size of dropped packages:0 B
Size of upgraded packages:   2.97 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20230327.n.0.iso

= ADDED PACKAGES =
Package: CFR-0.151-9.fc39
Summary: CFR - Another Java Decompiler
RPMs:CFR CFR-javadoc
Size:3.51 MiB

Package: iwyu-0.19-1.fc39
Summary: C/C++ source files #include analyzer based on clang
RPMs:iwyu
Size:2.77 MiB

Package: rust-timerfd-1.4.0-5.fc39
Summary: Rust interface to the Linux kernel's timerfd API
RPMs:rust-timerfd+default-devel rust-timerfd-devel
Size:21.84 KiB

Package: rust-userfaultfd-sys-0.4.3-1.fc39
Summary: Low-level bindings for userfaultfd functionality on Linux
RPMs:rust-userfaultfd-sys+default-devel 
rust-userfaultfd-sys+linux4_14-devel rust-userfaultfd-sys+linux5_7-devel 
rust-userfaultfd-sys-devel
Size:38.78 KiB

Package: rust-versionize_derive-0.1.5-1.fc39
Summary: Implements the Versionize derive proc macro
RPMs:rust-versionize_derive+default-devel rust-versionize_derive-devel
Size:30.80 KiB

Package: rust-vm-superio-0.7.0-1.fc39
Summary: Emulation for legacy devices
RPMs:rust-vm-superio+default-devel rust-vm-superio-devel
Size:39.41 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  ImageMagick-1:7.1.1.4-3.fc39
Old package:  ImageMagick-1:7.1.1.4-2.fc39
Summary:  An X application for displaying and manipulating images
RPMs: ImageMagick ImageMagick-c++ ImageMagick-c++-devel 
ImageMagick-devel ImageMagick-djvu ImageMagick-doc ImageMagick-heic 
ImageMagick-libs ImageMagick-perl
Size: 38.57 MiB
Size change:  2.82 KiB
Changelog:
  * Mon Mar 27 2023 Luya Tshimbalanga  - 1:7.1.1.4-3
  - Stop requiring ghostcripts-x11 upon request for security issue


Package:  Lmod-8.7.22-1.fc39
Old package:  Lmod-8.7.20-1.fc39
Summary:  Environmental Modules System in Lua
RPMs: Lmod
Size: 1.02 MiB
Size change:  1.76 KiB
Changelog:
  * Mon Mar 27 2023 Orion Poplawski  - 8.7.22-1
  - Update to 8.7.22


Package:  R-RInside-0.2.18-1.fc39
Old package:  R-RInside-0.2.17-4.fc38
Summary:  C++ Classes to Embed R in C++ (and C) Applications
RPMs: R-RInside R-RInside-devel R-RInside-examples
Size: 751.58 KiB
Size change:  -9.68 KiB
Changelog:
  * Mon Mar 27 2023 Mattias Ellert  - 0.2.18-1
  - New release 0.2.18


Package:  R-highlight-0.5.1-1.fc39
Old package:  R-highlight-0.5.0-11.fc38
Summary:  R Syntax Highlighter
RPMs: R-highlight
Size: 2.38 MiB
Size change:  -2.51 KiB
Changelog:
  * Mon Mar 27 2023 Mattias Ellert  - 0.5.1-1
  - Update to 0.5.1


Package:  R-littler-0.3.18-1.fc39
Old package:  R-littler-0.3.17-2.fc38
Summary:  littler: R at the Command-Line via 'r'
RPMs: R-littler R-littler-examples
Size: 465.93 KiB
Size change:  6.62 KiB
Changelog:
  * Mon Mar 27 2023 Mattias Ellert  - 0.3.18-1
  - New upstream release 0.3.18


Package:  abseil-cpp-20230125.1-1.fc39
Old package:  abseil-cpp-20220623.1-4.fc38
Summary:  C++ Common Libraries
RPMs: abseil-cpp abseil-cpp-devel
Size: 7.29 MiB
Size change:  865.68 KiB
Changelog:
  * Thu Feb 23 2023 Benjamin A. Beasley  - 20230125.1-1
  - Update to 20230125.1 (close RHBZ#2162638)


Package:  ags-3.6.0.46-1.fc39
Old package:  ags-3.6.0.44-1.fc39
Summary:  Engine for creating and running videogames of adventure (quest) 
genre
RPMs: ags
Size: 5.66 MiB
Size change:  11.84 KiB
Changelog:
  * Mon Mar 27 2023 Dominik Mierzejewski  - 3.6.0.46-1
  - update to 3.6.0.46 (#2179689)


Package:  arpwatch-14:3.3-15.fc39
Old package:  arpwatch-14:3.3-14.fc39
Summary:  Network monitoring tools for tracking IP addresses on a network
RPMs: arpwatch
Size: 1.34 MiB
Size change:  5.21 KiB
Changelog:
  * Sun Mar 26 2023 Benjamin A. Beasley  - 14:3.3-15
  - Generate ethercodes.dat from latest oui.csv


Package:  assertj-core-3.24.2-2.fc39
Old package:  assertj-core-3.23.1-2.fc38
Summary:  Library of assertions similar to fest-assert
RPMs: assertj-core assertj-core-javadoc
Size: 3.05 MiB
Size change:  270.72 KiB
Changelog:
  * Wed Feb 15 2023 Marian Koncek  - 3.24.2-1
  - Update to upstream version 3.24.2

  * Mon Feb 27 2023 Marian Koncek  - 3.24.2-2
  - Remove dependency on junit5-bom


Package:  awscli-1.27.100-1.fc39
Old package:  awscli-1.27.99-1.fc39
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.29 MiB
Size

[Bug 2182352] perl-Devel-CallParser-0.002-30.fc39 FTBFS: t/leximport.t fails

[bugzilla]

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



--- Comment #1 from Paul Howarth  ---
If this is still a problem by the time the Perl 5.38 rebuild comes along, we
could always work around it by dropping perl(Lexical::Sub) as a build
requirement - the failing test is optional and would be skipped in the absence
of Lexical::Sub.


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

[bugzilla]

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



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


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

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-Test-Compile-3.1.1-1.f
   ||c39
 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=2182227
___
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-Compile] PR #1: 3.1.1 bump; Package tests

[Jitka Plesnikova]

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

Merged pull-request:

``
3.1.1 bump; Package tests
``

https://src.fedoraproject.org/rpms/perl-Test-Compile/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-Test-Compile] PR #1: 3.1.1 bump; Package tests

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-Test-Compile` 
that you are following:
``
3.1.1 bump; Package tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test-Compile/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

Re: Anyone interested in packaging nim-lang?

[Ankur Sinha]

On Tue, Mar 28, 2023 17:11:06 +0530, Riya Bisht wrote:
> Hello,

Hi Riya,

> I'm interested to package and maintain nim-lang. I've never used nim before 
> but
> i would like to start packaging for fedora. I can learn nim in the process.
> Could you please help me to get started with this?

That's great to hear!

The starting point for package maintainers is here:
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/

Language stacks can be complex to build and package, and can also be
quite a bit of work to maintain. So, if you don't have any packaging
experience, I'd perhaps work on a few other packages to gain a good
understanding of the packaging pipeline before taking this on.

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


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

Re: Anyone interested in packaging nim-lang?

[Riya Bisht]

Hello,

I'm interested to package and maintain nim-lang. I've never used nim before
but i would like to start packaging for fedora. I can learn nim in the
process. Could you please help me to get started with this?

Thanks,
Regards,
Riya Bisht

On Tue, 28 Mar 2023, 4:19 pm Ankur Sinha,  wrote:

> Hi folks,
>
> One of my packages, taskopen[1], has moved to nim in the latest release.
> I'd like to update it, but I've never used nim (and don't intend to) and
> so, don't want to maintain a nim-lang stack all by myself.
>
> Any folks in the community interested in packaging and maintaining nim?
> I'll very happy to help, but I'd rather not be the primary maintainer.
>
> https://nim-lang.org/
> https://github.com/nim-lang/Nim/
>
> package manager:
> https://github.com/nim-lang/nimble
>
> [1] https://github.com/jschlatow/taskopen/blob/v2.0.1/Makefile#L31
>
>
> --
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) |
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London
> ___
> 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

[Bug 2182352] perl-Devel-CallParser-0.002-30.fc39 FTBFS: t/leximport.t fails

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

Link ID||CPAN 147376




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182352
___
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 2182352] New: perl-Devel-CallParser-0.002-30.fc39 FTBFS: t/leximport.t fails

[bugzilla]

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

Bug ID: 2182352
   Summary: perl-Devel-CallParser-0.002-30.fc39 FTBFS:
t/leximport.t fails
   Product: Fedora
   Version: rawhide
   URL: https://koschei.fedoraproject.org/package/perl-Devel-C
allParser
Status: NEW
 Component: perl-Devel-CallParser
  Assignee: jples...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, p...@city-fan.org,
perl-devel@lists.fedoraproject.org
Blocks: 2168842 (F39FTBFS,RAWHIDEFTBFS)
  Target Milestone: ---
Classification: Fedora



perl-Devel-CallParser-0.002-30.fc39 fails to build in Fedora 39 because a test
fails:

$ prove -b -I . -v t/leximport.t
t/leximport.t ..
1..5
ok 1
ok 2 - require Devel::CallParser;
ok 3
not ok 4

#   Failed test at t/leximport.t line 46.
#  got: 'syntax error at (eval 19) line 1, near "foo:"
# '
# expected: ''
not ok 5

#   Failed test at t/leximport.t line 47.
# Structures begin differing at:
#  $got = undef
# $expected = ARRAY(0x56053003c0f0)
# Looks like you failed 2 tests of 5.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/5 subtests

Test Summary Report
---
t/leximport.t (Wstat: 512 (exited 2) Tests: 5 Failed: 2)
  Failed tests:  4-5
  Non-zero exit status: 2

A difference between passing and failing build root is at
. An update of
perl-Lexical-Var from 0.009-31.fc38 to 0.010-1.fc39 is suspicious.



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=2182352
___
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

Anyone interested in packaging nim-lang?

[Ankur Sinha]

Hi folks,

One of my packages, taskopen[1], has moved to nim in the latest release.
I'd like to update it, but I've never used nim (and don't intend to) and
so, don't want to maintain a nim-lang stack all by myself.

Any folks in the community interested in packaging and maintaining nim?
I'll very happy to help, but I'd rather not be the primary maintainer.

https://nim-lang.org/
https://github.com/nim-lang/Nim/

package manager:
https://github.com/nim-lang/nimble

[1] https://github.com/jschlatow/taskopen/blob/v2.0.1/Makefile#L31


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

Upcoming Bodhi upgrade and notable change to update notes field

[Mattia Verga via devel]

Hello folks,

Bodhi will probably be upgraded to 7.1.1 before the F38 final freeze and
I want to highlight a notable change which may impact update
submissions. The change is that update notes field will now be limited
to 10k characters length.
The request came from https://github.com/fedora-infra/bodhi/issues/4982
which brought to attention that data of some updates were really huge
and may lead to DoS attacks. The 10k characters limit I chose should
have no impact for 99% of the updates. The limit is configurable in
bodhi config, personally I would have lowered that, but I preferred to
chose a high value to start with.

Most of the updates which have notes longer than 10k characters are
rawhide automatic updates which copies the RPM changelog over and over,
but there are some user created updates which would also been affected
by the new limit. I want to point out that copying the full upstream
changelogs into updates notes is not recommended.

With Bodhi 7.1.1 the webUI form will show a character counter at the
bottom of the notes input box which will help the user to check if
they're within length limits and the form will refuse to create the
update if notes exceed the limit. For CLI submitted updates, the server
will return an error and will refuse to create the update if notes
exceed the limit.

Other changes between the currently deployed Bodhi 7.0.1 and the
upcoming Bodhi 7.1.1 I encourage you to look at the upstream changelog
at https://github.com/fedora-infra/bodhi/releases

Cheers
Mattia

___
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 2182227] perl-Test-Compile-3.1.1 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 CC|jples...@redhat.com,|
   |mmasl...@redhat.com |
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182227
___
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: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Petr Pisar]

V Mon, Mar 27, 2023 at 11:46:49AM -0400, Neal Gompa napsal(a):
> On Mon, Mar 27, 2023 at 11:24 AM Fabio Valentini  wrote:
> >
> > On Mon, Mar 27, 2023 at 2:10 PM Neal Gompa  wrote:
> > >
> > > On Sun, Mar 26, 2023 at 12:27 PM Kalev Lember  
> > > wrote:
> > > >
> > > > On Sun, Mar 26, 2023 at 5:06 PM Zbigniew Jędrzejewski-Szmek 
> > > >  wrote:
> > > >>
> > > >> We should probably make it ^(/etc/|/bin/|/sbin/|/usr/bin/|/usr/sbin/). 
> > > >> Split-usr
> > > >> distros are a blast from the past, but adding the extra paths wouldn't 
> > > >> change
> > > >> anything for us, since we don't use them.
> > > >
> > > >
> > > > Please add /app/bin/ and /app/sbin/ as well to that list for flatpak 
> > > > rpm builds.
> > > >
> > >
> > > This shouldn't be needed because the buildsystem can happily pull
> > > filelists.xml. That said, this is part of the reason why we don't
> > > mandate a prefix in createrepo_c. We can't know what the prefix is
> > > going to be for RPMs for projects.
> >
> > If this is a difficult topic because different distros have different
> > expectations here, would it be possible to make this configurable
> > (either at runtime or at build time)?
> > That way createrepo_c wouldn't need to be opinionated ...
> >
> 
> Just don't anchor the regex with "^" the beginning. Then it works for 
> anything.
> 
> That is: "/bin/|/lib(|32|64|exec)/|/etc/"
> 
I don't think it's wise to match /usr/libexec which is defined as
:

/usr/libexec includes internal binaries that are not intended to be
executed directly by users or shell scripts.

-- Petr


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

Re: Strange hook in cloned package repositories

[Vitaly Zaitsev via devel]

On 27/03/2023 14:41, Fabio Valentini wrote:

It's doing new pre-push checks that were introduced in rpkg 1.66:


Thanks for the information.


As far as I know, there's no way to disable the checks for now, other
than to do "rm .git/hooks/pre-push".


Will do, because my $HOME is mounted with 'noexec,nodev,nosuid' flags 
and on every push it throws a warning:


$ git push
hint: The '.git/hooks/pre-push' hook was ignored because it's not set as 
executable.
hint: You can disable this warning with `git config advice.ignoredHook 
false`.


I think a new configuration option skip_hooks should be added to the 
~/.config/rpkg/fedpkg.conf file.


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

Re: How to generate new fedora.cert for package update

[Vitaly Zaitsev via devel]

On 27/03/2023 22:28, Andy Cress wrote:

I didn't find this when searching the guide.
Pointers?


You must use Kerberos now:

sudo dnf install fedora-packager fedora-packager-kerberos
fkinit --user $your_fas

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

Re: compiling gnome-extension with meson fails: ERROR: File null.gschema.xml does not exist.

[Martin Gansser]

Yes, it is an attempt to realise the whole thing with meson, but I have no 
experience with it at all.
Thanks for the info

Regards
Martin
___
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: SPDX Statistics - stilus annunciationis edition

[Miroslav Suchý]

Dne 27. 03. 23 v 11:45 Jonathan Wakely napsal(a):

>   License:        MIT
>
>
> Now going to https://spdx.org/licenses/ and looking for the SPDX Identifier
> shows:
>
> MIT License     MIT
>
>
> What am I supposed to do as a maintainer of libtermkey?

Double check which kind of MIT the package uses, and ensure it's the right SPDX 
identifier.

https://docs.fedoraproject.org/en-US/legal/update-existing-packages/#_mit


Right.

The more verbose answer: MIT in previous system was used for whole family of 
licenses. Under SPDX we recognize them as

'mpich2', 'libtiff', 'SMLNJ', 'SGI-B-2.0', 'NTP', 'MIT', 'MIT-open-group', 'MIT-feh', 'MIT-enna', 'MIT-Modern-Variant', 
'MIT-CMU', 'ICU', 'HPND', 'BSL-1.0', 'Adobe-Glyph'


and this list may not be even complete. You as a maintainer should check the license of your package. There is high 
chance that it will be still MIT. But it is not 100%. I, personally, use SPDX License Diff plugin to see what license it 
is https://github.com/spdx/spdx-license-diff


Once you update the package - and even if the package will have the same license string under SPDX - please add 
changelog entry https://docs.fedoraproject.org/en-US/legal/update-existing-packages/#_changelog_entry


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