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
You should be able to mount your FTP share and use it like you would a normal filesystem target. If I'm not mistaken, aptly will detect not being able to hardlink to your local pool and maintain a publication pool with "real" packages - I am not completely certain this will work, but please try it out.
If this does not help, it seems fixing this would be the better approach, as it would enable publishing to arbitrary mountpoints.
However, if you have any other way of connecting to the machine you want to publish your repositories to, or if you can run aptly right there, this would be a better solution. You would do yourself a favor if you stopped using FTP, relevant packages are even being phased out of general support at some places, e.g. Debian's curlftps package (Notice that there is no package for testing and bookworm, the recently released new stable codename.)
Would you add support for publishing to FTP endpoints?
For now I would have to create the snapshot with aptly with a filesystem endpoint, and then publish to FTP separately.
The text was updated successfully, but these errors were encountered: