unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 44953@debbugs.gnu.org
Subject: bug#44953: lsof: LTlock test consistently fails (possibly due to btrfs)
Date: Sun, 29 Nov 2020 20:30:20 -0500	[thread overview]
Message-ID: <87r1obd41k.fsf@netris.org> (raw)
In-Reply-To: <874kl7zw4u.fsf@nckx>

Hi Tobias,

Thanks for the super quick response and for reproducing the bug.

> This looks like an upstream bug to me.

Agreed.

> Do you have time to file 
> one?  We're using the <https://github.com/lsof-org/lsof> upstream 
> since Victor Abell retired.

I have time, but there's another problem: it appears that I cannot file
a bug report on Github without first creating an account, which in turn
requires me to formally agree to their legal agreement.  Among other
things, it includes an indemnification clause, meaning that I would have
to promise to pay their legal fees if some dispute arises involving me
and they decide to retain laywers to deal with it.  They also claim the
right to change the terms of the agreement at any time without notifying
me, and by continuing to use the service I would implicitly agree to
those new terms.

I refuse to sign that agreement, which means that I cannot file bug
reports on Github.  Oh well.

I don't actually care about 'lsof', except for the fact that our 'gnome'
package depends on it.  For now, I'll just disable the 'lsof' test suite
on my private branch.

> Alternatively we could disable this test in Guix ‘for now’ with a
> comment--but we both know how long it will remain unfixed.

Sounds fine to me, unless someone who has already has a Github account
wants to use it to file a bug.

  Thanks again,
      Mark




  reply	other threads:[~2020-11-30  1:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 21:02 bug#44953: lsof: LTlock test consistently fails (possibly due to btrfs) Mark H Weaver
2020-11-29 21:25 ` Mark H Weaver
2020-11-29 21:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-30  1:30   ` Mark H Weaver [this message]
2020-12-05  1:57     ` raingloom
2021-10-15  4:15       ` Maxim Cournoyer
2021-10-15  9:11         ` Mark H Weaver
2021-10-15  4:29       ` Maxim Cournoyer
2022-06-09 21:23         ` Maxim Cournoyer

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=87r1obd41k.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=44953@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).