From: Michael Shigorin <mike@osdn.org.ua>
To: devel@altlinux.ru
Subject: [devel] Re: BTE
Date: Tue, 10 Dec 2002 21:51:47 +0200
Message-ID: <20021210195147.GD49907@osdn.org.ua> (raw)
In-Reply-To: <3DF60F94.2020405@altlinux.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Tue, Dec 10, 2002 at 07:00:20PM +0300, AntonFarygin wrote:
> Не стоит забывать, что у нас сейчас будет открываться доступ к
> сборочным серверам через почтовый интерфейс. И, честно говоря,
> давать возможность создавать рутовые чруты по письму (пусть
> даже авторизованному) - страшно.
Это понятно. Мне, правда, почему-то казалось, что сборка в BTE
наружу не выставляется, а является (прерогативой|удобством) ОТК.
Т.е. доступ _уже_ ограничен, можно сказать -- и с целью
обеспечения этого самого К.
> Можно поподробнее про неодинаковое поведение?
> Поведение сборочной среды диктуется исключительно зависимостями
> пакета и возможностью указывать другой apt репозиторий.
Возможно ли поручиться за поведение кода _пакетов_?
PS: можно игнорировать, наверное.
--
---- WBR, Michael Shigorin <mike@altlinux.ru>
------ Linux.Kiev http://www.linux.kiev.ua/
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2002-12-10 19:51 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 17:47 [devel] Broken python21 Alexander Bokovoy
2002-12-09 18:06 ` aen
2002-12-09 20:58 ` Andrey Orlov
2002-12-09 18:12 ` Dmitry V. Levin
2002-12-09 18:23 ` Alexander Bokovoy
2002-12-09 18:53 ` Dmitry V. Levin
2002-12-09 19:04 ` Alexander Bokovoy
2002-12-09 18:49 ` Aleksandr Blokhin
2002-12-09 20:02 ` Dmitry V. Levin
2002-12-09 20:27 ` Aleksandr Blokhin
2002-12-09 19:52 ` Dmitry V. Levin
2002-12-09 19:56 ` aen
2002-12-09 20:08 ` Dmitry V. Levin
2002-12-09 20:09 ` Alexander Bokovoy
2002-12-09 20:11 ` AntonFarygin
2002-12-09 20:32 ` Alexander Bokovoy
2002-12-09 20:50 ` AntonFarygin
2002-12-10 9:47 ` Alexander Bokovoy
2002-12-10 10:02 ` AntonFarygin
2002-12-10 10:28 ` Alexander Bokovoy
2002-12-10 10:40 ` [devel] BTE Dmitry V. Levin
2002-12-10 10:51 ` Alexander Bokovoy
2002-12-10 11:02 ` Dmitry V. Levin
2002-12-10 11:15 ` Alexander Bokovoy
2002-12-10 11:33 ` Dmitry V. Levin
2002-12-10 11:52 ` Alexander V. Nikolaev
2002-12-10 12:13 ` Alexander Bokovoy
2002-12-10 12:29 ` AntonFarygin
2002-12-10 12:53 ` Alexander Bokovoy
2002-12-10 13:19 ` Dmitry V. Levin
2002-12-10 13:48 ` Alexander Bokovoy
2002-12-10 16:00 ` AntonFarygin
2002-12-10 16:35 ` Alexander Bokovoy
2002-12-10 17:04 ` AntonFarygin
2002-12-10 17:28 ` Alexander Bokovoy
2002-12-10 18:41 ` Dmitry V. Levin
2002-12-10 18:48 ` Alexander Bokovoy
2002-12-10 19:59 ` Dmitry V. Levin
2002-12-10 20:03 ` Alexander Bokovoy
2002-12-11 6:45 ` AntonFarygin
2002-12-11 6:40 ` AntonFarygin
2002-12-10 19:51 ` Michael Shigorin [this message]
2002-12-11 6:42 ` [devel] BTE AntonFarygin
2002-12-11 14:07 ` [devel] BTE Alexander Bokovoy
2002-12-11 14:21 ` AntonFarygin
2002-12-11 14:51 ` Alexander Bokovoy
2002-12-11 15:34 ` Dmitry V. Levin
2002-12-11 15:42 ` Alexander Bokovoy
2002-12-11 16:05 ` Dmitry V. Levin
2002-12-11 16:26 ` Alexander Bokovoy
2002-12-11 16:48 ` Dmitry V. Levin
2002-12-11 16:49 ` Alexander Bokovoy
2002-12-10 11:02 ` Alexander Bokovoy
2002-12-10 11:02 ` [devel] Broken python21 AntonFarygin
2002-12-10 11:19 ` Alexander Bokovoy
2002-12-10 11:36 ` [devel] BTE Dmitry V. Levin
2002-12-10 11:54 ` [devel] Broken python21 Alexander V. Nikolaev
2002-12-10 12:16 ` Alexander Bokovoy
2002-12-10 13:01 ` Alexander V. Nikolaev
2002-12-10 13:11 ` Alexander Bokovoy
2002-12-10 13:37 ` [devel] " Andrey Khavryuchenko
2002-12-10 13:57 ` Alexander Bokovoy
2002-12-10 13:32 ` Andrey Khavryuchenko
2002-12-10 13:41 ` Alexander V. Nikolaev
2002-12-10 13:49 ` Andrey Khavryuchenko
2002-12-10 14:11 ` aen
2002-12-10 14:51 ` Andrey Khavryuchenko
2002-12-09 21:03 ` [devel] " Dmitry V. Levin
2002-12-10 9:57 ` Alexander Bokovoy
2002-12-10 10:45 ` [devel] Dependencies Dmitry V. Levin
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=20021210195147.GD49907@osdn.org.ua \
--to=mike@osdn.org.ua \
--cc=devel@altlinux.ru \
/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