From: Saul Wold <sgw@linux.intel.com>
To: Zhai Edwin <edwin.zhai@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 3/9] avahi: Upgrade to 0.6.30 (from 0.6.28)
Date: Thu, 14 Apr 2011 14:14:05 -0700 [thread overview]
Message-ID: <4DA7639D.3010004@linux.intel.com> (raw)
In-Reply-To: <34aa0bc63962a57f4b819156fa824673252a559d.1302739788.git.edwin.zhai@intel.com>
On 04/13/2011 05:13 PM, Zhai Edwin wrote:
> From: Zhai Edwin<edwin.zhai@intel.com>
>
> This upgrade fix the one security issue:
> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-1002
> [YOCTO #975] fixed.
>
> This should be included in the Bernard point-release.
>
> Signed-off-by: Zhai Edwin<edwin.zhai@intel.com>
> ---
> .../avahi/{avahi_0.6.28.bb => avahi_0.6.30.bb} | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
> rename meta/recipes-connectivity/avahi/{avahi_0.6.28.bb => avahi_0.6.30.bb} (82%)
>
Since we are updating this recipe, I noticed that there is a patch and
also that the patch line has an older style (patch=1) that could be
removed. Please check into the patch and update the avahi.inc file.
Thanks
Sau!
> diff --git a/meta/recipes-connectivity/avahi/avahi_0.6.28.bb b/meta/recipes-connectivity/avahi/avahi_0.6.30.bb
> similarity index 82%
> rename from meta/recipes-connectivity/avahi/avahi_0.6.28.bb
> rename to meta/recipes-connectivity/avahi/avahi_0.6.30.bb
> index 6e034b0..1084c04 100644
> --- a/meta/recipes-connectivity/avahi/avahi_0.6.28.bb
> +++ b/meta/recipes-connectivity/avahi/avahi_0.6.30.bb
> @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=2d5025d4aa3495befef8f17206a5b0a1 \
> file://avahi-client/client.h;endline=23;md5=f4ac741a25c4f434039ba3e18c8674cf"
>
> RDEPENDS_avahi-daemon = "sysvinit-pidof"
> -PR = "r2"
> +PR = "r0"
>
> EXTRA_OECONF += "--disable-gtk3"
>
> @@ -15,5 +15,5 @@ FILES_avahi-autoipd = "${sbindir}/avahi-autoipd \
> ${sysconfdir}/avahi/avahi-autoipd.action \
> ${sysconfdir}/dhcp3/*/avahi-autoipd"
>
> -SRC_URI[md5sum] = "d0143a5aa3265019072e53ab497818d0"
> -SRC_URI[sha256sum] = "a0d80aac88212b9f9d5331c248091d3c9c9209f0e41985421636ebd14230fc91"
> +SRC_URI[md5sum] = "e4db89a2a403ff4c47d66ac66fad1f43"
> +SRC_URI[sha256sum] = "f9e4316c2339d0020726edd846d01bee0c39980906db0c247479e5807457ff1f"
next prev parent reply other threads:[~2011-04-14 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 0:13 [PATCH 0/9] [PULL] UX/X apps upgrade, edwin, Apr 13, 2011 Zhai Edwin
2011-04-14 0:13 ` [PATCH 1/9] libsoup-2.4: Upgrade to 2.32.2 (from 2.32.1) Zhai Edwin
2011-04-14 0:13 ` [PATCH 2/9] tasks: Upgrade to 0.19 (from 0.18) Zhai Edwin
2011-04-14 0:13 ` [PATCH 3/9] avahi: Upgrade to 0.6.30 (from 0.6.28) Zhai Edwin
2011-04-14 21:14 ` Saul Wold [this message]
2011-04-14 0:13 ` [PATCH 4/9] x11perf: Upgrade to 1.5.3 (from 1.5.2) Zhai Edwin
2011-04-14 0:13 ` [PATCH 5/9] libcanberry: Upgrade to 0.28 (from 0.26) Zhai Edwin
2011-04-14 0:13 ` [PATCH 6/9] xz: Upgrade to 5.0.2 (from 5.0.0) Zhai Edwin
2011-04-14 0:13 ` [PATCH 7/9] consolekit: Upgrade to 0.4.4 (from 0.4.3) Zhai Edwin
2011-04-14 0:13 ` [PATCH 8/9] polkit-gnome: Upgrade to 0.101 (from 0.99) Zhai Edwin
2011-04-14 0:13 ` [PATCH 9/9] libgpg-error: Upgrade to 1.10 (from 1.9) Zhai Edwin
2011-04-14 17:45 ` [PATCH 0/9] [PULL] UX/X apps upgrade, edwin, Apr 13, 2011 Saul Wold
2011-04-15 1:04 ` Zhai, Edwin
2011-04-18 21:49 ` Saul Wold
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=4DA7639D.3010004@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=edwin.zhai@intel.com \
--cc=poky@yoctoproject.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