From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libxml2
Date: Thu, 28 Aug 2008 13:37:01 +0200 [thread overview]
Message-ID: <20080828113701.GB4725@mx.loc> (raw)
In-Reply-To: <20080828105639.73E743C7AB@busybox.net>
On Thu, Aug 28, 2008 at 03:56:39AM -0700, laird at uclibc.org wrote:
>Author: laird
>Date: 2008-08-28 03:56:38 -0700 (Thu, 28 Aug 2008)
>New Revision: 23274
>
>Log:
>libxml2: Post process xml2-config file to actually work and bump version
>
>Version bumped to 2.6.31
>(2.6.32 has .rej files so patch target fails - upstream need to be informed).
Yes, please inform upstream. But such packaging issues are no excuse to
exclude that particular release.
I'm pretty sure that there is at least one other package that is also
shipped with .rej (which were apparently resolved properly) where we rm
-f $(FOO_DIR)/the/inappropriately_packaged.rej
Please consider doing the same for libxml2.
TIA,
next prev parent reply other threads:[~2008-08-28 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 10:56 [Buildroot] svn commit: trunk/buildroot/package/libxml2 laird at uclibc.org
2008-08-28 11:37 ` Bernhard Reutner-Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-27 15:02 jacmet at uclibc.org
2008-10-10 14:41 laird at uclibc.org
2008-08-24 7:48 jacmet at uclibc.org
2008-08-23 13:08 jacmet at uclibc.org
2008-08-23 13:08 jacmet at uclibc.org
2008-08-23 13:08 jacmet at uclibc.org
2008-08-23 13:08 jacmet at uclibc.org
2008-06-30 13:16 jacmet at uclibc.org
2008-06-20 21:45 jacmet at uclibc.org
2008-03-06 18:16 ninevoltz at uclibc.org
2008-03-07 0:09 ` Ulf Samuelsson
2007-09-23 14:23 ulf at uclibc.org
2007-08-19 20:59 ulf at uclibc.org
2007-08-07 17:28 ulf at uclibc.org
2007-07-24 14:12 ulf at uclibc.org
2007-07-17 15:17 ulf at uclibc.org
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=20080828113701.GB4725@mx.loc \
--to=rep.dot.nop@gmail.com \
--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