Fading out Tcl/Tk 8.5 from Debian

Hi fellow developers, Since Tcl/Tk 8.5 is currently at its End of Life (see [1]) I would like to start a campaign on removing it from Debian. There's a wiki page [2] with all binary packages which depend on Tcl/Tk 8.5 directly or indirectly, and with all packages which build-depend on tcl8.5-dev

Bug#887730: ITP: golang-github-google-jsonapi -- jsonapi.org style payload serializer and deserializer

Package: wnpp Severity: wishlist Owner: Sascha Steinbiss * Package name: golang-github-google-jsonapi Version : 1.0.0+git20171108.e0fc4ee-1 Upstream Author : Google * URL : https://github.com/google/jsonapi * License : MIT Programming Lang: Go Description

Bug#886238: Build-Profiles purpose, mechanism vs policy (was Re: Bug#886238: Please introduce official nosystemd build profile)

> "Adrian" == Adrian Bunk writes: Adrian> For many use flags the only benefit is an unused library Adrian> less on the system when the flag is disabled, and this also Adrian> applies to the proposed nosystemd profile discussed in this Adrian> bug. Agreed. Adrian> Suppor

Bug#887734: ITP: libqtshadowsocks -- Lightweight and ultra-fast shadowsocks library written in C++/Qt

Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org * Package name: libqtshadowsocks Version : 2.0.1 Upstream Author : Symeon Huang * URL : https://github.com/shadowsocks/libqtshadowsocks * License : LGPL-3+ Programming Lang: C++/Qt

TTF or OTF, bad behavior on upgraded systems

Hi all, I was looking at the fonts page[1] on the wiki and it mentions: "For most uses, you’ll want TrueType (TTF) and OpenType (OTF) fonts" In fact, is it necessary to install both, or just OTF if the same font is available as both? On a system that has been upgraded from etch through several

Updating the Maintainer field in preparation for Alioth's shutdown?

According to the schedule [1], incoming mail will be disabled for mailing lists hosted at Alioth in less than 2 weeks. I am still confused about what we are recommending that maintainers and teams do, so I'm asking questions now. :) 1. Are the lists still expected to stop accepting new mail on tha

Bug#887800: ITP: libfuture-asyncawait-perl -- deferred subroutine syntax for futures

Package: wnpp Owner: gregor herrmann Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libfuture-asyncawait-perl Version : 0.13 Upstream Author : Paul Evans * URL : https://metacpan.org/release/Future-AsyncAwa

Bug#887801: ITP: libsyntax-keyword-try-perl -- try/catch/finally syntax for perl

Package: wnpp Owner: gregor herrmann Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libsyntax-keyword-try-perl Version : 0.09 Upstream Author : Paul Evans * URL : https://metacpan.org/release/Syntax-Keyword