On Sun, 2019-03-31 at 05:13 +0000, Peter Robinson wrote:
On Sun, Mar 31, 2019 at 6:01 AM Kevin Fenzi kevin@scrye.com wrote:
On 3/30/19 9:50 PM, Peter Robinson wrote:
Great, thanks! I'll be keeping an eye on the composes to see if there are any issues.
Wasn't this disabled in the main Fedora branched compose? If so why would we want to enable it only on updates?
There's no updates in f30 indeed, but updates-testing should be there and available for testing. Nearer release we will enable updates and if we didn't enable this for them now we might well not remember to do so, so it seemed like a good idea to just do them both.
I was referring to commits 6c392f16 and 96adf9a in pungi-fedora, if it's disabled in the base fedora repo why enable it in updates/testing?
Hey Peter, the zchunk metadata generation was disabled in the base repo because of a bug that popped up in a combination that the compose process happened to hit: using a single baseurl and downloading a zchunk file with tens of thousands of chunks on a slow processor.
The bug has been fixed with updates to both zchunk and libcurl (see https://bugzilla.redhat.com/show_bug.cgi?id=1690971) and it shouldn't affect beta users because the number of chunks in updates and updates- testing is a magnitude lower than the base repo.
*However*
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.
Jonathan