You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While experimenting, I accidentally deleted my aptly configuration file after publishing a snapshot to a custom, file system endpoint.
With the conf files now missing, I correctly received an error message. However, the endpoint name in the error message was truncated strangely. Specifically, the "filesy" was missing from "filesystem".
$ aptly publish list
Published repositories:
* filesystem:nodesource-nodejs:./xenial [amd64] publishes {main: [nodesource-20180305]: Snapshot from mirror [nodesource]: https://deb.nodesource.com/node_6.x/ xenial}
# Deleted ~/.aptly.conf and /etc/aptly.conf
$ sudo aptly publish drop xenial filesystem:nodesource-nodejs:
ERROR: published local storage stem:nodesource-nodejs not configured
I'm using aptly 1.2.0 on Ubuntu 16.04.
While experimenting, I accidentally deleted my aptly configuration file after publishing a snapshot to a custom, file system endpoint.
With the conf files now missing, I correctly received an error message. However, the endpoint name in the error message was truncated strangely. Specifically, the "filesy" was missing from "filesystem".
It seems like this is happening in https://github.com/smira/aptly/blob/9cb2a302f8f138dba7887c848f956633f8b3eb01/context/context.go. I'm not sure why it skips over the first 6 characters.
The text was updated successfully, but these errors were encountered: