apt-get source report dead links to git://git.debian.org
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. Try to obtain source code of some package - for example for FreeMat with `apt-get source freemat`
2. Get console output:
Reading package lists... Done
Building dependency tree
Reading state information... Done
NOTICE: 'freemat' packaging is maintained in the 'Git' version control system at:
git://
Need to get 38,1 MB of source archives.
Get:1 http://
Get:2 http://
Get:3 http://
Fetched 38,1 MB in 22s (1 727 kB/s)
gpgv: Signature made Sat. 21 Dec. 2013 06:57:14 MSK using RSA key ID EA330543
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./freemat_
dpkg-source: info: extracting freemat in freemat-4.0
dpkg-source: info: unpacking freemat_
dpkg-source: info: unpacking freemat_
dpkg-source: info: applying 01_gcc_
dpkg-source: info: applying 07_fix_
dpkg-source: info: applying 09_warning.patch
dpkg-source: info: applying 10_llvm.patch
dpkg-source: info: applying gcc4.5.patch
dpkg-source: info: applying 11_ftbfs_qt48.patch
3. Try to get source code manually with `git` command
$ git clone git://git.
Cloning into 'freemat'...
fatal: unable to connect to git.debian.org:
git.
git.
Expected results:
* `apt-get source ...` reports correct link for the source code, user is able to get the source code manually.
Actual results:
* `apt-get source ...` reports wrong link for the source code, user is unable to get the source code manually.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.18
ProcVersionSign
Uname: Linux 3.13.0-153-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Jan 20 20:06:41 2019
InstallationDate: Installed on 2018-07-22 (181 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
Packages get updated and their source moved. Within Debian, the old git hosting infrastructure got replaced by the gitlab instance on https:/ /salsa. debian. org/. Given that there is not really a default schema where/how packages moved, redirects aren't an option. Older packages in the pool don't get updated for that, and only updated packages have current information again. Thus this is a wontfix or rather "will-fix- itself- over-time" .