samba - Feb 2020 - Provisioning fails - Codebase question

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Michael Hendricks via samba
> Verzonden: woensdag 12 februari 2020 2:36
> Aan: Rowland penny
> CC: sambalist
> Onderwerp: Re: [Samba] Provisioning fails - Codebase question
> 
> > On 2020-02-11 01:38, Rowland penny via samba wrote:
> >> On 10/02/2020 22:34, michael at chameleonoriginals.com wrote:
> >> I should have included this in the last response.? The 
> ExpressoBin v7 
> >> has a Marvell Armada 3700LP (88F3720) dual core ARM Cortex 
> A53 (arm64) 
> >> CPU, 1GB RAM.
> >> 
> >> Seeing that Samba 4.7.6 isn't working, I have stepped into 
> building 
> >> Samba from source (first attempt was 4.11.6).? After 
> identifying quite 
> >> a few dependencies not listed on Samba's own page 
> identifying Ubuntu 
> >> 18.04 dependencies, the make process seemed to go fairly well (but
> >> with quite a few warnings).? Note that I'm giving Samba 
> the benefit of 
> >> the doubt since I'm doing this on a SoC rather than a full PC
or
> >> server.
> > 
> > Which set of dependencies did you follow ?
> > On our wiki page: 
> > 
> https://wiki.samba.org/index.php/Package_Dependencies_Required
> _to_Build_Samba
> > There are two sets, an older set (that may or may not be 
> correct) or 
> > the ones that you should follow, these are under the 
> heading 'Verified 
> > Package Dependencies'
> 
> I've been following the whole process outlined at 
> https://wiki.samba.org/index.php/Build_Samba_from_Source.  Of course, 
> I've run update/upgrade.  I have already downloaded and executed the 
> bootstrap script for Ubuntu 18.04 from the page you mention.  After 
> this, ./configure starts with a large number of "NOT FOUND" 
> warnings.  I 
> traced those items down and installed them after the 
> bootstrap.  Those 
> unmentioned dependencies are included in the script I'm using 
> to create 
> and repeat the process when it fails.
> 
> >> After nearly two hours of apparent success in the compile 
> process, it 
> >> completely blows up with a huge number of
"libsamba-passdb.so:
> >> <different function names> has been removed - please update
major
> >> version"
> > No real idea about this, perhaps missing dependencies leading to 
> > something not being built.
Most probely, ( and not, i dont know everything here.).. 
But, some libs like : libsamba-passdb.so dont have numbers at the end.
Like libsamba-passdb.so.1 i see these warnings also while building. 
> 
> libsamba-passdb.so is part of the samba source downloaded for 
> the build 
> process.  The error implies (to me) that one or more of the 
> source files 
> wasn't properly updated (I'd assume libsamba-passdb.so or files it 
> depends upon) in the source package.  But I acknowledge that 
> I'm a total 
> noob at building from source.
Same here. Im a noob in buildin from sources.. 
> 
> >> I will be stepping back a few releases for the next 
> attempt, but am 
> >> wondering if you could point me to a "build from source 
> for dummies" 
> >> that doesn't fit the standard mold by speaking as if the 
> user has done 
> >> so for years?
> > 
> > Not really, I haven't built Samba for sometime, but it was 
> very simple, 
> > install the correct dependencies, run (as a normal user) 
> './configure', 
> > followed by 'make', followed by (as root) 'make
install'.
> This should 
> > lead to all of Samba being installed in /usr/local/samba
> 
> Everything is run as root (the only user on a first-boot 
> EspressoBin).  
> This is part of a bash script-package repo I'm building on 
> GitHub, which 
> will allow a total Linux noob to take an EspressoBin straight 
> out of the 
> box and then configure it as one of multiple configurations.  
> The main 
> script which installs Samba asks all of the necessary 
> questions at the 
> very beginning of the process.  It then allows the user to 
> step away for 
> a while (two-plus hours in the case of an AD DC, as it appears) as it 
> installs and configures everything via silent install, altering 
> configuration files and debconf-set-selections.  The script 
> then assigns 
> the user-entered password for root and creates a non-root 
> sudo user with 
> password.  A primary goal is to not have a single point of user 
> interaction between the initial questions and the "all done" 
> notification.
> 
> One of my goals with this script is to share my love of the 
> EspressoBin 
> and Linux with others.  I want this to allow more experienced users 
> (like me) to take advantage of the hardware.  I also want to give 
> less-advanced users the ability to poke around with the 
> EspressoBin and 
> Linux without feeling hopeless seeing all of the background 
> information 
> that is essential for installing and configuring a system and 
> software 
> like this.  The whole repo is built upon teaching users.  The scripts 
> include almost as much commentary as executable code, explaining what 
> nearly every command issued is doing and why it is needed.
> > 
> > If you want to build Samba packages, then perhaps Louis can 
> help here 
> > (when he gets time), he builds packages for the raspberrypi.
> 
> I'd love to hear from Louis.  I love the RasPi and currently 
> have eight 
#waving hi.. 

What i suggest to try, add the source line in apt also. 
Now, what might be a bit tricky.  The samba depends, IF you need to rebuild it.
And i suggest try first if it runs. 
Yes, even if you run ubuntu..  And if it runs, then start rebuilding. 

Now, i just added this to my repo, 
https://raw.githubusercontent.com/thctlo/samba4/master/get-samba-sources.sh 

The content explains enough, short version.

Pull the sources and add them in the order of building.
And show the minimal samba requirement to build it with OS supplied packages. 
or mine, even if you remove mine this still works. 

If you just : 
cd 01-talloc
apt-get build-dep talloc
apt-get source talloc -b

It already rebuilds. 

Repeat for the others.. 
And, for every *.deb you builded, add these to a folder and create a local repo
Include this and repaet it every step. 

Thats.. About this. 
mkdir $HOME/local-repo
cp *.deb $HOME/local-repo/

cd $HOME/local-repo/
apt-ftparchive packages ./ > Packages
echo "deb [trusted=yes] file://$HOME/local-repo/ ./" >
/etc/apt/sources.list.d/local.list
apt-get update

Next. 

Good luck..

Greetz, 

Louis

I had already found your work.  I abandoned your code, since the 
approach I tried within the last couple of weeks or so failed, since it 
(or my earlier work) didn't support arm64 architecture.  I'm hoping I 
just stepped away prematurely.  I have just gone from never building 
from source before to having made 40-plus attempts just within the last 
month, so have learned a lot since I first tried your code.

Cross your fingers.  I'll give this a shot.  Your email takes steps 
towards answering questions I anticipated asking once I get Samba to 
build.

If this does work, I'll need to "steal" some of your approach,
since it
breaks one of my core rules for the script I'm building.  I am making 
every effort to ask all questions within the first few minutes, and then 
let the user walk away until it has reached 100%.  I will gladly give 
you lots of credit in my repo's readme and the script itself!

Especially since you include one-of-many choices, you may want to take a 
look at whiptail.  I know it's installed by default on raspbian and 
Ubuntu (as well as many other distros).  It offers radio lists, 
checklists, yes/no among other options in terminal sessions.  You can 
take a look at my repos at https://github.com/ChameleonGeek/ (especially 
ebin-dc/kernel.sh).  I use whiptail extensively for user selection and 
inputs.  It prevents user typos and makes your scripts look more 
professional :)

I hear you work with the RasPi.  So do I.  You might like the 
EspressoBin.  The support sucks, but the hardware is sweet.  It yawns 
where the RasPi sweats, and is still less than $100 US including SD 
card.  My project is an attempt to help work around some of the shoddy 
support.  It won't do some of the things the Pi does, but does some of 
the things the Pi can't.  It blows the Pi out of the water for anything 
that requires high network <-> drive performance.

On 2020-02-12 08:05, L.P.H. van Belle via samba wrote:
> 
> #waving hi..
> 
> What i suggest to try, add the source line in apt also.
Not quite sure what you mean by this...Add additional sources to 
/etc/apt/sources...?
> Now, what might be a bit tricky.  The samba depends, IF you need to 
> rebuild it.
> And i suggest try first if it runs.
> Yes, even if you run ubuntu..  And if it runs, then start rebuilding.
> 
> Now, i just added this to my repo,
> https://raw.githubusercontent.com/thctlo/samba4/master/get-samba-sources.sh
> 
> The content explains enough, short version.
> 
> Pull the sources and add them in the order of building.
> And show the minimal samba requirement to build it with OS supplied 
> packages.
> or mine, even if you remove mine this still works.
> 
> If you just :
> cd 01-talloc
> apt-get build-dep talloc
> apt-get source talloc -b
> 
> It already rebuilds.
> 
> Repeat for the others..
> And, for every *.deb you builded, add these to a folder and create a 
> local repo
> Include this and repaet it every step.
> 
> Thats.. About this.
> mkdir $HOME/local-repo
> cp *.deb $HOME/local-repo/
> 
> cd $HOME/local-repo/
> apt-ftparchive packages ./ > Packages
> echo "deb [trusted=yes] file://$HOME/local-repo/ ./" >
> /etc/apt/sources.list.d/local.list
> apt-get update
> 
> Next.
> 
> Good luck..
> 
> Greetz,
> 
> Louis

I've tried your sources, and ran into a few errors/issues (not all 
resolved to date):
Each source directory must be owned by user _apt.  I receive permission 
denied errors if they are not owned by _apt.

As I proceed through the list of packages, I am encountering failures 
because previous builds/installs haven't been completed (necessary 
versions of packages aren't already installed or available).

For each package, I ran ./configure, make and make install, but as a 
noob at building from source, I'm stuck...
I see no indication that the package is installed, and am not finding 
any *.deb files

On 2020-02-12 18:46, Michael Hendricks via samba wrote:
> I had already found your work.  I abandoned your code, since the
> approach I tried within the last couple of weeks or so failed, since
> it (or my earlier work) didn't support arm64 architecture.  I'm
hoping
> I just stepped away prematurely.  I have just gone from never building
> from source before to having made 40-plus attempts just within the
> last month, so have learned a lot since I first tried your code.
> 
> Cross your fingers.  I'll give this a shot.  Your email takes steps
> towards answering questions I anticipated asking once I get Samba to
> build.
> 
> If this does work, I'll need to "steal" some of your
approach, since
> it breaks one of my core rules for the script I'm building.  I am
> making every effort to ask all questions within the first few minutes,
> and then let the user walk away until it has reached 100%.  I will
> gladly give you lots of credit in my repo's readme and the script
> itself!
> 
> Especially since you include one-of-many choices, you may want to take
> a look at whiptail.  I know it's installed by default on raspbian and
> Ubuntu (as well as many other distros).  It offers radio lists,
> checklists, yes/no among other options in terminal sessions.  You can
> take a look at my repos at https://github.com/ChameleonGeek/
> (especially ebin-dc/kernel.sh).  I use whiptail extensively for user
> selection and inputs.  It prevents user typos and makes your scripts
> look more professional :)
> 
> I hear you work with the RasPi.  So do I.  You might like the
> EspressoBin.  The support sucks, but the hardware is sweet.  It yawns
> where the RasPi sweats, and is still less than $100 US including SD
> card.  My project is an attempt to help work around some of the shoddy
> support.  It won't do some of the things the Pi does, but does some of
> the things the Pi can't.  It blows the Pi out of the water for
> anything that requires high network <-> drive performance.
> 
> On 2020-02-12 08:05, L.P.H. van Belle via samba wrote:
>> 
>> #waving hi..
>> 
>> What i suggest to try, add the source line in apt also.
> Not quite sure what you mean by this...Add additional sources to
> /etc/apt/sources...?
>> Now, what might be a bit tricky.  The samba depends, IF you need to 
>> rebuild it.
>> And i suggest try first if it runs.
>> Yes, even if you run ubuntu..  And if it runs, then start rebuilding.
>> 
>> Now, i just added this to my repo,
>>
https://raw.githubusercontent.com/thctlo/samba4/master/get-samba-sources.sh
>> 
>> The content explains enough, short version.
>> 
>> Pull the sources and add them in the order of building.
>> And show the minimal samba requirement to build it with OS supplied 
>> packages.
>> or mine, even if you remove mine this still works.
>> 
>> If you just :
>> cd 01-talloc
>> apt-get build-dep talloc
>> apt-get source talloc -b
>> 
>> It already rebuilds.
>> 
>> Repeat for the others..
>> And, for every *.deb you builded, add these to a folder and create a 
>> local repo
>> Include this and repaet it every step.
>> 
>> Thats.. About this.
>> mkdir $HOME/local-repo
>> cp *.deb $HOME/local-repo/
>> 
>> cd $HOME/local-repo/
>> apt-ftparchive packages ./ > Packages
>> echo "deb [trusted=yes] file://$HOME/local-repo/ ./" >
>> /etc/apt/sources.list.d/local.list
>> apt-get update
>> 
>> Next.
>> 
>> Good luck..
>> 
>> Greetz,
>> 
>> Louis