Announcement

Collapse
No announcement yet.

SOLVED - APT-GET Troubles, what does this mean?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SOLVED - APT-GET Troubles, what does this mean?

    Everytime I attempt to use APT-GET in any way (apt-get install, apt-get update, ect), I get this messege:

    user@computer:~$ sudo apt-get update
    E: Type 'http://ppa.launchpad.net/kubuntu-exp...ppa/ubuntudeb' is not known on line 54 in source list /etc/apt/sources.list

    What does this mean? Apt-get used to work fine.

    Help, please.

    #2
    Re: APT-GET Troubles, what does this mean?

    Open the file /etc/apt/sources.list with kate in super user mode, Alt-F2 "kdesudo kate /etc/apt/sources.list" with no quote marks, and insert a "#" mark at the beginning of that line, then "File>Save" and exit kate.

    In the Konsole, sudo apt-get update should put it back in business.

    Comment


      #3
      Re: APT-GET Troubles, what does this mean?

      Thanks for the quick response, worked magically.

      Comment


        #4
        Re: APT-GET Troubles, what does this mean?

        Cool. 8)

        If you could edit the title and add "SOLVED" in front of it, then it might help someone else with a similar problem -- thanks!

        Comment


          #5
          Re: SOLVED - APT-GET Troubles, what does this mean?

          It looks like the OP tried to add the KDE 4.2.3 repository to their sources.list file.

          The line should have looked like this:
          And from the CLI these command should have been executed:
          sudo apt-get update
          sudo apt-get dist-upgrade
          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
          – John F. Kennedy, February 26, 1962.

          Comment


            #6
            Re: SOLVED - APT-GET Troubles, what does this mean?

            Yes, I think that is so. But, not knowing whether there was another error to be discovered on line 55, it seemed best to get the file working correctly again, before attempting any improvements upon the repos. I think you're right about the intended repo.

            Comment

            Working...
            X