Adding needed repository....Failed! - upgrading from 1.2.0

[moto_ryan]

Hello,

I am very excited to be upgraded to the builds, from 1.2 - but I am having the same error. It seems the thread died with a solution if you ar
e behind a proxy, but both Scott and I are not. First, I was aiming for using btsync, but I am running into a permissions error - appears to be btsync itself, something in the config file I found here: https://github.com/tuxpoldo/btsync-deb/issues/182 . I am going to circle back to that error. For now, I used the wget and extracted the tarball. The installer found all of my old settings, but I am stuck adding a repository.

I am running FOG 1.2 on a Debian machine. I am stuck at

Adding needed repository…Failed!
System: Host:XXXXX Kernel: 3.16.0-4-amd64 x86_64 (64 bit) Desktop: MATE 1.10.0 Distro: LinuxMint 2 betsy

[EAHarvey]

What version of Linux are you running the server on?

[moto_ryan]

Thank you for the response. I am running LMDE Betsy2.
This is the Linux Mint, Debian fork. It is not Ubuntu based and does NOT support PPA. If the installer is adding a PPA respository, I could see that being the issue.

If I only knew what repository, I could add it myself. I looked through the installfog.sh as well as /lib/ but I am not a programmer.

[moto_ryan]

Just want to clarify that I have received the installer, it is checking my current settings and ready to install, then when adding the needed repository, it fails. Everything else on this machine and with FOG 1.2.0 is working brilliantly. I would like to update to the builds to start testing UEFI and MDADM support. No, I am not behind a proxy.

Are you sure you wish to continue (Y/N) y

Installation Started…

Installing required packages, if this fails
make sure you have an active internet connection.

• Adding needed repository…Failed!

[Wayne Workman]

@moto_ryan Comment out the exit code for that line in the script code - for debian.

trunk/lib/ubuntu/config.sh

(or is there a directory in 1.2.0 just for Debian, I have no clue)

Search for “exit 0” where the failure code is and just put a hashmark in front of that line, like this:

#exit 0

Be sure to comment out the correct exit line.

This will allow that part to fail, but the script to continue.

Might I ask why you’re using an off-the-beaten-trail version of Linux?