Bug#1055153: marked as done (skeema: FTBFS on mips64el)
Your message dated Wed, 15 Nov 2023 07:34:10 + with message-id and subject line Bug#1055153: fixed in skeema 1.11.0+ds-2 has caused the Debian Bug report #1055153, regarding skeema: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: skeema Version: 1.11.0+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=skeema&arch=mips64el&ver=1.11.0%2Bds-1%2Bb1&stamp=1698766711&raw=0 dh_auto_test cd _build && go test -vet=off -v -p 4 github.com/skeema/skeema github.com/skeema/skeema/internal/applier github.com/skeema/skeema/internal/dumper github.com/skeema/skeema/internal/fs github.com/skeema/skeema/internal/linter github.com/skeema/skeema/internal/shellout github.com/skeema/skeema/internal/tengo github.com/skeema/skeema/internal/util github.com/skeema/skeema/internal/workspace === RUN TestExitCode --- PASS: TestExitCode (0.00s) === RUN TestExitValueError --- PASS: TestExitValueError (0.00s) === RUN TestHighestExitCode --- PASS: TestHighestExitCode (0.00s) === RUN TestExit 2023-10-31 15:38:03 [␛[31;1mERROR␛[0m] errors that don't implement ExitCoder are all treated as fatal error 2023-10-31 15:38:03 [␛[31;1mERROR␛[0m] bad config --- PASS: TestExit (0.00s) === RUN TestPanicHandler 2023-10-31 15:38:03 [␛[31;1mERROR␛[0m] Uncaught panic in github.com/skeema/skeema.TestPanicHandler at /<>/_build/src/github.com/skeema/skeema/exit_test.go:100: If this test passes, this was actually caught properly, don't worry about the surrounding text This situation indicates a bug in Skeema. Use --debug to view full stack trace. Please file an issue report at https://github.com/skeema/skeema/issues with any available background information. --- PASS: TestPanicHandler (0.00s) === RUN TestIntegration SKEEMA_TEST_IMAGES env var is not set, so integration tests will be skipped! To run integration tests, you may set SKEEMA_TEST_IMAGES to a comma-separated list of Docker images. For example: $ SKEEMA_TEST_IMAGES="mysql:8.0,mariadb:10.11" go test --- SKIP: TestIntegration (0.00s) PASS ok github.com/skeema/skeema0.039s === RUN TestResultMerge --- PASS: TestResultMerge (0.00s) === RUN TestIntegration SKEEMA_TEST_IMAGES env var is not set, so integration tests will be skipped! To run integration tests, you may set SKEEMA_TEST_IMAGES to a comma-separated list of Docker images. For example: $ SKEEMA_TEST_IMAGES="mysql:8.0,mariadb:10.11" go test --- SKIP: TestIntegration (0.00s) PASS ok github.com/skeema/skeema/internal/applier 0.031s === RUN TestOptionsIgnore --- PASS: TestOptionsIgnore (0.00s) === RUN TestIntegration SKEEMA_TEST_IMAGES env var is not set, so integration tests will be skipped! To run integration tests, you may set SKEEMA_TEST_IMAGES to a comma-separated list of Docker images. For example: $ SKEEMA_TEST_IMAGES="mysql:8.0,mariadb:10.11" go test --- SKIP: TestIntegration (0.00s) PASS ok github.com/skeema/skeema/internal/dumper0.022s === RUN TestParseDir --- PASS: TestParseDir (0.01s) === RUN TestParseDirErrors --- PASS: TestParseDirErrors (0.01s) === RUN TestParseDirSymlinks --- PASS: TestParseDirSymlinks (0.04s) === RUN TestParseDirNamedSchemas --- PASS: TestParseDirNamedSchemas (0.02s) === RUN TestDirGenerator --- PASS: TestDirGenerator (0.01s) === RUN TestDirNamedSchemaStatements --- PASS: TestDirNamedSchemaStatements (0.02s) === RUN TestParseDirNoSchemas --- PASS: TestParseDirNoSchemas (0.01s) === RUN TestParseDirUnterminated --- PASS: TestParseDirUnterminated (0.02s) === RUN TestParseDirUnparsedStatements --- PASS: TestParseDirUnparsedStatements (0.00s) === RUN TestParseDirRedundantDelimiter --- PASS: TestParseDirRedundantDelimiter (0.01s) === RUN TestParseDirCreateSelect --- PASS: TestParseDirCreateSelect (0.01s) === RUN TestParseDirBOM --- PASS: TestParseDirBOM (0.01s) === RUN TestParseDirIgnorePatterns --- PASS: TestParseDirIgnorePatterns (0.01s) === RUN TestDirParseDirCasingConflict --- PASS: TestDirParseDirCasingConflict (0.00s) === RUN TestDirBaseName --- PASS: TestDirBaseName (0.01s) === RUN TestDirRelPath --- PASS: TestDirRelPath (0.01s) === RUN TestDirSubdirs --- PASS: TestDirSubdirs (0.04s) === RUN TestDirFileFor --- PASS: TestDirFileFor (0.01s) === RUN TestDirDirtyFiles --- PASS: TestDirDirtyFiles (0.01s
Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
Le 03/11/2023 à 21:32, Faidon Liambotis a écrit :
Control: reopen -1
Control: found -1 1:16.0.6-17
Note how /usr/include/wasm32-wasi/c++/v1 is missing.
Test case:
$ apt install clang lld libclang-rt-dev-wasm32 libc++-dev-wasm32
$ cat > hello.cpp <
int main() {
std::cout << "hello world" << std::endl;
return 0;
}
EOF
$ /usr/bin/clang++ -v --target=wasm32-wasi hello.cpp
Only C++ include paths are affected, not C. This almost certainly has to
do with the patch we carry for wasm include paths, that I have
contributed to. Unfortunately I have no time to look into it right now
:( I may find some time in a couple of weeks, but hoping someone else
can take care of it in the meantime :/
I understand better why I didn't get this problem locally:
If you install libc++-dev too, the problem goes away.
because it provides the symlink
/usr/include/c++/v1 -> ../../lib/llvm-16/include/c++/v1
which makes clang happy
but still looking into a different solution
cheers
S
Bug#1055901: marked as done (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)
Your message dated Tue, 14 Nov 2023 22:44:21 +0100 with message-id and subject line Re: Bug#1055901: Acknowledgement (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/) has caused the Debian Bug report #1055901, regarding raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: raspi-firmware Version: 1:1.20231024+ds-1+rpt1 Severity: serious Justification: Policy 6.4 Hello, the package fails to install on my system. I simply assumes that /boot/firmware is a mount point and fails if this is not the case. If /boot/firmware is expected to be a mount point the installer should have created it. The system was once installed as bullseye and later upgraded to bookworm. Himar -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: ii bluez-firmware 1.2-9+rpt2 ii firmware-brcm80211 1:20230210-5+rpt1 ii firmware-misc-nonfree 1:20230210-5+rpt1 -- no debconf information --- End Message --- --- Begin Message --- On 11/13/23 23:03, Debian Bug Tracking System wrote: Hi all, the packages was pulled in by rpi-eeprom, which was upgraded. I just noticed that I don't need the package b/c I run just an RPi 3. So I deleted all packages and I'm not affected any more. I close that bug, sorry for the noise! Hilmar Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1055901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055901. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. -- Testmail OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1055962: intel-microcode: CVE-2023-23583: INTEL-SA-00950
Source: intel-microcode Version: 3.20230808.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.20230808.1~deb12u1 Control: found -1 3.20230808.1~deb11u1 Hi, The following vulnerability was published for intel-microcode. CVE-2023-23583[0]: | Sequence of processor instructions leads to unexpected behavior for | some Intel(R) Processors may allow an authenticated user to | potentially enable escalation of privilege and/or information | disclosure and/or denial of service via local access. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-23583 https://www.cve.org/CVERecord?id=CVE-2023-23583 [1] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00950.html Regards, Salvatore
Processed: intel-microcode: CVE-2023-23583: INTEL-SA-00950
Processing control commands: > found -1 3.20230808.1~deb12u1 Bug #1055962 [src:intel-microcode] intel-microcode: CVE-2023-23583: INTEL-SA-00950 Marked as found in versions intel-microcode/3.20230808.1~deb12u1. > found -1 3.20230808.1~deb11u1 Bug #1055962 [src:intel-microcode] intel-microcode: CVE-2023-23583: INTEL-SA-00950 Marked as found in versions intel-microcode/3.20230808.1~deb11u1. -- 1055962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1055952: vlc: upgrade to libva 7:6.1-2
Processing control commands: > reassign -1 libavcodec60 7:6.1-1 Bug #1055952 [vlc] vlc: upgrade to libva 7:6.1-2 Bug reassigned from package 'vlc' to 'libavcodec60'. No longer marked as found in versions vlc/3.0.20-1. Ignoring request to alter fixed versions of bug #1055952 to the same values previously set Bug #1055952 [libavcodec60] vlc: upgrade to libva 7:6.1-2 Marked as found in versions ffmpeg/7:6.1-1. > severity -1 serious Bug #1055952 [libavcodec60] vlc: upgrade to libva 7:6.1-2 Severity set to 'serious' from 'normal' > tags -1 confirmed upstream Bug #1055952 [libavcodec60] vlc: upgrade to libva 7:6.1-2 Added tag(s) confirmed and upstream. -- 1055952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958692: node-matrix-js-sdk: Remove dependency to node-request
On Fri, 3 Nov 2023 00:27:36 +0530, Pirate Praveen said: > On 2/11/23 10:27 PM, Hubert Chathi wrote: >> On Sun, 29 Oct 2023 22:43:55 +0530, Praveen Arimbrathodiyil >> said: >> >>> On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote: Upstream has deprecated node-request: https://github.com/request/request/issues/3142 It can be replaced by node-got >> >>> Hi Jonas, Hubert, >> >>> Are you planning to update matrix-js-sdk? We'd like to remove >>> deprecated node-request from the archive and this package is a >>> blocker. >> I don't currently have time to update matrix-js-sdk. Feel free to >> remove it from testing so that it doesn't block anything else. I can >> always upload a new version later. >> > This is already not in testing for 525 days. We can't remove a package > from the archive if any package (build) depends on it. OK, I understand. Yes, go ahead and remove it. -- Hubert Chathi -- https://www.uhoreg.ca/ Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
Bug#1055896: marked as done (cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?)
Your message dated Tue, 14 Nov 2023 14:35:05 +
with message-id
and subject line Bug#1055896: fixed in cod-tools 3.8.0+dfsg-1
has caused the Debian Bug report #1055896,
regarding cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first
use in this function); did you mean ‘OP_CONST’?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1055896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cod-tools
Version: 3.7.0+dfsg-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=cod-tools&arch=s390x&ver=3.7.0%2Bdfsg-1%2Bb4&stamp=1699906136&raw=0
make[2]: Entering directory '/<>/src/lib/perl5/COD/SPGLib'
swig -perl5 -Wall -outdir lib/COD/ source.i
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-unused-value \
-I. -c \
`perl -MConfig -e 'print join(" ", @Config{qw(ccflags optimize
cccdlflags)}, "-I$Config{archlib}/CORE")'` \
source.c source_wrap.c
source.c: In function ‘get_sym_dataset’:
source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did
you mean ‘OP_CONST’?
33 | SPGCONST double lattice[3][3];
| ^~~~
| OP_CONST
source.c:33:5: note: each undeclared identifier is reported only once for each
function it appears in
source.c:33:13: error: expected ‘;’ before ‘double’
33 | SPGCONST double lattice[3][3];
| ^~~
| ;
source.c:36:13: error: ‘lattice’ undeclared (first use in this function); did
you mean ‘lattice_av’?
36 | lattice[i][j] = SvNV( (SV*)
| ^~~
| lattice_av
source.c:44:13: error: expected ‘;’ before ‘double’
44 | SPGCONST double positions[natoms][3];
| ^~~
| ;
source.c:49:13: error: ‘positions’ undeclared (first use in this function)
49 | positions[i][j] = SvNV( (SV*)
| ^
make[2]: *** [Makelocal-SWIG-module:36: source.o] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: cod-tools
Source-Version: 3.8.0+dfsg-1
Done: Andrius Merkys
We believe that the bug you reported is fixed in the latest version of
cod-tools, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrius Merkys (supplier of updated cod-tools package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 14 Nov 2023 08:51:31 -0500
Source: cod-tools
Architecture: source
Version: 3.8.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Andrius Merkys
Closes: 1055896
Changes:
cod-tools (3.8.0+dfsg-1) unstable; urgency=medium
.
* New upstream version 3.8.0+dfsg (Closes: #1055896)
* Refresh debian/copyright.
* Refresh patches.
* Update standards version to 4.6.2, no changes needed.
Checksums-Sha1:
6c61a561964d93a5b321b4e0f5e5e23462feb944 3396 cod-tools_3.8.0+dfsg-1.dsc
3dc177a6cc178c7fd6ab23d0617ab1a6c151de26 25460404
cod-tools_3.8.0+dfsg.orig.tar.xz
edeb2563b7e57ec43a92eaca43093953d3aeb6e0 14220
cod-tools_3.8.0+dfsg-1.debian.tar.xz
0d4b58f5eda2df7a7bd84826bdfb0a0e12281975 11767
cod-tools_3.8.0+dfsg-1_source.buildinfo
Checksums-Sha256:
ab26006b4c2ec40eee4b74ef4a121d6aff3fea35b6ddc595ea9be4e920ec58f3 3396
cod-tools_3.8.0+dfsg-1.dsc
1128e0bb27143dba93c832e770adb27855ee2173f0861d4d7eb928e086a70626 25460404
cod-tools_3.8.0+dfsg.orig.tar.xz
07428e166a9b1b35c5bb13dc2d3e20f31bc651e405b7e7c403cc7cb256fe15e7 14220
cod-tools_3.8.0+dfsg-1.debian.tar.xz
7b1c0a39d0d4f32f28360261e161fe5493e3408c36522611d1a6d19043fa3b39 11767
cod-tools_3.8.0+dfsg-1_source.buildinfo
Files:
44a5e287e0c181da11fe22e78f8ada88 3396 science optional
cod-tools_3.8.0+dfsg-1.dsc
964718143f5a7ef029f8d816b97a4964 25460404 science optional
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
On 14 November 2023 at 12:26, Graham Inggs wrote: | Hi Dirk | | On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote: | > Well that seems to be a) the wrong severity and b) the wrong package. | | Both are correct. We do not want rmatrix to migrate and break | packages in testing. Doesn't 'normal' do that? I always get the shivers when I see 'serious' as I fear that my package is at the risk of removal (which we of course Matrix can't be 'really' given its systemic status from its "recommended" status within R and very widespread use). | However, in this case, I only set the severity to match reality; | rmatrix is already blocked from migrating due to the autopkgtest | regressions. | | > We need to address the packages needing a rebuild. Mine (r-cran-lme4, | > r-cran-rcppeigen). have been taken care of. | | Agreed, and rmatrix may need some new Breaks to allow the affected | packages to migrate together. The issue is actually hugely problematic for CRAN and R Core, and there are some discussions but no solutions. They do not have (formal) notions like binary rebuild for parts where they distribute binaries, and no means of reaching binary redistributors such as us. Oh well. At least it doesn't happen often. Anyway. Now that you made it a bug I let you drive this. Upstream just made an unrelated bugfix Matrix 1.6-3 which I just sent to unstable. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Dirk On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote: > Well that seems to be a) the wrong severity and b) the wrong package. Both are correct. We do not want rmatrix to migrate and break packages in testing. However, in this case, I only set the severity to match reality; rmatrix is already blocked from migrating due to the autopkgtest regressions. > We need to address the packages needing a rebuild. Mine (r-cran-lme4, > r-cran-rcppeigen). have been taken care of. Agreed, and rmatrix may need some new Breaks to allow the affected packages to migrate together. Regards Graham
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
On 14 November 2023 at 09:15, Graham Inggs wrote: | Source: rmatrix | Version: 1.6-2-1 | Severity: serious | X-Debbugs-Cc: debia...@lists.debian.org | | Hi Dirk | | I'm opening this bug as a place for discussion and to track the | affected packages. It can be closed once rmatrix and its | reverse-dependencies are ready to migrate. Well that seems to be a) the wrong severity and b) the wrong package. We need to address the packages needing a rebuild. Mine (r-cran-lme4, r-cran-rcppeigen). have been taken care of. Dirk | I've copied your email to the debian-r mailing list [1] below. | | Regards | Graham | | | [1] https://lists.debian.org/debian-r/2023/11/msg00033.html | | | Package Matrix is having a new and energetic maintainer/contributor in Mikael | Jagan who is tidying up a few loose corners (and inter alia sent me a patch | to RcppEigen that resulted in a coordinated CRAN update of RcppEigen, lme4, | and OpenMx). | | Mikael also identified two sets of packages needed a rebuild in messages to | the r-package-devel list (the more-or-less official place in the R Project to | ask / discuss package changes, it is a decent to be on) following private | mails between him and me. See | | https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010051.html | https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010054.html | | The first concerns packages using a LinkingTo: Matrix and building against | Matrix _headers_. The second concerns caching of S4 signatures (which bit us | at work because of SeuratObject [not in Debian] and how I got onto this). | | Most of these are not in Debian but I think we need binary rebuilds of | |irlbabecause of headers |OpenMx because of headers, a new upstream 2.21.10 is out too |TMB because of headers |MatrixModels because of S4 caching | | I would appreciate it if someone could tickle rebuilds. To me a quick | informal touch of debian/changelog would do; if someone thinks this needs a | formal transition go for it. | | The R Core team and the CRAN maintainers are aware of the implicit problem | with signalling the need for binary rebuilds. They are discussing this, but | do not have an answer. Historically, CRAN has informally rebuilt its binaries | for windows and macOS, but that of course does not help binary distributors | such as us, other Linux distros, Conda, r2u, ... at all. -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed: dbcsr: please disable tests/inputs/test_H2O.perf and dbcsr_unittest2 on armel
Processing control commands: > block 1055914 by -1 Bug #1055914 [src:cp2k] cp2k: BD-Uninstallable on armel 1055914 was not blocked by any bugs. 1055914 was not blocking any bugs. Added blocking bug(s) of 1055914: 1055928 -- 1055914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055914 1055928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055896: cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?
Control: owner -1 ! Hi, On 2023-11-14 14:27, Gianfranco Costamagna wrote: https://github.com/cod-developers/cod-tools/commit/2e9c0aaa367366883105fa9a7ba3d965495700f8 Just removing SPGCONST from the source.c file is enough, trivial patch attached: Sadly I opened an upstream PR before upstream updated the branch, so the patch I uploaded in Ubuntu has my name as author [patch removed for brevity] I will soon update cod-tools to the newest upstream release where this bug is fixed. Best, Andrius
Processed: Re: Bug#1055896: cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?
Processing control commands: > owner -1 ! Bug #1055896 [src:cod-tools] cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’? Owner recorded as Andrius Merkys . -- 1055896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?
Processing control commands: > tags -1 patch Bug #1055896 [src:cod-tools] cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’? Added tag(s) patch. > tags -1 fixed-upstream Bug #1055896 [src:cod-tools] cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’? Added tag(s) fixed-upstream. -- 1055896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055896: cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?
control: tags -1 patch
control: tags -1 fixed-upstream
https://github.com/cod-developers/cod-tools/commit/2e9c0aaa367366883105fa9a7ba3d965495700f8
Just removing SPGCONST from the source.c file is enough, trivial patch attached:
Sadly I opened an upstream PR before upstream updated the branch, so the patch
I uploaded in Ubuntu has my name as author
cat debian/patches/new-spdlib-build-fix.patch
Author: Gianfranco Costamagna
Description: sed s/SPGCONST//g -i ./src/lib/perl5/COD/SPGLib/SPGLib.c
Due to upstream removing it https://github.com/spglib/spglib/pull/258/files
Bug-Debian: https://bugs.debian.org/1055896
Forwarded: https://github.com/cod-developers/cod-tools/pull/16
Last-Update: 2023-11-14
--- cod-tools-3.7.0+dfsg.orig/src/lib/perl5/COD/SPGLib/SPGLib.c
+++ cod-tools-3.7.0+dfsg/src/lib/perl5/COD/SPGLib/SPGLib.c
@@ -30,7 +30,7 @@ SV* get_sym_dataset( SV* lattice_ref, SV
int j;
int k;
-SPGCONST double lattice[3][3];
+double lattice[3][3];
for( i = 0; i < 3; i++ ) {
for( j = 0; j < 3; j++ ) {
lattice[i][j] = SvNV( (SV*)
@@ -41,7 +41,7 @@ SV* get_sym_dataset( SV* lattice_ref, SV
}
}
-SPGCONST double positions[natoms][3];
+double positions[natoms][3];
int types[natoms];
for( i = 0; i < natoms; i++ ) {
types[i] = SvIV( (SV*) *av_fetch( types_av, i, 0 ) );
On Mon, 13 Nov 2023 21:11:56 +0100 Sebastian Ramacher
wrote:
Source: cod-tools
Version: 3.7.0+dfsg-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=cod-tools&arch=s390x&ver=3.7.0%2Bdfsg-1%2Bb4&stamp=1699906136&raw=0
make[2]: Entering directory '/<>/src/lib/perl5/COD/SPGLib'
swig -perl5 -Wall -outdir lib/COD/ source.i
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-unused-value \
-I. -c \
`perl -MConfig -e 'print join(" ", @Config{qw(ccflags optimize cccdlflags)},
"-I$Config{archlib}/CORE")'` \
source.c source_wrap.c
source.c: In function ‘get_sym_dataset’:
source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did
you mean ‘OP_CONST’?
33 | SPGCONST double lattice[3][3];
| ^~~~
| OP_CONST
source.c:33:5: note: each undeclared identifier is reported only once for each
function it appears in
source.c:33:13: error: expected ‘;’ before ‘double’
33 | SPGCONST double lattice[3][3];
| ^~~
| ;
source.c:36:13: error: ‘lattice’ undeclared (first use in this function); did
you mean ‘lattice_av’?
36 | lattice[i][j] = SvNV( (SV*)
| ^~~
| lattice_av
source.c:44:13: error: expected ‘;’ before ‘double’
44 | SPGCONST double positions[natoms][3];
| ^~~
| ;
source.c:49:13: error: ‘positions’ undeclared (first use in this function)
49 | positions[i][j] = SvNV( (SV*)
| ^
make[2]: *** [Makelocal-SWIG-module:36: source.o] Error 1
Cheers
--
Sebastian Ramacher
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1054145: marked as done (libtk-img: undefined symbol: jpeg_std_huff_table)
Your message dated Tue, 14 Nov 2023 11:34:25 + with message-id and subject line Bug#1054145: fixed in libtk-img 1:1.4.15+dfsg-3 has caused the Debian Bug report #1054145, regarding libtk-img: undefined symbol: jpeg_std_huff_table to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtk-img Version: 1:1.4.15+dfsg-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: o...@wanadoo.es Dear Maintainer, $ wish % package require img::jpeg couldn't load file "/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.15/libjpegtcl9.5.0.so": /usr/lib/tcltk/x86_64-linux-gnu/Img1.4.15/libjpegtcl9.5.0.so: undefined symbol: jpeg_std_huff_table % -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libtk-img depends on: ii libc6 2.37-12 ii libjpeg62-turbo 1:2.1.5-2 ii libpng16-16 1.6.40-2 ii libtiff6 4.5.1+git230720-1 ii libtk8.6 [libtk] 8.6.13-2 ii libx11-6 2:1.8.7-1 ii zlib1g1:1.2.13.dfsg-3 libtk-img recommends no packages. Versions of packages libtk-img suggests: pn libtk-img-doc -- no debconf information --- End Message --- --- Begin Message --- Source: libtk-img Source-Version: 1:1.4.15+dfsg-3 Done: Sergei Golovan We believe that the bug you reported is fixed in the latest version of libtk-img, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergei Golovan (supplier of updated libtk-img package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 14 Nov 2023 14:05:01 +0300 Source: libtk-img Architecture: source Version: 1:1.4.15+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Sergei Golovan Changed-By: Sergei Golovan Closes: 1054145 Changes: libtk-img (1:1.4.15+dfsg-3) unstable; urgency=medium . * Fix undefined symbol jpeg_std_huff_table when loading img::jpeg (closes: #1054145). Checksums-Sha1: 3537c21a2d1d77402799345977c80fecdf18b12a 2141 libtk-img_1.4.15+dfsg-3.dsc 66032661a27269fc913ef5a702460e23cf9f4e64 14520 libtk-img_1.4.15+dfsg-3.debian.tar.xz b89a444fd2658ce4a2cb0df932003a2fe6b2cfff 9054 libtk-img_1.4.15+dfsg-3_amd64.buildinfo Checksums-Sha256: 81d86aa1792e4b5b9e7b89514128055f87a43cd71d2958c9aa694f2d089124b8 2141 libtk-img_1.4.15+dfsg-3.dsc 8b77700d083f863c9094697bf218e180563dfff3d5a13f1760f31dd5fbd949d2 14520 libtk-img_1.4.15+dfsg-3.debian.tar.xz e50e7ecfcdc9bec0889d082f2ef00525fee79e2c0e0a52a1dfdbc5705794cf06 9054 libtk-img_1.4.15+dfsg-3_amd64.buildinfo Files: e016c3a43cedf5d5c43b88bf626294a4 2141 libs optional libtk-img_1.4.15+dfsg-3.dsc d412b8088543787b793b4eb7c626b3aa 14520 libs optional libtk-img_1.4.15+dfsg-3.debian.tar.xz a1b39dbd1eaaa9c1dc83676f062cced1 9054 libs optional libtk-img_1.4.15+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAmVTVZYACgkQTyrk60tj 54ebEg//UJfpTp4kH3JFjmLrPsI4c4MHMxVsHpacqszrDKmD0t58C4BzPg0WFobz f/9K7JvcmYd3RE9hMiNJ4UkzZT6ItZu25pqjbFhqvaHkGEYSEH6gvaGfJ9AxgumJ E1sEa5CRl2wZIBjwF1dRJ83X9TQ0rshgytJh7XqFIyIiKRhNchd6gTkYEcb9kVcI WEOpVWcJKq1JksDtK8QRcYYo7ZXrIJCgViadCuxBFj0soiNke2Hn8S16bNhTlQPF SavzO5pK8v+jArFK+s4xwOqNnnYMeQqRY8QNx34m14PVosjDZ0XeeJv+BYEAc5KW cfw5Yxgqe5n3fFMpec0FutQvM4RUPWtXXKtcN0Q/K0Mo3ACi52Oi5KsDJ9BR+LJZ CLhRnoA4Hc2eWCDS+oJU56OxihisrTRUNZDbkVMqJenHxiD5fe7ofk/tn7Nat7Rx W6EZKRscUrivzxTbezMYsHiIPE9aMuvga16g8uEpFAbjgU4XvTe6uXDRsbcy82+5 DD6xG3k3oo+tuNkR0OF2Lz21Xn+80A+q+SZpIaKLvEPiElV2Pm2uBPWnehbX6260 DqPlfn9lSNCfZ5Xk3LZJUZSA1pTS6AJEsNo3F3w/lPo70N8EsQI8CthZAzpvPHn+ 6C8CUl9Ibi2htwBZln4eU+h7
Bug#1054700: marked as done (qtbase-opensource-src-gles: FTBFS: > main.cpp:2:10: fatal error: EGL/fbdev_window.h: No such file or directory)
Your message dated Tue, 14 Nov 2023 11:25:20 + with message-id and subject line Bug#1054700: fixed in qtbase-opensource-src-gles 5.15.10+dfsg-3 has caused the Debian Bug report #1054700, regarding qtbase-opensource-src-gles: FTBFS: > main.cpp:2:10: fatal error: EGL/fbdev_window.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qtbase-opensource-src-gles Version: 5.15.10+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd linuxaccessibility/ && ( test -e Makefile || /<>/bin/qmake -o > Makefile > /<>/src/platformsupport/linuxaccessibility/linuxaccessibility.pro > ) && make -f Makefile > rm -f ../../../lib/libQt5EglSupport.a > ar cqs ../../../lib/libQt5EglSupport.a .obj/qeglconvenience.o > .obj/qeglstreamconvenience.o .obj/qeglplatformcontext.o .obj/qeglpbuffer.o > .obj/qxlibeglintegration.o > make[5]: Leaving directory > '/<>/src/platformsupport/eglconvenience' > g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -fPIC -std=c++1z -fvisibility=hidden > -fvisibility-inlines-hidden -fno-exceptions -Wall -Wextra -Wvla -Wdate-time > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > -Wno-format-overflow -D_REENTRANT -DQT_NO_LINKED_LIST > -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_CAST_FROM_ASCII > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_XKBCOMMON_SUPPORT_LIB > -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS > -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS > -DQT_DISABLE_DEPRECATED_BEFORE=0x05 > -DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_NO_EXCEPTIONS > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_GUI_LIB > -DQT_CORE_LIB -I. -I../../../../include > -I../../../../include/QtXkbCommonSupport > -I../../../../include/QtXkbCommonSupport/5.15.10 > -I../../../../include/QtXkbCommonSupport/5.15.10/QtXkbCommonSupport > -I../../../../include/QtGui/5.15.10 -I../../../../include/QtGui/5.15.10/QtGui > -I../../../../include/QtCore/5.15.10 > -I../../../../include/QtCore/5.15.10/QtCore -I../../../../include/QtGui > -I../../../../include/QtCore -I.moc -I../../../../mkspecs/linux-g++ -o > .obj/qxkbcommon_3rdparty.o qxkbcommon_3rdparty.cpp > make[5]: Entering directory > '/<>/src/platformsupport/linuxaccessibility' > /<>/src/platformsupport/linuxaccessibility/qdbusxml2cpp_wrapper.sh > -i struct_marshallers_p.h -a deviceeventcontroller_adaptor.h: > dbusxml/DeviceEventController.xml > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -fPIC -std=c++1z -fvisibility=hidden > -fvisibility-inlines-hidden -fno-exceptions -Wall -Wextra -Wvla -Wdate-time > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > -Wno-format-overflow -D_REENTRANT -DQT_NO_LINKED_LIST > -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_CAST_FROM_ASCII > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT > -DQT_BUILD_LINUXACCESSIBILITY_SUPPORT_LIB -DQT_BUILDING_QT > -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT > -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS > -DQT_DISABLE_DEPRECATED_BEFORE=0x05 > -DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_NO_EXCEPTIONS > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG > -DQT_ACCESSIBILITY_SUPPORT_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. > -I../../../include -I../../../include/QtLinuxAccessibilitySupport > -I../../../include/QtLinuxAccessibilitySupport/5.15.10 > -I../../../include/QtLinuxAccessibilitySupport/5.15.10/QtLinuxAccessibilitySupport > -I../../../include/QtAccessibilitySupport > -I../../../include/QtAccessibilitySupport/5.15.10 > -I../../../include/QtAccessibilitySupport/5.15.10/QtAccessibilitySupport > -I../../../include/QtGui/5.15.10 -I../../../include/QtGui/5.15.10/QtGui > -I../../../include/QtCore/5.15.10 -I../../../include/QtCore/5.15.10/QtCore > -I../../../include/QtDBus -I../../../include/QtGui -I../../../include/QtCore > -I.moc -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 >
Processed: rmatrix: ABI change in Matrix 1.6-2
Processing commands for cont...@bugs.debian.org: > affects 1055922 + src:r-cran-tmb Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-tmb > affects 1055922 + src:r-cran-glmmtmb Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-glmmtmb > affects 1055922 + src:r-cran-ggefffects Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-ggefffects > affects 1055922 + src:r-cran-insight Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-insight > affects 1055922 + src:r-cran-irlba Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-irlba > affects 1055922 + src:r-cran-parameters Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-parameters > affects 1055922 + src:r-cran-performance Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-performance > affects 1055922 + src:r-cran-seurat Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-seurat > affects 1055922 + src:r-cran-uwot Bug #1055922 [src:rmatrix] rmatrix: ABI change in Matrix 1.6-2 Added indication that 1055922 affects src:r-cran-uwot > thanks Stopping processing here. Please contact me if you need assistance. -- 1055922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Source: rmatrix Version: 1.6-2-1 Severity: serious X-Debbugs-Cc: debia...@lists.debian.org Hi Dirk I'm opening this bug as a place for discussion and to track the affected packages. It can be closed once rmatrix and its reverse-dependencies are ready to migrate. I've copied your email to the debian-r mailing list [1] below. Regards Graham [1] https://lists.debian.org/debian-r/2023/11/msg00033.html Package Matrix is having a new and energetic maintainer/contributor in Mikael Jagan who is tidying up a few loose corners (and inter alia sent me a patch to RcppEigen that resulted in a coordinated CRAN update of RcppEigen, lme4, and OpenMx). Mikael also identified two sets of packages needed a rebuild in messages to the r-package-devel list (the more-or-less official place in the R Project to ask / discuss package changes, it is a decent to be on) following private mails between him and me. See https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010051.html https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010054.html The first concerns packages using a LinkingTo: Matrix and building against Matrix _headers_. The second concerns caching of S4 signatures (which bit us at work because of SeuratObject [not in Debian] and how I got onto this). Most of these are not in Debian but I think we need binary rebuilds of irlbabecause of headers OpenMx because of headers, a new upstream 2.21.10 is out too TMB because of headers MatrixModels because of S4 caching I would appreciate it if someone could tickle rebuilds. To me a quick informal touch of debian/changelog would do; if someone thinks this needs a formal transition go for it. The R Core team and the CRAN maintainers are aware of the implicit problem with signalling the need for binary rebuilds. They are discussing this, but do not have an answer. Historically, CRAN has informally rebuilt its binaries for windows and macOS, but that of course does not help binary distributors such as us, other Linux distros, Conda, r2u, ... at all.
Bug#1055916: uninstallable in unstable
Package: gedit Version: 44.2-1 Severity: serious Hi, currently, gedit cannot be installed in unstable with this error message from apt: Reading package lists... Building dependency tree... 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. The following information may help to resolve the situation: The following packages have unmet dependencies: libtepl-common : Breaks: libtepl-6-2 but 6.4.0-7 is to be installed E: Unable to correct problems, you have held broken packages. Sebastian Ramacher suggested in #debian-mentors that I file a bug about that against gedit as tepl is involved in an uncoordinated transition that needs action from their respective maintainers. Relevant other bug: https://bugs.debian.org/1055778 Thanks! cheers, josch
Bug#1055914: cp2k: BD-Uninstallable on armel
Source: cp2k Version: 2023.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=cp2k cp2k build-depends on missing: - libdbcsr-dev:armel (>= 2.6.0) libdbcsr-dev is a new build dependency, but it is not available on armel. Cheers -- Sebastian Ramacher
