Packages updates - how to become a collaborator

Hey!

First thing first, if you have something off-topic to say, or you wanna wish me not to succeed, please send me a message. I promise I will not read it because I don't care. Please keep this thread on-topic and clean. Thanks.

I was testing and updated some packages, I will list them with the hashes so some developer can update them easily. And I could build an image and flash it to my router successfully. (Asus RT-AC88U)

How to become a collaborator in GitHub? cause I couldn't open pull request for my suggestion of removing the unnecessary package for 53xx router.

Here are the packages. I will write the name of the package, old version, new version, the hash consecutively. (some packages are already updated in the feeds but not the course code)

7z	24.05 > 24.08	aa04aac906a04df59e7301f4c69e9f48808e6c8ecae4eb697703a47bfb0ac042
autoconf(in the feeds only	2.71 > 2.72	afb181a76e1ee72832f6581c0eddf8df032b83e2e0239ef79ebedc4467d92d6e
automake (in the feeds only)	1.16.5 > 1.17	397767d4db3018dd4440825b60c64258b636eaf6bf99ac8b0897f06c89310acd
bash	5.2.21 > 5.2.32	d3ef80d2b67d8cbbe4d3265c63a72c46f9b278ead6e0e06d61801b58f23f50b5
binutils	2.42> 2.43.1	13f74202a3c4c51118b797a39ea4200d3f6cfbe224da6d1d95bb938480132dfd
ccache 4.10 > 4.10.2	d90514fff15943a8607e84e3f42d45f823915a92f99984f3fc88202f6295d1e8
e2sfsprogs	1.47.0 > 1.47.1	0d2e0bf80935c3392b73a60dbff82d8a6ef7ea88b806c2eea964b6837d3fd6c2
gawk	5.3.0 > 5.3.1	694db764812a6236423d4ff40ceb7b6c4c441301b72ad502bb5c27e00cd56f78
gdb	14.1> 15.1	38254eacd4572134bca9c5a5aa4d4ca564cbbd30c369d881f733fb6b903354f2
gdbm	1.23 > 1.24	695e9827fdf763513f133910bc7e6cfdb9187943a4fec943e57449723d2b8dbf
gnunet 0.21.2 > .022.0	fd39730b904b9933f78d3b4b8e81da3239d4796ca105e4644739c67e4be071d9
gnunet-fuse	0.21 > .022.0	1090fa224507b0afdea943989e0855a7d9af550c89bdc3892c672221116b4ef3
libmicrohttpd	0.9.77 > 1.0.1	a89e09fc9b4de34dde19f4fcb4faaa1ce10299b9908db1132bbfa1de47882b94
lz4	1.9.4 > 1.10.0	537512904744b35e232912055ccf8ec66d768639ff3abe5788d90d792ec5f48b
mtools	4.0.43 > 4.0.44	37dc4df022533c3d4b2ec1c78973c27c7e8b585374c2d46ab64c6a3db31eddb8
nettle	3.9.1 > 3.10	b4c518adb174e484cb4acea54118f02380c7133771e7e9beb98a0787194ee47c
screen	4.9.1 > 5.0.0	f04a39d00a0e5c7c86a55338808903082ad5df4d73df1a2fd3425976aed94971
squashfs3-lzma	3.0 > 3.4	9ea1a9b3bd4f387ca11b5e96f00f8ae996fb81c4c7ad41f7c7f359917628a339
xz	5.4.6 > 5.6.2	e12aa03cbd200597bd4ce11d97be2d09a6e6d39a9311ce72c91ac7deacde3171
zile 2.3.24 > 2.6	77eb7daff3c98bdc88daa1ac040dccca72b81dc32fc3166e079dd7a63e42c741

how are these two parts related to each other ?

https://openwrt.org/meta/infobox/upgrade_packages_warning

Patience, my friend, somebody will take on surveying that bcm usb firmware's actual usage and doing your way. Breaking dozen devices accidentally is not exactly a good start for first contribution.

1 Like

You become a member of github and then you make a PR and start the review process and if you are lucky it will en up as a commit.

But you can’t do a PR from github webbpage or a windows computer github app.
You must in practical terms use git in a linux terminal to do a PR in github, in order to be able to do the preparation tasks like rebasing etc required to make it a working commit.

3 Likes

You need to fork main repository, then branch , then add your changes in a branch, then add,commit,push and complete pull request in github web interface.

2 Likes

And that also…making a pr was a lot harder than I thought first time.
And then we have the “first check”. Where everyone fails on signature protocol the first time.
And the commit headline must be meaningful and start with the object!

2 Likes

And for every adjustment the whole process must be repeated, every time.

2 Likes

This section is for developers!

@brada4 @flygarn12 I am using a browser I don't have the github app. There was no way to submit a pr using the browser?

Any way here is the proof of the build image!


Off-topic, but I will reply. Removing a firmware ware for USB WiFi chip on PCIE WiFi router will not brick the device.

Hi, can you explain a few things to better understand what you are trying to do?

What packages do you plan on removing, are you trying to remove them from the default built image or from the target completely? If you are planning to do the former (update the build script), then sure, you probably won't break other devices. If you are planning to do the latter then I'm not sure anyone will be for it as it will remove functionality that already exists for people using it and will need a really good reason.

In the updates list, some updates are for new revisions, some for new minor versions while some are for new major versions:

  • you should request updates for the packages individually or for related packages at once: 7z and bash don't have anything to do with each other
  • for major version updates, you probably need to test for regressions yourself and listing them before making a request
  • for example, xz is intentionally left at 5.4.6 for now because of the whole Jia Tan situation, and this is one example reason why every non-related package needs to be updated with separate request - to be reviewed individually

Generally I think now is a good time to request updates as I believe main developers will soon decide to branch 24.x since all targets now finally use linux 6.6.

@zekica -

There is a really long thread where the OP discusses a package they wish to remove. They have a test with exactly one device and want to create a PR that eliminates it from an entire family of devices.

A developer who is familiar with the chipsets in question needs to weigh in as an authoritative voice in the matter.

With that said, let's simply keep this thread about providing the OP the information necessary to create a PR and not rehash the previous discussion. Once submitted, it will be in the hands of the devs.

4 Likes

the backdoor was removed in xz 5.6.2, in the feeds it is already 5.6.2 (the router will se this version using okpg update) except in the source code it is still 5.4.6, when compiling 2 versions will be compiled.

You have to read the answers you get. If you don’t want to read instructions and answers you will have a very long way ahead to go to get this working.

1 Like

I read it, let me be more specific.

I forked, I made the changes, I wrote the pr, then I got a message that I have to be collaborator. There was no way to add without been invited as a collaborator!

Your patch removes globally support for broadcom USB wifi sticks

Off-topic: but no, it will remove the driver for these 2 specific usb chips, and they can be install later when inserting a USB wifi adapter with these 2 specific usb chips

Nope, you remove USB support from the driver, not firmware dependency of driver.

What are you talking about? I tested with my router and it worked just fine. It is working now without that package. Please stop.

Please post the complete terminal output of your PR work.

And from what repository to what repository are you actually trying to make a PR?