FAQ

Differences between revisions 19 and 20
Revision 19 as of 2007-05-29 15:26:07
Size: 2743
Editor: i59F7041D
Comment:
Revision 20 as of 2007-06-03 13:50:10
Size: 3436
Editor: dialin106056
Comment: added XSBC-Original-Maintainer to the FAQ
Deletions are marked like this. Additions are marked like this.
Line 52: Line 52:
=== What does XSBC-Original-Maintainer mean? ===

If a package gets modified we change the Maintainer field in debian/control to point to the Ubuntu team responsible for the Ubuntu specific changes.
As we don't want to raise the impression that Ubuntu did the complete packaging we keep the original maintainer in a new field: XSBC-Original-Maintainer . This is a user-defined field (X) which should be included in the .dsc file (S; part of the source package), the binary debs (B) and the .changes file (C; generated during package building) and the field name is "Original-Maintainer".
The value of XSBC-Original-Maintainer is the value of the Maintainer field before it got changed.

Include(MOTUMenuHeader)

Frequently Asked Questions

The Archive

How do I get my changed package X into Universe/Multiverse?

Via the SponsorshipProcess

NOTE : If it's important enough to be shipped in the stable distro, read StableReleaseUpdates.

What Version Should my Package Have ? / Should My Package have -0ubuntu1 appended to the End of the Version Number ?

How can I make multi pbuilders ? / How can I make a pbuilder for ( Edgy / Dapper / Breezy / Debian SID ) ?

What options do I need for debuild to make a source package including tar.gz?

  • debuild -S -sa

Upstream already provided a debian-dir in the orig.tar.gz, what now?

  • Always ask upstream kindly to remove it.
  • At your option (if you need to remove a file from the upstream debian-dir you will need to remove the upstream debian-dir from orig.tar.gz):
    • Remove it from the tarball, renaming the tarball while doing so. Example: foo_0.2.orig.tar.gz would then be foo_0.2repacked1.orig.tar.gz.
    • Just modify the package as usual.

I need to fix a bug in the upstream provided source, modify the source or add a patch?

  • If the package already has a packaging system, make a patch and add it.
  • If the package does not have a packaging system and the patch is small, you can modify the source. It is an Ubuntu goal to keep diffs with Debian small and so if modifying the source makes a smaller diff than adding a patch system you should generally modify the source.
  • If your package uses cdbs, you ought to consider using simple-patchsys and use cdbs-edit-patch to make your patch in any case.
  • See https://wiki.ubuntu.com/MOTU/School/PatchingSources for more information on patching

I want to maintain a package

Here's what it means if a package has your name and mail address in the Maintainer: field in debian/control:

  • You will take care of the package's bugs. It makes sense if you are bug contact for that package in Launchpad.
  • You will liaise with upstream.
    • You track what's going on upstream.
    • You will try to build a good communication to the upstream developers.
  • You will find out how to fix bugs appropriately. Uploading new upstream versions is just not enough. (Think of fixes in stable releases.)

What does XSBC-Original-Maintainer mean?

If a package gets modified we change the Maintainer field in debian/control to point to the Ubuntu team responsible for the Ubuntu specific changes. As we don't want to raise the impression that Ubuntu did the complete packaging we keep the original maintainer in a new field: XSBC-Original-Maintainer . This is a user-defined field (X) which should be included in the .dsc file (S; part of the source package), the binary debs (B) and the .changes file (C; generated during package building) and the field name is "Original-Maintainer". The value of XSBC-Original-Maintainer is the value of the Maintainer field before it got changed.


Back to [:MOTU].BRBR [:CategoryMOTU]

MOTU/FAQ (last edited 2014-02-18 22:20:12 by kotux)