[00:14] <Ubulette> bouhh, internal errors with codebrowse
[02:12] <poolie> thumper, re bug 49469
[02:12] <ubotu> Launchpad bug 49469 in launchpad-bazaar "Unable to register upstream release as already using Bazaar" [High,Fix released] https://launchpad.net/bugs/49469
[02:12] <poolie> i think it's still open, as a usabliity bug
[02:12] <poolie> indeed that might have been what hypatia was originally reporting...
[02:12] <thumper> yes and no
[02:13] <thumper> What I'd suggest is to file a new bug with a better title and description
[02:13] <thumper> as what the actual bug report says is incorrect
[02:13] <thumper> we could link it back
[02:13] <thumper> poolie: can we have a voice call this afternoon, there are some things I need to talk through with you
[02:14] <poolie> i was going to retitle it
[02:14] <poolie> so mary doesn't lose it, etc
[02:14] <thumper> ok
[02:14] <thumper> we could do that
[02:14] <thumper> Ubulette: we know about them, and they should be fixed with the 1.1.12 rollout next week
[02:14] <Ubulette> ?
[02:15] <thumper> Ubulette: the internal errors with codebrowse
[02:15] <Ubulette> oh, ok. I assumed you did
[02:15] <thumper> :)
[02:15] <poolie> thumper, i agree we should have a call -- irc our meeting with mark is tomorrow but you won't be there?
[02:15] <thumper> right
[04:30]  * lamont wonders why the hppa buildds haven't launched anything in 4 hours...
[04:32] <Fujitsu> lamont: Because queue-builder probably wants you to kick it. Hard.
[04:35] <lamont> Fujitsu: I can't kick queue builder
[04:35] <lamont> slavescanner is more likely, no?
[04:36] <Fujitsu> Hm, probably.
[04:36] <Fujitsu> queue-builder isn't quite so evil now it doesn't block slavescanner.
[04:37] <Fujitsu> Everything is surprisingly idle.
[04:37] <Fujitsu> Oh, not any more.
[04:38] <Fujitsu> That can't be right... On one load of the page, only one buildd was active.
[04:39] <lamont> hppa's last build ended 4 hours ago.  1600 items in the queue
[04:39] <Fujitsu> Yeah.
[04:40] <Fujitsu> Is slave-scanner known to single archs out? I wouldn't have thought it would be possible for it to do that sort of thing...
[04:55] <Fujitsu> lamont: Look at the latest build in kohnen's queue. Something is seriously screwed.
[04:55] <Fujitsu> s/queue/history/
[05:01] <lamont> that does look, um, interesting
[05:01] <Fujitsu> Yeah.
[05:02] <lamont> marked kohnen manual, I'll turn it on in a bit and see if it self-reproduces
[05:02] <Fujitsu> Rather more mysterious even that the Currently Building ones which look to be otherwise Pending.
[05:03] <lamont> I see nothing in 'currently building' for hppa
[05:03] <Fujitsu> There aren't any.
[05:03] <lamont> I do see that something keeps bumping priority on some packages that I threw down in the cellar back up to where queue-mangler thinks they belong
[05:03] <Fujitsu> But over the past couple of weeks there have been a number of builds with are listed as currently building, but have no builder, etc.
[05:04] <lamont> neato
[05:04] <Fujitsu> lamont: Right, there's a bug on that.
[05:04] <lamont> ah, so it's not just me.  cool
[05:04] <Fujitsu> queue-builder takes so long to run that it sometimes reads in build scores, thinks for a while, and writes out the recalculated ones, overwriting the manual change that was made in the meantime.
[05:27] <Fujitsu> lamont: kohnen seems markedly unimpressed.
[05:29] <Fujitsu> I note that sejong was doing a similar thing several hours ago.
[05:34]  * Fujitsu wonders why the lpia security buildd is concordia.
[06:42] <poolie_> hi
[06:43] <poolie> why doesn't a search for "setup.py" (no quotes) in launchpad find a bug with that word in the title?
[07:45] <gspr> I filed a question for my PPA to be cleared out. Someone replied and said it had been done. All the packages on the list are gone, but the files still remain, preventing me to upload new versions. What can I do?
[09:26] <mrevell> Morning Launchpadders!
[09:37] <jml> Good morning Mr Revell
[09:43] <soren> Hi, guys. I'm having trouble checking out bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/debian-installer/ubuntu .
[09:43] <soren> I get bzr: ERROR: Repository KnitPackRepository( blahblha) ) is not compatible with repository RemoteRepository(bzr+ssh://bazaar.launchpad.net/%7Eubuntu-core-dev/debian-installer/ubuntu/.bzr/)
[09:44] <soren> I've no clue what that is all about.
[09:48] <mrevell> mwhudson or jml: Are you able to help soren?
[09:48] <jml> soren: hi
[09:49] <jml> soren: what version of bazaar are you using locally?
[09:49] <mwhudson> you are trying to pull a branch from a dirstate repo into a dirstate-with-subtrees repo, or something like that i expect
[09:49] <mwhudson> (not a very clear message at all)
[09:50] <jml> mwhudson: do you know if there's a bug filed about making that message clearer?
[09:50] <mwhudson> jml: i do not
[09:50] <soren> jml: 1.0~rc2-2
[09:50] <mwhudson> there was some discussion on the list
[09:51] <soren> mwhudson: I'm not sure what that means?
[09:52] <mwhudson> soren: are you pulling the branch into a shared repo?
[09:52] <soren> mwhudson: Nope. Just a plain old "bzr co bzr+ssh://blah".
[09:52] <soren> mwhudson: I can do it anywhere on my filesystem.
[09:52] <soren> mwhudson: Well... No.
[09:52]  * jml tries branches
[09:52] <soren> I *can't*. That's the problem, you see :)
[09:52] <jml> s/es/branching/
[09:53] <mwhudson> ooooooooh
[09:53] <mwhudson> try sftp or http :(
[09:54] <soren> mwhudson: That works. Hm... will this affect all branches on Launchpad?
[09:54] <jml> I wish we had access to some logfiles.
[09:54] <soren> mwhudson: I checked something out yesterday without any problems.
[09:54] <jml> soren: I certainly hope not!
[09:54] <soren> jml: Could you shed smidgeon of light on the issue? I've no clue what the problem is.
[09:55] <mwhudson> there's a bug where initial branches over bzr+ssh always create local branches in the default format
[09:55] <mwhudson> which are sometimes incompatible with what you're about to bring over the wire
[09:55] <mwhudson> i think it might be fixed in 1.0
[09:55] <mwhudson> (hope so, anyway)
[09:55] <soren> Workaround?
[09:55] <jml> soren: sftp://
[09:55] <ubotu> New bug: #176085 in malone "subscribing someone should send a notification email" [Undecided,New] https://launchpad.net/bugs/176085
[09:55] <soren> jml: erk..
[09:55] <jml> soren: yeah
[09:56] <jml> soren: upgrading to 1.0rc3 might be worth a shot
[09:56] <soren> jml: Could I check out just a single revision using sftp, switch the parent branch url to bzr+ssh and pull the rest that way?
[09:57] <soren> That might speed things up a bit.
[09:57]  * soren stops asking silly questions and just tries it
[09:59] <mwhudson> soren: i think that will work
[10:00] <mwhudson> hey look, this poolie_ guy might know about the status of this bug
[10:00] <poolie_> hi
[10:00] <poolie_> which bug?
[10:00] <poolie_> i'm kinda done for today...
[10:00] <soren> 10:55:05 < ~mwhudson> there's a bug where initial branches over bzr+ssh always create local branches in the default format
[10:00] <soren> More context?
[10:01] <poolie_> yes, i know of it
[10:01] <poolie_> it's biting you?
[10:01] <soren> Yes. Trying to "bzr co bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/debian-installer/ubuntu" I get:
[10:02] <soren> bzr: ERROR: Repository KnitPackRepository( blahblha) ) is not compatible with repository  RemoteRepository(bzr+ssh://bazaar.launchpad.net/%7Eubuntu-core-dev/debian-installer/ubuntu/.bzr/)
[10:02] <mwhudson> poolie_: is there a bug report in launchpad?
[10:02] <mwhudson> i'm sure i found it, but now my searching is totally failing
[10:02] <poolie_> mwhudson, there are thousands! :-)
[10:02] <soren> mwhudson: Just pulling that one revision takes ages, too.
[10:02] <mwhudson> har, har
[10:03] <poolie_> bug 173002
[10:03] <ubotu> Launchpad bug 173002 in bzr "Branching from hpss doesn't preserve non-repository formats" [Medium,New] https://launchpad.net/bugs/173002
[10:03] <poolie_> i'll bump it up
[10:03] <poolie_> hm
[10:03] <poolie_> actually, this one was probably bug 164626
[10:03] <ubotu> Launchpad bug 164626 in bzr "branching from hpss doesn't preserve repository format" [High,Fix released] https://launchpad.net/bugs/164626
[10:05] <mwhudson> ah, it was fix released
[10:39] <jml> soren: I successfully branched from that one.
[10:49] <soren> jml: Oh? Newer bzr version or something?
[10:50] <jml> Bazaar (bzr) 1.0.0.candidate.1
[10:50] <jml> older, it seems
[10:50] <jml> (although pastebin the output of 'bzr version' to make sure)
[10:56] <ubotu> New bug: #176100 in launchpad "ppa page shows hardy even though there are no hardy packages available" [Undecided,New] https://launchpad.net/bugs/176100
[10:57] <soren> jml: http://paste.ubuntu-nl.org/48068/
[10:58] <jml> *awesome*
[10:59] <mwhudson> uh oh
[10:59] <jml> mwhudson: worth checking with the current 1.0 branch I reckon :)
[11:00]  * jml retires
[11:04]  * mwhudson tries
[11:47] <zerok> hi :)
[13:05] <_polto_> hello
[13:06] <_polto_> how can users find on my PPA my signature to add it to Synaptic pls?
[13:07] <Hobbsee> _polto_: you can't, yet.
[13:08] <_polto_> oh :(
[13:08] <_polto_> so users have to install unsigned package ?
[13:08] <_polto_> i mean whey can't verify ..
[13:08] <Hobbsee> yes, at the moment.
[13:38] <encompass> Things are getting really busy at launchpad.net/memaker is it possible to get this program a mailing list?  Our plan is to have this program ready for the release of ubuntu hardy.  It is hoped to be an integrated part of both the install and user preferences
[13:39] <mrevell> encompass: That's a service we may offer in the future but I'm afraid that, right now, you can't run a mailing list through Launchpad.
[13:40] <lamont> Fujitsu: because concordia is the machine we were given for security builds...
[13:41] <encompass> mrevell: dang... do you know of a common alternative?
[13:43] <mrevell> encompass: Have you come across Mailman before? It's a mailing list management system with web interface. It's easy to setup and run on your own server.
[13:43] <encompass> is it THAT easy?  hehe, I can give it a shot
[13:43] <encompass> yeah, I have heard of it
[13:44] <mrevell> encompass: It is pretty easy. I'm not a developer or a sysadmin and I managed to run a Mailman instance :)
[14:03] <kiko> mthaddon!
[14:03] <mthaddon> hi
[14:04] <SteveA> aha!
[14:05] <Hobbsee> scary.  it talks!
[14:05] <kiko> SteveA, -> #launchpad-meeting
[14:38] <kiko> mrevell, do note that we have mailing lists in beta this coming week, no?
[14:39] <mrevell> kiko: Thanks.
[14:40] <mrevell> encompass: If you join our beta team you can try the mailing list feature we're planning to release in the near future.
[14:40] <kiko> mrevell, so I mean, could you contact somebody at launchpad.net/memaker and let them know?
[14:40] <danilos> mrevell: we'll need to discuss some translations related stuff today (later) or tomorrow, can you make up some time for that
[14:40] <kiko> barry, can I get a 1-line summary of how the ML beta works?
[14:40] <mrevell> danilos: After the meeting?
[14:41] <danilos> mrevell: a bit later, I'll have to run out for a couple hours
[14:41] <danilos> mrevell: if you are not around, anytime tomorrow is fine as well
[14:41] <danilos> kiko: please change the topic in here :)
[14:41] <barry> kiko: teams which are members of a special 'mailing lists beta testers team' will have the opportunity to apply for a team mailing list
[14:41] <mrevell> danilos: No problem. I can be around later. TOmorrow I'm on holiday.
[14:41] <danilos> mrevell: ok, cool
[14:42] <Hobbsee> holiday?  waht's that?
[14:42] <kiko> danilos, this channel isn't +t, help me out!
[14:43] <Hobbsee> kiko: /topic foo ?
[14:43] <mrevell> danilos: Can we set a time now, though, please?
[14:43] <kiko> I'm trying to get danilos to do it Hobbsee :)
[14:43] <mrevell> barry: Do you have time for a short call today?
[14:43] <Hobbsee> kiko: oh, right.
[14:43] <barry> mrevell: yes.  think we can do it in 15 minutes?  i have another meeting in 1:15
[14:44] <mrevell> barry: That sounds great, thank you. Skype okay?
[14:44] <barry> mrevell: perfect!
[15:29] <mwhudson> soren: fwiw, the bzr 1.0 branch managed to successfully get your branch from launchpad
[15:29] <soren> mwhudson: Cool. I'll just wait patiently for an update to show up. thanks!
[15:37]  * Hobbsee ponders doing PPA support at this time of night
[15:37]  * Hobbsee decides "screw it", and leaves it to the paid people.
[16:06] <mwhudson> soren: aaaah
[16:06] <mwhudson> i can run _bzr get_ on your branch
[16:06] <mwhudson> but not _bzr checkout_
[16:06] <mwhudson> workaround: bzr get the branch, then bind it
[16:06] <mwhudson> also, seems like bug filing time...
[16:16] <lamont> cprov: can you help me understand why LP isn't starting any hppa builds?
[16:17] <cprov> lamont: since when ?
[16:17] <lamont> hppa build of gcc-4.2 4.2.2-4ubuntu2 in ubuntu hardy RELEASE
[16:17] <lamont> Build started 18 hours ago on kohnen (hppa) and finished 16 hours ago taking 2 hours 10 minutes — see the log 
[16:17] <lamont> that's the last build on kohnen
[16:17] <lamont> the others, longer.
[16:18] <lamont> 17 hours ago or later was when the last build finished on all 3 
[16:18] <lamont> er, 17 hours ago or less (later in time)
[16:18] <lamont> hppa build of gnome-panel 1:2.20.1-0ubuntu2 in ubuntu hardy RELEASE
[16:18] <lamont> Build started 17 hours ago on castilla (hppa) and finished 17 hours ago taking 45 minutes — see the log 
[16:19] <lamont> castilla was the last to start, and the 2nd of 3 to finish
[16:19] <lamont> looking at the log on kohnen, it was screaming about bzip2 finding end-of-file early, which kinda points at a bad chroot tarball??????
[16:26] <cprov> lamont: ok, let's wait q-b to stop and I will run slave-scanner manually to see what's it doing.
[16:27] <cprov> in 5 minutes
[16:27] <lamont> cool.  I'
[16:27] <lamont> ll wait to hear from you
[16:27] <lamont> stupid ' key
[16:31] <cprov> lamont: they are all in BUILDERFAIL status, they need to be restarted.
[16:32] <cprov> lamont, my network will be down for some minutes, brb
[16:32] <lamont> all restarted
[16:38] <kiko> wooo
[16:46] <cprov> ping
[16:48] <lamont> 2007/12/13 16:35 GMT [HTTPChannel,8,91.189.90.177] Build log: RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '472098-1127207', '/home/buildd/filecache-default/9bc3d0e680f2a161676f338820082aca8bc3018e']
[16:48] <lamont> 2007/12/13 16:35 GMT [-] Build log: Uncompressing the tarball...
[16:49] <lamont> 2007/12/13 16:35 GMT [-] Build log:
[16:49] <lamont> 2007/12/13 16:35 GMT [-] bunzip2: Compressed file ends unexpectedly;
[16:49] <lamont> 2007/12/13 16:35 GMT [-]        perhaps it is corrupted?  *Possible* reason follows.
[16:49] <lamont> so, uh, which tarball?
[16:50]  * lamont does a tar tvjf
[16:50] <lamont> -rw-r--r-- root/root   6361856 2007-12-12 21:19:31 chroot-autobuild/var/lib/apt/lists/ftpmaster.internal_ubuntu_dists_hardy_main_binary-hppa_Packages
[16:50] <lamont> bzip2: Compressed file ends unexpectedly;
[16:50] <lamont> ls -l /home/buildd/filecache-default/9bc3d0e680f2a161676f338820082aca8bc3018e*
[16:50] <lamont> -rw------- 1 buildd buildd  44937216 2007-12-12 22:38 /home/buildd/filecache-default/9bc3d0e680f2a161676f338820082aca8bc3018e
[16:50] <lamont> -rw------- 1 buildd buildd 140025000 2007-12-13 16:35 /home/buildd/filecache-default/9bc3d0e680f2a161676f338820082aca8bc3018e.tmp
[16:51] <lamont> and 25GB of free space, so I think we're good there
[16:54] <lamont> cprov: is the librarian copy the same size /etc?
[16:54] <lamont> fb904843cfe546b484c9fd77e518abf6
[16:54] <lamont> cpro1: let me guess.. you missed all that?
[16:54]  * lamont pastes in /query
[16:56] <lamont> cprov: ack?
[16:56] <kiko> you flood him and then expect him to ack immediately??
[16:57] <cprov> lamont: ack
[16:58] <lamont> kiko: of course. he's just that good.
[17:05] <lamont> kiko: and I was really just wanting to make sure that the flood had reached him, not that he'd read it...
[17:05] <lamont> and that he wasn't just bouncing in network-purgatory
[17:05] <kiko> heh
[17:20] <cr3> can someone make the hardware-certification-manual project private so that bugs and code are private?
[17:26] <ubotu> New bug: #176171 in malone "Unable to invalidate linux-source-2.6.24 bug" [Undecided,New] https://launchpad.net/bugs/176171
[17:30] <lamont> cprov: thanks again
[17:32] <lamont> cprov: and when boredom sets in sometime in the future, it'd be nice if the BUILDERFAIL status got more of that logfile spamage from the builder.
[17:33] <lamont> And I suppose that when we make it so that there's an LP interface for uploading chroot tarballs, it'd be a real win if there were some incoming QA checks on them before they got pushed live.
[18:15] <MiserySalin> Hi... how can I retrigger a build of my PPA? I have a "Missing dependencies: ...." in a package because it builds too fast that the other package-build were not be ready.
[18:16] <MiserySalin> there is no need to bump a version number... only a retry on i386 (amd64 and lpia builds fast enough)
[18:16] <kiko> MiserySalin, hmm, I'm not sure it's possible. cprov?
[18:17] <cprov> MiserySalin: you can't retry a build if it was already built.
[18:18] <cprov> MiserySalin: if it failed you should be able to hit 'retry' in the build page
[18:19] <MiserySalin> ooohhh...... I never saw that "retry"-link
[18:19] <MiserySalin> is that new?
[18:20] <MiserySalin> But thanks!
[18:20] <cprov> MiserySalin: not exactly, I think it was already there since 1.1.10. Did it work ?
[18:22] <stdin> funny thing is, the "Use the 'Retry build' link in the Actions menu if you wish to retry your build." line was added because the link seemed obscure
[18:22] <MiserySalin> yes, thanks.... "retry build" did the job ;-)
[18:25] <kiko> heh
[18:55] <profanephobia> how often are blueprints read through by devs?
[19:14] <Odd_Bloke> profanephobia: Depends on project.
[19:14] <profanephobia> k
[19:23] <no0tic> hi, I deactivated an old gpg key and activated a new one.. do I need to sign another time the ubuntu code of conduct I signed with the previous key?
[20:09] <mikkael> are these gutsy or hardy packages: the sources list entry shows hardy, the series say gutsy: https://launchpad.net/~notz/+archive ?
[20:31] <Fujitsu> lamont: Right, but it doesn't fit the naming scheme of the rest of the new buildds.
[20:32] <lamont> Fujitsu: yeah. but it already existed.
[20:32] <lamont> concordia is from the penguins or antartic bases theme...
[20:32] <lamont> which predate the elements theme
[20:34] <Fujitsu> Ah.
[20:35] <Fujitsu> mikkael: That's a known bug.
[21:15] <gspr> I filed a question for my PPA to be cleared out. Someone replied and said it had been done. All the packages on the list are gone, but the files still remain, preventing me to upload new versions. What can I do?
[21:29] <Fujitsu> gspr: I suspect that the files will vanish when you upload a new version of them.
[21:29] <Fujitsu> They shouldn't stop you from uploading a package with the same version.
[21:30] <Fujitsu> That is, all the `deleted' files will actually be deleted when you upload any package.
[21:36] <The-Kernel> hi, I created a PPA, and I was curious as to where the howto/documentation is located.
[21:36] <The-Kernel> anyone know?
[21:36] <The-Kernel> i found it
[21:36] <The-Kernel> thanks  though
[21:51] <gspr> Fujitsu: Actually, I get an error about mismatching .orig checksum when trying to upload the package.
[21:51] <gspr> Fujitsu: I reckon the orig is still around, and it doesn't like that
[22:41] <Fujitsu> cprov: Around?
[22:42] <cprov> Fujitsu: yes, I'm here. How can I help you ?
[22:42] <Fujitsu> cprov: gspr requested that things be deleted from his PPA, but the .orig.tar.gzs don't seem to have actually vanished, and so md5sum issues appear.
[22:43] <cprov> Fujitsu: which package ?
[22:44] <Fujitsu> That I'm not sure about.
[22:44] <Fujitsu> gspr: ^^
[22:46] <cprov> Fujitsu: https://edge.launchpad.net/~gspreemann/+archive?field.name_filter=&field.status_filter=any, the packages were not deleted yet, when was it requested.
[22:50] <Fujitsu> cprov: They are listed as deleted...
[22:50] <cprov> Fujitsu: https://answers.edge.launchpad.net/launchpad/+question/19886, deletion requested and perform yesterday, the 1.1.11 codeline still waiting 24 hours to perform deletions in archive disk. Summing up, the files will be deleted in 5 hours
[22:50] <Fujitsu> Ah.
[22:50] <Fujitsu> So Deleted in this case is the old PendingRemoval?
[22:51] <cprov> Fujitsu: but the files are still being presented, which indicates that they were not deleted yet
[22:52] <cprov> Fujitsu: sort of, PENDINGREMOVAL is not a publishing state anymore, but still part of the workflow
[22:52] <Fujitsu> I've seen other PPAs where the files have stuck around for days after being `deleted'.
[22:52] <Fujitsu> Right, hence `old'.
[22:53] <cprov> Fujitsu: in 1.1.12, deletions will be performed immediately (in the next mass-removal run, not in the N+2 run)
[22:54] <cprov> anyway,  I wonder why so many deletions in PPAs 
[22:59] <Fujitsu> People may upload something experimental to their PPA, and later want their PPA to be widely used. With the current model, users get all or nothing. IMO, components within a PPA should be flexible so owners can segregate things, but there's probably a good reason to not allow that.