Bug#770789: Reopen
reopen 770789 thanks Hi Don, On 2014-12-15 16:17, Don Armstrong wrote: user tech-c...@packages.debian.org usertag 770789 published On Sat, 13 Dec 2014, Don Armstrong wrote: I will announce the decision on -announce shortly. Announced; closing this bug. The CTTE decision announced is about df including "i" in the "units" output when asked for IEC output, an issue only related to the decision which needs to be made. As the example shows, the issue will present even when binary prefixes were not requested. While the results of your poll suggest the CTTE is willing to accept ambiguity and inconsistency, it does not condone usage of invalid units. Should you feel the need to publicize the results of future votes on mailing lists, thanks for avoiding debian-devel-announce, which is meant for important announcements. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772686: [dolibarr] "an [...] free software" in extended description
Package: dolibarr Version: 3.5.5+dfsg1-1 Severity: minor The extended description starts with: Dolibarr ERP & CRM is an easy to use open source/free software for small and medium companies, foundations or freelances. "a [...] free software" is not a proper noun phrase. Unlike "logiciel", in English, software is uncountable. By the way, all software in Debian is open source, so this is superfluous. I suggest: Dolibarr is an easy to use ERP and CRM for small and medium companies, foundations or freelances. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772073: [linux] "The Linux kernel x" in extended description
Source: linux Version: 3.16.7-2 Severity: minor This issue affects several (I presume all) extended descriptions of stock kernel packages. I will use linux-image-3.16.0-4-amd64 as an example. The description starts with: The Linux kernel 3.16 and modules for use on PCs with AMD64, Intel 64 or VIA Nano processors. "The Linux kernel 3.16" should be replaced with something like: 1. "The Linux kernel (version 3.16)" 2. "Version 3.16 of the Linux kernel" 3. "Version 3.16 of Linux" 4. "Linux (version 3.16)" 5. Simply "Linux 3.16" I would recommend either 1, 4 or 5. By the way, this sentence is misleading. The x86-64 flavor can be used on quite a broad range of hardware, including servers. -- Filipus Klutiero http://www.philippecloutier.com
Bug#772066: [krdc] Incompatibility with FreeRDP (fails to connect to some RDP servers with certain options)
Package: krdc Version: 4:4.14.1-1 Severity: important I regularly connect to 2 RDP hosts. The one I use the most, a Windows 8 server, does not work anymore after upgrading xfreerdp from 1.0 to 1.1.0~git20140921.1.440916e. My connection to a Windows Server 2003 host still works. If I try the Windows 8 connection with FreeRDP "1.1", the connection never completes, causing the infamous blue screen (upstream 339490). This is a known issue caused by usage of an unreleased FreeRDP version tracked in upstream's ticket 341284. New versions do not offer the same command-line interface. The interface isn't completely different. It appears to be possible to connect to any RDP server, but the right options need to be set. Also, it seems the target is also a variable - for some reason, my Windows Server 2003 appears to support any configuration I request, unlike my Windows 8 server. I see a few options: 1. Revert FreeRDP to 1.0 and wait until dependants support the new interface. 2. Make krdc compatible with the new interface. Upstream has a patch to support the new interface, but it doesn't support the old interface at the same time. Either we develop a new patch, or we apply the existing patch and make krdc conflict with FreeRDP 1.0 and earlier. FreeRDP should perhaps conflict with current krdc too. --- System information. --- Architecture: i386 Kernel: Linux 3.16-3-amd64 Debian Release: jessie/sid 990 testing ftp3.nrc.ca 500 unstable ftp3.nrc.ca 1 experimental ftp3.nrc.ca --- Package information. --- Depends (Version) | Installed ===-+-= kde-runtime (>> 4:4.10) | 4:4.14.2-1 libc6 (>= 2.1.3) | 2.19-13 libkcmutils4 (>= 4:4.11) | 4:4.14.2-3 libkdecore5 (>= 4:4.11) | 4:4.14.2-3 libkdeui5 (>= 4:4.11) | 4:4.14.2-3 libkdnssd4 (>= 4:4.11) | 4:4.14.2-3 libkio5 (>= 4:4.11) | 4:4.14.2-3 libknotifyconfig4 (>= 4:4.11) | 4:4.14.2-3 libqt4-dbus (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 libqt4-network (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 libqt4-xml (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 libqtcore4 (>= 4:4.8.4) | 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 libqtgui4 (>= 4:4.8.0) | 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 libstdc++6 (>= 4.1.1) | 4.9.1-19 libtelepathy-qt4-2 (>= 0.9.1) | 0.9.4+dfsg-3 libvncclient0 (>= 0.9.9) | 0.9.9+dfsg-6+b2 Recommends (Version) | Installed ==-+-=== rdesktop | freerdp-x11 (>= 1.0.2) | 1.1.0~git20140921.1.440916e+dfsg1-2+b1 Suggests (Version) | Installed =======-+-=== khelpcenter4 | 4:4.14.2-1 krfb | 4:4.14.2-1 -- Filipus Klutiero http://www.philippecloutier.com
Bug#771814: [xul-ext-video-without-flash] "flash" not capitalized in descriptions
Package: xul-ext-video-without-flash Version: 1.5.0-1 Severity: minor The extended description starts with: Fetch video source of flash based media and play the video directly with Iceweasel (a.k.a. Firefox), without the use of the flash plug-in. "Flash" is a proper noun and should be capitalized. Note that there are several plug-ins for Flash. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770789: [tech-ctte] df sizes output format
Package: tech-ctte Severity: normal X-Debbugs-Cc: 761...@bugs.debian.org As reported in #761424, the "sizes" output by df(1) are not actual sizes, due to the "units" used. The "units" used are merely unit prefixes. Moreover, df uses the same pseudo-units with different meanings. The output can therefore be misleading if one attempts to interpret it. 2 different calls seem to give different measurements for the same filesystems: chealer@debian:~$ LANG=C df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.8T 317G 1.4T 19% / udev 10M 0 10M 0% /dev tmpfs 252M 5.4M 247M 3% /run /dev/disk/by-uuid/a00f8767-e954-4b81-8035-c6bb414671cb 1.8T 317G 1.4T 19% / tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 961M 0 961M 0% /run/shm /dev/sdb2 2.2G 122M 2.0G 6% /tmp chealer@debian:~$ LANG=C df -H Filesystem Size Used Avail Use% Mounted on rootfs 2.0T 340G 1.6T 19% / udev 11M 0 11M 0% /dev tmpfs 264M 5.7M 259M 3% /run /dev/disk/by-uuid/a00f8767-e954-4b81-8035-c6bb414671cb 2.0T 340G 1.6T 19% / tmpfs 5.3M 4.1k 5.3M 1% /run/lock tmpfs 1.1G 0 1.1G 0% /run/shm /dev/sdb2 2.4G 128M 2.2G 6% /tmp chealer@debian:~$ In the first example call, JEDEC prefixes are used, while SI prefixes are used in the second. Michael Stone denies, excusing the behavior with space scarcity, documentation, and what he considers as little impact: I'm not going to deviate from upstream. [...] The space is more important (in my opinion) than the need for a constant reminder of the unit. The documentation is there for people to read the first time, after that it's just not that important. (Even for the numbers above the difference isn't really significant--the relative sizes are the consistent, and what are the odds that you need exactly 12 gigasomethings? If you did need exactly that much space, you're probably better off looking at kbytes or bytes anyway.) The space scarcity and impact arguments do not hold, and unfortunately, even the documentation does not define the pseudo-sizes currently output. -- Filipus Klutiero http://www.philippecloutier.com
Bug#770089: [iceweasel] "Keep the passion for a free and open Internet burning bright! #ChooseIndependent" on start page
Hi Carsten, On 2014-11-18 15:20, Carsten Schoenert wrote: Hello Filipus, Am 18.11.2014 um 21:04 schrieb Filipus Klutiero: But please, if you go that far, proceed via some link or something. Do not directly include big logos from private media in my default start page, without even offering me to get rid it of them. When I see this start page on the main browser of an OS made by free software advocates, I shake my head in disbelief. And we're pretending to be advocating independence... do you have taken the time and try out that "start page"? If so I would mind you haven't written such a bug report! It's simple video make by Mozilla to even explain who should own the net in these days. As I said, "I find the video cool [and] I for one don't mind seeing some Firefox promotion..." And if you don't like that, just turn it of. Just change the start page to nothing. I know how to workaround my install. The real victims are ignorant users, and our project's public image. The problematic part is at the end. The cryptic "#ChooseIndependent" and logos from private media, shown by default and in large size. I don't condemn marketing, but if we promote independence, let's not promote the opposite at the same time. There are several measures which can alleviate this besides simple removal: * only show the material once * offer to remove it * only show sharing material after the video was watched * do not show the sharing material (for example, only link to Mozilla's page) -- Filipus Klutiero http://www.philippecloutier.com
Bug#769859: [workrave] Displays 2 icons in the system tray (KDE?)
reopen 769859 retitle 769859 Applet displays a [duplicated] system tray icon rather than the applet in KDE thanks On 2014-11-17 15:39, Francois Marier wrote: On 2014-11-17 at 07:22:34, Filipus Klutiero wrote: Both are enabled, on Windows as well as on Debian. Disabling either removes an element. Does this mean they are supposed to behave differently? Ah, that's the problem then. You should just have "system tray icon" enabled if you don't want the second icon. That's how I run it. Ooh, OK, I get it. So disabling "Active applet" is indeed the right workaround for this (although disabling "Show system tray icon" would achieve the same as things stand). By default, both preferences are enabled. http://www.workrave.org/blog/2004/02/03/windows-applet-works/ shows what the applet is supposed to be. I wouldn't see the applet on Windows 8 even though it is also enabled by default because one also needs to enable its toolbar, as the screenshot shows. The applet does work on Windows 8, but there are several bugs with it, some reported upstream, some reported elsewhere, for example https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/981879 I didn't find one about KDE, but visibly, this is an upstream bug specific to KDE. It is not just a cosmetic bug, but apparently the applet being completely broken under KDE. For what it's worth, I find this applet invasive and would be fine with us disabling it by default. Francois -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769859: [workrave] Displays 2 icons in the system tray (KDE?)
Hi François, On 2014-11-17 01:25, Francois Marier wrote: Workrave has a system tray element with a sheep icon. On this install, starting Workrave always causes the appearance of 2 such elements. They would seem to represent 2 different Workrave instances, but in fact, a single process is behind both, and trying to terminate any of these apparent instances causes the disappearance of both elements. Are you sure you don't have both the "system tray icon" and the "applet" turned on? They can be turned on/off from the UI section of the preferences. Both are enabled, on Windows as well as on Debian. Disabling either removes an element. Does this mean they are supposed to behave differently? [...] -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769859: [workrave] Displays 2 icons in the system tray (KDE?)
Package: workrave Version: 1.10.4-3 Severity: normal X-Debbugs-Cc: 767...@bugs.debian.org Workrave has a system tray element with a sheep icon. On this install, starting Workrave always causes the appearance of 2 such elements. They would seem to represent 2 different Workrave instances, but in fact, a single process is behind both, and trying to terminate any of these apparent instances causes the disappearance of both elements. As it seems that interacting with any of these works, this is apparently nothing more than a "cosmetic" bug. This issue does not affect Windows. According to upstream ticket #786, Workrave has KDE-specific issues including a lack of sounds. This might be one, but this could also be a duplicate of #767739, which affects GNOME (I do not use GNOME, and the ticket is not clear enough to tell). --- System information. --- Architecture: i386 Kernel: Linux 3.16-2-amd64 Debian Release: jessie/sid 990 testing ftp3.nrc.ca 500 unstable ftp3.nrc.ca 1 experimental ftp3.nrc.ca --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769603: [rsibreak] Cannot file tickets upstream
Package: rsibreak Version: 4:0.11-3 Severity: important Tags: upstream It is not possible to report issues with RSIBreak upstream. The page opened by "Report Bug..." reads: Sorry, entering a bug into the product /rsibreak/ has been disabled. Please press *Back* and try again. Of course, Back is not even available. I'm not sure why reporting was disabled, but upstream seems quite inactive. I don't see any tracker outside KDE's Bugzilla. It looks like upstream currently has no issue tracker. -- Filipus Klutiero http://www.philippecloutier.com
Bug#769588: [libbaloowidgets4] "baloo" not capitalized in extended description
Package: libbaloowidgets4 Version: 4:4.14.0-1 Severity: minor The extended description contains: This package contains GUI widgets for baloo. "baloo" is a proper noun and should be capitalized. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769586: [liboggkate-dev] typo "off" in extended description
Package: liboggkate-dev Version: 0.4.1-4 Severity: minor The extended description contains: liboggkate provides an API for the encapsulation off kate streams into Ogg. "off" should read "of". By the way, I assume "kate" should be capitalized. -- Filipus Klutiero http://www.philippecloutier.com
Bug#769362: [kde-telepathy-data] "telepathy" not capitalized in extended description
Package: kde-telepathy-data Version: 0.8.1-3 Severity: minor The extended description contains: KDE telepathy shared data. "Telepathy" is a proper noun and should be capitalized. By the way, this sentence is incomplete, like many others from this source package's descriptions. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768166: [libpsl0] Typo in extended description
Package: libpsl0 Version: 0.5.1-1 Severity: minor The extended description contains: Libpsl allows checking domains against the Public Suffix List, It can be used to avoid privacy-leaking 'super-cookies', 'super domain' certificates, for domain highlighting purposes sorting domain lists by site and more. This should be two sentences. The first comma should be replaced with a period. By the way, I don't really understand what this library does after reading this description without getting more information, even though I am not ignorant about cookies, certificates and domains. Questions which come to mind: What is the Public Suffix List? What are 'super-cookies'? What are 'super domain'-s? What is domain highlighting? What does "sorting domain lists by site" mean? It is not necessary for the description to answer all of these, but if it's simple to answer some, this might help readers figure out what kind of service this package provides. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768118: [icedove] Errors in NEWS.Debian
Package: icedove Version: 31.2.0-1 Severity: minor NEWS.Debian.gz contains: icedove (31.2.0-1) unstable; urgency=low Mozilla implemented TLS 1.2 in NSS version 3.15.1 and Thunderbird 31.0 uses this as the default. It won't fall back to older protocol versions. This means every connection from Thunderbird/Icedove to a mail server will using TLS 1.2 with no fall back if you have configured TLS/SSL or STARTTLS for your connections. Some users reported trouble by this behavior. In case you are unable to get or sent any mails anymore from or to your mail server please ensure that your email provider is fully supporting TLS 1.2 if possible. There were reports that this causes problems with some providers (Bug #761245). This is usually indicated by: "connection to SMTP server was lost in the middle of the transaction." For information on how to fix that check README.Debian. -- Carsten Schoenert Wed, 15 Oct 2014 18:38:00 +0200 "will using" is incorrect. This could read "will use". "Some users reported trouble by this behavior." should surely read "Some users reported trouble *with* this behavior." "to get or sent" should read "to get or send". In the last paragraph, a comma is missing after "that". -- Filipus Klutiero http://www.philippecloutier.com
Bug#767679: [libsysfs2] "in Linux kernel" in extended description
Package: libsysfs2 Version: 2.1.0+repack-4 Severity: minor The extended description starts with: Sysfs is a virtual file system in Linux kernel 2.5+ that provides a tree of system devices. "Linux kernel" should read either "the Linux kernel", or simply "Linux". By the way, the "description" does not describe the package's contents. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766936: [pkg-otr-team] Bug#766936: [libotr5] Extended description: "Deniability" is not a feature per se
On 2014-10-29 05:49, Ian Goldberg wrote: On Tue, Oct 28, 2014 at 08:56:07PM -0400, Filipus Klutiero wrote: I am not convinced this is a good thing, but for sure the current phrasing is incorrect. According to the technical paper, OTR would merely send the key to the other participant, so only him could forge messages, unless someone captured the message. So the only person who can forge messages after the conversation is the other participant. Since he could already forge messages, that measure does not increase deniability in normal circumstances. No, that's not quite right; OTR sends the authentication (MAC) key *in the clear* so that anyone capturing the traffic on the wire can subsequently modify transcripts however they like. That's also what I was saying. It is not encrypted, but it has no effect except in cases where the communication is captured. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766936: [pkg-otr-team] Bug#766936: [libotr5] Extended description: "Deniability" is not a feature per se
Hi Harlan, On 2014-10-26 23:08, Harlan Lieberman-Berg wrote: On Sun, 2014-10-26 at 21:22 -0400, Filipus Klutiero wrote: Rather than advertising 2 independant items, these could be merged in a "Deniable authentication" item which would contain both sublists. One reason why I think "deniability" is important as a separate feature is that it is differentiating in the face of other, similar kinds of programs. Most encryption systems are not deniable; in fact, many systems are not deniable /by design/. This message, for example, is PGP signed and is not deniable at all. Anyone who gets a copy of the message can verify that I, or someone with control over my private key, composed and sent this message. The Pidgin-Encryption plugin similarly doesn't have deniability built into its threat model at all. I agree it is an important feature... In that context, I think it might be deserving of being listed as its own feature. I didn't mean it doesn't "deserve" being listed on its own. What I meant is that I consider it a subfeature of authentication, so I find it confusing to see it independent from authentication. Grouping would make it more understandable. By the way, I do not understand what "Anyone can forge messages after a conversation to make them look like they came from you." means. It's part of the deniability feature. While it's very difficult for an attacker to forge a signature while the conversation is going on, the ephemeral key used for signatures is publicly revealed after the conversation is over. That means that you could forge any messages, and theoretically, provide some defense against someone who /did/ manage to compromise the communication being able to prove that you said what you said. Thank you, I now understand what this sentence is about. I am not convinced this is a good thing, but for sure the current phrasing is incorrect. According to the technical paper, OTR would merely send the key to the other participant, so only him could forge messages, unless someone captured the message. So the only person who can forge messages after the conversation is the other participant. Since he could already forge messages, that measure does not increase deniability in normal circumstances. It is also unclear what "after a conversation" means. When does a conversation end? In any case, the technical paper doesn't say keys are revealed after a conversation. It is confusing to write that "However, _during_ a conversation, your correspondent is assured the messages they see are authentic and unmodified." While it is true, your correspondent obviously does not lose that assurance after a conversation. "Deniable authentication" is IMO contradictory. A better term might be "private authentication", for example, meaning you privately authenticate to your correspondent. In any case, we shouldn't simply name the property, we should describe what it provides. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766936: [libotr5] Extended description: "Deniability" is not a feature per se
Package: libotr5 Version: 4.1.0-1 Severity: minor The extended description contains: OTR allows you to have private conversations over IM by providing: [...] - Authentication - You are assured the correspondent is who you think it is. - Deniability - The messages you send do _not_ have digital signatures that are checkable by a third party. Anyone can forge messages after a conversation to make them look like they came from you. However, _during_ a conversation, your correspondent is assured the messages they see are authentic and unmodified. So-called "deniability" is not a feature per se, unless authentication is taken for granted, which is clearly not the case here. Rather than advertising 2 independant items, these could be merged in a "Deniable authentication" item which would contain both sublists. By the way, I do not understand what "Anyone can forge messages after a conversation to make them look like they came from you." means. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766935: [www.debian.org] packages.debian.org: missing some extended descriptions (unstable, experimental)
Package: www.debian.org Severity: normal packages.debian.org has been missing some extended descriptions in experimental, at least for many months. It seems this issue recently started to affect unstable too. Packages which did not change their extended description recently are not affected, but at least those which changed in the 4 previous days seem to be affected. Compare https://packages.debian.org/en/sid/apache2-utils (apache2-utils having had its extended description fixed in 2.4.10-6) with https://packages.debian.org/en/sid/apache2-bin 2.4.10-6 was uploaded 2014-10-21. Another example is https://packages.debian.org/en/sid/libotr5 (4.1.0-1 uploaded 2014-10-21). I never noticed this problem in short descriptions. There is no error message - it simply looks as if the extended description was empty. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764670: Re: Bug#764670: [libturbojpeg1] Please clarify description
Hi Ondřej, On 2014-10-14 10:48, Ondřej Surý wrote: Version: 1:1.3.1-5 The package description has been reviewed by debian-l10n team and the changes has been applied in 1:1.3.1-5. Cheers, Well, that's good, but this isn't really a l10n issue, and indeed, the problematic version reported is ulterior. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765657: [debian-reference-en] "This makes its documentation difficult to be [...]" in section 1
severity 765657 minor reopen 765657 thanks On 2014-10-17 09:58, Osamu Aoki wrote: control: tags 765657 - l10n control: severity 765657 wishlist control: tags 765657 + wontfix Hi, On Thu, Oct 16, 2014 at 10:53:27PM -0400, Filipus Klutiero wrote: Package: debian-reference-en Version: 2.55 Severity: minor Tags: l10n "l10n"? Are you doing this as English language proof reading? Strange tag. l10n is a common tag (which may indeed apply to English): https://www.debian.org/Bugs/Developer#tags Section 1 contains: The Debian system itself is a moving target. This makes its documentation difficult to be current and correct. Although the current unstable version of the Debian system was used as the basis for writing this, some contents may be already outdated by the time you read this. "to be" should read something like "to keep". I think both are OK and practically the same. Matter of taste. (If you wish to nitpick on style, you can find many..) Well, the current phrasing might be understandable, but a valid phrasing would be more to my taste. By the way, the version of the Debian system used as basis is not the current unstable version [anymore], and I'm not sure this paragraph is warranted. Pretty much all healthy software changes. Debian's documentation is no harder to keep updated than documentation for an equally complex project, disregarding language issues. I suggest shortening this to at most 2 sentences. Do you know this document has many translations to update, too. (They are kept in sync.) So this kind of changes are non-trivial. If the English version is the master version, then fixing it would be all the more urgent. The better the master version becomes, the easier translating will be. It is very hardwork for me ... Please do not comment like "no harder ...". Quite frankly, I was offended. I am sorry if you were offended, that should not have happened. I wrote "no harder", not "not hard". I am well aware that documenting is not easy. I was asking to change the paragraph, not necessarily to remove it entirely. I want to ensure that this paragraph is useful, and that it doesn't read as an excuse for providing a low quality document. I see 3 options: * Removal. The developer in me favors this, because the paragraph did not teach me anything. Very few projects have one release with documentation, then no further releases with functional changes. Almost all software documentation has the same challenge as the Debian Reference. Even then, readers may not realize this and it may be worth it to mention that. * A short version without going into the causes. I would suggest:"Parts of this are probably outdated." * Keep a treatment of the causes, but be clear. For example, Debian being a moving target can explain why the documentation would not be current, but how would it explain it not being *correct*? It may be warranted to keep some treatment of the problem, but readers would surely prefer to read an apology with an invitation to report issues if they notice some, than something which makes the problem sound as unavoidable. And we would probably get more feedback too. What have you done for Debian? If you can provide a patch with translation to me, I may consider ... but I think there are much higher priority things to update. systemd ... gTLD, ... minor severity is the minimal "priority" bugs can have. Even if the severity had been inflated, you would have been free to work on what you want, when you want. If you check changelog or VCS, you understand this document is pretty much single person work. Responding this is already a burden ... sigh. If you have a manpower issue, trying to get rid of tickets is definitely not going to solve it. Instead, respect the contributions you get, and try recruiting contributors so they can actually fix their issues and others, instead of being driven away. Looking at this package, it does seem like you have a major lack of manpower. If you can't fix that organically, I strongly suggest you open an RFH. On the other hand, it might be possible to realign the reference's scope with its means. If this has to stay a single-person work, perhaps some parts can be eliminated or moved out (section 11 and the one on mc, for example). If you are a native English speaker reviewing the whole text, give me a good set of real style update suggestions. I am not. Hmmm... googling your name I found: https://bugs.debian.org/501382 https://bugs.debian.org/508240 https://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=chealer%40gmail.com Maybe there was a reason for *ban*. I should not waste time on this. I am not sure what you mean. I certainly don't think "googling" my name is going to help solving this issue. Some bug reports are OK. But let's keep this as civi
Bug#765708: [libdc1394-22] "IEEE1394" in short description
Package: libdc1394-22 Version: 2.2.3-1 Severity: minor The short description is: high level programming interface for IEEE1394 digital camera There should be a space between "IEEE" and "1394". By the way, I guess "camera" should be plural. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765657: [debian-reference-en] "This makes its documentation difficult to be [...]" in section 1
Package: debian-reference-en Version: 2.55 Severity: minor Tags: l10n Section 1 contains: The Debian system itself is a moving target. This makes its documentation difficult to be current and correct. Although the current unstable version of the Debian system was used as the basis for writing this, some contents may be already outdated by the time you read this. "to be" should read something like "to keep". By the way, the version of the Debian system used as basis is not the current unstable version [anymore], and I'm not sure this paragraph is warranted. Pretty much all healthy software changes. Debian's documentation is no harder to keep updated than documentation for an equally complex project, disregarding language issues. I suggest shortening this to at most 2 sentences. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765500: [apache2-utils] typo "hostname" in extended description
Package: apache2-utils Version: 2.4.10-5 Severity: minor The extended description starts with: Provides some add-on programs useful for any web server. These include: - ab (Apache benchmark tool) - fcgistarter (Start a FastCGI program) - logresolve (Resolve IP addresses to hostname in logfiles) "hostname" should read "hostnames". By the way, the programs listed are not all useful for any web server. This might have been the case a long time ago, but it is certainly not anymore with programs like check_forensic. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764434: [bsdutils] extended description claims scriptreplay and others are needed
reopen 764434 thanks Hi Andreas, On 2014-10-08 04:20, Andreas Henriksson wrote: Hello Filipus Klutiero! On Tue, Oct 07, 2014 at 11:54:35PM -0400, Filipus Klutiero wrote: Package: bsdutils Version: 1:2.25.1-3 Severity: minor X-Debbugs-Cc: 532...@bugs.debian.org The extended description reads: This package contains the bare minimum of BSD utilities needed for a Debian system: logger, renice, script, scriptreplay, and wall. The remaining standard BSD utilities are provided by bsdmainutils. While bsdutils does contain the listed utilities, and while bsdutils is flagged as essential, Debian systems surely do not need script and scriptreplay, at least. By the way, I'm not sure "standard BSD utilities" means anything, but if it does, the last paragraph of bsdmainutils's extended description strongly suggests the sentence is no longer correct. It could be removed or changed to "Other BSD utilities are provided by bsdmainutils." This is a discussion you don't want to have with only me. Instead try to reach consensus with what the wider Debian community thinks. You must have received this mail because you are part of Debian's util-linux maintainers. I did not specifically send this email to you. Personally I have no problem with getting rid of all the BSD legacy but I know there are people out there who would rather see the sun stop burning then this happening. See for example the followup in the thread about trimming priority standard: https://lists.debian.org/debian-devel/2014/09/msg00466.html I guess the issue I meant to report wasn't clear. I'm sure some of the contents of bsdutils don't need priority essential, but I was by no means asking to get "rid of all the BSD legacy". All I'm asking is to change the description so readers stop being misled. I'm thus going to close your bug report as I don't see anything that's supposed to be fixed here. (I'll additionally set the wontfix tag to make sure this shows up in anyone searching for things in the future that has gone unfixed for various reasons.) Tickets can be closed or tagged wontfix, not both simultaneously. In this case, you meant to tag wontfix (by closing, people looking for unfixed things will cease to see the ticket). All I can do about the "standard BSD utilities" phrase not having any meaning to you is to suggest you do something which by todays means might be called archeology, or atleast getting to know the history. I'm not sure which history you allude to, but if that's your only suggestion, I can only recommend to cease using that term. Regards, Andreas Henriksson -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764994: description of aptitude in section 2.2.1
Hi Osamu, On 2014-10-13 02:39, Osamu Aoki wrote: Hi, Thanks for pointing out this bug. Actually, list was intended to be like what exactly you pointed out. It was my mistake in markup with asciidoc. (I got confused with mediawiki etc.) Ah, no problem. This seems to be the only case of this type of bug as I checked. Good, thanks As for the "Author", this is intentional choice. emacs/vim, apt-get/aptitude, ... there is no right or wrong for which one to use. I can only speak of me. "Debian" does not make position on which software is the best one. *I* personally feels people use apt-get over aptitude too much. Aptitude has some issues but *I* think it is the best package management tool on Debian. I have never used aptitude, so I certainly can't challenge your position. However, what I can do is to tell you how such an information will be perceived. If I would find a reference of this kind in the *reference* of an OS I was learning, I would likely close the book and go back to my current OS or look for another option. In other words, the reader will either: * Picture the project as amateur * Simply consider the information as irrelevant, in the best case I can also tell you some alternatives. Debian does make software choices. The reference *can* recommend a certain manager, if appropriate effort is made to ensure that the project wants to recommend that implementation. You can also expose your preferences indirectly, by putting more emphasis on a certain manager. In fact, the reference already does that in quite an extreme way for aptitude, dedicating the entire section 2.3 to it. As for combining text into long paragraph, I will not do so with 2 main reasons: * It does not match with the style used across this document. * It will break translations with no real advantage. At least, 3 sub-bulleted items describe different things: * typical results of incidents * speculated mechanism of incidents * solution to incidents Thanks I'm not sure how this proposal would conflict with the style. As for breaking translations, that's hard to avoid. Lists should be introduced, and the item currently in third position does not introduce the following [sub-]items. -- Filipus Klutiero http://www.philippecloutier.com
Bug#765313: [apt] Please split the apt binary package
Package: apt Version: 1.0.9.2 Severity: wishlist Following commit b463a73a03a50d886edef176fbdb5827e675d64b <http://anonscm.debian.org/cgit/apt/apt.git/commit/debian/control?id=b463a73a03a50d886edef176fbdb5827e675d64b>, the apt binary package is described as a "commandline package manager": This package provides commandline tools for searching and managing as well as querying information about packages as a low-level access to all features of the libapt-pkg library. Of course, this is just one component of apt, which is a dependency of all APT-based package managers. I wanted to request a change to descriptions, but descriptions would be simplified and apt would be lighter by splitting the "commandline package manager" part into another package. This package could be named apt-cli. It would certainly contain /usr/bin/apt and apt-get. The apt binary package should keep library files, manual pages / configuration as well as anything needed by APT-based package managers. I recommend to have the apt binary package recommend "apt-cli", at least initially. For transitional reasons, this should probably even be an absolute dependency, unless the package containing the core APT is renamed, in which case apt could be a transitional package depending on apt-cli. -- Filipus Klutiero http://www.philippecloutier.com
Bug#764994: [debian-reference-en] Confusing description of aptitude in section 2.2.1
Package: debian-reference-en Version: 2.54 Severity: minor Section 2.2.1. |apt-get| / |apt-cache| vs. |aptitude| contains: Although |aptitude| is a very nice interactive tool which the author mainly uses, you should know some cautionary facts: * The |aptitude| command is not recommended for the release-to-release system upgrade on the |stable| Debian system after the new release. * The use of "|apt-get dist-upgrade|" is recommended for it. See Bug #411280 <http://bugs.debian.org/411280>. * The |aptitude| command sometimes suggests mass package removals for the system upgrade on the |testing| or |unstable| Debian system. * This situation has frightened many system administrators. Don't panic. * This seems to be caused mostly by the version skew among packages depended or recommended by a meta-package such as |gnome-core|. * This can be resolved by selecting "Cancel pending actions" in the |aptitude| command menu, exiting |aptitude|, and using "|apt-get dist-upgrade|". That is, six first-level list items. However, these are really just 2 facts. Item 2 is a continuation of item 1 and items 4, 5 and 6 are a continuation of item 3. This could be fixed by turning items 2, 4, 5 and 6 into second-level list items. However, I am not sure that using so many items is necessary. I would merge items 4, 5 and 6 into a single item. By the way, this section would look a lot more serious if the mention to "the author" was removed. -- Filipus Klutiero http://www.philippecloutier.com
Bug#764861: [adwaita-icon-theme] "gnome" in extended description
Package: adwaita-icon-theme Version: 3.14.0-2 Severity: minor The extended description ends with: The icons are used in many of the official gnome applications like eog, evince, system monitor, and many more. "gnome" is a proper name and should be capitalized. By the way, "evince" should also be capitalized. -- Filipus Klutiero http://www.philippecloutier.com
Bug#764670: [libturbojpeg1] Please clarify description
Package: libturbojpeg1 Version: 1:1.3.1-6 Severity: wishlist The short description reads: TurboJPEG runtime library - SIMD optimized The extended description reads: The libjpeg-turbo JPEG library is a library for handling JPEG files. libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2, NEON) to accelerate baseline JPEG compression and decompression on x86, x86-64, and ARM systems. This package contains the TurboJPEG shared runtime library. There are a couple of issues here. The first sentence is probably the shortest sentence to contain both "JPEG" and "library" 3 times. Some of these mentions are "indirect", but this could easily be brought down to 2: "libjpeg-turbo is a library for handling JPEG files." More problematic is the fact that libjpeg-turbo is defined, but never referred to, while TurboJPEG is referred to, but never defined. One would think these are equivalent, but http://www.libjpeg-turbo.org/About/TurboJPEG explains that is not the case. I would like to offer a solution, but there's a reason why I was reading these descriptions, and the situation appears non-trivial. The page above suggests "the TurboJPEG shared runtime library" would be wrong, since it defines TurboJPEG as an API. However, if libjpeg-turbo builds 2 libraries, that's not clear from upstream's explanation. This looks like clarification with upstream might be warranted. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764434: [bsdutils] extended description claims scriptreplay and others are needed
Package: bsdutils Version: 1:2.25.1-3 Severity: minor X-Debbugs-Cc: 532...@bugs.debian.org The extended description reads: This package contains the bare minimum of BSD utilities needed for a Debian system: logger, renice, script, scriptreplay, and wall. The remaining standard BSD utilities are provided by bsdmainutils. While bsdutils does contain the listed utilities, and while bsdutils is flagged as essential, Debian systems surely do not need script and scriptreplay, at least. By the way, I'm not sure "standard BSD utilities" means anything, but if it does, the last paragraph of bsdmainutils's extended description strongly suggests the sentence is no longer correct. It could be removed or changed to "Other BSD utilities are provided by bsdmainutils." -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761612: Re: [libatomic1] Incomplete extended description
Hi Matthias, On 2014-09-30 05:28, Matthias Klose wrote: Control: tags -1 + wontfix By the way, the meaning of "__atomic", found in the short and the extended descriptions, is most unclear. It says "__atomic built-in functions", not just "__atomic". I don't think the package description is the place to describe the semantics of atomic functions. I would also be very skeptical. See the standards or the gcc-4.9-doc packages instead for such documentation. Frankly, I don't think I want to learn how libatomic works. All I'd like to know is what it contains - why gcc demands it. Why did you close this ticket? The extended description still opens with an incomplete sentence. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761424: Reopen
reopen 761424 thanks This bug persists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763835: Re: Bug#763835: [debian-installer] "linux" lowercase in changelog
Hi Cyril, On 2014-10-02 22:03, Cyril Brulebois wrote: Filipus Klutiero (2014-10-02): Package: debian-installer Version: 20141002 Severity: minor The latest Changes contains this entry: * Bump linux kernel version from 3.14-2 to 3.16-2. "Linux" is a proper noun and should be capitalized. Not a bug. Why do you think that this is not a bug? -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706368: [mediawiki] README.Debian broken/outdated
Hi Thorsten, On 2014-10-02 04:47, Thorsten Glaser wrote: On Sun, 28 Apr 2013, Filipus Klutiero wrote: As previously reported, README.Debian is mostly broken or outdated. However, Feel free to suggest a patch. The end could use a revision, but it's currently fair AFAICS, besides #469571 and this very bug. I'll just review the fixes and report remaining problems if there are some. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763835: [debian-installer] "linux" lowercase in changelog
Package: debian-installer Version: 20141002 Severity: minor The latest Changes contains this entry: * Bump linux kernel version from 3.14-2 to 3.16-2. "Linux" is a proper noun and should be capitalized. By the way, while thanking people in a changelog might be superfluous, specifying that you're not thanking someone is very much superfluous, and inappropriate. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763753: [php-wikidiff2] "is PHP 5 module" in extended description
Package: php-wikidiff2 Version: 1.2+git03ea59f-1 Severity: minor The extended description starts with: Wikidiff2 is PHP 5 module providing external diff engine for MediaWiki. The noun phrase "PHP 5 module" is missing a determiner, such as "a". By the way, it it superfluous to specify the current PHP version. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763678: [libtomcrypt0] "crypthographic" in extended description
On 2014-10-01 15:23, Filipus Klutiero wrote:
Package: libtomcrypt0
Version: 1.17-6
Severity: minor
The extended description starts with:
LibTomCrypt is a well documented, public domain open source crypthographic
toolkit written in C.
"crypthographic" should read "cryptographic".
By the way, the space in the compound modifier "well documented" should be replaced with
a hyphen ("-").
Sorry, I think that was wrong. However, I suggest replacing "public domain open source"
with just "public domain", since public domain implies open source, and since being part
of Debian also implies open source.
--
Filipus Klutiero
http://www.philippecloutier.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763678: [libtomcrypt0] "crypthographic" in extended description
Package: libtomcrypt0
Version: 1.17-6
Severity: minor
The extended description starts with:
LibTomCrypt is a well documented, public domain open source crypthographic
toolkit written in C.
"crypthographic" should read "cryptographic".
By the way, the space in the compound modifier "well documented" should be replaced with
a hyphen ("-").
--
Filipus Klutiero
http://www.philippecloutier.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763676: [apache2-dev] incorrect description of the ASF's goals in extended description
Package: apache2-dev Version: 2.4.10-3 Severity: minor The extended description of apache2-dev and several other packages contains: The Apache Software Foundation's goal is to build a secure, efficient and extensible HTTP server as standards-compliant open source software. The result has long been the number one web server on the Internet. This might have been true a long time ago, but that goal, if it is still one goal of the ASF, is certainly not *the* (only) goal of the ASF. I think it is superfluous to describe the ASF's goals when describing Apache httpd anyway. By the way, the should be a comma after "Apache 2 HTTP server" in the second paragraph. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763651: [redeclipse] "Max OSX" in extended description
On 2014-10-01 12:14, Fabian Greffrath wrote: Am Mittwoch, den 01.10.2014, 11:38 -0400 schrieb Filipus Klutiero: "Mac OSX" should read "Mac OS X" or "OS X". Since this is Debian, maybe nobody is interested in the content of the entire line anyway? I'd suggest to remove it. - Fabian I considered suggesting the same too. That being said, since the description stresses the fact that the game is multiplayer, this is not uninteresting, since it clarifies that Red Eclipse is a candidate for someone looking for a multiplayer FPS to play with people not using Debian, so there's an argument to keep it. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763651: [redeclipse] "Max OSX" in extended description
Package: redeclipse Version: 1.4-6 Severity: minor The extended description contains: * Available for Windows, Linux/BSD and Mac OSX "Mac OSX" should read "Mac OS X" or "OS X". By the way, a space is missing in the short description between "Cube" and "2". -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763415: [libturbojpeg1] Please clarify description
Package: libturbojpeg1 Version: 1:1.3.1-3 Severity: wishlist The short description reads: TurboJPEG runtime library - SIMD optimized The extended description reads: The LJT JPEG library is a library for handling JPEG files. libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2, NEON) to accelerate baseline JPEG compression and decompression on x86, x86-64, and ARM systems. This package contains the libturbojpeg.so.1 library, used by TigerVNC and other users of the past TurboJPEG library. This leaves room for greater clarity in a couple of places. The first paragraph defines "The LJT JPEG library", but it seems nothing refers to that in the rest of the description, so that definition's relevance is unclear. The last paragraph refers to "the past TurboJPEG library". It is unclear what "past" means there. Does it mean TurboJPEG is no longer current? If so, since the short description presents the package as "TurboJPEG runtime library", does this mean the package is outdated? Or what? -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763414: [libjpeg62] "with IIJ JPEG library" in extended description
Package: libjpeg62 Version: 1:1.3.1-3 Severity: minor The extended description contains: The LJT JPEG library is an API/ABI compatible with IIJ JPEG library. The noun phrase "IIJ JPEG library" is missing a determiner (probably "the"). This would still yield a peculiar phrasing. I would suggest: The LJT JPEG library and the IIJ JPEG library have the same API and ABI. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763413: [hyphen-en-us] Missing period in extended description
Package: hyphen-en-us Version: 2.8.8-1 Severity: minor The short description reads: This package contains the English (USA) hyphenation patterns for LibreOffice/OpenOffice.org A period is missing at the end. Note that OpenOffice.org is now simply known as "OpenOffice". -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763410: [installation-guide] 4.3.1: "written directly a USB stick"
Package: installation-guide Version: 20140916 Severity: minor X-Debbugs-Cc: jo...@debian.org Section 4.3.1. Preparing a USB stick using a hybrid CD or DVD image starts with: Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. A preposition such as "on" or "to" is missing between "directly" and "a". By the way, my English is not native, but 4.3's introduction looks like it contains a Frenchism to me: You should be able to see to which device the USB stick was mapped by running the command dmesg after inserting it. Shouldn't "to which device the USB stick was mapped" read "which device the USB stick was mapped to"? -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750519: closed by Michal Čihař (Bug#750519: fixed in phpmyadmin 4:4.2.9-1)
reopen 750519 thanks On 2014-09-22 06:27, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the phpmyadmin package: #750519: [phpmyadmin] "Cannot load or save configuration": Misleading instruction from setup script It has been closed by Michal Čihař . 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 Michal Čihař by replying to this email. I cannot see any difference with 4.2.9. I still see the misleading instruction, and not the proper one. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#640997: Upstream
tags 640997 upstream thanks I forwarded this upstream : https://bugs.kde.org/show_bug.cgi?id=339490 -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#640997: Duplicate
merge 640997 732304 thanks You probably have something wrong. I assume this is a duplicate of #640997. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749673: closed by Michael Gilbert (Bug#749673: fixed in chromium-browser 36.0.1985.32-1)
On 2014-06-04 03:24, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the chromedriver package: #749673: [chromedriver] "chromium" not capitalized in extended description It has been closed by Michael Gilbert . 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 Michael Gilbert by replying to this email. Hum, is this supposed to be fixed in unstable? Unstable's changelog doesn't contain 36.0.1985.32-1's changelog. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761424: [coreutils] df outputs misleading sizes / invalid units
Hi Michael, On 2014-09-13 15:44, Michael Stone wrote: On Sat, Sep 13, 2014 at 03:07:50PM -0400, Filipus Klutiero wrote: According to upstream ticket #18119, the output of df --si is misleading, since the numbers it outputs are different from --human-readable, even though the "units" are the same: $ df --human-readable /dev/sdb2 Filesystem Size Used Avail Use% Mounted on /dev/sdb282G 66G 12G 86% /home $ df --si /dev/sdb2 Filesystem Size Used Avail Use% Mounted on /dev/sdb288G 71G 13G 86% /home Bob Proulx made a point that "G" does not mean GiB nor GB, from which he concludes that the output is simply ambiguous. I will go further and state that the output is invalid, since "G", "M" and others are merely unit prefixes, not actual units. Although this would use more space, I fail to see a better solution than to add 1 or 2 characters to each cell which contains a size. Note that the unit *should* normally be separated from the number with a space. I'm not going to deviate from upstream. If they change, then the debian package will change. FWIW, I'd rather things stay the way they are. The space is more important (in my opinion) than the need for a constant reminder of the unit. The documentation is there for people to read the first time, after that it's just not that important. If you remember all of the documentation you read, your brain is one of a kind and should be promised to research. (Even for the numbers above the difference isn't really significant--the relative sizes are the consistent, and what are the odds that you need exactly 12 gigasomethings? If you did need exactly that much space, you're probably better off looking at kbytes or bytes anyway.) I find it inconsistent to provide 8 digits and more by default, then to say that precision is unimportant or that 1 or 2 spaces cost a lot. I would say 1000 GB is very different from 1000 Gb. An SSD to fit the first will cost hundreds of euros more than one which just stores the latter. Why did that message close the ticket? -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762645: [apache2-bin] Misleading extended description ("Do not install this package [...]")
Package: apache2-bin
Version: 2.4.10-2
Severity: minor
The last paragraph of apache2-bin's description reads:
This package contains the binaries only and does not set up a working
web-server instance. Install the "apache2" package to get a fully working
instance. Do not install this package unless you want to set-up the Apache
HTTP server entirely on your own.
Although the first 2 sentences may be useful, the last one is very confusing at
best. Installing apache2-bin is needed to run Apache, so apache2-bin needs to
be installed. Someone who wants to install Apache needs to install apache2-bin.
The author presumably assumed that administrators used APT and should not
install apache2-bin directly, leaving apache2-bin's installation to APT or the
computer. With that assumption, this is merely a terminological problem - who
is installing a dependency of a requested package, the administrator or the
computer (or both)?
The sentence should at least be clarified, but I think it should just be
removed.
By the way, the short description's parenthesis ("binary files and modules") is redundant, since
modules are binary files. I suggest to change "binary files" to something more specific or to
remove "and modules".
--
Filipus Klutiero
http://www.philippecloutier.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762246: [libmozjs185-1.0] "javascript" not capitalized in short description
Package: libmozjs185-1.0 Version: 1.8.5-1.0.0+dfsg-4.2 Severity: minor The short description reads: Spidermonkey javascript engine "JavaScript" is a proper noun and should at least have a capital "J". Note that "SpiderMonkey"'s "m" is usually uppercase. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762049: [dragonplayer] Unable to play an audio CD (CDDA), except for the first track
Package: dragonplayer Version: 4:4.14.0-1 Severity: important Tags: upstream As reported in upstream's ticket #222844, when playing an audio CD with Dragon Player, the menu items "Previous Chapter" and "Next Chapter" do nothing. Since Dragon stops playing once the first track is over, I am effectively unable to play tracks from an audio CD other than the first. However, this behavior is reportedly different for the author of the upstream ticket. I am using the VLC Phonon backend, 0.7.2. I am setting severity assuming that all Debian users are currently basically unable to play audio CDs, but if this is incorrect, as the upstream ticket suggests might be the case, severity could be re-evaluated. --- System information. --- Architecture: i386 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 990 testing debian.mirror.rafal.ca 500 unstable debian.mirror.rafal.ca 1 experimental debian.mirror.rafal.ca --- Package information. --- Depends (Version) | Installed ===-+- kde-runtime (>> 4:4.10) | 4:4.14.0-2 libc6 (>= 2.4) | 2.19-11 libgcc1 (>= 1:4.1.1) | 1:4.9.1-14 libkdecore5 (>= 4:4.11) | 4:4.14.0-1 libkdeui5 (>= 4:4.11) | 4:4.14.0-1 libkio5 (>= 4:4.11) | 4:4.14.0-1 libkparts4 (>= 4:4.11) | 4:4.14.0-1 libphonon4 (>= 4:4.6.0really4.5.0) | 4:4.7.2-1 libqt4-dbus (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libqtcore4 (>= 4:4.8.0) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libqtgui4 (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2 libsolid4 (>= 4:4.11) | 4:4.14.0-1 libstdc++6 (>= 4.1.1) | 4.9.1-14 phonon | 4:4.7.2-1 Package's Recommends field is empty. Package's Suggests field is empty. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762004: [imagemagick-6.q16] "for quantum depth of 16 bits" in extended description
Package: imagemagick-6.q16 Version: 8:6.8.9.6-4 Severity: minor The extended description ends with: This version of imagemagick is compiled for quantum depth of 16 bits. The noun phrase "quantum depth of 16 bits" is missing a determiner, such as "a". By the way, it is not clear what "Q16" (in the short description) means. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761936: [dolibarr] "third parties external modules" in extended description
Package: dolibarr Version: 3.5.4+dfsg2-1 Severity: minor The extended description ends with: You can also add third parties external modules or develop yours. "third parties external modules" should either read something like "external modules from third parties" or "third-party external modules". By the way, there is something inconsistent in the list. If the items are presented as examples, the last item shouldn't say "And a lot more modules". Either the presentation should just say "Dolibarr offers the following modules" or the last item should be removed. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760900: libteam: improving long description
Hi Dmitry,
On 2014-09-15 02:02, Dmitry Smirnov wrote:
On Mon, 15 Sep 2014 00:56:35 Filipus Klutiero wrote:
Thank you. Here are some more issues I notice:
"libteam" is a library for communication with kernel module (Netlink).|
The noun phrase "kernel module" is missing a determiner. Perhaps this should
read "with the Netlink kernel module".
Also, "libteam" should not be quoted.
This is already implemented in the Linux kernel by the bonding driver but
unlike the bonding driver, libteam (user space) have the following
additional features|
"libteam" is third person singular, therefore "have" should read "has".
Updated with our 5th correction of the long description:
http://anonscm.debian.org/cgit/collab-maint/libteam.git/commit/?id=00659711ac9ef2e69d0825dfe947a2ea4c469eb6
Thanks again for all your suggestions.
Thanks again for the changes.
Here is libteamdctl0's description with more suggestions:
|
"libteamdctl" is a library for communication with teamd process
(via D-Bus, unix socket or zeromq).|
|"libteamdctl" should not be quoted.
"unix" is a proper name and should be capitalized.
|
|
It is used by `teamdctl` utility.|
The noun phrase "`teamdctl` utility||" is missing a determiner. This should read "|the
|`teamdctl` utility||", or just "`teamdctl`||".
|
.
Libteam provides a mechanism to team multiple NICs (ports) at OSI Layer 2
(Data link) into a single virtual NIC. The process is called "channel
bonding", "Ethernet bonding", "channel teaming", "link aggregation", etc.
This is already implemented in the Linux kernel by the bonding driver but
unlike the bonding driver, libteam (user space) has the following
additional features:|
|"unlike [...] additional"| has something redundant. I'm not sure what libteam
is and whether is uses the bonding driver or whether it replaces it, but if it
supplements it, I would suggest the following formulation:
The user-space libteam library adds the following features to the basic
capabilities already implemented in the Linux kernel's bonding driver:
|
* load-balancing for LACP support
* NS/NA (IPV6) link monitoring
* port priorities and stickiness ("primary" option enhancement)
* separate per-port link monitoring setup
.
Libteam requires Linux kernel 3.3 or higher.|
The noun phrase "Linux kernel 3.3 or higher||"||" is missing a determiner. This could read
"version 3.3 or higher of the Linux kernel", or just "Linux 3.3 or higher", although I'm not
sure this sentence is necessary at this point.
--
Filipus Klutiero
http://www.philippecloutier.com
Bug#750891: flashplugin-nonfree: list of supported browsers
Hi Bart, On 2014-09-15 12:28, Bart Martens wrote: Hi Filipus, I'll point to https://wiki.debian.org/FlashPlayer instead. Pointing to wikis from descriptions is unusual and I think this is most important information. But thanks, I prefer no information to something incorrect. I suggest an alternative approach: document the most important browsers supported (at least Firefox / Iceweasel) and refer to the wiki page for more information. Perhaps the description should also explicitly say that Chromium is unsupported. I don't know about SeaMonkey Navigator. Feel free to add it to the wiki page if it works for you. I do not use it. Chromium doens't work with flashplugin-nonfree but it does work with pepperflashplugin-nonfree. So Chromium should be removed from the wiki page. Done Regards, Bart Martens -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760900: libteam: improving long description
Hi Dmitry, On 2014-09-14 21:50, Dmitry Smirnov wrote: On Sun, 14 Sep 2014 17:51:33 Filipus Klutiero wrote: The noun phrase "bonding driver" is missing a determiner such as "the" (this could read "unlike the bonding driver"). Also, I would recommend adding a comma after that. Thanks. Description updated yet again, I hope it is all good now: http://anonscm.debian.org/cgit/collab-maint/libteam.git/diff/?id=99cd2aff05febfaa8e3e8434828865aa13851c60 Thank you. Here are some more issues I notice: | "libteam" is a library for communication with kernel module (Netlink).| The noun phrase "kernel module" is missing a determiner. Perhaps this should read "with the Netlink kernel module". Also, "libteam" should not be quoted. | This is already implemented in the Linux kernel by the bonding driver but unlike the bonding driver, libteam (user space) have the following additional features| "libteam" is third person singular, therefore "have" should read "has". -- Filipus Klutiero http://www.philippecloutier.com
Bug#761612: [libatomic1] Incomplete extended description
Package: libatomic1 Version: 4.9.1-13 Severity: minor The extended description starts with: library providing __atomic built-in functions. By the way, the meaning of "__atomic", found in the short and the extended descriptions, is most unclear. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760900: tagged as pending
On 2014-09-13 23:20, Dmitry Smirnov wrote: On Sat, 13 Sep 2014 13:57:36 Filipus Klutiero wrote: Thanks. There is an issue left in "into logicalone (teamdev)||". The noun phrase is missing a determiner. This could read "into a single logical one", but "logical one" is at best unclear. I'd suggest "into a single virtual NIC". Thanks, I hope it is better now: http://anonscm.debian.org/cgit/collab-maint/libteam.git/diff/?id=aa5e280ba53d84d9eb547c0060abada42abb523d It is, thank you. I notice an issue in the following sentence: | This is already implemented in the Linux kernel by the bonding driver but unlike bonding driver libteam (user space) have the following additional features| The noun phrase "bonding driver" is missing a determiner such as "the" (this could read "unlike the bonding driver"). Also, I would recommend adding a comma after that. -- Filipus Klutiero http://www.philippecloutier.com
Bug#761424: [coreutils] df outputs misleading sizes / invalid units
Package: coreutils Version: 8.23-2 Severity: normal Tags: upstream According to upstream ticket #18119, the output of df --si is misleading, since the numbers it outputs are different from --human-readable, even though the "units" are the same: $ df --human-readable /dev/sdb2 Filesystem Size Used Avail Use% Mounted on /dev/sdb282G 66G 12G 86% /home $ df --si /dev/sdb2 Filesystem Size Used Avail Use% Mounted on /dev/sdb288G 71G 13G 86% /home Bob Proulx made a point that "G" does not mean GiB nor GB, from which he concludes that the output is simply ambiguous. I will go further and state that the output is invalid, since "G", "M" and others are merely unit prefixes, not actual units. Although this would use more space, I fail to see a better solution than to add 1 or 2 characters to each cell which contains a size. Note that the unit *should* normally be separated from the number with a space. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699139: [disktype] outputs misencoded Volume name for UDF disk ("<4300><6900><7600><6900>[...]")
Hi Eriberto, On 2014-09-13 00:15, Eriberto Mota wrote: Hi Filipus, I am the new disktype maintainer. Can you check if the file udf.c[1], dated 2009-04-05, solves the problem? If yes, I will add a patch to disktype. Thanks a lot for your attention. Cheers, Eriberto [1] http://disktype.cvs.sourceforge.net/viewvc/disktype/disktype/udf.c?revision=1.6&view=markup The only difference with the current file is indentation, so... no, no improvement. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760900: tagged as pending
On 2014-09-13 02:39, Dmitry Smirnov wrote: On Thu, 11 Sep 2014 20:12:27 Filipus Klutiero wrote: Thank you. One more issue persists: Libteam provides mechanism to team multiple NICs (ports) into logical one (teamdev) at OSI Layer 2 (Data link). "provides mechanism" is incorrect. "mechanism" is missing a determiner, such as "a" (the sentence could alternatively read "Libteam allows several NICs (ports) to be grouped into a single logical NIC [...]"). Thanks, updated as advised: http://anonscm.debian.org/cgit/collab-maint/libteam.git/commit/?id=ab95564b6214336007431051da104fce0dc66051 Thanks. There is an issue left in "into logicalone (teamdev)||". The noun phrase is missing a determiner. This could read "into a single logical one", but "logical one" is at best unclear. I'd suggest "into a single virtual NIC". [...] -- Filipus Klutiero http://www.philippecloutier.com
Bug#760900: tagged as pending
On 2014-09-09 01:44, Dmitry Smirnov wrote: tag 760900 pending -- We believe that the bug #760900 you reported has been fixed in the Git repository. You can see the commit message below and/or inspect the commit contents at: http://anonscm.debian.org/cgit/collab-maint/libteam.git/diff/?id=0d58638 (This message was generated automatically by 'git-post-receive-tag-pending-commitmsg' hook). --- commit 0d58638 (HEAD, master) Author: Dmitry Smirnov Date: Tue Sep 9 05:40:41 2014 Improve long description (Closes: #760900). Thanks, Filipus Klutiero. Thank you. One more issue persists: Libteam provides mechanism to team multiple NICs (ports) into logical one (teamdev) at OSI Layer 2 (Data link). "provides mechanism" is incorrect. "mechanism" is missing a determiner, such as "a" (the sentence could alternatively read "Libteam allows several NICs (ports) to be grouped into a single logical NIC [...]"). By the way, I have never heard about "channel teaming". Wikipedia however mentions "NIC teaming". -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760900: [libteamdctl0] "Libteam provide mechanism" in extended description
Package: libteamdctl0
Version: 1.12-1
Severity: minor
The extended description contains:
Libteam provide mechanism to team multiple NICs (ports) into one logical one
(teamdev) at L2 layer.
"Libteam" is singular, therefore "to provide" should be third person singular and end with an
"s" ("provides").
By the way, I wonder what "L2 layer" means.
--
Filipus Klutiero
http://www.philippecloutier.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754335: Follow-up
Removal of the test results was requested in #760809. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760809: [php5-common] Please do not ship test-results.txt.gz
Package: php5-common Version: 5.6.0+dfsg-1 Severity: wishlist php5-common ships /usr/share/doc/php5-common/test-results.txt.gz, a 289 kB file which contains nothing but... test results. Not shipping that file in the binary package would make it a quarter lighter. According to a comment from Ondřej Surý in #754335, shipping that file is intentional, hence wishlist severity. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760248: [dpkg] --verify: Please define or explain md5sum verification
Package: dpkg Version: 1.17.13 Severity: wishlist The documentation of the new --verify option discusses the check available: -V, --verify [package-name...] Verifies the integrity of package-name or all packages if omitted, by comparing information from the files installed by a package with the files metadata information stored in the dpkg database. The origin of the files metadata information in the database is the binary packages themselves. That metadata gets collected at package unpack time during the installation process. Currently the only functional check performed is an md5sum verification against the stored value in the files database. It will only get checked if the database contains the file md5sum. To check for any missing metadata in the database, the --audit command can be used. The output format is selectable with the --verify-format option, which by default uses the rpm format, but that might change in the future, and as such, programs parsing this command output should be explicit about the format they expect. The md5sum verification performed should be defined and/or its relevance should be explained (ideally in terms which don't expect the reader to know about hashing algorithms), so that readers understand what a failure means. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760089: [libspandsp-doc] Sentence fragment in extended description
Package: libspandsp-doc Version: 0.0.6-2 Severity: minor The extended description starts with an incomplete sentence: a low-level signal processing library that modulates and demodulates signals commonly used in telephony, such as the "noise" generated by a fax modem or DTMF touchpad. This seems to suggest the package contains the library itself. I suggest: spandsp is a low-level signal processing library that modulates and demodulates signals commonly used in telephony, such as the "noise" generated by a fax modem or DTMF touchpad. Other binary packages start with the same incomplete sentence. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760023: [libbalooqueryparser4] "baloo" not capitalized in extended description
Package: libbalooqueryparser4 Version: 4:4.14.0-1 Severity: minor The extended description contains: This package contains the baloo query parser library ported from Nepomuk. "Baloo" is a proper noun and should be capitalized. Note that this also applies to libbaloowidgets. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#759756: [libktpcommoninternalsprivate7] Typo "contians" in extended description
Package: libktpcommoninternalsprivate7 Version: 0.8.1-2 Severity: minor The extended description ends with: This contians the generic common components. "contians" should read "contains". By the way, "internal" should be pluralized in the short description. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#759755: [libdebconfclient0] "This is a reimplementation of the original debconf version in C." in extended description
Package: libdebconfclient0 Version: 0.191 Severity: minor The extended description reads: Debconf is a configuration management system for Debian packages. It is used by some packages to prompt you for information before they are installed. This is a reimplementation of the original debconf version in C. This is the libraries needed by libdebconfclient-dev and cdebconf. The last definition is the one intended. The first belongs to cdebconf. Replacing "This" with "cdebconf" in the first sentence would fix. However, the proper fix may be to remove the first definition, since a definition of cdebconf doesn't seem necessary. By the way, libdebconfclient is apparently more than the libraries needed by libdebconfclient-dev and cdebconf. Packages are usually defined by what they provide rather than by attempting to list their dependants by extension. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#758758: [python-wstools] unclear description
Package: python-wstools Version: 0.4.3-1.1 Severity: minor The short description of python-wstools is: WSDL parsing services package for Web Services Its extended description reads: Python module for WSDL parsing services package for Web Services. I do not understand what python-wstools contains. While that's no guarantee, it would likely help to stick to full sentences in the extended description and perhaps expand the acronym. -- Filipus Klutiero http://www.philippecloutier.com
Bug#758754: [libvncserver] "vnc" lowercase in short descriptions
Package: libvncserver Version: 0.9.9+dfsg-6 Severity: minor Most binary packages contain "vnc" lowercase. "VNC" is an acronym and should be uppercase. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757747: [libspandsp-doc] "the libspandsp" in extended description
Package: libspandsp-doc Version: 0.0.6-1 Severity: minor The extended description reads: This package contains the online API in HTML for the libspandsp, a low level signal processing library that modulates and demodulates signals commonly used in telephony, such as the "noise" generated by a fax modem or DTMF touchpad. libspandsp is a proper noun. "the libspandsp" should read either "the spandsp signal processing library" as in the short description, or just "libspandsp" or "spandsp". By the way, the issue reported in #725886 persists (in libspandsp2). -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757695: [sysvinit] VCS: "No repositories found"
Package: sysvinit Version: 2.88dsf-53.3 Severity: normal The URL indicated by Vcs-Browser is http://anonscm.debian.org/gitweb/?p=collab-maint/sysvinit This yields: No repositories found I do not know what the URL should be. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757626: [baloo] Typo "funcationality" in short descriptions
Source: baloo Version: 4:4.13.3-1 Severity: minor Half of baloo's binary packages contain "funcationality" rather than "functionality". Note that the short descriptions of baloo4 and baloo-utils are identical. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757625: [python-reportbug] confusing descriptions
Package: python-reportbug Version: 6.5.0+nmu1 Severity: normal The short description reads: Python modules for interacting with bug tracking systems The extended description reads: reportbug is a tool designed to make the reporting of bugs in Debian and derived distributions relatively painless. This package includes Python modules which may be reusable by other tools that want to interact with the Debian bug tracking system. To actually report a bug, install the reportbug package. I imagine that reportbug only supports debbugs, but this is mentioned nowhere. The first paragraph seems to suggest that all Debian derivatives are supported, which - whatever reportbug supports - is incorrect, since several do not have any issue tracking system. I suggest: Python modules for interacting with Debbugs reportbug is a tool designed to make reporting issues in Debian relatively painless. This package includes Python modules used by reportbug and which may be used by other tools that want to interact with issue tracking systems powered by Debbugs, such as Debian's. To actually report an issue, install the reportbug package. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756869: [konq-plugins] Transform Image plugin missing
Package: konq-plugins Version: 4:4.13.3-1 Severity: normal According to the extended description, konq-plugins contains: - Transform Image (service menu): rotate and flip images It appears konq-plugins no longer contains Transform Image. Konqueror does not offer to rotate or flip images. By the way, the Microformat Icon plugin was apparently renamed "Konqueror Feed Icon". -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756865: [libgpgme++2] "c++" not capitalized in short description
Package: libgpgme++2 Version: 4:4.13.3-2 Severity: minor The short description reads: c++ wrapper library for gpgme The "c" in "C++" should be capitalized. By the way, "gpgme" should be uppercase. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756579: [neverball] Please remove the version number from window title
Package: neverball Version: 1.6.0-2 Severity: wishlist Tags: upstream Neverball's window title is "Neverball 1.6.0". While the version number can be useful, it is not worth the space it uses in the taskbar. I guess the version number was put in the window title because it appeared nowhere else in Neverball. It would be best to move it in some screen. Typically, that's About or Credits, but Neverball has no such thing at this time. Alternatively, the number could be in the welcome screen or in Help. I assume this is an upstream issue. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756570: [print-manager] Please do not recommend system-config-printer
Package: print-manager Version: 4:4.13.3-1 Severity: wishlist Starting with 4.13.3-1, print-manager recommends system-config-printer, following a request made in #751966. According to the reporter, print-manager users have good reasons to install system-config-printer and system-config-printer-udev. However, while both system-config-printer and system-config-printer-udev are quite small, system-config-printer has a considerable set of dependencies. On my not-so-GTK-free testing install, upgrading print-manager would cause 18 MB more of disk usage (following 5 MB of download). According to #851966, print-manager should recommend system-config-printer-udev and system-config-printer separately. The former has a lot less dependencies and is an entirely reasonable dependency. We should then try to provide print-manager with what it needs from system-config-printer without resorting to a dependency on system-config-printer. At first sight, it would seem possible to split the D-Bus service from system-config-printer. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755976: [apache2] "It does not install the actual apache2 binaries." in extended description
Package: apache2 Version: 2.4.9-2 Severity: minor The extended description reads: The Apache Software Foundation's goal is to build a secure, efficient and extensible HTTP server as standards-compliant open source software. The result has long been the number one web server on the Internet. This package contains the configuration files, init scripts and support scripts. It does not install the actual apache2 binaries. While apache2 does not *contain* Apache binaries, I fail to see an interpretation of the last sentence which is both correct and useful. Apache binaries are in apache2-bin, which apache2 depends on, so apache2 does provide Apache binaries. If "apache2 does not install the actual apache2 binaries." doesn't mean that installing apache2 does not install the Apache binaries, the intended meaning needs clarification. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755760: [neverball] Fails to grab cursor (cursor moves while playing)
Package: neverball Version: 1.6.0-1 Severity: important When a level is underway, Neverball 1.5 and prior versions used to grab the mouse cursor. The cursor would become invisible until the level was completed or failed. This is no longer the case after the upgrade to 1.6 on my testing install. The cursor is always visible, and can even leave the window when not playing fullscreen. Seeing the cursor is an annoyance, but having it leave the window breaks the gameplay (unless someone was trying to make it even harder!), even though it's still possible to roll quite a bit. In fullscreen mode, the bug remains, but doesn't break ball control nearly as much. In fact, I'm not in a position to exclude that ball control works as it should in fullscreen mode. This is surely the result of the SDL migration (which does fix my problems with mouse handedness and focus, BTW). I'm experiencing this in KDE. I've set severity to important assuming that this affects many but not everyone (in which case, I'd have marked this serious). I have no idea what factors could make only some setups affected. No error is logged on the console. --- System information. --- Architecture: i386 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 990 testing debian.mirror.rafal.ca 500 unstable debian.mirror.rafal.ca 1 experimental debian.mirror.rafal.ca --- Package information. --- Depends (Version) | Installed ===-+-== neverball-data (= 1.6.0-1) | 1.6.0-1 libc6 (>= 2.11) | 2.19-7 libgl1-mesa-glx | 10.2.3-1 OR libgl1 | libjpeg8 (>= 8c) | 8d1-1 libphysfs1 | 2.0.3-2 libpng12-0 (>= 1.2.13-4) | 1.2.50-1 libsdl2-2.0-0 (>= 2.0.0) | 2.0.2+dfsg1-4 libsdl2-ttf-2.0-0 (>= 2.0.0) | 2.0.12+dfsg1-2 libvorbisfile3 (>= 1.1.2) | 1.3.2-1.4 Package's Recommends field is empty. Suggests (Version) | Installed ========-+-=== neverputt | -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754338: Confirmed
I can confirm that sysvinit-core is no longer required. systemd 208-6 just transitioned to testing. libpam-systemd now has a strict dependency on systemd-sysv (which still conflicts with sysvinit-core). Forced to choose between losing sysvinit-core and kde-plasma-desktop, I took the risk of replacing sysvinit-core with systemd-sysv. I am happy to report that this went very well. In fact, my system now boots at a scary pace. This will surely affect many testing users now. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755756: [libtommath0] "which is need" in extended description
Package: libtommath0 Version: 0.42.0-1 Severity: minor The extended description ends with: This package contains the library itself which is need to run programs that use LibTomMath. A minimal fix would be to changed "need" to "needed", but that still looks strange. I would recommend simply: This package contains the library needed to run programs that use LibTomMath. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755755: [libtomcrypt0] "the i386, x86_64 and ppc32 architecture" in extended description
Package: libtomcrypt0 Version: 1.17-5 Severity: minor The extended description ends with: It has several optimizations for the i386, x86_64 and ppc32 architecture. "architecture" should end with an "s". By the way, this sentence goes a little far compared to the usual scope of extended descriptions. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755567: [linux] "firmware: failed to load rtl_nic/rtl8168f-1.fw (-2)" with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Source: linux Version: 3.14.12-1 Severity: minor Systems with a RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller get a message such as: [...] r8169 [...] firmware: failed to load rtl_nic/rtl8168f-1.fw (-2) printed on tty1, unless non-free firmware which allegedly enhances the device is installed. On mine, kern.log contains: Jul 21 20:42:52 vinci kernel: [6.551626] r8169 :03:00.0: firmware: failed to load rtl_nic/rtl8168f-1.fw (-2) Jul 21 20:42:52 vinci kernel: [6.551631] r8169 :03:00.0: Direct firmware load failed with error -2 Jul 21 20:42:52 vinci kernel: [6.551633] r8169 :03:00.0: Falling back to user helper Jul 21 20:42:52 vinci kernel: [6.552140] r8169 :03:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168f-1.fw (-2) This happens with any i386 image. --- System information. --- Architecture: i386 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 990 testing debian.mirror.rafal.ca 500 unstable debian.mirror.rafal.ca 1 experimental debian.mirror.rafal.ca --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#632656: Confirmed
found 632656 2013.60-1 tags 632656 + confirmed thanks This reproduces on my testing install. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754917: [libndp0] "a library the IPv6" in extended description
Source: libndp Version: 1.3-1 Severity: minor Extended descriptions starts with: libndp is a library the IPv6 Neighbor Discovery Protocol (NDP). Something like a "for" is missing between "a library" and "the IPv6 Neighbor Discovery Protocol (NDP)". By the way, there is usually a hyphen in "high level". -- Filipus Klutiero http://www.philippecloutier.com
Bug#754439: [libmm-glib0] "bluetooth" not capitalized in extended description
Package: libmm-glib0 Version: 1.2.0-1 Severity: minor The extended description contains: Whether built-in devices, USB dongles, bluetooth-paired telephones or professional RS232/USB devices with external power supplies, ModemManager is able to prepare and configure the modems and setup connections with them. "Bluetooth" is a proper noun and should be capitalized. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754338: [sysvinit-core] Incorrect priority (required)
Package: sysvinit-core Version: 2.88dsf-53.2 Severity: serious X-Debbugs-Cc: bi...@debian.org X-Debbugs-Cc: 754...@bugs.debian.org sysvinit-core's priority field presents it as required. While I never tried running a Debian system without it or its predecessor, it would appear that sysvinit-core is not / no longer required. The hints I have observed to that effect are the conflict declared by systemd-sysv, Michael Biebl's intervention in #754059, as well as a conflict declared by upstart, as pointed out by Michael. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754335: [php5-common] Ships test-results.txt.gz
Package: php5-common Version: 5.6.0~rc2+dfsg-1 Severity: normal X-Debbugs-Cc: 752...@bugs.debian.org The "fix" for #752099 has visibly introduced an even greater bug. php5-common now ships /usr/share/doc/php5-common/test-results.txt.gz, which contains... a lot of text, thankfully compressed to a .gz which still takes 287 kB. By the way, many of the test results are failures. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754333: [libreoffice-common] Failures on removal ("rmdir: failed to remove [...]")
Package: libreoffice-common Version: 1:4.2.5-1 Severity: minor Removing libreoffice-common produces quite some junk : The following packages will be REMOVED: libreoffice-common 0 upgraded, 0 newly installed, 1 to remove and 8 not upgraded. After this operation, 76.6 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 122231 files and directories currently installed.) Removing libreoffice-common (1:4.2.5-1) ... rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or directory rmdir: failed to remove '/var/lib/libreoffice/share/': Directory not empty rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or directory rmdir: failed to remove '/var/lib/libreoffice': Directory not empty rmdir: failed to remove '/var/lib/libreoffice': Directory not empty Processing triggers for mime-support (3.56) ... Processing triggers for desktop-file-utils (0.22-1) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for shared-mime-info (1.3-1) ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' Processing triggers for gnome-icon-theme (3.12.0-1) ... root@vinci:/home/chealer# The Unknown media errors are probably not libreoffice's fault, but I guess the 5 rmdir failures are. I didn't investigate much, but taking the second as exemple, it won't remove because /var/lib/libreoffice/share/config/ (an empty directory) exists. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
On 2014-07-07 13:04, Michael Biebl wrote: Am 07.07.2014 18:50, schrieb Filipus Klutiero: I suppose there's a reason why a conflict was declared. I didn't mean declaring a conflict with sysvinit-core is a bug *per se*. The bug is to conflict with a package of required priority, namely sysvinit-core. If it's necessary to conflict with a required package, then something's very wrong with the package. Nope, it's not. See also other init systems, like the upstart package, which declare the same Conflicts/Replaces. I did specify "If it's necessary to conflict with a required package". I assume you're implying that's not the case for systemd-sysv and will report a bug regarding sysvinit-core's priority. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
reopen 754059 thanks On 2014-07-07 07:09, Michael Biebl wrote: Am 07.07.2014 08:56, schrieb Filipus Klutiero: Package: systemd-sysv Version: 204-14 Severity: serious systemd-sysv conflicts with sysvinit-core, which is required. Correct, systemd-sysv has a Conflicts/Replaces against sysvinit-core so it is actually possible to switch between different init systems. This is not a bug but intentional and necessary. Thus closing the bug report. Michael I suppose there's a reason why a conflict was declared. I didn't mean declaring a conflict with sysvinit-core is a bug *per se*. The bug is to conflict with a package of required priority, namely sysvinit-core. If it's necessary to conflict with a required package, then something's very wrong with the package. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
Package: systemd-sysv Version: 204-14 Severity: serious systemd-sysv conflicts with sysvinit-core, which is required. This is particularly problematic since libpam-systemd alternatively depends on systemd-sysv. On my testing install, APT's solution when asked to upgrade systemd is to remove sysvinit-core: # LANG=C apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following packages were automatically installed and are no longer required: libcolamd2.8.0 lp-solve xulrunner-29 Use 'apt-get autoremove' to remove them. Done The following packages will be REMOVED: sysvinit-core The following NEW packages will be installed: systemd-sysv The following packages will be upgraded: libpam-systemd libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0 libsystemd-login0 systemd 6 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Removing libpam-systemd isn't too tempting neither: # LANG=C apt-get remove libpam-systemd Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libcolamd2.8.0 libmodemmanagerqt1 libnetworkmanagerqt1 lp-solve xulrunner-29 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: colord hplip kde-plasma-desktop libpam-systemd network-manager plasma-nm plasma-widget-networkmanagement policykit-1 policykit-1-gnome printer-driver-postscript-hp udisks2 0 upgraded, 0 newly installed, 11 to remove and 5 not upgraded. I managed to solve this safely by installing systemd-shim. I was surprised to see APT propose the removal of a required package. I didn't test how that would go, but if that's not a problem, something must be wrong with its priority field. I'll save my system from such an experimentation and let others decide if this needs to be reassigned. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
