Test161 will not update past version 1.3.1

I tried updating test161 in order to submit but it will not update past version 1.3.1. I am running Ubuntu 16.04. I have tried clean installing as well and upon installation, test161 is still version 1.3.1 and will not allow submission because I am not at the most current version.

Does this not work?

sudo apt-get update && sudo apt-get upgrade

That does not work. I also clean installed everything and repulled from the repository and tried again. The version is still 1.3.1 and I am still unable to submit.

Odd. I just removed it and reinstalled it on my vagrant instance (16.04) and it was fine. The ops-class source repo won’t matter here since test161 comes from launchpad. I’d probably do the following:

Make sure it’s running the test161 binary that it should be. This should be /usr/bin/test161.

which test161

Make sure sudo apt-get update actually updated things:

apt-cache show test161

The version that the apt-cache command should output is Version: 1.3.2~20170304~xenial0.

which test161 displays /usr/bin/test161 as expected.

apt-cache show test161 displays the following:

Package: test161
Priority: optional
Section: utils
Installed-Size: 17803
Maintainer: Scott Haseley shaseley@buffalo.edu
Architecture: amd64
Version: 1.3.1~20170219~xenial1
Depends: libc6 (>= 2.4)
Filename: pool/main/t/test161/test161_1.3.1~20170219~xenial1_amd64.deb
Size: 3971358
MD5sum: 6191ca52875add2fe60ca416086c31be
SHA1: 83670b376646d0f0e846abe73d20312d9e00f000
SHA256: d76f0f21f92f0c40d99717ae96225ca699e339986a6a8661fc88c1cde693520f
Description-en: OS/161 testing tool
test161 is a command line tool and server for automated testing of OS/161
operating system kernels.
Description-md5: 575cd965c5ec170a46454bd9451c4d65

The problem seems to be that apt-get update is not actually updating things. I’ll look into why but if you have any solutions they’d be much appreciated.

What do you mean by this? test161 isn’t installed from a repository—it’s installed using apt-get. So there is nothing to pull…?

Was just trying to cover all of my bases. It ended up being that the ppa was somehow disabled.

1 Like

Normally when you upgrade to a new Ubuntu version PPAs are disabled. Not sure why that would have happened otherwise. Glad you got it sorted.