Firefox's official Debian package repository is 404 / broken link
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: mjevans1983, Unassigned)
Details
Steps to reproduce:
Follow the steps for "Install Firefox .deb package for Debian-based distributions (Recommended)"
https://packages.mozilla.org/apt leads to 404, not a Debian software repository / archive.
Step 4 (is broken)
Next, add the Mozilla APT repository to your sources list:
echo "deb [signed-by=/etc/apt/keyrings/packages.mozilla.org.asc] https://packages.mozilla.org/apt mozilla main" | sudo tee -a /etc/apt/sources.list.d/mozilla.list > /dev/null
Actual results:
It used to work, now there are no Firefox updates on Debian systems.
Expected results:
Firefox updates should continue to exist.
Comment 1•10 months ago
|
||
https://packages.mozilla.org/apt leads to 404, not a Debian software repository / archive.
That doesn't mean much. What matters is e.g. https://packages.mozilla.org/apt/dists/mozilla/Release or https://packages.mozilla.org/apt/dists/mozilla/main/binary-arm64/Packages, which work.
Did you actually edit your apt sources and used apt?
| Reporter | ||
Comment 2•10 months ago
|
||
Those links work, and I just got back from some errands that included visiting the relative's house where the laptop that couldn't reach the repo, and on which I tried to manually get there based on the URL in the repository line and thus seeing a 404 locked in on 'This is the problem, it must show me a valid result before I re-enable that source'.
So, it's working right now, but the lack of even a landing page on https://packages.mozilla.org/apt to direct someone where to test, or better, just a traditional auto-index of files, makes human trouble tests require 'expert in Debian package repository structure' status as well as moving past the 404 as an overall 'something broke this directory tree' indication.
Repeating, it is working, but whatever reason https://packages.mozilla.org/apt is set to not display a working result makes troubleshooting when it isn't working terribly difficult.
Comment 3•10 months ago
|
||
@glandium
Is this invalid? If not, I'm guessing is an enhancement request, but not sure in which component it belongs.
| Reporter | ||
Comment 4•10 months ago
|
||
I agree, when I filed it I thought it was much worse because it's so difficult for a human to troubleshoot. I'm also sorry, I could not find any better place to file it because infrastructure issues don't have a clear reporting path.
Comment 5•10 months ago
|
||
Closing as INVALID for now.
Description
•