Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#648 closed defect (worksforme)

Debian - Failed to fetch nginx source package

Reported by: https://stackoverflow.com/users/573152/bernard-rosset Owned by:
Priority: major Milestone:
Component: nginx-package Version: 1.6.x
Keywords: Debian Wheezy Cc:
uname -a: Linux 3.16-0.bpo.2-amd64 #1 SMP Debian 3.16.3-2~bpo70+1 (2014-09-21) x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.6.2
built by gcc 4.7.2 (Debian 4.7.2-5)

Description

When using the following sources:

deb http://nginx.org/packages/debian/ wheezy nginx
deb-src http://nginx.org/packages/debian/ wheezy nginx

and using the following commands:

sudo aptitude clean
sudo aptitude update

I get the following errors:

Error http://nginx.org wheezy/nginx Sources
  404  Not Found
[...]
E: Failed to fetch http://nginx.org/packages/debian/dists/wheezy/nginx/source/Sources : 404  Not Found

The binary package seems to update OK, but the sources one seems to fail.
I noticed the error during the nginx.conf already (when installing nginx during the training sessions) but I thought that was a local problem.

You might want to check if something has been broken in the package system last week.

Change History (2)

comment:1 by Sergey Budnevitch, 6 years ago

Resolution: worksforme
Status: newclosed

apt-get source nginx installs nginx sources quite well on deb7. There is no http://nginx.org/packages/debian/dists/wheezy/nginx/source/Sources file actually, but there is gzipped version http://nginx.org/packages/debian/dists/wheezy/nginx/source/Sources.gz and apt-get does install it with default settings. Please check apt configs on your side.

comment:2 by https://stackoverflow.com/users/573152/bernard-rosset, 6 years ago

It seemed strange indeed.

It may be related to the recent update of apt pushed for Debian-related systems.

I had no strange leftovers in the APT cache, but the index would not stop to fail to being rebuilt.
I actually managed to fix that by removing/adding again sources stanza for nginx and cleaning/updating the cache in between.

Well, if anyone gets this strange error, know you know where it came from... ;o)

Note: See TracTickets for help on using tickets.