Yes, I will prepare stable pu now, when I have confirmed that we have a fix.
Sorry for trouble.
Ondřej Surý
On 17. 5. 2013, at 6:33, Ben Hutchings wrote:
> On Thu, 2013-05-16 at 21:50 +0200, Ondřej Surý wrote:
>> Ben, I have uploaded -5 version to unstable.
>>
>> Would you be willing to try i
On Thu, 2013-05-16 at 21:50 +0200, Ondřej Surý wrote:
> Ben, I have uploaded -5 version to unstable.
>
> Would you be willing to try if that fixes the problem in some isolated
> environment?
[...]
That seems to work, thank you. Of course, it is also linked against
libdb5.1, new libc6, etc., so I
Ben, I have uploaded -5 version to unstable.
Would you be willing to try if that fixes the problem in some isolated
environment?
Thank you,
Ondrej
On Sun, May 5, 2013 at 4:34 PM, Ben Hutchings wrote:
> Package: cyrus-imapd-2.4
> Version: 2.4.16-4
> Severity: grave
>
> imapd was stopped during u
Ondrej,
I have not much experience in rebuild package but I tried
These were my steps:
apt-get source cyrus-imapd
vim cyrus-imapd-2.4-2.4.16/debian/cyrus-upgrade-db
diff cyrus-upgrade-db cyrus-imapd-2.4-2.4.16/debian/cyrus-upgrade-db
100d99
< cat $O
Perfect, amd64
Thank, Agu
El 15/05/2013 01:49 p.m., Ondřej Surý escribió:
I do not want to upload fixed packages before I know the fix is
correct. Anyway I can build the packages for you. What architecture?
i386 or amd64?
O.
On Wed, May 15, 2013 at 6:46 PM, Agustín Eijo wrote:
Hi,
El 15/05
I do not want to upload fixed packages before I know the fix is
correct. Anyway I can build the packages for you. What architecture?
i386 or amd64?
O.
On Wed, May 15, 2013 at 6:46 PM, Agustín Eijo wrote:
> Hi,
>
> El 15/05/2013 03:50 a.m., Ondřej Surý escribió:
>
>> Ben,
>>
>> I would be interes
Hi,
El 15/05/2013 03:50 a.m., Ondřej Surý escribió:
Ben,
I would be interested to hear if you can apply this fix and re-run the
upgrade in testing environment.
Yes, I have a Debian squeeze virtual PC with snapshot before than dist-upgrade
...
You upload the fix to testing repositories ?
O
Ben,
I would be interested to hear if you can apply this fix and re-run the
upgrade in testing environment.
Agustín, thank you very much for the analysis.
Just out of the interest – your /bin/sh is dash or some other shell?
Ondrej
On Tue, May 14, 2013 at 5:42 PM, Agustín Eijo wrote:
> The pos
The possible solution is:
while read -r OLD_DBKEY OLD_DBVALUE ; do
...
done < $OLD_LIST
for:
cat $OLD_LIST | \
while read -r OLD_DBKEY OLD_DBVALUE ; do
...
done
This creates a new child process with diferent variables
Source:
http://serverfault.com/questions/25
Sorry,
Had he made a mistake in the form of restore and The error is not "db4.7_recover: Build
signature doesn't match environment"
Now I think the problem is in the script upgrade-db with the variable
BERKELEY_DB_FOUND
The BERKELEY_DB_FOUND is set into the while .. done but out of while BE
It's possible you got hit bug bug similar to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625484
Could you downgrade the libdb4.7 version to squeeze and run the upgrade script
again?
Ondřej Surý
On 10. 5. 2013, at 19:10, Agustín Eijo wrote:
> Now, is:
>
> # dpkg -l | grep db4.7-util
> i
Now, is:
# dpkg -l | grep db4.7-util
ii db4.7-util 4.7.25-21 amd64Berkeley v4.7 Database
Utilities
db4.7-util configure first and then cyrus-common-2.4 (in apt-get dist-upgrade)
Before, I didn't have db4.7-util. I had only libdb4.7 (4.7.25-9). db4.7-util was
What was and is your db4.7-util version?
Ondřej Surý
On 10. 5. 2013, at 17:32, Agustín Eijo wrote:
> Hi,
>
> I had the same problem...
>
> Only restore old database directory /var/lib/cyrus and file
> /usr/lib/cyrus/cyrus-db-types.active
>
> #cat /usr/lib/cyrus/cyrus-db-types.active
> ANNOT
Hi,
I had the same problem...
Only restore old database directory /var/lib/cyrus and file
/usr/lib/cyrus/cyrus-db-types.active
#cat /usr/lib/cyrus/cyrus-db-types.active
ANNOTATION skiplist
DBENGINE BerkeleyDB4.7
DUPLICATE berkeley-nosync
MBOX skiplist
PTS berkeley
QUOTA quotalegacy
SEEN skipl
On Thu, May 9, 2013 at 4:18 AM, Ben Hutchings wrote:
> On Mon, 2013-05-06 at 07:23 +0200, Ondřej Surý wrote:
>> I still miss the answer for:
>>
>> >> Could you check the permissions on /var/lib/cyrus and it's contents?
>
> This is from the full system backup that ran just before the upgrade:
>
[..
On Mon, 2013-05-06 at 07:23 +0200, Ondřej Surý wrote:
> I still miss the answer for:
>
> >> Could you check the permissions on /var/lib/cyrus and it's contents?
This is from the full system backup that ran just before the upgrade:
# ls -al /restore/shadbolt-var/20130505/tree/lib/cyrus
total 1588
I still miss the answer for:
>> Could you check the permissions on /var/lib/cyrus and it's contents?
And could it be that you ran out of free space in /tmp?
I have tested the migration script throughly, but there still might be some
corner cases unhandled.
Well, it would help me to understand
On Sun, May 05, 2013 at 04:55:20PM +0200, Ondřej Surý wrote:
> Could you check the permissions on /var/lib/cyrus and it's contents?
>
> Also could you check the /var/backup/cyrus-imapd//, there should
> be a backup of your files, If you could send them to me off-list, it
> would help me with debug
Could you check the permissions on /var/lib/cyrus and it's contents?
Also could you check the /var/backup/cyrus-imapd//, there should
be a backup of your files, If you could send them to me off-list, it
would help me with debugging.
And please attach:
/usr/lib/cyrus/cyrus-db-types.txt
/usr/lib/c
Package: cyrus-imapd-2.4
Version: 2.4.16-4
Severity: grave
imapd was stopped during upgrade. I checked this by running:
$ sudo /usr/sbin/service status cyrus-imapd
but this did some kind of conversion process before finally telling
me that imapd was stopped:
Converting from /var/lib/cyrus/deli
20 matches
Mail list logo
