Re: Versioned Dependencies (Was: Re: libjgrapht0.6-java_0.6.0-7_amd64.changes is NEWW)

2009-09-16 Thread Onkar Shinde
On Wed, Sep 16, 2009 at 10:07 AM, Paul Wise p...@debian.org wrote: On Tue, Sep 15, 2009 at 11:09 PM, Torsten Werner twer...@debian.org wrote: 2. You cannot binNMU an Architecture: all package but java packages are usually of Architecture: all. That may change at some point, there have been

Re: Versioned Dependencies (Was: Re: libjgrapht0.6-java_0.6.0-7_amd64.changes is NEWW)

2009-09-16 Thread Michael Koch
On Wed, Sep 16, 2009 at 02:43:48PM +0530, Onkar Shinde wrote: On Wed, Sep 16, 2009 at 2:05 PM, Michael Koch konque...@gmx.de wrote: On Wed, Sep 16, 2009 at 01:59:56PM +0530, Onkar Shinde wrote: On Wed, Sep 16, 2009 at 10:07 AM, Paul Wise p...@debian.org wrote: On Tue, Sep 15, 2009 at 11:09

Re: Versioned Dependencies (Was: Re: libjgrapht0.6-java_0.6.0-7_amd64.changes is NEWW)

2009-09-15 Thread Paul Wise
On Tue, Sep 15, 2009 at 11:09 PM, Torsten Werner twer...@debian.org wrote: 2. You cannot binNMU an Architecture: all package but java packages are usually of Architecture: all. That may change at some point, there have been rumblings about throwing away maintainer-built packages (but still

Versioned Dependencies (Was: Re: libjgrapht0.6-java_0.6.0-7_amd64.changes is NEWW)

2009-09-02 Thread Matthew Johnson
On Wed Sep 02 08:46, Michael Koch wrote: IMO a possible solution would be to have two (or more) packages and let other packages using jgrapht (Build-)Depend on the version they need. E.g. libjgrapht-java could always be the latest API and libjgrapht0.6-java is an older API which some apps