public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: RE: Re: update: LCDproc 0.5.6 (2012) to 0.5.7 (2014)
Date: Mon, 09 May 2016 16:26:31 +0200	[thread overview]
Message-ID: <76a9343f2855ebac860c16a10321a179@mail01.ipfire.org> (raw)
In-Reply-To: <03f06dcd03c58c3355fc7d3c1ad62a86@email.freenet.de>

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

You have still installed the version 0.5.6 because we have not get 
feedback yet.
The new version 0.5.7 is only available in testing tree.
http://wiki.ipfire.org/en/configuration/ipfire/pakfire/testing?s[]=testing&s[]=tree

Arne


On 2016-05-09 10:39, g6094199(a)freenet.de wrote:
> Hi michael!,
> 
> when will the update hit the release? i installed 102 and at least the
> LCDd.conf has still a diff to the current lcdproc release.
> why i know this....there is an SDEC driver based display mounted in my
> watchgurad box and i had still to add it manually to the config, while
> the official release has it added already.
> 
> also:
> 
> [root(a)ipfire ~]# lcdproc -v
> LCDproc 0.5.6
> 
> so plz do update all the missing diffs, not only the drivers. just to
> not confuse users like me ;-)
> 
> BTW im happy to test, if u need somebody....
> 
> THX!
> 
> sash
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Michael Tremer
>> Gesendet: Mo. 02.05.2016 21:02
>> An: g6094199(a)freenet.de, development(a)lists.ipfire.org
>> Betreff: Re: update: LCDproc 0.5.6 (2012) to 0.5.7 (2014)
>> 
>> Have a look at the release announcement today:
>> 
>>   http://downloads.ipfire.org/release/ipfire-2.19-core101
>> 
>> -Michael
>> 
>> On Mon, 2016-05-02 at 13:51 +0200, g6094199(a)freenet.de wrote:
>> > He Guys,
>> >
>> > i'm experimenting with LCDproc and saw that the packge is quiet
> outdated. I
>> > would be nice if someone could update the current state:
>> >
>> > https://sourceforge.net/projects/lcdproc/files/lcdproc/0.5.7/ [1]
>> >
>> > mainly they added some drivers (e.g. raspberry pi related) and
> updated some
>> > others which seems interesting for us
>> >
>> >
>> > regards
>> > sash
>> >
>> >
>> > ---
>> > Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse
> mitnehmen!
>> > Rundum glücklich mit freenetMail>
>> 
>> -----Ursprüngliche Nachricht Ende-----SDEC
> 
> ---
> Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse
> mitnehmen! Rundum glücklich mit freenetMail [2]
> 
> Links:
> ------
> [1] 
> https://sourceforge.net/projects/lcdproc/files/lcdproc/0.5.7/&lt;/span>
> [2] https://email.freenet.de/mail/Uebersicht?epid=e9900000451


           reply	other threads:[~2016-05-09 14:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <03f06dcd03c58c3355fc7d3c1ad62a86@email.freenet.de>]

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=76a9343f2855ebac860c16a10321a179@mail01.ipfire.org \
    --to=arne.fitzenreiter@ipfire.org \
    --cc=development@lists.ipfire.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