This is interesting. Should we also keep those useless node-* packages out of stretch ?
Note: useless until the actual package we need is packaged (be it browserify, yarnpkg ...). Paolo -------- Messaggio Inoltrato -------- Oggetto: Bug#768073: [pkg-go] Bug#768073: LXC team take over ITP? Rispedito-Data: Fri, 17 Feb 2017 16:12:02 +0000 Rispedito-Da: Jonathan Dowland <j...@debian.org> Rispedito-A: debian-bugs-d...@lists.debian.org Rispedito-CC: w...@debian.org, ad...@hodzic.org Data: Fri, 17 Feb 2017 16:08:18 +0000 Mittente: Jonathan Dowland <j...@debian.org> Rispondi-a: Jonathan Dowland <j...@debian.org>, 768...@bugs.debian.org A: 768...@bugs.debian.org, Debian Go Packaging Team <pkg-go-maintain...@lists.alioth.debian.org> Hi folks, We didn't manage to get LXD into the archive in time for the freeze. We packaged the following specifically as LXD dependencies which did go in: * https://tracker.debian.org/pkg/golang-gopkg-flosch-pongo2.v3 * https://tracker.debian.org/pkg/golang-petname (possibly others, hit-list was at https://wiki.debian.org/LXD) IMHO, and at least for the ones I did, I think we should file RC bugs to prevent these packages from going into stretch. They should stay in the archive/sid, for continued work on LXD, but I don't think that they are valuable on their own in the next release: it's just stuff that people might try to use that isn't being looked after properly (since the reason for them being there does not exist), taking up archive space and apt metadata space, etc. Thoughts? -- Jonathan Dowland -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
