(Please CC me as I'm not subscribed to debian-devel)

Hi!

I have noticed some time ago that vcswatch doesn't recognize the releases
of some of my Debian packages such as fs-uae [1]. As a result, it sees 67 commits since the last release, asking me to perform an upload.

However, I have already uploaded all changes and I'm apparently just missing the proper tags. I have always used gbp for git packaging and "gbp dch --auto" to finalize the changelog, apparently that's not sufficient.

Could anyone tell me what the proper gbp command is for creating the changelog entries for the new release including the proper tag. The gbp manual [1] mentions
Debian tags but it doesn't seem to explain how to create them.

And if I wanted to add the tags later manually and push them, what is the expected
format of the tags? Just "debian/$VERSION"?

Thanks,
Adrian

[1] https://tracker.debian.org/pkg/fs-uae
[2] http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.releases.html#gbp.changelog.release

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello Adrian,

Am 05.10.21 um 12:06 schrieb John Paul Adrian Glaubitz:

Hi Timo!

On 10/5/21 12:04, Timo Röhling wrote:

* John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> [2021-10-05 11:45]:

Could anyone tell me what the proper gbp command is for creating the changelog
entries for the new release including the proper tag. The gbp manual [1] mentions
Debian tags but it doesn't seem to explain how to create them.

I usually run "gbp dch -R -c" first, then build and upload the
package, and finalize with "gbp tag && gbp push".

And if I wanted to add the tags later manually and push them, what is the expected
format of the tags? Just "debian/$VERSION"?

Yes.

Perfect, thank you. This answers all my questions.

I usually sign all the tags I've made (or gbp is doing for me e.g. while importing). So the tagging within a Debian branch looks then

$ ....
$ gbp tag --sign-tags
$ $(other further things to be done)

--
Regards
Carsten

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

* John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> [2021-10-05 11:45]: >Could anyone tell me what the proper gbp command is for creating the changelog >entries for the new release including the proper tag. The gbp manual [1] mentions

Debian tags but it doesn't seem to explain how to create them.

I usually run "gbp dch -R -c" first, then build and upload the
package, and finalize with "gbp tag && gbp push".

And if I wanted to add the tags later manually and push them, what is the expected
format of the tags? Just "debian/$VERSION"?

Yes.

--
⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯

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

iQGzBAABCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmFcIyQACgkQ+C8H+466 LVmtkAv9HNJOLMDWx3PxPD7w2HMW6hmgRSAbbxdL5oE3pV7wLGzdAVBuYHcRNP2I 114t/oHHqsiHhna7re9/p9PqadqyvjOKJZw2ooXn1Zg1qwGNwOYQCfutKl3wSUwC ER7JagG1gY96XfHCOgWzsQ0Mls3sTtzehGjnfLzRU5/KQRWzL5Xysqp9yt3McLqI bfQNopdWZ0lLGL4WpdD83OgHeAkPZY8DVHjKgnbpbtAfh7IJsxCzzVQoW7nrGk/Q MGBQYWabTJ/W1p/PSPudKCD/St5lKrtIlue/Mpobof/QfaCF1cfWnubfUNA+IA5w 3tvcPbnJih13hVNb6PIzmhUE6otG7B1UKEA42BA3irU

On 10/5/21 12:00, Jonas Smedegaard wrote:

I use this spell to finalize a package:

gpb dch -a
dch -r
gbp buildpackage
gbp tag
gbp push

Thanks.

(I guess specifically you were asking for the "gbp tag" step)

Yes, it seems that "gbp tag" is what I was missing.

I guess I can just add the missing tags with "git tag" unless gbp-tag
has a similar feature to add tags for historic commits.

Adrian

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

* Timo Röhling <roehling@debian.org> [2021-10-05 12:04]:

* John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> [2021-10-05 11:45]: >>Could anyone tell me what the proper gbp command is for creating the changelog

entries for the new release including the proper tag. The gbp manual [1] mentions
Debian tags but it doesn't seem to explain how to create them.

I usually run "gbp dch -R -c" first, then build and upload the
package, and finalize with "gbp tag && gbp push".

Or run one of these to build the package and tag it on success:

gbp buildpackage --git-builder=sbuild --git-tag
gbp buildpackage -S --git-tag

Cheers Jochen

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

iQIyBAABCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmFcJa8ACgkQW//cwljm lDMdcA/4nthSR/Dcj3hpt4liDhLLPy6PsgWh3b9QtwKkfEepL/p8xT9v6/FmX5Yb MmWhBI2yt7GJMYn/0AdVkucFlvEVPfdMzM0gXfIIasSXNHYJjkRgCM3mwaYu3eOS CNVFXqg7yJn9yaaec3v6ljEiKNkhA0fYliXCC1K453gHOzZLzvnKOX9b5RMkSjF+ nIRYg9EDZC1DOHAKaby9UZAXvksRczsoByyFtnwO+V4I5ooF/sDvwI4pAfG0nBKL Fpk3AQ3oifG99anF5KTmV0ZJfcHcn3K7VrNq+BxVe8QcAlqqXyUW7Hpqcc7GuQXp +JMKaaE8wKCMWcupDPpkrBqYubwlNuN5ROL8G1lesyT6VIuJ6pKhz7C18w1QPrqA iM8zwaDmEz9CfmDAjW99LyXmNySjgKTxS10FEx7PdvQwrhukU4JWYe+Jo7XiL6Ld CBaiOEiKnqtEcl7EFGO+ujRdKDHNQFacuLeXeC1Ge+AgHtVui7ASb3Wpmn5b0B3h uiQdecgdoB2pprbQr23sdhQjTfrjPODdTQjwgLmHgHdB1qed5hol3KcFMZuHH+h3 MrxoBI8RQW2G+DlbxeiNMocDecpmEIMv8ouYsKqYJo9FTOf2vh4i+PhZT/Q4caIh XymBdBfBMZ3yRpibr8FhMm8d6fxRSGPxycFhqDOJzWEDQIR3gQ==
=C6wF
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Oct 05, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:

Could anyone tell me what the proper gbp command is for creating the changelog

This works for me.

md:~ $ cat ~/bin/git-debtag
#!/bin/sh -e

VER="$(dpkg-parsechangelog --show-field Version)"

if [ -z "$VER" ]; then
echo "Could not parse the changelog!" >&2
exit 1
fi

# mangle the Debian version number as required by git conventions
VER="$(echo "$VER" | sed -e 's/~/_/g' -e 's/:/%/g')"

if dpkg-parsechangelog --show-field Version | egrep -q -- '-[0-9]+$'; then
TAG="debian/$VER"
else
TAG="v$VER"
fi

export GIT_COMMITTER_DATE="$(dpkg-parsechangelog --show-field Date)"

exec git tag -s -m "version $VER" $TAG $1

--
ciao,
Marco

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

iHUEABYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCYVwwqAAKCRDLPsM64d7X gTGnAPwKJcf1odp6WV4bjYTWhn1eUJQWC4/JD/EVxLucD1CXEwD/eP+d1/xwkTqZ wqn07mlz/uGDB2kMfgW+OaUWNTN1MAo=
=2H7V
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Quoting John Paul Adrian Glaubitz (2021-10-05 11:45:55)

(Please CC me as I'm not subscribed to debian-devel)

Hi!

I have noticed some time ago that vcswatch doesn't recognize the releases
of some of my Debian packages such as fs-uae [1]. As a result, it sees 67 commits since the last release, asking me to perform an upload.

However, I have already uploaded all changes and I'm apparently just missing the proper tags. I have always used gbp for git packaging and "gbp dch --auto"
to finalize the changelog, apparently that's not sufficient.

Could anyone tell me what the proper gbp command is for creating the changelog
entries for the new release including the proper tag. The gbp manual [1] mentions
Debian tags but it doesn't seem to explain how to create them.

And if I wanted to add the tags later manually and push them, what is the expected
format of the tags? Just "debian/$VERSION"?

I use this spell to finalize a package:

gpb dch -a
dch -r
gbp buildpackage
gbp tag
gbp push


(I guess specifically you were asking for the "gbp tag" step)


- Jonas

--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/

[x] quote me freely [ ] ask before reusing [ ] keep private --==============Y56689522100393865=MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Description: signature
Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

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

iQIzBAABCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFcIjcACgkQLHwxRsGg ASEMTA/6AmFbdg6iqEprcNY4PdPYh8ujFM3LeuN9V6qEq9bQPX6zChkOzKWxzQ9J neAZHjwcJkhLqsbO4GnrYuk5sWTqy+jlzwmTA/t5PsQX5pXBu+vxusWZJ9YFQLvx Lh7bRgXBhuCsiwYrp+rS+jt++CJmktSwj+kJb8doW2RQJ3Fa+V5BApL7B687NTjf /ODy3n6MsQ1RoKRdkUKTv09HklGiITkacvoWN9zFyVuGgPeQ3NbDu6Uh7u3cX+4O CUJHeX4HLxMAE5XEtKva7XanvTHXDNX9iFKO/696ia51/4ymWfM0WBRtDsM8Xix1 moHgYQ3f6LEFqqulqo8OJZYCXi7yqGIBL93wqyRMfXeaO6EsccmfWBmmL0k2eJs1 uzNqxBZQJJ7uKGcxxgzhXpCYAOKv0pchZQQQ314iyg+L7d6lbTVx+BLsSiqOz4JK 8lwvbgYO9qyTaYrKKAK5VvueEq2mecuTbjkRES7OqwaURy3HMOzTpTx8C/tYX+kF 2i7h5Dm3PtGTiA/fq

Hi Timo!

On 10/5/21 12:04, Timo Röhling wrote:

* John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> [2021-10-05 11:45]:

Could anyone tell me what the proper gbp command is for creating the changelog
entries for the new release including the proper tag. The gbp manual [1] mentions
Debian tags but it doesn't seem to explain how to create them.

I usually run "gbp dch -R -c" first, then build and upload the
package, and finalize with "gbp tag && gbp push".

And if I wanted to add the tags later manually and push them, what is the expected
format of the tags? Just "debian/$VERSION"?

Yes.

Perfect, thank you. This answers all my questions.

Adrian

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Quoting Carsten Schoenert (2021-10-05 12:10:58)

Hello Adrian,

Am 05.10.21 um 12:06 schrieb John Paul Adrian Glaubitz:

Hi Timo!

On 10/5/21 12:04, Timo Röhling wrote:

* John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
[2021-10-05 11:45]:

Could anyone tell me what the proper gbp command is for creating
the changelog entries for the new release including the proper
tag. The gbp manual [1] mentions Debian tags but it doesn't seem
to explain how to create them.

I usually run "gbp dch -R -c" first, then build and upload the
package, and finalize with "gbp tag && gbp push".

And if I wanted to add the tags later manually and push them, what
is the expected format of the tags? Just "debian/$VERSION"?

Yes.

Perfect, thank you. This answers all my questions.

I usually sign all the tags I've made (or gbp is doing for me e.g. while importing). So the tagging within a Debian branch looks then

$ ....
$ gbp tag --sign-tags
$ $(other further things to be done)

I want all tags and imports signed, so add this in packages I maintain:

debian/gbp.conf >>>

# clone this source: gbp clone $PKG_GIT_URL
# track upstream source: git remote add upstream-git $UPSTREAM_GIT_URL
# update this source: gbp pull
# update upstream source: git fetch upstream-git --tags
# import upstream release: gbp import-orig --upstream-vcs-tag=$VERSION --uscan # build package: gbp buildpackage
# publish source release: gbp tag && gbp push

[DEFAULT]
pristine-tar = True
sign-tags = True
filter = */.git*
debian-branch = debian/latest
upstream-branch = upstream/latest
<<< debian/gbp.conf <<<


- Jonas

--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/

[x] quote me freely [ ] ask before reusing [ ] keep private --==============!92693063952960463=MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Description: signature
Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

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

iQIzBAABCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFcKnkACgkQLHwxRsGg ASF2dRAAjg4SYTuRmabJA4WaC7/WALR1cLSrEcCeHzY9NlQhpNGjY64+BLlzHrcp je7uK+nQXd3099d4mNfHK4EzvLipC4WUQkOftTnjdadqOVXXpTu6HvFsCznF6TKp nN978KJcdH2yuzp7ioQT2W57ktKcRCI02M4Ewv0igikHcM/d2SjLfw19ReVnmcD4 KAG6KZ6ka4Mifb9zUvhJuRV299ftOc9avdmaLTVFsreC5Fgy4IdL1su5juXdjPl0 ozh1cCU8uJGarCeixP2GeERFVo3PkyhQZ4aUYrJK7KziULsHhWZhcjOJpsiDQi5e KDAGUqCKubf1k3Hjz64AfFIS0PDmoi1Hsuzt0DIAmwEwQd4TxwNceifUw/D/85Xh asLq8hOKewGURO0HWimEyh9lGw1HxjJoQb49UsVKVWWYS17trTT6RwIpe+NHD/3p dYUjaCSiCdOdg50hwAh4CQntIJbG52ZAK2mHrCvS9GjQHLuqh8vfwcqwOnYCocld q2+oEGACIT1s/zxyC