devel June 2014

devel@lists.fedoraproject.org

224 participants
220 discussions

Dangling "clustering" reference in comps-f21.xml.in
by Jerry James 07 Jul '14

07 Jul '14

There is a reference to a "clustering" group inside the "servers" category in comps-f21.xml.in, but no definition of "clustering" anywhere that I can see. Also: [comps]$ make validate ... comps-f21.xml:46: element packagereq: Relax-NG validity error : Element packagereq failed to validate attributes comps-f21.xml:46: element packagereq: Relax-NG validity error : Element packagelist has extra content: packagereq comps-f21.xml:118: element packagereq: Relax-NG validity error : Element packagereq failed to validate attributes comps-f21.xml:118: element packagereq: Relax-NG validity error : Element packagelist has extra content: packagereq comps-f21.xml:73: element group: Relax-NG validity error : Invalid sequence in interleave comps-f21.xml:73: element group: Relax-NG validity error : Element group failed to validate content comps-f21.xml:73: element group: Relax-NG validity error : Expecting element environment, got group comps-f21.xml:73: element group: Relax-NG validity error : Element comps has extra content: group comps-f21.xml fails to validate ... Is that output expected? I see similar output from comps-el4.xml, comps-el5.xml, comps-f18.xml, comps-f19.xml, and comps-f20.xml as well. Regards, -- Jerry James http://www.jamezone.org/

1 1

Package reviev : tayga
by William 06 Jul '14

06 Jul '14

Hi, I am looking to have the following package reviewed for inclusion into fedora. Tayga is a NAT64 implementation in userland. With the help of DNS64 (BIND), it allows an ipv6 only client to communicate with the ipv4 internet. http://www.litech.org/tayga/ I have attached the SRPM of what I have created. There are a few things that could change. First, I had thought that I would need more selinux policy than I did. At the moment the policy just provides a filecontext. Is there a better way to do this? The ifup / ifdown script read their variables from the /etc/tayga configuration file. In most scenarios, a system will run only one instance of this. However I would like feedback on: Should I enable it so that the ifup/down can accept a tayga.conf parameter to read OR Should the ifup/ifdown script generate the tayga.conf on the fly to say /var/run/tmp somewhere from values provided in the ifup / ifdown? Additionally, what I have in these scripts should really be reviewed, as I have never written them before. Finally, tayga is a long running process, as such, I have enabled the hardened build. It is possible to run as an alternate user and in a chroot of it's DB dir. What is the best way to go about adding a user for this package for the daemon to run as? Looking forwards to comments and advice, -- Sincerely, William Brown http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xEFC416D781A8099A

2 5

An update on System Tray, Plasma Next ("KDE 5") and GTK+
by Kevin Kofler 06 Jul '14

06 Jul '14

Hi, Quoting from Marco Martin's blog post: http://notmart.org/blog/2014/06/systemtray-plasma-next-and-gtk/ (Annotations from me are enclosed in parentheses.) > You may have heard that KDE Plasma Next won’t support anymore the old > X11,Xembed-based systemtray icons. (KDE Plasma Next is the next major version of the KDE workspace(s), to replace the current KDE Plasma 4 workspace(s). In particular, the new version is scheduled to replace KDE Plasma Desktop 4 in Fedora 22.) > (More information here > [http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/] (I already posted a message to this mailing list back then.) > Years ago, we developed a nicer, model/view based alternative in which is > the shell that actually draws the systemtray icon, allowing better > integration with the workspace, it’s a specification that is now shared > between KDE and Ubuntu Unity. > All KDE applications use it already, Qt4/Qt5-only application will use it > depending on a small patch (and soon Qt5 will do out of the box) > > But also GTK has some options: until today I was aware only about the > Ubuntu’s appindicator library [https://launchpad.net/libappindicator] but > I have just been contacted by the author of another neat library, that can > be found here on GitHub [https://github.com/jjk-jacky/statusnotifier] > It’s a very small, few dependencies GObject-based library that allows a > GTK3 application to export and control a statusnotifier-based systemtray > icon. I just tested it on KDE4 and Plasma Next and seems to work quite > well. > So if you have a GTK application that is using a systemtray icon, and you > would like the icon to be integrated in the next version of Plasma as > well, now you have an option more (and of course, the author will be happy > of any patch/bugreport/bugfix). (Short version: If you maintain a GTK+ application that uses system tray icons, please work with upstream on getting it ported to either https://launchpad.net/libappindicator or https://github.com/jjk-jacky/statusnotifier by Fedora 22 at the latest, or enable existing upstream support ASAP.) Kevin Kofler

2 1

delta rpms - can we turn them off
by Troy Dawson 03 Jul '14

03 Jul '14

Hi, I have a very small server room. It has very good network, but lots of not very powerful computers. Many of them are ARM based. As I hear about ARM users taking 8 hours to update 1 package (I've had it take 12 hours to fail to update a package) I irritates me. The fact that Fedora practically forces people to use delta rpm's has rattled my cage for quite a while. I eventually opened a bugzilla with what I consider a reasonable compromise.[1] " Please put deltarpm=1 in /etc/yum.conf, at a minimum. A comment about it would be better. It would be even better if you put deltarpm=0 for the arm builds. " Why bring it up here? Two reasons. 1 - As you can see, my bugzilla hasn't even been acknowledged. 2 - I'm wondering about dnf (Duke Nukem Forever) -- What is it's stance on delta rpms? --- Does it do them? --- Does it force you to do them like yum does? --- Is there an easy to find option to turn them off/on? Thanks Troy Dawson [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1074600

19 42

libgcrypt soname bump in rawhide
by Tomas Mraz 03 Jul '14

03 Jul '14

I'm rebasing libgcrypt in rawhide to libgcrypt-1.6.1. The new upstream release contains many improvements over the old one especially in terms of new crypto algorithm support and performance improvements. Unfortunately the rebase bumps soname to libgcrypt.so.20 due to dropping some long-ago deprecated API calls. This should not break builds of any reasonably current software. I've included the temporary old shared library so the buildroots are not broken. I will try to rebuild the dependencies eventually. Regards, -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb (You'll never know whether the road is wrong though.) _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

11 21

Heads-up on rpm 4.12 coming to rawhide soon
by Panu Matilainen 02 Jul '14

02 Jul '14

Hi all, Rpm 4.12 alpha just got released: http://lists.rpm.org/pipermail/rpm-announce/2014-June/000045.html The plan is to update rawhide to this shiny new version first thing on Monday morning and babysit as needed (ie the usual drill), but if you're feeling bored over the weekend or its as rainy wherever you live as it is in here now, and you're feeling a little bit brave, give it a spin in the meanwhile: https://copr.fedoraproject.org/coprs/pmatilai/rpm-snapshot/ The copr packages are for rawhide only and should be very close to what goes into rawhide on Monday. If you're dying to test but not willing to rawhide all the way, they can be used on F20 too if you 1) install perl-generators from rawhide 2) remove rpm-python3 package before updating As the announcement says, there are some rough edges still (as in, there's a reason its alpha). I run it on my systems and it's not expected to eat anybody (or their systems) alive, but do pay attention... Bug reports and other feedback welcome. - Panu -

4 10

Tasklist for the Fedora Workstation
by Christian Schaller 02 Jul '14

02 Jul '14

Hi everyone, As we are ramping up the development effort around the workstation we wanted to help increase transparency and enable more community participation in the Fedora Workstation effort by providing a more detailed view of the various tasks underway as derived from the more high level PRD and Technical Specification documents. You can find the current version of the tasklist here - http://fedoraproject.org/wiki/Workstation - but we hope to expand on it in the coming days and weeks to be even more comprehensive and also include more explanations around the motivation for each task. The list enumerates the various efforts that is being undertaken around the Fedora Workstation effort and also puts a name next to many of the items. If you are interested in helping out with any of these efforts please get in touch by reaching out either to the Working group board members or to the people listed next to the tasks in question. For those of you not familiar with the working group we have contact information and board membership information available on this page: http://fedoraproject.org/wiki/Workstation If you are getting this email you probably already know about the mailing list, but the working group can also be reached on IRC on #fedora-workstation on freenode. Looking forward to discussing our plans with both new and old contributors to the workstation product effort. Feel free to ask questions about the various tasks as I realize that the list is quite low on detail atm., and not all items might be self explanatory and as mentioned we do hope to add more detailed information to each item in the next few days. Sincerely, Christian Schaller

3 2

Agenda for Env-and-Stacks WG meeting (2014-07-01)
by Marcela Mašláňová 02 Jul '14

02 Jul '14

On odd weeks WG meeting will be at 15:00 UTC, 17:00 Central Europe, 11:00 (noon) Boston, 8:00 San Francisco, 0:00 Tokyo in #fedora-meeting on Freenode. = Topics = * free seats in Env WG * Taskotron and rpmgrill * OpenFloor

1 1

Non-responsive maintainer: Hubert Plociniczak (fas: hubert)
by Peter Lemenkov 02 Jul '14

02 Jul '14

Hello All! As fas as we know Hubert quit Fedora for a very long time (said in his private email). So it's time to change a poit of contact for the only package Hubert maintained - RabbitMQ server. https://admin.fedoraproject.org/pkgdb/package/rabbitmq-server/ I propose myself (FAS name: peter) and John Eckersberg (FAS name: jeckersb) as a primary maintainers. If anyone has any objections and/or suggestions, please, let us know. -- With best regards, Peter Lemenkov.

3 4

Re: [ACTION REQUIRED] Retiring packages for Fedora 21 v3
by Yaakov Selkowitz 02 Jul '14

02 Jul '14

On 2014-06-24 15:12, Till Maas wrote: > The following packages are orphaned or did not build for two > releases and will be retired when Fedora (F21) is branched, unless someone > adopts them. More patches: > alliance chitlesh, tnorth https://bugzilla.redhat.com/show_bug.cgi?id=1105945 > fuse-smb szpak https://bugzilla.redhat.com/show_bug.cgi?id=1106309 Yaakov Selkowitz

3 3

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 2014