date:20230125

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164678
___
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: List of long term FTBFS packages to be retired in February

2023-01-25 Thread Yaakov Selkowitz

On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote:
> Based on the current fail to build from source policy, the following
> packages
> should be retired from Fedora 38 approximately one week before branching.
> 
> 5 weekly reminders are required, hence the retirement will happen
> approximately in 2 weeks, i.e. around 2023-02-08.
> Since this is unfortunately after the branching,
> packages will be retired on rawhide and f38.
> 
> Policy: 
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Why isn't automatic orphaning at the beginning of this countdown part of this
policy, so that others have the chance to take and fix the package?  If
someone (other than the maintainer, who should already be well aware) were to
just now notice that one of these packages were about to be retired, there
isn't really enough time to go through the BZ route to get it orphaned first.

> free42   brouhaha
> gtkhash  nonamedotc
> kguitar  davidcornette
> kjots    kde-sig, thunderbirdtr
> kmplayer moceap, rdieter
> libmobi  avsej
> xml-security-c   bruno, kloczek

PRs have been posted for these.

-- 
Yaakov Selkowitz
Principal Software Engineer - Platform Enablement
Red Hat, Inc.

___
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 2164678] New: perl-YAML-LibYAML-0.86 is available

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

Bug ID: 2164678
   Summary: perl-YAML-LibYAML-0.86 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-YAML-LibYAML
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mmasl...@redhat.com,
mspa...@redhat.com, p...@city-fan.org,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.86
Upstream release that is considered latest: 0.86
Current version/release in rawhide: 0.85-2.fc38
URL: http://search.cpan.org/dist/YAML-LibYAML/

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


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


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

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



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

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=2162740
___
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 2162728] perl-CPAN-Perl-Releases-5.20230120 is available

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



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

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=2162728
___
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 2162728] perl-CPAN-Perl-Releases-5.20230120 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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=2162728
___
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 2162740] perl-Module-CoreList-5.20230120 is available

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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

2023-01-25 Thread updates

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4bfde08e46   
rubygem-git-1.13.0-1.el8
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a2ba6db56b   
seamonkey-2.53.15-1.el8
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5792a74fc0   
advancecomp-2.5-1.el8
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1d186ca718   
python-rq-1.12.0-1.el8


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

copr-cli-1.105-1.el8
copr-selinux-1.54-1.el8
cpuid-20230120-2.el8
fastfetch-1.9.1-1.el8
icewm-3.3.1-2.el8
python-copr-1.125-1.el8

Details about builds:



 copr-cli-1.105-1.el8 (FEDORA-EPEL-2023-a3f2753730)
 Command line interface for COPR

Update Information:

### copr-cli  - More understandable module hotfixes description - Add options to
download only built RPMs/spec files - Use the --dirname parameter for copr-cli
monitor - Disable appstream by default - Use SPDX license  ### python-copr  -
Drop the unneeded marshmallow dependency - Fix APIv3 additional_modules
CoprChroot option - More understandable module hotfixes description - Disable
appstream by default - Use SPDX license

ChangeLog:

* Tue Jan 24 2023 Jakub Kadlcik  1.105-1
- More understandable module hotfixes description
- Add options to download only built RPMs/spec files
- Use the --dirname parameter for copr-cli monitor
- Disable appstream by default
- Use SPDX license

References:

  [ 1 ] Bug #2151239 - RFE: Add --rpms option to download only rpms via 
download-build
https://bugzilla.redhat.com/show_bug.cgi?id=2151239




 copr-selinux-1.54-1.el8 (FEDORA-EPEL-2023-2a90d9c075)
 SELinux module for COPR

Update Information:

### copr-selinux  - Use spdx license  ### copr-dist-git  - Drop an unused
cgit_pkg_list_location option - Use SPDX license  ### copr-keygen  - Validate
name_email that we read from client query - Use SPDX license  ### copr-rpmbuild
- Retry when copr-distgit is temporarily down - Don't print traceback for 404
errors on SRPM download - Decode URL encoded characters such as %%5E into caret
- Use SPDX license  ### python-copr-common  - Periodically dump the priority
queue to a JSON file - Use SPDX license  ### copr-backend  - Fix chroot version
parsing with new python-packaging - Fix traceback for non-existing tasks -
Python: drop the unneeded marshmallow dep - Log general exceptions to find
issues more easily - Proper log argument formatting instead of .format - Use
spdx license  ### copr-frontend  - Don't resubmit anitya builds for pre-release
versions - Anytia query using sqlalchemy - Anitya builds handled on background -
Pypi anitya buils respects spec generator option - Allow uploading artificial
payload in custom webhook - Fix traceback for non-existing tasks - Fix typo in
basearch example value - Fix batches race logic by adding locks - wTForms
validate function now expect additional parameter - Change order of RPM build
logs - Update alembic migration template - Drop the unneeded marshmallow
dependency - Fix APIv3 additional_modules CoprChroot option - Customizable group
link to FAS - Don't depend on flask-restful - Fix homepage user count - Add
command for managing warning banner - More understandable module hotfixes
description - Don't let PR builds affect status badges - Add hover for table
rows - Frontend: fix a jinja2 traceback when displaying a nonexisting batch -
Add openeuler logo - Disable appstream by default - anitya: ignore pre-release
tarballs sooner - anitya: ignore alpha versions - fix the "Modules:" web-UI form
widget - ignore anitya BadRequest rebuild attempts- Use SPDX license

ChangeLog:

* Wed Nov 30 2022 Pavel Raiskup  1.54-1
- new package built with tito
- httpd_t on copr-frontend has the rights to link copr_data_t files (uploaded 
stuff)

References:

  [ 1 ] Bug #2081915 - copr-frontend FTBFS with werkzeug 2.1.2
https://bugzilla.redhat.com/show_bug.cgi?id=2081915
  [ 2 ] Bug #2162735 - Settings, Build Options, External Repository example 
incorrect
https://bugzilla.redhat.com/show_bug.cgi?id=2162735

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

2023-01-25 Thread updates

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-afd7021128   
ipython-3.2.3-1.el7
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-08427e256d   
seamonkey-2.53.15-1.el7


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

copr-cli-1.105-1.el7
imlib2-1.4.9-8.el7
python-copr-1.125-1.el7
python-websockify-0.6.0-4.el7

Details about builds:



 copr-cli-1.105-1.el7 (FEDORA-EPEL-2023-016a5af72a)
 Command line interface for COPR

Update Information:

### copr-cli  - More understandable module hotfixes description - Add options to
download only built RPMs/spec files - Use the --dirname parameter for copr-cli
monitor - Disable appstream by default - Use SPDX license  ### python-copr  -
Drop the unneeded marshmallow dependency - Fix APIv3 additional_modules
CoprChroot option - More understandable module hotfixes description - Disable
appstream by default - Use SPDX license

ChangeLog:

* Tue Jan 24 2023 Jakub Kadlcik  1.105-1
- More understandable module hotfixes description
- Add options to download only built RPMs/spec files
- Use the --dirname parameter for copr-cli monitor
- Disable appstream by default
- Use SPDX license

References:

  [ 1 ] Bug #2151239 - RFE: Add --rpms option to download only rpms via 
download-build
https://bugzilla.redhat.com/show_bug.cgi?id=2151239




 imlib2-1.4.9-8.el7 (FEDORA-EPEL-2023-2b409ccc37)
 Image loading, saving, rendering, and manipulation library

Update Information:

This update rebases imlib2 from version 1.4.5 to 1.4.9.  This is a compatible
update with the same library soname.  It resolves multiple high severity CVEs.
- CVE-2011-5326  - CVE-2014-9762 - CVE-2014-9763 - CVE-2014-9764 - CVE-2014-9771
- CVE-2016-3993 - CVE-2016-3994  - CVE-2016-4024

ChangeLog:

* Fri Feb  1 2019 Fedora Release Engineering  - 
1.4.9-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Fri Jul 13 2018 Fedora Release Engineering  - 
1.4.9-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Sun Feb 11 2018 Sandro Mani  - 1.4.9-6
- Rebuild (giflib)
* Wed Feb  7 2018 Fedora Release Engineering  - 
1.4.9-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Aug  2 2017 Fedora Release Engineering  - 
1.4.9-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild
* Wed Jul 26 2017 Fedora Release Engineering  - 
1.4.9-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Fri Feb 10 2017 Fedora Release Engineering  - 
1.4.9-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
* Fri May  6 2016 Tomas Smetana  - 1.4.9-1
- New upstream bugfix version
- Fix rhbz#1323617 - CVE-2016-3993: off by one error in MergeUpdate
- Fix rhbz#1327478 - CVE-2016-4024: integer overflow resulting in insufficient 
heap allocation
* Fri Apr  1 2016 Tomas Smetana  - 1.4.8-1
- New upstream bugfix version
- Fix rhbz#1323062 - out of bound read in GIF loader
- Fix rhbz#1323082 - divide by zero on 2x1 ellipse
* Thu Feb  4 2016 Fedora Release Engineering  - 
1.4.7-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
* Mon Jan 25 2016 Tomas Smetana  - 1.4.7-1
- Rebase to 1.4.7
- Fixes CVE-2014-9762, CVE-2014-9763, CVE-2014-9764
* Wed Jun 17 2015 Fedora Release Engineering  
- 1.4.6-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
* Thu Jan 22 2015 Tomas Smetana  - 1.4.6-3
- Fix output of imlib2-config --libs (rhbz #1184166)
* Sat Aug 16 2014 Fedora Release Engineering  
- 1.4.6-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
* Thu Jul 31 2014 Tomas Smetana  - 1.4.6-1
- New upstream bugfix version
* Sat Jun  7 2014 Fedora Release Engineering  
- 1.4.5-11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
* Sat Aug  3 2013 Fedora Release Engineering  
- 1.4.5-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild

References:

  [ 1 ] Bug #1301617 - CVE-2014-9762 CVE-2014-9763 CVE-2014-9764 imlib2: 
security issues fixed in 1.4.7 [epel-7]
https://bugzilla.redhat.com/show_bug.cgi?id=1301617
  [ 2 ] Bug #1323064 - CVE-2016-3994 imlib2: out of bound read in GIF loader

[rpms/perl-Wx-GLCanvas] PR #2: Rebuild with wxWidgets 3.2

2023-01-25 Thread Scott Talbert


swt2c commented on the pull-request: `Rebuild with wxWidgets 3.2` that you are 
following:
``
Thanks!  BTW, I haven't tested this with slic3r yet.  My rawhide VM is 
segfaulting on boot.  :(
``

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

[rpms/perl-Wx-GLCanvas] PR #2: Rebuild with wxWidgets 3.2


churchyard commented on the pull-request: `Rebuild with wxWidgets 3.2` that you 
are following:
``
Building perl-Wx-GLCanvas-0.09-34.fc38 for rawhide
Created task: 96686144
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=96686144
``

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

[rpms/perl-Wx-GLCanvas] PR #2: Rebuild with wxWidgets 3.2


churchyard merged a pull-request against the project: `perl-Wx-GLCanvas` that 
you are following.

Merged pull-request:

``
Rebuild with wxWidgets 3.2
``

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

[rpms/perl-Wx-GLCanvas] PR #2: Rebuild with wxWidgets 3.2

2023-01-25 Thread Fabien Boucher


zuul commented on the pull-request: `Rebuild with wxWidgets 3.2` that you are 
following:
``
Build succeeded.

- [check-for-arches 
](https://fedora.softwarefactory-project.io/zuul/build/5bea016a9e2e4e4eb314562c394638d9)
 : SUCCESS in 1m 30s
- [rpm-scratch-build 
](https://fedora.softwarefactory-project.io/zuul/build/de81cdcceb6d4752aad022e0f60b3da1)
 : SUCCESS in 12m 44s
- [rpm-scratch-build-s390x 
](https://fedora.softwarefactory-project.io/zuul/build/9a50ee89e13d47d4b3e66e9d15edef1e)
 : SUCCESS in 10m 44s (non-voting)
- [rpm-scratch-build-ppc64le 
](https://fedora.softwarefactory-project.io/zuul/build/e70f56921f664fce975eff4a455a7a70)
 : SUCCESS in 10m 13s (non-voting)
- [rpm-scratch-build-i686 
](https://fedora.softwarefactory-project.io/zuul/build/8623356417e34ece90cff2422b5aa979)
 : SUCCESS in 11m 43s (non-voting)
- [rpm-scratch-build-aarch64 
](https://fedora.softwarefactory-project.io/zuul/build/7f230ee9ddc24702bb9733e069c3fc49)
 : SUCCESS in 8m 40s (non-voting)
- [rpm-linter 
](https://fedora.softwarefactory-project.io/zuul/build/75348e3396bc4072b7da1ad9161f52de)
 : SUCCESS in 3m 39s (non-voting)
- [rpm-rpminspect 
](https://fedora.softwarefactory-project.io/zuul/build/f72ef6dd1c4f464b870765b24529df68)
 : SUCCESS in 4m 32s (non-voting)
- [check-for-sti-tests 
](https://fedora.softwarefactory-project.io/zuul/build/d4a87cc6f51944249d9efec151e43484)
 : SUCCESS in 1m 36s
- [check-for-fmf-tests 
](https://fedora.softwarefactory-project.io/zuul/build/cb438327634144659b75bad6a836902b)
 : SUCCESS in 1m 44s
- [rpm-install-test 
](https://fedora.softwarefactory-project.io/zuul/build/2e56123b5a124ea5b53a4fdfac5c54ac)
 : SUCCESS in 3m 15s
- [rpm-tmt-test 
](https://fedora.softwarefactory-project.io/zuul/build/69ef325030bf4379a39e9bf58310812d)
 : SKIPPED
- [rpm-sti-test 
](https://fedora.softwarefactory-project.io/zuul/build/762dd854b01e4b999f3bb2f3e4a35ab5)
 : SKIPPED

``

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

[rpms/perl-Wx-GLCanvas] PR #2: Rebuild with wxWidgets 3.2

2023-01-25 Thread Scott Talbert


swt2c commented on the pull-request: `Rebuild with wxWidgets 3.2` that you are 
following:
``
@churchyard this can be merged + built now.
``

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

Re: Some heads-ups for Rawhide users: python3-ptyprocess and systemd issues

On Wed, 2023-01-25 at 10:30 -0800, Adam Williamson wrote:
> Hey folks! Just wanted to send out a heads-up for Rawhide users about
> some issues that have shown up in openQA testing.
> 
> First, you may have found that trying to update to today's Rawhide
> fails like this:
> 
> Error: Transaction test error:
>   file /usr/lib/python3.11/site-packages/ptyprocess-0.7.0-py3.11.egg-info 
> from install of python3-ptyprocess-0.7.0-2.fc38.noarch conflicts with file 
> from package python3-ptyprocess-0.7.0-1.fc38.noarch
> 
> That's https://bugzilla.redhat.com/show_bug.cgi?id=2164207 , we figured
> out the problem (thanks to Panu for getting to the root cause of it)
> and it is fixed in python-ptyprocess-0.7.0-3.fc38 , which should be in
> the next Rawhide compose. If you really can't wait you can update
> directly to that version
> from https://koji.fedoraproject.org/koji/buildinfo?buildID=2138649 ,
> but you'd better watch out for issue #2...
> 
> The second issue is that systems that update to systemd-253~rc1-1.fc38
> seem to get stuck on boot. With Plymouth enabled you just see the
> splash screen. With it disabled (or by pressing esc) it seems to be
> stuck at "Stopped initrd-switch-root.service - Switch Root.". I'm still
> looking into this one, but it's happened to a lot of openQA tests and I
> was able to confirm it first try in a local VM, by installing from the
> 20230123.n.0 compose then updating systemd and rebooting. Fresh
> installs with the newer systemd seem to be OK, at least most openQA
> tests for the new compose passed - it seems to be only updating an
> existing install that has the problem, at least so far.

And to add to the fun, I think either a mesa update or a glibc update
has broken GNOME and KDE: in current openQA tests, with an updated base
image to avoid the systemd and ptyprocess issues, GNOME and KDE tests
boot fine initially, run an update that includes glibc and mesa, then
reboot and fail to reach the desktop. I'm gonna look into this in more
detail when I get home, but here's the X traceback:

Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) open /dev/fb0: 
Permission denied
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (WW) VGA arbiter: 
cannot open kernel arbiter, no multi-card support
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (II) modeset(0): 
Creating default Display subsection in Screen section
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: "Default 
Screen Section" for depth/fbbpp 24/32
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (==) modeset(0): Depth 
24, (==) framebuffer bpp 32
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (==) modeset(0): RGB 
weight 888
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (==) modeset(0): 
Default visual is TrueColor
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (II) Loading sub 
module "glamoregl"
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (II) LoadModule: 
"glamoregl"
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (II) Loading 
/usr/lib64/xorg/modules/libglamoregl.so
Jan 25 13:38:47 fedora abrtd[622]: Skipping 
/var/spool/abrt/ccpp-2023-01-25-16:38:47.526247-1012.new: directory locked. Is 
a backtrace being generated?
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (II) Module glamoregl: 
vendor="X.Org Foundation"
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: compiled for 
1.20.14, module version = 1.0.1
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: ABI class: 
X.Org ANSI C Emulation, version 0.4
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: free(): double free 
detected in tcache 2
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE)
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) Backtrace:
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: ABI class: 
X.Org ANSI C Emulation, version 0.4
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: free(): double free 
detected in tcache 2
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE)
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) Backtrace:
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 0: 
/usr/libexec/Xorg (ErrorFSigSafe+0xcc) [0x556438ff496c]
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 1: 
/lib64/libc.so.6 (__sigaction+0x50) [0x7fbae3c3bba0]
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 2: 
/lib64/libc.so.6 (__pthread_kill_implementation+0x114) [0x7fbae3c8cad4]
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 3: 
/lib64/libc.so.6 (gsignal+0x1e) [0x7fbae3c3baee]
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 4: 
/lib64/libc.so.6 (abort+0xdf) [0x7fbae3c2487f]
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 5: 
/lib64/libc.so.6 (__libc_message.cold+0x5) [0x7fbae3c2560f]
Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 6: 
/lib64/libc.so.6

Re: (Fixed) Re: Most OCaml packages have broken deps now

2023-01-25 Thread Jerry James

On Wed, Jan 25, 2023 at 2:43 AM Richard W.M. Jones  wrote:
> I think we're fixed now.  Here is the side tag & Bodhi update:

Thank you for taking care of that.

> - I have added support for rpmautospec

That's great.

> - There is now a cyclic dependency between ocaml-pp and ocaml-dune,
>   which I have broken by hand, but we should try to avoid it in future
>   if possible.

Well, that was an experiment, as you and I discussed starting here:
https://bugzilla.redhat.com/show_bug.cgi?id=2101964#c1.  Apparently,
the result is "that doesn't work".  Thanks for fixing.
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Most OCaml packages have broken deps now

2023-01-25 Thread Jerry James

On Tue, Jan 24, 2023 at 11:58 AM Richard W.M. Jones  wrote:
> FYI debuginfo generation failed on several packages.  I've had to
> disable it on a few to get around this.  For example:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=96625872
> https://kojipkgs.fedoraproject.org//work/tasks/5943/96625943/build.log
>
> I'm not clear exactly why this is happening.  Since it didn't happen
> in the mass rebuild just like a few days ago, it must be some very
> recent change in the build chain, yet I didn't change anything
> significant in the OCaml package.  The only thing I can think of is
> the new version of ocaml-findlib.

For some reason debugedit is not producing a list of source files.  I
also see that debugedit failed the mass rebuild, with 8 out of 26
tests failing.  Hopefully somebody can get debugedit working again,
and then we can reenable debuginfo generation for those packages.
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Heads up for KiCad in Rawhide

2023-01-25 Thread Steven A. Falco


KiCad will shortly be upgraded from 6.0.11 to 7.0.0-rc2 in Rawhide.

Designs created with KiCad 6 and earlier are readable / editable by KiCad 7.

However, once a design is saved with KiCad 7, it will no longer be readable by 
KiCad 6 or earlier.

Steve
___
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: Error in python3-ptyprocess on latest update

2023-01-25 Thread Alexander Ploumistos

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XI2QFIRCUJGX2FMEJ5K6ILLXOIWBGBIN/
___
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

Error in python3-ptyprocess on latest update

2023-01-25 Thread Reon Beon via devel

Error: Transaction test error:
  file /usr/lib/python3.11/site-packages/ptyprocess-0.7.0-py3.11.egg-info from 
install of python3-ptyprocess-0.7.0-2.fc38.noarch conflicts with file from 
package python3-ptyprocess-0.7.0-1.fc38.noarch
___
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 heads-ups for Rawhide users: python3-ptyprocess and systemd issues

On Wed, 2023-01-25 at 10:30 -0800, Adam Williamson wrote:
> 
> The second issue is that systems that update to systemd-253~rc1-1.fc38
> seem to get stuck on boot. With Plymouth enabled you just see the
> splash screen. With it disabled (or by pressing esc) it seems to be
> stuck at "Stopped initrd-switch-root.service - Switch Root.". I'm still
> looking into this one, but it's happened to a lot of openQA tests and I
> was able to confirm it first try in a local VM, by installing from the
> 20230123.n.0 compose then updating systemd and rebooting. Fresh
> installs with the newer systemd seem to be OK, at least most openQA
> tests for the new compose passed - it seems to be only updating an
> existing install that has the problem, at least so far.

I've now filed this as
https://bugzilla.redhat.com/show_bug.cgi?id=2164594 .
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
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: Bootstrapping package with circular dependencies in koji

2023-01-25 Thread Kevin Fenzi

On Wed, Jan 25, 2023 at 03:45:35PM +0100, Jaroslav Skarvada wrote:
> On Wed, Jan 25, 2023 at 12:13 PM Miro Hrončok  wrote:
> >
> > On 25. 01. 23 11:50, Vít Ondruch wrote:
> > > Reading the thread, I was afraid this will be the end result. 
> > > Nevertheless,
> > > given this would be used just for side-tags, is there a chance to exclude 
> > > side
> > > tags from the policy? Who would handle such request?

I thought we had already done this, but it seems not. 

I am not 100% koji has the needed policy for this, so I'd say file the
issue first as a koji issue and once we can allow/disallow this via
policy we can allow it for sidetags... but see below.

> > > Although being able to modify one macro means also possibility to edit all
> > > macros. Not sure this is desired. However one can achieve almost 
> > > everything by
> > > changing .spec file, so that should not be blocker IMHO.
> >
> Or add an option that will mark/unmark the sidetag for bootstrapping,
> i.e. option that will add only this specific bootstrap macro to the
> sidetag and nothing more.

Yeah, that would be better than allowing all tag options to be set.

> > I think the "commit the bootstrap conditional directly to bootstrap 
> > something"
> > approach is much more transparent than "fiddling with macros in Koji to save
> > myself one tiny commit" anyway.
> >
> It's one commit per package. If you rebuild more packages there may be
> more things that need bootstrapping.

Also: commits to reverse the horrible with/without syntax are error
prone. If we can avoid doing them, we can probibly avoid some mistakes. 

> > To answer the original question, it can be done like this:
> >
> > 1. commit all commits and push them all
> > 2. fedpkg request-side-tag
> > 3. koji chain-build --nowait f38-build-side-6
> > 'git+https://src.fedoraproject.org/rpms/python3.12.git#fe95b37f25338c94bcfa2fb653e53b5262ec2812'
> > : ..instert mid deps here... :
> > 'git+https://src.fedoraproject.org/rpms/python3.12.git#1bc45ffecb2b268fb56fbdc61ceb0ff429168d19'
> >
> If there already are the boostrap conditionals in the specs the logic
> progress is to have some support in the infra. Just manually reverting
> the condition in the spec is, let's say not the optimal solution. Just
> my two cents.

I personally agree. 

I think ideally koji would allow us to allow/deny changing taginfo to
side tags, and even better allow/deny changing just bootstrap=1. 

kevin


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

Some heads-ups for Rawhide users: python3-ptyprocess and systemd issues

Hey folks! Just wanted to send out a heads-up for Rawhide users about
some issues that have shown up in openQA testing.

First, you may have found that trying to update to today's Rawhide
fails like this:

Error: Transaction test error:
  file /usr/lib/python3.11/site-packages/ptyprocess-0.7.0-py3.11.egg-info from 
install of python3-ptyprocess-0.7.0-2.fc38.noarch conflicts with file from 
package python3-ptyprocess-0.7.0-1.fc38.noarch

That's https://bugzilla.redhat.com/show_bug.cgi?id=2164207 , we figured
out the problem (thanks to Panu for getting to the root cause of it)
and it is fixed in python-ptyprocess-0.7.0-3.fc38 , which should be in
the next Rawhide compose. If you really can't wait you can update
directly to that version
from https://koji.fedoraproject.org/koji/buildinfo?buildID=2138649 ,
but you'd better watch out for issue #2...

The second issue is that systems that update to systemd-253~rc1-1.fc38
seem to get stuck on boot. With Plymouth enabled you just see the
splash screen. With it disabled (or by pressing esc) it seems to be
stuck at "Stopped initrd-switch-root.service - Switch Root.". I'm still
looking into this one, but it's happened to a lot of openQA tests and I
was able to confirm it first try in a local VM, by installing from the
20230123.n.0 compose then updating systemd and rebooting. Fresh
installs with the newer systemd seem to be OK, at least most openQA
tests for the new compose passed - it seems to be only updating an
existing install that has the problem, at least so far.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
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: [Fedora Update] [CRITPATH] [comment] alt-ergo-2.3.3-5.fc38, apron-0.9.13-16.fc38, and 182 more

2023-01-25 Thread Kevin Fenzi

On Wed, Jan 25, 2023 at 01:12:47PM +, Richard W.M. Jones wrote:

...snip...

> Alternately, why does an older build block a push to stable?  Won't
> the old build simply be ignored if there's a higher NVR version
> around?

Nope, koji and pungi have no idea about 'older' or 'newer', they only
know 'latest tagged package' and 'previously tagged package'. 

So, when pungi does a compose it asks koji: "hey, give me the last
tagged package for all packages in f38 tag". 

So, in this case if we did let this through, the 'older' one would be in
the compose. 

kevin

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

Re: Retiring Bottles in favor of Flatpak provided by upstream

On Wed, 2023-01-25 at 17:42 +, Richard W.M. Jones wrote:
> On Wed, Jan 25, 2023 at 06:01:17PM +0100, Vít Ondruch wrote:
> > 
> > Dne 25. 01. 23 v 15:59 Josh Boyer napsal(a):
> > > On Wed, Jan 25, 2023 at 5:56 AM Vít Ondruch  wrote:
> > > > I am not user of Bottles so I won't complain about this particular case,
> > > > but the push towards (upstream) Flatpaks is unfortunate :/
> > > Can you elaborate on why you feel that way?
> > 
> > 
> > I don't trust upstream Flatpacks. I don't trust they follow any
> > standard except standard of their authors.
> > 
> > And I don't like Flatpacks, because their main advantage (their
> > isolation) is also their biggest disadvantage. There can't be both
> > without making compromises. If I am not mistaken, the isolation is
> > also mostly myth, because it is disabled in most cases.
> 
> In addition to this, the supposed promise of Flatpaks (eg [1]) is that
> they are built from Fedora's RPMs.

No, that's the promise of Fedora Flatpaks, which is an effort with a
distinct identity and philosophy (but which is, uh, not being its best
possible self so far, I think everyone would agree). It's not the
promise of flatpaks in general.

>   But how does that work for
> "upstream" Flatpaks?  How do we know they don't contain non-free
> software?  How do we ensure we can obtain and rebuild from source?

Basically, you have to trust that the maintainer of the upstream F/OSS
project cares about and ensures those things.

I'm not 100% a fan of this either (having seen enough cases where
upstream's interpretation of F/OSS differs from mine or Fedora's, and
enough cases where upstream just didn't take enough care about it).

OTOH, it's not reasonable to dictate to the person maintaining a Fedora
package whether they should think that's a reasonable use of their time
or not. The current maintainers of Bottles decided they trust the
upstream developers to distribute their software 'properly' and thus
didn't want to dedicate their time to maintaining the package any more;
that's entirely their decision to make.

Of course, it should still be the case that someone who still sees
value in distribution packaging of bottles can take the package over if
they want to, as Pete Walter has already asked to do.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
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: Retiring Bottles in favor of Flatpak provided by upstream

On Wed, Jan 25, 2023 at 06:01:17PM +0100, Vít Ondruch wrote:
> 
> Dne 25. 01. 23 v 15:59 Josh Boyer napsal(a):
> >On Wed, Jan 25, 2023 at 5:56 AM Vít Ondruch  wrote:
> >>I am not user of Bottles so I won't complain about this particular case,
> >>but the push towards (upstream) Flatpaks is unfortunate :/
> >Can you elaborate on why you feel that way?
> 
> 
> I don't trust upstream Flatpacks. I don't trust they follow any
> standard except standard of their authors.
> 
> And I don't like Flatpacks, because their main advantage (their
> isolation) is also their biggest disadvantage. There can't be both
> without making compromises. If I am not mistaken, the isolation is
> also mostly myth, because it is disabled in most cases.

In addition to this, the supposed promise of Flatpaks (eg [1]) is that
they are built from Fedora's RPMs.  But how does that work for
"upstream" Flatpaks?  How do we know they don't contain non-free
software?  How do we ensure we can obtain and rebuild from source?

Rich.

[1] https://fedoramagazine.org/an-introduction-to-fedora-flatpaks/

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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: Bootstrapping package with circular dependencies in koji

Dne 25. 01. 23 v 15:45 Jaroslav Skarvada napsal(a):

On Wed, Jan 25, 2023 at 12:13 PM Miro Hrončok wrote:

On 25. 01. 23 11:50, Vít Ondruch wrote:

Reading the thread, I was afraid this will be the end result. Nevertheless,
given this would be used just for side-tags, is there a chance to exclude side
tags from the policy? Who would handle such request?

Although being able to modify one macro means also possibility to edit all
macros. Not sure this is desired. However one can achieve almost everything by
changing .spec file, so that should not be blocker IMHO.

Or add an option that will mark/unmark the sidetag for bootstrapping,
i.e. option that will add only this specific bootstrap macro to the
sidetag and nothing more.

I think the "commit the bootstrap conditional directly to bootstrap something"
approach is much more transparent than "fiddling with macros in Koji to save
myself one tiny commit" anyway.

It's one commit per package. If you rebuild more packages there may be
more things that need bootstrapping.

Right. I was the one proposing bootstrap macro and I did it with Ruby on
Rails rebuild in mind. That was ~8 packages at that time (but the full
dependency chain is probably more than 100 packages). So it would be
really handy if I could do:

1. Commit everything.

2. Build with bootstrap everything.

3. Build without bootstrap everything.

I still think it would be of great benefit for mass rebuilds, where one
needs to work with large sets of packages without intimate knowledge of
each package.

Vít

---

To answer the original question, it can be done like this:

1. commit all commits and push them all
2. fedpkg request-side-tag
3. koji chain-build --nowait f38-build-side-6
'git+https://src.fedoraproject.org/rpms/python3.12.git#fe95b37f25338c94bcfa2fb653e53b5262ec2812'
: ..instert mid deps here... :
'git+https://src.fedoraproject.org/rpms/python3.12.git#1bc45ffecb2b268fb56fbdc61ceb0ff429168d19'

If there already are the boostrap conditionals in the specs the logic
progress is to have some support in the infra. Just manually reverting
the condition in the spec is, let's say not the optimal solution. Just
my two cents.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue

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

Re: Retiring Bottles in favor of Flatpak provided by upstream



Dne 25. 01. 23 v 15:59 Josh Boyer napsal(a):

On Wed, Jan 25, 2023 at 5:56 AM Vít Ondruch  wrote:

I am not user of Bottles so I won't complain about this particular case,
but the push towards (upstream) Flatpaks is unfortunate :/

Can you elaborate on why you feel that way?



I don't trust upstream Flatpacks. I don't trust they follow any standard 
except standard of their authors.


And I don't like Flatpacks, because their main advantage (their 
isolation) is also their biggest disadvantage. There can't be both 
without making compromises. If I am not mistaken, the isolation is also 
mostly myth, because it is disabled in most cases.



Vít




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


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

Re: Retiring Bottles in favor of Flatpak provided by upstream

2023-01-25 Thread Josh Boyer

On Wed, Jan 25, 2023 at 5:56 AM Vít Ondruch  wrote:
>
> I am not user of Bottles so I won't complain about this particular case,
> but the push towards (upstream) Flatpaks is unfortunate :/

Can you elaborate on why you feel that way?

josh
___
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-Wx] PR #2: Rebuild with wxWidgets 3.2

2023-01-25 Thread Scott Talbert


swt2c commented on the pull-request: `Rebuild with wxWidgets 3.2` that you are 
following:
``
@spot , Can you please build this in rawhide now?
``

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

Re: Bootstrapping package with circular dependencies in koji

2023-01-25 Thread Jaroslav Skarvada

On Wed, Jan 25, 2023 at 12:13 PM Miro Hrončok  wrote:
>
> On 25. 01. 23 11:50, Vít Ondruch wrote:
> > Reading the thread, I was afraid this will be the end result. Nevertheless,
> > given this would be used just for side-tags, is there a chance to exclude 
> > side
> > tags from the policy? Who would handle such request?
> >
> > Although being able to modify one macro means also possibility to edit all
> > macros. Not sure this is desired. However one can achieve almost everything 
> > by
> > changing .spec file, so that should not be blocker IMHO.
>
Or add an option that will mark/unmark the sidetag for bootstrapping,
i.e. option that will add only this specific bootstrap macro to the
sidetag and nothing more.

> I think the "commit the bootstrap conditional directly to bootstrap something"
> approach is much more transparent than "fiddling with macros in Koji to save
> myself one tiny commit" anyway.
>
It's one commit per package. If you rebuild more packages there may be
more things that need bootstrapping.

> ---
>
> To answer the original question, it can be done like this:
>
> 1. commit all commits and push them all
> 2. fedpkg request-side-tag
> 3. koji chain-build --nowait f38-build-side-6
> 'git+https://src.fedoraproject.org/rpms/python3.12.git#fe95b37f25338c94bcfa2fb653e53b5262ec2812'
> : ..instert mid deps here... :
> 'git+https://src.fedoraproject.org/rpms/python3.12.git#1bc45ffecb2b268fb56fbdc61ceb0ff429168d19'
>
If there already are the boostrap conditionals in the specs the logic
progress is to have some support in the infra. Just manually reverting
the condition in the spec is, let's say not the optimal solution. Just
my two cents.
___
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: [Fedora Update] [CRITPATH] [comment] alt-ergo-2.3.3-5.fc38, apron-0.9.13-16.fc38, and 182 more

On Wed, Jan 25, 2023 at 01:12:47PM +, Richard W.M. Jones wrote:
> How do you edit the list of builds (to remove a build)?  I cannot see
> any way to do this in the UI.

Thanks Mamoru Tasaka for editing it.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: [Fedora Update] [CRITPATH] [comment] alt-ergo-2.3.3-5.fc38, apron-0.9.13-16.fc38, and 182 more

2023-01-25 Thread Mamoru TASAKA


Richard W.M. Jones wrote on 2023/01/25 22:12:

On Wed, Jan 25, 2023 at 11:22:18AM +, Richard W.M. Jones wrote:

On Wed, Jan 25, 2023 at 10:43:50AM +, upda...@fedoraproject.org wrote:

The following comment has been added to the alt-ergo-2.3.3-5.fc38 
apron-0.9.13-16.fc38 [...] update:

bodhi - 2023-01-25 10:43:50.440400 (karma: 0)
This update cannot be pushed to stable. These builds graphviz-7.0.6-4.fc38 have 
a more recent build in koji's f38 tag.


Jaroslav, could you do a build into the f38-build-side-62208
side tag please, ie:

   fedpkg build --target=f38-build-side-62208

Alternately, I could drop the graphviz package from this update and
then you'll have to do a build afterwards (or the OCaml part will be
broken).

Rich.


To reply to this comment, please visit the URL at the bottom of this mail


  FEDORA-2023-7bd037f981

 Release: Fedora 38
  Status: testing
Type: unspecified
Severity: unspecified
   Karma: 0
Critpath: True
   Notes: Rebuild all OCaml packages after the F38 mass rebuild
   Submitter: rjones
   Submitted: 2023-01-25 09:41:44.872273
Comments: bodhi - 2023-01-25 10:43:50.440400 (karma 0)
  This update cannot be pushed to stable. These builds
  graphviz-7.0.6-4.fc38 have a more recent build in
  koji's f38 tag.
  bodhi - 2023-01-25 10:39:35.011437 (karma 0)
  This update's test gating status has been changed to
  'ignored'.
  bodhi - 2023-01-25 09:41:45.003272 (karma 0)
  This update's test gating status has been changed to
  'waiting'.

   https://bodhi.fedoraproject.org/updates/FEDORA-2023-7bd037f981


And I could do with some help here too...

How do you edit the list of builds (to remove a build)?  I cannot see
any way to do this in the UI.

Alternately, why does an older build block a push to stable?  Won't
the old build simply be ignored if there's a higher NVR version
around?

Rich.



For now I removed graphviz-7.0.6-4.fc38 from the above bodhi request, and
the rest 183 pkgs now went to f38 buildroot.

Just note: side-tag can be untagged:
$ koji untag f38-build-side-62208  graphviz-7.0.6-4.fc38

Then again go to the bodhi request and push "edit", and push "reload" side-tag
build, then actually untagged builds are removed from update request.

Regards,
Mamoru
___
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: List of long term FTBFS packages to be retired in February

2023-01-25 Thread Susi Lehtola

On 1/25/23 13:04, Alexander Ploumistos wrote:
> On Tue, Jan 24, 2023 at 3:56 PM Miro Hrončok  wrote:
>>
>> IQmoljussilehtola
> 
> I'm leaving this comment in case Susi (Cc) didn't get the previous
> mail like last time. I know that they're working with upstream to
> package the next version of IQmol, so this should be resolved sooner
> or later.

Hi,

yes, un-addressed mail (bcc) is insufficient to contact package maintainers;
thanks for the ping. I am aware of the issue thanks to Bugzilla, and am actively
working to find a resolution.

The current problem is that libQGLViewer (cc'd) was last updated 5 years ago,
and the up-to-date version of IQmol that supports OpenBabel3 needs a more recent
version of libQGLViewer.

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

Re: [Fedora Update] [CRITPATH] [comment] alt-ergo-2.3.3-5.fc38, apron-0.9.13-16.fc38, and 182 more

On Wed, Jan 25, 2023 at 11:22:18AM +, Richard W.M. Jones wrote:
> On Wed, Jan 25, 2023 at 10:43:50AM +, upda...@fedoraproject.org wrote:
> > The following comment has been added to the alt-ergo-2.3.3-5.fc38 
> > apron-0.9.13-16.fc38 [...] update:
> > 
> > bodhi - 2023-01-25 10:43:50.440400 (karma: 0)
> > This update cannot be pushed to stable. These builds graphviz-7.0.6-4.fc38 
> > have a more recent build in koji's f38 tag.
> 
> Jaroslav, could you do a build into the f38-build-side-62208
> side tag please, ie:
> 
>   fedpkg build --target=f38-build-side-62208
> 
> Alternately, I could drop the graphviz package from this update and
> then you'll have to do a build afterwards (or the OCaml part will be
> broken).
> 
> Rich.
> 
> > To reply to this comment, please visit the URL at the bottom of this mail
> > 
> > 
> >  FEDORA-2023-7bd037f981
> > 
> > Release: Fedora 38
> >  Status: testing
> >Type: unspecified
> >Severity: unspecified
> >   Karma: 0
> >Critpath: True
> >   Notes: Rebuild all OCaml packages after the F38 mass rebuild
> >   Submitter: rjones
> >   Submitted: 2023-01-25 09:41:44.872273
> >Comments: bodhi - 2023-01-25 10:43:50.440400 (karma 0)
> >  This update cannot be pushed to stable. These builds
> >  graphviz-7.0.6-4.fc38 have a more recent build in
> >  koji's f38 tag.
> >  bodhi - 2023-01-25 10:39:35.011437 (karma 0)
> >  This update's test gating status has been changed to
> >  'ignored'.
> >  bodhi - 2023-01-25 09:41:45.003272 (karma 0)
> >  This update's test gating status has been changed to
> >  'waiting'.
> > 
> >   https://bodhi.fedoraproject.org/updates/FEDORA-2023-7bd037f981

And I could do with some help here too...

How do you edit the list of builds (to remove a build)?  I cannot see
any way to do this in the UI.

Alternately, why does an older build block a push to stable?  Won't
the old build simply be ignored if there's a higher NVR version
around?

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

Re: Retiring Bottles in favor of Flatpak provided by upstream

2023-01-25 Thread Fabio Valentini

On Wed, Jan 25, 2023 at 12:38 PM Pete Walter  wrote:
>
> I am not happy about dropping Fedora packages in favor of upstream Flatpaks 
> either.
>
> Can you assign the package to me instead of retiring it? I can get it updated 
> so we can keep it in Fedora.

It looks like Bottles itself doesn't contain any Rust code, so I
assume some of its Python dependencies now build native modules that
are implemented in Rust?
If that's the case, then it should be possible to package them for
Fedora. The most prominent example is probably python-cryptography,
and assuming the Python packages use setuptools with the
setuptools_rust backend for building the native module, it can be used
as a guide for how to package Python packages with Rust dependencies
correctly.

If the projects use maturin as their build backend, some more work is
involved, since packaging maturin itself for Fedora will require
significant investment of time and resources (that I am currently
unable to provide alone). However, it should be possible in almost all
cases to "port" Python packages from maturin to setuptools_rust, since
setuptools_rust is more flexible and less opinionated than maturin
(and they are almost entirely compatible with each other, since
they're developed by the same project). Additionally, Fedora builds
don't need any of the additional bells and whistles that maturin
provides for upstream development (i.e. cross-compilation to different
targets + architectures), so porting projects back from maturin to
setuptools_rust should usually be possible without losing any
functionality that is required for building RPM packages for Fedora.

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

[Bug 2162854] perl-URI-Title-1.903 is available

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-URI-Title-1.903-1.fc38
 Resolution|--- |RAWHIDE
 Status|ASSIGNED|CLOSED
Last Closed||2023-01-25 12:43:30




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

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162740
___
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-URI-Title] PR #1: 1.903 bump; Package tests

2023-01-25 Thread Jitka Plesnikova


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

Merged pull-request:

``
1.903 bump; Package tests
``

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

[Bug 2162740] perl-Module-CoreList-5.20230120 is available

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



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


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

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
 CC|jose.p.oliveira.oss@gmail.c |
   |om, jples...@redhat.com,|
   |mspa...@redhat.com, |
   |spo...@gmail.com,   |
   |st...@silug.org |
   Fixed In Version||perl-Module-CoreList-5.2023
   ||0120-1.fc38
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162740
___
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: Retiring Bottles in favor of Flatpak provided by upstream

2023-01-25 Thread Vascom

Seems as bad practice to drop packages by upstream request.

ср, 25 янв. 2023 г. в 14:38, Pete Walter :
>
> I am not happy about dropping Fedora packages in favor of upstream Flatpaks 
> either.
>
> Can you assign the package to me instead of retiring it? I can get it updated 
> so we can keep it in Fedora.
>
> Pete
>
> 25.01.2023, 10:56, "Vít Ondruch" :
>
> I am not user of Bottles so I won't complain about this particular case,
> but the push towards (upstream) Flatpaks is unfortunate :/
>
>
> Vít
>
>
> Dne 24. 01. 23 v 22:44 Sandro napsal(a):
>
>  Hi,
>
>  Development of Bottles is moving fast and we have been struggling to
>  keep up with upstream releases, especially since the introduction of
>  Rust components.
>
>  Upstream has approached the maintainers [1,2] and asked us to retire
>  the package in favor of the Flatpak packages provided by upstream.
>
>  I'm planning to move forward with retiring Bottles in the coming days.
>  I will add a comment in all open bug reports, letting users know they
>  should switch to the Flatpak release.
>
>  Bottles in F36 and F37 will not receive any further updates unless
>  there are security related issues surfacing.
>
>  [1] https://github.com/bottlesdevs/Bottles/issues/2345
>  [2] https://bugzilla.redhat.com/show_bug.cgi?id=2160007
>
>  Cheers,
>
>  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
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162728] perl-CPAN-Perl-Releases-5.20230120 is available

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



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


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

sprintf assertion failure in rawhide

2023-01-25 Thread Florian Weimer

glibc-2.36.9000-24.fc38 should fix this assertion failure:

Fatal glibc error: printf_buffer_as_file.c:31 (__printf_buffer_as_file_commit): 
assertion failed: file->stream._IO_write_ptr <= file->next->write_end

It's a logic bug in the fortified implementation of the sprintf family
of functions.  This happens if GCC cannot divine the buffer length, but
still calls the fortified version for format string checking (for %n),
*and* that sprintf call uses a registered format specifier.  So far,
I've seen this with libquadmath, which registers
replacements/enhancement for the standard fFeEgGaA specifiers
(necessarily for the double type as well), to implement the Q modifier.

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

[Bug 2162728] perl-CPAN-Perl-Releases-5.20230120 is available

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-CPAN-Perl-Releases-5.2
   ||0230120-1.fc38




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

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

Jitka Plesnikova  changed:

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162728
___
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-URI-Title] PR #1: 1.903 bump; Package tests

2023-01-25 Thread Jitka Plesnikova


jplesnik opened a new pull-request against the project: `perl-URI-Title` that 
you are following:
``
1.903 bump; Package tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-URI-Title/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: Retiring Bottles in favor of Flatpak provided by upstream

2023-01-25 Thread Pete Walter

I am not happy about dropping Fedora packages in favor of upstream Flatpaks either. Can you assign the package to me instead of retiring it? I can get it updated so we can keep it in Fedora. Pete 25.01.2023, 10:56, "Vít Ondruch" :I am not user of Bottles so I won't complain about this particular case,but the push towards (upstream) Flatpaks is unfortunate :/VítDne 24. 01. 23 v 22:44 Sandro napsal(a): Hi, Development of Bottles is moving fast and we have been struggling to keep up with upstream releases, especially since the introduction of Rust components. Upstream has approached the maintainers [1,2] and asked us to retire the package in favor of the Flatpak packages provided by upstream. I'm planning to move forward with retiring Bottles in the coming days. I will add a comment in all open bug reports, letting users know they should switch to the Flatpak release. Bottles in F36 and F37 will not receive any further updates unless there are security related issues surfacing. [1] https://github.com/bottlesdevs/Bottles/issues/2345 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2160007 Cheers, Sandro,___devel mailing list -- devel@lists.fedoraproject.orgTo unsubscribe send an email to devel-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.orgDo 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: Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)


On 25. 01. 23 12:22, Zbigniew Jędrzejewski-Szmek wrote:

On Wed, Jan 25, 2023 at 12:18:59PM +0100, Miro Hrončok wrote:

On 24. 01. 23 18:57, Neal Gompa wrote:

On Tue, Jan 24, 2023 at 12:50 PM Ben Cotton  wrote:


NOTE: As explained by the owners in the Feedback section below, this
proposal was submitted after the deadline because the impact of the
package update proved to be broader than anticipated.

https://fedoraproject.org/wiki/Changes/Packaging_22%2B

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
Update to a new upstream release of python-packaging contains a
breaking change. Since version 22+ upstream removed support for
[https://github.com/pypa/packaging/pull/407 LegacySpecifier and
LegacyVersion] some packages will break. This is a breaking change and
projects are encouraged to use versions adherent to
[https://peps.python.org/pep-0440/ PEP 440].

Note: Currently, we plan to update to 23.0, but this can be updated
even further. The change proposal explicitly mentions version 22+
because that version removed support for LegacyVersions and legacy
version specifiers.



Can the title of this Change be changed? It's not particularly clear
what this is from the title.


Changed to: Update python-packaging to version >= 22

Leaving the URL as is, unless people think it should be changed too.


Mediawiki shows the page title as "Changes/Packaging 22+". I think
it should be renamed. Mediawiki handles redirects nicely.


https://fedoraproject.org/wiki/Changes/Update_python-packaging_to_version_22_plus

--
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: [Fedora Update] [CRITPATH] [comment] alt-ergo-2.3.3-5.fc38, apron-0.9.13-16.fc38, and 182 more

On Wed, Jan 25, 2023 at 10:43:50AM +, upda...@fedoraproject.org wrote:
> The following comment has been added to the alt-ergo-2.3.3-5.fc38 
> apron-0.9.13-16.fc38 [...] update:
> 
> bodhi - 2023-01-25 10:43:50.440400 (karma: 0)
> This update cannot be pushed to stable. These builds graphviz-7.0.6-4.fc38 
> have a more recent build in koji's f38 tag.

Jaroslav, could you do a build into the f38-build-side-62208
side tag please, ie:

  fedpkg build --target=f38-build-side-62208

Alternately, I could drop the graphviz package from this update and
then you'll have to do a build afterwards (or the OCaml part will be
broken).

Rich.

> To reply to this comment, please visit the URL at the bottom of this mail
> 
> 
>  FEDORA-2023-7bd037f981
> 
> Release: Fedora 38
>  Status: testing
>Type: unspecified
>Severity: unspecified
>   Karma: 0
>Critpath: True
>   Notes: Rebuild all OCaml packages after the F38 mass rebuild
>   Submitter: rjones
>   Submitted: 2023-01-25 09:41:44.872273
>Comments: bodhi - 2023-01-25 10:43:50.440400 (karma 0)
>  This update cannot be pushed to stable. These builds
>  graphviz-7.0.6-4.fc38 have a more recent build in
>  koji's f38 tag.
>  bodhi - 2023-01-25 10:39:35.011437 (karma 0)
>  This update's test gating status has been changed to
>  'ignored'.
>  bodhi - 2023-01-25 09:41:45.003272 (karma 0)
>  This update's test gating status has been changed to
>  'waiting'.
> 
>   https://bodhi.fedoraproject.org/updates/FEDORA-2023-7bd037f981
> 

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

Re: Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)

2023-01-25 Thread Zbigniew Jędrzejewski-Szmek

On Wed, Jan 25, 2023 at 12:18:59PM +0100, Miro Hrončok wrote:
> On 24. 01. 23 18:57, Neal Gompa wrote:
> > On Tue, Jan 24, 2023 at 12:50 PM Ben Cotton  wrote:
> > > 
> > > NOTE: As explained by the owners in the Feedback section below, this
> > > proposal was submitted after the deadline because the impact of the
> > > package update proved to be broader than anticipated.
> > > 
> > > https://fedoraproject.org/wiki/Changes/Packaging_22%2B
> > > 
> > > This document represents a proposed Change. As part of the Changes
> > > process, proposals are publicly announced in order to receive
> > > community feedback. This proposal will only be implemented if approved
> > > by the Fedora Engineering Steering Committee.
> > > 
> > > == Summary ==
> > > Update to a new upstream release of python-packaging contains a
> > > breaking change. Since version 22+ upstream removed support for
> > > [https://github.com/pypa/packaging/pull/407 LegacySpecifier and
> > > LegacyVersion] some packages will break. This is a breaking change and
> > > projects are encouraged to use versions adherent to
> > > [https://peps.python.org/pep-0440/ PEP 440].
> > > 
> > > Note: Currently, we plan to update to 23.0, but this can be updated
> > > even further. The change proposal explicitly mentions version 22+
> > > because that version removed support for LegacyVersions and legacy
> > > version specifiers.
> > > 
> > 
> > Can the title of this Change be changed? It's not particularly clear
> > what this is from the title.
> 
> Changed to: Update python-packaging to version >= 22
> 
> Leaving the URL as is, unless people think it should be changed too.

Mediawiki shows the page title as "Changes/Packaging 22+". I think
it should be renamed. Mediawiki handles redirects nicely.

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

Re: Late F38 proposal: Packaging 22+ (Self-Contained Change proposal)


On 24. 01. 23 18:57, Neal Gompa wrote:

On Tue, Jan 24, 2023 at 12:50 PM Ben Cotton  wrote:


NOTE: As explained by the owners in the Feedback section below, this
proposal was submitted after the deadline because the impact of the
package update proved to be broader than anticipated.

https://fedoraproject.org/wiki/Changes/Packaging_22%2B

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
Update to a new upstream release of python-packaging contains a
breaking change. Since version 22+ upstream removed support for
[https://github.com/pypa/packaging/pull/407 LegacySpecifier and
LegacyVersion] some packages will break. This is a breaking change and
projects are encouraged to use versions adherent to
[https://peps.python.org/pep-0440/ PEP 440].

Note: Currently, we plan to update to 23.0, but this can be updated
even further. The change proposal explicitly mentions version 22+
because that version removed support for LegacyVersions and legacy
version specifiers.



Can the title of this Change be changed? It's not particularly clear
what this is from the title.


Changed to: Update python-packaging to version >= 22

Leaving the URL as is, unless people think it should be changed too.

--
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: Bootstrapping package with circular dependencies in koji

On 25. 01. 23 11:50, Vít Ondruch wrote:
Reading the thread, I was afraid this will be the end result. Nevertheless,
given this would be used just for side-tags, is there a chance to exclude side
tags from the policy? Who would handle such request?

I think the "commit the bootstrap conditional directly to bootstrap something"
approach is much more transparent than "fiddling with macros in Koji to save
myself one tiny commit" anyway.

---

To answer the original question, it can be done like this:

--
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: List of long term FTBFS packages to be retired in February

2023-01-25 Thread Alexander Ploumistos

On Tue, Jan 24, 2023 at 3:56 PM Miro Hrončok  wrote:
>
> IQmoljussilehtola

I'm leaving this comment in case Susi (Cc) didn't get the previous
mail like last time. I know that they're working with upstream to
package the next version of IQmol, so this should be resolved sooner
or later.
___
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: Retiring Bottles in favor of Flatpak provided by upstream

I am not user of Bottles so I won't complain about this particular case, 
but the push towards (upstream) Flatpaks is unfortunate :/



Vít


Dne 24. 01. 23 v 22:44 Sandro napsal(a):

Hi,

Development of Bottles is moving fast and we have been struggling to 
keep up with upstream releases, especially since the introduction of 
Rust components.


Upstream has approached the maintainers [1,2] and asked us to retire 
the package in favor of the Flatpak packages provided by upstream.


I'm planning to move forward with retiring Bottles in the coming days. 
I will add a comment in all open bug reports, letting users know they 
should switch to the Flatpak release.


Bottles in F36 and F37 will not receive any further updates unless 
there are security related issues surfacing.


[1] https://github.com/bottlesdevs/Bottles/issues/2345
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2160007

Cheers,

Sandro


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

Re: FYI xz 5.4.1 in Fedora updates (F36, F37, Rawhide)


On 24. 01. 23 17:21, Miro Hrončok wrote:

On 24. 01. 23 16:20, Miro Hrončok wrote:

On 23. 01. 23 15:39, Richard W.M. Jones wrote:


F36: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d823c8dfb8

F37: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8362bcf475

One package which is known to depend on the exact version of xz is
perl-Compress-Raw-Lzma.  The updates above should do the right thing.

As far as I'm aware there are no other packages that depend on the
exact version of xz (or liblzma) and no breaking changes to liblzma,
but if there are please let us know.


For the record, Pythons now FTBFS with:

==
FAIL: test_unzip_zipfile (test.test_shutil.TestArchives.test_unzip_zipfile)
--
Traceback (most recent call last):
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/test/test_shutil.py", line 
1514, in test_unzip_zipfile

 subprocess.check_output(zip_cmd, stderr=subprocess.STDOUT)
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/subprocess.py", line 466, 
in check_output

 return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
    ^
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/subprocess.py", line 571, 
in run

 raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']' returned non-zero exit status 80.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
   File "/builddir/build/BUILD/Python-3.12.0a4/Lib/test/test_shutil.py", line 
1520, in test_unzip_zipfile

 self.fail(msg.format(exc, details))
AssertionError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']' returned non-zero exit status 80.

**Unzip Output**
Archive: 
/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip

*** buffer overflow detected ***: terminated
--


I have not yet verified this is cuased by new xz, but it is one of the suspects.

https://koschei.fedoraproject.org/package/python3.12?collection=f38


I cannot reproduce this in mock just by updating xz, so it seems it is 
unrelated.


I forgot to follow up. It is unzip:

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

--
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: FYI xz 5.4.1 in Fedora updates (F36, F37, Rawhide)


On 25. 01. 23 11:16, Zbigniew Jędrzejewski-Szmek wrote:

On Tue, Jan 24, 2023 at 04:20:41PM +0100, Miro Hrončok wrote:

subprocess.CalledProcessError: Command '['unzip', '-t', 
'/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']'
returned non-zero exit status 80.



**Unzip Output**
Archive: 
/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip
*** buffer overflow detected ***: terminated
--



I have not yet verified this is cuased by new xz, but it is one of the suspects.

https://koschei.fedoraproject.org/package/python3.12?collection=f38


It seems that 'unzip' fails, so not related to xz?


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


My guess would be that this is _FORTIFY_SOURCE=3 catching some bug in unzip.


That is a possibility.

--
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: Bootstrapping package with circular dependencies in koji

Reading the thread, I was afraid this will be the end result. 
Nevertheless, given this would be used just for side-tags, is there a 
chance to exclude side tags from the policy? Who would handle such request?


Although being able to modify one macro means also possibility to edit 
all macros. Not sure this is desired. However one can achieve almost 
everything by changing .spec file, so that should not be blocker IMHO.



Vít


Dne 25. 01. 23 v 9:18 Richard Lescak napsal(a):
Unfortunately we have tried to use 'koji edit-tag SIDETAG -x 
%_with_bootstrap=1' command but it always ended with 'koji: 
ActionNotAllowed: tag permission required (logged in as USER)' even 
when creator of the sidetag used the command.


On Tue, Jan 24, 2023 at 10:45 PM Kevin Fenzi  wrote:

On Tue, Jan 24, 2023 at 03:36:41PM -0500, Neal Gompa wrote:
> On Tue, Jan 24, 2023 at 3:00 PM Kevin Fenzi  wrote:
> >
> > On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote:
> > >
> > > I initially thought about:
> > > release bump
> > > $ koji edit-tag SIDETAG -x %_with_bootstrap=1
> > > build
> > > handle circular dep
> > > $ koji edit-tag SIDETAG -r %_with_bootstrap
> > > build
> > >
> > > But I haven't tried it yet because I didn't want to break
anything :)
> > > Is this the correct way to do it?
> >
> > That should work, (as long as you bump the release for the
second build
> > as koji will not let you rebuild the same n-v-r)
> > but I am not sure anyone has tried it.
> >
>
> The NVR will automatically change when you flip between modes, since
> it changes the DistTag.

Ah indeed.

So you should only need 1 initial commit.

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



--

Richard Lescak

Associate Software Engineer

Red Hat Czech - Brno TPB-C 




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


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

Re: FYI xz 5.4.1 in Fedora updates (F36, F37, Rawhide)

2023-01-25 Thread Zbigniew Jędrzejewski-Szmek

On Tue, Jan 24, 2023 at 04:20:41PM +0100, Miro Hrončok wrote:
> subprocess.CalledProcessError: Command '['unzip', '-t', 
> '/builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip']'
> returned non-zero exit status 80.

> **Unzip Output**
> Archive: 
> /builddir/build/BUILD/Python-3.12.0a4/build/debug/build/test_python_64979æ/tmpau1avwr6/archive.zip
> *** buffer overflow detected ***: terminated
> --

> I have not yet verified this is cuased by new xz, but it is one of the 
> suspects.
> 
> https://koschei.fedoraproject.org/package/python3.12?collection=f38

It seems that 'unzip' fails, so not related to xz?
My guess would be that this is _FORTIFY_SOURCE=3 catching some bug in unzip.

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

(Fixed) Re: Most OCaml packages have broken deps now