Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v17.01.1
  • v17.01.0
  • v17.01.0-rc2
  • v17.01.0-rc1
  • reboot
6 results
Search by author
  • Any Author
  • Johannes Rudolph Johannes Rudolph PowerPan
1 author
  1. Jul 05, 2016
    • Daniel Dickinson's avatar
      scripts/feeds: Prevent .config autocreation · 34527688
      Daniel Dickinson authored 
      
When using scripts/feeds upgrade the .config needs to be
updated but the code to do so was also autocreating a
.config if one didn't exist.  This is counter-productive
when you have not yet used menuconfig (or other config targets)
because things like selecting or deselecting CONFIG_ALL
(to build all package by default) only works if the
package selection has not already been done via an
existing .config selection.

Signed-off-by: default avatarDaniel Dickinson <lede@daniel.thecshore.com>
      34527688
  3. Jun 15, 2016
  5. Apr 28, 2016
  7. Aug 23, 2015
  9. Jul 14, 2015
  11. Jul 07, 2015
  13. Jun 24, 2015
  15. May 27, 2015
  17. May 23, 2015
  19. May 10, 2015
  21. Mar 15, 2015
  23. Feb 09, 2015
    • John Crispin's avatar
      build: allow openwrt.git packages to be replaced by feeds · 2e2c0477
      John Crispin authored 
      
Currently, replacing a package available in openwrt.git requires
modifications in openwrt.git, or requires duplicating the package in a
feed but with a different name, which causes all kind of problems
related to dependencies (all packages selecting it would have to be
modified accordingly to select the new package).

With this change, if a package with the same name is present both in
feeds/ and package/ folders, the one in feeds/ can override the one
in package/, both in the menuconfig and during the build, by passing the
"-f" option to "./scripts/feeds install"

This mechanism is particularly useful for vendor tree, or in general for
application which needs to replace one particular package which exists
within openwrt.git by a custom/newer version.

Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>

SVN-Revision: 44334
      2e2c0477
  25. Jan 22, 2015
    • John Crispin's avatar
      build: revert r44076 · b6f268d7
      John Crispin authored 
      
the patch causes issues when installing feeds

Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>

SVN-Revision: 44078
      b6f268d7
    • John Crispin's avatar
      build: allow openwrt.git packages to be replaced by feeds · de3bf7e4
      John Crispin authored 
      
Currently, replacing a package available in openwrt.git requires
modifications in openwrt.git, or requires duplicating the package in a
feed but with a different name, which causes all kind of problems
related to dependencies (all packages selecting it would have to be
modified accordingly to select the new package).

With this change, if a package with the same name is present both in
feeds/ and package/ folders, the one in feeds/ can override the one
in package/, both in the menuconfig and during the build, by passing the
"-f" option to "./scripts/feeds install"

This mechanism is particularly useful for vendor tree, or in general for
application which needs to replace one particular package which exists
within openwrt.git by a custom/newer version.

Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>

SVN-Revision: 44076
      de3bf7e4
  27. Oct 13, 2014
    • John Crispin's avatar
      scripts/feeds: handle missing/broken feeds better · 590b855c
      John Crispin authored 
      pts/feeds update -a" can fail rather silently for feeds using git, as
the script does not pause when updating a feed fails. Instead it prints the
error message and calmly continues to the next feed. It is very easy to
overlook update errors with the feeds updated first, as their text scrolls
rapidly away from the screen.

This behaviour has not been a big problem with svn feeds, as svn update stops
with a conflict message and interactively forces the user to resolve or
postpone the conflict. In any case the svn error is noticed by the user.

Majority of the feeds use now git, so this silent failure can affect users
doing private builds in an increasing amount.

Below is an example of update failing and script continuing:

perus@v1404:/Openwrt/barrier$ ./scripts/feeds update -a
Updating feed 'packages' from
'https://github.com/openwrt/packages.git;for-14.07' ...
remote: Counting objects: 17, done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 17 (delta 10), reused 8 (delta 1)
Unpacking objects: 100% (17/17), done.
 From https://github.com/openwrt/packages
62031da..dc26009  for-14.07  -> origin/for-14.07
Updating 62031da..dc26009
error: Your local changes to the following files would be overwritten by merge:
utils/collectd/Makefile
Please, commit your changes or stash them before you can merge.
Aborting
failed.
Updating feed 'luci' from 'http://git.openwrt.org/project/luci.git;luci-0.12' ...
Already up-to-date.
Create index file './feeds/luci.index'
Updating feed 'routing' from
'https://github.com/openwrt-routing/packages.git;for-14.07' ...
...

The script prints "failed.", but does not break the updating process. The
"update_feed" function returns an error code 1, but that value is not checked
in the "update" function, which continues to the next feed.
Return 1 as error:
​https://dev.openwrt.org/browser/trunk/scripts/feeds#L547
Call to update_feed without any error monitoring:
​https://dev.openwrt.org/browser/trunk/scripts/feeds#L585



The included patch makes the feeds script to stop updating after failing to
update a feed.

The script continues to the refresh_config step despite a possible failure in
updating, so the stopping action just prevents the other feeds from updating
and makes the error more clearly visible.

Signed-off-by: default avatarHannu Nyman <hannu.nyman@iki.fi>

SVN-Revision: 42891
      590b855c
  29. Aug 05, 2014
  31. Jun 30, 2014
  33. Sep 25, 2013
  35. Sep 02, 2013
  37. May 29, 2013
  39. Jun 25, 2012
  41. May 08, 2012
  43. Apr 26, 2012
    • Felix Fietkau's avatar
      build: rework verbosity level selection · 34ffb526
      Felix Fietkau authored 
      V=99 and V=1 are now deprecated in favor of a new verbosity class system,
though the old flags are still supported.
You can set the V variable on the command line (or OPENWRT_VERBOSE in the
environment) to one or more of the following characters:

- s: stdout+stderr (equal to the old V=99)
- c: commands (for build systems that suppress commands by default, e.g. kbuild)
- w: warnings/errors only (equal to the old V=1)

SVN-Revision: 31484
      34ffb526
  45. Apr 24, 2012
  47. Oct 21, 2011
  49. May 24, 2011
  51. Dec 06, 2010
  53. Oct 24, 2010
  55. Oct 18, 2010
  57. Oct 02, 2010
  59. Aug 26, 2010