Bug#926305: nis startup scripts are completely broken

2019-04-18 Thread Elimar Riesebieter
* Anton Ivanov  [2019-04-18 15:05 +0100]:

> That is not an advice.
> 
> If nscd is a required dependency, NIS should bring it in.

This is not a "must have"

> 
> Presently it is not.
> 
> Still broken

The advice is also mentioned in the changelog:

  * Drop -no-dbus from YPBINDARGS= in /etc/default/nis.
We no longer build nis with NetworkManager/D-Bus support, so setting
this option made ypbind fail to start. (Closes: #906436)

So setting "YPBINDARGS=" in /etc/default/nis should be your first step to get
nis working in buster ;-)

Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche


signature.asc
Description: PGP signature


Bug#926305: nis startup scripts are completely broken

2019-04-18 Thread Elimar Riesebieter
* Elimar Riesebieter  [2019-04-03 11:06 +0200]:

> * Anton Ivanov  [2019-04-03 09:43 +0100]:
> 
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > 
> > Startup scripts are completely broken. Something in the systemd 
> > conversion/autogeneration.
> > 
> > The ypbind binary is never started, the script goes into "backgrounded" and 
> > fails. From there
> > on the system is unusable - you cannot log in, UIDs and groups do not 
> > resolve, etc.
> > 
> > The same system operated correctly before buster upgrade and will operate 
> > correctly if
> > ypbind is invoked from the command line.
> > 
> > This looks like a pure systemd conversion issue of some sort.
> 
> At my systems installing nscd helped. As well setting "YPBINDARGS="
> in /etc/default/nis must be.

This bug should be closed as there is no response from the reporter.
As well it seems to be fixed following the advices given above,
though.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


signature.asc
Description: PGP signature


Bug#926305: nis startup scripts are completely broken

2019-04-03 Thread Elimar Riesebieter
* Anton Ivanov  [2019-04-03 09:43 +0100]:

> Package: nis
> Version: 3.17.1-3+b1
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> Startup scripts are completely broken. Something in the systemd 
> conversion/autogeneration.
> 
> The ypbind binary is never started, the script goes into "backgrounded" and 
> fails. From there
> on the system is unusable - you cannot log in, UIDs and groups do not 
> resolve, etc.
> 
> The same system operated correctly before buster upgrade and will operate 
> correctly if
> ypbind is invoked from the command line.
> 
> This looks like a pure systemd conversion issue of some sort.

At my systems installing nscd helped. As well setting "YPBINDARGS="
in /etc/default/nis must be.

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)



Bug#834298: nis: problem appears to be in invocation in /etc/init.d/nis

2018-10-17 Thread Elimar Riesebieter
* Christoph Terasa  [2018-10-17 11:56 +0200]:

> On Tue, 16 Oct 2018 14:56:57 -0600 Joe Pfeiffer 
> wrote:
> > The problem appears to be in line 172 of /etc/init.d/nis:
> > --exec ${NET}/ypbind -- $broadcast ${YPBINDARGS}
> >
> > If I execute this by hand (for my environment, which does not use
> > -broadcast and has empty YPBINDARGS), ie
> >
> > [...]
> >
> > If I delete the -- from the invocation it works.
> >
> 
> Good find, though the "--" is signaling the end of the start-stop-daemon
> options, and is not an option to ypbind. Options to the daemon (ypbind) come
> after the "--". Since your options to ypbind are empty anyway, it works in
> your case, but it might fail otherwise. This still looks like a
> bug/regression in the ypbind binary to me, not like a bug in the init.d
> script.

According to the changelog of 3.17.1-3

Drop -no-dbus from YPBINDARGS= in /etc/default/nis.
We no longer build nis with NetworkManager/D-Bus support, so setting
this option made ypbind fail to start. (Closes: #906436)

Running ypbind with no options and an empty YPBINDARGS= works here. So this bug
isn't relevant any more. Please confirm.

I am thinking about packaging

libnsl 1.2.0  
libnss_nis 3.0
ypbind-mt 
ypserv 2.5
yp-tools 4.2.2

separately to create clean packages. Whatt do you think?

libtirpc has to be updated to minimum 1.0.2 (not only in experimental!). Any co
maintaining would be great ;-) The packaging of Mark Brown aka broonie is
somewhat, h, old fashioned?  The versions are outdated. Anyway FMPOV not
maintainable.


Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)



Bug#910891: nis build against libgdbm.6 doesn't work as server on a sysvinit system

2018-10-14 Thread Elimar Riesebieter
* Elimar Riesebieter  [2018-10-12 22:12 +0200]:

> Package: nis
> Version: 3.17.1-3+b1
> Severity: serious
> Justification: 5 (f)
> 
> 
> Dear maintainer,
> 
> since 3.17.1-3+b1 nis dosn't work as server on a sysvinit system.
> 
> 3.17.1-3+b1:
> $ ldd /usr/sbin/ypbind
> 
[...] 

> 3.17.1-2:
> $ ldd /usr/sbin/ypbind
Should have been 3.17.1-1 !!

Well 3.17.1-3+b1 works now. Can't reproduce the bug playing with
different compile options so closing.

Sorry for the noise.

Elimar
-- 
.~.
/V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^


signature.asc
Description: PGP signature


Bug#910891: nis build against libgdbm.6 doesn't work as server on a sysvinit system

2018-10-12 Thread Elimar Riesebieter
Package: nis
Version: 3.17.1-3+b1
Severity: serious
Justification: 5 (f)


Dear maintainer,

since 3.17.1-3+b1 nis dosn't work as server on a sysvinit system.

3.17.1-3+b1:
$ ldd /usr/sbin/ypbind

linux-vdso.so.1 (0x7ffd9699)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7ff8ce6ff000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ff8ce6de000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7ff8ce6c5000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff8ce508000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ff8ce4fe000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff8ce2d8000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7ff8ce0b9000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7ff8cdd9d000)
/lib64/ld-linux-x86-64.so.2 (0x7ff8ce7a5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff8cdd98000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7ff8cdd76000)



3.17.1-2:
$ ldd /usr/sbin/ypbind

linux-vdso.so.1 (0x7ffd11af2000)
libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 
(0x7fd5fb4c4000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7fd5fb471000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fd5fb41d000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fd5fb30)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7fd5fb274000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd5fb253000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7fd5fb238000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5fb07b000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fd5faed7000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7fd5facce000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fd5fac5a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd5fac5)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fd5faa28000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fd5fa80b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7fd5fa4ef000)
/lib64/ld-linux-x86-64.so.2 (0x7fd5fb509000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fd5fa4e9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fd5fa2cb000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fd5fa0a3000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fd5fa088000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7fd5fa02c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5fa027000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7fd5fa005000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7fd5f9fb3000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fd5f9fa8000)

Elimar

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.71-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  hostname   3.21
ii  libc6  2.27-6
ii  libgdbm6   1.18-2
ii  libsystemd0239-10
ii  lsb-base   9.20170808
ii  make   4.2.1-1.2
ii  netbase5.4
ii  rpcbind [portmap]  0.2.3-0.6

nis recommends no packages.

Versions of packages nis suggests:
ii  nscd  2.27-6

-- Configuration Files:
/etc/ypserv.securenets changed [not included]
/var/yp/Makefile changed [not included]



Bug#328832: mol-drivers-macosx: Run Tiger with mol

2006-08-05 Thread Elimar Riesebieter
On Sat, 05 Aug 2006 the mental interface of
Aurélien GÉRÔME told:

> Hi,
> 
> On Sat, Sep 17, 2005 at 06:02:43PM +0200, Elimar Riesebieter wrote:
> > According to #328826 we need the bootx loader from
> > http://www-user.rhrk.uni-kl.de/~nissler/mol/bootx.gz to run OSX10.4
> > out of linux.
> 
> Is there somewhere by any chance the source code of this ELF file?

I don't know :(

Elimar


-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-- Linus Torvalds


pgpg6Bk8zQiFP.pgp
Description: PGP signature