Ansgar Burchardt dijo [Wed, Dec 05, 2018 at 08:17:56AM +0100]:
> The Reproducible Builds project was so kind to help and now runs one
> build in a non-merged-/usr and a second build in a merged-/usr
> environment. Packages that hardcode the path to utilities, but would
> pick up the wrong one in a
Hi,
Hideki Yamane writes:
> On Sun, 2 Dec 2018 15:15:21 +
> Simon McVittie wrote:
>> > - What is the problem? (broken build for which packages? Just R?)
>>
>> The problem we're aware of is:
>>
>> Some packages auto-detect the absolute path to an executable (for example
>> bash or perl) an
Hi,
Thanks Simon, it's perhaps clear for me now.
On Sun, 2 Dec 2018 15:15:21 +
Simon McVittie wrote:
> > - What is the problem? (broken build for which packages? Just R?)
>
> The problem we're aware of is:
>
> Some packages auto-detect the absolute path to an executable (for example
> b
On Sun, Dec 02, 2018 at 11:31:13PM +0100, Marco d'Itri wrote:
> On Dec 02, Wouter Verhelst wrote:
>
> > One thing that has not been answered yet in this discussion (and if the
> > TC is to make a decision about it, I think it should be) is "why are we
> > doing this". That is, what is the problem
On Dec 02, Wouter Verhelst wrote:
> One thing that has not been answered yet in this discussion (and if the
> TC is to make a decision about it, I think it should be) is "why are we
> doing this". That is, what is the problem that usrmerge is meant to
> solve, and how does it attempt to solve it?
On Wed, Nov 28, 2018 at 01:49:45PM +, Ian Jackson wrote:
> Control: reassign -1 tech-ctte
>
> Dear Technical Committee. I don't know if you are all aware of the
> discussion surrounding this, so I will recap:
>
> Recently debootstrap was changed to do merged-/usr by default, so that
> /bin -
On Sat, Dec 01, 2018 at 10:21:50PM +, Simon McVittie wrote:
> gzip, icecc and mailagent were most recently built for buster on
> 2018-11-08, which might be long enough ago that the buster chroot was
> not merged-/usr?
right. I triggered their builds and now they are all shown as unreproducible
On Sun, 02 Dec 2018 at 21:21:40 +0900, Hideki Yamane wrote:
> - What is the problem? (broken build for which packages? Just R?)
The problem we're aware of is:
Some packages auto-detect the absolute path to an executable (for example
bash or perl) and hard-code it into their output (for example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On Fri, 30 Nov 2018 19:40:45 +0100
"Didier 'OdyX' Raboud" wrote:
> tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by
> default now, or are you OK letting the TC decide on this subject?
Hmm, I'm still considering what'
On Sat, 01 Dec 2018 at 17:18:35 +, Holger Levsen wrote:
> https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html
> lists these packages.
>
> what surprises me currently, are those 3 packages which are reproducible
> in buster (even though we also var
Hi,
Ansgar, thanks a lot for doing this!
On Sat, Dec 01, 2018 at 06:06:28PM +0100, Ansgar Burchardt wrote:
> So, I went through all reproducible build failures in unstable without
> notes and added notes for differences caused by building in merged-/usr
> vs non-merged-/usr packages. Together wi
Ansgar Burchardt writes:
> There were discussions about enabling this by default years ago, I
> don't think minor issues should be a reason to delay this change.
>
> Note that it has been delayed for after the stretch release as there
> were major issues back then (it was enabled by default for a s
On Fri, 2018-11-30 at 19:40 +0100, Didier 'OdyX' Raboud wrote:
> Dear Hideki, dear src:debootstrap maintainers,
>
> tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by
> default now, or are you OK letting the TC decide on this subject?
There were discussions about enabling
Dear Hideki, dear src:debootstrap maintainers,
tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by
default now, or are you OK letting the TC decide on this subject?
Longer version:
As you might be aware, #914897 (initially filed on src:debootstrap) has now
been reassigned
On 11/28/18 4:14 PM, Ian Jackson wrote:
> Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
> merged /usr by default"):
>> On 11/28/18 2:49 PM, Ian Jackson wrote:
>>> This is a special case of a general problem: buster systems with
Hello,
On Wed, Nov 28, 2018 at 03:14:20PM +, 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
> >
Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
merged /usr by default"):
> On 11/28/18 2:49 PM, Ian Jackson wrote:
> > This is a special case of a general problem: buster systems with
> > merged-/usr sometimes build packages which are broken
On 11/28/18 2:49 PM, Ian Jackson wrote:
> Recently debootstrap was changed to do merged-/usr by default, so that
> /bin -> /usr/bin etc.
>
> It was discovered that when this change took effect on the Debian
> buildds, the buildds started to build packages which do not work on
> non-merged-/usr sys
Julien Cristau writes:
> We already have a change queued to revert it for build chroots. I don't
> believe anything more is warranted at this stage.
Making the package behave differently on build chroots is adding a bug,
not fixing one.
Bjørn
Processing control commands:
> reassign -1 tech-ctte
Bug #914897 [debootstrap] debootstrap, buster: Please disabled merged /usr by
default
Bug reassigned from package 'debootstrap' to 'tech-ctte'.
Ignoring request to alter found versions of bug #914897 to the same values
previously set
Ignoring
ncreasing the
number of buster installs in the field which generate packages which
are broken on non-merged-/usr systemss.
I filed this bug against debootstrap but its maintainers do not agree:
Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
merged /usr by defau
On 11/28/18 1:07 PM, Ian Jackson wrote:
> Package: debootstrap
> Version: debootstrap/1.0.110
> Severity: serious
>
> Merged /usr is now the default in buster. As discussed on
> debian-devel, however, binary packages built on a merged-usr system
> are not installable on a non-merged-usr system.
Package: debootstrap
Version: debootstrap/1.0.110
Severity: serious
Merged /usr is now the default in buster. As discussed on
debian-devel, however, binary packages built on a merged-usr system
are not installable on a non-merged-usr system. I think we would like
ad hoc builds of packages from o
23 matches
Mail list logo
