Re: repairing damage to package manager

songbird: > Chuck Hallenbeck wrote: >> >> One more O.T. observation: Debian let me do a truly dumb thing, but I >> wouldn't have it any other way. > > who here hasn't done an erroneous rm or some > other fumble fingered thing? > > a few weeks ago i was working on tagging some > pictures and

Re: repairing damage to package manager

Chuck Hallenbeck wrote: >Jochen Spieker wrote: >> Chuck Hallenbeck: >> > >> > # apt-get remove upgrade-system apt >> >> Nice one! This brightens my day a little as it reminds me how I found >> out the relationship betweent the commands available on MSDOS 5.0 and >> the contents of the C:\DOS dire

Re: repairing damage to package manager

On Friday 24 March 2017 19:57:56 Chuck Hallenbeck wrote: > One more O.T. observation: Debian let me do a truly dumb thing, but I > wouldn't have it any other way. :-))) +1 Lisi

Re: repairing damage to package manager

Chuck Hallenbeck: > > One more O.T. observation: Debian let me do a truly dumb thing, but I > wouldn't have it any other way. That's the spirit! J. -- If I am asked 'How are you' more than a million times in my life I promise to explode. [Agree] [Disagree]

Re: repairing damage to package manager

Hi J., On Fri, Mar 24, 2017 at 08:47:18PM +0100, Jochen Spieker wrote: > Chuck Hallenbeck: > > > > # apt-get remove upgrade-system apt > > Nice one! This brightens my day a little as it reminds me how I found > out the relationship betweent the commands available on MSDOS 5.0 and > the contents

Re: repairing damage to package manager

Chuck Hallenbeck: > > # apt-get remove upgrade-system apt Nice one! This brightens my day a little as it reminds me how I found out the relationship betweent the commands available on MSDOS 5.0 and the contents of the C:\DOS directory. :) I don't know how many times I had deleted stuff from there

Re: repairing damage to package manager

Hi, On Fri, Mar 24, 2017 at 03:22:06PM -0400, songbird wrote: > Chuck Hallenbeck wrote: > ... > > I presume you are suggesting using wget to retrieve the missing > > packages after identifying their URL's? > > if you haven't cleared /var/cache/apt/archives you > can check what is in there by:

Re: repairing damage to package manager

Chuck Hallenbeck wrote: ... > I presume you are suggesting using wget to retrieve the missing > packages after identifying their URL's? if you haven't cleared /var/cache/apt/archives you can check what is in there by: $ ls /var/cache/apt/archives/*.deb | grep apt and see what versions are show

Re: repairing damage to package manager

On Fri, Mar 24, 2017 at 11:53:59AM -0400, Chuck Hallenbeck wrote: > > I presume you are suggesting using wget to retrieve the missing > packages after identifying their URL's? > Yeah, or just download the package from packages.debian.org with a web browser, and then use dpkg -i on it. Check t

Re: repairing damage to package manager

Hi Jonathan, On Fri, Mar 24, 2017 at 03:40:52PM +, Jonathan Dowland wrote: > On Fri, Mar 24, 2017 at 11:30:31AM -0400, Chuck Hallenbeck wrote: > > dpkg-reconfigure doesn't help, nor dpkg -i apt-get. > > "apt-get" exists in the "apt" package, but "dpkg -i" takes an argument to > a local .deb a

Re: repairing damage to package manager

On Fri, Mar 24, 2017 at 11:30:31AM -0400, Chuck Hallenbeck wrote: > dpkg-reconfigure doesn't help, nor dpkg -i apt-get. "apt-get" exists in the "apt" package, but "dpkg -i" takes an argument to a local .deb archive, not a package name. Try downloading a .deb of apt for your version of debian and a

Re: repairing damage to package manager

Correction below: On Fri, Mar 24, 2017 at 11:30:31AM -0400, Chuck Hallenbeck wrote: > Hi folks, > > I've been using Debian Stretch for a couple of months, and following > this list for a month or two. I'm afraid I did something stupid anyway, > and find myself with a damaged apt-get and can't fi

repairing damage to package manager

Hi folks, I've been using Debian Stretch for a couple of months, and following this list for a month or two. I'm afraid I did something stupid anyway, and find myself with a damaged apt-get and can't figure out how to fix it short of reinstalling. Here is what I did to damage it: The discussion