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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
***********************************************
Ubuntu Distributed Development package importer
***********************************************
This tool imports source from Debian and Ubuntu source packages into Bazaar
branches.
It provides the ``http://package-import.ubuntu.com/`` service. You don't
need to run this code to use the branches produced by it.
For Ubuntu-developer-oriented documentation, see
<https://wiki.ubuntu.com/DistributedDevelopment/>.
Overview
********
``list-packages`` gets a list of all source packages in interesting releases
from Launchpad.
Deployment
**********
The package importer runs mostly unattended but some operations are still
handled manually by udd devs and a few ones requires help from a losa.
All the scripts used to run the package importer are in the lp:udd branch.
latest version
--------------
On ``jubany``, the udd scripts are located in
``/srv/package-import.canonical.com/new/scripts``. Run ``bzr update`` there
to deploy the most recent version. All merge proposals are landed in
``lp:udd`` after approval but deployment is done when time and circumstances
permit.
mass-import
-----------
The ``etc-init.d-mass-import`` script, installed into
``/etc/init.d/mass-import`` should be kept in sync. When changes are made to
this file, a losa should inspect them and install the new version.
It can be run either by root, or as the pkg_import user.
To start it simply::
./etc-init.d-mass-import start
To stop it typically you will want::
./etc-init.d-mass-import graceful-stop
If graceful stop is not possible, you may have to use the more brutal::
./etc-init.d-mass-import stop
but don't forget to requeue the killed imports later.
import-package
--------------
The ``import-package`` script is generally called in a subprocess by
``mass-import``.
For debug purposes, it can also be run locally with additional options:
* ``--no_push``: Do not push the updated branches,
* ``--keep-temp``: Keep temporary directories,
* ``--local-branches``: Use loca copies of lp branches (created if needed),
* ``UDD_DEBUG_HTTP``: Environment variable controlling the display on stdout
of the launchpad http API calls,
* more options in ``udd/scripts/import_package.py``.
builddeb
--------
The ``bzr-builddeb`` plugin is deployed (when needed) from
``lp:bzr-builddeb`` under
``/srv/package-import.canonical.com/new/scripts/plugins/builddeb``.
.. vim: ft=rst
|