On Wed, 2016-09-14 at 15:53 -0400, Neal Gompa wrote: > On Wed, Sep 14, 2016 at 3:50 PM, Richard Hughes <hughsient@xxxxxxxxx> wrote: > Although, perhaps given upstream has not had a release since 2006 and > we've acquired 14 out-of-tree security patches (and countless others > for various fixes) perhaps we should drop dep this from applications > completely? > > > > > ... snip ... > > > > libjasper.so.1()(64bit) is needed by (installed) opencv-2.4.12.3-3.fc24.x86_64 > > > > > If I recall correctly, we need libjasper for opencv for openqa, so I'm > not sure we can drop this? yeah, please don't just drop it. if anyone wants to work with me/openQA upstream/both to port it to something else, great, but we do need to cover that usage. note, we do have this update installed on all the openQA boxes, and they're all working perfectly fine. I generally agree with Matthew on the wider issue here; the update process isn't really meant to catch every issue ever, and this bug clearly doesn't break *all* jasper usage (see note about openQA being fine), so the feedback could well be perfectly legit. There really *is* an onus on developers as well as testers to provide appropriate test instructions and to configure updates appropriately. The autokarma threshold of 3 is only a *default*. Maintainers can make the number larger or turn autopush off entirely for sensitive updates. Also...I have the 'affected' jasper-libs on my F24 machine (a laptop), and I just ran gnome-software on it, and it ran perfectly fine? It runs, I can look at app pages (the screenshots render fine)... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
