On Fri, 2011-09-23 at 10:15 -0500, John Foster wrote: > On Fri, Sep 23, 2011 at 7:12 AM, Ralf Mardorf > <ralf.mard...@alice-dsl.net> wrote: > Hi :) > > how can I find out which packages I need to lock against > upgrading, to > avoid that Synaptic will remove other packages I need? Isn't > there a way > to lock packages against removing? > > Usually there only will be some packages that will be > upgraded, hence > it's easy to find out which packages I need to lock against > upgrading, > but now there are to many packages, that will be upgraded. > > I already made a backup of the current Debian and locked > several > packages, anyway, I'm unable to upgrade, since I would lose > needed > development packages. > > Regards, > > Ralf > > Best way is to check the dependencies and the suggested items from > Synaptics drop down menus when you highlite the main apps that you are > locking. Then once you know what they are select them & lock the > dependcies & the suggested ones that are installed. > Best Wishes! > john
Thank you John :) unfortunately this doesn't help. The properties don't help, since it shows possible conflicts, with packages that aren't installed and than a list of thousands of dependencies. Really thousands, since I need to do it for many packages, that should be removed, but I need to keep those packages. The existing conflicts aren't shown. It's already hard to handle conflicts, when you know them, but it's impossible to handle conflicts, when you have to puzzle through thousands of packages. Isn't there really no way to see the conflicting packages or to lock packages, that should be removed, in a way that they are protected against removal? If there shouldn't be a way, I need to use another Linux. I know at least, that this is easy to handle when using Suse. FWIW I didn't compile a lot my self and everything or nearly everything was installed by packages and nothing of those packages can conflict with the packages that will be removed. The conflicts are related to the used repositories, e.g. there's one conflict I solved, to keep the nv driver. Since nouveau driver can't be used for audio productions and nvidia proprietary just will work with some audio production capable kernels. Too bad that there's no serious multimedia repository for Debian. Is there any way to manage this issue with aptitude, apt or dpkg? Is there any repository that takes care of current Linux audio and video capabilities without running into dependency hell? That does mean that there has to be the possibility to get a package or at least to keep it possible, to self compile Ardour3 with videotimeline, qtractor and jack2 from subversion, ALSA to get a RME HDSP AIO run, to keep the nv driver etc., without the need to puzzle half a year, 8 hours a day through thousands of conflicts. Since testing is outdated for audio and video software, but anyway needs downgrades to stable for X packages, to use audio and video software, I wonder if Debian is interested in video and audio. We are living in media age and not everybody just wish to do amateur audio and video editing. Sorry, I'm pissed, since I would finish a production and need to upgrade, then I anyway would have to fight with compatibility issues, not seldom a production isn't compatible to upgraded packages. Is there really the need to use an OS/ a computers with it's own OS from evil companies to work professional? Why can't I simply protect packages against being removed? A lock for those packages by Synaptic doesn't. You need to search conflicting packages and to lock those against upgrading. If the conflict is known by the package management, why isn't it shown, why will it automatically remove important packages. Odd behaviour! No, much more, it's buggy, a broken OS. :( Ralf -- 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/1316797408.2362.55.camel@debian
