Your message dated Thu, 25 Feb 2016 09:33:01 +0100
with message-id <56cebc3d.1040...@physik.fu-berlin.de>
and subject line Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage 
errors
has caused the Debian Bug report #731806,
regarding debian-installer: FTBFS on sparc: genisoimage errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
731806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-installer
Version: 20131014
Severity: serious
Justification: FTBFS

Hi people,

(-sparc, -cd, genisoimage maintainers x-d-cc'd)

debian-installer 20131014 FTBFS'd on the buildd with:
| […]
| install -m 644 ./tmp/miniiso/boot_screens/notsupported.txt 
./tmp/miniiso/cd_tree/boot
| install -m 644 boot/sparc/silo.conf ./tmp/miniiso/cd_tree/boot
| genisoimage -r -J -o ./tmp/miniiso/mini.iso -G /boot/isofs.b -B ... 
./tmp/miniiso/cd_tree
| genisoimage: Error: './tmp/miniiso/cd_tree/boot/.' and 
'./tmp/miniiso/cd_tree/boot/..' have the same ISO9660 name ''.
| Unable to sort directory ./tmp/miniiso/cd_tree/boot

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=debian-installer&arch=sparc&ver=20131014&stamp=1381835153

I can't tell for sure since it's been a while but I think I was unable
to reproduce it on a porterbox. Probably some FS-dependent fun? Anyone
would have a clue about it?

Thanks for your time.

Mraw,
KiBi.

--- End Message ---
--- Begin Message ---
On 11/12/2015 11:35 PM, John Paul Adrian Glaubitz wrote:
> On 11/12/2015 11:28 PM, Patrick Baggett wrote:
>> If the output is -1, the bug has been fixed. If the output is 0, then
>> the bug is still present. 0 indicates the two strings are equal. Clearly
>> they are not. :)
> 
> Looks like it has been fixed. Anything non-zero means strcmp says the
> strings are not equal, so not just -1:

This is no longer reproducible and debian-installer builds fine on
sparc64. I have created multiple working NETINST images for sparc64.

Thus, closing.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

--- End Message ---

Reply via email to