[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#910877: marked as done (apt: Inconsistent behavior for a package version with an epoch)

Your message dated Fri, 9 May 2025 17:49:24 +0200
with message-id <20250509174821.GA1091248@debian.org>
and subject line Re: Bug#910877: apt: Inconsistent behavior for a package version with an epoch
has caused the Debian Bug report #910877,
regarding apt: Inconsistent behavior for a package version with an epoch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
910877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910877
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 1.4.8


$ apt-get source mongodb-dev=2:1.1.2-5
Fetched
$ apt-get source mongodb-dev=1.1.2-5
Fetched

$ apt-get download mongodb-dev=2:1.1.2-5
Fetched
$ apt-get download mongodb-dev=1.1.2-5
E: Version '1.1.2-5' for 'mongodb-dev' was not found

$ apt-get changelog mongodb-dev=2:1.1.2-5
Fetched
$ apt-get changelog mongodb-dev=1.1.2-5
E: Version '1.1.2-5' for 'mongodb-dev' was not found


It would be nice, if all commands select package of version with the
highest epoch automatically.

--- End Message ---
--- Begin Message --- 
On Sun, Apr 27, 2025 at 12:30:47PM +0200, Kamil Ignacak wrote:
> One thing that caught my eye here is that binary package's version includes
> epoch, whereas source package's version doesn't include epoch. Perhaps this
> is why "apt-get source" is able to fetch source of mongodb-dev in both cases.
[...]
> As you can see, both binary and source packages include epoch in version
> string, and apt-get source is unable to find a package when queried for
> version without epoch.
[...]
> I don't know what is the correct behaviour of apt when dealing with
> epoch numbers, but maybe the source of problem is the inconsistency in
> mongodb's version strings.

Indeed. APT treats epoch as part of the version string, and there is no
special casing for them, nor should there be.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en

--- End Message ---
Reply to: