Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 9:32 PM Greg Wooledge  wrote:
>
> On Wed, Jul 20, 2022 at 09:12:51PM -0500, Igor Korot wrote:
> > And those are what was made on Debian with the same Makefile.am:
>
> OK!
>
> [...]
> > /bin/bash ../libtool  --tag=CXX   --mode=link g++ -I../../dbinterface
> > -DUNICODE -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -L../dbinterface
> > -ldbinterface `odbc_config --libs` -lodbcinst   -o libodbc_lib.la
> > -rpath /usr/local/lib libodbc_lib_la-database_odbc.lo
> > /bin/bash: line 1: odbc_config: command not found
> > /bin/bash: line 1: odbc_config: command not found
>
> You're missing -lodbc here.  Presumably that should have come from
> your backtick command, which obviously failed, because it's not the
> correct command substitution for this platform.

Do you mean to say that the backticks are not supported on Debian?
Or that there is no odbc_config installed when it should?

>
> You either need to find a command substitution that works on ALL of your
> platforms, or you need to put something in ./configure which tries
> all known commands and selects the one that appears to work, or else you
> need to just throw all the commands into one big ugly horrible linker
> invocation, something like:
>
>   ../libtool --tag=CXX --mode=link g++ ... \
> $(odbc_config --libs 2>/dev/null) \
> $(pkg-config --libs whatever 2>/dev/null) \

That's definitely ugly.

> ...
>
> Or ask an ODBC developers' support channel how you're supposed to do it
> on all the platforms you wish to support.

The way to do it is by using odbc_config.
I already asked and that's why I'm using it.

>
> > As you can see the build succeeded.
> >
> > But after running "make install" trying to load that library will fail
> > because the library
> > libodbc.so will not be found.
>
> I believe that's caused by the missing -lodbc linker argument.  But please
> bear in mind that I haven't done serious C development work in many years,
> and I've never worked with ODBC in this way before.

You are presumably right.
Trouble is - I'm doing it correctly and it's Debian who is at fault
(see above)..

Now, it is possible that odbc_config is just called pkg-config where available
or vice versa.
But the official way from upstream is to use odbc_config.

Thank you.


>



Re: odbc_config missing

2022-07-20 Thread Greg Wooledge
On Wed, Jul 20, 2022 at 09:12:51PM -0500, Igor Korot wrote:
> And those are what was made on Debian with the same Makefile.am:

OK!

[...]
> /bin/bash ../libtool  --tag=CXX   --mode=link g++ -I../../dbinterface
> -DUNICODE -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -L../dbinterface
> -ldbinterface `odbc_config --libs` -lodbcinst   -o libodbc_lib.la
> -rpath /usr/local/lib libodbc_lib_la-database_odbc.lo
> /bin/bash: line 1: odbc_config: command not found
> /bin/bash: line 1: odbc_config: command not found

You're missing -lodbc here.  Presumably that should have come from
your backtick command, which obviously failed, because it's not the
correct command substitution for this platform.

You either need to find a command substitution that works on ALL of your
platforms, or you need to put something in ./configure which tries
all known commands and selects the one that appears to work, or else you
need to just throw all the commands into one big ugly horrible linker
invocation, something like:

  ../libtool --tag=CXX --mode=link g++ ... \
$(odbc_config --libs 2>/dev/null) \
$(pkg-config --libs whatever 2>/dev/null) \
...

Or ask an ODBC developers' support channel how you're supposed to do it
on all the platforms you wish to support.

> As you can see the build succeeded.
> 
> But after running "make install" trying to load that library will fail
> because the library
> libodbc.so will not be found.

I believe that's caused by the missing -lodbc linker argument.  But please
bear in mind that I haven't done serious C development work in many years,
and I've never worked with ODBC in this way before.



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 7:55 PM Greg Wooledge  wrote:
>
> On Wed, Jul 20, 2022 at 07:46:43PM -0500, Igor Korot wrote:
> > On Wed, Jul 20, 2022 at 7:28 PM Greg Wooledge  wrote:
> > > Can you show us the linker command that you ran, and its error message?
> >
> > This is the command generated on Gentoo:
>
> How is that relevant to DEBIAN?

Because I'm comparing the output of 2 "-config" files.
I sent the output the Debian generated. Sorry for the delay.
Debian is set on the VM.

>
> > [code]
> > /bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
> > -I/home/igor/dbhandler/libodbc -I..-I../../dbinterface -DUNICODE
> > -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -MT
> [...]
>
> That's all noise as far as Debian is concerned.
>
> > with the following Makefile.am:
> >
> > [code]
> > ## Process this file with automake to produce Makefile.in
> >
> >
> > lib_LTLIBRARIES =  \
> > libodbc_lib.la
> >
> > libodbc_lib_la_SOURCES =  \
> > database_odbc.cpp \
> > database_odbc.h
> >
> > libodbc_lib_la_CXXFLAGS = -I../../dbinterface \
> > -DUNICODE \
> > -DUNIXODBC \
> > -I`odbc_config \
> > --cflags`
> >
> > libodbc_lib_la_LDFLAGS = -L../dbinterface \
> > -ldbinterface \
> > `odbc_config \
> > --libs` \
> > -lodbcinst
> > [/code]
>
> It looks like you've made some false assumptions about this library.
> Apparently it has different linker options and library filenames on
> different platforms, and moreover, different *means of learning those
> names*.

Don't make any presumption.
Just check what Debian is generating.

>
> Sounds like a real bitch to work with.  Oh right, it's ODBC, so it's
> always going to be horrible, isn't it.

Why?
It's still going to be libodbc.so and libodbcinst.so, isn't it?

Thank you.

>
> Good luck!
>



Re: odbc_config missing

2022-07-20 Thread Igor Korot
And those are what was made on Debian with the same Makefile.am:

/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H
-I. -I../../libodbc -I..-I../../dbinterface -DUNICODE -DUNIXODBC
-I`odbc_config --cflags`  -g -O0 -MT libodbc_lib_la-database_odbc.lo
-MD -MP -MF .deps/libodbc_lib_la-database_odbc.Tpo -c -o
libodbc_lib_la-database_odbc.lo `test -f 'database_odbc.cpp' || echo
'../../libodbc/'`database_odbc.cpp
/bin/bash: line 1: odbc_config: command not found
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../libodbc -I..
-I../../dbinterface -DUNICODE -DUNIXODBC -I -g -O0 -MT
libodbc_lib_la-database_odbc.lo -MD -MP -MF
.deps/libodbc_lib_la-database_odbc.Tpo -c
../../libodbc/database_odbc.cpp  -fPIC -DPIC -o
.libs/libodbc_lib_la-database_odbc.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../libodbc -I..
-I../../dbinterface -DUNICODE -DUNIXODBC -I -g -O0 -MT
libodbc_lib_la-database_odbc.lo -MD -MP -MF
.deps/libodbc_lib_la-database_odbc.Tpo -c
../../libodbc/database_odbc.cpp -o libodbc_lib_la-database_odbc.o
>/dev/null 2>&1
mv -f .deps/libodbc_lib_la-database_odbc.Tpo
.deps/libodbc_lib_la-database_odbc.Plo
/bin/bash ../libtool  --tag=CXX   --mode=link g++ -I../../dbinterface
-DUNICODE -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -L../dbinterface
-ldbinterface `odbc_config --libs` -lodbcinst   -o libodbc_lib.la
-rpath /usr/local/lib libodbc_lib_la-database_odbc.lo
/bin/bash: line 1: odbc_config: command not found
/bin/bash: line 1: odbc_config: command not found
libtool: link: g++  -fPIC -DPIC -shared -nostdlib
/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/crti.o
/usr/lib/gcc/x86_64-linux-gnu/10/crtbeginS.o
.libs/libodbc_lib_la-database_odbc.o   -L../dbinterface -ldbinterface
-lodbcinst -L/usr/lib/gcc/x86_64-linux-gnu/10
-L/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib
-L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu
-L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/10/../../.. -lstdc++
-lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/10/crtendS.o
/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/crtn.o  -g
-O0   -Wl,-soname -Wl,libodbc_lib.so.0 -o .libs/libodbc_lib.so.0.0.0
libtool: link: (cd ".libs" && rm -f "libodbc_lib.so.0" && ln -s
"libodbc_lib.so.0.0.0" "libodbc_lib.so.0")
libtool: link: (cd ".libs" && rm -f "libodbc_lib.so" && ln -s
"libodbc_lib.so.0.0.0" "libodbc_lib.so")
libtool: link: ar cr .libs/libodbc_lib.a  libodbc_lib_la-database_odbc.o
libtool: link: ranlib .libs/libodbc_lib.a
libtool: link: ( cd ".libs" && rm -f "libodbc_lib.la" && ln -s
"../libodbc_lib.la" "libodbc_lib.la" )
igor@debian:~/dbhandler/Debug/libodbc$

As you can see the build succeeded.

But after running "make install" trying to load that library will fail
because the library
libodbc.so will not be found.

Thank you.


On Wed, Jul 20, 2022 at 7:55 PM Greg Wooledge  wrote:
>
> On Wed, Jul 20, 2022 at 07:46:43PM -0500, Igor Korot wrote:
> > On Wed, Jul 20, 2022 at 7:28 PM Greg Wooledge  wrote:
> > > Can you show us the linker command that you ran, and its error message?
> >
> > This is the command generated on Gentoo:
>
> How is that relevant to DEBIAN?
>
> > [code]
> > /bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
> > -I/home/igor/dbhandler/libodbc -I..-I../../dbinterface -DUNICODE
> > -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -MT
> [...]
>
> That's all noise as far as Debian is concerned.
>
> > with the following Makefile.am:
> >
> > [code]
> > ## Process this file with automake to produce Makefile.in
> >
> >
> > lib_LTLIBRARIES =  \
> > libodbc_lib.la
> >
> > libodbc_lib_la_SOURCES =  \
> > database_odbc.cpp \
> > database_odbc.h
> >
> > libodbc_lib_la_CXXFLAGS = -I../../dbinterface \
> > -DUNICODE \
> > -DUNIXODBC \
> > -I`odbc_config \
> > --cflags`
> >
> > libodbc_lib_la_LDFLAGS = -L../dbinterface \
> > -ldbinterface \
> > `odbc_config \
> > --libs` \
> > -lodbcinst
> > [/code]
>
> It looks like you've made some false assumptions about this library.
> Apparently it has different linker options and library filenames on
> different platforms, and moreover, different *means of learning those
> names*.
>
> Sounds like a real bitch to work with.  Oh right, it's ODBC, so it's
> always going to be horrible, isn't it.
>
> Good luck!
>



Re: odbc_config missing

2022-07-20 Thread Greg Wooledge
On Wed, Jul 20, 2022 at 07:46:43PM -0500, Igor Korot wrote:
> On Wed, Jul 20, 2022 at 7:28 PM Greg Wooledge  wrote:
> > Can you show us the linker command that you ran, and its error message?
> 
> This is the command generated on Gentoo:

How is that relevant to DEBIAN?

> [code]
> /bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
> -I/home/igor/dbhandler/libodbc -I..-I../../dbinterface -DUNICODE
> -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -MT
[...]

That's all noise as far as Debian is concerned.

> with the following Makefile.am:
> 
> [code]
> ## Process this file with automake to produce Makefile.in
> 
> 
> lib_LTLIBRARIES =  \
> libodbc_lib.la
> 
> libodbc_lib_la_SOURCES =  \
> database_odbc.cpp \
> database_odbc.h
> 
> libodbc_lib_la_CXXFLAGS = -I../../dbinterface \
> -DUNICODE \
> -DUNIXODBC \
> -I`odbc_config \
> --cflags`
> 
> libodbc_lib_la_LDFLAGS = -L../dbinterface \
> -ldbinterface \
> `odbc_config \
> --libs` \
> -lodbcinst
> [/code]

It looks like you've made some false assumptions about this library.
Apparently it has different linker options and library filenames on
different platforms, and moreover, different *means of learning those
names*.

Sounds like a real bitch to work with.  Oh right, it's ODBC, so it's
always going to be horrible, isn't it.

Good luck!



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 7:28 PM Greg Wooledge  wrote:
>
> On Wed, Jul 20, 2022 at 07:05:28PM -0500, Igor Korot wrote:
> > Please compare:
> >
> > In Gentoo:
> >
> > [code]
> > igor@IgorReinCloud ~ $ odbc_config --libs
> > -L/usr/lib64 -lodbc
> > igor@IgorReinCloud ~ $
> > [/code]
> >
> > In Debian:
> >
> > [code]
> > igor@debian: ~ $ pkg-config --libs odbc
> > -lodbc
> > [/code]
>
> FINALLY!  SOME ACTUAL DETAILS WE CAN WORK WITH!
>
> > Not good enough. ;-)
>
> Why not?
>
> According to packages.debian.org, the libodbc.so file is in:
>
>   File  Packages
>   /usr/lib/aarch64-linux-gnu/libodbc.so unixodbc-dev [arm64]
>   /usr/lib/arm-linux-gnueabi/libodbc.so unixodbc-dev [armel]
>   /usr/lib/arm-linux-gnueabihf/libodbc.so   unixodbc-dev [armhf]
>   /usr/lib/i386-linux-gnu/libodbc.sounixodbc-dev [i386]
>   /usr/lib/mips-linux-gnu/libodbc.sounixodbc-dev [mips]
>   /usr/lib/mips64el-linux-gnuabi64/libodbc.so   unixodbc-dev [mips64el]
>   /usr/lib/mipsel-linux-gnu/libodbc.so  unixodbc-dev [mipsel]
>   /usr/lib/powerpc64le-linux-gnu/libodbc.so unixodbc-dev [ppc64el]
>   /usr/lib/s390x-linux-gnu/libodbc.so   unixodbc-dev [s390x]
>   /usr/lib/x86_64-linux-gnu/libodbc.so  unixodbc-dev [amd64]
>
> Assuming you're on amd64, the /usr/lib/x86_64-linux-gnu/ directory is
> already in the linker's search path, right?  So you don't *need*
> an extra -L option.
>
> unicorn:~$ gcc -print-search-dirs
> install: /usr/lib/gcc/x86_64-linux-gnu/10/
> programs: 
> =/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/bin/
> libraries: 
> =/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/:/lib/x86_64-linux-gnu/10/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/10/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../:/lib/:/usr/lib/
>
> It's in there.
>
> > When someone tries to build something on Debian and then
> > test it it will fail because ldd will not be able to find the library.
>
> Can you show us the linker command that you ran, and its error message?

This is the command generated on Gentoo:

[code]
/bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
-I/home/igor/dbhandler/libodbc -I..-I../../dbinterface -DUNICODE
-DUNIXODBC -I`odbc_config --cflags`  -g -O0 -MT
libodbc_lib_la-database_odbc.lo -MD -MP -MF
.deps/libodbc_lib_la-database_odbc.Tpo -c -o
libodbc_lib_la-database_odbc.lo `test -f 'database_odbc.cpp' || echo
'/home/igor/dbhandler/libodbc/'`database_odbc.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I.
-I/home/igor/dbhandler/libodbc -I.. -I../../dbinterface -DUNICODE
-DUNIXODBC -I-DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H
-DHAVE_LONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include -g -O0 -MT
libodbc_lib_la-database_odbc.lo -MD -MP -MF
.deps/libodbc_lib_la-database_odbc.Tpo -c
/home/igor/dbhandler/libodbc/database_odbc.cpp  -fPIC -DPIC -o
.libs/libodbc_lib_la-database_odbc.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I.
-I/home/igor/dbhandler/libodbc -I.. -I../../dbinterface -DUNICODE
-DUNIXODBC -I-DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H
-DHAVE_LONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include -g -O0 -MT
libodbc_lib_la-database_odbc.lo -MD -MP -MF
.deps/libodbc_lib_la-database_odbc.Tpo -c
/home/igor/dbhandler/libodbc/database_odbc.cpp -o
libodbc_lib_la-database_odbc.o >/dev/null 2>&1
mv -f .deps/libodbc_lib_la-database_odbc.Tpo
.deps/libodbc_lib_la-database_odbc.Plo
/bin/sh ../libtool  --tag=CXX   --mode=link g++ -I../../dbinterface
-DUNICODE -DUNIXODBC -I`odbc_config --cflags`  -g -O0 -L../dbinterface
-ldbinterface `odbc_config --libs` -lodbcinst   -o libodbc_lib.la
-rpath /usr/local/lib libodbc_lib_la-database_odbc.lo
libtool: link: g++  -fPIC -DPIC -shared -nostdlib
/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../lib64/crti.o
/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/crtbeginS.o
.libs/libodbc_lib_la-database_odbc.o   -L../dbinterface -ldbinterface
-L/usr/lib64 -lodbc -lodbcinst
-L/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0
-L/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../lib64
-L/lib/../lib64 -L/usr/lib/../lib64
-L/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/lib

Re: odbc_config missing

2022-07-20 Thread Greg Wooledge
On Wed, Jul 20, 2022 at 07:05:28PM -0500, Igor Korot wrote:
> Please compare:
> 
> In Gentoo:
> 
> [code]
> igor@IgorReinCloud ~ $ odbc_config --libs
> -L/usr/lib64 -lodbc
> igor@IgorReinCloud ~ $
> [/code]
> 
> In Debian:
> 
> [code]
> igor@debian: ~ $ pkg-config --libs odbc
> -lodbc
> [/code]

FINALLY!  SOME ACTUAL DETAILS WE CAN WORK WITH!

> Not good enough. ;-)

Why not?

According to packages.debian.org, the libodbc.so file is in:

  File  Packages
  /usr/lib/aarch64-linux-gnu/libodbc.so unixodbc-dev [arm64]
  /usr/lib/arm-linux-gnueabi/libodbc.so unixodbc-dev [armel]
  /usr/lib/arm-linux-gnueabihf/libodbc.so   unixodbc-dev [armhf]
  /usr/lib/i386-linux-gnu/libodbc.sounixodbc-dev [i386]
  /usr/lib/mips-linux-gnu/libodbc.sounixodbc-dev [mips]
  /usr/lib/mips64el-linux-gnuabi64/libodbc.so   unixodbc-dev [mips64el]
  /usr/lib/mipsel-linux-gnu/libodbc.so  unixodbc-dev [mipsel]
  /usr/lib/powerpc64le-linux-gnu/libodbc.so unixodbc-dev [ppc64el]
  /usr/lib/s390x-linux-gnu/libodbc.so   unixodbc-dev [s390x]
  /usr/lib/x86_64-linux-gnu/libodbc.so  unixodbc-dev [amd64] 

Assuming you're on amd64, the /usr/lib/x86_64-linux-gnu/ directory is
already in the linker's search path, right?  So you don't *need*
an extra -L option.

unicorn:~$ gcc -print-search-dirs
install: /usr/lib/gcc/x86_64-linux-gnu/10/
programs: 
=/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/bin/
libraries: 
=/usr/lib/gcc/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/10/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/:/lib/x86_64-linux-gnu/10/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/10/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/lib/:/usr/lib/gcc/x86_64-linux-gnu/10/../../../:/lib/:/usr/lib/

It's in there.

> When someone tries to build something on Debian and then
> test it it will fail because ldd will not be able to find the library.

Can you show us the linker command that you ran, and its error message?



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi, guys,

Please compare:

In Gentoo:

[code]
igor@IgorReinCloud ~ $ odbc_config --libs
-L/usr/lib64 -lodbc
igor@IgorReinCloud ~ $
[/code]

In Debian:

[code]
igor@debian: ~ $ pkg-config --libs odbc
-lodbc
[/code]

Not good enough. ;-)

When someone tries to build something on Debian and then
test it it will fail because ldd will not be able to find the library.

Thank you.

On Wed, Jul 20, 2022 at 5:28 PM David Wright  wrote:
>
> On Wed 20 Jul 2022 at 14:33:39 (-0500), Igor Korot wrote:
> > On Wed, Jul 20, 2022 at 2:04 PM Greg Wooledge  wrote:
> > > On Wed, Jul 20, 2022 at 01:48:34PM -0500, Igor Korot wrote:
> > > > This sentence from the OP:
> > > >
> > > > [quote]
> > > > I just tried to compile my program and got an error about it.
> > > > [/quote]
> > > >
> > > > shows what I'm doing (it doesn't reference unixODBC at all, does it?)
> > > > and the issue I'm facing.
> > >
> > > No.  It does not.
> > >
> > > Here are two theoretical help requests.  I would like you to compare
> > > them:
> > >
> > >
> > > The first one:
> > > =
> > > Please help me!  I'm trying to compile a program and it doesn't work!
> > > I got an error!
> > > =
> > >
> > >
> > > The second one:
> > > =
> > > Please help me!  I'm trying to compile moon-lander 1.2.  I'm following
> > > the steps in the INSTALL file, but I get this error when I type make:
> > >
> > > fred@zanzibar:~$ make
> > > bash: make: command not found
> > >
> > > What should I do?
> > > =
> > >
> > >
> > > Try to put yourself in the position of someone reading your messages.
> > > How would you react, upon reading your own message, which is almost
> > > completely devoid of any useful information?  How would you help yourself
> > > based on that message?
> > >
> > > At the very least you have to tell people what the error message says.
> > > Do you think we can see your screen?  We can't.
> >
> > How about a 3rd one?
> >
> > [quote]
> > I am a developer and I'm trying to compile my own software.
> > The software depends on unixODBC.
> > Trying to compile I got an error that odbc_config is not found.
> > [/quote]
> >
> > You are comparing apples and oranges here.
>
> You actually wrote:
>
>   I tried to run
>   pkg-config --libs unixodbc
>   and it fails.
>
> but you haven't said much about which Debian packages you have
> installed on your system, and whether you have taken any actions
> as a result of reading the URLs that have been mentioned. And,
> as I said, "it fails" is of no help.
>
> > Like I said in the OP, I'm trying to compile my own program
> > not the one that has a package in the Debian distro.
> > From the issue I would guess that the odbc_config script
> > that should tell the compiler where the include and library
> > should be searched is missing/not installed.
> >
> > My first thought would be just like Reco, to ask if the unixODBC
> > or iODBC and its development package is installed on the system.
>
> I assumed that by today, you would already have checked that.
> (I'm not sure how you would otherwise know that the file in
> question was actually missing.)
>
> But the said URLs refer to Debian bugs #422207 and #852676,
> which seem to indicate some issues between the odbc_config file
> and the Debian maintainer, so you might want to read them more
> carefully than I have. (I don't know what the issue is.)
>
> > And then ask to check for pkg-config, because as a developer
> > those are 2 things that first come to mind.
> >
> > So yes - I would help myself in that situation based on the OP message
> > I sent.
>
> Cheers,
> David.
>



Re: odbc_config missing

2022-07-20 Thread David Wright
On Wed 20 Jul 2022 at 14:33:39 (-0500), Igor Korot wrote:
> On Wed, Jul 20, 2022 at 2:04 PM Greg Wooledge  wrote:
> > On Wed, Jul 20, 2022 at 01:48:34PM -0500, Igor Korot wrote:
> > > This sentence from the OP:
> > >
> > > [quote]
> > > I just tried to compile my program and got an error about it.
> > > [/quote]
> > >
> > > shows what I'm doing (it doesn't reference unixODBC at all, does it?)
> > > and the issue I'm facing.
> >
> > No.  It does not.
> >
> > Here are two theoretical help requests.  I would like you to compare
> > them:
> >
> >
> > The first one:
> > =
> > Please help me!  I'm trying to compile a program and it doesn't work!
> > I got an error!
> > =
> >
> >
> > The second one:
> > =
> > Please help me!  I'm trying to compile moon-lander 1.2.  I'm following
> > the steps in the INSTALL file, but I get this error when I type make:
> >
> > fred@zanzibar:~$ make
> > bash: make: command not found
> >
> > What should I do?
> > =
> >
> >
> > Try to put yourself in the position of someone reading your messages.
> > How would you react, upon reading your own message, which is almost
> > completely devoid of any useful information?  How would you help yourself
> > based on that message?
> >
> > At the very least you have to tell people what the error message says.
> > Do you think we can see your screen?  We can't.
> 
> How about a 3rd one?
> 
> [quote]
> I am a developer and I'm trying to compile my own software.
> The software depends on unixODBC.
> Trying to compile I got an error that odbc_config is not found.
> [/quote]
> 
> You are comparing apples and oranges here.

You actually wrote:

  I tried to run
  pkg-config --libs unixodbc
  and it fails.

but you haven't said much about which Debian packages you have
installed on your system, and whether you have taken any actions
as a result of reading the URLs that have been mentioned. And,
as I said, "it fails" is of no help.

> Like I said in the OP, I'm trying to compile my own program
> not the one that has a package in the Debian distro.
> From the issue I would guess that the odbc_config script
> that should tell the compiler where the include and library
> should be searched is missing/not installed.
> 
> My first thought would be just like Reco, to ask if the unixODBC
> or iODBC and its development package is installed on the system.

I assumed that by today, you would already have checked that.
(I'm not sure how you would otherwise know that the file in
question was actually missing.)

But the said URLs refer to Debian bugs #422207 and #852676,
which seem to indicate some issues between the odbc_config file
and the Debian maintainer, so you might want to read them more
carefully than I have. (I don't know what the issue is.)

> And then ask to check for pkg-config, because as a developer
> those are 2 things that first come to mind.
> 
> So yes - I would help myself in that situation based on the OP message
> I sent.

Cheers,
David.



Re: odbc_config missing

2022-07-20 Thread David Wright
On Wed 20 Jul 2022 at 14:35:37 (-0500), Igor Korot wrote:
> On Wed, Jul 20, 2022 at 2:24 PM Reco  wrote:
> > On Wed, Jul 20, 2022 at 12:41:03PM -0500, Igor Korot wrote:
> > > On Wed, Jul 20, 2022 at 12:09 PM Reco  wrote:
> > > > On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> > > > > I tried to run
> > > > >
> > > > > pkg-config --libs unixodbc
> > > > >
> > > > > and it fails.
> > > >
> > > > apt install unixodbc-dev
> > >
> > > It is installed and its the latest version...
> >
> > I see the problem. What you should actually execute is:
> >
> > pkg-config --libs odbc
> >
> > Or maybe:
> >
> > pkg-config --libs odbcinst
> 
> Will try them when I get home.
> 
> But that actually means that maintaining compatibility
> between different distributions is a nightmare. ;-)
> (No offense - I'm not trying to be rude)

I wouldn't know. I just type a pkg-config command line into
a search engine, and it turned up "Guide to pkg-config -
FreeDesktop.Org" which points to:
https://people.freedesktop.org/~dbn/pkg-config-guide.html

That page says that each library comes with a .pc file,
so I looked at the Debian packages page for unixodbc-dev
and saw that there were three .pc files. Perhaps these are
the names of the libraries that are being configured (or
is it 'quizzed about their configuration').

Cheers,
David.



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 2:24 PM Reco  wrote:
>
> On Wed, Jul 20, 2022 at 12:41:03PM -0500, Igor Korot wrote:
> > Hi,
> >
> > On Wed, Jul 20, 2022 at 12:09 PM Reco  wrote:
> > >
> > > Hi.
> > >
> > > On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> > > > I tried to run
> > > >
> > > > pkg-config --libs unixodbc
> > > >
> > > > and it fails.
> > >
> > > apt install unixodbc-dev
> >
> > It is installed and its the latest version...
>
> I see the problem. What you should actually execute is:
>
> pkg-config --libs odbc
>
> Or maybe:
>
> pkg-config --libs odbcinst

Will try them when I get home.

But that actually means that maintaining compatibility
between different distributions is a nightmare. ;-)
(No offense - I'm not trying to be rude)

Thank you.

>
> I'm not that familiar with ODBC to know the difference between those.
>
> Reco
>



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 2:04 PM Greg Wooledge  wrote:
>
> On Wed, Jul 20, 2022 at 01:48:34PM -0500, Igor Korot wrote:
> > This sentence from the OP:
> >
> > [quote]
> > I just tried to compile my program and got an error about it.
> > [/quote]
> >
> > shows what I'm doing (it doesn't reference unixODBC at all, does it?)
> > and the issue I'm facing.
>
> No.  It does not.
>
> Here are two theoretical help requests.  I would like you to compare
> them:
>
>
> The first one:
> =
> Please help me!  I'm trying to compile a program and it doesn't work!
> I got an error!
> =
>
>
> The second one:
> =
> Please help me!  I'm trying to compile moon-lander 1.2.  I'm following
> the steps in the INSTALL file, but I get this error when I type make:
>
> fred@zanzibar:~$ make
> bash: make: command not found
>
> What should I do?
> =
>
>
> Try to put yourself in the position of someone reading your messages.
> How would you react, upon reading your own message, which is almost
> completely devoid of any useful information?  How would you help yourself
> based on that message?
>
> At the very least you have to tell people what the error message says.
> Do you think we can see your screen?  We can't.

How about a 3rd one?

[quote]
I am a developer and I'm trying to compile my own software.
The software depends on unixODBC.
Trying to compile I got an error that odbc_config is not found.
[/quote]

You are comparing apples and oranges here.

Like I said in the OP, I'm trying to compile my own program
not the one that has a package in the Debian distro.
>From the issue I would guess that the odbc_config script
that should tell the compiler where the include and library
should be searched is missing/not installed.

My first thought would be just like Reco, to ask if the unixODBC
or iODBC and its development package is installed on the system.

And then ask to check for pkg-config, because as a developer
those are 2 things that first come to mind.

So yes - I would help myself in that situation based on the OP message
I sent.

>



Re: odbc_config missing

2022-07-20 Thread Reco
On Wed, Jul 20, 2022 at 12:41:03PM -0500, Igor Korot wrote:
> Hi,
> 
> On Wed, Jul 20, 2022 at 12:09 PM Reco  wrote:
> >
> > Hi.
> >
> > On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> > > I tried to run
> > >
> > > pkg-config --libs unixodbc
> > >
> > > and it fails.
> >
> > apt install unixodbc-dev
> 
> It is installed and its the latest version...

I see the problem. What you should actually execute is:

pkg-config --libs odbc

Or maybe:

pkg-config --libs odbcinst

I'm not that familiar with ODBC to know the difference between those.

Reco



Re: Com deshabilitar actualitzacions automàtiques

2022-07-20 Thread Eloi

El 20/7/22 a les 10:20, Joan ha escrit:

Bones,

No sé si és possible, però m'agrada saber si es poden deshabilitar les
actualitzacions automàtiques temporalment. No em refereixo a que no
s'executin, sinó sobretot a que no es descarreguin. Bàsicament per quan
estàs tirant de dades del mòbil per servir la wifi del portàtil.


En teoria la següent configuració a apt.conf hauria de valer:

APT::Periodic::Enable "0";

En el teu cas, l'hauries d'anar posant o traient d'algun lloc sota 
/etc/apt/apt.conf.d. No sabria dir-te quin seria el lloc adequat per 
posar-ho, doncs fa temps que no remeno la configuració d'apt (jo sóc de 
l'escola de quan encara estava tot en un únic fitxer...)




Re: Processors older than Intel Pentium 4

2022-07-20 Thread Oskar Skog

> Is anyone running Debian 11 on a processor older than Pentium 4?

I'm running Debian 10 on a 400 MHz Pentium II.
512 MiB RAM and a 240 GB SSD bottlenecked by a 33 MB/s IDE interface.

So, Debian 11 hardware compatibility the same as for Debian 10?
Because I don't want to deal with a (more) broken system.


> I ask because I would like to bump 32 bit OS support from i386 (1985) 
to i686 Pentium 4 and newer.


I think others have already pointed out that increasing the requirements
of the "i386" version won't leave many CPUs that it supports that aren't
also supported by the amd64 version and x32 version.

When the x32 port becomes official, the only reason (that I can imagine)
to use the i386 port would be for really old computers.


OpenPGP_0x473CD05C78734E49.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Re: odbc_config missing

2022-07-20 Thread Greg Wooledge
On Wed, Jul 20, 2022 at 01:48:34PM -0500, Igor Korot wrote:
> This sentence from the OP:
> 
> [quote]
> I just tried to compile my program and got an error about it.
> [/quote]
> 
> shows what I'm doing (it doesn't reference unixODBC at all, does it?)
> and the issue I'm facing.

No.  It does not.

Here are two theoretical help requests.  I would like you to compare
them:


The first one:
=
Please help me!  I'm trying to compile a program and it doesn't work!
I got an error!
=


The second one:
=
Please help me!  I'm trying to compile moon-lander 1.2.  I'm following
the steps in the INSTALL file, but I get this error when I type make:

fred@zanzibar:~$ make
bash: make: command not found

What should I do?
=


Try to put yourself in the position of someone reading your messages.
How would you react, upon reading your own message, which is almost
completely devoid of any useful information?  How would you help yourself
based on that message?

At the very least you have to tell people what the error message says.
Do you think we can see your screen?  We can't.



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi, David,

On Wed, Jul 20, 2022 at 1:40 PM David Wright  wrote:
>
> On Wed 20 Jul 2022 at 12:41:03 (-0500), Igor Korot wrote:
> > On Wed, Jul 20, 2022 at 12:09 PM Reco  wrote:
> > > On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> > > > I tried to run
> > > >
> > > > pkg-config --libs unixodbc
>
> >From a position of almost complete ignorance, I would have thought
> that the software you're trying to configure is odbc, and that it
> happens to be a unixodbc implementation that's packaged as unixodbc.
>
> Package: unixodbc
> Description-md5: dbef25e3cf8e980a394982ef6927a9ca
> Description-en: Basic ODBC tools
>  UnixODBC is an implementation of the Open Database Connectivity standard,
>  a database abstraction layer that allows applications to be used with
>  many different relational databases by way of a single library.
>  .
>  This package contains isql, a command-line tool that allows SQL commands
>  to be entered interactively.
>
> Package: unixodbc-dev
> Description-md5: 810ff6350f7d3725bcea408feaf73610
> Description-en: ODBC libraries for UNIX (development files)
>  This package contains the development files (headers and libraries) for
>  unixODBC, an implementation of the Open DataBase Connectivity interface
>  for Unix systems.  You should not need to install this package unless
>  you intend to develop C language applications which use ODBC, or to
>  compile ODBC-using applications from source.
>
> > > > and it fails.
> > >
> > > apt install unixodbc-dev
> >
> > It is installed and its the latest version...
>
> BTW you could be a bit more forthcoming about what you've consulted,
> what you've done, and what output you get. Writing "got an error about
> it" and "it fails" doesn't exactly show that you're putting the work in.

This sentence from the OP:

[quote]
I just tried to compile my program and got an error about it.
[/quote]

shows what I'm doing (it doesn't reference unixODBC at all, does it?)
and the issue I'm facing.

Yes, it is about unixODBC that Debian neglects to install completely
and therefore people who want to build and run their software
on have problems with.

BTW, PostgreSQL configuration script and mySQL configuration script
are both installed and work fine. My program depends on all 3 and only unixODBC
fails.

Thank you.

>
> Cheers,
> David.
>



Re: odbc_config missing

2022-07-20 Thread David Wright
On Wed 20 Jul 2022 at 12:41:03 (-0500), Igor Korot wrote:
> On Wed, Jul 20, 2022 at 12:09 PM Reco  wrote:
> > On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> > > I tried to run
> > >
> > > pkg-config --libs unixodbc

>From a position of almost complete ignorance, I would have thought
that the software you're trying to configure is odbc, and that it
happens to be a unixodbc implementation that's packaged as unixodbc.

Package: unixodbc
Description-md5: dbef25e3cf8e980a394982ef6927a9ca
Description-en: Basic ODBC tools
 UnixODBC is an implementation of the Open Database Connectivity standard,
 a database abstraction layer that allows applications to be used with
 many different relational databases by way of a single library.
 .
 This package contains isql, a command-line tool that allows SQL commands
 to be entered interactively.

Package: unixodbc-dev
Description-md5: 810ff6350f7d3725bcea408feaf73610
Description-en: ODBC libraries for UNIX (development files)
 This package contains the development files (headers and libraries) for
 unixODBC, an implementation of the Open DataBase Connectivity interface
 for Unix systems.  You should not need to install this package unless
 you intend to develop C language applications which use ODBC, or to
 compile ODBC-using applications from source.

> > > and it fails.
> >
> > apt install unixodbc-dev
> 
> It is installed and its the latest version...

BTW you could be a bit more forthcoming about what you've consulted,
what you've done, and what output you get. Writing "got an error about
it" and "it fails" doesn't exactly show that you're putting the work in.

Cheers,
David.



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 12:09 PM Reco  wrote:
>
> Hi.
>
> On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> > I tried to run
> >
> > pkg-config --libs unixodbc
> >
> > and it fails.
>
> apt install unixodbc-dev

It is installed and its the latest version...

Thank you.

>
> Reco
>



Re: odbc_config missing

2022-07-20 Thread Reco
Hi.

On Wed, Jul 20, 2022 at 10:40:45AM -0500, Igor Korot wrote:
> I tried to run
> 
> pkg-config --libs unixodbc
> 
> and it fails.

apt install unixodbc-dev

Reco



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Wed, Jul 20, 2022 at 10:13 AM Curt  wrote:
>
> On 2022-07-20, Igor Korot  wrote:
> >
> > Apparently it IS a known problem
> >
> > This - https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/551701 -
> > claims
> > Ubuntu installs it and wants debian to follow.
> > But then someone replied that they made pkg-config file and ask others to
> > follow.
>
>
> I guess because
>
>  # This script will query 'pkg-config' for the required cflags and
>  # ldflags.
>
> https://github.com/r-dbi/odbc/blob/main/configure

I tried to run

pkg-config --libs unixodbc

and it fails.

Thank you.

>
>
> > This I don't understand at all.
> >
> > Thank you.
> >
>



Re: libvirt netwerk Was: Verbinding na update

2022-07-20 Thread hanbenes
Hallo allen,

De libvirt netwerk kwestie is opgelost middels het vinkje "automatisch starten 
bij opstarten". Aanvankelijk had ik dat vinkje verkeerd geintepreteerd.

Het met Engelstalige notificaties uitvoeren van de "stuitering" zal ik nog doen 
maar dat wordt niet eerder dan volgende week. Als daar iets wetenswaardigs uit 
komt zal ik er hier iets over schrijven.

Tot zover dank voor alle moeite.

Groet,
Han






Re: odbc_config missing

2022-07-20 Thread Curt
On 2022-07-20, Igor Korot  wrote:
>
> Apparently it IS a known problem
>
> This - https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/551701 -
> claims
> Ubuntu installs it and wants debian to follow.
> But then someone replied that they made pkg-config file and ask others to
> follow.


I guess because 

 # This script will query 'pkg-config' for the required cflags and
 # ldflags.

https://github.com/r-dbi/odbc/blob/main/configure


> This I don't understand at all.
>
> Thank you.
>



Re: odbc_config missing

2022-07-20 Thread Igor Korot
Hi,

On Tue, Jul 19, 2022, 10:18 PM David Wright 
wrote:

> On Tue 19 Jul 2022 at 21:47:06 (-0500), Igor Korot wrote:
>
> > According to unixODBC maintainers, there is a script called odbc_config.
> >
> > It looks like this script is missing in Debian.
> >
> > I just tried to compile my program and got an error about it.
> >
> > How should I handle it?
>
> By typing the filename into a search engine. As if by magic,
> someone has the same problem, and someone else supplies a copy.
>

Apparently it IS a known problem

This - https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/551701 -
claims
Ubuntu installs it and wants debian to follow.
But then someone replied that they made pkg-config file and ask others to
follow.

This I don't understand at all.

Thank you.


> Cheers,
> David.
>
>


Re: Installing on Rock Pi 4

2022-07-20 Thread Nicolas George
Stefan Monnier (12022-07-19):
> I think the issue is that "Debian support" is distinct from "Debian
> installer support".  So you may need to use some other means to install
> Debian than the official Debian installer.

The Debian *installer* has:

- an announce that this device is now supported:

https://lists.debian.org/debian-devel-announce/2021/04/msg00011.html

- files in the official repository labeled specifically for this device:

https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/firmware.rock-pi-4-rk3399.img.gz

I can be wrong, but I think it means the installer is supposed to
officially support it. Alas, the procedure described just along with the
images:

https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/README.concatenateable_images

… just does not work.

> Personally I can't remember the last time I used the Debian installer to
> install Debian.  Instead I usually rely on things like `debootstrap`
> (and for little boxes like the Rock Pi, I usually rely on third party
> tools to install a boot loader and then configure the boot loader by
> hand to load Debian's own kernel and initramfs (and occasionally compile
> my own kernel by hand when the hardware is not supported well-enough by
> the vanilla kernel)).

It is my habit too, for architectures that I know well enough. But the
boot process here is so rough, with no diagnostics, that I would have
appreciated to have something well ironed for once.

Thanks.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature


Re: Installer BoF video link - [WAS Re: Installing on Rock Pi 4]

2022-07-20 Thread Nicolas George
Andrew M.A. Cater (12022-07-20):
> > > I think it is usual practice for this kind of video to become
> > > available for viewing
> > > on demand in the near future.
> > > 
> > > My recollection of the discussion is that Gunnar's work is welcomed
> > > by the installer team. And it is hoped and expected by all parties to move
> > > towards becoming official as a next step with the passage of time.
> > > However this move is not an immediate priority, as there are other
> > > changes under discussion regarding the installer, that are currently
> > > considered to be more important.

> The installer BoF is now in the Debconf video archives at 
> https://meetings-archive.debian.net/pub/debian-meetings/2022/DebConf22/debconf22-294-debian-installer-and-images-team-bof.webm
>  and on PeerTube and YouTube.
> 
> Disclaimer: I helped with raising many of the issues there but Gunnar and his
>  awesome work are not in issue :)

Thanks.

I do not have the time to watch it in whole right now, but I could skip
over parts that were obviously about something else, and I spotted
Raspberry Pi images mentioned twice, around 21' and 41', to say that
they were still unofficial.

This is different from my issue, since, unless I am reading things
wrong, the Rock Pi 4 device is officially supported, see:

https://lists.debian.org/debian-devel-announce/2021/04/msg00011.html

# The Debian Installer team[1] is pleased to announce the first
# release candidate of the installer for Debian 11 "Bullseye".
# […]
# Hardware support changes
# 
# […]
# - Add support for ROCK Pi 4 (A,B,C).

And:

https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/

# [ ]   firmware.rock-pi-4-rk3399.img.gz2022-07-05 15:57496K

My issue is that the procedure described there:

https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/README.concatenateable_images

… just does not work.


On the other hand, I was quite interested by the talk about OEM images,
around 43': images that we copy to the boot medium like live images but
that will ask the questions and configure themselves permanently at
first boot. I think it would be very useful for my other uses.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature


Installer BoF video link - [WAS Re: Installing on Rock Pi 4]

2022-07-20 Thread Andrew M.A. Cater
On Wed, Jul 20, 2022 at 06:54:40AM +0200, Christian Britz wrote:
> Thank you, very interesting!
> 
> >> I would call it semi-official. Gunnar Wolf is a respected Debian
> >> developer and the debian.net domain is a property of the project. I
> >> would prefer an official-official installer though.
> > 
> > This was briefly touched on during a livestreamed discussion between
> > the relevant Debian developers at Debconf less than 24 hours ago.
> > I think it was this one:
> >   
> > https://debconf22.debconf.org/talks/44-debian-installer-and-images-team-bof/
> > I think it is usual practice for this kind of video to become
> > available for viewing
> > on demand in the near future.
> > 
> > My recollection of the discussion is that Gunnar's work is welcomed
> > by the installer team. And it is hoped and expected by all parties to move
> > towards becoming official as a next step with the passage of time.
> > However this move is not an immediate priority, as there are other
> > changes under discussion regarding the installer, that are currently
> > considered to be more important.
> > 
> 
> -- 
> http://www.cb-fraggle.de
>

The installer BoF is now in the Debconf video archives at 
https://meetings-archive.debian.net/pub/debian-meetings/2022/DebConf22/debconf22-294-debian-installer-and-images-team-bof.webm
 and on PeerTube and YouTube.

Disclaimer: I helped with raising many of the issues there but Gunnar and his
 awesome work are not in issue :)

All the very best, as ever,

Andy Cater 



Re: Com deshabilitar actualitzacions automàtiques

2022-07-20 Thread Narcis Garcia

Jo estic provant amb això, però encara no tinc clar si em fa cas:
sudo systemctl disable packagekit
sudo systemctl mask packagekit
sudo systemctl disable apt-daily-upgrade
sudo systemctl mask apt-daily-upgrade
sudo systemctl disable apt-daily
sudo systemctl mask apt-daily



Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 20/7/22 a les 10:20, Joan ha escrit:

Bones,

No sé si és possible, però m'agrada saber si es poden deshabilitar les
actualitzacions automàtiques temporalment. No em refereixo a que no
s'executin, sinó sobretot a que no es descarreguin. Bàsicament per quan
estàs tirant de dades del mòbil per servir la wifi del portàtil.





Re: libvirt netwerk Was: Verbinding na update

2022-07-20 Thread Paul van der Vlis

Op 20-07-2022 om 01:49 schreef hanbenes:


als root op de commandline de user ("han" waarschijnlijk) rechten geven:
adduser han libvirt



Dat kan ik gaan onderzoeken.


Je maakt hiermee de user "han" lid van de groep "libvirt", wat bepaalde 
rechten geeft. Hij zal dan niet meer om een paswoord vragen bij het 
opstarten van virt-manager.



Dan in virt-manager:
bewerken | verbinding details | virtual networks
vinkje "automatisch starten bij opstarten".


Automatisch starten bij het opstarten is niet echt de bedoeling en ook niet 
nodig voor goed functioneren is mijn ervaring.


Of ik lees het verkeerd; het start automatisch de beheerder in niet de 
verschillende machines!?


Wat hij dan doet is automatisch het virtuele netwerk starten wat nodig 
is om de virtuele machine(s) met internet te verbinden.


Hij start dus geen virtuele machine automatisch o.i.d.


( Dit schijnt ook te kunnen als root op de commandline met:
virsh net-autostart default
Maar dat heb ik nog niet geprobeerd. )


Als ik de virt mach beheerder deinstalleer en dan opnieuw installeer, blijven 
de aangemaakte machines dan staan? Worden die dan weer ingelezen?


Ja, en ja.

Ik neem aan dat je "virt-manager" bedoeld, dat is een programma waarmee 
je virtuele machines kunt aanmaken en beheren. Er zijn echter meer van 
dit soort programma's.


Een programma verwijderen en dan weer installeren zal niets veranderen, 
tenzij er iets beschadigd zou zijn aan het programma, bijvoorbeeld omdat 
je met de hand onderdelen hebt gewist. Die kans lijkt me klein.



Daarna machine rebooten en dan moet het werken.


Voor een betere oplossing heb ik de instellingen afgezocht. Bij verbinding 
details staat automatisch verbinden al ingesteld. De foutmelding bevat vast de 
sleutel naar de oplossing. Ik weet alleen niet hoe ermee aan te vangen. Als 
iemand een tip heeft, graag.

Wat ik ook nog niet weet is, of dit verband kan houden met het update 
verschijnsel in mijn oorspronkelijk bericht, of dat dat onmogelijk is. Ik heb 
die update nog eens uitgevoerd met een virtuele machine die die update nog niet 
had, en heb gekeken wat er gebeurde. De internet verbinding leek weg te zijn, 
beide pictogrammen van LAN en van VPN werden leeg en er verscheen een venster 
die melde dat een wachtwoord voor de VPN benodigd was. Als test heb ik Firefox 
een zoekopdracht gegeven en de zoekresultaten werden gevonden. Er was dus toch 
verbinding met internet. Wat was er verdwenen en wat kwam ervoor in de plaats? 
Of was er niets verdwenen en waren de pictogrammen misleidend?
In de update van de fysieke machine toen, kon Thunderbird mijn gmail niet meer 
vinden maar mijn tele2 mailadres wel. Daarna merkte ik dat video's van youtube 
of duckduck niet afspeelden, maar de site werd wel gevonden. Paul gaf de 
sugestie dat VPN voor problemen kon zorgen. Ik heb bij de VPN instellingen 
niets vreemds kunnen ontdekken.


Als het wel goed werkt zonder VPN, dan weet je dat het ergens in die VPN
moet zitten. Of weet je niet hoe die VPN uit moet?



Aan- en uitzetten van VPN is geen probleem.


Kijk dan eens of het wel goed werkt zonder VPN.


Bedenk dat die VPN-beheerders van alles kunnen doen. Misschien zetten ze
het afspelen van Youtube video's wel uit als het erg druk wordt, want
dat levert natuurlijk veel verkeer op.




Zou kunnen dat VPN beheerders dat kunnen doen. De constante is dat elke machine 
dezelfde vreemde stuitering maakt bij die ene zelfde update op hetzelfde punt, 
waarvan ik mij afvroeg wat daar nu juist mis ging.


Eigenlijk denk ik dat er niets aan de hand is.

Maar voor het geval je je toch zorgen maakt heb je aangeraden het nog 
een keer te doen, en dan Engelstalig (met LANG=C voor het commando).

En dan op de Engelstalige foutmelding te zoeken.


De vraag, of deze twee kwesties verband met elkaar kunnen houden of niet, lijkt 
me toch van belang. Is daar iets zinnigs over te zeggen?


Het lijken me verschillende kwesties.



Okee


Ik voeg nog het laatste deel van de update toe, rond de defecte koppelingsgroep 
regulatory.db

Instellen van distro-info-data (0.51+deb11u2) ...
Instellen van openssh-client (1:8.4p1-5+deb11u1) ...
Instellen van wireless-regdb (2022.04.08-2~deb11u1) ...
update-alternatives: waarschuwing: het opnieuw installeren van alternatief 
/lib/firmware/regulatory.db-debian wordt afgedwongen, omdat koppelingsgroep 
regulatory.db defect is


Ik denk dat het niet erg is. Maar als je er op wilt zoeken is het handig
om de foutmelding Engelstalig te hebben. Zie mijn vorige mail.




Okee, ik zal me nu maar eerst behelpen met de beschikbare.


Ik denk dat je daarmee niet verder zult komen. Maar uiteraard kun je ook 
op de nederlandse tekst zoeken.


Groet,
Paul



--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/



Re: Exim4 smarthost conf

2022-07-20 Thread rudu

Thank you Tixy.

Le 19/07/2022 à 20:26, Tixy a écrit :

On Tue, 2022-07-19 at 17:37 +0200, rudu wrote:

Hi,

I'm at a lost here trying to configure exim4 on a laptop running
bookworm as a smarthost relay to my email provider.
I already made it working on my desktop machine (bookworm also) on the
same local network though I had difficulties too at the time.
All I'm trying to do is to send myself a mail in a terminal.

To make it quick and with the help of the config files I found on my
desktop, I did :

# dpkg-reconfigure exim4-config    # smtpauth.provider.fr::465

Do you definitely need port 465, not 587?

Just my provider's recommendations.
And my desktop uses them just fine.





# vi /etc/exim4/passwd.client    # putting the credentials here

The steps below aren't something I've needed to do


# vi /etc/exim4/exim4.conf.localmacros    # MAIN_TLS_ENABLE = 1
# /usr/share/doc/exim4/examples/exim-gencert    # generating exim.crt
and exim.key files in /etc/exim4/

My notes for the steps I did when setting up exim are...

Install exim4, ca-certificates and s-nail.

Run 'dpkg-reconfigure exim4-config' and answer questions...

General type of mail configuration: "mail sent by smarthost; received via 
SMTP or fetchmail"
System mail name: "yxit.co.uk"
IP-addresses to listen on for incoming SMTP connections: ""
Other destinations for which mail is accepted: "home"
Machines to relay mail for: "192.168.0.0/22"
IP address or host name of the outgoing smarthost: 
"mail.myisp.co.uk::587"
Hide local mail name: "Yes"
Visible domain name for local users: "yxit.co.uk"
Keep number of DNS-queries minimal (Dial-on-Demand)? "No"
Delivery method for local mail: "Maildir format in home directory"
Split configuration into small files?: "Yes"

Edit /etc/exim4/passwd.client to add

mail.myisp.co.uk:usen...@myisp.co.uk:password
My general type of exim4 configuration is "satellite" as I just intend 
to relay the outgoing mails to my provider.

Here is my config files :
# cat /etc/exim4/update-exim4.conf.conf
[...]
dc_eximconfig_configtype='satellite'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1'
dc_readhost='mydomain.com'
dc_relay_domains='*.*'
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='smtpauth.provider.fr::465'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'

# cat /etc/exim4/passwd.client
[...]
smtpauth.provider.fr:usern...@provider.fr:password

# exim4 -v -qff
LOG: queue_run MAIN
  Start queue run: pid=6510 -qff
delivering 1oDoHK-ta-0W (queue run pid 6510)
R: smarthost for m...@mydomain.com
T: remote_smtp_smarthost for m...@mydomain.com
Transport port=25 replaced by host-specific port=465
Connecting to provider.fr [109.234.xxx.xxx]:465 ...  TFO mode sendto, no 
data: EINPROGRESS

 connected
  SMTP(closed)<<
  SMTP(close)>>
cmdlog: '(unset)'
LOG: MAIN
  H=provider.fr [109.234.xxx.xxx]: Remote host closed connection in 
response to initial connection

LOG: MAIN
  == m...@mydomain.com R=smarthost T=remote_smtp_smarthost defer (-18) 
H=provider.fr [109.234.xxx.xxx]: Remote host closed connection in 
response to initial connection

delivering 1oDorR-0001DY-1p (queue run pid 6510)
R: smarthost for m...@free.fr
T: remote_smtp_smarthost for m...@free.fr
Transport port=25 replaced by host-specific port=465
Connecting to provider.fr [109.234.xxx.xxx]:465 ...  TFO mode sendto, no 
data: EINPROGRESS

 connected    *< Hangs there for several minutes*
  SMTP(closed)<<
  SMTP(close)>>
cmdlog: '(unset)'
LOG: MAIN
  H=provider.fr [109.234.xxx.xxx]: Remote host closed connection in 
response to initial connection

LOG: MAIN
  == m...@free.fr R=smarthost T=remote_smtp_smarthost defer (-18) 
H=provider.fr [109.234.xxx.xxx]: Remote host closed connection in 
response to initial connection

LOG: queue_run MAIN
  End queue run: pid=6510 -qff

Regards
Rudu



Com deshabilitar actualitzacions automàtiques

2022-07-20 Thread Joan
Bones,

No sé si és possible, però m'agrada saber si es poden deshabilitar les
actualitzacions automàtiques temporalment. No em refereixo a que no
s'executin, sinó sobretot a que no es descarreguin. Bàsicament per quan
estàs tirant de dades del mòbil per servir la wifi del portàtil.

-- 
Joan Cervan i Andreu
http://personal.calbasi.net

"El meu paper no és transformar el món ni l'home sinó, potser, el de
ser útil, des del meu lloc, als pocs valors sense els quals un món no
val la pena viure'l" A. Camus

i pels que teniu fe:
"Déu no és la Veritat, la Veritat és Déu"
Gandhi

"Donar exemple no és la principal manera d'influir sobre els altres; és
l'única manera" Albert Einstein

“Lluitarem contra el fort mentre siguem febles i contra nosaltres
mateixos quan siguem forts” Lluís Maria Xirinacs