Opened 2 months ago
Closed 2 months ago
#74189 closed defect (fixed)
muniversal portgroup broken with deferred loading
| Reported by: | saagarjha (Saagar Jha) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | jmroot (Joshua Root), MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) | |
| Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I've noticed that with the changes in [06ff92efad0e3bf8226ccdebfef3d05ba7142f43/macports-base] (and subsequent plumbing commits) the universal portgroup does not work anymore:
$ sudo port -N upgrade outdated Error: libiconv: Error executing universal: can't rename "portconfigure::configure_main": command doesn't exist Error: Unable to open port: Error evaluating variants Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
I can selfupdate just fine but I cannot upgrade anything because of this (I assume because I have +universal in my config).
Change History (8)
comment:1 Changed 2 months ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|
comment:2 Changed 2 months ago by jmroot (Joshua Root)
| Component: | base → ports |
|---|
comment:3 Changed 2 months ago by jmroot (Joshua Root)
comment:4 Changed 2 months ago by jmroot (Joshua Root)
comment:6 Changed 2 months ago by jmroot (Joshua Root)
| Cc: | MarcusCalhoun-Lopez added |
|---|
@saagarjha: Is it working for you now?
@MarcusCalhoun-Lopez: Is there a way that base could provide an interface to allow muniversal to do what it needs to do without messing around with internals? Is there a test suite for muniversal that could be used to verify that it still works after base changes?
comment:7 Changed 2 months ago by saagarjha (Saagar Jha)
Yep, I was able to upgrade without problems after running selfupdate to get that commit
comment:8 Changed 2 months ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.

This is because this portgroup is modifying code that is not part of the public API for Portfiles.