Cmd version tested:
  • Sencha Cmd v6.0.0.202
Ext version tested:

  • Ext 6.0.0.640
Description:
  • After using sencha package upgrade the sencha.cfg in the package is broken. It seems like some necessary configs are completly removed. Requiring the package in an app leeds to a failed build:
    Code:
    [ERR] com.sencha.exceptions.ExNotFound: Unknown definition for dependency
Diff of .sencha/package/sencha.cfg:
Code:
--- a/.sencha/package/sencha.cfg
+++ b/.sencha/package/sencha.cfg
@@ -1,53 +1,3 @@
-# The name of the package - should match the "name" property in ./package.json
-#
-package.name=basepackage
-
-# The namespace to which this package's SASS corresponds. The default value of
-# "Ext" means that the files in ./sass/src (and ./sass/var) match classes in
-# the Ext" root namespace. In other words, "Ext.panel.Panel" maps to
-# ./sass/src/panel/Panel.scss.
-# 
-# To style classes from any namespace, set this to blank. If this is blank,
-# then to style "Ext.panel.Panel" you would put SASS in
-# ./sass/src/Ext/panel/Panel.scss.
-#
-package.sass.namespace=Ext
-
-# This is the comma-separated list of folders where classes reside. These
-# classes must be explicitly required to be included in the build.
-#
-package.classpath=${package.dir}/src
-
-# This is the comma-separated list of folders of overrides. All files in this
-# path will be given a tag of "packageOverrides" which is automatically
-# required in generated apps by the presence of this line in app.js:
-#
-#   //@require @packageOverrides
-#
-package.overrides=${package.dir}/overrides
-
-# This is the folder where SASS "src" resides. This is searched for SCSS
-# files that match the JavaScript classes used by the application.
-#
-package.sass.srcpath=${package.dir}/sass/src
-
-# This is the folder where SASS "vars" resides. This is searched for SCSS
-# files that match the JavaScript classes used by the application.
-#
-package.sass.varpath=${package.dir}/sass/var
-
-# This file is automatically imported into the SASS build before "vars".
-#
-package.sass.etcpath=${package.dir}/sass/etc/all.scss
-
-# This is the folder in which to place "sencha packaage build" output.
-#
-package.build.dir=${package.dir}/build
-
-# The folder that contains example application(s) for this package.
-#
-package.examples.dir=${package.dir}/examples
-
 # The folder that contains sub-packages of this package. Only valid for "framework"
 # package type.
 #
@@ -57,4 +7,4 @@ package.subpkgs.dir=${package.dir}/packages
 # Custom Properties - Place customizations below this line to avoid merge
 # conflicts with newer versions
 
-package.cmd.version=6.0.0.154
+package.cmd.version=6.0.0.202
Steps to reproduce the problem:
  • upgrade sencha cmd to 6.0.0.202
  • upgrade ext to 6.0.0.640
  • upgrade package with "sencha package upgrade
How to solve the problem:
  • Readd the removed lines to sencha.cfg
  • sencha package build


Maybe someone else has similar problems and can make use of this Post.

I'm also interested in the reason of this issue/change.