[Pkg-samba-maint] another upload to -exp or to unstable?

[L. van Belle]

Hai, 

> -----Oorspronkelijk bericht-----
> Van: Pkg-samba-maint 
> [mailto:pkg-samba-maint-bounces+belle=bazuin.nl at alioth-lists.d
> ebian.net] Namens Michael Tokarev
> Verzonden: donderdag 7 april 2022 11:04
> Aan: Debian Samba Maintainers
> Onderwerp: [Pkg-samba-maint] another upload to -exp or to unstable?
> 
> Hi!
> 
> At this stage, I wonder if we should continue waiting
> for the python mess, or can just go and use this mess
> for our advantage, treating current unstable like some
> sort of experimental but with much larger audience.. :)
> 
> I don't see a way for python-defaults to migrate any time
> soon, many things are waiting there.  All samba-related
> packages are okay, either current or new. So we maybe can
> upload the thing to let people to try it out... and fix
> any reported issue, if any, before whole thing is migrated.
> 
> Not sure it is fair, but heck..
> 
> Louis, I think it is okay for you to make the packages
> available on your site if you want to. I hope anyway, -
> I see no obvious issues in there.

Yes, i started yesterday evening on this and i took the packages from
experimental. 

Talloc builds, saw only 2 things..
python3-talloc.lintian-overrides
Change. 
python3-talloc: library-not-linked-against-libc
usr/lib/x86_64-linux-gnu/libpytalloc-util.cpython-*.so.* 
To
python3-talloc: library-not-linked-against-libc
usr/lib/*/libpytalloc-util.cpython-*.so.*

That saved a warning in lintian.

And this one. 
usr/include/pytalloc.h ${DEB_PY3_INCDIR} 
Wrong variable, googled my ass of that one, could not find anything on that.


I going for a full sync of my packages against debian again to takes a bit
longer then normal. 
but that will fix a few upgrade points.. 

I choosen for the following naming. 
Per example order and lets take how that now looks. 
talloc (2.3.3-3) unstable; urgency=medium

Experimental         : 2.3.3-3
Sid                  : 2.3.3-3
Testing              : 2.3.3-2
bullseye-fasttrack   : 2.3.3-3~fto11+1
bullseye-backport    : 2.3.3-2~bpo11+1
Bullseye             : 2.3.1-2

So, if i add mine builds here, i would match up with fastrack.
https://wiki.debian.org/FastTrack 

Basicly i could do the fasttrack, currently i only have 2 more rules enables
in d/rules. 
                --enable-spotlight \
                --with-profiling-data	<< added. 
On request because some people use package of me that required samba build
with it for monitoring. 
And on spotlight, i enabled these 2 packages also for a full spotlight
support. 
               libtracker-miner-2.0-dev,
               libtracker-sparql-2.0-dev

Do note, this gives more packages that will be installed aside with samba. 
Mathieu had a look at it and desiced to go for the reduces package version, 
by not adding these 2 packages in build depends. 
Maybe its better now also, i dont know..(yet). 
Also I dont know the bigger picture here, the in and out, 
so on this part i leave this to you guys. 

But adding --with-profiling-data in d/rules fixes some problems with
monitoring. 
I tried to find the mail on which package this was, but cant find it atm, 
But it was a normal debian stable package/monitoring program.
Maybe we can/should add it.
I have currently about 2000 uniq ip's using my repo, all good. 
Save to add in my opinion. 

> 
> For older systems which needs updates for tdb/talloc/tevent, -
> I think we can even make it conditional and build just
> everything from samba source directly, in a way similar
> to how ldb is built. Once we learned how to do that, it
> become easy.  I don't know if it's a good idea doing
> in general, though.

For bookworm and up yeah, thats a good idea. 
Current stable, well, thats one i'll encounter i think. 

Again, thanks for amazing work here.. 
*and offcourse, lets not forget all the work Mathieu has bedoing all these
years also. 


Greetz, 

Louis