Bug#794301: [Pkg-fedora-ds-maintainers] Bug#794301: 389-console: missing bogus dependency
The console depends on the directory server, which does not depend on systemd, but still acts as if it does. And since the directory server conflicts with slapd, and I need a ldap server to test the ldap client, and I need a ldap client to verify and test the server before moving it from my test machine, and . . . On Mon, Aug 10, 2015 at 1:28 AM, Timo Aaltonen tjaal...@debian.org wrote: On 01.08.2015 05:12, Ben Hildred wrote: Package: 389-console Version: 1.1.7-2 Severity: serious Justification: Policy 9.11 386-ds assumes systemd but does not include it in its list of dependencies. Further why does a ldap browser need to depend on init? [15/07/31:19:15:16] - [Setup] Info Error: command '/bin/systemctl --system daemon-reload' failed - output [] error [No such file or directory][15/07/31:19:15:16] - [Setup] Fatal Error: Could not create directory server instance 'crystal'. This comes from setting up the directory server, you're not trying to use 389-console here.. -- -- Ben Hildred Automation Support Services 303 815 6721
Bug#794301: [Pkg-fedora-ds-maintainers] Bug#794301: Bug#794301: 389-console: missing bogus dependency
reassign 794301 389-ds-base thanks On 10.08.2015 22:47, Ben Hildred wrote: The console depends on the directory server, which does not depend on systemd, but still acts as if it does. And since the directory server conflicts with slapd, and I need a ldap server to test the ldap client, and I need a ldap client to verify and test the server before moving it from my test machine, and . . . 389-console does not depend on 389-ds-base: Package: 389-console Priority: extra Section: universe/java Installed-Size: 104 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian 389ds Team pkg-fedora-ds-maintain...@lists.alioth.debian.org Architecture: all Version: 1.1.7-2 Depends: libidm-console-framework-java original issue remains, 389-ds-base needs to depend on systemd apparently. -- t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794301: [Pkg-fedora-ds-maintainers] Bug#794301: Bug#794301: 389-console: missing bogus dependency
On 11.08.2015 05:43, Ben Hildred wrote: On Mon, Aug 10, 2015 at 8:30 PM, Timo Aaltonen tjaal...@debian.org mailto:tjaal...@debian.org wrote: reassign 794301 389-ds-base thanks On 10.08.2015 22:47, Ben Hildred wrote: The console depends on the directory server, which does not depend on systemd, but still acts as if it does. And since the directory server conflicts with slapd, and I need a ldap server to test the ldap client, and I need a ldap client to verify and test the server before moving it from my test machine, and . . . 389-console does not depend on 389-ds-base: oops, got it confused with the admin console (two consoles is kinda confusing). 389-admin-console depends on 389-admin. Probably could relax that then. original issue remains, 389-ds-base needs to depend on systemd apparently. Or better yet not depend on systemd, per policy. The policy says that sysvinit needs to be supported, which is true in this case (initscript provided). Plenty of packages depend on systemd the package, not systemd-sysv. -- t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794301: [Pkg-fedora-ds-maintainers] Bug#794301: 389-console: missing bogus dependency
On 01.08.2015 05:12, Ben Hildred wrote: Package: 389-console Version: 1.1.7-2 Severity: serious Justification: Policy 9.11 386-ds assumes systemd but does not include it in its list of dependencies. Further why does a ldap browser need to depend on init? [15/07/31:19:15:16] - [Setup] Info Error: command '/bin/systemctl --system daemon-reload' failed - output [] error [No such file or directory][15/07/31:19:15:16] - [Setup] Fatal Error: Could not create directory server instance 'crystal'. This comes from setting up the directory server, you're not trying to use 389-console here.. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794301: 389-console: missing bogus dependency
Package: 389-console Version: 1.1.7-2 Severity: serious Justification: Policy 9.11 386-ds assumes systemd but does not include it in its list of dependencies. Further why does a ldap browser need to depend on init? [15/07/31:19:15:16] - [Setup] Info Error: command '/bin/systemctl --system daemon-reload' failed - output [] error [No such file or directory][15/07/31:19:15:16] - [Setup] Fatal Error: Could not create directory server instance 'crystal'. -- System Information: Debian Release: stretch/sid APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages 389-console depends on: ii libidm-console-framework-java 1.1.7-2 389-console recommends no packages. 389-console suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
