[00:06] <Balaams_Miracle> Fujitsu: You had me curious, so i added up the percentages too. It's not exacly 100% but (according to gcalctool) 99.99%. This looks like bug #104024, with the differece that "need review" also show no translatables.
[00:06] <ubotu> Launchpad bug 104024 in rosetta "Untranslated filter shows no strings, but percentage untranslated < 100%" [High,Invalid] https://launchpad.net/bugs/104024
[00:20] <poolie> mpt, i'd really really like if it was easier to edit bug tags 
[00:20] <poolie> like from the edit status dialog-thing
[00:23] <Fujitsu> poolie: bug #76095, bug #127138
[00:23] <ubotu> Launchpad bug 76095 in xwpe "xwpe fails to work properly in AMD64" [Undecided,New] https://launchpad.net/bugs/76095
[00:23] <ubotu> Launchpad bug 127138 in malone "Can't add/remove tags while changing a bug's status" [Undecided,New] https://launchpad.net/bugs/127138
[00:23] <Fujitsu> Erm, first one is wrong.
[00:23] <Fujitsu> Bug #76085
[00:23] <ubotu> Launchpad bug 76085 in malone "A bug report should be entirely modifiable in the bug page" [Undecided,New] https://launchpad.net/bugs/76085
[00:23] <poolie> uh, also i guess we need bug voting ;-)
[00:24] <Fujitsu> malone-me-too, targetted for 1.2.3 or so, IIRC.
[00:25] <Fujitsu> Or perhaps vote-system, or bug #149775.
[00:25] <ubotu> Launchpad bug 149775 in ubuntu "Adding tags and voting on bug reports" [Undecided,Invalid] https://launchpad.net/bugs/149775
[00:30] <ubotu> New bug: #172689 in rosetta "Filter shows no strings when there are untranslated strings" [Undecided,New] https://launchpad.net/bugs/172689
[00:55]  * mpt hugs Fujitsu
[00:57]  * Fujitsu hugs mpt back.
[00:57] <Fujitsu> What did I do this time?
[01:04]  * Hobbsee waves
[01:05]  * ajmitch waves at Hobbsee 
[01:05]  * Fujitsu drops a Launchpad on Hobbsee.
[01:06] <Hobbsee> heya Fujitsu!
[01:06]  * Hobbsee catches the launchpad, and spins it around like a cube
[01:06] <Fujitsu> Nooo.
[01:06] <ajmitch> more shiny spinning cubes...
[01:07] <Fujitsu> ajmitch: Haha.
[01:10] <Fujitsu> mpt: Oh, was that about the voting/UI references that I gave above?
[01:18] <mpt> Fujitsu, yes
[01:23] <Fujitsu> mpt: Ah, that makes more sense.
[02:05] <ubotu> New bug: #172702 in malone "Bug assignee list searches users of all launchpad projects" [Undecided,New] https://launchpad.net/bugs/172702
[02:56] <jefferai> can anyone tell me how I can search for a member of launchpad?
[02:56] <jefferai> I'm trying to find a specific person on there
[02:56] <jefferai> their contact page
[02:56] <Hobbsee> launchpad.net/people and use the search?
[02:57] <jefferai> see, why is there no link to that page...
[02:57] <Hobbsee> i have no idea....
[02:57] <jefferai> Hobbsee: when I see code in launchpad, is that some internal ubuntu copy, or what?
[02:58] <LaserJock> I've never really understood why there wasn't a link to people/ from the frontpage
[02:58] <jefferai> I'm specifically looking at this: https://code.launchpad.net/~taglib-developers/taglib/taglib.ext
[02:58] <LaserJock> jefferai: well that's code from the taglib-developers team on Launchpad
[02:58] <jefferai> yeah, but how do I know how that syncs up with upstream?
[02:59] <jefferai> there's also "trunk" and "taglib.ext"
[02:59] <jefferai> trunk looks to be newer
[02:59] <LaserJock> hard to say
[02:59] <LaserJock> it's up to the team members
[03:01] <poolie> thumper, ping?
[03:01] <thumper> poolie: pong
[03:01] <poolie> just wanted to point you to jefferai's question - and how that might be more clear in the ui
[03:02] <jefferai> like trunk looks like it's upstream trunk
[03:02] <jefferai> but in that case, is taglib.ext the one packaged with Ubuntu, or trunk?
[03:02] <jefferai> when are they synced up? 
[03:02] <jefferai> etc
[03:02] <LaserJock> jefferai: you'd have to ask the owner
[03:02] <LaserJock> jefferai: it's not specific to Ubuntu I wouldn't think
[03:03] <poolie> well, you can see lukas merged from svn about 6 weeks ago
[03:03] <jefferai> right, I do see that
[03:03] <poolie>  i agree this is not a packaging branch
[03:04] <thumper> jefferai: trunk is an imported branch
[03:04] <thumper> I have been considering badging or somehow otherwise identifying the different branch types
[03:04] <jefferai> so that is imported from kde svn, then?
[03:04] <jefferai> and that is then merged into taglib.ext?
[03:05] <jefferai> taglib.ext sounds like it means "external" i.e. from kde svn, but it doesn't
[03:06] <thumper> jefferai: https://edge.launchpad.net/taglib/trunk shows that trunk is imported from svn://anonsvn.kde.org/home/kde/trunk/kdesupport/taglib
[03:06] <jefferai> ok
[03:06] <thumper> jefferai: I'll be the first to agree that this is somewhat ackward
[03:06] <jefferai> whatever edge is
[03:06] <thumper> jefferai: and there are plans in motion now to make the UI better around import branches
[03:06] <thumper> jefferai: sorry, edge is running the latest code
[03:07] <thumper> jefferai: and as a LP developer I get automaticly redirected to use edge
[03:07] <thumper> jefferai: as to the launchpad beta testers
[03:07] <jefferai> ah, ok
[03:21] <LaserJock> who would know about a vcs-import that doesn't seem to be updating?
[03:21] <Fujitsu> LaserJock: File an answer against launchpad-bazaar.
[03:22] <LaserJock> Fujitsu: isn't that file aquestion?
[03:22] <LaserJock> *a question
[03:22] <Fujitsu> LaserJock: You file bugs in Launchpad Bugs, so therefor you file answers in Launchpad Answers. QED.
[03:22] <LaserJock> hehe
[03:22] <Hobbsee> haha
[03:23] <LaserJock> Fujitsu: when does has that logic ever held? ;-)
[03:23] <LaserJock> s/does//
[03:23]  * ajmitch drinks
[03:23]  * Fujitsu files some translations.
[04:03] <Zelut> can someone point me to a reference on how to push my project code to code.launchpad.net/projectname?
[04:06] <Fujitsu> Zelut: You don't push directly to project. You push to a branch.
[04:06] <LaserJock> https://help.launchpad.net/FeatureHighlights/EasyBranching perhaps
[04:06] <Fujitsu> Although once you've created a branch, you can set it to be the trunk, and then you can branch/push directly from the project URL.
[04:07] <Zelut> I basically want to update what I already have here
[04:07] <Zelut> https://code.launchpad.net/folding
[04:09] <Fujitsu> Zelut: Right. You want to push to sftp://christer.edwards@bazaar.launchpad.net/~christer.edwards/folding/main
[04:10] <Zelut> I don't recall the bazaar syntax.  We use cvs at the office so I always forget.
[04:11] <Fujitsu> Zelut: bzr push someurl
[04:11] <Fujitsu> Though you'll need to bzr co it first.
[04:11] <Fujitsu> Er, bzr branch
[04:11] <Zelut> from within the ~/myproject folder I assume?
[04:11] <Fujitsu> Is said folder a brach?
[04:11] <Fujitsu> *branch
[04:12] <Fujitsu> The link LaserJock gave above is probably a good reference.
[04:18] <tonyyarusso> Is the build system portion of LP OSS yet?
[04:18] <Fujitsu> tonyyarusso: No.
[04:18] <tonyyarusso> Fujitsu: phooey.
[04:19] <Fujitsu> The only noticeable part of Launchpad that has been released is storm, and that's not even used in the main branch yet...
[04:21] <tonyyarusso> That's super-lame, frankly.
[05:36] <lamont> dear launchpad, is there any way to identify the signer of the source.changes file?
[05:37] <Fujitsu> lamont: Pipe it through GPG?
[05:38] <Fujitsu> Query the database with the SQL powers you don't have?
[05:39] <lamont> heh
[05:40] <lamont> https://edge.launchpad.net/ubuntu/hardy/+source/newt/0.52.2-11.1ubuntu1 would be an example
[05:40] <Fujitsu> Ask Keybuk; MoM does it.
[05:40] <ubotu> New bug: #172727 in launchpad "People page (/people) is too hard to find" [Undecided,New] https://launchpad.net/bugs/172727
[05:41] <lamont> oh, properly munging the changes file would have a significant effect.
[05:42] <Fujitsu> How are they improperly munged?
[05:45] <ubotu> New bug: #172729 in launchpad "show target milestone in (some?) bug lists and on the bug page" [Undecided,New] https://launchpad.net/bugs/172729
[06:26] <lamont> Fujitsu: if I had properly munged the chages file before I uploaded, it would be different..
[06:26] <lamont> OTOH, I'm pretty sure that changes file looked just like all the other sponsored uploads I've done for debian as well, so ...
[07:01] <ubotu> New bug: #172735 in launchpad-bazaar "Branch page advises people to join a restricted team" [Undecided,New] https://launchpad.net/bugs/172735
[07:14] <SAL123> What is the .changes file required by dput? I have my own deb package and want to build it for more ubuntu releases.
[07:20] <LaserJock> SAL123: you need a source package
[07:20] <SAL123> LaserJock: What is the source package? How I can create it?
[07:20] <LaserJock> which is made up generally of .dsc, .diff.gz, and .orig.tar.gz files
[07:20] <LaserJock> SAL123: well, if you can't find one from the same source you got the .deb you'll need to make one
[07:21] <LaserJock> !packagingguide
[07:21] <ubotu> packagingguide is The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[07:21] <LaserJock> ^^ that can help you
[07:23] <SAL123> Is the pbuilder package required to create my source package?
[07:24] <LaserJock> no required really
[07:24] <LaserJock> but suggested
[07:24] <SAL123> It contains many dependencies and I want to leave my chrooted ubuntu small.
[07:24] <LaserJock> well, pbuilder actually cuts down on dependencies
[07:25] <LaserJock> but does take up quite a bit of disk space
[07:25] <SAL123> LaserJock: PackagingGuide says about pbuilder to create the source package. Any other way? I have my .dsc and orig package build by dephelper tools (my package from debian).
[07:26] <LaserJock> oh ok
[07:26] <LaserJock> then you need to install the build depdencies
[07:26] <LaserJock> or way
[07:26] <LaserJock> *wait
[07:27] <LaserJock> you just want to build a source package? or a .deb?
[07:31] <SAL123> LaserJock: My deb builds fine, just I can't find a source package on my disk.
[07:31] <SAL123> -rw-r--r-- 1 ondrejj ondrejj    577 Oct 12 19:16 sagator_1.0.0-0beta27.dsc
[07:31] <SAL123> -rw-r--r-- 1 ondrejj ondrejj 214657 Oct 12 19:15 sagator_1.0.0-0beta27.tar.gz
[07:31] <SAL123> -rw-r--r-- 1 ondrejj ondrejj 361462 Oct 12 19:16 sagator_1.0.0-0beta27_all.deb
[07:31] <Fujitsu> Ew, native.
[07:32] <SAL123> that are my packages build from my source, there is no "patch" required, because it is my own project and it has all included in sources.
[07:32] <Fujitsu> SAL123: The source package is that .dsc and .tar.gz.
[07:32] <Fujitsu> Ah...
[07:32] <Fujitsu> However, you need a .changes. How are you building it?
[07:33] <SAL123> Fujitsu: dpkg-buildpackage -rfakeroot
[07:33] <Fujitsu> SAL123: I recommend that you build with `debuild -S'.
[07:36] <SAL123> Fujitsu: I want to avoid installing all required dependecies, if it is possible.
[07:37] <LaserJock> SAL123: debuild -S is what you want
[07:37] <Fujitsu> SAL123: You should also be test-building, so will need the build-dependencies anyway...
[07:37] <LaserJock> it's a wrapper around dpkg-buildpackage that also does the signing
[07:39] <SAL123> A lot of X* applications, spell checkers and more packages required py pdebuild. I want to use launchpad to build my packages and free some disk space, not use more of them. :(
[07:40] <LaserJock> well, it's not very idea to not test your packages at all
[07:40] <LaserJock> *ideal
[07:41] <LaserJock> you can save yourself a lot of trouble using pbuilder rather than waiting for a build to fail on Launchpad
[07:41] <Fujitsu> You should always test the build locally first; PPAs are not a test-building dumping ground.
[07:41] <LaserJock> SAL123: the dependecies should take all that much disk space
[07:42] <LaserJock> depending on the package
[07:42] <Fujitsu> s/should/shouldn't./
[07:42] <Fujitsu> s/\.//
[07:42] <LaserJock> yeah
[07:43] <SAL123> hmm, my package builds well with dpkg-buildpackage
[07:43] <LaserJock> right
[07:43] <Fujitsu> Oh, you're using *p*debuild?
[07:43] <SAL123> builds well on 2 debians, one ubuntu, fedora, suse, gentoo
[07:43] <LaserJock> ok, well if you're building it already then it shouldn't be a problem right?
[07:44] <SAL123> all of them (except gentoo) builds automatically in my chroots.
[07:45] <LaserJock> ok, then that would be at least some for of testing, although not as thorough as pbuilder
[07:45] <SAL123> Each beta/rc/stable release is built automatically in chroot and put into proper repository on my web. But I am limited with disk space and want to add more supported distributions, for example more ubuntu versions now.
[07:48] <LaserJock> well, pbuilders are very nice for that
[07:48] <LaserJock> because it is a compressed chroot environment that stays clean
[07:49] <SAL123> Is it working to chroot in another chroot?
[07:49] <LaserJock> in any case, at a minimum if you have a .dsc and .tar.gz you can run debuild -S instead of dpkg-buildpackage and you should get a .changes file
[07:50] <SAL123> I have no real ubuntu installed, just an chrooted one. :)
[07:50] <LaserJock> SAL123: you can install it in the chroot
[07:50] <LaserJock> or in a Debian install if you have one
[07:50] <SAL123> LaserJock: ok, I will try, there is no other option for me :(
[07:51] <LaserJock> it would be nice if you didn't have it as a native package (where the debian/ director is a part of the tar.gz) but that's up to you
[07:52] <SAL123> After unpacking 528MB will be used.     Wrrr.... :(
[07:53] <LaserJock> SAL123: what is that for?
[07:53] <SAL123> LaserJock: aptitude install pdebuild
[07:53] <LaserJock> SAL123: try aptitude -r install pbuilder
[07:54] <SAL123> LaserJock: Much better, just 4 MB. It will work?
[07:54] <LaserJock> yep
[07:55] <SAL123> LaserJock: Thanks. It's an ideal solution for me. :-)
[07:56] <LaserJock> well
[07:56] <LaserJock> it'll get bigger
[07:56] <LaserJock> the compressed chroot will take ~100MB
[07:56] <LaserJock> and you'll need enough disk space to actually build the thing, but it cleans up when it's done
[07:57] <LaserJock> and it's fairly easy to have pbuilders for multiple Ubuntu/Debian versions
[07:57] <LaserJock> so you can have one Ubuntu chroot with multiple pbuilders to build for various releases
[07:57] <LaserJock> rather than creating several different chroots
[08:00] <SAL123> LaserJock: I know, similiar application for Fedora is named mock. :)
[08:02] <LaserJock> ah yes
[08:02] <LaserJock> we had the guy who made mock come by the other day
[08:03] <carlos> morning
[08:03] <LaserJock> well, time for bed
[08:03] <LaserJock> carlos: hi .. bye
[08:03] <LaserJock> SAL123: good luck
[08:04] <carlos> LaserJock: good night!
[08:04] <SAL123> My package has been uploaded by dput, do I need to request a build?
[08:04] <SAL123> I can't find it on Ubuntu builds page.
[08:05] <SAL123> LaserJock: Thank you. :)
[08:05] <LaserJock> SAL123: make sure to read through the PPA Quick Start guide
[08:05] <LaserJock> https://help.launchpad.net/PPAQuickStart
[08:05]  * LaserJock out
[08:05] <SAL123> LaserJock: already read, it says only that If the build fails, you will receive a failure notification. 
[08:06] <SAL123> The quickstart is very quick, usable just for experienced packagers.
[08:53] <oly-> hi, i have my project hosted on launchpad, im looking ito getting it translated and noticed launchpad has a translation feature, but it wants a .pol file what are these and where can i find information about how to create them ?
[08:59] <SAL123> The icomming directory in dput.cf must always end with "ubuntu"?
[09:00] <ubotu> New bug: #172747 in soyuz "copy-package.py claims package isn't in -proposed when a -backports version exists" [Undecided,New] https://launchpad.net/bugs/172747
[09:00] <soren> SAL123: For PPA's, yes.
[09:13] <mrevell> morning
[09:14] <carlos> oly-: hi
[09:14] <carlos> oly-: a .pot file is the file format used by gettext library to translate applications
[09:15] <carlos> there are some tools to convert from other file formats into .pot files so you can use Launchpad for translations
[09:18] <SAL123> soren: And what if I missed and sent my package with wrong directory?
[09:19] <soren> SAL123: Probably nothing.
[09:19] <oly-> okay, carlos thxs will look into gettext library, 
[09:20] <carlos> oly-: what application are we talking about?
[09:21] <oly-> a python application, basically web managment tool
[09:21] <oly-> its all in english at moment, never tried to add support for translations in the passed so looking into it
[09:21] <SAL123> soren: Right. It's my problem. What now? I can't upload it again, because it says that it is already uploaded.
[09:21] <soren> SAL123: dput -f ppa asdfasdfasdf.changes
[09:22] <soren> SAL123:      ^^
[09:22] <SAL123> soren: thanks
[09:51] <SAL123> What must be in my .dput.cf in []? The user name or the package name? Must be followed by -ppa?
[09:59] <doko> how can I add a hosted branch for a team in LP?
[10:01] <doko> "You cannot assign a +junk branch to a team. Create a project first."
[10:13] <carlos> oly-: python documentation documents how to use gettext
[10:13] <oly-> yeah found that, also found an example tutorial to look at
[10:14] <oly-> because the python documentation did not seem that clear to me
[10:31] <carlos> oly-: ok
[10:32] <oly-> but thxs not heard of gettext till now :)
[10:42] <carlos> oly-: you are welcome :-)
[10:45] <ubotu> New bug: #172773 in launchpad "ProductReleaseFile doesn't have an owner column" [Undecided,New] https://launchpad.net/bugs/172773
[11:00] <SAL123> Step 4: Launchpad will give you an accepted or rejected upload notification. How it will give me this?
[11:03] <Fujitsu> SAL123: Email
[11:03] <SAL123> Fujitsu: And if there is no one? What's wrong?
[11:05] <Fujitsu> SAL123: It likely means you've signed it with a key that Launchpad doesn't know about, or no key at all.
[11:06] <Fujitsu> SAL123: Did you find the correct upload location in the PPAQuickStart?
[11:06] <SAL123> Fujitsu: incomming = ~ondrejj/ubuntu/      <- do you mean this?
[11:08] <SAL123> Fujitsu: I don't know, what to replace in example .dput.cf and what to leave unchanged.
[11:09] <Fujitsu> SAL123: Incoming should be spelt with a single m, but that looks to be otherwise correct.
[11:09] <SAL123> Fujitsu: i have proper one in my config, just typo when copying :)
[11:10] <SAL123> Fujitsu: my complete config looks like this: http://pastebin.com/d3eaadd49
[11:11] <Fujitsu> SAL123: That looks sane.
[11:11] <SAL123> Fujitsu: And what now? dput says at end: "Successfully uploaded packages."
[11:11] <Fujitsu> SAL123: When did you upload it?
[11:11] <SAL123> Fujitsu: But nothing found on: https://launchpad.net/~ondrejj/+archive/+builds?build_text=&build_state=all
[11:12] <SAL123> Fujitsu: many times, first aprox. hald hour ago.
[11:12] <SAL123> Fujitsu: half hour ago
[11:12] <Fujitsu> SAL123: Are you sure the .changes is signed properly?
[11:12] <Fujitsu> If you view it, does it have a signature visible?
[11:13] <SAL123> Fujitsu: yes, there is a signature. IMHO there is no other key in my chrooted ubuntu.
[11:14] <SAL123> gpg: Signature made Št 29. november 2007, 12:02:11 CET using DSA key ID 6B822FE7
[11:14] <SAL123> gpg: Good signature from "Jan ONDREJ (SAGATOR) <ondrejj@salstar.sk>"
[11:14] <Fujitsu> SAL123: OK, that looks fine...
[11:17] <cprov> morning, folks
[11:17] <Fujitsu> Hey cprov.
[11:18] <SAL123> Fujitsu: Any ideas, what to do?
[11:18] <Fujitsu> SAL123: I'm trying something, I'll report back in a bit more than a minute.
[11:19] <SAL123> Fujitsu: thanks, I am going to lunch :)
[11:21] <Fujitsu> SAL123: Are you sure you're uploading the correct .changes, and the rejected mail isn't being caught by a spam filter somewhere?
[11:23] <daub> how can i enable the bug report for a project?
[11:23] <Fujitsu> daub: Go into the `Change Details'
[11:24] <Fujitsu> ... page of the project, and scroll down to around the middle.
[11:24] <Fujitsu> There should be a selector for the bug tracker there; select Launchpad in it.
[11:26] <daub> ok, i'm in overview->change details. but i don't see a selector
[11:27] <Fujitsu> daub: Around the middle, `Bugs are tracked:'
[11:27] <Fujitsu> There are three option buttons with a drop-down list.
[11:28] <daub> https://launchpad.net/~daub/+edit
[11:28] <daub> is the the right url?
[11:29] <Fujitsu> daub: Ah, that's the page for your person.
[11:29] <Fujitsu> You can't file bugs on a person...
[11:29] <daub> :)
[11:29] <Fujitsu> You're looking for /forecastgnome/edit+?
[11:29] <Fujitsu> Er, +edit
[11:30] <ubotu> New bug: #172780 in rosetta "translated strings counts translations that may not be translated in Launchpad anymore" [Undecided,New] https://launchpad.net/bugs/172780
[11:31] <Fujitsu> Yay, third bug like that I've seen in 24 hours...
[11:31] <daub> Fujitsu: now i found it. thanks
[11:32] <Fujitsu> daub: Great.
[11:43] <SAL123> Fujitsu: I think it is the correct changes file.
[11:43] <SAL123> Fujitsu: There is only one in my chroot.
[11:45] <SAL123> Fujitsu: I have my own server and I can't find email with text "launchpad.net" in my spambox.
[11:45] <Fujitsu> cprov: Are you able to quickly look at any upload logs for ~ondrejj and see what is happening?
[11:45] <Fujitsu> It is signed with the correct key.
[11:48] <cprov> Fujitsu: PPA or primary ?
[11:48] <SAL123> cprov: primary
[11:48] <SAL123> cprov: oops
[11:48] <SAL123> cprov: ppa :)
[11:48] <cprov> ta
[11:48] <SAL123> cprov: sorry :)
[11:49] <Fujitsu> cprov: PPA.
[11:49]  * Fujitsu is too late.
[11:50] <cprov> Fujitsu: Subject: dvd95_1.3p0-0ubuntu1_source.changes rejected -> Signer has no upload rights to this PPA ?
[11:50] <SAL123> cprov: not, it's not mine
[11:51] <Fujitsu> cprov: That was me testing that it was actually accepting uploads, sorry.
[11:51] <Fujitsu> s/accepting/processing/
[11:51] <cprov> I see
[11:52] <cprov> Fujitsu: SAL123 -> Signing key B32D056EF40213C64B47C43B08AA50066B822FE7 not registered in launchpad.
[11:52] <Fujitsu> cprov: That key is! Or maybe we have a collision..
[11:52] <Fujitsu> 'twas the first thing I checked, though the fingerprint could be different.
[11:52] <SAL123> My fist upload has been uploaded without proper registration.
[11:53] <Fujitsu> Ah.
[11:53] <cprov> SAL123: could you try again now ?
[11:54] <Fujitsu> Preferably in the next 50 seconds.
[11:54] <SAL123> cprov: sure, done
[11:54] <cprov> thx
[11:55] <cprov> Jan ONDREJ (SAL) <ondrejj(at)salstar.sk>: no @ found in email address part.
[11:55] <Fujitsu> Hahaha.
[11:55] <SAL123> :-)
[11:56] <Fujitsu> Shouldn't it then email the signer at their default email address?
[11:56] <cprov> Fujitsu: possibly, first time I've seen this error
[11:56] <SAL123> Which email? In key or in package?
[11:57]  * Hobbsee waves
[11:57] <Fujitsu> Hey Hobbsee.
[11:57] <cprov> Fujitsu: debuild and/or dput should scream before. Does dak support this ?
[11:57] <SAL123> There is only a Maintainer: tag in .dst and .changes file with (at) string. I can't find other.
[11:58] <Fujitsu> cprov: That's a good question. I haven't looked at much of dak.
[11:59] <Fujitsu> cprov: It's fine to fail on it, but it should at least email the signer, as it knows a contact address from the key.
[11:59]  * SAL123 is trying to upload a modified package with maintainer without (at).
[11:59] <Fujitsu> Black-holing uploads is a bad idea unless there is no alternative.
[12:00] <elmo> dak will reject that
[12:00] <elmo> Fujitsu: that's not necessarily a good idea
[12:00] <Fujitsu> elmo: Why not?
[12:00] <elmo> Fujitsu: e.g. I could take some anti-ubuntu debian's persons uploads and feed them to PPA.  soyuz certainly shouldn't mail him/her just because they signed the upload
[12:01] <Fujitsu> elmo: That's true, but there are much worse things that can be done like that. They'll get accepted emails otherwise.
[12:01] <elmo> no, they won't get accepted emails
[12:01] <elmo> because the upload has to be targeted for ubuntu/ppa to get accepted
[12:02] <Fujitsu> elmo: I can upload a package from the primary archive to my PPA using the same .changes.
[12:02] <elmo> the primary _Ubuntu_ archive
[12:02] <elmo> and that's still a bug
[12:02] <Fujitsu> Right.
[12:02] <elmo> which is getting fixed, AFAIK
[12:02] <Fujitsu> You have a point.
[12:03] <Fujitsu> elmo: But I can upload something signed by me to an arbitrary person's PPA (indeed, I did that just before to test), and it will give me a rejected mail.
[12:03] <Fujitsu> I can presumably do that with lots of DD's packages too.
[12:03] <Fujitsu> And generally spam the hell out of everybody.
[12:03]  * Hobbsee wonders waht the discussion is on
[12:03] <elmo> Fujitsu: with what as the target suite?
[12:04] <Fujitsu> elmo: hardy.
[12:04] <Hobbsee> oh, mailing the person on a reject.  right
[12:04]  * Fujitsu tries to upload something targetted at sid to PPA.
[12:04] <Hobbsee> Fujitsu: an anti-debian person wouldn't upload to hardy.
[12:04] <Hobbsee> er, anti-ubuntu person wouldn't target stuff to hardy
[12:04] <Fujitsu> Hobbsee: Right, but I think it'll still reject them... Unknown suite, or so.
[12:05] <Hobbsee> this seems to be an argument about why we should, or should not have public signed changes files, then.
[12:05] <elmo> not really
[12:05] <elmo> I'm just saying with the current passive reject stuff, who it mails has to be very very carefuly thought through with maliciousness in mind
[12:06] <Fujitsu> Hobbsee: It is specifically an argument over whether this corner case shouldn't be emailed.
[12:06] <elmo> IIRC, cprov was looking at changing uploads to something that would allow for active/real time feedback and avoid almost all of this
[12:06] <Fujitsu> There is more malicious stuff that can be done with PPAs than emailing signers because they used incorrect email syntax.
[12:07] <Hobbsee> Fujitsu: and far more efficient ways of spamming big groups of people through lauchpad, too
[12:07] <elmo> Fujitsu: dude, you're arguing for doing something bad, because there are existing bugs in this area
[12:07] <Fujitsu> Hobbsee: This is true.
[12:07] <elmo> Hobbsee: in terms of Debian/Ubuntu relations, using Launchpad to spam Debian folks is about as efficently destructive as it gets
[12:08] <Hobbsee> elmo: agreed.  
[12:08] <Hobbsee> elmo: i was thinking globally over LP, but i see your point.  i now also see what your corner case actually *is*.
[12:08] <Fujitsu> elmo: You are correct on both counts.
[12:10] <Fujitsu> elmo: Is there a better way to notify people, though?
[12:10] <Fujitsu> Wait, why would an anti-Ubuntu person have their key registered in LP anyway?
[12:10] <elmo> Fujitsu: well, if we stopped using ftp, and moved to something which gave more immediate feedback - directly to the person doing the upload, that would avoid this entire class of problems
[12:10] <Fujitsu> If they thought it was that evil..
[12:10] <cprov> Fujitsu: not on a anonymous ftp server.
[12:11] <Fujitsu> That's true
[12:11] <Hobbsee> Fujitsu: to put crap on the bug reports and specs, etc, etc, etc.
[12:12] <Fujitsu> I wouldn't have imagined Soyuz would be planning to diverge from the norm so much, but that is a good thing.
[12:14] <SAL123> My bulid request has been accepted. When it will be displayed on: https://launchpad.net/~ondrejj/+archive/+builds?build_text=&build_state=all   ?
[12:15] <Fujitsu> SAL123: Within about 10 minutes, I believe, but cprov will be able to tell you for sure.
[12:16] <cprov> SAL123: 30 minutes in average.
[12:17] <Fujitsu> cprov: Is queue-builder still taking ages, or is there another thing that creates the build records?
[12:19] <SAL123> There is no "waiting build" status on a page? When displaying "All states" this does not display my job after accepting immediatelly in a waiting state?
[12:20] <Fujitsu> SAL123: Build records are not created immediately upon upload.
[12:20] <cprov> Fujitsu: exactly, not yet.
[12:21] <Fujitsu> cprov: It would be a lot less confusing to have the incoming processor create them, I think. Is that on the roadmap?
[12:23] <cprov> Fujitsu: yes, 1.1.12
[12:23] <Fujitsu> Ah, good.
[12:37]  * Fujitsu wonders if we can steal usernames that appear to have not been used for anything (perhaps only ShipIt)
[12:38] <kiko> Fujitsu, you can, yes.
[12:40] <Fujitsu> kiko: Can I please transform into william, then? They control @ubuntu.com emails address, so it'd be nice to have a better one.
[12:40] <kiko> Fujitsu, what is it today?
[12:40] <Fujitsu> kiko: fujitsu
[12:41] <Fujitsu> Hobbsee: Staying for a while this time?
[12:41] <Hobbsee> grrr
[12:41]  * Fujitsu finds the uiv2-inline-navigation spec to look counterproductive.
[12:41] <Hobbsee> Fujitsu: if my X doesn't crash a third time in ~5 mins, yes.
[12:42] <kiko> Fujitsu, you know, it is going to be much harder to find you on launchpad if you use fujitsu as your IRC nick though
[12:43] <Fujitsu> kiko: That's true. I was planning to change my IRC presence to something else (say, wgrant) at some point, but never got around to it.
[12:43] <Hobbsee> Fujitsu: you're not a canonical employee.  that only happens for them :P
[12:44] <Fujitsu> Hobbsee: tepsipakki is lost, tseng is, soon to be me too!
[12:44] <kiko> Fujitsu, if you want we can change everything at once and be consistent :)
[12:45] <Fujitsu> kiko: Perhaps. I might become wgrant across the board then, which I can probably do without duck intervention.
[12:46] <kiko> Fujitsu, ok. think it over and let me know; I'm happy to give you william as you are a most valued member, but I don't want to leave things more confusing than they are :)
[12:47]  * Fujitsu probably shouldn't be polluting namespaces with such common names, either.
[12:49] <kiko> we could blacklist william. that'd be most evil. :)
[12:49] <Hobbsee> incomming soyuz bug.
[12:49]  * Hobbsee has pondered taking over sarah.
[12:55] <ubotu> New bug: #172798 in soyuz "Builddmaster leaves buildlogs behind in /tmp" [High,In progress] https://launchpad.net/bugs/172798
[13:05] <daub> daub can i upload a package to the ppa without creating a source package?
[13:06] <daub> because my project is python based
[13:06] <Fujitsu> daub: No. Binary packages must be built from source inside Launchpad; manual binary uploads will be rejected.
[13:07] <daub> ok
[13:16] <lamont> Hobbsee: what if sarah doesn't want to be taken over?
[13:16] <Fujitsu> lamont: ... then she'll get attacked with a certain stick. Duh.
[13:16] <lamont> lol
[13:17] <Hobbsee> lamont: oh...there really is a sarah now.  there wasnt' before.
[13:17] <lamont> the one I'm thinking of has existed for 15 years or so. :-)
[13:20] <lamont> but I realize now that you just want to take over a _nick_.  not some other corpus.
[13:20] <lamont> my bad
[13:22] <Hobbsee> lamont: no, i'll take over every sarah on earth, i think :)
[13:24] <Fujitsu> Taking over Nicks and Sarahs? There go my two siblings.
[13:31] <ubotu> New bug: #160683 in ubuntu "vmware-server: Package requests recursive update (dup-of: 172275)" [High,Confirmed] https://launchpad.net/bugs/160683
[13:35] <ubotu> New bug: #164277 in vmware-server (partner) "vmware-server upgrade problem (dup-of: 172275)" [Undecided,New] https://launchpad.net/bugs/164277
[13:48] <kiko> t-10
[13:49]  * Hobbsee wonders when the ext user meeting is
[13:49] <Hobbsee> er, next
[13:57] <kiko> t-1
[13:57]  * kiko winks at BjornT 
[14:00] <BjornT> welcome to this weeks Launchpad developers' meeting
[14:01] <BjornT> we'll talk about Launchpad development for the next 45 minutes
[14:02] <ddaa> me
[14:02] <BjornT> == Agenda ==
[14:02] <BjornT> * Roll call * Agenda * Next meeting * Actions from last meeting * Oops report (Matsubara) * Critical Bugs (Rinchen) * Bug tags * Operations report (mthaddon) * DBA report (stub) * Sysadmin requests (Rinchen) * A top user-affecting issue (mrevell)
[14:02] <BjornT> ---- * Death to `[trivial]` (SteveA) * Clear up old work-in-progress branches (mwhudson)
[14:02] <BjornT> ---- * Blockers
[14:02] <mwhudson> me
[14:02] <BjornT> who's here?
[14:02] <barry_> me
[14:02] <flacoste> me
[14:02] <gmb> me
[14:02] <allenap> me
[14:02] <sinzui> me
[14:02] <ddaa> me
[14:02] <stub> me
[14:02] <salgado> me
[14:02] <EdwinGrubbs> me
[14:02] <carlos> me
[14:02] <adeuring> me
[14:02] <bac> me
[14:02] <jtv> me
[14:02] <kiko> me
[14:03] <schwuk> me
[14:03] <mrevell> me
[14:04] <jtv> Apology: Danilo is at a conference
[14:04] <BjornT> jamesh, Rinchen, matsubara, jsk send their apologies
[14:04] <BjornT> SteveA_ might be a bit late
[14:06] <BjornT> * Next meeting
[14:06] <BjornT> will anyone not be able to attend next week?
[14:06] <stub> Assuming my leave is (finally) approved, me
[14:06] <kiko> I'll be here
[14:06] <mrevell> I'll be sprinting along with mpt, matsubara, mthaddon and Rinchen, but I assume we'll be at the meeting
[14:07] <jamesh> BjornT: I think that apology is old for me.  Didn't realise it was there
[14:07] <carlos> I'm on leave
[14:07] <carlos> until next year...
[14:07] <SteveA_> BjornT: me
[14:07] <jtv> jamesh: a standing apology, cool idea.
[14:07] <BjornT> ok, that should be fine. next meeting will be 2007-12-06 at 1400 UTC
[14:08] <BjornT> * Actions from last meeting
[14:08] <BjornT> there doesn't seem to a log from last meeting, so i don't know if there were any actions. anyone remember?
[14:08] <SteveA_> BjornT: I will be on vacation next week
[14:09] <BjornT> SteveA_: ah, i thought wanted to raise your present. who will chair the meeting next week?
[14:09] <SteveA_> BjornT: would you like to do it again?
[14:09] <BjornT> SteveA: sure
[14:10] <BjornT> * Oops report (Matsubara)
[14:10] <BjornT> matsubara isn't here. did he delegate the oops report to anyone?
[14:10] <salgado> First congratulations to the Translations guys for nailing down bug 30602. The new top timeout contender is bug 50617, which intellectronica is already taking care of.
[14:10] <salgado> BjornT: Rinchen asked me to keep an eye on +filebug timeouts. We had five timeouts on +filebug yesterday: OOPS-697C31, OOPS-697C318, OOPS-697E26, OOPS-697C1706, OOPS-697D1789. Can you investigate and check if they're regressions of bug 86361?
[14:10] <salgado> That's all for today.
[14:10] <ubotu> Launchpad bug 30602 in rosetta "Timeout errors in +translate" [High,Fix released] https://launchpad.net/bugs/30602 - Assigned to Jeroen T. Vermeulen (jtv)
[14:10] <BUGabundo> hay
[14:10] <BUGabundo> I'm on edge
[14:10] <BUGabundo> and something really strange is going on
[14:10] <ubotu> Bug 50617 on http://launchpad.net/bugs/50617 is private
[14:10] <ubotu> Launchpad bug 86361 in malone "Search for duplicate and similar bugs on +filebug sometimes timeout" [High,Fix released] https://launchpad.net/bugs/86361 - Assigned to Francis J. Lacoste (flacoste)
[14:10] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/697C31
[14:10] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/697C318
[14:10] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/697E26
[14:10] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/697C1706
[14:10] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/697D1789
[14:10] <BUGabundo> there's no text box to insert the package for bug submits!
[14:10] <salgado> yep, that's his report, BjornT 
[14:11] <BUGabundo> mdz: hya
[14:11] <kiko> BUGabundo, please /msg me, we're mid-meeting.
[14:12] <BjornT> ok, i'll look at the +filebug timeouts later
[14:12] <BjornT> * Critical Bugs (Rinchen)
[14:12] <mrevell> Hi
[14:12] <mrevell> I'm standing if for Rinchen this week
[14:12] <mrevell> as he's away.
[14:13] <mrevell> Joey sent me an email with two bugs to look at. My email provider is down at the moment, so I don't have the email to hand. However, carlos tells me that he's just commited a fix for bug n #165218
[14:13] <mrevell> and cprov I see you have a private critical bug. Can you tell me what the status is, please for bug 157552?
[14:13] <ubotu> Bug 157552 on http://launchpad.net/bugs/157552 is private
[14:14] <cprov> shh ...
[14:14] <cprov> me
[14:14] <mrevell> cprov: /msg me if necessary
[14:14] <cprov> mrevell: k, continue
[14:14] <mrevell> Does anyone else have a message they want me to pass to Rinchen regarding critical bugs?
[14:15] <mrevell> 5
[14:15] <mrevell> 4
[14:15] <mrevell> 3
[14:15] <mrevell> 2
[14:15] <mrevell> 1
[14:15] <Hobbsee> mrevell: fix them all :)
[14:15] <mrevell> Thanks BjornT
[14:15] <BjornT> * Bug tags
[14:15] <SteveA> cprov: would you update the bug report on 157552 to give an idea of the current situation?
[14:15] <carlos> Hobbsee: ;-)
[14:16] <cprov> SteveA: will do, julian has 90% of the code done
[14:16] <Hobbsee> carlos: oh, and have it done by 3 weeks ago :)
[14:16] <BjornT> there are three tags proposed: bugtag, hwdb, and feeds
[14:16] <bigjools> I'm here, sorry I'm late
[14:17] <BjornT> i think we discussed these tags last week. has anything changed since then?
[14:17] <intellectronica> i'm also here, b.t.w - only missed the first few minutes
[14:17] <SteveA> well
[14:17] <SteveA> the link against bugtag now returns no bugs
[14:17] <SteveA> because it goes to bugtags
[14:18] <kiko> right
[14:18] <SteveA> but there are many bugs tagged with 'bugtag'
[14:18] <SteveA> which is what we agreed
[14:18] <kiko> we fixed
[14:18] <kiko> them
[14:18] <SteveA> so this tag can now become official on that page
[14:18] <kiko> Rinchen updated all of them manually
[14:18] <kiko> very good
[14:18] <kiko> SteveA, about hwdb, were you against it?
[14:18] <BjornT> so, is 'bugtag' approved?
[14:18] <SteveA> yes
[14:18] <SteveA> BjornT: yes
[14:19] <SteveA> kiko: I'm not totally against it.  More like -0 when there's only one bug that seems to apply
[14:19] <SteveA> I wonder also if it should be a project
[14:19] <kiko> SteveA, but there will be more bugs as the feature moves on.
[14:19] <kiko> it might be a separate project.. it sort of depends.
[14:19] <kiko> there are more bugs actually I believe
[14:19] <kiko> pity abel is on vac
[14:19] <kiko> schwuk?
[14:20] <adeuring> I'm here :)
[14:20] <SteveA> hi abel!
[14:20] <adeuring> hi SteveA
[14:20] <SteveA> I'm thinking the hwdb should be a project, and the hwdb-client should be a project
[14:20] <schwuk> kiko: I believe that the consensus last week was that there weren't enough bugs to justify the tag being official yet, but we wanted your input
[14:20] <SteveA> I don't feel very strongly on it though
[14:21] <kiko> SteveA, the client is a project indeed.
[14:21] <adeuring> Regrading the tag, I think too we can define it, when we need it
[14:21] <kiko> the backend is.. possibly best modeled as a project
[14:21] <kiko> okay
[14:21] <kiko> thanks guys
[14:21] <kiko> i'll update the page
[14:22] <schwuk> SteveA: hwdb-client actually exists as as separate project already - hwtest
[14:22] <SteveA> thanks \sh 
[14:22] <BjornT> and what about 'feeds'? it has 14 examples
[14:22] <SteveA> thanks schwuk 
[14:22] <SteveA> I think we need a tag for feeds.  Should it be called 'feeds' or 'feed' ?
[14:23]  * barry_ thinks feeds
[14:23] <BjornT> considering we renamed 'bugtags' to 'bugtag', maybe we should be consistent and call it 'feed'
[14:23] <mrevell> "feed" would sound odd
[14:23] <schwuk> BjornT: except that feeds are rarely referred to in the singular
[14:23] <bac> i prefer "feeds"
[14:23] <kiko> feeds
[14:24] <kiko> I think it should have been bugtags
[14:24] <SteveA> schwuk: "a line feed" ?   "a data feed"
[14:24] <kiko> but I don't care enough
[14:24] <schwuk> SteveA: with regard to RSS/Atom/XML feeds
[14:24]  * radix has an RSS feed.
[14:24] <BjornT> schwuk: well, the same applies for bugtag. you usally talk about 'tags'
[14:24] <schwuk> BjornT: so I agree with kiko
[14:25] <BjornT> well, me too actually
[14:25] <kiko> it should have been bugtags
[14:25] <kiko> but anyway
[14:25] <SteveA> let's go with 'feeds'
[14:25] <schwuk> radix: you may have one, but LP has multiple feeds
[14:25] <BjornT> so, let's approve 'feeds' then? we can consider renaming 'bugtags' later
[14:25] <BjornT> ok
[14:25] <kiko> yes
[14:25] <kiko> FINE
[14:25] <BjornT> * Operations report (mthaddon)
[14:25] <SteveA> I think 'feed' implies it's about an individual feed, and feeds says to me it's about the infrastructure
[14:26] <kiko> right
[14:26] <kiko> agred
[14:26] <SteveA> which also suggests 'bugtags' :-)
[14:26] <BjornT> mthaddon doesn't seem to be here
[14:26] <BjornT> anyone has his report?
[14:26] <SteveA> which would mean I was rooting for the wrong side a couple of weeks ago, but anyway ... ;-)
[14:27] <BjornT> ok, moving on. i'll ask mthaddon to send his report to the list
[14:27] <BjornT> * DBA report (stub)
[14:27] <stub> All postgres instances are now running 8.2.5. The fixes in 8.2.4 and 8.2.5 did have a significant impact on some of our queries and things are now running nicer.
[14:28] <stub> I would like to know *right now* if we can reboot carbon for some fs tweaks
[14:28] <SteveA> BjornT: please ask him to include in his report the current state of bug 157552 from his side
[14:28] <ubotu> Bug 157552 on http://launchpad.net/bugs/157552 is private
[14:28] <stub> Nothing else to report.
[14:28] <jtv> stub: we're running a test.
[14:28] <BjornT> SteveA: ok
[14:28] <stub> jtv: Please let elmo know when you are done then.
[14:28] <jtv> stub: ack
[14:28] <SteveA> BjornT: or better yet, leave a comment on the bug
[14:28] <jtv> stub: it'll be a while
[14:29] <SteveA> stub: I don't believe we're running any demos for people on there just now.
[14:29] <sinzui> could the DB upgrade be related the timeouts that bugs is experiencing?
[14:30] <kiko> 253 timeouts. wow!
[14:30] <stub> More timeouts than usual, or are they just noticeable now Rosetta isn't hogging the reports?
[14:31] <BjornT> i don't think there are more timeouts than usual. let's look at that later.
[14:31] <stub> Unlikely but possible. I don't think we will be going back though unless we have a dataloss or security type situation though so we need to deal anyway.
[14:32] <BjornT> * Sysadmin requests (Rinchen)
[14:32] <BjornT> mrevell: are you handling this as well?
[14:32] <kiko> I think there are much less timeouts in general
[14:32] <stub> We have a *gasp* metric for this don't we?
[14:32] <mrevell> BjornT: I don't have anything for sysadmin requests, no.
[14:33] <mrevell> However
[14:33] <SteveA> kiko: 253 time-outs total -- and not so many from bugs.  am I looking at the right stats?
[14:33] <kiko> stub, ha ha
[14:33] <mrevell> does anyone have something they'd like Joey's help in getting actioned?
[14:33] <kiko> SteveA, that's the right stats. 253 total. I was positively impressed
[14:33] <mrevell> Anyone have an RT request number they want Joey's help with?
[14:34] <kiko> 5 4 3 2 1 
[14:34] <BjornT> ok, let's move on
[14:34] <BjornT> * A top user-affecting issue (mrevell)
[14:34] <mrevell> Me again :)
[14:34] <mrevell> Looking at the Answers requests for Launchpad, there are two recurring questions:
[14:34] <mrevell>  "Please delete xxx from my PPA" and "Please rename project xxx".
[14:34] <mrevell>  We have plans to allow deleting packages from PPAs.
[14:35] <mrevell>  Do we have plans to allow project owners to rename their projects without involving a Launchpad admin?
[14:35] <kiko> not right now
[14:35] <ddaa> We used to have, Mark insisted that we don't.
[14:35] <mrevell> There's actually a third question that comes up a bit - regarding project deletion, but I realise that's a bigger deal.
[14:36] <mrevell> Okay, that pretty much answers it, thanks.
[14:36] <BjornT> mrevell: done?
[14:36] <kiko> well
[14:36] <kiko> I think we can reconsider project renames
[14:37] <kiko> and definitely deletion 
[14:37] <cprov> mrevell: yes, PPA deletion UI is planned for 1.2.1
[14:37] <kiko> but this work has not been scheduled yet
[14:37] <stub> We need to dig up or remember the use cases for us disabling it. There was a reason at the time, I'm sure, but there is a good chance it is no longer valid.
[14:37] <mrevell> We're not getting hundreds of requests, obviously but I wanted to see if it was something we could reconsider.
[14:37] <BjornT> ok, we don't have time to discuss this now, so let's have that discussion elsewhere, and move on
[14:37] <BjornT> * Clear up old work-in-progress branches (mwhudson)
[14:37] <mrevell> thanks guys
[14:38]  * mwhudson runs away, ddaa will take this
[14:38] <ddaa> After the lean training at UDS
[14:38] <ddaa> the code team decided to look for the status of all work-in-progress branches
[14:38] <ddaa> and clean up those that will never land
[14:38] <ddaa> we found this was a worthwhile exercise
[14:39] <ddaa> and encourage other teams to do the same
[14:39] <ddaa> I think that's it.
[14:40] <BjornT> ddaa: might consider sending a mail to the list about it
[14:40] <BjornT> * Death to `[trivial]` (SteveA)
[14:40] <BjornT> SteveA: 
[14:40] <SteveA> thanks BjornT 
[14:40] <SteveA> the review team discussed removing our use of the [trivial] tag to land code without review
[14:40] <ubotu> New bug: #172816 in launchpad "launchpad focus browser on summary and "hides" package" [Undecided,New] https://launchpad.net/bugs/172816
[14:41] <SteveA> now that we have processes that allow more timely reviews
[14:41] <SteveA> there should be much less overhead in getting small branches reviewed
[14:41] <SteveA> and the bzr project has had success with requiring a review for all landings, however trivial
[14:41] <kiko> wow.
[14:42] <kiko> this is a big step!
[14:42] <SteveA> so, I propose we remove the [trivial] tag for 2 months, and see what happens
[14:42] <SteveA> we need to introduce a different tag
[14:42]  * ddaa raises hand
[14:42] <SteveA> to allow, for example, stub
[14:42] <SteveA> and mthaddon
[14:42] <flacoste> we have rs=
[14:42] <kiko> they could use rs=
[14:42] <SteveA> to do procedural things that need doing via PQM
[14:42] <sinzui> sa=
[14:42] <stub> I was thinking db landings could go past the review team to see what happens. Might be confusion, might be helpful.
[14:42] <SteveA> so I propose we add [rollout] or something like that, for such tags
[14:43] <kiko> SteveA, I think stub's more on the right track
[14:43] <SteveA> sure, I'm in favour of keeping it consistent with no special cases
[14:43] <stub> [rollout] useful for ops stuff though - fixing configs and whatnot.
[14:43] <SteveA> if that's workable
[14:43] <barry_> iirc, mthaddon had no problem w/using existing procedures (sans trivial) for doing what he needs to do
[14:44] <SteveA> we can review use of [trivial] at the end of january
[14:44] <BjornT> so, do we remove the [trivial] tag, or does it need more discussion? time is running out, so we won't have time to discuss it in this meeting.
[14:44] <SteveA> and see how the experiment went
[14:44] <elmo> barry: (actually, I'm pretty sure he asked for a [sysadmin])
[14:44] <SteveA> BjornT: I will write a concrete proposal to the list
[14:44] <barry_> elmo, he did, but in a follow up agreed that it's probably not necessary
[14:44] <BjornT> ok, let's move on then
[14:44] <BjornT> * Blockers
[14:45] <SteveA> BjornT: I'd like everyone to note that [trivial] will be turned off next month
[14:45] <ddaa> Code: not blocked
[14:45]  * barry_ can dig up the email if necessary (or just ask mthaddon again ;)
[14:45] <SteveA> SC: not blocked
[14:45] <BjornT> Bugs Team: no
[14:45] <flacoste> Foundations Team: not blocked
[14:45] <bigjools> Soyuz Team: Not blocked
[14:45] <flacoste> elmo: do you time today to do this meeting with barry?
[14:46] <jtv> Translations team: not blocked
[14:46] <mrevell> Release team not blocked
[14:46] <bac> Commercialization team: not blocked
[14:46] <BjornT> adeuring, schwuk: hwdb?
[14:46] <adeuring> HWDB team: not blocked
[14:46] <BjornT> is that everyone?
[14:47] <BjornT> ok, meeting ended
[14:47] <mrevell> thanks BjornT, good job :)
[14:47] <barry_> thanks BjornT !
[14:47] <kiko> thanks guys!
[14:47]  * kiko waves
[14:48]  * carlos too
[14:51] <SteveA> thank you BjornT !
[14:51] <SteveA> great meeting chairing.
[15:25] <ubotu> New bug: #172825 in malone "Bug status import should happen outside transaction blogs" [High,Confirmed] https://launchpad.net/bugs/172825
[15:29] <dneary> Hi
[15:30] <dneary> When I download .po files from launchpad, I get some translations with "#-#-#-#-#  -  (PACKAGE VERSION)  #-#-#-#-#" lines in the middle
[15:31] <dneary> This ruins the translation presentation when I pull these down to my program and run po2ts - any idea why they're there?
[15:31] <dneary> And how to avoid them?
[15:37] <carlos> dneary: they come from a merge of two po files, that comes from gettext tools, not from Launchpad
[15:37] <carlos> dneary: is a way to denote that the merge had a conflict so the user needs to resolve it manually
[15:50] <dneary> carlos: Thanks
[15:50] <dneary> So I need to tell some people off, or could this happen when uploading a .po into launchpad?
[15:50] <carlos> we don't do that kind of merge
[15:50] <carlos> so it's something your translators introduced
[15:51] <carlos> it may stay in Launchpad as a suggestion
[15:51] <carlos> but just like any other bad translation
[16:04] <dneary> Is there any way to search for all of these?
[16:04] <dneary> Across all languages?
[16:04] <dneary> And stamp them out?
[16:05] <dneary> It's pretty widespread in the wengophone translations - I have 5 affected translations
[16:26] <bud3030> Were can i get info on my gpg
[16:40] <bud3030> I get this when I try to get a new gpg Invalid character
[16:41] <intellectronica> bud3030: what do you mean by "try to get a new gpg"?
[16:41] <intellectronica> bud3030: are you trying to upload a new gpg public key into launchpad?
[16:42] <Hobbsee> probably tryign to create a new gpg key
[16:42] <bud3030> yes what is going on I change the the wiki namen to my real name
[16:43] <bud3030> now it ask for a new gpg to activate ppa
[16:43] <bud3030> Hobbsee thank for the reply
[16:45] <intellectronica> bud3030: so, you take your public key and import it into launchpad by going to https://edge.launchpad.net/~bud3030/+editpgpkeys
[16:45] <bud3030> Hobbsee: it is tell me to but name prase and email
[16:46] <Hobbsee> bud3030: are you trying to use a strange character that isnt on a default english keyboard, by any chance?
[16:46] <Hobbsee> like, something you have to use the compose key for?
[16:46] <bud3030> no 
[16:46] <Hobbsee> what characters are you typing in?
[16:46] <bud3030> at first I typeed it in double quots the with out
[16:47] <bud3030> the qutos
[16:47] <Hobbsee> you shouldn't need to use quotes with it at all
[16:48] <intellectronica> bud3030: try a program called "seahorse", which is a nice GUI to GPG. you may find it easier
[16:48] <bud3030> I all so deleted my ssh and old email
[16:49] <bud3030> intellectronica : I have seahorese install I will give it a try
[16:52] <bud3030> hobbsee: thanks for help also intellectronica
[16:53] <intellectronica> bud3030: np
[17:00] <doko> how long does it take until a branch gets published on launchpad?
[19:05] <bbartek> Hi all
[19:05] <kiko> afternoon
[19:05] <bbartek> I just received my ubuntu membership on #ubuntu-members
[19:06] <kiko> well.. congratulations!
[19:06] <bbartek> is it possible to get an other launchpad name
[19:06] <bbartek> thank you kiko
[19:06] <bbartek> https://launchpad.net/~bart
[19:06] <kiko> it might be possible. 
[19:06] <bbartek> is from somebody who is not active
[19:07] <bbartek> https://launchpad.net/~broeckx
[19:07] <kiko> well
[19:07] <bbartek> this is the one i have wright now
[19:07] <kiko> isn't it better to use bbartek?
[19:08] <bbartek> Yes, i can use that one to but it's a short name
[19:08] <bbartek> my real name
[19:08] <kiko> well, it's also going to make it harder to identify you
[19:08] <bbartek> and from someone who probably doesn't even use ubuntu anymore
[19:08] <kiko> i.e. you make an administrative request and I can't figure out who you are
[19:08] <kiko> or I can't guess who to assign the bug to
[19:09] <kiko> it's always much (much!) better to have a uniquish name
[19:09] <kiko> even if it's cooler to have bart or fred or jane :)
[19:09] <bbartek> I do marketing and promotional activities 
[19:09] <bbartek> I'm not so active on launchpad
[19:09] <bbartek> i don't file bugs
[19:09] <bbartek> well a few
[19:10] <bbartek> bbartek is also poosible if it's better for you
[19:10] <kiko> well, I'm fine either way. that was just my advice as someone who deals with this sort of thing every day. :)
[19:11] <bbartek> if it's possible and not to much work i prefer bart
[19:11] <bbartek> but i will settle for bbartek to
[19:12] <bbartek> bart@ubuntu.com is cooler ;) 
[19:12] <kiko> bbartek, okay, bart is freed now. 
[19:13] <bbartek> kiko: thx
[19:13] <kiko> you can change your name in your +edit page
[19:13] <bbartek> ok i'll do it now
[19:13] <bbartek> thanks a lot
[19:14] <bbartek> done :)
[19:20] <cyberix> How am I supposed to credit translators?
[19:26] <kiko> cyberix, I'm not sure how you mean credit.
[19:26] <kiko> do you mean the translator-credits string?
[19:36] <cyberix> I collected latest po-files from Launchpad and I'm planning to include them in my upstream package.
[19:36] <cyberix> I'm talking about copyright
[19:36] <cyberix> The translators have copyright in their translations
[19:37] <cyberix> But I don't know who the translators are.
[19:58] <LaserJock> carlos: ping
[20:23] <lifeless> kiko: ping
[20:23] <kiko> lifeless!
[20:23] <lifeless> why was debian-bzr merged into registry? debian-bzr is the debian bzr packaging team
[20:24] <lifeless> (oh, and how are you :))
[20:28] <jelmer> lifeless: no, debian-bazaar is the debian bzr packaging team
[20:29] <jelmer> debian-bzr is a team I accidently created because I didn't know about debian-bazaar
[20:30] <lifeless> jelmer: ahha.
[20:30] <lifeless> kiko: so it sounds like I'm confused; is merging to registry how we delete teams ?
[20:30] <kiko> lifeless, yes.
[20:30] <kiko> well, it's how /I/ delete teams
[20:30] <kiko> nobody else does!
[20:31] <lifeless> kiko: the message to the user is very confusing
[20:32] <kiko> lifeless, there are worse things in life; I prefer admins to clear out membership first, but jelmer gets special treatment
[20:32] <kiko> lifeless, mpt has kept the bug on doing it properly open
[20:32] <lifeless> kiko: I see; its cool then.
[20:32] <lifeless> blame jelmer for me squawking
[20:33] <lifeless> jelmer: so debian-bazaar has just you in it
[20:35] <jelmer> huh
[20:36] <jelmer> bleh, time to quit drinking or something.. had this happen before
[20:36]  * jelmer filed two bugs about "bzr selftest -j", within a couple of months
[20:37] <jelmer> lifeless, kiko: Sorry for the trouble
[20:37] <kiko> nah
[20:37] <lifeless> jelmer: so what team am I meant to be in ?
[20:38] <jelmer> debian-bazaar - I'll add everybody to debian-bazaar
[20:38] <carlos> LaserJock: pong
[20:38] <LaserJock> carlos: was just talking to the gcompris author
[20:39] <carlos> LaserJock: indeed, the bug is fixed... let me retry it...
[20:39] <LaserJock> carlos: he says that the translations people are getting are incomplete, but do exist
[20:39] <LaserJock> I don't quite get why there should be any translations if there wasn't a .pot
[20:39] <carlos> hmm, no, the template was already imported (sorry I'm so busy I even forgot I already did it...)
[20:40] <carlos> LaserJock: we copy translations from one release to the other
[20:40] <carlos> LaserJock: so it would be for Feisty
[20:40] <LaserJock> he said he didn't think it was Feisty
[20:40] <LaserJock> so either it was maybe messed up in Feisty too
[20:40] <LaserJock> or something else
[20:40] <carlos> that's easy to check...
[20:41] <LaserJock> but my brain is hurting over trying to figure out this translations stuff :-)
[20:41] <carlos> indeed, Feisty was broken too
[20:42] <carlos> LaserJock: last update was 2006-05-11 21:00:08.796834+00:00
[20:43] <carlos> LaserJock: I think last update we got was from Dapper...
[20:43] <LaserJock> oh ...
[20:44] <LaserJock> ok, so to be clear, we're shipping the Dapper translations in Edgy, Feisty, and Gutsy?
[20:45] <ubotu> New bug: #172907 in launchpad "Deleting an email address that's used in subscriptions cases referential integrity error" [Undecided,New] https://launchpad.net/bugs/172907
[20:51] <LaserJock> carlos: am I correct? ^^
[20:54] <carlos> LaserJock: yes, although each one will have some translation updates
[20:55] <carlos> LaserJock: the problem is that message changes to the English string will be missing
[20:55] <LaserJock> yep
[20:55] <LaserJock> so that would account for the weird incomplete translations people are complaining about
[20:55] <LaserJock> since there have been new upstream releases, etc. since Dapper
[20:58] <LaserJock> carlos: ok, now with the new .pot I sent you will the upstream translations be given preference over what is in LP?
[20:58] <carlos> right
[20:59] <LaserJock> carlos: hmm, can I give you a Feisty .pot as well?
[21:00] <LaserJock> if we've got bad translations back to Edgy I'm thinking some Feisty users may benefit as well
[21:03] <mpt> Gooooooooooooooooood morning Launchpadders!
[21:18] <carlos> LaserJock: please, send it to rosetta@launchpad.net I'm leaving right now for some days
[21:18] <carlos> LaserJock: so danilo or jtv do the upload
[21:18] <LaserJock> carlos: ok thanks, and how often are new lang-packs created?
[21:19] <Kmos> OOPS-698EC85
[21:19] <carlos> LaserJock: it's supposed to be done monthly, although that's not always true... is better that you talk with pitti about it
[21:19] <Kmos> I'm at https://edge.launchpad.net/ubuntu/+source/elfutils/+publishinghistory and clicked on version 0.127-4 and it goes at https://edge.launchpad.net/ubuntu/gutsy/+source/elfutils/0.127-4
[21:19] <Kmos> but got OOPS
[21:20] <carlos> see you all!!
[21:20] <LaserJock> carlos: thanks again
[21:20] <carlos> you are welcome
[21:20] <carlos> enjoy!!!
[21:35] <ubotu> New bug: #172911 in launchpad "+publishinghistory causes OOPS when click in removed release version" [Undecided,New] https://launchpad.net/bugs/172911
[21:40] <xp_prg> hi all!  I created my vmware image with jeOS but it is working on my computer and not on another computer, can anyone help me?
[21:41] <xp_prg> I get error rejecting I/O to offline device
[21:41] <xp_prg> at the initramfs prompt
[21:43] <bigon> could someone schedule a new try to build https://edge.launchpad.net/ubuntu/hardy/+source/lablgtk2/2.10.0-2
[21:43] <bigon> ?
[21:44] <xp_prg> can anyone help me please:  https://answers.launchpad.net/ubuntu-jeos/+question/18996
[21:46] <daub> hi, i want to upload my package to the ppa. but i get following error:
[21:46] <daub> http://rafb.net/p/oc8gs094.html
[21:46] <xp_prg> does anyone see me?
[21:46] <daub> does anyone know something about it
[21:47] <daub> the output comes from dput
[21:47] <mpt> xp_prg, #launchpad is about the Launchpad site. It is not a jeOS support channel.
[21:49] <xp_prg> ok oops
[21:50] <ubotu> New bug: #172915 in launchpad "Download files view on a release does not show "Delete Files" button" [Medium,Confirmed] https://launchpad.net/bugs/172915
[21:56] <ubotu> New bug: #172919 in launchpad "Need a "Delete" icon" [Undecided,New] https://launchpad.net/bugs/172919
[22:30] <Fujitsu> bigon: You want to ask for a give-back on #ubuntu-devel.
[22:35] <bigon> thx
[22:54] <poolie> hi
[22:59] <cyberix> How long does it take after dput for packages to appear in PPA?
[23:00] <Fujitsu> cyberix: It processes them every 5 minutes.
[23:07] <cyberix> Will source packages be built automagically into binary packages?
[23:08] <Fujitsu> cyberix: Yes.
[23:09] <cyberix> How long does this take then?
[23:10] <Fujitsu> cyberix: Builds should be created within around 30 minutes of your upload, and then build soon (probably less than an hour) after that, depending on the load on the build machines.
[23:11] <cyberix> ok
[23:12] <cyberix> thanks
[23:12] <Fujitsu> Hm, I see the launchpad-bazaar merging feature is used so often. I just created the 34th merge...
[23:27] <somerville32> Fujitsu, My project will be using it heavily soon
[23:40] <dennda> can I somehow subscribe myself to all bugs that are reported for an entire project?
[23:41] <Fujitsu> dennda: Yes, just set yourself as the bug contact.
[23:42] <imbrandon> hrm i requested that my PPA have all packages removed ( prior to 1.1.11 rollout ) and they were marked "deleted" in the UI ( on edge ) within 24 hours, but now its been a week ( or more ) and they are still in the /pool , ideas ?
[23:42] <dennda> Fujitsu: how? (I am not the one who registered the project)
[23:43] <imbrandon> https://edge.launchpad.net/~imbrandon/+archive   and   http://ppa.launchpad.net/imbrandon/ubuntu are the relevant urls
[23:43] <Fujitsu> dennda: Ah, then I don't think you can do it yourself at the moment.
[23:43] <dennda> Fujitsu: The one who actually registered the project could do so?
[23:45] <dennda> (/me wonders why that isn't possible for users who are eager to fix bugs) :D
[23:45] <Fujitsu> dennda: Bug #3067.
[23:45] <ubotu> Launchpad bug 3067 in malone "Subscribe to a project's bugs" [Wishlist,Confirmed] https://launchpad.net/bugs/3067
[23:46] <dennda> I'll ask the 'owner' then. 
[23:46] <dennda> I see :)
[23:46] <Fujitsu> Being a bug contact implies additional privileges, unfortunately.
[23:47] <dennda> Oh, that thing has been registered a while ago...
[23:48] <Fujitsu> ?
[23:48] <dennda> thanks for the hints, Fujitsu. I will get some rest now
[23:48] <dennda> (the blueprint)
[23:48] <dennda> good night
[23:48] <dennda> and thanks again
[23:48] <Fujitsu> Ah, yes, LP development isn't entirely rapid.
[23:48] <Fujitsu> Night, and no problem.