[00:00] <MTecknology> what's dogfood for?
[00:00] <wgrant> MTecknology: Soyuz testing, mainly.
[00:01] <wgrant> beuno: I suspect a whole lot of missing icons aren't going to be noticed in the next couple of days, and after that they'll never be noticed...
[00:02] <MTecknology> wgrant: I just filed a missing icon bug yesterday :P
[00:02] <MTecknology> for deleting a series
[00:03] <wgrant> https://dogfood.launchpad.net/ubuntu/+source/firefox/1.5.dfsg+1.5.0.15~prepatch080614l-0ubuntu1 is missing the download icons from the files at the top, but there have been other changes to that page so it might be deliberate.
[00:15] <beuno> wgrant, hopefully grep will help me with that in my second pass at this work
[00:15] <beuno> and
[00:15] <beuno> we're going to go page by page top update their design to the 3.0 look
[00:15] <beuno> so whatever is missing should be cought in that process
[00:16] <wgrant> beuno: What's the difference between the 2.0 and 3.0 looks? I haven't seen anything new for 3.0...
[00:17]  * joey runs away as beuno grabs the bazooka.
[00:17] <joey> (it
[00:18] <joey> ti)
[00:19] <beuno> wgrant, it's cooking. We're moving to CSS grids and all kinds of 21st century technology
[00:19] <wgrant> beuno: ... in one release?
[00:19] <beuno> so the UI for it is being delayed until the proper templates are done
[00:19] <beuno> wgrant, no, in 3!
[00:19] <MTecknology> beuno: sounds scary
[00:20] <wgrant> beuno: But 3.0 is less than a month away!
[00:20] <wgrant> Or is the 3.0 UI not actually part of 3.0?
[00:21] <beuno> wgrant, it's fuzzy
[00:21] <beuno> MTecknology, it's actually beautiful
[00:21] <MTecknology> beuno: any samples?
[00:21] <beuno> MTecknology, not at the moment, no
[00:22] <beuno> but I will blog about it as soon as it's a bit more advanced
[00:22] <MTecknology> either way I'll see soon enough?
[00:22] <beuno> MTecknology, absolutely
[00:23] <beuno> wgrant, open sourcing is unaffected though
[00:23] <beuno> no matter what happens with the UI
[00:24] <wgrant> beuno: Well, that date is fuzzy too now.
[00:24] <wgrant> Which presumably means it will slip...
[00:24] <thumper> wgrant: we decoupled open sourcing and 3.0
[00:24] <thumper> wgrant: well...
[00:24] <wgrant> thumper: I see.
[00:24] <thumper> wgrant: one of the major things we had to do was done on Friday
[00:24] <thumper> wgrant: which is to move LP to the new bzr 2.0 format
[00:24] <thumper> which is still in alpha
[00:25] <thumper> it is causing some teething problems
[00:25] <thumper> as you'd expect
[00:25] <thumper> but we are shaking out the 2.0 bugs
[00:25] <wgrant> Right.
[00:25] <wgrant> Weekend-long reconciles are one complaint I've seen... ouch.
[00:25] <thumper> the repo size for the LP tree went from 1.3 gig to 180 meg fully packed or 250ish normal uses
[00:25] <MTecknology> you guys gonna hammer out every single lp bug w/ the 3.0 release? :P
[00:25] <thumper> wgrant: reconcile isn't yet optimised for 2.0 formats
[00:26] <thumper> which is one reason that is slow
[00:26] <ajmitch> thumper: that's a decent improvement on space though
[00:26] <thumper> MTecknology: no!
[00:26] <thumper> ajmitch: that it is
[00:26] <wgrant> thumper: Very nice.
[00:26] <wgrant> No branches eaten yet?
[00:26] <thumper> none eaten
[00:26] <ajmitch> are all branches getting migrated to that format?
[00:26] <thumper> a couple broken
[00:26] <thumper> ajmitch: eventually
[00:27] <thumper> but at least only broken in one place
[00:27] <thumper> yay DVCS
[00:27] <thumper> the new format makes many things much faster
[00:27] <wgrant> I can imagine. You've got a bit of history.
[00:27] <thumper> this large format move for LP branches caused some disruption at the end of last week and over the weekend
[00:28] <thumper> but really, much less than I feared
[00:28] <wgrant> I found it a bit strange that you did it at the end of week 3.
[00:28] <ajmitch> good, because I'm pulling the mariadb code at the moment & I hate to think how big it'll be on disk :)
[00:28] <thumper> well, the LOSAs are in London this week
[00:28] <thumper> and we've got a limited amount of time to iron out kinks
[00:29] <MTecknology> thumper: you should ue their proper name..
[00:29] <thumper> every day that we delayed potentially delayed open sourcing
[00:29] <thumper> and we care about that
[00:29] <thumper> ajmitch: open office is 4 gig :)
[00:30] <ajmitch> with the old or new format?
[00:30] <thumper> 1.9 rich root I think
[00:30] <thumper> not entirely sure
[00:30]  * thumper checks
[00:31]  * ajmitch isn't entirely convinced that this branch operation is actually doing anything useful at the moment
[00:31] <thumper> ajmitch: hah, new format
[00:32] <thumper> 262672 mainline revisions
[00:32] <ajmitch> that's a lot
[00:32] <kokachev> hi, guys.. Trying to upload over ftp I'm getting "[Errno 111] Connection refused".. also nmap -p21 ppa.launchpad.net reports
[00:32] <kokachev> "closed".. what's going on? could someone help me? thanks.
[00:33] <thumper> we've added a new column to record the branch size in bytes
[00:33] <thumper> kokachev: a would point you at an admin, but they are all on London time right now
[00:34] <kokachev> thumper: thanks.. I'll ask a little later..
[00:34] <wgrant> And cprov's in the same timezone now too :(
[00:35] <ajmitch> unfortunate timing
[00:37] <MTecknology> what does bzr pack do to the branch?
[00:43] <lifeless> it reorganises the database
[00:43] <lifeless> this reduces the number of separate files that need to be read to do operations
[00:43] <MTecknology> ok, thanks
[00:44] <lifeless> and in the bzr 2.0 format it can also increase compression. generally  though you should never needto run 'bzr pack' yourself.
[00:44] <lifeless> because bzr packs automatically to maintain things
[00:44] <wgrant> Does it reorganise the packs and re-groupcompress?
[00:45] <lifeless> which it?
[00:46] <wgrant> bzr pack
[00:46] <lifeless> it writes a single new pack with all the content from the repository, and in 2a formats recompresses all the texts in optimal-compression order
[00:46] <lifeless> the old packs then get obsoleted
[00:47] <wgrant> Right.
[00:55] <kokachev> is there any method (except ftp) to upload to launchpad? dput seems to support scp and sftp.. which one is supported by launchpad?
[00:59] <wgrant> kokachev: Just FTP for now.
[01:01] <kokachev> wgrant: got it.. Could 111 connection refused be caused by some security policy? because nmap -p21 ppa.launchpad.net turned from "open" to "closed" right after uploading attempt...
[01:01] <mwhudson> kokachev: ftp should be fixed now
[01:02] <kokachev> yepp.. fixed.. Thanks!
[02:42] <kokachev> Dear all.. Could someone point out, how to prepare same software version for two different ubuntu releases ( ex. Intrepid and Jaunty) to upload them to PPA..
[02:47] <persia> kokachev, Just upload to intrepid, and then copy to jaunty.
[02:49] <wjblack> Hi all!  I think I have my nifty new PPA set up correctly, but keep getting "Could not find PPA named 'r8169-2.6.30-backport' for 'bblack'".  I've tried various other iterations of the PPA name and userid with no luck.  Every invocation of dput seems to succeed.  And I'm stuck.  Anyone have an idea of where I might've gone wrong?
[02:51] <kokachev> persia: I tried that, but received rejection email.. I changed debian/changelog from "libid3tag (0.15.1b-11) intrepid; urgency=low" to libid3tag (0.15.1b-11) jaunty; urgency=low.. but email states, that ""Rejected:
[02:51] <kokachev> File libid3tag_0.15.1b-11.diff.gz already exists in ppa, but uploaded version has different contents
[02:51] <kokachev> Should I create ne version 0.15.1b-12 only for jaunty without any changes to source, but change only changelog?
[02:52] <persia> kokachev, not upload again.  copy.
[02:53] <MTecknology> Will 3.0 be able to do merges between branches?
[03:01] <kokachev> persia: thanks.. there is one more issue.. I'm uploading debian version for "unstable" distribution.. But this source is rejected. If I change unstable to jaunty , then everything is fine. Why I cannot upload debian sources?
[03:01] <persia> kokachev, Because there's no "unstable" series for Ubuntu.
[03:03] <MTecknology> kokachev: nope, we run stable stuff only :D
[03:04] <kokachev> persia: got it..
[03:04]  * MTecknology think about running jaunty on server 2mo prior to release :P
[03:04] <kokachev> MTecknology:  hehe..
[03:13] <kokachev> persia: trying to copy from jaunty to intrepid, but can copy only binaries. When i try to perform rebuild I'm getting error: The following source cannot be copied: libid3tag 0.15.1b-11 in jaunty (same version already has published binaries in the destination archive). Why?
[03:14] <RenatoSilva> How to create private branches?
[03:16] <persia> kokachev, Right.  Copy the binaries as well.
[03:18] <kokachev> persia: when i copy binaries and then install it on intrepid i'm getting dependency issue, because uploaded source was build for jaunty. maybe something is wrong with version name?
[03:18] <RenatoSilva> what's the purpose of ~launchpad-users?
[03:22] <MTecknology> RenatoSilva: private branches are commercial only, I forgot the link
[03:22] <RenatoSilva> :(
[03:23] <nhandler> MTecknology: s/commercial only/for the most part commercial only/
[03:23] <MTecknology> https://answers.edge.launchpad.net/launchpad/+faq/208
[07:49] <robin> Is jml here? urgent.
[07:50] <jml> robin, hi.
[07:50] <robin> jml: I saw your email. I am pushing my new branch now.
[07:50] <robin> jml:  But it takes a long time, and it is going on.
[07:51] <jml> robin, how long has it taken so far?
[07:51] <robin> jml: about 15 minutes. >150M now
[07:51] <jml> robin, what bzr version are you using ('bzr version')
[07:52] <jml> robin, and can you please pastebin the output of 'bzr info -v' on your local branch
[07:52] <robin> jml: 1.16
[07:52] <robin> jml:  branch: Branch format 7
[07:52] <robin> jml: I follow what you said.
[07:52] <jml> robin, also, I suggest killing the current push, deleting the branch on Launchpad, and pushing again with 'bzr -Dhpss lp:....'
[07:53] <jml> that will cause bzr to log more debug information in your ~/.bzr.log
[07:54] <robin> jml: -Dhpss? no push command?
[07:54] <jml> robin, oops :)
[07:54] <jml> bzr -Dhpss push lp:~foo/bar/baz
[07:55] <robin> jml: Do you think it is abnormal? I should to stop it?
[07:56] <jml> robin, Yes, I think it is abnormal. Please stop it and try again with the -Dhpss version of the command.
[07:56] <jml> (after deleting the partially pushed branch)
[08:11] <jml> robin, what's happening?
[08:22] <robin> jml: I repush it now.
[08:23] <jml> robin, ok cool.
[08:23] <robin> jml: >60M
[08:23] <robin> jml: Is it normal?
[08:23] <jml> robin, if it's still pushing after, say, 10mins then kill it and pastebin the .bzr.log somewhere
[08:30] <robin> jml: where should .bzr.log be?
[08:31] <jml> robin, in your home directory
[08:31] <jml> robin, are you using linux?
[08:31] <robin> jml: yes. Fedora
[08:31] <jml> robin, ~/.bzr.log
[08:32] <jml> robin, near the bottom of the file, there'll be a line similar to: 0.332  bzr arguments: [u'push', u'-Dhpss', u'lp:~jml/mysql-server/test-branch']
[08:32] <jml> there'll be a timestamp and a blank line preceding it.
[08:33] <jml> pastebin (e.g. paste.ubuntu.com) the contents of the log from there to the end of the file)
[08:33] <robin> jml: yes. Where do I post it?
[08:33] <jml> robin, paste.ubuntu.com.
[08:43] <jml> robin, you'll need to tell me the URL of the paste
[08:44] <robin> jml: ok, I want to wait for more 10 minutes.
[08:44] <jml> robin, no worries.
[08:51] <alkisg> If I have the .dsc, .tar.gz, .deb, and .changes files for an unreleased debian package (http://llama.freegeek.org/~vagrant/debian/UNRELEASED/),
[08:51] <alkisg> can I somehow upload them to my PPA without doing dpkg-source -x and without modifying debian/changelog ?
[08:52] <alkisg> (looking for the easiest way to update the PPA when new versions of the unreleased package come out)
[08:55] <noodles775> alkisg: good question. I'm not certain, but I *think* you are meant to at least update the changelog so that your email will be the one used if/when there are issues with the package... but it does seem a little strange to need to do so when you're not actually changing anything...
[08:55] <noodles775> al-maisan: ^^^^ any thoughts?
[08:55] <noodles775> or wgrant ^^^ (are you still around?)
[08:56] <wgrant> noodles775: I just got home.
[08:56] <wgrant> Let's see.
[08:56] <wgrant> alkisg: You can, but it's evil.
[08:56] <alkisg> Heh. How so?
[08:56] <wgrant> alkisg: If you give me a good reason not to add a changelog entry, I'll tell you.
[08:56] <noodles775> thanks wgrant :)
[08:57] <alkisg> wgrant: I'm able to copy .debs from other peoples PPAs. Why not from other people's sites?
[08:57] <alkisg> Why should I have to change the version, or put my name in a package I didn't make?
[08:57] <wgrant> alkisg: OK, that'll do. Add /seriesname to the end of the upload path. eg. ~wgrant/ppa/ubuntu/jaunty
[08:57] <alkisg> Heh! Thanks a lot, wgrant! :)
[08:58] <alkisg> (and thanks, noodles775)
[08:59] <noodles775> alkisg: np... it's an opportunity for me to learn too :)
[09:05] <wgrant> noodles775: You haven't had to dig into the dark evil of the backend much yet, I take it?
[09:05] <noodles775> wgrant: nope, I've been doing mainly front-end work... the little backend work that I've done hasn't required broad packaging knowledge either.
[09:06] <noodles775> wgrant: but I'm keen to get learn more packaging and understand soyuz from a packagers pov.
[09:19] <robin> jml: URL:http://paste.ubuntu.com/201933/
[09:19] <robin> jml: what is your bzr version?
[09:20] <jml> 1.17dev
[09:21] <jml> robin, looking at your paste now.
[09:24] <wgrant> Is it the shared repo being in an old format?
[09:29] <jml> robin, can you please paste the full output of 'bzr info -v' in your branch to paste.ubuntu.com
[09:30] <robin> jml: http://paste.ubuntu.com/201937/
[09:33] <jml> robin, ahhhh ok.
[09:34] <jml> robin, so, you've got an old format repository
[09:34] <robin> jml: Is it Branch format 7?
[09:34] <robin> jml: Do you know how to solve it?
[09:35] <jml> robin, yes, I do!
[09:35] <robin> jml: looking forward for your help.
[09:36] <jml> robin, gimme a second, I'm talking to three people at once and it's making me a little slow with all of them.
[09:36] <jml> sorry.
[09:36] <lifeless> jml: let me add a channel
[09:36] <lifeless> :P
[09:36] <robin> jml: never mind. I am waiting for you.
[09:36] <lifeless> jml: or perhaps I can help with one
[09:38] <jml> robin, in that directory, run 'bzr upgrade --1.9'
[09:38] <jml> robin, that'll take a while, but when it's done, you should be able to push your branch up quickly.
[09:38] <wgrant> How do I push a 2a branch to an existing project on Launchpad? It looks like it attempts to stack, then fails because they're incompatible formats.
[09:38] <robin> jml: bzr: ERROR: The branch format Meta directory format 1 is already at the most recent format.?
[09:38] <lifeless> wgrant: you can init, over sftp, the target branch.
[09:38] <wgrant> jml: Should robin do that in the branch, or repo?>
[09:38] <jml> in the repo
[09:39] <wgrant> lifeless: Ah, forgot that.
[09:39] <wgrant> lifeless: In fact, I think just pushing again should do it. Let's try.
[09:39] <wgrant> Yes, that worked.
[09:39] <lifeless> wgrant: also please file a bug that it doesn't 'just work but not stack'
[09:39] <wgrant> lifeless: Will do.
[09:41] <wgrant> lifeless: Somewhat similar to bug #328146
[09:41] <lifeless> yah same
[09:41] <wgrant> robin: Are you trying the upgrade in the repo, rather than the branch? /home/robin/gsoc/code is where you should be running it.
[09:41] <wgrant> lifeless: Thanks.
[09:42] <robin> wgrant: got it. It is upgrading now~
[09:43] <jml> :)
[09:51] <robin> jml: Conversion is done. And then?
[09:51] <jml> robin, on Launchpad, delete the failed attempt at pushing
[09:51] <jml> robin, then try again.
[09:52] <jml> (still use -Dhpss, just in case)
[09:55] <jml> robin, I have friends dragging me away from the computer.
[09:55] <robin> jml: ok.
[09:56] <jml> robin, if things still don't work out, either someone here might help...
[09:56] <jml> or you can use answers.launchpad.net/launchpad-code and mention my nick in the question.
[09:56] <robin> jml: OK. thx
[09:56] <jml> nyp
[09:56] <jml> np
[09:56] <jml> bye
[10:08] <Hamaryns> ping gmb
[10:09] <gmb> Hamaryns: Hi.
[10:09] <Hamaryns> Hi, I am trying to use your Trac migrate script, but it barfs, see https://answers.edge.launchpad.net/malone/+question/69864
[10:10] <Hamaryns> In the related answer, you said, one was allowed to ping you, so…
[10:11]  * gmb looks
[10:11] <Hamaryns> Do you also know about code imports from svn, or who should I ask about that?
[10:12] <gmb> Hamaryns: Unfortunately there aren't any codehosting guys online at the moment; I don't know all that much about it but maybe I can help. What do you want to know?
[10:13] <Hamaryns> There was a canceled import, I gave the incorrect uri initially, but now I am unable to request another import into the same branch, see https://code.launchpad.net/~vcs-imports/monasearch/trunk
[10:13] <Hamaryns> Seems like a bug in LP to me that there is no possibility to revive this.
[10:16] <gmb> Hamaryns: Well, you could have deleted the existing import, I think.
[10:16] <gmb> Hamaryns: I've updated it; it should run shortly.
[10:16] <wgrant> gmb: Only ~vcs-imports members can delete imports.
[10:17] <Hamaryns> actually, the instructions on the webpage mentioned above and the README of the trac importer differ: the first says to give the path to the db file, the latter to give the path to the directory
[10:17] <gmb> Once again, wgrant knows more than me. This is a base-state for the universe, I think.
[10:17] <gmb> wgrant: Thanks.
[10:17] <Hamaryns> yes, I did not see the option to delete it
[10:17] <gmb> Hamaryns: Right, I'll make sure that's corrected. It should be the path to the file.
[10:17] <gmb> Hamaryns: It looks as if you've got a missing attachment (the migrator was written with the assumption that nothing ever gets moved, changed or deleted and it gets easily upset
[10:18] <gmb> if something disappears)
[10:18] <Hamaryns> so can I request vcs-imports to delete it and restart the import request
[10:18] <gmb> Hamaryns: I've updated the import request for you, it should run shortly.
[10:18] <Hamaryns> Does that mean that in the Trac, there is an attachment defined but nothing there?  How can I fix that?
[10:18] <Hamaryns> great, many thanks
[10:18] <gmb> Hamaryns: In fact it's running now...
[10:19] <gmb> Hamaryns: I'm not sure. Can you paste an ls of the attachments directory for me on pastebin.ubuntu.com?
[10:20] <wgrant> gmb: I think I'll see just how little I know once I start poking at the code... I'd say you have the advantage there.
[10:21] <wgrant> Huh. That import failed with a very strange error.
[10:21] <gmb> wgrant: Don't be so sure. I spend a lot of time going "WTF?" before realising that I wrote the thing I'm looking at. I think there may have been mushrooms involved at some point, especially with checkwatches.
[10:21]  * gmb looks.
[10:22] <gmb> That's... bizarre.
[10:22] <wgrant> gmb: Yeah, I do that all the time too... "Which idiot wrote this code, and how did I miss it while reviewing? [...] Oh."
[10:22] <wgrant> Hamaryns: Are you attempting to move to bzr permanently?
[10:23] <Hamaryns> wgrant: yes, our current server is to be shut down
[10:23] <Hamaryns> I want to migrate the entire project to LP
[10:24] <wgrant> Hamaryns: You might be better off using bzr-svn as a one-time importer, then.
[10:24] <wgrant> Hamaryns: As a Launchpad VCS import loses some metadata, and is intended to run continuously and be read-only.
[10:25] <wgrant> Particularly since cscvs doesn't like it, bzr-svn looks like a good option here.
[10:25] <Hamaryns> gmb: http://pastebin.ubuntu.com/201969/
[10:25] <gmb> Hamaryns: I second that.
[10:25] <Hamaryns> aha, I didn’t know that
[10:25] <Hamaryns> can you give me a link to start that?
[10:25] <wgrant> Hamaryns: So, just install bzr-svn, and 'bzr co svn://blah'
[10:27] <wgrant> Hamaryns: If you have svn branches, you can import all of them using 'bzr svn-import'
[10:27] <gmb> Hamaryns: I've just tried using bzr-svn locally for your svn trunk and it works fine, FTR.
[10:27] <Hamaryns> Ok, I’ll do that
[10:27] <Hamaryns> and then how do I push it into LP?
[10:28] <Hamaryns> and can you then also cancel those imports (both monasearch/trunk and /visualization)?
[10:28] <wgrant> Hamaryns: Just like a normal branch. bzr push lp:~userorteam/projectname/branchname
[10:28] <Hamaryns> cool, I’m new you now, thanks
[10:28] <gmb> Hamaryns: I'll delete both of them for you.
[10:28] <gmb> bear with me...
[10:29] <gmb> Hamaryns: Can you unlink the trunk series from the /trunk import please? I don't have permission to break that link.
[10:29] <robin> It still does not work.......
[10:29] <Hamaryns> hm, I see there is svn2bzr as well, any difference?
[10:30] <wgrant> robin: What does it do? Still takes ages?
[10:30] <robin> wgrant: Yes...It drives me crazy.
[10:31] <gmb> Hamaryns: I think svn2bzr is deprecated in favour of bzr svn-import, but I could be wrong.
[10:31] <Hamaryns> gmb: what do you mean unlink, how?
[10:31] <wgrant> robin: Can you pastebin the latest stuff from .bzr.log again?
[10:32] <Hamaryns> ok, trying bzr-svn
[10:32] <wgrant> gmb: I thought svn2bzr was long-dead, but its trunk was committed to just a couple of weeks ago. Strange.
[10:32] <wgrant> Most people do seem to use bzr-svn now, though.
[10:33] <gmb> Hamaryns: If you go to https://edge.launchpad.net/monasearch/trunk/ you should see a "Change branch" link under the "Code for this series" heading. CLick that, then clear the field on the form that follows it and hit "Update"
[10:33] <robin> wgrant: Must add -Dpss args?
[10:33] <wgrant> robin: Ah, yes.
[10:33] <wgrant> robin: And make sure you're not pushing to an existing branch.
[10:33] <wgrant> robin: You *must* delete the branch on Launchpad before repushing, if the first push failed.
[10:34] <robin> wgrant: yes, I know
[10:34] <Hamaryns> gmb: done
[10:35] <gmb> Hamaryns: Okay, I've deleted both branches for you.
[10:35] <gmb> Hamaryns: WRT your trac migrator issue, try appending 'tickets/' to the attachment path. It looks like it's looking one directory too high.
[10:37] <Hamaryns> gmb: that seems to have worked, apart from the warning which was already there in the other tries
[10:37] <Hamaryns> ok, wo where do I post the xml
[10:38] <Hamaryns> ah, and can I import the Trac wiki into LP as well?  Or at least some pages of it?
[10:38] <Hamaryns> or will that be done automatically?
[10:38] <Hamaryns> I guess not
[10:38] <wgrant> Launchpad doesn't do wikis yet.
[10:38] <Hamaryns> right, that’s a shame\
[10:38] <gmb> Hamaryns: Email your xml to me. I'll pm you my address.
[10:38] <Hamaryns> so I need to maintain my own homepage for the project
[10:40] <robin> wgrant: Source branch format does not support stacking, using format:
[10:40] <robin>   Branch format 7
[10:40] <wgrant> robin: That's a good sign.
[10:40] <robin> wgrant:  is it fine?
[10:40] <wgrant> robin: That's fine.
[10:40] <wgrant> It means it's trying to stack...
[10:40] <robin> wgrant: It is finding revisions
[10:40] <wgrant> robin: OK. How long has it been going?
[10:41] <wgrant> Hopefully it will find that most of the revisions are already there, and just push the new ones.
[10:41] <robin> wgrant: I rerun it
[10:41] <wgrant> That warning is a very good sign, as it means it's at least trying to do the right thing.
[10:41] <robin> wgrant: Last time, I is going at least 10 minutes.
[10:42] <gmb> Hamaryns: Yes, at least for now.
[10:42] <Hamaryns> gmb: the file is on its way
[10:43] <gmb> Hamaryns: Thanks. I'll try to attend to it today, but we're releasing the new version of LP tomorrow so I doubt I'll be able to do much until after that. I'll check that the data's importable, though, and let you know if there are any problems.
[10:43] <Hamaryns> cheers, much thanks, really
[10:43] <Hamaryns> on to the next problem:
[10:43] <Hamaryns> http://pastebin.ubuntu.com/201989/
[10:44] <wgrant> Intriguing. That could be the same issue as cscvs had.
[10:44]  * wgrant tries it.
[10:48] <wgrant> cprov: Is it deliberate that sources are hidden from IArchive:+index when they have published binaries?
[10:49] <cprov> wgrant: the +index page only cares about the source publishing status, atm
[10:49] <cprov> wgrant: was the source superseded ?
[10:49] <wgrant> cprov: OK.
[10:49] <wgrant> cprov: It was, yes.
[10:51] <wgrant> Hamaryns: Any idea around which rev it failed?
[10:51] <wgrant> I'm almost up to 100 here, and it's going fine.
[10:51] <Hamaryns> no idea
[10:52] <wgrant> Hamaryns: OK, I guess I'll see how this goes.
[10:52] <gmb> Hamaryns, wgrant I've seen a couple of unicode warnings but I'm up to r480 with no ill efects...
[10:52] <wgrant> bzr-svn 0.6.2, subvertpy 0.6.1, bzr 1.16
[10:52] <LarstiQ> nice and current :)
[10:52] <wgrant> Hamaryns: I guess if it works for gmb, you can probably convince him to push the branch and then just copy off that.
[10:53] <gmb> Hamaryns, wgrant: Yes, I can do that, no problem.
[10:53] <gmb> Assuming this finishes, of course...
[10:53] <Hamaryns> are you guys actually doing svn-import on my svn repo?
[10:53] <Hamaryns> It’s about 600 revs, so you’re almost there
[10:53] <Hamaryns> feel free to push it to lp
[10:54] <Hamaryns> I guess I’ll have to grant you some rights on the MS project?
[10:54] <wgrant> LarstiQ: Not any more! You just uploaded a new subvertpy to the subvertpy PPA. I only bring this up because it's the first time I've browsed that PPA, but I managed to hit it 30 seconds after the first upload in 6 months. Nice timing.
[10:54] <wgrant> Hamaryns: No, anybody can push a branch to a project.
[10:54] <Hamaryns> How can I make someone else maintainer?
[10:54] <Hamaryns> aha, good
[10:54] <Hamaryns> in what sense is it then controlled?
[10:54] <wgrant> Hamaryns: That's part of the beauty of Bazaar and Launchpad: I as a random user can make my own branch of a project.
[10:54] <LarstiQ> wgrant: ah well, I'm not done with subvertpy yet. But bzr-svn I did yesterday.
[10:54] <wgrant> Hamaryns: You can set the development focus (aka. trunk) branch for a project.
[10:55] <Hamaryns> right
[10:55] <Hamaryns> and then?
[10:55] <wgrant> Hamaryns: What do you mean?
[10:55] <LarstiQ> Hamaryns: and people can't push to branches of teams they are not a member of
[10:55] <Hamaryns> do I have to do some reviews or something?
[10:56] <wgrant> What LarstiQ said. Branches can only be written to by their owner (or members of the owning team). Users can then request a merge from their branch into yours, and you can review it and do the merge if you wish.
[10:56] <LarstiQ> Hamaryns: so I can push to ~larstiq/monasearch/foo, but not to ~monasearch/monasearch/foo (if there is a monasearch team)
[10:56] <Hamaryns> it’s starting to dawn on me
[10:57] <Hamaryns> how do I create a team?
[10:57] <wgrant> Hamaryns: https://launchpad.net/people/+newteam
[10:57] <wgrant> https://help.launchpad.net/ is useful if you're ever unsure about anything.
[11:02] <gmb> Hamaryns: You can branch your trunk branch by doing `bzr branch lp:~gmb/monasearch/trunk` and the visualization branch by doing `bzr branch lp:~gmb/monasearch/visualization`.
[11:03] <gmb> Hamaryns: And then push them to wherever you need them to be.
[11:03] <Hamaryns> right, great, many thanks
[11:07] <Hamaryns> Is this the correct command? bzr push bzr+ssh://hamaryns@bazaar.launchpad.net/monasearch/trunk and how do I know it pushes the trunk branch only?
[11:13] <wgrant> Hamaryns: You need a team or person name in there, and you can make it much shorter using lp:. For example, I'd do 'bzr push lp:~wgrant/monasearch/trunk'
[11:13] <wgrant> That would yield a branch writable only by me.
[11:13] <Hamaryns> Right, so ‘bzr push lp:~monasearch/monasearch/trunk’ ?
[11:14]  * LarstiQ nods at Hamaryns 
[11:14] <wgrant> Hamaryns: If there is a team named monasearch, yes.
[11:14] <Hamaryns> and I do this in the root directory of the particular branch I want to push
[11:14] <wgrant> Yep.
[11:20] <Hamaryns> It seems like you can do this via the web interface as well.  I requested and approved a merge, but how is it now being merged?
[11:21] <wgrant> Hamaryns: That's just for reviewing merges. At the moment, you have to either do the merge manually, or configure a robot to do it automatically when a proposal is approved.
[11:22] <Hamaryns> this is getting complex.  Okay, how do I do that robot thing?  And with manually, you mean, with bzr from the command line?
[11:22] <wgrant> Also, if you look at https://code.launchpad.net/monasearch, you should see a message telling you to set the development focus branch, I think.
[11:22] <wgrant> Hamaryns: I'd go with merging manually for now, until you get the feel of things.
[11:22] <wgrant> Hamaryns: And yes, merging manually is done with bzr on the command line.
[11:23] <Hamaryns> okay, thanks again
[11:23] <Hamaryns> that worked now
[11:24] <Hamaryns> great, LP even registers that I did the merge, this is so cool
[11:25] <Hamaryns> gmb: did you import each revision of those two branches?
[11:25] <Hamaryns> I suppose so
[11:25] <gmb> Hamaryns: Yes.
[11:26] <gmb> Well, unless bzr-svn was lying to me.
[11:27] <Hamaryns> Ok, I have to get bzr-svn working as well, to import some older tags, I don’t want to bother you with that
[11:27] <Hamaryns> You’ve been a great help
[11:28] <wgrant> Hamaryns: Tags are done differently in the bzr world.
[11:28] <wgrant> A tag is just an extra label attached to a revision.
[11:29] <Hamaryns> Ok.  In svn, it is a copy, so basically also just a revision, but you imported only two branches, not the whole tags directory, so I guess I still have to import the tags directory and pick the relevant stuff from there
[11:30] <wgrant> Hamaryns: Is there anything there apart from the name<->revision information?
[11:31] <wgrant> Importing a tag as another branch probably doesn't make sense.
[11:31] <Hamaryns> I did some small bugfixes on some tags, yes
[11:31] <wgrant> But it depends how you've used tags.
[11:31] <wgrant> Ah.
[11:31] <Hamaryns> so they are no longer identical to a trunk revision
[11:31] <wgrant> So, try getting a new bzr/bzr-svn.
[11:31] <wgrant> Are you using Ubuntu?
[11:31] <Hamaryns> openSUSE 11.1
[11:31] <Hamaryns> I am trying svn2bzr now and it is running fine\
[11:31] <wgrant> Ah. I can't help you with packages for that, sorry.
[11:32] <wgrant> Using svn2bzr won't get you a branch that can merge with the bzr-svn branches.
[11:32] <Hamaryns> I just did zypper in bzr-svn and it worked fine
[11:32] <Hamaryns> no, but it will give me a usable repo, won’t it?
[11:32] <wgrant> It probably will. But what will you do with it then?
[11:33] <Hamaryns> I have a lot of stuff besides MonaSearch in that repo, mostly private, and I can use the bazaar repo locally then
[11:33] <Hamaryns> and I guess I can then checkout branches from that local repo and merge them into LP?
[11:34] <wgrant> It doesn't quite work like that.
[11:34] <wgrant> bzr-svn will generate bzr revision IDs different to those generated by svn2bzr.
[11:35] <wgrant> So you won't easily be able to do a merge with history from the svn2bzr branches.
[11:35] <Hamaryns> dammit, it crashed
[11:35] <wgrant> Because they will look like totally separate branches.
[11:35] <Hamaryns> right
[11:35] <wgrant> I suggest you just upgrade your bzr-svn.
[11:36] <Hamaryns> ok, I guess that would be bzr branch lp:bzr-svn?
[11:36] <wgrant> I suppose you could do that. I'd first try to find a package, though, as you probably installed using a package before.
[11:37] <Hamaryns> I did.  I found 3 possibilities: 0.5.4-3.1, 0.4.17-12.1 and 0.4.17-1.1, which should I take?
[11:38] <wgrant> Those are all pretty old.
[11:38] <wgrant> Which do you have now?
[11:39] <LarstiQ> Hamaryns: there are no 0.6.x packages? :/
[11:40] <Hamaryns> http://software.opensuse.org/search?p=1&baseproject=ALL&q=bzr-svn
[11:44] <Hamaryns> I have 0.4.17
[11:45] <wgrant> Try 0.5.4
[11:45] <wgrant> We can hope that will work better.
[11:45] <wgrant> And you only have to use it once.
[11:46] <Hamaryns> can I find out from the command line which version I have?
[11:46] <wgrant> bzr plugins
[11:46] <Hamaryns> svn2bzr crashed with the message that it had an invalid commit message, I suppose that is because it contained Windows line-endings
[11:47] <wgrant> cscvs, svn2bzr and old bzr-svn all seem to choke on that.
[11:47] <wgrant> I'm not sure it's the line-endings, though.
[11:47] <Hamaryns> damimit
[11:47] <Hamaryns> does it make sense to file a bug, or is it known?
[11:47] <wgrant> It's fixed in bzr-svn.
[11:47] <wgrant> svn2bzr is a bit dead.
[11:47] <Hamaryns> right
[11:47] <wgrant> And cscvs is... well... cscvs.
[11:48] <Hamaryns> I would like to use it though.  Although I can of course just use the svn dump to populate a local svn repo and stick with that
[11:48] <wgrant> You'd like to use what, exactly?
[11:48] <wgrant> svn2bzr?
[11:49] <Hamaryns> yes
[11:49] <wgrant> I'm fairly sure you want to use bzr-svn instead. Why do you want to use svn2bzr?
[11:49] <Hamaryns> as I described above, to create my own local Bazaar repo for my private stuff
[11:49] <wgrant> Can't you use bzr-svn for that?
[11:50] <wgrant> (assuming that we can get it to not crash)
[11:51] <Hamaryns> can I?
[11:52] <LarstiQ> sure
[11:52] <Hamaryns> anyway, I tried to install the 0.5 version and now bzr plugins says it cannot read the svn plugin
[11:52] <Hamaryns> good, I’ll forget about svn2bzr then
[11:56] <wgrant> Hamaryns: Does it give any error?
[11:56] <wgrant> I mean, a more meaningful one.
[11:56] <Hamaryns> Unable to load plugin 'svn' from '/usr/lib/python2.6/site-packages/bzrlib/plugins'
[11:57] <wgrant> Hamaryns: Open up python, and run 'import bzrlib.plugins.svn'
[11:57] <wgrant> I wonder if your subvertpy is too old.
[11:57] <Hamaryns> http://pastebin.ubuntu.com/202041/
[11:58] <LarstiQ> ehm, what version of bzr are you using?
[11:59] <Hamaryns> 1.11
[11:59] <Hamaryns> http://pastebin.ubuntu.com/202043/
[12:00] <wgrant> Filters are new in 1.14, aren't they?
[12:00] <LarstiQ> http://bazaar-vcs.org/BzrForeignBranches/Subversion#releases has the compatibility list
[12:01] <wgrant> One would expect that to be represented in the RPM dependencies.
[12:03] <Hamaryns> I am installing bzr 1.16 now
[12:11] <Hamaryns> oh man
[12:13] <Hamaryns> ok, so now bzr plugins mentions svn again, but bzr svn-import says I need subvertpy and easy_install subvertpy gives an error that apr-config is not found
[12:13] <wgrant> It's probably libapr-dev or something similar. But I'm not sure about OpenSUSE naming conventions.
[12:14] <Hamaryns> ah, right, I need the devel versiobn
[12:14] <Hamaryns> libapr1-devel
[12:14] <Hamaryns> does it need svn-devel as well??
[12:16] <Hamaryns> seems so
[12:16] <Hamaryns> bzr: ERROR: The API for "<module 'bzrlib' from '/usr/lib/python2.6/site-packages/bzrlib/__init__.pyc'>" is not compatible with "(1, 14, 0)". It supports versions "(1, 15, 0)" to "(1, 16, 0)".
[12:18] <wgrant> Argh. Looks like bzr-svn is fairly tightly version-locked.
[12:18]  * wgrant just uses the Ubuntu packages, trusting people like LarstiQ to work out this mess.
[12:19] <wgrant> Hamaryns: So, cd into ~/.bazaar/plugins, and try 'bzr co lp:bzr-svn svn'
[12:24] <Hamaryns> um, yes but then I need newest bzr as well, won’t I?
[12:24] <wgrant> 1.16 is the latest release.
[12:24] <wgrant> So hopefully bzr-svn hasn't gone past that yet.
[12:26] <Hamaryns> cool, it’s running now
[12:26] <wgrant> Otherwise just grab the latest bzr-svn tarball. And preferably convince somebody to maintain a repo of bzr stuff for openSUSE
[12:30] <Hamaryns> There is https://build.opensuse.org/project/show?project=home:maw:bzr, and there are several others that have a private branch
[12:30] <Hamaryns> it has bzr 1.16, but bzr-svn 0.4.17
[12:31] <wgrant> How strange.
[12:34] <Hamaryns> for example https://build.opensuse.org/project/show?project=home:LenzGr:branches:home:maw:bzr has branched maw’s bzr-svn and provides 0.5.4, but as I said, I tried installnig that and it didn’t quite work
[12:35]  * LenzGr heard his name
[12:35] <wgrant> That was because of the different bzr version, wasn't it?
[12:36] <LenzGr> Funny, I was just about to check if there is a newer version of bzr-svn...
[12:37] <wgrant> LenzGr: When you do package them, perhaps add versioned dependencies on the right version of bzr.
[12:37] <wgrant> (as shown on http://bazaar-vcs.org/BzrForeignBranches/Subversion#releases)
[12:37] <LenzGr>  wgrant: good point
[12:40]  * LenzGr updates his package repository to 0.6.2
[12:48] <LarstiQ> LenzGr: yay :)
[12:49] <Hamaryns|weg> so fast?
[12:49] <LarstiQ> LenzGr: I'm packaging bzr-svn for the Launchpad ppa, do you want me to ping you on new releases?
[12:49] <LenzGr> LarstiQ: That'd be appreciated! Can I subscribe to an announce list?
[12:50] <LarstiQ> LenzGr: bazaar-announce would be the appropriate list, but bzr-svn releases don't always get announced :/
[12:50] <LarstiQ> LenzGr: I'll ask jelmer if I should/could do bzr-svn release announcements too
[12:51] <LenzGr> I should probably get on bazaar-announce anyway, as I also maintain bzr on the openSUSE Build Service :)
[12:51] <LenzGr> LarstiQ: I think it would make sense
[12:51] <LarstiQ> cool
[12:52] <LenzGr> LarstiQ: By the way, https://launchpad.net/bzr-svn does not show the 0.6.2 release, either...
[12:52] <Hamaryns> LenzGr: you need a dependency from subvert also
[12:54] <LenzGr> Hamaryns: What is "subvert"?
[12:55] <LarstiQ> LenzGr: subvertpy are the subversion bindings bzr-svn uses
[12:56] <Hamaryns> right, that’s what I meant
[12:56] <LenzGr> Ah, I see
[12:56] <Hamaryns> I don’t recall precisely, but there were some missing dependencies, and I was not able to use your currently packaged 0.5.4 release
[12:58] <LenzGr> Hamaryns: It now requires:
[12:58] <LenzGr> bzr >= 1.15
[12:58] <LenzGr> bzr-rebase
[12:58] <LenzGr> subversion-python >= 1.4.4
[12:58] <wgrant> LenzGr: subversion-python == subvertpy?
[12:59] <lifeless> wgrant: no, they are different
[12:59] <lifeless> at least on ubuntu
[12:59] <LenzGr> wgrant: No, that's libsvn_swig_py
[12:59] <Hamaryns> LenzGr: I just tried with Yast, but it doesn’t find the 0.6 version yet?
[12:59] <LenzGr> Hamaryns: Give it a moment, the build farm needs to compile and distribute the packages first :)
[13:00] <wgrant> lifeless: Right, that's what I thought...
[13:08] <Hamaryns> aha
[14:01] <ersi> When does projects disappear from translations.launchpad.net/~user? Do they ever?
[14:23] <philn> heya, nice to see you reused my trac->lp migrator ;)
[14:24] <philn> was quite hackish around the edges tho
[14:54] <robin> jml: I am failed again.....
[15:26] <kiko> ersi, disappear?
[15:28] <ersi> kiko: I'm wondering 'if'/'when' they disappear from the user translation listing. I mean, if one has been inactive in a project etc. Sort of like the Launchpad Karma
[15:28] <kiko> not really
[15:45] <rick_h__1> anyone know what the lead time is usually on an email to verify the gpg key?
[15:46] <rick_h__1> I'm hitting an hour, checked spam folders, checked email spelling (long time account and I get other emails to it fine)
[15:50]  * maxb does not recall any email being involved when adding his gpg key
[15:51] <SamB> maxb: they send you one, I think?
[15:51] <SamB> to make sure you can decrypt it, possibly
[15:52] <SamB> rick_h__1: have you tried having it re-sent ?
[15:52] <rick_h__1> SamB: no, haven't tried having it resent
[15:52] <rick_h__1> yea, you get an encrypted email to verify you own the key
[15:53] <SamB> I remember something like that
[15:53] <maxb> hmm
[15:53] <maxb> Ah.
[15:53] <rick_h__1> canceled and retry
[15:53] <maxb> Last key I added was a sign-only one, that's probably why I didn't get a mail
[15:53] <rick_h__1> see if it works this time
[15:53] <SamB> maxb: ah, yeah, that would make it difficult for them to send you an encrypted email
[15:54] <SamB> but they could send you one with text for you to sign
[15:54] <SamB> well, I expect the entire email they send isn't encrypted -- there were probably some instructions above the encrypted portion
[16:09] <rick_h__1> hmmm, I think it hates me. Still no luck on the email
[16:22] <rick_h__1> anyone know how to turn off redirection when you're on edge.?
[16:22] <rick_h__1> not seeing the "cancel redirection for 2hrs" link
[16:56] <flacoste> rick_h__1: go to the front page
[16:56] <flacoste> rick_h__1: launchpad.net
[16:57] <rick_h__1> flacoste: ah, ok. I didn't get it when I clicked the link home there
[16:57] <flacoste> rick_h__1: i think it's one https://launchpad.net/
[16:58] <flacoste> not on https://edge.lauchpad.net/
[16:58] <flacoste> since edge doesn't do redirect
[16:58] <flacoste> only launchpad.net does
[16:58] <flacoste> but i agree it's confusing
[16:58] <flacoste> please file a bug about showing the disable button on the edge home page also
[17:01] <rick_h__1> thanks, ok. 3rd try to get the email. This time not on the beta site
[17:08] <rick_h__1> yay, got my launchpad email now. Must be something broken on the beta site
[17:41] <rick_h__1> flacoste: thanks, all good. Bug report filed on the redirection.
[18:19] <flacoste> rick_h__1: thanks
[18:55] <kirkland> is there anyone around to help me with some vcs-auto-imports questions?
[19:13] <kiko> kirkland, always. what's up?
[19:13] <kirkland> kiko: hiya, so the qemu upstream project just announced that they're going to start using launchpad for bug tracking
[19:13] <kirkland> kiko: i helped get them setup
[19:14] <kirkland> kiko: they're a very git-centric community, so I've been trying to setup an auto vcs import of their git tree into bzr for a couple of weeks now
[19:15] <kirkland> kiko: the initial import worked, but the auto updates are broken;  i think jelmer said that he's uploaded a fix, so I'm in a holding pattern waiting for LP to pick up this outside fix
[19:15] <kirkland> kiko: ...
[19:15] <kirkland> kiko: in the mean time, i'd like to try and automate it myself, perhaps
[19:16] <kirkland> kiko: i'm curious if anyone else has run into similar problems and how they have solved them
[19:16] <kirkland> kiko: i have the git fast-export | bzr fast-import working
[19:17] <kiko> kirkland, that's awesome
[19:17] <kiko> kirkland, do you have the bug number for the import?
[19:17] <kirkland> kiko: let me grab it
[19:18] <kiko> for the import issue, sorry
[19:21] <kirkland> kiko: okay, the broken import is https://code.edge.launchpad.net/~vcs-imports/qemu/git
[19:22] <kirkland> kiko: checked my email archive, and irc, turns out this has been an irc discussion only;  i can go file a question/bug now, if you like
[19:23] <kiko> kirkland, do you know the revision in which this fix was landed?
[19:23] <kirkland> kiko: Jun 16 22:03:50 <jelmer>        kirkland: confirmed that qemu also imports fine now
[19:23] <kiko> kirkland, "now"?
[19:23] <kirkland> kiko: a timestamp is the closest i have, at the moment
[19:24] <kiko> okay
[19:24] <kirkland> kiko: i pinged jelmer in #bzr, i can open a question in the meantime and try to track it down there
[19:24] <kirkland> kiko: i found it!
[19:24] <kiko> kirkland, can you or jelmer tell me a revision on https://code.edge.launchpad.net/~bzr/bzr-git/trunk ?
[19:24] <kiko> where it's fixed?
[19:24] <kirkland> kiko: question #73651
[19:25] <kirkland> kiko: sorry, where i filed this;  thumper indicates that he has a branch with the fix
[19:25] <kiko> kirkland, should be fixed tomorrow morning then
[19:25] <kiko> when the rollout happens
[19:25] <kirkland> kiko: perfect
[19:25] <kirkland> kiko: excellent, thanks for your help, man
[19:25] <kiko> kirkland, if it isn't can you update that question again and ping thumper/jelmer?
[19:25] <kiko> kirkland, no problem
[19:25] <kirkland> sure thing
[19:25] <kiko> kirkland, awesome that qemu is interested!
[19:26] <kirkland> kiko: yessir, it's going to really be a good thing for qemu, and ubuntu
[19:26] <kiko> kirkland, congratulations and good work in getting them onboard
[19:26] <kirkland> kiko: cheers
[19:27] <kiko> kirkland, bzr-git itself is rolled out onto our import boxes, which is why it is usually only updated on rollouts
[19:28] <kirkland> kiko: i updated that question, https://answers.edge.launchpad.net/launchpad-code/+question/73651
[19:29] <kirkland> kiko: just to make sure that that fix is in tomorrow's batch
[19:29] <kiko> sure
[19:57] <xpd259> hiya how do i setup a personal ppa in dput.cf
[19:58] <kiko> xpd259, help.launchpad.net/PPA
[19:58] <xpd259> kiko: i've followed that and i thought id set it up right but just got an error email saying ppa doesn't exist
[19:59] <kiko> xpd259, does your PPA exist? :)
[19:59] <kiko> what URL
[19:59] <xpd259> https://launchpad.net/~xpd259/+archive/ppa
[20:00] <nhandler> kiko: Do you think it would be beneficial to add the content from http://blog.launchpad.net/ppa/simplifying-dputcf-for-multiple-ppas (or link to it) on the help.launchpad.net/PPA page?
[20:01] <kiko> nhandler, link to it is a good idea
[22:53] <rodrigo_> rockstar: around?
[22:53] <rockstar> rodrigo_, hi.
[22:54] <rodrigo_> rockstar: I've been talking with statik about doing code review for some code we have in gnome's git repo, just like we do for ubuntuone
[22:55] <rodrigo_> rockstar: and tried to join the launchpad-users list but I need to be a team member
[22:55] <rodrigo_> (I was going to ask in the list how we could do that)
[22:55] <rockstar> rodrigo_, well, I'd first suggest joining the team and being on the list.  I think there's real value in having this be on list.
[22:56] <rodrigo_> yeah, so how do I join the team?
[22:57] <rodrigo_> ah, 'join the team' link I guess :)