Bug#722542: gcc-spu went away but is still being used
On 2013-11-26 13:46, Agustin Henze wrote: > Hi all, I'm glad to announce that I've adopted this package :) Hi, Thanks for taking care of this package. :) > and I've > uploaded a new version (2.0.0-1). This version doesn't build newlib-spu > anymore. It arrived on the archive a few days ago, should I request the > removal > of the old packages for close this bug? If they have no more rdeps in sid, then yes. > I just read[0] that "rene" should take over about it. But newlib orig 1.18 > still there :/ and the cruft-report doesn't show results about newlib. I don't > understand what happens, it's the first time that I have to deal with > something > like this. If someone can point me what is the correct way that I should > proceed I'll be very grateful. > > [0] https://wiki.debian.org/ftpmaster_Removals > I believe filing the bug will be correct in this case. :) ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722542: gcc-spu went away but is still being used
Hi all, I'm glad to announce that I've adopted this package :) and I've uploaded a new version (2.0.0-1). This version doesn't build newlib-spu anymore. It arrived on the archive a few days ago, should I request the removal of the old packages for close this bug? I just read[0] that "rene" should take over about it. But newlib orig 1.18 still there :/ and the cruft-report doesn't show results about newlib. I don't understand what happens, it's the first time that I have to deal with something like this. If someone can point me what is the correct way that I should proceed I'll be very grateful. [0] https://wiki.debian.org/ftpmaster_Removals -- TiN signature.asc Description: OpenPGP digital signature
Bug#722542: gcc-spu went away but is still being used
Control: severity -1 serious On 2013-09-12 14:37, Matthias Klose wrote: > Control: reassign -1 newlib > > Am 12.09.2013 08:31, schrieb Niels Thykier: >> Package: gcc-defaults,newlib >> Severity: important >> >> Dear maintainers of gcc-defaults and newlib, >> >> I noticed that gcc-defaults have removed the "gnu-spu" package in sid, >> but newlib still build-depends on it. Since there was no bug against >> either package, I am assuming no one has noticed this so far. As it >> is, this is one (of several) things blocking gcc-defaults migration to >> testing. >> >> This bug can be fixed either by re-introducing gcc-spu (possibly as a >> transitional package, if gcc-spu is no longer needed) or by newlib no >> longer Build-Depending on gcc-spu (since it is the last package using >> it). I will leave it to you to decide how this will be solved; please >> reassign this bug to the proper package. > > I don't maintain the spu cross toolchain anymore, as previously written to the > gcc and powerpc ML. So newlib maybe shouldn't build the spu packages anymore. > > Matthias > Hi all, This is currently blocking gcc-defaults from migrating to testing (and by extension a lot of other packages that is currently waiting for gcc-defaults), so I am bumping the severity to RC. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722542: gcc-spu went away but is still being used
Am 12.09.2013 18:06, schrieb Geoff Levand: > Hi, > > On Thu, 2013-09-12 at 14:37 +0200, Matthias Klose wrote: >> Control: reassign -1 newlib >> >> Am 12.09.2013 08:31, schrieb Niels Thykier: >>> Package: gcc-defaults,newlib >>> Severity: important >>> >>> Dear maintainers of gcc-defaults and newlib, >>> >>> I noticed that gcc-defaults have removed the "gnu-spu" package in sid, >>> but newlib still build-depends on it. Since there was no bug against >>> either package, I am assuming no one has noticed this so far. As it >>> is, this is one (of several) things blocking gcc-defaults migration to >>> testing. >>> >>> This bug can be fixed either by re-introducing gcc-spu (possibly as a >>> transitional package, if gcc-spu is no longer needed) or by newlib no >>> longer Build-Depending on gcc-spu (since it is the last package using >>> it). I will leave it to you to decide how this will be solved; please >>> reassign this bug to the proper package. >> >> I don't maintain the spu cross toolchain anymore, as previously written to >> the >> gcc and powerpc ML. So newlib maybe shouldn't build the spu packages anymore. > > I guess this means users will also need to build newlib (in addition to > the gnu-spu) if they want to do spu programming for cell. yes. > Matthias, please let us know in general what a user needs to do for > this. well, the spu cross toolchain needs packaging from a separate source package, like done for the mingw64 packages. I suppose newlib needs an update too, Arthur Loiret is MIA, so the package maybe should be orphaned or taken over as well. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722542: gcc-spu went away but is still being used
Hi, On Thu, 2013-09-12 at 14:37 +0200, Matthias Klose wrote: > Control: reassign -1 newlib > > Am 12.09.2013 08:31, schrieb Niels Thykier: > > Package: gcc-defaults,newlib > > Severity: important > > > > Dear maintainers of gcc-defaults and newlib, > > > > I noticed that gcc-defaults have removed the "gnu-spu" package in sid, > > but newlib still build-depends on it. Since there was no bug against > > either package, I am assuming no one has noticed this so far. As it > > is, this is one (of several) things blocking gcc-defaults migration to > > testing. > > > > This bug can be fixed either by re-introducing gcc-spu (possibly as a > > transitional package, if gcc-spu is no longer needed) or by newlib no > > longer Build-Depending on gcc-spu (since it is the last package using > > it). I will leave it to you to decide how this will be solved; please > > reassign this bug to the proper package. > > I don't maintain the spu cross toolchain anymore, as previously written to the > gcc and powerpc ML. So newlib maybe shouldn't build the spu packages anymore. I guess this means users will also need to build newlib (in addition to the gnu-spu) if they want to do spu programming for cell. Matthias, please let us know in general what a user needs to do for this. -Geoff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722542: gcc-spu went away but is still being used
Control: reassign -1 newlib Am 12.09.2013 08:31, schrieb Niels Thykier: > Package: gcc-defaults,newlib > Severity: important > > Dear maintainers of gcc-defaults and newlib, > > I noticed that gcc-defaults have removed the "gnu-spu" package in sid, > but newlib still build-depends on it. Since there was no bug against > either package, I am assuming no one has noticed this so far. As it > is, this is one (of several) things blocking gcc-defaults migration to > testing. > > This bug can be fixed either by re-introducing gcc-spu (possibly as a > transitional package, if gcc-spu is no longer needed) or by newlib no > longer Build-Depending on gcc-spu (since it is the last package using > it). I will leave it to you to decide how this will be solved; please > reassign this bug to the proper package. I don't maintain the spu cross toolchain anymore, as previously written to the gcc and powerpc ML. So newlib maybe shouldn't build the spu packages anymore. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722542: gcc-spu went away but is still being used
Package: gcc-defaults,newlib Severity: important Dear maintainers of gcc-defaults and newlib, I noticed that gcc-defaults have removed the "gnu-spu" package in sid, but newlib still build-depends on it. Since there was no bug against either package, I am assuming no one has noticed this so far. As it is, this is one (of several) things blocking gcc-defaults migration to testing. This bug can be fixed either by re-introducing gcc-spu (possibly as a transitional package, if gcc-spu is no longer needed) or by newlib no longer Build-Depending on gcc-spu (since it is the last package using it). I will leave it to you to decide how this will be solved; please reassign this bug to the proper package. Thank you in advance, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
