Dan, > cli-complete.ksh: > new_test "pkgsend [EMAIL PROTECTED]" > trans_id=$(pkgsend -s $REPO_URL open [EMAIL PROTECTED],5.11-0) > expect_exit 0 $? > eval $trans_id > pkgsend -s $REPO_URL close > expect_exit 0 $? > > new_test "pkgsend rename [EMAIL PROTECTED] [EMAIL PROTECTED]" > pkgsend -s $REPO_URL rename [EMAIL PROTECTED],5.11-0 [EMAIL > PROTECTED],5.11-0 > expect_exit 0 $? > > What I'm confused about here is that it seems like the "close" > operation closes the transaction, but that the code seems to > continue to use the transaction ID left in the user's environment.
The rename operation doesn't take a transaction ID. Is the presence of the stale transaction ID causing problems elsewhere? > I'm also seeing some tracebacks in the depot when I write > some simple test cases in this department: > > self.pkgsend(durl, "rename [EMAIL PROTECTED] [EMAIL > PROTECTED]") > > Yields a depot log of: > > Traceback (most recent call last): > File "/usr/lib/pkg.depotd", line 397, in do_GET > exec op_call > File "<string>", line 1, in ? > File "/usr/lib/pkg.depotd", line 200, in rename_0 > src_fmri = fmri.PkgFmri(rename_dict['Src-FMRI'][0], None) > File "modules/fmri.py", line 49, in __init__ > File "modules/version.py", line 164, in __init__ > AssertionError You're hitting an assertion in the FMRI code that requires a version string to contain a certain number of components. It looks like I forgot to catch this error. Have you filed a bug on this, or should I? Thanks, -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
