From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 9shTJoV7fGDESQEAgWs5BA (envelope-from ) for ; Sun, 18 Apr 2021 20:33:41 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id CHvLH4V7fGBiJAAAbx9fmQ (envelope-from ) for ; Sun, 18 Apr 2021 18:33:41 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id D7F3819D2C for ; Sun, 18 Apr 2021 20:33:40 +0200 (CEST) Received: from localhost ([::1]:40806 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lYCEm-0004Ru-1Q for larch@yhetil.org; Sun, 18 Apr 2021 14:33:40 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59604) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lYCEA-0004Rf-NV for guix-patches@gnu.org; Sun, 18 Apr 2021 14:33:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:36202) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lYCE9-0004i9-Nd for guix-patches@gnu.org; Sun, 18 Apr 2021 14:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lYCE9-0006HW-LB for guix-patches@gnu.org; Sun, 18 Apr 2021 14:33:01 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#47104] grumble status update Resent-From: Leo Prikler Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Sun, 18 Apr 2021 18:33:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47104 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: jgart , 47104@debbugs.gnu.org Cc: raghavgururajan@disroot.org, Raghav Gururajan Received: via spool by 47104-submit@debbugs.gnu.org id=B47104.161877072424070 (code B ref 47104); Sun, 18 Apr 2021 18:33:01 +0000 Received: (at 47104) by debbugs.gnu.org; 18 Apr 2021 18:32:04 +0000 Received: from localhost ([127.0.0.1]:47745 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lYCDE-0006G9-0O for submit@debbugs.gnu.org; Sun, 18 Apr 2021 14:32:04 -0400 Received: from mailrelay.tugraz.at ([129.27.2.202]:36618) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lYCDB-0006Fj-8R for 47104@debbugs.gnu.org; Sun, 18 Apr 2021 14:32:02 -0400 Received: from nijino.local (194-96-9-9.adsl.highway.telekom.at [194.96.9.9]) by mailrelay.tugraz.at (Postfix) with ESMTPSA id 4FNdp45Mwcz1LLyL; Sun, 18 Apr 2021 20:31:56 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 mailrelay.tugraz.at 4FNdp45Mwcz1LLyL DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tugraz.at; s=mailrelay; t=1618770717; bh=PjaIQXZOOANHr0itrHekZ9qP2XLRWkbjFI02+8USNnc=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=DQfsRkpruvVGqGv+JWm8+iyk1YnOCFWXZfdBWnSDp6tAk7zqeh6pQGGgVOLnSt98t d2cFA9urpanGFFPY77/gJgdKQlVVzyXmrAi0zr66w2Znq6jg7A97Z7D0W4qna3eu3z PDd/BdfdGx0JoxKD8WUFALRlE+8/W1pTVeqjK/LA= Message-ID: From: Leo Prikler Date: Sun, 18 Apr 2021 20:31:55 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-TUG-Backscatter-control: bt4lQm5Tva3SBgCuw0EnZw X-Spam-Scanner: SpamAssassin 3.003001 X-Spam-Score-relay: -1.9 X-Scanned-By: MIMEDefang 2.74 on 129.27.10.117 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: "Guix-patches" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1618770821; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=PjaIQXZOOANHr0itrHekZ9qP2XLRWkbjFI02+8USNnc=; b=DIMx0NOVNDi9o/ITCseEiNL0syH1sveQvQSwV7LZglE23PIjSRuIgx/0BrEklgxCU7q9Mw nvKClY4NMA+sHIV37xQg+j2rPsSjb8+sGz1cbGp+4Lslseeu078nhC18E3VMNWR4HSWLCQ Phiw4hesXBlgECj1vnv9vTNLmfV7ADE7+mhJN8zfGSyaSWciX73+vm5pM0fu/BBqBZ+vz7 82wCHnWoQXcoiDk5ix16FZ8GxSDprTSjZru7VqQZDhC5439eIxceP0bc7L7Mu9zzMpCF7m ZEwOthU3NfwlpTfXqvrNMV292t5xqhayFUm9eBXs/NjyATLveCPSRFsZnv9Wqw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1618770821; a=rsa-sha256; cv=none; b=cdcANKSz4u3v7n+iXNCQkn2vCWFHsKD5nW9K5BvijNZkPPWAiJ/YoFhKTCHFYWFZxqVGcT 7aDv/rx7IxKwOGqCtLHG6uFdzcqvXe2+r9oLtQG6itvL9Sekp1MGa5yJ98eaObVnuY4w1n TlJgfxUuGrVbCqw7ST1He6mHqLSdIN5OGmtQewYMlgMcsu/O2PycRKC/N5LXQI+rvJubkV t37cN0RiA6+uHyjct7XUS7Hy9OZgD9ZXNHBJ+bK2OjctEmNr96V9lj/ehQSornJnZFOmVF FauzPR5iMIrY5dfST8hk4HLr1E0nSklgv7w5xNLkbZkW2nNE+VyiEagoXUdyTg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=tugraz.at header.s=mailrelay header.b=DQfsRkpr; dmarc=fail reason="SPF not aligned (relaxed)" header.from=student.tugraz.at (policy=none); spf=pass (aspmx1.migadu.com: domain of guix-patches-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-patches-bounces@gnu.org X-Migadu-Spam-Score: -1.34 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=tugraz.at header.s=mailrelay header.b=DQfsRkpr; dmarc=fail reason="SPF not aligned (relaxed)" header.from=student.tugraz.at (policy=none); spf=pass (aspmx1.migadu.com: domain of guix-patches-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-patches-bounces@gnu.org X-Migadu-Queue-Id: D7F3819D2C X-Spam-Score: -1.34 X-Migadu-Scanner: scn0.migadu.com X-TUID: v8Nl6tMrN0Zh Hi jgart, Am Sonntag, den 18.04.2021, 17:25 +0000 schrieb jgart: > Hi Leo, > > > I know you mean this somewhat jokingly, but is there anything > > (apart > > maybe from the name of the binary), that would keep you from > > reusing > > murmur-service-type? > > See here: > > https://github.com/mumble-voip/grumble/issues/21 > https://github.com/mumble-voip/grumble/pull/26 > > There are more sources related to the grumble config that's currently > implemented that I can't locate at the moment. > > I remember reading that they didn't necessarily want to maintain > feature parity with the grumble config format. That's… disappointing. > > 1. Is this package in its current state usable? > > I would say yes. We packaged grumble while talking over grumble. It > feels pretty solid. > > Grumble also has an active fork as a library and being used by wahay: > https://wahay.org/ > > It is currently 16 commits ahead of upstream: > > https://github.com/digitalautonomy/grumble This doesn't really look active to me either. It appears as though they diverged at some point and simultaneously came to a halt. Now wahay is still active, but that's a different beast. > > 2. Is it still maintained upstream? It is a little stretch to say > > Grumble is undergoing active development after a year of no > > activity. > > It sounds like the project maintainers of the upstream grumble > project are very slow to review pull requests. It sounds like they > are too busy with other projects/work. > > See the complaint here by one of the contributors that chimed in when > I opened an issue: > > https://github.com/mumble-voip/grumble/issues/76 I take that as a "Maybe, but actually no". > > 3. https://github.com/mumble-voip/grumble#project-statuslists quite > > a > > few features that are lacking, but does it maybe contain features, > > that > > would make it worth packaging? > > See https://github.com/mumble-voip/grumble/issues/76 > > "... Grumble has the distinguishing feature of native support for > Websockets (because I was a lot worse at C++ back then and so I > contributed a patch here instead), and Murmur will probably not have > that for the foreseeable future. You could of course just configure a > proxy in front of Murmur if you need this. A lot of the plans for > work we were making a few years ago pointed towards Grumble being > more focused on ease-of-use and these small workloads I talked about > above. It makes sense: the Murmur static binary has issues and so a > Grumble static (just how Go works) binary that you can download and > run, trivially configure and easily negotiate certs over LE > (unfortunately never happened due to LE issues, but it would be > viable now), accessible over the Web could fulfil a sort of > "batteries-included" user-friendly niche." W.r.t. ease-of-use I don't think it should be too difficult to get murmur + certbot working in Guix. All I can recall from the Debian (yeah, I know) server, that I currently run murmur on, is that you need to get your hook for restarting murmur right. > > If the answer is "no" to any of the above, I'm not too sure whether > > it > > would be wise to have this in Guix upstream. If LibreMiami wanted > > to > > host grumble instances on Guix regardless, perhaps a channel might > > be a > > better fit? > > We can put this in a LibreMiami channel with a service for it if you > insist it not be included in upstream guix. It is not so much me insisting rather than me thinking, that channels fit such "niche" uses better. As far as I can tell, Guix tries to make system services as secure as possible and having a service with glaring security flaws is not really a good fit in that scenario. See also the recent removal of mongodb. > If upstream grumble picks up development then I can send a patch > again for review. Please do so. > That said, can you take the patch for go-github-com-gorilla- > websocket? > > We will need go-github-com-gorilla-websocket for many other packages > that we're working on. One of them being the hugo static site > generator that we're working on with Ryan Prior. While the package description itself LGTM, the patch inadvertently version bumps some Go protobuf package. If it's okay with you and Ryan, I think the better solution would be to send a clean patch along with hugo or perhaps separately. > Relatedly, we're planning on packaging wahay (https://wahay.org/). > > wahay depends on the fork of grumble that I linked above. > > Should we package only the fork of grumble in that case and not > upstream grumble? Again, since wahay has no public release and LibreMiami might want to tail upstream, I think that this would be a better fit outside of Guix. As for the differences in their versions of grumble, I honestly don't know what to do. Guix usually tries not to vendor packages and this might mean using upstream grumble for wahay, but the grumble fork might also implement features, that are necessary for wahay. This is just my personal opinion, but right now Guix seems to have about 70 "no release" comments, some of which are actually "no release since". I don't think there's a reason to bump this number unless the developer has a good reason not to assign version numbers (other than "it's not ready yet", which is a perfect reason not to assign version numbers, but also a perfect reason to refrain from packaging it), which does not seem to hold here. Regards, Leo