Taking over package aiocoap

Hi All, The package aiocoap is in bad shape and was asked to be removed. I would like to maintain it. Is there any objection? -- Mazen Neifer signature.asc Description: This is a digitally signed message part

Re: signify and signify-openbsd names

* Simon Richter [241007 09:50]: > On 10/7/24 21:43, Marvin Renich wrote: > > > trixie: > >remove old src: signify > > yes. > > >single source upload: > > src: signify -> signify-mail > > binary: signify -> signify-mail > > new signify as transitional > >

Re: signify and signify-openbsd names

* Simon Richter [241007 04:32]: > The correct approach is one release with a transitional package, pulling the > new package in, and one release with the name unused (so the transitional > package is listed in Obsolete/Local). > > The release without the package also makes sure that any archive v

Re: Taking over package aiocoap

Hi Johannes, On Mon, 2024-10-07 at 20:15 +0200, Johannes Schauer Marin Rodrigues wrote: > Quoting Mazen Neifer (2024-10-07 18:31:14) > > The package aiocoap is in bad shape and was asked to be removed. > > > > I would like to maintain it. Is there any objection? > > there is a process for this:

Re: signify and signify-openbsd names

On Sat, 05 Oct 2024 20:39:39 +0200, Ben Hutchings wrote: >I'm fairly sure there's no support for this in Debian infrastructure >(dak or debbugs). I have the gut feeling that this is going to cause at least minor discomfort because our tools don't care for that at all. I still get occasional mail

Re: signify and signify-openbsd names

Hi, On 10/7/24 16:58, Marc Haber wrote: I also see trouble in the archive when we have old signify in older distributions and new signify in unstable and testing. Without having any technical justification for that, I would probably go ahead to rename signify to signify-mail, leaving signify-op

Re: signify and signify-openbsd names

On Mon, 7 Oct 2024 17:31:33 +0900, Simon Richter wrote: >On 10/7/24 16:58, Marc Haber wrote: >> I also see trouble in the archive when we have old signify in older >> distributions and new signify in unstable and testing. Without having >> any technical justification for that, I would probably go

ITP: golang-github-olareg-olareg -- Minimal container registry

Package: wnpp Severity: wishlist Owner: Felix Moessbauer * Package name: golang-github-olareg-olareg Version : 0.1.1 Upstream Author : * URL : https://github.com/olareg/olareg * License : Apache-2.0 Programming Lang: Go Description : Minimal container

Bug#1084498: ITP: python-google-api-python-client -- This is the Google API Python client library for Google's discovery based APIs.

Package: wnpp Severity: wishlist Owner: EiPi Fun X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-google-api-python-client Version : 2.147.0 Upstream Contact: Anthonios Partheniou * URL : https://github.com/googleapis/google-api-python-client/ * Lice

Bug#1084525: ITP: gurk -- Signal messenger CLI client

Package: wnpp Severity: wishlist Owner: Matthias Geiger X-Debbugs-Cc: debian-devel@lists.debian.org, debian-r...@lists.debian.org, werdah...@debian.org * Package name: gurk Version : 0.5.1 Upstream Contact: boxdot * URL : https://github.com/boxdot/gurk-rs * License

Bug#1084537: ITP: uni-algo -- Unicode Algorithms Implementation for C/C++

Package: wnpp Severity: wishlist Owner: Yanhao X-Debbugs-CC: debian-devel@lists.debian.org * Package name: uni-algo Version : 1.2.0 Upstream Author : mg152 * URL : https://github.com/uni-algo/uni-algo * License : Public Domain or MIT Programming Lang: C++

Re: proposal: Hybrid network stack for Trixie

It seems to me this proposal is just a *tad* too ambitious. I haven't followed the entirety of all threads about this topic (has anyone?) but it seems to me we're proposing to do two major changes at once: 1. replace ifupdown with systemd-networkd 2. unify configuration of networkd and NetworkM

Re: signify and signify-openbsd names

Hi, On 10/7/24 21:43, Marvin Renich wrote: trixie: remove old src: signify yes. single source upload: src: signify -> signify-mail binary: signify -> signify-mail new signify as transitional unversioned Depends: signify-mail yes. trixie

ITP: golang-github-regclient-regclient -- Docker and OCI Registry Client in Go and tooling using those libraries.

Package: wnpp Severity: wishlist Owner: Felix Moessbauer * Package name: golang-github-regclient-regclient Version : 0.7.1-1 Upstream Author : * URL : https://github.com/regclient/regclient * License : Apache-2.0 Programming Lang: Go Description : Dock

Re: Taking over package aiocoap

Hi, Quoting Mazen Neifer (2024-10-07 18:31:14) > The package aiocoap is in bad shape and was asked to be removed. > > I would like to maintain it. Is there any objection? there is a process for this: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging Thanks!

Re: Taking over package aiocoap

Am 7. Oktober 2024 16:31:14 UTC schrieb Mazen Neifer : >Hi All, > >The package aiocoap is in bad shape and was asked to be removed. > >I would like to maintain it. Is there any objection? Hi Mazen, aiocap seems to be eligible for package salvaging, see [1] for the suggested process to salvage i

Bug#1084737: ITP: libcasilda-0.1 -- simple wayland compositor widget for Gtk 4

Package: wnpp Severity: wishlist Owner: Jonathan Carter X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: libcasilda-0.1 Version : 0.1 Upstream Contact: Juan Pablo Ugarte (https://gitlab.gnome.org/jpu) * URL : https://gitlab.gnome.org/jpu/casilda * License

Re: Taking over package aiocoap

Hi Mazen (2024.10.07_16:31:14_+) Not my package, but thank you! Stefano > Hi All, > > The package aiocoap is in bad shape and was asked to be removed. > > I would like to maintain it. Is there any objection? > -- > Mazen Neifer -- Stefano Rivera http://tumbleweed.org.za/ +1 415 6