[edgy] wrong dependencies in kdar

I can confirm this situation on edgy.

The same error here with Kubuntu RC:

kdar:
 Depends: libdar3c2a but it is not installable!

Confirmed in Edgy.

Also have the problem on Kubuntu/Edgy:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  kdar: Depends: libdar3c2a but it is not installable
E: Broken packages

Please, fix this bug!
kdar is a really important app for many users!

Thanks

I just came accross this bug. I recently upgraded to edgy eft and cannot do my backups anymore, as kdar cannot be installed due to unmet dependencies.

Confirmed:

"kdar: Depends: libdar3c2a but it is not installable"

kdar has the same problem in feisty. Need either a rebuild
or an upgrade to new upstream release 2.0.7.

this does not fix the problem in edgy of course ;)

Simpel rebuild on 2.0.6 on edgy is not enough, because
the configure script search for libdar, but it's now named
libdar64 (due to the 64bit support).

confirmed

I had a quick, unsucessful try to rebuild 2.0.6 and 2.07.
interdiff appended. Both FTFBS:

/home/ach/tmp/kdar/kdar-2.0.7/./src/createArchiveThread.cpp: In member function ‘virtual void createArchiveThread::run()’:
/home/ach/tmp/kdar/kdar-2.0.7/./src/createArchiveThread.cpp:81: error: cannot declare variable ‘userInteractionDialog’ to be of abstract type ‘KDarInteraction’
...

I've to add --enable-mode=64 to make it find the libdar64
and enable-largefile as suggested in dar's INSTALL. I've
no idea if with this change kdar can read old dapper kdar archives (I've never used kdar).

Any C++ expert, knowing how to fix the build problem?

@allee

Does the new new upstream release 2.0.7 handle the new name correctly?

If so, I think that it can be backported to edgy. Someone would have to package it first, it shouldn't be very hard if you look at the current kdar package at https://launchpad.net/distros/ubuntu/+source/kdar/2.0.6-0ubuntu3

the diff is rather small and most of it is the man page which I don't think needs updating.

... any volunteers? This could be your first ubuntu package!

@rbmorse

Why do you think this affects upstream?
Have you tried to build kdar from source?

Also, if you know that it is an upstream problem, and you decide to mark it as such, it would be nice if you open a bug report upstream (kdebugzilla perhaps?) and link it from here.

The project website http://kdar.sourceforge.net/kdar-news.html
was last updated more than one year ago. It may be that KDar cannot work/compile with recent dar and libdar versions. :(

Confirmed. In this thread [*] someone reports the same error as alleen. It seems there is no fix.

 Johnathan Burchill himself explains:
"KDar 2.x does not compile with dar 2.3.x. The dar library underwent some big and impressive changes from 2.2 to 2.3, and I have not finished upgrading the KDar source code."

I am wondering what will happen with KDar in Feisty. Will it be dropped from the distribution? I don't think that downgrading 'dar' is an option and I don't know the degree of compatibility of archives created by different dar versions.

[*] http://sourceforge.net/mailarchive/forum.php?thread_id=9874678&forum_id=37250

Either it'll be removed, if someone requests it, or it will just stay there uninstallable.

I think I may have a workaround for installing kdar in edgy. It involves installing the needed packages from dapper into edgy (its only two and all dar related). Check my blog for more info: http://psyoptik.wordpress.com/2006/12/20/kdar-dependency-fix-for-ubuntu-edgy/

PLEASE let me know if this is a bad idea, but so far no problems.

I only had to install the libdar3c2a package and kdar has
been working fine. Been doing this since Dapper and it
hasn't dropped a bit, yet.

RBM

On Wednesday 20 December 2006 17:07, psyoptik wrote:
> I think I may have a workaround for installing kdar in
edgy. It involves
> installing the needed packages from dapper into edgy (its
only two and
> all dar related). Check my blog for more info:
>
http://psyoptik.wordpress.com/2006/12/20/kdar-dependency-fix-for-ubuntu-
> edgy/
>
> PLEASE let me know if this is a bad idea, but so far no
problems.
>
> --
> [edgy] wrong dependencies in kdar
> https://launchpad.net/bugs/62699
>

It's really not a serious issue - I have _always_ had the old version of Ubuntu (and before that Debian) in my apt sources. So I have:

deb http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu dapper main restricted universe multiverse

This works and I only discovered that it needed the dapper libdar when I tried a fresh install from CD last week.

Properly built packages should never have a problem if you keep the old Ubuntu version in your sources.

I can confirm this on Kubuntu Edgy. Here is the full error report:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  kdar: Depends: libdar3c2a but it is not installable
E: Broken packages

I've since found the Grsync package will do what I need. It also has
more features and flexibility than KDAR.

I resisted it at first because it requires some GNOME libs, but I
ended up installing other applications that also needed a bunch of
the GNOME support stuff (Gnucash, mostly) so the overhead of
supporting Grsync became minimal.

Ron Morse

On Monday 15 January 2007 16:52, yonkeltron wrote:
> I can confirm this on Kubuntu Edgy. Here is the full error report:
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
>
> Since you only requested a single operation it is extremely likely
> that the package is simply not installable and a bug report against
> that package should be filed.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> kdar: Depends: libdar3c2a but it is not installable
> E: Broken packages

just a little fix: download "dar" and "libdar3c2a" for DAPPER(!!) from packages.ubuntu.com (.deb), install them, after that just install kdar and everything should work perfectly (you can update dar when apt wants you to)

Yeah! thats true! couldnot get thru the installation of Kdar while it says install libdar3c2a package with cannot be installed.

Please solve it !

Thanks

Am told kdar is depreciated. Take a look at grsync

Ron Morse

On Friday 26 January 2007, balarka wrote:
> Yeah! thats true! couldnot get thru the installation of Kdar while
> it says install libdar3c2a package with cannot be installed.
>
>
> Please solve it !
>
>
> Thanks

same problem on feisty -

I know it is depreciated but why it is on feisty if it doesn't work?

Confirmed on feisty.
I used this workaround:
http://www.ubuntugeek.com/disk-archive-backup-and-restore-using-dar-and-kdardar-frontend.html

it's in feisty because if we remove it, we then have to do all the packaging again when it *does* work.

However, i'm considering filing a removal request, just because it doesnt build, not even with 2.0.7.

I'm for a removal.

On Saturday 17 March 2007 06:45:19 Sarah Hobbs wrote:
> it's in feisty because if we remove it, we then have to do all the
> packaging again when it *does* work.
>
> However, i'm considering filing a removal request, just because it
> doesnt build, not even with 2.0.7.

I thought KDAR was depreciated and not being developed anymore. Is this not
correct?

The functional hot ticket seems to be keep, which works, now.

Ron Morse

Op zaterdag 17-03-2007 om 15:22 uur [tijdzone +0000], schreef rbmorse:
> On Saturday 17 March 2007 06:45:19 Sarah Hobbs wrote:
> > it's in feisty because if we remove it, we then have to do all the
> > packaging again when it *does* work.
> >
> > However, i'm considering filing a removal request, just because it
> > doesnt build, not even with 2.0.7.
>
> I thought KDAR was depreciated and not being developed anymore. Is this not
> correct?

If this is the case, could you please suggest a program with similar
functionality? Tnx.

--
Amedee Van Gasse <email address hidden>

On Saturday 17 March 2007 09:40:07 amedee wrote:

> If this is the case, could you please suggest a program with similar
> functionality? Tnx.

I'm on Feisty (ore-beta) now so I'm not sure what is available for other
versions, but Feisty comes with an application named:

keep

It's a KDE app, functionally similar to kdar, but easier to use and configure
(for me) and very functional.

The only thing I am using it for at the moment is to make an automatic backup
of /home to another physical hard drive, but it looks like it can do much
more. I haven't had time to get into it, yet. Give it a try.

grsync

also will do light backups but it is not very configurable (no excludes, for
one) but it is just a front-end to rsync so the basic engine is very robust.

Ron Morse

Sarah Hobbs wrote:
> it's in feisty because if we remove it, we then have to do all the
> packaging again when it *does* work.

Of course, that's not true. It can be moved out of the repos now, and
back if/when it works. Nothing in the repos should have dependency
problems.

Matthew Flaschen

Another alternative would be to rework the source pkg of
libdar3c2a so it can be installed in parallel, then adapt
kdar to new -dev name and rebuild.

I don't want to imply that that is the best solution ;)

On 3/17/07, Matthew Flaschen <email address hidden> wrote:
> Sarah Hobbs wrote:
> > it's in feisty because if we remove it, we then have to do all the
> > packaging again when it *does* work.
>
> Of course, that's not true. It can be moved out of the repos now, and
> back if/when it works. Nothing in the repos should have dependency
> problems.

Exactly. It is unmaintained upstream and the package is uninstallable;
it should be removed.

I think this is wise. see https://bugs.launchpad.net/ubuntu/+source/kdar/+bug/94274