[00:03] <elmo> launchpad is going down at 00:20 UTC for 15 minutes for emergency maintenance
[00:06] <geser> steveire: version is ok now, it takes some time after a upload till it appears in the build queue
[00:07] <geser> steveire: iirc new uploads are added to the build queue every twenty minutes (:00, :20, :40)
[00:07] <steveire> OK, so I'll check back tomorrow. Thanks for the help
[00:09] <geser> steveire: you got a mail that you uploaded was accepted?
[00:13] <steveire> geser: Yes
[00:14] <geser> good, so either have tomorrow build .debs or mails about a build failure
=== elmo changed the topic of #launchpad to: LAUNCHPAD DOWN FOR MAINTENANCE - due back 00:35 UTC || https://launchpad.net/ || Next meeting (all welcome): Thu 07 Feb 2008, 1800UTC #launchpad-meeting | Help: https://help.launchpad.net | Questions: https://answers.launchpad.net/launchpad | Channel logs: http://irclogs.ubuntu.com
=== kiko-afk is now known as kiko-zzz
[00:24] <steveire> I'm getting some emails about failure I think (State: Chroot problem)
[00:26] <steveire> I guess it's due to lp being down as elmo said
=== elmo changed the topic of #launchpad to: https://launchpad.net/ || Next meeting (all welcome): Thu 07 Feb 2008, 1800UTC #launchpad-meeting | Help: https://help.launchpad.net | Questions: https://answers.launchpad.net/launchpad | Channel logs: http://irclogs.ubuntu.com
[00:33] <steveire> elmo: Do I restart my build somehow, or is it automatic?
[00:33] <elmo> steveire: I'm sorry, I'm just a reboot monkey - if you're having problems with your build, you might want to file a question about it in the answer tracker
[00:34] <steveire> OK
[00:34] <elmo> steveire: it's very unlikely to have been affected by the emergency maintenance I was doing, FWIW
[00:34] <poolie> steveire, i would guess it would be detected as dead and restarted
[00:34] <poolie> but, you'd have to check
[00:34] <Hobbsee> if it's a chroot problem, the wise idea would be for someone to check the chroots, and see why it die
[00:34] <Hobbsee> d
[00:34] <emgent> i'm in gutsy
[00:35] <emgent> ops
[00:35] <emgent> worng window
[00:35] <emgent> s/worng/wrong/
[00:36] <steveire> Hobbsee: http://rafb.net/p/Q5SSN692.html <<< It means nothing to me.
[00:36] <steveire> Hobbsee: You're a gearhead, right? Do you build kde from trunk on kubuntu?
[00:39] <Hobbsee> steveire: not usually.  i occasionally build parts of it
[00:40] <steveire> Hobbsee: OK. It's just that kubuntu doesn't tend to keep up with the build deps of it. I'm wondering how kde devs on kubuntu do it.
[00:40] <Hobbsee> steveire: which package, and which arch?
[00:40]  * Hobbsee is a ubuntu/kubuntu dev, not a kde dev
[00:40] <Hobbsee> er, which package, and which ppa?
[00:41] <Hobbsee> oh, xine-lib
[00:41] <steveire> libxine and my ppa https://launchpad.net/~steveire/+archive
[00:41]  * Hobbsee retries the build
[00:41] <steveire> Hobbsee: You can rekick the build on the lp servers?
[00:42] <Hobbsee> yeah
[00:42] <Hobbsee> you can too, for ppa
[00:43] <steveire> Really? How?
[00:43] <Hobbsee> click the build, hit retry build
[00:44] <steveire> same chroot issue
[00:45] <Hobbsee> i think this is a launchpad bug.
[00:45] <steveire> http://ppa.launchpad.net/steveire/ubuntu really doesn't exist
[00:46] <Hobbsee> exactly
[00:46] <Hobbsee> Fujitsu: can you fix it?
[00:48] <Hobbsee> he's idling.  slacker.
[00:49] <mtaylor> statik: bah. 
[00:50] <mtaylor> statik: you do stuff with buildbot from time to time, right? 
[00:54] <steveire> mtaylor: You having the same issue?
[00:55] <mtaylor> steveire: I don't think so... sorry
[00:55] <mtaylor> steveire: I'm actually screwing around the the buildbot software, not to be confusted with launchpad's build stuff
[00:56] <mtaylor> steveire: but let me read the scroll-back
[00:56] <Hobbsee> mtaylor: (it's not)
[00:59] <mtaylor> Hobbsee: I agree
[01:49] <persia> Hello.  I've not been getting "Accepted" or "NEW" emails from Soyuz so far this morning.  I know there was an outage earlier, but I thought it was addressed (as the web interface seems to be working properly again).  Is there still something pending?  Should I expect my uploads to be processed later?
=== jamesh__ is now known as jamesh
[03:04] <emgent> ...
[03:40] <emgent> dermoth, STOP!
=== stub changed the topic of #launchpad to: https://launchpad.net/ || Next meeting (all welcome): Thu 14 Feb 2008, 1800UTC #launchpad-meeting | Help: https://help.launchpad.net | Questions: https://answers.launchpad.net/launchpad | Channel logs: http://irclogs.ubuntu.com
[04:04] <emgent> thanks statik 
[04:04] <emgent> stub
[04:04] <emgent> :)
=== asac_ is now known as asac
[04:56] <method> Does PPA sometimes take an incredibly long time after building to transfer the debs over, or do they tend to get lost?
[04:59] <jamesh> I guess he didn't want an answer ...
=== doko_ is now known as doko
[07:49] <carlos> morning
=== rraphink is now known as raphink
[11:16] <geser> can "dpkg-genchanges: warning: missing Section for binary package libaspectr all; using '-'" cause a "Failed to upload" error after a build?
=== salgado is now known as salgado-brb
=== salgado-brb is now known as salgado
=== \sh_away is now known as \sh
[11:53] <Hobbsee> cprov: found a bug, btw.
[11:54] <cprov> Hobbsee: hi.
[11:54] <cprov> Hobbsee: which one ?
[11:54] <Hobbsee> cprov: do i need to proxy-file it, or actually use effort and properly file it?
[11:54] <Hobbsee> cprov: the chroot waits for hte first package on any ppa
[11:55] <Hobbsee> cprov: as in:  user activates ppa, user uploads package, package gets stuck in chroot problem, enosolution, go bug cprov.
[11:56] <cprov> Hobbsee: chroot wait have to be retried manually, atm
[11:56] <Hobbsee> cprov: sure, but the problem isn't that the chroot waits need to be retried, it's that they occur in the first place.
[11:57] <Hobbsee> cprov: it's because ppa is attempting to check the packages in the new person's ppa, which doesn't exist, so gets back a 404, and dies with a chroot error.
[11:59] <cprov> Hobbsee: fine, but we do recognized missing/broken archive as chroot-wait. File a bug about this situation, I will discuss a solution with Adam.
[12:00] <Hobbsee> cprov: right, OK.  i assume that either a)  you should just create an empty packages.gz file when the ppa gets activated (probably the better solution), or b) special case the ppa line check.
[12:01] <cprov> Hobbsee: it's a race condition between publication & build, we will sort it out.
[12:01] <Hobbsee> ok
[12:11] <geser> cprov: is the error of "Failed to upload" somewhere visible? there are some package which "failed to upload" after build and I would like to know why
[12:13] <cprov> Hobbsee: yes, they are visible in the +builds interface. But the log of the failure is only sent in the build-failure-notification.
[12:14] <cprov> Hobbsee: https://edge.launchpad.net/ubuntu/+builds?build_text=&build_state=uploadfail
[12:16] <geser> cprov: I guess you mean me and not Hobbsee
[12:17] <cprov> geser: err, exactly, sorry. 
[12:17] <geser> cprov: can "dpkg-genchanges: warning: missing Section for binary package libaspectr all; using '-'" cause a "Failed to upload" error?
[12:17] <cprov> geser: is it in you PPA or in ubuntu ?
[12:17] <geser> in Ubuntu
[12:18] <cprov> geser: yes, it does
[12:18] <geser> https://edge.launchpad.net/ubuntu/+source/libaspectr/0.3.5-3ubuntu1/+build/478768
[12:19] <cprov> 22:38:37 WARNING Upload was rejected:
[12:19] <cprov> 22:38:37 WARNING        libaspectr_0.3.5-3ubuntu1_all.deb control file lists section as main/ but changes file has main/misc.
[12:20] <geser> cprov: so the solution here is to fix the package (add a Section)?
[12:22] <cprov> geser: yes, because the soyuz changesfile parser will assume "misc", IIRC
[12:22] <elmo> cprov: soyuz should really be more lenient about section mismatches like that
[12:22] <cprov> geser: which will conflict with the 'empty' one set in the control file
[12:22] <elmo> cprov: esp. in ppa - all it does is cause user confusion
[12:24] <cprov> elmo: yes, I agree for the PPA context. Although we should keep the restriction to ubuntu primary archive, right ?
[12:26] <geser> cprov: is it worth to file a bug that the reason for "failed to upload" be public (e.g. attached to the build log) so interested persons can find out why (and not only the uploader)? right now I can only guess why a package failed to upload.
[12:27] <Hobbsee> geser: nwo that would destroy the fun of guessing why a closed-source project happened to break this time in particular.
[12:28] <geser> Hobbsee: no one told me that it is intended to train your sixth sense
[12:28] <Hobbsee> geser: training your sixth sense is useful.
[12:29] <Hobbsee> geser: one of the first points in your sixth sense training is to *realise* that such things are training your sixth sense.
=== mrevell is now known as mrevell-lunch
[12:37] <geser> cprov: can you lookup the reason for the failed to upload of doc-debian in hardy? https://edge.launchpad.net/ubuntu/+source/doc-debian/3.1.5ubuntu1/+build/502337
[12:42] <cprov> geser: 18:53:24 WARNING Upload was rejected:
[12:42] <cprov> 18:53:24 WARNING        Unable to identify file debian-faq.en.html.tar.gz (byhand) in changes.
=== kiko-zzz is now known as kiko
[12:46] <ubotu> New bug: #145319 in libvirt "[l10n] PO-template wrong imported " [Undecided,Won't fix] https://launchpad.net/bugs/145319
[12:52] <geser> cprov: what's the best way to fix this? aren't byhand entries from dpkg-distaddfile supported?
[12:53] <cprov> geser: not 'html.tar.gz' files
[13:00] <ubotu> New bug: #190906 in soyuz "Make the reason for "Failed to Upload" public" [Undecided,New] https://launchpad.net/bugs/190906
[13:02] <kiko> cprov, that bug is for a public log of failures, right?
[13:03] <cprov> kiko: sort of, failed-to-upload happens in upload-time, it slightly different than failed-to-build
[13:04] <kiko> who said failed-to-build?
[13:04] <kiko> I meant keeping a public log of upload processing failures
[13:05] <cprov> kiko: you said just 'failures' and it is assumed as 'failed-to-build'
[13:06] <cprov> kiko: yes, 'keeping public log of binary upload processing failures' (aka failed-to-upload)
[13:06] <kiko> not binary uploads
[13:06] <kiko> source uploads.
[13:07] <geser> kiko: e.g. https://edge.launchpad.net/ubuntu/hardy/+source/kpovmodeler-kde4/+builds all failed to upload after building but there is no public log why
[13:07] <cprov> kiko: uhm, no, we are talking about binaries.
[13:26] <ubotu> New bug: #190913 in launchpad "Distinguish between GNU GPL V2 and V3 licenses" [Medium,Confirmed] https://launchpad.net/bugs/190913
=== mrevell-lunch is now known as mrevell
[13:32] <jelmer> jamesh: ping
[13:32] <jamesh> jelmer: pong
[13:32] <jelmer> jamesh: I would like to migrate one of my projects to launchpad
[13:32] <jamesh> jelmer: cool.  What are you migrating from?
[13:32] <Hobbsee> mrevell: speaking again at the open week, i see :)
[13:33] <jelmer> jamesh: The bugs are currently in trac and would have to be migated
[13:33] <mrevell> hi Hobbsee - it's more than likely  Mr Cprov will lead that session, but I shall be there :)
[13:33] <jamesh> jelmer: okay.  That's one of the systems we haven't done a migration for, so I don't have a ready-made conversion script
[13:33] <Hobbsee> mrevell: ahhh
[13:34] <jamesh> jelmer: if you are willing to help with converting the bug data, I can give you information about what format I need the data in
[13:34] <Hobbsee> cprov: good luck!
[13:35] <jelmer> jamesh: ok
[13:35] <cprov> Hobbsee: normally I'd ask if really need it. However I already know the answer ('yes, i do'), so, thanks :)
[13:36] <Hobbsee> cprov: heh :)
[13:36] <cprov> Hobbsee: will you have time to attend, at least, one of them ?
[13:36] <Hobbsee> cprov: no helpers either, this time
[13:36] <Hobbsee> cprov: what for?
[13:37] <jamesh> jelmer: the way the importer is structured at the moment is to use an XML bug interchange file.  So it will just be necessary to covert your data to that format.
[13:37] <cprov> Hobbsee: dunno, curiosity ?
[13:37] <jamesh> what email should I send the details to?
[13:37] <jelmer> jamesh: jelmer@samba.org
=== cprov is now known as cprov-afk
[13:38] <Hobbsee> cprov: depends what it is.  if it's mostly a copy of a wiki page, then i can read that
[13:38] <Hobbsee> i may be at the friday one, if there's something pretty special in it
[13:38] <Hobbsee> it's fairly evil in local time
[13:38] <Hobbsee> as for the monday, i'll be on VAC.
[13:39] <Hobbsee> <gasp>
[13:41] <Hobbsee> cprov-afk: i...um....er....now, i guess it goes without saying that you *are* going to fix that chroot problem bug, if indeed it does affect all new ppa'ers, before you try to get more people using PPA? :)
[13:46] <cprov-afk> Hobbsee: don't get stuck on details, that bug will get fixed, independently of the number of people using PPAs. Did you file the bug, btw ?
[13:47] <jamesh> jelmer: sent.
[13:47] <jelmer> thanks
[13:47] <Hobbsee> cprov-afk: i haven't done so yet
=== cprov-afk is now known as cprov
[13:48] <jamesh> jelmer: if you have any questions, don't hesitate to ask
[14:03] <Hobbsee> cprov: ah, good.  if you give it back hours later, it apperas to work
[14:05] <cprov> Hobbsee: yes, if you wait the PPA to be published the first time (<= 20 minutes after the upload) and 'retry' the build it will be fine.
[14:06] <Hobbsee> cprov: that's even though the binaries are showing on the main page?
[14:06] <Hobbsee> er, *sources* are showing on the main page?
[14:07] <cprov> Hobbsee: when the source is presented as 'published'.
[14:07] <Hobbsee> cprov: blink
[14:08] <Hobbsee> cprov: so, since when does publishing take so long?
[14:08] <Hobbsee> like, 10 hours?
[14:10] <jelmer> jamesh: thanks, will do
[14:11] <ubotu> New bug: #190930 in soyuz "builds from new PPAs fail due to chrootwait" [Undecided,New] https://launchpad.net/bugs/190930
[14:11] <cprov> Hobbsee: it doesn't, sources will get published within 20 minutes, unless the scripts were not running.
[14:11] <Hobbsee> cprov: so the time listed on the ppa page is wrong (x hours ago?)
[14:12] <Hobbsee> and so why did it fail when i gave it back, even though i'm fairly sure the source was listed as publisehd at the time?
[14:12] <Hobbsee> or were the scripts not running today?
[14:13] <cprov> Hobbsee: PPA url
[14:13] <cprov> ?
[14:13] <Hobbsee> cprov: it's in the bug
[14:13] <elmo> Hobbsee: I forgot to re-enable cron after the LP downtime; it's probably that
[14:13]  * Hobbsee points ~8 lines up
[14:13] <Hobbsee> elmo: ahhhh, right.  OK then :)
=== Martinp24 is now known as Martinp23
[15:06] <ubotu> New bug: #190945 in launchpad "Join/leave mailing list from team page" [Undecided,New] https://launchpad.net/bugs/190945
=== kiko is now known as kiko-fud
[15:21] <ubotu> New bug: #190951 in launchpad "Allow team admins to propose their teams as members of another team" [Undecided,New] https://launchpad.net/bugs/190951
=== matsubara is now known as matsubara-lunch
[15:25] <ubotu> New bug: #190953 in launchpad "Simplify archive link on team page" [High,Confirmed] https://launchpad.net/bugs/190953
=== salgado is now known as salgado-lunch
=== fabbione is now known as thegodfather
=== kiko-fud is now known as kiko
=== salgado-lunch is now known as salgado
[16:24] <ubotu> New bug: #190970 in soyuz "Filter PPA by series" [Undecided,New] https://launchpad.net/bugs/190970
[16:24] <ubotu> New bug: #190972 in launchpad "Once a day email about pending mailing lists" [Undecided,New] https://launchpad.net/bugs/190972
[16:24] <ubotu> New bug: #190974 in launchpad "Rename mailing-list-beta-testers after the feature is released" [Undecided,New] https://launchpad.net/bugs/190974
[16:40] <ubotu> New bug: #190984 in soyuz "PPA page loads very slowly" [Undecided,New] https://launchpad.net/bugs/190984
=== \sh is now known as \sh_away
=== salgado_ is now known as salgado
=== matsubara-lunch is now known as matsubara
=== mrevell is now known as mrevell-dinner
=== Ubulette_ is now known as Ubulette
[19:18] <goobsoft> In python programs, are absolute paths to images usually hard coded into the source?
[19:19] <kiko> rarely in good python programs
[19:19] <LarstiQ> it's bad practice in any program
[19:20] <goobsoft> I come from windows where you could do relative paths like images/my.png, but in debian, the programs are usually not all self contained in one folder.  How is this done where the program is in a completely separate directory from the images?
[19:22] <goobsoft> Also in windows, it's assumed that the shortcut can start the program with a current working directory of the installation root.. but that's not the case in debian.
[19:40] <hexmode> goobsoft: often there is some sort of configuration file that gives the locations
[19:40] <hexmode> and/or paths are set up at compile time
[19:40] <hexmode> (e.g. configure)
=== salgado is now known as salgado-brb
[19:45] <goobsoft> ok thanks hex
[19:45] <goobsoft> I gotta run
=== salgado-brb is now known as salgado
=== \sh_away is now known as \sh
=== Gwaihir_ is now known as Gwaihir
=== \sh is now known as \sh_away
=== mrevell-dinner is now known as mrevell
=== kiko is now known as kiko-afk
[23:20] <ubotu> New bug: #191111 in launchpad "no way to list related teams/lists" [Undecided,New] https://launchpad.net/bugs/191111
[23:22] <soren> cprov: ping?
=== jamesh__ is now known as jamesh