Deprecating CVS and Subversion imports
What are code imports?
Launchpad’s code import service allows users to automatically mirror code from external version control systems into Launchpad. Historically, this has supported imports from CVS, Subversion, Bazaar and Git.
As part of this, Launchpad currently also supports imports into Bazaar branches from:
- Concurrent Version System to Bazaar
- Subversion via cvs2svn to Bazaar
- Subversion via bzr-svn to Bazaar
These imports will be deprecated.
Why deprecate these imports?
As announced in Phasing out Bazaar code hosting, Bazaar itself has been deprecated and is no longer actively developed. The last release was in 2016, and usage has steadily declined.
Maintaining imports from these less common version controls to Bazaar requires significant efforts.
To streamline our services and focus resources where they matter most, Launchpad will be retiring the previously mentioned Bazaar-based imports.
Timelines
- September 18th, 2025: No new import configurations for the previously mentioned Bazaar-based imports will be accepted.
- October 1st, 2025: All existing CVS to Bazaar and SVN to Bazaar imports (both cvs2svn and bzr-svn) will be shut down. Import jobs will no longer run after this date.
Migration paths
If you are currently using these imports, we recommend:
- Migrating the source repository to Git.
- Reconfiguring your Launchpad project to use a Git-based import instead.
Guides and references:
- Migrate a Repository From Bazaar to Git
- General CVS/SVN to Git migration tools (such as git cvsimport, svn2git, or git svn) are widely documented.
Call for action
If you have a project still depending on CVS to Bazaar or SVN to Bazaar imports, and you are unsure how to migrate, please reach out to us.
You can contact us in #launchpad:ubuntu.com on Matrix, or via e-mail at feedback@launchpad.net.
Join the discussion at: https://discourse.ubuntu.com/t/deprecating-cvs-and-subversion-imports/66876
Tags: bazaar, codeimport, launchpad
