=== ttx_ is now known as ttx [17:09] nthykier: So, there's a new swt-gtk being synced from testing, and we've an eclipse that provides swt-gtk. [17:09] But this causes a bit f a conflict. Which should win? [17:15] persia: next upload with eclipse ships without swt [17:15] persia: sadly I do not have time right now (though I am available in a about 3-4 hours) - alternatively you can debate it with bdrung [17:15] OK. Should I authorise the sync now, and we can expect that upload in the next few days? [17:15] bdrung: Please pipe up if you like :) [17:16] nthykier: The sync is currently blocked. Later is fine if bdrung doesn't answer. [17:16] alright - later then [17:16] Thanks for the quick response even when you're busy. [17:18] late for class - the cold weather outside is not really motivating me [17:20] heh. [17:28] persia: i am here. eclipse in lucid does not provide the swt libs any more. so we need the swt-gtk source package again. [17:29] persia: but the version of swt-gtk must be bumped [17:29] bdrung: That information conflicts with what I was just told by an archive-admin. [17:29] Specifically, the sync is failing into lucid *because* eclipse is providing the binaries. [17:30] persia: eclipse 3.5.1+repack~3-0ubuntu1 provides the swt libs, 3.5.1+repack~3-0ubuntu2 does not. [17:30] check #ubuntu-devel from :08 to :15 [17:31] Well, that's confusing. [17:31] * persia checks a few other places [17:32] Bother, and those are in NBS. Gotcha. Thanks. [17:32] I'll file a bug to unblock the sync and sort it. [17:32] persia: we need to bump the swt-gtk version >> 3.5.1+repack~3-0ubuntu1 [17:34] So it's not a sync, and we need to upload swt-gtk 3.5.1-2 as swt-gtk 2.5.1+standard-0ubuntu1 ? [17:39] persia: 3.5.1+standard-0ubuntu1. or replace standard with something meaningful. [17:39] "standard" was just the first string >> "repack" that came to mind. Do you have any suggestions? [17:40] persia: repack would works, to [17:40] s [17:40] o [17:40] persia: repack would work, too [17:40] Except it is no longer a repack :) [17:41] nthykier: can you remember a good name for the swt-gtk version? [17:42] He's at class now :) [17:42] persia: there was a name starting with s, but i can't remember it [17:43] Alright. I can wait a few hours before uploading it and getting it unblacklisted. [17:43] persia: how about +versionbump? [17:43] heh. works for me. Shall I just upload with that? [17:43] persia: yes [17:44] persia: 3.5.1+versionbump-0build1 [17:44] Why -0build1? [17:44] persia: therefore it will get synced once the debian version is greater [17:45] And that means I don't need to mangle debian/control. I'll go with it. [17:45] persia: we use buildX for rebuilding and fakesyncs. so why not for versionbumps? [17:45] We don't use buildX for fakesyncs (or we shouldn't be doing that) [17:45] persia: how will you do the fakesync then? [17:46] persia: do you really want to edit debian/control for fakesyncs? [17:46] I tend to use -0ubuntu1 for fakesyncs. [17:46] persia: -0? [17:47] Err, no. [17:47] XubuntuY [17:47] k [17:47] The reason being that I can't sync -{X+1} [17:47] persia: Xubuntu1 [17:47] I need to wait for the next upstream. [17:47] Right. [17:48] I also want to preserve the Ubuntu debian/changelog entries so that it's clear who should get the complaints about creating the unsyncable tarball. [17:48] if dpkg --compare-versions 1build1 lt 1+1; then echo yes; fi [17:48] ${X+1} is "2" when X is "1". [17:48] (at least in my head, for which there is admittedly little documentation) [17:49] ups, yes [17:49] :) [17:52] * persia cringes at xulrunner-dev [18:07] bdrung: nthykier: version-bumped swt-gtk uploaded. [18:11] k [20:52] persia: thanks [20:54] nthykier: No problem. AnAnt was asking me about it earlier, but I hadn't been following the eclipse stuff closely, so I had no idea what was the right thing to do, and somehow ended up with my name against the blacklist, so had to clear it. [20:54] Thanks for helping to get me to understand what was needed. [20:55] persia: a large hammer, a lot of muscle and even more patience :P [20:59] heh