| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Puppet complained with "Files must be fully qualified" using the file()
function.
Follow-up to 0ea383bf2
|
|
|
|
| |
The service doesn't support TLS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This depends on a newer version of pybugz that's Python 3 compatible
(tested with 0.14) and git_multimail.py, which has already been updated.
Replace token support with API key support, as per the latest pybugz
(and Bugzilla). If an API key is found, it will be used and if not found
it will fall back to username/password. No attempt is made to try to
create an API key in the same way that a token was minted before. Use a
different file name for an API key for coexistence with a token, which
is still used by other programs.
Add a debug flag for enabling more logging to better see when things go
wrong.
Create variables for configuration items.
Log a message when an i18n e-mail is sent.
Do a few little code cleanups.
|
|
|
|
|
| |
Don't try to perform template variable substitution because there are
strings in the file that look like substitutions but aren't.
|
| |
|
|
|
|
|
| |
This file had what looked like an ERB delimiter eaten by Puppet so git
didn't see the right percent placeholder to get the address.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is from https://github.com/mhagger/git-multimail
I've reapplied the changes which avoid some unnecessary error messages
when the summary email address is not configured (used for i18n mails).
This latest upstream version also supports Python 3 although the shebang
is left at Python 2.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
git/softwarekey/binrepo/iurt/maintdb/schedbot/signbot/mga-advisories/mgasoft/mirror
puppet uses usermod which does not handle ldap.
|
|
|
|
|
|
|
| |
Well, everyone in the group.
topic branches should be a bit more collaborative and we just have
to trust people not to abuse this.
|
| |
|
| |
|
|
|
|
|
|
| |
The owners should be trusted to use this with care.
(This is mainly to give TV this power on the drak*/urpm* repos)
|
| |
|
|
|
|
|
|
| |
This really should fix git->bugzilla integration.
mga#14585
|
|
|
|
|
|
|
|
|
|
| |
Our bugzilla no longer supports cookies so we have to use a token
itstead. It's essentially exactly the same as a cookie, but different
therefore meaning we have to handle it ourselves manually.
I don't really get the benefit here, but hey ho.
mga#14585
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is because it's really easy to accidentally push both master
and a tag at the same time, but have master rejected but the tag
succeed (non-fastforward).
A better solution is to not allow tags that introduce new commits
but I'm not sure of the config to allow that so this is a bit of
a short term solution to allow Thierry to fix up a few of his
tags.
|
|
|
|
|
|
| |
If a sysadmin was assigned as a maintainer of a repo, the extra
powers granted to them would actually be overridden which is a
bit useless.
|
| |
|
|
|
|
|
|
| |
This is slightly recursive as this is where the definitions are kept, but
I'll add a readme to the git repo to make sure no-one actually adds definitions
in this tree (although a pre-receive hook would be better to really ban it)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This was a change I missed in an earlier commit.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is from https://github.com/mhagger/git-multimail
I've reapplied my changes which avoid some unnecessary error messages when the summary
email address is not configured (used for i18n mails).
The notable change is to synthesise dates in emails to hopefully fix ordering in
email clients (i.e. with multi-commit pushes).
|
|
|
|
|
|
|
|
|
|
| |
After sending the original email, we send a second email to i18n-reports
detailing any i18n changes.
The method of determining if any changes affect i18n is to look for a
folder (or folders) called '.tx' in the tree. If such folders exist,
then any changes in their parent folders are considered to be relevent
for i18n.
|
|
|
|
|
|
|
| |
When we will send to the i18n-reports ML info about i18n related changes we
will omit the overall summary mail (it's too complext to produce a summary
of only i18n changes) and thus we need to squash this error message which
will not be nice for those pushing changes.
|
| |
|
| |
|
|
|
|
|
| |
This keeps the stall time on a push to something sensible should there be
a problem.
|
| |
|
| |
|
|
|
|
|
| |
Add in notification of the 'on-the-pull' system for mirroring
in post-commit hook.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This means the Last Modified column in cgit will show the date of the last commit
not the date of the last push (which can be completely unrelated, especially when
doing rebases or forced pushes and fixups etc.)
Note: If we stop using rsync for replication then this can be removed and replaced
with a different hook on the receiving side.
|
| |
|