Bug#946046: unison-all should also depend on the old unison version, compatible with Debian 10

[Vincent Lefevre]

On 2019-12-03 14:39:47 +0100, Stéphane Glondu wrote:
> Le 03/12/2019 à 12:54, Vincent Lefevre a écrit :
> > BTW, I think that "unison" should just be a metapackage depending
> > on unison-debian, where  is the Debian version (with adapted
> > paths and executable names). That way, users could install both
> > Unison from stable and from testing/unstable (unison just depends
> > on libc6, so that this should be OK in practice).

Note: either unison-debian, or some other unison-, where 
would depend on the OCaml base-version used (hardcoded in the build
dependencies) and the version of the protocol used by unison (i.e.
the two possible causes of breakage).

The unison-debian is fine as long as testing/unstable machines
are upgraded at the same time, at least for the Unison packages,
which is not too much to ask for the users.

The unison- solution may be better in the future if the choice
of  is standardized across distributions and restricted to real
incompatibility changes, so that the user does not have to provide
a -servercmd option.

> I like this proposal...

> > This may make things easier for unison-all.
> 
> ...but I still see no future for unison-all, as it would need to depend
> on packages from stable and testing/unstable, wouldn't it?

Yes, this is what it would do. But after all, perhaps let the user
do things manually, because this is more complex: the user may also
need to install the oldstable version. In particular, this will be
needed when a new Debian/stable is released, as not all stable
machines are upgraded at the same time (in my lab, the admins wait
for several weeks, at least after the first Debian/stable update,
then some machines are upgraded so that they and users can test
them for regressions, then every machine is upgraded).

So I would suggest to drop unison-all, and rename unison to make
the current one co-installable with the one from Debian 10.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946046: unison-all should also depend on the old unison version, compatible with Debian 10

[Stéphane Glondu]

Le 03/12/2019 à 12:54, Vincent Lefevre a écrit :
> BTW, I think that "unison" should just be a metapackage depending
> on unison-debian, where  is the Debian version (with adapted
> paths and executable names). That way, users could install both
> Unison from stable and from testing/unstable (unison just depends
> on libc6, so that this should be OK in practice).

I like this proposal...

> This may make things easier for unison-all.

...but I still see no future for unison-all, as it would need to depend
on packages from stable and testing/unstable, wouldn't it?


Cheers,

-- 
Stéphane

Bug#946046: unison-all should also depend on the old unison version, compatible with Debian 10

[Stéphane Glondu]

Le 03/12/2019 à 12:27, Vincent Lefevre a écrit :
> The purpose of unison-all is the following (see the latest sentence
> in particular):
> [...]
>  Each of the supported versions uses a different protocol version;
>  installing this metapackage ensures the ability to synchronize with
>  old systems.
> 
> But it currently depends only on unison, which is no longer compatible
> with Debian 10 (buster), i.e. the current Debian/stable.

The transition to OCaml 4.02, the first one that revealed that Unison
was dependent on the version of OCaml used to compile it, also revealed
that providing such a compatibility package was not sustainable: it is
not possible to provide in bullseye a version of unison compatible with
the one in buster since they provide different versions of OCaml (and we
don't want to provide several versions of OCaml in the same release, not
just for unison). Maybe the best thing to do is to remove meta-unison
from Debian.

Depending on the old version is not possible, since it is meant to
disappear when unison migrates to testing.


Cheers,

-- 
Stéphane

Bug#946046: unison-all should also depend on the old unison version, compatible with Debian 10

[Vincent Lefevre]

On 2019-12-03 12:27:00 +0100, Vincent Lefevre wrote:
> The purpose of unison-all is the following (see the latest sentence
> in particular):
> 
> Description: file synchronization tool (all console versions)
>  This is a metapackage that depends on all supported console versions
>  of Unison, a file synchronization tool.
>  .
>  Each of the supported versions uses a different protocol version;
>  installing this metapackage ensures the ability to synchronize with
>  old systems.
> 
> But it currently depends only on unison, which is no longer compatible
> with Debian 10 (buster), i.e. the current Debian/stable.

Unfortunately, the old version I have on my machine is actually
older than buster and not installable in buster. Thus a compatible
version should be created first. Something like that was done in
the past.

BTW, I think that "unison" should just be a metapackage depending
on unison-debian, where  is the Debian version (with adapted
paths and executable names). That way, users could install both
Unison from stable and from testing/unstable (unison just depends
on libc6, so that this should be OK in practice). This may make
things easier for unison-all.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946046: unison-all should also depend on the old unison version, compatible with Debian 10

[Vincent Lefevre]

Package: unison-all
Version: 2.48+2
Severity: grave
Justification: renders package unusable

The purpose of unison-all is the following (see the latest sentence
in particular):

Description: file synchronization tool (all console versions)
 This is a metapackage that depends on all supported console versions
 of Unison, a file synchronization tool.
 .
 Each of the supported versions uses a different protocol version;
 installing this metapackage ensures the ability to synchronize with
 old systems.

But it currently depends only on unison, which is no longer compatible
with Debian 10 (buster), i.e. the current Debian/stable.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unison-all depends on:
ii  unison  2.48.4-1+b1

unison-all recommends no packages.

unison-all suggests no packages.

-- no debconf information