Long ago in a feat to never be replicated, I compiled ocaml and then unison for arm. (ipk ipkg type Funplug and Alt-F both use ) for my DNS-323 when it was 2.40. I packaged it as an ipkg. I loved it. Then 2.48
For awhile now I have just used rsync for transfers to my DNS. I still use unison 2.40 between discs on the DNS between hard drives. I am re-visiting how to get unison 2.40 to communicate with 2.48.
Has anyone had any luck making a flatpack of unison 2.40 for me to use in stable. Hopefully that would peacefully co-exist with 2.48 (I use 2.48 to sink with two netbooks that run Debian testing.
Previous
https://forums.bunsenlabs.org/viewtopic.php?id=1898 HOAS helped.
https://wiki.debian.org/SimpleBackportCreation
Yes, I know unison languishes in a semi vegetative state.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
unison 2.40 arm unison 2.48 stable
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: unison 2.40 arm unison 2.48 stable
You don't need to go to the trouble of making a flatpak — try running the old application from a jessie chroot (installed with debootstrap).paxmark1 wrote:making a flatpack of unison 2.40
EDIT: or use systemd-nspawn:
http://forums.debian.net/viewtopic.php?f=16&t=129390
^ That works for old stuff just as well as for new stuff
deadbang
Re: unison 2.40 arm unison 2.48 stable
a long time i used to have the problem that different unison versions don't tlak to each other.
for me the solution was to drop unison altogether.
i'd still need some sort of replacement for it, but then i'd always have to figure out what i want to sync where and what not...
and yes, i am taking backups, and i have a network drive, but unison was useful for usb drives mostly.
for me the solution was to drop unison altogether.
i'd still need some sort of replacement for it, but then i'd always have to figure out what i want to sync where and what not...
and yes, i am taking backups, and i have a network drive, but unison was useful for usb drives mostly.