Quoting Cyril Brulebois (k...@debian.org):
> Hi,
>
> Christian PERRIER (2015-07-27):
> > Quoting Joerg Jaspert (jo...@debian.org):
> > > Hi,
> > >
> > > following the last[1] announce, I just removed sparc from
> > >
> > > unstable
> > > experimental
> > > jessie-updates
> >
> > .../...
> >
>
On Fri, 2015-07-31 at 04:34 +0200, Cyril Brulebois wrote:
[...]
> I'm a bit unsure. If sparc ever comes back as sparc64, it might make
> sense to reuse some bits. But I'm not sure whether both archs would be
> close enough for that to happen, or if they would be different beasts
> like arm{el,hf} a
On Fri, 2015-07-31 at 04:34 +0200, Cyril Brulebois wrote:
> I'm a bit unsure. If sparc ever comes back as sparc64, it might make
> sense to reuse some bits.
They can always be recovered from the VCS history or the attic.
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
wit
Hi,
Christian PERRIER (2015-07-27):
> Quoting Joerg Jaspert (jo...@debian.org):
> > Hi,
> >
> > following the last[1] announce, I just removed sparc from
> >
> > unstable
> > experimental
> > jessie-updates
>
> .../...
>
> As a consequence, should we keep sparc-only packages -I know about
> s
Quoting Joerg Jaspert (jo...@debian.org):
> Hi,
>
> following the last[1] announce, I just removed sparc from
>
> unstable
> experimental
> jessie-updates
.../...
As a consequence, should we keep sparc-only packages -I know about
silo-installer at least) in trunk or should they be moved to the
5 matches
Mail list logo