[00:11] <dupondje> missing-license-paragraph-in-dep5-copyright paragraph 8 gpl-2+
[00:11] <dupondje> eh, I don't get it :(
[00:12] <jtaylor> its GPL-2+
[00:12] <jtaylor> and you need the header in the file
[00:15] <dupondje> jtaylor: http://anonscm.debian.org/viewvc/pkg-cryptsetup/cryptsetup/trunk/debian/copyright?revision=906&view=markup
[00:15] <dupondje> quite right no ?
[00:18] <jtaylor> I see no issue besides the wrong format url
[00:18] <jtaylor> the dep5 lintian check is a bit weird at times
[00:18] <Zhenech> dupondje, at line 40, split it up and make a separate "license: blah" block where you define the text of the license
[00:18] <jtaylor> the report does not necessarily match the real error
[00:19] <Zhenech> so you have files…\ncopyright…\nlicense..\n\nlicense…\ntext
[00:20] <jtaylor> is that really necessary in dep3?
[00:20] <Zhenech> at least for the checker
[00:21] <Zhenech> and my personal oppinion is that it is more readable tha way
[00:21] <Zhenech> and the url is now final: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
[00:21] <Zhenech> Stand-alone License paragraphs can be used to provide the full license text for a given license once, instead of repeating it in each Files paragraph that refers to it. The first line of the License field must be a single license short name or a short name followed by a license exception.
[00:22] <dupondje> I changed to Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/, and the error is gone now :s
[00:25] <dupondje> getting cryptsetup package in a better health :D
[01:13] <Gaming4JC> How much do I have to pay to hire a MOTU to push ia32libs into natty? :D
[01:13] <Gaming4JC> the one with LibOpenGL ofc :)
[01:19] <EvilResistance> an infinite amount
[01:20] <EvilResistance> Gaming4JC:  show a need for it to be updated, complete an SRU, and *maybe* it'll be updated, but not in main, in natty-updategs
[01:20] <EvilResistance> natty-updates *
[01:20] <EvilResistance> (according to how i've been explained the process)
[01:22] <Gaming4JC> Well,  the bug has been reported I've not done an SRU. https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/821100/
[01:23] <Gaming4JC> I'll send you an https://en.wikipedia.org/wiki/Euclidean_algorithm ;)
[01:23] <Gaming4JC> infinite amount
[01:23] <Gaming4JC> lol.
[01:25] <Gaming4JC> looks like another Dev already mentioned it was SRU'able' actually. And it seems to be a workflow not a form to write up.
[01:31] <Gaming4JC> too bad the bug never made it to ... http://people.canonical.com/~ubuntu-archive/pending-sru
[01:31] <Gaming4JC> :/
[01:32] <Gaming4JC> If I could find any documentation I'd compile ia32libs myself
[01:32] <Gaming4JC> :)
[09:52]  * valdur55 is away: I'm busy
[11:52] <verwilst> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-php54 < will php 5.4 be included in precise? anyone knows?
[11:54] <geser> ajmitch: ^^ didn't you experiment with php 5.4?
[18:59] <ajmitch> geser: I did, but that's not my decision to make :)
[19:27] <plipp1> Could you help me navigate a bit? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/923668
[19:30] <plipp1> "Changed in Unity",  "Changed in Unity (Ubuntu)",  "Changed in ayatana-design"..
[19:33] <plipp1> Apparently a fix has been committed upstream (ayatana-design). Triaged in "Unity" & assigned,  Triaged and unassigned in "Unity Ubuntu".
[19:34] <plipp1> However, milestone is set to "unity backlog" in 'Unity', and "Ubuntu ubuntu-12.04-beta-2"...
[19:35] <plipp1> "unity backlog" sounds to me that it's unclear when it will be fixed, but in Ubuntu the milestone is set (regardless of this fact) nor is anyone assigned to it (which makes sense as there's nothing to be done yet, I guess).
[19:35] <plipp1> Any thoughts on my ramblings?
[19:38] <Laney> I think that #ubuntu-unity will likely know more, but possibly not on a weekend.
[19:39] <plipp1> Also, "Fix committed", shouldn't there be a link to the commit? I have no idea where to find stuff (yet).
[19:39] <plipp1> Laney: Well, it's really more of a general question in how things usually work out
[19:39] <plipp1> In case this is "normal"
[19:40] <Laney> The workflow being applied here is goign to be specific to these projects
[19:42] <plipp1> Laney: Ok. I thought there might be a unified process on how to commit to a Ubuntu milestone
[19:42] <plipp1> As in, "don't promise stuff you won't keep anyway" :)