XBian DEVEL and STAGING repositories

[Killerbee]

(14th Dec, 2013 11:12 AM)f1vefour Wrote:  If you want to join Devel your sources.list should look like this:

Code:

deb http://xbian.brantje.com wheezy main
deb http://xbian.brantje.com devel main
deb http://xbian.brantje.com staging main

Just a stupid question:
Does the sequence matter?
For example is this allowed:

Code:

deb http://xbian.brantje.com staging main
deb http://xbian.brantje.com wheezy main
deb http://xbian.brantje.com devel main

KB

[mk01]

absolutely not

[Killerbee]

(14th Dec, 2013 07:11 PM)mk01 Wrote:  absolutely not

To be sure: sequence matter yes or no?
Because I asked two questions in my post.

Another issue I had today.
Samba upstream update packages

Splash Update .... was running forever.
I checked and some samba dialog screen was shown. Something like: an new /etc/samba/smb.conf file is available. Do you want to overwrite?

Maybe a suggestion to make it possible to "close" the splash by hitting the esc key?

[edit]
Maybe due to my mistake. I installed the samba-server upstream deb.
[/edit]

KB

[mk01]

this is a known issue, I was posting this somewhere. you probably updated with running apt manually. otherwise (xbian-config, auto anything else) would request the install without dialogs.

"no" is answer to sequence.

where is second question ???

[Killerbee]

(14th Dec, 2013 11:01 PM)mk01 Wrote:  this is a known issue, I was posting this somewhere. you probably updated with running apt manually. otherwise (xbian-config, auto anything else) would request the install without dialogs.

"no" is answer to sequence.

where is second question ???

This was my second "question"
For example is this allowed:

Code:

deb http://xbian.brantje.com staging main
deb http://xbian.brantje.com wheezy main
deb http://xbian.brantje.com devel main

Sorry it's clear now. So sequence is not important.
KB

[mk01]

ah ok.

but for your information, there is virtual sequencing based on ORIGIN importance if defined.

you can see the virtual sequence if you do "apt-cache policy xbian-update"

part of the sequence is of course version number, then origin.
(but not order in which sources are defined)

[IriDium]

So in clarification (I'd got it wrong in previous posts)
It doesn't matter what order you add the lines but it would run like this in reality: it's search order is Devel -> Staging -> Wheezy (Based on version numbers) I hope I have that right :-)

This may be a Xbian 1 feature but would it be possible to have an option in ssh xbian-config to show the currently installed "package" and the possible upgrades

eg. xbian-package-kernel
Current: 1.3-6.4
Wheezy: 1.3-6.4
Staging: 1.3-6.5
Devel: 1.3-6.7

I suppose just an output from apt-cache policy xbian-package-kernel but neater.

This would be easier for testers to determine their current installed versions against new previous releases. Also an option to "dump" the contents to a text file, that could then be posted on pastebin or the like.

[mk01]

(15th Dec, 2013 03:49 AM)IriDium Wrote:  So in clarification (I'd got it wrong in previous posts)
It doesn't matter what order you add the lines but it would run like this in reality: it's search order is Devel -> Staging -> Wheezy (Based on version numbers) I hope I have that right :-)

This may be a Xbian 1 feature but would it be possible to have an option in ssh xbian-config to show the currently installed "package" and the possible upgrades

eg. xbian-package-kernel
Current: 1.3-6.4
Wheezy: 1.3-6.4
Staging: 1.3-6.5
Devel: 1.3-6.7

I suppose just an output from apt-cache policy xbian-package-kernel but neater.

This would be easier for testers to determine their current installed versions against new previous releases. Also an option to "dump" the contents to a text file, that could then be posted on pastebin or the like.

xbian-apt-show-versions -u

---

(14th Dec, 2013 09:59 PM)Killerbee Wrote:  

(14th Dec, 2013 07:11 PM)mk01 Wrote:  absolutely not

To be sure: sequence matter yes or no?
Because I asked two questions in my post.

Another issue I had today.
Samba upstream update packages

Splash Update .... was running forever.
I checked and some samba dialog screen was shown. Something like: an new /etc/samba/smb.conf file is available. Do you want to overwrite?

Maybe a suggestion to make it possible to "close" the splash by hitting the esc key?

[edit]
Maybe due to my mistake. I installed the samba-server upstream deb.
[/edit]

KB

there is thd daemon in xbian, check man. just one hook and small script is needed.

[Perkabalo]

Hi I'm new around here, and currently on DEVEL.

Not sure if this is worth reporting, but here it goes..

Having problems upgrading package: xbian-package-cec [ 1.1-0.4 (1.1-1) ]
Looks like there's a dependency problem/missing package

sudo apt-get install xbian-package-cec

Quote:The following packages have unmet dependencies:
xbian-package-cec : Depends: inetutils-ping but it is not installable
E: Unable to correct problems, you have held broken packages.

sudo apt-get install inetutils-ping

Quote:Package inetutils-ping is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'inetutils-ping' has no installation candidate

[f1vefour]

(29th Dec, 2013 06:57 AM)Perkabalo Wrote:  Hi I'm new around here, and currently on DEVEL.

Not sure if this is worth reporting, but here it goes..

Having problems upgrading package: xbian-package-cec [ 1.1-0.4 (1.1-1) ]
Looks like there's a dependency problem/missing package

sudo apt-get install xbian-package-cec

Quote:The following packages have unmet dependencies:
xbian-package-cec : Depends: inetutils-ping but it is not installable
E: Unable to correct problems, you have held broken packages.

sudo apt-get install inetutils-ping

Quote:Package inetutils-ping is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'inetutils-ping' has no installation candidate

You must also add the staging repo.

[Perkabalo]

(29th Dec, 2013 06:45 PM)f1vefour Wrote:  

(29th Dec, 2013 06:57 AM)Perkabalo Wrote:  Hi I'm new around here, and currently on DEVEL.

Not sure if this is worth reporting, but here it goes..

Having problems upgrading package: xbian-package-cec [ 1.1-0.4 (1.1-1) ]
Looks like there's a dependency problem/missing package

sudo apt-get install xbian-package-cec

Quote:The following packages have unmet dependencies:
xbian-package-cec : Depends: inetutils-ping but it is not installable
E: Unable to correct problems, you have held broken packages.

sudo apt-get install inetutils-ping

Quote:Package inetutils-ping is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'inetutils-ping' has no installation candidate

You must also add the staging repo.

The staging repo is already present in sources.list:

Quote:deb http://xbian.brantje.com wheezy main
deb http://xbian.brantje.com devel main
deb http://xbian.brantje.com staging main

[mk01]

(29th Dec, 2013 06:57 AM)Perkabalo Wrote:  sudo apt-get install xbian-package-cec

Quote:The following packages have unmet dependencies:
xbian-package-cec : Depends: inetutils-ping but it is not installable
E: Unable to correct problems, you have held broken packages.

interesting as inetutils-ping is standard package available from upstream (raspbian/debian).

I get this one

Code:

root@xbian /mnt/src/git-mk01/xbmc-pvr-addons # apt-cache show inetutils-ping
Package: inetutils-ping
Source: inetutils
Version: 2:1.9-2
Architecture: armhf
Maintainer: Guillem Jover <guillem@debian.org>
Installed-Size: 255
Depends: libc6 (>= 2.13-28), netbase
Conflicts: hurd (<= 20010718-1), ping
Provides: ping
Homepage: http://www.gnu.org/software/inetutils/
Priority: extra
Section: net
Filename: pool/main/i/inetutils/inetutils-ping_1.9-2_armhf.deb
Size: 163414
SHA256: 08d1263b5dd1371cd58cedebe58165982b30e6fe5b043f8afc16d5f87915cdc3
SHA1: b328403fab7633736e0370d474e15159d854aaf9
MD5sum: d7fb2bf96c703a52bdc14da48b4d16ca
Description: ICMP echo tool
Ping uses ICMP to send out echo requests, and uses the reply packets to
calculate latency between the sending and the destination hosts.
.
This is the portable GNU implementation of ping.

Code:

root@xbian /mnt/src/git-mk01/xbmc-pvr-addons # apt-cache policy inetutils-ping
inetutils-ping:
  Installed: 2:1.9-2
  Candidate: 2:1.9-2
  Version table:
*** 2:1.9-2 0
        500 http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages
        100 /var/lib/dpkg/status

do you still have original raspbian repo enabled? should stay.

Code:

deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi

---

@IriDium

Code:

root@xbian /etc/init # xbian-apt-show-versions -a xbian-package-kernel
xbian-package-kernel 1.3-6.8a install ok installed
xbian-package-kernel 1.3-6.3a staging xbian.brantje.com
xbian-package-kernel 1.3-6.3  stable  xbian.brantje.com
xbian-package-kernel 1.3-6.2  stable  xbian.brantje.com
xbian-package-kernel 1.3-6.1  stable  xbian.brantje.com
xbian-package-kernel 1.3-5.5  stable  xbian.brantje.com
xbian-package-kernel 1.3-5.4  stable  xbian.brantje.com
xbian-package-kernel 1.3-6.8a newer than version in archive

xbian-config is showing versions. unfortunately raspbian repackaging is causing sooooo much long version number. sometimes even 20characters.

and for available upgrade, xbian-config follows apt-get behaviour. from all repos available, take the highest version. I suppose I understand what you mean probably, source repo is missing there but if you go for devel repo you don't care xbian-config.
repo origin is more relevant to auto-updates. as you can have all possible repos set, but by default only stable packages will get auto installed.

raspbian install is not the standard "case" there.

[Perkabalo]

Quote:do you still have original raspbian repo enabled? should stay.

Code:

deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi

---

Ah, that repo wasn't in sources.list, sorry for that.
That solved my self inflicted issue. Thanks!

[mk01]

no problem. in case raspbian - xbian issue appears, please report.

br,

[CurlyMo]

I'm on the latest devel branch and all working fine to date.