From: "Скрылевъ Малъ" <majioa@yandex.ru>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Q: опять сломали ruby, доколе?
Date: Mon, 08 Apr 2019 23:21:20 +0300
Message-ID: <27742291554754880@iva3-64eac1bc5e68.qloud-c.yandex.net> (raw)
In-Reply-To: <20190408201550.GB13570@altlinux.org>
08.04.2019, 23:15, "Dmitry V. Levin" <ldv@altlinux.org>:
> On Mon, Apr 08, 2019 at 11:00:57PM +0300, Скрылевъ Малъ wrote:
>> 08.04.2019, 22:20, "Dmitry V. Levin" <ldv@altlinux.org>:
>> > On Mon, Apr 08, 2019 at 10:11:59PM +0300, Скрылевъ Малъ wrote:
>
> [...]
>> >> скажем эта "поломка", появился только в i586 архитектуре,
>> >
>> > Нет, ronn завершается аварийно и на x86_64, об этом стало известно по
>> > результатам тестовой пересборки на x86_64, когда пакеты libidn2-2.1.1-alt1
>> > и opennebula-5.8.1-alt1 перестали собираться.
>> >
>> нет это не так:
>> во часть лога из задачи http://git.altlinux.org/tasks/226859/build/100/x86_64/log
>>
>> ronn -r idn2.md >idn2.1
>> roff: ./idn2.1
>>
>> ошибок не наблюдается.
>
> Значит, вы не там наблюдаете.
> http://git.altlinux.org/beehive/logs/Sisyphus-x86_64/archive/2019/0408/error/libidn2-2.1.1-alt1
> http://git.altlinux.org/beehive/logs/Sisyphus-x86_64/archive/2019/0408/error/opennebula-5.8.1-alt1
>
это устаревшие сведения, с разницей более 12 часов, я вам дал ссылку на последнюю тестовую пересборку сегодня.
--
Малъ Скрылевъ
about.me/majioa
next prev parent reply other threads:[~2019-04-08 20:21 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 12:05 ` Dmitry V. Levin
2019-04-08 12:11 ` Скрылевъ Малъ
2019-04-08 12:14 ` Скрылевъ Малъ
2019-04-08 12:16 ` Dmitry V. Levin
2019-04-08 12:18 ` [devel] [JT] " Michael Shigorin
2019-04-08 12:59 ` [devel] " Скрылевъ Малъ
2019-04-08 13:24 ` Dmitry V. Levin
2019-04-08 13:29 ` Sergey Afonin
2019-04-08 13:34 ` [devel] slang Dmitry V. Levin
2019-04-08 18:32 ` Sergey Y. Afonin
2019-04-08 18:39 ` Sergey Y. Afonin
2019-04-08 18:58 ` Dmitry V. Levin
2019-04-08 19:18 ` Sergey Y. Afonin
2019-04-08 19:29 ` Dmitry V. Levin
2019-04-08 20:33 ` Sergey Y. Afonin
2019-04-08 21:02 ` Dmitry V. Levin
2019-04-09 8:01 ` Aleksei Nikiforov
2019-04-09 13:19 ` Dmitry V. Levin
2019-04-09 13:21 ` Anton Farygin
2019-04-09 14:34 ` Mikhail Efremov
2019-04-09 14:41 ` Sergey Afonin
2019-04-09 14:46 ` Sergey Afonin
2019-04-09 15:28 ` Mikhail Efremov
2019-04-09 16:25 ` Anton Farygin
2019-04-09 16:31 ` Anton Farygin
2019-04-09 17:22 ` Sergey Y. Afonin
2019-04-09 17:36 ` Dmitry V. Levin
2019-04-09 17:55 ` Sergey Y. Afonin
2019-04-09 18:02 ` Sergey Y. Afonin
2019-04-09 18:15 ` Dmitry V. Levin
2019-04-09 18:24 ` Sergey Y. Afonin
2019-04-09 18:26 ` Andrey Savchenko
2019-04-09 18:30 ` Anton Farygin
2019-04-09 18:51 ` Paul Wolneykien
2019-04-09 19:08 ` Andrey Savchenko
2019-04-09 15:21 ` Anton Farygin
2019-04-10 7:25 ` Aleksei Nikiforov
2019-04-08 18:44 ` [devel] Q: опять сломали ruby, доколе? Dmitry V. Levin
2019-04-08 19:11 ` Скрылевъ Малъ
2019-04-08 19:19 ` Anton Farygin
2019-04-08 20:14 ` Скрылевъ Малъ
2019-04-08 20:18 ` Dmitry V. Levin
2019-04-09 1:19 ` Grigory Ustinov
2019-04-09 10:45 ` Andrey Savchenko
2019-04-09 10:49 ` Andrey Cherepanov
2019-04-09 11:18 ` Andrey Savchenko
2019-04-09 11:27 ` Anton Farygin
2019-04-09 14:01 ` Michael Shigorin
2019-04-09 14:16 ` Andrey Savchenko
2019-04-09 5:23 ` Anton Farygin
2019-04-08 19:20 ` Dmitry V. Levin
2019-04-08 20:00 ` Скрылевъ Малъ
2019-04-08 20:15 ` Dmitry V. Levin
2019-04-08 20:21 ` Скрылевъ Малъ [this message]
2019-04-08 20:55 ` Dmitry V. Levin
2019-04-08 19:49 ` Alexey V. Vissarionov
2019-04-08 19:56 ` Michael Shigorin
2019-04-08 19:59 ` Aleksey Novodvorsky
2019-04-09 5:50 ` [devel] JT - выпустить пар Anton Farygin
2019-04-09 6:56 ` Andrey Cherepanov
2019-04-09 13:27 ` Dmitry V. Levin
2019-04-08 20:05 ` [devel] Q: опять сломали ruby, доколе? Dmitry V. Levin
2019-04-09 5:48 ` Anton Farygin
2019-04-09 6:10 ` Sergey Afonin
2019-04-09 6:35 ` Dmitry V. Levin
2019-04-08 12:19 ` Sergey V Turchin
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=27742291554754880@iva3-64eac1bc5e68.qloud-c.yandex.net \
--to=majioa@yandex.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