Arch Linux

Ascyii

Member

Registered: 2024-01-18

Posts: 6

[SOLVED] Installing rpm package with PKGBUILD | Adding ipp printer

Hi, I have the following problem:
Mainly I want to get my Canon MAXIFY GX6050 printer to work with cups. On my journey through various error messages and many visited forums, I got the idea to install the IJ Printer Driver v. 6.20 for Linux (rpm) from the Canon website.
I have no idea if this will solve my problem, but I see no other way.

Now to the current problem I have:
In order to install an rpm package, I created a PKGBUILD file for installation using pacman.

# Metadata; be sure to set this to reasonable values to not confuse your
# package manager or cause name conflicts with the repositories.
pkgname="cnijfilter2"
pkgver="0.0.1"
pkgrel="1"
pkgdesc="Short description of rpm package"
arch=("x86_64")

# The RPM file you want to install; place in the same directory as this file.
source=("cnijfilter2.rpm")

# Assuming you're not going to push this to AUR or whatever, you can just skip
# the integrity check here. Otherwise, replace SKIP with the output of
# "sha -a 256 filename.rpm".
sha256sums=("SKIP")

package() {
  # Copy all directories from $srcdir into $pkgdir. $srcdir will already have
  # been populated with the contents of package.rpm, but it also contains a
  # symlink to it, which we don't want to copy; anything in $pkgdir after this
  # command will be installed to your root directory.
  find $srcdir/ -mindepth 1 -maxdepth 1 -type d | xargs cp -r -t "$pkgdir"
}

Now I get this error when installing with 'makepkg -i'

loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) cnijfilter2-0.0.1-1

Total Installed Size:  13.51 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [##################] 100%
(1/1) checking package integrity                   [##################] 100%
(1/1) loading package files                        [##################] 100%
(1/1) checking for file conflicts                  [##################] 100%
error: failed to commit transaction (conflicting files)
cnijfilter2: /usr/lib64 exists in filesystem (owned by filesystem)
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).

If anyone could help me with either getting the Canon printer to work or installing the rpm package I would be very grateful

Last edited by Ascyii (2024-05-24 20:51:11)

Tétrapyle

Member

Registered: 2014-01-03

Posts: 61

Re: [SOLVED] Installing rpm package with PKGBUILD | Adding ipp printer

Where did you copy your PKGBUILD template from?

Edit: Have you tried with Airprint (and CUPS)? According to Canon, after selecting Mac OS: This product is compatible with the operating system selected using AirPrint only - a driver is not required.

Last edited by Tétrapyle (2024-05-24 15:07:29)

Ascyii

Member

Registered: 2024-01-18

Posts: 6

Re: [SOLVED] Installing rpm package with PKGBUILD | Adding ipp printer

Where did you copy your PKGBUILD template from?

I got it from Stack Exchange: https://unix.stackexchange.com/question … arch-linux. I've never created my own PKGBUILD, so I don't actually know what I'm doing. (One should never do something they have no idea about, but I was in a hurry. )

Edit: Have you tried with Airprint (and CUPS)? According to Canon, after selecting Mac OS: This product is compatible with the operating system selected using AirPrint only - a driver is not required.

Now I just added my printer as an IPP printer, and guess what—it works! CUPS still complains that "Unable to set color space/depth for Raster output!", but as long as everything works, I will not complain.

But I'm still interested in why the PKGBUILD failed if someone can help me out.

loqs

Member

Registered: 2014-03-06

Posts: 18,911

Re: [SOLVED] Installing rpm package with PKGBUILD | Adding ipp printer

cnijfilter2: /usr/lib64 exists in filesystem (owned by filesystem)

The path would need to be adjusted from /usr/lib64 to /usr/lib.  /usr/lib64 is a symlink to /usr/lib provided by the filesystem package.  pacman does not follow symlinks hence the need for the path adjustments in the PKGBUILD.

Last edited by loqs (2024-05-24 18:44:52)