On 23 April 2015 at 06:36, Ben Finney wrote: | 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.
That is orthogonal to the python3 issue. | 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. I have write access to https://github.com/Debian but I am a few years behind converting my 100+ packages to using git. | > | 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>. In theory, yes. In practice that never mattered in the 20 years I uploaded packages to unstable because we "know" when unstable is effectively cut from testing / the release. With Jessie being released _this weekend_ I don't really see the point. | For changes intended to enter Debian only after the release freeze ends, | we upload only to “experimental”. Thanks for all that. Can we direct to coversation towards python3 now? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
