umt emits some specialized warnings on a per package basis but only
during `umt check`. This is late in the update preparation process, and
often a preparer has already tripped over some of these issues before
they even get to the point of running `umt check`.
To address this, also emit the warnings during `umt download`, when
someone is at the beginning of preparing an update, and will hopefully
take them into account when doing the preparation.
Signed-off-by: Steve Beattie <email address hidden>
Signed-off-by: Steve Beattie <email address hidden>
e77fabc...
by
"Leonidas S. Barbosa" <leo.barbosa@canonical>
Improving a bit the comment txt
e168e7f...
by
"Leonidas S. Barbosa" <leo.barbosa@canonical>
Adding a check for mismatch in destination release versus changelog
There are cases where one pass the destination:<release> while doing a umt upload.
For cases where one miss type the release, by e.g: esm-infra:focal, where the package to be updated
was in fact a xenial one it can cause a bit of disaster.
This patch fix it adding a check for theses cases.
umt qrt: Be smarter about how we tell apt to install binary packages
Use --only-upgrade so that apt won't install every single binary package
which we specify, only those which are already installed (and since we run
./install-packages ./test-xxxx.py beforehand the QRT test script should
have ensured we already have the required packages installed for the
test). Hence remove the --exclude-binaries option from umt qrt as this
shouldn't be needed anymore as --only-upgrade should DTRT to avoid
installing say incompatible binary packages from the same source package
etc.
It seems that this check is no longer needed
since dpkg-buildpackage handles the case where
patches are already applied even for quilt 1.0
by performing a pop -a.
