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

Bug#207132: marked as done (debian-policy is missing gcc transition plans)

Your message dated Wed, 04 Jul 2007 01:26:32 -0700
with message-id <87odisr2vb.fsf@windlord.stanford.edu>
and subject line Bug#207132: debian-policy is missing gcc transition plans
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)
--- Begin Message --- 
Package: debian-policy
Version: 3.6.1.0
Severity: normal

Hi,

again someone asks for what to do about gcc 2.95->3.2 transition and
the right place would be to point to the debian-policy package just as
with the libc6 transition.

Please include
  http://people.debian.org/~rmurray/c++transition.html
as soon as possible.

MfG
	Goswin

Ps: you might want to consider retiring the libc6 transition document.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dual 2.4.21-ac4 #1 SMP Sat Jul 5 17:53:13 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE

-- no debconf information

--- End Message ---
--- Begin Message --- 
Regardless of the merits of including transition plans in the Policy
package in general, this particular transition (gcc 2.95 to gcc 3.2) is
now so far in the past that I don't see any point in leaving this bug
open.

The project has since found other ways of discussing transition plans, and
my guess is that eventually the libc transition document will either be
kicked out of the debian-policy package or put somewhere appropriate as a
historic document.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

--- End Message ---
Reply to: