Bug 98153 - Fix a small buglet in sysutils/portupgrade
Summary: Fix a small buglet in sysutils/portupgrade
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Sergey Matveychuk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-30 15:40 UTC by Anton Berezin
Modified: 2006-06-02 11:10 UTC (History)
0 users

See Also:


Attachments
file.diff (632 bytes, patch)
2006-05-30 15:40 UTC, Anton Berezin
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Berezin freebsd_committer freebsd_triage 2006-05-30 15:40:28 UTC
In case of multiple origin change, when the resulting origin is the same
as the original origin, portupgrade still produces a warning.  Please
see the following IRC conversation for details:

< roth__> ** Package origin of 'pan' has been changed: 'news/pan' -> 'news/pan'
< roth__> ?
< roth__> persists after portupgrade -f
<@Grrrr> news/pan|news/pan2|2003-11-03|Stable release can be found in news/pan2
<@Grrrr> news/pan2|news/pan|2006-05-28|Use unversioned name
<@Grrrr> hmm?
< roth__> hehe
< roth__> makes sense though, to go back to unversioned, once that becomes stable
<@Grrrr> yes, the bitching is understandable, but wrong
<@arved> i think we had this before with a port, and removed the old MOVED line
<@Grrrr> arved, hmm, would not it be more correct to fix the offender to not produce those messages?
< roth__> more correct?
<@arved> hehe :-), nobody likes touching portupgrade
<@Grrrr> sounds like a really trivial fix
<@linimon_> it seems as though the canonical solution these days is to remove those two lines from MOVED.
<@Grrrr> two would be wrong for those who still has news/pan2 installed
<@linimon_> I'm not saying that I like that solution.
<@linimon_> the first line sounds like it should go, though.
<@Grrrr> http://rafb.net/paste/results/1qIGfC58.txt
<@Grrrr> roth__: can you test that it fixes it?
< roth__> ok, hold on
< roth__> Grrrr: no more complaining

Fix: The patch below can be applied either "upstream", or to the port itself,
I'll let the maintainer to decide.
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2006-05-30 15:44:21 UTC
Responsible Changed
From-To: freebsd-ports-bugs->tobez

Submitter has GNATS access
Comment 2 Edwin Groothuis freebsd_committer freebsd_triage 2006-05-30 15:44:30 UTC
State Changed
From-To: open->feedback

Awaiting maintainers feedback
Comment 3 Sergey Matveychuk freebsd_committer freebsd_triage 2006-06-01 09:00:44 UTC
Responsible Changed
From-To: tobez->sem

Take all portupgrade related PRs
Comment 4 Sergey Matveychuk freebsd_committer freebsd_triage 2006-06-01 16:07:23 UTC
State Changed
From-To: feedback->analyzed

Tested
Comment 5 Sergey Matveychuk freebsd_committer freebsd_triage 2006-06-02 11:10:48 UTC
State Changed
From-To: analyzed->closed

Committed. Thanks!