Bug#552018: Upgrading to grave

2010-01-25 Thread brian m. carlson
On Sun, Jan 24, 2010 at 09:22:33PM +0100, Daniel Leidert wrote: > You can easily workaround that. Just write your own catalog with > entries: I have a better solution: a working resolver. I did some looking into the code, and I found the problem. In Catalog.java, the method addDelegate looks thr

Bug#552018: Upgrading to grave

2010-01-24 Thread Daniel Leidert
Am Sonntag, den 24.01.2010, 19:54 + schrieb brian m. carlson: > On Sun, Jan 24, 2010 at 03:01:35PM +0100, Torsten Werner wrote: > > On Sat, Jan 23, 2010 at 12:04 AM, brian m. carlson > > wrote: > > > Yes. Even if someone were to disagree that this bug is grave, at the > > > very least, this i

Bug#552018: Upgrading to grave

2010-01-24 Thread brian m. carlson
On Sun, Jan 24, 2010 at 03:01:35PM +0100, Torsten Werner wrote: > On Sat, Jan 23, 2010 at 12:04 AM, brian m. carlson > wrote: > > Yes.  Even if someone were to disagree that this bug is grave, at the > > very least, this is serious, since nobody can reasonably claim that the > > package in this st

Bug#552018: Upgrading to grave

2010-01-24 Thread Torsten Werner
severity 552018 important thanks On Sat, Jan 23, 2010 at 12:04 AM, brian m. carlson wrote: > Yes.  Even if someone were to disagree that this bug is grave, at the > very least, this is serious, since nobody can reasonably claim that the > package in this state is suitable for release. We have ha

Bug#552018: Upgrading to grave

2010-01-22 Thread brian m. carlson
On Fri, Jan 22, 2010 at 09:44:39PM +0100, Torsten Werner wrote: > brian m. carlson schrieb: > > I'm upgrading this bug report to grave, because I've done more tests > > and it seems that this bug causes the resolver to produce bizarre, > > inconsistent results and makes it unsuitable for a stable r

Bug#552018: Upgrading to grave

2010-01-22 Thread Torsten Werner
brian m. carlson schrieb: > I'm upgrading this bug report to grave, because I've done more tests > and it seems that this bug causes the resolver to produce bizarre, > inconsistent results and makes it unsuitable for a stable release. Grave means: makes the package in question unusable or mostly s

Bug#552018: Upgrading to grave

2009-12-23 Thread brian m. carlson
severity 552018 grave kthxbye I'm upgrading this bug report to grave, because I've done more tests and it seems that this bug causes the resolver to produce bizarre, inconsistent results and makes it unsuitable for a stable release. For example, no matter what order I put the delegateURI and dele