Bug#914897: affects private debs too
On 29/11/2018 17:13, Adam Borowski wrote:
> Andreas Henriksson wrote:
>> On Wed, Nov 28, 2018 at 03:14:20PM +0000, Ian Jackson wrote:
>>> Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled merged /usr by default"):
>> [...]
>>>> I'd suggest that this should be fixed by not shipping any packages that
>>>> aren't built on buildds.
>>>
>>> It would be quite a radical departure for Debian to no longer support
>>> "I built this package for my mate to install on their computer".
>>
>> For the case of locally built binaries, bringing any problem
>> that usrmerge would hit to the light would be preferable.
>
> Any checks you can do may test only packages that reached the Debian
> archive. We can discipline DDs, be it by requiring source-only, or by
> catching misbuilt packages, but we can't do anything for local packages.
>
> And these in a good part are not based on Debian sources.
>
> I for one use a .deb package to distribute my .bashrc to machines under my
> control. Joe from a derivative named Debuntituan provides an
> uber-proprietary-drivers package to his users. Any PPA. A company-wide
> repo. Etc, etc.
>
> We'd need to have dpkg-dev Conflict: usrmerge, and even that won't catch
> systems installed with recent versions of debootstrap.
>
> Thus: sorry but there is no way we can possibly support usrmerged and
> non-usrmerged systems at the same time. Usrmerge is not viable without a
> flag day.
>
>
> So it's up to you to decide:
> * should there _be_ a flag day?
> * should that flag day happen before Buster?
>
> If the answer to the second question is "no", the debootstrap change
> needs to be at least temporarily reverted.
With my release team hat on: if we have a flag day to switch to merged-/usr,
that should wait for after buster, and it should happen in the early stages of a
release cycle, not right before the freeze.
Also if you ask me, I think debootstrap should default to non-merged /usr for
the time being. That change is only causing trouble.
As Julien said, we should aim to have source-only uploads everywhere and forbit
or discard binaries from the uploads. But that doesn't prevent this change from
being reverted. Both things should happen, and they don't depend on each other.
Cheers,
Emilio
Reply to: