php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #55861 snaps.php.net links to the wrong snapshot if you look at the right time
Submitted: 2011-10-06 14:47 UTC Modified: 2012-05-16 22:37 UTC
From: dk at uw dot no Assigned:
Status: Wont fix Package: Website problem
PHP Version: Irrelevant OS: N/A
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: dk at uw dot no
New email:
PHP Version: OS:

 

 [2011-10-06 14:47 UTC] dk at uw dot no 
Description:
------------
I saw this just now, while browsing for the latest code snapshot.

If you look at http://snaps.php.net/ while the tarballs are being generated, you may be (un)lucky enough to be presented with a 'half updated' view of reality.

In the case below, apparently just the .bz2 had yet been regenerated, and its link had been updated (...1430.tar.bz2), but the .gz was still the old link (...1230.tar.gz). Nevertheless it was claimed that both was built on the latest date.

Granted, this is extremely low impact, and it fixes itself after a minute or so when the .gz version is fully generated as well.


Generated HTML-output:

<th>Source</th></tr>
<tr>
<td valign="top">
<span><a href="php5.4-201110061430.tar.bz2">php-5.4-dev (tar.bz2)</a> (11.0M)</span><br>
<span><a href="php5.4-201110061230.tar.gz">php-5.4-dev (tar.gz)</a> (14.6M)</span><br>
<br></td>
</tr>
<tr>
<td>
<b>Built on:</b> Oct&nbsp;06,&nbsp;2011&nbsp;14:30&nbsp;UTC<br>
<span class="filelink"><a href="/index.php?branch=5.4&amp;distro=Source">Previous Builds</a></span><br>
</td>

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2012-05-16 22:37 UTC] danbrown@php.net
-Status: Open +Status: Wont fix
 [2012-05-16 22:37 UTC] danbrown@php.net 
A similar issue could potentially arise if a user is in the middle of 
downloading the snapshot as the new ones are released by the system.  For 
example, trying to download php5.4-latest.tar.xz could potentially be broken 
during the download if its symlink is replaced and linked to a newer snap.

Though inconvenient, as you said, it's very, very low-impact, and not something 
that justifies redeveloping the system to prevent.

Thank you for your report, though.  And if you continue to have timing like 
that, you really need to play the lottery.  ;-P
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Wed Jan 15 13:01:29 2025 UTC