On Sat, Oct 14, 2006, Peter Samuelson wrote:
> So, I've done that, but now I have second thoughts. libsvn-javahl is
> not in sarge, so this is only to support upgrading from old etch to new
> etch. Or from ubuntu dapper to etch. Is it really necessary to
> support that?
You have a point that i
[Loïc Minier]
> I propose you keep libsvn-javahl as a dummy package depending on
> libsvn-java until etch is released.
So, I've done that, but now I have second thoughts. libsvn-javahl is
not in sarge, so this is only to support upgrading from old etch to new
etch. Or from ubuntu dapper to et
[Loïc Minier]
> When upgrading a system with libsvn-javahl installed via aptitude from
> subversion 1.3.2-6, subversion, subversion-tools, libsvn0 are upgraded
> and libsvn-javahl is removed. libsvn-java is not selected.
>
> I propose you keep libsvn-javahl as a dummy package depending on
>
Package: libsvn-java
Version: 1.4.0-2
Severity: normal
Hi,
When upgrading a system with libsvn-javahl installed via aptitude from
subversion 1.3.2-6, subversion, subversion-tools, libsvn0 are upgraded
and libsvn-javahl is removed. libsvn-java is not selected.
I propose you keep libs
4 matches
Mail list logo