[12:24] <phaidros> hi, I'm trying to build my first package. giving my email in changelog, dpkg tries to sign the package. but I run into: gpg: can't connect to `/home/phaidros/.gnome2/seahorse-bRL1iN/S.gpg-agent': connect failed
[12:24] <phaidros> what to do?
[12:26] <phaidros> any hints?
[12:26] <Fujitsu> phaidros: Agents don't work properly with debuild.
[12:27] <phaidros> that would mean to stop seahorse?
[12:27] <Fujitsu> You'll need to comment out use-agent in ~/.gnupg/gpg.conf
[12:27] <phaidros> ok
[12:27] <phaidros> hm, is that possible as env var? (using seahorse for mail and such)
[12:28] <geser> phaidros: see https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/78165 there is a workaround
[12:28] <ubotu> Malone bug 78165 in devscripts "debuild fails to use seahorse-agent" [Undecided,Confirmed]  
[12:28] <phaidros> thanx geser 
[12:29] <geser> Fujitsu: that's only true for the seahorse agent, I've no problem with gnupg-agent, dpkg-buildpackage and signing (even within a chroot)
[12:29] <Fujitsu> geser: I know that that didn't work for me almost a year ago.
[12:30] <geser> seahorse agent or the gnupg-agent?
[12:30] <Fujitsu> gnupg-agent
[12:33] <geser> perhaps it was fixed in between, I've no problems to do signing with gnupg-agent
[12:37] <phaidros> geser, Fujitsu : with that solution it works with seahorse-agent
[12:37] <phaidros> thanx
[01:02] <nixternal> any word on the 2.6.20-15 kernel? is it good?
[01:03] <crimsun> topic of ubuntu+1 kthxbye
[01:06] <nixternal> haha, thanks ;p
[01:07] <TheMuso> heh love the topic.
[01:07] <jdong> not as good as #ubuntuforums :D
[01:47] <Kaleo> Hi everybody
[01:49] <TheMuso> Hi Kaleo 
[01:54] <Kaleo> I am not sure what I should do now for bug 88902
[01:54] <ubotu> Malone bug 88902 in istanbul "sync to upstream to solve some bugs" [Medium,Confirmed]  https://launchpad.net/bugs/88902
[01:54] <TheMuso> Kaleo: Unfortunately, its a little late to update to a new upstream version, as we we less than a week to release.
[01:56] <TheMuso> Kaleo: Oh I see. It has been approved.
[01:56] <TheMuso> Since it is a sync, all you can do is wait, but I doubt that it will be synced in time for the feisty release, given how busy the core dev team are.
[01:57] <bddebian> Heya gang
[01:57] <TheMuso> Heya bddebian.
[01:57] <Kaleo> TheMuso: it's unfortunate but thank you for having taken the time to look at it
[01:58] <bddebian> Hi TheMuso
[02:19] <marcin_ant> hi all
[02:19] <marcin_ant> is there someone that could help me with dbconfig-common configuration?
[02:30] <TheMuso> marcin_ant: Have you read through the docs?
[02:30] <TheMuso> I have found them to be very useful in the past when I have had to work with that package.
[02:32] <marcin_ant> TheMuso: I did but could not find answer for pretty simple question
[02:32] <TheMuso> Whats your question?
[02:32] <marcin_ant> TheMuso: I need to set dbname manually - and I don't know how
[02:33] <TheMuso> marcin_ant: Hold on a sec. I am going to look at a package I worked on recently. I think it did it.
[02:33] <marcin_ant> TheMuso: it's set to database_default (in postinst scripts) and dbconfig is trying to create it's own name that is in fact package name without '-'
[02:34] <TheMuso> marcin_ant: dbc_dbname and dbc_user are the variables you want to work with I think.
[02:34] <TheMuso> Thats how the package I worked on does it.
[02:34] <marcin_ant> TheMuso: so if my base package is  'something' and I create package 'something-different' then dbconfig is going to create 'somethingdifferent'
[02:34] <TheMuso> right
[02:34] <marcin_ant> TheMuso: I know variable name
[02:35] <TheMuso> marcin_ant: Otherwise, I don't know I am affraid.
[02:35] <marcin_ant> TheMuso: what I need is an example where should I input this variable in scripts
[02:35] <marcin_ant> TheMuso: to make dbconfig use this variable
[02:35] <TheMuso> marcin_ant: Download the drupal source. There is a good example in the debian/drupal-5.1.config file.
[02:36] <TheMuso> Thats the package I worked on.
[02:36] <TheMuso> And I tested that package heaps when I was putting it together for an update.
[02:37] <marcin_ant> TheMuso: just downloaded and now I will try to understand this - thank you
[02:40] <pochu> good night folks :)
[02:41] <TheMuso> marcin_ant: No problem.
[02:41] <harrisony> night
[02:41] <marcin_ant> TheMuso: hehe the problem is that I really don't understand this :D
[03:19] <ajmitch> now if I'm lucky, I'll be able to reboot & have a working system still..
[03:46] <unix_infidel> hmm, i thought rc1 was supposed to be released yesterday?
[03:46] <TheMuso> unix_infidel: There have meen many a kernel problem.
[03:49] <unix_infidel> TheMuso: lol, i guess i'll just have to wait another week.
[04:33] <ScottK> ajmitch: I was wondering if you've had a chance to consider the new clamav yet?  Bug #106357
[04:33] <ubotu> Malone bug 106357 in clamav "UVFe for clamav 0.90.2" [Undecided,Unconfirmed]  https://launchpad.net/bugs/106357
[04:34] <imbrandon> re
[04:34] <imbrandon> ajmitch, no problems on reboot ?
[04:39] <ajmitch> imbrandon: nah it was sweet
[04:39] <ajmitch> ScottK: I looked briefly
[04:39] <ScottK> Any thoughts?
[04:40] <ajmitch> it looks like something we want
[04:40] <ScottK> OK.  I put the package together, but I put about as much as I know about packaging into it.
[04:41] <imbrandon> yea -14.something broke mine, but i am doing a fresh install now ( needed to test clean upgrades anyhow )
[04:41] <ScottK> If there's stuff that needs to be cleaned up, I won'd feel bad at all if someone takes over.
[04:41] <ScottK> I did look in the source and make sure the debian/patches all still made sense.
[04:41] <ScottK> ajmitch: Thanks.  I'm off to bed now.
[04:41] <imbrandon> i finaly got another family member off windows after they upgraded to vista for a few weeks and hated it :)
[04:41] <ScottK> Good night everyone.
[04:42] <imbrandon> gnight ScottK 
[04:42] <tonyyarusso> yay imbrandon 
[04:42] <TheMuso> imbrandon: cool
[04:42] <imbrandon> cuts my "family support" down tremendously :)
[04:43] <imbrandon> now i just need to get them off a few windows apps but they work fine in wine for now
[04:43] <ajmitch> hehe
[04:44] <imbrandon> i'm tempted to go ahead an upgrade them to feisty now, so i wont have to venture back over here in a few days and upgrade it
[04:45] <imbrandon> close enough to release, and if -15 is in the archives everything should be ok
[04:45] <ajmitch> yeah
[04:45] <ajmitch> just update your local mirror again
[04:45] <imbrandon> yea, it will run in 15 minutes ( every 2 hours ) anyhow
[04:45] <imbrandon> it runs on even hours
[04:46] <imbrandon> well even hours local time :)
[04:46] <ajmitch> it chews cpu cycles
[04:47] <imbrandon> :)
[04:47] <imbrandon> i finaly picked up 3 700mhz/256mb ram boxen from work "for testing" here at the house
[04:47] <imbrandon> so i have etch on one
[04:47] <ajmitch> hehe nice
[04:48] <imbrandon> they were old old old old workstations from when the company started
[04:48] <imbrandon> i have etch on one, gnu solaris on the other, and the third i havent loaded yet
[04:50] <jdong> imbrandon: Vista!
[04:51] <imbrandon> i'll probably put feisty/ldap/domain controler server for here at the house on the 3rd
[04:51] <jdong> oh come on!
[04:51] <jdong> :)
[04:51] <imbrandon> jdong, my last vista box is going away as we speak
[04:51] <imbrandon> becoming feisty
[04:51] <imbrandon> :)
[04:51] <jdong> :)
[04:51] <jdong> I will follow suit.... as soon as I (1) run out of space (2) Stop being lazy
[04:51] <imbrandon> well not mine but my mom's :) basicly mine because i have to fix it when it breaks
[04:52] <jdong> oh boy if that's how ownership is defined then I'm in a lot of trouble :D
[04:52] <imbrandon> my dads still on XP but he will stay on XP till he dies, no converting him, been trying for years
[04:53] <imbrandon> my mom dont care as long as it "just works"(tm)
[04:54] <jdong> meh sometimes it's too much effort to convert that it's lose-lose :)
[04:54] <imbrandon> yea
[04:54] <imbrandon> ok brb rebooting the live cd
[05:05] <unix_infidel> imbrandon: so why not set them up on a VM?
[05:05] <unix_infidel> ubuntu as the host, xp as the guest, just in case something doesnt "just work"
[05:10] <ajmitch> nice & slow
[05:13] <jdong> VMWare 6 feels a lot faster
[05:13] <jdong> if my wallet were big I'd buy a copy
[05:17] <crimsun> your university has a site license.
[05:19] <jdong> crimsun: whoa we do?
[05:19] <jdong> nobody told me that :D
[05:20] <crimsun> consulted your local vice chancellor of IT/research lately?
[05:20] <jdong> no I haven't....
[05:21] <jdong> "MIT has licenses for VMWare. Send an email to software@csail.mit.edu to get a license number. From the vmware screen, choose 'help->Enter Serial Number' to enter the license."
[05:21] <jdong> hmm....
[05:21] <lfittl> a little OT, but, does anyone know how to stop a process, and then continue it in a screen session?
[05:41] <imbrandon> re
[05:41] <unix_infidel> anyone know what's up with the delayed RC1?
[05:41] <jdong> I think the kernel regressions are causing that, no?
[05:41] <crimsun> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-April/000279.html
[05:41] <imbrandon> unix_infidel,makin sure the kernel actualy boots the system is a good thing
[05:42] <crimsun> imbrandon: bullocks, that's icing.
[05:42] <imbrandon> :)
[05:42] <crimsun> I'm pleased that with the new initramfs, udev, and linux-source, I don't need to pass `break=mount` to the bootloader, though.
[05:43] <imbrandon> whats break= do? havent seen that cheatcode yet
[05:43] <jdong> I've heard it a few times on the forums...
[05:44] <unix_infidel> imbrandon: well is this release delay documented somewhere?
[05:44] <crimsun> unix_infidel: I /just/ pasted the URL.
[05:44] <imbrandon> unix_infidel, yes, crimsun just gave you a link
[05:45] <unix_infidel> spectacular.
[05:45] <crimsun> imbrandon: drops to a busybox shell before it mounts /
[05:45] <ajmitch> hello crimsun 
[05:45] <crimsun> allo ajmitch 
[05:45] <imbrandon> crimsun, ahh
[05:45] <jdong> can you also pass in other subsystems to break?
[05:45] <jdong> like break=alsa? :D
[05:45] <ajmitch> crimsun: I am rather happy about that as well
[05:45] <crimsun> imbrandon: in my instance, hardware was too slow for initramfs/upstart/udev
[05:46] <imbrandon> ahh
[05:46] <crimsun> break=jdong
[05:46] <jdong> :)
[05:46] <ajmitch> for me, it was a combination of the usual lvm & mdadm races with udev, kernel, devmapper
[05:46] <imbrandon> LOL
[05:46] <jdong> I think that's default though :D
[05:46] <imbrandon> for me its fskin network manager on a remote system
[05:46] <ajmitch> purge it
[05:47] <imbrandon> yea i did that 2 times, i need to blacklist it in the apt conf
[06:24] <guiment> will we get the feisty release candidate this weekend?
[06:25] <jdong> guiment: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-April/000279.html
[06:25] <jdong> guiment: unknown ETA right now
[06:25] <jdong> but everyone's working hard going out of their way to get things done
[06:25] <crimsun> colin, kyle, and ben have been troopers
[06:26] <guiment> jdong: so we don't know when the rc will be released, but as soon as it is released we know that one week later will get feisty final?
[06:27] <jdong> I'm not sure how the cycle will play out; maybe others can answer that
[06:27] <crimsun> guiment: I addressed this question some hours ago
[06:27] <crimsun> it all depends on RC
[06:27] <crimsun> stop drinking at the crack fountain
[06:30] <guiment> crimsun: could you pastebin me the log? please..?
[06:33] <TheMuso> cjwatson, BenC and co need a month's break for the work they do.
[06:41] <joejaxx> hello all
[06:41] <joejaxx> how is everyone doing?
[06:42] <harrisony> good
[06:42] <joejaxx> that is good
[06:43] <TheMuso> Hey joejaxx.
[06:48] <joejaxx> hello TheMuso 
[07:22] <ajmitch> hello Hobbsee 
[07:23] <Hobbsee> hi ajmitch 
[09:55] <stgraber> Could any MOTU have a look at bug #85640 when he'll have a moment (easy debdiff ready (two lines) and seems working)
[09:55] <ubotu> Malone bug 85640 in cryptsetup "[Feisty]  crypted root doesnt mount on start (cryptsetup)" [Medium,In progress]  https://launchpad.net/bugs/85640
[09:57] <ScottK> stgraber: Care for a non-MOTU comment?
[09:57] <stgraber> ScottK: Please
[09:58] <ScottK> Normally you put (Closes LP: #85640) at the end of the relevant changelog entry.  I think that's the syntax.
[09:58] <ScottK> Also when you want it reviewed for upload subscribe (not assign) Ubuntu-Universe-Sponsors to the bug.
[09:59] <ScottK> When you do that, put the status back to confirmed.
[10:00] <ScottK> You might also put in the comments what you've done to test the fix (particularly this late in the game).
[10:00] <ScottK> stgraber: That's it.
[10:01] <stgraber> ScottK: Ok, I'll do a quick changelog update
[10:02] <ScottK> Depending on who reviews it, some of them care more than others about that.
[10:03] <stgraber> (Never had any problem with that even when uploading to main, but who knows :))
[10:06] <StevenK> ScottK: (LP: #xxxxx)
[10:06] <ScottK> Ah.
[10:06] <ScottK> stgraber:  ^^ What he said.
[10:06] <stgraber> hmm, I'm going to flood the bug report :)
[10:07] <ScottK> Nah.  You should look at the bug report on the borked kernel.  That was a flooded bug.
[10:08] <stgraber> hehe :)
[10:10] <stgraber> ok, attached, status reset to confirmed and ubuntu-universe-sponsor is subscribed
[10:11] <ScottK> That should at least get it looked at.
[10:12] <stgraber> Yep, I hope for those people that it'll be uploaded, but we are coming really close to the final release ... (Personally I don't use that stuff, so ...) :)
[10:14] <crimsun> siretart: ping, can you confirm http://librarian.launchpad.net/7211179/bug85640.debdiff is a correct fix?
[10:14] <crimsun> (I don't recall immediately who uses cryptsetup...)
[10:14] <siretart> crimsun: I believe that it works, but I didn't have the chance to actually test it
[10:16] <crimsun> RAOF: as an earlier explanation for banshee 0.12.1, both andrew and I have approved the exception here on irc last week
[10:16] <RAOF> Ah, ok.
[10:16] <RAOF> Once I actually thought about it, I did wonder :)
[10:17] <crimsun> siretart: / stgraber: I'm fine with that debdiff if it fixes the issue correctly
[10:17] <RAOF> crimsun: Do you still want it, or have you done it yourself?
[10:17] <crimsun> RAOF: I have not done it
[10:18] <crimsun> RAOF: you mentioned another fix that you wanted to merge, and as I didn't know to which you were referring, it was in my best interest to not do the merge myself
[10:19] <RAOF> Ah, it was a trivial fix for bug #99817, but it's in no way important.
[10:19] <ubotu> Malone bug 99817 in banshee "[feisty]  stop hotkey not working" [Undecided,Confirmed]  https://launchpad.net/bugs/99817
[10:21] <crimsun> RAOF: http://librarian.launchpad.net/7297978/lp-99817.debdiff looks fine to me
[10:41] <ajmitch> hm, so we have to decide on clamav 0.90.2
[10:41] <ajmitch> siretart: what do you think?
[10:41] <crimsun> I'm fine with a +1, too
[10:42] <ajmitch> ok, I got the impression you wanted it in backports instead
[10:42] <crimsun> well, I'm not familiar w/ upstream's release history
[10:42] <lritter> hey there
[10:42] <lritter> there is a release soon i heard
[10:43] <ScottK> lritter: Yes.
[10:43] <lritter> are you guys aware that cd burning with gnomebaker is broken for regular users? ;)
[10:43] <ScottK> Do you have a bug number?
[10:43] <lritter> i filed a ticket some time ago but there was no reply
[10:43] <lritter> yes
[10:43] <lritter> sec
[10:43] <lritter> 93750
[10:43] <lritter> eek
[10:43] <lritter> 75753
[10:44] <lritter> fix already released
[10:44] <crimsun> how is clamav's release history? The changes seem a bit large for this late in the cycle, but I'm ok with it if upstream's release history is good.
[10:44] <lritter> didn't check my mail
[10:44] <lritter> allright :)
[10:44] <crimsun> ^ ScottK 
[10:44] <ScottK> crimsun: I don't know.
[10:45] <ScottK> I do know that we aren't carrying any bugfix patches in debian/patches
[10:45] <ScottK> They are all config issues and one doc typo.
[10:45] <lritter> i suppose i just have to reboot once and then it works ;)
[10:46] <ScottK> crimsun: I also wonder about the impact of http://lurker.clamav.net/message/20070413.012951.1d50edff.en.html
[10:46] <ScottK> If we are stuck on an unsupported version number, that impacts us even if we SRU the important fixes.
[10:47] <ScottK> As I said in the bug, I'm glad I don't have to decide.
[10:47] <crimsun> hmph.
[10:47] <crimsun> well, I think upstream just trumped my caution.
[10:48] <ScottK> In general I think it's lower risk to take a tested bugfix release than to cherrypick when you don't have a lot of time.
[10:48] <crimsun> if they're going to disable 0.90.1, I don't think we have any choice.
[10:49] <stgraber> crimsun: Looking at the comments I've received it seems to fix that issue, but as I've already said I'm not a user of that stuff myself.
[10:49] <ScottK> Then I'd encourage you to expend the caution on picking over the package as I am not experienced enough to have seen all the potential landmines.
[10:50] <crimsun> ScottK: 106357 updated accordingly.
[10:51] <ScottK> OK.  It's on REVU.  http://revu.tauware.de/details.py?upid=4816
[10:51] <ScottK> I can put my i386 .debs online if that would be helpful?
[10:52] <crimsun> working with the source now.
[10:55] <kofler> How would I update a package that's in a repository? For example, I have a local repository that runs a very network specific package in /apt/network/edgy/binary-i386/
[10:55] <ScottK> kofler: Download the source package, modify it, build it, and then install the .deb using dpkg.
[10:56] <minghua> you probably want to change the version number as well
[10:56] <kofler> No, no, I mean there's an apt-mirror on the network that has it in that location.
[10:56] <kofler> I updated the package's source, rebuilt it, etc.
[10:56] <kofler> Now how to I update it on the *repository*?
[10:57] <ScottK> Ah.  Sorry.  Misunderstood.
[10:57] <kofler> dpkg is very ugly. I prefer apt.
[10:57] <ScottK> Sure, but dpkg works if it's not in a repository.
[10:58] <RAOF> And apt just ends up using dpkg anyway, unless I'm mistaken.
[10:58] <kofler> True, but I rather have it update on the repository so cron-apt takes care of it network-wide.
[10:58] <kofler> It does, but it puts it in /var/cache/apt/archives and does other niceties.
[10:59] <siretart> apt-ftparchive packages /dev/null | tee Packages | gzip -9 > Packages.gz
[10:59] <siretart> perhaps with a '.' between packages and /dev/null
[11:00] <kofler> /dev/null ?
[11:00] <siretart> if you have an override file, use that
[11:00] <kofler> I'll go read up on it though. Thanks for the command.
[11:01] <siretart> nearly all (modern) archive management tools use apt-ftparchie as backend
[11:03] <ScottK> Just since I could, the .debs for clamav 0.90.2 I made are here http://www.kitterman.com/clamav/ if anyone wants to test.  Just i386.  Particularly if anyone uses the milter as I don't have a way to really test it.
[11:12] <kofler> Thanks a bunch siretart :)
[11:15] <RAOF> Oh, that's awkward.  Launchpad's down.  crimsun, I've been (trying) to follow MOTU/Merging (that's the right guide, yes?).  Once launchpad's back up, can you give it a run over?  Or shall I throw something up on REVU?
[11:16] <TheMuso> RAOF: There is stuff on the wiki about merging.
[11:17] <RAOF> TheMuso: You mean, wiki.ubuntu.com/MOTU/Merging?
[11:17] <RAOF> Or the wiki.ubuntu.com/Merging MOTU school transcripts?
[11:17] <RAOF> Actually, that last bit is probably not an actual MOTU school transcript :)
[11:18] <crimsun> ScottK: built debs look fine here. Please update debian/changelog to reflect the UVF exception being granted, and explicitly document the fact in debian/changelog that upstream is disabling support for < 0.90.2 on 16 Apr '07
[11:18] <ScottK> Will do.
[11:19] <crimsun> I'm off for a nap; if no one has uploaded in 4 hours, I'll be around
[11:20] <TheMuso> crimsun: I can upload it if you'd like.
[11:32] <ScottK> TheMuso: http://revu.tauware.de/details.py?upid=4817 - I did not rebuild the binaries since I just touched the changelog.
[11:33] <ScottK> TheMuso: If you are going to upload, I just noticed I left a ")" off my changelog entry.  Would you mind fixing it?  I can reupload?
[11:34] <TheMuso> ScottK: I haven't looked yet, so if you can fix it, that would be great.
[11:34] <ScottK> Fixing
[11:38] <jekil> hello
[11:38] <ScottK> hello
[11:42] <ScottK> TheMuso: http://revu.tauware.de/details.py?upid=4818
[11:46] <TheMuso> ScottK: Looking now.
[11:46] <ScottK> Great.
[11:47] <TheMuso> Ouch. Big tarball.
[11:47] <ScottK> Yep.  Mostly virus definitions.
[11:47] <TheMuso> Wow.
[11:49] <ScottK> Nothing like upstream on a security important application dumping a new release on you at the last moment.
[11:49] <TheMuso> Oh yeah.
[11:50] <TheMuso> ScottK: So what are they doing exactly? Dropping support for the old version?
[11:50] <TheMuso> And is this going to break anything else in the archive?
[11:51] <ScottK> They're dropping definition support (at least in part, I'm not sure).
[11:51] <TheMuso> ah just read the changelog
[11:51] <ScottK> Also there are two cves this fixes.
[11:51] <TheMuso> ScottK: So what was changed in the debian/ dir?
[11:51] <TheMuso> Right.
[11:51] <ScottK> I've tested the new debs with Klamav and Clamsmtp
[11:51] <ScottK> Just the changelog
[11:52] <TheMuso> Ok.
[11:52] <ScottK> I did look in the source and make sure that the code touched in devian/patches was unchanged.
[11:53] <TheMuso> Right.
[11:53] <TheMuso> Probably worth getting those patches upstream.
[11:53] <ScottK> Except one doc typo they are all config stuff.  Our stuff has been sent to Debian.
[11:53] <TheMuso> Right.
[11:59] <TheMuso> At least it doesn't take long to build.
[12:00] <ScottK> Yes.  Most of the bulk is definitions, not code.
[12:01] <TheMuso> As you said.
[12:02] <TheMuso> Ok, looks sane.
[12:04] <ScottK> BTW, this excercise is an excellent example of why using a patch system is a very good thing.  It made it much easier for someone relatively new like me to update the package for a new upstream release in short order.
[12:04] <TheMuso> Yes indeed.
[12:05] <TheMuso> ScottK: Uploading now.
[12:05] <TheMuso> I have acked on revu and archived.
[12:05] <ScottK> Great.  Thanks.
[12:05] <ScottK> I'll keep and eye on the bug.
[12:06] <TheMuso> Whats the bug number? I'll attach an upload report once I receive it from soyuz.
[12:07] <TheMuso> Looks like lp is back up.
[12:08] <RAOF> crimsun: When you get back, I've thrown up a merged banshee 0.12.1+dfsg-2ubuntu1 onto REVU, since it doesn't seem that banshee is on merges.ubuntu.com, so I can't follow the merging stuff on the wiki.  I'm off for dinner, but I'll be back later if you need/want anything more.
[12:08] <ScottK> Bug #106357
[12:08] <ubotu> Malone bug 106357 in clamav "UVFe for clamav 0.90.2" [Undecided,Confirmed]  https://launchpad.net/bugs/106357
[12:08] <TheMuso> ScottK: Thanks
[12:08] <ScottK> RAOF: Usually for a merge you attach the debdiff for the new version to the merge request bug.
[12:09] <ScottK> np
[12:09] <TheMuso> Still uploading...
[12:09] <ScottK> Not suprising.
[12:09] <Nafallo> RAOF: banshee has the same maintainer in Debian and Ubuntu. you might want to ask slomo before :-9
[12:09] <Nafallo> :-)
[12:11] <RAOF> I've kinda assumed that crimsun did that before asking me.  Mightn't be a bad idea, though :)
[12:19] <TheMuso> ScottK: Uploaded.
[12:20] <ScottK> TheMuso: Thanks.  I think I'll go sleep now (It's roughly 6AM here).
[12:20] <TheMuso> ScottK: Wow you've been up a long time.
[12:20] <TheMuso> Enjoy it.
[12:21] <ScottK> TheMuso: Yes, but it seemed important to get done.
[12:21] <TheMuso> Yeah.
[01:00] <ScottK> Bug #96090 is ready for UUS review if anyone is there.  
[01:00] <ubotu> Malone bug 96090 in klamav "[apport]  klamav crashed with SIGSEGV" [Medium,Confirmed]  https://launchpad.net/bugs/96090
[01:00] <ScottK> TheMuso?
[01:00] <ScottK> And I'm really going to bed now.
[01:01] <TheMuso> ScottK: heh
[01:01] <TheMuso> ScottK: I'm on it.
[01:01] <ScottK> Thanks.
[01:02] <TheMuso> ScottK: Tested I assume?
[02:32] <damko> ciao!
[02:47] <damko> pastebin doesn't work??
[02:47] <damko> Query failure: Can't open file: 'pastebin.MYI'. (errno: 145)
[02:48] <damko> is there another site like pastebin?
[02:48] <TomaszD> http://wklej.org
[02:48] <damko> thanks!
[02:48] <TomaszD> np
[02:49] <damko> for bash guru and for fun: how do u solve this problem? http://wklej.org/id/f8284bd2a1
[02:50] <ajmitch> nest them
[02:50] <damko> ajmitch: how ?
[02:50] <ajmitch> $(expr  $(sfdisk -s $2) / 1024)
[02:50] <ajmitch> or similar
[02:51] <ajmitch> ` doesn't nest like $() does
[02:51] <damko> ah thanks for the tip. i try
[02:54] <damko> ajmitch: wow .. then it means that b=$(sfdisk -s /dev/sdb) it's equal to b=`sfdisk -s /dev/sdb`, right? very nice. it works. thanks
[03:50] <cbx33> hey all any gsoc mentors around
[03:53] <ajmitch> night all
[03:59] <joejaxx> Good Night ajmitch 
[04:07] <Lathiat> anyone here using cacti on dapper?
[04:08] <Lathiat> i've attempted to basically copy debian sids update to 0.8.6i onto 0.8.6h in dapper to fix the security issues
[04:08] <Lathiat> and was hoping for some testing
[04:08] <Lathiat> seems to work here
[04:08] <StevenK> Lathiat: As in Debian's patch applies fine to the 0.8.6h in Dapper?
[04:08] <Lathiat> it seems to
[04:08] <Lathiat> hrm
[04:09] <Lathiat> heh
[04:09] <Lathiat> or not
[04:09] <StevenK> Heh
[04:09] <Lathiat> i didnt' save 00list
[04:09] <Lathiat> hrm almost applies
[04:09] <Lathiat> i'll fix this patch 
[04:10] <Lathiat> i've had 2 of my machines hacked by this bug because i was lazy and a mates as well so i figured i might try update the packages
[04:10] <StevenK> Lathiat: If it works for you and someone else, talk to pitti or keescook about it.
[04:10] <Lathiat> StevenK: ya this is why i was asking if anyone wanted to test it ;)
[04:23] <Lathiat> ok i got it working now
[04:45] <jrib> hi, does motu want to be assigned to needs-packaging bugs?  The email to the bug list didn't mention it, but I see a few needs-packaging bugs assigned to motu
[05:26] <jekil> if I submit a deb to revu now, i must set changelog to feisty or feisty+1? feisty+1 right?
[05:27] <Nafallo> it has a name you know... gutsy :-)
[05:27] <Nafallo> but I don't know the answer anyway :-P
[05:29] <jekil> i think gutsy because now feisty are in freeze..
[05:42] <jdong> Nafallo: gushy :)
[05:42] <jdong> Nafallo: see #ubuntuforums topic :)
[05:43] <Nafallo> I don't use forums! :-)
[05:43] <jdong> Nafallo: just read the topic :)
[05:43] <Nafallo> I'm lazy :-)
[05:43] <jdong> || Next release Gushy Giblets!
[05:44] <Nafallo> hmm. they are wrong. they should sign up on mailinglist. the TRUE informationsource ;-)
[05:44] <jdong> lol
[05:44] <jdong> and you get great pill deals too!
[05:44] <jdong> ;-)
[05:44] <Nafallo> haha
[05:44] <Nafallo> my bogofilter makes me not see those :-P
[05:59] <ScottK> jrib: No.  Don't assign them to MOTU.  MOTU approves new packages, but doesn't necessarily do the packaging.
[06:00] <jrib> ScottK: thanks
[06:02] <ScottK> TheMuso: Thanks for taking care of the klamav update.
[06:06] <jekil> so, i must set  gutsy in changelog?
[06:07] <pochu> jekil: yep
[06:07] <jekil> pochu: thanks
[06:08] <pochu> jekil: because it won't be accepted in Feisty :)
[06:08] <pochu> Too late ;)
[06:54] <_MMA_> Could someone close Bug #106560 for me. GIMP 2.3 isnt in the repos.
[06:54] <ubotu> Malone bug 106560 in ubuntustudio-meta "ubuntustudio-graphics needs gimp-svg v2.2.x! (Doesnt work with gimp v2.3.x))" [Undecided,Unconfirmed]  https://launchpad.net/bugs/106560
[06:55] <joejaxx> is that what the rejected status is for?
[06:55] <ScottK> I got it.
[06:56] <_MMA_> Thanx
[06:59] <ScottK> Done. Bug #106560
[06:59] <ubotu> Malone bug 106560 in ubuntustudio-meta "ubuntustudio-graphics needs gimp-svg v2.2.x! (Doesnt work with gimp v2.3.x))" [Undecided,Rejected]  https://launchpad.net/bugs/106560
[06:59] <_MMA_> ScottK: Im sorry. I thought you had to be MOTU to do it. I could have handled it. :)
[06:59] <_MMA_> Thanx though. :)
[07:00] <ScottK> Now you know.  The only thing you can't do without being MOTU, core-dev, or ubuntu-qa is set importance.
[07:00] <_MMA_> Ahh... Gotcha.
[07:00] <joejaxx> gnomefreak: maybe so
[07:00] <joejaxx> gnomefreak: but ubuntustudio-meta only exists in feisty
[07:00] <gnomefreak> but i am thinking its 2.2.13
[07:01] <_MMA_> gnomefreak: I dint know. I use gimp-svg from the repos just fine here. :(
[07:01] <gnomefreak> so im not real sure
[07:01] <joejaxx> _MMA_: same here
[07:01] <ScottK> gnomefreak: We'll find out if he replies to the bug I guess. TheGimp 2.1 was never in the Ubuntu repos, so either way, it's rejected.
[07:01] <gnomefreak> true
[07:02] <_MMA_> Shouldnt have been filed against "ubuntustudio-graphics" anyway. ;)
[07:02] <gnomefreak> there seems to be a 2.3 in devel in gimp
[07:03] <damko> bye! wish u all a good w.e.
[07:03] <gnomefreak> damko: you too
[07:03] <ScottK> Heh! - http://www.computerpartner.nl/article.php?news=int&id=5003 "Microsoft: Word 2007 crashes are a feature, not bug"
[07:03] <xtknight> lol
[07:04] <gnomefreak> lol
[07:04] <xtknight> see this? http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf
[07:04] <damko> :-)
[07:10] <syke> hi
[07:10] <ScottK> Hello
[07:10] <syke> how do I request a package to be updated for feisty?
[07:10] <syke> monodevelop 0.12 is what installs, but 0.13.1 is the first one that is really usable
[07:11] <gnomefreak> file a bug on it.
[07:11] <gnomefreak> is .13 stable?
[07:11] <ScottK> syke: But Feisty gets released in roughly a week, so it's extremely unlikely a new version gets brought in.
[07:12] <gnomefreak> oh he said feisty :(
[07:12] <syke> 0.13 is the only monodevelop version I have used that didn't crash within 10 minutes of usage
[07:12] <gnomefreak> feisty wont get anything now
[07:12] <ScottK> If there are specific bugs it fixes, someone (maybe you) might extract patches to fix the current one.
[07:13] <xtknight> could an updated pkg come thru the updates?
[07:13] <syke> specific patches aren't really possible, I don't think
[07:13] <xtknight> or only backported bugfixes to the current revision?
[07:13] <syke> if updating isn't a possibility, I would really just remove the pkg
[07:13] <jdong> syke: it's not going to happen in Feisty sadly....
[07:14] <jdong> syke: 0.13 requires newer stetic and friends, and I've been watching it go into Debian....
[07:14] <jdong> syke: 0.12 in the repos don't crash for me, and I use it regularly...
[07:14] <jdong> if you want 0.13 packages I think I have some
[07:14] <syke> jdong: if they're on a public URL, that would be nice
[07:15] <syke> I'm working on a book, pragmatic unit testing in C#, and I'm trying to make sure the code/examples in it works in all these environments
[07:15] <syke> we use a couple of screenshots of nunit-gui running in KUbuntu
[07:15] <jdong> syke: uploading, http://web.mit.edu/jdong/www/md/ 
[07:15] <syke> we mention monodevelop 0.13 because it adds an integrated unit test runner
[07:15] <gnomefreak> why not just doa  simple build to make life easy if the book isnt ubuntu specific
[07:15] <jdong> done.
[07:16] <jdong> gnomefreak: heh it's not as trivial a build as we'd like it to be
[07:16] <syke> yea, it's a big pain in the balls to build :(
[07:16] <syke> so many dependencies
[07:16] <jdong> syke: yeah but the debs I posted I've been using since 0.13.1's release... they're based off Ubuntu debs
[07:16] <jdong> and should be pretty safe to use
[07:16] <jdong> but the usual 3rd party unsupported package warning goes along with them ;-)
[07:16] <syke> great, that's better than nothing :)
[07:17] <syke> just trying to make sure the readers of the book can have a smooth experience with Linux :)
[07:17] <jdong> 0.13 also adds better code completion too
[07:17] <jdong> and partial class support
[07:17] <jdong> for the UI editor that is
[07:17] <syke> and, like I say, it doesn't crash nearly as much for me
[07:17] <jdong> well I'll attempt to backport it to Feisty once Gushy Giblets or whatever opens
[07:18] <syke> haw
[07:18] <syke> :)
[07:18] <jdong> :)
[07:18] <syke> the other package I had a question about was NUnit itself; I suppose there's no chance of updating that to 2.4, is there?
[07:18] <jdong> haven't looked into that
[07:19] <jdong> but Feisty, it's too late to update anything at this time
[07:19] <syke> I also noticed that even when the current NUnit package is installed, most configure scripts look for a mono-nunit.pc, and the current NUnit pkg only installs an nunit.pc
[07:20] <syke> ok, that's too bad for monodevelop :/ I'll add a general note about making sure to have the latest versions or downlaod them separately
[07:20] <jdong> slomo is the monodevelop guy around here; he will be thrilled to dicuss this with you :D
[07:20] <jdong> lol
[07:20] <syke> must be a private joke I'm missing out on :)
[07:20] <DktrKranz> could you clarify me about packages inserted into REJECTED queue?
[07:21] <syke> need to reboot to try this updated kernel and kdelibs, I'm having some issues with knetworkmanager that it will hopefully fix
[07:21] <syke> jdong: thanks for the info! :)
[07:23] <DktrKranz> recently \sh uploaded for me tutos2 package
[07:24] <DktrKranz> but I noticed it was inserted into REJECTED queue: https://launchpad.net/ubuntu/feisty/+queue?queue_state=4&queue_text=tutos2
[07:24] <DktrKranz> is there something to do in these cases?
[07:30] <ScottK> You need to ask one of the archive admins or maybe ask the MOTU that approved it to ask.
[07:30] <ScottK> When that happened to me, Tollef e-mailed my why. 
[07:31] <ScottK> They're possibly busy at the moment, so I'd ask the MOTU that uploaded it to ask.
[07:31] <DktrKranz> will do, thanks.
[07:32] <penguin42> would it be possible to get gnucash (in universe) updated to the latest release - is the right thing to put a bug in for that?
[07:35] <ScottK> penguin42: Not now.
[07:35] <ScottK> Not for Feisty
[07:35] <penguin42> sure I realise that's too late
[07:36] <penguin42> but just to get it on the radar that it needs getting done
[07:36] <ScottK> Once the repositories open for the next release, it should just happen.
[07:36] <penguin42> oh ok - the version in there is about 6 months old
[07:37] <ScottK> Actually, there is an Ubuntu specific variant, see https://launchpad.net/ubuntu/+source/gnucash so it will have to be merged.  It won't be automatic.
[07:39] <ScottK> penguin42: Maybe you could work on it in a few weeks? https://wiki.ubuntu.com/MOTU/Merging we can always use more help.
[07:39] <penguin42> ScottK: I wouldn't mind doing - but I've got about 3 or 4 geeky other projects I havn't got around to either :-(
[07:40] <penguin42> what do you mean by 'ubuntu specific varient' - I suspect gnucash doesn't actually have stuff for debs in it at all
[07:40] <ScottK> Right, but the Ubuntu version is modified from what we get from Debian.
[07:40] <penguin42> ah ok
[07:40] <ScottK> Put it on your TODO for about a month from now.
[07:42] <penguin42> Ah Debian have the latest version packaged - I'll try building it from their package and see how it goes
[07:42] <penguin42> ScottK: Is it easy to see why we have an ubuntu specific version?
[07:43] <ScottK> penguin42: Yes.  Download the source package (apt-get source gnucash) and look in debian/changelog
[07:43] <ScottK> It should explain the differences.
[07:44] <penguin42> actually they've got the latest in etch
[07:45] <ScottK> One thing to look at is is the Ubuntu version still required.  If Debian has made changes that make the Ubuntu specific stuff OBE, then it can be synched.
[07:45] <ScottK> Merges have to be done manually, so they don't always get done regularly.  Remember that MOTU is all volunteer.
[07:45] <penguin42> nod
[07:46] <ScottK> If you have the technical ability (and it sounds like you do) there is one easy way to make sure the Ubuntu gnucash stays up to date...
[07:46] <penguin42> Hmm according to the changelog there is a tiny build dependency difference (libgoffice-0-dev instead of libgoffice-1-dev)
[07:48] <ScottK> Look at sid though, not etch.
[07:49] <ScottK> By the time you are ready to merge it, sid will probably have changed.
[07:49] <penguin42> ScottK: What I don't have is the knowledge of the ways of the packaging rules and how to package stuff properly
[07:49] <ScottK> People here will help you learn that.
[07:49] <penguin42> hmph - let me try the obvious thing first, I'll just have a quick look if the debian package builds and runs ok
[07:50] <ScottK> That's a good one.
[07:51] <ScottK> http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html is a good place to start.
[07:51] <ScottK> Of course you could make the build-dep change and then it would probably build.  Look in debian/control in the source package.
[07:52] <penguin42> so do you guys have any tools that keep an eye on debian version updates?
[07:53] <mr_pouit> penguin42: you can use this page: http://tiber.tauware.de/~laserjock/motutodo/universe.html
[07:54] <ScottK> There is also http://merges.ubuntu.com/ and http://merges.ubuntu.com/universe.html
[07:54] <imbrandon> penguin42, if your wanting to make a custom list look into mdt
[07:55] <imbrandon> ( mdt == multi distro tools ) made just for that
[07:55] <penguin42> hmm it seems you and debian have a gentle disagreement of the naming of libgoffice-?-dev
[07:57] <ScottK> penguin42: Who uses which?
[07:57] <ScottK> It is not rare for Ubuntu to jump to a newer infrastructure sooner.
[07:58] <ScottK> For example, Python 2.5 is the default Python in Feisty and it's not yet supported in Sid.
[07:58] <penguin42> well they have a libgoffice-1-dev (0.2.1-4) and we have a libgoffice-0-dev (0.3.7-0ubuntu1)
[07:58] <ScottK> Ah.  I've no idea why.
[08:00] <penguin42> that one is a little nuts - the build dependency naming is the only thing that is stopping it being up to date
[08:00] <penguin42> hmm is there anything to tell apt to install all the packages this dsc it needs as build dependencies
[08:01] <imbrandon> sudo apt-get build-dep <package> ?
[08:02] <penguin42> hmm it won't actually take it from the dsc - still it will get me what I need
[08:02] <imbrandon> pbuilder-satisfydepends will get from the dsc
[08:02] <imbrandon> depends on how you want to do it
[08:14] <penguin42> ScottK: OK, now I'm confused - off the merges page of that package list page is one for gnucash and it shows a merge for the latest version
[08:15] <ScottK> Yes, but no one ever got around to submitting it.
[08:15] <ScottK> Those are drafts that someone has to actually work through.
[08:15] <penguin42> ah - is it automatic?
[08:16] <ScottK> Getting to the draft is automatic.
[08:16] <ScottK> From there a live volunteer has to look it over and verify it.
[08:16] <ScottK> It gets particularly interesting when Debian and Ubuntu has specific changes.
[08:16] <ScottK> err uh conflicting changes
[08:17] <penguin42> ah food calls - the build should be finished by the time I've eaten
[08:38] <geser> Hi bddebian
[08:39] <ScottK> Hello bddebian (you youngster).
[08:39] <bddebian> Heya gang
[08:39] <bddebian> Hi geser, ScottK ( :-) )
[09:07] <penguin42> well the gnucash seems to run fine from the debian 2.0.5 with teh build dependency tweaked
[09:13] <ScottK> penguin42: Then once the repositories open for graceful gibbon, you ought to file a merge request.
[09:14] <penguin42> ScottK: How does one file a merge request?
[09:15] <ScottK> penguin42: https://wiki.ubuntu.com/MOTU/Merging
[09:16] <ScottK> penguin42: Note that this is a relatively easy thing to do that MOTU never has enough people to keep up, so it's a REALLY great way to contribute.
[09:19] <penguin42> so I can see the bit about submitting a bug on it - is that it or is there something else?
[09:22] <ScottK> No.  That's pretty much it.  You make sure you got the package right (check the changes, build it, test it a bit), make a debdiff, and file the merge bug with the dediff attached.  A MOTU will review/approve.  Once it's approved, you just mark it fix released after the update builds in the repositories.
[09:23] <ScottK> Given what you've just done, you know most everything you need to know to start doing simple merges for gutsy.
[09:23] <ScottK> In cases where we have a fix that Debian doesn't it's good to file a bug in the Debian BTS so they can get it.  The Ubuntu goal is to minimize diff with Debian.
[09:24] <penguin42> nod - are the debian guys pulling stuff back into their worlds as well?
[09:24] <ScottK> They don't usually come here and look.  Some will take Ubuntu patches, some won't if they are BTS.
[09:25] <penguin42> if there is no diff needed - i.e. the automerge has done the right thing do I just point the bug at that?   Is there anything that can go away and check it builds on all the arches?
[09:25] <ScottK> https://wiki.ubuntu.com/ContributingToDebian/
[09:25] <ScottK> If there is no diff, it's a sync not a merge.
[09:25] <ScottK> Those are automatic up to a point and then they have to be requested.
[09:26] <penguin42> there is a diff - but the automerge thing seems to have taken the diff from last time
[09:26] <geser> penguin42: MoM doesn't add a correct changelog entry (listing the remaining changes) so need to edit it and then debdiff
[09:26] <ScottK> Right.  MoM guesses and then you have to make sure.
[09:26] <ScottK> See Debian import freeze on the schedule: https://wiki.ubuntu.com/GutsyReleaseSchedule
[09:27] <penguin42> geser: Ah OK - pity really
[09:27] <bluefoxicy> I blame ISV and compatibility
[09:27] <ScottK> bluefoxicy: If it gets to old and Debian isn't keeping up, you can package the update and submit it to REVU.
[09:28] <bluefoxicy> ScottK:  Yeah.  I'm more concerned that things like autopackage et al are hackey.. actually, autopackage works pretty well o.o  hmm
[09:28] <ScottK> penguin42: Personally, I'm impressed how well the MoM does, but would be petrified of taking the human out of the loop entirely.
[09:28] <geser> penguin42: sometimes it happens that a fix is included a second time because the patch file got an other name or Debian included a patch at an other line in a file
[09:28] <ScottK> Also now that Etch is released, more emphasis will go into Sid.
[09:29] <ScottK> bluefoxicy: Click N Run is supposed to be coming to Ubuntu 'real soon now".
[09:29] <penguin42> ScottK: Nod, if you take the human out of the loop the systems might start writing their own code
[09:29] <ScottK> And do it badly.
[09:29] <bluefoxicy> ScottK:  that's a centralized database, like Apt2 or something.
[09:29] <penguin42> it looks like the gnucash update in debian missed the freeze for feisty by about 3 days - bah!
[09:30] <ScottK> Gnucash would have had to be merged in any case so wouldn't have been automatic.
[09:30] <bluefoxicy> ScottK:  I want something where I can grab what I want from wherever, like Autopackage; but I'm not wholly convinced that Linux can handle backwards compatibility (try running Citrix once, if you install libxaw6 it doesn't work because libxaw6 doesn't have a symbol it needs)
[09:31] <penguin42> so if I come back this time next week and file the bug it should be OK?
[09:32] <ScottK> No.  Wait until the gutsy repositories open.
[09:32] <penguin42> when is that due?
[09:32] <ScottK> I thin it's roughly April 29.
[09:32] <ScottK> thin/think
[09:32] <ScottK> Then if you want, after it's in gutsy you can file for a backport into Feisty.
[09:33] <penguin42> but then do I have to go and gab gutsy tools and stuff?
[09:33] <ScottK> Not immediately.
[09:33] <penguin42> ok
[09:33] <bluefoxicy> ScottK:  CITRIX needs libxaw6 (not 5, not 7); but xaw6 doesn't have all the symbols (because the idiot programmers don't understand you're supposed to upgrade the ELF major version when you break the ABI); this seems to be a pretty chronic problem, programs just eventually don't work any more because the libraries are different somewhere along the line.  Most libs seem to get ELF versioning right these days (GTK+ is a model e
[09:33] <bluefoxicy> xample) but meh.
[09:33] <bluefoxicy> I suspect that autopackagers like autopackage will always hit that hurdle
[09:33] <penguin42> has their been any thought ever to building stuff in later distros with loose enough dependencies to still work on older ones?
[09:34] <penguin42> you'd think a lot of packages would work on multiple versions 
[09:34] <ScottK> Yes, but the binaries need to be built with the correct environment for that version.
[09:34] <penguin42> do thehy?
[09:35] <ScottK> So you don't upversion dependencies unless you need to and then you can use the backports system for stuff that qualifies.
[09:35] <ScottK> penguin42: Yes.  Usually it's OK, but sometimes you get burned.
[09:35] <ScottK> For your own use, it's probably OK, but for the distro as a whole, not.
[09:35] <penguin42> ScottK: I was thinking just applying it to packages that are OK
[09:35] <ScottK> There's no way to know.
[09:36] <ScottK> Keep the source as common as you can and then build in the correct environment is the only way to do it.
[09:36] <bluefoxicy> hmm
[09:36] <penguin42> going in the forward direction should work shouldn't it - I mean building newer packages on feisty and then using those also in feisty+1 say
[09:37] <ScottK> It's discussed here: https://wiki.ubuntu.com/MarkShuttleworth
[09:37] <bluefoxicy> something that will build a thin compatibility layer around new versions of libraries
[09:37] <ScottK> penguin42: Depends on if some library had removed some aspect of an API.
[09:37] <bluefoxicy> nah that would be a pain
[09:39] <penguin42> ScottK: But then they should bump their major version or disembowel their authors
[09:39] <ScottK> Yep.  That's the theory.
[09:40] <vil> imbrandon, ping
[09:40] <ScottK> Work in the process and get your stuff into the Ubuntu repositories and then it's Canonical's problem.  That keeps YOUR load down.
[09:40] <penguin42> so what builds the universe - is their a build farm that checks it builds on SPARC say?
[09:41] <penguin42> nod - just trying to understand how the universe goes together
[09:41] <ScottK> See https://launchpad.net/ubuntu/+source/klamav/0.41-0ubuntu1 - It shows you which archs Ubuntu builds.
[09:41] <ScottK> As an example.
[09:42] <ScottK> Universe and Main use the same toolset for this.
[09:44] <penguin42> hmm nice build system
[09:44] <penguin42> right, I'll try and remember to keep an eye on it and come back in a couple of weeks and file the stuff on gnucash
[09:44] <penguin42> thanks
[10:03] <danohuiginn> apt-get build-dep is telling me "build dependencies could not be satisfied". How can I get it to tell me *which* build-deps are the problem?
[10:04] <ScottK> danohuiginn: The error message should tell you.  Read closely.
[10:07] <danohuiginn> ScottK: it doesn't seem to. http://paste.ubuntu-nl.org/15654/
[10:07] <ScottK> looks
[10:08] <ScottK> Ah.  It's pbuilder that will tell you which.  Try and build the package and dpkg-buildpackage will bail out and tell you which.
[10:08] <ScottK> Sorry about that.
[10:08] <danohuiginn> ok, thanks
[10:18] <imbrandon> vil, pong
[10:18] <geser> danohuiginn: I can't reproduce it here
[10:18] <vil> imbrandon, again question regrarding ubuntuwire
[10:19] <imbrandon> sure, shoot
[10:19] <vil> there is supposed to be a problem with eclipse on sparc64, however, I don't have a way to test it
[10:20] <vil> imbrandon, do you thing that you could install the latest eclipse on sparky?
[10:20] <imbrandon> sparky is spark64 kernel iirc 
[10:20] <imbrandon> i would much rather you do it in a chroot 
[10:20] <imbrandon> than install it on the main box
[10:21] <vil> imbrandon, that's fine
[10:21] <imbrandon> vil, e.g. pbuilder-feisty login
[10:21] <imbrandon> then install from there
[10:21] <danohuiginn> geser: I got it sorted, thanks. It was tangled up in alternatives
[10:21] <vil> imbrandon, I will look at what is pbuilder login good for
[10:22] <imbrandon> vil, "pbuilder-feisty login" will give you a clean chroot that you can install it in, then when you "exit" it cleans it all up
[10:22] <imbrandon> and sets it back to default
[10:22] <vil> imbrandon, thanks again for your kind help
[10:23] <imbrandon> np
[11:28] <TheMuso> ScottK: You're welcome.
[11:32] <grayman> is there a problem with xkbd in Feisty?
[11:35] <grayman> xkb
[11:37] <marseillai_> hi
[11:38] <marseillai_> does anyone know where I can find a complete howto to create package from scratch using cdbs in the "ubuntu" way?
[11:39] <macd> marseillai_, http://doc.gwos.org/index.php/Deb_Guide isnt a bad start
[11:40] <jekil> marseillai_: is hard to find good cdbs documentation
[11:40] <macd> nvm, I didnt read what you said.
[11:40] <marseillai_> jekil: arf
[11:41] <jussi01> marseillai_, http://doc.ubuntu.com/ubuntu/packagingguide/C/basic-cdbs.html
[11:41] <damko> marseillai_: I made my first package 1 day ago and I found very useful yada to understand the mechanism to create a package. may be it's usefull also for u
[11:42] <marseillai_> jekil: assuming i want to make a clean package of an application (i've allready done one this afternoon : i've patch kopete, make debdiff and a deb) but from scratch, can i find some help here to teach me how to do with cdbs/pbuilder and else ???
[11:42] <jussi01> marseillai_, see the link i gave you
[11:42] <marseillai_> jussi01: it's pretty.... empty .....
[11:42] <jekil> marseillai_: read links above and google
[11:43] <jussi01> http://doc.ubuntu.com/ubuntu/packagingguide/C/basic-scratch.html
[11:43] <jussi01> also that
[11:43] <mr_pouit> marseillai_: for cdbs, you can also read https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml
[11:43] <marseillai_> mr_pouit: dja lu, un peu perdu
[11:43] <jussi01> marseillai_, on that first link was a link to more stuff
[11:47] <marseillai_> macd: does this doc is about cdbs or debhelper : http://doc.gwos.org/index.php/Deb_Guide ? or perhaps debhelper and cdbs are the same things ?
[11:48] <jekil> marseillai_: are 2 things...
[11:49] <jekil> i think that you must understend well this before use it
[11:52] <marseillai_> thanks jekil macd and jussi01