Fedora 18 updates-testing report
The following Fedora 18 Security updates need testing: Age URL 199 https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18 45 https://admin.fedoraproject.org/updates/FEDORA-2013-17195/spice-gtk-0.18-3.fc18 42 https://admin.fedoraproject.org/updates/FEDORA-2013-17431/thunderbird-17.0.9-1.fc18 39 https://admin.fedoraproject.org/updates/FEDORA-2013-17635/wireshark-1.10.2-4.fc18 38 https://admin.fedoraproject.org/updates/FEDORA-2013-17853/davfs2-1.4.7-3.fc18 37 https://admin.fedoraproject.org/updates/FEDORA-2013-17912/chicken-4.8.0.4-4.fc18 26 https://admin.fedoraproject.org/updates/FEDORA-2013-18647/gnupg-1.4.15-1.fc18 25 https://admin.fedoraproject.org/updates/FEDORA-2013-18802/phpMyAdmin-3.5.8.2-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20200/python-backports-ssl_match_hostname-3.4.0.2-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20176/mantis-1.2.15-3.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-20360/spice-0.12.4-3.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-20410/poppler-0.20.2-17.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-20429/xulrunner-25.0-2.fc18,firefox-25.0-3.fc18 1 https://admin.fedoraproject.org/updates/FEDORA-2013-20544/xen-4.2.3-7.fc18 The following Fedora 18 Critical Path updates have yet to be approved: Age URL 268 https://admin.fedoraproject.org/updates/FEDORA-2013-2192/nautilus-3.6.3-5.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20263/openssl-1.0.1e-30.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20268/sane-backends-1.0.24-4.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20279/gnome-abrt-0.3.3-1.fc18,abrt-2.1.9-1.fc18,libreport-2.1.9-1.fc18,satyr-0.11-1.fc18 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20150/nss-util-3.15.2-2.fc18,nss-softokn-3.15.2-2.fc18,nss-3.15.2-2.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-20434/thunderbird-24.1.0-1.fc18,thunderbird-lightning-2.6.2-2.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-20422/bind-9.9.3-7.P2.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-20410/poppler-0.20.2-17.fc18 The following builds have been pushed to Fedora 18 updates-testing VirtualGL-2.3.3-1.fc18 ardour3-3.5.14-1.fc18 cdm-0.5.3-13.fc18 chmsee-2.0.2-4.git86d101c9.fc18 epson-inkjet-printer-escpr-1.3.0-1.1lsb3.2.fc18 gfal2-python-1.3.0-1.fc18 gimp-2.8.8-1.fc18 libltc-1.1.2-1.fc18 libreswan-3.6-1.fc18 libsigrok-0.2.2-1.fc18 opendkim-2.8.4-4.fc18 pynag-0.7.0-1.fc18 python-jira-0.13-2.fc18 python-pkgwat-api-0.10-2.fc18 python-twiggy-0.4.5-2.fc18 youtube-dl-2013.11.02-1.fc18 Details about builds: VirtualGL-2.3.3-1.fc18 (FEDORA-2013-20616) A toolkit for displaying OpenGL applications to thin clients Update Information: Update to version 2.3.3. Fixes launching setuid root binaries in VGL. ChangeLog: * Sat Nov 2 2013 Gary Gatling - 2.3.3-1 - Update to 2.3.3. * Tue Aug 6 2013 Gary Gatling - 2.3.2-7 - Fix (#993894) unversioned docdir change for f20. * Sat Aug 3 2013 Fedora Release Engineering - 2.3.2-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild ardour3-3.5.14-1.fc18 (FEDORA-2013-20148) Digital Audio Workstation Update Information: Add ardour v3.x and libltc to Fedora. References: [ 1 ] Bug #1022255 - Review Request: libltc - Linear/Longitudinal Time Code (LTC) Library https://bugzilla.redhat.com/show_bug.cgi?id=1022255 [ 2 ] Bug #1007099 - Review Request: ardour3 - Digital Audio Workstation https://bugzilla.redhat.com/show_bug.cgi?id=1007099 cdm-0.5.3-13.fc18 (FEDORA-2013-20624) Very minimalistic login manager Update Information: Resurrecting CDM broken by xorg-x11-xinit changes introduced with systemd-logind - making at least the basic mode working. NOTE for testers: Don't forget to install the particular WM sessions before choosing them. ChangeLog: * Thu Oct 31 2013 Jaromir Capik - 0.5.3-
Re: Self-introduction: Ricardo Varas
On Mon, 2013-11-04 at 21:54 -0300, Ricardo Varas Santana wrote: > Hello everyone, > > > My name is Ricardo, 32 years old living in Santiago de Chile. > > I've been a Linux user since 2006 or so, and my contributions to the > Linux world have been related to KDE and openSUSE pretty much under > translation, marketing and a few of bug triage. Of course I can build > packages from source, know my way around repos, use of bugzilla, etc. > > Now I am moving on and, I really have no doubt I would love to join > the Fedora Project and focus on GNOME. I'll be glad to be part of the > Fedora QA Team in particular, and looking forward to it. Welcome Ricardo, thanks for joining! Let us know if you have questions or need help of any kind :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: GNOME Shell freeze
On Sat, 2013-11-02 at 18:54 -0600, Mike Ruckman wrote: > On Sat, 2 Nov 2013 17:19:30 +0100 > Michael Schwendt wrote: > > > On Sat, 02 Nov 2013 16:06:15 +0100, Noah Menzi wrote: > > > > > On 02.11.2013 13:14, Michael Schwendt wrote: > > > > Is this reproducible by anyone? > > > > > > > > 1. open a single gnome-terminal > > > > 2. log in as root via "su -" > > > > 3. run gedit > > > > 4. try to open gedit's Preferences via the application specific > > > > menu displayed on the top panel (does it open? here, it doesn't) > > > > 5. try to trigger the "Activities" hotspot with the mouse > > > > > > > > What happens? Here the desktop freezes completely. One can still > > > > move the mouse, but that's all. Killing gedit and gnome-terminal > > > > doesn't achieve anything. If killing more processes, eventually > > > > the "Oh no..." screen appears, but upon trying to log back in at > > > > GDM, the desktop doesn't load. > > > I can reproduce this bug. > > > On my Fedora 19 it doesn't open the application specific menu of > > > gedit, but gnome doesn't freeze. > > > On my Fedora 20 it doesn't open the application specific menu and > > > the gnome desktop freezes completely. I can still move the mouse > > > too. > > > > Among the more than 700 gnome-shell bugs in Fedora bugzilla, I've > > found > > > > https://bugzilla.redhat.com/956306 > > > > which exists since 2013-04-24 and is for Fedora 18. Since it has not > > been responded to by a maintainer, what would be the normal > > procedure? To open a new ticket for Fedora 20? > > Go ahead and file a bug - this will help for tracking and the worst > case scenario is it will merely be marked as a duplicate. You've > already documented the steps to reproduce, so most of the work of > filing a bug is already done :) There's no right answer to the question, as there's no official policy for handling bugs that affect multiple releases in Fedora's Bugzilla, and indeed no good way of doing it: the way we abuse Bugzilla, we just don't have a field that is capable of indicating 'affects all these releases'. So different reporters, maintainers, and components handle it differently; frequently the same person will handle it differently in different cases. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: automatic promotion of freeze exceptions?
On Sat, 2013-11-02 at 14:52 +, Andre Robatino wrote: > Do we or should we have a policy of automatically promoting unfixed freeze > exceptions from Alpha to Beta, or Beta to Final? The concept doesn't make > sense for blockers, since those have to be fixed at each stage before going > to the next, but FEs don't. This comes up every so often, but there isn't an explicit policy either way. In practice it does not happen because there is no process or automated mechanism to make it happen. > On a related note, I've noticed a tendency in blocker meetings to ask > reporters to repropose bugs as blockers for later stages. I thought it had > been decided that when reasonable, that should be done immediately when > blockers are rejected, so they don't fall through the cracks. When I do secretarialization I tend to go ahead and 'just do it' when there was a clear agreement at the meeting that it should happen, yeah. I'd say that should be part of the secretarialization stuff. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Self-introduction: Ricardo Varas
Welcome Ricardo. I joined the Fedora Project a few months ago and the community was very friendly and welcoming. This is the first community that I've every joined, so I don't have a point of comparison, but I can't imagine any other community being better. I have no regrets about choosing to join the Fedora Project. I just wanted to wish you luck and I hope you have as good an experience as I did. On Mon, 2013-11-04 at 21:54 -0300, Ricardo Varas Santana wrote: > Hello everyone, > > > My name is Ricardo, 32 years old living in Santiago de Chile. > > I've been a Linux user since 2006 or so, and my contributions to the > Linux world have been related to KDE and openSUSE pretty much under > translation, marketing and a few of bug triage. Of course I can build > packages from source, know my way around repos, use of bugzilla, etc. > > Now I am moving on and, I really have no doubt I would love to join > the Fedora Project and focus on GNOME. I'll be glad to be part of the > Fedora QA Team in particular, and looking forward to it. > > Contact info as follows: > > > > IRC: rvaras > > Twitter: ricardovs > Gmail: You already have it :) > > > Best Regards. > > -- > Ricardo Varas Santana -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: system question
On Sun, 2013-10-27 at 09:23 -0700, Richard Vickery wrote: > Hi Gang: > > > I called journalctl and got two lines that sparked a question: > > > Parsing /etc/bluetooth/input.conf failed: No such file or directory > > > Oct 17 15:17:36 localhost.localdomain bluetoothd[502]: > Parsing /etc/bluetooth/serial.conf failed: No such file or directory > > > Should I be creating a bluetooth directory and perhaps touching the > files: input.conf and serial.conf? In general, no. It's pretty common for code to do something if a file exists, but just go ahead 'as usual' if it doesn't; this kind of message doesn't necessarily mean anything is wrong. I would only start doing that kind of thing if there was obviously something wrong with Bluetooth functionality, and research indicated that these files being 'missing' might have something to do with it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Self-introduction: Ricardo Varas
Hello everyone, My name is Ricardo, 32 years old living in Santiago de Chile. I've been a Linux user since 2006 or so, and my contributions to the Linux world have been related to KDE and openSUSE pretty much under translation, marketing and a few of bug triage. Of course I can build packages from source, know my way around repos, use of bugzilla, etc. Now I am moving on and, I really have no doubt I would love to join the Fedora Project and focus on GNOME. I'll be glad to be part of the Fedora QA Team in particular, and looking forward to it. Contact info as follows: IRC: rvaras Twitter: ricardovs Gmail: You already have it :) Best Regards. -- Ricardo Varas Santana -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Should we update our bug reporting procedures/process ?
On Mon, 2013-11-04 at 12:32 +, "Jóhann B. Guðmundsson" wrote: > On 11/04/2013 10:37 AM, Alexander Todorov wrote: > > На 1.11.2013 21:03, moshe nahmias написа: > >> I think that some of the problem is that you have to register to file a > >> bug. There is no reason to register if you just want the developer to > >> know > >> there is a bug and from then on no interaction unless needed. > > > > > > How about enabling login(register) via social networking sites ? AFAIK > > all of them but LinkedIn and Twitter make it easy to access the > > account name and email. Registering will be as simple as clicking on a > > button to let you in. > > I'm pretty sure the security team as well as RH bugzilla admin will > frown upon that. Right. This is ultimately a well-known pain point we've had for years. Sharing a bug tracking system with almost all RH products leads to various compromises. There are choices we might want to make for Fedora bug reporting which we can't make in a system shared with a bunch of RH products, which includes all of the stuff discussed so far in this thread and the comment thread, including sign-up-free-submission, more simple submission, and SSO. We would love to have SSO to Bugzilla with your FAS credentials, but AIUI it is basically impossible as long as we're operating on the BZ instance shared with RH. However, the RH shared BZ is not _enough_ of a pain point that anyone's willing to make a plausible case for replacing it with an entirely separate Fedora-specific bug tracker, which would be a massive amount of work. It's clear that some benefits would accrue from doing so, but no-one has been able to make the case to any entity with the resources to actually do it that it would be worth their while investing those resources in that project. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 20 updates-testing report
The following Fedora 20 Security updates need testing: Age URL 36 https://admin.fedoraproject.org/updates/FEDORA-2013-17866/chicken-4.8.0.4-4.fc20 25 https://admin.fedoraproject.org/updates/FEDORA-2013-18705/phpMyAdmin-3.5.8.2-1.fc20 17 https://admin.fedoraproject.org/updates/FEDORA-2013-19198/quassel-0.9.1-1.fc20 10 https://admin.fedoraproject.org/updates/FEDORA-2013-19931/mod_nss-1.0.8-24.fc20 10 https://admin.fedoraproject.org/updates/FEDORA-2013-19934/openstack-glance-2013.2-2.fc20 6 https://admin.fedoraproject.org/updates/FEDORA-2013-20138/mantis-1.2.15-3.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2013-20216/python-setuptools-0.9.8-2.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2013-19507/openstack-keystone-2013.2-2.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2013-20517/xen-4.3.1-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-20566/kernel-3.11.6-302.fc20 The following Fedora 20 Critical Path updates have yet to be approved: Age URL 11 https://admin.fedoraproject.org/updates/FEDORA-2013-19861/libcomps-0.1.4-4.fc20 11 https://admin.fedoraproject.org/updates/FEDORA-2013-19854/lua-5.2.2-5.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2013-20219/perl-Socket-2.013-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2013-20216/python-setuptools-0.9.8-2.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2013-20406/dnf-0.4.6-1.fc20,libsolv-0.4.0-1.gitd49d319.fc20,librepo-1.3.0-1.fc20,hawkey-0.4.4-1.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2013-20393/phonon-4.6.0-9.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2013-20475/libevdev-0.4.1-1.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2013-20450/pungi-3.03-1.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2013-20466/thunderbird-24.1.0-1.fc20,thunderbird-lightning-2.6.2-2.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2013-20513/xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2013-20522/highlight-3.16.1-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-20610/soprano-2.9.4-2.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-20596/gupnp-0.20.8-1.fc20,gssdp-0.14.6-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-20573/iso-codes-3.48-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-20566/kernel-3.11.6-302.fc20 The following builds have been pushed to Fedora 20 updates-testing audacious-3.4.2-2.fc20 audacious-plugins-3.4.2-1.fc20 cdm-0.5.3-13.fc20 cego-2.19.11-1.fc20 chmsee-2.0.2-4.git86d101c9.fc20 codeblocks-12.11-2.fc20 copr-1.12-1.fc20 cups-1.7.0-4.fc20 epson-inkjet-printer-escpr-1.3.0-1.1lsb3.2.fc20 fence-virt-0.3.1-1.fc20 gimp-2.8.8-1.fc20 gssdp-0.14.6-1.fc20 gupnp-0.20.8-1.fc20 imagej-1.48-1.e.fc20 kipi-plugins-elegant-theme-1.4.0-2.fc20 langtable-0.0.18-1.fc20 lfcbase-1.5.8-1.fc20 libguestfs-1.24.1-1.fc20 libreswan-3.6-1.fc20 libsigrok-0.2.2-1.fc20 licq-1.8.1-1.fc20 opendkim-2.8.4-4.fc20 ovaldi-5.9.1-8.fc20 perl-DB_File-1.830-1.fc20 perl-Perl-Critic-1.121-1.fc20 perl-Rose-DB-0.774-1.fc20 perl-Rose-DB-Object-0.808-1.fc20 php-phpunit-File-Iterator-1.3.4-1.fc20 python-jira-0.13-2.fc20 python-pkgwat-api-0.10-2.fc20 python-twiggy-0.4.5-2.fc20 rrdtool-1.4.8-7.fc20 rubygem-bourne-1.5.0-2.fc20 rubygem-foreman_api-0.1.8-1.fc20 soprano-2.9.4-2.fc20 syslog-ng-3.4.5-1.fc20 wt-3.3.1-0.1.rc1.fc20 xmp-plugin-audacious-4.0.0-0.3.e0213c0.fc20 Details about builds: audacious-3.4.2-2.fc20 (FEDORA-2013-20609) Advanced audio player Update Information: Update from 3.4.1 to 3.4.2. Includes bug-fixes for upstream tickets #340, #346, #347, #356, #360, and #362. http://audacious-media-player.org/ ChangeLog: * Sun Nov 3 2013 Michael Schwendt - 3.4.2-2 - Create and install a preliminary AppData file (for upstream #349). * Sun Nov 3 2013 Dan Fruehauf - 3.4.2-1 - Update to 3.4.2 final (fixes bugs 340, 346, 347, 356, 360, and 362). audacious-plugins-3.4.2-1.fc20 (FEDORA-2013-20609) Plugins for the Audacious audio player Update Information: Update from 3.4.1 to 3.4.2. Includes bug-fixes for u
Printing Test Day tomorrow (Tuesday 2013-11-05)
The Printing Test Day for Fedora 20 is Tuesday of this week. https://fedoraproject.org/wiki/Test_Day:2013-11-05_Printing This test day is for testing all aspects of printing, including setting up the printer, sharing printers on the network, and printing jobs. The changes in Fedora 20 are relatively minor: switching to CUPS 1.7 and Ghostscript 9.10, and some improvements to cups-filters and the "Printers" part of GNOME Settings. Remember that CUPS unit testing is only one small part of the story: printing is very much in need of integration testing. Try printing with different applications, using options you don't normally use in the print dialog. Try to see how many different ways you can break it! If you have access to a printer and a machine running Fedora 20 (a live CD is fine), please join in! We'll be on IRC at the usual place: irc://irc.freenode.net/fedora-test-day Tim. */ signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20131104 changes
Compose started at Mon Nov 4 08:15:03 UTC 2013 Broken deps for i386 -- [OpenEXR_CTL] OpenEXR_CTL-1.0.1-16.fc20.i686 requires libImath.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmThread.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmImf.so.7 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIexMath.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIex.so.6 OpenEXR_CTL-1.0.1-16.fc20.i686 requires libHalf.so.6 OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIlmThread.so.6 OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIlmImf.so.7 OpenEXR_CTL-libs-1.0.1-16.fc20.i686 requires libIex.so.6 [R-RScaLAPACK] R-RScaLAPACK-0.6.1-13.fc20.i686 requires libatlas.so.3 [blueman] blueman-1.23-7.fc20.i686 requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.i686 requires gvfs-obexftp [cinnamon-control-center] cinnamon-control-center-2.0.5-1.fc21.i686 requires libupower-glib.so.1 [cinnamon-session] cinnamon-session-2.0.1-1.fc21.i686 requires libupower-glib.so.1 [cinnamon-settings-daemon] cinnamon-settings-daemon-2.0.5-1.fc21.i686 requires libupower-glib.so.1 cinnamon-settings-daemon-devel-2.0.5-1.fc21.i686 requires libupower-glib.so.1 [codeblocks] codeblocks-contrib-12.11-1.fc21.i686 requires [converseen] converseen-0.6.2-2.fc20.i686 requires libMagick++-6.Q16.so.1 [cp2k] cp2k-2.4-6.fc20.i686 requires libf77blas.so.3 cp2k-2.4-6.fc20.i686 requires libatlas.so.3 cp2k-mpich-2.4-6.fc20.i686 requires libf77blas.so.3 cp2k-openmpi-2.4-6.fc20.i686 requires libf77blas.so.3 [derelict] derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod [drawtiming] drawtiming-0.7.1-11.fc20.i686 requires libMagick++-6.Q16.so.1 [ekiga] ekiga-4.0.1-6.fc20.i686 requires libcamel-1.2.so.45 [evolution-mapi] evolution-mapi-3.10.1-1.fc21.i686 requires libcamel-1.2.so.45 [evolution-rss] 1:evolution-rss-0.3.94-1.fc21.i686 requires libcamel-1.2.so.45 [fatrat] 1:fatrat-1.2.0-0.14.beta2.fc20.i686 requires liblog4cpp.so.4 [freefem++] freefem++-3.19-3.1.fc18.i686 requires libf77blas.so.3 freefem++-3.19-3.1.fc18.i686 requires libcblas.so.3 freefem++-3.19-3.1.fc18.i686 requires libatlas.so.3 freefem++-glx-3.19-3.1.fc18.i686 requires libf77blas.so.3 freefem++-glx-3.19-3.1.fc18.i686 requires libcblas.so.3 freefem++-glx-3.19-3.1.fc18.i686 requires libatlas.so.3 freefem++-mpi-3.19-3.1.fc18.i686 requires libf77blas.so.3 freefem++-mpi-3.19-3.1.fc18.i686 requires libcblas.so.3 freefem++-mpi-3.19-3.1.fc18.i686 requires libatlas.so.3 [gnome-packagekit] gnome-packagekit-3.10.1-1.fc21.i686 requires libupower-glib.so.1 gnome-packagekit-installer-3.10.1-1.fc21.i686 requires libupower-glib.so.1 gnome-packagekit-updater-3.10.1-1.fc21.i686 requires libupower-glib.so.1 [gnome-power-manager] gnome-power-manager-3.10.1-1.fc21.i686 requires libupower-glib.so.1 [gradle] gradle-1.0-18.fc20.noarch requires plexus-container-default [gtkd] gtkd-2.0.0-29.20120815git9ae9181.fc18.i686 requires libphobos-ldc.so.60 [httpdtap] httpdtap-0.2-2.fc21.noarch requires kernel-debuginfo httpdtap-0.2-2.fc21.noarch requires httpd-debuginfo httpdtap-0.2-2.fc21.noarch requires apr-util-debuginfo httpdtap-0.2-2.fc21.noarch requires apr-debuginfo [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kxstitch] kxstitch-0.8.4.1-16.fc20.i686 requires libMagick++-6.Q16.so.1 [kyua-cli] kyua-cli-0.5-3.fc19.i686 requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.i686 requires liblutok.so.0 [libghemical] libghemical-2.99.1-24.fc20.i686 requires libf77blas.so.3 libghemical-2.99.1-24.fc20.i686 requires libatlas.so.3 [libopensync-plugin-evolution2] 1:libopensync-plugin-evolution2-0.22-37.fc20.i686 requires libcamel-1.2.so.45 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.i686 requires libopenobex.so.1 [mate-power-manager] mate-power-manager-1.6.3-0.3.gitbc54d96.fc21.i686 requires libupower-glib.so.1 [mpqc] mpqc-2.3.1-23.fc20.i686 requires libf77blas.so.3 mpqc-2.3.1-23.fc20.i686 requires libatlas.so.3 [netdisco] netdisco-1.1-6.fc20.noarch requires perl(SNMP::Info::Layer2::Bay) [nifti2dicom] nifti2dicom-0.4.6-3.fc20.i686 requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkTextAnalysis
Re: Should we update our bug reporting procedures/process ?
On 11/04/2013 10:37 AM, Alexander Todorov wrote: На 1.11.2013 21:03, moshe nahmias написа: I think that some of the problem is that you have to register to file a bug. There is no reason to register if you just want the developer to know there is a bug and from then on no interaction unless needed. How about enabling login(register) via social networking sites ? AFAIK all of them but LinkedIn and Twitter make it easy to access the account name and email. Registering will be as simple as clicking on a button to let you in. I'm pretty sure the security team as well as RH bugzilla admin will frown upon that. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-20 Branched report: 20131104 changes
Compose started at Mon Nov 4 09:15:05 UTC 2013 Broken deps for armhfp -- [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [bwm-ng] bwm-ng-0.6-11.1.fc20.armv7hl requires libstatgrab.so.9 [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [condor-wallaby] condor-wallaby-client-5.0.3-4.fc20.noarch requires python-qmf >= 0:0.9.1073306 [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [glpi] glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Version glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Stdlib glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-ServiceManager glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Loader glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-I18n glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Cache-apc glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Cache [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 [gradle] gradle-1.0-18.fc20.noarch requires plexus-container-default [grass] grass-6.4.3-2.fc20.armv7hl requires libgeos-3.3.8.so grass-libs-6.4.3-2.fc20.armv7hl requires libgeos-3.3.8.so [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 [monotone] monotone-1.0-11.fc19.armv7hl requires libbotan-1.8.2.so perl-Monotone-1.0-11.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) [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 [osm2pgsql] osm2pgsql-0.82.0-1.fc20.armv7hl requires libgeos-3.3.8.so [oyranos] oyranos-libs-0.4.0-7.fc19.armv7hl requires libraw.so.5 [perl-BerkeleyDB] perl-BerkeleyDB-0.53-1.fc20.armv7hl requires libdb = 0:5.3.21 [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [perl-MIME-Lite-HTML] perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) [perl-Padre] perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) [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 [ruby-spqr] ruby-spqr-0.3.6-7.fc20.noarch requires ruby-qpid-qmf [rubygem-audited-activerecord] rubygem-audited-activerecord-3.0.0-3.fc19.noarch requires rubygem(activerecord) < 0:4 [rubygem-fog] rubygem-fog-1.11.1-1.fc20.noarch requires rubygem(nokogiri) < 0:1.6 [scala] scala-2.9.2-2.fc19
Re: Should we update our bug reporting procedures/process ?
На 1.11.2013 21:03, moshe nahmias написа: I think that some of the problem is that you have to register to file a bug. There is no reason to register if you just want the developer to know there is a bug and from then on no interaction unless needed. How about enabling login(register) via social networking sites ? AFAIK all of them but LinkedIn and Twitter make it easy to access the account name and email. Registering will be as simple as clicking on a button to let you in. -- Alex -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
