Hello,
php-pear isn't installed.
In https://packages.debian.org/stretch/roundcube, php-pear is not a dependance,
the solution seems simply to set php-pear as dependance ofroundcube-core
Emmanuel.
Hey,
Thanks for digging intothe problem.
Can you check if php-pear is installed? And if not install it and retest it?
Regards,
sandro
--
Am Montag, 11. Januar 2016, 19:28:56 schrieb e-mmanu...@proxymail.eu:
> In /usr/share/roundcube/program/lib/Roundcube/bootstrap.php
> this line crashs the sc
In /usr/share/roundcube/program/lib/Roundcube/bootstrap.php
this line crashs the script :
@PEAR::setErrorHandling(PEAR_ERROR_CALLBACK, 'rcube_pear_error');
Then, I comment this line and run :
DEBIAN_PKG=TRUE RCMAIL_CONFIG_DIR=/etc/roundcube /usr/bin/php
/usr/share/roundcube/bin/update.sh --versi
Hey,
> Here is the path :
> /usr/share/roundcube/program/include/clisetup.php
okay can you now add some echos in the file to get an idea till what lines it's
running?
Regards,
sandro
signature.asc
Description: This is a digitally signed message part.
Here is the path :
/usr/share/roundcube/program/include/clisetup.php
Emmanuel.
PS : my previous email is disabled (trash mail) so I've created a new one.
No problem for me to read your reponse, I check bugs.debian.org
Le 07/01/2016 22:02, e-mmanu...@proxymail.eu a écrit :
Yes the path is fully
Hey,
> Yes the path is fully correct.
can you just add some echos in the file INSTALL_PATH . 'program/include/
clisetup.php' , to get an idea what path is taken?
Regards,
sandro
PS: I get like Vincent errors when sending you an email - how the hell you
read these mails ?
: host smtp.trashma
Yes the path is fully correct.
Hey,
can you echo also the INSTALL_PATH? and check if it correct?
Regards,
sandro
--
Am Thursday 07 January 2016, 21:20:03 schrieb e-mmanu...@proxymail.eu:
> >> + DEBIAN_PKG=TRUE RCMAIL_CONFIG_DIR=/etc/roundcube /usr/bin/php
> >> /usr/share/roundcube/bin/update.sh --version=1.1.3 --accept=true
+ DEBIAN_PKG=TRUE RCMAIL_CONFIG_DIR=/etc/roundcube /usr/bin/php
/usr/share/roundcube/bin/update.sh --version=1.1.3 --accept=true
What happens if you run this command manually (as root)? It's a bit odd
that it fails without saying anything.
=> nothing. No output.
When I add this echo in update
❦ 5 janvier 2016 23:14 +0100, Vincent Bernat :
>> + DEBIAN_PKG=TRUE RCMAIL_CONFIG_DIR=/etc/roundcube /usr/bin/php
>> /usr/share/roundcube/bin/update.sh --version=1.1.3 --accept=true
>
> What happens if you run this command manually (as root)? It's a bit odd
> that it fails without saying anythi
❦ 5 janvier 2016 20:59 +0100, "e-mman...@proxymail.eu"
:
> + DEBIAN_PKG=TRUE RCMAIL_CONFIG_DIR=/etc/roundcube /usr/bin/php
> /usr/share/roundcube/bin/update.sh --version=1.1.3 --accept=true
What happens if you run this command manually (as root)? It's a bit odd
that it fails without saying an
Sorry for the delay, I was waiting a new version to test on my server.
Unfortunately, I still have the problem.
Here are the informations :
roundcube-core's dependencies :
roundcube-core
Dépend: dbconfig-common
|Dépend: debconf
Dépend:
cdebconf
debconf
Dépend: ucf
|Dépend: liba
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
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.
29 matches
Mail list logo
