ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Anton Farygin <rider@basealt.ru>
To: devel@lists.altlinux.org
Subject: Re: [devel] hash collision in rpm
Date: Tue, 4 May 2021 13:32:59 +0300
Message-ID: <079b855b-b0d0-b0e6-2da3-4b31f4b4ab1f@basealt.ru> (raw)
In-Reply-To: <20210501090437.bp7fx33thclcgman@example.org>

On 01.05.2021 12:04, Alexey Gladkov wrote:
> On Sat, May 01, 2021 at 06:44:31AM +0000, ALT beekeeper wrote:
>> Package: rust-1:1.50.0-alt1
>> Status: Sisyphus/x86_64 test rebuild failed
<skip>
>> warning: hash collision: _ZN54_$LT$$LP$T10$C$T11$RP$$u20$as$u20$core..fmt..Debug$GT$3fmt17h34a8dd22db59980aE _ZN84_$LT$alloc..vec..Vec$LT$T$C$A$GT$$u20$as$u20$alloc..vec..SpecExtend$LT$T$C$I$GT$$GT$11spec_extend17h60ca674df9219823E
>> warning: hash collision: _ZN3syn5parse11ParseBuffer4peek17hf9a11eea8c9a3d3fE _ZN4core5slice5index74_$LT$impl$u20$core..ops..index..Index$LT$I$GT$$u20$for$u20$$u5b$T$u5d$$GT$5index17h5a12cf41c79d168fE
>> warning: hash collision: _ZN4core3ptr13drop_in_place17he21b3c2d21e2e2c1E _ZN4core4iter6traits12double_ended19DoubleEndedIterator15advance_back_by17hefd6f0c285c16047E
> Меня немного настораживает такое обилие предупреждений о коллизии. Как бы
> не было беды, когда кто-то решит собрать модули rust отдельно.
>
Я тоже с таким же столкнулся в новом пакете с библиотеками для C++:

warning: hash collision: _ZN23IGESData_IGESReaderData12AddStartLineEPKc 
_ZNK14IGESSolid_Loop4EdgeEi

и там такого довольно много.




  reply	other threads:[~2021-05-04 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  9:04 ` [devel] rust-1:1.50.0-alt1: Sisyphus/x86_64 test rebuild failed Alexey Gladkov
2021-05-04 10:32   ` Anton Farygin [this message]
2021-05-04 10:45     ` [devel] hash collision in rpm Alexey Gladkov
2021-05-04 12:50       ` Alexey Tourbin
2021-05-05  5:40         ` Alexey Tourbin
2021-05-05 13:10           ` Dmitry V. Levin
2021-05-05 14:11           ` Vladimir D. Seleznev

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=079b855b-b0d0-b0e6-2da3-4b31f4b4ab1f@basealt.ru \
    --to=rider@basealt.ru \
    --cc=devel@lists.altlinux.org \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git