Re: EPEL -ANNOUNCE Puppet 2.7 upgrade in 6
- Original Message - From: Jan-Frode Myklebust janfr...@tanso.net To: Sam Kottler skott...@redhat.com Cc: epel-devel-l...@redhat.com Sent: Tuesday, December 3, 2013 4:45:45 PM Subject: Re: EPEL -ANNOUNCE Puppet 2.7 upgrade in 6 On Sat, Nov 30, 2013 at 11:53:46AM -0500, Sam Kottler wrote: Hi! Puppet 2.7 is waiting to get pushed to stable and I just wanted to give people a heads up about the upgrade procedure. Please ensure that your master(s) get upgraded before your agents. I'd recommend following this [1] guide. This upgrade is critical because 2.6 is no longer supported and doesn't receive security releases, leaving both masters and agents potentially susceptible to attack. Thanks for the heads up. Let me know if you've got any issues or questions. Will you do a 2.7 for EPEL5 as well? That's the plan. I pushed EPEL6 first since I figured more people would be running masters on the newer distro and masters need to be on newer versions than agents. I'm hoping to get the EPEL5 upgrade into testing by the end of the week. -jf ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL dropbear update
Hi all, dropbear in EPEL6 will be updated to 2013.62 later in updates-testing with support of ECC. Full changelog is there: https://matt.ucc.asn.au/dropbear/CHANGES If you have any questions or objections, please reply here. Thanks. -- Yours sincerely, Christopher Meng Fєdоґa ї₴ al$о a кїпd оf нaт lїкє Яёd Haт. http://cicku.me ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Fedora 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 592 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 106 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11276/ssmtp-2.61-21.el5 82 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11560/fail2ban-0.8.10-4.el5 46 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5 21 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12091/bip-0.8.9-1.el5 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12157/varnish-2.0.6-4.el5 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12159/389-ds-base-1.2.11.25-1.el5 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12169/gc-7.1-6.el5 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12174/drupal7-7.24-1.el5 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12221/drupal6-6.29-1.el5 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12302/zabbix20-2.0.9-2.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing pythia8-8.1.80-1.el5 root-5.34.13-1.el5 xrootd-3.3.5-1.el5 zabbix20-2.0.9-2.el5 Details about builds: pythia8-8.1.80-1.el5 (FEDORA-EPEL-2013-12294) Pythia Event Generator for High Energy Physics Update Information: * root 5.34.13 ** See http://root.cern.ch/drupal/content/root-version-v5-34-00-patch-release-notes for a list of changes * xrootd 3.3.5 ** See https://github.com/xrootd/xrootd/blob/v3.3.5/docs/ReleaseNotes.txt for a list of changes * pythia8 8.1.80 ** See http://home.thep.lu.se/~torbjorn/pythia81html/UpdateHistory.html (scroll to the bottom) for a list of changes ChangeLog: * Wed Oct 30 2013 Mattias Ellert mattias.ell...@fysast.uu.se - 8.1.80-1 - Update to version 8.1.80 - Use full version in soname * Sun Aug 4 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 8.1.76-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild root-5.34.13-1.el5 (FEDORA-EPEL-2013-12294) Numerical data analysis framework Update Information: * root 5.34.13 ** See http://root.cern.ch/drupal/content/root-version-v5-34-00-patch-release-notes for a list of changes * xrootd 3.3.5 ** See https://github.com/xrootd/xrootd/blob/v3.3.5/docs/ReleaseNotes.txt for a list of changes * pythia8 8.1.80 ** See http://home.thep.lu.se/~torbjorn/pythia81html/UpdateHistory.html (scroll to the bottom) for a list of changes ChangeLog: * Tue Dec 3 2013 Mattias Ellert mattias.ell...@fysast.uu.se - 5.34.13-1 - Update to 5.34.13 - Remove java-devel build dependency (not needed with Fedora's libhdfs) - Adapt to pythia8 = 8.1.80 * Mon Nov 25 2013 Orion Poplawski or...@cora.nwra.com - 5.34.10-3 - Fix hadoop lib location * Mon Nov 18 2013 Dave Airlie airl...@redhat.com - 5.34.10-2 - rebuilt for GLEW 1.10 xrootd-3.3.5-1.el5 (FEDORA-EPEL-2013-12294) Extended ROOT file server Update Information: * root 5.34.13 ** See http://root.cern.ch/drupal/content/root-version-v5-34-00-patch-release-notes for a list of changes * xrootd 3.3.5 ** See https://github.com/xrootd/xrootd/blob/v3.3.5/docs/ReleaseNotes.txt for a list of changes * pythia8 8.1.80 ** See http://home.thep.lu.se/~torbjorn/pythia81html/UpdateHistory.html (scroll to the bottom) for a list of changes ChangeLog: * Tue Dec 3 2013 Mattias Ellert mattias.ell...@fysast.uu.se - 1:3.3.5-1 - Update to version 3.3.5 zabbix20-2.0.9-2.el5 (FEDORA-EPEL-2013-12302) Open-source monitoring solution for your IT infrastructure Update Information: This update solves the vulnerability described in CVE-2013-6824: Zabbix agent is vulnerable to remote command execution from the Zabbix server in some cases https://support.zabbix.com/browse/ZBX-7479
EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 592 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 106 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6 48 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11865/quassel-0.9.1-1.el6 21 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12079/bip-0.8.9-1.el6 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12156/varnish-2.1.5-5.el6 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12154/mediawiki119-1.19.9-1.el6 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12171/drupal7-7.24-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-1/drupal6-6.29-1.el6 4 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12238/seamonkey-2.21-2.esr1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12290/zabbix20-2.0.9-2.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12301/zabbix-1.8.18-2.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12299/lynis-1.3.6-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing dropbear-2013.62-1.el6 eventlog-0.2.13-1.el6 golang-1.2-1.el6 heat-cfntools-1.2.6-2.el6 lynis-1.3.6-1.el6 mod_form-0.1-1.20131204svn145.el6 perl-Net-GitHub-0.54-1.el6 pythia8-8.1.80-1.el6 python-chai-0.4.6-1.el6 python-cmdln-1.3.0-1.el6 root-5.34.13-1.el6 xrootd-3.3.5-1.el6 zabbix-1.8.18-2.el6 zabbix20-2.0.9-2.el6 Details about builds: dropbear-2013.62-1.el6 (FEDORA-EPEL-2013-12289) SSH2 server and client Update Information: 2013.62 - Tuesday 3 December 2013 - Disable interactive QoS connection options when a connection doesn't have a PTY (eg scp, rsync). Thanks to Catalin Patulea for the patch. - Log when a hostkey is generated with -R, fix some bugs in handling server hostkey commandline options - Fix crash in Dropbearconvert and 521 bit key, reported by NiLuJe - Update config.guess and config.sub again 2013.61test - Thursday 14 November 2013 - ECC (elliptic curve) support. Supports ECDSA hostkeys (requires new keys to be generated) and ECDH for setting up encryption keys (no intervention required). This is significantly faster. - curve25519-sha...@libssh.org support for setting up encryption keys. This is another elliptic curve mode with less potential of NSA interference in algorithm parameters. curve25519-donna code thanks to Adam Langley - -R option to automatically generate hostkeys. This is recommended for embedded platforms since it allows the system random number device /dev/urandom a longer startup time to generate a secure seed before the hostkey is required. - Compile fixes for old vendor compilers like Tru64 from Daniel Richard G. - Make authorized_keys handling more robust, don't exit encountering malformed lines. Thanks to Lorin Hochstein and Mark Stillwell 2013.60 - Wednesday 16 October 2013 - Fix make install so that it doesn't always install to /bin and /sbin - Fix make install MULTI=1, installing manpages failed - Fix make install when scp is included since it has no manpage - Make --disable-bundled-libtom work ChangeLog: * Wed Dec 4 2013 Christopher Meng r...@cicku.me - 2013.62-1 - Update to 2013.62 References: [ 1 ] Bug #1020251 - dropbear-2013.60 is available https://bugzilla.redhat.com/show_bug.cgi?id=1020251 eventlog-0.2.13-1.el6 (FEDORA-EPEL-2013-12298) Syslog-ng v2/v3 support library Update Information: Update to version 0.2.13 ChangeLog: * Wed Dec 4 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 0.2.13-1 - update to version 0.2.13 - updated the Source and URL fields golang-1.2-1.el6 (FEDORA-EPEL-2013-12293) The Go Programming Language Update Information: update to upstream go1.2 fix rpmspec conditional split out the golang-godoc Go programming language from Google, now available in EPEL. The Go Programming Language from Google, now available for EPEL.
Re: EPEL Updating ODB in ?
On Tue, Dec 3, 2013 at 12:06 AM, Dan Horák d...@danny.cz wrote: On Mon, 2 Dec 2013 21:42:10 -0700 Dave Johansen davejohan...@gmail.com wrote: On Mon, Dec 2, 2013 at 8:19 AM, Kevin Fenzi ke...@scrye.com wrote: On Mon, 2 Dec 2013 09:45:44 +0400 Peter Lemenkov lemen...@gmail.com wrote: Hello All! 2013/12/2 Dave Johansen davejohan...@gmail.com: I recently submitted ODB 2.2 to the EPEL for EL 5/6 and version 2.3 has been released ( http://codesynthesis.com/pipermail/odb-announcements/2013/37.html ). The wiki seems to indicate that updating software for feature releases is discouraged ( https://fedoraproject.org/wiki/EPEL_Updates_Policy#Stable_Releases ), so is updating ODB to 2.3 in the EPEL not really possible? Assuming that's the case, is there a recommended solution for maintaining access to newer versions of ODB for EL users? ODB is still a young package (in terms of existing in EL repositories) so I would update it anyway. However in the future ypu'd better to provide parallel-installable odb30, odb40 etc packages. The questions to ask are: Does the upgrade require intervention? ie, if someone did the upgrade would they have to manually change config files, or migrate databases or whatever? No, the 2.3 version just adds some features and there wouldn't be any needed changes to config files or databases to support the update. Next, is the package a gui one that changes look and feel? ie, would some user who updated suddenly have to relearn where the various options are? There's no GUI or user facing part of it, so it would be effect developers but not users. Finally, does it change abi/api any? If it was updated would people have to rebuild other things to work with it? There were additions to the API to support the new features and I'm guessing that there may be ABI changes as well. Basically, I'm guessing that a rebuild would be necessary. you can easily check the possible API/ABI difference with the abi-compliance-checker tool I put in a request to have it added to upstream-tracker.org and it looks like 2.3 does have ABI breakage issues: http://upstream-tracker.org/versions/libodb.html ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: Duplicate documentation files / potentially conflicting
On Wed, 2013-12-04 at 08:39 +0100, Michael Schwendt wrote: End of August I've opened tickets about duplicate and potentially conflicting (because if noarch - arch differences) %doc files. The response from packagers has not been brilliant so far. These are _package bugs_ specific to Fedora, so it's the responsibility of a Fedora Packager to fix them. It's a mistake in the spec file, not in the packaged software. Potentially conflicting may mean that several subpackages could not be installed at once and would cause a transaction error. Rather than spamming bugzilla with lots of NEEDINFO calls, hereby I'd like to raise awareness of the issue. I don't understand why packagers don't respond in bugzilla. Fedora 20 is near. If you mentioned a list of bugs or at least a shared string from the descriptions of all of them, maybe provenpackagers could take some time to help out. (Well, I guess we could go digging in your bugzilla history, but it seems like more trouble than is necessary.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: pl license change
On 2013-12-04, Kevin Kofler kevin.kof...@chello.at wrote: Petr Pisar wrote: [snip] and GPLv2 and GPLv3+. Huh? WTF is upstream smoking there? Upstream releases a tar ball bundling a lot of subprojects. Thus the complicated license. I do a licence review each new release and I always find new licenses. This time I had to drop two files because of non-commercial requirement. -- Petr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] 2013-12-04 @ 17:00 UTC - F20 Final Blocker Bug Review #4
# F20 Final Blocker Review meeting #4 # Date: 2013-12-04 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-blocker-review on irc.freenode.net Well folks, we still have proposed blockers on the list, so you know what that means: time for some more blocker review in just eight short hours! Please come out and help us review the new crop. We'll be reviewing the bugs to ensure they meet the Final release criteria [1] as blocking final release and that the bugs are getting the attention they need. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you soon! [1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate documentation files / potentially conflicting
On Wed, 04 Dec 2013 00:07:22 -0800, Adam Williamson wrote: If you mentioned a list of bugs or at least a shared string from the descriptions of all of them, maybe provenpackagers could take some time to help out. (Well, I guess we could go digging in your bugzilla history, but it seems like more trouble than is necessary.) They can be found when searching bugzilla for the subject line, and they are also on the list of the F20UnversionedDocDirs tracker ( https://bugzilla.redhat.com/993551 ). Once a provenpackager touches the packages, typically the owner will wake up and either complain or start asking questions. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: crypto consolidation status
I'd suggest to follow the Medium term goals from the page. That means to choose the backend from one of the following libraries (in the order of preference). 1. NSS 2. GNUTLS (with nettle as crypto backend, but nettle never used directly by applications) 3. OpenSSL 4. libgcrypt That's what I wanted to know. Thank you very much. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate documentation files / potentially conflicting
On Wed, 2013-12-04 at 09:54 +0100, Michael Schwendt wrote: On Wed, 04 Dec 2013 00:07:22 -0800, Adam Williamson wrote: If you mentioned a list of bugs or at least a shared string from the descriptions of all of them, maybe provenpackagers could take some time to help out. (Well, I guess we could go digging in your bugzilla history, but it seems like more trouble than is necessary.) They can be found when searching bugzilla for the subject line, and they are also on the list of the F20UnversionedDocDirs tracker ( https://bugzilla.redhat.com/993551 ). Once a provenpackager touches the packages, typically the owner will wake up and either complain or start asking questions. sounds like a win to me ;) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Meeting minutes - today's Env-and-Stacks WG meeting (2013-12-03)
#fedora-meeting: Env and Stacks (2013-12-03) Meeting started by mmaslano at 16:02:38 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-03/env_and_stacks.2013-12-03-16.02.log.html . Meeting summary --- * ACTION: handsome_pirate will do wiki pages (mmaslano, 16:09:53) * init process (mmaslano, 16:10:04) * In scope ecamples: Automated Review tools (abadger1999, 16:37:25) * In scope example: DevAssistant (abadger1999, 16:37:39) * In scope example: work on enhancing build systems (copr koji) (abadger1999, 16:38:07) * In scope example: Taskotron - Automated task system (abadger1999, 16:43:20) * In scope example: scale manpower of infra/qa/releng to add features to tools and deploy new tools (abadger1999, 16:43:58) * ACTION: people to work on outlining the sections of https://fedoraproject.org/wiki/User:Toshio/Env_and_Stacks_Charter_Brainstorming (abadger1999, 17:14:09) Meeting ended at 17:22:40 UTC. Action Items * handsome_pirate will do wiki pages * people to work on outlining the sections of https://fedoraproject.org/wiki/User:Toshio/Env_and_Stacks_Charter_Brainstorming Action Items, by person --- * handsome_pirate * handsome_pirate will do wiki pages * **UNASSIGNED** * people to work on outlining the sections of https://fedoraproject.org/wiki/User:Toshio/Env_and_Stacks_Charter_Brainstorming People Present (lines said) --- * abadger1999 (69) * tjanez (42) * mmaslano (29) * drieden (21) * handsome_pirate (14) * pkovar (13) * hhorak (7) * zodbot (5) * tflink (3) * samkottler (3) * vpavlin (2) * bkabrda (0) * juhp (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot 16:02:38 mmaslano #startmeeting Env and Stacks (2013-12-03) 16:02:38 zodbot Meeting started Tue Dec 3 16:02:38 2013 UTC. The chair is mmaslano. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:38 zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:49 mmaslano #meetingname Env and Stacks 16:02:50 zodbot The meeting name has been set to 'env_and_stacks' 16:03:00 handsome_pirate Ahoy 16:03:14 mmaslano #chair abadger1999 pkovar tjanez samkottler bkabrda handsome_pirate hhorak juhp 16:03:14 zodbot Current chairs: abadger1999 bkabrda handsome_pirate hhorak juhp mmaslano pkovar samkottler tjanez 16:03:14 * samkottler is here 16:03:23 mmaslano handsome_pirate: hi, I was looking for you. What about wiki pages? 16:03:29 handsome_pirate Sorry for the last couple of weeks; I've had a lot of personal stuff going on that's killed my free time 16:03:34 tjanez hello 16:03:34 hhorak Hi all! 16:03:37 handsome_pirate mmaslano: ^^ 16:03:47 handsome_pirate mmaslano: I just haven't had time to do them 16:05:05 mmaslano handsome_pirate: okay 16:05:42 handsome_pirate mmaslano: However, that should be cleared up, so I'll have some time again 16:06:01 drieden Hello 16:08:50 * pkovar is late 16:09:28 mmaslano abadger1999: ? 16:09:31 mmaslano are you here? 16:09:42 * abadger1999 here 16:09:53 mmaslano #action handsome_pirate will do wiki pages 16:10:04 mmaslano #topic init process 16:10:18 mmaslano does anyone have a new topic for discussion? 16:10:23 mmaslano new goal 16:10:55 drieden I have a question about the PRD, is there an outline for it? 16:11:36 mmaslano it shouldn't be real PRD, because we won't do a product 16:11:37 abadger1999 drieden: I do not believe so... we don't really have a PRD as we're not producing a single product like the workstation/server/cloud groups. 16:12:21 abadger1999 drieden: We may be able to look at what Base is doing for ideas though they don't have precisely the same issues but their issues are somewhat similar. 16:12:22 drieden abadger1999 okay, but is there a table of contents so we have some idea of the sections which will be in it? 16:13:02 abadger1999 drieden: Nope. We have a hard job as we're different than everyone else. 16:13:10 abadger1999 so we have to come up with all of this from scratch. 16:13:52 drieden Perhaps we can use a template and take out the things which don't pertain to us. 16:13:53 tflink I have some questions about tooling plans but they can wait for open floor 16:14:17 drieden I didn't know if there was a PRD template provided that all groups would be using. 16:15:10 mmaslano no template 16:15:43 abadger1999 drieden: groups are cribbing off of each other... but like I said, since we're not producing a produt.. a lot of what other groups are coming up with doesn't really match up with what we need to write up to clearly define our role. 16:15:49 drieden mmaslano Ok. Do we want to propose a TOC and then we can focus on each section? 16:16:17 drieden abadger1999 I realize that, but if we don't have at least a TOC, then it's hard to focus on what
F-20 Branched report: 20131204 changes
Compose started at Wed Dec 4 07:15:03 UTC 2013 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server = 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [ghc-hjsmin] ghc-hjsmin-devel-0.1.4.3-2.fc20.armv7hl requires ghc-devel(language-javascript-0.5.8-28fa88554adf134b03284de53334e91d) [gnome-do-plugins] gnome-do-plugins-thunderbird-0.8.4-14.fc20.armv7hl requires thunderbird [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) = 0:0.16.0 [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [mozilla-firetray] mozilla-firetray-thunderbird-0.3.6-0.5.143svn.fc18.1.armv7hl requires thunderbird = 0:11 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc = 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [pure] pure-doc-0.57-4.fc20.noarch requires pure = 0:0.57-4.fc20 [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.53.0 [rootplot] rootplot-2.2.1-7.fc19.noarch requires root-python [rubygem-audited-activerecord] rubygem-audited-activerecord-3.0.0-3.fc19.noarch requires rubygem(activerecord) 0:4 [scilab] scilab-doc-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 scilab-tests-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 [spacewalk-admin] spacewalk-admin-2.0.1-2.fc20.noarch requires spacewalk-base spacewalk-admin-2.0.1-2.fc20.noarch requires perl(RHN::SatelliteCert) [spring-maps-default] spring-maps-default-0.1-11.fc20.noarch requires spring [springlobby] springlobby-0.169-5.fc20.armv7hl requires spring [subsurface] subsurface-3.1.1-2.fc20.armv7hl requires libosmgpsmap.so.2 [syntastic] syntastic-d-2.3.0-11.20120917git72856e6.fc20.noarch requires ldc [tango] tango-doc-2-12.20120821git7b92443.fc19.noarch requires tango-devel = 0:2-12.20120821git7b92443.fc19 tango-geany-tags-2-12.20120821git7b92443.fc19.noarch requires tango = 0:2-12.20120821git7b92443.fc19 Broken deps for i386 -- [blueman] blueman-1.23-7.fc20.i686 requires obex-data-server = 0:0.4.3 blueman-1.23-7.fc20.i686 requires gvfs-obexftp [derelict] derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod [fts] fts-server-3.1.1-1.fc20.i686 requires libactivemq-cpp.so.14 [ghc-hjsmin] ghc-hjsmin-0.1.4.3-2.fc20.i686 requires
[Bug 1037241] perl-GD FTBFS if -Werror=format-security flag is used
https://bugzilla.redhat.com/show_bug.cgi?id=1037241 Dhiru Kholia dkho...@redhat.com changed: What|Removed |Added Blocks||1038083 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1038083 [Bug 1038083] tracker bug for -Werror=format-security change -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Ku98jFkewpa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: rawhide report: 20131204 changes
On Wed, Dec 04, 2013 at 12:02:53PM +, Fedora Rawhide Report wrote: [libguestfs] 1:libguestfs-1.25.12-1.fc21.i686 requires libprocps.so.1 [open-vm-tools] open-vm-tools-9.4.0-1.fc21.i686 requires libprocps.so.1(LIBPROCPS_0) open-vm-tools-9.4.0-1.fc21.i686 requires libprocps.so.1 Both being rebuilt now. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate documentation files / potentially conflicting
On Wed, Dec 04, 2013 at 08:39:21AM +0100, Michael Schwendt wrote: End of August I've opened tickets about duplicate and potentially conflicting (because if noarch - arch differences) %doc files. The response from packagers has not been brilliant so far. These are _package bugs_ specific to Fedora, so it's the responsibility of a Fedora Packager to fix them. It's a mistake in the spec file, not in the packaged software. Potentially conflicting may mean that several subpackages could not be installed at once and would cause a transaction error. Rather than spamming bugzilla with lots of NEEDINFO calls, hereby I'd like to raise awareness of the issue. I don't understand why packagers don't respond in bugzilla. Fedora 20 is near. I've read this several times, and https://fedoraproject.org/wiki/Changes/UnversionedDocdirs and I still don't understand what this message means. How would this cause subpackage conflicts? What has arch/noarch got to do with anything? Can you point to an example of a packaging problem? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File Fennec-2.011.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Fennec: 5c2ea67ed482dfa6f4c536eb720538e7 Fennec-2.011.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Fedora 20 TC4 AMIs
Matthew Miller mat...@fedoraproject.org writes: On Tue, Dec 03, 2013 at 04:42:44PM +0100, Vitaly Kuznetsov wrote: The only issue compared to TC3 is one more file with wrong selinux context (/var/log/cron). So, for TC4: # restorecon -R -v -n -e /proc -e /sys -e /dev -e/run -e/tmp / restorecon reset /var/log/cron context system_u:object_r:var_log_t:s0-system_u:object_r:cron_log_t:s0 restorecon reset /var/log/boot.log context system_u:object_r:var_log_t:s0-system_u:object_r:plymouthd_var_log_t:s0 These files don't exist initially -- I expect that just creating them before the fixfiles is run in the kickstart should do it. restorecon reset /var/cache/yum context system_u:object_r:file_t:s0-system_u:object_r:rpm_var_cache_t:s0 This _does_ exist, though, so it's more of a puzzle. Any guesses? restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0-system_u:object_r:boot_t:s0 And this is because it's immutable. not sure if it deserves BZ and against what if it does. Last time I created https://bugzilla.redhat.com/show_bug.cgi?id=1033274 against anaconda but it seems misplaced. Since we're building with appliance-creator, anaconda isn't involved. That will change in the future In the meantime, we have to hack around it with kickstart kludges. Can you test http://mattdm.fedorapeople.org/tmp/Fedora20-sda.qcow2 to see if it's any better? It definitely is: restorecon -R -v -n -e /proc -e /sys -e /dev -e/run -e/tmp / restorecon reset /mnt context unconfined_u:object_r:default_t:s0-unconfined_u:object_r:mnt_t:s0 restorecon reset /var/cache/yum context unconfined_u:object_r:file_t:s0-unconfined_u:object_r:rpm_var_cache_t:s0 But that's kvm. Unless cloud-init does some nasty magick in EC2 we're ok) BTW, our cloud-init is slighly outdated (0.7.4 is out for couple of weeks). -- Vitaly Kuznetsov -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-Locale-Codes] Filter private module Locale::Codes::LangFam_Retired from dependencies
commit 667e7ee070e27bc7007b564e953249b085bd50a8
Author: Petr Písař ppi...@redhat.com
Date: Wed Dec 4 13:58:50 2013 +0100
Filter private module Locale::Codes::LangFam_Retired from dependencies
perl-Locale-Codes.spec |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/perl-Locale-Codes.spec b/perl-Locale-Codes.spec
index 46df19d..012608d 100644
--- a/perl-Locale-Codes.spec
+++ b/perl-Locale-Codes.spec
@@ -1,6 +1,6 @@
Name: perl-Locale-Codes
Version:3.28
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Distribution of modules to handle locale codes
License:GPL+ or Artistic
Group: Development/Libraries
@@ -28,7 +28,7 @@ Provides: perl(Locale::Codes) = %{version}
# Filter dependencies on private modules. Generator:
# for F in $(find lib -type f); do perl -e '$/ = undef; $_ = ; if (/^package
#\R([\w:]*);/m) { print qq{|^perl($1)} }' $F; done
-%global __requires_exclude
%{?__requires_exclude:%__requires_exclude|}^perl\\(Locale::Codes::Country_Retired\\)|^perl\\(Locale::Codes::Script_Retired\\)|^perl\\(Locale::Codes::LangExt_Codes\\)|^perl\\(Locale::Codes::LangFam_Codes\\)|^perl\\(Locale::Codes::Script_Codes\\)|^perl\\(Locale::Codes::Language_Codes\\)|^perl\\(Locale::Codes::LangExt_Retired\\)|^perl\\(Locale::Codes::Currency_Codes\\)|^perl\\(Locale::Codes::LangVar_Retired\\)|^perl\\(Locale::Codes::Language_Retired\\)|^perl\\(Locale::Codes::Country_Codes\\)|^perl\\(Locale::Codes::LangVar_Codes\\)|^perl\\(Locale::Codes::Currency_Retired\\)
+%global __requires_exclude
%{?__requires_exclude:%__requires_exclude|}^perl\\(Locale::Codes::Country_Retired\\)|^perl\\(Locale::Codes::LangFam_Retired\\)|^perl\\(Locale::Codes::Script_Retired\\)|^perl\\(Locale::Codes::LangExt_Codes\\)|^perl\\(Locale::Codes::LangFam_Codes\\)|^perl\\(Locale::Codes::Script_Codes\\)|^perl\\(Locale::Codes::Language_Codes\\)|^perl\\(Locale::Codes::LangExt_Retired\\)|^perl\\(Locale::Codes::Currency_Codes\\)|^perl\\(Locale::Codes::LangVar_Retired\\)|^perl\\(Locale::Codes::Language_Retired\\)|^perl\\(Locale::Codes::Country_Codes\\)|^perl\\(Locale::Codes::LangVar_Codes\\)|^perl\\(Locale::Codes::Currency_Retired\\)
%description
Locale-Codes is a distribution containing a set of modules. The modules
@@ -57,6 +57,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Wed Dec 04 2013 Petr Pisar ppi...@redhat.com - 3.28-2
+- Filter private module Locale::Codes::LangFam_Retired from dependencies
+
* Tue Dec 03 2013 Petr Pisar ppi...@redhat.com - 3.28-1
- 3.28 bump
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: crypto consolidation status
On Út, 2013-12-03 at 22:28 +0100, Florian Weimer wrote: On 12/03/2013 07:58 PM, Tomas Mraz wrote: I'd suggest to follow the Medium term goals from the page. That means to choose the backend from one of the following libraries (in the order of preference). 1. NSS 2. GNUTLS (with nettle as crypto backend, but nettle never used directly by applications) 3. OpenSSL 4. libgcrypt I hope that both OpenJDK crypto providers are acceptable as well (one is a wrapper around NSS, the other one is a separate implementation, mostly in Java). The wrapper around NSS clearly is acceptable. On the other hand the separate implementation is not planned to be FIPS validated in Red Hat Enterprise Linux which might be a problem. -- 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 mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate documentation files / potentially conflicting
On Wed, 4 Dec 2013 12:08:08 +, Richard W.M. Jones wrote: I've read this several times, and https://fedoraproject.org/wiki/Changes/UnversionedDocdirs and I still don't understand what this message means. My message or a specific bugzilla ticket? How would this cause subpackage conflicts? Have you heard about Doxygen generated documentation causing conflicts? Here the problem is expanded into a conflict between the base package and the second package that also includes the documentation. What has arch/noarch got to do with anything? A noarch subpackage may be built on any build arch different than the builder that creates the base package. This triggers bugs (such as the Doxygen timestamp/footer bug), because the noarch build's doc files may differ from the arch build's doc files. If no noarch subpkg is involved, it [hopefully] boils down to just duplicated files. Can you point to an example of a packaging problem? Duplicate files are a packaging problem already. Duplicating the entire contents of a huge -doc subpackage in the base package is a problem. Worse if there is a conflict. The bug reports don't claim there is a conflict _always_. But we encounter Doxygen related conflicts regularly, even during review. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
how to fix this qt code for format-security flag FTBFS
Hi, I got a format-security flag FTBFS bug[1] for fontmatrix package which I maintain in Fedora. I am confused on how to fix line 86 qDebug() from http://fpaste.org/58952/13861663/ to fix this FTBFS. Can someone help to fix this? Regards, Parag. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1037066 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Schedule for Wednesday's FESCo Meeting (2013-12-04)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net. *That's today: sorry about the late message. There's no surprise new business, though.* To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '-MM-DD HH:MM UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #1193 reboots for all updates -- are we ready for this? .fesco 1193 https://fedorahosted.org/fesco/ticket/1193 #topic #1201 Enabling third party repositories .fesco 1201 https://fedorahosted.org/fesco/ticket/1201 = New business = None noted. = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: how to fix this qt code for format-security flag FTBFS
On 12/04/2013 03:26 PM, Parag N(पराग़) wrote: I got a format-security flag FTBFS bug[1] for fontmatrix package which I maintain in Fedora. I am confused on how to fix line 86 qDebug() from http://fpaste.org/58952/13861663/ to fix this FTBFS. Can someone help to fix this? This should do it: qDebug(%s, ds.arg(glyph) .arg(log) .arg(xadvance) .arg(yadvance) .arg(xoffset) .arg(yoffset) .arg(QChar(lChar)) .arg(hyphen.first.count()) .toLocal8Bit().data()); The original version relied on the operator char *() overload of QByteArray, but that isn't applied in a vararg context. -- Florian Weimer / Red Hat Product Security Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: how to fix this qt code for format-security flag FTBFS
Dne 4.12.2013 15:47, Florian Weimer napsal(a): On 12/04/2013 03:26 PM, Parag N(पराग़) wrote: I got a format-security flag FTBFS bug[1] for fontmatrix package which I maintain in Fedora. I am confused on how to fix line 86 qDebug() from http://fpaste.org/58952/13861663/ to fix this FTBFS. Can someone help to fix this? This should do it: qDebug(%s, ds.arg(glyph) .arg(log) .arg(xadvance) .arg(yadvance) .arg(xoffset) .arg(yoffset) .arg(QChar(lChar)) .arg(hyphen.first.count()) .toLocal8Bit().data()); The original version relied on the operator char *() overload of QByteArray, but that isn't applied in a vararg context. An even better and easier way is to #include QDebug and use sth like: qDebug() glyph log xadvance etc etc; -- Lukáš Tinkl lti...@redhat.com Software Engineer - KDE desktop team, Brno KDE developer lu...@kde.org Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: how to fix this qt code for format-security flag FTBFS
Hi, Thanks for replying to my query. I also got same help on #fedora-kde channel. Regards, Parag -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
a question about rpmbuild command
Hi,everyone http://www.redhat.com/archives/shrike-list/2003-April/msg00069.html http://fedoraproject.org/wiki/StackTraces http://old-en.opensuse.org/Packaging/Debuginfo This document said:passing -g to gcc or g++. And Note that the default CFLAGS and CXXFLAGS of the distro already contain -g, My question is : I build souce code a.c with myself gcc/make configfile. first time: compile a.c with -O2,then get a1.bin second time: compile a.c woth -O2 -g,then strip debug symbols.then get a2.bin But i find a2.bin is slower then a1.bin.The performance of a2.bin is 5% slower. Should a2.bin run as fast as a1.bin?(performance is same?)//Tomorrow i will provide the complete commands. Can anyone give some advice? I find that:rpmbuild run gcc one time with -g -O2,then get a.rpm and a.debuginforpm.-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora ARM Status Meeting 2013-12-04
Good day all, Please join us today (Wednesday, December 4th) at 4PM EST (9PM UTC) for the Fedora ARM status meeting in #fedora-meeting-1 on Freenode. On the agenda so far.. 1) Kernel Status Update 2) Aarch64 - Status Update - Images 3) F20 TC4 - Testing Summary 4) F21 Wish list 5) Open Floor If there is something that you would like to discuss that isn't mentioned please feel free to bring it up at the end of the meeting or send an email to the list. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora ARM Status Meeting 2013-12-04
Hi list(s),
We still doesn't have gnat compiler for %{arm} in Fedora. We (Ada community)
have compiled gcc with ada support using gcc-4.8.2 src.rpm and tested in.
It seems workable. At least we were able to compile most of the
packages from the stack with it.
I'd like to discuss way how to get it in Fedora (chicken-egg problem
should be solved).
--
Pavel
On Wed, 04 Dec 2013, Paul Whalen wrote:
| Good day all,
|
| Please join us today (Wednesday, December 4th) at 4PM EST (9PM UTC)
| for the Fedora ARM status meeting in #fedora-meeting-1 on Freenode.
|
| On the agenda so far..
|
| 1) Kernel Status Update
|
| 2) Aarch64 - Status Update
|- Images
|
| 3) F20 TC4 - Testing Summary
|
| 4) F21 Wish list
|
| 5) Open Floor
|
| If there is something that you would like to discuss that isn't mentioned
| please feel free to bring it up at the end of the meeting or send an email
| to the list.
|
| Paul
| --
| devel mailing list
| devel@lists.fedoraproject.org
| https://admin.fedoraproject.org/mailman/listinfo/devel
| Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Schedule for Thursday's FPC Meeting (2013-12-05 17:00 UTC)
Following is the list of topics that will be discussed in the FPC meeting Thursday at 2013-12-05 17:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. rktime): 2013-12-05 09:00 Thu US/Pacific PST 2013-12-05 12:00 Thu US/Eastern EST 2013-12-05 17:00 Thu UTC - 2013-12-05 17:00 Thu Europe/London - 2013-12-05 18:00 Thu Europe/Paris CET 2013-12-05 18:00 Thu Europe/Berlin CET 2013-12-05 22:30 Thu Asia/Calcutta IST --new day-- 2013-12-06 01:00 Fri Asia/Singapore SGT 2013-12-06 01:00 Fri Asia/Hong_Kong HKT 2013-12-06 02:00 Fri Asia/Tokyo JST 2013-12-06 03:00 Fri Australia/Brisbane EST Links to all tickets below can be found at: https://fedorahosted.org/fpc/report/12 = Followups = (approval and retirement sections already passed) #topic #339 software collections in Fedora .fpc 339 https://fedorahosted.org/fpc/ticket/339 #topic #358 Please make some autotools guidelines. .fpc 358 https://fedorahosted.org/fpc/ticket/358 #topic #364 exception for bundled library ccan in ocserv .fpc 364 https://fedorahosted.org/fpc/ticket/364 = New business = #topic #362 lpf should not be allowed in Fedora .fpc NNN https://fedorahosted.org/fpc/ticket/NNN #topic #367 Another bundled MD5 implementation originally by Ulrich Drepper .fpc NNN https://fedorahosted.org/fpc/ticket/367 #topic #369 Guidance on dealing with the bundled libev in perl-EV .fpc 369 https://fedorahosted.org/fpc/ticket/369 #topic #371 Packages approved without satisfied dependencies .fpc 371 https://fedorahosted.org/fpc/ticket/371 #topic #372 Temporary bundling exception for kernel event library .fpc 372 https://fedorahosted.org/fpc/ticket/372 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://fedorahosted.org/fpc/report/12 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fpc, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
FTBFS if -Werror=format-security flag is used
This is just a pain. Can someone explain to me why this is good? Original Message Subject: [Bug 1037125] hydrogen FTBFS if -Werror=format-security flag is used Date: Wed, 04 Dec 2013 11:33:47 + From: bugzi...@redhat.com To: brendan.jones...@gmail.com https://bugzilla.redhat.com/show_bug.cgi?id=1037125 Dhiru Kholia dkho...@redhat.com changed: What|Removed |Added Blocks||1038083 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1038083 [Bug 1038083] tracker bug for -Werror=format-security change -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On Wed, Dec 04, 2013 at 07:10:39PM +0100, Brendan Jones wrote: This is just a pain. Can someone explain to me why this is good? If you read the bug description you'll see the link which answers your question. https://fedoraproject.org/wiki/Format-Security-FAQ Daniel -- |: 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 :| -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/04/2013 07:29 PM, Daniel P. Berrange wrote: On Wed, Dec 04, 2013 at 07:10:39PM +0100, Brendan Jones wrote: This is just a pain. Can someone explain to me why this is good? If you read the bug description you'll see the link which answers your question. https://fedoraproject.org/wiki/Format-Security-FAQ Daniel I'm sorry, but I can't see why any of my packages (10+) are at risk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
Hi On Wed, Dec 4, 2013 at 1:45 PM, Brendan Jones wrote: I'm sorry, but I can't see why any of my packages (10+) are at risk This is just a best practice to mitigate any risks that might exist just like any of the other security improvements we make from time to time. Even if you don't see any immediate benefits, there is no harm in following the appropriate guidelines here. Coordinate with upstream Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] Please review: [389 Project] #605: support TLS 1.1 - adding backward compatibility
https://fedorahosted.org/389/ticket/605 https://fedorahosted.org/389/attachment/ticket/605/0001-Ticket-605-support-TLS-1.1-adding-backward-compatibi.patch Description: commit 88d4beccb9d9f7bb89f5e24c47828d7516ba7ca8 always expected the NSS version supporting TLS 1.2. It broke the build on the system having the NSS version that only supports TLS 1.1 (and older). This patch checks the NSS version and switches the supported TLS in ssl.c based upon the version info. -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Summary/Minutes from today's FESCo Meeting (2013-12-04)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 === #fedora-meeting: FESCO (2013-12-04) === Meeting started by sgallagh at 17:59:34 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-04/fesco.2013-12-04-17.59.log.html . Meeting summary - --- * init process (sgallagh, 17:59:45) * #1193 reboots for all updates -- are we ready for this? (sgallagh, 18:03:39) * ACTION: nirik to update the AppInstaller Change pages (sgallagh, 18:05:48) * #1201 Enabling third party repositories (sgallagh, 18:09:28) * at this time, issues around linking directly to copr repos include signing/key management, and mirrored distribution (mattdm, 18:34:46) * AGREED: At this time, copr-enablement packages cannot be shipped in the main repo. (sgallagh, 18:47:28) * Next week's chair (sgallagh, 18:51:28) * mattdm to chair next week's meeting (sgallagh, 18:52:26) * Open Floor (sgallagh, 18:52:30) * LINK: http://devconf.cz/ (sgallagh, 18:54:02) * LINK: fosdem.org (sgallagh, 18:54:16) * ACTION: mattdm to contact WG liasons about DevConf presentation (sgallagh, 19:00:44) Meeting ended at 19:02:21 UTC. Action Items - * nirik to update the AppInstaller Change pages * mattdm to contact WG liasons about DevConf presentation Action Items, by person - --- * mattdm * mattdm to contact WG liasons about DevConf presentation * nirik * nirik to update the AppInstaller Change pages * **UNASSIGNED** * (none) People Present (lines said) - --- * sgallagh (80) * abadger1999 (40) * nirik (36) * mattdm (33) * notting (21) * mmaslano (16) * pjones (14) * zodbot (8) * jzb (2) * misc (1) * pingou (1) * mitr (0) * t8m (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKffPIACgkQeiVVYja6o6PglQCdFLFXswpTfHVZMlrjUtbRNRcm w7sAnjMyMPAFlwayhf55p0bQkfaRI06U =zrqP -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora ARM Status Meeting 2013-12-04
On Wed, Dec 4, 2013 at 5:17 PM, Pavel Zhukov pzhu...@redhat.com wrote:
Hi list(s),
We still doesn't have gnat compiler for %{arm} in Fedora. We (Ada community)
have compiled gcc with ada support using gcc-4.8.2 src.rpm and tested in.
It seems workable. At least we were able to compile most of the
packages from the stack with it.
I'd like to discuss way how to get it in Fedora (chicken-egg problem
should be solved).
That's relatively straight forward. We need a documented process to
get it done. Once we have that I can sort it out with rel-eng but we
would need the gcc maintainer to review/approve it.
Generally what happens is that it would be built (or imported) into a
side tag build. I suspect it'll be using something like a cross
compiled version of ada which is then used to compile a native built
version of ada which is then tagged into rawhide at which point the
rest of the ada stack would be rebuilt.
Ultimately it should be straight forward and easy to complete once we
have the documented process.
Peter
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora ARM Status Meeting 2013-12-04
On Wednesday, December 04, 2013 07:11:40 PM Peter Robinson wrote:
On Wed, Dec 4, 2013 at 5:17 PM, Pavel Zhukov pzhu...@redhat.com wrote:
Hi list(s),
We still doesn't have gnat compiler for %{arm} in Fedora. We (Ada
community) have compiled gcc with ada support using gcc-4.8.2 src.rpm
and tested in. It seems workable. At least we were able to compile most
of the
packages from the stack with it.
I'd like to discuss way how to get it in Fedora (chicken-egg problem
should be solved).
That's relatively straight forward. We need a documented process to
get it done. Once we have that I can sort it out with rel-eng but we
would need the gcc maintainer to review/approve it.
Generally what happens is that it would be built (or imported) into a
side tag build. I suspect it'll be using something like a cross
compiled version of ada which is then used to compile a native built
version of ada which is then tagged into rawhide at which point the
rest of the ada stack would be rebuilt.
Yes. We cross-compiled bootstrap and compiled native version using it. It's
original Fedora gcc without any modifications (just added arm to the gnat
arches list) and applied short patch [1]
It was the long process [2] in qemu with all tests performed. I'm going to
recompile it once more time using Cubieboard and move to documentation step
after.
Ultimately it should be straight forward and easy to complete once we
have the documented process.
Peter
[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59382
[2] real12208m24.829s
user8047m56.250s
sys 3661m45.790s
--
Pavel
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora ARM Status Meeting 2013-12-04
On Wed, Dec 4, 2013 at 7:21 PM, Pavel Zhukov pa...@zhukoff.net wrote:
On Wednesday, December 04, 2013 07:11:40 PM Peter Robinson wrote:
On Wed, Dec 4, 2013 at 5:17 PM, Pavel Zhukov pzhu...@redhat.com wrote:
Hi list(s),
We still doesn't have gnat compiler for %{arm} in Fedora. We (Ada
community) have compiled gcc with ada support using gcc-4.8.2 src.rpm
and tested in. It seems workable. At least we were able to compile most
of the
packages from the stack with it.
I'd like to discuss way how to get it in Fedora (chicken-egg problem
should be solved).
That's relatively straight forward. We need a documented process to
get it done. Once we have that I can sort it out with rel-eng but we
would need the gcc maintainer to review/approve it.
Generally what happens is that it would be built (or imported) into a
side tag build. I suspect it'll be using something like a cross
compiled version of ada which is then used to compile a native built
version of ada which is then tagged into rawhide at which point the
rest of the ada stack would be rebuilt.
Yes. We cross-compiled bootstrap and compiled native version using it. It's
original Fedora gcc without any modifications (just added arm to the gnat
arches list) and applied short patch [1]
It was the long process [2] in qemu with all tests performed. I'm going to
recompile it once more time using Cubieboard and move to documentation step
after.
If you document it first I can test it on decent physical HW which
should be a lot faster to save you some time.
Peter
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
when Fedora 20 updates kernel to 3.12 ?
Hi, kernel 3.12 is out a long time, and still do see it on Fedora 20, to me doesn't make sense update it , just after lunching , should be test on test before . The politic of update stable kernel is fast to please me , sometimes in middle of a stable release you bump kernel , almost without testing it . Now that we are in testings, you don't put new kernel on that . Doesn't make sense to me. Thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
(read this one) when Fedora 20 updates kernel to 3.12 ?
Hi, kernel 3.12 is out a long time, and still don't see it on Fedora 20, to me doesn't make sense not update it, you will go update just after lunching ? Should be test on test before . The politic of update stables kernel is far to please me , sometimes in middle of a stable release you bump a kernel version, almost without testing it . Now that we are in testings, you don't put new kernel on that . Doesn't make sense to me. Thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: (read this one) when Fedora 20 updates kernel to 3.12 ?
On Wed, Dec 4, 2013 at 2:35 PM, Sérgio Basto ser...@serjux.com wrote: Hi, kernel 3.12 is out a long time, and still don't see it on Fedora 20, to me doesn't make sense not update it, you will go update just after lunching ? Should be test on test before . The politic of update stables kernel is far to please me , sometimes in middle of a stable release you bump a kernel version, almost without testing it . Now that we are in testings, you don't put new kernel on that . Doesn't make sense to me. You can find it for testing here: http://fedoraproject.org/wiki/RawhideKernelNodebug That is being kept at 3.12.y until a rebase is done in the releases. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: (read this one) when Fedora 20 updates kernel to 3.12 ?
On Wed, 04 Dec 2013 19:35:43 + Sérgio Basto ser...@serjux.com wrote: Hi, kernel 3.12 is out a long time, and still don't see it on Fedora 20, to me doesn't make sense not update it, you will go update just after lunching ? Should be test on test before . The politic of update stables kernel is far to please me , sometimes in middle of a stable release you bump a kernel version, almost without testing it . Now that we are in testings, you don't put new kernel on that . Doesn't make sense to me. Please see: https://lists.fedoraproject.org/pipermail/kernel/2013-November/004603.html and https://lists.fedoraproject.org/pipermail/kernel/2013-November/004635.html Basically it landed too late to get into Beta, and we don't want to ship final with a brand new kernel. It will be a update after release. This allows the installer images to use a known stable kernel, and folks who want the new one to get that one. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: when Fedora 20 updates kernel to 3.12 ?
On Wed, Dec 04, 2013 at 19:33:32 +, Sérgio Basto ser...@serjux.com wrote: Hi, kernel 3.12 is out a long time, and still do see it on Fedora 20, to me doesn't make sense update it , just after lunching , should be test on test before . The politic of update stable kernel is fast to please me , sometimes in middle of a stable release you bump kernel , almost without testing it . Now that we are in testings, you don't put new kernel on that . Doesn't make sense to me. 3.12 was not quite ready for beta, so it was decided to release with 3.11. Since the media are fixed at release it is very bad to have kernel bugs in them, so we are conservative with the version used with a Fedora release. 3.12 is available in the rawhide-nodebug repo now. It will probably be available as a zero day update for F20 (or will be an update shortly after release). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Test-Announce] 2013-12-04 @ 17:00 UTC - F20 Final Blocker Bug Review #4 Minutes
Below are the minutes from today's Blocker Review Meeting. We made it through all the listed blocker and freeze exception proposals. Looking forward to the Go/No-Go Meeting tomorrow... == #fedora-blocker-review: F20-blocker-review == Meeting started by pschindl at 17:00:04 UTC. Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/f20-blocker-review.2013-12-04-17.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/f20-blocker-review.2013-12-04-17.00.txt Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/f20-blocker-review.2013-12-04-17.00.log.html Meeting summary --- * Roll Call (pschindl, 17:00:08) * Introduction (pschindl, 17:02:00) * Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. (pschindl, 17:02:04) * We'll be following the process outlined at: (pschindl, 17:02:06) * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (pschindl, 17:02:07) * The bugs up for review today are available at: (pschindl, 17:02:09) * LINK: http://qa.fedoraproject.org/blockerbugs/current (pschindl, 17:02:11) * The criteria for release blocking bugs can be found at: (pschindl, 17:02:14) * LINK: https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria (pschindl, 17:02:16) * LINK: https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria (pschindl, 17:02:18) * LINK: https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria (pschindl, 17:02:26) * 7 Proposed Blockers (pschindl, 17:02:26) * 15 Accepted Blockers (pschindl, 17:02:27) * 2 Proposed Freeze Exceptions (pschindl, 17:02:27) * 14 Accepted Freeze Exceptions (pschindl, 17:02:27) * (1026834) method= combined with 'url' in kickstart fails to find packages, in certain situations (pschindl, 17:02:59) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1026834 (pschindl, 17:03:01) * Proposed Blocker, anaconda, NEW (pschindl, 17:03:03) * AGREED: 1026834 - RejectedBlocker AcceptedFreezeException - Non-functional method affects only virt users and post-release users won't be probably affected. Rejected as blocker but it's consider as FE (pschindl, 17:11:18) * (1037626) AttributeError: can't set attribute (pschindl, 17:11:34) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037626 (pschindl, 17:11:36) * Proposed Blocker, anaconda, MODIFIED (pschindl, 17:11:38) * AGREED: 1037626 - AcceptedBlocker - Broken text installation violates final criterion: When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces. (pschindl, 17:15:13) * (1037767) Text install : Error in sys.excepthook (pschindl, 17:15:18) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037767 (pschindl, 17:15:20) * Proposed Blocker, anaconda, POST (pschindl, 17:15:22) * AGREED: 1037767 - AcceptedBlocker - Reporting failures on ARM violates criterion: The installer must be able to report failures to Bugzilla, with appropriate information included. (pschindl, 17:29:53) * (1037934) 'unable to allocate aligned partition' errors keep occurring when trying to create partitions on iSCSI device, and does...other...odd...stuff (pschindl, 17:30:05) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037934 (pschindl, 17:30:07) * Proposed Blocker, anaconda, NEW (pschindl, 17:30:09) * 1037934 - needs more information. Now it's 2:1 against bug. Punt for more information. (pschindl, 17:38:01) * (881624) U.S. keyboard layout used for encryption passphrase entry during fedup second phase (pschindl, 17:38:18) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=881624 (pschindl, 17:38:20) * Proposed Blocker, fedup, NEW (pschindl, 17:38:22) * LINK: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-01-03/f18_final_gono-go_meeting.2013-01-03-17.01.log.txt is the log of previous discussion , search '881624' to find it (adamw, 17:42:44) * (1036961) Setting up bridge via NetworkManager gui in Gnome fails (pschindl, 17:55:49) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1036961 (pschindl, 17:55:51) * Proposed Blocker, NetworkManager, NEW (pschindl, 17:55:53) * AGREED: 1036961 - RejectedBlocker - Non-functional bridge NetworkManager setting is not considered as essential funcionality. (pschindl, 17:59:47) * (1037688) /root has 755 permissions - should be 550 (pschindl, 18:00:13) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1037688 (pschindl, 18:00:15) * Proposed Blocker, rootfiles, MODIFIED (pschindl, 18:00:17) * AGREED:
Re: FTBFS if -Werror=format-security flag is used
On 12/04/2013 07:59 PM, Rahul Sundaram wrote: Hi On Wed, Dec 4, 2013 at 1:45 PM, Brendan Jones wrote: I'm sorry, but I can't see why any of my packages (10+) are at risk This is just a best practice to mitigate any risks that might exist just like any of the other security improvements we make from time to time. Even if you don't see any immediate benefits, there is no harm in following the appropriate guidelines here. Coordinate with upstream Rahul Overkill if you ask me, Brendan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: (read this one) when Fedora 20 updates kernel to 3.12 ?
On Qua, 2013-12-04 at 12:42 -0700, Kevin Fenzi wrote: Basically it landed too late to get into Beta, and we don't want to ship final with a brand new kernel. It will be a update after release. This allows the installer images to use a known stable kernel, and folks who want the new one to get that one. We should ship kernel 3.12 rc something, instead. Don't landed to get into Beta is not a excuse (for me) . Beta is for testers, nothing better to test a new kernel, and not bumping after lunch a stable release ... , doesn't make sense to me . -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: (read this one) when Fedora 20 updates kernel to 3.12 ?
On Wed, Dec 4, 2013 at 3:15 PM, Sérgio Basto ser...@serjux.com wrote: On Qua, 2013-12-04 at 12:42 -0700, Kevin Fenzi wrote: Basically it landed too late to get into Beta, and we don't want to ship final with a brand new kernel. It will be a update after release. This allows the installer images to use a known stable kernel, and folks who want the new one to get that one. We should ship kernel 3.12 rc something, instead. Don't landed to get into Beta is not a excuse (for me) . It isn't an excuse. It's being conservative. Trying to nail a kernel for a Fedora release is fairly difficult, given that we can't plan for slips but we know they're coming. What we don't know is how many, how long, and what is going to happen upstream in bugzilla in the meantime. Beta is for testers, nothing better to test a new kernel, and not bumping after lunch a stable release ... , doesn't make sense to me . We'll take this under advisement for future releases. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
Hi On Wed, Dec 4, 2013 at 3:05 PM, Brendan Jones wrote: Overkill if you ask me, It might be appear to be one till it ends up avoiding or mitigating a security issue. It is just a bunch of trivial changes and I am sure you can ask for help for patches if needed. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Obsolete packages still included in Rawhide
Once again, there are obsolete packages still found in Rawhide. Obsolete here really means they are obsoleted (=replaced!) by some other package. Undead here means they are not marked dead in dist git. Please note that retiring packages is easier nowadays: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life If not retiring them properly, typically someone builds an update with a higher EVR that breaks existing Obsoletes tags. Undead and all builds obsoleted: blueman obsoleted by: bluez libmatekeyring obsoleted by: mate-desktop mate-keyring obsoleted by: mate-desktop mingw-pthreads obsoleted by: mingw-winpthreads openshift-origin-cartridge-cron-1.4 obsoleted by: openshift-origin-cartridge-cron openshift-origin-cartridge-diy-0.1 obsoleted by: openshift-origin-cartridge-diy php-channel-symfony2 obsoleted by: php-symfony php-symfony2-BrowserKit obsoleted by: php-symfony php-symfony2-ClassLoader obsoleted by: php-symfony php-symfony2-Config obsoleted by: php-symfony php-symfony2-Console obsoleted by: php-symfony php-symfony2-CssSelector obsoleted by: php-symfony php-symfony2-DependencyInjection obsoleted by: php-symfony php-symfony2-DomCrawler obsoleted by: php-symfony php-symfony2-EventDispatcher obsoleted by: php-symfony php-symfony2-Filesystem obsoleted by: php-symfony php-symfony2-Finder obsoleted by: php-symfony php-symfony2-Form obsoleted by: php-symfony php-symfony2-HttpFoundation obsoleted by: php-symfony php-symfony2-HttpKernel obsoleted by: php-symfony php-symfony2-Locale obsoleted by: php-symfony php-symfony2-OptionsResolver obsoleted by: php-symfony php-symfony2-Process obsoleted by: php-symfony php-symfony2-PropertyAccess obsoleted by: php-symfony php-symfony2-Routing obsoleted by: php-symfony php-symfony2-Security obsoleted by: php-symfony php-symfony2-Serializer obsoleted by: php-symfony php-symfony2-Templating obsoleted by: php-symfony php-symfony2-Translation obsoleted by: php-symfony php-symfony2-Validator obsoleted by: php-symfony php-symfony2-Yaml obsoleted by: php-symfony python-cpopen obsoleted by: vdsm qt5-qtjsbackend obsoleted by: qt5-qtdeclarative sysvinit obsoleted by: procps-ng -- http://mschwendt.fedorapeople.org/obscheck-remote.py -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Obsolete packages still included in Rawhide
python-ordereddict is obsolete also: https://bugzilla.redhat.com/show_bug.cgi?id=100 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate documentation files / potentially conflicting
On Wed, Dec 04, 2013 at 02:58:47PM +0100, Michael Schwendt wrote:
On Wed, 4 Dec 2013 12:08:08 +, Richard W.M. Jones wrote:
I've read this several times, and
https://fedoraproject.org/wiki/Changes/UnversionedDocdirs
and I still don't understand what this message means.
My message or a specific bugzilla ticket?
Your message. Let's take this bug at random, linked from the
tracker bug (993551):
https://bugzilla.redhat.com/show_bug.cgi?id=993805
If I'm understanding this correctly, the problem is that the GRASS
spec file will create /usr/share/doc/grass-%{version}/... files
because of:
http://pkgs.fedoraproject.org/cgit/grass.git/tree/grass.spec#n210
That's definitely an (un)versioned docdirs problem, no doubt.
GRASS uses doxygen. But it is not noarch, so presumably this package
is not affected?
If it's not affected, could you please link to the specific bug of a
package which is affected.
How would this cause subpackage conflicts?
Have you heard about Doxygen generated documentation causing conflicts?
Here the problem is expanded into a conflict between the base package
and the second package that also includes the documentation.
What has arch/noarch got to do with anything?
A noarch subpackage may be built on any build arch different than the
builder that creates the base package. This triggers bugs (such as the
Doxygen timestamp/footer bug), because the noarch build's doc files may
differ from the arch build's doc files.
Won't the subpackage put docs in /usr/share/doc/pkg-subpkg/ ?
If no noarch subpkg is involved, it [hopefully] boils down to just
duplicated files.
Can you point to an example of a packaging problem?
Duplicate files are a packaging problem already. Duplicating the entire
contents of a huge -doc subpackage in the base package is a problem.
So I think what you're saying is that all subpackage docs are (or
should be?) placed in /usr/share/doc/pkg/ ignoring the subpackage
name? That is *not* my understanding of how unversioned docdirs works.
Worse if there is a conflict. The bug reports don't claim there is a
conflict _always_. But we encounter Doxygen related conflicts regularly,
even during review.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Fedora-packaging] Proposal for Python guidelines change (in connection to Python 3 switch)
On Wed, Dec 04, 2013 at 07:18:31AM -0500, Bohuslav Kabrda wrote: - Original Message - Dne 4.12.2013 12:37, Bohuslav Kabrda napsal(a): (tkinter is actually a subpackage of python itself) I guess you know what I mean here, but to be clear: tkinter is only an example, we got more, like pyserial, PyYAML... Oh, I see. Some time ago, FPC has accepted a change that says, that packages with py in name should be prefixed with python- anyway [1]. Since this only applies to newly created packages, we will have to cope with this, unfortunately. So my idea of handling this would be: - all packages must have Provides: python-* - packages that weren't prefixed with python- previously (pyserial, PyYAML), should also carry an explicit Provides/Obsoletes for the old name. Sounds good? I would remove that first bullet point. The point of the Provides and Obsoletes is to provide backwards compatibility. If there's no previous python-* there's no need to take up that name in the namespace. Other thing: What about apps? Do we want something in the guidelines that would say: If the app clearly works with both Python 2 and Python 3, then the Fedora package is obligated to use Python 3 instead of Python 2. If however the app only works with one of them, obviously, Fedora package uses and requires that one. Or do we keep that on the packager's decision? Toshio already proposed a guidelines solution for this [2], but now that I look at it, it seems that it never got proposed to FPC. Toshio, will you propose that or should I? I guess we can do this regardless of the change I'm proposing now. [2] https://lists.fedoraproject.org/pipermail/python-devel/2013-November/000528.html Please do. I haven't got a whole lot of time these days :-( -Toshio pgpzv_fqzfdt2.pgp Description: PGP signature ___ python-devel mailing list python-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
Fedora ARM Status Meeting Minutes 2013-12-04
Thanks to those that were able to join us for the status meeting today, for those unable the minutes are posted below: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-04/fedora-meeting-1.2013-12-04-21.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-04/fedora-meeting-1.2013-12-04-21.00.txt Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-04/fedora-meeting-1.2013-12-04-21.00.log.html #fedora-meeting-1: Fedora ARM status meeting Meeting summary --- * 1) Kernel Status Update (pwhalen, 21:04:23) * rawhide scratch builds can be found - http://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/ (pwhalen, 21:11:10) * 3.12 kernel should be much better for imx6 in general, adding support for all Wandboards and initial support for Utilite (pwhalen, 21:13:38) * 2a) Aarch64 - Status Update (pwhalen, 21:16:15) * ACTION: hrw to send list of existing aarch64 patches to the fedora-arm list (pwhalen, 21:20:56) * 2b) Aarch64 - Images (pwhalen, 21:22:48) * rawhide aarch64 images expected before the end of the year (pwhalen, 21:25:04) * 3) F20 TC4 Testing Summary (pwhalen, 21:26:47) * LINK: Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test (pwhalen, 21:26:53) * LINK: Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test (pwhalen, 21:27:00) * LINK: Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test (pwhalen, 21:27:00) * LINK: https://fedoraproject.org/wiki/Architectures/ARM/AArch64/PatchesToMergeIntoFedora (hrw, 21:35:14) * 4) What are people planning to work on for F-21? (formerly known as F21 Wish list) (pwhalen, 21:37:45) * 4) Open Floor (pwhalen, 21:44:52) Meeting ended at 21:47:33 UTC. Action Items * hrw to send list of existing aarch64 patches to the fedora-arm list Action Items, by person --- * hrw * hrw to send list of existing aarch64 patches to the fedora-arm list * **UNASSIGNED** * (none) People Present (lines said) --- * pbrobinson (46) * pwhalen (41) * hrw (22) * zodbot (7) * jcapik (6) * bconoboy (6) * kylem (5) * masta (2) * dmarlin (1) * nirik (1) * ahs3 (0) * msalter (0) * jdisnard (0) * ctyler (0) * agreene (0) * handsome_pirate (0) * jonmasters (0) * dgilmore (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: (read this one) when Fedora 20 updates kernel to 3.12 ?
Am 04.12.2013 21:15, schrieb Sérgio Basto: On Qua, 2013-12-04 at 12:42 -0700, Kevin Fenzi wrote: Basically it landed too late to get into Beta, and we don't want to ship final with a brand new kernel. It will be a update after release. This allows the installer images to use a known stable kernel, and folks who want the new one to get that one. We should ship kernel 3.12 rc something, instead. Don't landed to get into Beta is not a excuse (for me) . Beta is for testers, nothing better to test a new kernel, and not bumping after lunch a stable release ... , doesn't make sense to me it makes sense if you find out too late that the new kernel has regressions which are affecting too much users there is no way to fix that and they all maybe are impossible to install the new release from the ISO image after the release even with the first yum-update you can boot with the old one if things go wrong and write a bugreport from a working machine signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/04/2013 09:39 PM, Rahul Sundaram wrote: Hi On Wed, Dec 4, 2013 at 3:05 PM, Brendan Jones wrote: Overkill if you ask me, It might be appear to be one till it ends up avoiding or mitigating a security issue. It is just a bunch of trivial changes and I am sure you can ask for help for patches if needed. Rahul Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On Wed, Dec 04, 2013 at 11:56:23PM +0100, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? Google for sudo format string exploit Yours Tony pgpit7eFTE85S.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? -- Ian Pilcher arequip...@gmail.com Sent from the cloud -- where it's already tomorrow -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate documentation files / potentially conflicting
On Wed, 4 Dec 2013 21:38:49 +, Richard W.M. Jones wrote:
On Wed, Dec 04, 2013 at 02:58:47PM +0100, Michael Schwendt wrote:
On Wed, 4 Dec 2013 12:08:08 +, Richard W.M. Jones wrote:
I've read this several times, and
https://fedoraproject.org/wiki/Changes/UnversionedDocdirs
and I still don't understand what this message means.
My message or a specific bugzilla ticket?
Your message. Let's take this bug at random, linked from the
tracker bug (993551):
https://bugzilla.redhat.com/show_bug.cgi?id=993805
That's not a ticket opened by me. It's about something else, albeit
also related to the unversioned docdirs change.
If I'm understanding this correctly, the problem is that the GRASS
spec file will create /usr/share/doc/grass-%{version}/... files
because of:
http://pkgs.fedoraproject.org/cgit/grass.git/tree/grass.spec#n210
Correct.
That's definitely an (un)versioned docdirs problem, no doubt.
GRASS uses doxygen. But it is not noarch, so presumably this package
is not affected?
Affected by what?
This particular ticket has been opened by Ville because for F20 the
package does _not_ install into an unversioned %doc dir (since it
explicitly installs into a versioned one).
If it's not affected, could you please link to the specific bug of a
package which is affected.
Affected by what? For duplicated %doc file trees there are the tickets
with the same subject as this thread. They may or may not cause conflicts
depending on which builder has been used and depending on whether a tool
like doxygen is configured correctly at build-time. The next build may
lead to a conflict. Hence potentially conflicting, not certainly
conflicting.
How would this cause subpackage conflicts?
Have you heard about Doxygen generated documentation causing conflicts?
Here the problem is expanded into a conflict between the base package
and the second package that also includes the documentation.
What has arch/noarch got to do with anything?
A noarch subpackage may be built on any build arch different than the
builder that creates the base package. This triggers bugs (such as the
Doxygen timestamp/footer bug), because the noarch build's doc files may
differ from the arch build's doc files.
Won't the subpackage put docs in /usr/share/doc/pkg-subpkg/ ?
Ah, now it's getting interesting! The tickets I've opened link the FPC
ticket #338 that gives the background. The answer to your question _would
be_ yes for the normal case that the packager used only %doc to include
local files in any subpackages. But packagers don't do that. They mix %doc
and /usr/share/doc/%{name}/* entries in the %files lists. _That_ causes the
base package to include _everything_ in that dir even if it only uses %doc
to include specific local files. - It's a side-effect of the %doc macro.
If no noarch subpkg is involved, it [hopefully] boils down to just
duplicated files.
Can you point to an example of a packaging problem?
Duplicate files are a packaging problem already. Duplicating the entire
contents of a huge -doc subpackage in the base package is a problem.
So I think what you're saying is that all subpackage docs are (or
should be?) placed in /usr/share/doc/pkg/ ignoring the subpackage
name?
No.
That is *not* my understanding of how unversioned docdirs works.
You've misunderstood something.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On Wed, Dec 04, 2013 at 05:11:16PM -0600, Ian Pilcher wrote: On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? With -D_FORTIFY_SOURCE=2 the program is aborted, unless the string resides in read-only memory ;) Jakub -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/05/2013 12:11 AM, Ian Pilcher wrote: On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? I remain unconvinced. Exploit my system with one of ams, aubio, hydrogen, jack-keyboard, phasex, portmidi or yoshimi. I just can't see it -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Retiring gksu-polkit
It seems that this package is no longer needed. Please let me know there is a reason that we should keep it. Will retire on all Fedora releases next week. Thanks, Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On Thu, Dec 5, 2013 at 12:11 AM, Brendan Jones brendan.jones...@gmail.com wrote: On 12/05/2013 12:11 AM, Ian Pilcher wrote: On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? I remain unconvinced. Exploit my system with one of ams, aubio, hydrogen, jack-keyboard, phasex, portmidi or yoshimi. I just can't see it Suppose I create a malicious drumkit and either get it uploaded to one of the officially recommended links at http://www.hydrogen-music.org/hcms/node/16 , or even just attach it in bugzilla to a bug report saying that the Fedora hydrogen package crashes or otherwise mishandles that file (causing _you_ personally to open that file, even if in a debugger)? Note that I _don't really know_ whether this is exploitable with hydrogen; though the incorrect format strings being in a class named Object does suggest that the affected input paths may be pretty widespread. Even if this weren't a security issue (or it were already mitigated by _FORTIFY_SOURCE), it's a simple correctness issue: the program's output should be correct, and the program should not abort just because 100%new happens to appear in a string. As long as it it's worth it to have software packaged in Fedora it's not unnecessary to fix bugs IMHO. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/05/2013 12:28 AM, Miloslav Trmač wrote: On Thu, Dec 5, 2013 at 12:11 AM, Brendan Jones brendan.jones...@gmail.com wrote: On 12/05/2013 12:11 AM, Ian Pilcher wrote: On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? I remain unconvinced. Exploit my system with one of ams, aubio, hydrogen, jack-keyboard, phasex, portmidi or yoshimi. I just can't see it Suppose I create a malicious drumkit and either get it uploaded to one of the officially recommended links at http://www.hydrogen-music.org/hcms/node/16 , or even just attach it in bugzilla to a bug report saying that the Fedora hydrogen package crashes or otherwise mishandles that file (causing _you_ personally to open that file, even if in a debugger)? Note that I _don't really know_ whether this is exploitable with hydrogen; though the incorrect format strings being in a class named Object does suggest that the affected input paths may be pretty widespread. Probably a bad example. I guess its another case of educating upstream. They love that -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On Wed, Dec 4, 2013 at 3:54 PM, Brendan Jones brendan.jones...@gmail.com wrote: On 12/05/2013 12:28 AM, Miloslav Trmač wrote: On Thu, Dec 5, 2013 at 12:11 AM, Brendan Jones brendan.jones...@gmail.com wrote: On 12/05/2013 12:11 AM, Ian Pilcher wrote: On 12/04/2013 04:56 PM, Brendan Jones wrote: Patching is not a problem. Unnecessary is the question. Explain to me (not you in particular Rahul) how these printf's can possibly be exploited? char *output; output = get_user_input(...); printf(output); What happens when the user enters %n? I remain unconvinced. Exploit my system with one of ams, aubio, hydrogen, jack-keyboard, phasex, portmidi or yoshimi. I just can't see it Suppose I create a malicious drumkit and either get it uploaded to one of the officially recommended links at http://www.hydrogen-music.org/hcms/node/16 , or even just attach it in bugzilla to a bug report saying that the Fedora hydrogen package crashes or otherwise mishandles that file (causing _you_ personally to open that file, even if in a debugger)? Note that I _don't really know_ whether this is exploitable with hydrogen; though the incorrect format strings being in a class named Object does suggest that the affected input paths may be pretty widespread. Probably a bad example. I guess its another case of educating upstream. They love that It's really a trivial fix. In some of my packages it was already patched upstream. Regardless of whether or not you are convinced or anyone else for that matter, possible security flaws should always be patched whether or not they are probably or improbable. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if -Werror=format-security flag is used
On 12/04/2013 12:10 PM, Brendan Jones wrote: This is just a pain. Can someone explain to me why this is good? Good or not, this is not the right question to ask. * Is this necessarry, and are the benefits worth the pains? * This change is Sofa King stupid. Why couldn't we have just enabled the warning without turning it into an error, THEN let packagers work with upstream in fixing those warnings? Regulate, not ban. Alex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Obsolete packages still included in Rawhide
On Wed, Dec 4, 2013 at 12:57 PM, Michael Schwendt mschwe...@gmail.com wrote: libmatekeyring obsoleted by: mate-desktop mate-keyring obsoleted by: mate-desktop We know about these 2 and will obsolete them soon. Thanks, Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-Sys-Virt] Update to 1.2.0 release
commit 5120638ecf31c4c4170206c3ff9a5c6b87510c39
Author: Daniel P. Berrange berra...@redhat.com
Date: Mon Dec 2 17:55:12 2013 +
Update to 1.2.0 release
Signed-off-by: Daniel P. Berrange berra...@redhat.com
perl-Sys-Virt.spec |5 -
sources|2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/perl-Sys-Virt.spec b/perl-Sys-Virt.spec
index 64c2bcc..edc96d3 100644
--- a/perl-Sys-Virt.spec
+++ b/perl-Sys-Virt.spec
@@ -1,7 +1,7 @@
# Automatically generated by perl-Sys-Virt.spec.PL
Name: perl-Sys-Virt
-Version:1.1.4
+Version:1.2.0
Release:1%{?dist}%{?extra_release}
Summary:Represent and manage a libvirt hypervisor connection
License:GPLv2+ or Artistic
@@ -59,6 +59,9 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Mon Dec 2 2013 Daniel P. Berrange berra...@redhat.com - 1.2.0-1
+- Update to 1.2.0 release
+
* Tue Nov 5 2013 Daniel P. Berrange berra...@redhat.com - 1.1.4-1
- Update to 1.1.4 release
diff --git a/sources b/sources
index 3382c1f..a891a6e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-1125059b25f48867ffdb3c432e757327 Sys-Virt-1.1.4.tar.gz
+bbb9c252ae785bd07d8a176b9be828e4 Sys-Virt-1.2.0.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the F-20 tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Language-Prolog-Yaswi
perl-Language-Prolog-Yaswi has broken dependencies in the rawhide tree: On x86_64: perl-Language-Prolog-Yaswi-0.21-14.fc21.x86_64 requires libswipl.so.6.4.1()(64bit) On i386: perl-Language-Prolog-Yaswi-0.21-14.fc21.i686 requires libswipl.so.6.4.1 On armhfp: perl-Language-Prolog-Yaswi-0.21-14.fc21.armv7hl requires libswipl.so.6.4.1 Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Locale-Codes
perl-Locale-Codes has broken dependencies in the rawhide tree: On x86_64: perl-Locale-Codes-3.28-1.fc21.noarch requires perl(Locale::Codes::LangFam_Retired) On i386: perl-Locale-Codes-3.28-1.fc21.noarch requires perl(Locale::Codes::LangFam_Retired) On armhfp: perl-Locale-Codes-3.28-1.fc21.noarch requires perl(Locale::Codes::LangFam_Retired) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the rawhide tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1037242] perl-Proc-ProcessTable FTBFS if -Werror=format-security flag is used
https://bugzilla.redhat.com/show_bug.cgi?id=1037242 Dhiru Kholia dkho...@redhat.com changed: What|Removed |Added Blocks||1038083 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1038083 [Bug 1038083] tracker bug for -Werror=format-security change -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ns2dczia3ja=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Language-Prolog-Yaswi] Rebuild against pl-6.6.0
commit f136ea3e565deb541017943fb00fadadde4b2e68
Author: Petr Písař ppi...@redhat.com
Date: Wed Dec 4 12:56:53 2013 +0100
Rebuild against pl-6.6.0
perl-Language-Prolog-Yaswi.spec |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/perl-Language-Prolog-Yaswi.spec b/perl-Language-Prolog-Yaswi.spec
index 89932a0..a388560 100644
--- a/perl-Language-Prolog-Yaswi.spec
+++ b/perl-Language-Prolog-Yaswi.spec
@@ -1,6 +1,6 @@
Name: perl-Language-Prolog-Yaswi
Version:0.21
-Release:14%{?dist}
+Release:15%{?dist}
Summary:Yet another interface to SWI-Prolog
License:GPL+ or Artistic
Group: Development/Libraries
@@ -65,6 +65,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Wed Dec 04 2013 Petr Pisar ppi...@redhat.com - 0.21-15
+- Rebuild against pl-6.6.0
+
* Wed Sep 04 2013 Petr Pisar ppi...@redhat.com - 0.21-14
- Rebuild against pl-6.4.1
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Fennec] Update to 2.011
commit 64a879bfca4627068b61b5fb84a7b91e30679b3b
Author: Paul Howarth p...@city-fan.org
Date: Wed Dec 4 12:09:52 2013 +
Update to 2.011
- New upstream release 2.011
- Typo fixes and documentation enhancements
- Support the generation of tracking debugging information
perl-Fennec.spec |9 +++--
sources |2 +-
2 files changed, 8 insertions(+), 3 deletions(-)
---
diff --git a/perl-Fennec.spec b/perl-Fennec.spec
index 3480fbc..3a9a0e3 100644
--- a/perl-Fennec.spec
+++ b/perl-Fennec.spec
@@ -2,8 +2,8 @@
# guarded by %{?perl_bootstrap} since it requires perl(Fennec) itself
Name: perl-Fennec
-Version: 2.010
-Release: 3%{?dist}
+Version: 2.011
+Release: 1%{?dist}
Summary: A tester's toolbox, and best friend
License: GPL+ or Artistic
Group: Development/Libraries
@@ -99,6 +99,11 @@ perl Build.PL installdirs=vendor
%{_mandir}/man3/Test::Workflow::Test.3pm*
%changelog
+* Wed Dec 4 2013 Paul Howarth p...@city-fan.org - 2.011-1
+- Update to 2.011
+ - Typo fixes and documentation enhancements
+ - Support the generation of tracking debugging information
+
* Mon Sep 2 2013 Paul Howarth p...@city-fan.org - 2.010-3
- BR: perl(lib) and perl(Data::Dumper) (#997554)
diff --git a/sources b/sources
index 257da14..0b94ace 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-908496545b51d31dd87a2dc8571b2e75 Fennec-2.010.tar.gz
+5c2ea67ed482dfa6f4c536eb720538e7 Fennec-2.011.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Fennec] Created tag perl-Fennec-2.011-1.fc21
The lightweight tag 'perl-Fennec-2.011-1.fc21' was created pointing to: 64a879b... Update to 2.011 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[389-devel] 389-ds-base_Debian_Wheezy - Build # 130 - Fixed!
389-ds-base_Debian_Wheezy - Build # 130 - Fixed: See attached build log for details. build.log Description: Binary data -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
[389-devel] please review: Ticket 47587 - hard coded limit of 64 masters in agreement and changelog code
https://fedorahosted.org/389/ticket/47587 https://fedorahosted.org/389/attachment/ticket/47587/0001-Ticket-47587-hard-coded-limit-of-64-masters-in-agree.patch -- Mark Reynolds 389 Development Team Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: [Fedora-packaging] Proposal for Python guidelines change (in connection to Python 3 switch)
Dne 4.12.2013 12:37, Bohuslav Kabrda napsal(a): (tkinter is actually a subpackage of python itself) I guess you know what I mean here, but to be clear: tkinter is only an example, we got more, like pyserial, PyYAML... Other thing: What about apps? Do we want something in the guidelines that would say: If the app clearly works with both Python 2 and Python 3, then the Fedora package is obligated to use Python 3 instead of Python 2. If however the app only works with one of them, obviously, Fedora package uses and requires that one. Or do we keep that on the packager's decision? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list python-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
Re: {__python2} for el6?
On Wed, Dec 04, 2013 at 02:41:30PM -0500, Ralph Bean wrote:
Back in August, the {__python} macro was deprecated in favor of
{__python2}. This is cool as it paves the way for an eventual python3
takeover.
https://fedoraproject.org/w/index.php?title=Packaging:Pythondiff=350838oldid=350837
However, {__python} is still the expected macro for el6 builds. Many of us
maintain single spec files that we build for Fedora and EPEL.
- Does anyone have any recommendations about how to handle this?
Someone should take a look at the present guidelines but I think just using
/usr/bin/python2 (or python2 and letting PATH do the rest) is probably okay.
I recently started using this blurb at the top of my new spec files.
Will it do?
%if 0%{?rhel} 0%{?rhel} = 6
%{!?__python2:%global __python2 %{__python}}
%{!?python2_sitelib: %global python2_sitelib %(%{__python} -c from
distutils.sysconfig import get_python_lib; print(get_python_lib()))}
%{!?python2_sitearch: %global python2_sitearch %(%{__python} -c from
distutils.sysconfig import get_python_lib; print(get_python_lib(1)))}
%endif
it's probably more correct to do this this way:
%if 0%{?rhel} 0%{?rhel} = 6
%{!?__python2:%global __python2 /usr/bin/python2}
%{!?python2_sitelib: %global python2_sitelib %(%{__python2} -c from
distutils.sysconfig import get_python_lib; print(get_python_lib()))}
%{!?python2_sitearch: %global python2_sitearch %(%{__python2} -c from
distutils.sysconfig import get_python_lib; print(get_python_lib(1)))}
%endif
- If we decide on a canonical approach, can it be added to the Python
guidelines as a recommendation?
Yeah, but please draft it up. I'm low on time so even completing writing of
the changes for this approved guideline change hasn't been something I've
gotten too:
https://fedorahosted.org/fpc/ticket/327#comment:9
-Toshio
pgpB7Y6uGMaqb.pgp
Description: PGP signature
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
