From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] openwrt package overriding issues on iproute2
Date: Tue, 26 May 2015 22:33:22 +0100 [thread overview]
Message-ID: <5564E6A2.8020207@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw4+bd9KXZ4L01xeY34XSf-b4s7=rF-VnPNAgh7iH-V-fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On 26/05/15 19:32, Dave Taht wrote:
> On Tue, May 26, 2015 at 11:01 AM, Kevin Darbyshire-Bryant
> <kevin@darbyshire-bryant.me.uk> wrote:
>> Hi Dave & Felix,
>>
>> Looks like someone else has noticed and fixed, I fell into this and other
>> package pointing difficulties a couple of days ago when trying to produce
>> some 'cake' install instructions for 'cake'.
>>
>> https://patchwork.ozlabs.org/patch/476504/
>>
>> A couple of other tidy ups too:
>>
>> https://patchwork.ozlabs.org/patch/476505/
>> https://patchwork.ozlabs.org/patch/476506/
>>
>> Applied all locally and things seem more sensible!
> groovy.
Sadly not so groovy. I was a little premature. The force option still
doesn't override iproute2, but the fixes do allow use of '-p' for the
other packages.
I wish I understood this stuff better I really do.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]
prev parent reply other threads:[~2015-05-26 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 8:49 Dave Taht
2015-05-26 18:01 ` Kevin Darbyshire-Bryant
2015-05-26 18:32 ` Dave Taht
2015-05-26 18:46 ` Dave Taht
2015-05-26 21:33 ` Kevin Darbyshire-Bryant [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5564E6A2.8020207@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nbd@nbd.name \
/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