[Pkg-cups-devel] Problems Building Etch and Lenny cups-1.3.8 Packages

Tue Sep 1 13:54:10 UTC 2009

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

No need to respond to this reported issue.  I have identified
two different bugs that are the cause of the issue and found a
way to work around both serious bugs.

Regards,

John L. Males
Toronto, Ontario
Canada
01 September 2009 09:54 EDT

Message replied to:

Date: Fri, 28 Aug 2009 21:43:25 -0400
From: "John L. Males" <jlmales at bluebottle.com>
To: pkg-cups-devel at lists.alioth.debian.org
Subject: Problems Building Etch and Lenny cups-1.3.8 Packages

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> I am have tried as many ideas to resolve the same problem that
> occurs with both Debian cups packages: 
> 
> cups_1.3.8-1lenny4~bpo40+1
> <http://backports.org/debian/pool/main/c/cups/cups_1.3.8-1lenny4~bpo40+1.dsc>
> 
> cups_1.3.8-1+lenny6.dsc
> <http://ftp.de.debian.org/debian/pool/main/c/cups/cups_1.3.8-1+lenny6.dsc>
> 
> The problem is related to test(s) during the
> "dpkg-buildpackage
> - -rfakeroot" process:
> 
> make[3]: Leaving directory
> `/media/hda7/Debian/4.0r4/kde/backports/cups-1.3.8/man/fr'
> make [2]: Leaving directory
> `/media/hda7/Debian/4.0r4/kde/backports/cups-1.3.8/man' Making
> all in monitor... Making all in notifier... Making all in
> scheduler... Making all in systemv...
> Making all in test...
> Making all in conf...
> Making all in data...
> Making all in doc...
> Making all in fonts...
> Making all in ppd...
> Making all in templates...
> Running CUPS test suite with defaults...
> Welcome to the CUPS Automated Test Script.
> 
> Before we begin, it is important that you understand that the
> larger tests require significant amounts of RAM and disk
> space.  If you attempt to run one of the big tests on a system
> that lacks sufficient disk and virtual memory, the UNIX kernel
> might decide to kill one or more system processes that you've
> grown attached to, like the X server.  The question you may
> want to ask yourself before running a large test is: Do you
> feel lucky?
> 
> OK, now that we have the Dirty Harry quote out of the way,
> please choose the type of test you wish to perform:
> 
> 0 - No testing, keep the scheduler running for me (all
> systems) 1 - Basic conformance test, no load testing (all
> systems) 2 - Basic conformance test, some load testing
> (minimum 256MB VM, 50MB disk) 3 - Basic conformance test,
> extreme load testing (minimum 1GB VM, 500MB disk) 4 - Basic
> conformance test, torture load testing (minimum 2GB VM, 1GB
> disk)
> 
> Enter the number of the test you wish to perform: [1]
> Running the timid tests (1)
> 
> Now you can choose whether to create a SSL/TLS encryption key
> and certificate for testing; these tests currently require the
> OpenSSL tools:
> 
> 0 - Do not do SSL/TLS encryption tests
> 1 - Test but do not require encryption
> 2 - Test and require encryption
> 
> Enter the number of the SSL/TLS tests to perform: [0]
> Not using SSL/TLS (0)
> 
> This test script can use the Valgrind software from:
> 
>     http://developer.kde.org/~sewardj/
> 
> Enter Y to use Valgrind or N to not use Valgrind: [N]
> Creating directories for test...
> Creating cupsd.conf for test...
> Creating printers.conf for test...
> Setting up environment variables for test...
> Starting scheduler:
>      ../scheduler/cupsd -c /tmp/cups-keypunch/cupsd.conf -f
> >/tmp/cups-keypunch/log/debug_log 2>&1 &
> 
> Scheduler is PID 9344.
> Waiting for scheduler to become ready...
> .../run-stp-tests.sh: line 467:  9344 Terminated
> $valgrind ../scheduler/cupsd -c /tmp/cups-$user/cupsd.conf -f
> >/tmp/cups-$user/log/debug_log 2>&1 Waiting for scheduler to
> >become ready... Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> Waiting for scheduler to become ready...
> ^Cmake[1]: *** wait: No child processes.  Stop.
> make[1]: *** Waiting for unfinished jobs....
> make[1]: *** wait: No child processes.  Stop.
> make: *** wait: No child processes.  Stop.
> make: *** Waiting for unfinished jobs....
> make: *** wait: No child processes.  Stop.
>         5117.2 real     105.9 user      14.0 sys
> 20090828 21:24:20-0400 EDT
> keypunch at gdkikvfskdfyksukiuo82i9kdyw2kepoowqpd:/media/hda7/Debian/4.0r4/kde/backports/cups-1.3.8
> tty1 $
> 
> I have tried a variety of web search terms and keywords to
> figure out what this issue is for the last 3 days and many
> attempts of both packages above.  I have to assume the cause
> is simple.  Both meet the required installed packages criteria
> that "dpkg-buildpackage" and the "./configure" scripts check
> for.  I can run "./configure" and "make" just fine manually.
> When I run "make test" then I experience the same as above.
> Any insight would be appreciated.
> 
> 
> Regards,
> 
> John L. Males
> Toronto, Ontario
> Canada
> 28 August 2009 21:43-0400 EDT
> 
> 
> ==============================================================
> 2009-08-28 21:29:08.807205708-0400-EDT
> 
> 28 Aug 21:29:08 ntpdate[12025]: ntpdate 4.2.2p4 at 1.1585-o Sun
> Mar  4 13:21:36 UTC 2007 (1)
> 
> 28 Aug 21:29:14 ntpdate[12030]: step time server
> 206.248.171.198 offset 0.368290 sec
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFKmIfOYn2YdVH66oYRAtsSAJ9ykUp/7hQOJqJFzZ2Ctky8NXRJfwCgqkU0
> Xb9SnznfFnw+F7azAR2CW+g=
> =aC5i
> -----END PGP SIGNATURE-----

==============================================================
2009-09-01 09:51:17.577507845-0400-EDT

 1 Sep 09:51:17 ntpdate[25114]: ntpdate 4.2.2p4 at 1.1585-o Sun
Mar  4 13:21:36 UTC 2007 (1)

 1 Sep 09:51:29 ntpdate[25119]: step time server 67.212.67.75
offset 0.022092 sec

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFKnSeKYn2YdVH66oYRAg8oAKDJ93hjTVQvoqqwcIBXNHdP5yodNwCgr6D/
0vSsEcjz9p5/sYQnhU6mSBk=
=NHyD
-----END PGP SIGNATURE-----