Re: Nightly Composes?
On 06/04/2012 07:02 PM, Kevin Fenzi wrote: > I usually wait a week or so around release, since I don't want people > looking for f17 to grab them. > > I'll update and look at doing a batch tomorrow. Anaconda newUI may be a significant customer of nightly builds for F18 rawhide. See https://fedoraproject.org/wiki/QA/Meetings/20120604 . Significant excerpts from QA minutes, recorded by Adam Williamson: + clumens plans to merge the new anaconda UI into Rawhide as soon as custom partitioning is implemented and broadly works. He estimates one month for that + If newUI lands in anaconda significantly before F18 branch point, we will ask releng to do rawhide nightlies until branching -- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
2012-05-14 - Fedora QA Meeting - recap
As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20120514 Next meeting was scheduled for 2012-05-21 at 1500 UTC in #fedora-meeting. TOPIC: Previous Meeting Follow-Up === * adamw followed up on GNOME boxes test day, event was not prepared in time so was pushed out another week, needs checking up again TOPIC: Fedora 17 Final Status/Planning === * See online minutes[1] for mini blocker review summary TOPIC: Upcoming QA Events === * GNOME Boxes Test Day on 2012-05-17[2] * Go/no-go scheduled for 2012-05-17 TOPIC: Pending Bugzilla upgrade === * Bugzilla upgrade scheduled for 2012-05-19 will break some stuff, waiting to find out how badly * libreport blocker filed for F17, will likely affect earlier releases * Blocker wiki page[3] will no longer work * Other scripts using python-bugzilla will likely not work after upgrade * Waiting on testing this week to find out how badly bodhi will be impacted * tflink will look into fixes for the broken tools after F17 is done TOPIC: AutoQA Update === * No news, due to F17 testing TOPIC: Open Floor === * nirik will be updating boot.fedoraproject.org for F17, he welcomes input and testing ACTION ITEMS === * j_dulaney to actually do his job and promote the GNOME boxes test day * adamw and tflink to check status of #810104 with TC5 * adamw to create some shared bugzilla searches for F17 final blocker/nth to replace the wiki page [1] http://meetbot.fedoraproject.org/fedora-meeting/2012-05-14/fedora-qa.2012-05-14-15.01.html [2] http://fedoraproject.org/wiki/Test_Day:2012-05-17_Gnome_Boxes [3] http://fedoraproject.org/wiki/Current_Release_Blockers -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nighlt-Composes?
On Tue, 5 Jun 2012 10:55:01 +1000 Amit Saha wrote: > On Tue, Jun 5, 2012 at 10:53 AM, Rob Healey > wrote: > > Greetings: > > > > I know that FC17 was just released a little while ago, but does > > anyone know when Nightly-Composes will be built upon fc18/ > > rawhide ??? > > This is where it usually should be [1]. But there seems that there > hasn't been any for a week now. I usually wait a week or so around release, since I don't want people looking for f17 to grab them. I'll update and look at doing a batch tomorrow. kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
2012-06-04 - Fedora QA Meeting - recap
As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20120604 Next meeting is scheduled for 2012-06-11 at 1500 UTC in #fedora-meeting. If you have topics you think we should bring up at the meeting, please add them to the Wiki page at https://fedoraproject.org/wiki/QA/Meetings/20120611 . Thanks! TOPIC: Previous meeting follow-up === N/A TOPIC: Fedora 18 planning === * Anaconda new UI: + clumens plans to merge the new anaconda UI into Rawhide as soon as custom partitioning is implemented and broadly works. He estimates one month for that + We don't believe QA can achieve much practical testing until that merge point, but we asked clumens to provide one or two public test images before then so testers can familiarize themselves with the new UI + Key areas of installer that provide much of the testable complexity are repository configuration, storage configuration and bootloader configuration + If newUI lands in anaconda significantly before F18 branch point, we will ask releng to do rawhide nightlies until branching * Fedora 17 retrospective tasks - Adam will work on this * Housekeeping tasks for 16, 17 and 18 cycles - Adam will sync with rbergeron TOPIC: AutoQA Update === * No AutoQA news, team still in F17 recovery TOPIC: Open Floor === N/A ACTION ITEMS === * adamw to review F17 retrospective and come up with an action plan * adamw to work with rbergeron to make sure housekeeping gets done for f16/f17/f18 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
2012-05-28 - Fedora QA Meeting - recap
As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20120528 Next meeting was scheduled for 2012-06-04 at 1500 UTC in #fedora-meeting. TOPIC: Previous meeting follow-up === * Current Blockers page was kept up to date by hand as planned TOPIC: Fedora 17 wrap-up / final tasks === * A vote of thanks to all for F17 validation * Common bugs page[1]: this query[2] lists the bugs proposed for inclusion but not yet added, please help write entries * AcceptedNTH but non-fixed bugs should be checked in case they should go onto common bugs * Kparal provided a table (now expired from fpaste) listing total validation tests run by each tester, Andre was the winner TOPIC: Fedora 18 planning === * We agreed to delay the discussion to next week due to the U.S. holiday depriving us of tflink and the anaconda crew TOPIC: AutoQA Update === * A bug was fixed that caused some duplicate mail spam to maintainers TOPIC: Open Floor === N/A [1] http://fedoraproject.org/wiki/Common_F17_bugs [2] http://bit.ly/fedora-commonbugs-proposed -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
2012-05-21 - Fedora QA Meeting - recap
As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20120521 Next meeting was scheduled for 2012-05-28 at 1500 UTC in #fedora-meeting. TOPIC: Previous meeting follow-up === * #810104 turned out to be an issue with the build environment, has been fixed * We decided we would update the blocker page by hand instead of generating shared searches TOPIC: Fedora 17 Final status/planning === * #822495 still needs to be verified * gtk3-3.4.3-2.fc17 needs karma in order to make it into RC3 * #823189 was rejected as a blocker, does not hit any of the Fedora 17 release criteria and it's too late in the release cycle to be taking anaconda changes for minor issues that have workarounds TOPIC: Upcoming QA Events === * Go/no-go scheduled for Thursday 2012-05-24 TOPIC: 2012-05-17 Gnome Boxes Test Day Results === * 6 testers reported results, 13 bugs referenced TOPIC: AutoQA Update === * jskladan spent time to optimize resultsdb searches and they're much faster now TOPIC: Open Floor === N/A ACTION ITEMS === * tflink or adamw to keep blocker wiki page updated by hand -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
2012-05-07 - Fedora QA Meeting - recap
As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20120507 Next meeting was scheduled for 2012-05-14 at 1500 UTC in #fedora-meeting. TOPIC: Previous Meeting Follow-Up === * pschindl followed up on GNOME boxes test day, event was not prepared in time so was pushed out another week, needs checking up again TOPIC: Fedora 17 Final Status/Planning === * tflink is planning a 'bugs that need re-testing' summary * We still need to complete the TC3 matrix to find any other lurking blockers, no point waiting till the RC * See online minutes[1] for mini blocker review summary TOPIC: Upcoming QA Events === * GNOME Boxes Test Day on 2012-05-10[2] * RC compose scheduled for 2012-05-08 * Final blocker review #5 2012-05-11 TOPIC: AutoQA Update === * No new AutoQA Updates TOPIC: Open Floor === N/A ACTION ITEMS === * adamw to check in on Boxes test day once more [1] http://meetbot.fedoraproject.org/fedora-meeting/2012-05-07/fedora-qa.2012-05-07-15.03.html [2] https://fedoraproject.org/wiki/Test_Day:2012-05-10_Gnome_Boxes -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nighlt-Composes?
On Tue, Jun 5, 2012 at 10:53 AM, Rob Healey wrote: > Greetings: > > I know that FC17 was just released a little while ago, but does anyone know > when Nightly-Composes will be built upon fc18/ rawhide ??? This is where it usually should be [1]. But there seems that there hasn't been any for a week now. [1] http://alt.fedoraproject.org/pub/alt/nightly-composes/ -Amit > > -- > Sincerely yours, > Rob G. Healey > > > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- http://echorand.me -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Nighlt-Composes?
Greetings: I know that FC17 was just released a little while ago, but does anyone know when Nightly-Composes will be built upon fc18/ rawhide ??? -- Sincerely yours, Rob G. Healey -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dropwatch package
On Mon, 4 Jun 2012 14:51:03 -0700 Rob Healey wrote: > Greetings: > > From looking at Koji Build System, I have noticed something weird: > > dropwatch-1.4-1 is being built or created for: > 1) fc18, and > 2) fc16 > > but not fc17! fc17 is getting 1.2-2 .. Can anyone tell me why? The maintainer seems to have failed to commit/build for F17. Perhaps drop them a note and ask why? kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
dropwatch package
Greetings: >From looking at Koji Build System, I have noticed something weird: dropwatch-1.4-1 is being built or created for: 1) fc18, and 2) fc16 but not fc17! fc17 is getting 1.2-2 .. Can anyone tell me why? -- Sincerely yours, Rob G. Healey -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Announcing Dogtail 0.8.0 - both GNOME3 and KDE4 compatible
Hi All! After having dealt with a number of issues in these last few months, we believe that the updated Dogtail, GUI test tool and automation framework, has now reached a state when we can release it. So finally - now more than two years after the last stable version - Dogtail 0.8.0 is out! It's already syncing into Fedora repositories, but you can also get it here [1]. So what is new? Some of you might have noticed, that Dogtail was no good since the release of Fedora 15. Thus most significantly, Dogtail was ported to be compatible with new GNOME 3 technologies and now works well again in major distributions centered around GNOME 3. And as a new, thanks to qt-at-spi, Dogtail now supports QT too and it can be used to test and automate KDE/QT applications as well! With QT accessibility enabled you will see the complete UI trees of QT applications as you were used to with GTK+ apps. KDE sessions are now supported both for working and script running environment out of the box with KDE 4.8.x and QT 4.8.2 onward. There were many more changes in Dogtail 0.8.0, you can find release highlights in the release notes [2]. We are making the 0.8.x series of releases the GNOME 3 / KDE 4 compatible branch, but for all of you who are using GNOME 2 / GTK+ 2 based systems we are continuing the 0.7.x branch, having released a bug-fixing update recently too [1]. We hope that all of you interested in GUI testing and automation will be interested in using dogtail again for GTK+ and try it up for QT apps too! Please don't hesitate to ask on IRC or write to the dogtail-list [3] if you have any questions. Thanks! Vita [1] https://fedorahosted.org/dogtail/ [2] https://fedorahosted.org/dogtail/browser/ChangeLog [3] https://mail.gnome.org/mailman/listinfo/dogtail-list -- Vita Humpa Desktop QE @ Red Hat -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20120604 changes
Compose started at Mon Jun 4 08:15:03 UTC 2012 Broken deps for x86_64 -- [389-admin] 389-admin-1.1.28-1.fc18.i686 requires libicuuc.so.48 389-admin-1.1.28-1.fc18.i686 requires libicui18n.so.48 389-admin-1.1.28-1.fc18.i686 requires libicudata.so.48 389-admin-1.1.28-1.fc18.x86_64 requires libicuuc.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicui18n.so.48()(64bit) 389-admin-1.1.28-1.fc18.x86_64 requires libicudata.so.48()(64bit) [389-dsgw] 389-dsgw-1.1.9-2.fc17.x86_64 requires libicuuc.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicui18n.so.48()(64bit) 389-dsgw-1.1.9-2.fc17.x86_64 requires libicudata.so.48()(64bit) [OpenGTL] OpenGTL-0.9.16-4.fc18.x86_64 requires libLLVM-3.0.so()(64bit) OpenGTL-devel-0.9.16-4.fc18.i686 requires libLLVM-3.0.so OpenGTL-devel-0.9.16-4.fc18.x86_64 requires libLLVM-3.0.so()(64bit) OpenGTL-libs-0.9.16-4.fc18.i686 requires libLLVM-3.0.so OpenGTL-libs-0.9.16-4.fc18.x86_64 requires libLLVM-3.0.so()(64bit) [PackageKit] PackageKit-zif-0.7.4-6.fc18.x86_64 requires libzif.so.3()(64bit) [aeolus-all] aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-doc = 0:0.4.0-2.fc17 aeolus-all-0.4.0-2.fc17.noarch requires aeolus-conductor-daemons = 0:0.4.0-2.fc17 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc18.noarch requires ruby-nokogiri [axis2c] axis2c-1.6.0-4.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 axis2c-1.6.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [boost141] boost141-graph-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-graph-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-graph-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-graph-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) boost141-regex-1.41.0-2.fc17.i686 requires libicuuc.so.48 boost141-regex-1.41.0-2.fc17.i686 requires libicui18n.so.48 boost141-regex-1.41.0-2.fc17.x86_64 requires libicuuc.so.48()(64bit) boost141-regex-1.41.0-2.fc17.x86_64 requires libicui18n.so.48()(64bit) [calligra] calligra-core-2.4.90-1.fc18.x86_64 requires calligra-kexi-map-form-widget < 0:2.4.90-1.fc18 [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [evolution-couchdb] evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-cal-1.2.so.15()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libedata-book-1.2.so.13()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libecal-1.2.so.11()(64bit) evolution-couchdb-0.5.91-10.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [evolution-rss] 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libedataserverui-3.0.so.1()(64bit) 1:evolution-rss-0.3.91-1.fc18.x86_64 requires libcamel-1.2.so.33()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python2-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-debug-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 gcc-python3-plugin-0.9-2.fc18.x86_64 requires gcc = 0:4.7.0-4.fc18 [gdb-heap] gdb-heap-0.5-8.fc17.x86_64 requires glibc(x86-64) = 0:2.15 [gnome-pilot] gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libedataserverui-3.0.so.1()(64bit) gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [gnome-python2-desktop] gnome-python2-evolution-2.32.0-9.fc17.x86_64 requires libecal-1.2.so.11()(64bit) [inkscape] inkscape-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) inkscape-view-0.48.2-5.fc17.x86_64 requires libpoppler.so.19()(64bit) [kdeplasma-addons] kdeplasma-addons-4.8.3-1.fc18.x86_64 requires libkexiv2.so.10()(64bit) plasma-wallpaper-marble-4.8.3-1.fc18.x86_64 requires libmarblewidget.so.13()(64bit) [mapnik] mapnik-2.0.0-4.fc17.i686 requires libicuuc.so.48 mapnik-2.0.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit) mapnik-utils-2.0.0-4.fc17.x86_64 requires libicuuc.so.48()(64bit) [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-postgresql-0.1.1-
Re: wine font changes system look and feel
> I'd like to brought to wider attention the bug > https://bugzilla.redhat.com/show_bug.cgi?id=693180 > > What's the matter? > > If you install wine, it brings as a dependency wine-tahoma font, that > is > then included in system wide fonts list. This causes the font to be > used > by applications like Firefox when pages require tahoma. As the font > is > badly looking, it makes many things to look terrible. > > Some of us think, this font should be made specific for the wine > application and not used system wide as it breaks the look and feel > of too > many things. > > Please make your voice to be heard on that. > > > Adam Pribyl Adam, it might be better to cross-post this also to devel@ list, doing that now. I believe there are a few good engineering practices that every software should keep. One of them is that installing one application should not have detrimental effects to another application. That is violated here. Installing wine brings broken fonts (Tahoma, maybe some others) into the system and then have detrimental effects on font rendering in web applications. We should do something about it. It is unfortunate that wine package maintainer doesn't want to discuss this issue any further. To some extent, he is even right. Wine depends on a font and fonts are installed into system-wide directories. Web pages request that font. End of story. But the reality is not perfect and often we have to do compromises. This is another obstacle presented by Microsoft to the opensource world and we can't simply insist on that "one and only correct solution". Because we know Tahoma rendering looks better on Windows and furthermore the web pages don't use it at all, it's just a fallback for some other font present in Windows but not in Linux. Our excuse is that there is a README in wine-tahoma-fonts package documenting how to blacklist it if you don't want it. Yes, but that doesn't help. We need Fedora to look good by default. I have heard several people saying "Fonts are ugly in Fedora, I'll rather use Ubuntu instead". And guess what, Ubuntu has made these broken wine fonts wine-specific, so that they are used in wine but not in other system applications. You might disagree with their other endeavors, but they care about their user-base. Putting some info in a README is good for hackers, but it is useless for end-users. I believe the best solution here is to make Tahoma (and maybe some other fonts that are rendered horribly) a wine-specific font. Then add a README how to make those fonts available for all applications, if someone ever needs that. Or we can create a separate package for system-wide installation. This way we will have reasonable defaults and more happy users. Anyone, if you have a better suggestion how to solve this problem, please be heard. The desirable outcome is: 1. Wine is installed 2. Web page rendering looks pretty (no bitmap fonts) 3. No manual steps are needed Comments welcome. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
