samba - Nov 2022 - Unable to access shares after upgrade to version 4.17.3

22.11.2022 23:02, spindles seven via samba wrote:
> Am trying to install from your repository but am failing at the first
hurdle:
> I have imported your key using:
> 
> gpg --keyserver keyring.debian.org --recv-keys
6EE195D1886E8FFB810D4324457CE0A0804465C5
btw, my key is included into debian-keyring package too.
> (don't know where that went as it didn't produce a separate file in
/usr/share/keyrings)
It went to ~/.gnupg/, - now you have to export it from there.
> but still getting:
> E: The repository 'http://www.corpit.ru/mjt/packages/samba
bullseye/samba-4.17/ InRelease' is not signed.
> So I tried putting [sign-by=/usr/share/keyrings/debian-keyring.gpg] in the
mjt.list file like this:
> deb [signed-by=/usr/share/debian-keyring.gpg]
http://www.corpit.ru/mjt/packages/samba bullseye/samba-4.17/
It is not debian-keyring.gpg it is debian-maintainers.gpg.

But please don't do that: I don't know how exactly this sign-by= works
with
keyrings having multiple keys, - should it be signed by all of them or any of
them?
> tried debian-maintainters.gpg with the same result.
Yeah.
> What am I doing wrong?
  gpg --export-key 6EE195D1886E8FFB810D4324457CE0A0804465C5 > mjt.key
  cp mjt.key /etc/apt/mjt.key (or whatever, - using /tmp is not a good idea ;)
  add signed-by=/etc/apt/mjt.key to the deb line (it is signed-by, not sign-by -
    see sources.list manpage).

Or you can extract the same key from debian-maintainers.gpg file you found
already - it's the same there and received from keyring.debian.org.

I probably should write whole thing in the README.
Ubuntu automates all this in its ppa thing nicely
(when actually using a PPA on launchpad).

/mjt

On 22 November 2022 20:46 Michael Tokarev wrote:
> 22.11.2022 23:02, spindles seven via samba wrote:
> 
> > Am trying to install from your repository but am failing at the first
hurdle:
> > I have imported your key using:
> >
> > gpg --keyserver keyring.debian.org --recv-keys
> > 6EE195D1886E8FFB810D4324457CE0A0804465C5
> 
> btw, my key is included into debian-keyring package too.
> 
> > (don't know where that went as it didn't produce a separate
file in
> > /usr/share/keyrings)
> 
> It went to ~/.gnupg/, - now you have to export it from there.
> 
> > but still getting:
> > E: The repository 'http://www.corpit.ru/mjt/packages/samba
bullseye/samba-4.17/
> InRelease' is not signed.
> 
> > So I tried putting [sign-by=/usr/share/keyrings/debian-keyring.gpg] in
the mjt.list file
> like this:
> > deb [signed-by=/usr/share/debian-keyring.gpg]
> > http://www.corpit.ru/mjt/packages/samba bullseye/samba-4.17/
> 
> It is not debian-keyring.gpg it is debian-maintainers.gpg.
> 
> But please don't do that: I don't know how exactly this sign-by=
works with keyrings
> having multiple keys, - should it be signed by all of them or any of them?
> 
> > tried debian-maintainters.gpg with the same result.
> 
> Yeah.
> 
> > What am I doing wrong?
> 
>   gpg --export-key 6EE195D1886E8FFB810D4324457CE0A0804465C5 > mjt.key
>   cp mjt.key /etc/apt/mjt.key (or whatever, - using /tmp is not a good idea
;)
>   add signed-by=/etc/apt/mjt.key to the deb line (it is signed-by, not
sign-by -
>     see sources.list manpage).
> 
> Or you can extract the same key from debian-maintainers.gpg file you found
already
> - it's the same there and received from keyring.debian.org.
> 
OK got over that problem by following the advice above, but now am getting:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ldb-tools : Depends: libldb2 (>= 1.1.5) but it is not going to be installed
             Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be
installed
 libpam-winbind : Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be
installed
 samba : Depends: python3-samba but it is not going to be installed
         Depends: samba-common-bin (= 2:4.17.3+dfsg-2~bpo11+1) but it is not
going to be installed
         Depends: libldb2 (>= 2:2.6.1) but it is not going to be installed
         Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be installed
         Depends: libtdb1 (>= 1.4.7~) but 1.4.3-1+b1 is to be installed
         Depends: libtevent0 (>= 0.13.0~) but it is not going to be installed
         Depends: samba-libs (= 2:4.17.3+dfsg-2~bpo11+1) but it is not going to
be installed
 samba-dsdb-modules : Depends: samba-libs (= 2:4.17.3+dfsg-2~bpo11+1) but it is
not going to be installed
                      Depends: libldb2 (= 2:2.6.1+samba4.17.3+dfsg-2~bpo11+1)
but it is not going to be installed
                      Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be
installed
                      Depends: libtdb1 (>= 1.4.7~) but 1.4.3-1+b1 is to be
installed
                      Depends: libtevent0 (>= 0.13.0~) but it is not going to
be installed
 samba-vfs-modules : Depends: samba-libs (= 2:4.17.3+dfsg-2~bpo11+1) but it is
not going to be installed
                     Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be
installed
                     Depends: libtdb1 (>= 1.4.7~) but 1.4.3-1+b1 is to be
installed
                     Depends: libtevent0 (>= 0.13.0~) but it is not going to
be installed
 smbclient : Depends: samba-libs (= 2:4.17.3+dfsg-2~bpo11+1) but it is not going
to be installed
             Depends: libsmbclient (>= 2:4.10.0+dfsg) but it is not going to
be installed
             Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be
installed
             Depends: libtevent0 (>= 0.13.0~) but it is not going to be
installed
 winbind : Depends: samba-common-bin (= 2:4.17.3+dfsg-2~bpo11+1) but it is not
going to be installed
           Depends: libtalloc2 (>= 2.3.4~) but 2.3.1-2+b1 is to be installed
           Depends: libtdb1 (>= 1.4.7~) but 1.4.3-1+b1 is to be installed
           Depends: libtevent0 (>= 0.13.0~) but it is not going to be
installed
           Depends: samba-libs (= 2:4.17.3+dfsg-2~bpo11+1) but it is not going
to be installed
E: Unable to correct problems, you have held broken packages.

Have tried commenting out the bullseye-backports line in /etc/apt/sources.list
but same result.    Tried adding -t bullseye/samba-4.17/ to the apt-get install
command:
root at goflex:~/samba# apt-get install -t bullseye/samba-4.17/ samba
samba-dsdb-modules samba-vfs-modules winbind libpam-winbind libnss-winbind
libpam-krb5 smbclient ldb-tools cifs-utils libnss-winbind libpam-winbind

but comes up with the error:
E: The value 'bullseye/samba-4.17/' is invalid for APT::Default-Release
as such a release is not available in the sources

How to resolve this?
> I probably should write whole thing in the README.
Yes, probably a good idea?

Thanks,
Roy