public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: A few updates - built under Core 120
Date: Thu, 03 May 2018 20:34:49 +0100	[thread overview]
Message-ID: <b907e270ed88c77ce108b4b3401d0d05f02de106.camel@ipfire.org> (raw)
In-Reply-To: <4a161392-a4c2-15d1-4876-99cb4e7c5a23@link38.eu>

[-- Attachment #1: Type: text/plain, Size: 2659 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ah, sorry I forget to check this out.

I just started my build and it will need a while now to go to the point where it
crashes. Probably has something to do with the core update folder. Just delete
that and the build should complete without creating any core updates.

Best,
- -Michael

On Thu, 2018-05-03 at 20:19 +0200, Peter Müller wrote:
> Hi,
> 
> just curios: Does anyone have an idea why the next-tree won't build?
> I poked a little bit, but without satisfying results.
> 
> Like Matthias, I am also interested in updating packages for IPFire 2.x,
> and experiencing the same problem (testing). Usually, I do that in
> a VM, but some network stuff is hard to port into that environment.
> Maybe we could specify some criteria here, but that is nothing with
> a high priority...
> 
> Best regards,
> Peter Müller
> 
> > Perfect. Keep them coming. It is good to bundle them together and align the
> > patches a little with the release schedule of the Core Updates though.
> > 
> > Also, please try to encourage people to review and *test*. We need to have
> > more
> > eyeballs on the patches that we merge than just mine.
> > 
> > Best,
> > -Michael
> > 
> > On Thu, 2018-05-03 at 19:01 +0200, Matthias Fischer wrote:
> > > Hi,
> > > 
> > > as I wrote, current 'next' won't build for me - it still doesn't.
> > > 
> > > So I prepared the following updates under Core 119 / Core 120:
> > > 
> > > pcre	=>	8.4.2
> > > libidn	=>	1.34
> > > nano	=>	2.9.6
> > > htop	=>	2.2.0
> > > openssh	=>	7.7.p1
> > > unbound	=>	1.7.1
> > > 
> > > All of these are running here, patches follow.
> > > 
> > > If anyone has any concerns about this, please let me know.
> > > 
> > > Best,
> > > Matthias
> 
> 
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlrrZFkACgkQgHnw/2+Q
CQc4UQ//RJExr7KDBXYWaMmaTaTA9+lSaSG4wJ5mm6NXaKc6sKpQ8/TCrYZ6dgaA
EtEKENLv7fx+Ch9zcdwAgfEDqLFONhtsA3crwvlwoFdYI4XlXQ8uJIRCUkvx10MW
OLmlFNmDfDm3LO+ZlpGqwKOkh1PBOo0iVnFV8gr4iIsH3Kpeq9FPw2Ls8yx4HXvr
nJRefshrpLdF33ARn+BbZZvj7iv3b5KgeIHagNpOjyTKMx7ggcpv7YD84V5lrQYV
bluDnlcQsq6UVj7PveuNx02FaOO8a7D+z4nUas01ofXH+dvFFumjKWxtwJ5yM7rr
bcYiiKQj4IOlLxmvdvcvpjZpVsHEZcFZwB1SvBqzSGS/oOHhxtHGJXQDU/l7nVUn
7KFBEc78QXbSOv3DD/5UaU5HkwBuqo1HWA1bOvyHRywIQeGvcS/rgIu4c548Gjwd
+XC9ywbY5yKQf6JKfTeaAkPfACOskV3+UVlyu7xc3feqcIBQnTPVnJe+cyz7FgYk
R3NCLEZXN/tJqOU5mPXpOBBKKO0w/ivj3SMgivmU2bmDqeEBAR7RaSVlGYl3paU1
HPRjxfyMDQKLJ0mITsTWkCvV/mI7bu5QwgH+n1kihgAo8Snx2Q69Ge9HptvF/IVq
qIZ0gXgqBx/IF7c0W9cLN21qppfepsm2V+XPqOjLGZb0PZgJtUI=
=YkXc
-----END PGP SIGNATURE-----


  reply	other threads:[~2018-05-03 19:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 17:01 Matthias Fischer
2018-05-03 17:08 ` Michael Tremer
2018-05-03 18:19   ` Peter Müller
2018-05-03 19:34     ` Michael Tremer [this message]
2018-05-04 20:13       ` Matthias Fischer
2018-05-04 20:19       ` Matthias Fischer
2018-05-05 17:50         ` 'next' with new kernel 4.14.39 took a long time - (was: Re: A few updates - built under Core 120) Matthias Fischer
2018-05-06 22:55           ` 'next' with new kernel 4.14.39 took a long time - Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b907e270ed88c77ce108b4b3401d0d05f02de106.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox