[Test-Announce] Fedora 19 Final Release Candidate 1 (RC1) Available Now!

2013-06-24 Thread Andre Robatino
As per the Fedora 19 schedule [1], Fedora 19 Final Release Candidate 1
(RC1) is now available for testing. Content information, including
changes, can be found at
https://fedorahosted.org/rel-eng/ticket/5623#comment:18 . Please see the
following pages for download links (including delta ISOs) and testing
instructions. Normally dl.fedoraproject.org should provide the fastest
download, but download-ib01.fedoraproject.org is available as a mirror
(with an approximately 1 hour lag) in case of trouble. To use it, just
replace "dl" with "download-ib01" in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Ideally, all Alpha, Beta, and Final priority test cases for Installation
[2], Base [3], and Desktop [4] should pass in order to meet the Final
Release Criteria [5]. Help is available on #fedora-qa on
irc.freenode.net [6], or on the test list [7].

Create Fedora 19 Final test composes (TC) and release candidates (RC)
https://fedorahosted.org/rel-eng/ticket/5623

Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current

[1] http://fedorapeople.org/groups/schedule/f-19/f-19-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Installation_validation_testing
[3] https://fedoraproject.org/wiki/QA:Base_validation_testing
[4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing
[5] https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria
[6] irc://irc.freenode.net/fedora-qa
[7] https://admin.fedoraproject.org/mailman/listinfo/test



signature.asc
Description: OpenPGP digital signature
___
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

Fedora 18 updates-testing report

2013-06-24 Thread updates
The following Fedora 18 Security updates need testing:
 Age  URL
 167  
https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18
 101  
https://admin.fedoraproject.org/updates/FEDORA-2013-3935/puppet-3.1.1-1.fc18
  94  
https://admin.fedoraproject.org/updates/FEDORA-2013-4243/stunnel-4.55-1.fc18
  81  
https://admin.fedoraproject.org/updates/FEDORA-2013-4823/microcode_ctl-2.0-3.fc18
  66  
https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18
  39  
https://admin.fedoraproject.org/updates/FEDORA-2013-8381/varnish-3.0.3-5.fc18
  24  
https://admin.fedoraproject.org/updates/FEDORA-2013-9707/livecd-tools-18.16-2.fc18
  20  
https://admin.fedoraproject.org/updates/FEDORA-2013-9962/subversion-1.7.10-1.fc18
  11  
https://admin.fedoraproject.org/updates/FEDORA-2013-10806/fail2ban-0.8.10-1.fc18
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-11212/haproxy-1.4.24-1.fc18
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-11198/dbus-1.6.12-1.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11396/glpi-0.83.9-1.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11407/qemu-1.2.2-13.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11419/python-bugzilla-0.9.0-1.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-11574/curl-7.27.0-11.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-10713/openstack-keystone-2012.2.4-5.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-11630/wordpress-3.5.2-1.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-11646/ReviewBoard-1.7.10-1.fc18


The following Fedora 18 Critical Path updates have yet to be approved:
 Age URL
 135  
https://admin.fedoraproject.org/updates/FEDORA-2013-2192/nautilus-3.6.3-5.fc18
  16  
https://admin.fedoraproject.org/updates/FEDORA-2013-10428/NetworkManager-0.9.8.2-1.fc18,network-manager-applet-0.9.8.2-1.fc18
  13  
https://admin.fedoraproject.org/updates/FEDORA-2013-10635/emacs-24.2-19.fc18
  13  
https://admin.fedoraproject.org/updates/FEDORA-2013-10643/dnsmasq-2.65-6.fc18
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-10939/dosfstools-3.0.20-2.fc18
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-11278/make-3.82-14.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11402/deltarpm-3.6-0.12.20110223git.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11375/gtk3-3.6.4-2.fc18
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11419/python-bugzilla-0.9.0-1.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-11574/curl-7.27.0-11.fc18
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-11498/binutils-2.23.51.0.1-10.fc18
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-11629/unzip-6.0-10.fc18


The following builds have been pushed to Fedora 18 updates-testing

Mars-4.3-1.fc18
ReviewBoard-1.7.10-1.fc18
choqok-1.3.1-0.2.20130624.fc18
dvd+rw-tools-7.1-13.fc18
ehcache-core-2.6.0-3.fc18
ghc-SafeSemaphore-0.9.0-1.fc18
ghc-shakespeare-text-1.0.0.5-1.fc18
gimp-2.8.6-1.fc18
gnuradio-3.6.5-3.fc18
gsi-openssh-6.1p1-7.fc18
hplip-3.13.6-2.fc18
ibus-typing-booster-1.1.0-1.fc18
mate-applet-softupd-0.2.8-1.fc18
nbdkit-1.0.0-4.fc18
postfix-2.9.7-1.fc18
python-rhsm-1.8.13-1.fc18
python-tahrir-api-0.2.2-1.fc18
subscription-manager-1.8.11-1.fc18
sx-2.15-1.fc18
tcpcopy-0.8.0-3.fc18
unzip-6.0-10.fc18
wordpress-3.5.2-1.fc18

Details about builds:



 Mars-4.3-1.fc18 (FEDORA-2013-11621)
 An interactive development environment for programming in MIPS assembly 
language

Update Information:

Fix ClassNotFoundExceptions on start and also update to the latest upstream 
version.

ChangeLog:

* Mon Jun 24 2013 Mat Booth  - 4.3-1
- Fix class not found exceptions at startup, rhbz#828973
- Also update to latest upstream
- Write a real build script to create the jar
* Wed Feb 13 2013 Fedora Release Engineering  
- 4.1-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild

References:

  [ 1 ] Bug #828973 - Mars MIPS simulator crashes immediately
https://bugzilla.redhat.com/show_bug.cgi?id=828973




 ReviewBoard-1.7.10-1.fc18 (FEDORA-2013-11646)
 Web-based code review tool

Update Information:

New upstream release 1.7.10

- http://www.reviewboard.org/docs/releasenotes/reviewboar

Fedora 17 updates-testing report

2013-06-24 Thread updates
The following Fedora 17 Security updates need testing:
 Age  URL
 354  
https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17
 166  
https://admin.fedoraproject.org/updates/FEDORA-2013-0455/fedora-business-cards-1-0.1.beta1.fc17
  94  
https://admin.fedoraproject.org/updates/FEDORA-2013-4234/stunnel-4.55-1.fc17
  89  
https://admin.fedoraproject.org/updates/FEDORA-2013-4501/libxslt-1.1.28-1.fc17
  86  
https://admin.fedoraproject.org/updates/FEDORA-2013-4581/libuser-0.57.6-2.fc17
  19  
https://admin.fedoraproject.org/updates/FEDORA-2013-10128/ssmtp-2.61-20.fc17
  19  
https://admin.fedoraproject.org/updates/FEDORA-2013-10121/subversion-1.7.10-1.fc17
  11  
https://admin.fedoraproject.org/updates/FEDORA-2013-10830/fail2ban-0.8.10-1.fc17
  11  
https://admin.fedoraproject.org/updates/FEDORA-2013-9123/kernel-3.9.5-101.fc17
   8  
https://admin.fedoraproject.org/updates/FEDORA-2013-10940/tomcat6-6.0.37-1.fc17
   5  
https://admin.fedoraproject.org/updates/FEDORA-2013-11234/haproxy-1.4.24-1.fc17
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11397/python-bugzilla-0.9.0-1.fc17
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11413/glpi-0.83.9-1.fc17
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-11568/curl-7.24.0-10.fc17
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-11649/wordpress-3.5.2-1.fc17


The following Fedora 17 Critical Path updates have yet to be approved:
 Age URL
 306  
https://admin.fedoraproject.org/updates/FEDORA-2012-12509/PackageKit-0.7.6-1.fc17
 114  
https://admin.fedoraproject.org/updates/FEDORA-2013-3304/libvpx-1.2.0-1.fc17
  13  
https://admin.fedoraproject.org/updates/FEDORA-2013-10602/dnsmasq-2.65-6.fc17
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11411/deltarpm-3.6-0.12.20110223git.fc17
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11397/python-bugzilla-0.9.0-1.fc17
   1  
https://admin.fedoraproject.org/updates/FEDORA-2013-11568/curl-7.24.0-10.fc17


The following builds have been pushed to Fedora 17 updates-testing

choqok-1.3.1-0.2.20130624.fc17
dvd+rw-tools-7.1-13.fc17
ehcache-core-2.6.0-2.fc17
gimp-2.8.6-1.fc17
gsi-openssh-5.9p1-12.fc17
ibus-typing-booster-1.1.0-1.fc17
mate-applet-softupd-0.2.8-1.fc17
python-rhsm-1.8.13-1.fc17
subscription-manager-1.8.11-1.fc17
sx-2.15-1.fc17
wordpress-3.5.2-1.fc17

Details about builds:



 choqok-1.3.1-0.2.20130624.fc17 (FEDORA-2013-11643)
 KDE Micro-Blogging Client

Update Information:

Snapshot release adds support for new twitter 1.1 api

ChangeLog:

* Mon Jun 24 2013 Rex Dieter  1.3.1-0.2.20130624
- 1.3.1 20130624git snapshot
- fix/prune %changelog
- .spec cosmetics
* Fri Jun 21 2013 Rex Dieter  1.3.1-0.1.20130621
- 1.3.1 20130621git snapshot (uses new twitter 1.1 api)
* Wed Feb 13 2013 Fedora Release Engineering  
- 1.3-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
* Tue Nov 27 2012 Rex Dieter  1.3-5
- rebuild (qjson)
* Fri Nov 23 2012 Rex Dieter  1.3-4
- rebuild (qjson)
* Wed Jul 18 2012 Fedora Release Engineering  
- 1.3-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild




 dvd+rw-tools-7.1-13.fc17 (FEDORA-2013-11642)
 Toolchain to master DVD+RW/+R media

Update Information:

Merged from rawhide.

ChangeLog:

* Mon Jun 24 2013 Frantisek Kluknavsky  - 7.1-13
- when formating blu-ray as srm+pow, handle it later correctly as srm+pow, not 
srm
(credits Thomas Schmitt)
* Wed Feb 13 2013 Fedora Release Engineering  
- 7.1-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
* Mon Aug 27 2012 Honza Horak  - 7.1-11
- Spec file cleanup
- Print error in case we want to write already written DVD-RW in Sequential
  Recording mode (bug #810838)
- Add man page for dvd+rw-format
* Wed Jul 18 2012 Fedora Release Engineering  
- 7.1-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild

References:

  [ 1 ] Bug #868527 - i/o error on K3b
https://bugzilla.redhat.com/show_bug.cgi?id=868527
  [ 2 ] Bug #858029 - growisofs fails to close the FIRST session with 
SK=5h/INVALID FIELD IN CDB when burning blu-ray BD-R SL
https://bugzilla.redhat.com/show_bug.cgi?id=858029



==

Re: F19: powertop is broken

2013-06-24 Thread Adam Williamson
On Sun, 2013-06-23 at 23:54 +1200, Gavin Flower wrote:
> On 23/06/13 23:47, Christian Menzel wrote:
> 
> > Hi, I upgraded to F19 from F18 via fedup and noticed that powertop
> > is not working anymore. It repeats constantly the following 2
> > messages: 
> > 
> > 
> > BUG: requesting unregistered parameter 95
> > BUG: requesting unregistered parameter 100
> > 
> > 
> > 
> > Has anyone else noticed this?
> > 
> > 
> > Regards
> > Chris
> > 
> > 
> > 
> > 
> I can run powertop in F19-TC5 (fresh install) no problems.

https://bugzilla.redhat.com/show_bug.cgi?id=947425
-- 
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: Forcing F19 to 'vga mode' + borked install after Virtualbox guest additions on F19

2013-06-24 Thread Fernando Cassia
On Mon, Jun 24, 2013 at 7:28 PM, Adam Williamson wrote:

> Honestly, I don't quite get why anyone would run a
> 32-bit guest, unless you're somehow still stuck with a 32-bit only host
> machine
>

performance?
http://superuser.com/questions/407072/why-do-some-applications-run-faster-on-a-32-bit-guest-vm-than-on-the-64-bit-host

FC
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19/Mate, strange desktop problem.

2013-06-24 Thread Fred Smith
On Sun, Jun 23, 2013 at 10:33:10PM -0500, Rex Dieter wrote:
> Fred Smith wrote:
> 
> > While trying to work thru problem with my netbook not going to sleep
> > when the lid is closed (in relation to some of the bugs discussed on
> > this last in the last several days) I had cause to do a yum update that
> > downloaded a pile of updates from  the testing repo.
> > 
> > ever since then, my desktop has no icons, and the right-click/context
> > menu on the desktop does not work.
> > 
> > Here's a list of the Mate packages currently installed:
> > 
> ...
> > mate-file-manager.x86_64  1.6.1-7.fc19@updates-testing
> ...
> > Not having seen anyone else complaining about this, I guess it's not
> > widespread, but if anyone has any clues for me I'd appreciate it!
> 
> Looks like you probably want to back out of:
> 
> https://admin.fedoraproject.org/updates/FEDORA-2013-11332/mate-file-manager-1.6.1-7.fc19
> 
> -- rex

Thanks Rex, that did the trick. I 'preciate the guidance.


-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
  "And he will be called Wonderful Counselor, Mighty God, Everlasting Father,
  Prince of Peace. Of the increase of his government there will be no end. He 
 will reign on David's throne and over his kingdom, establishing and upholding
  it with justice and righteousness from that time on and forever."
--- Isaiah 9:7 (niv) --
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Validation tests not yet run against Final

2013-06-24 Thread Adam Williamson
On Mon, 2013-06-24 at 19:31 -0400, Konrad Rzeszutek Wilk wrote:
> Adam Williamson  wrote:
> 
> >On Mon, 2013-06-24 at 15:21 -0400, Kamil Paral wrote:
> >
> >> QA:Testcase_Boot_Methods_Xen_Para_Virt
> >
> >Konrad, are you able to give F19 Final TC6 or later (RC1 may be built
> >today) a shot and check Xen is OK? Dennis, does any of your testing hit
> >this test case?
> 
> Of course.  Let me do that tomorrow if that is OK.  Thanks for reaching out 
> and poking me. 

That'd be awesome, thanks! RC1 should be available by then, all being
well.
-- 
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: Forcing F19 to 'vga mode' + borked install after Virtualbox guest additions on F19

2013-06-24 Thread Adam Williamson
On Mon, 2013-06-24 at 18:57 -0400, Fernando Cassia wrote:
> 
> On Mon, Jun 24, 2013 at 1:34 AM, Adam Williamson 
> wrote:
> > I wonder if anyone else has tested F19 (32bit) on Virtualbox
> guest
> 
> 
> Yes, several people.
> 
> Hi Adam,
> 
> Apparently not with the guest additions installed. There is a bug,
> that affects the X server only in the 32bit Fedora. It's been reported
> here and a patch provided.

Well, then you mean 'apparently not with 32-bit guests and the GA
installed', then. :) Honestly, I don't quite get why anyone would run a
32-bit guest, unless you're somehow still stuck with a 32-bit only host
machine. So I don't tend to assign 32-bit virt bugs much mental
priority.

> 
> https://bugzilla.redhat.com/show_bug.cgi?id=972095
> 
> Will we have to wait long for the fix to be incorporated upstream?

I've no idea; ajax and airlied may have some idea whether this will
likely get merged upstream soon, and how long it may take to show up in
Fedora.
-- 
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: Forcing F19 to 'vga mode' + borked install after Virtualbox guest additions on F19

2013-06-24 Thread Fernando Cassia
On Mon, Jun 24, 2013 at 1:34 AM, Adam Williamson wrote:

> > I wonder if anyone else has tested F19 (32bit) on Virtualbox guest
>
> Yes, several people.


Hi Adam,

Apparently not with the guest additions installed. There is a bug, that
affects the X server only in the 32bit Fedora. It's been reported here and
a patch provided.

https://bugzilla.redhat.com/show_bug.cgi?id=972095

Will we have to wait long for the fix to be incorporated upstream?

Thanks...
FC


-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Validation tests not yet run against Final

2013-06-24 Thread Adam Williamson
On Mon, 2013-06-24 at 15:21 -0400, Kamil Paral wrote:

> QA:Testcase_install_repository_NFS_variation
> QA:Testcase_install_repository_HTTP/FTP_graphical
> QA:Testcase_install_repository_NFS_graphical

I will at least get to these today, and try and hit up the ks/updates
path ones too.
-- 
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: Validation tests not yet run against Final

2013-06-24 Thread Adam Williamson
On Mon, 2013-06-24 at 15:21 -0400, Kamil Paral wrote:

> QA:Testcase_Boot_Methods_Xen_Para_Virt

Konrad, are you able to give F19 Final TC6 or later (RC1 may be built
today) a shot and check Xen is OK? Dennis, does any of your testing hit
this test case?
-- 
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: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Adam Williamson
On Mon, 2013-06-24 at 07:22 -0400, Jaroslav Reznik wrote:

> > that is, with the old spin-kickstarts and without the above update,
> > we're 19215872 bytes oversize; with the update but old spin-kickstarts,
> > we're 17118720 bytes oversize (the update saves ~2.1MB); and with the
> > update and latest spin-kickstarts, we're 5584384 bytes oversize (the
> > kickstart changes save ~11.5MB). We still need to find another 5.6MB
> > from somewhere.
> 
> Do we have to be byte strict here? For physical medium sizes, we had to
> be, this 1 GB is more "we set it as we think it's a good idea". Or maybe
> 1 GB sticks (what's the real size one can use + overlay?) but it's not
> as strict, as you could pick up bigger one.

So my take on that is:

* As long as we have a size limit we should be byte-strict. This is just
for practical reasons: it's excessively difficult to enforce a 'fuzzy'
size cap. It's much easier if it's just Thou Shalt Not.

* There is nothing magical about 100 (whatever the zero count
is) bytes. We picked the power-of-10 GB as a pessimistic number for the
USB stick case: we haven't actually sent anyone to Staples to buy a
bunch of USB sticks and figure out exactly how many bytes you can write
to one with a given stated capacity, we just figured that was the safe
pessimistic number to use. Personally I'm not in any way wedded to that
specific size limit for the desktop live image; if the desktop team
wants to change it, fine. As I wrote earlier in the thread, I'd just
like to make sure the spin doesn't get so large people consider it
bloated, and doesn't start interfering with our ability to do the
four-desktop live DVD.
-- 
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: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Adam Williamson
On Mon, 2013-06-24 at 15:21 +0200, drago01 wrote:
> On Mon, Jun 24, 2013 at 3:15 PM, Bill Nottingham  wrote:
> > Bruno Wolff III (br...@wolff.to) said:
> >> On Sun, Jun 23, 2013 at 18:04:55 -0400,
> >>   Matthias Clasen  wrote:
> >> >rpm db  82M
> >>
> >> I vaguely remember a discussion about dropping this for live images
> >> because it gets rebuilt every boot when needed. My memory is that we
> >> ended up removing this data while building live images, but haven't
> >> looked at it in a long time.
> >
> > It's useful in terms of having a RPM-based manifest of what's on
> > the image, and if you're installing the image to disk, you're going
> > to need it on the installed system...
> 
> And it allows stuff like "yum install foo" to work in the live environment.

which is *extremely* useful both for normal use and for testing (I do
'yum update anaconda' for a quick test run all the time, fr'instance).
Let's not lose that :)
-- 
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

F19 Final Blocker Bug Review #8 Minutes

2013-06-24 Thread Tim Flink
=
#fedora-blocker-review: f19final-blocker-review-8
=

Minutes: 
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-blocker-review-8.2013-06-24-16.00.html
Minutes (text): 
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-blocker-review-8.2013-06-24-16.00.txt
Log: 
http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-24/f19final-blocker-review-8.2013-06-24-16.00.log.html


Meeting summary
---
* Roll Call  (tflink, 16:00:43)

* Introduction  (tflink, 16:07:08)
  * 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 freeze
exception bugs.  (tflink, 16:07:13)
  * We'll be following the process outlined at:  (tflink, 16:07:18)
  * LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(tflink, 16:07:18)
  * The bugs up for review today are available at:  (tflink, 16:07:23)
  * LINK: http://qa.fedoraproject.org/blockerbugs/current   (tflink,
16:07:23)
  * The criteria for release blocking bugs can be found at:  (tflink,
16:07:28)
  * LINK:
https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria
(tflink, 16:07:28)
  * LINK: https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria
(tflink, 16:07:31)
  * LINK:
https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria
(tflink, 16:07:34)
  * Up for review today, we have:  (tflink, 16:07:37)
  * 3 Proposed Blockers  (tflink, 16:07:40)
  * 3 Accepted Blockers  (tflink, 16:07:40)
  * 14 Proposed Freeze Exceptions  (tflink, 16:07:40)
  * 20 Accepted Freeze Exceptions  (tflink, 16:07:40)

* (964443) Fedora 19 Live Alpha and Beta hangs in boot on HP Envy 23
  (tflink, 16:08:07)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=964443   (tflink,
16:08:10)
  * Proposed Blocker, kernel, NEW  (tflink, 16:08:12)
  * AGREED: 964443 - RejectedBlocker - While unfortunate, there have not
been enough reports of this bug to indicate that it is widespread
enough to justify blocking release of F19 final.  (tflink, 16:14:27)

* (974811) NetworkManager dispatchers dbus services misconfiguration
  (tflink, 16:14:34)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=974811   (tflink,
16:14:37)
  * Proposed Blocker, NetworkManager, NEW  (tflink, 16:14:39)
  * AGREED: 974811 - RejectedBlocker AcceptedFreezeException - The
issues described are not critpath, not 100% applicable to live
images and could be fixed with an update. Thus it doesn't qualify as
a release blocking issue but a tested fix would be considered after
freeze.  (tflink, 16:22:01)

* (973019) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in
  position 0: ordinal not in range(128)  (tflink, 16:22:09)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=973019   (tflink,
16:22:12)
  * Proposed Blocker, python-blivet, POST  (tflink, 16:22:15)
  * LINK:

https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Fedora&component=anaconda&component=python-blivet&list_id=1474576&query_format=advanced&short_desc=UnicodeDecodeError&short_desc_type=allwordssubstr
(adamw, 16:29:51)
  * LINK:

https://lists.fedorahosted.org/pipermail/anaconda-patches/2013-June/004732.html
(adamw, 16:36:01)
  * AGREED: 973019 - AcceptedBlocker - Violates the following F19 final
release criterion for many live installs using non-english
languages: "The installer must be able to create and install to any
workable partition layout using any file system offered in a default
installer configuration, LVM, software, hardware or BIOS RAID, or
combination of the above"  (tflink, 17:21:30)

* (973384) UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in
  position 0: ordinal not in range(128)  (tflink, 17:21:37)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=973384   (tflink,
17:21:40)
  * ProposedBlocker, python-blivet, NEW  (tflink, 17:21:43)
  * AGREED: 973384 - AcceptedBlocker - Violates the following F19 final
release criterion for many live installs using non-english
languages: "The installer must be able to create and install to any
workable partition layout using any file system offered in a default
installer configuration, LVM, software, hardware or BIOS RAID, or
combination of the above"  (tflink, 17:25:00)

* (874381) USB stick install is running from doesn't get filtered out as
  an install target  (tflink, 17:25:43)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=874381   (tflink,
17:25:46)
  * Proposed Freeze Exceptions, anaconda, MODIFIED  (tflink, 17:25:49)
  * LINK: https://bugzilla.redhat.com/show_b

Re: Validation tests not yet run against Final

2013-06-24 Thread Kamil Paral
Josef improved the script a bit, you can see the as-of-now test case stats here:

http://kparal.fedorapeople.org/testcase_stats/Category_Installation_validation_testing.html

(sort it by "Last in")

We definitely need to execute:
QA:Testcase_install_repository_NFS_variation
QA:Testcase_Anaconda_updates.img_via_local_media
QA:Testcase_Anaconda_updates.img_via_installation_source
QA:Testcase_Boot_Methods_Xen_Para_Virt
QA:Testcase_Kickstart_Nfs_Server_Path_Ks_Cfg
QA:Testcase_Kickstart_File_Path_Ks_Cfg
QA:Testcase_install_repository_HTTP/FTP_graphical
QA:Testcase_install_repository_NFS_graphical
QA:Testcase_Kickstart_Hd_Device_Path_Ks_Cfg

I'd like to see this auto-generated for F20. Right now I'll just update it 
manually from time to time.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[SOLVED] Re: grub2-mkconfig not picking up all kernels on another partition

2013-06-24 Thread Frank McCormick

On 06/23/2013 10:04 PM, Frank McCormick wrote:

On 06/23/2013 08:18 PM, Matthew Miller wrote:

On Sun, Jun 23, 2013 at 03:54:33PM -0600, Chris Murphy wrote:

bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
Post the result somewhere, then post the URL here. Sounds like an OS Prober 
issue, which is more problematic on UEFI than BIOS usually.

Try fpaste:

$ echo foo |fpaste
Uploading (0.1KiB)...
http://ur1.ca/ef6v3  ->http://paste.fedoraproject.org/20400/20331081




Further checking shows mkconfig IS putting all the kernels into 
grub.cfg

the problem is now grub is not displaying them! And it's happening on
19 and on 18.
Too tired tonight to pursue this further...I'll tackle it again tomorrow.

Thanks Chris and Matthew !






I checked grub.cfg again and it does contains all the kernels...so 
then I

stripped down /etc/default/grub.cfg to the bare minimum and lo and behold
all the kernels display.
I don't know which option or if any option was fouling up the 
display..but I am

happy even with the resulting bare bones menu.

Thanks

--
--Cheers--

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Matthias Clasen
On Mon, 2013-06-24 at 09:15 -0400, Bill Nottingham wrote:
> Bruno Wolff III (br...@wolff.to) said: 
> > On Sun, Jun 23, 2013 at 18:04:55 -0400,
> >   Matthias Clasen  wrote:
> > >rpm db  82M
> > 
> > I vaguely remember a discussion about dropping this for live images
> > because it gets rebuilt every boot when needed. My memory is that we
> > ended up removing this data while building live images, but haven't
> > looked at it in a long time.
> 
> It's useful in terms of having a RPM-based manifest of what's on
> the image, and if you're installing the image to disk, you're going
> to need it on the installed system...
> 

I don't really want to propose dropping the rpm db.
I merely stated those numbers to give some perspective on what takes up
how much space on the live image.

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Matthias Clasen
On Mon, 2013-06-24 at 09:14 -0400, Bill Nottingham wrote:
> > - We have both js and mozjs17. js is still used by gjs, libpeas,
> > libproxy-mozjs and gnome-shell. Possible savings: 7M
> 
> I thought Colin was fixing everything to use mosjz17. Is that a F-20
> thing?

It missed f19, yes.

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread drago01
On Mon, Jun 24, 2013 at 3:15 PM, Bill Nottingham  wrote:
> Bruno Wolff III (br...@wolff.to) said:
>> On Sun, Jun 23, 2013 at 18:04:55 -0400,
>>   Matthias Clasen  wrote:
>> >rpm db  82M
>>
>> I vaguely remember a discussion about dropping this for live images
>> because it gets rebuilt every boot when needed. My memory is that we
>> ended up removing this data while building live images, but haven't
>> looked at it in a long time.
>
> It's useful in terms of having a RPM-based manifest of what's on
> the image, and if you're installing the image to disk, you're going
> to need it on the installed system...

And it allows stuff like "yum install foo" to work in the live environment.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Bill Nottingham
Bruno Wolff III (br...@wolff.to) said: 
> On Sun, Jun 23, 2013 at 18:04:55 -0400,
>   Matthias Clasen  wrote:
> >rpm db  82M
> 
> I vaguely remember a discussion about dropping this for live images
> because it gets rebuilt every boot when needed. My memory is that we
> ended up removing this data while building live images, but haven't
> looked at it in a long time.

It's useful in terms of having a RPM-based manifest of what's on
the image, and if you're installing the image to disk, you're going
to need it on the installed system...

Bill
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Bill Nottingham
> - We have both js and mozjs17. js is still used by gjs, libpeas,
> libproxy-mozjs and gnome-shell. Possible savings: 7M

I thought Colin was fixing everything to use mosjz17. Is that a F-20
thing?

Bill
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F-19 Branched report: 20130624 changes

2013-06-24 Thread Fedora Branched Report
Compose started at Mon Jun 24 09:15:02 UTC 2013

Broken deps for x86_64
--
[avgtime]
avgtime-0-0.5.git20120724.fc19.x86_64 requires 
libphobos-ldc.so.60()(64bit)
[derelict]
derelict-ogg-3-13.20130516gitd8aa11d.fc19.i686 requires ogg
derelict-ogg-3-13.20130516gitd8aa11d.fc19.i686 requires OGG
derelict-ogg-3-13.20130516gitd8aa11d.fc19.x86_64 requires ogg
derelict-ogg-3-13.20130516gitd8aa11d.fc19.x86_64 requires OGG
derelict-ogg-devel-3-13.20130516gitd8aa11d.fc19.i686 requires ogg
derelict-ogg-devel-3-13.20130516gitd8aa11d.fc19.i686 requires OGG
derelict-ogg-devel-3-13.20130516gitd8aa11d.fc19.x86_64 requires ogg
derelict-ogg-devel-3-13.20130516gitd8aa11d.fc19.x86_64 requires OGG
derelict-pq-3-13.20130516gitd8aa11d.fc19.i686 requires pq
derelict-pq-3-13.20130516gitd8aa11d.fc19.i686 requires PQ
derelict-pq-3-13.20130516gitd8aa11d.fc19.x86_64 requires pq
derelict-pq-3-13.20130516gitd8aa11d.fc19.x86_64 requires PQ
derelict-pq-devel-3-13.20130516gitd8aa11d.fc19.i686 requires pq
derelict-pq-devel-3-13.20130516gitd8aa11d.fc19.i686 requires PQ
derelict-pq-devel-3-13.20130516gitd8aa11d.fc19.x86_64 requires pq
derelict-pq-devel-3-13.20130516gitd8aa11d.fc19.x86_64 requires PQ
derelict-tcod-3-13.20130516gitd8aa11d.fc19.i686 requires tcod
derelict-tcod-3-13.20130516gitd8aa11d.fc19.i686 requires TCOD
derelict-tcod-3-13.20130516gitd8aa11d.fc19.x86_64 requires tcod
derelict-tcod-3-13.20130516gitd8aa11d.fc19.x86_64 requires TCOD
derelict-tcod-devel-3-13.20130516gitd8aa11d.fc19.i686 requires tcod
derelict-tcod-devel-3-13.20130516gitd8aa11d.fc19.i686 requires TCOD
derelict-tcod-devel-3-13.20130516gitd8aa11d.fc19.x86_64 requires tcod
derelict-tcod-devel-3-13.20130516gitd8aa11d.fc19.x86_64 requires TCOD
[dragonegg]
dragonegg-3.1-19.fc19.x86_64 requires gcc = 0:4.7.2-9.fc19
[dsqlite]
dsqlite-1.0-4.fc19.i686 requires libphobos-ldc.so.60
dsqlite-1.0-4.fc19.x86_64 requires libphobos-ldc.so.60()(64bit)
[dustmite]
dustmite-1-8.20121031git1fb3ac4.fc18.x86_64 requires 
libphobos-ldc.so.60()(64bit)
[freeipa]
freeipa-server-strict-3.2.1-1.fc19.x86_64 requires pki-ca = 0:10.0.2
freeipa-server-strict-3.2.1-1.fc19.x86_64 requires 389-ds-base = 
0:1.3.1.0
[gl3n]
gl3n-0.20120813-4.fc19.i686 requires libphobos-ldc.so.60
gl3n-0.20120813-4.fc19.x86_64 requires libphobos-ldc.so.60()(64bit)
[gooddata-cl]
gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java
[kawa]
1:kawa-1.11-5.fc19.x86_64 requires servlet25
[koji]
koji-vm-1.8.0-1.fc19.noarch requires python-virtinst
[libkolab]
php-kolab-0.4.1-3.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64
php-kolab-0.4.1-3.fc19.x86_64 requires php(api) = 0:20100412-x86-64
[nodejs-tilelive]
nodejs-tilelive-4.4.3-2.fc19.noarch requires npm(optimist) < 0:0.4
[openbox]
gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel
gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires 
gnome-panel
[ovirt-engine]
ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires 
classpathx-mail
[ovirt-guest-agent]
ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires 
libgdmsimplegreeter.so.1()(64bit)
[perl-Bio-ASN1-EntrezGene]
perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires 
perl(Bio::Index::AbstractSeq)
[perl-Bio-SamTools]
perl-Bio-SamTools-1.35-2.fc19.x86_64 requires 
perl(Bio::SeqFeature::Lite)
perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq)
[python-TraitsBackendQt]
python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI
[scala]
scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library)
[spacewalk-web]
spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup)
[tango]
tango-2-12.20120821git7b92443.fc19.i686 requires libphobos-ldc.so.60
tango-2-12.20120821git7b92443.fc19.x86_64 requires 
libphobos-ldc.so.60()(64bit)
[zarafa]
php-mapi-7.0.13-1.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64
php-mapi-7.0.13-1.fc19.x86_64 requires php(api) = 0:20100412-x86-64



Broken deps for i386
--
[avgtime]
avgtime-0-0.5.git20120724.fc19.i686 requires libphobos-ldc.so.60
[derelict]
derelict-ogg-3-13.20130516gitd8aa11d.fc19.i686 requires ogg
derelict-ogg-3-13.20130516gitd8aa11d.fc19.i686 requires OGG
derelict-ogg-devel-3-13.20130516gitd8aa11d.fc19.i686 requires ogg
derelict-ogg-devel-3-13.20130516gitd8aa11d.fc19.i686 requires OGG
derelict-pq-3-13.20130516gitd8aa11d.fc19.i686 requires pq
derelict-pq-3-13.20130516gitd8aa11d.fc19.i686 requires PQ
der

[Test-Announce] Fedora 19 Go/No-Go Meeting, Thursday, June 27 @ 17:00 UTC

2013-06-24 Thread Jaroslav Reznik
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19.

Thursday, June 27, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)

"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of
the QA Team."

For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

In the meantime, keep an eye on the Fedora 19 Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/19/final/buglist

There are currently three unresolved accepted blockers, for full
status see mail [1] by adamw. Please help with the release of 
Fedora 19, take a look on bugs assigned to you!
 
Reminder: the Readiness meeting follows up the Go/No-Go meeting two
hours later.

[1] https://lists.fedoraproject.org/pipermail/devel/2013-June/184345.html

Jaroslav
___
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

rawhide report: 20130624 changes

2013-06-24 Thread Fedora Rawhide Report
Compose started at Mon Jun 24 08:15:03 UTC 2013

Broken deps for x86_64
--
[aries-blueprint]
aries-blueprint-0.3.1-5.fc19.noarch requires asm2
[chmsee]
chmsee-2.0-5.git0acc572a.fc20.x86_64 requires libxpcom.so()(64bit)
[cxf]
1:cxf-rt-2.6.6-1.fc19.noarch requires asm2
[ekiga]
ekiga-4.0.1-1.fc19.x86_64 requires libedata-book-1.2.so.17()(64bit)
[evolution-rss]
1:evolution-rss-0.3.93-3.fc20.x86_64 requires libeutil.so()(64bit)
1:evolution-rss-0.3.93-3.fc20.x86_64 requires libeshell.so()(64bit)
[firefox]
firefox-20.0-5.fc20.x86_64 requires libxpcom.so()(64bit)
[gdb-heap]
gdb-heap-0.5-12.fc19.x86_64 requires glibc(x86-64) = 0:2.17
[ghc-Agda]
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSzlib-0.5.4.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSxhtml-3000.2.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSvector-0.10.0.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSunix-2.5.1.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHStransformers-0.3.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHStime-1.4-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHStext-0.11.2.3-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSterminfo-0.3.2.5-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHStemplate-haskell-2.7.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSsyb-0.3.7-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSrandom-1.0.1.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSprocess-1.1.0.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSprimitive-0.5.0.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSpretty-1.1.1.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSold-time-1.1.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSold-locale-1.0.0.4-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSmtl-2.1.2-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSinteger-gmp-0.4.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHShaskell-src-exts-1.13.5-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHShaskeline-0.7.0.3-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHShashtables-1.0.1.8-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHShashable-1.1.2.5-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSghc-prim-0.2.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSfilepath-1.3.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSdirectory-1.1.0.2-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSdeepseq-1.3.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHScpphs-1.16-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHScontainers-0.4.2.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSbytestring-0.9.2.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSbinary-0.5.1.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSbase-4.5.1.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSarray-0.4.0.0-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
libHSQuickCheck-2.5.1.1-ghc7.4.2.so()(64bit)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(zlib-0.5.4.0-f9a7b27d857d3e506b8524567650abc8)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(xhtml-3000.2.1-290aa859a8b955ebda95b5ca3b1b69f3)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(syb-0.3.7-60af41a2377e93620710d393692aff24)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(process-1.1.0.1-608c248c1528f46eb960a08cead77291)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(pretty-1.1.1.0-91ed62f0481a81d292d550eec35ee75b)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(old-time-1.1.0.0-703543375fafbcbe67bc51a758e84f10)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(mtl-2.1.2-02e701f9b1590ee88a0b5b0bd5d93a29)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(haskell-src-exts-1.13.5-bdba692764e11c662d7ce456e9b0)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(haskeline-0.7.0.3-d7f3ccf9e91c534c80a7d7d408a958c4)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(hashtables-1.0.1.8-83bb853aa7f012eaa447f17f929e2fad)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requires 
ghc(hashable-1.1.2.5-14291f3b4e96b5599759ce7daa2bd37c)
ghc-Agda-2.3.0.1-12.fc20.x86_64 requir

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Jaroslav Reznik
- Original Message -
> - Original Message -
> > On Sat, 2013-06-22 at 22:17 -0700, Adam Williamson wrote:
> > > On Sat, 2013-06-22 at 11:00 -0400, Matthias Clasen wrote:
> > > > On Fri, 2013-06-21 at 14:14 -0700, Adam Williamson wrote:
> > > > 
> > > > > 
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=958426 - "19 Final TC1
> > > > > x86_64 Desktop Live is oversized (larger than 1 GB)" - desktop team
> > > > > (I
> > > > > know you're working on it)
> > > > 
> > > > I've filed an update with some 20 packages, only removing excess
> > > > baggage
> > > > from /usr/share/doc (duplicate docs, large ChangeLog files, etc). It
> > > > touches nothing outside /usr/share/doc, so should be fairly safe to let
> > > > in. That will probably only get us part of the way, so I've also cut
> > > > some more things from the package set in the .ks file
> > > > (gnome-system-log,
> > > > deja-dup).
> > > > 
> > > > If that is not enough, next step will probably be removing some of the
> > > > big font packages.
> > > 
> > > So Matthias forgot to link to his update, but here it is:
> > > 
> > > https://admin.fedoraproject.org/updates/FEDORA-2013-11471/PackageKit-0.8.9-6.fc19,gtk2-2.24.19-2.fc19,evolution-3.8.3-2.fc19,gedit-3.8.2-2.fc19,gnome-session-3.8.2.1-2.fc19,gdm-3.8.3-2.fc19,eog-3.8.2-2.fc19,telepathy-mission-control-5.14.1-2.fc19,yelp-3.8.1-5.fc19,libchamplain-0.12.4-2.fc19,dbus-glib-0.100-4.fc19,libisofs-1.2.8-2.fc19,libxslt-1.1.28-3.fc19,gnome-contacts-3.8.2-2.fc19,gtkmm24-2.24.2-6.fc19,glibmm24-2.36.2-2.fc19,folks-0.9.2-3.fc19,harfbuzz-0.9.18-3.fc19,tracker-0.16.1-3.fc19,libmx-1.4.7-7.fc19
> > > 
> > > It contains changes to some packages not entirely GNOME-y in nature,
> > > inc. dbus-glib and gtk2, so other people might want to give it the
> > > once-over just to make sure there are no inadvertent errors, and upkarma
> > > it assuming it's all good. I am about to test a live compose with the
> > > update to see the impact on image size.
> > 
> > So here's some results.
> > 
> > f2e707287dd82cccb05a3fef6b75cb356744ca58 (Jun 14), no update: 1019215872
> > f2e707287dd82cccb05a3fef6b75cb356744ca58 (Jun 14), update: 1017118720
> > 1a0c28fdf638796bda60ed2785f95eac16a85b65 (Jun 22), update: 1005584384
> > 
> > that is, with the old spin-kickstarts and without the above update,
> > we're 19215872 bytes oversize; with the update but old spin-kickstarts,
> > we're 17118720 bytes oversize (the update saves ~2.1MB); and with the
> > update and latest spin-kickstarts, we're 5584384 bytes oversize (the
> > kickstart changes save ~11.5MB). We still need to find another 5.6MB
> > from somewhere.
> 
> Do we have to be byte strict here? For physical medium sizes, we had to
> be, this 1 GB is more "we set it as we think it's a good idea". Or maybe
> 1 GB sticks (what's the real size one can use + overlay?) but it's not
> as strict, as you could pick up bigger one.

And I'm aware of multi desktop medias - not sure 5 megs means a huge
difference there (and it still makes sense to have some limit +/-).

R.

> R.
> 
> > 
> > Thanks folks!
> > --
> > Adam Williamson
> > Fedora QA Community Monkey
> > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> > http://www.happyassassin.net
> > 
> > --
> > devel mailing list
> > de...@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> --
> devel mailing list
> de...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 19 Final blocker status: fix and karma requests

2013-06-24 Thread Jaroslav Reznik
- Original Message -
> On Sat, 2013-06-22 at 22:17 -0700, Adam Williamson wrote:
> > On Sat, 2013-06-22 at 11:00 -0400, Matthias Clasen wrote:
> > > On Fri, 2013-06-21 at 14:14 -0700, Adam Williamson wrote:
> > > 
> > > > 
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=958426 - "19 Final TC1
> > > > x86_64 Desktop Live is oversized (larger than 1 GB)" - desktop team (I
> > > > know you're working on it)
> > > 
> > > I've filed an update with some 20 packages, only removing excess baggage
> > > from /usr/share/doc (duplicate docs, large ChangeLog files, etc). It
> > > touches nothing outside /usr/share/doc, so should be fairly safe to let
> > > in. That will probably only get us part of the way, so I've also cut
> > > some more things from the package set in the .ks file (gnome-system-log,
> > > deja-dup).
> > > 
> > > If that is not enough, next step will probably be removing some of the
> > > big font packages.
> > 
> > So Matthias forgot to link to his update, but here it is:
> > 
> > https://admin.fedoraproject.org/updates/FEDORA-2013-11471/PackageKit-0.8.9-6.fc19,gtk2-2.24.19-2.fc19,evolution-3.8.3-2.fc19,gedit-3.8.2-2.fc19,gnome-session-3.8.2.1-2.fc19,gdm-3.8.3-2.fc19,eog-3.8.2-2.fc19,telepathy-mission-control-5.14.1-2.fc19,yelp-3.8.1-5.fc19,libchamplain-0.12.4-2.fc19,dbus-glib-0.100-4.fc19,libisofs-1.2.8-2.fc19,libxslt-1.1.28-3.fc19,gnome-contacts-3.8.2-2.fc19,gtkmm24-2.24.2-6.fc19,glibmm24-2.36.2-2.fc19,folks-0.9.2-3.fc19,harfbuzz-0.9.18-3.fc19,tracker-0.16.1-3.fc19,libmx-1.4.7-7.fc19
> > 
> > It contains changes to some packages not entirely GNOME-y in nature,
> > inc. dbus-glib and gtk2, so other people might want to give it the
> > once-over just to make sure there are no inadvertent errors, and upkarma
> > it assuming it's all good. I am about to test a live compose with the
> > update to see the impact on image size.
> 
> So here's some results.
> 
> f2e707287dd82cccb05a3fef6b75cb356744ca58 (Jun 14), no update: 1019215872
> f2e707287dd82cccb05a3fef6b75cb356744ca58 (Jun 14), update: 1017118720
> 1a0c28fdf638796bda60ed2785f95eac16a85b65 (Jun 22), update: 1005584384
> 
> that is, with the old spin-kickstarts and without the above update,
> we're 19215872 bytes oversize; with the update but old spin-kickstarts,
> we're 17118720 bytes oversize (the update saves ~2.1MB); and with the
> update and latest spin-kickstarts, we're 5584384 bytes oversize (the
> kickstart changes save ~11.5MB). We still need to find another 5.6MB
> from somewhere.

Do we have to be byte strict here? For physical medium sizes, we had to
be, this 1 GB is more "we set it as we think it's a good idea". Or maybe
1 GB sticks (what's the real size one can use + overlay?) but it's not
as strict, as you could pick up bigger one.

R.

> 
> Thanks folks!
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> 
> --
> devel mailing list
> de...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19: Galaxy Nexus not working with MTP, does work with PTP

2013-06-24 Thread drago01
On Mon, Jun 24, 2013 at 11:41 AM, Pedro Francisco
 wrote:
> Gnome's MTP support is not working with my Galaxy Nexus. PTP does work.

Seems to work fine here with my Nexus 4
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F19: Galaxy Nexus not working with MTP, does work with PTP

2013-06-24 Thread Pedro Francisco
Gnome's MTP support is not working with my Galaxy Nexus. PTP does work.

 MTP mode ---
usb 2-2: new high-speed USB device number 4 using ehci-pci
usb 2-2: New USB device found, idVendor=04e8, idProduct=685c
usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 2-2: Product: Galaxy Nexus
usb 2-2: Manufacturer: samsung
usb 2-2: SerialNumber: <...>
usb 2-2: USB disconnect, device number 4
 PTP mode ---
usb 2-2: new high-speed USB device number 5 using ehci-pci
usb 2-2: New USB device found, idVendor=04e8, idProduct=6865
usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 2-2: Product: Galaxy Nexus
usb 2-2: Manufacturer: samsung
usb 2-2: SerialNumber: <...>
usb 2-2: USB disconnect, device number 5
 MTP mode ---
usb 2-2: new high-speed USB device number 6 using ehci-pci
usb 2-2: New USB device found, idVendor=04e8, idProduct=685c
usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 2-2: Product: Galaxy Nexus
usb 2-2: Manufacturer: samsung
usb 2-2: SerialNumber: <...>

It worked on F18 with the slower MTP fuse implementation and I was
expecting with the new gvfs-mtp the performance would be on par with
Windows MTP performance, but Gnome (or udev?) seems to be simply
ignoring the device.
It does work on PTP mode.

I've installed gvfs-mtp and I have libmtp which provides
/lib/udev/rules.d/69-libmtp.rules which contains:

(...)
# Samsung Galaxy models (MTP+ADB)
ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", SYMLINK+="libmtp-%k",
ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
(...)

So, what should I do next to get it working?

--
Pedro
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test