public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Samba update rootfile
Date: Tue, 19 Apr 2022 11:22:50 +0100	[thread overview]
Message-ID: <1EFFD8C2-29D6-4FE2-91A3-1029F4B21668@ipfire.org> (raw)
In-Reply-To: <c87ccd53-0984-4da5-a806-4463f874cd53@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

Hallo Adolf,

> On 19 Apr 2022, at 11:18, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I have done an update build of samba-4.16.0 which built fine after the installation of a new dependency perl-JSON.
> 
> My question is regarding the rootfile changes shown in the samba file in the log directory. Many of the libraries now have no version number and are replaced by just a .so file
> 
> As an example libasn1-samba4 has the following removed
> -usr/lib/samba/libasn1-samba4.so.8
> -usr/lib/samba/libasn1-samba4.so.8.0.0
> 
> and replaced by
> +usr/lib/samba/libasn1-samba4.so

This is probably not a bad idea from their point of view. Those libraries don’t need to be versioned, because at a time, you can only have one version of samba installed.

So we need to ship them all.

> There is no mention of any changes to the lib files in the Whats New file in the source tarball or on the samba website that I have been able to find.
> 
> I want to be sure that this is not occurring because of some error I have made somewhere.
> 
> Attached below is the whole of the samba logfile showing the new files and the files being removed.
> 
> Regards,
> 
> Adolf.
> 
> 
> -- 
> Sent from my laptop
> <samba_log_rootfile.txt>


      reply	other threads:[~2022-04-19 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 10:18 Adolf Belka
2022-04-19 10:22 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1EFFD8C2-29D6-4FE2-91A3-1029F4B21668@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox