• Fwd: Bug#956931: autopkgtest: Build profiles support for autopkgtest

    From Jiri Palecek@21:1/5 to All on Thu Apr 16 23:30:01 2020
    This is a multi-part message in MIME format.
    -------- Forwarded Message --------
    Subject: Bug#956931: autopkgtest: Build profiles support for autopkgtest Resent-Date: Thu, 16 Apr 2020 20:42:01 +0000
    Resent-From: Jiri Palecek <jpalecek@web.de>
    Resent-To: debian-bugs-dist@lists.debian.org
    Resent-CC: jpalecek@web.de, Debian CI team <team+ci@tracker.debian.org> Date: Thu, 16 Apr 2020 22:38:07 +0200
    From: Jiri Palecek <jpalecek@web.de>
    Reply-To: Jiri Palecek <jpalecek@web.de>, 956931@bugs.debian.org
    To: Debian Bug Tracking System <submit@bugs.debian.org>



    Package: autopkgtest
    Version: 5.12.2~6.gbp89ad39
    Severity: wishlist

    Dear Maintainer,

    with the latest and greatest changes in dpkg, I think it would be nice
    if autopkgtest followed suit. Particularly, it would be advantageous to
    support running and building tests in autopkgtest under build profiles
    (esp. nodoc!). This would allow for smaller test footprint, less
    packages to pull (ie. you don't need texlive on the testbed), and faster building of the packages.

    I prepared a patch implementing such a change here: https://salsa.debian.org/jpalecek-guest/autopkgtest/-/commit/6275da59305d6e836cb3558f9f442479eb24fc95

    The patch is functional, albeit incomplete due to missing documentation.

    The real issue is the control file format. In my patch, I use an extra
    stanza to specify build profiles, like this:

    Build-Profiles: nodoc

    Tests: run-some-tests
    <<<

    I chose this format, because adding the specification to some of the
    tests would be IMHO misleading: the build profile applies to all of the
    tests indiscriminately, not to any particular one. Also, I chose to
    apply them to all @builddep@ dependencies as well.

    However, there is a problem about this: it makes the control file format non-backwards-compatible. Particularly, dpkg needs to be patched or it
    will croak on packages with such d/t/control. Maybe, some artificial
    Tests: line like

    Tests: *

    could be added? That would make the change backwards compatible. Dpkg
    still needs to be patched, but the change would be rather minimal.

    What do you think about this proposal? Please comment here or on
    salsa. I'm also CC-ing the dpkg developers, since it concerns them.

    Regards
    Jiri Palecek

    -- System Information:
    Debian Release: 10.0
    APT prefers testing
    APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
    'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
    Architecture: i386 (i686)
    Foreign Architectures: amd64

    Kernel: Linux 5.5.0-rc5-686-pae (SMP w/2 CPU cores)
    Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
    Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ (charmap=ISO-8859-2)
    Shell: /bin/sh linked to /bin/dash
    Init: systemd (via /run/systemd/system)

    Versions of packages autopkgtest depends on:
    ii apt-utils 2.0.1
    ii libdpkg-perl 1.20.0+nmu2~1.gbpcd9614
    ii procps 2:3.3.16-4
    ii python3 3.8.2-2
    ii python3-debian 0.1.36

    Versions of packages autopkgtest recommends:
    pn autodep8 <none>

    Versions of packages autopkgtest suggests:
    pn lxc <none>
    pn lxd <none>
    pn ovmf <none>
    pn qemu-efi-aarch64 <none>
    pn qemu-efi-arm <none>
    pn qemu-system <none>
    ii qemu-utils 1:4.2-2
    ii schroot 1.6.10-9
    pn vmdb2 <none>

    -- no debconf information

    <html>
    <head>

    <meta http-equiv="content-type" content="text/html; charset=windows-1252">
    </head>
    <body>
    <p><br>
    </p>
    <div class="moz-forward-container"><br>
    <br>
    -------- Forwarded Message --------
    <table class="moz-email-headers-table" cellspacing="0"
    cellpadding="0" border="0">
    <tbody>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
    </th>
    <td>Bug#956931: autopkgtest: Build profiles support for
    autopkgtest</td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Resent-Date:
    </th>
    <td>Thu, 16 Apr 2020 20:42:01 +0000</td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Resent-From:
    </th>
    <td>Jiri Palecek <a class="moz-txt-link-rfc2396E" href="mailto:jpalecek@web.de">&lt;jpalecek@web.de&gt;</a></td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Resent-To:
    </th>
    <td><a class="moz-txt-link-abbreviated" href="mailto:debian-bugs-dist@lists.debian.org">debian-bugs-dist@lists.debian.org</a></td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Resent-CC:
    </th>
    <td><a class="moz-txt-link-abbreviated" href="mailto:jpalecek@web.de">jpalecek@web.de</a>, Debian CI team
    <a class="moz-txt-link-rfc2396E" href="mailto:team+ci@tracker.debian.org">&lt;team+ci@tracker.debian.org&gt;</a></td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
    <td>Thu, 16 Apr 2020 22:38:07 +0200</td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
    <td>Jiri Palecek <a class="moz-txt-link-rfc2396E" href="mailto:jpalecek@web.de">&lt;jpalecek@web.de&gt;</a></td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Reply-To:
    </th>
    <td>Jiri Palecek <a class="moz-txt-link-rfc2396E" href="mailto:jpalecek@web.de">&lt;jpalecek@web.de&gt;</a>,
    <a class="moz-txt-link-abbreviated" href="mailto:956931@bugs.debian.org">956931@bugs.debian.org</a></td>
    </tr>
    <tr>
    <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
    <td>Debian Bug Tracking System
    <a class="moz-txt-link-rfc2396E" href="mailto:submit@bugs.debian.org">&lt;submit@bugs.debian.org&gt;</a></td>
    </tr>
    </tbody>
    </table>
    <br>
    <br>
    Package: autopkgtest<br>
    Version: 5.12.2~6.gbp89ad39<br>
    Severity: wishlist<br>
    <br>
    Dear Maintainer,<br>
    <br>
    with the latest and greatest changes in dpkg, I think it would be
    nice<br>
    if autopkgtest followed suit. Particularly, it would be
    advantageous to<br>
    support running and building tests in autopkgtest under build
    profiles<br>
    (esp. nodoc!). This would allow for smaller test footprint, less<br>
    packages to pull (ie. you don't need texlive on the testbed), and
    faster<br>
    building of the packages.<br>
    <br>
    I prepared a patch implementing such a change here:<br>
    <a class="moz-txt-link-freetext" href="https://salsa.debian.org/jpalecek-guest/autopkgtest/-/commit/6275da59305d6e836cb3558f9f442479eb24fc95">https://salsa.debian.org/jpalecek-guest/autopkgtest/-/commit/6275da59305d6e836cb3558f9f442479eb24fc95</a><br>
    <br>
    The patch is functional, albeit incomplete due to missing
    documentation.<br>
    <br>
    The real issue is the control file format. In my patch, I use an
    extra<br>
    stanza to specify build profiles, like this:<br>
    <br>
    <blockquote type="cite">
    <pre class="moz-quote-pre" wrap=""><blockquote type="cite"><pre class="moz-quote-pre" wrap=""><blockquote type="cite"><pre class="moz-quote-pre" wrap="">
    </pre></blockquote></pre></blockquote></pre>
    </blockquote>
    Build-Profiles: nodoc<br>
    <br>
    Tests: run-some-tests<br>
    &lt;&lt;&lt;<br>
    <br>
    I chose this format, because adding the specification to some of
    the<br>
    tests would be IMHO misleading: the build profile applies to all
    of the<br>
    tests indiscriminately, not to any particular one. Also, I chose
    to<br>
    apply them to all @builddep@ dependencies as well.<br>
    <br>
    However, there is a problem about this: it makes the control file
    format<br>
    non-backwards-compatible. Particularly, dpkg needs to be patched
    or it<br>
    will croak on packages with such d/t/control. Maybe, some
    artificial<br>
    Tests: line like<br>
    <br>
    Tests: *<br>
    <br>
    could be added? That would make the change backwards compatible.
    Dpkg<br>
    still needs to be patched, but the change would be rather minimal.<br>
    <br>
    What do you think about this proposal? Please comment here or on<br>
    salsa. I'm also CC-ing the dpkg developers, since it concerns
    them.<br>
    <br>
    Regards<br>
    Jiri Palecek<br>
    <br>
    -- System Information:<br>
    Debian Release: 10.0<br>
    APT prefers testing<br>
    APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
    'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'),
    (1, 'experimental')<br>
    Architecture: i386 (i686)<br>
    Foreign Architectures: amd64<br>
    <br>
    Kernel: Linux 5.5.0-rc5-686-pae (SMP w/2 CPU cores)<br>
    Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
    TAINT_UNSIGNED_MODULE<br>
    Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2),
    LANGUAGE=cs_CZ (charmap=ISO-8859-2)<br>
    Shell: /bin/sh linked to /bin/dash<br>
    Init: systemd (via /run/systemd/system)<br>
    <br>
    Versions of packages autopkgtest depends on:<br>
    ii apt-utils 2.0.1<br>
    ii libdpkg-perl 1.20.0+nmu2~1.gbpcd9614<br>
    ii procps 2:3.3.16-4<br>
    ii python3 3.8.2-2<br>
    ii python3-debian 0.1.36<br>
    <br>
    Versions of packages autopkgtest recommends:<br>
    pn autodep8 &lt;none&gt;<br>
    <br>
    Versions of packages autopkgtest suggests:<br>
    pn lxc &lt;none&gt;<br>
    pn lxd &lt;none&gt;<br>
    pn ovmf &lt;none&gt;<br>
    pn qemu-efi-aarch64 &lt;none&gt;<br>
    pn qemu-efi-arm &lt;none&gt;<br>
    pn qemu-system &lt;none&gt;<br>
    ii qemu-utils 1:4.2-2<br>
    ii schroot 1.6.10-9<br>
    pn vmdb2 &lt;none&gt;<br>
    <br>
    -- no debconf information<br>
    </div>
    </body>
    </html>

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