Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have an interesting problem. The other day I updated my system with kpackage. I run kde. I am also running debian testing (squeeze). I had already made the change to sources.list for squeeze some time ago. This also only seams to affect my lappy which is running the 64.
When I did the last update I had the sources file open through the access method in kpackage. I don't recall the exact sequence of steps that I took at that time but I think I did some updating with the file open and some changes made to it. Don't recall what those changes were. As I remember I was adding a source for freenx for desktop sharing over ethernet. Never did install it.
The problem is that now when I try to look at the sources through kpackage there is nothing there. The sources.list file is there and it still contains every thing it did before, along with the changes I made to it. But it is not accessible through kpackage for editing. If I update the package list it works just like normal.
I have looked at the config files for kpackage but don't see any way to change where it looks for the sources.list file.
I had not given any thought about purging kpackage and doing a reinstall. The malfunction in kpackage is not critical for me. I generally mod my sources through a regular text editor. There is also not generally much reason to change it in the first place.
I think I will follow your advice and see what happens when I get a chance and have nothing more important to work on.
I would suggest using a different package management front end.. since apparently (from the bug reports) no-one cares about kpackage anymore, and most distros are preparing to yank it..
Kpackage has become useless and substitutions (kpackagekit?) are on the way, moreover is not maintained by its author and none cares to take the job of resolving bugs upstream. I think it's time to say R.I.P to kpackage.
Guess I will have to check out other apt-get front ends to see what is out there. I have used kpackage almost exclusively since I started using linux. Since I run kde I don't know what I might use with it.
I am not sure that is that big a deal because kpackage seams to work ok. It is just that I can't edit the sources from within kpackage, otherwize it seams to work fine.
Synaptic seems to be the most popular GUI front end these days.
As far as I can see the issue is more lack of support for kpackage. The Author no longer maintains it. No one else has taken up maintaining it. and no one on the Debian team in interested in maintaining the package. I also see a lot of bugs reported against kpackage, most unconfirmed but then if no-one is maintaining it who is going to confirm them ?
If you learn aptitude from the command line, you'll probably discover that the GUI front ends are slow, unresponsive and just gets in the way.. honest !!
I found out what happened. Somehow the permissions on sources.list got changed to allow only root access and no read access for any one else. So kpackage couldn't read the file. After I corrected that (# chmod 644) it went back to working like it should.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.