A bit ago, I wrote:
On 9/26/23 08:33, Simon McVittie wrote:
If we disregard non-standardized files like changelog.Debian.devmapper.gz,
I think we can model changelog entries as being keyed by (source package,
source version) pairs.
Changing apt-listchanges so that it always uses the version
Hi Simon,
Thanks for the response! Comments below.
On 9/26/23 08:33, Simon McVittie wrote:
If we disregard non-standardized files like changelog.Debian.devmapper.gz,
I think we can model changelog entries as being keyed by (source package,
source version) pairs.
Changing apt-listchanges so
On Tue, 26 Sep 2023 at 06:11:01 -0400, Jonathan Kamens wrote:
> This approach was based on two assumptions, neither of which is always
> true:
>
> 1. Assume that the version numbering for all packages that come from
>the same source package are in the same series.
> 2. Assume that the version
Hi Stefano,
Thanks for your quick reply! More thoughts inline below.
On 9/26/23 07:08, Stefano Rivera wrote:
Thanks for taking on a much bigger job than you probably expected to
have signed up for :)
Indeed, this has turned out to be a larger endeavor than I had expected,
but on the flip
Hi Jonathan (2023.09.26_10:11:01_+)
> I am hoping that this is an acceptable request to make of the
> technical committee
Absolutely. In this case, I doubt the committee needs to offer any
formal advice. These are my personal views, after only a few minutes of
thought.
> That bug prompted me
Package: tech-ctte
Severity: normal
Hello all,
I am hoping that this is an acceptable request to make of the
technical committee, for reasons which I explain below, but if not,
then I apologize for bothering you and you should kindly tell me to
buzz off. Thanks.
I'm in the process of adopting
6 matches
Mail list logo
