Path: csiph.com!news.neodome.net!weretis.net!feeder8.news.weretis.net!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod
From: Soren Stoutner <soren@debian.org>
Newsgroups: linux.debian.bugs.dist
Subject: Bug#1120549: sbuild: unclear how to do a source-only build
Date: Wed, 19 Nov 2025 03:00:01 +0100
Message-ID: <LSFEd-e16Z-3@gated-at.bofh.it>
References: <LQ6rf-ch6s-5@gated-at.bofh.it> <LSjkl-dM4b-1@gated-at.bofh.it> <LSp6p-dQ8J-1@gated-at.bofh.it> <LQ6rf-ch6s-5@gated-at.bofh.it> <LSp6p-dQ8J-1@gated-at.bofh.it>
X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org  Wed Nov 19 01:55:09 2025
Old-Return-Path: <debbugs@buxtehude.debian.org>
X-Spam-Flag: NO
X-Spam-Score: -2.399
Reply-To: Soren Stoutner <soren@debian.org>, 1120549@bugs.debian.org
Resent-To: debian-bugs-dist@lists.debian.org
Resent-Cc: sbuild@packages.debian.org
X-Debian-Pr-Message: followup 1120549
X-Debian-Pr-Package: sbuild
X-Debian-Pr-Source: sbuild
Organization: Debian
Face:  iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWIg4F7bGiws7ReTkyy kYoXFRrd6/4yMA0PAAACaklEQVQ4y22TwXabMBBFJaPuNZGSNZZp1uhM6BpkJeu4VFk3bsL/f0Lf CHC6qHyOgbl68zTDoIwaVfh3tUopTUGpbFToDiFnY9IY2oMAZYMiS4R9SfbSXepSS5EcFAa/muIU aRj8mkoUqrEraFzhYegBmqig0LyCIyM8DAwPlpBqmJVYaD2UeWZ3abVjsqKIojg+hY4omsyIcNSi qIBM6jJWOveS6kvBeVvHJ+VYzJUW88RmA12UiBx3HEcUMRuzIZI6tBQovTrPclNB3AuUXoXvs0XY C3B2baJpW4Dn2ZpVMInCirkxoyhM1qpK5nFrO65QvCrCqql2DyPgvm94iMQz5/PmISuEotxQGMD5 M5G1N9CjXJ5HQH96BZG2xx6AzejYZccxT4Re3Zr4bPKkCcGcz5Or3dVEABkAUY/znnVcQVVkrXVU vomoEJFe7x4nQuaZmZELL6qnXZGIB5YV/Q2IogtSmyNybEcBX2+QCLOAQYm+gmoORUrYzV7dc6R2 T1WPm45oVEQqsjtoIovHyTmcyxMhVVxTqapomZyLlAmTKC9AmjgamXXGZo+epNrXO3wGGiPRHbKL FnMy2RRgRb1gzFXXGjhICp8wqaTtdtyQH6nWTfkatJvJJoUCbOjSC7wR9/naEVognxrOFdLh7Ugx QpA/0QT4pRV0+u2dqsXD5y9EBDjVAJS3ZZLxmZblgmsU8x7mBeCKg48Py7WU2IiH1epbEbC8K9Ms y0cpcySVUcdQVrBY+rEsv+XpYgFKXT8B3v2yATxv8fKK2EfC358tsIMLYqfD401xA0j1EY4P/wWf IbhlOWyBv4OQsywBM8MAAAAAAElFTkSuQmCC
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2208488.bB369e8A3T"; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Debian-User: soren
X-Debian-Message: from BTS
X-Mailing-List: <debian-bugs-dist@lists.debian.org> archive/latest/1937484
List-ID: <debian-bugs-dist.lists.debian.org>
List-URL: <https://lists.debian.org/debian-bugs-dist/>
Approved: robomod@news.nic.it
Lines: 99
Sender: robomod@news.nic.it
X-Original-Date: Tue, 18 Nov 2025 18:52:50 -0700
X-Original-Message-ID: <2756990.k3LOHGUjKi@soren-desktop>
X-Original-References: <87ms4sku57.fsf@debian-qemu> <22933010.EfDdHjke4D@soren-desktop> <176345354274.11261.17410380309074266729@localhost> <87ms4sku57.fsf@debian-qemu> <176345354274.11261.17410380309074266729@localhost>
Xref: csiph.com linux.debian.bugs.dist:1270742

--nextPart2208488.bB369e8A3T
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Soren Stoutner <soren@debian.org>
Date: Tue, 18 Nov 2025 18:52:50 -0700
Message-ID: <2756990.k3LOHGUjKi@soren-desktop>
Organization: Debian
In-Reply-To: <176345354274.11261.17410380309074266729@localhost>
MIME-Version: 1.0

On Tuesday, November 18, 2025 1:12:22=E2=80=AFAM Mountain Standard Time Joh=
annes=20
Schauer Marin Rodrigues wrote:
> I would like for you to revert your revert or explain why you think that=
=20
this
> is incorrect information.

The information in the wiki has been specifically written so that the examp=
le=20
=2Esbuildrc produces a source.changes file and a <BINARY>.changes file suit=
able=20
for upload to Debian with each build.  This makes it so that a user can eas=
ily=20
do either of the following without needing any extra commands.

$ gbp buildpackage
$ cd ..
$ debsign <PACKAGE>_source.changes
$ dput <PACKAGE>_source.changes

or

$ gbp buildpackage
$ cd ..
$ debsign <PACKAGE>_amd64.changes
$ dput <PACKAGE>_amd64.changes

Having a .sbuildrc that does this is desirable to many users, particularly =
new=20
users.  In fact, this entire bug report exists because a user was uncertain=
=20
how to generate a source.changes file.  Having instructions in the wiki tha=
t=20
accomplish this goal by default is important.

I am unaware of any downsides to having sbuild always generate functional=20
copies of both changes files.  If there are, please feel free to enlighten =
me. =20
Otherwise, it is important that both of the following commands be included =
in=20
the example .sbuildrc or one or both of the .changes files will either not =
be=20
produced or not be produced correctly.


# Build the source in addition to the other requested build artifacts. =20
Without this, <BINARY>.changes files will not include the upstream source i=
n=20
their list and will fail uploads to Debian if they are for a -1 revision th=
at=20
includes a new upstream release; this is the same as passing `-s` to sbuild.
$build_source =3D 1;

# Produce a source.changes file suitable for a source-only upload; this is =
the=20
same as passing `--source-only-changes` to sbuild.
$source_only_changes =3D 1;


Of course, an individual user may prefer to not follow the example or to=20
disable these commands to their liking.

=2D-=20
Soren Stoutner
soren@debian.org
--nextPart2208488.bB369e8A3T
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmkdIvIACgkQwufLJ66w
tgPPpw/+Ppmz2GXLEMoMOv7VzDo+DnOmbJvVxz16IYLkk1sDjZtmyKxSM42zC9Aw
vtX3MfPQ0y6HGD5JryTDH2IP8zD3kcwq3uEe8qRsahhsZHnZL+WKM7B0ewDEO3/W
ozDgxINmh+EywoRfYRFn/tL0wF1UDaDewz3XYyyrIyCWKdPBY7SqLorFwQaUmj49
6576EDbz1v2mCoLPKCBjK71i79nRsf7cgjEF9vOSq9yZLnkx5fkrGGG8ikOwC7Ls
5RsmSMT72brljJ6+Py90+ryY92ek0qOsN1wMumODuBKxNKWMhdsRh3pN/z6dRRFI
Tz8c0sx6OsPErXFirfm6EU2LaaSec1AlwIA9/7N652ZVlsbWlZ7D2DkqZ6X6cks4
5QNEVVjHQx/auw0UXDI/enDSJLwcuP9ofbxLrAW/U2861TVZLaUoZvZ+IR7LJzWr
pUFc2eLVSkGeCqh5C/y2bYhjG6C9Mf0ckm0M4MlQJFBss7BwFKXQTwskFpdgmNHd
+Bpv4IRO/f4luTTB6yxGHTZJl1gL9AzcXr205reMGKRV11mU1ucZy9mGDnVa2jzj
mJ5hzNzL9+BYwR7BeRnUik+YW/Ji31Jc1VddMsBTurL7HaSrEIinhw5ke9hbXbO/
z18LVLQetm+Nr76pya2elZBv3fkkbOUiMGtQJSn/M0UaTeheup8=
=hrlF
-----END PGP SIGNATURE-----

--nextPart2208488.bB369e8A3T--