Package: tailor
Version: 0.8-2
Severity: important
Tags: patch
The tailor package ships with most of its files in the versioned
directory /usr/lib/python2.3. Therefore it's crucial that the python
dependency is versioned as well. This is most easily achieved by
including the ${python:Depends} substvar in control.
I'm including a slightly larger patch that results from a merge of a
private tailor package I had built some time ago, and your current
version. The patch additionally addresses a few minor issues:
- Adds proper python dependencies.
- Removes superfluous substvars ${shlibs:Depends} and ${misc:Depends}.
- Suggests all supported version control systems.
- Includes a description that's more geared towards end-users.
- Prevents an empty /usr/sbin from being included in the package.
It's up to you whether you find the extended patch useful or not, but in
any case please fix the dependency problem.
Regards,
Daniel.
diff -u tailor-0.8/debian/control tailor-0.8/debian/control
--- tailor-0.8/debian/control
+++ tailor-0.8/debian/control
@@ -8,9 +8,16 @@
Package: tailor
Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, python
-Description: Tool to keep in sync various kinds of repository (CVS, SVN, ...)
- Python tool able to keep in sync various kinds of repository: it works for
- various revision control systems, such as CVS, Subversion, Darcs and
- (still partially) Monotone, Mercurial and Codeville, preserving history.
+Depends: ${python:Depends}
+Suggests: cvs, subversion, darcs, mercurial, monotone, codeville, bzr
+Description: migrate changesets between version control systems
+ The tailor tool moves patches and changesets between different repositories,
+ preserving as much information as possible. The repositories can be managed
+ by different version control systems. Currently, CVS, Subversion, darcs,
+ mercurial, monotone, Codeville, and Bazaar-NG are supported.
+ .
+ While cvsync is useful for one-time operation, when switching to a different
+ version control system, it can also synchronise repositories on an ongoing
+ basis. Changesets are either pulled one-way from a master repository, or
+ migrated back and forth for full two-way synchronisation.
.
Homepage: http://www.darcs.net/DarcsWiki/Tailor
diff -u tailor-0.8/debian/dirs tailor-0.8/debian/dirs
--- tailor-0.8/debian/dirs
+++ tailor-0.8/debian/dirs
@@ -2 +1,0 @@
-usr/sbin
diff -u tailor-0.8/debian/control.in tailor-0.8/debian/control.in
--- tailor-0.8/debian/control.in
+++ tailor-0.8/debian/control.in
@@ -9,9 +9,16 @@
Cpu: all
System: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, python
-Description: Tool to keep in sync various kinds of repository (CVS, SVN, ...)
- Python tool able to keep in sync various kinds of repository: it works for
- various revision control systems, such as CVS, Subversion, Darcs and
- (still partially) Monotone, Mercurial and Codeville, preserving history.
+Depends: ${python:Depends}
+Suggests: cvs, subversion, darcs, mercurial, monotone, codeville, bzr
+Description: migrate changesets between version control systems
+ The tailor tool moves patches and changesets between different repositories,
+ preserving as much information as possible. The repositories can be managed
+ by different version control systems. Currently, CVS, Subversion, darcs,
+ mercurial, monotone, Codeville, and Bazaar-NG are supported.
+ .
+ While cvsync is useful for one-time operation, when switching to a different
+ version control system, it can also synchronise repositories on an ongoing
+ basis. Changesets are either pulled one-way from a master repository, or
+ migrated back and forth for full two-way synchronisation.
.
Homepage: http://www.darcs.net/DarcsWiki/Tailor
