unison 2.48

To which release????

Good point: 14.04.

LTS releases are rarely updated in favour of stability. If you report a bug and state the bug and security fixes are significant then the package will be updated sooner

Understood. The problem is not a bug, the problem is how unison works: you cannot connect to a computer with a different version of unison. If you realize that, keeping unison at an old release makes the it useless. Everyone else is moving up in version, while 14.04 LTS is not. This makes any computer with ubuntu LTS effectively excluded to use unison.

In fact, this is far worse that a bug/security fixes. At least there's a chance those will never happen. Unison's version will unavoidably go up, so your policy (which makes perfectly sense for any other piece of software) becomes intentionally counter-productive.

Then that is a bug. The program cannot do its job as it cannot connect to other clients as it is too far behind.

I don't believe the good people developing unison would call it a bug but I do agree it's a design flaw.

Back to my original question: when is it going to be packaged?

I am willing to help. This issue will probably reoccur, given the way unison is designed.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

well, well, are you a bunch of helpful people.

What do you expect? A definite date? Actionparsnip has already indicated that there have to be special reasons for updating a package in a LTS release.

You have to be aware that Ubuntu takes over most of its packages from Debian. And is you look at https://packages.debian.org/search?keywords=unison&searchon=names&suite=all&section=all you can see that also Debian is running 2.40 or even lower.

The recommended was is to ask Debian for an upgrade of their package, and Ubuntu will then follow.

If in your opinion the current Ubuntu package is unusable, please create a bug report to inform the developers of that problem.

> What do you expect? A definite date?

Yes, but not necessarily on the form of a date but something like 'in a few weeks'. I think this is clear from my original question.

> Actionparsnip has already indicated that there have to be special reasons for updating a package in a LTS release.

I replied to that, explaining those special reasons.

> If in your opinion the current Ubuntu package is unusable, please create a bug report to inform the developers of that problem.

It's not an opinion, nor it is a bug. If you read what I said, this is clear.

> The recommended was is to ask Debian for an upgrade of their package, and Ubuntu will then follow.

This is new information, thank you for that. Was that so hard?

>> What do you expect? A definite date?

>Yes, but not necessarily on the form of a date but something like 'in a few weeks'. I think this is clear from my original question.

Actionparsnip's first answer implicitly says: Never, unless there is a specific reason.

>> If in your opinion the current Ubuntu package is unusable, please create a bug report to inform the developers of that problem.

>It's not an opinion, nor it is a bug. If you read what I said, this is clear.

The bug reporting tool is used not only to report coding errors, but also for 'wishlist' type improvements etc.
If the version of unison in Ubuntu 12.04 cannot be used with unison's version normally installed in other operating systems, this is definitely worth being reported as bug.

> Actionparsnip's first answer implicitly says: Never, unless there is a specific reason.

There was a specific reason. It was dismissed by Actionparsnip as a bug, while that is not the case. He then proceeded to ignore this issue altogether, letting the question expire. Unless I'm mistaken, dismissive and inattentive answers pretty much go against the point of launchpad.

> If the version of unison in Ubuntu 12.04 cannot be used with unison's version normally installed in other operating systems, this is definitely worth being reported as bug.

New information again, thank you! That's what I call an answer.

All that information is already contained in actionparsnip's comment #4. Up to the moment that he gave his answer, there was no information given about a specific reason (namely the inoperability of different versions). He also advised to raise a bug report. So there is not much additional information in my comments compared to actionparsnip's (except mentioning Debian as additional player in the game).

You omit the following details:

- information was given about a specific reason and that was ignored by actionparsnip, letting the question expire;
- there is more additional information in your comments (in addition to mentioning Debian as additional player in the game), and that is that "The bug reporting tool is used not only to report coding errors, but also for 'wishlist' type improvements etc.".

These omissions are convenient to your argument, that being (to my understanding) that actionparsnip's handling of this question was adequate. Clearly it was not. The fact that you are excusing him indicates that it is preferable to you to excuse the ineptness of your colleague than conduct the purpose of launchpad. That in turn tell me that, probably, this whole set-up is pointless and unavoidably a dead end.

Oh I know, being unusable is never good enough reason for package upgrade and good occasion for another pointless discussion. Way to go devs. IT IS STILL NOT SOLVED.

Hello,
I have the same problem: I use Nas4Free to synchronize all my computers (and it worked flawlessly), it upgraded unison to 2.48 so my computers (all of them are ubuntu 14.10) can't sync anymore.

How is this "solved". I cannot find that definition in the Ubuntu Bug Status Wiki. Won't Fix would seem more appropriate.

https://wiki.ubuntu.com/Bugs/Bug%20statuses

This is also a problem for me as my Ubuntu laptop will no longer sync with my Arch Linux workstation.

Building Unision 2.48 on Utopic also did not work as OCaml on Ubuntu is also older version.

You are confusing the question and the problem.

The question "Any ideas when unison 2.48 is going to be added?" was answered (rather dismissively, but still answered). The answer is never unless a bug report is submitted.

sirmacik kindly took over that at: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1421184

Please subscribe to that bug to put pressure on this issue.

Thank you for clear up my confusion.

> Please subscribe to that bug to put pressure on this issue.

I've already done that. After failing in building Unison 2.48 on my own with Utopic; in frustration I copied by Arch Linuxj binaries over to my Ubuntu system. While I realize this is not an acceptable practice, it worked for me. The Arch Linux binaries ran in my Ubuntu Utopic x86_64 system.

You can find the binaries, icon, and unison.desktop file here (right hand side, "download from Mirror"):

x86_64
https://www.archlinux.org/packages/extra/x86_64/unison/

i686
https://www.archlinux.org/packages/extra/i686/unison/

Copy the binaries to your /usr/bin directory; the icon to /share/pixmaps, and the desktop file to /share/applications.

YMMV, for me, I am back up and running with Unison across different Linux platforms.

Excellent idea TK.
I used the Arch linux binaries you indicated on Ubuntu 14.10 and Unison works fine.

Thanks

I also came across this problem, Unison 2.48 has been in the Debian Sid (unstable) repo since August 2015, so I assume it will make it into the next Ubuntu release - 16.04 at this stage.