On Thu, 2016-09-08 at 15:36 +0200, Ansgar Burchardt wrote:
> Could you use the "Codename" field from Release to normalize the
> suite name? That should work even when the meaning of "stable"
> changes.
I've updated Marco's patch to include this change and prepared
everything as a Git series. The
On Thu, 7 Jul 2016 14:46:36 +0200 Marco d'Itri wrote:
> On Jul 05, Cyril Brulebois wrote:
>
> > For those wondering (and AFAICT) it seems the only issue here is
how to
> > handle multilib, since multiarch is “hidden†below usr/lib (in
> > usr/lib/ subdirectories).
> Indeed.
>
> > Actually,
How can we move forward with this?
On Aug 04, Marco d'Itri wrote:
> On Jul 07, Marco d'Itri wrote:
>
> > > > > first_stage_install () {
> > > > > + case $SUITE in
> > > > > + etch|etch-m68k|jessie|lenny|squeeze|wheezy) ;;
> > > > > + oldstable|stable) ;;
> > > > >
On Jul 07, Marco d'Itri wrote:
> > > > first_stage_install () {
> > > > + case $SUITE in
> > > > + etch|etch-m68k|jessie|lenny|squeeze|wheezy) ;;
> > > > + oldstable|stable) ;;
> > > > + *) setup_merged_usr ;;
> > >
> > > This means “debootstrap s
On Jul 05, Cyril Brulebois wrote:
> For those wondering (and AFAICT) it seems the only issue here is how to
> handle multilib, since multiarch is “hidden” below usr/lib (in
> usr/lib/ subdirectories).
Indeed.
> Actually, this means an architecture which isn't listed doesn't get
> extra paths, an
On Jul 05, Cyril Brulebois wrote:
> > + case $ARCH in
> > + hurd-*) return 0 ;;
> > + amd64) link_dir="lib32 lib64 libx32" ;;
[...]
> I don't think having to play catch up with src:glibc is a good idea.
> Can't that be determined automatically instead of hardcoding this
>
[ Adding kfreebsd and hurd porters to the loop. ]
Cyril Brulebois (2016-07-05):
> Marco d'Itri (2016-01-08):
> > +# Find out where the runtime dynamic linker and the shared libraries
> > +# can be installed on each architecture: native, multilib and multiarch.
> > +# This data can be verified by
On Tue, 2016-07-05 at 16:04 +0200, Cyril Brulebois wrote:
>
> > first_stage_install () {
> > + case $SUITE in
> > + etch|etch-m68k|jessie|lenny|squeeze|wheezy) ;;
> > + oldstable|stable) ;;
> > + *) setup_merged_usr ;;
I might be missing a part of the puzzle, but
Marco d'Itri (2016-01-08):
> +# Find out where the runtime dynamic linker and the shared libraries
> +# can be installed on each architecture: native, multilib and multiarch.
> +# This data can be verified by checking the files in the debian/sysdeps/
> +# directory of the glibc package.
> +#
> +#
On Jul 05, Andreas Henriksson wrote:
> I'm personally keen on seeing this move forward. As far as I'm aware
> there are no real blockers for this right now (since #817168 was recently
> fixed). If you're aware of any issues please tell me and I'd be happy
> to help out. Hoping to see us move forw
Hello!
On Fri, Jan 08, 2016 at 08:05:31AM +0100, Cyril Brulebois wrote:
> Christian PERRIER (2016-01-08):
> > To other D-I developers (not to say "to Kibi") : I'm very tempted to
> > give full confidence in Marco's proposals (this one and the one
> > related to devices creation), apply these patc
Christian PERRIER (2016-01-08):
> To other D-I developers (not to say "to Kibi") : I'm very tempted to
> give full confidence in Marco's proposals (this one and the one
> related to devices creation), apply these patches, upload and wait for
> input. Any objection?
I really think someone should c
And here comes the patch...
Please note that it must not be applied until it will be possible to
uninstall the usrmerge package from a system having installed
a reasonable selection of packages.
--
ciao,
Marco
diff --git a/debootstrap b/debootstrap
index 2a959bb..80d6a7a 100755
--- a/debootstr
Quoting Marco d'Itri (m...@linux.it):
> Package: debootstrap
> Version: 1.0.75
> Severity: normal
> Tags: d-i patch
> User: m...@linux.it
> Usertags: usrmerge
>
> After a discussion on #debian-boot it is my understanding that the d-i
> developers would prefer for debootstrap to create a merged /u
Package: debootstrap
Version: 1.0.75
Severity: normal
Tags: d-i patch
User: m...@linux.it
Usertags: usrmerge
After a discussion on #debian-boot it is my understanding that the d-i
developers would prefer for debootstrap to create a merged /usr
filesystem layout by default, and eventually add a d
15 matches
Mail list logo
