On Mon, Sep 8, 2014 at 3:45 PM, Mike Purvis <mpurvis@clearpathrobotics.com> wrote:
Might be another argument for someone to try building up a unofficial farm of Precise/Indigo debs. Do we have a sense how many of the 1000 or so released Indigo packages have an actual problem with the CMake/Boost versions which ship with Precise?

How ugly of a hack would it be to use the Saucy bloom branches to build Precise debs? How much time would it take to find out?

There is no way to do this that I know of, you would need to re-bloom all packages for precise. This is because the rosdep key -> ubuntu key will have changed for several of the keys. For example: PCL, OpenCV, urdfdom_headers, urdfdom, sdformat, gazebo, boost, ogre, just to name the ones off the top of my head. My guess is that the effort involved is considerable.

Another strategy would be to use a chroot method for trusty. This was used back when most people were still on precise but wanted to test indigo stuff. I'm not sure travis would allow this or condone this though. I'm just not sure.
 

On 8 September 2014 17:46, William Woodall <william@osrfoundation.org> wrote:
On Mon, Sep 8, 2014 at 2:43 PM, Dave Coleman <davetcoleman@gmail.com> wrote:
I'm not sure if this is the best mailing list for this question, but has anyone found a work around to use Travis CI with ROS Indigo? Travis only runs Ubuntu Precise, confirmed by

Nope, I just use hydro for now. There really isn't a good option if you want to use travis until travis supports Trusty. You could build what you need from source, but that probably would take too long.
 

So it lacks the ROS debians to build, for example, MoveIt's Indigo branch. Its frustrating to have all pull requests for Indigo fail i.e.
https://github.com/ros-planning/moveit_ros/pull/490

Thanks!

dave coleman


On Mon, Sep 8, 2014 at 6:00 AM, <ros-release-request@code.ros.org> wrote:
Send ros-release mailing list submissions to
        ros-release@code.ros.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ros.org/mailman/listinfo/ros-release
or, via email, send a message with subject or body 'help' to
        ros-release-request@code.ros.org

You can reach the person managing the list at
        ros-release-owner@code.ros.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ros-release digest..."


Today's Topics:

   1. Re: dropping unmaintained Ubuntu distributions ? (Tully Foote)


----------------------------------------------------------------------

Message: 1
Date: Sun, 7 Sep 2014 13:58:45 -0700
From: Tully Foote <tfoote@osrfoundation.org>
To: The ROS release mailing list <ros-release@code.ros.org>
Subject: Re: [ros-release] dropping unmaintained Ubuntu distributions
        ?
Message-ID:
        <CAM7qi7U9NcH6-drP82rPTU=Rp8C=jbwcLMe4u7Yy5EsCyx9-pA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Yes, we do plan to spin down the builds of EOL'd Ubuntu platforms. we have
not done this yet as we do not have that level of configuration built into
the buildfarm. So we'll need to do some development to support that.

With respect to libgphoto2 this isn't an EOL issue. It appears that in
Saucy only libgphoto2-6-dev was released to replace libgphoto2-2-dev but
the decision was reverted in trusty. So to fix this we just need to update
the rosdep rule.


Link online:
http://packages.ubuntu.com/search?keywords=libgphoto2-6-dev&searchon=names

>From saucy/amd64 Packages file:
Package: libgphoto2-6-dev
Priority: optional
Section: libdevel
Installed-Size: 11550
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian PhotoTools Maintainers <
pkg-phototools-devel@lists.alioth.debian.org>
Architecture: amd64
Source: libgphoto2
Version: 2.5.2-0ubuntu5
Replaces: libgphoto2-2-dev
Depends: libgphoto2-6 (= 2.5.2-0ubuntu5), libexif-dev, libusb-1.0-0-dev,
libc-dev, pkg-config
Conflicts: libgphoto2-2-dev
Filename:
pool/main/libg/libgphoto2/libgphoto2-6-dev_2.5.2-0ubuntu5_amd64.deb
Size: 3340498
MD5sum: d57c9dc5d1d22c38edeec64902755179
SHA1: 6f1ad45da2c535f799268e13f9b7f81fcc6b151f
SHA256: 9974beae6a435a5678e24d8e02abfefe36097e8db9c009920ee5cd783f68f019
Description: gphoto2 digital camera library (development files)
Homepage: http://www.gphoto.org/proj/libgphoto2/
Description-md5: 09f6d0ae3f118a398b90fb84845618e0
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Supported: 9m



Tully


On Sun, Sep 7, 2014 at 3:01 AM, Vincent Rabaud <vincent.rabaud@gmail.com>
wrote:

> Hi all,
>
> just a thought: we've had problems with Quantal and Oneiric builds in the
> past. And I see the same thing now on Saucy (
> http://jenkins.ros.org/view/IbinS32/job/ros-indigo-rospilot_binarydeb_saucy_i386/
> simply because for some reason,
> http://packages.ubuntu.com/lucid/libgphoto2-2-dev was not released in
> Saucy).
> Indigo is also an LTS for 5 years and I doubt we'll keep maintaining 10
> Ubuntu distributions.
>
> Wouldn't completing REP003 with dropping an Ubuntu distribution once it's
> out of life a good thing ? Do we have stats on package downloads to back
> that up ? Docs for what to drop here: https://wiki.ubuntu.com/Releases
> That would also obviously make bloom and builds faster (or cheaper).
>
> Thoughts ?
>
> _______________________________________________
> ros-release mailing list
> ros-release@code.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20140907/953fc4be/attachment-0001.html>

------------------------------

_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release


End of ros-release Digest, Vol 35, Issue 3
******************************************


_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release




--
William Woodall
ROS Development Team

_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release



_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release




--
William Woodall
ROS Development Team
william@osrfoundation.org
http://wjwwood.io/