On Sat, Jan 23, 2010 at 04:13:37PM +0100, Ralf Treinen wrote: > Hi Ron, > > On Sat, Jan 23, 2010 at 09:05:39PM +1030, Ron wrote: > > > > Hi Ralf, > > > > On Thu, Jan 21, 2010 at 10:27:26PM +0100, Ralf Treinen wrote: > > > I filed bug #542269 with severity=serious 3 months ago, but I cannot > > > find any trace of progress in the BTS. Is anyone looking at this bug? > > > > I thought it was fairly self evident that newlib-mingw32 was overwriting > > files from the toolchain. > > Well, for me that is not that obvious, since the fault can a priori be > in either of the two packages: had I first installed newlib-mingw3, > and then mingw32-runtime, then it would have been mingw32-runtime > that overwrites the files. However, I do not know a thing about > either of the two packages, I just detected the problem when running > distro-wide tests.
Yes sorry, I didn't mean obvious to you necessarily, I could see what you were doing, I meant to the people who need to do something to fix it, or who would bump into it when trying to actually use it. What you had already said was pretty much all the information I thought this report should need to get resolved. > You should care since the bug is filed against *both* packages. Hence, > you have an RC bug against mingw32-runtime. IF it is settled that > newlib-mingw3 is at fault then the bug should be reassigned to > that package (bts reasssign 542269 newlib-mingw3). For that you > should try to find an agreement with the maintainer of newlib-mingw3, > Arthur Loiret. For that we'll need to hear from Arthur :) Nothing is settled until that happens, but the longer it goes without any actual users reporting this trouble with it, the less I'm inclined to believe they actually do exist. So anyhow, Arthur, if there is something I can tweak to help you out here, let me know, but afaics it's the newlib package that will want to do any conflicting or replacing, or hiding in a different subtree (with its own triplet perhaps?) ... Me making parts of the toolchain conflict with it doesn't seem like the answer we're probably after. Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
