On 3/06/2016 10:38 p.m., David Kalnischkies wrote:
>
> btw: I just checked: I introduced the first of the two finds (which is
> the more obvious problem as that codepath is used more) on 7 Jul 2015
> (25f27319) [the other is 6 Dec 2015], so that problem isn't recent but
> lingers there since 1.1 a
Hi,
(purely optional mail follows)
On Fri, Jun 03, 2016 at 11:21:41AM +0200, Adam Borowski wrote:
> On Fri, Jun 03, 2016 at 02:25:45PM +0530, Ritesh Raj Sarraf wrote:
> > On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote:
> > From what you've explained, this bug should be reassigned to APT
On Fri, Jun 03, 2016 at 02:25:45PM +0530, Ritesh Raj Sarraf wrote:
> On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote:
> > So, to summarize, the issue is that since apt-get update runs find as a
> > non-root user, running it from a 700 directory breaks find.
>
> Thank you for the root caus
On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote:
> On Hurd, getting $PWD from the 700 directory fails, and find thus aborts
> immediately, without emitting any output, and thus no keyring is found.
>
> So, to summarize, the issue is that since apt-get update runs find as a
> non-root user
Samuel Thibault, on Thu 02 Jun 2016 00:15:11 +0200, wrote:
> More precisely, running it from a directory which has perms 700 gets the
> issue.
Ok, I see the issue. What happens is that nowadays apt uses an _apt
user to do some operations, and notably running
find -L /etc/apt/trusted.gpg.d/ -type
Samuel Thibault, on Thu 02 Jun 2016 00:08:58 +0200, wrote:
> Samuel Thibault, on Wed 01 Jun 2016 23:40:16 +0200, wrote:
> > apt-get install --reinstall debian-archive-keyring
> >
> > didn't fix it.
> >
> > dpkg --force-depends -P debian-archive-keyring
> > dpkg -i /var/cache/apt/archives/debian-a
Samuel Thibault, on Wed 01 Jun 2016 23:40:16 +0200, wrote:
> apt-get install --reinstall debian-archive-keyring
>
> didn't fix it.
>
> dpkg --force-depends -P debian-archive-keyring
> dpkg -i /var/cache/apt/archives/debian-archive-keyring*
>
> did fix it.
Ah, no, it's just that running apt-get
Adam Borowski, on Wed 01 Jun 2016 21:50:50 +0200, wrote:
> Despite all the relevant keys being installed (debian-archive-keyring,
> debian-ports-archive-keyring; "apt-key list" says they're there), I get:
>
> W: GPG error: http://ftp.ports.debian.org/debian-ports unreleased InRelease:
> The follow
Package: apt
Version: 1.2.12
Severity: important
Despite all the relevant keys being installed (debian-archive-keyring,
debian-ports-archive-keyring; "apt-key list" says they're there), I get:
W: GPG error: http://ftp.ports.debian.org/debian-ports unreleased InRelease:
The following signatures co
9 matches
Mail list logo
