unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: dian_cecht@zoho.com
Cc: 25356@debbugs.gnu.org
Subject: bug#25356: livestreamer no longer supported
Date: Thu, 25 Jan 2018 01:17:09 +0300	[thread overview]
Message-ID: <87wp06gavu.fsf@gmail.com> (raw)
In-Reply-To: <20170104160538.GA10030@khaalida> (dian cecht's message of "Wed, 4 Jan 2017 08:05:38 -0800")

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Hello,

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.

I got here from
<https://lists.gnu.org/archive/html/guix-devel/2017-04/msg00660.html>.

The streamlink package is available now from
f48feaa2848d999e100f27301680a01dc3bd7733

Should we still hold livestreamer?


Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-01-24 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 16:05 bug#25356: livestreamer no longer supported dian_cecht
2018-01-24 22:17 ` Oleg Pykhalov [this message]
2018-01-24 22:27   ` Leo Famulari
2018-01-24 23:13     ` Oleg Pykhalov
2018-01-30  5:01       ` Leo Famulari
2018-01-30  7:10         ` Oleg Pykhalov
2018-01-30 22:46           ` Leo Famulari
2018-01-31  3:41             ` Oleg Pykhalov

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=87wp06gavu.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=25356@debbugs.gnu.org \
    --cc=dian_cecht@zoho.com \
    /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).