[Bug 2262902] perl-Mail-SPF-3.20240206 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Mail-SPF-3.20240206-1.
   ||fc40
 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2024-02-06 07:26:30



--- Comment #4 from Fedora Update System  ---
FEDORA-2024-15893a1800 (perl-Mail-SPF-3.20240206-1.fc40) has been pushed to the
Fedora 40 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=2262902

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262902%23c4
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262902] perl-Mail-SPF-3.20240206 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #3 from Fedora Update System  ---
FEDORA-2024-15893a1800 (perl-Mail-SPF-3.20240206-1.fc40) has been submitted as
an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-15893a1800


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262902

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262902%23c3
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262917] perl-Business-ISBN-Data-20240206.001 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Business-ISBN-Data-202
   ||40206.001-1.fc40
 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2024-02-06 06:59:30



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-e39bc1e1b9 (perl-Business-ISBN-Data-20240206.001-1.fc40) has been
pushed to the Fedora 40 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=2262917

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262917%23c2
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262917] perl-Business-ISBN-Data-20240206.001 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2024-e39bc1e1b9 (perl-Business-ISBN-Data-20240206.001-1.fc40) has been
submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e39bc1e1b9


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262917

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262917%23c1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262917] New: perl-Business-ISBN-Data-20240206.001 is available

[bugzilla]

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

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



Releases retrieved: 20240206.001
Upstream release that is considered latest: 20240206.001
Current version/release in rawhide: 20240126.001-1.fc40
URL: https://metacpan.org/dist/Business-ISBN-Data/

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


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262917

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262917%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262902] New: perl-Mail-SPF-3.20240206 is available

[bugzilla]

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

Bug ID: 2262902
   Summary: perl-Mail-SPF-3.20240206 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Mail-SPF
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jpazdzi...@redhat.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 3.20240206
Upstream release that is considered latest: 3.20240206
Current version/release in rawhide: 3.20240205-1.fc40
URL: https://metacpan.org/dist/Mail-SPF/

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


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262902

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262902%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262902] perl-Mail-SPF-3.20240206 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
Created attachment 2015293
  --> https://bugzilla.redhat.com/attachment.cgi?id=2015293=edit
Update to 3.20240206 (#2262902)


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262902

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262902%23c2
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262902] perl-Mail-SPF-3.20240206 is available

[bugzilla]

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



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

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

StdOut:
setting SOURCE_DATE_EPOCH=1707177600
error: Bad file: ./Mail-SPF-3.20240206.tar.gz: No such file or directory

RPM build errors:
Bad file: ./Mail-SPF-3.20240206.tar.gz: No such file or directory


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

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262902

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262902%23c1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3f1f3dcef0   
wordpress-5.1.18-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-afdec12596   
libebml-1.3.9-2.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-25f8bac8aa   
chromium-121.0.6167.139-2.el7


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

globus-common-18.14-1.el7
globus-gass-copy-10.13-1.el7
globus-gridftp-server-13.25-1.el7
globus-gsi-cert-utils-10.11-1.el7
globus-gsi-credential-8.4-1.el7
globus-gsi-sysconfig-9.6-1.el7
globus-rsl-11.4-1.el7
myproxy-6.2.16-1.el7

Details about builds:



 globus-common-18.14-1.el7 (FEDORA-EPEL-2024-460f002209)
 Grid Community Toolkit - Common Library

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 Mattias Ellert  - 18.14-1
- New GCT release v6.2.20240202
* Wed Jan 24 2024 Fedora Release Engineering  - 
18.13-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Fedora Release Engineering  - 
18.13-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Wed Jul 19 2023 Fedora Release Engineering  - 
18.13-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Thu Jan 19 2023 Fedora Release Engineering  - 
18.13-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Thu Jul 21 2022 Fedora Release Engineering  - 
18.13-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Tue May 31 2022 Mattias Ellert  - 18.13-2
- Rebuild with correct perl version (EPEL 8)
* Mon May 30 2022 Jitka Plesnikova  - 18.13-2
- Perl 5.36 rebuild




 globus-gass-copy-10.13-1.el7 (FEDORA-EPEL-2024-460f002209)
 Grid Community Toolkit - Globus Gass Copy

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 Mattias Ellert  - 10.13-1
- New GCT release v6.2.20240202
* Wed Jan 24 2024 Fedora Release Engineering  - 
10.12-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Fedora Release Engineering  - 
10.12-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Wed Jul 19 2023 Fedora Release Engineering  - 
10.12-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Thu Jan 19 2023 Fedora Release Engineering  - 
10.12-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Thu Jul 21 2022 Fedora Release Engineering  - 
10.12-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild




 globus-gridftp-server-13.25-1.el7 (FEDORA-EPEL-2024-460f002209)
 Grid Community Toolkit - Globus GridFTP Server

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 Mattias Ellert  - 13.25-1
- New GCT release v6.2.20240202
- Drop patches included in the release
* Wed Jan 24 2024 Fedora Release Engineering  - 
13.24-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Fedora Release Engineering  - 
13.24-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Wed Jul 19 2023 Fedora Release Engineering  - 
13.24-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Wed Apr 19 2023 Mattias Ellert  - 13.24-5
- Reenable optional test dependency fakeroot on ppc64le in EPEL 8
* Thu Jan 19 2023 Fedora Release Engineering  - 
13.24-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild




 globus-gsi-cert-utils-10.11-1.el7 (FEDORA-EPEL-2024-460f002209)
 Grid Community Toolkit - Globus GSI Cert Utils Library

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 

[Bug 2262901] New: perl-LWP-Protocol-https-6.13 is available

[bugzilla]

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

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



Releases retrieved: 6.13
Upstream release that is considered latest: 6.13
Current version/release in rawhide: 6.12-1.fc40
URL: http://search.cpan.org/dist/LWP-Protocol-https/

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


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262901

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262901%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262363] perl-DateTime-TimeZone-2.62 is available

[bugzilla]

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



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

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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262363%23c6
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

bodhi push error

[Christoph Junghans]

Hi,

Has anybody seen this error before:
FEDORA-2024-310c0537ac ejected from the push because "Cannot find
relevant tag for gromacs-2023.4-1.fc39. None of ['f39-updates',
'f39-updates-pending'] are in ['epel9-next-testing', 'epel7-testing',
'eln-updates-testing', 'epel8-testing', 'epel9-testing',
'epel8-next-testing', 'f40-container-updates-testing',
'f38-modular-updates-testing', 'f38-flatpak-updates-testing',
'f40-updates-testing', 'f38-updates-testing',
'f38-container-updates-testing', 'f39-updates-testing',
'f39-container-updates-testing', 'f39-flatpak-updates-testing']."

Cheers,

Christoph

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Chuck Anderson]

On Tue, Feb 06, 2024 at 09:56:30AM +1000, Peter Hutterer wrote:
> On Mon, Feb 05, 2024 at 10:33:52AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Mon, Feb 05, 2024 at 10:34:13AM +1000, Peter Hutterer wrote:
> > > > And even before that, things were already only limping along. That was
> > > > happening for over a decade and in that timeframe *nobody* has wanted
> > > > to step up and work on it. Wayland is the future because otherwise we
> > > > have no graphics future, as things currently stand.
> > > 
> > > It also doesn't help that the "it's the same people working on X and
> > > Wayland" argument means that, absent significant breakthroughs in
> > > space-time research, we can work on one or the other, not both.
> > > Something's got to give.
> > 
> > We could also switch to a 4-day week, with 20h shifts ;)
> 
> "if 24h in a day isn't enough, work at night"
> 
> Uncredited because I'm not sure the person I got this from (in jest)
> really wants the credit ;)

Just schedule the work for Q5 (the fifth quarter).
--
___
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 2262363] perl-DateTime-TimeZone-2.62 is available

[bugzilla]

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



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

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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262363%23c5
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Peter Hutterer]

On Mon, Feb 05, 2024 at 10:33:52AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Feb 05, 2024 at 10:34:13AM +1000, Peter Hutterer wrote:
> > > And even before that, things were already only limping along. That was
> > > happening for over a decade and in that timeframe *nobody* has wanted
> > > to step up and work on it. Wayland is the future because otherwise we
> > > have no graphics future, as things currently stand.
> > 
> > It also doesn't help that the "it's the same people working on X and
> > Wayland" argument means that, absent significant breakthroughs in
> > space-time research, we can work on one or the other, not both.
> > Something's got to give.
> 
> We could also switch to a 4-day week, with 20h shifts ;)

"if 24h in a day isn't enough, work at night"

Uncredited because I'm not sure the person I got this from (in jest)
really wants the credit ;)

Cheers,
  Peter
--
___
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 - 2024-02-07 22:00 UTC

[Kevin Fenzi]

There will be an outage starting at 2024-02-07 22:00UTC,
which will last approximately 6 hours.

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

date -d '2024-02-07 22:00UTC'

Reason for outage:

We will be applying updates and rebooting servers. No one service should be 
down long, but may be up and down in the outage window.
Additionally, as time permits we will be doing the following additional work:

- resizing disks on database servers

- moving some database servers to rhel9 and newer postgresql

- applying some firmware updates

Affected Services:

Most services will be affected for a short time, but end user facing services 
(mirrorlists, websites) should not be affected.

Ticket Link:

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

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

Updated status for this outage may be available at
https://www.fedorastatus.org/


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 - 2024-02-07 22:00 UTC

[Kevin Fenzi]

There will be an outage starting at 2024-02-07 22:00UTC,
which will last approximately 6 hours.

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

date -d '2024-02-07 22:00UTC'

Reason for outage:

We will be applying updates and rebooting servers. No one service should be 
down long, but may be up and down in the outage window.
Additionally, as time permits we will be doing the following additional work:

- resizing disks on database servers

- moving some database servers to rhel9 and newer postgresql

- applying some firmware updates

Affected Services:

Most services will be affected for a short time, but end user facing services 
(mirrorlists, websites) should not be affected.

Ticket Link:

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

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

Updated status for this outage may be available at
https://www.fedorastatus.org/


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

List of long term FTBFS packages to be retired in February

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 40 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 4 weeks, i.e. around 2024-02-28.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f40.

I apologize for starting this process a bit later than required again.
Unfortunately, I had other work obligations.
Volunteers to take over this are always welcome.

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 37.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval for that.

If you see a package that can be rebuilt, please do so.

Package  (co)maintainers

calendardcantrell, egoode
erlang-jose bowlofeggs, erlang-maint-sig, jcline, peter
ghdlsailer
git-secrets keesdejong
golang-github-acme-lego eclipseo, go-sig
golang-github-gatherstars-com-jwz   eclipseo, go-sig
golang-github-genuinetools-pkg  eclipseo, go-sig
golang-github-gobs-pretty   eclipseo, go-sig
golang-github-jhillyerd-enmime  eclipseo, go-sig
golang-github-pierrre-compare   eclipseo, go-sig
golang-github-smartystreets-goconvey  alexsaezm, go-sig, jchaloup
golang-gopkg-square-jose-2  alexsaezm, go-sig
golang-gvisor   eclipseo, elmarco, go-sig
golang-opentelemetry-otel-0.20  alexsaezm, go-sig
golang-sigs-k8s-kustomize   dcavalca, go-sig
golang-vitess   eclipseo, go-sig
infinipath-psm  honli
j4-dmenu-desktopibotty
jackson-dataformats-binary  mbooth
jackson-dataformats-textmbooth
java-1.8.0-openjdk-aarch32  akasko, jvanek
jreen   rdieter
libdeltacloud   clalance
mingw-clucene   greghellings
mingw-speexdsp  janisozaur
nbd-runner  xiubli
nodejs-generic-pool patches, piotrp
ofono   njha, thunderbirdtr
openni-primesense   cottsay, jkastner, rmattes
pesign-test-app javierm, nfrayer, pjones, rharwood
pthsem  ixs
rust-drgjbtrystram, rust-sig
telepathy-gabbleaperezbios

The following packages require above mentioned packages:
Depending on: erlang-jose (1)
erlang-p1_acme (maintained by: bowlofeggs, erlang-maint-sig, peter)
erlang-p1_acme-1.0.8-9.fc40.noarch requires erlang-jose
erlang-p1_acme-1.0.8-9.fc40.src requires erlang-jose

Depending on: golang-github-gatherstars-com-jwz (1)
aerc (maintained by: eclipseo, go-sig)
aerc-0.15.2-2.fc39.src requires 
golang(github.com/gatherstars-com/jwz)

Depending on: golang-github-genuinetools-pkg (1)
reg (maintained by: go-sig, infra-sig, mattia)
reg-0.16.1-15.fc40.src requires 
golang(github.com/genuinetools/pkg/cli)

Depending on: golang-github-gobs-pretty (2)
golang-github-vinyldns (maintained by: eclipseo, go-sig)
		golang-github-vinyldns-0.9.13-1.fc40.2.src requires 
golang(github.com/gobs/pretty)


golang-github-acme-lego (maintained by: eclipseo, go-sig)
		golang-github-acme-lego-4.4.0-8.fc37.src requires 
golang(github.com/vinyldns/go-vinyldns/vinyldns)
		golang-github-acme-lego-devel-4.4.0-8.fc37.noarch requires 
golang(github.com/vinyldns/go-vinyldns/vinyldns)


Depending on: golang-github-jhillyerd-enmime (2)
golang-github-gatherstars-com-jwz (maintained by: eclipseo, go-sig)
		golang-github-gatherstars-com-jwz-1.3.0-1.fc37.src requires 
golang(github.com/jhillyerd/enmime)


aerc (maintained by: eclipseo, go-sig)
aerc-0.15.2-2.fc39.src requires 
golang(github.com/gatherstars-com/jwz)

Depending on: golang-github-pierrre-compare (1)
golang-github-pierrre-geohash (maintained by: eclipseo, go-sig)
		golang-github-pierrre-geohash-1.0.0-9.fc40.src requires 
golang(github.com/pierrre/compare)


Depending on: golang-github-smartystreets-goconvey (23)
golang-github-afex-hystrix (maintained by: alexsaezm, go-sig)
		golang-github-afex-hystrix-0-0.14.20190622gitfa1af6a.fc40.src requires 
golang(github.com/smartystreets/goconvey/convey)

Orphaning my last Google Cloud packages

[Major Hayden]

Hey there,

I orphaned quite a few of Google's Python SDKs recently and I'm ready to orphan 
some of the last few Google-related packages:

golang-github-googlecloudplatform-guest-logging
google-compute-engine-guest-configs
google-disk-expand
google-guest-agent
google-osconfig-agent

The guest-configs package isn't too difficult, but the others are challenging 
due to additional dependencies showing up in the upstream code from time to 
time. Lots of these hinge on getting an update to the osconfig-agent, but that 
leads to a brand new version of arrow with another long line of dependencies. 掠

My original goal with maintaining these was to build a great Google Cloud 
experience for Fedora inside the instance itself, but other priorities began to 
pile up and these upstreams make changes that are too rapid and vast for me to 
keep up with.

If you're interested in any of these, let me know! Otherwise I'll likely be 
orphaning them later this week. 

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

Re: [heads up] mass rebuild for opencv 4.9.0 with soname bump on rawhide

[Sérgio Basto]

On Sun, 2024-02-04 at 19:59 +, Sérgio Basto wrote:
> Hi,
> 
> I will start a mass rebuild in a side-tag, very soon , the goal is
> finish and merge it before branch of Fedora 40, please let me know we
> have any thing that prevent to proceeding.
> 

mass rebuild started on side-tag  f40-build-side-82977

Best regards,

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

[Bug 2257106] F40FailsToInstall: perl-WWW-Google-Contacts

[bugzilla]

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



--- Comment #2 from Fedora Fails To Install  ---
Hello,

Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/

This package fails to install and maintainers are advised to take one of the
following actions:

 - Fix this bug and close this bugzilla once the update makes it to the
repository.
   (The same script that posted this comment will eventually close this
bugzilla
   when the fixed package reaches the repository, so you don't have to worry
about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't
done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs
will continue.
This package may be orphaned in 4+ weeks.
This is the second reminder (step 4) from the policy.

Don't hesitate to ask for help on
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/ if
you are unsure how to fix this bug.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2257106

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257106%23c2
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2257106] F40FailsToInstall: perl-WWW-Google-Contacts

[bugzilla]

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

Fedora Fails To Install  changed:

   What|Removed |Added

  Flags|needinfo?(avibrazil@gmail.c |
   |om) |




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

[bugzilla]

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

Fedora Fails To Install  changed:

   What|Removed |Added

  Flags||needinfo?(avibrazil@gmail.c
   ||om)




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

[EPEL-devel] Bodhi 8.0.2 deployed to prod today

[Mattia Verga via epel-devel]

Hello,
I'd like to announce that Bodhi 8.0.2 has been deployed today and brings a 
feature which was requested specifically for EPEL: from now on (if everything 
works as expected) all builds submitted as buildroot overrides for EPEL9 will 
also be tagged as buildroot overrides for EPEL9N.
This is not hardcoded, but is rather configurable in Bodhi config file. Here it 
is the example that makes the current EPEL9-EPEL9N inheritance:
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/base/templates/production.ini.j2#_630
The line above (commented out) is just an example to show that this can work 
for multiple releases at once.

Apart from that, Bodhi 8.0 also makes possible to define different createrepo_c 
settings per release in an external config file.
The file is:
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/files/createrepo_c.ini
and I hope it is sufficiently self explanatory and clear.
I just want to write it here on the EPEL list, as the EPEL releases are those 
which need different settings from Fedora release. I copied the previously 
hardcoded values within Bodhi and I hope to have not misread any value.

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

Bodhi 8.0.2 deployed to prod

[Mattia Verga via devel]

Hello folks,

we (well, mostly kevin) have just deployed Bodhi 8.0.2 in prod.
There are several changes in the background, but what can be of some 
interest for you, users and developers, are these points:

- Fixed “cannot access local variable ‘tags’” error when editing flatpak 
updates
- Sidetags in the dropdown of the new update form are now sorted 
alphabetically
- Usernames containing a "-" are now correctly matched when mentioning
- Build NVRs are added to the Bugzilla comment
- There should be no more Updates ejected from the composes that remain 
stuck in pending state due to wrong tags applied to their builds (or, 
better, they should be automatically pushed again after 48 hours)
- The webUI now allows unpushing Rawhide updates which fail gating tests
- The release timeline graph now uses logarithmic scale for better display
- The UpdateReadyForTesting message format is simplified, and the 
message is now published on update creation and edit with changed builds 
instead of push to testing
- JSON APIs now support quering Releases by multiple states, for example 
'?state=pending=frozen'
- added a get_critpath_components json endpoint to list critical path 
components configured for a Release
- Builds associated to unpushed updates can now be moved to other 
existing updates
- Release data now give information about the status of pre_beta and 
post_beta and of the first date of release
- Members of QA groups defined in configuration are now able to waive or 
trigger tests for any update, despite they’re packagers/provenpackagers 
or not
- Update notes are now converted to plaintext when printed in email or 
messages
- Releases can now inherit buildroot override tags from other releases 
by settings in Bodhi config file
- Settings for repodata and updateinfo can now be set by an external 
config file and no more hardcoded

For the full changelog between the previous deployed 7.2.2 version and 
the latest 8.0.2, please check 
https://fedora-infra.github.io/bodhi/8.0/user/release_notes.html

Mattia

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

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

[updates]

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-11fae9c7fb   
python-aiohttp-3.7.4-2.el8
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-131343ad4f   
libebml-1.3.9-2.el8


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

ansible-packaging-1-12.el8
globus-common-18.14-1.el8
globus-gass-copy-10.13-1.el8
globus-gridftp-server-13.25-1.el8
globus-gsi-cert-utils-10.11-1.el8
globus-gsi-credential-8.4-1.el8
globus-gsi-sysconfig-9.6-1.el8
globus-rsl-11.4-1.el8
myproxy-6.2.16-1.el8

Details about builds:



 ansible-packaging-1-12.el8 (FEDORA-EPEL-2024-a8062e64d4)
 RPM packaging macros and generators for Ansible collections

Update Information:

%ansible_collection_url: handle new URL scheme

ChangeLog:

* Tue Dec  5 2023 Maxwell G  - 1-12
- %ansible_collection_url: handle new URL scheme
* Wed Jul 19 2023 Fedora Release Engineering  - 1-11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Thu May 11 2023 Maxwell G  - 1-10
- %ansible_collection_install - disable spurious collections path warnings
- ansible-packaging-tests - don't depend on pytest-forked with ansible-core 2.16
- ansible-srpm-macros - include license file in the package




 globus-common-18.14-1.el8 (FEDORA-EPEL-2024-6d0d969b44)
 Grid Community Toolkit - Common Library

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 Mattias Ellert  - 18.14-1
- New GCT release v6.2.20240202
* Wed Jan 24 2024 Fedora Release Engineering  - 
18.13-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Fedora Release Engineering  - 
18.13-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Wed Jul 19 2023 Fedora Release Engineering  - 
18.13-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Thu Jan 19 2023 Fedora Release Engineering  - 
18.13-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Thu Jul 21 2022 Fedora Release Engineering  - 
18.13-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild




 globus-gass-copy-10.13-1.el8 (FEDORA-EPEL-2024-6d0d969b44)
 Grid Community Toolkit - Globus Gass Copy

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 Mattias Ellert  - 10.13-1
- New GCT release v6.2.20240202
* Wed Jan 24 2024 Fedora Release Engineering  - 
10.12-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Fedora Release Engineering  - 
10.12-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Wed Jul 19 2023 Fedora Release Engineering  - 
10.12-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Thu Jan 19 2023 Fedora Release Engineering  - 
10.12-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Thu Jul 21 2022 Fedora Release Engineering  - 
10.12-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild




 globus-gridftp-server-13.25-1.el8 (FEDORA-EPEL-2024-6d0d969b44)
 Grid Community Toolkit - Globus GridFTP Server

Update Information:

Grid Community Toolkit (GCT) 6.2.20240202)

ChangeLog:

* Mon Feb  5 2024 Mattias Ellert  - 13.25-1
- New GCT release v6.2.20240202
- Drop patches included in the release
* Wed Jan 24 2024 Fedora Release Engineering  - 
13.24-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Fri Jan 19 2024 Fedora Release Engineering  - 
13.24-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Wed Jul 19 2023 Fedora Release Engineering  - 
13.24-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild

Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

[Daniel P . Berrangé]

On Mon, Feb 05, 2024 at 05:34:06PM +0100, Dan Horák wrote:
> Hi,
> 
> could someone in the mingw team look at mingw-libgsf / libgsf (please
> see the bug forwarded below)? If I see right, then the standalone
> mingw-libgsf package should be retired as there are mingw builds from
> the regular libgsf package, which seems to be regularly updated.

Copying Marc-André who added the mingw sub-RPMs to the native
package.

The mingw-libgsf should have been retired on rawhide, as soon
as the libgsf native had a successful build with mingw packages.

At this point I guess it'll need retiring on both rawhide
and f39

> 
> 
>   Thanks,
> 
>   Dan
> 
> 
> 
> Begin forwarded message:
> 
> Date: Mon, 05 Feb 2024 00:09:44 +
> From: bugzi...@redhat.com
> Subject: [Bug 2066129] mingw-libgsf-1_14_52 is available
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2066129
> 
> Upstream Release Monitoring
>  changed:
> 
>What|Removed |Added
> 
> Summary|mingw-libgsf-1_14_51 is |mingw-libgsf-1_14_52 is
>|available   |available
> 
> 
> 
> --- Comment #8 from Upstream Release Monitoring
>  --- Releases retrieved:
> 1_14_52 Upstream release that is considered latest: 1_14_52
> Current version/release in rawhide: 1.14.48-7.fc40
> URL: http://www.gnome.org/projects/libgsf/
> 
> 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/1980/
> 
> 
> To change the monitoring settings for the project, please visit:
> https://src.fedoraproject.org/rpms/mingw-libgsf
> 
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.
> https://bugzilla.redhat.com/show_bug.cgi?id=2066129
> 
> Report this comment as SPAM:
> https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202066129%23c8
> --
> ___
> 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

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262786] Upgrade perl-Mail-SPF to 3.20240205

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Mail-SPF-3.20240205-1.
   ||fc40
 Resolution|--- |ERRATA
Last Closed||2024-02-05 16:51:27



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-af967d44f3 has been pushed to the Fedora 40 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=2262786

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262786%23c2
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Rawhide Beta Everything.iso and other ISOs -- btrfs -- serious issue

[Kamil Paral]

That sounds like this Common Issue:
https://discussion.fedoraproject.org/t/its-difficult-to-reformat-a-btrfs-partition-subvolume-in-the-installer/89052
--
___
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 2262786] Upgrade perl-Mail-SPF to 3.20240205

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262786

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262786%23c1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[HEADS UP] [SONAME BUMP] libcbor will be updated to 0.11.0 in rawhide with a soname bump

[Gary Buhrmaster]

libcbor will be updated to 0.11.0 in rawhide in the
next week or so, which includes a soname bump.

The list of affected packages in rawhide are:

libfido2
fwupd

I will rebuild libfido2.  For fwupd, I will need the
maintainers (CC'ed) or a proven packager's assistance.

I have used the Mass Prebuild tool (mpb) to verify that
all the packages rebuild successfully, so I do not anticipate
any surprises.

Please use the side tag f40-build-side-82971

Thanks!
--
___
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-Mail-SPF] PR #2: 3.20240205 bump; Package tests

[Jitka Plesnikova]

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

Merged pull-request:

``
3.20240205 bump; Package tests
``

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

Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

[Dan Horák]

Hi,

could someone in the mingw team look at mingw-libgsf / libgsf (please
see the bug forwarded below)? If I see right, then the standalone
mingw-libgsf package should be retired as there are mingw builds from
the regular libgsf package, which seems to be regularly updated.


Thanks,

Dan



Begin forwarded message:

Date: Mon, 05 Feb 2024 00:09:44 +
From: bugzi...@redhat.com
Subject: [Bug 2066129] mingw-libgsf-1_14_52 is available


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

Upstream Release Monitoring
 changed:

   What|Removed |Added

Summary|mingw-libgsf-1_14_51 is |mingw-libgsf-1_14_52 is
   |available   |available



--- Comment #8 from Upstream Release Monitoring
 --- Releases retrieved:
1_14_52 Upstream release that is considered latest: 1_14_52
Current version/release in rawhide: 1.14.48-7.fc40
URL: http://www.gnome.org/projects/libgsf/

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


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2066129

Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202066129%23c8
--
___
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-Mail-SPF] PR #2: 3.20240205 bump; Package tests

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-Mail-SPF` that 
you are following:
``
3.20240205 bump; Package tests
``

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

Rawhide Beta Everything.iso and other ISOs -- btrfs -- serious issue

[Leslie Satenstein via devel]

I am not registered as an official test person. But I have been using Fedora 
for the past 20 years.

I have been doing some tests with  KDE,Gnome,xfce (all Fedora Rawhide distros).
With the Everything.iso, here is an example of a problem

I have a previous kde/gnome/kde installation that has pre-existing btrfs  / (eg 
root).The installation scripts have a checkmark indicated for reformat and I 
choose that for / which is, an existing btrfs that I wish to overwrite.There is 
no checkmark or option for delete/recreate of a btrfs partition.

With the installation scripts I tested, the new anaconda balks and will not 
allow reformat of any previously used existing btrfs formatted partition.  
With the Everything.iso, there is no way to excape to root, in order to perform 
a delete.
This shortcoming in the anaconda script means that I must exit the 
installation, use my existing Fedora 39 to delete the btrfs partition, and then 
try again. 

By the way, Fedora 39 Everything.iso has the delete partition (btrfs ) option

Do you want me to use bugzilla to post the above?  Better still if you format 
this email to the developer of the new anaconda interface.
Leslie SatensteinPS. Existing (Fedora 39 and earlier ) anaconda works 
perfectly.
--
___
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

[rawhide] libjpeg-turbo soname bump

[Frantisek Zatloukal]

In a few days, I'll start with bumping libjpeg-turbo in rawhide from 2.1.4
to 3.0.2 ( https://src.fedoraproject.org/rpms/libjpeg-turbo/pull-request/2
 ).

soname bump (0.2.0 to 0.3.0) is just for the turbojpeg consumers, libjpeg
so stays the same - API and ABI compatible, it's a drop-in replacement.

This would affect the following packages (All the consumers in rawhide
currently build fine both with the old and the new version. Impact checked
at https://copr.fedorainfracloud.org/coprs/frantisekz/turbojpeg-3/packages/
):
dcm
hyperhdr
imv
kf5-kwayland
kf5-kwindowsystem
krita
libjpeg-turbo
neatvnc
opentoonz
python-fslpy
VirtualGL
wayvnc
weston

If any of the maintainers would prefer to do the rebuild themselves, please
do feel free to speak up, I'll send the side-tag id here before the rebuild
starts. Otherwise, I'll handle all the rebuilds.


-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
--
___
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 2262788] Upgrade perl-Prima to 1.72

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 CC|ppi...@redhat.com   |
 Status|NEW |ASSIGNED



--- Comment #1 from Petr Pisar  ---
I know about it. Some tests fail on s390x.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262788

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262788%23c1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20240205.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20240203.n.0
NEW: Fedora-Rawhide-20240205.n.0

= SUMMARY =
Added images:5
Dropped images:  7
Added packages:  3
Dropped packages:9
Upgraded packages:   145
Downgraded packages: 0

Size of added packages:  65.56 KiB
Size of dropped packages:140.21 MiB
Size of upgraded packages:   6.80 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Silverblue ociarchive ppc64le
Path: 
Silverblue/ppc64le/images/Fedora-Silverblue-Rawhide.20240205.n.0.ociarchive
Image: Kinoite ociarchive ppc64le
Path: Kinoite/ppc64le/images/Fedora-Kinoite-Rawhide.20240205.n.0.ociarchive
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20240205.n.0.iso
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20240205.n.0.iso
Image: Astronomy_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-Rawhide-20240205.n.0.iso

= DROPPED IMAGES =
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20240203.n.0.ppc64le.qcow2
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20240203.n.0.iso
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20240203.n.0.ppc64le.raw.xz
Image: Server dvd ppc64le
Path: Server/ppc64le/iso/Fedora-Server-dvd-ppc64le-Rawhide-20240203.n.0.iso
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20240203.n.0.iso
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20240203.n.0.iso
Image: Server boot ppc64le
Path: Server/ppc64le/iso/Fedora-Server-netinst-ppc64le-Rawhide-20240203.n.0.iso

= ADDED PACKAGES =
Package: rust-sanitize-filename-0.5.0-1.fc40
Summary: Simple filename sanitizer, based on Node's sanitize-filename
RPMs:rust-sanitize-filename+default-devel rust-sanitize-filename-devel
Size:19.51 KiB

Package: rust-serde-big-array0.4-0.4.1-1.fc40
Summary: Big array helper for serde
RPMs:rust-serde-big-array0.4+default-devel rust-serde-big-array0.4-devel
Size:21.36 KiB

Package: sway-contrib-1.9~rc2-1.fc40
Summary: Collection of user-contributed scripts for Sway
RPMs:grimshot sway-contrib
Size:24.69 KiB


= DROPPED PACKAGES =
Package: mingw-dirac-1.0.2-32.fc40
Summary: Dirac is an open source video codec
RPMs:mingw32-dirac
Size:3.22 MiB

Package: rust-bitstream-io1-1.10.0-2.fc40
Summary: Library for reading/writing un-aligned values from/to streams
RPMs:rust-bitstream-io1+default-devel rust-bitstream-io1-devel
Size:43.83 KiB

Package: rust-gif0.11-0.11.4-3.fc40
Summary: GIF de- and encoder
RPMs:rust-gif0.11+default-devel rust-gif0.11+raii_no_panic-devel 
rust-gif0.11+std-devel rust-gif0.11-devel
Size:647.12 KiB

Package: rust-tiff0.6-0.6.1-4.fc40
Summary: TIFF decoding and encoding library in pure Rust
RPMs:rust-tiff0.6+default-devel rust-tiff0.6-devel
Size:1.35 MiB

Package: rust-winnow0.4-0.4.11-2.fc40
Summary: Byte-oriented, zero-copy, parser combinators library
RPMs:rust-winnow0.4+alloc-devel rust-winnow0.4+default-devel 
rust-winnow0.4+simd-devel rust-winnow0.4+std-devel 
rust-winnow0.4+unstable-doc-devel rust-winnow0.4-devel
Size:178.24 KiB

Package: seqan-1.4.2-53.fc40
Summary: Open source C++ library of efficient algorithms and data structures
RPMs:seqan seqan-devel seqan-doc
Size:67.36 MiB

Package: seqan2-2.4.0-22.fc40
Summary: C++ library of efficient algorithms and data structures
RPMs:seqan2-apps seqan2-examples seqan2-headers
Size:50.89 MiB

Package: sundials2-2.7.0-13.fc39
Summary: Suite of nonlinear solvers
RPMs:sundials2 sundials2-devel sundials2-doc sundials2-mpich 
sundials2-mpich-devel sundials2-openmpi sundials2-openmpi-devel
Size:9.94 MiB

Package: wise2-2.4.1-23.fc40
Summary: Tools for comparison of bio-polymers
RPMs:wise2 wise2-doc wise2-examples
Size:6.61 MiB


= UPGRADED PACKAGES =
Package:  COPASI-4.42.284-6.fc40
Old package:  COPASI-4.42.284-5.fc40
Summary:  Biochemical network simulator
RPMs: COPASI COPASI-data COPASI-doc COPASI-gui python3-COPASI
Size: 54.13 MiB
Size change:  -14.46 KiB
Changelog:
  * Sun Feb 04 2024 Antonio Trande  - 4.42.284-6
  - Exclude ix86 architectures


Package:  NsCDE-2.2-6.fc40
Old package:  NsCDE-2.2-5.fc40
Summary:  Modern and functional CDE desktop based on FVWM
RPMs: NsCDE NsCDE-data NsCDE-doc NsCDE-icon-theme
Added RPMs:   NsCDE-icon-theme
Size: 32.64 MiB
Size change:  4.24 MiB
Changelog:
  * Sat Feb 03 2024 Michel Lind  - 2.2-6
  - Split off icon theme
  - Move xsession file back into main package


Package:  PyQt-builder-1.15.4-1.fc40
Old package:  PyQt-builder-1.15.3-3.fc40
Summary:  The PEP 517 compliant PyQt build system

Re: Figure out what killed an app (rhbz#2253099)

[Yanko Kaneti]

On Mon, 2024-02-05 at 14:31 +0100, Florian Weimer wrote:
> * Yanko Kaneti:
> 
> > On Sat, 2024-02-03 at 13:29 +0100, Ondrej Mosnáček wrote:
> > > On Fri, 2 Feb 2024 at 17:52, Yanko Kaneti  wrote:
> > > > 
> > > > On Thu, 2024-02-01 at 09:44 +0100, Ondrej Mosnáček wrote:
> > > > > On Thu, 1 Feb 2024 at 09:13, Milan Crha  wrote:
> > > > > > The kernel tracing log for sig==9 shows:
> > > > > > 
> > > > > > gnome-terminal--2924[002] dN.2.  2520.462889: signal_generate:
> > > > > > sig=9 errno=0 code=128 comm=alloc-too-much pid=3502 grp=1 res=0
> > > > > > 
> > > > > > There is no such thing (apart of the tracing log) when Evolution is
> > > > > > suddenly killed, the logs are muted. That makes me believe it's not 
> > > > > > the
> > > > > > OOM killer whom kills the application. I'm back at square 1; or 
> > > > > > maybe
> > > > > > square 2, as I know possibly kernel sends it, but not why.
> > > > > 
> > > > > Try running `echo stacktrace >/sys/kernel/tracing/trace_options` (as
> > > > > root) and then collect the kernel trace again. That should give you a
> > > > > backtrace of kernel functions from the signal generation, which could
> > > > > help you/us to figure out the reason the process was killed.
> > > > 
> > > > So, figured the easiest way to help trigger the kill here is to put load
> > > > on the machine.
> > > > 
> > > >  $ stress-ng --cpu -1 --cpu-method all -t 5m --cpu-load 95
> > > > 
> > > > then starting evolution seems to do it almost every time shortly after
> > > > start (I have around 200k messages in the folder its trying to display)
> > > > 
> > > > I've enabled the stacktrace tracing option and like Milan set a sig==9
> > > > filter. And here is what I got in the trace buffer after it was killed
> > > > 
> > > > # tracer: nop
> > > > #
> > > > # entries-in-buffer/entries-written: 34/34   #P:16
> > > > #
> > > > #_-=> irqs-off/BH-disabled
> > > > #   / _=> need-resched
> > > > #  | / _---=> hardirq/softirq
> > > > #  || / _--=> preempt-depth
> > > > #  ||| / _-=> migrate-disable
> > > > #   / delay
> > > > #   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
> > > > #  | | |   | | |
> > > >evolution-9096[002] d..1.  1207.016489: signal_generate: 
> > > > sig=9 errno=0 code=128 comm=evolution pid=9096 grp=1 res=0
> > > >evolution-9096[002] d..1.  1207.016495: 
> > > >  => trace_event_raw_event_signal_generate
> > > >  => __send_signal_locked
> > > >  => posix_cpu_timers_work
> > > >  => task_work_run
> > > >  => irqentry_exit_to_user_mode
> > > >  => asm_sysvec_apic_timer_interrupt
> > > 
> > > So, browsing through the relevant kernel code, it seems the only cases
> > > which could have led to this backtrace are:
> > > 1. When a task's RT timeout goes over the RLIMIT_RTTIME hard limit
> > > (see function check_thread_timers() in
> > > kernel/time/posix-cpu-timers.c).
> > > 2. When a task's CPU time goes over the RLIMIT_CPU hard limit (see
> > > function check_process_timers() in kernel/time/posix-cpu-timers.c).
> > > 
> > > I may have missed some code path, but these resource limits should be
> > > the next thing to check.
> > 
> > Thanks a lot for diving it. This is probably it.
> > The kernel killing the main evolution process which was set as having rt
> > priority by some webkit coincidence.
> > 
> > Running with rtkit-daemon stoped and masked prevents the main evo
> > process being prioritized and consequently killed with higher load.
> > 
> > The fact that the kernel kills the (main)thread without a beep anywhere
> > in the logs is strange to me.
> 
> Interesting analysis, thanks!
> 
> I think it's not so unusual for the kernel not to log the SIGKILL.  This
> does not seem to be purely an emergency measure like the OOM killer—it's
> more like something that an application (set of processes) told the
> kernel to do to itself.  As such, it's not unreasonable for the
> application to do the logging.  On the other hand, I think it's
> difficult for rtkit-daemon to arrange for that logging because it can't
> monitor the target process directly.

Logical but leaves users like me scratching there head with mishaps like
these. Given that print-fatal-signals kernel param (which I just learned
about) is off by default.

> 
> Any idea why the signal is SIGKILL and not SIGXCPU?  To ensure that the
> process actually terminates promptly, without running signal handlers or
> generating a coredump?  SIGXCPU would point more directly to the cause.

No idea. I just saw kernel/time/poxis-cpu-timers.c after Ondrej
mentioned it. SIGXCPU for soft limits and KILL for hard it seems.


- Yanko
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to 

[Bug 2262788] New: Upgrade perl-Prima to 1.72

[bugzilla]

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

Bug ID: 2262788
   Summary: Upgrade perl-Prima to 1.72
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/Prima
Status: NEW
 Component: perl-Prima
  Assignee: ppi...@redhat.com
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: lkund...@v3.sk, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 1.71 version. Upstream released 1.72. When you have free
time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262788

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262788%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262786] New: Upgrade perl-Mail-SPF to 3.20240205

[bugzilla]

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

Bug ID: 2262786
   Summary: Upgrade perl-Mail-SPF to 3.20240205
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/Mail-SPF
Status: NEW
 Component: perl-Mail-SPF
  Assignee: jples...@redhat.com
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: jpazdzi...@redhat.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 2.9.0 version. Upstream released 3.20240205. When you
have free time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262786

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262786%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262785] New: Upgrade perl-Image-ExifTool to 12.76

[bugzilla]

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

Bug ID: 2262785
   Summary: Upgrade perl-Image-ExifTool to 12.76
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/Image-ExifTool
Status: NEW
 Component: perl-Image-ExifTool
  Assignee: spo...@gmail.com
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, spo...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 12.70 version. Upstream released 12.76. When you have
free time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262785

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262785%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2262784] New: Upgrade perl-CGI-Simple to 1.281

[bugzilla]

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

Bug ID: 2262784
   Summary: Upgrade perl-CGI-Simple to 1.281
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/CGI-Simple
Status: NEW
 Component: perl-CGI-Simple
  Assignee: spo...@gmail.com
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, spo...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 1.280 version. Upstream released 1.281. When you have
free time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2262784

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202262784%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Figure out what killed an app (rhbz#2253099)

[Florian Weimer]

* Yanko Kaneti:

> On Sat, 2024-02-03 at 13:29 +0100, Ondrej Mosnáček wrote:
>> On Fri, 2 Feb 2024 at 17:52, Yanko Kaneti  wrote:
>> > 
>> > On Thu, 2024-02-01 at 09:44 +0100, Ondrej Mosnáček wrote:
>> > > On Thu, 1 Feb 2024 at 09:13, Milan Crha  wrote:
>> > > > The kernel tracing log for sig==9 shows:
>> > > > 
>> > > > gnome-terminal--2924[002] dN.2.  2520.462889: signal_generate:
>> > > > sig=9 errno=0 code=128 comm=alloc-too-much pid=3502 grp=1 res=0
>> > > > 
>> > > > There is no such thing (apart of the tracing log) when Evolution is
>> > > > suddenly killed, the logs are muted. That makes me believe it's not the
>> > > > OOM killer whom kills the application. I'm back at square 1; or maybe
>> > > > square 2, as I know possibly kernel sends it, but not why.
>> > > 
>> > > Try running `echo stacktrace >/sys/kernel/tracing/trace_options` (as
>> > > root) and then collect the kernel trace again. That should give you a
>> > > backtrace of kernel functions from the signal generation, which could
>> > > help you/us to figure out the reason the process was killed.
>> > 
>> > So, figured the easiest way to help trigger the kill here is to put load
>> > on the machine.
>> > 
>> >  $ stress-ng --cpu -1 --cpu-method all -t 5m --cpu-load 95
>> > 
>> > then starting evolution seems to do it almost every time shortly after
>> > start (I have around 200k messages in the folder its trying to display)
>> > 
>> > I've enabled the stacktrace tracing option and like Milan set a sig==9
>> > filter. And here is what I got in the trace buffer after it was killed
>> > 
>> > # tracer: nop
>> > #
>> > # entries-in-buffer/entries-written: 34/34   #P:16
>> > #
>> > #_-=> irqs-off/BH-disabled
>> > #   / _=> need-resched
>> > #  | / _---=> hardirq/softirq
>> > #  || / _--=> preempt-depth
>> > #  ||| / _-=> migrate-disable
>> > #   / delay
>> > #   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
>> > #  | | |   | | |
>> >evolution-9096[002] d..1.  1207.016489: signal_generate: sig=9 
>> > errno=0 code=128 comm=evolution pid=9096 grp=1 res=0
>> >evolution-9096[002] d..1.  1207.016495: 
>> >  => trace_event_raw_event_signal_generate
>> >  => __send_signal_locked
>> >  => posix_cpu_timers_work
>> >  => task_work_run
>> >  => irqentry_exit_to_user_mode
>> >  => asm_sysvec_apic_timer_interrupt
>> 
>> So, browsing through the relevant kernel code, it seems the only cases
>> which could have led to this backtrace are:
>> 1. When a task's RT timeout goes over the RLIMIT_RTTIME hard limit
>> (see function check_thread_timers() in
>> kernel/time/posix-cpu-timers.c).
>> 2. When a task's CPU time goes over the RLIMIT_CPU hard limit (see
>> function check_process_timers() in kernel/time/posix-cpu-timers.c).
>> 
>> I may have missed some code path, but these resource limits should be
>> the next thing to check.
>
> Thanks a lot for diving it. This is probably it.
> The kernel killing the main evolution process which was set as having rt
> priority by some webkit coincidence.
>
> Running with rtkit-daemon stoped and masked prevents the main evo
> process being prioritized and consequently killed with higher load.
>
> The fact that the kernel kills the (main)thread without a beep anywhere
> in the logs is strange to me.

Interesting analysis, thanks!

I think it's not so unusual for the kernel not to log the SIGKILL.  This
does not seem to be purely an emergency measure like the OOM killer—it's
more like something that an application (set of processes) told the
kernel to do to itself.  As such, it's not unreasonable for the
application to do the logging.  On the other hand, I think it's
difficult for rtkit-daemon to arrange for that logging because it can't
monitor the target process directly.

Any idea why the signal is SIGKILL and not SIGXCPU?  To ensure that the
process actually terminates promptly, without running signal handlers or
generating a coredump?  SIGXCPU would point more directly to the cause.

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

Re: Heads-up: abseil-cpp 20240116.0 coming to F40/Rawhide

[Ben Beasley]

The rebuild is complete, and the side tag is merged via [1]. As of this 
writing, it is waiting on test gating.


Including parlaylib was an error on my part, since it is header-only and 
none of its binary packages depend on abseil-cpp. Nevertheless, 
parlaylib started to FTBFS in Rawhide after the initial announcement and 
before the rebuild, so I filed a bug[2].


The syslog-ng package already failed in the mass rebuild[3] because it 
FTBFS on i686[4], which is related to the Change PortingToModernC[5]. 
Since I knew rebuilding this package would fail (and a scratch build 
confirmed this[6] and showed that it actually fails on *all* 
architectures now), I did not bother to push a rebuild commit. Note that 
dropping i686 support from syslog-ng would require dropping it in 
perl-Unix-Syslog and therefore in a number of other packages. This is 
still probably feasible. I expect that syslog-ng-opentelemetry will now 
FTI until the package can be rebuilt in Rawhide and (post-branching) 
F40[7]. I am in contact with the syslog-ng maintainers via Bugzilla and 
have offered my assistance if they run into any trouble.


All other packages were successfully rebuilt.

If you think I missed something, let me know and I’ll help clean it up!

[1] https://bodhi.fedoraproject.org/updates/FEDORA-2024-ce6bbab91a

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

[3] https://bugzilla.redhat.com/show_bug.cgi?id=2261744

[4] https://bugzilla.redhat.com/show_bug.cgi?id=2258853

[5] 
https://fedoraproject.org/wiki/Changes/PortingToModernC#Use_of_incompatible_pointer_types_without_a_cast


[6] https://koji.fedoraproject.org/koji/taskinfo?taskID=112924642

[7] https://bugzilla.redhat.com/show_bug.cgi?id=2261744#c8

On 1/28/24 13:43, Ben Beasley wrote:
In one week, 2024-02-04, or slightly later, I plan to update 
abseil-cpp from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 
2024)[1] in side tags for F40/Rawhide. If I miss getting the update 
into Rawhide before F40 branching, I plan to do the update in both 
F41/Rawhide and F40/Branched.


Like all new calendar versions of abseil-cpp, this breaks ABI 
compatibility and bumps the SONAME version. There are also some small 
intentional breaking API changes[2].


Testing in COPR[3] indicates all directly-dependent packages are 
compatible, except mozc, which can be fixed by a PR[4].


Besides abseil-cpp, I plan to rebuild all dependent packages using 
maintainer/co-maintainer or provenpackager privileges. I also plan to 
merge the mozc PR if it is still open. These packages are:


    - bear
    - bloaty
    - credentials-fetcher
    - CuraEngine_grpc_definitions
    - fastnetmon
    - fcitx5-mozc
    - frr
    - grpc
    - ilbc
    - libarrow
    - libphonenumber
    - mozc
    - onnxruntime
    - parlaylib
    - plasma-dialer
    - qmlkonsole
    - qt6-qtgrpc
    - spacebar
    - syslog-ng

Of these, I expect plasma-dialer and syslog-ng to FTBFS in the side 
tag since they already FTBFS in Rawhide.


Maintainers of all affected packages should have received this email 
directly (by BCC rather than CC, to keep the message from being held 
for moderation due to a long CC list).


If you want to handle the rebuild of the package yourself, or you have 
other questions or concerns, please just let me know before 2024-02-04.


– Ben Beasley (FAS: music)


[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/16

[2] https://github.com/abseil/abseil-cpp/releases/tag/20240116.0

[3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/

[4] https://src.fedoraproject.org/rpms/mozc/pull-request/6



--
___
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: Retirement of sundials2 seqan seqan2 wise2

[Dominik 'Rathann' Mierzejewski]

Hi!

On Saturday, 03 February 2024 at 22:01, Antonio T. sagitter wrote:
> Hi all.
> 
> Following packages will be retired in Rawhide branch:

[...]
> wise2 (unmaintained by upstream, no longer needed in Fedora),
> https://src.fedoraproject.org/rpms/wise2

Can you drop my name from Bugzilla Assignee for EPEL before you retire?
I no longer maintain the EPEL7 branch.

Regards,
Dominik
-- 
Fedora   https://fedoraproject.org
Deep in the human unconscious is a pervasive need for a logical universe that
makes sense. But the real universe is always one step beyond logic.
-- from "The Sayings of Muad'Dib" by the Princess Irulan
--
___
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: Mounting USB Storage devices with "sync" option ?

[Simon Farnsworth via devel]

On Friday, 2 February 2024 21:47:00 GMT Dominique Martinet wrote:
> So I think Florian is correct in that barriers won't be issued on
> these disks, and if they internally have such a cache it'd probably be
> unsafe...
> 
> Now does the disk itself know that it's in such an enclosure and
> properly behaves as write through?
> I think we'd have a lot more corruptions on our hands if it was
> incorrect here, btrfs in particular is very sensitive to disks that
> lie with barriers but I'm not sure how much it's used on such drivers.
> 
As far as I can tell, having owned such an enclosure in the past, it doesn't 
tell the drive anything - it relies on the fact that SATA drives write back 
fairly aggressively when the command interface is idle, and thus the cache is 
fully written back to the medium when it's idle for a few seconds. If you go 
through the sequence "remove safely", then wait for UI confirmation, then 
unplug the USB port, it'll usually have written back the cache before you 
physically move your hands to the USB cable.

As these enclosures aren't particularly fast (for example, commands must 
complete in issue order, rather than being able to complete out of order as in 
TCQ/NCQ), I suspect most users of them don't use btrfs or xfs on them (I'd 
expect ext4 if Linux-only, FAT32, exFAT or NTFS if shared between OSes); 
they're basically intended to let you have a huge "thumb drive" for machine-
to-machine transfer, and they're fine in that use case.

On the other hand, turning on the "sync" mount option doesn't help with these 
enclosures; if anything, it'll make things worse by increasing the number of 
commands in flight which have to be handled before the drive switches to 
cleaning its cache.
-- 
Simon Farnsworth

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

[Zbigniew Jędrzejewski-Szmek]

On Sun, Feb 04, 2024 at 11:07:43PM +, Luis Correia wrote:
> Hi, I'm a long time Fedora user and used to help develop the Ralink
> Wireless driver (rt2x00) that's been present in the kernel for a long time.
> 
> I'm now entering the process of helping maintain the mixxx package over at
> rpmfusion.
> 
> Hope to be useful with this new venture.

Cool. Welcome.

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Zbigniew Jędrzejewski-Szmek]

On Sun, Feb 04, 2024 at 03:55:42AM +0100, Kevin Kofler via devel wrote:
> I can, though, speak for myself, and I am frankly surprised that you are 
> offended by the tone of my messages.

Kevin, thank you for the way you're participating in this thread.
Your civil tone and patience and writing about facts more than
opinions is appreciated. This difficult discussion could have been
much more difficult otherwise.

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

Re: [Test-Announce] 2024-02-05 @ 16:00 UTC - Fedora QA Meeting

[Peter Boy]

I would like to discuss about 

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

In connection with

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

and how to proceed with this.

As far as we know now, there is a config parameter to turn on/off whether a 
vgscan/vgchange/etc should inspect new or all connected devices of just devices 
in the/etc/lvm/devices/system.devices file.

It is a feature that upstream introduced some time ago. Upstream turn the 
parameter off, so that LVM inspected all devices after introducing  the feature 
and behaved as previously. LVM maintainer turn the parameter on, instead. Until 
now we have no information why they did it. We have no feedback in the bug nor 
on a direct email so far.

We have to consider if it is preferable to return to the previous state of the 
device file parameter.





> Am 05.02.2024 um 02:50 schrieb Adam Williamson :
> 
> # Fedora Quality Assurance Meeting
> # Date: 2024-02-05
> # Time: 16:00 UTC
> (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
> # Location:
> https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org
> 
> Greetings testers! It's meeting time again, and once again we'll
> be on Matrix.
> 
> If anyone has any other items for the agenda, please reply to this
> email and suggest them! Thanks.
> 
> == Proposed Agenda Topics ==
> 
> 1. Previous meeting follow-up
> 2. Fedora 40 check-in
> 3. Test Day / community event status
> 4. Open floor
> -- 
> Adam Williamson (he/him/his)
> Fedora QA
> Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
> https://www.happyassassin.net
> 
> 
> 
> 
> 
> -- 
> Adam Williamson (he/him/his)
> Fedora QA
> Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
> https://www.happyassassin.net
> --
> ___
> 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

--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast






--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast



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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Zbigniew Jędrzejewski-Szmek]

On Mon, Feb 05, 2024 at 10:34:13AM +1000, Peter Hutterer wrote:
> > And even before that, things were already only limping along. That was
> > happening for over a decade and in that timeframe *nobody* has wanted
> > to step up and work on it. Wayland is the future because otherwise we
> > have no graphics future, as things currently stand.
> 
> It also doesn't help that the "it's the same people working on X and
> Wayland" argument means that, absent significant breakthroughs in
> space-time research, we can work on one or the other, not both.
> Something's got to give.

We could also switch to a 4-day week, with 20h shifts ;)

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

Upcomming passwd utility change

[Tomas Halman]

Hi guys,

As a part of the libuser deprecation effort [1]
 we are going to
replace passwd in Fedora (now coming from separate project) with the one
coming from shadow utils.

The utilities are pretty the same but there are minor differences described
in the change page (some options have different names like --minimum is now
--mindays).

The missing --stdin option has been implemented in shadow utils passwd.

You may need to update your scripts in case they use passwd with old long
switch names.
Sorry for inconvenience.

Tomáš

-- 

Tomáš Halman

thal...@redhat.com

T: +420 727 830 769 <+420727830769>
*../``\..* Red Hat 


[1] https://fedoraproject.org/wiki/Changes/LibuserDeprecation
--
___
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