From: Sergey Vlasov <vsu@altlinux.ru> To: ALT Devel discussion list <devel@lists.altlinux.org> Subject: Re: [devel] [Sisyphus-cybertalk] I: Sisyphus-20060620 full list of x86_64 unmets (722/261) Date: Wed, 21 Jun 2006 12:29:35 +0400 Message-ID: <20060621082935.GV3206@master.mivlgu.local> (raw) In-Reply-To: <20060620181245.GA30076@localhost.localdomain> [-- Attachment #1: Type: text/plain, Size: 959 bytes --] On Tue, Jun 20, 2006 at 10:12:45PM +0400, Денис Смирнов wrote: > On Tue, Jun 20, 2006 at 03:02:02AM +0400, QA Team Robot wrote: > > QTR> 2006-05-30 kernel-complete-std-smp#2.4.26-alt4 kernel-image-std-smp > QTR> 2006-05-30 kernel-complete-std-up#2.4.26-alt4 kernel-modules-3c90x-std-up > > Этих надо сделать ExclusiveArch? Или кто-то занимается поддержкой ядер > 2.4.* для x86_64? На x86_64 поддержка 2.4.* вырезана как минимум из mkinitrd-busybox, поэтому загрузиться с таким ядром там невозможно, даже если его собрать. > QTR> 2006-05-30 python-module-Cheetah#1.0rc1-alt1 libc.so.6 > > Это как? Фальшивый noarch, собранный на i586? > QTR> 2006-05-31 kernel-modules-amedyn-std26-up#20040801-alt6.132622.5 kernel-image-std26-up = 2.6.14-alt5 > QTR> 2006-05-31 kernel-modules-amedyn-wks26-up#20040801-alt6.132622.5 kernel-image-wks26-up = 2.6.14-alt5 > > ? Эти модули перестали собираться с 2.6.16, и, похоже, никому не нужны. [-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-21 8:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-20 18:12 ` Денис Смирнов 2006-06-21 8:29 ` Sergey Vlasov [this message] 2006-06-21 10:28 ` Andrey Khavryuchenko 2006-06-21 10:42 ` [devel] Как поставить x86-64 на современный сервер Dmitry V. Levin 2006-06-21 11:21 ` Damir Shayhutdinov 2006-06-21 11:39 ` Anton Farygin 2006-06-21 12:13 ` ëÁË ÐÏÓÔÁ×ÉÔØ x86-64 ÎÁ ÓÏ×ÒÅÍÅÎÎÙÊ ÓÅÒ×ÅÒ Andrey Khavryuchenko 2006-06-21 12:24 ` [devel] (без темы) Anton Farygin 2006-06-21 10:51 ` [devel] [Sisyphus-cybertalk] I: Sisyphus-20060620 full list of x86_64 unmets (722/261) Igor Zubkov 2006-06-21 11:40 ` Anton Farygin
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=20060621082935.GV3206@master.mivlgu.local \ --to=vsu@altlinux.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