[MacPorts] #29324: sane-backends update issue

[MacPorts]

#29324: sane-backends update issue
---------------------------------+------------------------------------------
 Reporter:  zelegolas@…          |       Owner:  aguynamedryan+sane@…        
     Type:  defect               |      Status:  new                         
 Priority:  Normal               |   Milestone:                              
Component:  ports                |     Version:  1.9.2                       
 Keywords:                       |        Port:  sane-backends               
---------------------------------+------------------------------------------

Comment(by aguynamedryan+macports@…):

 I'm sorry to hear the upgrade isn't going smoothly for you.  I did not
 encounter any activation errors on my end.

 In the past, when I encountered such problems with other ports, I simply
 run:
 {{{
 sudo port -f activate some-port
 }}}
 and that seems to resolve the issue for me without causing any issues in
 the long run.


 I looked through a few pages of the wiki and found that most people
 recommend a similar course of action.  These are the relevant links I
 found:
   * [wiki:FAQ#whentoforce] - a page that suggests you do as I describe
 above
   * [wiki:ProblemHotlist#xmlwf] - a page that suggests the more drastic
 approach of zapping your entire MacPorts installation (you probably want
 to avoid this)


 I also looked at tickets for other ports that have run into this problem:
  * This one suggests that if you have a case-sensitive filesystem, you
 might have a problem: (#28634)
    * The solution was to force the activation
    * This one also suggests that maybe you need to migrate from the flat
 DB to sqlite for you MacPorts database
  * This one suggests removing the file, then attempting activation again
 (#26757)
  * And this one suggests that these kinds of bugs are non-issues unless it
 can be demonstrated that MacPorts itself is failing to record files in its
 filemap (#26114)


 I stopped looking through tickets after that because the first handful I
 saw all seem to suggest that this is not a bug that a maintainer can
 really addres.

 I hope you find this information helpful.  If you find there is anything
 else I can do, please let me know.

-- 
Ticket URL: <https://trac.macports.org/ticket/29324#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS