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

Re: Bug#1106094: RFS: subnetcalc/2.6.4-1



Thomas,

On Monday, May 19, 2025 8:49:21 AM Mountain Standard Time Thomas Dreibholz 
wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "subnetcalc 
> <https://www.nntb.no/~dreibh/subnetcalc/>":
> 
>   * Package name: subnetcalc
>     Version: 2.6.4-1
>     Upstream Author: Thomas Dreibholz <thomas.dreibholz@gmail.com>
>   * URL: https://www.nntb.no/~dreibh/subnetcalc/
>   * License: GPL-3+
>   * Section: net

Your package doesn’t appear to match the source at:

https://github.com/dreibh/subnetcalc/tree/master/debian

For example, the changelog file on GitHub looks like it was designed for 
Ubuntu and doesn’t match the one used for Debian packaging:

https://tracker.debian.org/media/packages/s/subnetcalc/changelog-2.6.2-1

Trying to build from your Git repository produces the following error, even 
when checking out the subnetcalc-2.6.4 tag:

dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/
subnetcalc_2.6.4-1ubuntu1.diff.dgZBqo

I would recommend you move your Debian packaging to Salsa.  In my experience 
as an upstream developer, it makes my life easier if you put your upstream 
source where ever you already have it and the Debian packaging on Salsa.  If 
you use gbp, importing each new upstream release can be as simple as:

gbp import-orig uscan
dch
gbp buildpackage
gbp tag
gbp push

I wrote an email a while back that explains a bit about how gbp works.

https://lists.debian.org/debian-mentors/2024/09/msg00057.html

In addition, placing the Debian packaging on Salsa lets you use Salsa CI, 
which catches a lot of problems before release, like the missing build flags.

https://qa.debian.org/bls/packages/s/subnetcalc.html

-- 
Soren Stoutner
soren@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: