public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Valters Jansons <valter.jansons@gmail.com>
To: location@lists.ipfire.org
Subject: Re: [PATCH] debian: Rework historical changelog
Date: Tue, 13 Apr 2021 19:41:52 +0300	[thread overview]
Message-ID: <CA+sCei3_UNw_bVwEPsEug2r5v5mAjHiNQc+x+G7S0Vj_oDs-dA@mail.gmail.com> (raw)
In-Reply-To: <d73906a6-a0ea-da2d-1d1b-8c825dbcafdd@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]

On Tue, Apr 13, 2021 at 6:38 PM Peter Müller <peter.mueller(a)ipfire.org> wrote:
> Eventually, we hoped libloc would be used by other distributions as well, since a decent
> part of the open source community is facing license trouble after MaxMind changed their
> terms and conditions. I remember Michael having a discussion with some members of the
> Debian development team, but my memories fail me when it comes to it's results.
>
> Therefore, I am not sure if libloc is ready in a way we would move from "UNRELEASED" to
> "unstable". On the one hand, it is used in production for IPFire since a while, on the
> other hand, nobody else is using the libloc _code_ as such - at least no one I am aware of.

I am in that boat actually, as I ended up looking at the repository
with the goal of migrating away from MaxMind, however I am on Ubuntu.
The build currently fails due to a bad test invocation which I hope to
take a closer look at. Additionally I would like to update the
debhelper compatibility level while I am at it, but that also needs to
be looked into - whether the resulting build is the same, however for
that I would like to have the automated build tooling in place (which
needs those test changes).

Regarding the topic of "UNRELEASED" vs "unstable": Having "unstable"
for a _released_ version is the standard way for Debian-native
packages.

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

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/0f9992cdb9b535bd42958a9ff6cb07723f064006/debian/changelog

The tool is available in Ubuntu repositories as well, where additional
patches are applied -- replacing Debian defaults with Ubuntu defaults
as required for the package. As a result, in Ubuntu a separate version
with a 'ubuntu' suffix gets created, while the history still lists
"unstable" throughout from its upstream:
https://changelogs.ubuntu.com/changelogs/pool/universe/d/debmirror/debmirror_2.33ubuntu1/changelog

--Valters

  reply	other threads:[~2021-04-13 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 13:01 Valters Jansons
2021-04-13 15:38 ` Peter Müller
2021-04-13 16:41   ` Valters Jansons [this message]
2021-04-14  9:31     ` Michael Tremer
2021-04-14 10:03       ` Valters Jansons
2021-04-14 10:05         ` Michael Tremer
2021-04-14 10:08           ` Valters Jansons
2021-04-14  9:28   ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+sCei3_UNw_bVwEPsEug2r5v5mAjHiNQc+x+G7S0Vj_oDs-dA@mail.gmail.com \
    --to=valter.jansons@gmail.com \
    --cc=location@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox