[Sugar-devel] Debian Advocacy for Sugar - Update - 02-June-2020

[James Cameron]

Thanks Shaan.

That's a good test outcome.

Try changing default release to unstable in order to simplify the install step.

Avoid or reduce the testing 117-3 if you can assess the change as not requiring a complete test.  Look at the commits to the Debian package repository to make that assessment, and write down your reasons for next report.

How to communicate is your decision, but if it were me I'd use GitHub markdown in .md files in a project repository (sugar-labs-gsoc-2020-debian-advocacy), and use the `discount` package on Debian or Ubuntu to convert to HTML for mailing, then I'd use `mutt` to send the mail with appropriate MIME type.  For me, my inbound HTML mail is converted to text using `w3m` by `mutt`, so my preference is plain text or markdown.

On Tue, Jun 02, 2020 at 01:16:26PM +0000, shaansubbaiah.cs18 at bmsce.ac.in wrote:
> Hello all,
> I have successfully got Sugar v117-2 working on Debian 10 Buster (Stable).
> Documented the steps I have followed if anyone is interested:
> 
> Install Debian 10 Buster on a VM
> I used `debian-live-10.4.0-amd64-kde.iso` from https://cdimage.debian.org/
> debian-cd/current-live/amd64/bt-hybrid/
> 
> Add the Debian testing and unstable repositories to sources.list:
> 
> ```
> # /etc/apt/sources.list
> 
> deb http://deb.debian.org/debian testing main contrib
> deb-src http://deb.debian.org/debian testing main contrib
> 
> deb http://deb.debian.org/debian unstable main contrib
> deb-src http://deb.debian.org/debian unstable main contrib
> ```
> 
> Set default package repository to stable
> ```
> # /etc/apt/apt.conf.d/my-default-release
> 
> APT::Default-Release "stable";
> ```
> 
> Install sucrose from the unstable repository  using:
> `sudo apt install sucrose/unstable`
> 
> 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:
> ```
> 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
> ```
> 
> After install, log out and login to Sugar.
> 
> -------------------------------
> 
> I haven't tested it in depth yet, but all the activities open, general
> functions work.
> 
> Unfortunately right after setting it up Sugar 117-3 got accepted into unstable.
> 
> 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.
> 
> 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?
> 

-- 
James Cameron
http://quozl.netrek.org/