Dirk Eddelbuettel <e...@debian.org> writes: > Can you recommend a debian/rules and debian/control for me to look at? > > The package mygrated happily from python 2.3, 2.4, ... to now 2.7; but > I have yet to work with python3 so a gentle nudge or push would be > appreciated.
I'll gladly work with you on this, Dirk. The existing source package doesn't have a ‘Vcs-*’ field. So I have established a Git repository at Alioth for the Debian packaging (‘ssh://git.debian.org/git/collab-maint/pkg-rpy2.git/’). If you are using a VCS already to track the packaging, please let me know. > | Please upload any new versions before Jessie's release to > | experimental, the Release Team has been doing such great work, it'd > | be a shame to see unstable out of sync before we release! > > Hm, unstable != testing. Do you really want this only in experimental? Uploads to “unstable” mean “I intend this package release to be released with the next release of Debian”. During the release freeze, the changes allowed into the next Debian release are restricted by the freeze policy <URL:https://release.debian.org/jessie/freeze_policy.html>. For changes intended to enter Debian only after the release freeze ends, we upload only to “experimental”. -- \ “Creativity can be a social contribution, but only in so far as | `\ society is free to use the results.” —Richard M. Stallman | _o__) | Ben Finney <b...@benfinney.id.au> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org