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

Bug#654116: Would love to help screen also!



Hi Sean,

Sean DuBois wrote:
> Hi I am new to Debian, but I am looking for a way to start out and
> learn the ropes.

Then welcome! Feel free to ask me questions by personal mail. Or on
IRC. Beyond other networks (Freenode, IRCNet, etc.), I'm on
irc.debian.org (aka OFTC) as XTaran.

> I am a C developer so I may be able to help with some patching.

Great. Because that's not my strength. :-)

> I am going to look through the instructions Axel sent out and
> try to get my feet wet.

A current itch where some more C knowledge would be of help is that
the patch from http://bugs.debian.org/600246 introduces a regression
as reported at http://bugs.debian.org/677512 -- I currently have no
idea how to change the patch in bug #600246 so that the regression
doesn't show up.

The currently most annoying issue is still
http://bugs.debian.org/644788 despite it's marked as solved in the bug
tracking system -- because it's just "solved" by informing the user
about the issue. Screen 4.1.0 and 4.0.3 speak a different protocol
version and the handshake between a 4.1.0 client and 4.0.3 seems to
end in a deadlock. Definitely non-trivial. Any patch for that will
likely be accepted upstream and cause the release of the first 4.1.0
beta release. ;-)

With regards to http://bugs.debian.org/677227 -- There's no need to
have deeper look at this. It's already solved in my head. Just needs
to written down and uploaded. Will fix it latest this weekend, likely
earlier. It's mostly a kfreebsd specific addition to the packaging.
:-)

> Is there anything Debian related I should be
> getting? As far as I am aware you really don't need to even worry about
> any accounts until you have been around for 6 months?

With git stuff contributing seems even easier. You pull from the
debian repo, commit locally, push your changes somewhere else
(gitorious, github, your own git server, etc.) and someone with write
access to the official packaging git repo can pull it from your repo
and push the changes to the official one.

How to start playing around with the source package:

Install build-essential, git, pristine-tar, quilt, lintian and
devscripts.

Clone the git repo at
http://anonscm.debian.org/gitweb/?p=collab-maint/screen.git

Make sure you also get the upstream and pristine-tar branches.

Have a look at how to use pristine-tar to extract the .orig.tar.gz
(something like "pristine-tar checkout
../screen_4.1.0~20120320gitdb59704.orig.tar.gz" inside the git
repository)

Use "quilt push -a" and "quilt pop -a" to apply and
unapply all patches in debian/patches/. Use the same commands without
"-a" for single step patch (un)applying.

If you want to change a patch, make it the topmost patch. If you want
to make the patch change a file it already modifies, edit that file
and run "quilt refresh" to refresh that patch. To add new files to a
patch (before editing them!) use "quilt add".

Use e.g. "debuild -uc -us" to build both, source and binary packages,
use "debuild -uc -us -b" to build only the binary package (i.e. to
just test if some patch does the right thing).

I think those commands should suffice to get the feets wet with the
package. :-)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@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



Reply to: