Your message dated Wed, 31 Jan 2018 15:16:32 +0100
with message-id <20180131141632.577zzz6vyul6u...@angband.pl>
and subject line Re: unreproducibile
has caused the Debian Bug report #861515,
regarding src:node-grunt-contrib-copy: FTBFS on armhf i386: test failure: ✖
copy - timestamp_equal
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.)
--
861515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-grunt-contrib-copy
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build on at least armhf and i386.
The test that fails is:
✖ copy - timestamp_equal
Architectures I've tested:
✖ armhf (native)
✖ armhf (arm64)
✔ armhf (qemu-user on amd64)
✔ amd64
✖ i386 (native)
✖ i386 (amd64)
✔ arm64 (native)
✔ arm64 (qemu-user on amd64)
It doesn't seem to be filesystem related: all but one were done on btrfs,
but that i386 machine uses ext4. That machine also uses stretch's official
kernel; the rest are on current mainline.
It's 1.0.0-2, so the previous FTBFS (#860634) is apparently fixed (and the
error is different).
Meow!
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: armhf (armv7l)
Kernel: Linux 4.11.0-rc7-00021-gc7b52626967a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Wed, Jan 31, 2018 at 10:07:39AM +0100, Paolo Greppi wrote:
> this seems now to have gone away by itself,
Aye, works for me too.
>> Architectures I've tested:
>> ✖ armhf (native)
>> ✖ armhf (arm64)
>> ✔ armhf (qemu-user on amd64)
>> ✔ amd64
>> ✖ i386 (native)
>> ✖ i386 (amd64)
>> ✔ arm64 (native)
>> ✔ arm64 (qemu-user on amd64)
Retested on armhf (native), armhf (arm64), i386 (amd64); can't check i386
(native) right now.
> possibly thanks to the upgrade from nodejs 4.x to 8.x:
> I don't see any error on the buildds, and it works without the patch on my
> x86 VM here.
>
> So I have reset the repo to the debian/1.0.0-2 tag, and moved the patch
> to a separate branch (wip/paolog/skip_test) in case we need it later.
>
> @Adam, if you have access to an armhf test machine, you could try yourself on
> that too.
Tried multiple times, succeeded evert time.
> I'll wait a bit more before I close this one and the upstream bug.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back. What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda? Łambinowice? Most ex-German KLs? If those were "soviet
⠈⠳⣄⠀⠀⠀⠀ puppets", Bereza Kartuska? Sikorski's camps in UK (thanks Brits!)?
--- End Message ---
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
