On Mon, Sep 03, 2018 at 06:29:34PM +0200, Michael Adam wrote:
On Mon, Sep 3, 2018 at 5:23 PM, Peter Robinson
<pbrobinson(a)gmail.com> wrote:
> On Mon, Sep 3, 2018 at 4:07 PM Michael Adam <madam(a)redhat.com> wrote:
> >
> > Hi all,
> >
> > Tinyproxy just released a new version 1.10 which is has been overdue
> > and containes 2 CVE fixes apart from several enhancements.
> >
> > I created builds for rawhide already.
> >
> > I was wondering if it is still possible to get tinyproxy to this
> important
> > update in f29, since no other packages depend on it, afaict.
> >
> > If so, what do I do? Just update the scm branch and bring it in through
> Bodhi?
>
Thanks for the swift response!
(And apologies for any cluelessness about newer aspects of the fedora
process - it's been a while since i did these things, and it worked a little
differently then...)
> Sounds like a reasonable course of action. Is it backward compatible
> in terms of any interface people might use?
There are a few config file additions.
The location of the binary has changed from /usr/sbin
to /usr/bin . Otherwise no Interfaces i'm aware of.
You should create a compat symlink from the old location to the new
location, at least in the stable releases, in case somebody calls the
binary by path.
> If so once it's baked in
> f29 for a bit, we're in freeze atm any so it won't progress from
> updates-testing -> stable until Beta gets signed off, you might want
> to consider pushing to stable releases too due to CVEs
>
Ok, so can you or s/o confirm next steps:
- bring it to the f29 scm
- build
- add it to bodhi and wait for a while
- possibly push to stable after some time
correct?
Yes, this looks correct.
Zbyszek