-=| Damyan Ivanov, Wed, Oct 10, 2007 at 11:18:32PM +0300 |=- > Eddy Petrișor prepared[1] a new version of svn-buildpackage that is > supposed to fix the problems we have with the one currently in the > archive. > > [1] > http://users.alioth.debian.org/~eddyp-guest/upload/svn-buildpackage_0.6.22-experimental/
Peter Makholm was so kind to try this and unfortunately the news are not very good. http://pastebin.ca/734528 1. [EMAIL PROTECTED]:~/ack$ svn-inject -l2 libfile-next-perl_1.00-2.dsc svn+ssh://[EMAIL PROTECTED]/svn/pkg-perl/ 2. cp -l /home/makholm/ack/libfile-next-perl_1.00.orig.tar.gz /home/makholm/ack/tarballs 3. mkdir -p branches/upstream/libfile-next-perl 4. tar -z -x -f /home/makholm/ack/libfile-next-perl_1.00.orig.tar.gz 5. mv File-Next-1.00 current 6. svn -q import -m [svn-inject] Installing original source of libfile-next-perl libfile-next-perl/trunk svn+ssh://[EMAIL PROTECTED]/svn/pkg-perl/trunk/libfile-next-perl 7. svn: 'libfile-next-perl/trunk' does not exist 8. Command svn -q import -m [svn-inject] Installing original source of libfile-next-perl libfile-next-perl/trunk svn+ssh://[EMAIL PROTECTED]/svn/pkg-perl/trunk/libfile-next-perl failed in <unknown>, how to continue now? [Qri?]: < brother> same issue if I try to svn-inject into a newly svnadmin creat'ed /tmp/repo There is one good news -- svn-upgrade works with no problems :) -- dam JabberID: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
