all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ngillmann@runbox.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH][WIP] gnu: Add debbugs.
Date: Fri, 30 Sep 2016 17:53:33 +0000	[thread overview]
Message-ID: <87k2dtl1eq.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87vaxdl5yi.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> ng0 <ngillmann@runbox.com> skribis:
>
>> So, here's debbugs. Disclaimer: I never ran or did setup or got in any
>> way in touch with debbugs on a server.
>>
>> Input welcome to adjust. All I know is that we'll need a service to make
>> this work. I have no reasonable interest in this, so I won't go all the
>> way. I'd like to fix this package up as far as usage goes.
>> I can not test it running, but from the build/install perspective it is
>> done. There are structures in code which can be changed etc, but this
>> was done in about ~30 minutes to get some input as I thought, hey we use
>> debbugs.. why do we not have debbugs packaged already?
>
> Because nobody did it I guess.
>
> Could you send an non-WIP patch?  Since you mark it as WIP, people most
> likely don’t look at it, because there’s already so many patches to
> review.  Please take extra time to test it and resend when you think
> it’s ready to apply.
>
> Thank you!
>
> Ludo’.
>

Technically this is finished and can be applied on master. Why I can't
test it I have described in the text above the email - I have no idea
how debbugs behaves, what is  expected etc.. that's why I think someone
with an interest to replace debbugs on their (mostly) debian based
server with debbugs from Guix should test it.
-- 

  reply	other threads:[~2016-09-30 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 20:01 [PATCH][WIP] gnu: Add debbugs ng0
2016-09-30 16:15 ` Ludovic Courtès
2016-09-30 17:53   ` ng0 [this message]
2016-12-20 15:41     ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k2dtl1eq.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.