-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
http://armpkgs.fedoraproject.org/mash/stage/19-TC6/
is a TC6 Final compose, We still have a bit to get done in a really short period of time. lets get testing and bug reports in.
We have, Minimal, XFCE, LXDE, Soas, KDE and Mate Images.
things left needed for GA, a script/utility to setup a sdcard for the different omap boards. maybe someone could look at the work Hans has done for allwinner card setup.
Fedora 19 final is fast approaching. https://qa.fedoraproject.org/blockerbugs/milestone/19/final/buglist is the current blockers for primary. we are expecting a RC request very soon.
QA schedule is http://fedorapeople.org/groups/schedule/f-19/f-19-quality-tasks.html Releng schedule http://fedorapeople.org/groups/schedule/f-19/f-19-releng-tasks.html
go/nogo meeting is a week away. its getting really critical that we get extensive testing on as many boards and systems as possible. as well as some more extensive testing of anaconda.
https://fedorahosted.org/rel-eng/ticket/5623#comment:16 is the list of requested changes in TC6
we need testing, feedback and comments.
Dennis
Hi,
On 06/21/2013 05:35 AM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
http://armpkgs.fedoraproject.org/mash/stage/19-TC6/
is a TC6 Final compose, We still have a bit to get done in a really short period of time. lets get testing and bug reports in.
I've ran my "Fedora armhfp to Fedora Allwinner A10" script on the XFCE image, and done some testing with that. Here are my findings:
-Overall it looks very good! -Can we make the image 4G instead of 8 again please, writing 8G take ages (4G only takes halve an age) ? -Can we use uboot and rootfs as fslabels again please, __ and __boot are *ugly* ? -There is no poweroff/shutdown option in the poweroff menu of lightdm, instead I get suspend and hibernate as only options. This may be related to the Allwinner specific kernel I'm using, or it could be a generic problem with lightdm using an x86 specific method to determine which buttons to show... -The first time I log into XFCE, choose default panel, and then logout again, I end up with no panel. Removing all the config for the user and doing it again fixes this. Am I the only one seeing this?
I've not yet filed bugs for any of these, if you believe I should file bugs, please let me know.
Regards,
Hans
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 21 Jun 2013 14:28:00 +0200 Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 06/21/2013 05:35 AM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
http://armpkgs.fedoraproject.org/mash/stage/19-TC6/
is a TC6 Final compose, We still have a bit to get done in a really short period of time. lets get testing and bug reports in.
I've ran my "Fedora armhfp to Fedora Allwinner A10" script on the XFCE image, and done some testing with that. Here are my findings:
-Overall it looks very good! -Can we make the image 4G instead of 8 again please, writing 8G take ages (4G only takes halve an age) ? -Can we use uboot and rootfs as fslabels again please, __ and __boot are *ugly* ? -There is no poweroff/shutdown option in the poweroff menu of lightdm, instead I get suspend and hibernate as only options. This may be related to the Allwinner specific kernel I'm using, or it could be a generic problem with lightdm using an x86 specific method to determine which buttons to show... -The first time I log into XFCE, choose default panel, and then logout again, I end up with no panel. Removing all the config for the user and doing it again fixes this. Am I the only one seeing this?
I've not yet filed bugs for any of these, if you believe I should file bugs, please let me know.
Regards,
Hans
Its now too late, you should have filed bugs. because you cc'd me on the email it got filtered elsewhere in a folder full of spam and i only saw it because I cleaned out the spam and noticed. please do not cc me on list emails. we are making 8gb images for F19, disk label will not be changing, as hiopped the images use UUID's appliance-creator sets the labels based on mount point, im not going to write support to set labels. as to poweroff/shutdown, it needs debugging, but RC1 final images are compressing now. ive not seen the XFCE issue, but without a bug its impossible to track or get on the radar for fixing.
Dennis
Hi,
On 06/25/2013 03:53 PM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 21 Jun 2013 14:28:00 +0200 Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 06/21/2013 05:35 AM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
http://armpkgs.fedoraproject.org/mash/stage/19-TC6/
is a TC6 Final compose, We still have a bit to get done in a really short period of time. lets get testing and bug reports in.
I've ran my "Fedora armhfp to Fedora Allwinner A10" script on the XFCE image, and done some testing with that. Here are my findings:
-Overall it looks very good! -Can we make the image 4G instead of 8 again please, writing 8G take ages (4G only takes halve an age) ? -Can we use uboot and rootfs as fslabels again please, __ and __boot are *ugly* ? -There is no poweroff/shutdown option in the poweroff menu of lightdm, instead I get suspend and hibernate as only options. This may be related to the Allwinner specific kernel I'm using, or it could be a generic problem with lightdm using an x86 specific method to determine which buttons to show... -The first time I log into XFCE, choose default panel, and then logout again, I end up with no panel. Removing all the config for the user and doing it again fixes this. Am I the only one seeing this?
I've not yet filed bugs for any of these, if you believe I should file bugs, please let me know.
Regards,
Hans
Its now too late, you should have filed bugs.
I understand, but the reason for me not filing them still exists, mainly where and against which component do I fie arm image bugs?
because you cc'd me on
the email it got filtered elsewhere in a folder full of spam and i only saw it because I cleaned out the spam and noticed. please do not cc me on list emails. we are making 8gb images for F19
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
disk label will not be changing, as hiopped the images use UUID's appliance-creator sets the labels based on mount point, im not going to write support to set labels.
Again I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
as to poweroff/shutdown, it needs debugging, but RC1 final images are compressing now.
Ok.
ive not seen the XFCE issue, but without a bug its impossible to track or get on the radar for fixing.
Well it is hard to reproduce for me too, which is why I wanted to gather more data first.
Regards,
Hans
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 14:42:17 +0200 Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 06/25/2013 03:53 PM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 21 Jun 2013 14:28:00 +0200 Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 06/21/2013 05:35 AM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
http://armpkgs.fedoraproject.org/mash/stage/19-TC6/
is a TC6 Final compose, We still have a bit to get done in a really short period of time. lets get testing and bug reports in.
I've ran my "Fedora armhfp to Fedora Allwinner A10" script on the XFCE image, and done some testing with that. Here are my findings:
-Overall it looks very good! -Can we make the image 4G instead of 8 again please, writing 8G take ages (4G only takes halve an age) ? -Can we use uboot and rootfs as fslabels again please, __ and __boot are *ugly* ? -There is no poweroff/shutdown option in the poweroff menu of lightdm, instead I get suspend and hibernate as only options. This may be related to the Allwinner specific kernel I'm using, or it could be a generic problem with lightdm using an x86 specific method to determine which buttons to show... -The first time I log into XFCE, choose default panel, and then logout again, I end up with no panel. Removing all the config for the user and doing it again fixes this. Am I the only one seeing this?
I've not yet filed bugs for any of these, if you believe I should file bugs, please let me know.
Regards,
Hans
Its now too late, you should have filed bugs.
I understand, but the reason for me not filing them still exists, mainly where and against which component do I fie arm image bugs?
appliance-creator
because you cc'd me on
the email it got filtered elsewhere in a folder full of spam and i only saw it because I cleaned out the spam and noticed. please do not cc me on list emails. we are making 8gb images for F19
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
it was a design decision I made. I guess that to change it discussion would need to happen on this list or the spins list since that's where discussions on spin-kickstarts happens which is where all the kickstart snippets live.
disk label will not be changing, as hiopped the images use UUID's appliance-creator sets the labels based on mount point, im not going to write support to set labels.
Again I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
appliance-creator do note ive taken over upstream for it.
as to poweroff/shutdown, it needs debugging, but RC1 final images are compressing now.
Ok.
ive not seen the XFCE issue, but without a bug its impossible to track or get on the radar for fixing.
Well it is hard to reproduce for me too, which is why I wanted to gather more data first.
okay
Dennis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 08:05:21 -0500 Dennis Gilmore dennis@ausil.us wrote:
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
it was a design decision I made. I guess that to change it discussion would need to happen on this list or the spins list since that's where discussions on spin-kickstarts happens which is where all the kickstart snippets live.
i choose 8gb because its common and because we dont have anything working to resize the rootfs. smaller images make the processes faster, bigger makes for a more usable out of box experience
Dennis
Hi,
On 06/26/2013 03:16 PM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 08:05:21 -0500 Dennis Gilmore dennis@ausil.us wrote:
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
it was a design decision I made. I guess that to change it discussion would need to happen on this list or the spins list since that's where discussions on spin-kickstarts happens which is where all the kickstart snippets live.
i choose 8gb because its common and because we dont have anything working to resize the rootfs. smaller images make the processes faster, bigger makes for a more usable out of box experience
Ah, what happened to the rootfs-resize script ctyler wrote, is that no longer working?
I agree that before moving back to 4gb images we should first have a working rootfs-resize.
Regards,
Hans
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 15:21:33 +0200 Hans de Goede hdegoede@redhat.com wrote:
Hi,
On 06/26/2013 03:16 PM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 08:05:21 -0500 Dennis Gilmore dennis@ausil.us wrote:
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
it was a design decision I made. I guess that to change it discussion would need to happen on this list or the spins list since that's where discussions on spin-kickstarts happens which is where all the kickstart snippets live.
i choose 8gb because its common and because we dont have anything working to resize the rootfs. smaller images make the processes faster, bigger makes for a more usable out of box experience
Ah, what happened to the rootfs-resize script ctyler wrote, is that no longer working?
yes it corrupts the filesystem, id like to look at some of the work in cloud land. there does look to be a ggod solution but its very new and i didnt want to throw it into F19 at the last minute
http://koji.fedoraproject.org/koji/packageinfo?packageID=16047
that dracut module uses cloud-utils-growpart from http://koji.fedoraproject.org/koji/packageinfo?packageID=15529 to resize the filesystem. so it would get resized in the initramfs in one shot.
I agree that before moving back to 4gb images we should first have a working rootfs-resize.
Regards,
Hans _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 06/26/2013 08:21 AM, Hans de Goede wrote:
Hi,
On 06/26/2013 03:16 PM, Dennis Gilmore wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 08:05:21 -0500 Dennis Gilmore dennis@ausil.us wrote:
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
it was a design decision I made. I guess that to change it discussion would need to happen on this list or the spins list since that's where discussions on spin-kickstarts happens which is where all the kickstart snippets live.
i choose 8gb because its common and because we dont have anything working to resize the rootfs. smaller images make the processes faster, bigger makes for a more usable out of box experience
Ah, what happened to the rootfs-resize script ctyler wrote, is that no longer working?
There is an open BZ on it:
https://bugzilla.redhat.com/show_bug.cgi?id=974631
d.marlin ========
I agree that before moving back to 4gb images we should first have a working rootfs-resize.
Regards,
Hans _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Wed, Jun 26, 2013 at 2:16 PM, Dennis Gilmore dennis@ausil.us wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 26 Jun 2013 08:05:21 -0500 Dennis Gilmore dennis@ausil.us wrote:
Why are we making 8GB images, is 4GB too small? or ... ?
I would really like to see this fixed for F-20, where and against which component do I file a bug for this?
it was a design decision I made. I guess that to change it discussion would need to happen on this list or the spins list since that's where discussions on spin-kickstarts happens which is where all the kickstart snippets live.
i choose 8gb because its common and because we dont have anything working to resize the rootfs. smaller images make the processes faster, bigger makes for a more usable out of box experience
It's easier to put a SD card larger than 4gb in a standard workstation and use something like gparted to increase the size manually than it is to decrease it. There's a lot of users that have 4gb cards because a class 10 4gb card is really cheap. I would prefer to see us use the smaller size rather than the larger size as in all cases it's easier to increase the size rather than decrease.
Peter
-
d.marlin -
Dennis Gilmore -
Hans de Goede -
Peter Robinson