Found a bug? Please report it, but remember to follow the bug reporting guidelines.
Missing a sane feature? Let us know!
But please do NOT request ports to other systems.
DAMMIT. Wouldn't it be nice for THEM to come here and tell us they do stuff like this, don't you think ?
This behaviour pisses me so much.
I think I'm gonna add a special easter egg for debian only that makes zsnes explode all the ROMdir contents while saying "I'll give you a reason to feel special now BITCH".
Thanks for the info. No idea what the point in the second one is though.
If anyone knows the Debian maintainer do me a favor and beat him up for us for not sending patches back. We shouldn't have to go through every distro's patch list. It's only proper if you fix our code to let us know.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________ Insane Coding
To look on the bright side, we're now using the Debian's way to handle bug reports / feature requests.
I.e.: "We believe that the <bug you reported / feature you requested> is <fixed / done> in the latest version, which is due to be coded in the next years."
THUMBS UP DEBIAN
Last edited by grinvader on Sat Apr 30, 2005 6:27 pm, edited 1 time in total.
Well, it's normal for users to report the bug to debian, since it could be a distribution issue and it would have no place here.
But yeah, usually, when the bug isn't distribution specific the maintainer do report upstream. Why wasn't it done this time, I don't know. The zsnes maintainer looks like he's really slow.
edit: about the second bug, the 1.337-4 changelog write "* Fix build with new NASM"
I guess some version of nasm failed with an end label? I did compile 1.42 with the latest nasm in testing without fixing that though and it worked.
Last edited by bztunk on Sat Apr 30, 2005 6:32 pm, edited 1 time in total.
Hum... that's an automatic email, written when some script sees in a changelog a "closes: #xxxx" line. And when it says "we believe", it's more like "it's been fixed according to the changelog", it's not some wild guess.
I blame Debian as a whole. If you don't pass changes you made to main code back or see to it that your maintainers do, there's something wrong.
It's nice and all that Debian keeps their Distro rock solid, but there's other people out there too, and they would be nowhere if they didn't have 3rd parties writing software.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________ Insane Coding
Nach wrote:Based on the problems, it definitly is some wild guess.
The resolutions? Maybe they are. But don't blame it on the script, he's just doing its job
We're not blaming the script itself (well, I do, because the message is plain stupid), but the fact that a distro maintainer uses an automated script to reply to bug reports / feature requests regardless of development, without forwarding said reports/requests.
Add to that the automated message lulls users in a false sense of safety - it's already fixed (even if it's not) - and you have a major blunder here.
grinvader wrote:Add to that the automated message lulls users in a false sense of safety - it's already fixed (even if it's not) - and you have a major blunder here.
Well, when you see the message appearing, it *is* fixed, if you get the latest debian package.
grinvader wrote:Now, since a bot is impervious to the worst forms of net-torture (including granny pron and gay bukkake), what's the best way to retaliate ?
Off Topic: Maybe if you send enough mails containing granny porn and gay bukkake it will make the server burst into flames.
*Sometimes I edit my posts just to correct mistakes.
grinvader wrote:Maybe so, but the message is a blatant lie. It is NOT fixed in the latest ZSNES version.
It is... in the debian archive.
If you look at the way the confirmation email is send, you can't really send it only when it's fixed in the "real" zsnes, since it's done by reading the debian changelog.