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…>
[1] <http://www.cpantesters.org/distro/O/OpenGuides.html#OpenGuides-0.76>
Hi,
I've just released OpenGuides 0.72 to CPAN.
The 3 major additions in this release are:
Allow a custom template, custom_auto_map_link.tt to populate map links in
node metadata.
Split out the node location search section of the node template.
Add an optional custom template to node_location_search.tt
A bug was fixed:
The date in json output is now correct.
Other changes were made but they dont actually effect the code.
Changes at https://metacpan.org/source/BOB/OpenGuides-0.72/Changes#L7
Full list of commits since last release
https://github.com/OpenGuides/OpenGuides/compare/rel0_71...rel0_72
--
bob walker
everything should be purple and bendy
http://randomness.org.uk
[moving to openguides-dev]
On Sun, Apr 21, 2013 at 08:06:31AM +0100, Kake wrote:
> On Sat 20 Apr 2013, Dominic Hargreaves <dom(a)earth.li> wrote:
> > https://github.com/OpenGuides/OpenGuides/commit/111c9339858fad183cabde46951…
>
> Nice! Would it be better to do it the other way around? As it
> stands, to use this in RGL/CGC I'd have to go through and remove all
> the map links from the data. Could we INCLUDE custom_auto_map_link.tt
> by default, and fall back to map_link only if there isn't one? Also,
> it might be better to call the template custom_auto_map_links.tt, since
> I at least will want to put in more than one map link.
Okay. The logic is right for Oxford, because we assume that if a map
link is provided, it's more interesting than a generic one. But the
Oxford custom template can easily replicate that functionality.
> Also, I'd like to see some tests for this new feature, as with all new
> features.
Okay.
This is back on my list.
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
I've moved across the trac tickets that i think are still relevant to
github issues. Quite a lot of them link back to the trac ticket if there
is a lengthy discussion there.
Ive left quite a few behind because i dont think they matter anymore.
https://github.com/OpenGuides/OpenGuides/issues?state=open
--
bob walker
everything should be purple and bendy
http://randomness.org.uk
Hello,
Given todays release of 0.71 I decided this would be an ideal time to
migrate OpenGuides to github.
So I did.
https://github.com/OpenGuides/OpenGuides
We have an OpenGuides organisation which only has an OpenGuides Repo.
Kake, Dom and Myself are currently set as owners of the organization.
Im intending to copy across important open issues from trac manually since
all the ways to do so automatically look painful.
--
bob walker
everything should be purple and bendy
http://randomness.org.uk