Bug#1009694: debsecan: Support for jessie
Package: debsecan Version: 0.4.20.1 Severity: normal Dear Maintainer, debsecan does not seem to work for jessie anymore: $ debsecan --suite jessie error: while downloading https://security- tracker.debian.org/tracker/debsecan/release/1/jessie: HTTP Error 404: Not Found Are you sure 'jessie' is a Debian codename? Is it because jessie is not officially supported anymore but only by LTS Exended? Warm regards, Tom
Bug#790814: ITP: kanboard -- A PHP project management system with a kanban workflow style interface and various integrations.
Has development on the package already begun? If so, I'm willing to test and give feedback. Warm regards, Tom
Bug#757549: owncloud: DB-Errors on Migration 6.0.3 to 7.0.0
Hi, On 09/08/14 22:45, Jan Wagner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi David, Am 09.08.14 14:04, schrieb David Prévot: Le 09/08/2014 02:12, Tom Fernandes a écrit : Package: owncloud Version: 7.0.0+dfsg-2~bpo70+2 “Please report bugs that you found in the packages to the backports mailinglist[1] and NOT to the Debian BTS!”[2] 1: http://lists.debian.org/debian-backports/ 2: http://backports.debian.org/Instructions/#index6h2 okay - thanks for the information - I wasn't aware of that. I just posted my issue there. […] My OC-instance seems to work fine, but I feel uneasy if the DB-migration executed fine in the end. I did not find a way to re-run the upgrade or to verify the status of the system. Is there a way to check if the upgrade/migration worked correctly? as this is a general question, I think the package maintainer could even answer this question (much more better then the backporter), even if this problem should have been raised on the backports mailing list. Just my 2 cents, Jan. well yes. In case one of the maintainers knows about this question, I'd be greatfull to here about it. warm regards, Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757549: owncloud: DB-Errors on Migration 6.0.3 to 7.0.0
Package: owncloud
Version: 7.0.0+dfsg-2~bpo70+2
Severity: normal
Dear Maintainer,
I upgraded OC from 6.0.3+dfsg-2~bpo70+1 to 7.0.0+dfsg-2~bpo70+2 and then
went to my OC-website. I was prompted for clicking to run the update,
which I did. Then it said there was an error and that I should report
this to the community.
The postgres-log says:
ERROR: relation oc_share_external already exists
STATEMENT: CREATE TABLE oc_share_external (id SERIAL NOT NULL,
remote VARCHAR(512) NOT NULL, share_token VARCHAR(64) NOT NULL,
password VARCHAR(64) NOT NULL, name VARCHAR(64) NOT NULL, owner
VARCHAR(64) NOT NULL, user VARCHAR(64) NOT NULL, mountpoint
VARCHAR(4000) NOT NULL, mountpoint_hash VARCHAR(32) NOT NULL, PRIMARY
KEY(id))
The OC-log reports:
ailed to update database structure (exception 'PDOException' with
message 'SQLSTATE[42P07]: Duplicate table: 7 ERROR: relation
oc_share_external already exists' in
/usr/share/php/Doctrine/DBAL/Connection.php:801 Stack trace: #0
/usr/share/php/Doctrine/DBAL/Connection.php(801): PDO-query('CREATE
TABLE o...') #1 /usr/share/owncloud/lib/private/db/migrator.php(179):
Doctrine\DBAL\Connection-query('CREATE TABLE o...') #2
/usr/share/owncloud/lib/private/db/migrator.php(35):
OC\DB\Migrator-applySchema(Object(Doctrine\DBAL\Schema\Schema)) #3
/usr/share/owncloud/lib/private/db/mdb2schemamanager.php(98):
OC\DB\Migrator-migrate(Object(Doctrine\DBAL\Schema\Schema)) #4
/usr/share/owncloud/lib/private/db.php(320):
OC\DB\MDB2SchemaManager-updateDbFromStructure('/usr/share/ownc...') #5
/usr/share/owncloud/lib/private/app.php(1172):
OC_DB::updateDbFromStructure('/usr/share/ownc...') #6
/usr/share/owncloud/lib/private/app.php(980):
OC_App::updateApp('files_sharing') #7
/usr/share/owncloud/lib/private/app.php(87):
OC_App::checkUpgrade('files_sharing') #8
/usr/share/owncloud/lib/private/app.php(72):
OC_App::loadApp('files_sharing') #9
/usr/share/owncloud/lib/private/updater.php(222): OC_App::loadApps() #10
/usr/share/owncloud/lib/private/updater.php(137):
OC\Updater-doUpgrade('7.0.0.8', '6.0.3.1') #11
/usr/share/owncloud/core/ajax/update.php(35): OC\Updater-upgrade() #12
{main} Next exception 'Doctrine\DBAL\DBALException' with message 'An
exception occurred while executing 'CREATE TABLE oc_share_external
(id SERIAL NOT NULL, remote VARCHAR(512) NOT NULL, share_token
VARCHAR(64) NOT NULL, password VARCHAR(64) NOT NULL, name
VARCHAR(64) NOT NULL, owner VARCHAR(64) NOT NULL, user VARCHAR(64)
NOT NULL, mountpoint VARCHAR(4000) NOT NULL, mountpoint_hash
VARCHAR(32) NOT NULL, PRIMARY KEY(id))': SQLSTATE[42P07]: Duplicate
table: 7 ERROR: relation oc_share_external already exists' in
/usr/share/php/Doctrine/DBAL/DBALException.php:91 Stack trace: #0
/usr/share/php/Doctrine/DBAL/Connection.php(811):
Doctrine\DBAL\DBALException::driverExceptionDuringQuery(Object(PDOException),
'CREATE TABLE o...') #1
/usr/share/owncloud/lib/private/db/migrator.php(179):
Doctrine\DBAL\Connection-query('CREATE TABLE o...') #2
/usr/share/owncloud/lib/private/db/migrator.php(35):
OC\DB\Migrator-applySchema(Object(Doctrine\DBAL\Schema\Schema)) #3
/usr/share/owncloud/lib/private/db/mdb2schemamanager.php(98):
OC\DB\Migrator-migrate(Object(Doctrine\DBAL\Schema\Schema)) #4
/usr/share/owncloud/lib/private/db.php(320):
OC\DB\MDB2SchemaManager-updateDbFromStructure('/usr/share/ownc...') #5
/usr/share/owncloud/lib/private/app.php(1172):
OC_DB::updateDbFromStructure('/usr/share/ownc...') #6
/usr/share/owncloud/lib/private/app.php(980):
OC_App::updateApp('files_sharing') #7
/usr/share/owncloud/lib/private/app.php(87):
OC_App::checkUpgrade('files_sharing') #8
/usr/share/owncloud/lib/private/app.php(72):
OC_App::loadApp('files_sharing') #9
/usr/share/owncloud/lib/private/updater.php(222): OC_App::loadApps() #10
/usr/share/owncloud/lib/private/updater.php(137):
OC\Updater-doUpgrade('7.0.0.8', '6.0.3.1') #11
/usr/share/owncloud/core/ajax/update.php(35): OC\Updater-upgrade() #12
{main})
My OC-instance seems to work fine, but I feel uneasy if the DB-migration
executed fine in the end.
I did not find a way to re-run the upgrade or to verify the status of
the system.
Is there a way to check if the upgrade/migration worked correctly?
Warm regards and thanks for the good work,
Tom
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages owncloud depends on:
ii fonts-font-awesome 3.2.1~dfsg-2~bpo7+1
ii fonts-liberation 1.07.2-6
ii fonts-linuxlibertine 5.1.3-1
ii fonts-lohit-deva 2.5.1-1
ii fonts-sil-gentium-basic 1.1-5
ii fonts-wqy-microhei 0.2.0-beta-2~bpo70+1
ii libjs-chosen 0.9.11-1~bpo7+1
ii libjs-dojo-dojox 1.7.2+dfsg-1
ii libjs-jcrop 0.9.12+dfsg-1~bpo70+1
ii libjs-jquery-minicolors
Bug#729488: npm: Please add a NPM backport for wheezy
Package: npm Severity: wishlist Hi everybody, It's wonderful, that Node.js exists as a backport for wheezy, but NPM is not there. Backporting it is tedious as it has lots of reverse dependencies. Upstream included NPM in their node.js package: https://github.com/joyent/node/issues/2083 AFAIK lots of people use NPM when they use Node.js. Would you mind to also backport NPM for wheezy? Or is there a simple way to build all the reverse dependencies? Warm regards and thanks for the good work, Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668511: Kernel panic with bridge networking
Hi, I was experiencing the same panics. Massimo pointed me to the changelog of 3.2.32 and commit bfa539657d2f54ed7f584e0577a37d4e06c2d959 which seemed to have fixed the issue. I'm running linux-image-3.2.0-4-amd64=3.2.32-1 for around 3 weeks now and haven't experienced the panics any more. warm regards, Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675913: ldirectord failed to start, RFC2553 compatible getaddrinfo/getnameinfo
Package: resource-agents
Followup-For: Bug #675913
Hi,
I'm hitting the same bug. It's present in the version in testing (1:3.9.2-5) and
in the version in unstable (1:3.9.3+git20121009-1).
I modified the initially attached patch as the offsets did not apply any more
for the current verion in testing and tested it. It seems to work correctly
although I haven't done intesive testing yet.
Zang - where does this patch come from and are you running it in production use?
I'm not in the position to dive into the code that deep to verify, that it
doesn't have any side effects.
As the issue still persists in version 1:3.9.3+git20121009-1 it looks like that
upstream hasn't yet fixed this issue.
It would be nice to have a working HA-stack for wheezy :-) .
warm regards and thanks for the good work,
Tom
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- resource-agents-3.9.2.orig/ldirectord/ldirectord.in
+++ resource-agents-3.9.2/ldirectord/ldirectord.in
@@ -828,7 +828,8 @@ use Pod::Usage;
#use English;
#use Time::HiRes qw( gettimeofday tv_interval );
use Socket;
-use Socket6;
+use Socket::GetAddrInfo qw( getaddrinfo getnameinfo NI_NUMERICHOST NI_NUMERICSERV NI_NAMEREQD );
+#use Socket6;
use Sys::Hostname;
use POSIX qw(setsid :sys_wait_h);
use Sys::Syslog qw(:DEFAULT setlogsock);
@@ -5039,17 +5040,21 @@ sub ld_gethostbyname
if ($name =~ /\[(.*)\]/) {
$name = $1;
}
- my @host = getaddrinfo($name, 0, $af);
- if (!defined($host[3])) {
- return undef;
- }
- my @ret = getnameinfo($host[3], NI_NUMERICHOST | NI_NUMERICSERV);
- if ($host[0] == AF_INET6) {
- return [$ret[0]];
- }
- else {
- return $ret[0];
- }
+ my %hints = ( family = $af );
+ my ( $err, @res ) = getaddrinfo($name, 0, \%hints);
+ return undef if ($err);
+ while( my $ai = shift @res ) {
+my ( $err, $hostname, $servicename ) = getnameinfo( $ai-{addr} );
+if (!$err) {
+ if ($ai-{family} == AF_INET6) {
+return [$hostname];
+ }
+ else {
+return $hostname;
+ }
+}
+ }
+ return undef;
}
# ld_gethostbyaddr
@@ -5064,13 +5069,12 @@ sub ld_gethostbyaddr
my ($ip)=(@_);
$ip = ld_strip_brackets($ip);
- my @host = getaddrinfo($ip,0);
- if (!defined($host[3])) {
- return undef;
+ my ( $err, @res ) = getaddrinfo($ip,0);
+ return undef if ($err);
+ while( my $ai = shift @res ) {
+my ( $err, $host, $service ) = getnameinfo($ai-{addr}, NI_NAMEREQD);
+return $host unless($err);
}
- my @ret = getnameinfo($host[3], NI_NAMEREQD);
- return undef unless(scalar(@ret) == 2);
- return $ret[0];
}
# ld_getservbyname
Bug#684147: nodejs: FTBFS on testing (wheezy) due to test-regress-GH-1697.js
Package: nodejs Version: 0.6.19~dfsg1-4 Severity: normal Hi, nodejs fails to build in a wheezy chroot. When I remove test/simple/test-regress-GH-1697.js it builds just fine. ---8-- === release test-regress-GH-1697 === Path: simple/test-regress-GH-1697 Server running. events.js:48 throw arguments[1]; // Unhandled 'error' event ^ Error: listen EADDRINUSE at errnoException (net.js:670:11) at Array.0 (net.js:771:26) at EventEmitter._tickCallback (node.js:190:39) events.js:48 throw arguments[1]; // Unhandled 'error' event ^ Error: write ECONNRESET at errnoException (net.js:670:11) at Object.afterWrite [as oncomplete] (net.js:503:19) Command: out/Release/node /usr/src/nodejs/nodejs-0.6.19~dfsg1/test/simple/test-regress-GH-1697.js [01:53|% 100|+ 350|- 1]: Done make[1]: *** [test] Error 1 make[1]: Leaving directory `/usr/src/nodejs/nodejs-0.6.19~dfsg1' make: *** [debian/stamp-makefile-check] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Build command 'cd nodejs-0.6.19~dfsg1 dpkg-buildpackage -b -uc' failed. E: Child process failed ---8-- warm regards, Tom -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592954: No support for file:/ based repos
Package: apt-cacher-ng Version: 0.5.2-1 Severity: wishlist Tags: upstream Hi, When having a local repository on the host apt-cacher-ng is running on, for now, one has to install a webserver on that host to enable apt-cacher-ng to serve those packages. This is not a problem - but just using a webserver as an interface for something which can be done with filesystem-based commands seems kind of superflous to me. It would be nice if apt-cacher-ng could also serve files from a local repo via a file:/ URL. thanks for the good work! Tom -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686+toi (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#472453: please include upstream CHANGELOG and FAQ files
Package: pound Version: 2.4-2 Severity: wishlist Hi, the upstream tarball includes a CHANGELOG and FAQ file. It would be nice if those would be in the debian package as well. thanks, Tom -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.utf8) Shell: /bin/sh linked to /bin/bash Versions of packages pound depends on: ii libc6 2.7-4 GNU C Library: Shared libraries ii libpcre3 7.6-2 Perl 5 Compatible Regular Expressi ii libssl0.9.8 0.9.8g-3 SSL shared libraries pound recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399996: [pkg-kolab] Bug#399996: kolab-cyrus-common: the squatter parameter is missing from cyrus.conf
Hi, On Thursday, 23. November 2006 05:20, Benoit Mortier wrote: Package: kolab-cyrus-common Version: 2.2.12-8 Severity: normal The cyrus.conf is missing the squatter parameter # index generation squatter cmd=/usr/sbin/squatter -v -r user period=1440 This build index, improve performance and get rid of the squatter messages hmm - not sure if this is really a good idea to make it a default setting. It is not a default setting in cyrus-imapd=2.2.13-9 and there's probably a reason for that. The cyrus maintainers might be able to explain why it's not enabled as default. Therefore CC'ing. Some reasons I can image is that for a small setup squatting might not be needed. For a large setup squatting (creating the indexes) takes _a long_ time. So IMHO it should be up to the administrator to enable or disable it. The cyrus maintainers have the following lines in their cyrus.conf: ---8--- # indexing of mailboxs for server side fulltext searches # reindex changed mailboxes (fulltext) approximately every other hour #squatter_1 cmd=/usr/bin/nice -n 19 /usr/sbin/squatter -s period=120 # reindex all mailboxes (fulltext) daily #squatter_a cmd=/usr/sbin/squatter at=0517 ---8 thanks, Tom
Bug#354221: xserver-xorg: confirming freezes with radeon driver
Package: xserver-xorg Version: 1:7.0.22 Followup-For: Bug #354221 Hi, I am not sure if I should open a new bugreport on my issue, but this one seems actually the most appropriate one to add my information as the problem is similar. System gets locked up with xorg 7.0.22. I did a fresh install so I don't know if these problems would have also occured with previous versions. Locked up means: no Ctrl-Alt-Backspace, no pinging over network, no mouse, no keyboard. I mainly found the freezes occuring when using firefox - sometimes even at the exact same point. From what I heard firefox uses acceleration. This might be related to #319263. But in gerneal the system freezes now and then. So I set NoAccel to true and since then I didn't experience a single freeze. Before I had at least 1-2 freezes a day and I didn't experience any freeze for about 2 weeks now. Uncommenting DRI or GLX didn't work for me AFAIR - I think I tried all possible combination of disabling the one and enabling the other or disabling them alltogether. Using the ATI driver did not help either. There's another bugreport which might be related: https://bugs.freedesktop.org/show_bug.cgi?id=6429 [EMAIL PROTECTED]:~$ lspci | grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY [EMAIL PROTECTED]:~$ uname -r 2.6.17-1-686 If you need any other info, let me know. Thanks for the good work, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370024: [pkg-kolab] Bug#370024: kolab-webadmin doesn't depend on kolabd
Hi, the default kolab-webadmin design doesn't put a lot of load on the server and there is usually an apache installed on the server for freebusy anyways. On the other hand it is definitely not compulsory to have the AF on the Kolab-server. It is stricktly speaking just another (Kolab-specific) LDAP client like phpldapadmin (which can also do kolab administration btw.). So it's kind of tricky. To be on the safe side I would not set a dependency - but let's gather some more opinions... Tom On Monday 05 June 2006 16:01, Noèl Köthe wrote: Am Freitag, den 02.06.2006, 11:14 -0700 schrieb Johannes Graumann: Hello Johannes, I'm really happy about your continuous help/suggestions to the packages! Kolab-webadmin does not depend on kolabd, which keeps e.g. apache2 installed in the case of a kolabd purge. Should be fixed. During packaging we thought about this. We didn't depend on kolabd because maybe you/people want to install the webfrontend on a different machine than the server is runing. Do you think this could be typical? If not, I agree the dependency should be set.
Bug#370529: [pkg-kolab] Bug#370529: README.Debian clarification: postmap
Hi, On Monday 05 June 2006 19:21, Johannes Graumann wrote: Package: kolabd Version: 1.9.4dfsg-3 Severity: normal Tags: patch Code example on how to create missing postfix lookup tables is cryptic and unintelligible to the novice (including me). The main problem is that this is bashism - this e.g. doesn't work in ksh. IMHO this is not a bug with a normal severity but rather with a minor though. Proposed change: 360c360 # ^touch^postmap^ it does look neat though, right? :) [...] Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368124: kolab-cyrus-imapd: Please include README.Debian.debug (and possibly other helpfull README's) in the package again
Package: kolab-cyrus-imapd Version: 2.2.12-7 Severity: minor Hi Kolab gods :), please include the README.Debian.debug in the package again. It is quite an important and helpfull document and it's a pain to always get it from the cyrus-imapd package when needed. Please also check if other README's were thrown out in the build process of these packages. As long as the README's are relevant to the kolab-cyrus-imapd as well they should remain in the package IMHO. Thanks, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368143: kolab-cyrus-imapd: renaming of the init script, the default script, cronjob, etc.
Package: kolab-cyrus-imapd Version: 2.2.12-7 Severity: minor Hoi, Not too sure if this is a bug - please judge and close if invalid. The init script, the script in /etc/default, the cronjob and some others are prefixed with kolab. They are e.g. named /etc/init.d/kolab-cyrus The cyrus script is named /etc/init.d/cyrus In the end the kolab-cyrus package is yet another cyrus package. So shouldn't the names of the scripts stick to the original ones if possible to make the fork as small as possible? On the other hand one might argue, that the scripts should have the package names name to keep things clear. warm regards, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367981: slapd: init script lacks PATH variable
Package: slapd Version: 2.2.26-5 Severity: normal Hi, slapd's init script lacks the PATH variable. Like this it is not possible to let the init script run through cron unless you declare the PATH in either the cronjob or include it in the init script. Not having the correct PATH set might also cause unwanted behaviour when using it in different environments like sudo. Please include something like PATH=/bin:/usr/bin:/sbin:/usr/sbin in /etc/init.d/slapd. Thanks for the good work, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360710: ingo1: missing directory scripts/sql
Package: ingo1 Severity: normal Hi, It seems like the upstream directory scripts/sql is missing from the package. It should probably go into /usr/share/doc/ingo1/examples/scripts/ Thanks, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360189: turba2: new upstream version 2.1 out
Package: turba2 Severity: wishlist Hi, By now the main horde packages from the 3.1 framework are out. Turba is still missing though. It would be nice to have turba updated soon as this package is essential for a lot of horde setups. Thanks for all the work, Tom -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356526: New upstream release
Package: horde3 Version: 3.0.4-4sarge2 Severity: wishlist Hello, There's a new Horde stable release out with several interesting kolab related bugfixes. Could you please update you package? Thanks and regards, Tom Fernandes -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages horde3 depends on: ii apache2-mpm-prefork [httpd] 2.0.54-5traditional model for Apache2 ii libapache-mod-php4 [phpapi-2 4:4.3.10-16 server-side, HTML-embedded scripti ii libapache2-mod-php4 [phpapi- 4:4.3.10-16 server-side, HTML-embedded scripti ii php4 4:4.3.10-16 server-side, HTML-embedded scripti ii php4-cli [phpapi-20020918] 4:4.3.10-16 command-line interpreter for the p ii php4-domxml 4:4.3.10-16 XMLv2 module for php4 ii php4-pear4:4.3.10-16 PEAR - PHP Extension and Applicati ii php4-pear-log1.6.0-1.1 Log module for PEAR -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356527: New upstream release
Package: imp4 Version: 4.0.2-2 Severity: wishlist Hello, There's a new upstream release out with a lot of new features and some bugfixes - could you please update your package? Thanks and regards, Tom Fernandes -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages imp4 depends on: ii horde3 3.0.4-4sarge2 horde web application framework ii php4-imap 4:4.3.10-16 IMAP module for php4 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356527: Bug#356526: New upstream release
Hi, On Sunday 12 March 2006 21:45, Ola Lundqvist wrote: Hi On Sun, Mar 12, 2006 at 05:05:36PM +0100, Tom Fernandes wrote: Package: horde3 Version: 3.0.4-4sarge2 Severity: wishlist Hello, There's a new Horde stable release out with several interesting kolab related bugfixes. Could you please update you package? Thanks and regards, Tom Fernandes What version are you referring to. 3.0.9 or later? I was referring to the horde release 3.1 that came out a few days back. That release has some bugifxes which enables the Kolab functionality again which was completely broken for months. Some fixes have gone into horde, some into kronolith and the other modules. To use horde as a webclient for the new Kolab packages from debian/alioth you need Horde 3.1. thanks for your good work, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353404: dovecot-imapd: wrong depends: should depend on dovecot-common=1.0.beta2-1
Package: dovecot-imapd Version: 1.0.beta2-1 Severity: important After upgrading from 1.0.alpha5-1 to 1.0.beta2-1 I got the following error: Warning: imap-login: Waiting for SSL parameter file /var/run/dovecot/ssl-parameters.dat and wasn't able to login via imaps anymore. This file should be automatically generated by /usr/sbin/dovecot. With the dovecot binary of 1.0.alpha5-1 it's not possible to create the appropriate file. /usr/sbin/dovecot version 1.0.alpha5-1 doesn't support --build-ssl-parameters - the binary of 1.0.beta2-1 does though. Running both - dovecot-imapd and dovecot-common version 1.0.beta2-1 works. btw. --build-ssl-parameters has been dropped again in beta3. thanks, Tom -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages dovecot-imapd depends on: ii dovecot-common 1.0.beta2-1 secure mail server that supports m ii libc62.3.5-13GNU C Library: Shared libraries an ii libssl0.9.8 0.9.8a-6SSL shared libraries -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312700: any progress?
Hi, I'm also curious if there's already a package ready for testing, regards, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
