Re: [Gnu-arch-users] Re: auto-deleting directory

[Brian May]

>>>>> "Charles" == Charles Duffy <address@hidden> writes:

    Charles> On Sat, 2004-01-17 at 21:16, Brian May wrote:
    >> It also creates a $root/info/{arch} directory, and considers
    >> the info directory as deleted. It looks like I really need to
    >> be in the root directory of the project before doing an update.

    Charles> If the incorrect {arch} directory were preexisting,
    Charles> (ie. copied or moved into info by mistake), this bug
    Charles> would make sense to me. In most cases, however, `tla
    Charles> tree-root` should correctly resolve the root of the tree,
    Charles> which update and kin (should) respect.

No, the '{arch}' directory was not pre-existing, and I have reproduced
the bug, repeatedly, with tla
address@hidden/tla--devo--1.2--patch-69

For example:

--- cut ---
[503] [scrooge:bam] ~/tree/arch/src/tla/tla >tla tree-root
/home/bam/tree/arch/src/tla
[504] [scrooge:bam] ~/tree/arch/src/tla/tla >tla tree-version
address@hidden/tla--devo--1.2
[505] [scrooge:bam] ~/tree/arch/src/tla/tla >tla whats-missing --summary

WARNING: no rule found for checking signatures from address@hidden

  Consider creating ~/.arch-params/signing/address@hidden
  or ~/.arch-params/signing/=default.check

patch-70
    rbrowse patch regexp feature (jblack)
patch-71
    plug a descriptor leak (lode.leroy)
[506] [scrooge:bam] ~/tree/arch/src/tla/tla >tla update

WARNING: no rule found for checking signatures from address@hidden

  Consider creating ~/.arch-params/signing/address@hidden
  or ~/.arch-params/signing/=default.check

* setting aside local changes temporarily
* linting the source tree
* reverting changes
* updating for new patches in archive
* finding or making tla--devo--1.2--patch-69
* finding or making tla--devo--1.2--patch-71
* computing changeset
A/ {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1
A/ {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden
A/ {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden/patch-log
A  {arch}/tla/tla--devo/tla--devo--1.2/address@hidden/patch-log/patch-70
A  {arch}/tla/tla--devo/tla--devo--1.2/address@hidden/patch-log/patch-71
A  {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden/patch-log/base-0
A  {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden/patch-log/patch-1
M  libarch/cmd-rbrowse.c
M  libarch/my.c
M  ChangeLog
* changeset: ./,,apply-delta-changeset.1074729583.5964.32
* applying changeset
A/  {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1
A/  {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden
A/  {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden/patch-log
A   {arch}/tla/tla--devo/tla--devo--1.2/address@hidden/patch-log/patch-70
A   {arch}/tla/tla--devo/tla--devo--1.2/address@hidden/patch-log/patch-71
A   {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden/patch-log/base-0
A   {arch}/tla/tla--rbrowse/tla--rbrowse--1.2.1/address@hidden/patch-log/patch-1
?M  ChangeLog
?M  libarch/cmd-rbrowse.c
?M  libarch/my.c
* reapplying local changes
* linting the source tree
[507] [scrooge:bam] ~/tree/arch/src/tla/tla >tla tree-root              
/home/bam/tree/arch/src/tla
[508] [scrooge:bam] ~/tree/arch/src/tla/tla >ls
{arch}/  Makefile.in  PLUGIN/  tla.c
--- cut ---

The only thing I don't understand here is why "tla tree-root" isn't pointing
to /home/bam/tree/arch/src/tla/tla???

Anyway, '{arch}' has:

--- cut ---
[510] [scrooge:bam] ~/tree/arch/src/tla/tla >tree '{arch}'
{arch}
`-- tla
    |-- tla--devo
    |   `-- tla--devo--1.2
    |       `-- address@hidden
    |           `-- patch-log
    |               |-- patch-70
    |               `-- patch-71
    `-- tla--rbrowse
        `-- tla--rbrowse--1.2.1
            `-- address@hidden
                `-- patch-log
                    |-- base-0
                    `-- patch-1

9 directories, 4 files
--- cut ---

The "correct" '../{arch}' has all the expected files minus the ones
mentioned above. The listing, as expected is very long, so I won't
include it here.

The last entry in ../Changelog is patch-69

What does '?M' mean? I am guessing it means "I can't find the file to
patch". Is there some reference to indicate what all these fields
mean?

This looks very broken to me.

The project tree had no changes from Lord's version.
-- 
Brian May <address@hidden>