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
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)
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
>
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
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
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
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
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
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
11 matches
Mail list logo
