-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Charles A Edwards wrote: > On Fri, 1 Aug 2003 17:53:51 +0200 > Tibor Pittich <[EMAIL PROTECTED]> wrote: > > >>hm, strange.. and where was exactly problem? > > > That is the point. > I do not know where the problem lies. > > Just attempted to upload again. > Dled the latest spec from CVS, sylpheed-0.9.4-1mdk > Since -1mdk never made it to contrib the only thing I change in the spec > is the date in changelog from Jul 28 to Aug 01 > > Upload both new rpm and src rpm to contrib > > Just got rejection notice > "You have not built your package with the changes from the previous > package > > * Fri Aug 01 2003 Charles A Edwards <[EMAIL PROTECTED]> 0.9.4-1mdk" > > At this point I am at a dead end as to how to proceed. >
The problem is this: [EMAIL PROTECTED] buchan]$ ls /contrib/*/sylpheed-0.9.* /contrib/RPMS/sylpheed-0.9.3-3mdk.i586.rpm /contrib/SRPMS/sylpheed-0.9.4-1mdk.src.rpm Incidentally, the same as mine: [EMAIL PROTECTED] buchan]$ ls /contrib/*/pam_mount* /contrib/RPMS/pam_mount-0.5.14-2mdk.i586.rpm /contrib/RPMS/pam_mount-devel-0.9.2-3mdk.i586.rpm /contrib/SRPMS/pam_mount-0.9.2-3mdk.src.rpm I have tried 4 uploads now to fix this issue, and never managed to get all 3 packages uploaded ... but other packages seem to upload fine ... Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/KqgRrJK6UGDSBKcRApkoAJ9jXoemyrL7q5WFkWSDaa/YhYcRxwCfcj3C Rh8a+phA5boK9xAh/+kPGFs= =tqyK -----END PGP SIGNATURE----- ****************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. ******************************************************************
