Reminder: GSoC 2021 - Update or add your ideas
Hi there, as I already wrote we're going to apply again as organization for Google Summer of Code in 2021. I just want to remind you to update your project ideas or add some new ones. Deadline for applications is February 14, at this point your ideas should be up to date, too! To do so please submit a pull request at https://github.com/freifunk/projects.freifunk.net-contents You'll see the ideas at https://projects.freifunk.net Please keep in mind that starting from this year, the project size is smaller, student should work on it a total of 175 hours, instead of 350 hours before. See https://google.github.io/gsocguides/mentor/#program-structure for details. Moneyquote: For 2021 there is increased flexibility in the planning for the milestones - students have 10 weeks to complete their 175 hour project. This opens it up for the student and mentor to decide together how they want to break up the project. Some folks may choose to stick to a 17-18 hour a week schedule with their students, others may factor in a couple of breaks during the program (for student and mentor) and some may have students focus 30 hours a week on their project so they wrap up in 6 weeks. Best regards, Andi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCHv3 1/3] base-files: use hwclock --systz
Rosen Penev kirjoitti 1.2.2021 klo 2.15:
The date -k patch is non standard and will be removed in the next
commit.
...
--- a/package/base-files/files/etc/init.d/system
+++ b/package/base-files/files/etc/init.d/system
@@ -27,7 +27,7 @@ system_config() {
ln -sf "/usr/share/zoneinfo/$zonename" /tmp/localtime && rm -f
/tmp/TZ
# apply timezone to kernel
- busybox date -k
+ hwclock -u --systz
As discussed in connection of the musl update PR ( starting from
https://github.com/openwrt/openwrt/pull/3004#issuecomment-764479005 ), the
addition of "-u" to the hwclock options seems to fix the strange timestamps
in early boot system logs that I noticed earlier.
I think that in the current form the busybox update to 1.33.0 works ok. I
have been using it in my own builds since early January for ath79/WNDR3700,
ipq806x/R7800 and mvebu/WRT3200ACM.
Would be great to have it in the tree before the 21.0x branching.
PS. this patch series is already actually v4, as patch v3 was sent on 7 Jan
2021.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Backporting opkg fixes to 19.07
On Sun, Jan 31, 2021 at 19:10, Baptiste Jonglez wrote: Hi, I've just pushed this to my (brand new) staging tree: https://git.openwrt.org/?p=openwrt/staging/zorun.git;a=shortlog;h=refs/heads/openwrt-19.07 If there are no objections, I will merge that in a couple of days. Thanks for the backport! Please merge it. Baptiste On 24-01-21, Baptiste Jonglez wrote: Hi, I would like to backport the opkg fix for https://bugs.openwrt.org/index.php?do=details&task_id=2690 to 19.07. The opkg package in 19.07 is a bit old, it's using: f2166a8 libopkg: implement lightweight package listing logic Since there were several other changes in opkg master, I would create a new openwrt-19.07 branch in opkg based on f2166a8, and backport these commits: 61b3c62 opkg_verify_integrity: better logging and error conditions f73d42f download: purge cached packages that have incorrect checksum 1c1480e download: factor out the logic for building cache filenames 293b1ce libopkg: factor out checksum and size verification a786e25 download: remove compatibility with old cache naming scheme And maybe also this fix for another issue: 66f458d libopkg: fix md5sum calculation As far as I can tell, it shouldn't cause issues such as ABI breakage, but I prefer if somebody can double-check... Thanks, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
