Deprecation warnings on Fedora Rawhide

Question

Deprecation warnings on Fedora Rawhide

quozl opened this issue 6 years ago · 12 comments

As of this date, Fedora Rawhide (experimental beta release) does log many deprecation warnings for Sugar Toolkit for GTK 3, some of which we have already fixed but not released, and some of which may yet need fixing. Suggested actions;

sort through and list the classes of warnings,
iterate through each class of warning and either fix it or confirm it has been fixed,
make pull request with commits for each class of warning.

Log file from Browse activity; 1668504-1534605.txt

Reference: unrelated problem https://bugzilla.redhat.com/show_bug.cgi?id=1668504

Answer 1 · 2019-02-14T02:29:02.000Z

Are there enough of these to be a GSoC project?

Answer 2 · 2019-02-14T02:43:11.000Z

I don't know. It seems to never end. https://github.com/orgs/sugarlabs/projects has some other bit rot type of tasking.

Answer 3 · 2019-02-14T04:02:40.000Z

As far as I know, Sugar stopped with Fedora 18. Current focus seems to be Ubuntu and Deb (for RPI). Why should we care what is done by Fedora rawhide? Tony

…

On 2/14/19 10:43 AM, James Cameron wrote: I don't know. It seems to never end. https://github.com/orgs/sugarlabs/projects has some other bit rot type of tasking. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAULkk89iQz8TjDr4mgW8UD0_np3Y10Qks5vNM0_gaJpZM4a6i0v>.

Answer 4 · 2019-02-14T04:14:30.000Z

This appears consistent with our obsession with the inconsequential. Many of our activities in ASLO are still not functional. The Bridge activity is now happily free of commas not followed by spaces. Sadly, it fails to start. Tony

…

On 2/14/19 10:29 AM, Walter Bender wrote: Are there enough of these to be a GSoC project? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAULkv9cc7UeFQjfKU1mmL8m4YSJB65Hks5vNMnugaJpZM4a6i0v>.

Answer 5 · 2019-02-14T04:26:13.000Z

Thanks. You ask why should we care? Because Fedora Rawhide becomes the next version of Sugar on a Stick, which is released by Fedora despite any new bugs that haven't been solved. Because what is in Fedora Rawhide that causes the bug may eventually appear in Debian and thus in Ubuntu. Fedora Rawhide is the canary in the coal mine.

That the next version of Sugar on a Stick may be affected also affects our recommended path for Raspberry Pi, which is SoaS. I've no focus on Ubuntu or Debian for Raspberry Pi, and I urge Raspberry Pi users to stick with SoaS for the best experience.

Some of these deprecations end up being important, but we can't tell yet. Many activities fail to start because of previous deprecations, and nobody cared. Why are you troubled that someone cares?

Answer 6 · 2019-02-14T05:58:35.000Z

As I am trying to make clear - it is incredibly frustrating to see this concern with triviata when major sugar activities do not function. I care because I am trying to enable Sugar to provide a meaningful educational experience for students in grades 4-6 who really could care less if an the python code for an activity satisfies flake but fails to start or (block party) doesn't have sound. Tony

…

On 2/14/19 12:26 PM, James Cameron wrote: Thanks. You ask why should we care? Because Fedora Rawhide becomes the next version of Sugar on a Stick, which is released by Fedora despite any new bugs that haven't been solved. Because what is in Fedora Rawhide that causes the bug may eventually appear in Debian and thus in Ubuntu. Fedora Rawhide is the canary in the coal mine. That the next version of Sugar on a Stick may be affected also affects our recommended path for Raspberry Pi, which is SoaS. I've no focus on Ubuntu or Debian for Raspberry Pi, and I urge Raspberry Pi users to stick with SoaS for the best experience. Some of these deprecations end up being important, but we can't tell yet. Many activities fail to start /because/ of previous deprecations, and nobody cared. Why are you troubled that someone cares? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAULktqGGAoXOFQDJDbdH1WCMKTOZaIvks5vNOVlgaJpZM4a6i0v>.

Answer 7 · 2019-02-14T06:38:00.000Z

Oh well, that's your lot then. For me, if someone draws to my attention a problem that can be fixed, and I don't want to fix it myself, I shall log it, as I have done here. I think this particular problem may eventually be important, and if someone who refuses to get involved in activity maintenance but nonetheless is happy to make trivial changes, I'm enabling their effort. Now, please stay out of this if it doesn't concern you, as your noise here degrades everybody's enthusiasm.

Answer 8 · 2019-02-14T08:14:12.000Z

This is clearly the easy course. Accept pull requests that put spaces after commas on an activity that fails to start. This problem is important to anyone who downloads the Bridge activity. I don't refuse to maintain activities, I do it and plan to continue doing it. I am frustrated by the lack of interest in the community and have no interest in jumping the 'pull request' hoops particularly after the 'gitorious' fiasco. Tony

…

On 2/14/19 2:38 PM, James Cameron wrote: Oh well, that's your lot then. For me, if someone draws to my attention a problem that can be fixed, and I don't want to fix it myself, I shall log it, as I have done here. I think this particular problem /may/ eventually be important, and if someone who /refuses/ to get involved in activity maintenance but /nonetheless/ is happy to make trivial changes, I'm enabling their effort. Now, please stay out of this if it doesn't concern you, as your noise here degrades everybody's enthusiasm. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAULklvAlq9eZeC3mSXD4lzXQ8bYDggNks5vNQRIgaJpZM4a6i0v>.

Answer 9 · 2019-02-14T21:41:51.000Z

I don't see your maintenance. Where are you publishing your changes?

Answer 10 · 2019-02-15T00:18:51.000Z

On the school server. Currently Browse-162.xo, Quiz-24.xo, Zim Desktop Wiki (gnome activity + Sugar launcher), GCompris (gnome activity + Sugar launcher), and helloworld-8.xo. I intend to try to identify and repair some of the broken activities in coming weeks to make them available via the school server to XO users. Tony

…

On 2/15/19 5:41 AM, James Cameron wrote: I don't see your maintenance. Where are you publishing your changes? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAULko8t26qImoyXXleEyCAGejbU_mqHks5vNdgggaJpZM4a6i0v>.

Answer 11 · 2019-02-15T03:09:28.000Z

I still don't see your maintenance. Please publish so other Sugar Labs members can see it. What you describe sounds like a hostile fork, where you have no intention of providing your changes to others or work with them. I'm fine with that, as the license allows it, but if you are going that way then you can't expect the rest of us to help you any further either.

Answer 12 · 2022-01-26T16:39:43.000Z

The classes that are deprecated are:
gdk_display_get_device_manager is deprecated
gdk_screen_make_display_name is deprecated
gdk_screen_get_number is deprecated
gdk_threads_enter is deprecated
gdk_threads_leave is deprecated
gdk_error_trap_pop is deprecated
gdk_error_trap_pop_ignored is deprecated
gdk_error_trap_push is deprecated
g_type_class_add_private is deprecated