Bug#410172: version missing on libnet-server-perl dependency
Package: amavisd-new Version: 2.4.2-5 While trying to update amavisd failed to restart: Setting up amavisd-new (2.4.2-5) ... Creating/updating amavis user account... Starting amavisd: Net::Server version 0.87 required--this is only version 0.85 at /usr/sbin/amavisd-new line 6405. BEGIN failed--compilation aborted at /usr/sbin/amavisd-new line 6405. (failed). invoke-rc.d: initscript amavis, action start failed. libnet-server-perl version was 0.85-3 Upgrading libnet-server-per to new version (apt-get install libnet-server-perl ; version installed 0.94-1) fixed the problem. Therefore, I think that amavisd-new dependency on libnet-server-perl should include version (= 0.87) i guess. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
Henrique de Moraes Holschuh wrote: severity 410172 wishlist tag 410172 wontfix thanks On Thu, 08 Feb 2007, Aidas Kasparas wrote: libnet-server-perl version was 0.85-3 Sarge has libnet-server-perl 0.87-3 (in fact, 0.87-3sarge1), according to packages.qa.debian.org/libnet-server-perl. Direct upgrades from releases earlier than Sarge to Etch are not supported, so I am downgrading this bug to a wishlist request. Since the depends in libnet-server-perl are currently unversioned, I will not add a version to it unless it is necessary. Therefore, this request won't be addressed at this time. Henrique, please help me understand reasons of such decision (and don't repeat mistake I did by reporting this bug)? Why dependency without version is better than dependency with version? If uplink cared to code: use Net::Server 0.87; # need Net::Server::PreForkSimple::done he has very good reason to indicate that version 0.87 will not work. So why should debian package? And regarding from releases earlier than Sarge... am I the last person, who upgrades packages from testing just when he need some new feature or sees security report? I tought, if dependency was versioned, some person like me would be saved from trouble while upgrading. So, where my tought are wrong? -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
Henrique de Moraes Holschuh wrote: On Thu, 08 Feb 2007, Aidas Kasparas wrote: And regarding from releases earlier than Sarge... am I the last person, who upgrades packages from testing just when he need some new feature or sees security report? I tought, if dependency was versioned, some person like me would be saved from trouble while upgrading. libnet-server-perl (0.85-3) unstable; urgency=low * debian/control: depends on libio-multiplex-perl (closes: #192921) -- Luca Filipozzi [EMAIL PROTECTED] Sat, 17 May 2003 16:00:32 -0700 Please explain to me how you had the above package installed in a Debian Sarge system. Sarge was released on 2005, and has version 0.87. It should have been upgraded at that time, when Sarge was made the Debian Stable release. This is what I don't understand. Did you upgrade from something that was not a pure, official Debian install at some time in the past? Well, that box was installed about 4 years ago (hardware was produced 2003-02). I guess it was installed from [Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-1 (20020718)] (commented line in sources.list). Then packages from testing were added. And later it was upgraded on package by package basis as needed. No upgrade to some formal stable release was made (reasons it should?). -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387404: hylafax: FTBFS: make: *** [install-doc] Error 1
Andreas, what are your umask settings? Just give command umask. If it gives anything but 022, then issue umask 022 before building and tell us if that changes anything. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383988: /dev/stderr is used but not allways present on the system
Package: dbconfig-common
Version: 1.8.20
Severity: important
Justification: dependant packages could not be installed on affected systems
Tags: patch
Not all systems have /dev/stderr symlinks. But
/usr/share/dbconfig-common/internel/common uses this file to redirect
output to stderr (I have couple systems with custom compiled 2.6.9 which
do not have these symlinks). As a consequence I was unable to install
otrs2 package (I believe others would fail too):
Setting up otrs2 (2.0.4p01-12) ...
dbconfig-common: writing config to /etc/dbconfig-common/otrs2.conf
Replacing config file /etc/otrs/database.pm with new version
/usr/share/dbconfig-common/internal/common: line 14: /dev/stderr:
Permission denied
/usr/share/dbconfig-common/internal/common: line 29: /dev/stderr:
Permission denied
/usr/share/dbconfig-common/internal/common: line 14: /dev/stderr:
Permission denied
/usr/share/dbconfig-common/internal/common: line 29: /dev/stderr:
Permission denied
/usr/share/dbconfig-common/internal/common: line 14: /dev/stderr:
Permission denied
/usr/share/dbconfig-common/internal/common: line 29: /dev/stderr:
Permission denied
/usr/share/dbconfig-common/internal/common: line 14: /dev/stderr:
Permission denied
dpkg: error processing otrs2 (--configure):
subprocess post-installation script returned error exit status 1
Please find attached patch which will not depend on presence of these
special symlinks. Applying this patch allowed me to install
aforementioned package.
--
Aidas Kasparas
IT administrator
GM Consult Group, UAB
--- common.R2006-08-21 12:26:10.734720687 +0300
+++ common 2006-08-21 12:26:32.782215689 +0300
@@ -11,7 +11,7 @@
dbc_logpart(){
# for the time being, at least, let's default to verbose
#if [ $dbc_debug ]; then
- echo -ne $@ /dev/stderr
+ echo -ne $@ 2
#fi
if [ $dbc_log ]; then
dbc_log=$dbc_log $@
@@ -26,7 +26,7 @@
dbc_logline(){
# for the time being, at least, let's default to verbose
#if [ $dbc_debug ]; then
- echo -e [EMAIL PROTECTED] /dev/stderr
+ echo -e [EMAIL PROTECTED] 2
#fi
if [ $dbc_log ]; then
dbc_log=$dbc_log [EMAIL PROTECTED]
Bug#355224: All .rml files are missing
Package: tinyerp-server Version: 3.2.1-1 Severity: important Justification: No raport/other document could be produced After purge and reinstall neither find /usr/lib/python2.3/site-packages/tinyerp-server/ -name \*.rml -ls nor dpkg -L tinyerp-server|grep '.rml$' produce any output. While tar ztf tinyerp-server-3.2.1.tgz |grep '.rml$' produce 15 lines with various documents/reports to be printed. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344921: Maybe libpaper1 should be in Pre-Depends:
If hylafax-client depends on libpaper1 to be configured, then maybe it should be not in Depends: , but in Pre-Depends: ? -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341398: Please, post backtraces
Hi, If you get racoon to disapear, please run under gdb, add -F option (to stay in foreground) and post backtrace. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341398: Can not reproduce
tags 341398 + moreinfo unreproducible thanks I see you're using non standard kernel. Can you reporoduce the same problem with standard kernel? I was unable to reproduce with 2.6.14-2-686. Can you state what kind of ipsec policies you have in place? Are you using any other tools which use pfkey sockets, or alter SPD in other ways? -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326785: Fails to start when socket file is present
Package: courier-filter-perl Version: 0.16 Severity: important When system running courier-filter-perl crashes (for example due to power failure) and boots, the following error is reported, filter is not started and all the messages are temporary rejected with the reason 432 Mail filters temporarily unavailable. Sep 1 03:04:58 sizifas courierfilter: Socket /var/lib/courier/allfilters/pureperlfilter already exists at /usr/share/courier-filter-perl/perl5/Courier/Filter.pm line 299. IMHO eihter courier-filter-perl ackage should work around leftover sockets or courier-mta package should provide some means of cleaning /var/lib/courier/allfilters directory uppon system boot. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#310327: patch
Please find bellow a patch which check EOF condition instead of no
input. Without fix for this bug package is virtually not useable (I
experienced mysterious attachment cuts, so I can not relay on it at it's
present form :-( Please consider importance of this bug as serious at
the very least.
--- ssmtp.c.R 2005-08-25 19:41:15.0 +0300
+++ ssmtp.c 2005-08-25 19:45:11.0 +0300
@@ -1532,7 +1532,13 @@
stdio functions like fgets in the first place */
fcntl(STDIN_FILENO,F_SETFL,O_NONBLOCK);
- while(fgets(buf, sizeof(buf), stdin)) {
+ while(!feof(stdin)) {
+ if (!fgets(buf, sizeof(buf), stdin)) {
+ /* if nothing was received, then no transmission
+* over smtp should be done */
+ sleep(1);
+ continue;
+ }
/* Trim off \n, double leading .'s */
standardise(buf);
- 8
--
Aidas Kasparas
IT administrator
GM Consult Group, UAB
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317974: ERROR: IPComp SPI size promoted from 16bit to 32bit
Stefan, Can you confirm that version is 0.5.2-1 on both ends? Or 0.5.2-1 do not want to play well with 0.6 on the other end? -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#310966: Debian Bug#310966: racoon don't work with Win-XP-Clients
Ganesan, Are configure's parameters the same across 0.5 .. 0.5.2 versions? Maybe some feature not-compiled produce this effect? Ganesan Rajagopal wrote: Hi, This problem is reported against ipsec-tools 0.5.2. The submitter claims that it was broken in 0.5 but working in 0.5.1. AFAIK, 0.5.2 has only bug fixes and I can't imagine anything in 0.5.2 that can break interoperability with WinXP. Has anyone else seen a similar report? Daniel, is the new problem identical to the one described at http://www.spenneberg.de/3715.html. I don't grok German but this log looks suspicicious. Apr 1 09:28:19 localhost racoon: ERROR: such policy does not already exist: 192.168.70.0/24[0] 145.254.79.xxx/32[0] proto=any dir=out Ganesan -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308976: On PPP side use unique insted of require
On PPP side change require to unique and everything will start working. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305616: ipsec-tools_1:0.5.1-1: FTBFS with gcc-4.0
I have commited fix for compilation with gcc-4.0 to the upstream CVS (0.5, 0.6 and Head branches). You can get it from sourceforge.net's cvs in couple of hours. And these fixes will be included in upcoming 0.5.2 version. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303573: Regression: Tabs in configuration cause setkey to fail
OK, I have reproduced this bug with setkey found in 0.5-5 deb. Only I had to press/ ask perl to write \t twice in the row. It appears, that directory listing is given if readline is compiled into setkey, and do not apears, if it is not. Therefore, there is a quick workaround to disable readline support. But, do we really need to go this way? Although I understand that there is no need to get file completion during setkey operation, how does it harm? 1) if setkey's operations are taken from file, then setkey should be invoked with -f option, not -c; in that case it ignores all \t even if it is compiled with readline; 2) if setkey is used interactively and user accidentally hits \t [twice] it can continue to enter his/her command and that command will be executed correctly; 3) if setkey -c is used in scripts to supply commands via pipe and command stream contains [double]\t then output will be clutered with filesystem data, yet settings will be set correctly. [Maybe it is possible to modify program which supplies commands to skip tabs, o even to sed tabs out?] Therefore questions: a) in which scenario tabs causes you problems? b) if that break is in code supplied by ipsec-tools debian package, then where exactly this is? c) is the severity of this bug really important? I promise to start discussion on this issue upstream, as file completion should not be in setkey anyway. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303573: Regression: Tabs in configuration cause setkey to fail
I can not reproduce this bug with package version you've indicated. Could you please provide more info: - what shell do you use; - are you really invoking ipsec-tools' setkey and not something builtin or some your script (which setkey); - what are your environment settings (maybe there is some environment variable which changes readline's behaviour) -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296557: uploaded 1:0.5-3 fixed this bug
package ipsec-tools tags 296557 +fixed -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296079: rename ipsec.conf to spd.boot
I suggest to name that file spd.boot . It would better describe what's inside. And by the way, there may be more spd.* files. For example, one to [change and] use when ppp connection is established. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290636: Localization do not honor LC_NUMERIC (maybe others)
Package: openoffice.org-l10n-lt Version: 1.1.3-4 Decimal separator is selected only on LANG environment variable basis. It does not allow to override numeric (any?) aspects of environment with LC_NUMERIC (LC_xxx) variables. In lt locale decimal separator is comma (,). I need it be period (.) and therefore I have LC_NUMERIC=C set. StarCalc do not take that into account: export LANG=lt_LT.UTF-8 scalc in cell enter: =2.2+2.3 result will be 76771 expected result 4.5 If I enter =2,2+2,3 I get 4,5 if I start scalc with LANG=C, it works as expected (result 4.5) Environment: $ locale LANG=lt_LT.UTF-8 LC_CTYPE=lt_LT.UTF-8 LC_NUMERIC=C LC_TIME=lt_LT.UTF-8 LC_COLLATE=lt_LT.UTF-8 LC_MONETARY=lt_LT.UTF-8 LC_MESSAGES=lt_LT.UTF-8 LC_PAPER=lt_LT.UTF-8 LC_NAME=lt_LT.UTF-8 LC_ADDRESS=lt_LT.UTF-8 LC_TELEPHONE=lt_LT.UTF-8 LC_MEASUREMENT=lt_LT.UTF-8 LC_IDENTIFICATION=lt_LT.UTF-8 LC_ALL= $ dpkg -l openoffice.org-\*|grep '^i' ii openoffice.org 1.1.3-4OpenOffice.org office suite binary files ii openoffice.org 1.1.3-3+1 Debian specific parts of OpenOffice.org ii openoffice.org 1.1.3-4English (US) language package for OpenOffice ii openoffice.org 1.1.3-4Lithuanian language package for OpenOffice.o -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
