Re: Dovecot Problems on Sid

2011-05-15 Thread Andrei Popescu
On Du, 15 mai 11, 11:41:18, deloptes wrote: > > The reason to say this the way I said it, is because already last time I > migrated dovecot I had many troubles and this is the job of the developers. > Believe me I know what I am doing (resp. saying). Dealing everyday with > software developers ...

Re: Dovecot Problems on Sid

2011-05-15 Thread deloptes
Stan Hoeppner wrote: > ""sid" is subject to massive changes and in-place library updates. This > can result in a very "unstable" system which contains packages that > cannot be installed due to missing libraries, dependencies that cannot > be fulfilled etc. Use it at your own risk!" Stan, stop re

Re: Dovecot Problems on Sid

2011-05-15 Thread deloptes
Stan Hoeppner wrote: > Your demonstrated frustration and cussing clearly demonstrate you are > NOT a proper candidate for using unstable packages.  Do yourself and > us a favor and stick to stable. you are not proper candidate to tell me what I should do. The reason to say this the way I said it

Re: Dovecot Problems on Sid

2011-05-14 Thread Stan Hoeppner
On 5/14/2011 2:25 PM, David Baron wrote: > Unfortunately, the maintainers changed the configurations to the "more > modern/recent" conf.d directory script system without providing any script > for > transition and NO WARNING for apt-listchanges. To tell us to avoid "unstable" > is no excuse, e

Re: Dovecot Problems on Sid

2011-05-14 Thread Stan Hoeppner
On 5/14/2011 1:28 PM, Ron Johnson wrote: > On 05/14/2011 11:32 AM, Stan Hoeppner wrote: >> On 5/14/2011 6:07 AM, deloptes wrote: >> >>> Someone is brainless - but definitely not me! >> >> deloptes@>yahoo.com< >> >> Nope, definitely not you. ;) >> > > That's pretty rude, and definitely uncalled for

Re: Dovecot Problems on Sid

2011-05-14 Thread Sven Joachim
On 2011-05-14 21:25 +0200, David Baron wrote: > Unfortunately, the maintainers changed the configurations to the "more > modern/recent" conf.d directory script system without providing any script > for > transition and NO WARNING for apt-listchanges. To tell us to avoid "unstable" > is no excu

Re: Dovecot Problems on Sid

2011-05-14 Thread David Baron
On Saturday 10 Iyar 5771 15:26:42 debian-user-digest-requ...@lists.debian.org wrote: > > Updating to the Sid version was a catastrophe--flagged all kinds of > > superseded syntax warning which were flagged as errors when I tried to > > edit them into the conf file. Commented out, got listening err

Re: Dovecot Problems on Sid

2011-05-14 Thread Ron Johnson
On 05/14/2011 11:32 AM, Stan Hoeppner wrote: On 5/14/2011 6:07 AM, deloptes wrote: Someone is brainless - but definitely not me! deloptes@>yahoo.com< Nope, definitely not you. ;) That's pretty rude, and definitely uncalled for on a public list. -- "Neither the wisest constitution nor the

Re: Dovecot Problems on Sid

2011-05-14 Thread Stan Hoeppner
On 5/14/2011 6:13 AM, deloptes wrote: > someone is thinking with his/her ass instead > of his/her head Your statement could very well be applied to occasional users who attempt to install unstable software, i.e. yourself. "sid" is subject to massive changes and in-place library updates. This can

Re: Dovecot Problems on Sid

2011-05-14 Thread Stan Hoeppner
On 5/14/2011 6:07 AM, deloptes wrote: > Someone is brainless - but definitely not me! deloptes@>yahoo.com< Nope, definitely not you. ;) -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Arc

Re: Dovecot Problems on Sid

2011-05-14 Thread deloptes
Camaleón wrote: > It's still unclear where the problem is. Camaleón, it's pretty clear - someone is thinking with his/her ass instead of his/her head when you have fixed it let me know - I spent about 2hours now with this shit, not working and I'm giving up. Even the information on the website

Re: Dovecot Problems on Sid

2011-05-14 Thread deloptes
David Baron wrote: > Updating to the Sid version was a catastrophe--flagged all kinds of > superseded syntax warning which were flagged as errors when I tried to > edit them into the conf file. Commented out, got listening errors for > various 9## ports. > > So I downgraded to the testing version

Re: Dovecot Problems on Sid (SOLVED)

2011-05-02 Thread David Baron
Problems were caused by combination of old conf file and the new conf.d files which were not removed on downgrade. I re-upgraded to the Sid packages, taking the new maintainer's conf files when asked. Then had to configure from scratch. Finally have it working. 1. New and old config files canno

Re: Dovecot Problems on Sid

2011-05-01 Thread Camaleón
On Sat, 30 Apr 2011 23:36:35 +0300, David Baron wrote: > On Saturday 26 Nisan 5771 22:59:04 David Baron wrote: >> > I would start with the usual tests: >> > >> > http://wiki.dovecot.org/TestInstallation >> >> Process is not running. There is no log entry after those listener >> errors (995 and

Re: Dovecot Problems on Sid

2011-04-30 Thread David Baron
On Saturday 26 Nisan 5771 22:59:04 David Baron wrote: > On Friday 25 Nisan 5771 16:39:11 > debian-user-digest-requ...@lists.debian.org > > wrote: > > > Updating to the Sid version was a catastrophe--flagged all kinds of > > > superseded syntax warning which were flagged as errors when I tried to >

Re: Dovecot Problems on Sid

2011-04-30 Thread David Baron
On Friday 25 Nisan 5771 16:39:11 debian-user-digest-requ...@lists.debian.org wrote: > > Updating to the Sid version was a catastrophe--flagged all kinds of > > superseded syntax warning which were flagged as errors when I tried to > > edit them into the conf file. Commented out, got listening erro

Re: Dovecot Problems on Sid

2011-04-29 Thread Camaleón
On Fri, 29 Apr 2011 14:29:31 +0300, David Baron wrote: (please, avoid using html formatted messages) > Updating to the Sid version was a catastrophe--flagged all kinds of > superseded syntax warning which were flagged as errors when I tried to > edit them into the conf file. Commented out, got li

Dovecot Problems on Sid

2011-04-29 Thread David Baron
Updating to the Sid version was a catastrophe--flagged all kinds of superseded syntax warning which were flagged as errors when I tried to edit them into the conf file. Commented out, got listening errors for various 9## ports. So I downgraded to the testing version and used a backed up conf fil