Hi,
I just build libzip-1.2.0-0.fc26.
This build temporarily provides both the old and new libraries
(to not break buildroot)
API changes:
http://rpms.remirepo.net/compat_reports/libzip/1.1.3_to_1.2.0/compat_report…
So, mostly, only the removed "zip_archive_set_tempdir" symbol could
raise some issues.
I will run a rebuild of other packages:
amftools
ebook-tools
fuse-zip
kchmviewer
libconcord
librfm
libsigrok
libykneomgr
naev
nodejs-zipfile
openlierox
php-pecl-zip
repsnapper
rodent
subsurface
vifir
Then I will rebuild without the compat hack.
Ping me if I miss some important stuff,
Remi.
= Proposed Self Contained Change: Arm Support In FMW =
https://fedoraproject.org/wiki/Changes/ArmSupportInFmw
Change owner(s):
* Martin Bříza <mbriza AT redhat DOT com>
Fedora Media Writer will gain the ability to write ARM images to SD
cards and other portable media.
== Detailed Description ==
With ARM (ARMv7A) being one of the primary architectures of Fedora, we
should support writing the images to bootable media for devices with
this architecture.
This means Fedora Media Writer will have to list the ARM images, offer
their download and be able to unpack them reliably (as they're shipped
LZMA-compressed - .xz). Memory card support should be improved,
especially in terms of reading drive information - many SD card
drivers report wrong names, sizes and media presence.
This will come along with many more features in FMW, such as
fullscreen screenshot preview, automatic FMW update check on Windows
and Mac, better reliability and performance improvements.
== Scope ==
* Proposal owners:
Implementation of this Change
* Other developers:
N/A (not a System Wide Change)
* Release engineering:
N/A
* List of deliverables:
N/A (not a System Wide Change)
* Policies and guidelines:
N/A (not a System Wide Change)
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Greetings!
Today, on 2017-Feb-28, we have reached Fedora 26 Change
Checkpoint:Completion deadline (testable) [1].
At this point, all accepted changes [2] should be substantially
complete, and testable. Additionally, if a change is to be enabled by
default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it
achieved completeness.
Incomplete and non testable Changes [3] will be reported to FESCo for
2017-Mar-03 meeting. Contingency plan for System Wide Changes, if
planned for Alpha (or in case of serious doubts regarding Change
completion), will be activated.
Side note: Currently we still have two Self-Contained Changes waiting
for FESco approval [4]. I am going to ask FESCo to consider postponing
of this Checkpoint for these two Changes if these are approved.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
[2] https://fedoraproject.org/wiki/Releases/26/ChangeSet
[3] http://red.ht/2ltXbqk
[4] https://pagure.io/fesco/issue/1635#comment-350632
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Greetings.
I've just finished setting up a new group of test machine instances for
package maintainers in the Fedora Infrastructure Private Cloud.
They now include ppc64 and ppc64le instances.
(We hope to add aarch64 before too long).
These instances should be faster and closer to repositories than
previous test instances, and require no special ssh config to use.
Please see:
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintaine…
for more details and access information on all the available instances.
These instances can help maintainers duplicate problems or gather
information from Fedora versions they may not have handy.
Hope they help,
kevin
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org