9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adrian Tritschler <ajft@ajft.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silly replica question (repeated m msgs won't go away)
Date: Tue, 10 Feb 2004 14:46:23 +1100	[thread overview]
Message-ID: <4028540F.6040500@ajft.org> (raw)
In-Reply-To: <a69cf15a26eeaefffa99dcf25697f0cb@plan9.ucalgary.ca>

mirtchov@cpsc.ucalgary.ca wrote (sometime last December):

>>Today I updated my fake-worm fs from sources (first time since summer).
>>
>>every time I replica/pull, I get lots of msgs like:
>>
>>m sys/lib/antiword/8859-1.txt 644 sys sys 1069793886
>>m sys/lib/antiword/8859-10.txt 644 sys sys 1069793886
>>m sys/lib/antiword/8859-13.txt 644 sys sys 1069793886
>>m sys/lib/antiword/8859-14.txt 644 sys sys 1069793886
>>m sys/lib/antiword/8859-15.txt 644 sys sys 1069793886
>>
>>and whenever I now run replica/pull again, I get the same...
>>
>>adding -s flag to replica/pull did not help
>>(fair enough, it serves a different purpose)
>>
>>What am I doing wrong, or overlooking?
>>I _think_ have the fake-worm fs permissions open enough, or???
>>
>>Thanks,
>>Axel.

> there were broken /sys/lib/antiword and /sys/src/cmd/aux/antiword with
> bad permissions on sources.  looks like you're stuck with a bad copy.
> try chmod-ing your own version to something world-readable.
> 
> or deleting them altogether and trying the -s flag to pull..
> 
> andrey

I'm suffering the same problem, every pull that I do from sources is 
producing two lines for each file in sys/lib/antiword and 
sys/src/cmd/aux/antiword.  I've tried removing all the files and redoing 
the pull as "pull -s sys/src/cmd/aux", but that then failed because 
/n/kfs/sys/src/cmd/aux/antiword didn't exist.  I created the directory, 
then the next time I did a pull I got
  :
a sys/src/cmd/aux/antiword/xml.c 644 sys sys 1069795877
  :
m sys/src/cmd/aux/antiword/xml.c 664 sys sys 1069795877

Then on every subsequent pull I get the two:
  :
m sys/src/cmd/aux/antiword/xml.c 644 sys sys 1069795877
  :
m sys/src/cmd/aux/antiword/xml.c 644 sys sys 1069795877

Is there any way to convince replica that I really do have all the files 
on my machine, and for it to stop flipping the permissions back and 
forth between 644 and 664?

RTFM accepted, but can some kind sole point me to the right part of the FM?

	Adrian

---------------------------------------------------------------
Adrian Tritschler                          mailto:ajft@ajft.org
Latitude 38°S, Longitude 145°E, Altitude 50m,      Shoe size 44
---------------------------------------------------------------


  reply	other threads:[~2004-02-10  3:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 15:49 Axel Belinfante
2003-12-02 16:10 ` mirtchov
2004-02-10  3:46   ` Adrian Tritschler [this message]
2004-02-10  5:07     ` Geoff Collyer
2004-02-10  5:12       ` Lucio De Re
2004-02-10 12:22       ` Charles Forsyth
2004-02-10 12:38         ` Lucio De Re
2004-02-10 15:00           ` David Presotto
2004-02-10 15:08             ` Fco.J.Ballesteros
2004-02-10 15:28             ` Lucio De Re
2004-02-11  1:52             ` boyd, rounin
2004-02-10 16:10 Charles Forsyth
2004-02-10 17:24 ` Lucio De Re

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4028540F.6040500@ajft.org \
    --to=ajft@ajft.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).