From: Roland Hieber <r.hieber@pengutronix.de>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] fbv package removed
Date: Fri, 5 Oct 2018 12:22:10 +0200 [thread overview]
Message-ID: <20181005102210.7yacqby46g2xq25r@pengutronix.de> (raw)
In-Reply-To: <CABDcava2n_i+br8dgj264f=BQ9Wt5L9Dmpxu2UJemabwFWhcEA@mail.gmail.com>
On Fri, Oct 05, 2018 at 12:17:45PM +0200, Guillermo Rodriguez Garcia wrote:
> Hi all,
>
> I just noticed that the fbv package has been removed after one year in
> staging. I am using this on several BSPs and didn't realize it had
> been moved to staging. The reasons for removal are:
>
> "Old and obsolete, upstream gone. Fails to build with current libpng."
>
> However, the libpng problem had already been addressed in this patch:
> https://git.pengutronix.de/cgit/ptxdist/commit?id=4a0738ec264fcbf809863dd245aff012bee274e6
>
> Also, upstream is alive: http://s-tech.elsat.net.pl/fbv/
>
> Given the above, can we revert this and move this out of staging
> again? Should I send this as a patch?
Yes, and yes. The only point of the staging area is to be a pool for
packages that don't build anymore and for which nobody seems to care. If
both those reasons are taken care of, no problem :)
- Roland
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-10-05 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 10:17 Guillermo Rodriguez Garcia
2018-10-05 10:22 ` Roland Hieber [this message]
2018-10-05 10:26 ` Guillermo Rodriguez Garcia
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=20181005102210.7yacqby46g2xq25r@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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