How to replace a cache package file with same name

[narcisgarcia]

I have pushed this package to a Debian archive:
sltd_1.1.6_all.deb
I've fixed some detail to package scripts (preinst, postinst,...) and packed again with dpkg-buildpackage, but freight-add and freight-cache commands don't update library/cache because they say that sltd_1.1.6_all.deb already exist.

How can I replace a .deb file that has same name?

[roelvanmeer]

There might be a better way, but this is the method I use:

• Remove the package from the lib dir
• Remove the package from the pool (important!)
• Update the freight cache

Then add the package as you normally would.

[mmoll]

I'm also using the @roelvanmeer method and think it would the normal Debian way to increment the package version (and also start with -1, e.g. 1.1.6-1).

[narcisgarcia]

I'll try @roelvanmeer method. The needing begun when I was debugging preinst/postinst/prerm/postrm files and needed to re-package, publish and install more than 50 times.

What's the difference between removal of these two from the pool?
debian/dists/jessie-20170404004935713703617/.refs/contrib/sltd_1.1.8_all.deb
debian/pool/jessie/contrib/s/sltd/sltd_1.1.8_all.deb

Is it enough to do after lib dir removal, this?
freight-clear-cache jessie/contrib
freight-cache jessie/contrib

[emillynge]

I need the ability to replace a deb file with incremented version in control file, but with the same name.
e.g. mypackage-1.0.deb with a control file where the actual version is 1.0-2.

How much work would be needed to implement a --force flag in the freight-add command? such that any package with the same file name gets purged such that the package can be added? I may be able to throw some time after the problem, if it wont take too much time and there is a possibility of getting a PR accepted.