From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] splashutils needs a maintainer
Date: Sun, 27 Jan 2013 23:06:35 +0100 [thread overview]
Message-ID: <1359324395.2927.43.camel@belkin4> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
With spock retirement, splashutils became orphan. The problem is that it
has a lot of unresolved bugs for a long time:
https://bugs.gentoo.org/buglist.cgi?quicksearch=splashutils&list_id=1521218
that would need someone with more knowledge about it to maintain it (as
I don't have splash on my systems for years).
Also looks like splashutils is no more developed, but I don't know if we
have a proper replacement for it in gentoo (most distributions are
moving to plymouth, but I haven't tried if it works ok on Gentoo)
Thanks for your help
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2013-01-27 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 22:06 Pacho Ramos [this message]
2013-01-27 23:25 ` [gentoo-dev] splashutils needs a maintainer Alex Legler
2013-01-28 19:26 ` Pacho Ramos
2013-01-28 21:41 ` Fabio Erculiani
2013-01-29 11:55 ` Sergey Popov
2013-02-02 19:19 ` Pacho Ramos
2013-02-02 19:24 ` Dustin C. Hatch
2013-02-03 0:05 ` Albert Hopkins
2013-01-29 8:05 ` Alexey Shvetsov
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=1359324395.2927.43.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox