I had to update some packages, related to GNOME. I simply executed a yum update:
yum update libsoup PackageKit PackageKit-glib pipewire pipewire-libs python3-gobject python3-gobject-base tracker
Now there are two versions of each package installed.
ex:
Installed Packages
Name : tracker
Version : 2.1.5
Release : 1.el8
Architecture : x86_64
Size : 4.1 M
Source : tracker-2.1.5-1.el8.src.rpm
Repository : #System
From repo : AppStream
Summary : Desktop-neutral metadata database and search tool
URL : https://wiki.gnome.org/Projects/Tracker
License : GPLv2+
Description : Tracker is a powerful desktop-neutral first class object database,
: tag/metadata database and search tool.
Name : tracker
Version : 2.1.5
Release : 2.el8
Architecture : x86_64
Size : 4.0 M
Source : tracker-2.1.5-2.el8.src.rpm
Repository : #System
How do I get the system to use the new package and remove the old one, like yum update does every other time?
Related
I am trying to upload images in ASW S3. But I get the error Class 'League\Flysystem\AwsS3v3\AwsS3Adapter' not found. So I tried to run composer require league/flysystem-aws-s3-v3 But it gives me error . The error is :
Problem 1
- league/flysystem-aws-s3-v3[2.0.0, ..., 2.x-dev] require league/flysystem ^2.0.0 -> found league/flysystem[2.0.0-alpha.1, ..., 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3[2.0.0-alpha.1, ..., 2.0.0-alpha.2] require league/flysystem 2.0.0-alpha.1 -> found league/flysystem[2.0.0-alpha.1] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3[2.0.0-alpha.4, ..., 2.0.0-beta.1] require league/flysystem 2.0.0-alpha.3 -> found league/flysystem[2.0.0-alpha.3] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3[2.0.0-beta.2, ..., 2.0.0-beta.3] require league/flysystem ^2.0.0-beta.1 -> found league/flysystem[2.0.0-beta.1, ..., 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3 2.0.0-RC1 requires league/flysystem ^2.0.0-RC1 -> found league/flysystem[2.0.0-RC1, 2.0.0, 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires league/flysystem-aws-s3-v3 ^2.0 -> satisfiable by league/flysystem-aws-s3-v3[2.0.0-alpha.1, ..., 2.x-dev].
My PHP version is : 7.4.11 and my Alaravel version is 7.30.0. Can someone please help me to resolve this?
You should try run this command in your terminal
composer require league/flysystem-aws-s3-v3 ^1.0
It works very well in my last experience using Laravel 7.30.3 (PHP v7.4)
I'm newcomer in drupal management with composer. As it, I need to do updates on my D8 websites (migrated from D6).
And I get mismatched informations between drush and composer, like this:
$ composer outdated drupal/*
drupal/feeds 3.0.0-alpha5 3.0.0-alpha6 Aggregates RSS/Atom/RDF feeds, imports CSV files and more.
drupal/migrate_tools 4.3.0 4.4.0 Tools to assist in developing and running migrations.
$ drush #sited8 pml --filter=feed
--------- ---------------------------------------- ---------- ----------------
Package Name Status Version
--------- ---------------------------------------- ---------- ----------------
Feeds Feeds (feeds) Disabled 8.x-3.0-alpha4
$ drush #sited8 pml --filter=migr
-------------------------- --------------------------------------------- --
Package Name Status Version
-------------------------- -----------------------------------------------
Migration Migrate Tools (migrate_tools) Disabled 8.x-4.1
So what's the good way to proceed with disabled modules ? Do I need to delete them with composer ? Doesn't exist a similar status as "disabled" for composer ?
Thanks
EDIT: good practice fixed, but what about mismatched informations between drush and composer ?
EDIT2: another case of mismatched informations
composer outdated drupal/*
drupal/admin_toolbar 1.27.0 2.0.0 Provides a drop-down menu interface to the core Drupal Toolbar.
drupal/better_exposed_filters 3.0.0-alpha6 4.0.0-alpha1 Provides advanced options (such as links, checkboxes, or jQueryUI widgets) for exposed Views elements.
drupal/webform 5.4.0 5.5.0 Enables the creation of webforms and questionnaires.
#ssh4:~/www/celony/sited8$ composer update drupal/admin_toolbar drupal/better_exposed_filters
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
More info: if update is mentionned as red I can run composer update, if it's in yellow, I do use composer require instead. Perhaps normal way ?
https://getcomposer.org/doc/03-cli.md#outdated
Is there a way to find, via an API or CLI, the latest available version of Gradle?
I'm working on a tool to check versions of dependencies and compare them to the latest versions, and I need a way to determine what the latest version of Gradle that is available.
To be clear, I am not looking for the version of Gradle I already have. I know how to get that any number of ways. I'm just looking for some officially maintained endpoint I can call to determine the latest version available.
Gradle has an API to retrieve all sorts of information:
https://services.gradle.org/
For the current version:
GET https://services.gradle.org/versions/current
{
"version" : "6.8.1",
"buildTime" : "20210122132008+0000",
"current" : true,
"snapshot" : false,
"nightly" : false,
"releaseNightly" : false,
"activeRc" : false,
"rcFor" : "",
"milestoneFor" : "",
"broken" : false,
"downloadUrl" : "https://services.gradle.org/distributions/gradle-6.8.1-bin.zip",
"checksumUrl" : "https://services.gradle.org/distributions/gradle-6.8.1-bin.zip.sha256",
"wrapperChecksumUrl" : "https://services.gradle.org/distributions/gradle-6.8.1-wrapper.jar.sha256"
}
You can get the data using curl and then use jq to extract the version key.
Node.js has in-built JSON support so this will be even easier.
CURRENT_GRADLE_VERSION="$(curl -s https://services.gradle.org/versions/current | jq -r '.version')"
echo "${CURRENT_GRADLE_VERSION}" # prints 6.8.1
I have a module App::Assixt, to which I've recently made a relatively large change. I've of course tested it on my local system, but would like to give it some field testing before calling it a "stable release".
Is there a way to "tag" this release as an "alpha", or "release-candidate", so this release will only be installed by people who have opted to use unstable/testing releases?
zef will treat versions the same as Perl 6:
# true because "1.0.a" < "1.0.0"
$ perl6 -e 'say Version.new("1.0.PREVIEW") < Version.new("1.0")'
True
If a Foo:ver<1.0.PREVIEW> is installed it can be used as Foo:ver<1.0.PREVIEW> or Foo:ver<1.0>. This means any systems that have Foo:ver<1.0.PREVIEW> installed would need to uninstall it to upgrade / install Foo:ver<1.0> in the future ( unless using --force-install ), but also that authors can write code for the final version without declaring the extra .PREVIEW everywhere.
This is not very useful in regards to publishing -- zef will grab the newest version by default despite the user not having opted in to whatever versioning scheme is in use. Since the user wants to opt-in for this, there are two options.
1) Create e.g. unstable, testing, stable` indexes and convince people to use them
This could be done by copying the zef config to %*ENV<XDG_CONFIG_HOME>/zef/config.json and incorporate the following:
"Repository" : [
{
"short-name" : "unstable",
"enabled" : 0,
"module" : "Zef::Repository::Ecosystems",
"options" : {
"name" : "unstable",
"mirrors" : [ "/path/or/url/to/package/list.json" ]
}
}
]
Which allows:
zef install Foo::Bar --unstable
2) Give out a link to the resource without publishing it
zef install https://github.com/ugexe/Perl6-Text--Table--Simple.git#v0.0.4
zef install https://github.com/ugexe/Perl6-Text--Table--Simple/archive/v0.0.3.zip
I am using window command prompt,When I update composer facing with below error
C:\xampp\htdocs\myproject>composer update
Warning: This development build of composer is over 60 days old. It is recommend
ed to update it by running "C:\ProgramData\ComposerSetup\bin\composer.phar self-
update" to get the latest version.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Failed to decode response: zlib_decode(): data error
Retrying with degraded mode, check https://getcomposer.org/doc/articles/troubles
hooting.md#degraded-mode for more info
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for phalcon/incubator dev-master -> satisfiable by ph
alcon/incubator[dev-master].
- phalcon/incubator dev-master requires ext-phalcon >=2.0.4 -> the requested
PHP extension phalcon is missing from your system.
The last line should give you a clue: You haven't yet installed PhalconPHP on your system, which is required by the Incubator package.
Also, run a composer self-update as recommended.