From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/rtorrent: bump version to 0.9.7
Date: Wed, 22 Aug 2018 18:47:19 +0200 [thread overview]
Message-ID: <nlg05fxp2v.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180822153649.06549ff0@windsurf
Hi Thomas,
Am Wed, 22 Aug 2018 15:36:49 +0200 schrieb Thomas Petazzoni:
> Why is this for next only ?
because when bumping libtorrent to an openssl-1.1-compatible version I
did not notice that librtorrent and rtorrent are bound to each other,
this is visible on their github release page:
https://github.com/rakshasa/rtorrent/releases
Rtorrent has no direct dependency to openssl, due to lack of time I do
not build-test all reverse dependencies of the many packages needed to be
updated directly for compatability with openssl-1.1.
From my pov build errors like these are expected behaviour, I just let
the autobuilders do their job ;) That's the reason I waited for the rc-
phase to flood the next branch with patches to prepare the version bumps
to ffmpeg-4.0.2 and openssl-1.1.0i. Doing so we should have enough time
until the 2018.11 release to fix all bugs related to these rather
intrusive bumps.
> What causes the build failure that makes it next-specific ?
https://git.buildroot.net/buildroot/commit/?
h=next&id=07673dd6eb2565468abb5730fa3ca9334df683fc
Regards, Bernd
next prev parent reply other threads:[~2018-08-22 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 21:39 [Buildroot] [PATCH/next 1/1] package/rtorrent: bump version to 0.9.7 Bernd Kuhls
2018-08-22 13:36 ` Thomas Petazzoni
2018-08-22 16:47 ` Bernd Kuhls [this message]
2018-09-08 12:51 ` Thomas Petazzoni
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=nlg05fxp2v.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--cc=buildroot@busybox.net \
/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