Re: 1.3.2 bzr 'fixes' - still can't deal with exec bit changes

[Steve Franks <bahamasfranks gmail com>]

Hi,

Quite simply, if the exec bit changes, bzr flags this with a '*'
(using an important character like that as status was probably a
whopper of a mistake in the first place, imho).  Meld then picks that
up as part of the filename, and subsequent bzr actions on the file
fail, because the asterisk is not actually part of the filename, but
status.

If I use bzr from the command line, and (i.e.) commit the file without
the * in the name, it works fine.  The quoted stderr in my origonal
email is from meld's status pane when I try to commit the same file
within meld.

Sorry for the confusion,
Steve


On Sat, Jul 10, 2010 at 3:19 PM, Kai <kai willadsen gmail com> wrote:
> On 9 July 2010 01:15, Steve Franks <bahamasfranks gmail com> wrote:
>> I'm sure there's some file somewhere I have to edit, and it's not
>> really a bug, but it's a major annoyance: meld always grabs the '*',
>> and bzr complains when it's used as part of the filename...meld's
>> pretty useless to me for bzr at the moment, since my ugly mix of winXP
>> boxes (virtualbox+cad), and FreeBSD machines (everything else) is
>> pretty much guaranteed to muck-up the exec bit when I edit a file.
>>
>> Best,
>> Steve
>>
>> bzr --no-aliases --no-plugins commit -m "chmod 775" uC/LPC13xx_UM.pdf*
>> (in /home/steve/projects/datasheets)
>> Committing to: bzr+ssh://192.168.2.69/raincloud/bzr/datasheets/trunk/
>> aborting commit write group: PathsNotVersionedError(Path(s) are not
>> versioned: "uC/LPC13xx_UM.pdf*")
>> bzr: ERROR: Path(s) are not versioned: "uC/LPC13xx_UM.pdf*"
>> Exit code: 3
>
> Sorry, but I've read this email twice and I can't figure out what the
> problem is, or where Meld is involved. Could you give some more
> details on what's actually going on?
>
> cheers,
> Kai
>