El 28/1/23 a las 16:50, Adam Borowski escribió:
Control: close 1027364
On Sat, Jan 28, 2023 at 04:31:25PM +0100, Santiago Vila wrote:
retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends on
tzdata)
reopen 1027364
found 0.5.0-2
thanks
Adam, please don't close bugs just because they say "bullseye" in the title.
In most cases, I really meant "bullseye and later".
I've just re-tested:
Distribution: bullseye
Host Architecture: amd64
Source-Version: 0.5.0-2
Status: successful
So the package does build ok. Do you have an example of a build environment
that is not explicitly declared "totally broken" by the Policy (§2.5)?
Policy 4.2 says packages MUST build from source in a build environment
having only essential and build-essential packages.
How do you suggest that I can check whether or not a package meets such
requirement (remember, a MUST requirement) if not by building in a chroot
with only essential and build essential packages?
Please, tell me, how can it be that at the same time:
a) Policy mandates that packages are buildable in a build environment with only
essential
and build essential packages,
and
b) I'm not allowed to build packages in a build environment with only essential
and build
essential packages to check that packages follow policy?
Are you missing the fact that tzdata is not build-essential?
I think you are missing the build-essential definition:
It is not necessary to explicitly specify build-time relationships on a minimal
set of packages that are always needed to compile, link and put in a Debian
package a standard “Hello World!” program written in C or C++. The required
packages are called build-essential, [...]
Do you need tzdata to build a hello world package? No, you don't. Nobody does.
Is tzdata essential? No, it's not essential either.
Therefore, tzdata is not build essential.
And because it's not build essential, one has to put it in build-depends if
you use it during build. It's that simple.
Thanks.
