Bug#342066: make-kpkg doesn't work with make 3.80-9
package: kernel-package version: 10.012 I had make 3.80-9 installed. And kept getting this error: == [EMAIL PROTECTED]:~/kernel/xen/linux-2.6.10-xenU$ time fakeroot make-kpkg kernel-image exec make -f /usr/share/kernel-package/ruleset/minimal.mk debian /usr/share/kernel-package/ruleset/misc/version_vars.mk:53: *** missing `endif'. Stop. == The make changelog mentions bug 296482 being closed, which pertains to $(eval) not working inside an if block. Please add a versioned depends on make (>= 3.80-10). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#338204: 12.3: define small for compression of documentation
package: debian-policy version: 3.6.2.1 Section 12.3 says extra documentation should be compressed if it is small. However, small is not defined. It would be useful if it was; otherwise, there is no real incentive to compress documentation, as one person's "too large" is another person's small. Also, the text says compressed with "gzip -9, unless it is small." Does that mean I can compress with gzip -1 if it's small, or bzip, or zip? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345091: ITP: checkgmail -- Alternative Gmail Notifier for Linux via Atom feeds
On Wed, 28 Dec 2005, Sandro Tosi wrote: > Package: wnpp > Severity: wishlist > Owner: Sandro Tosi <[EMAIL PROTECTED]> > > * Package name: checkgmail > Version : 1.4 > Upstream Author : Owen Marshall <[EMAIL PROTECTED]> > * URL : http://checkgmail.sourceforge.net/ > * License : GPL > Description : Alternative Gmail Notifier for Linux via Atom feeds I looked at the homepage, and while this does appear useful, is it really nescessary to be packaged all by itself? Think about a collection package; I don't think debian should be overloaded with tons of single-program packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324583: #324583: status of broken apply/unapply scripts
This bug was tagged pending on Aug 24, and was s upposed to be fixed in -6. However, we are at -10, and it is still broken. I need this fixed so that I can upload new xen packages, as they require pristine source to generate a patch against. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324583: #324583: status of broken apply/unapply scripts
On Thu, 27 Oct 2005, Sven Luther wrote: > On Thu, Oct 27, 2005 at 03:40:06PM -0500, Adam Heath wrote: > > This bug was tagged pending on Aug 24, and was s upposed to be fixed in -6. > > However, we are at -10, and it is still broken. > > > > I need this fixed so that I can upload new xen packages, as they require > > pristine source to generate a patch against. > > We are moving to 2.6.14 as soon as it is out anyway, and there will be no > 2.6.12 upload anymore hopefully. > > Can you check if this problem is still present in 2.6.14-rc5-1 currently > present in experimental ? So? It was supposed to be fixed in -6, but wasn't. Something is wrong with the communication of the team. Why can't a simple upload be done with the fix? And no, I can't check .14. Xen doesn't work with that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324583: #324583: status of broken apply/unapply scripts
On Fri, 28 Oct 2005, Sven Luther wrote: > Well, who told you it was supposed to be fixed, can you point to the svn > commit fixing it ? Did you even read the bug that is mail is a part of? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336133: libvideo-capture-v4l-perl is non-free
package: libvideo-capture-v4l-perl version: 0.224-5 severity: serious This package is non-free. The README file says this: -- License+Disclaimer == This code is distributed under GPLv2 (in other words, do what you like with it, but don't sell it, and give credit if you use it). THIS SOFTWARE IS IN NO WAY GUARANTEED TO WORK. IF YOU USE IT AND IT DOESN'T WORK, OR MESSES UP YOUR COMPUTER, IT'S YOUR OWN PROBLEM. -- The "but don't sell it" part fails DFSG#1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336906: debhelper(7) doesn't document COMPAT level for # comments
package: debhelper version: 4.9.15 severity: minor The debhelper(7) manpage documents that various files used by the scripts can take #-style comments. However, that is only true if debian/compat is 5. Please fix the documentation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336908: dh_install in compat(5) warns about missing files without showing the package
package: debhelper version: 4.9.15 severity: minor dh_install -N xen-docs --sourcedir=/home.local/adam/code/xen/xen-2.9.9+3.0-20051027/debian/install dh_install: missing files (usr/lib/libxencontrol.so.*), aborting It'd be nice if it told me which package had the error. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314711: jython NEWS is really changelog
Package: jython Version: 2.1.0-20 Severity: important The upstream NEWS file is really the upstream changelog. Please install it as such. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#159642: dpkg-dev: [DPKG-SOURCE] still complains about Enhances fields... 2 years later
On Mon, 23 May 2005, Martin-Eric Racine wrote: > Package: dpkg-dev > Version: 1.10.27 > Followup-For: Bug #159642 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Btw, the "Enhances" field indeed is a part of the Policy Manual (version > 3.6.1.1 Sarge) at sections 5.6.9 and 7.2, so > it definitely has moved beyond the wishlist severity. I just thought I'd > refresh everyone's memory on this bug item. Bother. Let's not get into that again. Policy is wrong for mentioning it prominately before code has had a chance to implement it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309045: SECURITY: unrar opens /tmp/debug_unrar.txt
package: unrar
tags: security
severity: serious
version: 1:0.0.1-1
[EMAIL PROTECTED]:/bt/incoming/Star.Trek.Enterprise.S04E21.HDTV.XviD-LOL$
ltrace unrar -t *.nfo 2>&1|grep /tmp
strcpy(0x8050e60, "/tmp/debug_unrar.txt")= 0x8050e60
fopen("/tmp/debug_unrar.txt", "w") = 0x80540b0
fopen("/tmp/debug_unrar.txt", "a") = 0x8054a68
fopen("/tmp/debug_unrar.txt", "a") = 0x8054a68
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291338: apt: md5/sha1 checksum routines should work if length of file is unknown
On Thu, 20 Jan 2005, Anthony Towns wrote:
> Package: apt
> Version: 0.5.4
> Severity: wishlist
> Tags: patch
>
> SHA1Summation::AddFD should work on pipes as well as regular files
> so files don't need to be uncompressed to disk to be summed. This
> impacts python-apt too, since it doesn't offer a cumulative interface
> to SHA1Summation.
>
> Easy fix seems like it'd be:
>
> bool SHA1Summation::AddFD(int Fd,unsigned long Size)
> {
> unsigned char Buf[64 * 64];
> int Res = 0;
> - while (Size != 0)
> + int ToEOF = (Size == 0);
> + while (Size != 0 || ToEOF);
> {
> - Res = read(Fd,Buf,MIN(Size,sizeof(Buf)));
> - if (Res < 0 || (unsigned) Res != MIN(Size,sizeof(Buf)))
> + int n = sizeof(Buf);
> + if (!ToEOF) n = MIN(Size,n);
> + Res = read(Fd,Buf,n);
> + if (Res < 0 || (!ToEOF && (unsigned) Res != n)) // error, or short read
> return false;
> + if (ToEOF && Res == 0) // EOF
> + break;
>Size -= Res;
>Add(Buf,Res);
> }
> return true;
> }
I have no problem with this; it's similiar to how dpkg does it(separate far to
indicate processing until eof is hit(dpkg does it with limit == -1, HTH)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293838: please add file overlap check to lintian
Package: lintian Version: 1.23.3 I had a file overlap(/usr/share/doc/xen/examples/xmexample[12]) between xen and xen-docs, both produced by the same source, and both installable at the same time. This kind of error should be easier to detect. You'd have to take into account conflicts, when seeing if 2 packages were installable at the same time. This feature could also be extended when checking the entire archive; however, that might be too heavy-weight. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293838: #293838: please add file overlap check to lintian
tag - wontfix thanks Well, that's funny. Jeroen van Wolffelaar and I were discussing on how to modify lintian to actually do this check. I've got a script started that works over the entire archive, and wouldn't be hard to make it work over a smaller set. If you give us time, we'll send in a patch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299699: dpkg: FTBFS (amd64/gcc-4.0): array type has incomplete element type
tag 299699 - patch thanks On Tue, 15 Mar 2005, Andreas Jochens wrote: > the latest version of gcc-4.0 is even more restrictive than the previous > ones. There is a new error message 'array type has incomplete element type' > for constructs like 'extern struct st x[];' when 'struct st' has not > been defined. > > When building 'dpkg' on amd64 with gcc-4.0, > I get the following error: > > gcc -g -O2 -Wall -Wwrite-strings -Wpointer-arith -Wimplicit > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wmissing-declarations -Wbad-function-cast -Wcast-qual -Wcast-align -Winline > -Wmissing-noreturn -Wsign-compare -DHAVE_CONFIG_H -D_GNU_SOURCE > -DLOCALEDIR=\"/usr/share/locale\" -I../../intl -I../intl -I../../include > -I../.. -I../../lib -I../include -I.. -I. -I../../optlib -DUSE_ZLIB > -DUSE_BZ2LIB -DCOPYINGFILE=\"/usr/share/doc/dpkg/copyright\" -c > ../../lib/dump.c > In file included from ../../lib/dump.c:37: > ../../include/parsedump.h:33: error: array type has incomplete element type > ../../lib/dump.c: In function 'w_charfield': > ../../lib/dump.c:95: warning: cast discards qualifiers from pointer target > type > ../../lib/dump.c: In function 'w_booleandefno': > ../../lib/dump.c:133: warning: cast discards qualifiers from pointer target > type > make[3]: *** [dump.o] Error 1 > make[3]: Leaving directory `/dpkg-1.10.27/build/lib' > > With the attached patch 'dpkg' can be compiled > on amd64 using gcc-4.0. > > The attached patch includes the patch from BTS bug #282669. This part has > already been applied to 'experimental' (thanks!). > > Regards > Andreas Jochens I don't agree with the patch; move the struct definition. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#252657: dpkg-dev: [arch]-specific Depends broken (see #170575)
On Fri, 18 Mar 2005, Scott James Remnant wrote: > Adam wrote that this is because of a parser error, that is not true, the > parser is fine. dpkg simply doesn't support per-arch dependencies. Correct, dpkg itself doesn't support it. > > > So there are three possibilities: > > > > * dpkg 1.10.11 did not add support for arch-specific entries in > > *Depends* and closing 170575 with dpkg 1.10.11's changelog was an > > error. > > > From what I can tell, this is correct. Support for per-arch BUILD > dependencies was added, not general dependencies. Wrong. You can have per-arch *regular* depends. dpkg-gencontrol just strips out the tokens that don't apply for the current arch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318964: module-assistant does not work with xen
package: module-assistant version: 0.9 When compiling a xen kernel, one passes "ARCH=xen" on the command line. However, m-a does not do this, and has no option to do so. kernel-package has been updated to work with xen, so it'd be nice if m-a had a way to do this as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303105: tla help output not consistent
package: tla version: 1.3-1 severity: minor All commands in tla that take -A | --archive do not show that they take a parameter of type ARCHIVE in their help output. I discovered this when I wrote a perl script to parse the tla help output, to produce a bash completion shell script. I'll be sending a patch shortly, when I get a bug number. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303168: ssh has poor -h|--help option parsing
package: openssh-client version: 1:3.9p1-3 severity: minor tags: experimental ssh doesn't support -h nor --help. However, the usage displayed shows -h as a valid option. Could you please add -h and --help processing, and make certain the exit value is 0, and that it displays on stdout instead? -- gradall:/home.local/adam# ssh -h 1>/dev/null;echo $? ssh: illegal option -- h usage: ssh [-1246AaCfghkMNnqsTtVvXxY] [-b bind_address] [-c cipher_spec] [-D port] [-e escape_char] [-F configfile] [-i identity_file] [-L port:host:hostport] [-l login_name] [-m mac_spec] [-o option] [-p port] [-R port:host:hostport] [-S ctl] [EMAIL PROTECTED] [command] 1 gradall:/home.local/adam# ssh --help 1>/dev/null;echo $? usage: ssh [-1246AaCfghkMNnqsTtVvXxY] [-b bind_address] [-c cipher_spec] [-D port] [-e escape_char] [-F configfile] [-i identity_file] [-L port:host:hostport] [-l login_name] [-m mac_spec] [-o option] [-p port] [-R port:host:hostport] [-S ctl] [EMAIL PROTECTED] [command] 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303452: add -o PidFile option to ssh
Package: openssh-client
Version: 3.9p1-3.1
Tags: experimental patch
When ssh -f is used, ssh forks into the background. However, it's then
difficult to kill that backgrounded ssh automatically, from other scripts.
Thet attached patch tells ssh to write a pid file. This happens irregardless
of whether -f is used, however.
This makes my ssh -MS wrapper more robust(ssh is buggy when -MNS pipe is used,
but not -f, and then you later reconnect to that master; the first slave works
fine, but subsequent slaves deadlock).
diff -u openssh-3.9p1/readconf.c openssh-3.9p1/readconf.c
--- openssh-3.9p1/readconf.c
+++ openssh-3.9p1/readconf.c
@@ -107,7 +107,7 @@
oAddressFamily, oGssAuthentication, oGssDelegateCreds,
oServerAliveInterval, oServerAliveCountMax, oIdentitiesOnly,
oSendEnv, oControlPath, oControlMaster,
- oProtocolKeepAlives, oSetupTimeOut,
+ oProtocolKeepAlives, oSetupTimeOut, oPidFile,
oDeprecated, oUnsupported
} OpCodes;
@@ -200,6 +200,7 @@
{ "controlmaster", oControlMaster },
{ "protocolkeepalives", oProtocolKeepAlives },
{ "setuptimeout", oSetupTimeOut },
+ { "pidfile", oPidFile },
{ NULL, oBadOption }
};
@@ -782,6 +783,10 @@
intptr = &options->setuptimeout;
goto parse_int;
+ case oPidFile:
+ charptr = &options->pidfile;
+ goto parse_string;
+
case oDeprecated:
debug("%s line %d: Deprecated option \"%s\"",
filename, linenum, keyword);
@@ -926,6 +931,7 @@
options->num_send_env = 0;
options->control_path = NULL;
options->control_master = -1;
+ options->pidfile = NULL;
}
/*
diff -u openssh-3.9p1/readconf.h openssh-3.9p1/readconf.h
--- openssh-3.9p1/readconf.h
+++ openssh-3.9p1/readconf.h
@@ -112,6 +112,7 @@
char*control_path;
int control_master;
+ char*pidfile;
} Options;
diff -u openssh-3.9p1/ssh.1 openssh-3.9p1/ssh.1
--- openssh-3.9p1/ssh.1
+++ openssh-3.9p1/ssh.1
@@ -694,6 +694,7 @@
.It NoHostAuthenticationForLocalhost
.It NumberOfPasswordPrompts
.It PasswordAuthentication
+.It PidFile
.It Port
.It PreferredAuthentications
.It Protocol
diff -u openssh-3.9p1/ssh.c openssh-3.9p1/ssh.c
--- openssh-3.9p1/ssh.c
+++ openssh-3.9p1/ssh.c
@@ -870,6 +870,21 @@
}
}
+static void
+make_pidfile()
+{
+ /* Create pid file as requested. */
+ if (options.pidfile) {
+ FILE *pidfile = fopen(options.pidfile, "w");
+ if (!pidfile)
+ fatal("open pidfile failed: %.200s", strerror(errno));
+ if (fprintf(pidfile, "%i", getpid()) < 0)
+ fatal("write pidfile failed: %.200s", strerror(errno));
+ if (fclose(pidfile))
+ fatal("close pidfile failed: %.200s", strerror(errno));
+ }
+}
+
static int
ssh_session(void)
{
@@ -1002,6 +1017,8 @@
packet_write_wait();
}
+ make_pidfile();
+
/* Enter the interactive session. */
return client_loop(have_tty, tty_flag ?
options.escape_char : SSH_ESCAPECHAR_NONE, 0);
@@ -1173,6 +1190,8 @@
if (daemon(1, 1) < 0)
fatal("daemon() failed: %.200s", strerror(errno));
+ make_pidfile();
+
return client_loop(tty_flag, tty_flag ?
options.escape_char : SSH_ESCAPECHAR_NONE, id);
}
diff -u openssh-3.9p1/ssh_config.5 openssh-3.9p1/ssh_config.5
--- openssh-3.9p1/ssh_config.5
+++ openssh-3.9p1/ssh_config.5
@@ -523,6 +523,8 @@
.Dq no .
The default is
.Dq yes .
+.It Cm PidFile
+Specifies a file to write the pid of the process to.
.It Cm Port
Specifies the port number to connect on the remote host.
Default is 22.
diff -u openssh-3.9p1/debian/changelog openssh-3.9p1/debian/changelog
--- openssh-3.9p1/debian/changelog
+++ openssh-3.9p1/debian/changelog
@@ -1,3 +1,10 @@
+openssh (1:3.9p1-3.1) experimental; urgency=low
+
+ * NMU.
+ * Add PidFile option; useful when -f is given.
+
+ -- Adam Heath <[EMAIL PROTECTED]> Wed, 06 Apr 2005 12:37:30 -0500
+
openssh (1:3.9p1-3) experimental; urgency=low
* Explain how to run sshd from inittab in README.Debian (closes: #147360).
Bug#303452: -o PidFile patch update
I discovered that the previous patch didn't allow the option value to contain
a space. This new patch does(based on ProxyCommand).
diff -u openssh-3.9p1/readconf.c openssh-3.9p1/readconf.c
--- openssh-3.9p1/readconf.c
+++ openssh-3.9p1/readconf.c
@@ -107,7 +107,7 @@
oAddressFamily, oGssAuthentication, oGssDelegateCreds,
oServerAliveInterval, oServerAliveCountMax, oIdentitiesOnly,
oSendEnv, oControlPath, oControlMaster,
- oProtocolKeepAlives, oSetupTimeOut,
+ oProtocolKeepAlives, oSetupTimeOut, oPidFile,
oDeprecated, oUnsupported
} OpCodes;
@@ -200,6 +200,7 @@
{ "controlmaster", oControlMaster },
{ "protocolkeepalives", oProtocolKeepAlives },
{ "setuptimeout", oSetupTimeOut },
+ { "pidfile", oPidFile },
{ NULL, oBadOption }
};
@@ -782,6 +783,15 @@
intptr = &options->setuptimeout;
goto parse_int;
+ case oPidFile:
+if (s == NULL)
+fatal("%.200s line %d: Missing argument.", filename,
linenum);
+charptr = &options->pidfile;
+len = strspn(s, WHITESPACE "=");
+if (*activep && *charptr == NULL)
+*charptr = xstrdup(s + len);
+return 0;
+
case oDeprecated:
debug("%s line %d: Deprecated option \"%s\"",
filename, linenum, keyword);
@@ -926,6 +936,7 @@
options->num_send_env = 0;
options->control_path = NULL;
options->control_master = -1;
+ options->pidfile = NULL;
}
/*
diff -u openssh-3.9p1/readconf.h openssh-3.9p1/readconf.h
--- openssh-3.9p1/readconf.h
+++ openssh-3.9p1/readconf.h
@@ -112,6 +112,7 @@
char*control_path;
int control_master;
+ char*pidfile;
} Options;
diff -u openssh-3.9p1/ssh.1 openssh-3.9p1/ssh.1
--- openssh-3.9p1/ssh.1
+++ openssh-3.9p1/ssh.1
@@ -694,6 +694,7 @@
.It NoHostAuthenticationForLocalhost
.It NumberOfPasswordPrompts
.It PasswordAuthentication
+.It PidFile
.It Port
.It PreferredAuthentications
.It Protocol
diff -u openssh-3.9p1/ssh.c openssh-3.9p1/ssh.c
--- openssh-3.9p1/ssh.c
+++ openssh-3.9p1/ssh.c
@@ -870,6 +870,21 @@
}
}
+static void
+make_pidfile()
+{
+ /* Create pid file as requested. */
+ if (options.pidfile) {
+ FILE *pidfile = fopen(options.pidfile, "w");
+ if (!pidfile)
+ fatal("open pidfile failed: %.200s", strerror(errno));
+ if (fprintf(pidfile, "%i", getpid()) < 0)
+ fatal("write pidfile failed: %.200s", strerror(errno));
+ if (fclose(pidfile))
+ fatal("close pidfile failed: %.200s", strerror(errno));
+ }
+}
+
static int
ssh_session(void)
{
@@ -1002,6 +1017,8 @@
packet_write_wait();
}
+ make_pidfile();
+
/* Enter the interactive session. */
return client_loop(have_tty, tty_flag ?
options.escape_char : SSH_ESCAPECHAR_NONE, 0);
@@ -1173,6 +1190,8 @@
if (daemon(1, 1) < 0)
fatal("daemon() failed: %.200s", strerror(errno));
+ make_pidfile();
+
return client_loop(tty_flag, tty_flag ?
options.escape_char : SSH_ESCAPECHAR_NONE, id);
}
diff -u openssh-3.9p1/ssh_config.5 openssh-3.9p1/ssh_config.5
--- openssh-3.9p1/ssh_config.5
+++ openssh-3.9p1/ssh_config.5
@@ -523,6 +523,8 @@
.Dq no .
The default is
.Dq yes .
+.It Cm PidFile
+Specifies a file to write the pid of the process to.
.It Cm Port
Specifies the port number to connect on the remote host.
Default is 22.
diff -u openssh-3.9p1/debian/changelog openssh-3.9p1/debian/changelog
--- openssh-3.9p1/debian/changelog
+++ openssh-3.9p1/debian/changelog
@@ -1,3 +1,10 @@
+openssh (1:3.9p1-3.1) experimental; urgency=low
+
+ * NMU.
+ * Add PidFile option; useful when -f is given.
+
+ -- Adam Heath <[EMAIL PROTECTED]> Wed, 06 Apr 2005 12:37:30 -0500
+
openssh (1:3.9p1-3) experimental; urgency=low
* Explain how to run sshd from inittab in README.Debian (closes: #147360).
Bug#324741: dpkg-gencontrol - loosed support for arch depend Depends line somewhere ago
On Wed, 24 Aug 2005, Scott James Remnant wrote: > reopen 170575 > merge 170575 324741 > thanks > > On Tue, 2005-08-23 at 20:21 +0200, Bastian Blank wrote: > > > #170575 was marked fixed some time ago, but the version in sid does not > > accept such dependency lines. > > > dpkg has _never_ had support for arch-specific Depend lines, just > Build-Depend. That bug should not have been closed. This is correct, _dpkg_ has never had support. However, dpkg-dev/dpkg-gencontrol did have support at one time(or the support is there but broken), and the arch-specific depends lines are fixed up when generating debian/tmp/DEBIAN/control. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329402: extra ) on expired keys
package: gnupg version: 1.4.1-1 severity: minor For expired headers on keys, gnupg has an extraneous ) before the final closing ]. No patch included, as this is so very trivial. == [EMAIL PROTECTED]:/job/parago/channel_incentives/ofbiz/crypto$ gpg --no-options --no-default-keyring --keyring /usr/share/keyrings/debian-role-keys.gpg --verbose --list-keys gpg: using classic trust model /usr/share/keyrings/debian-role-keys.gpg pub 1024D/38C6029A 2002-12-20 [expired: 2004-01-24)] uid Debian Archive Automatic Signing Key (2003) <[EMAIL PROTECTED]> pub 1024D/30B34DD5 2003-12-03 [expired: 2004-01-14)] uid Debian Archive Automatic Signing Key (2003 v2) <[EMAIL PROTECTED]> pub 1024R/1DB114E0 2004-01-15 [expired: 2005-01-27)] uid Debian Archive Automatic Signing Key (2004) <[EMAIL PROTECTED]> pub 1024D/4F368D5D 2005-01-31 [expires: 2006-01-31] uid Debian Archive Automatic Signing Key (2005) <[EMAIL PROTECTED]> == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323113: svk smerge -b $num IL /repopath/.. /repotpath/.. doesn't fail
package: svk smerge version: 1.02-1 severity: minor [EMAIL PROTECTED]:/bt/incoming$ svk smerge -b 6 Il /janino/projects/janino/current /janino/projects/janino/trunk;echo $? NAME smerge - Automatically merge all changes between branches . ALIASES sm 0 == It should exit with a failure code if an option or command pattern isn't recognized. ps: I forgot the - before Il, which is how I discovered this -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403294: missing depends on lsb-base
Package: aoetools Version: 11-1.1 Severity: serious I was attempting to install aoetools, and got an error from the init script. == Setting up aoetools (11-1.1) ... /etc/init.d/aoetools: line 28: /lib/lsb/init-functions: No such file or directory invoke-rc.d: initscript aoetools, action "start" failed. dpkg: error processing aoetools (--configure): subprocess post-installation script returned error exit status 1 == Installing lsb-base, which provides the above file, allowed it to continue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294351: marked as done (Please extend 9.4's ellipsis style requirement to cover maintainer scripts and dpkg)
> Policy is not a stick to beat maintainers with. Conversly, > changing policy to make a maintainer do a change that they are not > willing to do on their own is a bad idea. You need the Tech Ctte, > really. There's no valid reason to do this, really. Invoking the TC card would be a gross overstepping. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294540: ITP: concurrent -- utility classes for concurrent java programming
On Thu, 10 Feb 2005, Wolfgang Baer wrote: > Package: wnpp > Severity: wishlist > > Package name: concurrent > Version : 1.3.4 > Upstream Author : Doug Lea <[EMAIL PROTECTED]> > URL : http://gee.cs.oswego.edu/dl > License : Public domain > Description : utility classes for concurrent java programming > > The concurrent java library provides standardized, efficient versions of > utility classes commonly encountered in concurrent Java programming. > Discussions of the rationale and applications of several of these > classes can be found in the second edition of Concurrent Programming in Java. > > The package mainly consists of implementations of a few interfaces: > > * Sync -- locks, conditions > * Channel -- queues, buffers > * Barrier -- multi-party synchronization > * SynchronizedVariable -- atomic ints, refs etc > * java.util.Collection -- collections > * Executor -- replacements for direct use of Thread > > Plus some utilities and frameworks that build upon these. How does this fit in with java 1.5(from sun, non-free of course), but what about kaffe/gcj/sablevm? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295213: general: Upgrade removed /usr/local (symlink)
On Mon, 14 Feb 2005, Frank Küster wrote: > Please be so kind and keep the bug number address in the Cc > > Tuomo Valkonen <[EMAIL PROTECTED]> wrote: > > > On Mon, Feb 14, 2005 at 03:24:59PM +0100, Frank Küster wrote: > >> Is any tetex package installed on the system, and can you give the > >> version numbers currently installed and, ideally, of the old ones before > >> the upgrade? We had a bug with /usr/local/ in tetex-base, and this might > >> be connected. > > > > Tetex is installed, tetex-base being currently version 2.0.2c-6. I don't > > know the previous version, but I think I last upgraded sometime around > > mid-january. > > Could it have been after January 24st? This is the date when we released > a version (2.0.2c-4) that erroneously shipped /usr/local/share/texmf in > the deb. This caused a symlink to be converted to a real file for one > user when he upgraded from the buggy version to the fixed version, > 2.0.2c-5 (that did no longer contain that directory). Er, don't think so. dpkg doesn't convert symlinks to dirs. However, if a user uses tar directly, then this can occur.
Bug#294351: Please extend 9.4's ellipsis style requirement tocover maintainer scripts and dpkg
On Mon, 14 Feb 2005, wrote: > I have no intention of using policy to "beat anyone on the head". > To repeat, the dpkg maintainer _asked_ for policy guidance. That is > why he reassigned #254998 to debian-policy. You reassigned it back > to dpkg on the grounds that there was no "bug" in policy. That is > why I opened #294351 as a _wish_, hoping that there would be no > opposition to a simple and desirable extention of a policy clause. Does policy enforce output styles elsewhere? Does anything parse the output of these commands? If not, then it doesn't really matter. Maybe a best practices guide, but to mandate a particular style, hardly not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295619: busybox --help goes to stderr instead of stdout
package: busybox version: 1:0.60.5-2.2 severity: minor Could you please change --help to send it's output to stdout, instead of stderr? --help is a command, not an error, and as such, should not polute stderr. The same goes for all the applets. At the very least, --help should probably behave as the gnu it does for the gnu applet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295621: inconsistent error messages
package: debianutils version: 2.11.2 severity: minor [EMAIL PROTECTED]:/bt/incoming$ run-parts run-parts: missing operand Try run-parts --help' for more information. [EMAIL PROTECTED]:/bt/incoming$ run-parts -u run-parts: option requires an argument -- u Try `run-parts --help' for more information. Note how the first is missing `, or the second has an extra `. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290272: P: Doing something important
Package: cdebootstrap Version: 0.3.1 ... P: Configuring package bash P: Configuring package modutils P: Doing something important P: Doing something important P: Unpacking package apt P: Configuring package apt ... That message in the middle sucks; please change it to say what it is actually doing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298783: xend is stopped before xendomains in debs
package: run-parts On Wed, 9 Mar 2005, Henning Glawe wrote: > Moin, > just discovered a small problem in the xen-debian packages (2.0.4-4, from > people.d.o): > the sysv init links are done in the following way: > > S20xend > S20xendomains > K20xend > K20xendomains > > so xend is shutdown before the xen-domains are shutdown, which of cause fails > when there's no xend... This is a bug in run-parts. It should reverse the order. Or you are not understanding how it works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298783: xend is stopped before xendomains in debs
On Thu, 10 Mar 2005, Miquel van Smoorenburg wrote: > On Wed, 9 Mar 2005, Adam Heath wrote: > >On Wed, 9 Mar 2005, Adam Heath wrote: > >>On Wed, 9 Mar 2005, Henning Glawe wrote: > >>> > >>> Moin, > >>> just discovered a small problem in the xen-debian packages (2.0.4-4, from > >>> people.d.o): > >>> the sysv init links are done in the following way: > >>> > >>> S20xend > >>> S20xendomains > >>> K20xend > >>> K20xendomains > >>> > >>> so xend is shutdown before the xen-domains are shutdown, which of cause > >>> fails > >>> when there's no xend... > > > >>This is a bug in run-parts. It should reverse the order. > >> > >>Or you are not understanding how it works. > > > >reassign 298783 sysv-rc > >thanks > > I don't understand. What is the bug? The order sysv-rc uses to > run the scripts is the standard order used by POSIX when you > do a "for i in S??*". That is well known. If that isn't what > you'd like it to be, fix the priority of the Sxx symlinks. > > Or am I overlooking something ? Hrm. Maybe this is a problem with update-rc.d. But I don't know. update-rc.d defaults bar creates rc2.d/S20bar and rc6.d/K20bar, and update-rc.d defaults foo creates rc2.d/S20foo and rc6.d/K20foo. During start, bar is started before foo, which is what is expected. However, during shutdown, bar is stopped *before* foo, instead of the other way around. Yes, one can change the priority of one of the scripts. But that is a lot more overhead. I'm cc'ing devel, as this could be a more general problem, worthy of a broader fix. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#280773: new xen 2.0 packages
severity 280773 pending thanks http://people.debian.org/~doogie/xen/ Contains 2.0.4, and soon(in about an hour) 2.0.5. They are sitting in experimental, in incoming, waiting for ftp-master to accept them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#691508: [PATCH] ovs-vsctl: Allow command-specific options to mingle with global options.
On 11/02/2012 12:49 PM, Ben Pfaff wrote: > On Mon, Oct 29, 2012 at 03:03:13PM -0500, Adam Heath wrote: >> On 10/29/2012 11:34 AM, Ben Pfaff wrote: >>> Until now, a command like "ovs-vsctl --may-exist add-br br0" yielded a >>> confusing error message. Users had to realize that the correct form was >>> "ovs-vsctl -- --may-exist add-br br0", but instead they often reported a >>> bug or gave up in frustration. Even though the behavior was documented, it >>> was counterintuitive. >>> >>> This commit allows command-specific options to be mixed with global >>> options, making both forms of the command listed above equally acceptable. >> >> Tbh, I would actually prefer to have command-specific options that >> appear in the global area issue an error. >> >> == >> one-vsctl: Found command-specific --may-exist in global area, please >> use -- instead. >> == >> >> See (1) for a reason why I'd prefer it the way I suggested above. >> >> 1: http://lwn.net/Articles/520198/ >>you might need to wait a few days for it to become publically >>available. > > OK, it's available now, and I skimmed over it, but the analogy to > ovs-vsctl isn't really obvious to me. Can you elaborate? Providing variants for valid parameter processing makes it harder to understand. Instead, a warning/error should be issued saying the arg is not understood(and if it appears to be a per-cmd option in global space, then a message saying such should be displayed), but allowing for per-option to work for global is actually *breaking* existing scripts that error out. Any existing script that places --may-exist in global space, without --, will currently have an error. Your patch changes that. So, that is bad. Instead, if you just change the error message displayed in those cases, then there isn't any breakage. The article applies to this senario, because your new patch will break existing scripts. The article also applies because ovs-vsctl should have had better handling of border conditions in arg processing, by providing more concise error messages. == ovs-vsctl: Found an unrecognized option(--may-exist) in the global option area; perhaps you need to use -- to start a per-command option area? == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691508: [PATCH] ovs-vsctl: Allow command-specific options to mingle with global options.
On 11/02/2012 04:19 PM, Ben Pfaff wrote: > I still don't understand. Why would an existing script call ovs-vsctl > with --may-exist as a global option? The call would not do anything > useful, because it would exit with a fatal error every time. Taking > this argument to its logical conclusion, one must never extend any > program by adding a new option, because it could break some existing > script that tries to use that (nonexistent) option. Exactly. Your patch breaks existing scripts, by suddenly allowing for --may-exist to work where it used to not. I'm saying you should just change the error message, but do not allow for it to be used as a global option. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691508: [PATCH] ovs-vsctl: Allow command-specific options to mingle with global options.
On 11/06/2012 11:10 AM, Ben Pfaff wrote: > On Fri, Nov 02, 2012 at 02:26:20PM -0700, Ben Pfaff wrote: >> On Fri, Nov 02, 2012 at 04:21:56PM -0500, Adam Heath wrote: >>> On 11/02/2012 04:19 PM, Ben Pfaff wrote: >>>> I still don't understand. Why would an existing script call ovs-vsctl >>>> with --may-exist as a global option? The call would not do anything >>>> useful, because it would exit with a fatal error every time. Taking >>>> this argument to its logical conclusion, one must never extend any >>>> program by adding a new option, because it could break some existing >>>> script that tries to use that (nonexistent) option. >>> >>> Exactly. Your patch breaks existing scripts, by suddenly allowing for >>> --may-exist to work where it used to not. >> >> You still haven't explained why an existing script would call >> ovs-vsctl with --may-exist as a global option. Why would it do that? >> >>> I'm saying you should just change the error message, but do not allow >>> for it to be used as a global option. >> >> It's an option, and it's easier to do than the alternative patch that >> I sent out, but I don't understand why you think it will break any >> real script. Who is in the habit of writing useless scripts that do >> nothing but provoke errors? > > Do you have any further comment? If you don't see the issue, then I don't feel like trying to convince you of it. I've moved beyond the problem anyways, as my scripts explictly check for existance of whatever before attempting to create whatever. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691508: ovs-vsctl: --may-exist --if-exists don't work
Package: openvswitch-switch Version: 1.4.2+git20120612-9 >From the man page: [--may-exist] add-br bridge [--may-exist] add-br bridge parent vlan [--may-exist] add-port bridge port [column[:key]=value]... [--if-exists] del-port [bridge] port >From my script: ++ ovs-vsctl --may-exist add-port bf-public bf-public ovs-vsctl: unrecognized option '--may-exist' ++ ovs-vsctl --may-exist add-br bf-public ovs-vsctl: unrecognized option '--may-exist' I can work around the --may/--if not being supported for bridge add/remove. For port add/remove, it's a bit harder, as I have to parse the output of list-ports to see if the port exists or not. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691508: ovs-vsctl: --may-exist --if-exists don't work
On 10/26/2012 11:43 AM, Ben Pfaff wrote: > > [snip] Right you are, mea-culpa. You're right that there is an example in the manpage, showing exactly what I want. Sorry for the noise, and thanks for the fast response. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691508: ovs-vsctl: --may-exist --if-exists don't work
On 10/26/2012 01:11 PM, Ben Pfaff wrote: > On Fri, Oct 26, 2012 at 01:00:32PM -0500, Adam Heath wrote: >> On 10/26/2012 11:43 AM, Ben Pfaff wrote: >>> >>> [snip] >> >> Right you are, mea-culpa. You're right that there is an example in >> the manpage, showing exactly what I want. Sorry for the noise, and >> thanks for the fast response. > > It's counterintuitive and confusing. I need to do something about it, > at least improving the error message. So re-open the bug, change the title, and lower the priority? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691508: [PATCH] ovs-vsctl: Allow command-specific options to mingle with global options.
On 10/29/2012 11:34 AM, Ben Pfaff wrote: > Until now, a command like "ovs-vsctl --may-exist add-br br0" yielded a > confusing error message. Users had to realize that the correct form was > "ovs-vsctl -- --may-exist add-br br0", but instead they often reported a > bug or gave up in frustration. Even though the behavior was documented, it > was counterintuitive. > > This commit allows command-specific options to be mixed with global > options, making both forms of the command listed above equally acceptable. Tbh, I would actually prefer to have command-specific options that appear in the global area issue an error. == one-vsctl: Found command-specific --may-exist in global area, please use -- instead. == See (1) for a reason why I'd prefer it the way I suggested above. 1: http://lwn.net/Articles/520198/ you might need to wait a few days for it to become publically available. > > CC: 691...@bugs.debian.org > Reported-by: Adam Heath > Signed-off-by: Ben Pfaff > --- > AUTHORS |1 + > tests/ovs-vsctl.at | 13 - > utilities/ovs-vsctl.8.in | 11 ++-- > utilities/ovs-vsctl.c| 131 + > 4 files changed, 137 insertions(+), 19 deletions(-) > > diff --git a/AUTHORS b/AUTHORS > index 4687865..83e6bb5 100644 > --- a/AUTHORS > +++ b/AUTHORS > @@ -81,6 +81,7 @@ The following additional people are mentioned in commit > logs as having > provided helpful bug reports or suggestions. > > Aaron M. Ucko u...@debian.org > +Adam Heath doo...@brainfood.com > Ahmed Bilal numan...@gmail.com > Alan Shieh ash...@nicira.com > Alban Browaeys pra...@yahoo.com > diff --git a/tests/ovs-vsctl.at b/tests/ovs-vsctl.at > index e903619..cb12f31 100644 > --- a/tests/ovs-vsctl.at > +++ b/tests/ovs-vsctl.at > @@ -15,7 +15,7 @@ dnl RUN_OVS_VSCTL(COMMAND, ...) > dnl > dnl Executes each ovs-vsctl COMMAND. > m4_define([RUN_OVS_VSCTL], > - [m4_foreach([command], [$@], [ovs-vsctl --timeout=5 --no-wait > -vreconnect:emer --db=unix:socket -- command > + [m4_foreach([command], [$@], [ovs-vsctl --timeout=5 --no-wait > -vreconnect:emer --db=unix:socket command > ])]) > m4_define([RUN_OVS_VSCTL_ONELINE], >[m4_foreach([command], [$@], [ovs-vsctl --timeout=5 --no-wait > -vreconnect:emer --db=unix:socket --oneline -- command > @@ -655,6 +655,17 @@ AT_CLEANUP > AT_SETUP([database commands -- negative checks]) > AT_KEYWORDS([ovs-vsctl]) > OVS_VSCTL_SETUP > + > +AT_CHECK([ovs-vsctl --may-exist], > + [1], [ignore], [ovs-vsctl: missing command name (use --help for help) > +], [OVS_VSCTL_CLEANUP]) > +AT_CHECK([ovs-vsctl --may-exist --], > + [1], [ignore], [ovs-vsctl: missing command name (use --help for help) > +], [OVS_VSCTL_CLEANUP]) > +AT_CHECK([ovs-vsctl -- --may-exist], > + [1], [ignore], [ovs-vsctl: missing command name (use --help for help) > +], [OVS_VSCTL_CLEANUP]) > + > AT_CHECK([RUN_OVS_VSCTL([add-br br0])], >[0], [ignore], [], [OVS_VSCTL_CLEANUP]) > AT_CHECK([RUN_OVS_VSCTL([add-br br1])], > diff --git a/utilities/ovs-vsctl.8.in b/utilities/ovs-vsctl.8.in > index 1b80d05..8f70d6b 100644 > --- a/utilities/ovs-vsctl.8.in > +++ b/utilities/ovs-vsctl.8.in > @@ -43,9 +43,9 @@ implemented as a single atomic transaction against the > database. > The \fBovs\-vsctl\fR command line begins with global options (see > \fBOPTIONS\fR below for details). The global options are followed by > one or more commands. Each command should begin with \fB\-\-\fR by > -itself as a command-line argument, to separate it from the global > -options and following commands. (If the first command does not have > -any options, then the first \fB\-\-\fR may be omitted.) The command > +itself as a command-line argument, to separate it from the following > +commands. (The \fB\-\-\fR before the first command is optional.) The > +command > itself starts with command-specific options, if any, followed by the > command name and any arguments. See \fBEXAMPLES\fR below for syntax > examples. > @@ -769,10 +769,9 @@ Delete bridge \fBbr0\fR, reporting an error if it does > not exist: > .IP > .B "ovs\-vsctl del\-br br0" > .PP > -Delete bridge \fBbr0\fR if it exists (the \fB\-\-\fR is required to > -separate \fBdel\-br\fR's options from the global options): > +Delete bridge \fBbr0\fR if it exists: > .IP > -.B "ovs\-vsctl \-\- \-\-if\-exists del\-br br0" > +.B "ovs\-vsctl \-\-if\-exists del\-br br0" > .PP > Set the \fBqos\fR column of the \fBPort\fR record for \fBeth0\fR to > point to a new \fBQoS\fR record, which in turn points with its qu
Bug#626549: xserver-xorg-input-evdev: middle mouse button emulation doesn't anymore by default
severity 626549 important thanks I had this problem to. Bought a new laptop last sunday, installed squeeze. Did a full upgrade to testing earlier this week, and middle button emulation stopped. I suggest adding a debconf prompt during upgrade, and creating a config file snippet in /etc/X11/xorg.conf.d, with the appropriate option enabled. I might even go so far as to suggest that new installs have this prompt too. If (upgrading & $old_version < $version_with_changed_default) || (new_install); then .. fi Having this break during an upgrade is very bad, imho. important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656668: 3.2 has different /sys/class/power
package: linux-image-3.2.0-1-amd64 version: 3.2.1-1 severity: major linux 3.2 changed what is available in /sys/class/power_supply. wmbattery worked fine with 3.1, but the new 3.2 upgrade broke it. This is a kernel problem, please change this back. You can add the new ADP1, but don't remove the BAT0. It's a userspace/kernel breakage, the kernel shouldn't be doing that. From 3.2: == root@urk:~# tree /sys/class/power_supply/ADP1/ /sys/class/power_supply/ADP1/ ├── device -> ../../../ACPI0003:00 ├── online ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── subsystem -> ../../../../../../class/power_supply ├── type └── uevent == From 3.1: == root@urk:~# tree /sys/class/power_supply/BAT0/ /sys/class/power_supply/BAT0/ ├── alarm ├── cycle_count ├── device -> ../../../PNP0C0A:00 ├── energy_full ├── energy_full_design ├── energy_now ├── manufacturer ├── model_name ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── power_now ├── present ├── serial_number ├── status ├── subsystem -> ../../../../../../class/power_supply ├── technology ├── type ├── uevent ├── voltage_min_design └── voltage_now == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656668: 3.2 has different /sys/class/power
severity 656668 minor thanks (haven't actually gotten your mail yet, it's stuck due to greylisting; I'm writing this based on what I see in website). Actually, this is not the correct bug. My laptop lost complete power. The battery was fully drained. I plugged in it, booted it up, and there was *no* BAT0 in that folder. After some amount of charging, I rebooted back into 3.1, and there was the BAT0, but no ADP1. Rebooted back into 3.2, and there was both ADP1 and BAT0. So, the bug here is that when the battery has 0% charge, linux isn't adding it to the list. Sounds like a null vs. 0 type simple logic error. Additionally, linux only appears to enumerate batteries at system boot. What would happen if a battery was added/removed later on? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656675: acpid(8) manpage mentions /proc/acpi/event
package: acpid Version: 1:2.0.14-1 severity: wishlist The manpage for acpid(8) mentions /proc/acpi/event. That file doesn't exist in 3.2(probably 3.1, maybe others). I'm guessing that the file hasn't actually existed for a large number of kernel revisions. Since debian is going to be shipping a 3.x kernel, please modify the manpage to describe modern kernels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656676: acpi_listen(8) manpage has pointless See Also section
package: acpid
Version: 1:2.0.14-1
severity: wishlist
The See Also section the acpi_listen(8) manpage points to regcomp(3),
sh(1), socket(2), connect(2). Why should it point to the functions it
calls, or the shell, or even regcomp?
If that were a sane thing to do, then *all* programs installed in
/{,usr/}{bin,sbin} should mention sh(1), and mention *some* subset of
random functions/libraries that they use.
See Also in a manpage should provide useful links. Maybe one pointed
at acpid(8).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656677: pm-utils long description seems rather pointless
package: pm-utils Version: 1.4.1-9 severity: wishlist Looking at the description of this package, it says it contains scripts for suspending/hibernating a laptop. Why would I install it, when I already have s2disk/s2ram? Please create a better description, like maybe talking about how you can add things into .d style folders. Please make the description differentiate itself from what is already available. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656668: 3.2 has different /sys/class/power
I use module-init-tools 3.16-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699274: wget segfault: -T 0 --no-check-certificate
package: wget version: 1.13.4-2 version: 1.13.4-3 arch: i386 amd64 Issuing a wget to an https scheme that has a bad cert(both expired, and hostname != cert_host), then setting a timeout to 0, causes wget to segfault. == 10:53:19 -0600 adam@zoot:~(zoot)$ wget -T 0 --no-check-certificate "https://demo-stable.ofbiz.apache.org:8443/ecommerce/control/main"; --2013-01-29 10:53:53-- https://demo-stable.ofbiz.apache.org:8443/ecommerce/control/main Resolving demo-stable.ofbiz.apache.org (demo-stable.ofbiz.apache.org)... 140.211.11.50 Connecting to demo-stable.ofbiz.apache.org (demo-stable.ofbiz.apache.org)|140.211.11.50|:8443... connected. WARNING: The certificate of `demo-stable.ofbiz.apache.org' is not trusted. WARNING: The certificate of `demo-stable.ofbiz.apache.org' hasn't got a known issuer. The certificate has expired The certificate's owner does not match hostname `demo-stable.ofbiz.apache.org' HTTP request sent, awaiting response... Segmentation fault == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699923: grub-pc fails to upgrade when virtualized device changes type
package: grub-pc version: 1.99-23.1 severity: important I use opennebula for virtualization. I had originaly created a new image, and installed squeeze to it. The device mapping I used at the time exposed this drive as /dev/vda. Then, I cloned(copied) the image file, and started a new machine. When I started the new machine, I neglected to set the emulation correctly, so the drive was seen as /dev/sda. The machine booted correctly thru grub and early boot, into squeeze. The problem came about when I attempted to update to wheezy. Grub couldn't reinstall itself, because /boot/grub/device.map had hd0 configured to be /dev/vda. So grub-install couldn't find the correct drive mapping for what was now /dev/sda. Some kind of warning/fix should be detected/applied to device.map in these cases. Ideally, a grub upgrade should probably generate a new, temporary device.map, and compare to the current, and ask if it should be updated if changed. ps: Personally, I think this should be fixed before wheezy release. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639008: APT: removable automatically installed package list is not alphabetical
package: apt version: 0.8.10.3+squeeze1 severity: minor == The following packages were automatically installed and are no longer required: libffado-dev sharutils bochsbios libtasn1-3-dev libaudio-dev libiec61883-0 libkadm5clnt-mit7 liblucene-java libgpg-error-dev libc-dev-bin python-all mesa-common-dev libsysfs-dev libdirectfb-extra linux-libc-dev libavahi-client-dev libffi-dev tofrodos libsamplerate0-dev libdbus-1-dev wodim libraw1394-dev libxml2-dev libffado2 cdrdao psfontmgr libtiffxx0c2 libxml++2.6-2 libkadm5srv-mit7 libpixman-1-dev libpulse-browse0 libxcb-render0-dev libavahi-common-dev libsvga1-dev libcelt-dev == Please make that list alphabetical, just like the others. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639290: partial upgrade from squeeze to wheezy fails
package: libc6
The warnings about the locales below is because I don't have that
installed in the debootstrap squeeze chroot.
==
zoot:/Media/chroot# rsync squeeze.save/ squeeze/ --exclude
var/cache/apt/archives/ --exclude etc/apt/ -a
zoot:/Media/chroot# chroot squeeze
root@zoot:/# apt-get install perl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libdb4.7 perl-modules
Suggested packages:
perl-doc libterm-readline-gnu-perl libterm-readline-perl-perl make
The following NEW packages will be installed:
libdb4.7 perl perl-modules
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/7907 kB of archives.
After this operation, 30.7 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or
directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libdb4.7.
(Reading database ... 8499 files and directories currently installed.)
Unpacking libdb4.7 (from .../libdb4.7_4.7.25-9_i386.deb) ...
Selecting previously deselected package perl-modules.
Unpacking perl-modules (from
.../perl-modules_5.10.1-17squeeze1_all.deb) ...
Selecting previously deselected package perl.
Unpacking perl (from .../perl_5.10.1-17squeeze1_i386.deb) ...
Processing triggers for man-db ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or
directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up libdb4.7 (4.7.25-9) ...
Setting up perl-modules (5.10.1-17squeeze1) ...
Setting up perl (5.10.1-17squeeze1) ...
root@zoot:/# apt-get install -t testing iceweasel
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer
required:
libdb4.7
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
fontconfig fontconfig-config gcc-4.6-base libasound2 libatk1.0-0
libatk1.0-data libavahi-client3 libavahi-common-data libavahi-common3
libc-bin libc6
libcairo2 libcups2 libdatrie1 libdb5.1 libdbus-1-3 libevent-1.4-2
libexpat1 libffi5 libfontconfig1 libfreetype6 libgcrypt11
libgdk-pixbuf2.0-0
libglib2.0-0 libgnutls26 libgpg-error0 libgssapi-krb5-2 libgtk2.0-0
libgtk2.0-common libhunspell-1.2-0 libice6 libjasper1 libjpeg62
libjpeg8 libk5crypto3
libkeyutils1 libkrb5-3 libkrb5support0 liblocale-gettext-perl
libmozjs5d libnspr4-0d libnss3-1d libpango1.0-0 libpcre3 libpixman-1-0
libpng12-0 libsm6
libstartup-notification0 libstdc++6 libtasn1-3
libtext-charwidth-perl libtext-iconv-perl libthai-data libthai0
libtiff4 libvpx0 libx11-6 libx11-data
libx11-xcb1 libxau6 libxcb-render0 libxcb-shm0 libxcb-util0 libxcb1
libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3
libxft2 libxi6
libxinerama1 libxml2 libxrandr2 libxrender1 libxt6 multiarch-support
perl perl-base perl-modules shared-mime-info ttf-dejavu-core ucf
x11-common
xulrunner-5.0
Suggested packages:
defoma ttf-lyx latex-xft-fonts xfonts-mathml ttf-mathematica4.1
xprint mozplugger libasound2-plugins glibc-doc locales cups-common
rng-tools gnutls-bin
krb5-doc krb5-user librsvg2-common gvfs libjasper-runtime
ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp
ttf-arphic-gkai00mp ttf-arphic-bkai00mp
perl-doc libterm-readline-gnu-perl libterm-readline-perl-perl make
libdbus-glib-1-2 libgconf2-4 libgnomevfs2-0 libnotify1
libnotify1-gtk2.10 libgnomeui-0
libcanberra0
Recommended packages:
libc6-i686 dbus libglib2.0-data hicolor-icon-theme libgtk2.0-bin
hunspell-en-us hunspell-dictionary myspell-dictionary x-ttcidfont-conf
xml-core
libswitch-perl libpod-plainer-perl libclass-isa-perl
The following NEW packages will be installed:
fontconfig fontconfig-config gcc-4.6-base iceweasel libasound2
libatk1.0-0 libatk1.0-data libavahi-client3 libavahi-common-data
libavahi-common3
libcairo2 libcups2 libdatrie1 libdb5.1 libdbus-1-3 libevent-1.4-2
libexpat1 libffi5 libfontconfig1 libfreetype6 libgcrypt11
libgdk-pixbuf2.0-0
libglib2.0-0 libgnutls26 libgpg-error0 libgssapi-krb5-2 libgtk2.0-0
libgtk2.0-common libhunspell-1.2-0 libice6 libjasper1 libjpeg62
libjpeg8 libk5crypto3
libkeyutils1 libkrb5-3 libkrb5support0 libmozjs5d libnspr4-0d
libnss3-1d libpango1.0-0 libpcre3 libpixman-1-0 libpng12-0 libsm6
libstartup-
Bug#639290: Acknowledgement (partial upgrade from squeeze to wheezy fails)
Summary of simple steps to replicate the problem: == debootstrap squeeze squeeze chroot squeeze (edit sources.list, add wheezy) (edit apt.conf, disable suggests/recommends, set default-release to stable) apt-get install perl apt-get -t testing install iceweasel (or perl, or libc6) == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639290: partial upgrade from squeeze to wheezy fails
On 08/25/2011 12:37 PM, Jonathan Nieder wrote: > Hi APT team, > > Quick puzzle for you. > > Adam Heath wrote: > >> E: Could not perform immediate configuration on 'perl'. Please see man >> 5 apt.conf under APT::Immediate-Configure for details. (2) >> == >> >> libc6(wheezy) breaks perl << 5.12. perl 5.12 depends on libgdm3. >> libgdm3 pre-depends multiarch-support. multiarch-support depends on >> libc6(wheezy). >> >> This loop can't be broken by apt, so it complains. >> >> An upgrade or dist-upgrade from squeeze to wheezy *does* work. > > The dependencies seem right. I would expect my package manager to > either unpack the new perl or temporarily deconfigure perl in order to > upgrade libc. perl should not satisfy dependencies until the new > version is configured because the output of "perl -V:libpth" is wrong, > as described at <http://bugs.debian.org/636686>. > > But as pointed out at [*], when APT::Immediate-Configure is set, > "apt-get install" just bails out in this situation instead. Is that a > libc bug, a perl bug, or an apt bug? > > [*] http://bugs.debian.org/639290 639290 says that you can deconfigure perl. That is not possible. You can only unpack a newer perl(but not configure), which then causes perl to be in a deconfigured state. My guess here is that Breaks should not be used, but Conflicts. That still won't solve the actual problem(I think). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639290: partial upgrade from squeeze to wheezy fails
On 08/25/2011 12:37 PM, Jonathan Nieder wrote: > Hi APT team, > > Quick puzzle for you. > > Adam Heath wrote: > >> E: Could not perform immediate configuration on 'perl'. Please see man >> 5 apt.conf under APT::Immediate-Configure for details. (2) >> == >> >> libc6(wheezy) breaks perl << 5.12. perl 5.12 depends on libgdm3. >> libgdm3 pre-depends multiarch-support. multiarch-support depends on >> libc6(wheezy). >> >> This loop can't be broken by apt, so it complains. >> >> An upgrade or dist-upgrade from squeeze to wheezy *does* work. > > The dependencies seem right. I would expect my package manager to > either unpack the new perl or temporarily deconfigure perl in order to > upgrade libc. perl should not satisfy dependencies until the new > version is configured because the output of "perl -V:libpth" is wrong, > as described at <http://bugs.debian.org/636686>. > > But as pointed out at [*], when APT::Immediate-Configure is set, > "apt-get install" just bails out in this situation instead. Is that a > libc bug, a perl bug, or an apt bug? > > [*] http://bugs.debian.org/639290 And or remove the Depends: libc6(wheeze) from multiarch-support, and have that package provide the multiarch-aware ld.so, and dpkg-divert the one in libc6. Then have libc6 Replaces: multiarch-support, replacing the diverted-to ld.so, then undo the diversion. Or something. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639290: partial upgrade from squeeze to wheezy fails
On 08/26/2011 12:43 AM, Jonathan Nieder wrote: > reassign 639290 apt > quit > > Hi again, > > Adam Heath wrote: > >> 639290 says that you can deconfigure perl. That is not possible. > > Why? I thought the whole point of having a separate perl and > perl-base is that perl is not essential. > > So as an intermediate state during an upgrade, it should be perfectly > fine to deconfigure perl or to upgrade it without immediately > configuring it. How would you change the status in dpkg from Installed to Half-Installed(ie, deconfigure it)? I don't believe there is a way to do that, except by way of unpacking some version(any version). > Reassigning to APT. Please feel free to reassign back to libc6 or > perl when the problem is clearer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639290: partial upgrade from squeeze to wheezy fails
On 08/26/2011 09:20 AM, Jonathan Nieder wrote: > Julian Andres Klode wrote: > >> Obviously dpkg has no --deconfigure command that you could >> use for this. > > But it does have an --auto-deconfigure command that does just what one > might expect, so... > > We are dancing around the actual point, which is that if I understand > the report correctly, apt does not allow > > A Depends: B (>= new) > B Breaks: A (<= old) > > when A is important enough to get the immediate-configure treatment. > In this example, A is "a full-featured perl, including the -V:libpth > feature" and B is "support in the dynamic linker for multiarch paths". > > If A were essential or an unpack-time dependency of an essential > package, I would understand. But it is not. I don't think this is > right, unless that new category with new constraints on its > dependencies is described in policy or a similar document somewhere. Well, fixing this in apt won't be good enough, as that version won't be made available in stable. And you won't be able to upgrade to the newer apt in testing first, as that will eventually pull in the newer package set that is broken. Changing the algo apt is not the correct fix for this problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712909: ifquery doesn't process source correctly
package: ifupdown version: 0.7.8 severity: minor I make use of a relative path to source in /etc/network/interfaces, as implied by the manpage. ifup -a will see all defined interfaces in external files. However, ifquery uses $PWD when attempting to find the referenced file. So, if I am in /root, ifquery --list doesn't show anything from the included file. If I changed $PWD to /etc/network, then ifquery --list functions correctly. A workaround is to specify the full path in /etc/network/interfaces. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712909: ifquery doesn't process source correctly
On 06/20/2013 01:21 PM, Andrew Shadura wrote: A workaround is to specify the full path in /etc/network/interfaces. I'm not sure it's a bug, actually... It's said nowhere if relative paths are supported at all, or if they're calculated relatively to /e/n/interfaces. Not sure how it should be done. Not fixing the issue now, but not closing it either. ifquery should probably do the same thing as ifup. ifup -a *does* prepend /etc/network to it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712909: ifquery doesn't process source correctly
On 06/20/2013 01:37 PM, Andrew Shadura wrote:
Hello,
On Thu, 20 Jun 2013 13:30:14 -0500
Adam Heath wrote:
ifquery should probably do the same thing as ifup. ifup -a *does*
prepend /etc/network to it.
Ifquery is the same ifup which just doesn't run commands. The parsing
part is the same, so it's kind of strange effect. Could you please
double check (I'm not sure I have enough time to dig into that now)?
Ok, you are right, I was wrong. ifquery/ifup actually do the same thing.
==
root@virt-4:~# strace ifquery foobar 2>&1|grep open
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY) = 3
open("/etc/network/interfaces", O_RDONLY) = 3
open("vlans", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open("vlans/*.intf", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/run/network/ifstate", O_RDONLY) = 3
root@virt-4:~# strace ifup foobar 2>&1|grep open
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY) = 3
open("/etc/network/interfaces", O_RDONLY) = 3
open("vlans", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open("vlans/*.intf", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/run/network/ifstate", O_RDWR|O_CREAT|O_APPEND, 0666) = 3
open("/run/network/ifstate", O_RDWR|O_CREAT|O_APPEND, 0666) = 3
open("/run/network/.ifstate.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
open("/run/network/ifstate", O_RDWR|O_CREAT|O_APPEND, 0666) = 3
open("/run/network/.ifstate.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
==
Neither one is pre-pending /etc/network. So, this bug degrades to
either making ifupdown pre-pend /etc/network(my recommendation), or
fixing interfaces(5) to not show an example with a relative path, and be
explicity that relative paths are not supported.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#133491: Copyright of dpkg-awk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually, if I had to assign a license to anything I have written, I would probably go for 3-clause bsd-like. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOMt30iix9wovUpIkRAsIfAJsEbWA3C9PBA7EiwAApZwdY6yCcFwCfehop 4hTcOmnSTxDJPcxiDfFgxEQ= =dsFp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619841: RFP: MooseFS -- MooseFS is a fault tolerant, network distributed file system.
Any update on this? I just downloaded the 1.6.20-2.tar.gz from upstream, and it almost works. * $(MAKE) is commented out in debian/rules. * All the upstream example config files install as /etc/$foo.dist; they then need to be renamed for them to work. Since they are registered with dpkg as $foo.dist, this is sub-optimal. * Upstream example configs want to run as nobody, but the init scripts try to configure the permssions as mfs:mfs. I haven't gotten to much further than that, 'cuz my testing cluster has 1 32-bit node, and 3 64-bit nodes, and I haven't yet compiled a 64-bit version. I'm going to attempt to get this working, and will post further updates here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663041: please enable ib_srpt
Package: linux-image-3.3.0-rc6-amd64 Version: 3.3~rc6-1~experimental.1 Severity: wishlist http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=f59e842fc0871cd5baa213dc32e0ce8e5aaf4758 That enables SRP target support for Infiniband. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663041: please enable ib_srpt
On 03/08/2012 01:57 AM, Jonathan Nieder wrote: reassign 663041 src:linux-2.6 3.3~rc6-1~experimental.1 found 663041 linux-2.6/3.2.9-1 tags 663041 + upstream patch quit Adam Heath wrote: [commit a42d985bd5b234da8b61347a78dc3057bf7bb94d, applied during the 3.3 merge window] That enables SRP target support for Infiniband. For 3.3 release candidates in experimental, I believe you are requesting that CONFIG_INFINIBAND_SRPT=m be added to the kernel configuration in topconfig. For wheezy, a backport of the driver would presumably be useful. Thanks for a pleasant report, Jonathan Additionally, upgrading from 3.2.0 to 3.3.0-rc6 increased my ipoib bandwidth from 130MB/s to 283MB/s. I'm not certain which patchset does that. But that should really be a separate bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655026: bash <(pipeline) fails to reap children soon enough, causes file descriptor leak
package: bash version: 4.1-3 The attached short script showcases the bug. The important things needed for it to be replicated, is that the loop *must* be run in a function. The inner <(pipeline) is where the leak takes place. If you don't have the complex if .. fi, then bash will never reap the pipe descriptors, and eventually the limit of 1024 descriptors is hit. If you run the script, and you get a 'Warning', then your bash is leaking descriptors. The work-around is also part of the script. Run any sub-process in a pipe. The script does ": | :", as the shortest non-intrusive pipeline. pipe-leak-bug.sh Description: Bourne shell script
Bug#663623: mount doesn't support /etc/fstab.d
Package: mount Version: 2.20.1-4 Severity: wishlist libmount has support for /etc/fstab.d. However, /bin/mount does not. According to upstream(1), this wasn't fully supported, but will be for 2.21. I think it would be nice to backport this feature for the next release of stable, if possible. 1: http://comments.gmane.org/gmane.linux.utilities.util-linux-ng/5077 ps: filing the bug here, so it doesn't get misplaced. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664139: lintian should warn about mis-named file in /etc/apt/sources.list.d/
package: lintian version: 2.5.5~bpo60+1 severity: minor Reading package lists... Done N: Ignoring file 'my-common-apt' in directory '/etc/apt/sources.list.d/' as it has no filename extension I generally name these files $foo.list, but forgot to in this one situation. Lintian should warn in that case. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619841: No package of expected?
On 03/19/2012 04:43 PM, Vincent Blut wrote: > Le 15/03/2012 11:54, Frédéric Massot a écrit : >> Hi, >> > > Hi Frédéric, > >> No package of expected? > > I don't know if Aurélien (cc'd) is still working on it, but it seems that > Adam is interested to package it. Adam? I've got it packaged, and uploaded to the local repo here at work. I've moved the config files from /etc/ to /etc/mfs, kinda like how upstream has on it's TODO list. I just haven't had time to send my fixes anywhere. I still have my key in debian, but I haven't actually uploaded anything in a *long* time. >> This is a very interesting file system and running in production. The *biggest* issue is that you do *not* want your master to go away. We've had 16 power outages today in 3.5 hours, and the test rig(which doesn't have a hot-failover for master, nor even a ups) has gotten rather upset that mfs-master doesn't auto-start, and you have to run mfsmetarestore -a. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619841: No package of expected?
On 03/19/2012 06:58 PM, Vincent Blut wrote: Good to hear :-) BTW, did you package the last version (1.6.24)? 1.6.20-~3 is what I have uploaded locally. I'm using git as well, but I need to split/rebase my work into separate chunks before I send it anywhere. I can certainly use a newer upstream if needed. Well, we could make a script to auto-start it, but I think the Right Things™ is to manually run 'mfsmetarestore -a' in order to possibly catch any errors/warnings during the fixing operation. Sure. However, one thing that irks me is all the clients fail to mount the master if it isn't available at bootup, so then I have to go to each one and kick it. It'd be nice if the client kept retrying the master. The chunkservers do. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656675: acpid(8) manpage mentions /proc/acpi/event
On 01/24/2012 09:12 AM, Ted Felix wrote: On 1/20/2012 3:39 PM, Adam Heath wrote: The manpage for acpid(8) mentions /proc/acpi/event. That file doesn't exist in 3.2(probably 3.1, maybe others). I'm guessing that the file hasn't actually existed for a large number of kernel revisions. Since debian is going to be shipping a 3.x kernel, please modify the manpage to describe modern kernels Thanks for the bug report. The man page explains what happens if the /proc/acpi/events file does not exist: "If the events file does not exist, acpid will attempt to connect to the Linux kernel via the input layer and netlink." So the man page covers both old and modern kernels. Michael, I recommend closing this. I'll check again when I get home. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656676: acpi_listen(8) manpage has pointless See Also section
On 01/24/2012 09:15 AM, Ted Felix wrote: On 1/20/2012 3:42 PM, Adam Heath wrote: See Also in a manpage should provide useful links. Maybe one pointed at acpid(8). Thanks for the bug report. This has been done in my local version. It will appear in the next release of acpid (2.0.15). In the meantime, a patch is attached that can be used to close this bug. Looks good to me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664971: utf8 weirdness in some archived bugs
package: bugs.debian.org 473236: Found-In contains '0xab' 644945: Subject contains '0x95' 400153: Fixed-In contains '0xa0' 391560: Subject contains '0xff' '0xf4' '0xff' 0xfd' 107361: Found-In contains '0xa0' 117166: Fixed-In contains '0xa0' 153968: Fixed-In contains '0xa0' 390970: Fixed-In contains '0xa0' 185176: Fixed-In contains '0xa0' 24177: Found-In contains '0xad' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664972: incorrect blocked-by processing on bugs.d.o
package: bugs.debian.org severity: minor There are several bugs that are blocked by bug#1, which of course doesn't exist. Maybe the blocked-by processor doesn't verify that the target bug actually exists? == debbugs=> select b.archived, a.from_id as parent_bug_id, a.type_id, a.to_id as missing_bug_id from bug_assoc a join bug b on a.from_id = b.bug_id where a.to_id in (select bug_id from bug where archived is null); archived | parent_bug_id | type_id | missing_bug_id --+---++ N| 508138| BLOCKED_BY | 1 N| 475553| BLOCKED_BY | 1 Y| 541617| BLOCKED_BY | 1 Y| 543130| BLOCKED_BY | 1 Y| 539538| BLOCKED_BY | 1 Y| 532343| BLOCKED_BY | 1 Y| 534788| BLOCKED_BY | 1 Y| 535970| BLOCKED_BY | 1 (8 rows) == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664978: active bugs that are merged with archived bugs
package: bugs.debian.org == debbugs=> select a.bug_id, a.archived, b.type_id, c.bug_id, c.archived from bug a join bug_assoc b on a.bug_id = b.from_id join bug c on b.to_id = c.bug_id where a.archived = 'N' and c.archived = 'Y' and b.type_id = 'MERGED_WITH'; bug_id | archived | type_id | bug_id | archived +--+-++-- 518921 | N| MERGED_WITH | 526519 | Y (1 row) == doogie@busoni:/org/bugs.debian.org/spool$ grep Merged-With db-h/21/518921.summary archive/63/521863.summary archive/19/526519.summary db-h/21/518921.summary:Merged-With: 521863 526519 archive/63/521863.summary:Merged-With: 518921 526519 archive/19/526519.summary:Merged-With: 518921 521863 == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665200: http://bugs.debian.org/package/desktop-file-utils has invalid relative links
package: bugs.debian.org The url in $subject links to relative links, like 'bugreport.cgi' and 'version.cgi'. However, since the .htaccess pattern matching doesn't actually issue an external redirect, the base directory is wrong, so you end up getting a 404 when you click on anything. == 10:06:27 AM < WakiMiko > anyone else having problems with bugs.debian.org? when i try to look at a bug i get "The requested URL /x/package/bugreport.cgi was not found on this server. 10:24:23 AM < WakiMiko > i clicked on a link at http://bugs.debian.org/package/desktop-file-utils == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665684: bad package values in archived bugs
package: bugs.debian.org The following list of bad package values are split incorrectly in the cgi scripts. == file: archive/00/79500.summary package: amanda-server 1:2.4.1p1-12 file: archive/01/256801.summary package: libstdc++3-dev (1:3.0.4-7) , g++-3.0 (1:3.0.4-7) file: archive/04/93004.summary package: tetex-base version: 1.0.2+2804-7 severity: normal file: archive/06/476706.summary package: linux-image-2.6.18-6-686version: 2.6.18.dfsg.1-18etch1 ibm server6 disk in raid51 hba fiber channel (qla2xxx) on the boot of my linux image, 1 times on 3 it works. when it works my local disk is sda $ dmesg ...qla2xxx :04:04.0: found an isp2312, irq 201, iobase 0xf8842000 file: archive/06/476706.summary package: linux-image-2.6.18-6-686version: 2.6.18.dfsg.1-18etch1 ibm server6 disk in raid51 hba fiber channel (qla2xxx) on the boot of my linux image, 1 times on 3 it works. when it works my local disk is sda $ dmesg ...qla2xxx :04:04.0: found an isp2312, irq 201, iobase 0xf8842000 file: archive/08/358508.summary package: gallery version: 1.5.2-pl2-1 severity: normal file: archive/11/150911.summary package: xcdroast version: 0.98+0alpha10-4 severity: normal file: archive/16/75216.summary package: kdelibs3 4:2.0-20001002-0 file: archive/22/159922.summary package: ttf-openoffice version: 1.0-2 severity: critical file: archive/25/470825.summary package: ia32-libs version: 2.2 severity: normal file: archive/25/152825.summary package: perforate version: 1.0-13 severity: important file: archive/32/134732.summary package: debbugs: file: archive/38/407938.summary package: sisu version: 0.48.8-7 file: archive/54/164154.summary package: kdebase-libs 4:2.2-14 file: archive/60/137460.summary package: euro-support version: 1.10 severity: normal file: archive/63/19763.summary package: watchdog: file: archive/77/135477.summary package: boot-floopies: file: archive/78/178578.summary package: kde 4:2.2.25 file: archive/90/166190.summary package: amavis-exim version: 20020517-22 severity: important file: archive/94/21494.summary package: informVersion: 6.14-4 file: archive/95/21495.summary package: informVersion: 6.14-4 file: archive/96/654796.summary package: linux-source-3.1version: linux-image-3.1.0-1-686-pae file: archive/96/285196.summary package: exim4-config version: 4.34-9 severity: normal file: archive/97/654797.summary package: linux-source-3.1version: linux-image-3.1.0-1-686-pae == -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665686: bad found-in values in archived bugs
package: bugs.debian.org The following bugs have a url for their found-in values. I don't believe this is allowed. file: archive/36/297536.summary Found-In: http://d-i.alioth.debian.org/manual/en.powerpc/ch05s01.html file: archive/62/472762.summary Found-In: http://ftp.nl.debian.org/debian/dists/etch/main/installer-sparc/current/images/sparc32/netboot/2.6/boot.img -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668231: vmstat: output isn't aligned when a large amount of memory is available
package: procps version: 1:3.2.8-9 severity: minor See attached file(which shouldn't have any word-wrap issues). Basically, I have a machine with 24G of ram, and the value rows in vmstat don't align with their headers. 17:22:46 -0500 doogie@vm10:/home/doogie(master)$ vmstat 1 procs ---memory-- ---swap-- -io -system-- cpu r b swpd free buff cache si sobibo in cs us sy id wa 1 0 0 12342016 14352 1160624800 2506 3073 247 295 0 2 86 11 0 0 0 12332260 14352 1161533200 2048 2064 592 386 0 1 99 0 0 0 0 12325112 14352 1162252400 2048 2072 467 352 0 0 99 0 0 1 0 12313312 14360 1163418800 2504 2676 748 399 1 1 99 0 0 0 0 12297308 14360 1165032400 2048 2064 885 560 0 1 98 0 0 0 0 12278340 14372 1166618000 3908 136316 1450 2362 1 6 91 3 0 0 0 12265856 14372 1167758000 2048 2064 758 445 1 0 99 0 0 0 0 12260672 14384 1168363600 3912 135592 981 860 0 5 93 2 17:24:47 -0500 doogie@vm10:/home/doogie(master)$ free total used free sharedbuffers cached Mem: 24744900 172223127522588 0 15420 16342500 -/+ buffers/cache: 864392 23880508 Swap: 974844 0 974844
Bug#646965: lintian should check for validly formed /etc/apt/sources.list.d/foo files
package: linitian version: 2.4.3 severity: wishlist As $subject says. I had the following line in a local package, which apt barfed on. It would have been nice if lintian had warned me. http://name.domain.com/path distribution Note the lack of main/contrib/non-free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780622: RFP: mini-sendmail -- reads standard input and sends a copy of the message found there to all of the addresses listed
Package: wnpp Version: N/A; originaly reported 2003-06-11 Severity: wishlist * Package name: mini-sendmail Version : 1.3.2 Upstream Author : Jef Poskanzer * URL :http://www.acme.com/software/mini_sendmail/ * License : BSD Description : Reads its standard input up to an end-of-file and sends a copy of the message found there to all of the addresses listed. The message is sent by connecting to a local SMTP server. This means mini_sendmail can be used to send email from inside a chroot(2) area. -- This was originally filed as an ITP, by someone else, at http://bugs.debian.org/197018. It was closed, with ssmtp as a suggested workaround. That is not what this program is for. This program is meant to be installed into a reduced chroot, and redirect command line mail to localhost:25. It needs a real working MTA on the local machine. This program is meant to be used by php running in a chroot. ssmtp, on the otherhand, is designed to be such a real MTA. If it is installed. then it removes any other installed MTA(due to package conflicts). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780680: libpam-modules: pam_userdb.so depends on a library in /usr
package: libpam-modules Version: 1.1.3-7.1 Severity: serious A library in /lib shouldn't depend on a library in /usr/lib. However, pam_userdb.so has such an issue. == root@zoot:~# ldd /lib/x86_64-linux-gnu/security/pam_userdb.so linux-vdso.so.1 (0x76081000) libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x7f22218a3000) libdb-5.1.so => /usr/lib/x86_64-linux-gnu/libdb-5.1.so (0x7f222152) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7f22212e8000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f2220f3f000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f2220d3b000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f2220b1d000) /lib64/ld-linux-x86-64.so.2 (0x7f2221cc4000) == This problem also seems to still be around in version 1.1.8-3.1, which is in jessie. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762060: nodejs: non FHS config file location
package: nodejs version: 0.10.32-1nodesource1~wheezy1 severity: serious == root@HOST:~# npm config set --global proxy http://192.168.3.245:3128/ root@HOST:~# npm config list ; cli configs registry = "https://registry.npmjs.org/"; user-agent = "npm/1.4.28 node/v0.10.32 linux x64" ; globalconfig /usr/etc/npmrc proxy = "http://192.168.3.245:3128/"; ; node bin location = /usr/bin/node ; cwd = /root ; HOME = /root ; 'npm config ls -l' to show all defaults. == The location of that global config is quite bad, on a debian-based system. Please move it to /etc/, at the least. I'm marking this serious, as it goes against proper debian policy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#816406: mdadm mkconf doesn't parse mdadm.conf correctly(whitespace)
Package: mdadm Severity: minor Version: 3.3.2-5+deb8u1 /usr/share/mdadm/mkconf attemps to read DEVICE out of /etc/mdadm/mdadm.conf, using sed. It does this, with a simple regex, "s/^DEVICE //p". This is not valid. mdadm.conf(5) says you can have any whitespace after it(space, tab, even newline). The first sentence of the SYNTAX section, says it's a series of words separated by whitespace.
Bug#816409: /usr/share/mdadm/mkconf removes DEVICE settings
Package: mdadm
Severity: important
Version: 3.3.2-5+deb8u1
If I specify a DEVICE line in mdadm.conf, /usr/share/mdadm/mkconf does
*not* keep it; instead, the output file contains the DEVICE line
prefixed with a comment character('#').
==
root@virt-22:~# diff -u <(cat /etc/mdadm/mdadm.conf)
<(/usr/share/mdadm/mkconf)
--- /dev/fd/63 2016-03-01 11:03:13.103248544 -0600
+++ /dev/fd/62 2016-03-01 11:03:13.099248544 -0600
@@ -6,7 +6,7 @@
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to
scan, using
# wildcards if desired.
-#DEVICE partitions containers
+#DEVICE /dev/sde* /dev/sdf*
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
@@ -18,8 +18,7 @@
MAILADDR root
# definitions of existing MD arrays
-DEVICE /dev/sde* /dev/sdf*
ARRAY /dev/md/0 metadata=1.2 UUID=93abeb06:069eec23:6f98c97c:ceffb159
name=virt-22:0
ARRAY /dev/md/1 metadata=1.2 UUID=849ae009:3e40351e:620f0c9c:09f4e4ba
name=virt-22:1
-# This configuration was auto-generated on Fri, 26 Feb 2016 12:15:21
-0600 by mkconf
+# This configuration was auto-generated on Tue, 01 Mar 2016 11:03:13
-0600 by mkconf
==
It's also not nice to reorder the file, but that is a separate bug that
I don't feel like filing right now.
Bug#816410: "/usr/share/mdadm/mkconf generate" can erase mdadm.conf if it encounters an error
Package: mdadm Severity: important Version: 3.3.2-5+deb8u1 If you pass 'generate' to the mkconf script, it attempts to parse some existing values out of the file, then does an "exec >$CONFIG". At this point, the output file has been removed, and is effectively 0 bytes in size. All the existing content is gone. Later on, if there is an error, the script might abort writing the full file out; this is because set -e is in place. Please write to a temp file, and do an atomic move at the very end.
Bug#816687: -switch: Please use ifquery in init script
Package: openvswitch-switch Version: 2.3.0+git20140819-3 Severity: minor In /etc/init.d/openvswitch-switch, the function network_interfaces does a manual parse of /etc/network/interfaces. This prevents it from finding interfaces defined in /etc/network/interfaces.d. Please switch to use "ifquery --allow ovs --list" instead; that program has existed since 2012.
Bug#871420: dpkg(1) manpage path-exclude docs possible license issue
package: dpkg version: 1.17.27 In the manpage for dpkg, there is an example for path-exclude/path-include: == --path-exclude=/usr/share/doc/* --path-include=/usr/share/doc/*/copyright == These 2 patterns will end up skipping packages that have /usr/share/doc/$foo as a symlink to another package. Which means things like perl-base, libstdc++6, libgcc1, etc, which have their docs symlinked to another package from the same source, will be broken, as the copyright for the package is not available at /usr/share/doc/$pkg/copyright, as *required* by policy. Perhaps --path-exclude=/usr/share/doc/*/*, with the same include, might be better.
Bug#465651: Dpkg/Version.pm needs to use Dpkg::Gettext
Package: dpkg-dev Version: 1.14.16.6 Undefined subroutine &Dpkg::Version::_g called at /usr/share/perl5/Dpkg/Version.pm line 204. If I use Dpkg::Gettext, the problem goes away. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465781: /etc/init.d/isns stop is not fail-safe
package: isns version: 2.1-01+dfsg-1 Please add --oknodo to start-stop-daemon --stop. If the daemon is not running, and you attempt to stop it, s-s-d will fail. The --oknodo keeps the failure from happening. This keeps the package from being removed if the daemon has been stopped. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465782: /var/isns not removed during purge
package: isns version: 2.1-01+dfsg-1 severity: serious Please remove /var/isns when the package is purged. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506355: provide antlr library as a separate package
package: antlr version: 2.7.7-6 severity: minor This package has an java antlr library, some python antlr thing, and a system binary. When other packages just want to make use of the antlr jar by itself, all the other things get pulled in. Please split this package, and provide a libantlr-java, following the java policy in debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506357: split out the documentation
package: libbsf-java version: 1:2.4.0-2 severity: minor This package contains duplicate api docs(/usr/share/doc/$pkg/api and /usr/share/doc/$pkg/docs/api. Additionally, the documentation should not be in the library package. There's no reason to force it to be installed, when you just need to have the code in the package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506356: split out api docs into separate package
package: libcommons-digester-java version: 1.8-1 severity: minor The api docs included in this package are only useful during development of software. For production servers, they just take up useless space. Please split the api docs into a separate package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506359: split out api docs into a separate package
package: libcommons-discovery-java version: 0.4-1 severity: minor Production servers don't need to have api docs installed for every single library that their software requires. The api docs are only useful when developing code, not when running it. Please move the api docs into a separate package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506362: please move documentation to a separate package
package: libfreemarker-java version: 2.3.13+debian1-1 severity: minor The documentation included in this package is only of interest to developers; if another package has a depends on it, it is not interested in having all this extra baggage installed. It just increases the disk space usage. Please split the documentation into a separate package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506360: split api docs into separate package
package: libcommons-codec-java version: 1.3-4 severity: minor There is no reason to force the api docs to be installed, when one is only interested in the library code. Please split the docs into a separate package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506361: please split out api docs
package: libcommons-pool-java version: 1.3-1 severity: minor This package contains api documentation, that is not useful at runtime; it's only useful during development. Having it included for all installs, is a waste, as most installs don't need to see the individual method calls. Please split it out into a separate package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506366: move api docs to a separate package
package: libjdom1-java version: 1.0-4 severity: minor It's poor taste to include the api documentation alongside the code; packages that only require the library end up having to have the docs installed as well. This increases the disk space usage on production servers. Please split the docs into a separate package, to solve this problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
