[Bug 1702] Files .cvsignore'd but in the repository, some of them necessary to bootstrap

bugzilla-daemon at rtems.org bugzilla-daemon at rtems.org
Sun Sep 19 12:53:23 UTC 2010


--- Comment #2 from Peer Stritzinger <peerst at gmail.com> 2010-09-19 07:53:21 CDT ---
(In reply to comment #1)

> > contrib/crossrpms/autotools/rtems-4.11-autoconf.spec
> > contrib/crossrpms/autotools/rtems-4.11-automake.spec
> These are supposed to be in CVS and not to be in .cvsignore.
> They once had been in .cvsignore and have been removed from .cvsignore
> recently.

 cat contrib/crossrpms/autotools/.cvsignore 

This is the revision in the head  (rev 1.1)  (fresh checkout from Sep 17)

RCS file: /usr1/CVS/rtems/contrib/crossrpms/autotools/.cvsignore,v
Working file: contrib/crossrpms/autotools/.cvsignore
head: 1.1
locks: strict
access list:
symbolic names:
        rtems-4-8-2: 1.1

To make sure I checked the branch also (but there is no revision of this file
on the branch):

cvs update -r rtems-4-10-branch  -p contrib/crossrpms/autotools/.cvsignore 
Checking out contrib/crossrpms/autotools/.cvsignore
RCS:  /usr1/CVS/rtems/contrib/crossrpms/autotools/.cvsignore,v
VERS: 1.1

So I suppose these files are still cvsignored ...

> > I'm trying to track my changes in a VCS locally and ignoring all files
> > .cvsignore tells me to ignore results in problems with "bootstrap" that don't
> > occur when these files are present.
> I'd assume you to be facing issue with your VCS and/or your VCS import process.

The import to the local VCS went fine, rtems builds from it.  Recently however
I removed all files matched by cvsignore files from my current version.  
Version with ignore matches removed -> has the mentioned issue with bootstrap. 
Going back before the remove -> builds fine.

In the process to make this running again I created the list of .cvsignore
inconsistencies and posted it because it might help cleaning this up.

> None of these messages is supposed to be ignored, but also no idea what is
> going on for you (I can't reproduce this issue).

My main suspect are the  *.spec files mentioned above.  I'll put files back
into the tree and find out when boostrap stops complaining.

> > autoconf (GNU Autoconf) 2.65
> 2.65 is known to suffer from serious bugs. I haven't notice them to hit rtems
> yet, but I strongly recommend to upgrade to 2.67 (2.66 was a "brown paper bag",
> entirely unusable).


> BTW1: Which OS are you using? Wasn't it you who once mentioned to be facing
> issues with BSD's shell?

Yes I'm still on FreeBSD 8, but since the tree just went from building fine to
not building when I removed these files I don't suppose we are seeing these
shell issues now.  But I'll keep this in mind.

> BTW2: There recently was a CVS tag screw up.
> Try cvs up -dP -A (on CVS-HEAD) rsp. try a fresh checkout.

Did a fresh checkout at Sep 17th to produce the list.

Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the bugs mailing list