Bug#945325: RFS: fet/5.40.3-1 [QA] -- timetable generator

2019-11-22 Thread Thiago

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "fet"

 * Package name: fet
   Version : 5.40.3-1
   Upstream Author : Liviu Lalescu 
 Volker Dirr
 * URL : https://www.lalescu.ro/liviu/fet/
 * License : AGPL-3+
 * Vcs : https://salsa.debian.org/debian/fet
   Section : misc

It builds those binary packages:

  fet - timetable generator
  fet-data - timetable generator - documentation and examples

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/fet

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/f/fet/fet_5.40.3-1.dsc

Changes since the last upload:

   * QA upload, orphaning package; see #945298.
   * New upstream version 5.40.3.
   * debian/control:
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added VCS fields.
   - Bumped Standards-Version to 4.4.1.
   * debian/rules: Removed override_dh_dwz, no longer needed. (Closes: #934854)
   Thanks to Gianfranco Costamagna.

Regards,

--
  Thiago Andrade Marques



Re: debhelper versions

2019-11-22 Thread Paul Wise
On Fri, Nov 22, 2019 at 9:44 PM Wookey wrote:

> No, the compat file should match the dependency, and determines the
> actual behaviour of debhelper in the packaging. i.e. that's the
> important bit, and the control file dependency is just being set to
> match.

BTW, to avoid the possibility of mismatches, the debian/compat file
has been replaced in debhelper 12 with a debhelper-compat versioned
virtual package. So instead of depending on debhelper (>= 12~) you now
depend on debhelper-compat (= 12) instead and delete debian/compat. Of
course, you won't be able to use this since you need to support old
releases, but at some point in the future this feature will make
things simpler for you.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



Re: debhelper versions

2019-11-22 Thread Wookey
On 2019-11-22 14:10 +0100, Ake Hedman wrote:
> Hi,
> 
> I am packaging a bunch of projects that are supposed to install on
> Ubuntu/Debin/Raspian preferable on as old versions as possible.  I am
> trying to make scripts that make the packages automatically with
> pbuilder and I get a bit confused on how to handle the different
> debhelper versions.
> 
> For example I have the dependency setting in the debian/control file. If
> I want it to work for raspian jessie i need to set this to debhelper (>=
> 8) On buster it is (>= 11) and on Ubuntu there is other versions etc.

Set both the dependency and the 'compat' file to the oldest one you
need (e.g. '8' for Raspian jessie in this case). That should continue
to work everywhere (until actually deprecated in debhelper). Ignore
Lintian if it grumbles and only move it up when you are no longer
supporting something that only has '8'.
 
> And should the compat file be 11 in all cases?

No, the compat file should match the dependency, and determines the
actual behaviour of debhelper in the packaging. i.e. that's the
important bit, and the control file dependency is just being set to
match.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature


Re: debhelper versions

2019-11-22 Thread Andrey Rahmatullin
On Fri, Nov 22, 2019 at 02:10:12PM +0100, Ake Hedman wrote:
> I am packaging a bunch of projects that are supposed to install on
> Ubuntu/Debin/Raspian preferable on as old versions as possible.  I am
> trying to make scripts that make the packages automatically with
> pbuilder and I get a bit confused on how to handle the different
> debhelper versions.
> 
> For example I have the dependency setting in the debian/control file. If
> I want it to work for raspian jessie i need to set this to debhelper (>=
> 8) On buster it is (>= 11) and on Ubuntu there is other versions etc.

> How do people handle this. Build manually for all platforms?
You still need different changelog entries for different platforms, and in
many cases different build-deps, not to mention other packaging changes.

> And should the compat file be 11 in all cases?
compat shouldn't be higher than the debhelper version.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


debhelper versions

2019-11-22 Thread Ake Hedman
Hi,

I am packaging a bunch of projects that are supposed to install on
Ubuntu/Debin/Raspian preferable on as old versions as possible.  I am
trying to make scripts that make the packages automatically with
pbuilder and I get a bit confused on how to handle the different
debhelper versions.

For example I have the dependency setting in the debian/control file. If
I want it to work for raspian jessie i need to set this to debhelper (>=
8) On buster it is (>= 11) and on Ubuntu there is other versions etc.

How do people handle this. Build manually for all platforms?

And should the compat file be 11 in all cases?

/Ake