p.s. I can see what I was looking at now. I was tracing mpi4py
dependents and saw libgpuarray.
On 2019-10-20 23:03, Rebecca N. Palmer wrote:
Possible alternative (where $m is the module name) - note that this
outputs 1 line (the source package itself) not 0 for ready-to-remove
packages:
grep-dctrl -w -F Pre-Depends,Depends,Recommends,Suggests -s Source
"python-$m"
/var/lib/apt/lists/*_de
On 20/10/2019 14:25, Drew Parsons wrote:
http://sandrotosi.me/debian/py2removal/index.html, where src:libgpuarray
shows with no dependencies,
The 0 there is in the forward Depends column, not reverse depends (maybe
the column order should be changed, given that the reverse depends
column is
On 2019-10-20 20:14, Rebecca N. Palmer wrote:
The libgpuarray dependency chain is python-lasagne Depends
python-theano Recommends python-pygpu (src:libgpuarray), and none of
those have been uploaded recently.
Did you mean to post this to a different package, or are you using a
checking tool that
The libgpuarray dependency chain is python-lasagne Depends python-theano
Recommends python-pygpu (src:libgpuarray), and none of those have been
uploaded recently.
Did you mean to post this to a different package, or are you using a
checking tool that assumes binary name = python-sourcename and
Source: libgpuarray
Followup-For: Bug #936870
All libgpuarray python2 rdeps are now out of the way.
Ready for upload now I think!
6 matches
Mail list logo
