linux download filename has extra .tar
Categories
(Firefox :: File Handling, defect, P1)
Tracking
()
People
(Reporter: pf, Unassigned)
Details
+++ This bug was initially created as a clone of Bug #1770683 +++
I don't see a way to re-open that bug which is showing fixed/verified; but getting the latest Nightly, the .tar is still present...
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
firefox-102.0a1.en-US.linux-x86_64.tar.bz2 is posted as:
firefox-102.0a1.en-US.linux-x86_64.tar.bz2.tar <====<<<
This started after May 8. I always use the tar command out of my history, so I've been running the 05-08 version since then. Tonight, it was obvious something had to be wrong... tracked it down to my issuing:
tar xf firefox-102.0a1.en-US.linux-x86_64.tar.bz2
all this time until noticing the newer files have .tar added which makes no sense.
Actual results:
Someone updated a script..?
Expected results:
More careful editing... :)
|
||
Comment 1•3 years ago
|
||
What version of nightly are you using? You seem to be saying that you are using a version from a month ago.
|
||
Updated•3 years ago
|
|
Reporter | |
Comment 2•3 years ago
|
||
Since I couldn't find a way to re-open my original bug, I cloned it. This .tar issue has been messing up my updating (manual since browser is not run as root; but image is in /usr/local/bin/ which is owned by root -- I may need to review this).
Looks like I've been on 5/26 for 2 weeks:
Mozilla Firefox 102.0a1 20220526213638 20220526213638
until just now... (I was updating the binary when your question arrived.) After manually correcting this download, I'm on:
Mozilla Firefox 103.0a1 20220607214725 20220607214725
but since it's up-to-date, I'll have to wait until the next update to re-check.
So is this .tar within the browser? I would have bet on that being a server file naming issue...
|
||
Comment 3•3 years ago
|
||
At this point this bug really really needs accurate, detailed, and up-to-date steps. The steps from comment 0 are just copied and presumably obsolete? You now talk about "updating" the browser but offer no details, so it's really not clear what download is happening, how it's happening, what the actual/expected results are, and with what nightly build you're still seeing an issue.
|
|
||
Comment 4•3 years ago
|
||
:pf, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.
|
|
Reporter | |
Comment 5•3 years ago
|
||
I was under the impression this was a website problem; now, it appears it was within the browser itself, right?
Updating to 103 has solved it. Sorry for the confusion.
Description
•