samba - Nov 2022 - Samba 4.16 and 4.17 ubuntu focal and jammy packages

Hi!

So after the todays new releases, I made available ubuntu focal
and ubuntu jammy builds of the current samba releases.  See

  http://www.corpit.ru/mjt/packages/samba/
and
  http://www.corpit.ru/mjt/packages/samba/README

These are after I uploaded samba packages in Debian. So they're
definitely not any "better" or "worse" than in Debian.

For jammy, Debian source package is being built as it is, without
any changes, so the version number is the same.

For focal, which lacks liburing, a single modification has to be
done - to remove liburing-dev from Build-Depends in d/control.
So focal packages have "focal" suffix in their revision number.

I'm not sure I will be providing focal packages in the future,
because of this change needed to be done in the source. Or maybe
I'll automate this.

Whole thing is almost automatic: after building (and maybe uploading)
a Debian package, run a script which builds it for Ubuntu and uploads
the result to the repository referenced above.

The repository is signed with my usual GPG key which I use in Debian.

Hopefully this way it will stay for some time, - I like the layout
now. after many various experiments yesterday.  This repository is
used internally by the above mentioned script which compiles packages.

The fields in the Release file might change, however.  For one, I
didn't even try the source part of the repository so far.

Let's see how it will go.

Thanks,

/mjt

On Tue, Oct 25, 2022 at 8:47 AM Michael Tokarev via samba
<samba at lists.samba.org> wrote:
> The repository is signed with my usual GPG key which I use in Debian.
Okay so I tried to find where I should look for this before asking
here, and after almost an hour I'll just ask.
Where is your GPG key located so I can test this repo? If you'd write
out the commands to import it I'd also appreciate it to confirm the
proper way I should be doing this since there seem to be multiple
ways, including some being deprecated (apt-key).

Thanks,
Ralph

25.10.2022 15:45, Michael Tokarev via samba wrote:
> Hi!
> 
> So after the todays new releases, I made available ubuntu focal
> and ubuntu jammy builds of the current samba releases.? See
..

A (small?) warning here.

Once again, I've been reminded by the issue with sssd linking with
samba libraries, and certain samba upgrades breaks sssd.

Notable, both of 4.16 and 4.17 samba breaks sssd on both Focal and
Jammy, because samba-libs now ships libndr.so.2 instead of libndr.so.1
which is expected to be found by sssd.

I've added Breaks against older sssd packages to the new samba
packages now, so you at least know about this at install time.
These Breaks aren't yet in the versions found in the repository.

It is more: samba 4.17 contains libndr soname bump again, now
from libndr.so.2 to .3, which breaks even sssd which worked with
4.16.  I fixed it in current Debian version of Samba 4.17
packages (by reverting upstream libndr soname bump for now),
but these package aren't yet available in the repository above.

This is only relevant in case you're using sssd package, notable
sssd-ipa, sssd-ad or sssd-ad-common. If not, there's nothing to
worry about.

Thanks,

/mjt

1) what's the difference between 2:4.17.2+dfsg-7 and 2:4.17.2+dfsg-2 ?

2) Doing an in place upgrade fails.

root at nc1:~# apt policy samba
samba:
 ? Installed: 2:4.15.9+dfsg-0ubuntu0.2
 ? Candidate: 2:4.15.9+dfsg-0ubuntu0.2
 ? Version table:
 ???? 2:4.17.2+dfsg-7 100
 ??????? 100 http://www.corpit.ru/mjt/packages/samba 
ubuntu-22.04-jammy/samba-4.17/ Packages
 ???? 2:4.17.2+dfsg-2 100
 ??????? 100 http://www.corpit.ru/mjt/packages/samba 
ubuntu-22.04-jammy/samba-4.17/ Packages
 ?*** 2:4.15.9+dfsg-0ubuntu0.2 500
 ??????? 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 ??????? 500 http://us.archive.ubuntu.com/ubuntu jammy-security/main 
amd64 Packages
 ??????? 100 /var/lib/dpkg/status
 ???? 2:4.15.5~dfsg-0ubuntu5 500
 ??????? 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

root at nc1:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root at nc1:~# apt install samba=2:4.17.2+dfsg-2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
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:
 ?samba : Depends: samba-common (= 2:4.17.2+dfsg-2) but 
2:4.15.9+dfsg-0ubuntu0.2 is to be installed
 ???????? Depends: samba-common-bin (= 2:4.17.2+dfsg-2) but 
2:4.15.9+dfsg-0ubuntu0.2 is to be installed
 ???????? Depends: libldb2 (>= 2:2.6.1) but 2:2.4.4-0ubuntu0.1 is to be 
installed
 ???????? Depends: libtalloc2 (>= 2.3.4~) but 2.3.3-2build1 is to be 
installed
 ???????? Depends: libtdb1 (>= 1.4.7~) but 1.4.5-2build1 is to be installed
 ???????? Depends: libtevent0 (>= 0.13.0~) but 0.11.0-1build1 is to be 
installed
 ???????? Depends: samba-libs (= 2:4.17.2+dfsg-2) but 
2:4.15.9+dfsg-0ubuntu0.2 is to be installed

Hi Michael,

I like to try your repositories but, at the moment (and I think not only 
me) all .ru Domains are hard blocked. May by it's possible to move your 
repositories to a different domain. Don't take it personal, it's not you
I don't trust.

Stefan


Am 25.10.22 um 14:45 schrieb Michael Tokarev via samba:
> Hi!
> 
> So after the todays new releases, I made available ubuntu focal
> and ubuntu jammy builds of the current samba releases.? See
> 
>  ?http://www.corpit.ru/mjt/packages/samba/
> and
>  ?http://www.corpit.ru/mjt/packages/samba/README
> 
> These are after I uploaded samba packages in Debian. So they're
> definitely not any "better" or "worse" than in Debian.
> 
> For jammy, Debian source package is being built as it is, without
> any changes, so the version number is the same.
> 
> For focal, which lacks liburing, a single modification has to be
> done - to remove liburing-dev from Build-Depends in d/control.
> So focal packages have "focal" suffix in their revision number.
> 
> I'm not sure I will be providing focal packages in the future,
> because of this change needed to be done in the source. Or maybe
> I'll automate this.
> 
> Whole thing is almost automatic: after building (and maybe uploading)
> a Debian package, run a script which builds it for Ubuntu and uploads
> the result to the repository referenced above.
> 
> The repository is signed with my usual GPG key which I use in Debian.
> 
> Hopefully this way it will stay for some time, - I like the layout
> now. after many various experiments yesterday.? This repository is
> used internally by the above mentioned script which compiles packages.
> 
> The fields in the Release file might change, however.? For one, I
> didn't even try the source part of the repository so far.
> 
> Let's see how it will go.
> 
> Thanks,
> 
> /mjt
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20221111/5876e7c8/OpenPGP_signature.sig>