Dear Maintainer,

Thank you for continuing to maintain the Debian gedit-source-code-
browser-plugin:

As you may be aware there has been no activity in more than a decade
upstream. Bit rot is making the plugin no longer usable with recent
versions of GEdit.

There is a fork that is maintained by ildar below:

https://github.com/ildar/gedit-source-code-browser

Unfortunately I am advised by the maintainer that it too is currently
no longer compatible with the latest GEdit. 

https://github.com/MicahCarrick/gedit-source-code-browser/issues/40#issuecomment-1909725836

I have asked ildar if he intends to continue maintaining it. If he
does, then you you might want to consider switching from the old
upstream to ildar's release.

Dear Kip,

thanks for your mail and references. I have asked ildar, in the bug you
referred to, additional details on what broke in the last Gedit
versions. If anybody is able to fix his fork, or produce another one
and make some minimal commitment to update it (or accept contributions
for it) over time, I will be happy to switch the Debian package to it.

The best thing would clearly be having an up to date fork owned by a
project, rather than an individual who (legitimately) writes "I
personally don't plan to maintain this regularly". I would be happy to
be in such a project and occasionally contribute - while I would not
want to simply package my personal fork.

Pietro

Dear Kip,

thanks for your mail and references. I have asked ildar, in the bug you
referred to, additional details on what broke in the last Gedit
versions. If anybody is able to fix his fork, or produce another one
and make some minimal commitment to update it (or accept contributions
for it) over time, I will be happy to switch the Debian package to it.

The best thing would clearly be having an up to date fork owned by a
project, rather than an individual who (legitimately) writes "I
personally don't plan to maintain this regularly". I would be happy to
be in such a project and occasionally contribute - while I would not
want to simply package my personal fork.

Pietro

Thanks Pietro. It might well be that it's only a few trivial lines of a
patch to get it working again with the latest GEdit. I don't know
though because it's not an area I'm familiar with. I just know that his
last fix kept it alive for a while.

Thanks Pietro. It might well be that it's only a few trivial lines of a
patch to get it working again with the latest GEdit. I don't know
though because it's not an area I'm familiar with. I just know that his
last fix kept it alive for a while.

This shows the python exceptions:
I did a couple of steps with it and found it's no more one line fix,
unfortunately.

Il giorno sab, 27/01/2024 alle 13.55 +0600, Ildar Mulyukov ha scritto:

I'm still using Gedit 44, I will try to investigate as soon as I have a
46 to test.

Pietro

Hey Pietro,

Following up to see if there's been any new developments on getting the
plugin working with Gedit 46.

Hello Pietro,

I have some good news for you. It was brought to my attention today by
Ildar that heguangyu5 has created a successful upstream fix for gedit-
source-code-browser-plugin. I tested just now with Gedit 46.2 on Ubuntu
Noble and it works fine.

All I needed to do was take the current packaging, bump the package
version in d/changelog, and remove all of the old patches except 0001-
Retrieve-data-in-the-right-folder.patch from d/patches/series. The then
package built without any quilt errors and installed cleanly.

Yours truly,

It would probably help if I provided the upstream link!

https://github.com/heguangyu5/gedit-source-code-browser/

Wonderful news, thanks Kip!

What if I created a new Github (or gitlab.gnome.org?) project with
heguangyu5's fork and the three of us as maintainers? This would likely
reduce the chances that Debian's upstream dies again, and possibly push
other people to contribute future fixes...

If we want to do this I would also:
- propose heguangyu5 to join us
- contact MicahCarrick and ask if he'd rather just transfer his project
to us, to simplify the work also of other distributions

Pietro

Yes, I think that's a good idea. I'm fine being a contributor, although
I imagine our first focus should be on just getting it repaired and
packaged first before adding new features.

I think it's also a good idea if you ask them to join too, as proposed,
so that we can consolidate everyone's efforts on a single fork, ideally
remove the other ones that are abandoned, and everything is in a single
canonical location.