[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#676433: marked as done (nmu: kmymoney_4.6.2-3)

Your message dated Sun, 10 Jun 2012 16:15:30 +0200
with message-id <4FD4AC02.70403@debian.org>
and subject line Re: Bug#676433: nmu: kmymoney_4.6.2-3
has caused the Debian Bug report #676433,
regarding nmu: kmymoney_4.6.2-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
676433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676433
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu


Hello,

there was a new upstream release that introduced a soname bump in libaqbanking.
For this reason all packages with build-deps on libaqbanking33-dev needs a
source-full upload in order to switch to libaqbanking34-dev and to pick up the
dependency on the new package libaqbanking34.

The package kmymoney has a build-dep on 'libaqbanking33-dev |
libaqbanking-dev'. For this reason I hope that a binNMU is enough as a short
term solution to the problem. For the long term solution I filed bug #676430
against the kmymoney package.

nmu kmymoney_4.6.2-3 . ALL . -m "recompile against the new libaqbanking34-dev"

Thanks
Micha

--- End Message ---
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Adam,

Am 07.06.2012 00:22, schrieb Adam D. Barratt:
>>>> The package kmymoney has a build-dep on 'libaqbanking33-dev |
>>>> > >> libaqbanking-dev'. For this reason I hope that a binNMU is enough as a short
>>>> > >> term solution to the problem.
>>> > > 
>>> > > It's not even a short term solution, I'm afraid.  The buildds will only
>>> > > consider the first branch of an alternative build-dependency, which
>>> > > means libaqbanking33-dev will always be installed.
>> > 
>> > Huh, I was afraid that might happen - now it really happened. If the
>> > binNMU really isn't sufficient I will raise the severity of #676430
>> > accordingly and do a NMU as needed.
> It makes builds more reproducible, as you can guarantee which of the
> alternatives will be installed.  Having said that, libaqbanking33-dev
> will stay in unstable anyway until it's manually removed, which is
> unlikely to happen until all the {build-,}dependencies have migrated (or
> someone asks ftpmaster to remove it even though stuff breaks) so afaics
> the result would be the same in any case.

Okay, I fixed #676430 now by a regular NMU. This makes this bug
obsolete, hence I am closing it.

Regards,
Micha
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJP1KwCAAoJEOpsprlRuFE5Hb4QAJoYpxSoCO6jeTEbkDmAg2um
wK4RnVs5MuOqZm5XfP/EP4ajduu6cmXOvfr+4Bz+2QSE1RZ8s4oec6s0rPfnn3lp
YTmAoN3YcrwIBVBGfUf9NW5S3F0hv1EpworQU9YQCWZq50WDhpJ3bnXUKhYE5Eax
6J/8xmzRyIMnynhzs4A2fNCtIBOR8uN6kWaaeHrm25yBQarxGx2pRr8xnkVOVnRO
F+fjvmgSogBKdtinJAwlyvipyr7JwD6xhVlN1DzzAQLFzXVfNA/o+17k/r7nPUdN
CGyanEW8QAELVsyLuoITT2KocICwp9AkVoykRxsV216FL7hjgiFY3upJXqV3YnV4
h9iz53JBLox63DWKDVm2TYE0Uy1Gkhkei3FGpJ6airutSVi8FyNijXeF5PLtzuxK
6AO5JbioFiq4iwauBd2eOVykG1wejAZoTqm3rE/tK5JGvxIERv+DIZluf5FbNSPM
A8PS1rbfsssm2wqMOitY3oBNUddE9eLZfxLASxGxW1rSA8OwVuP7qzmHJSMm8yaZ
tIr7pq25+/bDv4XgepZEbCzNMQ0qUx/vF4ciPt76y8YQ9JgBVpzTI0xlg75zipuV
0mrl6FbQ+MsUWxlV+WF7WoeL2ZYWwrAFPwjY1T+WSqzYrzBrzcAcwOqrVQRnrRe3
Q8rM5Wg1xuoTk73dzPKK
=sd3p
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: