-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I seem to have a small problem to checkin the new interceptty package:
the "opd release" has not picked up the interceptty.patch file and
checked the package in without it. A second run does also not pickup
the patch and leads to an permission denied error  copying the
.src.rpm to ftp.openpkg.org.

So two questions arises:
- - did I something wrong?
- - how to I get new .patch files into cvs repository?

cheerio
   Steve

developer$ opd release
++ processing package interceptty
++ cleaning up sources and logs
++ determine [no]src extension
++ determine old version (if any)
++ determine new version
++ determine branch and related release number and upload suffix
++ checking release number
++ checking upload suffix
++ linting interceptty.spec (package specification)
++ releasing interceptty-0.6-20060429.src.rpm to distribution area
OpenPKG /current/SRC/
scp: //current/SRC//interceptty-0.6-20060429.src.rpm: Permission denied
++ determining commit message
++ determining commit file list
++ committing changes to CVS repository
cvs commit: Examining src/interceptty
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEU4U4QftxpMD/nVkRArcxAKDmejrSVs2IIywE1d4URFjafx3++gCgnSGJ
N9ZTgDxhPVjNA1wfJbcaU5o=
=GTR5
-----END PGP SIGNATURE-----

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to