20:24 <Pete90> When using a proxy server on the BB Blue do I configure my own port number or is there a specific one I should use? The command curl on a github .yaml link returns the error "curl: (5) Unsupported proxy syntax in 'https://[user:password@]proxy_server:port/'". And I want to setup the proxy syntax (?) to work I guess.

20:24 <zmatt> ehh

20:25 <Pete90> Doesn't sound like it'll be a simple fix :')

20:25 <zmatt> more like it's not really clear what you're doign

20:25 <zmatt> *doing

20:26 <zmatt> didn't you have normal internet access previously? why suddenly the need for a proxy?

20:27 <Pete90> So still trying to install ros, switched to Ubuntu 20.04 because the install has support for armhf, on the final step it fails with a long error message, one of the proposed "solutions" is making sure you can curl the the first link. I can't it returns that error.

20:27 <Pete90> Switched to ubuntu because the rosbridge didn't have a build method to actually host the website and I thought I might as well try the other method

20:28 <zmatt> "the rosbridge didn't have a build method to actually host the website" ... nothing in that sentence makes sense

20:28 <zmatt> also what instructions are you following?

20:29 <Pete90> I am aware that my speech is all over the place, what I mean is the rosbridge doesnt't have clear instructions on how to go further, I don't really know how to phrase it

20:30 <Pete90> wiki.ros.org/noetic/Installation/Ubuntu this guide, fails on the last instruction

20:30 <zmatt> were you able to build it?

20:30 <zmatt> rosbridge?

20:31 <Pete90> yes techinally, you helped with the catkin environment but the command to "run it" (I guess) didn't exist

20:32 <zmatt> http://wiki.ros.org/rosbridge_suite/Tutorials/RunningRosbridge#Running_Rosbridge

20:32 <Pete90> This command "roslaunch rosbridge_server rosbridge_websocket.launch" just throws all kinds of errors with little ways to fix them

20:32 <zmatt> (as usual ignore the "source /opt/ros" thing)

20:33 <zmatt> ... namely being?

20:35 <Pete90> I can't remember the errors it was at 2 this morning, I've already switched(I did save the Debian image) and I'm trying to get a form of ros running on ubuntu

20:35 <zmatt> as for your ubuntu issue... ubuntu is not officially supported on the beaglebone and rarely used/tested hence not recommended unless you're good at solving problems yourself. e.g. if something works fine on debian and not ubuntu, I probably can't really help you with it

20:36 <zmatt> are you actually trying to use a proxy? what did you configure where to set this up?

20:36 <rcn-ee> Try this base for ros.. https://rcn-ee.net/rootfs/ubuntu-armhf/2022-06-17/

20:36 <rcn-ee> It gets random feedback from users on usability..

20:37 <rcn-ee> (daily build)

20:38 <Pete90> rcn-ee: thanks I am using an image from May (2022-05-22), would you recommend changing from that?

20:38 <zmatt> rcn-ee: debian has native ros packages though

20:39 <Pete90> zmatt: I initally added lines to /etc/environment but I have since removed them

20:40 <Pete90> @zmatt

20:40 <Pete90> These lines https://pastebin.com/eBBeBjvy, unsure about the port though

20:42 <zmatt> ???? that is indeed syntactically invalid (the [] in the syntax description just indicate an optional part, not literal characters) ... but why are you trying to go through a proxy running on the same machine?

20:42 <Pete90> Its one of the solutions they suggested, it didn't work for me so I removed the lines

20:43 <zmatt> solutions for what? suggested by whom? where?

20:44 <Pete90> The first issue for "rosdep init" not working having an error of website may be down, the solution is here https://answers.ros.org/question/54150/rosdep-initialization-error/

20:44 <zmatt> that person explicitly said they were behind a proxy

20:45 <Pete90> It first didn't work without the edit on /etc/environment , I then added the lines and it still didn't work, removed them and then it worked

20:45 <zmatt> (i.e. they do not have direct internet access)

20:46 <zmatt> the error sounds like you just didn't have internet access when you first tried it (i.e. it wasn't connected to wifi)

20:48 <Pete90> as far as I know there was internet access, it could successfully ping websites

20:49 <zmatt> also, try to work on how to present your questions... when you're trying to get help with something... present the actual goal and the original problem, i.e. "I'm giving installation of ros on ubuntu 20.04 (2022-05-22) a try, but "rosdep init" is giving me this error: "..."

20:50 <zmatt> your opening question today was a classic example of https://xyproblem.info/

20:53 <Pete90> Okay, fair, my presenting of the problem wasn't sufficient, I'll work on it. Do I need to give a full description of the problem over again?

20:54 <zmatt> is there still a problem? you just said you removed the lines "and then it worked" ... unless the "it" is something else

20:55 <zmatt> if you're still giving a rosdep error, pastebin the command and the error it produced

20:55 <zmatt> or better yet, go back to debian since it seems to me you were further along there than you are here :P

21:01 <Pete90> Yes there is still a problem, the previous problem of "rosdep init" was present this morning and after trying numerous solutions of other people at some point it worked. The problem now is updating rosdep, the command "rosdep update" return the following long error message https://pastebin.com/ctuBcjsN , I only found one other person experiencing

21:01 <Pete90> the same error, with no solution posted. One person suggested trying to curl the first link to see if it works otherwise the problem lays there. Curling the link presents this error: https://pastebin.com/W7hMyqBt .

21:03 <zmatt> since there's clearly no port "port" in the url shown I'm guessing there's still some nonsensical proxy config somewhere

21:03 <Pete90> Technically ros was working on Debian, however I had no way of working with it since there were no guides or explanations on working with upstream distributions and integrating other packages. Thus I want to give it a try on Ubuntu as porting the drivers may be a problem later but the main objective of my project is working with ROS to build a map

21:03 <Pete90> of the environment

21:04 <Pete90> Could be yeah, like I said I'm not even sure at which point it started working, but it was after cleaning /etc/environment

21:05 <zmatt> you may need to reboot after cleaning your nonsense out of /etc/environment

21:06 <zmatt> and ROS mostly seems its own environment (own build tool, own installation tool, etc) ... so I really don't think there should be significant differences between debian or ubuntu after initial installation

21:07 <zmatt> but that's up to you

21:09 <Pete90> I'll try it again, like I said I do still have the image, but it seemed like a mission to get operable as there isn't much support for upstream ros especially from their forums

21:09 <Pete90> They do complain about it alot though

21:13 <zmatt> they're free to maintain their own packages for debian, but they seem to have neglected to do so :P

21:14 <zmatt> ubuntu is just a weird choice for this application, it's primarily a desktop OS

21:14 <zmatt> not an embedded one

21:15 <Pete90> Neglected is the right word yeah

21:16 <Pete90> At the moment I'm behind on my project so I want to get a form of mapping working, I have my LiDAR and I have my webcam but nothing to use it with at the moment

21:18 <rcn-ee> Last I looked.. ros on debian, was a random snapshot.. ros only supports a you build src for debian.. with Ubuntu, every release has a matching Ubuntu version...

21:18 <zmatt> so did reboot fix the lingering issues caused by your proxy nonsense?

21:19 <Pete90> zmatt its a bit slow but it has it's first hit, seems like it definitely fixed most of the problem, thanks for that

21:21 <Pete90> just finished and seems like its working, I'll try a tutorial now and check

21:24 <Pete90> There are full install guides for Debian, just not supported for armhf chips

21:26 <zmatt> why would architecture matter?

21:28 <Pete90> BB Blue is and armhf chip no? Does that not actually matter when installing programs?

21:28 <zmatt> in some rare cases, but usually not no

21:29 <Pete90> mmmm, I thought it would have more of an impact

21:29 <zmatt> like, binary packages are of course architecture-specific, but armhf is relevant enough that typically if people provide binary packages for x86_64 they'll also have armhf packages

21:30 <zmatt> this is certainly true for debian native packages (except those rare packages that are intrinsically architecture-specific)

21:31 <Pete90> Like theres no binary package of noetic for debian 10 on armhf http://wiki.ros.org/noetic/Installation and building from source failed last time, kind of why I've been jumping around otherwise I would ahve used the iot images provided by beaglebone

21:32 <zmatt> yeah really weird, especially since they do have armhf packages on ubuntu

21:32 <zmatt> pure laziness I guess

21:32 <zmatt> they just don't care

21:33 <Pete90> Wouldn't surprise me, still weird that building from source kept failing, maybe I'll revisit it during my holiday but for now I just need to make some progress

21:35 <zmatt> what originally failed anyway? like, I remember you running out of memory while trying to compile cmake for some reason, but there shouldn't be a reason to compile cmake from source anyway

21:36 <zmatt> btw their debian repo metadata does actually list armhf: http://packages.ros.org/ros/ubuntu/dists/buster/Release

21:37 <Pete90> I think it was in building the workspace, somewhere there it just didn't want to work anymore, came here and asked and you guys said to use Debian 11 so I started there :')

21:39 <zmatt> I'm pretty sure I didn't "say to use Debian 11" ... at most I said that debian 11 included a newer version of the native ros packages, but that's obviously irrelevant for the topic of building from source