vivid doesn't seem to have hdf5 packages

Asked by Nico Schlömer on 2015-01-02

```
$ apt search hdf5
```
yields no result on the latest vivid snapshot.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu hdf5 Edit question
Assignee:
No assignee Edit question
Solved by:
Nico Schlömer
Solved:
2015-01-06
Last query:
2015-01-06
Last reply:
2015-01-06

I suggest you report a bug. Vivid is not ready and not stable. If you want an OS that works as expected then I suggest you reinstall with Trusty and stay off pre-releases.

Pre-releases are not for the casual user. They are for users who want to report bugs to get the release ready for release dsy but don't mind feature holes and random crashes.

Manfred Hampl (m-hampl) said : #2

The packages are there, see https://launchpad.net/ubuntu/+source/hdf5/1.8.13+docs-15

Not sure. however, why they are not shown in the snapshot that you are using.

What is the output of the command

dpkg -l hdf5-tools

after updating the apt cache with

sudo apt-get update

?

Nico Schlömer (nschloe) said : #3

@actionparsnip Of course this isn't on my production system, just on a test box I use to rule out and obvious errors before a release.

@m-hampl
```
$ sudo apt-get update
[...]
$ dpkg -l hdf5-tools
dpkg-query: no packages found matching hdf5-tools
```
I do see that the packages are all supposed to be there (cf. the link you provide), so I guess there's something amiss with the current nightly snapshot. Where do I best file a bug?

If you run:

ubuntu-bug hdf5

It will start the process for you.

Nico Schlömer (nschloe) said : #5

@actionparsnip
```
$ ubuntu-bug hdf5
[...]
The problem cannot be reported:

The report belongs to a package that is not installed.
[...]
```
I wasn't sure either if this is a problem of the HDF5 package of vivid's packaging infrastructure.

Manfred Hampl (m-hampl) said : #6

What is the output of the terminal commands

uname -a
lsb_release -crid
apt-cache policy
apt-cache policy hdf5-tools

Nico Schlömer (nschloe) said : #7

As of the latest update, I'm getting the expected behavior.

Marking as invalid.