Opened 2 years ago

Closed 12 months ago

#57507 closed defect (invalid)

Old gegl 0.2 port got stuck

Reported by: mouse07410 (Mouse) Owned by:
Priority: Normal Milestone:
Component: base Version: 2.5.4
Keywords: Cc:


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';
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.

Change History (3)

comment:1 Changed 2 years ago by jmroot (Joshua Root)

Port: port removed
Version: 2.5.4

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?

comment:2 Changed 2 years ago by mouse07410 (Mouse)

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...

comment:3 Changed 12 months ago by dbevans (David B. Evans)

Resolution: invalid
Status: newclosed

This obsolete version has been removed for some time now. Valid gegl ports are gegl, gegl-devel (version 0.4), and gegl-0.3 (which will be obsoleted when current dependents are updated to gegl 0.4).

Note: See TracTickets for help on using tickets.