I am working with yocto on zeus branch. I wanted to add an antivirus so I checked on ClamAV.
I added meta-security and the clamAV recipe to my system with the meta-security revision b66e5e27b48c0a07494f9df9b809ed933cede047 (http://layers.openembedded.org/layerindex/recipe/110195/)
When I run the build, the following error appears, so it seems that the clamav mirror does not have the path to the necessary file:
ClamAV update process started at Thu Feb 9 13:40:08 2023
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.99.4 Recommended version: 0.103.7
DON'T PANIC! Read http://www.clamav.net/documents/upgrading-clamav
ERROR: getfile: Unknown response from database.clamav.net (IP: 104.16.218.84)
ERROR: Can't download main.cvd from database.clamav.net
Giving up on database.clamav.net...
Is there a way to obtain the file I am missing or to specify another mirror?
Thanks!!
That revision does not exist for some reason.
Create bbappend and try to use b66e5e27b48c0a07494f9df9b809ed933cede047 which is the HEAD of the same branch.
Related
I am trying to install Magento 2.3.5 using composer.
muk#muk:/var/www/html$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.3.5 magento23
Creating a "magento/project-community-edition" project at "./magento23"
Installing magento/project-community-edition (2.3.5-p1)
- Installing magento/project-community-edition (2.3.5-p1): Loading from cache
Created project in /var/www/html/magento23
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 463 installs, 0 updates, 0 removals
- Installing magento/magento-composer-installer (0.1.13): Loading from cache
- Installing laminas/laminas-dependency-plugin (1.0.3): Loading from cache
Plugin installation failed (include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory), rolling back
- Removing laminas/laminas-dependency-plugin (1.0.3)
[ErrorException]
include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory
create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [<package>] [<directory>] [<version>]
I am getting following error.
Plugin installation failed (include(/var/www/html/magento23/vendor/laminas/laminas-dependency-plugin/src/DependencyRewriterPlugin.php): failed to open stream: No such file or directory), rolling back
- Removing laminas/laminas-dependency-plugin (1.0.3)
My Composer version
muk#muk:/var/www/html$ composer --version
Composer version 1.10.5 2020-04-10 11:44:22
I am using VirtualBox with Shared folder.
How can I fix it?
Note: To fix it I stopped using shared folder. Now I keep the entire code in the VM and do not use shared folder. For file synching I am using mutagen.
if anyone runs into this issue, it looks to be a problem with virtualBox and shared folders. when unzipping files, they are not immediately available in the environment.
the solution is by rkamp and is also available here:
https://stackoverflow.com/a/66413857/1470145
in short, one needs to override unzip to add a brief delay after unzipping.
I thought I had the same issue, but turned out it was something else.
The upgrade went OK for me, for a sandbox/clean 2.3.4 install, and a client project running 2.3.4.
A few things:
This could possibly be an issue with your cache, try to clear your composer laminas cache (~/.composer/cache/files/laminas usually)
Although it would complain about that, you've possibly got unmet platform requirements (php version, etc.)
Try clearing your entire composer cache (~/.composer)
Double-check the repository URL (should it be 2.3.5 or 2.3.5-p1?)
Hope that helps
I am trying to install System.ComponentModel.Annotations through VS 2017 package manager console.
Command:
Install-Package System.ComponentModel.Annotations -Version 4.3.0
Outcome
Restoring packages for
C:\MyTest.csproj...
Installing NuGet package System.ComponentModel.Annotations 4.3.0.
Committing restore... Writing lock file to disk. Path:
C:\MyTest\obj\project.assets.json
Restore completed in 816.43 ms for
C:\MyTest.csproj.
Restoring packages for
C:\MyTest.csproj...
Committing restore... Lock file has not changed. Skipping lock file
write. Path:
C:\MyTest\obj\project.assets.json
Restore completed in 2.03 sec for
C:\MyTest.csproj.
Executing nuget actions took 4.12 sec Time Elapsed: 00:00:05.2258592
Note:
I am using .NETCoreApp1.1 framework.
Unable to install package. Lock file has not changed, Skipping lock file write
I also got the same outcome in the output windows when I restore/update that package, but I found that package was already installed to the project after checking the project Dependencies and project file(.csproj). And the outcome did not tell the installation failed, just prompting skip lock file write:
Restoring packages for C:\MyTest.csproj... Committing restore... Lock file has not changed. Skipping lock file write.
So this message comes only if that package was already installed to the project. When you got that log, you should double check the project reference, make sure if the package already installed.
One should also check if there is a Directory.Build.targets file in some parent directory of the project that defines the version of the package. If this is the case (I had this problem), VS will ignore the version you install and will keep the version defined in the file, so you have to update the version there.
I am trying to install spritebuilder but since it is no longer on the app store I have to do it through github. I ran the following code from the readme file on github.
git clone https://github.com/apportable/SpriteBuilder
cd SpriteBuilder
git submodule update --init --recursive
cd scripts
./build_distribution.py --version 1.x
but it keeps returning the error:
Testing failed:
Error: There is no SDK with the name or path '/Users/username/SpriteBuilder/scripts/SpriteBuilder/SpriteBuilder/macosx10.9'
** TEST FAILED **
The following build commands failed:
Check dependencies
(1 failure)
Am I doing something wrong? I went into the build folder despite the error and the .app is not able to be opened, saying it may be incomplete or corrupt.
I found a workaround by downloading Spritebuilder from a mirror hosting site.
I tried to run mongdodb's driver test using phpunit as stated at http://www.php.net/manual/en/mongo.testing.php but it seems to have a problem with a MongoInt32Test.php filew.
# phpunit tests/mongosuite.php
Warning: require_once(MongoInt32Test.php): failed to open stream: No such file or directory in C:\Documents and Settings\owner\Desktop\mongo-php-driver\tests\MongoSuite.php on line 4
Fatal error: require_once(): Failed opening required 'MongoInt32Test.php' (include_path='.;\programming_tools\xampp-portable\php\PEAR') in C:\Documents and Settings\owner\Desktop\mongo-php-driver\tests\MongoSuite.php on line 4
I am using a php_mongo-1.3.1-5.4-vc9.dll and running mongodb 2.0.8 in windows xp. Anybody knows how to fix this? I can't find MongoInt32Test.php anywhere.
The PHPUnit tests in the extension are legacy tests and are no longer supported. I created a ticket, PHP-695, to remind us to remove mention of them from the documentation. All extension tests are phpt files, and instructions for executing them are documented in the GitHub repository.
I have a Yocto bitbake image recipe that can be built successfully.
However, the same image recipe fails when generating SDK with -c populate_sdk command.
The error seems to be caused by mixing 32-bit and 64-bit versions of libraries, which is fine when building images with only binaries, but the header files collide with each other when populating the SDK root fs:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
file /usr/bin/curl-config from install of lib32-curl-dev-7.53.1-r0.cortexa7hf_neon_vfpv4 conflicts with file from package curl-dev-7.53.1-r0.aarch64
file /usr/include/nettle/version.h from install of lib32-nettle-dev-3.3-r0.cortexa7hf_neon_vfpv4 conflicts with file from package nettle-dev-3.3-r0.aarch64
file /usr/include/nettle/nettle-stdint.h from install of lib32-nettle-dev-3.3-r0.cortexa7hf_neon_vfpv4 conflicts with file from package nettle-dev-3.3-r0.aarch64
What is the best way to exclude 32-bit versions of libraries(recipes) when doing -c populate_sdk without excluding them entirely from the production image?
You can remove target packages from the toolchain by removing them from the TOOLCHAIN_TARGET_TASK variable and host packages by removing them from the TOOLCHAIN_HOST_TASK.
For example to remove the target package "curl-dev" from your sdk you have to add the following in your image recipe:
TOOLCHAIN_TARGET_TASK_remove = "curl-dev"
To remove the same host package from your sdk you have to add the following in your image recipe:
TOOLCHAIN_HOST_TASK_remove = "curl-dev"