On Monday, May 9, 2016 2:26:24 PM CDT Bruno Wolff III wrote:
On Mon, May 09, 2016 at 13:17:15 -0600,
Kevin Fenzi <kevin(a)scrye.com> wrote:
>Well, I guess we need to bring that up with QA, but right now the
>freeze process only uses bugzilla. So you would need to file a bugzilla
>bug and mention the PR or the like on it.
But how are the people doing the PRs going to know? Are they expected to
go look at the blocker bugs and see which are attached to PRs? That doesn't
seem good. So I guessing there would need to be some comment on the pull
request that says it's a blocker or freeze exception and points to the bug.
>Well, I was hoping to make labels for each ks, so you could watch for
>bugs with the label(s) you care about. If you saw a Xfce PR that came
>in and affects games, you could comment on it before it's merged.
That would help. It isn't always clear that some change is going to add
a lot of space (and some package updates do this as well) and it may not
be obvious until the compose is done, and there may not be time to do
another compose. Obviously, the earlier changes get made, the more time
there is to adjust to downstream affects of those changes.
For games, I'd be interested in an automated warning about size since it
happens so often. Though 4 GiB and 4.7 GB are starting to be less critical
as people aren't using FAT and DVDs as much now. Once your over 4 GB,
typically you need an 8GB USB flash drive, and Games is normally over 4 GB.
I don't think we want it to get too large though, for mirroring reasons. But
I do dislike having to make more cuts every release (except for the one
when we got xz kernel support).
There was a chaneg in lorax that switches the filesystem to UDF if it is
bigger than 4GiB so there should be no failures for going too big anymore.
Have you seen any recently? if so can you point me to them so we can get the
bug updated.
Dennis