SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Since cups ships with the core Slackware OS, there likely won't be a 3rd party SlackBuild. You could modify the one in the 13.37 source tree and see if that works for you. Understand the latter isn't very lazy, but maybe motivation will come later in the day :-)
I just modified the cups.SlackBuild that's on the SlackWare64 DVD under a/source and changed the version to 1.5.0 from 1.4.6. I put the source bz2 file, the new slackbuild script and the slack-desc file in a subdirectory and ran cups.SlackBuild. I then uninstalled the 1.4.6 package and install the new 1.5.0 package. I just printed out a LibreOffice spreadsheet without issue.
I got this while building cups 1.5.0 on Slackware-Current (32 bit):
Code:
Patching file backend/usb-libusb.c using Plan A...
Hunk #1 succeeded at 13.
Hunk #2 succeeded at 66 (offset 1 line).
Hunk #3 FAILED at 105.
Hunk #4 succeeded at 189.
Hunk #5 succeeded at 359.
Hunk #6 succeeded at 595 with fuzz 1 (offset 12 lines).
Hunk #7 succeeded at 631 (offset 12 lines).
Hunk #8 FAILED at 741.
2 out of 8 hunks FAILED -- saving rejects to file backend/usb-libusb.c.rej
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -urNad cups-1.4.3~/backend/usb-unix.c cups-1.4.3/backend/usb-unix.c
|--- cups-1.4.3~/backend/usb-unix.c 2009-12-08 03:13:42.000000000 +0100
|+++ cups-1.4.3/backend/usb-unix.c 2010-04-09 15:56:30.799666933 +0200
--------------------------
Patching file backend/usb-unix.c using Plan A...
Hunk #1 succeeded at 18.
Hunk #2 succeeded at 35.
Hunk #3 succeeded at 102 with fuzz 1.
Hunk #4 succeeded at 132 with fuzz 1.
Hunk #5 succeeded at 149 with fuzz 1 (offset -2 lines).
Hunk #6 succeeded at 193 (offset -2 lines).
Hunk #7 succeeded at 211 (offset -8 lines).
Hunk #8 succeeded at 317 (offset -8 lines).
Hunk #9 succeeded at 354 (offset -8 lines).
Hunk #10 succeeded at 407 (offset -8 lines).
Hunk #11 FAILED at 489.
Hunk #12 succeeded at 605 (offset -8 lines).
1 out of 12 hunks FAILED -- saving rejects to file backend/usb-unix.c.rej
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -urNad cups-1.4.3~/backend/usb.c cups-1.4.3/backend/usb.c
|--- cups-1.4.3~/backend/usb.c 2008-06-24 03:28:36.000000000 +0200
|+++ cups-1.4.3/backend/usb.c 2010-04-09 15:56:04.345707078 +0200
--------------------------
Patching file backend/usb.c using Plan A...
Hunk #1 succeeded at 56.
done
+1, I just took original slackbuild script, changed version to 1.5.0 and removed this lines:
Code:
# Fix the USB backend to use either usblp or libusb:
zcat $CWD/usb-backend-both-usblp-and-libusb.dpatch.gz | patch -p1 --verbose || exit 1
# Fix locking to avoid crashes with OpenSSL:
zcat $CWD/cups.fix_broken_locking.diff.gz | patch -p1 --verbose || exit 1
which are applying patches, which I believe already incorporated in 1.5.0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.