Hi,
I was mostly VAC while the discussion was going on, and I think I
missed the discussion. Andreas, do you have a good patch that I can
apply, or do I need to think through to get my way around it ?
The following patch I digged up from the past logs should probably be
revised ?
--- /usr/bin/d-devlibdeps 2008-02-28 00:32:40.000000000 +0100
+++ d-devlibdeps 2008-04-18 18:55:15.000000000 +0200
@@ -102,7 +102,7 @@
-e 's/libatk-1.0-0-dev/libatk1.0-dev/' \
-e 's/libxml2-2-dev/libxml2-dev/' \
-e 's/libgthread-2.0-0-dev/libglib2.0-dev/' \
- -e 's/libstdc++6-dev/libstdc++6-4.1-dev/' \
+ -e 's/libstdc++6-dev/libstdc++6-4.2-dev/' \
"[EMAIL PROTECTED]/#/-e}" \
At Mon, 3 Nov 2008 08:46:18 +0100 (CET),
Andreas Tille wrote:
>
> Hi,
>
> I would like to come back to the hardcoded libstdc++6-4.1-dev issue:
> I *really* regard this as an important problem which might even
> influence the Lenny release. I'm just hesitant to increase the severity
> because I'm a little bit unsure. Junichi, could you please comment
> on this?
>
> Kind regards
>
> Andreas.
>
> --
> http://fam-tille.de
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
