<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Am 02.08.2018 um 15:30 schrieb Michal Nowak:
<br>
<blockquote type="cite" style="color: #000000;">On Thursday, August
2, 2018 at 1:01 PM, Andreas Wacknitz <a
class="moz-txt-link-rfc2396E" href="mailto:A.Wacknitz@gmx.de"><A.Wacknitz@gmx.de></a>
wrote:
<br>
<blockquote type="cite" style="color: #000000;">Hi,
<br>
<br>
In my new build environment I have problems with zziplib. I have
created
<br>
a new sample-manifest an compared it to the original:
<br>
<br>
diff sample-manifest.p5m sample-manifest.p5m.orig
<br>
13c13
<br>
< # Copyright 2018 <contributor>
<br>
---
<br>
<blockquote type="cite" style="color: #000000;"># Copyright 2017
<contributor>
<br>
</blockquote>
121a122,131
<br>
<blockquote type="cite" style="color: #000000;">file
path=usr/share/man/man3/zzip_dir_alloc.3
<br>
file path=usr/share/man/man3/zzip_dir_alloc_ext_io.3
<br>
file path=usr/share/man/man3/zzip_dir_free.3
<br>
file path=usr/share/man/man3/zzip_dir_open.3
<br>
file path=usr/share/man/man3/zzip_dir_open_ext_io.3
<br>
file path=usr/share/man/man3/zzip_dir_read.3
<br>
file path=usr/share/man/man3/zzip_dir_real.3
<br>
file path=usr/share/man/man3/zzip_dir_stat.3
<br>
file path=usr/share/man/man3/zzip_dirfd.3
<br>
file path=usr/share/man/man3/zzip_dirhandle.3
<br>
</blockquote>
154a165,193
<br>
<blockquote type="cite" style="color: #000000;">file
path=usr/share/man/man3/zzip_error.3
<br>
file path=usr/share/man/man3/zzip_file_real.3
<br>
file path=usr/share/man/man3/zzip_file_stat.3
<br>
file path=usr/share/man/man3/zzip_fopen.3
<br>
file path=usr/share/man/man3/zzip_fread.3
<br>
file path=usr/share/man/man3/zzip_freopen.3
<br>
file path=usr/share/man/man3/zzip_fstat.3
<br>
file path=usr/share/man/man3/zzip_get_default_io.3
<br>
file path=usr/share/man/man3/zzip_init_io.3
<br>
file path=usr/share/man/man3/zzip_open.3
<br>
file path=usr/share/man/man3/zzip_open_ext_io.3
<br>
file path=usr/share/man/man3/zzip_open_shared_io.3
<br>
file path=usr/share/man/man3/zzip_opendir.3
<br>
file path=usr/share/man/man3/zzip_opendir_ext_io.3
<br>
file path=usr/share/man/man3/zzip_read.3
<br>
file path=usr/share/man/man3/zzip_realdir.3
<br>
file path=usr/share/man/man3/zzip_realfd.3
<br>
file path=usr/share/man/man3/zzip_rewinddir.3
<br>
file path=usr/share/man/man3/zzip_seek.3
<br>
file path=usr/share/man/man3/zzip_seek32.3
<br>
file path=usr/share/man/man3/zzip_seekdir.3
<br>
file path=usr/share/man/man3/zzip_seekdir32.3
<br>
file path=usr/share/man/man3/zzip_seterror.3
<br>
file path=usr/share/man/man3/zzip_strerror.3
<br>
file path=usr/share/man/man3/zzip_strerror_of.3
<br>
file path=usr/share/man/man3/zzip_tell.3
<br>
file path=usr/share/man/man3/zzip_tell32.3
<br>
file path=usr/share/man/man3/zzip_telldir.3
<br>
file path=usr/share/man/man3/zzip_telldir32.3
<br>
</blockquote>
<br>
At least some of the missing man pages actually cannot be shown
on my
<br>
system with the zziplib package installed, eg.
<br>
man zzip_dir_alloc
<br>
mandoc: zzip_dir_alloc_ext_io.3: ERROR: No such file or
directory
<br>
()
<br>
()
<br>
<br>
See the file zzip_dir_alloc_ext_io.3.
<br>
<br>
August 2,
<br>
2018 ()
<br>
<br>
<br>
<br>
<br>
I am not sure how to proceed here. Is it a problem on my build
env or do
<br>
others have the same problems?
<br>
<br>
Regards,
<br>
Andreas
<br>
<br>
</blockquote>
I was able to build the component recently.
<br>
</blockquote>
I used to be able to publish it, too. But not with my new build
environment.
<br>
Sometime I start from scratch in order to find errors we don't find
otherwise.
<br>
I have a list of packages that don't build or publish for one reason
or another (part of my components.ignore):
<br>
<br>
# Failing packages for aw
<br>
#
<br>
/^archiver\/zziplib$/d
<br>
/^database\/pgloader$/d
<br>
/^developer\/golang-110$/d
<br>
/^editor\/emacs$/d
<br>
/^library\/glibmm$/d
<br>
/^library\/goffice$/d
<br>
/^library\/libgtop$/d
<br>
/^library\/p11-kit$/d
<br>
/^library\/physfs$/d
<br>
/^multimedia\/sox$/d
<br>
/^python\/coherence$/d
<br>
/^scientific\/gdl$/d
<br>
/^sysutils\/clamav$/d
<br>
/^text\/hunspell-de$/d
<br>
/^text\/tidy$/d
<br>
<br>
This list is typically growing and from time to time I start to
investigate and try to fix the problems (or ask for help ;-)).
<br>
For example our emacs build isn't working at all. It has lisp
compile errros that
are easily overseen during the build process.<br>
Alarcher already confirmed this but has no time to fix it. I already
tried to build it with different compiler versions but with no luck
yet.
<br>
Furthermore, emacs-26.1 has the same problems. So even creating a
newer version doesn't solve the problem at the moment.<br>
<br>
<blockquote type="cite" style="color: #000000;">Are all build
requirements present in the environment? Specifically text/xmlto.
I configure script able to detect it properly?
<br>
</blockquote>
I I have created a simple script that I maintain that install almost
everything. (BTW: If you have a better solution for creating build
envs I am open for suggestions.
<br>
Maintaining a big script is tedious and errorprone.)
<br>
So yes, xmlto and xmltoman are installed.
<br>
<br>
<blockquote type="cite" style="color: #000000;">
<br>
Are those man pages generated or just not installed in the proto
area?
<br>
</blockquote>
They are in the proto area (or should be).
<br>
Can you check for me whether my example works for you:
<br>
man zzip_disk_buffer
<br>
gives an error for me (the installed package seems to have serveral
errors like this). Even if it builds and publishes on your
environment, there seem to be a problem with the package.
<br>
Did you start from a clean environment? I usually start with a
'gmake clean' and also remove former source folders (if the version
has changed).
<br>
Our build enviroment isnt't really well prepared for removes of
files.
<br>
<br>
Andreas
</body>
</html>