[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: nautilus-image-manipulator


2011/4/13 Paul Gevers <paul@climbing.nl>:
>> I have used pbuilder, and it seems to me that all needed build
>> dependencies are correctly addressed.
> < snip >
>> That's due to the Lintian version I have on my Ubuntu 10.04
>> workstation, which is not the most recent (2.3.4ubuntu2). What are the
>> consequences of not running the latest version of Lintian? How do we
>> go about this? Should I have sid in a VM somewhere to package my
>> software?
> You should always build in sid and check with lintian from sid. With
> pbuilder that should be fairly simple. As far as I understand this does
> not involve any VM, just an automatically generated chroot.

When running with pbuilder on my Ubuntu machine it uses the same
version of lintian, so I get the same warning message. I will thus
install Debian to use pbuilder from that.

>> Regarding your other comment:
>>   * You have an unwanted patch in debian/patches which was automatically
>>     added by the 3.0 (quilt) source format
>> This patch gets created automatically when running debuild, because
>> the .pot file gets generated again. How can I prevent this, and is it
>> a big problem (after all, the .mo files need to be compiled before
>> packaging, so I'm not sure this should be a problem).
> Remove it in your clean target and it will not get included in the
> patch. Make the patch as clean as possible, that is easier for review.

Can you please point me to a resource how to "[r]emove it in [my]
clean target"? Would I have to add that in debian/rules? How can I
make sure that I will only remove this change to the translation file,
an not any [future] potential valid change?

>> As a side note, should the .pot (translation template) be included in
>> the binary package? It is currently not.
> If the translations work without it, there is no need.

Great, nothing to change then.

> Paul


Reply to: