Bug#769583: unblock: bind9/ 9.9.5 with patch or 9.9.6?

[LaMont Jones]

On Mon, Nov 17, 2014 at 08:06:02PM +0100, Niels Thykier wrote:
> In the particular case, it has been suggested that the final changes
> compared to testing will be 87 000 (or more) lines.  Unless 97+% of this
> is pure documentational/auto-generated changes, which can be filtered
> out and turn this into a sanely reviewable diff, I find it unlikely that
> we can approve of these changes.

Again, without actually looking at it, I'm inclined to agree.  87k
lines this late in the process is too many.

I'll get a patch together for 9.9.5, but it may be wednesday before I have
it uploaded to sid, and a diff sent to you guys.

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141117224334.ga24...@mix.mmjgroup.com

Bug#769583: unblock: bind9/ 9.9.5 with patch or 9.9.6?

[LaMont Jones]

On Fri, Nov 14, 2014 at 07:28:02PM +0100, Daniel Pocock wrote:
> testing currently has bind9 version 1:9.9.5.dfsg-5
> 
> Upstream released 9.9.6 fixing some bugs with an impact on compatibility
> and at least one appears to be security related
> "Corrected bugs in the handling of wildcard records by the DNSSEC
> validator: invalid wildcard expansions could be treated as valid if
> signed, and valid wildcard expansions in NSEC3 opt-out ranges had the AD
> bit set incorrectly in responses. [RT #37093] [RT #37072]"

Generally speaking, I have found the fix-level updates to bind to be very
safe and sane, although sometimes they are somewhat large.  I have not
looked at 9.9.6 yet, but I expect it's in the same vein.  It is rare to
see them do anything in a fix-release than, well, fix things.

I would recommend 9.9.6 for the upstream fixes.  If that's good, I
should be able to upload it tonight.

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141117181932.ga32...@mix.mmjgroup.com

Bug#702412: pre-approval unblock: postfix

[LaMont Jones]

On Sat, Mar 09, 2013 at 05:59:32PM +, Adam D. Barratt wrote:
> A debdiff against the current wheezy package (possibly minus the .po
> changes and some of the repetitive documentation updates) would probably
> have been more useful, fwiw.

Noted for the future.

> > The source and amd64 binaries are to be found at:
> > deb http://people.debian.org/~lamont/postfix .
> > deb-src http://people.debian.org/~lamont/postfix .
> Please go ahead; thanks.

Done


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130311162138.ga6...@mix.mmjgroup.com

Bug#702412: pre-approval unblock: postfix

[LaMont Jones]

Per the IRC discussion, I have prepared postfix_2.9.6-2 for wheezy. Please let 
me know when to upload it.  The debdiff is below.

The source and amd64 binaries are to be found at:
deb http://people.debian.org/~lamont/postfix .
deb-src http://people.debian.org/~lamont/postfix .

lamont

diff -u postfix-2.9.6/debian/control postfix-2.9.6/debian/control
--- postfix-2.9.6/debian/control
+++ postfix-2.9.6/debian/control
@@ -1,8 +1,7 @@
 Source: postfix
 Section: mail
 Priority: extra
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: LaMont Jones 
+Maintainer: LaMont Jones 
 Standards-Version: 3.9.1.0
 Homepage: http://www.postfix.org
 Build-Depends: debhelper (>= 7), po-debconf (>= 0.5.0), groff-base, patch, 
lsb-release, libdb-dev (>=4.6.19), libldap2-dev (>=2.1), libpcre3-dev, 
libmysqlclient-dev|libmysqlclient15-dev|libmysqlclient14-dev, libssl-dev 
(>=0.9.7), libsasl2-dev, libpq-dev, libcdb-dev, hardening-wrapper, dpkg-dev (>= 
1.15.5), libsqlite3-dev
diff -u postfix-2.9.6/debian/changelog postfix-2.9.6/debian/changelog
--- postfix-2.9.6/debian/changelog
+++ postfix-2.9.6/debian/changelog
@@ -1,3 +1,10 @@
+postfix (2.9.6-2) wheezy; urgency=low
+
+  * Fix fumbled merge to actually have the right maintainer address. 
+See also bug 702412.  Closes: #699877
+
+ -- LaMont Jones   Wed, 06 Mar 2013 07:28:23 -0700
+
 postfix (2.9.6-1) unstable; urgency=low
 
   [Wietse Venema]


signature.asc
Description: Digital signature

Bug#702412: pre-approval unblock: postfix

[LaMont Jones]

On Wed, Mar 06, 2013 at 09:09:50AM +0100, Thijs Kinkhorst wrote:
> I've been looking into Postfix RC bug #700719. In short, my proposal is to
> fix the maintainer field and then unblock the package. Please see my message
> in the bug log for details.

wheezy has 2.9.3-2.1, sid has 2.10.0-1.  Given Wietse's track record,
I'm inclined to just go with 2.10.0-1, but if the release team would
like 2.9.6-2 uploaded to tpu, I'd be happy to do so.

Just let me know.
lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130306142203.gb3...@mix.mmjgroup.com

Bug#698658: bind9 with fix for 698641

[LaMont Jones]

On Mon, Jan 21, 2013 at 08:44:55PM +, Adam D. Barratt wrote:
> Debian admin has deployed the patch at [2] to the bind running the
> debian.org nameservers - else debian.org's nameservers would not have
> any resources left to answer legitimate queries.
> 
> We think it important that the bind version Debian ships be actually
> useable by the internet community in general, and ourselves in
> particular.  Therefore we ask you (and the release folks) to consider
> shipping wheezy's bind with the rate limiting patches applied.

1:9.8.4.dfsg.P1-5 is now at 14 days in sid with no reported regressions
relative to -4.

Please consider unblocking it.

thanks,
lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130214152137.ga11...@mix.mmjgroup.com

Bug#697798: pu: package bind9/1:9.7.3.dfsg-1~squeeze8

[LaMont Jones]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu

d.root-servers.net changed IP addresses 2013-01-03, the old IP will go
away in "about 6 months".

lamont
=
diff --git a/debian/changelog b/debian/changelog
index 13f278e..2ef9801 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+bind9 (1:9.7.3.dfsg-1~squeeze9) squeeze-proposed-updates; urgency=low
+
+  * Update db.root with new IP for D.root-servers.net.  Closes: #697352
+
+ -- LaMont Jones   Tue, 08 Jan 2013 07:07:02 -0700
+
 bind9 (1:9.7.3.dfsg-1~squeeze8) squeeze-security; urgency=high
 
   * Apply patch extracted from 9.7.6-P4 to fix CVE-2012-5166
diff --git a/debian/db.root b/debian/db.root
index d081faa..6c19741 100644
--- a/debian/db.root
+++ b/debian/db.root
@@ -9,8 +9,8 @@
 ;   on server   FTP.INTERNIC.NET
 ;   -OR-RS.INTERNIC.NET
 ;
-;   last update:Jun 17, 2010
-;   related version of root zone:   2010061700
+;   last update:Jan 3, 2013
+;   related version of root zone:   2013010300
 ;
 ; formerly NS.INTERNIC.NET
 ;
@@ -31,7 +31,8 @@ C.ROOT-SERVERS.NET.  360  A 192.33.4.12
 ; FORMERLY TERP.UMD.EDU
 ;
 .360  NSD.ROOT-SERVERS.NET.
-D.ROOT-SERVERS.NET.  360  A 128.8.10.90
+D.ROOT-SERVERS.NET.  360  A 199.7.91.13
+D.ROOT-SERVERS.NET. 360    2001:500:2D::D
 ;
 ; FORMERLY NS.NASA.GOV
 ;
=


-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130109200025.29977.26375.report...@catsear.mmjgroup.com

Re: Bug#669213: bind9: new upstream release: 9.9

[LaMont Jones]

On Mon, Oct 29, 2012 at 05:22:10PM +, Adam D. Barratt wrote:
> Indeed. In any case, were the new version to be accepted in to the
> release then the appropriate route would be via unstable, not direct
> to t-p-u.

Works for me.  I'll toss 9.8.4 into sid.  As for getting it into wheezy,
it'll make the support life easier for the inevitable security fixes that
will follow.  There are probably other reasons.

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121029203013.ga30...@mix.mmjgroup.com

Bug#610052: unblock: util-linux/2.17.2-6

[LaMont Jones]

On Tue, Jan 18, 2011 at 07:36:19PM +0100, Christian PERRIER wrote:
> Quoting Julien Cristau (jcris...@debian.org):
> Or grab the PO file from the BTS web interface

Yeah - files grabbed, I need to build the debs and I'll get them uploaded.
that should happen within the next 12-14 hours. (sleep is in there somehwere)

lamont



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2011011912.ga32...@mix.mmjgroup.com

Bug#610052: unblock: util-linux/2.17.2-6

[LaMont Jones]

On Tue, Jan 18, 2011 at 11:48:28AM -, Adam D. Barratt wrote:
> > Hmm, LaMont, would it be possible for you to reupload with fixed PO
> > files (I think you just need to dig them out from the BTSthey have
> > probably been broken by the infamous mutt encoding bug)? This,
> > assuming the release team is OK with that, of course.

Let me go digging.  how can I tell the good from the bad?

lamont



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110118123630.ga12...@mix.mmjgroup.com

Bug#602839: unblock: bind9/1:9.7.2.dfsg.P2-1

[LaMont Jones]

On Thu, Dec 09, 2010 at 03:10:09PM +0100, Julien Cristau wrote:
> 1:9.7.2.dfsg.P3-1 unblocked.

Thanks - the specific patch for the first CVE was not forthcoming.  And
the others just combined to make it more sensible to just unblock it, IMO.

lamont



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101210003249.ga2...@mix.mmjgroup.com

Bug#602839: unblock: bind9/1:9.7.2.dfsg.P2-1

[LaMont Jones]

On Tue, Nov 30, 2010 at 11:52:22PM +0100, Moritz Muehlenhoff wrote:
> > Lamont, would it be possible to prepare an upload fixing just the
> > security bug for squeeze (so based on 1:9.7.1.dfsg.P2-2)?
> 
> I looked into it a bit, but couldn't pinpoint the exact changes for 
> CVE-2010-3752 (not with a certainty to not mess up DNSSEC).
> I'll give it another go in the next days.

Likewise.  Looking at my schedule, 9.7.2 is something in the "early next
week" camp.

In what I saw, this CVE seems to have come in after they had already 
fixed it - there is no mention of it prior to the 9.7.2 release notes.
I'm more inclined to support the 9.7.2 upstream than I am to support a
frankenversion where we can't find an isolated fix for the bug.

But again, I'm going to worry about it more this weekend and monday/tuesday.

lamont



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101201005802.ga22...@mix.mmjgroup.com

postfix update for stable

[LaMont Jones]

After discussions with the affected security teams (debian and ubuntu),
postfix 2.6.5.3 was uploaded to sid, with the presumption that I would
contact -release to get the fix for my ancient screwup into the next
point release.

  * SECURITY-UPDATE: correct permissions on /var/spool/postfix/pid
- adjust /var/spool/postfix/pid directory to be owned by root, not
  postfix.
- CVE-2009-2930

If there is a desire to go from 2.3.8 to 2.3.19 for etch, or 2.5.5 to
2.5.9 for lenny, I'm open to that as well.  Wietse tends to be very
pedantic about what he adds in point releases.  At the same time, I
doubt that there is any critical need to do so.

thoughts?
lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: open issues with the hppa port

[LaMont Jones]

On Fri, Sep 11, 2009 at 02:35:00PM -0600, dann frazier wrote:
> That would prevent it from getting uploaded, but won't that package
> get marked as built, preventing other buildds from trying?

Yep.  If you just want to build packages over and over, then don't start
the buildd up, and just run sbuild on a series of sources

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: open issues with the hppa port

[LaMont Jones]

On Fri, Sep 11, 2009 at 02:06:36PM -0400, Carlos O'Donell wrote:
> On Fri, Sep 11, 2009 at 1:06 PM, dann frazier wrote:
> What happened to sarti? Loosing a box like that would certainly add
> load to the others.

Sarti failed to power on one day.

> >> >> Are you allowed to boot a kernel/initrd that I send you?
> >> > I don't see why not, assuming these changes don't add a risk of
> >> > producing bad binaries.
> >> To be safe, I think we should be throwing away the packages built when
> >> running the instrumented kernel. Is there a way we can do that? Can
> >> you find that out for me?
> > That would probably need to be answered by LaMont - he's the buildd
> > admin for these boxes.
> OK, I'll wait for LaMont to comment.

Simplest way is to change ~buildd/.forward-porters (or whatever it is)
to not send the logs to me.  second best would be to tell me what not to
upload. :-(

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: octave3.2 autobuild problems

[LaMont Jones]

On Fri, Jun 19, 2009 at 09:49:34PM +0200, Rafael Laboissiere wrote:
> The failure on caballero is due to the infamous alternatives problem [2] but
> nobody seem to care.  I wish I could ask for this:
> 2: http://lists.debian.org/debian-wb-team/2009/06/msg00058.html

I'll go fix caballero tonight - thanks for pointing out the issue.

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: BIND 1:9.5.1.dfsg.P2-1 for stable

[LaMont Jones]

On Wed, Apr 29, 2009 at 09:48:30AM +0200, Florian Weimer wrote:
> I'd like to upload 1:9.5.1.dfsg.P2-1 to stable-proposed-updates (as
> 1:9.5.1.dfsg.P2-1+lenny1) to fix a bug in DLV processing.  We can then
> point users to this version if they use dlv.isc.org and experience
> resolution failures for .gov:
> 

Sounds good to me.

lamont


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

bind9 upload for stable

[LaMont Jones]

bind9 1:9.5.1.dfsg.P1-2 was just uploaded to stable, and should
hopefully go into lenny r1  (-3 was then uploaded to sid... go me and
version numbers...)

All of the bugs fixed are properly either serious (atomic operations
broken in bad ways, resulting in an unusable package, or FTBFS under
certain conditions), or l10n additions to debconf (Basque was not there
before.)

I, and DSA, appreciate your acceptance of the upload.  (merkel's bind
was dying after the lenny upgrade, and is now running a version of bind9
with the patch from the bug below.)

thanks,
lamont

bind9 (1:9.5.1.dfsg.P1-3) unstable; urgency=low

  * package -2 for unstable

 -- LaMont Jones   Wed, 18 Mar 2009 09:40:18 -0600

bind9 (1:9.5.1.dfsg.P1-2) stable; urgency=low

  [Juhana Helovuo]

  * fix atomic operations on alpha.  Closes: #512285

  [Dann Frazier]

  * fix atomic operations on ia64.  Closes: #520179

  [LaMont Jones]

  * build-conflict: libdb4.2-dev.  Closes: #515074, #507013

  [localization folks]

  * l10n: Basque debconf template.  Closes: #516549 (Piarres Beobide)

 -- LaMont Jones   Wed, 18 Mar 2009 05:30:22 -0600


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: libvirt not being built on anything but i386/amd64

[LaMont Jones]

On Fri, Mar 07, 2008 at 09:13:55PM +0100, Philipp Kern wrote:
> On Fri, Mar 07, 2008 at 07:57:00PM +0100, Guido Günther wrote:
> > libvirt isn't an arch specific package, so the buildds should build it.
> > How can I get libvirt out of PAS?
> By mailing the p-a-s maintainers.  Lamont, could you please remove this
> bogus p-a-s entry?

At the time it was added to PaS, it had an architecture-independant
build-dep on libxen3.1-dev.


In any case, it's been dropped from PaS.

lamont


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

postfix_2.3.8-1 for etch?

[LaMont Jones]

As mentioned before, Wietse is one of the most pedantic upstreams I've
seen when it comes to point releases.  Here is the changelog for 2.3.8:

Both of the upstream fixes in 2.3.8 would be candidates to backport to
2.3.7 if I were so inclined.

  postfix (2.3.8-1) unstable; urgency=low

* New upstream version:
  - Workaround: GNU POP3D creates a new mailbox and deletes the
old one. Postfix now backs off and retries delivery later,
instead of appending mail to a deleted file.  File:
global/mbox_open.c.
  - Workaround: Disable SSL/TLS ciphers when the underlying
symmetric algorithm is not available in the OpenSSL crypto
library at the required bit strength. Problem observed with
SunOS 5.10's bundled OpenSSL 0.9.7 and AES 256. Also possible
with OpenSSL 0.9.8 and CAMELLIA 256. Root cause fixed in
upcoming OpenSSL 0.9.7m, 0.9.8e and 0.9.9 releases. Victor
Duchovni, Morgan Stanley. Files: src/smtp/smtp_proto.c,
src/smtpd/smtpd.c, src/tls/tls.h, src/tls/tls_client.c,
src/tls/tls_misc.c and src/tls/tls_server.c.
* Correct check for new (empty) answer to root alias debconf question.
  Introduced in 2.3.6-2.  Closes: #413610, #413086

   -- LaMont Jones <[EMAIL PROTECTED]>  Mon,  5 Mar 2007 21:43:22 -0700

And would you like -2?  I was stalling waiting for -1 to hit etch, but
can upload the freshened czech translations if you want...

  postfix (2.3.8-2) unstable-UNRELEASED; urgency=low

* Updated Czech debconf template.  Closes: #414392

   -- LaMont Jones <[EMAIL PROTECTED]>  Sun, 11 Mar 2007 19:58:07 -0600

Diffstat for 2.3.7-4 vs 2.3.8-1:

 HISTORY|   36 --
 README_FILES/RELEASE_NOTES |   10 +-
 RELEASE_NOTES  |   10 +-
 debian/arch-version|2 
 debian/changelog   |   21 ++
 debian/postfix.postinst|2 
 src/global/mail_version.h  |4 -
 src/global/mbox_open.c |   20 +
 src/smtp/smtp_proto.c  |2 
 src/smtpd/smtpd.c  |2 
 src/tls/Makefile.in|1 
 src/tls/tls.h  |1 
 src/tls/tls_client.c   |   22 ++
 src/tls/tls_misc.c |  155 ++---
 src/tls/tls_server.c   |   12 +--
 15 files changed, 253 insertions(+), 47 deletions(-)

thoughts?
lamont


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

please unblock util-linux_2.12r-18

[LaMont Jones]

Please consider unblocking util-linux_2.12r-18.

As you can see below, the patches are relatively trivial.  #385879 is
more of an annoyance to nfs-utils, since he gets the bug reports, not
me.

mips and mipsel successfully built on feb 5, although the binaries
haven't made it into the archive yet... sadness.

thoughts?
lamont

util-linux (2.12r-18) unstable; urgency=low

  * Stop printing erroneous "rpc.idmapd appears to not be running" message.
Files: 30nfs4.dpatch. Closes: #385879

 -- LaMont Jones <[EMAIL PROTECTED]>  Mon,  5 Feb 2007 13:47:10 -0700

util-linux (2.12r-17) unstable; urgency=low

  * Userspace software suspend fix.  Closes: #409365
  * armel support.  Closes: #408816

 -- LaMont Jones <[EMAIL PROTECTED]>  Fri,  2 Feb 2007 11:08:04 -0700


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

nmap_4.20-1 unblock request

[LaMont Jones]

Please consider nmap 4.20-1 for etch.  Nearly all of the bugs ever filed
against nmap have been enhancements, etc.  It would be a shame to not
have the latest nmap in etch, especially now that it's over 50 days
old...

Upstream's changelog below.

thoughts?
lamont

# Nmap Changelog ($Id: CHANGELOG 4229 2006-12-08 03:02:09Z fyodor $); -*-text-*-
4.20

o Integrated the latest OS fingerprint submissions.  The 2nd
  generation DB size has grown to 231 fingerprints.  Please keep them
  coming!  New fingerprints include Mac OS X Server 10.5 pre-release,
  NetBSD 4.99.4, Windows NT, and much more.

o Fixed a segmentation fault in the new OS detection system
  which was reported by Craig Humphrey and Sebastian Garcia.

o Fixed a TCP sequence prediction difficulty indicator bug. The index
  is supposed to go from 0 ("trivial joke") to about 260 (OpenBSD).
  But some systems generated ISNs so insecurely, that Nmap went
  berserk and reported a negative difficulty index.  This generally
  only affects some printers, crappy consumer devices, and Microsoft
  Windows (old versions).  Thanks to Sebastian Garcia for helping me
  track down the problem.

4.20RC2

o Integrated all of your OS detection submissions since RC1.  The DB
  has increased 13% to 214 fingerprints.  Please keep them coming!
  New fingerprints include versions of z/OS, OpenBSD, Linux, AIX,
  FreeBSD, Cisco CatOS, IPSO firewall, and a slew of printers and
  misc. devices.  We also got our first Windows 95 fingerprint,
  submitted anonymously of course :).

o Fixed (I hope) the "getinterfaces: intf_loop() failed" error which
  was seen on Windows Vista.  The problem was apparently in
  intf-win32.c of libcnet (need to define MIB_IF_TYPE_MAX to
  MAX_IF_TYPE rather than 32).  Thanks to Dan Griffin
  (dan(a)jwsecure.com) for tracking this down!

o Applied a couple minor bug fixes for IP options
  support and packet tracing.  Thanks to Michal Luczaj
  (regenrecht(a)o2.pl) for reporting them.

o Incorporated SLNP (Simple Library Network Protocol) version
  detection support.  Thanks to Tibor Csogor (tibi(a)tiborius.net) for
  the patch.

4.20RC1

o Fixed (I hope) a bug related to Pcap capture on Mac OS X.  Thanks to
  Christophe Thil for reporting the problem and to Kurt Grutzmacher
  and Diman Todorov for helping to track it down.

o Integrated all of your OS detection submissions since ALPHA11.  The
  DB has increased 27% to 189 signatures.  Notable additions include
  the Apple Airport Express, Windows Vista RC1, OpenBSD 4.0, a Sony
  TiVo device, and tons of broadband routers, printers, switches, and
  Linux kernels.  Keep those submissions coming!

o Upgraded the included LibPCRE from version 6.4 to 6.7.  Thanks to
  Jochen Voss (voss(a)seehuhn.de) for the suggestion (he found some bugs
  in 6.4)

4.20ALPHA11

o Integrated all of your OS detection submissions, bringing the
  database up to 149 fingerprints.  This is an increase of 28% from
  ALPHA10.  Notable additions include FreeBSD 6.1, a bunch of HP
  LaserJet printers, and HP-UX 11.11.  We also got a bunch of more
  obscure submissions like Minix 3.1.2a and "Ember InSight Adapter for
  programming EM2XX-family embedded devices".  Who doesn't have a few
  of those laying around?  I'm hoping that all the obscure submissions
  mean that more of the mainstream systems are being detected out of
  the box!  Please keep those submissions (obscure or otherwise)
  coming!

4.20ALPHA10

o Integrated tons of new OS fingerprints.  The DB now contains 116
  fingerprints, which is up 63% since the previous version.  Please keep
  the submissions coming!

4.20ALPHA9

o Integrated the newly submitted OS fingerprints. The DB now contains
  71 fingerprints, up 27% from 56 in ALPHA8.  Please keep them coming!
  We still only have 4.2% as many fingerprints as the gen1 database.

o Added the --open option, which causes Nmap to show only open ports.
  Ports in the states "open|closed" and "unfiltered" might be open, so
  those are shown unless the host has an overwhelming number of them.

o Nmap gen2 OS detection used to always do 2 retries if it fails to
  find a match.  Now it normally does just 1 retry, but does 4 retries
  if conditions are good enough to warrant fingerprint submission.
  This should speed things up on average.  A new --max-os-tries option
  lets you specify a higher lower maximum number of tries.

o Added --unprivileged option, which is the opposite of --privileged.
  It tells Nmap to treat the user as lacking network raw socket and
  sniffing privileges.  This is useful for testing, debugging, or when
  the raw network functionality of your operating system is somehow
  broken.

o Fixed a confusing error message which occured when you specified a
  ping scan or list scan, but also specified -p (which is only used for
  port scans).  Thanks to Thomas Buchanan for the patch.

o Applied some small cleanup patches from Kris Katterjohn

4.20ALPHA8

o Integrated the newly submitted OS fingerprints.  Th

xdelta 1.1.3-7 unblock request

[LaMont Jones]

Andrea Mennucc's debdelta project is blocked by #147187, which is fixed
in 1.1.3-7.  Please consider allowing it into etch.

lamont

xdelta (1.1.3-7) unstable; urgency=low

  * Acknowledge NMU.  Closes: #297844
  * Updates for standards version 3.7.2.0
  * Deltas generated on i386 don't apply on 64-bit machines.  Closes:
  * #147187
  * xdelta.m4 love.  Closes: #212677

 -- LaMont Jones <[EMAIL PROTECTED]>  Fri, 19 Jan 2007 12:15:11 -0700


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

Re: Please unblock bind9_9.3.4-2

[LaMont Jones]

On Tue, Jan 30, 2007 at 02:47:27PM +, Neil McGovern wrote:
> On Mon, Jan 29, 2007 at 04:07:13PM -0700, LaMont Jones wrote:
> Both marked as fixed in 1:9.3.4-2 in our tracker, HOWEVER:
> 355 files changed, 42564 insertions(+), 23165 deletions(-)
> which has lots of changes to lots of files.
> 
> Is there any chance the security/RC issues can be backported?

My mistake here - I had been of the belief that bind 9.3.3 had been
promoted to testing already.

Having said that, I think it would be a good thing to pull 9.3.4-2 into
testing for the following reasons:

1. Absolutely no support from upstream for 9.3.2, other than "upgrade to 9.3.4"

2. DNSSEC actually works well in 9.3.4

3. Other security fixes in 9.3.3 not yet incorporated in 9.3.2

I'm sure there are more.

Pretty please?
lamont


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

please unblock util-linux_2.12r-16

[LaMont Jones]

Please consider promoting util-linux_2.12r-16 to etch.  The first item
in the changelog is the one that really, really wants to be in etch.

The rest are simple fixes to either ugly (or trivial) bugs, making the
risk-benefit good, in my analysis.

Thoughts?
lamont

util-linux (2.12r-16) unstable; urgency=low

  * actually apply 30swsusp-resume.  And support userspace sw susp too.
Closes: #406204
  * Fix off-by-one issue in agetty -I.  Closes: #392445
  * Drop extraneous "again" from hwclock.sh and remove references to
hwclockfirst.sh.  Closes: #396755
  * Drop PAGE_SIZE usage completely, use sysconf(_SC_PAGESIZE).
  * Make intr the default for NFS v2 & v3 mounts in addition to being the
default for NFS v4.  Thanks to Tollef Fog Heen for the idea.

 -- LaMont Jones <[EMAIL PROTECTED]>  Wed, 17 Jan 2007 11:57:35 -0700



signature.asc
Description: Digital signature

Please unblock bind9_9.3.4-2

[LaMont Jones]

Like the subject says, bind9_9.3.4-2 should be promoted to testing,
either now, or in 2 days when it's old enough. :-)  (And yes, I know it
just went through dinstall today...)  It is currently built on alpha,
amd64, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc - which
leaves only m68k lagging, iirc.

9.3.4-2 fixes two security issues that were recently announced by ISC,
along with the release of 9.3.4.

--- 9.3.4 released ---

2126.   [security]  Serialise validation of type ANY responses. [RT #16555]

2124.   [security]  It was possible to dereference a freed fetch
context. [RT #16584]

--- 9.3.3 released ---

thanks,
lamont


signature.asc
Description: Digital signature

please unblock postfix_2.3.6-1

[LaMont Jones]

Please let postfix 2.3.6-1 into testing.  Wietse is probably one of the
most risk averse upstream authors I've ever had the pleasure of
working with - hence his changes in 2.3.5 and 2.3.6 are limited
specifically to bug fixes.

2.3.3-2 introduced a bug (#402788) that affects many upgrades of postfix.
This was fixed in 2.3.5-3, and should really be fixed in etch.

thanks,
lamont

Debian changelog since 2.3.4-3:

  postfix (2.3.6-1) unstable; urgency=low

* New upstream version
* French debconf template.  Closes: #404132
* Galician debconf template.  Closes: #404573
* fix typos in debconf messages.  Closes: #399916
* Catalan debconf template.  Closes: #405320

   -- LaMont Jones <[EMAIL PROTECTED]>  Fri,  5 Jan 2007 19:31:31 -0700

  postfix (2.3.5-3) unstable; urgency=low

* Fix typo.  Closes: #403121
* German translation update.  Closes: #403310

   -- LaMont Jones <[EMAIL PROTECTED]>  Sat, 16 Dec 2006 06:30:17 -0700

  postfix (2.3.5-2) unstable; urgency=low

* Don't call update-inetd in postinst if it's not there.  Fixes Ubuntu
  bug #73511.  Not yet reported in Debian.

   -- LaMont Jones <[EMAIL PROTECTED]>  Wed, 13 Dec 2006 09:04:10 -0700

  postfix (2.3.5-1) unstable; urgency=low

* New upstream version
* mydomain needs some cleanup if we're upgrading from < 2.3.5-1 on a machine
  where hostname(2) is a short name.  Bug introduced in 2.3.3-2.
  Closes: #402788

   -- LaMont Jones <[EMAIL PROTECTED]>  Tue, 12 Dec 2006 15:33:53 -0700

Upstream changelog since 2.3.4:

  20061113

  Bugfix: the Postfix install/upgrade procedure broke with
  non-default config_directory. File: conf/post-install.

  20061115

  Bugfix: null pointer bug in end-of-header Milter action
  when the last header line is too large.  Reported by Mark
  Martinec. The root of the problem is that the MIME state
  engine may execute up to three call-back functions when it
  reaches the end of the headers, before it returns to the
  caller; as long as call-backs return no result, each call-back
  has to check for itself if a previous call-back ran into a
  problem.  File: milter/milter8.c.

  Workaround: reduce effective header_size_limit to 6
  when Milter inspection is enabled, to avoid breaking the
  Milter protocol request length limit. File:
  cleanup/cleanup_message.c.

  20061123

  Workaround: more agressive early refill of in-memory
  recipients to prevent a worst-case scenario where the queue
  manager became starved until after the last batch of slow
  in-memory recipients of jumbo multi-recipient mail. Files:
  qmgr/qmgr_job.c.

  Safety: don't read more than 5000 recipients at a time, to
  avoid spending too much time away from interrupts.  File:
  qmgr/qmgr_message.c.

  20061201

  Workaround: don't complain with "Error 0" in the trivial-rewrite,
  verify, proxymap or connection cache client when the server
  exits after the client sends its request. We still complain,
  however, when the problem persists.  Files: global/rewrite_clnt.c,
  global/resolve_clnt.c, global/verify_clnt.c, global/scache_clnt.c,
  global/dict_proxy.c.


  Safety: the header_size_limit is now enforced more strictly,
  to avoid inter-operability problems with the Milter protocol.
  Long headers are truncated at a line boundary if possible,
  otherwise they are cut between line boundaries. File:
  cleanup/cleanup_out.c.

  20061203

  Bugfix (introduced with Postfix 2.2): with SMTP server
  tarpit delays of smtp_rset_timeout or larger, the SMTP
  client could get out of sync with the server while reusing
  a connection.  The symptoms were "recipient rejected .. in
  reply to DATA".  Fix by Victor Duchovni and Wietse.  File:
  smtp/smtp_proto.c.

  20061207

  Compatibility with Postfix < 2.3: undo the change to bounce
  instead of defer after pipe-to-command delivery fails with
  a signal. File: global/pipe_command.c.

  20061208

  Workaround: apparently, some mail software removes or hides
  "" in the Postfix bounce text, because it
  processes the text as if it were HTML. This confuses users.
  The bounce template has been updated to remove the < and
  >. File: bounce/bounce_templates.c.

  Cleanup: when smtp_generic_maps is turned on, don't parse
  MIME structures in the message body. Victor Duchovni. File:
  smtp/smtp_proto.c.

  20061210

  Robustness: low-cost re-entrancy guard that allows daemons
  to call msg_fatal() etc. from a signal handler, without
  risking memory

Re: BIND 8 deprecation for the release notes

[LaMont Jones]

On Fri, Jan 12, 2007 at 10:12:44PM +0100, Andreas Barth wrote:
> * Moritz Muehlenhoff ([EMAIL PROTECTED]) [070111 19:31]:
> About bind 8, I'm not so sure. Do the maintainers have any opinion about
> bind 8?

I just uploaded 'bind8' and friends (sitting in NEW last I saw), with a
README that deprecates it.  I'd be happy to upload a new 'bind' to TPU
with the deprecation in it as well, or we could consider pulling BIND8
into testing.

There are still some uses for BIND8, but they're getting smaller and
smaller.

thoughts?
lamont


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

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

[LaMont Jones]

On Wed, Jan 10, 2007 at 01:51:52PM -0700, LaMont Jones wrote:
> I'll freshen and clean the chroot and do a new build.

Broken chroot, all is well now.

lamont


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

Re: 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]

Re: libmail-cclient-perl

[LaMont Jones]

On Tue, May 10, 2005 at 10:13:41AM +0200, Jeroen van Wolffelaar wrote:
> line 495: 1.399 (lamont 05-Mar-04): %libmail-cclient-perl: !ia64 # [ANAIS]
> So, this package is marked as 'not for ia64', this line should be
> removed if that's no longer the case, or the ia64 binary should be
> removed if this is still valid (I don't see any rationale for this,
> except that the package apparantly excluded ia64 from its architecture:
> line previously, so I guess not).

ANAIS == arch not allowed in source.

Removed.

lamont


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

Re: lablgtk2 and misbehaved hppa/ia64 autobuilders.

[LaMont Jones]

On Thu, Mar 31, 2005 at 10:03:57AM +0200, Sven Luther wrote:
> Oh, it seems [EMAIL PROTECTED] is the canonical address, CCing there.

Yeah - I'm not actively reading debian-hppa, if I'm even subscribed to
it.

> Hi hppa buildd maintainers. We have a problem with the ocaml packages on hppa,
> since the buildd infrastructure is broken and don't handles virtual packages
> dependencies all to well. Could you retrigger the build of the below packages 
> ?
Will kick the dep-waits around

lamont


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

Re: util-linux for sarge

[LaMont Jones]

On Sat, Mar 26, 2005 at 11:45:26PM -0800, Thomas Bushnell BSG wrote:
> LaMont Jones <[EMAIL PROTECTED]> writes:
> > A source of many issues, and divergence from upstream, was the hurd
> > patch, which was dropped in 2.12l-1.  Having that code, with it's bugs,
> > in sarge would be painful.
> Why not fix the bugs?

1) it quit compiling in 2.12-3 (2.12-10 is in sarge)
2) that code is the source of much divergence from upstream, resulting
   in annoyance there.
3) No one from the hurd camp has stepped forward to address the bugs.

lamont


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

Re: util-linux for sarge

[LaMont Jones]

On Sat, Mar 26, 2005 at 03:49:17PM -0800, Steve Langasek wrote:
> On Sat, Mar 26, 2005 at 09:39:41AM -0700, LaMont Jones wrote:
> > An alternative that is less invasive to sarge would be to drop libblkid1
> > support from a t-p-u upload.
> Well, the version of mount currently in testing doesn't seem to use
> libblkid at all... :)

True, and badly phrased on my part.  An alternative if we want to get
the rest of the 2.12p fixes into sarge would be to drop libblkid1 use.

A source of many issues, and divergence from upstream, was the hurd
patch, which was dropped in 2.12l-1.  Having that code, with it's bugs,
in sarge would be painful.

lamont


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

Re: util-linux for sarge

[LaMont Jones]

On Fri, Mar 25, 2005 at 05:16:14PM -0800, Steve Langasek wrote:
> Additional con:
>  - depends on a newer version of e2fsprogs than we currently have in
> testing, which requires updating roughly a half dozen frozen libraries
> Hrm, this looks like a bug in libblkid1 to me, since the shlibs were not
> updated when the new public functions were added...

There is a security vulnerability caused by mount using the older
version of libblkid1, which didn't verify that euid=uid before blindly
using an environment variable for a file name...

One might argue that this is sufficient reason to bump the soname, but
sid and hoary are the only users of that function in that manner (inside
mount).

An alternative that is less invasive to sarge would be to drop libblkid1
support from a t-p-u upload.

lamont


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

util-linux for sarge

[LaMont Jones]

Please consider util-linux 2.12p-4 for Sarge.  Relevant changelog chunk
below.

Cons:
  - it's a change

Pros:
  - Fixes for a number of bugs.  2.12j through 2.12p were the result of
a bunch of activity between upstream and myself.
  - 2.12p-1 has been in sid since December, and -2 through -4 change
next to nothing (yes, "next to nothing" includes that security vul
compliments of libblkid1 fixed in -4.)
  - 2.12-10 (currently in sarge) represents only minor tweaks since the
previous significant work back in Feb 2004.
  - 2.12p-4 uses dpatch instead of a large monolithic .diff.gz, making
it much easier to maintain down the road.

thoughts?
lamont

util-linux (2.12p-4) unstable; urgency=low

  * Depend on newer libblkid1.

 -- LaMont Jones <[EMAIL PROTECTED]>  Thu, 17 Mar 2005 11:50:49 -0700

util-linux (2.12p-3) unstable; urgency=low

  * Add an alternative for pager pointing at pg (at pref 10).  Closes: #294218
  * enable fdisk on s390.  Closes: #238151

 -- LaMont Jones <[EMAIL PROTECTED]>  Tue,  8 Feb 2005 13:45:34 -0700

util-linux (2.12p-2) unstable; urgency=low

  * Really fix man page in alternatives.  Closes: #145647
  * more typos in hwclockfirst.sh.  Closes: #276372

 -- LaMont Jones <[EMAIL PROTECTED]>  Sat, 25 Dec 2004 08:08:12 -0700

util-linux (2.12p-1) unstable; urgency=low

  * New upstream version. (2.12p)
Closes: #182325, #270173, #192751, #229875, #230859, #214144, #254317, 
#272580
- cfdisk: fix number of new partition when partitions not in disk order
- fdisk: fix Sun label handling in sector mode
- mkfs: never truncate filename (not that that ever happened)
- more: fix redraw flaw.  Closes: #146678
  * New upstream version. (2.12o)  Closes: #286519, #132998, #207236
- lomount: revert patch from 2.12j
- lptune.8: -T option is obsolete
- mkswap, mkswap.8, swapon: support labels
  (use HAVE_BLKID=no as long as the blkid library doesnt support this)
- umount: allow user unmounting repeatedly mounted nfs mounts
  * Build-Depend on uuid-dev.  Closes: #282668
  * correct chown args in debian/rules.  Closes: #254780
  * include man page in update-alternatives for pager.  Closes: #145647
  * fix typos in howclockfirst.sh.  Closes: #276372
  * fix losetup -N documentation.  Closes: #239475
  * cleanup some narrow window sprintf issues in cfdisk.

 -- LaMont Jones <[EMAIL PROTECTED]>  Fri, 24 Dec 2004 14:38:23 -0700

util-linux (2.12m-1) unstable; urgency=low

  * New upstream version
- cfdisk: recognize JFS, support reiserfs labels ([EMAIL PROTECTED])
- mount: fix option parsing bug
- mount.8: several updates
    - swapon.8: document -v option

 -- LaMont Jones <[EMAIL PROTECTED]>  Mon, 20 Dec 2004 10:46:16 -0700

util-linux (2.12l-1) unstable; urgency=low

  * New upstream version, shrinking the size of the Debian diff.
- Makefile: remove cat-id-tbl.c upon make clean
- fdisk: fixed a bug that would cause a non-update of a sun disklabel
- fdisk: use sectorsize instead of 512 for SGI (Eric Y. Theriault)
- fdisk: use __attribute__((packed)) for alpha, ARM: avoid unaligned 
accesses
- hwclock: actually use HAVE_tm_gmtoff
- swapon: fix priority handling
- umount: refuse to unmount an empty string
  * Jetisoning the (broken) hurd patch for now.

 -- LaMont Jones <[EMAIL PROTECTED]>  Wed, 15 Dec 2004 17:27:44 -0700

util-linux (2.12k-2) unstable; urgency=low

  * Switch to dpatch.
  * Clean up --nohashpass in losetup.  Closes: #285639
  * Use stat instead of open in losetup.  (From #285353)

 -- LaMont Jones <[EMAIL PROTECTED]>  Wed, 15 Dec 2004 10:43:29 -0700

util-linux (2.12k-1) unstable; urgency=low

  * New upstream version.
* various translation updates
* gcc-3.4 support help

 -- LaMont Jones <[EMAIL PROTECTED]>  Mon, 13 Dec 2004 16:50:57 -0700

util-linux (2.12j-3) unstable; urgency=low

  * umount -l "" does bad things.  Don't do let the user do that.
  * remove non-utf8 characters from changelog.  sorry.

 -- LaMont Jones <[EMAIL PROTECTED]>  Fri, 10 Dec 2004 07:11:02 -0700

util-linux (2.12j-2) unstable; urgency=low

  * uninitialized variable.  Closes: #284597

 -- LaMont Jones <[EMAIL PROTECTED]>  Tue,  7 Dec 2004 10:52:55 -0700

util-linux (2.12j-1) unstable; urgency=low

  * New upstream version

 -- LaMont Jones <[EMAIL PROTECTED]>  Mon,  6 Dec 2004 03:29:45 -0700

util-linux (2.12h-4) unstable; urgency=low

  * mkswap on a file was broken. Thanks to Bas Zoetekouw <[EMAIL PROTECTED]>
for the patch.  Closes: #280032, #282678
  * add libblkid-dev to Build-Depends.  Closes: #282668

 -- LaMont Jones <[EMAIL PROTECTED]>  Thu,  2 Dec 2004 10:42:04 -0700

util-linux (2.12h-3) unstable; urgency=low

  * Fix mount segv's.  Closes: #279306

 -- LaMont Jones <[EMAIL PROTECTED]>  Wed,  3 Nov 2004 10:09:43 -0700

util-linux (2.12h-2) unstable; urgency=low

  * Cleanup t

Re: Bug#262941: What's the status of the modutils RC bugs, anyone investigated it?

[LaMont Jones]

On Wed, Oct 06, 2004 at 07:37:24PM +0200, Javier Fernández-Sanguino Peña wrote:
> I'm just curious since I sent a patch for this bug to #263224 almost a week 
> ago, sent a mail to debian-release [1] and nobody has taken action. Is 
> nobody (not even the maintainers!) addressing RC bugs in base packages? Was 
> this mail lost in the noise? Should I risk an NMU?  What is 
> the Answer to Life, the Universe, and Everything?

The maintainer has been out of town, and away from email.  I'll be
looking at modutils sometime this week, I expect.

lamont

util-linux/getty bug

[LaMont Jones]

I just uploaded 2.12-8 with Samuel Thibault's patch to sid.  The only
change from 2.12-7 is the fix for the 5 (duplicate) serious bugs in
getty.  #226443 has the patch from Samuel.

Once it's built on the buildd's, please snap it into sarge.

thanks,
lamont

Re: util-linux bug severity

[LaMont Jones]

On Sun, Sep 19, 2004 at 11:50:04PM +0100, Colin Watson wrote:
> On Sun, Sep 19, 2004 at 09:13:56PM +0200, Laszlo 'GCS' Boszormenyi wrote:
> Um. I had been under the impression that the latest version *fixed* this
> bug, which was one of the reasons I pushed it through to sarge.
> LaMont?

The bug remains that getty is launched being told to use a tty that the
kernel still has marked in use.  I have yet to isolate just exactly
_who_ the kernel thinks has it in use, so as to reassign the bug
appropriately.

lamont