Project

General

Profile

Actions
Copy link

Bug #1517

open

Prevent installation of gems (and other modules if so) through remote network

Added by Evgeny Novikov over 13 years ago. Updated almost 13 years ago.

Status:
Open
Priority:
High
Assignee:
Evgeny Novikov
Category:
Infrastructure
Start date:
07/14/2011
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

This problem leads to real bugs on QA server, since it doesn't perform any checks because of toolset isn't installed.
As examples, I saw following messages:

cd gems/logging&&  gem install --install-dir /all/qaserver-work/nighttests/inst/2011-07-08-00-00-02/shared/ruby/gem --bindir /all/qaserver-work/nighttests/inst/2011-07-08-00-00-02/shared/ruby/bin --no-rdoc --no-ri pkg/logging*.gem
ERROR:  http://gems.rubyforge.org/ does not appear to be a repository
ERROR:  Error installing pkg/logging-1.4.3.gem:
        logging requires little-plugger (>= 1.1.2, runtime)
make[1]: *** [logging-install] Error 1
make[1]: Leaving directory `/all/qaserver-work/build/master-2011-07-08/shared/ruby'
make: *** [shared/ruby-subdir-install] Error 2

and
cd gems/logging && gem install --install-dir /all/qaserver-work/nighttests/inst/2011-07-14-00-00-03/shared/ruby/gem --bindir /all/qaserver-work/nighttests/inst/2011-07-14-00-00-03/shared/ruby/bin --no-rdoc --no-ri pkg/logging*.gem
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    SocketError: getaddrinfo: Temporary failure in name resolution (http://gems.rubyforge.org/gems/little-plugger-1.1.2.gem)
make[1]: *** [logging-install] Error 1
make[1]: Leaving directory `/all/qaserver-work/build/master-2011-07-14/shared/ruby'
make: *** [shared/ruby-subdir-install] Error 2

Moreover, we should know out all places where installation process uses remote network and exchange them with local ones in some the way.

Actions
Copy link
 #1

Updated by Pavel Shved about 13 years ago

  • Priority changed from High to Normal
Actions
Copy link
 #2

Updated by Evgeny Novikov almost 13 years ago

  • Status changed from New to Open
  • Assignee changed from Pavel Shved to Evgeny Novikov
  • Priority changed from Normal to High

I suggest that the solution is to either include corresponding sources into LDV tools shares or add such the items to the dependency list of LDV tools.

Actions
Copy link

Also available in: Atom PDF