From: Alexander Smirnov <asmirnov@ilbers.de>
To: Gernot Hillier <gernot.hillier@siemens.com>, isar-users@googlegroups.com
Subject: Re: still Debian 9.1 because of ignoring "stretch-updates" (and security patches)?
Date: Thu, 16 Nov 2017 12:27:05 +0300 [thread overview]
Message-ID: <a6c21613-82ab-0309-d81c-eb6f969371fe@ilbers.de> (raw)
In-Reply-To: <f863791e-4fc8-1874-7f45-75d3ec1cb594@siemens.com>
Hi Gernot!
On 11/16/2017 12:17 PM, Gernot Hillier wrote:
> Hi there!
>
> I was quite confused why our Isar version still gives me a Debian 9.1
> image (according to /etc/debian_version) while Debian 9.2 is released
> more than a month ago.
>
> I finally found that we currently only install packages from
> distribution "stretch" which has nearly all packages from 9.2, but still
> provides old "base-files" including debian_version from 9.1.
>
> (I installed against deb.debian.org, not our internal mirror.)
>
> After adding "stretch-updates" to sources.list, I got updates of only
> two packages: "base-files" and "tzdata" - et voilà, we have Debian 9.2.
>
> After additionally adding "stretch/updates" from security.debian.org, I
> got updates to openssl, dnsmasq and wget.
>
> While still being puzzled why Debian adds this layer of confusion to the
> world, we should probably honor this and give the user an up-to-date
> image from all three sources, no?
>
> Or did we make some mistake in Isar setup?
I can't imagine what could be wrong in Isar in context of pure Debian
packages. Everything related to base system is handled by multistrap
which performs 'apt-get' from specified in config file upstream mirrors.
Probably user should add all these 3 mirrors to multisrtrap config in
his meta.
Alex
next prev parent reply other threads:[~2017-11-16 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 9:17 Gernot Hillier
2017-11-16 9:27 ` Alexander Smirnov [this message]
2017-11-21 12:55 ` Gernot Hillier
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=a6c21613-82ab-0309-d81c-eb6f969371fe@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=gernot.hillier@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