Bug#667068: wajig new - exits if package not in database

Package: wajig Version: 2.4.1 Followup-For: Bug #667068 Sorry, command as follows: # wajig new The cache has no package named 'libgecodeflatzinc31' I believe this occurs when some time has passed between running "wajig update" and "wajig new", during which the package database has been updated

Bug#667068: wajig new - exits if package not in database

> Dear Maintainer, > > if the apt-cache query fails for a package name, wajig exits with something > like: > The cache has no package named 'libgecodeflatzinc31' > > Even if there is a missing package, we would still like to see details of > other packages, so... > > p# diff util.py util.py.new >

Bug#667068: wajig new - exits if package not in database

Package: wajig Version: 2.4.1 Severity: normal Dear Maintainer, if the apt-cache query fails for a package name, wajig exits with something like: The cache has no package named 'libgecodeflatzinc31' Even if there is a missing package, we would still like to see details of other packages, so...