Kinetic prerelease KeyError: "The cache has no package named 'ros-kinetic-dynamic-reconfigure'"

edit

Hi!

I am in the process of releasing a new version (2.0.4) of the package http://wiki.ros.org/toposens. While for melodic everything went through smoothly, I am running into issues when trying to release for kinetic.

The following error occurs during running prerelease.shon my local machine (obtained from http://prerelease.ros.org/kinetic). Same can be found (with the complete console log) in the kinetic Jenkins Job devel ubuntu xenial amd64: http://build.ros.org/view/Kdev/job/Kdev__toposens__ubuntu_xenial_amd64/37/console

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 259, in __getitem__
    return self._weakref[key]
  File "/usr/lib/python3.5/weakref.py", line 131, in __getitem__
    o = self.data[key]()
KeyError: 'ros-kinetic-dynamic-reconfigure'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 263, in __getitem__
    rawpkg = self._cache[key]
KeyError: 'ros-kinetic-dynamic-reconfigure'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 287, in <module>
    main()
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 138, in main
    get_binary_package_versions(apt_cache, debian_pkg_names))
  File "/tmp/ros_buildfarm/ros_buildfarm/common.py", line 144, in get_binary_package_versions
    pkg = apt_cache[debian_pkg_name]
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 265, in __getitem__
    raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named 'ros-kinetic-dynamic-reconfigure'"

The changes are only minor compared to the previously released version (2.0.3), where a few months back the job succeeded. If I run prerelease.sh locally for the previous release (2.0.3), however, I now receive the same KeyError.

This leads me to the question, if there might be something off in the package repo? Or could it be caused by anything on our side?

Maybe anyone has had similar problems?

Any ideas greatly appreciated, Thanks!