Bug#245200: Info received (was upgrade postalias pukes on main.cf: virtual_alias_maps = ldap:/etc/postfix/ldap_aliases.cf)

[LaMont Jones]

On Thu, Jan 20, 2005 at 11:20:43PM -0500, Dan MacNeil wrote:
> I should also mention that it is reasonable to expect that
> postalias won't work on an file with an ldap query

That's why newaliases uses alias_database, while the alias lookups use
alias_maps:

# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi".  This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.

The only way I could see this as being related to the original report
would be if the ldap library on the machine was incorrectly built, and
_it_ was the one missing the symbol.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#292446: modutils: udebs missing Section and Priority

[LaMont Jones]

On Wed, Jan 26, 2005 at 09:22:10PM -0700, LaMont Jones wrote:
> On Thu, Jan 27, 2005 at 01:25:33PM +1100, Angus Lees wrote:
> > Package: modutils
> > Version: 2.4.26-1.1
> > Severity: normal
> > There should be "Section: debian-installer" and "Priority: extra"
> > fields in there (same for modutils-full).
> Interestingly, those fields are present in the source tree I have on my
> machine...  Apparently introduced in one of the recent NMUs...

And more interestingly, present in the control file for the -1.2 NMU as well.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#292446: modutils: udebs missing Section and Priority

[LaMont Jones]

On Thu, Jan 27, 2005 at 01:25:33PM +1100, Angus Lees wrote:
> Package: modutils
> Version: 2.4.26-1.1
> Severity: normal
> There should be "Section: debian-installer" and "Priority: extra"
> fields in there (same for modutils-full).

Interestingly, those fields are present in the source tree I have on my
machine...  Apparently introduced in one of the recent NMUs...

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#333434: [hppa] Cannot compile simple program linked against libglew

[LaMont Jones]

tags 333434 + patch
severity 333434 serious
--
The patch below fixes this issue.  (Specifically, since gcc is allowed to
have architecture-specific components in the link phase, you may not
link things built with gcc using ld.  Likewise, if building g++ objects,
you must link with g++.)

For pushing this upstream, you probably need to tweak config/Makefile.*,
instead of just config/Makefile.linux.

lamont
===
diff -ur t/glew-1.3.1/Makefile glew-1.3.1/Makefile
--- t/glew-1.3.1/Makefile   2005-01-05 20:19:02.0 +
+++ glew-1.3.1/Makefile 2005-11-30 18:37:56.0 +
@@ -86,7 +86,7 @@
$(AR) cr $@ $^
 
 lib/$(LIB.SHARED): $(LIB.SOBJS)
-   $(LD) $(LDFLAGS.SO) -o $@ $^ $(LIB.LDFLAGS) $(LIB.LIBS)
+   $(CC) $(LDFLAGS.SO) -o $@ $^ $(LIB.LDFLAGS) $(LIB.LIBS)
 ifeq ($(patsubst mingw%,mingw,$(SYSTEM)), mingw)
 else
$(LN) $(LIB.SHARED) lib/$(LIB.SONAME)
diff -ur t/glew-1.3.1/config/Makefile.linux glew-1.3.1/config/Makefile.linux
--- t/glew-1.3.1/config/Makefile.linux  2005-01-05 20:19:03.0 +
+++ glew-1.3.1/config/Makefile.linux2005-11-30 18:38:15.0 +
@@ -5,7 +5,7 @@
 CFLAGS.EXTRA = -DGLEW_MX
 endif
 PICFLAG = -fPIC
-LDFLAGS.SO = -shared -soname $(LIB.SONAME)
+LDFLAGS.SO = -shared -Wl,-soname,$(LIB.SONAME)
 LDFLAGS.EXTRA = -L/usr/X11R6/lib
 LDFLAGS.GL = -lXmu -lXi -lGLU -lGL -lXext -lX11
 LDFLAGS.STATIC = -Wl,-Bstatic
===


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#325624: marked as done (gnome-schedule: NEWS.gz is an empty file)

[LaMont Jones]

reopen 325624
--

Closed the wrong bug with a typo:

On Wed, Dec 07, 2005 at 03:48:04PM -0800, Debian Bug Tracking System wrote:
> Your message dated Wed, 07 Dec 2005 15:32:17 -0800
> with message-id <[EMAIL PROTECTED]>
> and subject line Bug#325624: fixed in postfix 2.2.6-1
> has caused the attached Bug report to be marked as done.
> 
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
> 
> (NB: If you are a system administrator and have no idea what I am
> talking about this indicates a serious mail system misconfiguration
> somewhere.  Please contact me immediately.)
> 
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
> 
> --
> Received: (at submit) by bugs.debian.org; 29 Aug 2005 20:37:06 +
> >From [EMAIL PROTECTED] Mon Aug 29 13:37:06 2005
> Return-path: <[EMAIL PROTECTED]>
> Received: from ms-smtp-04.nyroc.rr.com [24.24.2.58] 
>   by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
>   id 1E9qNO-0001iT-00; Mon, 29 Aug 2005 13:37:06 -0700
> Received: from localhost.localdomain (cpe-69-207-105-212.twcny.res.rr.com 
> [69.207.105.212])
>   by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id 
> j7TKb3V2018044;
>   Mon, 29 Aug 2005 16:37:03 -0400 (EDT)
> Received: by localhost.localdomain (Postfix, from userid 1000)
>   id ACA937B41C; Mon, 29 Aug 2005 16:37:23 -0400 (EDT)
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> From: Christine Spang <[EMAIL PROTECTED]>
> To: Debian Bug Tracking System <[EMAIL PROTECTED]>
> Subject: gnome-schedule: NEWS.gz is an empty file
> X-Mailer: reportbug 3.17
> Date: Mon, 29 Aug 2005 16:37:23 -0400
> Message-Id: <[EMAIL PROTECTED]>
> X-Virus-Scanned: Symantec AntiVirus Scan Engine
> Delivered-To: [EMAIL PROTECTED]
> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
>   (1.212-2003-09-23-exp) on spohr.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
>   autolearn=no version=2.60-bugs.debian.org_2005_01_02
> 
> Package: gnome-schedule
> Version: 0.9.0-3
> Severity: minor
> 
> /usr/share/doc/gnome-schedule/NEWS.gz is an empty file. I don't see
> any specific policy on such a thing, but it would seem logical to
> remove NEWS from debian/docs, to be re-added later if it ever comes into
> use.
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.12.080805
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> 
> Versions of packages gnome-schedule depends on:
> ii  anacron   2.3-11 a cron-like program that doesn't 
> g
> ii  at3.1.9  Delayed job execution and batch 
> pr
> ii  python2.3.5-3An interactive high-level 
> object-o
> ii  python-glade2 2.6.2-1GTK+ bindings: Glade support
> ii  python2.3-gnome2  2.10.0-2   Python bindings for the GNOME 
> desk
> ii  python2.3-gtk22.6.2-1Python bindings for the GTK+ 
> widge
> 
> gnome-schedule recommends no packages.
> 
> -- no debconf information
> 
> -------
> Received: (at 325624-close) by bugs.debian.org; 7 Dec 2005 23:37:46 +
> >From [EMAIL PROTECTED] Wed Dec 07 15:37:46 2005
> Return-path: <[EMAIL PROTECTED]>
> Received: from katie by spohr.debian.org with local (Exim 4.50)
>   id 1Ek8ll-0005Xs-Bo; Wed, 07 Dec 2005 15:32:17 -0800
> From: LaMont Jones <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> X-Katie: $Revision: 1.60 $
> Subject: Bug#325624: fixed in postfix 2.2.6-1
> Message-Id: <[EMAIL PROTECTED]>
> Sender: Archive Administrator <[EMAIL PROTECTED]>
> Date: Wed, 07 Dec 2005 15:32:17 -0800
> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
>   (1.212-2003-09-23-exp) on spohr.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
>   autolearn=no version=2.60-bugs.debian.org_2005_01_02
> X-CrossAssassin-Score: 2
> 
> Source: postfix
> Source-Version: 2.2.6-1
> 
> We believe that the bug you reported is fixed in the latest version of
> postfix, which is due to be installed in the Debian FTP archive:
> 
>

Bug#347200: dnsutils: cannot parse /etc/resolv.conf

[LaMont Jones]

severity 347200 normal
--

On Mon, Jan 09, 2006 at 07:04:59PM +0800, Paul Wise wrote:
> I'm unable to use the current versions of dig and host to resolve
> hostnames. Other applications work fine - wget for instance. My
> resolv.conf is the same as it has always been - generated by pump from
> dhcp information spit out by my adsl modem.
> 
> [EMAIL PROTECTED]:~$ cat /etc/resolv.conf
> search
> nameserver 203.21.20.20
> 
> Since removing the search line fixes this, I'm making this important
> instead of grave, but I'd rather not have to modify that file on
> startup.


% man resolv.conf
   search Search list for host-name lookup.
  The  search  list  is  normally determined from the local domain
  name; by default, it contains only the local domain name.  This
  may be changed by listing the desired domain search path follow‐
  ing the search keyword with spaces or tabs separating the names.


I expect that what you want the line to say is 'search .'

The line is, in fact, not correctly parsable, although I suppose the
intent could be divined.

lamont

Bug#344538: hppa dependency problems on build of pdns

[LaMont Jones]

On Tue, Jan 10, 2006 at 11:08:14AM +0100, Frank Küster wrote:
> Steve Langasek <[EMAIL PROTECTED]> wrote:
> > or a bug in some
> > maintainer script or other;
> How a bug in a maintainer script could have the result that installing
> an arch-all package fails because an other arch-all package is not
> there, and how this can happen on only one particular machine of one
> particular architecture, this I fail to see.

Simple.  Buggy postrm (or was it prerm) fails, and the package is left
with all its files removed, but still marked as installed in dpkg.  And
it never gets installed again.  There have been a few packages like
this, and tetex-$mumble seems to ring a bell as one of the b0rken ones.

lamont

Bug#336015: symbol lookup error

[LaMont Jones]

tags 336015 unreproducible
--
> piper:~# sendmail
> sendmail: symbol lookup error: /usr/lib/libpostfix-global.so.1:
> undefined symbol: mail_conf_lookup_evah
> piper:~# echo $?
> 127

I can't reproduce this.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#322771: postfix: smtp(8) can't resolve localhost any more

[LaMont Jones]

On Fri, Aug 12, 2005 at 09:30:38PM +0200, Beat Bolli wrote:
> Ever since the update of libc6 to 2.3.5, I get the following log entries
> when sending or receiving mail (wrapped for legibility):
> 
> Aug 12 20:53:21 bolli postfix/smtp[6973]: E8E774BBAA: \
> to=<[EMAIL PROTECTED]>, relay=none, delay=1, status=bounced \
> (Host or domain name not found. Name service error for name=localhost \
> type=A: Host not found)

Does this still occur with 2.2.7-1? (or even 2.2.6-1)

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#322320: acknowledged by developer (Re: Bug#322320: Postfix configuration in /etc/postfix incomplete)

[LaMont Jones]

On Sun, Dec 25, 2005 at 03:24:21AM +0800, Uwe Dippel wrote:
> This is bad news. The reasoning is flawed from the start:
> 1. There is no hint that /usr/share/postfix/main.cf.dist would be the 
> original main.cf. And it even isn't. How to know ?

well, except for these lines at the start of /etc/postfix/main.cf:
  # see /usr/share/postfix/main.cf.dist for a commented, fuller
  # version of this file.

> 5. dpkg-reconfigure - if it is to make any sense at all - would have to 
> cater for this highly subjective behaviour of Debian's postfix and 

more debconf questions would only make it worse...  As it is, if you 
edit main.cf after running debconf, it has to pick up your new answers
as the defaults, lest you change things when you just hit return...

> Once again: To offer *additional* explanations and examples are fine. 
> But these do not warrant to remove the original files from the 
> underlying sources with which most of the users are familiar and 
> replacing these with arbitrary partial collections without any 
> explanations.

Nor does cluttering up a file with useless things like manpages in the
form of comments.

> Examples here: What use would these parameters in main.cf as provided by 
> Debian have say to the average user ?:

The things in /etc/postfix/main.cf are the sum total of things that
debian has changed from the upstream defaults.  Everything not mentioned
in the file is the upstream default.  That is, if you take the debian
sources, and compile them on a non-debian system, you get the (expected)
upstream behavior.

> Instead something like this would belong into main.cf:
> ># Debian GNU/Linux specific:  Specifying a file name will cause the
> ># first line of that file to be used as the name.  The Debian default
> ># is /etc/mailname.
> >#
> >#myorigin = /etc/mailname
> Who is going to *think* of this or find it in 25kByte of that

That probably does belong in our main.cf.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#322320: acknowledged by developer (Re: Bug#322320: Postfix configuration in /etc/postfix incomplete)

[LaMont Jones]

On Sun, Dec 25, 2005 at 11:03:11AM +0800, Uwe Dippel wrote:
> LaMont Jones wrote:
> Well, saw this and asked myself what 'fuller' means. I don't expect that 
> one to be 'fuller', but eventually 'original'.

Ah, ok.

> How about something like
> ># This file contains a small subset of parameters. 
> ># Replace this file with /usr/share/postfix/main.cf.dist 
> ># if you need more specific settings

No.  Maybe:
# Add settings found in /usr/share/postfix/main.cf.dist if you need to
# change things.  But there's absolutely no reason to copy the whole
# file into place just to add one parm.


> Usability: I used postfix a few times before and know to handle it. On 
> Debian it took me half an hour to understand just how to get the 
> original main.cf (actually, I didn't. I copied it from elsewhere in the 
> end).

Which leads immediately to the question of why you felt you needed the
entire 25KB just to tweak a couple parameters that could have been
appended to the existing main.cf

> Thanks for the agreement.
> Have a look at that preposterous
> /usr/share/doc/postfix/README.Debian
> ...
> except it wouldn't address *any* of the items discussed in here.

8.  The upstream main.cf is deliverd as /usr/share/postfix/main.cf.dist,
rather than cluttering /etc/postfix/main.cf with comments.

Unsure why you say "preposterous", though.  Those are the significant
differences between upstream and Debian.  And I don't see any others
that I consider significant.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#322320: acknowledged by developer (Re: Bug#322320: Postfix configuration in /etc/postfix incomplete)

[LaMont Jones]

On Sun, Dec 25, 2005 at 12:55:18PM +0800, Uwe Dippel wrote:
> LaMont Jones wrote:
> Obvious. Obvious !
> This is - maybe only my - personal style.
> 1. It avoids typos (if I retyped the line)
> 2. It avoids opening any other file
> 
> I (use vi) simply /[parameter to be changed] and make the alteration 'on 
> the spot'. No typos, no search.
> 3. All explanations are there (comments)
> 
> Couldn't be less error-prone and easier !

And postinst uses 'postconf -e', which searches the file for uncommented
versions of the parameter, and (finding none) appends it to the end of
the file.  Then you go uncomment the earlier occurance and wonder why it
had no effect.  Very obvious. :-(

> I couldn't bother less if the .conf was 1 k or 50 k.
> Everything there, in place, with comments and explanation.

Not necessarily in place.  postconf ignores comments.

> And, if you read my initial report, after Maildir/ the mess on Debian 
> has just started. I want and need transport, virtual, and stuff. Where 
> is it ?? In my other distro, it is in /etc/postfix.
There's nothing in /etc/postfix/transport that isn't in man 5 transport.

And delivering the file means questions at upgrade time every time
upstream changes the manpage.  No thanks.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#315939: errors in log: Jun 27 02:35:01 lyra postfix/pipe[12885]: fatal: service mailman requires privileged operation

[LaMont Jones]

On Wed, Dec 28, 2005 at 06:45:06PM +0100, Sjoerd Simons wrote:
> On Mon, Jun 27, 2005 at 03:09:01AM +0800, Anand Vaidya wrote:

> > Further there is a line break just before ${nexthop} ${user} in the argv
> > line. Is that OK? I don't think so.
> > 
> >  argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}

No, it's fine.  Leading whitespace marks a continuation line, and causes
the line to be appended to the prior one as part of parsing.

> Could these fixes be applied for the next postfix package ? I just wasted an
> hour finding this problem, because i assumed the default debian config would 
> be okay.

  * Make mailman service run privileged.  sigh.  Closes: #315939

It'll be in 2.2.7-2, and later.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345798: nmap: New upstream release 3.95

[LaMont Jones]

tags 345798 + pending
--

> nmap 3.95 released Thu, 8 Dec 2005:
>   http://seclists.org/lists/nmap-hackers/2005/Oct-Dec/0002.html

And packaged December 9.  Now I just need to figure out why I didn't
actually upload it. :-(

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345887: acknowledged by developer (Bug#345887: fixed in confluence 0.10.6-3)

[LaMont Jones]

On Wed, Jan 04, 2006 at 09:13:33PM +0100, Julien Cristau wrote:
> Hi buildd/P-a-s maintainers,
> since confluence should now build on all debian archs, I'd like to
> request its removal from Packages-arch-specific, and a change of its
> wanna-build state on mips, mipsel and s390 to Needs-Build.

Removed from PaS: %confluence: !m68k

w-b state changes will either be automatic, or require the buildd admin
to do them.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#326961: acknowledged by developer (Bug#326961: fixed in iproute 20041019-4)

[LaMont Jones]

reopen 326961
--

You need the 2nd half of the patch (found in my reply to the original
bug report, as well as below...)

thanks,
lamont


diff -urNad iproute-20041019/tc/paretonormal.c 
/tmp/dpep.9YHbob/iproute-20041019/tc/paretonormal.c
--- iproute-20041019/tc/paretonormal.c  2004-10-19 14:49:02.0 -0600
+++ /tmp/dpep.9YHbob/iproute-20041019/tc/paretonormal.c 2005-09-06 
15:49:01.0 -0600
@@ -54,7 +54,7 @@
double *table;
int i,n;
 
-   table = calloc(TABLESIZE, sizeof(double));
+   table = calloc(TABLESIZE+1, sizeof(double));
if (!table) {
fprintf(stderr, "Out of memory!\n");
exit(1);



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#311828: modutils: ksyms does not work for 2.6.x kernels also

[LaMont Jones]

tags 311828 + wontfix
--

> ~$ /sbin/ksyms
> ksyms: QM_MODULES: Function not implemented
> $ uname -r
> 2.6.14

Use module-init-tools for 2.6 kernels.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#313229: bind9-host: Returns host: couldn't get address for '': not found

[LaMont Jones]

tags 313229 + unreproducible
--

On Sun, Jun 12, 2005 at 04:32:43PM +0100, Colin Davis wrote:
> The package returns:
> host: couldn't get address for '': not found
> when running: host xxx.tld

% host xxx.tld
Host xxx.tld not found: 3(NXDOMAIN)
% host www.cc
www.cc has address 198.41.1.40

Looks like I'll need an actual hostname.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#163134: postfix-tls: Upgrade from Debian 3.0 to 3.1 cause postfix to fail.

[LaMont Jones]

On Fri, Jun 17, 2005 at 01:19:04AM +0200, Robert Cheramy wrote:
> when upgrading from debian 3.0 to 3.1, postfix-tls not working causes
> postfix fail with the error:
> Jun 17 00:38:23 vd postfix/smtpd[13446]: fatal: no SASL authentication 
> mechanisms
> My /etc/postfix/sasl/smtp.d file looked like this:
> pwcheck_method:  sasldb
> 
> I think this bug should have its severity set to "grave".

At the request of the sasl maintainer, postfix does not Depend: on sasl2
modules.  using postfix-tls probably means that you need to install
sasl2 (woody's postfix-tls used sasl1.5), and configure that.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310597: postfix-ldap: newaliases command breaks upgrade on systems with alias_maps using LDAP

[LaMont Jones]

On Tue, May 24, 2005 at 10:14:35AM -0400, Stephen Touset wrote:
> # fetch aliases from LDAP and /etc/aliases
> alias_maps = ldap:ldapalias hash:/etc/aliases
> alias_database = ldap:ldapalias hash:/etc/aliases

Per the documentation:  alias_maps is the list of maps to query for
aliases.  Since not all maps can/should be regenerated, alias_database
is the list of maps to regenerate at newalias time.  You told it to
regenerate an ldap database, which fails.

This is a configuration issue, not a postfix bug.
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305311: postfix: dpkg-buildpackage only works once

[LaMont Jones]

fixed in 2.2.2-1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#271960: postfix - rejects ipv6 literal addresses in ehlo

[LaMont Jones]

On Thu, Sep 16, 2004 at 03:37:12PM +0200, Bastian Blank wrote:
> postfix rejects literal ipv6 addresses in ehlo commands.

Fixed in 2.2.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304920: postfix: more info about the sasl bug in 2.2.2-1

[LaMont Jones]

On Mon, Apr 18, 2005 at 08:03:12PM -0700, Paul Traina wrote:
> The problem is that patches/10tls.dpatch is not being executed.
> the permissions on this file are 644 instead of 755, which is
> probably why dpatch is not running.

Actually, the problem is the lack of '10tls' in debian/patches/00list.

Fixed in 2.2.1-2, which will be uploaded soon.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305521: dia_0.94.0-7: FTBFS with gcc-4.0

[LaMont Jones]

On Wed, Apr 20, 2005 at 05:52:54PM +0200, Roland Stigge wrote:
> On Wed, 2005-04-20 at 08:02 -0600, [EMAIL PROTECTED] wrote:
> > > shape_info.c:902: warning: pointer targets in passing argument 1 of 
> > > '__builtin_strcmp' differ in signedness
> > > shape_info.c:902: warning: pointer targets in passing argument 1 of 
> > > '__builtin_strcmp' differ in signedness
> > > shape_info.c:742: warning: unused variable 'ext_size'
> Haven't tried yet (there's no such package: gcc-4.0), but I don't see
> any error in the above.

Yeah - that was a bad cut on the part of the bug generator... sorry.
The relevant lines are:

> shape_info.c: At top level:
> shape_info.c:121: error: static declaration of 'parse_path' follows 
> non-static declaration
> shape_info.h:169: error: previous declaration of 'parse_path' was here

gcc-4.0_4.0-0pre10 is in experimental.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#308815: FTBFS: gcc-4.0 errors

[LaMont Jones]

Package: tar
Version: 1.15-1
Severity: normal
Tags: patch

> make[3]: Entering directory `/build/buildd/tar-1.15.1/tests'
> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I../lib -I../src-O2 -g 
> -Wall -MT genfile.o -MD -MP -MF ".deps/genfile.Tpo" -c -o genfile.o 
> genfile.c; \
> then mv -f ".deps/genfile.Tpo" ".deps/genfile.Po"; else rm -f 
> ".deps/genfile.Tpo"; exit 1; fi
> genfile.c:63: error: static declaration of 'argp_program_version' follows 
> non-static declaration
> ../lib/argp.h:428: error: previous declaration of 'argp_program_version' was 
> here
> genfile.c:64: error: static declaration of 'argp_program_bug_address' follows 
> non-static declaration
> ../lib/argp.h:444: error: previous declaration of 'argp_program_bug_address' 
> was here
> make[3]: *** [genfile.o] Error 1
> make[3]: Leaving directory `/build/buildd/tar-1.15.1/tests'

The patch below fixes it.

lamont

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

===
diff -ur t/tar-1.15.1/tests/genfile.c tar-1.15.1/tests/genfile.c
--- t/tar-1.15.1/tests/genfile.c2004-09-08 05:50:20.0 -0600
+++ tar-1.15.1/tests/genfile.c  2005-05-12 08:20:27.0 -0600
@@ -60,8 +60,8 @@
 /* Block buffer for sparse file */
 char *buffer;
 
-static const char *argp_program_version = "genfile (" PACKAGE ") " VERSION;
-static const char *argp_program_bug_address = "<" PACKAGE_BUGREPORT ">";
+const char *argp_program_version = "genfile (" PACKAGE ") " VERSION;
+const char *argp_program_bug_address = "<" PACKAGE_BUGREPORT ">";
 static char doc[] = N_("genfile generates data files for GNU paxutils test 
suite");
 
 static struct argp_option options[] = {
===


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#309025: ghc6: Crashes with bus error on hppa

[LaMont Jones]

> hppa people, any idea what's going on?

Bus errors happen when support for unaligned load/stores is turned off.

For various reasons, support is disabled on sarti.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#309025: ghc6: Crashes with bus error on hppa

[LaMont Jones]

On Sat, May 14, 2005 at 02:27:52PM +0100, Ian Lynagh wrote:
tags 309025 - unreproducible

> > make[1]: Entering directory `/build/buildd/missingh-0.11.0'
> > ghc -package Cabal Setup.lhs -o setup
> > make[1]: *** [setup] Bus error
> Works for me on paer:
> 
> hppa people, any idea what's going on?

echo 1 > /proc/sys/kernel/unaligned-trap 
and try again.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#309025: ghc6: Crashes with bus error on hppa

[LaMont Jones]

On Sat, May 14, 2005 at 08:18:43PM -0600, LaMont Jones wrote:
> > hppa people, any idea what's going on?
> echo 1 > /proc/sys/kernel/unaligned-trap 
> and try again.

Gah.  Let me try that again from the top.

echo 0 > /proc/sys/kernel/unaligned-trap

and you'll find that the unaligned load/store in ghc causes the bus
error.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#309025: ghc6: Crashes with bus error on hppa

[LaMont Jones]

On Sun, May 15, 2005 at 03:19:38PM +0100, Ian Lynagh wrote:
> Can someone please make paer and sarti agree on the value, so either the
> build works or I can debug it?

Paer has been changed.  cat /proc/sys/kernel/unaligned-trap to verify,
should be '0'.  (Worse things happen on the buildd when it's enabled,
etc, etc.)

Note that once paer is rebooted next, the config will revert.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#233891: [hppa] maxima/acl2 failures at -O1/-O2, -O0 ok

[LaMont Jones]

On Sat, May 21, 2005 at 03:58:23PM +0200, Falk Hueffner wrote:
> it seems that acl2 now builds on hppa. Can we close this bug?

yes.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#292928: transport map affects all MXs?

[LaMont Jones]

On Mon, Jan 31, 2005 at 12:27:25AM -0800, Ryan Murray wrote:
> With a transport map of:
> somehost.example.com smtp:somehost.example.com:portnum
> If somehost.example.com has two MXs, itself as lowest priority, and
> mx.example.com at priority 10, postfix will try to deliver to mx.example.com
> on portnum, rather than via regular smtp.

> Is this by design?  And if so, is there a workaround?

The transport map in the report will use MX RR's, by design.  To just use
A RR's, you want to say:
  somehost.example.com smtp:[smoehost.example.com]:portnum

Note that it should be attempting delivery in MX RR order.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291031: additional Info regarding #291031

[LaMont Jones]

On Tue, Jan 18, 2005 at 05:12:31PM +0100, Sebastian Feltel wrote:
> I was running into the same problems which Martin described while 
> upgrading postfix. I "solved" the problem by uncommenting the 
> newaliases-Section (line 438 - 450) in the postix postinst-Script.

> For reference I've saved my configuration at [1]. This configuration was 
> used under postfix 1.x and modified some times ago to be compatible with 
> postfix 2. Postfix is running quite well as before the upgrade to 
> postfix 2.1.5-4

alias_maps = hash:/etc/postfix/aliases, mysql:/etc/postfix/mysql-aliases.cf
alias_database = hash:/etc/postfix/aliases, mysql:/etc/postfix/mysql-aliases.cf

>From the documentation:
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi".  This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.

Since you can't rebuild mysql maps with newaliases, you really want to
have this instead:

alias_maps = hash:/etc/postfix/aliases, mysql:/etc/postfix/mysql-aliases.cf
alias_database = hash:/etc/postfix/aliases

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#293046: postfix: Postfix/IPv6 in chrootjail are an OpenRelay

[LaMont Jones]

tags 293046 + moreinfo
--

On Mon, Jan 31, 2005 at 10:17:49PM +0100, Nico Jochens wrote:
> Sorry for my bad english. When the postfix with IPv6-patch is running in a
> chrootjail, it's an OpenRelay. The reason is a bug in the IPv6-patch.
> The entry "mynetworks" is not to evaluate, because the /proc-directory
> isn't available in the chrootjail. Postfixversion without IPv6-patch,
> doesn't have a problem. It gives more problems, based on this bug.
> For more Questions please ask Peer Heinlein, the Author from the Postfix-Book,
> on [EMAIL PROTECTED], for more information because he is the discoverer
> from the bug.

Have you verified that this is the case?  If I'm reading things
correctly, the bug was actually fixed in 2.1.4-5.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#293501: postfix: Postfix 2.1.4-4 in unstable is an open relay unless relay_domains is explicitly set

[LaMont Jones]

tags 293501 - patch
tags 293501 + moreinfo
tags 293501 + unreproducible
--
(No patch present, just a workaround that disables a major chunk of
functionality...)

2.1.5-5 is the current version of postfix in sarge, and 2.1.5-6 is in
unstable.

Before being able to fix this bug, I'm going to need some more detail.
The most likely situation is that you have filed a duplicate of #267837,
which was fixed in 2.1.4-5, which was uploaded to unstable on 5 September
2004.

Without any concrete information to reproduce this issue, I'll need to
close it.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#293889: postfix: Fresh installation does not write alias for root

[LaMont Jones]

severity 293889 normal
--

> On fresh installation postfix _silently_ does not write alias for root.
> That is, it installs with /etc/aliases like

If /etc/aliases exists at install time, then it is left untouched, since
the admin obviously has what he wants there.  Your /etc/aliases is not
from a stock install of postfix, so it wouldn't have configured an alias
for root.

FWIW, the mail should be in /var/mail/nobody.

> Installation was performed in replace of exim4 which was intentionally
> left unconfigured during initial installation of Debian (to replace it
> with postfix immediately).

And replacing exim4 didn't correct the deficiency in exim4's alias file.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#294124: error in Postfix - unallocated memory block?

[LaMont Jones]

On Tue, Feb 08, 2005 at 01:18:41AM +0100, Waldemar Dworakowski wrote:
> Found something like line below in my error log.
> Feb  6 02:34:00 localhost postfix/smtp[9644]: panic: myfree: corrupt 
> or unallocated memory block

1) Do you have the postfix-tls package installed, or just postfix?
2) If yes, can we tell SASL or TLS was in use in the session that died?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305586: postfix: Still got the same issues when using 2.2.2-3

[LaMont Jones]

On Mon, May 02, 2005 at 10:54:24PM +0200, Roel van der Made wrote:
> When trying 2.2.2-3 (yes, I already downgraded to 2.1.5-9 since that one
> still works) I still got the same problems as mentioned in the report
> before:

Yeah...  The fix only affects new installs.  I'll have to go force
things for upgrades.  thanks.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#306851: postfix: pid files doesnt get removed when stopping

[LaMont Jones]

On Mon, May 02, 2005 at 08:35:34AM -0600, LaMont Jones wrote:
> On Fri, Apr 29, 2005 at 12:18:28AM +0200, Martin Skøtt wrote:
> > I discovered that stopping postfix (/etc/init.d/postfix stop) didn't
> > result in /var/spool/postfix/pid/master.pid being removed. This
> > explains why the if-up script thought postfix was running.
> 
> No it doesn't.  The if-up script thinks postfix running, if and only if

However, if-down does not have the detection code, and that could
explain things, if eth1 just changed IP's in your example.

lamont

Bug#306851: postfix: pid files doesnt get removed when stopping

[LaMont Jones]

On Fri, Apr 29, 2005 at 12:18:28AM +0200, Martin Skøtt wrote:
> I discovered that stopping postfix (/etc/init.d/postfix stop) didn't
> result in /var/spool/postfix/pid/master.pid being removed. This
> explains why the if-up script thought postfix was running.

No it doesn't.  The if-up script thinks postfix running, if and only if
1) /var/spool/postfix/pid/master.pid exists _AND_
2) the pid named in that file is executing /usr/lib/postfix/master.

What exactly does your if-up script have in it?

lamont

Bug#307439: (no subject)

[LaMont Jones]

On Mon, May 02, 2005 at 09:32:05PM -0700, John Hendrickson wrote:
> Subject: bind9: no docs or manual

apt-get install bind9-doc

For man pages, start with man named.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305586: postfix: Still got the same issues when using 2.2.2-3

[LaMont Jones]

On Tue, May 03, 2005 at 05:11:15PM +0200, Roel van der Made wrote:
> Just to keep things clear, 2.2.3-1 keeps nagging about the same sdbm
> libs. Also it complaints, when installing, about not beiing allowd to
> rename some bins in /usr/lib/postfix, when I remove them by hand the
> install goes allright, but postfix wont accept mail reporting the sdbm
> error messages as quoted in the beginning of this report..
> 
> If you need more info please let me know, I'd like to upgrade my postfix
> to the 2.2 release..

Sigh.  I was heading down the wrong rathole before.  Please try adding
this to /etc/apt/sources.list and installing postfix:

deb http://people.debian.org/~lamont/postfix /

If that works, I'll upload it.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#307780: SMTP Auth fails with latest postfix-tls (sarge)

[LaMont Jones]

On Thu, May 05, 2005 at 03:08:14PM +0200, Tim Weippert wrote:
> May  5 14:56:55 hebus postfix/smtp[20410]: smtp_sasl_authenticate:
> mail.topf-sicret.org[217.160.140.89]: SASL mechanisms DIGEST-MD5
> CRAM-MD5
> May  5 14:56:55 hebus postfix/master[20274]: warning: process
> /usr/lib/postfix/smtp pid 20410 killed by signal 11

This sounds like it's dying down in the SASL code...  please add a -v or
two to the end of the line that starts and ends with 'smtp' in
/etc/postfix/master.cf, and send me that output.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305634: quintuple-agent: agpg crashes

[LaMont Jones]

tags 305634 + patch
--

The issue is that the arglist is overrun by one argument.  The patch
below (and at http://patches.ubuntu.com/patches/quintuple-agent.malloc.patch)
fixes the problem.

lamont
diff -ur quintuple-agent-1.0.4-5/agpg.c quintuple-agent-1.0.4/agpg.c
--- quintuple-agent-1.0.4-5/agpg.c  2002-09-28 01:16:01.0 -0600
+++ quintuple-agent-1.0.4/agpg.c2005-05-09 19:04:56.0 -0600
@@ -175,7 +175,7 @@
 int i;
 
 close(p[1]);
-args = malloc(sizeof(char *) * (argc + 2));
+args = malloc(sizeof(char *) * (argc + 3));
 if (!args) {
   fprintf(stderr, _("out of memory\n"));
   return EXIT_FAILURE;


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#300258: --ignore-file-name-case doesn't work

[LaMont Jones]

Package: diff
Version: 2.8.1-7
Severity: normal

As described in https://bugzilla.ubuntu.com/show_bug.cgi?id=7291
diff --ignore-file-name-case does not appear to work.  To reproduce:

% mkdir a b
% touch a/foo b/FOO
% diff --ignore-file-name-case a b
Only in a: foo
Only in b: FOO

lamont

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.10-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#300278: defoma: debhelper files fail if defoma is removed before package

[LaMont Jones]

Package: defoma
Version: 0.11.8-0.1
Severity: serious

In the case where both defoma and, say fontconfig, are being removed in
the same dpkg run, defoma was removed first, and then fontconfig's prerm
script failed with:

> Removing defoma ...
> Purging configuration files for defoma ...
> dpkg - warning: while removing defoma, directory `/etc/defoma' not empty so 
> not removed.
> Removing libfreetype6 ...
> Purging configuration files for libfreetype6 ...
> Removing fontconfig ...
> /var/lib/dpkg/info/fontconfig.prerm: line 9: /usr/bin/defoma-app: No such 
> file or directory
> dpkg: error processing fontconfig (--remove):
>  subprocess pre-removal script returned error exit status 1

The patch at http://patches.ubuntu.com/patches/defoma.prerm.diff fixes
the problem by only running the commands if the binaries are present.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#301146: util-linux: fdisk: bad debian patch

[LaMont Jones]

tags 301146 + sarge
--
Fixed in 2.12l-1.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#183163: CDB support in postfix with a postfix-cdb package

[LaMont Jones]

On Wed, Jun 29, 2005 at 05:01:42PM +0200, Loic Le Loarer wrote:
> Since 2.2, Postfix has intergrated cdb support with tinycdb library. Is
> it possible to have a postfix-cdb package nowadays ? It would be helpful
> (I think cdb maps use less memory and is faster).

Once tinycdb has a shared lib, I can fix this.  Bug filed against
tinycdb.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#316253: please provide libcdb.so

[LaMont Jones]

Package: tinycdb
Version: 0.74-1
Severity: wishlist

Please provide libcdb.so, so that shared libraries can link against it.
This is preventing postfix from providing CDB map support.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#319143: Please integreate the path

[LaMont Jones]

On Thu, Jul 21, 2005 at 02:10:59PM +0200, Aurélien Labrosse EXT RSC-CIP-GRE 
wrote:
> Could you integrate the patch or at least change the dependency from
> slang1a-utf8 to libslang1-utf8 ? This is needed to create pbuilder
> images..

Just waiting for a libc6 upload to fix a header-file FTBFS, and I'll
upload a new util-linux.

lamont

Bug#300860: more complete patch for klic

[LaMont Jones]

implicit deps cause problems on 64-bit machines.  The attached patch
makes for far fewer warnings from gcc-4.0, although there are still
several:

  klicdb.c:126: warning: pointer targets in passing argument 1 of 'atoi' differ 
in signedness
  klicdb.c:252: warning: pointer targets in passing argument 1 of 
'enter_functor' differ in signedness
  klicdb.c:254: warning: pointer targets in passing argument 1 of 
'enter_predicate' differ in signedness
  bb.c:231: warning: assignment makes pointer from integer without a cast
  generic.c:243: warning: function definition has qualified void return type
  generic.c:243: warning: function return types not compatible due to 'volatile'
  generic.c:243: warning: function return types not compatible due to 'volatile'
  generic.c:243: warning: function return types not compatible due to 'volatile'
  ggoal.c:81: warning: pointer targets in passing argument 1 of 'strlen' differ 
in signedness
  ggoal.c:91: warning: pointer targets in passing argument 1 of 'strlen' differ 
in signedness
  ggoal.c:228: warning: passing argument 1 of 'find_pred_ent' discards 
qualifiers from pointer target type
  gunix.c:1813: warning: pointer targets in passing argument 3 of 'accept' 
differ in signedness
  gunix.c:1871: warning: pointer targets in passing argument 3 of 'getsockname' 
differ in signedness
  io.c:25: warning: pointer targets in passing argument 2 of 
'__builtin_strncpy' differ in signedness
  faisus.c:173: warning: passing argument 2 of 'do_fail' from incompatible 
pointer type
  debug.c:314:25: warning: trigraph ??/ ignored, use -trigraphs to enable
  faisus-t.c:173: warning: passing argument 2 of 'do_fail' from incompatible 
pointer type
  recsusp.c:66: warning: passing argument 1 of 'hash_pred' discards qualifiers 
from pointer target type
  debug-t.c:314:25: warning: trigraph ??/ ignored, use -trigraphs to enable
  trace.c:292: warning: passing argument 1 of 'enter_pred_hash' discards 
qualifiers from pointer target type
  /build/lamont/klic-3.003/runtime/gunix.c:2543: warning: the use of `mktemp' 
is dangerous, better use `mkstemp'

lamont
diff -ur t/klic-3.003/debian/changelog klic-3.003/debian/changelog
--- t/klic-3.003/debian/changelog   2005-07-23 14:23:00.0 -0600
+++ klic-3.003/debian/changelog 2005-07-23 13:59:07.0 -0600
@@ -1,3 +1,9 @@
+klic (3.003-2ubuntu1) breezy; urgency=low
+
+  * fix compile errors.  Closes: Debian #300860
+
+ -- LaMont Jones <[EMAIL PROTECTED]>  Sat, 23 Jul 2005 13:58:54 -0600
+
 klic (3.003-2) unstable; urgency=low
 
   * Change maintainer address.
diff -ur t/klic-3.003/compiler/klic.c klic-3.003/compiler/klic.c
--- t/klic-3.003/compiler/klic.c1999-03-25 00:33:16.0 -0700
+++ klic-3.003/compiler/klic.c  2005-07-23 14:04:38.0 -0600
@@ -18,6 +18,7 @@
 #ifdef USELOCKF
 #include 
 #endif
+#include 
 
 #define KL1_TO_C_COMPILER   KLIC_COMPILER
 
diff -ur t/klic-3.003/compiler/klicdb.c klic-3.003/compiler/klicdb.c
--- t/klic-3.003/compiler/klicdb.c  1999-03-25 00:33:16.0 -0700
+++ klic-3.003/compiler/klicdb.c2005-07-23 14:04:45.0 -0600
@@ -16,8 +16,7 @@
 #ifdef USELOCKF
 #include 
 #endif
-
-extern void *malloc();
+#include 
 
 char *dbdir = 0;
 char *initdbdir = 0;
diff -ur t/klic-3.003/include/klic/options.h klic-3.003/include/klic/options.h
--- t/klic-3.003/include/klic/options.h 1999-03-25 00:33:22.0 -0700
+++ klic-3.003/include/klic/options.h   2005-07-23 13:58:51.0 -0600
@@ -20,8 +20,6 @@
 ARG_NOT_USED
 };
 
-extern Const struct opttable opttable[];
-
 char *parse_opts();
 
 /* not copied when spawned */
diff -ur t/klic-3.003/runtime/alloc.c klic-3.003/runtime/alloc.c
--- t/klic-3.003/runtime/alloc.c1999-03-25 00:33:32.0 -0700
+++ klic-3.003/runtime/alloc.c  2005-07-23 14:06:08.0 -0600
@@ -7,8 +7,7 @@
 #include 
 #include 
 #include 
-
-extern char *malloc(), *realloc();
+#include 
 
 char *malloc_check(size)
  unsigned long size;
diff -ur t/klic-3.003/runtime/asyncio.c klic-3.003/runtime/asyncio.c
--- t/klic-3.003/runtime/asyncio.c  1999-03-25 00:33:32.0 -0700
+++ klic-3.003/runtime/asyncio.c2005-07-23 14:12:25.0 -0600
@@ -19,6 +19,7 @@
 #include 
 #include 
 #include 
+#include 
 
 /*
   void sigio_handler(allocp, sig)
@@ -169,7 +170,6 @@
 init_sigio_handler()
 {
   static sigio_initiated = 0;
-  extern char *malloc();
   int k;
   if (sigio_initiated)
 return;
@@ -246,7 +246,6 @@
 #ifdef USESIG
   static asyncio_initiated = 0;
   if (!asyncio_initiated) {
-extern char *malloc();
 int k;
 
 init_sigio_handler();
diff -ur t/klic-3.003/runtime/debug.c klic-3.003/runtime/debug.c
--- t/klic-3.003/runtime/debug.c1999-03-25 00:33:32.0 -0700
+++ klic-3.003/runtime/debug.c  2005-07-23 

Bug#300278: defoma: debhelper files fail if defoma is removed before package

[LaMont Jones]

On Sat, Mar 26, 2005 at 02:26:41AM -0800, Steve Langasek wrote:
> I'm not convinced that this is actually a bug in defoma; the trouble is that
> the failure happens in the fontconfig *pre*rm script, and fontconfig depends
> on defoma -- so how is it possible that defoma's files have been removed
> before the "prerm remove" call for a package depending on it, unless there
> is a bug in dpkg?

You know, it's entirely possible that this was left over screwage from
some other fontconfig/defoma/whatever mess.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#317018: postfix and virtual develery with mysql

[LaMont Jones]

On Tue, Jul 05, 2005 at 05:30:56PM +0200, Michael Rasmussen wrote:
> The patch solves the problem when you have enabled virtual delivery in
> postfix thru an external source like a database or ldap and postfix runs
> in chroot mode, which is the default configuration in Sarge. The problem

The other solution is to use the proxy: map specifier to de-chroot the
map lookup, as well as reducing the load on the external source.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#317825: ITP: dnspython -- ITP: dnspython: DNS module for python

[LaMont Jones]

Package: wnpp
Severity: wishlist


In TLA at http://www.dnspython.org/archives/2005-public/dnspython, I've
chatted with upstream about packaging it.

* Package name: dnspython
  Version : x.y.z
  Upstream Author : Name <[EMAIL PROTECTED]>
* URL : http://www.example.org/
* License : (GPL, LGPL, BSD, MIT/X, etc.)
  Description : ITP: dnspython: DNS module for python

(Include the long description here.)

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#301423: SASL Configuration Location Broken

[LaMont Jones]

On Tue, Apr 05, 2005 at 02:41:33PM -0700, [EMAIL PROTECTED] wrote:
> Thanks - I encountered this problem & saved some time thanks to your 
> report - except that you meant /usr/lib/sasl2/smtpd.conf - right?
> /var/... didn't work - /usr/... did : )

/usr/ - where it doesn't belong, by policy...

hence the next upload restores the default location to
/etc/postfix/sasl, while it should still find and use config files
in /usr/lib/sasl2.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304559: postfix: upgrade doesn't work cleanly

[LaMont Jones]

On Thu, Apr 14, 2005 at 01:58:32AM +0200, Adrian Bunk wrote:
> Installing new version of config file /etc/postfix/postfix-files ...
> postconf: error while loading shared libraries: libpostfix-global.so.1: 
> cannot open shared object file: No such file or directory

Are there any diversions of postfix stuff on the machine still?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#335734: postfix with TLS cannot locate libz.so

[LaMont Jones]

reassign 335734 libssl0.9.8
merge 335734 335271
--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#331684: Remove bidwatcher from the archive

[LaMont Jones]

Package: ftp.debian.org

Please remove bidwatcher from the archive - it's broken, has outstanding
security vuls, and upstream has been a bit distracted lately.  We'll
re-upload it when there's a new version that once again works.

thanks
lamont


--
On Tue, Oct 04, 2005 at 10:48:20AM +0200, Moritz Muehlenhoff wrote:
> I'm currently going through all open security bugs. IIRC from the
> Oldenburg meeting you wanted to get rid of bidwatcher completely,
> can you please file a bug against ftp.debian.org and request it's
> removal?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327070: Essential package util-linux depends on priority=extra slang1a-utf8

[LaMont Jones]

On Wed, Sep 07, 2005 at 02:12:48PM +0200, Ariel Garcia wrote:
> An essential/required package like util-linux shouldn't depend on one 
> (slang1a-utf8) which is Priority: extra , right?

Which is why it now Depends: libslang2, which is priority important.

Which is to say, libslang2 is really required...

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#307210: patch for sa_restorer bug

[LaMont Jones]

tags 307210 + patch
--
The patch below fixes the problem.

thanks,
lamont


diff -ur t/nufw-1.0/src/nuauth/authsrv.c nufw-1.0/src/nuauth/authsrv.c
--- t/nufw-1.0/src/nuauth/authsrv.c 2005-03-03 01:23:54.0 -0700
+++ nufw-1.0/src/nuauth/authsrv.c   2005-09-14 20:09:44.0 -0600
@@ -704,8 +704,8 @@
myaudit->cache_hit_nb = 0;
 
 
+   memset(&act,0,sizeof(act));
act.sa_handler=&process_poll;
-   act.sa_restorer = NULL;
act.sa_flags = SIGPOLL;
if (sigaction(SIGPOLL,&act,NULL) == -1){
printf("could not set signal");
@@ -713,7 +713,6 @@
}
 
act.sa_handler=&process_usr1;
-   act.sa_restorer = NULL;
act.sa_flags = SIGUSR1;
 
if (sigaction(SIGUSR1,&act,NULL) == -1){
@@ -722,7 +721,6 @@
}
 
act.sa_handler=&process_usr2;
-   act.sa_restorer = NULL;
act.sa_flags = SIGUSR2;
 
if (sigaction(SIGUSR2,&act,NULL) == -1){
diff -ur t/nufw-1.0/src/nufw/main.c nufw-1.0/src/nufw/main.c
--- t/nufw-1.0/src/nufw/main.c  2005-03-03 01:23:33.0 -0700
+++ nufw-1.0/src/nufw/main.c2005-09-14 20:39:00.0 -0600
@@ -320,8 +320,8 @@
 exit(1);
 }
 
+memset(&act,0,sizeof(act));
 act.sa_handler = &process_usr1;
-act.sa_restorer = NULL;
 act.sa_flags = SIGUSR1;
 if (sigaction(SIGUSR1,&act,NULL) == -1)
 {
@@ -330,7 +330,6 @@
 }
 
 act.sa_handler = &process_usr2;
-act.sa_restorer = NULL;
 act.sa_flags = SIGUSR2;
 if (sigaction(SIGUSR2,&act,NULL) == -1)
 {
@@ -339,7 +338,6 @@
 }
 
 act.sa_handler = &process_poll;
-act.sa_restorer = NULL;
 act.sa_flags = SIGPOLL;
 if (sigaction(SIGPOLL,&act,NULL) == -1)
 {



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#308693: udev: Doesn't create /dev/rtc on amd64

[LaMont Jones]

tags 308693 + wontfix
--

hwclockfirst.sh must run before modules are loaded [1], therefore, any
kernel which is foolish enough to have CONFIG_RTC=m will have errors in
hwclockfirst.sh, and the accompanying issues found in Bug#50572.

The good news is that hwclock.sh runs shortly after that, and will set
the time, providing pre-hwclockfirst.sh behavior.

Thanks to Adrian Bunk for the pointer.

lamont

 [1] http://bugs.debian.org/50572


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#324157: util-linux: bashisms in init.d scripts

[LaMont Jones]

severity 323872 serious
close 324157
merge 324157 323872
--

Dup.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#329782: hplip: FTBFS if /usr/share/applications does not exist

[LaMont Jones]

Package: hplip
Severity: important
Version: 0.9.5-3

> checking for icon directory... none
...
> if [ "" = "hplip.desktop" ]; then \
...
> fi
> if [ "" = "hplip" ]; then \
>echo -e "?package(xbase):command=\"/usr/lib/hplip/toolbox\" 
> icon=\"/usr/share/hplip/data/images/HPmenu.png\" \\" > ./; \
>echo -e "needs=\"X11\" section=\"Application/Utility\" 
> title=\"HPLIP\" \\" >> ./; \
>echo -e "longtitle=\"HPLIP Device Manager\" \\" >> ./; \
>echo -e "mimetypes=\"\" accept_url=\"false\" 
> multiple_files=\"true\"" >> ./; \
> fi
> /usr/bin/install -c -m 644  ./ 
> /build/lamont/hplip-0.9.5/debian/tmp/usr/share/hplip/data; \
> rm -f ./
> /usr/bin/install: `./' is a directory
> rm: cannot remove `./': Is a directory

It would be better to build the file correctly, by fixing configure.in and
configure to assign good default values to ICON_PATH and ICON_FILE.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#330209: dnsutils: weird error when /etc/resolv.conf contains hostname for nameserver

[LaMont Jones]

severity 330209 wishlist
--

On Mon, Sep 26, 2005 at 08:25:28PM +0200, Daniel Brockman wrote:
>   $ echo nameserver a.root-servers.net > /etc/resolv.conf
>   $ dig example.com
>   dig: couldn't get address for ' I : not found
>   $ dig example.com
>   dig: couldn't get address for ' y ': not found
> Expected result:  I'm not sure, but I'm pretty sure that the
> error message could be improved.  At the very least, the
> message should be consistent across invocations.

Syntax for resolv.conf is 'nameserver dot.ted.quad.IP', not a name.  I
suppose that the resolver could be slowed down to check that the admin
hasn't goofed, but

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#326110: sudo: Requires password for NOPASSWD invocation

[LaMont Jones]

On Thu, Sep 01, 2005 at 01:45:37PM -0700, Ryan Lovett wrote:
> However, when otheruser attempts to run the same command as an unlisted
> user, sudo prompts for a password:

This is correct behavior.  For a similar example, try logging into the
system with a non-existant user: you will be prompted for a password
before being denied access, even though the system knows that no
password will suffice before asking.

Exiting immediately leaks information about what may and may not be
done.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#43486: getty/init/X locking issues

[LaMont Jones]

On Tue, Sep 06, 2005 at 04:28:28PM +0200, Samuel Thibault wrote:
> LaMont Jones, le Tue 06 Sep 2005 08:26:27 -0600, a écrit :
> > And vt 2-15 when opened to check them, are also busy...
> No: vt_1_ is opened to check them.

And _WE_ have them open as stdin.

lamont

Bug#43486: getty/init/X locking issues

[LaMont Jones]

On Mon, Sep 05, 2005 at 10:26:09PM +0200, Samuel Thibault wrote:
> I hope to have found some correct fix, please see patch. Yes, linux has
> been providing VT_GETSTATE since something like 1.0.
> 
> Only vt 2-15 can be checked: 1 is always busy, and the size of the mask
> is limited. But that should be sufficient for normal use. If somebody
> really wants more, he can just set vts by hand.

And vt 2-15 when opened to check them, are also busy...  it's a broken
implementation, as per the comments when we ripped it back out.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#326961: FTBFS: normal.c heap corrution due to table overflow

[LaMont Jones]

Package: iproute
Version: 20041019-1
Severity: serious
Tags: patch

When tc/normal.c is populating the table that it callocs, it is possible
that it will get TABLESIZE for an answer, and thereby overrun the
table.  Depending on glibc's mood, this may or may not cause the library
to abort the detected heap corruption.

Additionally, the arguments to calloc are backwards.

The patch below fixes this.

lamont


=
#! /bin/sh /usr/share/dpatch/dpatch-run
## normal.dpatch by LaMont Jones <[EMAIL PROTECTED]>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Correct calloc call in normal to avoid running off the end of the
## DP: table.

@DPATCH@
diff -urNad iproute-20041019/tc/normal.c 
/tmp/dpep.eEsnGf/iproute-20041019/tc/normal.c
--- iproute-20041019/tc/normal.c2004-10-19 14:49:02.0 -0600
+++ /tmp/dpep.eEsnGf/iproute-20041019/tc/normal.c   2005-09-06 
14:42:16.0 -0600
@@ -26,7 +26,7 @@
double x, *table;
int i, n;
 
-   table = calloc(sizeof(double), TABLESIZE);
+   table = calloc(TABLESIZE+1, sizeof(double));
if (!table) {
fprintf(stderr, "Not enough memory\n");
return 1;
=
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages iproute depends on:
ii  libc6 2.3.5-0ubuntu1 GNU C Library: Shared libraries an

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#326961: Acknowledgement (FTBFS: normal.c heap corrution due to table overflow)

[LaMont Jones]

Sadly, I spoke too quickly... Here's the corrected patch, which also
fixes tc/paretonormal.c :-(

lamont
#! /bin/sh /usr/share/dpatch/dpatch-run
## normal.dpatch by LaMont Jones <[EMAIL PROTECTED]>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Correct calloc call in normal to avoid running off the end of the
## DP: table.

@DPATCH@
diff -urNad iproute-20041019/tc/normal.c 
/tmp/dpep.9YHbob/iproute-20041019/tc/normal.c
--- iproute-20041019/tc/normal.c2004-10-19 14:49:02.0 -0600
+++ /tmp/dpep.9YHbob/iproute-20041019/tc/normal.c   2005-09-06 
15:48:45.0 -0600
@@ -26,7 +26,7 @@
double x, *table;
int i, n;
 
-   table = calloc(sizeof(double), TABLESIZE);
+   table = calloc(TABLESIZE+1, sizeof(double));
if (!table) {
fprintf(stderr, "Not enough memory\n");
return 1;
diff -urNad iproute-20041019/tc/paretonormal.c 
/tmp/dpep.9YHbob/iproute-20041019/tc/paretonormal.c
--- iproute-20041019/tc/paretonormal.c  2004-10-19 14:49:02.0 -0600
+++ /tmp/dpep.9YHbob/iproute-20041019/tc/paretonormal.c 2005-09-06 
15:49:01.0 -0600
@@ -54,7 +54,7 @@
double *table;
int i,n;
 
-   table = calloc(TABLESIZE, sizeof(double));
+   table = calloc(TABLESIZE+1, sizeof(double));
if (!table) {
fprintf(stderr, "Out of memory!\n");
exit(1);

Bug#320946: util-linx: Uninstallable due to slang1 transition

[LaMont Jones]

On Tue, Aug 02, 2005 at 12:02:37PM +0200, Michael Banck wrote:
> util-linux needs to be changed to account for the slang1 transition.
> This is because util-linux has a versioned Pre-Depends on slang1a-utf8,
> while slang1a-utf8 is now merely provided by libslang1-utf8, which does
> not work with our packaging tools currently, AIUI.

I would love to do so, but util-linux is FTBFS because of libc6 headers
that remain broken.  grave bug filed against libc6-dev.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#373648: new boinc ports

[LaMont Jones]

On Wed, Jun 14, 2006 at 09:29:29PM +0200, Robert Millan wrote:
> Package: nmap
> Version: 4.10-1
> Severity: wishlist
> Tags: patch
> 

Fixed in 4.11-1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#405320: postfix: [INTL:ca] Catalan debconf templates translation update

[LaMont Jones]

On Tue, Jan 02, 2007 at 04:06:24PM +0100, Jordà Polo wrote:
> Here is an update for the Catalan debconf templates translation.

Here's a slightly fuzzy version of the file for 2.3.6-2

lamont
#
# Catalan translation for postfix package.
# Copyright (C) 2006 LaMont Jones.
# This file is distributed under the same license as the postfix package.
#
# Jordà Polo <[EMAIL PROTECTED]>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: 2.3.5-3\n"
"Report-Msgid-Bugs-To: [EMAIL PROTECTED]"
"POT-Creation-Date: 2007-01-22 13:58-0700\n"
"PO-Revision-Date: 2006-12-29 20:33+0100\n"
"Last-Translator: Jordà Polo <[EMAIL PROTECTED]>\n"
"Language-Team: Català \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Correct dynamicmaps.cf for upgrade?"
msgstr "Voleu esmenar dynamicmaps.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:1001
#, no-c-format
msgid ""
"Postfix version 2.0.2 and later require changes in dynamicmaps.cf. "
"Specifically, wildcard support is gone, and with it, %s expansion.  Any "
"changes that you made to dynamicmaps.cf that relied on these features will "
"need to be fixed by you.  Failure to correct these will result in a broken "
"mailer."
msgstr ""
"A partir de la versió 2.0.2 de Postfix es requereixen canvis a dynamicmaps."
"cf. Més concretament, ja no hi ha suport per a comodins, i per tant tampoc "
"per a l'expansió %s. Haureu de solucionar manualment qualsevol canvi "
"realitzat a dynamicmaps.cf que depengui d'aquestes característiques. Si no "
"solucioneu això, és possible que tingueu problemes amb l'administrador de "
"correu."

#. Type: boolean
#. Description
#: ../templates:1001
#, no-c-format
msgid ""
"Should dynamicmaps.cf be automatically changed?  Decline this option to "
"abort the upgrade, giving you the opportunity to eliminate wildcard and %s-"
"expansion-dependent configuration.  Accept this option if you have no such "
"configuration, and automatically make dynamicmaps.cf compatible with Postfix "
"2.0.2 in this respect."
msgstr ""
"S'ha de canviar el fitxer dynamicmaps.cf automàticament? Declineu aquesta "
"opció si voleu avortar l'actualització; això us donarà l'oportunitat "
"d'eliminar els comodins i les configuracions dependents de l'expansió %s. "
"Accepteu si no teniu cap configuració d'aquest tipus i voleu regenerar el "
"fitxer dynamicmaps.cf automàticament per a que sigui compatible amb Postfix "
"2.0.2 en aquest sentit."

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../templates:2001 ../templates:5001
msgid "Correct master.cf for upgrade?"
msgstr "Voleu esmenar master.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Postfix version 2.1 and later require new services in master.cf."
msgstr "Postfix 2.1 i posteriors requereixen nous serveis a master.cf."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Should this configuration be automatically added to master.cf?  Decline this "
"option to abort the upgrade, giving you the opportunity to add this "
"configuration yourself.  Accept this option to automatically make master.cf "
"compatible with Postfix 2.1 in this respect."
msgstr ""
"S'ha d'afegir automàticament aquesta configuració al fitxer master.cf? "
"Declineu aquesta opció per avortar l'actualització; això us donarà "
"l'oportunitat d'afegir aquesta configuració manualment. Accepteu si preferiu "
"regenerar el fitxer master.cf automàticament per a que sigui compatible amb "
"Postfix 2.1 en aquest sentit."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Add mydomain entry in main.cf for upgrade?"
msgstr ""
"Voleu afegir l'entrada «mydomain» al fitxer main.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(2) is not a fully-qualified "
"domain name (FQDN)."
msgstr ""
"A partir de la versió 2.3.3-2 de Postfix es requereixen canvis a main.cf. "
"Més concretament, s'ha d'especificar «mydomain», ja que hostname(2) no és un "
"nom de domini c

Bug#291288: SPF patched postfix

[LaMont Jones]

On Tue, Jan 23, 2007 at 04:50:04PM -0600, Taral wrote:
> I've patched up 2.3.6-2 with SPF and made the bits available:
> http://taral.dreamhost.com/postfix_2.3.6-2.spf.diff.gz
> http://taral.dreamhost.com/postfix_2.3.6-2.spf.dsc

I'll upload SPF when upstream includes it.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#398646: postfix-tls: dovecot-sasl support

[LaMont Jones]

On Tue, Nov 14, 2006 at 09:34:21PM +0100, Kurt Ã?rdal wrote:
> Can you please support dovecot sasl in the 
> postfix-tls package as a choice of sasl
> implementations?

At first glance, it appears that this might already be there...

With the version of postfix in testing, see if installing dovecot and
"smtpd_sasl_type=dovecot" in main.cf works...  If not, I've never used
dovecot, so it'll be a bit before I delve into it.

lamont

Bug#398180: FTBFS: experimental on alpha

[LaMont Jones]

On Sun, Nov 12, 2006 at 10:36:10AM +0100, Alexander Wirt wrote:
> Package: postfix
> Version: postfix_2.4-20061019-2
> Severity: normal
> 
> xsasl_cyrus_server.c:179: error: 'xsasl_getconfpath' undeclared here
> (not in a

I believe that this is fixed in the latest postfix experimental upload
(anything with 2.3.5-1 merged in should be good.)

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#394172: FTBFS on ia64: analyt.c:233: relocation truncated to fit: GPREL22 ...

[LaMont Jones]

On Sun, Nov 05, 2006 at 03:31:05PM +0100, Michael Banck wrote:
> On Sun, Nov 05, 2006 at 02:32:00PM +0100, Martin Michlmayr wrote:
> Can you try adding "CFLAGS=-g -Wall -ffunction-sections" at the bottom
> of debian/rules?  It works fine on merulo at least.

-ffunction-sections stands a good chance of fixing it.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#406037: Acknowledgement (gnuradio_3.0.2-2(ia64/unstable): FTBFS: sdcc SEGV)

[LaMont Jones]

reassign 406037 sdcc
severity 406037 normal
merge 394394 406037
--

oops.  already filed this bug.

sorry,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#406041: qscintilla is not binNMU-safe

[LaMont Jones]

Package: qscintilla
Version: 1.6-2

Because libqscintilla-dev Depends: on the exact version of
libqscintilla6 (or whatever soname), and is arch: all while the library
is arch-specific, binNMU's of qscintilla result in an unininstallable
libqscintilla-dev on whatever architecture does the binNMU.

This is the cause of the upload of qscintilla_1.6-2.1, which has no
source change from 1.6-2 other than debian/changelog.  That is, I didn't
make qscintilla binNMU-safe, but rather just worked around the problem.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#406329: twinkle_1:0.9-6(ia64/testing): FTBFS: unresolved externals

[LaMont Jones]

On Wed, Jan 10, 2007 at 08:03:55PM +, Mark Purcell wrote:
> I'm also a little curious that this is only happening on ia64, if it was a 
> source problem I would imagine it would also be occurring on other arch's as 
> well.
> Perhaps we could reschedule a rebuild, or how can I get the necessary 
> build-deps setup on an ia64, so I can try and debug.

I'll freshen and clean the chroot and do a new build.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#317018: postfix and virtual develery with mysql

[LaMont Jones]

On Sat, Nov 25, 2006 at 06:22:39PM -0500, Andres Salomon wrote:
> -BEGIN PGP SIGNED MESSAGE-
> + # if postfix-mysql is installed, attempt to ensure mysqld's
> + # socket is available if we can.
> + [ -f /usr/lib/postfix/dict_mysql.so ] && \
> + [ ! -d var/run/mysqld ] && {
> + mkdir -p var/run/mysqld
> + mount --bind /var/run/mysqld var/run/mysqld || true
> + }

Note that since the script runs -e, this would be a bad way to code the
conditional

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389645: Shallo I fix it? Shall I NMU?

[LaMont Jones]

On Mon, Nov 27, 2006 at 06:04:16PM +0100, Eduard Bloch wrote:
> if you are busy with your Ubuntu work, I can understand that. It is not
> as important as the boring Debian stuff. But please react to this
> message. Shall I fix the problem and NMU util-linux? Is anybody working
> on that?

And yes, since it wasn't a bug, I was ignoring it while I did HP
stuff, and fixed some postfix and util-linux bugs.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#394877: Processed: Re: Bug#394877: base: device files are not used uniquely

[LaMont Jones]

What are the contents of /proc/mounts?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#396186: bind9: Installation breaks with shadow passwords disabled

[LaMont Jones]

reassign 396186 adduser
severity 396186 normal
merge 396186 330471
--

This is an adduser bug, not a bind9 bug.

lamont

On Mon, Oct 30, 2006 at 11:52:29AM +, Kevin Campbell wrote:
> Package: bind9
> Version: 1:9.3.2-P1.0-1
> Severity: important
> 
> The bind9 installation appears to fail when shadow passwords are disabled
> 
> Adding group `bind' (GID 112) ...
> Done.
> Adding system user `bind' (UID 107) ...
> Adding new user `bind' (UID 107) with group `bind' ...
> chage: the shadow password file is not present
> /usr/bin/chage failed with return code 15, shadow not enabled, password aging 
> cannot be set. Continuing.
> Not creating home directory `/var/cache/bind'.
> wrote key file "/etc/bind/rndc.key"
> Starting domain name service...: bind.
>   
>
>  
> Enabling shadow passwords and removing / reinstalling resolves the issue.
> 
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.16-xen
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> 
> Versions of packages bind9 depends on:
> ii  adduser   3.97   Add and remove users and groups
> ii  libbind9-01:9.3.2-P1.0-1 BIND9 Shared Library used by BIND
> ii  libc6 2.3.6.ds1-4GNU C Library: Shared libraries
> ii  libdns21  1:9.3.2-P1.0-1 DNS Shared Library used by BIND
> ii  libisc11  1:9.3.2-P1.0-1 ISC Shared Library used by BIND
> ii  libisccc0 1:9.3.2-P1.0-1 Command Channel Library used by 
> BI
> ii  libisccfg11:9.3.2-P1.0-1 Config File Handling Library 
> used 
> ii  liblwres9 1:9.3.2-P1.0-1 Lightweight Resolver Library 
> used 
> ii  libssl0.9.8   0.9.8c-3   SSL shared libraries
> ii  lsb-base  3.1-15 Linux Standard Base 3.1 init 
> scrip
> ii  netbase   4.25   Basic TCP/IP networking system
> 
> bind9 recommends no packages.
> 
> -- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#396062: nmap does not work on distant host

[LaMont Jones]

On Sun, Oct 29, 2006 at 04:37:09PM +0100, Fabrice Dagorn wrote:
> Architecture : ARM
> Kernel Version : 2.6.16
> Nmap does not work on my NSLU2 (Debian testing).
> It works on localhost, but nowhere else.

What does tcpdump show as the activity during the nmap 192.168.2.251?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392667: closed by LaMont Jones <[EMAIL PROTECTED]> (Re: Bug#392667: bind9 dependency problem in stable)

[LaMont Jones]

On Tue, Oct 31, 2006 at 09:53:51PM -0600, Mike wrote:
> I have been using debian for several years now and I think it is the best 
> Linux distribution. It's just such a shame that all the people actually 
> associated with it are such jerks. This was most definitely not a user error. 
> I even put in the bug report the exact command I ran and the exact output. I 
> also stated what I had in my sources list which is what is in a default 
> stable install. I have since worked around the issue, but that does not mean 
> that the problem was user error. There was and as far as I know still is a 
> problem with a stock stable install if you want to install bind9. If you 
> don't feel like supporting bind9 for stable then pull it out, but it 
> certainly broken at this point.

The most likely situation is a broken mirror, if there's nothing on hold
on your machine...  The package is certainly fine in the archive.

lamont

Stock stable system:
% apt-get -ud install bind9
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
  adduser ifupdown iputils-ping libdns16 libisc7 libisccc0 libisccfg0
  liblwres1 libwrap0 net-tools netbase netkit-inetd tcpd
Suggested packages:
  liblocale-gettext-perl dnsutils bind9-doc iproute dhcp3-client dhcp-client
  ppp
The following NEW packages will be installed:
  adduser bind9 ifupdown iputils-ping libdns16 libisc7 libisccc0 libisccfg0
  liblwres1 libwrap0 net-tools netbase netkit-inetd tcpd
0 upgraded, 14 newly installed, 0 to remove and 1 not upgraded.
Need to get 1272kB/1929kB of archives.
After unpacking 5554kB of additional disk space will be used.
Do you want to continue? [Y/n] 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#398396: postfix: FTBFS on hurd-i386: make tidy fails in clean rule

[LaMont Jones]

On Mon, Nov 13, 2006 at 04:47:32PM +0100, Michael Banck wrote:
> thanks for applying the 30_hurd.dpatch, unfortunately postfix still
> FTBFS:

I don't have a hurd box to work on fixing this.  patch?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#398498: mount says loop device is writable, bit it isn't.

[LaMont Jones]

On Tue, Nov 14, 2006 at 12:13:53AM -0500, A. Costa wrote:
> This looks like one of those bugs that are so old and people are so
> accustomed to that they've ceased to think of it as bug, it just seems
> normal to them.  I didn't find a report on it in the BTS, and it seems
> there should be one...

And it's a kernel bug...  Or not, depending on how you think about it...

> 2) So I mount it as 'write':
> % mount -w -o loop /tmp/di/I4000A23.iso /mnt/tmp ; echo $?
> 0

The kernel returned success on a read/write mount request.  It's
possible that the kernel should return a failure for the mount in this
case.

> 4) Copy a file over:
> % cp /tmp/BIOS/I4100A06.EXE /mnt/tmp ; echo $?
> cp: cannot create regular file `/mnt/tmp/I4100A06.EXE': Read-only file 
> system
> 1

The underlying filesystem in the kernel returns read-only for all
writes, since it doesn't support doing them.

> Questions:
> Why does step '3)' show "rw" if it's not?

It is mounted rw - but the underlying file system doesn't support
writes.

> Suggested easy kludges, nothing low-level:
>   Parse for '-w' and an ISO9660 mount, and return an error.
>   Don't show ISO9660 as 'rw'.

That's a kludge - not a fix.  having the filesystem return an error is a
correct solution.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#398449: this is bug #386226

[LaMont Jones]

severity 398449 important
merge 398449 386226
--

On Thu, Nov 16, 2006 at 03:36:18AM +0100, Vincent Lefevre wrote:
> See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386226

Merged.

Thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#399370: util-linux: split system time utilites (collect all bugs, wish to maintain (help))

[LaMont Jones]

On Sun, Nov 19, 2006 at 03:10:38PM +0100, Oleg Verych wrote:
> Upsteram util-linux package is unmaintained, even lkml got thread on it:
> 
> As i'm interesting in timekeeping, updated hwclock.sh, now seeing how
> many clock related bugs unsorted, i want to split package (and try to
> deal with that critical mass of bugs).

The correct solution here is to work with the other distros on
maintaining util-linux, not splitting a source package that is not split
upstream.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#399802: Hostname cannot be canonicalized

[LaMont Jones]

On Tue, Nov 21, 2006 at 09:16:54PM -0800, Jack Bates wrote:
> I don't set myhostname in main.cf. Postfix used to successfully get
> myhostname from the resolver or from /etc/mailname. I confirmed that
> `hostname --fqdn` still reports tor.lat, and /etc/mailname still
> contains tor.lat, but Postfix now uses tor.localdomain.
> 
> I found bug #26784 regarding Postfix using /etc/mailname. I think
> Postfix should use /etc/mailname for myhostname since the mailname man
> page says it is:

Postfix should default $myhostname to the same result as 'hostname --fqdn'.

It should not set $myhostname to the contents of /etc/mailname.

I still need to figure out why it's not doing that.
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#294210: postfix can not start after fresh install

[LaMont Jones]

tags 294210 - patch
--
No patch given.

On Tue, Feb 08, 2005 at 03:14:46PM +0100, Fabien VALLON wrote:
> Package: postfix
> Version:  2.1.5-5

Fixed in 2.1.5-6

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#295633: expect_5.42.1-1.2(i386/unstable): FTBFS: really build-depends autoconf2.13

[LaMont Jones]

Package: expect
Version: 5.42.1-1.2
Severity: serious
Tags: patch

1) On a machine with autoconf installed, the package fails to build - it
really build-depends on autoconf2.13, not autoconf.  A patch to fix this
is available from http://patches.ubuntu.com/patches/expect.autoconf.diff

2) config.guess and config.sub are out-of-date.  Please see the
autotools-dev README file for some options on making them current.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#290170: mount segfaults when mounting a new partition (160 GB)

[LaMont Jones]

On Wed, Jan 12, 2005 at 06:18:21PM -0500, Jeff Abrahamson wrote:
> (Log output from first call is below, second call never returns, no
> log output.)

That's the kernel segfaulting, not mount.

> Jan 12 18:09:25 krypton kernel: EXT3-fs error (device ide0(3,65)): 
> ext3_check_de
> scriptors: Block bitmap for group 1 not in group (block 0)!
> Jan 12 18:09:25 krypton kernel: Unable to handle kernel NULL pointer 
> dereference
>  at virtual address 0074
> Jan 12 18:09:25 krypton kernel:  printing eip:
> Jan 12 18:09:25 krypton kernel: e083e354

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#257096: noexec /var breaks postfix chroot

[LaMont Jones]

On Thu, Mar 03, 2005 at 05:11:55PM +0100, Klaus Fuerstberger wrote:
> With Postfix 2.1.4-5 the Problem still appears. No Mails reaches the 
> relayhost on my Firewalls with stmp=chroot and /var mounted noexec.

Your choices are:
1) mount /var/ without noexec
2) unchroot postfix

This is because it uses .so files for name resolution, that are loaded
from the chroot.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#203433: nmap false positive

[LaMont Jones]

On Mon, Mar 07, 2005 at 06:04:15PM -0500, Stephen Gran wrote:
> It's a non-issue:

That's why it's wishlist and tagged 'wontfix'.  It's not an nmap
problem.  OTOH, closing it will only tend to get other people to submit
it as they encounter this same non-issue.

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#277532: nmap -oS segfault

[LaMont Jones]

On Tue, Mar 08, 2005 at 02:43:07AM +0100, christophe wrote:
> Ok, iirc I replied directly to floydor, instead of replying to the list,
> apologies for that.
> 
> As the nmap debian package doesn't have debug turned on, I downloaded
> the last nmap version (3.81) from insecure.org and compiled it with
> --debug.

Uh, works here for me...  What kind of host is at 192.168.0.1 for you?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#238151: fix for #238151

[LaMont Jones]

severity 238151 important
--

On Fri, Feb 25, 2005 at 02:12:53PM +0100, Bastian Blank wrote:
> I prepare a porter NMU for util-linux to fix #238151 according to
> Developers reference 5.10.2.2, it will hit unstable in 7 days from now,
> 4.3.2005.

Diff???

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410075: smbmount not compatible with utf-8

[LaMont Jones]

reassign 410075 smbfs
--

clearly not a mount bug, possibly an smbmount bug???

lamont

On Wed, Feb 07, 2007 at 03:55:49PM +0100, Jean-Michel wrote:
> Package: mount
> Version: 2.12r-15
> Severity: normal
> 
> On my new debian etch, which is about full-UTF8 (by default),
> I have a filesystem exported via samba.
> 
> Here I have a file which is correctly display both in local and from
> windows.
> 
> However, when I add //server/echange  /mnt/essai  smbfs dome_options
> 0   2
> in /etc/fstab
> and mount it, the file is not correctly displayed.
> 
> t_manège is displayed t_man?ge
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -- System Information:
> Debian Release: 4.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.18-4-amd64
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> 
> Versions of packages mount depends on:
> ii  libblkid 1.39+1.40-WIP-2006.11.14+dfsg-1 block device id library
> ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
> ii  libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library
> 
> mount recommends no packages.
> 
> -- no debconf information

Bug#410871: 2.3.7-2 still not installable

[LaMont Jones]

On Wed, Feb 14, 2007 at 11:58:07AM +, Magnus Therning wrote:
> I just tried upgrading to 2.3.7-2 and it failed in the exact way
> described in bug #410871 (verified by adding the 'set -x' in
> postfix.postinst).  My attempts to install postfix from experimental
> failed in the same way, as did downgrading to Etch's version.

What version of update-inetd do you have?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410871: 2.3.7-2 still not installable

[LaMont Jones]

On Wed, Feb 14, 2007 at 11:58:07AM +, Magnus Therning wrote:
> I just tried upgrading to 2.3.7-2 and it failed in the exact way
> described in bug #410871 (verified by adding the 'set -x' in
> postfix.postinst).  My attempts to install postfix from experimental
> failed in the same way, as did downgrading to Etch's version.

Trying another tactic, can you add this to /etc/apt/sources.list:
deb http://people.debian.org/~lamont/postfix /
And see if postfix-2.3.7-3~0 fixes the issue for you?

thanks,
lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410871: 2.3.7-2 still not installable

[LaMont Jones]

On Wed, Feb 14, 2007 at 02:23:43PM +, Magnus Therning wrote:
> On 2/14/07, LaMont Jones <[EMAIL PROTECTED]> wrote:
> The installation worked fine, but there now seems to be something else 
> # mailq
> postqueue: warning: Mail system is down -- accessing queue directly

If postfix was not running before the upgrade, I believe that it doesn't
restart it after the upgrade.  That could be what it is...

if you start postfix (/etc/init.d/postfix start), and then dpkg
--reinstall the .deb, does it restart it?

lamont


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]