dCore Import Debian Packages to Mountable SCE extensions > dCore X86
sce-update, possible quick check feature
netnomad:
hi friends,
i attached a screenshot about two missing files.
tc@box:~$ version -r
You are running dCore-jessie:2016.01.13.01.02, the latest release candidate.
thank you for your interest.
nitram:
Sorry still something not right, excuse if netnomad indicated same - Dillo can't download attached screenshots properly.
After a fresh boot, didn't run any other sce-* commands or anything previously:
--- Code: ---tc@box:~$ version -r
You are running dCore-jessie:2016.01.13.01.02, the latest release candidate.
tc@box:~$ sce-update -a
/usr/bin/sce-update: line 116: can't open /tmp/debinx: no such file
debian
#################### 100.0% 0.0 kBps DONE
verifying download...checksum matches OK
used 11409408 local, fetched 0
Debian Index synced: debian_jessie_main_i386_Packages
#################### 100.0% 0.0 kBps DONE
verifying download...checksum matches OK
used 362496 local, fetched 0
Debian Security Index synced: debian_jessie_security_i386_Packages
Using the repo http://security.debian.org jessie main
cat: /tmp/PKGEXTRAFILEMD5SUMLIST: No such file or directory
Your SCEs are up to date.
--- End code ---
Jason W:
Ok, I will check into it tonight.
Jason W:
Bugs hopefully fixed, and added option to view diff of new and old debinx data.
Jason W:
Here is an issue I see with this. Unless "sce-update -a" is run and completed, and instead updating only one or several SCEs, the NEWDEBINX when copied to OLDDEBINX at the completion of sce-update, it gives a false impression all SCEs are up to date and therefore until a new change in DEBINX data occurs, it kind of assumes all SCEs have been updated to the latest OLDDEBINX state. Don't know how to fix or work around. Ideas welcome.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version