[Python-modules-team] Bug#830172: python-docker: fix autopkgtest in current git packaging

Andreas Henriksson andreas at fatal.se
Sat Oct 8 17:20:37 UTC 2016


Hello Ondrej (and python-docker maintainers),

Thanks for your quick followup.

On Fri, Oct 07, 2016 at 11:36:37PM +0200, Ondrej Novy wrote:
> Hi Andreas,
> 
> thanks for your contribution. I pushed it to git. Then I imported new
> upstream version, which introduces new deps - dockerpy-creds. I tried to
> create package for this simple Python module, but it
> needs docker-credential executable which i don't have and can't find it in
> Debian.

It seems this is what you're looking for:
https://github.com/docker/docker-credential-helpers

(FYI, docker-credential-secretservice is the name of the linux variant)

OTOH, I think this is proving to be a case of "perfect is the enemy
of good". We're failing to provide our users with usable software
because we're constantly digging up new blockers for updating.

We should just go back to the new 1.9 release (which there are no
blockers for uploading and allows us to move forward)!
(Uploading 1.9 instead of 1.10 also has the benefit of avoiding to
introduce more unmaintained software in the archive.)

(We've wasted enough time here and we'll be wasting more of our users
time if we can't manage to move forward before stretch freeze. I feel
strongly about this and in my opinion providing useless official
packages is in violation of the social contract where we promise to put
our users first. If we can't provide a usable version it would be much
better to be upfront about that and just tell our users to look
elsewhere directly instead of wasting time on the official debian
packages and finding out they're not providing solutions.)

> 
> I pushed all my changes done so far. Because this is not my package, I'm
> giving it up now. Paul/Tianon, can you continue with this update please?

If there's noone with interest I'm going to remind everyone of my
offer to NMU.

Please reply soon or I'll take the silence as an acknowledgement to go
ahead. A reply saying if you'd still have future intentions to maintain
the package or if I should just orphan it while doing an upload would be
much appreciated. 

Regards,
Andreas Henriksson



More information about the Python-modules-team mailing list