Re: nose2 reverse dependancies

2016-03-07 Thread Paul Wise 
On Tue, Mar 8, 2016 at 12:02 PM, Brian May wrote:
> Paul Wise writes:

> Are these available in Debian/testing? If so, what packages?

According to packages.debian.org and apt metadata:

botch is only in unstable

dose-ceve is in dose-extra, which is in all suites.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: nose2 reverse dependancies

2016-03-07 Thread Brian May 
Paul Wise  writes:

> debtree

This appears to work:

debtree -b python-djangorestframework

Although it doesn't show nose2, so maybe not complete (despite it
looking very complicated)

Suspect the problem is that it only looks at build-depends for 1st level
build dependancies (e.g. mkdocs), not the build depends of these
packages (i.e. the packages mkdocs requires to build).

Which means it doesn't really help debugging the autoremoval message.


> apt-cache dotty

This don't appear to show the dependacy between
python-djangorestframework and mkdocs. Might not support build depends.

> botch
> dose-ceve

Are these available in Debian/testing? If so, what packages?
-- 
Brian May

Re: nose2 reverse dependancies

2016-03-01 Thread Paul Wise 
On Wed, Mar 2, 2016 at 7:02 AM, Mattia Rizzolo wrote:

> FYI, I don't know of a nice way to build a dependency graph, like
> sometimes I see somewhere, with graphiz

On #debian-mentors recently this question came up and the answers were:

debtree
apt-cache dotty
botch
dose-ceve

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: nose2 reverse dependancies

2016-03-01 Thread Brian May 
Mattia Rizzolo  writes:

> They are down the dep chain:
>
> nose2 => nose2-cov => python-pytest-cov => python-watchdog =>
> python-mkdocs => djangorestframework
>
> (if I did my work correctly)

That looks about right. Thanks.

The removal messages are fine if it is an immediate dependancy, however
if there is a long chain it gets hard to work out what the problem
is. Especially as it could be build-depends or depends for any number of
packages in the chain.
-- 
Brian May

Re: nose2 reverse dependancies

2016-03-01 Thread Barry Warsaw 
On Mar 01, 2016, at 11:02 PM, Mattia Rizzolo wrote:

>FYI, I don't know of a nice way to build a dependency graph, like sometimes I
>see somewhere, with graphiz

That's a tool I'd sometimes love to have too.

Cheers,
-Barry


pgpSD9s_Vutxe.pgp
Description: OpenPGP digital signature

Re: nose2 reverse dependancies

2016-03-01 Thread Mattia Rizzolo 
On Wed, Mar 02, 2016 at 09:42:57AM +1100, Brian May wrote:
> According to https://udd.debian.org/cgi-bin/autoremovals.cgi:
> 
> Brian May 
>djangorestframework: buggy deps nose2, flagged for removal in 28.7 days
>python-mkdocs: buggy deps nose2, flagged for removal in 28.7 days
> 
> Which is fine, nose2 really is broken, am about to upload a fix.
> 
> However I can't see any reason why a buggy nose2 is affecting
> djangorestframework or python-mkdocs.
> 
> There doesn't appear to be anything that build-depends on nose2, or its
> binary packages python-nose2 or python3-nose2. Have I missed something
> obvious???

They are down the dep chain:

nose2 => nose2-cov => python-pytest-cov => python-watchdog =>
python-mkdocs => djangorestframework

(if I did my work correctly)

To be more precise, that's what will get removed from testing if you
don't fix that bug (from autoremovals.yaml.cgi):

nose2:
  bugs:
  - '812710'
  dependencies_only: false
  last_checked: 2016-03-01 17:51:47
  rdeps:
  - aodh
  - borgbackup
  - ceilometer
  - couchapp
  - cov-core
  - designate
  - django-countries
  - django-oauth-toolkit
  - djangorestframework
  - djangorestframework-gis
  - djoser
  - drf-fsm-transitions
  - drf-haystack
  - hovercraft
  - mistral
  - mitmproxy
  - nose2-cov
  - openstack-meta-packages
  - python-jsonrpc2
  - python-kdcproxy
  - python-mkdocs
  - python-pymemcache
  - python-pytest-cov
  - python-tooz
  - python-watchdog
  - vmware-nsx
  - vulture
  removal_date: 2016-03-30 17:33:24
  source: nose2
  version: 0.5.0-2

> Reason I ask is because I was planning on testing building packages
> against nose2 that were broken before uploading a new nose2, however I
> can't see any packages that require nose2, which I find somewhat
> confusing. So probably will upload anyway.

Hopefully I cleared some.
FYI, I don't know of a nice way to build a dependency graph, like
sometimes I see somewhere, with graphiz

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature