On Sun, Oct 23, 2016 at 01:18:54AM +0200, Marco d'Itri wrote: > On Oct 23, Mark Brown <broo...@debian.org> wrote:
> > Which was uploaded yesterday without warning which isn't exactly > > helpful, there's not even been a proposal from anyone working on this > > for how to fix it. I would expect that if something like this were > > going to be imposed it'd be imposed towards the start of the release > > cycle rather than at the very end. > We have been discussing switching to merged /usr for over two years and > there are just five broken packages left, all of them rarely used. My expectation is that the people working on a transition like this would be pushing it forwards - things get talked about for a long time often (and Debian is quite big so the fact that some people have been talking about it doesn't mean everyone knows), there's a difference between talking about something and it actually happening. In the case of merging / and /usr it's been talked about for pretty much as long as I've been involved in Debian but the change in bug severity was the first indiciation I'd had that there was a chance of it actually being implemented. I'd have expected to at least have seen something going round saying that the transition was mostly complete and that there were only a few packages blocking it prior to just dumping a new version of deboostrap in unstable and rendering everything instabuggy. Most similar transitions have come along with patches (usually quite early on in the process) though it's not always possible, in this case I suspect it is. > This bug has been open since january and you never asked for help > (actually you hinted that yp-tools was useless anyway as is). I didn't ask for help because I just don't care about this transition, in part because as I indicated there's no way to really use yp-tools at present so it's the least of anyone's worries so when I'm spending time on these packages it'd be on the things that are required to make the package more practically useful. > We (people interested in merged /usr) are not going to waste another > release cycle. That doesn't mean it's a good idea to just implement the transition quite late in the release cycle without making any effort to coordinate with the affected packages. Some advance warning would have made all the difference here.
signature.asc
Description: PGP signature
