Bug#343423: lynx in xterm
Note that I recently installed and later removed a bunch of web browsers. Now readlink -f $(which www-browser) = /usr/bin/lynx.stable. I ran a dist-upgrade from an xterm, and the changelogs appeared in a new xterm with lynx running (as in xterm -e lynx /tmp/foo), and the apt-get process waited until the xterm exited, as it should have. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343444: bug is gone
On Wed, Dec 21, 2005 at 03:40:50PM +0100, Tobias Knieper wrote: Hello, i made a dist-upgrade this morning and the bug is gone. apt upgraded only a few (six or seven) packages. Is it possible to find out which packages my system upgraded? Recent dpkg keeps a log in /var/log/dpkg.log*. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344288: glademm: 'C Options' tab available even when language is not C
Package: glademm Version: 2.6.0-1.2 Severity: minor Tag: upstream I wanted to compare OO GUI coding in glade with nonOO GUI coding, so I created a new project, with only a single window, and selected C++ output. I deselected Output Build Files, which has the ToolTip If files for building the source code are output, including Makefile.am, I expected that Makefile.am would not be generated. However, it was. I guess that 'C options' doesn't affect C++ output. So I suggest that this tab is greyed out and made unavailable unless C is the output language. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344290: glade: Please suggest or recommend glademm
Package: glade Version: 2.10.1-1 Severity: minor File: ./debian/control Please make glade either 'Suggest:' or 'Recommend:' glademm, since it is required for outputting in c++. Also, 'gate' is apparently not packaged for Debian, so it might be nice to disable the ada 95 output language. Or, one could test at runtime if the necessary components are installed.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336982: dh-make: Difficulties with the debian/copyright template
Package: dh-make Version: 0.40 Severity: important File: debian/copyright The problem is with the template ./debian/copyright files created by /usr/bin/dh_make, not /u/s/d/dh-make/copyright. I'm Cc: debian-legal, and I checked the BTS documentation so its going to work right This Time. Please, add comments as necessary; I've tried to do my best to create a sane template, and to dicuss the present problems. Lots of people see and are affected by the dh_make templates, so I think lots of people should comment on changes there. Please keep in mind that lots of new developers will use the New Maint Guide, which essentially has as step 1, Run /usr/bin/dh_make. So it should be easy to understand, and intuitively clear how to do the right thing, even to someone who has no formal education in copyright law. I filed bug #286843: Please use 'Copyright Holder: boilerplate', and dh_make now does so. It looks like: Copyright Holder: put author(s) name and email here This has to include a copyright year, also. Please update the boilerplace to indicate that. Also, the copyright holder is not necessarily the author. This is necessary, I think, in the case that one tries to investigate the trail from authorship, through a list of people between whom copyright may have been transferrred. There is also an issue with the license boilerplace. Consider the developer who notices that their package is apparently (by cursory inspection of a ./COPYING file, or a header in the sources files) under the GPL license. They will be tempted to run: dh_make -c gpl. However, that will cause their packages' copyright file to include the version 2 or later clause, even if it wasn't present in the upstream sources! The same goes for the LGPL. In fact, with the LGPL, there is also the issue of s/package/program/ and s/library/lesser/. I think it is confusing and in bad form to include a modified distribution license covering another's work. Updating the FSF postal address should be okay IMHO. There is another annoyance; .. dh_make -c specifies the license. The -l option is taken by library package. To me, -c means copyright, but then the user is specifying -c gpl, and the gpl is not a copyright holder (which is the most of the motivation behind these bugs). The best solution I came up with involves removing the -c option, thusly removing any implied confusion between copyright and license. Then update the templates, which could become: Upstream Authors: template Include the names and contact addresses of all upstream authors; this is useful, for example, in the case that they need to be contacted regarding licensing issues. It might also make sense to include support addresses here. Example: Justin Pryzby [EMAIL PROTECTED] Support Address [EMAIL PROTECTED] Legal Issues [EMAIL PROTECTED] /template Copyright Statements: template Include the names of all copyright holders here. Also include the range of years during which they made contributions to the package. The copyright holder is not necessarily the same as the upstream author; employers usually hold the copyright on works for hire; other works are placed in the public domain by their authors, which means that copyright is relinquished; other times, copyright is transferred from the author to a publishing agent. All source files must be accounted for; oftentimes, multiple authors are involved in a given software package. You should at least look for evidence of this with a command like: grep -ir copyright . A typical copyright reference will look like: Copyright (C) 2005 Justin Pryzby [EMAIL PROTECTED] /template Distribution Licenses: template Include the licenses of all source files here. Oftentimes, there are multiple licenses involved in a single software package, and each msut be clearly documented. Be particularly careful of such things as the GPL version 2 or later clause; include that clause if and only if the upstream license includes it. /template Lintian should error on m/template/i; I have bug #286842 which is relevant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336982: dh-make: Difficulties with the debian/copyright template
I intended to add to the sections on copyright statements and distribution licenses the following text: This should be copied as nearly verbatim as possible from the upstream sources. On Tue, Nov 01, 2005 at 08:17:46PM -0500, Justin Pryzby wrote: Package: dh-make Version: 0.40 Severity: important File: debian/copyright -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337066: imview: Improper copyright file
Package: imview Version: 1.1.8-2 Severity: normal File: /usr/share/doc/imview The copyright file confuses license and copyright: If not otherwise noted (see below), this software is written by Hugues Talbot and comes with the following copyright: By accepting this notice, you agree to be bound by the following agreements: Please s/copyright/license/ on the second line. Otherwise this file looks to be very well written! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337068: apt-file: curl_getdate warning
Package: apt-file Version: 2.0.6 Severity: normal $ sudo apt-file update Warning: Illegal date format for -z/--timecond (and not a file name). Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337114: dh_make: accepts extra cmd line args
Package: dh_make Version: 0.40 Severity: normal File: /usr/bin/dh_make /tmp/xx-1$ dh_make foo Type of package: single binary, multiple binary, library, kernel module or cdbs? [s/m/l/k/b] dh_make should exit indicating failure if any arguments do not m/^-/, as per Usage: dh_make [options]. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337160: dpatch: manpage typo: s/ th / the /
Package: dpatch Version: 2.0.15 Severity: minor File: /usr/share/man/man7/dpatch.7.gz Tags: patch $ zgrep -w th /usr/share/man/man7/dpatch.7.gz compatibility, th second argument is only present when a working -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337281: sextractor: Provide: sextractor-doc
Package: sextractor
Version: 2.4.3-1
Severity: normal
Tags: confirmed, patch
This is a reminder for myself to edit debian/control for the next
upload. I intend to Provide: sextractor-doc such that users of
previous sextractor packages (by me, with -doc package split by
Florian) will have that package removed (it is obsoleted by this
package). A separate -doc package is still a consideration, though.
Florian, can you confirm that Provide will do what I want? I know
Replaces+Provides+Conflicts is a thing specially interpretted by dpkg.
But I don't need the Conflict or Replaces (though I could use them
anyway, if necessary to have the effect). It seems that Provide:
sextractor-doc will do the right thing, since ${Source-Version} will
be greater than the previous version, and will cause an upgrade.
Right?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337281: sextractor: Provide: sextractor-doc
On Fri, Nov 04, 2005 at 05:30:49PM +0100, Florian Ernst wrote:
On Thu, Nov 03, 2005 at 11:48:47AM -0500, Justin Pryzby wrote:
This is a reminder for myself to edit debian/control for the next
upload. I intend to Provide: sextractor-doc such that users of
previous sextractor packages (by me, with -doc package split by
Florian) will have that package removed (it is obsoleted by this
package). A separate -doc package is still a consideration, though.
Well, I started to split out a separate -doc package in 2.3.2-1, but
according to my webserver logs not even a single person has ever
downloaded those, and soon thereafter I dropped my ITP and sextractor
was completely removed from Debian (bug#204464).
I downloaded them; I think you made them available to me after taking
down the original packages. I still have your diff, thats how I got
the changelog entries.
Florian, can you confirm that Provide will do what I want? I know
Replaces+Provides+Conflicts is a thing specially interpretted by dpkg.
But I don't need the Conflict or Replaces (though I could use them
anyway, if necessary to have the effect). It seems that Provide:
sextractor-doc will do the right thing, since ${Source-Version} will
be greater than the previous version, and will cause an upgrade.
Right?
All in all, Debian has never shipped split packages. I don't know how
widespread use your packages have had, but they weren't split as well
(or were they?), so I guess there is no problem we have to solve.
They were split. Its not a huge problem of course, but might as well
solve it ..
However, if you wish to make sure any sextractor-doc packages that
might have been installed get replaced for now you'll have to set the
triplet as mentioned above or in 7.5.2 Replacing whole packages at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s7.5.2.
Okay.
It might still be worth a though or two on whether a -doc package
should be split out in the future, though, but as you mention above
this is still consideration...
Yea, its a balance between more disk space (~1MB * ~15 archs) vs the
additional overhead of a binary package; I think I remember Joerg
talking about this.
--
Clear skies,
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337605: gstreamer0.8-misc: Upgrade removes /root/.gstreamer-0.8/registry.xml ?!
Package: gstreamer0.8-misc Severity: important Version: 0.8.8-3 File: /root/.gstreamer-0.8/registry.xml Preparing to replace gstreamer0.8-misc 0.8.8-3 (using .../gstreamer0.8-misc_0.8.11-2_i386.deb) ... removed `/root/.gstreamer-0.8/registry.xml' rmdir: removing directory, /root/.gstreamer-0.8 Unpacking replacement gstreamer0.8-misc ... I can't fathom a legitimate reason to remove anything under /root/, ever. I hope that I am I misinterprettign this message, but I just read the preinst script, and I am not: if [ -r /root/.gstreamer-0.8/registry.xml ]; then current=`cat /root/.gstreamer-0.8/registry.xml` if [ $orig = $current ]; then rm -f -v /root/.gstreamer-0.8/registry.xml || true rmdir -v /root/.gstreamer-0.8 || true fi fi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337605: gstreamer0.8-misc: Upgrade removes /root/.gstreamer-0.8/registry.xml ?!
severity 337605 minor thanks On Sat, Nov 05, 2005 at 11:21:21AM +0100, Loic Minier wrote: On Sat, Nov 05, 2005, Justin Pryzby wrote: removed `/root/.gstreamer-0.8/registry.xml' rmdir: removing directory, /root/.gstreamer-0.8 Unpacking replacement gstreamer0.8-misc ... I can't fathom a legitimate reason to remove anything under /root/, ever. I hope that I am I misinterprettign this message, but I just read the preinst script, and I am not: if [ -r /root/.gstreamer-0.8/registry.xml ]; then current=`cat /root/.gstreamer-0.8/registry.xml` if [ $orig = $current ]; then rm -f -v /root/.gstreamer-0.8/registry.xml || true rmdir -v /root/.gstreamer-0.8 || true fi fi Previously, gst-register-0.8 was called without the GST_REGISTRY environment, and that caused some spurious files to be written to /root/.gstreamer-0.8. Okay; I noticed this bug by cheer luck, and all system ever having a gstreamer package installed (be it 0.6 or 0.8) had some spurious directories. Hence, I decided to fix the problem and try removing as much cruft as possible, so all packages where the fix appeared saw the addition of code to detect whether the file was automatically generated. Okay; why do you use a sh = test rather than diff followed by a check of $? ?. (diff Priority: required) As you can see, the script is very cautious about removing a file with the exact same contents as one generated by the package, and only removes the directory if empty. Actually I didn't even read the conditional part last night. If you think something else should have been done, please suggest what. I agree that this is pretty safe. Maybe leave the bug open until this snipped is removed from preinst? Which I guess is the first upload after etch release, correct? But is the problem actually fixed?? (Reading database ... 174462 files and directories currently installed.) Preparing to replace gstreamer0.8-misc 0.8.8-2 (using .../gstreamer0.8-misc_0.8.11-2_i386.deb) ... removed `/root/.gstreamer-0.8/registry.xml' rmdir: removing directory, /root/.gstreamer-0.8 Unpacking replacement gstreamer0.8-misc ... Setting up gstreamer0.8-misc (0.8.11-2) ... [EMAIL PROTECTED]:~$ ls /root/.g .gconf/ .gnome/ .gnome2_private/ .gconfd/ .gnome2/ .gstreamer/ [EMAIL PROTECTED]:~$ ls /root/.gstreamer/registry.xml [EMAIL PROTECTED]:~$ ls /root/.gstreamer/registry.xml /root/.gstreamer/registry.xml -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337605: gstreamer0.8-misc: Upgrade removes /root/.gstreamer-0.8/registry.xml ?!
On Sat, Nov 05, 2005 at 06:21:35PM +0100, Loic Minier wrote: retitle 337605 [post-etch] please remove postinst snipset to cleanup /root/.gstreamer-0.8 thanks Hi, On Sat, Nov 05, 2005, Justin Pryzby wrote: Okay; why do you use a sh = test rather than diff followed by a check of $? ?. (diff Priority: required) I didn't think, I don't think this is terribly ugly. Okay. I agree that this is pretty safe. Maybe leave the bug open until this snipped is removed from preinst? Which I guess is the first upload after etch release, correct? Fine for me. Great. But is the problem actually fixed?? [EMAIL PROTECTED]:~$ ls /root/.g .gconf/ .gnome/ .gnome2_private/ .gconfd/ .gnome2/ .gstreamer/ As I explained, I noticed the problem when I took up the packages, and I thought it was too late for gstreamer 0.6 (called gstreamer) which was already gone from the archive. Hence, I only fixed the 0.8 series, I didn't want to fix 0.6 stuff in the 0.8 series... OH okay. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337667: accepts invalid versions on submit; impossible to correct
On Mon, Sep 26, 2005 at 09:22:31PM +0200, Peter Eisentraut wrote: Package: bugs.debian.org Severity: normal This is concerning bug #329597. The user submitted the bug with the following headers: Package: egroupware Version: egroupware/1.0.0.007-2.dfsg-2sarge1 The version line was recorded literally, which throws off the found/fixed calculation. I've tried to fix it by sending the following to control@: notfound 329597 egroupware/1.0.0.007-2.dfsg-2sarge1 found 329597 1.0.0.007-2.dfsg-2sarge1 But the BTS reacted to the first line with Unknown command or malformed arguments to command. Either the control commands are more flexible in what they accept as arguments, or the version number format should be checked on submission (probably a good idea anyway; the valid format of a version number is well-known and the found/fixed system requires a valid version number). One could also check that it is a version of a package (currently) available from Debian. If the version is not currently available, the person should try updating. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337068: (no subject)
I think this happens when the file doesn't exist. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336098: considering the removal of saods9
I'm considering having saods9 removed. The FTBFS bugs aren't a problem; the original one is fixed upstream, in 4.0b7, and the others are easy to fix by adding lines like class matrix;. Also, I can either link against tcl8.3 (after applying a patch) or statically link against a specially-compiled tcl8.4 to solve the reported crash on Horizontal cut graph. But, ./saods9/sla/ contains obscured C code. slalib is written by Patrick Wallace, and a Fortran copy is distributed under the GPL by Starlink. A proprietary C copy is commercially available from Wallace. ./sla/ is an obscured C copy, with a GPL header. I'm not sure whether the GPL header was added by Wallace or by Bill Joye upstream, but it doesn't really matter WRT to the DFSG. Bill Joye just got back to me after conversation with Pat Wallace, Doug Mink, and John Roll. I guess the v4 release isn't planned to fix this problem, so its apparently up to me to fix. I'm going to fool around with the GPL fortran implementation, and see if I can come up with anything useful. First, I'll have to reread about C, Fortran, and f2c calling conventions. I've filed an RC removal bug, against saods9 only, and given myself a deadline of 2006-01-01 to have a new package uploaded, otherwise I will give up. FYI, the upstream websever hea-www.harvard.edu has been down for a few days now (again). Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336661: bash: assertion fails when logging in to NIS account
reassign 336661 bash, libc6 severity 336661 important thanks On Mon, Oct 31, 2005 at 02:22:27PM -0500, Bradley, James D. wrote: Package: bash Version: 3.0-17 Severity: normal *** Please type your report below this line *** On my NIS client system (running nis 3.15-2), I have my NIS accounts imported using a netgroup in /etc/passwd and /etc/shadow ([EMAIL PROTECTED]:::...). When I try to log in or su to a NIS account, I get the following error: bash: nss_nis/nis-netgrp.c:79: _nss_nis_setnetgrent: Assertion `malloc_usable_size (netgrp-data) = len + 1' failed. Since thats a glibc file, I suspect a glibc bug. Libraries should never fail assertions. In fact, shouldn't assertions be disabled with -DNDEBUG=1? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334798: screen position
I'm more convinced than ever that this is a blackbox bug. When the window shifts itself to the center row, the position which blackbox indicates for the window is: 2147483647 aka INT32_MAX. Not only that, moving by one pixel changes the X position to 2147483647. The Y position is never really visible, since the X position takes up so much space .. but it appears to work as expected; 0 at the top of the screen and 700 at the bottom. Still can't fathom why it only happens with firefox, though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337922: too much aggressive HELO_DYNAMIC_* tests
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 HELO_DYNAMIC_DHCP and HELO_DYNAMIC_IPADDR both will not match if an ISP's relay is used; they fire only if the last untrusted IP delivered them directly. They also do not act on rDNS; they act on HELO strings that match that kind of rDNS. Major difference. - --j. Marco d'Itri writes: A single generic rDNS in a Received header is enough to raise way too much the score. Also, it appears that this check would be applied even to mail delivered trought an ISP relay. X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on wonderland.linux= =2Eit X-Spam-Level: * X-Spam-Status: Yes, score=3D5.4 required=3D5.0 tests=3DBAYES_00,HELO_DYNAMI= C_DHCP, HELO_DYNAMIC_IPADDR autolearn=3Dno version=3D3.1.0 X-Spam-Report:=20 * 3.8 HELO_DYNAMIC_DHCP Relay HELO'd using suspicious hostname (DH= CP) * 3.9 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (= IP addr * 1) * -2.3 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.] X-Original-To: ...wonderland.linux.it Delivered-To: ...wonderland.linux.it Received: from attila.bofh.it (localhost [127.0.0.1]) by wonderland.linux.it (Postfix) with ESMTP id 65F211C7C7 for ...wonderland.linux.it; Mon, 7 Nov 2005 10:44:17 +0100 (CET) Received: from picard.linux.it (picard.linux.it [IPv6:2001:1418:10:5::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by attila.bofh.it (Postfix) with ESMTP id C099A5F7AA for ...wonderland.linux.it; Mon, 7 Nov 2005 10:44:17 +0100 (CET) Received: from dsl-217-155-153-11.zen.co.uk (dsl-217-155-153-11.zen.co.uk [= 217.155.153.11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by picard.linux.it (Postfix) with ESMTP id 4D32F3F00 for [EMAIL PROTECTED]; Mon, 7 Nov 2005 10:44:16 +0100 (CET) Received: from phil by dsl-217-155-153-11.zen.co.uk with local (Exim 4.54) id 1EZ3Xz-0002SP-MZ for [EMAIL PROTECTED]; Mon, 07 Nov 2005 09:44:15 + --=20 ciao, Marco --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDbyVbFGfw2OHuP7ERAhBtAJ9PdhbYtSk47bAKgC6SkwTT/4kDwACfcsKY qT6szMyk+xgiAC3fX55j8nE= =Ib10 -END PGP SIGNATURE- --PEIAKu/WMn1b1Hv9-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Exmh CVS iD8DBQFDb5clMJF5cimLx9ARAovXAKCPI2a8BFbJcsMlOpbeS24o7HpgJQCggyht 8ifMQM3++qIOzrb5q4LMk2Y= =vLps -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336982: packaging copyright and license
Lets also include in ./debian/copyright some templates of the form: Debian packaging is a work by NAME DEBEMAIL, during the period YEARS. The packaging is hereby released as public domain. OR The packaging is hereby released under the LICENSE license. LICENSE TEXT HERE It would be good to include such a thing in ./debian/rules, also: #!/usr/bin/make -f # -*- makefile for sextractor -*- Is this some emacs line? Why can't it say # Build rules for sextractor # This file was originally written by Joey Hess and Craig Small. # As a special exception, when this file is copied by dh-make into a # dh-make output file, you may use that output file without # restriction. # This special exception was added by Craig Small in version 0.37 of # dh-make. # Modifications for PACKAGE are a work of NAME DEBEMAIL, during the # period $YEARS, and are hereby released under the LICENSE license. # LICENSE TEXT HERE (or, are hereby released as 'public domain'). Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338048: *.d.o: Please document ftp hints
Package: qa.debian.org, ftp.debian.org, www.debian.org Severity: wishlist File: http://ftp-master.debian.org/testing/hints/ Please integrate documentation of the testing hints in useful places. I would suggest the following: http://packages.qa.debian.org/ might need a section to indicate when a package has been hinted, or can be added to an existing section; http://www.debian.org/devel/testing/ might have a direct link and a new paragraph about testing hints and how they relate to the conditions necessary for testing propogation; http://ftp.debian.org/ might have a direct link and a sentence about aTesting hints/a are available. I would also suggest that other such things are made available from the FTP webserver. Also, it would be nice this were also available from FTP server, or if directory browsing from a higher level directory was allowed for the webserver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330812: source the script
Why not source the script? Error in the script should IMHO be detected and cause the initscript to fail. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337922: too much aggressive HELO_DYNAMIC_* tests
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Armstrong writes: This may not have been the wisest choice by the administrator considering the circumstances, but I think it's hard to argue that people should use an HELO string different from the rDNS... Quite. If I set it differently to the rDNS then I hit another set of reject rules. Unfortunately, my ISP doesn't currently offer the ability to set my own rDNS to match my personal domain, which is what I'd prefer to do obviously. What are those other reject rules? The problem here is *not* simply that your rDNS looks dynamic in any way. We in SpamAssassin understand that many ISPs still do that, c'est la vie. The problem, instead, is threefold: 1. that the rDNS string appears symptomatic of a dynamic pool 2. that you're delivering direct-to-MX 3. that the HELO string matches the dynamic-looking rDNS The combination of all 3 has been a very strong spam signature with virtually nonexistent nonspam hits, for over a year. The easiest part to fix is number 3. Change your MTA to use its own name (e.g. mail.yourdomain.com) as the HELO string, instead of whatever rDNS it has been assigned. To the best of my knowledge and experience, using a HELO string that doesn't match rDNS will not cause issues with filtering elsewhere, as it's SOP for many other domains. If after this you still believe that a 7.7 score is correct then please say so, at least he (who I Cc'ed) will know why in the future all his mail will be rejected by spamassassin. :-) 7.7! Seems extreme for someone who has a static ip address has set the SMTP HELO to match the rDNS for that ip. Given that this is *precisely* what is suggested by the relevant RFCs I'm slightly peeved! I'm seeing 4.7 here, nowhere near 7.7. - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Exmh CVS iD8DBQFDcOXxMJF5cimLx9ARAipXAJ9mu7L8z6j9KAPK5+eFMjzixCvpwgCgiA6j n9OkiyHTFXkltKzcHBqO+F0= =WqqW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338203: 73 pkgs contain debhelper maintscript remnant (cruft?)
Package: lintian Severity: wishlist I am including a list of 73 packages which happened to be installed on my laptop which contain a maintscript with the fragment: # dh_installdeb will replace this with shell code automatically # generated by other debhelper scripts. Maybe this is a debhelper bug? Both of my packages contain postinst and postrm, only, and generated entirely by debhelper. They have sections like: # Automatically added by dh_installmenu ... # End automatically added section Which I think is well done. But IMHO the section about debhelper will replace ... is indicitive of a bug. Either that text should be removed, or something should be put in its place. Maybe these packages are buggy and need to do some certain thing, such that debhelper can do that replacement, but they don't do it? In any case, I would like to request that lintian includes a check to ensure that new packages do not contain that text. Package list follows; 73 out of 1269 (5.8%) installed packages are affected. Please Cc: me. -- Clear skies, Justin apt apt-listchanges apt-show-versions aptitude avifile-player bittornado ca-certificates chaksem checksecurity clara dangen ddclient debtags defoma dhcp3-client dict-bouvier dict-gazetteer2k-counties dict-gazetteer2k-places dict-gazetteer2k-zips dpkg-cross eep24c electricsheep elinks gs-common gs-gpl gsfonts hevea icebreaker imagemagick info2www jadetex le less libcupsys2 libdevmapper1 libgtk1 libgtk2 libmoe1 libmysqlclient12 libmysqlclient14 libpam-runtime libpango1 libroken16-kerberos4kth libruby1 libsensors3 libsndfile0 login lp-solve lprng mailliststat menu-xdg moon-buggy-esd mpg321 ncurses-hexedit nvram-wakeup openssh-client openssh-server passwd procps psfontmgr sbuild tetex-base tetex-bin timidity tkinfo tpconfig upgrade-system usbutils vche vtgrab w3c-dtd-xhtml xfig xtux-server -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338213: www: experimental.debian.net says that it is the home of the main buildd network
Package: www.debian.org File: http://experimental.debian.net/ Severity: normal Version: 20051108 Tags: patch Probably www.debian.org isn't the right place for this bug, but I have doubts that there is a better place. Cc: [EMAIL PROTECTED] who is the experimental contact. The given address says: This is the central coordination site for the Debian GNU/Linux package auto-builders. But it shouldn't say that. Rather it should say something of the form: This is the auto-building coordination site for the experimental distribution of aDebian/a. The non-experimental buildd site is ahere/a. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338350: gaim: grammar in IRC message: you're not channel operator
Package: gaim Version: 1:1.5.0+1.5.1cvs20051015-1 Severity: minor Tags: patch The message You're not channel operator I think should be You're not a channel operator ^^^ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338412: mingw32: defining _NO_OLD_NAMES and including unistd.h causes errs
Package: mingw32
Version: 3.4.4.20050522.1-2
Severity: normal
Compiling any trivial program which includes unistd.h with
_NO_OLDNAMES defined fails with the following sorts of errors:
/usr/lib/gcc/i586-mingw32msvc/3.4.4/../../../../i586-mingw32msvc/include/unistd.h:23:
error: syntax error before off_t
...
This doesn't happen for normal gcc, and its useful for me to be able
to define that macro (since lots of astronomy code uses WCS world
coordinate system functions, whose names conflict with the wcs*
functions, but don't conflict if that macro isn't defined).
--
Clear skies,
Justin
#define _NO_OLDNAMES1
#include unistd.h
int main(){return 0;}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303665: preparing upload
package saods9 tag 318042 pending tag 336098 pending tag 303665 pending tag 315690 pending tag 303668 pending thanks I'm preparing an upload now which will close the listed bugs. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343444: bug is gone
On Wed, Dec 21, 2005 at 05:04:58PM +0100, Frank K??ster wrote: Tobias Knieper [EMAIL PROTECTED] wrote: Hello, i made a dist-upgrade this morning and the bug is gone. apt upgraded only a few (six or seven) packages. Is it possible to find out which packages my system upgraded? If you use aptitude, it's in /var/log/aptitude; I think dpkg does not yet keep a log. It does by default since 1.13.5 and possible since 1.13.2! -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#158937: does this bug apply to glade-2?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=158937 glade segfaults when I try to write source for this design. This XML file doesn't work with glade-2; I suspect that this bug no longer applies to any package in Debian, and should thus be closed. Right? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240817: moreinfo
tag 240817 moreinfo thanks Please close this bug after 2006-01-01 if the submitter hasn't responded; I believe this bug no longer applies. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344374: linux-image: error message missing words/variables/parameters
Package: linux-image-2.6.14-2-686 Version: 2.6.14-6 Severity: normal x Error running the boot loader in test mode. x x x x An error occurred while running the boot loader in test mode. A log is x x available in /var/log/lilo_log.11026. Please edit /etc/.conf manually x x and re-run , or make other arrangements to boot your machine. x the boot loader ___ in test mode /etc/___.conf re-run ___, or make -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344526: glade: Please upload to unstable
Package: glade Version: 2.10.1-1 Severity: wishlist Please upload to unstable, now that [2005-12-22] gtk+2.0 2.8.9-2 MIGRATED to testing (Britney). I'm anxious to have it not crash :) Thanks. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343423: (no subject)
This problem isn't specific to being run under /usr/bin/screen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299127: agree
I agree with Roland here, that if 'aptitude download' is successful, the file should exist in the CWD. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344544: linux-doc: provides man9/ but no manpages in this package
Package: linux-doc-2.6.14 Version: 2.6.14-4 Severity: minor $ dpkg -L linux-doc-2.6.14 |grep man9 /usr/share/man/man9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324143: patch
package tktable tag 320551 = patch tag 343138 = patch tag 324143 moreinfo tag 339056 patch thanks My patch doesn't fix #324143, and I still don't know what causes it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On Fri, Dec 23, 2005 at 09:36:47PM +0100, [EMAIL PROTECTED] wrote: Why didn't you prevent bash 3.1-1 entering to testing if you knew about this fucking regression? I really think bash 3.0 should be in testing until a fix for this bug is found. Why? It was rated a 'normal' severity bug by the submitter, and nobody changed it. I think this is the correct severity. Since it isn't RC, it doesn't prevent testing propogation. Is there some reason why this is highly important to you? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On Sat, Dec 24, 2005 at 12:06:07AM +0100, [EMAIL PROTECTED] wrote: Justin Pryzby wrote: On Fri, Dec 23, 2005 at 09:36:47PM +0100, [EMAIL PROTECTED] wrote: Why didn't you prevent bash 3.1-1 entering to testing if you knew about this fucking regression? I really think bash 3.0 should be in testing until a fix for this bug is found. Why? It was rated a 'normal' severity bug by the submitter, and nobody changed it. I think this is the correct severity. Since it isn't RC, it doesn't prevent testing propagation. Is there some reason why this is highly important to you? It's a regression. I thing regressions should prevent packages from entering testing otherwise code can degrade if nobody fixes it. I had to downgrade to 3.0 because of this regression. Regressions are bad, of course. But, whereas the regression was known before testing propogation, there were of course other changes made, which fixed other problems, and included other enhancements, such has possibly made bash more easily maintainable. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#160418: reopen bug for /var/lock/
reopen 160418 thanks Do you still want to move the lockfile to /var/lock/? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342488: upgrade still doesn't happen
reopen 342488 thanks It seems that the upgrade still doesn't happen as it should. This is with libsvncpp0c2_0.8.0-3 installed, though I don't understand why not. $ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done The following packages have been kept back: rapidsvn udev If I force the upgrade of rapidsvn, then it works as it should: $ sudo apt-get install rapidsvn Reading package lists... Done Building dependency tree... Done The following extra packages will be installed: libsvncpp0c2a The following packages will be REMOVED: libsvncpp0c2 The following NEW packages will be installed: libsvncpp0c2a The following packages will be upgraded: rapidsvn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344831: DevRef: Please document best practice for submitters testing bugs
Package: developers-reference Severity: wishlist Do you think it would be worthwhile to include some documentation to the following effect, perhaps added to either 5.8.2 or 5.8.3? It is best to close bugs only when the submitter agrees that it should be closed. Oftentimes during bug triage, stale bugs are discovered which may have been fixed many releases ago, but which remain opened. Sometimes, the report is short and simple, and it is easy to check whether the bug still applies. Other times, the discussion in the bug log is long and documents requests by various people. In any case, it is good to have the submitters approval that the reported problem has been solved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#155334: (no subject)
Bugs #155334 and #316001 are related. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#155334: (no subject)
Bugs #160225, #155334 and #316001 are related. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344831: additional info
I would also like to add the suggestion that each bug report might have a patch sent to it by the maintainer, whenever thats appropriate. This allows submitters to test that the patch actually resolves the problem, and let the maintainer know if it does or does not. It is also nice if the maintainer compilies an unofficial package, and makes a copy available from, for example, people.d.o, which allows for easy testing by even novice users. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344847: thuriaux's scripts definite MIAs
Package: qa.debian.org Severity: wishlist Version: 20051226 On Mon, Dec 26, 2005 at 03:29:43PM -0500, Nathanael Nerode wrote: So the scripts at http://haydn.debian.org/~thuriaux-guest/qa ROCK. Can we get them integrated into the main QA website perhaps? Agree. At least lets mention them so I don't spend time googling for them every day :} FWIW c2html, restartd, and ttylog *sound* interesting, and I think I've used c2html in the past, with good results. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344831: additional info
I suppose there should also be mention of MIA submitters :) Something like: If submitters cannot be contacted within a reasonable time, or are otherwise unable to test whether the problem is solved, then the bug can be closed or left opened depending on preference the of the maintainer. If someone experiences the problem in the future, the information in the bug can be referenced. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344971: dh-make: Please change to use $@ variable rather than hardcoded names
Package: dh-make Version: 0.40 Severity: minor dh_make touches the following targets by filename: $ dpkg -L dh-make |xargs grep -o 'touch [^ ]*' /usr/bin/dh_make:touch configure-stamp\n; /usr/share/debhelper/dh_make/debiank/rules:touch build-arch-stamp /usr/share/debhelper/dh_make/debiank/rules:touch build-indep-stamp /usr/share/debhelper/dh_make/debianl/rules:touch build-stamp /usr/share/debhelper/dh_make/debianm/rules:touch build-arch-stamp /usr/share/debhelper/dh_make/debianm/rules:touch build-indep-stamp /usr/share/debhelper/dh_make/debians/rules:touch build-stamp /usr/share/doc/dh-make/examples/kde-singlebinary/rules:touch build-stamp I think each of these should be touch $@ to avoid repetition of the target name. (This might be mentioned in another bug, by me?, but I can't find it now, so I risk reporting it again. Well it should probably be separate anyway.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344972: Please add more pointers to debconf-devel(7) (Was: Re: Policy documentation on debconf)
Package: developers-reference, www.debian.org Severity: wishlist Please mention devconf-devel(7) in the developers reference and at debian.org/devel/ I really hope its clear that debconf-devel needs to have something else pointing to it, since it is the second time in 30 days that someone has been unable to find it: http://lists.debian.org/debian-mentors/2005/11/msg00258.html http://lists.debian.org/debian-mentors/2005/12/msg00383.html I don't know if this ever made it into DevRef, but I can't find that it did. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344973: xmove: shlibs file has no EOL
Package: xmove Severity: minor Version: 2.0beta2-8 File: DEBIAN/shlibs $ wc -l /var/lib/dpkg/info/*.shlibs |sort -n |head -2 0 /var/lib/dpkg/info/xmove.shlibs 1 /var/lib/dpkg/info/apt-utils.shlibs $ ls -ald /var/lib/dpkg/info/xmove.shlibs -rw-r--r-- 1 root root 18 Sep 25 14:18 /var/lib/dpkg/info/xmove.shlibs The file contains the information that it should, but lacks a newline. I recommend ensuring that a newline exists, since some random thing might someday fail and require lots of debugging :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344973: dh_makeshlibs
You can fix the problem by generating the shlibs file dynamically with dh_makeshlibs. You have to call it before dh_shlibdeps for the binaries. (This is untested, but the typical way of doing it now, I gather). -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303651: (no subject)
test -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344978: fetchmailconf: typos an clarifications in helpfile
Package: fetchmailconf Version: 6.2.5.4-1 Severity: minor I see the following in Fetchmail novice configuration help: 5. A polling interval. What are the units? Seconds? Minutes? 6. Options to fetch old messages as well as new, uor to suppress deletion of fetched message. Please s/ uor / or / if thats what is meant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303651: (no subject)
test -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320519: remove gtkhtml3.2 ?
Can gtkhtml3.2 be removed from the archive? Jeroen note that it should be removed soon some 4 months ago, and the 2 pacakges which used to depend on it apparently have moved to a newer version. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344980: please provide an package source filename search
Package: ftp.debian.org, www.debian.org Severity: wishlist File: ftp://debian.org/, http://packages.debian.org, http://www.debian.org/distrib/packages I would find it useful to be able to search the filenames of sources of Debian packages. Something like an Contents-src.sid.tar.bz2 or whatever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#126471: grave bug? chdrv: freezes terminal on startup
Hello Martin, You changed the severity of this bug to 'grave' without any explanation: http://bugs.debian.org/126471 Though I don't know anything about chdrv, I wonder whether this was the wrong bug? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#286929: remove gtkhtml3.0 ?
Can this package be removed, too? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#259324: serious
severity 259324 serious
clone 259324 -1
clone 259324 -2
severity -2 minor
retitle -2 tkrat: typo in ./configure --help output; s/eanbled/enabled/
retitle -1 tkrat: FTBFS missing --with-tcl-include
tag -1 patch
tag 259324 confirmed
thanks
I can trivial reproduce this bug as per the submitters instructions;
this package appears to not meet the policy requirements for
documenting packages' dependencies.
There are lots of valgrind warnings, probably from the underlying tcl
stuff, and it seems that the SEGV is ultimately from a NULL pointer.
Of course, the fix is trivial; add an explicit dependency on tk8.4.
There is also an FTBFS present, fixed by configuring with
--with-tcl-include=/usr/include/tcl8.4.
But then I get:
checking system version (for imap dynamic loading)... ./configure:
line 7109: syntax error near unexpected token `('
There is also a typo:
--with-ssl Enable/disable SSL support (default eanbled)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327049: progress on this bug? -- wwwoffle: Restores removed conffile
Is there any progress on this bug? http://bugs.debian.org/327049 -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340072: progress on this bug? -- xsp: FTBFS: dh_installxsp not found
Is there any progess on this bug? Where is dh_installxsp supposed to come from? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340127: progress on this bug ? -- boo: New version doesn't work
Has there been any progress on this bug? http://bugs.debian.org/340127 -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341247: progress on this bug ? -- beast: overwrite /usr/share/mime/globs
Has there been any progress on this bug? http://bugs.debian.org/341247 -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#277068: upgradable
I can't reproduce this bug, but it would be a 'serious' bug to depend on the existace of a configuration file., which may be removed, and this removal must be preserved by package updates. If slocate depends on the data which it presently assumes is available as /etc/cron.daily.find.notslocate must be provided by slocate or by some package it depends on, for example, as /usr/share/slocate/cron.daily.find. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#282331: old bug on which nobody has commented
severity 282331 minor retitle 282331 slocate uses an ugly filename: /etc/cron.daily.find.notslocate thanks I'm disappointed that nobody has [intentionally] commented on this bug in 13 months. I reported it as a 'normal' severity bug in an attempt to be useful; I thought that perhaps the 'slocate' package had accidentally stored information to a new filename. I thought that reporting this bug might help solve future problems. Now, reading through buglog#277068, I note that the maintainer intends to have that file exist by that name; I'm disappointed that this couldn't have been noted to me, or at least to my bug report long ago. Now I know that it is intentional, my [original] complaint with this file is that its name is ugly. Therefor it is severity 'minor'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#37078: procmail for bugsubscriptions
I'm using the included procmail file for subscribing myself to all bugs for which I am the submitter, or on which I have commented. I see 4 problems: It is implemented on the clientside, and it would IMHO be better if debbugs implemented it (but that is known:). It doesn't track control bot messages. So if I tag a bug, but don't otherwise comment on it, I won't get subscribed. I want to be able to do so. It doesn't subscribe me to bugs that I've commented on in the past. This could be solved by a solution to #293166: bug.debian.org: Provide list of bugs on which I have commented. It might subscribe me multiple times. I don't know if the BTS handles this gracefully. In the worst case, I will get subscribed to a bug for each time I comment on it. In the best case, the BTS will ignore the initial subscribe message from addresses which are already subscribed (or, in the case of an subscribe-this-*other*-address command, that the other address is subscribed), and this will reduce mail traffic. This can probably be fixed by adding an 'grep -w $MATCH ' before sending the messages. -- Clear skies, Justin # This handles the mail Thank you for the problem report ... # And also the mail: Thank you for the additional information ... :0 * ^From: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$ * ^Subject: Bug#\/[0-9]* |echo |mail [EMAIL PROTECTED] # TODO: Subscribe to all bugs I've affected via control bot. # This is difficult because there's not necessarily anything useful to # MATCH in the subject, and matching the body is more complicated than # I want to deal with now. # :0 # * ^To: Justin Pryzby [EMAIL PROTECTED] # * ^From: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$ # * ^Subject: Processed: # |echo |mail [EMAIL PROTECTED] :0 * ^From: [EMAIL PROTECTED] * ^Subject: Please confirm subscription to [EMAIL PROTECTED] * ^Reply-To: \/[EMAIL PROTECTED] |echo |mail $MATCH :0 * ^From: [EMAIL PROTECTED] * ^Subject: Subscription to [EMAIL PROTECTED] successful$ Mail/bug_subscription_success
Bug#272429: reopen
reopen 272429 thanks Surely this bug report about missing fonts wasn't meant to be closed by this changelog entry: - The password database is used instead of $HOME to determine where aptitude's configuration file goes, so people using sudo don't end up with root-owned mode 0700 files in their home directory. (Closes: #272429, #274216, #285334, #272409) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342820: not reproducible for me :
I haven't seen this happen in a long while; I even tried to do it by starting GT 100 times. I guess it would be useful if other people would report if they experience this bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#331690: state of this bug -- cat: /var/lib/xfree86/xorg.conf.md5sum: No such file or directory
Please can someone comment on the state of this bug? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#289011: mozilla-firefox: Fails to update address bar
On Wed, Dec 28, 2005 at 07:31:58PM -0500, Eric Dorland wrote: still seeing this in firefox 1.5? I just upgraded to firefox/sid; I'll watch out for it. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345109: dh-make: please don't ship the conffiles.ex as it exists now
Package: dh-make Version: 0.40 Severity: normal conffiles.ex is confusing to people, since, as of debhelper compat level 3, all files which a package includes in /etc/ are automatically marked as conffiles. Please either document that this is true (and provide examples of strange conffiles files which are not in /etc/: Note that normal conffiles in /etc/ should not be listed here. Only strange and nonconforming conffiles not in /etc/ should be listed here, such as /), or don't ship conffiles.ex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345112: firefox: unnecessary prompts about conffiles after migrating from package 'mozilla-firefox'
Package: firefox
Version: 1.5.dfsg-3
Severity: important
File: ./debian/preinst,
bookmarks.html,
firefox.js,
search.rdf
I just updated to the 'firefox' package available in sid, replacing
'mozilla-firefox' packages in testing to test a bug, as requested by
Eric. I got prompts about conffiles which I should not have gotten,
since I did not modify those files. This is probably caused by the
new package shipping conffiles which were previously owned by the old
package, and failing to provide any preinst foo to handle it.
Please see the examples at http://www.dpkg.org/ConffileHandling. The
goal is to save all our users from having to deal with this prompt,
which will, until fixed, affect sarge to etch upgrades. Remember to
preserve deletion of a conffile.
I can't reproduce this behaviour of causing a .diff after a conffile
is changed in a new package name which conflicts+replaces the old
package, btw.
Included are the files which I saw changed on 2 upgrades.
firefox.tar.bz2
Description: Binary data
BZh91AYSYh?2? FB??? ? `2}? *? [EMAIL
PROTECTED]
[EMAIL PROTECTED]( AT [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]M4OJxS'??i2bh?f??Dz?h???10?S [EMAIL
PROTECTED]
1
[EMAIL PROTECTED][EMAIL PROTECTED]
*K?2h?^??=???a?JP(T???Q)BI\??,IbKP*0RIZ%[$?T?H??7}2EL1Ib?D??)!_?#?% i???J??i=5/???;???al??Ym???Z?.r#??xfh\,????D?9?5='X??? ?i?RA}???[EMAIL
PROTECTED])S?*???Y?yS???I??(?b}?bO??T???K8??FU?Q?3???m?m?V???]??9? ??cZ??a\X7WJ1???UX?PE???J?
??b?IqR?+?'e?k? ??k7?*l?\R?*z???j?J???SU??[
??Y?l??n??S?Ul`fGA-m?ek`?y}??M?_dk??c4?K,uZZDm?M2? ,?^%?35?Q?,?8?YZ1g??L?kE.??85o?[?I?5j9
,om??u??[???R??2??h??n??9C ??=-iY??F ?
0e??E?jgM?Lm[?+m??m??_???y?7???QP~[???7??j*XQ?u????o7???(???Sn???+MEK??W9j?'??`R?)=???S??H?H?Im?
( ??Z?Y?uF?
7aHd?l(?l _?u1?)?##?=???z?{?9??'!qHn Z? #?:?b?II#?Ij?q*a,5???'??$?,4?%K?C??M,i21?MW?o??
???:?
_Jk7?9??U??1?7?JQ??E?DQH??QB}IBm???#e%??69%?z??M???^n-|olT?v?S??.?n?*???Z??9)vL0?J?XZ)yV
??D??J??lX0K?S8???r?4(??i?*???(?4??lN???B???/???Q?? v???i ???q??Q~?\,I'iQD??+Q??? % ??T]r??Q???I ??fS?I,?=???$??K?Z?k?_L/????5J?*??3??q#??}?b?XX ?Y2? ?-.?hX?k??K??S
;?l?=?K!0(m9?c5??*0?5??V?
e ??'???d?^*Q(??I??=v???:???$??Q??L? ??M???9Y??#q??F1Z???\J?Y???7?+Y.'?0?J7??^5S:
$n(]8c??V!?l(?*=?U?h4?AE???p3*m??sA30?L??C?O;??6 W??f?CAYa?Vq???p????n;??K???l ??^,Z??V?F???*??GB?1???,I0??M??mUFE?? ?E?Q?b??ZK???
z???kd???Yt?K???Qb='!?#wt?jr|?i(??+??]??8???M2a6?.[CB?t???j?Lj?;J?7[
(??S?Yy?E*???f??C??7??R$???? ??
I9?G??p 'I?z?
u?gi=kQ*v3???ZN??bs*n??Mjb?fGss?}???i??o?i%?*???b?M_J?1|?;Oa8???x?O9?O1h?O???d?q???3?z?cx?e???}?G???I?9???7 ??N?,?Z?{,?%ICd?t???B?y???J??|*I??V???m1???(??:???z??l???T{?Vl;???C?t?hhLRny??N????(r,O3y^??Mt???4?:5??d9NBTfKM??A?O?Lg??bq??p?b|Y
??=?c+?P?9??z??]m'???T}?
6??e?k?
?e??*I.Tkc9???f???3?0?L?? ?4 ???/??BQ3 ?rh3.#C?V?v?
??R??Q-c?P???J ?zT8\M-???k?D^Vu?]?-O}???K??4??u??zN???Ow??m???KRL?S??G:?a|??
?%??e????q?j9?-rZ??'???Y:?O???r??U?an??v$??/???aq8ec??%o???gZ?
??^u??^l??P?V? m???K?X{M)3??p?XTg0???s?bF??%??+{?Z??????J????e? ???k?q ?T?p2?.\
?d??j?x?
G?j7??i==.???9?,KJ??N??Kf|OVf.?_Ng
2???R??K???* ??5?Mbgo(?0??Z]QB:?R?;?%;?'??.?bSd?2??p(?? ????t
3#?P???l ??O??N3aE??=????X?q?L???e??dVh%??u?\'2?BOq?-0?-{V2C'???%
?LFST?R]Z?/??$??$??\?2?
?L?X??#?v*5?D??s3/D???? ??XI?]C?L??s??Y??X?
(J4XTa??2qAI?'??u?+?$4?u?5;???O?Ae??F)|??`?E.?u?B#???DJ)dR??d?E??. ??{???5??o
R??R?????J??yK?uI}?y?f#f??g?b?q?]d??g??'mn???Z0^*bfS2?FK?,??2O?b5????a^T??$??#?d??)?A\I?Q? ???$??n ?.j3Q?1(?y
? ??bV?`4???Rb1
#?1??h6??0??H? 0q?J
?YZH,T??93?3?F?Y(L??t???/??j???`o?:-?H?G?`???H?3????~
???L?Z_N2f2X?P?%???--o2?g9?j??F P4?#6???10,[EMAIL
PROTECTED]??Xn?LMw???%??j?S?9I?N?ZO1Y?^6???06??XM?XJ???T????I????$?B??Q?r???D?q???}???X~L?g??x '??9??
??r:T?(?;;?(?#d O??0???a?z??h?megq??n??l$??J?????1?t??;
t???'Y1 ?Q??Mg??V???%DY?k#??i???;N?Q??D?.??????i??J?OQ??F?y?J??Nbl??$??d'Y-b=??j?
?O??Or?X??%d~?Ai?Oi?mw???j??|???E???P?B?r?Z|]D?%d?=???_???c'
6?s??_#yY?x?_=p??f?N q??$?fx4? ?k??g???'
??P???'?? ?m???IR???F?d ?J$??bQcTK??c?`Y$?[EMAIL
PROTECTED]( ?L?O???%??v?}E?/H=?bZM?V???UPq?A???I???
c9?????ZZTm4?Q????7I??`8????+P?=?FB????9??XT?'pm?IG?d?(M???Q???K?j:K???|K??
Bug#345113: mysql-server-4.1: conffile prompts during upgrade
Package: mysql-server-4.1
Severity: important
Upgrading from 4.0.24-10sarge1 to 5.0.16-1 I got a large number of
unnecessary conffile prompts. I'm including a tarball of the files
that caused prompting. Actually I'm not sure about the package names
or versions, so I'm also including my dpkg.log fragments.
This might be useful: http://www.dpkg.org/ConffileHandling
firefox and openssh also have this problem.
BZh91AYSY0?\' %? }??? ` ` ?p ?? ? ?hh ?
CCCL?
h?? p ?? ? ?hh ?
CCCL?
h?? 4?#?`L? 0 ??? ?# ?$ ? [EMAIL PROTECTED]xLS'?(=
?d~U?|??%B?? ??z??^?wm?{?%$mb([??~?6??hJT7??]JS???J(???*?'?)R?E?YB???Q,?dYIdgi??/???O?k ?n|
?N 8?K)LF|lq??a?
?
f?cb???n8?:???7?{ ?k?81S?a?E??c??O?~??s]?e?n]???/k+??Y???X?3F{?6C???]g??e)?,???.?UZ??MT?)?VmY?]O#a?{iT???sk
??
??;N?'?v??6i??H??)IvH?
G?R$ZZJ)J*QEJ?R \?U?LN?K?)F???%'???Rmj??a?w?Y??3?M???IF?f???nf?f?c???{?L?2j?S?6??w??K??s.??nG???v6z[?)?j?o??#
???:??_??? C'??`?:S???u75r~7 ???;|+?
YUly ???45I?ojq??JSA???!!w?x?9???? ?hdt?V????UH??l?Wk?e??lzSQ?[??} E?
?t???S??R?9,7)??5??,R??|??YuYO??3??z?4|G%????F?#7[l?h?h??m??fj\???ZroZ)??[s?Y?U
_a?:Y:?t=?d?{q??}??my ?sV?gA???4S??h???f??Gj?S???8b?:??,??}U?0?7 ?t?fSc7??%Q???,?m?wq?? ???8??8??? ,8)??j???nl/R:0???nmYe??)G??pqlS_#7?x^?G]H??qrf;??R??\0???Z2n]??
??G???hqd?v?O'sF?
L??j??M?;[??L???x)??g???l4h?:?=???18?b?{???
?2[r? ?=???g??^?O??w??
?e??Jgl?U??^g2?ZS f?FRdnt6??^?k6oj?.??uuO??$h??3???Hu??%?h?^7R?3u=gk6O?f ??=j4?]??g??:?x ??6N????h ??z?qY?JRO?0? ?C??'?*? ?0aK ?K(??J?2Q,?)r?h? uK?K(s??.?P?
Y7?d?v??^??I?s{??;?;???V??'7??K??Y??=?V??? 0h?6No???)?????}U?RKUJ???-???$0?!??T?Q*?? r/2o???cr?5?[EMAIL
PROTECTED]?Ya?`u2??iN.m???-?K4ld???z???t)??`??R?xWi???|?
'?JHi?#? K+?Tm?4L???T???'????6???qC7?:??G???R?E?6?K5?T?I?An?E0??? ???T?H?J?U%L?ba? O??:\?G??RGd?VT?z?hC?=
?l?O??? `??
??CE?%M?(??E????+?d?:?FIJ+?*U?UTQQ tY??5L?F??yH??I9H??
9ttq???-?R??$E?%ydW ??I:e?i??Hey???
??]i1?Hj?.4??V$kQ??e#??q|?e)E?
??a*DS-??M-x???,?ld???jd?b?#2C)6??T?I?b?TF5?d??4(?d?1???R*C
???
?l??l?f??t? ??B?I?!??%?!v??c?=? g(?)?$n)'H???!u???bag!?}?~8?73|?)??R?Jj??,? ?????G?Q?8??j???C?? ???^g???
a?
7?j??J?co?=qO?G'??S?f~ ???5M???\?;??}/?d?WR,?'??P??E9??K?r??C]
??R9T???i?]??z?? ??h???g???JdnN???{??#?F6su?v??${g???)?6x?,?R???Z?Y???u:n:S???A??sbln?7?6??q??ne???S???L?]?#??'???n -??m{V\? ??b???T??eX??QD
Ir?W???]??J]???O???M?{?r?o!? ??*?Q??]g?sE?S'B6=??e???~d?}7)#(?Tf???O??n???Q?grI?Ig?9?$qn:$??f`?Rh??Z?
?(??N-?doh?(?`??I -Mp?\?? d??2~???
#???$?HN??Q.???d??P???~Q3(O[]?[??Z;? ??{ ?ag?Y?E???Uq!J{
?'? D???E?^E p?Iw|?6???,???h?
T??*j????u(?aL??oB,?bs?RToadN??)P??I??Nh?B???mF?k4Y61? ??
~?czQ??{??5mN/??YK?=?]G??F?mM?a?:??2f5??Wgh?E?t???K ?Y??Ye?Yl?R?b?R??0???VlI:??g????(?f?D??P??,??)?f
T?)??y?O???I?ae???p?n?wZZ??U?k--k*??r|jxpfNFT5HnQ6
I?]?jS?y? 5#j?Qb KC?w#????u? ???+?]K???O[?:'R?a?? ?Z3
?n#?nOC??f?2??? s??.Y?Rw?e?R??8;??` ??Yj??E??E??M?*Q?'??#???JsR??(?Ja?E??'Sp?)?zIag??+
: ~X?hZXawZ]f,???I:7fl6?S
[? ?h????z^V??sbEI??J^KI?R?EH?8 +6Fe
??yb?3DaK???R??I7??Y?I???i-SE??=B???K???u?.a????`JJK?9???2???S
K%??K? D???pu?=m???gA???Fe'?9?#???UU*?U???.??Jap??%E_?D?a:'??? ??H???eG5M,?J!f??:???W???o,???
?r???L[%Z?*???$??d?{?qx?J)Q#???? ??d???I??aJ?+#X6?
f??? ??U.?,?*K?s? ?N+]B?O???u2R??Yk%??M??p?R?NwTj??v 53S??),nS:?d]I?M?d??=??h?6?y?P?Bf??mN??=???)?w???$??E?QPR*1e?x$??R?E'{U??o
?:??Kl,????? v$aS'aJZ,?u?d??,?,??)??4d:?YR*J)rN?M
??u?,???Q?M??l??2Re?1?T?)R?R?y ki??H?Cj??=??6???%?%*M?b??u?ba? ?w??Ro]w???d?c???d????mn???{?oZEKJYL?T?_?S????3]???72L2?K?K?f???t?g?f?0???A???oQM??VjQ:T?dy??+???Yu:V?eI?
??]??j?iY4R?.??1O?J?K=?#k{d???L.?l*JjZ/?J]???q
1v??4]?I??R?J(?b?6?]X? ]?b?
Yb??,???y??8???j??}Z?p?d?s??C??t7? R\?cb?fj?k5OCdd?
?c???N
2QY$
VU+?F??s??m???.???Q??ifMe??S+???^????C?b???8?]x?,?5,??R1???Yh?N-VT??JWy?d??sw?R??t?]?W`???uJR)E?I?}??T?(?EI?B???; c'?nw?0S
7DvH?S?7???a?)Z;??FK7)?????E??u.??xXlx??6M?s{(???j?j??Md?J2Yj???4a??MJ^?%?bK3E??rh??G?P??$FI 5MQr?9?6f??mZ\??LR?2??O??o??w???
??
Bug#335259: ssh conffile prompts
severity 335259 important severity 339978 important merge 335259 3339978 35276 thanks ssh doesn't handle conffiles the right way at all. I'm including a tarball of stuff that failed to work properly while upgrading from 1:3.8.1p1-8.sarge.4 to 1:4.2p1-5, excluding the moduli files, because I don't know if their contents are sensitive.. I think you can do what is necessary with custom MD5 handling as described at: http://www.dpkg.org/ConffileHandling mozilla and mysql also have this problem. ssh.tar.bz2 Description: Binary data
Bug#345114: yasgml: reference and assigment to free variable
Package: yasgml Version: 1.5-7 Severity: important While dist-upgrading, I got the following message during emacs21 postinst: Loading yatexhks... While compiling toplevel forms in file /usr/share/emacs21/site-lisp/yasgml/yasgml.el: ** reference to free variable shell-command-option ** assignment to free variable kanji-fileio-code While compiling yasgml-jump-to-name in file /usr/share/emacs21/site-lisp/yasgml/yasgml.el: ** reference to free variable href While compiling the end of the data in file /usr/share/emacs21/site-lisp/yasgml/yasgml.el: ** The following functions are not known to be defined: set-file-coding-system, YaTeX-typeset Wrote /usr/share/emacs21/site-lisp/yasgml/yasgml.elc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345112: (no subject)
mysql and openssh also have this problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345115: allows me to subscribe myself to a given bug multiple times
Package: bugs.debian.org, lists.debian.org Version: 20051229 Severity: minor b.d.o appears to allow me to subscribe multiple times to a given bug. For its own sake, and for a convenience to myself, it should either check before adding me again, and do nothing if I am already subscribed, or something to the effect of |sort -u. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300760: changelog best practice
I agree with the sentiment which I think Bastian Blank is expressing. It is a documented best-practice to document what change caused each bug to be closed. http://www.us.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-upload-bugfix The idea is that bug reporters will get ample information in the 'close' message, rather than just a note that 'a bug you reported was fixed'. If the bugs were all fixed because of the new upstream release, I would have expected the close entries to be indented below the comment for that release. Furthermore, since you are the upstream author, it should be simple to provide more information. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#37078: bts procmail 2
Included is a second-attempt procmail config file which also handles control bot messages. -- Clear skies, Justin # This handles initial submissions (Thank you for the problem # report...) and also followups (Thank you for the additional # information...). :0 * ^From: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$ * ^Subject: Bug#\/[0-9]* |echo |mail [EMAIL PROTECTED] # This handles bug reports on which I've had an effect via the control # bot. :0 * ^To: Justin Pryzby [EMAIL PROTECTED]$ * ^From: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$ * ^Subject: Processed: |grep -Eo '^Bug#[0-9]+:' |sed -e 's/^Bug#//' -e 's/:$/[EMAIL PROTECTED]/ ' |tr '\n' ',' |sed -e 's/^/To: /' -e 's/,$/\n/' |sendmail -t :0 * ^From: [EMAIL PROTECTED] * ^Subject: Please confirm subscription to [EMAIL PROTECTED] * ^Reply-To: \/[EMAIL PROTECTED] |echo |mail $MATCH :0 * ^From: [EMAIL PROTECTED] * ^Subject: Subscription to [EMAIL PROTECTED] successful$ Mail/bug_subscription_success
Bug#341195: patch not working
On Thu, Dec 29, 2005 at 03:46:26PM +0100, Andreas Barth wrote: # patch doesn't work - sorry tag 341195 - patch Is the problem that we don't understand the mangling, then? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342737: can confirm this bug
I can confirm this behaviour. I tested that the problem can be worked around by encoding ',' as %2b. gaim could do this, although I don't know that it is a gaim bug. I can't see what gaim does to start firefox, though, because gdb isn't playing nicely this morning. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344570: can't reproduce the png crash
I can't actually reproduce the png crash described in #344570 in 1.5.dfsg-3. Am I missing something? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339826: homepage pseudofield
Hello Andreas, I'm still not happy with DevRef WRT the 'homepage' field. #339826: Please discuss Homepage padding more fully It now has: Please make sure that this line matches the regular expression /^ Homepage: [^ ]*$/, as this allows packages.debian.org to parse it correctly. But this is wrong IMO, and should be /^ Homepage: [^ ]*$/. I just checked the CVS and this appears to be a problem with HTML conversion only. I don't know how to fix that problem. But, I'm including a patch which reworks this section, and . Emphasises that this pseudofield is special, and handled specially; . Makes it easier to see the extra indentation; . Stops discouraging people from using the pseudofield, because it will eventually be a real field . Gives a fuller example . Fixes a grammar problem -- Clear skies, Justin --- /tmp/developers-reference.sgml 2005-12-29 20:39:54.0 -0500 +++ /tmp/developers-reference.sgml-new 2005-12-29 20:40:07.0 -0500 @@ -3833,26 +3833,30 @@ We recommend that you add the URL for the package's home page to the package description in filedebian/control/file. This information should be added at the -end of description, using the following format: +end of the long description, using a special format recognized by +filepackages.debian.org/file. You can see an example of how the +homepage will be displayed at +url id=url-eg-desc-upstream-info;. + +A package using this field will have have a Description such as: example . +Description: foo + bar + . Homepage: http://some-project.some-place.org//example -Note the spaces prepending the line, which serves to break the lines -correctly. To see an example of how this displays, see url -id=url-eg-desc-upstream-info;. +Note the spaces prepending the last line. Packages using the Homepage +pseudofield will have filedebian/control/file files which match +the regular expression tt/^ Homepage: [^ ]*$//tt. + p If there is no home page for the software, this should naturally be left out. p Note that we expect this field will eventually be replaced by a proper filedebian/control/file field understood by prgndpkg/prgn and -ttpackages-host;/tt. If you don't want to bother migrating the -home page from the description to this field, you should probably wait -until that is available. - Please make sure that this line matches the regular expression - tt/^ Homepage: [^ ]*$//tt, - as this allows filepackages.debian.org/file to parse it correctly./p +ttpackages-host;/tt./p /sect1 /sect
Bug#342948: sudo security patch
Hello Joey, I was perusing the new queue, and noticed the sudo package there (for reasons unknown). I noticed that it closes bug#342948, and at the end of the buglog, you said: When you've uploaded the sid package, please drop me a line. I assume that an it ends there. What did you mean to say? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345283: mutt: can't see the bottom of some messages
Package: mutt
Version: 1.5.11-4
Severity: normal
Mutt can't see the bottom line of the attached email (To unsubscribe,
send mail to [EMAIL PROTECTED]), I guess because of
the attachment. It should be made visible some{how,where}.
mutt-cant-see-the-unsubscribe-footer.gz
Description: Binary data
Bug#345287: vtgrab: includes /bin/ unnecessarily
Package: vtgrab Version: 0.1.8-2 Severity: minor vtgrab binary .deb unnecessarily includes the /bin/ directory, but no files within it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305355: 100% cpu load on Xorg
On Fri, Dec 30, 2005 at 02:54:01PM -0500, marius mikucionis wrote: I ran into this page, which generates coninuous 100% CPU load in Xorg process: http://www.info-cybernetics.org/citsa2006 (this conference is connected to infamous Systemic proceedings, uncovered by SCIgen paper generator) it is also the case when javascript is turned off. Custom Linux-2.6.14.5 preemptive, Dell Inspiron P4-M 2GHz 1GB RAM. please confirm its firefox-1.5 or Xorg problem, anyone? This is probably because of the rotating title text, right? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344831: DevRef: Please document best practice for submitters testing bugs
On Sat, Dec 31, 2005 at 11:46:44AM +0900, Osamu Aoki wrote: Hi, On Mon, Dec 26, 2005 at 02:01:18PM -0500, Justin Pryzby wrote: Package: developers-reference Severity: wishlist Do you think it would be worthwhile to include some documentation to the following effect, perhaps added to either 5.8.2 or 5.8.3? It is best to close bugs only when the submitter agrees that it should be closed. I do not think this is the standard practice. Closing bug properly with [EMAIL PROTECTED] will send notification to submitter anyway. IF submitter disagrees, bugs can be always reopened. Part of my motivation is from the result of reading apt-listchanges output and finding bugs closed which shouldn't have been closed. Either wrong bugs closed (wrong package even!), bugs not close, bugs closed by not related to upload, etc. Not to mention submitters who are at a new or temporarily-down email address. I'm not sure that the devref edit will help at all, or that it is the right way to go about it. I do not mind stating something alon: The developer should ensure bugs are fixed when closing bug reports. The developer should refrain from closing bug reports when submitter disagrees with reason and should leave them on BTS with the wontfix tag. This doesn't accomplish much of what I want. In case of no reply, I think it is discression of DD to keep or close depending on each situation. Agree. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342737: can confirm this bug
On Sat, Dec 31, 2005 at 12:27:23PM +0100, Mike Hommey wrote:
On Sat, Dec 31, 2005 at 01:59:46AM -0500, Eric Dorland [EMAIL PROTECTED]
wrote:
tags 342737 confirmed
thanks
* Justin Pryzby ([EMAIL PROTECTED]) wrote:
I can confirm this behaviour.
I tested that the problem can be worked around by encoding ',' as
%2b. gaim could do this, although I don't know that it is a gaim
bug.
I can't see what gaim does to start firefox, though, because gdb isn't
playing nicely this morning.
I guess it depends on whether a , is allowed to be unencoded in a
url.
What does your desktop/gnome/url-handlers/http/command gconf key say ?
If you're talking to me, and if you mean
/etc/gconf/gconf.xml.defaults/desktop/gnome/url-handlers/http/%gconf.xml,
then it is attached.
BTW my www-browser is presently set to lynx ('xterm -e lynx ' or
whatever) for some reason, since I installed some other browsers last
week, and then removed them.
--
Clear skies,
Justin
%gconf.xml
Description: application/xml
Bug#37078: bts procmail attempt 3
Third attempt, which includes a necessary To: condition which avoids being subscribed to packages and its newly submitted bugs, (which isn't so much a problem except when other people submit lots of bugs). -- Clear skies, Justin # This handles initial submissions (Thank you for the problem # report...) and also followups (Thank you for the additional # information...). :0 * ^To: Justin Pryzby [EMAIL PROTECTED]$ * ^From: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$ * ^Subject: Bug#\/[0-9]* |echo |mail [EMAIL PROTECTED] # This handles bug reports on which I've had an effect via the control # bot. The 'To:' condition is necessary, otherwise I'd occasionally # be subscribed to a massive number of bugs when Don reassigns from # debbugs to bugs.d.o, or Eric from mozilla-firefox to firefox, and # I'm already subscribed to those packages anyway.. :0 * ^To: Justin Pryzby [EMAIL PROTECTED]$ * ^From: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$ * ^Subject: Processed: |grep -Eo '^Bug#[0-9]+:' |sed -e 's/^Bug#//' -e 's/:$/[EMAIL PROTECTED]/ ' |tr '\n' ',' |sed -e 's/^/To: /' -e 's/,$/\n/' |sendmail -t :0 * ^From: [EMAIL PROTECTED] * ^Subject: Please confirm subscription to [EMAIL PROTECTED] * ^Reply-To: \/[EMAIL PROTECTED] |echo |mail $MATCH :0 * ^From: [EMAIL PROTECTED] * ^Subject: Subscription to [EMAIL PROTECTED] successful$ Mail/bug_subscription_success
Bug#342737: can confirm this bug
clone 342737 -1 reassign -1 libgnomevfs2-common retitle -1 libgnomevfs2-common: initial http handler should be generic browser command, and not 'epiphany' thanks On Sat, Dec 31, 2005 at 03:33:12PM +0100, Mike Hommey wrote: On Sat, Dec 31, 2005 at 08:09:12AM -0500, Justin Pryzby [EMAIL PROTECTED] wrote: On Sat, Dec 31, 2005 at 12:27:23PM +0100, Mike Hommey wrote: On Sat, Dec 31, 2005 at 01:59:46AM -0500, Eric Dorland [EMAIL PROTECTED] wrote: tags 342737 confirmed thanks * Justin Pryzby ([EMAIL PROTECTED]) wrote: I can confirm this behaviour. I tested that the problem can be worked around by encoding ',' as %2b. gaim could do this, although I don't know that it is a gaim bug. I can't see what gaim does to start firefox, though, because gdb isn't playing nicely this morning. I guess it depends on whether a , is allowed to be unencoded in a url. What does your desktop/gnome/url-handlers/http/command gconf key say ? If you're talking to me, and if you mean /etc/gconf/gconf.xml.defaults/desktop/gnome/url-handlers/http/%gconf.xml, then it is attached. Can you give me the output for the command: gconftool-2 -g /desktop/gnome/url-handlers/http/command It is: epiphany %s I'd be interested by Eric's too. Because I can't reproduce the bug, with both firefox %s and firefox %s as a value there, and the default value for a brand new gnome user is epiphany %s, while I don't even have epiphany installed. Nor I, though it is one of the ones I installed and removed last week: pn epiphany none (no description available) pn epiphany-brows none (no description available) pn epiphany-brows none (no description available) pn epiphany-exten none (no description available) I think I'm going to file a bug on libgnomevfs2-common for that it should be sensible-browser %s (or maybe x-www-browser)... I guess so. But that isn't the cause of the gaim/firefox problem, right? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278990: firefox: adds a buggy entry to /etc/mailcap (needs a wrapper to copy the file)
On Sat, Dec 31, 2005 at 04:33:24PM +0100, Vincent Lefevre wrote: retitle 278990 firefox: adds a buggy entry to /etc/mailcap (needs a wrapper to copy the file) thanks On 2005-12-31 10:11:39 -0500, Justin Pryzby wrote: This problem still exists, so this bug report should remain open, however cloned, reassigned, retitled, blocked, or tagged. If the file should be copied, so that mutt doesn't remove or zero it, then let us implement that as necessary in mailcap or some wrapper thereof. OK, I didn't think you were refering to the system mailcap. Indeed, I have here: text/html; /usr/bin/firefox '%s'; description=HTML Text; test=test -n $DISPLAY; nametemplate=%s.html text/xml; /usr/bin/firefox '%s'; description=XML Text; test=test -n $DISPLAY; nametemplate=%s.xml which is not correct (as my previous mail explained). The bug title should now clearly say what the bug is. But IMHO, the wrapper should be generic and be provided by Mutt. Something like: text/html; /usr/bin/view-attach /usr/bin/firefox '%s'; description=HTML Text; test=test -n $DISPLAY; nametemplate=%s.html where view-attach would do the copy, call the command and unlink the file. Firefox should also have an option so that the command quits whether Firefox was already running or not. Yes, as you knew, wrapper is actually wrappee. Is the problem specific to mozilla, or are there other things that will have this problem, that may or may not already have bugs filed against them? (I'm trying to do hurry and do my good deed for 2005 by anticipating possible bugs). -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345445: bugs.debian.org: please don't bold forwarded-to links
I agree with this. -- Clear skies, Justin On Sat, Dec 31, 2005 at 04:54:14PM +0100, Thijs Kinkhorst wrote: Package: bugs.debian.org Severity: wishlist The titles of bugs are bolded links. However, if you mark a bug as forwarded to some http-location (eg an upstream bts), you get two bolded, long links for the same bug entry on the overview page. That makes the section Forwarded Bugs very noisy. Example: http://bugs.debian.org/squirrelmail the forwarded wishlist items section is very busy with all those long bold links. I'd suggest to give the forwarded-to information the same colour and weight as the 'package' and 'reported by' links: normal weight and gray-coloured. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345459: vim-common: mishighlights /etc/fstab line with NFS
Package: vim-common Version: 1:6.4-006+1 Severity: minor 192.168.1.2:/home/pryzbyj/share/a-b /mnt/cetus nfs defaults,users,noauto 0 0 ^ ^ ^ cetus.homeunix.net:/home/pryzbyj /mnt/cetus nfs defaults,users,noauto 0 0 ^^^ These parts are highlighted in red, even though this line works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345460: nfs-kernel-server: Please provide an example in /etc/exports
Package: nfs-kernel-server Version: 1:1.0.7-3 Severity: wishlist File: /etc/exports Please add an example line to /etc/exports, in addition to the reference to exports(5). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278990: firefox: adds a buggy entry to /etc/mailcap (needs a wrapper to copy the file)
On Sat, Dec 31, 2005 at 06:53:07PM +0100, Vincent Lefevre wrote: On 2005-12-31 11:14:42 -0500, Justin Pryzby wrote: Is the problem specific to mozilla, or are there other things that will have this problem, that may or may not already have bugs filed against them? I don't know. I'd say that applications that make sure that one instance is run are in the same case. Perhaps OpenOffice? Do you know how I can get a list of all potential entries there? I guess it is (typically?) updated by dh_installmime, right? /usr/bin/see /usr/bin/edit /usr/bin/compose /usr/bin/print Can those be the wrapper/wrappee or whatever? Should all programs just call one of those? Do they? I just saw Colin's response to your ssh bug btw :-P -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345464: devscripts: Please provide an 'alert' service for my moreinfo bugs
Package: devscripts Version: 2.9.10 Severity: wishlist Please provide an 'alert'er service which tells me about my bugs which are tagged 'moreinfo'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342737: this is a gaim bug Re: Bug#342737: can confirm this bug
On Sun, Jan 01, 2006 at 07:51:59PM +0100, Mike Hommey wrote:
On Sun, Jan 01, 2006 at 01:22:53PM -0500, Justin Pryzby [EMAIL PROTECTED]
wrote:
reassign 342737 gaim
tag 342737 upstream
retitle 342737 gaim: Interfacing with browsers with netscape-style -remote
option requires URL encoding any commas in the URLs
clone 342737 -1
retitle -1 gaim: outputs quot to stdout rather than a quote
severity -1 minor
thanks
On Sat, Dec 31, 2005 at 11:24:37PM +0100, Mike Hommey wrote:
On Sat, Dec 31, 2005 at 09:42:18AM -0500, Justin Pryzby [EMAIL
PROTECTED] wrote:
On Sat, Dec 31, 2005 at 03:33:12PM +0100, Mike Hommey wrote:
(...)
I think I'm going to file a bug on libgnomevfs2-common for that it
should be sensible-browser %s (or maybe x-www-browser)...
I guess so.
But that isn't the cause of the gaim/firefox problem, right?
Mm... that means your gaim doesn't do the same as mine...
I don't understand what you mean here, but I don't think it matters
now, right?
Could you attach here a trace of what gaim does when you try to open an
url ? (strace -f -p `pidof gaim`)
The relevant bit follows:
write(1, gtknotify: Executing firefox -a firefox -remote
quot;openURL(http://www.wired.com/news/politics/0,1283,69773,00.html,new-tab)quot;\n,
133) = 133
access(~/bin//firefox, X_OK) = -1 ENOENT (No such file or
directory)
access(~/src/src/bin//firefox, X_OK) = -1 ENOENT (No such file or
directory)
access(/usr/local/bin/firefox, X_OK) = -1 ENOENT (No such file or
directory)
access(/usr/bin/firefox, X_OK)= 0
getuid32() = 1000
stat64(/usr/bin/firefox, {st_dev=makedev(3, 1), st_ino=286295,
st_mode=S_IFREG|0755, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=16, st_size=7153, st_at
ime=2005/12/28-19:51:31, st_mtime=2005/12/24-05:06:31,
st_ctime=2005/12/28-19:52:00}) = 0
pipe([16, 18]) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb74bd708) = 15349
which has:
execve(/usr/bin/firefox, [firefox, -a, firefox, -remote,
openURL(http://www.wired.com/news/politics/0,1283,69773,00.html,new-tab)],
[EMAIL PROTECTED]) = 0
So this looks like a gaim bug; caused by firefox interpretting the substring
following the first comma as an option/parameter to the openURL function.
FWIW, it's not at all necessary with the wrapper scripts for both
mozilla and firefox (and since firefox 1.5, even the wrapper script
doesn't need to use the remote interface).
So, changing the code to only run firefox or mozilla with the url as
argument would be pretty straightforward.
Can you do {new,existing}-{tab,window} with that interface?
--
Clear skies,
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
