Problem installing k3b

Choucete · 04-09-2009, 04:39 AM

Hi, I was trying to install k3b from current but I keep getting the following error:

Code:

bash-3.1# slackpkg install k3b

Looking for k3b in package list. Please wait... DONE

<selection screen>

Package: k3b-r936571-i486-1.tgz                                                                                                             
        Downloading k3b-r936571-i486-1.tgz...                                                                                               
--2009-04-09 06:32:39--  http://ftp.belnet.be/packages/slackware/slackware-12.2/slackware/kde/k3b-r936571-i486-1.tgz                        
Resolving ftp.belnet.be... 193.190.67.15, 2001:6a8:a40::21                                                                                  
Connecting to ftp.belnet.be|193.190.67.15|:80... connected.                                                                                 
HTTP request sent, awaiting response... 404 Not Found                                                                                       
2009-04-09 06:32:39 ERROR 404: Not Found.

--2009-04-09 06:32:39--  http://ftp.belnet.be/packages/slackware/slackware-12.2/slackware/kde/k3b-r936571-i486-1.tgz.asc
Resolving ftp.belnet.be... 193.190.67.15, 2001:6a8:a40::21
Connecting to ftp.belnet.be|193.190.67.15|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2009-04-09 06:32:40 ERROR 404: Not Found.

        ERROR - Package not installed! Not found error!

Searching for NEW configuration files
                No .new files found.


==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:

k3b-r936571-i486-1.tgz: Not found

==============================================================================

So I went to review the changelogs and found this

Code:

kde/k3b-r948463-i486-1.tgz: Upgraded to k3b-r948463.

I already tried switching mirrors. The thing is that as some of you may know I'm new to slackware current and slackpkg. Doesn't it install because I first need to upgrade everything else? Or could I just install the latest k3b without that step?

Ramurd · 04-09-2009, 05:08 AM

Looking at your log: you're not downloading it from the -current, but from the 12.2 tree;
The package in 12.2 is k3b-1.0.5-i486-2.tgz
In Slackware-current on http://ftp.belnet.be/packages/slackw...slackware/kde/ is k3b-1.0.5-i486-2.tgz (the same)

It may well be that this mirror is not synced yet with the latest build, so I went looking a bit for you ;-)
http://mirror.pacific.net.au/linux/s...463-i486-1.tgz is a valid file; probably the one you're looking for.

The -current tree is for testing purposes and is usually only good for those that know what they're doing. Normally it is used by those who have a dislike for very stable systems and want things more bleeding edge, so they have some excitement... The latest release (at the moment 12.2) is for those that want a stable system ;-)

Didier Spaier · 04-09-2009, 05:31 AM

Anyhow do not install packages from -current in a -stable distribution, this often won't work.

This is especially true at time of writing for KDE apps, as Slackware 12.2 includes KDE 3 and Slackware current KDE 4.

At best this won't work, at worst you will screw up your system.

Choucete · 04-09-2009, 10:08 AM

Well, I created this thread before going to bed and I was really tired, so I can see I missed a few points: in the first place, Ramurd, you're right, I was trying to download from the 12.2 tree, but I just switched again to one from current and I keep getting the same error.

Didier Spaier, I am in slackware current, my question was because I'm not on the _latest_ slackware current, since I just migrated around two weeks ago and I'm not sure that if I do slackpkg upgrade-all I might brake everything. Can it be the problem? should I upgrade everything again in order to get k3b working? I think I'll try it now.

Choucete · 04-09-2009, 10:41 AM

Well, I've been trying but I keep getting this message:

Code:

bash-3.1# slackpkg upgrade-all

Looking for packages to upgrade. Please wait... DONE

No packages match the pattern for upgrade. Try:

        /usr/sbin/slackpkg install|reinstall

Could it be that the mirrors are not updated yet? Or what am I doing wrong?

disturbed1 · 04-09-2009, 12:06 PM

Quote:

Originally Posted by Choucete

Could it be that the mirrors are not updated yet? Or what am I doing wrong?

If you are using ftp.belnet.be, it is sadly far out of date. Take a look at http://ftp.belnet.be/packages/slackw...slackware/kde/ They still have KDE 3.5 packages from Sept. 2008 - In the current directory. Pick another mirror

You can try
ftp://ftp.slackware.at/
ftp://ftp.bit.nl/ (current and 10.2 only)
ftp://ftp.nluug.nl/
ftp://sharon.esrac.ele.tue.nl

Didier Spaier · 04-09-2009, 02:38 PM

Or ftp://slackware.mirrors.tds.net/pub/...kware-current/

Regularly updated and fast.

Do "slackpkg update" then "slackpk upgrade-all", then "slackpkg install-new" to get new packages, not only updated ones.

If k3b still doesn't show, download it manually then "upgradepkg --install-new --reinstall <package_name>"

Ramurd · 04-09-2009, 05:49 PM

As Didier said, the belnet site is far out of date; Maybe we should report to slackware to either keep them in the list and they update or they get removed from the list of mirrors. Best policy, I think, is to check out some mirrors that are relatively near and up-to-date. Then you can set that as your preferred mirror as they apparently update regulary still.

As for the other question: I think if you update from current to "very current" you should be on the safe spot. But limitations do apply as said about the -current tree, it _may_ break. Warranties just do not exist in the -current tree; Hope this helps.

Choucete · 04-13-2009, 08:39 PM

Sorry it took my some time to reply. This one is fixed and now I have K3b up and running (even thought I haven't tried to burn anything yet). The update wasn't working because I had missed the initial step of 'slackpkg update'.

You'll see, I'm new to the whole current stuff and slackpkg, even though that's no excuse.

Thanks a lot for all the help provided.

janhe · 04-15-2009, 11:00 AM

Quote:

Originally Posted by Ramurd

As Didier said, the belnet site is far out of date; Maybe we should report to slackware to either keep them in the list and they update or they get removed from the list of mirrors. Best policy, I think, is to check out some mirrors that are relatively near and up-to-date. Then you can set that as your preferred mirror as they apparently update regulary still.

As for the other question: I think if you update from current to "very current" you should be on the safe spot. But limitations do apply as said about the -current tree, it _may_ break. Warranties just do not exist in the -current tree; Hope this helps.

I've mailed the friendly people at Belnet. Apparently the problem was with an upstream mirror. They hadn't noticed it yet.

According to the guy who mailed me back, they have fixed the problem and resynced the mirror. (I haven't got a chance to check it yet)

Ramurd · 04-17-2009, 09:34 AM

Quote:

I've mailed the friendly people at Belnet

That's an even better solution :-)