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

2023-11-15 Thread updates 
The following Fedora EPEL 8 Security updates need testing:
 Age  URL
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6b5f919719   
tor-0.4.8.9-1.el8
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f535d91d21   
chromium-119.0.6045.123-1.el8
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-bdf128f5d3   
audiofile-0.3.6-36.el8


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

libabigail-2.4-2.el8
php-fedora-autoloader-1.0.1-7.el8
php-theseer-autoload-1.27.2-1.el8
php-theseer-directoryscanner-1.3.3-2.el8
php-zetacomponents-base-1.9.3-2.el8
php-zetacomponents-console-tools-1.7.3-1.el8

Details about builds:



 libabigail-2.4-2.el8 (FEDORA-EPEL-2023-c18475b8f2)
 Set of ABI analysis tools

Update Information:

Fix sourceware.org/PR31045

ChangeLog:

* Wed Nov 15 2023 Dodji Seketeli  - 2.4-2
- Fix sourceware.org/PR31045
  "Don't try setting translation unit for unique types"
  Apply patch
  0001-Bug-31045-Don-t-try-setting-translation-unit-for-uni.patch.
- Fix sourceware.org/PR31017
  "Support Flex array conversion suppression"
  Apply patch 0002-suppression-Add-has_strict_flexible_array_data_membe.patch
- Use SPDX license description
- Add git as build requirement
- Use git to apply the patches as they apply binary changes and patch
  doesn't know how to handle these.
- As the paches touch Makefile.am files, run autoreconf after
  applying the patches.

References:

  [ 1 ] Bug #31017 - AMI Megaraid driver problem
https://bugzilla.redhat.com/show_bug.cgi?id=31017
  [ 2 ] Bug #31045 - None
https://bugzilla.redhat.com/show_bug.cgi?id=31045




 php-fedora-autoloader-1.0.1-7.el8 (FEDORA-EPEL-2023-ac02c031b8)
 Fedora Autoloader

Update Information:

Static PSR-4, PSR-0, and classmap autoloader.  Includes loader for required and
optional dependencies.

ChangeLog:

* Mon Dec  6 2021 Remi Collet  - 1.0.1-7
- disable test suite on EL
* Fri Jul 23 2021 Fedora Release Engineering  - 
1.0.1-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Mon Mar  8 2021 Remi Collet  - 1.0.1-5
- use range dependencies
- switch to phpunit8
* Wed Jan 27 2021 Fedora Release Engineering  - 
1.0.1-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Tue Jul 28 2020 Fedora Release Engineering  - 
1.0.1-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Wed Feb 12 2020 Shawn Iwinski  - 1.0.1-2
- Add tests bootstrap to fix EPEL6 build
* Wed Feb 12 2020 Shawn Iwinski  - 1.0.1-1
- Update to 1.0.1 (RHBZ #1802372)
* Thu Jan 30 2020 Fedora Release Engineering  - 
1.0.0-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
* Fri Jul 26 2019 Fedora Release Engineering  - 
1.0.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
* Sat Feb  2 2019 Fedora Release Engineering  - 
1.0.0-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Tue Dec  4 2018 Remi Collet  - 1.0.0-5
- cleanup for EL-8
* Fri Jul 13 2018 Fedora Release Engineering  - 
1.0.0-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Fri Feb  9 2018 Fedora Release Engineering  - 
1.0.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Thu Jul 27 2017 Fedora Release Engineering  - 
1.0.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Thu May  4 2017 Shawn Iwinski  - 1.0.0-1
- Update to 1.0.0
* Tue Mar 28 2017 Shawn Iwinski  - 1.0.0-0.1.rc1
- Update to 1.0.0-rc1
- Test with SCLs if available
- Add fedora2 template relying on include_path
* Sat Feb 11 2017 Fedora Release Engineering  - 
0.2.1-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
* Fri Oct 28 2016 Shawn Iwinski  - 0.2.1-2
- Do not install tests into buildroot
* Fri Oct 28 2016 Shawn Iwinski  - 0.2.1-1
- Update to 0.2.1
- Remove applied patches that are included in 0.2.1
- Re-add custom include_path and bootstrap for tests
- Add php-cli build dependency
* Thu Oct 27 2016 Shawn Iwinski  - 0.2.0-5
- Add upstream patch "Remove self-autoload constant and prepend
  self-autoload PSR-4 register"
- Remove custom include_path and bootstrap for tests
* Thu Oct 27 2016 Remi Collet  - 0.2.0-4
- workaround when not in global autoloader
* Wed Oct 26 2016 Shawn Iwinski  - 0.2.0-3
- Update to 0.2.0
- Remove

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

2023-11-15 Thread updates 
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eca2daf875   
chromium-119.0.6045.123-1.el7


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

libabigail-2.4-2.el7

Details about builds:



 libabigail-2.4-2.el7 (FEDORA-EPEL-2023-75e690ecb2)
 Set of ABI analysis tools

Update Information:

Fix sourceware.org/PR31045

ChangeLog:

* Wed Nov 15 2023 Dodji Seketeli  - 2.4-2
- Fix sourceware.org/PR31045
  "Don't try setting translation unit for unique types"
  Apply patch
  0001-Bug-31045-Don-t-try-setting-translation-unit-for-uni.patch.
- Fix sourceware.org/PR31017
  "Support Flex array conversion suppression"
  Apply patch 0002-suppression-Add-has_strict_flexible_array_data_membe.patch
- Use SPDX license description
- Add git as build requirement
- Use git to apply the patches as they apply binary changes and patch
  doesn't know how to handle these.
- As the paches touch Makefile.am files, run autoreconf after
  applying the patches.

References:

  [ 1 ] Bug #31017 - AMI Megaraid driver problem
https://bugzilla.redhat.com/show_bug.cgi?id=31017
  [ 2 ] Bug #31045 - None
https://bugzilla.redhat.com/show_bug.cgi?id=31045


___
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

[Rawhide] soname bump for openvdb 11.0.0

2023-11-15 Thread Luya Tshimbalanga 

Hello team,

Openvdb is updated to version 11.0.0  [1]with soname change affecting 
the following packages:


OpenImageIO -> (blender, luxcorerender, usd)
blender -> ()
luxcorerender -> ()
openvkl -> ()
prusa-slicer -> ()
usd -> (blender)

Please use the side-tag "f40-build-side-77820" for building the affected 
packages.


Reference

--

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=109091596

--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
___
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: Summary/Minutes from today's FESCo Meeting (2023-11-09)

2023-11-15 Thread Kevin Kofler via devel 
Neal Gompa wrote:
> * AGREED: Fedora explicitly declines to support the LSB 5.0 or
> earlier. Packagers will remove any information that implies
> otherwise. No implementation of an LSB package may expressly state
> or offer compliance for any LSB module that Fedora does not or
> cannot comply with. (+6, 0, 0)  (Son_Goku, 17:59:18)

So Fedora has completely discarded any notion of backwards compatibility. 
Sad.

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

Re: SPDX Statistics - Kristallnacht edition

2023-11-15 Thread Kevin Kofler via devel 
Miroslav Suchý wrote:
> Why Kristallnachte edition? On today's date at 1938, was i Kristallnacht
> (Night of Broken Glass) - a pogrom against Jews in Germany. It was first
> step where every other step was worse than the previous one. It was
> basicaly a first step that lead to holocaust.
> 
> 
https://en.wikipedia.org/wiki/Kristallnacht#Kristallnacht_as_a_turning_point

Note that the term "Kristallnacht" (or "Reichskristallnacht") is itself a 
nazi propaganda term, and it is nowadays generally agreed in Austria and 
Germany that that term should not be used. Broken glass is just broken 
glass, not "crystal". And the term only (euphemistically) mentions the 
violence against things and neglects to mention the violence against people.

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

[EPEL-devel] Packages to be untagged from epel-next

2023-11-15 Thread Troy Dawson 
The following packages have the same version in epel-next as in epel.
I plan on untagging them from epel-next unless people tell me otherwise.

epel8-next:
boinc-client-7.20.2-1.el8.next
darktable-3.8.1-2.el8.next
kimageannotator-0.6.1-1.el8.next
ksnip-1.10.1-1.el8.next
python3.11-dns-epel-2.2.1-2.el8.next
python3.11-jmespath-epel-1.0.1-1.el8.next

epel9-next:
cargo2rpm-0.1.13-1.el9.next
keepassxc-2.7.6-1.el9.next
python3.11-dns-epel-2.2.1-2.el9.next
python3.11-jmespath-epel-1.0.1-1.el9.next
python3.11-netaddr-epel-0.8.0-1.el9.next
python3.11-ntlm-auth-epel-1.5.0-1.el9.next
rust-addr2line-0.19.0-1.el9.next
rust-aho-corasick-1.1.2-1.el9.next
rust-ansiterm-0.12.2-1.el9.next
rust-arbitrary-1.3.0-1.el9.next
rust-automod-1.0.13-1.el9.next
rust-backtrace-0.3.67-2.el9.next
rust-bitflags-2.4.1-1.el9.next
rust-bstr0.2-0.2.17-1.el9.next
rust-bstr-1.7.0-1.el9.next
rust-bumpalo-3.14.0-1.el9.next
rust-bytesize-1.3.0-1.el9.next
rust-byte-unit-4.0.19-1.el9.next
rust-cargo-0.64.0-3.el9.next
rust-clap3-3.2.25-1.el9.next
rust-clap_complete3-3.2.5-1.el9.next
rust-clap_derive3-3.2.25-1.el9.next
rust-crossbeam-epoch-0.9.15-2.el9.next
rust-csv-1.3.0-1.el9.next
rust-csv-core-0.1.11-1.el9.next
rust-ctor-0.2.5-1.el9.next
rust-deranged-0.3.8-1.el9.next
rust-directories4-4.0.1-1.el9.next
rust-directories-5.0.1-1.el9.next
rust-env_logger-0.10.0-1.el9.next
rust-env_logger0.9-0.9.3-1.el9.next
rust-grep-cli-0.1.7-1.el9.next
rust-grep-printer-0.1.7-1.el9.next
rust-grep-regex-0.1.11-1.el9.next
rust-grep-searcher-0.1.11-1.el9.next
rust-half1-1.8.2-1.el9.next
rust-hashbrown-0.14.2-1.el9.next
rust-ignore-0.4.20-1.el9.next
rust-indexmap-2.0.2-1.el9.next
rust-is_executable-1.0.1-1.el9.next
rust-jobserver-0.1.27-1.el9.next
rust-lexopt-0.3.0-1.el9.next
rust-libc-0.2.149-1.el9.next
rust-libm-0.2.8-1.el9.next
rust-lock_api-0.4.11-1.el9.next
rust-memchr-2.6.4-1.el9.next
rust-miniz_oxide0.5-0.5.4-1.el9.next
rust-miniz_oxide-0.7.1-3.el9.next
rust-num_enum-0.5.11-1.el9.next
rust-num_enum_derive-0.5.11-1.el9.next
rust-num-traits-0.2.17-1.el9.next
rust-object-0.30.3-1.el9.next
rust-os_pipe0.9-0.9.2-3.el9.next
rust-os_str_bytes-6.6.1-1.el9.next
rust-packaging-25.2-1.el9.next
rust-parking_lot_core-0.9.9-1.el9.next
rust-predicates-core-1.0.6-1.el9.next
rust-print_bytes-1.2.0-1.el9.next
rust-proc-macro2-1.0.69-1.el9.next
rust-rayon-1.8.0-1.el9.next
rust-rayon-core-1.12.0-1.el9.next
rust-regex-1.10.2-1.el9.next
rust-regex-automata-0.4.3-1.el9.next
rust-regex-syntax0.7-0.7.5-1.el9.next
rust-regex-syntax-0.8.2-1.el9.next
rust-relative-path-1.9.0-1.el9.next
rust-roff0.1-0.1.0-1.el9.next
rust-roff-0.2.1-1.el9.next
rust-rpassword5-5.0.1-1.el9.next
rust-rpassword-7.2.0-1.el9.next
rust-rstest-0.18.2-1.el9.next
rust-rstest_macros-0.18.2-1.el9.next
rust-rstest_reuse-0.6.0-1.el9.next
rust-rtoolbox-0.0.1-1.el9.next
rust-rust_decimal-1.32.0-1.el9.next
rust-serde-1.0.189-1.el9.next
rust-serde_derive-1.0.189-1.el9.next
rust-serde_json-1.0.107-1.el9.next
rust-shared_child-1.0.0-3.el9.next
rust-smallvec-1.11.1-1.el9.next
rust-strip-ansi-escapes0.1-0.1.1-1.el9.next
rust-strip-ansi-escapes-0.2.0-1.el9.next
rust-syn-2.0.38-1.el9.next
rust-system-deps-6.1.2-1.el9.next
rust-tempfile-3.8.0-1.el9.next
rust-termcolor-1.3.0-1.el9.next
rust-terminal_size0.2-0.2.6-1.el9.next
rust-terminal_size-0.3.0-1.el9.next
rust-textwrap0.15-0.15.2-1.el9.next
rust-textwrap-0.16.0-1.el9.next
rust-thread-id-4.2.1-1.el9.next
rust-timeago-0.4.2-1.el9.next
rust-time-core-0.1.1-1.el9.next
rust-toml0.5-0.5.11-1.el9.next
rust-toml0.7-0.7.8-1.el9.next
rust-toml-0.8.2-1.el9.next
rust-toml_edit0.19-0.19.15-1.el9.next
rust-toml_edit-0.20.2-1.el9.next
rust-ucd-parse-0.1.10-1.el9.next
rust-winnow0.4-0.4.11-1.el9.next
rust-winnow-0.5.16-1.el9.next
rust-xml-rs-0.8.19-1.el9.next


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

[rpms/perl-Image-ExifTool] PR #1: Update to 12.69

2023-11-15 Thread Tom Callaway 

spot closed without merging a pull-request against the project: 
`perl-Image-ExifTool` that you
are following.

Closed pull-request:

``
Update to 12.69
``

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

[rpms/perl-Image-ExifTool] PR #1: Update to 12.69

2023-11-15 Thread Tom Callaway 

spot commented on the pull-request: `Update to 12.69` that you are following:
``
Upstream for this one has asked us to track latest stable in CPAN, not latest 
available.

Also, I am not a fan of %autorelease/%autochangelog.
``

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

Re: Orphaned pipenv

2023-11-15 Thread Andrej Manduch 

Hi,

Do you think I can help you co-maintain that? I wanna become part of 
fedora for a very long time. and this seems like great opportunity for me.


thx.

--

Kind regards,

Andrej Manduch

On 11/15/23 15:30, Priscila Gutierres wrote:

I would like to maintain it, but I'm now just a contributor
Can someone please sponsor me to allow me to become a maintainer and  
take this package?


Priscila.

On Wed, Nov 15, 2023 at 10:41 AM Tomáš Orsava  wrote:

Hi,
I just orphaned pipenv: https://src.fedoraproject.org/rpms/pipenv

I haven't been using the package for some time, and upstream releases
versions too fast for me to keep up. Also I'm not sure how many
people
use the package.

There are two open BZs for the package, but they'll likely be
resolved
by updating to the latest upstream version.

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

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

2023-11-15 Thread Miro Hrončok 

On 15. 11. 23 16:15, Michael J Gruber wrote:



Am Mi., 15. Nov. 2023 um 15:31 Uhr schrieb Priscila Gutierres 
mailto:prgut...@redhat.com>>:


I would like to maintain it, but I'm now just a contributor
Can someone please sponsor me to allow me to become a maintainer and  take
this package?

Priscila.

On Wed, Nov 15, 2023 at 10:41 AM Tomáš Orsava mailto:tors...@redhat.com>> wrote:

Hi,
I just orphaned pipenv: https://src.fedoraproject.org/rpms/pipenv


I haven't been using the package for some time, and upstream releases
versions too fast for me to keep up. Also I'm not sure how many people
use the package.

There are two open BZs for the package, but they'll likely be resolved
by updating to the latest upstream version.

Tomas


Looking at the myriad of py packages which Fedora's pipenv bundles, I'm really 
wondering whether we should package this at all, at least in this form. I'm not 
saying that unbundling is easy or even feasible.


We used to unblundle it. It didn't work. We added the bundled things back one 
by one until we gave up.


The packaged pipenv is broken on Fedora 38 and Fedora 39 and nobody seems to be 
screaming about it. I think we should let it die.


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

Re: Orphaned pipenv

2023-11-15 Thread Michael J Gruber 
Am Mi., 15. Nov. 2023 um 15:31 Uhr schrieb Priscila Gutierres <
prgut...@redhat.com>:

> I would like to maintain it, but I'm now just a contributor
> Can someone please sponsor me to allow me to become a maintainer and  take
> this package?
>
> Priscila.
>
> On Wed, Nov 15, 2023 at 10:41 AM Tomáš Orsava  wrote:
>
>> Hi,
>> I just orphaned pipenv: https://src.fedoraproject.org/rpms/pipenv
>>
>> I haven't been using the package for some time, and upstream releases
>> versions too fast for me to keep up. Also I'm not sure how many people
>> use the package.
>>
>> There are two open BZs for the package, but they'll likely be resolved
>> by updating to the latest upstream version.
>>
>> Tomas
>>
>>
Looking at the myriad of py packages which Fedora's pipenv bundles, I'm
really wondering whether we should package this at all, at least in this
form. I'm not saying that unbundling is easy or even feasible. But this
really seems to call for `pip install pipenv` and stretches our packaging
guidelines.

Michael
___
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: F40 Change Proposal: Linker Error on Security Issues (System-Wide)

2023-11-15 Thread Dominik 'Rathann' Mierzejewski 
Hi,

On Monday, 13 November 2023 at 12:07, Aoife Moloney wrote:
[...]
> == Summary ==
> Change the system linker (ld.bfd) so that by default it will generate
> an error message and fail if it is asked to create an executable
> binary that contains one or more known security issues.  These issues
> are:
> * an executable stack
> * a loadable segment with read, write and execute permissions,
> * a thread local storage segment with execute permission.
[...]
> * Other developers:
[...]
> Other developers can use the "--no-warn-execstack" and
> "--no-warn-rwx-segments" linker command line options to disable the
> errors.

Three issues were mentioned to start causing errors, but only two
options to disable this new behaviour.

Does the `--no-warn-rwx-segments` disable erroring out on both loadable
rwx segments and tls rwx segments?

In general, I'm +1 to this change. Potential security issues should
be detected as early as possible.

Regards,
Dominik
-- 
Fedora   https://fedoraproject.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected 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: Orphaned pipenv

2023-11-15 Thread Priscila Gutierres 
I would like to maintain it, but I'm now just a contributor
Can someone please sponsor me to allow me to become a maintainer and  take
this package?

Priscila.

On Wed, Nov 15, 2023 at 10:41 AM Tomáš Orsava  wrote:

> Hi,
> I just orphaned pipenv: https://src.fedoraproject.org/rpms/pipenv
>
> I haven't been using the package for some time, and upstream releases
> versions too fast for me to keep up. Also I'm not sure how many people
> use the package.
>
> There are two open BZs for the package, but they'll likely be resolved
> by updating to the latest upstream version.
>
> Tomas
> ___
> 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

Re: Problem with updating powerdevil and libddcutil from F38

2023-11-15 Thread Qiyu Yan 

Hi,

Just looked into the issue, the root cause is due to that 2 different 
updates are being built and pushed simultaneously in 2 different 
side-tags for 2 different sobumps, and one overrides another.


This is being be sorted out by following update:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-581f3d0e12

Following the instructions you should be able to update both ddcutil and 
powerdevil.


And question for development list: how can we avoiding this sort of 
things from happening again, like always setup buildroot override for 
pending (in testing) so-name change updates that it will propagate to 
other side-tags?


Cheers,
Qiyu


Related updates:
ddcutil: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e4abfc9685
KDE: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cae9bc16b8

在 2023/11/15 11:35, Jeffrey Walton 写道:

Hi Everyone,

I'm trying to upgrade a KDE-based workstation from F38 to F39. I
delayed the upgrade to ensure this workstation would remain available.
The delay allowed a problem with powerdevil and libddcutil to creep
in. It is causing `dnf update` and `dnf update --refresh` to fail.

I use only Fedora repos. I don't have any third party repos enabled,
like RPM Fusion.

I see a couple of other specific questions about powerdevil and
libddcutil from F38, but I don't see a clear path forward.

How do I fix the problem?

Thanks in advance.

-

$ sudo dnf update
Package manager: /bin/dnf
Fedora 38 - x86_64  8.7 MB/s |  83 MB 00:09
Fedora 38 OpenH264 (from Cisco) - x86_645.6 kB/s | 2.5 kB 00:00
Fedora Modular 38 - x86_64  2.3 MB/s | 2.8 MB 00:01
Fedora 38 - x86_64 - Updates9.8 MB/s |  35 MB 00:03
Fedora Modular 38 - x86_64 - Updates2.5 MB/s | 2.1 MB 00:00
Metadata cache created.
Last metadata expiration check: 0:00:04 ago on Wed 15 Nov 2023 06:12:54 AM EST.
Dependencies resolved.

  Problem: package powerdevil-5.27.9-2.fc38.x86_64 from @System
requires libddcutil.so.4()(64bit), but none of the providers can be
installed
   - cannot install both libddcutil-2.0.0-1.fc38.x86_64 from updates
and libddcutil-1.4.1-1.fc38.x86_64 from @System
   - cannot install both libddcutil-2.0.0-1.fc38.x86_64 from updates
and libddcutil-1.4.1-1.fc38.x86_64 from fedora
   - cannot install the best update candidate for package
libddcutil-1.4.1-1.fc38.x86_64
   - problem with installed package powerdevil-5.27.9-2.fc38.x86_64

  PackageArchitecture   VersionRepository   Size

Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
  libddcutil x86_64 2.0.0-1.fc38   updates 319 k

Transaction Summary

Skip  1 Package

$ sudo dnf update --best --allowerasing
Fedora 38 - x86_64   11 MB/s |  83 MB 00:07
Fedora 38 OpenH264 (from Cisco) - x86_641.4 kB/s | 2.5 kB 00:01
Fedora Modular 38 - x86_64  3.4 MB/s | 2.8 MB 00:00
Fedora 38 - x86_64 - Updates4.0 MB/s |  35 MB 00:08
Fedora Modular 38 - x86_64 - Updates1.8 MB/s | 2.1 MB 00:01
Error:
  Problem: The operation would result in removing the following
protected packages: plasma-desktop
(try to add '--skip-broken' to skip uninstallable packages)

$ sudo dnf update --best --allowerasing --skip-broken
Last metadata expiration check: 0:00:24 ago on Wed 15 Nov 2023 06:14:00 AM EST.
Error:
  Problem: The operation would result in removing the following
protected packages: plasma-desktop
___
users mailing list -- us...@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/us...@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

Orphaned pipenv

2023-11-15 Thread Tomáš Orsava 

Hi,
I just orphaned pipenv: https://src.fedoraproject.org/rpms/pipenv

I haven't been using the package for some time, and upstream releases 
versions too fast for me to keep up. Also I'm not sure how many people 
use the package.


There are two open BZs for the package, but they'll likely be resolved 
by updating to the latest upstream version.


Tomas
___
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 2249795] perl-Sys-Virt-9.8.0 is available

2023-11-15 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2249795

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Sys-Virt-9.8.0-1.fc40
Last Closed||2023-11-15 11:54:35



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-66fac55cbe 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=2249795

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

2023-11-15 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2249795

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202249795%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 2249795] New: perl-Sys-Virt-9.8.0 is available

2023-11-15 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2249795

Bug ID: 2249795
   Summary: perl-Sys-Virt-9.8.0 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sys-Virt
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: berra...@redhat.com, crobi...@redhat.com,
jples...@redhat.com,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 9.8.0
Upstream release that is considered latest: 9.8.0
Current version/release in rawhide: 9.7.0-1.fc40
URL: https://metacpan.org/release/Sys-Virt/

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


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


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

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

HEADS UP: gdal-3.8.0 coming to rawhide

2023-11-15 Thread Sandro Mani 

Hi

I'll be building gdal-3.8.0 in the f40-build-side-77750 side tag. It 
carries a soname bump, and I'll rebuild the following dependencies:


  GMT
  mapserver
  liblas
  python-fiona
  postgis
  merkaartor
  R-rgdal
  bes
  qmapshack
  PDAL
  ncl
  vfrnav
  python-rasterio
  vtk
  paraview
  kealib
  OpenSceneGraph
  cloudcompare
  grass
  mapnik
  opencv
  mingw-opencv
  osgearth
  qgis
  gazebo

Thanks
Sandro
___
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: DNF5: Checking signatures of packages installed out of a repository?

2023-11-15 Thread Petr Pisar 
V Tue, Nov 14, 2023 at 01:25:08PM -0500, Christopher napsal(a):
> On Tue, Nov 14, 2023 at 9:24 AM Petr Pisar  wrote:
> >
> > V Tue, Nov 14, 2023 at 08:16:39AM -0500, Christopher napsal(a):
> > > On Tue, Nov 14, 2023 at 8:03 AM Jaroslav Mracek  
> > > wrote:
> > > >
> > > > I believe that one of the strong complains was related to not signed 
> > > > packages. The use case is that when I build RPMs locally and then I 
> > > > install them (see bellow).
> > > >
> > > > dnf install *.rpm --setopt=localpkg_gpgcheck=true
> > > > ...
> > > > Package dnf-4.17.1-1.git.9598.552e61e.fc38.noarch.rpm is not signed
> > > > Package dnf-automatic-4.17.1-1.git.9598.552e61e.fc38.noarch.rpm is not 
> > > > signed
> > > > Package dnf-data-4.17.1-1.git.9598.552e61e.fc38.noarch.rpm is not signed
> > > > Package python3-dnf-4.17.1-1.git.9598.552e61e.fc38.noarch.rpm is not 
> > > > signed
> > > > Package yum-4.17.1-1.git.9598.552e61e.fc38.noarch.rpm is not signed
> > > > Error: GPG check FAILED
> > > >
> > > > Jaroslav
> > >
> > > I think for the sake of security, it'd be better if this were on by
> > > default, and you just had to specify the --nogpgcheck
> >
> > Technical note: --nogpgcheck does not imply localpkg_gpgcheck=false. Both of
> > them operate independently. That's another painful property of the current
> > code and documentation.
> >
> > -- Petr
> 
> Why wouldn't this apply? Both the documentation for 'dnf' and
> 'dnf.conf' use similar terminology "gpgcheck", and the man page says
> "Skip checking GPG signatures on packages (if RPM policy allows)."

dnf.conf(5) reads (shortened):

gpgcheck
Whether to perform GPG signature check on packages found in this
repository.

localpkg_gpgcheck
Whether to perform a GPG signature check on local packages (packages in
a file, not in a repository).

> it doesn't apply, it seems like it definitely *should*, for
> intuitiveness-sake.

I agree it's not intuitive. That's why SuSE wants the meaning of "gpgcheck"
option to be configurable
.

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