unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: dian_cecht@zoho.com
Cc: guix-devel@gnu.org
Subject: Re: bug#25356: livestreamer no longer supported
Date: Wed, 04 Jan 2017 18:50:14 +0000	[thread overview]
Message-ID: <87mvf6u0bd.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170104160538.GA10030@khaalida>

dian_cecht@zoho.com writes:

> I just wanted to point out that livestreamer seems to be entirely dead and the
> project has been forked. As of this bugreport, the last change was Febuary 2nd,
> 2016, and while this isn't exactly a long time, considering it no longer works
> properly with Twitch.tv (one of, if not the, largest streaming site atm afaik),
> gives the impression that it is a dead project.
>
> The fork is named streamlink and is located at https://streamlink.github.io/ and
> seems to work well.
>
> I'm not sure who is maintaining the livestreamer package, so I'm simply filing
> this as a bug here and hope everything is forwarded nicely.

Thanks!

Do I read this correctly that they include some kind of
anti-military license in there? I mean I am very much welcoming
such an exclusion but with all the past discussions I had it lead
to the point where it is not compatible with free software.

Do we have to strip OCB from the source?
https://github.com/Legrandin/pycryptodome/blob/master/LICENSE.rst

Pycryptodome is a dependency of streamlink.

-- 
♥Ⓐ  ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org

       reply	other threads:[~2017-01-04 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170104160538.GA10030@khaalida>
2017-01-04 18:50 ` ng0 [this message]
2017-01-04 20:28   ` bug#25356: livestreamer no longer supported Leo Famulari
2017-04-28 15:18     ` ng0
2018-01-30  6:47       ` Ricardo Wurmus

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=87mvf6u0bd.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@libertad.pw \
    --cc=dian_cecht@zoho.com \
    --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).