On 23 May 2015 at 11:53, Florian Bruhin wrote:

I think the wiki should contain some information/hints on how to convert existing git repos (which might be without .SRCINFO) so they can be pushed to aur4. I think some while ago there was a script for that here on the ML?

At least I remember this post [ 0 ] and several more around those days containing scripts and discussions about the subject. For example this thread if you're already storing your packages in a git repo [ 1 ] Most of the discussion in this ML was focused IIRC late December 2014 to early January 2015. [ 0 ] https://lists.archlinux.org/pipermail/aur-general/2014-December/030051.html [ 1 ] https://lists.archlinux.org/pipermail/aur-general/2014-December/030021.html

Hi, Just a reminder that I wrote this script when this first came up to help maintainers who already maintain *multiple* packages in one git repo to split them into separate git repos, upload them individually to AUR4, etc.

https://github.com/ido/packages-archlinux/blob/master/bin/import-to-aur4.sh

Also, the link in your notification email is broken: Arch_User_Repository#Submitting_packages_to_aur-dev.archlinux.org should be Arch_User_Repository#Submitting_packages_to_aur4.archlinux.org

Cheers, Ido  

How does it handle repos where .SRCINFO weren't tracked in the past? When I used git subtree to split out one dir and tried to push that to aur-dev it complained about missing .SRCINFO in the latest commit. Amended .SRCINFO to the latest commit and the push to aur-dev complained again about missing .SRCINFO in the next commit after the latest. So I had the impression I would need to rewrite the whole history of all my maintained packages. But looking at your script it seems I misinterpret something from the error message back then, as the files just get created, but not added to the index? Best regards Lex

On Sat, 23 May 2015 11:53:24 +0200 Florian Bruhin wrote:

* Lukas Fleischer [2015-05-23 11:07:25 +0200]:

...

Hi,

I just added a section to the AUR article in the Arch wiki that describes how to submit packages to the new AUR. Here is a draft of the notification that I plan to send to all AUR package maintainers on June 1st: [...]

I think the wiki should contain some information/hints on how to convert existing git repos (which might be without .SRCINFO) so they can be pushed to aur4. I think some while ago there was a script for that here on the ML?

(Sorry for not doing that myself - I'm aware it's a wiki, but I'm a bit busy at the moment, so I'd appreciate if someone else could take care of that, if people agree with the idea)

Florian

I think the command you're looking for is git filter-branch --tree-filter mksrcinfo <branch> The scripts you referred to are for people who tracked all of their packages in a single git tree. Crazy, I know, but some people are stuck in subversion mode. Doug

On Sat, 23 May 2015 18:50:44 +0200 Florian Bruhin wrote:

* Doug Newgard [2015-05-23 11:14:28 -0500]:

...

On Sat, 23 May 2015 11:53:24 +0200 Florian Bruhin wrote:

...

* Lukas Fleischer [2015-05-23 11:07:25 +0200]:

...

Hi,

I just added a section to the AUR article in the Arch wiki that describes how to submit packages to the new AUR. Here is a draft of the notification that I plan to send to all AUR package maintainers on June 1st: [...]

I think the wiki should contain some information/hints on how to convert existing git repos (which might be without .SRCINFO) so they can be pushed to aur4. I think some while ago there was a script for that here on the ML?

(Sorry for not doing that myself - I'm aware it's a wiki, but I'm a bit busy at the moment, so I'd appreciate if someone else could take care of that, if people agree with the idea)

Florian

I think the command you're looking for is

git filter-branch --tree-filter mksrcinfo <branch>

The scripts you referred to are for people who tracked all of their packages in a single git tree.

That's actually the situation I'm in - but I guess the wiki should have some pointers for both cases.

...

Crazy, I know, but some people are stuck in subversion mode.

I disagree - I never used SVN and used git since about 5 years, but I really don't want to clutter my GitHub account and/or own git page with 37 repos, most of it only containing a single file.

Florian

Do you put all of your configs and other projects in the same repo? That would be cleaner, too, wouldn't it?

On 23/05/15, Troy Engel wrote:

On Sat, May 23, 2015 at 12:19 PM, Doug Newgard wrote:

...

On Sat, 23 May 2015 18:50:44 +0200 Florian Bruhin wrote:

...

I disagree - I never used SVN and used git since about 5 years, but I really don't want to clutter my GitHub account and/or own git page with 37 repos, most of it only containing a single file.

Do you put all of your configs and other projects in the same repo? That would be cleaner, too, wouldn't it?

I agree with Florian. His use case is the same as mine, I am an individual contributor to AUR and have no need for 37 different repositories when one repo with 37 subdirectories is just fine. I'll be trying to figure out that new way outlined in this thread to make them all appear as one project using git magic when I'm required to convert to the new AUR git method.

I think it's quite common to have a repository with all your aur packages instead of one for each. I'm in the same situation[1] so any hints on how to move history to the new AUR 4 would be great {wiki or mailing list} [1]: https://github.com/inglor/pkgbuild --

On 23/05, Doug Newgard wrote:

You may agree, but that doesn't make it right, just lazy.

How is it lazy to not want to have tens or hundreds of git repos with just a single or two files in them around when there's no reason for it? -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/

On Sat, 2015-05-23 at 16:56 -0700, Tai-Lin Chu wrote:

aur4 at this moment is still inconvenient to use because makepkg is designed for the old aur. Should we update makepkg first?

I also hope that the coexist period of new and old aur is short, or there is a way to propagate updates to new aur to old aur so that packagers don't have to update twice.

On Sat, May 23, 2015 at 2:53 PM, Johannes Löthberg wrote:

...

On 23/05, Doug Newgard wrote:

...

You may agree, but that doesn't make it right, just lazy.

How is it lazy to not want to have tens or hundreds of git repos with just a single or two files in them around when there's no reason for it?

-- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/

I agree to the already mentioned criticism, that there is to few documentation. An additional option for makepkg would be great and will definitely make the migration process a whole lot easier. However I disagree that it is useless to make a custom git repo for each and every package. Though it seems like an odd choice for the maintainer, it is way better when thinking about the server-side administration. Managing co-maintainers, disowning and adopting packages is much easier if they are isolated in their own repo. The only logical choice for me was to split my repo, which once contained all my packages into several small ones and then worked with them through git-submodules.

On 24/05, Pablo Lezaeta Reyes wrote:

Maybe you want add the anounce to the AUR mainpage too, the massage if is posted in the Arch mainpage only it can get lost if other messages are added and displace AUR4 to the bottom.

It is an email notification.. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/

* Tai-Lin Chu (Sun, 24 May 2015 11:00:19 -0700):

I made a plain script called "srcinfo" that generates srcinfo in the simplest way.

There already is `mksrcinfo` available at https://aur.archlinux.org/packages/pkgbuild-introspection-git Best, Marcel

* brent saner (Sun, 24 May 2015 19:12:57 -0400):

just wanted to throw this in there, used mksrcinfo and uploaded my packages to aur4's git system last night. seemed to work pretty well but the git hooks choked a bit on a split PKGBUILD.

Which one?

additionally, i accidentally created a repo with a typo- is there a way to remove that? i didn't seem to find one.

It's probably the same as with current AUR: upload a new package and file a merge request. But for now, I think it's not necessary, as the new site will be wiped before the mail will be sent, as far as I did understand earlier mails about AUR 4.0.0. Or isn't it? Best, Marcel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 05/24/2015 07:29 PM, Marcel Korpel wrote:

* brent saner (Sun, 24 May 2015 19:12:57 -0400):

...

just wanted to throw this in there, used mksrcinfo and uploaded my packages to aur4's git system last night. seemed to work pretty well but the git hooks choked a bit on a split PKGBUILD.

Which one?

https://aur4.archlinux.org/pkgbase/nquake/ [master (root-commit) 6ffd60f] initial commit/convert from AUR3 4 files changed, 293 insertions(+) create mode 100644 .SRCINFO create mode 100644 PKGBUILD create mode 100644 nquake-base.install create mode 100644 nquake-generic.install Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 4.41 KiB | 0 bytes/s, done. Total 6 (delta 1), reused 0 (delta 0) To ssh+git://aur@aur4.archlinux.org/nquake.git/ * [new branch] master -> master [master (root-commit) 9b5d933] initial commit/convert from AUR3 4 files changed, 116 insertions(+) create mode 100644 .SRCINFO create mode 100644 PKGBUILD create mode 100644 nquake.install create mode 100644 nquake.launcher Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 2.08 KiB | 0 bytes/s, done. Total 6 (delta 0), reused 0 (delta 0) remote: error: The following error occurred when parsing commit remote: error: 9b5d9338adf57fdf04cd1b5a254b6254f1b5ad4c: remote: error: invalid pkgbase: nquake remote: error: hook declined to update refs/heads/master

...

additionally, i accidentally created a repo with a typo- is there a way to remove that? i didn't seem to find one.

It's probably the same as with current AUR: upload a new package and file a merge request.

Gotcha; so i'd have to generate a dummy PKGBUILD and SRCINFO and then request a deletion. Bit of a pain, but no more of a hassle than the current stable AUR, agreed.

But for now, I think it's not necessary, as the new site will be wiped before the mail will be sent, as far as I did understand earlier mails about AUR 4.0.0. Or isn't it?

Best, Marcel

I'd have to check again- anyone else know off the top of their head if this is true? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJVYnVGAAoJEIwATC+TSB9rc2wP/j4FQSOFKRtIiQRu/dNgdLWa t0hrwgqs3AF5jyuiCh/7ipa2acXcS4petSSaQZcx+g1ALLrdij5CeoMsldG2knzC dJK9EyADfIWTwIFoV0F/e9MxI2kYdATVC658bMhhQE8tfIylviQBDyTKvRMdnwd1 AZi/o5q5YPdLebGuX+ecLm++ek4ZnuyzONM0nrBpxtXfobfN9LSR9JFqjbqgKoRe OeMo6ivhH7b8wVLmeoQ8o+xI+wRoc7/oRnRNSzwD8A8vMJ5JZv6FB2jbTVEPzpvD 7Oy3l/GWqwfkrV9SADfoMyQLpXtYJnmUCSskVc3gLn2SW+EpwOyYKJU0bQiiIshR i5aLV4bUYFhhpGOowXy5e2QAnIUCFd0cpNFVJzLxED0jaAdBylOKBitGcp8jzD63 gUCDwoehVOvWXoDnbtuE0B3ew1ekwtXcMHboHMbg25OEPyD5eLaS7Km1yPFowXkR U68n5hXx/vZhPESeN4lLEp5jacCBSwOkzm8TatRSzHouDkdPkmM5FsWrrSwT7DuK qlWx8qkaXNF2+NBIbn7baLaNj0jj0lJDCHmfXUBkDn7VXepM6Beezpvn/nq5PoVV oPToUn3344gfnenAJle+Gb4QpfHrnhEbeI54MNKkbxIL1m8/gdGpUK+JLk3lHzh9 PdVfw8UAz3X9LGuAs7ew =xgg7 -----END PGP SIGNATURE-----

Also I noticed that aur4.archlinux.org is working here. but the main page lack of a link that specificaly mention that intructions for uloading packager are here, they links only are guideliness for packaging for TU aur user, for user itself and bugtracker. I son't know if is time but why not add a string with something like "For uploading packages ", or "for instructions to upload packages refer to <specific section on aur wiki article>". The first will show in the main page how, so new users will know what to do when they first enter the page even befor set an acount or think in read the wiki, the seccond (my fav) encourage read the wiki. I can say that the actual text show no easy to notice indicators of what to do to upload but a simple 1 liner text even could help. Also I keep thinking that either a emailed anounce and a arch mainpage anounce will be the best and that 1 repo per package is a bad idea. -- *Pablo Lezaeta*

* Pablo Lezaeta Reyes (Mon, 25 May 2015 17:49:56 -0300):

Also I noticed that aur4.archlinux.org is working here. but the main page lack of a link that specificaly mention that intructions for uloading packager are here, they links only are guideliness for packaging for TU aur user, for user itself and bugtracker.

I think the instructions in https://lists.archlinux.org/pipermail/aur-dev/2014-December/003013.html should be incorporated into the wiki. Notice that the port number has been changed to the default one (22) and the host name to aur4.archlinux.org. Best, Marcel

Νῖκος, On Tue, 26 May 2015, Νῖκος Θεοδώρου wrote:

When I do "git push", I get

nikos@Russell:~/Desktop/AUR4/coolvlviewer$ git push -v origin master Pushing to ssh+git://aur4.archlinux.org/coolvlviewer.git/ error: src refspec master does not match any. error: failed to push some refs to 'ssh+git://aur4.archlinux.org/coolvlviewer.git/'

try git push -u origin master not -v --brian

On 26-05-2015 07:15, Νῖκος Θεοδώρου wrote:

Thank you, but still: nikos@Russell:~/Desktop/AUR4/coolvlviewer$ git push -u origin master error: src refspec master does not match any. error: failed to push some refs to 'ssh+git://aur4.archlinux.org/coolvlviewer.git/' I found out that if you accidentally commit the PKGBUILD without the .SRCINFO, and then try to push the .SRCINFO file after, it won't work. My suggestion to you, start with a clean clone of your repo. I was able to up every project I have on aur.archlinux.org to aur4.

Cheers, Giancarlo Razzolini

use git filter-branch --tree-filter to add .SRCINFO to earlier commits

using git filter-branch --tree-filter for any new commit is wrong because it will run on all past trees. A lot of inefficient work is done here. On Tue, May 26, 2015 at 6:27 AM, Marcel Korpel wrote:

* Giancarlo Razzolini (Tue, 26 May 2015 10:21:01 -0300):

...

I found out that if you accidentally commit the PKGBUILD without the .SRCINFO, and then try to push the .SRCINFO file after, it won't work. My suggestion to you, start with a clean clone of your repo. I was able to up every project I have on aur.archlinux.org to aur4.

Or, as Doug Newgard already said, use git filter-branch --tree-filter to add .SRCINFO to earlier commits.

Best, Marcel

* Tai-Lin Chu (Sat, 23 May 2015 16:56:58 -0700):

I also hope that the coexist period of new and old aur is short, or there is a way to propagate updates to new aur to old aur so that packagers don't have to update twice.

That's not the way it's planned: old AUR is made readonly and then you can submit packages to new AUR. You have one month to upload all your packages to new AUR, then the package names are made available to anyone. Best, Marcel