Hi,

Quoting Ian Jackson (2016-08-19 14:04:40)
> And to those others who replied, I would like to point out that answers of
> the form "oh no surely they don't" to questions like Johannes's can be
> harmful.

I read their answers as: "I don't think it is necessary for sbuild to support a
distribution that is so old that it doesn't receive any official or unofficial
support anymore".

> > I want to be able to build backports to old installations.
> 
> Is there some other way for me to be able to do this which doesn't
> involve all that annoying work ?
> 
> What would happen if we took older sbuild and arranged for it to be
> coinstallable with the new sbuild, so that one could use sbuild-old
> for the old chroots ?
> 
> Or perhaps there are other ways of doing this.  Sadly I don't think
> running a jessie chroot containing a lenny chroot (or whatever) is a good
> plan...

Old sbuild will not help you. The problem is mainly, that older chroots contain
an apt installation that has no support for the [trusted=yes] option in
sources.list. This in turn means that it is required of subild to sign the
internal dummy repository. This signing happens with a private/public key pair
that is generated by the host running sbuild. The challenge is, to make it such
that the keys generated by gnupg on the host can be consumed by older gnupg
inside the chroot. I did lots of work in this direction already by for example
changing the export format for the keys generated by $(sbuild-update --keygen)
but apparently there are still bugs around as recently reported by weasel via
IRC.

Since I sank lots of time into this issue of cross-gpg-version-compatibility
already I was wondering if it is worth to spend more time on it than I already
have or whether I can just rip out the whole key generation and consumption
part. It is not needed anymore for any Debian release after squeeze (thanks to
newer apt).

If there are still users who plan to build for squeeze on sbuild from stretch,
help to keep compatibility for squeeze would be very much appreciated.

Thank you!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to