Commit failed with attribute error

Bug #187330 reported by Jeroen Hellingman
10
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

Running bzr status, then bzr commit, I get the following output (copied from my command window):

L:\eLibrary\Books\D\DeAarde\1917\1917-01-Molukken>bzr status
modified:
  D/DeAarde/1917/1917-01-Molukken/1917-01-Molukken-0.0.tei
unknown:
  B/Barrows/A History of the Philippines/HistoryPhilippines-p5.xml
  B/Barrows/A History of the Philippines/HistoryPhilippines-words.html
  B/Barrows/A History of the Philippines/HistoryPhilippines.html
  B/Barrows/A History of the Philippines/HistoryPhilippines.txt
  B/Barrows/A History of the Philippines/HistoryPhilippines.xml
  B/Barrows/A History of the Philippines/images/p024.jpg
  B/Blink/Heerlijk Vaderland 2/HeerlijkVaderland-p5.xml
  B/Blink/Heerlijk Vaderland 2/HeerlijkVaderland-words.html
  B/Blink/Heerlijk Vaderland 2/HeerlijkVaderland.html
  B/Blink/Heerlijk Vaderland 2/HeerlijkVaderland.txt
  B/Blink/Heerlijk Vaderland 2/HeerlijkVaderland.xml
  B/Blink/Heerlijk Vaderland 2/imageinfo.xml
  B/Blink/Heerlijk Vaderland 2/images/p2-032h.jpg
  D/DeAarde/1917/1917-Inhoud-0.0.tei
  D/DeAarde/1917/1917-01-Molukken/1917-01-Molukken-0.2.tei
  D/DeAarde/1917/1917-01-Molukken/1917-01-Molukken-0.3.tei
  D/DeAarde/1917/1917-01-Molukken/1917-01-Molukken-0.4x.tei

L:\eLibrary\Books\D\DeAarde\1917\1917-01-Molukken>bzr commit
Committing to: L:/eLibrary/Books/
modified D/DeAarde/1917/1917-01-Molukken/1917-01-Molukken-0.0.tei
bzr: ERROR: exceptions.AttributeError: 'NoneType' object has no attribute 'abort
'

Traceback (most recent call last):
  File "bzrlib\commands.pyc", line 806, in run_bzr_catch_errors
  File "bzrlib\commands.pyc", line 762, in run_bzr
  File "bzrlib\commands.pyc", line 492, in run_argv_aliases
  File "bzrlib\builtins.pyc", line 2328, in run
  File "bzrlib\decorators.pyc", line 167, in write_locked
  File "bzrlib\workingtree_4.pyc", line 1134, in unlock
  File "bzrlib\branch.pyc", line 1366, in unlock
  File "bzrlib\repofmt\pack_repo.pyc", line 2005, in unlock
  File "bzrlib\repository.pyc", line 482, in abort_write_group
  File "bzrlib\repofmt\pack_repo.pyc", line 1847, in _abort_write_group
  File "bzrlib\repofmt\pack_repo.pyc", line 1651, in _abort_write_group
AttributeError: 'NoneType' object has no attribute 'abort'

bzr 1.1.0 on python 2.5.1.final.0 (win32)
arguments: ['bzr', 'commit']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
  launchpad F:\Programs\Bazaar\lib\library.zip\bzrlib\plugins\launchp
ad [unknown]
  multiparent F:\Programs\Bazaar\lib\library.zip\bzrlib\plugins\multipa
rent.pyc [unknown]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.

L:\eLibrary\Books\D\DeAarde\1917\1917-01-Molukken>

Reporting bug as requested...

Tags: commit
Revision history for this message
Jeroen Hellingman (jhellingman) wrote :

The root cause agains appears to be lack of disk space. Cleaning up a little, and trying again works. Needs about the size of .bzr directory (> 830 MB) to succeed on 100th commit.

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 187330] Re: Commit failed with attribute error

Am Mittwoch, den 30.01.2008, 15:57 +0000 schrieb Jeroen Hellingman:
> The root cause agains appears to be lack of disk space. Cleaning up a
> little, and trying again works. Needs about the size of .bzr directory
> (> 830 MB) to succeed on 100th commit.
The attribute error appears to be caused by the fact that an exception
was raised during the commit but while bzr was trying to clean up
(aborting the transacation) because of that exception caused another.

--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Revision history for this message
James Westby (james-w) wrote :

Hi,

This appears to be a duplicate of bug #184898.

Jeroen, do you have bzr-gtk installed?

Alexander, is there any chance that what was packaged
as 1.1 for windows was in fact a couple of revisions older
than the 1.1 branch? The fix for this was the penultimate
commit before 1.1 was branched, so it should be in
1.1.

Thanks,

James

Revision history for this message
Jeroen Hellingman (jhellingman) wrote :

Nope, no brz-gtk, afaik. Just used the windows installer for 1.1 (upgrade from 1.0)

Revision history for this message
Alexander Belchenko (bialix) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Westby пишет:
| This appears to be a duplicate of bug #184898.
|
| Jeroen, do you have bzr-gtk installed?
|
| Alexander, is there any chance that what was packaged
| as 1.1 for windows was in fact a couple of revisions older
| than the 1.1 branch? The fix for this was the penultimate
| commit before 1.1 was branched, so it should be in
| 1.1.

No, I'm always build from the official source tarball.
Check it first, please.
Or say me where to look and what to looking for.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHoPc3zYr338mxwCURApoHAJ9Var12cmPfQx4+8nGrXTqvQBqk2gCgiztj
Sj1bqIcVpVN/9tjgcZH7RjI=
=u4bh
-----END PGP SIGNATURE-----

Revision history for this message
James Westby (james-w) wrote :

On Wed, 2008-01-30 at 22:15 +0000, Alexander Belchenko wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> James Westby пишет:
> | This appears to be a duplicate of bug #184898.
> |
> | Jeroen, do you have bzr-gtk installed?
> |
> | Alexander, is there any chance that what was packaged
> | as 1.1 for windows was in fact a couple of revisions older
> | than the 1.1 branch? The fix for this was the penultimate
> | commit before 1.1 was branched, so it should be in
> | 1.1.
>
> No, I'm always build from the official source tarball.
> Check it first, please.
> Or say me where to look and what to looking for.

Hey, the tarball at

https://launchpad.net/bzr/1.1/1.1/+download/bzr-1.1.tar.gz

doesn't include the fix. However

http://codebrowse.launchpad.net/~mbp/bzr/bzr.1.1/annotate/pqm%
40pqm.ubuntu.com-20080115030052-x4n7l0pf5g5icfp4?file_id=pack_repo.py-20070813041115-gjv5ma7ktfqwsjgn-1

says that it should.

Martin, was it you that released 1.1. Can you explain what happened
here?

Alexander, I should never have doubted you, my apologies.

Thanks,

James

James Westby (james-w)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Alexander Belchenko (bialix) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Westby пишет:
| On Wed, 2008-01-30 at 22:15 +0000, Alexander Belchenko wrote:
|> James Westby пишет:
|> | This appears to be a duplicate of bug #184898.
|> |
|> | Jeroen, do you have bzr-gtk installed?
|> |
|> | Alexander, is there any chance that what was packaged
|> | as 1.1 for windows was in fact a couple of revisions older
|> | than the 1.1 branch? The fix for this was the penultimate
|> | commit before 1.1 was branched, so it should be in
|> | 1.1.
|>
|> No, I'm always build from the official source tarball.
|> Check it first, please.
|> Or say me where to look and what to looking for.
|
| Hey, the tarball at
|
| https://launchpad.net/bzr/1.1/1.1/+download/bzr-1.1.tar.gz
|
| doesn't include the fix. However
|
| http://codebrowse.launchpad.net/~mbp/bzr/bzr.1.1/annotate/pqm%
|
40pqm.ubuntu.com-20080115030052-x4n7l0pf5g5icfp4?file_id=pack_repo.py-20070813041115-gjv5ma7ktfqwsjgn-1
|
| says that it should.
|
| Martin, was it you that released 1.1. Can you explain what happened
| here?
|
| Alexander, I should never have doubted you, my apologies.

No, it's OK. A bit of doubts does not hurt.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHoQcwzYr338mxwCURAtjUAJ92Vl8Va867XVHPjUiNxetgbToeFwCgi3lk
upmDp7hq871aMs0C+749EIE=
=aS5u
-----END PGP SIGNATURE-----

Revision history for this message
mmp (mmpatels) wrote :

Hi all

im new to linux so ur help vl b highly appreciated

when i try to run command

gcc -Os -g -I/usr/include/bogl -fPIC -c usplash-mine.c -o usplash-mine.o

i get a error

usplash-mine.c:1: error: expected '=', ',', ';', 'asm' or '___attribute__' before 'opening'

can some 1 help me to solve this problem

thx
mmp

Revision history for this message
James Westby (james-w) wrote :

mmp,

you have sent your message to a bug report on bzr. This is
not the correct place for your support question.

I would suggest you go to

https://answers.launchpad.net/usplash/+addquestion

and ask your question there.

Thanks,

James

Revision history for this message
mmp (mmpatels) wrote :

thx james

i vl do that

regards
mmp

Revision history for this message
Robert Collins (lifeless) wrote :

Is this fixed? I believe James Westby submitted a patch (based on discussion in the duplicate)

Jelmer Vernooij (jelmer)
tags: added: commit
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.