sudo dnf upgrade --advisory=FEDORA-EPEL-2018-31ccd7aee3
This update has been submitted for testing by remi.
This update has obsoleted php-tcpdf-6.2.22-1.el7, and has inherited its bugs and notes.
since 6.2.2 which was the prior fedora package (see https://bodhi.fedoraproject.org/updates/?packages=php-tcpdf) there have been the fixes:
Version 6.2.25: Fix support for image URLs.
Version 6.2.24: Support remote urls when checking if file exists.
Version 6.2.23: Simplify file_exists function.
Do you know which of these fixes is a security fix?
@muench, read the above changelog...
Version 6.2.20: Fix for security vulnerability: ...
IIUC other are regression fix.
Sorry my mistake, I wrote since 6.2.2 but i meant 6.2.22 (which is the last fedora package before this security update). The security fix from Version 6.2.20 you mentioned was already referenced in the 6.2.22 release (see https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-4255a1292d)
Previous update was obsoleted by this one, so this one keep the security flag for the fix in 6.2.20
This update has been pushed to testing.
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for batched by remi.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Comment fields support Fedora-Flavored Markdown.
Text fields in Bodhi2 support an
version of markdown.
This is a cheat sheet for your reference.
You can do headers by underlining or by prefixing with the # character:
This is an H1
This is an H2
# This is another H1
## This is another H2
You can do blockquotes using email-style prefixes with the > character:
> This is a quotation
> over many lines
> > and it can be nested(!)
Lists work like you'd expect, by prefixing with any of the *, +, or - characters:
Check out this list:
* a list..
You need a blank line between a paragraph and the start of a list for the renderer to pick up on it.
Emphasis can be added like this:
You can save your code references from being misinterpreted as emphasis by surrounding them with backtick characters (`):
Use `the_best_function()` and _not_ that crummy one.
Links look like this:
..but we also support bare links if you just provide a URL.
You can create code blocks by indenting
every line of the block by at least 4 spaces or 1 tab.
Here is a code block:
for i in range(4):
You can reference bug reports by simply writing something of the form tracker#ticketid.
This fixes PHP#1234 and Python#2345
... we will automatically generate links to the tickets in the appropriate trackers in place.
The supported bug tracker prefixes are: (these are all case-insensitive)
And you can refer to other users by prefixing their username with the @ symbol.
This will generate a link to their profile, but it won't necessarily send them a notification unless they have a special FMN rule set up to catch it.
Lastly, you can embed inline images with syntax like this:
Is the update generally functional? (karma)
You need to be logged in to add karma!
Copyright © 2007-2018 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.