logwatch should depend on exim4 instead of exim (which is exim3)

Bug #121265 reported by Mike Fedyk
4
Affects Status Importance Assigned to Milestone
logwatch (Ubuntu)
Fix Released
Undecided
Unassigned
Dapper
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: logwatch

The last maintenance release for exim was in 2002 and it is in universe.

Also the exim4 package is in main and exim is in universe.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Probably true, although this issue is best dealt with in Debian. It should probably be exim4 | mta in Debian if logwatch works with other mail servers.

Revision history for this message
Mike Fedyk (mfedyk) wrote :

http://packages.debian.org/unstable/admin/logwatch

It already does depend on exim4 in Debian unstable, that means it will probably get into gutsy.

I want it to depend on exim4 in dapper, which is the long term support release.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Yes, that's the version in the Gutsy repositories now.

Changed in logwatch:
status: Unconfirmed → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote :

After reviewing the policy for updates to stable releases, https://wiki.ubuntu.com/MOTU/SRU, I don't think this issue applies. The impact is (AFAICT) limited to having to install an extra package that you won't use. If that's not correct, please reopen the Dapper task and explain which SRU catagory this bug fits into.

Changed in logwatch:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.