Difference between revisions of "Bugs"

From AminetWiki
Jump to navigation Jump to search
Line 15: Line 15:
 
{| border="1" cellspacing="0" cellpadding="5"
 
{| border="1" cellspacing="0" cellpadding="5"
 
! ID
 
! ID
| 2007-02-18-03
+
| 2008-06-18-01
 
|-
 
|-
 
! Status
 
! Status
Line 21: Line 21:
 
|-  
 
|-  
 
! Description
 
! Description
| When replacing an existing file, admin.pl fails to move the old package to priv/deleted:
+
| moderating comm/net/MarranoFTP.lha while package comm/net/marranoftp.zip already exists, results in the proper "Already on Aminet:" warning. Choosing to replace the existing package will move the old readme to deleted/, but marranoftp.zip is still in comm/net, and still in the database. Note that this behaviour is pretty much as in bug 2006-06-05-01, but it does no longer 'silently' accept the new package (cg)
 
 
mv: cannot stat `../util/sys/Argue.lha': No such file or directory
 
 
|}
 
|}
  
Line 29: Line 27:
 
{| border="1" cellspacing="0" cellpadding="5"
 
{| border="1" cellspacing="0" cellpadding="5"
 
! ID
 
! ID
| 2007-02-18-01
+
| 2007-02-18-03
 
|-
 
|-
 
! Status
 
! Status
Line 35: Line 33:
 
|-  
 
|-  
 
! Description
 
! Description
| ADT server is not running yet. It also needs to be added to server startup.
+
| When replacing an existing file, admin.pl fails to move the old package to priv/deleted:
|}
 
  
 
+
mv: cannot stat `../util/sys/Argue.lha': No such file or directory
{| border="1" cellspacing="0" cellpadding="5"
+
(cg)
! ID
 
| 2007-02-15-03
 
|-
 
! Status
 
| NEW
 
|-
 
! Description
 
| Using admin.php to delete files won't let the moderator enter a reason for deleting the package:
 
 
 
home/aminet/aminet_root/doc>/home/aminet/aminet_root/phpinclude/admin.php delete_package util/wb/AmiSnap11.lha<br>
 
X-Powered-By: PHP/5.1.2<br>
 
Content-type: text/html<br>
 
Please state a reason for deleting util/wb/AmiSnap11.lha<br>
 
Reason: SUCCESS: Deleted: util/wb/AmiSnap11.lha<br>
 
 
|}
 
|}
  
Line 59: Line 42:
 
{| border="1" cellspacing="0" cellpadding="5"
 
{| border="1" cellspacing="0" cellpadding="5"
 
! ID
 
! ID
| 2007-02-15-02
+
| 2007-02-18-01
 
|-
 
|-
 
! Status
 
! Status
Line 65: Line 48:
 
|-  
 
|-  
 
! Description
 
! Description
| Using admin.php to move files results in an error message that admin.php is unable to fix the moved readme's type: field:
+
| ADT server is not running yet. It also needs to be added to server startup (cg)
 
 
home/aminet/aminet_root/doc>/home/aminet/aminet_root/phpinclude/admin.php move_package game/misc/Q2CE.lha game/edit<br>
 
X-Powered-By: PHP/5.1.2<br>
 
Content-type: text/html<br>
 
Renaming game/misc/Q2CE.lha to game/edit/Q2CE.lha in database<br>
 
Moving game/misc/Q2CE.lha to game/edit/Q2CE.lha in filesystem<br>
 
Moving game/misc/Q2CE.readme to game/edit/Q2CE.readme<br>
 
Unable to read from readme file for editing "type"-header<br>
 
 
|}
 
|}
 
  
  
Line 86: Line 60:
 
|-  
 
|-  
 
! Description
 
! Description
| If an uploaded package has a size of 0 bytes, the email offered for flaming is that of the *previously* moderated package. This only happens under certain circumstances, probably if the faulty package has no uploader email of its own.
+
| If an uploaded package has a size of 0 bytes, the email offered for flaming is that of the *previously* moderated package. This only happens under certain circumstances, probably if the faulty package has no uploader email of its own (cg)
 
|}
 
|}
  
Line 99: Line 73:
 
|-  
 
|-  
 
! Description
 
! Description
| AmFTP doesn't display RECENT files when in ADT mode
+
| AmFTP doesn't display RECENT files when in ADT mode (cg)
 
|}
 
|}
  
Line 125: Line 99:
 
|-  
 
|-  
 
! Description
 
! Description
| If a readme contains backslashes (in the body, not in one of the header fields - didn't check header fields), these get stripped from *both* the actual readme *and* the database entry. Enclosing the string containing backslashes in double quotes helps the backslashes to actually reach the database entry, but they're still getting stripped from the actual readme. An example would be the windows path in [http://main.aminet.net/package.php?package=comm/www/firefox_searchplugin.zip comm/www/firefox_searchplugin.zip]. (cg)
+
| If a readme contains backslashes (in the body, not in one of the header fields - didn't check header fields), these get stripped from *both* the actual readme *and* the database entry. Enclosing the string containing backslashes in double quotes helps the backslashes to actually reach the database entry, but they're still getting stripped from the actual readme. An example would be the windows path in [http://main.aminet.net/package.php?package=comm/www/firefox_searchplugin.zip comm/www/firefox_searchplugin.zip] (cg)
 
|}
 
|}
  
Line 138: Line 112:
 
|-  
 
|-  
 
! Description
 
! Description
| admin.pl will not complain if you try to moderate misc/unix/foo.tar.bz2 while misc/unix/foo.tgz already exists, it will overwrite the existing readme instead. Both packages will be listed in the database afterwards.
+
| admin.pl will not complain if you try to moderate misc/unix/foo.tar.bz2 while misc/unix/foo.tgz already exists, it will overwrite the existing readme instead. Both packages will be listed in the database afterwards (cg)
  
 
<b>Update</b> (20060728):
 
<b>Update</b> (20060728):
  
This is apparently not limited to 'double' extensions ("tar.gzip" etc.). Yesterday admin.pl silently accepted mods/boray/DayUnknown.zip while mods/boray/DayUnknown.lha already existed.
+
This is apparently not limited to 'double' extensions ("tar.gzip" etc.). Yesterday admin.pl silently accepted mods/boray/DayUnknown.zip while mods/boray/DayUnknown.lha already existed (cg)
|}
 
 
 
 
 
 
 
{| border="1" cellspacing="0" cellpadding="5"
 
! ID
 
| 2006-06-17-01
 
|-
 
! Status
 
| NEW
 
|-
 
! Description
 
| According to "eisblock", who used to run "Aminet Comments" at http://www.amiga-online-games.de/AmiNetCom/ (currently offline), his server can no longer access the ADT_RECENT#? files
 
 
|}
 
|}

Revision as of 23:54, 17 June 2008

File bugs here, move them to Changelog when they are fixed. Use the following format:

ID YYYY-MM-DD-number
Status NEW
Description Some description


ID 2008-06-18-01
Status NEW
Description moderating comm/net/MarranoFTP.lha while package comm/net/marranoftp.zip already exists, results in the proper "Already on Aminet:" warning. Choosing to replace the existing package will move the old readme to deleted/, but marranoftp.zip is still in comm/net, and still in the database. Note that this behaviour is pretty much as in bug 2006-06-05-01, but it does no longer 'silently' accept the new package (cg)


ID 2007-02-18-03
Status NEW
Description When replacing an existing file, admin.pl fails to move the old package to priv/deleted:

mv: cannot stat `../util/sys/Argue.lha': No such file or directory (cg)


ID 2007-02-18-01
Status NEW
Description ADT server is not running yet. It also needs to be added to server startup (cg)


ID 2007-02-15-01
Status NEW
Description If an uploaded package has a size of 0 bytes, the email offered for flaming is that of the *previously* moderated package. This only happens under certain circumstances, probably if the faulty package has no uploader email of its own (cg)


ID 2007-02-07-03
Status NEW
Description AmFTP doesn't display RECENT files when in ADT mode (cg)


ID 2006-09-01-01
Status NEW
Description admin.php: If you're not in doc/ move_package fails to change the value of the type: field in the readme, because there's an fopen() call which uses a relative path instead of an absolute path (cg)


ID 2006-08-12-01
Status NEW
Description If a readme contains backslashes (in the body, not in one of the header fields - didn't check header fields), these get stripped from *both* the actual readme *and* the database entry. Enclosing the string containing backslashes in double quotes helps the backslashes to actually reach the database entry, but they're still getting stripped from the actual readme. An example would be the windows path in comm/www/firefox_searchplugin.zip (cg)


ID 2006-06-05-01
Status NEW
Description admin.pl will not complain if you try to moderate misc/unix/foo.tar.bz2 while misc/unix/foo.tgz already exists, it will overwrite the existing readme instead. Both packages will be listed in the database afterwards (cg)

Update (20060728):

This is apparently not limited to 'double' extensions ("tar.gzip" etc.). Yesterday admin.pl silently accepted mods/boray/DayUnknown.zip while mods/boray/DayUnknown.lha already existed (cg)