[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: WNPP Update Package source of gjiten



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 <ldrolez@debian.org>. 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.



Reply to: