=== kentb is now known as kentb-out [04:33] Rhonda: IA-32 libs didn't even sound like a good idea at the time, it was just something that could be done quickly. [06:18] ssh, don't debunk my catch phrase :) [06:23] don't let facts get in the way of a good argument? :) [06:34] 'sactly! === sagaci_ is now known as sagaci [06:54] good morning === almaisan-away is now known as al-maisan [07:28] huhm [07:28] I think I now saw the issue with packages.ubuntu.com myself … [08:30] \o/ tumbleweed :) [08:33] Rhonda: lintian wasn't very impressed with it, though [08:47] hmm? [08:47] E: gitolite: control-file-has-bad-permissions md5sums 0664 != 0644 [08:47] E: gitolite: control-file-has-bad-permissions templates 0664 != 0644 [08:47] duh, how did that happen? Doesn't over here [08:48] Ah, some umask probably playing into it on the build server [08:48] yeah, ubuntu changed umask recently [08:49] but there is this "find $(TMP) ! -type l -print0 2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s" in debian/rules which should adjust that? [08:49] ah, wait, templates and md5sums, the control files [08:49] heh, I see Rhonda doesn't like packaging helpers :P [08:49] which get generated _after_ the fixperms [08:50] Hey, I wanted to know what kind of magic was going on in the background. Apparently not that much. :) [08:52] tumbleweed: not liking is based on bad experiences where I had to do handstand coding to get rid of some annoyances, but that was years ago :) [08:54] it's a rather short rules for a no-helper package, I guess it helps that it's a nice simple one [08:57] I tried to keep it short and simple so that it can be used as example :) [08:57] Maybe I should throw in comments like "# this is the magic that dh_fixperms is actually doing" [08:58] For more complex packages it though gets complicated and irritating. Don't look at spl's debian/rules. ;) [08:59] Hmm, not that overwhelming than I thought, but that might just be me and my experience with code … 226 lines [09:01] tumbleweed: Should I fix the lintian issues you are seeing and request again, does that mean the package is now blocked, or is it even though it's an error acceptable? [09:02] I'd either suggest uploading 2.0.3-1ubuntu1 with that fixed, or just fix that in Debian and sync. If you made other changes in Debian too, I'd want to review it again [09:03] I'd fix some other lintin output too [09:03] if that's manpages, that's fine with me [09:03] debian-rules-missing-recommended-target [09:03] out-of-date-copyright-format-uri [09:04] Those three lines [09:04] fine [09:06] the guy requesting the inkscape backport is my new best friend [09:13] ok. I do not catch it. Package libc6-dev-armhf-cross provides libc6-dev-armhf-armel-cross but gcc-4.6-multilib-arm-linux-gnueabi depends on libc6-dev-armhf-armel-cross and complains on install that libc6-dev-armhf-armel-cross is not installed. Why "provides" does not solve it? [09:14] is the depends versioned? [09:15] Laney: package is 2.13 and depends is on >= 2.5 [09:16] versioned deps on virtual packages won't work http://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual [09:17] thanks [09:17] will have to create dummy packages then [09:18] let amd speeds up with buldozer cpus... I need to upgrade my machine [09:37] tumbleweed: uploaded. :P [10:36] hmm. Now I have gitolite_2.0.3-2_source.changes - what next? Never used syncpackage before, where to upload that to? :) [10:39] And why did syncpackage re-sign the .dsc file while it already had a good signature? [10:39] are you trying to do a --no-lp upload? [10:40] No clue. :) [10:40] So far I only did upload to my PPA, and did requestsync :) [10:40] oh, sorry Rhonda I should have been clearer when I suggested using syncpackage :) [10:41] I meant a new syncpackage that can do LP native syncing [10:41] No problem, I want to learn. :) [10:41] >= 0.129 [10:43] ubuntu-dev-tools 0.101 [10:43] ah, we don't have a backport to debian stable [10:44] I bet that's a rather small userbase :-) [10:44] although the PPA build for maverick might work on there [10:44] Laney could do it, he got upload permissions to backports recently. :P [10:44] otherwise, it should run fine out of a bzr checkout [10:44] it requires some other backports too [10:44] since some scripts moved about [10:44] Anyway, I let it rest for now, will try at home from my wheezy laptop [10:44] yeah, stuff moved to devscripts, distro-info, and lp-tools [10:45] bdrung said a backport to natty would be too hard, so stable … [10:45] Laney: OTOH, backporting this specific feature anywhere wouldn't be that hard [10:45] I'm fine with that. [10:45] Laney: you can do it, if you backport devscripts, distro-info, lp-tools, and python-debian [10:46] if [list of tiresome things] [10:47] I wouldn't know enough about how cherry-pickable syncpackage is — didn't it require some changes in ubuntutools/? [10:47] but, I support doing that [10:47] I'm happy to do some exploration into that [10:48] Laney: I wouldn't accept a cherry-picked backport anyway. :P [10:49] I was referring to natty-backports [10:49] this is a generally useful thing to backport in Ubuntu [10:49] probably less so in Debian [10:51] talking of which, I still need someone to review my u-d-t SRUs in Ubuntu. I don't like verifying my own SRUs === al-maisan is now known as almaisan-away [10:53] Rhonda: btw, is there any plan for backports integrating with the bts? Like it learning about backports versions and so on. === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [11:30] Laney: http://lists.debian.org/debian-devel/2011/06/msg00247.html and following [11:32] Laney: tl;dr - no version tracking in the BTS, but most important: No concept of different maintainers for a package [11:33] well yeah, but that's not unsolvable [11:33] if backporting, change the maintainer and let the bts know that different versions can have different maintainers [11:33] but i will read it [11:33] I'll tell don that we have a volunteer \o/ [11:34] But that's exact the issue: The bts doesn't has the concept yet that different versions can have different maintainers [11:36] or have backports bugs sent to some pts keyword that the maintainer isn't subscribed to by default [11:40] There are loads of ideas how it could be done, but noone doing the actual code. The issue is known since a pretty long time now. (in this case) unfortunately there isn't a canonical behind Debian that would make sure that such things get done in a timely manner, and it didn't itch noone big enough yet to fix it [11:41] I'd be more than interested in digging into it, but there are so much other tasks that I look after that otherwise would be lying around because they are also uninteresting to others [11:41] :-) [11:42] Heck, I haven't got to looking at the squeeze RC graph since a few months, and squeeze is meant to be a supported release. %-/ === Quintasan_ is now known as Quintasan [12:10] Laney, bdrung: I did a quick and dirty backport in bug 860506 [12:10] Launchpad bug 860506 in natty-backports "Backport native package syncing to ubuntu-dev-tools" [Undecided,New] https://launchpad.net/bugs/860506 [12:10] there is unecessary stuff included, but I don't think it's dangerous, and I preferred to backport whole files where possible [12:12] cool [12:12] it'd be good to test various types of sync [12:13] * tumbleweed only did simulated requestsync and syncpackage === almaisan-away is now known as al-maisan [14:11] why when I am dputting http://paste.ubuntu.com/697897/ to ppa I do not get orig.tar.gz uploaded http://paste.ubuntu.com/697898/ ? [14:11] did you include it in "build"? [14:12] good point. _source.changes lacks it [14:12] -sa to debbuild [14:14] Zhenech: thx [14:14] it defaults to include it in -1 uploads and do not in everything else [14:15] but there was no uploads of it previously and package is -1~linaro5 for a reason [14:15] ok, /me -> code [14:15] weill, -1~linaro5 isn't -1 ;) [14:17] and debuild doesnt know that you didnt upload anything else yet [14:17] yep === shadeslayer is now known as shocklateboy42 === shocklateboy42 is now known as shadeslayer === al-maisan is now known as almaisan-away [17:26] is Box2D going to be updated any time soon? [17:28] oh, feature freeze. === yofel_ is now known as yofel [18:40] SMJ: yeah, it would require lots of jumping up and down to make it happen (and a good reason, and some testing) === bulldog98_ is now known as bulldog98 === medberry is now known as med_out === jrib is now known as Guest49180 === Guest49180 is now known as jrib