We have now =dev-util/xdelta-1* in SLOT="0" and =dev-util/xdelta-3* in SLOT="3". Version 1 is providing binary called 'xdelta' but version 3 is providing one with 'xdelta3'. So either.. lock down xdelta dep. for rune to version 1, or test it with version 3 and adjust the command in ebuild accordingly. (It requires a CDROM to be present which I don't obviously have, sorry.)
For these I've changed ebuilds to depend on =dev-util/xdelta-1* for now. games-strategy/heroes3-1.3.1a-r2 games-util/loki_patch-20050324 games-util/loki_patch-20051209 games-action/rune For these I've changed kde-meta.eclass to DEPEND on =dev-util/xdelta-1* for now. kde-base/artsplugin-mpg123-3.5.0:kdexdeltas kde-base/dcopc-3.5.0:kdexdeltas kde-base/dcopperl-3.5.0:kdexdeltas kde-base/kcheckpass-3.5.0:kdexdeltas kde-base/kdeaddons-kfile-plugins-3.5.0:kdexdeltas kde-base/kdeartwork-sounds-3.5.0:kdexdeltas kde-base/kdebugdialog-3.5.0:kdexdeltas kde-base/kdesdk-misc-3.5.0:kdexdeltas kde-base/kreadconfig-3.5.0:kdexdeltas kde-base/kspy-3.5.0:kdexdeltas kde-base/kstart-3.5.0:kdexdeltas kde-base/libksieve-3.5.0:kdexdeltas kde-base/librss-3.5.0:kdexdeltas kde-base/qtsharp-3.5.0:kdexdeltas kde-base/secpolicy-3.5.0:kdexdeltas kde-base/xparts-3.5.0:kdexdeltas
What needs to be done here? and why is it assigned to maintainer-needed? Thanks.
(In reply to comment #2) > What needs to be done here? and why is it assigned to maintainer-needed? > > Thanks. > xdelta-1 and xdelta-3 are for same purpose, but different packages. version -1 installs command xdelta, and a shared library to go with. version -3 installs command xdelta3 and no shared library. so if ebuilds are only using the command xdelta, not the shared library, they should be converted into xdelta3 after verifying it works. also, i'm not sure is the command-line syntax same. assigned to maintainer-needed, because xdelta is maintainer-needed.
the reasoning to switch into xdelta3 is simple -> it's maintained, upstream.
This needs fixing: app-portage/deltup/deltup-0.4.4.ebuild: || ( dev-util/bdelta >=dev-util/xdelta-1.1.3 ) Does xdelta-3 use the same file format as xdelta-1?
(In reply to comment #5) > Does xdelta-3 use the same file format as xdelta-1? > No
(In reply to comment #6) > (In reply to comment #5) > > Does xdelta-3 use the same file format as xdelta-1? > > > No > So there's very little chance, if any, of -3 working for apps using -1 now?
(In reply to comment #7) > So there's very little chance, if any, of -3 working for apps using -1 now? it is a complete rewrite, has different format and completely different command line arguments it is possible to use it for some packages as rune... the delta file needs to be recreated for this though
xdelta1 - rsync algorithm xdelta3 - standardized VCDIFF format
(In reply to comment #5) > This needs fixing: > > app-portage/deltup/deltup-0.4.4.ebuild: || ( dev-util/bdelta > >=dev-util/xdelta-1.1.3 ) Fixed, and closing this bug as there's nothing left to do (based on last comments)
(In reply to comment #10) > (In reply to comment #5) > > This needs fixing: > > > > app-portage/deltup/deltup-0.4.4.ebuild: || ( dev-util/bdelta > > >=dev-util/xdelta-1.1.3 ) > > Fixed, and closing this bug as there's nothing left to do (based on last > comments) > i'm not sure deltup should depend on xdelta||bdelta ... deltup is a wrapper utility for several binary-delta-patches .. including bdelta and xdelta1 (two different formats)
