Bug#766769: marked as done (nmu: beast-mcmc_1.8.0-1)
Your message dated Sat, 25 Oct 2014 21:57:31 +0100
with message-id <1414270651.27925.1.camel@adam-barratt.org.uk>
and subject line Re: Bug#766769: nmu: beast-mcmc_1.8.0-1
has caused the Debian Bug report #766769,
regarding nmu: beast-mcmc_1.8.0-1
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.)
--
766769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766769
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
Hello,
as written on debian-mentors I was wondering why beast-mcmc does not
migrate. Niels recommended that I should file a bug which I'm doing
hereby. Remark: In addition what Niels said below I would like to
mention that one of the binary packages is actually amd64 only:
Package: libnucleotidelikelihoodcore0
Architecture: amd64
I have no idea whether this might be the problem or the solution.
Kind regards
Andreas.
On 2014-10-25 13:00, Andreas Tille wrote:
> Hi,
>
> https://qa.debian.org/excuses.php?package=beast-mcmc
>
> says:
>
> beast-mcmc/i386 unsatisfiable Depends: libnucleotidelikelihoodcore0 (>= 1.8.0-1)
>
> but I have asked ftpmaster for removal of beast-mcmc from arch i386 and
> packages.debian.org says it is only for amd64. Any idea how to enable
> the migration? I guess there might be some remainings from former i386
> versions - but where?
>
> Kind regards
>
> Andreas.
>
Being an arch:all package, it will appear on all architectures. Britney
uses i386 as the architecture to determine whether an arch:all package
is installable or not.
Please file a bug against release.debian.org requesting assistence for
this special case[1] (explaining the situation). The alternative is to
make beast-mcmc an arch:amd64 package. In the given case, it might make
sense...
~Niels
[1] I believe it needs a "force-hint", but I leave the final judgement
to the other members of the RT, who has more experience with this kind
of special case.
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Sat, 2014-10-25 at 18:36 +0200, Andreas Tille wrote:
> as written on debian-mentors I was wondering why beast-mcmc does not
> migrate. Niels recommended that I should file a bug which I'm doing
> hereby. Remark: In addition what Niels said below I would like to
> mention that one of the binary packages is actually amd64 only:
>
> Package: libnucleotidelikelihoodcore0
> Architecture: amd64
>
> I have no idea whether this might be the problem or the solution.
Well, Niels's mail made it quite clear that that's exactly the problem,
so far as I can see (arch:all packages are only checked for
installability on i386, and beast-mcmc is clearly uninstallable on that
architecture). The mail even included a (correct) suggestion as to the
solution.
I've therefore done:
==> adsb
# 20141025
force-hint beast-mcmc/1.8.0-1
so the package should migrate in the next britney run. Note that this
will happen for every migration, at least unless/until britney checks
arch:all on amd64 instead.
Regards,
Adam
--- End Message ---
Reply to: