package.own_source_invalid: Application's packages: lists your company's git locations wrongly

Application's packages: lists your company's git locations wrongly.

Area 11, External services; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

A package from a repository under one of own_sources: installs without a person's acceptance, so the list says exactly whose code the app trusts. An entry is a host and a path ending in /, and is matched by its host and its whole path parts. Anything else could read as covering more than it does, or cover nothing while a reviewer believes it does, so Jadpo doesn't guess what was meant.

What it looks like

An entry with no path would let in every repository on the host:

example

application {    packages: {        own_sources: ["github.com/"]    }}

jadpo checkcheck failed: 1 error, 1 file

error github.com/ isn't a host and a path ending in /

--> main.jadpo:3:23

  |3 |         own_sources: ["github.com/"]  |                       ^^^^^^^^^^^^^ not a git location

reason: An entry is a host and a path ending in /, such as github.com/acme/: github.com/ alone would let in every repository on the host, a stranger's among them.
next: Name the company's folder on the host, such as github.com/acme/ (agent)
rule: package.own_source_invalid
help: https://jadpo.dev/docs/errors/package.own_source_invalid

(agent) at the end of the next: line means your coding agent can make the fix itself.

An entry that doesn't end in / is refused, with the edit to the one that does:

example

application {    packages: {        own_sources: ["github.com/acme"]    }}

jadpo checkcheck failed: 1 error, 1 file

error github.com/acme isn't a host and a path ending in /

--> main.jadpo:3:23

  |3 |         own_sources: ["github.com/acme"]  |                       ^^^^^^^^^^^^^^^^^ not a git location

reason: An entry is a host and a path ending in /, such as github.com/acme/. An entry ends in / so that what it covers reads plainly: github.com/acme/ covers github.com/acme/tools, and never github.com/acme-evil/tools.
next: Write github.com/acme/ (agent)
rule: package.own_source_invalid
help: https://jadpo.dev/docs/errors/package.own_source_invalid

So is an address with a scheme, which says how a repository is fetched, not whose it is:

example

application {    packages: {        own_sources: ["https://github.com/acme/"]    }}

jadpo checkcheck failed: 1 error, 1 file

error https://github.com/acme/ isn't a host and a path ending in /

--> main.jadpo:3:23

  |3 |         own_sources: ["https://github.com/acme/"]  |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^ not a git location

reason: An entry is a host and a path ending in /, such as github.com/acme/, with no scheme: https:// is how a repository is fetched, not whose it is.
next: Write github.com/acme/ (agent)
rule: package.own_source_invalid
help: https://jadpo.dev/docs/errors/package.own_source_invalid

A misspelt setting is refused with the edit to own_sources, since a list that was never read would let nothing in without a word:

example

application {    packages: {        own_source: ["github.com/acme/"]    }}

jadpo checkcheck failed: 1 error, 1 file

error own_source isn't something packages: holds

--> main.jadpo:3:9

  |3 |         own_source: ["github.com/acme/"]  |         ^^^^^^^^^^ not a setting

reason: packages: holds only own_sources:, your company's git locations.
next: Use own_sources instead of own_source (agent)
rule: package.own_source_invalid
help: https://jadpo.dev/docs/errors/package.own_source_invalid

How to fix it

If the entry should cover your company's repositories, write its host and the folder that holds them, ending in /:

example

application {    packages: {        own_sources: ["github.com/acme/"]    }}

A package locked from github.com/acme/postcodes now needs no PackageChange.git_source, and github.com/acme-evil/postcodes still does. The change that adds the entry needs a person's acceptance itself: "github.com/acme/": PolicyChange.own_source_added.

Why Jadpo refuses it

What it looks like

How to fix it

Related