From: ng0 <ngillmann@runbox.com>
To: 18742@debbugs.gnu.org
Cc: guix-devel@gnu.org
Subject: bug#18742: bug #18742
Date: Fri, 30 Sep 2016 14:52:42 +0000 [thread overview]
Message-ID: <87h98xv3r9.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <877f9xjj9l.fsf@we.make.ritual.n0.is>
ng0 <ngillmann@runbox.com> writes:
> Leo Famulari <leo@famulari.name> writes:
>
> > However you are replying to these bug reports is changing the "Subject"
> > line to only include the bug number. It's hard to know what the bug is
> > about...
>
> I did not want to reply directly to these specific bugs, which is why I
> asked on this list first.
>
> > On Tue, Sep 27, 2016 at 04:38:03PM +0000, ng0 wrote:
> > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18742
> > >
> > > Logs are gone since hydra got reset at least once since October 2014. I
> > [ 2 more citation lines. Click/Enter to show. ]
> > > can not see but only assume that the tests I am currently helping to fix
> > > are different tests than the ones which failed in 2014, as the test
> > > suite for GNUnet was refactored.
> > > Can we close this bug or should I reference this bug in an update commit
> > > if/when the test suite is fixed for Guix builds?
>
> > It seems to be building or not building (depending on the architecture)
> > consistently. If you are happy with those results, please close the bug
> > :)
>
> I think I can not do this, close bugs I did not create myself. If I am
> wrong about this I advise that we write a short appendum for Guix
> documentation (part: contributing, new subsection: reporting bugs) which
> explains debbugs usage, because upstream or at least the version+online
> handbook on gnu.org is simply terrible in getting to the point.
>
>
> > https://hydra.gnu.org/search?query=gnunet
>
> Dependencies fail on architecture I do not have available (yet / in a
> forseeable future).
Related to this: what are affordable, powerful (should at least be able
to bootstrap any X11 based system) hardware systems for arm and mips
where people build Guix on?
> I think I'm okay with referencing this bug when/if I can close the
> current failing test suite bug.
> --
> ng0
>
>
--
prev parent reply other threads:[~2016-09-30 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y42djo2c.fsf@we.make.ritual.n0.is>
[not found] ` <20160927175823.GF2569@jasmine>
2016-09-27 18:21 ` bug#18742: bug #18742 ng0
[not found] ` <877f9xjj9l.fsf@we.make.ritual.n0.is>
2016-09-30 14:52 ` ng0 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h98xv3r9.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=18742@debbugs.gnu.org \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).