[03:26] <DNS> hi:) can some1 please check whats wrong with that import → https://code.launchpad.net/~rbose-vcs-imports/emacs/trunk i can not see any error in the log or what could be wrong
[03:31] <wgrant> DNS: There's nothing wrong
[03:31] <wgrant> It's just importing gradually, 30000 revisions at a time
[03:31] <wgrant> Rather than trying to convert potentially hundreds of thousands or millions of revisions at once
[03:32] <DNS> but there are no files after "job is finished"?
[03:34] <wgrant> They'll be available after the initial import is done, once the jobs start finishing completely (a green tick, rather than a grey partial success)
[03:36] <DNS> ah i think i understand now:)
[03:39] <DNS> wgrant: thx for the info
[03:39] <wgrant> np
[03:42] <DNS> wgrant: btw i filed a bug about 2 weeks ago not sure if you saw my reply: https://bugs.launchpad.net/launchpad/+bug/1078172 the mc packages for example are from 2011-07-23, so i wonder if that is related to bug https://bugs.launchpad.net/launchpad/+bug/1071562
[03:44] <StevenK> It takes two weeks for binaries to fully expire out
[03:45] <DNS> but those are deleted in 2011?
[03:45] <DNS> and still shown?
[03:46] <DNS> i tried to delete them again thats why a new date is shown
[03:53] <DNS> ok sorry im confused, it seems those files werent deleted in 2011 but should be more than 2 weeks ago now :x
[04:00] <DNS> and https://launchpad.net/~dns/+archive/sound/+delete-packages?field.name_filter=gmidi&field.status_filter=superseded&field.series_filter= says it had a "Removal requested on 2012-03-03." so i wonder a bit
[04:00] <DNS> why this is still shown
[04:13] <wgrant> DNS: Things will be shown there until their files are actually removed, which most often happens if there are binaries left over (in which case you'll need to redelete), or if the source is published in another series too
[04:21] <DNS> wgrant: ok, thx again for info :)
[05:18] <ebergen> hooray for the ability to change a username
[06:04] <profzoom> I'm trying to request a merge of a branch.  The documentation says there should be a "Propose for merging into another branch" link on the branch page, but I can't find it anywhere.  Could anyone point me in the right direction?
[06:06] <wgrant> profzoom: Which page are you looking at?
[06:10] <profzoom> https://code.launchpad.net/~profzoom/+junk/wmaker
[06:10] <profzoom> I'm trying to request that it be merged into the wmaker package
[06:32] <wgrant> profzoom: Ah, +junk branches aren't related to a project or package, so you can't propose them for merging. You might want to push to eg. lp:~profzoom/ubuntu/quantal/wmaker/bug-1079925 instead.
[06:32] <wgrant> That way it will be mergable into other wmaker branches
[10:07] <shadeslayer> would it be possible for someone to rescore a small build for me? it's a 5 minute build and I'll have to wait an hour before it gets built
[10:07] <shadeslayer> kind of blocking my work :P
[10:08] <shadeslayer> https://launchpad.net/~netrunner-os/+archive/build/+build/4018538
[10:11] <czajkowski> an hour isn't that bad compared to others.
[10:11] <czajkowski> but will see
[10:17] <shadeslayer> czajkowski: thanks :)
[10:21] <czajkowski> StevenK: could you help out please with this ppa increase
[10:21] <czajkowski> I've tried to bump the score but nothing changed.
[10:21] <StevenK> It didn't work, I've done so
[10:22] <czajkowski> StevenK: cheers
[10:31] <shadeslayer> StevenK: czajkowski thanks alot!
[12:18] <Laney> https://launchpadlibrarian.net/124313309/buildlog_ubuntu-raring-i386.libubuntuone_4.0.0-0ubuntu2%7Eubuntu13.04.1_FAILEDTOBUILD.txt.gz
[12:18] <Laney> sad PPA buildd?
[12:30] <geser> "Unrecognized character \x06 at /home/buildd/.sbuildrc line 1." nice error
[14:33] <oerdnj> hi, akhlut builds are broken, do you already know it or should I report it somewhere?
[14:37] <oerdnj> says: Unrecognized character \x06 at /home/buildd/.sbuildrc line 1.
[14:44] <czajkowski> oerdnj: we know
[14:44] <oerdnj> czajkowski: ok, cool, goot to know. no need to report bug then... thanks for the answer
[17:14] <vankooch> Hi, I've uploaded a package to launchpad… but I've problems.. to get it build there… it builds correct on i386 but does fail on amd64. Locally I only have a amd64, and it builds there without any problems on a clean vm and on my dev machine. A friend also tried to build it locally on his amd64 machine without any problems. All have been tested on 12.04. Can someone please help me?
[17:14] <vankooch> that is the log: https://launchpadlibrarian.net/124266893/buildlog_ubuntu-precise-amd64.yate_4.2.1-ubuntu1-sico1~precise_FAILEDTOBUILD.txt.gz
[22:46] <xnox> launchpad has an interesting interpretation of release milestones
[22:46] <xnox> https://launchpad.net/procenv/+series
[22:48] <wgrant> xnox: What do you mean? Those were manually created by the project maintainer
[22:48] <xnox> wgrant: sure, but the ordering is intersting it's neither: numeric, alphabetic, chronological
[22:49] <xnox> wgrant: on the graph.
[22:49] <wgrant> It's going to be a little confused by the v being added in some of the milestone names
[22:49] <wgrant> I've never seen a project do that before
[22:49] <xnox> wgrant: the latest releases for the trunk paragraph below is correct (reverse chronological?!)
[22:50] <xnox> wgrant: sure. it's peculiar =) but the project is FTBFS across 12 architectures on debian and each 'release' tried to fix some of them to uncover more problems.
[22:51] <wgrant> Sure, but that doesn't explain why the version scheme grew a 'v' at the start recently :)
[22:51] <wgrant> Changing that half way through is likely to confuse things, so I can't really blame LP for beings somewhat confused.
[22:57] <xnox> wgrant: do you want this bug of questionable value, or will you remember this as an omg "funny things launchpad users do" =)))))
[22:57] <wgrant> We have enough bugs already, but if you really want to file it you can
[22:57] <wgrant> I'd suggest just making the milestone naming consistent, though!
[22:58] <maxb> Perhaps the bug should be "LP should document how it handles milestone ordering on the milestone creation form"