devel December 2016

devel@lists.fedoraproject.org

217 participants
258 discussions

Two more concrete ideas for what a once-yearly+update schedule would look like
by Matthew Miller 03 Aug '17

03 Aug '17

Trying to make this idea a little more concrete. Here's two suggestions for how it might work. These are strawman ideas -- please provide alternates, poke holes, etc. And particularly from a QA and rel-eng point of view. Both of these are not taking modularity into account in any way; it's "how we could do this with our current distro-building process". Option 1: Big batched update 1. Release F26 according to schedule https://fedoraproject.org/wiki/Releases/26/Schedule 2. At the beginning of October, stop pushing non-security updates from updates-testing to updates 3. Bigger updates (desktop environment refreshes, etc.) allowed into updates-testing at this time. 4. Mid-October, freeze exceptions for getting into updates-testing even. 5. Test all of that together in Some Handwavy Way for serious problems and regressions. 6. Once all good, push from updates-testing to updates at end of October or beginning of November. Option 2: Branching! 1. Release F26 according to schedule. 2. July/August: branch F26.1 from F26 (not rawhide) 3. Updates to F26 also go into F26.1 (magic happens here?) 4. No Alpha, but do "Beta" freeze and validation as normal for release. 5. And same for F26.1 final 6. And sometime in October/November, release that (but without big press push). 7. GNOME Software presents F26.1 as upgrade option 8. F26 continues in parallel through December 9. In January, update added to F26 which activates the F26.1 repo. 10. And also in January updates stop going to F26. Some of this idea, by the way, is reminiscent of Spot's suggestions at FUDCon Lawrence in 2013. This is not completely coincidence - I always liked those ideas! -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

39 150

Xulrunner - intent to remove from Fedora 24
by Martin Stransky 27 Jun '17

27 Jun '17

Hi, does anyone use the xulrunner package? (and gecko-devel actually). Mozilla does not maintain it any more and the XUL as technology is going to be removed/deprecated. I'd like to remove the package from Fedora 24. ma.

21 30

F25 Self Contained Change: IBus Emoji Typing
by Jaroslav Reznik 09 May '17

09 May '17

= Proposed Self Contained Change: IBus Emoji Typing = https://fedoraproject.org/wiki/Changes/IBus_Emoji_Typing Change owner(s): * Takao Fujiwara <tfujiwar [at] redhat [dot] com> The IBus core will provide the Emoji Unicode typing with the IBus XKB engines. == Detailed Description == IBus has already provided Unicode hex codes tying with Ctrl-Shift-u and now we think the similar implementation for the Emoji typging. With IBus XKB engines, Emoji typing will be provided with the Emoji annotations [1] following Ctrl- Shift-e. == Scope == * Proposal owners: - IBus core provide the dictionary of the Emoji typing. - IBus XKB engines load the Emoji dictionary. * Other developers: N/A * Release engineering: N/A - List of deliverables: N/A * Policies and guidelines: N/A * Trademark approval: N/A [1] http://unicode.org/emoji/charts/index.html#col-annotations

7 24

iproute package update policy
by Phil Sutter 14 Mar '17

14 Mar '17

Hi, So far my idea of maintaining Fedora's iproute package was to do full version updates only in Rawhide and backport patches selectively to stable versions on behalf of bug reports. But since stable versions indeed receive full kernel updates (not just backported patches), there is an understandable amount of frustration amongst users when the shiny new kernel that comes with e.g. F22 provides features userspace does not support. Especially since upstream iproute2 does not really have a concept of stable versions, I'm in a bit of a dilemma here: update to keep in sync with the kernel or not update to not unnecessarily destabilize the system? Any comments/advice are highly appreciated. Thanks, Phil

7 13

whatever happened to yum + btrfs snapshotting?
by Neal Becker 13 Mar '17

13 Mar '17

Some time back there was discussion of being able to rollback yum updates via btrfs snapshotting. As I recall, it turned out that the default btrfs install was not setup correctly to make this feasible (I had briefly tested it on my machine). I haven't heard anything since - this seems like a great idea. -- -- Those who don't understand recursion are doomed to repeat it

7 7

Is Kalpa Welivitigoda still active at maintaining packages?
by Iiro Laiho 25 Feb '17

25 Feb '17

Hi, I am asking if anyone knows anything about the whereabouts of Fedora developer Kalpa Welivitigoda? He is the maintainer of unetbootin package. Bug 1229874 would need fixing, but it seems that he is not responding to the bug comments anymore. I tried to ask him about that matter via Facebook as well last Tuesday, but he doesn't seem to respond there either. – Iiro Laiho

3 2

Call to retire gstreamer-0.10
by Michael Cronenworth 13 Feb '17

13 Feb '17

Hi, As I'm sure everyone is well aware gstreamer-0.10 is obsolete and has been replaced by gstreamer-1.0. An upstream release for gst-0.10 has not been made in over 4 years. Last month there were a handful of security vulnerabilities disclosed[1] and upstream no longer maintains the 0.10 series. While we could patch and update our Fedora packages this is a perfect opportunity to retire it. Here is an approximate list of packages depending on gst-0.10. They themselves should be considered obsolete or retirement material as their upstreams may not have adopted gst-1.0. If the package doesn't have a gst-1.0 equivalent there may be some cases where we could patch in support for gst-1.0. Are there any non-Fedora software that would prevent retirement from being possible? anchorman banshee-community-extensions bigloo-libs clutter-gst compat-wxGTK3-gtk2-media drawtk evas-generic-loaders flumotion gcompris gloobus-preview gnome-mud gnomebaker gstreamer-devel gstreamer-ffmpeg gstreamer-plugins-bad gstreamer-plugins-bad-free gstreamer-plugins-bad-free-extras gstreamer-plugins-base gstreamer-plugins-base-tools gstreamer-plugins-good gstreamer-plugins-good-extras gstreamer-plugins-ugly gstreamer-python gstreamer-rtsp gstreamer-rtsp-python gstreamermm gstreamermm-devel ignuit iptux libgnome-media-profiles libnice-gstreamer lordsawar media-explorer moodbar oggconvert perl-GStreamer perl-GStreamer-Interfaces player pocketsphinx-plugin presence psimedia qt-mobility-multimediakit sap subtitleeditor vagalume winswitch wxGTK-media wxGTK3-media xfce4-mixer xfce4-volumed Thank you, Michael [1] https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-advancing-expl…

18 34

HEADS UP: shapelib soname bump
by Sandro Mani 12 Feb '17

12 Feb '17

Hi I'm preparing the shapelib-1.4.0 update, which bumped the soname. There are no API changes, it was just to synchronize with the debian soname. Dependent packages are: gpsbabel-0:1.5.3-4.fc24 grads-0:2.0.2-18.fc26 librecad-0:2.1.0-1.fc25 marble-widget-qt5-1:16.08.3-1.fc26 plplot-libs-0:5.11.1-5.fc25 I'll need help rebuilding the above packages. Thanks Sandro

5 8

Weak password madness is back again
by Hans de Goede 22 Jan '17

22 Jan '17

Hi, So 2 devel cycles ago we had this whole discussion about how forcing people to choose strong passwords in anaconda was making live hard for testers / test-installs and this decision was reverted. So now here I'm doing a F25 Fedora ARM test install, end up in the gnome-ified first-time-setup wizzard and cannot continue until I make my test-user password strong enough. UGH. So can we get this fixed please, or do we need to escalate this all the way up to FESco again ? Regards, Hans

10 23

RFC: static builds for user emulators in Fedora QEMU RPMs
by Daniel P. Berrange 14 Jan '17

14 Jan '17

For those who aren't familiar, QEMU actually provides two completely different sets of emulators - system emulators - they emulate a full virtual machine and thus run a full guest OS. - user emulators - they emulate the Linux userspace ABI letting you run non-native arch executables directly. The user emulators are what I'm concerned with in this mail, so ignore the system emulators. Currently all the user emulators are provided in the "qemu-user" RPM which also includes files in /usr/lib/binfmt.d to register each emulator binary as a binary format handler for its respective architecture. This is ok if you have a non-native arch binary that's statically linked and you just want to run it from context of your main OS root filesystem. Running dynamic linked binaries won't fly because if say running an arm binary on x86_64 host, it'll look for /lib/libc.so and find the i386 one, instead of the arm one. You can't set LD_LIBRARY_PATH to override this as the env var will apply to both qemu-arm (an x86_64 binary) and the binary it is trying to run (an arm binary). More typical though is that you have a directory containing an fullish install tree of a non-native architecture and you just want to chroot into that. When doing such a chroot, the qemu-$ARCH emulator must be present inside the chroot too. ie the x86_64 build of /usr/bin/qemu-arm must be present inside at /my/chroot/for/fedora-arm/usr/bin/qemu-arm. So again you have the potential problem of clashing libc.so in /usr/lib It is a shame Fedora doesn't have full multi-arch support, instead of merely multi-lib to avoid these clashing lib dirs across architecture RPMs. The recommended way to deal with this for the qemu user emulator binaries to be statically linked, so when copied inside the non-native arch chroot, they never need to resolve any native arch libraries. Fedora's qemu user binaries are all dynamic linked right now. Debian handles this by having several packages [1] - qemu-user - the dynamic linked qemu user binaries - qemu-binfmt - binfmt rules registering the dynamic linked binaries - qemu-user-static - the static linked qemu user binaries *and* binfmt rules to register them. The static binaries all have -static suffix on their name NB, this means qemu-binfmt and qemu-user-static are mutually exclusive since they both provide the same binfmt files. You can however have both qemu-user and qemu-user-static installed as their binary names won't clash, and in this case the static ones will be registered as binfmts This nice thing about this multiple package approach is that when you copied the x86_64 build of the "qemu-arm-static" binary into your arm chroot, you still then have the possibility of installing the arm build of the "qemu-arm" binary inside that chroot without filename clash. An alternative simpler approach would be to just have one package, qemu-user, which contains the static binaries and never ship any dynamic linked qemu user binaries. This is slightly more restrictive though, as explained in the previous paragraph, so I'd like to avoid doing that. I'd like to make using non-native arch chroots simple with Fedora without people needing to manually build their own static QEMU binaries, or download static binaries provided by another distro[2]. So I'm suggesting to make a change to Fedora qemu packages to essentially copy the way Debian has done things. Specifically I will - Pull the binfmt registration files out of qemu-user and into a new qemu-binfmt package which depends on qemu-user. - Add static builds of qemu user emulators to a new qemu-user-static package, along with binfmt registration files The static build of QEMU user emulators is moderately light on dependancies, only requiring glib2-static, pcre-static, zlib-static and glibc-static packages. The change to introduce a qemu-binfmt package has small upgrade implications since anyone with qemu-user installed today, will loose the binary format rules unless they manually install qemu-binfmt. I think the number of people affected is probably quite small, and some of them may well wish to use qemu-user-static instead anyway. Obviously this would only be done in rawhide, not any existing stable releases of Fedora. Nothing will change about the rest of QEMU packaging - ie all system emulators will continue to use dynamic linking Regards, Daniel [1] https://wiki.debian.org/QemuUserEmulation [2] https://rwmj.wordpress.com/2013/12/22/how-to-run-aarch64-binaries-on-an-x86… -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|

9 17

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel December 2016