Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] support/docker: use a fixed Debian snapshot
Date: Tue, 6 Feb 2018 10:20:46 +0100	[thread overview]
Message-ID: <20180206092046.GA28439@scaer> (raw)
In-Reply-To: <2fc6c71c-c2f5-9c90-e111-de25bde185eb@mind.be>

Arnout, All,

On 2018-02-06 09:52 +0100, Arnout Vandecappelle spake thusly:
> On 04-02-18 15:44, Yann E. MORIN wrote:
> > Since we're now using a specific base image tag, we need to also use a
> > specific, stable repository to get additional packages from for this
> > image.
[--SNIP--]
> > diff --git a/support/docker/apt-sources.list b/support/docker/apt-sources.list
> > new file mode 100644
> > index 0000000000..789fb8fc17
> > --- /dev/null
> > +++ b/support/docker/apt-sources.list
> > @@ -0,0 +1,4 @@
> > +# Latest just before 20171210T000000Z:
> > +deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/20171209T220346Z/ stretch main
> 
>  AFAIU, snapshot should resolve any date to the latest available snapshot, so
> http://snapshot.debian.org/archive/debian/20171210T000000Z/ should work as well
> here. It should redirect to exactly the same URLs.

Yeah, I knew about the latest-prior-to-given-date rule, but see below...

> Note thought that this
> doesn't work for the top-level, only for a specific release (because they are
> snapshotted at different times). So just clicking on the URL above won't work,
> but if you put dists/stretch after iti

For me, I even got http 500, and apt-get update would also fail from
time to time (about once for three).

That is indeed something I should have mentioned in the commit log.

> it redirects to
> http://snapshot.debian.org/archive/debian/20171209T220346Z/dists/stretch/

nd what's even weird ios that it now works, even for the debian-security
suite, which is not tagged at the same date:
    http://snapshot.debian.org/archive/debian-security/20171209T224618Z/dists/stretch/updates/

>  Anyway, OK for now, but something to keep in mind when it is bumped.

Yeah, I also would have preferred it, but as I said, it was sometimes
failing for me... :-/

Thanks for the feedback! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-02-06  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 14:44 [Buildroot] [PATCH 0/5] support/docker: generate reproducible base images Yann E. MORIN
2018-02-04 14:44 ` [Buildroot] [PATCH 1/5] support/docker: limit the number of layers Yann E. MORIN
2018-02-04 14:44 ` [Buildroot] [PATCH 2/5] support/docker: don't be silent when setting up Yann E. MORIN
2018-02-04 14:44 ` [Buildroot] [PATCH 3/5] support/docker: use a known base distribution Yann E. MORIN
2018-02-04 14:44 ` [Buildroot] [PATCH 4/5] support/docker: use a fixed Debian snapshot Yann E. MORIN
2018-02-06  8:52   ` Arnout Vandecappelle
2018-02-06  9:20     ` Yann E. MORIN [this message]
2018-02-04 14:44 ` [Buildroot] [PATCH 5/5] support/dockker: create and push tagged images Yann E. MORIN
2018-02-04 21:00 ` [Buildroot] [PATCH 0/5] support/docker: generate reproducible base images Peter Korsgaard
2018-02-05  7:21   ` Yann E. MORIN

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=20180206092046.GA28439@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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