Hi Jackie,
regarding "armhf, arm64, and Debian Jessie": Are those now required
target platforms for Kinetic? They are not listed here:
http://www.ros.org/reps/rep-0003.html#kinetic-kame-may-2016-may-2021
Cheers,
Georg.
On 12.04.2016 03:41, Jackie Kay via ros-release wrote:
> *tl;dr*: April 25th is the deadline for desktop-full. Fix your failing
> jobs on the farm or ask us to disable them. Check your repo's status
> on
> http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html
> *
> Release Deadline*
> Today's update is brought to you by the metapackage "desktop-full".
>
> desktop-full consists of the metapackages "desktop", "perception", and
> "simulators".
>
> After desktop-full is released into Kinetic, we can consider ourselves
> in beta for Kinetic.
>
> I would like to establish a deadline of April 25th for releasing
> desktop-full.
>
> Here are the remaining packages that need to be released:
>
> control_msgs
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.control_msgs>
> executive_smach
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.executive_smach>
> gazebo_ros_pkgs
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.gazebo_ros_pkgs>
> image_transport_plugins
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.image_transport_plugins>
> laser_pipeline
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.laser_pipeline>
> perception_pcl
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.perception_pcl>
> robot_state_publisher
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.robot_state_publisher>
> rqt_common_plugins
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.rqt_common_plugins>
> rqt_robot_plugins
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.rqt_robot_plugins>
> stage_ros
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.stage_ros>
> urdf_tutorial
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.urdf_tutorial>
> visualization_tutorials
> <http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.visualization_tutorials>
>
> Maintainers of these packages (this includes me), let's get moving. If
> we released 1 package per day, we would beat the deadline. It's
> important to release early so that we can catch packaging errors on
> the farm.
>
> *armhf, arm64, and Debian Jessie*
> There are a lot of failing binary jobs on the farm right now. I
> believe all of the failures are currently on armhf/arm64 platforms,
> Debian Jessie, or both.
>
> To the maintainers of packages with failing jobs (this also includes me):
>
> If your failing job is due to architectural differences on ARM, please
> either address the problem or ask us to disable the armhf/arm64 build
> for your repo.
>
> If your failing job is due to missing package dependencies in Jessie,
> please look into adding the correct rosdep keys or adding a backport
> for missing dependencies. We do not have a way to blacklist packages
> in Debian only, but luckily these issues are usually easier to
> identify and fix than architecture differences.
>
> And if at some point your package fails on all architectures and you
> don't make efforts to fix it, I will blacklist it entirely because
> those emails are really annoying to receive.
>
> *Blocked Repos Webpage
> *
> An intern at OSRF is working on a web interface for the
> check_blocking_repos.py script announced on this list a few weeks ago.
>
> You can test it here:
> http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html
>
> I encourage you to use it to figure out which packages are blocking
> your package (or if you are blocking someone else's packages).
>
> It's still in review and has a few minor improvements pending. If you
> find issues with it, you can report them on
> https://github.com/ros-infrastructure/ros_buildfarm
>
> Your ROS boss,
>
> Jackie
>
>
> _______________________________________________
> ros-release mailing list
> ros-release@lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
(text/plain)