Bug 140880 - ports-mgmt/portupgrade: portversion confused with ezm3 on amd64
Summary: ports-mgmt/portupgrade: portversion confused with ezm3 on amd64
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: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-25 22:40 UTC by Helmut Schneider
Modified: 2011-08-21 22:16 UTC (History)
0 users

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 Helmut Schneider 2009-11-25 22:40:06 UTC 
# pkg_info | grep ezm3
ezm3-1.1_2          Easier, more portable Modula-3 distribution for building CV
# portversion -v | grep ezm3
ezm3-1.1_2                  <  needs updating (port has 1.2_1)
# grep -ir amd64 /usr/ports/lang/ezm3/distinfo
MD5 (ezm3/ezm3-1.1-FBSD_AMD64-boot.tar.bz2) = 9a035001f85ebe063ad24f5993d787aa
SIZE (ezm3/ezm3-1.1-FBSD_AMD64-boot.tar.bz2) = 1533175
MD5 (ezm3/ezm3-amd64-patchset-2.tar.bz2) = 8c6ee79d7971cb723d5919a921a8aa76
SIZE (ezm3/ezm3-amd64-patchset-2.tar.bz2) = 294919
SHA256 (ezm3/ezm3-1.1-FBSD_AMD64-boot.tar.bz2) = c99b572764361c45d41465de420452614947f675554477e4b38f2973deb511cf
SHA256 (ezm3/ezm3-amd64-patchset-2.tar.bz2) = 0fbefd87a084fec319bb39f61d1f18437927767f83574d0ac685566da0adb3e8
# portupgrade -v ezm3-1.1_2
--->  Session started at: Wed, 25 Nov 2009 23:34:04 +0100
** None has been installed or upgraded.
--->  Session ended at: Wed, 25 Nov 2009 23:34:04 +0100 (consumed 00:00:00)
#

I assume that 1.1 is recent for amd64 allthough even freshports is confusing:

http://www.freshports.org/lang/ezm3/
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-11-25 23:18:02 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Fix synopsis and assign.
Comment 2 Sergey Matveychuk freebsd_committer freebsd_triage 2009-12-18 14:48:02 UTC 
State Changed
From-To: open->closed

The port has two different version for i386 and amd64. This is not 
compatible with INDEX build logic. So, it's not quite portupgrade issue.
Comment 3 Sergey Matveychuk freebsd_committer freebsd_triage 2009-12-18 14:48:08 UTC 
State Changed
From-To: closed->suspended

A better state is suspended.
Comment 4 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-10 00:11:58 UTC 
Responsible Changed
From-To: ruby->pgollucci

I will take it
Comment 5 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-10 00:15:19 UTC 
State Changed
From-To: suspended->open

open
Comment 6 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-24 07:22:51 UTC 
Responsible Changed
From-To: pgollucci->freebsd-ports-bugs

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

Over to maintainer(s).
Comment 8 Tilman Keskinoz freebsd_committer freebsd_triage 2011-07-25 11:26:26 UTC 
State Changed
From-To: open->suspended

As sem stated earlier, this is a problem with the INDEX build logic 
So suspend this PR
Comment 9 Steve Wills freebsd_committer freebsd_triage 2011-08-21 22:15:50 UTC 
Responsible Changed
From-To: ruby->swills

I'll take it.
Comment 10 Steve Wills freebsd_committer freebsd_triage 2011-08-21 22:16:20 UTC 
State Changed
From-To: suspended->closed

This isn't a portupgrade specific issue and no change to portupgrade is 
going to fix it. Closing PR. If there are further issues, please open a 
new PR.