Accepted pcre3 1:8.36-1 (source amd64) into unstable

2014-11-24 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 24 Nov 2014 22:41:12 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.36-1 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted pcre3 1:8.35-3 (source amd64)

2014-07-23 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 23 Jul 2014 21:19:41 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.35-3 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted pcre3 1:8.35-2 (source amd64)

2014-07-12 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 12 Jul 2014 23:03:47 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.35-2 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted pcre3 1:8.35-1 (source amd64)

2014-07-11 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Jul 2014 19:54:51 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.35-1 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted pcre3 1:8.31-5 (source amd64)

2014-04-23 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 23 Apr 2014 21:00:35 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.31-5 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted pcre3 1:8.31-4 (source amd64)

2014-04-18 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 18 Apr 2014 10:06:31 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.31-4 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted pcre3 1:8.31-3 (source amd64)

2014-04-08 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 08 Apr 2014 22:37:58 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.31-3 Distribution: unstable Urgency: medium Maintainer: Mark Baker m

Accepted chimera2 2.0a19-8 (source i386)

2013-05-12 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 20:22:27 +0100 Source: chimera2 Binary: chimera2 Architecture: source i386 Version: 2.0a19-8 Distribution: unstable Urgency: low Maintainer: Mark Baker m...@mnb.org.uk Changed-By: Mark Baker m...@mnb.org.uk

Accepted pcre3 1:8.31-2 (source i386)

2013-01-03 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 03 Jan 2013 20:30:05 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 1:8.31-2 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 1:8.31-1 (source i386)

2012-09-13 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 13 Sep 2012 19:58:45 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 1:8.31-1 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 1:8.30-5 (source i386)

2012-05-01 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 01 May 2012 22:38:42 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 1:8.30-5 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 1:8.30-4 (source i386)

2012-03-23 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 23 Mar 2012 22:34:54 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 1:8.30-4 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 8.30..-2 (source i386)

2012-03-22 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 22 Mar 2012 17:52:35 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.30..-2 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 8.30..-3 (source i386)

2012-03-22 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 22 Mar 2012 19:45:03 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.30..-3 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 8.30-1 (source i386)

2012-03-21 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 21 Mar 2012 21:03:39 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.30-1 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted chimera2 2.0a19-7 (source i386)

2012-03-06 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Mar 2012 22:53:11 + Source: chimera2 Binary: chimera2 Architecture: source i386 Version: 2.0a19-7 Distribution: unstable Urgency: low Maintainer: Mark Baker m...@mnb.org.uk Changed-By: Mark Baker m...@mnb.org.uk

Accepted chimera2 2.0a19-6 (source i386)

2011-09-15 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 15 Sep 2011 20:52:50 +0100 Source: chimera2 Binary: chimera2 Architecture: source i386 Version: 2.0a19-6 Distribution: unstable Urgency: low Maintainer: Mark Baker m...@mnb.org.uk Changed-By: Mark Baker m...@mnb.org.uk

Accepted pcre3 8.12-4 (source i386)

2011-08-05 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Jul 2011 21:59:44 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.12-4 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 8.12-3 (source i386)

2011-02-20 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 20 Feb 2011 12:46:44 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.12-3 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 8.12-2 (source i386)

2011-02-08 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 08 Feb 2011 20:38:49 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.12-2 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 8.12-1 (source i386)

2011-02-07 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Feb 2011 23:53:42 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 8.12-1 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 7.8-3 (source i386)

2009-10-06 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 07 Oct 2009 00:05:25 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 7.8-3 Distribution: unstable Urgency: low Maintainer: Mark Baker m

Accepted pcre3 7.8-2 (source i386)

2008-10-05 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 05 Oct 2008 17:06:46 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 7.8-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL

Accepted pcre3 7.8-1 (source i386)

2008-09-21 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Sep 2008 21:23:00 +0100 Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source i386 Version: 7.8-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL

Accepted pcre3 7.6-2 (source i386)

2008-02-13 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 13 Feb 2008 22:19:35 + Source: pcre3 Binary: pcregrep libpcre3-dbg libpcre3 libpcrecpp0 libpcre3-udeb libpcre3-dev Architecture: source i386 Version: 7.6-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL

Accepted pcre3 7.6-1 (source i386)

2008-01-28 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Jan 2008 23:01:05 + Source: pcre3 Binary: pcregrep libpcre3-dbg libpcre3 libpcrecpp0 libpcre3-udeb libpcre3-dev Architecture: source i386 Version: 7.6-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL

Accepted pcre3 7.4-1 (source i386)

2008-01-11 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Jan 2008 21:03:34 + Source: pcre3 Binary: pcregrep libpcre3-dbg libpcre3 libpcrecpp0 libpcre3-udeb libpcre3-dev Architecture: source i386 Version: 7.4-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL

Accepted pcre3 7.3-2 (source i386)

2007-09-17 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 17 Sep 2007 20:52:51 +0100 Source: pcre3 Binary: pcregrep libpcre3 libpcrecpp0 libpcre3-dev Architecture: source i386 Version: 7.3-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted pcre3 7.3-1 (source i386)

2007-08-28 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 28 Aug 2007 20:53:39 +0100 Source: pcre3 Binary: pcregrep libpcre3 libpcrecpp0 libpcre3-dev Architecture: source i386 Version: 7.3-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted pcre3 7.2-1 (source i386)

2007-08-03 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Aug 2007 23:06:28 +0100 Source: pcre3 Binary: pcregrep libpcre3 libpcrecpp0 libpcre3-dev Architecture: source i386 Version: 7.2-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

[Fwd: Bug#387557: pcre3: Please ship pcre_internal.h]

2006-09-25 Thread Mark Baker
What do people think about this? Personally I feel that the internal in the name really should have been a big enough clue, and I don't want to include a file that's not meant to be used just because some idiots have written software that needs it. I'm not even sure it will work; what is it

Accepted pcre3 6.7-1 (source i386)

2006-09-25 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 25 Sep 2006 23:24:55 +0100 Source: pcre3 Binary: pcregrep libpcre3 libpcrecpp0 libpcre3-dev Architecture: source i386 Version: 6.7-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted inform 6.30-2 (source i386 all)

2006-08-25 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Aug 2006 21:29:45 +0100 Source: inform Binary: inform-docs inform Architecture: source i386 all Version: 6.30-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Accepted pcre3 6.4-2 (source i386)

2006-04-27 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Apr 2006 22:32:06 +0100 Source: pcre3 Binary: pcregrep libpcre3 libpcrecpp0 libpcre3-dev Architecture: source i386 Version: 6.4-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted exim 3.36-18 (source i386)

2006-01-11 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 Jan 2006 21:34:39 + Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-18 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted chimera2 2.0a19-5 (source i386)

2006-01-11 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 Jan 2006 21:52:10 + Source: chimera2 Binary: chimera2 Architecture: source i386 Version: 2.0a19-5 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted pcre3 6.4-1 (source all i386)

2005-10-10 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 10 Oct 2005 23:14:53 +0100 Source: pcre3 Binary: pcregrep libpcre3 pgrep libpcre3-dev Architecture: source all i386 Version: 6.4-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted chimera2 2.0a19-4 (source i386)

2005-09-14 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 20 Aug 2005 18:22:53 +0100 Source: chimera2 Binary: chimera2 Architecture: source i386 Version: 2.0a19-4 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted pcre3 6.3-1 (source all i386)

2005-08-27 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 27 Aug 2005 18:12:22 +0100 Source: pcre3 Binary: pcregrep libpcre3 pgrep libpcre3-dev Architecture: source all i386 Version: 6.3-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted exim 3.36-17 (i386 source)

2005-05-02 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 2 May 2005 21:49:44 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-17 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-16 (i386 source)

2005-04-08 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 8 Apr 2005 19:59:46 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-16 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-15 (i386 source)

2005-04-06 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 6 Apr 2005 22:24:33 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-15 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-14 (i386 source)

2005-03-03 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 3 Mar 2005 21:39:44 + Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-14 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted pcre3 5.0-1 (i386 source all)

2005-02-16 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Feb 2005 21:47:14 + Source: pcre3 Binary: pcregrep libpcre3 pgrep libpcre3-dev Architecture: source all i386 Version: 5.0-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted rcs 5.7-14 (i386 source)

2005-01-21 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 18:16:20 + Source: rcs Binary: rcs Architecture: source i386 Version: 5.7-14 Distribution: unstable Urgency: high Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED] Description

Accepted exim 3.36-13 (i386 source)

2005-01-09 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 9 Jan 2005 12:08:50 + Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-13 Distribution: unstable Urgency: high Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-12 (i386 source)

2005-01-06 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 6 Jan 2005 23:12:57 + Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-12 Distribution: unstable Urgency: high Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-11 (i386 source)

2004-05-06 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 6 May 2004 18:09:46 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-11 Distribution: unstable Urgency: high Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted inform 6.30-1 (i386 source all)

2004-03-29 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Mar 2004 23:52:44 +0100 Source: inform Binary: inform-docs inform Architecture: source i386 all Version: 6.30-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Accepted pcre3 4.5-1 (i386 source all)

2004-03-09 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Feb 2004 20:49:33 + Source: pcre3 Binary: pcregrep libpcre3 pgrep libpcre3-dev Architecture: source all i386 Version: 4.5-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark

Accepted pcre3 4.3-4 (i386 source)

2004-01-08 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 8 Jan 2004 21:19:51 + Source: pcre3 Binary: libpcre3 pgrep libpcre3-dev Architecture: source i386 Version: 4.3-4 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Accepted exim 3.36-9 (i386 source)

2003-10-15 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 14 Oct 2003 21:59:14 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-9 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Re: Bug#209116: exim daemon does not restart after last two security upgrades

2003-09-08 Thread Mark Baker
Zygo Blaxell wrote: I have exim configured in daemon mode and I use xinetd instead of inetd. The last two security updates left me with no running exim daemon and nothing listening in port 25. The latest one was nice enough to create an /etc/inetd.conf that was empty except for this line: smtp

Accepted exim 3.36-8 (i386 source)

2003-08-27 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 26 Aug 2003 22:38:15 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-8 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-7 (i386 source)

2003-07-24 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Jul 2003 22:33:51 +0100 Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-7 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted pcre3 4.3-3 (i386 source)

2003-06-25 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Jun 2003 21:09:22 +0100 Source: pcre3 Binary: libpcre3 pgrep libpcre3-dev Architecture: source i386 Version: 4.3-3 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Accepted pcre3 4.3-2 (i386 source)

2003-06-19 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Jun 2003 21:00:39 +0100 Source: pcre3 Binary: libpcre3 pgrep libpcre3-dev Architecture: source i386 Version: 4.3-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Bug in test suite for pcre 4.3

2003-06-18 Thread Mark Baker
Andreas Metzler wrote: Mark has uploaded it yesterday in the evening. The bad news is that 4.3 seems to be broken on m68k, ia64 and alpha, make test fails. I do not believe it is actually broken, at least not on alpha; I'm assuming the problems on the other architectures are similar. It does not

Accepted pcre3 4.3-1 (i386 source)

2003-06-16 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 22:11:08 +0100 Source: pcre3 Binary: libpcre3 pgrep libpcre3-dev Architecture: source i386 Version: 4.3-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Accepted exim 3.36-5 (i386 source)

2003-03-10 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 10 Mar 2003 22:56:54 + Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-5 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-4 (i386 source)

2002-12-07 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 7 Dec 2002 18:36:19 + Source: exim Binary: exim eximon Architecture: source i386 Version: 3.36-4 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted pcre3 3.9-1 (i386 source)

2002-10-26 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 Oct 2002 18:12:13 +0100 Source: pcre3 Binary: libpcre3-dev libpcre3 pgrep Architecture: source i386 Version: 3.9-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL

Accepted exim 3.36-3 (i386 source)

2002-09-20 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 20 Sep 2002 18:33:47 +0100 Source: exim Binary: eximon exim Architecture: source i386 Version: 3.36-3 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-2 (i386 source)

2002-09-17 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Sep 2002 21:58:53 +0100 Source: exim Binary: eximon exim Architecture: source i386 Version: 3.36-2 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Accepted exim 3.36-1 (i386 source)

2002-08-30 Thread Mark Baker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 30 Aug 2002 21:52:46 +0100 Source: exim Binary: eximon exim Architecture: source i386 Version: 3.36-1 Distribution: unstable Urgency: low Maintainer: Mark Baker [EMAIL PROTECTED] Changed-By: Mark Baker [EMAIL PROTECTED

Re: IPv6 support in Debian

2001-01-07 Thread Mark Baker
On Wed, Jan 03, 2001 at 02:00:07PM +1100, Dancer Vesperman wrote: Certainly we have things like exim, lftp, ssh that work 'out of the box' with v6...and apps that work with v6 work (equally) flawlessly in v4-only environments. That's not necessarily the case. There were lots of problems

pcre

2000-08-19 Thread Mark Baker
I've just uploaded version 3 of libpcre. I've put it in a new package, libpcre3, and given it a new soname. I'm not sure if this was strictly necessary or not: the upstream documentation doesn't mention binary compatibility with the old version, probably because older versions weren't intended to

Re: exim 3.00-1 (source i386) available for testing

1999-05-16 Thread Mark Baker
On Sat, May 15, 1999 at 10:26:35AM +0100, James Troup wrote: * OS/Makefile-Default: Enabled IPv6 support (this therefore requires glibc 2.1) Bah, this will break exim for m68k. :( So will everything else network-related then, since we're hoping to get as much as possible using IPv6.

Re: Yet another Linux distribution! :-)

1998-05-03 Thread Mark Baker
On Sat, May 02, 1998 at 10:52:48PM +, Rev. Joseph Carter wrote: But this is aimed at dialup users! You don't want a send-only MTA, as dialup users presumably want to store their mail locally. Their mail isn't gonna get delivered by smtp No? I know several dialup ISPs that do provide

Re: Yet another Linux distribution! :-)

1998-05-02 Thread Mark Baker
On Fri, May 01, 1998 at 11:10:39PM -0700, Jim Pick wrote: - targetted towards desktop use only, no server apps, just a few games - minimal size - optimized for installation via 28.8k modem via FTP, which will be the primary distribution mechanism (not CD). These don't seem consistent

Re: Yet another Linux distribution! :-)

1998-05-02 Thread Mark Baker
On Sat, May 02, 1998 at 11:36:28AM -0700, John Labovitz wrote: have you looked at ssmtp? i just took a quick look at the source, and it seems that it's *extremely* simple -- sounds like a good one for a send-only MTA. But this is aimed at dialup users! You don't want a send-only MTA, as

Re: Yet another Linux distribution! :-)

1998-05-02 Thread Mark Baker
On Sun, May 03, 1998 at 01:37:28AM +1000, Hamish Moffatt wrote: things (like different alias files per domain). exim and smail are both easy to set up with the provided configuration programs though (which seem pretty much identical in my limited experience). eximconfig was originally based

Re: X and Window Mangers

1998-04-28 Thread Mark Baker
On Tue, Apr 28, 1998 at 01:26:37AM -0500, Branden Robinson wrote: 1) ship an empty /etc/X11/window-managers with xbase 2) mark it as a conffile So you don't think other packages---such as the window managers---should modify it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Re: How Debian Linux could be made more secure

1998-04-28 Thread Mark Baker
On Tue, Apr 28, 1998 at 04:50:45PM +0200, Thomas Roessler wrote: Today, I reported two bugs in debian packages which install binaries suid root. Both bugs were avoidable: There's a third one too---we install xterm suid root, which isn't necessary (the alternative is to use a wrapper program to

Re: CERT* VB-98.04: Vulnerabilities in xterm and Xaw

1998-04-28 Thread Mark Baker
On Tue, Apr 28, 1998 at 05:57:55PM +0200, A Mennucc wrote: Vulnerabilities exist in the terminal emulator xterm(1), and the Xaw library distributed in various MIT X Consortium; X Consortium, Inc.; and The Open Group X Project Team releases. These vulnerabilities may be exploited by an

Re: CERT* VB-98.04: Vulnerabilities in xterm and Xaw

1998-04-28 Thread Mark Baker
On Tue, Apr 28, 1998 at 12:45:33PM -0500, Branden Robinson wrote: Well, the reason xterm is setuid is because it needs privileged access to the utmp file. However, this is presently a problem under some circumstances (see bug #20685). I understand it also needs it to allocate a pty.

Re: PROPOSAL: Services, inetd and xinetd

1998-04-28 Thread Mark Baker
On Tue, Apr 28, 1998 at 10:59:49AM +0200, Andreas Jellinghaus wrote: btw: in my opinion debian needs a general resource database (something like windows nt registry, but with a better, unixlike implementation). We have one. It's called /etc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Re: Conflicts between developers and policy

1998-04-27 Thread Mark Baker
On Mon, Apr 27, 1998 at 01:49:33PM -0500, Manoj Srivastava wrote: I understand that one may want a little more leeway than say the policy documents are writ in stone (I personally prefer that), but to deny that and make no mention of any mechanism of enforcement of policy is

Re: Proposed Constitution

1998-04-27 Thread Mark Baker
On Mon, Apr 27, 1998 at 06:05:51PM -0400, Bob Hilliard wrote: include the plural. Then all of the clumsy constructions using plural pronouns (they, their) to refer to singular entities (Leader, Secretary, etc.) should be changed to use singular masculine pronouns (him, his). They is not only

Re: base-files etc.

1998-04-26 Thread Mark Baker
. # # This currently does almost but not quite like what bash does by # default - the differences are the reading of root's .bashrc, for # use with su, and the default bashrc if the user doesn't have one. # # Mark Baker - 31 October 1996 # case ${--} in *i*) # Shell is interactive - no scripts

Re: interest in xfstt package

1998-04-21 Thread Mark Baker
On Mon, Apr 20, 1998 at 10:24:33PM -0500, Branden Robinson wrote: After hamm is released I'm going to be re-engineering XFree86 a bit. An xserver-common package will be created, I understand that will be necessary (or at least highly desirable) in future anyway, since new releases of XFree86

Re: fltk and XForms compliance

1998-04-18 Thread Mark Baker
On Fri, Apr 17, 1998 at 11:56:02AM +0100, Enrique Zanardi wrote: That will be a problem with lyx as the upstream side is thinking about a switch anyway, but qt is the leading candidate there. Someone should tell them about GTK, now that version 1.0 has been released. A little bit of info

Re: Are we shipping 2.0 with ipmasq in the default kernel?

1998-04-15 Thread Mark Baker
On Wed, Apr 15, 1998 at 05:02:39PM +, Rev. Joseph Carter wrote: The thing is that I had a prefectly working IPmasq setup, with rules changed in ip-up and ip-down. hmm, now there's an idea. Since I don't use diald or similar, I just set the rules static. I do use diald, and set the

Re: [gtk-list] ANNOUNCE: GTK+ 1.0.0 Released!

1998-04-15 Thread Mark Baker
On Tue, Apr 14, 1998 at 05:32:17PM -0800, Ben Gertzfield wrote: Marcus Did the interface change (e.g. do we need to upload new Marcus versions of related packages) ? No, the API has not changed since 0.99.4. There are still some packages using the old API though, I believe. What

Re: Anyone working on new lyx version?

1998-01-10 Thread Mark Baker
On Tue, Jan 06, 1998 at 01:26:22PM +0100, Michael Meskes wrote: Did anyone take over lyx? It seems as if we're close the release of a new stable version. I took it over. I haven't done anything to it until now, because of the lack of a libc6-based xforms (and you (IIRC) beat me to it once there

Re: imap4

1998-01-10 Thread Mark Baker
On Sat, Jan 10, 1998 at 03:00:17PM -0500, Jaldhar H. Vyas wrote: Thanks but I was able to solve the pw_encrypt problem on my own. Apparently in libc6 you can just replace it with crypt(). I tried that and it didn't work: have you tested it? Maybe I just did something silly. -- TO

Re: BS in rxvt+ncurses

1997-12-07 Thread Mark Baker
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Brian Mays) writes: Okay. I'm building a new unstable version of rxvt with backspace set to ^H. From this point on, Debian's rxvt policy will be to use ^H as backspace by default. Couldn't you force it to ^? instead? That would be far

Re: crontab

1997-12-07 Thread Mark Baker
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Miquel van Smoorenburg) writes: that do this, and file a bug report against them. You should mention that tail +4 is dangerous since the behaviour of crontab -l might change , and recommend something like: crontab -l | sed -e

Re: Need someone to take some of my packages.

1997-12-03 Thread Mark Baker
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Dale Scheetz) writes: The one that is desperate for a new home is imap-4. I have never been able to adequately test this package. There are several outstanding bugs that I have been unable to come to terms with and for this reason alone

Re: bo-updates packages

1997-12-03 Thread Mark Baker
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Adam P. Harris) writes: The issue of keeping Debian bo crunchy and fresh w/o inhibiting the bold experimentalism of the hamm lineage is critical to Debian's success. It hopefully won't be a problem once hamm is released. With a

Re: linux/unix to NT

1997-12-02 Thread Mark Baker
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Mariusz Pagowski) writes: I learned about samba package allowing me to access disks on NT machine from unix/linux. Actually the other way round; samba lets you turn your unix box into a windows network compatible fileserver. There is a

Re: Sub-categorizing the /usr/doc directory.

1997-06-29 Thread Mark Baker
On Sun, 29 Jun 1997, Joey Hess wrote: The directory is very large when you have a lot of packages installed, and it takes a lot of processing to open it with a file manager, web browser, or dired. I completly agree. I have 434 items in /usr/doc, and that's too many. Splitting it up by

Re: Documentation Policy

1997-06-28 Thread Mark Baker
On Tue, 24 Jun 1997, Joey Hess wrote: I haven't been following this thread closely (catching up on mail backlog after vacation), but the reason I've heard why it's not acceptable to ship only info files and convert to html on the fly is because the converter in dwww that does this produces

Re: question about dpkg-source : why does it create a copy of the orig.tar.gz file ?

1997-06-28 Thread Mark Baker
On Sat, 28 Jun 1997, Andreas Jellinghaus wrote: dpkg-source -x /some/path/to/file_version-rev.dsc creates not only file_version/, but also file_version.orig.tar.gz. why ? So that once you've modified it you can easily package up your changed version. -- TO UNSUBSCRIBE FROM THIS MAILING

Re: dc and bc in Important?

1997-06-28 Thread Mark Baker
On Sat, 28 Jun 1997, Erik Andersen wrote: iThis is correct, but has the unfortunate side effect of not being portable, since not all /bin/sh happin to be bash. No, it also works with ksh. I believe posix.2 specifies that /bin/sh has to provide various features---basically to be a clone of

Re: Experiences with compiling Debian

1997-06-24 Thread Mark Baker
On 24 Jun 1997, Mark Eichin wrote: 0.5.21, gpc is 2.something, who knows about gnat... gnat is 3.09, 3.10a is in test and might be released some time... in any case, while merging gcc/g77/gpc into one release probably makes a lot of sense, gnat is not like the others -- because it's

Re: Documentation Policy

1997-06-24 Thread Mark Baker
On Tue, 24 Jun 1997, Philip Hands wrote: I think we should aim to get all documentation into separate packages. Would it not be possible to make the package building tools (deb-make, debstd etc.) assume a simplest case of ``single binary, and single docs package'' rather than the current

Re: Experiences with compiling Debian

1997-06-23 Thread Mark Baker
On Mon, 23 Jun 1997, joost witteveen wrote: (in fakt so much, that I may be tempted to write it myself. You don't need that many changes). Well, you need to write your own version of make that looks for any attempt to run chmod, chown etc, and then fakes all the ownership and modes in the

Re: Experiences with compiling Debian

1997-06-22 Thread Mark Baker
On Sun, 22 Jun 1997, Lars Wirzenius wrote: - having a central repository for autoconf test result might speed things up (I think autoconf supports this; someone should investigate) Yes; I do it. You need to set the environment variable CONFIG_SITE to the name of a file---I use

Re: leap second

1997-06-21 Thread Mark Baker
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Kai Henningsen) writes: Consider a system using real time. On June 31, its idea of time would be wrong until the next software upgrade. No. Using real time, the system clock increments normally, and correctly measures the time since

  1   2   >