Bug#996569: getmail6 naming issues

2021-11-08 Thread Charles Cazabon
Sudip Mukherjee wrote: > > iiuc, getmail6 is not a "hostile fork". It is; I could explain it, but I already have. Quoting from the getmail documentation: Why do I say it's a "hostile" fork? Because I have communicated with the maintainer and indicated I would be thrilled to accept

Bug#996569: getmail6 naming issues

2021-11-08 Thread Sudip Mukherjee
On Sun, Nov 7, 2021 at 11:39 PM Charles Cazabon wrote: > > Sudip Mukherjee wrote: > > > > So, my preference is: > > 1. rename the package and executable. As I have pointed out, this is the > normal, polite, accepted best practice when forking a project. The fact that > Roland claims to have

Bug#996569: getmail6 naming issues

2021-11-07 Thread Charles Cazabon
Sudip Mukherjee wrote: > > 1) The Debian maintainers of getmail have offered to help with > supporting python3 and have even submitted patches or pointed to their > wip branches in github which I think were all rejected. I have not rejected anything. I have asked questions of people who

Bug#996569: getmail6 naming issues

2021-11-07 Thread Sudip Mukherjee
I have thought about it again while going through all the old mails of getmail mailing list and also https://bugs.debian.org/936604 and these are my thoughts: 1) The Debian maintainers of getmail have offered to help with supporting python3 and have even submitted patches or pointed to their wip

Bug#996569: getmail6 naming issues

2021-10-30 Thread Remco Rijnders
I'd like to strongly object to the removal of this package from Debian. As per the Debian social contract: "4. Our priorities are our users and free software. We will be guided by the needs of our users and the free software community. *We will place their interests first in our priorities*".

Bug#996569: getmail6 naming issues

2021-10-18 Thread Charles Cazabon
Hi, On Mon, 18 Oct 2021 12:09:56 +0100 Sudip Mukherjee wrote: > > I think I was not able to explain properly. Even if I rename or remove > the package now, it will only affect Debian unstable and testing > releases. It will not affect Debian Bullseye release. Surely such a change can be

Bug#996569: getmail6 naming issues

2021-10-18 Thread Sudip Mukherjee
On Sun, Oct 17, 2021 at 11:38 PM Charles Cazabon wrote: > > Hi, Sudip, > > Thanks for the response. > > > > On Fri, 15 Oct 2021 10:55:40 -0600 Charles Cazabon wrote: > > > > > > > > I would appreciate it if this package/project was renamed to something > > > > that does not contain the word

Bug#996569: getmail6 naming issues

2021-10-17 Thread Charles Cazabon
Hi, Sudip, Thanks for the response. > > On Fri, 15 Oct 2021 10:55:40 -0600 Charles Cazabon wrote: > > > > > > I would appreciate it if this package/project was renamed to something > > > that does not contain the word "getmail" or anything confusingly > > > similar. > > "getmail" and "getmail6"

Bug#996569: getmail6 naming issues

2021-10-17 Thread Sudip Mukherjee
Hi Charles, On Sat, Oct 16, 2021 at 8:33 PM Charles Cazabon wrote: > > On Fri, 15 Oct 2021 10:55:40 -0600 Charles Cazabon wrote: > > > > So: fork is fine. Imposing a large support burden on the original project > > is > > not. I would appreciate it if this package/project was renamed to

Bug#996569: getmail6 naming issues

2021-10-16 Thread Charles Cazabon
On Fri, 15 Oct 2021 10:55:40 -0600 Charles Cazabon wrote: > > So: fork is fine. Imposing a large support burden on the original project is > not. I would appreciate it if this package/project was renamed to something > that does not contain the word "getmail" or anything confusingly similar. I

Bug#996569: getmail6 naming issues

2021-10-15 Thread Charles Cazabon
Package: getmail6 Version: 6.14-1 Hi, I'm the original author of getmail, which was included in the Debian repositories for a long time (until you dropped most packages depending on Python 2). getmail6 is a fork of getmail. I'm fine with forking; I chose the GPLv2 for a reason. However, the