FAQ
3436
Comment: added XSBC-Original-Maintainer to the FAQ
|
2830
Updated broken links for Packaging Guide and Documentation Resources.
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
[[Include(MOTUMenuHeader)]] | <<Include(MOTU/Headers/Menu)>> |
Line 5: | Line 5: |
Here is a list of questions that are frequently asked by new contributors on #ubuntu-motu and the ubuntu-motu mailing list. If you don't find an answer to your question here, please add it along with the answer when you find out. | |
Line 6: | Line 7: |
== The Archive == | '''This page contains MOTU specific frequently asked questions. Technical content that used to be on this page, has moved to [[UbuntuDevelopment/FAQ]], which is the general place for FAQ regarding Packaging and Ubuntu Development.''' |
Line 8: | Line 9: |
<<TableOfContents>> | |
Line 9: | Line 11: |
=== How do I get my changed package X into Universe/Multiverse? === | == What is MOTU and What does it do? == |
Line 11: | Line 13: |
Via the SponsorshipProcess | This is the team which takes care of universe and Multiverse and universe components in ubuntu |
Line 13: | Line 15: |
''NOTE : If it's important enough to be shipped in the stable distro, read StableReleaseUpdates.'' | == Starting Points == |
Line 15: | Line 17: |
Be sure to check out these pages as well: * [[UbuntuDevelopment]] * [[UbuntuDevelopment/FAQ]] * [[http://packaging.ubuntu.com/html/|Packaging Guide]] * [[http://packaging.ubuntu.com/html/#knowledge-base|Knowledge Base]] |
|
Line 16: | Line 23: |
=== What Version Should my Package Have ? / Should My Package have -0ubuntu1 appended to the End of the Version Number ? === | === I want to help out Ubuntu MOTU and learn packaging, where do I start? === |
Line 18: | Line 25: |
* Ubuntu and Debian have slightly different package versioning schemes, for an explanation see https://help.ubuntu.com/ubuntu/packagingguide/C/basic-scratch.html#id2577623 | Take a look at [[MOTU/Contributing|MOTU/Contributing]] and the more concise overview at [[MOTU/GettingStarted]]. |
Line 20: | Line 27: |
=== How can I make multi pbuilders ? / How can I make a pbuilder for ( Edgy / Dapper / Breezy / Debian SID ) ? === | === How do I get help and pointers around in Ubuntu Development processes? === |
Line 22: | Line 29: |
* You can Read about setting up pbuilder ( a system to easily build packages in a clean chroot environment ) at http://wiki.ubuntu.com/PbuilderHowto | There are many ways to get help and pointers in ubuntu development |
Line 24: | Line 31: |
=== What options do I need for debuild to make a source package including tar.gz? === | For pointers or a introduction into the process, Please get in touch with the DeveloperAdvisoryTeam in ubuntu. |
Line 26: | Line 33: |
* `debuild -S -sa` | Or if you want some human interaction in real time please catch us on ''#ubuntu-motu'' on ''irc.freenode.net'' |
Line 28: | Line 35: |
=== 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. |
There are a lot of sessions that go on on Ubuntu development in the UbuntuDeveloperWeek on ''#ubuntu-classroom'' |
Line 34: | Line 37: |
=== I need to fix a bug in the upstream provided source, modify the source or add a patch? === | Please feel free to pitch in for any of those sessions which interests you in the UbuntuDeveloperWeek series :) |
Line 36: | Line 39: |
* 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 |
=== Do I need to know a lot of programming languages to become a MOTU? === |
Line 41: | Line 41: |
Much more important than having a lot of progamming experience is * being a good team player * learning by reading documentation, trying things out and not being afraid to ask questions * being highly motivated * having a knack for trying to make things work * having some detective skills |
|
Line 42: | Line 48: |
=== I want to maintain a package === | == How MOTU works == |
Line 44: | Line 50: |
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.) |
There are different processes in ubuntu development such as [[https://wiki.ubuntu.com/UbuntuDevelopment/Merging|Merge]], StableReleaseUpdates, [[https://wiki.ubuntu.com/Bugs/HowToFix|Bug Fixing]] and so on |
Line 51: | Line 52: |
A good starting point would be: [[https://wiki.ubuntu.com/MOTU/GettingStarted|MOTU/GettingStarted]] | |
Line 52: | Line 54: |
=== What does XSBC-Original-Maintainer mean? === | === Who resolves conflict? Who can I talk to if I experience problems in the MOTU team? === |
Line 54: | Line 56: |
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(MOTU/Council/Disclaimer)>> Talk to one of the members of the [[DeveloperMembershipBoard]]. Part of their goal is to keep the atmosphere in the team productive and calm. |
Line 60: | Line 63: |
Back to '''[:MOTU]'''.[[BR]][[BR]] [:CategoryMOTU] |
Back to '''[[MOTU]]'''.<<BR>><<BR>> [[CategoryMOTU]] |
Frequently Asked Questions
Here is a list of questions that are frequently asked by new contributors on #ubuntu-motu and the ubuntu-motu mailing list. If you don't find an answer to your question here, please add it along with the answer when you find out.
This page contains MOTU specific frequently asked questions. Technical content that used to be on this page, has moved to UbuntuDevelopment/FAQ, which is the general place for FAQ regarding Packaging and Ubuntu Development.
Contents
What is MOTU and What does it do?
This is the team which takes care of universe and Multiverse and universe components in ubuntu
Starting Points
Be sure to check out these pages as well:
I want to help out Ubuntu MOTU and learn packaging, where do I start?
Take a look at MOTU/Contributing and the more concise overview at MOTU/GettingStarted.
How do I get help and pointers around in Ubuntu Development processes?
There are many ways to get help and pointers in ubuntu development
For pointers or a introduction into the process, Please get in touch with the DeveloperAdvisoryTeam in ubuntu.
Or if you want some human interaction in real time please catch us on #ubuntu-motu on irc.freenode.net
There are a lot of sessions that go on on Ubuntu development in the UbuntuDeveloperWeek on #ubuntu-classroom
Please feel free to pitch in for any of those sessions which interests you in the UbuntuDeveloperWeek series
Do I need to know a lot of programming languages to become a MOTU?
Much more important than having a lot of progamming experience is
- being a good team player
- learning by reading documentation, trying things out and not being afraid to ask questions
- being highly motivated
- having a knack for trying to make things work
- having some detective skills
How MOTU works
There are different processes in ubuntu development such as Merge, StableReleaseUpdates, Bug Fixing and so on
A good starting point would be: MOTU/GettingStarted
Who resolves conflict? Who can I talk to if I experience problems in the MOTU team?
The MOTU Council is not operative at the moment. All its responsibilities have been assumed by:
Talk to one of the members of the DeveloperMembershipBoard. Part of their goal is to keep the atmosphere in the team productive and calm.
Back to MOTU.
CategoryMOTU
MOTU/FAQ (last edited 2022-11-23 15:53:53 by tartley)