Be the first to post a text review of slackcurrent. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• File released: /slackcurrent/slackcurrent-0.1.6/slackcurrent-0.1.6-noarch-1.tgz.asc

  posted 646 days ago

• File released: /slackcurrent/slackcurrent-0.1.6/slackcurrent-0.1.6-noarch-1.tgz

  posted 646 days ago

• slackcurrent slackcurrent-0.1.6 file released: slackcurrent-0.1.6-noarch-1.tgz.asc

  - The version tokens were expanded to 4 tokens now. There were some problem (again!) with packages with crazy names (and they were official ones!) so I decided to expand the version tokens to 4 to try to deal with more exceptions. Thanks to Trevor Carey-Smith for warning me about that! - A lot more of testing on slackcurrent_test.py. - When asked to create the upgrade list, Slackcurrent now tells you about some packages (local and remote) that will not be handled because of their name formats. May be the names are ok and you just found another bug, but there are some packages that really don't follow the package name conventions. You'll need to download and upgrade those packages manually. - The invalid local packages can be checked using -li or --list-invalid-local. If you are using Slackcurrent as part of another app, you can get the list using the getlocalinvalidlist() method. - The invalid remote packages can be checked using -ri or --list-invalid-remote. If you are using Slackcurrent as part of another app, you can get the list using the getremoteinvalidlist() method.

  posted 646 days ago

• slackcurrent slackcurrent-0.1.6 file released: slackcurrent-0.1.6-noarch-1.tgz

  - The version tokens were expanded to 4 tokens now. There were some problem (again!) with packages with crazy names (and they were official ones!) so I decided to expand the version tokens to 4 to try to deal with more exceptions. Thanks to Trevor Carey-Smith for warning me about that! - A lot more of testing on slackcurrent_test.py. - When asked to create the upgrade list, Slackcurrent now tells you about some packages (local and remote) that will not be handled because of their name formats. May be the names are ok and you just found another bug, but there are some packages that really don't follow the package name conventions. You'll need to download and upgrade those packages manually. - The invalid local packages can be checked using -li or --list-invalid-local. If you are using Slackcurrent as part of another app, you can get the list using the getlocalinvalidlist() method. - The invalid remote packages can be checked using -ri or --list-invalid-remote. If you are using Slackcurrent as part of another app, you can get the list using the getremoteinvalidlist() method.

  posted 646 days ago

• File released: /slackcurrent/slackcurrent-0.1.5/slackcurrent-0.1.5-noarch-1.tgz.asc

  posted 777 days ago

• File released: /slackcurrent/slackcurrent-0.1.5/slackcurrent-0.1.5-noarch-1.tgz

  posted 777 days ago

• slackcurrent slackcurrent-0.1.5 file released: slackcurrent-0.1.5-noarch-1.tgz.asc

  - Fixed a bug about how to check some packages with version numbers like 1.2.99.905 were calculated. The number got an overflow on the 3 digits limit and there we go to avoid updates to the package. :-( - Added an unit test file on /etc/slackcurrent.

  posted 777 days ago

• slackcurrent slackcurrent-0.1.5 file released: slackcurrent-0.1.5-noarch-1.tgz

  - Fixed a bug about how to check some packages with version numbers like 1.2.99.905 were calculated. The number got an overflow on the 3 digits limit and there we go to avoid updates to the package. :-( - Added an unit test file on /etc/slackcurrent.

  posted 777 days ago

• File released: /slackcurrent/slackcurrent-0.1.4/slackcurrent-0.1.4-noarch-1.tgz.asc

  posted 1339 days ago

• File released: /slackcurrent/slackcurrent-0.1.4/slackcurrent-0.1.4-noarch-1.tgz

  posted 1339 days ago