[opensuse] Out of date CUPS...
Hi all. I note that the latest version of cups in any of the official repositories is version 1.5.4, but the latest version available from cups.org is 1.7.4. According to the cups.org release notes, 1.7.4 includes many fixes including at least one security related fix. Is anyone working on packaging 1.7.4 for openSuSE? I would do it myself via the build service but every time I've tried to do that has ended in abject failure. I obviously have no idea what I'm doing there... Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 16 Jul 2014 20:01:34 Rodney Baker wrote:
Hi all. I note that the latest version of cups in any of the official repositories is version 1.5.4, but the latest version available from cups.org is 1.7.4.
According to the cups.org release notes, 1.7.4 includes many fixes including at least one security related fix. Is anyone working on packaging 1.7.4 for openSuSE?
I would do it myself via the build service but every time I've tried to do that has ended in abject failure. I obviously have no idea what I'm doing there...
Regards, Rodney.
Hmmm. The OBS manual is hopelessly incomplete (at least, the online version is). Useless for a newby, so far. Nevertheless, i have downloaded the source from cups.org, modified the supplied spec file BuildRequires lines to match the distro package names/versions for the dependencies and successfully built it locally using rpmbuild. Next, I've created a new project on OBS and uploaded the tar.bz2 source file (which I was able to build directly, locally, with rpm -ta <source-file.bz2>). Now what? OBS just doesn't want to know about building with only the compressed source file uploaded (at least, not via the web interface) but how to I tell it to extract it? Isn't this supposed to be easy? -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 16 Jul 2014 20:55:52 Rodney Baker wrote:
On Wed, 16 Jul 2014 20:01:34 Rodney Baker wrote: [...] Next, I've created a new project on OBS and uploaded the tar.bz2 source file (which I was able to build directly, locally, with rpm -ta <source- file.bz2>). Now what? OBS just doesn't want to know about building with only the compressed source file uploaded (at least, not via the web interface) but how to I tell it to extract it?
Isn't this supposed to be easy?
OK, so now I got it to start building by uploading the (locally working) spec file separately to the source tarball, but it fails on the configure step with "need pkgconfig to enable libusb support". Where to now? Any OBS users or experts here? Or am I on the wrong list? Sigh... -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rodney Baker [16.07.2014 13:52]:
On Wed, 16 Jul 2014 20:55:52 Rodney Baker wrote:
On Wed, 16 Jul 2014 20:01:34 Rodney Baker wrote: [...] Next, I've created a new project on OBS and uploaded the tar.bz2 source file (which I was able to build directly, locally, with rpm -ta <source- file.bz2>). Now what? OBS just doesn't want to know about building with only the compressed source file uploaded (at least, not via the web interface) but how to I tell it to extract it?
Isn't this supposed to be easy?
OK, so now I got it to start building by uploading the (locally working) spec file separately to the source tarball, but it fails on the configure step with "need pkgconfig to enable libusb support".
Where to now? Any OBS users or experts here? Or am I on the wrong list?
You might get more responeses on <opensuse-buildservice@opensuse.org> :-) Did you look at the packages in the Printing (https://build.opensuse.org/project/show/Printing) repo? Maybe you can take them as a start for your own work. OBS has its pitfalls... Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 16 Jul 2014 15:09:36 Werner Flamme wrote:
[...]
OK, so now I got it to start building by uploading the (locally working) spec file separately to the source tarball, but it fails on the configure step with "need pkgconfig to enable libusb support".
Where to now? Any OBS users or experts here? Or am I on the wrong list?
You might get more responeses on <opensuse-buildservice@opensuse.org> :-)
Did you look at the packages in the Printing (https://build.opensuse.org/project/show/Printing) repo? Maybe you can take them as a start for your own work. OBS has its pitfalls...
Regards, Werner
Thanks, Werner. Yet another mailing list to subscribe to. :-| But seriously, thanks. I'll see what I can dig up there. I've had a look at the Printing repo but that's still at version 1.5.4 and I really have no idea how those packages are built. Perhaps they're built without libusb support - I might have to figure out how to dig out the spec file from the rpm and see. Regards, Rodney -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/16/2014 09:30 AM, Rodney Baker pecked at the keyboard and wrote:
On Wed, 16 Jul 2014 15:09:36 Werner Flamme wrote:
[...]
OK, so now I got it to start building by uploading the (locally working) spec file separately to the source tarball, but it fails on the configure step with "need pkgconfig to enable libusb support".
Where to now? Any OBS users or experts here? Or am I on the wrong list?
You might get more responeses on <opensuse-buildservice@opensuse.org> :-)
Did you look at the packages in the Printing (https://build.opensuse.org/project/show/Printing) repo? Maybe you can take them as a start for your own work. OBS has its pitfalls...
Regards, Werner
Thanks, Werner. Yet another mailing list to subscribe to. :-| But seriously, thanks. I'll see what I can dig up there. I've had a look at the Printing repo but that's still at version 1.5.4 and I really have no idea how those packages are built. Perhaps they're built without libusb support - I might have to figure out how to dig out the spec file from the rpm and see.
Regards, Rodney
Perhaps it's time to split off a version for Linux and perhaps call it CLiPS (Common Linux integrated Printing Service). :-) -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Rodney, On 16.07.2014 15:30, Rodney Baker wrote:
I might have to figure out how to dig out the spec file from the rpm and see.
To get to the spec file, you have to install the corresponding source rpm (.srpm) Installation of that should copy the contents to ~/rpmbuild and you should find the spec in ~/rpmbuild/SPECS Regards mararm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/16/2014 10:29 AM, mararm wrote:
Hi Rodney,
On 16.07.2014 15:30, Rodney Baker wrote:
I might have to figure out how to dig out the spec file from the rpm and see.
To get to the spec file, you have to install the corresponding source rpm (.srpm) Installation of that should copy the contents to ~/rpmbuild and you should find the spec in ~/rpmbuild/SPECS
Regards mararm
or just: rpm2cpio rpmname.rpm | cpio -idmv specfile.spec if you don't know the specfile name, then you can get it by the 'spec' extension with: for i in $(rpm -qpl rpmname.rpm); do \ test ${i##*.} = "spec" && rpm2cpio rpmname.rpm | cpio -idmv "$i" \ done -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/16/2014 02:11 PM, David C. Rankin pecked at the keyboard and wrote:
On 07/16/2014 10:29 AM, mararm wrote:
Hi Rodney,
On 16.07.2014 15:30, Rodney Baker wrote:
I might have to figure out how to dig out the spec file from the rpm and see.
To get to the spec file, you have to install the corresponding source rpm (.srpm) Installation of that should copy the contents to ~/rpmbuild and you should find the spec in ~/rpmbuild/SPECS
Regards mararm
or just:
rpm2cpio rpmname.rpm | cpio -idmv specfile.spec
if you don't know the specfile name, then you can get it by the 'spec' extension with:
for i in $(rpm -qpl rpmname.rpm); do \ test ${i##*.} = "spec" && rpm2cpio rpmname.rpm | cpio -idmv "$i" \ done
Or use mc to extract the spec file. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-16 21:17 (GMT-0400) Ken Schneider - openSUSE composed:
David C. Rankin wrote:
rpm2cpio rpmname.rpm | cpio -idmv specfile.spec
if you don't know the specfile name, then you can get it by the 'spec' extension with:
for i in $(rpm -qpl rpmname.rpm); do \ test ${i##*.} = "spec" && rpm2cpio rpmname.rpm | cpio -idmv "$i" \ done
Or use mc to extract the spec file.
Near infinitely simpler, particularly when all you want is a few words or lines from a contained text file, which you can locate and copy out with MC's editor for pasting elsewhere in less than the time it takes to simply consider using rpm2cpio/for/test/cpio et al. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 16 Jul 2014 21:43:30 Felix Miata wrote:
On 2014-07-16 21:17 (GMT-0400) Ken Schneider - openSUSE composed:
David C. Rankin wrote:
rpm2cpio rpmname.rpm | cpio -idmv specfile.spec
if you don't know the specfile name, then you can get it by the 'spec' extension with:
for i in $(rpm -qpl rpmname.rpm); do \ test ${i##*.} = "spec" && rpm2cpio rpmname.rpm | cpio -idmv "$i" \ done
Or use mc to extract the spec file.
Near infinitely simpler, particularly when all you want is a few words or lines from a contained text file, which you can locate and copy out with MC's editor for pasting elsewhere in less than the time it takes to simply consider using rpm2cpio/for/test/cpio et al.
All good info. Thanks, guys. Esp. re MC - that is one tool that I haven't played with nearly enough (haven't really felt the need), although I remember its Norton Commander counterpart from the DOS (and i think even OS/2) days, not to mention the venerable xtree gold... -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/16/14 12:31, Rodney Baker wrote:
Hi all. I note that the latest version of cups in any of the official repositories is version 1.5.4, but the latest version available from cups.org is 1.7.4.
According to the cups.org release notes, 1.7.4 includes many fixes including at least one security related fix. Is anyone working on packaging 1.7.4 for openSuSE?
You may want to look at https://en.opensuse.org/Portal:Printing, section "Work in Progress" And also https://bugzilla.novell.com/show_bug.cgi?id=735404 "CUPS >= 1.6 has major incompatible changes. Do not use CUPS >= 1.6 on production systems!" for the reasons *why* new newest official version is 1.5.4. Basically, our CUPS Apple overlords removed many of the non-OS-X features from CUPS core distribution that Linux depended on. Be careful, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 16 Jul 2014 15:29:19 Joachim Schrod wrote:
[...]
You may want to look at https://en.opensuse.org/Portal:Printing, section "Work in Progress"
And also https://bugzilla.novell.com/show_bug.cgi?id=735404 "CUPS >= 1.6 has major incompatible changes. Do not use CUPS >= 1.6 on production systems!"
for the reasons *why* new newest official version is 1.5.4. Basically, our CUPS Apple overlords removed many of the non-OS-X features from CUPS core distribution that Linux depended on.
Be careful,
Joachim
Thanks, Joachim. Hmmm - Ken's idea starts to sound like good one. Sounds like the Common UNIX Printing System is not so common any more... -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16 July 2014 15:19, Rodney Baker <rodney.baker@iinet.net.au> wrote:
for the reasons *why* new newest official version is 1.5.4. Basically, our CUPS Apple overlords removed many of the non-OS-X features from CUPS core distribution that Linux depended on.
Thanks, Joachim. Hmmm - Ken's idea starts to sound like good one. Sounds like the Common UNIX Printing System is not so common any more...
It's a complicated situation, so far the OpenPrinting group managed to come up with solutions for all the bits Apple is removing, but eventually they will remove stuff we can't replace. Apple obviously have an interest in new features in CUPS, and as they control the entire OS and wrap CUPS in their own API they are free to dump stuff they no longer need. They also don't backport bug fixes much to earlier versions that distros still use. Linux distros however have to be concerned about legacy support, etc. For example, the widely used Qt4 toolkit only supports CUPS 1.2 and is feature frozen so cannot be upgraded to the new CUPS 1.6 way of doing things. They found a way around that (browserd) but that solution took a while to materialise and missed the openSUSE 13.1 window. Longer term, Red Hat does have a contingency plan for the day when Apple does something that cannot be worked around, but trying to maintain a separate print system with support for tens of thousands of printers is hard work, and sharing that system with Apple at least ensures hardware manufactures take more of an interest in writing drivers. The future is with driverless printing using IPP, but it will be years before everyone has a printer capable of that so we need the legacy support. Basically the plan is to replace the print spooler with something modern, but keep the CUPS hardware backend. Ideally the Linux Foundation's Core Infrastructure Initiative would spend some money on LTS for older Cups versions and pay towards any future new spooler, but don't hold your breath, printing is decidedly non-sexy and struggles to attract funding or attention. John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/16/2014 09:19 AM, Rodney Baker wrote:
On Wed, 16 Jul 2014 15:29:19 Joachim Schrod wrote:
[...]
You may want to look at https://en.opensuse.org/Portal:Printing, section "Work in Progress"
And also https://bugzilla.novell.com/show_bug.cgi?id=735404 "CUPS >= 1.6 has major incompatible changes. Do not use CUPS >= 1.6 on production systems!"
for the reasons *why* new newest official version is 1.5.4. Basically, our CUPS Apple overlords removed many of the non-OS-X features from CUPS core distribution that Linux depended on.
Be careful,
Joachim
Thanks, Joachim. Hmmm - Ken's idea starts to sound like good one. Sounds like the Common UNIX Printing System is not so common any more...
Rodney, Take a look at the Archlinux cups package. I'm running cups 1.7.3-4 on my server at work, so they obviously solved the issues somehow. See: https://www.archlinux.org/packages/extra/i686/cups/ https://wiki.archlinux.org/index.php/CUPS -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/16/2014 09:19 AM, Rodney Baker wrote:
On Wed, 16 Jul 2014 15:29:19 Joachim Schrod wrote:
[...]
You may want to look at https://en.opensuse.org/Portal:Printing, section "Work in Progress"
And also https://bugzilla.novell.com/show_bug.cgi?id=735404 "CUPS >= 1.6 has major incompatible changes. Do not use CUPS >= 1.6 on production systems!"
for the reasons *why* new newest official version is 1.5.4. Basically, our CUPS Apple overlords removed many of the non-OS-X features from CUPS core distribution that Linux depended on.
Be careful,
Joachim
Thanks, Joachim. Hmmm - Ken's idea starts to sound like good one. Sounds
On Wed, 16 Jul 2014 13:17:46 David C. Rankin wrote: like
the Common UNIX Printing System is not so common any more...
Rodney,
Take a look at the Archlinux cups package. I'm running cups 1.7.3-4 on my server at work, so they obviously solved the issues somehow.
See:
Thanks, David and John. Yes, I found Johannes' repository and tried 1.7.3 from there, along with cups-browsed and cups-filters, but because the config options are now split betweeen cupsd and cups-browsed (at least, I'm assuming that's the cause) it broke printing via samba (although local printing, even using cups-pdf, still worked). That's probably solvable, but I ran out of time to try to troubleshoot that, so I've reverted to 1.5.4 until such time as I can get the config sorted. I note to that in 1.6/1.7 support for pushing Windows drivers to clients is deprecated and no longer supported (not a big deal for a small home network, which I run as a domain a) because I can and b) as a learning exercise0 but probably not great if you're maintaining a large network with a large number of Windows workstations. Thanks for everyone's suggestions and help; I'll do more playing when next i have time. :) -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16 July 2014 11:31, Rodney Baker <rodney.baker@iinet.net.au> wrote:
Hi all. I note that the latest version of cups in any of the official repositories is version 1.5.4, but the latest version available from cups.org is 1.7.4.
According to the cups.org release notes, 1.7.4 includes many fixes including at least one security related fix. Is anyone working on packaging 1.7.4 for openSuSE?
I would do it myself via the build service but every time I've tried to do that has ended in abject failure. I obviously have no idea what I'm doing there...
Per the bug report at https://bugzilla.novell.com/show_bug.cgi?id=735404 :
Johannes Meixner 2014-06-26 09:29:50 UTC
FYI:
CUPS 1.7.3 is available from OBS home project "home:jsmeix".
cups-filters 1.0.54 is available from OBS devel project "Printing".
They are not thoroughly tested by me.
Check the RPM changelog entries for basic information.
Regarding packages from "home:jsmeix" and "Printing" read https://build.opensuse.org/project/show?project=home%3Ajsmeix and https://build.opensuse.org/project/show/Printing
Cheers! John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
David C. Rankin -
Felix Miata -
Joachim Schrod -
John Layt -
Ken Schneider - openSUSE -
mararm -
Rodney Baker -
Werner Flamme