Hi Bertrand,
I got a similar behaviour. This is probably due to dropped NetworkManager
support in the last package version by Michael Biebl. Presently I cannot
run sucessfully a plain
/usr/sbin/ypbind
in a startup script, not even in /etc/rc.local. If this is a run after
system startup, then
I can confirm this bug. I use a Debian NIS master (still on stretch)
but on a buster client, the nis service is not started during booting
# systemctl|grep nis says:
nis.service loaded active exited LSB: Start NIS client and server daemons
# journalctl
buster nis[702]: Starting NIS servic
On 8/20/18 14:40, Nuno Oliveira wrote:
> Hi Bertrand,
>
> I got a similar behaviour. This is probably due to dropped
> NetworkManager support in the last package version by Michael Biebl.
> Presently I cannot
> run sucessfully a plain
>
> /usr/sbin/ypbind
>
> in a startup script, not even in /et
ypbind is started by /etc/init.d/nis which includes this:
# Required-Start: $network $portmap $remote_fs
There's not ypbind.service or any other .service file inside the nis
package. Maybe this is a problem?
--
regards Thomas
On Mon, 20 Aug 2018 22:46:42 +0200 Thomas Lange
wrote:
>
> ypbind is started by /etc/init.d/nis which includes this:
> # Required-Start: $network $portmap $remote_fs
>
> There's not ypbind.service or any other .service file inside the nis
> package. Maybe this is a problem?
nis ships a Sy
Package: src:guile-gnome-platform
Version: 2.16.4-5
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
test -x debian/rules
mkdir -p
fteproxy 0.2.19-3 is marked for autoremoval from testing on 2018-09-26
It (build-)depends on packages with these RC bugs:
906041: python-fte: python dependencies are missing
7 matches
Mail list logo
