projects / debcargo-conf.git / blame
| Commit | Line | Data |
|---|---|---|
| 23d43431 SL |
1 | ========== |
| 2 | Sponsoring | |
| 3 | ========== | |
| 4 | ||
| 5 | ||
| 6 | Ready for upload (Request For Sponsor) | |
| 7 | ====================================== | |
| 8 | ||
| 9 | If you do not have upload rights, simply ``touch src/$crate/debian/RFS`` in | |
| 10 | your crate's directory, commit and push it, and a DD or DM will get around to | |
| 11 | it at some point. | |
| 12 | ||
| 13 | Please join the IRC channel #debian-rust on OFTC to be available to answer | |
| 14 | to questions. Please monitor the RFS file as the sponsors can use it to | |
| 15 | communicate with the maintainer. | |
| 16 | ||
| 17 | If you haven't seen activity for 2 or 3 weeks, feel free to ping sylvestre on the | |
| 18 | IRC #debian-rust channel. | |
| 19 | ||
| 20 | If your update breaks semver compatibility, please first check the reverse | |
| 21 | dependencies by running:: | |
| 22 | ||
| 23 | $ aptitude search '~Dlibrust-$cratename' | |
| 24 | ||
| 25 | and try to verify that they won't be broken by your update, by building them. | |
| 26 | If they are broken, then: | |
| 27 | ||
| 28 | 1. Document the problem in ``debian/BLOCK``. | |
| 29 | 2. File an issue upstream to report that they should update to the new library | |
| 30 | 3. Write a patch if you can get that working, and document it. | |
| 31 | ||
| 32 | ||
| 33 | Review list | |
| 34 | =========== | |
| 35 | ||
| 36 | To list all packages under RFS, run ``dev/list-rfs.sh``. |