On Sat, Sep 17, 2016 at 12:36:01PM +0200, Bas Couwenberg wrote:
> On September 17, 2016 9:10:56 AM GMT+02:00, Mattia Rizzolo 
> <mat...@debian.org> wrote:
> >On Sun, Sep 11, 2016 at 11:08:03AM +0200, Sebastiaan Couwenberg wrote:
> >> On 09/11/2016 12:32 AM, Andreas Beckmann wrote:
> >> > Or is it possible to just not build libproj-java on kfreebsd*?
> >> > Removing proj from kfreebsd* would affect a lot of packages:
> >> 
> >> libproj-java doesn't have reverse dependencies are a very low popcon,
> >so
> >> dropping the package is an option. Now is not the time to do that
> >though.
> >
> >Why not?  Would you like/need a patch for it?
> Because we've just had a proj transition for which the last rdep only 
> migrated to testing today.

That's really totally irrelevant.
The package already migrated.  More: all rdeps migrated too.
that transition is done, and the package is just open for business as
There are no rdeps of libproj-java, so you wouldn't trig any transition
by removing the package, be it only in kfreebsd or everywhere.

> I don't like packaging differences between architectures, so I'm
> currently doubting whether to drop the Java package entirely or
> complicate matters by only removing it from the problematic
> architectures

I don't personally find such variation across architectures a
complication that needs to be taken into account as "excessive
Though if you would be just happy to drop the whole libproj-jave package
from everywhere, that would be just fine to me too.

                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reply via email to