Ticket #26869 (closed enhancement: fixed)
e2fsprogs conflict with kerberos5
| Reported by: | lagrave+bugs+macosforge.org@… | Owned by: | cal@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | macsforever2000@…, dersh@…, pboe@…, shanto@…, hosseini@…, andrewbass@…, maverick.woo@…, willy.wolff.0@…, michael.klein@…, piotr1212@…, deesto@…, macports@…, nick.fabry@…, egall@…, rmstonecipher@… | |
| Port: | e2fsprogs kerberos5 |
Description (last modified by macsforever2000@…) (diff)
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
comment:1 Changed 3 years ago by ryandesign@…
- Summary changed from e2fsprogs conflict with kerberos to e2fsprogs conflict with kerberos5
comment:3 Changed 22 months ago by 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 21 months ago by snc@…
- Status changed from new to closed
- Resolution set to worksforme
These were already marked as conflicting, they cannot collide.
comment:5 in reply to: ↑ 4 Changed 14 months ago by russell.jones@…
- Status changed from closed to reopened
- Resolution worksforme deleted
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 14 months ago by russell.jones@…
This should be marked as an enhancement rather than a defect, but I can't do that myself.
comment:7 Changed 14 months ago by raimue@…
- Type changed from defect to enhancement
Similar ticket #16271 about conflict on libuuid with ossp-uuid.
comment:16 Changed 7 months ago by macsforever2000@…
- Version 1.9.1 deleted
- Description modified (diff)
comment:24 follow-up: ↓ 25 Changed 4 months 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 in reply to: ↑ 24 Changed 4 months ago by cal@…
- Status changed from reopened to new
- Owner changed from macports-tickets@… to cal@…
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 4 months ago by cal@…
- Status changed from new to closed
- Resolution set to fixed
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.