Opened 14 years ago
Closed 11 years ago
#26869 closed enhancement (fixed)
e2fsprogs conflict with kerberos5
| Reported by: | lagrave+bugs+macosforge.org@… | Owned by: | neverpanic (Clemens Lang) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | mf2k (Frank Schima), dershow, pboe@…, shanto@…, hosseini@…, andrewbass@…, maverickwoo (Maverick Woo), willy.wolff.0@…, mklein-de (Michael Klein), piotr1212@…, deesto (John S. De Stefano Jr.), macports@…, NickFabry (Nick Fabry), cooljeanius (Eric Gallager), rmstonecipher@… | |
| Port: | e2fsprogs kerberos5 |
Description (last modified by mf2k (Frank Schima))
port -d install e2fsprogs
...
---> Activating e2fsprogs @1.41.12_0
Error: Target org.macports.activate returned: Image error: /opt/local/bin/compile_et is being used by the active kerberos5 port. Please deactivate this port first, or use 'port -f activate e2fsprogs' to force the activation.
DEBUG: Backtrace: Image error: /opt/local/bin/compile_et is being used by the active kerberos5 port. Please deactivate this port first, or use 'port -f activate e2fsprogs' to force the activation.
while executing
"_activate_contents $name $imagefiles $imagedir"
(procedure "portimage::activate" line 110)
invoked from within
"registry_activate $name "${version}_${revision}${portvariants}" [array get user_options]"
(procedure "portactivate::activate_main" line 6)
invoked from within
"$procedure $targetname"
Log for e2fsprogs is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_e2fsprogs/main.log
Error: Status 1 encountered during processing.
I don't use kerberos directly but it is required by GnuPG and OpenSSL
Change History (26)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | e2fsprogs conflict with kerberos → e2fsprogs conflict with kerberos5 |
|---|
comment:3 Changed 13 years ago by Russell-Jones-OxPhys (Russell Jones)
Why do they need to conflict? Can't the file concerned be renamed or relocated? It looks like they both have the same package as a subsidiary build. Could this be moved to a separate port?
comment:4 follow-up: 5 Changed 13 years ago by nerdling (Jeremy Lavergne)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
These were already marked as conflicting, they cannot collide.
comment:5 Changed 12 years ago by Russell-Jones-OxPhys (Russell Jones)
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
Replying to snc@…:
These were already marked as conflicting, they cannot collide.
Yes, that's the problem! I want to install both of these ports at the same time.
comment:6 Changed 12 years ago by Russell-Jones-OxPhys (Russell Jones)
This should be marked as an enhancement rather than a defect, but I can't do that myself.
comment:7 Changed 12 years ago by raimue (Rainer Müller)
| Type: | defect → enhancement |
|---|
Similar ticket #16271 about conflict on libuuid with ossp-uuid.
comment:16 Changed 12 years ago by mf2k (Frank Schima)
| Description: | modified (diff) |
|---|---|
| Version: | 1.9.1 |
comment:24 follow-up: 25 Changed 11 years ago by rmstonecipher@…
Forgive me if this is a dumb question:
How could a committer with subversion (which depends upon kerberos5) installed revise e2fsprogs to test and commit changes?
comment:25 Changed 11 years ago by neverpanic (Clemens Lang)
| Owner: | changed from macports-tickets@… to cal@… |
|---|---|
| Status: | reopened → new |
Replying to rmstonecipher@…:
How could a committer with subversion (which depends upon kerberos5) installed revise e2fsprogs to test and commit changes?
Xcode ships a subversion binary. You could also rebuild cyrus-sasl2 with -kerberos to avoid the dependency.
I've updated e2fsprogs to 1.42.7 in r102458. This commit also moves libcomerr, which is the culprit in this bug to a separate port and changes kerberos5 to use this library (rather than installing it's own builtin version) in r102459.
comment:26 Changed 11 years ago by neverpanic (Clemens Lang)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This solves the conflict between kerberos5 and e2fsprogs.
They were already marked as conflicting in r63087. Not sure why your MacPorts doesn't seem to be recognizing that.