Bug#846608: shibboleth-sp2-utils: shibd.service is installed disabled, unlike init script

[Etienne Dysli-Metref]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 08/12/16 16:33, Ferenc Wágner wrote:
> Your changes look sane.  I didn't comment on this report because I 
> failed to reproduce it: installing shibboleth-sp2-utils starts and 
> enables shibd on my test system, and after a reboot it's running
> again. I guess the SysV compatibility layer hides the issue from
> me, possibly because I still have some packages installed which
> aren't essential anymore.  But I haven't found the time to dig
> deeper yet.

I managed to reproduce it on a fresh stretch install and I've also got
reports from people using my Ubuntu backports being confused after an
upgrade+reboot.

> The full Shibboleth stack is about to be removed from stretch due
> to the OpenSSL transition, which is a more pressing issue at the 
> moment.

Indeed! :O

  Etienne
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJYSYCFAAoJEDtvu5hdVFPu0nAP/R/5V8V2LHZiz+eo2M4CBeuM
qIt8IxopKb553RPUbKxZ6S8BQsjH4kwbkEgtVn9sHx8/MVoUG8yioCkqMf4x6tpR
5hlm+//AvoyBwoAmNbiat+fbMbeKCM0yT8xt+8NOL4O4uJ+7dA1/1tuF+9DketMk
obXuh4eLhXeYabSBrPpKs/9HLScJSyuyFulRJCPX1q2AmIvmdLfmp4Uw8mNfJH6q
dNU36YW7PDyWhdly5jClwn8orXhWNcn7Dao9zJfzm/FS2JSOxCzIFtJinnDOCJ/b
jtpNlLue12ewxrnYRvLX459Su5d/tXKuQ98Sddc2T1tNY2oytBhnNiJeOLF/5mGa
R3yhqhz+pMWtvJ8DfnquqwDOpPUK5IQNll2D7x80G0inhpx1JUPXn74klnSBYVOP
P9D5DRI01G86XjPMBHobV8Ij+tMREIuUPrsRTptsRTA+Fb53IUCZaYvEdK9fieBv
b9RhM9kkCGKVGZ02Ix7vGHRwuMthdGT/yOh0I43tApskabU4iOovQ++DApIJanUT
kXz9EXyffmu00dg2nHCWfaHHlA9cP6myVzbU9C18pTNbbozl0sJUgGPw6pLLpmqA
0edQVy+8l8GbxRbjEjCXrOxHADcYT2NYyADm+psKrXbw9r9RCew1m41MqrQVaWwd
uLVEdkKCRJgxHXcD/Ie4
=DrTc
-END PGP SIGNATURE-

Bug#846608: shibboleth-sp2-utils: shibd.service is installed disabled, unlike init script

[Ferenc Wágner]

Etienne Dysli-Metref  writes:

> On 05/12/16 22:36, Russ Allbery wrote:
>
>> General Debian policy is to enable all services at boot by default.
>> So yes, this is the correct approach.
>
> I managed to fix this and uploaded a new revision at
> https://mentors.debian.net/package/shibboleth-sp2. I've pushed the
> changes in branch edm/debian/master, if they are fine I'll merge them
> in debian/master. I'd be glad if either you or Ferenc could review and
> upload the package to unstable. :)

Your changes look sane.  I didn't comment on this report because I
failed to reproduce it: installing shibboleth-sp2-utils starts and
enables shibd on my test system, and after a reboot it's running again.
I guess the SysV compatibility layer hides the issue from me, possibly
because I still have some packages installed which aren't essential
anymore.  But I haven't found the time to dig deeper yet.  The full
Shibboleth stack is about to be removed from stretch due to the OpenSSL
transition, which is a more pressing issue at the moment.
-- 
Regards,
Feri

Bug#846608: shibboleth-sp2-utils: shibd.service is installed disabled, unlike init script

[Etienne Dysli-Metref]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 05/12/16 22:36, Russ Allbery wrote:
> General Debian policy is to enable all services at boot by default.
> So yes, this is the correct approach.

Thanks Russ!

I managed to fix this and uploaded a new revision at
https://mentors.debian.net/package/shibboleth-sp2. I've pushed the
changes in branch edm/debian/master, if they are fine I'll merge them
in debian/master. I'd be glad if either you or Ferenc could review and
upload the package to unstable. :)

Cheers,
   Etienne
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJYSXhvAAoJEDtvu5hdVFPuVsoP/jcg1adJKK8ZnsLGu7yP1Tm0
I2RTMVwxSkFg1xzGSRhgombeRlXIA4VmWMRGEDKxPwGI2LBSZDDFJKusfgm4PNk3
V9MLGJYx5S0twQa2WtzjF/Ycg8yDMP3vnArCiEKzdcnkqd0wOvaRj1zwfoqJ4Rhj
28timfPJ+M+EZjXArP9oJyvXYjRflwzm8OP+P+Ds6nEizZGT3kmkHhHNYtKzzwJk
Wm/XxZAfk813np9nVcJt6p1mj7exRRSiGkaUKPoObYXCe3FZvWtsftySf8ml+GDT
MVJ2Wo8MiES5/9QQ/sw2McNYWSixr0CY96AiL+W4mh9wHKS+27S6H7sDk5ArjNVJ
onBU7eOxSAPfrU4xCWOXP5CpCfkIBWXcjErj2q/ndl4nkyECn5vrNua5zLYyew8h
C1Jip+GO0IVqqjgws3r2m400c61nKlKB7sLk6jxe+y5Pf0BJNaSfeL9ivNuknX+O
IqSSPOZbcY9njSDSLbiFquraDo5vDIdXfOkz8PChtJUpI49S8qqXeuHY5bCDVBCH
99mziQ90+L6/Ruwbo7s4P8B+rlaNCMB82QxZlkMt5PbDZXFPrkz3B6jm8hMb8lWu
owkv5AoFtENsHo8JRSKTLK6bjb6SCJWuWC3/td/Ywapalwwlr6zv8Q3+wCCnjuic
dBq2fxenfaPbMkOxWsrE
=3Kls
-END PGP SIGNATURE-

Bug#846608: shibboleth-sp2-utils: shibd.service is installed disabled, unlike init script

[Russ Allbery]

Etienne Dysli-Metref  writes:
> On 02/12/16 16:22, Etienne Dysli-Metref wrote:

>> I would expect the shibd service to be enabled to start at boot 
>> during installation.

> I was unable to find an answer in the Debian policy about whether to
> enable services at boot, section 9.3 [1] isn't clear about this. I
> propose we enable shibd at installation time with dh_systemd [2] to keep
> the behaviour of previous versions. What do you think?

General Debian policy is to enable all services at boot by default.  So
yes, this is the correct approach.

-- 
Russ Allbery (r...@debian.org)   

Bug#846608: shibboleth-sp2-utils: shibd.service is installed disabled, unlike init script

[Etienne Dysli-Metref]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 02/12/16 16:22, Etienne Dysli-Metref wrote:
> I would expect the shibd service to be enabled to start at boot 
> during installation.

I was unable to find an answer in the Debian policy about whether to
enable services at boot, section 9.3 [1] isn't clear about this. I
propose we enable shibd at installation time with dh_systemd [2] to
keep the behaviour of previous versions. What do you think?

Cheers,
   Etienne

[1] https://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
[2]
https://wiki.debian.org/Teams/pkg-systemd/Packaging#Using_debhelper_with
_dh_systemd
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJYRR5MAAoJEDtvu5hdVFPu6rYQAK/7NQdi8c8aGTnCw3g6Dset
40DKnQd2jYHXIGThUvNy1ThbcFt2YTzc5UH1waxli1KqZ/VcJEgLHGl7nFFpSEpL
nXaBs9FNrH4pWn5PMuYJ1wbzQCpu3IkzoPTvSTJRHmFLadVtiRw58ax+cb5rGPz5
0SavdKrYiGzBg7UOOQoAV2kOocPSYG4rVGr52wr0pSc9tAuJc+VIcLiAapBi3uPE
usu+on1r6ACGBpk3fvbMuP777n+WCb2vC4tyb6OKjyQ/5WPZ3IdG7V6qkSGIynzn
3KQVr6dqcMkN/DGMFmrCICBHWXVR6/fRuHyrLWo0fYpRahQx++mBA89AbiNzTTGP
qzJfDmCBBFYX8b16zOSNfppfezkafxQ9Zzyu6u918v5nq/6FQybTwOwOpvqHoVs6
M+xxFsfpaHwZUXAyxWWJ508AHiJ5tBueQ+A7MB1jo3nZpjkR95z/Ald8tXGo1W/P
NGHmJdSXk+7ln5vMuMxZIQqatSpaWl/IRoyg2ekM1tFl13pslIgHU+lXBCeYfOel
OpX3dEX97Ghi518kKIkL4Hi2snL6D2XIHdjee485cJPRKJpEvEXDVNCtad5zzpPV
4iNCVmsRtqDKocF0ChlfP0WSBc/nxaOh7eLc2AUv9yBTmKPu4fF/SHmc0TmlO9JC
6jelpMBCY3zadAzKfvnh
=ib4k
-END PGP SIGNATURE-

Bug#846608: shibboleth-sp2-utils: shibd.service is installed disabled, unlike init script

[Etienne Dysli-Metref]

Package: shibboleth-sp2-utils
Version: 2.6.0+dfsg1-3+b1
Severity: normal

Dear Maintainers,

I installed libapache2-mod-shib2 and its dependencies (among them 
shibboleth-sp2-utils) and shibd was running after the package finished 
installing. However, after a reboot, shibd is not started because the 
systemd service unit for shibd is disabled. If I remember correctly, 
this behaviour is different from previous versions of this package where 
the init script was enabled upon installation.

I would expect the shibd service to be enabled to start at boot during 
installation.

Cheers,
  Etienne

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages shibboleth-sp2-utils depends on:
ii  adduser3.115
ii  libc6  2.24-7
ii  libfcgi0ldbl   2.4.0-8.4
ii  libgcc11:6.2.0-13
ii  liblog4shib1v5 1.0.9-3
ii  libsaml9   2.6.0-4
ii  libshibsp-plugins  2.6.0+dfsg1-3+b1
ii  libshibsp7 2.6.0+dfsg1-3+b1
ii  libstdc++6 6.2.0-13
ii  libsystemd0232-6
ii  libxerces-c3.1 3.1.3+debian-2.1+b1
ii  libxmltooling7 1.6.0-3

Versions of packages shibboleth-sp2-utils recommends:
ii  openssl  1.1.0c-2

shibboleth-sp2-utils suggests no packages.

-- no debconf information