Re: subtle issue with systemd, dnf 'greedy' obsoletes behaviour, and multiple repos

Dne 05. 06. 20 v 8:41 Kevin Kofler napsal(a): The fact that Obsoletes from outdated packages are being considered is the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1748187 but the DNF developers refused to acknowledge this and just closed the bug when the issue was worked around in the fo

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/CompilerPolicy > > == Summary == > Fedora has historically forced packages to build with GCC unless the > upstream project for the package only supported C

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 9:11 AM Igor Raits wrote: > Also we probably should mention that -fstack-clash-protection is not > available in clang, so in theory binaries can be less secure due to > that. > This seems to be worked on as per https://reviews.llvm.org/D68720?id=224102 (on x86, I am not su

Re: Fedora 33 System-Wide Change proposal: swap on zram

I am +1 for this change, I don't have any numbers but from day-to-day usage, both my systems seem far more responsive when swapping to zram instead of swap. On Fri, Jun 5, 2020 at 8:56 AM Kevin Kofler wrote: > I do not think it is safe to assume that zram is sufficient to completely > replace di

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/SwapOnZRAM > > == Summary == > > Swap is useful, except when it's slow. zram is a RAM drive that uses > compression. Create a swap-on-zram during start-up

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 09:16 +0200, Frantisek Zatloukal wrote: > On Fri, Jun 5, 2020 at 9:11 AM Igor Raits < > ignatenkobr...@fedoraproject.org> > wrote: > > > Also we probably should mention that -fstack-clash-protection is > > not > > available in

Re: Fedora 33 System-Wide Change proposal: swap on zram

On Fri, Jun 5, 2020 at 12:33 AM Milan Crha wrote: > > On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote: > > ... The memory used is not preallocated. It's > > dynamically allocated and deallocated, on demand. ... > > > > The system will use RAM normally up until it's full, and then start > > pag

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

Ben Cotton wrote: > == Summary == > Fedora has historically forced packages to build with GCC unless the > upstream project for the package only supported Clang/LLVM. This > change proposal replaces that policy with one where compiler selection > for Fedora follows the package's upstream preferenc

Re: Fedora 33 System-Wide Change proposal: swap on zram

On Fri, Jun 5, 2020 at 1:25 AM Frantisek Zatloukal wrote: > I believe having zram as a high priority swap and then normal swap with lower > priority to be used when zram gets filled up might be an option too (I am not > saying we should go that route, just mentioning it's a possibility). That

Fedora-Cloud-32-20200605.0 compose check report

No missing expected images. Soft failed openQA tests: 1/1 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 612010 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/612010 -- Mail generated by check-compose: https://pagure.i

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 08:54 +0200, Kevin Kofler wrote: > Ben Cotton wrote: > > Swap is useful, except when it's slow. zram is a RAM drive that > > uses > > compression. Create a swap-on-zram during start-up. And no longer > > use > > swap partitions

Re: Fedora 33 System-Wide Change proposal: swap on zram

On Fri, Jun 5, 2020 at 1:33 AM Igor Raits wrote: > > > == Upgrade/compatibility impact == > > > > Add Supplements:fedora-release-common to zram-generator to pull it in > > on upgrades. > > I would do it other way around just to keep logic sane. Hmmm. > > > Existing systems without swap will hav

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 09:52 +0200, Kevin Kofler wrote: > Ben Cotton wrote: > > == Summary == > > Fedora has historically forced packages to build with GCC unless > > the > > upstream project for the package only supported Clang/LLVM. This > > change

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 9:57 AM Kevin Kofler wrote: > Ben Cotton wrote: > > == Summary == > > Fedora has historically forced packages to build with GCC unless the > > upstream project for the package only supported Clang/LLVM. This > > change proposal replaces that policy with one where compiler

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 02:03 -0600, Chris Murphy wrote: > On Fri, Jun 5, 2020 at 1:33 AM Igor Raits > wrote: > > > > > == Upgrade/compatibility impact == > > > > > > Add Supplements:fedora-release-common to zram-generator to pull > > > it in > > >

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 10:17 +0200, Igor Raits wrote: > On Fri, 2020-06-05 at 02:03 -0600, Chris Murphy wrote: > > On Fri, Jun 5, 2020 at 1:33 AM Igor Raits > > wrote: > > > > > > > == Upgrade/compatibility impact == > > > > > > > > Add Supplements

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 9:56 AM Kevin Kofler wrote: > I am opposed to this change. Chromium and Firefox build fine with GCC. I > think that a distribution should be built with a consistent toolchain > wherever possible. > Kevin, that's not true at all. Maybe it looks like it builds fine for you,

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 10:15 +0200, Frantisek Zatloukal wrote: > On Fri, Jun 5, 2020 at 9:57 AM Kevin Kofler > wrote: > > > Ben Cotton wrote: > > > == Summary == > > > Fedora has historically forced packages to build with GCC unless > > > the > > >

Fedora-Cloud-31-20200605.0 compose check report

No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedorap

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05/06/20 10:23 +0200, Tomáš Popela wrote: On Fri, Jun 5, 2020 at 9:56 AM Kevin Kofler wrote: I am opposed to this change. Chromium and Firefox build fine with GCC. I think that a distribution should be built with a consistent toolchain wherever possible. Kevin, that's not true at all. Ma

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05/06/20 10:26 +0200, Igor Raits wrote: Well, upstreams are not necessarily enabling many security features or optimizations. So you are effectively saying "upstream knows better" where I would have to disagree with you. Yes, this is a very good point. Many of Fedora's packages have upstrea

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05/06/20 09:09 +0200, Igor Raits wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote: https://fedoraproject.org/wiki/Changes/CompilerPolicy == Summary == Fedora has historically forced packages to build with GCC unless the upstream proj

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 04/06/20 16:30 -0400, Ben Cotton wrote: https://fedoraproject.org/wiki/Changes/CompilerPolicy [snip] == Documentation == Several years ago Red Hat's tools team championed for Fedora policy to strongly discourage the use of LLVM/Clang for package building. Exceptions were made for packages t

Re: Proposal: Install gparted to Live installers

Ian McInerney left as an exercise for the reader: > There are a couple of advantages to gparted (that I haven't found analogous > operations for in gnome-disks): (apologies if this mail is received twice; i attached an image first, and it was blocked by the listserv) A few years ago, I wrote a t

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 05, 2020 at 09:52:09AM +0200, Kevin Kofler wrote: > I do not see why we should allow yet another special case for Firefox, nor > why we should let random packages make their own choice of compiler and risk > running into hidden binary incompatibilities. We have a system compiler for

Re: Rebuilt for OpenCV 4.3.0 in rawhide

Le ven. 5 juin 2020 à 08:52, Igor Raits a écrit : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On Fri, 2020-05-29 at 14:02 +0200, Nicolas Chauvet wrote: > > Hello there, > > > > There is an update to opencv 4.3.0 in preparation for rawhide. > > This will be handled in a side tag along

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

Dne 05. 06. 20 v 9:52 Kevin Kofler napsal(a): > Ben Cotton wrote: >> == Summary == >> Fedora has historically forced packages to build with GCC unless the >> upstream project for the package only supported Clang/LLVM. This >> change proposal replaces that policy with one where compiler selection

Re: How to convert from GRUB to systemd-boot?

> Is there someone that can help me convert my Fedora install from GRUB to > systemd-boot and actually get it where kernel updates won't break it? > > The reason is that my MS Surface GO does not work with GRUB for some reason. > Probably a non-standard UEFI implementation but I both found this t

Re: Fedora 33 System-Wide Change proposal: swap on zram

On Thu, Jun 4, 2020 at 10:32 PM Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/SwapOnZRAM > > == Summary == > > Swap is useful, except when it's slow. zram is a RAM drive that uses > compression. Create a swap-on-zram during start-up. And no longer use > swap partitions by default. >

Re: Fedora 33 System-Wide Change proposal: swap on zram

On 04.06.2020 22:30, Ben Cotton wrote: > Swap is useful, except when it's slow. zram is a RAM drive that uses > compression. Create a swap-on-zram during start-up. And no longer use > swap partitions by default. I'm strongly against this, because zram will replace disk swap and disable hibernation

Re: Fedora 33 System-Wide Change proposal: swap on zram

On 05.06.2020 09:24, Frantisek Zatloukal wrote: > I am +1 for this change, I don't have any numbers but from day-to-day > usage, both my systems seem far more responsive when swapping to zram > instead of swap. But it will cause a huge memory fragmentation and significantly decrease overall perfor

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

* Igor Raits: > From what I see, GCC supports it on x86, x86_64, s390x, riscv64, > ppc64le. So this just does not include ARM / AArch64 from Fedora > architectures. GCC has aarch64 support for stack-clash-protection, but it only works well with 64K pages (otherwise detection is not reliable). Th

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 04.06.2020 22:30, Ben Cotton wrote: > Fedora has historically forced packages to build with GCC unless the > upstream project for the package only supported Clang/LLVM. This > change proposal replaces that policy with one where compiler selection > for Fedora follows the package's upstream pref

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05.06.2020 09:52, Kevin Kofler wrote: > I am opposed to this change. Chromium and Firefox build fine with GCC. I > think that a distribution should be built with a consistent toolchain > wherever possible. Clang is much better than GCC nowadays. It has better architecture, support lots of opt

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 12:34 +0200, Vitaly Zaitsev via devel wrote: > On 04.06.2020 22:30, Ben Cotton wrote: > > Swap is useful, except when it's slow. zram is a RAM drive that > > uses > > compression. Create a swap-on-zram during start-up. And no lo

Re: Fedora 33 System-Wide Change proposal: swap on zram

On 05.06.2020 12:50, Igor Raits wrote: > It does not work in some cases even today anyway. Okay, then the second point - zram will will cause a huge memory fragmentation and significantly decrease overall performance. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___

Re: Fedora 33 System-Wide Change proposal: swap on zram

On 6/5/20 1:23 PM, Vitaly Zaitsev via devel wrote: > On 05.06.2020 12:50, Igor Raits wrote: >> It does not work in some cases even today anyway. > > Okay, then the second point - zram will will cause a huge memory > fragmentation and significantly decrease overall performance. If you say this is

Re: Upcoming fedoraproject Datacenter move reminder and plans

On 02. 06. 20 18:40, Kevin Fenzi wrote: Greetings. As previously announced, fedoraproject is moving many of it's servers from one datacenter (phx2 near phoenix, arizona, usa) to another (iad2: near arlington, virginia, usa). As we move from the old datacenter to the new, we will have a temporar

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 10:14 +0100, Jonathan Wakely wrote: > On 04/06/20 16:30 -0400, Ben Cotton wrote: > > https://fedoraproject.org/wiki/Changes/CompilerPolicy > [snip] > > == Documentation == > > Several years ago Red Hat's tools team championed fo

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 6:47 AM Vitaly Zaitsev via devel wrote: > > On 05.06.2020 09:52, Kevin Kofler wrote: > > I am opposed to this change. Chromium and Firefox build fine with GCC. I > > think that a distribution should be built with a consistent toolchain > > wherever possible. > > Clang is muc

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 8:26 AM Neal Gompa wrote: > > On Fri, Jun 5, 2020 at 6:47 AM Vitaly Zaitsev via devel > wrote: > > > > On 05.06.2020 09:52, Kevin Kofler wrote: > > > I am opposed to this change. Chromium and Firefox build fine with GCC. I > > > think that a distribution should be built wit

Re: Fedora 33 System-Wide Change proposal: swap on zram

On Fri, Jun 5, 2020 at 1:52 am, Chris Murphy wrote: That is the plan, otherwise the swap-on-zram device probably never gets used. And then its overhead, which is small but not zero, is just a waste. I thought the plan was to get rid of the disk-based swap partition, since it has an unacceptab

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05/06/2020 10:15, Frantisek Zatloukal wrote: [...] Apart from browsers, LibreOffice is going to use LLVM/Clang from Release 7.0 too, so that would potentially be another added work to LibreOffice packagers in the future. Just to clarify, upstream LibreOffice supports both GCC and Clang on

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 11:19 +0200, Jakub Jelinek wrote: > On Fri, Jun 05, 2020 at 09:52:09AM +0200, Kevin Kofler wrote: > > I do not see why we should allow yet another special case for Firefox, nor > > why we should let random packages make their own choice of compiler and > > risk > > running

Re: Fedora 33 System-Wide Change proposal: swap on zram

> On 05.06.2020 12:50, Igor Raits wrote: > > It does not work in some cases even today anyway. > > Okay, then the second point - zram will will cause a huge memory > fragmentation and significantly decrease overall performance. Have you got proof of that and can provide figures? Having been runnin

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 07:42 -0500, Michael Catanzaro wrote: > On Fri, Jun 5, 2020 at 1:52 am, Chris Murphy > > wrote: > > That is the plan, otherwise the swap-on-zram device probably never > > gets used. And then its overhead, which is small but no

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 1:51 PM Stephan Bergmann wrote: > On 05/06/2020 10:15, Frantisek Zatloukal wrote: > > [...] Apart from > > browsers, LibreOffice is going to use LLVM/Clang from Release 7.0 too, > > so that would potentially be another added work to LibreOffice packagers > > in the future.

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05/06/2020 15:16, Ian McInerney wrote: On Fri, Jun 5, 2020 at 1:51 PM Stephan Bergmann > wrote: On 05/06/2020 10:15, Frantisek Zatloukal wrote: > [...] Apart from > browsers, LibreOffice is going to use LLVM/Clang from Release 7.0 too, > so t

Is the name of this review package OK?

https://bugzilla.redhat.com/show_bug.cgi?id=1825456 Proposed package name is "libvirt-test-api". Upstream name is "libvirt-test-API". It is, very very loosely, a Python 3 API and the package includes Python development files. But on the other hand it's a set of regression tests and the fact the

Re: [HEADS UP] F33 Boost 1.73.0 rebuilds starting in a side tag

Next problem... /usr/include/boost/geometry/index/detail/rtree/node/variant_visitor.hpp:51:25: error: no matching function for call to 'apply_visitor(boost::geometry::index::detail::rtree::visitors::insert, WireJoiner::PntGetter>::members_holder, boost::geometry::index::detail::rtree::insert_defau

Let's standardize the way to disable tests during RPM build?

Hi, I think it would be useful to have a standard way of disabling the running of tests during RPM build (in the %check section of a spec file). I see a lot of packages already having %bcond's or other macro definitions to archieve this, but each package has their own way, there's no real sta

Re: Fedora 33 System-Wide Change proposal: swap on zram

On Fri, Jun 05, 2020 at 01:50:29AM -0600, Chris Murphy wrote: > On Fri, Jun 5, 2020 at 12:33 AM Milan Crha wrote: > > > > On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote: > > > ... The memory used is not preallocated. It's > > > dynamically allocated and deallocated, on demand. ... > > > > > >

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 05, 2020 at 08:27:13AM -0400, Neal Gompa wrote: > On Fri, Jun 5, 2020 at 8:26 AM Neal Gompa wrote: > > > > On Fri, Jun 5, 2020 at 6:47 AM Vitaly Zaitsev via devel > > wrote: > > > > > > On 05.06.2020 09:52, Kevin Kofler wrote: > > > > I am opposed to this change. Chromium and Firefox

Re: Let's standardize the way to disable tests during RPM build?

On Fri, Jun 05, 2020 at 04:10:20PM +0200, Tomas Orsava wrote: > Hi, > I think it would be useful to have a standard way of disabling the > running of tests during RPM build (in the %check section of a spec > file). > > I see a lot of packages already having %bcond's or other macro > definitions to

Re: [Fedora-packaging] Let's standardize the way to disable tests during RPM build?

Or just a new option to rpmbuild that skips %check ? Sent from my iPhone > On Jun 5, 2020, at 10:11, Tomas Orsava wrote: > > Hi, > I think it would be useful to have a standard way of disabling the running of > tests during RPM build (in the %check section of a spec file). > > I see a lot o

Re: Let's standardize the way to disable tests during RPM build?

On 05. 06. 20 16:26, Richard W.M. Jones wrote: On Fri, Jun 05, 2020 at 04:10:20PM +0200, Tomas Orsava wrote: Hi, I think it would be useful to have a standard way of disabling the running of tests during RPM build (in the %check section of a spec file). I see a lot of packages already having %b

Re: [Fedora-packaging] Let's standardize the way to disable tests during RPM build?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 16:10 +0200, Tomas Orsava wrote: > Hi, > I think it would be useful to have a standard way of disabling the > running of tests during RPM build (in the %check section of a spec > file). > > I see a lot of packages already havi

Re: [Fedora-packaging] Let's standardize the way to disable tests during RPM build?

On Fri, Jun 05, 2020 at 10:28:39AM -0400, Paul Wouters wrote: > Or just a new option to rpmbuild that skips %check ? It exists already: rpmbuild --nocheck. It's not wired into the rest of the stack - eg. you cannot start a Koji build with checks disabled. IMHO that's a good thing, although when

Re: Let's standardize the way to disable tests during RPM build?

On 6/5/20 4:26 PM, Richard W.M. Jones wrote: On Fri, Jun 05, 2020 at 04:10:20PM +0200, Tomas Orsava wrote: Hi, I think it would be useful to have a standard way of disabling the running of tests during RPM build (in the %check section of a spec file). I see a lot of packages already having %bco

Re: [Fedora-packaging] Let's standardize the way to disable tests during RPM build?

On 6/5/20 4:39 PM, Richard W.M. Jones wrote: On Fri, Jun 05, 2020 at 10:28:39AM -0400, Paul Wouters wrote: Or just a new option to rpmbuild that skips %check ? It exists already: rpmbuild --nocheck. It's not wired into the rest of the stack - eg. you cannot start a Koji build with checks disab

Re: Let's standardize the way to disable tests during RPM build?

On Fri, Jun 05, 2020 at 04:38:03PM +0200, Miro Hrončok wrote: > On 05. 06. 20 16:26, Richard W.M. Jones wrote: > >On Fri, Jun 05, 2020 at 04:10:20PM +0200, Tomas Orsava wrote: > >>Hi, > >>I think it would be useful to have a standard way of disabling the > >>running of tests during RPM build (in th

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 06/05/2020 12:09 AM, Igor Raits wrote: > On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote: >> https://fedoraproject.org/wiki/Changes/CompilerPolicy > >> == Summary == >> Fedora has historically forced packages to build with GCC unless the >> upstream project for the package only supported Cl

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 10:24 AM Richard W.M. Jones wrote: > > On Fri, Jun 05, 2020 at 08:27:13AM -0400, Neal Gompa wrote: > > On Fri, Jun 5, 2020 at 8:26 AM Neal Gompa wrote: > > > > > > On Fri, Jun 5, 2020 at 6:47 AM Vitaly Zaitsev via devel > > > wrote: > > > > > > > > On 05.06.2020 09:52, Kev

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 06/05/2020 03:42 AM, Vitaly Zaitsev via devel wrote: > On 04.06.2020 22:30, Ben Cotton wrote: >> Fedora has historically forced packages to build with GCC unless the >> upstream project for the package only supported Clang/LLVM. This >> change proposal replaces that policy with one where compil

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 06/05/2020 08:05 AM, Neal Gompa wrote: > On Fri, Jun 5, 2020 at 10:24 AM Richard W.M. Jones wrote: >> >> On Fri, Jun 05, 2020 at 08:27:13AM -0400, Neal Gompa wrote: >>> On Fri, Jun 5, 2020 at 8:26 AM Neal Gompa wrote: On Fri, Jun 5, 2020 at 6:47 AM Vitaly Zaitsev via devel wrot

Re: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 07:33 +, devel-requ...@lists.fedoraproject.org wrote: > -- > > Date: Fri, 5 Jun 2020 09:16:21 +0200 > From: Frantisek Zatloukal > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy >

Re: Let's standardize the way to disable tests during RPM build?

On 6/5/20 4:46 PM, Richard W.M. Jones wrote: On Fri, Jun 05, 2020 at 04:38:03PM +0200, Miro Hrončok wrote: On 05. 06. 20 16:26, Richard W.M. Jones wrote: On Fri, Jun 05, 2020 at 04:10:20PM +0200, Tomas Orsava wrote: Hi, I think it would be useful to have a standard way of disabling the running

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 14:38 +, devel-requ...@lists.fedoraproject.org wrote: > > Date: Fri, 5 Jun 2020 15:23:57 +0100 > From: "Richard W.M. Jones" > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > Change > To: Development discussions related to Fedora > > Cc:

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 08:07 -0700, Tom Stellard wrote: > On 06/05/2020 03:42 AM, Vitaly Zaitsev via devel wrote: > > On 04.06.2020 22:30, Ben Cotton wrote: > > > Fedora has historically forced packages to build with GCC unless > > > the > > > upstrea

Re: System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 12:27 +, devel-requ...@lists.fedoraproject.org wrote: > > On Fri, 2020-06-05 at 10:14 +0100, Jonathan Wakely wrote: > > On 04/06/20 16:30 -0400, Ben Cotton wrote: > > > https://fedoraproject.org/wiki/Changes/CompilerPolicy > > [snip] > > > == Documentation == > > > Severa

Re: Let's standardize the way to disable tests during RPM build?

Le vendredi 05 juin 2020 à 15:46 +0100, Richard W.M. Jones a écrit : > > For the RISC-V bootstrap we used rpmbuild directly (before Koji and > its dependencies had been ported), and added --nocheck. However once > Koji was working we built packages properly with checks enabled. > > How often do

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

Hi, On Fri, 2020-06-05 at 09:25 -0600, Jeff Law wrote: > The LTO bytecode streams do not survive past any given package build. ie, > they > are used within the build, then discarded. They're not supposed to show up in > any installed libraries. > > Thus the fact that the two compilers use tota

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, Jun 5, 2020 at 8:27 AM Neal Gompa wrote: > > On Fri, Jun 5, 2020 at 6:47 AM Vitaly Zaitsev via devel > wrote: > > > > On 05.06.2020 09:52, Kevin Kofler wrote: > > > I am opposed to this change. Chromium and Firefox build fine with GCC. I > > > think that a distribution should be built wit

Re: Fedora 33 System-Wide Change proposal: swap on zram

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 15:11 +0100, Richard W.M. Jones wrote: > On Fri, Jun 05, 2020 at 01:50:29AM -0600, Chris Murphy wrote: > > On Fri, Jun 5, 2020 at 12:33 AM Milan Crha > > wrote: > > > > > > On Thu, 2020-06-04 at 16:30 -0400, Ben Cotton wrote:

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 12:27 +, devel-requ...@lists.fedoraproject.org wrote: > > Date: Fri, 5 Jun 2020 08:26:04 -0400 > From: Neal Gompa > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > Change > To: Development discussions related to Fedora > > Cc: Vitaly Zai

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 15:56 +, devel-requ...@lists.fedoraproject.org wrote: > Send devel mailing list submissions to > devel@lists.fedoraproject.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > devel-requ...@lists.fedoraproject.org >

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

I would also add that Clang/LLVM is missing some of the newer C language revisions at least for the pppc64le target. Both IEEE/ISO _Float128 and _Decimalxx support is missing. Ie the type is not supported or if supported basic arithmetic and math.h support is missing. Also finding bugs for in-lin

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 10:51 +, devel-requ...@lists.fedoraproject.org wrote: > Send devel mailing list submissions to > > Date: Fri, 05 Jun 2020 12:42:03 +0200 > From: Florian Weimer > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > Change > To: Igor Raits > Cc: Dev

Re: Is the name of this review package OK?

On 05. 06. 20 15:55, Richard W.M. Jones wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1825456 Proposed package name is "libvirt-test-api". Upstream name is "libvirt-test-API". It is, very very loosely, a Python 3 API and the package includes Python development files. But on the other han

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 05/06/20 12:46 +0200, Vitaly Zaitsev via devel wrote: On 05.06.2020 09:52, Kevin Kofler wrote: I am opposed to this change. Chromium and Firefox build fine with GCC. I think that a distribution should be built with a consistent toolchain wherever possible. Clang is much better than GCC nowa

[Test-Announce] Fedora-IoT 33 RC 20200605.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora-IoT 33 RC 20200605.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_pl

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 06/05/2020 09:15 AM, Steven Munroe wrote: > I would also add that Clang/LLVM is missing some of the newer C > language revisions at least for the pppc64le target. > > Both IEEE/ISO _Float128 and _Decimalxx support is missing. Ie the > type is not supported or if supported basic arithmetic and

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 10:51 +, devel-requ...@lists.fedoraproject.org wrote: > > Date: Fri, 5 Jun 2020 12:42:30 +0200 > From: Vitaly Zaitsev > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > Change > To: devel@lists.fedoraproject.org > Message-ID: <08a3d005-da6e-248f

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2020-06-05 at 11:15 -0500, Steven Munroe wrote: > I would also add that Clang/LLVM is missing some of the newer C > language revisions at least for the pppc64le target. > > Both IEEE/ISO _Float128 and _Decimalxx support is missing. Ie the >

Re: [Fedora-packaging] Let's standardize the way to disable tests during RPM build?

On 05. 06. 20 16:45, Tomas Orsava wrote: On 6/5/20 4:39 PM, Richard W.M. Jones wrote: On Fri, Jun 05, 2020 at 10:28:39AM -0400, Paul Wouters wrote: Or just a new option to rpmbuild that skips %check ? It exists already: rpmbuild --nocheck. It's not wired into the rest of the stack - eg. you c

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 16:23 +, devel-requ...@lists.fedoraproject.org wrote: > Date: Fri, 5 Jun 2020 11:15:39 -0500 > From: Steven Munroe > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > Change > To: devel@lists.fedoraproject.org > Message-ID: > > Content-Type

Re: devel Digest, Vol 196, Issue 58

On Fri, 2020-06-05 at 10:22 +, devel-requ...@lists.fedoraproject.org wrote: > Date: Fri, 5 Jun 2020 11:19:54 +0200 > > From: Jakub Jelinek > > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > > Change > > To: Development discussions related to Fedora > >

Re: [HEADS UP] F33 Boost 1.73.0 rebuilds starting in a side tag

On 05/06/20 09:00 -0500, Richard Shaw wrote: Next problem... /usr/include/boost/geometry/index/detail/rtree/node/variant_visitor.hpp:51:25: error: no matching function for call to 'apply_visitor(boost::geometry::index::detail::rtree::visitors::insert, WireJoiner::PntGetter>::members_holder, boos

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 10:22 +, devel-requ...@lists.fedoraproject.org wrote: > Date: Fri, 5 Jun 2020 11:42:36 +0200 > > From: Vít Ondruch > > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > > Change > > To: devel@lists.fedoraproject.org > > Message-ID: <0f69dde

Fedora-IoT-33-20200605.0 compose check report

Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Failed openQA tests: 1/13 (x86_64) Old failures (same test failed in Fedora-IoT-33-20200604.0): ID: 612411 Test: x86_64 IoT-dvd_ostree-iso iot_greenboot URL: https://openqa.fedoraproject.org/tests/612411 Passed openQA tests: 12/13 (x

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 14:57 +, devel-requ...@lists.fedoraproject.org wrote: > Date: Fri, 5 Jun 2020 07:56:57 -0700 > > From: Tom Stellard > > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > > Change > > To: Development discussions related to Fedora > >

Re: System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 14:11 +, devel-requ...@lists.fedoraproject.org wrote: > Date: Fri, 5 Jun 2020 14:16:58 +0100 > > From: Ian McInerney > > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > > Change > > To: Development discussions related to Fedora > >

Re: [HEADS UP] F33 Boost 1.73.0 rebuilds starting in a side tag

On Fri, Jun 5, 2020 at 11:43 AM Jonathan Wakely wrote: > On 05/06/20 09:00 -0500, Richard Shaw wrote: > The next error tells you the reason it couldn't be called: > > /usr/include/boost/variant/detail/apply_visitor_unary.hpp:46:1: error: > 'typedef void boost::static_visitor::result_type' is inac

Re: [HEADS UP] F33 Boost 1.73.0 rebuilds starting in a side tag

On 05/06/20 17:42 +0100, Jonathan Wakely wrote: On 05/06/20 09:00 -0500, Richard Shaw wrote: Next problem... /usr/include/boost/geometry/index/detail/rtree/node/variant_visitor.hpp:51:25: error: no matching function for call to 'apply_visitor(boost::geometry::index::detail::rtree::visitors::ins

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 07:58 +, devel-requ...@lists.fedoraproject.org wrote: > > Date: Fri, 05 Jun 2020 09:52:09 +0200 > From: Kevin Kofler > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > Change > To: devel@lists.fedoraproject.org > Message-ID: > Content-Type: tex

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

* Jeff Law: > I'm not suggesting switching the default. I'm suggesting the compiler > choice be made by the upstream projects. Some prefer LLVM, others > prefer GCC. Fedora should get out of the way and use the same tools > that the upstream projects are using. Do we know how many upstream pro

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 6/5/20 12:31 PM, Jeff Law wrote: On Fri, 2020-06-05 at 16:23 +, devel-requ...@lists.fedoraproject.org wrote: Date: Fri, 5 Jun 2020 11:15:39 -0500 From: Steven Munroe Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change To: devel@lists.fedoraproject.org Messag

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

* Ben Cotton: > https://fedoraproject.org/wiki/Changes/CompilerPolicy > > == Summary == > Fedora has historically forced packages to build with GCC unless the > upstream project for the package only supported Clang/LLVM. This > change proposal replaces that policy with one where compiler selectio

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 19:23 +0200, Florian Weimer wrote: > * Jeff Law: > > > I'm not suggesting switching the default. I'm suggesting the compiler > > choice be made by the upstream projects. Some prefer LLVM, others > > prefer GCC. Fedora should get out of the way and use the same tools > > th

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On Fri, 2020-06-05 at 19:31 +0200, Florian Weimer wrote: > * Ben Cotton: > > > https://fedoraproject.org/wiki/Changes/CompilerPolicy > > > > == Summary == > > Fedora has historically forced packages to build with GCC unless the > > upstream project for the package only supported Clang/LLVM. This

  1   2   >