BugFixingInitiative
8192
Comment:
|
8667
|
Deletions are marked like this. | Additions are marked like this. |
Line 70: | Line 70: |
=== No ${misc:Depends} === http://lintian.ubuntuwire.org/quantal/tags/debhelper-but-no-misc-depends.html lists a lot of packages which use debhelper, but don't have ${misc:Depends} specified in their Depends: line. If you decide to pick any of the list, please also check if the package is in Debian as well. http://packages.debian.org can be used for this. If the package exists in Debian as well, please consider [[Debian/Bugs|sending the patch to Debian first]]. |
Getting Started |
Bug fixing initiatives
We plan to have regular bug fixing initiatives, which should be particularly interesting for new contributors.
Instructions
If you are interested in helping out, you might want to
- read these articles first:
Our development guide has much more interesting information as well.
join us in #ubuntu-motu on IRC
Please: If you decide to work on fixing the issues pointed out below, please make sure you add your Launchpad ID next to them, ie:
- fix bug 12345
turns into
- fix bug 12345 (dholbach)
Have a great time and be sure to ask questions if you have any.
New contributors
Invalid brace expansions in Debhelper config files
Some config files in these packages use {foo,bar} constructs which should be eliminated. They should be either replaced by an explicit list of files, or use one of the features mentioned in the page linked below.
http://lintian.ubuntuwire.org/quantal/tags/brace-expansion-in-debhelper-config-file.html
- Make sure to forward your changes back to Debian if the problem appears there.
- You can use debdiff on _amd64 or _i386 .changes files to make sure that your modification was correct. Just check that the file lists are identical before and after.
Spelling errors
Here are a few packages which have spelling errors in their package description. An easy way to fix them is:
run bzr branch ubuntu:<packagename>
edit the debian/control file
- fix the spelling mistake
run dch -i to document the change you did
- For the ones specifically mentioned below:
run debcommit
run bzr push lp:~<your LP ID>/ubuntu/quantal/<source package>/typo-fix
run bzr lp-propose
This time around we will try to fix the following issues:
- linux-tools-3.4.0-3 (dependant dependent)
- happycoders-libdbg-dev (This packages These packages)
- qgfe (allows to allows one to)
- kdevelop-custom-buildsystem (arbitary arbitrary, allows to allows one to)
- gambas2-gb-crypt (allows to allows one to)
There are obviously more packages to be fixed, but as they are also in Debian, we'd prefer to get them fixed in Debian, so you might want to take these steps as well:
run bzr bd -- -S
run submittodebian to submit your changes to Debian
Adding Debtags
Quoting an introduction about Debtags by Enrico Zini:
- The Debian archive is getting larger and larger, and the software more and more diverse and complex. Organising software in the archive is difficult, and the existing section system, designed to cope with a much smaller number of packages, is no longer sufficient.
..
Debags attaches categories (we call them tags) to packages, creating a new set of useful structured metadata that can be used to implement more advanced ways of presenting, searching, maintaining and navigating the package archive.
There is a web-based Debtags editor, also one can start from the Debtags TODO list
No ${misc:Depends}
http://lintian.ubuntuwire.org/quantal/tags/debhelper-but-no-misc-depends.html lists a lot of packages which use debhelper, but don't have ${misc:Depends} specified in their Depends: line.
If you decide to pick any of the list, please also check if the package is in Debian as well. http://packages.debian.org can be used for this. If the package exists in Debian as well, please consider sending the patch to Debian first.
Experienced contributors
GCC 4.7
If you have a bit more experience, you might want to help out with the transition to gcc-4.7.
Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html
- To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from quantal.
Here's the list in the Debian bug tracker:
Outstanding bugs -- Serious (policy violations or makes package unfit for release); Unclassified
Forwarded bugs -- Serious (policy violations or makes package unfit for release)
Make sure you
Java 7
If you are a bit more experienced and have worked with Java before this might be just the right thing for you.
Have a look at JavaTeam/Java7Default and familiarise yourself with the general task of porting packages to Java 7
Pick any of the bug list and propose a fix
Make sure you
submit your changes to Debian with the usertag 'openjdk-7-transition'
Working with patch systems
Unfortunately, the are many bugs on Launchpad that have patches attached that haven't seen any attention from a developer. Often these patches need intervention by a developer before they are ready for upload. They may just be changes against the upstream code with none of the packaging details taken care of. Often they just need to use the package's patch system, have a changelog entry added, and go through the SponsorshipProcess.
Working on these bugs is a great way to become familiar with patch systems.
Review the patch system documentation before you begin. The ReviewersTeam also has some useful information on getting patches ready to be uploaded.
- Confirm that the bug still exists.
- Review and test the provided patch, making sure that it actually fixes the bug.
Apply the patch to the package using a patch system.
- Produce a debdiff and subscribe ubuntu-sponsors or propose a merge.
Below are a few suggested targets, but many more can be found on Launchpad with this bug search.
Bug #947892: Scrolling ncurses app in xfce4-terminal with mouse wheel not working
Bug #737838: No way to change Tasque Preferences without a systray icon
Bug #979060: Mutt should be able to set screen/tmux window title
Make sure you submit your changes to Debian if the problem applies there as well.
More bugs
MOTU/TODO lists lots and lots of other tasks you might want to start working on.
Organisation
If you want to help out organising these events, check out our Organisation page and join us at MOTU/Meetings or generally in #ubuntu-motu on irc.freenode.net
UbuntuDevelopment/BugFixingInitiative (last edited 2013-12-03 12:01:55 by dholbach)