• Bug#1095932: openjdk-8: Misbuilds packages when calling only binary-* t

    From Thorsten Glaser@21:1/5 to Guillem Jover on Fri Feb 14 01:40:01 2025
    On Fri, 14 Feb 2025, Guillem Jover wrote:

    As was discovered in bug #1095746, this package misbuilds when calling
    for example «fakeroot debian/rules binary-arch» w/o first calling >«debian/rules build-arch», which is a policy violation:

    Yes. I noticed yesterday (or so… memory is a bit fuzzy) and had that
    on my radar. (Is this the counter-bugreport?)

    Do you, by chance, have an idea if Doko fixed that on any of his other packages, so I could just cherry-pick that?

    (I have a vague guess that replacing one := with = might fix it, but
    this package takes a huge amount of ressources to build…)

    bye,
    //mirabilos
    --
    “ah that reminds me, thanks for the stellar entertainment that you and certain
    other people provide on the Debian mailing lists │ sole reason I subscribed to
    them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
    not strike me as a place for good humour, much less German admin-style humour”

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Guillem Jover@21:1/5 to All on Fri Feb 14 01:20:02 2025
    Source: openjdk-8
    Source-Version: 8u442-ga-2
    Severity: serious

    Hi!

    As was discovered in bug #1095746, this package misbuilds when calling
    for example «fakeroot debian/rules binary-arch» w/o first calling «debian/rules build-arch», which is a policy violation:

    ,---
    "binary" (required), "binary-arch" (required), "binary-indep" (required)

    The "binary" target must be all that is necessary for the user to
    build the binary package(s) produced from this source package. It
    is split into two parts: "binary-arch" builds the binary packages
    which are specific to a particular architecture, and "binary-indep"
    builds those which are not.

    "binary" may be (and commonly is) a target with no commands which
    simply depends on "binary-arch" and "binary-indep".

    Both "binary-*" targets should depend on the "build" target, or on
    the appropriate "build-arch" or "build-indep" target, so that the
    package is built if it has not been already. It should then create
    the relevant binary package(s), using "dpkg-gencontrol" to make
    their control files and "dpkg-deb" to build them and place them in
    the parent of the top level directory.

    […]
    `---

    Thanks,
    Guillem

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)