[ilgello]

(19th Jul, 2014 08:05 PM)mk01 Wrote:  

(11th Jul, 2014 06:11 PM)Fabio72 Wrote:  I'm trying a dist-upgrade but I'm getting warnings about mandatory package deletions.
My current version should be 1RC2 Gotham
Am I upt to date?
Have I to wait before doing dist-upgrade?

@Fabio

without trying to force my truth there (but it is the truth in that case ), what is the concern/problem which makes you trying dist-upgrade?

purpose of dist-upgrade is for live distribution upgrades (for instance process of going from wheezy to jessie without reimaging). and because of that dist-upgrade is not honouring standard rules as defined for SAFE apt-get operations (for instance "upgrade").

dist-upgrade is allowed to remove even by USER installed packages and if it considers others as priority - but with one specific purpose => allow distro generation change what can mean completely different deb package structure.

with this ability it is often misused to avoid typing two commands instead of one. for security reasons APT will not UPGRADE package if its dependencies changed. imagine you running auto updates and you installed program putting "hello world" on your screen day before. second day someone change that package and put a trojan horse as dependency. the third day you are a victim of crime (because APT auto installed the trojan horse as was requested with the new version of "hello world" package. would be bad, wasn't it?

now back to XBian. as we were developing from A5 -> RC2 user and our expectations changed over time. also, upgrading from Frodo to Gotham means other support programs - this time because XBMC developers decided that way. for APT that means that someone is trying to hijack your installation. that's why it will list those packages as "on hold"

there are two ways how to install such packages. one is misuse of dist-upgrade. but dist-upgrade will HONOR original Debian packages over any other installed. In Xbian's case it means removing UPSTART thus making you system to remove all other XBian packages because we rely on it. Don't go this way. (just for info this particular conflict is open as bug at Debian for over 1.5y and by many many users). Also we tried to put this into EACH bigger upgrade howto (B1, B2 and so on). There I just try to say that don't worry it is not your install wrong, it is by design (unfortunately).

second option to install the packages (if you prefer command line) is just simply telling APT to install them. That means

Code:

apt-get install pkg1 pkg2 pkg3 pkg4

where pkgX is name of package which APT lists as on hold during operations.

And because we always wish for seamless and easy user experience we designed the upgrade module of xbian-config (within XBMC or SSH) to directly list those packages for you to check it for upgrade and confirmation with OK. Nothing less or more is asked.

At the end of long story: I'm not encouraging you to forget about dist-upgrade. I'm trying to be sure you understand the risks involved there. This is also reason why some of the XBian packages are flagged as MANDATORY. If they would not, your Installation would be useless few minutes after you hit Enter on dist-upgrade.

For more info check "man apt-get" (only if interested, otherwise is quite boring ).
If you follow this best-practices and still will hit strange things, don't hesitate to open ISSUE report at github to get it solved ASAP.

mk

---

(14th Jul, 2014 09:58 AM)ilgello Wrote:  Hi guys, big linux noob here.

I have updated to Gotham and now I cannot connect to my rutorrent anymore "502 Bad Gateway", rtorrent is runing in background so are nginx and php.

There was also a php lib update I did together with Gotham and a bunch of other updates, I am kind of lost at this point, I tried to reinstall rtorrent using the script I have used previously but nothing changes...

Can you help me out ? I am happy to give you more info but I wouldn't what is relevant at this point...

I'm just shooting blind but I have strange feeling it could be with new XBMC allocating different TCP port for ES component and by accident that is the one used before by some of the downloader programs .

Try to check list of ISSUES reported at github.

Thanks for your reply, I think it's not an XBMC related issue, I have reverted the updates using BTFRS and I am now upgrading every package one by one so I can isolate the issue.