Bug 201250 - cad/z88: Update to 14.0
Summary: cad/z88: Update to 14.0
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Rene Ladan
URL:
Keywords: needs-qa, patch
Depends on:
Blocks:
 
Reported: 2015-07-01 13:47 UTC by Anton Shterenlikht
Modified: 2015-12-26 11:57 UTC (History)
3 users (show)

See Also:


Attachments
patch to pass the checksum stage (1.72 KB, patch)
2015-07-03 09:36 UTC, Anton Shterenlikht
no flags Details | Diff
svn diff for cad/z88 (37.19 KB, patch)
2015-07-27 08:34 UTC, Anton Shterenlikht
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Shterenlikht 2015-07-01 13:47:16 UTC
cad/z88 is marked
BROKEN=         Unfetchable

The latest version can be fetched from

http://en.z88.de/download-z88os

e.g.

http://download.z88.de/z88os/z88v14os_english.tar.gz

Anton
Comment 1 Dmitry Marakasov freebsd_committer freebsd_triage 2015-07-01 15:21:00 UTC
The port has no maintainer, so it's likely that there's nobody to work out an update beside you.
Comment 2 Anton Shterenlikht 2015-07-01 15:25:12 UTC
thought so. I'll try.
Comment 3 Anton Shterenlikht 2015-07-03 09:36:16 UTC
Created attachment 158281 [details]
patch to pass the checksum stage

Stuck on the patch stage, need help
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2015-07-05 01:39:14 UTC
The best references for instructions on how to test ports is the Porters Handbook, which you can find here:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-testing.html

There are also IRC channels dedicated to FreeBSD Ports:

 * #bsdports (efnet)
 * #freebsd-ports (freenode)
Comment 5 Anton Shterenlikht 2015-07-27 08:34:20 UTC
Created attachment 159300 [details]
svn diff for cad/z88

svn diff against /usr/ports.
To apply copy the patch to /usr/ports,
cd /usr/ports
svn patch z88.diff

Unresolved problem: make package hangs.

build/install proceed fine.
Comment 6 Rene Ladan freebsd_committer freebsd_triage 2015-12-01 21:35:29 UTC
The patch does not work here, the last part of the poudriere log (9.3-RELEASE i386):

=======================<phase: configure      >============================
===>   z88-14.0 depends on executable: pkgconf - found
===>   z88-14.0 depends on file: /usr/local/libdata/pkgconfig/glproto.pc - found
===>   z88-14.0 depends on file: /usr/local/libdata/pkgconfig/dri2proto.pc - found
===>   z88-14.0 depends on file: /usr/local/bin/ccache - found
===>   z88-14.0 depends on shared library: libgtkglext-x11-1.0.so - found (/usr/local/lib/libgtkglext-x11-1.0.so)
===>   z88-14.0 depends on shared library: libGLU.so - found (/usr/local/lib/libGLU.so)
===>   z88-14.0 depends on shared library: libatk-1.0.so - found (/usr/local/lib/libatk-1.0.so)
===>   z88-14.0 depends on shared library: libglib-2.0.so - found (/usr/local/lib/libglib-2.0.so)
===>   z88-14.0 depends on shared library: libgtk-x11-2.0.so - found (/usr/local/lib/libgtk-x11-2.0.so)
===>   z88-14.0 depends on shared library: libpango-1.0.so - found (/usr/local/lib/libpango-1.0.so)
===>  Configuring for z88-14.0
===========================================================================
=======================<phase: build          >============================
===>  Building for z88-14.0
make: don't know how to make /wrkdirs/usr/ports/cad/z88/work/z88v14os/src/z88com/unix/z88com.c. Stop
*** [do-build] Error code 2

Stop in /usr/ports/cad/z88.

The same happens when I do a "dirty" in-place build.

It looks like z88/work/z88v14os/ does not exist, but z88/work/z88-14.0/z88v14os/ does.

I have full poudriere logs for 9.3-RELEASE-i386 and 11.0-CURRENT-amd64 available.
Comment 7 Rene Ladan freebsd_committer freebsd_triage 2015-12-26 11:53:04 UTC
No feedback for 25 days, and r404471 made the current version of the port workable again.
Comment 8 Kubilay Kocak freebsd_committer freebsd_triage 2015-12-26 11:57:31 UTC
Feedback timeout as per comment 7.

@Mexas, please re-open the issue if you can provide a patch update to fix the issue reported in comment 6