Re: docbook fails to build with jhalfs

Pierre Labastie ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
On Mon, 2026-08-17 at 09:57 +0200, Pierre Labastie wrote:
> On Mon, 2026-08-17 at 09:53 +0200, Pierre Labastie wrote:
> > On Mon, 2026-08-17 at 15:05 +0800, Zhang Wen wrote:
> > > docbook-xml contains one directory ent and various files in the
> > > source
> > > file, which be treated as containing top directory by accident.
> > > The following patch work for me and can be cleanly applied to the
> > > trunk branch:
> > > 
> > > --- a/BLFS/xsl/scripts.xsl
> > > +++ b/BLFS/xsl/scripts.xsl
> > > @@ -1188,8 +1188,8 @@ case $PACKAGE in
> > >       JH_UNPACKDIR=`head -n1 unpacked | cut  -d" " -f2 | sed
> > > 's@^\./@@;s@/.*@@'`
> > >       ;;
> > >    *.zip)
> > > -     python3 -m zipfile -l $SRC_DIR/$PACKAGE &gt; unpacked
> > > -     JH_UNPACKDIR="$(sed -n 's@/.*@@p' unpacked | uniq )"
> > > +     python3 -m zipfile -l $SRC_DIR/$PACKAGE|sed '1d' &gt;
> > > unpacked
> > > +     JH_UNPACKDIR="$(sed 's@/.*@@p' unpacked | uniq )"
> > >       if test $(wc -w &lt;&lt;&lt; $JH_UNPACKDIR) -eq 1; then
> > >         python3 -m zipfile -e $SRC_DIR/$PACKAGE .
> > >       else
> > 
> > Hmmm: which version of docbook-xml? I made a change yesterday
> > (commit
> > 84b266463) for docbook-5. Do we have to change something for 4.5?
> > Looks
> > like it worked for me...
> > 
> 
> Oh, sorry, I understand now: it is for docbook-4.5. The sed removes
> all
> lines that do not contain a `/'. If there are files in the listing,
> they get removed too... I think your solution with sed 1d is better
> (but then the p should be suppressed otherwise you get duplicated
> lines...)
> 

Hopefully fixed at commit a76d857. Thanks a lot for report and patch

Pierre

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.