Control: tag -1 + pending
Hi,
On Mon, 07 Dec 2015 21:49:41 +0100 Johannes Schauer wrote:
> Quoting Johannes Schauer (2015-12-07 21:13:10)
> > It seems that apt has support for trusted=yes since 0.8.16~exp3, so since
> > wheezy.
>
> keeping support for signing the internal
Am Donnerstag, den 15.10.2015, 23:54 +0200 schrieb Helmut Grohne:
> On Wed, Oct 14, 2015 at 06:53:56PM +0200, Helmut Grohne wrote:
> > I would like to be able to use sbuild without having to create a gpg key
> > for it. I understand that creating a key is required for operating as a
> > buildd,
Hi all,
Quoting Benjamin Drung (2015-12-07 12:37:01)
> Am Donnerstag, den 15.10.2015, 23:54 +0200 schrieb Helmut Grohne:
> > On Wed, Oct 14, 2015 at 06:53:56PM +0200, Helmut Grohne wrote:
> > > I would like to be able to use sbuild without having to create a gpg key
> > > for it. I understand
Hi,
Quoting Johannes Schauer (2015-12-07 21:13:10)
> It seems that apt has support for trusted=yes since 0.8.16~exp3, so since
> wheezy.
keeping support for signing the internal repository is important for as long as
we want to support squeeze. When running sbuild, then the apt *inside* the
On Wed, Oct 14, 2015 at 06:53:56PM +0200, Helmut Grohne wrote:
> I would like to be able to use sbuild without having to create a gpg key
> for it. I understand that creating a key is required for operating as a
> buildd, but sbuild can be used in other scenarios as well. This bug is
> supposed to
Package: sbuild
Severity: wishlist
Dear sbuild maintainers,
I would like to be able to use sbuild without having to create a gpg key
for it. I understand that creating a key is required for operating as a
buildd, but sbuild can be used in other scenarios as well. This bug is
supposed to
6 matches
Mail list logo