Your message dated Thu, 08 Aug 2013 22:48:36 +0000
with message-id <[email protected]>
and subject line Bug#675820: fixed in obnam 1.5-1
has caused the Debian Bug report #675820,
regarding ERROR: Larch B-tree is in read-only mode, no changes allowed
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 [email protected]
immediately.)
--
675820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675820
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: obnam
Version: 1.0-1
Severity: normal
Hello,
obnam is not able to fsck-fix my backup repo. The error reported is:
"ERROR: Larch B-tree is in read-only mode, no changes allowed"
The fsck-errors were artificially created by aborting several times a backup.
This may be the normal behaviour, but it does not seem clear to me why this
occurs.
The fsck command reports unused chunks, I rerun fsck in fix mode
immediately after and get this error:
$ obnam --lock-timeout=3 -r /home/damien/tmp/disk fsck
chunk 17152530288956314516 not used by anyone
chunk 17152530288956314520 not used by anyone
(etc...)
$ obnam --lock-timeout=3 -r /home/damien/tmp/disk fsck --fsck-fix
ERROR: Larch B-tree is in read-only mode, no changes allowed
regards,
Damien
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (450, 'stable-updates'), (450, 'stable'), (300,
'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages obnam depends on:
ii libc6 2.13-32
ii python 2.7.2-10
ii python-cliapp 0.29-1
ii python-larch 0.31-1
ii python-paramiko 1.7.7.1-2
ii python-tracing 0.6-2
ii python-ttystatus 0.18-1
ii python2.6 2.6.7-4
ii python2.7 2.7.3~rc2-2.1
obnam recommends no packages.
obnam suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: obnam
Source-Version: 1.5-1
We believe that the bug you reported is fixed in the latest version of
obnam, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lars Wirzenius <[email protected]> (supplier of updated obnam package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 08 Aug 2013 22:26:17 +0100
Source: obnam
Binary: obnam
Architecture: amd64 i386 source
Version: 1.5-1
Distribution: unstable
Urgency: low
Maintainer: Lars Wirzenius <[email protected]>
Changed-By: Lars Wirzenius <[email protected]>
Closes: 675820 676490 686191 700097 701209 719014
Description:
obnam - online and disk-based backup application
Changes:
obnam (1.5-1) unstable; urgency=low
.
* New upstream release. This fixes the following bugs in Debian:
- Larch B-tree is in read-only mode, no changes allowed (Closes: #675820)
- obnam should not pass excessive options to ssh (Closes: #700097)
- DEBUG OSError ((95, 'Operation not supported', '<filename>'), )
sshfs problem? (Closes: #701209)
- new upstream version (Closes: #719014)
- hidden exclude option (Closes: #686191)
- manpage nit: says "obnam backup [FILE]" where it expects a directory
(Closes: #676490)
* Update cmdtest build dependency to get yarn.
* Update larch dependencies, to get important bug fixes.
Checksums-Sha1:
3f498abca4d93f40b9842e281648d51abf566cbd 100444 obnam_1.5-1_amd64.deb
9ce0ebc6f850e5f243eda4aaa7a30344edccf5b5 100526 obnam_1.5-1_i386.deb
8487d8adbb02c6f64423c9ac7d09920e5a370910 1565 obnam_1.5-1.dsc
12e2e61c654e772d03b36094ba5912c4be767977 172563 obnam_1.5.orig.tar.gz
402a058b0e1290cc72b8354bbe8c70ff62f6ceb3 5069 obnam_1.5-1.diff.gz
Checksums-Sha256:
223204ed83106d2fe276ddde036087197f240c62ae581a83a6c59e510f6f76fd 100444
obnam_1.5-1_amd64.deb
dfb06ecbdfc270859c69861be96e9db31fe3961694d2141c1cd0b764637fd36a 100526
obnam_1.5-1_i386.deb
3bbb2ba29fd44199ea9ded5fb9cc3de184a515bd2b46b132a8385b72dbfb1a33 1565
obnam_1.5-1.dsc
7808514b942a75ef0cee46bbd6d14115c92f3ac40ef3e73a361c7df017faf8e9 172563
obnam_1.5.orig.tar.gz
c2a3e267d186e821683899641cb8f90a6517b0097de86a6f2c9dcc3b22aad5a6 5069
obnam_1.5-1.diff.gz
Files:
2f143e923e1332460d741d5cb82653e8 100444 python optional obnam_1.5-1_amd64.deb
49fa7d5d051691dda3981612b6c8eed4 100526 python optional obnam_1.5-1_i386.deb
c9257c4767f91b49159bd3c93d7f29f3 1565 python optional obnam_1.5-1.dsc
f12245eb7c896d6fe31dcae5692fb9f2 172563 python optional obnam_1.5.orig.tar.gz
27aa5bb51a0263d0b1cc8ba5530f26af 5069 python optional obnam_1.5-1.diff.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBCAAGBQJSBBxOAAoJEIahkFub41rmC6oH/1qAciewzUQg+43zr/uuEO2p
hsJt8Rw1N6V6mP6+TFVoAEKs6rNK+w4aZtb+7K9uXbdLUwWbXso7hMvam3lblJd2
wy3gCVI+izitFn67cSnLqJY+pf48N2Ny++r2LXmBxMm0BdAeiajRzCy40yrZxnUa
UKeYtEaYrU+h6DRiEYkR1uauB7u45ewqxDvAKtaKvxDNKdswg+ygUZcuKflrf6XS
2RwpK9KHZaJ7aemJ/tIG4QzT1lv313Mb/Tb2gf8leBG954jkXU/IqBBDC6ySRTWd
piVrKz+ctnI88cWcwK7zpbjz3ern5mCtqyOF5mzkbW0ZG8zpyvovHFaXW9mJQHg=
=34Zq
-----END PGP SIGNATURE-----
--- End Message ---
