From: Aleksey Avdeev <solo@solin.spb.ru> To: ALT Linux Team development discussions <devel@lists.altlinux.org> Subject: [devel] Q: Как правильно собирать hasher`ом на people? Date: Wed, 20 Jan 2016 16:31:59 +0300 Message-ID: <569F8C4F.8040806@solin.spb.ru> (raw) [-- Attachment #1: Type: text/plain, Size: 1443 bytes --] Приветствую. А как сейчас правильно выполнять сборку hasher`ом на people (people.egro.altlinux.org)? На данный момент натыкаюсь на следующее: [solo@people ~]$ hsh -v --initroot-only /tmp/.private/solo/hasher/ 2>&1 | tee hsh.log hsh: changed working directory to `/tmp/.private/solo/hasher' hsh: Locked working directory `/tmp/.private/solo/hasher' mkaptbox: changed working directory to `/tmp/.private/solo/hasher' ... hasher-priv: chrootuid: mount namespace isolation is not supported by the kernel: Operation not permitted hasher-priv: chrootuid: IPC namespace isolation is not supported by the kernel: Invalid argument hsh-initroot: Unpacked setup-2.2.14-alt1.noarch.rpm. ... hasher-priv: chrootuid: mount namespace isolation is not supported by the kernel: Operation not permitted hasher-priv: chrootuid: IPC namespace isolation is not supported by the kernel: Invalid argument hsh-initroot: Unpacked rpm-4.0.4-alt100.88.x86_64.rpm. hsh-initroot: Unpacked initial package list. hsh-initroot: Created entry point: /tmp/.private/solo/hasher/chroot/.host/entry hasher-priv: chrootuid: mount namespace isolation is not supported by the kernel: Operation not permitted hasher-priv: chrootuid: IPC namespace isolation is not supported by the kernel: Invalid argument FATAL: kernel too old hsh-initroot: Failed to create RPM database. Пока не пойму как бороться. -- С уважением. Алексей. [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 230 bytes --]
next reply other threads:[~2016-01-20 13:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-20 13:31 Aleksey Avdeev [this message] 2016-01-20 13:47 ` Gleb Fotengauer-Malinovskiy 2016-01-20 15:10 ` Aleksey Avdeev 2016-01-22 5:17 ` Vitaly Lipatov
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=569F8C4F.8040806@solin.spb.ru \ --to=solo@solin.spb.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