Bug#945447: RFS: emacs-websocket/1.12+1.g74e4b82-1 [ITP] -- Emacs WebSocket client and server

On 2019-11-27 07:43:59, Nicholas D Steeves wrote: > Hi Antoine, > > Antoine Beaupré writes: > >> A few comments... >> >> Why do you specify a compression level and algorithm in gbp.conf? >> >> compression = xz >> compression-level = 9 >> > > This reduces the incidence of encountering an annoying

Bug#945447: RFS: emacs-websocket/1.12+1.g74e4b82-1 [ITP] -- Emacs WebSocket client and server

Hi Antoine, Antoine Beaupré writes: > A few comments... > > Why do you specify a compression level and algorithm in gbp.conf? > > compression = xz > compression-level = 9 > This reduces the incidence of encountering an annoying gbp bug, where gbp fails, allegedly because "two tarballs were

Bug#945447: RFS: emacs-websocket/1.12+1.g74e4b82-1 [ITP] -- Emacs WebSocket client and server

A few comments... Why do you specify a compression level and algorithm in gbp.conf? compression = xz compression-level = 9 Upstream doesn't seem to use any peculiar tarball format, so that generated tarball won't match the one published on github. I also wonder if it's really necessary to ship

Bug#945447: RFS: emacs-websocket/1.12+1.g74e4b82-1 [ITP] -- Emacs WebSocket client and server

Package: sponsorship-requests Severity: wishlist Control: block 945329 by -1 Dear mentors, I am looking for a sponsor for my package "emacs-websocket", which is a required dependency of atomic-chrome-el (Bug #909336). * Package name: emacs-websocket Version : 1.12+1.g74e4b82-1