Debian 10 Buster 64bits

Logs

====== Attempt #1

-----> Fetching repository

Cloning into '/tmp/d20200306-6-pg1q6p/input'...

-----> Setting up package repository...

-----> Starting packaging process

-----> Additional environment variables

UUID=4c881773-ba4f-4fd3-a3ab-44d99d55effd

HOME=/home/pkgr

-----> Found valid cache

-----> Restoring cache...

-----> Fetching pkgr fdcef6d6bdaab4a74a061ac32a4e17b255faa93d...

-----> Starting packaging process...

-----> Fetching buildpack https://github.com/pkgr/heroku-buildpack-ruby.git at v206-1

-----> Fetching buildpack https://github.com/pkgr/heroku-buildpack-python.git at buildcurl

-----> Fetching buildpack https://github.com/heroku/heroku-buildpack-nodejs.git at v106

-----> Node.js app

-----> Creating runtime environment

NPM_CONFIG_PRODUCTION=true

NPM_CONFIG_LOGLEVEL=error

NODE_VERBOSE=false

NODE_ENV=production

NODE_MODULES_CACHE=true

-----> Installing binaries

engines.node (package.json): >=8

engines.npm (package.json): unspecified (use default)

Resolving node version >=8 via semver.io...

Downloading and installing node 13.10.1...

Detected package-lock.json: defaulting npm to version 5.x.x

Resolving npm version 5.x.x via semver.io...

Downloading and installing npm 5.10.0 (replacing version 6.13.7)...

-----> Restoring cache

Skipping cache restore (new-signature)

-----> Building dependencies

Installing node modules (package.json)

up to date in 1.624s

[!] 2 vulnerabilities found [5519 packages audited]

Severity: 1 Low 1 High

Run `npm audit` for more detail

-----> Caching build

Clearing previous node cache

Saving 2 cacheDirectories (default):

- node_modules (nothing to cache)

- bower_components (nothing to cache)

-----> Build succeeded!

! This app may not specify any way to start a node process

https://devcenter.heroku.com/articles/nodejs-support#default-web-process-type

-----> Uploading packages

PACKAGE: gitea_1.10.4-1583476471.81072af8.buster_amd64.deb (62.54 MiB)

-----> DONE in 88s