Robbie Harwood
88ba66fe53
New upstream release - 1.16.1
2018-05-04 14:59:45 +00:00
Robbie Harwood
9869daa1e8
New upstream release (1.16)
...
- No changes from beta2
- Add spec file support for COPR
2017-12-06 18:07:52 +00:00
Robbie Harwood
6f4f842e5f
New upstream prerelease (1.16-beta2)
2017-11-27 22:15:31 +00:00
Robbie Harwood
533a73fdd1
New upstream prerelease (1.16-beta1)
2017-10-05 20:29:13 +00:00
Robbie Harwood
f1e535bb81
New upstream release - krb5-1.15.2
...
Adjust patches as appropriate
2017-09-25 19:24:33 +00:00
Robbie Harwood
58aed41605
Fix custom build with -DDEBUG
2017-06-07 15:18:05 +00:00
Robbie Harwood
2a20da0e2a
New upstream release - 1.15.1
2017-03-04 00:34:47 +00:00
Robbie Harwood
621f3cf2e6
Add free hook to KDB; increments KDB version
...
Add KDB version flag.
All patches are touched because git made the hash lengths in patches longer.
2017-01-20 18:07:42 -05:00
Robbie Harwood
be80cb9861
New upstream release
2016-12-05 20:52:58 +00:00
Robbie Harwood
c3f7090334
New upstream release
2016-11-16 21:22:01 +00:00
Robbie Harwood
442bc9dfe4
Ensure we can build with the new CFLAGS
...
Also remove the git versioning in patches.
2016-11-10 20:32:41 +00:00
Robbie Harwood
821dac42ed
Upstream release 1.15-beta1
...
Also update selinux with RHEL hygene.
Resolves : #1314096
2016-10-20 23:34:55 +00:00
Robbie Harwood
32ef372877
Backport getrandom() support and remove patch numbering
2016-09-22 19:39:24 +00:00
Robbie Harwood
14f028579d
New upstream release and integrate with external git
2016-09-19 23:49:31 +00:00
Robbie Harwood (frozencemetery)
a89bdde4da
Revert "New upstream version: krb5-1.14-alpha1"
...
This reverts commit 1138991893
.
2015-10-01 18:33:34 +00:00
Robbie Harwood (frozencemetery)
1138991893
New upstream version: krb5-1.14-alpha1
...
Drop patches that have since been applied. Create new patches as
needed.
2015-09-24 17:57:53 +00:00
Nalin Dahyabhai
dc293b3d84
Add a hackish attempt at a workaround for #961235
...
Add a patch to create /run/user/0 if we're trying to resolve a
DIR: ccache somewhere below it and neither the target location
nor /run/user/0 exist yet.
The better workaround is to set the location's owner to "linger"
via logind, since even after we do what we're doing here, if
the user logs in and logs back out, our location is still removed.
2013-05-30 12:26:42 -04:00