[MacPorts] #60993: Upgrading fails because of boost port: no matching file found for...

[MacPorts]

#60993: Upgrading fails because of boost port: no matching file found for...
-----------------------+-----------------------
  Reporter:  tillyboy  |      Owner:  michaelld
      Type:  defect    |     Status:  accepted
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.6.3
Resolution:            |   Keywords:
      Port:  boost     |
-----------------------+-----------------------

Comment (by ryandesign):

 Replying to [comment:5 tillyboy]:
 > > Why trace mode?
 >
 > More debugging information is more better.

 Yes, but trace mode is not perfect. It doesn't work at all on macOS 13 or
 later on Apple Silicon systems, it doesn't properly hide python files, it
 causes bmake to fail to build, etc., etc. It's great when it works but it
 can cause builds to fail that wouldn't ordinarily fail. However, I don't
 think trace mode is to blame here (though I don't know what is).

 > So in any case there are broken build variants.

 That's not the conclusion I would reach. We see from your transcript that
 you were downloading a precompiled archive from our server. That means we
 were able to build and install that combination of variants on that OS
 version on our build server, yet you were not. That points to a unique
 problem on your machine.

 The ID number in your message (`id=1116` or whatever) is likely an SQLite
 row ID from the MacPorts registry database. This is the kind of backbone
 MacPorts base code that is used to install every port. Nothing should ever
 fail here. It makes me wonder if your registry database is corrupt in some
 way. You could use standard SQLite commands to try to verify it.

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