Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
Thank you for your help! Happy hacking!
Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
Hi Alfred, Success! At 2023-09-01T11:41:57-0400, Alfred M. Szmidt wrote: >$ cvsu [...] > Not a typo, it is part of the cvsutils package. Aha! Today I learned...(and "apt-got"). >$ cvs update -PAd > > Right, cvs update will try to add the files back. Did you do remove? > You also need to do commit after. I won't say I didn't have other problems, but that was the worst one. I stumbled a few more times (for a few minutes, groff.html.mode.tar.gz was essentially an empty archive) but I think I finally got it done. The old "html_node" directory with version 1.22.4 of our manual, now out of date, is now 404ing on the GNU site, as desired. Crawlers will do their thing and gradually ensure that more people are steered to the groff 1.23.0 manual. Thank you for your help! Regards, Branden signature.asc Description: PGP signature
Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
It looks like I need some coaching with CVS. It's been a long, long time since I used it daily. No worries, same here .. trying to recall. > $ cvsu > X manual/html_node $ cvsu cvsu: command not found I assume you had a typo, but for what, I'm not sure. Not a typo, it is part of the cvsutils package. $ cvs update -PAd Right, cvs update will try to add the files back. Did you do remove? You also need to do commit after. So basically, cvs remove foo.html; cvs commit -m "foo.html: Delete." foo.html If my memory serves me right. I would suggest, just to be on the safe side, to do it in a fresh checkout. _IF_ you want, you can add me to the groff project, and I can wipe those files.
Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
Hi Alfred, It looks like I need some coaching with CVS. It's been a long, long time since I used it daily. At 2023-08-26T14:15:55-0400, Alfred M. Szmidt wrote: >I asked my CVS checkout what the status of the former is. > >$ cvs status | grep html_node || echo NO RESULT >cvs status: Examining . >NO RESULT > > Which, given a fresh checkout, does not return NO RESULT; since the > directory html_node exists in CVS. That appears to be the case. > So the question remains, how did you checkout, and what did you do in > your directory. I would _guess_ that you've removed it locally, but > never done the cvs step of removing it. I don't remember at this point, but your last hypothesis seems sound. > E.g., in a fresh checkout, I do > > $ rm -rf manual/html_node > $ cvs status|grep html_node||echo NO RESULT > cvs2 status: Examining . > cvs2 status: Examining manual > cvs2 status: Examining manual/groff.html.node > NO RESULT Yes. I'm with you up to this point. After that, things start to go wrong. > $ cvsu > X manual/html_node $ cvsu cvsu: command not found I assume you had a typo, but for what, I'm not sure. > And I will bet that if you do "cvs update -PAd" .. you will once again > have that directory. Yes. Albeit with some problems. $ cvs update -PAd ? LOG ? diff ? manual/groff.html.node/Adjustment.html ? manual/groff.html.node/Argument-Units.html [...] ? manual/groff.html.node/while.html cvs update: Updating . cvs update: Updating manual cvs update: Updating manual/groff.html.node cvs update: move away `manual/groff.html.node/Adjustment.html'; it is in the way C manual/groff.html.node/Adjustment.html cvs update: move away `manual/groff.html.node/Argument-Units.html'; it is in the way [...] C manual/groff.html.node/while.html cvs update: Updating manual/html_node U manual/html_node/Additional-ms-Macros.html U manual/html_node/Argument-Units.html > To remove it, you need to do "cvs remove manual/html_node" -- or > similar. Similar, maybe, but not exactly--this suggestion fails. $ cvs remove manual/html_node cvs remove: Removing manual/html_node cvs remove: file `manual/html_node/Additional-ms-Macros.html' still in working directory cvs remove: file `manual/html_node/Argument-Units.html' still in working directory [...] cvs remove: file `manual/html_node/while.html' still in working directory cvs remove: 220 files exist; remove them first Taking its advice is not helpful. $ rm -f manual/html_node/* rm: cannot remove 'manual/html_node/CVS': Is a directory $ cvs remove manual/html_node/* cvs [remove aborted]: no such directory `manual/html_node' I'd very much appreciate your further assistance! :-O Regards, Branden signature.asc Description: PGP signature
Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
>https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/ If you open that URL you will find a directory: https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/html_node/ Yes, that directory exists. alongside this one: https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/groff.html.node/ So does this one. I asked my CVS checkout what the status of the former is. $ cvs status | grep html_node || echo NO RESULT cvs status: Examining . NO RESULT Which, given a fresh checkout, does not return NO RESULT; since the directory html_node exists in CVS. So the question remains, how did you checkout, and what did you do in your directory. I would _guess_ that you've removed it locally, but never done the cvs step of removing it. E.g., in a fresh checkout, I do $ rm -rf manual/html_node $ cvs status|grep html_node||echo NO RESULT cvs2 status: Examining . cvs2 status: Examining manual cvs2 status: Examining manual/groff.html.node NO RESULT $ cvsu X manual/html_node And I will bet that if you do "cvs update -PAd" .. you will once again have that directory. To remove it, you need to do "cvs remove manual/html_node" -- or similar.
Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
Hi Alfred, At 2023-08-26T09:43:09-0400, Alfred M. Szmidt wrote: >There is a stale directory in the GNU groff project's website. > >https://www.gnu.org/software/groff/manual/html_node/ > >This corresponds to the groff 1.22.4 release, which is nearly 5 years >old. > >The directory also shows up in ViewVC. > >https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/ > >However it is _not_ present in my CVS checkout. > > How did you checkout your directory? What did you do in your > checkout? > > I did a fresh checkout, and manual/ is there, as it should be from the > looks of it. So it is not stale, might be out-dated, but that is > becuase nobody removed it. I apologize for (I think) not being sufficiently clear. >https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/ If you open that URL you will find a directory: https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/html_node/ alongside this one: https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/groff.html.node/ I asked my CVS checkout what the status of the former is. $ cvs status | grep html_node || echo NO RESULT cvs status: Examining . NO RESULT > I'm not sure what intervention is needed, manual/ is part of the > source tree, nobody (you?) never removed it. manual/ isn't the problem--html_node/ is. Thanks for the swift follow-up. Regards, Branden signature.asc Description: PGP signature
Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project
There is a stale directory in the GNU groff project's website. https://www.gnu.org/software/groff/manual/html_node/ This corresponds to the groff 1.22.4 release, which is nearly 5 years old. The directory also shows up in ViewVC. https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/ However it is _not_ present in my CVS checkout. How did you checkout your directory? What did you do in your checkout? I did a fresh checkout, and manual/ is there, as it should be from the looks of it. So it is not stale, might be out-dated, but that is becuase nobody removed it. My memories of CVS are that it didn't handle symlinks well. Does this require administrative intervention? I'm not sure what intervention is needed, manual/ is part of the source tree, nobody (you?) never removed it.
