Quoting Cyril Brulebois (k...@debian.org):
> Cyril Brulebois (2017-10-30):
> > I think both issues are connected: if we can't trust the InRelease
> > signature for testing, we can't download packages from this suite in a
> > secure fashion, hence the “E: Some packages could not be authenticated”
>
Cyril Brulebois (2017-10-30):
> I think both issues are connected: if we can't trust the InRelease
> signature for testing, we can't download packages from this suite in a
> secure fashion, hence the “E: Some packages could not be authenticated”
> error?
>
> It might be due to new keys for testin
Christian PERRIER (2017-10-30):
> > | W: GPG error: http://ftp.de.debian.org/debian testing InRelease: The
> > following signatures couldn't be verified because the public key is not
> > available: NO_PUBKEY 7638D0442B90D010
> > | W: The repository 'http://ftp.de.debian.org/debian testing InRele
Quoting Cyril Brulebois (k...@debian.org):
> Package: d-i.debian.org
> Severity: important
>
> Hi,
>
> Since dillon's upgrade to stretch, the following cron job no longer works:
I've seen this for quite a while, yes.
> | Subject: Cron nice -n 19 $HOME/bin/generate_l10n-stats
> | …
> | ---
Package: d-i.debian.org
Severity: important
Hi,
Since dillon's upgrade to stretch, the following cron job no longer works:
| Subject: Cron nice -n 19 $HOME/bin/generate_l10n-stats
| …
| -- Level 1 --
| Getting sources:I do not have permission to write to /var/lib/debtags/
5 matches
Mail list logo
