On 2/18/20 1:06 AM, Chris Billington via arch-general wrote: > [community]/python-tqdm has updated 13 times in the last week, though the > upstream has not been releasing that rapidly - the new Arch packages > correspond to the last few months of releases. > > This process hasn't quite gotten it up to date yet, so I expect one more > update is on the way! > > Is there a reason for not just skipping right to the latest version, if > several intermediate versions were missed? > > If this is for testing (incremental updates are usually easier to test), > presumably it should occur in [testing]. > > Or perhaps this is the behaviour of some automated tooling that is > detecting when a package is out of date, and a human hasn't noticed? Actually updating of tqdm was blocked for quite some time due to tests being broken (which turns out to be my fault that used a broken way to run it). I did intensionally slow down the update to examine and check changelogs, also run it for a while so this won't happen again. Sorry for the trouble caused and it should soon be up-to-date. -- Regards, Felix Yan
Attachment:
signature.asc
Description: OpenPGP digital signature
