Adam Borowski writes:
> I see that we're debating the merits of merged-usr vs non-merged-usr, while
> expending lots of effort and filing bugs (requiring further urgent action of
> unrelated maintainers), for little gain.
There is no "urgent action" required (unlike, say, for the last glibc
update
I see that we're debating the merits of merged-usr vs non-merged-usr, while
expending lots of effort and filing bugs (requiring further urgent action of
unrelated maintainers), for little gain.
In the above, note that the debate vs effort touch different problems:
1. is usrmerge good?
vs
2. how t
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 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 Sun, 02 Dec 2018 at 21:04:55 +0100, Marc Haber wrote:
> The next debhelper change might choose to give / instead of /usr as a
> target directory by default, moving hundreds of megabytes from /usr to /
> over time.
I don't think anyone is proposing that. There's no reason why it would be
preferr
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 -
Marc Haber writes:
> The next debhelper change might choose to give / instead of /usr as a
> target directory by default, moving hundreds of megabytes from /usr to /
> over time. My question was about the distant future, and not the current
> snapshot of things.
If anything then /usr would be the
On Sun, 02 Dec 2018 at 19:54:39 +, Simon McVittie wrote:
> When installed on a merged /usr system:
Oops, of course this should have said:
.deb contains -> /bin/grep/usr/bin/perl
/bin/fooexists thanks to /bin symlink exists thanks to /bin symlink
/usr/bin/foo
Marc Haber writes:
> On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
>> Le samedi, 1 décembre 2018, 19.29:59 h CET Marc Haber a écrit :
>> > Will binaries move from /usr/bin to /bin? Or will binaries move from
>> > /bin to /usr/bin?
>>
>> A merged-/usr has a /bin → /usr/bin s
On Sun, Dec 02, 2018 at 07:54:39PM +, Simon McVittie wrote:
> I would encourage anyone with questions about the behaviour of merged and
> unmerged /usr systems to try them, either by building one chroot, container
> or VM with merged /usr and one without, or by building a chroot, container
> or
On Sun, 02 Dec 2018 at 20:16:10 +0100, Marc Haber wrote:
> On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
> > A merged-/usr has a /bin → /usr/bin symlink; so a .deb package unpacking
> > /bin/grep will make that binary end up in /usr/bin/grep; but the
> > /bin → /usr/bin syml
On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
> Le samedi, 1 décembre 2018, 19.29:59 h CET Marc Haber a écrit :
> > Will binaries move from /usr/bin to /bin? Or will binaries move from
> > /bin to /usr/bin?
>
> A merged-/usr has a /bin → /usr/bin symlink; so a .deb package
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'
16 matches
Mail list logo
