Processed: forcibly merging 603102 603101

To: Bastian Blank <waldi@debian.org>
Cc: GNU Libc Maintainers <debian-glibc@lists.debian.org> (libc6 for {603102,603101})
Subject: Processed: forcibly merging 603102 603101
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 11 Nov 2010 12:03:10 +0000
Message-id: <[🔎] handler.s.C.12894767277708.transcript@bugs.debian.org>
In-reply-to: <1289476705-1011-bts-waldi@debian.org>
References: <1289476705-1011-bts-waldi@debian.org>

Processing commands for control@bugs.debian.org:

> forcemerge 603102 603101
Bug#603102: After update of libc6 from 2.7-18lenny4 to 2.7-18lenny6, virtual machines (VirtualBox) unable to start.
Bug#603101: After update of libc6 from 2.7-18lenny4 to 2.7-18lenny6, virtual machines (VirtualBox) unable to start.
Forcibly Merged 603101 603102.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
603102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603102
603101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603101
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Reply to:

Prev by Date: Bug#603102: After update of libc6 from 2.7-18lenny4 to 2.7-18lenny6, virtual machines (VirtualBox) unable to start.
Next by Date: Bug#603102: After update of libc6 from 2.7-18lenny4 to, 2.7-18lenny6, virtual machines (VirtualBox) unable to start.
Previous by thread: Bug#603102: marked as done (After update of libc6 from 2.7-18lenny4 to 2.7-18lenny6, virtual machines (VirtualBox) unable to start.)
Next by thread: Bug#603102: After update of libc6 from 2.7-18lenny4 to, 2.7-18lenny6, virtual machines (VirtualBox) unable to start.
Index(es):
- Date
- Thread