Re: Login issues to lists.* and src.*? Any outages?
On 2/26/24 12:13, Michal Konecny wrote: On 24. 02. 24 12:30, Richard W.M. Jones wrote: ... So I sometimes have issues logging in. For example it happened about 5 minutes ago, but the error isn't very interesting: Original URL:https://id.fedoraproject.org/login/gssapi/negotiate?ipsilon_transaction_id=8d11a868-b8f5-4e65-b48b-a53f592d2cfb Redirected URL:https://id.fedoraproject.org/login/pam Gateway Timeout The gateway did not receive a timely response from the upstream server or application. Is it useful to report these? Sometimes just retrying works, as in fact happened when I retried it this time. Rich. It's usually good to wait for some time and try again. If the issue persists you can open ticket on https://pagure.io/fedora-infrastructure/issues Speaking of the devil, I just started getting 500s when trying to log in, so I filed https://pagure.io/fedora-infrastructure/issue/11793. Michal ... -- ___ 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 -- ___ 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
Copr builds are stuck at package signing
Hey, Thanks to Packit I noticed that a lot of our jobs are running longer than usual, and a quick glance at the Copr task queue[0] tells me there's something fishy going on. I opened a couple of jobs[1][2][3] and all of them seem to be stuck in the same step - signing the build RPMs: builder-live.log: RPMResults finished backend.log: [2023-12-05 16:22:41,769][ INFO][PID:2234386] Calling '/bin/sign -u rpmsoftwaremanagement#ci-libdnf5-pr1...@copr.fedorahosted.org -p' (attempt #2) [2023-12-05 16:22:43,127][WARNING][PID:2234386] Command '/bin/sign -u rpmsoftwaremanagement#ci-libdnf5-pr1...@copr.fedorahosted.org -p' failed with: unknown key: rpmsoftwaremanagement#ci-libdnf5-pr1...@copr.fedorahosted.org [2023-12-05 16:22:43,129][WARNING][PID:2234386] Going to sleep 20s and re-try. [2023-12-05 16:23:03,130][ INFO][PID:2234386] Calling '/bin/sign -u rpmsoftwaremanagement#ci-libdnf5-pr1...@copr.fedorahosted.org -p' (attempt #3) [2023-12-05 16:23:04,949][WARNING][PID:2234386] Command '/bin/sign -u rpmsoftwaremanagement#ci-libdnf5-pr1...@copr.fedorahosted.org -p' failed with: unknown key: rpmsoftwaremanagement#ci-libdnf5-pr1...@copr.fedorahosted.org [2023-12-05 16:23:04,950][WARNING][PID:2234386] Going to sleep 20s and re-try. Looks like the last 20s sleep takes _way_ longer than 20s. Is this a known issue? [0] https://copr.fedorainfracloud.org/status/running/ [1] https://copr.fedorainfracloud.org/coprs/packit/cockpit-project-cockpit-19698/build/6726609/ [2] https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/CI-libdnf5-pr1008/build/6726763/ [3] https://copr.fedorainfracloud.org/coprs/eliasofwaffle/gnome-shell-patched/build/6727378/ -- ___ 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: Getting package NEVR list from core dump ?
Hey
On 10/13/23 09:41, Daniel P. Berrangé wrote:
Not too long ago Fedora added a new ELF note with the NEVR information for
a package, to all shared libraries
https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects
For cores dumped by processes on my local system, coredumpctl extracts the
package info which is great.
Along with the ELF notes, systemd-analyze gained a new verb - inspect-elf -
that can be used to retrieve them:
$ systemd-analyze inspect-elf
core.varlinkctl.1000.89df21ab140948a591f91ecc084568f8.2677628.169711649200
path:
/home/mrc0mmand/tmp/core.varlinkctl.1000.89df21ab140948a591f91ecc084568f8.2677628.169711649200
elfType: coredump
elfArchitecture: AMD x86-64
module name: libnl-3.so.200
type: rpm
name: libnl3
version: 3.7.0-3.fc38
architecture: x86_64
osCpe: cpe:/o:fedoraproject:fedora:38
buildId: c9b97577bfc2cc4651143f597ded2b3e1bd2
...
Also in JSON:
$ systemd-analyze inspect-elf --json=pretty
core.varlinkctl.1000.89df21ab140948a591f91ecc084568f8.2677628.169711649200
{
"elfType" : "coredump",
"elfArchitecture" : "AMD x86-64",
"libnl-3.so.200" : {
"type" : "rpm",
"name" : "libnl3",
"version" : "3.7.0-3.fc38",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:38",
"buildId" : "c9b97577bfc2cc4651143f597ded2b3e1bd2"
},
"libnl-route-3.so.200" : {
"type" : "rpm",
"name" : "libnl3",
"version" : "3.7.0-3.fc38",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:38",
"buildId" : "e71fe7f76f1c4bff5d935f0d19c5498c8505c61a"
},
...
Lets say, however, that I receive a coredump from an end user, and thus it
isn't known to coredumpctl.
What's the "right" way to extract the NEVR list from a standalone core
dump ?
Presumably there's a better way than just running 'strings' over the binary...
$ strings core | grep osCpe:
{"type":"rpm","name":"qemu","version":"7.2.6-1.fc38","architecture":"x86_64","osCpe":"cpe:/o:fedoraproject:fedora:38"}
{"type":"rpm","name":"librsvg2","version":"2.56.3-1.fc38","architecture":"x86_64","osCpe":"cpe:/o:fedoraproject:fedora:38"}
{"type":"rpm","name":"libogg","version":"1.3.5-5.fc38","architecture":"x86_64","osCpe":"cpe:/o:fedoraproject:fedora:38"}
..snip...
{"type":"rpm","name":"pixman","version":"0.42.2-1.fc38","architecture":"x86_64","osCpe":"cpe:/o:fedoraproject:fedora:38"}
{"type":"rpm","name":"libXau","version":"1.0.11-2.fc38","architecture":"x86_64","osCpe":"cpe:/o:fedoraproject:fedora:38"}
{"type":"rpm","name":"qemu","version":"7.2.6-1.fc38","architecture":"x86_64","osCpe":"cpe:/o:fedoraproject:fedora:38"}
With regards,
Daniel
___
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: KDE Plasma 6 (System Wide)
On 9/13/23 21:50, Sérgio Basto wrote: On Wed, 2023-09-13 at 19:52 +0200, Kevin Kofler via devel wrote: For Fedora Linux, the transition to KDE Plasma 6 will also include dropping support for the X11 session entirely, leaving only Plasma Wayland as the sole offered desktop mode. Huh?! Why?! KDE upstream is still supporting X11 in Plasma 6. I see no reason to force Wayland upon all users. I do not want Wayland on my desktop (it is already enough of a pain that it is forced upon us by Plasma Mobile on the PinePhone) and I will have to switch to another distribution and orphan all my packages if this happens. +1 , I still not use wayland , it just crash all the time , smplayer and I think many other apps simple doesn't work with wayland. other packages we cann see Exec=env QT_QPA_PLATFORM=xcb /usr/bin/foo [1]. Also packages based on vnc , libvnc, x11vnc I think doesn't support wayland, xpra also I think that still doesn't work with wayland. I don't see why we want move to wayland if X11 works very well . I second this as well. I tried to use Wayland with Plasma, but there's a weird issue where with a multi-monitor setup, switching focus from a window on the first monitor to a running Firefox on the second one would cause random clicks in Firefox that would switch tabs/click on links on the current page, which was driving me insane. Unfortunately, I still haven't got around to properly debug that and use X11 instead. ___ 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: libtommath minor soname bump
On 9/7/23 11:40, Dominik 'Rathann' Mierzejewski wrote: On Thursday, 07 September 2023 at 11:13, František Šumšal wrote: Hello, I plan to bump libtommath to 1.2.1 in Rawhide, which bumps the respective shared library to libtommath.so.1.2.1. According to repoquery all dependencies depend only on libtommath.1, so no rebuild should be necessary: $ dnf repoquery --releasever rawhide --whatrequires 'libtommath.so.*' Last metadata expiration check: 0:20:29 ago on Thu Sep 7 10:34:05 2023. dropbear-0:2022.82-3.fc39.x86_64 firebird-0:4.0.3.2975-1.fc39.x86_64 libfbclient2-0:4.0.3.2975-1.fc39.i686 libfbclient2-0:4.0.3.2975-1.fc39.x86_64 libtomcrypt-0:1.18.2-17.fc39.i686 libtomcrypt-0:1.18.2-17.fc39.x86_64 libtommath-devel-0:1.2.0-13.fc40.i686 libtommath-devel-0:1.2.0-13.fc40.x86_64 moarvm-0:2023.06-1.fc39.i686 moarvm-0:2023.06-1.fc39.x86_64 $ dnf repoquery --releasever rawhide --whatrequires 'libtommath.so.1.*' Last metadata expiration check: 0:21:06 ago on Thu Sep 7 10:34:05 2023. <...no results...> Please correct me if I'm missing something. Your first step should be checking for any ABI changes using abipkgdiff and rpmsodiff. Only if there are removed symbols do you need to worry about rebuilding consumers. However, added unversioned symbols do mean that backwards compatibility is not preserved (i.e. an application built against a newer version, say 1.2.1, might not work with 1.2.0 installed if it depends on a symbol introduced in 1.2.1). Thanks for the pointers, much appreciated! Both abipkgdiff and rpmsodiff seem to be happy, i.e. there were no added/changed/removed symbols between 1.2.0 and 1.2.1, so the bump should be safe. Cheers, Frantisek ___ 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
libtommath minor soname bump
Hello, I plan to bump libtommath to 1.2.1 in Rawhide, which bumps the respective shared library to libtommath.so.1.2.1. According to repoquery all dependencies depend only on libtommath.1, so no rebuild should be necessary: $ dnf repoquery --releasever rawhide --whatrequires 'libtommath.so.*' Last metadata expiration check: 0:20:29 ago on Thu Sep 7 10:34:05 2023. dropbear-0:2022.82-3.fc39.x86_64 firebird-0:4.0.3.2975-1.fc39.x86_64 libfbclient2-0:4.0.3.2975-1.fc39.i686 libfbclient2-0:4.0.3.2975-1.fc39.x86_64 libtomcrypt-0:1.18.2-17.fc39.i686 libtomcrypt-0:1.18.2-17.fc39.x86_64 libtommath-devel-0:1.2.0-13.fc40.i686 libtommath-devel-0:1.2.0-13.fc40.x86_64 moarvm-0:2023.06-1.fc39.i686 moarvm-0:2023.06-1.fc39.x86_64 $ dnf repoquery --releasever rawhide --whatrequires 'libtommath.so.1.*' Last metadata expiration check: 0:21:06 ago on Thu Sep 7 10:34:05 2023. <...no results...> Please correct me if I'm missing something. Cheers, Frantisek ___ 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
On 9/6/23 09:02, Christiano Anderson wrote:
--- Original Message ---
On Tuesday, September 5th, 2023 at 13:54, Miro Hrončok
wrote:
I got an error while running fedpkg update
Could not execute update: Could not generate update request: {"status": "error", "errors": [{"location": "body", "name": "builds", "description":
"Update for python-iowait-0.2-25.fc40 already exists"}, {"location": "body", "name": "builds", "description": "Invalid tag: python-iowait-0.2-25.fc40 not tagged
with any of the following tags ['epel9-next-testing-candidate', 'epel7-testing-candidate', 'eln-updates-candidate', 'epel8-testing-candidate', 'epel9-testing-candidate', 'epel8-next-testing-candidate',
'f40-container-updates-candidate', 'f37-modular-updates-candidate', 'f38-modular-updates-candidate', 'f39-container-updates-candidate', 'f38-flatpak-updates-candidate', 'f40-updates-candidate', 'f37-updates-candidate',
'f37-container-updates-candidate', 'f37-flatpak-updates-candidate', 'f38-updates-candidate', 'f38-container-updates-candidate', 'f39-flatpak-updates-candidate', 'f39-updates-candidate', 'f38-build-side-72874',
'f39-build-side-72708', 'f39-build-side-72878', 'f38-build-side-72953', 'epel9-build-side-72957', 'f38-build-side-72973', 'f40-build-side-72979', 'f38-build-side-72997', 'f39-build-side-73035', 'f40-build-side-73053',
'f39-build-side-73063', 'f40-build-side-73083', 'f37-build-side-73089', 'f38-build-side-73087', 'f40-build-side-73039', 'f40-build-side-73113', 'f39-build-side-73125', 'f39-build-side-73127', 'f39-build-side-73145',
'f38-build-side-73167']"}]}
A copy of the filled in template is saved as bodhi.template.last
Could you please tell me what's wrong here?
Updates for Rawhide are created automagically after a successful build, so the
update already exists [0], no need to create it manually. You'll need to do
that only for F39.
[0] https://bodhi.fedoraproject.org/updates/FEDORA-2023-dc1dca2af6
___
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
On 9/4/23 17:10, Miro Hrončok wrote: botan2 orphan, thm 0 weeks ago It currently both FTI and FTBFS, but the latter one seems to be easily fixable with a patch already committed to the upstream, which in turn fixes the FTI. I'll prep the builds. -- PGP Key ID: 0xFB738CE27B634E4B ___ 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: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
On 7/8/23 19:48, Dominik 'Rathann' Mierzejewski wrote: On Saturday, 08 July 2023 at 19:39, Kevin Fenzi wrote: On Sat, Jul 08, 2023 at 01:06:01PM +0200, Vitaly Zaitsev via devel wrote: On 06/07/2023 18:10, Aoife Moloney wrote: but the conversation about each change will take place on Fedora Discussion at ... 97 posts were merged into an existing topic: Opt-in / Opt-Out? A breakout topic for the F40 Change Request on Privacy-preserving telemetry for Fedora Workstation and the link leads to: https://discussion.fedoraproject.org/t/opt-in-opt-out-a-breakout-topic-for-the-f40-change-request-on-privacy-preserving-telemetry-for-fedora-workstation/85393 Which, when I visit it, says "This page does not exist or is private". If that's how it's supposed to work then I'll stay on the mailing list, thank you very much. I don't think this is a result of the "evil Red Hat", more like a result of the particular post being moved back and forth, so the link became invalid. If you strip the post ID from the link, it'll work: https://discussion.fedoraproject.org/t/opt-in-opt-out-a-breakout-topic-for-the-f40-change-request-on-privacy-preserving-telemetry-for-fedora-workstation/ As mentioned in the thread (and also in [0]) - this is the first time we use discourse for such active discussion, so some transient issues are understandable. [0] https://discussion.fedoraproject.org/t/thoughts-about-the-earlier-proposal-to-use-discourse-for-change-discussions/85380 -- PGP Key ID: 0xFB738CE27B634E4B 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: What is Fedora?
On 6/22/23 06:21, Gordon Messmer wrote: On 2023-06-21 13:06, Philip Wyett wrote: https://www.redhat.com/en/blog/furthering-evolution-centos-stream ... I see an impasse here. Why contribute to fedora when Red Hat will lock it down in other products? I don't think this is a major change from the status quo. In the past, Red Hat has published a subset of the git repositories used to create RHEL. They have published spec and patches used to create the current minor release of each major, but nothing from the EUS or SAP support periods. That is, they haven't published any updates to any branch other than the latest branch they publish. There is only one available branch at any time. Now that Stream is available, the same thing is (apparently) true. At least, as best as I understand their announcement. There will be just one available branch, and that branch will contain the spec and patches used to create the latest packages. That's how I understand it well and I'm a bit confused what's the "fuss" about. The git.centos.org mirrored sources that were used to build CentOS. Since CentOS is no longer supported, and we have the CentOS Stream, the same is true - the sources are still available, just at different location [0]. So this doesn't seem like RH is "locking things down", just getting rid of things that are not needed anymore. Note that I'm in a no way endorsing the change, I'm just trying to understand what's the big deal (if there's any). [0] https://gitlab.com/redhat/centos-stream/rpms [1] https://vault.centos.org/centos/8-stream/ -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B ___ 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: Orphaning my packages
Hey, On 6/29/22 16:56, Francisco J. Tsao Santín via devel wrote: Hello, I've been maintaining some packages, but I can't at this time continue taking care of them. So, next Sunday I'll orphan them if nobody ask me the transfer: * ascii * netmask * ez-pine-gpg * python-meld3 * gpart * python-sysv_ipc * reptyr I'll gladly take over reptyr. Cheers, -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Self Introduction: Radka Brychtova
Welcome, Radka, and good luck! Frantisek On 4/5/22 12:06, Radka Brychtova wrote: Hi, I am Radka, I have been working in Red Hat Brno since 2014 as a RHEL Quality Engineer. A few years ago you might know me as Radka Skvarilova. I am interested in upstreaming our internal tests and helping our developers to feel more safe with releasing some changes in their packages. Have a nice day. Radka ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure -- PGP Key ID: 0xFB738CE27B634E4B 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: mass rebuild status - 2022-01-25
On 1/27/22 14:58, Michael Schwendt wrote: On Thu, 27 Jan 2022 14:01:40 +0100, František Šumšal wrote: Looks like the culprit is: You may have noticed that there are many more compiler errors in the build.log, but it seems you've missed that the src.rpm builds fine for all other archs. What gives? I've indeed noticed the other warnings. However, given this mass rebuild was done with a new snapshot of gcc-12, the error is probably related to that, that's why I pointed out the most severe issue (since it's an error, not a warning). As Jakub wrote in the thread above - getting a preprocessed source would be the next step to get to the root of the 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 on the list, report it: https://pagure.io/fedora-infrastructure -- PGP Key ID: 0xFB738CE27B634E4B 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: mass rebuild status - 2022-01-25
Looks like the culprit is: In file included from common/mptPathString.cpp:13: ./src/mpt/uuid/uuid.hpp: In constructor 'constexpr mpt::mpt_libopenmpt::UUID::UUID()': ./src/mpt/uuid/uuid.hpp:195:17: error: 'goto' is not a constant expression 195 | return; | ^~ ./src/mpt/uuid/uuid.hpp: In constructor 'constexpr mpt::mpt_libopenmpt::UUID::UUID(mpt::mpt_libopenmpt::uint32, mpt::mpt_libopenmpt::uint16, mpt::mpt_libopenmpt::uint16, mpt::mpt_libopenmpt::uint64)': ./src/mpt/uuid/uuid.hpp:202:17: error: 'goto' is not a constant expression 202 | return; | ^~ On 1/27/22 13:54, Michael Schwendt wrote: On Tue, 25 Jan 2022 10:04:32 -0800, Kevin Fenzi wrote: After that we will be done and it will be on maintainers to sort out FTBFS issues. What's up with the armv7hl arch being _the only one_ (!) that failed? https://koji.fedoraproject.org/koji/taskinfo?taskID=81787304 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure -- PGP Key ID: 0xFB738CE27B634E4B 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Intent to orphan gnu-efi
On 1/25/22 19:20, Miro Hrončok wrote:
On 25. 01. 22 19:17, Robbie Harwood wrote:
Hello, we plan to orphan gnu-efi shortly after I finish fixing the
FTBFS. There do not appear to be any consumers:
# dnf repoquery --repo=rawhide{,-source} --whatrequires gnu-efi{,-devel}
--source
Last metadata expiration check: 0:05:32 ago on Tue 25 Jan 2022 01:09:26 PM EST.
gnu-efi-3.0.11-7.1.fc36.src.rpm
$ repoquery --repo=rawhide{,-source} --whatrequires gnu-efi-devel
efitools-0:1.9.2-6.fc36.src
fwupd-efi-0:1.2-1.fc36.src
pesign-test-app-0:5-26.fc34.src
sbsigntools-0:0.9.4-7.fc36.src
shim-unsigned-aarch64-0:15-1.fc28.src
systemd as well, but it's not included in the repoquery possibly because
the dependency is arch-specific:
https://src.fedoraproject.org/rpms/systemd/blob/rawhide/f/systemd.spec#_103
https://src.fedoraproject.org/rpms/systemd/blob/rawhide/f/systemd.spec#_163
--
PGP Key ID: 0xFB738CE27B634E4B
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Bad exit status from %prep during chmod -Rf a+rX,u+w,g-w,o-w . (coreutils 9.0-1.fc36)
Some results from a Rawhide podman container:
# koji download-build --arch x86_64 coreutils-9.0-1.fc36
# dnf install coreutils-common-9.0-1.fc36.x86_64.rpm
coreutils-9.0-1.fc36.x86_64.rpm
# git clone https://github.com/systemd/systemd
# cd systemd
# /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
# echo $?
1
Some further tests:
# mkdir test
# cd test
# touch testfile
# ln -s testfile testlink
# strace /usr/bin/chmod -R a+rX,u+w,g-w,o-w .
execve("/usr/bin/chmod", ["/usr/bin/chmod", "-R", "a+rX,u+w,g-w,o-w", "."],
0x7ffc34d019f8 /* 13 vars */) = 0
brk(NULL) = 0x5589ce102000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffc33618dc0) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
... snip ...
newfstatat(AT_FDCWD, ".", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
fchmodat(AT_FDCWD, ".", 0755) = 0
openat(AT_FDCWD, ".", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
newfstatat(3, "", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_EMPTY_PATH) = 0
fcntl(3, F_GETFL) = 0x18800 (flags
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY)
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
fcntl(3, F_DUPFD_CLOEXEC, 3)= 4
getdents64(3, 0x5589ce107120 /* 4 entries */, 32768) = 112
getdents64(3, 0x5589ce107120 /* 0 entries */, 32768) = 0
close(3)= 0
newfstatat(4, "testfile", {st_mode=S_IFREG|0644, st_size=0, ...},
AT_SYMLINK_NOFOLLOW) = 0
fchmodat(4, "testfile", 0644) = 0
newfstatat(4, "testlink", {st_mode=S_IFLNK|0777, st_size=8, ...},
AT_SYMLINK_NOFOLLOW) = 0
close(4)= 0
close(1)= 0
close(2)= 0
exit_group(1) = ?
+++ exited with 1 +++
However, with coreutils-8.32-31.fc36.x86_64:
# strace /usr/bin/chmod -R a+rX,u+w,g-w,o-w .
... snip ...
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=346132, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 346132, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fcfb35d2000
close(3)= 0
umask(000) = 022
newfstatat(AT_FDCWD, ".", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
fchmodat(AT_FDCWD, ".", 0755) = 0
openat(AT_FDCWD, ".", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
newfstatat(3, "", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_EMPTY_PATH) = 0
fcntl(3, F_GETFL) = 0x18800 (flags
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY)
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
fcntl(3, F_DUPFD_CLOEXEC, 3)= 4
getdents64(3, 0x55748075f120 /* 4 entries */, 32768) = 112
getdents64(3, 0x55748075f120 /* 0 entries */, 32768) = 0
close(3)= 0
newfstatat(4, "testfile", {st_mode=S_IFREG|0644, st_size=0, ...},
AT_SYMLINK_NOFOLLOW) = 0
fchmodat(4, "testfile", 0644) = 0
newfstatat(4, "testlink", {st_mode=S_IFLNK|0777, st_size=8, ...},
AT_SYMLINK_NOFOLLOW) = 0
close(4) = 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
On 10/4/21 13:33, František Šumšal wrote:
I just noticed that as well in our systemd Packit runs, but so far
only on i386, because the repos for x86_64, ppc64le, and aarch64
are still on coreutils-8.32-32.fc36 (whereas i386 has
coreutils-9.0-1.fc36):
https://copr.fedorainfracloud.org/coprs/packit/systemd-systemd-20923/build/2873236/
https://copr.fedorainfracloud.org/coprs/packit/systemd-systemd-20926/build/2873203/
On 10/4/21 11:57, Miro Hrončok wrote:
Hello,
I see this failure in dnf in Copr and Koji:
https://copr.fedorainfracloud.org/coprs/churchyard/patch251/build/2872812/
https://koji.fedoraproject.org/koji/taskinfo?taskID=76673401
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.x8REO2
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf dnf-4.9.0
+ /usr/bin/gzip -dc /builddir/build/SOURCES/dnf-4.9.0.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd dnf-4.9.0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
error: Bad exit status from /var/tmp/rpm-tmp.x8REO2 (%prep)
Bad exit status from /var/tmp/rpm-tmp.x8REO2 (%prep)
I am perplexed with the error.
Could it be some problem with updated coreutils?
___
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/d
Re: Bad exit status from %prep during chmod -Rf a+rX,u+w,g-w,o-w . (coreutils 9.0-1.fc36)
I just noticed that as well in our systemd Packit runs, but so far only on i386, because the repos for x86_64, ppc64le, and aarch64 are still on coreutils-8.32-32.fc36 (whereas i386 has coreutils-9.0-1.fc36): https://copr.fedorainfracloud.org/coprs/packit/systemd-systemd-20923/build/2873236/ https://copr.fedorainfracloud.org/coprs/packit/systemd-systemd-20926/build/2873203/ On 10/4/21 11:57, Miro Hrončok wrote: Hello, I see this failure in dnf in Copr and Koji: https://copr.fedorainfracloud.org/coprs/churchyard/patch251/build/2872812/ https://koji.fedoraproject.org/koji/taskinfo?taskID=76673401 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.x8REO2 + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf dnf-4.9.0 + /usr/bin/gzip -dc /builddir/build/SOURCES/dnf-4.9.0.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd dnf-4.9.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . error: Bad exit status from /var/tmp/rpm-tmp.x8REO2 (%prep) Bad exit status from /var/tmp/rpm-tmp.x8REO2 (%prep) I am perplexed with the error. Could it be some problem with updated coreutils? -- PGP Key ID: 0xFB738CE27B634E4B 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: peek package
On 1/3/20 10:49 AM, Leigh Scott wrote: >> But what about users which actually have ffmpeg installed? Do you think >> they don't deserve having peek in menu? >> >> On Fri, Jan 3, 2020, 04:02 John M. Harris Jr > wrote: > > NO, it's not required on cinnamon, users can use the screenshot+ Record > desktop applet instead. Could you, please, stop with these definitely uncalled for shout outs? Users should definitely have a freedom of choice, and as Samuel pointed out in this thread, the package is not installed by default, so should you find it unsuitable for your system (either a different DE or missing ffmpeg), you can simply uninstall it and replace it with any of the numerous alternatives already previously mentioned. Throwing tantrum because peek doesn't work in your DE won't help in any way apart from causing unnecessary flame wars. Thank you. -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B 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
Re: Intend to orphan i3 and some related packages
On 9/4/19 12:02 PM, Christian Dersch wrote: > I intend to orphan the packages related to i3 window manager Hello! I'd definitely take the dmenu package if there's no-one else! -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B 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
Re: Orphaned packages looking for new maintainers
On 8/26/19 10:20 AM, Miro Hrončok wrote: > 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 releng issues: > https://pagure.io/releng/issues > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2019-08-26.txt > grep it for your FAS username and follow the dependency chain. > > Package (co)maintainers Status > Change > <...snip...> > arandr orphan 0 weeks ago Filed an "adoption" ticket for arandr: https://pagure.io/releng/issue/8686 -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B 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
