Control: severity -1 important
Hey,
I also tried to reproduce the problem with piuparts and it went through
smoothly (1.1.2+dfsg.1-4~bpo8+2 -> 1.1.2+dfsg.1-5 -> 1.1.3+dfsg.1-1). The only
difference is that in that case mysql-server is used instead of mariadb for
piuparts. But the problems with
Processing control commands:
> severity -1 important
Bug #801973 [roundcube] error 255 on package configuration
Severity set to 'important' from 'serious'
--
801973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 + moreinfo unreproducible
Bug #801973 [roundcube] error 255 on package configuration
Added tag(s) moreinfo and unreproducible.
--
801973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Control: tags -1 + moreinfo unreproducible
Any news on that, e-mmanuel? It would be great if we could avoid the
autoremoval from testing ;-)
On Mon, 19 Oct 2015 at 21:15:00 +0200, e-mmanuel wrote:
> the problem occurs on my other server.
> Both are clean (production servers).
FWIW, it's not bec
❦ 12 novembre 2015 18:47 +0100, "e-mman...@proxymail.eu"
:
> In fact, I did the upgrade and got the same error.
> So I have replaced "set -e" by "set -x" in
> /var/lib/dpkg/info/roundcube-core.postinst
> and there was no error.
Previously, did you also replace "set -e" by "set -x"? You need to
In fact, I did the upgrade and got the same error.
So I have replaced "set -e" by "set -x" in
/var/lib/dpkg/info/roundcube-core.postinst
and there was no error.
I did a roundcube purge only from 0.9.5+dfsg1-4.2 to 1.1.1+dfsg.1-1
The output from debconf-get-selections | grep roundcube :
# Mot d
❦ 12 novembre 2015 13:16 +0100, e-mmanuel :
> Same behavior during the upgrade to 1.1.3+dfsg.1-1.
> With "set -x" option in /var/lib/dpkg/info/roundcube-core.postinst,
> the upgrade has no error !
But I suppose that you get a failed upgrade, you add set -x, retry and
it works. I think it would
Hello,
Same behavior during the upgrade to 1.1.3+dfsg.1-1.
With "set -x" option in /var/lib/dpkg/info/roundcube-core.postinst, the
upgrade has no error !
Here is the output :
Paramétrage de roundcube-core (1.1.3+dfsg.1-1) ...
+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ exp
I've just verified on my second server.
No filter or autoresponder installed and I've had the problem on the
upgrade.
Le 03/11/2015 18:57, e-mmanuel a écrit :
Here are my symlinks :
/usr/share/roundcube
0 lrwxrwxrwx 1 root root 46 oct. 6 15:19
plugins/jqueryui/config.inc.php ->
/etc/rou
Here are my symlinks :
/usr/share/roundcube
0 lrwxrwxrwx 1 root root 46 oct. 6 15:19
plugins/jqueryui/config.inc.php ->
/etc/roundcube/plugins/jqueryui/config.inc.php
/var/lib/roundcube
0 lrwxrwxrwx 1 root root 14 sept. 11 08:43 config -> /etc/roundcube/
0 lrwxrwxrwx 1 root root
❦ 3 novembre 2015 10:48 +0100, e-mmanuel :
> But during the upgrade from 0.9.5+dfsg1-4.2 to 1.1.1+dfsg.1-1, I
> purged the roundcube* packages and removed /etc/roundcube because all
> was broken (error 255 too).
>
> Maybe I have forgotten symlinks.
> If you have a list of symlinks to check, let
But during the upgrade from 0.9.5+dfsg1-4.2 to 1.1.1+dfsg.1-1, I purged
the roundcube* packages and removed /etc/roundcube because all was
broken (error 255 too).
Maybe I have forgotten symlinks.
If you have a list of symlinks to check, let me known,
Emmanuel.
❦ 3 novembre 2015 10:13 +0100, e-mmanuel :
> unfortunately, last week, I have forced the upgrade with exit 0 at the
> top of the script on my both servers.
> I'll activate "set -x" for the next upgrade.
>
> It's strange I was the the only one with this bug...
It may be due to a left-over of a
Hello,
unfortunately, last week, I have forced the upgrade with exit 0 at the
top of the script on my both servers.
I'll activate "set -x" for the next upgrade.
It's strange I was the the only one with this bug...
Emmanuel.
❦ 30 octobre 2015 20:57 +0100, Vincent Bernat :
>> Hello,
>> the problem occurs on my other server.
>> Both are clean (production servers).
>> Just for information, I use MariaDB not MySQL.
>
> Hello Emmanuel,
>
> I am also unable to reproduce the issue. Here is what I tried:
>
> From a clean De
❦ 19 octobre 2015 22:15 +0200, e-mmanuel :
> Hello,
> the problem occurs on my other server.
> Both are clean (production servers).
> Just for information, I use MariaDB not MySQL.
Hello Emmanuel,
I am also unable to reproduce the issue. Here is what I tried:
From a clean Debian sid chroot:
Hello,
the problem occurs on my other server.
Both are clean (production servers).
Just for information, I use MariaDB not MySQL.
Emmanuel.
Hi,
On Fri, 16 Oct 2015 at 16:01:21 +0200, e-mmanuel wrote:
> During upgrade of roundcube (from 1.1.2+dfsg.1-4 to 1.1.2+dfsg.1-5),
> aptitude reports errors and upgrade stops.
Hmm odd. The 1.1.2+dfsg.1-4 → 1.1.2+dfsg.1-5 upgrade works just file in a
clean(+dialog) sid chroot:
~# echo 'deb http:
Package: roundcube
Version: 1.1.2+dfsg.1-5
Severity: serious
Justification: 3
Dear Maintainer,
During upgrade of roundcube (from 1.1.2+dfsg.1-4 to 1.1.2+dfsg.1-5),
aptitude reports errors and upgrade stops.
Despite this error, roundcube works but last time (upgrade from
0.9.5+dfsg1-4.2 to 1.1.
19 matches
Mail list logo
