sure, unless someone has an old program compiled against it. the new
library (or -text) has support files that should work with the old
library, they just have some new stuff in them (translations, new
strings, etc) so there's no compelling reason not to. On the other
hand, it doesn't seem to me
On Thu, Aug 14, 2008 at 10:11:17PM +0100, Barak A. Pearlmutter wrote:
> Actually replaces: would work too, and be a bit gentler.
> Feel free to NMU with that if you want; if you don't I'll get around
> to it sometime.
> (Since this is a etch->lenny upgrade stopper, I think something fixing
> the pr
Thanks.
Actually replaces: would work too, and be a bit gentler.
Feel free to NMU with that if you want; if you don't I'll get around
to it sometime.
(Since this is a etch->lenny upgrade stopper, I think something fixing
the problem has to be pushed through the freeze barrier.)
On Wed, Aug 13, 2008 at 05:18:29PM +0200, Marius Mikucionis wrote:
> I guess libdjvulibre-text should have a conflict with libdjvulibre15 the
> same way as djvulibre-desktop does.
Indeed. I added the conflicts and it now upgrades fine in an Etch
chroot.
NMU uploaded to delayed/2-days. Debdiff a
doh! I also bumped into this one on a more outdated machine.
interestingly, the other two (more up-to-date) ones did not show this
problem and upgrade silently succeeded.
I guess these packages were not designed to be upgraded in "one big hop"
skipping some intermediate versions.
I worked-around t
5 matches
Mail list logo
