Re: dselect, init and systemd-sysv
On Sun, 17 Jan 2016 11:26:54 +0100 Aldo Maggi <aldoma...@katamail.com> wrote: > Yesterday while updating my system via dselect (I'm using testing) > I've received the warning that "init and systemd-sysv" were going to > be uninstalled and I had to approve or deny that action. You have to be prepared to face things like this if you're using testing. If you want everything to work peachy-perfect, use stable. I had the same problem a few days ago, back when I was still using testing. A whole host of issues and buggy packages led me to learn from my folly and switch to stable, of which I am a proud user once more. If you must continue using testing for some reason, be prepared to put up with problems such as these; they are manifold (occasionally). > I've thought that as in previous cases (to be frank not recently but > many years ago) there was a mistake, since looking at the packages > which were going to be installed it didn't seem that a replacement > was present, therefore I've stopped the updating. > This morning I've tried again but got the same warning. > So I've used apt-get update && apt-get upgrade, in this case no > warning appears and systemd-sysv appears among the pkgs to be > upgraded. This should already be a sign that apt-get and aptitude are vastly superior to dselect. dselect hasn't been the preferred dpkg frontend since woody. > Is dselect still working safely or should I give up and change > package mgr? Use apt-get. Seriously. The latest documentation for dselect is from woody, and 14 years old (2002): https://www.debian.org/releases/woody/i386/ch-main.en.html
Re: dselect, init and systemd-sysv
On Sun, 17 Jan 2016 12:00:02 +0100, Aldo Maggi wrote: > Yesterday while updating my system via dselect (I'm using testing) I've > received the warning that "init and systemd-sysv" were going to be > uninstalled and I had to approve or deny that action. > I've thought that as in previous cases (to be frank not recently but > many years ago) there was a mistake, since looking at the packages which > were going to be installed it didn't seem that a replacement was > present, therefore I've stopped the updating. > This morning I've tried again but got the same warning. > So I've used apt-get update && apt-get upgrade, in this case no warning > appears and systemd-sysv appears among the pkgs to be upgraded. > > Is dselect still working safely or should I give up and change package > mgr? > > Many thanks > > Aldo Without seeing the specific message output by dselect it isn't possible to say for sure- but I would guess that your testing system is trying to do a dist-upgrade, and in the process switching your init to the new default, systemd. If you don't want this to happen then it might be prevented by installing the systemd-shim package IIRC. If you're confused by the behavior of dselect I recommend using the `apt` tool instead, or one of `aptitude` or `apt-get`. Again, without the specific output messages you are seeing it's not possible to properly diagnose the situation- so everything I'm saying here could be entirely wrong!
dselect, init and systemd-sysv
Yesterday while updating my system via dselect (I'm using testing) I've received the warning that "init and systemd-sysv" were going to be uninstalled and I had to approve or deny that action. I've thought that as in previous cases (to be frank not recently but many years ago) there was a mistake, since looking at the packages which were going to be installed it didn't seem that a replacement was present, therefore I've stopped the updating. This morning I've tried again but got the same warning. So I've used apt-get update && apt-get upgrade, in this case no warning appears and systemd-sysv appears among the pkgs to be upgraded. Is dselect still working safely or should I give up and change package mgr? Many thanks Aldo
dselect, init and systemd-sysv
Yesterday while updating my system via dselect (I'm using testing) I've received the warning that "init and systemd-sysv" were going to be uninstalled and I had to approve or deny that action. I've thought that as in previous cases (to be frank not recently but many years ago) there was a mistake, since looking at the packages which were going to be installed it didn't seem that a replacement was present, therefore I've stopped the updating. This morning I've tried again but got the same warning. So I've used apt-get update && apt-get upgrade, in this case no warning appears and systemd-sysv appears among the pkgs to be upgraded. Is dselect still working safely or should I give up and change package mgr? Many thanks Aldo
Re: dselect in wheezy; Old timers question
On Sat, 2013-12-14 at 16:09 -0600, Selim T. Erdogan wrote: John W. Foster, 14.12.2013: I'm managing a couple of remote VPS servers with no GUI access except putty. I have been using dselect to assist with this process up to yesterday it worked well as it has for years. I did a apt-get distupgrade and all went as expected and the system is running fine. However after I did the upgrade from old stable to wheezy, I decided that I needed to get an upgraded openjdk-7-jre installed for the game systems I'm running. When I did that the dselect decided I needed a lot of extra stuff to go along and I hit 'ctrl x' to abandon those changes. I reloaded the selections available and went into get ONLY the jre that I needed using apt-get install the entire load of X related stuff popped up. Now I have tried to clear the caches of dselect and apt but they all seem stuck. Running apt-get clean autoclean do not clear the dselect picked dependencies. Any ideas on how to get the dependencies suggested selections cleared out. Hello, fellow dselect old-timer. :) You should have hit X, not Ctrl-X, Anyway, here's what 'man dselect' says: If you mistakenly establish some settings and wish to revert all the selections to what is currently installed on the system, press the 'C' key. This is somewhat similar to using the unhold command on all pack‐ ages, but provides a more obvious panic button in cases where the user pressed enter by accident. (The previous paragraph was about using X to back out changes. The screen in which you should have done that is the context of the pressed enter by accident.) I never tried this. Let us know how it works. worked exactly as stated. Sorry I didn't even think of checking the man pages. I've been usin dselect for decades just 'thought' I knew what I was doing LOL just go's to show.. Thanks John -- !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 TRANSITIONAL//EN HTML HEAD META HTTP-EQUIV=Content-Type CONTENT=text/html; CHARSET=UTF-8 META NAME=GENERATOR CONTENT=GtkHTML/4.4.4 /HEAD BODY John FosterBR BR /BODY /HTML -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1387283481.31576.1.ca...@beast.johnwfoster.com
dselect in wheezy; Old timers question
I'm managing a couple of remote VPS servers with no GUI access except putty. I have been using dselect to assist with this process up to yesterday it worked well as it has for years. I did a apt-get distupgrade and all went as expected and the system is running fine. However after I did the upgrade from old stable to wheezy, I decided that I needed to get an upgraded openjdk-7-jre installed for the game systems I'm running. When I did that the dselect decided I needed a lot of extra stuff to go along and I hit 'ctrl x' to abandon those changes. I reloaded the selections available and went into get ONLY the jre that I needed using apt-get install the entire load of X related stuff popped up. Now I have tried to clear the caches of dselect and apt but they all seem stuck. Running apt-get clean autoclean do not clear the dselect picked dependencies. Any ideas on how to get the dependencies suggested selections cleared out. Thanks John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1387034479.16886.10.ca...@beast.johnwfoster.com
Re: dselect in wheezy; Old timers question
Perhaps using the Aptitude UI (Ncurses TUI) will let you unselect the currently selected packages. - Nate -- The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true. Ham radio, Linux, bikes, and more: http://www.n0nb.us -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131214185601.gu14...@n0nb.us
Re: dselect in wheezy; Old timers question
John W. Foster, 14.12.2013: I'm managing a couple of remote VPS servers with no GUI access except putty. I have been using dselect to assist with this process up to yesterday it worked well as it has for years. I did a apt-get distupgrade and all went as expected and the system is running fine. However after I did the upgrade from old stable to wheezy, I decided that I needed to get an upgraded openjdk-7-jre installed for the game systems I'm running. When I did that the dselect decided I needed a lot of extra stuff to go along and I hit 'ctrl x' to abandon those changes. I reloaded the selections available and went into get ONLY the jre that I needed using apt-get install the entire load of X related stuff popped up. Now I have tried to clear the caches of dselect and apt but they all seem stuck. Running apt-get clean autoclean do not clear the dselect picked dependencies. Any ideas on how to get the dependencies suggested selections cleared out. Hello, fellow dselect old-timer. :) You should have hit X, not Ctrl-X, Anyway, here's what 'man dselect' says: If you mistakenly establish some settings and wish to revert all the selections to what is currently installed on the system, press the 'C' key. This is somewhat similar to using the unhold command on all pack‐ ages, but provides a more obvious panic button in cases where the user pressed enter by accident. (The previous paragraph was about using X to back out changes. The screen in which you should have done that is the context of the pressed enter by accident.) I never tried this. Let us know how it works. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131214220953.ga12...@cs.utexas.edu
Re: no .info info on info (was Re: dselect fun)
I was speaking about the integrated aptitude help page, which is using exactly same interface as info. ah, now i understand. at least, i think i do. i'm assuming by exactly the same interface you mean they both take input from and provide output to a terminal? since that describes practically every tool i use, you had me confused for a second. (perhaps i still am?) Since it uses the same interfaces, my mind merged those informations without asking me! It should ask... :P you must have clicked the do not show this message again box. This interface is accessible when you run aptitude in ncurse mode, then, I think you'll find your way. i will try to remember your optimism when the time comes. The common problem with man, is when things come to non CLI interface: for ncurses and X GUI, man does not sounds really efficient. ah, i see. aptitude is primarily an interactive tool, so its primary documentation can be internal to the application, and accessed while you are interacting with it. interesting point. i get it now. Man was never something hard for me. I think it is because I discovered less and immediately fall in love with that tool (I previously only known the more tool from DOS, it explains my love I think). they do say that less provides more functionality. ;) unfortunately, in debian, afaik until one installs texinfo-doc-nonfree Oh, I'll check it out. Having doc for info could potentially help me a lot! cool. three more things. well, four: 1. there exists a --vi-keys command line option for info that advertises itself as being more like less and vi. i'm not a vi user, so i don't use it. but when you are using this option, `H' provides a listing of the appropriate key bindings. 2. to run info run within emacs: `ESC x info'. 3. i haven't tried pinfo, mentioned by another poster. (thanks, brian.) the package description mentions that it has lynx-like key bindings. 4. as long as i'm spamming the list, there's a description of a dozen basic info commands below. cheers, wes === basic info commands === there are other commands, many of them useful, but the six pairs below are good to understand. 1 nodes=pages: an ontological conundrum === technological breakthroughs of the previous century now permit the publication of documents whose pages are not of uniform length. therefore, we need new words. (wait, what?) in an info document, a node is a page that covers a given topic. (because documents are trees, and a tree is an arrangement of things called nodes.) let's move on. 2 forwards and backwards `]' and `[' page through a document's nodes like the pages of a book---one node after the other, in the sequence they'd show up if each node were a page in a book. `]' looks forward and `[' looks back. since sometimes all the text in a node doesn't fit into one screenful, there are also SPACE and BACKSPACE (or perhaps DEL instead). SPACE moves forward. the other one goes the other way. if an ascii-art flip book were set in info format, then holding down `]' would be play, and releasing it would be pause. but if it were a pornographic ascii-art flip book and the interesting parts didn't show up on the first screenful of a node, then in order to pollute your innocence you'd have to SPACE through them. if you accidentally spaced past the best frame, you might use BACKSPACE to go back to it. 3 documents are trees = the information in a piece of documentation is structured by its generality (some topics are subtopics of others). by convention, up is general, down is specific. also, when a given topic requires the discussion of several distinct subtopics of equivalent generality, they are arranged in a particular sequence. (Q: why? A: excellent question.) so, count them: *two* dimensions. whoa. 3.1 down and up: dimension one == anyways, `m' (menu) moves down into more specific topics, and `u' (up) moves back up into more general ones. to go down into a subtopic with `m', you'll need to specify which one. start typing its name, and hit TAB when you get sick of typing. tab completion works. (if you change your mind about the whole menu thing, do control-g to cancel. depending on how much there is to cancel, you might need to hit it twice.) 3.2 next and previous: the next dimension = also, when you're looking at a subtopic (`balloons', let's say) of some topic (maybe `loud things'), then `n' (next) moves on to the next loud thing (perhaps `fire engines'). `p' (previous) will go back to the previous loud thing (probably `barking dogs', in this case). nb: if your current subtopic (let's stick with `balloons') has subtopics of its own (`inflation', `static electricity', etc) and you hit `n', you will not see them. why? because `n' at `balloons' takes you to
Re: no .info info on info (was Re: dselect fun)
Le Dim 27 janvier 2013 17:02, wes davidson a écrit : hi morel. you wrote: Note: I did not read the info page of aptitude. i think perhaps there does not exist such a document for aptitude. if i am wrong about this, i would be grateful to learn where it can be obtained. Hum... maybe not info by info command in fact (I have no way to try it for now, and I'll have forgot when I'll be able, this evening ;) ). I was speaking about the integrated aptitude help page, which is using exactly same interface as info. Since it uses the same interfaces, my mind merged those informations without asking me! It should ask... :P This interface is accessible when you run aptitude in ncurse mode, then, I think you'll find your way. when i first read a unix man page twenty years ago, i had a rather similar reaction. it took me an embarrassingly long time to screw in the lightbulb and do 'man man'. (perhaps i am a closet homophobe.) Man was never something hard for me. I think it is because I discovered less and immediately fall in love with that tool (I previously only known the more tool from DOS, it explains my love I think). i am not sure which document you refer to, here. info has a manpage, which is indeed not terribly helpful to the novice. it is, after all, a manpage, and manpages are not intended to be helpful to novices. The common problem with man, is when things come to non CLI interface: for ncurses and X GUI, man does not sounds really efficient. but there exists a much more extensive document in .info format (namely info.info), geared toward the novice user, including a tutorial that i personally found very helpful. Did not found it. Where is it? I usually try to simply run the software alone to explore it's menus and/or try common shortcuts like F1, CTRL+H, ? and alike. unfortunately, in debian, afaik until one installs texinfo-doc-nonfree Oh, I'll check it out. Having doc for info could potentially help me a lot! ps: please do not mistake my unhealthy interest in the info system for some kind of pushy advocacy. i merely seek (perhaps unsuccessfully) to clarify its accessibility. No problem, and thanks for the tips. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6054cd6a72fac3824e0a293f7ce5de9e.squir...@www.sud-ouest.org
Re: no .info info on info (was Re: dselect fun)
On Sun 27 Jan 2013 at 11:02:22 -0500, wes davidson wrote: hi morel. you wrote: I do not like info at all: this is a software which pretends to help you, but you have to learn how it works before being able to use it. when i first read a unix man page twenty years ago, i had a rather similar reaction. it took me an embarrassingly long time to screw in the lightbulb and do 'man man'. (perhaps i am a closet homophobe.) Reading info pages with pinfo has never been a chore for me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130128175200.GI3027@desktop
no .info info on info (was Re: dselect fun)
hi morel. you wrote: Note: I did not read the info page of aptitude. i think perhaps there does not exist such a document for aptitude. if i am wrong about this, i would be grateful to learn where it can be obtained. i am aware of various manpages and the html documentation for aptitude, which i do have, and which are fine as far as they go. but if (say) the html doc were converted to .info format, i would find it more convenient to browse. I do not like info at all: this is a software which pretends to help you, but you have to learn how it works before being able to use it. when i first read a unix man page twenty years ago, i had a rather similar reaction. it took me an embarrassingly long time to screw in the lightbulb and do 'man man'. (perhaps i am a closet homophobe.) likewise, it was initially somewhat frustrating to learn how to use info. iirc, most of the frustration was due to the absence of /usr/share/info/info.info (or some analogous file) on the system i used at the time. 'info info' just brought up a manpage in an obnoxiously unfamiliar reader. in other words, on that system, there was no .info info on info! And, it's info manual is just useless. i am not sure which document you refer to, here. info has a manpage, which is indeed not terribly helpful to the novice. it is, after all, a manpage, and manpages are not intended to be helpful to novices. but there exists a much more extensive document in .info format (namely info.info), geared toward the novice user, including a tutorial that i personally found very helpful. on a system with this latter document installed, 'info info' renders it in the info reader. unfortunately, in debian, afaik until one installs texinfo-doc-nonfree from the non-free repositories, the files for this self-documentation don't exist on the system, and 'info info' will merely render info's manpage unto the unsuspecting newb. cheers, wes davidson ps: please do not mistake my unhealthy interest in the info system for some kind of pushy advocacy. i merely seek (perhaps unsuccessfully) to clarify its accessibility. - `But the plans were on display...' `On display? I eventually had to go down to the cellar to find them.' `That's the display department.' `With a torch.' `Ah, well the lights had probably gone.' `So had the stairs.' `But look you found the notice didn't you?' `Yes,' said Arthur, `yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying BEWARE OF THE LEOPARD.' On 2013-01-27 in 'dselect fun', berenger.mo...@neutralite.org wrote: Note: I did not read the info page of aptitude. I do not like info at all: this is a software which pretends to help you, but you have to learn how it works before being able to use it. And, it's info manual is just useless. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1301270853200.23...@brutus.ling.ohio-state.edu
Re: dselect fun
Le 24.01.2013 22:01, Richard Owlett a écrit : Chris Bannister wrote: On Wed, Jan 23, 2013 at 09:54:17AM +, Darac Marjal wrote: chime in with a reminder that dselect is considered discouraged these days. It's spiritual successor (a TUI interface to apt) is now aptitude. That depends on who you ask. For newbies, I certainly wouldn't recommend dselect, but if they wanted to use it I certainly wouldn't discourage them from doing so. In fact, if they can get their head around dselect, then anything else that is thrown at them will probably seem like a piece of cake. As to the overall Linux market there are at least two distinct classes of newbies. There is the class who is targeted by the Canonical (cf Microsoft) mentality - Big Brother knows best. There is class who wants the best from his system. BEST is not a simple one dimensional parameter. When I was in school a strong emphasis was placed on first principles. I think Debian could benefit from that outlook. I.E. Use the intuitive/user friendly/simple/simplistic interface(s) when appropriate. But know hat goes on under the hood. I'll follow the later route. I started my transition from Windows to Linux over two years ago. I could have had a system up in a day. But I don't see how it would have been significantly better/ than (insert your least favorite OS implementation here). I'll continue to pursue the back to basics route. I do not wish to discourage pointing newbies to most modern tools. BUT please point them to the fundamentals. I could not agree more. It sounds like I am following the same road that you, starting more or less at the same time: 2 years ago, or maybe 3, I fully switched to Debian, using windows only for few games (previously, I had debian installed while a year, but was never using it, lacks of games...), from time to time (but learning and programming are now my favorite games, so I spend more time on Debian). Now, despite the fact I'm still a newbie, I am trying to go on gentoo's road, and never learn about dselect. Just by taking a quick look, I can say that it have interesting options aptitude lacks. It is still a graphical software (ok, a semi-graphical one, like aptitude) which is important for me, because apt-get does not allow you to learn as easily why your packages are installed and their description in the same time, but in 2 seconds, I noticed it gave some options aptitude never gave me: choosing to install from cdrom, cdrom-set, nfs, sounds very powerful! I think I'll try it deeper now. But I do not think there are many kinds of newbies. A newbie is someone which is trying to learn, and, in my opinion, it is not an insult at all (some people on MMO games think it is). It is a compliment (not sure about word) since I think people who want to learn are very valuable guys. Regularly more than some self-proclaimed experts (well... lamers). But maybe I am keeping too much memories from the time where I was learning to crack softwares: in that time, every tutorial was starting with some terminology: lamer, newbie, cracker, hacker, black/white hat were explained before the first technical lessons. That knowledge of terminology should be, in my opinion, teach in regular classes too. It would avoid or restrain medias to say that music counterfeiters (damn, that word is ugly) are hackers. There are simply newbies and users. Users do not mind to learn or not, they want to use, and only use. They will use anti-viruses to remove their responsibilities of stupid acts, they will ask to professional to maintain their car, they'll ask to insurances to change their window's glasses, etc. When newbies will do the task themselves, and learn from their failures. Of course, we are all users in a domain or another, because being a newbie costs time, and money. But when you become a tinkerer, you'll just take that time and money back :) About aptitude... the ncurse version is correct. Slow, but correct (when you have a break somewhere, every move take ages! I guess it checks broken dependencies every time you move.). Or at least, was, before multi-arch. Since multi-arch, everything is 2 times slower: upgrades (double data to download), browsing (double lines to browse), fixing broken dependencies... and debtags uses still lacks features (currently, AFAIK, we can only browse tags by the tree, not specify we refuse some tags. Imagine I refuse to install all KDE stuff - which is true - I can not say to aptitude to avoid showing packages with KDE debtag). I do not speak about the GTK version. It simply have nothing related to ncurse version, event shortcuts differs (a real problem, since I think ncurse aptitude users like it for them). So, if dselect can be faster, I think I might use it now, instead of aptitude. Note: I did not read the info page of aptitude. I do not like info at all: this is a software which pretends to help you, but you have to learn how
Re: dselect fun
Chris Bannister wrote: On Wed, Jan 23, 2013 at 09:54:17AM +, Darac Marjal wrote: chime in with a reminder that dselect is considered discouraged these days. It's spiritual successor (a TUI interface to apt) is now aptitude. That depends on who you ask. For newbies, I certainly wouldn't recommend dselect, but if they wanted to use it I certainly wouldn't discourage them from doing so. In fact, if they can get their head around dselect, then anything else that is thrown at them will probably seem like a piece of cake. As to the overall Linux market there are at least two distinct classes of newbies. There is the class who is targeted by the Canonical (cf Microsoft) mentality - Big Brother knows best. There is class who wants the best from his system. BEST is not a simple one dimensional parameter. When I was in school a strong emphasis was placed on first principles. I think Debian could benefit from that outlook. I.E. Use the intuitive/user friendly/simple/simplistic interface(s) when appropriate. But know hat goes on under the hood. I'll follow the later route. I started my transition from Windows to Linux over two years ago. I could have had a system up in a day. But I don't see how it would have been significantly better/ than (insert your least favorite OS implementation here). I'll continue to pursue the back to basics route. I do not wish to discourage pointing newbies to most modern tools. BUT please point them to the fundamentals. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5101a113.9070...@cloud85.net
Re: dselect fun
On Tue, Jan 22, 2013 at 04:49:04PM -0800, Arne de Boer wrote: sudo bash apt-get install dpkg dselect dpkg --get-selections /root/dpkglistOK dselect mess around ;-) when finished: dpkg --set-selections /root/dpkglistOK I'm not entirely sure if this message was supposed to be in reply to something or if you missed out some narrative, but I just thought I'd chime in with a reminder that dselect is considered discouraged these days. It's spiritual successor (a TUI interface to apt) is now aptitude. signature.asc Description: Digital signature
Re: dselect fun
On Wed, Jan 23, 2013 at 09:54:17AM +, Darac Marjal wrote: chime in with a reminder that dselect is considered discouraged these days. It's spiritual successor (a TUI interface to apt) is now aptitude. That depends on who you ask. For newbies, I certainly wouldn't recommend dselect, but if they wanted to use it I certainly wouldn't discourage them from doing so. In fact, if they can get their head around dselect, then anything else that is thrown at them will probably seem like a piece of cake. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130124004332.GA21347@tal
dselect fun
sudo bash apt-get install dpkg dselect dpkg --get-selections /root/dpkglistOK dselect mess around ;-) when finished: dpkg --set-selections /root/dpkglistOK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1358902144.31907.yahoomailclas...@web162401.mail.bf1.yahoo.com
Re: Debian 5.0 - dselect fejler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 25, 2009 at 07:40:05AM +0100, Ole Kofoed Hansen wrote: Anders E. Andersen skrev: P.S. sorry for direkte mail. Firefox skoder max til mailinglister.. :-[ Tjoh, Firefox er i det hele taget ret ringe til mail. Jeg bruger selv Thunderbird. :-) Mener du Iceweasel, eller bruger du ikke Debian? - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmlEvUACgkQn7DbMsAkQLhiZQCfewyHhYu86Js8iLf57VOnyb7U J1wAmgOTKb00CuU64KxHE443uFT6xsdN =rUq/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian 5.0 - dselect fejler
Torben Schou Jensen skrev: Har opgraderet til Debian 5.0 idag, alt er gået fint. Men ser nu at dselect (eller måske dpkg) fejler med Cannot allocate memory ved check for updates. Wow! Rimeligt old-school der! Aptitude rykker hårdt. Prøv det. :) Anders http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516742 Tja, vanen tro, har kørt server med Debian Stable i mange år og har altid været gode venner med dselect. Er endnu ikke blevet lige så god ven med aptitude, men det kommer sikkert en dag. Fik løst mig problem ved at indlægge en ny swap fil på 256MB, nu 512MB swap. /Torben -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian 5.0 - dselect fejler
Torben Schou Jensen skrev: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516742 Tja, vanen tro, har kørt server med Debian Stable i mange år og har altid været gode venner med dselect. Er endnu ikke blevet lige så god ven med aptitude, men det kommer sikkert en dag. Fik løst mig problem ved at indlægge en ny swap fil på 256MB, nu 512MB swap. Kender godt følelsen. Det tog også lang tid før jeg indså at Amiga ikke kom tilbage. Anders P.S. sorry for direkte mail. Firefox skoder max til mailinglister.. :-[ -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian 5.0 - dselect fejler
Anders E. Andersen skrev: P.S. sorry for direkte mail. Firefox skoder max til mailinglister.. :-[ Tjoh, Firefox er i det hele taget ret ringe til mail. Jeg bruger selv Thunderbird. :-) Med venlig hilsen Ole -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Debian 5.0 - dselect fejler
Har opgraderet til Debian 5.0 idag, alt er gået fint. Men ser nu at dselect (eller måske dpkg) fejler med Cannot allocate memory ved check for updates. Laver en af de normale, dselect 1 til 3 1. [U]pdate 2. [S]elect 3. [I]nstall men når jeg vælger 3 stopper dselect med dselect: unrecoverable fatal error, aborting: fork failed: Cannot allocate memory Kan starte dselect igen og kun vælge 3 og så virker det fint. Der er ingen udestående opdateringer at installere. debian:/etc/monit# free total used free sharedbuffers cached Mem:255188 132488 122700 0 2012 57444 -/+ buffers/cache: 73032 182156 Swap: 265032 254128 10904 dpkg 1.14.25 dselect 1.14.25 Overvejer at submitte en bug, men er det en fejl i dselect eller dpkg, eller noget 3'de. Mvh Torben -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debian 5.0 - dselect fejler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Feb 23, 2009 at 12:06:39AM +0100, Torben Schou Jensen wrote: Har opgraderet til Debian 5.0 idag, alt er gået fint. Men ser nu at dselect (eller måske dpkg) fejler med Cannot allocate memory ved check for updates. Overvejer at submitte en bug, men er det en fejl i dselect eller dpkg, eller noget 3'de. Sandsynligvis ligger fejlen i dselect - fordi ingen bruger det program længere, udover dig. Det anbefalede program at bruge, som også ligner lidt dselect (bare 100 gange bedre, men også mere ressourcekrævende), er aptitude. Du kan bruge aptitude lissom apt-get, fra en kommandolinje, men du kan også køre programmet uden argumenter så det starter i fuldskærmsmodus lissom dselect. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmh7GIACgkQn7DbMsAkQLiF0QCdFxWjpSZJ+dcqTXQIaXsl5p/6 DiMAoKN9o7afXGwLTIGCwk8NLJuoTDzs =038C -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dselect.
Obrigado pela dica mais uma vez Renato. -- Leandro Hamid SERPRO - Serviço Federal de Processamento de Dados Maito: [EMAIL PROTECTED] Maito: [EMAIL PROTECTED] Skype: leandro_hamid http://www.serpro.gov.br Weblog: http://sysaprendiz.wordpress.com/ 2008/12/2 Renato S. Yamane [EMAIL PROTECTED] Sávio Ramos escreveu: Felipe Augusto van de Wiel (faw) escreveu: Você também pode usar o synpatic em modo gráfico ou o novíssimo aptitude-gtk. :-) Aonde está a trapizonga? You have searched for packages that names contain aptitude-gtk in all suites, all sections, and all architectures. Sorry, your search gave no results. O código do aptitude-gtk foi integrado ao próprio aptitude e está no repositório experimental (release 0.5). *Provavelmente* ele poderá ser executado com um aptitude --gui (ou coisa parecida). Att, Renato -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect.
Em Mon, 01 Dec 2008 14:02:30 +0100 Felipe Augusto van de Wiel (faw) [EMAIL PROTECTED] escreveu: Você também pode usar o synpatic em modo gráfico ou o novíssimo aptitude-gtk. :-) Aonde está a trapizonga? You have searched for packages that names contain aptitude-gtk in all suites, all sections, and all architectures. Sorry, your search gave no results. Informação de bastidor... -- Sávio M Ramos Arquiteto, Rio, RJ Só uso Linux desde 2000 www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect.
Sávio Ramos escreveu: Felipe Augusto van de Wiel (faw) escreveu: Você também pode usar o synpatic em modo gráfico ou o novíssimo aptitude-gtk. :-) Aonde está a trapizonga? You have searched for packages that names contain aptitude-gtk in all suites, all sections, and all architectures. Sorry, your search gave no results. O código do aptitude-gtk foi integrado ao próprio aptitude e está no repositório experimental (release 0.5). *Provavelmente* ele poderá ser executado com um aptitude --gui (ou coisa parecida). Att, Renato -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect.
2008/11/27 Leandro Hamid escreveu: Eu estou estudando muito o Debian e ainda o conceito do gerenciador de pacotes dselect ainda é nebuloso pra mim, não entendi bem o funcionamento do mesmo, será que alguém me alar um pouco sobre este gerenciador de pacotes e dizer também quais são as vantagens com relação ao apt-get...Desde já agradeço. O dselect é um gerenciador de baixo nível. Usado pelos de alto nível. Também sugiro que você use o aptitude. O dselect pode ser útil nos raros casos em que o gerenciador de alto nível dá erro. -- Bruno Schneider http://www.dcc.ufla.br/~bruno/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01-12-2008 12:04, Bruno Schneider wrote: 2008/11/27 Leandro Hamid escreveu: Eu estou estudando muito o Debian e ainda o conceito do gerenciador de pacotes dselect ainda é nebuloso pra mim, não entendi bem o funcionamento do mesmo, será que alguém me alar um pouco sobre este gerenciador de pacotes e dizer também quais são as vantagens com relação ao apt-get...Desde já agradeço. O dselect é um gerenciador de baixo nível. Usado pelos de alto nível. Ahhh... nem sempre. O dselect foi uma das primeiras idéias de gerenciador de pacotes com interface de usuário (e não somente linha de comando), mas há implementações de alto nível que sequer tomam conhecimento da existência do dselect. Também sugiro que você use o aptitude. O dselect pode ser útil nos raros casos em que o gerenciador de alto nível dá erro. Você também pode usar o synpatic em modo gráfico ou o novíssimo aptitude-gtk. :-) Abraço, - -- Felipe Augusto van de Wiel (faw) Debian. Freedom to code. Code to freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkz4GYACgkQCjAO0JDlykYpXACgo2dPst96/H3NzoHT5OAc1C/B o2AAn3LqTmKJfZXgpEMyK8QL7hFLjLAe =CkcB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect.
Muito obrigado pelos esclarecimentos pessoal, já estou dando uma olhada no aptitude e logo darei uma olhada no aptitude-gtk.Forte abraço a todos. -- Leandro Hamid SERPRO - Serviço Federal de Processamento de Dados Maito: [EMAIL PROTECTED] Maito: [EMAIL PROTECTED] Skype: leandro_hamid http://www.serpro.gov.br Weblog: http://sysaprendiz.wordpress.com/ 2008/12/1 Felipe Augusto van de Wiel (faw) [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01-12-2008 12:04, Bruno Schneider wrote: 2008/11/27 Leandro Hamid escreveu: Eu estou estudando muito o Debian e ainda o conceito do gerenciador de pacotes dselect ainda é nebuloso pra mim, não entendi bem o funcionamento do mesmo, será que alguém me alar um pouco sobre este gerenciador de pacotes e dizer também quais são as vantagens com relação ao apt-get...Desde já agradeço. O dselect é um gerenciador de baixo nível. Usado pelos de alto nível. Ahhh... nem sempre. O dselect foi uma das primeiras idéias de gerenciador de pacotes com interface de usuário (e não somente linha de comando), mas há implementações de alto nível que sequer tomam conhecimento da existência do dselect. Também sugiro que você use o aptitude. O dselect pode ser útil nos raros casos em que o gerenciador de alto nível dá erro. Você também pode usar o synpatic em modo gráfico ou o novíssimo aptitude-gtk. :-) Abraço, - -- Felipe Augusto van de Wiel (faw) Debian. Freedom to code. Code to freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkz4GYACgkQCjAO0JDlykYpXACgo2dPst96/H3NzoHT5OAc1C/B o2AAn3LqTmKJfZXgpEMyK8QL7hFLjLAe =CkcB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dselect.
Boa tarde pessoal. Eu estou estudando muito o Debian e ainda o conceito do gerenciador de pacotes dselect ainda é nebuloso pra mim, não entendi bem o funcionamento do mesmo, será que alguém me alar um pouco sobre este gerenciador de pacotes e dizer também quais são as vantagens com relação ao apt-get...Desde já agradeço. -- Leandro Hamid SERPRO - Serviço Federal de Processamento de Dados Maito: [EMAIL PROTECTED] Maito: [EMAIL PROTECTED] Skype: leandro_hamid http://www.serpro.gov.br Weblog: http://sysaprendiz.wordpress.com/
Re: dselect.
O dselect é um gerenciador de pacotes antigo em formato texto, ja usei muito ele, hoje o gerenciador em modo texto acredito que o melhor seja o aptitude. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect
On Mon, Nov 17, 2008 at 12:40:54PM -0600, John Hasler wrote: Florian Kulzer writes: Let's ask fortune: $ fortune debian -m Andrew Morton (/usr/share/games/fortunes/debian) % I was attacked by dselect as a small child and have since avoided debian. -- Andrew Morton % I met with it as a mature adult and so was better able to deal with the trauma but it still left scars. I met Debian before aptitude could keep me away from it. Just wait until aptitude rapes you ;) On the other hand, it may have saved Debian from becoming Ubuntu (with a little help from the old installer). Old installler? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect
* lee [EMAIL PROTECTED] [2008 Nov 18 06:19 -0600]: On Mon, Nov 17, 2008 at 12:40:54PM -0600, John Hasler wrote: Florian Kulzer writes: Let's ask fortune: $ fortune debian -m Andrew Morton (/usr/share/games/fortunes/debian) % I was attacked by dselect as a small child and have since avoided debian. -- Andrew Morton % I met with it as a mature adult and so was better able to deal with the trauma but it still left scars. I met Debian before aptitude could keep me away from it. Just wait until aptitude rapes you ;) As clunky as deslect was/is, it was still light years better than what was on Slackware in 1999. On the other hand, it may have saved Debian from becoming Ubuntu (with a little help from the old installer). Old installler? The reason Debian handles upgrades so well. ;-) - Nate -- The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true. Ham radio, Linux, bikes, and more: http://n0nb.us/index.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Mon, Nov 17, 2008 at 07:51:30PM -0800, Daniel Burrows wrote: The expected workflow in aptitude is that you pick all the changes you want to make, then ask aptitude to show you all the changes that will be made (including ones that were required by your past changes). If you like it, you confirm that it's OK and aptitude applies the changes. Then how do you know what changes cause what? Are you going through the list and somehow trace back all the dependencies to figure that out? And when you make another change, you have to start all over again? BTW, how do you tell aptitude to tell you what it would do? I just started it and couldn't figure that out. I would like to see what it would do without me making any changes. The expected workflow in dselect is that as you pick each change that you want to make, dselect jumps to a screen where it tells you all the other changes it's about to make because they were required by what you just did. If you like them, you confirm that they're OK and dselect drops you back to the main package list. Once you've finished picking changes, you tell dselect to proceed with applying them all. Yeah, very easy and straightforward :) Can you configure aptitude to do that? Believe me, there are people who hate the dselect model just as passionately as you hate how aptitude does it; aptitude was deliberately designed to be different for just this reason. Luckily, we still have both options and you can use the one that works for you. :-) As far as I understood it, it was supposed to replace dselect because it has some advantages in how it's managing the packages. Since aptitude came out, I'm afraid that deselect might be removed some day. Maybe I even come to like to aptitude if I can figure it out. But aptitude does *not* remove software without asking -- it just asks in a different place. How do you know that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Tue, Nov 18, 2008 at 2:33 PM, lee [EMAIL PROTECTED] wrote: On Mon, Nov 17, 2008 at 07:51:30PM -0800, Daniel Burrows wrote: The expected workflow in aptitude is that you pick all the changes you want to make, then ask aptitude to show you all the changes that will be made (including ones that were required by your past changes). If you like it, you confirm that it's OK and aptitude applies the changes. Then how do you know what changes cause what? Are you going through the list and somehow trace back all the dependencies to figure that out? And when you make another change, you have to start all over again? BTW, how do you tell aptitude to tell you what it would do? I just started it and couldn't figure that out. I would like to see what it would do without me making any changes. The expected workflow in dselect is that as you pick each change that you want to make, dselect jumps to a screen where it tells you all the other changes it's about to make because they were required by what you just did. If you like them, you confirm that they're OK and dselect drops you back to the main package list. Once you've finished picking changes, you tell dselect to proceed with applying them all. Yeah, very easy and straightforward :) Can you configure aptitude to do that? Believe me, there are people who hate the dselect model just as passionately as you hate how aptitude does it; aptitude was deliberately designed to be different for just this reason. Luckily, we still have both options and you can use the one that works for you. :-) As far as I understood it, it was supposed to replace dselect because it has some advantages in how it's managing the packages. Since aptitude came out, I'm afraid that deselect might be removed some day. Maybe I even come to like to aptitude if I can figure it out. If you can't figure it out, that doesn't mean it sucks. But aptitude does *not* remove software without asking -- it just asks in a different place. How do you know that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Tue, Nov 18, 2008 at 02:39:10PM +0200, Aioanei Rares wrote: Maybe I even come to like to aptitude if I can figure it out. If you can't figure it out, that doesn't mean it sucks. That you can figure it out doesn't mean that it doesn't suck. Maybe I did figure it out but found that it wouldn't do what I wanted it to do. There's no way to know now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Tue, Nov 18, 2008 at 06:33:39 -0600, lee ([EMAIL PROTECTED]) wrote: On Mon, Nov 17, 2008 at 07:51:30PM -0800, Daniel Burrows wrote: But aptitude does *not* remove software without asking -- it just asks in a different place. How do you know that? Because he wrote it (aptitude, that is) ;-) -- Bob Cox. Stoke Gifford, near Bristol, UK. Debian on the NSLU2: http://bobcox.com/slug/ Registered user #445000 with the Linux Counter - http://counter.li.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Tue, Nov 18, 2008 at 06:33:39AM -0600, lee [EMAIL PROTECTED] was heard to say: On Mon, Nov 17, 2008 at 07:51:30PM -0800, Daniel Burrows wrote: The expected workflow in aptitude is that you pick all the changes you want to make, then ask aptitude to show you all the changes that will be made (including ones that were required by your past changes). If you like it, you confirm that it's OK and aptitude applies the changes. Then how do you know what changes cause what? Are you going through the list and somehow trace back all the dependencies to figure that out? And when you make another change, you have to start all over again? If you select a package in the preview screen, aptitude will show you packages that are related by dependencies. You can also type i a few times to see a package that you selected manually which requires each newly installed package (but this isn't perfect in some corner cases). BTW, how do you tell aptitude to tell you what it would do? I just started it and couldn't figure that out. I would like to see what it would do without me making any changes. Press g and you get a summary of all the changes you've made. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Tue, Nov 18, 2008 at 07:24:02AM -0600, lee wrote: On Tue, Nov 18, 2008 at 02:39:10PM +0200, Aioanei Rares wrote: Maybe I even come to like to aptitude if I can figure it out. If you can't figure it out, that doesn't mean it sucks. That you can figure it out doesn't mean that it doesn't suck. Maybe I did figure it out but found that it wouldn't do what I wanted it to do. There's no way to know now. Have you read the excellent aptitude manual (I think its in package aptitude-doc)? Also, be sure to use the curses interface (rather than the command-line apt-get replacement). Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Tue, Nov 18, 2008 at 10:22:08AM -0500, Douglas A. Tutty wrote: Have you read the excellent aptitude manual (I think its in package aptitude-doc)? Also, be sure to use the curses interface (rather than the command-line apt-get replacement). Not yet, but I'll take a look at it, thanks. -- http://en.wikipedia.org/wiki/Posting_style -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
using dselect (was: Re: debian installation help)
On Mon, Nov 17, 2008 at 07:00:31AM -0800, Daniel Burrows wrote: On Mon, Nov 17, 2008 at 03:28:20AM -0600, lee [EMAIL PROTECTED] was heard to say: It was yast on Suse after 6.2 that made me switch to Debian because yast kept doing things I didn't want it to do, and it finally managed to remove qmail which I had spend a lot of work on to install it and get it to work by myself, without even asking me. Aptitude seems to be the same. aptitude never removes anything without asking you. (or rather, if it does it's a bug) The point is that aptitude left unclear how I'm supposed to use it to install or remove the packages I want. It kept showing me lists of packages which I wasn't sure what they are supposed to mean (the lists, not the packages). Trying to select packages for installation eventually changed the lists in an apparently arbitrary manner and eventually seemed to install a large amount of packages I didn't want to install, for unknown reasons, i. e. not because of dependencies (I can't tell for sure, but that would have been way to many packages to be installed because of deps). It didn't let me see what is actually selected for installation. Trying to change a selection yielded arbitrary changes in the list. Aptitude seemed to want to totally mess up the installation because it didn't seem to know anything about what had been installed with dselect. In short, it was awful and unusable. Dselect is straightforward, it lets you select a package for install|hold|purge|remove, shows you dependencies right away if needed. Before doing anything, you will be shown what it is going to do. Why make it more difficult and confusing? Why shouldn't using dselect be recommended? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
On Mon, Nov 17, 2008 at 11:05:48 -0600, lee wrote: [...] Why shouldn't using dselect be recommended? Let's ask fortune: $ fortune debian -m Andrew Morton (/usr/share/games/fortunes/debian) % I was attacked by dselect as a small child and have since avoided debian. -- Andrew Morton % -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect
Florian Kulzer writes: Let's ask fortune: $ fortune debian -m Andrew Morton (/usr/share/games/fortunes/debian) % I was attacked by dselect as a small child and have since avoided debian. -- Andrew Morton % I met with it as a mature adult and so was better able to deal with the trauma but it still left scars. On the other hand, it may have saved Debian from becoming Ubuntu (with a little help from the old installer). -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using dselect (was: Re: debian installation help)
I think I understand. The expected workflow in aptitude is that you pick all the changes you want to make, then ask aptitude to show you all the changes that will be made (including ones that were required by your past changes). If you like it, you confirm that it's OK and aptitude applies the changes. The expected workflow in dselect is that as you pick each change that you want to make, dselect jumps to a screen where it tells you all the other changes it's about to make because they were required by what you just did. If you like them, you confirm that they're OK and dselect drops you back to the main package list. Once you've finished picking changes, you tell dselect to proceed with applying them all. Believe me, there are people who hate the dselect model just as passionately as you hate how aptitude does it; aptitude was deliberately designed to be different for just this reason. Luckily, we still have both options and you can use the one that works for you. :-) But aptitude does *not* remove software without asking -- it just asks in a different place. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt/dselect anomaly
On Sun, May 18, 2008 at 08:33:35PM -0400, Marty [EMAIL PROTECTED] was heard to say: I usually keep current with the Debian archive using apt-get. Sometimes, however, I install programs using dselect. After upgrading to the latest Debian archive using apt-get update/upgrade, I got the following message while running dselect: The following packages will be upgraded: openssh-client openssh-server It happened on two different similarly configured machines. I'm pretty sure this has never happened to me before. I have always thought that upgrading using either apt-get or dselect (using the apt method) were equivalent, at least with respect to staying current with the archive. Am I missing something major? Thanks for any illumination. The latest version of openssh-server depends on openssh-blacklist due to the security problems with openssl that came up recently. If you only use apt-get upgrade, openssh-server won't get upgraded because upgrade refuses to install new packages. Did openssh-blacklist get installed too when you used dselect? Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt/dselect anomaly
Daniel Burrows wrote: On Sun, May 18, 2008 at 08:33:35PM -0400, Marty [EMAIL PROTECTED] was heard to say: I usually keep current with the Debian archive using apt-get. Sometimes, however, I install programs using dselect. After upgrading to the latest Debian archive using apt-get update/upgrade, I got the following message while running dselect: The following packages will be upgraded: openssh-client openssh-server It happened on two different similarly configured machines. I'm pretty sure this has never happened to me before. I have always thought that upgrading using either apt-get or dselect (using the apt method) were equivalent, at least with respect to staying current with the archive. Am I missing something major? Thanks for any illumination. The latest version of openssh-server depends on openssh-blacklist due to the security problems with openssl that came up recently. If you only use apt-get upgrade, openssh-server won't get upgraded because upgrade refuses to install new packages. Did openssh-blacklist get installed too when you used dselect? Yes. I had missed the warning about the kept back packages. Thanks. I have repeated the upgrade with another machine to confirm this explanation: apt-get update/upgrade outputs in part: The following packages have been kept back: openssh-client openssh-server The following packages will be upgraded: libssl0.9.8 linux-source-2.6.18 openssl rdesktop ssh dselect outputs in part: The following NEW packages will be installed: openssh-blacklist The following packages will be upgraded: openssh-client openssh-server 2 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apt/dselect anomaly
I usually keep current with the Debian archive using apt-get. Sometimes, however, I install programs using dselect. After upgrading to the latest Debian archive using apt-get update/upgrade, I got the following message while running dselect: The following packages will be upgraded: openssh-client openssh-server It happened on two different similarly configured machines. I'm pretty sure this has never happened to me before. I have always thought that upgrading using either apt-get or dselect (using the apt method) were equivalent, at least with respect to staying current with the archive. Am I missing something major? Thanks for any illumination. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt/dselect anomaly
Marty [EMAIL PROTECTED]: I usually keep current with the Debian archive using apt-get. Sometimes, however, I install programs using dselect. After upgrading to the latest Debian archive using apt-get update/upgrade, I got the following message while running dselect: The following packages will be upgraded: openssh-client openssh-server It happened on two different similarly configured machines. I'm pretty sure this has never happened to me before. I have always thought that upgrading using either apt-get or dselect (using the apt method) were equivalent, at least with respect to staying current with the archive. Am I missing something major? Thanks for any illumination. http://svn.debian.org/viewsvn/pkg-openssl/openssl/trunk/rand/md_rand.c?rev=141r1=140r2=141 A major flaw has been discovered in the way Debian has been creating ssh and ssl keys. I'm surprised anyone's not heard of it yet. Upgrading those two packages places you in a position to fix the problem as it affects your systems. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
On Sun, Oct 07, 2007 at 01:19:33AM +0200, Tobias Nissen wrote: Hi Martin! Martin Waller wrote: Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Yes, it is safe. dselect and aptitude use different databases. dpkg seems to rely on dselect for some reason: [EMAIL PROTECTED]:~# dpkg --purge dselect dpkg: dependency problems prevent removal of dselect: dpkg depends on dselect. [..] -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
[EMAIL PROTECTED] (Chris Bannister) writes: dpkg seems to rely on dselect for some reason: It did a lonnng time ago, but it doesn't anymore. [EMAIL PROTECTED]:~# dpkg --purge dselect dpkg: dependency problems prevent removal of dselect: dpkg depends on dselect. When's the last time you updated this system?!? -Miles -- Would you like fries with that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
On Mon, Oct 08, 2007 at 08:51:05AM -0400, Chris Bannister [EMAIL PROTECTED] was heard to say: On Sun, Oct 07, 2007 at 01:19:33AM +0200, Tobias Nissen wrote: Hi Martin! Martin Waller wrote: Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Yes, it is safe. dselect and aptitude use different databases. dpkg seems to rely on dselect for some reason: [EMAIL PROTECTED]:~# dpkg --purge dselect dpkg: dependency problems prevent removal of dselect: dpkg depends on dselect. [..] dpkg depends on dselect because dselect used to be part of the dpkg package. When dselect was split out, the dpkg maintainers wanted to ensure that no-one lost dselect during an upgrade, so dpkg depended (in fact, pre-depended IIRC) on dselect for some time. There's no technical reason to have dselect around. That said, the dependency went away sometime between sarge and etch, although a quick scan of the changelog doesn't tell me when. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
On Sun, Oct 07, 2007 at 11:41:02AM +0100, Martin Waller wrote: Thanks for the input - I asked because I thought I'd seen warnings about using aptitude after using dselect since installation. I am using aptitude now without apparent issue, although my system isn't a very complex setup and I'm on stable. Don't top post. The first things to do: Run aptitude interactively (no command args) Select options, tell it not to include recommends. Then, go down the list of all packages and if its one that you yourself don't specifically want installed, then mark it as automatic. Continue going down the list. When you think you have it all good: hit 'g' to see what aptitude would like to do. If its wrong, fix it (marking things manuall, install, whatever), then it 'q' to go back to the main screen. Then hit 'g' to see if its correct. When everything in the first 'g' screen is correct, hit 'g' again and it will clean out any cruft build-up you have. Then you can continue to use aptitude as your package manager and it will keep the system tidy. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
Daniel Burrows [EMAIL PROTECTED] writes: On Mon, Oct 08, 2007 at 08:51:05AM -0400, Chris Bannister [EMAIL PROTECTED] was heard to say: On Sun, Oct 07, 2007 at 01:19:33AM +0200, Tobias Nissen wrote: Hi Martin! Martin Waller wrote: Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Yes, it is safe. dselect and aptitude use different databases. dpkg seems to rely on dselect for some reason: [EMAIL PROTECTED]:~# dpkg --purge dselect dpkg: dependency problems prevent removal of dselect: dpkg depends on dselect. [..] dpkg depends on dselect because dselect used to be part of the dpkg package. When dselect was split out, the dpkg maintainers wanted to ensure that no-one lost dselect during an upgrade, so dpkg depended (in fact, pre-depended IIRC) on dselect for some time. There's no technical reason to have dselect around. That said, the dependency went away sometime between sarge and etch, although a quick scan of the changelog doesn't tell me when. I just looked and dselect still shows 'Priority: required' in etch even though nothing is listed as depending on it. Maybe that should be changed. -- Carl Johnson[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
Douglas A. Tutty wrote: On Sun, Oct 07, 2007 at 11:41:02AM +0100, Martin Waller wrote: Thanks for the input - I asked because I thought I'd seen warnings about using aptitude after using dselect since installation. I am using aptitude now without apparent issue, although my system isn't a very complex setup and I'm on stable. Don't top post. :( sorry The first things to do: Run aptitude interactively (no command args) Select options, tell it not to include recommends. Then, go down the list of all packages and if its one that you yourself don't specifically want installed, then mark it as automatic. Continue going down the list. When you think you have it all good: hit 'g' to see what aptitude would like to do. If its wrong, fix it (marking things manuall, install, whatever), then it 'q' to go back to the main screen. Then hit 'g' to see if its correct. When everything in the first 'g' screen is correct, hit 'g' again and it will clean out any cruft build-up you have. Then you can continue to use aptitude as your package manager and it will keep the system tidy. Doug. OK - thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
Thanks for the input - I asked because I thought I'd seen warnings about using aptitude after using dselect since installation. I am using aptitude now without apparent issue, although my system isn't a very complex setup and I'm on stable. Martin Miles Bader wrote: Mumia W.. [EMAIL PROTECTED] writes: That's true, but that wasn't what he asked. Martin wanted to know if it is safe to use aptitude after having used dselect up to now, and the answer is no--unless certain steps are taken in aptitude. Christ Mumia, would you stop spreading this clueless FUD? It should be perfectly safe, in general, to use aptitude having used dselect up to now. -Miles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
(etch) Using aptitude after using dselect - any issues?
Hello, Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Thnaks, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
On 10/6/07, Martin Waller [EMAIL PROTECTED] wrote: Hello, Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Thnaks, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Sure, aptitude is a better tool than dselect. -- Márcio H. Parreiras @ Pedro Leopoldo - MG - Brazil Por favor evite enviar-me anexos Excel (.xls), PowerPoint (.ppt) ou Word (.doc); Veja http://www.gnu.org/philosophy/no-word-attachments.pt.html Please avoid sending me Excel (.xls), PowerPoint (.ppt) or Word (.doc) attachments; See http://www.gnu.org/philosophy/no-word-attachments.html Experimente http://www.broffice.org Try http://www.openoffice.org A caixa dizia: Requer MS Windows ou superior, então eu instalei Debian/GNU Linux! http://www.debian.org/index.pt.html The box said: Requires MS Windows or better, then I installed Debian/GNU Linux! http://www.debian.org/index.en.html http://pt.wikipedia.org/wiki/Linux http://en.wikipedia.org/wiki/Linux Codificação de caracteres / Character coding: Unicode (UTF-8) .
Re: (etch) Using aptitude after using dselect - any issues?
Hi Martin! Martin Waller wrote: Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Yes, it is safe. dselect and aptitude use different databases. For a comparison, see Joey Hess' article about aptitude vs. dselect[0]. HTH, Tobias [0] http://groups.google.com/group/linux.debian.user/msg/ef229f2835c06b4b pgp457UrWhXre.pgp Description: PGP signature
Re: (etch) Using aptitude after using dselect - any issues?
On 10/06/2007 11:24 AM, Márcio H. Parreiras wrote: On 10/6/07, Martin Waller [EMAIL PROTECTED] wrote: Hello, Is it safe to switch to using aptititude as my package manager after having used dselect up to now? Thnaks, Martin Sure, aptitude is a better tool than dselect. That's true, but that wasn't what he asked. Martin wanted to know if it is safe to use aptitude after having used dselect up to now, and the answer is no--unless certain steps are taken in aptitude. I think those steps are to find out what aptitude wants to uninstall automatically and to perform unmarkauto on those packages. Aptitude's interactive interface is very useful for this. Martin would want to get aptitude to the point where it does not want install or uninstall anything automatically. After aptitude is satisfied with the current system, it's probably safe to start using aptitude regularly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (etch) Using aptitude after using dselect - any issues?
Mumia W.. [EMAIL PROTECTED] writes: That's true, but that wasn't what he asked. Martin wanted to know if it is safe to use aptitude after having used dselect up to now, and the answer is no--unless certain steps are taken in aptitude. Christ Mumia, would you stop spreading this clueless FUD? It should be perfectly safe, in general, to use aptitude having used dselect up to now. -Miles -- What the fuck do white people have to be blue about!? Banana Republic ran out of Khakis? The Espresso Machine is jammed? Hootie and The Blowfish are breaking up??! Shit, white people oughtta understand, their job is to GIVE people the blues, not to get them!-- George Carlin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg + dselect
Em 05/06/07, Renato S. Yamane [EMAIL PROTECTED] escreveu: Alemao escreveu: Segui uma dica de um colega da lista para replicar os pacotes de uma máquina para outra: numa maquina: dpkg --get-selections pacotes.txt outra maquina:dpkg --set-selections pacotes.txt dselect install Até ai tudo bem, porém gostaria que um pacote desses selecionados fosse removido. Já tentei apagar a linha do pacote no pacotes.txt, mas toda vez que rodo o dselect install ele continua querendo instalar aquele bendito pacote :( Provavelmente porque ele é uma dependência. Como foi dito algum pacote deve depender dele por isso vc não consegue remover ele. Verifique se não é isso At+ Oéslei.
dpkg + dselect
Olá lista, =) Segui uma dica de um colega da lista para replicar os pacotes de uma máquina para outra: numa maquina: dpkg --get-selections pacotes.txt outra maquina:dpkg --set-selections pacotes.txt dselect install Até ai tudo bem, porém gostaria que um pacote desses selecionados fosse removido. Já tentei apagar a linha do pacote no pacotes.txt, mas toda vez que rodo o dselect install ele continua querendo instalar aquele bendito pacote :( Já tentei o dpkg --clear-selections, mas também nao atualizou porque continua querendo installar o pacote. Alguém sabe como remover explicitamente com o dkpg certo pacote da lista de seleção? Valeu! --- - Alemão -- ---
Re: dpkg + dselect
Alemao escreveu: Segui uma dica de um colega da lista para replicar os pacotes de uma máquina para outra: numa maquina: dpkg --get-selections pacotes.txt outra maquina:dpkg --set-selections pacotes.txt dselect install Até ai tudo bem, porém gostaria que um pacote desses selecionados fosse removido. Já tentei apagar a linha do pacote no pacotes.txt, mas toda vez que rodo o dselect install ele continua querendo instalar aquele bendito pacote :( Provavelmente porque ele é uma dependência. Att, Renato -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with phpbb and mysql vi dselect
Bill Warren wrote: -Original Message- From: Angelo Bertolli [mailto:[EMAIL PROTECTED] Sent: Mon 12/18/2006 10:20 PM To: Bill Warren Cc: debian-user@lists.debian.org Subject: Re: Problems with phpbb and mysql vi dselect Bill Warren wrote: Hello, I have dselected phpbb2 and mysql. The database is done and works. When I go to http://mywebsite.com/phpbb the web page I get: The database module for the database you are using, MySQL, is not available. Please (re)install the php4-mysql package or if it's already installed, add extension=mysql.so to the relevant /etc/php//php.ini and restart the webserver if appropriate. I went to /etc/php4/apache/php.ini and removed the uncommented the section where it talks about Dynamic Extensions and extension=mysql.so. Then I restarted apache. Apache restarts with the following error: Starting web server: apache-perlPHP Warning: Unknown(): Invalid library (maybe not a PHP library) 'mysql.so' in Unknown on line 0 In /etc/php4/apache/php.ini it has a place for the directory and it is correct. So, I don't know why it does not like it. Any ideas? Well it said to make sure you had php4-mysql installed... do you have it installed? dpkg -l | fgrep mysql -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Yep, when I run that command I get: marge:/# dpkg -l | fgrep mysql ii libdbd-mysql-p 2.9006-1 A Perl5 database interface to the MySQL data ii libmysqlclient 4.0.24-10sarge mysql database client library ii mysql-client 4.0.24-10sarge mysql database client binaries ii mysql-common 4.0.24-10sarge mysql database common files (e.g. /etc/mysql rc mysql-common-4 4.1.11a-4sarge mysql database common files (e.g. /etc/mysql ii mysql-server 4.0.24-10sarge mysql database server binaries rc mysql-server-4 4.1.11a-4sarge mysql database server binaries ii php4-mysql 4.3.10-18 MySQL module for php4 Anybody else have an idea what to check next? Thanks, Bill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with phpbb and mysql vi dselect
Angelo Bertolli wrote: Bill Warren wrote: -Original Message- From: Angelo Bertolli [mailto:[EMAIL PROTECTED] Sent: Mon 12/18/2006 10:20 PM To: Bill Warren Cc: debian-user@lists.debian.org Subject: Re: Problems with phpbb and mysql vi dselect Bill Warren wrote: Hello, I have dselected phpbb2 and mysql. The database is done and works. When I go to http://mywebsite.com/phpbb the web page I get: The database module for the database you are using, MySQL, is not available. Please (re)install the php4-mysql package or if it's already installed, add extension=mysql.so to the relevant /etc/php4//php.ini and restart the webserver if appropriate. I went to /etc/php4/apache/php.ini and removed the uncommented the section where it talks about Dynamic Extensions and extension=mysql.so. Then I restarted apache. Apache restarts with the following error: Starting web server: apache-perlPHP Warning: Unknown(): Invalid library (maybe not a PHP library) 'mysql.so' in Unknown on line 0 In /etc/php4/apache/php.ini it has a place for the directory and it is correct. So, I don't know why it does not like it. Any ideas? Well it said to make sure you had php4-mysql installed... do you have it installed? dpkg -l | fgrep mysql -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Yep, when I run that command I get: marge:/# dpkg -l | fgrep mysql ii libdbd-mysql-p 2.9006-1 A Perl5 database interface to the MySQL data ii libmysqlclient 4.0.24-10sarge mysql database client library ii mysql-client 4.0.24-10sarge mysql database client binaries ii mysql-common 4.0.24-10sarge mysql database common files (e.g. /etc/mysql rc mysql-common-4 4.1.11a-4sarge mysql database common files (e.g. /etc/mysql ii mysql-server 4.0.24-10sarge mysql database server binaries rc mysql-server-4 4.1.11a-4sarge mysql database server binaries ii php4-mysql 4.3.10-18 MySQL module for php4 Hrmmm, sorry I'm out of ideas then... I don't have any experience with apache-perl and haven't used apache 1 for quite a while now. I wonder why it says line 0. That seems to be a clue as to what it's doing. Angelo Line 0 of /etc/php4/apache/php.ini is engine = On If I comment out the line that it says I need, it starts with no problem. Bill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems with phpbb and mysql vi dselect
Hello, I have dselected phpbb2 and mysql. The database is done and works. When I go to http://mywebsite.com/phpbb the web page I get: The database module for the database you are using, MySQL, is not available. Please (re)install the php4-mysql package or if it's already installed, add extension=mysql.so to the relevant /etc/php//php.ini and restart the webserver if appropriate. I went to /etc/php4/apache/php.ini and removed the uncommented the section where it talks about Dynamic Extensions and extension=mysql.so. Then I restarted apache. Apache restarts with the following error: Starting web server: apache-perlPHP Warning: Unknown(): Invalid library (maybe not a PHP library) 'mysql.so' in Unknown on line 0 In /etc/php4/apache/php.ini it has a place for the directory and it is correct. So, I don't know why it does not like it. Any ideas? Thanks, Bill
Re: Problems with phpbb and mysql vi dselect
Bill Warren wrote: Hello, I have dselected phpbb2 and mysql. The database is done and works. When I go to http://mywebsite.com/phpbb the web page I get: The database module for the database you are using, MySQL, is not available. Please (re)install the php4-mysql package or if it's already installed, add extension=mysql.so to the relevant /etc/php//php.ini and restart the webserver if appropriate. I went to /etc/php4/apache/php.ini and removed the uncommented the section where it talks about Dynamic Extensions and extension=mysql.so. Then I restarted apache. Apache restarts with the following error: Starting web server: apache-perlPHP Warning: Unknown(): Invalid library (maybe not a PHP library) 'mysql.so' in Unknown on line 0 In /etc/php4/apache/php.ini it has a place for the directory and it is correct. So, I don't know why it does not like it. Any ideas? Well it said to make sure you had php4-mysql installed... do you have it installed? dpkg -l | fgrep mysql -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Problems with phpbb and mysql vi dselect
-Original Message- From: Angelo Bertolli [mailto:[EMAIL PROTECTED] Sent: Mon 12/18/2006 10:20 PM To: Bill Warren Cc: debian-user@lists.debian.org Subject: Re: Problems with phpbb and mysql vi dselect Bill Warren wrote: Hello, I have dselected phpbb2 and mysql. The database is done and works. When I go to http://mywebsite.com/phpbb the web page I get: The database module for the database you are using, MySQL, is not available. Please (re)install the php4-mysql package or if it's already installed, add extension=mysql.so to the relevant /etc/php//php.ini and restart the webserver if appropriate. I went to /etc/php4/apache/php.ini and removed the uncommented the section where it talks about Dynamic Extensions and extension=mysql.so. Then I restarted apache. Apache restarts with the following error: Starting web server: apache-perlPHP Warning: Unknown(): Invalid library (maybe not a PHP library) 'mysql.so' in Unknown on line 0 In /etc/php4/apache/php.ini it has a place for the directory and it is correct. So, I don't know why it does not like it. Any ideas? Well it said to make sure you had php4-mysql installed... do you have it installed? dpkg -l | fgrep mysql -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Yep, when I run that command I get: marge:/# dpkg -l | fgrep mysql ii libdbd-mysql-p 2.9006-1 A Perl5 database interface to the MySQL data ii libmysqlclient 4.0.24-10sarge mysql database client library ii mysql-client 4.0.24-10sarge mysql database client binaries ii mysql-common 4.0.24-10sarge mysql database common files (e.g. /etc/mysql rc mysql-common-4 4.1.11a-4sarge mysql database common files (e.g. /etc/mysql ii mysql-server 4.0.24-10sarge mysql database server binaries rc mysql-server-4 4.1.11a-4sarge mysql database server binaries ii php4-mysql 4.3.10-18 MySQL module for php4
Re: Re: dselect and resolving
Dont know what that is , but I do know I cant get on your site Scott t. Parr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing packages with apt-get, aptitude and dselect
On Tue, Dec 05, 2006 at 11:21:04PM -0800, Andrew Sackville-West wrote: well, you answered your own question, but here's what I do. mostly I ignore anyhting marked as done. Anything marked as pending (or other things, are there others?) I review carefully to IIRC, there was a post on debian-devel where anything marked as done does not necessarily mean it was resolved/fixed. Something to do with version tracking in apt-listbugs, although I've never been bitten by ignoring anything marked as done. -- Chris. == ... the official version cannot be abandoned because the implication of rejecting it is far too disturbing: that we are subject to a government conspiracy of `X-Files' proportions and insidiousness. Letter to the LA Times Magazine, September 18, 2005. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing packages with apt-get, aptitude and dselect
On Mon, Dec 11, 2006 at 09:49:20PM +1300, Chris Bannister wrote: On Tue, Dec 05, 2006 at 11:21:04PM -0800, Andrew Sackville-West wrote: well, you answered your own question, but here's what I do. mostly I ignore anyhting marked as done. Anything marked as pending (or other things, are there others?) I review carefully to IIRC, there was a post on debian-devel where anything marked as done does not necessarily mean it was resolved/fixed. Something to do with version tracking in apt-listbugs, although I've never been bitten by ignoring anything marked as done. yeah. I'm just for the first time seeing that with this apt bug. yesterday apt-listbugs showed it as done in version 0.6.46.4 but the candidate was still 0.6.46.3. of course now we've caught up and 0.6.46.4 is the candidate. So I've never been bitten by a done either, but one must actually read the thing and see what's going on. A signature.asc Description: Digital signature
Re: Problem installing packages with apt-get, aptitude and dselect
Andrew Sackville-West wrote: mostly I ignore anyhting marked as done. Anything marked as pending (or other things, are there others?) I review carefully to see if it applies on my system. Often, the bugs are for different architectures or are things that aren't critical to me and I can safely ignore them. In fact this apt bug is the first one (in about 6 months of using apt-listbugs) that gave me pause and caused me to hold the package. so to answer your question again: no, just be cause a bug is listed doesn't mean you shouldn't install it. youmust research it a bit. I am curious what others do. A This is a good enough explanation for me. It clears things up quite a bit. :-) Thanks. -- Sincerely Jose Alburquerque -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem installing packages with apt-get, aptitude and dselect
Hi list. I'm running into a little bit of a problem with package management on my system and I was hoping someone out there might help: My problem occurs with apt-get, aptitude, dselect, synaptic or any other front-end to apt. I can manually download packages and successfully install/upgrade them using dpkg. In fact, I gave the 'smartpm' package manager a try and found it to work successfully because it uses dpkg directly and not apt. My problem is as follows: When I run 'aptitude upgrade' or 'apt-get upgrade' I get a segmentation fault when it tries to update the list of packages (I guess that's what the message says, but it is overwritten with Segmentation fault): [10:[EMAIL PROTECTED]:~]$ aptitude upgrade Segmentation faultsts... 0% [10:[EMAIL PROTECTED]:~]$ Segmentation faultsts... 0% [10:[EMAIL PROTECTED]:~]$ apt-get upgrade Segmentation faultsts... 0% [10:[EMAIL PROTECTED]:~]$ If I try to update with 'apt-get update' or 'aptitude update' (the output is the same for both), the update completes but, again, when they get to the update the lists part (I don't know exactly what the message is exactly because it's overwritten with Segmentation fault), there is a segfault: [10:[EMAIL PROTECTED]:~]$ aptitude update Get:1 http://http.us.debian.org testing Release.gpg [378B] Get:2 http://http.us.debian.org unstable Release.gpg [378B] Get:3 http://debian-multimedia.dfoell.org unstable Release.gpg [189B] Hit http://http.us.debian.org testing Release Get:4 http://security.debian.org testing/updates Release.gpg [189B] Hit http://debian-multimedia.dfoell.org unstable Release Hit http://http.us.debian.org unstable Release Hit http://security.debian.org testing/updates Release Get:5 http://snapshot.debian.net unstable Release.gpg [189B] Hit http://snapshot.debian.net unstable Release Hit http://http.us.debian.org testing/main Packages/DiffIndex Hit http://http.us.debian.org testing/non-free Packages/DiffIndex Hit http://http.us.debian.org testing/contrib Packages/DiffIndex Hit http://http.us.debian.org testing/main Sources/DiffIndex Hit http://http.us.debian.org testing/non-free Sources/DiffIndex Hit http://http.us.debian.org testing/contrib Sources/DiffIndex Ign http://debian-multimedia.dfoell.org unstable/main Packages/DiffIndex Hit http://http.us.debian.org unstable/main Packages/DiffIndex Ign http://debian-multimedia.dfoell.org unstable/main Sources/DiffIndex Hit http://http.us.debian.org unstable/non-free Packages/DiffIndex Hit http://http.us.debian.org unstable/contrib Packages/DiffIndex Hit http://http.us.debian.org unstable/main Sources/DiffIndex Hit http://http.us.debian.org unstable/non-free Sources/DiffIndex Hit http://http.us.debian.org unstable/contrib Sources/DiffIndex Ign http://security.debian.org testing/updates/main Packages/DiffIndex Hit http://debian-multimedia.dfoell.org unstable/main Packages Ign http://security.debian.org testing/updates/contrib Packages/DiffIndex Ign http://security.debian.org testing/updates/non-free Packages/DiffIndex Ign http://security.debian.org testing/updates/main Sources/DiffIndex Ign http://security.debian.org testing/updates/contrib Sources/DiffIndex Ign http://security.debian.org testing/updates/non-free Sources/DiffIndex Hit http://security.debian.org testing/updates/main Packages Hit http://security.debian.org testing/updates/contrib Packages Hit http://debian-multimedia.dfoell.org unstable/main Sources Hit http://security.debian.org testing/updates/non-free Packages Hit http://security.debian.org testing/updates/main Sources Hit http://security.debian.org testing/updates/contrib Sources Hit http://snapshot.debian.net unstable/main Packages/DiffIndex Hit http://security.debian.org testing/updates/non-free Sources Hit http://snapshot.debian.net unstable/contrib Packages/DiffIndex Hit http://snapshot.debian.net unstable/non-free Packages/DiffIndex Fetched 5B in 15s (0B/s) Segmentation faultsts... 0% [10:[EMAIL PROTECTED]:~]$ The only sort of clue that provides something meaningful, that I can't figure out is dselect. When I update in dselect, I get the same output as above (up to the Fetched line) with the following error: /usr/lib/dpkg/methods/apt/update: line 42: 8949 Segmentation fault $APTGET $OPTS $APT_OPT0 $APT_OPT1 update update available list script returned error exit status 1. Press enter to continue. I really don't understand the error message much and seem to not know what to do. I ran 'dpkg --audit' to make sure there are no half-installed packages that might be ruining my system and there are none (I get no output). Beyond that, I really don't think I've done anything to produce this on my system! Unfortunately, I can't install any new packages with apt-get or aptitude and cannot upgrade as I normally do with either of them. Anyone know what might be going on or how I might fix this? I'd really appreciate some help. Thanks so much in advanced. -- Sincerely Jose Alburquerque -- To UNSUBSCRIBE
Re: Problem installing packages with apt-get, aptitude and dselect
On Tue, Dec 05, 2006 at 10:55:43AM -0500, José Alburquerque wrote: Hi list. I'm running into a little bit of a problem with package management on my system and I was hoping someone out there might help: My problem occurs with apt-get, aptitude, dselect, synaptic or any other front-end to apt. I can manually download packages and successfully install/upgrade them using dpkg. In fact, I gave the 'smartpm' package manager a try and found it to work successfully because it uses dpkg directly and not apt. My problem is as follows: When I run 'aptitude upgrade' or 'apt-get upgrade' I get a segmentation fault when it tries to update the list of packages (I guess that's what the message says, but it is overwritten with Segmentation fault): [10:[EMAIL PROTECTED]:~]$ aptitude upgrade Segmentation faultsts... 0% [10:[EMAIL PROTECTED]:~]$ snipped various permutations of segfaults Unfortunately, I can't install any new packages with apt-get or aptitude and cannot upgrade as I normally do with either of them. Anyone know what might be going on or how I might fix this? I'd really appreciate some help. Thanks so much in advanced. what version of apt-get? check out bug 401263. Interestingly, though the bug says it applies to 0.6.46.2, I am running that with no problems. (k7 arch). but there are a variety of possible solutions posted. you may have to use dpkg to manually install an older(or newer) apt until it gets resolved. hth A signature.asc Description: Digital signature
Re: Problem installing packages with apt-get, aptitude and dselect
Andrew Sackville-West wrote: what version of apt-get? check out bug 401263. Interestingly, though the bug says it applies to 0.6.46.2, I am running that with no problems. (k7 arch). but there are a variety of possible solutions posted. you may have to use dpkg to manually install an older(or newer) apt until it gets resolved. hth A Thanks so much for your guidance! I'm running version 0.6.46.3 of apt, but thanks to your pointing out of the bug report I was able to fix the segfaulting by following the temporary solution given in the bug report. I'll most probably contribute to the bug report. Thanks again. -- Sincerely Jose Alburquerque -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing packages with apt-get, aptitude and dselect
On Tue, Dec 05, 2006 at 06:01:51PM -0500, José Alburquerque wrote: Andrew Sackville-West wrote: what version of apt-get? check out bug 401263. Interestingly, though the bug says it applies to 0.6.46.2, I am running that with no problems. (k7 arch). but there are a variety of possible solutions posted. you may have to use dpkg to manually install an older(or newer) apt until it gets resolved. hth A Thanks so much for your guidance! I'm running version 0.6.46.3 of apt, but thanks to your pointing out of the bug report I was able to fix the segfaulting by following the temporary solution given in the bug report. I'll most probably contribute to the bug report. check out the package apt-listbugs. It puls down critical (and maybe severe) bug reports and prompts you before installing packages. That's how I saw the segfault bug in apt and held my apt and apt-utils at the current version pending resolution. A signature.asc Description: Digital signature
Re: Problem installing packages with apt-get, aptitude and dselect
Andrew Sackville-West wrote: check out the package apt-listbugs. It puls down critical (and maybe severe) bug reports and prompts you before installing packages. That's how I saw the segfault bug in apt and held my apt and apt-utils at the current version pending resolution. A The funny thing is that I do have this package installed. Don't know why I didn't catch this bug. When installation pauses because of a pending bug, does that always mean that a package should not be installed? -- Sincerely Jose Alburquerque -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing packages with apt-get, aptitude and dselect
José Alburquerque wrote: When installation pauses because of a pending bug, does that always mean that a package should not be installed? Oops I didn't realize that the man page for apt-listbugs sort of explains it. Never mind the simplistic question. :-) -- Sincerely Jose Alburquerque -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing packages with apt-get, aptitude and dselect
On Tue, Dec 05, 2006 at 08:05:23PM -0500, José Alburquerque wrote: Andrew Sackville-West wrote: check out the package apt-listbugs. It puls down critical (and maybe severe) bug reports and prompts you before installing packages. That's how I saw the segfault bug in apt and held my apt and apt-utils at the current version pending resolution. A The funny thing is that I do have this package installed. Don't know why I didn't catch this bug. When installation pauses because of a pending bug, does that always mean that a package should not be installed? well, you answered your own question, but here's what I do. mostly I ignore anyhting marked as done. Anything marked as pending (or other things, are there others?) I review carefully to see if it applies on my system. Often, the bugs are for different architectures or are things that aren't critical to me and I can safely ignore them. In fact this apt bug is the first one (in about 6 months of using apt-listbugs) that gave me pause and caused me to hold the package. so to answer your question again: no, just be cause a bug is listed doesn't mean you shouldn't install it. youmust research it a bit. I am curious what others do. A signature.asc Description: Digital signature
Log for dselect / dpkg
I cannot seem to find an option to have dselect log any adds, changes, deletes to my system. The FAQ seems to say that there is a --log-options option for dpkg, but it doesn't work and the log /var/log/dpkg.log line described is ignored by dpkg, except to throw an error. How do folks track the actions of dselect since this log option doesn't work? Samhain lets me know about all of the files that are changed, but I would like to track the packages to help in roll-backs. bc William Chipman, Infrastructure Manager JSA Technologies 817-810-0485x2204 [EMAIL PROTECTED] www.jsatech.com attachment: winmail.dat
dselect i rekonfiguracja pakirtów
Witam! aptitude sciagnalem pakiet + pare zaleznych od niego pakietow. pozniej byla konfiguracja tychze pakietow ale musialem ja w pewnym momencie przerwac (czyli jakies tam pakiety zostaly nieskonfigurowane). gdy chcialem ponownie skonfigurowac pakiety poprzez dselect mam takie oto komunikaty: dselect running dpkg --pending --configure ... dpkg: baza danych stanu jest zablokowana przez inny proces dpkg --configure otrzymano kod powrotu 2. Wciśnij ENTER aby kontynuować. i mam teraz proste pytanie - co robic? -- Pozdrowienia, stentor mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect i rekonfiguracja pakirtów
06-07-30, stentor [EMAIL PROTECTED] napisał(a): Witam! aptitude sciagnalem pakiet + pare zaleznych od niego pakietow. pozniej byla konfiguracja tychze pakietow ale musialem ja w pewnym momencie przerwac (czyli jakies tam pakiety zostaly nieskonfigurowane). gdy chcialem ponownie skonfigurowac pakiety poprzez dselect mam takie oto komunikaty: dselect running dpkg --pending --configure ... dpkg: baza danych stanu jest zablokowana przez inny proces dpkg --configure otrzymano kod powrotu 2. Wciśnij ENTER aby kontynuować. i mam teraz proste pytanie - co robic? jesli dpkg --configure -a nie zadziala to dodaj np. --force-all , a jesli to nei zadziala to poprostu usn plik blokujący dpkg przez uruchomieniem (gdzies w /var/cache albo /var/lock - ale pewnien nie jestem bo debiana pod reka nie mam ). pzdr. -- Wojciech Ziniewicz| jid:[EMAIL PROTECTED] http://silenceproject.org | http://zetho.wordpress.com
Re: dselect i rekonfiguracj a pakirtów
On Sun, Jul 30, 2006 at 06:12:53PM +0200, Wojciech Ziniewicz wrote: 06-07-30, stentor [EMAIL PROTECTED] napisał(a): Witam! aptitude sciagnalem pakiet + pare zaleznych od niego pakietow. pozniej byla konfiguracja tychze pakietow ale musialem ja w pewnym momencie przerwac (czyli jakies tam pakiety zostaly nieskonfigurowane). gdy chcialem ponownie skonfigurowac pakiety poprzez dselect mam takie oto komunikaty: dselect running dpkg --pending --configure ... dpkg: baza danych stanu jest zablokowana przez inny proces dpkg --configure otrzymano kod powrotu 2. Wciśnij ENTER aby kontynuować. i mam teraz proste pytanie - co robic? jesli dpkg --configure -a nie zadziala to dodaj np. --force-all , a jesli to nei zadziala to poprostu usn plik blokujący dpkg przez uruchomieniem (gdzies w /var/cache albo /var/lock - ale pewnien nie jestem bo debiana pod reka nie mam ). Może lepiej znaleźć ten proces, który blokuje bazę i go zakończyć? Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dselect stopped after trying to update menu.lst
Hello, I tried to search the list's messages from the last couple of weeks to see if others might have experienced this problem. Didn't see anything, so I'm posting here. Point me to other similar posts if there were any. I was upgrading my system using dselect and after purging linux-image-2.6.14-2-686, it was probably doing something related to splash image (I didn't have splash image on the machine before this upgrade). It didn't find any splash image and said skipping It updated menu.lst and now is sitting there doing nothing :( There were two initramfs related bugs marked as critical #361270 and #358397. I wonder if one of those were a reason of this behaviour! I will leave it running till the morning so as to wait for responses/suggestions on how to proceed from here. Thanks, /ks Fetched 105MB in 6m20s (275kB/s) Reading package fields... Done Reading package status... Done Retrieving bug reports... Done grave bugs of python-cairo (- 2.4, 2.3) done #325379 - python-cairo: undefined symbol: cairo_ps_surface_create critical bugs of initramfs-tools (- 0.68b) open #361270 - update-initrams doesn't call lilo, when grub is around grave bugs of busybox ( - 1:1.1.3-2) open #163501 - busybox: cp -a doesn't copy symlinks grave bugs of initramfs-tools (- 0.68b) open #358397 - initramfs-tools: Fails to install grave bugs of python-gnome2 (- 2.12.4-3) open #354614 - foomatic-gui: segfaults when invoked Summary: python-cairo(1 bug), busybox(1 bug), initramfs-tools(2 bugs), python-gnome2(1 bug) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] Reading changelogs... Done Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 146544 files and directories currently installed.) Removing aptitude ... Purging configuration files for aptitude ... Removing libgnome-menu0 ... Purging configuration files for libgnome-menu0 ... Removing libreadline4 ... Purging configuration files for libreadline4 ... (Reading database ... 146521 files and directories currently installed.) Removing libtasn1-2-bin ... (Reading database ... 146507 files and directories currently installed.) Removing linux-image-2.6.14-2-686 ... Purging configuration files for linux-image-2.6.14-2-686 ... Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.16-1-686 Found kernel: /vmlinuz-2.6.15-1-686 Updating /boot/grub/menu.lst ... done -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect stopped after trying to update menu.lst
[KS] wrote: Hello, I tried to search the list's messages from the last couple of weeks to see if others might have experienced this problem. Didn't see anything, so I'm posting here. Point me to other similar posts if there were any. I was upgrading my system using dselect and after purging linux-image-2.6.14-2-686, it was probably doing something related to splash image (I didn't have splash image on the machine before this upgrade). It didn't find any splash image and said skipping It updated menu.lst and now is sitting there doing nothing :( There were two initramfs related bugs marked as critical #361270 and #358397. I wonder if one of those were a reason of this behaviour! I will leave it running till the morning so as to wait for responses/suggestions on how to proceed from here. Thanks, /ks Fetched 105MB in 6m20s (275kB/s) Reading package fields... Done Reading package status... Done Retrieving bug reports... Done grave bugs of python-cairo (- 2.4, 2.3) done #325379 - python-cairo: undefined symbol: cairo_ps_surface_create critical bugs of initramfs-tools (- 0.68b) open #361270 - update-initrams doesn't call lilo, when grub is around grave bugs of busybox ( - 1:1.1.3-2) open #163501 - busybox: cp -a doesn't copy symlinks grave bugs of initramfs-tools (- 0.68b) open #358397 - initramfs-tools: Fails to install grave bugs of python-gnome2 (- 2.12.4-3) open #354614 - foomatic-gui: segfaults when invoked Summary: python-cairo(1 bug), busybox(1 bug), initramfs-tools(2 bugs), python-gnome2(1 bug) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] Reading changelogs... Done Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 146544 files and directories currently installed.) Removing aptitude ... Purging configuration files for aptitude ... Removing libgnome-menu0 ... Purging configuration files for libgnome-menu0 ... Removing libreadline4 ... Purging configuration files for libreadline4 ... (Reading database ... 146521 files and directories currently installed.) Removing libtasn1-2-bin ... (Reading database ... 146507 files and directories currently installed.) Removing linux-image-2.6.14-2-686 ... Purging configuration files for linux-image-2.6.14-2-686 ... Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.16-1-686 Found kernel: /vmlinuz-2.6.15-1-686 Updating /boot/grub/menu.lst ... done It seems that linux-image-2.6.14-2-686 was causing some problems. dpkg: error processing linux-image-2.6.14-2-686 (--purge): subprocess post-removal script killed by signal (Interrupt) Errors were encountered while processing: linux-image-2.6.14-2-686 E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: les presque nouveaux paquetages dans dselect
Bonjour, Lorsqu'un paquetage disparaît des serveurs, il devient obsolète. Mon problème est quand il réapparaît (car beaucoup finissent par réapparaître). Si je ne l'ai pas désinstallé lorsqu'il est devenu obsolète (il me semblait trop important), aucun ennui. Si je l'ai désinstallé quand il est devenu obsolète, lors de son retour, il me semble qu'il n'apparaît pas dans les nouveaux mais se mélange plutôt à tous les paquetages non installés. Ce qui m'oblige à conserver sur papier une liste de ceux que j'ai désinstallés en attendant qu'ils soient dans une version compatible avec testing, et à les chercher régulièrement. Question bête : pourquoi les désinstalles-tu pour la seule raison qu'ils disparaissent des dépôts ? Je n'ai pas dit cela. Je les désinstalle pour une des trois raisons que tu donnes ci-dessous ou parce que, par erreur, je pense qu'ils ne sont plus utiles. En Testing, les paquets vont et viennent et en avoir des « obsolètes » est normal. Comme tu l'as remarqué, beaucoup reviennent rapidement. Oui. Les paquets obsolètes à enlever sont ceux qui : - ne servent plus ; - sont remplacés ; - occasionnent des conflits. Oui. Les paquets qui sont vraiment supprimés de la distribution sont annoncés (au moins dans les Nouvelles hebdomadaires Debian (Debian Weekly News)). Il n'y a pas vraiment de raison de les enlever sinon. J'avoue ne pas toujours prendre le temps de les lire complètement. :-/ Y a-t-il une configuration possible qui permette de les faire réapparaître dans les nouveaux ? J'ai un doute : est-ce que les paquets « purgés » ne sont pas reconnus comme nouveaux ? Non. Ce matin, par exemple, la paquetage eclipse ne m'est pas apparu comme nouveau sur une de mes machines qui en avait eu un installé (bien que retiré et purgé depuis bien longtemps). Je n'utilise plus dselect depuis quelques temps, je ne sais pas trop comment il fait la différence, ou plutôt où il la mémorise : aptitude mémorise tout dans /var/lib/aptitude, dselect semble ne se servir que de /var/lib/dpkg/status... Retirer l'entrée correspondante dans ce fichier est peut-être une solution. Mais elle ne me plaît pas trop, ce devrait être plus aisément configurable... Merci. [CITATION ALÉATOIRE : Un jour tout sera bien, voilà notre espérance ; tout est bien aujourd'hui, voilà l'illusion. Voltaire] -- Pierre Crescenzo mailto:[EMAIL PROTECTED] http://www.crescenzo.nom.fr/
Re: les presque nouveaux paquetages dans dselect
Mardi 30 mai 2006, 11:24:31 CEST, Pierre Crescenzo a écrit : Bonjour, 'soir, [...] Lorsqu'un paquetage disparaît des serveurs, il devient obsolète. Mon problème est quand il réapparaît (car beaucoup finissent par réapparaître). Si je ne l'ai pas désinstallé lorsqu'il est devenu obsolète (il me semblait trop important), aucun ennui. Si je l'ai désinstallé quand il est devenu obsolète, lors de son retour, il me semble qu'il n'apparaît pas dans les nouveaux mais se mélange plutôt à tous les paquetages non installés. Ce qui m'oblige à conserver sur papier une liste de ceux que j'ai désinstallés en attendant qu'ils soient dans une version compatible avec testing, et à les chercher régulièrement. Question bête : pourquoi les désinstalles-tu pour la seule raison qu'ils disparaissent des dépôts ? En Testing, les paquets vont et viennent et en avoir des « obsolètes » est normal. Comme tu l'as remarqué, beaucoup reviennent rapidement. Les paquets obsolètes à enlever sont ceux qui : - ne servent plus ; - sont remplacés ; - occasionnent des conflits. Les paquets qui sont vraiment supprimés de la distribution sont annoncés (au moins dans les Nouvelles hebdomadaires Debian (Debian Weekly News)). Il n'y a pas vraiment de raison de les enlever sinon. Y a-t-il une configuration possible qui permette de les faire réapparaître dans les nouveaux ? J'ai un doute : est-ce que les paquets « purgés » ne sont pas reconnus comme nouveaux ? Je n'utilise plus dselect depuis quelques temps, je ne sais pas trop comment il fait la différence, ou plutôt où il la mémorise : aptitude mémorise tout dans /var/lib/aptitude, dselect semble ne se servir que de /var/lib/dpkg/status... -- Sylvain Sauvage -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dselect
J'ai un problème d'authentification quand je télécharge des paquets Lecture des listes de paquets... Fait W: GPG error: ftp://ftp.debian.org unstable Release: Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 010908312D230C5F W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect
Bonjour, herve thibaud a écrit : J'ai un problème d'authentification quand je télécharge des paquets Lecture des listes de paquets... Fait W: GPG error: ftp://ftp.debian.org unstable Release: Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 010908312D230C5F W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. Ce genre de questio a déjà été abordée sur la liste, une recherche t'aurais certainement donner la réponse à ta question : # gpg --keyserver hkp://subkeys.pgp.net --recv-key 2D230C5F # gpg --export --armor 2D230C5F | sudo apt-key add - Cordialement, Yannick -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect: unable to open/create access method lockfile
Hi, I describe a partial solution and the next problem below. David Kirchner wrote: On 12/16/05, Brian C [EMAIL PROTECTED] wrote: dselect: unable to open/create access method lockfile but I still get the same error. Can anyone explain how to allow dselect to create the lockfile it wants to? I'm not sure where it would put the lockfile, but you may be able to find out using 'strace'. strace will show you the system calls the process is attempting, including what files it's trying to read. 'strace -o foo dselect' and then 'grep access foo' or 'grep open foo' may give you the answer. trying to apt-get something gave me a more useful error and I knew I needed the following files and directories: mkdir -p /var/lib/dpkg touch /var/lib/dpkg/status mkdir -p /var/lib/dpkg/updates This allows dselect to run. However, having lost my 'status' file is now a bigger problem because it created a new status file that believes I have NOTHING installed and so it wants to re-install every required Debian package. I'd rather not find out what happens if I let it do that. How can I create a status file that accurately reflects the packages already installed on my system? Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dselect: unable to open/create access method lockfile
Hi, You may recall that I destroyed my /var partition earlier this month trying to learn how to use dd to clone a hard drive. See: http://lists.debian.org/debian-user/2005/12/msg00612.html I have, surprisingly, managed to mostly recover from backups. However, I did not have a full /var backup and keep coming across sub-directories of /var that some program or other cannot find. A full hierarchy of /var from a clean minimal Sarge installation would be welcome. My most immediate problem is that dselect won't let me upgrade anything because when I tell it to update, it replies: dselect: unable to open/create access method lockfile I've tried creating several /var subdirectories that I think dselect might be looking for, including: /var/cache/apt/archives/ /var/cache/apt/archives/partial/ /var/lib/apt/lists /var/lib/apt/lists/partial/ but I still get the same error. Can anyone explain how to allow dselect to create the lockfile it wants to? Thanks, Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect: unable to open/create access method lockfile
On 12/16/05, Brian C [EMAIL PROTECTED] wrote: dselect: unable to open/create access method lockfile but I still get the same error. Can anyone explain how to allow dselect to create the lockfile it wants to? I'm not sure where it would put the lockfile, but you may be able to find out using 'strace'. strace will show you the system calls the process is attempting, including what files it's trying to read. 'strace -o foo dselect' and then 'grep access foo' or 'grep open foo' may give you the answer.
configurar dselect
Olah, Tentei usar o dselect para atualizar alguns pacotes do meu sistema (Kurumin 5.0). Tendo marcado esses pacotes para instalação (usando o apt como meio de acesso), ele entra numa tela de resolução de conflitos, até aqui tudo bem, mas tendo eu apertado enter (isto eh, aceitado as sugestoes de instalação do dselect), eu continuo na mesma tela de resolução de conflitos. Eh como se ele não marcasse automaticamente os pacotes sugeridos para instalação. Pesquisei bem a minha seleção de pacotes e vi que não resulta numa configuração impossível, na verdade percebi que o dselect usa como lista de todos os pacotes apenas pacotes da distribuição stable do debian (que está como a distribuição default no arquivo apt.conf --APT::Default-Release stable;), por isso como existem pacotes na minha seleção que dependem de pacotes que são da distribuição testing (como p.ex, libstdc++6 v. 4.0.2-2), o dselect não sai da tela de resolução de conflito, esperando para que eu desmarque o pacote para instalação. Usando o comando: apt-get -t testing install `pacote_que_quero` . Vou conseguindo instalar os pacotes que causam a dependencia dos demais, mas isso eh trabalhoso, serah que alguém tem uma forma de resolver isso usando apenas o dselect? (Obs, não quero mudar de distribuição, isto eh usar o apt-get dist-upgrade, que mudaria mais pacotes do que desejo). Obirgado, Marco Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dselect
Olah, Tentei usar o dselect para atualizar alguns pacotes do meu sistema (Kurumin 5.0). Tendo marcado esses pacotes para instalação (usando o apt como meio de acesso), ele entra numa tela de resolução de conflitos, até aqui tudo bem, mas tendo eu apertado enter (isto eh, aceitado as sugestoes de instalação do dselect), eu continuo na mesma tela de resolução de conflitos. Eh como se ele não marcasse automaticamente os pacotes sugeridos para instalação. Pesquisei bem a minha seleção de pacotes e vi que não resulta numa configuração impossível, na verdade percebi que o dselect usa como lista de todos os pacotes apenas pacotes da distribuição stable do debian (que está como a distribuição default no arquivo apt.conf), por isso como existem pacotes na minha seleção que dependem de pacotes que são da distribuição testing (como p.ex, libstdc++6 v. 4.0.2-2), o dselect não sai da tela de resolução de conflito, esperando para que eu desmarque o pacote para instalação. Usando o comando: apt-get -t testing install `pacote_que_quero` . Vou conseguindo instalar os pacotes que causam a dependencia dos demais, mas isso eh trabalhoso, serah que alguém tem uma forma de resolver isso usando apenas o dselect? (Obs, não quero mudar de distribuição, isto eh usar o apt-get dist-upgrade, que mudaria mais pacotes do que desejo). At. Marco Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Erro no dselect
Luiz Souza wrote: Estou tendo a seguinte situação de erro ao efetuar apt-get update. Estou atrás de um proxy e coloquei a linha export http_proxy=http://proxy:port/; no .bashrc de um usuário $, com o qual logo no sistema e em seguida logo como root. Autentico no proxy antes, mas ao tentar dar apt-get update recebo esse erro: Err http://http.us.debian.org stable/main Packages Falaha temporária resolvendo 'http.us.debian.org Isso foi erro do DNS. Digite 'host http.us.debian.org' e veja se o site realmente existe. No meu achou varios IPs... Se nao achar nada, verifique se o /etc/resolv.conf está ok. deve conter pelo menos uma linha com 'nameserver xxx.xxx.xxx.xxx' -- Marcos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Ign ... lors d'un dselect
Bonjour, Sous sarge, lorsque je lance la Mise à jour de dselect, j'ai des (c'est un exemple) : Ign http://ftp.debian.org testing-proposed-updates/main Packages Cependant, quelques lignes plus loin : Atteint http://ftp.debian.org testing-proposed-updates/main Packages Et j'ai l'impression que les mises à jour se font normalement... Suis-je simplement supposé ignoré les Ign ... ou comment corriger ? Dans tous les cas, quelle en est la cause ? Merci. A+ [CITATION ALÉATOIRE : Vous pourrez vous acquitter de cette taxe l'an prochain si vous êtes encore vivant. Perle de l'Administration] -- Pierre Crescenzo mailto:[EMAIL PROTECTED] http://www.crescenzo.nom.fr/
Erro no dselect
Estou tendo a seguinte situação de erro ao efetuar apt-get update. Estou atrás de um proxy e coloquei a linha export http_proxy=http://proxy:port/ no .bashrc de um usuário $, com o qual logo no sistema e em seguida logo como root. Autentico no proxy antes, mas ao tentar dar apt-get update recebo esse erro: Err http://http.us.debian.org stable/main Packages Falaha temporária resolvendo 'http.us.debian.org' Err http://http.us.debian.org stable/main Release Falaha temporária resolvendo 'http.us.debian.org' Err http://http.us.debian.org stable/contrib Packages Falaha temporária resolvendo 'http.us.debian.org' Err http://http.us.debian.org stable/contrib Release Falaha temporária resolvendo 'http.us.debian.org' Err http://http.us.debian.org stable/non-free Packages Falaha temporária resolvendo 'http.us.debian.org' Err http://http.us.debian.org stable/non-free Release Falaha temporária resolvendo 'http.us.debian.org' Falha ao baixar http://http.us.debian.org/debian/dists/stable/main/binary-i386/Packages.gz Falaha temporária resolvendo 'http.us.debian.org' Falha ao baixar http://http.us.debian.org/debian/dists/stable/main/binary-i386/Release Falaha temporária resolvendo 'http.us.debian.org' Falha ao baixar http://http.us.debian.org/debian/dists/stable/contrib/binary-i386/Packages.gz Falaha temporária resolvendo 'http.us.debian.org' Falha ao baixar http://http.us.debian.org/debian/dists/stable/contrib/binary-i386/Release Falaha temporária resolvendo 'http.us.debian.org' Falha ao baixar http://http.us.debian.org/debian/dists/stable/non-free/binary-i386/Packages.gz Falaha temporária resolvendo 'http.us.debian.org' Falha ao baixar http://http.us.debian.org/debian/dists/stable/non-free/binary-i386/Release Falaha temporária resolvendo 'http.us.debian.org' Lendo Lista de Pacotes... Pronto E: Alguns arquivos de índice falharam no download, eles foram ignorados ou os antigos foram usados em seu lugar. O que está errado?-- Luiz Carlos Barreto - na Net :-)lcbnet arroba gmail.com
différence apt-get / dselect
Bonjour, après avoir fait un apt-get update et un apt-get upgrade, je lance dselect, je choisis de voir la liste des paquets, j'appuie sur espace puis entrée (je ne modifie donc pas la liste en demandant d'installer ou du supprimer des paquets), et deselect m'indique néanmoins les changements suivants : « Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Les paquets suivants seront ENLEVÉS : php4-gd2 samba Les NOUVEAUX paquets suivants seront installés : gdk-imlib11 libbeecrypt6 libdmx1 libexif12 libfs6 libgnutls12 libmagick9 libneon24 libopenexr2c2 libparted1.6-13 libroken16-kerberos4kth libsepol1 libsigc++-2.0-0c2 libsqlite3-0 libssl0.9.8 libxau6 libxaw8 libxdmcp6 libxinerama1 libxkbfile1 libxkbui1 libxss1 libxxf86dga1 libxxf86misc1 libxxf86vm1 lsb-base php-db php-http php-mail php-net-smtp php-net-socket php-pear php-xml-parser php5-common readline-common tex-common x11-common xserver-xorg Les paquets suivants seront mis à jour : apache-common apache-ssl apache2-utils apt apt-utils aptitude console-common ftp-ssl hdparm imagemagick initscripts libapache-mod-perl libapache-mod-php4 libapache-mod-ssl libgnutls11 libgphoto2-2 libgtk2.0-0 libgtk2.0-bin libnet-ssleay-perl libreadline4 libreadline5 librpm4 libsane libx11-6 mutt netbase nmap openssl parted php4 php4-cgi php4-cli php4-common php4-pear rpm samba-common smbclient smbfs stunnel sysvinit tcpdump texinfo wget xbase-clients xfree86-common xlibmesa-gl xserver-common xserver-xfree86 xterm xutils 50 mis à jour, 38 nouvellement installés, 2 à enlever et 9 non mis à jour. Il est nécessaire de prendre 54,1Mo dans les archives. Après dépaquetage, 26,7Mo d'espace disque supplémentaires seront utilisés. » pourquoi cette différence si importante entre dselect et apt-get update/upgrade ? Cordialement, -- PII 233 -- Pensez � lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez � rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: différence apt-get / dselect
Le Dimanche, 13 Novembre 2005 10.50, PII 233 a écrit : Bonjour, bonjour pourquoi cette différence si importante entre dselect et apt-get update/upgrade ? il y a plusieurs raisons qui ont été discutées récemment sur cette liste (voir les archives et en particulier un mail d'un des responsable d'aptitude qui décrit le tout en détail, mais que je n'ai malheureusement plus sous la main). Ce qui en ressort, c'est qu'il faut maintenant utiliser aptitude, qui gère bien mieux les dépendances que dselect et apt-get. Cordialement, de même
Re: différence apt-get / dselect
Le Dimanche, 13 Novembre 2005 11.43, steve a écrit : Le Dimanche, 13 Novembre 2005 10.50, PII 233 a écrit : Bonjour, bonjour pourquoi cette différence si importante entre dselect et apt-get update/upgrade ? il y a plusieurs raisons qui ont été discutées récemment sur cette liste (voir les archives et en particulier un mail d'un des responsable d'aptitude qui décrit le tout en détail, mais que je n'ai malheureusement plus sous la main). Ce qui en ressort, c'est qu'il faut maintenant utiliser aptitude, qui gère bien mieux les dépendances que dselect et apt-get. voilà j'ai retrouvé le fil : http://lists.debian.org/debian-user/2004/04/msg03138.html bonne lecture Cordialement, de même
