Bug 192867 - security/zxid fails when upgrading from 1.05 to 1.18
Summary: security/zxid fails when upgrading from 1.05 to 1.18
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Rodrigo Osorio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-20 21:11 UTC by Andres Montalban
Modified: 2015-01-26 15:50 UTC (History)
1 user (show)

See Also:


Attachments
Build log error (54.70 KB, text/plain)
2014-08-20 21:11 UTC, Andres Montalban
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Montalban 2014-08-20 21:11:32 UTC
Created attachment 146089 [details]
Build log error

Hi,

security/zxid fails to upgrade from prior port version (1.05) to 1.18. Attached you can see the build log.

I think that the problem is that when linking it's using old libraries instead of the libraries built by the port upgrade.

Thank you very much for doing such great software!

All the best,
Andres Montalban
Comment 1 John Marino freebsd_committer freebsd_triage 2014-08-20 22:14:45 UTC
There is no maintainer for this port, so there's nobody to look at this.
Moving PR to open.

Chance are this is an issue local to you anyway; it's building everywhere:

http://portsmon.freebsd.org/portoverview.py?category=security&portname=zxid
Comment 2 Andres Montalban 2014-08-20 23:12:21 UTC
Hi John,

In order to get 1.18 installed I had to uninstall security/zxid (1.05) and install  it again. Installing on clean systems works ok, the problem is generated when you upgrade it.

Please check: https://forums.freebsd.org/viewtopic.php?f=5&t=47683

I can try to test this tomorrow and see if I can supply a patch.

Let me know if you guys need any further information.

Thanks!
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2014-11-07 23:07:21 UTC
> In order to get 1.18 installed I had to uninstall security/zxid (1.05) and
> install  it again. Installing on clean systems works ok, the problem is
> generated when you upgrade it.

Same with the upgrade from 1.18 to 1.22.
Comment 4 Rodrigo Osorio freebsd_committer freebsd_triage 2015-01-05 16:34:53 UTC
took.
Comment 5 Rodrigo Osorio freebsd_committer freebsd_triage 2015-01-16 14:13:28 UTC
@Andres : are you interested by taking this port maintenership ?
Comment 6 Andres Montalban 2015-01-16 18:10:44 UTC
(In reply to Rodrigo Osorio from comment #5)
Hi Rodrigo,

Yeah, why not? Just a side note, I'm a total beginner with port maintenance :).

Let me know.

Thanks!
Comment 7 Rodrigo Osorio freebsd_committer freebsd_triage 2015-01-18 19:38:09 UTC
Ok, this port was updated to v1.22 in November but still have no maintainer,
so you can request maintenership if you want. Ports are better maintained
if they have an owner who uses them :)
Comment 8 Rodrigo Osorio freebsd_committer freebsd_triage 2015-01-18 19:39:43 UTC
please check if the last update fixes your upgrade issues,
so we can close this PR
Comment 9 Rodrigo Osorio freebsd_committer freebsd_triage 2015-01-26 15:50:15 UTC
The issue can't be reproduced since the port was updated to v1.22 in November 2014.