From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: Jessie: Host configuration leakage around apt-get
Date: Wed, 28 Jun 2017 19:53:11 +0200 [thread overview]
Message-ID: <e18a70d0-dcbc-d53e-a2d2-75d296172d54@siemens.com> (raw)
In-Reply-To: <20170628161026.GB32130@yssyq.radix50.net>
On 2017-06-28 18:10, Baurzhan Ismagulov wrote:
> On Tue, Jun 27, 2017 at 07:38:46PM +0200, Jan Kiszka wrote:
>> for days, I was hunting a nasty bug around multistrap mystically failing
>> in a jessie docker container while working fine in a stretch container
>> as well as a regular jessie VM installation. It turned out that the
>> docker image (debian:jessie-slim) contains
>>
>> /etc/apt/apt.conf.d/docker-gzip-indexes
>>
>> which disables the unpacking of packages index files after downloading.
>> Due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774698, this
>> also affected the multistrap call of apt-get. So, everyone trying to
>> build Isar images with jessie can run into this bug. Maybe we should
>> detect the affect version (<2.2.1) and warn at least?
>
> Good idea, thanks for the analysis! I've opened
> https://github.com/ilbers/isar/issues/16.
>
I can try writing a patch. Do you have a suggestion where to hook up
this check best?
>
>> Considering to pull in 2.2.9 from stretch into my builder image now...
>
> Did this help with gzipped indexes?
>
Yep, see my patch for the kas docker image.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2017-06-28 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 17:38 Jan Kiszka
2017-06-28 16:10 ` Baurzhan Ismagulov
2017-06-28 17:53 ` Jan Kiszka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e18a70d0-dcbc-d53e-a2d2-75d296172d54@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox