|
Re: [meta-security][master|dunfell][PATCH 1/2] clamav: resolve multilib issues
merged to both.
thanks
armin
On 6/12/20 7:19 PM, Jeremy Puhlman wrote:
merged to both.
thanks
armin
On 6/12/20 7:19 PM, Jeremy Puhlman wrote:
|
By
Armin Kuster
·
#49702
·
|
|
Re: Go toolchain in SDK
Unlike other languages go has the ability to produce cross platform binaries. In my case, I just used my go to produce binaries for my yocto based target and just included it. it was too much effort
Unlike other languages go has the ability to produce cross platform binaries. In my case, I just used my go to produce binaries for my yocto based target and just included it. it was too much effort
|
By
Srini
·
#49701
·
|
|
Re: #yocto - meta-anaconda installer gives "An unknown error has occurred"
#yocto
I get this message before I get configparser.NoSectionError: No section: 'Rootfs'
File '/usr/lib/python3.7/site-packages/pyanaconda/threading.py"
I get this message before I get configparser.NoSectionError: No section: 'Rootfs'
File '/usr/lib/python3.7/site-packages/pyanaconda/threading.py"
|
By
srijan.nandi@...
·
#49700
·
|
|
Re: #yocto - meta-anaconda installer gives "An unknown error has occurred"
#yocto
Every time i reboot it, it hangs. But i get to see a piece of error message that I write down. This time before the configparser.NoSectionError: No section: 'Rootfs' error message,
it showed the
Every time i reboot it, it hangs. But i get to see a piece of error message that I write down. This time before the configparser.NoSectionError: No section: 'Rootfs' error message,
it showed the
|
By
srijan.nandi@...
·
#49699
·
|
|
Re: MACHINE and inc files
You do not need to include anything. Maybe I did not understand you. Can you provide a file structure/use case?
Gabriele
NOTE: I won't be able to reply till Tuesday 23rd
You do not need to include anything. Maybe I did not understand you. Can you provide a file structure/use case?
Gabriele
NOTE: I won't be able to reply till Tuesday 23rd
|
By
Gabriele
·
#49698
·
|
|
Re: Distro upgrade strategies
Right. Where I work, the updates would be performed through an A/B partition scheme: if the update is botched, it is always possible to roll back. This doubles the disk space requirement, but is far
Right. Where I work, the updates would be performed through an A/B partition scheme: if the update is botched, it is always possible to roll back. This doubles the disk space requirement, but is far
|
By
Alexander Kanavin
·
#49697
·
|
|
Re: Distro upgrade strategies
I would like to add that this is a design decision. Package updates, be
they based on rpm, deb, or ipk, are not atomic. Which means that if you
power off during an update the system will usually not
I would like to add that this is a design decision. Package updates, be
they based on rpm, deb, or ipk, are not atomic. Which means that if you
power off during an update the system will usually not
|
By
csimmonds
·
#49696
·
|
|
Re: Distro upgrade strategies
Yocto does not support or test upgrading from one yocto release to the next through dnf. Nothing conceptually prevents it, but you need to set up and test such upgrades yourself, and send any needed
Yocto does not support or test upgrading from one yocto release to the next through dnf. Nothing conceptually prevents it, but you need to set up and test such upgrades yourself, and send any needed
|
By
Alexander Kanavin
·
#49695
·
|
|
Re: MACHINE and inc files
And then do include ${MAGIC_NUMBER}. But this is not good idea. Each time new x version appers I will have to extend temp.bb file about the line you wrote but with another x version.
pt., 19.06.2020,
And then do include ${MAGIC_NUMBER}. But this is not good idea. Each time new x version appers I will have to extend temp.bb file about the line you wrote but with another x version.
pt., 19.06.2020,
|
By
Tomek The Messenger <tomekthemessenger@...>
·
#49694
·
|
|
Re: MACHINE and inc files
Hi Tomek,
you can specify machine-specific variables/function with the following syntax:
<PROPERTY_NAME>_[MACHINE_NAME] = "value"
ex:
MAGIC_NUMBER_velismate-x21 = "12345"
inside your
Hi Tomek,
you can specify machine-specific variables/function with the following syntax:
<PROPERTY_NAME>_[MACHINE_NAME] = "value"
ex:
MAGIC_NUMBER_velismate-x21 = "12345"
inside your
|
By
Gabriele
·
#49693
·
|
|
MACHINE and inc files
Hi
I have various ${MACHINE} called:
uruguay-x11
uruguay-x21
supa-rte-x11
supa-rte-x13
supa-rte-x21
velismate-x11
velismate-x21
I created some bb recipe:
temp.bb
where there are common things done for
Hi
I have various ${MACHINE} called:
uruguay-x11
uruguay-x21
supa-rte-x11
supa-rte-x13
supa-rte-x21
velismate-x11
velismate-x21
I created some bb recipe:
temp.bb
where there are common things done for
|
By
tomekthemessenger@...
·
#49692
·
|
|
Re: [meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254
<zhixiong.chi@...> wrote:
Sounds good.
And yes, in master I prefer to upgrade the version and I typically do
those upgrades every 2 months.
For the CVE patches, it is just helpful if we
<zhixiong.chi@...> wrote:
Sounds good.
And yes, in master I prefer to upgrade the version and I typically do
those upgrades every 2 months.
For the CVE patches, it is just helpful if we
|
By
Bruce Ashfield
·
#49691
·
|
|
Distro upgrade strategies
Hello all,
I'm struggling conceptually with a recommended upgrade strategy for our distribution (i.e. the resultant distribution on an ARM-based embedded device, not the development SDK itself). I
Hello all,
I'm struggling conceptually with a recommended upgrade strategy for our distribution (i.e. the resultant distribution on an ARM-based embedded device, not the development SDK itself). I
|
By
Hugh Boddington
·
#49690
·
|
|
Re: #yocto - meta-anaconda installer gives "An unknown error has occurred"
#yocto
Hello All,
I was finally able to view the error message. It says configparser.NoSectionError: No section: 'Rootfs'. This comes as soon as the anaconda installer starts and then it hangs on this
Hello All,
I was finally able to view the error message. It says configparser.NoSectionError: No section: 'Rootfs'. This comes as soon as the anaconda installer starts and then it hangs on this
|
By
srijan.nandi@...
·
#49689
·
|
|
Re: [swupdate] RE: [yocto] [PATCH] [meta-swupdate] Fix build error of dependence.
Hi Zheng,
Yes
Just send the patch to SWUpdate's ML, I will integrate then.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering
Hi Zheng,
Yes
Just send the patch to SWUpdate's ML, I will integrate then.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering
|
By
Stefano Babic
·
#49688
·
|
|
Re: #yocto - meta-anaconda installer gives "An unknown error has occurred"
#yocto
I am using zeus as the yocto version.
I tried both the boot modes Legacy as well as UEFI. But failed. I thing it is a python issue but as the screen is stuck I cannot see the error nor click on debug.
I am using zeus as the yocto version.
I tried both the boot modes Legacy as well as UEFI. But failed. I thing it is a python issue but as the screen is stuck I cannot see the error nor click on debug.
|
By
srijan.nandi@...
·
#49687
·
|
|
Re: [swupdate] RE: [yocto] [PATCH] [meta-swupdate] Fix build error of dependence.
Hi,
So, the conclusion is adding a default SSL implementation option(CONFIG_SSL_IMPL_OPENSSL) into defconfig, is it?
Is there anybody plans to do it? Or let me submit a patch?
Best regards
Zheng
Hi,
So, the conclusion is adding a default SSL implementation option(CONFIG_SSL_IMPL_OPENSSL) into defconfig, is it?
Is there anybody plans to do it? Or let me submit a patch?
Best regards
Zheng
|
By
zhengruoqin
·
#49686
·
|
|
Re: [meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254
On 2020/6/19 上午11:19, Zhixiong Chi wrote:
s/fundell/dunfell/g
-- ---------------------Thanks,Zhixiong ChiTel: +86-10-8477-7036
On 2020/6/19 上午11:19, Zhixiong Chi wrote:
s/fundell/dunfell/g
-- ---------------------Thanks,Zhixiong ChiTel: +86-10-8477-7036
|
By
Zhixiong Chi
·
#49685
·
|
|
Re: [meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254
On 2020/6/19 上午10:29, Zhixiong Chi wrote:
I have checked the master/dunfell branch, the CVE-2020-8555 and CVE-2019-11254 isse don't affect master branch, but the two affect
On 2020/6/19 上午10:29, Zhixiong Chi wrote:
I have checked the master/dunfell branch, the CVE-2020-8555 and CVE-2019-11254 isse don't affect master branch, but the two affect
|
By
Zhixiong Chi
·
#49684
·
|
|
Re: [meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254
On 2020/6/18 下午8:49, Bruce Ashfield wrote:
Hi Bruce,
Sorry for that, it's possible that there is something wrong with our mail server. I just saw your response a few
On 2020/6/18 下午8:49, Bruce Ashfield wrote:
Hi Bruce,
Sorry for that, it's possible that there is something wrong with our mail server. I just saw your response a few
|
By
Zhixiong Chi
·
#49683
·
|