Control: tags -1 +help
On Sun, Apr 27, 2014 at 02:48:27PM +0200, David Suárez wrote:
During a rebuild of all packages in sid, your package failed to build on
amd64.
The extract of the build log[0] on the bug report isn't particularly helpful.
All the test failures (there are more than just the ones listed) are
of the form:
Unhandled error: [DBD::SQLite::st execute failed: attempt to write a readonly
database at /usr/share/perl5/Wiki/Toolkit/Store/Database.pm line 567.
The first of this appears at t/109_autocreate.t:
$ perl -Ilib t/109_autocreate.t
1..13
Creating table internal_links... done
Creating table content... done
Creating table metadata... done
Creating table schema_info... done
Creating table node... done
Unhandled error: [DBD::SQLite::st execute failed: attempt to write a readonly
database at /usr/share/perl5/Wiki/Toolkit/Store/Database.pm line 567.
] at /usr/share/perl5/Wiki/Toolkit.pm line 849.
# Looks like your test exited with 2 before it could output anything.
Next, t/802_stylesheet.t:
$ perl -Ilib t/802_stylesheet.t
1..3
Creating table metadata... done
Creating table content... done
Creating table schema_info... done
Creating table node... done
Creating table internal_links... done
Unhandled error: [DBD::SQLite::st execute failed: attempt to write a readonly
database at /usr/share/perl5/Wiki/Toolkit/Store/Database.pm line 567.
] at /usr/share/perl5/Wiki/Toolkit.pm line 849.
# Looks like your test exited with 2 before it could output anything.
Thirdly, 809_recent_changes_ip_addr.t, just to demonstrate it doesn't
always happen immediately:
$ perl -Ilib t/809_recent_changes_ip_addr.t
1..10
Creating table internal_links... done
Creating table metadata... done
Creating table schema_info... done
Creating table node... done
Creating table content... done
ok 1 - prefs available as TT var on recent changes
ok 2 - ...even when there's a recent changes tracking cookie set
Unhandled error: [DBD::SQLite::st execute failed: attempt to write a readonly
database at /usr/share/perl5/Wiki/Toolkit/Store/Database.pm line 567.
] at /usr/share/perl5/Wiki/Toolkit.pm line 849.
# Looks like you planned 10 tests but ran 2.
# Looks like your test exited with 2 just after 2.
Running strace on the first of these gives:
access("/home/dom/working/deb-git/openguides/t/node.db-journal", F_OK) = -1
ENOENT (No such file or directory)
fstat64(3, {st_mode=S_IFREG|0644, st_size=12288, ...}) = 0
_llseek(3, 24, [24], SEEK_SET) = 0
read(3, "\0\0\0\7\0\0\0\f\0\0\0\0\0\0\0\0", 16) = 16
fstat64(3, {st_mode=S_IFREG|0644, st_size=12288, ...}) = 0
access("/home/dom/working/deb-git/openguides/t/node.db-wal", F_OK) = -1 ENOENT
(No such file or directory)
fstat64(3, {st_mode=S_IFREG|0644, st_size=12288, ...}) = 0
time(NULL) = 1409869756
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
time(NULL) = 1409869756
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
fcntl64(3, F_SETLK64, {type=F_WRLCK, whence=SEEK_SET, start=1073741825, len=1},
0xbfbf4b04) = 0
_llseek(3, 7168, [7168], SEEK_SET) = 0
read(3, "\r\0\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
_llseek(3, 5120, [5120], SEEK_SET) = 0
read(3, "\r\0\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
stat64("/home/dom/working/deb-git/openguides/t/node.db", {st_mode=S_IFREG|0644,
st_size=12288, ...}) = 0
fcntl64(3, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741826,
len=510}, 0xbfbf4a04) = 0
fcntl64(3, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=1073741824, len=2},
0xbfbf4a04) = 0
fcntl64(3, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0},
0xbfbf4a54) = 0
write(2, "Unhandled error: [DBD::SQLite::s"..., 196Unhandled error:
[DBD::SQLite::st execute failed: attempt to write a readonly database at
/usr/share/perl5/Wiki/Toolkit/Store/Database.pm line 567.
] at /usr/share/perl5/Wiki/Toolkit.pm line 849.
) = 196
which doesn't immediately explain why we got the error. It does seem
to be peculiar to the Debian environment (no failures at [1] except
unrelated ones on Windows).
I should probably make explicit that I don't think these are genuine
ACL problems. The file and its containing directory remain writeable by the
user at all times, as far as I can see. It doesn't seem to be architecture
specific (at least it fails with i386 and amd64 equally).
I'm at a bit of a loss how to proceed, here. Does anyone have any ideas?
Dominic.
[0]
<http://aws-logs.debian.net/ftbfs-logs/2014/04/26/openguides_0.76-1_unstable.log>
[1] <http://www.cpantesters.org/distro/O/OpenGuides.html#OpenGuides-0.76>
