Bug#1025413: ITP: python-pyglfw -- Python bindings for GLFW
Package: wnpp Severity: wishlist Owner: Étienne Mollier X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-pyglfw Version : 2.5.5 Upstream Author : Florian Rhiem * URL : https://github.com/FlorianRhiem/pyGLFW * License : Expat Programming Lang: Python Description : Python bindings for GLFW This module provides Python bindings for GLFW. It is a ctypes wrapper which keeps very close to the original GLFW API, except for: . * function names use the pythonic words_with_underscores notation instead of camelCase * GLFW_ and glfw prefixes have been removed, as their function is replaced by the module namespace * structs have been replaced with Python sequences and namedtuples * functions like glfwGetMonitors return a list instead of a pointer and an object count * Gamma ramps use floats between 0.0 and 1.0 instead of unsigned shorts * GLFW errors are reported as glfw.GLFWError warnings if no error callback is set * instead of a sequence for GLFWimage structs, PIL/pillow Image objects can be used This package is part of the missing dependencies of psychopy. It will be maintained under Debian Python Team umbrella. Development will occur on salsa[1]. [1]: https://salsa.debian.org/python-team/packages/python-pyglfw Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/9, please excuse my verbosity. On air: Neverland - Buy Your Dream signature.asc Description: PGP signature
propose: provide "docker" package as docker, not wmdocker
Hi, I'd like to propose wmdocker package would rename its source package from docker to wmdocker, and then docker.io package provides docker binary package and transitional docker.io package. Most of users who is not Debian expert still confusing with docker package, so I want to fix it in Debian12 "bookworm". wmdocker and transitional dummy docker package is already in Debian10 "buster", so it does not confuse users and also other packages as well. Any thoughts? If there's no objections against it, I'll file a bug and upload renamed source package for wmdocker (maybe with some more updates to comply with current Standards-version) first. -- Hideki Yamane
debian/watch: Ignoring pre-release on GittHub
Hi, Recently, I've faced an issue with debian/watch with pre-released version. Here is the scenario: 1. upstream releases x.y.z with pre-release label. (tagged with x.y.z) 2. new release x.y.z was detected on developer dashboard (https://qa.debian.org/developer.php) 3. upstream releases x.y.z as the official release. (re-tagged with x.y.z) After step 3, it is okay to do packaging normally, but Just after step 1, there may be a possibility to be overlooked that it should not be ready for packaging. (from qa.d.o overview) (even though looking at GitHub release page, it is obvious that it is "pre-release") Is there any good rule to ignore the pre-release in debian/watch? -- Kentaro Hayashi
Bug#1025425: ITP: fonts-vazir -- Persian TrueType Font
Package: wnpp Severity: wishlist Owner: Danial Behzadi X-Debbugs-Cc: debian-devel@lists.debian.org, dani.be...@ubuntu.com * Package name: fonts-vazir Version : 33.003 Upstream Author : Saber Rastikerdar * URL : https://rastikerdar.github.io/vazirmatn/en * License : OFL Programming Lang: FontForge Description : Persian TrueType Font Vazirmatn project is a Persian-Arabic typeface family with nine weights started in 2015 under the name of Vazir and its design and development continued during these years. The Vazirmatn font has a simple and smooth form and can be used in most contexts. For Latin glyphs the Roboto font has been used. This is a free and open source software.
Re: Automated backports based on Janitor work?
On Sat, Dec 03, 2022 at 09:11:57AM +0100, Niels Thykier wrote: > Jelmer Vernooij: > > On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote: > > > [...] > > > Jelmer, did you already think about that? Is there a way one could help > > > you? > > > > Reviving this thread that's more than a year old... > > > > [...] > > > > Known issues that still need to be addressed: > > > > * backport from testing rather than unstable > > * rename the suite from bullseye-backports to something that does't > > clash with the official backports (version strings are already > > different) > > * finish processing the rest of the archive > > * better sanity checking to prevent too many dependencies from being > > pulled in > > > > I haven't decided on a name yet. "auto-bullseye-backports", perhaps? > > To save the janitor some compute power, would make sense to skip packages > that have already been backported? E.g., I noted there is an auto-backport > for debhelper even though debhelper is "in sync" between stable-backports > and testing (or even sid at the moment). > > Other than that, I think this looks great and I hope this will help make > backporting more smooth. Yeah, that's a good point - I've now excluded these and packages with the same version in stable and testing. Reduces the todo queue by about 5000 packages :) Cheers, Jelmer
Re: debian/watch: Ignoring pre-release on GittHub
You can try to take a look at the GitHub API, e.g. [1]. Inside is an `prerelease` entry. Not sure how easy this is to implement in uscan though. Cheers, Stephan [1]: https://api.github.com/repos/lutris/lutris/releases?per_page=100
