Differences between revisions 18 and 19
⇤ ← Revision 18 as of 2008-04-10 17:42:56 →
Size: 5104
Editor: SandroTosi
Comment:
← Revision 19 as of 2009-03-16 03:33:54 → ⇥
Size: 5104
Editor: anonymous
Comment: converted to 1.6 markup
No differences found!
  • debcheckout - checkout the development repository of a Debian package
    • useful to download a package from Vcs-* field on debian/control file
  • {{{who-uploads gpe-gallery

Uploads for gpe-gallery: 0.97-3 to unstable: Neil Williams (Debian) <codehelp@debian.org> 0.97-2 to unstable: Neil Williams (Debian) <codehelp@debian.org> 0.97-1 to unstable: Neil Williams (Debian) <codehelp@debian.org>}}}

  • diffstat
    • to check .diff.gz for deb pkgs?
  • {{{$ grep-available -F Depends 'python-central' -a -F Architecture 'all' -s Package

Package: python-sqlobject Package: bzr Package: python-pexpect Package: python-serial Package: reportbug Package: python-optcomplete Package: python-setuptools Package: python-formencode}}}

  • {{{Executing 'grep-excuses <pkg>' will tell you why <pkg> has not

transitioned to testing yet. This can be helpful to fix any issues which are blocking the transition or to know if it's wise to upload a new version of a package or not. Note that interrupting mass transitions by uploading a new version of a package in the middle of a current transition is not really appreciated.}}}

  • licensecheck 
    • You need to complete the debian/copyright a little more as it does
not even reference GPL v2, which it is. See the package tnef for an
example. A good habit is to run

   licensecheck -r .

from the working directory on every package you work on.

A bit picky on my part, but remove the:

## All lines beginning with `## DP:' are a description of the patch.

line in debian/patches/*.dpatch files. It just takes up space. You
might also consider slightly more verbose descriptions in each patch
just to make it easier on yourself (or the next maintainer) a few
years from now. Also, make sure to pass on the patches to upstream.

----------

A useful tool in this situation is 'licencecheck -r .' - part of the
devscripts package.
  • debcheck

  • {{{> Many Debian packages aren't designed to support cross-compilation.

> Currently the only way to reliably build for multiple architectures is > to build on multiple architectures.

I just found a "qemubuilder" packages, from the same author as pbuilder and cowbuilder and can build packages for different platforms using qemu. That's awesome.

> Try using DEBOOTSTRAP=debootstrap in your .pbuilderrc. [Though it > seems to be a bug in cdebootstrap; probably #448210 or similar.]

Le Fri, Dec 21, 2007 at 12:51:31PM +0100, Luca Bruno a écrit : > That is probably bug #448210. Try using plain debootstrap insted of > cdebootstrap.

Le Fri, Dec 21, 2007 at 11:55:15AM -0430, Jose Luis Rivas Contreras a écrit : > It's a but in cdebootstrap but the patch had worked for me very well.

Thanks everybody for your answers, I used debootstrap instead of cdebootstrap and it worked well.}}}

dealing with inactive and/or unreachable maintainers

misc