devel June 2013

devel@lists.stg.fedoraproject.org

224 participants
259 discussions

twinkle: Intent to retire
by Kevin Fenzi 12 Aug '13

12 Aug '13

Greetings. I'm the current Fedora maintainer of the twinkle package. Sadly, it's in poor shape: - Segfaults on start in recent fedora versions (depending on config). - Has not had an upstream release in 4+ years. - Has not had any response from upstream maintainer in at least that long. - Uses Qt3 and a complex stack of c++ libraries. - 8 open bugs: https://apps.fedoraproject.org/packages/twinkle/bugs/all Debian removed it last year, Arch moved it to a user repo instead of the main repo last year. So, I am going to retire this package in rawhide soon unless there's folks with a very strong C++ background wishing to fix issues and basically become the new upstream. kevin

11 21

F20 System Wide Change: Perl 5.18
by Jaroslav Reznik 08 Aug '13

08 Aug '13

= Proposed System Wide Change: Perl 5.18 = https://fedoraproject.org/wiki/Changes/perl5.18 Change owner(s): Petr Písař <ppisar(a)redhat.com>, Jitka Plesníková <jplesnik(a)redhat.com> A new perl 5.18 version brings a lot of changes done over a year of development. See [1] for more details. == Detailed description == New perl is released every year and updates containing mainly bug fixes follow during the year. The 5.18.0 version is stable release this year and 5.18.1 and subsequent revisions will follow during the year to fix issues introduced in 5.18.0. Because of change in dlopen(3) from RTLD_GLOBAL to RTLD_LOCAL (bug #960048) [2], we will try to link all native perl module DSOs to libperl.so explicitly. This item needs discussion. Current status does not allow to use perl interpreter via dlopen() from other programs (like slapd, snmpd), but proposed change can bring other unforeseen difficulties (like double-linking). [1] http://search.cpan.org/dist/perl-5.18.0/pod/perldelta.pod [2] https://bugzilla.redhat.com/show_bug.cgi?id=960048 _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

13 22

Attention F19 users! DO NOT upgrade to Erlang R16B01 if prompted.
by Peter Lemenkov 06 Aug '13

06 Aug '13

Hello All. Recent Erlang bugfix release fixed a few issues but added another nasty one - actually almost all Erlang application will fail to start. I'm working on it. Meanwhile please stay with R16B or downgrade to it. Here are few links for those who's curious: * http://thread.gmane.org/gmane.comp.lang.erlang.general/68995/focus=69001 * https://issues.apache.org/jira/browse/COUCHDB-1833 * http://thread.gmane.org/gmane.comp.networking.rabbitmq.general/23889 * http://thread.gmane.org/gmane.comp.lang.erlang.general/69019 Sorry for that. I hope to fix everything before next monday. -- With best regards, Peter Lemenkov.

1 4

Orphaning Docky
by Lukas Zapletal 01 Aug '13

01 Aug '13

Hello all, although package Docky was lot of work for me (licensing patching etc) I am no longer using it and last two releases were very unstable. There are couple of bugzillas reported mainly because of gconf migration. """ Docky is an advanced shortcut bar that sits at the edges of your screen. It provides easy access to some of the files, folders and applications on your computer, displays which applications are currently running, holds windows in their minimized state and more. Docky is written in mono. http://wiki.go-docky.com """ Please ping me if you are interested to maintain the package. -- Later, Lukas "lzap" Zapletal #katello #systemengine

2 1

Fwd: Orphaning few packages
by Nicolas Chauvet 26 Jul '13

26 Jul '13

Hi Because I need more concentration on fewer packages, here is a list of packages I'm orphaning, some might end deprecated at some point One the same line are package linked together. cinepaint (can be built without oyranos) directfb tslib libproxy (critical path) libmodman oyranos icc_examin elektra fmtools makehuman animorph mhgui libmpcdec jrosetta matio perl\* (see pkgdb) Please add yourself as maintainer. Nicolas (kwizart)

10 20

Plan to drop php-pecl-apc from Fedora - Urgent review needed
by Remi Collet 20 Jul '13

20 Jul '13

Hi, PHP opcode cache is a very important feature for sites with large traffic. APC is mostly a dead project. No stable release for php 5.4, lot of issues. Upstream move most of dev resources to new "Zend OPcache" which will be the official opcode cache, integrated in PHP 5.5.0 To be able to drop this package, we need 1/ php-pecl-zendopcache, the Zend OPcache for php 5.3 / 5.4 https://bugzilla.redhat.com/show_bug.cgi?id=911111 Target version is EPEL-6 and Fedora <= 18 as Fedora >= 19 already have php-opcache (subpackage of main php, same code) 2/ php-pecl-apcu, APCu, the drop-in replacement of APC for user data cache. https://bugzilla.redhat.com/show_bug.cgi?id=928196 Target versions : Fedora >= 18 and EPEL-6 Please, review this. Remi.

4 5

More unhelpful update descriptions
by Michael Catanzaro 16 Jul '13

16 Jul '13

There still seems to be an issue with the update descriptions that we present in PackageKit. A lot of people just write "update to version x.y.z" which is not great, but a whole lot better than some of the ones we've been seeing recently. For example, from two updates I got today: * "Not tested locally yet, I need to spin back up a Fedora 18 VM." * "Here is where you give an explanation of your update." Now the first one is obviously a one-off mistake, but had the update been checked over just once it would have been caught. The placeholder one is a big recurring problem, though: it seems to show up at least every week or so, which is not OK. And once, about two months ago -- I really should have complained then and not now -- an update was pushed where the text displayed in PackageKit was something along the lines of "why do I have to describe my update here when I've already filled out the RPM changelog." I wish it was a joke, but something like that was actually pushed as the description of a F18 update presented to every user who glances over the updates.... We need written policy on update descriptions, since despite the last discussion on this list [1], poor update descriptions continue to blemish the otherwise-professional image of the distro. A starting point suggestion: "Every update should have at least a one sentence description." If the update is not worth writing one sentence about, it is not worth pushing out. Happy Friday, Michael Catanzaro [1] https://lists.fedoraproject.org/pipermail/devel/2013-March/179655.html

27 70

F19 upgrade pulls in a lot of i686 packages
by Steve Grubb 07 Jul '13

07 Jul '13

Hi, Did anyone notice all the i686 packages that get pulled in if you try to upgrade from F18? My system has no i686 packages on it today. But when I try to upgrade it starts getting i686 dependencies pulled in. It starts like this: ---> Package mesa-libEGL.x86_64 0:9.2-0.7.20130528.fc18 will be updated ---> Package mesa-libEGL.x86_64 0:9.2-0.12.20130610.fc19 will be an update ---> Package mesa-libEGL-devel.i686 0:9.2-0.12.20130610.fc19 will be obsoleting --> Processing Dependency: libEGL.so.1 for package: mesa-libEGL-devel-9.2-0.12.20130610.fc19.i686 ---> Package mesa-libEGL-devel.x86_64 0:9.2-0.12.20130610.fc19 will be obsoleting >From that it goes into: ---> Package mesa-libEGL.i686 0:9.2-0.12.20130610.fc19 will be installed --> Processing Dependency: libxcb.so.1 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libxcb-xfixes.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libxcb-shape.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libxcb-render.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libxcb-dri2.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libwayland-server.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libwayland-client.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libudev.so.1(LIBUDEV_183) for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libudev.so.1 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libselinux.so.1 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libpthread.so.0(GLIBC_2.0) for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libpthread.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libglapi.so.0 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libgbm.so.1 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libdrm.so.2 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libdl.so.2(GLIBC_2.1) for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libdl.so.2(GLIBC_2.0) for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libdl.so.2 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libc.so.6(GLIBC_2.4) for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libX11.so.6 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 --> Processing Dependency: libX11-xcb.so.1 for package: mesa-libEGL-9.2-0.12.20130610.fc19.i686 and then later dozens more get pulled in. Should looking for this be part of future release criteria? -Steve

6 7

Minimal install diff from F16 to F19 (TC6)
by Adam Williamson 07 Jul '13

07 Jul '13

As it may be interesting and I have the data on hand, here's the package diff between a minimal install of F16 and a minimal install of F19. F16 has 203 packages (I think it's really 202 but I somehow got an extra one into my test), F19 TC6 has 238. --- 16min.txt 2013-06-19 09:06:52.075305098 -0700 +++ 19tc6_min.txt 2013-06-20 00:09:20.725960756 -0700 @@ -1,48 +1,47 @@ acl -attr audit audit-libs authconfig +avahi +avahi-autoipd +avahi-libs basesystem bash bind-libs-lite bind-license biosdevname -bzip2 bzip2-libs ca-certificates -checkpolicy chkconfig coreutils -coreutils-libs cpio cracklib cracklib-dicts cronie cronie-anacron crontabs -cryptsetup-luks-libs +cryptsetup-libs curl cyrus-sasl cyrus-sasl-lib -dash -db4 -db4-utils dbus +dbus-glib dbus-libs +dbus-python device-mapper device-mapper-event device-mapper-event-libs device-mapper-libs +device-mapper-persistent-data dhclient dhcp-common dhcp-libs diffutils -dmraid -dmraid-events +dnsmasq dracut e2fsprogs e2fsprogs-libs +ebtables elfutils-libelf expat fedora-logos @@ -53,8 +52,8 @@ findutils fipscheck fipscheck-lib +firewalld freetype -gamin gawk gdbm gettext @@ -64,26 +63,35 @@ glibc-common gmp gnupg2 +gnutls +gobject-introspection gpgme -gpg-pubkey grep +groff-base grub2 +grub2-tools grubby gzip +hardlink hesiod hostname hwdata info initscripts iproute +iprutils iptables iputils +json-c kbd kbd-misc kernel keyutils-libs +kmod +kmod-libs kpartx krb5-libs +less libacl libassuan libattr @@ -93,28 +101,43 @@ libcom_err libcroco libcurl +libdaemon libdb +libdb-utils libdrm +libedit +libee +libestr libffi libgcc libgcrypt libgomp libgpg-error +libgudev1 libidn +liblognorm +libmicrohttpd libmount +libnl3 +libpcap libpciaccess +libpipeline +libpwquality libselinux +libselinux-python libselinux-utils libsemanage libsepol libss libssh2 libstdc++ -libudev +libsysfs +libtasn1 libunistring libuser libutempter libuuid +libverto libxml2 linux-atm-libs linux-firmware @@ -122,29 +145,35 @@ lua lvm2 lvm2-libs -m4 -mingetty -module-init-tools +make +man-db +mozjs17 ncurses ncurses-base ncurses-libs -net-tools -netxen-firmware +nettle +NetworkManager +NetworkManager-glib newt newt-python nspr nss -nss-myhostname nss-softokn nss-softokn-freebl nss-sysinit +nss-tools nss-util openldap openssh +openssh-clients openssh-server openssl +openssl-libs os-prober +p11-kit +p11-kit-trust pam +parted passwd pciutils-libs pcre @@ -154,17 +183,26 @@ plymouth-core-libs plymouth-scripts policycoreutils +polkit +polkit-pkla-compat popt +ppp procmail -procps -psmisc +procps-ng pth +pygobject3-base pygpgme +pyliblzma python +python-decorator python-iniparse python-libs python-pycurl +python-slip +python-slip-dbus python-urlgrabber +pyxattr +qrencode-libs readline rootfiles rpm @@ -176,28 +214,26 @@ selinux-policy selinux-policy-targeted sendmail -setserial setup -sgpio shadow-utils shared-mime-info slang sqlite sudo -system-config-firewall-base systemd +systemd-libs systemd-sysv -systemd-units sysvinit-tools -tar tcp_wrappers-libs tzdata -udev ustr util-linux vim-minimal which +wpa_supplicant +xz xz-libs yum yum-metadata-parser zlib -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

23 58

Bad file access on the rise
by Steve Grubb 06 Jul '13

06 Jul '13

Hello, Every now and then I look at the distribution to see that from an auditing perspective the OS is nicely behaving in the absence of intrusion. Meaning we are not getting audit events unnecessarily. One of the typical rules required by the DISA STIG is to watch for file access being denied due to permissions. This could be indicative of someone trying to access something they shouldn't. The rule is: -a always,exit -F arch=b64 -S creat -S open -S openat -S truncate -S ftruncate -F exit=-EPERM -F auid>=500 -F auid!=4294967295 -k access Lately F18 has been showing lots of audit events where access is being denied opening a file: # aureport --start today --key --summary Key Summary Report =========================== total key =========================== 537 access 25 module-load 6 container-config 6 system-locale 6 bypass This is after using the system for 2 hours. Let's see what files were trying to be accessed: ]# ausearch --start today -k access --raw | aureport --file --summary | head File Summary Report =========================== total file =========================== 88 /dev/shm/pulse-shm-838240362 88 /dev/shm/pulse-shm-191856280 88 /dev/shm/pulse-shm-3756395503 7 /dev/shm/pulse-shm-1545675388 6 /usr/share/icons/hicolor/48x48/apps/firefox.png Let's look at one of these pule-shm events: # ausearch --start today -k access -f pulse-shm -i --just-one ---- type=PATH msg=audit(06/07/2013 07:13:46.377:215) : item=0 name=/dev/shm/pulse- shm-3756395503 inode=25089 dev=00:10 mode=file,400 ouid=gdm ogid=gdm rdev=00:00 obj=system_u:object_r:user_tmpfs_t:s0 type=CWD msg=audit(06/07/2013 07:13:46.377:215) : cwd=/ type=SYSCALL msg=audit(06/07/2013 07:13:46.377:215) : arch=x86_64 syscall=open success=no exit=-13(Permission denied) a0=0x7fffbeda83c0 a1=O_RDONLY| O_NOFOLLOW|O_CLOEXEC a2=0x0 a3=0x0 items=1 ppid=2369 pid=2370 auid=sgrubb uid=sgrubb gid=sgrubb euid=sgrubb suid=sgrubb fsuid=sgrubb egid=sgrubb sgid=sgrubb fsgid=sgrubb ses=2 tty=(none) comm=pulseaudio exe=/usr/bin/pulseaudio subj=unconfined_u:system_r:unconfined_t:s0 key=access So, gdm is creating a file 400 and pulse-audio can't open it. Is it suppose to be like that? What about the firefox one? type=PATH msg=audit(06/07/2013 08:13:52.465:633) : item=0 name=/usr/share/icons/hicolor/22x22/apps/firefox.png inode=16943495 dev=09:01 mode=file,644 ouid=root ogid=root rdev=00:00 obj=system_u:object_r:usr_t:s0 type=CWD msg=audit(06/07/2013 08:13:52.465:633) : cwd=/home/sgrubb type=SYSCALL msg=audit(06/07/2013 08:13:52.465:633) : arch=x86_64 syscall=open success=no exit=-1(Operation not permitted) a0=0x7fc3be80e880 a1=O_RDONLY| O_NOATIME a2=0x0 a3=0x0 items=1 ppid=2395 pid=2670 auid=sgrubb uid=sgrubb gid=sgrubb euid=sgrubb suid=sgrubb fsuid=sgrubb egid=sgrubb sgid=sgrubb fsgid=sgrubb ses=2 tty=(none) comm=firefox exe=/usr/lib64/firefox/firefox subj=unconfined_u:unconfined_r:unconfined_t:s0 key=access It is using the O_NOATIME flag. To use O_NOATIME requires CAP_FOWNER and firefox should no have capabilities. So, how bad is the NOATIME problem? # ausearch --start today -k access -i | grep NOATIME | awk '{ print $30 }' | ~sgrubb/working/BUILD/numeric-tools/summary exe=/usr/bin/cinnamon 193 exe=/usr/lib64/firefox/firefox 31 exe=/usr/bin/gnome-terminal 12 exe=/usr/bin/nautilus 10 exe=/usr/bin/xchat 4 exe=/usr/bin/nm-applet 2 exe=/usr/bin/kontact 2 This seems to account for a good number of the problematic accesses. Anything except backup programs using O_NOATIME is probably thinking they are making the program faster, but instead is failing to open files. -Steve

17 70

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2013