[1] Archiv / MLD 4.x / General / vdr-plugin-markad would break existing dependencies
 

Offline StP

  • Member
  • **
  • Posts: 76
    • View Profile
    • Private Seite mit vielen Bildern über und unter Wasser.
vdr-plugin-markad would break existing dependencies
« on: January 24, 2015, 09:18:10 »
Hallo,

ich habe gerade versucht auf meinem Server das Plugin "vdr-plugin-markad" zu aktivieren.

ich bekomme immer die folgenden Meldungen:
Code: [Select]
Install vdr-plugin-markad
Create a snapshot of '/mnt/root/@root' in '/mnt/root/2015-01-24 09:05'
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-markad:
* vdr (>= 2.1.7.152) * vdr (<= 2.1.7.152-:) *
Installing vdr-plugin-markad (0-21_2.1.7.152) on root.
Downloading http://www.minidvblinux.de/download/4.0.1-64/files/base/vdr-plugin-markad_0-21_2.1.7.152.opk.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break  existing dependencies.

Was kann ich da machen?
Proxmox Server: ASRock Q1900M, 16 GB RAM, 1 x 477GB SSD (boot), 1 x 1,8TB HDD
VDR: VM MLD 5.4 amd64 stable
SAT: OctopusNet 1.1.6
Streaming-Client: Apple TV 4 MrMC, FireTV Kodi

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20445
    • View Profile
    • ClausMuus.de
vdr-plugin-markad would break existing dependencies
« Reply #1 on: January 24, 2015, 09:42:50 »
Hi,

da hilft nur vorab nen komplettes Upgrade zu machen, da das Plugin für die bei Dir installierte VDR Version nicht mehr verfügbar ist.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 5.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 12TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline StP

  • Member
  • **
  • Posts: 76
    • View Profile
    • Private Seite mit vielen Bildern über und unter Wasser.
vdr-plugin-markad would break existing dependencies
« Reply #2 on: January 24, 2015, 09:56:27 »
Hallo,

ist nur leider nichts zum upgraden da.

Code: [Select]
mld>  opkg list-installed |grep "vdr -"
vdr - 2.1.7.152-152

Gruß Stefan
Proxmox Server: ASRock Q1900M, 16 GB RAM, 1 x 477GB SSD (boot), 1 x 1,8TB HDD
VDR: VM MLD 5.4 amd64 stable
SAT: OctopusNet 1.1.6
Streaming-Client: Apple TV 4 MrMC, FireTV Kodi

Offline MegaX

  • Administrator
  • Expert Member
  • ********
  • Posts: 1822
    • View Profile
vdr-plugin-markad would break existing dependencies
« Reply #3 on: January 24, 2015, 11:41:22 »
Hi

mit dem Befehl siehst du auch nur das was auf deiner MLD installiert ist.

Code: [Select]
opkg list-upgradable | grep "vdr -"zeigt dir das was auf dem Server liegt an Upgrades.
Gruß MegaX

Hardware (show / hide)

Offline StP

  • Member
  • **
  • Posts: 76
    • View Profile
    • Private Seite mit vielen Bildern über und unter Wasser.
vdr-plugin-markad would break existing dependencies
« Reply #4 on: January 24, 2015, 11:46:21 »
Hallo,

der Befehl gibt bei mir nichts aus.

Gibt's denn eine neuere Version als "vdr - 2.1.7.152-152"?

Ein "opkg upgrade" macht auch nichts, deshalb denke ich das alles aktuell ist.

Oder mache ich etwas falsch?

Gruß Stefan
Proxmox Server: ASRock Q1900M, 16 GB RAM, 1 x 477GB SSD (boot), 1 x 1,8TB HDD
VDR: VM MLD 5.4 amd64 stable
SAT: OctopusNet 1.1.6
Streaming-Client: Apple TV 4 MrMC, FireTV Kodi

Offline michi72

  • Newbie
  • *
  • Posts: 21
    • View Profile
vdr-plugin-markad would break existing dependencies
« Reply #5 on: January 24, 2015, 14:58:51 »
Hallo,

ich hänge mich hier mal mit rein. Habe leider genau die gleichen Probleme, trotz vollem opkg upgrade, da kommt nämlich folgendes:
Code: [Select]
vdr> opkg upgrade
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Assuming locally installed package vdr (2.1.6.141-151) is up to date.
Upgrading vdr-plugin-opkg from 0.1.0-22_2.1.6.141 to 0.1.0-22_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-setup from 0.3.1-24_2.1.6.141 to 0.3.1-24_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-streamdev-server from 2014.12.23-8_2.1.6.141 to 2014.12.23-8_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-epgsearch from 2014.12.27-11_2.1.6.141 to 2014.12.27-11_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-vnsiserver6 from 2015.01.17-0_2.1.6.141 to 2015.01.18-0_2.1.6.141 on root.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-markad from 0-21_2.1.6.141 to 0-21_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-live from 2013.05.04-4_2.1.6.141 to 2013.05.04-4_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-systeminfo from 0.1.3-7_2.1.6.141 to 0.1.3-7_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-skincurses from 2.1.1-4_2.1.6.141 to 2.1.1-4_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-dummydevice from 1.0.2-3_2.1.6.141 to 1.0.2-3_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-fritzbox from 1.5.3-2_2.1.6.141 to 1.5.3-2_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-osdteletext from 2014.01.12-2_2.1.6.141 to 2014.01.12-2_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-svdrpservice from 1.0.0-5_2.1.6.141 to 1.0.0-5_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-undelete from 2014.06.08-1_2.1.6.141 to 2014.06.08-1_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-burn from 0.2.2-2_2.1.6.141 to 0.2.2-2_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-smarttvweb from 2014.10.04-2_2.1.6.141 to 2015.01.18-2_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-control from 0.0.2a-4_2.1.6.141 to 0.0.2a-4_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Upgrading vdr-plugin-svdrposd from 1.0.0-4_2.1.6.141 to 1.0.0-4_2.1.7.152 on root.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
Not selecting vdr 2.1.6.141 as installing it would break existing dependencies.
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-opkg:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-setup:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-streamdev-server:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-epgsearch:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-vnsiserver6:
 *      vdr (>= 2.1.6.141) *    vdr (<= 2.1.6.141-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-markad:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-live:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-systeminfo:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-skincurses:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-dummydevice:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-fritzbox:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-osdteletext:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-svdrpservice:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-undelete:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-burn:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-smarttvweb:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-control:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for vdr-plugin-svdrposd:
 *      vdr (>= 2.1.7.152) *    vdr (<= 2.1.7.152-:) *


Und:


Code: [Select]
vdr> opkg upgrade vdr
Create a snapshot of '/mnt/root/@root' in '/mnt/root/2015-01-24 14:53'
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
vdr> opkg list-upgradable | grep "vdr -"
vdr> opkg list-upgradable
Not selecting vdr 2.1.7.152 as installing it would break existing dependencies.
vdr-plugin-svdrposd - 1.0.0-4_2.1.6.141 - 1.0.0-4_2.1.7.152
vdr-plugin-control - 0.0.2a-4_2.1.6.141 - 0.0.2a-4_2.1.7.152
vdr-plugin-smarttvweb - 2014.10.04-2_2.1.6.141 - 2015.01.18-2_2.1.7.152
vdr-plugin-burn - 0.2.2-2_2.1.6.141 - 0.2.2-2_2.1.7.152
vdr-plugin-undelete - 2014.06.08-1_2.1.6.141 - 2014.06.08-1_2.1.7.152
vdr-plugin-svdrpservice - 1.0.0-5_2.1.6.141 - 1.0.0-5_2.1.7.152
vdr-plugin-osdteletext - 2014.01.12-2_2.1.6.141 - 2014.01.12-2_2.1.7.152
vdr-plugin-fritzbox - 1.5.3-2_2.1.6.141 - 1.5.3-2_2.1.7.152
vdr-plugin-dummydevice - 1.0.2-3_2.1.6.141 - 1.0.2-3_2.1.7.152
vdr-plugin-skincurses - 2.1.1-4_2.1.6.141 - 2.1.1-4_2.1.7.152
vdr-plugin-systeminfo - 0.1.3-7_2.1.6.141 - 0.1.3-7_2.1.7.152
vdr-plugin-live - 2013.05.04-4_2.1.6.141 - 2013.05.04-4_2.1.7.152
vdr-plugin-markad - 0-21_2.1.6.141 - 0-21_2.1.7.152
vdr-plugin-vnsiserver6 - 2015.01.17-0_2.1.6.141 - 2015.01.18-0_2.1.6.141
vdr-plugin-epgsearch - 2014.12.27-11_2.1.6.141 - 2014.12.27-11_2.1.7.152
vdr-plugin-streamdev-server - 2014.12.23-8_2.1.6.141 - 2014.12.23-8_2.1.7.152
vdr-plugin-setup - 0.3.1-24_2.1.6.141 - 0.3.1-24_2.1.7.152
vdr-plugin-opkg - 0.1.0-22_2.1.6.141 - 0.1.0-22_2.1.7.152


Ehrlich gesagt habe ich etwas Muffensausen, einfach ein opkg --nodeps oder --force-depends zu machen ... Ich weiß auch nicht weiter.

Was nun?

Gruß
Michi
Server: Atom-ITX Board ION, 4xAtom 1,6 GHz, 4GB RAM, 40GB HDD, per NFS eingebunden NAS per Netzwerk, Board=Zotac ION ITX-F mit Intel Atom-CPU und ION-Nvidia Grafik, PCIe=DigitalDevices Cine S2 mit vierfach Tuner, ngene Treiber
Clients: alle auf Android mit XBMC (CS918 Boxen mit Wasser-Firmware)

Offline StP

  • Member
  • **
  • Posts: 76
    • View Profile
    • Private Seite mit vielen Bildern über und unter Wasser.
vdr-plugin-markad would break existing dependencies
« Reply #6 on: January 24, 2015, 17:06:29 »
Hallo,

hab gerade nochmal die Paketliste aktualisiert (zum x-ten mal heute).
Danach konnte ich das vdr-plugin-markad installieren.

Gruß Stefan
Proxmox Server: ASRock Q1900M, 16 GB RAM, 1 x 477GB SSD (boot), 1 x 1,8TB HDD
VDR: VM MLD 5.4 amd64 stable
SAT: OctopusNet 1.1.6
Streaming-Client: Apple TV 4 MrMC, FireTV Kodi

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20445
    • View Profile
    • ClausMuus.de
vdr-plugin-markad would break existing dependencies
« Reply #7 on: January 24, 2015, 22:21:11 »
Hi Michi,

das vnsiserver6 Paket gibt's nicht mehr. Das gab's nur nen paar Tage, dann habe ich das in vnsiserver umbenannt, da es sowohl das 5'er als auch das 6'er vereint.
Deinstalliere man das vdr-plugin-vnsiserver6, mach dann das Upgrade und anschließend installiere das vdr-plugin-vnsiserver. Dann sollte es gehen.
Allerdings sollte das upgrade inzwischen auch direkt funktionieren.

Claus
« Last Edit: January 24, 2015, 22:23:02 by clausmuus »
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 5.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 12TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline michi72

  • Newbie
  • *
  • Posts: 21
    • View Profile
vdr-plugin-markad would break existing dependencies
« Reply #8 on: January 25, 2015, 00:16:32 »
Hallo Claus,

leider nein. Es funktioniert leider immer noch nicht. Und ein --force-depends bzw. --nodeps installiert zwar ein wenig weiter, aber dann kann ich kein plugin mehr installieren. Mist. OK, ich habe jetzt ein Backup vom 20.01. wieder eingespielt und warte nun ein wenig mit opkg upgrade. Vielleicht bin ich ja doch nicht der Einzige mit diesen Problemen.

Gruß
Michi
Server: Atom-ITX Board ION, 4xAtom 1,6 GHz, 4GB RAM, 40GB HDD, per NFS eingebunden NAS per Netzwerk, Board=Zotac ION ITX-F mit Intel Atom-CPU und ION-Nvidia Grafik, PCIe=DigitalDevices Cine S2 mit vierfach Tuner, ngene Treiber
Clients: alle auf Android mit XBMC (CS918 Boxen mit Wasser-Firmware)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20445
    • View Profile
    • ClausMuus.de
vdr-plugin-markad would break existing dependencies
« Reply #9 on: January 29, 2015, 13:12:33 »
Hi,

gestern hab ich nen kleinen opkg fix reaktiviert, der versehentlich raus geflogen war. Nun müsste folgendes funktionieren:
Code: [Select]
opkg update
opkg upgrade opkg
opkg --force-depends upgrade
opkg update
Anschließend sollten alle Pakete aktuell sein, und auch ein hinzufügen weiterer Pakete sollte gehen.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 5.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 12TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline michi72

  • Newbie
  • *
  • Posts: 21
    • View Profile
vdr-plugin-markad would break existing dependencies
« Reply #10 on: January 29, 2015, 14:34:12 »
Hallo Claus,

wow, Danke! Alles geht, alles aktualisiert. Und bis jetzt läuft noch alles  ;)
Eine tolle Distri mit tollem Support, großes Danke nach S..dorf!

Gruß
Michi
Server: Atom-ITX Board ION, 4xAtom 1,6 GHz, 4GB RAM, 40GB HDD, per NFS eingebunden NAS per Netzwerk, Board=Zotac ION ITX-F mit Intel Atom-CPU und ION-Nvidia Grafik, PCIe=DigitalDevices Cine S2 mit vierfach Tuner, ngene Treiber
Clients: alle auf Android mit XBMC (CS918 Boxen mit Wasser-Firmware)

[1] Archiv / MLD 4.x / General / vdr-plugin-markad would break existing dependencies
 



Users Online Users Online

0 Members and 1 Guest are viewing this topic.