2014-04-10 0:30 GMT+02:00 Diane Trout <di...@ghic.org>: > That was my mistake. I wonder why I didn't find the java team package? > > Is there a way to retract my package in favor of the java teams? > Hi, I packaged it for Java team because it was (is) a Java library but I made it on behalf of the DebianMed team... ;-)
I have seen this duplication yesterday. You packaged latest libcofoja version and it replaced mine, that's fine for me, and if everyone agree, let's remove cofoja in favor of libcofoja-java as it is a matter of source package only, binary package is the same (but version) and as such will not impact dependent packages. Olivier > > Diane > > On Thursday, April 10, 2014 00:13:49 Emmanuel Bourg wrote: > > Hi all, > > > > I just noticed that cofoja has been packaged twice. There are two source > > packages, cofoja [1] and libcofoja-java [2], that both create a > > libcofoja-java binary package. > > > > - cofoja has been packaged last year by Olivier Sallou for the Debian > > Java Team > > - libcofoja-java has been packaged last month by Diane Trout and Andreas > > Tille for the Debian Med Team > > > > What is the proper way to resolve this conflict? > > > > Emmanuel Bourg > > > > [1] http://packages.qa.debian.org/c/cofoja.html > > [2] http://packages.qa.debian.org/libc/libcofoja-java.html > > -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
