From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id yDJfBZGEvV7tKgAA0tVLHw (envelope-from ) for ; Thu, 14 May 2020 17:49:05 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id WEdhO5CEvV7SQwAA1q6Kng (envelope-from ) for ; Thu, 14 May 2020 17:49:04 +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 B351E940418 for ; Thu, 14 May 2020 17:49:04 +0000 (UTC) Received: from localhost ([::1]:60604 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jZHyh-0002Ma-Nm for larch@yhetil.org; Thu, 14 May 2020 13:49:03 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43664) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jZHyZ-0002MH-9v for guix-devel@gnu.org; Thu, 14 May 2020 13:48:55 -0400 Received: from mail-vs1-xe31.google.com ([2607:f8b0:4864:20::e31]:35094) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jZHyY-0002Xb-DB for guix-devel@gnu.org; Thu, 14 May 2020 13:48:55 -0400 Received: by mail-vs1-xe31.google.com with SMTP id 62so2525333vsi.2 for ; Thu, 14 May 2020 10:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mmLc+lSQ3Sp3wC31HIw9cwffqM2RNgxWr+6XdkDoPd0=; b=BnH0ZwGCODJB5qHox9mv4K76Wz8vAjkHrjuh3Na3v6DRm7UXV51iBldnSzK5Ep+nwr QFe7HB/qts6p3lrsIyrM7KkUUcTWz1DlZkvNtq3qA/YA3NbYD/eMlPBx1qiJOxqZ3gmB 9iv4plw2wCen8Yd819sYqxA/qTwFKAwREytdZ7U/Lv7QYhzEr7YzL6t5DvRV1pAW+3II RxUJ3Z1mLsN3JWcxGy5ThFQXYLgMvn9vnuJytFyhnem6cbj9ZYrph/MCkemIDDUmrctD KiH7z32WCrQG1ywN4jP0bGV5TmppAGIh3PgeR9OQBZRG1orXjlqbwcCHJlxwpP5W/WmZ mQzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mmLc+lSQ3Sp3wC31HIw9cwffqM2RNgxWr+6XdkDoPd0=; b=qbTrv6DSXqbq+/74i2EDbJ/RyXLD0F5fDtCXDxzhCCNikGIl244wOwErDz0WEsLcrF DSS9Q0oML9EgQazv92vbEWdXjdFQeli5n6UPw4GjQkpXjeNDcFsL7UYUZXfxzK++e4D1 piHVabl+fjJ0f0p5TD/EL4fdJ9rihGu0yQ3c0XdWmO+sRIFln/S0GDsDaOG76d5ZjdpB iHF/GKpYU4d8rN3W+h7GvQJCHAtmDiujOGtQwRyY0+c1ugdkyBECBQIoKO7ioX6G2RGb R2Lt+dFi3siPAjt2GWGoMY6FokUMO5F8pNAdubmc+anIMLqSX5HIAD4zcvY3VCCleI5Q Onew== X-Gm-Message-State: AOAM533/f8JLUvkOvJxNGTm4vsML71n/zsOKA0FwSrBNSmqZrhq91Nbr FsFWdGur9Ex+BjVW+K8iT0O0Rm9oz4HZmbPlDfvE/eOA X-Google-Smtp-Source: ABdhPJzZDWhwCPnmg6hLc3czSeuuMGo3gTfCRiilZgyt3W1tGG0s6UveoQC/L6L0RfGQSnzm0fHfTk+/LSGgNUVJFt4= X-Received: by 2002:a05:6102:3025:: with SMTP id v5mr4603389vsa.16.1589478532925; Thu, 14 May 2020 10:48:52 -0700 (PDT) MIME-Version: 1.0 References: <87d077nd1z.fsf@cbaines.net> In-Reply-To: <87d077nd1z.fsf@cbaines.net> From: Josh Marshall Date: Thu, 14 May 2020 13:48:40 -0400 Message-ID: Subject: Re: Where is the packaging request backlog To: Christopher Baines Content-Type: multipart/alternative; boundary="000000000000554bd405a59f4fa3" Received-SPF: pass client-ip=2607:f8b0:4864:20::e31; envelope-from=joshua.r.marshall.1991@gmail.com; helo=mail-vs1-xe31.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=BnH0ZwGC; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -0.21 X-TUID: ltT66Gg/BZcx --000000000000554bd405a59f4fa3 Content-Type: text/plain; charset="UTF-8" If that is an appropriate use, I'll go with that. Prepare for a few hundred reports. On Thu, May 14, 2020, 04:19 Christopher Baines wrote: > > Josh Marshall writes: > > > I'm trying to package watchman and have been poking at it for some weeks. > > Things are getting a little large and more dependent packages are needed. > > And this is still a spin off from me trying to update django which will > > cause another huge backlog of package updates and additions. I'd like > some > > more official way to track what code needs packaging and in what order. > Is > > there something for this? > > I sympathise, both with the rabbit hole you're going down, but also the > issue around tracking all the work and interdependencies. > > My personal advice would be to file some bugs on debbugs.gnu.org against > the guix-patches package, which is the approach for tracking patch > submissions. Even if you don't have a patch to send yet, but are working > on one, it still might be useful to have a bug open, as that indicates > to others that there might be a patch available soon. > > You can mark bugs as "More information needed", which I've been using at > least to categorise bugs that lack a patch, or where the patch won't be > ready to merge for a little while. You can also mark one bug as blocking > another. > > I'm also personally interested in getting Django 2 and 3 in to Guix, so > let me know how that's going :) > > Thanks, > > Chris > --000000000000554bd405a59f4fa3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If that is an appropriate use, I'll go with that.=C2= =A0 Prepare for a few hundred reports.

=
On Thu, May 14, 2020, 04:19 Christoph= er Baines <mail@cbaines.net> = wrote:

Josh Marshall <joshua.r.marshall.1991@gmail.com> wr= ites:

> I'm trying to package watchman and have been poking at it for some= weeks.
> Things are getting a little large and more dependent packages are need= ed.
> And this is still a spin off from me trying to update django which wil= l
> cause another huge backlog of package updates and additions.=C2=A0 I&#= 39;d like some
> more official way to track what code needs packaging and in what order= .=C2=A0 Is
> there something for this?

I sympathise, both with the rabbit hole you're going down, but also the=
issue around tracking all the work and interdependencies.

My personal advice would be to file some bugs on debbugs.gnu.org against
the guix-patches package, which is the approach for tracking patch
submissions. Even if you don't have a patch to send yet, but are workin= g
on one, it still might be useful to have a bug open, as that indicates
to others that there might be a patch available soon.

You can mark bugs as "More information needed", which I've be= en using at
least to categorise bugs that lack a patch, or where the patch won't be=
ready to merge for a little while. You can also mark one bug as blocking another.

I'm also personally interested in getting Django 2 and 3 in to Guix, so=
let me know how that's going :)

Thanks,

Chris
--000000000000554bd405a59f4fa3--