Re: catastrophe - but how? Aptitude goes mad

Gene writes: > No, thats just grep being grep, it says that of ANY binary file it > tries to read as text. No, it says that of any binary file in which it finds a match. You don't want it to print out the "line" in the binary file where it found the match because the "line" could be thousands of

Re: catastrophe - but how? Aptitude goes mad

On Sunday 03 July 2016 17:11:43 Wes wrote: > On 2016-06-30, Lisi Reisz wrote: > > I ran > > # aptitude install libreoffice-grammarcheck-en-gb > > and aptitude just carried on without asking as is correct when there > > is only one package; but it proceeded to uninstall my entire desktop > >

Re: catastrophe - but how? Aptitude goes mad

On 2016-06-30, Lisi Reisz wrote: I ran # aptitude install libreoffice-grammarcheck-en-gb and aptitude just carried on without asking as is correct when there is only one package; but it proceeded to uninstall my entire desktop environment, hundreds of packages. Both apt-get and aptitude have

Re: catastrophe - but how? Aptitude goes mad

On Fri, 1 Jul 2016 00:37:32 +0100, Lisi Reisz wrote: > > I used bash's history to confirm that I had had no such mental aberration. > It > confirmed that, after the root screen prompt, I had typed: > aptitude install libreoffice-grammarcheck-en-gb > and nothing else -

Re: catastrophe - but how? Aptitude goes mad

On Sat, 02 Jul 2016, Lisi Reisz wrote: > On Friday 01 July 2016 19:07:11 Henrique de Moraes Holschuh wrote: > > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > > Try this when you open a root session (in a typical console, and >

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 19:07:11 Henrique de Moraes Holschuh wrote: > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > Try this when you open a root session (in a typical console, and > > > certainly in a typical graphical

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 18:12:51 +, Curt wrote: > On 2016-07-01, Brian wrote: > >> > >> That's not what I meant. I meant ask *him* *here* in this public thread > >> why ... > >> etc. > > > > He is a subscriber to -user. By definition he *has been* asked here in > > this

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Brian wrote: >> >> That's not what I meant. I meant ask *him* *here* in this public thread why >> ... >> etc. > > He is a subscriber to -user. By definition he *has been* asked here in > this public thread. Well, there you go then, man. Maybe he's

Re: catastrophe - but how? Aptitude goes mad

On Fri, 01 Jul 2016, Lisi Reisz wrote: > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > Try this when you open a root session (in a typical console, and > > certainly in a typical graphical terminal): > > > > stty sane > > No output in either. "stty sane"

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 18:18:42 Brian wrote: > On Fri 01 Jul 2016 at 17:59:34 +0100, Lisi Reisz wrote: > > On Friday 01 July 2016 17:52:08 Curt wrote: > > > On 2016-07-01, Lisi Reisz wrote: > > > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > >>

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 17:59:34 +0100, Lisi Reisz wrote: > On Friday 01 July 2016 17:52:08 Curt wrote: > > On 2016-07-01, Lisi Reisz wrote: > > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > >> Try this when you open a root session (in a typical

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Lisi Reisz wrote: > On Friday 01 July 2016 17:52:08 Curt wrote: >> On 2016-07-01, Lisi Reisz wrote: >> > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: >> >> Try this when you open a root session (in a typical

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 16:57:02 +, Curt wrote: > On 2016-07-01, Lisi Reisz wrote: > > On Friday 01 July 2016 17:39:57 Curt wrote: > >> > > Because then the answer might be private too, and this is a public thread. > > I > > would obviously be interested in the answer,

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Lisi Reisz wrote: > On Friday 01 July 2016 17:39:57 Curt wrote: >> > Because then the answer might be private too, and this is a public thread. I > would obviously be interested in the answer, and many others might be too. > Not to mention that it would

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 17:52:08 Curt wrote: > On 2016-07-01, Lisi Reisz wrote: > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > >> Try this when you open a root session (in a typical console, and > >> certainly in a typical graphical terminal): > >> >

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Lisi Reisz wrote: > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: >> Try this when you open a root session (in a typical console, and >> certainly in a typical graphical terminal): >> >> stty sane > > No output in either. > What

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 17:39:57 Curt wrote: > On 2016-07-01, Brian wrote: > >> >> > Must be progress. GNU grep 2.12 here. > >> > > >> > Bug #678652. > >> > >> He didn't write that. > > > > No, you wrote it and I accidentally snipped a line when replying. But > > now we know

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Brian wrote: >> >> >> >> > Must be progress. GNU grep 2.12 here. >> > >> > Bug #678652. >> >> He didn't write that. > > No, you wrote it and I accidentally snipped a line when replying. But > now we know why the manual for grep 2.20-4.1 says something

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > Try this when you open a root session (in a typical console, and > certainly in a typical graphical terminal): > > stty sane No output in either. Lisi

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 15:19:20 +, Curt wrote: > On 2016-07-01, Brian wrote: > > On Fri 01 Jul 2016 at 13:56:22 +0200, to...@tuxteam.de wrote: > > > >> On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: > >> > On 2016-07-01,

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 16:06:30 Ralph Katz wrote: > On 07/01/2016 10:25 AM, Lisi Reisz wrote: > ... > > > Aptitude has served me well, reliably and faithfully for 14 years. I was > > not rushing to blame it in this case. > > > > But until I do find out what went wrong, I shall be a little nervous

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Brian wrote: > On Fri 01 Jul 2016 at 13:56:22 +0200, to...@tuxteam.de wrote: > >> On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: >> > On 2016-07-01, wrote: >> >> [...] >> >> > > GNU grep 2.20, Debian package grep

Re: catastrophe - but how? Aptitude goes mad

On 07/01/2016 10:25 AM, Lisi Reisz wrote: ... > Aptitude has served me well, reliably and faithfully for 14 years. I was not > rushing to blame it in this case. > > But until I do find out what went wrong, I shall be a little nervous of > aptitude. :-( ... Sorry to read of your upgrade

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 08:36:02 (-0400), Gene Heskett wrote: > On Friday 01 July 2016 05:43:44 Jörg-Volker Peetz wrote: > > Gene Heskett wrote on 07/01/16 01:35: > > > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > > > > > > > > No, thats just grep being grep, it says that of ANY binary

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 13:19:46 Brian wrote: > On Fri 01 Jul 2016 at 00:37:32 +0100, Lisi Reisz wrote: > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > > > assumed, it wasn't asked to remove anything. It was asked to add one >

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 05:43:44 Jörg-Volker Peetz wrote: > Gene Heskett wrote on 07/01/16 01:35: > > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > > > > No, thats just grep being grep, it says that of ANY binary file it > > tries to read as text. I have spent days pouring over the

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 03:44:01 to...@tuxteam.de wrote: > On Fri, Jul 01, 2016 at 09:42:09AM +0200, to...@tuxteam.de wrote: > > [...] > > > And I have paid tribute to the (in the man/info pages) unnamed > > authors (but one can find out [1]) who gave me such a little jewel. > > Eh, sorry. Forgot

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 00:37:32 +0100, Lisi Reisz wrote: > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > > assumed, it wasn't asked to remove anything. It was asked to add one > > > thing which in now way depended on anything

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 13:56:22 +0200, to...@tuxteam.de wrote: > On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: > > On 2016-07-01, wrote: > > [...] > > > > GNU grep 2.20, Debian package grep 2.20-4.1 -- progress or regression? > > [...] > > > Must

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: > On 2016-07-01, wrote: [...] > > GNU grep 2.20, Debian package grep 2.20-4.1 -- progress or regression? [...] > Must be progress. GNU grep 2.12 here.

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, wrote: > >> I looked it up in the man page too. It said: >> >> -R, -r, --recursive >> Read all files under each directory, recursively; this >> is equivalent to the -d recurse option. > > Hm. My man page seems more complete (it's the one

Re: catastrophe - but how? Aptitude goes mad

H, Dario Strbenac wrote: > Have you considered upgrading your customer's computer to Windows 10 > instead ? It's free to do until the end of the month! Beware, Microsoft had to pay 10,000 USD in damages after Windows 10 installed itself on a customer's computer. Have a nice day :) Thomas

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 01, 2016 at 09:36:16AM +, Curt wrote: > On 2016-07-01, wrote: > > > > I freely admit I didn't know, but now I do: > > > > -R follows (recursively) symbolic links > > -r follows a symbolic link

Re: catastrophe - but how? Aptitude goes mad

Gene Heskett wrote on 07/01/16 01:35: > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > No, thats just grep being grep, it says that of ANY binary file it tries > to read as text. I have spent days pouring over the manpages for grep, > looking for a option to feed it to make grep quit

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 07:00:08 Dario Strbenac wrote: > Have you considered upgrading your customer's computer to Windows 10 > instead ? It's free to do until the end of the month! :-)) ROTFLOL! It hasn't ever seen Windows, this lucky computer. So I can't upgrade!! Lisi

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, wrote: > > I freely admit I didn't know, but now I do: > > -R follows (recursively) symbolic links > -r follows a symbolic link only if it is the top-level argument I looked it up in the man page too. It said: -R, -r, --recursive Read

Re: catastrophe - but how? Aptitude goes mad

Have you considered upgrading your customer's computer to Windows 10 instead ? It's free to do until the end of the month!

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 01, 2016 at 09:42:09AM +0200, to...@tuxteam.de wrote: [...] > And I have paid tribute to the (in the man/info pages) unnamed authors > (but one can find out [1]) who gave me such a little jewel. Eh, sorry. Forgot [1]

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 30, 2016 at 06:57:06PM -0400, Gene Heskett wrote: > On Thursday 30 June 2016 16:12:46 Henrique de Moraes Holschuh wrote: > > > grep -r Assume-Yes /etc > > 100% missing here, but lemme see what happens when I use the recursive -R > since

Re: catastrophe - but how? Aptitude goes mad

On Thu 30 Jun 2016 at 22:41:57 (-0400), Gene Heskett wrote: > On Thursday 30 June 2016 20:51:37 David Wright wrote: > > On Thu 30 Jun 2016 at 19:35:44 (-0400), Gene Heskett wrote: > > > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > > > On Thursday 30 June 2016 21:12:46 Henrique de Moraes

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 20:51:37 David Wright wrote: > On Thu 30 Jun 2016 at 19:35:44 (-0400), Gene Heskett wrote: > > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > > On Thursday 30 June 2016 21:12:46 Henrique de Moraes Holschuh wrote: > > > > On Thu, 30 Jun 2016, Gene Heskett wrote:

Re: catastrophe - but how? Aptitude goes mad

On Thu 30 Jun 2016 at 19:35:44 (-0400), Gene Heskett wrote: > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > On Thursday 30 June 2016 21:12:46 Henrique de Moraes Holschuh wrote: > > > On Thu, 30 Jun 2016, Gene Heskett wrote: > > > > Thats not excusable behavior, but whats worse is that

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 00:35:44 Gene Heskett wrote: > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > On Thursday 30 June 2016 21:12:46 Henrique de Moraes Holschuh wrote: > > > On Thu, 30 Jun 2016, Gene Heskett wrote: > > > > Thats not excusable behavior, but whats worse is that debian's >

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > assumed, it wasn't asked to remove anything. It was asked to add one > > thing which in now way depended on anything removed. That is what > > puzzles me. And > > I don't know why it

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > On Thursday 30 June 2016 21:12:46 Henrique de Moraes Holschuh wrote: > > On Thu, 30 Jun 2016, Gene Heskett wrote: > > > Thats not excusable behavior, but whats worse is that debian's > > > people are denying there is a problem. 'scuse me? I

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 21:12:46 Henrique de Moraes Holschuh wrote: > On Thu, 30 Jun 2016, Gene Heskett wrote: > > Thats not excusable behavior, but whats worse is that debian's people are > > denying there is a problem. 'scuse me? I swear, they couldn't smell > > coffee with a nose full of it.

Re: catastrophe - but how? Aptitude goes mad

On Fri, 01 Jul 2016, Lisi Reisz wrote: > assumed, it wasn't asked to remove anything. It was asked to add one thing > which in now way depended on anything removed. That is what puzzles me. And I don't know why it would do that. Well, it shouldn't ask about deleting one thousand packages if

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 17:25:41 Francesco Ariis wrote: > On Thu, Jun 30, 2016 at 05:27:16PM +0100, Lisi Reisz wrote: > > I ran > > # aptitude install libreoffice-grammarcheck-en-gb > > and aptitude just carried on without asking as is correct when there > > is only one package; but it proceeded

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 20:27:03 Brian wrote: > On Thu 30 Jun 2016 at 19:59:52 +0200, Hans wrote: > > Correct myself: > > > I used the log file and edited it that way, that I took all the > > > packagages from it and made an "aptitude reinstall" in front of the > > > package list. > > > > Then I

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 21:12:46 Henrique de Moraes Holschuh wrote: > On Thu, 30 Jun 2016, Gene Heskett wrote: > > Thats not excusable behavior, but whats worse is that debian's people are > > denying there is a problem. 'scuse me? I swear, they couldn't smell > > coffee with a nose full of it.

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 16:12:46 Henrique de Moraes Holschuh wrote: > grep -r Assume-Yes /etc 100% missing here, but lemme see what happens when I use the recursive -R since I can't ever recall using the lower case r for recursion. That took at least 3 or 4 minutes to complete, whereas the -r

Re: catastrophe - but how? Aptitude goes mad

On Thu, 30 Jun 2016, Gene Heskett wrote: > Thats not excusable behavior, but whats worse is that debian's people are > denying there is a problem. 'scuse me? I swear, they couldn't smell > coffee with a nose full of it. > > Cheers, Gene Heskett Well, if either of you two (that suffered the

Re: catastrophe - but how? Aptitude goes mad

On Thursday 30 June 2016 12:27:16 Lisi Reisz wrote: > I ran > # aptitude install libreoffice-grammarcheck-en-gb > and aptitude just carried on without asking as is correct when there > is only one package; but it proceeded to uninstall my entire desktop > environment, hundreds of packages. I

Re: catastrophe - but how? Aptitude goes mad

Correct myself: > I used the log file and edited it that way, that I took all the packagages > from it and made an "aptitude reinstall" in front of the package list. Then I made a shellscript of it, just added the shebang line and made it executable with root-permissions. Hans

Re: catastrophe - but how? Aptitude goes mad

> 5. Assess the damage. Glance at the output of 'dpkg -l | less'. Is X >still about? The desktop? Anything obvious missing? Look at the files >in /var/log/apt. All packages removed and installed are recorded. >Supposedly aptitude also logs? > I used the log file and edited it that

Re: catastrophe - but how? Aptitude goes mad

On Thu 30 Jun 2016 at 17:27:16 +0100, Lisi Reisz wrote: > I ran > # aptitude install libreoffice-grammarcheck-en-gb > and aptitude just carried on without asking as is correct when there > is only one package; but it proceeded to uninstall my entire desktop > environment, hundreds of packages. I

Re: catastrophe - but how? Aptitude goes mad

On Thu, 30 Jun 2016 17:27:16 +0100 Lisi Reisz wrote: >I ran ># aptitude install libreoffice-grammarcheck-en-gb >and aptitude just carried on without asking as is correct when there >is only one package; but it proceeded to uninstall my entire desktop >environment, hundreds

Re: catastrophe - but how? Aptitude goes mad

On Thu, Jun 30, 2016 at 05:27:16PM +0100, Lisi Reisz wrote: > I ran > # aptitude install libreoffice-grammarcheck-en-gb > and aptitude just carried on without asking as is correct when there > is only one package; but it proceeded to uninstall my entire desktop > environment, hundreds of packages.

catastrophe - but how? Aptitude goes mad

I ran # aptitude install libreoffice-grammarcheck-en-gb and aptitude just carried on without asking as is correct when there is only one package; but it proceeded to uninstall my entire desktop environment, hundreds of packages. I couldn't believe it and used the bash history to confirm that that