[backport] Krusader uses unsafe installation method

Bug #51069 reported by John Dong
2
Affects Status Importance Assigned to Milestone
Dapper Backports
Fix Released
Low
Colin Watson
krusader (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Krusader is installed by fetching Debian Sid packages and using dpkg to install it. This is not an acceptable way of installing packages on Ubuntu, and will lead to binary incompatibilities and/or upgrade hell come time for Edgy.

I understand a new version of Krusader is not in Dapper. The proper way to get these packages is through Backports, or by using pbuilder to build clean Dapper packages.

Tags: backport
Revision history for this message
John Dong (jdong) wrote :

I'll use pbuilder to properly compile some 1.70 debs. Until then, the krusader instaler shoud just use Dapper's version.

Changed in automatix:
assignee: nobody → jdong
status: Unconfirmed → Confirmed
Revision history for this message
John Dong (jdong) wrote :

Dapper Backports marked as affected -- a newer Krusader should be brought in via Backports.

Marking as Needs Info as the package is not in Edgy.

Changed in dapper-backports:
importance: Untriaged → Low
status: Unconfirmed → Needs Info
Revision history for this message
John Dong (jdong) wrote :

Also marked Ubuntu source package krusader as affected. When you guys get the chance, please sync a newer krusader from Sid (sid is already at 1.70, and that's good for us)

Thanks!

Changed in krusader:
status: Unconfirmed → Confirmed
Revision history for this message
John Dong (jdong) wrote :

Fixes are under way. Marking as In Progress.

Changed in automatix:
status: Confirmed → In Progress
Revision history for this message
Phillip Heath (mstlyevil) wrote :

I will downgrade the package to 1.6 until the backports can be updated. This will be done on the next release.

Revision history for this message
John Dong (jdong) wrote : Dapper krusader packages

These are krusaders built in a dapper pbuilder, with a backports-style version suffix.

Automatix should use these while awaiting Dapper Backports.

Revision history for this message
Phillip Heath (mstlyevil) wrote : Re: [KDE] Krusader uses unsafe installation method

I will downgrade the package to 1.6 until the backports can be updated. This will be done on the next release.

Revision history for this message
Phillip Heath (mstlyevil) wrote :

We are going to host this package on our server until the backports are updated.

Revision history for this message
John Dong (jdong) wrote :

New version already synced to Edgy; closing Ubuntu ticket.

Changed in krusader:
status: Confirmed → Fix Released
Revision history for this message
John Dong (jdong) wrote :

Package approved for backporting; subscribing the ubuntu-archive team.

Changed in dapper-backports:
status: Needs Info → In Progress
Revision history for this message
Colin Watson (cjwatson) wrote :

 * Trying to backport krusader...
  - <krusader_1.70.0-1ubuntu1.dsc: downloading from librarian>
  - <krusader_1.70.0-1ubuntu1.diff.gz: downloading from librarian>
  - <krusader_1.70.0.orig.tar.gz: downloading from librarian>
I: Extracting krusader_1.70.0-1ubuntu1.dsc ... done.
I: Building backport of krusader-1.70.0 ... done.

Changed in dapper-backports:
assignee: nobody → kamion
status: In Progress → Fix Released
Revision history for this message
John Dong (jdong) wrote :

Automatix team -- updated krusader packages have landed in dapper-backports. There is no need for the unofficial packages anymore.

Changed in automatix:
assignee: jdong → nobody
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.