0004998: Get ruby-awesome-print back into testing or get rid of it

ID	Project	Category	View Status	Date Submitted	Last Update

0004998	Kali Linux	Kali Package Bug	public	2018-09-17 14:32	2019-03-29 16:24

Reporter	rhertzog	Assigned To	rhertzog
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	resolved	Resolution	fixed

Summary	0004998: Get ruby-awesome-print back into testing or get rid of it
Description	The package has failing tests with ruby2.5 and it got dropped from Debian Testing but we have kept it for "idb" that uses it. Upstream has been rather inactive on the various issues reported lately... it's not clear what's the best course of action. We might want to contact the upstream of "idb" to have his opinion on the status of this dependency.

rhertzog 2019-01-15 14:17 administrator ~0010216	Looking more closely into this I discovered that idb is using Qt4 which is no longer maintained. So I filed a ticket upstream asking them to switch to Qt5 but it seems unlikely that this will happen since proper Qt5 ruby bindings are not available: https://github.com/dmayer/idb/issues/111 idb is the only package which depends on ruby-qtbindings so I would rather remove "idb" and "ruby-qtbindings" and be closer to the Qt4 removal goal: https://lists.debian.org/debian-devel-announce/2017/08/msg00006.html https://wiki.debian.org/Qt4Removal @dookie any objection to the removal of "idb" ? It's not mentioned in the PWK course and it's not in any meta-package. @g0tmi1k idb has been packaged on your request last year (see 0001767), but we failed to identify the above problem early enough. What's your opinion ? Is it problematic to remove idb ?

rhertzog 2019-01-15 15:06 administrator ~0010221	FTR Dookie said elsewhere: "i think you can remove idb"

rhertzog 2019-03-29 16:24 administrator ~0010462	In the mean time, ruby-awesome-print is back into testing... but given the discussion, I just removed idb and ruby-qtbindings anyway.

Date Modified	Username	Field	Change
2018-09-17 14:32	rhertzog	New Issue
2018-09-17 14:32	rhertzog	Assigned To	=> rhertzog
2018-09-17 14:32	rhertzog	Status	new => assigned
2019-01-15 14:17	rhertzog	Note Added: 0010216
2019-01-15 15:06	rhertzog	Note Added: 0010221
2019-03-29 16:24	rhertzog	Status	assigned => resolved
2019-03-29 16:24	rhertzog	Resolution	open => fixed
2019-03-29 16:24	rhertzog	Note Added: 0010462