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

2024-03-27 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3f86ec863a   
seamonkey-2.53.18.2-1.el7


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

chromium-123.0.6312.58-1.el7

Details about builds:



 chromium-123.0.6312.58-1.el7 (FEDORA-EPEL-2024-15cde9f00b)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

Update to 123.0.6312.58
 * High CVE-2024-2625: Object lifecycle issue in V8
 * Medium CVE-2024-2626: Out of bounds read in Swiftshader
 * Medium CVE-2024-2627: Use after free in Canvas
 * Medium CVE-2024-2628: Inappropriate implementation in Downloads
 * Medium CVE-2024-2629: Incorrect security UI in iOS
 * Medium CVE-2024-2630: Inappropriate implementation in iOS
 * Low CVE-2024-2631: Inappropriate implementation in iOS

ChangeLog:

* Wed Mar 20 2024 Than Ngo  - 123.0.6312.58-1
- update to 123.0.6312.58
   * High CVE-2024-2625: Object lifecycle issue in V8
   * Medium CVE-2024-2626: Out of bounds read in Swiftshader
   * Medium CVE-2024-2627: Use after free in Canvas
   * Medium CVE-2024-2628: Inappropriate implementation in Downloads
   * Medium CVE-2024-2629: Incorrect security UI in iOS
   * Medium CVE-2024-2630: Inappropriate implementation in iOS
   * Low CVE-2024-2631: Inappropriate implementation in iOS
* Fri Mar 15 2024 Than Ngo  - 123.0.6312.46-1
- update to 123.0.6312.46

References:

  [ 1 ] Bug #2269307 - CVE-2024-2400 chromium: chromium-browser: Use after free 
in Performance Manager [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2269307
  [ 2 ] Bug #2270390 - CVE-2024-2626 CVE-2024-2627 CVE-2024-2628 CVE-2024-2629 
CVE-2024-2630 CVE-2024-2631 chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270390
  [ 3 ] Bug #2270392 - CVE-2024-2625 chromium: chromium-browser: Object 
lifecycle issue in V8 [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270392


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


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

2024-03-27 Thread updates
The following Fedora EPEL 9 Security updates need testing:
 Age  URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-684f77a897   
podman-tui-1.0.0-1.el9
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-5d9511ad6e   
prometheus-podman-exporter-1.11.0-1.el9
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3e437ee2d0   
pandoc-2.14.0.3-17.el9 patat-0.8.7.0-4.el9
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-1e7f709e59   
suricata-6.0.17-1.el9
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-5e764f8789   
opensmtpd-7.4.0p1-1.el9


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

chromium-123.0.6312.58-1.el9
netdata-1.45.1-1.el9
python-damo-2.2.7-1.el9
redict-7.3.0~rc1-1.el9
sbsigntools-0.9.5-3.el9
tinyxml-2.6.2-28.el9

Details about builds:



 chromium-123.0.6312.58-1.el9 (FEDORA-EPEL-2024-24aceec24b)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

Update to 123.0.6312.58
 * High CVE-2024-2625: Object lifecycle issue in V8
 * Medium CVE-2024-2626: Out of bounds read in Swiftshader
 * Medium CVE-2024-2627: Use after free in Canvas
 * Medium CVE-2024-2628: Inappropriate implementation in Downloads
 * Medium CVE-2024-2629: Incorrect security UI in iOS
 * Medium CVE-2024-2630: Inappropriate implementation in iOS
 * Low CVE-2024-2631: Inappropriate implementation in iOS

ChangeLog:

* Wed Mar 20 2024 Than Ngo  - 123.0.6312.58-1
- update to 123.0.6312.58
   * High CVE-2024-2625: Object lifecycle issue in V8
   * Medium CVE-2024-2626: Out of bounds read in Swiftshader
   * Medium CVE-2024-2627: Use after free in Canvas
   * Medium CVE-2024-2628: Inappropriate implementation in Downloads
   * Medium CVE-2024-2629: Incorrect security UI in iOS
   * Medium CVE-2024-2630: Inappropriate implementation in iOS
   * Low CVE-2024-2631: Inappropriate implementation in iOS
* Fri Mar 15 2024 Than Ngo  - 123.0.6312.46-1
- update to 123.0.6312.46

References:

  [ 1 ] Bug #2269307 - CVE-2024-2400 chromium: chromium-browser: Use after free 
in Performance Manager [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2269307
  [ 2 ] Bug #2270390 - CVE-2024-2626 CVE-2024-2627 CVE-2024-2628 CVE-2024-2629 
CVE-2024-2630 CVE-2024-2631 chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270390
  [ 3 ] Bug #2270392 - CVE-2024-2625 chromium: chromium-browser: Object 
lifecycle issue in V8 [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270392




 netdata-1.45.1-1.el9 (FEDORA-EPEL-2024-99d0280e19)
 Real-time performance monitoring

Update Information:

Update from upstream

ChangeLog:

* Wed Mar 27 2024 Didier Fabert  1.45.1-1
- Update from upstream
* Thu Mar 21 2024 Didier Fabert  1.45.0-1
- Update from upstream

References:

  [ 1 ] Bug #2270902 - netdata-1.45.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270902




 python-damo-2.2.7-1.el9 (FEDORA-EPEL-2024-987d9aa9f1)
 Data Access Monitoring Operator

Update Information:

v2.2.7
Support region box right-side aligning (--region_box_align) of 'damo show'
Cleanup code
v2.2.6
Cleanup code

ChangeLog:

* Tue Mar 26 2024 Packit  - 2.2.7-1
- Update to 2.2.7
- Resolves rhbz#2271542
* Tue Mar 19 2024 Packit  - 2.2.6-1
- Update to 2.2.6
- Resolves rhbz#2270231

References:

  [ 1 ] Bug #2271542 - python-damo-2.2.7 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2271542




 redict-7.3.0~rc1-1.el9 (FEDORA-EPEL-2024-5e3399739d)
 A persistent key-value database

Update Information:

initial package 

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

2024-03-27 Thread updates
The following Fedora EPEL 8 Security updates need testing:
 Age  URL
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a4cbda11c6   
suricata-6.0.17-1.el8
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-8f366635a6   
seamonkey-2.53.18.2-1.el8


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

chromium-123.0.6312.58-1.el8
netdata-1.45.1-1.el8
redict-7.3.0~rc1-1.el8
tinyxml-2.6.2-28.el8

Details about builds:



 chromium-123.0.6312.58-1.el8 (FEDORA-EPEL-2024-fc233c6d2e)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

Update to 123.0.6312.58
 * High CVE-2024-2625: Object lifecycle issue in V8
 * Medium CVE-2024-2626: Out of bounds read in Swiftshader
 * Medium CVE-2024-2627: Use after free in Canvas
 * Medium CVE-2024-2628: Inappropriate implementation in Downloads
 * Medium CVE-2024-2629: Incorrect security UI in iOS
 * Medium CVE-2024-2630: Inappropriate implementation in iOS
 * Low CVE-2024-2631: Inappropriate implementation in iOS

ChangeLog:

* Wed Mar 20 2024 Than Ngo  - 123.0.6312.58-1
- update to 123.0.6312.58
   * High CVE-2024-2625: Object lifecycle issue in V8
   * Medium CVE-2024-2626: Out of bounds read in Swiftshader
   * Medium CVE-2024-2627: Use after free in Canvas
   * Medium CVE-2024-2628: Inappropriate implementation in Downloads
   * Medium CVE-2024-2629: Incorrect security UI in iOS
   * Medium CVE-2024-2630: Inappropriate implementation in iOS
   * Low CVE-2024-2631: Inappropriate implementation in iOS
* Fri Mar 15 2024 Than Ngo  - 123.0.6312.46-1
- update to 123.0.6312.46

References:

  [ 1 ] Bug #2269307 - CVE-2024-2400 chromium: chromium-browser: Use after free 
in Performance Manager [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2269307
  [ 2 ] Bug #2270390 - CVE-2024-2626 CVE-2024-2627 CVE-2024-2628 CVE-2024-2629 
CVE-2024-2630 CVE-2024-2631 chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270390
  [ 3 ] Bug #2270392 - CVE-2024-2625 chromium: chromium-browser: Object 
lifecycle issue in V8 [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2270392




 netdata-1.45.1-1.el8 (FEDORA-EPEL-2024-4e50496ed5)
 Real-time performance monitoring

Update Information:

Update from upstream

ChangeLog:

* Wed Mar 27 2024 Didier Fabert  1.45.1-1
- Update from upstream
* Thu Mar 21 2024 Didier Fabert  1.45.0-1
- Update from upstream

References:

  [ 1 ] Bug #2270902 - netdata-1.45.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2270902




 redict-7.3.0~rc1-1.el8 (FEDORA-EPEL-2024-d9878ed2b4)
 A persistent key-value database

Update Information:

initial package build

ChangeLog:

* Sun Mar 24 2024 Jonathan Wright  - 7.3.0~rc1-1
- Initial package build, release candidate

References:

  [ 1 ] Bug #2271615 - Review Request: redict - A persistent key-value database
https://bugzilla.redhat.com/show_bug.cgi?id=2271615




 tinyxml-2.6.2-28.el8 (FEDORA-EPEL-2024-0ced8d6066)
 A simple, small, C++ XML parser

Update Information:

Security fixes for CVE-2021-42260, CVE-2023-34194 and its duplicate
CVE-2023-40462.
Fix incorrect text element encoding (upstream isssue #51).
Enable tests.

ChangeLog:

* Wed Jan  3 2024 Dominik Mierzejewski  - 2.6.2-28
- apply Debian patch to fix CVE-2021-42260 (rhbz#2253716, rhbz#2253718)
- apply Debian patch to fix CVE-2023-34194 and its duplicate, CVE-2023-40462
  (rhbz#2254376, rhbz#2254381)
- fix incorrect text element encoding (upstream isssue #51)

[Bug 2271821] perl-DBD-MySQL: improper use of the %{eln} macro

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271821



--- Comment #4 from Fedora Update System  ---
FEDORA-2024-8d07fa18c7 has been pushed to the Fedora 40 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-8d07fa18c7`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8d07fa18c7

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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271821%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 2271724] perl-URI-5.28 is available

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271724



--- Comment #4 from Fedora Update System  ---
FEDORA-2024-2671431b9f has been pushed to the Fedora 40 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-2671431b9f`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2671431b9f

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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271724%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 2267346] Please branch and build perl-Fuse for EPEL9

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2267346

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Fuse-0.16.1-27.el9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2024-03-28 01:06:14



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2024-b9c3804d4d (perl-Fuse-0.16.1-27.el9) has been pushed to the
Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202267346%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 2270256] perl-DBD-MySQL-5.004 is available

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2270256

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-DBD-MySQL-5.004-1.fc41 |perl-DBD-MySQL-5.004-1.fc41
   ||perl-DBD-MySQL-5.004-1.fc40



--- Comment #5 from Fedora Update System  ---
FEDORA-2024-277e98e1b9 (perl-DBD-MySQL-5.004-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=2270256

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270256%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


[Bug 2270204] perl-Variable-Magic-0.64 is available

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2270204

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Variable-Magic-0.64-1. |perl-Variable-Magic-0.64-1.
   |fc41|fc41
   ||perl-Variable-Magic-0.64-1.
   ||fc40



--- Comment #5 from Fedora Update System  ---
FEDORA-2024-fef134e490 (perl-Variable-Magic-0.64-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=2270204

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270204%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: %pyproject_buildrequires -r/-x: Attempt to read runtime dependencies from pyproject.toml?

2024-03-27 Thread Maxwell G
On Wed Mar 27, 2024 at 15:48 +0100, Karolina Surma wrote:
> Hello,

Hi Karolina,

Thank you for bring this to the mailing list.

> recently, we were suggested an improvement for %pyproject_buildrequires 
> -r/-x.
> We could read the project's runtime dependencies (if they're not marked 
> as `dynamic`) from pyproject.toml [project] table directly, without 
> calling prepare_metadata_for_build_wheel or building the wheel to read 
> the dependency metadata from it.

> Reading the metadata via prepare_metadata_for_build_wheel is already 
> quite fast, however implementing that hook is optional for the build 
> backends.

I'll note that all build backends packaged in Fedora (setuptools,
hatchling, flit-core, poetry-core, the pdm one, and scikit) other than
meson-python support this hook. Only 9 packages BuildRequire
python3-meson-python.

> Maxwell has raised some valid concerns there:
> - Other tools (build frontends, e.g. pip/build) call 
> prepare_metadata_for_build_wheel, our macros would diverge in 
> functionality compared to the rest of the landscape.
> - pyproject.toml's [project] may not be the source of metadata that the 
> build backend uses. A project could switch to a build backend without 
> PEP 621 support (e.g. poetry-core) and forget to remove the [project] table.
> - There can be potential differences between BuildRequires and Requires 
> generators when one generates dependencies based on the pyproject.toml 
> [project] table while the other on the packaged dist-info metadata.
> - Using macros to build on older systems: e.g. RHEL 9's old setuptools 
> version silently ignores the pyproject.toml [project] table - 
> %pyproject_buildrequires could still pull the dependency information 
> from it, but the resulting package would be broken because it did not 
> include those in the packaged dist-info metadata.

I could not have said it better myself :D.

> One way to mitigate would be to make the proposed behavior opt-in only, 
> with the possibility to either build wheel with -w option (already 
> existing) or e.g. -p (now-proposed: reading from pyproject.toml) in case 
> backend doesn't have prepare_metadata_for_build_wheel.

Yeah, I think -p (for *p*yproject) is good flag name choice.

> However, this adds a layer of complexity for packagers and macros
> maintainers.

> The questions we'd love your input for:
>  - Should this behavior exist but not be the default (explicit flag 
> would be required to opt-in)?

I consider this the only reasonable solution other than not implementing
the feature at all.

>  - Can you think of a better alternative than the ones described here?

I guess I will throw something out there, but I am not convinced it is a
great idea: what about making the `-p` flag fail if
`prepare_metadata_for_build_wheel` is available? In my opinion, this
should only be a last resort for backends that do not implement the hook.

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


Re: So you can't just copy 'sources' from one package to another?

2024-03-27 Thread Sérgio Basto
On Fri, 2024-03-08 at 16:19 +, Richard W.M. Jones wrote:
> For mingw-* packages we (sometimes) have a separate package from the
> native package, eg. libgcrypt vs mingw-libgcrypt.  Therefore two
> different packages are sometimes built with the exact same sources.
> 
> However I discovered copying 'sources' (ie the file) from libgcrypt
> dist-git to mingw-libgcrypt dist-git alone isn't sufficient to get
> the
> package to build.  You still have to download the source tarballs in
> libgcrypt, copy them to mingw-libgcrypt, and 'fedpkg new-sources
> ' to upload them again.
> 
> Isn't the lookaside cache shared across the whole of Fedora?
> 
> (This doesn't matter, I was just wondering aloud.)


you may request an RFE on fedpkg-minimal [1] , fedpkg-minimal is
responsible for download the sources of the packages when koji starts
the builds. Take a look in fedpkg-base [2] is a very simple script , 
It shouldn't be difficult do what you ask, I think, it will be more
complicated define the concept and be accepted by upstream . 

Best regards


[1]
https://pagure.io/fedpkg-minimal 

[2]
https://pagure.io/fedpkg-minimal/blob/master/f/bin/fedpkg-base

> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog:
> http://rwmj.wordpress.com
> virt-p2v converts physical machines to virtual machines.  Boot with a
> live CD or over the network (PXE) and turn machines into KVM guests.
> http://libguestfs.org/virt-v2v
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

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


Fedora CoreOS Community Meeting Minutes 2024-03-27

2024-03-27 Thread Adam Piasecki
Minutes:
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-03-27/fedora-coreos-meeting.2024-03-27-16.30.html
Minutes (text):
https://meetbot-raw.fedoraproject.org//meeting-1_matrix_fedoraproject-org/2024-03-27/fedora-coreos-meeting.2024-03-27-16.30.txt
Log:
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-03-27/fedora-coreos-meeting.2024-03-27-16.30.log.html

=
# #meeting-1:fedoraproject.org: fedora_coreos_meeting
=

Meeting started by @apiaseck:matrix.org at 2024-03-27 16:30:00



Meeting summary
---
* TOPIC: roll call (@apiaseck:matrix.org, 16:30:29)
* TOPIC: Action items from last meeting (@apiaseck:matrix.org, 16:33:54)
* ACTION: Veify with fifofonix if there is consensus (1.28 cluster
with zswap), that checking the `--flag` is useful/relevant
(@apiaseck:matrix.org, 16:40:53)
* TOPIC: Platform Request: Akamai Connected Cloud (Linode)
(@apiaseck:matrix.org, 16:42:20)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1701
(@apiaseck:matrix.org, 16:42:28)
* AGREED: We think this is a good idea. We will reserve the akamai
platform ID for the Akamai Connected Cloud (Linode) platform and
support the contributors from Akamai on adding support for it.
(@apiaseck:matrix.org, 17:01:34)
* TOPIC: New Package Request: zip (@apiaseck:matrix.org, 17:03:20)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1690
(@apiaseck:matrix.org, 17:03:27)
* AGREED: We will document how to use bsdtar to unzip files
(@apiaseck:matrix.org, 17:30:59)
* TOPIC: F39 drops some firmware packages that provide wifi/BT
firmware (@apiaseck:matrix.org, 17:32:52)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1575
(@apiaseck:matrix.org, 17:33:07)
* TOPIC: Open Floor (@apiaseck:matrix.org, 17:53:37)
* INFO: our `next` stream is now on F40 (beta) content
(@dustymabe:matrix.org, 17:54:15)

Meeting ended at 2024-03-27 17:59:56

Action items

* Veify with fifofonix if there is consensus (1.28 cluster with
zswap), that checking the `--flag` is useful/relevant

People Present (lines said)
---
* @dustymabe:matrix.org (67)
* @siosm:matrix.org (59)
* @apiaseck:matrix.org (47)
* @phrozenbyte:matrix.org (15)
* @jlebon:fedora.im (12)
* @zodbot:fedora.im (11)
* @fifofonix:matrix.org (11)
* @jbtrystram:matrix.org (9)
* @aaradhak:matrix.org (5)
* @jmarrero:matrix.org (5)
* @ravanelli:matrix.org (3)
* @meetbot:fedora.im (2)
* @marmijo:fedora.im (2)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [SPDX] Mass license change: Intro and change of "Bitstream Vera" to "Bitstream-Vera"

2024-03-27 Thread Otto Liljalaakso

27. maaliskuuta 2024 12.59.11 GMT+02:00 Petr Pisar  
kirjoitti:
>V Tue, Mar 26, 2024 at 02:52:50PM +0100, Miroslav Suchý napsal(a):
>> I have no strong opinion how to process with the case of  "MIT and BSD and
>> Bitstream Vera and OFL". I think that converting it to " MIT and BSD and
>> Bitstream-Vera and OFL" is probably best option. I.e. the License tag will
>> become mixture of Callaway and SPDX. It will not make it valid SPDX formula
>> so it will still pop up as package to be fixed, but at least some work will
>> be done.
>
>In other words, it will be a regression. Invalid by either system:
>
>$ license-validate 'MIT AND BSD AND Bitstream-Vera and OFL'
>Not a valid license string
>Run with -v option to see more information.
>$ license-validate --old 'MIT AND BSD AND Bitstream-Vera and OFL'
>Not a valid license string
>Run with -v option to see more information.
>
>I wouldn't do it.
>
>If you want to hint the packager, then open a pull request with the partial
>conversion.
>
>-- Petr

I also think the conversion should only be done if the full License string can 
be converted. Partial conversion is confusing, and there is not much value, 
since trivial conversion is, well, trivial, and whoever will eventually need to 
take a look at the nontrivial parts can easily handle it then.
--
___
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: some man pages have bugs, can't be grep'd

2024-03-27 Thread Tim Landscheidt
I wrote a very long time ago:

>> I've been seeing this since clean installing Fedora 30. I don't recall
>> ever seeing it before, including on a Fedora 29 -> Fedora 30 upgraded
>> system (is now the clean installed system).

>> [chris@flap ~]$ man rpm | grep -C 10 rpmverbosity
>> :176: warning [p 3, 0.8i]: cannot adjust line
>> [chris@flap mantest]$ man rpm >rpm.stdout 2>rpm.stderr
>> [chris@flap mantest]$ ll
>> -rw-rw-r--. 1 chris chris62 Jul 16 14:24 rpm.stderr
>> -rw-rw-r--. 1 chris chris 28498 Jul 16 14:24 rpm.stdout

>> Is this a bug that should be reported against rpm or something else?
>> I'm certain I've seen it in other man pages, but offhand I can't find
>> another example.

> (This also happens on Fedora 29, JFTR.)  The warning seems
> to stem from this line in rpm.8:

> | […]
> | 175 The default \fIFILELIST\fR is
> | 176 
> \fI/usr/\:lib/\:rpm/\:macros\fR:\:\fI/usr/\:lib/\:rpm/\:macros.d/\:macros.*\fR:\:\fI/usr/\:lib/\:rpm/\:platform/\:%{_target}/\:macros\fR:\:\fI/usr/\:lib/\:rpm/\
> | 176 
> :fileattrs/\:*.attr\fR:\:\fI/usr/\:lib/\:rpm/\:redhat/\:macros\fR:\:\fI/etc/\:rpm/\:macros.*\fR:\:\fI/etc/\:rpm/\:macros\fR:\:\fI/etc/\:rpm/\:%{_target}/\:macro
> | 176 s\fR:\:\fI~/.rpmmacros
> | 177
> | […]

> This line is too long for the standard layout.  It already
> has hints ("\:"; zero-width break points) where it should be
> broken, but these seem to be ignored.  So prima facie RPM
> has done everything right, and there is an error somewhere
> in the groff/man ecosphere.

That analysis was wrong: "cannot adjust line" does not mean
that the line is too long, but rather that there are no spa-
ces that groff can expand to adjust (justify) the line.

For rpm(8) this was worked around by formatting the default
value as a code block, with line breaks after each colon,
thus not requiring the lines to be adjusted/justified.

Tim
--
___
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: Orphaned packages looking for new maintainers

2024-03-27 Thread Miro Hrončok

On 27. 03. 24 16:03, Jens-Ulrik Petersen wrote:
On Wed, Mar 27, 2024 at 9:46 PM Miro Hrončok > wrote:


On 25. 03. 24 7:48, Jens-Ulrik Petersen wrote:
 > Also botan got orphaned despite the FTI going away
 > > [1] ;-(
 > Could it be un-orphaned back?

 > [1] Seems FTI failed to close the bug fixed on 2024-03-07

It was closed after it was fixed. The update was stuck at beta freeze and
nobody associated the FTI bugzilla with it.


No, it was reported  
installable (comment 5) on 7th March by fti-bugs but was not closed as it 
should have been then.


On Fedora 41 only.

Then it was orphaned  
(comment 6) on 21st March.


Yes, because it was still NEW and not acted upon by the maintainer.

Then again reported  
installable (comment 7) on 25th which actually closed the bug.


On Fedora 40.


Which is why I am asking if the orphaned can be reverted, please.


Yes, if the previous maintainer is still interested in maintaining it, they can 
take the package back by clicking on the *Take* button.


It makes no sense to me to assign it back to them if they are not interested.

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


Fedora 40 compose report: 20240327.n.0 changes

2024-03-27 Thread Fedora Branched Report
OLD: Fedora-40-20240326.n.0
NEW: Fedora-40-20240327.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  4
Dropped packages:0
Upgraded packages:   15
Downgraded packages: 0

Size of added packages:  13.25 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1005.35 MiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Silverblue ociarchive ppc64le
Path: Silverblue/ppc64le/images/Fedora-Silverblue-40.20240327.n.0.ociarchive
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-40-20240327.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: kf5-qqc2-breeze-style-5.27.11-1.fc40
Summary: Qt5QuickControls2 breeze style
RPMs:kf5-qqc2-breeze-style
Size:775.17 KiB

Package: kf5-qqc2-desktop-style-5.115.0-2.fc40
Summary: QtQuickControls2 style for consistency between QWidget and QML apps
RPMs:kf5-qqc2-desktop-style
Size:694.71 KiB

Package: ruqola-2.1.0-1.fc40
Summary: Qt-based client for Rocket Chat
RPMs:ruqola ruqola-doc
Size:11.61 MiB

Package: rust-adblock-0.8.8-1.fc40
Summary: Native Rust module for Adblock Plus syntax
RPMs:rust-adblock+addr-devel rust-adblock+content-blocking-devel 
rust-adblock+default-devel rust-adblock+embedded-domain-resolver-devel 
rust-adblock+full-regex-handling-devel rust-adblock+lifeguard-devel 
rust-adblock+object-pooling-devel rust-adblock+regex-debug-info-devel 
rust-adblock+resource-assembler-devel rust-adblock+serde_json-devel 
rust-adblock+unsync-regex-caching-devel rust-adblock-devel
Size:211.83 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  audit-4.0.1-1.fc40
Old package:  audit-4.0-8.fc40
Summary:  User space tools for kernel auditing
RPMs: audispd-plugins audispd-plugins-zos audit audit-libs 
audit-libs-devel audit-rules python3-audit
Size: 2.85 MiB
Size change:  75.42 KiB
Changelog:
  * Mon Mar 11 2024 Steve Grubb  4.0.1-1
  - New upstream release


Package:  containers-common-5:0.58.0-2.fc40
Old package:  containers-common-5:0.57.3-3.fc40
Summary:  Common configuration and documentation for containers
RPMs: containers-common containers-common-extra
Size: 111.69 KiB
Size change:  1.11 KiB
Changelog:
  * Fri Mar 01 2024 Daniel J Walsh  - 5:0.57.3-4
  - Update for podman 5.0

  * Fri Mar 01 2024 Daniel J Walsh  - 5:0.57.3-5
  - local build

  * Wed Mar 13 2024 Lokesh Mandvekar  - 5:0.57.3-6
  - make passt and netavark hard dependencies

  * Wed Mar 13 2024 Lokesh Mandvekar  - 5:0.58.0-1
  - bump to v0.58.0

  * Wed Mar 20 2024 Lokesh Mandvekar  - 5:0.58.0-2
  - container-selinux should be a hard Requires


Package:  distribution-gpg-keys-1.102-1.fc40
Old package:  distribution-gpg-keys-1.101-1.fc40
Summary:  GPG keys of various Linux distributions
RPMs: distribution-gpg-keys distribution-gpg-keys-copr
Size: 78.86 MiB
Size change:  585.64 KiB
Changelog:
  * Fri Mar 08 2024 Miroslav Such??  1.102-1
  - update copr keys
  - Create cathugger.asc
  - Create zzz.key.asc
  - Create idk.key.asc
  - Create hulahoop.asc
  - Create adrelanos.asc
  - Create makemkv_pub.txt


Package:  firefox-124.0.1-2.fc40
Old package:  firefox-124.0.1-1.fc40
Summary:  Mozilla Firefox Web browser
RPMs: firefox firefox-langpacks
Size: 457.08 MiB
Size change:  55.11 KiB
Changelog:
  * Mon Mar 25 2024 Martin Stransky - 124.0-2
  - Reverted IM patch


Package:  net-snmp-1:5.9.4-5.fc40
Old package:  net-snmp-1:5.9.4-3.fc40
Summary:  A collection of SNMP protocol tools and libraries
RPMs: net-snmp net-snmp-agent-libs net-snmp-devel net-snmp-gui 
net-snmp-libs net-snmp-perl net-snmp-perl-module net-snmp-utils python3-net-snmp
Size: 12.01 MiB
Size change:  4.20 KiB
Changelog:
  * Fri Feb 16 2024 Josef Ridky  - 1:5.9.4-4
  - Autoconf upgrade (#2256768)

  * Tue Mar 12 2024 Josef Ridky  - 1:5.9.4-5
  - Fix parsing issue for kernel 6.7+ (#2266893)
  - revert autoconf patch for F40 and lower


Package:  netavark-1.10.3-3.fc40
Old package:  netavark-1.10.3-1.fc40
Summary:  OCI network stack
RPMs: netavark
Size: 14.44 MiB
Size change:  -1.43 KiB
Changelog:
  * Wed Mar 13 2024 Lokesh Mandvekar  - 0:1.10.3-2
  - make aardvark-dns a hard dep across the board

  * Wed Mar 20 2024 Lokesh Mandvekar  - 0:1.10.3-3
  - rebuild for podman 5 f40 bodhi


Package:  openelp-0.9.3-1.fc40
Old package:  openelp-0.9.2-10.fc40
Summary:  Open Source EchoLink Proxy
RPMs: openelp openelp-devel
Size: 962.53 KiB
Size change:  257 B
Changelog:
  * Sun Mar 17 2024 Scott K Logan  - 0.9.3-1
  - Update to 0.9.3


Package:  perl-Compress-Raw-Bzip2-2.210-1.fc40
Old package:  perl-Compress-Raw-Bzip2-2.209-1.fc40
Summary:  Low-level interface to bzip2 compression library
RPMs: perl-Compress-Raw-Bzip2 perl

[Bug 2271882] New: Upgrade perl-HTTP-Tinyish to 0.19

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271882

Bug ID: 2271882
   Summary: Upgrade perl-HTTP-Tinyish to 0.19
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/HTTP-Tinyish
Status: NEW
 Component: perl-HTTP-Tinyish
  Assignee: emman...@seyman.fr
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.18 version. Upstream released 0.19. 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=2271882

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271882%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 2271881] New: Upgrade perl-Crypt-SMIME to 0.30

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271881

Bug ID: 2271881
   Summary: Upgrade perl-Crypt-SMIME to 0.30
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/Crypt-SMIME
Status: NEW
 Component: perl-Crypt-SMIME
  Assignee: steve.tray...@cern.ch
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
steve.tray...@cern.ch, xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.29 version. Upstream released 0.30. 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=2271881

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271881%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 2271821] perl-DBD-MySQL: improper use of the %{eln} macro

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271821

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
   Fixed In Version||perl-DBD-MySQL-5.004-2.fc41
 Resolution|--- |ERRATA
Last Closed||2024-03-27 15:15:28



--- Comment #3 from Fedora Update System  ---
FEDORA-2024-02b5f27ca2 (perl-DBD-MySQL-5.004-2.fc41) has been pushed to the
Fedora 41 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=2271821

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271821%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 2271821] perl-DBD-MySQL: improper use of the %{eln} macro

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271821



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-8d07fa18c7 (perl-DBD-MySQL-5.004-2.fc40) has been submitted as an
update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8d07fa18c7


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271821%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 2271821] perl-DBD-MySQL: improper use of the %{eln} macro

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271821

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2024-02b5f27ca2 (perl-DBD-MySQL-5.004-2.fc41) has been submitted as an
update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-02b5f27ca2


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271821%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


Re: on dnf autoremove aggressive behaviour

2024-03-27 Thread Neal Gompa
On Wed, Mar 27, 2024 at 11:00 AM Germano Massullo
 wrote:
>
> I recently updated to F40 KDE, but Jami software [1] bundled Qt6 RPM
> package messed up with system Qt6 (see later fix at [2]), so I had to run:
> # dnf autoremove
> # dnf reinstall $(rpm -qa)
>
> I have noticed an aggressive packaging removal behaviour from "dnf
> autoremove", indeed it removed various essential packages, some of them
> even installed by default during Fedora installation (complete list at
> [3]) For example:
> - gdisk
> - openssl
> - lz4
> - java-21-openjdk
>
> dnf man page, says:
> 
> dnf [options] autoremove
> Removes  all  "leaf"  packages from the system that were originally
> installed as dependencies of user-installed packages, but which are no
> longer required by any such package.
> Packages listed in installonlypkgs are never automatically removed by
> this command.
> 
> I wonder:
> 1) where installonlypkgs is defined, I could not find it in /etc/dnf
> 2) why it removed also packages that are shipped by default during a
> Fedora installation, like gdisk and openssl
>

1) installonlypkgs is determined in the code. It is any package that
has "installonlypkg(kernel)", "installonlypkg(kernel-module)", or
"multiversion(kernel)" Provides. Basically the kernel packages.
2) None of those packages are installed directly, they are installed
as dependencies, and if the thing that depended on it no longer is on
the system, they are considered safe to remove.



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


Re: Orphaned packages looking for new maintainers

2024-03-27 Thread Jens-Ulrik Petersen
On Wed, Mar 27, 2024 at 9:46 PM Miro Hrončok  wrote:

> On 25. 03. 24 7:48, Jens-Ulrik Petersen wrote:
> > Also botan got orphaned despite the FTI going away
> >  [1] ;-(
> > Could it be un-orphaned back?
>
> > [1] Seems FTI failed to close the bug fixed on 2024-03-07
>
> It was closed after it was fixed. The update was stuck at beta freeze and
> nobody associated the FTI bugzilla with it.
>

No, it was reported 
installable (comment 5) on 7th March by fti-bugs but was not closed as it
should have been then.
Then it was orphaned
 (comment 6) on
21st March.
Then again reported 
installable (comment 7) on 25th which actually closed the bug.
Which is why I am asking if the orphaned can be reverted, please.

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


on dnf autoremove aggressive behaviour

2024-03-27 Thread Germano Massullo
I recently updated to F40 KDE, but Jami software [1] bundled Qt6 RPM 
package messed up with system Qt6 (see later fix at [2]), so I had to run:

# dnf autoremove
# dnf reinstall $(rpm -qa)

I have noticed an aggressive packaging removal behaviour from "dnf 
autoremove", indeed it removed various essential packages, some of them 
even installed by default during Fedora installation (complete list at 
[3]) For example:

- gdisk
- openssl
- lz4
- java-21-openjdk

dnf man page, says:

dnf [options] autoremove
Removes  all  "leaf"  packages from the system that were originally 
installed as dependencies of user-installed packages, but which are no 
longer required by any such package.
Packages listed in installonlypkgs are never automatically removed by 
this command.


I wonder:
1) where installonlypkgs is defined, I could not find it in /etc/dnf
2) why it removed also packages that are shipped by default during a 
Fedora installation, like gdisk and openssl


[1]: https://en.wikipedia.org/wiki/Jami_(software)
[2]: 
https://review.jami.net/c/jami-project/+/27951/2/packaging/rules/rpm/jami-libqt.spec

[3]: https://paste.centos.org/view/ec0ae480
--
___
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


%pyproject_buildrequires -r/-x: Attempt to read runtime dependencies from pyproject.toml?

2024-03-27 Thread Karolina Surma

Hello,

recently, we were suggested an improvement for %pyproject_buildrequires 
-r/-x.
We could read the project's runtime dependencies (if they're not marked 
as `dynamic`) from pyproject.toml [project] table directly, without 
calling prepare_metadata_for_build_wheel or building the wheel to read 
the dependency metadata from it.


Reading the metadata via prepare_metadata_for_build_wheel is already 
quite fast, however implementing that hook is optional for the build 
backends. When the hook is not available, we need to build the wheel, 
which can be potentially very slow and resource-hungry (imagine building 
the entire scipy project).
Metadata in pyproject.toml is standardized (PEP 621), however there is 
no way of telling ahead of time if the build backend already supports 
that standard.


See the details and discussion in bugzilla: 
https://bugzilla.redhat.com/2261939


Maxwell has raised some valid concerns there:
- Other tools (build frontends, e.g. pip/build) call 
prepare_metadata_for_build_wheel, our macros would diverge in 
functionality compared to the rest of the landscape.
- pyproject.toml's [project] may not be the source of metadata that the 
build backend uses. A project could switch to a build backend without 
PEP 621 support (e.g. poetry-core) and forget to remove the [project] table.
- There can be potential differences between BuildRequires and Requires 
generators when one generates dependencies based on the pyproject.toml 
[project] table while the other on the packaged dist-info metadata.
- Using macros to build on older systems: e.g. RHEL 9's old setuptools 
version silently ignores the pyproject.toml [project] table - 
%pyproject_buildrequires could still pull the dependency information 
from it, but the resulting package would be broken because it did not 
include those in the packaged dist-info metadata.


One way to mitigate would be to make the proposed behavior opt-in only, 
with the possibility to either build wheel with -w option (already 
existing) or e.g. -p (now-proposed: reading from pyproject.toml) in case 
backend doesn't have prepare_metadata_for_build_wheel. However, this 
adds a layer of complexity for packagers and macros maintainers.


The questions we'd love your input for:
- Should %pyproject_buildrequires try to read dependencies from 
pyproject.toml first and fall back to calling hooks only if that fails?
- Should %pyproject_buildrequires call the hook and try to fall 
back to reading dependencies from pyproject.toml when the hook is not 
availbale?
- Should this behavior exist but not be the default (explicit flag 
would be required to opt-in)?

- Can you think of a better alternative than the ones described here?


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


Re: Fedora Linux 40 Beta Released

2024-03-27 Thread Leslie Satenstein via devel
Check outIndex of /compose/branched

| 
| 
|  | 
Index of /compose/branched


 |

 |

 |





Leslie Satenstein
 

On Wednesday, March 27, 2024 at 04:51:18 a.m. EDT, Barry 
 wrote:  
 
 

> On 26 Mar 2024, at 15:09, Kevin Fenzi  wrote:
> 
> I think it was being edited when you looked?
> 
> It seems to have the details now? Or is there something missing?

All there now. Original visible was just one line.

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


Fedora rawhide compose report: 20240327.n.0 changes

2024-03-27 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20240326.n.1
NEW: Fedora-Rawhide-20240327.n.0

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

Size of added packages:  7.95 MiB
Size of dropped packages:0 B
Size of upgraded packages:   3.37 GiB
Size of downgraded packages: 0 B

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

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

= DROPPED IMAGES =
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20240326.n.1.iso
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20240326.n.1.iso

= ADDED PACKAGES =
Package: gap-pkg-anupq-3.3.0-1.fc41
Summary: ANU p-Quotient for GAP
RPMs:gap-pkg-anupq gap-pkg-anupq-doc
Size:4.83 MiB

Package: gap-pkg-permut-2.0.5-1.fc41
Summary: Permutability in finite groups for GAP
RPMs:gap-pkg-permut gap-pkg-permut-doc
Size:397.41 KiB

Package: libomp17-17.0.6-1.fc41
Summary: OpenMP runtime for clang
RPMs:libomp17 libomp17-devel
Size:2.74 MiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  anaconda-41.7-2.fc41
Old package:  anaconda-41.6-1.fc41
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-widgets anaconda-widgets-devel
Size: 17.63 MiB
Size change:  9.86 KiB
Changelog:
  * Tue Mar 26 2024 Packit  - 41.7-1
  - Update translations from Weblate for master (github-actions)
  - Disable preexec for vtActivate() (mkolman)


Package:  arc-kde-20220908-8.fc41
Old package:  arc-kde-20220908-6.fc40
Summary:  Port of the popular GTK theme Arc for the Plasma 5 desktop
RPMs: arc-kde arc-kde-decorations arc-kde-konsole arc-kde-konversation 
arc-kde-kvantum arc-kde-wallpapers arc-kde-yakuake
Size: 31.73 MiB
Size change:  1.25 KiB
Changelog:
  * Tue Mar 26 2024 Arthur Bols  - 20220908-7
  - Patch for plasma 6 support

  * Tue Mar 26 2024 Arthur Bols  - 20220908-8
  - Add missing arc-kde-plasma-6-support.patch


Package:  avr-gcc-1:13.2.0-4.fc41
Old package:  avr-gcc-1:13.2.0-3.fc40
Summary:  Cross Compiling GNU GCC targeted at avr
RPMs: avr-gcc avr-gcc-c++
Size: 192.13 MiB
Size change:  -244.02 KiB
Changelog:
  * Tue Mar 26 2024 Michal Hlavinka  - 1:13.2.0-4
  - drop i686 build as per 
https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval


Package:  blend2d-0.10.6-3.fc41
Old package:  blend2d-0.10.6-2.fc41
Summary:  2D Vector Graphics Engine Powered by a JIT Compiler
RPMs: blend2d blend2d-devel
Size: 3.63 MiB
Size change:  126 B
Changelog:
  * Wed Mar 27 2024 topazus  - 0.10.6-3
  - fix the test on s390x


Package:  bootc-0.1.9-2.fc41
Old package:  bootc-0.1.8-1.fc41
Summary:  Bootable container system
RPMs: bootc
Size: 7.66 MiB
Size change:  10.91 KiB
Changelog:
  * Tue Mar 26 2024 Colin Walters  - 0.1.9-1
  - https://github.com/containers/bootc/releases/tag/v0.1.9

  * Tue Mar 26 2024 Colin Walters  - 0.1.9-2
  - Add generator to filelist


Package:  btrfs-progs-6.8-1.fc41
Old package:  btrfs-progs-6.7.1-1.fc41
Summary:  Userspace programs for btrfs
RPMs: btrfs-progs btrfs-progs-devel libbtrfs libbtrfsutil 
python3-btrfsutil
Size: 6.66 MiB
Size change:  3.53 KiB
Changelog:
  * Tue Mar 26 2024 Neal Gompa  - 6.8-1
  - Update to 6.8


Package:  calc-2.15.0.6-3.fc41
Old package:  calc-2.15.0.6-1.fc41
Summary:  Arbitrary precision arithmetic system and calculator
RPMs: calc calc-devel calc-libs calc-stdrc
Size: 5.60 MiB
Size change:  1.38 MiB
Changelog:
  * Tue Mar 26 2024 Matthew Miller  - 2.15.0.6-2
  - no longer exclude s390

  * Tue Mar 26 2024 Matthew Miller  - 2.15.0.6-3
  - Renable custom library by default


Package:  cramjam-cli-0.1.1-3.fc41
Old package:  cramjam-cli-0.1.1-2.fc41
Summary:  Simple CLI to a variety of compression algorithms
RPMs: cramjam-cli
Size: 3.71 MiB
Size change:  -250.18 KiB
Changelog:
  * Tue Mar 26 2024 Benjamin A. Beasley  - 0.1.1-3
  - Update libcramjam crate dependency to 0.3.0


Package:  dnf-plugins-core-4.6.0-1.fc41
Old package:  dnf-plugins-core-4.5.0-1.fc40
Summary:  Core Plugins for DNF
RPMs: dnf-plugins-core dnf-utils python3-dnf-plugin-leaves 
python3-dnf-plugin-local python3-dnf-plugin-modulesync 
python3-dnf-plugin-post-transaction-actions 
python3-dnf-plugin-pre-transaction-actions python3-dnf-plugin-show-leaves 
python3-dnf-plugin-versionlock python3-dnf-plugins-core
Added RPMs:   python3-dnf-plugin-pre-transaction-actions
Size: 530.09 KiB
Size change:  15.21 KiB
Changelog:
  * Tue Mar 26 2024

Re: Orphaned packages looking for new maintainers

2024-03-27 Thread Miro Hrončok

On 25. 03. 24 7:48, Jens-Ulrik Petersen wrote:
Also botan got orphaned despite the FTI going away 
 [1] ;-(

Could it be un-orphaned back?


Yes, by clicking the *Take* button.


[1] Seems FTI failed to close the bug fixed on 2024-03-07


It was closed after it was fixed. The update was stuck at beta freeze and 
nobody associated the FTI bugzilla with it.


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


[rpms/perl-LWP-Protocol-https] PR #7: 6.14 bump

2024-03-27 Thread Michal Josef Špaček

mspacek closed without merging a pull-request against the project: 
`perl-LWP-Protocol-https` that you
are following.

Closed pull-request:

``
6.14 bump
``

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


[rpms/perl-LWP-Protocol-https] PR #10: 6.14 bump

2024-03-27 Thread Michal Josef Špaček

mspacek closed without merging a pull-request against the project: 
`perl-LWP-Protocol-https` that you
are following.

Closed pull-request:

``
6.14 bump
``

https://src.fedoraproject.org/rpms/perl-LWP-Protocol-https/pull-request/10
--
___
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 2271821] New: perl-DBD-MySQL: improper use of the %{eln} macro

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271821

Bug ID: 2271821
   Summary: perl-DBD-MySQL: improper use of the %{eln} macro
   Product: Fedora
   Version: rawhide
OS: Linux
Status: NEW
 Component: perl-DBD-MySQL
  Severity: medium
  Assignee: jples...@redhat.com
  Reporter: sgall...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, msch...@redhat.com,
mspa...@redhat.com,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com
  Target Milestone: ---
Classification: Fedora



The spec file is using the %{eln} macro, which is restricted to approval[1] by
the ELN SIG.

In this case, it looks like the %{eln} macro was being used to guard around a
now-obsolete distinction between community-mysql and mysql.

Please correct this usage or open a ticket with the ELN SIG justifying why ELN
and RHEL/CentOS Stream need to differ here.

[1] See ELN FAQ question "When should I use the rpm macro %{eln}?" at
https://docs.fedoraproject.org/en-US/eln/faq/

Reproducible: Always


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271821%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: openclonk: undefined reference to `zmemcpy'

2024-03-27 Thread Antonio T. sagitter

Hi all.

I'm seriously thinking to abandon 'openclonk' rpm.
The project is currently unmaintained.

On 08/03/24 16:01, Martin Gansser wrote:

Hi,

when compiling openclonk [1] on rawhide it fails with this error message [2]:
/usr/bin/cmake -E cmake_link_script CMakeFiles/c4group.dir/link.txt --verbose=1
/usr/bin/g++ -O2 -flto=auto -ffat-lto-objects -fexceptions -g 
-grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang 
-Wno-error=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 
-Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 
-march=x86-64 -mtune=generic -fasynchronous-unwind-tables 
-fstack-clash-protection -fcf-protection -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer -Wall -Wextra -Wredundant-decls -Wendif-labels 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Winit-self 
-Wsign-promo -Wno-reorder -Wno-unused-parameter -Wnon-virtual-dtor 
-Woverloaded-virtual -Wformat-security -Werror=delete-incomplete -DNDEBUG 
-flto=auto -fno-fat-lto-objects -Wl,-z,relro -Wl,--as-needed  
-Wl,-z,pack-relative-relocs -Wl,-z,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -W
  l,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes 
CMakeFiles/c4group.dir/c4group_autogen/mocs_compilation.cpp.o 
CMakeFiles/c4group.dir/src/c4group/C4GroupMain.cpp.o -o c4group  liblibmisc.a 
/usr/lib64/libz.so -lpthread -lrt
make[2]: Leaving directory 
'/builddir/build/BUILD/openclonk-701bcf38c9f3c4877e1b4a8651b9ce922b15969e/build'
/usr/bin/ld: /tmp/ccgvFyfu.ltrans1.ltrans.o: in function `c4_gzread':
/builddir/build/BUILD/openclonk-701bcf38c9f3c4877e1b4a8651b9ce922b15969e/src/zlib/gzio.c:450:(.text+0x3fd0):
 undefined reference to `zmemcpy'
collect2: error: ld returned 1 exit status

How can this be fixed ??

[1] 
https://martinkg.fedorapeople.org/ErrorReports/openclonk/openclonk-8.1-24.20210103git701bcf3.fc39.src.rpm
[2] https://kojipkgs.fedoraproject.org//work/tasks/5278/114665278/build.log

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


--
---
Antonio Trande
Fedora Project
https://fedoraproject.org/wiki/User:Sagitter
mailto: sagit...@fedoraproject.org
GPG key: 0x40FDA7B70789A9CD
GPG keys server: https://keys.openpgp.org/


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


Re: [SPDX] Mass license change: Intro and change of "Bitstream Vera" to "Bitstream-Vera"

2024-03-27 Thread Petr Pisar
V Tue, Mar 26, 2024 at 02:52:50PM +0100, Miroslav Suchý napsal(a):
> I have no strong opinion how to process with the case of  "MIT and BSD and
> Bitstream Vera and OFL". I think that converting it to " MIT and BSD and
> Bitstream-Vera and OFL" is probably best option. I.e. the License tag will
> become mixture of Callaway and SPDX. It will not make it valid SPDX formula
> so it will still pop up as package to be fixed, but at least some work will
> be done.

In other words, it will be a regression. Invalid by either system:

$ license-validate 'MIT AND BSD AND Bitstream-Vera and OFL'
Not a valid license string
Run with -v option to see more information.
$ license-validate --old 'MIT AND BSD AND Bitstream-Vera and OFL'
Not a valid license string
Run with -v option to see more information.

I wouldn't do it.

If you want to hint the packager, then open a pull request with the partial
conversion.

-- Petr


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


Re: [SPDX] Mass license change: Intro and change of "Bitstream Vera" to "Bitstream-Vera"

2024-03-27 Thread Vít Ondruch


Dne 27. 03. 24 v 7:40 Miroslav Suchý napsal(a):

Dne 26. 03. 24 v 6:00 odp. Artur Frenszek-Iwicki napsal(a):

If we're going to introduce any kind of (semi-)automatic
conversion of existing license tags, I think it'd be good
to make "convert «and» and «or» to upper-case"
part of the process.

A.FI.

[0]https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/#d2-case-sensitivity


*nod*

BTW based of the feedback of all of you and because it is very common 
error in writing SPDX formula in SPDXv3 it will likely be allowed to 
use "and", "or".


https://github.com/spdx/spdx-spec/pull/892



I wish there was also comma operator `,` with the meaning of `AND`, that 
could be useful.


Just FTR, I have opened this RPM discussion a while ago:

https://github.com/rpm-software-management/rpm/discussions/2892

Just to realize not long ago that one hurdle is how to merge the tags 
together, because RPM itself does not know anything about SPDX or any 
other license identifiers. If needed, comma would be the most natural 
operator for list of licenses.


Not mentioning, it does not have issues with upper / lower case and 
writing ", " instead of " AND " requires just 40 % of the effort.



Vít



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


[Bug 2271724] perl-URI-5.28 is available

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271724

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-URI-5.28-1.fc41
 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2024-03-27 08:57:28



--- Comment #3 from Fedora Update System  ---
FEDORA-2024-609132bbc7 (perl-URI-5.28-1.fc41) has been pushed to the Fedora 41
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=2271724

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271724%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


Re: Fedora Linux 40 Beta Released

2024-03-27 Thread Barry


> On 26 Mar 2024, at 15:09, Kevin Fenzi  wrote:
> 
> I think it was being edited when you looked?
> 
> It seems to have the details now? Or is there something missing?

All there now. Original visible was just one line.

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


[Now Playing] Toolbx Test Day 2024-03-27

2024-03-27 Thread Sumantro Mukherjee
Hey Folks,

Toolbx is now a blocker and pre-installed app for Fedora Workstation.
The advent of Podman 5[0] can have a few complications with Toolbx's
primary deliverables and workflow. To ensure a smooth transition, we
are inviting  testers to install latest version of
Toolbx and Podman 5 in F40 and report issues[1]. The wiki[2] has
all the necessary details. Join us and make Fedora better!

[0] https://fedoraproject.org/wiki/Changes/Podman5
[1] https://github.com/containers/toolbox
[2] https://fedoraproject.org/wiki/Test_Day:2024-03-27_Toolbx


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
--
___
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 2271724] perl-URI-5.28 is available

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271724



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-2671431b9f (perl-URI-5.28-1.fc40) has been submitted as an update
to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2671431b9f


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271724%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 2271724] perl-URI-5.28 is available

2024-03-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2271724

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2024-609132bbc7 (perl-URI-5.28-1.fc41) has been submitted as an update
to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-609132bbc7


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202271724%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


Re: [SPDX] Mass license change: Intro and change of "Bitstream Vera" to "Bitstream-Vera"

2024-03-27 Thread Miroslav Suchý

Dne 26. 03. 24 v 6:00 odp. Artur Frenszek-Iwicki napsal(a):

If we're going to introduce any kind of (semi-)automatic
conversion of existing license tags, I think it'd be good
to make "convert «and» and «or» to upper-case"
part of the process.

A.FI.

[0]https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/#d2-case-sensitivity


*nod*

BTW based of the feedback of all of you and because it is very common error in writing SPDX formula in SPDXv3 it will 
likely be allowed to use "and", "or".


https://github.com/spdx/spdx-spec/pull/892

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
___
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