<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div>Hello all,<br><div>I have successfully got Sugar v117-2 working on Debian 10 Buster (Stable). Documented the steps I have followed if anyone is interested:</div><br>Install Debian 10 Buster on a VM<br>I used `debian-live-10.4.0-amd64-kde.iso` from https://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/<br><br>Add the Debian testing and unstable repositories to sources.list:<br><br>```<br># /etc/apt/sources.list<br><br>deb http://deb.debian.org/debian testing main contrib<br>deb-src http://deb.debian.org/debian testing main contrib<br><br>deb http://deb.debian.org/debian unstable main contrib<br>deb-src http://deb.debian.org/debian unstable main contrib<br>```<br><br>Set default package repository to stable<br>```<br># /etc/apt/apt.conf.d/my-default-release<br><br>APT::Default-Release "stable";<br>```<br><br>Install sucrose from the unstable repository using:<br>`sudo apt install sucrose/unstable`<br><br>By default, a lot of dependencies aren't satisfied as sucrose will depend on the sugar v117 packages from unstable. Quick way of installing them from unstable is running:<br>```<br>apt install {sugar{-session,-chat-activity,-browse-activity,-read-activity,-calculate-activity,-log-activity,-write-activity,-terminal-activity,-pippy-activity,-imageviewer-activity,-jukebox-activity,-themes},python3{,-cairo,-gi,-gi-cairo,-sugar3,-jarabe,-pygame,-xapian,-gst-1.0},gvfs,ethtool,telepathy-gabble,libgnutls30,libtasn1-6,libmount1,libmount-dev,libglib2.0-dev}/unstable<br>```<br><br>After install, log out and login to Sugar.<br><br>-------------------------------<br><br><div>I haven't tested it in depth yet, but all the activities open, general functions work.</div><div><br></div><div>Unfortunately right after setting it up Sugar 117-3 got accepted into unstable.</div><div><br></div>I'm sure a few of the packages in the installation command above can be avoided. I have created snapshots prior to the install, I'll test further and update.<br><br>Aside, this message is pretty long and I'm assuming future mails will be too. I have found browser extensions that will render markdown as HTML for mail but it might look broken in the Sugar-Devel archive. Shall I send these mails as plaintext next time or is there some other alternative the community uses? <br></div><div dir="ltr" data-setdir="false"><br></div></div></body></html>