#53311 closed defect (fixed)
kdepimlibs4 @4.14.3_8 conflicts with gpgme @1.8.0_1
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | NicosPavlov |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | leonardo@…, dbevans (David B. Evans), mkae (Marko Käning) | |
Port: | kdepimlibs4, gpgme |
Description
---> Activating kdepimlibs4 @4.14.3_8 Error: Failed to activate kdepimlibs4: Image error: /opt/local/include/gpgme++/configuration.h is being used by the active gpgme port. Please deactivate this port first, or use 'port -f activate kdepimlibs4' to force the activation.
Change History (5)
comment:1 Changed 8 years ago by NicosPavlov
Status: | new → assigned |
---|
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Revbumping kdelibs4 doesn't automatically fix the already-installed kdepimlibs4, which still gives:
$ sudo port install kdepimlibs4 ---> Computing dependencies for kdepimlibs4 ---> Activating kdepimlibs4 @4.14.3_8 Error: Failed to activate kdepimlibs4: Image error: /opt/local/include/gpgme++/configuration.h is being used by the active gpgme port. Please deactivate this port first, or use 'port -f activate kdepimlibs4' to force the activation. Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_macports-ports_kde_kdepimlibs4/kdepimlibs4/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port kdepimlibs4 failed
comment:3 Changed 8 years ago by mkae (Marko Käning)
Cc: | mkae added |
---|
comment:4 Changed 8 years ago by NicosPavlov
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Indeed. I also wanted to check the other KDE ports, which also required a revbump. Done in [bd777452e51291cefa6d1faa738d9c747078eaad/macports-ports].
comment:5 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Please use TracLinks to link to your commits when you mention them. I've fixed your above comment to do this.
Note: See
TracTickets for help on using
tickets.
Thanks for pointing that out. I stupidly missed a port to revbump (now done in commit [6adbcd2e8541fcbeee932313c11574b8ca24e3eb/macports-ports]), which indirectly caused this.
I am keeping the ticket live for now, as I still want to check if that means that dependents ports need yet another revbump.