Re: packages broken on debian / Lemote?
On Thu, Sep 10, 2009 at 10:41 PM, Zhang Weiwu <email@example.com> wrote:
> Non of the problem I mention is a recent problem. They all happened about
> 1/2 years ago. It is the former discussion on lemote reminds me that I still
> have some applications not working. Since we talk this far, I recall
> sloccount also could not get a report for 'path not found' error, adding to
> the broken application list.
According to your source.list config file, those are all testing branches.
And also it's half year ago. Can you still face these problems?
If not, I think you can just leave them alone.
> No, I don't upgrade. I also didn't notice a lot of change on the source, so
What do you mean by 'a lot of changes on the source'? IMHO they should
be binary distribution.
> it is likely the source (which is dev.lemote.com) is outdated. However I am
> afraid of breaking something: I am not a Debian user until half a year ago,
> and I am very busy that if I break something I couldn't find time to fix it
Again, do you mean you accidentally removed some critical files?
> (I broke one lemote last year, luckily Lemote refunded me though not their
> fault), yet I could not ask my colleague to fix for me because Lemote isn't
> part of company business yet, so I try to be careful, a.k.a.
> not to upgrade, unless the gurus on this list says it is safe to do it and
> they did it before.
> I don't see any error updating. My /etc/apt/soruce.list follows:
> # deb http://172.16.0.8/debian/ etch main
> #deb http://www.lemote.com/debian-testing/ testing main contrib non-free
> #deb-src http://www.lemote.com/debian-testing/ testing main contrib non-free
> deb http://dev.lemote.com/debian-loongson loongson contrib main non-free
> deb-src http://dev.lemote.com/debian-loongson loongson main
> deb http://dev.lemote.com/debian lenny main contrib non-free
> deb-src http://dev.lemote.com/debian lenny main contrib non-free
Can you also try to provide 'uname -a' and 'dpkg -l | grep