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

Bug#868146: marked as done (transition: alglib)



Your message dated Sat, 15 Sep 2018 06:23:00 +0000
with message-id <d2f3d1f1-edd3-20ef-12f7-1478537c27af@thykier.net>
and subject line Re: Bug#868146: transition: alglib
has caused the Debian Bug report #868146,
regarding transition: alglib
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.)


-- 
868146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868146
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: transition

Dear release team,

please provide a slot for the transition of alglib-library.
The new version 3.11 has been uploaded to the experimental
and built succesfully an all relevant platforms [1].

All reverse dependencies has been successfully built against
the new library version (vtk6, qtiplot and qmapshack).

Ben file:

title = "alglib";
is_affected = .depends ~ "libalglib3.10" | .depends ~ "libalglib3.11";
is_good = .depends ~ "libalglib3.11";
is_bad = .depends ~ "libalglib3.10";


[1] https://buildd.debian.org/status/package.php?p=alglib&suite=experimental

Thanks,

Anton

--- End Message ---
--- Begin Message ---
On Sat, 15 Jul 2017 09:36:18 +0200 Emilio Pozuelo Monfort
<pochu@debian.org> wrote:
> On 14/07/17 23:00, Anton Gladky wrote:
> > 2017-07-14 9:16 GMT+02:00 Emilio Pozuelo Monfort <pochu@debian.org>:
> >> Go ahead now.
> > 
> > Uploaded.
> 
> binNMUs scheduled.
> 
> Emilio
> 
> 

Closing this (long done) transition bug.

Thanks,
~Niels

--- End Message ---

Reply to: