Dear Adam, thanks for your message. I am out of office for 10 days, so I tried the same steps again on a different PC. This time it worked without any problem.
FYI here is what I did: Using VirtualBox on Win11 Host Install Trixie RC2 Amd64 Netinst Choose German / Germany and Xfce Desktop sudo apt install build-essential sudo apt install libdbus-1-dev As far as I can tell I did everything as before. No idea why it behaves differently now. Ok, looks like the problem is gone now, so you may close this issue. Thanks for your time and best regards, Christoph -----Original Message----- From: Adam D. Barratt <[email protected]> Sent: Friday, August 1, 2025 7:10 PM To: Christoph Strunk <[email protected]>; [email protected] Cc: [email protected]; Simon McVittie <[email protected]> Subject: Re: Bug#1110212: Failed while fetching libcap-dev from deb.debian.org (Fastly): 403 Forbidden Control: tags -1 + moreinfo On Fri, 2025-08-01 at 17:28 +0100, Simon McVittie wrote: > On Fri, 01 Aug 2025 at 09:22:40 +0200, Christoph Strunk wrote: > > in Debian trixie (even in RC2) the package cannot be installed > > because it depends on libcap-dev which cannot be installed. > > > > When executing "sudo apt install libdbus-1-dev" it always ends up > > in error message like (manually translated from german) > > Err:1 http://deb.debian.org/debian trixie/main amd64 libcap-dev > > amd64 1:2.75-10+b1 > > 403 Forbidden [IP: 146.75.122.132 80] > > Error: Failed while fetching > > http://deb.debian.org/debian/pool/main/libc/libcap2/libcap-dev_2.75-10%2bb1_amd64.deb > > 403 Forbidden [IP: 146.75.122.132 80] > > > > As a result, libdbus-1-dev cannot be installed. > > This is not a bug in libdbus-1-dev, which genuinely does require > libcap-dev. It seems more like a problem with the deb.debian.org > mirror provided by the Fastly CDN service, so I'm reassigning the bug > to the mirrors pseudo-package. In principle, I'd agree that it looks like a mirror issue. However, the deb.debian.org Fastly configuration results in all 403s being logged on one of Debian's central logging servers, and the log for today contains no trace of the failure mentioned above. I've also failed to reproduce the issue in manual testing: adam@darzee:~$ curl -v --resolve deb.debian.org:80:146.75.122.132 http://deb.debian.org/debian/pool/main/libc/libcap2/libcap-dev_2.75-10%2bb1_amd64.deb * Added deb.debian.org:80:146.75.122.132 to DNS cache * Hostname deb.debian.org was found in DNS cache * Trying 146.75.122.132:80... * Connected to deb.debian.org (146.75.122.132) port 80 (#0) > GET /debian/pool/main/libc/libcap2/libcap-dev_2.75-10%2bb1_amd64.deb HTTP/1.1 > Host: deb.debian.org > User-Agent: curl/7.88.1 > Accept: */* > < HTTP/1.1 200 OK Is the issue still reproducible for you? Does it also manifest if you use HTTPS rather than HTTP? Regards, Adam
