[Bug 2181971] perl-Glib-Object-Introspection-0.050 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
FEDORA-2023-f98d2dea6c 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-f98d2dea6c`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f98d2dea6c

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=2181971
___
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 2181308] perl-DateTime-TimeZone-2.58 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
FEDORA-2023-a326f439fc 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-a326f439fc`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a326f439fc

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=2181308
___
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 2181578] perl-DateTime-TimeZone-2.59 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2023-a326f439fc 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-a326f439fc`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-a326f439fc

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=2181578
___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

[bugzilla]

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



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

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

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=2181971
___
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 2181578] perl-DateTime-TimeZone-2.59 is available

[bugzilla]

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



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

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

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=2181578
___
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 2181308] perl-DateTime-TimeZone-2.58 is available

[bugzilla]

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



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

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

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=2181308
___
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 2182064] perl-Function-Parameters-2.001006 is available

[bugzilla]

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



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

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

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=2182064
___
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 2178364] perl-ExtUtils-MakeMaker-7.68 is available

[bugzilla]

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



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

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

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=2178364
___
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 2181856] perl-Scope-Upper-0.34 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2181856
___
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 2181733] perl-Archive-Tar-3.00 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2181733
___
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 2181845] perl-ExtUtils-MakeMaker-7.70 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2181845
___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #6 from Fedora Update System  ---
FEDORA-2023-43ac6bf5f5 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-43ac6bf5f5`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-43ac6bf5f5

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=2181971
___
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 2181308] perl-DateTime-TimeZone-2.58 is available

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
FEDORA-2023-7ba355bcc4 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-7ba355bcc4`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ba355bcc4

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=2181308
___
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 2181578] perl-DateTime-TimeZone-2.59 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-7ba355bcc4 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-7ba355bcc4`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ba355bcc4

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=2181578
___
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] New: perl-Test-Compile-3.1.1 is available

[bugzilla]

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

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



Releases retrieved: 3.1.1
Upstream release that is considered latest: 3.1.1
Current version/release in rawhide: 3.1.0-3.fc38
URL: http://search.cpan.org/dist/Test-Compile/

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


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


-- 
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 CoreOS Test Week is underway

[Sumantro Mukherjee]

Hey All,

The Fedora 38 CoreOS Test Week focuses on testing FCOS based on Fedora
38. The FCOS next stream is already rebased on Fedora 38 content,
which will be coming soon to testing and stable. To prepare for the
content being promoted to other streams the Fedora CoreOS and QA teams
have organized test days on Tues, March 28, 2023 (results accepted
through Sun , 02 April). Refer to the wiki page[0] for links to the
test cases and materials you’ll need to participate.

The FCOS and QA team will meet and communicate with the community sync
on a Google Meet[1] at the beginning of test week and async over
multiple matrix/element channels. Read more about them in this
announcement[2].

[0] http://fedoraproject.org/wiki/Test_Day:Fedora_38_CoreOS
[1] https://meet.google.com/dsb-wixf-kqk
[2] 
https://lists.fedoraproject.org/archives/list/cor...@lists.fedoraproject.org/thread/YHFQBZI2CLE2VDLQQXDKKN4ZVJ4H6ICY/

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

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

[Alexander Ploumistos]

I don't think we're using that anymore. See this:
https://docs.fedoraproject.org/en-US/package-maintainers/Installing_Packager_Tools/
___
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

How to generate new fedora.cert for package update

[Andy Cress]

It has been a while, and my existing cert has expired, so when I do
   fedpkg new-sources /tmp/mypackage.tar.gz
it fails.   I need to regenerate my ~/fedora.cert.  

In the past, I went to https://admin.fedoraproject.org/accounts/user/gencert to 
generate a cert, but I cannot find the correct new location.
I didn't find this when searching the guide.  
Pointers?
___
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

Planned Outage - Server updates/reboots - 2023-03-29 21:00 UTC

[Kevin Fenzi]

There will be an outage starting at 2023-03-29 21:00UTC,
which will last approximately 5 hours.

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

date -d '2023-03-29 21:00UTC'

Reason for outage:

We will be applying updates and rebooting various servers as well as
re-installing some. Services may be up and down in the outage window and
package maintainers are advised to avoid submitting builds.

Affected Services:

Most services will be affected, but only for short times in the outage
window as servers are updated and rebooted.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/11209

Please join #fedora-admin or #fedora-noc on irc.libera.chat
or add comments to the ticket for this outage above.


signature.asc
Description: PGP signature
___
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

Planned Outage - Server updates/reboots - 2023-03-29 21:00 UTC

[Kevin Fenzi]

There will be an outage starting at 2023-03-29 21:00UTC,
which will last approximately 5 hours.

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

date -d '2023-03-29 21:00UTC'

Reason for outage:

We will be applying updates and rebooting various servers as well as
re-installing some. Services may be up and down in the outage window and
package maintainers are advised to avoid submitting builds.

Affected Services:

Most services will be affected, but only for short times in the outage
window as servers are updated and rebooted.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/11209

Please join #fedora-admin or #fedora-noc on irc.libera.chat
or add comments to the ticket for this outage above.


signature.asc
Description: PGP signature
___
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

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

[Gary Buhrmaster]

On Mon, Mar 27, 2023 at 7:22 PM Troy Dawson  wrote:

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

While I am sure that occasionally RH chooses to add
a package to RHEL just because they think it is a good
idea[0], I would expect that these days adding a
package is mostly about customer requirements[1],
even if it is an indirect requirement (even as a
dependency of a dependency of a dependency).

I think your new wording is fine.

There will of course still be a few EPEL maintainers
who will ask the question of "why now?", but those
are likely to be few enough to handle on a case by
case basis.

Thanks.



[0] Although I suspect that is not a common occurrence,
as few organizations want to add to their ongoing
support burden without something more formal than a
whim.

[1] Formal requests, or easily anticipated requests
based on industry technology directions, and/or from
the various industry advisory boards.
___
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: EPEL2RHEL - New Wording? - New Workflow?

[Troy Dawson]

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

Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Zbigniew Jędrzejewski-Szmek]

On Mon, Mar 27, 2023 at 11:46:49AM -0400, Neal Gompa wrote:
> 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 want to keep it clear that _my_ proposal is to make this narrower,
to match the packaging guidelines. The guidelines say that packages
SHOULD NOT use paths outside of /usr/bin|/usr/sbin|/etc, so any other
paths that we put in primary just make things less efficient.

And as mentioned previously, adding libs would blow up the number
of paths in primary, even though they are not useful because we
have a dependency generator.

Making this configurable is probably easier than discussing the
"correct" path endlessly. Then the setting for Fedora can easily
be made to match the guidelines. What other distros do will be up
to them.

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

[Bug 2182064] perl-Function-Parameters-2.001006 is available

[bugzilla]

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



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


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

[Clemens Lang]

Steve Dickson  wrote:


I'm trying to access kernel.org with kup
script but it does not seem to be in Fedora 37.

The only rpm I can find is kup-0.3.6-11.fc36.rpm.

What am I missing??


The package has been orphaned and retired:

  https://src.fedoraproject.org/rpms/kup

If you want to unretire and maintain it, see

  
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Orphaning_Process/#claiming_ownership_of_an_orphaned_package


--
Clemens
___
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: What happen kup in Fedora 37

[Dan Horák]

On Mon, 27 Mar 2023 11:35:43 -0400
Steve Dickson  wrote:

> Hello,
> 
> I'm trying to access kernel.org with kup
> script but it does not seem to be in Fedora 37.
> 
> The only rpm I can find is kup-0.3.6-11.fc36.rpm.
> 
> What am I missing??

no new maintainer was found for it after being orphaned, thus got
retired and removed, see
https://src.fedoraproject.org/rpms/kup/c/2e9e1f6c9c75a34801d8ea1b830591dca0635d23?branch=rawhide


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

[Bug 2182064] perl-Function-Parameters-2.001006 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-Function-Parameters-2.
   ||1.6-1.fc39
 Status|MODIFIED|CLOSED
Last Closed||2023-03-27 15:54:20



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-42b6d1a479 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=2182064
___
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 2182064] perl-Function-Parameters-2.001006 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


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

[Neal Gompa]

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




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

Re: openldap: gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0

[Dmitry Belyavskiy]

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

openldap: gdb: symbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0

[Jun Aruga (he / him)]

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

What happen kup in Fedora 37

[Steve Dickson]

Hello,

I'm trying to access kernel.org with kup
script but it does not seem to be in Fedora 37.

The only rpm I can find is kup-0.3.6-11.fc36.rpm.

What am I missing??

steved.
___
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)

[Fabio Valentini]

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

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

Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Maxwell G]

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

--
Maxwell G (@gotmax23)
Pronouns: He/They
___
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 10:32:13AM -0400, Stephen Smoogen wrote:
> Or hear me out here for this wild thought: We stop offering drpms.

yes, yes, I just wanted to know if there was a plan forward for people
interested in doing the work to support them. I am not committing to
doing that work. ;) 

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

[Stephen Smoogen]

On Mon, 27 Mar 2023 at 10:29, Kevin Fenzi  wrote:

> On Mon, Mar 27, 2023 at 11:57:04AM -, Aleš Matěj wrote:
> > > On Fri, Mar 24, 2023 at 05:25:17PM +, Mattia Verga via devel wrote:
> > > I have a few additional questions:
> > >
> > > * How does this impact zchunk? or does it?
> >
> > I also think there shouldn't be any impact on zchunk.
>
> ok. Great to hear.
>
> > > * Kind of unrealted to this change, but I'll ask here as createrepo_c
> > > folks might know off hand: Is it possible to decouple drpms from a
> repo?
> > > ie, if we had a updates repo and a completely seperate updates-drpms
> > > repo with just drpms in it, what would it take to use that? Changes in
> > > dnf I guess? but also changes in createrepo_c to generate repodata for
> a
> > > repo that was only drpms?
> >
> > Such repos can be created by createrepo_c and modifyrepo_c but it is a
> bit awkward.
> > Basically first create normal (coupled) repo and then extract the
> prestodelta.xml and drpms
> > into a new repo. Additionally createrepo_c API could be used to make it
> more straight forward.
>
> Well, I was thinking of a completely disconnected process. ie, the drpms
> are created compltely seperately from the main repo and a
> prestodelta.xml is created there in the seperate repo.
>
>
Or hear me out here for this wild thought: We stop offering drpms.



-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
___
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 11:57:04AM -, Aleš Matěj wrote:
> > On Fri, Mar 24, 2023 at 05:25:17PM +, Mattia Verga via devel wrote:
> > I have a few additional questions:
> > 
> > * How does this impact zchunk? or does it?
> 
> I also think there shouldn't be any impact on zchunk.

ok. Great to hear. 

> > * Kind of unrealted to this change, but I'll ask here as createrepo_c
> > folks might know off hand: Is it possible to decouple drpms from a repo?
> > ie, if we had a updates repo and a completely seperate updates-drpms
> > repo with just drpms in it, what would it take to use that? Changes in
> > dnf I guess? but also changes in createrepo_c to generate repodata for a
> > repo that was only drpms?
> 
> Such repos can be created by createrepo_c and modifyrepo_c but it is a bit 
> awkward.
> Basically first create normal (coupled) repo and then extract the 
> prestodelta.xml and drpms
> into a new repo. Additionally createrepo_c API could be used to make it more 
> straight forward.

Well, I was thinking of a completely disconnected process. ie, the drpms
are created compltely seperately from the main repo and a
prestodelta.xml is created there in the seperate repo.

> 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


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: compiling gnome-extension with meson fails: ERROR: File null.gschema.xml does not exist.

[Vít Ondruch]

I might be wrong, having no experience with Meson, but I think the 
culprit is in `schemas/meson.build` file. There is the second line, 
where the `jq` command is used to lookup `"settings-schema"` section in 
the `metadata.json` file, but there is not such section. This results in 
`null.gschema.xml` filename which not surprisingly does not exist.


Is that your attempt to convert to Meson? Because I can't see files such 
as `schemas/meson.build` in upstream repository.



Vít


Dne 24. 03. 23 v 16:57 Martin Gansser napsal(a):

Hi,

I would like to compile the gnome extension netspeed [1] with meson, but 
unfortunately I cannot.

If I compile the software with the following command:

/usr/bin/meson setup --buildtype=plain --prefix=/usr --libdir=/usr/lib64 
--libexecdir=/usr/libexec --bindir=/usr/bin --sbindir=/usr/sbin 
--includedir=/usr/include --datadir=/usr/share -- mandir=/usr/share/man 
--infodir=/usr/share/info --localedir=/usr/share/locale --sysconfdir=/etc 
--localstatedir=/var --sharedstatedir=/var/lib --wrap-mode=nodownload 
--auto-features=enabled . redhat-linux-build

I get the error message:

The Meson build system
Version: 1.0.1
Source dir: /home/martin/rpmbuild/BUILD/gnome-shell-extension-netspeed-32
Build dir: 
/home/martin/rpmbuild/BUILD/gnome-shell-extension-netspeed-32/redhat-linux-build
Build type: native build
Project name: gnome-shell-extension-netspeed
Project version: 32
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program sh found: YES (/usr/bin/sh)
Program jq found: YES (/usr/bin/jq)
WARNING: You should add the boolean check kwarg to the run_command call.
  It currently defaults to false,
  but it will default to true in future releases of meson.
  See also: https://github.com/mesonbuild/meson/issues/9300

schemas/meson.build:6:0: ERROR: File null.gschema.xml does not exist.

A full log can be found at 
/home/martin/rpmbuild/BUILD/gnome-shell-extension-netspeed-32/redhat-linux-build/meson-logs/meson-log.txt

[1] 
https://martinkg.fedorapeople.org/Sources/gnome-shell-extension-netspeed-32.tar.gz

thanks for any help

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


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

[Kevin Fenzi]

On Sun, Mar 26, 2023 at 04:54:37PM +, Mattia Verga via devel wrote:
> 
> So, we're using different settings for pungi config and for
> updateinfo.xml generated by Bodhi.
> 
> I don't think there's a (easy) way to have bodhi inherit configuration
> from pungi config file.
> 
> I would first suggest to "fix" Bodhi metadata generation to use the same
> compression setting (which is now XZ) for everything except EPEL7 and
> EPEL8 (with the current conditional it's using BZ2 for EPEL9 also). Then
> we can discuss about switching from XZ to ZSTD, but I think the choice
> should be mirrored on pungi side.

Sounds reasonable.

> This would be a kind of hard coded change in bodhi code. If there's a
> rationale we could modify bodhi to have those parameters set in database
> for each Release object, but does it worth the work?

I'm not sure. I suppose down the road fedora 45 or something might
change again, but we could deal with the hard coded change then, or
implement the release object thing.

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

[Bug 2181971] perl-Glib-Object-Introspection-0.050 is available

[bugzilla]

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



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


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

[bugzilla]

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



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


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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


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

[Neal H. Walfield]

Hi Zbyszek,

Thanks for the clarifications.

Neal

On Mon, 27 Mar 2023 14:32:58 +0200,
Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Mar 27, 2023 at 01:29:38PM +0200, Neal H. Walfield wrote:
> > On Mon, 27 Mar 2023 13:16:45 +0200,
> > Zbigniew Jędrzejewski-Szmek wrote:
> > > I agree. The scope of the issue is fairly narrow, and the underlying
> > > issue is an invalid signature made by the anydesk maintainers.
> > > We also have a simple command that users can use to work around
> > > the issue.
> > 
> > If you are thinking of sq-keyring-linter, that won't help here.  This
> > is not a SHA-1 issue.
> 
> I know. I mentioned neither of those two things ;)
> 
> The workaround I had in mind: add '--exclude-anydesk'.
> We don't have a good replacement for graphical users yet, but I'm
> sure we'll be able to write something up in CommonBugs before F38 is released.
> 
> > The issue (I think) is that the anydesk maintains were too aggressive
> > in what they striped when they exported the OpenPGP certificate.
> [snip]
> 
> Yes, probably. Anyway, the end result is that "based on the knowledge
> that Sequoia has, the certificate was not valid when the signature was
> made."   (This is based on your comment [1]. I'm reproducing this
> here for others.)
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c124
> 
> 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
___
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 2182064] New: perl-Function-Parameters-2.001006 is available

[bugzilla]

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

Bug ID: 2182064
   Summary: perl-Function-Parameters-2.001006 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Function-Parameters
  Keywords: FutureFeature, Triaged
  Assignee: p...@city-fan.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.001006
Upstream release that is considered latest: 2.001006
Current version/release in rawhide: 2.1.5-1.fc38
URL: http://search.cpan.org/dist/Function-Parameters/

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


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


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

[Fedora Rawhide Report]

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

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

Size of added packages:  78.06 KiB
Size of dropped packages:0 B
Size of upgraded packages:   238.53 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   571.56 KiB
Size change of downgraded packages: 0 B

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

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

= ADDED PACKAGES =
Package: python-hid-parser-0.0.3-2.fc39
Summary: Parse HID report descriptors
RPMs:python3-hid-parser
Size:57.98 KiB

Package: python-pytest-cython-0.2.1-1.fc39
Summary: Pytest plugin for testing Cython extension modules
RPMs:python3-pytest-cython
Size:20.08 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  backupninja-1.2.2-1.fc39
Old package:  backupninja-1.2.1-3.fc38
Summary:  Lightweight, extensible backup system
RPMs: backupninja
Size: 112.33 KiB
Size change:  694 B
Changelog:
  * Sat Mar 25 2023 Denis Fateyev  - 1.2.2-1
  - Update to 1.2.2 version


Package:  dh-make-2.202301-1.fc39
Old package:  dh-make-2.202204-2.fc38
Summary:  Tool that converts source archives into Debian package source
RPMs: dh-make
Size: 52.05 KiB
Size change:  -123 B
Changelog:
  * Mon Mar 27 2023 S??rgio Basto  - 2.202301-1
  - Update dh-make to 2.202301 (#2156634)


Package:  digikam-7.10.0-1.fc39
Old package:  digikam-7.9.0-6.fc39
Summary:  A digital camera accessing & photo management application
RPMs: digikam digikam-devel digikam-doc digikam-libs
Size: 94.96 MiB
Size change:  24.41 KiB
Changelog:
  * Sun Mar 26 2023 Alexey Kurov  - 7.10.0-1
  - digiKam-7.10.0
  - BR: ksanecore-devel
  - BR: libheif-devel


Package:  eccodes-2.29.0-1.fc39
Old package:  eccodes-2.28.0-1.fc39
Summary:  WMO data format decoding and encoding
RPMs: eccodes eccodes-data eccodes-devel eccodes-doc
Size: 12.23 MiB
Size change:  26.72 KiB
Changelog:
  * Sun Mar 26 2023 Jos de Kloe  - 2.29.0-1
  - Upgrade to upstream version 2.29.0
Note that the source code now uses g++ in stead of gcc for compilation.


Package:  ghc-charset-0.3.9-28.fc39
Old package:  ghc-charset-0.3.9-5.fc38
Summary:  Fast unicode character sets based on complemented PATRICIA tries
RPMs: ghc-charset ghc-charset-devel ghc-charset-doc ghc-charset-prof
Size: 2.78 MiB
Size change:  1.55 KiB
Changelog:
  * Sun Mar 26 2023 Jens Petersen  - 0.3.9-28
  - set %autorelease baserelease over f37


Package:  ghc-extensible-exceptions-0.1.1.4-39.fc39
Old package:  ghc-extensible-exceptions-0.1.1.4-37.fc38
Summary:  Extensible exceptions
RPMs: ghc-extensible-exceptions ghc-extensible-exceptions-devel 
ghc-extensible-exceptions-doc ghc-extensible-exceptions-prof
Size: 192.82 KiB
Size change:  1.30 KiB
Changelog:
  * Sun Mar 26 2023 Jens Petersen  - 0.1.1.4-39
  - bump %autorelease baserelease to upgrade from f37


Package:  ghc-graphviz-2999.20.1.0-36.fc39
Old package:  ghc-graphviz-2999.20.1.0-9.fc38
Summary:  Bindings to Graphviz for graph visualization
RPMs: ghc-graphviz ghc-graphviz-devel ghc-graphviz-doc ghc-graphviz-prof
Size: 34.20 MiB
Size change:  38.14 KiB
Changelog:
  * Sun Mar 26 2023 Jens Petersen  - 2999.20.1.0-36
  - bump %autorelease baserelease to upgrade from f37


Package:  ghc-infer-license-0.2.0-16.fc39
Old package:  ghc-infer-license-0.2.0-11.fc38
Summary:  Infer software license from a given license file
RPMs: ghc-infer-license ghc-infer-license-devel ghc-infer-license-doc 
ghc-infer-license-prof
Size: 550.30 KiB
Size change:  1.23 KiB
Changelog:
  * Sun Mar 26 2023 Jens Petersen  - 0.2.0-16
  - set %autorelease baserelease for upgrade from f37


Package:  ghc-js-flot-0.8.3-24.fc39
Old package:  ghc-js-flot-0.8.3-13.fc38
Summary:  Obtain minified flot code
RPMs: ghc-js-flot ghc-js-flot-devel ghc-js-flot-doc ghc-js-flot-prof
Size: 740.29 KiB
Size change:  1.23 KiB
Changelog:
  * Sun Mar 26 2023 Jens Petersen  - 0.8.3-24
  - set %autorelease baserelease for upgrade from f37


Package:  ghc-js-jquery-3.3.1-24.fc39
Old package:  ghc-js-jquery-3.3.1-14.fc38
Summary:  Obtain minified jQuery code
RPMs: ghc-js-jquery ghc-js-jquery-devel ghc-js-jquery-doc 
ghc-js-jquery-prof
Size: 413.43 KiB
Size change:  1.31 KiB
Changelog:
  * Sun Mar 26 2023 Jens Petersen  - 3.3.1-24
  - set %autorelease baserelease for upgrade from f37


Package:  ghc-language-ecmascript-0.19.1.0-24.fc39
Old package:  ghc-language-ecmascript-0.19.1.0-15.fc38
Sum

Re: Strange hook in cloned package repositories

[Fabio Valentini]

On Mon, Mar 27, 2023 at 2:14 PM Vitaly Zaitsev via devel
 wrote:
>
> Hello.
>
> All of the newly cloned Fedora package repositories have a strange Git
> pre-push hook.
>
> Code listing:
>
> ```
> #!/bin/bash
>
> _remote="$1"
> _url="$2"
>
> exit_code=0
> while read -r _local_ref local_sha _remote_ref _remote_sha
> do
>  command -v fedpkg >/dev/null 2>&1 || { echo >&2 "Warning: 'fedpkg'
> is missing, \
> pre-push check is omitted. See .git/hooks/pre-push"; exit 0; }
>  fedpkg pre-push-check "$local_sha"
>  ret_code=$?
>  if [ $ret_code -ne 0 ] && [ $exit_code -eq 0 ]; then
>  exit_code=$ret_code
>  fi
> done
>
> exit $exit_code
> ```
>
> What is the purpose of this hook? Is it possible to disable its
> generation for my packages?

It's doing new pre-push checks that were introduced in rpkg 1.66:
https://docs.pagure.org/rpkg/releases/1.66.html#checking-a-repo-configuration-before-git-push-with-a-git-hook-script

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

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

Re: crypto-policies

[Zbigniew Jędrzejewski-Szmek]

On Mon, Mar 27, 2023 at 01:29:38PM +0200, Neal H. Walfield wrote:
> On Mon, 27 Mar 2023 13:16:45 +0200,
> Zbigniew Jędrzejewski-Szmek wrote:
> > I agree. The scope of the issue is fairly narrow, and the underlying
> > issue is an invalid signature made by the anydesk maintainers.
> > We also have a simple command that users can use to work around
> > the issue.
> 
> If you are thinking of sq-keyring-linter, that won't help here.  This
> is not a SHA-1 issue.

I know. I mentioned neither of those two things ;)

The workaround I had in mind: add '--exclude-anydesk'.
We don't have a good replacement for graphical users yet, but I'm
sure we'll be able to write something up in CommonBugs before F38 is released.

> The issue (I think) is that the anydesk maintains were too aggressive
> in what they striped when they exported the OpenPGP certificate.
[snip]

Yes, probably. Anyway, the end result is that "based on the knowledge
that Sequoia has, the certificate was not valid when the signature was
made."   (This is based on your comment [1]. I'm reproducing this
here for others.)

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c124

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

Strange hook in cloned package repositories

[Vitaly Zaitsev via devel]

Hello.

All of the newly cloned Fedora package repositories have a strange Git 
pre-push hook.


Code listing:

```
#!/bin/bash

_remote="$1"
_url="$2"

exit_code=0
while read -r _local_ref local_sha _remote_ref _remote_sha
do
command -v fedpkg >/dev/null 2>&1 || { echo >&2 "Warning: 'fedpkg' 
is missing, \

pre-push check is omitted. See .git/hooks/pre-push"; exit 0; }
fedpkg pre-push-check "$local_sha"
ret_code=$?
if [ $ret_code -ne 0 ] && [ $exit_code -eq 0 ]; then
exit_code=$ret_code
fi
done

exit $exit_code
```

What is the purpose of this hook? Is it possible to disable its 
generation for my packages?


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

Fedora 38 compose report: 20230327.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-38-20230326.n.1
NEW: Fedora-38-20230327.n.0

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

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

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

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

= DROPPED IMAGES =
Image: LXQt raw-xz aarch64
Path: Spins/aarch64/images/Fedora-LXQt-38-20230326.n.1.aarch64.raw.xz

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  buku-4.8-1.fc38
Old package:  buku-4.7-4.fc38
Summary:  Powerful command-line bookmark manager
RPMs: buku
Size: 257.92 KiB
Size change:  1010 B
Changelog:
  * Sat Mar 18 2023 Robert-Andr?? Mauchin  - 4.8-1
  - Update to 4.8


Package:  canl-java-2.8.3-1.fc38
Old package:  canl-java-2.8.2-3.fc38
Summary:  EMI Common Authentication library - bindings for Java
RPMs: canl-java canl-java-javadoc
Size: 773.24 KiB
Size change:  -717 B
Changelog:
  * Fri Mar 17 2023 Mattias Ellert  - 2.8.3-1
  - Update to 2.8.3


Package:  celestia-data-1.7.0~20230223ffc806d-2.fc38
Old package:  celestia-data-1.7.0~20230223ffc806d-1.fc38
Summary:  Data, models and textures for Celestia
RPMs: celestia-data
Size: 280.59 MiB
Size change:  1.37 KiB
Changelog:
  * Fri Mar 17 2023 Mattia Verga  - 
1.7.0~20230223ffc806d-2
  - Change requires to celestia-common


Package:  ddgr-2.1-3.fc38
Old package:  ddgr-2.1-2.fc38
Summary:  DuckDuckGo from the terminal
RPMs: ddgr
Size: 48.05 KiB
Size change:  104 B
Changelog:
  * Wed Mar 15 2023 Zephyrus Lykos  - 2.1-3
  - Move fish completion file to vendor_completions.d


Package:  goodvibes-0.7.6-1.fc38
Old package:  goodvibes-0.7.5-2.fc38
Summary:  Lightweight Radio Player
RPMs: goodvibes
Size: 1.22 MiB
Size change:  -9.92 KiB
Changelog:
  * Sat Mar 18 2023 Robert-Andr?? Mauchin  - 0.7.6-1
  - Update to 0.7.6


Package:  gssntlmssp-1.2.0-2.fc38
Old package:  gssntlmssp-1.2.0-1.fc38
Summary:  GSSAPI NTLMSSP Mechanism
RPMs: gssntlmssp gssntlmssp-devel
Size: 310.91 KiB
Size change:  -653 B
Changelog:
  * Fri Mar 17 2023 Simo Sorce  - 1.2.0-2
  - Fix potential crash, backport for upstream


Package:  kvantum-1.0.9-1.fc38
Old package:  kvantum-1.0.7-2.fc38
Summary:  SVG-based theme engine for Qt5, KDE and LXQt
RPMs: kvantum kvantum-data
Size: 4.39 MiB
Size change:  5.75 KiB
Changelog:
  * Sat Mar 18 2023 Robert-Andr?? Mauchin  - 1.0.9-1
  - Update to 1.0.9


Package:  lgogdownloader-3.10-1.fc38
Old package:  lgogdownloader-3.9-3.fc38
Summary:  GOG.com download client
RPMs: lgogdownloader
Size: 1.81 MiB
Size change:  164.34 KiB
Changelog:
  * Mon Feb 20 2023 Jonathan Wakely  - 3.9-4
  - Rebuilt for Boost 1.81

  * Sat Mar 18 2023 Benjamin Lowry  - 3.10-1
  - lgogdownloader 3.10


Package:  libqalculate-4.6.0-1.fc38
Old package:  libqalculate-4.5.1-1.fc38
Summary:  Multi-purpose calculator library
RPMs: libqalculate libqalculate-devel qalculate
Size: 12.42 MiB
Size change:  217.76 KiB
Changelog:
  * Mon Jan 30 2023 Yaakov Selkowitz  - 4.5.1-2
  - Fix flatpak build

  * Thu Mar 09 2023 Mukundan Ragavan  - 4.6.0-1
  - Update to v4.6.0


Package:  libreoffice-icon-theme-papirus-20170228-13.fc38
Old package:  libreoffice-icon-theme-papirus-20170228-10.fc38
Summary:  Papirus theme for LibreOffice
RPMs: libreoffice-icon-theme-papirus
Size: 5.99 MiB
Size change:  4.49 MiB
Changelog:
  * Sat Mar 18 2023 Robert-Andr?? Mauchin  - 20170228-13
  - Make arched for libdir detection


Package:  lua-mpack-1.0.10-1.fc38
Old package:  lua-mpack-1.0.9-4.fc38
Summary:  Implementation of MessagePack for Lua
RPMs: lua-mpack lua5.1-mpack
Size: 204.02 KiB
Size change:  399 B
Changelog:
  * Sat Mar 18 2023 Andreas Schneider  - 1.0.10-1
  - resolves: rhbz#2179479 - Update to version 1.0.10


Package:  marshalparser-0.3.4-1.fc38
Old package:  marshalparser-0.3.3-3.fc38
Summary:  Parser for Python internal Marshal format
RPMs: marshalparser
Size: 37.87 KiB
Size change:  -8 B
Changelog:
  * Fri Mar 17 2023 Lumir Balhar  - 0.3.4-1
  - Update to 0.3.4 (rhbz#2179370)


Package:  ocp-0.2.103-2.fc38
Old package:  ocp-0.2.101-2.fc38
Summary:  Open Cubic Player for MOD/S3M/XM/IT/MIDI music files
RPMs: ocp
Size: 18.05 MiB
Size change:  63.88 KiB
Changelog:
  * Mon Jan 23 2023 Charles R. Anderson  - 0.2.102-1
  - update to 0.2.102
  - add BR: ancient-devel

  * Wed Mar 08 2023 Charles R. Anderson 
  - unifont-fonts switched from .ttf to .otf, specify

Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Neal Gompa]

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.



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

Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Aleš Matěj]

> If we're planning to drop by-default compatibility with EL7 anyway and bump 
> to 1.0, we
> could go a little bit further.
> 
> * "createrepo_c" doesn't need to support sqlite metadata generation at all,
> so long as the repository producer can run "sqliterepo_c".  If I recall
> correctly, yum on EL7 doesn't actually need the sqlite metadata to be 
> generated in any
> case, it can produce that metadata itself so long as it has the XML.  Making 
> it available
> only avoids a local processing step.  But if "modifyrepo_c" will be necessary 
> to
> work with most EL7 repos, then making "sqliterepo_c" necessary for a minor
> optimization isn't a big leap.

We were also discussing adding some "mode" options that could be set to EL7 to 
generate
compatible metadata for EL7 with just createrepo_c.
 
> * createrepo_c currently has two different switches for compression types,
> "compress-type" and "general-compress-type", where the latter applies
> to everything and the former only applies to files that are *not* "primary",
> "filelists", and "other".  there should be one compression type option
> and it should be applied uniformly to all metadata produced by the
> "createrepo_c" tool.  Yum would have choked on this because of the special
> handling around "comps", but I believe it should no longer be a concern?
Yes that is a good suggestion. There are also other command line options that
could use some (re)work. For example the unique --xz option which bypasses
the mentioned compression options. 
Unfortunately I am not sure if we will be able to prioritize all the 
improvements.
___
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: Next Open NeuroFedora Meeting: 1300 UTC on Monday, 27 March (today)

[Luna Jernberg]

Not attending today being sick

On 3/27/23, Ankur Sinha  wrote:
> Hello everyone,
>
> Please join us at the next Open NeuroFedora team meeting on Monday 27th
> March
> at 1300UTC in #fedora-neuro on Matrix or IRC
> (Libera.chat).  The meeting is a public meeting, and open for everyone
> to attend. You can join us over:
>
> Matrix: https://matrix.to/#/#neuro:fedoraproject.org
> IRC: https://webchat.libera.chat/?channels=#fedora-neuro
>
> You can use this link to see the local time for the meeting:
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230327T13=%3A=1
>
> or you can use this command in a terminal:
> $ date --date='TZ="UTC" 1300 Monday'
>
> The meeting will be chaired by @ankursinha. The agenda for the
> meeting is:
>
> - New introductions and roll call.
> - Tasks from last meeting:
> https://meetbot.fedoraproject.org/latest/neurofedora
> - Open Pagure tickets:
> https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
> - Package health check:
> https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
> - Open package reviews check:
> https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro
> - CompNeuro lab compose status check for F38:
> https://koji.fedoraproject.org/koji/packageinfo?packageID=30691
> - Neuroscience query of the week
> - Next meeting day, and chair.
> - Open floor.
>
> We hope to see you there!
>
> The meeting announcement is also posted on the NeuroFedora blog here:
> https://neuroblog.fedoraproject.org/2023/03/27/next-open-neurofedora-meeting-27-March-1300-utc.html
>
> You can learn more about NeuroFedora here:
> https://neuro.fedoraproject.org
>
>
> --
> 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

Re: Unretire rust-blake2

[Fabio Valentini]

On Mon, Mar 27, 2023 at 1:52 PM Kai A. Hiller  wrote:
>
> Hello,
>
> the rust-blake2 package[1] was retired recently. I’d like to take
> ownership of it, because I need it to package new versions of
> matrix-synapse.

Hi,

The package was retired by me because nothing depended on it for over a year.
If you only need the package as a dependency for matrix-synapse but
are not interested in Rust packaging other than having the packages
exist in Fedora, then some Rust SIG member (probably me) could also
become new primary maintainer after unretirement, if you'd prefer
that.

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

Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Aleš Matěj]

> On Fri, Mar 24, 2023 at 05:25:17PM +, Mattia Verga via devel wrote:
> I have a few additional questions:
> 
> * How does this impact zchunk? or does it?

I also think there shouldn't be any impact on zchunk.

> * Kind of unrealted to this change, but I'll ask here as createrepo_c
> folks might know off hand: Is it possible to decouple drpms from a repo?
> ie, if we had a updates repo and a completely seperate updates-drpms
> repo with just drpms in it, what would it take to use that? Changes in
> dnf I guess? but also changes in createrepo_c to generate repodata for a
> repo that was only drpms?

Such repos can be created by createrepo_c and modifyrepo_c but it is a bit 
awkward.
Basically first create normal (coupled) repo and then extract the 
prestodelta.xml and drpms
into a new repo. Additionally createrepo_c API could be used to make it more 
straight forward.
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.
___
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

Unretire rust-blake2

[Kai A. Hiller]

Hello,

the rust-blake2 package[1] was retired recently. I’d like to take 
ownership of it, because I need it to package new versions of 
matrix-synapse.


Kai

[1] https://src.fedoraproject.org/rpms/rust-blake2
___
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 2181856] perl-Scope-Upper-0.34 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-Scope-Upper-0.34-1.fc3
   ||9




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

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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

[Neal H. Walfield]

On Mon, 27 Mar 2023 13:16:45 +0200,
Zbigniew Jędrzejewski-Szmek wrote:
> I agree. The scope of the issue is fairly narrow, and the underlying
> issue is an invalid signature made by the anydesk maintainers.
> We also have a simple command that users can use to work around
> the issue.

If you are thinking of sq-keyring-linter, that won't help here.  This
is not a SHA-1 issue.

The issue (I think) is that the anydesk maintains were too aggressive
in what they striped when they exported the OpenPGP certificate.  They
probably ran: `gpg --export --export-options export-minimal
FINGERPRINT`.  According to the gpg manual page, that does:

```
 export-minimal
  Export the smallest key possible.  This removes all signatures
  except the most recent self-signature on each user ID. This
  option is the same as running the '--edit-key' command
  "minimize" before export except that the local copy of the key
  is not modified.  Defaults to no.
```

This makes sense when sharing an OpenPGP certificate via email, say,
so that someone can (in the future) send you an encrypted message.
But it doesn't make sense when sending the certificate to someone who
should then verify past signatures, which is the case here.

Neal
___
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: crypto-policies

[Zbigniew Jędrzejewski-Szmek]

On Mon, Mar 27, 2023 at 11:40:05AM +0200, Fabio Valentini wrote:
> On Mon, Mar 27, 2023 at 11:23 AM Kamil Paral  wrote:
> >
> > On Sat, Mar 25, 2023 at 8:20 AM Neal H. Walfield  wrote:
> >>
> >> Panu wrote https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c126 :
> >>
> >> > To me the key points here are
> >> > 1) there's a lot of obsolete/broken crypto out there
> >> > 2) we need better error messages
> >> >
> >> > Properly dealing with 2) needs an API redesign, but we'll try to work 
> >> > out some sort of bandaid solution.
> >>
> >> Are better diagnostics sufficient from your point of view, or are you
> >> looking for a different solution?
> >
> >
> > I think my question in 
> > https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c125 wasn't really 
> > answered, or at least I don't understand the implications.
> 
> *putting on both my FESCo and rpm-sequoia package maintainer hats*
> 
> The issue which was voted on for blocker status by FESCo ("In order to
> unblock, RPM must accept SHA-1 hashes and DSA keys for Fedora 38
> (...)") has been resolved.
> As far as I can tell, the anydesk case is different. It's not a
> problem caused by the new crypto policy - the packages don't use a
> SHA-1 signature - but happens because the Sequoia PGP implementation
> is stricter about checking signatures for sanity / validity.
> If I understand correctly, the packages are signed with a key that
> fails validation, so I'm inclined to say "this is not our problem"
> (and it also looks like this is an issue that's specific to this
> third-party package vendor, in contrast to the original SHA-1 / DSA
> issue which affected repositories that are officially endorsed by
> Fedora Workstation).

I agree. The scope of the issue is fairly narrow, and the underlying
issue is an invalid signature made by the anydesk maintainers.
We also have a simple command that users can use to work around
the issue.

The way that this is handled by rpm/dnf can be improved, but
we shouldn't block the release on this, and we should also track
this in #2170878, it is long enough already.

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

[Bug 2181845] perl-ExtUtils-MakeMaker-7.70 is available

[bugzilla]

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



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


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

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 CC|iarn...@gmail.com,  |
   |jples...@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=2181856
___
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-IO-Socket-IP] PR #3: Package tests

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-IO-Socket-IP` that 
you are following:
``
Package tests
``

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

[Bug 2181845] perl-ExtUtils-MakeMaker-7.70 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-ExtUtils-MakeMaker-7.7
   ||0-1.fc39
 CC|jples...@redhat.com,|
   |mspa...@redhat.com, |
   |ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value
 Status|NEW |MODIFIED




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

[Panu Matilainen]

On 3/27/23 12:40, Fabio Valentini wrote:

On Mon, Mar 27, 2023 at 11:23 AM Kamil Paral  wrote:


On Sat, Mar 25, 2023 at 8:20 AM Neal H. Walfield  wrote:


Panu wrote https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c126 :


To me the key points here are
1) there's a lot of obsolete/broken crypto out there
2) we need better error messages

Properly dealing with 2) needs an API redesign, but we'll try to work out some 
sort of bandaid solution.


Are better diagnostics sufficient from your point of view, or are you
looking for a different solution?



I think my question in https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c125 
wasn't really answered, or at least I don't understand the implications.


Kamil, would've been good to state that in the bug then. I only saw this 
email by sheer luck.



*putting on both my FESCo and rpm-sequoia package maintainer hats*

The issue which was voted on for blocker status by FESCo ("In order to
unblock, RPM must accept SHA-1 hashes and DSA keys for Fedora 38
(...)") has been resolved.
As far as I can tell, the anydesk case is different. It's not a
problem caused by the new crypto policy - the packages don't use a
SHA-1 signature - but happens because the Sequoia PGP implementation
is stricter about checking signatures for sanity / validity.
If I understand correctly, the packages are signed with a key that
fails validation, so I'm inclined to say "this is not our problem"
(and it also looks like this is an issue that's specific to this
third-party package vendor, in contrast to the original SHA-1 / DSA
issue which affected repositories that are officially endorsed by
Fedora Workstation).


Indeed. The RpmSequoia change is not really about phasing out any 
specific algorithms, that's a different topic. The anydesk case is 
actually a fine showcase of Sequoia doing exactly what the change is 
advertising! Only it's getting drowned in this SHA1/DSA noise, and poor 
error messages (which is rpm's, not Sequoias fault).


- Panu -
___
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 2181733] perl-Archive-Tar-3.00 is available

[bugzilla]

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



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


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

[Jonathan Wakely]

On Monday, March 27, 2023, Andreas Schneider  wrote:
> On Sunday, 26 March 2023 01:56:32 CEST Miroslav Suchý wrote:
>> Two weeks ago we had:
>> > * 23107 spec files in Fedora
>> >
>> > * 29503license tags in all spec files
>> >
>> > * 20302 tags have not been converted to SPDX yet
>> >
>> > * 8096 tags can be trivially converted using `license-fedora2spdx`
>>
>> Today we have:
>>
>> * 22882 spec files in Fedora
>>
>> * 29366license tags in all spec files
>>
>> * 19784 tags have not been converted to SPDX yet(huray, we are under 20k)
>>
>> * 7912tags can be trivially converted using `license-fedora2spdx`
>>
>> The list of packages needed to be converted is again here:
>>
>>
https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-fi
>> nal.txt
>>
>> List by package maintainers is here
>>
>>
https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-fi
>> nal-maintainers.txt
>
> Looking into this it lists for example:
>
> libtermkey   asn salimma
>
>
> The spec file of libtermkey has:
>
>   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
___
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: crypto-policies

[Fabio Valentini]

On Mon, Mar 27, 2023 at 11:23 AM Kamil Paral  wrote:
>
> On Sat, Mar 25, 2023 at 8:20 AM Neal H. Walfield  wrote:
>>
>> Panu wrote https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c126 :
>>
>> > To me the key points here are
>> > 1) there's a lot of obsolete/broken crypto out there
>> > 2) we need better error messages
>> >
>> > Properly dealing with 2) needs an API redesign, but we'll try to work out 
>> > some sort of bandaid solution.
>>
>> Are better diagnostics sufficient from your point of view, or are you
>> looking for a different solution?
>
>
> I think my question in 
> https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c125 wasn't really 
> answered, or at least I don't understand the implications.

*putting on both my FESCo and rpm-sequoia package maintainer hats*

The issue which was voted on for blocker status by FESCo ("In order to
unblock, RPM must accept SHA-1 hashes and DSA keys for Fedora 38
(...)") has been resolved.
As far as I can tell, the anydesk case is different. It's not a
problem caused by the new crypto policy - the packages don't use a
SHA-1 signature - but happens because the Sequoia PGP implementation
is stricter about checking signatures for sanity / validity.
If I understand correctly, the packages are signed with a key that
fails validation, so I'm inclined to say "this is not our problem"
(and it also looks like this is an issue that's specific to this
third-party package vendor, in contrast to the original SHA-1 / DSA
issue which affected repositories that are officially endorsed by
Fedora Workstation).

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

[rpms/perl-Params-Coerce] PR #1: Update license to SPDX format

[Michal Josef Špaček]

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

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Params-Coerce/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: crypto-policies

[Kamil Paral]

On Sat, Mar 25, 2023 at 8:20 AM Neal H. Walfield  wrote:

> Panu wrote https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c126 :
>
> > To me the key points here are
> > 1) there's a lot of obsolete/broken crypto out there
> > 2) we need better error messages
> >
> > Properly dealing with 2) needs an API redesign, but we'll try to work
> out some sort of bandaid solution.
>
> Are better diagnostics sufficient from your point of view, or are you
> looking for a different solution?
>

I think my question in
https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c125 wasn't really
answered, or at least I don't understand the implications.
___
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-Params-Coerce] PR #1: Update license to SPDX format

[Michal Josef Špaček]

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

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Params-Coerce/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 2181733] perl-Archive-Tar-3.00 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Archive-Tar-3.00-1.fc3
   ||9




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

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com,|
   |ka...@ucw.cz,   |
   |mspa...@redhat.com, |
   |rhug...@redhat.com, |
   |rstr...@redhat.com, |
   |sandm...@redhat.com,|
   |st...@silug.org |
   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=2181733
___
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 2181578] perl-DateTime-TimeZone-2.59 is available

[bugzilla]

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



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


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

[bugzilla]

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



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


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

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-DateTime-TimeZone-2.59
   ||-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=2181578
___
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 2181578] perl-DateTime-TimeZone-2.59 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 CC|iarn...@gmail.com,  |
   |jples...@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=2181578
___
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

Next Open NeuroFedora Meeting: 1300 UTC on Monday, 27 March (today)

[Ankur Sinha]

Hello everyone,

Please join us at the next Open NeuroFedora team meeting on Monday 27th March
at 1300UTC in #fedora-neuro on Matrix or IRC
(Libera.chat).  The meeting is a public meeting, and open for everyone
to attend. You can join us over:

Matrix: https://matrix.to/#/#neuro:fedoraproject.org
IRC: https://webchat.libera.chat/?channels=#fedora-neuro

You can use this link to see the local time for the meeting:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230327T13=%3A=1

or you can use this command in a terminal:
$ date --date='TZ="UTC" 1300 Monday'

The meeting will be chaired by @ankursinha. The agenda for the
meeting is:

- New introductions and roll call.
- Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora
- Open Pagure tickets: 
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
- Package health check: 
https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
- Open package reviews check: 
https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro
- CompNeuro lab compose status check for F38: 
https://koji.fedoraproject.org/koji/packageinfo?packageID=30691
- Neuroscience query of the week
- Next meeting day, and chair.
- Open floor.

We hope to see you there!

The meeting announcement is also posted on the NeuroFedora blog here:
https://neuroblog.fedoraproject.org/2023/03/27/next-open-neurofedora-meeting-27-March-1300-utc.html

You can learn more about NeuroFedora here:
https://neuro.fedoraproject.org


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

[Andreas Schneider]

On Sunday, 26 March 2023 01:56:32 CEST Miroslav Suchý wrote:
> Two weeks ago we had:
> > * 23107 spec files in Fedora
> > 
> > * 29503license tags in all spec files
> > 
> > * 20302 tags have not been converted to SPDX yet
> > 
> > * 8096 tags can be trivially converted using `license-fedora2spdx`
> 
> Today we have:
> 
> * 22882 spec files in Fedora
> 
> * 29366license tags in all spec files
> 
> * 19784 tags have not been converted to SPDX yet(huray, we are under 20k)
> 
> * 7912tags can be trivially converted using `license-fedora2spdx`
> 
> The list of packages needed to be converted is again here:
> 
> https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-fi
> nal.txt
> 
> List by package maintainers is here
> 
> https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-fi
> nal-maintainers.txt

Looking into this it lists for example:

libtermkey   asn salimma


The spec file of libtermkey has:

  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?



Best regards


Andreas

___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-Glib-Object-Introspection-0.050-1.fc36.src.rpm for rawhide failed
http://koji.fedoraproject.org/koji/taskinfo?taskID=99177575


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

[bugzilla]

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

Bug ID: 2181971
   Summary: perl-Glib-Object-Introspection-0.050 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Glib-Object-Introspection
  Keywords: FutureFeature, Triaged
  Assignee: berra...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: berra...@redhat.com,
perl-devel@lists.fedoraproject.org, ser...@serjux.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.050
Upstream release that is considered latest: 0.050
Current version/release in rawhide: 0.049-11.fc38
URL: http://search.cpan.org/dist/Glib-Object-Introspection/

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


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


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

[bugzilla]

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Created attachment 1953871
  --> https://bugzilla.redhat.com/attachment.cgi?id=1953871=edit
Update to 0.050 (#2181971)


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