Bug#598477: ITP: opencl-headers -- OpenCL (Open Computing Language) header files

[Russ Allbery]

Andreas Beckmann <debian at abeckmann.de> writes:

> OK, I'm targeting driver 256.53-2 as the first version this will work
> with.

> As 256.xx will be only in experimental for a while, it uploading
> opencl-headers (and and nvidia-cuda-tookit later on) to unstable OK?
> Currently these packages will be useful only with the driver packages
> from experimental, but once we update the driver in unstable they should
> become useful without requiring another upload. And as there is no
> previous version in unstable that could be broken/removed by this "new
> upstream", I think going to unstable directly should be OK.

I would mildly lean towards uploading them to experimental.  I'm going to
make a run through all the packages I maintain or co-maintain and
re-upload experimental packages to unstable once squeeze is out, and I
don't mind doing that with packages I sponsor as well.  But if you really
want to target unstable, it doesn't make much difference to me and it
shouldn't hurt.

>> Let's plan on 256.53-2.  Should I upload it to experimental?  (Does it
>> have all the changes that are on trunk?  It looks like it might not.)

> I'm going to fix up 256.53-2 now.

Thanks!

> Also something went wrong with the nvidia-cuda-toolkit upload:

>     Subject: nvidia-cuda-toolkit_3.1-1_amd64.changes REJECTED

>     Reject Reasons:
>     The key (0xF985E3400AFC7476) used to sign nvidia-
>     cuda-toolkit_3.1-1.dsc wasn't found in the keyring(s).

Oh, hm.  That's interesting.  Apparently if one changes one's key in the
Debian keyring between the time a package was uploaded and went into NEW
and the time the package was then processed, it ends up rejected.

> Don't reupload again right now, there are some more changes needed.
> Do we do the new upload with revision -1 again or should this be
> incremented?

Keep revision -1, since it never made it into the archive, unless there's
some other reason to bump the revision.  That also makes doing the build a
touch easier, since I don't have to remember to pass in special flags to
be sure the upstream .orig.tar.gz is included.

Let me know when this is set and I'll re-upload.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>