Closed Bug 402847 Opened 18 years ago Closed 18 years ago

cvs wonkyness in l10n/fy-NL/toolkit/chrome/places, or Places?

Categories

(mozilla.org :: CVS: Administration, task)

Product:
mozilla.org
Component:
CVS: Administration
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Pike, Assigned: justdave)

Details

There is something wonky with the l10n/fy-NL/toolkit/chrome/Places dir, or places. I'm getting mixed results on that locally, and IIRC, Wim committed it the wrong way and tried to fix it. But somehow, this is still awkward. It doesn't seem to bust any builds, and it's impact seems to be platform or cvs version dependent, too. I think. Could you take a look at that on the rep side and see if there's a fix? I'd let it linger until Nick has done the Fx3B1 builds, as currently it doesn't seem to be causing bustages, as I don't know what's wrong, I don't really know what a fix could break. To recap, l10n/fy-NL/toolkit/chrome/Places/places.properties should be l10n/fy-NL/toolkit/chrome/Places/places.properties. Thanks
(In reply to comment #0) > To recap, l10n/fy-NL/toolkit/chrome/Places/places.properties should be > l10n/fy-NL/toolkit/chrome/Places/places.properties. The second one was supposed to be "l10n/fy-NL/toolkit/chrome/places/places.properties", presumably?
Component: Server Operations → CVS: Administration
Duh, yes, of course. Too many things with too little conference wifi. Thanks for catching that.
Both places and Places exist in CVS. This is generally bad for Mac and Windows which have case-insensitive filesystems, which will probably wind up with the uppercase version getting created and the contents of the lowercase one winding up in it. Because of the way Attics work and so forth, the only way around it is to outright delete the upper-case version from the repository, losing any history it has along the way.
Assignee: server-ops → justdave
ok, having looked at the content, there's nothing in the uppercase version except the initial commit and subsequent delete of the file which looks to be the same as the one in the lowercase version, so I went ahead and nuked it. You might have to delete the directory and let it get recreated on Mac and Windows. Linux/Unix users will probably have to manually remove the uppercase one from your CVS/Entries file in the parent directory. (Win/Mac might have to do that also -- you'll know if you get weird errors about the directory not existing)
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
win32 and mac tinderboxes required intervention, linux is fine (no uppercase line in CVS/Entries).
You need to log in before you can comment on or make changes to this bug.