[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#317106: marked as done (gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link)



Your message dated Wed, 6 Jul 2005 13:52:00 +0200
with message-id <17099.50656.706845.48480@gargle.gargle.HOWL>
and subject line Bug#317106: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link
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; 6 Jul 2005 11:18:52 +0000
>From arne.anka@gmx.net Wed Jul 06 04:18:52 2005
Return-path: <arne.anka@gmx.net>
Received: from mail.bytecamp.net [212.204.60.9] 
	by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
	id 1Dq7vX-000699-00; Wed, 06 Jul 2005 04:18:52 -0700
Received: (qmail 1838 invoked by uid 85); 6 Jul 2005 11:18:20 -0000
Received: from arne.anka@gmx.net by mail.bytecamp.net by uid 88 with qmail-scanner-1.20 
 (clamscan: 0.85.1  Clear:RC:0(80.146.187.235):. 
 Processed in 4.575023 secs); 06 Jul 2005 11:18:20 -0000
Received: from unknown (HELO decodon.com) (mathias.fricke@ginguppin.de@80.146.187.235)
  by mail.bytecamp.net with SMTP; 6 Jul 2005 11:18:15 -0000
To: "Debian Bug Tracking System" <submit@bugs.debian.org>
Subject: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link
Date: Wed, 06 Jul 2005 13:17:49 +0200
From: "Arne Anka" <arne.anka@gmx.net>
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <[🔎] op.sthobzzaorjy69@decodon.com>
User-Agent: Opera M2/8.01 (Linux, build 1204)
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: gcc-4.0
Version: 4.0.0-12
Severity: normal

gcc should warn or, better, ask before changing the target of the link
/usr/bin/gcc. i lost a half day of work just because /usr/bin/gcc since
the update today in the morning points to gcc-4.0 instead of 3.3 which
broke my library i had to compile. i solely by chance detected this
change.

-- 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.11.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gcc-4.0 depends on:
ii  binutils                 2.15.94.0.2.2-1 The GNU assembler, linker and  
bina
ii  cpp-4.0                  4.0.0-12        The GNU C preprocessor
ii  gcc-4.0-base             4.0.0-12        The GNU Compiler Collection  
(base
ii  libc6                    2.3.2.ds1-23    GNU C Library: Shared  
libraries an
ii  libgcc1                  1:4.0.0-12      GCC support library

Versions of packages gcc-4.0 recommends:
ii  libc6-dev                   2.3.2.ds1-23 GNU C Library: Development  
Librari
pn  libmudflap0-dev             <none>       (no description available)

-- no debconf information

---------------------------------------
Received: (at 317106-done) by bugs.debian.org; 6 Jul 2005 11:52:09 +0000
>From doko@cs.tu-berlin.de Wed Jul 06 04:52:09 2005
Return-path: <doko@cs.tu-berlin.de>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Dq8Rk-0002Ju-00; Wed, 06 Jul 2005 04:52:09 -0700
Received: from mailhost.cs.tu-berlin.de (postfix@mail.cs.tu-berlin.de [130.149.17.13])
	by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id NAA15851;
	Wed, 6 Jul 2005 13:52:06 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
	by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 3F637FC60;
	Wed,  6 Jul 2005 13:52:06 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
 by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
 id 10830-45; Wed,  6 Jul 2005 13:52:01 +0200 (MEST) 11274
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
	by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
	Wed,  6 Jul 2005 13:52:01 +0200 (MEST)
Received: (from doko@localhost)
	by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j66Bq0vk010833;
	Wed, 6 Jul 2005 13:52:00 +0200 (MEST)
From: Matthias Klose <doko@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17099.50656.706845.48480@gargle.gargle.HOWL>
Date: Wed, 6 Jul 2005 13:52:00 +0200
To: "Arne Anka" <arne.anka@gmx.net>, 317106-done@bugs.debian.org
Subject: Re: Bug#317106: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link
In-Reply-To: <[🔎] op.sthobzzaorjy69@decodon.com>
References: <[🔎] op.sthobzzaorjy69@decodon.com>
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: 317106-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-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
X-Spam-Level: 

Arne Anka writes:
> Package: gcc-4.0
> Version: 4.0.0-12
> Severity: normal
> 
> gcc should warn or, better, ask before changing the target of the link
> /usr/bin/gcc. i lost a half day of work just because /usr/bin/gcc since
> the update today in the morning points to gcc-4.0 instead of 3.3 which
> broke my library i had to compile. i solely by chance detected this
> change.

no. you can either install apt-listchanges, inspecting the packages
you upgrade, or read debian-devel-announce.



Reply to: