[Piuparts-devel] Bug#863089: Bug#863089: Please provide post-processed logs output for manpages.d.o
holger at layer-acht.org
Wed May 31 09:47:36 UTC 2017
On Wed, May 31, 2017 at 11:32:46AM +0200, Michael Stapelberg wrote:
> The fact that these manpages are included at all is what the
> slave-alternative handling got us :)
> > ok, I'll request this once we got closer… (see below)
> Thanks :).
done (as you know, but for the record of this bug…)
> The code is authenticated via HTTPS. If you don’t trust GitHub and/or the
> TLS certificate infrastructure, then we should find an alternative.
I dont trust GitHub, or rather, it's bad enough trusting alioth, I dont want
to also trust Github… (and TLS, no…)
(we should probably rather trust signed tags, but anyway, as we dont have
that I would prefer to only trust one repo…)
> > Also, I don't expect debiman-piuparts-distill to change very often, do you?
> Agreed, most likely it will not change very often.
> > does the code need to live in github.com/Debian/debiman at all? One copy
> > in the piuparts repo should be enough, or?
> That’s correct; I was referring to code that is shared between different
> debiman components. Specifically,
> But, if the conclusion is that debiman-piuparts-distill should live in the
> piuparts repo, we can duplicate that code. I don’t expect it to change
I think I would really prefer the code to live in the piuparts repo.
Or alternativly, life in your repo and then we deploy it on demand, but not
everyday. Having it in the piuparts repo would be easier for deployments, but
I can see how its a bit more hassle for you to maintain the code in another
repo. But then, I know how to be very liberal to accept your code changes to
your code in our piuparts repo :)
Patches welcome! :-D
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 811 bytes
Desc: Digital signature
More information about the Piuparts-devel