Bug#594113: task_manager.pl daemon failed to start
On Thu, Sep 02, 2010 at 08:11:34AM +0200, Emmanuel Bouthenot wrote: So if you honestly let me choose, I suggest we simply close this as a non-bug. What do you think of a tagging it wontfix instead of closing it? It will leave a trace for people encountering the problem. I thought about suggesting it myself, but changed my mind: In my opinion it is a non-bug, not a bug we won't fix. The "bug" that I won't fix - the one of failing to work due to routinely suppressing recommends expecting that all whould still work smoothly - really should be filed against debian-policy, IMO. The "bug" in this package is a wishlist request to work out-of-the-box also in the odd situation of someone disliking centrally distributed ca-certificates and therefore suppressing that particular recommendation. If someone wants to work on that, then sure let's lower this bugreport to severity wishlist and retitle it appropriately. But that won't help serve others in same situation as you, I suspect. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
> So if you honestly let me choose, I suggest we simply close this as a
> non-bug.
What do you think of a tagging it wontfix instead of closing it? It will
leave a trace for people encountering the problem.
M.
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Wed, Sep 01, 2010 at 11:00:42PM +0200, Emmanuel Bouthenot wrote: Until eventually fixed upstream, could we perhaps provide an empty CRL at that fallback location? If we want to do that we have to be careful to not break current installations (which uses the CA bundle provided by ca-certificates). I still think that adding a dependency on ca-certiticates is a good compromise for now (and squeeze). The ball is in your court, I'll let you choose. Well, my stand in this is that recommending ca-certificates is fine and dandy, and we need nothing more than that. A package failing to work out-of-the-box when recommendations are ignored is not a packaging bug as I read Debian Policy. It is a user deliberately overriding a usability feature of Debian in favor of a flexibility feature. So if you honestly let me choose, I suggest we simply close this as a non-bug. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
> Until eventually fixed upstream, could we perhaps provide an empty
> CRL at that fallback location?
If we want to do that we have to be careful to not break current
installations (which uses the CA bundle provided by ca-certificates).
I still think that adding a dependency on ca-certiticates is a good
compromise for now (and squeeze).
The ball is in your court, I'll let you choose.
M.
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Thu, Aug 26, 2010 at 09:54:41AM +0200, Stefan Hornburg (Racke) wrote: On 08/26/2010 09:49 AM, Jonas Smedegaard wrote: According to Sympa web page it can instead be a directory containing CA certificates. And it can be undefined, meaning S/MIME is disabled. AFAIR S/MIME is disabled by the default package installation. If not, that is a bug :-). Then what actually _uses_ the apparently mandatory cafile/capath option? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
On Thu, Aug 26, 2010 at 10:51:26AM +0200, Stefan Hornburg (Racke) wrote:
On 08/24/2010 11:44 AM, Jonas Smedegaard wrote:
Hi Emmanuel,
On Mon, Aug 23, 2010 at 09:20:38PM +0200, Emmanuel Bouthenot wrote:
Package: sympa
Version: 6.0.1+dfsg-2
Severity: grave
To start correctly, task_manager.pl daemon expects
/usr/share/sympa/default/ca-bundle.crt to be a valid symlink to
/etc/ssl/certs/ca-certificates.crt.
ca-certificates (which provides /etc/ssl/certs/ca-certificates.crt)
should be a real dependency instead of a recommend.
Is that path hardcoded or configurable?
If configurable, only recommending is the proper relation to use.
The path is configurable, but you cannot omit it.
An empty value for cafile in sympa.conf is rejected.
Otherwise a default setting kicks in:
unless ( (defined $o{'cafile'}) || (defined $o{'capath'} )) {
$o{'cafile'}[0] = Sympa::Constants::DEFAULTDIR . '/ca-bundle.crt';
}
So we need in fact a real dependency. I also think this is upstream bug
resp. inconsistency in the documentation.
Until eventually fixed upstream, could we perhaps provide an empty CRL
at that fallback location?
Or instead of undefining, then set capath to an empty dir.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
On 08/24/2010 11:44 AM, Jonas Smedegaard wrote:
Hi Emmanuel,
On Mon, Aug 23, 2010 at 09:20:38PM +0200, Emmanuel Bouthenot wrote:
Package: sympa
Version: 6.0.1+dfsg-2
Severity: grave
To start correctly, task_manager.pl daemon expects
/usr/share/sympa/default/ca-bundle.crt to be a valid symlink to
/etc/ssl/certs/ca-certificates.crt.
ca-certificates (which provides /etc/ssl/certs/ca-certificates.crt)
should be a real dependency instead of a recommend.
Is that path hardcoded or configurable?
If configurable, only recommending is the proper relation to use.
The path is configurable, but you cannot omit it.
An empty value for cafile in sympa.conf is rejected.
Otherwise a default setting kicks in:
unless ( (defined $o{'cafile'}) || (defined $o{'capath'} )) {
$o{'cafile'}[0] = Sympa::Constants::DEFAULTDIR . '/ca-bundle.crt';
}
So we need in fact a real dependency. I also think this is upstream bug
resp. inconsistency in the documentation.
Regards
Racke
--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On 08/26/2010 09:49 AM, Jonas Smedegaard wrote: On Thu, Aug 26, 2010 at 08:24:46AM +0200, Emmanuel Bouthenot wrote: Well, you not experiencing problems avoiding Recommends do not really change the Debian definition of the Recommends: stanza: >`Recommends' > This declares a strong, but not absolute, dependency. Nothing defines “absolute”, for me it is (absolute) because: - SYMPA provides a symlink to this third party package - a daemon fail to start without this dependency The text continued, describing how most uses would need recommended packages. Why did you cut out that elaboration? My question is if it is *possible* to hand-tune. Probably if you are enough skilled to understand the bug and fix it on your own. It requires the skill of either a) disabling S/MIME or b) changing the cacert option to point to some folder containing CA certificates. And yes, suppressing recommended packages is indeed an indication that you are a skilled person. You do not agree that the needed file is possible to create by other means and with other content than installing that package? This file should a be a bundle of root CA certificates, According to Sympa web page it can instead be a directory containing CA certificates. And it can be undefined, meaning S/MIME is disabled. AFAIR S/MIME is disabled by the default package installation. If not, that is a bug :-). Regards Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Thu, Aug 26, 2010 at 08:24:46AM +0200, Emmanuel Bouthenot wrote: Well, you not experiencing problems avoiding Recommends do not really change the Debian definition of the Recommends: stanza: >`Recommends' >This declares a strong, but not absolute, dependency. Nothing defines “absolute”, for me it is (absolute) because: - SYMPA provides a symlink to this third party package - a daemon fail to start without this dependency The text continued, describing how most uses would need recommended packages. Why did you cut out that elaboration? My question is if it is *possible* to hand-tune. Probably if you are enough skilled to understand the bug and fix it on your own. It requires the skill of either a) disabling S/MIME or b) changing the cacert option to point to some folder containing CA certificates. And yes, suppressing recommended packages is indeed an indication that you are a skilled person. You do not agree that the needed file is possible to create by other means and with other content than installing that package? This file should a be a bundle of root CA certificates, According to Sympa web page it can instead be a directory containing CA certificates. And it can be undefined, meaning S/MIME is disabled. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
> Well, you not experiencing problems avoiding Recommends do not really
> change the Debian definition of the Recommends: stanza:
>
> >`Recommends'
> >This declares a strong, but not absolute, dependency.
Nothing defines “absolute”, for me it is (absolute) because:
- SYMPA provides a symlink to this third party package
- a daemon fail to start without this dependency
[...]
> My question is if it is *possible* to hand-tune.
Probably if you are enough skilled to understand the bug and fix it on
your own.
(As a workaround we could add a note in the README.Debian but I doubt of
its effectiveness: it looks like a bug, the first reaction would be to
check BTS rather that reading README.Debian).
[...]
> You do not agree that the needed file is possible to create by other
> means and with other content than installing that package?
This file should a be a bundle of root CA certificates, hence there is 2
choices:
- You try to collect all the root CA certificates manually to build
your own CA file
- You install the ca-certificates package to use the CA bundle it
provides
[...]
> Because in some special cases it is not needed and gets in the way.
I agree when the Recommends add optional features which don't affect
the core program.
[...]
> I do feel, however, that your arguments are tied to how you are used
> to handle package relationships in the past, whereas I believe my
> arguments are tied to how Debian Policy defines the package relation
> stanzas.
WE are tied on how we understand them:
« Recommends: This declares a strong, but not absolute, dependency. »
What mean “absolute”?
> And as I wrote earlier on to this bugreport, I do believe that if
> ca-certificates missing causes sympa to consume all resources on the
> system, then there is a bug in sympa code which should be filed
> separately - and passed upstream.
It's just a possible consequence, the main problem is that the
task_manager daemon doesn't starts. Whatever its role, I think it's a
big issue.
M.
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Wed, Aug 25, 2010 at 10:50:39AM +0200, Stefan Hornburg (Racke) wrote: On 08/25/2010 10:34 AM, Jonas Smedegaard wrote: On Wed, Aug 25, 2010 at 09:18:36AM +0200, Stefan Hornburg (Racke) wrote: IMHO Sympa daemons should work without packages in Recommends. And ca-certificates isn't really a problem to be depend on. Is S/MIME a mandatory or optional feature of sympa? Optional. Then Sympa *does* work without the recommended ca-certificates package. If Sympa not only should work without recommends, but work out of the box, then we should IMO change the default configuration to not enable S/MIME support out of the box. You are right that ca-certificated isn't really a problem to depend on for the wast majority of users, but for the minority of users who might choose to not trust the third parties provided in ca-certificates, it *is* a problem to remove that package if depended on by Sympa. Yes, it is possible to install ca-certificates and then configure it to disable all of its certificates, and then at each upgrade of the package again make sure to disable them all, but that has an in-built risk of accidentally enabling them. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
On 08/25/2010 10:34 AM, Jonas Smedegaard wrote: On Wed, Aug 25, 2010 at 09:18:36AM +0200, Stefan Hornburg (Racke) wrote: IMHO Sympa daemons should work without packages in Recommends. And ca-certificates isn't really a problem to be depend on. Is S/MIME a mandatory or optional feature of sympa? - Jonas Optional. Regards Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Wed, Aug 25, 2010 at 09:18:36AM +0200, Stefan Hornburg (Racke) wrote: IMHO Sympa daemons should work without packages in Recommends. And ca-certificates isn't really a problem to be depend on. Is S/MIME a mandatory or optional feature of sympa? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
On Wed, Aug 25, 2010 at 09:11:33AM +0200, Emmanuel Bouthenot wrote: When not respecting recommends, you cannot expect package to work "out of the box" but will need some hand-tuning to get working. I never install Recommends on my Debian machines (servers, desktop, laptop). It's the first time I encounter such problems. Well, you not experiencing problems avoiding Recommends do not really change the Debian definition of the Recommends: stanza: `Recommends' This declares a strong, but not absolute, dependency. The `Recommends' field should list packages that would be found together with this one in all but unusual installations. Do you dare say that it is not possible - with hand-tuning - to get some parts of sympa working when ca-certificates is not around? If I install SYMPA I expect that *all* parts works (not only 3 daemons among 4). I do understand what you expect. My question is if it is *possible* to hand-tune. I strongly suspect that even without changing a single line in sympa configuration files, but only using some openssl command to generate a certificate and a crl file for it, sympa can run fine. Do you not agree with that? No, You do not agree that the needed file is possible to create by other means and with other content than installing that package? AFAIK this CA file (which expects to be a bundle of root CA certificates) is also used by SYMPA to redistribute S/MIME encrypted messages sent by subscribers[1]. Yes, I believe so too. I still don't understand why I should install a Recommend which is needed to get a basic setup working. Because in some special cases it is not needed and gets in the way. ca-certificates contains certificates for a bunch of trusted third parties. Sympa *can* trust these third parties, but is not forced to do so. The funny thing is that SYMPA depends on perl-suid and libfcgi-perl which should probably be ‘Recommends’. I don't find that funny. I find it a relevant discovery: If not *always* needed, those relations should be lowered to recommends too. As a SYMPA maintainer, it's a bit sad that I can't fix something I consider to be a bug. Sure you can: Just as well as I can close the bug, you can open it again. I do feel, however, that your arguments are tied to how you are used to handle package relationships in the past, whereas I believe my arguments are tied to how Debian Policy defines the package relation stanzas. Jonas, I don't want to fight with you about this. It seems that I can't convince you. I prefer to focus on the other bugs to fix. I won't stop you. And as I wrote earlier on to this bugreport, I do believe that if ca-certificates missing causes sympa to consume all resources on the system, then there is a bug in sympa code which should be filed separately - and passed upstream. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
On 08/25/2010 09:11 AM, Emmanuel Bouthenot wrote: When not respecting recommends, you cannot expect package to work "out of the box" but will need some hand-tuning to get working. I never install Recommends on my Debian machines (servers, desktop, laptop). It's the first time I encounter such problems. Do you dare say that it is not possible - with hand-tuning - to get some parts of sympa working when ca-certificates is not around? If I install SYMPA I expect that *all* parts works (not only 3 daemons among 4). I strongly suspect that even without changing a single line in sympa configuration files, but only using some openssl command to generate a certificate and a crl file for it, sympa can run fine. Do you not agree with that? No, AFAIK this CA file (which expects to be a bundle of root CA certificates) is also used by SYMPA to redistribute S/MIME encrypted messages sent by subscribers[1]. I still don't understand why I should install a Recommend which is needed to get a basic setup working. The funny thing is that SYMPA depends on perl-suid and libfcgi-perl which should probably be ‘Recommends’. As a SYMPA maintainer, it's a bit sad that I can't fix something I consider to be a bug. Jonas, I don't want to fight with you about this. It seems that I can't convince you. I prefer to focus on the other bugs to fix. IMHO Sympa daemons should work without packages in Recommends. And ca-certificates isn't really a problem to be depend on. Regards Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
> When not respecting recommends, you cannot expect package to work
> "out of the box" but will need some hand-tuning to get working.
I never install Recommends on my Debian machines (servers, desktop,
laptop). It's the first time I encounter such problems.
> Do you dare say that it is not possible - with hand-tuning - to get
> some parts of sympa working when ca-certificates is not around?
If I install SYMPA I expect that *all* parts works (not only 3 daemons
among 4).
> I strongly suspect that even without changing a single line in sympa
> configuration files, but only using some openssl command to generate
> a certificate and a crl file for it, sympa can run fine.
>
> Do you not agree with that?
No,
AFAIK this CA file (which expects to be a bundle of root CA certificates)
is also used by SYMPA to redistribute S/MIME encrypted messages sent by
subscribers[1].
I still don't understand why I should install a Recommend which is
needed to get a basic setup working.
The funny thing is that SYMPA depends on perl-suid and libfcgi-perl
which should probably be ‘Recommends’.
As a SYMPA maintainer, it's a bit sad that I can't fix something I
consider to be a bug.
Jonas, I don't want to fight with you about this. It seems that I can't
convince you. I prefer to focus on the other bugs to fix.
M.
[1] http://www.sympa.org/manual/x509
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Tue, Aug 24, 2010 at 10:09:09PM +0200, Emmanuel Bouthenot wrote: You disabled the auto-pilot. Now steer manually. Particularly: Now create that file missing since you chose to not have that file provided by a package but would rather create it yourself. So no, you did not (yet) convince me that this is a real bug. You didn't convince me neither that it's not a bug :) SYMPA package provides a symlink to /etc/ssl/certs/ca-certificates.crt (which is essential for one of its daemon to start) hence I think that it creates a strong dependency on this package. If I enable auto-pilot (ie: Recommends), installing SYMPA pulls ca-certificates and all the daemons works perfectly. For some reason, if ca-certificates is removed then SYMPA will be broken with the next restart. When not respecting recommends, you cannot expect package to work "out of the box" but will need some hand-tuning to get working. Do you dare say that it is not possible - with hand-tuning - to get some parts of sympa working when ca-certificates is not around? I strongly suspect that even without changing a single line in sympa configuration files, but only using some openssl command to generate a certificate and a crl file for it, sympa can run fine. Do you not agree with that? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
> You disabled the auto-pilot. Now steer manually. Particularly: Now
> create that file missing since you chose to not have that file
> provided by a package but would rather create it yourself.
> So no, you did not (yet) convince me that this is a real bug.
You didn't convince me neither that it's not a bug :)
SYMPA package provides a symlink to /etc/ssl/certs/ca-certificates.crt
(which is essential for one of its daemon to start) hence I think that
it creates a strong dependency on this package.
If I enable auto-pilot (ie: Recommends), installing SYMPA pulls
ca-certificates and all the daemons works perfectly. For some reason, if
ca-certificates is removed then SYMPA will be broken with the next
restart.
That sounds like a bug :)
M.
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
On Tue, Aug 24, 2010 at 09:24:35PM +0200, Emmanuel Bouthenot wrote: So sympa needs _some_ value for cafile, and ca-certificates provides a sane default for _most_ situations. The Recommends: stanza is _exactly intended for such situations. There was a long-time bug in apt-get to wrongly treating Recommends like Suggests. It was a bug and it has been solved. What is left is the wrong assumption amongst those used to the old wrong behaviour of apt-get. You need to un-learn that :-) I disagree: I've spotted the bug because on all the Debian machines I administer (especially servers), I explicitly disable the installation of Suggests and Recommends. After installing SYMPA in a fresh Debian, I wondered why listmanager failed to start. I had to trace the daemon to understand the problem. Hence SYMPA is not fully usable if Recommends are disabled. I think that it's not reasonable. What do you think? The package is not expected to be "fully usable" when Recommends are ignored. You disabled the auto-pilot. Now steer manually. Particularly: Now create that file missing since you chose to not have that file provided by a package but would rather create it yourself. So no, you did not (yet) convince me that this is a real bug. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
> So sympa needs _some_ value for cafile, and ca-certificates provides
> a sane default for _most_ situations.
>
> The Recommends: stanza is _exactly intended for such situations.
>
> There was a long-time bug in apt-get to wrongly treating Recommends
> like Suggests. It was a bug and it has been solved. What is left is
> the wrong assumption amongst those used to the old wrong behaviour of
> apt-get. You need to un-learn that :-)
I disagree:
I've spotted the bug because on all the Debian machines I administer
(especially servers), I explicitly disable the installation of Suggests
and Recommends.
After installing SYMPA in a fresh Debian, I wondered why listmanager
failed to start. I had to trace the daemon to understand the problem.
Hence SYMPA is not fully usable if Recommends are disabled. I think that
it's not reasonable.
What do you think?
M.
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
Hi Jonas,
> Is that path hardcoded or configurable?
Yes, the “cafile” option in sympa.conf but...
> If configurable, only recommending is the proper relation to use.
It's configurable but (AFAIK) the taskmanager daemon needs it to start.
If this option is not defined in sympa.conf, there is a fall back to the
default hardcoded value: /usr/share/sympa/default/ca-bundle.crt
> Also, why is this a grave issue?
I agree that the severity is probably too high.
The taskmanager is used to purge several kinds of datas (old bounced
mails, database logs, etc...). Under some conditions, it could conduct
to eat more and more disk space (on /var for example) and to hang the
whole system.
> Anyway, thanks a lot for caring about sympa and filing this bugreport!
Thanks for your help too.
M.
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594113: task_manager.pl daemon failed to start
Hi Emmanuel, On Mon, Aug 23, 2010 at 09:20:38PM +0200, Emmanuel Bouthenot wrote: Package: sympa Version: 6.0.1+dfsg-2 Severity: grave To start correctly, task_manager.pl daemon expects /usr/share/sympa/default/ca-bundle.crt to be a valid symlink to /etc/ssl/certs/ca-certificates.crt. ca-certificates (which provides /etc/ssl/certs/ca-certificates.crt) should be a real dependency instead of a recommend. Is that path hardcoded or configurable? If configurable, only recommending is the proper relation to use. Also, why is this a grave issue? Anyway, thanks a lot for caring about sympa and filing this bugreport! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#594113: task_manager.pl daemon failed to start
Package: sympa Version: 6.0.1+dfsg-2 Severity: grave To start correctly, task_manager.pl daemon expects /usr/share/sympa/default/ca-bundle.crt to be a valid symlink to /etc/ssl/certs/ca-certificates.crt. ca-certificates (which provides /etc/ssl/certs/ca-certificates.crt) should be a real dependency instead of a recommend. M. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.33-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
