Fedora 20 updates-testing report
The following Fedora 20 Security updates need testing: Age URL 87 https://admin.fedoraproject.org/updates/FEDORA-2014-5897/nrpe-2.15-2.fc20 67 https://admin.fedoraproject.org/updates/FEDORA-2014-6551/chicken-4.8.0.6-2.fc20 65 https://admin.fedoraproject.org/updates/FEDORA-2014-6615/drupal7-views-3.8-1.fc20 37 https://admin.fedoraproject.org/updates/FEDORA-2014-7551/asterisk-11.10.2-2.fc20 36 https://admin.fedoraproject.org/updates/FEDORA-2014-7613/perl-Email-Address-1.905-1.fc20 27 https://admin.fedoraproject.org/updates/FEDORA-2014-7936/python3-3.3.2-16.fc20 18 https://admin.fedoraproject.org/updates/FEDORA-2014-8065/rubygem-activerecord-4.0.0-4.fc20 16 https://admin.fedoraproject.org/updates/FEDORA-2014-5497/openstack-keystone-2013.2.3-5.fc20 14 https://admin.fedoraproject.org/updates/FEDORA-2014-8334/python-bottle-0.12.6-1.fc20 10 https://admin.fedoraproject.org/updates/FEDORA-2014-8412/mosquitto-1.3.2-1.fc20 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8485/drupal7-7.29-1.fc20 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8510/sdcc-3.3.0-1.fc20 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8458/gd-2.1.0-6.fc20 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8495/drupal6-6.32-1.fc20 6 https://admin.fedoraproject.org/updates/FEDORA-2014-8581/phpMyAdmin-4.2.6-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-8601/moodle-2.5.7-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-8189/krb5-1.11.5-10.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2014-8743/openstack-neutron-2013.2.3-13.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2014-8752/cups-1.7.4-3.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2014-8865/exim-4.80.1-7.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2014-8790/trafficserver-4.2.1.1-0.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-8901/ansible-1.6.10-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2014-8920/bugzilla-4.2.10-1.fc20 The following Fedora 20 Critical Path updates have yet to be approved: Age URL 5 https://admin.fedoraproject.org/updates/FEDORA-2014-8189/krb5-1.11.5-10.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2014-8922/gnome-shell-3.10.4-8.fc20,mutter-3.10.4-3.fc20 The following builds have been pushed to Fedora 20 updates-testing bugzilla-4.2.10-1.fc20 freesteam-2.1-3.20140724svn753.fc20 geary-0.6.1-2.fc20 gnome-shell-3.10.4-8.fc20 kBuild-0.1.9998-2.r2730.fc20 kde-plasma-nm-0.9.3.4-11.201407024git38b75ec.fc20 libreoffice-4.2.5.2-11.fc20 libsigrokdecode-0.3.0-1.fc20 mutter-3.10.4-3.fc20 texstudio-2.8.2-1.fc20 Details about builds: bugzilla-4.2.10-1.fc20 (FEDORA-2014-8920) Bug tracking system Update Information: This version of bugzilla includes a security fix for CVE-2014-1546. With previous versions, an attacker can get access to some bug information using the victim's credentials using a specially crafted HTML page. ChangeLog: * Fri Jul 25 2014 Emmanuel Seyman - 4.2.10-1 - Update to 4.2.10 which fixes a security bug (CVE-2014-1546) References: [ 1 ] Bug #1123172 - CVE-2014-1546 bugzilla: Cross Site Request Forgery issue with Bugzilla's JSONP endpoint https://bugzilla.redhat.com/show_bug.cgi?id=1123172 freesteam-2.1-3.20140724svn753.fc20 (FEDORA-2014-8921) Calculate the properties of water and steam Update Information: New package References: [ 1 ] Bug #1120791 - Review Request: freesteam - Calculate the properties of water and steam https://bugzilla.redhat.com/show_bug.cgi?id=1120791 geary-0.6.1-2.fc20 (FEDORA-2014-8917) A lightweight email program designed around conversations Update Information: Added a patch to fix incorrectly formatted date headers in new emails. ChangeLog: * Fri Jul 25 2014 Thomas Moschny - 0.6.1-2 - Add patch to fix timezone in date header (rhbz#1121306). - Add patch to build with vala 0.25.
Fedora 19 updates-testing report
The following Fedora 19 Security updates need testing: Age URL 275 https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19 87 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19 67 https://admin.fedoraproject.org/updates/FEDORA-2014-6553/chicken-4.8.0.6-2.fc19 65 https://admin.fedoraproject.org/updates/FEDORA-2014-6597/drupal7-views-3.8-1.fc19 38 https://admin.fedoraproject.org/updates/FEDORA-2014-7496/readline-6.2-8.fc19 37 https://admin.fedoraproject.org/updates/FEDORA-2014-7570/asterisk-11.10.2-2.fc19 36 https://admin.fedoraproject.org/updates/FEDORA-2014-6774/claws-mail-3.10.1-1.fc19,claws-mail-plugins-3.10.0-1.fc19,libetpan-1.5-1.fc19 36 https://admin.fedoraproject.org/updates/FEDORA-2014-7610/perl-Email-Address-1.905-1.fc19 27 https://admin.fedoraproject.org/updates/FEDORA-2014-7939/lzo-2.08-1.fc19 22 https://admin.fedoraproject.org/updates/FEDORA-2014-8089/rubygem-activerecord-3.2.13-2.fc19 14 https://admin.fedoraproject.org/updates/FEDORA-2014-8328/python-bottle-0.12.6-1.fc19 14 https://admin.fedoraproject.org/updates/FEDORA-2014-8332/transmission-2.84-1.fc19 10 https://admin.fedoraproject.org/updates/FEDORA-2014-8443/mosquitto-1.3.2-1.fc19 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8515/drupal7-7.29-1.fc19 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8528/sdcc-3.3.0-1.fc19 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8564/dpkg-1.16.15-1.fc19 8 https://admin.fedoraproject.org/updates/FEDORA-2014-8488/drupal6-6.32-1.fc19 6 https://admin.fedoraproject.org/updates/FEDORA-2014-8577/phpMyAdmin-4.2.6-1.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-8176/krb5-1.11.3-24.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-8609/moodle-2.4.11-1.fc19 4 https://admin.fedoraproject.org/updates/FEDORA-2014-8352/cups-1.6.4-7.fc19 4 https://admin.fedoraproject.org/updates/FEDORA-2014-8771/ReviewBoard-1.7.27-1.fc19 2 https://admin.fedoraproject.org/updates/FEDORA-2014-8803/exim-4.80.1-4.fc19 2 https://admin.fedoraproject.org/updates/FEDORA-2014-8809/thunderbird-24.7.0-1.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-8904/ansible-1.6.10-1.fc19 0 https://admin.fedoraproject.org/updates/FEDORA-2014-8919/bugzilla-4.2.10-1.fc19 The following Fedora 19 Critical Path updates have yet to be approved: Age URL 223 https://admin.fedoraproject.org/updates/FEDORA-2013-22326/fedora-bookmarks-15-5.fc19 149 https://admin.fedoraproject.org/updates/FEDORA-2014-3245/testdisk-6.14-2.fc19.1,ntfs-3g-2014.2.15-1.fc19 12 https://admin.fedoraproject.org/updates/FEDORA-2014-8360/pcre-8.32-10.fc19 12 https://admin.fedoraproject.org/updates/FEDORA-2014-8338/curl-7.29.0-21.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-8176/krb5-1.11.3-24.fc19 4 https://admin.fedoraproject.org/updates/FEDORA-2014-8761/systemd-204-20.fc19 4 https://admin.fedoraproject.org/updates/FEDORA-2014-8352/cups-1.6.4-7.fc19 2 https://admin.fedoraproject.org/updates/FEDORA-2014-8809/thunderbird-24.7.0-1.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-8910/qt5-qtbase-5.3.1-5.fc19,qt-4.8.6-10.fc19 The following builds have been pushed to Fedora 19 updates-testing bugzilla-4.2.10-1.fc19 kBuild-0.1.9998-2.r2730.fc19 Details about builds: bugzilla-4.2.10-1.fc19 (FEDORA-2014-8919) Bug tracking system Update Information: This version of bugzilla includes a security fix for CVE-2014-1546. With previous versions, an attacker can get access to some bug information using the victim's credentials using a specially crafted HTML page. ChangeLog: * Fri Jul 25 2014 Emmanuel Seyman - 4.2.10-1 - Update to 4.2.10 which fixes a security bug (CVE-2014-1546) References: [ 1 ] Bug #1123172 - CVE-2014-1546 bugzilla: Cross Site Request Forgery issue with Bugzilla's JSONP endpoint https://bugzilla.redhat.com/show_bug.cgi?id=1123172 kBuild-0.1.9998-2.r2730.fc19 (FEDORA-2014-8915) A cross-platform build environment Update Information: Update to trunk HEAD version, have a fix for gcc >= 4.7 (http://trac.netlabs.org/kbuild/ticket/112) ChangeLog: * Sun Jun 8 2014 Fedora Release Engineering - 0.1.9998-2.r2730 - Rebuilt for https://fedorap
fedora-logos- erase skipped
This message has been happening on the screens of my more than a dozen F21 and Rawhide installations during most (all?) yum upgrades since long before the branching, but doesn't show up in /var/log/yum.log. Does it happen to anyone else? Is it normal for pre-release installations? The result from query on the 21 currently booted is 21.0.3-1, which has last changelog entry back in February. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
On Seg, 2014-07-28 at 00:06 +0200, Jon Ingason wrote: > 2014-07-27 23:36, Sérgio Basto skrev: > > On Dom, 2014-07-27 at 23:31 +0200, Jon Ingason wrote: > >> 2014-07-27 21:50, Kevin Fenzi skrev: > >>> On Sun, 27 Jul 2014 18:24:16 +0200 > >>> Jon Ingason wrote: > >>> > I follow the Rawhide wiki how to branch Rawhide to Fedora 21. > What I did was that I installed > Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with > libvirt. Then I clone it and used it to do the brancing. > >>> > >>> ...snip... > >>> > What does that mean? How can I fix this? > >>> > >>> What does: > >>> > >>> rpm -q fedora-release fedora-repos fedora-repos-rawhide > >>> > >>> output? > >> > >> $ rpm -q fedora-realese fedora-repos fedora-rawhide-repos > >> paket fedora-realese är inte installerat > >> fedora-repos-22-0.1.noarch > > > > you need remove fedora-repos-22-0.1.noarch , at least > > > > yum remove fedora-repos-22-0.1.noarch > > Did that but did not help. > > Found that fedora-release-22-0-4.noarch was installed an remove it. Then > I could run yum update, but there was lot of f22 package still > installed. Need find way to remove them later. rpm -q fedora-release-21 fedora-release-20 fedora-release-22 you must have just one fedora-release $ more /etc/fedora-release Fedora release 21 (Twenty One) $ su -c 'yum --releasever=21 distro-sync' or just if system already assume that is 21 $ su -c 'yum distro-sync' > > > >> fedora-repos-21-0.5.noarch > >> paket fedora-rawhide-repos är inte installerat > >> $ > >> > >>> > >>> kevin > >>> > >>> > >>> > >> > >> > >> -- > >> Regards > >> > >> Jon Ingason > > > > > -- > Regards > > Jon Ingason > -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Re: Problem with update after branching Rawhide to F21
On Monday 28 July 2014 00:06:52 Jon Ingason wrote: > Did that but did not help. > > Found that fedora-release-22-0-4.noarch was installed an remove it. Then > I could run yum update, but there was lot of f22 package still > installed. Need find way to remove them later. How about yum distro-sync Regards, -- José Abílio -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
2014-07-27 23:36, Sérgio Basto skrev: > On Dom, 2014-07-27 at 23:31 +0200, Jon Ingason wrote: >> 2014-07-27 21:50, Kevin Fenzi skrev: >>> On Sun, 27 Jul 2014 18:24:16 +0200 >>> Jon Ingason wrote: >>> I follow the Rawhide wiki how to branch Rawhide to Fedora 21. What I did was that I installed Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with libvirt. Then I clone it and used it to do the brancing. >>> >>> ...snip... >>> What does that mean? How can I fix this? >>> >>> What does: >>> >>> rpm -q fedora-release fedora-repos fedora-repos-rawhide >>> >>> output? >> >> $ rpm -q fedora-realese fedora-repos fedora-rawhide-repos >> paket fedora-realese är inte installerat >> fedora-repos-22-0.1.noarch > > you need remove fedora-repos-22-0.1.noarch , at least > > yum remove fedora-repos-22-0.1.noarch Did that but did not help. Found that fedora-release-22-0-4.noarch was installed an remove it. Then I could run yum update, but there was lot of f22 package still installed. Need find way to remove them later. > >> fedora-repos-21-0.5.noarch >> paket fedora-rawhide-repos är inte installerat >> $ >> >>> >>> kevin >>> >>> >>> >> >> >> -- >> Regards >> >> Jon Ingason > -- Regards Jon Ingason -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
On Dom, 2014-07-27 at 23:31 +0200, Jon Ingason wrote: > 2014-07-27 21:50, Kevin Fenzi skrev: > > On Sun, 27 Jul 2014 18:24:16 +0200 > > Jon Ingason wrote: > > > >> I follow the Rawhide wiki how to branch Rawhide to Fedora 21. > >> What I did was that I installed > >> Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with > >> libvirt. Then I clone it and used it to do the brancing. > > > > ...snip... > > > >> What does that mean? How can I fix this? > > > > What does: > > > > rpm -q fedora-release fedora-repos fedora-repos-rawhide > > > > output? > > $ rpm -q fedora-realese fedora-repos fedora-rawhide-repos > paket fedora-realese är inte installerat > fedora-repos-22-0.1.noarch you need remove fedora-repos-22-0.1.noarch , at least yum remove fedora-repos-22-0.1.noarch > fedora-repos-21-0.5.noarch > paket fedora-rawhide-repos är inte installerat > $ > > > > > kevin > > > > > > > > > -- > Regards > > Jon Ingason -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
2014-07-27 21:24, Sérgio Basto skrev: > On Dom, 2014-07-27 at 18:24 +0200, Jon Ingason wrote: >> I follow the Rawhide wiki how to branch Rawhide to Fedora 21. >> What I did was that I installed >> Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with libvirt. >> Then I clone it and used it to do the brancing. >> >> I did following: >> >> $ su -c 'yum-config-manager --disable rawhide' >> $ su -c 'yum-config-manager --enable fedora,updates,updates-testing' >> $ su -c 'yum --releasever=(version) distro-sync' >> >> $ more /etc/fedora-release >> Fedora release 21 (Twenty One) >> >> Then I tested to do update with following results: >> >> $ sudo yum update >> [sudo] password for user: >> Inlästa insticksmoduler: langpacks >> fedora/22/x86_64/metalink | 29 kB >> 00:00 >> Could not parse metalink >> https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64 >> error was >> No repomd file > > (...) > >> What does that mean? How can I fix this? > > mean that some var environments , thinks that the relversion is 22 , > logout and login or more drastically, reboot, should solve the > problem . > No, reboot did not solv this problem. -- Regards Jon Ingason -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
2014-07-27 21:50, Kevin Fenzi skrev: > On Sun, 27 Jul 2014 18:24:16 +0200 > Jon Ingason wrote: > >> I follow the Rawhide wiki how to branch Rawhide to Fedora 21. >> What I did was that I installed >> Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with >> libvirt. Then I clone it and used it to do the brancing. > > ...snip... > >> What does that mean? How can I fix this? > > What does: > > rpm -q fedora-release fedora-repos fedora-repos-rawhide > > output? $ rpm -q fedora-realese fedora-repos fedora-rawhide-repos paket fedora-realese är inte installerat fedora-repos-22-0.1.noarch fedora-repos-21-0.5.noarch paket fedora-rawhide-repos är inte installerat $ > > kevin > > > -- Regards Jon Ingason -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] 2014-07-28 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2014-07-28 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We haven't met for a while, and there's been a big F21 slip, so let's get together and see where we are with F21, Flock, Taskotron deployment and any other topics anyone has to bring up! Same bat time, same bat channel. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 21 status 3. Taskotron deployment 4. Flock 5. Open floor -- 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 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
On Sun, 27 Jul 2014 18:24:16 +0200 Jon Ingason wrote: > I follow the Rawhide wiki how to branch Rawhide to Fedora 21. > What I did was that I installed > Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with > libvirt. Then I clone it and used it to do the brancing. ...snip... > What does that mean? How can I fix this? What does: rpm -q fedora-release fedora-repos fedora-repos-rawhide output? kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Problem with update after branching Rawhide to F21
On Dom, 2014-07-27 at 18:24 +0200, Jon Ingason wrote: > I follow the Rawhide wiki how to branch Rawhide to Fedora 21. > What I did was that I installed > Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with libvirt. > Then I clone it and used it to do the brancing. > > I did following: > > $ su -c 'yum-config-manager --disable rawhide' > $ su -c 'yum-config-manager --enable fedora,updates,updates-testing' > $ su -c 'yum --releasever=(version) distro-sync' > > $ more /etc/fedora-release > Fedora release 21 (Twenty One) > > Then I tested to do update with following results: > > $ sudo yum update > [sudo] password for user: > Inlästa insticksmoduler: langpacks > fedora/22/x86_64/metalink | 29 kB > 00:00 > Could not parse metalink > https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64 > error was > No repomd file (...) > What does that mean? How can I fix this? mean that some var environments , thinks that the relversion is 22 , logout and login or more drastically, reboot, should solve the problem . -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Torvalds & GCC 4.9
On Sun, Jul 27, 2014 at 05:14:33PM +0100, Sérgio Basto wrote:
> > This bug is fixed in gcc-4.9.1-2.fc{21,22} already, and given that it has
> > been reported only after a few years since the bug has been introduced, it
> > is not very likely to trigger on other code.
>
> So, we should do a new mass rebuild for gcc on F21 branch and rawhide !
Why? There were at least 15 wrong-code bugs in GCC fixed in between the 4.9.0
and 4.9.1 releases. If we had to rebuild for every one, we'd be constantly
rebuilding things. Normally we only rebuild packages that are known to be
miscompiled.
Jakub
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Problem with update after branching Rawhide to F21
I follow the Rawhide wiki how to branch Rawhide to Fedora 21. What I did was that I installed Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with libvirt. Then I clone it and used it to do the brancing. I did following: $ su -c 'yum-config-manager --disable rawhide' $ su -c 'yum-config-manager --enable fedora,updates,updates-testing' $ su -c 'yum --releasever=(version) distro-sync' $ more /etc/fedora-release Fedora release 21 (Twenty One) Then I tested to do update with following results: $ sudo yum update [sudo] password for user: Inlästa insticksmoduler: langpacks fedora/22/x86_64/metalink | 29 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64 error was No repomd file One of the configured repositories failed (Okänd), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true File /var/cache/yum/x86_64/22/fedora/metalink.xml does not exist $ What does that mean? How can I fix this? -- Regards Jon Ingason -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Torvalds & GCC 4.9
On Dom, 2014-07-27 at 09:11 +0200, Jakub Jelinek wrote:
> On Sat, Jul 26, 2014 at 11:32:49PM -0700, Chuck Forsberg WA7KGX wrote:
> > Phoeonix.com is reporting that Linus has found a code generation
> > error in 4.9 and has switched back to 4.8.
>
> The bug existed from 4.5.0 up, so switching back to 4.8 is a weird
> solution.
>
> > Since Fedora has been including 4.9 in F21 for some time,
> > one would like to know which compiler is used for compiling F21.
>
> This bug is fixed in gcc-4.9.1-2.fc{21,22} already, and given that it has
> been reported only after a few years since the bug has been introduced, it
> is not very likely to trigger on other code.
So, we should do a new mass rebuild for gcc on F21 branch and rawhide !
> > Caould some of the strange problems I've seen with F21 be
> > caused by GCC 2.9 code generation error(s)???
>
> Have you filed bugs if you suspect gcc problems?
>
> Jakub
--
Sérgio M. B.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
screen to USB serial not working today
So I go away for a day and come back to test with the latest and all typing into sreen program is coming up garbage characters. I have tried stopping are restarting screen. I have unplugged are replugged the usb. No difference. Still garbage characters. any recommendations? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Torvalds & GCC 4.9
On Sun, Jul 27, 2014 at 11:36 AM, Chuck Forsberg WA7KGX wrote:
>
> On 07/27/2014 12:11 AM, Jakub Jelinek wrote:
>>
>> On Sat, Jul 26, 2014 at 11:32:49PM -0700, Chuck Forsberg WA7KGX wrote:
>>>
>>> Phoeonix.com is reporting that Linus has found a code generation
>>> error in 4.9 and has switched back to 4.8.
>>
>> The bug existed from 4.5.0 up, so switching back to 4.8 is a weird
>> solution.
>>
>>> Since Fedora has been including 4.9 in F21 for some time,
>>> one would like to know which compiler is used for compiling F21.
>>
>> This bug is fixed in gcc-4.9.1-2.fc{21,22} already, and given that it has
>> been reported only after a few years since the bug has been introduced, it
>> is not very likely to trigger on other code.
>>
>>> Caould some of the strange problems I've seen with F21 be
>>> caused by GCC 2.9 code generation error(s)???
>>
>> Have you filed bugs if you suspect gcc problems?
>>
>> Jakub
>
> I have not seen GCC related bugs in the software I wrote,
> but then my usage of C is not very subtle.
>
> I was wondering if some of the recent problems which come and go, such as
> installs with anything but Gnome failing to boot to a desktop.
> Saturday's rsync had this problem, Friday's was OK in this respect.
Well bugs happens in pretty much anything ... just blaming the
compiler is a bit premature.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
F-21 Branched report: 20140727 changes
Compose started at Sun Jul 27 07:15:02 UTC 2014 Broken deps for armhfp -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [PyKDE] PyKDE-3.16.6-14.fc20.armv7hl requires sip-api(10) >= 0:10.0 [audtty] audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0 [csound] csound-java-5.19.01-1.fc20.armv7hl requires libgcj_bc.so.1 csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat csound-java-5.19.01-1.fc20.armv7hl requires java-1.5.0-gcj csound-tk-5.19.01-1.fc20.armv7hl requires libtk8.5.so csound-tk-5.19.01-1.fc20.armv7hl requires libtcl8.5.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [dragonegg] dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [eclipse-jbosstools] eclipse-jbosstools-jst-4.1.1-2.fc21.noarch requires eclipse-wtp-jst-web eclipse-jbosstools-ws-4.1.1-2.fc21.noarch requires osgi(org.eclipse.jst.ws.annotations.core) [edelib] edelib-2.1-4.fc21.armv7hl requires libedelib.so edelib-devel-2.1-4.fc21.armv7hl requires libedelib.so [eucalyptus] eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl requires hibernate3-jbosscache >= 0:3.6.10-7 [fatrat] 1:fatrat-1.2.0-0.20.beta2.fc21.armv7hl requires libgloox.so.11 [flashrom] flashrom-0.9.6.1-5.svn1705.fc20.armv7hl requires libftdi.so.1 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires libpython3.3dm.so.1.0 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0 gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires libvala-0.24.so.0 [gnome-python2-desktop] gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires libmetacity-private.so.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0 [golang-github-smarterclayton-go-systemd] golang-github-smarterclayton-go-systemd-devel-0-0.5.git5cb9e9e.fc21.noarch requires golang(github.com/guelfey/go.dbus) [grass] grass-6.4.3-5.fc21.armv7hl requires libtk8.5.so grass-6.4.3-5.fc21.armv7hl requires libtcl8.5.so [hibernate-search] hibernate-search-4.5.1-4.fc21.noarch requires mvn(org.apache.avro:avro) [ice] ice-php-3.5.1-4.fc21.armv7hl requires php(zend-abi) = 0:20121212-32 ice-php-3.5.1-4.fc21.armv7hl requires php(api) = 0:20121113-32 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [libghemical] libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3 libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1 [licq] licq-1.8.2-1.fc21.armv7hl requires libgloox.so.11 [ltsp] ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog [mapserver] mapserver-java-6.2.1-7.fc21.armv7hl requires java-gcj-compat [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala < 0:0.25.0 [mypaint] mypaint-devel-1.1.0-2.fc21.armv7hl requires pkgconfig(json) [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [openvas-client] openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_omp.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_nasl.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_misc.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_hg.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_base.so.6 [orsa] orsa-0.7.0-28.fc21.armv7hl requires libginac.so.2 orsa-mpich-0.7.0-28.fc21.armv7hl requires libginac.so.2 orsa-openmpi-0.7.0-28.fc21.armv7hl requires libginac.so.2 [php-pecl-parsekit] php-pecl-parsekit-1.3.0-5.fc21.armv7hl requires php(zend-abi) = 0:20121212-32 php-pecl-parsekit-1.3.0-5.fc21.armv7hl requires php(api) = 0:20121113-32 [qgis] qgis-2.2.0-4.fc21.armv7hl requires libspatialite.so.5 qgis-grass-2.2.0-4.fc21.armv7hl requires libspatialite.so.5 qgis-maps
Re: Torvalds & GCC 4.9
On 07/27/2014 12:11 AM, Jakub Jelinek wrote:
On Sat, Jul 26, 2014 at 11:32:49PM -0700, Chuck Forsberg WA7KGX wrote:
Phoeonix.com is reporting that Linus has found a code generation
error in 4.9 and has switched back to 4.8.
The bug existed from 4.5.0 up, so switching back to 4.8 is a weird
solution.
Since Fedora has been including 4.9 in F21 for some time,
one would like to know which compiler is used for compiling F21.
This bug is fixed in gcc-4.9.1-2.fc{21,22} already, and given that it has
been reported only after a few years since the bug has been introduced, it
is not very likely to trigger on other code.
Caould some of the strange problems I've seen with F21 be
caused by GCC 2.9 code generation error(s)???
Have you filed bugs if you suspect gcc problems?
Jakub
I have not seen GCC related bugs in the software I wrote,
but then my usage of C is not very subtle.
I was wondering if some of the recent problems which come and go, such as
installs with anything but Gnome failing to boot to a desktop.
Saturday's rsync had this problem, Friday's was OK in this respect.
--
Chuck Forsberg WA7KGX c...@omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: Torvalds & GCC 4.9
On Sat, Jul 26, 2014 at 11:32:49PM -0700, Chuck Forsberg WA7KGX wrote:
> Phoeonix.com is reporting that Linus has found a code generation
> error in 4.9 and has switched back to 4.8.
The bug existed from 4.5.0 up, so switching back to 4.8 is a weird
solution.
> Since Fedora has been including 4.9 in F21 for some time,
> one would like to know which compiler is used for compiling F21.
This bug is fixed in gcc-4.9.1-2.fc{21,22} already, and given that it has
been reported only after a few years since the bug has been introduced, it
is not very likely to trigger on other code.
> Caould some of the strange problems I've seen with F21 be
> caused by GCC 2.9 code generation error(s)???
Have you filed bugs if you suspect gcc problems?
Jakub
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
