devel October 2015

devel@lists.stg.fedoraproject.org

207 participants
307 discussions

C++11 enabling in F22?
by Marek Skalický 11 Nov '15

11 Nov '15

Hello everyone, I would like to ask what do you think about enabling c++11 in library in F22? Is it permitted by Fedora guidelines? I am asking because of this bug - https://bugzilla.redhat.com/show_bug.cgi?id=1274307 . And I want to know the opinion of someone else, to decide. Thank you, Marek

6 11

Fedora 23 Final RC10 status is GO !
by Jan Kurik 09 Nov '15

09 Nov '15

At the third round of Fedora 23 Final Go/No-Go Meeting, that just ends, has been Fedora 23 Final-RC10 declared as GOLD. GA of this release is planed on Tuesday 2015-Nov-03. Meeting details can be seen here: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2015-10-30/f23-final-go_n… <http://meetbot.fedoraproject.org/fedora-meeting-2/2015-10-29/f23-final-go_n…>Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2015-10-30/f23-final-go_n… <http://meetbot.fedoraproject.org/fedora-meeting-2/2015-10-29/f23-final-go_n…> Thanks everyone who participated on this release! Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

20 41

Re: daveisfera's odb_2.3_cern copr build of odb for epel-5-i386 finished with 'failed'
by Dave Johansen 09 Nov '15

09 Nov '15

The links in the above email don't work. For example, the "Build log" link says "Content Encoding Error" when I load it in Firefox: https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… This is the link that is listed if I start at the main page and drill down to find the same file and it works: https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… Is this a known issue? Or should I open a bugzilla/ticket somewhere? Thanks, Dave On Sat, Oct 17, 2015 at 3:58 PM, <notifications(a)fedoraproject.org> wrote: > Package: odb > COPR: daveisfera/odb_2.3_cern > Built by: daveisfera > Status: failed > ID: 00128590 > > Logs: > Build: > https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… > Root: > https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… > Copr: > https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… > Mockchain: > https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… > Results: > https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… > Repodata: > https://copr-be.cloud.fedoraproject.org/results/daveisfera/odb_2.3_cern/epe… > > > https://copr.fedoraproject.org/coprs/daveisfera/odb_2.3_cern/build/128590/ > > -- > You received this message due to your preference settings at > > https://apps.fedoraproject.org/notifications/daveisfera.id.fedoraproject.or… >

2 2

Oprhaned EPEL7 branch of Quassel
by Adam Miller 07 Nov '15

07 Nov '15

Hello all, I have orphaned the EPEL7 branch of Quassel as I have stopped using it long ago and no longer have the spare time to give it the amount of attention it deserves. It's a package with many co-maintainers so I doubt it will be orphaned for long. https://admin.fedoraproject.org/pkgdb/package/quassel/ Thank you, -AdamM

2 1

Looking for someone to take over Asterisk and related packages
by Jeffrey Ollie 04 Nov '15

04 Nov '15

So, after almost 10 years, it's time to find someone else to take over the Asterisk packages. If you're interested, reply to the list. I'd prefer if someone with proven packaging skills would step up - Asterisk has several security-related releases a year in addition to several bug-fix releases so this isn't the package to get started with. -- Jeff Ollie

2 2

Fedora IPv6 testing and improvements - request for ideas
by Pavel Simerda 04 Nov '15

04 Nov '15

Hi all, I am writing to Fedora development mailing lists to get opinions and ideas regarding our project on improving IPv6 support in Fedora across its components. https://fedoraproject.org/wiki/QA/Networking Most prominent subpages: * https://fedoraproject.org/wiki/QA/Networking/Test_environment * https://fedoraproject.org/wiki/QA/Networking/Client_software * https://fedoraproject.org/wiki/QA/Networking/Server_software During the first phase we are interested in getting feedback on testing methods and test cases. Any other ideas are of course welcome. Even contacts for future collaboration would be great. Cheers, Pavel

11 20

[HEADS UP] Upcoming soname change for libtirpc
by Steve Dickson 03 Nov '15

03 Nov '15

Hello, Well place sources tell me in the upcoming libtirpc release the soname will be changing due to some API changes. The API changes will make the Linux version more compatible with litbirpc implementations Obviously this change will just go in rawhide but how do I 1) request the build rpm go be added to the build root? 2) find and rebuild all the dependencies? 3) anything else I need to do? tia, steved.

6 18

Self Introduction: Randy Barlow
by Randy Barlow 02 Nov '15

02 Nov '15

Hello! I would like to become a Fedora package maintainer. I've long been a proponent of Free Software, and have been a Fedora user for about three years now (Gentoo before that, and Red Hat before that). I work at Red Hat as a contributor to the Pulp project: http://pulp.readthedocs.org/ I've been contributing to Fedora by running alphas, betas, and rawhide and trying to file quality bug reports with Fedora and upstream projects so that bugs can get fixed before they get released to the stable Fedoras. I've enjoyed this work, and want to get more involved so I decided to pursue becoming a package maintainer. I've filed a request to add a new package called ari-backup: https://bugzilla.redhat.com/show_bug.cgi?id=1269609 ari-backup is a simple wrapper around rdiff-backup that allows admins to describe their backup jobs in simple Python files. It adds the ability to manage LVM or ZFS snapshots so that the backups can be crash consistent. I am one of the contributors to ari-backup. Let me know if there is anything I can or should do to aide in the review process. I look forward to participating even more in Fedora!

3 4

Ownership of /usr/lib/rpm/fileattrs
by Orion Poplawski 02 Nov '15

02 Nov '15

Various packages now install files into /usr/lib/rpm/fileattrs for use when building rpms. Currently that directory is owned by: rpm-build-4.13.0-0.rc1.4.fc23.x86_64 javapackages-tools-4.6.0-6.fc23.noarch Of the various packages on my machine that install files there: gstreamer1-1.6.0-2.fc23.x86_64 javapackages-tools-4.6.0-6.fc23.noarch kde-settings-23-7.fc23.noarch nodejs-0.10.36-4.fc23.x86_64 perl-generators-1.06-1.fc23.noarch python3-cups-1.9.72-2.fc23.x86_64 redhat-rpm-config-36-1.fc23.noarch rpm-build-4.13.0-0.rc1.4.fc23.x86_64 rpm-mpi-hooks-3-2.fc23.noarch only rpm-mpi-hooks requires rpm-build for directory ownership, while javapackages-tools takes the route of owning the directory. However, I'd rather rpm-mpi-hooks not require rpm-build as it's not really necessary other than for this directory. The simple thing I think would be for rpm to own the directory. Does that seem reasonable? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

7 11

To distro-sync or not distro-sync?
by Miroslav Suchý 02 Nov '15

02 Nov '15

I am trying to upgrade to F23 (I know still not finished but...) In past I always done 'distro-sync'. Albeit with yum. Now I tried: dnf system-upgrade download --releasever=23 --distro-sync dnf system-upgrade download --releasever=23 --distro-sync --best dnf system-upgrade download --releasever=23 --distro-sync --best --allowerasing And all of them fail. See below for full log. On the other hand: dnf system-upgrade download --releasever=23 succeed. Actually most of the problem are caused by retired or obsoleted packages. E.g fedup-dracut or rubygem-celluloid (this one reported as BZ 1275030). My question is should we use --distro-sync at all? Are users supposed to remove obsoleted packages manually? If I do not pass --distro-sync then some packages are not upgraded. E.g in my case after upgrade I have grub2-tools-2.02-0.16.fc22.x86_64. Full log of failures. # dnf system-upgrade download --releasever=23 --distro-sync --best cannot install both kernel-devel-4.2.3-300.fc23.x86_64 and kernel-devel-3.19.4-200.fc21.x86_64. package rubygem-celluloid-0.15.2-2.fc22.noarch requires rubygem(timers) < 1.2, but none of the providers can be installed. package rubygem-celluloid-0.15.2-2.fc22.noarch requires rubygem(timers) < 1.2, but none of the providers can be installed. package fedup-dracut-0.9.2-1.fc22.x86_64 requires librpm.so.3()(64bit), but none of the providers can be installed. package rpm-libs-4.12.0.1-12.fc22.x86_64 requires rpm = 4.12.0.1-12.fc22, but none of the providers can be installed (try to add '--allowerasing' to command line to replace conflicting packages) # dnf system-upgrade download --releasever=23 --distro-sync Error: package rubygem-celluloid-0.15.2-2.fc22.noarch requires rubygem(timers) < 1.2, but none of the providers can be installed. package grub2-tools-1:2.02-0.23.fc23.x86_64 requires librpm.so.7()(64bit), but none of the providers can be installed (try to add '--allowerasing' to command line to replace conflicting packages) # dnf system-upgrade download --releasever=23 --distro-sync --best --allowerasing Error: package rubygem-celluloid-0.15.2-2.fc22.noarch requires rubygem(timers) < 1.2, but none of the providers can be installed. package fedup-dracut-0.9.2-1.fc22.x86_64 requires librpm.so.3()(64bit), but none of the providers can be installed -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

14 27

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 October 2015