Hi,
Quoting Johannes Schauer (2016-08-17 19:24:51)
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
>
> I would like to remove some code from sbuild which is only useful for chroots
> with very old apt inside (specifically apt without support for [trusted=yes]
On Fri, Aug 19, 2016 at 03:36:37PM +0200, Johannes Schauer wrote:
> Hi,
>
> Quoting Ian Jackson (2016-08-19 14:25:52)
> > (Would it not be possible to generate the key inside the chroot? I
> > guess there are probably other problems with that.)
>
> that would require lots of time and entropy -
Hi,
Quoting Dimitri John Ledkov (2016-08-21 23:32:17)
> Surely old sbuild gpg key handing works correctly with gpg1. (Try gpg1
> first, if missing use gpg, assume it's classic gpg1)
>
> With new enough apt, no gpg key handing is needed.
>
> No support for gpg2 is needed, as any chroots with
Hello,
On 21 August 2016 at 22:05, Johannes Schauer wrote:
> Hi,
>
> Quoting Peter Samuelson (2016-08-21 11:45:35)
>> [Johannes Schauer]
>> > Old sbuild will not help you. The problem is mainly, that older
>> > chroots contain an apt installation that has no support for the
>>
Hi,
Quoting Peter Samuelson (2016-08-21 11:45:35)
> [Johannes Schauer]
> > 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.
>
> So if someone really needs this, I guess a
[Johannes Schauer]
> 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.
So if someone really needs this, I guess a workaround would be to
backport apt 1.0 to squeeze...?
Yes,
Hi,
Quoting Ian Jackson (2016-08-19 14:25:52)
> (Would it not be possible to generate the key inside the chroot? I
> guess there are probably other problems with that.)
that would require lots of time and entropy - unless somebody knows how to
trick gpg to generate a private/public key pair
Johannes Schauer writes ("Re: Does anybody plan to keep using sbuild with
Squeeze or older chroots?"):
> 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
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
On Fri, Aug 19, 2016 at 01:01:23PM +0100, Ian Jackson wrote:
> > does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> > chroots?
>
> Yes.
I'm actually not doing Debian packaging for it, but at work there still
are embedded machines running Lenny, where upgrading is simply
Ian Jackson writes ("Re: Does anybody plan to keep using sbuild with Squeeze or
older chroots?"):
> Johannes Schauer writes ("Does anybody plan to keep using sbuild with Squeeze
> or older chroots?"):
> > does anybody plan to use sbuild in Stretch with Deb
Johannes Schauer writes ("Does anybody plan to keep using sbuild with Squeeze
or older chroots?"):
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
Yes.
> I would like to remove some code from sbuild which is only useful
> for chroots wi
On Thu, Aug 18, 2016 at 12:19:02PM +0800, Paul Wise wrote:
> On Thu, Aug 18, 2016 at 1:24 AM, Johannes Schauer wrote:
> > does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> > chroots?
> ISTR folks on IRC mentioning they are still supporting clients on
> lenny and older.
at
On Thu, Aug 18, 2016 at 1:24 AM, Johannes Schauer wrote:
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
ISTR folks on IRC mentioning they are still supporting clients on
lenny and older.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, Aug 17, 2016 at 07:24:51PM +0200, Johannes Schauer wrote:
> does anybody plan to use sbuild in Stretch with Debian Squeeze or older
> chroots?
>
> I would like to remove some code from sbuild which is only useful for chroots
> with very old apt inside (specifically apt without support
Hi,
does anybody plan to use sbuild in Stretch with Debian Squeeze or older
chroots?
I would like to remove some code from sbuild which is only useful for chroots
with very old apt inside (specifically apt without support for [trusted=yes] in
the sources.list). Maintaining this piece of code
16 matches
Mail list logo