[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#913229: release.debian.org: RC status of merged-/usr bugs?



Am 08.11.18 um 18:53 schrieb Simon McVittie:
> On Thu, 08 Nov 2018 at 15:50:48 +0000, Holger Levsen wrote:
>> On Thu, Nov 08, 2018 at 04:31:32PM +0100, Michael Biebl wrote:
>>> Wasn't there the idea to utilise the reproducible-build effort to detect
>>> binaries that differ depending on whether they were built in merged-usr
>>> environment or not?
> 
> <https://bugs.debian.org/901473>
> 
>> however, I would prefer a way which would prevent such
>> buggy binary packages from entering the archive in the first place...
> 
> Do you have a way in mind?
> 
> Are you saying that buildds should stick to unmerged /usr until we are
> more confident that merged /usr buildds will not misbuild packages, as
> I suggested? Or something else?

I'm basically with you on this.
I think we should stick with unmerged-usr on the buildds as the
resulting binaries are more likely to work with both merged and unmerged
usr setups (at least for the time being).
If we made merged-usr the default, even for upgraded systems, I wouldn't
worry as much. The current plan though afaik is to only have merged-usr
for newly deployed systems.

I'm well aware that we don't enforce source-only uploads yet, i.e.
rebuild everything. So we still might have binaries which are built
locally in a merged-usr setup. So this would only minimize the risk.

That's why I hope that we can more systematically detect any such issues
via reproducible-builds.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: