Re: [Fedora QA] #393: Revise release criteria for ARM as primary arch

[Fedora QA]

#393: Revise release criteria for ARM as primary arch
---+---
  Reporter:  adamwill  |  Owner:  adamwill
  Type:  task  | Status:  new
  Priority:  major |  Milestone:  Fedora 20
 Component:  Release criteria  |Version:
Resolution:|   Keywords:
Blocked By:|   Blocking:
---+---
Changes (by ausil):

 * cc: ausil (added)


Comment:

 to date we have produced a network install tree and pre-canned images for
 use where anaconda is not feasible.

 we can look at making a bootable raw install disk

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora QA] #394: Revise validation process / templates for ARM as primary arch

[Fedora QA]

#394: Revise validation process / templates for ARM as primary arch
---+---
  Reporter:  adamwill  |  Owner:
  Type:  task  | Status:  new
  Priority:  major |  Milestone:  Fedora 20
 Component:  Wiki  |Version:
Resolution:|   Keywords:
Blocked By:|   Blocking:
---+---
Changes (by ausil):

 * cc: ausil (added)


Comment:

 we are only making the basearch of armhp primary.

-- 
Ticket URL: 
Fedora QA 
Fedora Quality Assurance
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Criteria revision proposal: Expected installed system boot behavior (Alpha)

[Kamil Paral]

> "A working mechanism to create a user account must be clearly presented
> during installation and/or first boot of the installed system.
> 
> A system installed with a release-blocking desktop must boot to a log in
> screen where it is possible to log in to a working desktop using a user
> account created during installation or a 'first boot' utility."
> 
> The third criterion, "A system installed without a graphical package set
> must boot to a state where it is possible to log in through at least one
> of the default virtual consoles.", remains unchanged.
> 
> We add one more 'footnote':
> 
> "On the first boot after installation, a utility for creating user
> accounts and other configuration may run prior to a log in screen
> appearing."

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

Confused Rawhide (F20) set correct time Xfce

[Frank Murphy]

Can't connect securely to Dropbox, as it says time and date wrong.
Have checked both the bios, and datetime applet, both have correct
time and date.

~$ locale
LANG=en_IE.UTF-8

sudo hwclock --debug
hwclock from util-linux 2.23.1
Using /dev interface to clock.
Last drift adjustment done at 1334072322 seconds after 1969
Last calibration done at 1334072322 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2013/07/19 11:00:10
Hw clock time : 2013/07/19 11:00:10 = 1374231610 seconds since 1969
Fri 19 Jul 2013 12:00:10 IST  -0.814446 seconds



-- 
Regards,
Frank  "When in doubt PANIC!"
 I check for new mail app. 20min
www.frankly3d.com
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test