Bug#790254: marked as done (nmu: ovito_2.3.3-3)
Your message dated Tue, 30 Jun 2015 11:05:19 +0200
with message-id <55925BCF.40407@debian.org>
and subject line Re: Bug#790254: nmu: ovito_2.3.3-3
has caused the Debian Bug report #790254,
regarding nmu: ovito_2.3.3-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.)
--
790254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790254
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,
the recent tachyon package upgrade comes with a minor library transition:
it appears that ovito is the only package that depends on tachyon for now,
and that this unique dependency currently blocks the migration of the tachyon
package from unstable to testing. The current ovito package may rebuild against
the new tachyon package without issue.
Please rebuild ovito against the new tachyon package in view to unblock the
migration of the tachyon package from Sid to Stretch.
Thanks in advance,
Jerome
nmu ovito_2.3.3-3 . ALL . -m "tachyon library transition"
--- End Message ---
--- Begin Message ---
On 30/06/15 06:31, Anton Gladky wrote:
> Hi,
>
> 2015-06-28 22:04 GMT+02:00 Jerome BENOIT <calculus@rezozer.net>:
>> I don't see ovito depending on tachyon. It build depends on it, but it doesn't
>> seem to depend on any of tachyon's packages. Can you say what exactly depends on
>> what?
>
> I have disabled tachyon plugin in ovito for the moment and removed
> it from build-depends not to keep the transition. Will try to switch
> it on with a newer ovito upstream version.
OK, closing this as no binNMU is needed then.
Cheers,
Emilio
--- End Message ---
Reply to: