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

Bug#685209: marked as done (unblock: ball/1.4.1+20111206-4)

Your message dated Sat, 13 Apr 2013 12:31:34 +0100
with message-id <1365852694.4627.26.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#685209: unblock: ball/1.4.1+20111206-4
has caused the Debian Bug report #685209,
regarding unblock: ball/1.4.1+20111206-4
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.)


-- 
685209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685209
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: unblock

Please unblock package ball

The uploader is upstream who kindly added a patch to fix a FTBFS.
The buildd are happy now, the package as a good rate of acceptance
on popcon http://qa.debian.org/popcon.php?package=ball
and also scientifically won a series of prices over the last months.
We should expect the number of installations to raise further.

With upstream involving many groups from at (now) many different
institutions, the free license is intrinsic to their development.
Debian Med helps with the distribution of the science, but upstream
is more with Ubuntu and more a virtual-image type of user of Debian
and so the one to blame for the late upload is mostly me who I did
not communicate the freeze in time.

Paired with all the extra funding they get for their research,
also for adopting the very latest hardware from the processor
makers, it is good for Debian to have that link and it would be
sad not to see this structural biology environment in Wheezy.

Many thanks

Steffen

unblock ball/1.4.1+20111206-4

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Sat, 2012-08-18 at 12:34 +0100, Adam D. Barratt wrote:
> On Sat, 2012-08-18 at 13:17 +0200, Steffen Möller wrote:
> > On 08/18/2012 12:48 PM, Adam D. Barratt wrote:
> > > On Sat, 2012-08-18 at 12:05 +0200, Steffen Moeller wrote:
> > >> The uploader is upstream who kindly added a patch to fix a FTBFS.
> [...]
> > > While I'm happy to believe that a number of the patches are required to
> > > fix building with gcc-4.7, these at least don't look like they are:
> > > 
> > >  patches/0007-Fixed-the-FPT-version-of-bond-order-assignment.patch       |  447 ++++
> > >  patches/0008-Added-MAX_PENALTY-option-to-bond-order-assignment.patch    |  975 ++++++++++
> > >  patches/0009-Fixed-a-bug-in-the-AssignBondOrderProcessor.patch          |  271 ++
> > > 
> > > Indeed some of those look like they may well introduce ABI changes if
> > > the changes are reflected in libball.
> 
> Some comment on this, possibly from upstream, would be helpful.  I
> realise that nothing outside of ball uses the libraries, but they (I
> missed libballview) are shipped as public soversioned libraries and
> nothing in the package dependencies appears to ensure that the packages
> are upgraded in step.

I can't find any such comment in the follow-ups. :-(

I'm still somewhat concerned about that, but hopefully it turns out not
to be an issue in the end. Unblocked, with a couple of fingers crossed,
if only in case we need to rebuild ball in stable for any reason.

Regards,

Adam

--- End Message ---
Reply to: