Increasing number of conflicts
in [Debian]
|
Prev: X Window System on Samsung n210 (Intel GMA 3150)
Next: PDF is blocked for printing, etc. OK for acroread (it behaves as expected), but KPDF allows me to print it, even if it is protected! Why?
From: Joe on 19 Apr 2010 15:30 On 19/04/10 15:34, B. Alexander wrote: > On Mon, Apr 19, 2010 at 9:28 AM, Wolodja Wentland< > >> I assume that this will allow aptitude to take actions which are more to >> your liking as you obviously don't like the ones proposed by aptitude >> when you run safe-upgrade. >> > > safe-upgrade just does the upgrades that don't cause a ruckus. dist-upgrade > is the one that displays the conflicts and wants to remove packages. > > Thanks for testing a development branch of Debian :) >> > > No problem. Most of my Debian installs at home run sid, with the rest > running testing...Except my firewall, which runs stable for the first 6 > months or so (until critical packages start getting long in the tooth), then > I upgrade it to testing and run until the next stable release. > We all have different experiences, depending on what is loaded, and certainly sid has been fairly active in the last couple of months. I usually wait a week or so when a problem arises, during which time most of them disappear. When they don't it's usually because of a change of the structure of a package, and some old components must be removed to allow new components with different names to be installed. Occasionally, it is even necessary to remove a vital package, and reinstate it either immediately after the now-successful upgrade, or do a bit more research into how to retain it. Sometimes, an upgrade really does conflict with a long-established package, and you have to decide which to keep. I have a feeling that recently happened with two different Flash viewers. Do keep track of what you do, as I have just severely embarrassed myself by clearing such a logjam and then assuming that as nothing complained about dependencies, all was well. Some time later (weeks, I'm sure, and I had actually forgotten the conflict until seeing it on your list), a further upgrade to the package (mysql) stopped the daemon from starting, and I reported a bug, only to find a vital part of the system missing... You don't run sid unless you have a sense of humour. -- Joe -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BCCAED0.3090804(a)jretrading.com
From: Boyd Stephen Smith Jr. on 19 Apr 2010 16:00 On Monday 19 April 2010 08:16:02 B. Alexander wrote: > I've got an issue with a sid box that I have been maintaining for a while. > This is my workstation, and I have noticed a growing number of broken > packages, unmet dependencies and conflicts. I have been using safe-upgrade > for months now, hoping that it would work itself out over time. However, > this hasn't happened. So what can I do to fix the problems without losing > functionality? Below is the result of aptitude full-upgrade (forgive the > cut-and-paste): I would use (aptitude full-upgrade), then when/if the first suggestion doesn't meet with my approval, use the option to go into the ncurses interface at the [Y/n] prompt. (Answer '?' to get the full list of valid responses.) (NB: The keystrokes below are from memory, they may be incorrect, but should be in the aptitude documentation.) The ncurses interface will load and the current suggestion will be presented. Use the arrow keys to highlight the most onerous part of the suggestion then hit 'r' ([R]eject that action). Then, hit '.' to have aptitude comes up with a different list of suggestions. You can repeat this process until one of this following occurs: a) the suggestions provided by aptitude are acceptable, b) aptitude runs out of suggestions and re-presents the previous suggestions, or c) aptitude searches for suggestions for multiple minutes. If (a), I believe '!' will accept the current suggestsions. You will then hit 'g' and a preview of the changes will be presented. Hit 'g' one more time, and the changes will be made (which will include one or more dpkg runs). If (b), you can use ',' and '.' to navigate through all the suggestions presented and choose the least onerous one. Or, you can hit 'q' to [Q]uit aptitude, and try again rejecting fewer (or different) options. If (c), aptitude will usually churn until it's solver exhausts all available memory and it either dies, or is killed by the OMM-killer in the kernel. You can 'Ctrl+C' to kill aptitude earlier if you wish, and try again rejecting fewer (or different) options. Aptitude's interactive solver is one of the things that makes me use Debian (or a derivative) everywhere possible. IME, similar pieces of software on openSUSE are less interactive and less "intelligent". -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss(a)iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
From: Boyd Stephen Smith Jr. on 19 Apr 2010 17:50 You sent just to me. I'm sending back to the list and CC'ing you. On Monday 19 April 2010 16:27:08 B. Alexander wrote: > Thank you for this. I knew that aptitude had a an ncurses interface, but to > be honest, it looked too similar to dselect, which dredged up some bad > memories from about 10 years ago, when I was a Debian n00b... :) I can understand. I used dselect roughly once before my head exploded. Though, some do really like the dselect interface (or at least are used to it) and you can "theme" aptitude look very much like dselect. (The behavior remains much more sane.) > Just out of curiosity, I upgraded today (to 0.6.2-1), and now I get a > segfault when trying to do a full-upgrade or going into the ncurses > interface: > # aptitude full-upgrade [...] > python-kde4: Depends: python-qt4 (< 4.7-2+~) but 4.7.3-1 is to be > installed. > Depends: python-sip4 (>= <none>) but 4.10.2-1 is to be > installed. > Segmentation fault > > > # aptitude > Ouch! Got SIGSEGV, dying.. > Segmentation fault > > Has anyone else seen this? I wanted to verify before opening a bug. Check your kernel logs and see if anything bad is happening in the kernel or hardware. If not, it is probably a aptitude bug. You can try installing the version from Lenny or testing if the one from unstable is broken. I use the one from Lenny for handling mixed systems, so it should be able to handle most things. I do know that apt-get/aptitude is one of the first things you should upgrade when moving oldstable->stable as the resolver in the newer versions handles the multiple transitions easily. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss(a)iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
From: Mark Allums on 19 Apr 2010 18:10 On 4/19/2010 8:28 AM, Wolodja Wentland wrote: > On Mon, Apr 19, 2010 at 09:16 -0400, B. Alexander wrote: >> I've got an issue with a sid box that I have been maintaining for a while. This >> is my workstation, and I have noticed a growing number of broken packages, >> unmet dependencies and conflicts. I have been using safe-upgrade for months >> now, hoping that it would work itself out over time. However, this hasn't >> happened. So what can I do to fix the problems without losing functionality? >> Below is the result of aptitude full-upgrade (forgive the cut-and-paste): > > As a sid user you are certainly aware of the differences between > 'safe-upgrade' and 'full-upgrade' and I would be interested in the > actions proposed by aptitude if you run a full-update. > > I assume that this will allow aptitude to take actions which are more to > your liking as you obviously don't like the ones proposed by aptitude > when you run safe-upgrade. > > Thanks for testing a development branch of Debian :) > > Wolodja I noticed OP's post contained g++. My Sid is also trying to uninstall g++. Without me posting about 8k worth of useless diagnostics, would you happen to know the reason why? MAA -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BCCD3F9.8030102(a)allums.com
From: Andrei Popescu on 20 Apr 2010 15:20
On Mon,19.Apr.10, 20:28:16, Joe wrote: > You don't run sid unless you have a sense of humour. That's a good one :) You might want to attach a full name to it, for proper attribution ;) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic |