beta2

[mk01]

(11th Nov, 2013 08:06 PM)Klimaks Wrote:  

Code:

sudo mount -t nfs 192.168.1.99:Media /mnt/test
mount.nfs: access denied by server while mounting 192.168.1.99:Media

This is the content of /etc/exports on my synology (which as been ok for 1.1)

Code:

/volume1/Media  *(rw,async,no_wdelay,insecure,no_root_squash,sec=sys,anonuid=0,anongid=0)~

this would be one of the issues which are appearing with updates to base system .there is already one discussion regarding nfs and strange changes in the packages (portmap, nfslibs etc).

just quick look to your mount and export. I assume your synology is creating this as nfs3/2 export, … but your command syntax is asking for nfs4 to try first. Definitely what will be tried at the beginning is /media on synology and nfs4.


I'm fine with the permission denied in such case. try mounting "192.168.1.99:/volume1/Media" ?

---

(11th Nov, 2013 12:42 AM)f1vefour Wrote:  

(5th Nov, 2013 01:20 AM)mk01 Wrote:  

(3rd Nov, 2013 09:08 AM)f1vefour Wrote:  No other daemons are running.

From 'ps ax' after I run lircd the running command is simply 'lircd' with no trailing arguments.

ok isn't this caused by the -u parameter (when used by lirc)? two-three posts have been there about it already.

It is caused by the -u parameter, it should be removed.

@CurlyMo,

any comment to -u (uinput) usage there ? It has been always there since I remember. I don't want to break lirc again.

---

(9th Nov, 2013 09:20 PM)CurlyMo Wrote:  I've noticed a small but significant bug in the deb package generator scripts.

Some of the scripts calculate the package size by running the following command.

Code:

printf "Installed-Size: %d\n" $(du -s ./content | awk '{print $1}') >> ./content/DEBIAN/control

This will generate a wrong installed size for a package.

true. you are right.

and it is not the only bug there. that's why packages with significant size and content causing the bugs to realize (spaces in file names, binaries & libs are not always stripped before packaging - others I don't remember) had the script updated some time ago already. those "lucky" packages have always been xbmc, kernel, headers, … this gen.package script should have been distributed to other packages …

will happen latest with moving beta2 to pub - and packages with wrong info file repacked.

---

(6th Nov, 2013 09:34 PM)rikardo1979 Wrote:  @mk01 can we keep OP post updated please? I mean like a DL link for the latest testing image?
-thx-

was and is … or is not working for you the link ?

---

(7th Nov, 2013 05:00 AM)adepssimius Wrote:  I resolved this already. I was able to fix with an

Terminal

apt-get -f install

which fixed the issue. A week or two ago when I tried (what i thought was) the same procedure I got a different result. Either way, resolution is documented for posterity.

yes, … because based on feedback like yours and some others (very old versions going to be updated or too much dep changes for new packages - or too strict deps in new) we are updating also the control files for deb packages now and then and not only to reflect latest XBian's versions of packages - but also to help APT to choose different order while installing debs or to mitigate number of kept back for older installs etc.