I will build ntl 6.1.0 for Rawhide today. This involves an soname
bump, so I will also rebuild dependent packages, namely:
- eclib
- flint
- latte-integrale
- linbox
- Macaulay2
- polybori
- sagemath
- Singular
I have already been in contact with maintainers of these packages
about the rebuilds.
--
Jerry James
http://www.jamezone.org/
Reposted from
http://fedoramagazine.org/five-things-in-fedora-this-week-2014-04-01/
Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn't comprehensive news coverage — just quick summaries with links
to each. I know it's traditional for the Internet to be useless today,
but, despite the temptation, I'm sticking to the facts. So, here we go
for April 1st, 2014:
Trying Wayland (and Gnome 3.12)
-------------------------------
Wayland is the upcoming successor to the X11 graphics protocol which
powers our desktops. It's not done yet, but you can try it first in
Fedora. You'll need to be running Rawhide (Fedora's development
branch). In theory, it should work on Fedora 20 with Gnome 3.12, but
from the mailing list thread, it looks like that's not working yet.
* http://wayland.freedesktop.org/
* https://lists.fedoraproject.org/pipermail/desktop/2014-March/009543.html
Wait, Gnome 3.12 on Fedora 20, you ask? Yes; although F20 shipped with
3.10, 3.12 is available for those of you who are a little adventurous
but not so brave as to run Rawhide, via Richard Hughes’ Gnome 3.12
COPR. There's a Fedora Magazine article with instructions, too.
* https://copr.fedoraproject.org/coprs/rhughes/f20-gnome-3-12/
* http://fedoramagazine.org/running-gnome-3-12-on-fedora-20/
Infrastructure downtime *today*
-------------------------------
What better time for major upgrades than April Fool's Day? If you
notice that some Fedora infrastructure services are unavailable later
this evening, it's no joke, just planned work, including an upgrade to
Koji, Fedora's package and image building service. The work should
happen between 21:00 and 01:00 UTC (`date -d '2014-04-01 21:00 UTC'` in
your local time).
* https://lists.fedoraproject.org/pipermail/announce/2014-March/003204.html
Last call for Flock talk proposals
----------------------------------
Flock is our big annual development and planning conference, held this
year in Prague from August 6th–9th. The deadline for talk proposals is
April 3rd — that's Thursday. So if you are thinking of something, it's
time to put those thoughts in writing. Note that there is some funding
available for travel and hotel subsidies; it's not guaranteed, but we
want as many contributors there as possible, so if you have a need,
there is a box to check at registration time.
* http://flocktofedora.org/
* https://flock-lmacken.rhcloud.com/submit_proposal
Fedora 21 change plan deadline
------------------------------
Speaking of deadlines... the Fedora Change Proposal deadline is April
8th, a week from today. These change proposals are our primary means
for coordinating development across the project, so particularly if you
want to do something which affects other areas, get it in now. FESCo
(Fedora's technical steering committee) reviews and approves each
proposal and may accept late entries (especially for "self-contained"
changes), but it really helps to know sooner rather than later. Note
that these proposals are largely statements of intent to do something,
not orders for someone else to. As a community project developed by
volunteers, we don't have a mechanism to *force* anyone do anything, so
if you want to make something happen and can't do it all yourself,
discuss on the Fedora devel list (or the appropriate SIGs) and get
others inspired to sign on as collaborators.
* https://lists.fedoraproject.org/pipermail/devel-announce/2014-April/001345.…
Fedora Docs starts a Cookbook
-----------------------------
The Fedora Docs team does an excellent job of producing our
book-quality documentation, but we have a unfilled need for
easy-to-contribute-to howto and quickstart articles. The Docs team
recently held an Activity Day focused on finding a solution, and Pete
Travis (a.k.a. "randomuser") describes the results:
The answer we settled on is what will become the Fedora Cookbook, and
it is a process as much as a book. Anyone can submit a 'recipe' for
the Cookbook [...] using provided templates, and Docs volunteers will
review, mark up, submit for translation, and publish.
There's a lot more in Pete's post, so if this is an area of interest to
you, and especially if you've been wanting to contribute but aren't
sure how, don't miss it.
* http://docs.fedoraproject.org/
* http://blog.randomuser.org/posts/open-books.html
5tFTW note
----------
This is the third installment of this series, and I'm still calibrating
a few things. I'm aiming at a wide audience, but I'm not quite sure how
much explaining I should do of general Fedora knowledge. Is it helpful
for me to (as above), give a quick explanation when I talk about
Rawhide, Flock, or FESCo? Or, does that just increase the word count
for no reason? Let me know.
Also, as always, tips on what's going on in your part of Fedora are
appreciated — e-mail them to me directly, or ping me on IRC.
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
"Tepid change for the somewhat better!"
= Proposed Self Contained Change: KDE Frameworks 5 =
https://fedoraproject.org/wiki/Changes/KDE_Frameworks_5
Change owner(s): Daniel Vrátil <dvratil(a)redhat.com>
KDE Frameworks 5 is a set of libraries and technologies developed in the KDE
project over the past 18 years. Most of the frameworks come from the kdelibs
module, which has been split, cleaned up, dependencies were strightened and
packed into individual libraries. This allows developers and projects outside
the KDE ecosystem to make use of these technologies and benefit from work of
the KDE Community.
== Detailed Description ==
KDE Frameworks 5 is the successor to KDE Platform 4, bringing significant
technical differences and a change in focus. It will be the first release of
KDE libraries based on Qt 5, which brings significant improvements to users.
New technologies are being introduced and libraries are being cleaned up,
reviewed and brought up to date with new standards. At the same time, the team
is making the development platform more modular and making it easier to reuse
solutions in a wider range of platforms and devices, including desktop and
mobile. Technologies such as QML allow KDE developers to take advantage of a
leading graphics rendering engine, and allow for more organic and fluid user
interfaces across devices.
An important goal of KDE Frameworks 5 is to bring the benefits of KDE
technology to Qt5 users outside the KDE Community. Libraries are split into
distinct components, making it possible for Qt developers to take components
without dragging in other unnecessary libraries. (from [1])
KDE Frameworks 5 don't provide any UI or applications on their own, but are
meant as extensions and addons for the Qt toolkit. In future there will be
various desktop shells like Plasma 2 and applications built on top of KDE
Frameworks 5 providing the full-featured KDE desktop ("KDE 5").
All Frameworks are co-installable with current all KDE 4 packages.
== Scope ==
* Proposal owners: All frameworks are already packaged and are currently
provided in a COPR repository [2]. We only need to have all the packages
reviewed and submit them into Fedora. Given the amount of frameworks
(currently 60), this will take some time to process. This is a completely
isolated change that will not affect any other packages or changes.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://dot.kde.org/2013/09/04/kde-release-structure-evolves
[2] http://copr.fedoraproject.org/coprs/dvratil/kde-frameworks/
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
I promised a while ago that I would provide a text version of my talk at
DevConf, for people who couldn't make it and because sitting through a video
of me standing up there going on and on doesn't really make for good
followup discussion.
I posted a link to the first part last week:
<http://fedoramagazine.org/fedora-present-and-future-a-fedora-next-2014-upda…>
and now, Part II:
<http://fedoramagazine.org/fedora-present-and-future-a-fedora-next-2014-upda…>
And as I said last week, I will take questions, comments, complaints, in any
media including replies here, on the article, on the social media, or at any
bar or coffee shop within walking distance of Boston's MBTA.
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
"Tepid change for the somewhat better!"
On Mon, 31 Mar 2014 13:37:51 +0000 (UTC)
buildsys(a)fedoraproject.org wrote:
>
>
> libdmtx has broken dependencies in the rawhide tree:
> On x86_64:
> libdmtx-utils-0.7.2-11.fc20.x86_64 requires libMagickWand-6.Q16.so.1()(64bit)
> libdmtx-utils-0.7.2-11.fc20.x86_64 requires libMagickCore-6.Q16.so.1()(64bit)
> On i386:
> libdmtx-utils-0.7.2-11.fc20.i686 requires libMagickWand-6.Q16.so.1
> libdmtx-utils-0.7.2-11.fc20.i686 requires libMagickCore-6.Q16.so.1
> On armhfp:
> libdmtx-utils-0.7.2-11.fc20.armv7hl requires libMagickWand-6.Q16.so.1
> libdmtx-utils-0.7.2-11.fc20.armv7hl requires libMagickCore-6.Q16.so.1
> Please resolve this as soon as possible.
there seems to be an unannounced soname bump in ImageMagick in rawhide,
but the same release is going to F-20 too. Per changelog the reason is
mainly fixing multiple CVEs, but a rebuild of all dependent packages
will be required.
http://pkgs.fedoraproject.org/cgit/ImageMagick.git/log/http://koji.fedoraproject.org/koji/buildinfo?buildID=508129
Dan
Hi,
the Change Proposals Submission Deadline is coming in one week!
The date is Tuesday, 2014-04-08 for System Wide Changes. Self
Contained Changes deadline will be set later.
I'd like to ask especially WGs to work on the PRD/Tech
Specs break out into the Change Proposals - so the scope of release
can be evaluated and also for tracking purposes to know where we are
with Fedora 21/Next release.
One particular topic that should be included are product deliverables,
to get a wider agreement on how each product will be distributed and
to allow release engineering team (and others as websites) to adjust
for product needs.
See https://fedoraproject.org/wiki/Changes/Policy for current policy for
submissions and start a new proposal using this template
https://fedoraproject.org/wiki/Changes/EmptyTemplate
Let me know in case of any issues, I'll try to help you!
[1] https://fedoraproject.org/wiki/Releases/21/Schedule
Jaroslav
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce