Re: proposed change to FESCo voting rules

Ben Cotton wrote: > This will be helpful to people who aren't regularly involved in FESCo > votes. If that's you: the proposal presented here is largely > clarification. There's not much in the way of substance change. Actually, it changes existing practice in that it changes the meaning of the "

Re: btrfs loses 32-bit application compatibility after a while

On Thu, Jul 20, 2023, at 11:55 AM, Florian Weimer wrote: > * Demi Marie Obenour: > >> From this thread, it appears that non-LFS 32-bit software is fundamentally >> unsupportable in the long run, just like software with 32-bit time_t is >> unsupportable. That leaves two options: >> >> 1. Break th

Orphaned libdmapsharing

I orphaned the libdmapsharing package. All of the F38 and Rawhide packages that depended on libdmapsharing have moved on to libdmapsharing4. I recommend allowing libdmapsharing to retire in favor of libdmapsharing4. -- Mike :wq ___ devel mailing list -

Java-devel list?

Is there something wrong with the Java-Devel list? I can send a message to the list and get no reject or error, but is never shows up, at least it looks like that. Or did I miss something? -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1)

Re: Should Fedora switch to full kernel preemption (CONFIG_PREEMPT=y)?

On Thu, 20 Jul 2023 09:17:51 -0500 Justin Forbes wrote: > for them. I have been running preempt=full for quite some time on my > desktops systems here. I've been running custom compiled kernels with preempt_full=Y on my desktop for several years (since at least kernel 5.1). Currently running 6.5

Re: python3 build failure

On Thu, 2023-07-20 at 15:38 -0400, Steve Dickson wrote: > On 7/20/23 2:09 PM, Yaakov Selkowitz wrote: > > On Thu, 2023-07-20 at 13:59 -0400, Steve Dickson wrote: > > > This bz[1] was opened on one of my packages not building on f39. > > > I did a quick rawhide scratch build and sure enough > > > th

Re: Potential changes to systemd RPM macros

On Thu, Jul 20, 2023 at 07:40:08AM -0700, Andrea Bolognani wrote: > Hi, > > this requires a bit of background, so please bear with me :) Thanks for all the background... :) ...snip reasonable stuff... I agree that an upstream systemd solution is what we should strive for. > The problem is that

Re: Making sense of golang packaging guidelines

Hi Fabio, Robert-André, Thank you for the explanation. It makes sense. Golang has this uniqueness about libs that removes some of the shared objects pros but I see there are other things at play. Thank you, Carlos. On Thu, Jul 20, 2023 at 1:44 PM wrote: > On 7/20/23 8:20 PM, Carlos Rodriguez F

Re: proposed change to FESCo voting rules

On Thu, Jul 20, 2023 at 3:46 PM Zbigniew Jędrzejewski-Szmek wrote: > > Stephen Gallagher proposed a change to FESCo voting rules [1]. This will be helpful to people who aren't regularly involved in FESCo votes. If that's you: the proposal presented here is largely clarification. There's not much

Fedora rawhide compose report: 20230720.n.1 changes

OLD: Fedora-Rawhide-20230719.n.0 NEW: Fedora-Rawhide-20230720.n.1 = SUMMARY = Added images:4 Dropped images: 2 Added packages: 4 Dropped packages:0 Upgraded packages: 128 Downgraded packages: 1 Size of added packages: 15.69 MiB Size of dropped packages:0

proposed change to FESCo voting rules

Hi, Stephen Gallagher proposed a change to FESCo voting rules [1]. The latest draft: --&<- Ticket Votes (Preferred) Once a formal proposal is made in a ticket, voting will proceed. A Change ticket is assumed to be a a formal propos

Summary/Minutes from today's FESCo Meeting (2023-07-20)

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2023-07-20/fesco.2023-07-20-17.00.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-2/2023-07-20/fesco.2023-07-20-17.00.txt Log: https://meetbot.fedoraproject.org/fedora-meeting-2/2023-07-20/fesco.2023-07-20-17.00.lo

Re: python3 build failure

On 7/20/23 2:09 PM, Yaakov Selkowitz wrote: On Thu, 2023-07-20 at 13:59 -0400, Steve Dickson wrote: This bz[1] was opened on one of my packages not building on f39. I did a quick rawhide scratch build and sure enough the build fails with [2] The important part is earlier in the log: ModuleN

Re: Making sense of golang packaging guidelines

On 7/20/23 8:20 PM, Carlos Rodriguez Fernandez wrote: Hi all, I am interested in packaging some golang programs for Fedora (and EPEL), and I read through the guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/

Re: Making sense of golang packaging guidelines

On Thu, Jul 20, 2023 at 8:22 PM Carlos Rodriguez Fernandez wrote: > > Hi all, > > I am interested in packaging some golang programs for Fedora (and EPEL), and > I read through the guidelines: > https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/ > > My question is more about the rea

Making sense of golang packaging guidelines

Hi all, I am interested in packaging some golang programs for Fedora (and EPEL), and I read through the guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/ My question is more about the reasoning for the recommended handling of dependencies. Other language platforms hav

Re: python3 build failure

On Thu, 2023-07-20 at 13:59 -0400, Steve Dickson wrote: > This bz[1] was opened on one of my packages not building on f39. > I did a quick rawhide scratch build and sure enough > the build fails with [2] The important part is earlier in the log: ModuleNotFoundError: No module named 'distutils' d

python3 build failure

Hello, This bz[1] was opened on one of my packages not building on f39. I did a quick rawhide scratch build and sure enough the build fails with [2] Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py", line 93, in trace result = func(

Re: Several questionable packages installed on fresh system

On Thu, 13 Jul 2023 14:10:37 +0200 Vít Ondruch wrote: > Dne 10. 07. 23 v 10:38 Vít Ondruch napsal(a): > > Hi, > > > > > > libtomcrypt > > > > So this is the dependency chain: > > libtomcrypt <= python3-crypto <= python3-beaker <= python3-mako I raised https://bugzilla.redhat.com/show_bug.cgi

Re: btrfs loses 32-bit application compatibility after a while

* Demi Marie Obenour: > From this thread, it appears that non-LFS 32-bit software is fundamentally > unsupportable in the long run, just like software with 32-bit time_t is > unsupportable. That leaves two options: > > 1. Break the ABI, preferably in such a way that causes non-LFS >code to fa

Re: btrfs loses 32-bit application compatibility after a while

On 7/20/23 11:06, Florian Weimer wrote: > * Demi Marie Obenour: > >> On 7/17/23 09:51, Florian Weimer wrote: >>> * Daniel P. Berrangé: >>> > But that still raises the question - why does it look like this > started to happen pretty suddenly around June 30? > The list of updates that we

Re: btrfs loses 32-bit application compatibility after a while

Thu, Jul 20, 2023 at 5:07 PM Florian Weimer wrote: > > * Demi Marie Obenour: > > > On 7/17/23 09:51, Florian Weimer wrote: > >> * Daniel P. Berrangé: > >> > But that still raises the question - why does it look like this > started to happen pretty suddenly around June 30? > The list

Re: btrfs loses 32-bit application compatibility after a while

* Demi Marie Obenour: > On 7/17/23 09:51, Florian Weimer wrote: >> * Daniel P. Berrangé: >> But that still raises the question - why does it look like this started to happen pretty suddenly around June 30? The list of updates that were applied to builders in that timeframe doe

Potential changes to systemd RPM macros

Hi, this requires a bit of background, so please bear with me :) Earlier this year, the libvirt project changed its RPM package to be more granular[1] as a step towards a future where the legacy monolithic daemon (libvirtd) is completely gone. This change has happened upstream, but the Fedora pa

Re: Should Fedora switch to full kernel preemption (CONFIG_PREEMPT=y)?

On Thu, Jul 20, 2023 at 8:53 AM Daniel P. Berrangé wrote: > > On Sat, May 20, 2023 at 06:14:17PM -0500, Justin Forbes wrote: > > On Sat, May 20, 2023 at 3:44 PM Demi Marie Obenour > > wrote: > > > > > > I noticed that by default, Qubes OS has voluntary kernel preemption > > > as opposed to full p

Re: libarrow (Apache Arrow) soname bump in Rawhide

On Thu, Jul 20, 2023 at 4:07 PM Kaleb Keithley wrote: > > > > On Mon, May 1, 2023 at 8:01 AM Kaleb Keithley wrote: >> >> >> >> Now Apache Arrow 12.0.0 has been released. >> >> Rebase landing soon in Rawhide. > > > Apache Arrow (libarrow) 13.0.0 has been released. > > At least within Fedora, only

Re: libarrow (Apache Arrow) soname bump in Rawhide

On Mon, May 1, 2023 at 8:01 AM Kaleb Keithley wrote: > > > Now Apache Arrow 12.0.0 has been released. > > Rebase landing soon in Rawhide. > Apache Arrow (libarrow) 13.0.0 has been released. At least within Fedora, only Ceph (ceph-common, ceph-radosgw, ceph-test, librgw2) depends on libarrow. I

Re: Should Fedora switch to full kernel preemption (CONFIG_PREEMPT=y)?

On Thu, Jul 20, 2023, at 9:53 AM, Daniel P. Berrangé wrote: > What's the downside from full pre-empt that makes it inappropriate > as the defualt for Fedora server spins too ? Is it that it is > trading off overall peak performance in favour of reduced latency, > and we think servers would prefe

Re: Should Fedora switch to full kernel preemption (CONFIG_PREEMPT=y)?

On Thu, Jul 20, 2023, at 9:51 AM, Michael Catanzaro wrote: > On Wed, Jul 19 2023 at 06:50:24 PM -0400, Chris Murphy > wrote: >> If restricted to desktops, then we can only do it with kernel >> parameters. That probably means doing it in Anaconda kickstart, with >> a per edition/spin option fo

Re: Should Fedora switch to full kernel preemption (CONFIG_PREEMPT=y)?

On Sat, May 20, 2023 at 06:14:17PM -0500, Justin Forbes wrote: > On Sat, May 20, 2023 at 3:44 PM Demi Marie Obenour > wrote: > > > > I noticed that by default, Qubes OS has voluntary kernel preemption > > as opposed to full preemption. I found that enabling full preemption > > (preempt=full on ke

Re: Should Fedora switch to full kernel preemption (CONFIG_PREEMPT=y)?

On Wed, Jul 19 2023 at 06:50:24 PM -0400, Chris Murphy wrote: If restricted to desktops, then we can only do it with kernel parameters. That probably means doing it in Anaconda kickstart, with a per edition/spin option for doing so. I'm not fond of this solution. In practice, this would likel

Re: btrfs loses 32-bit application compatibility after a while

On 7/17/23 09:51, Florian Weimer wrote: > * Daniel P. Berrangé: > >>> But that still raises the question - why does it look like this >>> started to happen pretty suddenly around June 30? >>> The list of updates that were applied to builders in that timeframe >>> doesn't raise any alarm bells (exc

Re: Orphaned Zim

On 20-07-2023 14:38, Otto Liljalaakso wrote: I think I may have used Zim in the past and I may have some use for it again. I'd be happy to co-maintain. Great! I have added you with commit privileges. In case you (or anybody else) know Python buildsystems, you could check the upstream issue ab

Re: Say goodbye to polymake

On Thu, Jul 20, 2023 at 02:20:59AM +0200, Kevin Kofler via devel wrote: > Richard W.M. Jones wrote: > > > /home/rjones/d/fedora/polymake/rawhide/polymake-4.10/lib/core/src/perl/RefHash.xxs:737:11: > > error: ‘Perl_ck_fun’ was not declared in this scope; did you mean > > ‘Perl_cx_dup’? > > 737 |

Re: Orphaned Zim

Sandro kirjoitti 20.7.2023 klo 12.42: On 19-07-2023 23:11, Otto Liljalaakso wrote: Robin Lee kirjoitti 14.7.2023 klo 17.53: I've orphaned the Zim package. It fails to build with Python 3.12 in Rawhide. Users can move to the flatpak on Flathub, which is also packaged by me. Thank you for main

Re: F39 proposal: Perl 5.38 (System-Wide Change proposal)

Hi，I am interesting in the upgrading of perl. Where can I find the detailed process of upgrading and building Perl, including the entire build steps, the list of built RPM packages, and the building order of Perl module packages? ___ devel mailing list

Orphaned Onboard

Hi all, I've orphaned the Onboard package. I stopped using it personally and don't have enough time to handle some bug report. If anyone want to take it please do so. - Qiyu ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send

Schedule for Thursday's FESCo Meeting (2023-07-20)

Following is the list of topics that will be discussed in the FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on irc.libera.chat. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2023-07-20 17:00 UTC' Links to all issues to be

Re: DNF5-5.0.1 has a stable API

Miroslav Suchý wrote: > "Only dead projects has stable API" Sorry, but this is just nonsense. APIs can be appended to, even rewrites can be made API-compatible if developers actually care about that. Even if the internal code is completely different, the public API can be retained, at least if

Re: DNF5-5.0.1 has a stable API

On Thu, Jul 20, 2023 at 10:46 AM Miroslav Suchý wrote: > > Dne 20. 07. 23 v 10:08 Peter Robinson napsal(a): > > The dnf5 API has similar primitives (Base, Goal, Package, etc.), but it's > >> not at all compatible. > > It may be worth to add the link to the API: > > https://dnf5.readthedocs.io/en/l

Re: DNF5-5.0.1 has a stable API

Dne 20. 07. 23 v 10:08 Peter Robinson napsal(a): The dnf5 API has similar primitives (Base, Goal, Package, etc.), but it's not at all compatible. It may be worth to add the link to the API: https://dnf5.readthedocs.io/en/latest/api/index.html So everything has to be rewritten across the ent

Re: Orphaned Zim

On 19-07-2023 23:11, Otto Liljalaakso wrote: Robin Lee kirjoitti 14.7.2023 klo 17.53: I've orphaned the Zim package. It fails to build with Python 3.12 in Rawhide. Users can move to the flatpak on Flathub, which is also packaged by me. Thank you for maintaining the Zim package until now. I to

Re: DNF5-5.0.1 has a stable API

On Wed, Jul 19, 2023 at 11:35 PM Maxwell G wrote: > > > 2023-07-19T13:39:57Z Peter Robinson : > > > On Wed, Jul 19, 2023 at 2:20 PM Nicola Sella wrote: > >> > >> Hi all, > >> Yesterday, DNF5 5.1.0 was released upstream[1] and in rawhide[2]. This > >> update makes DNF5's API stable. This means tha