[Debian-med-packaging] Fwd: Bug#673434: dssp: ftbs with gcc-4.7

Laszlo Kajan lkajan at rostlab.org
Mon May 21 13:51:02 UTC 2012


Hello Maarten!

Thanks for the patch that fixes the FTBFS.

My intention was to keep the dh compatibility level 7 until Precise becomes the LTS release for Ubuntu, expected in July. It is also important
for me that the package can be built in squeeze; that has dh 8.

There seem to be ways to do hardening with dh << 9: [1].

All the best,

Laszlo

[1] http://wiki.debian.org/Hardening#Notes_for_packages_using_CMake

On 21/05/12 14:17, Maarten L. Hekkelman wrote:
> Op 21-5-2012 13:30, Andreas Tille schreef:
>> On Mon, May 21, 2012 at 01:23:36PM +0200, Maarten L. Hekkelman wrote:
>>> One of the reasons I see is that changing compat to contain a number
>>> higher than 8 is that pdebuild stops working in squeeze... Since I'm
>>> using a production machine to build packages, this is a show
>>> stopper.
>>
>> Perhaps this is a missunderstanding of using pdebuild:  Before you
>> upload to official Debian you should build every package in a clean
>> chroot (probably using pbuilder or some similar tool) which is featuring
>> an `unstable` system.  The rationaly is that you are uploading to
>> `unstable` anyway.  This requirement is independent from whatever
>> system you are running (it might be stable or any Ubuntu version).
> 
> That's what pdebuild is for. It builds the package in a clean `unstable` environment (in my setup anyway) and throws the environment away after
> building. However, pdebuild starts by inspecting the debian directory using the current debian package tools and complains when compat contains
> anything > 8.
> 
>>> Anyway, I checked in a version of dssp with dh version 9, I believe
>>> it works as intended.
>>
>> PLease do not missunderstand me:  I was not requesting you to change
>> debhelper version back if you have good reasons to do (and Laszlo who
>> seemed to have introduced the change) might have its reasons I have
>> currently (=as long as we did not discussed pros and cons) no reason to
>> override.  It just should be *documented* in changelog as changes
>> between the last an this version.
>>
>> Moreover I think that when using debhelper 7 you need to manually care
>> for the hardening flags as described in the Wiki[1] to deal with the new
>> hardening related lintian warnings.
> 
> Well, since it was Laszo asking for a dssp with debhelper 7, I think he should join in to decide how to proceed?
> 
> best regards,
> 
> -maarten



More information about the Debian-med-packaging mailing list