ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Ivan A. Melnikov" <iv@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Fwd: bird-1.6.4-alt1.S1: Sisyphus/x86_64 test rebuild failed
Date: Wed, 16 Jan 2019 14:41:48 +0400
Message-ID: <20190116104148.7u53ruznzl36b7pb@titan.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1901161322480.6081@imap.altlinux.org>

On Wed, Jan 16, 2019 at 01:24:15PM +0300, Ivan Zakharyaschev wrote:
> On Wed, 16 Jan 2019, Ivan A. Melnikov wrote:
> 
> > On Wed, Jan 16, 2019 at 12:56:31PM +0300, Ivan Zakharyaschev wrote:
> 
> Можно переопределить значение ubt (во всех бранчах?) в .S1. Что думаете?
> 
> С целью облегчения использования rebuild.

Шо, опять? (с)

Пожалуйста не надо больше никогда трогать %ubt. Это уже просьба
мейнтейнера догоняющей сборки в mipsel. Мы огребём.

Например, наверняка есть пакеты, собранные с релизом altX%ubt
уже при %ubt выставленном в %nil. Я сейчас не придумаю,
как их искать, но по началу их было много.

--
  wbr,
    iv m.


  parent reply	other threads:[~2019-01-16 10:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16  7:42 ` Anton Farygin
2019-01-16  9:09   ` Ivan Zakharyaschev
2019-01-16  9:22     ` Ivan Zakharyaschev
2019-01-16  9:28       ` Anton Farygin
2019-01-16  9:49         ` Ivan Zakharyaschev
2019-01-16  9:56           ` Ivan Zakharyaschev
2019-01-16  9:58             ` Ivan Zakharyaschev
2019-01-16 10:02             ` Ivan A. Melnikov
2019-01-16 10:06               ` Ivan Zakharyaschev
2019-01-16 10:24               ` Ivan Zakharyaschev
2019-01-16 10:27                 ` Anton Farygin
2019-01-16 10:31                   ` Ivan Zakharyaschev
2019-01-16 10:33                     ` Anton Farygin
2019-01-16 10:36                       ` Anton Farygin
2019-01-16 10:40                         ` Ivan Zakharyaschev
2019-01-16 10:48                           ` Anton Farygin
2019-01-16 11:06                             ` Ivan Zakharyaschev
2019-01-16 11:24                               ` Anton Farygin
2019-01-16 11:30                                 ` Ivan Zakharyaschev
2019-01-16 11:37                               ` Ivan A. Melnikov
2019-01-16 11:44                                 ` Aleksei Nikiforov
2019-01-21 14:38                                   ` Sergey V Turchin
2019-01-16 12:25                                 ` Ivan Zakharyaschev
2019-01-16 10:37                       ` Ivan Zakharyaschev
2019-01-16 10:35                     ` Ivan Zakharyaschev
2019-01-16 10:37                       ` Anton Farygin
2019-01-16 10:49                           ` Anton Farygin
2019-01-16 10:37                     ` Sergey V Turchin
2019-01-16 10:39                       ` Anton Farygin
2019-01-16 11:27                         ` Sergey V Turchin
2019-01-16 10:41                 ` Ivan A. Melnikov [this message]
2019-01-16 10:05             ` Ivan Zakharyaschev
2019-01-16 10:39               ` Sergey V Turchin
2019-01-16 10:41                 ` Ivan Zakharyaschev
2019-01-16 10:02         ` Ivan Zakharyaschev
2019-01-16 10:11           ` Anton Farygin
2019-01-16 10:15             ` Ivan Zakharyaschev
2019-01-16 10:17               ` Anton Farygin
2019-01-16 10:21                 ` Ivan Zakharyaschev
2019-01-16  9:29       ` Sergey V Turchin
2019-01-16  9:38         ` Ivan A. Melnikov
2019-01-16 13:15           ` [devel] hsh-rebuild --query-repackage Dmitry V. Levin
2019-01-16 13:25             ` Dmitry V. Levin
2019-01-17 10:47               ` Michael Shigorin
2019-01-16  9:30       ` [devel] Fwd: bird-1.6.4-alt1.S1: Sisyphus/x86_64 test rebuild failed Ivan Zakharyaschev
2019-01-16  9:36         ` Ivan Zakharyaschev

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=20190116104148.7u53ruznzl36b7pb@titan.localdomain \
    --to=iv@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