[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: messed up release in apt



I have removed the /etc/apt/trusted.gpg and that removed the error from apt update.
I will try now adding correct stretch-backports and installing the packages I  require,
thanks a lot, 

On Tue, May 1, 2018, at 12:29 PM, Brian wrote:
> On Tue 01 May 2018 at 09:18:56 -0500, David Wright wrote:
> 
> > On Tue 01 May 2018 at 08:11:28 (-0500), Anil Duggirala wrote:
> > > > If it were my machine (so that if I sank it I would be the only one
> > > > to
> > > > go down with the ship), I might run:
> > > > 
> > > >  'apt-key update'
> > > > 
> > > 
> > > When running that command I am getting :
> > > Warning: 'apt-key update' is deprecated and should not be used anymore!
> > > Note: In your distribution this command is a no-op and can therefore be
> > > removed safely.
> > > 
> > > > after removing 
> > > > 
> > > >  '/etc/apt/trusted.gpg' 
> > > > 
> > > When you say removing you mean :
> > > rm /etc/apt/trusted.gpg ?
> > > 
> > > I appreciate any other alternative procedure to correct this,
> > > thanks,
> > 
> > I don't know if this rather long thread would help. It does appear
> > that /etc/apt/trusted.gpg is no longer used, in favour of
> > /etc/apt/trusted.gpg.d/ but if the former exists, it can cause
> > problems. There's a new user on stretch called _apt but I don't
> > know its function.
> 
> A security enhancement. _apt is an unprivileged user, allowing
> sandboxed downloading. The user exists to protect against bugs
> in the http protocol handler, ssl libraries, compressors, etc.
> It also protects against permission issues elsewhere.
> 
> -- 
> Brian.
> 


Reply to: