Re: [HEADS UP] Rebuild of wxGTK wxGLCanvas-using packages
Scott Talbert wrote on 2022/11/24 2:23: Hi all, In order to fix some incompatibilities with wxWidgets wxGLCanvas (which is currently built with OpenGL EGL support) and several package users which are expecting OpenGL GLX support, I need to rebuild wxWidgets with a different configuration option. Unfortunately, this results in an ABI change, so all packages that link with libwx_gtk3u_gl-3.2.so.0 need to be rebuilt. Unfortunately #2, this also needs to be done in F37. I've opened two side tags to do the rebuilds for F37 and F38. F37: f37-build-side-60200 F38: f38-build-side-60198 The following packages need to be rebuilt in the above side tags (note, I've already taken care of python-wxpython4 and CubicSDR, which are also affected): 0ad OpenSceneGraph erlang hugin kicad mrpt panoglview visualboyadvance-m wxmacmolplt If the maintainers of those packages could rebuild their packages in both of the above side tags, it would be creatly appreciated. After a week, I'll flag down a provenpackager to assist with the rest. Thanks, Scott All the requested packages have been successfully rebuilt: https://koji.fedoraproject.org/koji/builds?inherited=0=60198=-build_id=1 https://koji.fedoraproject.org/koji/builds?inherited=0=60200=-build_id=1 Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf8500ac5b python-slixmpp-1.7.1-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-08012668ea libbsd-0.11.7-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-da88fe53cf advancecomp-2.4-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-15988b1700 qpress-20220819-3.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing pspg-5.5.13-1.el8 Details about builds: pspg-5.5.13-1.el8 (FEDORA-EPEL-2022-6a36b6327b) A unix pager optimized for psql Update Information: new upstream release, per release notes: https://github.com/okbob/pspg/releases/tag/5.5.13 https://github.com/okbob/pspg/releases/tag/5.5.12 https://github.com/okbob/pspg/releases/tag/5.5.11 https://github.com/okbob/pspg/releases/tag/5.5.10 https://github.com/okbob/pspg/releases/tag/5.5.9 https://github.com/okbob/pspg/releases/tag/5.5.8 https://github.com/okbob/pspg/releases/tag/5.5.7 ChangeLog: * Sat Nov 26 2022 Pavel Raiskup - 5.5.13-1 - new upstream release, per release notes: https://github.com/okbob/pspg/releases/tag/5.5.13 https://github.com/okbob/pspg/releases/tag/5.5.12 https://github.com/okbob/pspg/releases/tag/5.5.11 https://github.com/okbob/pspg/releases/tag/5.5.10 https://github.com/okbob/pspg/releases/tag/5.5.9 https://github.com/okbob/pspg/releases/tag/5.5.8 https://github.com/okbob/pspg/releases/tag/5.5.7 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-10049c7b14 libbsd-0.11.7-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing pspg-5.5.13-1.el7 Details about builds: pspg-5.5.13-1.el7 (FEDORA-EPEL-2022-210c1d1236) A unix pager optimized for psql Update Information: new upstream release, per release notes: https://github.com/okbob/pspg/releases/tag/5.5.13 https://github.com/okbob/pspg/releases/tag/5.5.12 https://github.com/okbob/pspg/releases/tag/5.5.11 https://github.com/okbob/pspg/releases/tag/5.5.10 https://github.com/okbob/pspg/releases/tag/5.5.9 https://github.com/okbob/pspg/releases/tag/5.5.8 https://github.com/okbob/pspg/releases/tag/5.5.7 ChangeLog: * Sat Nov 26 2022 Pavel Raiskup - 5.5.13-1 - new upstream release, per release notes: https://github.com/okbob/pspg/releases/tag/5.5.13 https://github.com/okbob/pspg/releases/tag/5.5.12 https://github.com/okbob/pspg/releases/tag/5.5.11 https://github.com/okbob/pspg/releases/tag/5.5.10 https://github.com/okbob/pspg/releases/tag/5.5.9 https://github.com/okbob/pspg/releases/tag/5.5.8 https://github.com/okbob/pspg/releases/tag/5.5.7 ___ 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
Re: F38 proposal: Reproducible builds: Clamp build mtimes to $SOURCE_DATE_EPOCH (System-Wide Change proposal)
On Fri, Nov 11, 2022 at 10:14:56AM -0500, Neal Gompa wrote: > On Fri, Nov 11, 2022 at 8:46 AM Clemens Lang wrote: > > > > Hi, > > > > Alexander Sosedkin wrote: > > > > > In RPM world, I've even entertained an idea of having a subpackage for > > > auditability not unlike how we have debuginfo, since rebuilding a package > > > reproducibly requires builddep pinning. But if that's avoidable, I’d > > > rather just not mix artifacts with meta. > > > > Debian is working on this already, they call those “buildinfo” files: > > > >https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles > >https://manpages.debian.org/testing/dpkg-dev/deb-buildinfo.5.en.html > > > > If we want something similar, I’d propose not to completely re-invent the > > wheel. > > > > We've discussed an RPM-specific format upstream. Debian and Arch both > have their own formats that are tailored to their package systems, and > RPM may have one too, eventually. For context, the discussion is here: https://github.com/rpm-software-management/rpm/pull/1532 -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab 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: Direct to stable updates
@kevin I've announced on Bodhi matrix channel that I was planning to draft the new release, but since I received no response I've pushed out Bodhi 7.0.0. I have followed the SOP at [1] and bodhi-* RPMs are now available in both f37-infra-stg and f36-infra-stg. Tests run smoothly in F37, so I think it's ok to move bodhi-backend on it. Can you take care of running the playbooks on staging so that we can start testing the new version? Mattia [1] https://fedora-infra.github.io/bodhi/develop/developer/releases.html#deploying-a-development-snapshot-to-staging ___ 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: F38 prospoal: Enable bootupd for Fedora Silverblue & Kinoite (Self-Contained Change proposal)
On Mon, Nov 21, 2022 at 05:08:40PM -0500, Colin Walters wrote: > > > On Mon, Nov 21, 2022, at 3:52 PM, Zbigniew Jędrzejewski-Szmek wrote: > > > In particular, two reasons why an upgrade might be interrupted were raised: > > power being cut and the system crashing. Bootupd (or any other daemon) > > cannot > > do much about crashes so this isn't a good motivation. For power, we have > > partial solutions: software-initited poweroffs or reboots should be delayed > > by > > systemd inhibitors. > > Oh yes, definitely an obvious omission from the current code. Filed > https://github.com/coreos/bootupd/issues/403 - thanks! > > > Bootupd+bootupctl creates a lot of interface for the admin > > (status, update, adopt-and-update, validate). This is additional stuff > > to learn. > > Yeah, totally valid comment; though `adopt-and-update` is not something most > admins will need to know. I've been thinking lately that `rpm-ostree > upgrade` should at least *also* display information when bootupd needs to be > invoked too. (And if we did that then combined with the "dnf image" bit then > typing `dnf update` would show this too, which should help a lot. Plus > having clients like gnome-software also become aware of bootupd was part of > the idea) Hmm, so this seems like the wrong direction: gnome-software shouldn't need to know about such low-level details. If gnome-software needs to handle bootloader updates in a special way, it means that bootloader updates become visible to the user, and this shouldn't be necessary. > > It is also additional logic to implement: bootupd must understand > > EFI and boot partitions, mount points, what to do during upgrades, etc. > > I took a brief look at the code and it makes various assumptions about > > how the partitions are named (instead of using part-type uuids!), > > Part of the rationale of for this is that in order to do redundant disk EFI, > we can't use the discoverable UUIDs. Or at least, it'd need to be queried > per disk and not globally. I filed https://github.com/systemd/systemd/issues/25540 (/dev/disk/by-partuuid should have a variant which includes the disk) for this. > > Also, bootupd does up-calls into the package manager to query state. > > No - at least, not in the way you're thinking. bootupd has a separation > between "image build phase" and the client side. The package management > query only happens during image builds (e.g. rpm-ostree compose image/tree > today) which are normally server side. Ah, OK. Thanks for for the explanation. > > Information should flow from the package management system into lower-level > > components > > Yes...though did you read https://github.com/coreos/bootupd/issues/50 and the > sub-thread with Robbie on this? If we want to support lifecycling bootloader > updates separately from the RPM database, that inherently calls for having > the "package manager" (or more generally, the OS updater, which may not > actually "manage packages" at least by default) *not* invoke bootloader > updates - at least by default. > > To connect this with the previous comment - on the client side, bootupd has > its own notion of "update payload" which is just a bit of JSON that today > captures the NEVRA of the component RPMs (but could obviously support content > not from RPM too). > > To state this all another way, remember *today* with systems using MBR/BIOS > and grub2, `dnf update` does *not* update the MBR and hence `rpm -q grub2` is > misleading. So we already have a situation in which the RPM database is not > the same thing as the bootloader state. > > > The raison d'être for bootupd seems to be updates of grub. I guess there > > isn't > > much that can be done in the short term: grub doesn't provide a way to do > > updates atomically, and we need to do those updates, and bootupd seems to > > be a > > reasonable interim solution to wrap them. But I hope this will stop being > > necessary, and either grub will provide such functionality and/or we'll use > > a > > different bootloader. In other words, I understand and won't block this > > Change, > > but doesn't make me particularly happy. It seems that it's code that will be > > used for some time and then go away. > > Thanks, I agree with all of this in general; though, there's going to be a > really long tail on "go away", particularly when one tries to scope in > actually switching bootloaders... Yeah, this is all a thorny problem. I'm not pretending to have any idea how to solve this comprehensively, but as I wrote before, building tools that interact with the user seems like the wrong direction. I think it's fine to add some temporary tooling (if a few years can be considered temporary) to make the update safer. But the end goal should be for those updates to happen in the background without any interaction. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe
Re: [Anaconda-devel] Feedback on Webui Anaconda ISO
Hi Phil, Thanks for your feedback. It's really valuable. Dne 23. 11. 22 v 20:54 Phil Reese napsal(a): Hi, I've tried out your ISO on two systems. One was a USB install while the other was using the Cockpit tool. The USB install went well but seems too dumbed down. No real option for disk configuration. On a 2560x1440 screen there were ACRES of white space and I literally had to turn my head to read from one end to the other of the line. While not ideal for your theme, it might make sense to box the install screen to a modest size and center it in black space. The install was successful and I was able to create an account in the little forced step through process (Note this 'Tour' was boxed in, surrounded by other window space and was much easier to read and interact with.) Yes, we know about this issue and we are right now discussing improvement of the experience. Probably the window will be smaller in the center of the screen as it's popular with also other system installers but we are not yet decided. The second install using Cockpit was a bust. As has been with other F36 ISO installs in Cockpit. The major issue is that the many changed window sizes that the Anaconda process uses didn't work out well with the VNC viewer. The initial Language suggestion screen couldn't be used as the 'Next' box couldn't be clicked on, nor was it obvious that TAB stepped through all the options available (though I could be wrong, as I could only see the smallest top sliver of the blue box.) Not sure what exactly you mean by "using Cockpit". Could you please explain this in bigger detail. Do you mean remote installations? Nice look but it seems to give up too many configuration option that the current Anaconda offers and doesn't work well (or at all) with Cockpit. Please take into account that this is just a first public preview image, definitely not a final one. More configuration will be added but we are not yet there. The image will be updated when there will be something new to show and get feedback on. Best Regards, Jirka Phil Reese ___ Anaconda-devel mailing list -- anaconda-de...@lists.fedoraproject.org To unsubscribe send an email to anaconda-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/anaconda-de...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20221126.n.0 changes
OLD: Fedora-Rawhide-20221125.n.0 NEW: Fedora-Rawhide-20221126.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 10 Dropped packages:0 Upgraded packages: 112 Downgraded packages: 0 Size of added packages: 18.16 MiB Size of dropped packages:0 B Size of upgraded packages: 1.15 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -31.10 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Server_KVM qcow2 ppc64le Path: Server/ppc64le/images/Fedora-Server-KVM-Rawhide-20221125.n.0.ppc64le.qcow2 = ADDED PACKAGES = Package: gap-pkg-standardff-0.9.4-1.fc38 Summary: Standardized generation of finite fields and cyclic subgroups RPMs:gap-pkg-standardff gap-pkg-standardff-doc Size:880.70 KiB Package: php-doctrine-persistence3-3.1.0-1.fc38 Summary: Doctrine Persistence abstractions, version 3 RPMs:php-doctrine-persistence3 Size:41.84 KiB Package: python-azure-mgmt-support-6.0.0-1.fc38 Summary: Microsoft Azure Support Management Client Library for Python RPMs:python3-azure-mgmt-support Size:78.05 KiB Package: python-binary-memcached-0.31.1-1.fc38 Summary: Python module python-binary-memcached RPMs:python3-binary-memcached Size:51.00 KiB Package: python-opfunu-1.0.0-1.fc38 Summary: Benchmark functions for numerical optimization problems RPMs:python-opfunu-doc python3-opfunu Size:9.96 MiB Package: rubygem-gdk4-4.0.3-2.fc38 Summary: Ruby/GDK4 is a Ruby binding of GDK-4.x RPMs:rubygem-gdk4 rubygem-gdk4-doc Size:327.21 KiB Package: rust-bindgen-cli-0.63.0-1.fc38 Summary: Automatically generates Rust FFI bindings to C and C++ libraries RPMs:bindgen-cli Size:6.41 MiB Package: rust-bindgen0.59-0.59.2-1.fc38 Summary: Automatically generates Rust FFI bindings to C and C++ libraries RPMs:rust-bindgen0.59+clap-devel rust-bindgen0.59+default-devel rust-bindgen0.59+env_logger-devel rust-bindgen0.59+log-devel rust-bindgen0.59+logging-devel rust-bindgen0.59+runtime-devel rust-bindgen0.59+static-devel rust-bindgen0.59+testing_only_docs-devel rust-bindgen0.59+testing_only_extra_assertions-devel rust-bindgen0.59+testing_only_libclang_3_9-devel rust-bindgen0.59+testing_only_libclang_4-devel rust-bindgen0.59+testing_only_libclang_5-devel rust-bindgen0.59+testing_only_libclang_9-devel rust-bindgen0.59+which-devel rust-bindgen0.59+which-rustfmt-devel rust-bindgen0.59-devel Size:291.32 KiB Package: rust-crossterm0.22-0.22.1-1.fc38 Summary: Crossplatform terminal library for manipulating terminals RPMs:rust-crossterm0.22+default-devel rust-crossterm0.22+event-stream-devel rust-crossterm0.22+futures-core-devel rust-crossterm0.22+serde-devel rust-crossterm0.22-devel Size:140.99 KiB Package: ykocli-1.0.1-1.fc38 Summary: Front-end script for ykman to obtain TOTP tokens RPMs:ykocli Size:24.56 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: 4Pane-8.0-2.fc38 Old package: 4Pane-8.0-1.fc38 Summary: Multi-pane, detailed-list file manager RPMs: 4Pane Size: 6.56 MiB Size change: -67 B Changelog: * Fri Nov 25 2022 Mamoru TASAKA - 8.0-2 - 8.0 Package: aide-0.16-21.fc38 Old package: aide-0.16-20.fc37 Summary: Intrusion detection environment RPMs: aide Size: 602.69 KiB Size change: 1.08 KiB Changelog: * Fri Nov 25 2022 Florian Weimer - 0.16-21 - Apply upstream patches to port configure to C99 Package: antimicrox-3.3.2-1.fc38 Old package: antimicrox-3.3.1-2.fc38 Summary: Graphical program used to map keyboard buttons and mouse controls to a gamepad RPMs: antimicrox Size: 4.06 MiB Size change: 21.07 KiB Changelog: * Fri Nov 25 2022 Gergely Gombos - 3.3.2-1 - 3.3.2 Package: argus-3.0.8.2-20.fc38 Old package: argus-3.0.8.2-19.fc37 Summary: Network transaction audit tool RPMs: argus argus-clients argus-devel Size: 16.55 MiB Size change: 41.86 KiB Changelog: * Fri Nov 25 2022 Florian Weimer - 3.0.8.2-20 - Port configure scripts to C99 Package: btrfs-progs-6.0.2-1.fc38 Old package: btrfs-progs-6.0.1-1.fc38 Summary: Userspace programs for btrfs RPMs: btrfs-progs btrfs-progs-devel libbtrfs libbtrfsutil python3-btrfsutil Size: 5.61 MiB Size change: 7.95 KiB Changelog: * Fri Nov 25 2022 Neal Gompa - 6.0.2-1 - Update to 6.0.2 Package: ccze-0.2.1-30.fc38 Old package: ccze-0.2.1-29.fc37 Summary: A robust log colorizer RPMs: ccze Size: 335.60 KiB Size change: 593 B Changelog: * Fri Nov 25 2022 Florian Weimer - 0.2.1-30stable, %define release 2.norlug - Port configure script to C99 Package: cfn-lint-0.72.0-1.fc38 Old package: cfn-lint-0.71.1-1.fc38 Summary: CloudFormation Linter RPMs: cfn-lint Size: 1.22 MiB Size change: 10.78 KiB Changelog: * Fri Nov 25 2022 Benjamin
Re: Inactive packagers to be removed after the F37 release
Il 24/11/22 09:38, Vít Ondruch ha scritto: > @Ben isn't it the time to finish this round? > > > Vít > > It's being worked on in https://pagure.io/fedora-infrastructure/issue/11002 Mattia ___ 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: fedpkg clone fails with Permission denied (publickey).
Pavlos Orfanidis a écrit : > I cannot connect to fedorapeople ssh due to public key Permission > denied. Why desn't it sync my public key? (Of course I have added it > to my account) The subject said "fedpkg clone fails with Permission denied (publickey)" But you are talking about fedorapeople servers Please send output of ssh -v Maybe the issue is on the client side: - if you have many ssh keys - if you try password challenge auth first - if you have a custom ssh config - too any "if"... -- GnuPG: AE157E0B29F0BEF2 at keys.openpgp.org CA Cert: https://dl.casperlefantom.net/pub/ssl/root.der Jabber/XMPP Messaging: cas...@casperlefantom.net 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
