On 13 February 2016 at 00:12, Michael D wrote:
> The upstream packaging is located here:
> https://github.com/docker/docker/tree/master/hack/make/.build-deb
>
> Aside from bundling all the depends into the source tree it seems ok.
As Dmitry's mentioned, the blocker isn't the
The upstream packaging is located here:
https://github.com/docker/docker/tree/master/hack/make/.build-deb
Aside from bundling all the depends into the source tree it seems ok.
^Michael
On 13 February 2016 at 19:03, Dmitry Smirnov wrote:
> On Sat, 13 Feb 2016 07:11:36 AM
On Sat, 13 Feb 2016 07:11:36 AM Michael D wrote:
> I'll take a look at the packaging process
Thanks.
> Since upstream already produces Debian packages, it can't be too difficult
> to apply the Debian changes.
I couldn't find upstream debian packaging sources but I have impression that
they
On Sat, 13 Feb 2016 08:12:57 AM Michael D wrote:
> The upstream packaging is located here:
> https://github.com/docker/docker/tree/master/hack/make/.build-deb
I see... Thank you.
--
All the best,
Dmitry Smirnov.
---
It is a mistake to try to look too far ahead. The chain of destiny can only
On Sat, 13 Feb 2016 06:15:34 AM Michael D wrote:
> Seconding this, 1.10.1 was just released. Quite disappointing to see the
> Debian packages so far behind :(
Please be patient or consider helping us. Every new release of Docker is
quite disruptive as every we have to package heaps of its new
Sorry about the subject, not really familiar with replying to a bug that
isn't already in my mailbox.
I'll take a look at the packaging process. Since upstream already produces
Debian packages, it can't be too difficult to apply the Debian changes.
On 13 Feb 2016 18:00, "Dmitry Smirnov"
Package: docker.io
Version: 1.8.3~ds1-2
Severity: normal
Dear Maintainer,
The 1.9.0 release introduces support for `docker build` environment
variables that are not persisted. This should finally solve all my
"build behind a proxy" issues.
See
7 matches
Mail list logo