Re: nodejs package issues
On Sun, Feb 19, 2017 at 05:21:33PM +1300, Michael Cree wrote: > Thanks for doing that. If there is no action on that by the > maintainer in the near future, which is likely to be the case since > Debian is in hard freeze, I could upload a rebuilt libkf5purpose-bin > with the nodejs dependency removed to debian-ports unreleased. That seems to me to be a good way to go. Besides, does "hard freeze" have any meaning for a non-release architecture anyway? All our updates are from "unstable", "experimental", and "unreleased" as it is. > In the meantime I have found the source of the bug in the binutils > package (but not the fix) and have reported that upstream: > https://sourceware.org/bugzilla/show_bug.cgi?id=21181 Nice work. Going to be interesting to see what the explanation is for the section offset difference. --Bob
Re: nodejs package issues
On Sat, Feb 18, 2017 at 09:49:43PM -0600, Bob Tracy wrote: > On Sat, Feb 18, 2017 at 11:49:06AM -0600, Bob Tracy wrote: > > On Fri, Feb 17, 2017 at 09:13:51AM +0100, Helge Deller wrote: > > > On hppa we will not support jnode short-term (and I assume it's true for > > > most other ports too). > > > So, if you open a bug, please include hppa to have the nodejs dependency > > > removed. > > > > I'll take care of this... Requested closure of #855259 with probable > > status of "won't fix" due to the magnitude of the work required to port > > "nodejs". Agreed that removing the inappropriate dependency on "nodejs" > > by "libkf5purpose-bin" is the way to go. > > Done. See Debian bug #855486. "alpha" and "hppa" specifically > mentioned. Thanks for doing that. If there is no action on that by the maintainer in the near future, which is likely to be the case since Debian is in hard freeze, I could upload a rebuilt libkf5purpose-bin with the nodejs dependency removed to debian-ports unreleased. In the meantime I have found the source of the bug in the binutils package (but not the fix) and have reported that upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=21181 Cheers Michael.
Re: nodejs package issues
On Sat, Feb 18, 2017 at 11:49:06AM -0600, Bob Tracy wrote: > On Fri, Feb 17, 2017 at 09:13:51AM +0100, Helge Deller wrote: > > On hppa we will not support jnode short-term (and I assume it's true for > > most other ports too). > > So, if you open a bug, please include hppa to have the nodejs dependency > > removed. > > I'll take care of this... Requested closure of #855259 with probable > status of "won't fix" due to the magnitude of the work required to port > "nodejs". Agreed that removing the inappropriate dependency on "nodejs" > by "libkf5purpose-bin" is the way to go. Done. See Debian bug #855486. "alpha" and "hppa" specifically mentioned. --Bob
Re: nodejs package issues
On Fri, Feb 17, 2017 at 09:13:51AM +0100, Helge Deller wrote: > On 17.02.2017 06:56, Michael Cree wrote: > > On Thu, Feb 16, 2017 at 08:43:28PM -0600, Bob Tracy wrote: > >> On Thu, Feb 16, 2017 at 08:23:05AM +1300, Michael Cree wrote: > >>> On Wed, Feb 15, 2017 at 03:43:02AM -0600, Bob Tracy wrote: > >>> (...) > Next issue is the "-m32" argument getting passed to the compiler. Not > appropriate for Alpha. > >>> > >>> That's a bug that should be reported to the package maintainer. > >> > >> Done. See Debian bug #855259 filed against the source package > > > > We have libkf5purpose-bin up to date in the archive but it depends on > > nodejs. We should have filed a bug against libkf5purpose-bin to have > > the nodejs dependency removed as has been already been done for armel > > which also does not have nodejs built. Indeed the bug report should > > probably ask for the dependency to be removed for all ports arches > > without nodejs (looks like alpha, hppa, m68k, powerpcspe, sh4, sparc64 > > and x32 but I am not sure whether there is active work or not to > > support nodejs on any of those.) > > On hppa we will not support jnode short-term (and I assume it's true for > most other ports too). > So, if you open a bug, please include hppa to have the nodejs dependency > removed. I'll take care of this... Requested closure of #855259 with probable status of "won't fix" due to the magnitude of the work required to port "nodejs". Agreed that removing the inappropriate dependency on "nodejs" by "libkf5purpose-bin" is the way to go. --Bob
