Hi Mike On 07/31/2017 05:11 AM, Michael Gilbert wrote: > On Fri, Jul 21, 2017 at 3:03 PM, Jens Reyer wrote: >> I just uploaded 0~svn33340-0.1 to delayed/10, debdiff attached. >> >> Changelog: >> >> khronos-api (0~svn33340-0.1) unstable; urgency=medium >> >> * Non-maintainer upload. >> * New (and final in svn) upstream revision 33340. >> * Refresh timestamps.patch. >> * Make package Multi-Arch: foreign (closes: #865308). >> Thanks to Hugh McMaster >> * Minor improvement to the package description (closes: #865307). >> * Bump standards version to 4.0.0, no changes needed. >> * Fix file exclusion in tarball generation. > > Hi Jens, > > This isn't really a great version, but ok it will land later today. > It would be far better to update to upstream git, which is now in sync > with the latest opengl 4.5 spec.
For the reasoning to do this intermediate version see my follow-up bug #869233. (btw, I'm quite busy atm, but luckily upstream Wine had a patch for this just today, so they will do the initial testing.) > By the way, NMUs are not supposed to touch maintainer fields like the > standards version, but it's not a big deal. I'm not sure about your intention here. My goal is keeping the build-dependencies of Wine (especially unicode-data and khronos-api) in fine shape. Since I know that you don't have much time I offered to add me as co-maintainer, and started to work on the package in kind of an extension of pkg-wine. The spirit of this upload was to fix uncritical things, while I opened #869233 before doing eventually controversial things. Not checking and bumping the standards version would have felt wrong to me. Maintainer fields aren't mentioned explicitly in policy 5.11, while large parts of Debian take a very liberal stance at NMUs nowadays. So I'm really not sure about your intention here, and how/if to progress with khronos-api: should I only work on khronos-api if there's a rc bug and no sign of activity from your side? Or how far can I go in helping you here and do you want a specific workflow, e.g. bugs for every change or a git repo? So I'll postpone this until further notice from you. I'd really appreciate an answer to #869233. Greets jre
