Hi Thorsten, > On 8 Oct 2016, at 21:52, Thorsten Glaser <t...@mirbsd.de> wrote: > > James Clarke dixit: > >> I agree, this is bad. However, if this is only affecting sarge chroots, > > I never said that. That’s just where I noticed it.
Ok, my bad, that's just how I read it. > Every time anything listed in REMOVEPACKAGES has a different state > between the host system and the chroot, and when the chroot’s distro > doesn’t actually have that package at all, this makes --update fail. I'm surprised I've never run into this, but I will take your word for it. >> If it's problematic for wheezy+ chroots, please feel free to change >> the severity back to serious. > > It’s about 50% likely to do that. > > I can’t construct a realistic case right now, but I think if you > add libeatmydata1 to REMOVEPACKAGES, an --update of a wheezy sans > backports chroot will fail. > > Honestly, just quickly upload a fix and let’s not hang ourselves > up on the severity. That’s up to Mattia, but the severity change was not a reflection of wanting to delay the fix more than necessary. Regards, James
