Bug 127889 - ports-mgmt/portupgrade detects spurious failures and skips ports unnecessarily
Summary: ports-mgmt/portupgrade detects spurious failures and skips ports unnecessarily
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bryan Drewery
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-06 00:20 UTC by Nate Eldredge
Modified: 2015-05-14 18:53 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Eldredge 2008-10-06 00:20:04 UTC 
When running portupgrade -a, if ports A and B are to be upgraded and B depends on A, it sometimes happens that A is upgraded first, successfully, but portupgrade for some reason thinks it fails and skips upgrading B.

A script session with portupgrade is posted at http://math.ucsd.edu/~neldredg/script-200810051055 (too large to attach).  Note, at line 53711, that textproc/rarian was skipped due to the ostensible failure of libxslt.  However, just before this we see that libxslt in fact installed successfully.  If portupgrade is run a second time, rarian will upgrade successfully.

Fix: 

As a workaround, you can just run portupgrade -a repeatedly until no more packages are skipped, but this is a pain.
How-To-Repeat: It is a bit awkward because it requires that you have ports that are out of date, and once you run portupgrade, they are no longer out of date.  I tried to put together an easy testcase, but did not succeed.  But hopefully there is enough information here to let someone else make one.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-10-06 00:37:38 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->sem

Over to maintainer.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2009-07-25 02:48:50 UTC 
Responsible Changed
From-To: sem->ruby

sem@ has turned over maintainership of portupgrade to the ruby mailing list.
Comment 3 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-10 00:10:36 UTC 
Responsible Changed
From-To: ruby->pgollucci

I will take it
Comment 4 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-24 07:21:46 UTC 
Responsible Changed
From-To: pgollucci->freebsd-ports-bugs

going to have enotime for the next 2 weeks, sorry
Comment 5 Steve Price freebsd_committer freebsd_triage 2011-01-03 17:23:03 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Over to maintainer(s).
Comment 6 Philip M. Gollucci freebsd_committer freebsd_triage 2012-02-22 05:22:55 UTC 
State Changed
From-To: open->suspended

Over to maintainer.
Comment 7 Philip M. Gollucci freebsd_committer freebsd_triage 2012-02-22 05:22:55 UTC 
Responsible Changed
From-To: ruby->freebsd-ports-bugs

Over to maintainer.
Comment 8 Chris Rees freebsd_committer freebsd_triage 2012-04-12 11:03:13 UTC 
State Changed
From-To: suspended->open

This should not be suspended.
Comment 9 Bryan Drewery freebsd_committer freebsd_triage 2012-08-02 14:07:12 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->bdrewery

Over to maintainer.
Comment 10 Carlo Strub freebsd_committer freebsd_triage 2014-09-07 17:51:26 UTC 
Is this PR still relevant?
Comment 11 Bryan Drewery freebsd_committer freebsd_triage 2015-05-14 18:53:18 UTC 
In github at https://github.com/freebsd/portupgrade/issues/14

Closing as this is not reproducible.