> FWIW, the effects described in this bug report are 100% reproducible > on any version, as long as the loader (lilo, grub, whatever) ends up putting > the bootsect+setup in any location below 9000:0000.
... and the problem actually predates the fork of memtest86 and memtest86+; IOW, the same crap is present in memtest86 as well - it triggers on the same boxen, the same patch applies[*] and gets the damn thing working. How does one normally deal with that kind of shared bugs? Two packages with identical bugs; same setups trigger those, same fix, code actually predates the fork that produced one of those packages from another. Opening a matching bug report in memtest86 and refering to this one in it? At least memtest86 and memtest86+ have the same maintainer... [*] except that there setup.S has CRLF for EOL, so applying it requires either converting the sucker into normal text file first, or applying via sed -e 's/$/\r/' | patch -p1 -E --binary -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
