Re: [OpenWrt-Devel] Annoying opkg bug since r17152
Note this happens for any package source, not just the openwrt.org one. On Fri, Aug 7, 2009 at 12:46 AM, Dave Cooper wrote: > Since the opkg source was bumped in r17152, everything works fine, but > all legal opkg operations trail with the following error message: > > Collected errors: > * ERROR: duplicate src declaration. Skipping: > src snapshots > http://downloads.openwrt.org/snapshots/trunk/brcm47xx/packages > > I've done a little bit of bug chasing, and it seems the config file > /etc/opkg/opkg.conf is parsed twice and this causes the error. It > could cause other errors as well. Not sure about a fix just yet, but > it seemed prudent to report since opkg is a somewhat important > package. :P > > Thanks, > Dave Cooper > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Annoying opkg bug since r17152
Since the opkg source was bumped in r17152, everything works fine, but all legal opkg operations trail with the following error message: Collected errors: * ERROR: duplicate src declaration. Skipping: src snapshots http://downloads.openwrt.org/snapshots/trunk/brcm47xx/packages I've done a little bit of bug chasing, and it seems the config file /etc/opkg/opkg.conf is parsed twice and this causes the error. It could cause other errors as well. Not sure about a fix just yet, but it seemed prudent to report since opkg is a somewhat important package. :P Thanks, Dave Cooper ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] base-files: set default value for config_get via 4th parameter plus some more (#5636)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Applied in r17155-r17160. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkp7jWsACgkQdputYINPTPMRGgCbBqXwvqdDrdhVkdys9/WSc4fw xHAAoIbUOkESdZrGa7YWkhKokaFuvD3P =TKwc -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Mercurial or Git repository for OpenWrt?
Hi! On Thu, Aug 6, 2009 at 11:44 PM, Jan Willies wrote: > If you prefer working with git, it is possible to use: > > * git://nbd.name/openwrt.git (clone of trunk) > * git://nbd.name/packages.git (clone of packages) I must have been blind. ;-) Mitar ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Mercurial or Git repository for OpenWrt?
Hi Mitar, Am 06.08.2009 23:40, schrieb Mitar: Or at least if there would be a Mercurial/Git read-only repository which would be kept in sync with SVN repository so that changes could be pulled from it. from https://dev.openwrt.org/wiki/GetSource: If you prefer working with git, it is possible to use: * git://nbd.name/openwrt.git (clone of trunk) * git://nbd.name/packages.git (clone of packages) - jan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [patch] opkg Repository Switch Config Option
Hi all, Here a quick patch to abstract the opkg repository used in a build as a configuration option, with the default pointing to downloads.openwrt.org as usual. Useful for hosting different OpenWrt trees. If applied, a minor note that the repository location for future releases should be updated in packages/opkg/Makefile and not in packages/opkg/files/opkg.conf. Also, _ARCH_ is now used as the architecture instead of $S. Best, Dave Cooper Signed-off-by: David Cooper (attached as GMail loves chomping my patches) Index: package/opkg/files/opkg.conf === --- package/opkg/files/opkg.conf (revision 17153) +++ package/opkg/files/opkg.conf (working copy) @@ -1,4 +1,4 @@ -src/gz snapshots http://downloads.openwrt.org/snapshots/trunk/$S/packages +src/gz snapshots $SOURCE dest root / dest ram /tmp lists_dir ext /var/opkg-lists Index: package/opkg/Makefile === --- package/opkg/Makefile (revision 17153) +++ package/opkg/Makefile (working copy) @@ -6,10 +6,13 @@ include $(TOPDIR)/rules.mk +# Change this URL for a release, use _ARCH_ for architecture +OPKG_PACKAGE_SRC=http://downloads.openwrt.org/snapshots/trunk/_ARCH_/packages + PKG_NAME:=opkg PKG_REV:=215 PKG_VERSION:=$(PKG_REV) -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_SOURCE_PROTO:=svn PKG_SOURCE_VERSION:=$(PKG_REV) @@ -69,7 +72,8 @@ $(INSTALL_DIR) $(1)/etc $(INSTALL_DIR) $(1)/etc/opkg $(INSTALL_DATA) ./files/opkg.conf $(1)/etc/opkg/ - $(SED) 's,S,$(PKGARCH),g' $(1)/etc/opkg/opkg.conf + $(SED) 's#SOURCE#$(if $(call qstrip,$(CONFIG_OPKG_CUSTOM_SRC)),$(call qstrip,$(CONFIG_OPKG_CUSTOM_SRC)),$(OPKG_PACKAGE_SRC))#g' $(1)/etc/opkg/opkg.conf + $(SED) 's#_ARCH_#$(PKGARCH)#g' $(1)/etc/opkg/opkg.conf $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/opkg-cl $(1)/bin/opkg $(INSTALL_DIR) $(1)/usr/lib $(CP) $(PKG_INSTALL_DIR)/usr/lib/libopkg.so.* $(1)/usr/lib/ Index: Config.in === --- Config.in (revision 17153) +++ Config.in (working copy) @@ -97,6 +97,16 @@ help This removes all ipkg data from the target directory before building the root fs +config OPKG_CUSTOM_SRC + string + prompt "Custom opkg package source" + default "" + help + Use this URL as a custom opkg package source. Leave blank for the + default (ie openwrt.org). Use _ARCH_ as short for the current + architecture. + Example: http://www.example.com/openwrt/_ARCH_/packages + choice prompt "Binary stripping method" default USE_STRIP if USE_GLIBC || USE_EGLIBC ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Mercurial or Git repository for OpenWrt?
Hi! I am wondering if it would be possible to migrate OpenWrt's SVN repository to Mercurial or Git. In this way it would be much much easier to develop OpenWrt based projects and pull/merge new code changes from OpenWrt repository to projects' repositories. Trac also supports both Mercurial and Git. I think this would be the best approach in a longer run. Or at least if there would be a Mercurial/Git read-only repository which would be kept in sync with SVN repository so that changes could be pulled from it. I know I can establish such sync locally, but I would like to open a question as maybe it would benefit also others to have Mercurial or Git access to source changes. Mitar ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [patch] combined uci support for etherwake and wol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, also had some private discussions about this, especially one with Lubek. It turned out that most people will either use etherwake or wol, but normally not both. For example I never got wol to work correctly, but etherwake worked right from the start. So the combined uci support would only be meaningful for a few or no user. Hence I re-created uci support for etherwake similar to the current wol package. The init script can wake up targets on boot, but also wake up special targets when called with "start ". ftp://ftp.maddes.net/openwrt/kamikaze/orion/patches/etherwake/ On 03.08.2009 22:31, Jo-Philipp Wich wrote: > The UCI handling looks good, but why separate commands for the uci version? > > Wouldn't it be better to have for example a "wol" script that calls > "wol.real"? If the "wol" script is called without arguments, it'll use > the uci configuration, if flags are provided it operates as usual. > > What do you think about this? Also had the idea for a wrapper script, but skipped it immediately as I didn't dare to rename an executable. The wrapper script should handle three situations: no parameter - wake up all targets that are marked for 'wakeuponboot' target name - wake up the target from the uci config mac - wake up the given mac target "no parameter" is typically an init script. "mac" is typically the original executable itself. Hence adding the "target name" functionality to the init script was straight forward. Regards Matthias "Maddes" Bücher -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkp7RQkACgkQUXXT+9wZdbXC9QCg4k0jrxvhWnCDQrS5wQ2TlF/L 52UAoIkEReNZ+HnVyfqMoTj8aEizWRMS =Lgh2 -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ksymoops for ARM / orion available?
Matthias Buecher / Germany wrote: > Is ksymoops for ARM / Orion working? > If so can it be added to the OpenWrt repository? > Currently the package seems to be restricted to Mipsel and x86. > > I just ask because I want to investigate the oops message from OpenVPN I > got (see #5341). In toplevel menuconfig, select "Compile the kernel with symbol table information". That way the kernel will be compiled with the KALLSYMS option, which makes it unnecessary to run ksymoops. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] base-files: set default value for config_get via 4th parameter plus some more (#5636)
The command config_get_bool allows a fourth parameter which defines a default value. At many places it would be very useful if the plain three-parameter version of config get supported such a parameter as well, that saves a bunch of [ -z "$foo" ] checks in my scripts. In bug 5636 [0] you can find some patches: The first [1] introduces an optional fourth parameter to config_get. That patch could be backported to 8.09 branch. The next four patches [2,3,4,5] apply this four-parameter version in functions.sh, init.d/boot, init.d/led and init.d/fstab. Finally there's another patch [6] to /lib/network/config.sh which also includes some refactoring moving around some code and localizes a lot of variables which weren't so before. The changes don't spread over more than two hunks per refactoring. Cheers, Malte [0]https://dev.openwrt.org/ticket/5636 [1]https://dev.openwrt.org/attachment/ticket/5636/0001--package-base-files- allow-default-value-for-config.patch [2]https://dev.openwrt.org/attachment/ticket/5636/0002--package-base-files- port-functions.sh-to-new-confi.patch [3]https://dev.openwrt.org/attachment/ticket/5636/0003--package-base-files- port-init.d-boot-to-new-config.patch [4]https://dev.openwrt.org/attachment/ticket/5636/0004--package-base-files- port-init.d-led-to-new-config_.patch [5]https://dev.openwrt.org/attachment/ticket/5636/0005--package-base-files- clean-up-init.d-fstab-and-port.patch [6]https://dev.openwrt.org/attachment/ticket/5636/0006--package-base-files- some-lib-network-config.sh-re.patch -- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [patch] create typical OpenWrt image for WRT350N v2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Signed-off-by: Matthias Bücher -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkp6rhYACgkQUXXT+9wZdbX+DwCePJSxS1QV3KhC9ktRzCb3gBTM j+gAoL9CI5wmlUoOUEBdvc+RI0s5YZYg =FFtp -END PGP SIGNATURE- Index: target/linux/orion/image/Makefile === --- target/linux/orion/image/Makefile (revision 17139) +++ target/linux/orion/image/Makefile (working copy) @@ -48,7 +48,11 @@ endef define Image/Build/Linksys -# placeholder for the WRT350N v2 + ( \ + dd if=$(KDIR)/$(2)-uImage bs=1024k conv=sync; \ + dd if=$(KDIR)/root.$(1) bs=128k conv=sync; \ + ) > $(BIN_DIR)/openwrt-$(2)-$(1).img +# ToDo: WRT350N v2 webupgrade image endef define Image/Build/Freecom -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEABECAAYFAkp6rhYACgkQUXXT+9wZdbUUdQCaAmXg7Hdqv/FtmS0EnF5SwXA3 tsEAnixt0fXD1efw5PPXGzsLABzyvOk2 =L+c7 -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
