#52443 closed defect (fixed)
The snowleopard-i386-legacy buildbot worker has a case-insensitive filesystem
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | server/hosting | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
The snowleopard-i386-legacy buildbot worker was inadvertently set up with a case-insensitive filesystem. The disk needs to be cloned to a new disk with a case-sensitive filesystem.
The other buildbot workers are not affected.
Change History (2)
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Note: See
TracTickets for help on using
tickets.
I discovered this issue in the course of investigating the nepomuk-core case sensitivity issue (#42904, #49559). After fixing this worker, nepomuk-core still failed to build, because it turns out soprano also has files whose names differ only by case, and the soprano package built on the case-insensitive filesystem did not work on the case-sensitive filesystem. Soprano is not distributable, so the only place where the bad package existed was on this worker, so revbumping the port was not appropriate. Since I also didn't know how many other ports were affected, I uninstalled all ports on this worker, to let it rebuild them correctly. Any distributable ports with case sensitivity issues that were built incorrectly on the old case-insensitive filesystem will need their revisions increased, as I already did for nepomuk-core in r153339.