Dear Dan,

this is very clear to me.. this way fix the issue .. but i can suggest you and the stuff to update the Doc pages..

--> http://mediaproxy.ag-projects.com/download/


The right way for configure is to add on the source list of apt the follow lines.. where you need to substitude "jessie" with the debian release..


deb http://ftp.debian.org/debian/ jessie-backports main
deb-src http://ftp.debian.org/debian/ jessie-backports main

deb http://ag-projects.com/debian jessie main
deb-src http://ag-projects.com/debian jessie main


Thanks a lot for your support.

Regards



Il 24/07/18 13:27, Dan Pascu ha scritto:
Your problem is that you mix debian 8.11 (jessie) with ag-projects' debian 
unstable repositories.

Change your ag-projects repositories to read 'jessie main' instead of 'unstable 
main', rerun apt-get update and it should work.

You might also consider adding the jessie-backports repository:

deb http://ftp.it.debian.org/debian/ jessie-bakcports main
deb-src http://ftp.it.debian.org/debian/ jessie-bakcports main

Some of our software needs newer versions of some packages that are only 
available in the jessie-backports repository (not sure if mediaproxy is one of 
them, but others like blink or sipsimple are).

On 24 Jul 2018, at 13:48, Simone Sestini wrote:

Hi,

only the standard and official repository here..

-------
deb http://ftp.it.debian.org/debian/ jessie main
deb-src http://ftp.it.debian.org/debian/ jessie main

deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main

# jessie-updates, previously known as 'volatile'
deb http://ftp.it.debian.org/debian/ jessie-updates main
deb-src http://ftp.it.debian.org/debian/ jessie-updates main

# AG Projects software
deb http://ag-projects.com/debian unstable main
deb-src http://ag-projects.com/debian unstable main

-------

and here the output for the  policy you requested.

test-rtp:~# apt-cache policy iptables mediaproxy-common
iptables:
   Installato: 1.4.21-2+b1
   Candidato:  1.4.21-2+b1
   Tabella versione:
  *** 1.4.21-2+b1 0
         500 http://ftp.it.debian.org/debian/ jessie/main amd64 Packages
         100 /var/lib/dpkg/status
mediaproxy-common:
   Installato: (nessuno)
   Candidato:  2.6.6
   Tabella versione:
      2.6.6 0
         500 http://ag-projects.com/debian/ unstable/main amd64 Packages


Thanks


Il 24/07/18 12:32, Dan Pascu ha scritto:
Please paste apt's sources list (you can delete private repositories if you 
have any, I only want to see debian's and ag-projects' repositories). 
Alternatively you can paste the output from

apt-cache policy iptables mediaproxy-common

On 24 Jul 2018, at 12:20, Simone Sestini wrote:

Dear list..

I'm trying to install mediaproxy software on Debian 8.11.

I'm looking around for a solution.. because i'm receiving
test-rtp:/# apt-get install mediaproxy-common  mediaproxy-relay 
mediaproxy-web-sessions
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Alcuni pacchetti non possono essere installati. Questo può voler dire
che è stata richiesta una situazione impossibile oppure, se si sta
usando una distribuzione in sviluppo, che alcuni pacchetti richiesti
non sono ancora stati creati o sono stati rimossi da Incoming.
Le seguenti informazioni possono aiutare a risolvere la situazione:

I seguenti pacchetti hanno dipendenze non soddisfatte:
  mediaproxy-common : Dipende: libiptc0 ma non è installabile
E: Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati.
test-rtp:/#

Praticaly mediaproxy-common depend of libiptc0 but it's not found on debian.

The only lib exist are
lrwxrwxrwx 1 root root   16 nov  8  2014 /lib/libiptc.so -> libiptc.so.0.0.0
lrwxrwxrwx 1 root root   16 nov  8  2014 /lib/libiptc.so.0 -> libiptc.so.0.0.0
-rw-r--r-- 1 root root 5816 nov  8  2014 /lib/libiptc.so.0.0.0

and i tried to add libiptc0 links too but it dosn't fix..

lrwxrwxrwx 1 root root   16 lug 23 12:49 /lib/libiptc0.so -> libiptc.so.0.0.0
lrwxrwxrwx 1 root root   16 lug 23 12:50 /lib/libiptc0.so.0 -> libiptc.so.0.0.0

Any idea ?

Regards
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Dan





_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

--
Dan





_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to