From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 349] New: update libsoup to version 2.26.2
Date: Mon, 25 May 2009 09:42:54 +0000 (UTC) [thread overview]
Message-ID: <bug-349-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=349
Summary: update libsoup to version 2.26.2
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P4
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: s.neumann at raumfeld.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=347)
--> (https://bugs.busybox.net/attachment.cgi?id=347)
update version in libsoup.mk
Attached patch updates libsoup to version 2.26.2.
This is relevant for bug 303 as it allows to compile gvfs with much less
patching.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-05-25 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 9:42 bugzilla at busybox.net [this message]
2009-05-25 9:57 ` [Buildroot] [Bug 349] update libsoup to version 2.26.2 bugzilla at busybox.net
2009-06-23 10:37 ` bugzilla at busybox.net
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=bug-349-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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