Processing control commands:
> severity -1 important
Bug #1092181 [cpp-11,cpp-11-x86-64-linux-gnu] cpp-11 and
cpp-11-x86-64-linux-gnu have an undeclared cross-architecture file conflict
Severity set to 'important' from 'serious'
--
1092181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092
Processing control commands:
> severity -1 important
Bug #1092182 [cpp-12,cpp-12-x86-64-linux-gnu] cpp-12 and
cpp-12-x86-64-linux-gnu have an undeclared cross-architecture file conflict
Severity set to 'important' from 'serious'
--
1092182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092
Control: severity -1 important
as you said, this is not a regression compared to earlier releases. I'm
downgrading this, as it doesn't affect our "normal" use case building
natively. Maybe we also should clarify, if cross-architecture file
conflicts are RC issues.
I am not keen to backport
Package: cpp-11,cpp-11-x86-64-linux-gnu
Severity: serious
Justification: fails to install
User: debian...@lists.debian.org
Usertags: fileconflict
Control: clone -1 -2
Control: retitle -2 cpp-12 and cpp-12-x86-64-linux-gnu have an undeclared
cross-architecture file conflict
Control: reassign -2 cpp
Processing control commands:
> clone -1 -2
Bug #1092181 [cpp-11,cpp-11-x86-64-linux-gnu] cpp-11 and
cpp-11-x86-64-linux-gnu have an undeclared cross-architecture file conflict
Bug 1092181 cloned as bug 1092182
> retitle -2 cpp-12 and cpp-12-x86-64-linux-gnu have an undeclared
> cross-architectur
LAST_UPDATED: Obtained from git: releases/gcc-13.3.0 revision
b71f1de6e9cf7181a288c0f39f9b1ef6580cf5c8
=== acats tests ===
=== acats Summary ===
# of expected passes2328
# of unexpected failures0
Native configuration is riscv64-unknown-linux-gn
6 matches
Mail list logo
