Re: Steam install bug

On 10/25/22 23:51, Reon Beon via devel wrote: Only when done by command line. That almost certainly means that the PackageKit metadata cache was stale. "pkcon refresh force" would probably force an update, but it doesn't matter now anyway since you've already done your update from the comma

Re: Steam install bug

Only when done by command line. ___ 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 Guideli

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

> Hi > > > On Tue, Oct 25, 2022 at 7:14 AM Jaroslav Mracek wrote: > > > This response really doesn't clarify what the end result is supposed to be. > Are you planning to maintain a symlink from DNF and Yum to DNF5 after the > transition is complete or not? > > Rahul Yes, we have a plan to m

Re: F38 proposal: RPM Sequoia (System-Wide Change proposal)

On 10/24/22 23:23, Petr Menšík wrote: Hi, maybe it was already answered. Not long ago Thunderbird switched from using installed GPG to its own implementation inside. I think I have found the library part and it seems to be in C++, which should be much more easier to integrate than rust librar

Re: Steam install bug

On 10/25/22 21:47, Reon Beon via devel wrote: They are up to date: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6451 You said it installs fine, so what's the bug? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email t

Re: Steam install bug

They are up to date: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6451 ___ 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

Re: Steam install bug

On 10/25/22 19:41, Reon Beon via devel wrote: Can not download xz-libs. https://ibb.co/cQPHXQw Sounds like a not up-to-date mirror or stale metadata. Did you modify your repo config? ___ devel mailing list -- devel@lists.fedoraproject.org To unsub

Re: Mailman3 on Fedora 36

Subscribe. ___ 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://fedorapr

Re: Mailman3 on Fedora 36

Interesting, thanks. ___ 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:

Steam install bug

Can not download xz-libs. https://ibb.co/cQPHXQw ___ 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-con

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

... > > Concretely, as an upstream maintainer, what should they do to test > > the behaviour of their code ? Is there more to it than just > > setting CFLAGS="-std=gnu99", if they want to validate this in their > > upstream CI ahead of GCC 14 arriving ? > > It's -Werror=implicit-int -Werror=impli

Re: F39 proposal: Python 3.12 (System-Wide Change proposal)

On 25. 10. 22 23:10, Maxwell G via devel wrote: On Tue Oct 25, 2022 at 15:46 -0400, Ben Cotton wrote: * 2023-07-17: Expected side tag-merge (pessimistic) * 2023-07-19: Fedora 39 Mass Rebuild ** The mass rebuild happens with the fourth beta. We might need to rebuild Python packages later in excep

Re: F39 proposal: Python 3.12 (System-Wide Change proposal)

On Tue Oct 25, 2022 at 15:46 -0400, Ben Cotton wrote: > * 2023-07-17: Expected side tag-merge (pessimistic) > * 2023-07-19: Fedora 39 Mass Rebuild > ** The mass rebuild happens with the fourth beta. We might need to > rebuild Python packages later in exceptional case. > ** If the Koji side-tag is n

F39 proposal: Python 3.12 (System-Wide Change proposal)

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

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On 25. 10. 22 16:05, Ben Cotton wrote: == Summary == Back in 1999, a new revision of the C standard removed several backwards compatibility features. However, GCC still accepts these obsolete constructs by default. Support for these constructs is confusing to programmers and potentially affect GC

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, Oct 25, 2022 at 7:42 PM Florian Weimer wrote: > > * Alexander Sosedkin: > > > Since it's a build-time-only change, > > can it be rolled out under controlled pressure like this? > > > > 1. every package explicitly opts out (with some macro in specfile, IDK) > > 2. switch gets flipped, nothi

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

* Alexander Sosedkin: > Since it's a build-time-only change, > can it be rolled out under controlled pressure like this? > > 1. every package explicitly opts out (with some macro in specfile, IDK) > 2. switch gets flipped, nothing changes > 3. bugs get filed to drop that macro and opt into new beh

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, Oct 25, 2022 at 10:05:52AM -0400, Ben Cotton wrote: > Neither change is trivial to implement because introducing errors for > these constructs (as required by C99) alters the result of autoconf > configure checks. Quite a few such checks use an implicitly declared > `exit` function, for ins

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

* Ralf Corsépius: > Am 25.10.22 um 16:05 schrieb Ben Cotton: >> https://fedoraproject.org/wiki/Changes/PortingToModernC. >> This document represents a proposed Change. As part of the Changes >> process, proposals are publicly announced in order to receive >> community feedback. This proposal will

Re: Mailman3 on Fedora 36

On 25/10/2022 18.58, Michael J Gruber wrote: Can you give a bit more context about what you are trying to achieve? I want to be able to continue to use Fedora on the system on which I run mailman for a bunch of mailing lists. Currently that system runs Fedora 35, but that will soon be end-of

Re: Heads up! OpenImageIO 2.4 series coming to rawhide

On Tue, Oct 25, 2022 at 10:31 AM Tom Rix wrote: > > On 10/24/22 1:02 PM, Richard Shaw wrote: > > On Mon, Oct 24, 2022 at 2:48 PM Tom Rix wrote: > >> I was looking at the epel9 build of 2.4 recently but could not figure out >> how to get past the OpenColorIO dependency. >> >> How do you do that ?

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, 2022-10-25 at 15:51 +0100, Daniel P. Berrangé wrote: > I feel that this need to start on the prep work in F38/F39 is not > very obvious from the F40 change proposal text. I thought this was kinda very obviously implicit in the decision to file an F40 Change proposal *now*. -- Adam William

Re: Mailman3 on Fedora 36

Can you give a bit more context about what you are trying to achieve? A quick look at mailman3 and postorius in fedora dist-git reveals that they were retired from rawhide/f37 because they do not build against python 3.11. So, a minor update on f36 (which still has python 3.10) is not really wha

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, Oct 25, 2022 at 5:09 PM Daniel P. Berrangé wrote: > So this change is talking about a new GCC landing in Fedora 40. > > To avoid massive disruption to Fedora though, we need to be doing > work way earlier than the Fedora 40 dev cycle though. > > Identifying all the places where autocon

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

Am 25.10.22 um 16:05 schrieb Ben Cotton: https://fedoraproject.org/wiki/Changes/PortingToModernC. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approve

Mailman3 on Fedora 36

I have created RPMs for mailman3 on Fedora 36. The current (in the repos) version cannot be installed, but my version, based on mailman 3.3.5 can. Also, I have RPMs for postorius and hyperkitty. These RPMs are based on the Fedora 26 source RPMs, but updated to later versions. Also, a whole

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

Hi everyone, Ben Cotton wrote: Neither change is trivial to implement because introducing errors for these constructs (as required by C99) alters the result of autoconf configure checks. Quite a few such checks use an implicitly declared `exit` function, for instance. These failures are not re

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

* Neal Gompa: > Why C99? Why not C18 instead? If we're going to go through this > effort, we should ramp up like we did for C++ and bump all the way up > to the latest published standard. Getting past C99 is the hardest part because it's not possible (as far as I can see) to do fully automated re

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

* Daniel P. Berrangé: > Good to see it mentions autoconf, as such tests were my immediate > concern upon reading the intro. > > I presume the same problem will exist in other build systems that > probe for features, both well known ones like cmake/meson/etc, > but also home grown ones that are pac

Re: Heads up! OpenImageIO 2.4 series coming to rawhide

On 10/24/22 1:02 PM, Richard Shaw wrote: On Mon, Oct 24, 2022 at 2:48 PM Tom Rix > wrote: I was looking at the epel9 build of 2.4 recently but could not figure out how to get past the OpenColorIO dependency. How do you do that ? I haven't branched OIIO or

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

* Ben Cotton: > On Tue, Oct 25, 2022 at 10:05 AM Ben Cotton wrote: >> >> == Upgrade/compatibility impact == >> The change is expected to be transparent to those users who do not use >> C compilers. No features are supposed to be added or removed as a >> result. In fact, most of the porting effort

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, Oct 25, 2022 at 10:51 AM Daniel P. Berrangé wrote: > > On Tue, Oct 25, 2022 at 10:05:52AM -0400, Ben Cotton wrote: > > == Owner == > > * Name: [[User:fweimer| Florian Weimer]] > > * Email: [mailto:fwei...@redhat.com| fwei...@redhat.com] > > > > > > == Detailed Description == > > The most i

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, Oct 25, 2022 at 10:05:52AM -0400, Ben Cotton wrote: > == Owner == > * Name: [[User:fweimer| Florian Weimer]] > * Email: [mailto:fwei...@redhat.com| fwei...@redhat.com] > > > == Detailed Description == > The most important change is the removal of implicit function > declarations. This leg

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Tue, Oct 25, 2022 at 10:05 AM Ben Cotton wrote: > > == Upgrade/compatibility impact == > The change is expected to be transparent to those users who do not use > C compilers. No features are supposed to be added or removed as a > result. In fact, most of the porting effort focuses on avoiding >

F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

https://fedoraproject.org/wiki/Changes/PortingToModernC. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Commit

Non-schedule for Tuesday's FESCo Meeting (2022-10-25)

There are no topics to be discussed in the FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on irc.libera.chat. Hence I decided to cancel it. I will chair the next meeting. = Discussed and Voted in the Ticket = #2880 Fixing accidental change to format preference in GNOME Software https://p

Re: F38 proposal: Ostree Native Container (Phase 2, stable) (System-Wide Change proposal)

On Mon, Oct 24, 2022, at 11:45 PM, Dusty Mabe wrote: > There are a lot of things going on in this proposal: > > - shipping editions as container images in quay https://pagure.io/releng/issue/11047 > - migrating existing users to the new container image based updates (No tracker yet) > - overr

Fedora 37 compose report: 20221025.n.0 changes

OLD: Fedora-37-20221024.n.0 NEW: Fedora-37-20221025.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 13 Downgraded packages: 1 Size of added packages: 0 B Size of dropped packages:0 B Size of

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

Hi On Tue, Oct 25, 2022 at 7:14 AM Jaroslav Mracek wrote: > > DNF team has experience with replacing of YUM in Fedora and RHEL. It give > us an advantage to not repeat the same mistakes. We already know that > shipping DNF as YUM was not a good idea. > This response really doesn't clarify what

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

> Are there going to be provided some deprecation warning in current > version of DNF, should some commands or option change in DNF5? I think > this would help prepare users for the changes in advance and possible > make the transition smoother. > > Vít > > > > Dne 06. 09. 22 v 20:28 Ben Cot

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

> Dne 17. 10. 22 v 9:28 Jaroslav Mracek napsal(a): > > > So why there is proposed the `/usr/bin/dnf` symlink? To create the > confusion again? For Fedora 38 we cannot ship DNF binary. We also cannot provide dnf, hawkey or libdnf in Python bindings, because the those name spaces are already tak

Fedora rawhide compose report: 20221025.n.0 changes

OLD: Fedora-Rawhide-20221024.n.1 NEW: Fedora-Rawhide-20221025.n.0 = SUMMARY = Added images:4 Dropped images: 1 Added packages: 2 Dropped packages:0 Upgraded packages: 6 Downgraded packages: 0 Size of added packages: 1.40 MiB Size of dropped packages:0 B

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

I am sorry, `libdnf-devel` and `libdnf5-devel` conflict on file level. We had a plan to remove the conflict, but community did not considered it as required, therefore we drop that plan. Also the conflict we can take as a feature. The code that would use libdnf and libdnf5 at the same time would

Re: c99-port branches in dist-git

* Richard W. M. Jones: > On Wed, Oct 19, 2022 at 11:30:59AM +0200, Florian Weimer wrote: >> I'm going to push a branch to dist-git for very few packages (so far gcc >> and redhat-rpm-config) which will be used by COPR builds to port Fedora >> to C99 and later language standards. >> >> GCC 14 is e

/usr/lib/debug/usr/lib64/libpython3.so-3.11.0-1.fc38.x86_64.debug in python3.11-debuginfo-3.11.0-1.fc38 on x86_64 is missing ELF sections

Hey, rpminspect tells me that: /usr/lib/debug/usr/lib64/libpython3.so-3.11.0-1.fc38.x86_64.debug in python3.11-debuginfo-3.11.0-1.fc38 on x86_64 is missing ELF sections Details: Missing: .debug_info On rawhide and f37. Is this something I need to worry about? What do I do about it? --

Re: c99-port branches in dist-git

On Wed, Oct 19, 2022 at 11:30:59AM +0200, Florian Weimer wrote: > I'm going to push a branch to dist-git for very few packages (so far gcc > and redhat-rpm-config) which will be used by COPR builds to port Fedora > to C99 and later language standards. > > GCC 14 is expected to reject certain const