On Tue, Nov 1, 2011 at 11:42 AM, Colin Watson wrote:
> On Tue, Nov 01, 2011 at 10:01:31AM -0400, Andrew Starr-Bochicchio wrote:
>> On Tue, Nov 1, 2011 at 8:25 AM, Colin Watson wrote:
>> >oh for lintian.ubuntu.com ...
>>
>> This is something I've also wished for. Is there any historical reason
>>
On 01.11.2011 13:25, Colin Watson wrote:
> If my grep is correct (oh for lintian.ubuntu.com ...) there are 119
> packages using debhelper compat level 9 in precise right now. I've
> examined all of these, and have so far refined that list to 16 packages
> that look as though their behaviour may be
On Tue, Nov 01, 2011 at 10:01:31AM -0400, Andrew Starr-Bochicchio wrote:
> On Tue, Nov 1, 2011 at 8:25 AM, Colin Watson wrote:
> >oh for lintian.ubuntu.com ...
>
> This is something I've also wished for. Is there any historical reason
> why this doesn't exist beyond no one making it happen yet?
On Tue, Nov 1, 2011 at 8:25 AM, Colin Watson wrote:
>oh for lintian.ubuntu.com ...
This is something I've also wished for. Is there any historical reason
why this doesn't exist beyond no one making it happen yet?
Russ Allbery says "the web generation framework isn't really
"productionalized" in
On Tue, 01 Nov 2011, Colin Watson wrote:
> What I think we settled on as the least bad option is to refine the
> dpkg-buildpackage workaround so that it does not export environment
> variables if the package it's building is using debhelper compat level 9
> or above, and to manually review all such
We have a nasty little problem in precise, and unfortunately it's mainly
of our own making. I've been discussing this with a few people at UDS
(mainly Steve Langasek, Adam Conrad, and Matthias Klose), but I want to
have something on the record, in part so I don't forget the details.
Historically
