Re: cups (sharing network printer)
Brian wrote: > On Mon 09 May 2016 at 23:45:18 +0200, deloptes wrote: > >> Pol Hallen wrote: >> >> >> Unless I am misunderstanding the question, >> > >> > I need to print using 192.168.1.10 (server) not directly by network >> > printer >> > >> > thanks! >> > >> > >> > Pol >> >> Hi >> >> In /etc/cups/client.conf >> >> set the ServerName >> >> ServerName 192.168.1.10 >> >> try lpstat -a >> >> $ lpstat -a >> HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST > > The OP talks about *"clients"*. Would your advice stay the same if there > was a 1000 of them? I do not have any better solution - this autodiscovery did not work for me and setting the ServerName in client.conf works. If he has 1000 - he has to manage them automatically anyway - or what do you do in such a case? Anyway I'll be glad to have better solution regards
bash Shell - escapes
On 2016-05-10 11:18, Die Optimisten wrote: Hi, How can I escape a ' inside '...' e.g. perl -e 'print '$ and a' '# I don't want to use " thank you Andrew I have to add, its bash - specific and PLEASE also CC: me using inform (AT) die-optimisten.net I'm not subscribed here THANKs
Shell - escapes
Hi, How can I escape a ' inside '...' e.g. perl -e 'print '$ and a' '# I don't want to use " thank you Andrew
bash - shell events "!"
Hello echo hello!# displays that, BUT: echo "Hello!" # tells: -su: !": event not found# this worked years before without problem! Is that intended? These leads to errors in many scripts (including installig package dkms) How can this be turned off? For me this behaviou should be changed, for example: Events should contain whitespace before or after it, or only work outside quoting... using GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Re: bash - shell events "!"
Hi, It is the historical part of C shell, you can disable it typing or adding it to your profile : set +H Regards, Jonathan Le 10 mai 2016 11:48 AM, "Die Optimisten" a écrit : Hello echo hello!# displays that, BUT: echo "Hello!" # tells: -su: !": event not found# this worked years before without problem! Is that intended? These leads to errors in many scripts (including installig package dkms) How can this be turned off? For me this behaviou should be changed, for example: Events should contain whitespace before or after it, or only work outside quoting... using GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Re: Re: "lvmetad is not active yet"
this solved to me https://forum.dug.net.pl/viewtopic.php?pid=292809
Re: Shell - escapes
On Tue, 10 May 2016 at 18:36, Die Optimisten wrote: > Hi, > > How can I escape a ' inside '...' > e.g. perl -e 'print '$ and a' '# I don't want to use " > > thank you > Andrew > > perl -e 'print '\''$ and a'\'' ' The things that might look like double quotes in the above depending on your font are actually two single quotes side by side. Mark
Re: Shell - escapes
'...' doesn't interpolate. push @f, '$ and a'; push @f, "'"; print join '', @f; If you want. I have a feeling YDIW and need to step back and present the actual problem. On May 10, 2016 05:36, "Die Optimisten" wrote: > Hi, > > How can I escape a ' inside '...' > e.g. perl -e 'print '$ and a' '# I don't want to use " > > thank you > Andrew > >
Re: bash Shell - escapes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 11:20:23AM +0200, Die Optimisten wrote: > On 2016-05-10 11:18, Die Optimisten wrote: > >Hi, > > > >How can I escape a ' inside '...' > >e.g. perl -e 'print '$ and a' '# I don't want to use " The short answer is... you can't. Quoting from the bash man page: "Enclosing characters in single quotes preserves the literal value of each character within the quotes. A single quote may not occur between single quotes, even when preceded by a backslash" The long answer is... this woldn't be a shell if there were no useful workarounds. The trick in this situation is just to break up the string. Be aware that to a shell, everything is text, so foo, "foo" and 'foo' are all (in some way) equivalent. This would work: perl -e 'print '"'"'$ and a'"'"' '# I don't want to use " That is, you glue your string out of several parts, here separated by spaces; only the embedded ' are quoted by "": 'print ' "'" '$ and a' "'" ' ' Of course, in practice you wouldn't do that blind transform, but optimize it a bit, e.g.: "print '"'$'" and ax ' " I.e. just use the '' where you need 'em Then, you can escape the $ whithin the "" with a \ Lots of ways, use whatever is most readable. hth - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcxtVcACgkQBcgs9XrR2kZmlgCffAw1D1VN5+S6M9QlMtzb+egm 9FcAn1VzNSS8Y0R+APMmc8r0fKUkIeV8 =F9uz -END PGP SIGNATURE-
Re: Shell - escapes
On Tuesday 10 May 2016 11:18:06 Die Optimisten wrote: > Hi, > > How can I escape a ' inside '...' > e.g. perl -e 'print '$ and a' '# I don't want to use " This seems to work: perl -e 'print '\''$ and a'\' It must be understood as the concatenation of these strings: * literal string: 'print ' * escaped \' * literal string: '$ and a' * escaped \' Frederic
Re: bash - shell events "!"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 11:32:47AM +0200, Die Optimisten wrote: > Hello > > echo hello!# displays that, BUT: > echo "Hello!" # tells: > -su: !": event not found# this worked years before without problem! > Is that intended? These leads to errors in many scripts (including > installig package dkms) > How can this be turned off? For me this behaviou should be changed, > for example: Events should contain whitespace before or after it, > or only work outside quoting... Note that this is only a problem in interactive mode. In batch mode the ! passes through undamaged. You can disable ! completely (look up the shell man page under 'HISTORY EXPANSION' to learn what it's good for), as has been said in this thread, or you can just escape a single ! with a backslash: \! regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcxtpMACgkQBcgs9XrR2kZ/EQCdFxlrN2Qi4FVkl+9PrsW2aWFo 0PoAn3z+03JhPj2u07aHAqQDogTCIXe9 =0Mp1 -END PGP SIGNATURE-
Re: cups (sharing network printer)
On Mon 09 May 2016 at 20:01:28 -0500, David Wright wrote: > On Mon 09 May 2016 at 23:22:44 (+0100), Brian wrote: > > On Mon 09 May 2016 at 23:45:18 +0200, deloptes wrote: > > > Pol Hallen wrote: > > > >> Unless I am misunderstanding the question, > > > > I need to print using 192.168.1.10 (server) not directly by network > > > > printer > > > > In /etc/cups/client.conf > > > > > > set the ServerName > > > > > > ServerName 192.168.1.10 > > > > > > try lpstat -a > > > > > > $ lpstat -a > > > HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST > > > > The OP talks about *"clients"*. Would your advice stay the same if there > > was a 1000 of them? > > Your first and last comments were too terse for me to understand. I > think you might be implying here that the solution doesn't scale well. The advice is fine as far as it goes and should work. It is a technique I use myself on a machine or two when I do not want a local cupsd or prefer not to have avahi-daemon on a print server with limited resources. Scaling is an issue and I do not know how one efficiently adopts to adding large number of clients or a change in the server's IP. The assumption is also being made that the server is online and available. Visitors on a network would have to be informed of the IP; this may be a hassle for them, particularly if they are unfamiliar with the device they are using or not comfortable with altering its settings. Visiting Big Company Boss would likely not be amused having to take a lesson in network configuration just to print. The reality is that mobile devices (laptops, phones etc) are probably more numerous than desktops. Linking them with a single infrastructure and pointing to a single server negates the advantages they have for printing. Devices using AirPrint should immediately be at home with Debian CUPS and really have no need of a client.conf. Also, if the network is down or there are network errors or the server is not available, the application may not retry and printing will be prevented. A user closing the lid on a laptop before an application has finished submitting a job is to be avoided; the job isn't going anywhere. > Can you explain the difference between the purported solution above > and your earlier "Set up the clients to discover the server. Print.", > ie how "Set up"? With a local cupsd a job can be queued and recovery from temporary issues is much easier. The local cupsd can coordinate with the OS to keep the system (and network stack) up long enough to send the job remotely. The client software can adapt to the network/location more easily (for example, when roaming). What is displayed in print dialogues of applications is what is actually online, not what may have disappeared a week ago and which you now have to re-locate. The "Set up" on a Jessie client consists of apt-get install cups The default for the installation is for print queues on a remote server to be offered by applications or displayed by 'lpstat -a'. Immediate printing capability, in other words.
Re: Shell - escapes
Hi, Die Optimisten wrote: > > How can I escape a ' inside '...' > > e.g. perl -e 'print '$ and a' ' Mark Fletcher wrote: > perl -e 'print '\''$ and a'\'' ' Or by ending the range of ' and packing the literal ' into double quotes: perl -e 'print '"'"'$ and a'"'"' ' consisting of these quotation pieces 'print ' "'" '$ and a' "'" ' ' If there was no $ in the text, one could do it more simply by packing the whole text into double quotes: perl -e "print '$ and a' " Have a nice day :) Thomas
Re: cups (sharing network printer)
try lpstat -a T640 accepting requests since Mon 09 May 2016 07:29:09 PM CEST Pol
Re: Shell - escapes
Hi, to...@tuxteam.de wrote: >perl -e 'print '"'"'$ and a'"'"' '# I don't want to use " You were faster than me. :)) > I.e. just use the '' where you need 'em I actually do it vice versa: If purely literal text is intended, i use '' where possible and escape only '. That's most safe because i do not have to ponder which character is interpreted and converted inside "" and which will stay as is. So it is also easy to program in C. Have a nice day :) Thomas
Re: cups (sharing network printer)
Please post the outputs of 'lpstat -t' on the server and a client. scheduler is running system default destination: T640 device for PDF: cups-pdf:/ device for T640: socket://192.168.1.220:9100 PDF accepting requests since Mon 09 May 2016 07:25:03 PM CEST T640 accepting requests since Tue 10 May 2016 01:00:30 PM CEST printer PDF is idle. enabled since Mon 09 May 2016 07:25:03 PM CEST printer T640 is idle. enabled since Tue 10 May 2016 01:00:30 PM CEST Pol
Re: Shell - escapes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 01:08:04PM +0200, Thomas Schmitt wrote: > Hi, > > to...@tuxteam.de wrote: > >perl -e 'print '"'"'$ and a'"'"' '# I don't want to use " > > You were faster than me. :)) > > > > I.e. just use the '' where you need 'em > > I actually do it vice versa: > If purely literal text is intended, i use '' where possible and > escape only '. > > That's most safe because i do not have to ponder which character > is interpreted and converted inside "" and which will stay as is. > So it is also easy to program in C. Good insight. This was my first cut as well, but I came from a slightly different angle: starting from '...', what would an automatic transformation look like? > Have a nice day :) same to you :-) - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcxxbQACgkQBcgs9XrR2kb7cACfXYcRaA+YSDCLzaQCL6S8sJFw b4wAni2zG9YVvh0LoCyn/GyWJ8xs6LgI =/y2Z -END PGP SIGNATURE-
Re: cups (sharing network printer)
On Tue 10 May 2016 at 13:12:14 +0200, Pol Hallen wrote: > >Please post the outputs of 'lpstat -t' on the server and a client. > > scheduler is running > system default destination: T640 > device for PDF: cups-pdf:/ > device for T640: socket://192.168.1.220:9100 > PDF accepting requests since Mon 09 May 2016 07:25:03 PM CEST > T640 accepting requests since Tue 10 May 2016 01:00:30 PM CEST > printer PDF is idle. enabled since Mon 09 May 2016 07:25:03 PM CEST > printer T640 is idle. enabled since Tue 10 May 2016 01:00:30 PM CEST Two outputs were asked for. Would you post the one for a client.
Re: Shell - escapes
> If there was no $ in the text, one could do it more simply by packing the whole text into double quotes: perl -e "print '$ and a' " > Have a nice day :) Thomas That's why I constructed that example :) I think it would be useful to have a (new, meta) quote, which fully hides contents from bash-interpretion so that (perl-)strings can be built without thinking of quoting/escaping. Would it be useful / possible to change '...' so that nothing _except_ \' ist interpreted, I think that would be a nice solution --- or use a new (unused???) character. - Is it worth to forward it to the bash-experts (perhaps sb of them reading this...) Thanks for that many answers! Andrew
Re: Shell - escapes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 01:54:35PM +0200, Die Optimisten wrote: > > If there was no $ in the text, one could do it more simply by > packing the whole text into double quotes: > perl -e "print '$ and a' " > > Have a nice day :) Thomas > > That's why I constructed that example :) > > I think it would be useful to have a (new, meta) quote, which fully > hides contents from bash-interpretion > so that (perl-)strings can be built without thinking of quoting/escaping. > Would it be useful / possible to change '...' so that nothing > _except_ \' ist interpreted, I think that would be a nice solution > --- or use a new (unused???) character. > - Is it worth to forward it to the bash-experts (perhaps sb of them > reading this...) You can try that, but be warned that shell (Unix) syntax in general and bash syntax in particular is a rather mature affair, result of many shaping forces (esp. compatibility to other shells and backward compatibility considerations). At this point in history it has achieved an exquisite equilibrium and there's a huge body of scripts to cater for. So motivation to change syntax at such a basic level is probably pretty low (and with a reason). If you are embedding longer scripts in your shell, consider using "here documents", which are more flexible wrt. embedded quotes. For one-liners, Thomas' solution works nicely. regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcx0gwACgkQBcgs9XrR2kb6TACfYgdtxEWKUq63xrKc8E53Gd/b QHoAn0/3IB0YTKnmSKVV6LDx6sFwR97A =KOjh -END PGP SIGNATURE-
Re: cups (sharing network printer)
On Tue 10 May 2016 at 12:58:13 +0200, Pol Hallen wrote: > >>try lpstat -a > > T640 accepting requests since Mon 09 May 2016 07:29:09 PM CEST Please test from your client with lp -d T640 ~/.profile Does the file print?
Re: Shell - escapes
On Tue, May 10, 2016 at 9:20 PM wrote: > > If you are embedding longer scripts in your shell, consider using > "here documents", which are more flexible wrt. embedded quotes. > For one-liners, Thomas' solution works nicely. > > Except that it does what the OP clearly said he does NOT want to do -- it uses double quotes.
Re: Shell - escapes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 01:14:57PM +, Mark Fletcher wrote: > On Tue, May 10, 2016 at 9:20 PM wrote: > > > > > If you are embedding longer scripts in your shell, consider using > > "here documents", which are more flexible wrt. embedded quotes. > > For one-liners, Thomas' solution works nicely. > > > > > Except that it does what the OP clearly said he does NOT want to do -- it > uses double quotes. I think in the thread it's explained nicely why it can't work with single quotes alone. For the non-single-quoted stretches you can of course do without double quotes (use backslash), but I think we are splitting hairs at this point. Thomas and me just guessed at the OP's intentions: (s)he didn't want double quotes to protect the $ in there. I think we guessed right :-) regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcx4JQACgkQBcgs9XrR2kZpjQCffzfOP5OuC771S28FItQjFus0 3ecAmgMIILeAmt1TdBuhVnXJHhDOMrjL =I5y2 -END PGP SIGNATURE-
Re: Shell - escapes
Hello,
On Tue, May 10, 2016 at 11:18:06AM +0200, Die Optimisten wrote:
> How can I escape a ' inside '...'
> e.g. perl -e 'print '$ and a' '# I don't want to use "
You can't, so if it were me I would use one of perl's alternatives
for single-quoted strings, such as:
perl -e 'print q{$ and a} '
http://perldoc.perl.org/perlop.html#Quote-and-Quote-like-Operators
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
> The optimum programming team size is 1.
Has Jurassic Park taught us nothing? — pfilandr
signature.asc
Description: Digital signature
How to find reason for sporadic chime from computer?
Suddenly, my computer has started emitting a chime sound at random times. (Roughly every 30 minutes or so, but with high variance.) I have found nothing else that correlates with this chiming. In particular, nothing changes on the screen (i.e., no pop-ups, dialogs, etc. show up). I normally disable all beeps and sound notifications on my system, so I find this behavior pretty disconcerting. How can I troubleshoot this? TIA! kj
Re: Shell - escapes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 10, 2016 at 01:36:22PM +, Andy Smith wrote:
> Hello,
>
> On Tue, May 10, 2016 at 11:18:06AM +0200, Die Optimisten wrote:
> > How can I escape a ' inside '...'
> > e.g. perl -e 'print '$ and a' '# I don't want to use "
>
> You can't, so if it were me I would use one of perl's alternatives
> for single-quoted strings, such as:
>
> perl -e 'print q{$ and a} '
>
> http://perldoc.perl.org/perlop.html#Quote-and-Quote-like-Operators
"There Is More Than a Way To Do It" :-)
By the way, this is recommended reading (back to the shell and
especially bash):
http://wiki.bash-hackers.org/
Enjoy
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlcx538ACgkQBcgs9XrR2ka7GgCfd2N8PaoE2ng7i4hPuASpH+up
/6IAmwSHaxmQVI9f9s3DhJAmARPHoPVw
=k8A/
-END PGP SIGNATURE-
Re: Shell - escapes
On Tue 10 May 2016 at 13:16:27 (+), Mark Fletcher wrote: > On Tue, May 10, 2016 at 9:20 PM wrote: > > If you are embedding longer scripts in your shell, consider using > > "here documents", which are more flexible wrt. embedded quotes. > > For one-liners, Thomas' solution works nicely. > > > Except that it does what the OP clearly said he does NOT want to do -- it > uses double quotes. It appears to me that the OP included that condition in order to persuade us that: (a) a new quoting mechanism is needed for building perl strings in shell: https://lists.debian.org/debian-user/2016/05/msg00403.html and (b) an old quoting mechanism should be changed: https://lists.debian.org/debian-user/2016/05/msg00388.html You can call me cynical if you wish. Cheers, David.
Re: How to find reason for sporadic chime from computer?
On Tue 10 May 2016 at 09:45:52 (-0400), Kynn Jones wrote: > Suddenly, my computer has started emitting a chime sound at random > times. (Roughly every 30 minutes or so, but with high variance.) I > have found nothing else that correlates with this chiming. In > particular, nothing changes on the screen (i.e., no pop-ups, dialogs, > etc. show up). > > I normally disable all beeps and sound notifications on my system, so > I find this behavior pretty disconcerting. > > How can I troubleshoot this? AFAICT xclock chimes on my desktop (non-randomly) even though I don't specify -chime when it starts. On my laptop (used in silent environments) I have this file: $ cat /etc/modprobe.d/whatever-you-like-to-name-it.conf # blacklist PC Speaker, particularly on the # laptop where it is far too strident blacklist pcspkr blacklist snd_pcsp # $ That should allow you to eliminate the beeper as the source. Cheers, David.
Re: Shell - escapes
Hi, > I think it would be useful to have a (new, meta) quote, which fully hides > contents from bash-interpretion The '' quote does this. It's simply impossible that an end quotation mark can be distinguished from a literal quotation mark. If there would be escaping of literal string end marks, then you get even more interpretation and conversion. So the solution with two kinds of quotation marks is the most simple, if you do not want to go to FORTRAN strings with length number and Hollerith constant: 5Hhello Unambiguous, ingenious, uncomfortable. The best alternative i know of would be an adjustable end mark. Before the string begins, one would adjust the environment to a character or string which surely is not part of the literal text. The Here Documents of the shell are an example of this design pattern. Get some unlikely text: $ uuidgen 2bf661c8-b400-43f3-addc-d2d75f018013 Announce and use it as delimiter: $ wc <<2bf661c8-b400-43f3-addc-d2d75f018013 ... text ... 2bf661c8-b400-43f3-addc-d2d75f018013 Regrettably, Here Documents let the shell fiddle with their text. $ wc -c < Would it be useful / possible to change One can switch from one shell to the other, one can even program an own shell. But i see very few chance that bash or dash upstream would accept any change or addition attempt about quoting. It is just too fundamental and there are viable ways to express a literal string. Have a nice day :) Thomas
Re: Shell - escapes
On Tue 10 May 2016 at 16:19:10 (+0200), Thomas Schmitt wrote: > Regrettably, Here Documents let the shell fiddle with their text. > > $ wc -c < $(echo hello) > x > 6 > > So this is not a way to express arbitrary literal text. $ wc -c <<"x" $(echo hello) x 14 $ Cheers, David.
Lượt khách truy cập rất nhiều...
Chào bạn listn, hôm bữa mình có liên hệ đến bạn mà ko thấy bạn trả lời.. mình thấy trang web của bạn có nhiều lượt người truy cập, nhưng trang web chưa có gắn hộp chat uhchat .net Hộp chát sẽ giúp khách truy cập nhắn tin với bạn ngay tại trang web và bạn cũng biết được số điện thoại của họ để liên lạc với họ sau này. Có gì bạn cứ vào trang uhchat .net mình sẽ gắn cho bạn dùng thử hộp chat này luôn bạn nhé.
Re: Shell - escapes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 10, 2016 at 04:19:10PM +0200, Thomas Schmitt wrote: > Regrettably, Here Documents let the shell fiddle with their text. > > $ wc -c < $(echo hello) > x > 6 > > So this is not a way to express arbitrary literal text. Not if you quote the delimiter cookie in single quotes (in bash, at least): | cat < the current shell is /bin/bash, I think but: | cat <<'EOT' | the current shell is $SHELL, I think | EOT | | => the current shell is $SHELL, I think A bit like Perl (or was it the other way 'round? ;-) > > Would it be useful / possible to change > > One can switch from one shell to the other, one can even program an > own shell. But i see very few chance that bash or dash upstream would > accept any change or addition attempt about quoting. It is just too > fundamental and there are viable ways to express a literal string. That's my take too. And I think the decision to move slowly, if ever does make a ton of sense in this context. regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlcx8MgACgkQBcgs9XrR2kZ3LwCdHCYhbwBUo5KlgsZJoxPOfuXO p58AnR+iq50k4Hk61RY59/0Fn4boEs64 =IIYV -END PGP SIGNATURE-
Re: Shell - escapes
Hi, i wrote: > > So this is not a way to express arbitrary literal text. David Wright wrote: > $ wc -c <<"x" Indeed. One more way to reach the goal. At least with bash and dash. Have a nice day :) Thomas
mutt attachment error
I tried to use mutt to send someone a zip file of about 50 Mb and got the error: "Error sending message, child exited 1 (). Could not send message." I assumed the attachment was too large and so went to /etc/exim4/conf.d/main/02*/ and altered the configuration to be: # Message size limit. The default (used when MESSAGE_SIZE_LIMIT # is unset) is 50 MB .ifdef MESSAGE_SIZE_LIMIT # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line message_size_limit = 200 MB # I added this line .endif I restarted exim, but it had no effect. Haines
dpkg: error: error executing hook
I just now installed several fresh security updates for Wheezy LTS and received the following error from dpkg (and I quote): dpkg: error: error executing hook 'if [ -x /usr/share/debian-security-support/check-support-status.hook ] ; then /usr/share/debian-security-support/check-support-status.hook ; fi', exit code 2560 E: Sub-process /usr/bin/dpkg returned an error code (2) I guess it won't kill me but is there anything I should do (apart from filing a bug report)? -- Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and so entirely in harmony with the demagogic appeals to cultural democracy that accompany (and distract one’s attention from) the ever-tightening grip of plutocratic capitalism. - Susan Sontag
Re: How to find reason for sporadic chime from computer?
Find computer's hardware manual and see if chiming is something your hardware will do no matter which operating system is in use to warn about impending undesireable hardware events. You may find a table with the different chime codes and may then find out why this now happens and what to do about it. On Tue, 10 May 2016, Kynn Jones wrote: Date: Tue, 10 May 2016 09:45:52 From: Kynn Jones To: Debian User Subject: How to find reason for sporadic chime from computer? Resent-Date: Tue, 10 May 2016 13:46:12 + (UTC) Resent-From: debian-user@lists.debian.org Suddenly, my computer has started emitting a chime sound at random times. (Roughly every 30 minutes or so, but with high variance.) I have found nothing else that correlates with this chiming. In particular, nothing changes on the screen (i.e., no pop-ups, dialogs, etc. show up). I normally disable all beeps and sound notifications on my system, so I find this behavior pretty disconcerting. How can I troubleshoot this? TIA! kj --
Re: mutt attachment error
On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote: > I tried to use mutt to send someone a zip file of about 50 Mb and got > the error: "Error sending message, child exited 1 (). Could not send > message." > > I assumed the attachment was too large and so went to > /etc/exim4/conf.d/main/02*/ and altered the configuration to be: > > # Message size limit. The default (used when MESSAGE_SIZE_LIMIT > # is unset) is 50 MB > .ifdef MESSAGE_SIZE_LIMIT > # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line > message_size_limit = 200 MB # I added this line > .endif > > I restarted exim, but it had no effect. Isn't the Debian way to put MESSAGE_SIZE_LIMIT=foo into /etc/exim4/update-exim4.conf.conf and then run # dpkg-reconfigure exim4-config where foo should be, perhaps, 200M or why not just 2 You've obviously remembered the overhead for mime. Pity your ISP! If your someone runs linux, you might try man split. Cheers, David.
Re: mutt attachment error
On Tue 10 May 2016 at 10:28:24 -0500, David Wright wrote: > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote: > > I tried to use mutt to send someone a zip file of about 50 Mb and got > > the error: "Error sending message, child exited 1 (). Could not send > > message." > > > > I assumed the attachment was too large and so went to > > /etc/exim4/conf.d/main/02*/ and altered the configuration to be: > > > > # Message size limit. The default (used when MESSAGE_SIZE_LIMIT > > # is unset) is 50 MB > > .ifdef MESSAGE_SIZE_LIMIT > > # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line > > message_size_limit = 200 MB # I added this line > > .endif > > > > I restarted exim, but it had no effect. > > Isn't the Debian way to put > > MESSAGE_SIZE_LIMIT=foo > > into /etc/exim4/update-exim4.conf.conf and then run > # dpkg-reconfigure exim4-config I think it is necessary only to restart exim after altering the file. I use the split configuration and put directives in my own file /etc/exim4/conf.d/main/00_custom_macros.
Re: mutt attachment error
David Wright wrote: > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote: >> I tried to use mutt to send someone a zip file of about 50 Mb and got >> the error: "Error sending message, child exited 1 (). Could not send >> message." >> >> I assumed the attachment was too large and so went to >> /etc/exim4/conf.d/main/02*/ and altered the configuration to be: >> >> # Message size limit. The default (used when MESSAGE_SIZE_LIMIT >> # is unset) is 50 MB >> .ifdef MESSAGE_SIZE_LIMIT >> # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line >> message_size_limit = 200 MB # I added this line >> .endif >> >> I restarted exim, but it had no effect. > Isn't the Debian way to put > MESSAGE_SIZE_LIMIT=foo > into /etc/exim4/update-exim4.conf.conf and then run > # dpkg-reconfigure exim4-config No, that won't work. You cannot just put stuff into /etc/exim4/update-exim4.conf.conf and hope it will make it into the configuration. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: mutt attachment error
On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote: > David Wright wrote: > > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote: > > >> I tried to use mutt to send someone a zip file of about 50 Mb and got > >> the error: "Error sending message, child exited 1 (). Could not send > >> message." > >> > >> I assumed the attachment was too large and so went to > >> /etc/exim4/conf.d/main/02*/ and altered the configuration to be: > >> > >> # Message size limit. The default (used when MESSAGE_SIZE_LIMIT > >> # is unset) is 50 MB > >> .ifdef MESSAGE_SIZE_LIMIT > >> # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line > >> message_size_limit = 200 MB # I added this line > >> .endif > >> > >> I restarted exim, but it had no effect. > > > Isn't the Debian way to put > > > MESSAGE_SIZE_LIMIT=foo > > > into /etc/exim4/update-exim4.conf.conf and then run > > # dpkg-reconfigure exim4-config > > No, that won't work. You cannot just put stuff into > /etc/exim4/update-exim4.conf.conf and hope it will make it into the > configuration. Didn't spot that; exim's .confs can be confusing. What file is used for non-split configuration?
Re: mutt attachment error
Brian wrote: > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote: >> David Wright wrote: >> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote: I tried to use mutt to send someone a zip file of about 50 Mb and got the error: "Error sending message, child exited 1 (). Could not send message." I assumed the attachment was too large and so went to /etc/exim4/conf.d/main/02*/ and altered the configuration to be: # Message size limit. The default (used when MESSAGE_SIZE_LIMIT # is unset) is 50 MB .ifdef MESSAGE_SIZE_LIMIT # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line message_size_limit = 200 MB # I added this line .endif I restarted exim, but it had no effect. >>> Isn't the Debian way to put >>> MESSAGE_SIZE_LIMIT=foo >>> into /etc/exim4/update-exim4.conf.conf and then run >>> # dpkg-reconfigure exim4-config >> >> No, that won't work. You cannot just put stuff into >> /etc/exim4/update-exim4.conf.conf and hope it will make it into the >> configuration. > Didn't spot that; exim's .confs can be confusing. The file /etc/exim4/update-exim4.conf.conf is the configuration file for the configuration generator, not Exim4 itself. > What file is used for non-split configuration? Have a look at /usr/share/doc/exim4/README.Debian.gz, Section 2.1.3 "Using Exim Macros to control the configuration" Everything is documented there and the following sections, on how to expand or override the configuration system provided by the Exim4 maintainers. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: mutt attachment error
Haines Brown wrote: > I tried to use mutt to send someone a zip file of about 50 Mb and got > the error: "Error sending message, child exited 1 (). Could not send > message." > I assumed the attachment was too large and so went to > /etc/exim4/conf.d/main/02*/ and altered the configuration to be: > # Message size limit. The default (used when MESSAGE_SIZE_LIMIT > # is unset) is 50 MB > .ifdef MESSAGE_SIZE_LIMIT > # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line > message_size_limit = 200 MB # I added this line > .endif > I restarted exim, but it had no effect. Of course it had no effect. The code snippet above (before your edit) does the following: If the Macro MESSAGE_SIZE_LIMIT is defined set the config option message_size_limit to the contents of MESSAGE_SIZE_LIMIT What you did was If the Macro MESSAGE_SIZE_LIMIT is defined set the config option message_size_limit to 200MB Since MESSAGE_SIZE_LIMIT is normally undefined, the code does nothing in both cases. What you need to do is to revert you changes and define MESSAGE_SIZE_LIMIT in a file called "/etc/exim4/exim4.conf.localmacros", which will then get included in the autogenerated config file. Please read /usr/share/doc/exim4/README.Debian.gz as everything is documented in there. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: pastebinning (was: Posts don't show on list)
> Gary Roach composed on 2016-04-30 12:08 (UTC-0700): > > >Someone said that I need to use a pastebin for images. I've never used > >one before so another Fxx Learning Experience. No, it's not necessary, in fact its preferable to not use pastebin. There's been other threads where this has been fleshed out. -- The media's the most powerful entity on earth. They have the power to make the innocent guilty and to make the guilty innocent, and that's power. -- Malcolm X
Re: Posting picture files
On Tue, May 03, 2016 at 12:41:10PM -0700, Gary Roach wrote: > > > You know, I thought I had tried switching themes with out success. I just > tried it again and the Oxygen theme cleared up the problem. So this is the solution to a problem in another thread? :/ -- The media's the most powerful entity on earth. They have the power to make the innocent guilty and to make the guilty innocent, and that's power. -- Malcolm X
Re: Posting picture files
On Sun, May 01, 2016 at 11:57:34AM -0400, Gene Heskett wrote: > On Sunday 01 May 2016 11:07:39 Sven Arvidsson wrote: > > > > "Do not submit an attachment larger than 10 KiB. Consider using > > paste.debian.net and including a link in your post." > > > > From https://wiki.debian.org/DebianMailingLists#Posting_Rules.2C_Guide > >lines.2C_and_Tips > > Thanks Sven. But it does seem rather archaic today, 100k would be a lot > more useful as attaching a well smunched screenshot is a lot less Well, it is a wiki. :) That certaily seems like a random joe blogs post, considering pastebin is not good for a user suport mailing list that archives its posts. -- The media's the most powerful entity on earth. They have the power to make the innocent guilty and to make the guilty innocent, and that's power. -- Malcolm X
Re: pastebinning (was: Posts don't show on list)
On 10 May 2016 at 19:18, wrote: > > Gary Roach composed on 2016-04-30 12:08 (UTC-0700): > > > > >Someone said that I need to use a pastebin for images. I've never used > > >one before so another Fxx Learning Experience. > > No, it's not necessary, in fact its preferable to not use pastebin. > There's been other threads where this has been fleshed out. > I think we need a pastebin for OCD tidy types to post their gripes and exhortations and another separate one for Finnegan's Wake type OT discussions and rants. Both need to have really long and complex learning curves and be encrypted. Regards MF > -- > The media's the most powerful entity on earth. > They have the power to make the innocent guilty > and to make the guilty innocent, and that's power. > -- Malcolm X > > -- Climostat Ltd Rm 5169 The Heath Business & Technical Park The Heath Runcorn Cheshire WA7 4QX Tel. 01 928 515 015
Re: mutt attachment error
On Tue 10 May 2016 at 19:58:36 +0200, Sven Hartge wrote: > Brian wrote: > > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote: > >> David Wright wrote: > >>> Isn't the Debian way to put > > >>> MESSAGE_SIZE_LIMIT=foo > > >>> into /etc/exim4/update-exim4.conf.conf and then run > >>> # dpkg-reconfigure exim4-config > >> > >> No, that won't work. You cannot just put stuff into > >> /etc/exim4/update-exim4.conf.conf and hope it will make it into the > >> configuration. > > > Didn't spot that; exim's .confs can be confusing. > > The file /etc/exim4/update-exim4.conf.conf is the configuration file for > the configuration generator, not Exim4 itself. > > > What file is used for non-split configuration? > > Have a look at /usr/share/doc/exim4/README.Debian.gz, Section 2.1.3 > "Using Exim Macros to control the configuration" /usr/share/doc/exim4-config/README.Debian.gz or /usr/share/doc/exim4-base/README.Debian.gz on my system. (the "light" version of exim4). > Everything is documented there and the following sections, on how to > expand or override the configuration system provided by the Exim4 > maintainers. You have jogged my memory as to why I have 00_custom_macros with my split configuration of many years.
Re: Posting picture files
On Wed 11 May 2016 at 06:36:43 +1200, cbannis...@slingshot.co.nz wrote: > On Sun, May 01, 2016 at 11:57:34AM -0400, Gene Heskett wrote: > > On Sunday 01 May 2016 11:07:39 Sven Arvidsson wrote: > > > > > > "Do not submit an attachment larger than 10 KiB. Consider using > > > paste.debian.net and including a link in your post." > > > > > > From https://wiki.debian.org/DebianMailingLists#Posting_Rules.2C_Guide > > >lines.2C_and_Tips > > > > Thanks Sven. But it does seem rather archaic today, 100k would be a lot > > more useful as attaching a well smunched screenshot is a lot less > > Well, it is a wiki. :) Which anyone, including you, can contribute to. :)
Re: all at a sudden Firefox
On Sun, May 01, 2016 at 08:39:58PM +0100, Lisi Reisz wrote: > On Sunday 01 May 2016 19:43:37 Curt wrote: > > As far as here goes, in mixed company, the masculine form takes > > precedence (which may or may not have anything to do with anything). > > Depending. "Guys" can indeed sometimes be used as the common gender, and it > is "man"kind. But I object to "Sirs"!!! Me too! I definitely haven't been knighted. -- The media's the most powerful entity on earth. They have the power to make the innocent guilty and to make the guilty innocent, and that's power. -- Malcolm X
Re: all at a sudden Firefox
While I agree with the general principle, "guys" doesn't really work in mixed company (most women definitely do not want to be "one of the guys"). "People" probably works better. But it might give one second thoughts about using the word "guy" at all if one knew the origin of the word: It comes from Guy Fawkes and originally referred to his effigy traditionally hanged on Guy Fawkes Day. John L. Ries Salford Systems Phone: (619)543-8880 x107 or (435)867-8885 From: cbannis...@slingshot.co.nz Sent: Tuesday, May 10, 2016 2:05 PM To: debian-user@lists.debian.org Subject: Re: all at a sudden Firefox On Sun, May 01, 2016 at 08:39:58PM +0100, Lisi Reisz wrote: > On Sunday 01 May 2016 19:43:37 Curt wrote: > > As far as here goes, in mixed company, the masculine form takes > > precedence (which may or may not have anything to do with anything). > > Depending. "Guys" can indeed sometimes be used as the common gender, and it > is "man"kind. But I object to "Sirs"!!! Me too! I definitely haven't been knighted. -- The media's the most powerful entity on earth. They have the power to make the innocent guilty and to make the guilty innocent, and that's power. -- Malcolm X
Re: mutt attachment error
On Tue, 10 May 2016 17:03:47 +0100 Brian wrote: >On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote: > >> David Wright wrote: >> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote: >> >> >> I tried to use mutt to send someone a zip file of about 50 Mb and got >> >> the error: "Error sending message, child exited 1 (). Could not send >> >> message." >> >> >> >> I assumed the attachment was too large and so went to >> >> /etc/exim4/conf.d/main/02*/ and altered the configuration to be: >> >> >> >> # Message size limit. The default (used when MESSAGE_SIZE_LIMIT >> >> # is unset) is 50 MB >> >> .ifdef MESSAGE_SIZE_LIMIT >> >> # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line >> >> message_size_limit = 200 MB # I added this line >> >> .endif >> >> >> >> I restarted exim, but it had no effect. >> >> > Isn't the Debian way to put >> >> > MESSAGE_SIZE_LIMIT=foo >> >> > into /etc/exim4/update-exim4.conf.conf and then run >> > # dpkg-reconfigure exim4-config >> >> No, that won't work. You cannot just put stuff into >> /etc/exim4/update-exim4.conf.conf and hope it will make it into the >> configuration. > >Didn't spot that; exim's .confs can be confusing. What file is used for >non-split configuration? > Not meaning to send this to you, Brian, but I lost the previous message. I would like to know that, too. Since /etc/exim4/update-exim4.conf.conf has the following at the beginning: # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' That would seem to me to be the way to make it work. -- Charlie Kravetz Linux Registered User Number 425914 [http://linuxcounter.net/user/425914.html] Never let anyone steal your DREAM. [http://keepingdreams.com]
Re: all at a sudden Firefox
On Tue, 10 May 2016 19:16:30 + "John L. Ries" wrote: > > gender, and it is "man"kind. But I object to "Sirs"!!! > > Me too! I definitely haven't been knighted. > None of my male teachers had, either, but... -- Joe
Re: mutt attachment error
On Tue 10 May 2016 at 12:56:47 -0600, Charlie Kravetz wrote: > On Tue, 10 May 2016 17:03:47 +0100 > Brian wrote: > > > >Didn't spot that; exim's .confs can be confusing. What file is used for > >non-split configuration? > > > > Not meaning to send this to you, Brian, but I lost the previous message. > > I would like to know that, too. Since /etc/exim4/update-exim4.conf.conf > has the following at the beginning: >From a previous Sven Hartge post https://lists.debian.org/debian-user/2016/05/msg00426.html you need to use "a file called "/etc/exim4/exim4.conf.localmacros", which will then get included in the autogenerated config file". I've not tried it but the advice looks kosher. > # /etc/exim4/update-exim4.conf.conf > # > # Edit this file and /etc/mailname by hand and execute update-exim4.conf > # yourself or use 'dpkg-reconfigure exim4-config' > > That would seem to me to be the way to make it work. /etc/exim4/update-exim4.conf.conf is for configuring how Debian's exim4 basically works for sending or receiving mail, not for setting exim4 specific parameters which modify the sending or receiving.
Re: pastebinning (was: Posts don't show on list)
On Tuesday 10 May 2016 19:42:41 Michael Fothergill wrote: > On 10 May 2016 at 19:18, wrote: > > > Gary Roach composed on 2016-04-30 12:08 (UTC-0700): > > > >Someone said that I need to use a pastebin for images. I've never used > > > >one before so another Fxx Learning Experience. > > > > No, it's not necessary, in fact its preferable to not use pastebin. > > There's been other threads where this has been fleshed out. > > I think we need a pastebin for OCD tidy types to post their gripes and > exhortations and another separate one for Finnegan's Wake type OT > discussions and rants. > > Both need to have really long and complex learning curves and be encrypted. > > Regards > > MF Were you referring to the ballad or the book? If the book then the steep learning curve and encryption is already there, not so? Eike
Re: pastebinning (was: Posts don't show on list)
On 10 May 2016 at 21:03, Eike Lantzsch wrote: > On Tuesday 10 May 2016 19:42:41 Michael Fothergill wrote: > > On 10 May 2016 at 19:18, wrote: > > > > Gary Roach composed on 2016-04-30 12:08 (UTC-0700): > > > > >Someone said that I need to use a pastebin for images. I've never > used > > > > >one before so another Fxx Learning Experience. > > > > > > No, it's not necessary, in fact its preferable to not use pastebin. > > > There's been other threads where this has been fleshed out. > > > > I think we need a pastebin for OCD tidy types to post their gripes and > > exhortations and another separate one for Finnegan's Wake type OT > > discussions and rants. > > > > Both need to have really long and complex learning curves and be > encrypted. > > > > Regards > > > > MF > > Were you referring to the ballad or the book? > I meant the book. It is hard going but if it was posted up in a really tough mark up language and you had to run your own decryption algorithm to hack in and upload it that would that would make it the ultimate pesky pastebin neat freak purity test. MF > If the book then the steep learning curve and encryption is already there, > not > so? > > Eike > > -- Climostat Ltd Rm 5169 The Heath Business & Technical Park The Heath Runcorn Cheshire WA7 4QX Tel. 01 928 515 015
Re: mutt attachment error
On Wed, 11 May 2016 at 04:43, Brian wrote: > On Tue 10 May 2016 at 12:56:47 -0600, Charlie Kravetz wrote: > > > On Tue, 10 May 2016 17:03:47 +0100 > > Brian wrote: > > > > > >Didn't spot that; exim's .confs can be confusing. What file is used for > > >non-split configuration? > > > > > > > Not meaning to send this to you, Brian, but I lost the previous message. > > > > I would like to know that, too. Since /etc/exim4/update-exim4.conf.conf > > has the following at the beginning: > > >From a previous Sven Hartge post > > https://lists.debian.org/debian-user/2016/05/msg00426.html > > you need to use "a file called "/etc/exim4/exim4.conf.localmacros", > which will then get included in the autogenerated config file". I've > not tried it but the advice looks kosher. > > > # /etc/exim4/update-exim4.conf.conf > > # > > # Edit this file and /etc/mailname by hand and execute update-exim4.conf > > # yourself or use 'dpkg-reconfigure exim4-config' > > > > That would seem to me to be the way to make it work. > > /etc/exim4/update-exim4.conf.conf is for configuring how Debian's exim4 > basically works for sending or receiving mail, not for setting exim4 > specific parameters which modify the sending or receiving. > > So where would you advocate putting, say, the IP address exim should listen on? Mark
Re: all at a sudden Firefox
On Tuesday 10 May 2016 20:16:30 John L. Ries wrote: > traditionally hanged on Guy Fawkes Day. No, traditionally burned on Guy Fawkes Day. Lisi
jessie: can't install that which found
# aptitude search iceape ... c iceape-browser- Iceape Navigator (Internet browser) and Composer c iceape-chatzilla - Iceape Chatzilla IRC client v iceape-dom-inspector - c iceape-mailnews - Iceape Mail & Newsgroups and Address Book v iceape-noscript - v iceape-openinbrowser - ... # aptitude install iceape-browser No candidate version found for iceape-browser No candidate version found for iceape-browser No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. What? How can a package manager find a package yet refuse to find it when directed to install it? Same problem with apt-get. ??? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
dist-upgrade: Current status: 0 broken [~42], 0 updates [~880], 24238 new [~79]
That's the last last line printed to screen as a result of a dist-upgrade from Wheezy to Jessie. What do the numbers actually refer to, particularly those within [ ]? Space consumed on 19G / before starting was ~39%, after, ~71%. I actually did two dist-upgrades, doing Squeeze to Wheezy first. The Squeeze installation featured TDE as primary DE. Jessie somehow was turned into Gnome, with both libreoffice and openoffice installed. Purging openoffice* and gnome* followed by autoremove brought / consumption down to ~60%. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
clamtk freetuxtv lxde-logout, rant for "essential user perspective"
Dear fellow debian users, I am grateful for the efforts that goes into debian gnu/linux. One observation: In this list more users, less email traffic represent scissors graphic and we are there. Let there be hope. Freetuxtv can pass synching channels in jessie. Original support site says it was fixed in version long-time-ago. Where is the log-jam? ClamTK GUI auto-updates invent update ready message, yet never update. Is there another option in the repository with GUI. LXDE panel-logout launcher button on right end of the pannel is lost. Some say because counsel-kit was bumped out by systemd?! As a discussion concluded in a forum on the n-th take, elsewhere (May be some Lubuntu forum on the web). So, against the wonders of scientists this counter-balancing weight has to be dropped on the other scale-pan and may count for users' perspective: "I like state of the art features, pray tell me how do I add again?" :) Best wishes to you all, hec.
Re: Shell - escapes
On 05/10/2016 06:36 AM, Andy Smith wrote:
perl -e 'print q{$ and a} '
+1
David
Re: jessie: can't install that which found
https://packages.debian.org/search?suite=jessie&arch=any&mode=filename&searchon=contents&keywords=iceape actually I have no such package. с - it means that when the package is installed, but not purged from the system. On 11.05.2016 04:25, Felix Miata wrote: What? How can a package manager find a package yet refuse to find it when directed to install it? Same problem with apt-get. ??? -- Sincerely, Gavrilov Aleksey System Administrator Ltd. "Hearst Shkulev Digital Rugion" tel .: 8 (351) 729-94-90, ext. 345 mob. +7 999 581 7934 gavri...@info74.ru Chelyabinsk, st. Melkombinat February 1st Precinct, 18, office 208 for TRC `Rodnik`
Re: dist-upgrade: Current status: 0 broken [~42], 0 updates [~880], 24238 new [~79]
Felix Miata wrote: > That's the last last line printed to screen as a result of a dist-upgrade > from Wheezy to Jessie. What do the numbers actually refer to, particularly > those within [ ]? > > Space consumed on 19G / before starting was ~39%, after, ~71%. I actually > did two dist-upgrades, doing Squeeze to Wheezy first. > > The Squeeze installation featured TDE as primary DE. Jessie somehow was > turned into Gnome, with both libreoffice and openoffice installed. Purging > openoffice* and gnome* followed by autoremove brought / consumption down > to ~60%. Hi Felix, I upgraded time ago following the upgrade guides. All worked fine back then. Did you do upgrade followed by dist-upgrade? I don't use aptitude - those [] seem to be coming from there, but from what I've heard apt-get should be better. regards
