[devel] uname -m for i586 nodes Re: [#306082] [test-only] p10 FAILED apt.git=0.5.15lorg2-alt75 (fwd)
Ivan Zakharyaschev
imz на altlinux.org
Чт Сен 1 16:38:36 MSK 2022
Здравствуйте!
Судя по тому, что случилось в install check для i586 здесь, на узле uname
-m даёт значение x86_64. А раньше было не так, это нормально работало как
ожидается.
И были уже похожие случаи тут сообщены, например, в beehive configure
неправильно определил архитектуру как 64-битную.
Код в apt, который это значение читает:
bool pkgInitConfig(Configuration &Cnf)
{
const char *cpu = NULL;
struct utsname name;
if (uname(&name) == 0)
cpu = strdup(name.machine);
if (cpu == NULL)
cpu = COMMON_CPU;
// General APT things
if (strcmp(COMMON_OS,"linux") == 0 ||
strcmp(COMMON_OS,"unknown") == 0)
Cnf.CndSet("APT::Architecture",cpu);
else
Cnf.CndSet("APT::Architecture",COMMON_OS "-" COMMON_CPU);
Поэтому пакеты i586 стали считаться не основной архиетктуры, к их имени в
тестах стало добавляться .32bit.
On Thu, 1 Sep 2022, Girar awaiter (imz) wrote:
> https://git.altlinux.org/tasks/306082/logs/events.1.1.log
>
> subtask name aarch64 armh i586 ppc64le x86_64
> #100 apt 2:04 2:54 1:23 2:22 1:20
>
> 2022-Sep-01 13:08:15 :: test-only task #306082 for p10 started by imz:
> 2022-Sep-01 13:08:15 :: message: reproduce_i586_test_failure
> #100 build 0.5.15lorg2-alt75 from /gears/a/apt.git fetched at 2022-Sep-01 13:08:13 from p10
> 2022-Sep-01 13:08:16 :: [ppc64le] #100 apt.git 0.5.15lorg2-alt75: build start
> 2022-Sep-01 13:08:16 :: [x86_64] #100 apt.git 0.5.15lorg2-alt75: build start
> 2022-Sep-01 13:08:16 :: [aarch64] #100 apt.git 0.5.15lorg2-alt75: build start
> 2022-Sep-01 13:08:16 :: [armh] #100 apt.git 0.5.15lorg2-alt75: build start
> 2022-Sep-01 13:08:16 :: [i586] #100 apt.git 0.5.15lorg2-alt75: build start
> 2022-Sep-01 13:09:36 :: [x86_64] #100 apt.git 0.5.15lorg2-alt75: build OK
> 2022-Sep-01 13:09:39 :: [i586] #100 apt.git 0.5.15lorg2-alt75: build OK
> 2022-Sep-01 13:10:20 :: [aarch64] #100 apt.git 0.5.15lorg2-alt75: build OK
> 2022-Sep-01 13:10:38 :: [ppc64le] #100 apt.git 0.5.15lorg2-alt75: build OK
> 2022-Sep-01 13:11:10 :: [armh] #100 apt.git 0.5.15lorg2-alt75: build OK
> 2022-Sep-01 13:12:08 :: #100: apt.git 0.5.15lorg2-alt75: build check OK
> 2022-Sep-01 13:12:08 :: build check OK
> 2022-Sep-01 13:12:24 :: noarch check OK
> 2022-Sep-01 13:12:26 :: plan: src +1 -1 =17863, aarch64 +9 -9 =30021, armh +9 -9 =28242, i586 +9 -9 =30625, noarch +5 -5 =16472, ppc64le +9 -9 =29595, x86_64 +9 -9 =31321
> 2022-Sep-01 13:13:14 :: patched apt indices
> 2022-Sep-01 13:13:28 :: created next repo
> 2022-Sep-01 13:13:36 :: duplicate provides check OK
> 2022-Sep-01 13:14:13 :: dependencies check OK
> 2022-Sep-01 13:14:38 :: [x86_64 i586 aarch64 ppc64le armh] ELF symbols check OK
> 2022-Sep-01 13:14:49 :: [i586] #100 apt: install check OK
> 2022-Sep-01 13:14:49 :: [x86_64] #100 apt: install check OK
> 2022-Sep-01 13:14:57 :: [aarch64] #100 apt: install check OK
> 2022-Sep-01 13:14:59 :: [ppc64le] #100 apt: install check OK
> 2022-Sep-01 13:15:06 :: [armh] #100 apt: install check OK
> x86_64: apt-basic-checkinstall=0.5.15lorg2-alt75 post-install unowned files:
> /root/.apt_history
> /var/nobody/tmp
> 2022-Sep-01 13:15:06 :: [x86_64] #100 apt-basic-checkinstall: install check OK
> i586: apt-basic-checkinstall=0.5.15lorg2-alt75 install failed:
> /usr/share/apt/tests /tmp/sh.A4MuP251
> Run Testcase (1/47) test-without-repo-apt-check-simple
> Run Testcase (2/47) test-without-repo-apt-config-dump
> Run Testcase (3/47) test-without-repo-apt-install-conflicting-packages
> I: Preparing environment for test-without-repo-apt-install-conflicting-packages in /tmp/sh.A4MuP251/tmp.Ik6SykcPfH??? DONE
> Building package: conflicting-package-one
> Building package: conflicting-package-two
> Test that package(s) are not installed with rpm -q conflicting-package-one conflicting-package-two ??? PASS
> package conflicting-package-one is not installed
> package conflicting-package-two is not installed
> Test of regex match of apt-get install /tmp/sh.A4MuP251/tmp.Ik6SykcPfH/usr/src/RPM/RPMS/i586/conflicting-package-one-1-alt1.i586.rpm /tmp/sh.A4MuP251/tmp.Ik6SykcPfH/usr/src/RPM/RPMS/i586/conflicting-package-two-1-alt1.i586.rpm ??? FAIL
> -Reading Package Lists\.\.\.
> -Building Dependency Tree\.\.\.
> -Selecting conflicting-package-one for '[^']+'
> -Selecting conflicting-package-two for '[^']+'
> -Some packages could not be installed\. This may mean that you have
> +Reading Package Lists...
> +Building Dependency Tree...
> +Selecting conflicting-package-one.32bit for '/tmp/sh.A4MuP251/tmp.Ik6SykcPfH/usr/src/RPM/RPMS/i586/conflicting-package-one-1-alt1.i586.rpm'
> +Selecting conflicting-package-two.32bit for '/tmp/sh.A4MuP251/tmp.Ik6SykcPfH/usr/src/RPM/RPMS/i586/conflicting-package-two-1-alt1.i586.rpm'
> +Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> -or been moved out of Incoming\.
> +or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> - conflicting-package-one: Conflicts: conflicting-package-two
> - conflicting-package-two: Conflicts: conflicting-package-one
> + conflicting-package-one.32bit: Conflicts: conflicting-package-two
> + conflicting-package-two.32bit: Conflicts: conflicting-package-one
> E: Broken packages
> test-without-repo-apt-install-conflicting-packages ... FAIL
> Run Testcase (4/47) test-without-repo-apt-install-double
Подробная информация о списке рассылки Devel