[Piuparts-devel] Bug#850917: Bug#850917: Please export /var/lib/dpkg/alternatives content after installation

[Michael Stapelberg]

Thanks for the quick reply. Answers inline:

On Wed, Jan 11, 2017 at 2:06 AM, Holger Levsen <holger at layer-acht.org> wrote:
> Hi Michael,
>
> thanks for your bug report, this seems like a viable idea to me.
>
> On Wed, Jan 11, 2017 at 09:27:56AM +0100, Michael Stapelberg wrote:
>> …followed by making /tmp/export.tar.bz2 available as
>> <suite>_<binarypkg>_<version>_alternatives.tar.bz2, e.g.
>> stretch_vim_2:8.0.0134-1_alternatives.tar.bz2.
>
> except that the suite should not be part of that filename, but rather be
> part of the path, so that next to
> https://piuparts.debian.org/stretch/pass/vim_2:8.0.0134-1.log
> there would be
> https://piuparts.debian.org/stretch/pass/vim_2:8.0.0134-1.alternatives.tar.bz2

Sure, the suite can go into the path name :). One question: is it
necessary for the piuparts status to be reflected by the path? I.e.,
for my purposes, I don’t really care about whether the other checks
succeeded, I’m only interested in the alternatives tarball.

>
>> Please consider implementing this feature request. Let me know if this
>> is something where you’d like some assistance, but it seems to me that
>> the complexity lies in actually changing piuparts, which is something
>> where I don’t have any experience.
>
> yes, we like some assistance as in patches here. First, you'd need to
> get piuparts.py to actually produce that tarball and then it needs to be
> copied from the slave to the master… (I can probably hint you where the
> relevant code lives…)
>
> piuparts maintenance is somewhat understaffed these days… (constant and
> onetime) help is much welcome!

Alright. I’ll take a stab at this later today hopefully. Will let you
know how it goes.

>
>
> --
> cheers,
>         Holger



-- 
Best regards,
Michael