[00:00] <jdong> ok will do
[00:06] <lool> jdong, persia: updated the bug
[00:06] <jdong> thanks
[00:06] <persia> lool: jdong: Thanks
[00:07] <lool> Hmm but jdong wasn't upgrading from karmic
[00:07] <lool> Which is precisely the code path which the SRU addresses
[00:07] <persia> jeandaniel: Was your install an upgrade from karmic?
[00:08] <jdong> lool: ah, that makes a difference?
[00:09] <zul_> persia: ping
[00:09] <persia> zul_: Your name was mentioned to help verify bug #576662
[00:10] <persia> zul_: Your machine doesn't happen to be an upgrade from karmic, does it?
[00:10] <zul> persia: no i upgraded fine
[00:10] <persia> OK, I'm feeling a lot more comfortable.
[00:11] <mdeslaur> zul: did you upgrade to the latest grub2 update?
[00:11] <mdeslaur> zul: actually, are you using grub2?
[00:11] <lool> jdong: Yup
[00:11] <lool> persia: I mailed cjwatson now
[00:11] <zul> mdeslaur: yeah im not sure which version of grub im using...gimme a sec
[00:11] <zul> assuming this is on the mac right?
[00:12] <jdong> yes
[00:12] <lool> persia: Fwed to you
[00:12] <lool> Not sure whether I should forward to TB
[00:12] <persia> lool: Thanks.
[00:12] <lool> Seems overkill
[00:12] <persia> I think it's overkill with the chourus of negative replication attempts.
[00:12] <zul> persia: 1.98-1ubuntu6 but im not running it from a MBR
[00:13] <persia> zul: I didn't think you *had* an MBR on a MacBook.
[00:13] <lool> persia: Dont you need to tag one bug regression-update?
[00:13] <jdong> lool: if everyone were reproducing it, then I'd panic and get the TB involved. Right now, that does not seem to be the case.
[00:13] <persia> sbeattie told me to tag it verification-failed
[00:13] <lool> Hmm I fantasy that regression-update tag I think
[00:14]  * lool => bed &
[00:14] <jdong> persia: is it still in -proposed?
[00:14] <jdong> or -updates already?
[00:15] <jdong> it's in -updates
[00:15] <persia> jdong: -updates
[00:15] <jdong> it's a regression-update, not a verification-failed
[00:15] <persia> Ah.
[00:15] <jdong> v-f is for -proposed packages not working
[00:15] <persia> sbeattie: ^^
[00:15] <persia> Does that tag go against the new bug or the old bug?
[00:18] <jdong> errrrr it should go against the old bug, the actual SRU
[00:18] <jdong> and probably this bug should be tagged dupe of the original SRU as well, if we're 100% sure the SRU is the cause.
[00:19]  * persia got very different instructions in #ubuntu-testing a while back, and suspects there would be benefit to an ubuntu-sru+sru-verification meeting
[00:20] <persia> regression-update added to 508173
[00:33] <cnd> I have a new package in debian sid, and I'd like to do a sync request to have it synced to lucid
[00:33] <cnd> should I be using the -e option of requestsync in this instance?
[00:35] <xnox> cnd, it should go at SRU
[00:35] <xnox> !SRU
[00:35] <xnox> cnd, i don't know whether requestsync supports that =)
[00:36] <xnox> cnd, try it and change the resulting bug report to match SRU requirements
[00:36] <cnd> xnox: are you sure? this wouldn't be an update to an existing package
[00:36] <persia> cnd: Can't do it.
[00:36] <xnox> cnd, we have released lucid already you can't add *new* packages
[00:37] <cnd> persia: oh, I thought you could
[00:37] <persia> cnd: New packages have to appear in new releases.  Once it's in maverick, it can be backported.
[00:37] <cnd> ok, nm then
[00:37] <cnd> thanks!
[00:37] <persia> So you can get it into lucid-backports, but not lucid.
[00:37] <YokoZar> oh snap I think I found a genuine dpkg bug
[00:37] <cnd> yeah
[00:37] <persia> (and not lucid-updates)
[00:38] <xnox> YokoZar, what about?
[00:40] <YokoZar> xnox: https://bugs.launchpad.net/ubuntu/+source/wine1.2/+bug/571999  -- it seems to be using the wrong Conflicts information.  wine (karmic) user upgrades, wine (lucid) is a dummy package that installs wine1.2 (lucid).  wine1.2 (karmic) conflicts with wine, but wine1.2 (lucid) doesn't conflict.  dpkg refuses to upgrade, saying that wine1.2(lucid) conflicts with wine.
[00:41] <xnox> hmmm shouldn't wine (lucid) have Conflicts wine << version.in.karmic?
[00:41] <xnox> that way you make sure that wine karmic is removed first and then lucid's wine1.2 is installed
[00:41] <xnox> ?
[00:41] <YokoZar> xnox: err yeah, it does
[00:42] <xnox> huh
[00:42] <xnox> now this is strange
[00:42] <xnox> let me look
[00:42] <YokoZar> xnox: if you look at the log it upgrades wine(karmic) to wine(lucid)
[00:45] <lifeless> maxb: https://code.launchpad.net/~maxb/ubuntu/maverick/junitperf/ari-tczew-lp-521390/+merge/24868 - are you entirely happy with the diff that bzr is generating ?
[00:46] <lifeless> maxb: I'm looking at the mail that was sent out and wondering if we can make what you're doing more obvious
[00:46] <maxb> Well, what I was trying to do was to discover whether playing with prerequisite branches could make LP generate a nicer diff, and the answer seemed to be no
[00:48] <maxb> I think the one absolute that can be agreed on is that there is no single diff that is appropriate for all merges
[00:48] <xnox> YokoZar, I've added useful comment to that bug.
[00:51] <lifeless> maxb: we can try.
[00:51] <lifeless> maxb: so what structure of pre-req branches did you use?
[00:51] <maxb> I just tried pointing it at lp:debian/junitperf. It conflicted horridly
[00:52] <xnox> maxb, I've tried using prerequisite branches before and it seems like the merge generation uses 3-way diff instead of actually performing bzr diff --old --new. I've tried to represent debian sid, ubuntu-merge (my) & ubuntu-current branches for a package and both diffs on the merge proposal
[00:52] <xnox> had conflict markers although if you pull the branches in order on your machine they are fully merged and have no conflicts
[00:53] <xnox> there is a bug about it tagged with "udd" but i can't be asked to search for it now =)
[00:55] <lifeless> maxb: what did you expect/want it to do ?
[00:56] <maxb> I expected it to not do what I wanted. I vaguely hoped it might do something useful :-)
[00:56] <xnox> I was expecting pre-requisite to generate: debdiff between candidate version and current debian. debdiff between candidate and current ubuntu version =)
[00:57] <ajmitch> maxb: I was able to diff the branch there against the debian branch locally without any issues
[00:57] <xnox> I failed to achieve that =)
[00:57] <maxb> Ultimately I think there needs to be a special merge proposal mode specifically for ubuntu merges
[00:59] <maxb> You really want to see two diffs: (1) common-ancestor(merge-source, debian-equivalent-of-ubuntu-merge-target)..merge-source  and (2) result-of-merge as we have now, but only the debian/ directory
[01:05] <lifeless> maxb: lets try for better labels
[01:05] <lifeless> maxb: I think you mean 'code changes' and 'packaging changes' as separate diffs
[01:06] <maxb> The thing about my (1) is that it is *not* 'change introduced by this merge', it is 'ubuntu delta remaining after this merge'
[01:10] <lifeless> maxb: thus why we want better labels.
[01:10] <lifeless> maxb: so there are three things that may be interesting in a merge from debian:
[01:11] <lifeless>  - upstream changes, debian[code and packaging] changes, ubuntu[code and packaging] changes we're discarding, ubuntu[code and packaging] changes being altered by the merge
[01:11] <lifeless> perhaps
[01:12] <lifeless> I'm going to write a coverall bug on this; I certainly agree that we need more sophisticated review diffs; I don't necessarily agree that we can't come up with a single sane one (as an umbrella thing with sections or something)
[01:18] <psusi> bah!  damn kernel apparently ignores the fact that blocks are in the buffer cache from being read on the raw block device, and reads them again when you read the file
[01:18] <ion> Ouch
[01:19] <psusi> I got ureadahead reworked to read on the raw block device rather than going through the filesystem.... so it finishes real fast and gets peak disk throughput.. but then everything gets read again slowly as the buffer cache is totally ignored
[01:20] <ion> Heh
[01:31] <jdong> psusi: hahahaha!
[01:31] <psusi> I HAVE A PLAN!
[01:31]  * psusi codes like the wind
[01:33] <psusi> I'm going to try reading only the directories through the raw block device, and go back to opening and reading files normally
[01:40] <blendmaster1024> when is DIF for the next release?
[01:40] <blendmaster1024> whatever it's called
[01:44] <virtuald> blendmaster1024: https://wiki.ubuntu.com/MaverickReleaseSchedule
[01:44] <blendmaster1024> thank you
[01:45] <blendmaster1024> i have a game i'm working on that i'd like to see a demo of in maverick
[01:45] <virtuald> :>
[01:45] <blendmaster1024> so i need to have an idea of when to have the demo done by
[01:46] <blendmaster1024> woah i only have till june ...
[01:48] <lifeless> maxb: https://bugs.edge.launchpad.net/launchpad-code/+bug/509901
[01:50] <virtuald> do you guys know of any app for todo lists?
[01:50] <blendmaster1024> is it just me, or is ubottu all-powerful?
[01:50] <blendmaster1024> (j/k)
[01:50] <blendmaster1024> seems like it can do everything any other information bot can, plus a lot
[01:50] <blendmaster1024> is it custom for ubuntu?
[01:51] <virtuald> i don't know much about it, maybe ask in #ubuntu-bots
[01:51] <blendmaster1024> the people there ignore the channel :/
[01:51] <virtuald> ok
[02:19] <imbrandon> blendmaster1024: yes its custom for Ubuntu, originaly written by Seveas , you can find the code for it ( and the other bots ) on Launchpad, they are opensource
[02:19] <blendmaster1024> cool
[04:45]  * ScottK had forgotten how long boost takes to build.
[05:14] <ajmitch> ScottK: will earlier versions of boost be removed from maverick?
[05:14] <ScottK> ajmitch: That would be the goal.  Same as usual.
[05:16]  * ajmitch was just wondering if it was still worth doing the boost1.40 merge
[05:17] <ScottK> ajmitch: I'd vote no.
[05:17] <ScottK> Better spend the time on getting stuff on 1.42 after it's in.
[05:18] <ajmitch> ok
[05:19] <ScottK> pitti: boost1.42 is in source New.  If we can get that through New (source and binary) and into Main and boost-defaults sync'ed before the first autosync run, I think it will save us rebuilds later and make the boost transition easier.
[05:19] <ScottK> That or maybe slangasek will have insomnia and take care of it....
[05:45] <MTecknology> I'm trying to figure this out - how do I use aptitude-run-state-bundle?
[05:45] <MTecknology> If I run it on the file I generated from its counterpart it opens aptitude after working for a while and making a temp directory- but I can't restore teh packages state from it
[05:49] <MTecknology> or am I just using it wrong?
[08:10] <dholbach> good morning
[08:15] <zyga> good morning
[08:57] <arand> andersk: I was thinking of updating my ppa packages with your patch for mountall, just to make sure, your patch replaces Tero Mononen's right?
[08:59] <arand> (I really don't trust my lacking know of code, one bit)
[09:16] <andersk> arand: Yes, my patch replaces all the previous mountall patches. (Plymouth still needs to be patched separately.)
[09:17] <arand> andersk: Okay, I'll slap the new mountall up to my ppa then.
[09:40] <joaopinto> good morning
[11:55] <elleuca> was the "find and replace" OO.o dialog customized in 10.04?
[12:13] <unimatrix> why is fitts's law broken in ubuntu 10.04 again?
[12:13] <unimatrix> doesn't anyone care about this?
[12:13] <Tm_T> unimatrix: is there bug report about this?
[12:13] <unimatrix> Tm_T i've reported one for karmic
[12:13] <unimatrix> and nobody gave a damn
[12:13] <unimatrix> in lucid it's even worse
[12:16] <Tm_T> unimatrix: then you should update that bugreport with new details
[12:16] <unimatrix> Tm_T it's a new bug
[12:17] <unimatrix> https://bugs.launchpad.net/ubuntu/+source/human-theme/+bug/436066 <-- this is the old one (still present in lucid, since karmic)
[12:17] <unimatrix> now i need to open yet another one for the buttons
[12:17] <unimatrix> but what's the point when nobody is going to look at it for the next 5 years
[12:18] <Tm_T> I'd say more than complaining in irc (:
[12:28] <ScottK> asac: I've uploaded the new boost for Maverick (1.42) and it's in New.  The build system changed since 1.40 (no longer using CMake) and so I'm not certain my port of the thumb patch to the new version is complete.  Would you please have someone take a look at it? https://launchpad.net/ubuntu/maverick/+queue?queue_state=0
[12:29] <ScottK> unimatrix: The design group is on #ayatana, so possibly more luck there.
[12:29] <unimatrix> ScottK thanks
[13:13] <pitti> jdstrand: firefox> no, I had a server outage which ate my IRC proxy scrollback
[13:15] <pitti> ScottK: boost1.42 source NEWed to main
[13:16]  * pitti -> back to conference
[13:19] <jdstrand> pitti: k, here you go:
[13:20] <jdstrand> 10:03 < jdstrand> pitti: hi! can I have you opinion on http://people.canonical.com/~jamie/ff36-apparmor.diff.txt? background: there is a pending firefox update and there are these 4 bug fixes to the apparmor profile. the aa profile is disabled by default and no chance of regression (plus, me and several other people use the profile with these commits)
[13:20] <jdstrand> 10:04 < jdstrand> pitti: the question is whether to SRU these separately, with all the associated archive churn, or push them with the pending security update
[13:20] <jdstrand> 10:05 < jdstrand> pitti: I wouldn't normally ask, but in the case of firefox, upstream adds features and bug fixes beyond security fixes, so these low regression potential items seemed kinda gray...
[13:21] <jdstrand> (don't worry about Chris' changelog entry-- it is unrelated)
[13:21] <pitti> jdstrand: looks safe to me, I think it's fine to include it
[13:24] <ogra> hmm, is the archive usable now ?
[13:24]  * ogra wonders why uploads still end up in unapproved
[13:25] <pitti> ogra: I asked for thawing
[13:25] <pitti> (yesterday and today)
[13:25] <ogra> thanks :)
[13:25] <jdstrand> pitti: thanks!
[13:25] <pitti> but I can't be on IRC very often during the conference
[13:25] <ogra> indeed
[13:36] <nigelbabu> lool: so whats the final call on the MIR?
[13:55] <ScottK> pitti, doko: dpkg-checkbuilddeps: Unmet build dependencies: build-essential <-- boost1.42 - It sure didn't do that when I test built it last night .....
[13:56] <doko> ScottK: yes, there are other strange things: see the binutils build failure on i386 ...
[13:57] <ScottK> doko: OK.  I'll be patient then.
[14:24] <wgrant> doko: Those build failures are some pretty odd maverick brokenness.
[14:24] <wgrant> http://paste.ubuntu.com/429514/ looks reasonably bad.
[14:24] <wgrant> ScottK: ^^
[14:25] <ScottK> Thanks.
[14:25] <ScottK> Some kind of in completeness in the switch to 4.5 then.
[14:25] <wgrant> Looks like it.
[14:26] <ScottK> pretend that space wasn't there...
[14:26] <wgrant> Well, I can't see gcc 4.5 anywhere, except in some dependency lines.
[14:39]  * StevenK twitches at ScottK's sync package name
[14:40] <ScottK> The boost-defaults one?
[14:40] <StevenK> ScottK: python-django-djblets
[14:40] <ScottK> Ah.  Yes.
[14:40] <StevenK> It has djb in it. Worse, implications of more of them. Noooooooooooooooo.
[14:40] <ScottK> Stuff like that you just can't make up.
[14:44] <soren> ScottK: Why is it called djblets? I don't see any references to djb in there. :-/
[14:45] <ScottK> soren: I just fixed it.  I didn't name it.
[14:45] <soren> ScottK: I just thought you might know.
[14:45] <StevenK> I think I'd rather blacklist it, than sync it
[14:45] <ScottK> You'd have to remove it too.
[14:46] <ScottK> And that still wouldn't remove the history.
[14:46] <StevenK> No, I can do them seperately
[14:46] <StevenK> blacklisting just means it can't be synced
[14:46] <StevenK> It is able to exist in the archive while being blacklisted
[15:08] <ryan22> ive decided to fork ubuntu
[15:09] <ejat> ?
[15:09] <ryan22> I have serious concerns about the release system employed by Ubuntu and feel that the sound system it uses is inadequate for the needs of the average user (it can stream music to your kitchen but can't play games...). The proposals I posted on the Ubuntu developer mailing lists were rejected so I will be taking infinityOS, my distribution, in a different direction then Ubuntu. infinityOS will remain 100% binary compatible with Ubuntu. My go
[15:09] <ryan22> for infinityOS to become the Firefox to Ubuntu's Mozilla.
[15:10] <ryan22> My distribution will be switching from PulseAudio to OSS4 as it provides per-application volume controls while remaining compatible with existing applications and code.
[15:11] <ryan22> I find the notion that existing application should modify their code to work PulseAudio ridiculous, especially when OSS4 works without modification
[15:12] <ryan22> *with
[15:13] <ScottK> ryan22: Off topic for this channel.
[15:13] <ryan22> alright
[15:13] <ryan22> sorry
[15:14] <ryan22> i have told the ubuntu developers that will remain in contact with upstream
[15:14] <ryan22> *I
[15:39] <dholbach> Last day of https://wiki.ubuntu.com/UbuntuOpenWeek starts in 21m in #ubuntu-classroom with "Introduction to Ubuntu Development"
[15:40] <nigelbabu> Can someone moderate my mail to ubuntu-devel titled "patch day success"?
[15:54] <nigelbabu> cjohnston: ^^^
[15:54] <nigelbabu> cjwatson: ^^^
[15:54] <nigelbabu> cjohnston: sorry ;)
[15:55] <cjohnston> uh huh
[15:56] <nigelbabu> tabfail :/
[17:27] <lool> nigelbabu: No final call on the MIR; as I noted, I'm not sure it's needed anymore
[17:38] <zul> lool: is this the MIR for backuppc?
[17:38] <lool> zul: Yes and know
[17:38] <lool> zul: backuppc is in main already
[17:38] <lool> zul: It's the MIR on a dep
[17:38] <lool> a perl lib
[17:38] <zul> lool: ah ok
[17:39] <lool> https://bugs.launchpad.net/ubuntu/+source/libtime-modules-perl/+bug/525512
[17:39] <bulettin> хм
[18:22] <nigelbabu> lool: ok :)
[18:25] <ccheney> if printing under gnome thinks your printer is out of paper but it isn't is there any way to fix it without rebooting?
[18:26] <ccheney> i tried restarting cups but it doesn't seem to help
[18:26] <ccheney> is there some cups command to reinit the printer?
[18:31]  * ccheney decided to just yank the usb cable, couldn't find a way to make it work otherwise :-\
[19:18] <Azoff> &wc
[19:23] <ScottK> ccheney: You obviously didn't read enough Ubersoft recently.  If you had, you'd know that printing never works.
[19:23] <ccheney> ScottK: heh
[19:24] <ccheney> apparently for the hp printers if the printer ever runs out of paper it doesn't have the ability to determine you put more in, you have to reset the printer by yanking the cable
[19:25] <ScottK> Weird.
[19:25] <ScottK> I don't have that problem (HP printers, but KDE).
[19:37] <psusi> I hate HP printers... used to do IT desktop support at a big company that used HP network printers... we had to keep two different windows drivers for the thing and swap people back and forth because one version supported printing on the front and back of a page, and the other supported printing 2 or 4 pages on on.. but for some reason hp couldn't just put both features in one driver
[19:37] <psusi> that and their drivers always seem to busy wait, pegging the cpu to 100% while printing
[19:39] <psusi> and they seemed to be growing by leaps and bounds every year... probably up to a gigabyte download these days just for a damn driver... heh.
[19:42] <jdong> psusi: my experience with HP printers has been far worse in a diffrent way.
[19:42] <jdong> psusi: almost all of them accept unauthenticated magical packets to put "FEED ME" on the screen and other cute office pranks...
[19:43] <jdong> psusi: but some of them are insane enough to have a Java VM and 128MB RAM onboard
[19:43] <psusi> lol
[19:43] <jdong> once I've found a *NESSUS SCANNER* running on an HP printer on our network
[19:43] <jdong> no idea how it was put on there, but probably there's a magical kiss of death packet for loading your own fun toys onto the printers.
[19:43] <psusi> a what?
[19:43] <jdong> psusi: metasploit-type vulnerability scanner
[19:43] <psusi> oh dear
[19:44] <jdong> e.g. kinda like nmap but it can tell you "192.168.1.4 is vulnerable to CVE-...."
[19:44] <jdong> yeah....
[19:44] <psusi> rootkit on a printer... damn... heh
[19:44] <jdong> I have to give the kid creativity points though. Who'd check the printer's traffic as a suspect for foul play?
[19:44] <psusi> yea
[19:46] <psusi> heh, reminds me of an exploit I found in highschool on our netware server... found out that the print server had an object in the netware bindery it logged in as that was supervisor equivalent... with no password... patched the login program to change the type id from user to printer when logging in and presto, instant all access pass ;)
[19:46] <psusi> nobody ever noticed that the print server had supervisory access... never expected anyone to be able to log in as one
[19:47] <jdong> haha yeah, high school exploits are the most amusing
[19:47] <psusi> hehe.... I had a real cool teacher for a few years... his policy was if you're smart enough to get one by him, you're smart enough to keep it and be trusted not to muck things up
[19:48] <jdong> yeah I had a good relationship like that too. I found ways around their proxy for SSH'ing to my machine and doing other benevolent things, and they let me do it as long as it didn't disrupt the network or get used for malicious purposes
[19:51] <topfs2> I have abit of a problem. Can anyone confirm UPower sleeping signal working in ubuntu? it should be in UPower 0.9.1 but it doesn't work for me
[20:17] <ScottK> doko: Any thoughts on fixing build essential?
[20:27] <gangil> is there an alternative of dkio.h in ubuntu ?
[21:04] <zaytsev> hi! could someone please advise me on why my package build fail on ubuntu < karmic. I'm changing permissions for some files in lib in  binary-post-install and it works for karmic and lucid, but others can't find the file
[21:04] <zaytsev> https://launchpad.net/~zyv/+archive/ppa/+packages <-- the whole series is here
[21:08] <Redache> 8
[21:10] <zaytsev> Very confusing
[21:10] <zaytsev> It seems that although the builds do not fail, the permissions are on changed even on karmic / lucid
[21:10] <zaytsev> -rwxr-xr-x root/root     10472 2010-05-07 19:53 ./usr/lib/mc/cons.saver <-- supposed to be root:tty and sgid
[21:12] <Laney> you should use dpkg-statoverride to do that
[21:13] <Laney> that'll be dh_fixperms resetting it
[21:14] <zaytsev> Laney, google tells me that statoverride is to override the permissions of the maintainer??? I am the maintainer :)
[21:15] <zaytsev> Is there any package that I can refer to see an example on how to use it?
[21:16] <zaytsev> Also, now I use ifeq ($(DEB_HOST_ARCH_OS), linux) to do this changes, because they are linux kernel specific. I am not sure how this will fit
[21:16] <Laney> yes, mediatomb does it
[21:22] <zaytsev> Laney, wow!!! that looks complicated. Is it possible to use DEB_HOST_ARCH_OS in postinst then?
[21:23] <zaytsev> If yes, I guess I have to rewrite it this way
[21:43] <ajmitch>  
[22:06] <zaytsev> Laney, I've found a compelling advice while googling that I can put my permissions reset in package.postinst / configure
[22:07] <zaytsev> This looks hundred times easier than the crazy mediatomb stuff, considering that I have to do overrides for ~10 files
[22:11]  * Laney shrugs
[22:11] <Laney> I don't think it's particularly crazy
[22:11] <Laney> you could also pass -X blah to dh_fixperms if you like
[22:11] <Laney> see the man page
[22:11] <zaytsev> This would be an option if the package wouldn't be CDBS based
[22:11] <zaytsev> Do you think I will blow up something if I do it in postints :) ?
[22:12] <Laney> you have to take care not to stomp over end user changes
[22:15] <zaytsev> Ah, if this is the only trick, who the hell cares :) these scripts are intended to have these permissions and there is no sane scenario when they would have to be changes. Screw the users :) let THEY use dpkg-statoverride :)
[22:16] <Laney> but if they do, you'll override them when your postinst is run
[22:16] <Laney> must go to bed anyway, night
[22:26] <Dandre1> hello,
[22:27] <Dandre1> I have created a local repository with reprepro containing my ow deb files and I get errors when I try to update:
[22:27] <Dandre1> apt-get update gives lines like:
[22:27] <Dandre1> Ign file: lucid/main Packages
[22:27] <Dandre1> how could I see what's going wrong?
[22:43] <ScottK> doko, pitti, etc: gcc-4.5-base | 4.5.0-2ubuntu2 | maverick/universe | amd64, i386 <-- would explain why build-essential is uninstallable.
[22:44] <slangasek> ScottK: fixed
[22:45] <ScottK> Thanks.
[22:45] <ScottK> wgrant: ^^^ Thanks.
[23:51] <xnox> Halarious I broke binutils on my machine =) time to go to bed?