> During a rebuild of all packages in unstable, your package failed to build:
It appears the function in question is a variadic function. The documentation for curl_easy_setopt says. "That parameter can be a long, a function pointer, an object pointer or a curl_off_t, depending on what the specific option expects." ( https://curl.se/libcurl/c/curl_easy_setopt.html ) It looks like the new version of curl added some compile time checking (when built with gcc) that the parameter is what was expected, and throws a warning if it's wrong. This package uses -Werror which turns that warning into an error. And the example for CURLOPT_PROXYTYPE shows the value being cast to a long before being passed to curl_easy_setopt. https://curl.se/libcurl/c/CURLOPT_PROXYTYPE.html The affected code seems to be from an embedded code copy of git, doing some searching the issue does NOT seem to be fixed in git upstream. Passing a parameter of the wrong type to a variadic function can have consequences that vary by architecture. It's possible that the right thing will happen by "accident", either because the types are in-fact the same size, or for example a 32-bit value may be converted to a 64-bit value where the top bits are garbage and the bottom bits are correct this may then be converted back to a 32-bit value throwing away the garbage. But it's equally possible the right thing will not happen, that the variadic function will end up dealing with garabage and will misbehave or crash. I will file a bug report against the git package with further followup. I think we probably want to get this fixed in git first, then port the patch over to the git-cinnabar package.
