Bug#324643: marked as done (symbolic link loop: /usr/src/linux-headers-2.6.12-1-386/arch/i386/Makefile)
Your message dated Mon, 3 Oct 2005 16:38:35 +0900
with message-id <20051003073834.GI5059@verge.net.au>
and subject line Bug#324643: symbolic link loop: /usr/src/linux-headers-2.6.12-1-386/arch/i386/Makefile
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 23 Aug 2005 08:50:53 +0000
>From zn@mbf.nifty.com Tue Aug 23 01:50:53 2005
Return-path: <zn@mbf.nifty.com>
Received: from master.debian.org [146.82.138.7]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E7UUf-00027t-00; Tue, 23 Aug 2005 01:50:53 -0700
Received: from gnulinux.good-day.net (localhost.localdomain) [220.218.190.206]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1E7UUd-0008KU-00; Tue, 23 Aug 2005 03:50:52 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Kazuhiro NISHIYAMA <zn@mbf.nifty.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: symbolic link loop: /usr/src/linux-headers-2.6.12-1-386/arch/i386/Makefile
X-Mailer: reportbug 3.15
Date: Tue, 23 Aug 2005 17:51:04 +0900
X-Debbugs-Cc: zn@mbf.nifty.com
Message-Id: <E1E7UUd-0008KU-00@master.debian.org>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-9.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
OUR_MTA_MSGID,X_DEBBUGS_CC autolearn=ham
version=2.60-bugs.debian.org_2005_01_02
Package: linux-headers-2.6.12-1-386
Version: 2.6.12-5
Severity: important
When make modules,
error occured:
/usr/src/linux-headers-2.6.12-1-386/arch/i386/Makefile: Too many levels
of symbolic links
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages linux-headers-2.6.12-1-386 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii linux-headers-2.6.12-1 2.6.12-5 Common architecture-specific heade
linux-headers-2.6.12-1-386 recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 324643-done) by bugs.debian.org; 3 Oct 2005 09:32:45 +0000
>From horms@koto.vergenet.net Mon Oct 03 02:32:45 2005
Return-path: <horms@koto.vergenet.net>
Received: from koto.vergenet.net [210.128.90.7]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EMMgf-0008Ob-00; Mon, 03 Oct 2005 02:32:45 -0700
Received: by koto.vergenet.net (Postfix, from userid 7100)
id 818F234044; Mon, 3 Oct 2005 18:32:14 +0900 (JST)
Date: Mon, 3 Oct 2005 16:38:35 +0900
From: Horms <horms@debian.org>
To: jurij@wooyd.org, 324643-done@bugs.debian.org
Subject: Re: Bug#324643: symbolic link loop: /usr/src/linux-headers-2.6.12-1-386/arch/i386/Makefile
Message-ID: <20051003073834.GI5059@verge.net.au>
References: <Pine.LNX.4.63.0509302123230.6033@bobcat>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.63.0509302123230.6033@bobcat>
X-Cluestick: seven
User-Agent: Mutt/1.5.10i
Delivered-To: 324643-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
On Fri, Sep 30, 2005 at 09:26:27PM -0700, Jurij Smakov wrote:
> Hi,
>
> As far as I can tell, this bug has been caused by a packaging glitch, but
> has been fixed at least since the release 2.6.12-6, while the current one
> is 2.6.12-10. Is there any reason for this bug to be still open?
On the theory that closed bugs are good bugs, I'm closing
this on the strength of your comments. Interested parties,
please reopen if need be.
--
Horms
Reply to: