IRC Logs

Network: freenode Channel: #debian

	Enter your search terms Submit search form
	Web www.irclog.org

[07:11]<mjgmnfnfzzzj>!+info kdelibs4
[07:11]<mlcr>Package 'kdelibs4' does not exist.
[07:11]<zun_xjusn>hah
[07:11]<mjgmnfnfzzzj>!+info kdelibs4 sarge
[07:11]<mlcr>kdelibs4: (KDE core libraries), section libs, is optional. Version: 4:3.3.2-6.4 (sarge), Packaged size: 8011 kB, Installed size: 23440 kB
[07:11]<zun_xjusn>there's defiance
[07:11]<mjgmnfnfzzzj>rue_house: you don't specify sid versions unless you're running sid.
[07:12]<zun_xjusn>this is be getting bit for adding unstable package sources to my system to get the things I want isn't it?
[07:12]<rrrm>what is the difference between apt-get upgrade and apt-get dist-upgrade?
[07:12]<mjgmnfnfzzzj>acad: man apt-get; explains it fairly well.
[07:13]<mjgmnfnfzzzj>rue_house: no, you don't want to do that. You shouldn't need unstable packages to build kdenlive.
[07:13]<mjgmnfnfzzzj>if you have to, you want to backport exactly the packages required to build it... but with kde even that may be madness.
[07:13]<zun_xjusn>no I need them for other software packages that otherwise aren't available
[07:13]<zun_xjusn>I think I had to do it to make my nvidia kernel work under kernel 2.6
[07:13]<mjgmnfnfzzzj>rue_house: uh... so build them against sarge, or backport them.
[07:14]<mjgmnfnfzzzj>using packages from sid without understanding what you're doing will end up with your system in the state that you've gotten it in
[07:14]<zun_xjusn>its caught in limbo isn't it?
[07:14]<zun_xjusn>its too old to be new and to new to be old, isn't it?
[07:15]<mjgmnfnfzzzj>rue_house: no, it's just got packages which are from different versions and aren't necessarily compatible. You have to resolve the problems yourself by figuring out what versions you want installed, and which you don't. The curses aptitude interface will help you somewhat.
[07:15]<rryg2jww>so i get the gnome 2.14 splash screen, and when it finally disappears, all i get is the old X gray with the x cursor. what gives?
[07:16]<mjgmnfnfzzzj>RainbowW: the window manager didn't start.
[07:16]<mjgmnfnfzzzj>(for whatever reason)
[07:16]<zun_xjusn>it helped me last time, it cant make sensse out of the mess I have now
[07:16]<zun_xjusn>ok, idea
[07:17]<zun_xjusn>I comment out the unstable packages, and start uninstalling everything supurflious thats gone in over the past 3 days
[07:17]<zun_xjusn>add thing back one piece at a time
[07:17]<zun_xjusn>does apt keep a dated log of my screwups?
[07:18]<rryg2jww>no.
[07:18]<zun_xjusn>cause I know theyaren't in the history files anymore...
[07:18]<zun_xjusn>damn
[07:18]<zun_xjusn>that would be nice
[07:18]<zun_xjusn>how about dpkg, does it keep a log?
[07:19]<zun_xjusn>stardate 21-01-03 4:34 user pushing my buttons by installing less nedit and vim
[07:19]<rryg2jww>dondelelcaro: is there a log somewhere that might explain why the wm isn't starting? or some other useful place i might look?
[07:19]<zun_xjusn>/var/log/Xorg*
[07:21]<rryg2jww>i'll take that as a no.
[07:23]<wryvyrr>lets have a cof
[07:26]<pfuzmjyrr>hello.. im getting a kernel panic after upgrading the kernel. looks like my lilo config is out of wack but i cant access the box as it has no cdrom/floppy to boot thru for fs access
[07:27]<pfuzmjyrr>the error is: kernel panic : not syncing; VFS; Unable to mount root fs on unknown-block (3,2)
[07:27]<pfuzmjyrr>is there any way for me to muck with lilo boot params without getting into the system?
[07:27]<mjgmnfnfzzzj>RainbowW: .ssession-errors often has errors too
[07:27]<nmzzzmjwn2>hello
[07:27]<pfuzmjyrr>i find myself at that ugly red lilo menu but 'e' doesnt do anything :/
[07:28]<mjgmnfnfzzzj>flurdoing: can you boot the system somehow?
[07:28]<pfuzmjyrr>dondelelcaro: nope
[07:28]<mjgmnfnfzzzj>flurdoing: oh, I understand now... you want to specify a root= option there.
[07:28]<nmzzzmjwn2>what is Linux of wiki
[07:28]<mjgmnfnfzzzj>flurdoing: sorry, I thought you meant remotely.
[07:28]<pfuzmjyrr>dondelelcaro: i have another deb box- but its a laptop. i tried connecting the disk to it via this cheap ide->usb cable, but couldnt mount it
[07:28]<mjgmnfnfzzzj>flurdoing: type in the name of the kernel you want to boot, then root=/right/bootpath
[07:28]<mjgmnfnfzzzj>flurdoing: if you want a different kernel, just select it with the arrow keys.
[07:29]<pfuzmjyrr>dondelelcaro: i cant select with arrow keys-- only option is the broken one
[07:29]<pfuzmjyrr>dondelelcaro: so i can specify it manually if i know the name of the kernel (i'm going to have to guess) :/
[07:29]<mjgmnfnfzzzj>flurdoing: the name is what is listed there
[07:30]<pfuzmjyrr>stupid lilo.. it randomly decides whether or not to show me the boot menu :/
[07:30]<lyqzrw0q>how can I mp3 to dcf for my mobile.
[07:31]<zun_xjusn>er? turn up the timeout
[07:31]<mjgmnfnfzzzj>or hold down shift
[07:31]<pfuzmjyrr>rue_house: i'd love to :) if i could only get into the box
[07:32]<pfuzmjyrr>holding down shift works. :)
[07:32]<zun_xjusn>oh sorry, thought you knew that
[07:34]<pfuzmjyrr>any guesses as to what root= should read? :S
[07:34]<wryvyrr>flurdoing: no guessing! read manpage :P
[07:34]<mjgmnfnfzzzj>flurdoing: something like /dev/hda5 or whatever your root device actually is
[07:34]<pfuzmjyrr>i promise to read the manpage once i'm back in my box
[07:35]<wryvyrr>flurdoing: its online, too : )
[07:35]<mjgmnfnfzzzj>unfortunatly, I can't tell you what that is.
[07:35]<mjgmnfnfzzzj>flurdoing: if you really can't do it, boot off of a cdrom or floppy or something
[07:35]<rryg2jww>azureus fails with a cairo error, cairo does not yet support the requested image format. the only google reference i can find is in polish. has someone run into this before?
[07:35]<pfuzmjyrr>yeah.. i'll have to go get a cdrom / fd
[07:37]<rryg2jww>trying that was a disaster too.
[07:38]<rryg2jww>at the moment i'm stuck with qtorrent.
[07:39]<rryg2jww>which is a resonable client if you like no-frills, except of course that it's a cpu hog.
[07:39]<pfuzmjyrr>when it says it was unable to mount root fs on unknwon-block(3,2)-- what exactly is going on?
[07:40]<rryg2jww>flurdoing: it means you're screwed.
[07:40]<pfuzmjyrr>i can keep trying boot= options-- there are few disks/partitions
[07:40]<pfuzmjyrr>does it mean the disk is dead? or does it mean it couldnt find a kernel image? i dont get it :/
[07:40]<wryvyrr>flurdoing: its that the block device is unknown :)
[07:40]<pfuzmjyrr>i had recently done an apt-get (tho it was a while ago) the box rebooted, then this happend..
[07:40]<mjgmnfnfzzzj>flurdoing: it means that it either 1) couldn't find the root filesystem there or 2) doesn't have the right module to mount the device there.
[07:40]<wryvyrr>flurdoing: the numbers are some hardware bus stuff
[07:41]<pfuzmjyrr>box rebooted due to a power failure btw.. so im worried it wrecked my disk
[07:41]<wryvyrr>flurdoing: attach a CD-ROM to it and run a system rescue cd
[07:41]<wryvyrr>flurdoing: there are good ones
[07:41]<pfuzmjyrr>which do you suggest waiting?
[07:41]<wryvyrr>hmmm
[07:42]<wryvyrr>http://www.sysresccd.org
[07:42]<wryvyrr>saves my ass once :)
[07:42]<wryvyrr>:X my prolongued behind
[07:43]<zun_xjusn>instead of saying things like UNSTAISFIED why dont they say "Conflict", or "Available version too old" or "package unavailable"
[07:44]<zun_xjusn>apt errors are SO unhelpfull
[07:44]<wryvyrr>rue_house: because that was unsatisfying ^^
[07:44]<rlv>...but errors is already something else...
[07:44]<wryvyrr>apt, you know a lot
[07:44]<zun_xjusn>but how do I even find out in aptitude WHY is says unsatisfied?
[07:44]<zun_xjusn>I cant
[07:45]<zun_xjusn>I have to apt-get install, look at the failures, and apt-cache policy each one
[07:45]<mjgmnfnfzzzj>rue_house: sure you can. press enter on the package, and look at what is broken.
[07:45]<zun_xjusn>it dosn't say!
[07:45]<zun_xjusn>if I hit enter on a red line, it just gives me a servion number

Back to #debian
Or go to some related logs:
#gentoo
#debian
#netbsd
#reactos
#gentoo