File: debdiff.rst

package info (click to toggle)
debusine 0.14.2
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 15,200 kB
  • sloc: python: 195,951; sh: 849; javascript: 335; makefile: 116
file content (49 lines) | stat: -rw-r--r-- 1,844 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
.. task:: DebDiff

DebDiff task
------------

A task to compute the differences between two source or binary Debian packages
using the ``debdiff`` utility.

The ``task_data`` associated to this task can contain the following keys:

* ``input`` (required): a dictionary describing the input data

  * ``source_artifacts`` (optional): a list with two elements (original, new).
    Each element is a :ref:`lookup-single` pointing to a
    :artifact:`debian:source-package` artifact.
  * ``binary_artifacts`` (optional): a list with two elements (original, new).
    Each element is a :ref:`lookup-multiple` pointing to
    :artifact:`debian:upload` or :artifact:`debian:binary-package`
    artifacts. If the lookup returns multiple artifacts, they must be of
    category :artifact:`debian:binary-package`.

The task computes dynamic metadata as:

.. dynamic_data::
  :method: debusine.tasks.debdiff::DebDiff.build_dynamic_data


.. note::

  Note that exactly one of ``source_artifacts`` or ``binary_artifacts`` is required.

* ``extra_flags`` (optional): a list of flags to be passed to the debdiff command, such as ``--nocontrol`` or ``--diffstat``.
  If an unsupported flag is passed then the request will fail.

* ``backend`` (optional, defaults to ``unshare``).
  If ``auto``, the task uses the default.
  Supported backends: ``incus-lxc``, ``incus-vm``, and ``unshare``.

* ``environment`` (:ref:`lookup-single` with default category
  :collection:`debian:environments`, required): artifact that will be used
  to run ``debdiff`` (it will be installed if necessary).

* ``build_architecture`` (required): the architecture that we want to run
  ``debdiff``.

The ``debdiff`` output will be provided as a new :artifact:`debian:debdiff`
artifact.

The task returns success if ``debdiff`` returns an exit code of 0 or 1, and failure otherwise.