Bugs
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 | 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 | the combination glib.i386-aros.tar.gz and glib.i386-aros.tar.readme got accepted by admin.pl, moved to the Aminet tree but *not* added to the database. Not sure if I got an error message (didn't notice anything, can't verify because scrollback buffer was fucked up by invoking pico).
Renaming the files to glib.i386-aros.tgz and glib.i386-aros.readme and moderating them again solved the problem. (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.
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. |
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 |
ID | 2006-06-17-02 |
---|---|
Status | NEW |
Description | Flaming an uploader results in an error message. This message is apparently not created by any of the scripts (which continue as if nothing happened), but by some daemon or sth. like that. The message is:
send-mail: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol send-mail: warning: inet_protocols: configuring for IPv4 support only postdrop: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol postdrop: warning: inet_protocols: configuring for IPv4 support only |