Daniel Schepler <[EMAIL PROTECTED]> wrote Tue, Apr 05, 2005: > Matt Brubeck <[EMAIL PROTECTED]> writes: > > >> Unfortunately, today's upload of sgml2x didn't fix the problem. > > > > I didn't have any problem building the latest sgml2x in a chroot. What > > was the exact error? > > As I said in the original bug report, the message is > > links -no-home -dump TODO-html/t1.htm >TODO.txt > ELinks: Permission denied > make[1]: *** [TODO.txt] Error 1 > make[1]: Leaving directory `/tmp/buildd/sgml2x-1.0.0' > make: *** [build-stamp] Error 2 > > It's easy to reproduce this just by using pbuilder with a standard > setup (I just retried it after updating my base.tgz).
I have problems reproducing this. I do: $ pbuilder create $ apt-get source sgml2x $ pbuilder build sgml2x_1.0.0-9.dsc [...] make[1]: Entering directory `/tmp/buildd/sgml2x-1.0.0' [...] sed 's|@SGMLDIR@|/usr/share/sgml|g' < catalog-installable.in > catalog-installable bin/docbook-2-html -c catalog -C ./sgml2x-aliases -s nwalsh TODO.sgml openjade1.3:W: unsupported declaration will be ignored openjade1.3:W: unsupported declaration will be ignored openjade1.3:W: unsupported declaration will be ignored links -no-home -dump TODO-html/t1.htm >TODO.txt cd doc && /usr/bin/make all make[2]: Entering directory `/tmp/buildd/sgml2x-1.0.0/doc' docbook-to-man sgml2x.sgml > sgml2x.1 [...] What am I doing wrong? Do I need to pass some flags to pbuilder? I am running Debian unstable. > >> To get a similar error outside a chroot, I can run 'dpkg-buildpackage > >> ... </dev/null', which causes elinks to output an error message > >> > >> ELinks: Unknown file type > > > > This can be fixed by adding the following option to the "links" command > > line: > > > > -eval 'set protocol.file.allow_special_files=1' > > This fixes the </dev/null case, but not the pbuilder case. If I add > </dev/null as well as the -eval flag, the package builds successfully > under pbuilder. > > But that's just a workaround. If the program is running in -dump > mode, it should just be skipping all the initialization which has to > do with user interaction. The problem is in the buggy autodetection of stdin and stdout which caused /dev/stdin to always be added to the URL list. I have fixed this so that it is only added if no URL is given. Futhermore if /dev/stdin is added special files are automatically allowed. So this part of the bug should theoretically have been resolved once I backport the fix to 0.10.4. > By the way, this bug is now also affecting jargon-text. I will try to release 0.10.4 tonight or tomorrow and then hope Gervai have time to upload it. -- Jonas Fonseca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
