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

Bug#708521: marked as done (pu: package gcc-4.7/4.7.2-5+deb7u1)

Your message dated Mon, 30 Sep 2013 00:30:38 +0200
with message-id <20130929223038.GL21946@mraw.org>
and subject line Re: Bug#708521: pu: package gcc-4.7/4.7.2-5+deb7u1
has caused the Debian Bug report #708521,
regarding pu: package gcc-4.7/4.7.2-5+deb7u1
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
708521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708521
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: pu

Hi,

I'd like to get gcc-4.7 updated in wheezy to add an extra Breaks that
will fix some upgrade paths from squeeze (#690172).
It's mainly about giving apt a small push to remove some obsolete
packages (that existed in squeeze but no longer exist in wheezy) and
therefore properly upgrade all packages and don't 'keep back' that many.

I ve been testing this in piuparts for a long time now without running
into problems, but getting much cleaner upgrade results :-)

I would clearly prefer a maintainer upload (perhaps with some more
cherry-picked fixes) instead of doing a NMU.


Andreas

diff -u gcc-4.7-4.7.2/debian/control gcc-4.7-4.7.2/debian/control
--- gcc-4.7-4.7.2/debian/control
+++ gcc-4.7-4.7.2/debian/control
@@ -18,7 +18,7 @@
 Priority: required
 Depends: ${misc:Depends}
 Replaces: ${base:Replaces}
-Breaks: gcj-4.4-base (<< 4.4.6-9~), gnat-4.4-base (<< 4.4.6-3~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.6 (<< 4.6.1-5~), dehydra (<= 0.9.hg20110609-2)
+Breaks: gcc-4.4-base (<< 4.4.7), gcj-4.4-base (<< 4.4.6-9~), gnat-4.4-base (<< 4.4.6-3~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.6 (<< 4.6.1-5~), dehydra (<= 0.9.hg20110609-2)
 Description: GCC, the GNU Compiler Collection (base package)
  This package contains files common to all languages and libraries
  contained in the GNU Compiler Collection (GCC).
diff -u gcc-4.7-4.7.2/debian/control.m4 gcc-4.7-4.7.2/debian/control.m4
--- gcc-4.7-4.7.2/debian/control.m4
+++ gcc-4.7-4.7.2/debian/control.m4
@@ -105,7 +105,7 @@
 Priority: PRI(required)
 Depends: ${misc:Depends}
 Replaces: ${base:Replaces}
-Breaks: gcj-4.4-base (<< 4.4.6-9~), gnat-4.4-base (<< 4.4.6-3~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.6 (<< 4.6.1-5~), dehydra (<= 0.9.hg20110609-2)
+Breaks: gcc-4.4-base (<< 4.4.7), gcj-4.4-base (<< 4.4.6-9~), gnat-4.4-base (<< 4.4.6-3~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.6 (<< 4.6.1-5~), dehydra (<= 0.9.hg20110609-2)
 Description: GCC, the GNU Compiler Collection (base package)
  This package contains files common to all languages and libraries
  contained in the GNU Compiler Collection (GCC).
diff -u gcc-4.7-4.7.2/debian/changelog gcc-4.7-4.7.2/debian/changelog
--- gcc-4.7-4.7.2/debian/changelog
+++ gcc-4.7-4.7.2/debian/changelog
@@ -1,3 +1,10 @@
+gcc-4.7 (4.7.2-5.0anbe0piuparts0gcc47.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * gcc-4.7-base: Add Breaks: gcc-4.4-base (<< 4.4.7)  (Closes: #690172)
+
+ -- Andreas Beckmann <debian@abeckmann.de>  Thu, 17 Jan 2013 14:10:12 +0100
+
 gcc-4.7 (4.7.2-5) unstable; urgency=low
 
   * Add __gnu_* symbols to the libgcc1 symbols file for armel and armhf.

--- End Message ---
--- Begin Message --- 
Julien Cristau <jcristau@debian.org> (2013-06-03):
> On Mon, Jun  3, 2013 at 20:02:45 +0200, Andreas Beckmann wrote:
> 
> > I'm pretty confident this only has an influence on the upgrades that
> > didn't upgrade gcc-4.4-base (and kept the version from squeeze).
> > I can help testing upgrade paths in advance if you can describe some
> > squeeze package sets you are interested in.
> > And I'll help debugging+fixing in case there are any unexpected failures
> > caused by this.
> > 
> The time to play with/debug/fix the upgrade path is a year ago, not post
> release, IMO.  For non-critical issues (and "a few packages are held
> back and need manual handling" certainly isn't critical), I don't think
> we should be doing anything at this stage.  I don't think any amount of
> testing is going to convince me otherwise.  OMMV.

Same mileage here. Already not happy with situations which are way
easier, so certainly not going to play around with core packages like
those. Closing accordingly.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: