Bug 746993

Summary: Source RPM does not compile in mock
Product: [Fedora] Fedora Reporter: Patrick Monnerat <patrick>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: mclasen, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 21:47:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Patch to prevent network access by xsltproc when builing docs none

Description Patrick Monnerat 2011-10-18 14:02:15 UTC
Description of problem:
There are some xsltproc errors preventing successful compilation of source RPM in mock.

Version-Release number of selected component (if applicable):
gdm-3.2.0-2.fc16

How reproducible:
Always (well, at least today 2011/18/10

Steps to Reproduce:
1. mock --rebuild -r fedora-16-x86_64 gdm-3.2.0-2.fc16.src.rpm
  
Actual results:
Extracted from build log:
.
.
.
xsltproc -o gdm-de.omf --stringparam db2omf.basename gdm --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.1.2//EN" --stringparam db2omf.lang de --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/builddir/build/BUILD/gdm-3.2.0/docs/gdm.omf.in"  `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` de/gdm.xml || { rm -f "gdm-de.omf"; exit 1; }
.
.
.
xsltproc -o gdm-en_GB.omf --stringparam db2omf.basename gdm --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.1.2//EN" --stringparam db2omf.lang en_GB --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/builddir/build/BUILD/gdm-3.2.0/docs/gdm.omf.in"  `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` en_GB/gdm.xml || { rm -f "gdm-en_GB.omf"; exit 1; }
http://www.oasis-open.org/docbook/xml/4.1.2/dbpoolx.mod:3408: parser warning : PEReference: %tbl.table.att; not found
                %tbl.table.att;
                               ^
.
.
.
xsltproc -o gdm-fr.omf --stringparam db2omf.basename gdm --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.1.2//EN" --stringparam db2omf.lang fr --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/builddir/build/BUILD/gdm-3.2.0/docs/gdm.omf.in"  `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` fr/gdm.xml || { rm -f "gdm-fr.omf"; exit 1; }
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:115: parser warning : PEReference: %list.class; not found
                %local.divcomponent.mix;">
                                         ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:115: parser warning : PEReference: %admon.class; not found
                %local.divcomponent.mix;">
                                         ^
.
.    ...lots of warnings as above, then:
.
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:236: parser error : ContentDecl : Name or '(' expected
        | keywordset | itermset | %bibliocomponent.mix;)+)>
                                                       ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:236: parser error : expected '>'
        | keywordset | itermset | %bibliocomponent.mix;)+)>
                                                         ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:236: parser error : Content error in the external subset
        | keywordset | itermset | %bibliocomponent.mix;)+)>
                                                         ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:243: parser warning : PEReference: %setinfo.attlist; not found
<![%setinfo.attlist;[
                    ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:243: parser error : conditional section INCLUDE or IGNORE keyword expected
<![%setinfo.attlist;[
                    ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:243: parser error : Content error in the external subset
<!ATTLIST setinfo
 ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:243: parser error : Content error in the external subset
<!ATTLIST setinfo
    ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:243: validity error : All markup of the conditional section is not in the same entity
<!ATTLIST setinfo
    ^
http://www.oasis-open.org/docbook/xml/4.1.2/dbhierx.mod:243: parser error : Content error in the external subset
<!ATTLIST setinfo
       ^
unable to parse de/gdm.xml
make[2]: *** [gdm-de.omf] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/builddir/build/BUILD/gdm-3.2.0/docs'
.
.
.

Expected results:
Successful rpm compilation.

Thanks for fixing it.

Comment 1 Patrick Monnerat 2011-10-24 14:31:40 UTC
Created attachment 529885 [details]
Patch to prevent network access by xsltproc when builing docs

The bug is still present in 3.2.1.1.

It is caused by xsltproc downloading files at build time: network access is blocked in koji, so it compiles successfully. But in a typical mock installation, network is accessible and parse errors cause the build to fail.

I resolved this problem by applying the "nonet" patch and by a "BuildRequires: docbook-dtds".

Please consider applying this to the Fedora "official" version. Thanks in advance.

Comment 2 Matthias Clasen 2011-10-24 19:48:09 UTC
gnome-doc-utils.make is a generated file, so ideally this needs to be fixed in gnome-doc-utils.

Comment 3 Patrick Monnerat 2011-10-25 09:32:12 UTC
You're probably right: I don't know this later package.

But since the gnome-doc-utils.make file generation occurred before making the gdm tarball, I think the current package should be fixed that way for now.

Please note also that BuildRequiring docbook-dtds may do the job even without the patch, simply by satisfying support files presence (but I did not test it).

Of course, speaking of this problem to gnome-doc-utils people is not forbidden :-)

Comment 4 Fedora End Of Life 2013-01-16 17:16:38 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 21:47:04 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.