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: >

Re: messed up release in apt

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' > > > > > > >

Re: messed up release in apt

On 05/01/2018 06:11 AM, 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:

Re: messed up release in apt

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

Re: messed up release in apt

On 2018-05-01, 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

Re: messed up release in apt

> 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

Re: messed up release in apt

> By old, I was referring to sources.list with jessie backports. I wold > do > that to make sure that apt will clean up all dependencies for Wine in > jessie backports. I thought that was what you meant, I did as you instructed. Just trying to get rid of this "key" error now. thanks a lot,

Re: messed up release in apt

On 2018-04-30, Anil Duggirala wrote: > > I removed all backported packages. Then did apt-get autoremove. Then > removed the jessie-backports line from sources.list. I appear to have > come back to my original system. However I am now getting an error on > apt update. >

Re: messed up release in apt

On 30-04-18, Anil Duggirala wrote: > > I would first use old sources.list to purge wine and follow it up > > with > > autoremove. But after that new, this time intended and correct, > > sources.list with apt-get should solve problem. > > > > When you say "old" do you mean the sources.list

Re: messed up release in apt

> > The Debian English-language backports wiki FAQ suggests (to find > all backported packages on a given machine): > > https://backports.debian.org/FAQ/ > I removed all backported packages. Then did apt-get autoremove. Then removed the jessie-backports line from sources.list. I appear to have

Re: messed up release in apt

> I would first use old sources.list to purge wine and follow it up > with > autoremove. But after that new, this time intended and correct, > sources.list with apt-get should solve problem. > When you say "old" do you mean the sources.list without the jessie backports entry? Could you explain

Re: messed up release in apt

On 2018-04-30, Anil Duggirala wrote: > hello, > I mistakenly added an etc/apt/sources.list line for "jessie"(backports) > instead of "stretch", which is my current release. I proceded to update > apt and installed Wine (along with many packages, some i386) from the >

Re: messed up release in apt

On 30-04-18, Brian wrote: > On Mon 30 Apr 2018 at 11:49:33 -0500, Anil Duggirala wrote: > > > hello, > > I mistakenly added an etc/apt/sources.list line for "jessie"(backports) > > instead of "stretch", which is my current release. I proceded to update > > apt and installed Wine (along with many

Re: messed up release in apt

On Mon 30 Apr 2018 at 11:49:33 -0500, Anil Duggirala wrote: > hello, > I mistakenly added an etc/apt/sources.list line for "jessie"(backports) > instead of "stretch", which is my current release. I proceded to update > apt and installed Wine (along with many packages, some i386) from the >

messed up release in apt

hello, I mistakenly added an etc/apt/sources.list line for "jessie"(backports) instead of "stretch", which is my current release. I proceded to update apt and installed Wine (along with many packages, some i386) from the jessie-backports source (i.e. apt install wine/jessie-backports). Please tell