bzr push fails with "uncommitted changes" error, but bzr status shows nothing

Bug #1014571 reported by Jelmer Vernooij on 2012-06-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Unassigned
bzr (Debian)
Confirmed
Unknown
bzr (Ubuntu)
Medium
Unassigned

Bug Description

Imported from Debian bug http://bugs.debian.org/672977:

Package: bzr
Version: 2.1.2-1
Severity: normal

I just had a problem with bzr 2.1.2 where a push failed with this error:

bzr: ERROR: Working tree "/home/ajapted/aww/" has uncommitted changes (See bzr status). Use --no-strict to force the push.

However using bzr status showed no uncommitted changes at all.
I checked that .bzrignore was not masking any files.

I don't know how to reproduce the problem, the only thing that I did differently recently
was to use "bzr shelve" on a file. I tried unshelving that file and reverting the changes but
the error still occurred.

A workaround was to use "bzr commit --unchanged ." which committed an apparently
empty commit, but it obviously did something as since the push worked after that.

Cheers,
--
Andrew Apted

-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bzr depends on:
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii python 2.6.6-3+squeeze4 interactive high-level object-orie
ii python-central 0.6.16+nmu1 register and build utility for Pyt
ii python-configobj 4.7.2+ds-1 simple but powerful config file re
ii python-elementtree 1.2.6-14 Light-weight toolkit for XML proce
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages bzr recommends:
pn bzrtools <none> (no description available)
ii ca-certificates 20090814 Common CA certificates
ii python-paramiko 1.7.4-0.1 Make ssh v2 connections with pytho

Versions of packages bzr suggests:
pn bzr-doc <none> (no description available)
pn bzr-gtk <none> (no description available)
pn bzr-svn <none> (no description available)
pn python-kerberos <none> (no description available)
pn python-pycurl <none> (no description available)
ii xdg-utils 1.0.2-6.1 desktop integration utilities from

-- no debconf information

Jelmer Vernooij (jelmer) on 2012-06-18
Changed in bzr (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Changed in bzr:
status: New → Triaged
importance: Undecided → Medium
Changed in bzr (Debian):
importance: Undecided → Unknown

Jelmer Vernooij пишет:
> A workaround was to use "bzr commit --unchanged ." which committed an apparently
> empty commit, but it obviously did something as since the push worked after that.

That looks like the situation with TREE_ROOT changes: the very first
commit after `bzr init` should commit TREE_ROOT, but it does not show up
in status output.

Changed in bzr (Debian):
status: New → Confirmed
Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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