From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: [PATCH] debian: Ensure changelog distribution is tagged
Date: Thu, 23 Sep 2021 11:34:27 +0100
Message-ID: <8411109B-824D-4323-AEFD-DBE34EB04194@ipfire.org>
In-Reply-To: <20210923102350.4613-1-valter.jansons@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6557656728241212458=="
List-Id: <location.lists.ipfire.org>

--===============6557656728241212458==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Valters,

Thank you for your patch. I have merged it.

> On 23 Sep 2021, at 11:23, Valters Jansons <valter.jansons(a)gmail.com> wrot=
e:
>=20
> UNRELEASED should not be left as-is when actually releasing.
> The latest changelog entry now point at unstable instead.
>=20
> The simple d/genchangelog.sh now does `dch -r ''` automatically
> to ensure this distribution update doesn't get lost along the way
> on future invocations.
> ---
> I am still not sure what to propose for organizing this better across
> multiple projects. In our organization we use `repo` by Google,
> originally intended for syncing Android repositories, so that we track
> multiple repositories that belong together while avoiding mono-repos.

Hmm, I do not think it is worth it to add a large dependency just to keep a c=
ouple of scripts in sync.

If we would want to go down that line, I would say a Git submodule is the eas=
iest way and should work well.

Do you know any cool build tools that could automatically build and publish t=
hese packages? I have a couple of custom built scripts (debian/build.sh and s=
omething more to publish and sign the packages), but that doesn=E2=80=99t fee=
l very rock-solid to me.

-Michael

> It uses a default.xml manifest file in a dedicated "manifest" repo,
> which then just lists which repositories should be pulled in.
>=20
> Command/tool ref: https://source.android.com/setup/develop/repo
> Manifest file ref: https://gerrit.googlesource.com/git-repo/+/master/docs/m=
anifest-format.md
>=20
> A sample manifest, which should do the trick, could be:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <manifest>
>  <remote name=3D"origin"
>    fetch=3D"https://git.ipfire.org/pub/git/"
>    pushurl=3D"ssh://people.ipfire.org/pub/git/" />
>  <default remote=3D"origin" revision=3D"master" />
>=20
>  <project name=3D"location/libloc" />
>  <project name=3D"location/location-database" />
> </manifest>
>=20
> debian/changelog       | 2 +-
> debian/genchangelog.sh | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>=20
> diff --git a/debian/changelog b/debian/changelog
> index fcef2cb..3b90542 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,4 +1,4 @@
> -libloc (0.9.8-1) UNRELEASED; urgency=3Dmedium
> +libloc (0.9.8-1) unstable; urgency=3Dmedium
>=20
>   [ Michael Tremer ]
>   * importer: Do not try to initialise a column that cannot be NULL with
> diff --git a/debian/genchangelog.sh b/debian/genchangelog.sh
> index 85d3922..ab1c198 100755
> --- a/debian/genchangelog.sh
> +++ b/debian/genchangelog.sh
> @@ -31,6 +31,8 @@ main () {
>     echo "$author_name <$author_email>  $subject"
>     DEBFULLNAME=3D"$author_name" DEBEMAIL=3D"$author_email" debchange --ups=
tream --multimaint-merge "$subject"
>   done
> +
> +  debchange --release ''
> }
>=20
> main "$@" || exit $?
> --=20
> 2.33.0
>=20


--===============6557656728241212458==--