Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

2018-08-20 Thread Nuno Oliveira

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 nis starts normally, though.


Regards,

Nuno.



Bug#906436: confirm this bug

2018-08-20 Thread Thomas Lange
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 services: ypbindbinding to YP 
server...failed (backgrounded).
buster systemd[1]: Started LSB: Start NIS client and server


But ypbind is not started. I can start it manually and then
everythings works. But it's not started when rebooting the machine.
-- 
regards Thomas



Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

2018-08-20 Thread Michael Biebl
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 /etc/rc.local. If this is a run after
> system startup, then nis starts normally, though.
>

Does ypbind need the network to be up before it can start?
If so, how do you configure your network (details please, including
configuration files.)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#906436: nis

2018-08-20 Thread Thomas Lange


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



Bug#906436: nis

2018-08-20 Thread Michael Biebl
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 SysV init script which is supposed to start all necessary
daemons.
Obviously it would be much better, if the individual daemons would have
a separate, native .service file, but that's a different issue.
The nis package would need a lot of love to be a properly maintained
package. It's imho at a pretty sad state atm.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#906778: guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found)

2018-08-20 Thread Santiago Vila
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 "."
CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
set -e;   mv ./build-aux/config.guess ./build-aux/config.guess.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.guess ./build-aux/config.guess;
set -e;   mv ./build-aux/config.sub ./build-aux/config.sub.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.sub ./build-aux/config.sub;
dh_autoreconf 
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'

[... snipped ...]

Making check in glib
make[4]: Entering directory '/<>/glib/doc/glib'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in guile-gnome-glib.info guile-gnome-glib.info-[0-9] 
guile-gnome-glib.info-[0-9][0-9] guile-gnome-glib.i[0-9] 
guile-gnome-glib.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo   -I . \
 -o guile-gnome-glib.info guile-gnome-glib.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./guile-gnome-glib.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[4]: *** [Makefile:470: guile-gnome-glib.info] Error 127
make[4]: Leaving directory '/<>/glib/doc/glib'
make[3]: *** [Makefile:399: check-recursive] Error 1
make[3]: Leaving directory '/<>/glib/doc'
make[2]: *** [Makefile:513: check-recursive] Error 1
make[2]: Leaving directory '/<>/glib'
make[1]: *** [Makefile:457: check-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-gnome-platform.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.



fteproxy is marked for autoremoval from testing

2018-08-20 Thread Debian testing autoremoval watch
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