Re: [aur-general] KeyError(key)

[Lukas Fleischer]

That sounds like a bug to me. Could you please upload your repository
somewhere else (e.g. on GitHub) and file a bug report on [1]?

Thanks,
Lukas

[1] https://bugs.archlinux.org/index/proj2

[aur-general] KeyError(key)

[Harley W]

> Can you copy the exact contents of the (error) messages?> FTR, I didn't copy 
> the complete contents of ~/.ssh/id_rsa-aur.pub to my> account page, I had to 
> omit the "username@host" part at the end,> otherwise my key wasn't accepted.> 
> Best, MarcelSorry about that. I'm new to all this :)I hope this fixes the 
> format issues and the sending twice problem. In 'My Account', the public key 
> doesn't end with anything under the form 'username@host'. Here is the error 
> message I'm getting:$ git push origin masterEnter passphrase for key 
> '/home/myusername/.ssh/id_rsa' :...remote: File "hooks/update", line 198, in 
> remote:blob = repo[treeobj.id]remote: File 
> "/usr/lib/python3.4/site-packages/pygit2/repository.py", line 90, in 
> __getitem__remote:raise KeyError(key)remote: KeyError: *there is an 
> encrypted string following this"remote: error: hook declined to update 
> /refs/heads/masterTo ssh://a...@aur4.archlinux.org/savant-git.git ! [remote 
> rejected] master -> master (hook declined)error: failed to push some refs to 
> 'ssh://a...@aur4.archlinux.org/savant-git.git'
Thanks for any help,Harley

Re: [aur-general] Adding a git package to AUR4

[Marcel Korpel]

* Harley W  (Tue, 9 Jun 2015 18:26:21 -0400):
> Just tried the git filter-branch solution, which got rid of the
> SRCINFO error, however now i get a KeyError... I believe this may be
> related to the SSH public key, however I'm not sure how I got that
> wrong. I just copied what was in my .ssh/id_rsa.pub to the public key
> field in my AUR account.

First, please don't top-post. Second, do you know you're sending your
emails twice?

Can you copy the exact contents of the (error) messages?

FTR, I didn't copy the complete contents of ~/.ssh/id_rsa-aur.pub to my
account page, I had to omit the "username@host" part at the end,
otherwise my key wasn't accepted.

Best, Marcel

Re: [aur-general] Adding a git package to AUR4

[Harley W]

Just tried the git filter-branch solution, which got rid of the SRCINFO error, 
however now i get a KeyError... I believe this may be related to the SSH public 
key, however I'm not sure how I got that wrong. I just copied what was in my 
.ssh/id_rsa.pub to the public key field in my AUR account. Thanks for the help.

Sent from my Samsung device

 Original message 
From: Ido Rosen 
Date: 06-09-2015  5:05 PM  (GMT-05:00)
To: "Discussion about the Arch User Repository (AUR)" 

Subject: Re: [aur-general] Adding a git package to AUR4

On Tue, Jun 9, 2015 at 5:00 PM, Harley W  wrote:
> Hello,I'm having a lot of trouble transferring my package to AUR4. It is a 
> git package, so after trying for about an hour to get it to work the way that 
> is described on the wiki page, I thought I could try to push it to a separate 
> remote repository (the aur4 repository). Is there a way to do this? I tried
> $ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git 
> commit -m "Initial upload to aur4"$ git push aur4 master
> Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
> appear to be a git repository. Is there a way to accomplish it this way?
> If not, the issue I was having in the method described in the wiki was that 
> it would keep telling me:remote: error: missing .SRCINFOEven though I 
> committed it and I copied it into pretty much every directory, I don't 
> understand this at all.
> Sorry about this question, I am still quite new to git and I've never dealt 
> with SSH before.Thanks for any help.
Try:
  pacman -Sy pkgbuild-introspection
  git filter-branch -f --tree-filter "test -f .SRCINFO || mksrcinfo"

This will go through the current branch and, if no .SRCINFO exists in
a commit, create one and edit the commit (rewriting history).  This is
part of what my script[1] does.

Ido

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

Re: [aur-general] Adding a git package to AUR4

[Harley W]

Just tried the git filter-branch solution, which got rid of the SRCINFO error, 
however now i get a KeyError... I believe this may be related to the SSH public 
key, however I'm not sure how I got that wrong. I just copied what was in my 
.ssh/id_rsa.pub to the public key field in my AUR account. Thanks for the help.

Sent from my Samsung device

 Original message 
From: Ido Rosen 
Date: 06-09-2015  5:05 PM  (GMT-05:00)
To: "Discussion about the Arch User Repository (AUR)" 

Subject: Re: [aur-general] Adding a git package to AUR4

On Tue, Jun 9, 2015 at 5:00 PM, Harley W  wrote:
> Hello,I'm having a lot of trouble transferring my package to AUR4. It is a 
> git package, so after trying for about an hour to get it to work the way that 
> is described on the wiki page, I thought I could try to push it to a separate 
> remote repository (the aur4 repository). Is there a way to do this? I tried
> $ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git 
> commit -m "Initial upload to aur4"$ git push aur4 master
> Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
> appear to be a git repository. Is there a way to accomplish it this way?
> If not, the issue I was having in the method described in the wiki was that 
> it would keep telling me:remote: error: missing .SRCINFOEven though I 
> committed it and I copied it into pretty much every directory, I don't 
> understand this at all.
> Sorry about this question, I am still quite new to git and I've never dealt 
> with SSH before.Thanks for any help.
Try:
  pacman -Sy pkgbuild-introspection
  git filter-branch -f --tree-filter "test -f .SRCINFO || mksrcinfo"

This will go through the current branch and, if no .SRCINFO exists in
a commit, create one and edit the commit (rewriting history).  This is
part of what my script[1] does.

Ido

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

Re: [aur-general] How to install wine packages the require drive_c system wide?

[LoneVVolf]

On 09-06-15 21:56, Storm Dragon wrote:

Hi,
I am thinking of packaging some  audio games. The problem is, they 
will require a sapi5 voice to work. I can create a package for that 
too, except I think it requires something like c:\System32. Is there a 
way to do this system wide instead of using a ~/.wine prefix?

Thanks
Storm
I suggest you contact the people behind winetricks , 
https://github.com/Winetricks/winetricks/releases .
Winetricks provides many runtime binaries for wine in a way the user can 
easily install/remove them.


LVV

Re: [aur-general] Adding a git package to AUR4

[Harley W]

Thank you very much. I will try this when I get a chance, and if that doesn't 
work ill try out your script.


Sent from my Samsung device

 Original message 
From: Ido Rosen 
Date: 06-09-2015  5:05 PM  (GMT-05:00)
To: "Discussion about the Arch User Repository (AUR)" 

Subject: Re: [aur-general] Adding a git package to AUR4

On Tue, Jun 9, 2015 at 5:00 PM, Harley W  wrote:
> Hello,I'm having a lot of trouble transferring my package to AUR4. It is a 
> git package, so after trying for about an hour to get it to work the way that 
> is described on the wiki page, I thought I could try to push it to a separate 
> remote repository (the aur4 repository). Is there a way to do this? I tried
> $ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git 
> commit -m "Initial upload to aur4"$ git push aur4 master
> Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
> appear to be a git repository. Is there a way to accomplish it this way?
> If not, the issue I was having in the method described in the wiki was that 
> it would keep telling me:remote: error: missing .SRCINFOEven though I 
> committed it and I copied it into pretty much every directory, I don't 
> understand this at all.
> Sorry about this question, I am still quite new to git and I've never dealt 
> with SSH before.Thanks for any help.
Try:
  pacman -Sy pkgbuild-introspection
  git filter-branch -f --tree-filter "test -f .SRCINFO || mksrcinfo"

This will go through the current branch and, if no .SRCINFO exists in
a commit, create one and edit the commit (rewriting history).  This is
part of what my script[1] does.

Ido

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

Re: [aur-general] Adding a git package to AUR4

[Harley W]

Thank you very much. I will try this when I get a chance, and if that doesn't 
work ill try out your script.


Sent from my Samsung device

 Original message 
From: Ido Rosen 
Date: 06-09-2015  5:05 PM  (GMT-05:00)
To: "Discussion about the Arch User Repository (AUR)" 

Subject: Re: [aur-general] Adding a git package to AUR4

On Tue, Jun 9, 2015 at 5:00 PM, Harley W  wrote:
> Hello,I'm having a lot of trouble transferring my package to AUR4. It is a 
> git package, so after trying for about an hour to get it to work the way that 
> is described on the wiki page, I thought I could try to push it to a separate 
> remote repository (the aur4 repository). Is there a way to do this? I tried
> $ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git 
> commit -m "Initial upload to aur4"$ git push aur4 master
> Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
> appear to be a git repository. Is there a way to accomplish it this way?
> If not, the issue I was having in the method described in the wiki was that 
> it would keep telling me:remote: error: missing .SRCINFOEven though I 
> committed it and I copied it into pretty much every directory, I don't 
> understand this at all.
> Sorry about this question, I am still quite new to git and I've never dealt 
> with SSH before.Thanks for any help.
Try:
  pacman -Sy pkgbuild-introspection
  git filter-branch -f --tree-filter "test -f .SRCINFO || mksrcinfo"

This will go through the current branch and, if no .SRCINFO exists in
a commit, create one and edit the commit (rewriting history).  This is
part of what my script[1] does.

Ido

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

Re: [aur-general] Adding a git package to AUR4

[Ido Rosen]

On Tue, Jun 9, 2015 at 5:00 PM, Harley W  wrote:
> Hello,I'm having a lot of trouble transferring my package to AUR4. It is a 
> git package, so after trying for about an hour to get it to work the way that 
> is described on the wiki page, I thought I could try to push it to a separate 
> remote repository (the aur4 repository). Is there a way to do this? I tried
> $ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git 
> commit -m "Initial upload to aur4"$ git push aur4 master
> Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
> appear to be a git repository. Is there a way to accomplish it this way?
> If not, the issue I was having in the method described in the wiki was that 
> it would keep telling me:remote: error: missing .SRCINFOEven though I 
> committed it and I copied it into pretty much every directory, I don't 
> understand this at all.
> Sorry about this question, I am still quite new to git and I've never dealt 
> with SSH before.Thanks for any help.
Try:
  pacman -Sy pkgbuild-introspection
  git filter-branch -f --tree-filter "test -f .SRCINFO || mksrcinfo"

This will go through the current branch and, if no .SRCINFO exists in
a commit, create one and edit the commit (rewriting history).  This is
part of what my script[1] does.

Ido

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

Re: [aur-general] Adding a git package to AUR4

[Noel Kuntze]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello Harley,

The .SRCINFO file needs to be present in _every_ commit in the repo.
I stumbled over that, too.

Mit freundlichen Grüßen/Kind Regards,
Noel Kuntze

GPG Key ID: 0x63EC6658
Fingerprint: 23CA BB60 2146 05E7 7278 6592 3839 298F 63EC 6658

Am 09.06.2015 um 23:00 schrieb Harley W:
> Hello,I'm having a lot of trouble transferring my package to AUR4. It is a 
> git package, so after trying for about an hour to get it to work the way that 
> is described on the wiki page, I thought I could try to push it to a separate 
> remote repository (the aur4 repository). Is there a way to do this? I tried
> $ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git 
> commit -m "Initial upload to aur4"$ git push aur4 master
> Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
> appear to be a git repository. Is there a way to accomplish it this way?
> If not, the issue I was having in the method described in the wiki was that 
> it would keep telling me:remote: error: missing .SRCINFOEven though I 
> committed it and I copied it into pretty much every directory, I don't 
> understand this at all.
> Sorry about this question, I am still quite new to git and I've never dealt 
> with SSH before.Thanks for any help.  

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJVd1Q/AAoJEDg5KY9j7GZYB8YP+gKcp3t1pyDrlxuqFlw2yaAS
hX+olr+clqmcZDiyARSy9BCn95hb6ykYfO2ZIs2x4JdRoiTYOA2Oe9zUZ37nNG2s
HULxVRiJR0RJnF+RRcsvKuJp2Wd2aYukw8LjzV0fa1p/ACIE1Tl2dwGqMI4gg88A
YNI7OsPu2UXqHeWsDMO5Scz61eNxfYlQLh0MS46WKBWvrtK7Vm0yRALc08Ax7Jpj
2UOx5xj4MRmSEc/D+gmBdQb2VA6kAiO+CxSMgc0Czz8aRxDHstWhe52OODvyFV+b
ZbCk10wuw8z9dN7qOfKQd9n/OVsg+76KLdTmdbr6pG33T/pdSa9f/Ko1gVqjt4Ag
6D3kc/KPx11a4p1TDjWmNuR8yMPSNFpwQyYzeLnpiCS5Y4MWn4gXD2EbScqO13Pd
LXZlA7ejSmISICnaqsk8PJgkEi+b9unXX6iYCF2F48WT3GB55/Onmp3LPJwlxgaW
+dMbectL2cnR+5gCmP688SDAWt50+piCfDuv+aFPBWGkGMxHK09RW0CUOXTMb/kt
g9vLGEYb9843+XLbq7E7y1l6tzKc7OYCoW9WLwKOsKkKtWg99BJ7dbM8BpPv631h
KSn2w3tehO5sJaFqJdqTtoMTAczVdxgQ8o7k5j/0toILhaUBXYhGo/9WtGug73wk
yyTkk/rDOwqR1U5R80zF
=T3WY
-END PGP SIGNATURE-

[aur-general] Adding a git package to AUR4

[Harley W]

Hello,I'm having a lot of trouble transferring my package to AUR4. It is a git 
package, so after trying for about an hour to get it to work the way that is 
described on the wiki page, I thought I could try to push it to a separate 
remote repository (the aur4 repository). Is there a way to do this? I tried
$ git add remote aur4 aur4.archlinux.org/savant-git.git$ git add *$ git commit 
-m "Initial upload to aur4"$ git push aur4 master
Which said, as I expected, that aur4.archlinux.org/savant-git.git does not 
appear to be a git repository. Is there a way to accomplish it this way?
If not, the issue I was having in the method described in the wiki was that it 
would keep telling me:remote: error: missing .SRCINFOEven though I committed it 
and I copied it into pretty much every directory, I don't understand this at 
all.
Sorry about this question, I am still quite new to git and I've never dealt 
with SSH before.Thanks for any help.  

Re: [aur-general] How to install wine packages the require drive_c system wide?

[Martti Kühne]

On Tue, Jun 9, 2015 at 9:56 PM, Storm Dragon  wrote:
> Hi,
> I am thinking of packaging some  audio games. The problem is, they will
> require a sapi5 voice to work. I can create a package for that too, except I
> think it requires something like c:\System32. Is there a way to do this
> system wide instead of using a ~/.wine prefix?
> Thanks
> Storm


There's not much the package manager does in ~ (and hence, ~/.wine)
and I *think* wine doesn't (and in my opinion should not) have a
system-wide software directory.
Therefore I believe that these concepts can't be used with each other.
The other things that come to mind about this is that Windows isn't an
*operating* system and Wine is not an emulator...

cheers!
mar77i

[aur-general] How to install wine packages the require drive_c system wide?

[Storm Dragon]

Hi,
I am thinking of packaging some  audio games. The problem is, they will require 
a sapi5 voice to work. I can create a package for that too, except I think it 
requires something like c:\System32. Is there a way to do this system wide 
instead of using a ~/.wine prefix?
Thanks
Storm
--
Powered by Arch Linux! I am registered Linux user number 508465: 
https://linuxcounter.net/user/508465.html
My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key 43DDC193
Free and open source social networking, get your account TODAY! 
http://social.2mb.solutions/main/register
How many Internet mail list subscribers does it take to change a lightbulb? 
http://goo.gl/eO4PJ
"Shine glorious we ride, we stare into the blackened sky. Save the last command, the 
virtue blinding."
DragonForce - The Last Journey Home


pgpo4q0tMlZk3.pgp
Description: PGP signature

Re: [aur-general] [AUR4] Recommended procedure for merging several split packages into one pkgbase with split packages inside?

[Bruno Pagani]

Le 09/06/2015 18:31, ShadowKyogre a écrit :
> I was contemplating either filing a bunch of merge requests or a bunch
> of deletion requests before trying to resubmit, but there's probably a
> better way to handle this that I'm not sure of.

Currently, the way is a bunch of merge requests, unless someone comes
out with a better idea.



signature.asc
Description: OpenPGP digital signature

[aur-general] [AUR4] Recommended procedure for merging several split packages into one pkgbase with split packages inside?

[ShadowKyogre]

In the AUR, these packages are currently split off as their own separate 
packages without a common package base:


mse-extrafoils-clights
mse-extrafoils-fire
mse-extrafoils-fracture
mse-extrafoils-ghost
mse-extrafoils-gold
mse-extrafoils-jss
mse-extrafoils-mosaic
mse-extrafoils-old
mse-extrafoils-parallel
mse-extrafoils-ribbons
mse-extrafoils-snow

For the new AUR, I've prepared a split PKGBUILD and .SRCINFO for the 
AUR4 submission, but I get this error when I try to submit my finished work:


Counting objects: 4, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 1.52 KiB | 0 bytes/s, done.
Total 4 (delta 0), reused 0 (delta 0)
remote: error: cannot overwrite package: mse-extrafoils-fracture
remote: error: hook declined to update refs/heads/master
To ssh://a...@aur4.archlinux.org/mse-extrafoils.git
 ! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 
'ssh://a...@aur4.archlinux.org/mse-extrafoils.git'


I was contemplating either filing a bunch of merge requests or a bunch 
of deletion requests before trying to resubmit, but there's probably a 
better way to handle this that I'm not sure of.

Re: [aur-general] AUR4 migration of orphan packages

[Joakim Hernberg]

On Tue, 9 Jun 2015 18:14:58 +0200
Chris Warrick  wrote:

> On Tue, Jun 9, 2015 at 5:53 PM, Ido Rosen  wrote:
> > I think some of the orphans on AUR are just maintained by multiple
> > people.  The usage pattern is:

IMO, it would be a lot better for the distro to get rid of badly
packaged software instead of cleaning out orphans (that may or may
not be up to date and/or useful to many users)...

Sadly I have no bright idea for how to bring this about :)

-- 

   Joakim

Re: [aur-general] AUR4 migration of orphan packages

[Ido Rosen]

On Tue, Jun 9, 2015 at 12:14 PM, Chris Warrick  wrote:
> On Tue, Jun 9, 2015 at 5:53 PM, Ido Rosen  wrote:
>> I think some of the orphans on AUR are just maintained by multiple
>> people.  The usage pattern is:
>>
>> Person A adopts, updates, and disowns.
>> Person B some time later notices it's out of date, adopts, updates, disowns.
>>
>> It seems perfectly reasonable to have multiple people maintain a
>> package over time this way.  Maybe we just need better support for
>> this style of non-maintainership that isn't quite "orphaned"?  Support
>> for multiple maintainers/collaborators like on GitHub repos?
>> (Outright owning a package in AUR prevents anyone else from updating
>> it.)
>
> It also prevents a third party (Mallory) from taking it over and:
>
> (a) replacing it with something else (malware?);
> (b) preventing Alice and Bob from updating it;
> (c) requesting deletion;
> (d) [insert other harmful actions here].

Yes, that's right, and these are all good reasons why we should
continue to have ownership, which is why I suggested we support
something in-between as well (before I knew about co-maintainership
capabilities in AUR, which basically resolve this).
>
>> if someone wants to update a package faster than I can get to it […]
>
> You should use some service that would tell you about package updates,
> for example requires.io for Python, or RSS feeds.  Will take 5 minutes
> to do it in many cases (to update pkgver and the checkums)

Thanks for the suggestion, but these services don't work for some (or
most) of the packages I maintain, and some of the packages are
academic in nature.  For updates that are just updating the pkgver &
updpkgsums, I do those myself, but there are cases (major version
changes, new feature requests, upstream breaks something, dependent
packages break something, etc.) where debugging/more time is needed.
That's when it may take me a week or more to get around to updating
the package, in which case if someone else with more time gets to it
sooner, I encourage them to submit a pull request and add them as a
Contributor: (and thank them for helping!). :-)

Another thing that having the pull request workflow I use allows is
for the users of the package to add things to the package (e.g.
optdepends as they come out) and fix bugs.  It makes my work after
initially creating the package basically just QA to make sure their
PRs don't break anything in many cases, which I like.

>
> --
> Chris Warrick 
> PGP: 5EAAEA16

Re: [aur-general] AUR4 migration of orphan packages

[Chris Warrick]

On Tue, Jun 9, 2015 at 5:53 PM, Ido Rosen  wrote:
> I think some of the orphans on AUR are just maintained by multiple
> people.  The usage pattern is:
>
> Person A adopts, updates, and disowns.
> Person B some time later notices it's out of date, adopts, updates, disowns.
>
> It seems perfectly reasonable to have multiple people maintain a
> package over time this way.  Maybe we just need better support for
> this style of non-maintainership that isn't quite "orphaned"?  Support
> for multiple maintainers/collaborators like on GitHub repos?
> (Outright owning a package in AUR prevents anyone else from updating
> it.)

It also prevents a third party (Mallory) from taking it over and:

(a) replacing it with something else (malware?);
(b) preventing Alice and Bob from updating it;
(c) requesting deletion;
(d) [insert other harmful actions here].

> if someone wants to update a package faster than I can get to it […]

You should use some service that would tell you about package updates,
for example requires.io for Python, or RSS feeds.  Will take 5 minutes
to do it in many cases (to update pkgver and the checkums)

-- 
Chris Warrick 
PGP: 5EAAEA16

Re: [aur-general] AUR4 migration of orphan packages

[Dominik Heidler]

Am Dienstag, 9. Juni 2015, 11:53:53 schrieb Ido Rosen:
> It seems perfectly reasonable to have multiple people maintain a
> package over time this way.  Maybe we just need better support for
> this style of non-maintainership that isn't quite "orphaned"?  Support
> for multiple maintainers/collaborators like on GitHub repos?
> (Outright owning a package in AUR prevents anyone else from updating
> it.)

According to the AUR4 webui it is possible to specify co-maintainers for a pkg 
(if you own a pkg, you'll find the button next to the disown button).


But I actually like the idea of using git for non-co-maintainers to 
contribute:
I assume that only the master branch is used for the actual pkg - so if we 
allow any user to update every branch (but the master branch) of every 
package, we could have something similar to pull requests. A user could just 
submit his patch into a new branch and the actual maintainer can simply merge 
it into master.

Re: [aur-general] AUR4 migration of orphan packages

[Ido Rosen]

I didn't know that existed!  Cool.

Maybe this should be front and center next to any links/buttons to
disown a package?  E.g. "Are you sure you want to disown this package?
 Remember, you can always add co-maintainers rather than disowning and
readopting later..."

On Tue, Jun 9, 2015 at 11:59 AM, Bruno Pagani  wrote:
> You mean that:
> https://aur4.archlinux.org/pkgbase/${pkgname}/comaintainers/ ?
>
> Le 09/06/2015 17:53, Ido Rosen a écrit :
>> I think some of the orphans on AUR are just maintained by multiple
>> people.  The usage pattern is:
>>
>> Person A adopts, updates, and disowns.
>> Person B some time later notices it's out of date, adopts, updates, disowns.
>>
>> It seems perfectly reasonable to have multiple people maintain a
>> package over time this way.  Maybe we just need better support for
>> this style of non-maintainership that isn't quite "orphaned"?  Support
>> for multiple maintainers/collaborators like on GitHub repos?
>> (Outright owning a package in AUR prevents anyone else from updating
>> it.)
>>
>> I do something in between outright maintainership and this "adopt,
>> update, disown" non-maintainership: I have a git repo with my AUR
>> packages, and accept pull requests on GitHub -- if someone wants to
>> update a package faster than I can get to it (since I only have time
>> on weekends), they submit a pull request and I merge it in, test, and
>> submit to AUR (which takes 2 min to verify & submit the package, vs.
>> the a-priori-unknown time commitment of doing it all myself).  It
>> would be nice if there were an official way to make AUR support
>> collaborative maintainership like this.
>>
>> On Tue, Jun 9, 2015 at 11:10 AM, Giancarlo Razzolini
>>  wrote:
>>> On 09-06-2015 08:17, Jesse McClure wrote:
 Agreed.  All the packages that no one carries over to aur4 will still be
 archived for some time, so if anyone*actually*  wants them in aur4, they
 can
 adopt them.  One can keep their own store of PKGBUILDs, but the aur is for
 packages that it is likely multiple users will want.  If not even*one*
 person
 wants a package enough to maintain it in the aur, then it doesn't need to
 be
 there.
>>> I have adopted some packages, created a few more, but I think that this
>>> migration should serve the purpose of cleansing the database. We already
>>> have orphans on aur4 and that is unacceptable. Migrate a package and then
>>> orphan it is not ideal and we will end up having the same number of orphans
>>> as we already have.
>>>
>>> Cheers,
>>> Giancarlo Razzolini
>
>
>
>

Re: [aur-general] AUR4 migration of orphan packages

[Jiachen Yang]

I think the new AUR4 indeed have a co-maintainer list for each package.
It is just in the package actions panel.
(Although I haven't try this feature)

On Wed, Jun 10, 2015 at 12:53 AM, Ido Rosen  wrote:

> I think some of the orphans on AUR are just maintained by multiple
> people.  The usage pattern is:
>
> Person A adopts, updates, and disowns.
> Person B some time later notices it's out of date, adopts, updates,
> disowns.
>
> It seems perfectly reasonable to have multiple people maintain a
> package over time this way.  Maybe we just need better support for
> this style of non-maintainership that isn't quite "orphaned"?  Support
> for multiple maintainers/collaborators like on GitHub repos?
> (Outright owning a package in AUR prevents anyone else from updating
> it.)
>
> I do something in between outright maintainership and this "adopt,
> update, disown" non-maintainership: I have a git repo with my AUR
> packages, and accept pull requests on GitHub -- if someone wants to
> update a package faster than I can get to it (since I only have time
> on weekends), they submit a pull request and I merge it in, test, and
> submit to AUR (which takes 2 min to verify & submit the package, vs.
> the a-priori-unknown time commitment of doing it all myself).  It
> would be nice if there were an official way to make AUR support
> collaborative maintainership like this.
>
> On Tue, Jun 9, 2015 at 11:10 AM, Giancarlo Razzolini
>  wrote:
> > On 09-06-2015 08:17, Jesse McClure wrote:
> >>
> >> Agreed.  All the packages that no one carries over to aur4 will still be
> >> archived for some time, so if anyone*actually*  wants them in aur4, they
> >> can
> >> adopt them.  One can keep their own store of PKGBUILDs, but the aur is
> for
> >> packages that it is likely multiple users will want.  If not even*one*
> >> person
> >> wants a package enough to maintain it in the aur, then it doesn't need
> to
> >> be
> >> there.
> >
> > I have adopted some packages, created a few more, but I think that this
> > migration should serve the purpose of cleansing the database. We already
> > have orphans on aur4 and that is unacceptable. Migrate a package and then
> > orphan it is not ideal and we will end up having the same number of
> orphans
> > as we already have.
> >
> > Cheers,
> > Giancarlo Razzolini
>



-- 

Jiachen Yang 楊嘉晨
Graduate School of Information Science and Technology, Osaka University
Tel:   080-3853-2770
MSN:   firechild...@hotmail.com
GMail: farsee...@gmail.com

Re: [aur-general] AUR4 migration of orphan packages

[Bruno Pagani]

You mean that:
https://aur4.archlinux.org/pkgbase/${pkgname}/comaintainers/ ?

Le 09/06/2015 17:53, Ido Rosen a écrit :
> I think some of the orphans on AUR are just maintained by multiple
> people.  The usage pattern is:
>
> Person A adopts, updates, and disowns.
> Person B some time later notices it's out of date, adopts, updates, disowns.
>
> It seems perfectly reasonable to have multiple people maintain a
> package over time this way.  Maybe we just need better support for
> this style of non-maintainership that isn't quite "orphaned"?  Support
> for multiple maintainers/collaborators like on GitHub repos?
> (Outright owning a package in AUR prevents anyone else from updating
> it.)
>
> I do something in between outright maintainership and this "adopt,
> update, disown" non-maintainership: I have a git repo with my AUR
> packages, and accept pull requests on GitHub -- if someone wants to
> update a package faster than I can get to it (since I only have time
> on weekends), they submit a pull request and I merge it in, test, and
> submit to AUR (which takes 2 min to verify & submit the package, vs.
> the a-priori-unknown time commitment of doing it all myself).  It
> would be nice if there were an official way to make AUR support
> collaborative maintainership like this.
>
> On Tue, Jun 9, 2015 at 11:10 AM, Giancarlo Razzolini
>  wrote:
>> On 09-06-2015 08:17, Jesse McClure wrote:
>>> Agreed.  All the packages that no one carries over to aur4 will still be
>>> archived for some time, so if anyone*actually*  wants them in aur4, they
>>> can
>>> adopt them.  One can keep their own store of PKGBUILDs, but the aur is for
>>> packages that it is likely multiple users will want.  If not even*one*
>>> person
>>> wants a package enough to maintain it in the aur, then it doesn't need to
>>> be
>>> there.
>> I have adopted some packages, created a few more, but I think that this
>> migration should serve the purpose of cleansing the database. We already
>> have orphans on aur4 and that is unacceptable. Migrate a package and then
>> orphan it is not ideal and we will end up having the same number of orphans
>> as we already have.
>>
>> Cheers,
>> Giancarlo Razzolini






signature.asc
Description: OpenPGP digital signature

Re: [aur-general] AUR4 migration of orphan packages

[Ido Rosen]

I think some of the orphans on AUR are just maintained by multiple
people.  The usage pattern is:

Person A adopts, updates, and disowns.
Person B some time later notices it's out of date, adopts, updates, disowns.

It seems perfectly reasonable to have multiple people maintain a
package over time this way.  Maybe we just need better support for
this style of non-maintainership that isn't quite "orphaned"?  Support
for multiple maintainers/collaborators like on GitHub repos?
(Outright owning a package in AUR prevents anyone else from updating
it.)

I do something in between outright maintainership and this "adopt,
update, disown" non-maintainership: I have a git repo with my AUR
packages, and accept pull requests on GitHub -- if someone wants to
update a package faster than I can get to it (since I only have time
on weekends), they submit a pull request and I merge it in, test, and
submit to AUR (which takes 2 min to verify & submit the package, vs.
the a-priori-unknown time commitment of doing it all myself).  It
would be nice if there were an official way to make AUR support
collaborative maintainership like this.

On Tue, Jun 9, 2015 at 11:10 AM, Giancarlo Razzolini
 wrote:
> On 09-06-2015 08:17, Jesse McClure wrote:
>>
>> Agreed.  All the packages that no one carries over to aur4 will still be
>> archived for some time, so if anyone*actually*  wants them in aur4, they
>> can
>> adopt them.  One can keep their own store of PKGBUILDs, but the aur is for
>> packages that it is likely multiple users will want.  If not even*one*
>> person
>> wants a package enough to maintain it in the aur, then it doesn't need to
>> be
>> there.
>
> I have adopted some packages, created a few more, but I think that this
> migration should serve the purpose of cleansing the database. We already
> have orphans on aur4 and that is unacceptable. Migrate a package and then
> orphan it is not ideal and we will end up having the same number of orphans
> as we already have.
>
> Cheers,
> Giancarlo Razzolini

Re: [aur-general] AUR4 migration of orphan packages

[Giancarlo Razzolini]

On 09-06-2015 08:17, Jesse McClure wrote:

Agreed.  All the packages that no one carries over to aur4 will still be
archived for some time, so if anyone*actually*  wants them in aur4, they can
adopt them.  One can keep their own store of PKGBUILDs, but the aur is for
packages that it is likely multiple users will want.  If not even*one*  person
wants a package enough to maintain it in the aur, then it doesn't need to be
there.
I have adopted some packages, created a few more, but I think that this 
migration should serve the purpose of cleansing the database. We already 
have orphans on aur4 and that is unacceptable. Migrate a package and 
then orphan it is not ideal and we will end up having the same number of 
orphans as we already have.


Cheers,
Giancarlo Razzolini

Re: [aur-general] AUR4 migration of orphan packages

[Jesse McClure]

Simon Brulhart  [2015-06-09 11:36:09 +0200]:
> > There are a lot of orphan packages that haven't been updated for months
> > or years, but still work fine and could be considered useful.

Considered useful by whom?  We don't need them around because they *might* be
useful to some hypothetical person in some hypothetical situation.

On Tue, Jun 09, 2015 at 11:45:30AM +0200, Florian Bruhin wrote:
> If you care enough to want a package ported (e.g.  because you use it and
> it's currently orphaned), you should care enough to adopt it, IMHO. :)

Agreed.  All the packages that no one carries over to aur4 will still be
archived for some time, so if anyone *actually* wants them in aur4, they can
adopt them.  One can keep their own store of PKGBUILDs, but the aur is for
packages that it is likely multiple users will want.  If not even *one* person
wants a package enough to maintain it in the aur, then it doesn't need to be
there.

-Jesse
AKA 'Trilby' on archlinux.org

Re: [aur-general] AUR4 migration of orphan packages

[Florian Bruhin]

* Simon Brulhart  [2015-06-09 11:36:09 +0200]:
> There are a lot of orphan packages that haven't been updated for months
> or years, but still work fine and could be considered useful. I
> understand that these packages will still be available even if nobody
> port them. However I don't know if the current AUR helpers will be able
> to see them or if they will be updated for this purpose.
> If not, I would be happy to adopt some of these packages to do the
> transition, even if I may disown most of them shortly after.
> 
> I suppose that adapting the tooling (if needed) would be a better
> approach, but if they don't consider to do it I would find it sad to let
> all these packages sink into oblivion.

I agree! It'd be helpful to see the archived old-AUR packages
somewhere in AUR helpers, marked accordingly, so one can easily
discover and adopt them even after the AUR transition is done.

For yaourt[*], I opened an issue here yesterday:
https://github.com/archlinuxfr/yaourt/issues/115

I don't think just porting and then disowning packages is the right
thing to do - then the new AUR will be cluttered with things nobody
cares about again. If you care enough to want a package ported (e.g.
because you use it and it's currently orphaned), you should care
enough to adopt it, IMHO. :)

Florian

[*] Just to preempt this: I hope it won't be necessary to mention
this, but I use yaourt since I use Arch (>5 years), I'm still happy
with it, and yes - I know how to use makepkg manually. If you really
feel like discussing about yaourt instead of the rest of the mail,
please do so with a personal reply, not to the ML. Thanks!

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpJNSnP6owEf.pgp
Description: PGP signature

[aur-general] AUR4 migration of orphan packages

[Simon Brulhart]

Hi,

There are a lot of orphan packages that haven't been updated for months
or years, but still work fine and could be considered useful. I
understand that these packages will still be available even if nobody
port them. However I don't know if the current AUR helpers will be able
to see them or if they will be updated for this purpose.
If not, I would be happy to adopt some of these packages to do the
transition, even if I may disown most of them shortly after.

I suppose that adapting the tooling (if needed) would be a better
approach, but if they don't consider to do it I would find it sad to let
all these packages sink into oblivion.

Simon





signature.asc
Description: OpenPGP digital signature

[aur-general] Signoff report for [community-testing]

[Arch Website Notification]

=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 15 packages missing signoffs
* 6 packages older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)



== Incomplete signoffs for [community] (15 total) ==

* opencl-headers-2:1.2.20150123-1 (any)
0/2 signoffs
* iscan-2.30.1-8 (i686)
0/1 signoffs
* python-xcffib-0.2.3-1 (i686)
0/1 signoffs
* python2-netlib-0.12.1-1 (i686)
0/1 signoffs
* python2-systemd-220-1 (i686)
0/1 signoffs
* shairport-sync-2.2.4-1 (i686)
0/1 signoffs
* synapse-0.2.99.1-1 (i686)
0/1 signoffs
* virtualbox-modules-lts-4.3.28-2 (i686)
0/1 signoffs
* iscan-2.30.1-8 (x86_64)
0/2 signoffs
* python-xcffib-0.2.3-1 (x86_64)
0/2 signoffs
* python2-netlib-0.12.1-1 (x86_64)
0/2 signoffs
* python2-systemd-220-1 (x86_64)
0/2 signoffs
* shairport-sync-2.2.4-1 (x86_64)
0/2 signoffs
* synapse-0.2.99.1-1 (x86_64)
0/2 signoffs
* virtualbox-modules-lts-4.3.28-2 (x86_64)
0/2 signoffs


== All packages in [community-testing] for more than 14 days (6 total) ==

* virtualbox-modules-lts-4.3.28-2 (i686), since 2015-05-15
* virtualbox-modules-lts-4.3.28-2 (x86_64), since 2015-05-15
* python2-systemd-220-1 (i686), since 2015-05-25
* python2-systemd-220-1 (x86_64), since 2015-05-25
* synapse-0.2.99.1-1 (i686), since 2015-05-26
* synapse-0.2.99.1-1 (x86_64), since 2015-05-26


== Top five in signoffs in last 24 hours ==

1. lcarlier - 1 signoffs