On 08/26/2010 04:07 PM, Tim Penhey wrote:
> On Fri, 27 Aug 2010 05:49:36 you wrote:
>> A potential workaround would be to delete the PPA the release was
>> published in
>
> That seems somewhat extreme. What other options are there?
I don't know of any other workarounds at present. I guess if there was
some way to delete a sourcepackagerelease, that would work.
Or you could run an SQL query to NULL the appropriate sourcepackagerelease.
Obviously, a non-workaround solution is desirable.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/26/2010 04:07 PM, Tim Penhey wrote:
> On Fri, 27 Aug 2010 05:49:36 you wrote:
>> A potential workaround would be to delete the PPA the release was
>> published in
>
> That seems somewhat extreme. What other options are there?
I don't know of any other workarounds at present. I guess if there was lease, that would work.
some way to delete a sourcepackagere
Or you could run an SQL query to NULL the appropriate sourcepackagere lease.
Obviously, a non-workaround solution is desirable.
Aaron enigmail. mozdev. org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkx 2zLoACgkQ0F+ nu1YWqI2fRwCfZ3 tc4HwbJoJKFFiWL UN08DV7 fXDgZY2IdxwSH+ 2dO
HUIAn0J6xrbqGLU
=cZgL
-----END PGP SIGNATURE-----