[00:05] <NCommander> finally got mono installed
[00:07] <NCommander> Building evo-sharp
[00:09] <NCommander> WOOT
[00:09] <NCommander> Success!
[00:14] <NCommander> https://bugs.edge.launchpad.net/ubuntu/+source/mono/+bug/247782 - FATALITY!
[00:15] <NCommander> should I change it from In Progress to Fix COmmited?
[00:16] <directhex> Confirmed, IMHO
[00:16] <NCommander> directhex, the debdiff is there if you wish to add it to your backports repo ;-)
[00:17] <NCommander> ScottK, ping
[00:21] <emgent> hello there
[00:24] <tacone> how to know which version format use for a watch file ?
[00:35] <tacone> in the changelog shall I put my email or motu's ?
[00:37] <NCommander> tacone, yours
[00:38] <tacone> ok
[00:38] <emgent> tacone: use export. and than dch
[00:38] <emgent> export DEBFULLNAME='Emanuele Gentili'
[00:38] <emgent> export DEBEMAIL='emgent@ubuntu.com'
[00:39] <tacone> emgent: we set that together. I was just unsure.
[00:39] <NCommander> I gtg
[00:39] <tacone> thanks
[00:39] <emgent> np
[01:25] <NCommander> SO its the CPU fan
[01:25] <NCommander> damn it
[01:26] <NCommander> ScottK, ping
[01:31] <emgent> lol
[01:31] <NCommander> FIgures the 14 day return policy is one day over
[01:31] <NCommander> At least I kept an image of the Vista this thing came with so I can send it Sony at some point
[01:33] <NCommander> emgent, BTW, I'm curious, whatever happened to Grumpy Groundhog, it seems to have never properly materialized
[01:47] <NCommander> w00t, I just figured out what kernel driver was causing suspend to not work
[01:50] <CyberCod> NCommander, you ever get that wishlist bug posted?  I'm curious what it looks like
[01:51] <NCommander> Whoops
[01:51] <NCommander> I knew I forgot to do something
[02:19] <bahadunn> how is syncing from debian to ubuntu usually done?
[02:20] <RAOF> bahadunn: By someone running the 'please sync this package from $REPOSITORY' script.  Someone with datacenter access, I think.
[02:20] <bahadunn> oh okay
[02:20] <bahadunn> so it is only something that core devs do?
[02:21] <RAOF> Archive admins.
[02:21] <bahadunn> I see
[02:21] <bahadunn> thanks for the info
[02:21] <RAOF> But anyone can file a sync bug, if appropriate.
[02:21] <RAOF> It's just that only archive admins can act on it.
[02:21] <bahadunn> okay
[02:22] <RAOF> Also, if you wouldn't have permission to upload the package, you'll need to get an appropriate sponsor - subscribe whichever of "ubuntu-universe-sponsors" or "ubuntu-main-sponsors" is appropriate.
[02:23] <RAOF> You probably want to look at https://wiki.ubuntu.com/UbuntuDevelopment/Merging if you haven't already.
[02:23] <bahadunn> I have read so many docs in the last few days I am not sure if I read that one or not so I will check it
[03:01] <ScottK> NCommander: Pong.
[03:03] <NCommander> sorry
[03:03] <NCommander> ScottK, can you sponsor mono for me?
[03:04]  * NCommander is having perpahs the weird sleep suspend issue
[03:04] <ScottK> NCommander: I'm seriously not touching Mono.  If it broked, people'd think I did it on purpose.  ubuntu-main-sponsors usually has a pretty short wait.
[03:04] <ScottK> broked/broke
[03:05] <NCommander> It's already broke ;-)
[03:05] <NCommander> but I completely understand
[03:05] <ScottK> NCommander: You're doing good work.  Don't let some waiting get you down.  Just subscribe u-m-s and move on....
[03:05] <NCommander> I did
[03:05] <ScottK> OK.  Great.
[03:05] <NCommander> Right now, I'm going to fight suspend on my laptop
[03:05] <NCommander> I got it working
[03:05] <NCommander> But now the moment the wifi card connects to a network, I loose the keyboard
[03:06] <NCommander> Until I disconnect the wifi card with the mouse o_o;
[03:06] <ScottK> Kewl.
[03:06] <NCommander> I can't decide if this is progress or not
[03:11] <NCommander> ScottK, so  on average its 1-2 months before I should even consider applying for contributing developer (which, if the wiki is to believed, required to do syncs/merges)
[03:12] <ScottK> NCommander: Contributing developer is a community thing, not really a technical thing.  Anyone can file bugs with debdiffs for merges or sync requests and ask to have them sponsored.
[03:12] <ScottK> Being a contributing developer doesn't affect that.
[03:12] <NCommander> ah
[03:12] <NCommander> The wiki lists that under contrib devel
[03:12] <ScottK> It's the same until you're MOTU and can upload the merge/ask for the sync directly.
[03:12] <NCommander> I did know I could get things sponosered
[03:13] <ScottK> Contributors still need sponsorship.
[03:13] <ScottK> I suspect that was an attempt to stear beginners away from sync/merge as knowing what bits of diff between Ubuntu and Debian is not, IMO, a beginner task.
[03:13] <NCommander> I tried to do some merges
[03:14] <NCommander> But they were all assigned to developers already
[03:14] <ScottK> NCommander: Even though you're new here, clearly you aren't a beginner.
[03:14] <coppro> speaking of which, is anyone here up for REVUing a package?
[03:14] <NCommander> ScottK, one of the perks on working on Debian ;-)
[03:14] <ScottK> Yes.
[03:14] <ScottK> NCommander: Do the newt merge and I'll sponsor it.
[03:14] <coppro> http://revu.ubuntuwire.com/details.py?package=libmk4
[03:15] <NCommander> Hold on
[03:15] <NCommander> The ubuntu machine currently having a siezure
[03:15] <NCommander> I think I got modprobe stuck in an infinite lop
[03:15] <NCommander> *loop
[03:16] <NCommander> Well, now I have working suspend, wifi, and keyboard!
[03:16] <NCommander> I can work on packages!
[03:17] <coppro> you have working suspend?
[03:17] <coppro> lucky
[03:17] <NCommander> Just got it working
[03:17] <ScottK> Mine works too.
[03:17] <NCommander> Sony SZ CGN-660N
[03:17] <NCommander> *VGN
[03:18] <NCommander> coppro, does your laptop use an intel wireless card?
[03:18] <coppro> dunno, I don't have it right now.
[03:18] <ScottK> Mine does.
[03:18] <coppro> probably
[03:18] <NCommander> coppro, does it fail to go to sleep
[03:18] <NCommander> (like does it get stuck at a flashing prompt?)
[03:19] <coppro> hibernation usually is the problem
[03:19] <coppro> standby usually works
[03:19] <NCommander> Hibernation is a freaking pain to get working
[03:19] <NCommander> But it might now work on this machine
[03:20] <NCommander> ScottK, do you mean libnewt?
[03:20] <coppro> hibernation seems to be jargon for "hold down power button for <manufacturer-defined-constant> seconds"
[03:20] <ScottK> NCommander: Newt.  http://merges.ubuntu.com/n/newt/REPORT
[03:24] <NCommander> ok
[03:25] <NCommander> It merged cleanly, so just need to see if the ubuntu packages are still needed, and if it builds cleanly
[03:28] <NCommander> ScottK, is there anything beyond that I need to do; I listed the remaining changes int he changelog, and I'm making sure it builds
[03:29] <ScottK> Make sure the changes are sensible and all documented.  Then file a merge bug (remember to close it in debian/changelog) and attach a debdiff from the current Debian release to the bug.
[03:29] <NCommander> which changes, the ones from debian, or the ones from ubuntu?
[03:29] <ScottK> Given Joey Hess did the NMU, I'm going to guess it's probably a good one.
[03:30] <NCommander> It's pretty clear on what he added as a patch
[03:30] <NCommander> My changelog simply lists the ubuntu specific changes which is what its suspose to be, right?
[03:31] <ScottK> Yes.  If you use the grab-merge script it'll give you a new debian/changelog entry in the right format.
[03:31] <NCommander> Yup
[03:31] <NCommander> THat's extactly what I did
[03:31] <ScottK> Don't forget you want the entire Ubuntu change history in debian/changelog, not just add one entry on top of the Debian one.
[03:31] <ScottK> Should be good then.
[03:33] <NCommander> ScottK, http://paste.ubuntu.com/27891/ - that look right? THe debian change is right below it
[03:33] <ScottK> You'll want to close the merge bug you haven't filed yet, but other than that, yes.
[03:33] <NCommander> Right, I can't close I bug I haven't filed yet ;-)
[03:38] <NCommander> ScottK, well, this is a unique bug
[03:38] <NCommander> firefox seems to freeze up when I try to attach the patch
[03:40] <ScottK> NCommander: Use a proper web browser like Konqueror then.
[03:40] <NCommander> ouch
[03:40]  * NCommander installs opera
[03:41] <ScottK> NCommander: You know Canonical has packages for Opera in their 'partner' repo, right?
[03:41] <NCommander> Now I do ;-)
[03:41] <NCommander> It's in non-free on Debian
[03:41] <ScottK> If you're going to use it you might as well use the one that's built for Ubuntu.
[03:41] <NCommander> WHo's bright idea was it to have a beta go for a LTS
[03:41] <ScottK> NCommander: Really had no choice.
[03:42] <ScottK> Upstream support for 2.0 dies out in a year.
[03:42] <NCommander> I'm suprised canonical simply doesn't make an exception to backport firefox
[03:42] <ScottK> So it was either go with the beta for release and try to get as many plugins updated as possible or suck up the pain later.
[03:42] <ScottK> If it was just Firefox, they probably would have, but it's got a whole ecosystem of packages around it.
[03:43] <NCommander> No, I realize that
[03:43] <NCommander> But B5 -> 3.0 should be straightforward
[03:43] <ScottK> They did or will shortly update it.
[03:43] <ScottK> I think it's updated already.
[03:43] <NCommander> mcasadevall@blacksteel:~/.mozilla$ firefox --version
[03:43] <NCommander> Mozilla Firefox 3.0, Copyright (c) 1998 - 2008 mozilla.org
[03:43] <NCommander> I dont' remember seeing the update
[03:44] <NCommander> THis really has to be a first
[03:44] <NCommander> firefox is broken
[03:44] <ScottK> It's the final in the repos.
[03:44] <NCommander> brb
[03:45] <NCommander> or ... not
[03:45] <NCommander> X11 seems to be stuck
[03:45]  * ScottK hasn't been much of a fan since 1.5 released.
[03:50] <NCommanders> ScottK, back
[03:50] <NCommanders> https://bugs.edge.launchpad.net/ubuntu/+source/newt/+bug/249290
[03:51] <NCommanders> Got anymore for me?
[03:51]  * ScottK looks
[03:51] <ScottK> How about libnet-dns-perl
[03:52] <NCommanders> just tell me first to make sure I did the last one right ;-)
[03:54] <ScottK> Sure.
[03:54] <ScottK> NCommanders: Did you look at the open newt bugs and see if you could fix any of them?
[03:55] <NCommanders> No, I didn't >.<;
[03:55] <NCommanders> Probably should have
[03:55] <NCommanders> libnet-dns-perl should simply be synced
[03:55] <NCommanders> Upstream merged our patches
[03:56] <ScottK> NCommanders: Agreed.  You want to practice with requestsnyc -s?
[03:56] <NCommanders> I already had started that ;-)
[03:57] <ScottK> This is, BTW, a happy ending of a story that started with an Ubuntu archive-admin noticing the debian/copyright problem when reviewing for inclusion in Main and me filing a bug with a patch in Debian.
[03:57] <NCommanders> d'oh
[03:57] <NCommanders> The environment variable DEBEMAIL needs to be set to make use of this script.
[03:57] <NCommanders> Something went wrong. No sync request filed.
[03:58] <ScottK> It uses DEBEMAIL to figure out what email address to use for GPG signing.
[03:58] <NCommanders> oh
[03:58] <NCommanders> I shouldn't be running that in the chroot then
[03:59] <ScottK> You probably have to configure something to use an MTA you have relay access for.
[03:59] <ScottK> No.
[03:59] <NCommanders> what package is requestsync in?
[03:59] <ScottK> Email bug filing in LP needs to be GPG signed.
[03:59] <ScottK> ubuntu-dev-tools
[03:59]  * NCommanders figures now is a good time to get his MTA to smarthost to gmail
[04:01] <Hobbsee> smarthost?
[04:02] <ScottK> Use Gmail as an outbound relay for if you don't have a static IP and don't want your mail rejected.
[04:03] <NCommanders> ScottK, yeah, that's how I did it in the past
[04:03] <NCommanders> I just been lazy and hadn't set it up
[04:03] <NCommanders> and now I have working outgoing email ;-)
[04:04] <NCommanders> ok, lets try this again
[04:05] <ScottK> NCommanders: Your debdiff looks good.
[04:05] <ScottK> Assuming my test build works, I'll upload it.
[04:05] <NCommanders> requestsync ran
[04:05] <ScottK> Note: I test build everything - don't take it personally.
[04:05] <NCommanders> I do the same when I did checking of hurd patches
[04:05] <NCommanders> So its not taken personally
[04:06] <NCommanders> ;-)
[04:06] <NCommanders> ScottK, why do I get the weird feeling you were testing me though (since you already knew that this merge could be removed and replaced with a sync)
[04:07] <ScottK> NCommanders: Probably because I was testing you.
[04:07] <NCommanders> oh good, its not me
[04:07] <NCommanders> I don't think my firefox failure was your fault though
[04:07] <NCommanders> It's just Ubuntu getting back at me for actually fixing sleep suspend, then running the machine through 20 said cycles
[04:08] <NCommanders> and when did I become plural O_O;
[04:08] <ScottK> Strictly speaking it's not even Ubuntu's fault.  Due to Mozilla corp Trademark policy, we need permission to patch stuff.
[04:08] <NCommander> ScottK, I'm well aware of Iceweasel/Icecat/etc. ;-)
[04:09] <ScottK> Just making sure the finger gets pointed in the right direction.
[04:09] <Ademan> stupid quick question, how come e17 isn't in the repos?
[04:09] <ScottK> Also that wasn't just for your benifit.
[04:09] <NCommander> The only thing I think that can be changed with firefox pretty much out of the box is some of the defaults, and some of the default SSL certs, otherwise you need explicate permission to use the firefox logo, and use --enable-branding ;-)
[04:09] <ScottK> Ademan: What is e17?
[04:09] <ScottK> Yes and yet somehow they want to be considered Free software.
[04:10] <NCommander> SOmeone should sync iceweasel
[04:10] <Ademan> ScottK: enlightenment window manager, their newest version, i believe it's being developed in parallel with e16 (which *is* in the repos)
[04:10]  * NCommander dives for cover
[04:10] <RAOF> Ademan: Is that actually released yet?  It was in a semi-permanent svn checkout status last time I checked (which was a while ago)
[04:11] <Ademan> RAOF: oh really? that may be, i just know it's been around *forever* and i kinda just assumed there was a release
[04:11] <NCommander> I'm actually suprised iceweasel isn't synced; and kept up to date for FF3; it could be the testing ground for patches until they can be cleared through Mozilla Corperation
[04:11] <ScottK> NCommander: Thank you for your contribution to Ubuntu.  Newt uploaded.
[04:11] <Ademan> RAOF: i only bothered asking because i got brave and tried it out through elbuntu's repositories, and it seemed quite stable, and really nice...
[04:11]  * NCommander always finds that statement funny for some reason
[04:12] <RAOF> Ademan: Nope.  svn snapshots of e17 have been around *forever*.  This may give some indication of the release strategy.
[04:12] <NCommander> how long does it take for an email based bug report to appear on launchpad?
[04:14] <vorian> 5 min or so
[04:14]  * NCommander grumbles
[04:15] <NCommander> That's the same reason I detest BTS
[04:15] <NCommander> https://bugs.edge.launchpad.net/ubuntu/+source/libnet-dns-perl/+bug/249300
[04:15]  * ScottK goes afk for a while.  I'll ack it tomorrow if not tonight.  Thanks.
[04:16]  * NCommander looks at vorian 
[04:16] <vorian> NCommander: it's in main, sorry :(
[04:17] <vorian> you might want to subscribe ubuntu-main-sponsors
[04:17] <NCommander> it did automatically ;-)
[04:17] <NCommander> I keep thinking your a core-dev for some reason
[04:17] <vorian> are you sure it didn't subscribe ubuntu-archive?
[04:17] <NCommander> Probably because you remember me of the vorian from Debian
[04:17] <NCommander> "Ubuntu Sponsors for main"
[04:18] <vorian> werd
[04:24]  * NCommander keeps wondering who else he knows called vorian 
[04:24] <NCommander> I know the DD vorian
[04:24] <NCommander> but I have that weird feeling I know more then one (and since they all wear encounter suits, you can't tell if its the same one ;-))
[04:25] <vorian> :)
[04:26] <NCommander> are you Kosh?
[04:26] <vorian> are you sure it's not vorlon?
[04:26] <NCommander> hrm
[04:26] <NCommander> maybe
[04:26] <NCommander> Perpahs I'm not caffinated enough
[04:26] <NCommander> Yes ... yes ... oh look, ... something exciting!
[04:26]  * NCommander runs away while vorian is distracted
[04:27] <vorian> I would never accuse you of not having enough caffine
[04:28]  * NCommander looks at his desk
[04:28] <NCommander> five cans and two bottles
[04:28] <NCommander> Nope, not enough
[04:45] <ScottK> NCommander: Ack'ed  Thanks.
[04:45] <NCommander> np
[04:45] <NCommander> I'm working right now on packaging adeona
[04:45] <NCommander> But I hit a GPL linking snag, so I'm hoping upstream can resolve
[04:45] <NCommander> I'd also like to package codeblocks, but Debian is allergic to wxWidgets 2.8
[04:46] <NCommander> so I never took a stab at it
[04:46] <coppro> http://revu.ubuntuwire.com/details.py?package=libmk4 <- please REVU
[04:46] <NCommander> Ubuntu has wxWidgets 2.8, but we need wxGTK, and I'm not sure if I should package it, or ask the wx guys too
[04:46] <NCommander> I'm no MOTU, but I'll look it over
[04:46] <coppro> thanks
[04:47] <ScottK> Actually, I think 2.8 is in Sid now too.
[04:47] <NCommander> Do you need the .dirs? dh_install should automatically create any /usr/* dir needed. the dirs file is only really needed if its a non-standard place last time I looked
[04:47] <NCommander> (that was for coppro)
[04:48] <coppro> well, the script put it there
[04:48] <coppro> so I just modified it
[04:48] <coppro> I probably don't need it
[04:49] <NCommander> I recommend replacing the install line with a dh_install based solution. It's not strictly necessary, but it keeps the rules file mostly clutter free
[04:49] <ScottK> It's a good suggestion.
[04:49] <NCommander> Changelog should close the needs-packaging bug
[04:49] <NCommander> (here's irony, me saying that)
[04:50] <coppro> think I forgot to make one lol
[04:50] <NCommander> Standards-Version should be 3.8.0 (I guess revu must be using lintian from hardy)
[04:51] <NCommander> your copyright file looks good
[04:51] <coppro> (I am using lintian from hardy)
[04:51] <coppro> (which explains the Standards-Version)
[04:51] <NCommander> Use intrepid's
[04:52] <NCommander> just a handy tip
[04:52] <coppro> should I be making a chroot at this point?
[04:52] <NCommander> Unless your doing a backport, I recommend doing all packaging work in a intrepid chroot
[04:52] <coppro> can someone please walk me through this? I
[04:52] <coppro> *I have gotten lost before
[04:52] <NCommander> For instance, when I (re)packaged , it worked fine on hardy, and FTBFS on intrepid ;-)
[04:53] <NCommander> Ok, ever work with chroots before?
[04:53] <coppro> I know how they work and how to set one up with debbootstrap, but apparently there's some pbuilder stuff or something
[04:53] <NCommander> oh, your pbuilder chroot is not working?
[04:54] <NCommander> I've never tried making an intrepid chroot from hardy in pbuilder
[04:54] <NCommander> I simply run pbuilder in my intrepid chroot
[04:54] <NCommander> You should package the files in doc/*
[04:54] <coppro> no, I don't know how to use pbuilder
[04:54] <NCommander> Either add them to the dev package, or add a new doc package
[04:54] <NCommander> (the doc package is arch all)
[04:54] <NCommander> Oh!
[04:54] <NCommander> Well, its easy
[04:55] <NCommander> install pbuilder
[04:55] <NCommander> then
[04:55] <NCommander> pbuilder create --distribution intrepid
[04:55] <coppro> from inside the chroot?
[04:55] <NCommander> Nah, you can do it in hardy
[04:55] <NCommander> pbuilder creates its own chroot for building packages
[04:56] <coppro> okk
[04:56] <NCommander> I also recommend installing the lintian backport if its available
[04:56] <coppro> I have backports in my sources.list
[04:56] <NCommander> ^and you don't want to do your packaging in a intrepid chroot
[04:56] <coppro> where does pbuilder create the chroot?
[04:57] <NCommander> well, when packaging, you have a pbuilder chroot; which is used solely by pbuilder for building a package. Pbuilder is a simple way to replicate the conditions your package will be built in
[04:57] <NCommander> But you can't actually do any packaging work in it (pbuilder creates the chroot on the fly from a base.tgz file it generates)
[04:57] <coppro> ok so pbuilder just stashes it someplace I don't need to care about it?
[04:57] <NCommander> pretty much
[04:58] <NCommander> (I use both pbuilder and sbuild, but sbuild can be a pain to work with, so only use it if your trying to figure out why a package is going boom on a buildd)
[04:58] <coppro> so does that mean I nead a pbuilder chroot and a regular variety? or should I just be running lintian more recently than when the hardy one was available
[04:58] <ScottK> siretart_: Reading, http://news.launchpad.net/cool-new-stuff/launchpads-new-look it seems clear that Launchpad is not at all concerned about concerns of experienced users.
[04:58] <NCommander> Meh
[04:58]  * NCommander was a gforge maintainer, and they didn't care either
[04:58] <NCommander> Savannah is about the only one who does
[04:58] <NCommander> coppro, well, here's how I have it setup
[04:59] <NCommander> I have a pbuilder intrepid chroot (created via pbuilder create)
[04:59] <coppro> ok, doing that as we speak
[04:59] <ScottK> NCommander: They keep pretending their part of the FOSS community, but clearly they aren't.
[04:59] <NCommander> I have a /chroot folder, in which I have chroot-intrepid, chroot-intrepid-i386, chroot-intrepid-lpia, and chroot-intrepid-powerpc, and chroot-intrepid-sparc
[04:59] <NCommander> ;-)
[04:59] <NCommander> For your needs, that's a little overkill
[04:59] <coppro> no kidding
[05:00] <NCommander> (I also have a sid and hardy one in there too)
[05:00] <coppro> lol
[05:00] <coppro> but the question is, do I need any of that?
[05:00] <NCommander> (and another intrepid one in /home/buildd/chroot/chroot-intrepid if I actually have to use sbuild)
[05:00] <NCommander> YOu should have a standalone intrepid chroot created via debootstrap
[05:00] <coppro> ok
[05:00] <coppro> ill make that
[05:00] <coppro> after this one finishes
[05:00] <NCommander> yeah
[05:00] <NCommander> YOu can package on hardy, and usually get away with it
[05:01] <NCommander> But you can get weird failures, especially because of the new glibc in intrepid
[05:01] <NCommander> (I've currently been working on resolving as many as I can, but I'ms tarting to think ipv6's API is completely broken in 2.8)
[05:01] <StevenK> Don't tell Ulrich Drepper
[05:01] <NCommander> coppro, are you running i386, or amd64?
[05:02] <StevenK> Because oh-mi-god, libc is never broken
[05:02] <coppro> i386
[05:02] <NCommander> StevenK, I told him extactly what I think of glibc ;-)
[05:02] <ScottK> And if you pay him, he'll explain why.
[05:02] <StevenK> If you pay him enough, the explaination might even make sense
[05:02] <coppro> lol
[05:02] <NCommander> coppro, ok, if you were on amd64, I would recommend having an i386 chroot around, but since you don't need to worry about it
[05:03] <ScottK> StevenK: I wouldn't go that far.
[05:03] <StevenK> I run amd64, and I have an i386 chroot just to build stuff
[05:03] <coppro> just out of curiosity, what good is a chroot for a different processor?
[05:03] <StevenK> ScottK: Okay, it will make sense to him
[05:03] <NCommander> coppro, amd64 can run i386 and lpia natively
[05:03] <coppro> oh, okk
[05:03] <coppro> that makes sense
[05:03] <ScottK> That I'll buy.
[05:03] <StevenK> Since they're all x86
[05:03] <NCommander> with qemu, it can also run powerpc, and I've heard it can make it run sparc
[05:03] <StevenK> Ish
[05:03] <coppro> *doy*
[05:03] <StevenK> NCommander: And arm
[05:03] <eboyjr> Hey, I made a GNOME applet that I would like packaged, yet I don't know much about packaging. I know what files need to be in place. The Ubuntu Wiki says that I need a link to the software's homepage, but there is none.
[05:03] <NCommander> I still haven't had success with sparc ;-)
[05:03]  * coppro was confusing amd64 and ppc
[05:03] <NCommander> no ubuntu-arm (yet)
[05:04] <NCommander> But I do have an actual arm box for that
[05:04]  * coppro hits himself over the head multiple times
[05:04] <NCommander> don't worry
[05:04] <NCommander> When I was new, I knew what you were going through
[05:04] <ScottK> eboyjr: There needs to be an upstream location for it.
[05:04] <ScottK> eboyjr: You can always set up a Launchpad project to host it.
[05:05] <eboyjr> ScottK: Okay, thanks!
[05:05] <NCommander> ScottK, unless you want to do what I do, and resolve FTBFS, a native chroot is all you do
[05:05] <coppro> ok, how do I submit a needs-packaging bug?
[05:05] <NCommander> coppro, I assume you know what a FTBFS is?
[05:05] <eboyjr> ScottK: Even for a Gnome applet, though?
[05:05] <coppro> fail to build something something?
[05:06] <NCommander> coppro, reportbug script, or just file a bug against ubuntu on launchpad, with needs-packaging as the tag
[05:06] <NCommander> coppro, Failure/Fails to build from source
[05:06] <coppro> ok
[05:06] <ScottK> eboyjr: It's non-native software, so yes.
[05:06] <coppro> i've heard that before, just couldn't remember
[05:06] <eboyjr> thx
[05:06] <NCommander> eboyjr, I've seen debian packages, that if the upstream handles debian/, use debian native versioning
[05:06] <NCommander> THat's allowed under policy
[05:06] <NCommander> er, that was for ScottK
[05:07] <NCommander> of course, that doesn't apply for Ubuntu (since we'd use 0ubuntuX)
[05:07] <ScottK> NCommander: It is allowed, but personally I think it's a bad idea.
[05:07] <ScottK> We can use that in native versioning too.
[05:08] <NCommander> I didn't say it was a good idea ;-)
[05:08] <NCommander> having it as a native package prevents NMUs
[05:08] <NCommander> ^from working sanely
[05:08] <ScottK> Also it forces a new upstream every time you have a packaging change.  For non-Debian users it gets painful.
[05:08] <NCommander> coppro, did you catch what I said about packaging the documents?
[05:08] <NCommander> ScottK, not like they care about us (much)
[05:09] <coppro> nope, missed it
[05:09] <ScottK> If you want to be a good upstream ....
[05:09] <ScottK> Of course some people don't.
[05:09] <coppro> I know there ought to be a docs package, I just haven't gotten to it
[05:10] <NCommander> coppro, Package the stuff in the /doc folders, either shove it in the -dev package, or add a seperate doc (remember that the doc should be arch all)
[05:10] <NCommander> if its just a few pages, I usually just stick it in the -dev package
[05:10] <NCommander> But that's just me
[05:10] <coppro> I
[05:10] <coppro> I'll put it in separately
[05:10] <NCommander> The rules file looks good, but I'd remove some of the dh_make comments (again, not necessary, but it makes your package more shiny ;-))
[05:11] <NCommander> and I recommend a get-orig-source: target
[05:11] <coppro> how does one do that?
[05:11] <NCommander> It's (usually) just a simple wget to the upstream tarball
[05:12] <NCommander> so something like this
[05:12] <NCommander> get-orig-source:
[05:12] <RAOF> If you've got a watch file, it's easy to get uscan to do the heavy lifting for you.
[05:12] <NCommander> cd .. && wget *url to upstream tarball*
[05:12] <NCommander> Oooh, RAOF I completely forgot about that
[05:12] <RAOF> And you should have a watch file :)
[05:12] <StevenK> RAOF: I have a stupid question about Do.
[05:12]  * coppro apparently doesn't have a watchfile :(
[05:13] <coppro> don't tell me, I can do this
[05:13] <RAOF> StevenK: Go ahead!
[05:13] <StevenK> RAOF: I have put gnome-do in my session. But then that means that I get Do popping up when I log in.
[05:13] <RAOF> StevenK: pass --quiet to gnome-do in your session thingy.
[05:14] <StevenK> Ah, sweet
[05:14] <RAOF> man gnome-do actually exists, and describes this option :)
[05:14] <StevenK> So I see. :-)
[05:14] <coppro> ok, I have a watch file, so I just do get-orig-source: uscan?
[05:15] <RAOF> Not quite, there's a bit of magic required.
[05:16] <RAOF> You can do get-orig-source :
[05:16] <RAOF> uscan --download --package <yourpackagename> --destdir=$(CURDIR) --no-symlink --upstream-version 0 --watchfile=$(dir $(_))/watch
[05:17] <coppro> I'm gonna trust you on this one lol
[05:17] <RAOF> Basically the only piece of magic there is the $(_) make variable; I haven't found that documented, but it's the path to the Makefile being executed.
[05:18] <RAOF> (in this case, it's the path to your rules file)
[05:19] <coppro> ah. Can't we assume that we are in the project root directory and that uscan will Do The Right Thing?
[05:19] <RAOF> No.
[05:20] <RAOF> If you read Debian policy, get-orig-source is explicitly described as being able to be called from any directory.
[05:20] <coppro> ok
[05:21] <coppro> nope you are wrong
[05:21] <RAOF> ?
[05:22] <coppro> $(_) appears to be the path to the make instance
[05:22] <coppro> because it's looking for /usr/bin/watch
[05:22] <RAOF> Hm.  This is why my rules files have a big comment above that get-orig-source target :)
[05:22] <RAOF> On the other hand, that works for me.
[05:23] <RAOF> Just confirmed by running "Packaging/Debian/GNOME-Do/trunk/debian/rules get-orig-source"
[05:25] <coppro> echo $(_) gives "/usr/bin/make"
[05:27] <RAOF> http://cooperteam.net/foo <- running ./foo bar results in "/home/raof/./foo"
[05:28] <coppro> oh
[05:28] <coppro> doy
[05:28] <coppro> i get it
[05:28] <coppro> ok ty
[05:28]  * NCommander feels like packaging something
[05:28] <NCommander> ScottK, Can you see any issues with wxGTK+ getting packaged?
[05:29] <eboyjr> What license should my applet be released under?
[05:29] <ScottK> Ah, it starts with a G?
[05:29]  * NCommander whacks ScottK 
[05:30] <NCommander> ScottK, you can't directly sync libnet-dns-perl?
[05:30] <ScottK> Cool.  The LP drop downs are gone.  Now it takes even more clicks to get stuff done.
[05:30] <ScottK> NCommander: Archive admins are supposed to execute syncs.
[05:30] <coppro> wxGTK isn't packaged?
[05:31] <NCommander> coppro, only 2.6 is
[05:31] <NCommander> I can't access the wxWidgets page
[05:32] <NCommander> ScottK, so why were you testing me? Any specific reason?
[05:32] <coppro> I have a package called libwxgtk-2.8-0 on my system
[05:32] <NCommander> coppro, did you install codeblocks?
[05:32] <NCommander> hrm
[05:32] <NCommander> well
[05:32] <coppro> no
[05:32] <NCommander> I'll be damned
[05:32] <NCommander> THere it is
[05:32] <coppro> lol
[05:32] <NCommander> packaged.u.c is being glitchy again
[05:32] <NCommander> it only showed the 2.8 version
[05:33]  * NCommander grabs codeblocks and begins packaging
[05:34] <coppro> why does uscan think my upstream version is 0?
[05:34] <ScottK> NCommander: I figure you'll want to be a MOTU and I want to know how I'm going to react to your application.
[05:34] <NCommander> I think its a little early to consider me for MOTU
[05:35] <ScottK> NCommander: Agreed.  Just planning ahead.
[05:35] <NCommander> I suspect my DD application will have been processed and rejected because I really doubt I'm going to get accepted on the grounds of being a "m68k/hurd porter"
[05:35] <RAOF> coppro: Becuase you told it to compare against 0?
[05:35] <coppro> doy
[05:35] <coppro> probably a good reason
[05:35] <RAOF> Because it's a fair bet that any upstream version will be > 0 :)
[05:36] <NCommander> ScottK, codeblocks already has a debian folder, I assume I should just amend its changelog, and clear lintian, and shove it in revu?
[05:36] <ScottK> NCommander: Make it a good package.  Depending on upstream it may or may not take a lot of additional work.
[05:37] <NCommander> It looks good so far
[05:37] <NCommander> Its not using checkinstall for one ;-)
[05:37] <coppro> how do I specify that I close the needs-packaging bug
[05:37] <ScottK> That's a start.
[05:37] <NCommander> coppro, in the changelog, at the end of Inital release, add (LP: nnnn) where nnnn is the bug number
[05:37] <coppro> ok ty
[05:38] <coppro> unrelated question: is there a way to tell diff to ignore all underscore-only changes?
[05:40]  * NCommander works on clearing the lintian issues
[05:42] <ScottK> NCommander: (LP: #nnnnnn)
[05:42] <ScottK> coppro: ^^
[05:42] <coppro> lol
[05:42] <NCommander> ooh
[05:42] <NCommander> doh
[05:42] <ScottK> The regex doesn't actually look for the parens.  Those are just for style.
[05:42] <coppro> (yes it does)
[05:43]  * ScottK declines to get in an argument.
[05:44] <coppro> it does, because of the fact that for a couple of reasons, my regex, rather than libmk4-(.*)\.tar\.gz
[05:44] <coppro> is libmk4-(2\.4.*)\.tar\.gz
[05:45] <coppro> and when I only had the parens around the .*, it got confused
[05:45]  * RAOF thinks coppro and ScottK are thinking of different regexs
[05:46] <coppro> oh
[05:46] <coppro> yeah, that would probably be it
[05:46] <ScottK> Apparently.
[05:48] <ScottK> If anyone wants some fun, they can probably file a removal bug for firefox.
[05:48] <coppro> lol
[05:48] <NCommander> file for removal O_o?
[05:48] <NCommander> Huh, what, why?
[05:49] <NCommander> Unless Ubuntu going the Iceweasel route
[05:49] <DarkMageZ> cause firefox-3.0 covers firefox :P
[05:49] <NCommander> firefox-3.0 has Provides firefox line in it?
[05:49] <ScottK> Yes.
[05:50] <ScottK> We ship firefox 2 as firefox in Hardy for some transitional period.
[05:50] <NCommander> Is there a wiki page on the specific way to do this
[05:50] <NCommander> Or simply file the bug against firefox, add ubuntu-archive, and justify the reason
[05:51] <ScottK> There is a spot on the wiki that describes it.
[06:27] <ScottK> Good night all.
[07:25] <NCommander> kees, jdstrand ping
[07:36] <NCommander> kees, jdstrand https://bugs.edge.launchpad.net/ubuntu/gutsy/+source/clamav/+bug/249316
[07:37] <NCommander> er, wow
[09:47] <huats> morning everyone
[10:01] <NCommander> morning huats
[10:01] <huats> morning NCommander
[10:04] <jpds> morning
[10:04] <huats> hey jpds
[10:04] <jpds> hey huats
[10:05] <NCommander> THis conversation isn't going anywhere fast
[10:05]  * NCommander returns to packaging codeblocks
[10:07] <tacone> omg, someone vandalized launchpad layout :-o
[10:08] <NCommander> tacone, just upgraded to the beta launchpad
[10:08] <NCommander> Or did they just roll that out for all users
[10:09] <tacone> NCommander: n° 2.
[10:09] <NCommander> o_o;
[10:09] <NCommander> huh?
[10:18] <slangasek> NCommander: yes, it's been rolled out today
[10:19] <NCommander> I have mixed feeligns about the new UI
[10:19] <NCommander> I think it looks nicer, but it also feels so slow in firefox
[10:22] <NCommander> slangasek, I didn't know you were involved with Ubuntu. Amazing what you learn just being in #u-motu
[10:24] <NCommander> slangasek, can you approve security updates?
[10:25] <wgrant> NCommander: Just subscribe ubuntu-security to the bug, mark it In Progress, and poke kees or jdstrand_ about it.
[10:25] <slangasek> yes, there are many things one can learn here. ;)
[10:25] <slangasek> no, I don't handle security updates.
[10:26] <NCommander> wgrant, I did ;-), I was just curious if there was someone awake who could
[10:26] <NCommander> slangasek, yeah, well, I learned more about dak and britney then most people ever would want to hanging out in #d-devel
[10:30] <NCommander> so what are you up to this fine morning?
[10:30] <wgrant> NCommander: Patches unfortunately sit around for weeks.
[10:31] <NCommander> wgrant, I'd hope security ones go a little faster ;-)
[10:31] <wgrant> NCommander: Not always.
[10:31] <wgrant> We do have a bottleneck of two people.
[10:31] <NCommander> I'm surprised there aren't more
[10:32] <wgrant> Canonical apparently doesn't feel the need.
[10:32] <Syntux> any possible way to search this channel logs?
[10:33] <NCommander> ah, the "joy" of having corporate overlords.
[10:33] <wgrant> Indeed.
[10:34] <Iulian> Syntux: irclogs.ubuntu.com
[10:34] <Syntux> Iulian, looking for search-able one
[10:41]  * NCommander hits his head on the desk a few thousand times
[10:42] <huats> Syntux: hello
[10:42] <Syntux> hey huats
[10:42] <huats> Syntux: did you get my email ?
[10:42] <Syntux> yes I did
[10:42] <huats> did you understand what I mean ?
[10:43] <Syntux> sure
[10:43] <NCommander> I'm either going to have to give codeblocks' configure script a root canal, or do something crazy
[10:43] <huats> Syntux: great
[10:43] <huats> :)
[10:54] <slytherin> Syntux: in what way do you want to search?
[11:03] <Syntux> slytherin, channel logs.
[12:01] <tacone> hello. running uscan as root inside my intrepid chroot gives: Can't exec "debian/orig-tar.sh": Permission denied at /usr/bin/uscan line 1296.
[12:31] <lilgies> hello I create my first debian package and I have this error : dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2
[12:31] <devfil> lilgies: paste in pastebin.com all the output please
[12:32] <huats> norsetto !!!
[12:32] <norsetto> norsetto!?
[12:32] <huats> :)
[12:32] <norsetto> huats !!!
[12:33] <tacone> hello, I am trying to debuild -S -sa the "grace" package in intrepid but I get this http://pastebin.com/m6c93e67d
[12:33] <lilgies> devfil: ok the output is here : http://pastebin.com/m572653a9
[12:34] <devfil> tacone: have you installed quilt package?
[12:34] <devfil> lilgies: #
[12:34] <devfil> /bin/bash ../../mkinstalldirs /usr/share/qtuneroid/pics/
[12:34] <devfil> #
[12:34] <devfil> mkdir -p -- /usr/share/qtuneroid/pics/
[12:34] <devfil> #
[12:34] <devfil> mkdir: cannot create directory `/usr/share/qtuneroid': Permission denied
[12:35] <tacone> no. I'll get a "quilt" tatoo on my arm to never forget that again
[12:35] <ion_> ‘script; pastebinit -i typescript’ might be useful, btw.
[12:35] <tacone> devfil: works. thanks
[12:35] <ion_> The output is sent to pastebin after you exit (^D) from the shell launched by script.
[12:37] <devfil> lilgies: your package try to install files in /usr/share/qtuneroid/pics/ instead of /tmp/buildd/qtuneroid-0.9/debian/qtuneroid/usr/share/qtuneroid/pics/
[12:40] <jdstrand> NCommander: re clamav> thanks! will process today
[12:41] <emgent> moin
[12:49] <Iulian> apachelogger: Could you please have a look at gtkmm-utils on revu?
[12:50] <abogani> Hi MOTUs! Could Someone review my package on REVU please? The packages is rt-tests (http://revu.ubuntuwire.com/details.py?package=rt-tests): A set of programs that test and measure various components of "realtime" kernel behavior, such as timer latency, signal latency and the functioning of  priority-inheritance mutexes. Thanks in advance! Please be patient with me it's my first package! :-) Thanks in advance!
[12:50] <abogani> TheMuso: ^
[12:51] <TheMuso> abogani: I will if I get some time this afternoon.
[12:51] <abogani> Thanks Luke.
[12:52] <lilgies> thanks devfil
[12:53] <emgent> TheMuso: o/
[13:04] <lilgies> devfil: how can I change the directory ?
[13:06] <devfil> lilgies: where is the tarball of qtuneroid?
[13:06] <RainCT> hi
[13:06] <norsetto> Hola RainCT
[13:08] <lilgies> devfil: he is in /home/nico/packaging/qtuneroid/qtuneroid_0.9.orig.tar.gz
[13:09] <devfil> lilgies: a link to download it please
[13:10] <lilgies> devfil: http://cjoint.com/?hrojMwQoVz
[13:10] <lilgies> http://cjoint.com/data/hrojMwQoVz_qtuneroid_0.9.orig.tar.gz
[13:21] <devfil> lilgies: can you paste your rules?
[13:23] <lilgies> yes
[13:23] <lilgies> devfil: http://pastebin.com/d59ad39e3
[13:28] <devfil> lilgies: I don't know but it is an error caused by mkinstalldirs script, so take a look a it
[13:29] <lilgies> devfil: ok thank you for your help
[13:46] <lilgies> devfil: I don't found the error :(
[13:47] <lilgies> someone else can it create the package?
[13:56] <hefe_bia> Hi MOTUs, I need some (more experienced) help on bug 223812. It would be good if someone could take a look and say what's the best course of action. I could provide the debdiffs then. Several prior solutions didn't work out.
[15:39] <bddebian> Heya gang
[15:41] <ScottK-laptop> Heya bddebian.
[15:42] <ScottK-laptop> See you later.   Back to $WORK.
[16:25] <Iulian> Hi bddebian
[16:25] <bddebian> Hello Iulian
[16:37] <Iulian> If anyone has some spare time and would like to review a package, please have a look at http://revu.ubuntuwire.com/details.py?package=gtkmm-utils (C++ utility and widget library), needed by paperbox.
[16:39] <geser> Hi bddebian
[16:42] <bddebian> Heya geser
[16:45] <phyphor> Hi, I have a question that I think is best answered in here
[16:46] <phyphor> There's a very, very old version of IDJC available through Synaptic
[16:47] <phyphor> There are newer versions available, but I am not sure if they aren't available because of the mp3 licensing issue
[16:47]  * phyphor can't make its way around the possible issues and figured coming and asking might be sensible
[16:53] <kirkland> zul: wanna sponsor an ecryptfs-utils merge?
[16:53] <kirkland> zul: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/249503
[16:53] <kirkland> zul: not a rush
[16:53] <kirkland> zul: today would be nice :-)
[16:53] <zul> kirkland: poke me after lunch
[16:53] <kirkland> zul: k
[17:04]  * phyphor wonders if, perhaps, this wasn't the most appropriate channel after all
[17:07] <Amaranth> phyphor: file a bug asking for a new version, i guess
[17:07] <Amaranth> I don't think we have any problems with mp3 stuff, it'd just go in multiverse
[17:07] <phyphor> I wasn't sure if the reason it wasn't upgraded was mp3 licensing, or if it just hadn't been done yet
[17:08] <phyphor> Thanks Amaranth :)
[18:19] <RoAkSoAx> norsetto: to request a mentor should i write to motu-mentoring-reception at reponses.net or to to motu-mentors list?
[18:20] <norsetto> RoAkSoAx: motu-mentoring-reception at reponses.net
[18:20] <RoAkSoAx> norsetto: thnks :)
[18:20] <norsetto> RoAkSoAx: wasn't clear in the wiki pages?
[18:20] <RoAkSoAx> norsetto: it was but since a couple guys where writing to motu-mentors list...
[18:21] <norsetto> RoAkSoAx: ok, they were wrong ;-)
[18:21] <RoAkSoAx> norsetto: i know that now :) it just made me doubt for a lil bit xD
[18:30] <DarkAudit> Are these two actually bugs, or me not knowing what I'm doing: https://bugs.launchpad.net/ubuntu/+source/apt-build
[18:31] <DarkAudit> I used the /etc/apt/preferences configuration as seen in the generally cited apt-build tutorial without success... or at least what I expected to have happen
[18:45] <NCommander> ScottK, morning
[19:06] <slytherin> geser: Are we expected to file bugs to contrib java packages to Debian for the things we fix in Ubuntu?
[19:07] <NCommander> slytherin, yeah, we are, its good to gert our changes back upstream if possible
[19:08] <slytherin> NCommander: I am not talking about upstream. I am tired of fixing build problems in Ubuntu that could easily be fixed if contrib packages were build on build servers. Sometime it looks like they are not even built in pbuilder.
[19:10] <NCommander> you mean the Debian source packages?
[19:11] <geser> slytherin: yes, that's a common problem for arch:all packages in Debian as they're build on the Debian buildds but by the DD uploading them
[19:11] <slytherin> geser: when?
[19:12] <slytherin> and how hard is it to check the package in builder before uploading them?
[19:12] <slytherin> s/builder/pbuilder
[19:13] <NCommander> slytherin, You can avoid ever having a package built on one of the debian buildds by simply uploading all the architecture binaries
[19:13] <NCommander> I personally disagree
[19:13] <geser> slytherin: it's up to the DD how much they test them. Ideally they should build them in a pbuilder.
[19:13] <azeem> NCommander: this is about Arch: all packages
[19:13] <NCommander> I'm aware of that.
[19:14] <slytherin> geser: I was also referring to packager. How hard is it to him. I mean we strictly check packages on revu in pbuilder even before making any other comments.
[19:15] <azeem> slytherin: it's not unheard of that Ubuntu devs upload packages that FTBFS as well
[19:16] <slytherin> azeem: I am not claiming that. I am specifically talking about the problems related to missing build dependencies. I once found a package which didn't have ant in build dependency even though the app was supposed to use ant for building.
[19:18] <directhex> still waiting for debian ppa support
[19:18] <laga> directhex: that'd be great
[19:18] <directhex> laga, currently, opensuse build service supports debian & ubuntu
[19:19] <NCommander> I'm surprised there isn't a debian ppa tbh
[19:19] <laga> does the opensuse build service produce sensible debs?
[19:19] <slytherin> directhex: But afaik, creating source packages is a bit tidious. I have not personally tried myself.
[19:19] <mario_limonciell> do you give it source packages?
[19:19] <directhex> laga, sure. i've filed a few bug reports, but it seems to be a sensible buildd
[19:19] <directhex> laga, this is using dsc/diff, not trying to generate debs from a specfile
[19:19] <mario_limonciell> oh phew.
[19:20] <laga> ah.
[19:20] <directhex> i think that's semi-supported (i.e. you can somehow use patches from a specfile in a debian package, in some undocumented manner
[19:20] <laga> so you still need to give it separate source packages for each distro i guess
[19:20] <NCommander> laga, as an alternative, setting up a buildd isn't that difficult
[19:20] <directhex> laga, depends how well-crafted your debian/control is ;)
[19:21] <mario_limonciell> mk-sbuild-lv sets up very nice buildd style builds for your own buildd
[19:21] <laga> NCommander: i know. i think falcon has some support for that.. but i don't care enough about debian to do that - it'd just be nice to have the PPAs also produce debs for debian
[19:21] <NCommander> falcon?
[19:21] <laga> directhex: well, debian/control isn't going to work on suse.
[19:22] <laga> NCommander: seveas' repository manager. very nice piece of software IMHO
[19:22] <directhex> laga, no, but it'll use the same source package on any .deb distro
[19:22] <slytherin> geser: Can you help fix this FTBFS, some problem with ld - http://launchpadlibrarian.net/15969377/buildlog_ubuntu-intrepid-i386.libmatthew-java_0.7.1-1_FAILEDTOBUILD.txt.gz
[19:22] <mario_limonciell> laga, did you sort out that FTBFS?
[19:23] <NCommander> slytherin, Oh, this issue, I keep seeing it crop up all over the place
[19:23] <NCommander> slytherin, I can kick out a fix for this
[19:23] <slytherin> NCommander: you mean that ld throws error about unrecognized options? What is the fix?
[19:24] <laga> mario_limonciell: i've just uploaded a fresh build without the firewire tester
[19:25] <NCommander> slytherin, the fix is change LDFLAGS to remove the -Wl,
[19:25]  * directhex tries some belgian beer
[19:26] <slytherin> NCommander: Ok. I will try that. But give me reason so that I can add to changelog.
[19:26] <NCommander> "Correcting incorrect LDFLAGS that pass -Wl to the linker"
[19:26] <NCommander> -Wl, is used when called by GCC, it shouldn't pass -WL,
[19:27] <directhex> laga, example OBS package page: https://build.opensuse.org/package/show?package=Mono&project=home%3Aoerc
[19:27] <NCommander> speaking of mono
[19:27] <mario_limonciell> directhex, you need a login for that?
[19:28] <NCommander> my patch is still stuck -_-;
[19:28] <directhex> urgh. possibly
[19:28] <directhex> who's on sponsorship duty today?
[19:28]  * NCommander is feeling the urge to code
[19:29] <NCommander> Maybe I should setup a buildd service; upload a package, get it built for Ubuntu, and Debian
[19:29] <laga> NCommander: just complain to the launchpad guys ;)
[19:29] <NCommander> All it needs is dak, some custom coding, and such
[19:29] <NCommander> Would be a very interesting project
[19:29] <mario_limonciell> NCommander, urge to code eh?  fix some bugs with that urge i says :_)
[19:30] <NCommander> mario_limonciell, I already stomped out a rather nasty mono bug this week :-P
[19:30] <slytherin> NCommander: I can not find that flag set anywhere in rules file.
[19:30] <directhex> NCommander, a nasty ubuntu bug. not strictly speaking any mono dev's fault ;)
[19:32] <NCommander> Actually, "abusing" dak to support such builds would be rather cool ;-)
[19:34] <NCommander> ugh
[19:34] <NCommander> Codeblocks changes binary files in its source package when it builds
[19:35] <NCommander> WTF, I type make distclean, and the package configures itself O_O;
[19:35] <ion_> If it *generates* them on build, simply remove them in clean rule.
[19:35] <NCommander> ion_, No, it shipped them in the source package
[19:36] <RoAkSoAx> norsetto: is this a good request? http://pastebin.ubuntu.com/28096/
[19:36] <NCommander> I'm not sure if they're cleanly regenerated or not yet
[19:37] <ion_> ncommander: http://sam.zoy.org/lectures/20050910-debian/img20.html
[19:37] <ion_> ncommander: I mean, if they are shipped in the source package but it builds the same whether they exist in the tree before build or not, just remove them in the clean rule.
[19:38] <NCommander> Yeah, I'm checking to see if that's the case
[19:38] <NCommander> but I need to remove them from the original source package because dpkg-source freaks out about it
[19:38] <ion_> There should be no need for that.
[19:39] <ion_> As long as you delete them in the clean rule, it should just ignore them when creating a diff.gz
[19:39] <NCommander> works for me
[19:39] <NCommander> Thank you for saving me some extremely anonying work ;-)
[19:40] <NCommander> I'm probably going to have to lobotimize this package to make it move plugins into the lib folder vs. share
[19:42] <DarkAudit> con someone take a look at https://bugs.launchpad.net/ubuntu/+source/apt-build for a moment? The sources.list issue is probably a definite bug. The other one I can't get anyone to tell me one way or the other.
[19:42]  * NCommander kicks his printer
[19:43] <NCommander> Bah, PC LOAD LEGAL my ass
[19:43]  * ion_ loves his printer
[19:43] <ion_> Bought a non-sucky one recently.
[19:43] <directhex> anything other than PC LOAD A4 implies you need to be stabbed through the brain
[19:43] <NCommander> I've had this LaserJet 4 for years
[19:43] <NCommander> Works great
[19:43] <NCommander> I even have a Postscript module installed
[19:43] <laga> i've got a brother printer which is also a scanner and photo copier. the linux drivers are *slow*
[19:44] <laga> next thing will be a laser printer with postscript and network support.
[19:44] <NCommander> sure its just not the printer
[19:44] <ion_> It speaks Ethernet and Postscript, and is *really* fast. A used LaserJet 2300
[19:44] <NCommander> I have a LJ 2300
[19:44] <laga> NCommander: i hear it's faster in windows.
[19:44] <NCommander> But I perfer my 4 cause I can still use a font cart
[19:44] <directhex> we have a networked brother at work with a nasty print driver bug
[19:44] <directhex> i think there's a LP bug open for it
[19:45] <NCommander> Brother printers are in general a bug
[19:45] <NCommander> I had one of those brother all in ones
[19:45] <NCommander> It was more reliably to have my laptop use the cell to fax it the printer to print something else then to print on it directly
[19:46] <NCommander> DarkAudit, looks like a legit bug
[19:48]  * NCommander fiddles with dak
[19:48] <NCommander> Anyone else want to help create a PPA service ;-)
[19:48] <ion_> falcon
[19:49] <NCommander> falcon doesn't appear to build packages ...
[19:51] <laga> NCommander: see file:///usr/share/doc/falcon/html/index.html ;)
[19:51] <DarkAudit> NCommander: I had concerns about the installing one, but soething else is up when long-accepted procedures don't make a difference, like my /etc/apt/preferences file being ignored.
[19:51]  * NCommander is suprised that the PPA doesn't build on all Ubuntu ports platforms
[19:52] <StevenK> NCommander: It has to do with how the PPA buildds builds packages versus how Ubuntu buildds build packages
[19:52] <NCommander> Care to enlighten then ;-)
[19:53]  * NCommander would always love to know more about how launchad ticks
[19:53] <laga> there is launchpad podcast. i don't like podcasts tho :(
[19:55] <NCommander> I just wish Launchpad itself was properly open ...
[19:57] <norsetto> RoAkSoAx: looks good to me
[19:58] <NCommander> at least launchpad isn't running as horrible as it was before
[20:00] <DarkAudit> apt-build install is meant, when properly configured, to install the package that was just built on the local system, right?
[20:02] <NCommander> I don't use it so I don't really know
[20:04] <DarkAudit> NCommander: I'm trying to find out if apt's installing of the remote package instead is the result of a bug, or my not configuring something properly. I've yet to find what that "something" is, though.
[20:05] <RoAkSoAx> norsetto: thanks :=)
[20:06] <norsetto> RoAkSoAx: de nada
[20:12] <DarkAudit> hm.. when apt-build switches to the install part of the process, it's actually handed over to apt to complete the task?
[20:19] <k0p> hi all.
[20:19] <k0p> package-installs-python-pyc <- ideas to solve this warning?
[20:20] <ion_> Prevent the inclusion of pyc files in the package.
[20:21] <k0p> hm
[20:21] <k0p> yeah
[20:24] <k0p> ion_, maybe adding a code in debian rules to delete these files?
[20:37] <norsetto> cody-somerville: are you free to check a couple of sru?
[20:38] <k0p> norsetto, hi
[20:38] <cody-somerville> norsetto, not at this very moment but if you post the bugs #'s I'll take a look in a minute.
[20:39] <norsetto> cody-somerville: I've got 4 pending, but one should be really easy to ack, its bug 249355, thx
[20:39] <k0p> norsetto, what version of lintian do you use?
[20:39] <norsetto> k0p: lintian the superbitch edition
[20:39] <k0p> lolol
[20:39] <k0p> :P
[20:39] <k0p> norsetto, can you see if I silent warnings on umit?
[20:40] <cody-somerville> norsetto, so it would just be a no source change rebuild?
[20:40] <k0p> I don't have lintian that show me this warnings..
[20:40] <norsetto> cody-somerville: yep
[20:40] <norsetto> k0p: what do you mean?
[20:40] <cody-somerville> norsetto, Potential for regression?
[20:41] <norsetto> cody-somerville: by rebuilding? I dunno, maybe we can cause a buildd to explode
[20:41] <k0p> norsetto, well.. yesterday or before, you told me that umit have lot of warnings. I make a fix now and I would like if I can remove this warnings.
[20:41] <cody-somerville> norsetto, have you rebuilt it yourself and confirmed it works all fine and dandy?
[20:41] <k0p> can you take a look, please?
[20:42] <norsetto> cody-somerville: well, I can't test that particular error conditions, I haven't got his source files
[20:43] <cody-somerville> norsetto, It seems to me that it would be simple to reproduce. He says that any source file that uses both lablGL and Sdlgl will trigger the failure.
[20:45] <norsetto> cody-somerville: yes, like ? I haven't got any source files which uses both lablGL and Sdlgl. All I can do is ask him for a simple test case that we can use to reproduce
[20:46] <cody-somerville> norsetto, Okay. Let me know when you get a test case.
[20:46] <norsetto> k0p: your lintian should be exactly like mine, I don't see why my lintian would pick up things that yours can't
[20:47] <k0p> yeah
[20:47] <norsetto> cody-somerville: willco
[20:47] <k0p> :\ what exactly command that you do?
[20:47] <norsetto> k0p: just lintian on the deb will do
[20:48] <norsetto> k0p: have you uploaded to REVU? If so, please post a link
[20:48] <k0p> norsetto, yeah
[20:48] <k0p> on deb
[20:48] <k0p> now I see.
[20:48] <k0p> not yet, I need make more fixes :d thanks
[20:49] <norsetto> k0p: ah, $deity bless lintian, no problem :-)
[20:49] <cody-somerville> norsetto, I suppose you haven't been able to confirm it is fixed on Intrepid either, eh? :]
[20:51] <norsetto> cody-somerville: what needs to be fixed? Can you not see that it is built with the right version of the library?
[20:57] <cody-somerville> norsetto, I'm wondering why the Intrepid task is marked as confirmed.
[20:57] <norsetto> cody-somerville: I haven't opened any intrepid task, just an hardy one
[20:59] <cody-somerville> norsetto, If you look at bug, you'll notice there is two tasks. One for Ubuntu and then one specifically for Hardy.
[20:59] <norsetto> cody-somerville: yes, and where is the intrepid task?
[20:59] <cody-somerville> norsetto, If I understand correctly, the one for Ubuntu (the normal one) represents a task in the latest development version.
[20:59] <norsetto> cody-somerville: nope, you have to explicitly open a task for that
[20:59] <k0p> I need help here with executable-not-elf-or-script warning.. what is the way to solve this?
[21:00] <norsetto> k0p: chmod -x it
[21:01] <cody-somerville> norsetto, If you do that, the one I'm talking about will say it is tracked in Intrepid. I'm pretty sure that tasks not targeted to a specific release are tasks in the latest development version (ie. Intrepid). So should the main one not be marked appropriately if it is not a problem?
[21:01] <k0p> norsetto, don't have +x
[21:02] <k0p> -rw-r--r--
[21:02] <norsetto> cody-somerville: if I click on it it doesn't go to https://bugs.launchpad.net/ubuntu/intrepid/+source/ocamlsdl
[21:03] <norsetto> cody-somerville: making that fix-released I think its pretty confusing, it would be better to open a specific intrepid task and mark that as fix-released
[21:04] <cody-somerville> norsetto, so it sorta sounds like a bug/UI issue in launchpad then
[21:04] <norsetto> cody-somerville:IMHO it definetively is
[21:04] <mcasadevall_> What's wrong with launchpad?
[21:04] <mcasadevall_> and ...
[21:04] <Iulian> What's wrong with it?
[21:04] <norsetto> mcasadevall_: whats not wrong with launchpad?
[21:05] <NCommander> norsetto, I was avoiding going there ...
[21:05] <norsetto> NCommander: why? When you see a bridge taht just begs to be crossed ...
[21:05] <NCommander> Stupid question
[21:05] <NCommander> How do I push a package to my PPA
[21:05] <NCommander> I've never done it before
[21:05] <NCommander> (aka, where does it need to be uploaded to)
[21:06] <Iulian> NCommander: https://help.launchpad.net/PPAQuickStart
[21:06] <NCommander> Just found that
[21:06] <NCommander> THanks ;-)
[21:06] <cody-somerville> siretart, ^^
[21:10] <NCommander> Anyone care to play with my codeblocks WIP package?
[21:14] <k0p> norsetto, almost fixed all warnings :D
[21:14] <norsetto> k0p: cool
[21:15] <Jazzva> norsetto: Thanks for the notice. I'll prepare the upgrade for gnome-mplayer and gecko-mediaplayer 0.6.3. I'll also check your packages from mentors.d.n
[21:16] <jdstrand> NCommander: hi! thanks for your work on clamav. I updated bug #249316 with some requested changes
[21:16] <norsetto> Jazzva: okki
[21:16] <NCommander> jdstrand, ah, I see
[21:16] <cody-somerville> NCommander, Ever thought about contributing to Xubuntu? :)
[21:16] <norsetto> porthose: I wish you would stop americaniZing my english ....
[21:16] <NCommander> I apologize, I have never done security fixs
[21:17] <NCommander> cody-somerville, I use xubuntu on my other machine, its awesome ;-)
[21:17] <siretart> cody-somerville: ?
[21:17] <cody-somerville> siretart, norsetto and I were just commenting on how it would probably be easier to understand to have the dev release automatically targeted when targeting a stable release
[21:17] <NCommander> jdstrand, do you also want me to correct the hardy patch? (Scott Kitterman did that one, I did the others at his request)
[21:18] <jdstrand> NCommander: the versioning is fine in that one (though references is not where it's preferred-- but no need to respin for that)
[21:19] <NCommander> jdstrand, I apologize for the mistake
[21:19] <jdstrand> NCommander: np. thanks for your work! :)
[21:19] <siretart> cody-somerville: I'm not sure if I understand that...
[21:19] <siretart> cody-somerville: what do you mean with 'targetting'?
[21:19] <cody-somerville> siretart, nominating for release
[21:20] <NCommander> jdstrand, I'm kinda confused though how to change the version, clamav in gutsy/feisty/dapper don't have a -XubuntuX on it
[21:20] <NCommander> jdstrand, looking at the other entries in the change log, this is the next logical number for security uploads
[21:20] <jdstrand> NCommander: no, it was an oddball case where it went through -proposed
[21:21] <jdstrand> NCommander: since we are doing a regular upload, we can get the versioning back under control
[21:21] <jdstrand> (I admit the versioning is/was confusing)
[21:21] <NCommander> Oh, so you want an ubuntu style version number (1ubutuntu0.1), right?
[21:22] <jdstrand> NCommander: yes please
[21:22] <NCommander> jdstrand, just to confirm, gutsy would become: 0.92.1~dfsg2-1.1ubuntu0.1~gutsy3 then
[21:22] <NCommander> (still kinda ugly)
[21:22] <siretart> cody-somerville: hm. you mean that it doesn't make sense to target a bug for a stable release, but not for the development release?
[21:23] <NCommander> jdstrand, (I have the changes more or less done, as soon as you confirm I got the versioning right, I'll post debdiffs)
[21:23] <cody-somerville> siretart, no, thats not what I'm saying. I'm saying the UI is confusing and it could be clarified by automatically targeting a bug for the development release if you target it for a stable release.
[21:24] <cody-somerville> siretart, For example, look at https://bugs.edge.launchpad.net/ubuntu/+source/ocamlsdl/+bug/249355
[21:24] <cody-somerville> siretart, There is two tasks open. One for Ubuntu (the primary task if you will) and a target for Hardy. Correct?
[21:24] <jdstrand> NCommander: 0.92.1~dfsg2-1.1~gutsy3.1
[21:24] <NCommander> *bink*
[21:24] <porthose> norsetto: np done :)
[21:24] <NCommander> Wow, I wasn't expecting that
[21:24] <jdstrand> NCommander: this is a weird case
[21:24] <siretart> cody-somerville: yes.
[21:25] <jdstrand> NCommander: I asked you to follow SecurityUpdateProcedures but then I changed that on you didn't I? :)
[21:25] <NCommander> Pretty much ;-)
[21:25] <NCommander> jdstrand, any reason we're going to 3.1 vs 4 on the final number since all the security updates thus far have gone kinda weird
[21:25] <norsetto> porthose: okki, I just send a reminder to the list just in case somebody else wants to use Franc-English or English-tiliano ;-)
[21:25] <siretart> cody-somerville: ah, and now the problem with this bug is that there is no bugtask for 'intrepid', right?
[21:25] <NCommander> I do know dak gets VERY picky about version numbers
[21:25]  * NCommander is reminded of his own little nightmares with that piece of softare
[21:25] <jdstrand> NCommander: gutsy is already ubuntufied-- but the point is we really want the '.1'
[21:25] <siretart> cody-somerville: TBH, I have the feeling that this can only be properly solved by proper version tracking
[21:26] <NCommander> argh
[21:26] <jdstrand> NCommander: and by 'gutsy', I mean the '~gutsy...' part
[21:26] <NCommander> Damn it, these packages are failing to debian/rules clean
[21:26] <cody-somerville> siretart, I think that simply by adding a target for the dev release automatically would make it easier to understand in the interim, no?
[21:26] <siretart> cody-somerville: I'm not sure. I would also find it convincing if there was no way at all to 'target' a bug to the development release.
[21:27] <jdstrand> NCommander: since it's oddball, I can just fix dapper and feisty-- repost gutsy
[21:27] <siretart> cody-somerville: because you could argue that the 'default ubuntu' task is for the development release
[21:27] <cody-somerville> siretart, I agree. Thats my opinion.
[21:27] <cody-somerville> siretart, but it isn't clear.
[21:27]  * jdstrand intended to help 'mentor' NCommander with SecurityUpdateProcedures, but seems to have failed miserably
[21:28] <cody-somerville> siretart, and as you know, when you target the development release, the 'default ubuntu' task will change to say "tracked in intrepid".
[21:28] <NCommander> jdstrand, It's ok, the ONE time I helped with Debian security update, the same thing happened ;-)
[21:28] <siretart> cody-somerville: okay, I'll make a note and see that I file a bug about this
[21:28] <cody-somerville> Okay, thanks.
[21:29] <jdstrand> NCommander: hopefully this won't scare you off for future Ubuntu updates! :)
[21:29] <NCommander> jdstrand, nah, I already have 12 FTBFS fixed, and an almost done codeblocks package :-)
[21:29] <NCommander> (and a few merges)
[21:29] <jdstrand> \o/
[21:29]  * NCommander waits for pbuilder to finish
[21:29] <norsetto> jdstrand: to scare off NCommander you would need at least a full-gear battalion of angry marines
[21:29] <jdstrand> heh
[21:29] <emgent> norsetto: o/
[21:30] <NCommander> I'm a Debain hurd porter
[21:30] <NCommander> I don't scare
[21:30] <jdstrand> wow, that's brave :)
[21:30] <norsetto> emgent: o/
[21:30] <NCommander> jdstrand, I'm curious, does Ubuntu use dak, or something canonical built to handle archiving?
[21:31] <NCommander> If its dak, I feel your pain, I ran it for m68k to create a testing distribution
[21:31] <jdstrand> NCommander: currently we do use dak for -security, but that is supposed to change pretty soon to use soyuz (ie the regular buildd's as seen in Launchpad)
[21:31] <NCommander> Sounds like a general improvement
[21:32] <jdstrand> it should be, once all the corner cases are worked out
[21:32] <NCommander> Keeping dak happy is like trying to get Microsoft to opensource Windows ;-)
[21:32] <NCommander> ok, it passes pbuilder, uploading gutsy
[21:32] <jdstrand> NCommander: thanks again
[21:33] <NCommander> jdstrand, if there are any more security updates that need work, I'd glad to help
[21:33] <NCommander> Now that I have a full set of Ubuntu, and Debian chroots for two architectures
[21:33] <NCommander> (and four for intrepid)
[21:34] <NCommander> jdstrand, as soon as Launchpad decides to let me upload ...
[21:34] <jdstrand> NCommander: your help is most welcome. You can see what needs to be done by checking out https://code.launchpad.net/~ubuntu-security
[21:34] <NCommander> jdstrand, Uploaded
[21:35] <kees> NCommander: and the cve tracker's output for universe is here: http://people.ubuntu.com/~ubuntu-security/cve/universe-all.html
[21:35] <jdstrand> NCommander: there's a bzr branch that tracks all our CVEs, and a good README file explaining the layout, scripts, how it's used, etc
[21:35] <emgent> NCommander: see also https://wiki.ubuntu.com/SecurityTeam
[21:35] <cody-somerville> siretart, let me know what the bug number is. I made some screenshots to demonstrate.
[21:35] <NCommander> jdstrand, wow, you look a little understaffed to fix all these CVEs ....
[21:36] <jdstrand> NCommander: it was originally inspired by Debian kernel-sec, but is tailored for our workflow
[21:36] <NCommander> jdstrand, that's why this looks familar
[21:36] <jdstrand> NCommander: *sigh* yes, but that is slowly changing
[21:36]  * NCommander mirrors the branch
[21:36] <emgent> :)
[21:36] <jdstrand> NCommander: however, universe is community supported, which is a particularly important area that needs work
[21:37] <NCommander> I'm no MOTU :-/
[21:37] <jdstrand> NCommander: though we accept debdiffs for main too :)
[21:37] <NCommander> (not yet anyway, but maybe someday)
[21:37] <NCommander> man, Dapper is NOT happy
[21:37] <cody-somerville> NCommander, You'll be a MOTU sooner rather then later.
[21:38] <jdstrand> Dapper rarely is
[21:38] <NCommander> how long until that finally goes out of support
[21:38] <jdstrand> (it's getting a bit long in the tooth, which makes backporting hard)
[21:38] <jdstrand> NCommander: desktop 2009, and server 2011
[21:38] <NCommander> Damn it. That's a LONG time
[21:39]  * jdstrand nods
[21:39] <NCommander> I'll see if I can nail the dnsmasq security bug
[21:39] <jdstrand> as hard as it can be to support, it has been really great for user's that need that kind of stability
[21:39] <NCommander> I just use it to bootstrap Ubuntu on my PPC
[21:39] <NCommander> That, or I have a hacked d-i install disk which grabs from the Ubuntu repos vs the Debian ones
[21:40] <jdstrand> NCommander: be sure to coordinate with Koon on #ubuntu-server or #ubuntu-hardened wrt dnsmasq.  he has been in touch with upstream and they have been refining their patch
[21:41] <NCommander> if its already being handled, I'll let it be
[21:41] <NCommander> jdstrand, I'm just currently reading through the ubuntu-cvs-tracker
[21:41] <jdstrand> NCommander: I think he's only handling hardy
[21:41] <jdstrand> (it's the only version in main)
[21:41] <k0p> what's the better way to solve gk/kde sudo trouble?
[21:41] <jdstrand> though he may backport...
[21:42] <NCommander> I assume you try and port against the old codebase if it is at all possible
[21:42] <jdstrand> NCommander: absolutely-- the clamav thing is *very* rare
[21:43] <jdstrand> NCommander: but ScottK did an excellent job in with testing it and we were able to do a one-time MicroVersionUpdate for it
[21:43] <NCommander> yeah, so you do it just like d-security
[21:43] <NCommander> Although you see a little more open to help ;-)
[21:43]  * jdstrand nods
[21:43] <jdstrand> always :)
[21:44] <NCommander> oooh, damn the scponly one is evil
[21:45] <phyphor> Sorry to interrupt, but I'm trying to work out whether this is an appropriate channel to ask about a package that appears to be available in intrepid but not in hardy (which I sort of asked about earlier)
[21:45] <phyphor> (or should I wait to see if I can get an answer over in #ubuntu)
[21:46] <NCommander> phyphor, intrepid is the development branch, any new packages will end up there unless someone backports it to gutsy-backports
[21:46] <NCommander> jdstrand, with your permission, I'd like to work on fixing the scponly issue
[21:46] <NCommander> (I found the patch, looks easy enough to backport
[21:47] <jdstrand> NCommander: don't need my permission! :) basically, if something isn't Assigned, feel free to grab it. If something is Assigned, but doesn't seem to be going anywhere, just ping whoever is assigned
[21:48]  * NCommander looks for the bug report
[21:48] <jdstrand> NCommander: you can assign yourself in LP if there is a bug, otherwise create one and assign it to yourself and subscribe the security team
[21:48] <phyphor> NCommander: The version of IDJC in Hardy is well out of date (and has various bugs raised against it), 0.7.8a is available from source (but won't build as it is looking for jack not jackd), but 0.7.7 is in intrepid - I was wondering what the recommended advice is for a user - do I raise a bug under hardy, work out how to build it from source somehow, or pin so I can get it from IDJC. I figured you guys would be able to tell me the right 
[21:48] <NCommander> jdstrand, is there anything I should do in my local copy of the security branch that needs to be merged?
[21:48] <NCommander> phyphor, probably the proper bet is to request it be backported
[21:49] <jdstrand> NCommander: if you plan to do a lot of triaging, then yes-- just ping kees or I and we can merge it in
[21:49] <NCommander> YEah, I will, this is something I find quite interesting
[21:49] <NCommander> ANd its just like solving FTBFS ;-)
[21:49] <NCommander> yeah, no security bug
[21:51] <jdstrand> NCommander: for patching and the like, just make sure the ubuntu security team is subscribed to any bugs and upload your debdiffs, and we'll update ubuntu-cve-tracker. if some time goes by and nothing is happening, feel free to contact either me or kees
[21:52] <NCommander> jdstrand, cool. Out of curosity, do you need to work at canonical to be an offical part of the security team, or do you recruit regular devs?
[21:53] <jdstrand> to be on ubuntu-security in LP, you need to be a canonical employee. however, there is motu-swat, which is the community security team
[21:54] <jdstrand> NCommander: motu-swat will soon be able to process universe updates once security-in-soyuz is in place, which will obviously help with bottlenecks
[21:54] <NCommander> nice
[21:54] <NCommander> jdstrand, as an added note, how do I get it to show the progress for individual distrubution likes on the clamav note (I don't really use Launchpad's bug tracker that often, and I don't see anything obvious)
[21:55] <phyphor> NCommander: I fear I'm bordering on newbie questions here but I'm trying to find out how to request a backport and the pages I'm finding are all suggesting I should just be able to grab the 0.7.7 version from the intrepid repository. Any advice (even if it's to leave this channel for the masters)?
[21:55] <jdstrand> NCommander: for individual releases (dapper, feisty, etc), you use 'Nominate for release'
[21:56] <NCommander> jdstrand, ok, the fix is in progress :-)
[21:56] <jdstrand> NCommander: for help with ubuntu security processes, feel free to contact me, kees or onyone in motu-swat
[21:56] <jdstrand> https://launchpad.net/~motu-swat
[22:12] <NCommander> jdstrand, you've got patches: https://bugs.edge.launchpad.net/ubuntu/+source/scponly/+bug/249593
[22:16] <cody-somerville> How do I not have access to that bug? :/
[22:16] <NCommander> cody-somerville, it's marked private
[22:17] <cody-somerville> NCommander, I can usually see private bugs.
[22:17] <NCommander> cody-somerville, your not on the security team I take it ;-)
[22:24] <Syntux> Are we strict on .desktop file specs? even with warnings?
[22:25] <norsetto> cody-somerville: feel free to ack when you have time, we can now verify
[22:25] <amikrop> Hello. My RSA public key, is the same as my GPG public key?
[22:26] <cody-somerville> norsetto, I just attempted to run it but either his sample is faulty or I'm missing a dependency.
[22:26] <norsetto> cody-somerville: I had to modify it
[22:27] <norsetto> cody-somerville: just get rif of the loop, and substitute it with a Sdltimer.delay 2000;
[22:27] <norsetto> cody-somerville: s/rif/rid
[22:27] <norsetto> cody: also, for the linking, the command is ocamlc not ocaml
[22:28] <norsetto> cody-somerville: Also, if you want to test it in intrepid, be careful that we have 3.10.2, not 3.10.0
[22:31] <Syntux> when fixing invalid .desktop file do we have to fix errors only or errors and warnings?
[22:33] <norsetto> Syntux: are you using desktop-file-validate? If so, just get it right it, doing half of the work is not worth it, is it?
[22:34] <Syntux> norsetto, sure I'm using it and indeed it's amazing but I was wondering if I have to fix a warning like "deprecated value in Key category: Application" and if we have a list of registered categories.
[22:35] <cody-somerville> norsetto, ACK
[22:35] <norsetto> syntux: just use the freedesktop spec, let me fetch a link for you
[22:35] <Syntux> norsetto, I'm already there.
[22:36] <norsetto> cody-somerville: thanks
[22:37] <cody-somerville> norsetto, np. It was fun to play with another programming language :)
[22:39] <norsetto> Syntux: than what is the problem? You have all categories in appendix A
[22:41] <Syntux> norsetto, ok, just wasn't sure if we follow freedesktop list strictly.
[22:42] <norsetto> Syntux: to the letter ;-)
[22:42] <Syntux> dandy :-)
[22:42] <norsetto> Syntux: we also follow the Gnome HIG
[22:43] <Syntux> I guess I'll have some interesting reads tonight.
[22:43] <norsetto> Syntux: just in case: http://library.gnome.org/devel/hig-book/stable/
[22:43] <Syntux> already there ;)
[22:44] <huats> norsetto: I haven't understand why you mention that "utilised" stuff :)
[22:46] <norsetto> huats: trying to make porthose angry, but he is resilient :-)
[22:46] <huats> :)
[22:46]  * NCommander would like a sponsor for this: https://bugs.edge.launchpad.net/ubuntu/+source/nget/+bug/246723
[22:46]  * norsetto hugs porthose
[22:48]  * porthose hugs norsetto :)
[22:48] <Syntux> huats :-)
[22:48] <Syntux> huh?
[22:48]  * Syntux hugs huats 
[22:49]  * NCommander hugs someone
[22:49]  * Syntux announces MOTU free hugs day.
[22:49]  * huats hugs Syntux back
[22:49] <huats> :)
[22:49] <Laney> is that free as in beer?
[22:49]  * NCommander pokes ScottK 
[22:50]  * ion_ hugs self
[22:51]  * NCommander hugs ion_ 
[22:51] <Syntux> __unicode__(self):  return self.hug
[22:51] <NCommander> time to go get some food
[22:51] <ion_> That single line demonstrated many of the things that are ugly about Python. :-)
[22:51] <Syntux> huats, I was about to send you a .deb for testing.
[22:52] <huats> Syntux: great
[22:52] <huats> can you also provide me the debdiff please ?
[22:52] <Syntux> sure
[22:52] <huats> and the entry of the changelog ?
[22:52] <huats> that would rock
[22:52] <huats> :)
[22:53]  * ion_ ghci NCommander
[22:53] <NCommander> ghci?
[22:53]  * huats uses some dholbach words since he is on holidays :)
[22:53] <ion_> ncommander: It’s an alternative to hugs.
[22:59] <nedko> persia: i'm doing preview packages for upcoming lash-0.6.0, it is on revu, feedback is welcome, i've made some tweaks for pylash for example
[23:01] <persia> nedko: Great news.  Do the current apps work against it, or does it need a recompile?
[23:01] <nedko> persia: no need to rebuild apps
[23:03] <nedko> persia: FYI this and some other packages (jack,laditools,patchage) are important for LADI project: http://nedko.arnaudov.name/wiki/moin.cgi/LADI
[23:03] <persia> nedko: Even cooler.  I won't have a proper test environment until next week, but I'll take a look at the packaging if I can get a chance earlier.
[23:04] <nedko> persia: there is no hurry at all, i have lot of packaging work to do and i'm packaging newbie so i do small and slow steps
[23:05] <nedko> persia: also i've given up for intrepid anyway
[23:07] <persia> nedko: That looks incredibly cool.  While I doubt we can get integration working in Ubuntu, we ought be able to get most of the necessary packages in, and be in a positin to discuss it sensibly in intrepid +1
[23:08] <nedko> persia: the main obstacle is that all software is not yet released as tarballs
[23:09] <persia> nedko: Are you in touch with the relevant upstreams?  Do we expect release in the next month or so?
[23:10] <Laney> vorian: Here?
[23:10] <nedko> persia: i'm dev in all upstreams, except probably patchage (i'm close but not willing to fork it)
[23:11] <norsetto> porthose: Forgiven as long as you admit that warm stout suck and tea is for sissies ;-)
[23:11] <nedko> persia: i'm not sure how close releases are, lash-0.6.0 should be probably ready in august/september because Jusso summercode ends in august
[23:11] <huats> norsetto: I like tea too..
[23:11] <Laney> Or can anyone else re-ack bug #242826 - sync request with a new Debian revision since the previous ack
[23:12] <norsetto> huats: big sissi :-)
[23:12] <vorian> Laney: hi
[23:12] <porthose> beer is good cold or warm
[23:12] <vorian> lemme see
[23:12] <Laney> vorian: Hi, ^^^^
[23:12] <Laney> It b/i/r fine :)
[23:13] <persia> nedko: Hmm.  I'm a little leery of prerelease if we're not confident of upstream release before distro release.
[23:13] <nedko> persia: yup, i do agree, still i want preview packages in the ladi team ppa
[23:14] <nedko> persia: so review is still welcome
[23:14] <Laney> vorian: You might also be interested in acking bug #249610 as this will be broken with Trac 0.11
[23:14] <persia> nedko: That makes sense.  Would you mind also workig with Jusso to see if we can get a release?  The current lash is good, but not quite as much as we'd like.
[23:14]  * persia will loose network connectivity in a couple minutes
[23:14] <persia> s/oo/o/
[23:15] <vorian> Laney: sure, I'll look at them here in a bit
[23:15] <Laney> vorian: Thanks a lot
[23:15] <vorian> thanks for the update
[23:15]  * Laney nods
[23:16] <Laney> I should have checked trac for an existing sync request before doing mine, whoops
[23:16] <nedko> persia: probably we can get lash release before deadline, but i'm affraid to push it to ubuntu mainstream users
[23:16] <persia> nedko: Depends on testing.  Might also check with the #ubuntustudio folk
[23:17] <nedko> persia: it is major refactoring (lash is becoming 100% dbus), and thus somewhat risky, still i dont have regressions here
[23:17] <nedko> persia: i'm there too ;)
[23:19]  * k0p cdbs rocks! :D
[23:21] <geser> Laney: the archive admin will always sync the recent version from Debian
[23:22] <geser> this can be sometimes a problem a problem after FF where one just want the last fixes from Debian and gets a newly uploaded new upstream version
[23:22] <Laney> geser: Oh really? I can see why that would be a problem
[23:22] <Laney> This is why I thought a sync request was for a particular debian revision
[23:24] <emgent> hello there.
[23:25] <geser> Laney: the Debian archive contains only the version in unstable, testing and stable. If you wanted a specific version which isn't anymore in unstable you would need to fetch them snapshot.d.n
[23:25] <Laney> Especially as requesters/sponsors will only have tested the version at the time of request, you could end up causing more problems than the sync would have solved
[23:26] <geser> Laney: yes, it already happened once to me
[23:27] <geser> I wanted a version from testing fixing some bugs but got the a new upstream version from unstable and needed to file some UVF exceptions to get the whole stack in sync again
[23:27] <Laney> urgh
[23:37] <lilgies> hy someone can help me please ?
[23:38] <lilgies> I create my first package and I have an error of directory
[23:38] <lilgies> http://pastebin.com/m1ef254c6
[23:58] <kop__> people my deb package is creating python-support/site-packages/ with nothing inside. how I fix this warning?