Package version given as 0.0.0

Bug #2011821 reported by Bob Kline
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apscheduler (Ubuntu)
New
Undecided
Unassigned

Bug Description

The build of Python APScheduler created for the Ubuntu package incorrectly gives the version number when running in Python as 0.0.0, even though the package manager claims it has installed version 3.8.1.

$ dpkg -l | grep apscheduler
ii python3-apscheduler 3.8.1-1 all In-process task scheduler with Cron-like capabilities
$ python3 -c 'import apscheduler as a; print(a.version)'
0.0.0

In a virtual environment with the package installed using pip, the package has been built correctly, and gives the real version number from Python (as it does if I build the package by hand).

$ . venv/bin/activate
(venv) $ python3 -c 'import apscheduler as a; print(a.version)'
3.10.1

The same discrepancy is present if I use the Python builtin importlib.metadata.

The inability to query the package at runtime to determine its version prevents software from making correct decisions about how the package will behave.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: python3-apscheduler 3.8.1-1
ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 16 07:21:46 2023
InstallationDate: Installed on 2020-05-23 (1026 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apscheduler
UpgradeStatus: Upgraded to jammy on 2023-03-15 (0 days ago)

Revision history for this message
Bob Kline (bob.kline) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.