I can submit bug reports, include PR's in them, but I'm not sure how I would submit a PR for upstream changes as there are the extra changes required to be made to get the package working.Perhaps after some success in packaging and testing locally, I'll be able to submit those changes aswell.
The updates are made by the Packaging Team https://salsa.debian.org/groups/pkg-sugar-team/-/group_members On Saturday, July 11, 2020, 4:50:13 PM GMT+5:30, Chihurumnaya Ibiam <ibiamchihurumn...@gmail.com> wrote: I thought your project was supposed to be you doing downstream updates when needed. Who makes the updates? -- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com On Sat, Jul 11, 2020 at 12:03 PM Shaan Subbaiah B C <shaansubbaiah.c...@bmsce.ac.in> wrote: No I can't, I'm not part of Debian Sugar Maintainers team. On Sat, 11 Jul, 2020, 3:50 pm Chihurumnaya Ibiam, <ibiamchihurumn...@gmail.com> wrote: Can you make the necessary updates downstream? -- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com On Sat, Jul 11, 2020 at 9:42 AM shaansubbaiah.c...@bmsce.ac.in <shaansubbaiah.c...@bmsce.ac.in> wrote: Update, 1. sugar-record-activity is v102 in the Debian Archive, and is based on Python2. The latest release in the Sugar Labs GitHub Repo is v201, based on Python3. 2. Similarly, sugar-finance-activity is v12 in the Debian Archive, and is based on Python2. The latest release in the Sugar Labs GitHub Repo is v15, based on Python3. The upstream changes haven't been pulled in a while, not sure why. On Saturday, July 11, 2020, 1:49:29 PM GMT+5:30, shaansubbaiah.c...@bmsce.ac.in <shaansubbaiah.c...@bmsce.ac.in> wrote: Sure! I’ll look into the other activities and try to find out why they aren’t included. sugar-etoys-activity is part of the the [contrib] archives as it depends on etoys which is [non-free]. I should be able to install the package after enabling non-free packages in my sources.list. Regarding the other activities, I can try my hand at packaging the activities ported to Python3. On Saturday, July 11, 2020, 5:04:42 AM GMT+5:30, James Cameron <qu...@laptop.org> wrote: Thanks. Is there anything you can help with to get those three activities included? You might first find out why they are not part of the testing distribution, and see if you can improve the situation. Is there anything you can do to get other activities included? On Fri, Jul 10, 2020 at 12:58:49PM +0000, shaansubbaiah.c...@bmsce.ac.in wrote: > Hello all, > > I’ve listed the issues found in the Memorize activity. This was the last > activity that I could test on Debian Bullseye. > The remaining activities: sugar-record-activity, sugar-etoys-activity, > sugar-finance-activity from the [1]Sugar Debian Repository are not part of the > Debian Bullseye packages at the moment. > I will post what was tested and the issues found in all the activities on > Debian Bullseye soon. > > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ > > Sugar Memorise Activity v58 > > sudo apt install sugar-memorize-activity > > 1. On hovering over ‘grid size’ buttons, a warning is displayed: > > (sugar-activity3:1859): Gtk-WARNING **: 21:04:20.416: Drawing a gadget >with negative dimensions. > Did you forget to allocate a size? (node menuitem owner >SugarPaletteHeader) > > 2. Editing the game doesn’t work, the activity gets stuck [2]#29 > > 3. Activity saves its state to the Datastore but does not load it properly, a > fresh instance is started. Therefore, the user is unable to save their > progress and continue later. > > 4. The activity’s sounds and images (which are optional) depend on art4apps ( > [3]http://wiki.sugarlabs.org/go/Art4Apps), which is not installed by > default. Hence none of the sounds and words to generate cards dynamically > are included. The user is not notified of winning as there is neither text > displayed saying he/she has won nor the winning sound (win.wav from > art4apps) is played. > > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ > > This simple Multitail config for highlighting the logs that I’ve setup, may be > useful to others: > > # Paste the snippet into /etc/multitail.conf > # (or) save as .multitailrc in the home directory > > # Sugar > colorscheme:sugar > cs_re:green:DEBUG > cs_re:red:ERROR > cs_re_s:yellow:(Warning.*) > cs_re_s:blue:([0-9]{10,}\.[0-9]{6,}) > # > > Usage: multitail -CS sugar -iw "*YOUR_PACKAGE_NAME*" 1 -m 0 > eg. multitail -CS sugar -iw "*Memorize*" 1 -m 0 > > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ > > Best, > Shaan > > > > References: > > [1] https://salsa.debian.org/pkg-sugar-team > [2] https://github.com/sugarlabs/memorize-activity/issues/29 > [3] http://wiki.sugarlabs.org/go/Art4Apps -- James Cameron http://quozl.netrek.org/ _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
