ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Ivan Zakharyaschev <imz@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] I: verify-elf for plugins etc. with RPM_LD_PRELOAD_xxxx & RPM_FILES_TO_LD_PRELOAD_xxxx; was: Re:  python3-3.5 unmets
Date: Sun, 18 Dec 2016 19:32:34 +0300 (MSK)
Message-ID: <alpine.LFD.2.20.1612181927140.1300@imap.altlinux.org> (raw)
In-Reply-To: <20161218160241.GN11962@imap.altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]


On Sun, 18 Dec 2016, Michael Shigorin wrote:

> On Sun, Dec 18, 2016 at 06:14:24PM +0300, Ivan Zakharyaschev wrote:
>> Для справки: сейчас не проходят строгую проверку verify-elf
>> (на unresolved symbols):
>> 
>> [imz@people success]$ cd /beehive/logs/Sisyphus-x86_64/latest/success/
>> [imz@people success]$ fgrep 'ELF verification disabled' -rl . | less
>> ./FlightGear-data-2016.1.1-alt1
>
> Объёмным данным её проходить совершенно незачем :)

А разве от объёмности данных какая-то беда. file довольно быстро скажет, 
что это не ELF, и всё.

>> ./firefox-classic_theme_restorer-1.5.6-alt1
>> ./firefox-lazarus-3.2-alt1
>> ./rocksndiamonds-emc-1:2.0.0-alt3
>> ./fortunes-fido-20070503-alt1
>> ./firefox-colorfultabs-23.8-alt1
>> ./FlightGear-tu154b-3.1-alt1
>> ./typo3_src-4.5.40-alt1
>> ./typo3-dummy-4.5.40-alt1
>> ./firefox-tree_style_tab-0.15.2014120101-alt1
>> ./gimp-help-2.6.1-alt2
>
> Этим тоже явно ни к чему.  Вычти из списка noarch.

Кажется, для всяких noarch можно просто включить (и ошибок не будет, с 
которыми пришлось бы разбираться, раз оно noarch) и больше не обращать 
внимания.

-- 
Best regards,
Ivan

  reply	other threads:[~2016-12-18 16:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 16:01 [devel] " Ivan Zakharyaschev
2016-03-02  6:40 ` Ivan Zakharyaschev
2016-03-02  7:46   ` Denis Medvedev
2016-03-02 10:01     ` Ivan Zakharyaschev
2016-03-03  6:44       ` Yuri N. Sedunov
2016-03-04 19:02       ` Ivan Zakharyaschev
2016-03-04 19:31         ` Denis Medvedev
2016-03-04 19:40           ` [devel] aiohttp native build problems; was: " Ivan Zakharyaschev
2016-03-04 20:36         ` [devel] " Ivan Zakharyaschev
2016-03-04 21:55           ` Ivan Zakharyaschev
2016-03-09  8:50         ` Ivan Zakharyaschev
2016-03-09  9:02           ` Ivan Zakharyaschev
2016-03-09  9:45             ` Ivan Zakharyaschev
2016-03-09 12:53               ` Ivan Zakharyaschev
2016-04-01 19:49           ` Ivan Zakharyaschev
2016-04-02  8:24             ` [devel] please approve python3-3.5 rebuild of pkgs; was:Re: " Ivan Zakharyaschev
2016-04-04 10:48                     ` sbolshakov
2016-04-04 11:17                           ` sbolshakov
2016-04-04 13:34                             ` Alexey Shabalin
2016-04-05 19:42                   ` sbolshakov
2016-04-05 21:19                     ` Gleb Fotengauer-Malinovskiy
2016-04-05 22:13                       ` Igor Vlasenko
2016-04-06  8:38                         ` sbolshakov
2016-04-19 16:41                     ` Ivan Zakharyaschev
2016-04-19 18:37                       ` Igor Vlasenko
2016-04-04 21:45             ` [devel] I: verify-elf for plugins etc. with RPM_LD_PRELOAD_xxxx & RPM_FILES_TO_LD_PRELOAD_xxxx; was: " Ivan Zakharyaschev
2016-04-07 20:46               ` Alexey Tourbin
2016-12-18 10:13               ` Ivan Zakharyaschev
2016-12-18 15:14                 ` Ivan Zakharyaschev
2016-12-18 16:02                   ` Michael Shigorin
2016-12-18 16:32                     ` Ivan Zakharyaschev [this message]
2016-12-19 12:25                   ` Alexey Gladkov
2016-12-19 13:28                     ` Ivan Zakharyaschev
2016-12-19 13:55                       ` Alexey Gladkov

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=alpine.LFD.2.20.1612181927140.1300@imap.altlinux.org \
    --to=imz@altlinux.org \
    --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