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: Rework historical changelog
Date: Wed, 14 Apr 2021 11:05:12 +0100
Message-ID: <7BEE897E-853B-4A28-B470-8DA9DD2821DA@ipfire.org>
In-Reply-To:
 <CA+sCei1D83bTxJRdTeV_XCTe_yHOZsD7suB2emtnCrC9G4wMow@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2186327667457780536=="
List-Id: <location.lists.ipfire.org>

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

Hello,

> On 14 Apr 2021, at 11:03, Valters Jansons <valter.jansons(a)gmail.com> wrot=
e:
>=20
> On Wed, Apr 14, 2021 at 12:31 PM Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
>> It should work just fine on Ubuntu. We are only dependent on a POSIX-compa=
tible system so Windows might be a bit tricky. I used to build it on Mac OS X=
, too.
>>=20
>> If there is interest, I wouldn=E2=80=99t mind publishing Ubuntu packages. =
Better would of course be to make it an upstream package.
>=20
> Understandable - and I completely agree in the benefit of having the
> package available in Debian to be pulled into all Debian derivative
> distributions that way.
>=20
> The building problem is not directly linked with Ubuntu. Instead, it
> is about auto_test failing, due to `make check` failing on the root
> Makefile. Testsuite for libloc in the root directory passes, however
> the check-recursive target then tries to `make check` inside of po
> subdirectory which fails with: "No rule to make target
> '../src/python/__init__.py', needed by 'libloc.pot'.  Stop."
>=20
> The broken scenario that needs patching can simplified to:
> $ autoreconf --install --symlink
> $ intltoolize --force --automake
> $ ./configure --prefix=3D/usr --sysconfdir=3D/etc --libdir=3D/lib
> $ make -j$(nproc)
> $ make -j$(nproc) check
>=20
> I will shortly provide a patch with an updated po/POTFILES.in as
> generated by `rm po/POTFILES.in && make po/POTFILES.in`.

This does not show any changes on my system.

>>> You can take the `debmirror` tool as a simple example. The official
>>> upstream changelog there can be seen in the source containing
>>> "unstable": https://salsa.debian.org/debian/debmirror/-/blob/debian/1%252=
.33/debian/changelog
>>>=20
>>> As people are working on future changes, "UNRELEASED" is used for
>>> tracking changes until the release is tagged (by replacing
>>> "UNRELEASED" with "unstable", and updating the maintainer name/email
>>> and date). A sample of work in progress in source can be seen:
>>> https://salsa.debian.org/debian/debmirror/-/blob/0f9992cdb9b535bd42958a9f=
f6cb07723f064006/debian/changelog
>>=20
>> We normally do not build packages with a development version.
>=20
> The UNRELEASED distribution is tagged for that reason, as to signal
> that a package should not be built from that source. I was simply
> highlighting a development workflow in place for one Debian package
> which tracks changes during development, where individual
> commits/patches also update the changelog file. This approach ensures
> that at release time only the s/UNRELEASED/unstable/ replacement needs
> to happen along with `update-maintainer` -- without having to worry
> about collecting the list of changes.
>=20
> --Valters


--===============2186327667457780536==--