Hello,

I started to get delivery failures like below when posting to
linaro-dev@ , while having other recipients in to: or cc: too. It seems
ok if I post/forward directly (and only) to linaro-dev@. Can you please
look into this?


Thanks,
Paul



Begin forwarded message:

Date: Fri, 22 Jul 2011 13:57:52 +0000
From: Mail Delivery Subsystem <mailer-dae...@googlemail.com>
To: paul.sokolov...@linaro.org
Subject: Delivery Status Notification (Failure)


Delivery to the following recipient failed permanently:

     linaro-dev@lists.linaro.org

Technical details of permanent failure: 
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 550 550 Message headers fail syntax check
(state 18).

----- Original message -----

Received: by 10.204.15.4 with SMTP id i4mr470780bka.320.1311343071796;
        Fri, 22 Jul 2011 06:57:51 -0700 (PDT)
Return-Path: <paul.sokolov...@linaro.org>
Received: from x34f ([95.15.169.226])
        by mx.google.com with ESMTPS id
g11sm527663bku.49.2011.07.22.06.57.49 (version=SSLv3 cipher=OTHER);
        Fri, 22 Jul 2011 06:57:51 -0700 (PDT)
Date: Fri, 22 Jul 2011 16:57:42 +0300
From: Paul Sokolovsky <paul.sokolov...@linaro.org>
To: linaro-andr...@linaro.org <linaro-andr...@linaro.org>,
 linaro-dev@lists.linaro.org, James Westby <james.wes...@linaro.org>,
Zach Pfeffer <zach.pfef...@linaro.org>
Subject: Linaro Android Manifest changes
Message-ID: <20110722165742.2b01c707@x34f>
Organization: Linaro
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.22.0; i486-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hello,

There have been few changes regarding manifests for Linaro Android,
which may need some actions from anybody who builds or develops Linaro
Android.

1. For compatibility with upstream, manifest git repository was renamed
to git://git.linaro.org/android/platform/manifest.git (previously it
was in plural, manifests.git). This is probably the most visible
changing, coping with which will require fresh checkout of Linaro
Android (unless you're brave enough to edit repo's/git's internal
structures and config; in which case you probably know how to do that,
there're no instructions and it's not officially supported). To
alleviate migration headaches during release time, there's still
symlink to make manifests.git work, so you're welcome to schedule
re-checkout at your convenience, the link will stay for a couple of
weeks. Otherwise, the docs throughout the wiki were updated, and builds
are being migrated. https://wiki.linaro.org/Platform/Android/GetSource
has complete instructions or checking out Linaro Android.

2. To further facilitate compatibility with upstream, and support
Gerrit patch uploading, the Linaro remote in manifests were split in
two independent ones, one referring to Android components (having
android/ path prefix) and another to any component outside of android/
subtree. This is more transparent change, and it might be picked up by
"repo sync". Note that only manifests in "linaro_android_2.3.4" were
converted, in particular pinned manifests in
"linaro-android-11.07-release" were not. It would be nice if Android
team replaced manifests in linaro-android-11.07-release with split
ones, but it's up to them to decide if it's worth doing this before
2011.07 release.

3. Gerrit Review server, http://android.git.linaro.org/ were set for
linaro-android upstream in the manifests, which together with the
changes above will allow to use "repo upload" command to post
developers' change for review to Gerrit in seamless manner.



Please note that these are just incremental changes, with more coming


-- 
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to