Adding needed repository Failed!

[Wolfbane8653]

Ran into this again with r3706–>r3711

Debian GNU/Linux 7 \n \l

needed:

apt-get install libapache2-mod-php5 

Tom fixed this in r3712. Thanks again Tom.

[Scott B]

I ended up copying the .fogsettings file from a fresh test FOG install and changing the needed IP addresses. Then I could get past the repository failing issue, but would not update/install any needed software. I found that when manually running the installs I needed to say okay to installing to an untrusted resource. After that everything is up and how it should be.

[tbs]

i am having the same issue on Debian 8.1"jessie" and the installation from trunk (git). It just stalls at " Adding needed repository…"

and noting ever happens

[Scott B]

@Tom-Elliott I’m getting the repository failed issue again. Current FOG is SVN 4266. Does the same if I use GIT also.

[Oleg]

Hello to all,

I have the same problem with the repository. My FOG is behind a proxy but if proxy is enabled or not, the upgrade script is not working. My SVN version is 3735. Tried the upgrade wit git and SVN. Both are failing at this first step.

[Wayne Workman]

@Oleg What Linux distribution?

[Tom Elliott]

http://askubuntu.com/questions/53146/how-do-i-get-add-apt-repository-to-work-through-a-proxy

The variables it’s attempting to use should be capable of passing directly from the ./installfog.sh.

You would change the install part from ./installfog.sh to:

http_proxy=http://<proxy>:<port> ./installfog.sh This is theory, never fully tested though.

[Oleg]

My system is Ubuntu Server 14.04.3.
I cannot fully understand why but this worked for me:

First add the proxy with:
export http_proxy=http://username:password@host:port/
export https_proxy=https://username:password@host:port/

Then put in /etc/sudoers:
Defaults env_keep=“https_proxy”

Last:
start the installfog.sh as root and not as sudo

[Scott B]

@Tom-Elliott said:

http://askubuntu.com/questions/53146/how-do-i-get-add-apt-repository-to-work-through-a-proxy

The variables it’s attempting to use should be capable of passing directly from the ./installfog.sh.

You would change the install part from ./installfog.sh to:

http_proxy=http://<proxy>:<port> ./installfog.sh This is theory, never fully tested though.

Any idea if we are not using a proxy?

[moto_ryan]

@Scott-B

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

[Wayne Workman]

@moto_ryan said:

@Scott-B

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

Future readers, follow @moto_ryan 's specific problem in this thread here: https://forums.fogproject.org/topic/5756/adding-needed-repository-failed-upgrading-from-1-2-0