/srv/irclogs.ubuntu.com/2011/01/07/#launchpad.txt

wgrantyofel: svn: No such revision 1620800:00
wgrantyofel: Their SVN repo says it was last changed in 2006.00:00
wgrantThat sounds potentially wrong.00:01
yofelhm, indeed, I'll check the repos00:03
yofelright, the svn repository got corrupted, can someone approve the new import? https://code.launchpad.net/~scribus/scribus/trunk00:28
mwhudsonyofel: done00:29
yofelthanks!00:29
tgall_foowgrant, ok thanks ...  let me know if i need to take action to reupload that build again or what have you ...00:44
wgranttgall_foo: I've tracked down and fixed the bug. We'll be able to reprocess the upload once it's deployed.00:45
wgranttgall_foo: You'll get one last email about it.00:45
tgall_foowgrant, great, thanks!   amazingly fast work!00:46
wgranttgall_foo: Sorry about all the email.00:46
cody-somervillehttp://launchpadlibrarian.net/61829075/vcs-imports-django-trunk.log <-- hmmm... whats the "Getting exising bzr branch from central store." mean?01:10
mwhudsoncody-somerville: launchpad doesn't import the branch from scratch each time01:13
cody-somervillemwhudson, the branch has never been successfully imported in the first place :(01:13
cody-somervillemwhudson, https://code.launchpad.net/~vcs-imports/django/trunk01:13
mwhudsonthe log message is printed before it knows that01:13
cody-somervilleok, so next question: why is the import failing?01:14
mwhudsoncody-somerville: a strange error, on the face of it01:14
mwhudsoncody-somerville: ask jelmer, i guess01:14
=== Ursinha is now known as Ursinha-zzz
=== thumper changed the topic of #launchpad to: Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/
geserwhen I branch from lp:ido where should I push my branch for later merging? (bzr: ERROR: Permission denied: "~geser/ido/fix-linking-no-add-needed/": : You cannot create branches in "~geser/ido")10:25
janimoin which cases can failed builds not be retried on LP? If a package failed on 10.10 but was not updated since seems to be an example10:26
wgrantjanimo: You'll need to do a fresh upload.10:27
wgrantYou can't retry the maverick build, since that would attempt to upload to maverick, which would be... bad.10:27
janimowgrant, ok, so this is the case for build1 version uploads?10:27
wgrantjanimo: One case for them, yes.10:27
janimoI understand 10.,10 is closed10:27
janimowgrant, I wonder if it made sense to try rebuilding FTBFS archs when moving binaries to a new release10:28
janimoauotmatically in soyuz I mean10:28
wgrantjanimo: We used to do that.10:28
wgrantBut the script to do so has bitrotten.10:28
geserjanimo: I asked the same once in the past and got asked back "what makes me believe that it will build now?"10:29
janimogeser, well, different toolchain woudl be the most obiosu answer10:29
wgrantThe utility of automatically trying the rebuild is limited. Allowing a rebuild would be nice.10:30
janimobut ithe chances of building may imporve in time (deps being ready). So at beginning of the cycle it would still fail, but in a month not10:30
janimobut it is probably a not too frequent case to worry about10:30
janimojust annoying a bit, to upload no changes, when LP could be a bit smarter about it10:30
janimolike offer rebuild on current cycle if the package was broken all the time10:30
StevenKWhy should LP track the time since a new series was started? It doesn't sound like it offers much value10:31
wgrantgeser: The project still has a private branch policy, restricting non-DX people from pushing branches.10:31
janimowgrant I agree automatic, while useful would mean too much resources used with probably little gain10:31
wgrantgeser: You should probably ask DX to convince an LP admin to relax that policy.10:32
janimoStevenK, not the time. The retry should be allowed manually just in case someone retries after a while10:32
geserwgrant: thanks10:32
wgrantgeser: https://code.launchpad.net/ido should say this.10:32
wgrantBut instead it just says they're public... not sure what's going on there.10:32
StevenKjanimo: Can you restate, that doesn't make sense?10:33
janimoStevenK, no time tracking was implied by me. I said after 3 months into the cycle, chances of a package building (same version) are higher than at the beginning, if it ended the rpevious cucle in FTBFS10:34
janimoso a 'Retry build' button would be nice10:34
fta2wgrant, hi, read your comment about the arch-ppa bug. how can i workaround this?10:34
janimofiling a bug anyway10:34
wgrantfta2: What problems is it causing you?10:35
fta2wgrant, bugs stats for one, and too many iterations10:36
fta2wgrant, like, say a py deb, arch all, with 10 dls, is exposed with 10 for i386 + 10 for amd64 + 10 * (sparc + powerpc + armel + ia...)10:37
janimoStevenK, filed bug #699744 which I hope describes  clearly the issue as I see it10:37
ubot5Launchpad bug 699744 in fakeroot-ng (Ubuntu) "fakeroot-ng can't ptrace in maverick" [Undecided,New] https://launchpad.net/bugs/69974410:37
fta2wgrant, so once aggregated by arch, it's 80 instead of 1010:37
wgrantfta2: Right. I'm not sure how best to fix it on our end, since this part of the data model is based on decisions from more than six years ago, and it's pretty ingrained :/ Perhaps if you can tell me what sort of data you actually need, I can expose it in a less raw form, without duplicates.10:38
fta2wgrant, and of course, each requires an interation, making the thing incredibly long to run10:38
wgrantfta2: Hence my inclination to expose it in a form that is more directly usable.10:39
fta2wgrant, i poll the stats and store raw tuples { pkgname, pkgversion, dist, arch, date, count } in a cache, so that i can later aggregate by any of those keys without re-polling10:41
fta2the reason for the cache is that it's way too slow to poll several times to have different views10:41
wgrantRight.10:42
fta2it will probably take more than a day to just poll the stats for the chromium/daily ppa10:42
fta2and probably timeout somewhere10:42
fta2it's probably 10 times worse for the mozilla/day ppa, it has zillions of packages10:43
fta2bin-pkgs10:44
=== yofel_ is now known as yofel
=== Ursinha-zzz is now known as Ursinha
=== matsubara-afk is now known as matsubara
=== doko_ is now known as doko
=== gnomelogger is now known as markeylogger
=== markeylogger is now known as apachelogger
=== oubiwann is now known as oubiwann_
=== matsubara is now known as matsubara-lunch
madcSPYnXfffhii15:24
madcSPYnXfffhi15:24
madcSPYnXfffis there any person alive15:25
madcSPYnXfffhello15:25
madcSPYnXfffhelo15:25
* benji checks his pulse... yep alive.15:26
madcSPYnXfffhey15:26
madcSPYnXfffhey benji15:27
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
madcSPYnXfffwhat is launchpad.net?15:38
=== leonardr_ is now known as leonardr
=== matsubara-lunch is now known as matsubara
=== Ursinha is now known as Ursinha-lunch
=== beuno is now known as beuno-lunch
=== beuno-lunch is now known as beuno
=== benji is now known as benji-lunch
ScottKwgrant: Related to the retry discussion from ~7 hours ago, I was thinking that if someone mashes the retry button, they should get the email when it fails again, not the original uploader.17:38
=== Ursinha-lunch is now known as Ursinha
=== benji-lunch is now known as benji
=== leonardr is now known as leonardr-afk
exarkunI wonder if anyone could suggest how I should move some code onto launchpad.  I have a bzr mirror of the svn repository which used to hold the code for half a dozen related projects, and on launchpad a while ago someone created <https://launchpad.net/divmod> and imported some of the code.18:44
exarkunCan I get rid of <https://launchpad.net/divmod>?  Change it into a regular project?18:44
benjiexarkun: there is a process (not sure what it is at the moment) to claim improperly registered projects, or you could ask the person that registered the project to hand ownership over to you18:49
exarkunI think he already made me an admin on the project or something like that18:50
exarkunBut I still can't push to it18:50
exarkunbzr: ERROR: Server sent an unexpected error: ('error', '<Fault -1: "Unexpected Zope exception: TypeError: (\'Could not adapt\', <ProjectGroup at 0x1875a550>, <InterfaceClass lp.code.interfaces.branchtarget.IBranchTarget>)">'18:51
benjiunfortunately I don't have much time to help at the moment; it does look like you're pushing to something other than a branch, perhaps you need something more on the target URL18:52
exarkunThat's from pushing to "lp:divmod"18:53
benjiit should be something like lp:divmod/name-of-branch; where "name-of-branch" migth be "trunk" or "2.2.1", etc.18:54
exarkunIt fails the same way for "lp:divmod/trunk"18:55
tsimpsonthere seems to only be lp:nevow in that project18:55
benjiif you go to https://code.launchpad.net/divmod you can see the current branches18:56
exarkunDoes this have something to do with "ProjectGroup"?  I don't really know what's going on, but it seems like launchpad has different kinds of projects, and this isn't the usual one.18:56
benjiwe've now exhausted my knowlege about this area of LP :)18:58
exarkunokay, thanks!18:58
benjiexarkun: this might help you on your journey: https://help.launchpad.net/Code/QuickStart19:01
tumbleweedexarkun: yes, project groups are collections of projects, and don't hold bugs / code themselves. But I'm not a lp admin, so I can't tell you anything about changing it into a project or renaming it out the way19:09
* benji learns something now.19:10
maxbexarkun: 'divmod' is a project group, and from what you said, it sounds like you have multiple projects to import too. So, why not register additional projects and mark them as part of the divmod group?19:15
exarkunThe projects are all in the same bzr branch19:15
maxboh. and eww19:16
maxbI would suggest fixing that before pushing19:16
exarkunThat sounds hard.19:16
maxbThe project as a whole is migrating from svn 2 bzr?19:16
exarkunyes19:16
maxbIf so, now is the opportunity to do it right19:16
maxbHow interrelated are the projects?19:17
exarkunsomewhat19:17
exarkun(I don't know how to be more precise than that)19:17
maxbWell, what are the projects?19:18
exarkunNevow, Epsilon, Axiom, Mantissa, Quotient, Hyperbola, Imaginary19:18
exarkuntemplating library/web server, random utility library, object database, application server, email server, blog server, text adventure library19:19
maxbuh, wow19:19
maxbright19:19
maxbyou definitely don't want that lot all in one bzr branch19:19
exarkunCan I convince anyone at Canonical to split it up for me? :)19:20
exarkunAlso, here's a complication19:20
ScottKexarkun: One major thing you lose going from svn to bzr is the ability to do partial checkouts.  Meaning anyone who wants one of those would need to branch/checkout all of them unless they are split up.19:21
exarkunIt's a mirror of the whole svn repository, so there are 178 branches (probably some are obsolete and perhaps shouldn't be pushed, but I'm sure at least a few dozen are relevant)19:21
maxbPerhaps you could push the existing branch(es) to lp:~exarkun/+junk/various, then people can see what the current form of the branch(es) is19:21
maxbI don't suppose the original svn repository still exists?19:21
exarkunI have a copy of that too, yea19:22
maxbHow large is that?19:23
maxbIf not too big, simply letting me download it might be the easiest way to explain what the situation is19:23
exarkun374MB19:24
maxbmy connection will be happy with that if yours is :-)19:25
exarkunwe can give it a try.  my upstream is somewhat limited, so it might take a while.19:25
exarkunjust waiting for bzip219:27
maxbThe output of 'svn log -v file:///path/to/repo' would be smaller and somewhat informative, if a little more cumbersome to read than exploring an actual repository.19:27
exarkunboth of those things available at http://home.intarweb.us:8080/19:31
exarkun(hopefully, let me know if I didn't hit my firewall right)19:31
maxbHmm. gosh. very weird branching system19:33
exarkunoh, I forgot about the username thing.  that goes away after a while.19:35
exarkunanything else weird about it?19:35
exarkunI think it's normal enough that bzr-svn largely figured it out automatically19:35
maxbHmm. So there are single commits that cross multiple projects19:35
maxbWhat did bzr-svn do by default? Did you get 1 trunk, or 1 trunk per project?19:36
exarkunsomeone else actually ran it, so I'm not sure.  But what he gave me was 1 trunk.19:37
exarkunhttp://codepad.org/MYbxKKt919:37
maxbhmm19:38
maxbOK, so the fundamental problem with this conversion is what ScottK was saying. If you go with this style of conversion, everyone will always have to branch, tag, checkout, work on a tree containing all the projects, always, all the time19:38
* exarkun nods19:39
maxbWhilst there seems to be some relationship (e.g. Axiom and Mantissa often getting commits together), it seems unlikely that you really want your object database's development fundamentally linked to that of a text adventure library :-)19:39
exarkunBut if I want to split it up by project, then the branches that touch more than one project are going to be a problem?19:40
maxbDepends.... bzr-svn should be happy to import them as one-branch-per-branchname-per-project19:42
maxbBut whether you consider that to be a useful conversion, I don't know19:42
exarkunis that done by specifying a different layout for the import?19:43
exarkun`--layout=ARGRepository layout (none, trunk, etc). Default: auto.` - is etc expanded anywhere?19:44
maxbI've never actually had cause to use bzr-svn against this sort of layout, I need to peer at the code a bit19:44
maxbOh, no. It looks like it would be necessary to code a custom layout class to make sense of this repository19:45
maxbHrm19:47
maxbthat's probably not what you wanted to hear, but I think it's likely still worth pursuing, for the good of the future development of the project19:47
exarkunis there any documentation about writing custom layouts?19:49
maxbNot really, no19:50
exarkunokay19:52
maxbI need to go seek food before shops close around here. I'll have a closer look at the situation in ~4 hours or so, and let you know my thoughts19:52
exarkunthanks for all the help so far19:52
=== leonardr-afk is now known as leonardr
=== matsubara is now known as matsubara-afk
=== Lcawte is now known as Lcawte|Away
=== Lcawte is now known as Lcawte|Away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!