WARNING: Libreoffice - Do not remove ~/.config/libreoffice

2017-07-07 Thread Hans
Hi folks, due to another problem in libreoffice (no gallery, when dmaths is installed), I moved ~/.config/libreoffice out of the way, to get a fresh configuration. DO NOT DO THIS except you have a backup available! If you do so, you will not be able, to start libreoffice any more. If you mov

Re: How to remove extra files created when building a package?

2017-06-29 Thread deloptes
Thomas Nyberg wrote: > I am trying to build the thunderbird package with some modifications. I > made the modifications and commited the changes to a local patch, but > then during the build (using `debuild -uc -us`) I ran out of space. I > ran `debuild clean` and then deleted different things on

Re: How to remove extra files created when building a package?

2017-06-29 Thread Thomas Nyberg
On 06/29/2017 09:34 PM, Greg Wooledge wrote: > On Thu, Jun 29, 2017 at 09:30:26PM +0200, Thomas Nyberg wrote: >> $ for file in $(find . -name '*.pyc'); do rm -v $file; done >> $ for file in $(find . -name '*.o'); do rm -v $file; done >> $ for file in $(find . -name '*.so'); do rm -v

Re: How to remove extra files created when building a package?

2017-06-29 Thread Greg Wooledge
On Thu, Jun 29, 2017 at 09:30:26PM +0200, Thomas Nyberg wrote: > $ for file in $(find . -name '*.pyc'); do rm -v $file; done > $ for file in $(find . -name '*.o'); do rm -v $file; done > $ for file in $(find . -name '*.so'); do rm -v $file; done *cringe* No, no, no find . -n

Re: How to remove extra files created when building a package?

2017-06-29 Thread Thomas Nyberg
Thanks for all the helpful info! On 06/29/2017 09:15 PM, Sven Joachim wrote: > On 2017-06-29 20:36 +0200, Thomas Nyberg wrote: > > In my experience, if you are serious about changing packages it's always > better to create a git repository, if only temporarily. Ideally clone > the existing one m

Re: How to remove extra files created when building a package?

2017-06-29 Thread Thomas Nyberg
Okay it looks like I solved the problem myself, but figured that I should recored it in the list for posterity. The first problem I had (even before the current question), was that I got errors that all started with: "dpkg-source: error: cannot represent change to ..." This seemed to have

Re: How to remove extra files created when building a package?

2017-06-29 Thread Sven Joachim
On 2017-06-29 20:36 +0200, Thomas Nyberg wrote: > I am trying to build the thunderbird package with some modifications. I > made the modifications and commited the changes to a local patch, but > then during the build (using `debuild -uc -us`) I ran out of space. I > ran `debuild clean` and then d

How to remove extra files created when building a package?

2017-06-29 Thread Thomas Nyberg
Hello, I am trying to build the thunderbird package with some modifications. I made the modifications and commited the changes to a local patch, but then during the build (using `debuild -uc -us`) I ran out of space. I ran `debuild clean` and then deleted different things on my computer and then t

Re: Remove topic

2017-03-30 Thread Tony Baldwin
On 03/30/2017 05:21 PM, Brad Rogers wrote: On Thu, 30 Mar 2017 16:42:58 -0400 Catherine Gramze wrote: Hello Catherine, The Debian mailing lists are publicly available. Perhaps the Debian IRC chat channels would give you the anonymity you want. I am sorry if this disclosure of your name has ha

Re: Remove topic

2017-03-30 Thread Brad Rogers
On Thu, 30 Mar 2017 16:42:58 -0400 Catherine Gramze wrote: Hello Catherine, >The Debian mailing lists are publicly available. Perhaps the Debian IRC >chat channels would give you the anonymity you want. I am sorry if this >disclosure of your name has harmed you in any way. You may not have >unde

Re: Remove topic

2017-03-30 Thread Tony Baldwin
On 03/30/2017 04:16 PM, Lounis ILLOURMANE wrote: Hello, Can you please remove the topic on this URL https://lists.debian.org/debian-user/2010/06/msg02062.html There's my first and family name, some people try to use this informations to hurt me. Please help me. Please do not make this me

Re: Remove topic

2017-03-30 Thread Catherine Gramze
> On Mar 30, 2017, at 4:16 PM, Lounis ILLOURMANE wrote: > > Hello, > Can you please remove the topic on this URL > https://lists.debian.org/debian-user/2010/06/msg02062.html > There's my first and family name, some people try to use this informations to > hurt me.

Remove topic

2017-03-30 Thread Lounis ILLOURMANE
Hello, Can you please remove the topic on this URL https://lists.debian.org/debian-user/2010/06/msg02062.html There's my first and family name, some people try to use this informations to hurt me. Please help me. Please do not make this message public. Good regards Lounis illourmane

Re: How to >>COMPLETELY<< remove an application?

2017-03-11 Thread Jörg-Volker Peetz
ed it. > > I've noticed that some times aptitue purge does not remove everything > as show by running aptitude search on the pkg name and seeing the 'c' > (lower case `c' ) the indicates some files remain that have user > changes. > > When that happens I

Re: How to >>COMPLETELY<< remove an application?

2017-03-11 Thread Harry Putnam
Cindy-Sue Causey writes: > Do Synaptic, Aptitude, and possibly anything else of that family have > similarly close but still different flags/commands? I haven't seen this mentioned in the thread... but may have missed it. I've noticed that some times aptitue purge does not remo

Re: How to >>COMPLETELY<< remove an application?

2017-03-09 Thread Hans
rare happened. In that case, i.e, when a library is missing, I am just reinstall this partiular one. For uninstalling old kernels, I also like to use aptitude purge ~n4.8.0-1-amd64-* (the same is apt-get --purge remove 4.8.0-1-amd64-* which installs all packages with 4.8.0-1-amd64 in its name

Re: How to >>COMPLETELY<< remove an application?

2017-03-09 Thread Brian
ientifically to verify yay or nay for fact. "purge" indeed does remove all the files the package installed [1]. This is something an experienced user like the OP should be familiar with. > >From "man apt-get": > > + > > remove >remove is

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Marc Shapiro
g the as originally installed environment. I used Synaptic to remove the package - choosing the "Mark for complete removal" option. It notified me that it would remove configuration files which was why I chose that option. I reinstalled grml-debootstrap from the same DVD set. I did a dr

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Richard Owlett
deborphan, it will update, upgrade, autoremove and check for orphaned packages with the one command. On a Stable system let 'upgrade-system' have it's way, it's safe and will remove your crud, but on testing and Sid check what packages it's going to remove just like you would

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Jimmy Johnson
used Synaptic to remove the package - choosing the "Mark for complete removal" option. It notified me that it would remove configuration files which was why I chose that option. I reinstalled grml-debootstrap from the same DVD set. I did a dry run and got a quite different set of errors.

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Brian
On Wed 08 Mar 2017 at 13:34:08 -0600, Richard Owlett wrote: > On 03/08/2017 12:32 PM, Cindy-Sue Causey wrote: > >On 3/8/17, Richard Owlett wrote: [Lots of snipping to get to to the heart of the question] > >>What is the most effective way to completely remove an appli

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Richard Owlett
believe I've narrowed the problem source to two specific files. I have used script to record some of my test runs after I had edited the files in question. I wanted to record a test run duplicating the as originally installed environment. I used Synaptic to remove the package - choosing the

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Richard Owlett
On 03/08/2017 12:24 PM, Frank wrote: Op 08-03-17 om 19:01 schreef Richard Owlett: What is the most effective way to completely remove an application? Remove it - as you did - including the configuration files (i.e. any files in /etc). Then check your home directory - also ~/.config and

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Cindy-Sue Causey
owed the problem source to two specific files. > > I have used script to record some of my test runs after I had edited the > files in question. > > I wanted to record a test run duplicating the as originally installed > environment. I used Synaptic to remove the package - choosing

Re: How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Frank
Op 08-03-17 om 19:01 schreef Richard Owlett: What is the most effective way to completely remove an application? Remove it - as you did - including the configuration files (i.e. any files in /etc). Then check your home directory - also ~/.config and ~/.local/share - for any user owned

How to >>COMPLETELY<< remove an application?

2017-03-08 Thread Richard Owlett
used script to record some of my test runs after I had edited the files in question. I wanted to record a test run duplicating the as originally installed environment. I used Synaptic to remove the package - choosing the "Mark for complete removal" option. It notified me that

Re: Remove Account

2016-09-22 Thread Curt
On 2016-09-22, Cindy-Sue Causey wrote: >> Brian wrote: >>> How are you reading these replies? >> >> By mails forwarded from the subscribed address to the unsubscribed one. >> I understand he cannot send mail from the subscribed address. > > > THEN... in a case like this thread is seeming to sa

Re: Remove Account

2016-09-21 Thread Cindy-Sue Causey
On 9/20/16, Thomas Schmitt wrote: > > Benjamin R. Zakarin wrote: >> Therefore I implore of you to entirely scrub bzaka...@umich.edu from ALL >> MAILING LISTS AND ANY REGISTRY. > > I don't know whether anybody listens here who has the power to do so. > > Did you already try the "Unsubscribe" button

Re: Remove Account

2016-09-21 Thread Kent West
On Sep 21, 2016 4:30 AM, "Michael Lange" wrote: > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. I'm so rusty with my Morse, it took me a minute and some effort to decode this. I always planned to get good at code. Maybe I will, if your alien blessing works for me ;-)

Re: Remove Account

2016-09-21 Thread Michael Lange
On Wed, 21 Sep 2016 09:08:12 +0100 Lisi Reisz wrote: (...) > Sadly that doesn't help with the OP's problem. That requires access to > the subscribed email address. He no longer has access to the > subscribed email address and everything is being forwarded to him so he > wants to stop it.. Here

Re: Remove Account

2016-09-21 Thread Lisi Reisz
On Wednesday 21 September 2016 08:29:09 Andrew M.A. Cater wrote: > On Tue, Sep 20, 2016 at 10:30:57PM +0100, Brian wrote: > > On Tue 20 Sep 2016 at 22:40:23 +0200, Thomas Schmitt wrote: > > > Brian wrote: > > > > But you said he would read list mail as follows: > > > > > > He said he _receives_ lis

Re: Remove Account

2016-09-21 Thread Curt
On 2016-09-21, Andrew M.A. Cater wrote: > > It's a bot that handles requests to join the list. > > debian-user-requ...@lists.debian.org > > with a subject of > > subscribe > > for example and > > unsubscribe > > Note the capitalisation. > > AndyC > I learned something here because I had thoug

Re: Remove Account

2016-09-21 Thread Andrew M.A. Cater
On Tue, Sep 20, 2016 at 10:30:57PM +0100, Brian wrote: > On Tue 20 Sep 2016 at 22:40:23 +0200, Thomas Schmitt wrote: > > > Brian wrote: > > > But you said he would read list mail as follows: > > > > He said he _receives_ list mail. He did not say that he reads it. > > > > > Now he is mass deleti

Re: Remove Account

2016-09-20 Thread Brian
On Tue 20 Sep 2016 at 22:40:23 +0200, Thomas Schmitt wrote: > Brian wrote: > > But you said he would read list mail as follows: > > He said he _receives_ list mail. He did not say that he reads it. > > > Now he is mass deleting it! > > Potentially. An assumption as base for an in-advance workar

Re: Remove Account

2016-09-20 Thread Thomas Schmitt
Hi, Brian wrote: > But you said he would read list mail as follows: He said he _receives_ list mail. He did not say that he reads it. > Now he is mass deleting it! Potentially. An assumption as base for an in-advance workaround offer. He mentioned multiple debian lists. Nobody can read them al

Re: Remove Account

2016-09-20 Thread Brian
On Tue 20 Sep 2016 at 21:22:02 +0200, Thomas Schmitt wrote: > Brian wrote: > > But he can reply to either of our mails. > > Yeah. But i expect that the automat at debian-user-requ...@lists.debian.org debian-user-request has nothing to do with it. He can reply to -user in the same way he sent his

Re: Remove Account

2016-09-20 Thread Thomas Schmitt
Hi, i looked at the confirmation request from my subscription here, a year ago. The hope for a HTTP link dwindles. But there is the advise to send a mail To: debian-user-requ...@lists.debian.org Subject: unsubscribe bzaka...@umich.edu If this does not help, then send your problem report

Re: Remove Account

2016-09-20 Thread Brian
On Tue 20 Sep 2016 at 20:41:45 +0200, Thomas Schmitt wrote: > Brian wrote: > > How are you reading these replies? > > By mails forwarded from the subscribed address to the unsubscribed one. That's a good point. If he is receiving all -user amils I needn't have sent a Cc:. Damn. > I understand

Re: Remove Account

2016-09-20 Thread Thomas Schmitt
Hi, Benjamin R. Zakarin wrote: > Therefore I implore of you to entirely scrub bzaka...@umich.edu from ALL > MAILING LISTS AND ANY REGISTRY. I don't know whether anybody listens here who has the power to do so. Did you already try the "Unsubscribe" button on https://lists.debian.org/debian-use

Re: Remove Account

2016-09-20 Thread Brian
On Tue 20 Sep 2016 at 12:17:53 -0400, Benjamin R. Zakarin wrote: > Attention: > > I have been trying to do this for years with NO HELP. I was signed up > for every Debian mailing list in college as a joke (floods your inbox) > and I cannot get rid of all of the subscriptions/emails. > > The iss

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-05 Thread Jörg-Volker Peetz
Gene Heskett wrote on 06/05/16 21:52: > On Sunday 05 June 2016 13:03:09 Jörg-Volker Peetz wrote: > >> >> >>> I just let it do it all, and will "wait for the other shoe to drop" >>> One thing that seems missing in these procedures is when a bunch of >>> libs have been purged, is a run of ldconfig

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-05 Thread Gene Heskett
On Sunday 05 June 2016 13:03:09 Jörg-Volker Peetz wrote: > > > > I just let it do it all, and will "wait for the other shoe to drop" > > One thing that seems missing in these procedures is when a bunch of > > libs have been purged, is a run of ldconfig to clean up things. > > No, when purging a d

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-05 Thread Jörg-Volker Peetz
> I just let it do it all, and will "wait for the other shoe to drop" > One thing that seems missing in these procedures is when a bunch of libs > have been purged, is a run of ldconfig to clean up things. > No, when purging a debian package, dpkg triggers actions like ldconfig as prescribed by

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-05 Thread Gene Heskett
ixman-1-0 (>= 0.21.6). > > libcairo2:i386 depends on libpixman-1-0 (>= 0.21.6). > > > > dpkg: error processing libpixman-1-0:i386 (--purge): > > dependency problems - not removing > > Errors were encountered while processing: > > libpixman-1-0:i386 >

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-05 Thread Jörg-Volker Peetz
i386 depends on libpixman-1-0 (>= 0.21.6). > > dpkg: error processing libpixman-1-0:i386 (--purge): > dependency problems - not removing > Errors were encountered while processing: > libpixman-1-0:i386 > Since the automatism is too reckless, we can use manual control, j

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-05 Thread Lisi Reisz
On Sunday 05 June 2016 03:18:38 David Wright wrote: > On Sat 04 Jun 2016 at 21:11:23 (-0400), Gene Heskett wrote: > > On Saturday 04 June 2016 17:49:02 Jörg-Volker Peetz wrote: > > > aptitude search '~g' > > > > And that returns an equally lengthy list, all prefaced with an 'id'. No > > clue wha

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-04 Thread David Wright
On Sat 04 Jun 2016 at 21:11:23 (-0400), Gene Heskett wrote: > On Saturday 04 June 2016 17:49:02 Jörg-Volker Peetz wrote: > > aptitude search '~g' > > And that returns an equally lengthy list, all prefaced with an 'id'. No > clue what that means as I don't believe I have the reference manual.

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Gene Heskett
On Saturday 04 June 2016 17:55:41 Lisi Reisz wrote: > On Saturday 04 June 2016 19:06:01 Gene Heskett wrote: > > Thank you for the link Lisi, I believe it was helpful in showing me > > that at my age, I am finally in over my head, > > Many years ago now I had that salutary lesson - at a MUCH younge

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-04 Thread Gene Heskett
4+deb7u2). xserver-xorg-core depends on libpixman-1-0 (>= 0.21.6). libcairo2:i386 depends on libpixman-1-0 (>= 0.21.6). dpkg: error processing libpixman-1-0:i386 (--purge): dependency problems - not removing Errors were encountered while processing: libpixman-1-0:i386 > Or heavier

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Lisi Reisz
On Saturday 04 June 2016 19:06:01 Gene Heskett wrote: > Thank you for the link Lisi, I believe it was helpful in showing me that > at my age, I am finally in over my head, Many years ago now I had that salutary lesson - at a MUCH younger age. My six year old son was musically gifted. There is a

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-04 Thread Jörg-Volker Peetz
> - window manager of the Xfce project > > That's all folks! Thanks JVP. > > Cheers, Gene Heskett > All these remnants of previously installed packages can be safely removed from your system in my opinion. If you prefer dpkg, try dpkg --

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-04 Thread Gene Heskett
On Saturday 04 June 2016 16:12:30 Jörg-Volker Peetz wrote: > I'm glad it worked for you. > Now I'm just curious what > > aptitude search '~c' > > spits out now. > > Regards, > jvp. A rather lengthy list I'll paste, wordwrap off again: root@coyote:/var/lib/dpkg# aptitude search ~c c brasero

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-04 Thread Jörg-Volker Peetz
I'm glad it worked for you. Now I'm just curious what aptitude search '~c' spits out now. Regards, jvp.

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages [SOLVED]

2016-06-04 Thread Gene Heskett
> > libpng12-0:amd64 PNG library - runtime > > libhunspell-1.3-0:amd64 spell checker and morphological analyzer > > (shared library) libstdc++6:amd64 GNU Standard C++ Library v3 > > libglib2.0-0:amd64 GLib library of C routines > > libkrb5-3:amd64

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Gene Heskett
On Saturday 04 June 2016 11:11:32 Lisi Reisz wrote: > On Saturday 04 June 2016 15:45:17 Gene Heskett wrote: > > On Saturday 04 June 2016 05:53:17 Jörg-Volker Peetz wrote: > > > The aptitude on your system is an older version (on sid it is > > > 0.8.1), > > > > Yes, this is wheezy. 6.8.2 here. > >

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Jörg-Volker Peetz
Gene Heskett wrote on 06/04/16 16:45: > On Saturday 04 June 2016 05:53:17 Jörg-Volker Peetz wrote: > >> The aptitude on your system is an older version (on sid it is 0.8.1), > > Yes, this is wheezy. 6.8.2 here. > >> maybe it hasn't the full architecture support. >> The dpkg output is reliable, I

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Gene Heskett
On Saturday 04 June 2016 11:11:32 Lisi Reisz wrote: > On Saturday 04 June 2016 15:45:17 Gene Heskett wrote: > > On Saturday 04 June 2016 05:53:17 Jörg-Volker Peetz wrote: > > > The aptitude on your system is an older version (on sid it is > > > 0.8.1), > > > > Yes, this is wheezy. 6.8.2 here. > >

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Lisi Reisz
On Saturday 04 June 2016 15:45:17 Gene Heskett wrote: > On Saturday 04 June 2016 05:53:17 Jörg-Volker Peetz wrote: > > The aptitude on your system is an older version (on sid it is 0.8.1), > > Yes, this is wheezy. 6.8.2 here. Which, according to " is also Y2K-compliant, non-fattening, naturally

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Gene Heskett
On Saturday 04 June 2016 05:53:17 Jörg-Volker Peetz wrote: > The aptitude on your system is an older version (on sid it is 0.8.1), Yes, this is wheezy. 6.8.2 here. > maybe it hasn't the full architecture support. > The dpkg output is reliable, I think. Since in the output of the dpkg > command a

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-04 Thread Jörg-Volker Peetz
The aptitude on your system is an older version (on sid it is 0.8.1), maybe it hasn't the full architecture support. The dpkg output is reliable, I think. Since in the output of the dpkg command all amd64 packages have an "ii" at the beginning of the line, it shows that all your amd64 packages are

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Gene Heskett
On Friday 03 June 2016 20:06:57 Jörg-Volker Peetz wrote: > Some more explanations: these tilde-on-letter combinations are search > patterns for aptitude. "~c" stands for packages already removed but > not purged, there are some config files left on the system. See also > "--purge --pending" in the

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Jörg-Volker Peetz
Some more explanations: these tilde-on-letter combinations are search patterns for aptitude. "~c" stands for packages already removed but not purged, there are some config files left on the system. See also "--purge --pending" in the man page of dpkg. So this does no harm if you don't intend to rei

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Gene Heskett
On Friday 03 June 2016 14:15:17 Jörg-Volker Peetz wrote: > aptitude purge '~i~ramd64 Returns: root@coyote:/var/lib/dpkg# aptitude purge '~i~ramd64' No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Gene Heskett
ubbornly > > ghosted, so I cannot fix any broken patckages that are preventing > > the install of any updates. > > > > So I try to have dpkg remove the amd64 aarchitecture, but now get a > > database is locked error. The system is working, quite stably, but > > I

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Jörg-Volker Peetz
so I cannot >> fix any broken patckages that are preventing the install of any updates. >> >> So I try to have dpkg remove the amd64 aarchitecture, but now get a >> database is locked error. The system is working, quite stably, but I > > Using aptitude I would com

Re: Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Jörg-Volker Peetz
of any updates. > > So I try to have dpkg remove the amd64 aarchitecture, but now get a > database is locked error. The system is working, quite stably, but I Using aptitude I would command aptitude purge '~ramd64' and maybe aptitude purge '~c' whi

Pursuant to my efforts to remove, and update the remaining :amd64 built packages

2016-06-03 Thread Gene Heskett
Greetings all; I re-added the amd64 architecture to the architecture's in dpkg/synaptic, but the package -> force-version remains stubbornly ghosted, so I cannot fix any broken patckages that are preventing the install of any updates. So I try to have dpkg remove the amd64 aarchitect

Re: What/How Files to Remove for a Xen Guest

2016-01-11 Thread Darac Marjal
On Sat, Jan 09, 2016 at 06:05:51PM -0800, ray wrote: I would like to remove a specific domU (test01--pv--guest) from my machine. I am not sure how far/to what extent to remove files. Here are the files and properties it seems I should remove: For this task, you're actually better off

What/How Files to Remove for a Xen Guest

2016-01-09 Thread ray
I would like to remove a specific domU (test01--pv--guest) from my machine. I am not sure how far/to what extent to remove files. Here are the files and properties it seems I should remove: lrwxrwxrwx 1 root root 10 Jan 9 11:05 /dev/disk/by-id/dm-name-xenvg-test01--pv--guest--disk

Re: Trying to remove "architecture i386"

2015-12-01 Thread Steve McIntyre
ltiarch myself, but it works for the >> native architecture and "*:all"). >> >> Ansgar > >Thanks Ansgar. > >--8<---cut here---start->8--- >dpkg -l "*:i386" >Desired=Unknown/Install/Remove/Purge/Hold >|

Re: Trying to remove "architecture i386"

2015-12-01 Thread Sharon Kimble
t; and then - > > ╭ > │dpkg --print-foreign-architectures > ╰ > > then I did a 'apt-get update' and tried to install crossover again. I've > now given up trying to instal it and wish to move back to just being a > 64-bit machine using amd64 packages only. I&#

Re: Trying to remove "architecture i386"

2015-12-01 Thread Sharon Kimble
Ansgar Burchardt <"Ansgar Burchardt"@43-1.org> writes: > Sharon Kimble writes: >> ╭──── >> │sudo dpkg --remove-architecture i386 >> ╰ >> >> which failed saying - >> >> dpkg: error: cannot remove architecture 'i386'

Re: Trying to remove "architecture i386"

2015-12-01 Thread Martin Read
On 01/12/15 08:47, Ansgar Burchardt wrote: Do you still have any i386 packages installed? I think running dpkg -l "*:i386" should list them (I don't use multiarch myself, but it works for the native architecture and "*:all"). I can confirm on my multiarch system that the command you sugges

Re: Trying to remove "architecture i386"

2015-12-01 Thread Ansgar Burchardt
Sharon Kimble writes: > ╭ > │sudo dpkg --remove-architecture i386 > ╰ > > which failed saying - > > dpkg: error: cannot remove architecture 'i386' currently in use by the > database > > How then can I remove 'i386' please, or should I

Trying to remove "architecture i386"

2015-11-30 Thread Sharon Kimble
'apt-get update' and tried to install crossover again. I've now given up trying to instal it and wish to move back to just being a 64-bit machine using amd64 packages only. I've therefore done - ╭ │sudo dpkg --remove-architecture i386 ╰ which failed saying - --8<

Re: remove me

2015-06-14 Thread Frank
On 06/14/2015 12:42 PM, pete wrote: To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". ^^^

remove me

2015-06-14 Thread pete
remove On 06/14/2015 06:32 AM, debian-user-digest-requ...@lists.debian.org wrote: -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557daef8.1000...@bofanez.org

Re: Remove subject

2015-05-17 Thread Stuart Longland
On 12/05/15 17:34, Mis Ntmurth wrote: > Ok thanks > I will contact debian They don't participate in Internet censorship either. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.

Re: OT: linguistic mis-usages (was Re: Remove subject)

2015-05-15 Thread Anthony Campbell
On 15 May 2015, The Wanderer wrote: > On 05/15/2015 at 07:35 AM, Chris Bannister wrote: > > > On Tue, May 12, 2015 at 09:16:17AM +0100, Anthony Campbell wrote: > > >> Since we're well off-topic already, I can't resist citing a rather > >> similar and increasingly prevalent negative usage that ma

Re: Remove subject

2015-05-15 Thread Mihamina Rakotomandimby
On 05/12/2015 10:34 AM, Mis Ntmurth wrote: Ok thanks I will contact debian regards You're also good to contact GMAne http://article.gmane.org/gmane.linux.debian.user/385152/match=problem+installing+gplflash Marc Info: http://marc.info/?l=debian-user&m=127780632904466 Google: https://groups.goo

OT: linguistic mis-usages (was Re: Remove subject)

2015-05-15 Thread The Wanderer
On 05/15/2015 at 07:35 AM, Chris Bannister wrote: > On Tue, May 12, 2015 at 09:16:17AM +0100, Anthony Campbell wrote: >> Since we're well off-topic already, I can't resist citing a rather >> similar and increasingly prevalent negative usage that makes no >> sense. I quite often read the phrase:

Re: Remove subject

2015-05-15 Thread Chris Bannister
On Tue, May 12, 2015 at 09:16:17AM +0100, Anthony Campbell wrote: > On 11 May 2015, Lisi Reisz wrote: > > > [snip] > > I hear that a _lot_. But I am hearing it more and more in cases > > like this above where only the negative makes sense. When it is written, > > some are, I am sure, typos.

Re: Remove subject

2015-05-12 Thread Anthony Campbell
On 11 May 2015, Lisi Reisz wrote: > [snip] > I hear that a _lot_. But I am hearing it more and more in cases > like this above where only the negative makes sense. When it is written, > some are, I am sure, typos. But I am equally sure that soemtimes when I > understand the positive the ne

Re: Remove subject

2015-05-12 Thread Mis Ntmurth
Ok thanks I will contact debian regards 2015-05-11 22:45 GMT+02:00 Jochen Spieker : > [Cc'ed to OP since I am sure (s)he is subscribed] > > Mis Ntmurth: > > > > Can you please remove the page where my name appears, at this page, > > https://lists.debian.org/d

Re: Remove subject

2015-05-11 Thread Lisi Reisz
On Monday 11 May 2015 22:30:13 Patrick Wiseman wrote: > On Mon, May 11, 2015 at 5:07 PM, Lisi Reisz wrote: > > On Monday 11 May 2015 21:45:33 Jochen Spieker wrote: > >> [Cc'ed to OP since I am sure (s)he is subscribed] > > > > This is a modern usage that I find very confusing. I take it to mean >

Re: Remove subject

2015-05-11 Thread Jochen Spieker
John Hasler: > Jochen Spieker wrote: >> [Cc'ed to OP since I am sure (s)he is subscribed] > > Lisi Reisz writes: >> This is a modern usage that I find very confusing. > > I assume that it is a mistake and that Jochen intended to write "Cc'ed > to OP since I not am sure (s)he is subscribed" Yes,

Re: Remove subject

2015-05-11 Thread Patrick Wiseman
On Mon, May 11, 2015 at 5:07 PM, Lisi Reisz wrote: > On Monday 11 May 2015 21:45:33 Jochen Spieker wrote: >> [Cc'ed to OP since I am sure (s)he is subscribed] > > This is a modern usage that I find very confusing. I take it to mean what I > would phrase "Cc'ed to OP since I am NOT sure (s)he is s

Re: Remove subject

2015-05-11 Thread John Hasler
Jochen Spieker wrote: > [Cc'ed to OP since I am sure (s)he is subscribed] Lisi Reisz writes: > This is a modern usage that I find very confusing. I assume that it is a mistake and that Jochen intended to write "Cc'ed to OP since I not am sure (s)he is subscribed" -- John Hasler jhas...@newsguy.

Re: Remove subject

2015-05-11 Thread Lisi Reisz
On Monday 11 May 2015 21:45:33 Jochen Spieker wrote: > [Cc'ed to OP since I am sure (s)he is subscribed] This is a modern usage that I find very confusing. I take it to mean what I would phrase "Cc'ed to OP since I am NOT sure (s)he is subscribed", ( or "am sure (s)he is NOT subscribed") since

Re: Remove subject

2015-05-11 Thread Jochen Spieker
[Cc'ed to OP since I am sure (s)he is subscribed] Mis Ntmurth: > > Can you please remove the page where my name appears, at this page, > https://lists.debian.org/debian-user/2010/06/msg02062.html > this subject is very old and have no answer and no interest now. It appears

Remove subject

2015-05-10 Thread Mis Ntmurth
Hello, Can you please remove the page where my name appears, at this page, https://lists.debian.org/debian-user/2010/06/msg02062.html this subject is very old and have no answer and no interest now. Good regards

Re: Remove safely rsyslog on a fresh Debian Jessie ?

2015-05-02 Thread Ludovic Gasc
2015-05-02 14:26 GMT+02:00 Sven Hartge : > Ludovic Gasc wrote: > > > After a fresh install of a Debian Jessie, I see that journald and rsyslog > > are both installed and launched. > > > I've found this post how to remove rsyslog: > > > http

Re: Remove safely rsyslog on a fresh Debian Jessie ?

2015-05-02 Thread Sven Hartge
Ludovic Gasc wrote: > After a fresh install of a Debian Jessie, I see that journald and rsyslog > are both installed and launched. > I've found this post how to remove rsyslog: > http://www.reddit.com/r/linux/comments/1xm6x3/getting_started_with_systemd_on_debian_jessie/cfcpx2

Remove safely rsyslog on a fresh Debian Jessie ?

2015-05-02 Thread Ludovic Gasc
Hi, After a fresh install of a Debian Jessie, I see that journald and rsyslog are both installed and launched. I've found this post how to remove rsyslog: http://www.reddit.com/r/linux/comments/1xm6x3/getting_started_with_systemd_on_debian_jessie/cfcpx2f Nevertheless, I could have an issue

Re: how to remove libsystemd0 from a live-running debian desktop system

2015-02-19 Thread Martin Read
On 17/02/15 17:34, Tanstaafl wrote: Honest question... What exactly is libsystemd0? It's a shared library maintained by the systemd maintainers. It provides a variety of (mostly fairly simple) utility functions such as: sd_notify (etc.) - Notify service manager about start-up completion and

Re: how to remove libsystemd0 from a live-running debian desktop system

2015-02-19 Thread Tanstaafl
Honest question... What exactly is libsystemd0? Maybe a simple solution would be to just rename it to something less 'offensive' to some, like: libinit - or libinit0 ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas.

Re: how to remove libsystemd0 from a live-running debian desktop system

2015-02-17 Thread Ric Moore
On 02/17/2015 01:15 PM, Luke Kenneth Casson Leighton wrote: On Tue, Feb 17, 2015 at 5:58 PM, Andrew Shadura wrote: Hi, On 17 February 2015 at 18:20, claude juif wrote: Really rude answer. Really bad. I find it really rude to send emails of about 300 lines of text in total. Extremely rude.

Re: how to remove libsystemd0 from a live-running debian desktop system

2015-02-17 Thread Luke Kenneth Casson Leighton
On Tue, Feb 17, 2015 at 6:25 PM, Luke Kenneth Casson Leighton wrote: > which should help answer the question you asked: your work - fantastic > as it is - was *impossible to find*. it doesn't even remotely come up > on the radar of queries. *nobody knows what you've achieved* and > that's somet

Re: how to remove libsystemd0 from a live-running debian desktop system

2015-02-17 Thread Luke Kenneth Casson Leighton
On Tue, Feb 17, 2015 at 7:03 PM, Andrew Shadura wrote: > Hello, > > I'd like to apologise for my mail I sent about two hours ago. I have > overreacted mainly because of the length of the email, CAPS INSIDE and > also because it's a topic which is being discussed for more than a year > and which ma

Re: how to remove libsystemd0 from a live-running debian desktop system

2015-02-17 Thread Andrew Shadura
Hello, I'd like to apologise for my mail I sent about two hours ago. I have overreacted mainly because of the length of the email, CAPS INSIDE and also because it's a topic which is being discussed for more than a year and which many of people here are already tired of. I however still think that

<    1   2   3   4   5   6   7   8   9   10   >