Bug#446665: mercury: should this package be removed?
Lucas Nussbaum wrote: Package: mercury Version: 0.11.0.rotd.20040511-5 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, Your package came up as a candidate for removal from Debian, because: * 4 RC bugs opened for a long time Of the bugs: * #281369: Dummy RC bug against Mercury explained below. * #430313: ldbl128 transition for alpha, powerpc, sparc, s390 I'm reasonably sure that doesn't apply to Mercury as the language doesn't support long doubles, but I want to be certain before closing this bug. * #297217: mercury: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment * #381813: mercury: FTBFS: cannot stat `./debian/tmp/usr/lib/mercury/bin': No such file or directory For both of these, Mercury has _never_ worked with gcc-4.0 - it does work with gcc-3.4 (recommended by upstream), gcc-4.1 or gcc-4.2 (my preferred version, but there's some issues and testing I need to work through). * not suitable for a stable release according to #281369 I've checked with the previous maintainer and upstream on this one. The reason for the bug is that the previous maintainer didn't want a 'release of the day' (Mercury has two available branches - the numbered releases, and the 'release of the day') getting into testing/stable. I intend to package only the numbered releases. Upstream has no objections to this being packaged for Debian. * Low popcon (19 insts) I consider the current package is too old to be useful (I've been telling people to install from source rather than the package). Also, as a logic programming language, it's unlikely to ever have a particularly high popcon. * Hasn't been in testing for a very long time See comments on bug #281369 * New upstream release available for a long time now I'm working on packaging that - it's still going to take some time (in the order of weeks). If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. This is confusing - I thought it was already orphaned, which is when I filed an ITA. snip If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. Whether to remove or not in the meantime I'm not certain. What makes the most sense - to leave it in until I get upload a replacement (for which I will need to find a sponsor), or remove it in the meantime and I can apply to get it added to Debian as a fresh package? My preference would be to keep it, as upgrading a package will be easier than adding a new one, and it means the name, bug history, description etc. gets kept, but I'm open to suggestions on that one. I will close this bug in the meantime. It's not an option to quickly release a partial fix, as Mercury is a reasonably large package (and it takes quite a while to build) and I want to have something pretty much right before a sponsor gets to spend any time on it. Cheers, Roy Ward. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446691: defrag: should this package be removed?
Package: defrag Version: 0.73pjm1-8 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, While reviewing some packages, your package came up as a possible candidate for removal from Debian, because: * 4 RC bugs, opened for a long time, with no resolution path in sight. * only really works with old ext2 filesystems. * dangerous with modern ext2/ext3 FS, without telling so (#396449). I think that it would be much better to remove it from Debian for now. There's no point in keeping it just to collect RC bugs. If upstream work happens, you can always re-upload it... If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. If you agree, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn ftp.debian.org retitle nn RM: packagename -- RoM; reasons thanks For more information, see http://wiki.debian.org/ftpmaster_Removals http://ftp-master.debian.org/removals.txt If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446692: twin: should this package be orphaned?
Package: twin Version: 0.5.1-3 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing some packages, your package came up as a package that should maybe be orphaned by its maintainer, because: * 3 RC bugs, 2 of them opened for a long time, all of them without any comment from the maintainer. * NMU never acked. f you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: packagename -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422822: libgstreamer-perl: FTBFS: Failed 3/31 test scripts, 34/492 subtests failed
Hi Marc, On 08/05/07 at 12:16 +0200, Michael Ablassmeier wrote: Package: libgstreamer-perl Severity: serious Version: 0.09-1 Justification: policy violation hi, Lucas has rebuild the archive on i386 and your package Failed to Build from Source with the following error(s): dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-8 Failed 8/8 tests, 0.00% okay t/GstIndex..ok t/GstIndexFactory...ok t/GstIterator...ok t/GstMessageok 13/70 skipped: clock tests t/GstMiniObject.ok t/GstObject.ok t/GstPaddubious Test returned status 0 (wstat 11, 0xb) DIED. FAILED tests 32-39 Failed 8/39 tests, 79.49% okay t/GstPadTemplateok t/GstPipeline...ok t/GstPlugin.ok t/GstPluginFeature..ok t/GstQuery..ok t/GstRegistry...undef is not of type GStreamer::PluginFeature at t/GstRegistry.t line 22. # Looks like you planned 21 tests but only ran 3. # Looks like your test died just after 3. dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 4-21 Failed 18/21 tests, 14.29% okay [..] Failed Test Stat Wstat Total Fail Failed List of Failed --- t/GstGhostPad.t 255 65280 8 15 187.50% 1-8 t/GstPad.t 01139 16 41.03% 32-39 t/GstRegistry.t 255 6528021 36 171.43% 4-21 34 subtests skipped. Failed 3/31 test scripts, 90.32% okay. 34/492 subtests failed, 93.09% okay. the full log can be found here: http://people.debian.org/~lucas/logs/2007/05/rebuild.sid.i386/libgstreamer-perl_0.09-1_sid32.buildlog Could you have a look at this bug? It has been opened for a longgg time, and I can still reproduce it. See e.g http://people.debian.org/~lucas/logs/2007/10/09/libgstreamer-perl_0.09-1_sid32.buildlog libgstreamer-perl shows up in my list of packages that should maybe be removed/orphaned, but I would prefer to avoid filing such bugs on your packages ;) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446693: uclibc: should this package be orphaned?
Package: uclibc Version: 0.9.27-1 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing some packages, your package came up as a package that should maybe be orphaned by its maintainer, because: * 4 RC bugs opened for a long time, with no action from the maintainer on 3 of them. * several new upstream versions available. If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: packagename -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428186: Consider offering only a dev version.
You might want to consider only offering a dev version of guichan, and require that packages using guichan link statically. This is recommended by the debian policy manual in certain cases, such as for libraries whose interfaces are in flux or under development. http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-static Guichan upstream recommends that every project that uses guichan includes the source files manually in their project. I think the end effect is the same thing as linking statically. Although with this solution, there would be no libguichan* or libguichan-dev package. http://guichan.sourceforge.net/wiki/index.php/Getting_started -Brandon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446665: mercury: should this package be removed?
Hi Roy, On 15/10/07 at 11:03 +1300, Roy Ward wrote: * New upstream release available for a long time now I'm working on packaging that - it's still going to take some time (in the order of weeks). If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. This is confusing - I thought it was already orphaned, which is when I filed an ITA. Ooops, the ITA line on the PTS should be in bold :-) I missed it. I'm perfectly fine with keeping the package in Debian for now, if you are working on packaging the new version. Thank you for the very detailed information. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428186: Consider offering only a dev version.
Severity: normal Brandon wrotes: You might want to consider only offering a dev version of guichan, and require that packages using guichan link statically. This is recommended by the debian policy manual in certain cases, such as for libraries whose interfaces are in flux or under development. http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-static Guichan upstream recommends that every project that uses guichan includes the source files manually in their project. I think the end effect is the same thing as linking statically. Although with this solution, there would be no libguichan* or libguichan-dev package. http://guichan.sourceforge.net/wiki/index.php/Getting_started -Brandon Hello, bumping SONAMES is a good thing for often needed packages and if upstream provides SONAME support, I will include it. The current solution (with conflicts) is okay. So I set the severity of this bug to 'normal' and I will close it if upstream (and after that this package) provides the support. -- Mit freundlichem Gruß / With kind regards, Patrick Matthäi E-Mail: [EMAIL PROTECTED] Homepage: http://www.Linux-Dev.org/ begin:vcard fn;quoted-printable:Patrick Matth=C3=A4i n;quoted-printable:Matth=C3=A4i;Patrick org:Ameus IT-Systeme;Technik adr:;;Technologiepark 21;Paderborn;Nordrhein-Westfalen;33100;Deutschland email;internet:[EMAIL PROTECTED] x-mozilla-html:TRUE url:http://www.ameus.de/ version:2.1 end:vcard
Bug#432414: marked as done (vcdimager is GPLv2 or later, debian/copyright says GPLv2 only)
Your message dated Sun, 14 Oct 2007 22:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#432414: fixed in vcdimager 0.7.23-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: vcdimager
Version: 0.7.23-3
Severity: serious
The debian/copyright file states the following:
| This program is free software; you can redistribute it and/or modify
| it under the terms of the GNU General Public License as published by
| the Free Software Foundation; version 2 dated June, 1991.
However all files in vcdimager have this mention:
| This program is free software; you can redistribute it and/or modify
| it under the terms of the GNU General Public License as published by
| the Free Software Foundation; either version 2 of the License, or
| (at your option) any later version.
This is a very important distinction now that GPLv3 is out and is
incompatible with GPLv2.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.20.1 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages vcdimager depends on:
ii libc6 2.5-11GNU C Library: Shared libraries
ii libcdio6 0.76-1library to read and control CD-ROM
ii libiso9660-4 0.76-1library to work with ISO9660 files
ii libpopt0 1.10-3lib for parsing cmdline parameters
ii libvcdinfo00.7.23-3 library to extract information fro
ii libxml22.6.29.dfsg-1 GNOME XML library
vcdimager recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: vcdimager
Source-Version: 0.7.23-4
We believe that the bug you reported is fixed in the latest version of
vcdimager, which is due to be installed in the Debian FTP archive:
libvcdinfo-dev_0.7.23-4_powerpc.deb
to pool/main/v/vcdimager/libvcdinfo-dev_0.7.23-4_powerpc.deb
libvcdinfo0_0.7.23-4_powerpc.deb
to pool/main/v/vcdimager/libvcdinfo0_0.7.23-4_powerpc.deb
vcdimager_0.7.23-4.diff.gz
to pool/main/v/vcdimager/vcdimager_0.7.23-4.diff.gz
vcdimager_0.7.23-4.dsc
to pool/main/v/vcdimager/vcdimager_0.7.23-4.dsc
vcdimager_0.7.23-4_powerpc.deb
to pool/main/v/vcdimager/vcdimager_0.7.23-4_powerpc.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nicolas Boullis [EMAIL PROTECTED] (supplier of updated vcdimager package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Oct 2007 00:12:48 +0200
Source: vcdimager
Binary: libvcdinfo0 vcdimager libvcdinfo-dev
Architecture: source powerpc
Version: 0.7.23-4
Distribution: unstable
Urgency: low
Maintainer: Nicolas Boullis [EMAIL PROTECTED]
Changed-By: Nicolas Boullis [EMAIL PROTECTED]
Description:
libvcdinfo-dev - library to extract information from VideoCD (development
files)
libvcdinfo0 - library to extract information from VideoCD
vcdimager - A VideoCD (VCD) image mastering and ripping tool
Closes: 432414
Changes:
vcdimager (0.7.23-4) unstable; urgency=low
.
* Fix debian/copyright that obsoleted pretended vcdimager was GPL v2
only while it is GPL v2 or above. Thanks to Samuel Hocevar who pointed
the problem.(Closes: #432414)
* Use ${binary:Version} instead of the deprecated ${Source-Version},
as suggested by lintian.
* Don't ignore failures of make distclean, as suggested by lintian.
Files:
c8f125fbb84fdf0a9a678485fae8a5ff 803 otherosfs optional vcdimager_0.7.23-4.dsc
ea149d6910e454387c1312b38ce32f56 194408 otherosfs optional
vcdimager_0.7.23-4.diff.gz
ebe7ae5afcdfe1402d80dc38004be75f 571060 otherosfs optional
vcdimager_0.7.23-4_powerpc.deb
97f5b16d3c0d50f549871ffb8b71090c 161144 libdevel optional
libvcdinfo-dev_0.7.23-4_powerpc.deb
dd41ea3b46bb869f79db6c3289cf5ee6 135568 libs optional
libvcdinfo0_0.7.23-4_powerpc.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Processed: Severity
Processing commands for [EMAIL PROTECTED]: severity #428186 normal Bug#428186: libguichan0: symbols dropped without soname bump Severity set to `normal' from `serious' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: tag 445720 pending Bug#445720: segmentation fault There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Setting back to serious
Processing commands for [EMAIL PROTECTED]: severity #428186 serious Bug#428186: libguichan0: symbols dropped without soname bump Severity set to `serious' from `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446710: ntpd won't start up due to upgraded libssl
Package: ntp Version: 1:4.2.4p3+dfsg-1 Severity: grave Justification: renders package unusable Recently libssl0.9.8 was upgraded to 0.9.8f-1 When this happenned the following occured in the logs: Oct 15 14:03:28 jandi3 ntpd[3848]: ntpd [EMAIL PROTECTED] Mon Aug 13 16:20:18 UTC 2007 (1) Oct 15 14:03:28 jandi3 ntpd[3848]: ntpd: OpenSSL version mismatch. Built against 90805f, you have 908070 and ntpd failed to start. Solved (temporarily) by downgrading to libssl0.9.8 version 0.9.8e-9. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20final_dccp (PREEMPT) Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages ntp depends on: ii adduser 3.105 add and remove users and groups ii libc6 2.6.1-5GNU C Library: Shared libraries ii libcap1 1:1.10-14 support for getting/setting POSIX. ii libreadline5 5.2-3 GNU readline and history libraries ii libssl0.9.8 0.9.8e-9 SSL shared libraries ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii netbase 4.30 Basic TCP/IP networking system ii perl 5.8.8-11 Larry Wall's Practical Extraction ntp recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444715: skippy: should this package be removed?
On Sun, 2007-09-30 at 16:13 +0200, Lucas Nussbaum wrote: Hi, While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * 1 RC bug opened for a long time. This bug is tagged help for a while and nobody has stepped in. * useless with X.org, superseded by skippy-xd. It's only superseeded by skippy-xd on systems where composite runs reasonably fast, witch is only a little share of all. If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. I've been thinking about orphaning/removing skippy, but I still feel that it can be usefull to some. If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. ACK -- Niv -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: severity 446711 grave Bug#446711: ntp: Please build against OpenSSL 908070 Severity set to `grave' from `important' merge 446711 446710 Bug#446710: ntpd won't start up due to upgraded libssl Bug#446711: ntp: Please build against OpenSSL 908070 Merged 446710 446711. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: package 'vncserver' should be removed from amd64
Processing commands for [EMAIL PROTECTED]: severity 276948 grave Bug#276948: vncserver: Segmentation fault on amd64 Severity set to `grave' from `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Severity
Processing commands for [EMAIL PROTECTED]: severity #428186 normal Bug#428186: libguichan0: symbols dropped without soname bump Severity set to `normal' from `serious' -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446524: marked as done (linhdd: Execute error: /usr/bin/linHDD line 411)
Your message dated Mon, 15 Oct 2007 10:26:28 +0530 with message-id [EMAIL PROTECTED] and subject line linHDD: Please check.. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linhdd Version: 0.4-2 Severity: grave Justification: renders package unusable When I try to run linHDD it gives this error: Traceback (most recent call last): File /usr/bin/linHDD, line 559, in ? main() File /usr/bin/linHDD, line 554, in main DriveWin() File /usr/bin/linHDD, line 411, in __init__ self.frac = float(self.perc.rstrip(%)) / 100 AttributeError: 'NoneType' object has no attribute 'rstrip' The source code on this lines is: self.prt_lst = [] self.prt_lst = self.get_prt_lst(init_drv) self.d1 = self.get_params(init_drv) self.perc = self.get_free(self.prt_lst[0]) if self.perc == '': self.perc = 0% self.frac = 0 else: self.frac = float(self.perc.rstrip(%)) / 100 hdico = gtk.gdk.pixbuf_new_from_xpm_data(hdd_xpm) Thanks for packing for debian !!! -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=es_MX, LC_CTYPE=es_MX (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linhdd depends on: ii hdparm7.7-1 tune hard disk parameters for high ii python2.4.4-6An interactive high-level object-o ii python-gtk2 2.12.0-1 Python bindings for the GTK+ widge linhdd recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Hi, Thanks for reporting bug! Please check that, You are running as root. This is same as: #442093. I confess that man page and description is somewhat bad. It will be fixed in next upload. Sorry, for inconvience.. -- Cheers, --- Kartik Mistry || GPG: 0xD1028C8D || IRC: kart_ kartikmistry.org/blog || kartikm.wordpress.com -- ---End Message---
