Removing cups 1.5.4 to install cups 1.6.4

[phhpro]

...

[francois]

Hello fanthom. Thanks for having a look at it.

I am working linux (i.e. no .dat container) and in always fresh mode.

But you gave me an idea. I am going to save my modules and download rc1 anew. 8)

[francois]

Thanks Peter,

It seems that I wrote that last post at the same time you were filling yours. Thus I never saw it. This is what I will do. However, I may take a few days off of porteus, as I have a few other things to do.

I imagine that by minimal you mean porteus base: 000-kernel, 001-core, 002-core, 003-kde and a browser 04-firefox in the case I need to fetch some files.

[phhpro]

...

[francois]

Finally, I decided to build cups 1.7.0. Here is the problem:
I have some difficulty building the cups-filter from:
https://github.com/willysr/SlackHacks/t ... ps-filters

Under root:

Code: Select all

root@porteus: ./cups-filters.SlackBuild
...
...
chown: invalid group: ‘root:root’
root@porteus:/mnt/sda5/64bit_v30/porteus/test-cups/cups-filter# 

Under normal user:

Code: Select all

guest@porteus:~/cups-filter$ su ./cups-filters.SlackBuild
No passwd entry for user './cups-filters.SlackBuild'
guest@porteus:~/cups-filter$ ./cups-filters.SlackBuild
mkdir: cannot create directory ‘/tmp/build/package-cups-filters’: Permission denied

Any turnaround? I would like to run ./cups-filters.SlackBuild in root mode.
Thanks.

[phhpro]

...

[francois]

I imagine you are right:

Code: Select all

root@porteus:/mnt/sda5/64bit_v30/porteus/test-cups/cups-1.7# id root
uid=0(root) gid=0 groups=0

This first link of yours does not work, but the second one is really on target. Thanks a lot, I will have a try during this day.

[francois]

It seems that I got it sorted out. The difficult part was to build the cups-filters package. I should come back with the necessary cups package 1.6.x and 1.7.0 as soon as porteus 3.0 hits the road.
http://www.linuxfoundation.org/collabor ... enprinting

PDF is the standard print job format from CUPS 1.6.x on

All important desktop applications (GTK/GNOME, Qt/KDE, LibreOffice/OpenOffice.org, Firefox, Thunderbird, ...) send print jobs in PDF and not in PostScript any more by default. In addition, a complete CUPS filter chain to process print jobs in PDF is available and used.(continued)

These packages get us in the pdf era characteristic of the actual printer related packages: most packages are able to generate pdf files directly. There is no need to work with ps (postscript files) anymore.
http://www.bsmdevelopment.com/Reference ... 30002.html


Comment on cups 1.6.x and higher:

The cups package were built with the following slackbuilds:
https://github.com/willysr/SlackHacks/t ... uilds/cups
For some reason the slackbuild would not work out of the box, so I built some dependencies according to linux-from-scratch gracefully suggested by phhpro:
http://www.linuxfromscratch.org/blfs/vi ... lters.html

After playing around with cups 1.7.0, I can imagine some of the reasons that slackware is not completely ready for going 1.6.x and higher:
1.0 cups does no more support cups-filters which are supported from then on by the openprinting foundation. The slackbuild package that I found needs user root and group user root which we do not have on porteus. We have user root, but its associated group user is 0.
1.1 this has consequences on additional package building needed for cups-filters 1.0.43: poppler-0.24.4, qpdf-5.1.0 (which in turn need pcre-8.34) amongst others. At some point, you might be able to print with cups and cups-filter with your usual text editor (libreoffice ...), however the print test might fail. Here are two of the solutions to be implemented to have it going on:

1.12 qpdf building needs random number generator. Under porteus it seems that we do not have a functional random number generator which should be found into /dev/random /dev/urandom. This random number generator is needed for security reason or encryption thru qpdf.

At first glance cups 1.6.4 seems different, as it need less recent files. But it is still pdf oriented.

[Blaze]

francois,

please unpack your module holding cups-1.5.4 (prinitng.xzm?) and then run following command:

Code: Select all

ROOT=/path/folder_of_unpacked_module removepkg cups

Where /path/folder_of_unpacked_module - it's way for folder of unpacked module
Extract cups-1.7.0-x86_64-1wsr.xzm
copy contents of the folder cups-1.7.0-x86_64-1wsr to the folder 07-printing and then to build 07-printing.xzm module.

[francois]

Thanks a lot blaze. I will try that as soon as I get to have a little more control on the stability of the package that I produce.