[oi-dev] Problems publishing zziplib
mnowak at startmail.com
Thu Aug 2 20:42:03 UTC 2018
On 08/02/18 05:08 PM, Andreas Wacknitz wrote:
> Am 02.08.2018 um 15:30 schrieb Michal Nowak:
>> On Thursday, August 2, 2018 at 1:01 PM, Andreas Wacknitz
>> <A.Wacknitz at gmx.de> wrote:
>>> In my new build environment I have problems with zziplib. I have created
>>> a new sample-manifest an compared it to the original:
>>> diff sample-manifest.p5m sample-manifest.p5m.orig
>>> < # Copyright 2018 <contributor>
>>>> # Copyright 2017 <contributor>
>>>> file path=usr/share/man/man3/zzip_dir_alloc.3
>>>> file path=usr/share/man/man3/zzip_dir_alloc_ext_io.3
>>>> file path=usr/share/man/man3/zzip_dir_free.3
>>>> file path=usr/share/man/man3/zzip_dir_open.3
>>>> file path=usr/share/man/man3/zzip_dir_open_ext_io.3
>>>> file path=usr/share/man/man3/zzip_dir_read.3
>>>> file path=usr/share/man/man3/zzip_dir_real.3
>>>> file path=usr/share/man/man3/zzip_dir_stat.3
>>>> file path=usr/share/man/man3/zzip_dirfd.3
>>>> file path=usr/share/man/man3/zzip_dirhandle.3
>>>> file path=usr/share/man/man3/zzip_error.3
>>>> file path=usr/share/man/man3/zzip_file_real.3
>>>> file path=usr/share/man/man3/zzip_file_stat.3
>>>> file path=usr/share/man/man3/zzip_fopen.3
>>>> file path=usr/share/man/man3/zzip_fread.3
>>>> file path=usr/share/man/man3/zzip_freopen.3
>>>> file path=usr/share/man/man3/zzip_fstat.3
>>>> file path=usr/share/man/man3/zzip_get_default_io.3
>>>> file path=usr/share/man/man3/zzip_init_io.3
>>>> file path=usr/share/man/man3/zzip_open.3
>>>> file path=usr/share/man/man3/zzip_open_ext_io.3
>>>> file path=usr/share/man/man3/zzip_open_shared_io.3
>>>> file path=usr/share/man/man3/zzip_opendir.3
>>>> file path=usr/share/man/man3/zzip_opendir_ext_io.3
>>>> file path=usr/share/man/man3/zzip_read.3
>>>> file path=usr/share/man/man3/zzip_realdir.3
>>>> file path=usr/share/man/man3/zzip_realfd.3
>>>> file path=usr/share/man/man3/zzip_rewinddir.3
>>>> file path=usr/share/man/man3/zzip_seek.3
>>>> file path=usr/share/man/man3/zzip_seek32.3
>>>> file path=usr/share/man/man3/zzip_seekdir.3
>>>> file path=usr/share/man/man3/zzip_seekdir32.3
>>>> file path=usr/share/man/man3/zzip_seterror.3
>>>> file path=usr/share/man/man3/zzip_strerror.3
>>>> file path=usr/share/man/man3/zzip_strerror_of.3
>>>> file path=usr/share/man/man3/zzip_tell.3
>>>> file path=usr/share/man/man3/zzip_tell32.3
>>>> file path=usr/share/man/man3/zzip_telldir.3
>>>> file path=usr/share/man/man3/zzip_telldir32.3
>>> At least some of the missing man pages actually cannot be shown on my
>>> system with the zziplib package installed, eg.
>>> man zzip_dir_alloc
>>> mandoc: zzip_dir_alloc_ext_io.3: ERROR: No such file or directory
>>> See the file zzip_dir_alloc_ext_io.3.
>>> August 2,
>>> 2018 ()
>>> I am not sure how to proceed here. Is it a problem on my build env or do
>>> others have the same problems?
>> I was able to build the component recently.
> I used to be able to publish it, too. But not with my new build
> Sometime I start from scratch in order to find errors we don't find
> I have a list of packages that don't build or publish for one reason or
> another (part of my components.ignore):
> # Failing packages for aw
> This list is typically growing and from time to time I start to
> investigate and try to fix the problems (or ask for help ;-)).
> For example our emacs build isn't working at all. It has lisp compile
> errros that are easily overseen during the build process.
> 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.
> Furthermore, emacs-26.1 has the same problems. So even creating a newer
> version doesn't solve the problem at the moment.
>> Are all build requirements present in the environment? Specifically
>> text/xmlto. I configure script able to detect it properly?
> 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.
> Maintaining a big script is tedious and errorprone.)
> So yes, xmlto and xmltoman are installed.
>> Are those man pages generated or just not installed in the proto area?
> They are in the proto area (or should be).
> Can you check for me whether my example works for you:
> man zzip_disk_buffer
> 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.
> 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).
> Our build enviroment isnt't really well prepared for removes of files.
It seems to me like a bug in docbook-xsl:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831831 Once I add that
patch, the man page is in correct format and `man` is able to display.
However, I don't know why we are short of some man pages...
More information about the oi-dev