rescuing cherrytree (it has been kicked from debian10)

Forum Forums antiX-development Development rescuing cherrytree (it has been kicked from debian10)

  • This topic has 3 replies, 2 voices, and was last updated Jul 3-7:49 am by Anonymous.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #24038
    Anonymous

      https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822586

      cherrytree: depends on python-gtksourceview2 which is deprecated

      upstream 0.38 version of cherrytree is GTK3
      (ongoing break/fix GTK3 nonsense, w/ currently 367 open issue tickets)

      I’m preserving the 0.37 branch (GTK2)

      This is v0.37.6-1.1, pulled from debian sid repo; tested built on antiX 17
      (uploaded debfile for testing. It is installable on both 32bit and 64bit systems)
      https://gitlab.com/skidoo/cherrytree

      https://gitlab.com/skidoo/python-gtksourceview2
      “python bindings for the version 2 of the GtkSourceView library”
      tested built on antiX 17; uploaded src + 64-bit debfile

      #24052
      Forum Admin
      anticapitalista
        Helpful
        Up
        0
        ::

        Thanks skidoo

        Philosophers have interpreted the world in many ways; the point is to change it.

        antiX with runit - leaner and meaner.

        #24126
        Forum Admin
        anticapitalista
          Helpful
          Up
          0
          ::

          We have an MX version of cherrytree (.38.5).
          Is that not working ok on stretch (antiX-17) and buster(antiX-19)?

          Philosophers have interpreted the world in many ways; the point is to change it.

          antiX with runit - leaner and meaner.

          #24127
          Anonymous
            Helpful
            Up
            0
            ::

            The v0.38.5 works, but it depends on GTK3 libraries.
            This forum topic can just serve as a reminder of the continued availability of the gtk2 version.

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.