Re: Criteria proposal: applying 'post-install' criteria to live and appliance images

[moshe nahmias]

Sounds good

On Wed, Jan 20, 2016 at 5:12 AM, Jared K. Smith 
wrote:

>
> On Tue, Jan 19, 2016 at 8:21 PM, Adam Williamson <
> adamw...@fedoraproject.org> wrote:
>
>> Does this general approach sound good? If so, I'll post some drafts
>> later in the week. Thanks!
>>
>
>
> Sounds great to me.
>
> --
> Jared Smith
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
>
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Re: Blocker Bugs page, Chrome vs Firefox

[moshe nahmias]

Hi Chris,
Just checked with Chrome (on fedora 20) and it works well.

Moshe


On Tue, Aug 19, 2014 at 1:47 AM, Chris Murphy 
wrote:

> Any Chrome users seeing missing header text in the blocker bugs page? I'm
> seeing missing text in Chrome on OS X but not Firefox. It also works in
> Firefox on Fedora. I don't have Chrome on Fedora at the moment.
>
> Ticket here, includes screen shots of what I'm seeing:
> https://fedorahosted.org/fedora-infrastructure/ticket/4491
>
> And this is the URL for the blocker bug tracking page:
> https://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist
>
>
> Chris Murphy
>
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: haddop installation

[moshe nahmias]

Searching for hadoop in yum resulted in some results, did you try to
install those packages? (I don't know hadoop so it might not work, but it
does seem the first thing one should check).


On Wed, Jun 18, 2014 at 6:51 AM, shailendra acharya <
acharyashailend...@gmail.com> wrote:

> hello folks,
> i need to install hadoop on fedora 20 but i am hearing it
> can be done in feodra use ubuntu. well friends i m used to fedora so plz
> provide me path where i can install and use hadoop. thnx and have faith
> that you will look this issue
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 20 Swastika

[moshe nahmias]

I think that it doesn't look like a swastika, but I can understand why some
people think they see it in the picture. The orientation is wrong for the
Nazi symbol. Since the context of fedora is about the absolute opposite of
the Nazi philosophy and the old symbol is also a good one (the one the Nazi
copied from) I don't see why we should not use this picture.

I am a Jew and Israeli if it matters for the discussion.


On Thu, Nov 21, 2013 at 12:39 PM, Ian Malone  wrote:

> On 21 November 2013 07:12, Petr Schindler  wrote:
> > On Čt, 2013-11-21 at 07:57 +0200, Gilboa Davara wrote:
> >> On Tue, Nov 19, 2013 at 9:25 PM, James Patterson
> >>  wrote:
> >> >
> >> > Hello,
> >> >
> >> > I noticed the new Fedora 20 wallpaper looks like a swastika. It would
> be
> >> > great if it didn't for the final release, it would upset a few people.
> >> >
> >> > I filed a bug here under wallpapers, but moved it to distro since
> it's a
> >> > policy decision:
> >> >  https://bugzilla.redhat.com/show_bug.cgi?id=1030643
> >> >
> >>
> >> Hi,
> >>
> >> I do see the swastika, but it you I doubt that I would have seen it
> >> unless I knew what I was looking for.
> >> In my view, given the fact that the image was never designed to
> >> resemble the swastika, there's no reason to change it.
> >
> > Hi,
> >
> > I'm trying to see swastika there but I haven't been able to do so. There
> > is nothing what could be interpreted as swastika. Can someone draw it
> > and send a picture? I think that this thread is totally insane and sad.
> > But it is probably because people always tend to see things they don't
> > like everywhere (like conspiracies).
> >
>
> I'm not convinced having a copy with a swastika drawn on it floating
> around is a good solution to this problem. There are intersecting
> diagonal lines, it doesn't have the characteristic rotational symmetry
> (which made it such a common symbol before it was appropriated). If
> you stare at it long enough you can try and invent the necessary arms,
> but really if we've got lots of people looking at this trying to see
> something and failing then it's not there. Or you're going to have to
> ban diagonals from all future wallpapers.
>
> Not really seeing the H either.
>
> --
> imalone
> http://ibmalone.blogspot.co.uk
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
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 ?

[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.
I understand why there is a need to be able to contact the reporter and ask
for more info, but that can be done by getting your email. If more info is
needed then the system can send mail for more info or something.

BTW, on the page of infrastructure fedora bug tracker I saw there is a need
for perl hackers, I know some perl and want to contribute.

Moshe


On Fri, Nov 1, 2013 at 7:14 PM, Tim Flink  wrote:

> On Fri, 01 Nov 2013 10:12:32 +
> "Jóhann B. Guðmundsson"  wrote:
>
> >
> > On 11/01/2013 10:03 AM, Alexander Todorov wrote:
> > > Hi folks,
> > > recently OpenSource.com published an article of mine explaining why
> > > users should take the extra step to submit a bug:
> > >
> http://opensource.com/business/13/10/user-guide-bugs-open-source-projects
> > >
> > >
> > > It is based on real event, which happened to me during Fedora test
> > > days last month. The comments after the article are very
> > > interesting. Please take a look at them.
> > >
> > >
> > > Re-reading my article and comments today got me thinking if we need
> > > to change something wrt Bugzilla. It appears that users may be
> > > having difficulties with it. Any ideas, comments, rants?
> >
> > There is nothing in that area that is not already known or trying to
> > be addressed.
>
> Apologies if this comes across as me picking on you specifically but one
> of the articles linked from the one Alex wrote was:
>
> http://opensource.com/life/12/3/its-scary-join-open-source-project
>
> I'm not saying that Alex is new, but you could have elaborated a
> bit more or at least been a bit less dismissive in your tone.
>
> "be excellent to each other"
>
> Tim
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Fedora 20 updates-testing report

[moshe nahmias]

I had the same problem, will tell if happens again


On Mon, Oct 7, 2013 at 9:37 PM, Jon Ciesla  wrote:

>
>
>
> On Mon, Oct 7, 2013 at 1:33 PM, Dennis Gilmore  wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> El Mon, 7 Oct 2013 11:07:26 -0500
>> Jon Ciesla  escribió:
>> > My Gmail thinks this is a scam.  Did something change? If not, sorry
>> > for the noise.
>> >
>> > -J
>> Nothing has changed in how, or where its made
>>
>> Fascinating.
>
> I'll see if it flags the next one, or rawhide.
>
> -J
>
>
>> Dennis
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.21 (GNU/Linux)
>>
>> iEYEARECAAYFAlJS/pUACgkQkSxm47BaWfeMKACdELPriq6yz0TWT8WThobuTTyl
>> pb4AnAv9TQPmHrzI+D3KA95DqfUTWwEH
>> =S0HK
>> -END PGP SIGNATURE-
>> --
>> test mailing list
>> test@lists.fedoraproject.org
>> To unsubscribe:
>> https://admin.fedoraproject.org/mailman/listinfo/test
>
>
>
>
> --
> http://cecinestpasunefromage.wordpress.com/
> 
> in your fear, seek only peace
> in your fear, seek only love
>
> -d. bowie
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Gnome 3.10: Network UI missing from new system status area

[moshe nahmias]

I think that it must be possible to make the icon visible as an option. I
use a cellular modem on my laptop and the easiest way to connect with it to
the net is by clicking that icon...
I guess that it's possible to connect from other places, but it won't be as
easy.


On Fri, Oct 4, 2013 at 8:48 AM, John Morris  wrote:

> On Thu, 2013-10-03 at 20:59 +0200, drago01 wrote:
> > You should get an icon indicating failure just no success one. Which
> > is even very unixy ;)
>
> Well GNU is Not Unix and these days Fedora isn't even following that
> star.  How does Apple do it?
>
> Screen space is valuable so removing an icon that is 'always' there and
> isn't typically displaying useful information is sensible enough.  But
> as the bug commenters noted, some people DO move between wired
> connections and such so an option to put it back really needs a bit of
> thought.  And your idea that if anything goes wrong, loss of link,
> failure to acquire a lease, etc. it should put up a no-net icon is very
> good since these days no-network is the odd case, probably an error
> state and almost always something the user wants to know about.  Better
> still of course if it has a tooltip with useful information.
>
> Any move to remove it with zero option should be a position that needs
> defending first, not something one person imposes from on high.  If for
> no other reason than it is going to surprise people so some awareness
> building is probably a good idea.
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Bug report with private info

[moshe nahmias]

Christopher, I think he meant about the feature that the ABRT will say
which fields are the fields are the private fields that is shown.
Kamil, am I right?

With regards, Moshe


On Tue, Aug 20, 2013 at 1:09 PM, Christopher Meng wrote:

> 在 2013-8-20 PM5:48，"Kamil Paral" 写道：
>
> > Definitely. I also miss this in ABRT. Could you please file a bug report
> and link it here?
>
> It's my bug related to gdm.
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Bug report with private info

[moshe nahmias]

Isn't it possible to list all the fields of the sensitive data?
That way it will be easier for the user to see which data is compromised
and at the very least the user won't have to go through all the data
transmitted just to see that the user name is the only sensitive info
that's sent.
It is easier that way to find if the password is there too for example,
it's harder to find the needle in the haystack if the data is not organized.

Moshe


On Fri, Aug 16, 2013 at 10:43 PM, Adam Williamson wrote:

> On Thu, 2013-08-15 at 12:09 +0100, Pedro Francisco wrote:
> > On Mon, Aug 12, 2013 at 2:39 PM, Adam Williamson 
> wrote:
> > > On Mon, 2013-08-12 at 13:03 +0100, Pedro Francisco wrote:
> > >> Hello!
> > >> I found a bug report with possible private info on it.
> > >>
> > >> What should I do?
> > >>
> > >> 1- Contact bugzilla admin to remove the attachment?
> > >> 2- Contact the owner of the bug and warn him of it?
> > >> 3- Both?
> > >
> > > Not quite sure what you mean by 'private info', but definitely do
> > > something - you mean it exposes the user's secrets? Definitely do #2
> and
> > > if it's really urgent do #1 at the same time. Anyone with editbugs
> > > privileges can mark a comment as private which at least limits the
> > > number of people who could see the secret data, so you can contact
> > > anyone you trust who's a package maintainer or has editbugs privs
> > > through the old triage group or something (including me, and many
> others
> > > on this list) and ask if they can mark the attachment as private, too.
> >
> >
> > Now that the issue is taken care of, should a bug be open to prevent
> > something like this to happen again? I know ABRT has a notice saying
> > 'possible private info detected, please review', but usually it's just
> > the username...
>
> Perhaps abrt could warn harder if the detected field is something that
> may be a password rather than a username. Like you I've gotten rather
> blase about that warning since it started showing up for usernames;
> classic example of the 'false positive' problem for security
> mechanisms...
> --
> 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
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Picture of Wifi Readout

[moshe nahmias]

Does the 5GH work on fedora 18 or any other OS? (we need to make sure it's
not a hardware problem first)


On Fri, May 3, 2013 at 10:56 PM, Lawrence Graves wrote:

>  Just so you can see what is happening. My card is seeing both the 2.4
> and the 5ghz channels. The HolySpirit1 is 2.4 and HolySpirit2 is 5ghz. It
> will connect to the 2.4 but not the 5.
> --
> All things are workable but don't all things work. Prov. 3:5 & 6
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Network Manager Problems

[moshe nahmias]

I didn't understand what is your problem, you say that you replaced the
card before checking with fedora 18, so if the problem is with the card how
can you know it?
try with the same card to work with fedora 18 (the same card meaning the
same configuration and all between the tries).
If you can't make it work on fedora and don't know if it works at all on
what ever version you can get hold of you can try windows just to make sure
(even though I don't trust windows to work anyway :) )


On Fri, May 3, 2013 at 3:29 PM, Lawrence Graves  wrote:

>  I have reported the fact that I am having trouble with connecting to my
> 5ghz wifi to bugzilla. Was that the place to report. If not where do I
> report this problem. I am running Fedora 19 Beta TC2 on Dell 9400
> Inspiron with iwl4965 card which handles 2.4ghz and 5ghz bands. I replaced
> the card and then installed Fedora 18 and it worked fine so that told me it
> was not my card but problem with network manager.
> --
> All things are workable but don't all things work. Prov. 3:5 & 6
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Blocker Tracking App Moving to Production

[moshe nahmias]

Hi,
Just looking on the app and found that the updates don't work, it gives
this error-
Internal Server Error

The server encountered an internal error and was unable to complete your
request. Either the server is overloaded or there is an error in the
application.

it's suppose to be a 500 error according to the title of the page


On Mon, Apr 29, 2013 at 4:10 PM, Tim Flink  wrote:

> On Mon, 29 Apr 2013 05:28:43 -0400 (EDT)
> Kamil Paral  wrote:
>
> > > The blocker tracking app is moving to production today and the
> > > upgrade should be seamless from a users' perspective.
> >
> > The IRC format doesn't display newlines properly, one has to display
> > the page source:
> > https://qa.fedoraproject.org/blockerbugs/milestone/19/beta/irc
>
> Honestly, it never has. I've
> > Maybe it would be better to serve it as an HTML page with the text
> > confined in  tag? Or the web server needs to serve it as
> > text/plain.
>
> I don't want to make the page HTML because that breaks my existing
> workflow with wget - that link has been around pretty much as long as
> the app has, it just hasn't been visible until now.
>
> I'll poke at changing the mime-type, though. I honestly hadn't thought
> of trying that since I always used wget for the data.
>
> > And one more cosmetic detail, the Propose Bug page doesn't have any
> > title.
>
> Thanks, hadn't noticed that before - should be an easy fix.
>
> Tim
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Updates for f19?

[moshe nahmias]

OK, so how do I learn it? I guess it can help me to help in this team
anyway :)
On the wiki syntax I think I can see what you have done to learn from if
not anywhere else (and I know a bit from elsewhere)


On Wed, Apr 24, 2013 at 3:06 AM, Adam Williamson wrote:

> On 23/04/13 12:20 PM, moshe nahmias wrote:
>
>> Is there any needed knowledge for doing this? I don't know (at least
>> yet) most of what is needed most likely but can do it time wise. If
>> there is a link to learn what's needed then I can do it (any way I will
>> ask here for improvements but its better if I will know what I am doing
>>   )
>>
>
> Well, the needed knowledge is 'how Branched actually works', obviously :)
> Beyond that all you'd really need is basic Wiki syntax.
> --
> 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<https://admin.fedoraproject.org/mailman/listinfo/test>
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Updates for f19?

[moshe nahmias]

Is there any needed knowledge for doing this? I don't know (at least yet)
most of what is needed most likely but can do it time wise. If there is a
link to learn what's needed then I can do it (any way I will ask here for
improvements but its better if I will know what I am doing [?]
 )


On Tue, Apr 23, 2013 at 8:48 PM, Kevin Fenzi  wrote:

> On Mon, 22 Apr 2013 08:55:26 -0400 (EDT)
> Jaroslav Reznik  wrote:
>
> > Branch Freeze Policy page got outdated with not following freeze from
> > branch time anymore, I marked it there but otherwise it's pretty nice
> > described there. I tried to add a few details regarding it to Change
> > Deadline page but it's also not a best place where to put it.
> >
> > Are there any more places where we can put the info? Or create a new
> > one? As this is quite important part of release process and it's
> > really time to make it clear and correct. I'll take care of it - and
> > I'm open to any ideas how to make it usuable ;-).
>
> We really need to revamp the "Branched" page:
>
> http://fedoraproject.org/wiki/Releases/Branched
>
> I started to, but ran low on time. :) I guess I can try again.
>
> Really I think best would be to take my re-done Rawhide page
> ( http://fedoraproject.org/wiki/Releases/Rawhide ) and fill out a new
> Branched one the same format/way, and then go and add branch specific
> stuff (like the cycle and what happens where, etc).
>
> Would someone like to do that? Or I can try and find the time...
>
> kevin
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
<<328.png>>-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

Thanks to Kamil, Adam, Eric, stephen, Dennis and anyone else that thought
on how to help me. Problem solved after I enabled vt-d and UEFI.
My guess is that when not working with UEFI the OS didn't recognize the
possibility of working with virtualization for some reason. I will check
that on my next reboot if I will remember to.

Now the system is installed, but I can't get to the display manager, I
installed the mate desktop. Is this a known issue or should I submit a bug
report? What info is needed?


On Sat, Apr 20, 2013 at 9:29 AM, Phil Dobbin  wrote:

> On 04/19/2013 09:15 PM, moshe nahmias wrote:
>
> > According to what intel says my processor does support virtualization
> > (model Q9400). Wasn't able to update the bios yet, can't make a bootable
> > cd with the files needed, and on capabilities from lshw says among other
> > things vmx (at least on other places on this thread people said that
> > means virtualization).
> >
> > about cat /proc/cpuinfo |grep -E "flags|model name", here is the output:
> >
> > [moshe@moshe-desktop ~]$ cat /proc/cpuinfo |grep -E "flags|model name"
> > model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
> > flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
> > nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni
> > dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm dtherm tpr_shadow vnmi flexpriority
> > model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
> > flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
> > nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni
> > dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm dtherm tpr_shadow vnmi flexpriority
> > model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
> > flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
> > nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni
> > dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm dtherm tpr_shadow vnmi flexpriority
> > model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
> > flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
> > nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni
> > dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm dtherm tpr_shadow vnmi flexpriority
> >
> >
>
> Yep, the 'vmx' flag shows the cpu is capable of virtualization. Check
> the BIOS next. There should be an option to enable VT-x although on some
> models, even if they're capable of it, it's impossible to enable (for
> reasons best known to the vendors).
>
> Cheers,
>
>   Phil...
>
> --
> currently (ab)using
> CentOS 5.9 & 6.4, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
> Lubuntu 12.10, OpenSuSE 12.3, OS X Snow Leopard & Ubuntu Precise & Quantal
> GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

According to what intel says my processor does support virtualization
(model Q9400). Wasn't able to update the bios yet, can't make a bootable cd
with the files needed, and on capabilities from lshw says among other
things vmx (at least on other places on this thread people said that means
virtualization).

about cat /proc/cpuinfo |grep -E "flags|model name", here is the output:

[moshe@moshe-desktop ~]$ cat /proc/cpuinfo |grep -E "flags|model name"
model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
dtherm tpr_shadow vnmi flexpriority
model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
dtherm tpr_shadow vnmi flexpriority
model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
dtherm tpr_shadow vnmi flexpriority
model name: Intel(R) Core(TM)2 Quad CPUQ9400  @ 2.66GHz
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
dtherm tpr_shadow vnmi flexpriority


On Fri, Apr 19, 2013 at 9:50 PM, Dennis Jacobfeuerborn <
denni...@conversis.de> wrote:

> On 19.04.2013 20:12, moshe nahmias wrote:
>
>> I have VT and VT-d on my bios, I enabled VT both and it doesn't help.
>> When I try to use the command eric gave (thanks for that) I have the
>> same problems with VT and VT-d enabled or disabled.
>> When I enabled VT-d I had an error from abrt that said that most likely
>> my bios weren't configured right so now only VT is enabled.
>>
>>
> Please post the model name and flags of your processor:
> cat /proc/cpuinfo |grep -E "flags|model name"
>
> That will make it much easier to determine what your CPU can do.
>
> Regards,
>   Dennis
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.**org/mailman/listinfo/test<https://admin.fedoraproject.org/mailman/listinfo/test>
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

I have VT and VT-d on my bios, I enabled VT both and it doesn't help.
When I try to use the command eric gave (thanks for that) I have the same
problems with VT and VT-d enabled or disabled.
When I enabled VT-d I had an error from abrt that said that most likely my
bios weren't configured right so now only VT is enabled.

The result of virt-host-validate is (its the same for VT/VT-d enabled or
disabled):
  QEMU: Checking for hardware
virtualization : PASS
  QEMU: Checking for device
/dev/kvm : FAIL (Check that the
'kvm-intel' or 'kvm-amd' modules are loaded & the BIOS has enabled
virtualization)
  QEMU: Checking for device
/dev/vhost-net   : WARN (Load the
'vhost_net' module to improve performance of virtio networking)
  QEMU: Checking for device
/dev/net/tun : PASS
   LXC: Checking for Linux >=
2.6.26 : PASS

My problem now is that I don't know how to enable kvm-intel (my proccessor
is intel branded, so I guess I need kvm-intel, right?). Tryed with modprobe
but it says opperation not supported, so what is the right command and is
this the right way to go (at least as far as we know from that info)?


On Fri, Apr 19, 2013 at 8:13 PM, Adam Williamson wrote:

> On 19/04/13 10:04 AM, Stephen John Smoogen wrote:
>
>>
>>
>>
>> On 19 April 2013 03:58, moshe nahmias > <mailto:mosheg...@gmail.com>> wrote:
>>
>> I checked the sha and it matches the one on the site, so I guess
>> thats not the problem. thanks for the try.
>>
>> I just installed libvirt-daemon-kvm and qemu-kvm and still can't
>> work with kvm.
>> It says that KVM is not available. What should I install so I will
>> have it?
>>
>>
>>
>> Does the CPU have the proper KVM flags? I have a Pentium(R) Dual-Core
>>   CPU  E5300 which turned out not to have the VMX flags but other models
>> did (for some reason Intel sold a series of CPU's that had vmx burnt out
>> on it for some reason..)
>>
>
> They disabled VT-d on lower-end CPUs for some time as a market
> differentiation tactic (you need virt, you pay more).
>
> --
> 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<https://admin.fedoraproject.org/mailman/listinfo/test>
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

I checked the sha and it matches the one on the site, so I guess thats not
the problem. thanks for the try.

I just installed libvirt-daemon-kvm and qemu-kvm and still can't work with
kvm.
It says that KVM is not available. What should I install so I will have it?


On Fri, Apr 19, 2013 at 12:01 PM, Kamil Paral  wrote:

> > When I open the virtual machine and go to view->details on overview
> details
> > are as follows:
> > Hhpervisor: qemu
>
> I believe this is the source of the problem. You should use kvm, not qemu.
> KVM is the default option.
>
> QEMU is so slow, that it takes 10 minutes on my Core i7 just to begin
> starting of GDM. I had no more patience. I guess that the mounting process
> somehow times out on your system.
>
> Always use KVM. Also try to increase the RAM. If the problem remains,
> please post a screenshot with the exact error messages.
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

I didn't do anything special.
When I open the virtual machine and go to view->details on overview details
are as follows:
Hhpervisor: qemu
architecture: 64 bit
emulator: /usr/bin/qemu-system-x86_64

operating system
host name: unknown
product name: unknown

machine settings
enable acpi: checked
enable apic: checked
clock offset: utc

security
model: selinux
type: dynamic checked

cpu allocation 1
memory allocation 1024 MB

boot options
CD-ROM, hard disk are checked

virtual hard disk
size 20 gigs.
disk bus: IDE
storage format: raw

performance options
cache mode: default
i/o mode: default
IO tuning
everything on 0

virtual CD-ROM
the same as hard disk except for source path, the source path is to the
image of the fedora image I downloaded and in the link above.

virtual network
source device: virtual network 'default': NAT
device model: hypervisor default

display (spice server)
type: spice
address: 127.0.0.1
port and TLS port: automatically allocated
password: (no password)
key map: auto

sound device
ich6

serial device (none)

channel device
device type: spicevmc
target type: virtio
target name: com.redhat.spice.0

video QXL
model: QXL
ram: 64 MB
heads: 1

controller usb
type: usb
model: default

controller IDE
type: IDE
model: default

controller virtio serial
type: virtio serial
model: default

that's the end of it.
Is this what you wanted to know? if not then where can I get what you need
to know so you will be able to help?

anyway, Adam and Kamil, thanks for trying (and hopefully succeeding later
on) to help me


On Thu, Apr 18, 2013 at 11:53 PM, Adam Williamson wrote:

> On 18/04/13 02:07 AM, moshe nahmias wrote:
>
>> Hi,
>> I tried to install Fedora-19-Alpha-i386-DVD.iso
>> <http://dl.fedoraproject.org/**pub/alt/stage/19-Alpha-RC4/**
>> Fedora/i386/iso/Fedora-19-**Alpha-i386-DVD.iso<http://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC4/Fedora/i386/iso/Fedora-19-Alpha-i386-DVD.iso>
>> >
>>
>> from the link above on virt on fedora 18.
>> The install don't work.
>> It says that dracut-initqueue[284] could not boot because /dev/root
>> doesn't exist.
>>
>> 1. Is there anything I should do to install the system exept running
>> virt (It says while making the machine that it install the system)? how
>> do I install the system on virt?
>>
>> 2. If its a bug then what should I upload to help debugging?
>>
>
> How *exactly* did you set up your test VM?
>
> --
> 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<https://admin.fedoraproject.org/mailman/listinfo/test>
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

I run virt via the graphic menu on mate.
I use the default installation of virtual machine manager (as far as I
remember) version number 0.9.5.

Since I am pretty sure I didn't give the details you want...
What exactly do you want to know? And how to get the info?


On Thu, Apr 18, 2013 at 4:08 PM, Kamil Paral  wrote:

> > Hi,
> > I tried to install Fedora-19-Alpha-i386-DVD.iso from the link above on
> virt
> > on fedora 18.
> > The install don't work.
> > It says that dracut-initqueue[284] could not boot because /dev/root
> doesn't
> > exist.
>
> What virt tools do you use? How do you run it?
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

Another bit of info.
Is it possible that it's because I use QEMU on my virt?
If so, than how can I use something else?

I am new at this, so a link to somewhere I can learn about it will be
appreciated.

Moshe


On Thu, Apr 18, 2013 at 12:07 PM, moshe nahmias  wrote:

> Hi,
> I tried to install 
> Fedora-19-Alpha-i386-DVD.iso<http://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC4/Fedora/i386/iso/Fedora-19-Alpha-i386-DVD.iso>from
>  the link above on virt on fedora 18.
> The install don't work.
> It says that dracut-initqueue[284] could not boot because /dev/root
> doesn't exist.
>
> 1. Is there anything I should do to install the system exept running virt
> (It says while making the machine that it install the system)? how do I
> install the system on virt?
>
> 2. If its a bug then what should I upload to help debugging?
>
> Moshe
>
>
> On Thu, Apr 18, 2013 at 11:07 AM, Joerg Lechner  wrote:
>
>>  Hi,
>>  " 
>> Fedora-Live-LXDE-i686-19-Alpha-1.iso<https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC4/Live/i386/Fedora-Live-LXDE-i686-19-Alpha-1.iso>17-Apr-2013
>>  02:24 709M
>> ", this build seems to be the same code as the last build(s). Successful
>> boot not possible on a Samsung X22 laptop.
>> Kind Regards Joerg
>>
>>
>>  -Ursprüngliche Mitteilung-
>> Von: Andre Robatino 
>> An: test-announce 
>> Verschickt: Mi, 17 Apr 2013 9:33 pm
>> Betreff: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4)
>> Available Now!
>>
>>
>>  NOTE: All DVD and Live images except KDE Live and SoaS Live are still
>> oversize (as they have been since 19 Alpha TC3).
>>
>> As per the Fedora 19 schedule [1], Fedora 19 Alpha Release Candidate 4
>> (RC4) is now available for testing. Content information, including
>> changes, can be found 
>> athttps://fedorahosted.org/rel-eng/ticket/5545#comment:25 . 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 priority test cases for Installation [2], Base [3],
>> and Desktop [4] should pass in order to meet the Alpha Release Criteria
>> [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the
>> test list [7].
>>
>> Create Fedora 19 Alpha test composes (TC) and release candidates 
>> (RC)https://fedorahosted.org/rel-eng/ticket/5545
>>
>> 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_Alpha_Release_Criteria
>> [6] irc://irc.freenode.net/fedora-qa
>> [7] https://admin.fedoraproject.org/mailman/listinfo/test
>>
>>  ___
>> test-announce mailing 
>> listtest-announce@lists.fedoraproject.orghttps://admin.fedoraproject.org/mailman/listinfo/test-announce
>>
>>  --
>> test mailing listt...@lists.fedoraproject.org
>> To unsubscribe:https://admin.fedoraproject.org/mailman/listinfo/test
>>
>>
>> --
>> test mailing list
>> test@lists.fedoraproject.org
>> To unsubscribe:
>> https://admin.fedoraproject.org/mailman/listinfo/test
>>
>
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!

[moshe nahmias]

Hi,
I tried to install
Fedora-19-Alpha-i386-DVD.isofrom
the link above on virt on fedora 18.
The install don't work.
It says that dracut-initqueue[284] could not boot because /dev/root doesn't
exist.

1. Is there anything I should do to install the system exept running virt
(It says while making the machine that it install the system)? how do I
install the system on virt?

2. If its a bug then what should I upload to help debugging?

Moshe


On Thu, Apr 18, 2013 at 11:07 AM, Joerg Lechner  wrote:

>  Hi,
>  " 
> Fedora-Live-LXDE-i686-19-Alpha-1.iso17-Apr-2013
>  02:24 709M
> ", this build seems to be the same code as the last build(s). Successful
> boot not possible on a Samsung X22 laptop.
> Kind Regards Joerg
>
>
>  -Ursprüngliche Mitteilung-
> Von: Andre Robatino 
> An: test-announce 
> Verschickt: Mi, 17 Apr 2013 9:33 pm
> Betreff: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4)
> Available Now!
>
>
>  NOTE: All DVD and Live images except KDE Live and SoaS Live are still
> oversize (as they have been since 19 Alpha TC3).
>
> As per the Fedora 19 schedule [1], Fedora 19 Alpha Release Candidate 4
> (RC4) is now available for testing. Content information, including
> changes, can be found 
> athttps://fedorahosted.org/rel-eng/ticket/5545#comment:25 . 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 priority test cases for Installation [2], Base [3],
> and Desktop [4] should pass in order to meet the Alpha Release Criteria
> [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the
> test list [7].
>
> Create Fedora 19 Alpha test composes (TC) and release candidates 
> (RC)https://fedorahosted.org/rel-eng/ticket/5545
>
> 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_Alpha_Release_Criteria
> [6] irc://irc.freenode.net/fedora-qa
> [7] https://admin.fedoraproject.org/mailman/listinfo/test
>
>  ___
> test-announce mailing 
> listtest-announce@lists.fedoraproject.orghttps://admin.fedoraproject.org/mailman/listinfo/test-announce
>
>  --
> test mailing listt...@lists.fedoraproject.org
> To unsubscribe:https://admin.fedoraproject.org/mailman/listinfo/test
>
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: kernel-3.8.2-206.fc18.x86_64

[moshe nahmias]

My wireless card on my laptop is BCM4313 but I didn't update to 3.8.2, is
it on update-testing?
If it is I will start using update-testing on the laptop at least for help
on this one

On Tue, Mar 12, 2013 at 11:41 AM, Ankur Sinha wrote:

> On Mon, 2013-03-11 at 22:09 -0400, ergodic wrote:
> > Ankur thanks for for you repliy.
> > I will hold until next kernel update and if the problem persist
> > I will BZ it. In the interim I will try to debug the boot failure
> >
> > Best regards
>
> No worries.
>
> To keep this thread going, are there any BCM4313 (Broadcom 4313 wifi)
> users here? Has anyone had trouble using wifi recently with this kernel?
> I can't seem to get a stable connection to some wifi networks. Relevant
> bug filed here: https://bugzilla.redhat.com/show_bug.cgi?id=920480
>
> It's pretty troublesome. I'm back to 3.8.1-201.fc18.x86_64 for the time
> being.
> --
> Thanks,
> Warm regards,
> Ankur: "FranciscoD"
>
> Please only print if necessary.
>
> Looking to contribute to Fedora? Look here:
> https://fedoraproject.org/wiki/Fedora_Join_SIG
>
> http://fedoraproject.org/wiki/User:Ankursinha
> http://dodoincfedora.wordpress.com/
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Major criteria re-write / re-design proposal

[moshe nahmias]

I like better the grey background with normal text, it makes the lines
easier to find and breaks the monotonous white background.
On the other hand it's a matter of taste more then anything.

On Mon, Mar 11, 2013 at 5:17 PM, Kamil Paral  wrote:

> > I'm not fully convinced on the presentation style, I find the
> > collapsible comments to be more visible than the criteria themselves
> > (they are bold and highlighted, so they draw more attention), but
> > that's something that we can tweak easily.
>
> I tried to come up with a few more designs of the collapsible comments:
>
> https://fedoraproject.org/wiki/User:Kparal/Draft_Alpha_Criteria
>
> There are four styles in the document:
> 1. transparent background, italic
> 2. gray background, normal weight
> 3. transparent background, gray bold text
> 4. adam's original - bold text on violet (please forgive my
> colorblindness, if it's a different color)
>
> Ideas? The first one seems clean, visible and non-intrusive to me.
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Major criteria re-write / re-design proposal

[moshe nahmias]

Hi,

Looks good, but I do have 2 things, one that isn't clear to me and one
suggestion to make things clearer.

On the "Alpha Release Requirements" paragraph, there is the sentence
"Mostly met items are incomplete until they are met.", what does it mean?
Or is it the obvios, that most of the criterions are incomplete till we
stumble on them?

On the "Package sets" paragraph, it says "the installer must be able to
install each of the release blocking desktops, as well as the minimal
package set.".
And on the "not all at once it says that you should be able to install KDE,
Gnome, and minimal set but not necesarily all at once", does it mean that
it's OK to be able to install just one of the desktops or that you must be
able to install all of them but not necesarily on the same boot?

If the former is the right one (at least one works) than I have a revision
to make, I think it will be clearer to say that "the installer must be able
to install at least one of the release blocking desktops".

Hope it helps. Moshe

On Sat, Mar 9, 2013 at 3:24 AM, Adam Williamson  wrote:

> Hi, folks. So I've been working on this for a while, but we're getting
> close to F19 Alpha time and I really want to get it out there for
> comments.
>
> Several people have noted that the release criteria have grown quite a
> lot over time. Just compare F13 and F18:
>
> https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria
> https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria
>
> Individually, all the changes have been good ones that made sense, but
> the sum effect of them is that the criteria have turned into a bit of a
> Wall-O-Text. It's also true that we've kind of slipped in quite a few
> things that 'make sense if you already know what they mean' - some of
> the legalistic wording can be a bit confusing if you don't know the
> history of what it's doing there.
>
> So I've been trying to come up with some major changes to the criteria
> for F19, incorporating all the ideas that have come up in meetings,
> retrospective etc. I see there being, broadly, three strands to this:
>
> 1) Some major revisions to the wording of the actual criteria themselves
> 2) Addition of 'metadata' on some criteria
> 3) Change in the layout/presentation/design of the criteria pages
>
> So bearing in mind that this is something that combines *all three of
> the above*, here's what I have so far. I have only done the Alpha page
> for now:
>
> https://fedoraproject.org/wiki/User:Adamwill/Draft_alpha_criteria_sandbox
>
> Basically, what I've done is:
>
> DESIGN STUFF
> 
>
> * group the criteria into a few sections, and made (almost) each
> individual criterion a sub-section - this might seem a bit odd at first,
> but it breaks up the 'wall of text' flow, makes the table of contents
> more useful, and gives us stable 'anchors' to link and refer to specific
> criteria. Previously they were one big numbered list, but we kept
> changing the numbers. In just a couple of places I put two or three
> criteria together in a sub-category, where it seemed to make sense (e.g.
> 'Expected installed system boot behaviour', which is a group of very
> closely inter-related criteria).
>
> * Split off the more laborious legalistic bits of various criteria into
> separate paragraphs hidden behind 'hide/show' bars. This lets us make
> the basic, always-visible criterion text short, simple and clear, and
> keep the legalistic exception stuff at a lower level; it should make the
> basic intent of the criteria easier to read, reduce the wall-o-text
> effect, and make it easier for non-experts to see what criteria apply to
> issues.
>
> 'METADATA'
> --
>
> * Overlaps with the second point above - the 'clarification' paragraphs
> are part of what I'm talking about as metadata. Some of these I just
> separated out from existing wording; some I added, as the new design
> lets us add quite a lot of 'metadata' without making the basic flow of
> the page too long and messy. The 'Supported images must boot' section is
> a good idea. We can also write the 'metadata' is a less tortured way
> since we're not trying to keep it short; I tried to go with a sort of
> relaxed, chatty, conversational style.
>
> * I also added References for a lot of the criteria: for now I've tried
> to find the list discussions where criteria were added and/or modified,
> and called out a couple of significant discussion threads and bugs. We
> could, of course, add far more of these. I think it'll be pretty helpful
> for the case where you're looking at a criterion and thinking 'why do we
> have that?' - the References section will point you right at the answer.
> It does stretch things out design-wise, though.
>
> REWORDING
> -
>
> * As noted above, a lot of the rewording was simply to break off the
> legalistic stuff into separate, hidden paragraphs and rewrite the basic
> criteria to be clear and simple.
>
> * I also did some major tweaking of a few criteria, tho

Re: FreezeException process improvement - proposal

[moshe nahmias]

May be I didn't understand you right or I don't understand the whole point
of FE so tell me if I'm wrong.

As I understand it your proposal is that a bug that no one is willing to
fix can't be a FE, right?
If that's the case then I think it's wrong, since there are bugs that can
be important enough for FE even if there is no one that is willing to fix
it.

And one more thing, what is SOP? is there a wiki for the acronyms that are
used so I won't have to bother you with those questions too often?

Moshe

On Fri, Mar 8, 2013 at 2:19 PM, Kamil Paral  wrote:

> > I can see where you're going with this, but I do have a few concerns.
> >
> > I really don't want to rely on the web front end for blocker
> > proposal.
> > At least not *yet*. Right now its status is that of an 'experimental
> > front end to existing processes'. We were pretty solid in discussions
> > (maybe more in person than on list, I don't recall) that the web app
> > should just do stuff you can also do manually: it's just a
> > convenience.
> >
> > Maybe in future if it works well and people are happy with it we can
> > start to refine the process in ways where 'manual' submission isn't
> > plausible and we have to rely on helper frontends like the webapp,
> > but
> > I'm not sure we're at the point to start doing that yet. Especially
> > *now*, for Fedora 19.
>
> I never intended to say that the web app is necessary for the process to
> work. If it is down, all of my proposed work-flow can be done by hand. If
> it is not ready by Fedora 19, we don't have to use it at all. The bugzilla
> messages won't be so pretty and unified, but the core of the proposal was a
> different nomination process, not directly tied to the web app.
>
> If we change the SOP and the web app is not ready, it will not be so
> straightforward, but hey, that's it. The user can still contact the
> developer via bugzilla or IRC ask him to nominate the particular bug for a
> freeze exception. The developer can still tag the bug and provide
> justification in the comment. Just the crutches are not there. (By the way,
> the last few sentences was a TL;DR version of my whole proposal, minus the
> web app adjustments).
>
>
> >
> > You addressed this to some extent, but I'd like the proposal to be
> > much
> > more specific and much less hand-wavy about the 'FreezeException as a
> > priority list' case. Practically speaking, we do not use the priority
> > field in Bugzilla at all; FE status does act as a somewhat useful
> > proxy
> > for 'this bug is probably pretty important'. It's not meant to do
> > that,
> > but it kind of does. We - that is, QA - should definitely be manually
> > eyeballing proposed FE bugs, even if we aren't formally evaluating
> > all
> > of them.
>
> Sorry, I don't follow you here. What exactly is hand-wavy and how is it
> connected to priorities?
>
> I'd like to decouple the FE list from the "probably important issue" list.
> Currently people go through bugzilla and do: "this seems important - mark;
> this as well - mark; mark mark mark". I know it, because I do it too. But
> this brings us heavy burden.
>
> That's why in my proposal the FE list is a list of bugs that developers
> are really willing to work on in the remaining short timeframe. That trims
> the list substantially.
>
> In order to still have a list of "good to eyeball" bugs, I proposed a
> different QAWatchList tracker. So next time I or anybody else has a tagging
> frenzy,  they will populate QAWatchList instead of FE list. Because those
> are decoupled, we won't have a heap of
> probably-important-but-incomplete-information bugs to go through on the
> next blocker bug meeting.
>
>
> >
> > Finally, I think some of the problems identified in your mail are
> > more
> > F18 artifacts than ongoing things. My recollection is that we managed
> > to
> > do NTH evaluation pretty well in cycles prior to F18: it was only due
> > to
> > the massive blocker load in F18 that we got substantially behind on
> > NTH
> > evaluation.
>
> I agree here, because of F18 delays we had much more FE bugs to go through
> compared to previous releases. But... this is not strictly relevant to
> release quality. This is more relevant to the _people_ evaluating the bugs.
> If a new person joins Fedora QA and is very passionate and active, we can
> have dozens of FE bugs tagged in a single week. Will we forbid him to do
> so? Or will we improve the process?
>
> I, personally, often don't tag mildly important bugs as FEs, because I
> don't want to increase our load when I know there's 99% chance that no one
> will fix the issue anyway. I've nearly given up on nominating FEs in the
> last cycle. That's a process failure in my eyes.
>
> To sum up, we fail in the notion what FE-nominated bug really is.
> Currently we say that FE-nominated bug is any bug that any single Fedora
> community person considers as such. I'm trying to suggest that FE-nominated
> bug is any bug that has a voiced developer support (i.e. "I am Chuck

Re: Bugzappers

[moshe nahmias]

I am new here (at least relatively :) ).
didn't contribute yet but hope to start soon as time permits.

About your questions I don't have any opinions yet.

Moshe

On Wed, Feb 27, 2013 at 4:02 AM, William Morris wrote:
>
>> Hi all,
>>
>> I am looking for input from current Bugzappers, as we all know our group
>> is being folded into the QA group. I want to know first off who is still
>> around. I know that we are an inactive group right now, but that is okay.
>>
>> I am also looking for input on a couple of fronts. First is that I am
>> interested in knowing what people think about our documentation. We have a
>> lot of it and I think that it is all good, but we have a crap load of
>> documentation. I know that when I triage a bug, I only use a couple
>> different documents. So I am wondering if we want to keep all of it or if
>> it needs to be reformatted.
>>
>> My second question is that I want to know what people think about the
>> move? I realize that we may not have a lot of say in the matter but I still
>> want to hear what you think.
>>
>> Thanks for reading this and I look forward to reading and responding to
>> you all.
>>
>> --
>> Will Morris
>> Bugzapper, Amabasador
>> irc: wmorri
>>
>>
>> --
>> test mailing list
>> test@lists.fedoraproject.org
>> To unsubscribe:
>> https://admin.fedoraproject.org/mailman/listinfo/test
>>
>
>
>
> --
> projecthuh.com
> Never underestimate the carelessness of boredom...
> Most people prefer Windows because most people are idiots...
>
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Proposing Blocker/Freeze Exception Bugs Through the Blocker Tracking App

[moshe nahmias]

On Wed, Feb 13, 2013 at 1:48 AM, Adam Williamson wrote:

> On 07/02/13 02:00 AM, Kamil Paral wrote:
>
>> OK, I think its being my mistake...
>>> Is the bug id section is to define which bug is the blocker/freeze
>>> exception?
>>> If so then my comment is wrong on my part.
>>>
>>
>> This is a good feedback. When I think about it, the label could be much
>> clearer if we use "Proposed bug number" (or similar) instead of "Bug ID".
>>
>
> We had fun trying to pick the label for that field in the initial UI
> design. I think we went with 'Bug ID' in the end because that's what
> Bugzilla calls it. It's kinda hard to predict what name will work out best
> for the majority of people - I could equally see someone being confused by
> 'Proposed bug number', really...


When I think about it I see what you mean.
How about "Bug ID of the proposed bug"? Or is it too long?
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Failure to load images with gpicview, mirage in Rawhide

[moshe nahmias]

I am not an expert but is it possible that something with the files is the
problem?
Can you open the files in f18 for example (or in some other program which
is not editing program in rawhide)?

No idea about the cause of the problem.

Moshe

On Fri, Feb 8, 2013 at 2:55 AM, Steven I Usdansky
wrote:

>
>
> Rawhide, fully updated after being away for two weeks. I get a segfault
> when trying to load a jpg or png file in gpicview; mirage gives me a
> "Cannot load image" message in the status bar. No problems loading
> images in GIMP. Not sure which component is at fault. Ideas?
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Proposing Blocker/Freeze Exception Bugs Through the Blocker Tracking App

[moshe nahmias]

OK, I think its being my mistake...
Is the bug id section is to define which bug is the blocker/freeze
exception?
If so then my comment is wrong on my part.

I thought we don't need the bug id (mixed up the idea of bug id with when
reporting on a new bug).

On Tue, Feb 5, 2013 at 11:23 PM, Tim Flink  wrote:

> On Tue, 5 Feb 2013 19:04:20 +0200
> moshe nahmias  wrote:
>
> > What is the point of the bugzilla ID?
> > I think that the best way to do it is to assign a number that will be
> > eventually the ID for the bug in this field if its needed on the form
> > (though i don't know how easy it will be to do it).
>
> I'm not sure I understand what you're referring to with bugzilla id
> in this or what number would be assigned. Can you elaborate a bit more?
>
> The bug id is the number/id of the bug being proposed as a blocker/fe.
> The bugzilla user/login is used to add the proposer to the cc list of
> the bug being proposed as a blocker/FE.
>
> Tim
>
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Proposing Blocker/Freeze Exception Bugs Through the Blocker Tracking App

[moshe nahmias]

What is the point of the bugzilla ID?
I think that the best way to do it is to assign a number that will be
eventually the ID for the bug in this field if its needed on the form
(though i don't know how easy it will be to do it).
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: boot.iso vs netinst.iso vs efiboot.img

[moshe nahmias]

Hi,
I'm new here and just sent the introduction mail so I hope I don't do
something horribly wrong here...

I see that some of the debate here is that the documentation is not full
enough (uefi stuff), if I am right on this then I think the best way to
handle it will be to include the relevant paragraphs from the man page on
the wiki...

I am willing to do this but since I don't really know what exactly you are
talking about I need some guidance...

I would like to see where can I see the rest of this debate and others if
needed.

If I did something wrong here I apologize

Moshe

On Sat, Jan 26, 2013 at 10:05 PM, Chris Murphy wrote:

>
> On Jan 26, 2013, at 12:06 PM, John Reiser  wrote:
>
> > It's a matter of cost, which varies.  My out-of-pocket expense
> > of burning "4x" DVD+RW (@ $0.24) has been about the same as using USB
> stick (@ $12.)
> > I've had USB sticks wear out (bit errors, and not from too many writes)
> > after some years, just as I have had DVD+RW fail after fewer than 100
> rewrites.
> > Sometimes wall-clock latency matters a lot to me; then top-quality "16x"
> DVD+R
> > (@ $0.25) is best.
>
> Besides USB being on all computers that run Fedora, and computers with
> optical drives shrinking; even 16x DVD is slower than molasses on a
> Minnesota Tuesday in the dead of winter. If time is money, and the choice
> is a matter of cost, then DVD is expensive.
>
>
> > I have no problems producing USB sticks that are UEFI bootable [and they
> do work],
> > because I read the documentation, which includes "man
> livecd-iso-to-disk",
> > where the "--efi" parameter is explained.
>
> I'm not talking about you, or me. The context from the outset was the
> Installation Guide, and regular users.
>
> The Installation Guide does not mention man livecd-iso-to-disk, or any of
> its switches. And it would be *inappropriate*, to say the least, if the
> Installation Guide did refer the user to a man page.
>
> > I do get persistent user data when I use the appropriate incantation.
>
> Incantation is not in the Installation Guide.
>
> > I get a re-format when I ask for it via --format.
>
> That incantation is not in the Installation Guide.
>
>
> >
> >>> The only hassles are when I switch between i386 and x86_64, or between
> >>> UEFI and non-UEFI systems, both of which work better for me with a
> re-format.
> >
> > <>
> >> So I'm still left wondering why dd is last.
> >
> > It's a wiki.  Put your $0.02 there, too.
>
> OK thanks for scraping the bottom of the barrel.
>
> boot.iso vs Fedora-18-x86_64-netinst.iso, presumably you prefer
> Fedora-18-x86_64-netinst.iso?
>
> efiboot.img doesn't actually create bootable media, so presumably you
> prefer Fedora-18-x86_64-netinst.iso for that too?
>
> And "Not available" for both UEFI install and minimal USB media,
> presumably you agree is incorrect, and should have Fedora-18-x86_64-DVD.iso
> and Fedora-18-x86_64-netinst.iso respectively.
>
> Chris Murphy
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Introduction

[moshe nahmias]

Hi,
I started working with fedora about half a year ago and wanted to
contribute but didn't take the required step to start doing it so now I am
doing it at last.
I started working with fedora as my operating system with f17 beta.

My experience with linux started with ubuntu and I used it for about 3.5
years and helping to new users with problems they have on the local IRC and
forums. since ubuntu 11.10 i started to feel the distro is going on the
wrong direction and since I feel I am new to linux I wanted to try some
other distro's so I decided to try fedora according to a recommendation of
a friend. Since I am using fedora I think its only apropriate that I will
contribute as I can (and since fedora is releasing the contributions
upstream I want to help more then if it didn't go upstream).

My main experience is with helping on our forums here in Israel for ubuntu
and recently on a forum for open source and free software. I know a bit of
programing in perl and php and I know html, CSS and a bit of javascript if
it can help.

So, I should introduce myself...

My name is Moshe Nahmias, I am 34 years old and from Israel (as you could
have guessed), I started with linux a bit more then 4 years ago and using
linux ever since. I use windows only when have to (at work, university).

I you want to contact me here are the options I use most of the time:
gtalk: mosheg...@gmail.com
mesenger: mosheg...@gmail.com
mail: mosheg...@gmail.com
IRC: moshe742 at freenode

feel free to contact me for help, I will do what I can

So, thanks for accepting me and I hope to be a good contributor here.

One last thing, if you see a mistake on my language I want you to tell me
about it, even though I am rather good in English I know i have mistakes
some times and want to learn from them since I am not from an English
speaking country.

Thanks

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