kick out from release

Bug #1812737 reported by Gianfranco Costamagna
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jscommunicator (Ubuntu)
Fix Released
Undecided
Unassigned
jssip (Ubuntu)
Fix Released
Undecided
Unassigned
node-duplexer2 (Ubuntu)
Fix Released
Undecided
Unassigned
node-grunt-contrib-concat (Ubuntu)
Invalid
Undecided
Unassigned
node-marked-man (Ubuntu)
Invalid
Undecided
Unassigned
node-mbtiles (Ubuntu)
Won't Fix
Undecided
Unassigned
node-millstone (Ubuntu)
Won't Fix
Undecided
Unassigned
node-sqlite3 (Ubuntu)
Won't Fix
Undecided
Unassigned
node-tilejson (Ubuntu)
Won't Fix
Undecided
Unassigned
node-websocket (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Kick them out from release
node-websocket: debian bug: #918441
jssip: dependency of node-websocket
node-sqlite3: debian bug: #918408
node-marked-man: debian bug: #912168
node-grunt-contrib-concat: debian bug: #878337
node-duplexer2: needs to be removed, already removed in debian, included and provided by node-duplexer3

description: updated
description: updated
description: updated
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

Removing packages:
 node-duplexer2 0.1.4-1 in disco
  node-duplexer2 0.1.4-1 in disco amd64
  node-duplexer2 0.1.4-1 in disco arm64
  node-duplexer2 0.1.4-1 in disco armhf
  node-duplexer2 0.1.4-1 in disco i386
  node-duplexer2 0.1.4-1 in disco ppc64el
  node-duplexer2 0.1.4-1 in disco s390x
Comment: (From Debian) ROM; FTBFS + provided by node-duplexer3; Debian bug #919575
Remove [y|N]? y

Changed in node-duplexer2 (Ubuntu):
status: New → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

$ reverse-depends src:jssip
Reverse-Depends
===============
* libjs-jscommunicator (for libjs-jssip-bundle)

Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x
$

Changed in jssip (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

$ reverse-depends src:node-marked-man -b
Reverse-Build-Depends
=====================
* node-gulp (for node-marked-man)
* node-loose-envify (for node-marked-man)
* node-semver (for node-marked-man)
* node-sshpk (for node-marked-man)
* npm (for node-marked-man)

$

Changed in node-marked-man (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

$ reverse-depends src:node-sqlite3
Reverse-Depends
===============
* node-mbtiles (for node-sqlite3)
* node-millstone (for node-sqlite3)
* node-tilejson (for node-sqlite3)

Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x
$

Changed in node-sqlite3 (Ubuntu):
status: New → Incomplete
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

$ reverse-depends src:node-sqlite3
Reverse-Depends
===============
* node-mbtiles (for node-sqlite3)
* node-millstone (for node-sqlite3)
* node-tilejson (for node-sqlite3)

they should all go in proposed too, as it is happening in debian (millstone is already out from testing)

Changed in node-sqlite3 (Ubuntu):
status: Incomplete → New
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

$ reverse-depends src:jssip
Reverse-Depends
===============
* libjs-jscommunicator (for libjs-jssip-bundle)

yes, also this one should go in -proposed

Changed in jssip (Ubuntu):
status: Incomplete → New
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

for marked-man, I presume we have to fix it in some way...

Revision history for this message
Steve Langasek (vorlon) wrote :

> they should all go in proposed too, as it is happening in debian
> (millstone is already out from testing)

I don't see evidence that this is what is happening with each of these packages. node-mbtiles is still in testing and has no bug reports filed against it.

The triggering bug, Debian bug #918408, is also fixed in experimental. Should we be syncing node-sqlite3 from experimental instead?

Revision history for this message
Steve Langasek (vorlon) wrote :

Removing packages from disco:
 jscommunicator 2.1.3-1ubuntu1 in disco
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco amd64
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco arm64
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco armhf
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco i386
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco ppc64el
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco s390x
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco amd64
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco arm64
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco armhf
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco i386
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco ppc64el
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco s390x
Comment: Transitively depends on to-be-removed node-websocket, FTBFS, removed from Debian testing; Debian bug #888579, LP: #1812737
1 package successfully removed.

Changed in jscommunicator (Ubuntu):
status: New → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

Debian bug #918441 is not on its own sufficient justification to remove node-websocket, since the missing -lnode is easily fixed by adding a build-dependency on libnode-dev. However, after adding that build-dependency locally, the package still fails to build.

Steve Langasek (vorlon)
Changed in node-mbtiles (Ubuntu):
status: New → Won't Fix
Changed in node-sqlite3 (Ubuntu):
status: New → Won't Fix
Changed in node-tilejson (Ubuntu):
status: New → Won't Fix
Changed in node-millstone (Ubuntu):
status: New → Won't Fix
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

removing the block-proposed tag which is almost always counterproductive.

Steve Langasek (vorlon)
tags: removed: block-proposed
Revision history for this message
Matthias Klose (doko) wrote :

Removing packages from disco:
 node-websocket 1.0.23-3build2 in disco
  libjs-websocket 1.0.23-3build2 in disco amd64
  libjs-websocket 1.0.23-3build2 in disco arm64
  libjs-websocket 1.0.23-3build2 in disco armhf
  libjs-websocket 1.0.23-3build2 in disco i386
  libjs-websocket 1.0.23-3build2 in disco ppc64el
  libjs-websocket 1.0.23-3build2 in disco s390x
  node-websocket 1.0.23-3build2 in disco amd64
  node-websocket 1.0.23-3build2 in disco arm64
  node-websocket 1.0.23-3build2 in disco armhf
  node-websocket 1.0.23-3build2 in disco i386
  node-websocket 1.0.23-3build2 in disco ppc64el
  node-websocket 1.0.23-3build2 in disco s390x
Comment: LP: #1812737: remove node-websocket and demote rdep jssip
1 package successfully removed.

Removing packages from disco-proposed:
 node-websocket 1.0.28-3 in disco
  libjs-websocket 1.0.28-3 in disco amd64
  libjs-websocket 1.0.28-3 in disco arm64
  libjs-websocket 1.0.28-3 in disco armhf
  libjs-websocket 1.0.28-3 in disco i386
  libjs-websocket 1.0.28-3 in disco ppc64el
  libjs-websocket 1.0.28-3 in disco s390x
  node-websocket 1.0.28-3 in disco amd64
  node-websocket 1.0.28-3 in disco arm64
  node-websocket 1.0.28-3 in disco armhf
  node-websocket 1.0.28-3 in disco i386
  node-websocket 1.0.28-3 in disco ppc64el
  node-websocket 1.0.28-3 in disco s390x
Comment: LP: #1812737: remove node-websocket and demote rdep jssip
1 package successfully removed.

Changed in node-websocket (Ubuntu):
status: New → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

Demoting packages to disco-proposed:
 jssip 0.6.34-5 in disco
Comment: LP: #1812737: remove node-websocket and demote rdep jssip
1 package successfully demoted.

Changed in jssip (Ubuntu):
status: New → Fix Released
Changed in node-grunt-contrib-concat (Ubuntu):
status: New → Invalid
Revision history for this message
Steve Langasek (vorlon) wrote :

unsubscribing ubuntu-archive; there's no further action to take until someone sorts out what should be done with the reverse-dependencies of node-marked-man.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

node-marked-man has been fixed in version 0.4.0-1 in the meanwhile, so just invalid for now.

Changed in node-marked-man (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.