Conflicts when repackaging JACK

[Nicholas M. Revere]

Hello,

My name is Nick Revere.  I am attempting to repackage the latest version
of JACK for my distribution (Mepis 7.0), which is based on etch.  I have
previously packaged JACK 0.109.2-1 successfully.  However, the new
0.109.2-3 packages refuse to install over the previous packages using
"dpkg -i *.deb".  I keep getting the following error:

dpkg: regarding jackd_0.109.2-3mlrepo1_i386.deb containing jackd:
  libjack0 conflicts with jackd (>> 0.109.2-2mepcom1)
   jackd (version 0.109.2-3mlrepo1) is to be installed.
dpkg: error processing jackd_0.109.2-3mlrepo1_i386.deb (--install):
  conflicting packages - not installing jackd
dpkg: regarding libjack0_0.109.2-3mlrepo1_i386.deb containing libjack0:
  libjack0 conflicts with jackd (<< 0.109.2-3mlrepo1)
   jackd (version 0.109.2-2mepcom1) is installed.
dpkg: error processing libjack0_0.109.2-3mlrepo1_i386.deb (--install):
  conflicting packages - not installing libjack0
(Reading database ... 188490 files and directories currently installed.)
Preparing to replace libjack0.100.0-0 0.109.2-2mepcom1 (using
libjack0.100.0-0_0.109.2-3mlrepo1_all.deb) ...
Unpacking replacement libjack0.100.0-0 ...
Preparing to replace libjack0.100.0-dev 0.109.2-2mepcom1 (using
libjack0.100.0-dev_0.109.2-3mlrepo1_all.deb) ...
Unpacking replacement libjack0.100.0-dev ...
Preparing to replace libjack-dev 0.109.2-2mepcom1 (using
libjack-dev_0.109.2-3mlrepo1_i386.deb) ...
Unpacking replacement libjack-dev ...
dpkg: dependency problems prevent configuration of libjack0.100.0-0:
  libjack0.100.0-0 depends on libjack0 (>= 0.109.2-3mlrepo1); however:
   Version of libjack0 on system is 0.109.2-2mepcom1.
dpkg: error processing libjack0.100.0-0 (--install):
  dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libjack-dev:
  libjack-dev depends on libjack0 (= 0.109.2-3mlrepo1); however:
   Version of libjack0 on system is 0.109.2-2mepcom1.
dpkg: error processing libjack-dev (--install):
  dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libjack0.100.0-dev:
  libjack0.100.0-dev depends on libjack-dev (>= 0.109.2-3mlrepo1); however:
   Package libjack-dev is not configured yet.
dpkg: error processing libjack0.100.0-dev (--install):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  jackd_0.109.2-3mlrepo1_i386.deb
  libjack0_0.109.2-3mlrepo1_i386.deb
  libjack0.100.0-0
  libjack-dev
  libjack0.100.0-dev

I can install the new packages after using the --force-all option in
dpkg to install libjack0, but these packages are intended for a
community repository, and I am unsure of how these things will be
handled by package management software.  I have tried several edits of
the control file (Conflicts, Replaces, etc.)  If you could advise, it
would be much appreciated.  I am sorry if the solution is obvious and I
have wasted your time, but this problem seems intractable.

Thanks,
Nick Revere


--
To UNSUBSCRIBE, email to debian-multimedia-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Daniel James-2]

Hi Nick,

I think these are the pertinent lines:

>  libjack0.100.0-0 depends on libjack0 (>= 0.109.2-3mlrepo1); however:
>   Version of libjack0 on system is 0.109.2-2mepcom1.

>  libjack-dev depends on libjack0 (= 0.109.2-3mlrepo1); however:
>   Version of libjack0 on system is 0.109.2-2mepcom1.

There's a slight version mismatch there. The system is looking for the
package suffix 2-3mlrepo1 but it's finding the suffix 2-2mepcom1.

Cheers!

Daniel


--
To UNSUBSCRIBE, email to debian-multimedia-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Nicholas M. Revere]

Daniel James wrote:

> Hi Nick,
>
> I think these are the pertinent lines:
>
>>  libjack0.100.0-0 depends on libjack0 (>= 0.109.2-3mlrepo1); however:
>>   Version of libjack0 on system is 0.109.2-2mepcom1.
>
>>  libjack-dev depends on libjack0 (= 0.109.2-3mlrepo1); however:
>>   Version of libjack0 on system is 0.109.2-2mepcom1.
>
> There's a slight version mismatch there. The system is looking for the
> package suffix 2-3mlrepo1 but it's finding the suffix 2-2mepcom1.
>
> Cheers!
>
> Daniel
>
>

Hello Daniel,

Thanks for your reply!  I see what you mean.  However, the new package
with the suffix 2-3mlrepo1 is supposed to be installed by the same dpkg
process.  The problem is that the new libjack0 refuses to install over
the old packages without being forced.  In these lines:

dpkg: regarding jackd_0.109.2-3mlrepo1_i386.deb containing jackd:
  libjack0 conflicts with jackd (>> 0.109.2-2mepcom1)
   jackd (version 0.109.2-3mlrepo1) is to be installed.
dpkg: error processing jackd_0.109.2-3mlrepo1_i386.deb (--install):
  conflicting packages - not installing jackd
dpkg: regarding libjack0_0.109.2-3mlrepo1_i386.deb containing libjack0:
  libjack0 conflicts with jackd (<< 0.109.2-3mlrepo1)
   jackd (version 0.109.2-2mepcom1) is installed.
dpkg: error processing libjack0_0.109.2-3mlrepo1_i386.deb (--install):
  conflicting packages - not installing libjack0

you can see I am trying to install the new libjack0 package as well, but
it is refusing to install over the old version.  If I use the option
--force-all with just the libjack0 package, it will install, and I can
then install the rest of the packages without issue.  I just don't know
how this would translate to a repository.  If I have to manually force
the package, how will Synaptic et al. deal with it?  If Synaptic will
make it work properly, than there is no issue.  But isn't Synaptic just
a front-end to dpkg?  Is there something I can edit in the control file
to make dpkg realize it has to replace libjack0 first?  I tried using
the Replace: and Conflicts: lines, putting in the old version (e.g. in
the libjack0 Conflicts: section added libjack0 (= 0.109.2-2mepcom1) and
added a Replaces: line with the same), but it still did not work
properly.  I also tried with no version, and adding jackd with and
without a version to libjack0's Conlicts and Replaces.  I also tried the
same things in the jackd section, and none of it worked.  Is this only a
problem because they are both the same upstream version?  The original
-2mepcom1 packages installed fine over the stock etch versions using
dpkg -i *.deb.  The newest one is a newer Debian revision.  Again, thank
you for your reply, it is much appreciated!

Nick


--
To UNSUBSCRIBE, email to debian-multimedia-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Daniel James-2]

Hi Nick,

 > The problem is that the new libjack0 refuses to install over
> the old packages without being forced.  In these lines:
>
> dpkg: regarding jackd_0.109.2-3mlrepo1_i386.deb containing jackd:
>  libjack0 conflicts with jackd (>> 0.109.2-2mepcom1)
>   jackd (version 0.109.2-3mlrepo1) is to be installed.

It does look like you'd have to remove all jackd dependant packages
before upgrading libjack0, which seems wrong. However, I should add that
jackd 0.109.2 is not stable; you should really wait for a new upstream
release before suggesting that users upgrade.

>  If I use the option
> --force-all with just the libjack0 package, it will install, and I can
> then install the rest of the packages without issue.  I just don't know
> how this would translate to a repository.

Hmm, that's not good, you're bound to get complaints :-)

Cheers!

Daniel


--
To UNSUBSCRIBE, email to debian-multimedia-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Nicholas M. Revere]

Daniel James wrote:

> Hi Nick,
>
>  > The problem is that the new libjack0 refuses to install over
>> the old packages without being forced.  In these lines:
>>
>> dpkg: regarding jackd_0.109.2-3mlrepo1_i386.deb containing jackd:
>>  libjack0 conflicts with jackd (>> 0.109.2-2mepcom1)
>>   jackd (version 0.109.2-3mlrepo1) is to be installed.
>
> It does look like you'd have to remove all jackd dependant packages
> before upgrading libjack0, which seems wrong. However, I should add that
> jackd 0.109.2 is not stable; you should really wait for a new upstream
> release before suggesting that users upgrade.
>
>>  If I use the option
>> --force-all with just the libjack0 package, it will install, and I can
>> then install the rest of the packages without issue.  I just don't
>> know how this would translate to a repository.
>
> Hmm, that's not good, you're bound to get complaints :-)
>
> Cheers!
>
> Daniel
>
>

Daniel,

Thanks again for the help.  I have decided to build against the version
from Studio64, 0.103.0, for the repo.  That way everyone who already has
my 0.109.2 packages installed can keep them, and those who don't
(hopefully) won't face any upgrade issues.

Nick


--
To UNSUBSCRIBE, email to debian-multimedia-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...