Matthew Johnson schrieb: > Hi Matthias, > > Do you have any reason to believe that jarwrapper breaks fastjar? I have > no idea how it possibly could; the maintainer scripts just cass > update-binfmts, but the problem would seem to be: > > update-alternatives: error: alternative jar.1.gz can't be slave of jar: > it is a master alternative. > > All I have to do with fastjar is depend on it and call it. > > Don't forget that when you reassign I don't get the email unless you CC > me, I just see that a bug number has been assigned to my package. > > Looking at the bug report more closely, the root cause might actually > be something to do with: > > update-alternatives: warning: alternative /usr/lib/jdk1.1/bin/jar.1.gz > (part of link group jar.1.gz) doesn't exist. Removing from list of > alternatives. > > Could this be caused by a package not from the archive which was > installed in /usr/lib/jdk1.1 and has since been removed, but which left > alternatives around?
ok, I didn't see the jdk1.1 link. that maybe indeed the root cause. Then, maybe just close it? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
