[sane-devel] sane-devel Digest, Vol 186, Issue 26

[Ralph Little]

Hi,

On 2020-12-20 6:53 p.m., pj.world at gmx.com wrote:
> I would like to apologize. I had had a difficult day and had some
> beverages. I went to update my computer and ran into this dependency
> issue.
>  
> I would like to start over if I may.
>  

No worries.

> ...
>   
> ~$ sudo add-apt-repository ppa:sane-project/sane-release
> You are about to add the following PPA:
>  Ubuntu SANE packages from SANE Stable Source
> (https://gitlab.com/sane-project/backends/-/releases).
> Please send scanner related questions to the SANE mailing list:
> sane-devel at alioth-lists dot debian dot net.
> If you need the more recent scanner driver from git, you can use my
> other PPA: https://launchpad.net/~sane-project/+archive/ubuntu/sane-git.
>  More info:
> https://launchpad.net/~sane-project/+archive/ubuntu/sane-release
> Press Enter to continue or Ctrl+C to cancel
> Executing: /tmp/apt-key-gpghome.jzCViHcebx/gpg.1.sh --keyserver
> hkps://keyserver.ubuntu.com:443 --recv-keys
> B5904B171A07B33815710C02DDEAC554C101175B
> gpg: key DDEAC554C101175B: "Launchpad PPA for sane-project" not changed
> gpg: Total number processed: 1
> gpg:              unchanged: 1
> gpg: invalid key resource URL '/etc/apt/trusted.gpg.d/home:pzz.gpg'
> gpg: keyblock resource '(null)': General error
> gpg: key 23E07629B9E3C9E4: 1 signature not checked due to a missing key
> gpg: key A6616109451BBBF2: 12 signatures not checked due to missing keys
> gpg: key 3B4FE6ACC0B21F32: 3 signatures not checked due to missing keys
> gpg: key D94AA3F0EFE21092: 3 signatures not checked due to missing keys
> gpg: key C8CAB6595FDFF622: 2 signatures not checked due to missing keys
> gpg: key 871920D1991BC93C: 1 signature not checked due to a missing key
> gpg: Total number processed: 8
> gpg:       skipped new keys: 8
>  
OK, it seems there are a few broken things here. I think you have a repo
from openSUSE, quite possibly to get an up-to-date sane-airscan, but
it's not all really working very well.

First off, these command lines are all very well, but I hardly ever use
them unless I have to.
If you are running a Desktop, then I would definitely check out the
"Software Sources" utility that you can find in the Administration menu.
If you are not running a desktop, let me know then we can pursue the
commands, but I prefer not to go down that road if possible :)

However, if you are, fire that up:

1) Remove the key for pzz, the one that you should see as listed as
"invalid key resource" above.
2) Remove the pzz repository

Also, it looks like you have both sane-release and sane-git repositories
there. They should be able to co-exist, but I would remove the one that
you don't require. It will just complicate things.
If you want bleeding edge SANE (that might break from time to time),
remove sane-release repository.
If you want the stable most recent release of 1.0.31, then remove the
sane-git repository.

Then when you finish with that, in a terminal do (more for paranoia):

$ sudo apt-get remove libsane1 xsane
$ sudo apt-get update
$ sudo apt-get install xsane libsane1

And it should install SANE 1.0.31

And let us know how you got on.
It might take a couple of iterations, but we will definitely get there.

Cheers,
Ralph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20201220/3c29a84d/attachment.html>