With ubuntu latest, python gtk2 dev package is not found
anymore:
E: Unable to locate package python-gtk2-dev
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
The upstream version is lacking a maintainer. So, let's use
a version from my own repository, with has all packages updated
and works fine when called via workflow_dispatch.
With that, we can get rid of an attempt to write a logic
like that, half-implemented under update_release.yml.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
This script is not complete, but it seems that the only way
for a new script to be tested is to have it merged first
at master. So, later patches will fix any issues that it
may have.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
When there is a PR and a push happens, two events doing the same
thing is triggered. Fix that.
While here, drop the manual even trigger. It is useless, as it
will just repeat the same task from the same push.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
In order to avoid triggering actions on other projects,
tag the new releases as pre-releases.
This will be manually overrided after the release
creation.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Instead of using pbuilder, let's use the same script that
will be used to generate a release.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Ubuntu 18.04 (ubuntu-latest) is older than
debhelper-compat (= 12). While we could change it, as
ubuntu-latest will soon be upgraded to point to ubuntu-20.04,
let's just use it instead.
While here, do some minor improvements at the build procedure.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
While pbuilder helps to solve some things and to create a
clean build environment, the current procedure has some
issues with regards to version numbering: basically, it
expects that the ZBar version to be the one from the Ubuntu
repository (0.23.1).
While this is ok for CI bots, it will cause issues if minor
changes. The package names will also be weird.
So, let's use debuild instead. This requires a small trick,
though:
dh_shlibdeps will start complaing for each new symbol, due to
SONAME debian rules. So, we need to patch debian rules to
make it ignore them.
Also, the script needs to ensure that the same version number
as defined at configure.ac will be at debian/changelog.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Instead of creating the release manually, add its creation
logic to be built inside the workflow.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
It is very hard to develop a workflow if it can't be manually
trigged. That's specially interesting for release workflows.
So, add an option to be able to manually trigger them via
GUI.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
There's no need to add some configure options here, as
configure should be able to auto-detect them.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Split into two jobs, in order to allow running it in parallel,
and cleanup the steps names.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Change the Windows matrix for it to generate ZBar with
4 different environments:
- i386, VfW
- i386, DShow
- x86_64, VfW
- x86_64, DShow
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
While it is easier to develop it in separate, let's merge
to a single CI file, as this helps maintaing it.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Instead of keeping one action per target, place them on a common
file.
That makes easier to maintain and to see the status once the
action runs.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
