There is an RPM for fuse compress:
https://rpmfind.net/linux/rpm2html/search.php?query=fusecompress(x86-64)
So, if I do
If I do
rpm -ivh fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64.rpm
I am getting
warning: fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 78d019f5: NOKEY
error: Failed dependencies:
fuse is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
libboost_filesystem.so.1.42.0()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
libboost_iostreams.so.1.42.0()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
libboost_program_options.so.1.42.0()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
libboost_serialization.so.1.42.0()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
libboost_system.so.1.42.0()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
libfuse.so.2()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
liblzma.so.2()(64bit) is needed by fusecompress-0.6-1.0.git.20100107.5mdv2010.1.x86_64
However, the installation of libboost results in very many unfilled dependencies.
There is the stack:
[root#tmp]# rpm -ivh libboost5-1.39.0-2mdv2010.0.i586.rpm
warning: libboost5-1.39.0-2mdv2010.0.i586.rpm: Header V3 DSA/SHA1
Signature, key ID 70771ff3: NOKEY
error: Failed dependencies:
libbz2.so.1 is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6 is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.0) is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.1) is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.1.3) is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.2) is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.3.2) is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.3.4) is needed by libboost5-1.39.0-2mdv2010.0.i586
libc.so.6(GLIBC_2.4) is needed by libboost5-1.39.0-2mdv2010.0.i586
libdl.so.2 is needed by libboost5-1.39.0-2mdv2010.0.i586
libexpat.so.1 is needed by libboost5-1.39.0-2mdv2010.0.i586
libgcc_s.so.1 is needed by libboost5-1.39.0-2mdv2010.0.i586
libgcc_s.so.1(GCC_3.0) is needed by libboost5-1.39.0-2mdv2010.0.i586
libgcc_s.so.1(GCC_4.0.0) is needed by libboost5-1.39.0-2mdv2010.0.i586
libgcc_s.so.1(GLIBC_2.0) is needed by libboost5-1.39.0-2mdv2010.0.i586
libicudata.so.42 is needed by libboost5-1.39.0-2mdv2010.0.i586
libicui18n.so.42 is needed by libboost5-1.39.0-2mdv2010.0.i586
libicuuc.so.42 is needed by libboost5-1.39.0-2mdv2010.0.i586
libm.so.6 is needed by libboost5-1.39.0-2mdv2010.0.i586
libm.so.6(GLIBC_2.0) is needed by libboost5-1.39.0-2mdv2010.0.i586
libm.so.6(GLIBC_2.1) is needed by libboost5-1.39.0-2mdv2010.0.i586
libm.so.6(GLIBC_2.2) is needed by libboost5-1.39.0-2mdv2010.0.i586
libpthread.so.0 is needed by libboost5-1.39.0-2mdv2010.0.i586
libpthread.so.0(GLIBC_2.0) is needed by libboost5-1.39.0-2mdv2010.0.i586
libpthread.so.0(GLIBC_2.1) is needed by libboost5-1.39.0-2mdv2010.0.i586
libpthread.so.0(GLIBC_2.2) is needed by libboost5-1.39.0-2mdv2010.0.i586
libpthread.so.0(GLIBC_2.3.2) is needed by libboost5-1.39.0-2mdv2010.0.i586
libpython2.6.so.1.0 is needed by libboost5-1.39.0-2mdv2010.0.i586
librt.so.1 is needed by libboost5-1.39.0-2mdv2010.0.i586
libstdc++.so.6 is needed by libboost5-1.39.0-2mdv2010.0.i586
libstdc++.so.6(GLIBCXX_3.4) is needed by libboost5-1.39.0-2mdv2010.0.i586
libstdc++.so.6(GLIBCXX_3.4.11) is needed by libboost5-1.39.0-2mdv2010.0.i586
libstdc++.so.6(GLIBCXX_3.4.5) is needed by libboost5-1.39.0-2mdv2010.0.i586
libstdc++.so.6(GLIBCXX_3.4.9) is needed by libboost5-1.39.0-2mdv2010.0.i586
libutil.so.1 is needed by libboost5-1.39.0-2mdv2010.0.i586
libz.so.1 is needed by libboost5-1.39.0-2mdv2010.0.i586
Is there any known sequence for installation?
This is what my colleague found:
cd '/etc/yum.repos.d/'
curl 'https://copr.fedorainfracloud.org/coprs/scx/fusecompress/repo/epel-7/scx-fusecompress-epel-7.repo' > 'scx-fusecompress-epel-7.repo'
yum install -y 'fusecompress'
Related
The qt program deployed by ubuntu20.04 does not work.
./test: error while loading shared libraries: libQt5Network.so.5: cannot open shared object file: No such file or directory
(LD_LIBRARY_PATH works fine. However, LD_LIBRARY_PATH should not be used.)
The qt program deployed by ubuntu18.04 works well without any problems.
(Use rpath and qt.conf without LD_LIBRARY_PATH)
I don't know why the Qt program deployed by ubuntu20.04 can't find some Qtlibs.
libQt5Gui.so.5 => /home/admin/EXE_2004/./qt/lib/libQt5Gui.so.5 (0x00007f260b2cc000)
libQt5Xml.so.5 => /home/admin/EXE_2004/./qt/lib/libQt5Xml.so.5 (0x00007f260b28a000)
libQt5Sql.so.5 => /home/admin/EXE_2004/./qt/lib/libQt5Sql.so.5 (0x00007f260b23a000)
libQt5Core.so.5 => /home/admin/EXE_2004/./qt/lib/libQt5Core.so.5 (0x00007f260acf1000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f260aaff000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f260aae4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f260a8f2000)
libQt5Network.so.5 => not found
libpulse.so.0 => /lib/x86_64-linux-gnu/libpulse.so.0 (0x00007f260a89b000)
Is there a good solution?
Thank you.
I have "#reduxjs/toolkit": "1.4.0", and "redux": "4.0.5"
Getting an error with the type of preloadedState in configureStore.ts.
It's really likely that you've got multiple conflicting redux dependencies. You can probably resolve this by:
Remove the redux dependency as it's unnecessary - #reduxjs/toolkit will include it for you
Purge your node_modules
Remove your lock file
Reinstall
C:\git\test (master) × berks --version
7.0.8
I have an issue with Berkshelf resolving chained git dependencies.
I have a test cookbook I generated to narrow down the issue, this cookbook depends on the cookbook windows-automation via a git reference.
test Berksfile
# frozen_string_literal: true
source 'https://supermarket.chef.io'
cookbook 'win-telegraf', path: '../win-telegraf/'
cookbook 'windows-automation', '~> 0.4.0', git: 'git#git.osky.io:ops/chef-windows-automation.git', branch: 'master'
# cookbook 'windows-library', '~> 0.1.0', git: 'git#git.osky.io:ops/chef-windows-library.git', branch: 'master'
metadata
test metadata.rb
depends 'win-telegraf'
depends 'windows-automation', '~> 0.4.0'
# depends 'windows-library', '~> 0.1.0'
windows-automation depends on windows-library via another git reference
windows-automation Berksfile
source 'https://supermarket.chef.io'
metadata
cookbook 'powershell', '~> 6.1.3'
cookbook 'windows', '~> 4.2.5'
# cookbook 'windows-library', path: '../chef-windows-library'
cookbook 'windows-library', '~> 0.1.0', git: 'git#git.osky.io:ops/chef-windows-library.git', branch: 'master'
windows-automation metadata
supports 'windows'
depends 'powershell', '~> 6.1.3'
depends 'windows-library', '~> 0.1.0'
This issue comes when I try to run berks install for the test cookbook. I get the following output
C:\git\test (master) × berks install
Resolving cookbook dependencies...
Fetching 'test' from source at .
Fetching 'win-telegraf' from source at ../win-telegraf
Fetching 'windows-automation' from git#git.osky.io:ops/chef-windows-automation.git (at master)
Fetching cookbook index from https://supermarket.chef.io...
Unable to satisfy constraints on package windows-library, which does not exist, due to solution constraint (test = 0.1.0). Solution constraints that may result in a constraint on windows-library: [(test = 0.1.0) -> (windows-automation = 0.4.0) -> (windows-library >= 0.0.0)], [(windows-automation = 0.4.0) -> (windows-library >= 0.0.0)]
Missing artifacts: windows-library
Demand that cannot be met: (test = 0.1.0)
Unable to find a solution for demands: test (0.1.0), win-telegraf (0.1.0), windows-automation (0.4.0)
This issue gets resolved if in the test cookbook I add a dependency to windows-library. But I am wondering why berkshelf cannot resolve this without the dependency. I feel like I should not need to explicitly depend on all transative git dependencies.
Known issue with berkshelf that is marked as wontfix.
https://github.com/berkshelf/berkshelf/issues/1829
After adding 'com.google.android.material:material-rc01' in place of com.android.support:design as per documentation, studio failed to detect the dependency.
Then I downgrade the version of dependency to
implementation 'com.google.android.material:material:1.1.0-alpha09'
and it works.
But why this problem arises? any explanation?
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation"org.jetbrains.kotlin:kotlin-stdlib-
jdk7:$kotlin_version"
implementation 'androidx.appcompat:appcompat:1.0.2'
implementation 'com.google.android.material:material-rc01'
implementation 'androidx.core:core-ktx:1.0.2'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'androidx.test:runner:1.2.0'
androidTestImplementation 'androidx.test.espresso:espresso core:3.2.0'
}
ERROR: Failed to resolve: com.google.android.material:material-rc01:
Affected Modules: app
The error arises due to the fact that you're not specifying a version for the implementation; the program needs the following:
The group
The name of the dependency to implement
Version of the dependency
All this is covered in more detail here
When I got this error message, I solved it with the below line:
implementation 'com.google.android.material:material:1.0.0-rc01'
As you can see, the line above follows the implement 'compileGroup:name:version' pattern from the list, which in this case is 1.0.0-rc01; -rc01 seems to be a name for the version, just like -alpha09.
Note as well that you are not downgrading as you say if you didn't specify a version previously, which is why your app couldn't build.
I just had the same issue. I solved it by using the following dependency:
implementation "com.google.android.material:material:1.0.0"
To solve such issues you always can check if the lib you are looking for does really exists in Google's Maven repo: https://dl.google.com/dl/android/maven2/index.html
Hope that help, cheers!
I'm currently trying to build a signed release APK on Windows using Flutter. I've performed the tasks outlined in the documentation on the flutter site. When I run the build command here's the output I get. It seems to be around the firebase plugins. Any ideas?
pubspec.yaml
dependencies:
flutter:
sdk: flutter
firebase_auth: 0.4.0
firebase_database: ^0.3.0
Flutter Doctor Output
C:\Users\myuser\projects\myflutterapp>flutter doctor
[√] Flutter (on Microsoft Windows [Version 10.0.16299.125], locale en-US, channel alpha)
• Flutter at C:\Users\myuser\flutter
• Framework revision 8f65fec5f5 (3 weeks ago), 2017-12-12 09:50:14 -0800
• Engine revision edaecdc8b8
• Tools Dart version 1.25.0-dev.11.0
• Engine Dart version 2.0.0-edge.d8ae797298c3a6cf8dc9f4558707bd2672224d3e
[√] Android toolchain - develop for Android devices (Android SDK 27.0.1)
• Android SDK at C:\Users\myuser\AppData\Local\Android\Sdk
• Android NDK at C:\Users\myuser\AppData\Local\Android\Sdk\ndk-bundle
• Platform android-27, build-tools 27.0.1
• ANDROID_HOME = C:\Users\myuser\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)
[√] Android Studio (version 3.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)
[-] Connected devices
• None
Error Log Information
C:\Users\myuser\projects\myflutterapp>flutter build apk --release
Initializing gradle... 0.9s
Resolving dependencies... 1.1s
Running 'gradlew assembleRelease'...
Configuration 'debugCompile' in project ':app' is deprecated. Use 'debugImplementation' instead.
Configuration 'profileCompile' in project ':app' is deprecated. Use 'profileImplementation' instead.
Configuration 'releaseCompile' in project ':app' is deprecated. Use 'releaseImplementation' instead.
Configuration 'compile' in project ':app' is deprecated. Use 'implementation' instead.
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
Configuration 'debugProvided' in project ':firebase_auth' is deprecated. Use 'debugCompileOnly' instead.
Configuration 'releaseProvided' in project ':firebase_auth' is deprecated. Use 'releaseCompileOnly' instead.
Configuration 'compile' in project ':firebase_core' is deprecated. Use 'implementation' instead.
Configuration 'debugProvided' in project ':firebase_core' is deprecated. Use 'debugCompileOnly' instead.
Configuration 'releaseProvided' in project ':firebase_core' is deprecated. Use 'releaseCompileOnly' instead.
Configuration 'debugProvided' in project ':firebase_database' is deprecated. Use 'debugCompileOnly' instead.
Configuration 'releaseProvided' in project ':firebase_database' is deprecated. Use 'releaseCompileOnly' instead.
Skipping AOT snapshot build. Fingerprint match.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:profileRuntimeClasspath'.
> Could not resolve project :firebase_auth.
Required by:
project :app
> Unable to find a matching configuration of project :firebase_auth:
- Configuration 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found compatible value 'java-runtime'.
- Configuration 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'release'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'release'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found compatible value 'java-runtime'.
> Could not resolve project :firebase_database.
Required by:
project :app
> Unable to find a matching configuration of project :firebase_database:
- Configuration 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found compatible value 'java-runtime'.
- Configuration 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'release'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'release'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found compatible value 'java-runtime'.
> Could not resolve project :firebase_core.
Required by:
project :app
> Unable to find a matching configuration of project :firebase_core:
- Configuration 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found compatible value 'java-runtime'.
- Configuration 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'release'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'profile' and found incompatible value 'release'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required.
- Required org.gradle.api.attributes.Usage 'java-runtime' and found compatible value 'java-runtime'.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help at https://help.gradle.org
BUILD FAILED in 38s
Gradle build failed: 1
Turns out, the best way to handle this is to make the following change in android/app/build.gradle:
android {
compileSdkVersion 26
buildToolsVersion '26.0.3'
lintOptions {
disable 'InvalidPackage'
}
defaultConfig {
applicationId "com.example.app"
minSdkVersion 16
targetSdkVersion 26
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
signingConfigs {
release {
keyAlias keystoreProperties['keyAlias']
keyPassword keystoreProperties['keyPassword']
storeFile file(keystoreProperties['storeFile'])
storePassword keystoreProperties['storePassword']
}
}
// This is the main section that I've updated
// to get the release APK to build
buildTypes {
release {
profile {
matchingFallbacks = ['debug', 'release']
}
signingConfig signingConfigs.release
}
}
}
flutter {
source '../..'
}
dependencies {
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.1'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'
}
apply plugin: 'com.google.gms.google-services'
With this change I was able to build the release APK.
try this:
lintOptions {
disable 'InvalidPackage'
checkReleaseBuilds false
}
android/app/build.gradle
I just deactivated the lint. It solved my release built issue.
lintOptions {
disable 'InvalidPackage'
checkReleaseBuilds false
}
I had the same error, it turned out that I used buildTypes by mistake twice
buildTypes {
buildTypes {
.....
}
}
If you are having issue with build apk from android then try using terminal commands:
Flutter build apk --build-name =1.0.1
Flutter build apk --build-Number=10
Flutter build apk --build-name =1.0.1 --build-number=10
Make sure you will always change build name and build number when build apk. For example, if your last version name is 1.0.1 use 1.0.2 or higher and also with build number=11. Every time change this and your issue will be fixed.
I tried changing from debug to release. That solution didn't work for me. However, when I checked this site: https://www.dartlang.org/tools/pub/dependencies it says you can set a dependency without specifying a version. So in the pubspec.yaml file I did this and it worked for me...
dependencies:
flutter:
sdk: flutter
image_picker:
google_sign_in:
firebase_analytics:
firebase_auth:
firebase_database:
firebase_storage: