I seem to have tracked the problem down. libaccess-bridge-java is a
dependency of openjdk-6-jre, and that depends on default-jre |
openjdk-jre, so if openjdk-jre is removed, then default-jre is forcably
installed. Thus a circular dependency.
One can solve the problem by removing libaccess-bridge
On Sat, 13 Nov 2010 01:34:43 +0100, Julien Cristau wrote:
> > I would appreciate a ruling on whether this bug should be
> > release-critical for squeeze? Thank you very much for your time.
> >
> Regardless of anything else, I think you shouldn't be playing severity
> ping pong with package mainta
On Fri, Nov 12, 2010 at 7:34 PM, Julien Cristau wrote:
> Regardless of anything else, I think you shouldn't be playing severity
> ping pong with package maintainers.
Of course. This is why I am deferring to your sage wisdom.
I really do my best to avoid BTS ping pong, but when I'm presented
with
On Fri, Nov 12, 2010 at 19:19:08 -0500, Michael Gilbert wrote:
> openjdk has a bug that I personally consider serious [0], but the
> maintainer does not. We can't seem to reach a consensus,
> so I am requesting a release team determination.
>
> The problem is that once openjdk-6-jre and openjdk-
On Fri, Oct 22, 2010 at 12:31 AM, Michael Gilbert wrote:
> severity serious
> thanks
>
> On Thu, Oct 21, 2010 at 12:59 AM, Matthias Klose wrote:
>> even this scenario is not reproducible for me in a fresh sid chroot. No, the
>> question whether this is reproducible for other people or in a fresh ch
severity serious
thanks
On Thu, Oct 21, 2010 at 12:59 AM, Matthias Klose wrote:
> even this scenario is not reproducible for me in a fresh sid chroot. No, the
> question whether this is reproducible for other people or in a fresh chroot
> is not answered. The removal of these packages on the build
severity 600664 important
tag 600664 + moreinfo
thanks
On 21.10.2010 06:39, Michael Gilbert wrote:
severity 600664 serious
tag -moreinfo
it looks like you also need to have openjdk-6-jre installed to be ablo
to reproduce this. otherwise, removal works fine.
note that in this situation, openjdk
severity 600664 serious
tag -moreinfo
it looks like you also need to have openjdk-6-jre installed to be ablo
to reproduce this. otherwise, removal works fine.
note that in this situation, openjdk-6-jre is also unremovable. in
fact it *installs* packages given a removal command:
$ sudo apt-get p
severity 600664 important
tags 600664 + moreinfo help
thanks
unable to reproduce. is this repeatable by somebody else or in a fresh chroot?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: openjdk-6-jre-lib
Version: 6b18-1.8.2-1
Severity: serious
openjdk-6-jre-lib is currently not removeable on sid. this may be
because openjdk-6-jre-headless depends on openjdk-6-jre-lib
(>= ${source:Version} and openjdk-6-jre-lib depends on
openjdk-6-jre-headless (>= ${base:Version}). i g
10 matches
Mail list logo
