On Sun, 2019-03-31 at 10:37 -0700, Kevin Fenzi wrote: > On 3/31/19 10:35 AM, Jonathan Dieter wrote: > > On Sun, 2019-03-31 at 10:28 -0700, Kevin Fenzi wrote: > > > On 3/31/19 1:56 AM, Jonathan Dieter wrote: > > > > On Sun, 2019-03-31 at 09:09 +0100, Jonathan Dieter wrote: > > > > > Due to an unrelated *major* bug in the latest librepo update ( > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1694411), I'd like to > > > > > request that we disable zchunk metadata generation in updates and > > > > > updates-testing until it's fixed. > > > > > > > > Just to be clear, until either: > > > > * We get a new updates compose out without zchunk metadata, or > > > > * The user sets zchunk=False in /etc/dnf/dnf.conf > > > > > > > > dnf update is broken for anybody using F30 > > > > > > > > Should I send an email to -devel explaining the above? > > > > > > Please do, perhaps devel-announce ? > > > > > > I have reverted things and am working on a new f30-updates-testing push. > > > There was a failed f29-updates-testing last night so I have to finish > > > that first, but hopefully we will have it out in a few hours. > > > > I've sent it out to devel-announce, but it was rejected as I'm not in > > the right group. Will I send it to you and let you forward it? > > Yeah, you have to be subscribed to devel-announce to post there... if > you just subscribe and resend it should go to moderation and I can pass it. > > Or if you want, just send it my way and I can post it... Ok, I've subscribed, sent the message, and it's awaiting moderation. Jonathan
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
