OpenWrt Forum Archive

Topic: Transition period between old packages feed and new packages feed

The content of this topic has been archived on 1 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi all,

As you probably noticed, we recently moved the packages feed that was at http://git.openwrt.org/packages.git to a github hosted packages repository at the following address: https://github.com/openwrt/packages

The rationale behind that moved have been explained by Steven in this email: https://lists.openwrt.org/pipermail/ope … 25810.html

In order to allow for a smooth transition, we will keep the old and new package feeds enabled at the same time for a grace period of 3 weeks, that will end on the 2nd of July 2014, such that we allow any package maintainer to progressively move the packages from the old feed to the new feed.

ok,早一點出聲呀,我以為倒閉了

後來發覺全新下載命令更改成為:
1.     "git clone git://git.openwrt.org/openwrt.git"
2.     "git clone git://github.com/openwrt/packages.git"
3.     "cd openwrt;git pull;./scripts/feeds update -a;./scripts/feeds install -a"
4.     "cd..;mv packages ./openwrt/feeds/
5.     "cd openwrt;./scripts/feeds update -a;./scripts/feeds install -a"

sorry,佔了位置了.........

(Last edited by k25c2yf on 11 Jun 2014, 23:49)

那麼以後"svn up"更新源碼不能用了,取代的命令是:"git pull"

Thank you for this florian as I was wondering where quite a lot of packages had vanished to when running the scripts to update them all just a few hours ago.  I'm looking to do some full feature builds especially now that it looks like sysupgrade support is enabled for at least the WNDR4300 (Netgear) routers.

The grace period ended. Every day the oldpackages feed stays active can be considered your lucky day :-)

How does one move a package from git.openwrt.org to GitHub? Is a pull request on GitHub sufficient, and if so who will commit the deletion on git.openwrt.org?

florian_ wrote:

In order to allow for a smooth transition, we will keep the old and new package feeds enabled at the same time for a grace period of 3 weeks, that will end on the 2nd of July 2014, such that we allow any package maintainer to progressively move the packages from the old feed to the new feed.

The three weeks have gone and oldpackages is still enabled by default.

Will oldpackages be disabled in feeds.conf.default soon?
Or have your plans changed, e.g. oldpackages to be removed after BB branching after rc2 ?

roger_ wrote:

How does one move a package from git.openwrt.org to GitHub? Is a pull request on GitHub sufficient, and if so who will commit the deletion on git.openwrt.org?

I would like to know the answer to this question, as well. Anyone?

Trying to answer although I am not a core OpenWrt developer. Not sure if everything is correct, but appears to have worked for me when I tried to get the madplay package from oldpackages into trunk again:

Install trunk SDK

cat feeds.conf.default | sed 's/#src-git oldpackages/src-git oldpackages/' > feeds.conf

./scripts/feeds update oldpackages

./scripts/feeds install madplay

make

On GitHub, clone the openwrt/packages repository
On GitHub, make a new branch
On the new branch, add the Makefile for the package

Add the following fields to the Makefile (of course you might have to change the values according to the upstream source; PKG_MAINTAINER is you):

PKG_LICENSE:=GPL-2.0+
PKG_LICENSE_FILES:=COPYING
PKG_MAINTAINER:=My Name <name@domain.tld>

IMPORTANT:
The commit message needs to start with the package name, followed by a ":", e.g.:
madplay: Create Makefile
The commit message needs to have the following comment:
Signed-off-by: My Name <name@domain.tld>

On GitHub, create a pull request

Title:
madplay: import from old packages feed

Watch the pull request you made, e.g.,:
https://github.com/openwrt/packages/pull/817

Possibly it is a good idea to stay around in #openwrt-devel on irc.freenode.net

Once it is merged, you can delete your branch.

NOTE: If you forgot to add the Signed-off-by comment in your commit message, then you need to follow https://help.github.com/articles/changi … t-message/ to rewrite your commit message.

(Last edited by probono on 24 Jan 2015, 17:47)

The discussion might have continued from here.