NVIDIA Question
by David St.Clair
This may be a dumb question, but why can't Redhat distribute NVIDIA binary
drivers?
In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it
says:
"2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section
2.1.1, SOFTWARE designed exclusively for use on the Linux operating system
may be
copied and redistributed, provided that the binary files thereof are not
modified in any
way (except for unzipping of compressed files)."
So, what's keeping RedHat from putting the drivers in the distribution? If
it's a GPL
thing, would it be easy to just download it during installation or at
least give the option to the user?
Thanks,
--
David St.Clair
dstclair(a)cs.wcu.edu
1 year, 10 months
Mouse goes crazy
by Jonathan Villa
Ok, I have had Yarrow working well for a while now, but yesterday I
started experiencing some odd issues with my mouse. All of a sudden it
stops working correctly. The only thing that seems to fix is to kill X
and run mouse-test, then restart.
Any ideas?
Also, I have FC 1 running on a desktop which is hooked up to a KVM
switch. Whenever I go to another PC, and return, the same thing
happens, the mouse goes crazy.
???
1 year, 10 months
[Fedora QA] #472: create testcase for resizing in custom partitioning
by fedora-badges
#472: create testcase for resizing in custom partitioning
------------------------+------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 22
Component: Test cases | Version:
Keywords: | Blocked By:
Blocking: |
------------------------+------------------------
After discovering https://bugzilla.redhat.com/show_bug.cgi?id=1221247 it
seems reasonable we should test this more properly in the future.
Currently we seem to have no test case about resizing partitions in manual
part dialog. We probably should, and test it against at least a standard
partition and a logical volume. Optionally, we can split standard
partitions into ext4 and ntfs, to cover similar use cases as in our
QA:Testcase_partitioning_guided_shrink .
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/472>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
7 years, 3 months
[Fedora QA] #480: Fedora 24 Translation (L10n) Test Day
by fedora-badges
#480: Fedora 24 Translation (L10n) Test Day
--------------------------------------+------------------------
Reporter: anipeter | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 23
Component: Blocker bug tracker page | Version:
Keywords: l10n, fltg | Blocked By:
Blocking: |
--------------------------------------+------------------------
Fedora 24 Alpha release is on 22nd March (Tuesday) and Software
Translation Deadline is on 5th April (Tuesday) [1].
As per mail discussion [2], the date for F24 L10n Test day is finalized as
29th March (Tuesday)
FLTG team will be working towards coordinating and arranging the test day
including creating new test cases, reviewing old test cases, listing
existing bugs, provide required assistance to get the image for testing,
help testers on test day etc. The list of items to do will be listed soon.
Thanks Ani Peter (apeter)
FLTG
[1] - https://fedoraproject.org/wiki/Releases/24/Schedule[[BR]]
[2] - bit.ly/1TdUirs
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/480>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
7 years, 3 months
Fedora 24: i686 images no longer 'release blocking'
by Adam Williamson
Hi, folks! As discussed at last week's meeting, it seemed a good idea
to flag this up on the list for anyone who missed it.
From Fedora 24 onwards, FESCo has decided that i686 (32-bit x86) images
are no longer 'release blocking', by policy:
https://fedorahosted.org/fesco/ticket/1469
I have tweaked the release criteria 'preamble' text slightly to mention
this explicitly, and also to link to the canonical list of release-
blocking images that the program manager is maintaining now (the F24
list is
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/... ).
I noted that the question of whether we 'support' / block on 32-bit
*upgrades* is not yet resolved, so I've filed a FESCo ticket for that:
https://fedorahosted.org/fesco/ticket/1539
What this means to us is pretty simple: we no longer have to worry
about getting all the validation tests done for 32-bit images. Woot! We
still *can* test them, if we want, but we don't have to. They're just
like the LXDE live, or any other non-blocking image.
An outstanding question is what we do with the validation matrices.
Cloud was easy enough - I just marked all rows in the i386 table as
'Optional'. Base, Server and Desktop don't really split out x86_64 and
i386/i686 (sidebar: the best thing about ditching i386/i686/x86_32 is
we no longer have to be terminally confused about what it's freaking
*called*...), so they're OK too. However, Installation is a bit of a
problem:
https://fedoraproject.org/wiki/Template:Installation_test_matrix
quite a lot of the tables have 'i386' and 'x86_64' as environments.
Especially with the Milestone column, listing i386 alongside x86_64 is
a bit misleading if i386 is no longer blocking. I can see a few
options:
1) just ditch the i386 columns entirely; openQA can continue testing
it, and people can test manually if they want, but we don't bother
tracking the results in the validation pages
2) stick an admon template at the top of the page saying 'the i386
tests aren't blocking', with links out to the criteria and/or the FESCo
ticket
3) Duplicate each table which distinguishes between 'i386' and
'x86_64', so we have one table with just an 'i386' column and all tests
marked Optional, and another table with the other columns and the
appropriate milestone
I can see arguments for any of those approaches. #1 is nice and simple
and reduces the scariness of the page, but I guess means we don't get a
quick overview of i386 status and probably means fewer people bothering
to do i386 tests. I don't know how much we care about that.
#2 is also simple and keeps the tests around, but people are probably
going to miss the admon note and will therefore be confused about
whether we're "missing" a lot of required results, if i386 isn't done.
#3 is probably the most 'theoretically correct', but would probably be
something of a giant PITA to read. I suppose we could have the i386
tables collapsed by default. That might work. Now I think about it,
though, I think having rows that are identical except for their
environments might confuse python-wikitcms, I'd have to look into it.
If you're thinking "4) change the Milestone column", I'd rather not,
because those values are somewhat significant to Wikitcms. Other ideas
welcome!
If anyone can think of any other system/process which might need
adjusting for this change, too, please do let us know! Or just go fix
it. ;)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 8 months
Non-image blocker process change proposal
by Adam Williamson
Hi, folks! It's been a recurring issue in the blocker review / release
validation process in recent times that we run across bugs that qualify
as blockers, but for which the fix does not need to be in the final
frozen media or install trees.
Common cases are bugs related to upgrading, especially since the
introduction of fedup and even more so of dnf-system-upgrade; most
upgrade-related issues can now be sufficiently fixed by package updates
to either the source or target release. Bugs to do with writing USB
media from the previous release, for instance, also often fall in this
category.
Up until now we've been sort of handwaving these as 'special blockers',
following the regular blocker process but noting in comments that they
don't block the compose. We haven't been tracking very hard if they
actually *are* being fixed with updates promptly, we've just been sort
of waving a magic wand and assuming it will happen. I just found one
which was supposed to be fixed with a 0-day update for Beta, but hadn't
been fixed yet: https://bugzilla.redhat.com/show_bug.cgi?id=1263230
So, we kinda need to do this better.
Up top I'd like to note there are really kind of two buckets of
'special blockers' for any given release. If the release being
validated is N, they are:
1) Bugs for which the fix must be in the 0-day update set for N
2) Bugs for which the fix must be stable in N-1 and N-2 by N release day
There will be a lot of process nerd detail involved in any fix, but
before any detailed drafts I'd like to suggest two broad possible
approaches and see what people think:
#1 Separate trackers
--------------------
As a sort of on-the-spot PoC for F23 Beta, I created a new tracker bug
for bucket 1: https://bugzilla.redhat.com/show_bug.cgi?id=1264167
We could formalize that approach, and have a '0-day' blocker tracker
for each milestone. We could either just have one '0-day' tracker and
throw bugs for both the pending release and previous stable releases on
the same tracker and keep track of what needs updating where in each
bug, or we could have two 0-day trackers for each milestone, one for
the pending release, and one for previous stable releases.
So we'd have something like:
F24AlphaBlocker
F24AlphaFreezeException
F24Alpha0Day
(F24AlphaStable) (? - better alias suggestions welcome)
and so on. This is a lot of bugs, but there is a script to create them,
so we're not adding a bunch of onerous work.
So far as proposing bugs goes, I think we'd probably want to extend the
current somewhat flexible approach; formally you would nominate a bug
as a particular type of blocker/FE (by marking it as blocking the
appropriate tracker), but we would move things around in blocker review
meetings sensibly, as we currently do (when something is nominated as
FE but should really be a blocker, or vice versa). In blocker review
we'd go through all bugs nominated for any of the trackers, probably
starting with 'Blocker', then '0Day' and 'Stable', then
'FreezeException'.
#2 MOAR METADATA
----------------
The alternative is to make the existing Blocker trackers do more work.
In this model we wouldn't add any new tracker bugs; we'd just add new
'magic words' in the Whiteboard field. Right now, an accepted blocker
is identified by the string 'AcceptedBlocker' appearing in the
whiteboard field. We could simply add some more magical strings like
that: 'Accepted0Day' and 'AcceptedStable', say (better suggestions
welcome).
I kind of like this idea as it's less change and involves creating
fewer new bugs. We'd have to make some changes to blockerbugs either
way - tflink can say if either approach would be more work in
blockerbugs, but I'm gonna guess they'd be fairly similar.
With either approach, the basic goal is to make it more feasible to
keep an eye on each of the different categories of 'release blocker'
bugs; right now we have solid processes in place for ensuring the
'normal' blockers are all addressed in the release media, but we don't
have any processes in place for ensuring 0Day and Stable bugs actually
get updates shipped when we say they must.
My suggestion would be that we make sure 'blockerbugs' includes lists
of each type of blocker. Ahead of and at Go/No-Go meetings, we would
want to have a formal assurance from the person responsible for fixing
the bug that the fix would be provided by a certain time - say, one day
or two days ahead of the release date - and it would be QA's
responsibility to ensure the updates are tested promptly, and releng's
responsibility to ensure they are pushed on time after being tested. I
would suggest the Program Manager ought to have overall responsibility
for keeping an eye on the 0Day and Stable blocker lists and making sure
the maintainer, QA, and releng all did their jobs on time.
It'd be great if folks could post their general thoughts on this, and
any preference for option 1 or option 2. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 9 months
Criteria proposal: applying 'post-install' criteria to live and
appliance images
by Adam Williamson
Hi, folks! I'm working through some criteria issues that came up during
F23 validation.
Here's one: a few times, we hit issues on live images which would have
been violations of the 'post-install' release criteria, except those
are explicitly for 'installed' systems. We generally felt that the
relevant 'post-install' criteria should also apply to live boots.
Here's a top-level idea for handling that:
1. Rename the 'Post-install requirements' section on each criteria page
to 'Post-deployment and live requirements'
2. Add some text at the top of the section explaining the general idea:
the requirements in the section apply to installed systems, 'appliance'
environments like the cloud images, *and* live environments, where
appropriate
3. Adjust the wording of each individual criterion in the sections,
where appropriate. Just to give an example:
"Unless explicitly specified otherwise, after system installation
SELinux must be enabled and in enforcing mode."
would become something like:
"Unless explicitly specified otherwise, SELinux must be enabled and in
enforcing mode in live environments and after system installation."
Does this general approach sound good? If so, I'll post some drafts
later in the week. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 9 months
Is anyone but me using fedfind for anything?
by Adam Williamson
Hi folks!
So, I spent most of this week rewriting my 'fedfind' tool for the new
world of Pungi 4 composes. The work is currently on the 'pungi4'
branch:
https://www.happyassassin.net/cgit/fedfind/log/?h=pungi4
I'm more or less happy with what I've got now, but it makes some rather
large API changes.
I've made the CLI continue to work more or less unchanged; there's a
new --respin arg for specifying the 'respin' for relevant compose
types, and the debug output looks slightly different, but any way you
could run it before you should still be able to run it now and it
should behave basically the same. So if you just use fedfind as a CLI
tool, relax, you don't have to worry.
However, I wanted to ask if anyone apart from me is using fedfind as a
Python package. If there *are* any non-me users, I'll probably try to
be a bit polite about sending out the new code as a stable release and
pushing it to the Fedora repositories. If I *don't* find any non-me
users I'm just going to convert the things I'm in charge of that use
fedfind, and then send out a 2.0 release everywhere.
So if you're using it, please speak up :) Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 9 months
Fedora 23 updates-testing report
by updates＠fedoraproject.org
The following Fedora 23 Security updates need testing:
Age URL
162 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16240 nagios-4.0.8-1.fc23
120 https://bodhi.fedoraproject.org/updates/FEDORA-2015-81ded368fe miniupnpc-1.9-6.fc23
93 https://bodhi.fedoraproject.org/updates/FEDORA-2015-27392b3324 jbig2dec-0.12-2.fc23
43 https://bodhi.fedoraproject.org/updates/FEDORA-2015-dd52a54fa1 python-pymongo-3.0.3-1.fc23
43 https://bodhi.fedoraproject.org/updates/FEDORA-2015-06a7c972e8 thttpd-2.25b-37.fc23
32 https://bodhi.fedoraproject.org/updates/FEDORA-2016-a69ee02554 xulrunner-44.0-1.fc23
14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-40401300ed 389-ds-base-1.3.4.8-1.fc23
14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-65a1f22818 community-mysql-5.6.29-1.fc23
14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-94b0b50351 gummi-0.6.6-1.fc23
8 https://bodhi.fedoraproject.org/updates/FEDORA-2016-637618fcd4 mingw-nsis-2.50-1.fc23
5 https://bodhi.fedoraproject.org/updates/FEDORA-2016-cdd4228cc7 pcs-0.9.149-2.fc23
3 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f12be382f4 mote-0.5.1-3.fc23
3 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8411497132 drupal6-6.38-1.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-eeb0f0c94f drupal7-7.43-1.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-ae14784e4e libmodbus-3.0.6-1.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-120b194a75 qpid-cpp-0.34-6.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-1642a20327 kernel-4.4.3-300.fc23
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-65833b5dbc pcre-8.38-6.fc23
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-dec1faadc5 graphite2-1.3.6-1.fc23
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f802cade15 exiv2-0.25-3.fc23
The following Fedora 23 Critical Path updates have yet to be approved:
Age URL
32 https://bodhi.fedoraproject.org/updates/FEDORA-2016-a69ee02554 xulrunner-44.0-1.fc23
12 https://bodhi.fedoraproject.org/updates/FEDORA-2016-054e18a33d htdig-3.2.0-0.23.b6.fc23
8 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8dde5e377c lxsession-0.5.2-8.fc23
8 https://bodhi.fedoraproject.org/updates/FEDORA-2016-2400dcd3d1 virtuoso-opensource-6.1.6-10.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-ffbae3a870 selinux-policy-3.13.1-158.9.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-1642a20327 kernel-4.4.3-300.fc23
1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-e10d786768 pungi-4.0.6-1.fc23
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f802cade15 exiv2-0.25-3.fc23
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d360559a79 rpm-4.13.0-0.rc1.12.fc23
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-65833b5dbc pcre-8.38-6.fc23
The following builds have been pushed to Fedora 23 updates-testing
3dprinter-udev-rules-0.1-1.fc23
bugyou_plugins-0.1-1.fc23
cherrytree-0.36.6-1.fc23
djview4-4.10.6-1.fc23
easytag-2.4.2-2.fc23
exiv2-0.25-3.fc23
gerrymander-1.5-2.fc23
gkrellm-2.3.6-0.1.rc1.git20160226.fc23
gkrellm-sun-1.0.0-20.fc23
graphite2-1.3.6-1.fc23
kubernetes-1.2.0-0.12.alpha6.gitf0cd09a.fc23
lilypond-2.19.37-1.fc23
lilypond-doc-2.19.37-1.fc23
nacl-arm-newlib-2.1.0-3.git373135e.fc23
oz-0.15.0-1.fc23
pcre-8.38-6.fc23
pcre2-10.21-3.fc23
perl-App-a2p-1.009-2.fc23
perl-CBOR-XS-1.4.1-1.fc23
python-behave-1.2.5-9.fc23
python-zanata2fedmsg-0.2-1.fc23
rpm-4.13.0-0.rc1.12.fc23
skopeo-0.1.9-1.fc23
transmission-2.90-1.fc23
xfig-3.2.5-48.c.fc23
yad-0.34.2-1.fc23
Details about builds:
================================================================================
3dprinter-udev-rules-0.1-1.fc23 (FEDORA-2016-739a9100da)
Rules for udev to give regular users access to operate 3D printers
--------------------------------------------------------------------------------
Update Information:
Rules for udev to give regular users access to operate 3D printers
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1312296 - Review Request: 3dprinter-udev-rules - Rules for udev to give regular users access to operate 3D printers
https://bugzilla.redhat.com/show_bug.cgi?id=1312296
--------------------------------------------------------------------------------
================================================================================
bugyou_plugins-0.1-1.fc23 (FEDORA-2016-18eaad36f3)
Plugins for Bugyou
--------------------------------------------------------------------------------
Update Information:
Initial packaging.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1309782 - Review Request: bugyou_plugins - Plugins and Services for Bugyou
https://bugzilla.redhat.com/show_bug.cgi?id=1309782
--------------------------------------------------------------------------------
================================================================================
cherrytree-0.36.6-1.fc23 (FEDORA-2016-a44b7aea31)
Hierarchical note taking application
--------------------------------------------------------------------------------
Update Information:
update to cherrytree-0.36.6 ---- update to 0.36.5 ---- Update to 0.36.4
---- update to cherrytree 0.36.3
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1311778 - cherrytree-0.36.6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1311778
[ 2 ] Bug #1309140 - cherrytree-0.36.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1309140
[ 3 ] Bug #1160249 - cherrytree-0.36.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1160249
[ 4 ] Bug #1301941 - cherrytree-0.36.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1301941
--------------------------------------------------------------------------------
================================================================================
djview4-4.10.6-1.fc23 (FEDORA-2016-a0ef29f987)
DjVu viewer
--------------------------------------------------------------------------------
Update Information:
Update to latest upstream release djview 4.10.6.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1312984 - djview4-4.10.6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1312984
--------------------------------------------------------------------------------
================================================================================
easytag-2.4.2-2.fc23 (FEDORA-2016-893ed9bec1)
Tag editor for MP3, Ogg, FLAC and other music files
--------------------------------------------------------------------------------
Update Information:
Fix crash in the load filenames dialog (#1312163)
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1312163 - [abrt] easytag: g_type_check_instance_cast(): easytag killed by SIGSEGV
https://bugzilla.redhat.com/show_bug.cgi?id=1312163
--------------------------------------------------------------------------------
================================================================================
exiv2-0.25-3.fc23 (FEDORA-2016-f802cade15)
Exif and Iptc metadata manipulation library
--------------------------------------------------------------------------------
Update Information:
Avoid possible XML entity expansion security issue.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #888769 - exiv2: embedded copy of exempi should be compiled with BanAllEntityUsage
https://bugzilla.redhat.com/show_bug.cgi?id=888769
--------------------------------------------------------------------------------
================================================================================
gerrymander-1.5-2.fc23 (FEDORA-2016-48a5138e81)
The gerrit client tools
--------------------------------------------------------------------------------
Update Information:
Add the Python PrettyTable dependency to relevant sub-packages ---- New
upstream release 1.5 ---- Add 'python-prettytable' to 'Requires'; fixes rhbz#
1307167
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1307167 - gerrymander should require: python-prettytable
https://bugzilla.redhat.com/show_bug.cgi?id=1307167
--------------------------------------------------------------------------------
================================================================================
gkrellm-2.3.6-0.1.rc1.git20160226.fc23 (FEDORA-2016-e10fd8290e)
Multiple stacked system monitors in one process
--------------------------------------------------------------------------------
Update Information:
- Update to a gkrellm-2.3.6-rc git snapshot bringing in various fixes - Fix
crash after sun-plugin has been disabled (rhbz#1231394) - Add appdata
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1231394 - [abrt] gkrellm: exit(): gkrellm killed by SIGSEGV
https://bugzilla.redhat.com/show_bug.cgi?id=1231394
[ 2 ] Bug #1312561 - Review Request: gkrellm-sun - Sun clock plugin for GKrellM
https://bugzilla.redhat.com/show_bug.cgi?id=1312561
--------------------------------------------------------------------------------
================================================================================
gkrellm-sun-1.0.0-20.fc23 (FEDORA-2016-e10fd8290e)
Sun clock plugin for GKrellM
--------------------------------------------------------------------------------
Update Information:
- Update to a gkrellm-2.3.6-rc git snapshot bringing in various fixes - Fix
crash after sun-plugin has been disabled (rhbz#1231394) - Add appdata
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1231394 - [abrt] gkrellm: exit(): gkrellm killed by SIGSEGV
https://bugzilla.redhat.com/show_bug.cgi?id=1231394
[ 2 ] Bug #1312561 - Review Request: gkrellm-sun - Sun clock plugin for GKrellM
https://bugzilla.redhat.com/show_bug.cgi?id=1312561
--------------------------------------------------------------------------------
================================================================================
graphite2-1.3.6-1.fc23 (FEDORA-2016-dec1faadc5)
Font rendering capabilities for complex non-Roman writing systems
--------------------------------------------------------------------------------
Update Information:
Unspecified security fixes
--------------------------------------------------------------------------------
================================================================================
kubernetes-1.2.0-0.12.alpha6.gitf0cd09a.fc23 (FEDORA-2016-5a203fd7ac)
Container cluster management
--------------------------------------------------------------------------------
Update Information:
Update to origin 1.1.3, disable v1beta1, v1beta3, fix application/json content
type ---- A lot of changes here: rebase to origin based kubernetes from 1.0.3
to 1.2.0. This will need a lot of testing to discover regressions and new issues
introduced by the rebase.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1311861 - kubectl exec is broken in kubernetes-1.2.0-0.4.alpha1
https://bugzilla.redhat.com/show_bug.cgi?id=1311861
[ 2 ] Bug #1291860 - Packaged old version (1.06) of kubernetes in most recent release. kubernetes rpm labeled 1.1xxxx
https://bugzilla.redhat.com/show_bug.cgi?id=1291860
--------------------------------------------------------------------------------
================================================================================
lilypond-2.19.37-1.fc23 (FEDORA-2016-0c83c25c39)
A typesetting system for music notation
--------------------------------------------------------------------------------
Update Information:
Latest upstream.
--------------------------------------------------------------------------------
================================================================================
lilypond-doc-2.19.37-1.fc23 (FEDORA-2016-0c83c25c39)
HTML documentation for LilyPond
--------------------------------------------------------------------------------
Update Information:
Latest upstream.
--------------------------------------------------------------------------------
================================================================================
nacl-arm-newlib-2.1.0-3.git373135e.fc23 (FEDORA-2016-86e9d3f14a)
C library intended for use on embedded systems
--------------------------------------------------------------------------------
Update Information:
New package: nacl-arm-newlib - C library intended for use on embedded systems
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1270375 - Review Request: nacl-arm-newlib - C library intended for use on embedded systems
https://bugzilla.redhat.com/show_bug.cgi?id=1270375
--------------------------------------------------------------------------------
================================================================================
oz-0.15.0-1.fc23 (FEDORA-2016-7586e24a5e)
Library and utilities for automated guest OS installs
--------------------------------------------------------------------------------
Update Information:
Release 0.15.0
--------------------------------------------------------------------------------
================================================================================
pcre-8.38-6.fc23 (FEDORA-2016-65833b5dbc)
Perl-compatible regular expression library
--------------------------------------------------------------------------------
Update Information:
This release fixes a heap buffer overflow in handling of nested duplicate named
groups with a nested back reference and a heap buffer overflow in pcretest
causing infinite loop when matching globally with an ovector less than 2.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1295385 - CVE-2016-1283 pcre: heap buffer overflow in handling of duplicate named groups (8.39/14)
https://bugzilla.redhat.com/show_bug.cgi?id=1295385
[ 2 ] Bug #1312782 - pcre: Heap buffer overflow in pcretest causing infinite loop
https://bugzilla.redhat.com/show_bug.cgi?id=1312782
--------------------------------------------------------------------------------
================================================================================
pcre2-10.21-3.fc23 (FEDORA-2016-55953d3cc5)
Perl-compatible regular expression library
--------------------------------------------------------------------------------
Update Information:
This release fixes a typo in pcre2_study().
--------------------------------------------------------------------------------
================================================================================
perl-App-a2p-1.009-2.fc23 (FEDORA-2016-b4bc777e25)
Awk to Perl translator
--------------------------------------------------------------------------------
Update Information:
This release fixes a buffer overflow when parsing long enough -n argument.
--------------------------------------------------------------------------------
================================================================================
perl-CBOR-XS-1.4.1-1.fc23 (FEDORA-2016-f9a1de2ff9)
Concise Binary Object Representation (CBOR)
--------------------------------------------------------------------------------
Update Information:
This release fixes nested FREEZE and THAW calls.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1312516 - perl-CBOR-XS-1.41 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1312516
--------------------------------------------------------------------------------
================================================================================
python-behave-1.2.5-9.fc23 (FEDORA-2016-9e381832b8)
Tools for the behavior-driven development, Python style
--------------------------------------------------------------------------------
Update Information:
Fixed managing python3 builds.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1216989 - Please upgrade to 1.2.5 in F21+
https://bugzilla.redhat.com/show_bug.cgi?id=1216989
[ 2 ] Bug #1276923 - provide Python3 version of the package
https://bugzilla.redhat.com/show_bug.cgi?id=1276923
--------------------------------------------------------------------------------
================================================================================
python-zanata2fedmsg-0.2-1.fc23 (FEDORA-2016-d19b3fd12c)
A web app bridging zanata webhooks to fedmsg
--------------------------------------------------------------------------------
Update Information:
Initial packaging.
--------------------------------------------------------------------------------
================================================================================
rpm-4.13.0-0.rc1.12.fc23 (FEDORA-2016-d360559a79)
The RPM package management system
--------------------------------------------------------------------------------
Update Information:
- Remove size limit when expanding macros (#1303034)
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1303034 - rpm macro expansion works incorrectly when looping over a long list using lua
https://bugzilla.redhat.com/show_bug.cgi?id=1303034
--------------------------------------------------------------------------------
================================================================================
skopeo-0.1.9-1.fc23 (FEDORA-2016-02cc4cb057)
Inspect Docker images and repositories on registries
--------------------------------------------------------------------------------
Update Information:
update to v0.1.9 ---- update to v0.1.8
--------------------------------------------------------------------------------
================================================================================
transmission-2.90-1.fc23 (FEDORA-2016-99d6679320)
A lightweight GTK+ BitTorrent client
--------------------------------------------------------------------------------
Update Information:
Latest upstream. http://www.transmissionbt.com/
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1312701 - transmission-2.90 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1312701
--------------------------------------------------------------------------------
================================================================================
xfig-3.2.5-48.c.fc23 (FEDORA-2016-a23c447f3e)
An X Window System tool for drawing basic vector graphics
--------------------------------------------------------------------------------
Update Information:
- Bring in various bugfixes from Debian - Convert icons to png - Add appdata
--------------------------------------------------------------------------------
================================================================================
yad-0.34.2-1.fc23 (FEDORA-2016-380e55dae6)
Display graphical dialogs from shell scripts or command line
--------------------------------------------------------------------------------
Update Information:
update to 0.34.2 ---- update to yad-0.34.1 ---- update to 0.34.0 ----
Update to yad-0.33.1 ---- update to 0.33.0
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1312645 - yad-0.34.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1312645
[ 2 ] Bug #1310485 - yad-0.34.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1310485
[ 3 ] Bug #1297601 - yad-0.33.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1297601
[ 4 ] Bug #1296780 - yad-0.33.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1296780
--------------------------------------------------------------------------------
7 years, 9 months
