[04:23] <elopio> hello.
[04:24] <elopio> anyone around to help me with a simple debian bug?
[04:25] <elopio> tumbleweed: ping.
[07:00] <dholbach> good morning
[07:07] <Rhonda> elopio: If you would describe your issue I could have answered now - instead I have to ask: what problem do you have? :)
[13:37] <FlowRiser> Hey all :)
[13:37] <FlowRiser> How can I test a greeter using lightdm ?
[13:44] <exodus> Hello FlowRiser, here are two links about the subject:
[13:44] <exodus> http://www.mattfischer.com/blog/?p=5
[13:44] <FlowRiser> exodus, thanks :D
[13:45] <exodus> FlowRiser, you want to edit the lightdm.conf
[13:45] <FlowRiser> oh, i see; then put the name of my preferred greeter
[13:45] <FlowRiser> thanks :)
[13:46] <exodus> FlowRiser, exactly, the blog post shows you how, but if you're not up for the read, check /etc/lightdm/lightdm.conf
[14:47] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek last day starting in 13 minutes in #ubuntu-classroom
[14:53] <elopio> Rhonda: I know :) But I don't want an answer, I would like somebody to help me for around ten minutes sending my first patch to debian.
[14:53] <elopio> anyone interested in giving me a hand?
[14:54] <tumbleweed> there are people here who will help you
[14:55] <tumbleweed> !ask | elopio
[14:55] <tumbleweed> where are you stuck?
[14:56] <tumbleweed> I know it seems rude to just ask, but it really works best when you aren't relying on  one person to help you, but rather everyone who is around
[14:58] <elopio> tumbleweed: I attended your class and dholbach's. Now I want to fix this:
[14:58] <elopio> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682011
[14:58] <elopio> tumbleweed: I did quilt edit and refresh as you mentioned, with the fix.
[14:58] <elopio> I tried to debuild, and it failed. And I don't know what to do next. Let me get you the error.
[14:58] <tumbleweed> elopio: ok, quilt isn't relevant here, because it's a change to the debian packaging
[14:58] <tumbleweed> I actually don't think there's anything that needs to be done
[14:58] <tumbleweed> that bug report contains a good "verbal patch"
[14:58] <elopio> tumbleweed: hum, I know. But I filed it like a month ago, and hasn't been fixed.
[14:58] <tumbleweed> debian is currently in feature freeze, so minor things like that are not likely to get much attention until wheezy releases
[14:58] <tumbleweed> even if it wasn't in the freeze, that's just something one would normally roll into the next upload. Not something that would be fixed on its own
[14:58] <elopio> tumbleweed: and I wanted to use it to learn how to send the patch to debian. I still don't understand the workflow.
[14:59] <tumbleweed> ok, if you want to generate a patch: modify the source, add a changelog entry, debuild -S, and debdiff
[15:00] <elopio> tumbleweed: and then send it by mail? Is there no way for me to propose a merge like in launchpad?
[15:01] <tumbleweed> elopio: you send it by email to 682011@bugs.debian.org
[15:02] <tumbleweed> if you look at the PTS page for sikuli, you'll see that teh packaging is in git
[15:02] <tumbleweed> but really, for almost everything, just e-mailing a patch or two is the easiest
[15:03] <elopio> ok, I get it. And this is really easy, the patch that way makes no sense. I better look for a different one.
[15:04] <elopio> tumbleweed: ok, a question. When I did pull-lp-source sikuli-ide I got 4 things.
[15:04] <elopio> a folder, a .tar.gz, a .dsc and a .build.
[15:04] <elopio> can you explain to me what are they?
[15:05] <elopio> oh, and an .orig.tar.gz
[15:05] <tumbleweed> elopio: http://wiki.debian.org/IntroDebianPackaging covers a lot of this
[15:06] <elopio> all right, thanks.
[15:09] <elopio> other question. Should I use pbuilder to create a sid chroot, right?
[15:09] <tumbleweed> or sbuild. personally, I use sbuild
[15:22] <elopio> good. Thanks. I'll be playing around and come back with more questions :)
[15:48] <TheLordOfTime> anyone knokw where i can find the SRU queue, for items pending review for an SRU?  or should i just poke someone on the SRU team and ask?
[15:48] <micahg> TheLordOfTime: in proposed or not accepted yet?
[15:49] <tumbleweed> https://launchpad.net/ubuntu/precise/+queue?queue_state=1 are the things uploaded to precise and not accepted by SRU team yet
[15:49] <TheLordOfTime> micahg:  in proposed, last i heard, according to the sponsor for that package (its in Main, but...)
[15:49] <TheLordOfTime> (was awaiting SRU team approval last i checked, which was 3 days ago)
[15:50] <tumbleweed> http://people.canonical.com/~ubuntu-archive/pending-sru.html once they are accepted
[15:50]  * micahg is confused, but now you have both links :)
[15:51] <TheLordOfTime> micahg:  i don't have upload rights.  The sponsor who I worked with uploaded the changed package to precise-proposed, and i was curious whether the SRU team had accepted it yet or not :P
[15:51] <TheLordOfTime> if its still in proposed, its not accepted :P
[15:52] <tumbleweed> TheLordOfTime: no
[15:52] <tumbleweed> TheLordOfTime: uplaods to precise-proposed have to be accepted by the SRU team
[15:52] <TheLordOfTime> tumbleweed:  really?
[15:52] <tumbleweed> before they are published in precise-proposed
[15:52] <tumbleweed> then they have to age for a week and be verified, before being copied to -updates
[15:53] <TheLordOfTime> ah, wait its in the upload queue
[15:53]  * TheLordOfTime misread
[15:54] <TheLordOfTime> tbh, i'd be stabbing the SRU team left and right if it weren't for the PPA i published the fix for the package to... the package has a regression that popped up between oneiric and precise, which prevents php5 from reporting errors back to the webserver (at least in nginx), and fixes an (obscure, but possible to encounter) issue of a segfault.
[15:54] <TheLordOfTime> i just needed the links, though, thanks.
[15:55] <tumbleweed> they've just had a point release, we can give them some slack :)
[15:55] <TheLordOfTime> tumbleweed:  *shrugs* a medium priority and a high priority bug sometimes pique my interest.  especially when they affect my production environments :P
[17:41]  * Laney slides a glance towards iulian
[17:42]  * Laney wonders if he might have a few spare minutes to upload some cheeky rebuilds tonight
[17:42]  * Laney will be out
[17:42] <Laney> starting now. ttyl!
[17:45] <highvoltage> byelaney
[19:05] <iulian> Laney: Certainly.
[21:46] <TheLordOfTime> anyone able to help me in figuring out why debuild -S is ignoring the orig.tar.gz in a given package build?
[21:52] <TheLordOfTime> hello?
[21:57] <Bachstelze> TheLordOfTime: most probably the filename doesn't match the package name
[21:58] <TheLordOfTime> Bachstelze:  unlikely, the .orig.tar.gz was built with dh_make --createorig
[21:58] <TheLordOfTime> it literally shows right there
[21:58] <TheLordOfTime> 4.0K drwxrwxr-x 4 teward teward 4.0K Aug 30 17:56 formatjunkie-1.04/
[21:58] <TheLordOfTime> 148K -rw-rw-r-- 1 teward teward 145K Aug 30 17:56 formatjunkie_1.04.orig.tar.gz
[21:58] <TheLordOfTime> :/
[22:00] <TheLordOfTime> Bachstelze:  this is the debuild -S output: http://paste.ubuntu.com/1176749/
[22:01] <Bachstelze> uh, what exactly do you mean by "ignoring"?
[22:01] <TheLordOfTime> oh wait hang on
[22:01]  * TheLordOfTime tests something
[22:02] <TheLordOfTime> ah, figured out why
[22:02] <TheLordOfTime> somehow, it generated a changelog that had other data in it o.O
[22:03] <TheLordOfTime> Bachstelze:  by "ignore" i meant that it was omitting the .orig.tar.gz file as part of the source package
[22:03] <TheLordOfTime> so LP PPAs would autoreject
[22:03] <Bachstelze> that's normal, you have to use debuild -S -sa
[22:04] <Bachstelze> to include the source in the upload
[22:04] <TheLordOfTime> i think i already had that defined...
[22:04] <TheLordOfTime> ... somewhere *checks*
[22:04] <Bachstelze> your debuild output says you don't
[22:04] <TheLordOfTime> *shrugs*
[22:05] <TheLordOfTime> i just rebuilt it and it built now *shrugs*
[22:05] <Bachstelze> the default is to not include it because normally the source is already up
[22:05] <TheLordOfTime> is there a way i can perpetually tell it to always include the source tarball?
[22:05] <Bachstelze> no
[22:05] <TheLordOfTime> Bachstelze:  even if that's the case, PPAs want that anyways, so...
[22:05] <Bachstelze> er
[22:05] <Bachstelze> probably but it would be a bad idea <= better phrasing
[22:06] <TheLordOfTime> there's no harm, though, if in ~/.devscripts i have DEBUILD_DPKG_BUILDPACKAGE_OPTS=-kKEYID
[22:06] <TheLordOfTime> right?
[22:07]  * TheLordOfTime has about 7 different GPG keys on this system
[22:07] <TheLordOfTime> (not all are for Ubuntu :P)
[22:07] <Bachstelze> ase don the same source tarball)
[22:08] <Bachstelze> ugh
[22:08] <Bachstelze> TheLordOfTime: that's fine, you can even put -sa ther eif you want, but you will get a package rejected if you want to upload a new version of the same package (ie. based on the same source tarball)
[22:08] <Bachstelze> the server will not let you upload the same source tarball twice (hence why it' snot uploaded by default, you only do it once)
[22:10] <TheLordOfTime> Bachstelze:  then why was it not recognizing this as a new package i wonder...
[22:10] <TheLordOfTime> *shrugs*
[22:12] <Bachstelze> TheLordOfTime: how would it do that? it would have to probe the archive to see if the tarball is already up there, that would be unconvenient
[22:12] <Bachstelze> for example then you can't build packages while offline
[22:12] <TheLordOfTime> this convo's going nowhere...
[22:12]  * TheLordOfTime returns to checking whether the upload was accepted
[22:13] <TheLordOfTime> Bachstelze:  i think my system was just having a hissy fit
[22:13] <TheLordOfTime> it started doing that a bit after a small power surge about an hour ago