Package: dhcpcd
Version: 1:3.2.3-3
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of dhcpcd_1:3.2.3-3 on caballero by sbuild/ia64 98
Build started at 20090831-2336
[...]
** Using build dependencies supplied by package:
Build-Depends: debhelper
Package: trousers
Version: 0.3.2-4
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of trousers_0.3.2-4 on caballero by sbuild/ia64 98
Build started at 20090831-2304
[...]
** Using build dependencies supplied by package:
Build-Depends: debhelper
Package: jconv
Version: 0.8.1-1
Severity: serious
There was an error while trying to autobuild your package:
Depending on the architecture, the name of libc6 is, um, different.
Automatic build of jconv_0.8.1-1 on caballero by sbuild/ia64 98
Build started at 20091105-1957
[...]
** Using
REQUIRE that name resolution work on the machine.
Therefore, $named is the correct thing to require.
My next bit of investigation will be to look into what Provides: $named
when dnsmasq is NOT installed.
lamont
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
as
whitespace by the parser. (They're completely optional.)
lamont
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: anope
Version: 2.0.2-1
Severity: serious
If the daemon is not running, reload should fail. It currently passes.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
to dig out, since it
errors out after the daemon forks...
Either the docs or source needs to change.
Workaround: For now, I just went with 'name = services.log', which
takes care of everything somewhat nicely.
lamont
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
don't care either way on that part.
patch attached
lamont
From ce09340e7c51f23c3e2b08b5e069355aa8eecdad Mon Sep 17 00:00:00 2001
From: LaMont Jones lam...@canonical.com
Date: Thu, 23 Apr 2015 08:16:06 -0600
Subject: [PATCH] add m_sql and m_regex_{posix,pcre} modules
---
debian/control | 2
On Thu, Apr 23, 2015 at 11:34:43PM +0100, Dominic Hargreaves wrote:
On Thu, Apr 23, 2015 at 08:29:14AM -0600, LaMont Jones wrote:
Package: anope
Version: 2.0.2-1
Severity: serious
If the daemon is not running, reload should fail. It currently passes.
Really? A quick review of init
Package: anope
Severity: wishlist
--
Please include the attached apparmor profile as part of the packge.
It should be delivered as /etc/apparmor.d/usr.sbin.anope.
See also https://wiki.debian.org/AppArmor
thanks,
lamont
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Thu, May 21, 2015 at 12:31:43PM +0200, Dominic Hargreaves wrote:
On Wed, May 20, 2015 at 09:19:26PM -0600, LaMont Jones wrote:
On Wed, May 20, 2015 at 08:24:55PM +0100, Dominic Hargreaves wrote:
# we need libraries, and we need to be able to restart
/usr/lib{,32,64}/** mr,
/usr
Package: wnpp
Severity: wishlist
--
lamont
be a "almost correct" diff for bug 786768. This will be fixed in
3.0.4-2
lamont
ostfix/sbin
and then I'll be making sure that shlib loading doesn't get to traverse
into the subdirectory.
One way or another, I'd expect that to get uploaded before the weekend
is over. (Targetting Friday sometime, but I've learned to be
conservative in what I commit.)
lamont
fixed 3.0.3-2
--
3.0.3-2 has the migration code to properly rewrite dynamicmaps.cf to reflect
upstream changes when incorporating shared libraries and dynamicmaps.
lamont
On Thu, Apr 12, 2012 at 08:22:17PM +0400, Michael Tokarev wrote:
> On 12.04.2012 18:51, Debian Bug Tracking System wrote:
> > [LaMont Jones]
> >* Link with and use sqlite when building dict_sqlite. add sqlite
> > dictionary to dynamicmaps.cf. Closes: #666950
>
ive mirror that is there.
Please fix the validator to allow hyphens in the tld_re.
The fix for <https://code.djangoproject.com/ticket/25452#comment:2> appears to
be when this regression was introduced.
lamont
o land
it in sid shortly.
lamont
ters, what does mail.log have to say about the situation?
lamont
stfix/master[8473]: warning:
> /usr/libexec/postfix/smtpd: bad command startup -- throttling
What revision did you upgrade from? and can you attach:
1) the contents of /etc/postfix/main.cf
2) the output of: postconf | grep directory
lamont
cv to return LWRES_R_IOERROR to
> lwres_context_sendrecv()
>
> This renders libnss-lwres useless.
Just to eliminate the obvious, please provide the output of
'sudo lsof -np :921'
from the machine??
The trace would be easy to explain if lwresd is not listening on that
port...
thanks,
lamont
othing in the package adds this
line, not just because it would violate Debian policy. Simply delete
these two lines from main.cf. For extra credit, figure out how they got
there in the first place. Since it was "fixing problem caused by package
maintainer", we can bet that it's not part of the packaging...
lamont
n this state.
>
> This is what I get in systemctl status:
>
> ene 19 13:38:04 named[1020]: ENGINE_by_id failed (crypto failure)
Can you provide a named.conf that reproduces the issue?
thanks,
lamont
On Sun, Jan 15, 2017 at 06:09:35PM +0300, Sergey Alyoshin wrote:
> Package: postfix
> Version: 3.1.3-6
> Priority: wishlist
> Tags: l10n patch
This file is unchanged from one that landed in the source tree on the 9th..
Was that intentional?
lamont
: 0.0.0.0
802.1q VLAN ID : Disabled
802.1q VLAN Priority: 0
Cipher Suite Priv Max : Not Available
Bad Password Threshold : Not Available
#
The iLo in question is configured with a static IPv6 address (though SLAAC made
no difference), and is quite reachable:
ssh -l lamont 2001
reach my pcre map file.
Try 755 -- postfix is picky about world writable directories, iirc.
> Did you use postmap [1] to update the map?
pcre maps do not need postmap compilation (nor does postmap accept such
requests.)
The next thing to do would be to add some -v options (3 or 4 of them) to
the cleanup line in master.cf and see what it has to spew into the logs.
FWIW, pcre maps seem to work just fine for me in 3.1.3-4.
lamont
On Fri, Jan 06, 2017 at 03:22:34PM +0100, Thomas Leuxner wrote:
> $ grep lmtp /etc/postfix/master.cf
> lmtp unix - - y - - lmtp
Is there by any chance any trailing whitespace on that line?
lamont
interested
in the configuration of the host that led to this, so that we can make that
path work better.
lamont
On Sat, May 20, 2017 at 12:29:15PM +0100, James Cowgill wrote:
> On 11/03/17 16:32, Herwig Burgert wrote:
> > Package: postfix
> >
> > Version: 3.1.4-4
++.)
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
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
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
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]
/proc/sys/kernel/unaligned-trap
and try again.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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
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]
.
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]
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
been a few packages like
this, and tetex-$mumble seems to ring a bell as one of the b0rken ones.
lamont
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
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
, 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]
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]
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
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
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]
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
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
reassign 335734 libssl0.9.8
merge 335734 335271
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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
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]
_before_ modules are
loaded. In fact, I believe that we're pretty close to the point where I
can drop hwclockfirst entirely, although anyone with /dev/rtc really
should not be building it as a module, if they want time to be
correct, at least with older versions of module-init-tools...
lamont
On Mon, Aug 14, 2006 at 12:07:37PM +0200, Udo Mueller wrote:
Please send me a copy of /etc/postfix/postfix-script.
Attached
Interestingly, that is not the version of postfix-script delivered by
the package... Any chance you are running an old copy of
postfix-script?
lamont
of that file.
lamont
On Sat, Dec 24, 2005 at 09:14:02PM +0100, Beat Bolli wrote:
LaMont Jones wrote:
Does this still occur with 2.2.7-1? (or even 2.2.6-1)
Yes, unless I put disable_dns_lookups = yes in my main.cf file. I'm
still on 2.2.6-1.
Interesting... what do the following files have in them:
/etc/postfix
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
- 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]
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
or directory
Which would tend to indicate that libsvn-dev is unusable...
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
title 394784 nmap website no longer accepts fingerprints from stable NMAP
severity 394784 normal
forward 394784 [EMAIL PROTECTED]
--
Fyodor - any hints on when a compatible version of nmap will be
official?
thanks,
lamont
On Mon, Oct 23, 2006 at 01:22:21AM -0300, Alexandre Pereira Nunes wrote
... :-( paer.debian.org would be a good place
to debug the configure failure.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
...
Actually, I expect that it's a leftover from when inotify wasn't found
in the headers everywhere yet.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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
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
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
PUQ0PUM1PUQyPUMyPUQyPUNGPUM0LD89?=
Date: Wed, 1 Nov 2006 12:17:08 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset=koi8-r;
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express
of fixing it.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
] \
+ [ ! -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
, 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]
tags 382386 + patch
thanks
This adds support for HPPA linux machines.
lamont
diff -ur t/tightvnc-1.2.9/Xvnc/config/cf/linux.cf
tightvnc-1.2.9/Xvnc/config/cf/linux.cf
--- t/tightvnc-1.2.9/Xvnc/config/cf/linux.cf2006-08-10 22:50:08.0
+
+++ tightvnc-1.2.9/Xvnc/config/cf/linux.cf
Package: vpopmail-bin
Severity: serious
Version: 5.4.4-1
vpopmail-bin Depends: libmysqlclient10, which is no longer in the
archive, making the package uninstallable.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sun, Aug 13, 2006 at 04:00:29PM +0200, Udo Mueller wrote:
Patch attached but does not suppress any messages.
Please send me a copy of /etc/postfix/postfix-script.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
. This would make it easier for the Kolab Maintainers.
I still don't see this even in a postfix-2.3 snapshot.
waiting,
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
: the
restriction on the first character is relaxed to allow either a
letter or a digit. Host software MUST support this more liberal
syntax.
The patch below changes check_name so that it actually implements the
RFCs. Admittedly, it doesn't check on maximum label lengths...
lamont
reopens 343447. Correct patch applied, fixed in
2.12r-4, uploading shortly.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
newaliases
Starting Postfix Mail Transport Agent: postfixpostfix/postfix-script:
fatal: the Postfix mail system is already running
failed!
I can't reproduce this here... preinst stops postfix, and postinst
starts it... That hasn't changed in any of the recent uploads.
lamont
of possibly sensitive
information into the chroot.
I'll update the LDAP readme to reflect this.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
#443487.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[ 9239.043602] FAT: utf8 is not a recommended IO charset for FAT filesystems,
filesystem will be case sensitive!
All of which leaves me at a loss to determine what to change to remove
that.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
is a versioned Breaks, which is supported by dpkg as
of lenny, and therefore usable for lenny+1. Alas, not for lenny.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
:
[EMAIL PROTECTED]:~# ll /var/log/named/query.log
-rw-r--r-- 1 bind bind 2147483647 Aug 29 09:01 /var/log/named/query.log
Generally speaking, one wants to rotate log files LONG before they get
to 2GB...
I'll forward the report upstream.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
for this.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to deal
with making syslog happier, or (assuming it actually works) bind
mounting /dev/log. If not chrooted, then the issue is non-existent.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
connection. I don't
actively use ipv6, but I do have the localhost entries for it in my hosts
file.
What, if anything, do you have for a listen-on-v6 type directive in your
config? explicitly specifying it is likely to help.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
: yeah, it's a bug, it sucks, and the bug of aborting in the
preinst and thereby assuring a working system that a competent admin can
fix, is the best solution available to the problem at hand.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
to be best for
configuring named, no effort was made to migrate existing configs to
running as non-root.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
it when it comes down from upstream.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
about.
I'll dig into it a bit more, but I don't think that part of things is
touched at all.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
in a way that prevents rndc from working - I'd love
do better document the ways that people break it.
thanks,
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to look up
host gmx.de: Name or service not known)
What does /var/spool/postfix/etc/resolv.conf look like, and how does
that compare to /etc/resolv.conf?
This sounds far more like a resolution issue than a postfix issue...
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
to edit syslog's config file so that
it sees things when it restarts.
Once there's a way for postfix to hook up to syslogd in a
policy-conformant manner, we can fix this bug.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
this patch rolled forward to 2.5, I'll toss it at the list
again and see if we can get it into 2.6. Once it goes in upstream, I
don't mind backporting it to 2.5.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to assign this issue, just that fdisk and
mount are behaving as they should.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the idea
useful.
Given that work in this arena is ongoing, and didn't make the cut for
2.5, I'm inclined to wait for this to come down from upstream, rather
than inventing our own solution now.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
here is quite possibly that postfix's install doesn't make
dealing with a machine that needs to tweak myorigin (usually because
it's not in the DNS for the rest of the internet) easier.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
building - that'd be a debian-security question.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, and not 9.3.1. It's best to
use the docs for the version of the package that you're using, rather
than the online docs for the latest version of the package...
lamont
tags 395191 + wontfix
--
I'll add this when it comes down from ISC.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, Aug 06, 2007 at 02:42:27PM -0400, Ross Vandegrift wrote:
On Mon, Aug 06, 2007 at 12:11:46PM -0600, LaMont Jones wrote:
On Mon, Aug 06, 2007 at 12:02:24PM -0400, Ross Vandegrift wrote:
Shouldn't adding libpq-dev to the build-dep only require the pgsql
libraries? I haven't had too much
301 - 400 of 743 matches
Mail list logo
