28th Jun, 2013, 06:53 PM
28th Jun, 2013, 06:53 PM
28th Jun, 2013, 07:04 PM
28th Jun, 2013, 07:12 PM
(28th Jun, 2013 06:43 PM)rikardo1979 Wrote: [ -> ]also this was an open testNo that is not acceptable. The alphas were so much better than this beta that everyone had a reasonable expectation that the beta would be even better. Instead this beta is much worse than the alphas. Really Rikardo, no point dodging the issue. These things happens but don't tell people their expectations for excellence were unfounded. To some people, 'bleeding edge' means the latest tested and mostly reliable software. A good example is Firefox Aurora. It's alphaware but I've been using it since Mozilla switched to rapid releases and rarely have I experience any issues. I realise that XBian doesn't have the resources of Mozilla but not utilising the users who are willing to help before a "release" is silly.as beta means that it is still in testing stage and all should expect that something may go wrong, thats why it is Beta 1.0
(28th Jun, 2013 07:04 PM)Smultie Wrote: [ -> ]If upgrading causes that many problems, then just don't offer the option to upgrade imho.+1
Full respect to the XBian people. I've been absent for quite a while so I can't really expect to whine too much without putting in the effort to help. However all humanity is imperfect. This was a bad release and rightfully has been pulled. Let's not deny it and move on.
I'm willing to do clean installs of 1A5 and then upgrade to beta if that is the testing scenario that needs more work.
28th Jun, 2013, 07:36 PM
@raspberry_pd
nice reading for you, especially
full article
http://en.m.wikipedia.org/wiki/Software_versioning
And as you can see we do not saying that there are no problems an always advice to make a backup before upgrade procedure.
Also there were a major changes between alpha and beta so we have to tested this way as there is no way do it internally as we do not have that many pre-release testers in team
As usual we all do the best to help all and trying to solve the issues asap.
Still,keep in mind, none of us do this as full time job and none of us take any pay. All is done in a free time of each of us.
All need a time.
-thx-
nice reading for you, especially
Quote:
Pre-release versions
In conjunction with the various versioning schemes listed above, a system for denoting pre-release versions is generally used, as the program makes its way through the stages of the software release life cycle.
Programs that are in an early stage are often called "alpha" software, after the first letter in the Greek alphabet. After they mature but are not yet ready for release, they may be called "beta" software, after the second letter in the Greek alphabet. Generally alpha software is tested by developers only, while beta software is distributed for community testing.
full article
http://en.m.wikipedia.org/wiki/Software_versioning
And as you can see we do not saying that there are no problems an always advice to make a backup before upgrade procedure.
Also there were a major changes between alpha and beta so we have to tested this way as there is no way do it internally as we do not have that many pre-release testers in team
As usual we all do the best to help all and trying to solve the issues asap.
Still,keep in mind, none of us do this as full time job and none of us take any pay. All is done in a free time of each of us.
All need a time.
-thx-
28th Jun, 2013, 09:26 PM
28th Jun, 2013, 09:37 PM
28th Jun, 2013, 10:07 PM
28th Jun, 2013, 11:24 PM
(28th Jun, 2013 07:36 PM)rikardo1979 Wrote: [ -> ]@raspberry_pd
nice reading for you, especially
Quote:
Pre-release versions
In conjunction with the various versioning schemes listed above, a system for denoting pre-release versions is generally used, as the program makes its way through the stages of the software release life cycle.
Programs that are in an early stage are often called "alpha" software, after the first letter in the Greek alphabet. After they mature but are not yet ready for release, they may be called "beta" software, after the second letter in the Greek alphabet. Generally alpha software is tested by developers only, while beta software is distributed for community testing.
full article
http://en.m.wikipedia.org/wiki/Software_versioning
And as you can see we do not saying that there are no problems an always advice to make a backup before upgrade procedure.
Also there were a major changes between alpha and beta so we have to tested this way as there is no way do it internally as we do not have that many pre-release testers in team
As usual we all do the best to help all and trying to solve the issues asap.
Still,keep in mind, none of us do this as full time job and none of us take any pay. All is done in a free time of each of us.
All need a time.
-thx-
If I can't say anything nice, better to say nothing at all.
28th Jun, 2013, 11:28 PM
Hmm it seems after i left it over night, speed is back to normal... I will install my crap (SB, nzbget, samba & trakt) and see if it still works, and if it survives a reboot
28th Jun, 2013, 11:38 PM
29th Jun, 2013, 12:05 AM
29th Jun, 2013, 01:55 AM
29th Jun, 2013, 02:05 AM
29th Jun, 2013, 02:17 AM
May be slightly off topic for this forum but then again maybe not as the Beta release has been pulled. Question is how do I get a new build or upgrade of Xbian running XBMC 12.2? I'm still learning Linux so go easy! 
I have a nicely working setup of Xbian 1.0A5 (XBMC 12.1) on a Pi and XBMC on a couple of PC's using a shared DB on my Synology NAS so I have been planning an upgrade gradually!
I did a fresh install of Xbian 1.0A5 on a test SD card on Sunday night followed by the upgrade commands I had found "sudo apt-get update" and "sudo apt-get install xbian-package-xbmc -y" followed by the nightly install mentioned in the notes to fix the mouse jumping issue. All worked fine and it upgraded XBMC to version 12.2. So I was planning at some point to upgrade my live system!
But then the new Beta version was released on Tuesday (which I have tried!) and since then the upgrade commands above apart from the first get update command, fail to work!
I assumed it would still work as its a different download package I guess!?
On Thursday the command "sudo apt-get install xbian-package-xbmc -y" generated a lot of errors ending with the error "E: There are problems and -y was used without --force-yes"
As a test I ran the command again as "sudo apt-get install xbian-package-xbmc -y --force-yes" and it did a lot more but still did not upgrade XBMC.
Today its changed again and results in the error below.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
xbian-package-xbmc : Depends: upstart but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
What am I doing wrong? Is there a working XBMC 12.2 version? Is there a simply fix or should I hold on XBMC 12.1 for now? And apologies if this post is too long!
I have a nicely working setup of Xbian 1.0A5 (XBMC 12.1) on a Pi and XBMC on a couple of PC's using a shared DB on my Synology NAS so I have been planning an upgrade gradually!
I did a fresh install of Xbian 1.0A5 on a test SD card on Sunday night followed by the upgrade commands I had found "sudo apt-get update" and "sudo apt-get install xbian-package-xbmc -y" followed by the nightly install mentioned in the notes to fix the mouse jumping issue. All worked fine and it upgraded XBMC to version 12.2. So I was planning at some point to upgrade my live system!
But then the new Beta version was released on Tuesday (which I have tried!) and since then the upgrade commands above apart from the first get update command, fail to work!
I assumed it would still work as its a different download package I guess!?On Thursday the command "sudo apt-get install xbian-package-xbmc -y" generated a lot of errors ending with the error "E: There are problems and -y was used without --force-yes"
As a test I ran the command again as "sudo apt-get install xbian-package-xbmc -y --force-yes" and it did a lot more but still did not upgrade XBMC.
Today its changed again and results in the error below.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
xbian-package-xbmc : Depends: upstart but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
What am I doing wrong? Is there a working XBMC 12.2 version? Is there a simply fix or should I hold on XBMC 12.1 for now? And apologies if this post is too long!
29th Jun, 2013, 02:31 AM