[MacPorts] #57507: Old gegl 0.2 port got stuck

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[MacPorts] #57507: Old gegl 0.2 port got stuck

MacPorts
#57507: Old gegl 0.2 port got stuck
------------------------+--------------------
 Reporter:  mouse07410  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  Normal      |  Milestone:
Component:  base        |    Version:
 Keywords:              |       Port:  port
------------------------+--------------------
 MacOS High Sierra 10.13.6, current Macports.


 {{{
 $ sudo sqlite3 /opt/local/var/macports/registry/registry.db
 SQLite version 3.25.2 2018-09-25 19:08:10
 Enter ".help" for usage hints.
 sqlite> SELECT * FROM ports WHERE name='gegl';
 2131|gegl|2bd1fd9639671665cf8a79359d3fa4d8ccaa7c53c6625aa62cadf9f05c239060-4819|/opt/local/var/macports/software/gegl/gegl-0.2.0-20180218_2+quartz.darwin_17.x86_64.tbz2|0|0.2.0-20180218|2|+quartz||installed|1525053324|image|x86_64|0|darwin|17|libc++|0
 sqlite> .quit
 $ port installed gegl gegl-0.2 gegl-0.4
 The following ports are currently installed:
   gegl @0.2.0-20180218_2+quartz (active)
   gegl-0.4 @0.4.12_2+x11 (active)
 $ sudo port uninstall gegl @0.2.0-20180218_2
 Error: port uninstall failed: Registry error: gegl @0.2.0-20180218_2 not
 registered as installed
 $ sudo port deactivate gegl @0.2.0-20180218_2
 Error: port deactivate failed: Active version of gegl is not
 0.2.0-20180218_2 but 0.2.0-20180218_2+quartz.
 $ sudo port clean gegl @0.2.0-20180218_2
 Warning: Skipping gegl (not in the ports tree)
 $
 }}}

 Thankfully, I managed to get rid of that old gegl 0.2 thing, by doing


 {{{
 $ sudo port uninstall gegl @0.2.0-20180218_2+quartz
 Warning: Failed to open Portfile from registry for gegl
 @0.2.0-20180218_2+quartz
 Warning: Failed to open Portfile from registry for gegl
 @0.2.0-20180218_2+quartz
 --->  Deactivating gegl @0.2.0-20180218_2+quartz
 --->  Uninstalling gegl @0.2.0-20180218_2+quartz
 $ sudo port clean gegl @0.2.0-20180218_2+quartz
 Error: Port gegl not found
 $ sudo port -v rev-upgrade
 --->  Scanning binaries for linking errors
 --->  No broken files found.
 --->  No broken ports found.
 $
 }}}

 But it shouldn't've happened at all - I shouldn't have had to do that.

--
Ticket URL: <https://trac.macports.org/ticket/57507>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #57507: Old gegl 0.2 port got stuck

MacPorts
#57507: Old gegl 0.2 port got stuck
-------------------------+--------------------
  Reporter:  mouse07410  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  base        |    Version:  2.5.4
Resolution:              |   Keywords:
      Port:              |
-------------------------+--------------------
Changes (by jmroot):

 * version:   => 2.5.4
 * port:  port =>


Comment:

 Some of those errors are expected. If you provide a version specifier, it
 needs to be exactly as shown by `port installed`, including any variants.
 `sudo port uninstall gegl` would have figured out the version for you
 since there was only one version installed.

 Failing to open the Portfile in the registry is something that shouldn't
 happen, but as you can see there is a fallback path for when it does. I
 don't suppose you have any way of showing us the failing Portfile now?

--
Ticket URL: <https://trac.macports.org/ticket/57507#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #57507: Old gegl 0.2 port got stuck

MacPorts
In reply to this post by MacPorts
#57507: Old gegl 0.2 port got stuck
-------------------------+--------------------
  Reporter:  mouse07410  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  base        |    Version:  2.5.4
Resolution:              |   Keywords:
      Port:              |
-------------------------+--------------------

Comment (by mouse07410):

 > I don't suppose you have any way of showing us the failing Portfile now?

 I don't know. Probably not. Also, I'm not sure it's the Portfile of this
 specific (outdated) port that failed. My suspicion is that during the
 upgrade to gegl-0.4 or such something got removed without accounting for
 that removal...

--
Ticket URL: <https://trac.macports.org/ticket/57507#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS