On 2023-06-17, Holger Levsen wrote:
> On Sat, Jun 17, 2023 at 02:08:20PM -0700, Vagrant Cascadian wrote:
>> From what I recall looking at the log posted in irc it might be
>> sufficient to "apt autoremove usrmerge" after the fact, as usrmerge is
>> not really reversible... e.g. the /bin -> /usr/bin
On Sat, Jun 17, 2023 at 02:08:20PM -0700, Vagrant Cascadian wrote:
> From what I recall looking at the log posted in irc it might be
> sufficient to "apt autoremove usrmerge" after the fact, as usrmerge is
> not really reversible... e.g. the /bin -> /usr/bin and other symlinks
> should continue to
On 2023-06-17, Holger Levsen wrote:
> first: i've temporarily disabled testing usrmerge variation last
> night as this broke our builds, because the .buildinfo files vary
> (usrmerge installed or not), causing basically all builds to fail.
Ah well!
From what I recall looking at the log posted in
hi,
first: i've temporarily disabled testing usrmerge variation last
night as this broke our builds, because the .buildinfo files vary
(usrmerge installed or not), causing basically all builds to fail.
second: this has been happening since a few weeks, I still don't
get why this suddenly stopped
On 2023-06-15, Chris Lamb wrote:
> Holger Levsen wrote:
>
>> as soon as buildds are merged, varying trixie no longer makes
>> sense to me in either case
> […]
>> so should we stop testing usrmerge variations at all now?
>
> Thanks for taking this to the list. For 100% clarity, I understa
Holger Levsen wrote:
> as soon as buildds are merged, varying trixie no longer makes
> sense to me in either case
[…]
> so should we stop testing usrmerge variations at all now?
Thanks for taking this to the list. For 100% clarity, I understand
Holger's "at all" suffix to mean, "shall
hi,
so we are testing trixie now as well, and thus the following question came
up on #debian-reproducible:
helmut: until now, we have varied whether the usrmerge package is
installed, when testing bookworm, unstable & experimental. shall we
keep varying this for bookworm? shal
