Cups-1.2.10

Hi all,

Currently, the book has CUPS-1.2.7. 1.2.10 is the current
version.

However, the current version fails the test suite miserably.
It is
a known bug, and fixed in SVN. I made a very small patch
that updates
the 1.2.10 'test' directory to SVN, and all but 1 test
passes (there
are 9 that fail before the patch).

Note that you must run the dbus-uuidgen program first, or
you will
get additional failures.

I cannot figure out which other file(s) needs changing to
get all the
tests to fail, so I created a patch that bumps the current
version
(1.2.10) to current SVN. It builds, and tests just fine.
Here are
the files changed using the bigger patch:

patching file CHANGES.txt
patching file backend/usb-darwin.c
patching file backend/usb-unix.c
patching file backend/usb.c
patching file conf/mime.convs
patching file conf/mime.types
patching file config-scripts/cups-common.m4
patching file configure
patching file cups/cups.h
patching file cups/language.c
patching file cups/localize.c
patching file cups/ppd.c
patching file cups/request.c
patching file filter/interpret.c
patching file filter/pstops.c
patching file packaging/cups.spec
patching file scheduler/classes.c
patching file scheduler/conf.c
patching file scheduler/ipp.c
patching file scheduler/job.c
patching file scheduler/printers.c
patching file templates/pl/printers.tmpl
patching file test/4.2-cups-printer-ops.test
patching file test/4.3-job-ops.test
patching file test/4.4-subscription-ops.test
patching file test/run-stp-tests.sh


Our choices are this:

1. Simply leave 1.2.7 in the book until 1.2.11 comes out.
2. Use the small patch (4006 bytes) and note in the book
that one
   test will fail.
3. Use the larger patch (706998 bytes) and call it
'upstream_fixes'
   or something.
4. Do something else (Fedora CVS doesn't really help, and I
didn't
   check any other distro, including Paldo).


Which way should we go?

-- 
Randy

rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc
(GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3
i686]
12:17:00 up 3 days, 17:14, 1 user, load average: 0.00, 0.00,
0.00
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Randy McMurchy wrote:
> Hi all,
> 
> Currently, the book has CUPS-1.2.7. 1.2.10 is the
current version.
> 
> However, the current version fails the test suite
miserably. It is
> a known bug, and fixed in SVN. I made a very small
patch that updates
> the 1.2.10 'test' directory to SVN, and all but 1 test
passes (there
> are 9 that fail before the patch).
> 
> Note that you must run the dbus-uuidgen program first,
or you will
> get additional failures.
> 
> I cannot figure out which other file(s) needs changing
to get all the
> tests to fail, so I created a patch that bumps the
current version
> (1.2.10) to current SVN. It builds, and tests just
fine. Here are
> the files changed using the bigger patch:

> Our choices are this:
> 
> 1. Simply leave 1.2.7 in the book until 1.2.11 comes
out.
> 2. Use the small patch (4006 bytes) and note in the
book that one
>    test will fail.
> 3. Use the larger patch (706998 bytes) and call it
'upstream_fixes'
>    or something.
> 4. Do something else (Fedora CVS doesn't really help,
and I didn't
>    check any other distro, including Paldo).
> 
> 
> Which way should we go?

I understand that the tests fail due to test suite problems,
but does
the program itself fail in normal use?

It sounds like #2 would be a temporary workaround until
1.2.11 comes out
(#1).  Perhaps that is the best way to go.

  -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Bruce Dubbs wrote these words on 04/08/07 13:06 CST:
> Randy McMurchy wrote:
>> 3. Use the larger patch (706998 bytes) and call it
'upstream_fixes'
>>    or something.
>>
>> Which way should we go?
> 
> I understand that the tests fail due to test suite
problems, but does
> the program itself fail in normal use?

Dunno. Never tried it. I typically won't install a package
that has
a myriad of test failures, when all the tests in prior
versions
*never* failed.


> It sounds like #2 would be a temporary workaround until
1.2.11 comes out
> (#1).  Perhaps that is the best way to go.

Well, after thinking about it some more, I feel a new
version
will be released soon. So, I used the large patch which
takes the
package to a version which may end up being the next
production
version. And that's the one I want to install on my test
system,
and test all the other packages against.

So, since I cannot vouch for the 1.2.10 (unpatched) as
working,
I'll leave the update for someone else, or we'll just move
to
1.2.11 when it is released.

Attached is the small patch if anyone's interested in
updating CUPS
to 1.2.10.

-- 
Randy

rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc
(GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3
i686]
14:07:00 up 3 days, 19:04, 1 user, load average: 0.17, 0.04,
0.02

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Bruce Dubbs schrieb am 08.04.2007 20:06:
> Randy McMurchy wrote:
>> Hi all,
>>
>> Currently, the book has CUPS-1.2.7. 1.2.10 is the
current version.
>>
>> However, the current version fails the test suite
miserably. It is
>> a known bug, and fixed in SVN. I made a very small
patch that updates
>> the 1.2.10 'test' directory to SVN, and all but 1
test passes (there
>> are 9 that fail before the patch).
..........
> 
> I understand that the tests fail due to test suite
problems, but does
> the program itself fail in normal use?

I tried it a few days ago but reverted back to 1.2.7,
because it was not 
possible to authorize root from the localhost:631 interface
(using 
Firefox 2.0.0.3 as browser).

Bernd

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

On Mon, 2007-04-09 at 00:48 +0200, Bernd Pol wrote:
> Bruce Dubbs schrieb am 08.04.2007 20:06:
> > Randy McMurchy wrote:
> >> Hi all,
> >>
> >> Currently, the book has CUPS-1.2.7. 1.2.10 is
the current version.
> >>
> >> However, the current version fails the test
suite miserably. It is
> >> a known bug, and fixed in SVN. I made a very
small patch that updates
> >> the 1.2.10 'test' directory to SVN, and all
but 1 test passes (there
> >> are 9 that fail before the patch).
> ..........
> > 
> > I understand that the tests fail due to test suite
problems, but does
> > the program itself fail in normal use?
> 
> I tried it a few days ago but reverted back to 1.2.7,
because it was not 
> possible to authorize root from the localhost:631
interface (using 
> Firefox 2.0.0.3 as browser).

Works fine here using Cups 1.2.10 on paldo.

Jürg

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Just getting back from vacation.

On 4/8/07, Randy McMurchy <randylinuxfromscratch.org>
wrote:
>
> Note that you must run the dbus-uuidgen program first,
or you will
> get additional failures.

This is with dbus-1.0.x, right? dbus-uuidgen has been added
in the
0.9.x series and should be run during `make install', I
think. It's a
standard part of the dbus installation now to give your
machine a
unique identifier for dbus over a network.

It's definitely not run if you install to a DESTDIR, but I
think it
should be run on a normal install. I don't know offhand, but
it will
certainly be addressed if that's not the case when dbus is
updated in
the book. Here's a little background:

http://lists.freedesktop.org/archives/dbus/20
06-October/005994.html

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Dan Nicholson wrote these words on 04/09/07 09:19 CST:
> On 4/8/07, Randy McMurchy <randylinuxfromscratch.org> wrote:
>> Note that you must run the dbus-uuidgen program
first, or you will
>> get additional failures.
> 
> This is with dbus-1.0.x, right?

Yes. 1.0.2


> dbus-uuidgen has been added in the
> 0.9.x series and should be run during `make install', I
think. It's a
> standard part of the dbus installation now to give your
machine a
> unique identifier for dbus over a network.

Well, it must have not been run during my installation. I
looked at
the installation log and don't see anything. Additionally, I
had
to manually run it, so that CUPS could find the file.


> It's definitely not run if you install to a DESTDIR,
but I think it
> should be run on a normal install. I don't know
offhand, but it will
> certainly be addressed if that's not the case when dbus
is updated in
> the book.

I was going to mention this, however, it appears to be out
in the
open now.

-- 
Randy

rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc
(GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3
i686]
09:21:01 up 4 days, 14:18, 1 user, load average: 0.08, 0.10,
0.08
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

On 4/9/07, Randy McMurchy <randylinuxfromscratch.org>
wrote:
> Dan Nicholson wrote these words on 04/09/07 09:19 CST:
> > dbus-uuidgen has been added in the
> > 0.9.x series and should be run during `make
install', I think. It's a
> > standard part of the dbus installation now to give
your machine a
> > unique identifier for dbus over a network.
>
> Well, it must have not been run during my installation.
I looked at
> the installation log and don't see anything.
Additionally, I had
> to manually run it, so that CUPS could find the file.

Major correction. dbus-uuidgen is supposed to be run from
the
bootscripts according to NEWS and it is not run during `make
install'
at all. Here's that info:

- dbus-uuidgen --ensure is now run in the init script so
there is no need to
  run it in a post script
- dbus-uuidgen now writes out to /var/lib/dbus to work with
systems that do not
  have a writable /etc. Packages should install and own the
/var/lib/dbus
  directory

Here's what the RedHat bootscript does:

start() {
    echo -n $"Starting system message bus: "
    if [ -x EXPANDED_BINDIR/dbus-uuidgen ] ; then
        EXPANDED_BINDIR/dbus-uuidgen --ensure
    fi
...

So, it looks like we'll have to fix up the bootscript a bit
for 1.0.2.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page