[opensuse-arm] Chromebook image update
Hi, could you accept SR#220462 which fix Chromebook boot process and image creation, please. Then, we could work on fixing the kernel more easily. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 31.01.2014, at 12:16, Guillaume Gardet
Hi,
could you accept SR#220462 which fix Chromebook boot process and image creation, please.
Then, we could work on fixing the kernel more easily.
Please make
@@ -30,7 +30,10 @@
<!-- we need to keep our time in sync, because there is no RTC -->
<package name="ntp"/>
<package name="openssh"/>
+#if !IS_FLAVOR_chromebook
+<!-- kernel-chromebook is in conflict with openSUSE-release -->
<package name="openSUSE-release"/>
+#endif
<package name="openSUSE-release-ftp"/>
#if IS_FLAVOR_raspberrypi
<package name="pihwm"/>
a bit more friendly to the other targets. Something like
#if chromebook
<!-- foo -->
#else
On Freitag, 31. Januar 2014, 12:24:38 wrote Alexander Graf:
On 31.01.2014, at 12:16, Guillaume Gardet
wrote: Hi,
could you accept SR#220462 which fix Chromebook boot process and image creation, please.
Then, we could work on fixing the kernel more easily.
Please make
@@ -30,7 +30,10 @@ <!-- we need to keep our time in sync, because there is no RTC --> <package name="ntp"/> <package name="openssh"/> +#if !IS_FLAVOR_chromebook +<!-- kernel-chromebook is in conflict with openSUSE-release -->
Argh, you are aware that openSUSE-release is a generated package and we rely that the content is in sync with the product settings?
<package name="openSUSE-release"/> +#endif <package name="openSUSE-release-ftp"/> #if IS_FLAVOR_raspberrypi <package name="pihwm"/>
a bit more friendly to the other targets. Something like
#if chromebook <!-- foo --> #else
#endif btw, any particular reason we're not using zImage?
Alex
-- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 31/01/2014 12:57, Adrian Schröter a écrit :
On Freitag, 31. Januar 2014, 12:24:38 wrote Alexander Graf:
On 31.01.2014, at 12:16, Guillaume Gardet
wrote: Hi,
could you accept SR#220462 which fix Chromebook boot process and image creation, please.
Then, we could work on fixing the kernel more easily. Please make
@@ -30,7 +30,10 @@ <!-- we need to keep our time in sync, because there is no RTC --> <package name="ntp"/> <package name="openssh"/> +#if !IS_FLAVOR_chromebook +<!-- kernel-chromebook is in conflict with openSUSE-release --> Argh, you are aware that openSUSE-release is a generated package and we rely that the content is in sync with the product settings?
For an unknown reason, kernel-chromebook is in conflict with openSUSE-release in 13.1 (not in Factory). Not sure why. It is a temp workaround to get images built. What would be the problem on a running system if openSUSE-release is missing? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 31/01/2014 13:12, Guillaume Gardet a écrit :
Le 31/01/2014 12:57, Adrian Schröter a écrit :
On Freitag, 31. Januar 2014, 12:24:38 wrote Alexander Graf:
On 31.01.2014, at 12:16, Guillaume Gardet
wrote: Hi,
could you accept SR#220462 which fix Chromebook boot process and image creation, please.
Then, we could work on fixing the kernel more easily. Please make
@@ -30,7 +30,10 @@ <!-- we need to keep our time in sync, because there is no RTC --> <package name="ntp"/> <package name="openssh"/> +#if !IS_FLAVOR_chromebook +<!-- kernel-chromebook is in conflict with openSUSE-release --> Argh, you are aware that openSUSE-release is a generated package and we rely that the content is in sync with the product settings? For an unknown reason, kernel-chromebook is in conflict with openSUSE-release in 13.1 (not in Factory). Not sure why.
It is a temp workaround to get images built. What would be the problem on a running system if openSUSE-release is missing?
I removed the opeSUSE-release hack for now, so that the SR get accepted according to Adrian comment. Please accept SR #220471. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 31/01/2014 12:24, Alexander Graf a écrit :
On 31.01.2014, at 12:16, Guillaume Gardet
wrote: Hi,
could you accept SR#220462 which fix Chromebook boot process and image creation, please.
Then, we could work on fixing the kernel more easily. Please make
@@ -30,7 +30,10 @@ <!-- we need to keep our time in sync, because there is no RTC --> <package name="ntp"/> <package name="openssh"/> +#if !IS_FLAVOR_chromebook +<!-- kernel-chromebook is in conflict with openSUSE-release --> <package name="openSUSE-release"/> +#endif <package name="openSUSE-release-ftp"/> #if IS_FLAVOR_raspberrypi <package name="pihwm"/>
a bit more friendly to the other targets. Something like
#if chromebook <!-- foo --> #else
#endif
Done. Please accept SR #220465.
btw, any particular reason we're not using zImage?
u-boot-chromebook does not support zImage ATM. Once kernel boot will be fixed, we could work on upgrading u-boot and/or using zImage. But really need working 13.1 images. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Adrian Schröter
-
Alexander Graf
-
Guillaume Gardet