Glitch-y wicd-curses Install
Upgrading wicd-curses 1.7.0-2 to 1.7.0-3 with aptitude on squeeze. First I noticed that wicd was installed, which is supposed to conflict with wicd-curses and which I remember purposefully not installing. But the upgrade asked to remove wicd so I just took that. The install succeeded but threw errors attached below. Have I gotten myself into something here? (Some script-heavy packages can be hard to back out of.) I also have python errors in apt-listchanges. | | Unpacking replacement wicd-curses ... | Preparing to replace wicd-daemon 1.7.0-2 (using | .../wicd-daemon_1.7.0-3_all.deb) ... | Stopping Network connection manager: wicd. | Unpacking replacement wicd-daemon ... | Preparing to replace python-wicd 1.7.0-2 (using | .../python-wicd_1.7.0-3_all.deb) ... | Unpacking replacement python-wicd ... | Preparing to replace shared-mime-info 0.70-1 (using | .../shared-mime-info_0.71-1_i386.deb) ... | Unpacking replacement shared-mime-info ... | Processing triggers for man-db ... | Processing triggers for python-support ... | Setting up iso-codes (3.13-1) ... | Setting up python-wicd (1.7.0-3) ... | Setting up wicd-daemon (1.7.0-3) ... | Installing new version of config file /etc/init.d/wicd ... | Restarting Network connection manager: wicd. | Setting up wicd-curses (1.7.0-3) ... | Setting up shared-mime-info (0.71-1) ... | Unknown media type in type 'all/all' | | Unknown media type in type 'all/allfiles' | | Unknown media type in type 'uri/mms' | | Unknown media type in type 'uri/mmst' | | Unknown media type in type 'uri/mmsu' | | Unknown media type in type 'uri/pnm' | | Unknown media type in type 'uri/rtspt' | | Unknown media type in type 'uri/rtspu' | | Unknown media type in type 'fonts/package' | | Unknown media type in type 'interface/x-winamp-skin' | | Processing triggers for python-support ... | Press return to continue. | -- Kind Regards, Freeman -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Help Please !
On Fri, Dec 25, 2009 at 08:22:12PM +, Kwaku Obeng wrote: >Hi folks, > >My name is Kwaku Obeng and a Ghanaian by birth. I read about Debian a few >months ago on website and I have been trying to download the DVD packs so >I can practice the tutorials on the site but always end up with a corrupt >copy which I am unable to boot from. I therefore wish to make an appeal to >any of you who can send me a copy of the Debian 5.0 DVD Pack. >Thank you. > >My postal address is: An ISO file is an archive. You can't just transfer the archive to a CD. Use a CD burner with an option to a create disk from an ISO image. If you are doing this with Windows, CDburnerXP will work, it is easy and free, http://cdburnerxp.se/ . -- Kind Regards, Freeman -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: rolling-back, reverting system upgrades?
On Mon, Dec 21, 2009 at 06:42:46AM -0800, Andrew Sackville-West wrote: > On Mon, Dec 21, 2009 at 10:43:53AM +, Liviu Andronic wrote: > > Dear all > > How would I roll back system upgrades? > This is the purpose of the testing distribution, to test packages for > breakage so that bugs don't migrate into stable with the next > release. With all due respect, if you aren't prepared to deal with > occaisional breakage, then you should be running testing. > > > In the old times with Gentoo, breakages occurred more often than > > needed, but it was quite easy to revert an upgrade: each > > tree---stable and testing---usually contained several, similar > > versions of the package (much closer than in Lenny and > > Squeeze). That meant that whenever something went wrong after a > > package upgrade, I simply reverted to a previous minor version, got > > on with my work and waited for a new version to pop up. > > as I said above, you can often manually fix things using dpkg and the > old debs. Sometimes you'd have to force it. But to really make this > work, you have to keep careful tabs on what packages were upgraded and > cause the breakage. So far as I know there is no automated way of > doing this. > Two of the machines I use regularly dual-boot into testing. I use one to examine the new packages. The other I leave alone until it seems safe. I like to think I *qualified* myself for testing by learning to use aptitude. In lenny, I had to pin lots of backports packages. (Luckily I didn't get into some system wide pinning scheme.) With aptitude preferences set correctly, I never have to worry about a package being upgraded until I select it and I can always put a package on hold if it concerns me. My rules for running testing with aptitude: 1. Don't treat testing as a "rolling release." Get used to ignoring a sometimes inflated pool of upgradable packages. 2. Consult aptitude's dependency handling and play with it, you might noticing things to help undo log jams. 3. Only upgrade packages that you are comfortable with or well read on, as the case may require. Maybe start here: http://packages.qa.debian.org/common/index.html. 4. Install apt-listbugs. 5. Put packages you are unsure of on hold in aptitude. 6. Set aptitude preferences to display changes in advance and read first. 7. Set aptitude preferences not to delete obsolete packages and don't clean the cache to often. 7.a. However, this may not help with upgrades because the prior version will still be replaced I think. 8. Do the above on a schedule so it doesn't get rushed. I have started to look into apt-cacher to see if that can pool older versions, given the disk space. Currently, my brain doesn't have much info absorption capacity left for that. The other thing, given disk space, might be to dual-boot two installations of testing, one to test testing. "sup dog, I heard you like testing so I installed a version of testing with your testing so you can test testing while your run testing." Maybe too much work. :) -- Freeman -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Sound Only Plays Behind System Bell
I've been installing lenny over the past weeks. All was well. Somewhere the sound stopped working. "I wasn't checking it after each new package." Can't get any test sounds in multimedia selector. Tried different settings there including turning off system sounds. Tried alsaconf even though it said it was unnecessary on lenny. Tried installing alsa drivers with module-assistant. Still modprobe shows nothing about alsa. Left streaming radio playing once and noticed I could here the music behind system bells from xterm. I don't know where to go from here other than to start uninstalling backward through the aptitude log. Not looking forward to that. Any help appreciated! :) -- freeman Chip is SigmaTel STAC9752,53 Results of lspci & aptitude installed packages search: lspci IDE interface: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 1) aptitude search ~isound esound clients esound common flashplugin-nonfree-extrasound libasound2 linux-sound-base sound-juicer aptitude search ~ialsa alsa-base alsa-firmware-loaders alsa-modules-2.6.26-1-686 alsa-oss alsa-source alsa-tools alsa-tools-gui alsa-utils alsamixergui alsaplayer-alsa alsaplayer-common alsaplayer-esd alsaplayer-gtk alsaplayer-oss gstreamer-0.10-alsa libpt-1.10.10-plugins-alsa libpt-1.11.2-plugins-alsa libsdl1.2debian-alsa aptitude search ~ioss alsa-oss alsaplayer-oss libossp-uuid-perl libossp-uuid15 libpt-1.10.10-plugins-oss oss-compat aptitud search ~iesd alsaplayer-esd gstreamer0.10-esd libesd0 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
