On May 14, Michael Ablassmeier ([EMAIL PROTECTED]) wrote:
 > Package: opensp
 > Severity: serious
 > Version: 1.5.2-3
 > Justification: policy violation
 > 
 > hi, 
 > 
 > Lucas has rebuild the archive on i386 and your package Failed to Build
 > from Source with the following error:
 > 
 >  test -z "/usr/share/doc/OpenSP" || mkdir -p -- 
 > "/build/user/opensp-1.5.2/debian/tmp/usr/share/doc/OpenSP"
 >  install -o root -g root -m 644 -p 'releasenotes.html' 
 > '/build/user/opensp-1.5.2/debian/tmp/usr/share/doc/OpenSP/releasenotes.html'
 >  install -o root -g root -m 644 -p 'releasenotes.pdf' 
 > '/build/user/opensp-1.5.2/debian/tmp/usr/share/doc/OpenSP/releasenotes.pdf'
 >  install -o root -g root -m 644 -p './releasenotes.ps' 
 > '/build/user/opensp-1.5.2/debian/tmp/usr/share/doc/OpenSP/releasenotes.ps'
 >  install: cannot stat `./releasenotes.ps': No such file or directory
 >  make[5]: *** [install-pkgdocDATA] Error 1
 >  
 > the full log can be found here:
 > 
 >  
 > http://people.debian.org/~lucas/logs/2007/05/13/opensp_1.5.2-3_sid32.buildlog
 > 
 > bye,
 >     - michael

I'm having trouble reproducing this.  If you look in the log at the part just
prior to the errors you provided, you'll see that it executes:

/usr/bin/pdf2ps releasenotes.pdf releasenotes.ps

which is supposed to convert the PDF file releasenotes.pdf into the Postscript
file releasenotes.ps.  However, in the log you provided, rather than putting
the Postscript in a file, it is getting dumped to stdout or stderr, i.e., it
appears in the log.  So, the later step where it tries to install
releasenotes.ps fails because that files was not created. When I build this
package on an up to date sid system, that does not occur, it creates
releasenotes.ps just fine.  I tried building it three ways: "debian/rules
install", dpkg-buildpackage and pdebuild, and all built fine. How exactly was
this built, i.e., what utility/commands did Lucas use?

-- 
Neil Roeth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to