From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tiff: Update to 4.0.4
Date: Sat, 27 Jun 2015 08:16:13 +0100 [thread overview]
Message-ID: <1435389373.10583.42.camel@linuxfoundation.org> (raw)
In-Reply-To: <558E0148.10705@windriver.com>
On Fri, 2015-06-26 at 21:50 -0400, Randy MacLeod wrote:
> On 2015-06-26 06:50 PM, Richard Purdie wrote:
> > On Fri, 2015-06-26 at 16:34 -0400, Randy MacLeod wrote:
> >> On 2015-06-26 04:27 PM, Randy MacLeod wrote:
> >>> Update tiff to latest version. None of the local CVE patches
> >>> are needed based on reviewing the ChangeLog so remove them.
> >>
> >> I didn't want to clutter the long log but I also built for
> >> all qemu arches. On qemux86-64, core-image-sato, I installed
> >> the libtiff-util rpms and ran:
> >>
> >> # tiffinfo /tmp/gmarbles.tif
> >> TIFF Directory at offset 0x8 (8)
> >> Subfile Type: (0 = 0x0)
> >> Image Width: 1419 Image Length: 1001
> >> Resolution: 300, 300 pixels/inch
> >> Bits/Sample: 8
> >> Compression Scheme: LZW
> >> Photometric Interpretation: min-is-black
> >> Samples/Pixel: 1
> >> Rows/Strip: 5
> >> Planar Configuration: single image plane
> >> Photoshop Data: <present>, 272 bytes
> >> Predictor: horizontal differencing 2 (0x2)
> >>
> >> I could do more testing but this appears to be bug fixes only.
> >
> > It would be lovely to have this as an automated ptest or other form of
> > sanity test...
>
> I can do that but I'd like to keep it separate from the upgrade.
Agreed, this was more an observation that it would be nice to have, the
upgrade doesn't depend on this.
> The package has a "make check" target with ~ 70 tests so
> I'll make that build for ptest and try it on some qemu targets.
>
> Ptests are useful but I wonder if anyone has a way to
> monitor regressions...
The QA team are supposed to be working on this in 1.9 as a major
feature.
Cheers,
Richard
prev parent reply other threads:[~2015-06-27 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 20:27 [PATCH] tiff: Update to 4.0.4 Randy MacLeod
2015-06-26 20:34 ` Randy MacLeod
2015-06-26 22:50 ` Richard Purdie
2015-06-27 1:50 ` Randy MacLeod
2015-06-27 7:16 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1435389373.10583.42.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox