Re: Upgrade to F30 gone wrong

2019-05-04 Thread Chris Murphy
On Sat, May 4, 2019 at 2:50 PM Sam Varshavchik wrote: > > Chris Murphy writes: > > > This bug itself was expected to be an edge case, that not many users > > would be affected, in that not many would have a stale Fedora 20 or > > older bootloader. Surely 'grub2-install' would have been manually ru

Re: Enable dmarc mitigations

2019-05-04 Thread Vitaly Zaitsev via devel
Hello, Stephen J. Turnbull. Sun, 5 May 2019 05:58:48 +0900 you wrote: > As a Mailman developer, I > will strongly oppose turning on user choice by default because my > constituents are list owners, not subscribers. But that implies it > would be rarely available. That's why it's time to deprec

Re: Enable dmarc mitigations

2019-05-04 Thread Stephen J. Turnbull
Florian Weimer writes: > Based on some reports, I don't think this is how the Gmail > implementation works. It will discard mailing list mail for senders > with a DMARC policy that does not set p=reject, too. Based on conversations with GMail developers, that has nothing to do with DMARC, tho

Re: Enable dmarc mitigations

2019-05-04 Thread Stephen J. Turnbull
Vitaly Zaitsev via devel writes: > I think it should be an option in mailman's settings. Each user can > enable or disable mitigations for his email address. Patches welcome at GNU Mailman. Potential time waste warning: The list owner must have the choice whether to delegate the choice to subs

Re: module load inside rpmbuild inside docker

2019-05-04 Thread Orion Poplawski
On 5/3/19 4:00 PM, Christoph Junghans wrote: Hi, I wanted to bump the legion package to 19.04.0 (https://bugzilla.redhat.com/show_bug.cgi?id=1705033), however for some reason all tests segfault with openmpi (https://koji.fedoraproject.org/koji/taskinfo?taskID=34577005), so I reported this upstre

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Sam Varshavchik
Chris Murphy writes: This bug itself was expected to be an edge case, that not many users would be affected, in that not many would have a stale Fedora 20 or older bootloader. Surely 'grub2-install' would have been manually run, or the user has done a recent clean install since Fedora 20, right?

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Chris Murphy
On Sat, May 4, 2019 at 12:44 PM Steve Grubb wrote: > > On Saturday, May 4, 2019 1:43:56 PM EDT Chris Murphy wrote: > > Currently, there is no way to determine who owns the bootloader on a > > BIOS computer, and therefore to avoid stepping on a bootloader that we > > don't own, we never update it.

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Chris Murphy
On Sat, May 4, 2019 at 12:31 PM Sam Varshavchik wrote: > > Chris Murphy writes: > > > Actually, that's a problem too. The stale bootloader problem goes back > > to an era where it was possible to install the bootloader into the > > first sector of the boot partition, and in those cases, /dev/sda1

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Steve Grubb
On Saturday, May 4, 2019 1:43:56 PM EDT Chris Murphy wrote: > On Sat, May 4, 2019 at 8:55 AM Steve Grubb wrote: > > > > > > > On Saturday, May 4, 2019 10:29:18 AM EDT Tom Hughes wrote: > > > > > On 04/05/2019 15:24, Steve Grubb wrote: > > > > > > > I upgraded from a fully updated F29 to F30 tod

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Sam Varshavchik
Chris Murphy writes: Actually, that's a problem too. The stale bootloader problem goes back to an era where it was possible to install the bootloader into the first sector of the boot partition, and in those cases, /dev/sda1 is actually valid. And again, no practical way to discover this automat

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Chris Murphy
On Sat, May 4, 2019 at 11:43 AM Chris Murphy wrote: > > On Sat, May 4, 2019 at 8:55 AM Steve Grubb wrote: > > This is what happens: > > > > # mount | grep boot > > /dev/sda1 on /boot type ext4 (rw,relatime,seclabel) > > [root ~]# grub2-install /dev/sda1 > > Installing for i386-pc platform. > > g

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Chris Murphy
On Sat, May 4, 2019 at 8:55 AM Steve Grubb wrote: > > On Saturday, May 4, 2019 10:29:18 AM EDT Tom Hughes wrote: > > On 04/05/2019 15:24, Steve Grubb wrote: > > > I upgraded from a fully updated F29 to F30 today. Upon reboot I see > > > > > > grub> > > > > > > This seems like a pretty major bug in

Re: Firefox certificate

2019-05-04 Thread Phil Wyett
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 2019-05-04 at 16:10 +0100, Richard W.M. Jones wrote: > I think I've been hit by this Firefox mess: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 > > or at least all the extensions in Firefox were just now disabled by an > incredi

Re: Firefox certificate

2019-05-04 Thread Peter Robinson
> > I think I've been hit by this Firefox mess: > > > >https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 > > > > or at least all the extensions in Firefox were just now disabled by an > > incredible coincidence. I know it's a Saturday and a public holiday > > weekend in a few countries, but

Re: Firefox certificate

2019-05-04 Thread Tom Hughes
On 04/05/2019 16:10, Richard W.M. Jones wrote: I think I've been hit by this Firefox mess: https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 or at least all the extensions in Firefox were just now disabled by an incredible coincidence. I know it's a Saturday and a public holiday weekend

Re: I wish to stop maintaining python2-defusedxml

2019-05-04 Thread Miro Hrončok
On 27. 04. 19 15:33, Miro Hrončok wrote: On 20. 04. 19 20:33, Miro Hrončok wrote: Only one package (fawkes-devenv) requires python2-defusedxml. It already has broken dependencies on mogodb-server and the source package (fawkes) doesn't build. fawkes-devenv is not required by any other packag

Firefox certificate

2019-05-04 Thread Richard W.M. Jones
I think I've been hit by this Firefox mess: https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 or at least all the extensions in Firefox were just now disabled by an incredible coincidence. I know it's a Saturday and a public holiday weekend in a few countries, but does anyone know if there

Docker and user namespaces on F30

2019-05-04 Thread Julien Enselme
Hi, I just updated to F30 and my docker setup with user namespaces doesn't work anymore. When I try to run: docker run -it --rm docker.io/php:7-fpm-alpine sh I get this error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Tom Hughes
Obviously I don't know your setup, but it's more normal for the bootloader to be installed at device level rather than at partition level, so you would want: grub2-install /dev/sda Obviously this should have been fixed as part of the upgrade process - that's why the page is called "common bugs"

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Steve Grubb
Hello, One detail is missing, see below On Saturday, May 4, 2019 10:54:49 AM EDT Steve Grubb wrote: > On Saturday, May 4, 2019 10:29:18 AM EDT Tom Hughes wrote: > > > On 04/05/2019 15:24, Steve Grubb wrote: > > > > > I upgraded from a fully updated F29 to F30 today. Upon reboot I see > > > > >

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Steve Grubb
On Saturday, May 4, 2019 10:29:18 AM EDT Tom Hughes wrote: > On 04/05/2019 15:24, Steve Grubb wrote: > > I upgraded from a fully updated F29 to F30 today. Upon reboot I see > > > > grub> > > > > This seems like a pretty major bug in some component somewhere. I don't > > think this is a recoverabl

Re: module load inside rpmbuild inside docker

2019-05-04 Thread Christoph Junghans
On Sat, May 4, 2019 at 5:30 AM Neal Gompa wrote: > > On Sat, May 4, 2019 at 7:26 AM Daniel Walsh wrote: > > > > On 5/3/19 6:00 PM, Christoph Junghans wrote: > > > Hi, > > > > > > I wanted to bump the legion package to 19.04.0 > > > (https://bugzilla.redhat.com/show_bug.cgi?id=1705033), however fo

Fedora Rawhide-20190504.n.0 compose check report

2019-05-04 Thread Fedora compose checker
Missing expected images: Atomichost qcow2 x86_64 Atomichost raw-xz x86_64 Compose FAILS proposed Rawhide gating check! 3 of 47 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQ

Re: Upgrade to F30 gone wrong

2019-05-04 Thread Tom Hughes
On 04/05/2019 15:24, Steve Grubb wrote: I upgraded from a fully updated F29 to F30 today. Upon reboot I see grub> This seems like a pretty major bug in some component somewhere. I don't think this is a recoverable bug for most people, meaning they would have to reinstall and possibly lose ever

Upgrade to F30 gone wrong

2019-05-04 Thread Steve Grubb
Hello, I upgraded from a fully updated F29 to F30 today. Upon reboot I see grub> This seems like a pretty major bug in some component somewhere. I don't think this is a recoverable bug for most people, meaning they would have to reinstall and possibly lose everything. What component is at fau

Fedora rawhide compose report: 20190504.n.0 changes

2019-05-04 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20190503.n.0 NEW: Fedora-Rawhide-20190504.n.0 = SUMMARY = Added images:5 Dropped images: 9 Added packages: 11 Dropped packages:2 Upgraded packages: 64 Downgraded packages: 0 Size of added packages: 15.65 MiB Size of dropped packages

Re: Problem with docker image for fedora:29

2019-05-04 Thread Dridi Boukelmoune
On Thu, May 2, 2019 at 5:31 PM Irina Boverman wrote: > > and this: > dnf install -y --allowerasing git zip unzip python krb5-workstation > java-1.8.0-openjdk java-1.8.0-openjdk-devel authconfig expect python3 > python3-requests python3-websockets pycurl which > Fedora 29 - x86_64 - Updates

libsbml-5.18.0

2019-05-04 Thread Antonio Trande
Hi all. libsbml-5.18.0 is coming on rawhide. Packages involved: COPASI-0:4.25.207-1.fc31.src libCombine-0:0.2.2-9.20180426git8902b68.fc30.src libCombine-devel-0:0.2.2-9.20180426git8902b68.fc30.i686 libCombine-devel-0:0.2.2-9.20180426git8902b68.fc30.x86_64 libnuml-0:1.1.1-14.fc30.src libsedml-1:0.

Re: How to install a mountpoint directory from an rpm?

2019-05-04 Thread Nico Kadel-Garcia
On Fri, May 3, 2019 at 9:13 PM jaltman wrote: > > > Say they're not, and need some other distinct setup. If it's > > standardized, as is seeming more apparent from the existing SELinux > > hooks, OK. Perhaps it's worth adding to the FSH, if it's such a > > standard usage? > > The use of /afs as th

Re: module load inside rpmbuild inside docker

2019-05-04 Thread Neal Gompa
On Sat, May 4, 2019 at 7:26 AM Daniel Walsh wrote: > > On 5/3/19 6:00 PM, Christoph Junghans wrote: > > Hi, > > > > I wanted to bump the legion package to 19.04.0 > > (https://bugzilla.redhat.com/show_bug.cgi?id=1705033), however for > > some reason all tests segfault with openmpi > > (https://koj

Re: module load inside rpmbuild inside docker

2019-05-04 Thread Daniel Walsh
On 5/3/19 6:00 PM, Christoph Junghans wrote: > Hi, > > I wanted to bump the legion package to 19.04.0 > (https://bugzilla.redhat.com/show_bug.cgi?id=1705033), however for > some reason all tests segfault with openmpi > (https://koji.fedoraproject.org/koji/taskinfo?taskID=34577005), so I > reported