Bug#557568: db4.7_load.1, .SH NAME: standart in - standart input
Package: db4.7-util Version: 4.7.25-8 Severity: minor Tags: patch File: /usr/share/man/man1/db4.7_load.1.gz I think standart input is a bit more meaningful. --- db4.7_load.12009-11-22 23:45:38.0 +0300 +++ db4.7_load.1.patched2009-11-22 23:46:23.0 +0300 @@ -2,7 +2,7 @@ .\ documentation by Thijs Kinkhorst th...@kinkhorst.com. .TH DB4.7_LOAD 1 7 August 2007 .SH NAME -db4.7_load \- Load data from standard in +db4.7_load \- Load data from standard input .SH SYNOPSIS .B db4.7_load [-nTV] [-c name=value] [-f file] [-h home] [-P password] [-t btree | hash | queue | recno] file -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555716: Wrong description. Are there header files?
Package: libcap-ng0 Version: 0.6.2-3 Severity: normal One line prior to last line of description states: This package contains header files and libraries for libcap-ng. Doesn't header files usually reffers to *.h include files? -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555494: dh_strip doesn't prevent leakage of the build directory.
Package: debhlper
Version: 7.4.3
Severity: wishlist
Version 2.9.27 of libc6 has the following item in
changelog.Debian.gz:
Strip *.o files manually (dh_strip does not do it) to prevent
leakage of the build directory.
According to
http://lists.debian.org/debian-glibc/2009/11/msg00089.html,
the code is:
find . -name \*crt\*.o -exec objcopy
--only-keep-debug '{}' ../$(libc)-dbg/usr/lib/debug/'{}'
';' || true;
find . -name \*crt\*.o -exec objcopy
--add-gnu-debuglink=../$(libc)-dbg/usr/lib/debug/'{}'
'{}' ';' || true);
find debian/$(curpass) -name \*crt\*.o -exec
strip --strip-debug --remove-section=.comment
--remove-section=.note --strip-unneeded '{}' ';' || true;
Is it possible to have similar lines in dh_strip?
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538173: nut.init: /wait_delay/s:default/nut:nut/nut.conf:
This should solve it: --- /etc/init.d/nut 2009-07-27 02:50:53.0 +0200 +++ debian/nut.init 2009-11-05 19:35:36.0 +0200 @@ -160,7 +160,7 @@ poweroff) flag=`sed -ne 's#^ *POWERDOWNFLAG *\(.*\)$#\1#p' /etc/nut/upsmon.conf` -wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p' /etc/default/nut` +wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p' /etc/nut/nut.conf` if [ -f $flag ] ; then if $upsmon -K /dev/null 21 ; then log_daemon_msg Shutting down the UPS ... -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551867: iptables.8 has an obscure single f letter
Package: iptables Vesrion: 1.4.4-2 Severity: minor File: /usr/share/man/man8/iptables.8.gz That man page has an obscure single f letter: length This module matches the length of the layer-3 payload (e.g. layer-4 packet) f a packet against a specific value or range of values. [!] --length length[:length] -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551444: /usr/share/doc/vsftpd/: examples - debconf
Package: vsftpd Version: 2.2.0-3 Severity: wishlist The name of the directory /usr/share/doc/vsftpd/examples is a bit confusing. More so when there is also upstream EXAMPLE directory. Please rename it to debconf or debconf-examples or something. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551457: typo in db4.7_load.1: keyword instead of keywork
Package: db4.7-util Version: 4.7.25-8 Severity: minor File: /usr/share/man/man1/db4.7_load.1.gz --- db4.7_load.12009-10-18 12:28:52.0 +0200 +++ db4.7_load.1.fix2009-10-18 12:28:28.0 +0200 @@ -72,7 +72,7 @@ \fBkeys\fR is specified as set, the input must be paired lines of text, where the first line of the pair is the key item, and the second line of the pair is its corresponding data item. If the database to be created -is of type Queue or Recno and the keywork \fBkeys\fR is not set, the +is of type Queue or Recno and the keyword \fBkeys\fR is not set, the input must be lines of text, where each line is a new data item for the database. .sp -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547210: DEB_BUILD_OPTIONS are recomended in policy, section 4.9.1
That section also has an example. I think the patch that I provided is more clear and more common. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546325: if ((rc=ioctl(i8k_fd, I8K_BIOS_VERSION, args)) 0) {
On Sat, Sep 12, 2009 at 04:15:48PM +0100, Bradley Smith wrote:
Gah sorry, I misread the bug report..
1) The problem seem to appear because
ioctl(i8k_fd, I8K_BIOS_VERSION, args))
return value is less then 0.
$ grep -A2 I8K_BIOS_VERSION i8kutils-1.32/i8kctl.c
if ((rc=ioctl(i8k_fd, I8K_BIOS_VERSION, args)) 0) {
return NULL;
}
What makes an ioctl call return less then 0?
Perhaps i8kutils-1.32/i8kctl.c should be patched to print errno to
stderr?
2) Is it related to the fact that the author states there are bugs:
$ grep -A1 I8K_BIOS_VERSION i8kutils-1.32/i8k.h
#define I8K_BIOS_VERSION_IOR ('i', 0x80, int) /* broken:
meant 4 bytes */
#define I8K_MACHINE_ID _IOR ('i', 0x81, int) /* broken:
meant 16 bytes */
?
Is fixing this problem is a matter of just fixing
i8kutils-1.32/i8k.h, or should the kernel module be fixed?
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546325: Printing errno after ioctl failure
Running i8kctl with the following patch yeilds:
$ i8kctl
ioctl failed: Invalid argument
ioctl failed: Invalid argument
ioctl failed: Invalid argument
1.0 (null) 6WNHA 44 2 2 -1 -1 0 0
The patch is:
--- i8kutils-1.32/i8kctl.c 2009-08-22 14:27:09.0 +0300
+++ i8kutils-1.32/i8kctl.c.mod2009-09-17 16:44:09.0 +0100
@@ -37,6 +37,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_BIOS_VERSION, args)) 0) {
+ perror(ioctl failed);
return NULL;
}
@@ -55,6 +56,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_MACHINE_ID, args)) 0) {
+ perror(ioctl failed);
return NULL;
}
@@ -70,6 +72,7 @@
args[0] = fan;
args[1] = speed;
if ((rc=ioctl(i8k_fd, I8K_SET_FAN, args)) 0) {
+ perror(ioctl failed);
return rc;
}
@@ -84,6 +87,7 @@
args[0] = fan;
if ((rc=ioctl(i8k_fd, I8K_GET_FAN, args)) 0) {
+ perror(ioctl failed);
return rc;
}
@@ -98,6 +102,7 @@
args[0] = fan;
if ((rc=ioctl(i8k_fd, I8K_GET_SPEED, args)) 0) {
+ perror(ioctl failed);
return rc;
}
@@ -111,6 +116,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_GET_TEMP, args)) 0) {
+ perror(ioctl failed);
return rc;
}
@@ -124,6 +130,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_POWER_STATUS, args)) 0) {
+ perror(ioctl failed);
return rc;
}
@@ -137,6 +144,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_FN_STATUS, args)) 0) {
+ perror(ioctl failed);
return rc;
}
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546325: A tiny improvment to the previous patch
Not just printing the same message 3 times. Tagging it (Error
or Warning) and specify the faulty ioctl.
$ i8kctl
Warning: ioctl I8K_BIOS_VERSION failed: Invalid argument
Warning: ioctl I8K_GET_SPEED failed: Invalid argument
Warning: ioctl I8K_GET_SPEED failed: Invalid argument
1.0 (null) 6WNHA 44 2 2 -1 -1 0 0
$
--- i8kctl.c.orig 2009-08-22 14:27:09.0 +0100
+++ i8kctl.c 2009-09-17 21:05:10.0 +0100
@@ -37,6 +37,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_BIOS_VERSION, args)) 0) {
+ perror(Warning: ioctl I8K_BIOS_VERSION failed);
return NULL;
}
@@ -55,6 +56,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_MACHINE_ID, args)) 0) {
+ perror(Warning: ioctl I8K_MACHINE_ID failed);
return NULL;
}
@@ -70,6 +72,7 @@
args[0] = fan;
args[1] = speed;
if ((rc=ioctl(i8k_fd, I8K_SET_FAN, args)) 0) {
+ perror(Error: ioctl I8K_SET_FAN failed);
return rc;
}
@@ -84,6 +87,7 @@
args[0] = fan;
if ((rc=ioctl(i8k_fd, I8K_GET_FAN, args)) 0) {
+ perror(Warning: ioctl I8K_GET_FAN failed);
return rc;
}
@@ -98,6 +102,7 @@
args[0] = fan;
if ((rc=ioctl(i8k_fd, I8K_GET_SPEED, args)) 0) {
+ perror(Warning: ioctl I8K_GET_SPEED failed);
return rc;
}
@@ -111,6 +116,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_GET_TEMP, args)) 0) {
+ perror(Warning: ioctl I8K_GET_TEMP failed);
return rc;
}
@@ -124,6 +130,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_POWER_STATUS, args)) 0) {
+ perror(Warning: ioctl I8K_POWER_STATUS failed);
return rc;
}
@@ -137,6 +144,7 @@
int rc;
if ((rc=ioctl(i8k_fd, I8K_FN_STATUS, args)) 0) {
+ perror(Warning: ioctl I8K_FN_STATUS failed);
return rc;
}
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547210: debian/rules: DEB_BUILD_OPTIONS
Package: i8kutils Version: 1.32 Severity: minor Tags: patch I think the following is the more common structure in debian/rules for debug,noopt,nostrip alternatives: --- debian/rules2009-09-17 20:36:51.0 +0100 +++ debian/rules2009-09-17 20:40:15.0 +0100 @@ -1,12 +1,11 @@ #!/usr/bin/make -f -CFLAGS = -Wall -g +CFLAGS := -Wall -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 -else - CFLAGS += -O2 -endif +DEB_BUILD_OPTIONS := +CFLAGS+=$(if $(findstring debug,$(DEB_BUILD_OPTIONS)),-g) +CFLAGS+=$(if $(findstring noopt,$(DEB_BUILD_OPTIONS)),-O0,-O2) +CONFIGUREFLAGS+=$(if $(findstring nostrip,$(DEB_BUILD_OPTIONS)),,--enable-strip) build: build-stamp build-stamp: -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546316: README.i8kutils: www.debian.org/~dz/i8kutils - packages.debian.org/i8kutils
Package: i8kutils Version: 1.32 Severity: Normal Tags: Patch In view of the current content of www.debian.org/~dz/i8kutils, I suggests the following patch: --- README.i8kutils 2009-09-12 16:57:22.0 +0100 +++ README.i8kutils.mod 2009-09-12 17:11:41.0 +0100 @@ -43,7 +43,7 @@ The latest version of the i8kutils package, including the latest i8k kernel driver, can be downloaded from: -http://www.debian.org/~dz/i8k/ +http://packages.debian.org/i8kutils The driver works only with kernels 2.4 onwards (i.e. 2.4, 2.5 and 2.6 are confirmed to work). There will not be a porting to older kernels. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546325: proc/i8k has the the version. The utility doesn't report it.
Package: i8kutils Version: 1.32 Severity: Normal The proc file does know the version, namely A14: $ cat /proc/i8k 1.0 A14 6WNHA 45 2 2 -22 -22 -1 0 Why the utility doesn't report it? It states (null): $ i8kctl 1.0 (null) 6WNHA 45 2 2 -1 -1 0 0 Is the last '0' in that report the culprit, or another bug? -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#492832: Same problem with 0.4.11.11-1+b2
Just reporting that I have the same problem with 0.4.11.11-1+b2. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#317358: postinst: debconf might be confused by output to stdout.
Qouting debconf-devel.7
Avoid outputting anything to stdout in your postinst, since
that can confuse debconf, and postinst should not be verbose
anyway. Output to stderr is ok, if you must.
--- portmap.postinst2009-08-10 01:18:51.0 +0100
+++ portmap.postinst2009-08-21 13:46:23.0 +0100
@@ -9,7 +9,7 @@
if [ $1 = configure ] [ -n $2 ]
dpkg --compare-versions $2 lt 5-3; then
err=$( update-rc.d -f portmap remove 21 /dev/null ) || {
- echo $err 2
+ echo $err 2
exit 1
}
fi
@@ -78,13 +78,15 @@
else
- echo Portmap options have already been configured in
$CONFFILE
- echo This script will not modify it, please edit this file
manually.
+ echo Portmap options have already been configured in\
+ $CONFFILE. This script will not modify it, please \
+ edit this file manually. 2
fi
fi
if [ ! -e $CONFFILE ] [ $1 = reconfigure ] ; then
- echo Cannot reconfigure portmap since $CONFFILE has been
manually re
moved by the admin
+ echo Cannot reconfigure portmap since $CONFFILE has \
+ been manually removed by the admin. 2
fi
db_stop
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#317358: 6.0-10 - 6.0-11: had the same problem.
I was upgrading from 6.0-10 to 6.0-11, and had exactly the same situation that was decribed by the original submitter of the bug. It could be that I had it on earlier upgrades, but only noticed at this upgrade. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542884: debconf-devel.7: An example for using debconf(1)
Package: debconf-doc
Version: 1.5.27
Severity: wishlist
It took me a while to get the suggestion to debug with debconf(1)
right. Hopefully, the following will help others:
--- debconf-devel.7 2009-08-22 01:53:08.0 +0100
+++ debconf-devel.7.new 2009-08-22 03:12:22.0 +0100
@@ -620,12 +620,141 @@
user, pointing at a personal config.dat and template.dat for the
user, you
can load up templates and run config scripts all you like, without
any root
access. If you want to start over with a clean database, just blow
away the
-*.dat files.
+*.dat files. You might also want to rename config.dat-old to
config.dat.
.P
For details about setting this up, see
.BR debconf.conf (5) ,
and note that /etc/debconf.conf makes a good template for a personal
-~/.debconfrc file.
+~/.debconfrc file. An example while trying to debug the portmap
+configuration is as follows:
+.P
+.in +4n
+.nf
+# Creates the debconfrc
+$ sed -ne '/Config: configdb/,/templates.dat/p' \\
+.fi
+.in
+.in +8n
+.nf
+/etc/debconf.conf /home/user/.debconfrc
+.fi
+.in
+.in +4n
+.nf
+$ sed -ne '/Config: configdb/,/templates.dat/p' \\
+.fi
+.in
+.in +8n
+.nf
+/etc/debconf.conf /home/user/.debconfrc
+.fi
+.in
+.in +4n
+.nf
+$ sed -ie 's:/var/cache/debconf/:/home/user/portmap/:' \\
+.fi
+.in
+.in +8n
+.nf
+/home/user/.debconfrc
+.fi
+.in
+.P
+.in +4n
+.nf
+# Creating a dedicated directory is not necessary.
+$ mkdir portmap
+$ cd portmap
+.fi
+.in
+.P
+.in +4n
+.nf
+# Copying the default file serves to emphasize path
+# issues.
+$ cp /etc/default/portmap default
+.fi
+.in
+.P
+.in +4n
+.nf
+$ cp {/var/lib/dpkg/info/portmap.,}postinst
+.fi
+.in
+.P
+.in +4n
+.nf
+# It is important to set the paths in a way that
+# debconf sees the files.
+$ sed -i '/^CONFFILE=/s:.*:CONFFILE=/home/user/portmap/default:' \\
+.fi
+.in
+.in +8n
+.nf
+postinst
+.fi
+.in
+.P
+.in +4n
+.nf
+$ cp {/var/lib/dpkg/info/portmap.,}templates
+.fi
+.in
+.P
+.in +4n
+.nf
+$ debconf-loadtemplate portmap templates
+# Note that some *.dat get created, but not config.dat-old.
+.fi
+.in
+.P
+.in +4n
+.nf
+$ cp {/var/lib/dpkg/info/portmap.,}config
+.fi
+.in
+.P
+.in +4n
+.nf
+# It is important to set the paths in a way that debconf
+# see the files.
+$ sed -i '/^CONFFILE=/s:.*:CONFFILE=/home/user/portmap/default:' \\
+.fi
+.in
+.in +8n
+.nf
+config
+.fi
+.in
+.P
+.in +4n
+.nf
+$ debconf -freadline -pmedium /home/user/portmap/config \\
+.fi
+.in
+.in +8n
+.nf
+configure 6.0-10
+.fi
+.in
+.P
+.in +12n
+.nf
+ . . . User get prompted
+.fi
+.in
+.P
+.in +4n
+.nf
+$ debconf -freadline -pmedium /home/user/portmap/postinst \\
+.fi
+.in
+.in +8n
+.nf
+configure 6.0-10
+.fi
+.in
+.P
.RE
.SH ADVANCED PROGRAMMING WITH DEBCONF
.SS Config file handling
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523615: An `i' (9th letter in ABC) character instead of a `1' character
It took me a while to see what this is all about. I hope I am not the only one that have that difficulty. For the benefit of others, the problem is that there should be an `i' character instead of a `1' character. The affix for the package name is `i8k', not `18k'. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542637: I find it highly inappropriate to state that the maintainer doesn't maintain the package.
Package: i8kutils Version: 1.31 Severity: normal Tags: patch Files: /usr/share/doc/i8kutils/README.i8kutils I understand that the following statement was written by the prevoius maintainer. I find highly inappropriate to keep it as it is: --- README.i8kutils.orig2009-08-20 17:54:38.0 +0100 +++ README.i8kutils 2009-08-20 17:55:39.0 +0100 @@ -2,13 +2,6 @@ = -IMPORTANT! -== - -This software is no longer maintained by me. I don't use it anymore and I'm -not interested in maintaing it. Please DON'T SEND BUG REPORT OR PATCHES. - - -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542637: Actually, the report is not accurate
I read the file more carefully. The header is for 1.28. The footer has the email address of the prevoius maintainer. Since he doesn't wish to recieve any messages for the utilities I think that that pragraph must make it clear that the statement only refer to the single person whose email address is in the footer. And that that person used to be the upstream author. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542517: etc/default/i8kmon: Change to one _to_ enable i8kmon
Package: i8kutils Version: 1.31 Severity: minor Tags: patch --- etc/default/i8kmon2009-05-26 17:42:52.0 +0100 +++ etc/default/i8kmon 2009-08-20 03:51:21.0 +0100 @@ -1,4 +1,4 @@ # /etc/default/i8kmon -# Change to one enable i8kmon +# Change to one to enable i8kmon ENABLED=0 -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531220: nut.postinst: my 3 lines for re processing nut.conf MODE so that it can be sourced
2.4.1-3 has: # re process nut.conf MODE so that it can be sourced NUT_MODE=`sed -ne 's#^ *MODE = *\(.*\)$#\1#p' /etc/nut/nut.conf` sed s/^MODE\(.*\)/MODE=$NUT_MODE/ /etc/nut/nut.conf /etc/nut/nut.conf.new mv /etc/nut/nut.conf.new /etc/nut/nut.conf Those lines are buggy. I suggest: # re process nut.conf MODE so that it can be sourced NUT_MODE=`grep MODE /etc/nut/nut.conf | tr -d ` sed s/^.*MODE.*/$NUT_MODE/ /etc/nut/nut.conf \ /etc/nut/nut.conf.new mv /etc/nut/nut.conf.new /etc/nut/nut.conf -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528222: The example has spaces around shell variable settings (VAR = value).
The prevoius patch contains spaces around shell variable settings. This can confuse new users: --- nut.conf.5 2009-08-16 01:29:51.0 +0100 +++ devel/debian/nut/nut-2.4.1/man/nut.conf.5 2009-08-16 01:28:42.0 +0100 @@ -70,19 +70,23 @@ # /etc/nut/nut.conf. See nut.conf(5) -MODE = none +MODE=none -UPSD_OPTIONS = +UPSD_OPTIONS= -UPSMON_OPTIONS = +UPSMON_OPTIONS= -# POWEROFF_WAIT = 15m +# POWEROFF_WAIT=15m .SH INTEGRATION An init script, such as /etc/init.d/nut, is expected to source this file in order to determine which component(s) has to be started. +Note: There should be no spaces around the '=' character in the example +above. The reason for that restriction is that in most cases, such +spaces will confuse shell scripts that source that file. + .SH SEE ALSO \fBups.conf\fR(5), \fBupsd.conf\fR(5), \fBupsd.users\fR(5), \fBupsmon.conf\fR(5) -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541629: nut.preinst: With rm -f, there is no need to test for files existance
--- debian/nut.preinst 2009-07-15 22:29:32.0 +0100 +++ debian/nut.preinst.new 2009-08-16 03:12:48.0 +0100 @@ -2,7 +2,7 @@ if [ $1 = upgrade ]; then # remove the obsolete udev file -[ -f /etc/udev/rules.d/025_nut-usbups.rules ] rm -f /etc/udev/rules.d/025_nut-usbups.rules +rm -f /etc/udev/rules.d/025_nut-usbups.rules # Remove previous rules if unchanged, otherwise move to new filename. if [ -e /etc/udev/rules.d/52_nut-usbups.rules ]; then -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531220: Have you considered tr -d instead of the 2nd sed invocation?
Perhaps you should just grep the whole line, and then use tr, instead of sed, for the actual fix? $ for str in MODE = standalone MODE= standalone MODE =standalone; do printf $str\t\t; printf $str\n | tr -d ; done MODE = standalone MODE=standalone MODE= standalone MODE=standalone MODE =standalone MODE=standalone -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526770: The permissions I set on the serial port were modified
The original submitter wrote: 3) The permissions I set on the serial port, that is connected to the UPS, were modified A possible reason is udev. $ zcat /usr/share/doc/udev/NEWS.Debian.gz | head udev (0.140-1) unstable; urgency=low Starting from this release the last applicable NAME directive will be used instead of the first one: check any custom udev rules. The default rules files have been moved to /lib/udev/rules.d/ and /etc/udev/rules.d/ is supposed to contain only generated files or custom directives. -- Marco d'Itri m...@linux.it Wed, 18 Mar 2009 02:34:13 +0100 -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541629: udev files that are added on preinst are not removed on purge
Package: nut Version: 2.4.1-3 Severity: Normal Tags: patch udev files that are added on preinst are not removed on purge: --- debian/nut.postrm 2009-08-15 03:11:28.0 +0100 +++ debian/nut.postrm.new 2009-08-15 03:14:22.0 +0100 @@ -12,6 +12,12 @@ ;; purge) +[ -f /etc/udev/rules.d/025_nut-usbups.rules ] \ +rm -f /etc/udev/rules.d/025_nut-usbups.rules +[ -f /etc/udev/rules.d/52_nut-usbups.rules ] \ +rm -f /etc/udev/rules.d/52_nut-usbups.rules +[ -f /etc/udev/rules.d/52-nut-usbups.rules ] \ +rm -f /etc/udev/rules.d/52-nut-usbups.rules # remove the nut user if getent passwd nut /dev/null; then deluser --quiet nut -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541629: With rm -f, there is no need to test for files existance
With rm -f, there is no need to test for existance:
--- debian/nut.postrm 2009-08-15 03:14:22.0 +0100
+++ debian/nut.postrm.new 2009-08-15 03:56:36.0 +0100
@@ -5,19 +5,15 @@
remove)
# remove sample file if those were previously (wrongly) installed
for file in ups.conf upsd.conf upsmon.conf upsd.users \
upssched.conf ; do
- if [ -f /etc/nut/${file}.sample ] ; then
-rm -f /etc/nut/${file}.sample
- fi
+ rm -f /etc/nut/${file}.sample
done
;;
purge)
-[ -f /etc/udev/rules.d/025_nut-usbups.rules ] \
-rm -f /etc/udev/rules.d/025_nut-usbups.rules
-[ -f /etc/udev/rules.d/52_nut-usbups.rules ] \
-rm -f /etc/udev/rules.d/52_nut-usbups.rules
-[ -f /etc/udev/rules.d/52-nut-usbups.rules ] \
-rm -f /etc/udev/rules.d/52-nut-usbups.rules
+# remove udev rules files
+rm -f /etc/udev/rules.d/025_nut-usbups.rules
+rm -f /etc/udev/rules.d/52_nut-usbups.rules
+rm -f /etc/udev/rules.d/52-nut-usbups.rules
# remove the nut user
if getent passwd nut /dev/null; then
deluser --quiet nut
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539432: Please better explain the use of `found' in http://www.debian.org/Bugs/server-control
Package: bugs.debian.org Severity: normal the following was in a response from the bts: found 539230 1:9.6.1.dfsg.P1-1 Bug #539230 [bind9] debian/control: s/libdb-dev (4.6)/libdb-dev ( 4.6)/ There is no source info for the package 'bind9' at version '1:9.6.1.dfsg.P1-1' with architecture '' Unable to make a source version for version '1:9.6.1.dfsg.P1-1' Bug Marked as found in versions 1:9.6.1.dfsg.P1-1. I find that unclear: why is there no source (is it the epoch?)? How should I submitted the message correctly? Why does this message mention an architecture, while an architecture is not mentioned in http://www.debian.org/Bugs/server-control? In view of those warnings, what is the meaning of marking the bug in version 1:9.6.1.dfsg.P1-1? I think you should clarify the `found' description in http://www.debian.org/Bugs/server-control. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539165: init.d/bind9: PIDFILE ignores possible setting in the configuration
Package: bind9
Version: 1:9.6.1.dfsg-2
Severity: normal
Tags: patch
Files: /etc/init.d/bind9
The init script uses a hard coded PIDFILE. It overrides possible
setting of pid-file by the local administrator. This patch
somewhat remedy this problem:
--- debian/bind9.init 2009-07-29 17:18:50.0 +0300
+++ debian/bind9.init.new 2009-07-29 17:20:45.0 +0300
@@ -25,7 +25,8 @@
test -x /usr/sbin/rndc || exit 0
. /lib/lsb/init-functions
-PIDFILE=/var/run/named/named.pid
+PIDFILE=`grep -sr pid-file /etc/bind | sed -n 's/.* \(.*\);/\1/p'`
+[ ! -f ${PIDFILE} -o ! -r ${PIDFILE} ] PIDFILE=/var/run/bind/named.pid
check_network() {
if [ -x /usr/bin/uname ] [ X$(/usr/bin/uname -o) = XSolaris ]; then
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539230: satisfydepends-aptitude: warning, `' is obsolete, use `=' or `' instead`' is obsolete, use `=' or `' instead
Package: pbuilder Version: 0.189 Severity: normal The warning below is indented by me. ... Setting up cdebootstrap (0.5.4) ...^M Setting up pbuilder (0.188) ...^M I: Setting DEBBUILDOPTS= - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: i386 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder and should Depends: libkrb5-dev, debhelper (= 5), libssl-dev, libtool, bison, libdb-dev (4.6), libldap2-dev, libxml2-dev, libcap2-dev, hardening-wrapper, libgeoip-dev (= 1.4.6) Conflicts: libdb4.2-dev warning, in file '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy/DEBIAN/control' near line 7 package 'pbuilder-satisfydepends-dummy': `Depends' field, reference to `libdb-dev': `' is obsolete, use `=' or `' instead dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Reading package lists... ... If that matter, the command line - in the pkg directory - was pdebuild --use-pdebuild-internal --buildresult .. -- --basetgz \ /var/cache/pbuilder/squeeze.base.tgz The basetgz is squeeze. It could be that some packages in it are at most 2 weeks old. I haven't updated it before building the package. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539165: Am I confused about the reasons to close #212659?
On one hand: $ zgrep 212659 /usr/share/doc/bind9/changelog.Debian.gz * upstream now uses a bind subdir. Closes: #212659 and on the other: $ grep -A3 2486 CHANGES 2486. [func] The default locations for named.pid and lwresd.pid are now /var/run/named/named.pid and /var/run/lwresd/lwresd.pid respectively. Isn't that a contradiction? -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526770: A suggestion to add some code to upsd.c:check_command
1. It could be that the logging problem that was reported by shaul Karl was beacuse of tcpd. 2. upsd.c:check_command: 2.1 I suggest to add a upsdebugx call when hosts_access returns 0. 2.2 upsd.c:server_load add 127.0.0.1 when no LISTEN addres has been specified. In that case, upsd.c:check_command should allow 127.0.0.1 in the same circumstances. It is reasonble to expect that when no LISTEN address has been specified, no modifications will be done for tcpd to allow upsd. That may address the report of alex bodnaru in the bug report. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526770: Suggested patch for what is described in the prevoius message
The following implements my suggestions from the prevoius message:
--- server/upsd.c 2009-07-26 19:19:22.0 +0300
+++ server/upsd.c.new 2009-07-27 01:16:34.0 +0300
@@ -69,6 +69,7 @@
/* default is to listen on all local interfaces */
static stype_t *firstaddr = NULL;
+ /* At this point, if no LISTEN address has been seen */
+static int firstaddrFromConf = 0;
#ifdef HAVE_IPV6
static int opt_af = AF_UNSPEC;
@@ -472,8 +474,13 @@
if (!hosts_access(req)) {
/* tcp-wrappers says access should be denied */
- send_err(client, NUT_ERR_ACCESS_DENIED);
- return;
+ upslogx(LOG_WARNING, tcpd denied %s,
client-addr);
+ if (!firstaddrFromConf)
+ upslogx(LOG_WARNING, override tcpd. %s
was set by %s, client-addr, progname);
+ else {
+ send_err(client,
NUT_ERR_ACCESS_DENIED);
+ return;
+ }
}
#endif /* HAVE_WRAP */
}
@@ -621,7 +628,10 @@
#else
listen_add(127.0.0.1, string_const(PORT));
#endif
+ upslogx(LOG_NOTICE, no LISTEN addres has been
specified. localhost was set by %s, progname);
}
+ else
+ firstaddrFromConf = 1;
for (server = firstaddr; server; server = server-next) {
setuptcp(server);
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538785: /etc/init.d/nut status does not work
Package: nut
Version: 2.4.1-3
Severity: normal
Tags: patch
With
$ ps axf | grep /sbin/ups
9442 pts/4S+ 0:00 \_ grep /sbin/ups
16096 ?Ss 0:01 /sbin/upsd
16099 ?Ss 0:00 /sbin/upsmon
16100 ?S 0:01 \_ /sbin/upsmon
I get
# /etc/init.d/nut status
Checking status of Network UPS Tools
upsd is not running failed!
upsmon is not running failed!
--- debian/nut.init 2009-07-15 22:29:32.0 +0300
+++ debian/nut.init.new 2009-07-27 02:37:46.0 +0300
@@ -65,11 +65,11 @@
check_status() {
case $MODE in
standalone|netserver)
- status_of_proc $DESC upsd
- status_of_proc $DESC upsmon
+ status_of_proc -p $upsd_pid $upsd upsd
+ status_of_proc -p $upsmon_pid $upsmon upsmon
;;
netclient)
- status_of_proc $DESC upsmon
+ status_of_proc -p $upsmon_pid $upsmon upsmon
;;
none|*)
;;
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537795: Addition of sources.redhat.com/gdb/onlinedocs/ in README.Debian
Package: gdb Version: 6.8-3 Severity: wishlist I think that http://sources.redhat.com/gdb/onlinedocs/gdb.html#SEC_Top is great to get someone quickly into gdb. I wish it would be specifically mentioned in /usr/share/doc/gdb/README.Debian . -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537583: mv /etc/sensors3.conf /etc/sensors3/main
Package: libsensors4 Version: 1:3.1.1-2 Severity: wishlist There is already a sensors.d directory under /etc/. Having the main configuration in it seems to me a less clattered /etc. And while at it, /etc/sensors.d might be renamed /etc/sensors. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520587: Some minor modifications to the patch
I have modified a bit the patch that the original submitter proposed:
--- lsof.8.orig 2009-07-20 04:58:52.0 +0300
+++ lsof.8.new 2009-07-20 05:16:02.0 +0300
@@ -127,31 +127,31 @@
by user ``foo''.
The exceptions are:
.IP
-.TP \w'1) 'u
+.TP \w'1)\ 'u
1)
the `^' (negated) login name or user ID (UID), specified with the
-.B \-u
+.B \-u
option;
-.TP \w'1) 'u
+.TP \w'1)\ 'u
2)
the `^' (negated) process ID (PID), specified with the
-.B \-p
+.B \-p
option;
-.TP \w'1) 'u
+.TP \w'1)\ 'u
3)
the `^' (negated) process group ID (PGID), specified with the
-.B \-g
+.B \-g
option;
-.TP \w'1) 'u
+.TP \w'1)\ 'u
4)
the `^' (negated) command, specified with the
-.B \-c
+.B \-c
option;
-.TP \w'1) 'u
+.TP \w'1)\ 'u
5)
the ('^') negated TCP or UDP protocol state names, specified with the
-.BI \-s [p:s]
-option.
+.B \-s
+ [p:s] option.
.PP
Since they represent exclusions, they are applied without ORing or
ANDing
and take effect before any other selection criteria are applied.
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537201: dpkg --print-installation-architecture vs dpkg --print-architecture revisited
Package: console-data
Version: 1.09-1
Severity: normal
Tags: patch
debian/attic/console-data.config uses
dpkg --print-installation-architecture
, which is obsolete and prints a warning to the user.
$ dpkg --print-installation-architecture
dpkg: warning: obsolete option '--print-installation-architecture',
please use '--print-architecture' instead.
i386
It used to have `dpkg --print-architecture', but was changed to the
current usage in #54798. Qouting the relevat part of #54798:
If you read the dpkg --help you'll see that :
dpkg --print-architectureprint target architecture (uses
GCC)
You should be using dpkg --print-installation-architecture ... this
is
a common mistake and it should be in a debian developers FAQ if
there was one.
Without gcc, dpkg --print-architecture is failing and caused your
package
postinst to abort (note the empty arch string outputted by
console-data debug line)...
dpkg --help doesn't mention anymore the requirment for gcc for
--print-architecture. There for, I suggested either:
--- console-data.config 2009-07-16 03:59:07.0 +0300
+++ console-data.config.mod 2009-07-16 03:59:21.0 +0300
@@ -359,7 +359,7 @@
sub guess_arch {
my ($defs) = @_;
-my $arch = `dpkg --print-installation-architecture`;
+my $arch = `dpkg --print-architecture`;
chomp $arch;
# Overrides for testing:
Or:
--- console-data.config 2009-07-16 03:59:07.0 +0300
+++ console-data.config.mod 2009-07-16 04:00:30.0 +0300
@@ -359,7 +359,7 @@
sub guess_arch {
my ($defs) = @_;
-my $arch = `dpkg --print-installation-architecture`;
+my $arch = `dpkg --print-architecture 2/dev/null`;
chomp $arch;
# Overrides for testing:
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536599: debian/rules: s:dh_clean -k:dh_prep:
Package: nut Version: 2.4.1-2 Severity: normal According to dh_clean(1), -k is deprecated, use dh_prep(1) instead. There are 2 instances of dh_clean -k. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534404: One of the assorted links at the bottom of www.d.o/devel points to 404
Package: www.debian.org Severity: normal One of the assorted links at the bottom of www.debian.org/devel is `Debian OID hierarchy'. That link is broken. It pints to a 404 Not Found. -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533857: vfork.2: exit(2) -- _exit(2)
Package: manpages-dev Version: 3.21-1 Severity: normal Tags: patch File: /usr/share/man/man2/vfork.2.gz --- vfork.2.orig2009-06-21 03:53:54.0 +0300 +++ vfork.2 2009-06-21 03:54:52.0 +0300 @@ -83,7 +83,7 @@ in that the parent is suspended until the child terminates (either normally, by calling -.BR exit (2), +.BR _exit (2), or abnormally, after delivery of a fatal signal), or it makes a call to .BR execve (2). Rational: 1. There is no exit(2), is there? 2. Other places in that manpage reffers to _exit(2). -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532072: Are changelogs of packages not getting updated?
Package: ftp.debian.org Severity: normal It looks to me that chagelogs of packages not getting updated when new versions are accepted. Are you aware of that? Is that intended? For example, reportbug 4.4 is in testing, while /changelogs/pool/main/r/reportbug/current points to 4.2 -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532045: strcpy.3: SEE ALSO mention strpcpy. Where is strpcpy?
Package: manpages-dev Version: 3.21-1 Severity: normal File: /usr/share/man/man3/strcpy.3.gz strcpy mentions strpcpy. Does strpcy has a manpages? -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528628: While at environ.7, please mention that environ[last_element]==NULL
--- environ.7 2009-05-16 16:21:37.0 +0300 +++ environ.7.mod 2009-05-16 16:30:18.0 +0300 @@ -52,6 +52,10 @@ This array of strings is made available to the process by the .BR exec (3) call that started the process. +The last element of the array is a NULL pointer. +There fore, the expression +\fIenviron[last_element]\fP\fB == \fP\fINULL\fP +is true. By convention these strings have the form \fIname\fP\fB=\fP\fIvalue\fP. Common examples are: -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528628: environ.7: What is meant by `Many a system'?
Package: manpages Version: 3.21-1 Severity: normal Quoting environ.7 BUGS, 1st paragraph: Clearly there is a security risk here. Many a system command has Isn't `Many a system' bad English? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528641: Files that are not used by the application are marked as connfiles
Package: nut
Version: 2.4.1-2
Severity: normal
Tags: patch
The *.sample files that are written to /etc/nut by the deb are marked
as conffiles even though the application does not read them.
I suggest to:
1. Remove the .sample suffix
2. Have the distributed files also in /usr/share/doc/nut/examples.
Having them in the examples dir allows the user to get a short
version in the CONF dir, while preserving the useful skeltons,
with the comments, in a known, namely examples, directory.
--- debian/nut-cgi.examples 1970-01-01 02:00:00.0 +0200
+++ debian/nut-cgi.examples 2009-05-14 04:11:53.0 +0300
@@ -0,0 +1,4 @@
+./debian/tmp/etc/nut/hosts.conf
+./debian/tmp/etc/nut/upsset.conf
+./debian/tmp/etc/nut/upsstats-single.html
+./debian/tmp/etc/nut/upsstats.html
--- debian/nut-cgi.install 2009-05-14 13:43:52.0 +0300
+++ debian/nut-cgi.install 2009-05-14 03:41:23.0 +0300
@@ -1,6 +1,6 @@
-debian/tmp/etc/nut/hosts.conf.sample
-debian/tmp/etc/nut/upsset.conf.sample
-debian/tmp/etc/nut/upsstats.html.sample
-debian/tmp/etc/nut/upsstats-single.html.sample
+debian/tmp/etc/nut/hosts.conf
+debian/tmp/etc/nut/upsset.conf
+debian/tmp/etc/nut/upsstats.html
+debian/tmp/etc/nut/upsstats-single.html
debian/tmp/usr/lib/cgi-bin/
debian/tmp/usr/share/nut/www
--- debian/nut.examples 1970-01-01 02:00:00.0 +0200
+++ debian/nut.examples 2009-05-14 04:12:10.0 +0300
@@ -0,0 +1,6 @@
+./debian/tmp/etc/nut/nut.conf
+./debian/tmp/etc/nut/ups.conf
+./debian/tmp/etc/nut/upsd.conf
+./debian/tmp/etc/nut/upsd.users
+./debian/tmp/etc/nut/upsmon.conf
+./debian/tmp/etc/nut/upssched.conf
--- debian/nut.install 2009-05-14 13:43:52.0 +0300
+++ debian/nut.install 2009-05-14 03:40:59.0 +0300
@@ -7,11 +7,11 @@
debian/tmp/usr/share/nut/driver.list
debian/tmp/*/udev/
debian/tmp/etc/nut/nut.conf
-debian/tmp/etc/nut/ups.conf.sample
-debian/tmp/etc/nut/upsd.conf.sample
-debian/tmp/etc/nut/upsd.users.sample
-debian/tmp/etc/nut/upsmon.conf.sample
-debian/tmp/etc/nut/upssched.conf.sample
+debian/tmp/etc/nut/ups.conf
+debian/tmp/etc/nut/upsd.conf
+debian/tmp/etc/nut/upsd.users
+debian/tmp/etc/nut/upsmon.conf
+debian/tmp/etc/nut/upssched.conf
debian/tmp/etc/bash_completion.d/nut
debian/tmp/lib/nut/genericups
debian/tmp/lib/nut/mge-shut
--- debian/rules2009-05-14 13:43:52.0 +0300
+++ debian/rules2009-05-14 03:55:31.0 +0300
@@ -93,14 +93,19 @@
# install the bash completion script
mkdir -p $(CURDIR)/debian/tmp/etc/bash_completion.d
- cp $(CURDIR)/scripts/misc/nut.bash_completion
$(CURDIR)/debian/tmp/et
c/bash_completion.d/nut
-
- # install the default configuration
- mv $(CURDIR)/debian/tmp/etc/nut/nut.conf.sample
$(CURDIR)/debian/tmp
/etc/nut/nut.conf
+ cp $(CURDIR)/scripts/misc/nut.bash_completion \
+ $(CURDIR)/debian/tmp/etc/bash_completion.d/nut
+ # install the default configuration
+ for f in $(CURDIR)/debian/tmp/etc/nut/*; do \
+ nf=`basename $${f} | sed 's/\(.*\).sample/\1/'`; \
+ mv $${f} $(CURDIR)/debian/tmp/etc/nut/$${nf}; \
+ done
+
dh_installchangelogs ChangeLog
dh_installinit -- start 50 2 3 4 5 . stop 50 0 1 6 .
dh_install
+ dh_installexamples
dh_installman
dh_installdocs -XMakefile
dh_link
--
sobtw...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528222: Without automake-1.10, here is the patch for man/Makefile.in
--- Makefile.in 2009-02-17 11:24:10.0 +0200 +++ Makefile.in.new 2009-05-12 10:42:52.0 +0300 @@ -236,8 +236,8 @@ upscli_splitname.3 upscli_strerror.3 upscli_fd.3 upscli_get.3 \ upscli_list_next.3 upscli_list_start.3 upscli_ssl.3 \ upscli_upserror.3 $(am__append_1) -CONF_PAGES = ups.conf.5 upssched.conf.5 upsd.conf.5 upsmon.conf.5 \ - upsd.users.5 +CONF_PAGES = nut.conf.5 ups.conf.5 upssched.conf.5 upsd.conf.5 \ + upsmon.conf.5 upsd.users.5 CLIENT_PAGES = upsc.8 upsrw.8 upscmd.8 upslog.8 upssched.8 \ upsmon.8 upsd.8 nutupsdrv.8 upsdrvctl.8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
