Hi Gilles, > I can. Since I complain about Debian packagers, the best thing should > be I complain to myself. I don't know if there is a rule like > "an upstream developer must not package his own software".
No, there is not, but usually upstream debian/ directories are loosy and not well maintained, created with the intention of just build a ubuntu package quickly without any quality considerations. > I also need to learn a little about Debian packaging and be > accepted as packager. I know it isn't so easy. You can do, I am sure. > I use Debian but I don't use the imapsync package so I complain only > when I receive Debian bug reports or bugs relative to debian release. Yeah, this is the case for me too nowadays, from the lot of imap synchronization packages, nowadays I use offlineimap. There were not so many good quality imap solutions back then when I have uploaded the first imapsync to Debian. Actually I made at least two mail server migrations with it, but it was ages ago. > imapsync now support both 2.2.9 and 3.x Mail-IMAPCLient. > A good thing could be to automate the debian packaging > to stay up to date easily (one of the first thing I'll > do if I were a packager). Of course, if it were so easy, but there are always changes here and there in the upstream packages. For example imapsync had this 2.2.9 vs 3.0 bug for months, other packages have other issues. But basically you are right, I try to keep everything in git: http://git.debian.org/?p=collab-maint/imapsync.git;a=summary In an ideal update you only import the new upstream sources and GO! :) But the upstream sources has documentation which is not dfsg compliant (I think these are the RFCs in your case), users report bugs which you have to check and reproduce yourself in the old version to see if the new version fixes it. If not, you have to forward it to the upstream, etc. After that you do the upload, it breaks on 6/15 architectures, then you login to those machines, try to fix the issues, upload again, wait. And now you are happy, but there is already a new upstream version :) I am not complaining, of course these all are more or less interesting, I am just saying, that please do not think that all of this can be automated. Bots are not that good in communicating with users, fixing bugs and figuring out architecture dependent issues. > imapsync is free/open software, even if I ask to remove it you can keep it > in Debian or anywhere else, otherwise it wouldn't be free/open. > But I do appreciate you took care of my opinion. Then may I ask you to tell me what new version would you like to see in Debian? I will do the packaging. If you want to comment/patch on anything about it, please use the aformentioned git repository. Thanks, Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
