Bug#587587: [Pkg-sysvinit-devel] Bug#587587: Persists, affects ManageEngine NetFlow Analyzer
Hi Petter, > -Message d'origine- > De : Petter Reinholdtsen [mailto:petter.reinholdt...@usit.uio.no] De la part > de Petter Reinholdtsen > Envoyé : 28 décembre 2016 14:15 > À : Philippe Cloutier <pclout...@gvq.ca>; 587...@bugs.debian.org > Objet : Re: [Pkg-sysvinit-devel] Bug#587587: Persists, affects ManageEngine > NetFlow Analyzer > > [Philippe Cloutier] > > This seems to persist in jessie, and seems to affect ManageEngine > > NetFlow Analyzer 12.1, which uses an init script. I did not install > > NetFlow Analyzer from a Debian package. The init script does not come > > with LSB headers. The result is equally catastrophic and cryptic. > > What happen when you add LSB headers and dependency information? I managed to fix dpkg's database by adding the following LSB header and running insserv: ### BEGIN INIT INFO # Provides: OpManagerServer # Required-Start:$remote_fs $named # Required-Stop: $remote_fs $named # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start or stop ManageEngine NetFlow Analyzer ### END INIT INFO I do not know if this is a condition to trigger this bug, but I notice that /etc/init.d/OpManagerServer is a symlink to /opt/ManageEngine/OpManager/bin/na_service. > > Which version of insserv do you have installed? Jessie's version, i.e. 1.14.0-5.
Bug#587587: Persists, affects ManageEngine NetFlow Analyzer
This seems to persist in jessie, and seems to affect ManageEngine NetFlow Analyzer 12.1, which uses an init script. I did not install NetFlow Analyzer from a Debian package. The init script does not come with LSB headers. The result is equally catastrophic and cryptic. If, as seems to be the case, insserv considers init scripts without LSB headers as having an absolute dependency on all other scripts, I recommend upgrading severity to serious. Philippe Cloutier Développement des systèmes d'information Groupe Voyages Québec * 1 [418] 525-4585 #107 | 1[800] 463-1598 7 1 [418] 525-8005 * <mailto:pclout...@gvq.ca> pclout...@gvq.ca
Bug#820794: Fixed
fixed 820794 2:4.2.14+dfsg-0+deb8u2 thanks I confirm that 4.2.14+dfsg-0+deb8u2 finally actually fixes. 4.2.14+dfsg-0+deb8u2 has reached stable-security. Thank you very much Mathieu. Philippe Cloutier Développement des systèmes d'information Groupe Voyages Québec * 1 [418] 525-4585 #107 | 1[800] 463-1598 7 1 [418] 525-8005 * <mailto:pclout...@gvq.ca> pclout...@gvq.ca P Est-ce nécessaire dimprimer ce message?
Bug#820794: marked as pending
Merci d'avance Mathieu. Note that the link to git.debian.org is broken (404). > -Message d'origine- > De : Mathieu Parent [mailto:math.par...@gmail.com] > Envoyé : 7 décembre 2016 15:46 > À : 820794-submit...@bugs.debian.org > Objet : Bug#820794: marked as pending > > tag 820794 pending > thanks > > Hello, > > Bug #820794 reported by you has been fixed in the Git repository. You can > see the changelog below, and you can check the diff of the fix at: > > http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=68168a5 > > --- > commit 68168a5c57df43425bfe40a69fc28c32a08b63bf > Author: Mathieu Parent> Date: Wed Dec 7 21:45:45 2016 +0100 > > Changelog for previous commit > > diff --git a/debian/changelog b/debian/changelog > index 2259e6c..edf9c25 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -1,3 +1,9 @@ > +samba (2:4.2.14+dfsg-0+deb8u2) UNRELEASED; urgency=medium > + > + * Fix smbclient compatibility with Windows 10 (Closes: #820794) > + > + -- Mathieu Parent Wed, 07 Dec 2016 21:44:28 +0100 > + > samba (2:4.2.14+dfsg-0+deb8u1) jessie; urgency=high > >* New upstream release. > > -- > To unsubscribe, send mail to 820794-unsubscr...@bugs.debian.org.
Bug#820794: Correction
De : Philippe Cloutier [mailto:pclout...@gvq.ca] Envoyé : 18 juillet 2016 14:09 À : 820794-subscr...@bugs.debian.org; 820794-submit...@bugs.debian.org; cont...@bugs.debian.org Objet : Confirmed tags 820794 + confirmed thanks > I am also experiencing this bug on 2 Debian 8 clients on 2 tested trying to > install a Windows 10 SMB server. That is, trying to *access* a Windows 10 SMB server. The affected clients have no issues accessing Windows 7 and Windows Server 2003 servers.
Bug#806446: resolv.conf(5): single-request-reopen description misleading
Package: manpages Version: 3.74-1 Severity: normal Tags: ipv6 Option single-request-reopen was documented following ticket #699387: The resolver uses the same socket for the A and requests. Some hardware mistakenly sends back only one reply. When that happens the client system will sit and wait for the second reply. Turning this option on changes this behavior so that if two requests from the same port are not handled correctly it will close the socket and open a new one before sending the second request. While the description is correct, it seems to imply that the option is only meant to workaround broken hardware (presumably routers). This may have been the original intent, but as I personally found out, the option also works around broken Windows Server DNS servers. In my case, this was Windows Server 2008 [R1], which is relatively obsolete, but according to http://robert.penz.name/902/slow-dns-resolving-with-linux-systems-against-windows-dns-server/ this persists in current versions, so even though the fault seems to be Microsoft's, this better be as clear as possible. As a minimum, we should use a generic designation (something like "DNS servers" rather than "hardware"). It may even be warranted to mention specific examples, as if I understand correctly, this affects default Debian clients using default Windows Server DNS servers. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) manpages depends on no packages. manpages recommends no packages. Versions of packages manpages suggests: ii konqueror [man-browser] 4:4.14.2-1 ii man-db [man-browser] 2.7.0.2-5 -- no debconf information
Bug#803515: ppp: chap-secrets permissions reset to 600 every upgrade
Package: ppp Version: 2.4.6-3.1 Severity: normal postinst modifies the permissions of 2 configuration files, pap-secrets and chap-secrets: # install /etc/ppp/pap-secrets and /etc/ppp/chap-secrets from templates, # if necessary for file in pap-secrets chap-secrets; do if [ -f /etc/ppp/$file ]; then TAG=$(head --lines=1 /etc/ppp/$file) if [ "$TAG" = "#GENERATED-BY-DEBIAN-INSTALLER#" ]; then (sed -e "s/-HOSTNAME-/$HOST/g" /usr/share/ppp/$file; \ cat /etc/ppp/$file) > /etc/ppp/$file.tmp mv /etc/ppp/$file.tmp /etc/ppp/$file fi else sed -e "s/-HOSTNAME-/$HOST/g" < /usr/share/ppp/$file > /etc/ppp/$file fi chmod 600 /etc/ppp/$file done The permission change at the last line is always performed, even on upgrade. This causes /etc/ppp/chap-secrets to go back to 0600 even if the administrator has set different permissions. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ppp depends on: ii init-system-helpers 1.22 ii libc62.19-18+deb8u1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libpcap0.8 1.6.2-2 ii procps 2:3.3.9-9 ppp recommends no packages. ppp suggests no packages. -- no debconf information
Bug#795319: Please improve port testing use case
Package: netcat-traditional Version: 1.10-41 Severity: wishlist Tags: upstream By default, netcat outputs nothing when it connects. This makes an instance connecting from an instance connected indistinguishable until the target host has sent content or a timeout has expired (after which netcat displays an error if it failed to connect). A timeout will hapen when trying to connect to a filtered port. Option -v solves this by printing a message when the connection is established, but is not enabled by default. This could be addressed either by making -v the default or via documentation. Documentation could at least specify that -v prints a line when the connection is established. There could also be explicit treatment of the issue in the introduction or in the BUGS section.
Bug#703852: [Pkg-mediawiki-devel] Bug#703852: Bug#703852: [mediawiki] mw{en, dis}ext ineffective for new installs
2013/4/2 Thorsten Glaser t.gla...@tarent.de On Thu, 28 Mar 2013, Filipus Klutiero wrote: There's a very simple solution to that which would solve even more problems. Unfortunately, it requires a larger change. Well, let’s just not do that right now. The upgrade to 1.19 was on very short notice already, and, IIRC, Jonathan wanted to make something that installs more nicely after the release anyway. And, for what’s worth, I’m obviously against any non-backwards-compatible changes in that manner… I don't see which backwards-incompatibility you have in mind. The list of extensions in /etc/mediawiki-extensions/extensions-available/ has nothing for Interwiki (except a symlink to its predessors, SpecialInterwiki). The SpecialInterwiki.php one is the correct one to use. https://evolvis.org/plugins/mediawiki/wiki/evolvis/index.php/Special:Interwiki (for example) works just fine (provided you’re Forge Admin ☺), and that’s what this extension is supposed to provide. I didn't mean Special:Interwiki couldn't work. I'm just saying we're missing a symlink to the new (although outdated) version. I'm not aware of actual problems keeping the old version would cause, but if we have the new version, we should at least have a symlink to it. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke
Bug#468668: Bug: #468668: Unable to start d-i after running win32-loader (empty GRUB)
Hi Didier, thanks, I don't know why I didn't get Robert's reply. I didn't use win32-loader after filing this report. I figure if this bug was so easy to reproduce and persisted, someone else would have confirmed it. It might have only happened when GRUB was not installed yet, but GRUB is already installed on this PC so I can't test that quickly. I may test when I get a new PC, perhaps in a couple of years :-) Until then, if nobody else is experiencing, this is likely fixed. 2010/11/10 Didier 'OdyX' Raboud did...@raboud.com tags 468668 +unreproducible thanks Hi Filipus, you reported this bug (#468668) 2½ years ago and never answered to Robert's questions. Is this bug still reproducible for you using actual Squeeze's win32-loader ? I'm hereby tagging this bug as unreproducible; tell me if it can be reproduced nowadays or if I can close it. (I pushed a standalone version there if you want to try from a Windows host: http://alioth.debian.org/~odyx-guest/win32-loader-standalone.exehttp://alioth.debian.org/%7Eodyx-guest/win32-loader-standalone.exe) Thanks in advance, cheers, OdyX, win32-loader co-maintainer -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com
Bug#508240: closed by Don Armstrong [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) (Re: Bug#508240: Filipus Klutiero banned from posting to debian-release)
Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the lists.debian.org package: #508240: Filipus Klutiero banned from posting to debian-release It has been closed by Don Armstrong [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Don Armstrong [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) by replying to this email. Sujet: Re: Bug#508240: Filipus Klutiero banned from posting to debian-release Expéditeur: Don Armstrong [EMAIL PROTECTED] Date: Mon, 8 Dec 2008 22:38:43 -0800 Destinataire: [EMAIL PROTECTED] Destinataire: [EMAIL PROTECTED] On Tue, 09 Dec 2008, Filipus Klutiero wrote: As indicated in the forwarded mail, I was banned from posting to debian-release (I did not receive any reply to that mail). See #508240 where you previously brought up this issue, along with previous messages on this subject whose existance you continue to ignore. #508240 is the report your message replies to. If you think some previous messages shed light on this issue, mention which ones. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#468773: copyright outdated about source
Package: nfs-utils Version: 1.1.1-13 Severity: minor copyright contains This is a git snapshot, downloaded August 6th, 2007 using the following commands: git clone git://git.linux-nfs.org/pub/linux/nfs-utils/ nfs-utils-1.1.1\~git-20070709 ( cd nfs-utils-1.1.1\~git-20070709/ sh ./autogen.sh ) tar --exclude=.git -zcf nfs-utils_1.1.1\~git-20070709.orig.tar.gz nfs-utils-1.1.1\~git-20070709 but 1.1.1-13 is the true 1.1.1 release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#468487: allows unauthorized remote arbitrary code execution (CVE-2007-5689)
Package: sun-java6 Version: 6-00-2 Severity: critical Tags: security, upstream The sun-java6 version in testing is vulnerable to CVE-2007-5689 : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5689 From http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5689 : Overview The Java Virtual Machine (JVM) in Sun Java Runtime Environment (JRE) in SDK and JRE 1.3.x through 1.3.1_20 and 1.4.x through 1.4.2_15, and JDK and JRE 5.x through 5.0 Update 12 and 6.x through 6 Update 2, allows remote attackers to execute arbitrary programs, or read or modify arbitrary files, via applets that grant privileges to themselves. Impact CVSS Severity (version 2.0): CVSS v2 Base score: 10.0 (High) (AV:N/AC:L/Au:N/C:C/I:C/A:C) (legend) Impact Subscore: 10.0 Exploitability Subscore: 10.0 This is fixed in the unstable version, which is waiting a missing ia64 build or to be forced to migrate.
Bug#468256: doesn't configure on first use
Package: reportbug Version: 3.39 Severity: normal reportbug doesn't ask to configure it when using it for the first time on this machine. -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/chealer/.reportbugrc: reportbug_version 3.39 mode expert ui text -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages reportbug depends on: ii apt 0.7.11 Advanced front-end for dpkg ii python2.4.4-6An interactive high-level object-o ii python-central0.5.15-0.1 register and build utility for Pyt reportbug recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466783: Ethernet not capitalized in package descriptions
Package: bridge-utils Version: 1.4-1 Severity: minor ethernet should be capitalized in the package descriptions. BTW, it's superfluous to talk about required Linux versions now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466812: Kde not completely capitalized in short description
Package: knmap Version: 2.1-1 Severity: minor In the short description Kde interface to nmap, the Network Mapper, Kde should be completely capitalized: KDE. BTW, there is no need to mention nmap's homepage in the extended description. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466814: no way to report upstream bugs
Package: knmap Version: 2.1-1 Severity: normal According to About Knmap, Please use http://bugs.kde.org to report bugs. But there's no knmap product in KDE's Bugzilla. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466494: please don't recommend openoffice.org-style-{hiconstrast,industrial}
Le February 19, 2008 12:54:54 pm Rene Engelhard, vous avez écrit : tag 466494 + pending thanks Philippe Cloutier wrote: Please only suggest openoffice.org-style-hiconstrast and openoffice.org-style-industrial. I red the descriptions, and I see nothing these do besides adding to the choice of the other 3 themes which are installed by default. -crystal only is installed per default when you have -kde, same with -gtk. Unless I'm missing something, -crystal and -tango are also installed by default, the same way as -hiconstast and -industrial currently are, through -common. Though I don't think this is bad, because people like me who just installed openoffice.org-writer still get the crystal theme. But we can make hicontrast and industrial suggests, yes.. Thank you
Bug#466333: Wrong capitalization for Xfce
Le February 18, 2008 02:17:08 am Christian Perrier, vous avez écrit : Quoting Philippe Cloutier ([EMAIL PROTECTED]): Package: win32-loader Version: 0.6.1 Severity: minor In the question about the desktop environment, Xfce is completely capitalized (XFCE). It should be Xfce. I think that translations unfuzzy is OK for this one (basically, that means 's/XFCE/Xfce' on PO files. I checked quickly and IIRC only the question is translated, not the choices.
Bug#466494: please don't recommend openoffice.org-style-{hiconstrast,industrial}
Package: openoffice.org-common Version: 1:2.3.1-5 Severity: wishlist Please only suggest openoffice.org-style-hiconstrast and openoffice.org-style-industrial. I red the descriptions, and I see nothing these do besides adding to the choice of the other 3 themes which are installed by default. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466497: Ethernet not capitalized in descriptions
Package: packeth Version: 1.5-1 Severity: minor Ethernet should be capitalized in the short and extended descriptions. BTW, in It allows you to create and send any possible packet or sequence of packets on the ethernet. I think you mean packets via Ethernet rather than packets on the ethernet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466333: Wrong capitalization for Xfce
Package: win32-loader Version: 0.6.1 Severity: minor In the question about the desktop environment, Xfce is completely capitalized (XFCE). It should be Xfce. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464066: X Windows in extended description
Package: laptop-mode-tools Version: 1.35-1 Severity: minor The last sentence of the extended description contains X Windows: It also supports various other power management features, such as starting and stopping daemons depending on power mode, automatically hibernating if battery levels are too low, and adjusting terminal blanking and X Windows screen blanking. This should be replaced by X Window System or X11. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463501: allows unauthorized remote arbitrary code execution (CVE-2007-5689)
Package: sun-java5 Version: 1.5.0-10-3 Severity: critical Tags: security, fixed-upstream 1.5.0-10 is vulnerable to CVE-2007-5689 : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5689 From http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5689 : Overview The Java Virtual Machine (JVM) in Sun Java Runtime Environment (JRE) in SDK and JRE 1.3.x through 1.3.1_20 and 1.4.x through 1.4.2_15, and JDK and JRE 5.x through 5.0 Update 12 and 6.x through 6 Update 2, allows remote attackers to execute arbitrary programs, or read or modify arbitrary files, via applets that grant privileges to themselves. Impact CVSS Severity (version 2.0): CVSS v2 Base score: 10.0 (High) (AV:N/AC:L/Au:N/C:C/I:C/A:C) (legend) Impact Subscore: 10.0 Exploitability Subscore: 10.0
Bug#462129: intro/organization: Randall Donald still listed as FTP assistant
Package: www.debian.org Severity: normal Randall Donald resigned from the archive maintainance team in December, but is still listed as an FTP assistant on http://www.us.debian.org/intro/organization.en.html http://www.khensu.org/index.php?itemid=203 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460838: Please don't ship rules/base in source
Package: xkb-data Version: 1.1~cvs.20080104.1-1 Severity: wishlist I don't really know how rules/base works, but it seems to be autogenerated and possible not to ship it in the source. I see that even upstream tarballs contain it, but maybe the Debian patch could just remove it. The reason I ask this is that having this file seems to cause problems when trying to modify rules. Apparently if I build the package, then edit the source code and finally build and retry cleaning, cleaning fails because rules/base is updated so unpatching fails: Le patch add_void_definition_pl-324647.diff ne se retire pas proprement (rafraichissez le, ou forcez avec -f) --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.ift.ulaval.ca 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed ===-+-=== | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407598: Test result
Le January 8, 2008 01:29:55 pm Raúl Sánchez Siles, vous avez écrit : Hello Philippe: El Lunes, 7 de Enero de 2008, Philippe Cloutier escribió: Raul asked me via IRC to check whether ~/.kde/share/config/kmixrc was regenerated if I removed it while running KDE, removed /usr/share/autostart/restore_kmix_volumes.desktop then logged out and relogged in. It was regenerated with good values. I think I didn't explain myself properly on IRC, you did almost the same I told you but not exactly the same ;) I'll try to do a summary of what we talked about: First of all I think we agreed that what you were complaining at, what you consider a bug, is that kmix changes volume settings on KDE start. As you know, kmix has an option in Preferences-Configure KMix... name Restore settings on startup (translated from Spanish). By default this option is enabled, what you consider a bug that you have explained along this bug report. I think a good solution for you would be disabling this option by default. Debian could only solve this bug itself if it were the kmix package configuration the one that has enable that setting by default and hence the test I told you to do was conceived for that purpose. The setting in this matter is named as startkdeRestore in the kmix configuration file ~/.kde/share/config/kmixrc and if you pay attention to this file it will have a value of true. We will try to default this to false. Looking at the Debian kmix package, I saw that it was including a file, which should be located at /usr/share/autostart/restore_kmix_volumes.desktop that you could inspect yourself. This file includes a line like this: X-KDE-autostart-condition=kmixrc::startkdeRestore:true I think what this line is doing is making kmix to enable that option, which you don't want, but I wasn't sure, neither I am. :) It's used as a condition to perform the autostart action. Thus i ask you for this test: 1- Move that file(/usr/share/autostart/restore_kmix_volumes.desktop) into some other place, e.g. your home. You will need to be root. 2- Log out from kde (as regular user) making sure that kmix will start automatically on next logon 3- Login as your regular user into a text console(not KDE) and move the kmix configuration file(~/.kde/share/config/kmixrc) to elsewhere, e.g. your home dir. 4- Now log into kde as your regular user and go to preferences to checkout if that option is still enabled. It's still enabled. As it's obvious now only 2 things can happen :). If it didn't work, we'll have to go on investigating. If it worked, then we could toast with champagne, but being so expensive we will take a beer from the fridge :P Now seriously, the .desktop file is provided upstream, so the regular way would be to ask them to consider your opinion and change the file accordingly. I will try to poll them, I don't know what they will think. It may not be desirable upstream. I have no idea how systems which don't use ALSA save mixer levels. It should be safe to change in Debian which mostly uses Linux, but I guess it would be better to do something upstream depending on the platform on which kmix runs. The thing is that being kde3 at this mature stage, you have to know that they are reluctant to made important modifications. Alternatively a fix could be provided by Debian if anyone submit a patch and Debian packagers agree to apply it. The smart way would be asking them first after knowing the complexity of such a change. For simply changing the default, I think it just needs to be changed in kmix.cpp.
Bug#407598: Test result
Raul asked me via IRC to check whether ~/.kde/share/config/kmixrc was regenerated if I removed it while running KDE, removed /usr/share/autostart/restore_kmix_volumes.desktop then logged out and relogged in. It was regenerated with good values. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459257: lsb-release reports testing/unstable mix as unstable
Package: lsb-release Version: 3.1-24 Severity: minor lsb-release outputs No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux unstable (sid) Release:unstable Codename: sid on a testing/unstable mix (with only 2 packages from unstable). --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.ift.ulaval.ca --- Package information. --- Depends (Version) | Installed ===-+-=== python | 2.4.4-6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407598: One more opinion.
Le January 4, 2008 09:33:45 pm Raúl Sánchez Siles, vous avez écrit : Hello Filipus: IMHO, I think you are mixing different concepts. One thing is system wide volume level which are stored on a system wide basis, previosluy with alsa-utils init script ( no longer present) Since when?
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Le December 28, 2007 04:45:39 am Franklin PIAT, vous avez écrit : Hi Philippe, On Thu, 2007-12-27 at 23:27 -0500, Philippe Cloutier wrote: Le December 27, 2007 06:36:31 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 04:39:34 pm Luk Claes, vous avez écrit : [..] Ok, check the description of the apt package: http://packages.debian.org/sid/apt Advanced front-end for dpkg!! Yes, it's not clear. I opened #458029 about that. And does aptitude depends on the apt package? No! Depends on libapt! Which is not apt. It doesn't directly depend on apt, but it does effectively depend on it. I've read with interest this thread (as a reader of debian-www ml). It would be nice to have a Wiki page explaining clearly what is APT (architecture, library, tool...?), and it's accepted meanings. This page could also have some recommended usages and sample phrasing, etc... which could help RM and other writers. Could you contribute such page on wiki.d.o as you seem knowledgeable on this matter. I'm not very knowledgeable about APT. I never looked at the code. Also, there are already two more prioritary items on my todo list for a long time: restarting to maintain Wikipedia's APT article and clearing wiki.d.o's licensing situation. Don't expect an APT article on wiki.d.o from me too soon :S
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Le December 27, 2007 03:12:22 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Package: www.debian.org Severity: minor As its predecessor, http://www.us.debian.org/News/2007/20071227 contains Upgrading to this revision online is usually done by pointing the aptitude (or apt) package tool (see the sources.list(5) manual page) to one of Debian's many FTP or HTTP mirrors. This can confuse readers about what apt and aptitude are, suggesting that one can use one or the other. This should probably read by pointing the Advanced Packaging Tool (APT) (see the sources.list(5) manual page) to [...]. You can use one or the other, depending on which one you prefer to use. Actually, you have to use APT, since aptitude uses APT. The problem is precisely that the announcement suggests that aptitude does not use APT, which is already a common misconception.
Bug#457994: broken links on /devel/debian-installer/ to multi-arch images
Package: www.debian.org Severity: normal The 2 links to multi-arch CD images on http://www.debian.org/devel/debian-installer/ are broken, yielding Forbidden You don't have permission to access /cdimage/daily-builds/daily/arch-latest/multi-arch/iso-cd/ on this server. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Package: www.debian.org Severity: minor As its predecessor, http://www.us.debian.org/News/2007/20071227 contains Upgrading to this revision online is usually done by pointing the aptitude (or apt) package tool (see the sources.list(5) manual page) to one of Debian's many FTP or HTTP mirrors. This can confuse readers about what apt and aptitude are, suggesting that one can use one or the other. This should probably read by pointing the Advanced Packaging Tool (APT) (see the sources.list(5) manual page) to [...]. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Le December 27, 2007 03:26:11 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:12:22 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Package: www.debian.org Severity: minor As its predecessor, http://www.us.debian.org/News/2007/20071227 contains Upgrading to this revision online is usually done by pointing the aptitude (or apt) package tool (see the sources.list(5) manual page) to one of Debian's many FTP or HTTP mirrors. This can confuse readers about what apt and aptitude are, suggesting that one can use one or the other. This should probably read by pointing the Advanced Packaging Tool (APT) (see the sources.list(5) manual page) to [...]. You can use one or the other, depending on which one you prefer to use. Actually, you have to use APT, since aptitude uses APT. The problem is precisely that the announcement suggests that aptitude does not use APT, which is already a common misconception. No, aptitude uses libapt... For an enduser he can choose whatever package manager to use, though we recommend aptitude (or apt). I guess I have not been clear enough about the problem. The announcement says this: You can use A or B. B being a library used by A, users have to use B anyway, the only choice is to use A or not. Actually, the choice is which APT front-end to use. It could also be changed to pointing your favorite package manager (such as aptitude and Synaptic) to [...] though in reality, you're pointing APT to a source, and you're only pointing your package manager to a source indirectly. The current sentence is a bit like saying that you can use Debian or Linux to replace Windows.
Bug#455283: flashplugin-nonfree in etch
Le December 19, 2007 04:28:38 pm Scott Kitterman, vous avez écrit : On Wednesday 19 December 2007 12:06, Holger Levsen wrote: Hi, I would like to know what the stable release managers plan to do regarding flashplugin-nonfree in etch. As I see it, there are three options: 1. do nothing, keep a broken package in etch 2. remove the broken package from etch 3. request another upload, as the version currently in stable-proposed updates has broken since it was uploaded (which was before r1) Additionally I would like to (officially) ask the volatile team about their opinion of including flashplugin-nonfree in volatile/contrib. As I read the requierements for volatile, the package fully fulfills them. (The package is rock stable and just an installer for (the latest) nonfree flash (from adobe) - so it does exactly what the users expect.) The new Flash is *known* to break konqueror but works as intended on FireFox, the reason for this is konqueror does not support XEmbed. For a stable distribution, I'm not sure what the best solution would be. This problem was reported against flashplugin-nonfree at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455283 What happened with this? Was it introduced in 4.0r2, the same way as in testing? I have no etch install, but I checked the changelog and the package a bit and I saw nothing mitigating this bug. There were more than 10 duplicates of the bug report requesting XEmbed support in upstream konqueror nsplugins opened in the last 2 weeks.
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Le December 27, 2007 04:39:34 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:47:40 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:26:11 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:12:22 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Package: www.debian.org Severity: minor As its predecessor, http://www.us.debian.org/News/2007/20071227 contains Upgrading to this revision online is usually done by pointing the aptitude (or apt) package tool (see the sources.list(5) manual page) to one of Debian's many FTP or HTTP mirrors. This can confuse readers about what apt and aptitude are, suggesting that one can use one or the other. This should probably read by pointing the Advanced Packaging Tool (APT) (see the sources.list(5) manual page) to [...]. You can use one or the other, depending on which one you prefer to use. Actually, you have to use APT, since aptitude uses APT. The problem is precisely that the announcement suggests that aptitude does not use APT, which is already a common misconception. No, aptitude uses libapt... For an enduser he can choose whatever package manager to use, though we recommend aptitude (or apt). I guess I have not been clear enough about the problem. The announcement says this: You can use A or B. B being a library used by A, users have to use B anyway, the only choice is to use A or not. Actually, the choice is which APT front-end to use. It could also be changed to pointing your favorite package manager (such as aptitude and Synaptic) to [...] though in reality, you're pointing APT to a source, and you're only pointing your package manager to a source indirectly. The current sentence is a bit like saying that you can use Debian or Linux to replace Windows. No, it's not, apt is a package manager, it's libapt that is a library. Quoting English Wikipedia: APT is a C++ library of functions (known as libapt) which are used by front-end programs for dealing with packages [...] As you can see, APT can be considered as libapt. apt can also be considered as the apt package, but it still contains libapt, so apt either is or contains libapt. Therefore, suggesting that one can use aptitude without using apt is misleading. Last time: For *end users* apt is a package manager. You mean a libapt front-end? If so, which one is it?
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Le December 27, 2007 03:47:40 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:26:11 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:12:22 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Package: www.debian.org Severity: minor As its predecessor, http://www.us.debian.org/News/2007/20071227 contains Upgrading to this revision online is usually done by pointing the aptitude (or apt) package tool (see the sources.list(5) manual page) to one of Debian's many FTP or HTTP mirrors. This can confuse readers about what apt and aptitude are, suggesting that one can use one or the other. This should probably read by pointing the Advanced Packaging Tool (APT) (see the sources.list(5) manual page) to [...]. You can use one or the other, depending on which one you prefer to use. Actually, you have to use APT, since aptitude uses APT. The problem is precisely that the announcement suggests that aptitude does not use APT, which is already a common misconception. No, aptitude uses libapt... For an enduser he can choose whatever package manager to use, though we recommend aptitude (or apt). I guess I have not been clear enough about the problem. The announcement says this: You can use A or B. B being a library used by A, users have to use B anyway, the only choice is to use A or not. Actually, the choice is which APT front-end to use. It could also be changed to pointing your favorite package manager (such as aptitude and Synaptic) to [...] though in reality, you're pointing APT to a source, and you're only pointing your package manager to a source indirectly. The current sentence is a bit like saying that you can use Debian or Linux to replace Windows. No, it's not, apt is a package manager, it's libapt that is a library. Quoting English Wikipedia: APT is a C++ library of functions (known as libapt) which are used by front-end programs for dealing with packages [...] As you can see, APT can be considered as libapt. apt can also be considered as the apt package, but it still contains libapt, so apt either is or contains libapt. Therefore, suggesting that one can use aptitude without using apt is misleading.
Bug#458026: Advanced Package or Packaging Tool?
Package: apt-howto, apt Severity: normal apt and apt-howto are inconsistent in their expansions of APT. apt expands it to Advanced Package Tool in apt-doc's extended description and in apt(8). apt-howto expands it to Advanced Packaging Tool in chapter 1: Here again, Debian led the way and gave birth to APT, the Advanced Packaging Tool, which has since been ported by Conectiva for use with rpm and has been adopted by some other distributions. I think packaging means it would be used for making packages, so I think that package makes more sense, but I am not a native English speaker. I can't tell which package is buggy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458029: package descriptions are unclear
Package: apt Version: 0.7.6 Severity: normal The packages descriptions are unclear, particularly about what apt contains. The short description is Advanced front-end for dpkg. The extended description contains This is Debian's next generation front-end for the dpkg package manager. It provides the apt-get utility and APT dselect method that provides a simpler, safer way to install and upgrade packages. This is OK for apt-get and other programs, but there is no mention of libapt. Nothing indicates that APT is also a back-end for APT front-ends such as aptitude and Synaptic. This is rather confusing, because the primary role of apt is and should become more and more to be a back-end for GUI package managers and other more refined console tools. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457995: new update/revision announcement pages confusing about aptitude/apt
Le December 27, 2007 06:36:31 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 04:39:34 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:47:40 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:26:11 pm Luk Claes, vous avez écrit : Philippe Cloutier wrote: Le December 27, 2007 03:12:22 pm Jose Luis Rivas Contreras, vous avez écrit : Philippe Cloutier wrote: Package: www.debian.org Severity: minor As its predecessor, http://www.us.debian.org/News/2007/20071227 contains Upgrading to this revision online is usually done by pointing the aptitude (or apt) package tool (see the sources.list(5) manual page) to one of Debian's many FTP or HTTP mirrors. This can confuse readers about what apt and aptitude are, suggesting that one can use one or the other. This should probably read by pointing the Advanced Packaging Tool (APT) (see the sources.list(5) manual page) to [...]. You can use one or the other, depending on which one you prefer to use. Actually, you have to use APT, since aptitude uses APT. The problem is precisely that the announcement suggests that aptitude does not use APT, which is already a common misconception. No, aptitude uses libapt... For an enduser he can choose whatever package manager to use, though we recommend aptitude (or apt). I guess I have not been clear enough about the problem. The announcement says this: You can use A or B. B being a library used by A, users have to use B anyway, the only choice is to use A or not. Actually, the choice is which APT front-end to use. It could also be changed to pointing your favorite package manager (such as aptitude and Synaptic) to [...] though in reality, you're pointing APT to a source, and you're only pointing your package manager to a source indirectly. The current sentence is a bit like saying that you can use Debian or Linux to replace Windows. No, it's not, apt is a package manager, it's libapt that is a library. Quoting English Wikipedia: APT is a C++ library of functions (known as libapt) which are used by front-end programs for dealing with packages [...] As you can see, APT can be considered as libapt. apt can also be considered as the apt package, but it still contains libapt, so apt either is or contains libapt. Therefore, suggesting that one can use aptitude without using apt is misleading. Last time: For *end users* apt is a package manager. You mean a libapt front-end? If so, which one is it? Ok, check the description of the apt package: http://packages.debian.org/sid/apt Advanced front-end for dpkg!! Yes, it's not clear. I opened #458029 about that. And does aptitude depends on the apt package? No! Depends on libapt! Which is not apt. It doesn't directly depend on apt, but it does effectively depend on it.
Bug#457916: apt-show-versions: unknown suite for packages with different versions in testing and unstable
Package: apt-show-versions Version: 0.11 Severity: normal In a testing/unstable mix, when a package has different versions in testing and unstable, apt-show-versions shows unknown as suite. For example, libqt4-core being at 4.3.2-1 in testing and at 4.3.3-1 in unstable, it is shown as libqt4-core/unknown uptodate 4.3.2-1 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt-show-versions depends on: ii apt 0.7.6 Advanced front-end for dpkg ii libapt-pkg-perl 0.1.21+b1 Perl interface to libapt-pkg ii perl [libstorable-perl] 5.8.8-12 Larry Wall's Practical Extraction apt-show-versions recommends no packages. -- no debconf information deb http://debian.ift.ulaval.ca/debian/ lenny main contrib non-free deb http://debian.savoirfairelinux.net/debian/ sid main contrib non-free deb-src http://debian.savoirfairelinux.net/debian/ sid main deb http://security.debian.org/ lenny/updates main contrib non-free #deb http://gulus.usherbrooke.ca/pub/distro/debian/debian-multimedia/ testing main #deb http://www.debian-multimedia.org testing main groff-base/sid uptodate 1.18.1.1-15 m4/sid uptodate 1.4.10-1 libslp1/unknown uptodate 1.2.1-6.2 libqt4-core/unknown uptodate 4.3.2-1 w32codecs 1:20071007-0.0 installed: No available version in archive libgphoto2-2/sid uptodate 2.4.0-8 libvorbis0a/sid uptodate 1.2.0.dfsg-2 xserver-xorg-input-kbd/unknown uptodate 1:1.2.0-1+1.2.1 libvorbisenc2/sid uptodate 1.2.0.dfsg-2 binutils/sid uptodate 2.18.1~cvs20071027-1 samba/unknown uptodate 3.0.28-1~lenny1 libxcursor1/sid uptodate 1:1.1.9-1 mtr-tiny/sid uptodate 0.72-2 kdesvn-kio-plugins/sid uptodate 0.14.1-1 libsdl1.2debian/unknown uptodate 1.2.11-9 adept-installer/unknown uptodate 2.1.3+b1 xserver-xorg-video-s3/unknown uptodate 1:0.5.0-2 libfribidi0/sid uptodate 0.10.7-4 libdbus-glib-1-2/sid uptodate 0.74-1 libgl1-mesa-dri/unknown uptodate 7.0.2-2 exim4-daemon-light/sid uptodate 4.68-2 libx11-6/sid uptodate 2:1.0.3-7 libavcodec1d/sid uptodate 0.cvs20070307-6 sun-java5-jre/sid uptodate 1.5.0-13-1 grep/sid uptodate 2.5.3~dfsg-3 libtasn1-3/sid uptodate 1.1-1 kde-core/sid uptodate 5:47 sgml-data/sid uptodate 2.0.3 svgalibg1/unknown uptodate 1:1.4.3-24 sysvinit-utils/sid uptodate 2.86.ds1-38.1 psfontmgr/sid uptodate 0.11.10-0.1 pcmciautils/sid uptodate 014-4 fastjar/sid uptodate 2:0.95-1 tar/sid uptodate 1.19-1 libwmf0.2-7/sid uptodate 0.2.8.4-6 libfontconfig1-dev/unknown uptodate 2.4.2-1.2 module-assistant/sid uptodate 0.10.11 xml-core/sid uptodate 0.11 libxrandr-dev/sid uptodate 2:1.2.2-1 libxau-dev/sid uptodate 1:1.0.3-2 libnss-mdns/sid uptodate 0.10-3 ttf-dejavu-extra/unknown uptodate 2.21-1 xfonts-scalable/sid uptodate 1:1.0.0-6 xserver-xorg/unknown uptodate 1:7.2-5 libxft2/sid uptodate 2.1.12-2 libasound2/sid uptodate 1.0.15-3 kivio-data/unknown uptodate 1:1.6.3-3+lenny1 libwpd8c2a/sid uptodate 0.8.13-2 libdb4.3/sid uptodate 4.3.29-11 libgsf-1-common/sid uptodate 1.14.7-2 libxmu6/sid uptodate 1:1.0.3-1 ksysguard/sid uptodate 4:3.5.8.dfsg.1-2 kaudiocreator/unknown uptodate 4:3.5.7-3 libnss3-0d/sid uptodate 3.12.0~1.9b1-2 exim4-base/sid uptodate 4.68-2 libcupsys2/sid uptodate 1.3.4-4 cupsys-driver-gutenprint/sid uptodate 5.0.1-4 debconf-i18n/sid uptodate 1.5.17 libdpkg-ruby1.8/sid uptodate 0.3.2 gcj-4.2-base/unknown uptodate 4.2.1-5 libcroco3/sid uptodate 0.6.1-1 libggzdmod6/sid uptodate 0.0.14-2 xscreensaver-gl/unknown uptodate 5.04-1 kword-data/unknown uptodate 1:1.6.3-3+lenny1 python-foomatic/sid uptodate 0.7.7 libfreetype6/sid uptodate 2.3.5-1+b1 discover1-data/sid uptodate 2.2007.08.07 udev/sid uptodate 0.114-2 libmagick9/sid uptodate 7:6.2.4.5.dfsg1-2 xscreensaver/unknown uptodate 5.04-1 dmidecode/sid uptodate 2.9-1 console-data/unknown uptodate 2:1.03-1 pppoeconf/sid uptodate 1.17 mjpegtools 1:1.8.0-0.5 installed: No available version in archive libxv1/sid uptodate 1:1.0.3-1 libaprutil1/sid uptodate 1.2.7+dfsg-2+b1 unattended-upgrades/sid uptodate 0.25.1debian1 rt2x00-source/sid uptodate 2.0.12+git20071103-3 libjline-java/sid uptodate 0.9.93-1 libthai0/sid uptodate 0.1.9-1 info/unknown uptodate 4.11.dfsg.1-2 openoffice.org-java-common/unknown uptodate 2.2.1-10 libfaad0/sid uptodate 2.6-1 cpp-4.1/sid uptodate 4.1.2-18 libslang2/unknown uptodate 2.0.7-3 whois/sid uptodate 4.7.24 libjpeg-progs/sid uptodate 6b-14 python-numeric/sid uptodate 24.2-8 enscript/sid uptodate 1.6.4-12 libxi-dev/sid uptodate 2:1.1.3-1 libimlib2/sid uptodate 1.4.0-1 libapt-pkg-perl/unknown uptodate 0.1.21+b1 shared-mime-info/sid uptodate 0.22-2 kdelibs4c2a/sid uptodate 4:3.5.8.dfsg.1-4 libgcj8-1/unknown uptodate 4.2.1-5 libpci2/sid uptodate 2:2.1.11-3 sun-java5-jdk/sid uptodate 1.5.0-13-1 rss-glx/sid uptodate 0.8.1-8 xmoto/sid uptodate
Bug#402593: Upgrade?
Le December 23, 2007 06:36:11 pm Stephen Gran, vous avez écrit : This one time, at band camp, Philippe Cloutier said: Le December 23, 2007 05:14:20 pm Stephen Gran, vous avez écrit : This one time, at band camp, Philippe Cloutier said: Now that clamav 0.9x is in testing, should this bug's severity be upgraded to grave, serious or important? I tried using klamav and it doesn't seem to work, but I have no experience with it. klamv is broken by design. klamav doesn't use published interfaces, or the actual programs. Since it wants to use it's own internal representation of the state of the programs, it needs to advance in lockstep with the clamav upstream. If it's maintainer isn't willing to do that, it should probably be removed from the archive. We don't need more software that is broken by design. If upstream klamav wants to change to use a published clamav interface rather than muck around in the internals, it will probably go easier for them, but failing that, it's up to the Debian maintainer if he wants to keep it in the archive. Heh. I see the relation between the bug and what you wrote, but this is my first time using ClamAV so I can't discuss meta bugs yet. All I can discuss is this specific bug. Feel free to open a new report about the design. My question is whether this particular incompatibility makes KlamAV unusable or is still just a normal bug. OK, I'm not bothered either way about it. If you don't think you're interested in thinking about the bug report for some reason, that's OK with me. I'm just a little confused about why you're inquiring about the appropriate severity of a bug that you don't then want to take any further interest in. Hum, I don't really understand what you wrote. My main interest is to have this specific bug marked as an RC bug if it is an RC bug. For example, if the package is unusable, the severity should be upgraded to grave, so that klamav is not released in lenny as an unusable package. I'm asking because klamav seems broken to me, but I never used it, so it would be easier for someone who already used it to determine if klamav is just partially broken but also partially usable, and set the bug's severity accordingly.
Bug#457526: linux not capitalized in extended description
Package: sg3-utils Version: 1.24-1 Severity: minor linux should be capitalized in This package includes a number of utilities to manipulate the linux sg (version 3) device driver. and other places of the extended description. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455531: KDE3 in extended description
Package: kdebase-bin-kde3 Version: 4:3.5.8.dfsg.1-2 Severity: minor The extended description contains This package contains miscellaneous programs needed by other KDE applications, particularly those in the KDE base module. They can be provided by KDE3 or KDE4. This package provides the KDE3 versions. There should be a space between KDE and its version; KDE 3 and KDE 4. BTW, maybe this can be simplified to This package contains the KDE 3 version of miscellaneous programs needed by other KDE applications, particularly those in the KDE base module. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455010: Fixed
Le December 9, 2007 05:34:03 pm Philippe Cloutier, vous avez écrit : Version: 5.0.45-4 Norbert, open/closed isn't really used anymore, now that the BTS tracks versions. If a bug is fixed in a version, it should be marked as such. You can tag the bug + stable to indicate that the bug should be fixed there. Sorry, s/stable/etch/
Bug#455066: typo Frambebuffer in short description
Package: libxineliboutput-fbfe Version: 1.0.0~rc2-8 Severity: minor The short description reads Local Frambebuffer frontend for the xineliboutput plugin. Frambebuffer should be replaced by framebuffer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455067: typo A various plugins in package description
Package: libxine1-misc-plugins Version: 1.1.8-3 Severity: minor The extended description contains It contains a various plugins you generally would expect to find on a xine installation. This should read It contains various plugins you generally would expect to find on a xine installation. (or even better, something which doesn't use you). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454162: Re: Bug#454162: libxine1-plugins: should not depend on libxine1-gnome
This bug is now about that all plugins are installed by default, dragging in too many dependencies at install/upgrade time. I have the following compromise in mind, which I first want to be commented on before I do the follwing changes: a) Let's introduce 2 meta packages: libxine1-all-plugins, which depends on all binary packages including libxine1-gnome, and another one libxine1-common-plugins, which depends on all packages except libxine1-gnome. b) Additionally, the libxine1 package gets versioned conflicts against all gnome/gtk2 related frontends in etch. I'm not sure about a) ; how would these meta packages be used? b) looks great. Thanks for caring about this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454767: Perl5 in short description
Package: libio-stringy-perl Version: 2.110-3 Severity: minor The short description contains Perl5 without a space between Perl and 5. This should read Perl 5, or maybe just Perl, since this is the short description and other versions of Perl aren't common. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452287: broken link in import's manual
Package: imagemagick Version: 7:6.2.4.5.dfsg1-2 Severity: minor import(1) contains a broken link to http://www.imagemagick.org/script/import.php --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.ift.ulaval.ca 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed ==-+-== libbz2-1.0 | 1.0.3-7 libc6 (= 2.6.1-1) | 2.6.1-1+b1 libfreetype6(= 2.3.5) | 2.3.5-1+b1 libice6 (= 1:1.0.0) | 2:1.0.4-1 libjasper1(= 1.900.1) | 1.900.1-3 libjpeg62 | 6b-14 liblcms1 (= 1.15-1) | 1.16-6 libmagick9 | 7:6.2.4.5.dfsg1-2 libpng12-0 (= 1.2.13-4) | 1.2.15~beta5-3 libsm6 | 2:1.0.3-1+b1 libtiff4 | 3.8.2-7 libx11-6 | 2:1.0.3-7 libxext6 | 1:1.0.3-2 libxml2(= 2.6.29) | 2.6.30.dfsg-2 libxt6 | 1:1.0.5-3 zlib1g (= 1:1.2.3.3.dfsg-1) | 1:1.2.3.3.dfsg-6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451576: wrong path for USB device when missing permissions on printer
Package: qink Version: 0.3.3-1 Severity: normal When there are no printers detected, qink suggests For USB printers, try chmod 666 /dev/usblpX (as root), where X is your printer's USB port number. There's a / missing between usb and lp (/dev/usb/lpX). I'm setting normal severity since I don't know how many systems have this problem. --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-k7 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.ift.ulaval.ca 500 unstable debian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed =-+-= libc6 (= 2.6.1-1) | 2.6.1-1+b1 libgcc1 (= 1:4.2.1) | 1:4.2.2-3 libinklevel4 | 0.7.2-1 libqt4-core (= 4.3.2) | 4.3.2-1 libqt4-gui (= 4.3.2) | 4.3.2-1 libstdc++6 (= 4.2.1) | 4.2.2-3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360554: disk LED blinks constantly
Le November 8, 2007 10:38:23 am Philippe Cloutier, vous avez écrit : Le November 8, 2007 06:37:42 am Michael Biebl, vous avez écrit : Hi, could you please try the following: hdparm -B 254 /dev/hdX and see if it helps. Hi Michael, it doesn't help. Thanks anyway Shame on me for trying this with my hard drive while being perfectly aware that this is a ODD issue. By some chance I looked at this bug again and realized my error now, so I tried with hdb: vinci:~# hdparm -B 254 /dev/hdb /dev/hdb: setting Advanced Power Management level to 0xfe (254) HDIO_DRIVE_CMD failed: Input/output error So it doesn't help, but maybe it reveals another problem?
Bug#360554: disk LED blinks constantly
Le November 8, 2007 06:37:42 am Michael Biebl, vous avez écrit : Hi, could you please try the following: hdparm -B 254 /dev/hdX and see if it helps. Hi Michael, it doesn't help. Thanks anyway
Bug#435386: nvidia-kernel-source: bad attempt to nest fakeroot sessions
Le October 23, 2007 02:14:36 pm Bastian Kleineidam, vous avez écrit : Hi, I just hit bug #435386, attached is a build log. As stated in my previous message, removing $(ROOT_CMD) from debian/rules fixes the nested fakeroot error. Regards, Bastian Which command triggers this problem?
Bug#447545: Fails to connect to SMB share
Package: kdebase-kio-plugins Version: 4:3.5.7.dfsg.1-1 Severity: normal If I go to smb://localhost/ as user chealer, I see two shares, as expected, one of them homes. If I click on it, konqueror displays an error popup The file or folder smb://localhost/homes does not exist. Setting the default username to chealer and the default password to my Unix password in kcmshell lanbrowser works around the problem. Expected behaviour: If the assumption is right but fails, provide an appropriate error message, or prompt for real credentials. If the assumption is wrong, prompt for real credentials before trying. A similar problem happens in nautilus. According to Stephan Kulow, this is a libsmbclient bug. --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.savoirfairelinux.net 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed ===-+-=== kdelibs4c2a (= 4:3.5.7-1) | 4:3.5.7.dfsg.1-7 libc6 (= 2.6.1-1) | 2.6.1-1+b1 libdbus-1-3 (= 1.1.1) | 1.1.1-3 libdbus-qt-1-1c2 (= 0.62.git.20060814) | 0.62.git.20060814-2 libgcc1(= 1:4.2.1) | 1:4.2.1-4 libhal-storage1 (= 0.5.9) | 0.5.9.1-6 libhal1 (= 0.5.9) | 0.5.9.1-6 libldap2 (= 2.1.17-1) | 2.1.30.dfsg-13.5 libopenexr2ldbl (= 1.2.2) | 1.2.2-4.4 libqt3-mt (= 3:3.3.7) | 3:3.3.7-9 libsasl2-2 | 2.1.22.dfsg1-14 libsmbclient (= 3.0.2a-1) | 3.0.26a-1 libstdc++6 (= 4.2.1) | 4.2.1-4 libxcursor1 ( 1.1.2) | 1:1.1.9-1 zlib1g(= 1:1.2.3.3.dfsg-1) | 1:1.2.3.3.dfsg-6 kdesktop| 4:3.5.7.dfsg.1-1 libsasl2-modules| 2.1.22.dfsg1-14 psmisc | 22.5-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447545: Fails to connect to SMB share
Le October 21, 2007 11:50:16 pm Ana Guerrero, vous avez écrit : On Sun, Oct 21, 2007 at 10:47:18PM -0400, Philippe Cloutier wrote: Package: kdebase-kio-plugins Version: 4:3.5.7.dfsg.1-1 Severity: normal If I go to smb://localhost/ as user chealer, I see two shares, as expected, one of them homes. If I click on it, konqueror displays an error popup The file or folder smb://localhost/homes does not exist. Setting the default username to chealer and the default password to my Unix password in kcmshell lanbrowser works around the problem. Expected behaviour: If the assumption is right but fails, provide an appropriate error message, or prompt for real credentials. If the assumption is wrong, prompt for real credentials before trying. A similar problem happens in nautilus. According to Stephan Kulow, this is a libsmbclient bug. Then why do not file it against libsmbclient :? Ana Mostly because I don't know libsmbclient [enough]. I'm not sure it is a libsmbclient bug, and if it is, I couldn't explain what the bug is nor provide a testcase. Second, other users are more likely to look for a bug report against kdebase-kio-plugins than libsmbclient. Ideally, someone would check how kio-smb uses libsmbclient, open a new report if appropriate, and mark this one as blocked.
Bug#445649: Support and display Homepage field
Package: adept-manager Version: 2.1.3+b1 Severity: wishlist It would be nice if Adept Manager could display the Homepage field, like in apt-cache show ikiwiki for example. This will be linked from http://wiki.debian.org/DpkgHomepageFieldTransition -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445567: any otherthird-party plugins in extended description
Package: libgimp2.0 Version: 2.4.0~rc3-1 Severity: minor The extended description ends with It has been split off from the main gimp package in order to facilitate easy development for packages that use libgimp, like SANE, the Scanner Access package for GIMP, as well as any other third-party plugins. plugins should be singular. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445568: doesn't support double quote () in summary when calling KMail
Package: reportbug-ng Version: 0.2007.08.20 Severity: minor If a summary contains a double quote (), KMail doesn't launch when clicking Ok. --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.savoirfairelinux.net 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed =-+-=== python| 2.4.4-6 python-central (= 0.5.8) | 0.5.15 python-qt3| 3.17.3-3 python-soappy | 0.12.0-2 xdg-utils | 1.0.1-2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445569: KMail incorrectly capitalized
Package: reportbug-ng Version: 0.2007.08.20 Severity: minor Kmail should be capitalized as KMail. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445343: please use 6ux version format rather than 6-0x
Package: sun-java6 Version: 6-03-2 Severity: wishlist Please use 6ux as version format rather than 6-0x, for example 6u3 rather than 6-03. This would be more clear for me. I do not know Java and am sorry if there is a reason behind the current format, in which case feel free to close this report. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397753: Reproduced
It seems this doesn't happen only in the case described by Ritesh, but also in the simple case of upgrading a.1 to a.2 where a.2 a RC bug in a was introduced in version 2. This happened to me on 2 machines today when upgrading ucf from 3.001 to 3.003. Could the severity be upgraded to serious? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444492: GTK not capitalized in extended description
Package: libgtkmm2.4-1-c2a Version: 1:2.10.10-0.2 Severity: minor gtk is not fully capitalized in the extended description. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444233: gimp.desktop's Name contains description (menu item)
Package: gimp Version: 2.2.17-1 Severity: minor gimp.desktop contains Name=GIMP Image Editor. Image Editor is simply repeated in the GenericName. This results in the rather awkward GIMP Image Editor - Éditeur d'images in French using the default Name - Description. In English, this should be GIMP Image Editor - Image Editor. The name should be changed to GIMP.
Bug#444042: offers to upgrade to current version
Package: ksudoku Version: 0.4-1.1 Severity: normal ksudoku 0.4 offers to upgrade from 0.3 to 0.4: Your program version is 0.3, the latest version is 풿4풿Ҏ�� [EMAIL PROTECTED] �. Do you want to update? --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-486 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.savoirfairelinux.net 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed ===-+- kdelibs4c2a (= 4:3.5.6-1) | 4:3.5.7.dfsg.1-7 libc6(= 2.5-5) | 2.6.1-1+b1 libgcc1 (= 1:4.2-20070516) | 1:4.2.1-4 libgl1-mesa-glx | 7.0.1-2 OR libgl1 | libglu1-mesa| 7.0.1-2 OR libglu1 | libqt3-mt (= 3:3.3.7) | 3:3.3.7-8 libstdc++6(= 4.2-20070516) | 4.2.1-4
Bug#443643: considers some official mirrors as third-party sources
Package: software-properties-kde Version: 0.60.debian-1 Severity: important On this machine, 2 official sources are listed as sources of third-party software: deb http://security.debian.org/ lenny/updates main contrib non-free deb http://debian.savoirfairelinux.net/debian/ lenny main contrib non-free On my other machine, also a lenny/sid mix, all sources are considered as third-party. --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-486 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.savoirfairelinux.net 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed =-+-=== python (= 2.4) | 2.4.4-6 python-support (= 0.2) | 0.6.4 python| 2.4.4-6 python-qt4| 4.3-5 python-software-properties| 0.60.debian-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443418: extended description and README.Debian refer to old FUSE status
Package: ntfs-3g Version: 1:1.710-2 Severity: minor The extended description contains ntfs-3g is based on FUSE (userspace filesystem framework for Linux), thus you will have to prepare fuse kernel module to be able to use it. Similarly, README.Debian contains 1. Load fuse kernel module and add them to /etc/modules : modprobe fuse echo fuse /etc/modules These must refer to previous issue with fuse. Currently everything seems automagical. BTW, README.Debian's content is quite similar to the last part of the upstream's README content. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428561: severity of 428561 is serious
# Automatically generated email from bts, devscripts version 2.10.7 # not endorsing serious severity, just downgrading severity 428561 serious -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442901: Built for obsolete Linux images
Package: nvidia-graphics-legacy-71xx-modules-i386 Version: 1.0.7185+1 Severity: grave 2.6.18-4 is obsolete, replaced by 2.6.21-2 in testing and 2.6.22-2 in unstable. These packages are no more usable in testing and unstable, if they ever have been. They should be updated or removed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442902: Built for obsolete Linux images
Package: nvidia-graphics-legacy-71xx-modules-amd64 Version: 1.0.7185+1 Severity: grave 2.6.18-4 is obsolete, replaced by 2.6.21-2 in testing and 2.6.22-2 in unstable. These packages are no more usable in testing and unstable, if they ever have been. They should be updated or removed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442942: clean fails
Package: xkb-data Version: 1.0~cvs.20070916-1 Severity: normal clean fails producing the following log: /usr/share/quilt/pop: line 134: [: too many arguments Patch resync_rules_base.diff does not remove cleanly (refresh it or enforce with -f) --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-486 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.savoirfairelinux.net 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed ===-+-=== | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442948: Page Up/Down switches levels rather than zooming in/out
Package: xmoto Version: 0.3.3-1 Severity: normal Contrary to the behaviour shown in the options and previous versions, Page Up/Down now circulates between levels rather than zooming in/out. --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-486 Debian Release: lenny/sid 990 testing security.debian.org 990 testing debian.savoirfairelinux.net 500 unstabledebian.savoirfairelinux.net --- Package information. --- Depends (Version) | Installed =-+-== libbz2-1.0| 1.0.3-7 libc6 (= 2.6-1) | 2.6.1-1+b1 libcurl3-gnutls (= 7.16.2-1) | 7.16.4-2 libgcc1 (= 1:4.2-20070516) | 1:4.2.1-4 libgl1-mesa-glx | 7.0.1-1 OR libgl1| libglu1-mesa | 7.0.1-1 OR libglu1 | libjpeg62 | 6b-14 liblua50 (= 5.0.3) | 5.0.3-3 liblualib50(= 5.0.3) | 5.0.3-3 libode0debian1 (= 1:0.8.dfsg-3) | 1:0.8.dfsg-3 libpng12-0 (= 1.2.13-4) | 1.2.15~beta5-2 libsdl-mixer1.2(= 1.2.6) | 1.2.6-3 libsdl-ttf2.0-0 | 2.0.9-1 libsdl1.2debian (= 1.2.10-1) | 1.2.11-9 libsqlite3-0 (= 3.4.2) | 3.4.2-1 libstdc++6 (= 4.2-20070516) | 4.2.1-4 zlib1g (= 1:1.2.3.3.dfsg-1) | 1:1.2.3.3.dfsg-5 xmoto-data(= 0.3.3-1) | 0.3.3-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442445: includes non-free manpages
Package: gcc-4.2 Version: 4.2.1-4 Severity: serious gcc-4.2 includes gcc-4.2's manpage, which is a non-free document under the GFDL with invariant sections. gcov's manpage has the same issue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442784: please do not recommend maint-guide-fr
Package: doc-debian-fr Version: 3.1.3.1 Severity: wishlist doc-debian-fr is a document for end users, but it recommends the Debian New Maintainers' Guide, which is for developers. Few users are developers, so please remove the recommendation on the Debian New Maintainers' Guide as in other doc-debian* packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442805: please do not recommend perl-doc
Package: perl Version: 5.8.8-7 Severity: wishlist perl is found on almost all systems, but perl-doc is only found in 13.41% of installs, despite it being currently recommended by perl. This speaks for itself; systems with perl and without perl-doc are certainly not unusual. perl-doc was previously a suggestion, but was upgraded to a recommendation in 5.8.4-7: * Upgrade suggestion on perl-doc to recommends now that dselect is less pedantic about the latter. perl-doc is a 7 MB download, so it would be important not to install it on default installs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442805: please do not recommend perl-doc
On September 16, 2007 09:57:24 pm Brendan O'Dea wrote: There is a bit of history with the perl-doc package... The perl community has been at times very critical of the fact that the docs are split out *at all*. The argument is that the docs are an integral part of the perl distribution. Are you sure the criticism was about perl-doc being split out, or about perl not warranting that Perl documentation is installed? I guess criticism was that perl should ensure that documentation is available. This is a valid point. If you think it's worth considering, perl could be renamed to something, say perl-bin, and a new perl metapackage could created, depending on perl-bin and perl-doc. I am not convinced that this is worth adding a metapackage though. For example, Apache suggests the documentation and this is fine for me. perl-doc is a 7 MB download, so it would be important not to install it on default installs. If you don't want it, don't install it. I can avoid installing it, but not when doing a default install. Unless you think the package should be installed by default, you're the only one that can avoid that...except perhaps tasksel maintainers by delaying recommends consideration even more :/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442814: please do not recommend jackd
Package: libjack0 Version: 0.103.0-6 Severity: wishlist Several applications that support JACK depend on libjack. Thus, libjack is installed on over 56% of systems. Under 12% of systems use JACK. This means that under 1 of 5 systems where libjack is installed want JACK. However, libjack0 recommends jackd. Please downgrade libjack0's dependency on jackd to a suggestion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442410: recommends developers-reference-fr
Package: doc-debian-fr Version: 3.1.3.1 Severity: minor doc-debian-fr is a document for end users, but it recommends the Debian Developer's Reference, which is for developers. It's not unusual for a user to not be a developer, so the Developer's Reference shouldn't be recommended, as in other doc-debian* packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442417: recommends imagemagick
Package: konq-plugins Version: 4:3.5.7-2 Severity: normal konq-plugins recommends imagemagick, presumably for the image gallery creation plugin. It must be a good idea that imagemagick is suggested, but it shouldn't be recommended since image gallery creation is not the only plugin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442421: recommends gksu (without alternatives)
Package: synaptic Version: 0.60+b1 Severity: normal synaptic recommends gksu, but KDE users should prefer kdesu (in kdebase-bin) (and Synaptic used a lot with KDE). I suggest to change the recommandation to gksu|kdebase-bin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442422: recommends deborphan
Package: synaptic Version: 0.60+b1 Severity: minor I think it was never unusual to use synaptic without deborphan, but with APT 0.7 it became even less usual. I don't know if Synaptic still does something special with deborphan; if so, deborphan could be downgraded to a suggestion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442432: recommends gdb
Package: kdebase-bin Version: 4:3.5.7-3 Severity: minor kdebase-bin recommends gdb, but it is not unusual that kdebase-bin is used without gdb. The relation should probably be downgraded to a suggestion, although I have no idea what gdb is useful for. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380685: Forwarded
forwarded 380685 http://bugs.kde.org/show_bug.cgi?id=149903 retitle kio_tar: impossible to open symlinks thanks I reproduce this with 3.5.7. I don't see how the commit Andreas pointed could have caused such a regression, since it restricts the cases where KTar will detect an invalid file, rather than invalidating files previously considered as valid. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442442: recommends kamera
Package: kdebase-kio-plugins Version: 4:3.5.7-3 Severity: minor kdebase-kio-plugins recommends gdb, but it is not unusual that kdebase-kio-plugins is used without kamera. The relation should probably be downgraded to a suggestion, although I'm not sure how kamera improves kdebase-kio-plugins. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442220: Typo simplay in epoll
Package: manpages Version: 2.63-1 Severity: minor In By contrast, when used as a level-triggered interface, epoll is simplay a faster poll(2), and can be used wherever the latter is used since it shares the same semantics., simplay should read simply. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442302: README.Debian.gz refers to php4-gd2 rather than php5-gd
Package: mediawiki1.10 Version: 1.10.1-2 Severity: minor README.Debian.gz contains - Image thumbnailing : Install 'php4-gd2' or 'imagemagick' to use this feature. php4-gd2 should be updated to php5-gd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442311: README.Debian.gz assumes /mediawiki/ is an alias to /var/lib/mediawiki1.10
Package: mediawiki1.10 Version: 1.10.1-2 Severity: normal README.Debian.gz contains The configuration uses an easy web-based system ; just go to this URL : http://www.myserver.org/mediawiki/config/index.php This won't work unless /mediawiki/ is an alias to /var/lib/mediawiki1.10. By default, Alias /mediawiki /var/lib/mediawiki1.10 is commented in mediawiki1.10.conf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441419: originaly in extended description
Package: supertuxkart Version: 0.3-1 Severity: minor The extended description starts with SuperTuxKart is an enhanced version of TuxKart. The kart racing game, originaly done by Steve Baker, featuring Tux and a bunch of his friends. originaly should read originally. Also, the syntax is incorrect. In an apposition, a comma should be used after TuxKart rather than a period. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440971: Wrong French translation for Mark additional required changes?
Package: synaptic Version: 0.60+b1 Severity: minor Tags: l10n patch Mark additional required changes? is currently translated to Prévoir d'effectuer d'autres changements?, which can be translated to Plan to do other changes?. A correct translation would be Sélectionner les changements additionnels nécessaires?. --- fr_1.po 2007-06-10 14:11:06.0 -0400 +++ fr.po 2007-09-05 16:14:11.0 -0400 @@ -2519,8 +2519,7 @@ span weight=\bold\ size=\larger\Mark additional required changes?/ span msgstr -span weight=\bold\ size=\large\Prévoir d'effectuer d'autres -changements ?/span +span weight=\bold\ size=\large\Sélectionner les changements additionnels nécessaires?/span #: ../gtk/window_changes.glade.h:2 msgid
Bug#440576: packages.debian.org: You reached this site over an old URL. when searching for contents/file
Package: www.debian.org Severity: minor With the latest pdo, URL-s changed, which introduces among others a regression in pdo itself. For example, searching for test points to http://packages.debian.org/cgi-bin/search_contents.pl?word=testsearchmode=searchfilescase=insensitiveversion=stablearch=i386 which starts with You reached this site over an old URL. Depending on the exact parameters your search might work or not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439307: please suggest kexi-mdb-plugin
Package: kexi Version: 1:1.6.3-1lenny1 Severity: wishlist Please make kexi suggest kexi-mdb-plugin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439110: extended description should refer to squashfs-tools rather than squashfs
Package: squashfs-source Version: 1:3.2r2-3 Severity: minor The extended description contains The squashfs package is also required in order to make use of these modules. squashfs should read squashfs-tools there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438787: /devel/debian-installer/ links to outdated weekly and daily images
Package: www.debian.org Severity: normal http://www.debian.org/devel/debian-installer/ links to http://cdimage.debian.org/cdimage/weekly-builds/ on current weekly snapshot of Debian testing, but these images aren't current currently, dating from May. There are current netinst and businesscard images for testing which are linked from the same page - the problem is that the outdated images appear first. Similarly, daily multi-arch CD images are not current. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438705: /CD/http-ftp/ links to old Official CD/DVD images of the testing distribution
Package: cdimage.debian.org Severity: normal http://www.debian.org/CD/http-ftp/ links to http://cdimage.debian.org/cdimage/weekly-builds/ on Official CD/DVD images of the testing distribution (regenerated weekly), but these images aren't generated weekly currently, and date from May. There are current netinst and businesscard images for testing which are linked from the same page - the problem is that the outdated images appear first. I suggest to comment this line for now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438496: unix not capitalized in short description
Package: ed Version: 0.2-20 Severity: minor In the short description, unix should be capitalized. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438588: Short description indicates that gimp2.0-quiteinsane is just for GIMP 2.0
Package: gimp2.0-quiteinsane Version: 0.3-8 Severity: minor gimp2.0-quiteinsane's short description A Qt based SANE plugin for GIMP 2.0 indicates that it is not for GIMP 2.2, but it actually works fine with it. Please remove the version from the description. Renaming to gimp-quiteinsane could also be a good thing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437956: please mention that akregator supports Atom in description
Package: akregator Version: 4:3.5.5.dfsg.1-6 Severity: normal Although akregator supports Atom feeds, the short description suggests that it doesn't (RSS feed aggregator for KDE). Changing that to KDE feed aggregator or KDE RSS and Atom feed aggregator should solve this issue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437968: writing errors in description
Package: jd Version: 1:1.9.5-070630-1 Severity: normal In the short description, gtk+ should be capitalized (GTK+). In the extended description, uses should read use in 2ch-style Bulletin board System that uses. Rather than It supports you to read/write articles in such BBS., the description should contain It allows you to read/write articles in such BBS. (or perhaps helps). Rather than 2ch-style BBSs are [...] and so on. please use 2ch-style BBS include [...]. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436009: communciation in extended description
Package: libice-dev Version: 1:1.0.3-2 Severity: minor The extended description contains This package provides the main interface to the X11 Inter-Client Exchange library, which allows for communciation of data between X clients. There is a typo in communciation, which should read communication. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]