Does anyone know if removing source code from the repo is a policy change or an error?

Hello!
Today when using apt source to grab a tarball from cli, I was receiving some errors, I was not paying attention, then I realized it was 404 errors.

Going to the main repo at archive.ubuntu.com I saw that there are no more tarballs anywhere?

I’ve looked and seems like as the mirrors are more and more getting in sync with this removal.

Here’s an example:

https://mirrors.ocf.berkeley.edu/ubuntu/pool/main/c/casper/
https://archive.ubuntu.com/ubuntu/pool/main/c/casper/

$ apt source linux
Reading package lists... Done
NOTICE: 'linux' packaging is maintained in the 'Git' version control system at:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
Please use:
git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 235 MB of source archives.
Err:1 http://mx.archive.ubuntu.com/ubuntu noble-updates/main linux 6.8.0-59.61 (dsc)
  404  Not Found [IP: 185.125.190.82 80]
Err:2 http://mx.archive.ubuntu.com/ubuntu noble-updates/main linux 6.8.0-59.61 (tar)
  404  Not Found [IP: 185.125.190.82 80]
Err:3 http://mx.archive.ubuntu.com/ubuntu noble-updates/main linux 6.8.0-59.61 (diff)
  404  Not Found [IP: 185.125.190.82 80]
E: Failed to fetch http://mx.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux_6.8.0-59.61.dsc  404  Not Found [IP: 185.125.190.82 80]
E: Failed to fetch http://mx.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux_6.8.0.orig.tar.gz  404  Not Found [IP: 185.125.190.82 80]
E: Failed to fetch http://mx.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux_6.8.0-59.61.diff.gz  404  Not Found [IP: 185.125.190.82 80]
E: Failed to fetch some archives.

$ apt source casper
Reading package lists... Done
NOTICE: 'casper' packaging is maintained in the 'Git' version control system at:
https://git.launchpad.net/casper
Please use:
git clone https://git.launchpad.net/casper
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 109 kB of source archives.
Err:1 http://mx.archive.ubuntu.com/ubuntu noble/main casper 1.498 (dsc)
  404  Not Found [IP: 91.189.91.81 80]
Err:2 http://mx.archive.ubuntu.com/ubuntu noble/main casper 1.498 (tar)
  404  Not Found [IP: 91.189.91.81 80]
E: Failed to fetch http://mx.archive.ubuntu.com/ubuntu/pool/main/c/casper/casper_1.498.dsc  404  Not Found [IP: 91.189.91.81 80]
E: Failed to fetch http://mx.archive.ubuntu.com/ubuntu/pool/main/c/casper/casper_1.498.tar.xz  404  Not Found [IP: 91.189.91.81 80]
E: Failed to fetch some archives.

My question is:

Do you not if this is a change in policy or maybe someone had a bad day at work, and hopefully they’ll be back later?

There is a technical problem on the mirroring mechanism, currently under investigation.

4 Likes

It’s by accident, not by design. Canonical are aware, and it’s being investigated. Some internal machinery at Canonical on the Launchpad side has broken.

If you want the source files before the issue is fixed, though, you can still find them on Launchpad.

e.g. 1.498 : casper package : Ubuntu & 6.8.0-59.61 : linux package : Ubuntu

You can use the same pattern as I did above for the URL or search your engine for ($PACKAGE)_($VERSION) launchpad $(UBUNTU_RELEASE). It’s almost always the first hit.

5 Likes

The internal archive mirror now has source packages, they are in the process of being synced out to the machines behind archive.ubuntu.com etc so this should all be fixed soon.

6 Likes

Thank you for the quick answers.
Hopefully that will be back in place in the coming hours / days.

Best regards.

Hi,

the source files are now back. But there seems to be one missing:

ubuntu/pool/universe/p/plib-doc/plib-doc_1.8.5.orig.tar.gz

which is listed in

ubuntu/dists/bionic/universe/source/Sources.gz
ubuntu/dists/focal/universe/source/Sources.gz
ubuntu/dists/bionic/universe/source/Sources.xz
ubuntu/dists/focal/universe/source/Sources.xz

Can you check if this is intentional?

Regards,
Jean Rene

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.