Got it. At a top level the requirement is showing stuff running on real
hardware (all archs) as well as within QEMU (all archs). As far as what
is shown on what, that's another matter.

Regards,

-pja

On Tue, 2010-10-19 at 14:51 -0700, Darren Hart wrote:

On 10/19/2010 02:48 PM, Anderson, Paul wrote:

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

There has been no discussion of a QEMU demo for the media network demo.
I've tested some components with QEMU, but we aren't currently planning
on demo'ing this in QEMU.

I think Paul is talking about a different demo, one where we're just
able to boot all four qemu architectures alongside each other.

This should be possible with our release images, we just need someone to
own it and to bring a machine with it working on it (and have a backup
of the setup in case of filesystem corruption etc.).

Any volunteers?

Cheers,

Richard

On Tue, 2010-10-19 at 14:44 -0700, Hart, Darren wrote:

On 10/19/2010 09:04 AM, Zanussi, Tom wrote:

On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:

* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

I can try getting everything running on one machine too - would it make
sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
both?

Everything on One machine doesn't make a lot of sense to me, for two
reasons:

1) This is heavily network dependent, making sure the machines can find
eachother is a critical aspect of testing this.
2) Qemu does some magic with tun/tap devices, you have to configure
things to get multicast working between guests. I've tested the
mediatomb image in qemu, it works. We need to test on real hardware.
3) We don't an image that will install everything on the same machine,
and making one doesn't make a lot of sense to me.
4) Running a NAS to serve up media to itself doesn't test the networking
side of things as well.

I'd rather use 3 real devices (even if they are all emenlow or
blacksand) rather than qemu or all on one.

Yeah, it doesn't make sense as a demo per se, but for the folks who only
have one system, to get it all going. Another motivition I thought was
to have 'something' as a worst-case fallback, e.g. with all the 'moving
pieces' Dave is worried about.

Actually, it could make a little bit of sense to have a single
nas-mediatomb-xxxclient image, pointing to each other on localhost, that
could be easily tweaked in the field and swapped in/out as any one of
the components - just a thought and probably not worth it at this point.

Tom

--
Darren

Tom

On 10/19/2010 02:48 PM, Anderson, Paul wrote:

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

There has been no discussion of a QEMU demo for the media network demo. I've tested some components with QEMU, but we aren't currently planning on demo'ing this in QEMU.

--
Darren Hart
Embedded Linux Kernel

On 10/19/2010 02:12 PM, Mark Hatle wrote:

On 10/19/10 4:01 PM, Alex deVries wrote:

On 2010-10-19, at 11:40 AM, Stewart, David C wrote:

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it.

Yes, so what I need is something like:

- description
- expected behaviour
- hardware used
- how to build and install the software

... for all four boards. The sooner we have something, the sooner I can start.

Does that make sense, Darren?

Darren (or someone else can correct me.. but what I'm doing now)

Board: RouterStationPro
Purpose: NAS and boot server for other board
Features:
- Contains file server for multimedia and other files
- Can serve files via:
- NFS
- http

http isn't needed. (the DLNA server will mount the files over NFS into its filesystem and Mediatomb runs it's own http server on a special port to server up the files to the media renderers).

- tftp (likely needed if the other boards need to network boot)
- ftp (maybe)

No need.

- Will act as THE authoritation DHCP server for the network of boards
- no DNS on the network (is it needed?)

No DNS needed, runs over multicast, and we can specify the NFS server with a dotted quad.

Software:
- From the meta-demo, build the poky-image-nas with the machine target of the
routerstationpro (thats the goal, but there might be some custom config files
in the end.. still working on it)

Perfect. Looks good Mark.

--
Darren Hart
Embedded Linux Kernel

On 10/19/2010 02:48 PM, Anderson, Paul wrote:

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

There has been no discussion of a QEMU demo for the media network demo. I've tested some components with QEMU, but we aren't currently planning on demo'ing this in QEMU.

--
Darren Hart
Embedded Linux Kernel

On 10/19/2010 02:12 PM, Mark Hatle wrote:

On 10/19/10 4:01 PM, Alex deVries wrote:

On 2010-10-19, at 11:40 AM, Stewart, David C wrote:

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it.

Yes, so what I need is something like:

- description
- expected behaviour
- hardware used
- how to build and install the software

... for all four boards. The sooner we have something, the sooner I can start.

Does that make sense, Darren?

Darren (or someone else can correct me.. but what I'm doing now)

Board: RouterStationPro
Purpose: NAS and boot server for other board
Features:
- Contains file server for multimedia and other files
- Can serve files via:
- NFS
- http

http isn't needed. (the DLNA server will mount the files over NFS into its filesystem and Mediatomb runs it's own http server on a special port to server up the files to the media renderers).

- tftp (likely needed if the other boards need to network boot)
- ftp (maybe)

No need.

- Will act as THE authoritation DHCP server for the network of boards
- no DNS on the network (is it needed?)

No DNS needed, runs over multicast, and we can specify the NFS server with a dotted quad.

Software:
- From the meta-demo, build the poky-image-nas with the machine target of the
routerstationpro (thats the goal, but there might be some custom config files
in the end.. still working on it)

Perfect. Looks good Mark.

--
Darren Hart
Embedded Linux Kernel

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

Regards,

-pja

On 10/19/2010 09:04 AM, Zanussi, Tom wrote:

On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:

* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

I can try getting everything running on one machine too - would it make
sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
both?

Everything on One machine doesn't make a lot of sense to me, for two reasons:

1) This is heavily network dependent, making sure the machines can find eachother is a critical aspect of testing this.
2) Qemu does some magic with tun/tap devices, you have to configure things to get multicast working between guests. I've tested the mediatomb image in qemu, it works. We need to test on real hardware.
3) We don't an image that will install everything on the same machine, and making one doesn't make a lot of sense to me.
4) Running a NAS to serve up media to itself doesn't test the networking side of things as well.

I'd rather use 3 real devices (even if they are all emenlow or blacksand) rather than qemu or all on one.

--
Darren

Tom

--
Darren Hart
Embedded Linux Kernel

On Tue, 2010-10-19 at 11:04 -0500, Tom Zanussi wrote:

On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:

* demo

** Alex will put the hardware bits together, Darren to write down
the description of what needs to come together and wiki-fy it. RP
suggests that maybe getting all the pieces running on one hardware
might be a good way to try it out just in case.

I can try getting everything running on one machine too - would it make
sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
both?

I'd go with emenlow since it has working sound. We've never supported
sound under qemu.

Cheers,

Richard

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Dongxiao,

Can you take a look at this since you have worked with the gstreamer?

Thanks
Sau!

Hi all,

I've packaged Rygel, a upnp media server and renderer, to use as the
media renderer in the upnp demo. However I'm seeing a segfault at launch
and as it's getting late here I'm wondering if someone in a strategic
timezone can help debug while I cycle home and sleep.

The (ugly) recipes are in the josh/demo branch of the meta-demo
repository.

rygel --gst-debug-level=5

shows plenty of output, but nothing that jumps out to a gstreamer newb
like me. AFAICT I have all of the plugins required but it's possible we
need to add more.

If not I'll pick it up again in the morning.

Thanks,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre

On 10/19/10 4:01 PM, Alex deVries wrote:

On 2010-10-19, at 11:40 AM, Stewart, David C wrote:

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it.

Yes, so what I need is something like:

- description
- expected behaviour
- hardware used
- how to build and install the software

... for all four boards. The sooner we have something, the sooner I can start.

Does that make sense, Darren?

Darren (or someone else can correct me.. but what I'm doing now)

Board: RouterStationPro
Purpose: NAS and boot server for other board
Features:
- Contains file server for multimedia and other files
- Can serve files via:
- NFS
- http
- tftp (likely needed if the other boards need to network boot)
- ftp (maybe)
- Will act as THE authoritation DHCP server for the network of boards
- no DNS on the network (is it needed?)

Software:
- From the meta-demo, build the poky-image-nas with the machine target of the routerstationpro (thats the goal, but there might be some custom config files in the end.. still working on it)

- A

On 2010-10-19, at 11:40 AM, Stewart, David C wrote:

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it.

Yes, so what I need is something like:

- description
- expected behaviour
- hardware used
- how to build and install the software

... for all four boards. The sooner we have something, the sooner I can start.

Does that make sense, Darren?

- A


--
Alex deVries
Chief Linux Technologist
Wind River Systems

On Tue, 2010-10-19 at 22:26 +0800, ke.yu@... wrote:

meta/recipes-core/busybox/busybox.inc | 13 +++-
meta/recipes-core/busybox/busybox_1.16.2.bb | 2
meta/recipes-extended/sysklogd/files/syslog.conf | 70 +++++++++++++++++++++++
meta/recipes-extended/sysklogd/sysklogd.inc | 3
meta/recipes-extended/sysklogd/sysklogd_1.5.bb | 2
5 files changed, 86 insertions(+), 4 deletions(-)

Yu Ke (1):
sysklogd: correct the syslog link and conf file

Pull URL: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/bug482

Merged into master, thanks.

Richard

On Tue, 2010-10-19 at 13:55 +0100, Richard Purdie wrote:

I've pushed some more invasive changes to the fetcher in the Poky master
branch. I'd appreciate the teams help in finding out if these work or
not, with both existing builds and with totally fresh from scratch
builds.

If they prove not to have major issues we're likely to merge these into
the release branch as what is there is going to bite people and look
rather bad.

There were some issues that Tom and Joshua were seeing which I debugged
and found that we weren't adding in new branches in the fetching code.

I was able to reproduce and then have added a patch to the git fetcher
which ensures these things are cloned correctly and any new branches are
created. I talked with Bruce to confirm my diagnosis and the solution.

This fix makes an awful lot of sense and explains various issues we've
been chasing for a while with the fetcher bugs so I'm very pleased to
have this fix checked in.

Could people continue to test the code and report any problems...

Thanks,

Richard

On 10-10-19 11:40 AM, Stewart, David C wrote:

Attending: davest, RP, Saul, Kevin, Jessica, Tom, Mark, Alex, Jeff, Josh

Sorry I missed without notice. I was standing outside of
the daycare providers house with an 18 month old wonder
where everyone was at 11:00 am this morning :(

Bruce

Exec Summary:
EIGHT DAYS TO LAUNCH.
RC3 testing is going, will be finished on time for Oct 22
Readiness review on Oct 21, Saul will set up
The Fetcher is showing serious problems, this needs to be addressed for release. Richard will update daily on this.

You all have items to complete below, please follow up


ARs:
AR: Saul - set up readiness review
AR: Darren - demo use case notes to ScottR
AR: Kevin - do we need to retain the WR copyrights on the kernel doc? or can we rebrand as LF?
AR: Saul - ask Nitin to investigate delta with the MeeGo toolchain
AR: Dave to send CB, boards, panels, etc to Tom
AR: Bruce to take the recipes, bring up the 4 arch demo and train Alex on them
AR: MarkH - Package summary doc to ScottR
AR: Jessica - work on getting Eclipse plug-in download location set up with ScottR

Giveaway:


Sprint B (Due: Oct 01, Midnight PDT)


* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

** create and document on Yocto Linux website the use cases

** NAS: NFS (Mark)
Will do by end of his day today. This will run on MIPS RouterStation Pro
Mark will bring this board and drive to Cambridge

** DNLA Server (Darren)

** UPnP Renderer (Josh)
Will test with real hardware because audio on qemux86 isn't working

* autobuilder runtime testing of images (ScottG)
Will defer this change until release bits are safely out the door


Sprint C (Due: Oct 8, Midnight PDT)

* Go through each of the recipe file summary info and make sure they are there and correct, load all into a spreadsheet (Distro team) tech writer correct them and send them back (MarkH, Bug 281)
Tech writer info pending, may move to 1.0

* add class for rpmbuild (JeffP)
WIP

* ldat compatibility
** importing packages from LDAT (JeffP)
WIP

* determine way to distribute SDK (Jessica)
Done, waiting for the build to push it.

* setup and test RPM feed (Saul)
done


Sprint D (Due: Oct 15 (note: Thursday), Midnight PDT)

** shrink kernel repo size (Bruce)

* demo
** kit up boards for give away (Dave/Saul)

** ensure sato desktop runs on ppc real h/w (Bruce)

* qemu ppc graphics (Bruce)

On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:

* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

I can try getting everything running on one machine too - would it make
sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
both?

Tom

Attending: davest, RP, Saul, Kevin, Jessica, Tom, Mark, Alex, Jeff, Josh

Exec Summary:
EIGHT DAYS TO LAUNCH.
RC3 testing is going, will be finished on time for Oct 22
Readiness review on Oct 21, Saul will set up
The Fetcher is showing serious problems, this needs to be addressed for release. Richard will update daily on this.

You all have items to complete below, please follow up


ARs:
AR: Saul - set up readiness review
AR: Darren - demo use case notes to ScottR
AR: Kevin - do we need to retain the WR copyrights on the kernel doc? or can we rebrand as LF?
AR: Saul - ask Nitin to investigate delta with the MeeGo toolchain
AR: Dave to send CB, boards, panels, etc to Tom
AR: Bruce to take the recipes, bring up the 4 arch demo and train Alex on them
AR: MarkH - Package summary doc to ScottR
AR: Jessica - work on getting Eclipse plug-in download location set up with ScottR

Giveaway:


Sprint B (Due: Oct 01, Midnight PDT)


* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

** create and document on Yocto Linux website the use cases

** NAS: NFS (Mark)
Will do by end of his day today. This will run on MIPS RouterStation Pro
Mark will bring this board and drive to Cambridge

** DNLA Server (Darren)

** UPnP Renderer (Josh)
Will test with real hardware because audio on qemux86 isn't working

* autobuilder runtime testing of images (ScottG)
Will defer this change until release bits are safely out the door


Sprint C (Due: Oct 8, Midnight PDT)

* Go through each of the recipe file summary info and make sure they are there and correct, load all into a spreadsheet (Distro team) tech writer correct them and send them back (MarkH, Bug 281)
Tech writer info pending, may move to 1.0

* add class for rpmbuild (JeffP)
WIP

* ldat compatibility
** importing packages from LDAT (JeffP)
WIP

* determine way to distribute SDK (Jessica)
Done, waiting for the build to push it.

* setup and test RPM feed (Saul)
done


Sprint D (Due: Oct 15 (note: Thursday), Midnight PDT)

** shrink kernel repo size (Bruce)

* demo
** kit up boards for give away (Dave/Saul)

** ensure sato desktop runs on ppc real h/w (Bruce)

* qemu ppc graphics (Bruce)

From: Yu Ke <ke.yu@...>

This commit fix [BUGID #482]

Two issues cause bug 482:
- firsty, there are two version of syslog: sysklogd and busybox.
the busybox one is directly installed as /etc/init.d/syslog,
and the sysklogd one is installed by update-alternative. the
update-alternative will thus fail because the /etc/init.d/syslog
(busybox one) already exist and not a link. so the correct way
is to install busybox one by update-alternative, the layout will be:
/etc/init.d/syslog.busybox
/etc/init.d/syslog.sysklogd
/etc/init.d/syslog -> syslog.busybox or
/etc/init.d/syslog -> syslog.sysklogd

- secondly, sysklogd default conf is not comply with poky. Its dir /var/adm/
does not exist. Check the debian /etc/syslog.conf and find it is more
sophiscated and suitable, so port /etc/syslog.conf from debian.

Signed-off-by: Yu Ke <ke.yu@...>
---
meta/recipes-core/busybox/busybox.inc | 13 ++++-
meta/recipes-core/busybox/busybox_1.16.2.bb | 2 +-
meta/recipes-extended/sysklogd/files/syslog.conf | 70 ++++++++++++++++++++++
meta/recipes-extended/sysklogd/sysklogd.inc | 3 +-
meta/recipes-extended/sysklogd/sysklogd_1.5.bb | 2 +-
5 files changed, 86 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-extended/sysklogd/files/syslog.conf

diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
index b3c6c66..b8c009c 100644
--- a/meta/recipes-core/busybox/busybox.inc
+++ b/meta/recipes-core/busybox/busybox.inc
@@ -53,7 +53,7 @@ do_install () {
# Move back the sh symlink
test -h ${D}/busybox${base_bindir}/sh && mv ${D}/busybox${base_bindir}/sh ${D}${base_bindir}/

- install -m 0755 ${WORKDIR}/syslog ${D}${sysconfdir}/init.d/
+ install -m 0755 ${WORKDIR}/syslog ${D}${sysconfdir}/init.d/syslog.${PN}
install -m 644 ${WORKDIR}/syslog.conf ${D}${sysconfdir}/
if grep "CONFIG_CROND=y" ${WORKDIR}/defconfig; then
# Move crond back to /usr/sbin/crond
@@ -107,6 +107,8 @@ pkg_postinst_${PN} () {

# This adds the links, remember that this has to work when building an image too, hence the $D
while read link; do case "$link" in /*/*/*) to="../../bin/busybox";; /bin/*) to="busybox";; /*/*) to="../bin/busybox";; esac; bn=`basename $link`; update-alternatives --install $link $bn $to 50; done <$D/etc/busybox.links
+
+ update-alternatives --install ${sysconfdir}/init.d/syslog syslog-init syslog.${PN} 50
}

pkg_prerm_${PN} () {
@@ -138,4 +140,13 @@ pkg_prerm_${PN} () {
bn=`basename $link`
sh /usr/bin/update-alternatives --remove $bn $to
done </etc/busybox.links
+
+ # remove syslog
+ if test "x$D" = "x"; then
+ if test "$1" = "upgrade" -o "$1" = "remove"; then
+ /etc/init.d/syslog stop
+ fi
+ fi
+
+ update-alternatives --remove syslog-init syslog.${PN}
}
diff --git a/meta/recipes-core/busybox/busybox_1.16.2.bb b/meta/recipes-core/busybox/busybox_1.16.2.bb
index 0952f4d..80dbeab 100644
--- a/meta/recipes-core/busybox/busybox_1.16.2.bb
+++ b/meta/recipes-core/busybox/busybox_1.16.2.bb
@@ -1,5 +1,5 @@
require busybox.inc
-PR = "r0"
+PR = "r1"

SRC_URI = "http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \
file://udhcpscript.patch \
diff --git a/meta/recipes-extended/sysklogd/files/syslog.conf b/meta/recipes-extended/sysklogd/files/syslog.conf
new file mode 100644
index 0000000..795d735
--- /dev/null
+++ b/meta/recipes-extended/sysklogd/files/syslog.conf
@@ -0,0 +1,70 @@
+# /etc/syslog.conf Configuration file for syslogd.
+#
+# Ported from debian by Yu Ke <ke.yu@...>
+#
+
+#
+# First some standard logfiles. Log by facility.
+#
+
+auth,authpriv.* /var/log/auth.log
+*.*;auth,authpriv.none -/var/log/syslog
+#cron.* /var/log/cron.log
+daemon.* -/var/log/daemon.log
+kern.* -/var/log/kern.log
+lpr.* -/var/log/lpr.log
+mail.* -/var/log/mail.log
+user.* -/var/log/user.log
+
+#
+# Logging for the mail system. Split it up so that
+# it is easy to write scripts to parse these files.
+#
+mail.info -/var/log/mail.info
+mail.warn -/var/log/mail.warn
+mail.err /var/log/mail.err
+
+# Logging for INN news system
+#
+news.crit /var/log/news/news.crit
+news.err /var/log/news/news.err
+news.notice -/var/log/news/news.notice
+
+#
+# Some `catch-all' logfiles.
+#
+*.=debug;\
+ auth,authpriv.none;\
+ news.none;mail.none -/var/log/debug
+*.=info;*.=notice;*.=warn;\
+ auth,authpriv.none;\
+ cron,daemon.none;\
+ mail,news.none -/var/log/messages
+
+#
+# Emergencies are sent to everybody logged in.
+#
+*.emerg *
+
+#
+# I like to have messages displayed on the console, but only on a virtual
+# console I usually leave idle.
+#
+#daemon,mail.*;\
+# news.=crit;news.=err;news.=notice;\
+# *.=debug;*.=info;\
+# *.=notice;*.=warn /dev/tty8
+
+# The named pipe /dev/xconsole is for the `xconsole' utility. To use it,
+# you must invoke `xconsole' with the `-file' option:
+#
+# $ xconsole -file /dev/xconsole [...]
+#
+# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
+# busy site..
+#
+daemon.*;mail.*;\
+ news.err;\
+ *.=debug;*.=info;\
+ *.=notice;*.=warn |/dev/xconsole
+
diff --git a/meta/recipes-extended/sysklogd/sysklogd.inc b/meta/recipes-extended/sysklogd/sysklogd.inc
index 76ab707..9bd7728 100644
--- a/meta/recipes-extended/sysklogd/sysklogd.inc
+++ b/meta/recipes-extended/sysklogd/sysklogd.inc
@@ -18,6 +18,7 @@ RDEPENDS_${PN}_append = " ${@base_conditional("ONLINE_PACKAGE_MANAGEMENT", "none
SRC_URI = "http://www.infodrom.org/projects/sysklogd/download/sysklogd-${PV}.tar.gz \
file://no-strip-install.patch \
file://sysklogd \
+ file://syslog.conf \
"

INITSCRIPT_NAME = "syslog"
@@ -33,7 +34,7 @@ do_install () {
mv ${D}${base_sbindir}/syslogd ${D}${base_sbindir}/syslogd.${PN}
mv ${D}${base_sbindir}/klogd ${D}${base_sbindir}/klogd.${PN}
install -d ${D}${sysconfdir}
- install -m 644 ${S}/syslog.conf ${D}${sysconfdir}/syslog.conf
+ install -m 644 ${WORKDIR}/syslog.conf ${D}${sysconfdir}/syslog.conf
install -d ${D}${sysconfdir}/init.d
install -m 755 ${WORKDIR}/sysklogd ${D}${sysconfdir}/init.d/syslog.${PN}
}
diff --git a/meta/recipes-extended/sysklogd/sysklogd_1.5.bb b/meta/recipes-extended/sysklogd/sysklogd_1.5.bb
index 8344e27..27146c7 100644
--- a/meta/recipes-extended/sysklogd/sysklogd_1.5.bb
+++ b/meta/recipes-extended/sysklogd/sysklogd_1.5.bb
@@ -1,2 +1,2 @@
require sysklogd.inc
-PR = "r0"
+PR = "r1"
--
1.7.0.4