Recently I faced with the "strange" pinto behavior. This is "user story"
Step1. I added distinct version of package "Foo" with pinto add command, let say version 0.1.0
Step2 After a few weeks or months, the author of "Foo" package released new version, let say 0.2.0. I decided to pull package "Foo" with pinto pull command, expecting I will be taken latest version. Pinto "silently" took old distribution archive ( was created in step 1) and instead of pulling new version created index pointed to old version - 0.1.0
It may lead to subtle bugs, hard to investigate.
I know this is how pinto works with distributions archives and packages, .... but to make long story short, I'd like to monitor such a situations with something like that:
akarelas
commented
10 years ago
Recently I faced with the "strange" pinto behavior. This is "user story"
pinto addcommand, let say version 0.1.0pinto pullcommand, expecting I will be taken latest version. Pinto "silently" took old distribution archive ( was created in step 1) and instead of pulling new version created index pointed to old version - 0.1.0 It may lead to subtle bugs, hard to investigate.I know this is how pinto works with distributions archives and packages, .... but to make long story short, I'd like to monitor such a situations with something like that: