On Sun, 27 May 2018 21:08:42 +0200
Raphael Hertzog wrote:
> If anything your argument would mean that we should have different default
> for the --merged-usr flag for different release. This might indeed be
> important if we want to make sure that recent debootstrap do not
Hi,
On Sun, 27 May 2018, Hideki Yamane wrote:
> On Tue, 22 May 2018 16:21:01 +0200
> Raphael Hertzog wrote:
> > I don't understand your question. The required fixes are in the version of
> > dpkg that is in stretch.
>
> I mean, if we try to create new stretch chroot with
On Tue, 22 May 2018 16:21:01 +0200
Raphael Hertzog wrote:
> I don't understand your question. The required fixes are in the version of
> dpkg that is in stretch.
I mean, if we try to create new stretch chroot with merged-usr,
it becomes to be NOT equal to stretch
On Sat, 19 May 2018, Hideki Yamane wrote:
> On Thu, 17 May 2018 11:37:32 +0200
> Laurent Bigonville wrote:
> > + * Enable merged-/usr by default again now that dpkg-shlibdeps is fixed
>
> Is it applied to from buster to sid?
> It maybe break the enviroment until stretch
On Thu, 17 May 2018 11:37:32 +0200
Laurent Bigonville wrote:
> + * Enable merged-/usr by default again now that dpkg-shlibdeps is fixed
Is it applied to from buster to sid?
It maybe break the enviroment until stretch release.
--
Regards,
Hideki Yamane henrich @
---
debian/changelog | 7 ++-
debootstrap | 4 ++--
debootstrap.8| 2 +-
3 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 3463794..48c0cfd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,14 @@
debootstrap
6 matches
Mail list logo