[00:33] <gianmt> guys what shall I do if bzr keeps on telling me to run bzr upgrade to get better performance when I push on launchpad but when I run it it says that I'm already at the laste version
[00:33] <gianmt> Format <RepositoryFormatKnit1> for bzr+ssh://bazaar.launchpad.net/%7Epoppler-python/poppler-python/trunk/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
[00:33] <gianmt> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.
[00:44] <mthaddon> gianmt: what version of bzr are you using?
[00:49] <mwhudson> gianmt: what exact command are you running?
[00:51] <crimsun> gianmt: are you actually providing the repo path? i was also receiving that message for my pulseaudio branch until i realised that i needed `bzr upgrade lp:~crimsun/pulseaudio/ubuntu'
[00:52] <crimsun> FWIW, the message "please use 'bzr upgrade'" *could* be a bit more informative
[00:52] <gianmt> mwhudson, I think I fix it, I was running it only on my local copy, I thought it would have fix also the remote copy
[00:52] <gianmt> crimsun, yeah, then I've done that
[00:52] <mwhudson> gianmt: right, that was what i was suspecting :)
[00:52] <gianmt>  bzr upgrade bzr+ssh://bazaar.launchpad.net/~poppler-python/poppler-python/trunk/
[00:52] <gianmt> should be fine now
[00:53] <gianmt> thanks all :)
[00:53] <NCommander> Out of curosity, who manages dogfood? (which team)
[00:54] <gianmt> g'nite all
[00:54] <mwhudson> NCommander: soyuz
[00:57] <kirkland> beuno: perhaps you might know who owns dogfood.launchpad.net?
[00:58] <kirkland> beuno: NCommander was asking me, i pointed him here
 Out of curosity, who manages dogfood? (which team)
[00:58] <NCommander> * kirkland (n=kirkland@cpe-66-68-12-58.austin.res.rr.com) has joined #launchpad
[00:58] <kirkland> NCommander: ah, missed it, sorry
[00:59] <NCommander> well, unless you have a time machine
[00:59] <NCommander> not your fault
[00:59] <kirkland> NCommander: its in my scrollback, i just missed it
[01:00] <NCommander> kirkland, I said it before you joined ;-)
[01:00] <stdin> nope, kirkland joined, then you asked
[01:00] <beuno> kirkland, the soyuz guys
[01:00] <stdin> you has lag ;)
[01:01] <beuno> kirkland, so you need to talk to cprov or bigjools
[01:02] <kirkland> beuno: rock on, thanks man!
[01:02] <kirkland> NCommander: ^^
[01:02]  * beuno keeps on rockin'
[01:03]  * NCommander keeps on rocking in the free world
[01:03] <maxb> NCommander: Hi, I was just reading https://wiki.ubuntu.com/CruftBusters and wondering: are only members of the team supposed to subscribe it to bugs, or is it allowed for anyone to do that to request review from the team?
[01:04] <NCommander> maxb, generally speaking, the cruft buster team are people who are a handy pool of volunteers to descend on some evil transition
[01:05] <maxb> Ah. I've made a list of packages which have been FTBFS since before intrepid and am wondering what I should do with those bugs when I file them
[01:06] <maxb> in terms of making sure the right people see them
[01:09] <NCommander> maxb, we already have the FTBFS page
[01:13] <maxb> where can I find that page?
[01:44] <cprov> NCommander: soyuz-team manages dogfood.l.n, what we can do for you ?
[01:47] <NCommander> cprov, I'm not sure I'm going to need anything anymore, I just came to a realization that something else can handle my needs without making the dogfood team run around in circles ;-)
[01:47] <cprov> NCommander: what exactly did you have in mind ?
[02:06] <james_w> maxb: qa.ubuntuwire.com
[02:17] <ScottK> cprov: Is the copy of packages-arch-specific used by Soyuz publically available  anywhere?
[02:23] <NCommander> ScottK, it uses the one Debian uses
[03:02] <afiestas> yep! is there any way to remove a serie from a project ?
[03:03] <beuno> afiestas, not currently, no
[03:03] <beuno> there will be soon
[03:03] <afiestas> ook! I'm gonna add this channel at autojoing :p
[03:04] <savvas> Add an auto-question too :) "Is it done yet?" "How about now?" "And now?" hehe
[03:37] <ovnicraft> hi, can i download launchpad app?
[03:38] <beuno> ovnicraft, you mean the code for Launchpad?
[03:39] <ovnicraft> yes
[03:39] <beuno> Launchpad's code will be opened around July/August, but it's currently not available
[03:40]  * beuno forgot the date which it will be opened
[03:40] <ovnicraft> where can i read more info about that?
[03:41] <beuno> ovnicraft, it was announced during the last UDS, and more details will be published shortly on the Launchpad blog
[03:41] <beuno> news.launchpad.net
[03:42] <crimsun> ovnicraft: https://dev.launchpad.net/OpenSourcing
[04:06] <ovnicraft> is wrote in python?
[04:07] <ovnicraft> crimsun, that is a great news
[04:07] <beuno> ovnicraft, it's mostly python, yes
[04:39] <ScottK> NCommander: I understand that's the theory.  Since Debian changed p-a-s maintenance, I'm not sure.
[08:21] <mvo> hi, I got a question about launchpad projects and their translations - will rosetta automatically pull the latest pot file for my project from bzr or will I have to do this manually? or will it use some other source (like the ubuntu package)?
[08:25] <henninge> hi mvo, there is no automated update process implemented (yet).
[08:25] <henninge> mvo: there is a blueprint for syncing with bzr https://blueprints.edge.launchpad.net/rosetta/+spec/rosetta-translates-branch
[08:26] <mvo> henninge: thanks, so the workflow would be to manually upload the pot on each string change?
[08:26] <mvo> (currently)
[08:26] <henninge> mvo: yes, that is the current situation.
[08:27] <mvo> thanks for confirming henninge, not ideal but at least I know now that I have not overlooked a checkbox or something :)
[08:27] <henninge> mvo: the next likly step will be tackled is to sync with branches hosted on launchpad
[08:28] <henninge> mvo: That would save the upload but I don't know about automatic
[08:28] <mvo> henninge: great, most (all?) of my stuff is hosted there :) any (rough) time estimates? is it [ ] weeks [ ] months [ ] years away?
[08:28] <henninge> months [x]
[08:28] <mvo> thanks :)
[08:29] <henninge> I'd say, but there is no definite timeline yet ... ;-)
[08:29] <henninge> mvo: vou're welcome
[08:29] <mvo> its fine, just wanted to get a idea if its worth building some script magic or if its around the corner anyway so not worth bothering
[08:30] <henninge> mvo: have a look at this, then: https://edge.launchpad.net/lp-translations-tools/
[08:32] <mvo> henninge: thanks, I have something similar here, but *much* less well documented and a lot less options ;)
[11:23]  * mpt goes to report a bug and finds it's already been reported by some "Matthew Paul Thomas" person
[15:28] <CarlFK> whats a good way to script adding a ppa to sources.list?
[15:29] <CarlFK> something like sudo (echo >>/etc/apt/sources.list)
[15:29] <bigjools> use "sudo tee -a"
[15:29] <Daviey> echo "deb http://ppa.launchpad/etc main" | sudo tee /etc/apt/sources.list.d/jackjones-ppa.list
[15:30] <Daviey> is _one_ way
[16:27] <superm1> hi guys, i've got an arch All binary package defined in debian/control that seems to not be getting added by the PPA build for i386 or amd64.  can someone take a look?  the package is nvidia-180-libvdpau-dev on https://bugs.edge.launchpad.net/~superm1/+archive
[16:27] <superm1> i see references to it in the build logs as being a built binary, but LP doesn't seem to add it
[16:28] <bigjools> superm1: gladly, I like the look of that package :)
[16:29] <superm1> thanks bigjools
[16:31] <bigjools> superm1: ok so the build's completed, you just need to wait a bit longer for the publishing cycle to start
[16:31] <superm1> bigjools, bug doesn't the status say "published" already?
[16:31] <bigjools> that's just the source
[16:31] <superm1> oh, that's confusing. i see
[16:31] <bigjools> yeah it is a bit
[16:32] <superm1> perhaps two different status bits would be a good idea "Source published" and "Binaries published"
[16:34] <bigjools> some sort of indication of which packages in which arches are published would be good
[16:34] <bigjools> if you file a bug I'll get it looked at
[16:35] <superm1> sure
[16:35] <superm1> against soyuz?
[16:35] <bigjools> yes please
[16:36] <superm1> okay will do
[16:51] <superm1> bigjools, i filed the bug, but are you sure that's what it was?  It's been 30 minutes since the build finished and both the resulting binaries pages don't show a reference to the package (https://bugs.edge.launchpad.net/~superm1/+archive/+build/829489 and https://bugs.edge.launchpad.net/~superm1/+archive/+build/829490 )
[16:51] <bigjools> superm1: let me check again
[16:53] <bigjools> superm1: I can see them published ok, e.g. http://ppa.launchpad.net/superm1/ubuntu/pool/main/n/nvidia-graphics-drivers-180/
[16:54] <superm1> bigjools, but not for the latest build (ppa8)
[16:54] <superm1> that's the one where i made them arch all
[16:55] <bigjools> superm1: I can see ppa8 in there
[16:55] <superm1> for libvdpau-dev?  i just see ppa4 and two ppa6's
[16:55] <bigjools> ah that one, sorry
[16:56] <bigjools> superm1: right, there's no such package built
[16:56] <superm1> but look at the amd64 build log, you'll see it referenced in the changes file
[16:57] <superm1> and it's listed in debian/control too
[16:58] <bigjools> I see it
[16:58] <bigjools> weird
[16:58] <bigjools> does it work if you build locally?
[16:58] <superm1> let me give it a quick shot
[16:59] <bigjools> superm1: ok so it's in the changes file Binary: header but there's no actual file referenced
[17:04] <superm1> bigjools, hum well that's odd, it looks like even with "sbuild -A" it's not showing up locally either.  well i guess i've got some other problem with the package then that i'm not realizing.  sorry for the chatter, but thanks for taking a look
[17:04] <bigjools> superm1: no problem, good luck :)
[17:23] <NCommander> hey cprov
[17:29] <superm1> bigjools, fwiw i found the problem, the original packager must have not anticipated arch independent packages because they blurted -s's in the rules file in a few places, so updating that resolves things
[17:30] <bigjools> superm1: great
[18:54] <krow> Ok, feeling like a n00b,... anyone have the URL to add a new project to LP?
[18:55] <beuno> krow, https://launchpad.net/projects/+new
[18:55] <krow> beuno: Thanks!
[19:09] <pochu> no help contact? :)
[19:10] <pochu> danilos: hi! I uploaded a bunch of translations templates for a lot of languages for emesene, and they are still in "needs review". when I uploaded them, I show a message saying they would be automatically checked, though. Does it take much for them to get through?
[19:10] <pochu> danilos: https://translations.edge.launchpad.net/emesene/trunk/+imports
[19:22] <Ursinha> henninge, ^
[19:25] <henninge> pochu: Imports are processed by an auto-approval script.
[19:25] <henninge> pochu: the script tries to guess the language from the file name
[19:26] <henninge> pochu: I am not sure if the filenames are good for that, although they  contain the language code.
[19:26] <henninge> pochu: let me check ...
[19:26] <pochu> henninge: thanks a lot
[19:43] <gsuveg> re
[19:43] <gsuveg> beuno, hi
[19:43] <gsuveg> beuno, i have a solution....
[19:44] <gsuveg> beuno, with a new ssh-key its works.... (and edit the .ssh/config)
[19:49] <henninge> pochu: yep, the filenames should have been just the language code to get approved automatically, like "zh_TW.po"
[19:49] <henninge> pochu: did you upload them in a tarball, btw?
[19:50] <pochu> henninge: yes
[19:50] <pochu> henninge: I can reupload them with the correct names
[19:50] <henninge> pochu: no, that would create extra entries
[19:51] <henninge> pochu: although ...
[19:51] <pochu> I can put the current ones to "deleted"
[19:51] <pochu> henninge: but if you can accept them, that would be awesome too :)
[19:52] <henninge> pochu: yes, deleting was my idea
[19:52] <henninge> pochu: it is either your work in renaming the files or my work in approving them manually ... ;-)
[19:53] <henninge> pochu: but I'd suggest you rename the file to be consistent with future uploads.
[19:53] <henninge> s/file/files/
[19:53] <pochu> right
[19:53] <pochu> makes sense
[19:54] <henninge> pochu: no need to include the template again, btw, as it has already been  imported.
[19:54] <pochu> henninge: sure. thanks a lot for looking into it :)
[19:56] <henninge> pochu: pleasure
[20:12] <mtaylor> how do I tell ~vcs-imports nevermind... I didn't really mean to do the import thing
[20:12] <mtaylor> ?
[20:13] <mtaylor> oh, maybe I did'
[20:13] <mtaylor> everyone stop paying attention to me
[20:24] <gsuveg> bye
[21:22] <cprov> NCommander: hey
[21:23] <NCommander> hey cprov
[21:23] <cprov> NCommander: can I help ?
[21:24] <NCommander> cprov, I had to ask you for something, but my mind went *bink* and I can't remember :-/
[21:25] <cprov> NCommander: ehe, no problem.
[21:34] <maxb> cprov: hi, is it documented anywhere where Soyuz gets its Packages-arch-specific from, and how often it gets it? I'd like to be certain I'm looking at the exact same version that Soyuz is.
[21:35] <cprov> maxb: we use the debian P-a-s as it is.
[21:35] <cprov> maxb: http://buildd.debian.org/quinn-diff/Packages-arch-specific
[21:35] <maxb> Thanks - that was what I was wondering - did it get it by http, cvs, or git
[21:36] <maxb> updates propagate automatically?
[21:37]  * maxb is pondering a P-a-s masked binaries report
[21:37] <cprov> maxb: cvs, every 15 min
[21:38] <maxb> ah... and what about the fact that P-a-s is no longer maintained in cvs? :-)
[21:38] <cprov> maxb: you might be thinking about https://bugs.launchpad.net/bugs/311952
[21:38] <maxb> yup, I filed that bug :-)
[21:39] <cprov> maxb: cvs still up-to-date, but we will migrate to the http interface soon
[21:41] <maxb> cprov: Are you sure cvs is still up-to-date? Looks to me like http and git have changes that cvs does not
[21:43] <cprov> maxb: no, I am not sure.
[21:44] <maxb> ok then. I've diffed the various sources - cvs is stale
[21:44] <maxb> this is useful information, I shall use the stale version in working on my reporting script for now, then :-)
[21:49] <cprov> maxb: right, quite a lot of changes.
[22:30] <ScottK> cprov: What's the English version of infinity's comment on the p-a-s bug?
[23:09] <ronny> yo
[23:10] <ronny> any plans to lower the response times of launchpad?
[23:10] <ronny> i geting something betwen 3-10 seconds peer request
[23:10] <ronny> thats killing the usability
[23:13] <spiv> ronny: yes.  See all the bugs tagged 'performance' in the bug tracker.
[23:46] <f4> hi
[23:48] <f4> a dev made a mistake on my project, and committed and pushed to his launchpad branch
[23:48] <f4> to restore to last revision i do bzr uncommit then i have to do bzr push --overwrite ?
[23:49] <danser> when I delete a project on launchpad, will its name become available for other users again?
[23:49] <mwhudson> yeah. that works
[23:49] <f4> because a normal push says "No new revisions to push." (which is right)
[23:49] <mwhudson> danser: *you* can'
[23:49] <mwhudson> t delete a project
[23:49] <mwhudson> but, yes, aiui
[23:50] <f4> mwhudson, your first line was for me? ^^
[23:50] <danser> ah, okay, in that case: could a launchpad admin change the ID of 'atlantis' to 'stipvis'? afaik, there are no links to project pages yet.
[23:50] <mwhudson> f4: yeah
[23:50] <f4> ok thanks then :)
[23:50] <mwhudson> spm: can you handle danser's request?
[23:51] <spm> mwhudson: sure
[23:51] <danser> spm: if it's more work than deleting a project, deleting is ok to me too - I'll just recreate it with the new name
[23:51] <spm> danser: is about the same :-)
[23:53] <spm> danser: https://edge.launchpad.net/stipvis
[23:53] <danser> spm: great, thanks!
[23:54] <spm> np