Bug#955609: ITP: golang-github-valyala-tcplisten -- Customizable TCP net.Listener for Go

2020-04-03 Thread Alois Micard

Package: wnpp
Severity: wishlist
Owner: Aloïs Micard 

* Package name: golang-github-valyala-tcplisten
  Version : 0.0~git20161114.ceec8f9-1
  Upstream Author : Aliaksandr Valialkin
* URL : https://github.com/valyala/tcplisten
* License : Expat
  Programming Lang: Go
  Description : Customizable TCP net.Listener for Go

 Package tcplisten provides customizable TCP net.Listener with
 various performance-related options.
 .
 This package is needed for valyala/fasthttp

--
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2



Bug#955611: ITP: golang-github-valyala-fasthttp -- Fast HTTP package for Go. Tuned for high performance.

2020-04-03 Thread Alois Micard

Package: wnpp
Severity: wishlist
Owner: Alois Micard 

* Package name: golang-github-valyala-fasthttp
  Version : 1.9.0-1
  Upstream Author : Aliaksandr Valialkin
* URL : https://github.com/valyala/fasthttp
* License : Expat
  Programming Lang: Go
  Description : Fast HTTP package for Go. Tuned for high 
performance. Zero memory allocations in hot paths. Up to 10x faster than 
net/http


 Fast HTTP implementation for Go.

--
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2



trends.debian.net updated

2020-04-03 Thread Lucas Nussbaum
Hi,

https://trends.debian.net/ was just updated (with data until April 1st).

The main change is that graphs are now displayed by default for Debian
'testing' (thus hiding broken packages in unstable only). Graphs for
'unstable' are still available.

There are a few things that strike me:

- first, one can see how the number of package in testing decreases
  slowly during freezes, as broken packages are removed

- second, it's surprising to see how the number of packages has been
  quite stable since the beginning of the buster freeze

I keep wondering if we should make an effort to remove from testing
packages whose packaging 'style' is clearly outdated, such as packages
not updated since 2004 ('beav' is an example)...

Lucas


signature.asc
Description: PGP signature


Re: What to do when DD considers policy to be optional? [kubernetes]

2020-04-03 Thread Thomas Goirand
On 3/28/20 2:41 AM, Dmitry Smirnov wrote:
> On Friday, 27 March 2020 7:08:35 PM AEDT Marc Haber wrote:
>> Many upstreams deliver .deb packages of their current releases in
>> noticeably high quality from a Debian point of view. One should look
>> at them before putting them in production.
> 
> I have a very different observations regarding upstream packaging for Debian.
> Most vendor packages are of notoriously bad quality, disconnected from Debian 
> practices and bug reports, not benefiting from QA and continuous testing, 
> heavily compromising on policy compliance, not following library transitions, 
> etc., etc.
> 
> The very existence of vendor packaging often indicates unwillingness to do 
> the job properly, up to our standards, and maybe even unwillingness to 
> cooperate with Debian to achieve proper integration. Precisely because it is 
> easier to do a quick sloppy work that won't be accepted without much 
> improvements.

+1 to all you wrote, Dmitry.

I have very rarely found good upstream packages. Even worth: very few
upstream provide the source package (and when they do, it's extremely
hard to find).

Cheers,

Thomas Goirand (zigo)



Re: trends.debian.net updated

2020-04-03 Thread Paul Gevers
Hi Lucas

On 03-04-2020 22:41, Lucas Nussbaum wrote:
> There are a few things that strike me:
> 
> - first, one can see how the number of package in testing decreases
>   slowly during freezes, as broken packages are removed

And interesting to see that this hardly happened during the last freeze.

> - second, it's surprising to see how the number of packages has been
>   quite stable since the beginning of the buster freeze

I expect this to be the result of the Python2 support removal which has
caused lots of packages to be removed from the archive.

> I keep wondering if we should make an effort to remove from testing
> packages whose packaging 'style' is clearly outdated, such as packages
> not updated since 2004 ('beav' is an example)...

Is there something wrong with those packages? If so, what is it exactly?
You can file RC bugs for real issues obviously.

Paul



signature.asc
Description: OpenPGP digital signature