Could you PLEASE stop posting to debian-ports@? You are sending these mails to
every Debian Ports architecture mailing list.
I already asked for the third time now.
Thank You,
Adrian
> On May 26, 2019, at 5:34 AM, wrote:
>
> Sorry if this is off-topic, but I can't help asking if that "15381
Sorry if this is off-topic, but I can't help asking if that "15381 March 1977"
was on purpose or just from some wonky email client: 15380 days after March 1st
1977 happens to be April 10th 2019, so...
--
Pengcheng Xu
https://jsteward.moe/
> -Original Message-
> From: Aurelien Jarno
On 15413 March 1977, Aurelien Jarno wrote:
Thats ok, end of May is a nice point to take.
Thanks for the work and the timeframe for the rest!
kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As
hurd-i386 has been moved earlier, it means that all the 3 architectures
have now
* John Paul Adrian Glaubitz [2019-05-25 08:54
+0200]:
> On 5/25/19 8:28 AM, Elimar Riesebieter wrote:
> > is there any reason why the systemd packages are not been updated in
> > ports?
>
> They are. It's just that systemd failed to build on powerpc this time,
> see [1]. Packages are always
On 2019-05-25 13:00, Manuel A. Fernandez Montecelo wrote:
> Hi,
>
> Em sáb, 25 de mai de 2019 às 10:57, Aurelien Jarno
> escreveu:
> >
> > kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As
> > hurd-i386 has been moved earlier, it means that all the 3 architectures
> > have
Hi,
Em sáb, 25 de mai de 2019 às 10:57, Aurelien Jarno
escreveu:
>
> kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As
> hurd-i386 has been moved earlier, it means that all the 3 architectures
> have now been moved.
Nice :-)
Not sure who's the admin (I couldn't find the
Hi,
On 2019-04-24 12:34, Joerg Jaspert wrote:
> On 15381 March 1977, Aurelien Jarno wrote:
>
> > > > It would be nice to have a bit more than 2 weeks to do all of that.
> > > Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this
> > > is on the table already, it doesn't make
On 5/25/19 8:28 AM, Elimar Riesebieter wrote:
> is there any reason why the systemd packages are not been updated in
> ports?
They are. It's just that systemd failed to build on powerpc this time,
see [1]. Packages are always built automatically and when a new version
of systemd gets uploaded to
Hi all,
is there any reason why the systemd packages are not been updated in
ports?
Elimar
--
Do you smell something burning or is it me?
9 matches
Mail list logo
