Bug#291194: dpkg should handle tar posix format
On Wednesday, January 19, 2005 1:38 PM, Samuel Thibault
<[EMAIL PROTECTED]> wrote:
> Scott James Remnant, le mer 19 jan 2005 11:35:51 +, a dit :
>> On Wed, 2005-01-19 at 12:02 +0100, Samuel Thibault wrote:
>>
>>> So as to have proper file name encoding, I'm used to have
>>> TAR_OPTIONS=--format=posix
>>> But then built packages don't work:
>>>
>> I think this is a dup of the above bug. If that patch doesn't work,
>> please unmerge these bugs.
>
> It doesn't. Doing some gdb showed me that the first tar entry has
> h.Type 'x', which is unknown. Here is the printing of the first
> header: (gdb) p *(TarHeader *)block
> $10 = {Name = "./PaxHeaders.28427/.", '\0' ,
GNU tar indeed does not understand `x' (or any other lower-case letter) as a
valid file type. See the thread starting at
http://lists.debian.org/debian-devel/2004/04/msg01376.html for a fuller
discussion.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291355: Fwd: Re: Bug#291355: gaim-gnome: installation fails, depends on uninstalable libpanel-applet0
> - Forwarded message from julian <[EMAIL PROTECTED]> - [...] >> gaim-gnome was discontinuted starting with the 0.60 release, we >> (upstream) removed the gnome code from gaim. as a result, it would >> only be installable on a woody system at this point. >> >> > Shouldn't then gaim-gnome be removed from list of avalaible packages > for > sid? It isn't in said list, as http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&version =all&exact=1&keywords=gaim-gnome will show. In fact, there have been no gaim-gnome packages in unstable for nearly two years. They were removed on 19 February 2003. Either the submitter has stable sources in their sources.list, or is using a very badly broken mirror. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341149: Cannot search contents of testing AMD64 packages on package search.
On Monday, November 28, 2005 6:36 PM, Joshua Gilbert <[EMAIL PROTECTED]> wrote: > Package: www.debian.org > Severity: important > > The following is using the search box at: > http://www.us.debian.org/distrib/packages#search_contents > > Search for anything with AMD64 as the architecture and testing as the > distribution. I haven't found any string that yields a result. As far as I can see, this is due to the fact that the contents file for testing/AMD64 is currently empty - see http://amd64.debian.net/debian-amd64/dists/testing/Contents-amd64.gz. There is a a "Contents-amd64.gz.new" at the same location, but that's not publicly readable. This looks like it needs fixing by the ftpmasters of the AMD64 archive, so I've cc:ed them. Cheers, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341243: 2 of 3 security.debian.org mirrors are missing /debian-non-US/
On Tuesday, November 29, 2005 2:27 PM, Wolfram Schlich <[EMAIL PROTECTED]> wrote: > Package: security.debian.org > > /debian-non-US/ can only be found on one of the three > security.debian.org mirror servers: [...] > Is that by design?! There's no reason at all why any security.d.o mirror needs to contain a folder which isn't part of the security infrastructure. 194.109.137.218 is klecker.debian.org, a.k.a. non-us.debian.org, which is the only reason it *does* possess that folder. (Aside from which, non-US is depracated as of the Sarge release, and will disappear as of Etch). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#224125: obsolete key creates security and nonus Release.gpg
On Mon, 2003-12-15 at 23:07 -0700, Andre Lehovich wrote: > Package: security.debian.org > > The Release.gpg files in the security and nonus archives are > still being created using the old automatic signing GPG key: > http://ftp-master.debian.org/ziyi_key_2003.asc > not the new key > http://ftp-master.debian.org/ziyi_key_2003v2.asc > > Presumably a new key wouldn't have been issued if the old > key could still be trusted, hence this bug report. The current Release.gpg files in the security archive are signed by a current key, specifically: pub 1024D/4F368D5D 2005-01-31 [expires: 2006-01-31] Key fingerprint = 4C7A 8E5E 9454 FE3F AE1E 78AD F1D5 3D8C 4F36 8D5D uid Debian Archive Automatic Signing Key (2005) <[EMAIL PROTECTED]> The Release.gpg files in the non-US archive appear to be signed by both the 2004 and 2005 keys; I'm assuming these won't be updated further due to the deprecation of non-US. On the basis of the above, this report should imho be closed. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#222213: rsync access and security.debian.org
On Wed, 2003-11-26 at 10:08 +0200, Oskar Pearson wrote: > Package: security.debian.org > > Hi there > > I used to mirror security.debian.org via rsync, but since the > recent security compromise, the config appears to have changed. > > It seems that rsync is no longer enabled on that machine. [...] > As per the previous bug, the rsync module used to be named > "debian-security". rsync is currently enabled on all of the machines that comprise the security.d.o cluster: [EMAIL PROTECTED]:~$ for h in $(dig +short security.debian.org); do printf "$h: "; rsync $h:: | egrep debian-security; done 128.101.80.133: debian-security Debian Security FTP Archive 194.109.137.218: debian-securityDebian security archive 82.94.249.158: debian-security Debian security archive Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341568: Please mention [EMAIL PROTECTED]
Package: developers-reference Tags: patch Hi, http://lists.debian.org/debian-devel/2005/01/msg01651.html and the surrounding thread suggests that [EMAIL PROTECTED] is the appropriate address to use if one suspects a maintainer is MIA, as opposed to [EMAIL PROTECTED] The attached patch applies this change to the MIA section of the dev-ref. Regards, Adam dev-ref-mia.diff Description: Binary data
Bug#342237: apt: where is the archive keyring? not /usr/share/keyrings/debian-archive-keyring.gpg
reassign 342237 debian-keyring severity 342237 wishlist retitle 342237 Please provide Debian archive keyring merge 342237 316344 thanks mateOn Tuesday, December 06, 2005 1:30 PM, Sean Finney <[EMAIL PROTECTED]> wrote: > Package: apt > Version: 0.6.43 > Severity: normal > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > copelandia[~]14:24:26$ sudo apt-key update > ERROR: Can't find the archive-keyring > Is the debian-keyring package installed? The key is intended to become part of the debian-keyring package, but isn't yet. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316344;msg=15 for example. Reasssigning and merging with the above report. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344060: /usr/bin/apt-get: Doesn't recognize need to update vulnerable kernel
On Mon, 2005-12-19 at 12:25 -0600, Tim Christian wrote: > Package: apt > Version: 0.5.28.6 > Severity: important > File: /usr/bin/apt-get > > > I was using (via `dpk -l`): kernel-image-2.4.27-1-38 2.4.27-6 > > I noticed the following security alert: > http://www.debian.org/security/2005/dsa-921 > > Therefore, I issued: apt-get update && apt-get upgrade > The update did not recognize that I needed to update the kernel. Indeed not, nor should it have. kernel-image-2.4.27-1-686 is an entirely different package from kernel-image-2.4.27-2-686. (The difference in the package names exists for a reason and one does not necessarily want to automatically upgrade a kernel to one with a different module abi). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344158: The FHS is from 2000 and should be updated
package debian-policy
severity 344158 wishlist
merge 344158 230217
thanks
On Tuesday, December 20, 2005 2:17 PM, Michelle Konzack
<[EMAIL PROTECTED]> wrote:
> Package: debian-policy
> Version: 3.6.1.1
> Severity: normal
>
> Error description:
>
> The Filesystem Hierarchy Standard in
>
> /usr/share/doc/debian-policy/fhs/fhs.html/
>
> should be updated to reflect the major changes to /sys, /srv, /media
The expanded version in that folder is indeed an older version (2.1).
/usr/share/doc/debian-policy/fhs-2.3.{html,pdf.gz,ps.gz,txt.gz} however are,
as their name suggests, version 2.3 of the standard, which is current.
The most likely reason for this arrangement is that Policy currently
requires adherence to version 2.1. There are already bugs open requesting
this to be updated, so I'm merging this.
Regards,
Adam
--
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
Hi, On Mon, 2005-09-26 at 21:22 +0200, Peter Eisentraut wrote: > Package: bugs.debian.org > Severity: normal > > This is concerning bug #329597. [...] > 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. Not 100% intuitive, but found 329597 found 329597 1.0.0.007-2.dfsg-2sarge1 should achieve what you want. (See http://www.debian.org/Bugs/server-control) Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347381: RM: kgeography -- geography learning tool
Steffen Joeris wrote, Wednesday, January 11, 2006 9:20 AM > On Wednesday 11 January 2006 01:33, Adeodato Simó wrote: >> * Steffen Joeris [Tue, 10 Jan 2006 13:50:21 +0100]: >> > Package: ftp.debian.org >> > Severity: serious >> > >> > Please remove this package because the provided binary now >> > exists in kdeedu from kde 3.5 which is now in unstable. >> >> Heh, where did you get the idea that this needed a bug against >> ftp.d.o (bogus documentation somewhere?), and at such high severity? >Aehm I asked some other DD's (because I also had no idea against which > package to fill the bug) and they told me that ftp.debian.org is the ToDo-list > for the ftp-masters. Sorry if it was wrong. Source packages are semi-automatically removed once they are no longer responsible for building any binary package present in the archive. Bugs are only normally necessary if for some reason the new package doesn't entirely replace the old (e.g. the old package built the binaries for an architecture that the new package doesn't). > I set the priority to serious, because in unstable are two kgeography > binaries, but I think one of the ftp-master corrected it. Not an ftp-master, but yeah. ;-) Bug severities have no effect on the order in which ftp.d.o bugs are dealt with, so filing them as anything other than normal or wishlist is largely pointless. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347540: GPG error on update: public key not available
reassign 347540 apt severity 347540 serious merge 347540 345891 thanks On Wednesday, January 11, 2006 12:08 PM, jetxee <[EMAIL PROTECTED]> wrote: > Package: ftp.debian.org > > As of Wed Jan 11 12:58:48 CET 2006, I get the following error messages > on aptutude update: > > W: GPG error: ftp://ftp.it.debian.org testing Release: The following > signatures couldn't be verified because the public key is not > available: NO_PUBKEY 010908312D230C5F [...] > I failed to found a contemporary report on this subject in BTS, so > post a new one. That's because you're looking in the wrong place. :-) This is http://bugs.debian.org/345891 against apt and those merged with it. Merging this report also. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347923: lists.d.o: the purpose of the debian-testing list
On Friday, January 13, 2006 3:12 PM, Justin Pryzby <[EMAIL PROTECTED]> wrote: > Package: lists.debian.org > Severity: normal > > What is the purpose of this list? > > I know that I'm not sure myself, but I know that it isn't supposed to > be for discussion of random bugs that people find, which are almost > always already known, and sometimes fixed. > [...] > If my understanding is correct, I propose the following "short > description" for d-t: > > Owner of the upgrade-reports pseudo-package providing an archive of > new bugs The long description was actually updated for roughly this reason last May, to remove "testing individual packages" (http://cvs.debian.org/webwml/english/MailingLists/desc/user/debian-testing? root=webwml&r1=1.4&r2=1.5). As I understand it, the purpose of the list is to find issues with "testing" relating to upgrading to it from stable or trying to install it afresh (as this would obviously be required to work once testing became stable). Cheers, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344980: please provide an package source filename search
reassign 344980 apt-utils retitle 344980 'Please provide a means for generating Contents files for source packages' thanks On Wed, 2005-12-28 at 00:53 -0500, Justin Pryzby wrote: > 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. ftp.d.o currently uses apt-ftparchive to generate the packages / sources / contents lists, so I'm reassigning the request to apt-utils. Cheers, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#272127: remove freecdb
On Sat, 2005-12-31 at 06:00 -0500, Nathanael Nerode wrote: > Jeroen van Wolffelaar wrote: [...] > > cvm, mailfront and vpopmail are not migrated yet, so it hasn't been done > > yet. I only checked cvm, and on that package, there isn't even a bug > > filed requesting it to be migrated. > > > > What's up? > > Oops, missed some. :-P Finding reverse build-depends (when there are > no "Depends") is annoyingly difficult. Got a script which does it > efficiently and accurately? :-PCause I'd really like one. It should be fairly trivial for a single distribution and architecture, given an appropriate deb-src line in sources.list (extending beyond a single distribution would require some further work on the apt-cache invocation), viz: #!/bin/sh BINPKGS="($(apt-cache showsrc $1 | egrep "^Binary:" | cut -d" " -f2- | \ sed -e 's/, /|/g'))" grep-dctrl -sPackage -e -FBuild-Depends "$BINPKGS" \ /var/lib/apt/lists/*_Sources | sort -g | uniq and pass it a source package name. Extending it to cope with binary package names isn't particularly difficult. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345671: xbase-clients: [startx] uses non-POSIX statements (/bin/bash)
package xbase-clients severity 345671 normal merge 345671 345446 thanks On Mon, 2006-01-02 at 19:55 +0200, Jari Aalto wrote: > Package: xbase-clients > Version: 6.9.0.dfsg.1-1 > Severity: serious > > The new /usr/X11R6/bin/startx script contains statement that is > is not /bin/sh compatible. I use /bin/sh => /bin/dash and the > script fails to start. The only problem with the line is the fact that a $ was missed out accidentally; this has already been reported as 345446 a few days ago, and is already fixed in SVN. $(()) for shell arithmetic is perfectly POSIX complaint. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345883: Please allow usertags to be set when bug is submitted
reassign 345883 bugs.debian.org merge 345883 327591 thanks Hi, > Package: debbugs > Severity: wishlist > Please allow usertags to be set when a bug is submitted. This would > really help those of us that need to track rc-type bugs for non-rc archs > with usertags. A similar request has already been filed against the bugs.d.o pseudo-package; reassigning and merging. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345984: lsb: Allow package to be built on sarge
Package: lsb Version: 3.0-13 Severity: wishlist Tags: patch Hi, The attached patch allows lsb to be built on a sarge system, and at least lsb-base to be installed correctly on sarge (tested on i386). Obviously lsb-core will be uninstallable without more work by the backporter due to the glibc dependency. The patch is based on the example in http://lists.debian.org/debian-devel-announce/2005/06/msg00010.html; fwiw, that post also states that the appropriate version of dpkg-dev to depend on for the new DEB_* variables is 1.13.5, not 1.13.2. Regards, Adam lsb_sarge.diff Description: Binary data
Bug#346002: apt: GPG error when updating
# BTS control commands package apt # Raising severities as per the rationale in #345891 severity 346002 serious severity 345823 serious severity 345956 serious merge 346002 345823 345956 345891 thanks On Wed, 2006-01-04 at 20:25 +0100, Ferenczi Viktor wrote: > Package: apt > Version: 0.6.43 > Severity: normal > > > I got an unusal GPG error when updating with apt-get update: [...] > W: GPG error: http://ftp.us.debian.org unstable Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 010908312D230C5F This is the same issue as reported in #345891 and the two bugs I've just merged with it (see above). Merging this report and the other three. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336887: exim: massive parrallel delevery attemts should be handled better
On Tue, 2005-11-01 at 10:26 -0800, Blars Blarson wrote: > Package: exim > Severity: wishlist > > spohr.debian.org aka bugs.debian.org gets a lot of spam. Sometimes > spammers try to send large ammounts of spam at once from many > locations. spohr is currently suffering such an attack, with over > 18000 processes (almost all exim or exim3) and a load average of 64, > but still with 20% idle time. No mail is getting delivered. This > situation is an unintentional greylisting. Eventually the processes > time out and things get back to our normal 100,000 spams/day to filter > out a few hunderd non-spams from. (This has happended before.) > > What I would like to see is limits to how many exim processes run and > faster recovery when this type of DDOS attack happens. Since I don't > use exim, I don't know if it can be tuned better. Spohr is currently > running sarge, and the problem happend when it was running woody. fwiw, upstream development on exim 3 (i.e. the version represented by the "exim" package) stopped over three years ago and the codebase is not going to get any further changes. However, a quick look through the 3.30 documentation gives the following, which may be of use (from http://www.exim.org/exim-html-3.30/doc/html/spec_11.html#IDX897): Since Exim has no central queue manager, there is no way of controlling the total number of simultaneous deliveries if the configuration allows a delivery attempt as soon as a message is received. If you want to control the total number of deliveries on the system, you need to set the queue_only option, which ensures that all incoming messages are simply added to the queue. Then set up an Exim daemon to start queue runner processes at appropriate intervals (probably fairly often, for example, every minute), and limit the total number of queue runners by setting the queue_run_max parameter. Because each queue runner delivers only one message at a time, the maximum number of deliveries that can then take place at once is queue_run_max multiplied by remote_max_parallel. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312848: exim4: Install created conf.d jungle even when asking for monolithic conf
On Friday, June 10, 2005 2:35 PM, Heikki Levanto <[EMAIL PROTECTED]> wrote: > Package: exim4 > Version: 4.50-8 > Severity: normal > > When installing exim4 over an old exim installation - just after > upgrading to sarge, it asked if I wanted to have a monolithic config > file, or a set of smaller ones. I chose a monolithic one, but the > install still created a lot of small directories in /etc/exim4/conf.d To be precise you are asked if you want to *use* the smaller files. It is not possible to only install conf.d/* in some circumstances, as they are dpkg conffiles and shipped as part of the default exim4-config package. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314187: lintian: incorrect warning about useless-call-to-update-menus
package lintian
retitle 314187 Please update menu checks to use /usr/share/menu
thanks
On Wednesday, June 15, 2005 6:22 AM, Wesley J. Landaker <[EMAIL PROTECTED]>
wrote:
> Package: lintian
> Version: 1.23.8
> Severity: normal
>
> When I run lintian on one of my packages, it gives me warnings about
> useless calls to update-menus.
[...]
> Well, the warning is kind of right, I don't have a menu file in
> /usr/lib/menu. But, that is because in Debian Policy section 3.1, it
> says they should go in /usr/share/menu, which is where it is:
[...]
> Is this some new check added to lintian on purpose? It contradicts
> current Debian policy...
Section 3.1 of Debian Policy is "The package name". I'm assuming you mean
section 3.1 of http://www.nl.debian.org/doc/packaging-manuals/menu.html/
("Debian Menu System"), which *isn't* policy.
That document appears to have last been updated three days ago. At the end
of March, the text in question read
Packages provided menu files should be in `/usr/lib/menu/'.
System-local menu files should be in `/etc/menu/'. User-specific menu
files should be in `~/.menu/'
so, afaics, no this isn't "some new check added to lintian on purpose" and
it *doesn't* contradict Policy. What's happened is that the menu maintainers
have changed their recommendations as to where menu files should be placed.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310633: exim4-daemon-heavy: av_scanner permission error with clamav
On Tue, 2005-05-24 at 15:18 -0600, tom morgan wrote: > Package: exim4-daemon-heavy > Version: 4.50-4 > Severity: important > > i apologize if this is tied to the wrong package. it's hard to tell if > it is an exim4 bug or a clamav bug. based on the solution given below, > i selected this one. > > after enabling the av_scanner directive in exim4, using clamav, we > started receiving the following error: [...] > the solution is to add the user clamav to the group Debian-exim . as > such, i am suggesting that clamav be added to group Debian-exim as part > of the exim4 install/configuration. This has previously been suggested a number of times against the clamav package, as bug #250335 and the three others merged with it. For this reason, /usr/share/doc/clamav-base/README.Debian.gz contains details of how to integrate Clamav with sendmail, exim4 and Amavis. IMHO, adding users to groups created by other packages isn't something unrelated packages should be doing - even less so when one the vast majority of new sarge and sid systems will be running exim4 but may never be running clamav (or may have clamav added later, since exim4 will be installed by the installer). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310750: Conflicts with alsa-base
On Wed, 2005-05-25 at 19:26 +0200, Jacobo wrote:
Subject: Bug#310750: Conflicts with alsa-base
> Package: exim4-config
Erm...? :-)
> I guess exim4-config should depend on exim4-base, shouldn't it?
No, it shouldn't. It's entirely possible to (want to) install an
exim4-config package on a machine that doesn't run exim4 - for instance
in order to examine the configuration before upgrading the machine to
the exim4 packages using that configuration.
exim4-base correctly depends on a package providing one of the virtual
packages exim4-config{,-2}. The requirement is that installing exim4
ensures that an appropriate configuration is installed, not vice versa.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311386: Severity of 311386 is normal
# Missing smilies and buddy graphics doesn't constitute "breaks the whole system" package gaim severity 311386 normal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#305192: [CONFFILE][TRIVIAL] dpkg allow overwrite files by default
On Monday, April 18, 2005 4:07 PM, Olleg Samoylov <[EMAIL PROTECTED]> wrote: > Default dpkg.conf include force-overwrite. This is improper. All > "force" options must be setted by admin explicitly. > > Severity is grave because this can lead to significant data lost in > unstable distrib. For instance, package ia32libs version 1.1 in amd64 > distr suddenly overwrite many /bin/* files from coreutils. This is only the case on the first install of the dpkg package, when the package is being configured. Since d-i does not use dpkg to install dpkg, the postinst is never called with --configure, and as such an install using d-i will not create the file. > Also add /etc/dpkg/dpkg.cfg as conf file instead of copy in > dpkg.postinst. > It is strange to see such vilolation package packing in package dpkg. Policy does not require that /etc/dpkg/dpkg.cfg be a confile. The file is only copied in postinst if dpkg was not previously installed, and the file does not already exist. This is by design, so that the installer can modify the contents of the file if required. Since the file is never modified by the maintainer scripts after the initial install, local modifications are respected, and there is no need for it to be flagged as a conffile. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309435: gaim: Vulnerabilities in sarge version
package gaim tags 309435 + pending thanks Javier Fernández-Sanguino Peña wrote, Tuesday, May 17, 2005 8:57 AM > This is just a reminder that there are known vulnerabilities in > gaim 1.2.1 in sarge that need to be fixed in the release process > either through t-p-u or by allowing 1.3.0 in to sarge: > From http://gaim.sourceforge.net/security/index.php: > > - MSN Remote DoS, CAN-2005-1262 > - Remote crash on some protocols, CAN-2005-1261 Joey Hess uploaded 1:1.2.1-1.1 to t-p-u yesterday. See http://lists.debian.org/debian-release/2005/05/msg01024.html Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309790: dpkg: [Emacs] compiling *.el files shoudl display errors, not just log file name
package dpkg reassign 309790 emacs-goodies-el thanks On Thu, 2005-05-19 at 18:21 +0300, Jari Aalto wrote: > Package: dpkg > Version: 1.10.27 > Severity: normal > > Recent install of dpkg-dev-el reads: [...] > Setting up debian-el (24.10-1) ... > install/debian-el: Handling emacs21, logged in /tmp/elc_oXqYUf.log > install/debian-el: Handling xemacs21, logged in /tmp/elc_dzTAtg.log > > However, this is not enough. dpkg _should_ display all Emacs Lisp > compiler warnings if there were any during making the *.elc files. > Now the user does not know form this output if all went ok or not. Neither dpkg-dev-el nor debian-el are provided by dpkg. dpkg knows nothing about Emacs Lisp, yet alone its compiler warnings. Reassigning to emacs-goodies-el, which is where both packages come from. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292857: clamav-daemon: PAckage description 'suggests' refers to non-existing 'lha'
On Sun, 2005-01-30 at 18:32 +0200, Jari Aalto wrote: > Package: clamav-daemon > Version: 0.80-7 > Severity: minor > > During installation, following messages are displayed: [...] > Suggested packages: > unrar lha clamav-docs daemon libcurl3-gssapi ca-certificates [...] > However, there is no package 'lha'. There *is*. It's in non-free, which is fine as clamav only suggests it, and does not depend on it. > You may want update the "Recommends". s/Recommends/Suggests/. Either way, see above. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292759: shell script sniplets in /usr/bin?
On Sun, 2005-01-30 at 17:18 +0100, Goswin von Brederlow wrote:
> Matthew Palmer <[EMAIL PROTECTED]> writes:
[...]
> > "Because I don't wanna play by the rules!" is not a rationale. So you have
> > to specify a path -- so what? The way things stand at the moment, if I were
> > to drop a gettext.sh in my ~/bin (which is quite likely, except that I don't
> > like to put a .sh on my helper scripts) your shell scripts would suddenly go
> > tits-up in a most unpleasant fashion. Personally, *that* would be enough to
> > make me want to hardcode the path.
[...]
> That is why you normaly have ~/bin last in PATH.
Not if you're using Debian's default install of bash you don't
(admittedly they're commented out by default, but...):
# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ] ; then
PATH=~/bin:"${PATH}"
fi
More to the point, putting ~/bin last in PATH breaks most of the reasons
for having it there in the first place (being able to override
system-installed versions).
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292857: [Fwd: Mail delivery failed: returning message to sender]
Submitter's e-mail appears to be broken. Grrr. Forwarded Message From: Mail Delivery System <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender Date: Sun, 30 Jan 2005 12:23:37 -0500 This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mailer after RCPT TO:<[EMAIL PROTECTED]>: host cante.net [81.197.3.110]: 550 unknown user -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292925: clamav-daemon: [manual] clarify allowed values in LogFileMaxSize
On Monday, January 31, 2005 7:38 AM, Jari Aalto <[EMAIL PROTECTED]> wrote: [...] > Manual page reads: [...] > However, the parameter "SIZE" is ambigous. It the default value in > bytes? Does it allow all formats like nK, nM where N is any value > (with fractions like 1.12M). Please clarify accepted values and their > notations. It's not at all ambiguous. If you read the top of the page, there's a section headed "FILE FORMAT", which specifies *exactly* what "SIZE" means, and how it can be specified. IMHO, this bug should be closed due to user error, but I'll leave that to the maintainer's discretion. Regards, Adam (Fully expecting this to bounce) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293845: Syntax error in dpkg-preconfigure
reassign 293845 debconf
severity 293845 grave
close 293845
merge 293845 293666
thanks
On Sun, 2005-02-06 at 11:27 +0100, Thue Janus Kristensen wrote:
> Package: dpkg
> Version: 1.10.26
> Severity: important
>
> When running apt-get upgrade I got this output. Note the syntax error
> right after fetching the packages. They seemed to install ok, but I
> don't really feel safe ignoring this...
[...]
> Get:2 http://ftp.acc.umu.se unstable/main debconf 1.4.45 [102kB]
[...]
> String found where operator expected at /usr/sbin/dpkg-preconfigure line 96,
> near "die sprintf(gettext(""
> (Might be a runaway multi-line "" string starting on line 94)
> (Missing semicolon on previous line?)
This isn't a dpkg bug, as dpkg-reconfigure isn't part of dpkg.
[EMAIL PROTECTED]:~$ dpkg -S /usr/sbin/dpkg-reconfigure
debconf: /usr/sbin/dpkg-reconfigure
This was also fixed yesterday in debconf 1.4.44. Based on the above
output, you've already got a debconf package containing the fix
installed.
Reassigning this to debconf, closing and merging with the other reports.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294098: String found where operator expected at /usr/sbin/dpkg-preconfigure
reassign 294098 debconf
severity 294098 grave
close 294098
merge 294098 293666
thanks
On Mon, 2005-02-07 at 21:48 +0100, Nils R Grotnes wrote:
> Package: dpkg
> Severity: normal
>
>
> After updating the system with Synaptic, the terminal output screen contained
> this error message:
>
>
> String found where operator expected at /usr/sbin/dpkg-preconfigure line 96,
> near "die sprintf(gettext(""
> (Might be a runaway multi-line "" string starting on line 94)
> (Missing semicolon on previous line?)
This isn't a dpkg bug, as dpkg-reconfigure isn't part of dpkg.
[EMAIL PROTECTED]:~$ dpkg -S /usr/sbin/dpkg-reconfigure
debconf: /usr/sbin/dpkg-reconfigure
This was also fixed over the weekend in debconf 1.4.44. As long as
you've got at least that version on the system then the error shouldn't
occur again.
Reassigning this to debconf, closing and merging with the other reports.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308450: startx -nolisten works only on :0
package xbase-clients close 308448 thanks On Tuesday, May 10, 2005 10:12 AM Anton <[EMAIL PROTECTED]> wrote: > Package: xbase-clients > Version: 4.3.0.dfsg.1-12.0.1 > > !!![OOps. Typo in previous mail...]!! Please don't open a new bug report just to correct a typo. Closing the first report with this message. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308478: passwd: Allowable characters in user/group names regex broken
Package: passwd Version: 4.0.3-33 Severity: critical Tags: sid Justification: Breaks unrelated software (exim4 plus others) Hi, Between -32 and -33, a chunk of code from libmisc/chkname.c:good_name() was moved in to 406_good_name.dpatch. Unfortunately, that file is currently commented out in debian/patches/00list, and the patch is therefore not applied. This leads to an inability to install exim4, as the user/group name "Debian-exim4" does not match upstream's regex ([a-z_][a-z0-9_-]*). For example: Adding system-user for exim (v4) groupadd: Debian-exim is a not a valid group name groupdel: group Debian-exim does not exist dpkg: error processing exim4-config (--configure): subprocess post-installation script returned error exit status 1 Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#315063: clamav-freshclam: logrotate fails when freshclam is not running as daemon
package clamav-freshclam tags 315063 + sarge thanks Hi, On Monday, June 20, 2005 12:14 PM, Anders Henke <[EMAIL PROTECTED]> wrote: > Package: clamav-freshclam > Version: 0.84-2 > > No, this is no dupe to #315042 :-) It /is/, however, a dupe of #308153 > The postrotate script in /etc/logrotate.d/clamav-freshclam contains > a line > > [ -f /var/run/clamav/freshclam.pid ] && kill -HUP `cat > /var/run/clamav/freshclam.pid` This was fixed in 0.85-1, which unfortunately didn't make it in to sarge. Backported packages are available from http://volatile.debian.net/debian-volatile/ Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#316155: Exim4 queue runner loops infinitely on MX without IP address
package exim4-daemon-heavy tags 316155 - sarge thanks On Tue, 2005-06-28 at 22:09 +0200, Stefan Hornburg wrote: > package: exim4-daemon-heavy > version: 4.50-5 > severity: important > tags: sarge sarge contains 4.50-8 > Note > > This might be critical bug (DoS), please escalate if necessary. > At least this should be resolved for next Sarge point release. This bug is not present in the version of exim4 contained in sarge, so there is nothing to be resolved in sarge > Justification > > On of my servers Exim4 claimed the CPU on queue running. This problem > has been described and confirmed on Exim users list: > > http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20050404/msg00071.html > > Removing the patch for #296492 apparently resolved the problem. Indeed, and this was exactly what was done in 4.50-6, which was uploaded over two months ago: * The upstream fix for #296492 sometimes causes an endless loop. Update patch with correction from Philip's commit, revision 1.10. (mh) Please upgrade to the version of the packages present in sarge. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#316166: clamav-base: preconfiguration errors
On Wednesday, June 29, 2005 4:12 PM, Lior Kaplan <[EMAIL PROTECTED]> wrote: >>> When upgrading to clamav-base I got these errors: Can't exec >>> "/tmp/clamav-base.config.47861": Permission denied at >>> /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of >>> /tmp/clamav-base.config.47861 configure 0.86-1 failed at >>> /usr/share/perl5/Debconf/ConfModule.pm line 44 >> Is /tmp mounted noexec? > Yes. I thought of that after I reported the bug. > > I know not every user use it, but any change to have a fix which > doesn't means mounting tmp without noexec? The errors are being caused by debconf, not clamav itself. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89797 (there are others, but that seems the most useful) Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#316406: dpkg-dev : can not open fakeroot
On Friday, July 01, 2005 6:03 AM, Christian Perrier <[EMAIL PROTECTED]> wrote: [...] > I also got some strange things happening while building packages. > > Running "debuild" just keeps nothign visible happening. > > Running "fakeroot dpkg-buildpackage" drops me in a shellExiting > from that shell starts the build process: [...] > I'm not sure that the right package to assign this is dpkgprobably > better assign this to fakeroot. That sounds like #316307, which was fixed in fakeroot 1.4.1 Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#319014: spamassassin should properly handle unicode garbage
package spamassassin merge 319014 291093 thanks Adrian von Bidder wrote, Tuesday, July 19, 2005 9:19 AM [...] > Occasionally, I see in my log: > == > Parsing of undecoded UTF-8 will give garbage when decoding entities > at /usr/share/perl5/Mail/SpamAssassin/HTML.pm line 182, line 105. > == > (1) this is probably some minor bug in HTML handling. AFAICT spamassassin More specifically, it's #291093 and #306496 in Debian's BTS and #4046 in upstream bugzilla. Merging with the previous reports. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320014: ClamAV library heap overflows
package clamav merge 320014 319898 thanks On Tuesday, July 26, 2005 1:47 PM, Oliver Paulus <[EMAIL PROTECTED]> wrote: > Package: clamav > Version: 0.86.1-2 > Severity: critical > > clamav <= 0.86.1 has several heap overflows. "At least 4 of its file This has already been reported as #319898, so I'm merging the reports (the original was filed less than 24 hours ago). ftp-master is still down, so uploads of updated packages are currently impossible. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#147564: queue run: process 2090 crashed with signal 11 while delivering 179Oiq-0000Vr-00
package exim tags 147564 + upstream wontfix thanks Hi, On Mon, 2002-05-20 at 20:06 +0200, Holger von Rhein wrote: > Package: exim > Version: 3.35-1 > > # /usr/sbin/exim -qf > 2002-05-20 19:50:14 queue run: process 2532 crashed with signal 11 while > delivering 179Oiq-Vr-00 Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#191805: exim: be more specific about "Delivery attempts will continue for some time"
package exim tags 191805 + upstream wontfix thanks Hi, On Sun, 2003-05-04 at 03:35 +0800, Dan Jacobson wrote: > Here in offline land, one queues some mail, but before connecting the > modem, we instead go out to play, turning off the computer and turning > it back on 36 hours later. We then see: [...] > Mail> No action is required on your part. Delivery attempts will continue for > Mail> some time, and this warning may be repeated at intervals if the message [...] > Anyway, in today's computer world, "some time" is not good enough, > especially when coming from a computer, not a human. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#190647: exim: not clear what machine the reject message is coming from
package exim tags 190647 + upstream wontfix thanks On Thu, 2003-04-24 at 13:58 +0800, Dan Jacobson wrote: > Examining the message body a user sees: [...] > It is not entirely clear just what machine produced the message. > > Why not say "by mail delivery software (Exim) on [machine name]" Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#179151: exim: Cannot bind to IPv6 link-local addresses
package exim tags 179151 + upstream wontfix thanks On Sun, 2003-02-02 at 13:06 +0100, Lionel Elie Mamane wrote: > On Sun, Feb 02, 2003 at 11:06:13AM +, Mark Baker wrote: [...] > > I agree, this is an upstream issue. I'll wait to see whether there's > > a response before I do anything. [...] > > The response may be that your patch looks correct but that there won't be > > another new version of exim 3.xx, in which case I'll include your patch in > > the next debian release. > > Upstream didn't comment about my patch, but indeed said exim3 is > frozen: > > Philip Hazel wrote: > > Exim 3 is frozen. All new development is happening in Exim 4, which > has been out for almost a year now. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is not going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#259857: exim: fallback_hosts fails if retry time is not reached on original hosts list
package exim tags 259857 + wontfix thanks Hi, On Fri, 2004-07-16 at 19:12 -0400, Tyson Whitehead wrote: > Package: exim > Version: 3.36-11 > Severity: normal > > I've configured my machine to deliver it's own mail if possible, and if > not to fall back on the organizations smtp server. [...] > I'm not sure, but I think the problem is that the fallback hosts for > the smtp transport is not used unless the retry time has been reached > for some of the original hosts (i.e. a bit of missed/bad logic around > the retry time host database and the fallback host for the smtp > transport). Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#224024: exim: /etc/init.d/exim doesn't start exim in the background
package exim tags 224024 + unreproducible thanks Hi, On Mon, 2003-12-15 at 21:10 +, Mark Baker wrote: > Lothar Hegebart wrote: > > >as the init-script starts the process in the foreground the whole > >apt-get upgrade came to a halt > > > > > I can't reproduce this at all: > > dailuaine:~>sudo /etc/init.d/exim start > Starting MTA: exim. > dailuaine:~> You reported this bug against exim over 18 months ago. The maintainer could not reproduce the report at the time, no-one has reported a similar problem since, and I cannot reproduce the issue with any version of the exim packages currently in the Debian archive. Are you still able to reproduce this? If you cannot confirm that the problem still occurs, I propose to close this bug on or after August 27th. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#222068: exim: application bug: exim(429) has SIGCHLD set to SIG_IGN but calls wait().
package exim tags 222068 + upstream wontfix thanks Hi, On Tue, 2003-11-25 at 14:49 +0100, Piotr Roszatycki wrote: > Exim produces a lot of messages. I.e.: > > Nov 25 13:35:12 szafir kernel: application bug: exim(24490) has SIGCHLD > set to SIG_IGN but calls wait(). [...] > This is because exim sets SIG_IGN on SIGCHLD signal and this is error > for Linux kernel. [...] > http://www.exim.org/pipermail/exim-users/Week-of-Mon-20030414/052632.html Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#238673: -bs and -d options are incompatible ; should be said somewhere in doc or manpage
package exim tags 238673 + upstream wontfix thanks Hi, On Thu, 2004-03-18 at 12:15 +0100, [EMAIL PROTECTED] wrote: > Package: exim > Version: 3.36-9.1 [...] > This is not really a "bug", but I think it should be forwarded to the > mainstream author to state somewhere the incompatibilities between -bs > and -d options. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#198356: eximon: a
package exim tags 198356 + upstream wontfix thanks On Sun, 2003-06-22 at 04:43 +0800, Dan Jacobson wrote: > the screen is broken into 3 windows, but they seem to lack titles, > (like log, queue) > > in the log window one can hold down the down arrow an enter into > whitespace for no good reason, instead of stopping at the last line of > data. > > we see the four control buttons are split onto two lines. If they were > on one line we could save screen space. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#201046: exim: blank line added to bounces?
package exim tags 201046 + upstream wontfix thanks Hi, On Sun, 2003-07-13 at 02:36 +0800, Dan Jacobson wrote: [...] > when exim says > -- This is a copy of the message, including all the headers. -- > on bounces, one notices a blank line added to the beginning and end of > messages. Well, I suppose there are no standards for that[?], but some > news readers, e.g. gnus, seem to at least think the trailing blank > line was part of the original message. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#173599: exim: can't tell which smtp auth method was used
package exim tags 173599 + wontfix thanks On Wednesday, December 18, 2002 1:38 AM, Dan Jacobson <[EMAIL PROTECTED]> wrote: > Package: exim > Version: 3.36-3 > Severity: wishlist > Tags: upstream > > In the standard logs we don't see which of the three smtp methods at > the bottom of exim.conf was actually used. This seems like something > to mention in the logs without requiring more than current debug info levels. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#172435: exim: mailq should think in terms of hours and minutes
package exim tags 172435 + wontfix thanks On Monday, December 09, 2002 11:03 PM, Dan Jacobson <[EMAIL PROTECTED]> wrote: > $ mailq > 2h 468 18LU9M-Sv-00 <[EMAIL PROTECTED]> > [EMAIL PROTECTED] > > 76m 440 18LUkv-aj-00 <[EMAIL PROTECTED]> > [EMAIL PROTECTED] > > 70m 1.4K 18LUqT-bN-00 <[EMAIL PROTECTED]> > [EMAIL PROTECTED] > D [EMAIL PROTECTED] > > 0m 1.2K 18LVwY-h8-00 <[EMAIL PROTECTED]> > [EMAIL PROTECTED] > > Odd, I would put the cut off point for beginning to show hours at > 60m. Apparently it is perhaps 100m. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#162362: exim: Info page index troubled links
package exim tags 162362 + upstream wontfix thanks On Wednesday, September 25, 2002 10:02 PM, Dan Jacobson <[EMAIL PROTECTED]> wrote: > Package: exim > Version: 3.35-1 > Severity: minor > > In the exim Info page index, some of these: > * alias errors: Errors in alias files. > * alias file: <1>: The aliasfile director. > * alias file:: Options common to the > aliasfile and forwardfile directors. > * alias file: backslash in: Types of alias item. > * alias file: building <1>: -bi. > ... > > are linked to the wrong thing or cause errors upon hitting RET Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#150026: exim dies with sig 11
package exim tags 150026 + upstream wontfix thanks On Friday, June 14, 2002 6:29 PM, Jörg Sommer <[EMAIL PROTECTED]> wrote: > some queue runner dies with sig 11. I checked the ram, but there isn't > anything. I run ltrace with exim and it seams, the crash happens > evertime at the same location. I append the ltrace output and my > config files. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#130467: exim: mangles newlines on headers of incoming mail
package exim tags 130467 + upstream wontfix thanks On Tuesday, January 22, 2002 10:31 PM, Dagfinn Ilmari Mannsåker <[EMAIL PROTECTED]> wrote: > On incoming mail the headers generated by exim have only LF newlines, > while > the rest of the headers have CRLF. This causes mutt and other programs > (such as vim) to interpret the file as having LF newlines, and thus > displaying annoying ^M characters. local->local mail only has LF > newlines. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#145585: sendmail uses -N ... -R ... for DSN; but exim's -N ==do *not* deliver
package exim tags 145585 + upstream wontfix thanks On Thursday, May 02, 2002 6:28 PM, Wolfgang Weisselberg <[EMAIL PROTECTED]> wrote: > Problem: sendmail uses -N -R to set DSN. This is > reflected in mutt, which will use -N if dsn_notify is set. > > However exim will not deliver messages if any "-N" flag appears in the > command line. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#129025: general: exim crash with sig11 while getservbyname
package exim tags 129025 + upstream wontfix thanks On Sunday, January 13, 2002 3:19 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > in exim-3.33/src/transports/smtp.c, line 1889: > > struct servent *smtp_service = getservbyname(ob->service, "tcp"); > > does a crash with signal 11 on my installation, i dunno but > /etc/services > seems correct and if i use the following, it works: > > /* */ the whole else statement and use: > port = (int)htons(25); > > to get the smtp port statically Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#148633: exim: eximstats idea
package exim tags 148633 + upstream wontfix thanks On Friday, May 31, 2002 9:26 AM, Paul Johnson <[EMAIL PROTECTED]> wrote: > Package: exim > Version: 3.35-1 > Severity: wishlist > > For us spamfighters out there, it would be kinda cool if we could get > eximstats to parse rejectlogs and give us stats on which RBL blocked > how much mail. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#111646: Segfault during mail delivery
package exim tags 111646 + upstream wontfix thanks On Saturday, September 08, 2001 12:32 AM, Nick Holgate <[EMAIL PROTECTED]> wrote: > Package: exim > Version: 3.32-2 & 3.31-1 > Severity: critical > > Arch: m68k > Kernel: 2.2.19 & 2.4.9 > Libc6: 2.2.3-9 & 2.2.4-1 > > After installing either of the above versions of exim all mail fails > to get delivered. Running the queue by hand exhibits a signal 11 error. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#129562: exim: doesn't handle non-RFC-compliant SMTP AUTHdeclaration in response to EHLO
package exim tags 129562 + upstream wontfix thanks On Wednesday, January 16, 2002 8:43 PM, Mauricio Julio Fernández Pradier <[EMAIL PROTECTED]> wrote: > Several major MTAs (such as qmail) use a non-standard SMTP AUTH > supported method declaration in response to a EHLO command. This Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#107506: Default Exim Configuration Can Be Black-Holed by ORBS
On Thursday, August 02, 2001 6:29 PM, Evan Prodromou <[EMAIL PROTECTED]> wrote: > [NOTE: this bug is not about USING black hole services. It is about > being PUT ON black hole lists.] > > Installing exim with the default configuration will make the server > fail the tests used for ORBS blackhole lists (and derivative lists). > This can mean that the server will be blackholed by large ISPs and > other servers, which will prevent mail from being delivered. As noted in t -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#112500: eximon: Spool window not clearing
package exim tags 112500 + upstream wontfix thanks On Monday, September 17, 2001 3:22 AM, Justin Keene <[EMAIL PROTECTED]> wrote: > Package: eximon > Version: 3.32-2 > Severity: important > > Whenever the spool window updates (manually or automatically) it > appends the items in the spool to the end of list instead of > replacing the current list. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#102385: exim: infinite loop of "Message frozen" messages
package exim tags 102385 + upstream wontfix thanks On Tuesday, June 26, 2001 6:39 PM, Adam M. Costello <[EMAIL PROTECTED]> wrote: > When exim fails to deliver a message to postmaster, it probably > shouldn't report the failure by sending another message to > postmaster... > I just cleaned several thousand "Message frozen" messages out of my > mailbox and /var/spool/exim/. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#85898: exim: verify_sender should be able to do VRFY on smarthosts
package exim tags 85898 + upstream wontfix thanks On Wednesday, February 14, 2001 1:38 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > There's currently no way for a node that has a single smart host as > its router to verify sender addresses correctly without duplicating > the configuration of the smart host. What we need is a way of getting > -bv to send VRFY's to remote_smtp transports to verify the > sender/recipient addresses. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#83000: exim feature: accept/reject mail based on externalprogram
package exim tags 83000 + upstream wontfix thanks On Sunday, January 21, 2001 3:27 AM, Brian White <[EMAIL PROTECTED]> wrote: > I think it would be very beneficial to be able to extend exim's > incoming mail handling abilities by having it able to reject a > message based on > the results of an exernal program call. This would allow the easy > addition of more agressive spam filters, virus checkers, and more. Upstream development on exim 3 stopped over three years ago, and it is no longer Debian's default MTA. The behaviour discussed in this bug report is never going to change / be fixed in the Debian packages, so I'm tagging the report to indicate that. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#135881: tasksel: file server task description is wrong
Hi, On Tue, 2002-02-26 at 11:51 -0500, Joey Hess wrote: > Sebastian Rittau wrote: > > The tasksel description of the file server task is wrong: It mentions > > that it would install Netatalk (for Macs), but it doesn't. So, please > > either fix the description or add the package "netatalk". > > Tasksel does include netatalk in the task, but it looks like packages in > non-us do not get a Task: header added to them by the overrides. I think > aj must have forgotten to install that stuff there. I have pinged him > about this Is this bug still relevant, given that non-us has been obsoleted with the Sarge release and netatalk has moved in to main since it was reported? Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#315348: Bug 315348: ftp.debian.org: intltool-debian size mismatch
Hi, On Tue, 2005-06-21 at 19:21 -0700, Kevin Dalley wrote: > Package: ftp.debian.org > Severity: grave > Justification: renders package unusable > > > intltool-debian has a size mismatch on ftp.debian.org. Here's the > error message. > > > Failed to fetch > http://ftp.debian.org/debian/pool/main/i/intltool-debian/intltool-debian_0.30+20040213_all.deb > Size mismatch This looks like a configuration error on your side (or at least somewhere between you and ftp.d.o) on the basis that - it works fine here (and presumably for everyone else who hasn't reported a bug) - ftp.debian.org is 128.101.80.133 and 208.185.25.35 [EMAIL PROTECTED]:~$ wget -q -O- \ http://128.101.80.133/debian/dists/testing/main/binary-i386/Packages | \ egrep -A10 '^Package: intltool-debian' | egrep '^(Version|Size)' Version: 0.30+20040213 Size: 23514 (the result being identical across both servers, and both testing and unstable package lists) and [EMAIL PROTECTED]:~$ wget -S http://128.101.80.133/debian/pool/main/i/intltool-debian/intltool-debian_0.30+20040213_all.deb 2>&1 | egrep '(Content-Length| saved )' 7 Content-Length: 23514 20:32:29 (41.47 KB/s) - `intltool-debian_0.30+20040213_all.deb' saved [23514/23514] As far as I can see, everything matches (at least today :-) Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#313294: dists/etch does not contain Contents-*.gz files
On Wed, 2005-06-15 at 02:41 +0200, Jeroen van Wolffelaar wrote: > On Mon, Jun 13, 2005 at 12:30:26AM +0200, Adeodato Sim?? wrote: > > AFAICS, there are no Contents-$(ARCH).gz files in the archive for the > > etch distribution. As these have been provided in the past for the > > testing distribution, and other tools rely on them (apt-file, perhaps > > packages.debian.org), it'd be nice to make them available. > > > > I told Jeroen about this on IRC, and he recommended that I filed a > > wishlist bug report. > > Beats me why this isn't happening. The apt.conf that we use > (/org/ftp.debian.org/katie/apt.conf, copy on merkel) seems to correctly > enable this for testing (etch) too. It doesn't happen though. Judging from http://ftp.debian.org/dists/etch/ all of the architectures' Contents files have been regenerated in the past week. Assuming they weren't processed manually, is it safe to assume that everything is now working ok? Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311794: Removal request for agrep on m68k
On Fri, 2005-06-03 at 14:02 +0200, Daniel Baumann wrote: > Package: ftp.debian.org > Severity: wishlist > Title: Removal request for agrep on m68k > > Since there is no buildd for m68k, I request the removal of agrep in > that very architecture. [There are no buildds for non-free at all, for the same reasons that the packages are in non-free] According to http://packages.debian.org/agrep/ there are currently no m68k agrep packages in the archive, in any distribution. Thus, it would be impossible to remove them. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248600: Contents file for woody does not contain non-US anymore
On Thu, 2004-05-13 at 10:17 +0200, Martin Schulze wrote: [...] > James Troup wrote: > > Martin Schulze <[EMAIL PROTECTED]> writes: [...] > > > It seems that the Contents-$arch.gz file for woody does not contain > > > non-US anymore. > > > > It never did? [...] > Well, if it never did, it's a wishlist bug at most... Given that non-US has now been obsoleted, is it reasonable to assume that this will never be implemented? Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#229306: ftp.debian.org: Remove boot-floppies
On Sat, 2004-01-24 at 11:36 +, Colin Watson wrote: [...] > Please make sure that this situation is corrected first: > > boot-floppies | 3.0.22 |stable | source > boot-floppies | 3.0.23 | unstable | source > > [EMAIL PROTECTED]:~$ ls -l ftp/dists/stable/main/disks-*/current > lrwxrwxrwx1 archvsyn archvsyn 17 Jun 20 2003 > ftp/dists/stable/main/disks-alpha/current -> 3.0.23-2002-05-21 [...] > Otherwise removing boot-floppies from unstable will mean that we'll be > shipping boot-floppies in woody without corresponding source. Bug > #225704 is also open about this. Is it still possible to do this, other than by waiting for etch to be released, and therefore for woody to be removed from the archive? (I have no idea whether there's any non-painful way to update oldstable, and oldstable still obviously has the "matching source" requirement). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#125992: Closing old NMUed bug reports
package exim close 126181 close 125992 thanks Hi, Both of these bugs were fixed in an NMU nearly four years ago, and are therefore currently open and tagged fixed. Given that they were fixed upstream in 3.34 and the oldest version of exim in the archive is 3.35, they can now be safely closed. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318353: libglu1-xorg-dev: Should not depend on any C++ libraries
On Friday, July 15, 2005 10:09 AM, Keenan Pepper <[EMAIL PROTECTED]> wrote: > Subject: libglu1-xorg-dev: Should not depend on any C++ libraries > Followup-For: Bug #318353 > Package: libglu1-xorg-dev > > libglu1-xorg-dev currently depends on libstdc++6-dev; submitter of > this bug suggested it should depend on libstdc++6-4.0-dev, but IMHO it > should not depend on any C++ libraries because the GLU library can be > used from plain C. It should probably recommend or suggest > libstdc++6-4.0-dev, but not depend on it. More specifically, the dependency is unneeded - this is already known by the packagers. build-essential's dependencies will always ensure that the correct version on libstdc++-dev is installed. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303130: exim4-daemon-heavy: exim4 "forgets" emails in /var/spool/exim4/scan, leaving emails undelivered without notice
On Tuesday, April 05, 2005 7:19 AM, Marc Haber <[EMAIL PROTECTED]> wrote: > On Tue, Apr 05, 2005 at 12:58:47AM +0200, Sebastian Hegler wrote: >> Lately, I found lots of undelivered emails in /var/spool/exim4/scan. > > /var/spool/exim4/scan is not used by the Debian exim4 packages. I > seriously suspect a local configuration error. That directory is used by exiscan to unpack files in to when the demime acl condition is used (I assume also the decode condition in the MIME ACL). The usual cause of files remaining there is a crashed or terminated instance of exim/ClamAV/spamassassin which hasn't been able to tidy up after itself. [...] >> Could also somebody please help me to get the stuck messages >> delivered? Thanks in advance! > > Something in the line of exim4 -qff -DSPOOL_DIR=/var/spool/exim4/scan > should do the trick. Sadly that's unlikely to work, as the directory contains a series of .eml files containing the mails being scanned, together with their attachments in individual files, rather than an exim format spool directory. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303553: Spamassassin initd script fails to stop spamd
On Thursday, April 07, 2005 1:52 PM, Lars Roland <[EMAIL PROTECTED]> wrote: > When running spamassassin with the following options (in > /etc/default/spamasssassin) > > OPTIONS="-d -x -u qmailq --socketpath=/var/run/spamd -m10 -s null" > > then I cannot use the Debian init script to stop spamd as it reports > that spamd is not running although it is already up (it should be > noted that running spamd as the user qmailq has no effect on this bug, > you can run it as any user and the behaviour will be the same). The > following example shows the problem: [...] > I have noticed this bug in spamasssissin in Sarge and Sid. It is not > immediately clear to me how to solve this bug, but one idea would be > to use pidof in the init script to check if the program is really > running. I suspect you're falling foul of the qmailq user being unable to read/write the PID file. Solving the bug simply involves either giving the user r/w access to the existing file, or moving it somewhere the user already has r/w access. By the way, /etc/default/spamassassin includes the following, which should have been a rather large hint ;-) --- quote from /e/d/spamassassin # Pid file # Where should spamd write its PID to file? If you use the -u or # --username option above, this needs to be writable by that user. # Otherwise, the init script will not be able to shut spamd down. PIDFILE="/var/run/spamd.pid" --- end quote from /e/d/spamassassin Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303581: gaim my be crashed remotely: CAN-2005-0965 CAN-2005-0966
tags - sid thanks On Thursday, April 07, 2005 4:29 PM, Helge Kreutzmann <[EMAIL PROTECTED]> wrote: > Unfortunately the CAN-pages are not yet present, the summary on > http://lwn.net/Articles/130537/ > > seems to indicate, that "only" a DOS is possible, if indeed > information *from* the user can be extracted, than please raise the > priority. > > If you've fixed them in 1:1.2.1-1 or earlier please remove the sid-tag > (and maybe add a CAN in an later upload). According to http://gaim.sourceforge.net/security/ CAN-2005-096[5-7] were all fixed in upstream's 1.2.1 release; settings tags appropriately. (fwiw, as far as I can see 1:1.2.1-1 should be entering sarge in the next couple of days, rendering this as a woody-only issue). The changelog for 1:1.2.1-1 says * New upstream version. Fixes IRC escaping remote DOS problems, hence medium priority. which I would assume is a reference to CAN-2005-0966 Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#304244: freepops: Uses incorrect domain names for UK variants
Package: freepops
Version: 0.0.24-1
Severity: normal
Tags: patch
Hi,
/etc/freepops/config.lua contains two entries for domains ending in
".com.uk". There is no such second-level domain; attempting to use the
domains in their correct form fails. The patch below supplies the
correct domain names.
Regards,
Adam
--- /etc/freepops/config.lua2005-04-07 19:30:31.0 +0100
+++ config.lua 2005-04-11 22:25:20.0 +0100
@@ -55,7 +55,7 @@
freepops.MODULES_MAP["yahoo.ca"] = {name="yahoo.lua"}
freepops.MODULES_MAP["yahoo.co.in"]= {name="yahoo.lua"}
freepops.MODULES_MAP["yahoo.com.tw"] = {name="yahoo.lua"}
-freepops.MODULES_MAP["yahoo.com.uk"] = {name="yahoo.lua"}
+freepops.MODULES_MAP["yahoo.co.uk"]= {name="yahoo.lua"}
freepops.MODULES_MAP["yahoo.com.cn"] = {name="yahoo.lua"}
freepops.MODULES_MAP["yahoo.es"] = {name="yahoo.lua"}
@@ -81,7 +81,7 @@
freepops.MODULES_MAP["aol.com.pr"] = {name="aol.lua"}
freepops.MODULES_MAP["aol.com.br"] = {name="aol.lua"}
freepops.MODULES_MAP["jp.aol.com"] = {name="aol.lua"}
-freepops.MODULES_MAP["aol.com.uk"] = {name="aol.lua"}
+freepops.MODULES_MAP["aol.co.uk"] = {name="aol.lua"}
freepops.MODULES_MAP["aol.ca"] = {name="aol.lua"}
freepops.MODULES_MAP["aola.com"] = {name="aol.lua"}
freepops.MODULES_MAP["netscape.net"]= {name="aol.lua"}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#330701: locales: LANG from /etc/environment is not chosen, always LANG= and POSIX
reassign 330701 libpam-modules close 330701 0.79-2 merge 330701 330458 thanks Hi, On Thursday, September 29, 2005 12:47 PM, Luca Capello <[EMAIL PROTECTED]> wrote: [...] > I don't know exactly since when (I upgrade my Debian unstable every > morning and anyway since no more than a week), but now the LANG > variable is no more set (and so the locales): This isn't a bug in locales, but in libpam-modules. The fixed package has already been uploaded, and should hit mirrors tonight. Reassigning, merging with the earlier reports and closing. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#330701:
Hi, On Thursday, September 29, 2005 3:36 PM, Michael Setzer <[EMAIL PROTECTED]> wrote: [...] > This means that you have to add something like > > [EMAIL PROTECTED] > > to your /etc/security/pam_env.conf and everything should work again as > usual. That's a workaround, not a solution. The correct solution is to upgrade to the fixed version of libpam-modules - the package that caused the problem - which should hit mirrors tonight (0.79-2) > Maybe this issue should be reflected in the next version of the > locales package so that the pam_env.conf file will be upgraded > properly by any `dpkg-reconfigure locales`. No. locales shouldn't, and more to the point *can't*, touch pam_env.conf, as it belongs to an entirely different package. [EMAIL PROTECTED]:~$ dpkg -S /etc/security/pam_env.conf libpam-modules: /etc/security/pam_env.conf (Hence the first paragraph above, and the fact that I reassigned and closed this bug earlier). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#330897: locales: POSIX used, but not chosen
reassign 330897 libpam-modules close 330897 0.79-2 merge 330897 330458 thanks Hi, On Friday, September 30, 2005 11:52 AM, Calum Mackay <[EMAIL PROTECTED]> wrote: > Package: locales > Version: 2.3.5-6 > Severity: normal > > Something odd seems to have happened to my locales, today. Although I > didn't ask for it, the LC settings have changed to POSIX: This isn't a bug in locales, but in libpam-modules. The fixed package was uploaded yesterday. Reassigning, merging with the earlier reports and closing. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#331299: exim4: bashisms in init script
On Sun, 2005-10-02 at 17:31 -0400, Justin Pryzby wrote:
> Package: exim4
> Severity: normal
> Version: 4.52-1
> File: /etc/init.d/exim4
>
> The exim4 initscript /etc/init.d/exim4 uses:
>
> #!/bin/sh
[...]
> if [ "$(readlink /proc/$pid/root)" == "/" ]; then
[...]
> Isn't '$(' a bashism (That's what the vim maintainer said in #319825)
No, $() should be supported by any POSIX-compliant shell; it's a "shall"
in the standard. See
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_03
The ==, otoh, *is* non-compliant and a Bashism.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#332230: wrong distro update for /etc/init.d/exim4 (= substitute ==)
On Wednesday, October 05, 2005 9:49 AM, Emiliano Gabrielli (aka AlberT) <[EMAIL PROTECTED]> wrote: > On Wednesday 05 October 2005 10:46, you wrote: [...] >> Closing this report as this isn't a bug. > > ok, sorry for the report .. I searched in the sh man page .. but it > was bash :-P > > thnx for explaination. > > BTW, what about the backgrounding of start_exim ? That would be a matter for the maintainers to consider, so I'm ccing this back to the BTS. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328447: python2.4-apt: Missing examples
Hi, On Thursday, September 15, 2005 12:22 PM, Joerg Hoh <[EMAIL PROTECTED]> wrote: > Package: python2.4-apt > Version: 0.6.13.1 > Severity: wishlist > > > It seems that the python2.4-apt package is missing its examples. Can > you > add them again? The examples are in python-apt, as they're not specific to the version of python being used - likewise, python2.3-apt does not contain any examples. It doesn't appear to be possible to install python-apt and python2.4-apt simultaneously, but I'm not entirely sure whether that's intentional or not. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328615: Debian-exim username considered bad
package exim4 severity 328615 wishlist tags 328615 + wontfix merge 328615 255493 thanks Hi, > I have the following exim4 packages installed: [...] > Debian-exim:x:102:102::/var/spool/exim4:/bin/false > > This username: [...] > I suggest it be changed to something like 'exim' or 'exim4' in a > future release. The maintainers have previously (and repeatedly) made their position on this issue clear - they will not be changing the username. Please see bug #255493, the four other reports merged with it, /usr/share/doc/exim4-base/README.Debian-accountname and the discussion in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255493&msg=7 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255493&msg=14 . Tagging the report appropriately and merging it with the previous reports. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#333430: new spamassassin v3.1.0 needs new logcheck ignore files
package spamassassin tags 333430 + patch thanks Duncan Findlay wrote, Tuesday, October 11, 2005 11:58 PM: > On Tue, Oct 11, 2005 at 05:41:38PM -0400, Douglas F. Calvert wrote: >> THe new spamassassin changes the syslog entries. The logcheck.ignore >> files were not updated to reflect the new logging format. This is not >> a showstopper but it is annoying and means that admins are less likely >> to read the logs closely... > You don't happen to have a patch do you? I don't use logcheck, so > patches are welcome. (Not necessary, I can figure it out without a > patch, but it'd be nice!) :-) http://lists.debian.org/debian-volatile/2005/10/msg4.html includes a patch that appears reasonable. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328447: python2.4-apt: Missing examples
On Friday, September 23, 2005 12:06 PM, Michael Vogt <[EMAIL PROTECTED]> wrote: > On Thu, Sep 15, 2005 at 02:32:22PM +0100, Adam D. Barratt wrote: >> On Thursday, September 15, 2005 12:22 PM, Joerg Hoh >> <[EMAIL PROTECTED]> wrote: >>> Package: python2.4-apt >>> Version: 0.6.13.1 >>> Severity: wishlist >>> >>> It seems that the python2.4-apt package is missing its examples. Can >>> you >>> add them again? >> >> The examples are in python-apt, as they're not specific to the >> version of python being used - likewise, python2.3-apt does not >> contain any examples. >> >> It doesn't appear to be possible to install python-apt and >> python2.4-apt simultaneously, but I'm not entirely sure whether >> that's intentional or not. > > Installing python2.3-apt, python2.4-apt and pyhton-apt together seems > to work fine here (update-to-date sid). What error do you get when you > try it? Mea culpa. I misremembered the dependencies. I suspect I confused the python (<<2.4) dependency with a conflict against python2.4. Obviously that's incorrect. My original point still stands however - the examples aren't missing, just not in python2.4-apt. :-) Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#330160: RM: acl-installer [amd64] -- RoQA; already removed on other archs
On Monday, September 26, 2005 1:25 PM, Matej Vela <[EMAIL PROTECTED]> wrote: > Package: ftp.debian.org > > Friedrich Dominicus <[EMAIL PROTECTED]> writes: > >> I installed the packages just a 5 days or so ago. If it's orphaned >> why is is there still then? > > There seems to have been a snafu; acl-installer was removed from i386 > and powerpc (http://bugs.debian.org/317416), but is still present on > amd64. Hopefully the ftpmasters will correct this. They can't, as amd64 isn't part of Debian yet. As Joerg Jaspert's message to d-d-a in May said: "The contact address is [EMAIL PROTECTED], please never direct any amd64 related question to the @debian.org counterpart." Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#325299: apt: --names-only doesn't just search names
On Sat, 2005-08-27 at 09:42 -0400, Greg Wooledge wrote: > Package: apt > Version: 0.6.40.1 > Severity: normal > > The man page says: > > and if --names-only is given then the long description is not searched, > only the package name is. > > But: > > griffon:~$ apt-cache search --names-only ming > apache-common - support files for all Apache webservers You're hitting an undocumented feature of `apt-cache search'. It's definitely a feature, as there are comments in the source code indicating that it's supposed to happen. :-) Specifically, search doesn't just examine package names, but also virtual package names. apache-common Provides: libapache-mod-roaming, which matches the supplied pattern. Try `apt-cache search --names-only mail-tran', for instance. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#325887: spamassassin: Please remove the "Depends: spamc" from spamassassin.
On Wednesday, August 31, 2005 4:10 PM, Bob Proulx <[EMAIL PROTECTED]> wrote: > Package: spamassassin > Version: 3.0.3-2 > Severity: wishlist > > The spamassassin package depends upon spamc. But the spamassassin > package is quite useful without the spamc package installed. > Depending upon spamc makes it inconvenient to test upgrades. Please > remove the depends spamc from the spamassassin package and make this a > recommends spamc instead. > > I can guess why things are this way. So that the clueless newbie who > installs spamassassin gets spamc without thinking. And I can live > with that. But it was annoying me and I could find no information in > the BTS about it. It's that way because woody contains a single source package - spamassassin - from which spamc was then split out. The dependency is there to ensure that upgrades work, and there /is/ information about it in the BTS :-) See #213979 and #178277 for example. Those bugs do say the dependency will be downgraded after sarge's release, so if nothing else it's a gentle prod for the maintainer. :) > Meanwhile the spamc package says in the description: > > This package is useless unless you have spamassassin installed, > either on this machine or another local machine (i.e. a mail > server). > > But it does not depend upon spamassassin. If it truly is useless then > it should Depend: spamassassin. But of course this would make a > circular dependency which is undesirable. But with a recommends then > this would work. The main reason that a dependency is inappropriate is that although spamc needs to be able to connect to a spamasassin instance, that instance need not be on the same machine as spamc (the same reason that, for instance, squirrelmail only recommends an IMAP server, despite requiring one in order to operate). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#325860: PTS: Missing get parameter quoting on links
On Wed, 2005-08-31 at 11:20 +, Philipp Kern wrote: > Package: qa.debian.org > Severity: normal > > The PTS fails to quote get parameters when package names are inserted > into links. I encountered this problem when I followed the link to the > BTS on a package having several plus signs in its name (libxml++2.6). > Such special characters which have a special meaning in get should be > onverted to their hexadecimal value and passed with the percent sign > before them. Otherwise it is impossible for the linked script to receive > the name correctly. If I remember it correctly, neither the equals sign > or the ampersand are valid in package names, so probably this only > occurs with the plus sign. > > In this case the correct quoting would be: libxml%2b%2b2.6 As far as I can see, the only URL that doesn't currently work is the "Patches from BTS" link, which definitely needs encoding as described. All the other links appear to work fine as they are - http://packages.debian.org/libxml++2.6 and http://bugs.debian.org/src:libxml++2.6 for instance are both handled correctly by the relevant rewrite rules. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#325988: ftp.debian.org: Please remove cl-cedilla package
package ftp.debian.org retitle 325988 RM: cl-cedilla -- RoM; renamed to cedilla thanks Hi, On Thursday, September 01, 2005 5:06 AM, Peter Van Eynde <[EMAIL PROTECTED]> wrote: > Could you please remove the cl-cedilla package as I renamed it to > cedilla on request of upstream. To save anyone else getting confused :-) as of the time of this e-mail the only visible packages for cl-cedilla are in incoming.d.o, presumably having recently made it through NEW. The renamed cedilla package is currently stuck in NEW. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327019: ssh: scp allows remote execution of shell commands when semicolon is used in filename
On Wednesday, September 07, 2005 6:36 AM, Alexey Feldgendler <[EMAIL PROTECTED]> wrote: > Package: ssh > Version: 1:3.8.1p1-8.sarge.4 > Severity: critical > > Here is my testcase: > > $ scp remotehost@';uname -a' scp [EMAIL PROTECTED]:';uname -a', surely? Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#321896: Incorrect security info on AMD64 page
On Tue, 2005-08-09 at 00:19 -0500, Ross Combs wrote: > "Adam D. Barratt" <[EMAIL PROTECTED]> wrote: > > > On Monday, August 08, 2005 2:15 AM, Ross Combs <[EMAIL PROTECTED]> wrote: > > > > > The security support for the AMD64 port is still (apparently) not > > > in place. > > > > This is not the case - see > > http://lists.debian.org/debian-devel-announce/2005/08/msg1.html > > I believe you are mistaken. I filed the report after trying to use > security.debian.org and having to dig up the old post to see why it > wasn't working. > > It is still not working (yes, the directory seems to exist, but I > can't believe there are zero security updates for AMD64 sarge. The message referred to above says: "Joey Schulze from the Security Team offered to do an accumulative security announce, covering all the amd64 packages which now get added for all the past advisories[1], so expect one big DSA in the near future. (ETA is Monday at the moment). All new DSAs from now on will simply include amd64." I'm assuming the cumulative announcement has been delayed for some reason (although the above does only provide an ETA). Other than that, the message is dated last Wednesday - there have been no security updates for *any* architecture between then and now. I'm afraid at the moment the best advice is to wait for a) the promised cumulative announcement and/or b) the next standard DSA. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#322366: Package has suddenly become Debian native
Package: nessus-plugins Version: 2.2.5-1 Severity: minor Hi, The new version of the nessus-plugins package appears to have been uploaded as a Debian native package. Previous versions of the package were not native, and there is no mention in the changelog of this change being intentional. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#322365: Installs header files to incorrect location
Package: libnasl Version: 2.2.5-1 Severity: grave Hi, As part of the update to debhelper compatibility version 4, a libnasl-dev.install file was added to the package. Unfortunately, an error was made in this file, leading to the header files being installed in /usr/include/include/nessus, rather than /usr/include/nessus. Thus, depending packages will FTBFS due to being unable to locate the header files. The following trivial patch fixes the problem. --- libnasl-2.2.5-1/debian/libnasl-dev.install 2005-08-10 09:34:25.0 +0100 +++ libnasl-dev.install 2005-08-10 12:41:56.0 +0100 @@ -1,6 +1,6 @@ usr/lib/*.so usr/lib/ usr/lib/*.la usr/lib/ usr/lib/*.ausr/lib/ -usr/include/ usr/include/ +usr/include/* usr/include/ usr/bin/nasl-config usr/bin/ usr/share/man/man1/nasl-config.1 usr/share/man/man1/ Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310477: localedef: typo in --help
On Wednesday, August 17, 2005 3:59 AM, GOTO Masanori <[EMAIL PROTECTED]> wrote: > At Mon, 23 May 2005 23:28:01 +0300, > Lars Wirzenius wrote: >> The English output of "localedef --help" contains this: >> >> --posixBe strictly POSIX conform >> >> The last word should surely be "conforming". > > You'll find "POSIX conform" has been used like a noun via google. That Google indexes pages containing broken English does not make that English correct. :-) > I think this trivial change is not needed. The current wording certainly does not make sense in English. Either the suggested wording or, for instance, "Conform strictly to POSIX" does. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323594: OpenVPN 2.0.1 released
package openvpn found 309787 2.0-4 thanks On Wednesday, August 17, 2005 2:17 PM, Luca Corti <[EMAIL PROTECTED]> wrote: > Package: openvpn > Version: 2.0-4 > Severity: wishlist > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > found 309787 2.0-4 > merge 309787 -1 > thanks You can't do that when opening a bug :-) Even if you could a) it wouldn't work as control@ would have given up parsing on the "-BEGIN PGP SIGNED MESSAGE-" line (the fifth without a command) and b) you can't merge bugs of differing severities. Fixing the found status with this mail (although not the merging, as that would require making one of the bugs the wrong severity). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
