aboutsummaryrefslogtreecommitdiffhomepage
path: root/gbp/scripts/pq_rpm.py
Commit message (Collapse)AuthorAge
* pq-rpm: implement --drop optionMarkus Lehtonen2018-01-17
| | | | | | | Makes it possible to automatically drop the pq-branch after a successful export. Counterpart for the --drop option of (deb) gbp-pq. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
* pq: import pq branch on switchGuido Günther2017-10-20
| | | | Closes: #761166
* pq-rpm: Correctly pass abbrev to format-patchGuido Günther2017-08-22
| | | | broken by 75e18fc5bb4831df924bc708130b0a6ab311a230
* pq: make --abbrev= configurableChris Lamb2017-08-22
| | | | | Closes: #872351 Signed-off-by: Guido Günther <agx@sigxcpu.org>
* pkg: clear __init__.pyGuido Günther2017-08-03
| | | | for readability
* pq_rpm: use binary mode for copyingGuido Günther2017-08-02
| | | | to stay out of conversion troubles
* pq_rpm: clarify doc stringGuido Günther2017-06-24
| | | | | | | | mention RPM and start with a capital letter to make gbp --list-cmds output consistent.
* pq_rpm: flake8 cleanGuido Günther2016-12-07
|
* pq_rpm: use relative path names for patchesGuido Günther2016-12-07
| | | | | | Based on a patch from Tzafrir Cohen Closes: #834582
* Fix new flake8 errorsGuido Günther2016-11-15
| | | | E305 expected 2 blank lines after class or function definition
* pep8/pyflakes cleanupsGuido Günther2016-09-12
|
* Give more instructions when config is unparseableGuido Günther2016-07-04
| | | | | | | | and make return codes and messages consistent. This allows us to move some test code from the component tests to the unit tests which is always nice. Closes: #733640
* buildpackage: Handle Ctrl-C more gracefullyGuido Günther2016-07-04
|
* pq: Report number of imported patchesGuido Günther2016-06-03
|
* Remove unused importsGuido Günther2015-10-23
| | | | Git-Dch: Ignore
* pq_rpm.parse_spec: always set packaging_dirMarkus Lehtonen2015-10-19
| | | | | | | Make sure that the packaging_dir option always points to the directory containing rpm packaging files. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
* Rewrite gbp.tmpfileMarkus Lehtonen2015-08-19
| | | | | | | | | | | | | | | | | | This commit changes the tmpfile module to only contain minimal init_tmpdir() and del_tmpdir() functions, intended to be called at the beginning and end of the scipts. The init function creates a base tempdir and configures the Python tempfile module to use that as the (default) directory for temporary files and directories. Correspondingly, the del function removes the base tempdir and restores the configuration of the tempfile module. The new logic ensures that all temporary files/directories will be created in the desired base tempdir (assuming that no 'dir' argument is given to the tempfile functions). The base tempdir is not removed by del_tmpdir() if a non-empty value of GBP_TMPFILE_NOCLEAN is found in environment. This can be useful e.g. in debugging. Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
* Fix FSF address - thanks rpmlintEvgeni Golov2015-06-22
| | | | use gnu.org/licences instead of a postal address, as suggested by Guido
* Use Python3 compatible syntaxGuido Günther2015-05-28
| | | | Gbp-Dch: Ignore
* Extract exception message in a less arcane wayGuido Günther2015-03-27
|
* Handle ConfigParser -> configparser renameGuido Günther2015-02-20
| | | | | | to work towards Python3 support Gbp-Dch: Ignore
* parse_gbp_commands: support command filteringGuido Günther2015-02-08
| | | | | | | | | When we write out patches to subdirs using a topic we want to filter out this topic from the commit message. Support for this was lost in 7ce15d2434ee42aa5a1afce3d03069c5efb2db1b add it back. Also fix parsing of the deprecated commands.
* Introduce gbp-pq-rpmMarkus Lehtonen2014-12-29
Initial version of gbp-pq-rpm - a tool for managing patch queues for rpm packages. The functionality more or less corresponds to that of the (Debian) gbp-pq. The only major difference probably being (in addition to the obvious of working with .spec files instead of debian/) is that patches are always imported on top of the upstream version, not on top of the packaging branch (which might not even contain any source code). Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Olev Kartau <olev.kartau@intel.com>