Quoting Santiago Vila (2026-05-09 15:22:16) > reopen 1135277 > thanks > > Hello. As strange as it may seem (because I also can see the successful > builds in buildd.debian.org seven days ago), this is still happening: > > error[E0053]: method `debug` has an incompatible type for trait > > I've put an updated build log in the same directory as before: > > https://people.debian.org/~sanvila/build-logs/202604/ > > I have no idea why this happens. It could be a circular depends, or an > undeclared build-dependency on ca-certificates, or who knows. > > Maybe this happens randomly in general but always in some cases. > My build environment is made of machines with 1 and 2 CPUs, and I have > never been able to build this package since it was uploaded for > unstable for the first time. This is my combined build history: > > Status: failed sass-grass_0.13.4-2_amd64-20260428T205705.530Z > Status: failed sass-grass_0.13.4-2_amd64-20260428T205708.210Z > Status: failed sass-grass_0.13.4-2_amd64-20260430T122403.947Z > Status: failed sass-grass_0.13.4-2_amd64-20260430T122403.698Z > Status: failed sass-grass_0.13.4-2_amd64-20260430T122403.607Z > Status: failed sass-grass_0.13.4-2_amd64-20260430T122403.574Z > Status: failed sass-grass_0.13.4-2_amd64-20260502T045434.394Z > Status: failed sass-grass_0.13.4-2_amd64-20260502T050050.158Z > Status: failed sass-grass_0.13.4-3_amd64-20260502T151309.299Z > Status: failed sass-grass_0.13.4-3_amd64-20260502T151310.450Z > Status: failed sass-grass_0.13.4-3_amd64-20260509T050142.135Z > Status: failed sass-grass_0.13.4-3_amd64-20260509T050840.219Z
It seems fishy to me for a random error to persistently fail at your setup and (with only few samples, but still) consistently succeed on Debian buildds. I asked a gAI to reason on this bugreport, and after first reaching for your suggestion that the patch was sensible, it agreed with my own understanding that it was in fact not changing anything, and it then pointed to caching issues in the build infrastructure as a possible cause and Debian packaging system being another. Since there seems to be a clear difference in build environments and no difference in Debian tooling, I lean towards the issue here being some caching stuff in your system different from both mine and those of Debian build daemons. > While we are at it: Could you please make the repository public in > salsa? This automatic checking tool is unable to access: > > https://qa.debian.org/cgi-bin/vcswatch?package=sass-grass Fixed now with release packaging release 0.13.4-5. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
