Move completed projects to the correct section
Update link to the BuildinfoFiles page
|Deletions are marked like this.||Additions are marked like this.|
|Line 101:||Line 101:|
|* ReproducibleBuilds/BuildinfoSpecification||* ReproducibleBuilds/BuildinfoFiles|
The team is in charge of the dpkg package manager, dpkg-repack and debsig-verify. It maintains it and develops new features.
Alioth Project: https://alioth.debian.org/projects/dpkg
Functional test suite:
git clone https://anonscm.debian.org/git/dpkg/dpkg-tests.git (web interface)
Unit test suite code coverage: https://dpkg.alioth.debian.org/coverage/
Packages autobuilt from git: master branch
Interacting with the team
Development mailing list: <debian-dpkg AT lists DOT debian DOT org> (subscribe form)
Public IRC channel: #debian-dpkg on irc.debian.org (OFTC).
GuillemJover (guillem) is the primary developer.
- Many other translators have commit access to maintain their translations.
- Several other contributors provide occasional patches/branches.
See the Contribute page, and check the following links:
GitUsage: recommendations for handling the Git repository
Porting: Resources used for porting.
Downstream: list of downstream distributions shipping dpkg.
Triggers HOWTO by Sean Finney (from archive.org).
- Current projects:
Current proposals (no endorsement implied by items being present in the list):
/TimeTravelFixes: Design problems possibly too costly to solve now.
- The eternal dpkg 2.0 rewrite:
- Conffile handling improvements:
- .deb format:
Finished projects (from dpkg PoV):
?/PerlAPICleanup: work needed to cleanup the perl API.
/DebianRules: environment variables setup.
Bits from the dpkg maintainer (dpkg 1.13.x upload to experimental)
Bits from the dpkg maintainer (dpkg 126.96.36.199 to 1.13.9)
New dpkg in experimental (dpkg 1.14.7~newshlib)
Misc development news (dpkg 1.14.6 to 1.14.8)
Bits from the dpkg team (dpkg 188.8.131.52 to 184.108.40.206)
Recent changes in dpkg (dpkg 1.15.6 to 1.15.7)
dpkg summit (around 2007, never happened)
The project has transitioned over several different version control systems ("tarballs", CVS, Bazaar and git). Historic VCS data and scripts were used when switching to git, to try to preserve as much history as possible.