Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202609/

Note: The failure happens randomly, but I've noticed that the
failure rate is a lot higher when the machine has a single CPU,
therefore I recommend GRUB_CMDLINE_LINUX="nr_cpus=1" to reproduce.
(If that's not enough I always offer a VM to reproduce).

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:golang-cel-cel-go, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
=== RUN   TestContextEval
    cel_test.go:1266: Got result 1975, wanted timeout error
--- FAIL: TestContextEval (0.01s)
[...]
=== RUN   TestInterpreter_InterruptableEval
    interpreter_test.go:2112: Got true, wanted operation interrupted error
--- FAIL: TestInterpreter_InterruptableEval (0.01s)

We believe that the bug you reported is fixed in the latest version of
golang-cel-cel-go, 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 1146551@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Lee (李健秋) <ajqlee@debian.org> (supplier of updated golang-cel-cel-go 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 03 Sep 2026 16:27:00 +0200
Source: golang-cel-cel-go
Architecture: source
Version: 0.32.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Changed-By: Andrew Lee (李健秋) <ajqlee@debian.org>
Closes: 1146551
Changes:
 golang-cel-cel-go (0.32.0+ds-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/salsa-ci.yml: switch to standard salsa-ci.
   * debian/rules: disable specific flaky tests. (Closes: #1146551)
   * debian/rules: Allow tests failed on 32bits DEB_HOST_ARCH_BITS.
   * debian/control: build-deps on dh-sequence-single-binary.
Checksums-Sha1:
 5f19d78f165817b03a5b5a506f08cd7239ee0476 2442 golang-cel-cel-go_0.32.0+ds-2.dsc
 fe0e51882350829047d598e4a23236e9e489807b 648452 golang-cel-cel-go_0.32.0+ds.orig.tar.xz
 c66d055ed2f934fc49eb4495e0d783b9f5c7dbbc 34276 golang-cel-cel-go_0.32.0+ds-2.debian.tar.xz
 6f3a139348e65b6dbc50cf2d8a8216e1b6a3854a 6918 golang-cel-cel-go_0.32.0+ds-2_source.buildinfo
Checksums-Sha256:
 68a17c91a76edebc1d269a4065486ebbd6a2e911fd523515ccea27d021749aae 2442 golang-cel-cel-go_0.32.0+ds-2.dsc
 866c7c9e3c1423c9e286dc6f62b3deec19eb2f951c1ea0c5a34671e80ac534fb 648452 golang-cel-cel-go_0.32.0+ds.orig.tar.xz
 5a4740efc6f8d4e1f2efddb70f923a9857d82271c0478a0a253f01fd3629e160 34276 golang-cel-cel-go_0.32.0+ds-2.debian.tar.xz
 3b68025306a9db10afbde8d2bf8aa4c253585e987f262c666756fc3668b496ab 6918 golang-cel-cel-go_0.32.0+ds-2_source.buildinfo
Files:
 1184acf1318b7001a1e70952f86d7360 2442 golang optional golang-cel-cel-go_0.32.0+ds-2.dsc
 b7a9f236285fce45aa7d22953a719a5b 648452 golang optional golang-cel-cel-go_0.32.0+ds.orig.tar.xz
 67d89f7ed2aaad0017ffdf7798f00972 34276 golang optional golang-cel-cel-go_0.32.0+ds-2.debian.tar.xz
 cce6070756de1b491f90f4011a5017ad 6918 golang optional golang-cel-cel-go_0.32.0+ds-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE703UlH90QYpfEyJV58vhUqwX+XMFAmqZho4ACgkQ58vhUqwX
+XMsFg/8DxcVnmvtbelpnQc4qcHSeeLrMsQ1VfSJ1ZLZJmpsysyvQEi01zEIOU13
1WVxEzVMWfdotCLKvRgRJVkDYXUFdi+LVFarpsPBWEzGshTfB3brfZKiAh0f47eG
7TJWcW09v1dZKS51pzZDCz+cEIc+uqUPmYXPtSpUjMNSE9U432Qmr199W3pE8Hm0
iWLX9wzI2QHd8SmWB+RhSfyvpzSU0ocu7bTB+grRjX572xO4sWz6uYh/jTQVCZBi
NYvViWX74XVUjYrqwnr6Kupqgkyy76uUdC7h1EYNzN9ocWMEaVsMJn0SoJv59djO
1jUwe/nBRbuFV7wWJ0sYx7ms8hFCSsZW3MSjz4hTpSmB+wZWGAdRpVdpcIxiAQKG
szD8FCoElqUTlmcJtB5YQH81zRwDMvCfiS8zJ4TAmYmRna+SC9HA5KaBf3on9s/a
OMhA7ZaOJQ6mmoPntgGSxziB6QlQsvq8xHrqUXwAQdIuxBWH8mC5faej2sy3L4k0
9pCN4NZaT1DNRx5Bt6VPuIvcsNGfuJmGGkYe8t0ybzwX7Zz8ZllnVFb5fOY1wwMt
HQVj2Hbie90TGX4IgCT7o97hL0dw78pmHZm5SDpN49DtmjNT6twOdDO63od63gTK
lc+5uSHyCtDKmOse96p8CUrOX3Wb5IcEWpOdBJ+Yn2DdW4DhnW8=
=dhai
-----END PGP SIGNATURE-----

Hi.

Thanks a lot for the quick fix.

The tests which failed for me were these two:

but I see you have disabled also "TestConcurrentEval".

Did this test really fail somewhere other than the bug I reported?
(ci.debian.net maybe? your own PC?)

Thanks.

Hi Saniago,

Yes, it was also failed in 32bits tests. So I disabled it as well.

Best regards,

If you have, I could even forward the issue upstream.

The thing is that I plan to do an upload for trixie-proposed-updates
fixing the two tests which failed for me, as they also fail in trixie.

Should I also disable "TestConcurrentEval" in trixie, or it does not matter?

Thanks.

But I end up allow tests FAIL on 32 bits in debian/rules:
```
# Allow tests failed on 32bits DEB_HOST_ARCH_BITS
ifeq ($(DEB_HOST_ARCH_BITS),32)
        GOLANG_PROTOBUF_REGISTRATION_CONFLICT=warn dh_auto_test --
-short || true
else
```

So re-enable this Test should be fine for 32 bits.
Mind to do a team upload for this?

Best regards,

Yes, will do.

Thanks a lot.

This is now done.

But now the watch file does not work...

I'm not brave enough to fix that (does the project need another rename?),
so I did the upload and then I've filed a separate bug for that (#1147279).

Thanks.

forwarded 1146551 https://github.com/cel-expr/cel-go/issues/1475
thanks

Even if already fixed this by disabling the tests, I'm curious about
what upstream can say about it.

Hi Santiago,

Here is upstream explaination on the path and version relationships;
https://github.com/cel-expr/cel-go/issues/1329#issuecomment-5430413293

Our module-aware offline builds depend on matching Go import paths
directly to installed Debian packages on filesystem. Because of this,
we want to rename the Debian package to match its Go import path. This
keeps the package name stable as long as the import path stays the
same.

If upstream changed the import path later, we will create fork a new
package for the new path and keep the old package, so existing
reverse-depends does not break. Once no other packages need the old
version, Simon's zombie automated collection script will clean it up.

Best regards,