Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google has stopped pushing Git tags for some Android source code

grapheneos.social

Post reply on HN
Print view View original

161–170 of 350 posts

Re: Google has stopped pushing Git tags for some Android source code

#161

Post by tannertech »

mvdtnz wrote: post #154
grapheneos wrote: post #105

Earlier quoted context omitted.

Yes, and we do mirror their source code on GitLab. We put the upstream 17 code in the 17-base branch and our code on top of it in the 17 branch: https://gitlab.com/grapheneos/kernel_pixel/-/tree/17-base https://gitlab.com/grapheneos/kernel_pixel_muzel/-/tree/17-b... We also have mirrors of the QPR1 Beta and QPR2 Beta code there too. It's not meant to be distributed as a tarball or a single Git repository. The build s…

[flagged]

Answered long ago: https://grapheneos.org/faq#future-devices

Re: Google has stopped pushing Git tags for some Android source code

#162

Post by thayne »

gruez wrote: post #103
spydum wrote: post #3

isn't this just malicious compliance? not clear how this would violate GPLv2?

My guess is that all their code is in their monorepo (google3), and they don't want to set up a tool to sync it to a public git repo, so the easiest way is just to have someone create a tarball on demand.

But google already built a tool to do exactly that: https://github.com/google/copybara

Re: Google has stopped pushing Git tags for some Android source code

#163

Post by petre »

urbnspacecowboy wrote: post #120
aleph_minus_one wrote: post #85

Earlier quoted context omitted.

But after one person does this, the source code access is a solved problem.

No it's not, because "one person" has to keep sitting up and begging for access, every time there's a new release, over and over and over and over and over.

Maybe we colld getan AI agent to pester them with forms?

Re: Google has stopped pushing Git tags for some Android source code

#164

Post by thayne »

paxys wrote: post #21
demibabs wrote: post #17

Can someone explain what this means? Am not familiar with the terminology

Google uses libraries licensed under GPLv2 in Android (I’m not sure which specific part of Android the author is talking about), and so is required to make the full source code available for anyone to view. They previously used to publish release tag tarballs, but now require you to fill out a Google form and then (weeks later) will share the source with you on Google Drive.

Android is built on the linux kernel which uses GPLv2

Re: Google has stopped pushing Git tags for some Android source code

#166

Post by eredengrin »

RachelF wrote: post #118
cdrnsf wrote: post #60

Give them a few years and they'll only provide it by printing out a copy and mailing it to you.

Don't give them ideas!

Seriously, if we keep this up they'll be sending us pallets of punch cards before you know it.

Re: Google has stopped pushing Git tags for some Android source code

#167

Post by nikanj »

geokon wrote: post #160
grapheneos wrote: post #105

Earlier quoted context omitted.

Yes, and we do mirror their source code on GitLab. We put the upstream 17 code in the 17-base branch and our code on top of it in the 17 branch: https://gitlab.com/grapheneos/kernel_pixel/-/tree/17-base https://gitlab.com/grapheneos/kernel_pixel_muzel/-/tree/17-b... We also have mirrors of the QPR1 Beta and QPR2 Beta code there too. It's not meant to be distributed as a tarball or a single Git repository. The build s…

Maybe a naiive question, but couldn't you request the source code from phone companies? Say you request it from Xiaomi - sure they're not the original writers of the code, but they too "distributing GPL code" and therefore must release the code on request. They may be more amenable to your request since they have leverage with Google and are in an adversarial relationship

You can request anything from anyone, but compelling a company to follow their GPL obligations requires cooperation from the copyright holders + infinite funds for legal fees

Re: Google has stopped pushing Git tags for some Android source code

#168

Post by grapheneos »

hedora wrote: post #126
TheMiddleMan wrote: post #47

Relevant: https://keepandroidopen.org/ > Starting in 2027*, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.

Any word as to whether this will apply to GrapheneOS? If I had to choose, I'd block apps that did comply with this BS.

It doesn't apply to GrapheneOS.

Google's upcoming change means Google Mobile Services operating systems will show a warning for apps from unverified developers. Bypassing the warning will require a one-time 24 hour wait via the regular user interface. It can be immediately bypassed using Android Debug Bridge instead.

Developers with Play Store apps are already verified. It's counterproductive for app developers with existing Play Console accounts considered verified to refuse to register their apps distributed outside of the Play Store. That would encourage users to stick to the Play Store.

The problem is for developers without a Play Console account who would need to register and verify their identify to avoid their apps showing a warning. If people are already registered, they might as well list their apps distributed outside the Play Store to avoid the warning.

Re: Google has stopped pushing Git tags for some Android source code

#169

Post by rbits »

hedora wrote: post #126
TheMiddleMan wrote: post #47

Relevant: https://keepandroidopen.org/ > Starting in 2027*, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.

Any word as to whether this will apply to GrapheneOS? If I had to choose, I'd block apps that did comply with this BS.

> Any word as to whether this will apply to GrapheneOS? If I had to choose, I'd block apps that did comply with this BS.

I doubt it, considering Android developer verification will go through Google Play Services, which GrapheneOS has siloed off from most of the OS as far as I'm aware.

Post reply on HN