On 27/03/17 13:17, Rafał Miłecki wrote:
From: Rafał Miłecki
Signed-off-by: Rafał Miłecki
Acked-by: John Crispin
---
libfstools/mount.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/libfstools/mount.c b/libfstools/mount.c
index 81176ce..5358536 100644
--- a/libf
On 23/03/17 23:49, Piotr Dymacz wrote:
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them
The return value of fw3_parse_options() should be checked and
when it fails the section should be skipped.
Signed-off-by: Pierre Lebleu
---
defaults.c |6 +-
forwards.c |7 ++-
includes.c |7 ++-
ipsets.c |7 ++-
zones.c|7 ++-
5 files changed, 29 in
To create gpt formatted disk for use with UEFI, a tool for interacting
with gpt partitioned disk is needed. Import roodsbook's gptfdisk for
this purpose.
The tool will be available as gdisk (for interactive use) and sgdisk
(for scripting use).
Signed-off-by: Alif M. Ahmad
---
tools/gptfdisk/Mak
Hi.
I am using the SDK and IB from LEDE 17.01.0 release (mips_24kc). I've
been using it successfully the last days until now. I did not change
anything but I get the error:
* opkg_install_pkg: Package luci-lib-nixio sha256sum mismatch. Either
the opkg or the package index are corrupt. Try 'opkg u
Just to clarify, this SDK/IB work is for the LibreMesh project. We want
to base our new release on LEDE 17.01.0 with the new tool we are
developing for cooking the firmware [1].
So we need actual frozen releases to be sure that once we publish a
release it will be always the same.
[1] https://git
On Mon, Mar 20, 2017 at 3:08 PM, Alexandru Ardelean
wrote:
> From: Alexandru Ardelean
>
> Traditionally if a reload script fails, it will fallback to restart.
>
> That seems to be the default behavior in case no reload
> handler has been specified, and `reload` will return 1.
>
> That also has th
Hi Pau,
On Tue, Mar 28, 2017 at 09:28:22PM +0200, Pau wrote:
> Hi.
>
> I am using the SDK and IB from LEDE 17.01.0 release (mips_24kc). I've
> been using it successfully the last days until now. I did not change
> anything but I get the error:
>
> * opkg_install_pkg: Package luci-lib-nixio sha25
Hi Daniel, thanks for your reply. Find my comments in-line.
On 28/03/17 22:37, Daniel Golle wrote:
> Hi Pau,
>
> On Tue, Mar 28, 2017 at 09:28:22PM +0200, Pau wrote:
>> Hi.
>>
>> I am using the SDK and IB from LEDE 17.01.0 release (mips_24kc). I've
>> been using it successfully the last days unti
Hi,
the mt76-driver package was split up into separate packages and kmod-mt76 was
changed into a metapackage. So when installing kmod-mt76 it will pull the
individual packages.
But kmod-mt76 is not build as package and therefor can't be installed. This
caused some devices already adapted to it
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 28/03/17 17:37, Daniel Golle wr
I am motivated to rant again on this topic. Repeating what I said last
November, before the new release process was finalized, in response to
David Lang:
---
>> There is an interesting question of how to refer to what state of each feed
>> you use for a release. Currently OpenWRT doesn't even tr
On 03/28/2017 06:19 PM, Gui Iribarren via Lede-dev wrote:
>> Packages from the feeds and even base-packages (think: openssl) can
>> change after a release, just like for other distributions.
> i agree packages can and should be maintained, but in progressivereleases.
>i.e. if i install ubuntu 12.04
On 03/29/2017 12:19 AM, Gui Iribarren via Lede-dev wrote:
>i.e. if i install ubuntu 12.04 today, i expect to have exactly the same
>system than what i got if i installed ubuntu 12.04 at the time of its
>release
>if i want to get the fixes that happened after the time of original
>12.04 release, i
On Tue, Mar 28, 2017 at 10:55:09PM +0200, Pau wrote:
> Hi Daniel, thanks for your reply. Find my comments in-line.
>
> On 28/03/17 22:37, Daniel Golle wrote:
> > Hi Pau,
> >
> > On Tue, Mar 28, 2017 at 09:28:22PM +0200, Pau wrote:
> >> Hi.
> >>
> >> I am using the SDK and IB from LEDE 17.01.0 rel
On Tue, Mar 28, 2017 at 11:22:42PM +, Alberto Bursi wrote:
> On 03/29/2017 12:19 AM, Gui Iribarren via Lede-dev wrote:
> > all we want to do is create a firmware based on a specific LEDE release,
> > and not fear that if we want to rebuild the exact same firmware in two
> > months (or days!), w
Hi James,
On Tue, Mar 28, 2017 at 04:58:54PM -0600, James Feeney wrote:
> I am motivated to rant again on this topic. Repeating what I said last
> November, before the new release process was finalized, in response to
> David Lang:
>
> ---
>
> >> There is an interesting question of how to refer
On 29/03/17 02:45, Daniel Golle wrote:
> On Tue, Mar 28, 2017 at 10:55:09PM +0200, Pau wrote:
>> Hi Daniel, thanks for your reply. Find my comments in-line.
>>
>> On 28/03/17 22:37, Daniel Golle wrote:
>>> Hi Pau,
>>>
>>> On Tue, Mar 28, 2017 at 09:28:22PM +0200, Pau wrote:
Hi.
I am
Hi Daniel
> Well, this was actually fixed by having a specific snapshot of all
> feeds referenced in the SDK. Which is exactly the cause of all the
> confusion now...
> ...
>>> ... It would mean that every build was repeatable.
>
> Every build of what exactly?
> Do you realise that *none* of the p
19 matches
Mail list logo
