E: Malformed line 62 in source list /etc/apt/sources.list (URI parse) E: The list of sources could not be read.

[Steven Vollom]

On Thursday 13 August 2009 01:36:55 am Goh Lip wrote:
> Steven Vollom wrote:
> > deb http://packages.medibuntu.org/ jaunty free non-free
> > deb-src http://packages.medibuntu.org/ jaunty free non-free
> > deb http://wine.budgetdedicated.com/apt jaunty main #WineHQ - Ubuntu 9.04
> > "Jaunty Jackalope"
> > deb http://ppa.launchpad.net/bz/ppa/ubuntu jaunty main
> > deb-src http://ppa.launchpad.net/bz/ppa/ubuntu jaunty main
> > deb http://moblock-deb.sourceforge.net/debian intrepid main
> > deb-src http://moblock-deb.sourceforge.net/debian intrepid main
> > deb > http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu jaunty main
> >
> > The Kate window looked like there might be more data, but I couldn't get
> > the screen to scroll or page up or page down.  Does it look like I
> > supplied the entire list?  If not, how do I scroll that page?  Thank you.
> >
> > Steven
> >
> >>> I am baffled.  When I hit F11, it put the number 1 on the first line
> >>> with cursor blinking and no data.  No data at all.
> >
> > deb > http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu jaunty
> > main.  If this line is causing my problem, what do I do to repair the
> > problem, delete it?  And if i delete it, what will happen to the
> > application it is needed for?
>
> Just to be sure, at Dolphin, help,about kde, what is your kde version
> number?

KDE 4.2.2.
>
> In case you did not receive my earlier message, (are you using kmail
> now? what happens to old messages? and why are you repeating questions
> others have replied to?), comment out the ppa repositories. I will also
> recommend commenting out the medibuntu repositories. As for moblock.....

I have only used kmail for about a year now.
>
> Steven, one thing to note, when there is a new change, like from kde
> 4.2.2 to kde 4.3, the 'external' repositories may gum up your computer,
> as these repositories sometimes need some files which may conflict with
> the newer upgrades. So when you add more complications to it, I would
> not be surprised if you keep hitting all the problems you are getting.

This is not a karmic problem it is in the final version of Jaunty.  What I like 
about this problem was the fact that when I got to the line that had the 
problem, I was able to see the problem without help.  I compared it to the 
other entries and it had a '>' between the deb and the http://.  The others 
did not have that, so when I mentioned it, I got several confirmations of what 
was wrong.  When I removed it and also removed the #, it was repaired.

Wow, Goh Lip, I have only had two problems in over a month.  You fixed the one, 
and I learned a lot from the instruction and from the problem.  It was a win 
win situation as far as I am concerned.

The current problem isn't such a big deal.  It kept me from using the CLI for 
a couple of days, but I learned, by action, how to look for an error in a 
computer application.  I am just thrilled with the results.

Actually Jaunty has become so stable, I may have to move my attentions to 
Karmic just to stimulate learning.  I do respect every opinion you have, 
though, my very good friend.  What was amazing was your repair of my previous 
problem seemed such an easy solution for you, and the list had difficulty with 
it.  But without the lingering solution, I may not have come to an 
understanding.  I really think if a similar problem arises, I will have the 
solution without looking at notes or reviewing emails.  What could be better 
than that.

Before I was afraid to enter Kate in sudo mode, now I will be careful, but 
will search out the instruction from the CLI before I trouble the list.  That 
feels like progress.  My love and regards to you and yours.

Steven
> You may think it's a great learning experience, I don't.
>
> Regards,
> Goh Lip