Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)

2012-09-23 Thread Matthias Klose
On 22.09.2012 15:04, Andreas Beckmann wrote: On 2012-09-22 12:08, Matthias Klose wrote: I don't want this in gcc-4.7. Please provide a patch for gcc-defaults. This should work as well. That won't work, just tried it. The only package from gcc-defaults that could be involved in the

Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)

2012-09-23 Thread Andreas Beckmann
On 2012-09-23 14:32, Matthias Klose wrote: On 22.09.2012 15:04, Andreas Beckmann wrote: On 2012-09-22 12:08, Matthias Klose wrote: I don't want this in gcc-4.7. Please provide a patch for gcc-defaults. This should work as well. That won't work, just tried it. The only package from

Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)

2012-09-22 Thread Andreas Beckmann
reassign 677582 gcc-4.7-base 4.7.2-2 reopen 677582 thanks On 2012-09-21 14:22, Andreas Beckmann wrote: [...] I'm now trying to add these Breaks to gcc-4.7-base, that can't be held back, hopefully. Attached is a diff that finally fixes this upgrade issue, hopefully. gcc-4.7-base isn't that

Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)

2012-09-22 Thread Matthias Klose
I don't want this in gcc-4.7. Please provide a patch for gcc-defaults. This should work as well. On 22.09.2012 09:23, Andreas Beckmann wrote: reassign 677582 gcc-4.7-base 4.7.2-2 reopen 677582 thanks On 2012-09-21 14:22, Andreas Beckmann wrote: [...] I'm now trying to add these Breaks to

Bug#677582: needs to be fixed in gcc-4.7-base (gcc-4.4-base: upgrade problems since removal of gcj-4.4)

2012-09-22 Thread Andreas Beckmann
On 2012-09-22 12:08, Matthias Klose wrote: I don't want this in gcc-4.7. Please provide a patch for gcc-defaults. This should work as well. That won't work, just tried it. The only package from gcc-defaults that could be involved in the problematic upgrade paths is gcj-jre-headless and that