[aur-general] AUR 4.0.0 pre-alpha
The 4.0.0 release brings Git repositories to AUR packages. You can test a pre-alpha version at aur-dev.archlinux.org [1]. In order to submit packages, you can follow these steps: 1. Create a new SSH key pair for the AUR. While this step is not strictly necessary (you can use any existing SSH key), it is recommended to do this: $ ssh-keygen -f ~/.ssh/id_rsa-aur 2. Log into the AUR web interface at [1], go to "My Account" and copy the content of ~/.ssh/id_rsa-aur.pub (or any other key you want to use) into the "SSH Public Key" field. Click "Update" to save the key. 3. The SSH daemon for the AUR uses a custom user and a custom port. It is recommended to add the following lines to your ~/.ssh/config so you don't need to specify user and port each time you connect to the AUR SSH interface: Host aur-dev.archlinux.org IdentityFile ~/.ssh/id_rsa-aur User aur Port 2222 4. To create a new (empty) package base foobar, run the following command: $ ssh aur-dev.archlinux.org setup-repo foobar 5. If you want to submit changes to a package base, you need to clone the package repository via SSH: $ git clone ssh+git://aur-dev.archlinux.org/foobar.git/ When making changes to the repository, make sure you always include the PKGBUILD and .SRCINFO in the top-level directory. You can submit new versions of a package base to the AUR by committing the new PKGBUILD and .SRCINFO and running `git push`. If you spot any major flaws or have suggestions for the new interface, please let me know. Regards, Lukas [1] https://aur-dev.archlinux.org/
Will all existing AUR packages automatically get their own git repositories or will we have to resubmit all packages? On Mon, Dec 29, 2014 at 4:01 PM, Lukas Fleischer <archlinux@cryptocrack.de> wrote:
The 4.0.0 release brings Git repositories to AUR packages. You can test a pre-alpha version at aur-dev.archlinux.org [1]. In order to submit packages, you can follow these steps:
1. Create a new SSH key pair for the AUR. While this step is not strictly necessary (you can use any existing SSH key), it is recommended to do this:
$ ssh-keygen -f ~/.ssh/id_rsa-aur
2. Log into the AUR web interface at [1], go to "My Account" and copy the content of ~/.ssh/id_rsa-aur.pub (or any other key you want to use) into the "SSH Public Key" field. Click "Update" to save the key.
3. The SSH daemon for the AUR uses a custom user and a custom port. It is recommended to add the following lines to your ~/.ssh/config so you don't need to specify user and port each time you connect to the AUR SSH interface:
Host aur-dev.archlinux.org IdentityFile ~/.ssh/id_rsa-aur User aur Port 2222
4. To create a new (empty) package base foobar, run the following command:
$ ssh aur-dev.archlinux.org setup-repo foobar
5. If you want to submit changes to a package base, you need to clone the package repository via SSH:
$ git clone ssh+git://aur-dev.archlinux.org/foobar.git/
When making changes to the repository, make sure you always include the PKGBUILD and .SRCINFO in the top-level directory. You can submit new versions of a package base to the AUR by committing the new PKGBUILD and .SRCINFO and running `git push`.
If you spot any major flaws or have suggestions for the new interface, please let me know.
Regards, Lukas
On Mon, 29 Dec 2014 at 22:16:45, Ido Rosen wrote:
Will all existing AUR packages automatically get their own git repositories or will we have to resubmit all packages? [...]
Both. The current plan is as follows: A couple of weeks before the official release of 4.0.0, I will reset the setup on aur-dev.archlinux.org and create an empty Git repository for each package that exists in the AUR at that moment. The package maintainer will be retained so that nobody can take over anybody else's package. AUR package maintainers are then asked to upload their packages to aur-dev.archlinux.org and co-maintain them on aur.archlinux.org and the Git repository on aur-dev.archlinux.org for some time (roughly four weeks). Users who have already been using Git for their AUR packages can add .SRCINFO to all commits and import the whole history. At some point in time, I am going to remove all package bases that have not been uploaded to aur-dev.archlinux.org and move everything from aur-dev.archlinux.org to aur.archlinux.org. It is a huge AUR cleanup.
On Mon, 29 Dec 2014 22:28:04 +0100 Lukas Fleischer <archlinux@cryptocrack.de> wrote:
It is a huge AUR cleanup.
Which means we should start saving PKGBUILDS of the dependences of our packages too, in case they don't make it, so we can reupload them… -- Νῖκος Θεοδώρου «Ἀγεωμέτρητος μηδεὶς εἰσίτω!»
On Mon, 29 Dec 2014 at 22:52:18, Νῖκος Θεοδώρου wrote:
On Mon, 29 Dec 2014 22:28:04 +0100 Lukas Fleischer <archlinux@cryptocrack.de> wrote:
It is a huge AUR cleanup.
Which means we should start saving PKGBUILDS of the dependences of our packages too, in case they don't make it, so we can reupload them… [...]
Just to clarify: There will be an archive of PKGBUILDs from the "old AUR". You can always recover packages if the maintainer doesn't upload them within the four weeks.
On Mon, 29 Dec 2014 23:05:28 +0100 Lukas Fleischer <archlinux@cryptocrack.de> wrote:
On Mon, 29 Dec 2014 at 22:52:18, Νῖκος Θεοδώρου wrote:
On Mon, 29 Dec 2014 22:28:04 +0100 Lukas Fleischer <archlinux@cryptocrack.de> wrote:
It is a huge AUR cleanup.
Which means we should start saving PKGBUILDS of the dependences of our packages too, in case they don't make it, so we can reupload them… [...]
Just to clarify: There will be an archive of PKGBUILDs from the "old AUR". You can always recover packages if the maintainer doesn't upload them within the four weeks.
Thanks. -- Νῖκος Θεοδώρου «Ἀγεωμέτρητος μηδεὶς εἰσίτω!»
On 29/12, Lukas Fleischer wrote:
AUR package maintainers are then asked to upload their packages to aur-dev.archlinux.org and co-maintain them on aur.archlinux.org and the Git repository on aur-dev.archlinux.org for some time (roughly four weeks).
Speaking of co-maintainership, any thoughts having multiple users being able to maintain the same package? -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
On Tue, 30 Dec 2014 at 02:34:14, Johannes Löthberg wrote:
On 29/12, Lukas Fleischer wrote:
AUR package maintainers are then asked to upload their packages to aur-dev.archlinux.org and co-maintain them on aur.archlinux.org and the Git repository on aur-dev.archlinux.org for some time (roughly four weeks).
Speaking of co-maintainership, any thoughts having multiple users being able to maintain the same package? [...]
Yes, that is a feature that will definitely be added before 4.0.0 will be released.
On Mon, Dec 29, 2014 at 10:01:45PM +0100, Lukas Fleischer wrote:
If you spot any major flaws or have suggestions for the new interface, please let me know.
I see that the submit button has been removed since uploads are now handled through git. Perhaps a "Create Package" button could be added in its place, which creates an empty repository and gives instructions on how to upload to it. Anyway, I liked the idea of using git for AUR packages when I first saw that someone had suggested it, and I'm glad its finally coming.
On Mon, 29 Dec 2014 at 23:26:38, wrote:
On Mon, Dec 29, 2014 at 10:01:45PM +0100, Lukas Fleischer wrote:
If you spot any major flaws or have suggestions for the new interface, please let me know.
I see that the submit button has been removed since uploads are now handled through git. Perhaps a "Create Package" button could be added in its place, which creates an empty repository and gives instructions on how to upload to it.
You can create an empty repository via SSH: $ ssh aur-dev.archlinux.org setup-repo foobar I agree that it is a good idea to add instructions on how to submit packages, though.
Anyway, I liked the idea of using git for AUR packages when I first saw that someone had suggested it, and I'm glad its finally coming.
On Mon, Dec 29, 2014 at 11:36:58PM +0100, Lukas Fleischer wrote:
You can create an empty repository via SSH:
$ ssh aur-dev.archlinux.org setup-repo foobar
I agree that it is a good idea to add instructions on how to submit packages, though.
That works, but I think it would be nice to also have a button in the web interface. Something similar to how you create a repository on github. You click the button, it asks you for a package name and category, and then it explains how to upload. That said, I currently upload packages with burp and probably wouldn't use such an interface. It just seems like a nice thing to have, and would make it easier for new users. (Of course, making it a little difficult could be used as a way to filter out incompetent maintainers, which is not a bad idea.)
But if someone missed the deadline (something that I'm sure will happend for a few hundeds at least either because lazines, bussyness or not want (or can't) reach aur-dev page) there are a place to take the PKGBUILD that was deleted in the "lets break AUR" cleanup? Also translations need to be pulled, the last time the translation weren't taken from transfex (as I can noticed) and viceversa, so why not let the submit button there but intead add the instructions on how now upload packages to aur. 2014-12-29 19:48 GMT-03:00 Ian D. Scott <ian@perebruin.com>:
On Mon, Dec 29, 2014 at 11:36:58PM +0100, Lukas Fleischer wrote:
You can create an empty repository via SSH:
$ ssh aur-dev.archlinux.org setup-repo foobar
I agree that it is a good idea to add instructions on how to submit packages, though.
That works, but I think it would be nice to also have a button in the web interface. Something similar to how you create a repository on github. You click the button, it asks you for a package name and category, and then it explains how to upload.
That said, I currently upload packages with burp and probably wouldn't use such an interface. It just seems like a nice thing to have, and would make it easier for new users. (Of course, making it a little difficult could be used as a way to filter out incompetent maintainers, which is not a bad idea.)
-- *Pablo Lezaeta*
mmm fails for me refuses upload because "remote: error: missing .SRCINFO" but that file is include in the root of the repository i missing steps? I use: - git clone ssh+git://aur-dev.archlinux.org/foobar.git/ (change foobar with the package name) - add PKGBUILD. SRCINFO and other files include in the sources array - git add . - git commit -m 'brawbraw' - git push greetings 2014-12-30 0:01 GMT+01:00 Pablo Lezaeta Reyes <prflr88@gmail.com>:
But if someone missed the deadline (something that I'm sure will happend for a few hundeds at least either because lazines, bussyness or not want (or can't) reach aur-dev page) there are a place to take the PKGBUILD that was deleted in the "lets break AUR" cleanup?
Also translations need to be pulled, the last time the translation weren't taken from transfex (as I can noticed) and viceversa, so why not let the submit button there but intead add the instructions on how now upload packages to aur.
2014-12-29 19:48 GMT-03:00 Ian D. Scott <ian@perebruin.com>:
On Mon, Dec 29, 2014 at 11:36:58PM +0100, Lukas Fleischer wrote:
You can create an empty repository via SSH:
$ ssh aur-dev.archlinux.org setup-repo foobar
I agree that it is a good idea to add instructions on how to submit packages, though.
That works, but I think it would be nice to also have a button in the web interface. Something similar to how you create a repository on github. You click the button, it asks you for a package name and category, and then it explains how to upload.
That said, I currently upload packages with burp and probably wouldn't use such an interface. It just seems like a nice thing to have, and would make it easier for new users. (Of course, making it a little difficult could be used as a way to filter out incompetent maintainers, which is not a bad idea.)
-- *Pablo Lezaeta*
On Tue, 30 Dec 2014 at 00:12:06, SpinFlo wrote:
mmm fails for me
refuses upload because "remote: error: missing .SRCINFO"
but that file is include in the root of the repository
i missing steps?
I use:
- git clone ssh+git://aur-dev.archlinux.org/foobar.git/ (change foobar with the package name) - add PKGBUILD. SRCINFO and other files include in the sources array
Just to clarify: The file is called .SRCINFO (note the leading dot). If it still fails, could you please push to another public repository and send me a link in a private email so I can investigate the issue?
- git add . - git commit -m 'brawbraw' - git push [...]
I'd like to chime in. I'm in the same boat as SpinFlo. Only thing I did differently is add PKGBUILD in one commit, attempt to push, then added .SRCINFO in another commit. Cheers. -- David Phillips GPG Key 0x7BF3D17D0884BF5B Fingerprint 2426 235A 7831 AA2F 56AF 4BC0 7BF3 D17D 0884 BF5B
On Tue, 30 Dec 2014 at 00:22:53, David Phillips wrote:
I'd like to chime in. I'm in the same boat as SpinFlo. Only thing I did differently is add PKGBUILD in one commit, attempt to push, then added .SRCINFO in another commit. [...]
Oh, every commit needs to refer to a tree object that contains a .SRCINFO file. The idea is that every commit corresponds to a revision of the package and must provide meta data for that revision. You can use `git commit --amend` or `git rebase -i` if you forgot to add meta data to any local commit. I am open for suggestions on how to improve this.
One little question. is possible add a .gitignore from the local repo? is for not duplicate my repository, one for clean files and other for working (with sources and SRC/PKG directory and others) in that .gitignore contains something like this: *.xz *.7z *.zip ... *. <put here the extension of package source> /src /pkg /<name of the repo if use a git/svn/hg> etc etc or exist a method to use white list (only files/directory allowed) instead of blacklist (list of exclude dirs/files) greetings
2014-12-30 0:52 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
or exist a method to use white list (only files/directory allowed) instead of blacklist (list of exclude dirs/files)
greetings
oh, i fount it: http://stackoverflow.com/questions/15288712/gitignore-whitelist-on-directory... greetings
2014-12-30 0:57 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
2014-12-30 0:52 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
or exist a method to use white list (only files/directory allowed) instead of blacklist (list of exclude dirs/files)
greetings
oh, i fount it: http://stackoverflow.com/questions/15288712/gitignore-whitelist-on-directory...
greetings
ok i tried test with a .gitignore (do'h, 'git add *' don't work again. but use 'git add .gitignore' works :/) with this content: * !.gitignore !.SRCINFO !PKGBUILD !somefile.desktop !somefile.patch !someimage.png !sometextfile.ext then added the package sources and dozens of files. 'git add *' says that files are ignored, included the src/pkg dirs(and contents) i'm sure this is a best chice to avoid the duplicate local repos (one to work, and other to clean push) greetings
but what if the file not contain any extention? or if a different file is need (like a .svg or a .sh or a .webm? We will ended adding all the posibilities for images? or there will be an alternat8but is need to installive if a user need update a package with anything that is not in the whitelist withut ended renaming it at makepkg time. Maybe if a user need add a exeption they can contact the mailist for ask about an exception to they blacklist in they git-sub-tree-whatever. 2014-12-29 22:14 GMT-03:00 SpinFlo <sl1pkn07@gmail.com>:
2014-12-30 0:57 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
2014-12-30 0:52 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
or exist a method to use white list (only files/directory allowed) instead of blacklist (list of exclude dirs/files)
greetings
oh, i fount it:
http://stackoverflow.com/questions/15288712/gitignore-whitelist-on-directory...
greetings
ok i tried test with a .gitignore (do'h, 'git add *' don't work again. but use 'git add .gitignore' works :/) with this content:
* !.gitignore !.SRCINFO !PKGBUILD !somefile.desktop !somefile.patch !someimage.png !sometextfile.ext
then added the package sources and dozens of files. 'git add *' says that files are ignored, included the src/pkg dirs(and contents)
i'm sure this is a best chice to avoid the duplicate local repos (one to work, and other to clean push)
greetings
-- *Pablo Lezaeta*
On Tue, Dec 30, 2014 at 11:19 AM, Pablo Lezaeta Reyes <prflr88@gmail.com> wrote:
but what if the file not contain any extention? or if a different file is need (like a .svg or a .sh or a .webm? We will ended adding all the posibilities for images? or there will be an alternat8but is need to installive if a user need update a package with anything that is not in the whitelist withut ended renaming it at makepkg time. Maybe if a user need add a exeption they can contact the mailist for ask about an exception to they blacklist in they git-sub-tree-whatever.
2014-12-29 22:14 GMT-03:00 SpinFlo <sl1pkn07@gmail.com>:
2014-12-30 0:57 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
2014-12-30 0:52 GMT+01:00 SpinFlo <sl1pkn07@gmail.com>:
or exist a method to use white list (only files/directory allowed) instead of blacklist (list of exclude dirs/files)
greetings
oh, i fount it:
http://stackoverflow.com/questions/15288712/gitignore-whitelist-on-directory...
greetings
ok i tried test with a .gitignore (do'h, 'git add *' don't work again. but use 'git add .gitignore' works :/) with this content:
* !.gitignore !.SRCINFO !PKGBUILD !somefile.desktop !somefile.patch !someimage.png !sometextfile.ext
then added the package sources and dozens of files. 'git add *' says that files are ignored, included the src/pkg dirs(and contents)
i'm sure this is a best chice to avoid the duplicate local repos (one to work, and other to clean push)
greetings
-- *Pablo Lezaeta*
You can still force add them with 'git add -f foo.bar' But most smart shell auto completions won't work with it either which is a bit annoying. I use a blacklist, and it works for all of my packages, but I don't have anything pulling things like .deb sources or a million other possibilities; I think using a whitelist instead of a blacklist may be the way to go. Regards, Justin Dray E: justin@dray.be M: 0433348284
mmm, not detect the sources_i686/sources_x86_64 fields (pacman 4.2 new structure) https://aur-dev.archlinux.org/cgit/lsi-msm.git/tree/PKGBUILD greetings
ok. now fixed. i don't know why. bit in the first attempt 'git add *' and 'git add .' don't work ( That's because of how shell GLOBBING works. Use "git add --all" instead :-) Cheers! On Mon Dec 29 2014 at 7:36:30 PM SpinFlo <sl1pkn07@gmail.com> wrote:
mmm, not detect the sources_i686/sources_x86_64 fields (pacman 4.2 new structure)
https://aur-dev.archlinux.org/cgit/lsi-msm.git/tree/PKGBUILD
greetings
Is there currently a script to just create a .SRCINFO from a PKGBUILD? I don't want any side effects like downloading src packages (i.e. I don't want to run makepkg or mkaurball), etc. since this is for use in git filter-branch --tree-filter.
.SRCINFO, in my knowledge, is only generated by makepkg -S. (mkaurball is now deprecated)
On Mon, Dec 29, 2014 at 09:49:24PM -0500, Ido Rosen wrote:
Is there currently a script to just create a .SRCINFO from a PKGBUILD? I don't want any side effects like downloading src packages (i.e. I don't want to run makepkg or mkaurball), etc. since this is for use in git filter-branch --tree-filter.
There exists a tool in the pkgbuild-introspection git repo[1] which will write a .SRCINFO to standard output when given a PKGBUILD. Pull requests welcome to give it a better name (mksrcinfo?) and some UI. dR [1] https://github.com/falconindy/pkgbuild-introspection/blob/master/introspect
On Mon, Dec 29, 2014 at 10:21:17PM -0500, Dave Reisner wrote:
On Mon, Dec 29, 2014 at 09:49:24PM -0500, Ido Rosen wrote:
Is there currently a script to just create a .SRCINFO from a PKGBUILD? I don't want any side effects like downloading src packages (i.e. I don't want to run makepkg or mkaurball), etc. since this is for use in git filter-branch --tree-filter.
There exists a tool in the pkgbuild-introspection git repo[1] which will write a .SRCINFO to standard output when given a PKGBUILD. Pull requests welcome to give it a better name (mksrcinfo?) and some UI.
dR
[1] https://github.com/falconindy/pkgbuild-introspection/blob/master/introspect
Nevermind, this (mksrcinfo) now exists in pkgbuild-introspection-git. Bug reports welcome. dR
On Mon, Dec 29, 2014 at 11:00 PM, Dave Reisner <d@falconindy.com> wrote:
On Mon, Dec 29, 2014 at 10:21:17PM -0500, Dave Reisner wrote:
On Mon, Dec 29, 2014 at 09:49:24PM -0500, Ido Rosen wrote:
Is there currently a script to just create a .SRCINFO from a PKGBUILD? I don't want any side effects like downloading src packages (i.e. I don't want to run makepkg or mkaurball), etc. since this is for use in git filter-branch --tree-filter.
There exists a tool in the pkgbuild-introspection git repo[1] which will write a .SRCINFO to standard output when given a PKGBUILD. Pull requests welcome to give it a better name (mksrcinfo?) and some UI.
dR
[1] https://github.com/falconindy/pkgbuild-introspection/blob/master/introspect
Nevermind, this (mksrcinfo) now exists in pkgbuild-introspection-git. Bug reports welcome.
dR
Thanks. For now, I'm just copying and pasting this into my script rather than depending on pkgbuild-introspection-git. :-) See other thread (one git <-> AUR4 per package git repos) in a minute for the script contents.
Posted in other thread, but: The AUR4 update hook compares an str to an int when looking at the pkginfo['epoch'], so packages with an epoch set fail to pass the update hook. Probably should check that the string pkginfo['epoch'] contains only numbers, then do an int(pkginfo['epoch']) in the comparison line there... line 45 of save_srcinfo. Failed to setup-repo ceph-git ... maybe it already exists? + git push ssh+git://aur@aur-dev.archlinux.org:2222/ceph-git.git/ aur4/ceph-git:master Counting objects: 35, done. Delta compression using up to 8 threads. Compressing objects: 100% (25/25), done. Writing objects: 100% (35/35), 7.48 KiB | 0 bytes/s, done. Total 35 (delta 17), reused 14 (delta 10) remote: Traceback (most recent call last): remote: File "hooks/update", line 212, in <module> remote: save_srcinfo(srcinfo, db, cur, user) remote: File "hooks/update", line 45, in save_srcinfo remote: if 'epoch' in pkginfo and pkginfo['epoch'] > 0: remote: TypeError: unorderable types: str() > int() remote: error: hook declined to update refs/heads/master To ssh+git://aur@aur-dev.archlinux.org:2222/ceph-git.git/ ! [remote rejected] aur4/ceph-git -> master (hook declined) On Mon, Dec 29, 2014 at 11:15 PM, Ido Rosen <ido@kernel.org> wrote:
On Mon, Dec 29, 2014 at 11:00 PM, Dave Reisner <d@falconindy.com> wrote:
On Mon, Dec 29, 2014 at 10:21:17PM -0500, Dave Reisner wrote:
On Mon, Dec 29, 2014 at 09:49:24PM -0500, Ido Rosen wrote:
Is there currently a script to just create a .SRCINFO from a PKGBUILD? I don't want any side effects like downloading src packages (i.e. I don't want to run makepkg or mkaurball), etc. since this is for use in git filter-branch --tree-filter.
There exists a tool in the pkgbuild-introspection git repo[1] which will write a .SRCINFO to standard output when given a PKGBUILD. Pull requests welcome to give it a better name (mksrcinfo?) and some UI.
dR
[1] https://github.com/falconindy/pkgbuild-introspection/blob/master/introspect
Nevermind, this (mksrcinfo) now exists in pkgbuild-introspection-git. Bug reports welcome.
dR
Thanks. For now, I'm just copying and pasting this into my script rather than depending on pkgbuild-introspection-git. :-)
See other thread (one git <-> AUR4 per package git repos) in a minute for the script contents.
On Tue, 30 Dec 2014 at 05:39:28, Ido Rosen wrote:
Posted in other thread, but:
The AUR4 update hook compares an str to an int when looking at the pkginfo['epoch'], so packages with an epoch set fail to pass the update hook. Probably should check that the string pkginfo['epoch'] contains only numbers, then do an int(pkginfo['epoch']) in the comparison line there... line 45 of save_srcinfo. [...]
Fixed. Thanks for reporting!
Hi Howto remove a own repo (only make setup) if created with bad name? greetings
On Tue, 30 Dec 2014 at 15:46:18, SpinFlo wrote:
Hi
Howto remove a own repo (only make setup) if created with bad name?
Don't worry about it now -- I don't care about orphan packages in a testing environment. When AUR 4.0.0 goes live, you can file a package deletion request to delete a package. The Git repositories of deleted packages (and empty repositories that haven't had any commits for a long time) will be wiped periodically.
greetings
2014-12-30 16:22 GMT+01:00 Lukas Fleischer <archlinux@cryptocrack.de>:
Don't worry about it now -- I don't care about orphan packages in a testing environment. When AUR 4.0.0 goes live, you can file a package deletion request to delete a package. The Git repositories of deleted packages (and empty repositories that haven't had any commits for a long time) will be wiped periodically.
oh, thanks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 29 December 2014 23:31:03 GMT+00:00, Lukas Fleischer <archlinux@cryptocrack.de> wrote:
On Tue, 30 Dec 2014 at 00:22:53, David Phillips wrote:
I'd like to chime in. I'm in the same boat as SpinFlo. Only thing I did differently is add PKGBUILD in one commit, attempt to push, then added .SRCINFO in another commit. [...]
Oh, every commit needs to refer to a tree object that contains a .SRCINFO file. The idea is that every commit corresponds to a revision of the package and must provide meta data for that revision. You can use `git commit --amend` or `git rebase -i` if you forgot to add meta data to any local commit.
I am open for suggestions on how to improve this.
Maybe instead of creating an empty repository initiate a s default or empty .SRCINFO (and PKGBUILD)? This should prevent people from making similar mistakes, and provide them with a starting point. - -- "We apologize for the inconvenience" -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQJLBAEBCgA1BQJUoe/uLhxKb29zdCBCcmVtbWVyIChPbiBtb2JpbGUpIDx0b29z dC5iQGdtYWlsLmNvbT4ACgkQW+wCGFKbV01h+w//Xa8S1RulV7tWT2nBS6HtVLSx MGUV4h06OOTxCyGcrbjsmCdmloODVwRV2/f+3Ti/m96lsysTS6XYTOMXB7ivfjj7 j7cjU499TWYwWK2irFVCoqEJwqFzatxsIz4UHon3XGkegyedfxuwbCVoGx3Cc4HH J0JCmviHSbsdDTDBGTclm1pbrIXLDvxxxNcqeiEIxkku60VolueL6CXKKty6aZr4 4cr7tx1B2/vF4kd6se6Mt3/AB0UBAeBznEOuWIfOt6pmwARu6zKh5kjUz9nxQLH0 R+15hReo63YyoVnbNGDGig4xdTpJ8768fhBuwVvr69ljwIBBr261sBEVmaaRRSTh eyoZiAyuzcwSFiwYBBrsjezb+7AF9F7ffv9iX/HUF/9kRGghrZX43G90uRbrHqZ8 pOhWIPit2OgnIrObcvYl3X/JOf20PI10qAuk9yVTXb0c5gF28auytgv93VuvVsYv ZU8wU3VCDftEFtY14Vmv0OdV4C30+8ZiWFzImN3b4x19gscOxOPvSNgJzbJ5AQhx tt1SuPh26TofxoZnvq5pTXdeoXs5R0Vf3RysvW1NkpPaoNlIwTIJlD8wQwWxb7Yf VtqlbhFXYBxTK/LZKxv8SE0ES/VohAPAiCAWBbTqFai0fplk0cxNPFsYsoKlTV26 jtx6Czavo89qvgBcyb0= =0jAw -----END PGP SIGNATURE-----
ok. now fixed. i don't know why. bit in the first attempt 'git add *' and 'git add .' don't work (not added .SRCINFO file), I started over again and now it has worked my steps is little changed. because in my first attemp use 'git add *' (failed) instead of 'git add .' (like my first post, the 'git add .' is a second attemp)(failed again) - clone te remote repo - move the necesary files (make sure have .SRCINFO file in root of repo) - git add * - git commit -m 'message' - git push greetings
Thanks Lukas. I did try to rebase, but my git-foo isn't very remarkable. -- David Phillips GPG Key 0x7BF3D17D0884BF5B Fingerprint 2426 235A 7831 AA2F 56AF 4BC0 7BF3 D17D 0884 BF5B
* David Phillips <dbphillipsnz@gmail.com> (Tue, 30 Dec 2014 12:51:23 +1300):
Thanks Lukas. I did try to rebase, but my git-foo isn't very remarkable.
I hope this helps: https://help.github.com/articles/using-git-rebase/ Regards, Marcel
* Marcel Korpel <marcel.korpel@gmail.com> (Tue, 30 Dec 2014 01:01:00 +0100):
I hope this helps: https://help.github.com/articles/using-git-rebase/
BTW, I found git-uncommit [1] a useful tool, too. Regards, Marcel [1] https://github.com/rev22/git-uncommit
Hello Pablo, On Tue, 30 Dec 2014 at 00:01:05, Pablo Lezaeta Reyes wrote:
But if someone missed the deadline (something that I'm sure will happend for a few hundeds at least either because lazines, bussyness or not want (or can't) reach aur-dev page) there are a place to take the PKGBUILD that was deleted in the "lets break AUR" cleanup?
As I already mentioned in a reply to Νῖκος, it is possible to recover PKGBUILDs that have been deleted from an archive.
Also translations need to be pulled, the last time the translation weren't taken from transfex (as I can noticed) and viceversa, so why not let the submit button there but intead add the instructions on how now upload packages to aur. [...]
Are you talking about 3.5.1 or 4.0.0? The setup on aur-dev.archlinux.org is a pre-alpha release and thus, there aren't any translations yet.
2014-12-29 20:15 GMT-03:00 Lukas Fleischer <archlinux@cryptocrack.de>:
Hello Pablo,
But if someone missed the deadline (something that I'm sure will happend for a few hundeds at least either because lazines, bussyness or not want (or can't) reach aur-dev page) there are a place to take the PKGBUILD
On Tue, 30 Dec 2014 at 00:01:05, Pablo Lezaeta Reyes wrote: that
was deleted in the "lets break AUR" cleanup?
As I already mentioned in a reply to Νῖκος, it is possible to recover PKGBUILDs that have been deleted from an archive.
Well, I will look in that, but "never underestimate the ingenioty of complete fools as humans are" -My Boss-
Also translations need to be pulled, the last time the translation weren't taken from transfex (as I can noticed) and viceversa, so why not let the submit button there but intead add the instructions on how now upload packages to aur. [...]
Are you talking about 3.5.1 or 4.0.0? The setup on aur-dev.archlinux.org is a pre-alpha release and thus, there aren't any translations yet.
In days later from 3.4 release I noticed missing articles before Aur (as my language need them: "El AUR" [I ended consulting to the Fundéu fundation about that]) I fixed them, but ever now these aren't showed in the page. so, yeah, the .pot files are different from what is now in transifex and waht was for the 3.4.1 in transifex too. -- *Pablo Lezaeta*
* Lukas Fleischer <archlinux@cryptocrack.de> (Mon, 29 Dec 2014 22:01:45 +0100):
5. If you want to submit changes to a package base, you need to clone the package repository via SSH:
$ git clone ssh+git://aur-dev.archlinux.org/foobar.git/
When making changes to the repository, make sure you always include the PKGBUILD and .SRCINFO in the top-level directory. You can submit new versions of a package base to the AUR by committing the new PKGBUILD and .SRCINFO and running `git push`.
I followed all steps, cloned empty repository 'ctemplate' and did an initial commit, but git push failed: $ git push No refs in common and none specified; doing nothing. Perhaps you should specify a branch such as 'master'. fatal: The remote end hung up unexpectedly error: failed to push some refs to 'ssh+git://aur-dev.archlinux.org/ctemplate.git/' $ git push master fatal: 'master' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. $ git l * 73f44cb (HEAD, master) Initial commit 6 minutes ago What did I do wrong? Regards, Marcel
On 30/12, Marcel Korpel wrote:
$ git push master fatal: 'master' does not appear to be a git repository fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
You need to actually specify the remote too, named origin by default when you clone a repo, so `git push origin master` -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
* Johannes Löthberg <johannes@kyriasis.com> (Tue, 30 Dec 2014 01:22:24 +0100):
You need to actually specify the remote too, named origin by default when you clone a repo, so `git push origin master`
Now it works. Strange, as with other repositories `git push` just works, as 'origin' is the default. Regards, Marcel
On Tue, 30 Dec 2014 at 12:19:35, Marcel Korpel wrote:
* Johannes Löthberg <johannes@kyriasis.com> (Tue, 30 Dec 2014 01:22:24 +0100):
You need to actually specify the remote too, named origin by default when you clone a repo, so `git push origin master`
Now it works. Strange, as with other repositories `git push` just works, as 'origin' is the default.
`git push` should work. `git push master` does not work, though, because you cannot specify a refspec without specifying a remote repository.
Regards, Marcel
On Tuesday 30 December 2014 at 12:19:35, Marcel Korpel wrote:
* Johannes Löthberg <johannes@kyriasis.com> (Tue, 30 Dec 2014 01:22:24 +0100):
You need to actually specify the remote too, named origin by default when you clone a repo, so `git push origin master`
Now it works. Strange, as with other repositories `git push` just works, as 'origin' is the default.
There is such thing as `git branch --set-upstream-to` or `git push -u`. IOW, each branch has its "default upstream" -- or does not have it. Your case seems to be the latter. -- Ivan Shapovalov / intelfx /
If you just cloned a repo; master will have upstream set to origin/master. You should only have to set upstream when you create a new local branch. and if you do, you can use 'git push -u origin branch-name' to set it and push in one go. Regards, Justin Dray E: justin@dray.be M: 0433348284
for me need this after clone repository
'git add *' -> to add/update files to repo 'git commit -m 'message'' -> to add the commit to repo
and then push the changes
2014-12-29 21:30 GMT-03:00 SpinFlo <sl1pkn07@gmail.com>:
for me need this after clone repository
'git add *' -> to add/update files to repo 'git commit -m 'message'' -> to add the commit to repo
and then push the changes
There is a way to preven malicious userd that efectively create and acount and do al the stuf to only pload malware like a PKGBUILD, .SRCPKG and 1G patch x 10 or a giantic commit -sm "like copy pasting an entire book"?? -- *Pablo Lezaeta*
2014-12-30 1:50 GMT+01:00 Pablo Lezaeta Reyes <prflr88@gmail.com>:
There is a way to preven malicious userd that efectively create and acount and do al the stuf to only pload malware like a PKGBUILD, .SRCPKG and 1G patch x 10 or a giantic commit -sm "like copy pasting an entire book"??
-- *Pablo Lezaeta*
I belive have a any security like a if don't detect .SRCINFO file can't push the commits. but adapt if the file have a size or the number of files is huge
On Tue, 30 Dec 2014 at 01:50:55, Pablo Lezaeta Reyes wrote:
2014-12-29 21:30 GMT-03:00 SpinFlo <sl1pkn07@gmail.com>:
for me need this after clone repository
'git add *' -> to add/update files to repo 'git commit -m 'message'' -> to add the commit to repo
and then push the changes
There is a way to preven malicious userd that efectively create and acount and do al the stuf to only pload malware like a PKGBUILD, .SRCPKG and 1G patch x 10 or a giantic commit -sm "like copy pasting an entire book"??
Yes, we already reject huge files.
-- *Pablo Lezaeta*
participants (15)
-
Dave Reisner
-
David Phillips
-
Dustin Falgout
-
Ian D. Scott
-
ian＠perebruin.com
-
Ido Rosen
-
Ivan Shapovalov
-
Johannes Löthberg
-
Joost Bremmer
-
Justin Dray
-
Lukas Fleischer
-
Marcel Korpel
-
Pablo Lezaeta Reyes
-
SpinFlo
-
Νῖκος Θεοδώρου