[MacPorts] #49559: neponuk can't be installed on a case-sensitive system
#49559: neponuk can't be installed on a case-sensitive system ---------------------+-------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: base | Version: 2.3.4 Keywords: neponuk | Port: kdenlive ---------------------+-------------------------------- see ticket #49458 for details [https://trac.macports.org/ticket/49458#comment:15] -- Ticket URL: <https://trac.macports.org/ticket/49559> MacPorts <https://www.macports.org/> Ports system for OS X
#49559: neponuk can't be installed on a case-sensitive system -----------------------+-------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: neponuk Port: kdenlive | -----------------------+-------------------------------- Changes (by mf2k@…): * priority: High => Normal Comment: The Priority field is for use by Macports team members only. -- Ticket URL: <https://trac.macports.org/ticket/49559#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49559: neponuk can't be installed on a case-sensitive system -----------------------+-------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: neponuk Port: kdenlive | -----------------------+-------------------------------- Comment (by info@…): no problem. why is the priority field accessible to the public when we create a new ticket then ? we shouldn't have that option available if it's for your team only... -- Ticket URL: <https://trac.macports.org/ticket/49559#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#49559: neponuk can't be installed on a case-sensitive system ----------------------+-------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: neponuk | ----------------------+-------------------------------- Changes (by ryandesign@…): * keywords: neponuk => * port: kdenlive => neponuk Old description:
see ticket #49458 for details
New description: see ticket #49458 for details comment:ticket:49458:15 -- Comment: I'm not aware whether Trac can be configured to restrict the use of the priority field. Our ticket filing instructions make clear that it isn't to be used. In any case, please provide in this ticket a summary of the problem. You've marked this is as a bug in base, but I don't understand what we could change in base to alter this situation. -- Ticket URL: <https://trac.macports.org/ticket/49559#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#49559: neponuk can't be installed on a case-sensitive system ----------------------+-------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: neponuk | ----------------------+-------------------------------- Comment (by rjvbertin@…): I don't think the reporter knows, nor do I. The issue is this: nepomuk installs `${prefix}/include/nepomuk2/variant.h` and `${prefix}/include/Nepomuk2/Variant`. Contrary to the bug title, this installs fine on a case-*sensitive* filesystem. On case-insensitive, this leads to a single directory that contains both `variant.h` and `Variant` (and the other C-style vs. C++ style headers). The name of that directory will be `nepomuk2` (not `Nepomuk2` because the C-style headers are installed last. The binary package produced by the build bots show the same phenomenon, something I have reported before already. Why this happens is a mystery to me, but this would happen if the destroot that serves to create the binary package is on a case-insensitive FS, for instance. C++ code will use `#include <Nepomuk2/Variant`. When the header is installed as `${prefix}/include/nepomuk2/Variant` on a case-sensitive filesystem, this include statement will fail. -- Ticket URL: <https://trac.macports.org/ticket/49559#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#49559: nepomuk-core can't be installed on a case-sensitive system -----------------------------+-------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: fixed | Keywords: Port: nepomuk-core | -----------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * cc: ryandesign@…, nicos@…, rjvbertin@… (added) * component: base => server/hosting * resolution: => fixed * port: neponuk => nepomuk-core Comment: Replying to [comment:4 rjvbertin@…]:
The binary package produced by the build bots show the same phenomenon, something I have reported before already. Why this happens is a mystery to me, but this would happen if the destroot that serves to create the binary package is on a case-insensitive FS, for instance.
The new buildbot setup does not show this behavior, so I revbumped nepomuk-core in r153339 so that all the packages are correctly rebuilt for case-sensitive systems. See also #42904. -- Ticket URL: <https://trac.macports.org/ticket/49559#comment:5> MacPorts <https://www.macports.org/> Ports system for the Mac operating system
participants (1)
-
MacPorts