Bug#324480: dovecot-imapd: Incorrectly Conflicts: with imap-server

2005-08-23 Thread Fabio Tranchitella
Il giorno lun, 22/08/2005 alle 11.57 +0100, Edward Speyer ha scritto:
 Package: dovecot-imapd
 Severity: important
 
 While trying to make the transition from uw-imapd to dovecot-imapd, I
 find I am unable to have both packages installed concurrently due to the
 Conflicts: section for dovecot-imapd.
 
 (I would like to test dovecot before going live with it, and to have
 my old imapd running during this test period.)

 Surely it should be possible to have both packages installed at once?
 Is there a technical reason why it would be bad to have both IMAPDs
 running?

You are right, we'll remove the conflicts field with the next upload 
(dovecot-1.0.alpha1).

Thanks for the suggestion,

-- 
Fabio Tranchitella http://www.kobold.it
Studio Tranchitella Assoc. Professionale   http://www.tranchitella.it
_
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564


signature.asc
Description: This is a digitally signed message part


Bug#324480: dovecot-imapd: Incorrectly Conflicts: with imap-server

2005-08-23 Thread Fabio Tranchitella
Il giorno mar, 23/08/2005 alle 11.31 +0100, Edward ha scritto:
 I actually built a custom dovecot package without either the Provides:
 imap-server or Conflicts: imap-server because the Provides:
 imap-server from dovecot conflicted with the Conflicts: imap-server
 of uw-imapd, my previous IMAP daemon.

I've done something similar when I had to migrate a customer's mail
server from courier to dovecot, but in that case courier did not
conflict with imap-server.

I think the conflicts line is there for the same tcp port needed
problem, and its use is allowed by debian policy (7.3):


A special exception is made for packages which declare a conflict with
their own package name, or with a virtual package which they provide
see below): this does not prevent their installation, and allows a
package to conflict with others providing a replacement for it.  You
use this feature when you want the package in question to be the only
package providing some feature.


However, I think we should get rid of all these imap-server and
pop3-server conflicts: it is quite common to have two or more imap/pop3
server installed.

 Perhaps I should take this to a debian-* list.  If I were to do so, I
 would value your opinion as a DD and imap-server package maintainer.

Yes, could you please ask on debian-devel list?

-- 
Fabio Tranchitella [EMAIL PROTECTED].''`.
Proud Debian GNU/Linux developer, admin and user.: :'  :
 `. `'`
   http://people.debian.org/~kobold/   `-
_
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564


signature.asc
Description: This is a digitally signed message part


Bug#324480: dovecot-imapd: Incorrectly Conflicts: with imap-server

2005-08-23 Thread Edward
On Tue, 2005-08-23 12:06, Fabio Tranchitella wrote:
 Il giorno lun, 22/08/2005 alle 11.57 +0100, Edward Speyer ha scritto:
  Package: dovecot-imapd
  Severity: important
  
  While trying to make the transition from uw-imapd to dovecot-imapd, I
  find I am unable to have both packages installed concurrently due to the
  Conflicts: section for dovecot-imapd.
  
  (I would like to test dovecot before going live with it, and to have
  my old imapd running during this test period.)
 
  Surely it should be possible to have both packages installed at once?
  Is there a technical reason why it would be bad to have both IMAPDs
  running?
 
 You are right, we'll remove the conflicts field with the next upload 
 (dovecot-1.0.alpha1).

I actually built a custom dovecot package without either the Provides:
imap-server or Conflicts: imap-server because the Provides:
imap-server from dovecot conflicted with the Conflicts: imap-server
of uw-imapd, my previous IMAP daemon.

There are lots of other 'imap-server' packages that have the problem of
not wanting to co-install with other 'imap-server' packages:

  [EMAIL PROTECTED]:~$ grep-dctrl -sPackage,Provides,Conflicts 
-FProvides,Conflicts 'imap-server' /var/lib/apt/lists/*Packages
  Package: bincimap-run
  Provides: imap-server
  Conflicts: imap-server

  Package: courier-imap
  Provides: imap-server
  Conflicts: imap-server

  Package: cyrus-imapd
  Provides: imap-server
  Conflicts: imap, imapd, imap-4, imap-server

  Package: cyrus21-imapd
  Provides: imap-server
  Conflicts: imap-server

  Package: dovecot-imapd
  Provides: imap-server
  Conflicts: imap-server

  Package: mailutils-imap4d
  Provides: imap-server
  Conflicts: imap-server

  Package: uw-imapd
  Provides: imap-server
  Conflicts: imapd, imap-4, imap, imap-server, logcheck ( 1.1.1-9)


Either:

  - What I originally wanted to do was extra-ordinary, and that, on
balance, it is better for any package that provides imap-server to
also conflict with imap-server

  - All these packages incorrectly Conflict with imap-server, which
stops syadmins co-installing two imap servers in order to do tests
and make smooth transitions[*]

Perhaps I should take this to a debian-* list.  If I were to do so, I
would value your opinion as a DD and imap-server package maintainer.

Thanks,

Ed

[*] Obviously, massive bias there on my part :)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#324480: dovecot-imapd: Incorrectly Conflicts: with imap-server

2005-08-22 Thread Edward Speyer
Package: dovecot-imapd
Severity: important

While trying to make the transition from uw-imapd to dovecot-imapd, I
find I am unable to have both packages installed concurrently due to the
Conflicts: section for dovecot-imapd.

(I would like to test dovecot before going live with it, and to have
my old imapd running during this test period.)

Surely it should be possible to have both packages installed at once?
Is there a technical reason why it would be bad to have both IMAPDs
running?

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.31
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]