Re: [Fedora-packaging] BuildrootError: could not init mock buildroot ... see root.log ...

2024-01-17 Thread Mamoru TASAKA 

Brad Bell wrote on 2024/01/18 14:00:

I got the Result in the subject above for the following build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=111912575

Looking at the corresponding root.log
https://kojipkgs.fedoraproject.org//work/tasks/2575/111912575/root.log
does not indicate to me what went wrong or how I should proceed ?
--
___


Looking at root.log:

x86_64 (successful)
https://kojipkgs.fedoraproject.org//work/tasks/2577/111912577/root.log

DEBUG util.py:558:  Executing command: ['/bin/mount', '-n', '-o', 
'remount,private,rbind', '--target', 
'/var/lib/mock/f40-build-48240062-5748626-bootstrap/root/var/lib/mock/f40-build-48240062-5748626/root']
 with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 
'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'C.UTF-8'} 
and shell False
DEBUG util.py:610:  Child return code was: 0
DEBUG file_util.py:18:  ensuring that dir exists: 
/var/lib/mock/f40-build-48240062-5748626/root/installation-homedir
DEBUG file_util.py:21:  created dir: 
/var/lib/mock/f40-build-48240062-5748626/root/installation-homedir
DEBUG package_manager.py:289:  ['/usr/bin/dnf5', '--installroot', 
'/var/lib/mock/f40-build-48240062-5748626/root/', 'group', 'install', 'build', 
'--setopt=deltarpm=False', '--setopt=allow_vendor_change=yes']
DEBUG util.py:636:  child environment: None
DEBUG util.py:553:  Using nspawn with args ['--capability=cap_ipc_lock', 
'--bind=/tmp/mock-resolv.fdt5pbne:/etc/resolv.conf']
DEBUG util.py:558:  Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '69286198251d4cbebe3bbba5ac862e76', '-D', 
'/var/lib/mock/f40-build-48240062-5748626-bootstrap/root', '-a', '--capability=cap_ipc_lock', 
'--bind=/tmp/mock-resolv.fdt5pbne:/etc/resolv.conf', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', 
'--setenv=HOME=/var/lib/mock/f40-build-48240062-5748626/root/installation-homedir', '--setenv=HOSTNAME=mock', 
'--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf 
"\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', 
'--setenv=LC_MESSAGES=C.UTF-8', '--resolv-conf=off', '/usr/bin/dnf5', '--installroot', 
'/var/lib/mock/f40-build-48240062-5748626/root/', 'group', 'install', 'build', '--setopt=deltarpm=False', 
'--setopt=allow_vendor_change=yes', '--setopt=tsflags=nocontexts'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': 
'/var/lib/mock/f40-build-48240062-5748626/root/installation-homedir', 'HOSTNAME': 'mock', 'PATH': 
'/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': 
' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'LC_MESSAGES': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 
'SYSTEMD_SECCOMP': '0'} and shell False
DEBUG util.py:463:  Updating and loading repositories:
DEBUG util.py:463:   build  100% |  97.2 MiB/s 
|  17.6 MiB |  00m00s

i686 (failing)
https://kojipkgs.fedoraproject.org//work/tasks/2575/111912575/root.log

DEBUG util.py:558:  Executing command: ['/bin/mount', '-n', '-o', 
'remount,private,rbind', '--target', 
'/var/lib/mock/f40-build-48240060-5748626-bootstrap/root/var/lib/mock/f40-build-48240060-5748626/root']
 with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 
'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'C.UTF-8'} 
and shell False
DEBUG util.py:610:  Child return code was: 0
DEBUG file_util.py:18:  ensuring that dir exists: 
/var/lib/mock/f40-build-48240060-5748626/root/installation-homedir
DEBUG file_util.py:21:  created dir: 
/var/lib/mock/f40-build-48240060-5748626/root/installation-homedir
DEBUG package_manager.py:289:  ['/usr/bin/dnf5', '--installroot', 
'/var/lib/mock/f40-build-48240060-5748626/root/', 'group', 'install', 'build', 
'--setopt=deltarpm=False', '--setopt=allow_vendor_change=yes', '--allowerasing'] 
<=
DEBUG util.py:636:  child environment: None
DEBUG util.py:553:  Using nspawn with args ['--capability=cap_ipc_lock', 
'--bind=/tmp/mock-resolv.4fqzpd1k:/etc/resolv.conf']
DEBUG util.py:558:  Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '41961b9ee3b140eda2ee2c91559a676a', '-D', 
'/var/lib/mock/f40-build-48240060-5748626-bootstrap/root', '-a', '--capability=cap_ipc_lock', 
'--bind=/tmp/mock-resolv.4fqzpd1k:/etc/resolv.conf', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', 
'--setenv=HOME=/var/lib/mock/f40-build-48240060-5748626/root/installation-homedir', '--setenv=HOSTNAME=mock', 
'--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf 
"\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', 
'--setenv=LC_MESSAGES=C.UTF-8', '--resolv-conf=off', '/usr/bin/dnf5', '--installroot', 
'/var/lib/mock/f40-build-48240060-5748626/root/', 'group', 'install', 'build', '--setopt=deltarpm=False', 
'--setopt=allow_vendor_change=yes', '--allowerasing',

Fedora rawhide compose report: 20240117.n.0 changes

2024-01-17 Thread Fedora Rawhide Report 
OLD: Fedora-Rawhide-20240115.n.0
NEW: Fedora-Rawhide-20240117.n.0

= SUMMARY =
Added images:6
Dropped images:  1
Added packages:  21
Dropped packages:1
Upgraded packages:   257
Downgraded packages: 0

Size of added packages:  7.47 GiB
Size of dropped packages:1.22 MiB
Size of upgraded packages:   11.07 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20240117.n.0.iso
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20240117.n.0.iso
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-Rawhide-20240117.n.0.aarch64.raw.xz
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20240117.n.0.iso
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20240117.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20240117.n.0.iso

= DROPPED IMAGES =
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20240115.n.0.iso

= ADDED PACKAGES =
Package: fawltydeps-0.13.3-1.fc40
Summary: Find undeclared and unused 3rd-party dependencies in your Python 
project
RPMs:fawltydeps
Size:114.47 KiB

Package: frugally-deep-0.15.30-2.fc40
Summary: Header-only library for using Keras (TensorFlow) models in C++
RPMs:frugally-deep-devel
Size:397.40 KiB

Package: ghc-linear-1.22-1.fc40
Summary: Linear Algebra
RPMs:ghc-linear ghc-linear-devel ghc-linear-doc ghc-linear-prof
Size:14.35 MiB

Package: golang-github-aybabtme-rgbterm-0-0.13.20190624gitcc83f3b.fc40
Summary: RGB colors for your terminal
RPMs:golang-github-aybabtme-rgbterm-devel
Size:18.54 KiB

Package: golang-github-tidwall-match-1.1.1-3.fc40
Summary: Simple string pattern matcher for Go
RPMs:golang-github-tidwall-match-devel
Size:13.87 KiB

Package: golang-github-tj-buffer-1.2.0-7.fc40
Summary: Generic buffer for batching entries, such as log events
RPMs:golang-github-tj-buffer-devel
Size:13.40 KiB

Package: jack-example-tools-4-1.fc40
Summary: Examples and tools for JACK
RPMs:jack-example-tools-common jack-examples jack-examples-server 
jack-tools jack-tools-server
Size:1020.09 KiB

Package: java-21-openjdk-portable-1:21.0.1.0.12-5.fc40
Summary: OpenJDK 21 Runtime Environment portable edition
RPMs:java-21-openjdk-portable java-21-openjdk-portable-devel 
java-21-openjdk-portable-devel-fastdebug 
java-21-openjdk-portable-devel-slowdebug java-21-openjdk-portable-docs 
java-21-openjdk-portable-fastdebug java-21-openjdk-portable-misc 
java-21-openjdk-portable-slowdebug java-21-openjdk-portable-sources 
java-21-openjdk-portable-static-libs 
java-21-openjdk-portable-static-libs-fastdebug 
java-21-openjdk-portable-static-libs-slowdebug 
java-21-openjdk-portable-unstripped
Size:7.44 GiB

Package: pgrouting-3.6.1-1.fc40
Summary: Provides routing functionality to PostGIS / PostgreSQL
RPMs:pgrouting
Size:2.99 MiB

Package: rust-globwalk0.8-0.8.1-1.fc40
Summary: Glob-matched recursive file system walking
RPMs:rust-globwalk0.8+default-devel rust-globwalk0.8-devel
Size:25.71 KiB

Package: rust-owo-colors3-3.5.0-1.fc40
Summary: Zero-allocation terminal colors that'll make people go owo
RPMs:rust-owo-colors3+alloc-devel rust-owo-colors3+default-devel 
rust-owo-colors3-devel
Size:52.84 KiB

Package: rust-pretty-hex0.3-0.3.0-1.fc40
Summary: Pretty hex dump of bytes slice in the common style
RPMs:rust-pretty-hex0.3+alloc-devel rust-pretty-hex0.3+default-devel 
rust-pretty-hex0.3-devel
Size:28.96 KiB

Package: rust-rlimit-0.10.1-1.fc40
Summary: Resource limits
RPMs:rust-rlimit+default-devel rust-rlimit-devel
Size:37.67 KiB

Package: rust-uu_nl-0.0.23-1.fc40
Summary: nl ~ (uutils) display input with added line numbers
RPMs:rust-uu_nl+default-devel rust-uu_nl-devel uu_nl
Size:3.23 MiB

Package: rust-uu_numfmt-0.0.23-1.fc40
Summary: numfmt ~ (uutils) reformat NUMBER
RPMs:rust-uu_numfmt+default-devel rust-uu_numfmt-devel uu_numfmt
Size:1.71 MiB

Package: rust-uu_od-0.0.23-1.fc40
Summary: od ~ (uutils) display formatted representation of input
RPMs:rust-uu_od+default-devel rust-uu_od-devel uu_od
Size:1.73 MiB

Package: rust-uu_paste-0.0.23-1.fc40
Summary: paste ~ (uutils) merge lines from inputs
RPMs:rust-uu_paste+default-devel rust-uu_paste-devel uu_paste
Size:1.52 MiB

Package: rust-uu_pr-0.0.23-1.fc40
Summary: pr ~ (uutils) convert text files for printing
RPMs:rust-uu_pr+default-devel rust-uu_pr-devel uu_pr
Size:3.47 MiB

Package: rust-uu_yes-0.0.23-1.fc40
Summary: yes ~ (uutils) repeatedly display a line with STRING (or 'y')
RPMs:rust-uu_yes+default-devel rust-uu_yes-devel

[Bug 2258922] New: perl-Email-Sender-2.601 is available

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258922

Bug ID: 2258922
   Summary: perl-Email-Sender-2.601 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Email-Sender
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, iarn...@gmail.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.601
Upstream release that is considered latest: 2.601
Current version/release in rawhide: 2.600-3.fc39
URL: https://metacpan.org/release/Email-Sender/

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


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


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

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

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

2024-01-17 Thread updates 
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-8edcddc48e   
chromium-120.0.6099.216-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-fbdcbc3c7a   
python-templated-dictionary-1.4-1.el7


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

seamonkey-2.53.18.1-1.el7

Details about builds:



 seamonkey-2.53.18.1-1.el7 (FEDORA-EPEL-2024-45fe6b2ce2)
 Web browser, e-mail, news, IRC client, HTML editor

Update Information:

Update to 2.53.18.1

ChangeLog:

* Wed Jan 17 2024 Dmitry Butskoy  2.53.18.1-1
- update to 2.53.18.1


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

[Test-Announce] Fedora 40 Rawhide 20240117.n.0 nightly compose nominated for testing

2024-01-17 Thread rawhide 
Announcing the creation of a new nightly release validation test event
for Fedora 40 Rawhide 20240117.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20240107.n.0: anaconda-40.15-1.fc40.src, 20240117.n.0: 
anaconda-40.17-1.fc40.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/40

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240117.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Upcoming ABI breaks: amtk, tepl, gedit

2024-01-17 Thread Yaakov Selkowitz 
Plese note that as part of the update to Gedit 46, the following
packages will break ABI:

* amtk: renamed to libgedit-amtk, review needed:
https://bugzilla.redhat.com/show_bug.cgi?id=2258912

* tepl

* gedit 

Affected packages are gedit-plugins which needs to be updated to match
gedit, and (gnome-)genius which just needs a rebuild.  This will be
done in a side-tag for rawhide only once the mass rebuild is complete
and libgedit-amtk is approved.

-- 
Yaakov Selkowitz
Principal Software Engineer - Emerging RHEL
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

Re: Mass rebuild: git push --no-verify

2024-01-17 Thread kevin 
On Tue, Jan 16, 2024 at 02:50:43PM -0700, Jerry James wrote:
> Given the problems we had with font packages not being rebuilt in the
> last mass rebuild, can we ensure that the mass rebuild script uses
> "git push --no-verify" instead of plain "git push"?
> 
> See:
> - https://bugzilla.redhat.com/show_bug.cgi?id=2233878
> - 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/7IIZPEC6B4BEOOOV5YFEUGOONNOH5LZO/

I suppose this might be a good idea... I'd be afraid of what it might
break, while fixing the fonts packages though. But of course if it was
completely broken it would fail after that anyhow...

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: Announce: Log Detective - AI tool to analyze build logs failures

2024-01-17 Thread Jiri Kyjovsky 
Hello Tristan,

We store the data in json format. You can access and download the data directly 
at our main page at the bottom - "Download collected data". Or via 
https://log-detective.com/download

Cheers
Jiri
--
___
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

HEADSUP boost and tbb rebuilds starting in a side tag

2024-01-17 Thread Jonathan Wakely 
I'll be building boost, tbb, and the packages that depend on them in
the f40-build-side-81691
side tag over the next few hours (in advance of the mass rebuild tomorrow).

If your package gets a "Rebuilt for Boost 1.83.0" comment, please
don't rebuild it in rawhide, we're building it in the side tag and
will merge it back to rawhide. If you need to update your package
before the mass rebuild, please let me and Patrick (CC'd) know and
your changes can be built in the side tag too.

(Since there is overlap between the packages that depend on boost and
tbb I'm doing them all at once)
https://fedoraproject.org/wiki/Changes/F40Boost183
https://fedoraproject.org/wiki/Changes/F39TBB2020.3
--
___
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 2258864] New: perl-App-Cme-1.040 is available

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258864

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



Releases retrieved: 1.040
Upstream release that is considered latest: 1.040
Current version/release in rawhide: 1.039-1.fc40
URL: https://metacpan.org/dist/App-Cme/

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


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


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

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

Fedora CoreOS Community Meeting Minutes 2024-01-17

2024-01-17 Thread Jonathan Lebon 
Text Log: 
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-01-17/fedora-coreos-meeting.2024-01-17-16.29.log.txt
HTML Log: 
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-01-17/fedora-coreos-meeting.2024-01-17-16.29.log.html
Text Minutes: 
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-01-17/fedora-coreos-meeting.2024-01-17-16.29.txt
HTML Minutes: 
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-01-17/fedora-coreos-meeting.2024-01-17-16.29.html

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

Meeting started by @dustymabe:matrix.org at 2024-01-17 16:29:18



Meeting summary
---
* TOPIC: roll call (@dustymabe:matrix.org, 16:29:23)
* TOPIC: Action items from last meeting (@dustymabe:matrix.org, 16:35:27)
* TOPIC: there are no action items from the last meeting.
(@dustymabe:matrix.org, 16:35:44)
* TOPIC: Platform Request: Proxmox (@dustymabe:matrix.org, 16:35:58)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/736
(@dustymabe:matrix.org, 16:36:05)
* INFO: there is work going on that should make proxmox easier to
add FCOS support for if a motivated individual came along:
https://github.com/coreos/fedora-coreos-tracker/issues/736#issuecomment-1892669133
(@dustymabe:matrix.org, 16:51:29)
* AGREED: We will reserve the `proxmoxve` platform ID for the
proxmox platform. (@dustymabe:matrix.org, 16:54:42)
* TOPIC: Podman v5 breaking changes (@dustymabe:matrix.org, 16:56:45)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1629
(@dustymabe:matrix.org, 16:56:53)
* INFO: we are looking for a volunteer to drive the process to
help users migrate older systems to newer settings that will allow
them to adopt podman v5 without issue (@dustymabe:matrix.org,
17:04:56)
* TOPIC: Open Floor (@dustymabe:matrix.org, 17:07:43)

Meeting ended at 2024-01-17 17:13:47

Action items


People Present (lines said)
---
* @dustymabe:matrix.org (43)
* @jlebon:fedora.im (18)
* @zodbot:fedora.im (9)
* @apiaseck:matrix.org (3)
* @mnguyen:fedora.im (3)
* @jbtrystram:matrix.org (3)
* @meetbot:fedora.im (2)
* @gurssing:matrix.org (2)
* @buckaroogeek:fedora.im (2)
* @marmijo:fedora.im (2)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F40 Change Proposal: F40 Change Proposal: Unify /usr/bin and /usr/sbin (System-Wide)

2024-01-17 Thread Ben Beasley 

I attempted a quick check:

    $ repoquery -q --repo=rawhide -l -a | tee >(

        grep -E '^/usr/bin/[^/]+$' | sort -u | xargs -n 1 basename > 
bin.txt


        ) | grep -E '^/usr/sbin/[^/]+$' | sort -u | xargs -n 1 basename 
> sbin.txt


    $ wc -l bin.txt sbin.txt

     31229 bin.txt
      2998 sbin.txt
     34227 total

    $ comm -1 -2 bin.txt sbin.txt

    arping
    backintime-qt-root
    bat
    beesu
    chkrootkit
    etherape
    exabgp-healthcheck
    faxq
    gearmand
    hcidump
    hddtemp
    hunt
    ifstat
    iscsistart
    lshw-gui
    lspci
    makemap
    mate-system-log
    msktutil
    named-checkconf
    named-checkzone
    named-compilezone
    pidof
    ping
    ptdump
    rdistd
    rhino
    rpcbind
    rpcinfo
    sendfax
    sestatus
    setup
    sievec
    subscription-manager
    system-switch-java
    tmpwatch
    tracepath
    udevadm
    updatedb
    v4l-conf
    vpnc
    vpnc-disconnect

That should be a reasonably accurate list of the executables that need 
investigation, and for which the packages that provide them probably 
need some kind of modification.


On 1/7/24 10:47, Gary Buhrmaster wrote:

On Wed, Dec 20, 2023 at 7:54 PM Aoife Moloney  wrote:

Wiki -> https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin


I do not see as part of the plan a process to
go through all Fedora packages and identifying
binaries in /usr/bin that have the same name
as a binary in /usr/sbin (from the same, or
different packages) such that the packager
(or the multiple packages) will need to
coordinate the changes (perhaps by engaging
upstream).

I agree that there should be few, but
identifying impacts in advance provides
for a better decision process, and minimizes
the last minute work that packagers need
to do (they will have a longer warning and
preparation time).
--
___
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

Postponement of Mass Rebuild by One Day

2024-01-17 Thread Samyak Jain 
Hello Folks,

I hope this email finds you well. I am writing to inform you about a
slight adjustment in our schedule for the upcoming mass rebuild which
was planned to happen on Jan 17, 2024. As per the discussion in our
releng weekly call today, due to an unexpected delay in merging the
side tag covering the update for the latest GCC version, we find it
necessary to postpone the mass rebuild by one day.

The relevant FESCo ticket addressing this matter can be found at the
following link: Ticket #3145[1]. As a result of this postponement, we
will be holding off on the mass rebuild until the side tag is
successfully merged, and the Bodhi update is created. This decision is
crucial to ensure the smooth integration of the latest GCC version
into the Fedora ecosystem.

Thanks for understanding. We will keep you updated on any further
developments regarding the mass rebuild schedule.

Best regards,

Samyak Jain
Fedora Release Engineering

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

Fedora 40 Mass Rebuild will be held this week

2024-01-17 Thread Samyak Jain 
Hi all,

Per the Fedora Linux f40 schedule [1] we will be having a mass rebuild on
2024-01-17 for Fedora f40. We are running this mass rebuild for the
changes listed in:

https://pagure.io/releng/issues?status=Open=mass+rebuild=f40=changes

This mass rebuild will be done in a side tag (f40-rebuild) and merged
when completed.

The following tracker will be active on the day of the mass rebuild:

Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f40-failures.html


Things still need rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f40-need-rebuild.html


FTBFS (Fails To Build From Source) bugs will be filed after the
mass rebuild is complete.

Please be sure to let releng know if you see any bugs in the reporting.
You can contact releng in the #releng:fedoraproject.org room on Matrix,
or by dropping an email to our list [2] or filing an issue in pagure [3].

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,
Samyak Jain
Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Postponement of Mass Rebuild by One Day

2024-01-17 Thread Samyak Jain 
Hello Folks,

I hope this email finds you well. I am writing to inform you about a
slight adjustment in our schedule for the upcoming mass rebuild which
was planned to happen on Jan 17, 2024. As per the discussion in our
releng weekly call today, due to an unexpected delay in merging the
side tag covering the update for the latest GCC version, we find it
necessary to postpone the mass rebuild by one day.

The relevant FESCo ticket addressing this matter can be found at the
following link: Ticket #3145[1]. As a result of this postponement, we
will be holding off on the mass rebuild until the side tag is
successfully merged, and the Bodhi update is created. This decision is
crucial to ensure the smooth integration of the latest GCC version
into the Fedora ecosystem.

Thanks for understanding. We will keep you updated on any further
developments regarding the mass rebuild schedule.

Best regards,

Samyak Jain
Fedora Release Engineering

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

Orphaned packages looking for new maintainers

2024-01-17 Thread Maxwell G 
 Report started at 2024-01-15 15:04:52 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package  (co)maintainers   Status Change

3proxyorphan   1 weeks ago  
cdsclient @astro-sig, orphan   2 weeks ago  
cp2k  @scitech_sig, jussilehtola,  1 weeks ago  
  lecris, orphan, tomspur   
csmithorphan   2 weeks ago  
drumstick0orphan, yanqiyu  2 weeks ago  
elpa  @scitech_sig, orphan 1 weeks ago  
kf6-karchive  @kde-sig, orphan 0 weeks ago  
kf6-kplotting @kde-sig, orphan 0 weeks ago  
kf6-networkmanager-qt @kde-sig, orphan 0 weeks ago  
kf6-syntax-highlighting   @kde-sig, orphan 0 weeks ago  
kio-ftps  @kde-sig, orphan, rdieter,   0 weeks ago  
  than  
kjots @kde-sig, orphan 0 weeks ago  
kmag  @kde-sig, orphan, rdieter,   0 weeks ago  
  than  
kmetronomeorphan   2 weeks ago  
koko  @kde-sig, orphan 0 weeks ago  
kongress  @kde-sig, orphan,0 weeks ago  
  thunderbirdtr 
kpipewire5@kde-sig, orphan 0 weeks ago  
libASLorion, orphan, slaanesh  4 weeks ago  
mygnuhealth   orphan   2 weeks ago  
obs-service-cargo_vendor  orphan   4 weeks ago  
php-PHP-CSS-Parserorphan   1 weeks ago  
python-GridDataFormats@scitech_sig, orphan 1 weeks ago  
python-Pymplerorphan   1 weeks ago  
python-colorspacious  orphan   1 weeks ago  
python-compressed-rtf orphan   2 weeks ago  
python-google-cloud-access-   @python-packagers-sig, fkolwa,   4 weeks ago  
approval  miyunari, orphan  
python-google-cloud-access-   @python-packagers-sig, fkolwa,   4 weeks ago  
context-manager   miyunari, orphan  
python-google-cloud-api-gateway   @python-packagers-sig, fkolwa,   4 weeks ago  
  miyunari, orphan  
python-google-cloud-apigee-   @python-packagers-sig, fkolwa,   4 weeks ago  
connect   miyunari, orphan  
python-google-cloud-appengine-@python-packagers-sig, fkolwa,   4 weeks ago  
admin miyunari, orphan  
python-google-cloud-asset @python-packagers-sig, fkolwa,   4 weeks ago  
  miyunari, orphan  
python-google-cloud-automl@python-packagers-sig, fkolwa,   4 weeks ago  
  miyunari, orphan  
python-google-cloud-bigquery  @python-packagers-sig, fkolwa,   4 weeks ago  
  miyunari, orphan  
python-google-cloud-bigquery- @python-packagers-sig, fkolwa,   4 weeks ago  
connectionmiyunari, orphan

Fedora 40 Mass Rebuild will be held this week

2024-01-17 Thread Samyak Jain 
Hi all,

Per the Fedora Linux f40 schedule [1] we will be having a mass rebuild on
2024-01-17 for Fedora f40. We are running this mass rebuild for the
changes listed in:

https://pagure.io/releng/issues?status=Open=mass+rebuild=f40=changes

This mass rebuild will be done in a side tag (f40-rebuild) and merged
when completed.

The following tracker will be active on the day of the mass rebuild:

Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f40-failures.html


Things still need rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f40-need-rebuild.html


FTBFS (Fails To Build From Source) bugs will be filed after the
mass rebuild is complete.

Please be sure to let releng know if you see any bugs in the reporting.
You can contact releng in the #releng:fedoraproject.org room on Matrix,
or by dropping an email to our list [2] or filing an issue in pagure [3].

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,
Samyak Jain
Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/
--
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Announce: Log Detective - AI tool to analyze build logs failures

2024-01-17 Thread Tristan Cacqueray 

On Wed, Jan 17, 2024 at 12:34 Jiri Kyjovsky wrote:
> Hey, Fedora devs!
>
> Ever find yourself lost in the labyrinth of build logs, desperately seeking
> the elusive culprit behind a failed build? Enter Log Detective – your
> future personal AI guru dedicated to unravelling the mysteries of build log
> failures within the RPM community.
>
> *What is Log Detective?*
>
> Log Detective will be an AI tool for analyzing failed build logs in the RPM
> community. We are currently in the early stage of development and plan to
> train the AI using real-world data from maintainers, creating a specialized
> model for error identification. Thus we created a data collection portal
> [1], where you can contribute your failed build logs.
>
> *Why Log Detective?*
>
> Diving into build logs feels like navigating a jungle of thousands of
> lines. When a build fails, spotting the glitch easily turns into a
> head-scratcher even for pros. "ERROR" in logs doesn't guarantee always a
> quick fix, and these errors don't reveal themselves at the log's end.
> Untangling this requires a keen understanding of packaging difficulties.
>
> *Help us shape the future of Log Detective!*
>
> We're reaching out to developers like you to contribute by uploading your
> recent failed build logs on our website [1] and explaining why the build
> failed. Your input is crucial in building the dataset that will train Log
> Detective's AI model. By participating, you're playing a key role in
> creating a tool to streamline error resolution for the entire RPM
> community. Join us in making Fedora even more powerful!
>
> *How to contribute data to Log Detective data collection website?*
>
> Visit log-detective.com [1] and share your recent failed build. We can
> fetch the logs from build systems like Copr [2], Koji [3], services like
> Packit [4] or arbitrary URL. Highlight the lines in the log associated with
> the failure and describe how it can be fixed. The more detailed, the
> merrier for our final tool, and the more hints for you and other developers
> when your build fails in future.
>
> *Join the Log Detective!*
>
> Drop by our GitHub repository [5] to share your ideas. Let's collaborate to
> build a tool that changes the game for handling build log failures.
>
> Log Detective isn't just a tool, it's your AI sidekick for defeating build
> log challenges. Be part of the revolution!
>
> Cheers,
> The Log Detective Crew
>
> [1] - https://log-detective.com/
> [2] - https://copr.fedorainfracloud.org/
> [3] - https://koji.fedoraproject.org/
> [4] - https://packit.dev/
> [5] - https://github.com/fedora-copr/log-detective-website

Hello,

I'm building a similar project named logjuicer using the
following dataset for evaluation:
  https://github.com/logjuicer/logjuicer-tests

How do you store the collected data and is there a schema/library to
access it?

Cheers,
-Tristan


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

2024-01-17 Thread Vít Ondruch 


Dne 17. 01. 24 v 12:45 Priscila Gutierres napsal(a):

Hello James,

I started some months ago as a maintainer and I have been learning 
since then.
One important thing I've learned is to ask if  "this package should be 
kept or should it be retired?"



Good hint is typically in dist-git Pagure, e.g. look left at here:

https://src.fedoraproject.org/rpms/rubygem-rails-deprecated_sanitizer

These days, I am not sure if orphaned packages are the right start. They 
could be, but generally, it is good to start with package which is close 
to your heart, something you use.



Vít


If you want to start to contribute, you can send PRs bumping or fixing 
opened bugs first, and I can

help with that.

Priscila.


On Wed, Jan 17, 2024 at 8:32 AM James Richardson  
wrote:


Hi All,

I am not sponsored into the packager group yet, but I would like
to begin by maintaining a package that is on this list as
"orphaned" however, it is very difficult to understand which
package(s) might be suitable for a newcomer like me. Any help,
advice, or suggested package would be greatly appreciated. After
completing the sponsoring process, I would be able to maintain
that package, or co-maintain if needed.

Sincerely,

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

[Bug 2258808] New: perl-Sys-Virt-10.0.0 is available

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258808

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



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

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3355/


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


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

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

[rpms/perl-libwww-perl] PR #52: 6.73 bump

2024-01-17 Thread Michal Josef Špaček 

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

Merged pull-request:

``
6.73 bump
``

https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/52
--
___
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-libwww-perl] PR #52: 6.73 bump

2024-01-17 Thread Michal Josef Špaček 

mspacek opened a new pull-request against the project: `perl-libwww-perl` that 
you are following:
``
6.73 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/52
--
___
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 2258753] perl-5.38.2-503.fc40 FTBFS: constants.h:580:20: error: ‘F’ undeclared

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258753

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |RAWHIDE
   Fixed In Version||perl-5.38.2-504.fc40
Last Closed||2024-01-17 13:14:03




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2258753
--
___
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 2258753] perl-5.38.2-503.fc40 FTBFS: constants.h:580:20: error: ‘F’ undeclared

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258753

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #2 from Jitka Plesnikova  ---
There were PR for perl and it fixed the build.
https://src.fedoraproject.org/rpms/perl/pull-request/11

The dual-life package perl-Compress-Raw-Zlib already fixed.


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

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

[rpms/perl] PR #11: Update Compress::Raw::Zlib for improved compatibility with zlib-ng

2024-01-17 Thread Jitka Plesnikova 

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

Merged pull-request:

``
Update Compress::Raw::Zlib for improved compatibility with zlib-ng
``

https://src.fedoraproject.org/rpms/perl/pull-request/11
--
___
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

Orphaning rubygem-rubygems-mirror

2024-01-17 Thread Pavel Valena 
Hello,

I'm orphaning $SUBJ as I have no longer use for it:

https://src.fedoraproject.org/rpms/rubygem-rubygems-mirror

(Also it fails to build with Ruby 3.3.)

Regards,
Pavel
--
___
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-distro-aliases - The easiest way to get numbers of active Fedora releases

2024-01-17 Thread Barry Scott 


> On 17 Jan 2024, at 10:57, Jakub Kadlcik  wrote:
> 
> Hello,
> I just wanted to quickly announce a small project I did in collaboration with 
> the Packit folks.
> 
> Do you have some tools or services that perform actions on all currently 
> active Fedora releases? And do you have to manually update their list every 
> time a new Fedora release is branched or EOLed? The fedora-distro-aliases 
> will make your life easier.
> 
> https://github.com/rpm-software-management/fedora-distro-aliases
> 
> It defines aliases such as `fedora-stable`, `epel-all`, `fedora-latest`, etc. 
> To evaluate them, it queries Bodhi, so they are always up-to-date (but the 
> tradeoff is that it requires an internet connection). There are multiple 
> examples in the project README but the usage is simple, e.g.:
> 
> >>> from fedora_distro_aliases import get_distro_aliases
> >>> aliases = get_distro_aliases()
> >>> [x.namever for x in aliases["fedora-all"]]
> ['fedora-38', 'fedora-39', 'fedora-rawhide']

Yes I have tools I update the list of fedora releases in.
Thanks for this tool!

Now I'm off to update my tools to use this.

> 
> The package is already in Fedora, give it a shot,

And its called python3-fedora-distro-aliases

Barry

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

[rpms/perl-libwww-perl] PR #51: 6.73 bump

2024-01-17 Thread Michal Josef Špaček 

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

Merged pull-request:

``
6.73 bump
``

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

Re: Orphaned packages looking for new maintainers

2024-01-17 Thread Priscila Gutierres 
Hello James,

I started some months ago as a maintainer and I have been learning since
then.
One important thing I've learned is to ask if  "this package should be kept
or should it be retired?"
If you want to start to contribute, you can send PRs bumping or fixing
opened bugs first, and I can
help with that.

Priscila.


On Wed, Jan 17, 2024 at 8:32 AM James Richardson 
wrote:

> Hi All,
>
> I am not sponsored into the packager group yet, but I would like to begin
> by maintaining a package that is on this list as "orphaned" however, it is
> very difficult to understand which package(s) might be suitable for a
> newcomer like me. Any help, advice, or suggested package would be greatly
> appreciated. After completing the sponsoring process, I would be able to
> maintain that package, or co-maintain if needed.
>
> Sincerely,
>
> James
> --
> ___
> 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

Announce: Log Detective - AI tool to analyze build logs failures

2024-01-17 Thread Jiri Kyjovsky 
Hey, Fedora devs!

Ever find yourself lost in the labyrinth of build logs, desperately seeking
the elusive culprit behind a failed build? Enter Log Detective – your
future personal AI guru dedicated to unravelling the mysteries of build log
failures within the RPM community.

*What is Log Detective?*

Log Detective will be an AI tool for analyzing failed build logs in the RPM
community. We are currently in the early stage of development and plan to
train the AI using real-world data from maintainers, creating a specialized
model for error identification. Thus we created a data collection portal
[1], where you can contribute your failed build logs.

*Why Log Detective?*

Diving into build logs feels like navigating a jungle of thousands of
lines. When a build fails, spotting the glitch easily turns into a
head-scratcher even for pros. "ERROR" in logs doesn't guarantee always a
quick fix, and these errors don't reveal themselves at the log's end.
Untangling this requires a keen understanding of packaging difficulties.

*Help us shape the future of Log Detective!*

We're reaching out to developers like you to contribute by uploading your
recent failed build logs on our website [1] and explaining why the build
failed. Your input is crucial in building the dataset that will train Log
Detective's AI model. By participating, you're playing a key role in
creating a tool to streamline error resolution for the entire RPM
community. Join us in making Fedora even more powerful!

*How to contribute data to Log Detective data collection website?*

Visit log-detective.com [1] and share your recent failed build. We can
fetch the logs from build systems like Copr [2], Koji [3], services like
Packit [4] or arbitrary URL. Highlight the lines in the log associated with
the failure and describe how it can be fixed. The more detailed, the
merrier for our final tool, and the more hints for you and other developers
when your build fails in future.

*Join the Log Detective!*

Drop by our GitHub repository [5] to share your ideas. Let's collaborate to
build a tool that changes the game for handling build log failures.

Log Detective isn't just a tool, it's your AI sidekick for defeating build
log challenges. Be part of the revolution!

Cheers,
The Log Detective Crew

[1] - https://log-detective.com/
[2] - https://copr.fedorainfracloud.org/
[3] - https://koji.fedoraproject.org/
[4] - https://packit.dev/
[5] - https://github.com/fedora-copr/log-detective-website
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2024-01-17 Thread James Richardson 
Hi All,

I am not sponsored into the packager group yet, but I would like to begin by 
maintaining a package that is on this list as "orphaned" however, it is very 
difficult to understand which package(s) might be suitable for a newcomer like 
me. Any help, advice, or suggested package would be greatly appreciated. After 
completing the sponsoring process, I would be able to maintain that package, or 
co-maintain if needed.

Sincerely,

James
--
___
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-libwww-perl] PR #51: 6.73 bump

2024-01-17 Thread Michal Josef Špaček 

mspacek opened a new pull-request against the project: `perl-libwww-perl` that 
you are following:
``
6.73 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/51
--
___
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 2258287] perl-libwww-perl-6.73 is available

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258287

Michal Josef Spacek  changed:

   What|Removed |Added

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



--- Comment #1 from Michal Josef Spacek  ---
Changes:
6.73  2024-01-13 20:19:09Z
- Fix no_proxy subdomain matching (GH#447) (Axel Burri)

For F39 and rawhide


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

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

Re: dnsmasq default configuration changed

2024-01-17 Thread Petr Menšík 

Thanks, that is exactly the message I wanted to tell.

Perhaps I should keep corner cases to myself until someone actually hits 
them. It has clearly confused people and created unnecessary reactions. 
Conflict will arise only when configuration change done by administrator 
were not complete.


On 16. 01. 24 10:18, Miroslav Lichvar wrote:

On Mon, Jan 15, 2024 at 05:31:36PM +0100, Kevin Kofler via devel wrote:

Petr Menšík wrote:

Anyway, dnsmasq will listen by default on 127.0.0.1, as every standard
resolver does. You can use listen-address=127.0.0.53 if you like, but
then it will conflict with systemd-resolved.

You just wrote that you make it listen by default on all interfaces, and
then filter.

If I understand it correctly, it will do that only if the
configuration was modified (an additional interface was specified).
The default configuration should work exactly as before.


This means it will conflict over the port 53.

They bind to different addresses by default.


--
Petr Menšík
Software Engineer, RHEL
Red Hat, http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
--
___
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: dnsmasq default configuration changed

2024-01-17 Thread Petr Menšík 
Please, Stephen, would you please read what I wrote, not what Kevin 
wrongly deducted?


The change I made in dnsmasq does not conflict with systemd-resolved in 
default configuration or if configured correctly. I have wrote scenario, 
when it can conflict and how to fix it. So no, there is no need to 
revert my change. If it is, *PLEASE* report it with exact step to 
reproduce. I have tested those changes do not cause regressions. If you 
(or anyone else) know something I have missed, I need much more precise 
steps than those below to fix it.


I would suggest everyone to try that change in rawhide actually, verify 
what is listening on and whether it does conflict with anything. I use 
"lsof -np $(pidof dnsmasq)" command for quick checks.


On 15. 01. 24 20:04, Stephen Gallagher wrote:

On Mon, Jan 15, 2024 at 11:32 AM Kevin Kofler via devel
  wrote:

Petr Menšík wrote:

systemd-resolved is unfortunately known to broken.

[snip]

Dnsmasq does not break DNSSEC, systemd-resolved does.

[snip]

Unfortunately broken are clients having systemd-resolved enabled.

How exactly is it broken? If you refer to:
https://github.com/systemd/systemd/issues/25676
fixes for that are finally coming in now (as of 3 weeks ago).


I have reported issues known to me:

https://github.com/systemd/systemd/issues?q=is%3Aopen+is%3Aissue+author%3Apemensik+label%3Aresolve+

https://bugzilla.redhat.com/buglist.cgi?quicksearch=reporter%3Apemensik%40redhat.com%20component%3Asystemd_id=13235040

There are some others, which I consider important enough. If it works 
for you, good for you. It does not work well for others, I do not want 
to discuss it here. This thread is about dnsmasq only and I would like 
to focus to that only.





I would recommend having systemd-resolved forwarded to dnsmasq, which can
then be forwarded further.

If you think dnsmasq should replace systemd-resolved by default, then please
propose that through the Changes process, which will also ensure the glibc
resolver, NetworkManager, and the like get configured properly for it.
Simply shipping dnsmasq with a default configuration that conflicts with
systemd-resolved is not a productive approach.

If systemd-resolved is really broken, then it either needs to be fixed or
replaced. The former needs to be handled through systemd upstream, the
latter through the Fedora Changes process.
Yes, I plan to propose changes to default system wide resolver, because 
long reported bugs to systemd-resolved were mostly ignored. For years. 
But the solution I want to propose is not replacing it with dnsmasq. I 
am dnsmasq maintainer, I know it has own issues. In my opinion it is 
less broken, but not perfect. We are preparing different solution, which 
should be better. But it is not yet ready and therefore there is no 
Fedora Change filled. We fill create that once we are sure it brings 
features without causing regressions.



But this change should create conflict with systemd-resolved only in case
it was improperly configured.

But the default configuration you ship will conflict.


Anyway, dnsmasq will listen by default on 127.0.0.1,
  as every standard
resolver does. You can use listen-address=127.0.0.53 if you like, but
then it will conflict with systemd-resolved.

You just wrote that you make it listen by default on all interfaces, and
then filter. This means it will conflict over the port 53. That said,
listening on the lo interface only will also conflict with systemd-resolved
or any other local resolver, so you are probably right that your change does
not change much for the default configuration, it just makes it harder (more
settings to change) to set up coexistence. 127.0.0.53 is unfortunately not
an independent interface, it is still the lo interface.


Based on my reading of this thread, this change is going to break the
default configuration and needs to be reverted immediately. Petr,
please file a Change Proposal for Fedora *41*. You have missed the
deadline for F40 System-Wide Changes (Dec. 26th) and this is
absolutely NOT a self-contained Change.


I am sorry my intention were not understood correctly. Miroslav already 
mentioned that.We will fill System-Wide Change, but this change does not 
need it. If it breaks something, please use bug #2258062 to report 
details or create a new one for rawhide. But reproducible details are 
needed, not just assumptions.


Cheers,

Petr

PS: I consider it rude to be commented on issue closed for discussion, 
especially if the comment is misleading and false.


--
Petr Menšík
Software Engineer, RHEL
Red Hat,http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
--
___
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:

fedora-distro-aliases - The easiest way to get numbers of active Fedora releases

2024-01-17 Thread Jakub Kadlcik 
Hello,
I just wanted to quickly announce a small project I did in collaboration
with the Packit folks.

Do you have some tools or services that perform actions on all currently
active Fedora releases? And do you have to manually update their list every
time a new Fedora release is branched or EOLed? The fedora-distro-aliases
will make your life easier.

https://github.com/rpm-software-management/fedora-distro-aliases

It defines aliases such as `fedora-stable`, `epel-all`, `fedora-latest`,
etc. To evaluate them, it queries Bodhi, so they are always up-to-date (but
the tradeoff is that it requires an internet connection). There are
multiple examples in the project README but the usage is simple, e.g.:

>>> from fedora_distro_aliases import get_distro_aliases
>>> aliases = get_distro_aliases()
>>> [x.namever for x in aliases["fedora-all"]]
['fedora-38', 'fedora-39', 'fedora-rawhide']

The package is already in Fedora, give it a shot,
Jakub
--
___
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 2258753] perl-5.38.2-503.fc40 FTBFS: constants.h:580:20: error: ‘F’ undeclared

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258753



--- Comment #1 from Petr Pisar  ---
This is an issue in bundled Compress-Raw-Zlib, fixed probably with their
upstream patch:

commit 0a8fb7141a43b8e49609fb06f05fad5150a97c2a
Author: pmqs 
Date:   Fri Jun 9 14:30:36 2023 +0100

Change storage of ZLIBNG_VER_STATUS from IV to PV
https://github.com/pmqs/Compress-Raw-Zlib/issues/24


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

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

[Bug 2258753] perl-5.38.2-503.fc40 FTBFS: constants.h:580:20: error: ‘F’ undeclared

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258753

Petr Pisar  changed:

   What|Removed |Added

Link ID||Github
   ||pmqs/Compress-Raw-Zlib/issu
   ||es/24 Github
   ||Perl/perl5/issues/21238




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2258753
--
___
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 2258753] New: perl-5.38.2-503.fc40 FTBFS: constants.h:580:20: error: ‘F’ undeclared

2024-01-17 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=2258753

Bug ID: 2258753
   Summary: perl-5.38.2-503.fc40 FTBFS: constants.h:580:20: error:
‘F’ undeclared
   Product: Fedora
   Version: rawhide
   URL: https://koschei.fedoraproject.org/package/perl
Status: NEW
 Component: perl
  Assignee: jples...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com, ka...@ucw.cz,
mmasl...@redhat.com, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com,
psab...@redhat.com, rhug...@redhat.com,
spo...@gmail.com
Blocks: 2231791 (F40FTBFS,RAWHIDEFTBFS)
  Target Milestone: ---
Classification: Fedora



perl-5.38.2-503.fc40 fails to build in Fedora 40:

gcc -c  -I/usr/include -D_REENTRANT -D_GNU_SOURCE -O2 -flto=auto
-ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall
-Wno-complain-wrong-lang -Werror=format-security
-Werror=implicit-function-declaration -Werror=implicit-int
-Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fwrapv
-fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -Werror=pointer-arith -Werror=vla -Wextra -Wno-long-long
-Wno-declaration-after-statement -Wc++-compat -Wwrite-strings
-Wno-use-after-free -g   -DVERSION=\"2.204_001\" -DXS_VERSION=\"2.204_001\"
-fPIC "-I../.."  -DNO_VIZ  -DGZIP_OS_CODE=3  -DPerl_crz_BUILD_ZLIB=0 Zlib.c
[...]
In file included from Zlib.xs:37:
constants.h: In function ‘constant’:
constants.h:580:20: error: ‘F’ undeclared (first use in this function); did you
mean ‘OF’?
  580 |   *iv_return = ZLIBNG_VER_STATUS;
  |^
constants.h:580:20: note: each undeclared identifier is reported only once for
each function it appears in
make[1]: Leaving directory
'/builddir/build/BUILD/perl-5.38.2/cpan/Compress-Raw-Zlib'
make[1]: *** [Makefile:349: Zlib.o] Error 1

A difference between passing and failing build root is at
. This is probably triggered
by upgrading from zlib-devel-1.2.13-5.fc40 to
zlib-ng-compat-devel-2.1.3-7.fc40.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2231791
[Bug 2231791] Fedora 40 FTBFS Tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2258753

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

Re: Build error with GCC 14, not even a warning in GCC 13

2024-01-17 Thread Aleksei Bavshin 

On 1/16/24 15:54, Tom Hughes via devel wrote:

On 16/01/2024 23:49, Richard Shaw wrote:
On Tue, Jan 16, 2024 at 5:36 PM Aleksei Bavshin 
mailto:aleba...@fedoraproject.org>> wrote:


    Ah, I misread the include path. It's our package that is too old :(
    https://src.fedoraproject.org/rpms/rapidjson/pull-request/4
     should
    help.

It doesn't look like the pull request has gotten any attention. 
Perhaps it's time to initiate the non-responsive maintainer process?


Right because the other two PRs I've merged in the last couple of
weeks, including one today, are not evidence of responsiveness?

That PR is on my to look at list but rather obviously it needs
more work than the other ones.

I'm not really keen on packaging a random git snapshot because
there's no way to know how good or bad it is but I realise that
due to upstream being a pain it may be necessary here.


For a conservative approach, cherry-picking 3b2441b, 862c39b, 24ebd51, 
64faab2, a98e999 seems to be enough. The first 2 commits take care of 
the issue from this thread, and the remaining 3 are needed to support 
using rapidjson from projects with -std=c++20.




Tom





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