Re: Heads up: Python 3.7 rebuild in progress

I spent a bit of time last night trying to fix the python-pyopengl build failure. Here's where I got to: It is the accelerate module which is failing to build when compiling the .c files that ship with the source tarball. These are generated upstream by Cython from the shipped .pyx files. Build fa

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Tue, Jun 26, 2018 at 1:47 PM, Lennart Poettering wrote: > The logic I am working on is built as an add-on to the boot loader > spec: I simply encode the counter in the file name of the snippet, so > that counting down and marking an entry as good is a simple rename > operation, which has a goo

Re: F29 System Wide Change: Make BootLoaderSpec the default ['id' field]

On Tue, Jun 26, 2018 at 5:36 PM, Javier Martinez Canillas wrote: > On Tue, Jun 26, 2018 at 4:33 PM, Peter Jones wrote: [snip] >> >>> It attempts to sort using the id field, and if this isn't defined >>> other fields are used as fallback in the following order: version, >>> title, linux. >> >> Y

FYI: Potential delay in toolchain readiness for 64-bit POWER LE transition to 128-bit IEEEE long double.

FYI. As part of the glibc 2.28 development upstream plans to change the ppc64le default ABI for long double from "IBM long double" to "IEEE 128-bit long double", this change is documented here: https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition We have a potential problem here i

Re: F29 System Wide Change: Make BootLoaderSpec the default ['id' field]

On Di, 26.06.18 10:33, Peter Jones (pjo...@redhat.com) wrote: > On Tue, Jun 26, 2018 at 03:46:59PM +0200, Javier Martinez Canillas wrote: > > > That raises two questions: > > > 1. Why isn't just the bls-snippet filename used as the key? It's > > >necessarily unique and should be usable for the

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Di, 26.06.18 12:51, Chris Murphy (li...@colorremedies.com) wrote: > I'm making it about systemd-boot because it is literally the only > bootloader that can't read any file system that the firmware can't > already read; it's a UEFI only bootloader and it definitely sounds > like the spec is writ

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Tue, Jun 26, 2018 at 1:33 PM, Peter Jones wrote: >> > There's a lot of clouds going to uEFI now >> >> [citation needed] > ... >> I got sort of lost in Azure versus Hyper-V and gen1/gen2 - apparently >> Hyper-V likes >> UEFI and supports secure boot but Azure may not or something? > > Ignoring

Re: F29 System Wide Change: Make BootLoaderSpec the default

> > There's a lot of clouds going to uEFI now > > [citation needed] ... > I got sort of lost in Azure versus Hyper-V and gen1/gen2 - apparently Hyper-V > likes > UEFI and supports secure boot but Azure may not or something? Ignoring the question of how many is a lot, I think you may just be dis

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Tue, Jun 26, 2018, at 11:48 AM, Peter Robinson wrote: > There's a lot of clouds going to uEFI now [citation needed] In my brief google searches: AWS: https://forums.aws.amazon.com/thread.jspa?threadID=155626 GCE: https://groups.google.com/forum/#!topic/gce-discussion/OD_Zd_6YVbw DO: http

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Mon, Jun 25, 2018 at 11:22 AM, Kyle Marek wrote: > > /boot is already ext on Fedora. Why does anyone *need* to implement XFS > for GRUB? The use case is an XFS root filesystem, and /boot is just a directory. There is no separate boot volume. ext4 is default for a volume mounted at /boot; bu

Re: change in -fpic handling?

On 06/26/2018 02:53 PM, Dave Love wrote: What has changed in the last month to affect building shared libraries in rawhide? I tried to rebuild libxsmm in rawhide, after changing the spec to use python2 explicitly, and it failed with /usr/bin/ld: build/intel64/libxsmm_main.o: relocation R_X86

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Mon, Jun 25, 2018 at 10:09 AM, Andrew Lutomirski wrote: > (d) It is useful to write to $BOOT from the bootloader to indicate > that we're trying to boot and again from the booted system to indicate > that the boot succeeded. > (g) The bootloader's driver for $BOOT should implement at least r

Re: F29 System Wide Change: Make BootLoaderSpec the default

On Mon, Jun 25, 2018 at 4:40 AM, Lennart Poettering wrote: > I am not sure why you are making this about systemd-boot. Let's just > focus on why (or why not) vfat is the best option for $BOOT. I'm making it about systemd-boot because it is literally the only bootloader that can't read any file s

Re: Heads up: Python 3.7 rebuild in progress

On 25.6.2018 15:45, Miro Hrončok wrote: On 19.6.2018 11:27, Miro Hrončok wrote: On 13.6.2018 15:14, Miro Hrončok wrote: I've just started to build the bootstrap sequence in a side tag (f29-python). I'm now mass rebuilding everything. Will do a couple of rounds before I will look at the log

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180625.0

On Tue, Jun 26, 2018 at 7:51 PM, wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 28.20180625.0 > Commit(x86_64): fbed0e26736fc189129f80e9547bfd > 71497377ca49f0cfd421f173667f5ea825 > Commit(aarch64): b5067e5e11d6a5b178b782e91fef80 > 820cc8ce04b1d57dc076a

Re: F29 System Wide Change: Make BootLoaderSpec the default

>> > And in my opinion, it's not simple to say: OK if you have this size >> > ESP to start, you get this layout, and if it's bigger you get this >> > other layout, and if it's BIOS you have this 3rd layout. > > Chris, I have to say I'm glad you're part of the Fedora community - your > input on this

Re: F29 System Wide Change: Make BootLoaderSpec the default ['id' field]

On Tue, Jun 26, 2018 at 4:33 PM, Peter Jones wrote: > On Tue, Jun 26, 2018 at 03:46:59PM +0200, Javier Martinez Canillas wrote: >> > That raises two questions: >> > 1. Why isn't just the bls-snippet filename used as the key? It's >> >necessarily unique and should be usable for the purpose of u

Re: change in -fpic handling?

On 2018-06-26, Dave Love wrote: > What has changed in the last month to affect building shared libraries > in rawhide? > > I tried to rebuild libxsmm in rawhide, after changing the spec to use > python2 explicitly, and it failed with > Did you check continuous integration results

[Modularity] Working Group IRC meeting minutes (2018-06-26)

Meeting started by langdon at 14:05:28 UTC. Minutes: https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2018-06-26-14.05.html Minutes (text): https://meetbot-raw.fedoraproject.org/teams/modularity_wg/modularity_wg.2018-06-26-14.05.txt Log: https://meetbot.fedoraproject.org/teams/m

Re: F29 System Wide Change: Make BootLoaderSpec the default ['id' field]

On Tue, Jun 26, 2018 at 03:46:59PM +0200, Javier Martinez Canillas wrote: > > That raises two questions: > > 1. Why isn't just the bls-snippet filename used as the key? It's > >necessarily unique and should be usable for the purpose of uniquely > >identifying the boot entry without creating

Fedora Atomic Host Two Week Release Announcement: 28.20180625.0

A new Fedora Atomic Host update is available via an OSTree update: Version: 28.20180625.0 Commit(x86_64): fbed0e26736fc189129f80e9547bfd71497377ca49f0cfd421f173667f5ea825 Commit(aarch64): b5067e5e11d6a5b178b782e91fef80820cc8ce04b1d57dc076a3dfaa7d490a17 Commit(ppc64le): 721a3c8fe5dedf496cd1c796d

Re: F29 System Wide Change: Make BootLoaderSpec the default ['id' field]

On Mon, Jun 25, 2018 at 6:14 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Jun 18, 2018 at 04:40:41PM +0200, Ondřej Lysoněk wrote: >> On 14.6.2018 12:06, Jan Kurik wrote: >> I noticed the official spec defines a field named "machine-id". AFAICS, >> GRUB2 doesn't implement that option, but it su

[copr] follow Fedora branching by default?

Hi, there was an idea to turn on the "Follow Fedora branching" feature in Copr by default (for newly created copr projects). That feature automatically creates new fedora-NN-* chroots from fedora-rawhide-* chroots (at Fedora branching time), and "forks" the related builds (so the packages don't ha

Re: F28's "ImprovedLaptopBatteryLife" causing USB issues?

On Mon, Jun 25, 2018 at 2:29 PM, Hans de Goede wrote: > Hi, > > On 25-06-18 13:26, Radka Janekova wrote: > >> ref: https://fedoraproject.org/wiki/Changes/ImprovedLaptopBattery >> Life#Current_status >> > "Enable USB autosuspend for USB bluetooth receivers by default. If all >> other USB devices

change in -fpic handling?

What has changed in the last month to affect building shared libraries in rawhide? I tried to rebuild libxsmm in rawhide, after changing the spec to use python2 explicitly, and it failed with /usr/bin/ld: build/intel64/libxsmm_main.o: relocation R_X86_64_PC32 against symbol `libxsmm_crc32_u64'

Re: Prioritizing ~/.local/bin over /usr/bin on the PATH

- Original Message - > From: "Sorin Sbarnea" > To: "Miro Hrončok" > Cc: "Development discussions related to Fedora" > > Sent: Tuesday, May 29, 2018 11:19:02 AM > Subject: Re: Prioritizing ~/.local/bin over /usr/bin on the PATH > > I ended up creating > https://fedoraproject.org/wiki/

Unannounced soname bump: toxcore

Hello, I accidentally soname bumped toxcore from libtoxcore.so.2.2.0 to libtoxcore.so.2.3.0. It was a minor patch release and I didn't anticipate the soname change. Affected package are utox and qtox (rpmfusion). They will be rebuilt shortly. I don't expect anyone to be affected by it, since I

Re: New FESCo Meeting Time and Ticket Policy

Dne 25.6.2018 v 20:03 Till Maas napsal(a): > On Tue, Jun 19, 2018 at 01:18:04PM +0200, Vít Ondruch wrote: > >> Although still, the FESCo meeting agenda used to be place, where it was >> obvious, that something probably happened with the ticket and it needs >> FESCo (and possibly my) attention. Th

REMINDER: Fedora 29 Change Checkpoint: Proposal submission deadline (System Wide Changes) in one week

Hi everyone! The submission deadline for System Wide Change Proposals of Fedora 29 [1] is coming pretty soon - in one weeks on July 3rd. Please, submit your System Wide Changes by this deadline, earlier better. As the deadline applies for System Wide Changes it is always good to have most of Self