* Gordian Edenhofer (Wed, 27 May 2015
09:37:17 +0200):
> You as a maintainer have until August 1st to upload your packages to
> AUR4 otherwise everyone may take over what you once
> maintained.
That's not entirely correct, the window is exactly one month:
* Lukas Fleischer (Sat, 23 May 2015 11:
On Tue, 2015-05-26 at 20:29 -0400, Storm Dragon wrote:
> Howdy,
> Will all existing AUR packages be moved over? Will it be an automated
> process for existing packages? I'm wondering because there are quite
> a few unmaintained packages. If not, is there something I can do to
> help? I don't min
Howdy,
Will all existing AUR packages be moved over? Will it be an automated process
for existing packages? I'm wondering because there are quite a few unmaintained
packages. If not, is there something I can do to help? I don't mind taking on
more packages if that is what's needed.
Thanks
Storm
Pablo,
On Tue, 26 May 2015, Pablo Lezaeta Reyes wrote:
> For the record it take for me 4 hours to upload 44 packages, included
> registration and ssh-key generation.
For me, 2 days for 360 packages, which is almost the identical pace.
But, some maintainers have thousands of packages.
--brian
> And John, I understand it's a PITA to make this transition, Brian's
> script might work.
>
> Do the official AUR-web maintainers provide such a script (I know Lukas
> is away and you already have a lot of work to do, just asking)?
>
For the record it take for me 4 hours to upload 44 packages, in
* Jakob Gruber (Tue, 26 May 2015 16:02:49
-0700):
> Just use
>
> git add -A
>
> to add everything.
>
> On Tue, May 26, 2015 at 2:05 PM, John D Jones III
> wrote:
>
> > On 5/26/15 11:09 AM, SpinFlo wrote:
> >
> >>
> >> this don't work for me
> >>
> >> i need first:
> >>
> >> git add .SRCINFO
>
Just use
git add -A
to add everything.
On Tue, May 26, 2015 at 2:05 PM, John D Jones III
wrote:
> On 5/26/15 11:09 AM, SpinFlo wrote:
>
>>
>> this don't work for me
>>
>> i need first:
>>
>> git add .SRCINFO
>> git add .gitignore (if use)
>>
>> and then 'git add * && git -am "initial commit"'
John,
On Tue, 26 May 2015, John D Jones III wrote:
> Oh great I am NOT looking forward to having to migrate my 870ish
> packages Does anyone have a script that will automate the process?
This script worked for 350 packages, but it has some issues. It's a
starting point.
https://gist
On 5/26/15 11:09 AM, SpinFlo wrote:
this don't work for me
i need first:
git add .SRCINFO
git add .gitignore (if use)
and then 'git add * && git -am "initial commit"'
:/
Oh great I am NOT looking forward to having to migrate my 870ish
packages Does anyone have a script that will au
>>
>> $ git add .
>> $ git commit -m "Initial commit"
>>
this don't work for me
i need first:
git add .SRCINFO
git add .gitignore (if use)
and then 'git add * && git -am "initial commit"'
:/
On Tue, 26 May 2015 18:30:17 +0200
Marcel Korpel wrote:
> * Νῖκος Θεοδώρου (Tue, 26 May 2015 19:21:52
> +0300):
> > nikos@Russell:~/Desktop/AUR4/coolvlviewer$ git filter-branch
> > --tree-filter fatal: Needed a single revision
>
> You need to add a command that is performed on each revision, bu
* Νῖκος Θεοδώρου (Tue, 26 May 2015 19:21:52
+0300):
> nikos@Russell:~/Desktop/AUR4/coolvlviewer$ git filter-branch
> --tree-filter fatal: Needed a single revision
You need to add a command that is performed on each revision, but in
your case, this step is not necessary, as there are no old git
re
On Tue, 26 May 2015 06:24:12 -0600
"Brian F. G. Bidulock" wrote:
I just realised I did "reply" and not "reply all", so I'm repeating
(sorry!)
So, again:
nikos@Russell:~/Desktop$ mkdir AUR4
nikos@Russell:~/Desktop$ cd AUR4
nikos@Russell:~/Desktop/AUR4$ ssh aur4.archlinux.org setup-repo
coolvl
* Tai-Lin Chu (Tue, 26 May 2015 08:25:10 -0700):
>> 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.
No, you run that
> 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
* 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
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 a
On Tue, 26 May 2015 04:04:48 -0600
"Brian F. G. Bidulock" wrote:
> Νῖκος,
>
> 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.
Νῖκος,
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 ref
Hello everyone.
I apologise, but I can't figure out how to upload anything to AUR4. I
followed the instructions here:
On Mon, 25 May 2015 23:50:03 +0200
Marcel Korpel wrote:
> I think the instructions in
> https://lists.archlinux.org/pipermail/aur-dev/2014-December/003013.html
> should be incor
* 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 use
On 25-05-2015 17:49, Pablo Lezaeta Reyes wrote:
> 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 a
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
* brent timothy saner (Sun, 24 May 2015
21:05:22 -0400):
>> 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?
>
> I'd have to check again- anyone else know off the top o
-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
On 23-05-2015 06:07, Lukas Fleischer wrote:
> Note that aur4.archlinux.org does not work yet but will updated to point
> to the same IP address as aur-dev.archlinux.org soon. Comments welcome.
Lukas,
Since we are moving from an https submission system to an git+ssh
one, I think it's advisable
Not forget that are some users that have typos or base64-ed they mails they
will likely miss the anounce if is Mail only.
Also I agree that 1repo per package is overkill for maintainer of 40+ or
100+ packages.
Question: if I upload my pkg to aurdev now will we keep after the deadline,
some of use
* 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
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. additionally, i accidentally
created a repo with a typo- is there a way to remove that? i didn't seem to
find
* 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
* 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
@Ido
@everyone else
I made a plain script called "srcinfo" that generates srcinfo in the
simplest way. It behaves just like makepkg, which expects a PKGBUILD
file in the current working directory.
https://gist.github.com/taylorchu/5d8bdb97acbb22e8b698#file-gistfile1-txt-L181
I really just wrote
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 I
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.
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 n
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 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: 0x50FB9B273A9D0
On Sat, 23 May 2015 12:40:38 -0500
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 GitH
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 gi
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 co
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 artic
On Sat, May 23, 2015 at 11:27 AM, wrote:
>
> So I had the impression I would need to rewrite the whole history of all my
> maintained packages.
...if it comes to that, I had to cook up a little script for a project
that extracted files from a shared tree of scripts and create separate
repos for
* 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
>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
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 s
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
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 r
* 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
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:
Hello,
This is an automated email to all AUR package maintainers.
49 matches
Mail list logo
