Hi together, sorry for the late reply, I wasn't subscribed to this RFH bug report (but I am now :-) and as it's not a bug report against the screen package but the wnpp pseudo package, I didn't receive your replies, just found them by accident yesterday (and Francesco pointed me to them today, too :-).
Francesco Apollonio wrote: > I'm interested to help the packaging of screen, if you still need help > please contact me. L. Alberto Giménez wrote: > I use this package quite often, but I haven't looked into the code > but if you still need help and Francesco's help is not enough, feel > free to contact me. Jeffrey Vandenborne wrote: > I'm very interested in contributing if you still need help so > contact me anytime if you like. Since it is not so obvious, here are some facts about the current state of the package: The package in Debian Experimental represents the current state. Please use that version when looking at code or trying to reproduce bugs. It uses the "3.0 (quilt)" source format and should be uptodate with regards to Standards-Version, etc. and also should have just minor Lintian warnings. See also my blog posting about it: http://noone.org/blog/English/Computer/Debian/Git%20Snapshot%20of%20GNU%20Screen%20in%20Debian%20Experimental.futile So please ignore what's currently in Debian Sid. :-) Unfortunately http://packages.qa.debian.org/s/screen.html shows mostly meta-information about the package in Sid, so most information there is outdated with regards to packaging. The only reason why I haven't uploaded the current package to Sid is http://bugs.debian.org/644788 -- but happily Upstream works on that issue already, see https://lists.gnu.org/archive/html/screen-devel/2012-02/msg00004.html :-) So for now we don't need to invest much time in writing DebConf templates informing the user about the incompibility and the possibility to use /tmp/screen-4.0.3-bin or so instead which would be copied there by the preinst script. (This kind of work may become important again if upstream doesn't manage to get 4.1.0 clients talk with 4.0.3 servers.) See http://anonscm.debian.org/gitweb/?p=collab-maint/screen.git for the current state of packaging and http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=screen;dist=experimental for the bugs which are still open in Debian Experimental. To stay uptodate what the others do with regards to bug reports, it's best to subscribe to screen's "package mailinglist" (i.e. receive all mails the package maintainer would receive, including bug report stuff) at the bottom of http://packages.qa.debian.org/s/screen.html With regards to what could be done to help screen in Debian (and to some degree also in downstream distributions like Ubuntu): * Some further bug triage would be good. - Checking if bugs open in Experimental are also still present in Experimental. I suspect that I still haven't found all of them. :-) - Checking if the attached patches from bugs still apply or maybe even already have been applied by Upstream. - Tagging bugs where appropriate, see http://www.debian.org/Bugs/Developer#tags for the available tags and their meaning. - Checking which bugs are (or should be) tagged "upstream" (but not fixed-upstream or fixed in Experimental :-), but are not listed on https://savannah.gnu.org/bugs/?group=screen (only 50 bugs per page, use the search function) -> Create a bug report in Upstream's bug tracker, refer to the Debian bug report in the report's text. -> Set the forwarded address of the Debian bug report to the URL of the Upstream bug report. * If you have some experience with C, check if there are bugs where you think you can write a fix for. * 4.1.0 doesn't seem to work properly on at least kfreebsd-i386 (but likely the same problem on kfreebsd-amd64) at a first glance. I though haven't investigated further yet and a bug report still has to be written. * If you have a Launchpad account another good thing would be to look through the bugs at https://bugs.launchpad.net/ubuntu/+source/screen and see which have corresponding bugs in Debian which are not yet linked in Launchpad and link them. - If the corresponding Debian bug report is fixed in Experimental, or the bug is not Ubuntu-specific and fixed by the version in Debian Experimental the bug report in Ubuntu can be put at least in the state fix-committed, maybe with a comment that it's fixed in Debian Experimental. I likely have forgotten something where help could be needed, too, so if you think that's the case, feel free to say so. :-) Thanks for your interest in helping with Debian's screen package! Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120207125413.gs25...@sym.noone.org
