Hello,


I'm working on the "Gjiten" package ([1]). It was kind of abandoned and used Gtk2.
I upgraded it to Gtk3 and did some further development on it (see [2]).

I'd like to get the new codebase into the debian repos. If I understand correctly, I need a sponsor for that(?) Is there anyone willing to sponsor the package?


References
-------------

[1] GJiten on debian https://packages.debian.org/search?searchon=names&keywords=gjiten


[2] GJiten version 3.1
https://github.com/DarkTrick/gjiten/tree/gjiten-3.1


-- Chris

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, Oct 5, 2021 at 7:06 AM notebook wrote:

I'm working on the "Gjiten" package ([1]). It was kind of abandoned and used Gtk2.
I upgraded it to Gtk3 and did some further development on it (see [2]).

I'd like to get the new codebase into the debian repos. If I understand correctly, I need a sponsor for that(?) Is there anyone willing to sponsor the package?

Is there is a particular reason you used the Debian tarballs instead
of the old upstream CVS repository when creating the new upstream git repository? I'd suggest creating a new git upstream repository based
on the old upstream CVS repository and then rebasing your new changes
on top of that. Otherwise you are hiding the history of the project.

I note that the person in the Debian package Uploaders field is a
Debian member and was last active in Debian in March 2021, so I
suggest asking them about the situation, they are likely to respond.

Also ask them if they still have access to the SourceForge project and
could setup a redirect to your fork of the upstream project.

--
bye,
pabs

https://wiki.debian.org/PaulWise

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thank you for the lot of input!
(I wish I had it a year ago when I started developing.).

Is there is a particular reason you used the Debian tarballs instead
of the old upstream CVS repository when creating the new upstream git repository?

When I asked for the package source back then, I was referred only to the debian tarball. I.e. I was not aware of anything else existing.

I'd suggest creating a new git upstream repository based
on the old upstream CVS repository and then rebasing your new changes
on top of that. Otherwise you are hiding the history of the project.

As my changes are huge and the project has previously been basically dead, I think it's not worth the effort vs the risk and work effort.

I note that the person in the Debian package Uploaders field is a
Debian member

I guess you're talking about Ludovic Drolez <[email protected]>. I contacted him 8 months ago without any answer. I infered the mail is dead or he's too busy with other stuff. But perhaps from member to member there's a higher success rate :)

Also ask them if they still have access to the SourceForge project and
could setup a redirect to your fork of the upstream project.

I thought, if all links in the package point to github in the future, the source forge project becomes obsolete.


-- Chris


On 2021/10/06 11:52, Paul Wise wrote:

On Tue, Oct 5, 2021 at 7:06 AM notebook wrote:

I'm working on the "Gjiten" package ([1]). It was kind of abandoned and used Gtk2.
I upgraded it to Gtk3 and did some further development on it (see [2]).

I'd like to get the new codebase into the debian repos. If I understand correctly, I need a sponsor for that(?) Is there anyone willing to sponsor the package?

Is there is a particular reason you used the Debian tarballs instead
of the old upstream CVS repository when creating the new upstream git repository? I'd suggest creating a new git upstream repository based
on the old upstream CVS repository and then rebasing your new changes
on top of that. Otherwise you are hiding the history of the project.

I note that the person in the Debian package Uploaders field is a
Debian member and was last active in Debian in March 2021, so I
suggest asking them about the situation, they are likely to respond.

Also ask them if they still have access to the SourceForge project and
could setup a redirect to your fork of the upstream project.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 2021-10-06 at 13:50 +0900, notebook wrote:

When I asked for the package source back then, I was referred only to
the debian tarball. I.e. I was not aware of anything else existing.

The package source and the upstream source are two different things.
When creating a fork of an existing upstream project you should use the
source of the existing upstream project.

As my changes are huge and the project has previously been basically
dead, I think it's not worth the effort vs the risk and work effort.

There should be almost zero risk since the tarballs are likely
identical to the source in CVS. The effort is likely not much, just
converting the repo and then exporting and applying all the patches you created. It is also inappropriate to erase the contributions and names
of the previous upstream contributors from the git history.

I guess you're talking about Ludovic Drolez <[email protected]>. I
contacted him 8 months ago without any answer. I infered the mail is
dead or he's too busy with other stuff. But perhaps from member to
member there's a higher success rate :)

Hmm, OK. Maybe try him again.

I thought, if all links in the package point to github in the future,
the source forge project becomes obsolete.

For Debian purposes yes, but Debian is not the entire Free Software
world. Individual users and other redistributors will probably continue
to encounter the SourceForge project until someone makes it redirect to
your fork of the project. Personally when a project is undermaintained
I contribute to and or take over the project instead of forking because
it maintains the continuity of the one project in one place instead of proliferating copies of it many different places.

https://repology.org/project/gjiten/packages

--
bye,
pabs

https://wiki.debian.org/PaulWise

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmFdOY0ACgkQMRa6Xp/6 aaMy5Q/+MgjNm4zfxsoVe5/uVrggxIr9O0o0YZDZWcO6caGq/57ce67I59u+fjGr CeHpl+LBNJ81N1tYbkOq0GmKDKlRpfGWsezBdu6uxBwTIQgmgRv0wTie7wAKyD8o ffRUUxT6H0oqB78/BNwFrjuEpCHjEhW5v1o/pn9SmnKIjUU+HdZfZFltWekmKICd v1l9aN2vqmL1EHZV91Hu5Oa5qkvocrfKFXFE9d2tfBmN1WwI8YRYM7/DaVCtX2Qe MRAIX+lpzLTAQNb6nx7ivwUxsFgo4lV5Lm7yyNjnpGCHleWEqsw2opWJUkE01YhL pUNz6Uu/+09Nzx+NRYjt5kttl5WKNrU5rA45aWaXZs96PqajDBKK/jMXVw+m6kSU tTbsCmR6viKqmQ/A0egbrTo3f5klBeOB528hYR8VtSjrUkOb4YNDO8R1Mx3qsBr7 v4hm5yknGgBZwRg5RxyikPi3u/1dJzk3altnjjkl9Q/EbWl8OzjoKYAn5KJKBdwc Nnx+w/9yAkyw351NAPVk0j8YqHKR5x+tFsgdC0MkRnx/NrRvW+seI2OMv4NskTn1 ZvMpJ+tO0uEa/difrDAwETBoZnO1IfrWZwa6Bj8GvL2jI6I44q0RMCMMgqXYlTkM BM21b1IDmEGg5olzqVi0HWgs8X9Cfbx1wdZpZpytL4qOvo5lIWk=
=sQpZ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)