Hi Simon, On 2/9/23 14:50, Simon McVittie wrote: > My understanding from the changelog is that the maintainer Daniel Baumann > first packaged a bunch of GNOME Shell extensions according to the GNOME > team's usual convention (one package per independent upstream project), > and then was asked by the ftp team to replace them with a single package > collecting together multiple unrelated extensions?
yes, that's correct. > If one of the bundled extensions isn't ready for a new GNOME Shell and > can't easily be ported, then "hold back all the bundled extensions" isn't > really an option: we are not going to delay a GNOME Shell upgrade just > because an extension isn't keeping up, because GNOME Shell is much more > important to the distribution than any individual extension. absolutely, yes; however.. > The options > would be to drop incompatible extensions from the bundled package, or > to remove the entire bundled package from testing until it can be made > compatible again. ..I don't think for this case it matters whetever an extension is part of an aggregated package or not: * if it's a standalone src+bin package, the extension would have an RC bug and would eventually be removed from testing until it's fixed. * if it's part of an aggregated package, the extension would be dropped from the aggregated package until it's fixed. so, basically same result from a testing users point of view wrt/ availability of the extension in the archive. Regards, Daniel