[aur-general] Package deletion request

2014-02-09 Thread Joseph Carta
Hi. I've just claimed ownership to and updated the previously orphaned 
package extract-xiso [1]. Since the author of this program incorporated 
the somski mod into it, the package extract-xiso-somski [2] has been 
made redundant and should be deleted.


[1] https://aur.archlinux.org/packages/extract-xiso/
[2] https://aur.archlinux.org/packages/extract-xiso-somski/


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

2014-02-09 Thread 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
* 25 packages missing signoffs
* 4 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] (21 total) ==

* acpi_call-1.1.0-2 (i686)
0/1 signoffs
* bbswitch-0.8-6 (i686)
0/1 signoffs
* dssi-vst-0.9.2-3 (i686)
0/1 signoffs
* exim-4.82-2 (i686)
0/1 signoffs
* qtractor-0.5.12-2 (i686)
0/1 signoffs
* r8168-8.037.00-7 (i686)
0/1 signoffs
* rt3562sta-2.4.1.1-52 (i686)
0/1 signoffs
* tp_smapi-0.41-44 (i686)
0/1 signoffs
* vhba-module-20130607-24 (i686)
0/1 signoffs
* virtualbox-modules-4.3.6-5 (i686)
0/1 signoffs
* xjadeo-0.7.6-2 (i686)
0/1 signoffs
* acpi_call-1.1.0-2 (x86_64)
0/2 signoffs
* bbswitch-0.8-6 (x86_64)
0/2 signoffs
* exim-4.82-2 (x86_64)
0/2 signoffs
* qtractor-0.5.12-2 (x86_64)
0/2 signoffs
* r8168-8.037.00-7 (x86_64)
0/2 signoffs
* rt3562sta-2.4.1.1-52 (x86_64)
0/2 signoffs
* tp_smapi-0.41-44 (x86_64)
0/2 signoffs
* vhba-module-20130607-24 (x86_64)
0/2 signoffs
* virtualbox-modules-4.3.6-5 (x86_64)
0/2 signoffs
* xjadeo-0.7.6-2 (x86_64)
0/2 signoffs

== Incomplete signoffs for [unknown] (4 total) ==

* libnftnl-1.0.0-1 (i686)
0/1 signoffs
* nftables-0.099-1 (i686)
0/1 signoffs
* libnftnl-1.0.0-1 (x86_64)
0/2 signoffs
* nftables-0.099-1 (x86_64)
0/2 signoffs


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

* libnftnl-1.0.0-1 (i686), since 2014-01-20
* libnftnl-1.0.0-1 (x86_64), since 2014-01-20
* nftables-0.099-1 (i686), since 2014-01-20
* nftables-0.099-1 (x86_64), since 2014-01-20


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

1. allan - 11 signoffs
2. eric - 3 signoffs
3. bpiotrowski - 1 signoffs
4. foutrelis - 1 signoffs



[aur-general] Alfresco - many packages, some disowned... which are needed?

2014-02-09 Thread Oliver Bandel


Hello,

I looked up alfresco in AUR package search.
I found a lot of packages, some undermaintenance,others not.
At least one of the maintained packages is flagged outdated
since about 10 months.

Someone here, who knows more about this bunch of packages?
Should seome become deleted, updatedor become baclk under maintenance?

https://aur.archlinux.org/packages/?O=0K=alfresco


Ciao,
   Oliver



Re: [aur-general] Merge request: sm-ssc-hg into stepmania-git

2014-02-09 Thread Jonathan Steel
On Sat 08 Feb 2014 at 18:49, Devin J. Pohly wrote:
 Please merge sm-ssc-hg [0] (orphaned) into stepmania-git [1].  StepMania
 development has moved to GitHub, and the sm-ssc name is long outdated.
 
 0: https://aur.archlinux.org/packages/sm-ssc-hg/
 1: https://aur.archlinux.org/packages/stepmania-git/

Merged, thanks.

-- 
Jonathan Steel


pgpBxURPdziQt.pgp
Description: PGP signature


Re: [aur-general] AUR Requests

2014-02-09 Thread Jonathan Steel
On Sun 02 Feb 2014 at 13:24, Rob McCathie wrote:
 On Sun, Feb 2, 2014 at 10:53 AM, Michael Schubert mschu@gmail.com wrote:
  Hi,
 
  (Maintainers, if any, are in CC.)
 
  Could you please merge:
 
  https://aur.archlinux.org/packages/python2-imaging/ -
  https://aur.archlinux.org/packages/python2-imaging-alt/ **
  Reason: PIL is being phased out by pillow; 1st is orphan and 2nd one not to
  be replaced like in [community]
  Maintainer: please add a replaces=() flag, it should replace python2-imaging
  and not python-imaging
 [...]
 I agree python2-imaging should be deleted or merged into
 python2-imaging-alt

I don't agree that this should happen.

 since when a user installs python2-imaging the
 next time they go to system update pacman of course offers to replace
 it with python2-pillow. (Yes I know they /could/ just use IgnorePkg=
 in pacman.conf)

I do agree this is what you should do if you want to continue using it,
rather than upload an incorrectly named, duplicate package. I will remove
python2-imaging-alt.

-- 
Jonathan Steel


pgp7E0otGza6w.pgp
Description: PGP signature


Re: [aur-general] AUR Requests

2014-02-09 Thread Jonathan Steel
On Sat 01 Feb 2014 at 23:53, Michael Schubert wrote:
 Hi,
 
 (Maintainers, if any, are in CC.)
 
 Could you please merge:
 [...]
 
 https://aur.archlinux.org/packages/python2-socksipy-branch/ -
 https://aur.archlinux.org/packages/python2-socks/
 https://aur.archlinux.org/packages/python-socksipy-branch/ ** -
 https://aur.archlinux.org/packages/python-socks/
 Reason: socksipy and -branch are dead, socks is maintained and has same API
 Maintainer: please let me know if you'd like to maintain the new package/why
 we should keep a dead branch

Merged.
 
 And remove:
 
 https://aur.archlinux.org/packages/sundials25/ **
 Reason: sundials=2.5 current and available, package installs into /usr
 directly and should not be used
 [...]

Removed, thanks.

-- 
Jonathan Steel


pgpjeyyhJOb4v.pgp
Description: PGP signature


Re: [aur-general] Package deletion request

2014-02-09 Thread Xyne
On 2014-02-09 03:35 -0500
Joseph Carta wrote:

Hi. I've just claimed ownership to and updated the previously orphaned 
package extract-xiso [1]. Since the author of this program incorporated 
the somski mod into it, the package extract-xiso-somski [2] has been 
made redundant and should be deleted.

[1] https://aur.archlinux.org/packages/extract-xiso/
[2] https://aur.archlinux.org/packages/extract-xiso-somski/

merged, thanks


[aur-general] python-mock in AUR and community

2014-02-09 Thread François Boulogne
Hi,

I want to report that python-mock is in community and AUR.

Thank you.

-- 
François Boulogne.
http://www.sciunto.org
GPG fingerprint: 25F6 C971 4875 A6C1 EDD1  75C8 1AA7 216E 32D5 F22F



[aur-general] Code review request: new PKGBUILD omodoro

2014-02-09 Thread Oliver Kraitschy

Hello trusty Arch people,

i just created my first PKGBUILD for the little python script omodoro 
i wrote. It would be nice if you guys could do a code review to approve 
the PKGBUILD i wrote for the AUR.


The PKGBUILD is here:

http://www.okraits.de/upload/omodoro/PKGBUILD

Any feedback/criticism is appreciated!

Greetings,

Oliver



[aur-general] Merge request

2014-02-09 Thread Zack Gold
I've moved 'boto-git' to 'python2-boto-git' because it's intended for
Python 2. I'd like to now merge boto-git with python2-boto-git.


Re: [aur-general] Code review request: new PKGBUILD omodoro

2014-02-09 Thread David Phillips
Related to (4): I've got a PKGBUILD
(https://aur.archlinux.org/packages/pa/passgen/PKGBUILD) which points
to a git repo, but *not* using a git://xyz.git url. Instead, I'm
using the format
https://github.com/phillid/passgen/archive/master.zip; - should this
package have -git appended? I'm thinking it doesn't need the -git
suffix because it's pulled over HTTP and doesn't need git... What's
the convention on this?

Cheers.

On 10/02/2014, Doug Newgard scimmi...@outlook.com wrote:
 
 Date: Mon, 10 Feb 2014 00:15:55 +0100
 From: okra...@arcor.de
 To: aur-general@archlinux.org
 Subject: [aur-general] Code review request: new PKGBUILD omodoro

 Hello trusty Arch people,

 i just created my first PKGBUILD for the little python script omodoro
 i wrote. It would be nice if you guys could do a code review to approve
 the PKGBUILD i wrote for the AUR.

 The PKGBUILD is here:

 http://www.okraits.de/upload/omodoro/PKGBUILD

 Any feedback/criticism is appreciated!

 Greetings,

 Oliver

 1. Your pkgver function doesn't work. pkgver should not be random, it should
 increase with each commit to the repo.
 2. Don't have it depend on an old, replaced package (python3). You just want
 'python'.
 3. Please quote paths that contain a variable like $pkgdir.
 4. You should append -git to the pkgname when you're pulling from git
 master.
 5. Why bother to define _gitname if it's the same as pkgname? Since you
 should be changing pkgname, _gitname can make sense or you can just do
 ${pkgname%-git} and get the same thing without having to use an extra
 variable.

 Those are my suggestions, nothing too serious.
 


-- 
David Phillips


Re: [aur-general] Code review request: new PKGBUILD omodoro

2014-02-09 Thread Anatol Pomozov
Hi

On Sun, Feb 9, 2014 at 9:08 PM, David Phillips dbphillip...@gmail.com wrote:
 Related to (4): I've got a PKGBUILD
 (https://aur.archlinux.org/packages/pa/passgen/PKGBUILD) which points
 to a git repo, but *not* using a git://xyz.git url. Instead, I'm
 using the format
 https://github.com/phillid/passgen/archive/master.zip; - should this
 package have -git appended?

Yes, it should. The -git suffix indicates that the package is built
from VCS. master.zip source file *also* comes from VCS, from git
repo and means current HEAD of master branch. The main point of VCS
package is that the source is moving target and it changes
independently from package maintainer. And it differs from 'versioned'
package where sources are changed only when maintainer updates
PKGBUILD.

Using master.zip is a bad idea because:
 - Once master.zip downloaded it is cached in the local directory. If
you run makepkg again nothing will be redownloaded even if upstream
repository has changed.
 - Updating local git repository is more effective as it fetches only
the latest changes. Thus package rebuild is faster.


So what you want for passgen:
 - rename it to passgen-git
 - use git repository for sources=() instead of 'master.zip'
 - add 'git' to makedepends
 - add proper pkgver()
 - use 'SKIP' for sha1sum as project head can change at any moment


 I'm thinking it doesn't need the -git
 suffix because it's pulled over HTTP and doesn't need git... What's
 the convention on this?

 Cheers.

 On 10/02/2014, Doug Newgard scimmi...@outlook.com wrote:
 
 Date: Mon, 10 Feb 2014 00:15:55 +0100
 From: okra...@arcor.de
 To: aur-general@archlinux.org
 Subject: [aur-general] Code review request: new PKGBUILD omodoro

 Hello trusty Arch people,

 i just created my first PKGBUILD for the little python script omodoro
 i wrote. It would be nice if you guys could do a code review to approve
 the PKGBUILD i wrote for the AUR.

 The PKGBUILD is here:

 http://www.okraits.de/upload/omodoro/PKGBUILD

 Any feedback/criticism is appreciated!

 Greetings,

 Oliver

 1. Your pkgver function doesn't work. pkgver should not be random, it should
 increase with each commit to the repo.
 2. Don't have it depend on an old, replaced package (python3). You just want
 'python'.
 3. Please quote paths that contain a variable like $pkgdir.
 4. You should append -git to the pkgname when you're pulling from git
 master.
 5. Why bother to define _gitname if it's the same as pkgname? Since you
 should be changing pkgname, _gitname can make sense or you can just do
 ${pkgname%-git} and get the same thing without having to use an extra
 variable.

 Those are my suggestions, nothing too serious.


 --
 David Phillips


Re: [aur-general] Merge request

2014-02-09 Thread Felix Yan
On Sunday, February 09, 2014 22:25:01 Zack Gold wrote:
 I've moved 'boto-git' to 'python2-boto-git' because it's intended for
 Python 2. I'd like to now merge boto-git with python2-boto-git.

Merged. Please include links to packages next time, thanks.

Regards,
Felix Yan

signature.asc
Description: This is a digitally signed message part.


Re: [aur-general] Code review request: new PKGBUILD omodoro

2014-02-09 Thread David Phillips
Right, that makes sense. In that case, I'll just switch it back to
using static source tarballs.

Thanks for your help.

On 10/02/2014, Anatol Pomozov anatol.pomo...@gmail.com wrote:
 Hi

 On Sun, Feb 9, 2014 at 9:08 PM, David Phillips dbphillip...@gmail.com
 wrote:
 Related to (4): I've got a PKGBUILD
 (https://aur.archlinux.org/packages/pa/passgen/PKGBUILD) which points
 to a git repo, but *not* using a git://xyz.git url. Instead, I'm
 using the format
 https://github.com/phillid/passgen/archive/master.zip; - should this
 package have -git appended?

 Yes, it should. The -git suffix indicates that the package is built
 from VCS. master.zip source file *also* comes from VCS, from git
 repo and means current HEAD of master branch. The main point of VCS
 package is that the source is moving target and it changes
 independently from package maintainer. And it differs from 'versioned'
 package where sources are changed only when maintainer updates
 PKGBUILD.

 Using master.zip is a bad idea because:
  - Once master.zip downloaded it is cached in the local directory. If
 you run makepkg again nothing will be redownloaded even if upstream
 repository has changed.
  - Updating local git repository is more effective as it fetches only
 the latest changes. Thus package rebuild is faster.


 So what you want for passgen:
  - rename it to passgen-git
  - use git repository for sources=() instead of 'master.zip'
  - add 'git' to makedepends
  - add proper pkgver()
  - use 'SKIP' for sha1sum as project head can change at any moment


 I'm thinking it doesn't need the -git
 suffix because it's pulled over HTTP and doesn't need git... What's
 the convention on this?

 Cheers.

 On 10/02/2014, Doug Newgard scimmi...@outlook.com wrote:
 
 Date: Mon, 10 Feb 2014 00:15:55 +0100
 From: okra...@arcor.de
 To: aur-general@archlinux.org
 Subject: [aur-general] Code review request: new PKGBUILD omodoro

 Hello trusty Arch people,

 i just created my first PKGBUILD for the little python script omodoro
 i wrote. It would be nice if you guys could do a code review to approve
 the PKGBUILD i wrote for the AUR.

 The PKGBUILD is here:

 http://www.okraits.de/upload/omodoro/PKGBUILD

 Any feedback/criticism is appreciated!

 Greetings,

 Oliver

 1. Your pkgver function doesn't work. pkgver should not be random, it
 should
 increase with each commit to the repo.
 2. Don't have it depend on an old, replaced package (python3). You just
 want
 'python'.
 3. Please quote paths that contain a variable like $pkgdir.
 4. You should append -git to the pkgname when you're pulling from git
 master.
 5. Why bother to define _gitname if it's the same as pkgname? Since you
 should be changing pkgname, _gitname can make sense or you can just do
 ${pkgname%-git} and get the same thing without having to use an extra
 variable.

 Those are my suggestions, nothing too serious.


 --
 David Phillips



-- 
David Phillips