No yarnrc.yml even after following directions - yarn-v2

This instruction:
`https://devcenter.heroku.com/articles/migrating-to-yarn-2
says to run yarn install and it will create a .yarnrc.yml file. It does not. yarn
install reports no errors and I can run yarn set version berry and I get:
Wed Jun 29 12:43:22 MDT 2022
➤ YN0000: Retrieving https://repo.yarnpkg.com/3.2.1/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-3.2.1.cjs
➤ YN0000: Done in 0s 327ms
I tried yarn set version 2 and then yarn install, but still no joy.
scottc in ~/Sites/vpermits.us on branch main > yarn set version 2
Wed Jun 29 12:44:52 MDT 2022
➤ YN0000: Retrieving https://repo.yarnpkg.com/2.4.3/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-2.4.3.cjs
➤ YN0000: Done in 0s 391ms
My build fails with this error message:
-----> Building on the Heroku-20 stack
-----> Determining which buildpack to use for this app
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
USE_YARN_CACHE=true
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Build failed
! The 'yarnrc.yml' file is not found
It looks like the 'yarnrc.yml' file is missing from this project. Please
make sure this file is checked into version control and made available to
Heroku.
To generate 'yarnrc.yml', make sure Yarn 2 is installed on your local
machine and set the version in your project directory with:
$ yarn set version berry
Read more at the Yarn docs: https://yarnpkg.com/getting-started/install#per-
project-install
https://devcenter.heroku.com/articles/nodejs-support
! Push rejected, failed to compile Node.js app.
! Push failed`
There is no yarnrc.yml (or .yarnrc.yml) in my directory.

Related

CentOS Stream 8 - DNF Broken - Unable to Run Update/Upgrade

I thought I successfully upgraded from CentOS8 to Centos Stream 8, however I was never able to get dnf distro-sync to work. Now DNF appears to be broken and dnf upgrade throws unsatisfied dependencies for libsmartcols.so.1 in relation to DNF itself.
dnf distro-sync:
When running the sync, the following appears:
Error:
Problem: The operation would result in removing the following protected packages: setup
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I tried every possible combination of --skip-broken, --nobest --allowerasing, etc. to resolve. Tried using the vault versions, no difference. All of the old CentOS repos were removed, so the only repos in the /etc/yum.repos.d/ folder are -Stream-. I do not have any EPEL repos installed at this time.
cat /etc/centos-release => CentOS Stream release 8
The server survives reboots and seems to work correctly for everything else.
When running dnf -y upgrade -v, the following results:
dnf -y upgrade -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, groups-manager, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.7.0
cachedir: /var/cache/dnf
User-Agent: constructed: 'libdnf (CentOS Stream 8; generic; Linux.x86_64)'
repo: using cache for: appstream
appstream: using metadata from Tue 08 Feb 2022 07:27:22 PM EST.
repo: using cache for: baseos
baseos: using metadata from Tue 08 Feb 2022 07:26:22 PM EST.
repo: using cache for: extras
extras: using metadata from Tue 08 Feb 2022 04:08:34 PM EST.
Last metadata expiration check: 0:26:35 ago on Thu 10 Feb 2022 12:44:57 PM EST.
--> Starting dependency resolution
---> Package dnf-plugins-core.noarch 4.0.21-8.el8 will be upgraded
---> Package dnf-plugins-core.noarch 4.0.21-10.el8 will be an upgrade
---> Package libdnf.x86_64 0.63.0-5.el8 will be upgraded
---> Package libdnf.x86_64 0.63.0-7.el8 will be an upgrade
---> Package python3-dnf-plugins-core.noarch 4.0.21-8.el8 will be upgraded
---> Package python3-dnf-plugins-core.noarch 4.0.21-10.el8 will be an upgrade
---> Package python3-hawkey.x86_64 0.63.0-5.el8 will be upgraded
---> Package python3-hawkey.x86_64 0.63.0-7.el8 will be an upgrade
---> Package python3-libdnf.x86_64 0.63.0-5.el8 will be upgraded
---> Package python3-libdnf.x86_64 0.63.0-7.el8 will be an upgrade
--> Finished dependency resolution
Dependencies resolved.
==============================================================================================================================================================================================================
Package Architecture Version Repository Size
==============================================================================================================================================================================================================
Upgrading:
dnf-plugins-core noarch 4.0.21-10.el8 baseos 71 k
libdnf x86_64 0.63.0-7.el8 baseos 701 k
python3-dnf-plugins-core noarch 4.0.21-10.el8 baseos 230 k
python3-hawkey x86_64 0.63.0-7.el8 baseos 116 k
python3-libdnf x86_64 0.63.0-7.el8 baseos 778 k
Transaction Summary
==============================================================================================================================================================================================================
Upgrade 5 Packages
Total size: 1.9 M
Downloading Packages:
[SKIPPED] dnf-plugins-core-4.0.21-10.el8.noarch.rpm: Already downloaded
[SKIPPED] libdnf-0.63.0-7.el8.x86_64.rpm: Already downloaded
[SKIPPED] python3-dnf-plugins-core-4.0.21-10.el8.noarch.rpm: Already downloaded
[SKIPPED] python3-hawkey-0.63.0-7.el8.x86_64.rpm: Already downloaded
[SKIPPED] python3-libdnf-0.63.0-7.el8.x86_64.rpm: Already downloaded
Using rpmkeys executable at /usr/bin/rpmkeys to verify signatures
Running transaction check
Error: transaction check vs depsolve:
libsmartcols.so.1()(64bit) is needed by libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.25)(64bit) is needed by libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.28)(64bit) is needed by libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.29)(64bit) is needed by libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.30)(64bit) is needed by libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1()(64bit) is needed by python3-hawkey-0.63.0-7.el8.x86_64
libsmartcols.so.1()(64bit) is needed by python3-libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.25)(64bit) is needed by python3-libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.27)(64bit) is needed by python3-libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.28)(64bit) is needed by python3-libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.29)(64bit) is needed by python3-libdnf-0.63.0-7.el8.x86_64
libsmartcols.so.1(SMARTCOLS_2.30)(64bit) is needed by python3-libdnf-0.63.0-7.el8.x86_64
To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue.
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
I have tried cleaning the packages (dnf clean all), removing the cache files, individually trying to update/upgrade each package, etc.. I'm out of ideas.
Any suggestions?
Afer a couple more hours of trying, I was able to resolve it by performing the following:
Copy a CentOS-Base.repo file from another server
Edit the repo file to reflect the vault.centos.org location, turn off gpgcheck
dnf clean all
dnf install libsmartcols-2.32.1-28.el8
Ran dnf -y upgrade again and it worked. Go figure.
Hopefully, this will help someone else with the same or similar issue.

elrepo archive metadata doesn't list kernel-lt as of 2018-10-01 0600 UTC

Anyone seeing problems with the elrepo archive mirrors not able to install or list all available kernels?
yum list available --showduplicates \
--disablerepo=* --enablerepo elrepo-amirror-kernel kernel-lt
Prior to 10 am today / 6 am UTC our artifactory instance could report multiple kernel-lt packages. After whether I use artifactory or go directly to the remote repository I see nothing:
Loading "fastestmirror" plugin
Loading "presto" plugin
Running "config" handler for "presto" plugin
Config time: 0.018
Running "init" handler for "fastestmirror" plugin
Yum Version: 3.2.29
COMMAND: yum list available --showduplicates --disablerepo=* --enablerepo elrepo-amirror-kernel kernel*
Installroot: /
Ext Commands:
available
kernel*
Reading Local RPMDB
rpmdb time: 0.000
Setting up Package Sacks
Running "postreposetup" handler for "fastestmirror" plugin
Loading mirror speeds from cached hostfile
pkgsack time: 0.003
Error: No matching Packages to list
Repo definition
[elrepo-amirror-kernel]
name=ELRepo.org Community Enterprise Linux Kernel Repository - el6
baseurl=http://lon.mirror.rackspace.com/elrepo/archive/kernel/el6/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-elrepo.org
protect=0
Mirrors Tested
http://mirrors.coreix.net/elrepo-archive-archive
http://lon.mirror.rackspace.com/elrepo/archive/kernel
Direct access to repos fails, so it cannot be artifactory.
The following had no impact:
clean all, makecache
rm -rf /var/cache/yum/ and makecache
Well, there may have been a problem with our artifactory instance but this problem above was caused by an exclude for kernels to avoid automatically changing kernel upon reboot.
Adding --disableexcludes=all to the line allow us to see the kernel-lt packages.

yarn install ember-cli fails with incompatible node engine

My CircleCI builds started failing today and it looks like yarn is having trouble installing ember-cli. I tried locally and am suddenly getting the same error.
I recently upgraded to ember-cli 2.13.2, but I don't think that's related because builds were working after the upgrade.
Here's my console output:
~/code/my-app(master ✗) yarn global add ember-cli
yarn global v0.24.6
warning No license field
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
error core-object#3.1.2: The engine "node" is incompatible with this module. Expected version "=> ^4.0.0".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
What is your Node version? I've tried installing by yarn Ember CLI 1.13 project and it failed because CoreObject required versions between 4 and 7. I've downgraded Node from 8 to 7 and it worked.
I figured out my issue. I was using a Docker image that uses the latest version of node. When node updated to 8, my Circle builds started using that. I ended up creating my own image that is pegged at version 6 and using that on Circle instead.

Unable to "cf push" into Bluemix, using swift_buildpack 2.0.5

I am no longer able to push my app to Bluemix. I am using the swift_buildback for a Kitura app.
The last time I successfully pushed it, was yesterday. I noticed that the default buildpack is now 2.0.5. The last time I pay attention to that, it was 2.0.4. I don't know how to specify an older version of the buildpack, to rule out a problem there.
The cf push returns the following:
Downloading swift_buildpack...
Downloaded swift_buildpack
Creating container
Successfully created container
Downloading app package...
Downloaded app package (46.5M)
Downloading build artifacts cache...
Downloaded build artifacts cache (43.9M)
Staging...
-----> Buildpack version 2.0.5
-----> Default supported Swift version is 3.1
-----> Configure for apt-get installs...
-----> Writing profile script...
-----> Copying deb files to installation folder...
-----> No Aptfile found.
-----> Getting swift-3.0.2
-----> WARNING: Default supported Swift version: swift-3.1
-----> WARNING: Requested Swift version for your app: swift-3.0.2
Cached swift-3.0.2
-----> Unpacking swift-3.0.2.tar.gz
-----> Getting clang-3.8.0
Cached clang-3.8.0
-----> Unpacking clang-3.8.0.tar.xz
-----> .ssh directory and config file not found.
-----> Loading from cache:
-----> - Packages
-----> Fetching Swift packages and parsing Package.swift files...
-----> Additional packages to download: libcurl4-openssl-dev openssl libssl-dev
-----> libcurl4-openssl-dev is already installed.
-----> openssl is already installed.
-----> libssl-dev is already installed.
-----> No additional packages to download.
-----> Skipping installation of App Management (debug)
-----> Installing system level dependencies...
-----> Installing deb_files
dpkg-deb: error: failed to read archive `deb_files': No such file or directory
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223
Destroying container
FAILED
Error restarting application: BuildpackCompileFailed
In order to verify that your app works with the previous version of the buildpack, just add the -b <buildpack name> flag to your cf push command.
The names of the available buildpacks can be obtained by running cf buildpacks. In this case, since you want the old 2.0.4 buildpack version, the command will look like this:
cf push <app_name> -b swift_buildpack_v2_0_4-20170125-2344
The team that administers the Swift buildpack for Bluemix can help troubleshoot issues like this in their open Slack team - https://swift-at-ibm-slack.mybluemix.net.

Travis.yml failing with minimalistic contents?

I have the current travis.yml on my Github:
# see http://about.travis-ci.org/docs/user/languages/php/ for more hints
language: php
# list any PHP version you want to test against
php:
# aliased to a recent 5.4.x version
- 5.4
# aliased to a recent 5.5.x version
- 5.5
All my jobs keep failing, but with a minimalistic build, i Cannot see why it fails.. As Travis doesn't exactly have the best information.. Here is the last few chunks of my logs:
Job 9.1:
$ git clone --depth=50 --branch=master git://github.com/SlayerSolutions/Authentication.git SlayerSolutions/Authentication
Cloning into 'SlayerSolutions/Authentication'...
remote: Counting objects: 128, done.
remote: Compressing objects: 100% (104/104), done.
remote: Total 128 (delta 55), reused 83 (delta 15)
Receiving objects: 100% (128/128), 19.17 KiB | 0 bytes/s, done.
Resolving deltas: 100% (55/55), done.
$ cd SlayerSolutions/Authentication
git.2
$ git checkout -qf 1df78d018dbe8a81e66490e90012229adcff7af8
$ phpenv global 5.4
$ php --version
PHP 5.4.16 (cli) (built: Jun 28 2013 11:14:20)
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies
with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans
$ composer --version
Warning: This development build of composer is over 30 days old. It is recommended to update it by running "/home/travis/.phpenv/versions/5.4.16/bin/composer.phar self-update" to get the latest version.
Composer version 7755564962718189d5d7d9fdee595283c8f032b7
$ phpunit
PHPUnit 3.7.21 by Sebastian Bergmann.
Usage: phpunit [switches] UnitTest [UnitTest.php]
phpunit [switches] <directory>
--log-junit <file> Log test execution in JUnit XML format to file.
...Bla,bla,bla
The command "phpunit" exited with 2.
Done. Your build exited with 1.
and Job 9.2:
Is the same and ends with:
The command "phpunit" exited with 2.
Done. Your build exited with 1.
So, what is going wrong here?
Any non-zero exit code of the scripts you run with Travis are considered a failure.
Your minimalistic .travis.yml does not specify a build script, therefore the default build script for PHP is run, which is phpunit (see also the documentation).
As you don't have a phpunit.xml in your repository, there is basically nothing to run for Travis. This leads to the failing build.
It really depends what you want to do with Travis, but either you configure your repository according to the default or define a script to execute when running the build like this:
language: php
php:
- 5.4
- 5.5
script: ./build.sh
Then you can specify whatever you want in the build.sh to be executed when running build.
You may need to insure that ./build.sh is executable which you can do with
before_install:
- chmod +x build.sh
You can also make the script bash build.sh or sh build.sh.