You are not logged in.
Hi @all,
i build and pushed some AUR packages, but unfortunately had to delete some. This was no problem at all, because the delete request was accepted immediately.
However, as i want to publish the package again, after "git clone" i get my old crap again. I don't want to take a new package name.
So how long does AUR servers hold those "deleted" git trees in place or can i do something about it?
Thank you!
Offline
Why would you expect the content to be gone? Why does it matter, just make the changes, commit, and push, and your new PKGBUILD will overwrite the old one. If there are patches or other files you just want gone, `git rm` them.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Thank you for this quick reply.
The problem with that "old" data is my real name in the commits. I was stupid enough to forget about "git config user.name". It looks like there is no way of removing the git commit history - even when the package is actually deleted in the AUR.
Offline
It looks like there is no way to do so? Did you search at all? I just did a websearch for "git remove history" and these were two of the first results:
https://git-scm.com/book/en/v2/Git-Tool … ng-History
https://help.github.com/articles/remove-sensitive-data/
Much more is possible than one might initially imagine, but generally only when they ask the question they actually are looking for the answer to.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
>Did you search at all? I just did a websearch for "git remove history" and these were two of the first results:
Hmm. Yes i dit. But nothing worked. So i choosed to delete the package.
>https://help.github.com/articles/remove-sensitive-data/
This is about removing Files, not sensitive info from the commit history. This just not seem to work, as i have no access to the remote .git/ dir ..
>https://git-scm.com/book/en/v2/Git-Tool … ng-History
Oh yes, i had found this one before. It wont work. As it is written there: "[…] don’t amend your last commit if you’ve already pushed it". I tried it anyway
As for rebase, it reads: "Don’t include any commit you’ve already pushed to a central server […]", but i haven't tried this.
Last resort was "filter-branch". worked local like a charm. but when i tried to "git push", it refuses to work because the local HEAD is now older than the remote one. So "git pull" will merge them. But guess what: There it is. My old commit history with real name still visible.
After all research, i gave up. This was also what to expect, since https://bugs.archlinux.org/task/45425 claimed that it is not possible to undo this sort of privacy leak.
Offline
That bugreport also clearly states "Send an email to aur-support@archlinux.org if you have strong reasons for wanting to edit already pushed commits."
Because even if the TUs think you can't really prevent the privacy leak, they are committed to "give the users a possibility to minimize the degree of damage".
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline