Bug 914970

Summary:	Please update larch
Product:	[Fedora] Fedora	Reporter:	Neal Becker <ndbecker2>
Component:	python-larch	Assignee:	Michel Lind <michel>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	michel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-06 22:55:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Neal Becker 2013-02-23 19:33:03 UTC

Description of problem:
Lars Wirzenius
Feb 16 (7 days ago)

to me, obnam 
On Fri, Feb 15, 2013 at 07:18:44AM -0500, Neal Becker wrote:
> I started running fsck, but killed it (so I could run it with --fsck-fix).
>
> Now I have a bigger problem.  Maybe obnam didn't like being killed.
>
> obnam --verb fsck --fsck-fix
> ERROR: Larch B-tree is in read-only mode, no changes allowed

I think you need to upgrade your larch package.

Latest version is 1.20121216
Current is python-larch-1.20121006-1.fc18.noarch

http://liw.fi/larch/NEWS/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Michel Lind 2013-02-25 08:38:02 UTC

Apologies, missed the update notification since due to the Debian freeze, releases are now back on the author's site (Debian is still on Obnam 1.1, even)

Comment 2 Fedora Update System 2013-02-26 03:39:17 UTC

obnam-1.3-1.fc18,seivot-1.18-1.fc18,python-larch-1.20121216-1.fc18,genbackupdata-1.7-1.fc18,summain-0.17-1.fc18,cmdtest-0.5-1.fc18,python-ttystatus-0.21-1.fc18,python-cliapp-1.20121216-1.fc18,python-tracing-0.7-2.fc18,python-coverage-test-runner-1.9-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/obnam-1.3-1.fc18,seivot-1.18-1.fc18,python-larch-1.20121216-1.fc18,genbackupdata-1.7-1.fc18,summain-0.17-1.fc18,cmdtest-0.5-1.fc18,python-ttystatus-0.21-1.fc18,python-cliapp-1.20121216-1.fc18,python-tracing-0.7-2.fc18,python-coverage-test-runner-1.9-1.fc18

Comment 3 Fedora Update System 2013-02-26 07:58:24 UTC

seivot-1.18-1.fc17,obnam-1.3-1.fc17,python-larch-1.20121216-1.fc17,genbackupdata-1.7-1.fc17,summain-0.17-1.fc17,cmdtest-0.5-1.fc17,python-ttystatus-0.21-1.fc17,python-cliapp-1.20121216-1.fc17,python-tracing-0.7-2.fc17,python-coverage-test-runner-1.9-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/seivot-1.18-1.fc17,obnam-1.3-1.fc17,python-larch-1.20121216-1.fc17,genbackupdata-1.7-1.fc17,summain-0.17-1.fc17,cmdtest-0.5-1.fc17,python-ttystatus-0.21-1.fc17,python-cliapp-1.20121216-1.fc17,python-tracing-0.7-2.fc17,python-coverage-test-runner-1.9-1.fc17

Comment 4 Fedora Update System 2013-02-27 02:30:38 UTC

Package seivot-1.18-1.fc17, obnam-1.3-1.fc17, python-larch-1.20121216-1.fc17, genbackupdata-1.7-1.fc17, summain-0.17-1.fc17, cmdtest-0.5-1.fc17, python-ttystatus-0.21-1.fc17, python-cliapp-1.20121216-1.fc17, python-tracing-0.7-2.fc17, python-coverage-test-runner-1.9-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing seivot-1.18-1.fc17 obnam-1.3-1.fc17 python-larch-1.20121216-1.fc17 genbackupdata-1.7-1.fc17 summain-0.17-1.fc17 cmdtest-0.5-1.fc17 python-ttystatus-0.21-1.fc17 python-cliapp-1.20121216-1.fc17 python-tracing-0.7-2.fc17 python-coverage-test-runner-1.9-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3089/seivot-1.18-1.fc17,obnam-1.3-1.fc17,python-larch-1.20121216-1.fc17,genbackupdata-1.7-1.fc17,summain-0.17-1.fc17,cmdtest-0.5-1.fc17,python-ttystatus-0.21-1.fc17,python-cliapp-1.20121216-1.fc17,python-tracing-0.7-2.fc17,python-coverage-test-runner-1.9-1.fc17
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-03-04 07:06:12 UTC

python-coverage-test-runner-1.9-1.el6,python-tracing-0.7-2.el6,python-cliapp-1.20121216-1.el6,python-ttystatus-0.21-1.el6,cmdtest-0.5-1.el6,summain-0.17-1.el6,genbackupdata-1.7-1.el6,python-larch-1.20121216-1.el6,seivot-1.18-1.el6,obnam-1.3-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/python-coverage-test-runner-1.9-1.el6,python-tracing-0.7-2.el6,python-cliapp-1.20121216-1.el6,python-ttystatus-0.21-1.el6,cmdtest-0.5-1.el6,summain-0.17-1.el6,genbackupdata-1.7-1.el6,python-larch-1.20121216-1.el6,seivot-1.18-1.el6,obnam-1.3-1.el6

Comment 6 Fedora Update System 2013-03-06 22:55:33 UTC

seivot-1.18-1.fc17, obnam-1.3-1.fc17, python-larch-1.20121216-1.fc17, genbackupdata-1.7-1.fc17, summain-0.17-1.fc17, cmdtest-0.5-1.fc17, python-ttystatus-0.21-1.fc17, python-cliapp-1.20121216-1.fc17, python-tracing-0.7-2.fc17, python-coverage-test-runner-1.9-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2013-03-06 22:58:33 UTC

obnam-1.3-1.fc18, seivot-1.18-1.fc18, python-larch-1.20121216-1.fc18, genbackupdata-1.7-1.fc18, summain-0.17-1.fc18, cmdtest-0.5-1.fc18, python-ttystatus-0.21-1.fc18, python-cliapp-1.20121216-1.fc18, python-tracing-0.7-2.fc18, python-coverage-test-runner-1.9-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-03-24 18:01:41 UTC

python-coverage-test-runner-1.9-1.el6, python-tracing-0.7-2.el6, python-cliapp-1.20121216-1.el6, python-ttystatus-0.21-1.el6, cmdtest-0.5-1.el6, summain-0.17-1.el6, genbackupdata-1.7-1.el6, python-larch-1.20121216-1.el6, seivot-1.18-1.el6, obnam-1.3-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.