Difference between revisions of "Bugs"

From AminetWiki
Jump to navigation Jump to search
Line 12: Line 12:
 
|}
 
|}
  
 
{| border="1" cellspacing="0" cellpadding="5"
 
! 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)
 
|}
 
  
  
 
{| border="1" cellspacing="0" cellpadding="5"
 
{| border="1" cellspacing="0" cellpadding="5"
 
! ID
 
! ID
| 2007-02-18-03
+
| 2015-06-19-01
 
|-
 
|-
 
! Status
 
! Status
Line 33: Line 22:
 
|-  
 
|-  
 
! Description
 
! Description
| When replacing an existing file, admin.pl fails to move the old package to priv/deleted:
+
| if admin.pl is trying to replace package path/to/foo.zip with package path/to/foo.lha, it forgets to delete the old database entry so we end up with database entries for foo.zip and foo.lha (cg)
 
 
mv: cannot stat `../util/sys/Argue.lha': No such file or directory
 
(cg)
 
 
|}
 
|}
  
Line 45: Line 31:
 
|-
 
|-
 
! Status
 
! Status
| NEW
+
| WONTFIX
 
|-  
 
|-  
 
! Description
 
! Description
Line 62: Line 48:
 
| 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)
 
| 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 75: Line 60:
 
| AmFTP doesn't display RECENT files when in ADT mode (cg)
 
| AmFTP doesn't display RECENT files when in ADT mode (cg)
 
|}
 
|}
 
  
  
Line 88: Line 72:
 
| 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)
 
| 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)
 
|}
 
|}
 
  
  
Line 100: Line 83:
 
! 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)
|}
 
 
 
 
{| border="1" cellspacing="0" cellpadding="5"
 
! 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)
 
 
<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 (cg)
 
 
|}
 
|}

Revision as of 00:10, 20 June 2015

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 2015-06-19-01
Status NEW
Description if admin.pl is trying to replace package path/to/foo.zip with package path/to/foo.lha, it forgets to delete the old database entry so we end up with database entries for foo.zip and foo.lha (cg)


ID 2007-02-18-01
Status WONTFIX
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)