From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mike@fly.osdn.org.ua>
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on sa.int.altlinux.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham
	version=3.2.5
Date: Mon, 23 Jan 2012 14:58:44 +0200
From: Michael Shigorin <mike@osdn.org.ua>
To: devel@lists.altlinux.org
Message-ID: <20120123125844.GH792@osdn.org.ua>
Mail-Followup-To: devel@lists.altlinux.org
References: <20120123112737.GA16111@ssh.git.altlinux.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120123112737.GA16111@ssh.git.altlinux.org>
User-Agent: Mutt/1.4.2.1i
Subject: [devel] =?koi8-r?b?0NLPIM7P19nKIGlwcm91dGUyINcgdDY=?=
X-BeenThere: devel@lists.altlinux.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ALT Linux Team development discussions <devel@lists.altlinux.org>
List-Id: ALT Linux Team development discussions <devel.lists.altlinux.org>
List-Unsubscribe: <https://lists.altlinux.org/mailman/options/devel>,
	<mailto:devel-request@lists.altlinux.org?subject=unsubscribe>
List-Archive: <http://lists.altlinux.org/pipermail/devel>
List-Post: <mailto:devel@lists.altlinux.org>
List-Help: <mailto:devel-request@lists.altlinux.org?subject=help>
List-Subscribe: <https://lists.altlinux.org/mailman/listinfo/devel>,
	<mailto:devel-request@lists.altlinux.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2012 12:58:54 -0000
Archived-At: <http://lore.altlinux.org/devel/20120123125844.GH792@osdn.org.ua/>
List-Archive: <http://lore.altlinux.org/devel/>
List-Post: <mailto:devel@altlinux.org>

On Mon, Jan 23, 2012 at 03:27:37PM +0400, ALT beekeeper wrote:
> 	9 NEW error logs
> 
> collectd-5.0.1-alt3.M60T.1
> 	netlink.c: In function 'ir_read':
> 	netlink.c:574:2: error: too many arguments to function 'rtnl_dump_filter'
> 	/usr/include/libnetlink.h:40:12: note: declared here
> 	netlink.c:612:6: error: too many arguments to function 'rtnl_dump_filter'
> 	/usr/include/libnetlink.h:40:12: note: declared here

Стоило ли забрасывать слишком свежий iproute2 в t6/branch,
учитывая, что библиотеками в сизифе зацепило и сломало достаточно
много -- но там это по крайней мере нормально?

Как минимум стоит при изменении ABI одного из параллельных
бранчей (t6) координироваться с ответственным за второй (p6)
во избежание неоправданной разницы.

-- 
 ---- WBR, Michael Shigorin <mike@altlinux.ru>
  ------ Linux.Kiev http://www.linux.kiev.ua/