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: closed by Elimar Riesebieter (Re: Bug#926305: nis startup scripts are completely broken)

2019-04-18 Thread Anton Ivanov

Please reopen.

Advice is no replacement for a Depends in the package control file.

As shipped the package is still broken and at the reported severity - 
breaking most of the system


A.

On 18/04/2019 14:48, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the nis package:

#926305: nis startup scripts are completely broken

It has been closed by Elimar Riesebieter .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Elimar Riesebieter 
 by
replying to this email.



--
Anton R. Ivanov
https://www.kot-begemot.co.uk/



Bug#926305: nis startup scripts are completely broken

2019-04-18 Thread Anton Ivanov

That is not an advice.

If nscd is a required dependency, NIS should bring it in.

Presently it is not.

Still broken

A.

On 18/04/2019 14:43, Elimar Riesebieter wrote:

* 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


--
Anton R. Ivanov
https://www.kot-begemot.co.uk/



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-07 Thread Andreas Henriksson
Hello everyone,

Greetings from the Gothenburg BSP.

If someone is interested in modernizing the nis package
it seems like ArchLinux has native systemd units for
nis and related services so I'd suggest importing those:

https://aur.archlinux.org/packages/nis-utils/
https://www.archlinux.org/packages/core/x86_64/rpcbind/

See also https://wiki.archlinux.org/index.php/NIS

Regards,
Andreas Henriksson



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#926305: nis startup scripts are completely broken

2019-04-03 Thread Anton Ivanov
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.

-- Package-specific info:

NIS domain: home 

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  hostname   3.21
ii  libc6  2.28-8
ii  libgdbm6   1.18.1-4
ii  libsystemd0241-1
ii  lsb-base   10.2019031300
ii  make   4.2.1-1.2
ii  netbase5.6
ii  rpcbind [portmap]  1.2.5-0.3

nis recommends no packages.

Versions of packages nis suggests:
pn  nscd  

-- Configuration Files:
/etc/yp.conf changed [not included]

-- debconf information:
* nis/domain: home