| ... | ... | @@ -12,6 +12,17 @@ The result of this query is put on the [Bug of the day web page](http://blends.d |
|
|
|
|
|
|
|
If the package does not fit in any team it should be imported into the [Salvage Team](https://salsa.debian.org/salvage-team) to get the bug fixed there first. The whole procedure should follow the [Salvage procedure described in Wiki](https://wiki.debian.org/PackageSalvaging).
|
|
|
|
|
|
|
|
## Checklist when tackling a bug
|
|
|
|
|
|
|
|
1. Go to [Salsa](https://salsa.debian.org/) and seek for the package name. In some cases the packaging was just migrated but it was not uploaded with `Vcs`-fields set. Note: The Salsa search does not seek in private developer repositories.
|
|
|
|
2. Look for other bugs of the package you want to fix by having a look at `https://bugs.debian.org/src:PACKAGENAME`
|
|
|
|
3. Check package tracker for more information at `https://tracker.debian.org/PACKAGENAME`
|
|
|
|
4. Check the Homepage of the package. Is `debian/control` pointing to the correct homepage or did it moved
|
|
|
|
5. Check the `debian/watch` file whether it reports the latest upstream version correctly
|
|
|
|
6. Is `debian/rules` using `dh` or possibly `cdbs` / long `debhelper`. It might be worth migrating to `dh` in case we will salvage the package.
|
|
|
|
7. Is `debian/copyright` in DEP-5 format? It might be worth migrating to DEP-5 in case we will salvage the package.
|
|
|
|
8. What happens if you run `routine-update -f` on the packaging? Its migrating the package to latest packaging standards. It might create some noise since latest packaging standards for instance mean that the upstream testsuite is run in `dh_auto_test` and `dh_mising` defaults to `failmissing`. These are things you might like to deal with when salvaging the package.
|
|
|
|
|
|
|
|
## Some hints
|
|
|
|
|
|
|
|
### Importing into Salsa
|
| ... | ... | |
