Re: Packaging Ray for Debian Med
On Tue, Nov 06, 2012 at 09:17:59AM -0500, Sébastien Boisvert wrote:
> >I guess now you need to fire up
> >
> > lintian -i ray_2.1.0-1_amd64.changes
> >
>
> I don't get anything when I run this command. I am on Squeeze.
For development I'd (strongly) suggest to do drop a file
/etc/apt/preferences.d/01-lintian.pref
containing
Package: lintian
Pin: release a=unstable
Pin-Priority: 605
provided that Squeeze supports this /etc/apt/preferences.d way - if not
add this to your normal /etc/apt/preferences that should contain something
like
Package: *
Pin: release a=stable
Pin-Priority: 501
Package: *
Pin: release a=unstable
Pin-Priority: 50
Package: *
Pin: release a=experimental
Pin-Priority: 5
Once you might have done this please check
apt-cache policy lintian
It should give lintian from unstable preference. Alternatively you
can explicitely do
sudo apt-get install -t unstable lintian
(always provided your sources.list has an entry for unstable).
Please check again the lintian report with a recent lintian.
> >Regarding
> >
> > W: ray: hardening-no-relro usr/bin/Ray
> > W: ray: hardening-no-fortify-functions usr/bin/Ray
> >
>
> Do you know why I don't see these warning with lintian ?
Because of using lintian from stable.
> >I would recommend to simply try
> >
> > debian/compat: 9
> >
> >and in Build-Depends: debhelper (>= 9) which gives you good chances that
> >hardening will be switched on in case Ray has a properly crafted build
> >system.
> >
>
> Changed compat and debbuilder to 9.
OK.
> >BTW, in debian/changelog you are using "stable" as target distribution.
> >Besides the fact that you *never* can upload to stable and always have
> >to target at "unstable" our convention is to use "UNRELEASED" in VCS as
> >long as the package is not yet uploaded.
> >
>
> Changed to UNRELEASED.
OK.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: