- Aur-general - lists.archlinux.org

Re: [aur-general] Proofreading request
by Evan Teitelman 27 Aug '13

27 Aug '13

On Mon, Aug 26, 2013 at 11:17:16PM +0200, Cl?ment Junca wrote: > Could someone have a look at the attached package, please ? It's my first > AUR package written from scratch. I made some changes to your PKGBUILD file. Here they are: # Maintainer: Clément Junca <cju.arch(a)gmail.com> # Remove unused variables. pkgname=feather-git _gitname=feather pkgver=19.3a91bc7 pkgrel=1 pkgdesc="A tarsnap script that performs and maintains a set of backups as defined by a yaml configuration file" arch=('any') url="https://github.com/danrue/feather" license=('custom:beerware') depends=('tarsnap' 'python2-yaml') # Note: The quotation marks are not necessary here but they are an impromptu # standard---probably for reasons of consistency. makedepends=('git') source=('git://github.com/danrue/feather.git' 'feather.patch') md5sums=('SKIP' '61ca0090775f0f7910dd525a19ac5540') pkgver() { cd $_gitname echo $(git rev-list --count HEAD).$(git rev-parse --short HEAD) # No need to reset the current working directory. } # Patch in the `prepare` function. prepare() { # Use the full path. cd "$srcdir/$_gitname" # The `|| exit 1` part is not necessary. `makepkg` traps errors. # You make come across `|| return 1` on the AUR though. It used to be necessary. patch -p1 -i ../feather.patch } # Note: Only the `package` function is mandatory. package() { # Note: Use double quotation marks around `$pkgdir` and `$srcdir`. # These variables store absolute paths. Some people have spaces or special # characters in their build paths. cd "$srcdir/$_gitname" # Using `install` to create directories is common. I believe `makepkg` sets # `umask` appropriately though so `makedir` should work. install -dm755 "$pkgdir/etc" install -dm755 "$pkgdir/usr/bin" install -dm755 "$pkgdir/usr/share/licenses/$pkgname" # Whitespace is nice. # The `-D` switch is not necessary here. install -m755 feather "$pkgdir/usr/bin/feather" install -m644 feather.yaml.dist "$pkgdir/etc/feather.yaml" # You should put LICENSE in the `source` array. install -m644 ../../LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE" } # Modelines are an eyesore. # I have this in my Vim configuration: # autocmd BufRead,BufNewFile, PKGBUILD setlocal tabstop=2 shiftwidth=2 expandtab # vim:set ts=2 sw=2 et:

2 1

Re: [aur-general] Proofreading request
by Evan Teitelman 27 Aug '13

27 Aug '13

On Mon, Aug 26, 2013 at 11:17:16PM +0200, Cl?ment Junca wrote: > Could someone have a look at the attached package, please ? It's my first > AUR package written from scratch. A few additional notes: - Your patch is small. You can use `sed` instead. sed -i 's|env python|env python2|' feather sed -i 's|binpath: /usr/local/bin/|binpath: /usr/bin/|' feather.yaml.dist - Here is a fixed and cleaned version of your `config.install` file: # You should probably run this on install, not on upgrade. # If you want to run this on both install and upgrade, you can do this: # post_install() { # post_upgrade # } post_install() { # Install file output should be dense. echo 'Feather is designed to be run from cron like this:' # The quotation marks are necessary here. Without them, the shell will expand the asterisks. echo ' */5 * * * * /usr/bin/feather /etc/feather.yaml' # 'shall' gives the impression that the file will be updated automatically. echo 'Configuration file /etc/feather.yaml must be updated before running.' } - It is common to name install files after the packages they belong to. You should consider naming your install file `feather.install` or `feather-git.install`.

1 0

[aur-general] Inactive until 18. September
by Thorsten Töpper 27 Aug '13

27 Aug '13

Hello, I will be inactive until the 18th September 2013. I voted in any of the currently open votes, so count me into the quorum. The reason for my inactivity is, that I need to focus on my thesis until I hand it in. I won't be completely gone, I just won't invest much time into reading and writing mails or spent much time online at all. Please take care of my packages and be aware that john is based on the community enhanced version and not the official free version that lacks lots of features. (1.7.9 with jumbo patches is ahead of a plain 1.8.0 but includes its features.) Cheers, Thorsten

1 0

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 27 Aug '13

27 Aug '13

=== 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 * 1 fully signed off package * 7 packages missing signoffs * 0 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] (7 total) == * devil-1.7.8-17 (i686) 0/1 signoffs * mplayer-vaapi-36265-4 (i686) 0/1 signoffs * synfig-0.64.0-7 (i686) 0/1 signoffs * devil-1.7.8-17 (x86_64) 0/2 signoffs * mplayer-vaapi-36265-4 (x86_64) 0/2 signoffs * netsurf-3.0-4 (x86_64) 1/2 signoffs * synfig-0.64.0-7 (x86_64) 0/2 signoffs == Completed signoffs (1 total) == * netsurf-3.0-4 (i686) == Top five in signoffs in last 24 hours ==

1 0

Re: [aur-general] Request name change/orphaing of drawterm
by Marshall Conover 26 Aug '13

26 Aug '13

Hello aur-general, I messaged the list about two weeks about the drawterm[1] package, saying that I had flagged the package out of date, uploaded a working package build to the page as a comment, and attempted to contact the owner of the package two weeks prior; I then asked that the package be orphaned/updated with my working package build. I was asked by speps to send an email to the package maintainer at his gmail address, as the domain for his other email address seems out of sorts; that address was actually the one I had originally sent it to, but I figured I"d give it more time and check IRC and speps suggested. I have still been unable to contact the prior maintainer. I have uploaded a new package, drawterm-hg[2], which (as far as I can tell) meets the criteria for a package on the AUR, and fixes the issues with the old drawterm package (which also used mercurial, but didn't have it in the name). As the new package seems to hit all the points needed, I believe the old drawterm should be deleted. Let me know if anything else is required! Thanks, Marshall Conover [1] https://aur.archlinux.org/packages/drawterm/ [2] https://aur.archlinux.org/packages/drawterm-hg/ <https://aur.archlinux.org/packages/drawterm/>-- Have a good day, Marshall Conover

2 1

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 26 Aug '13

26 Aug '13

=== 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 * 1 fully signed off package * 7 packages missing signoffs * 0 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] (7 total) == * devil-1.7.8-17 (i686) 0/1 signoffs * mplayer-vaapi-36265-4 (i686) 0/1 signoffs * synfig-0.64.0-7 (i686) 0/1 signoffs * devil-1.7.8-17 (x86_64) 0/2 signoffs * mplayer-vaapi-36265-4 (x86_64) 0/2 signoffs * netsurf-3.0-4 (x86_64) 1/2 signoffs * synfig-0.64.0-7 (x86_64) 0/2 signoffs == Completed signoffs (1 total) == * netsurf-3.0-4 (i686) == Top five in signoffs in last 24 hours == 1. allan - 4 signoffs 2. andyrtr - 1 signoffs

1 0

[aur-general] Merge request: beclock into bekwinfx-git
by David Strobach 26 Aug '13

26 Aug '13

Please merge beclock[1] int bekwinfx-git[2]. The BeClock effect has been incorporated in and superseded by the BE::KWinFX effect suite. It is no longer maintained and is incompatible with KDE >= 4.10. [1] https://aur.archlinux.org/packages/beclock [2] https://aur.archlinux.org/packages/bekwinfx-git

2 1

[aur-general] Unused account on BBS and AUR web interface
by William Gathoye 25 Aug '13

25 Aug '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, I would like to contribute to the AUR, but it appears the account 'wget' has already been registrered, but no one seems to currently use it. It looks like someone has asked for a password reset but hasn't clicked on the confirmation link from the email yet. Would it be possible for you to unlock this account and release this username for me? I'm experiencing the same issue with the BBS forum. I got 'Invalid username' as a response from the registration form. It would be nice if I could keep the same e-dentity for the ArchLinux community, as I'm using the same nickname for the communities where I'm getting involved in. Regards, - -- William Gathoye <william(a)gathoye.be> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJRhSpxAAoJEA595SwE1xaDaEYQAMaVsrNPep/Gm/UXSkCr0dlm 84upblK10lQcjiq3BeUU4sSrPFWq1ewVR6tr2w86VuzPG2Pa8jpwbJ53ZomsiCP4 2MFn6OqQ9aDWb2ghSEyTmY/588Y64PXMV4H7bAtTE6JXPDh3S0ekLF47cWY23bxe LvRDCvgxwPGERSHEW1YD2bOUoODiB8THYBQdZWZZsy6ule5/UAKsu0G4y5gvBlqT Hfk/pzdS5BnNRx11mUVceqZkRy5pgfjNHjGa2ZvRHlycPnEnwM7fMXraDAJ5OH7Q JW+cxMrQQgtd16iUt7V1n2e3f44lSytG8CP32n5ioXPAz0INz/FPbGl0NVeja+MP rcpgvYD9ql+685wrRcO+a5iyimjb6cBaxFGKCD2t/cJrQTL5B4dne8BakbMLChLa ajtpVLnCvFefV4FKkRKfxDTxENIhEW3HD9cuJrKIJM/ZNH4sYdfj5Uf+iAFI5Gmb 7Fr7iqiiA3KtMF/tQ+VxNXdTObVuTbeTAzZPzQOaYsL05Ii9lLg0tyuphDpM90aK OVDgfo618YAEvIe9WMKrWrSVkQ3FuD4yNOoWhDis0pF+fYi0S2vWo39NRtZhgaWr kWS0ydcYQXh6r9szsiOc2wfEWHWL9loAWQlcA0/nuupxypp35QH5BQG1LWWj70l1 dGchvAA74CJR4mGXuabx =jSyj -----END PGP SIGNATURE-----

5 8

Re: [aur-general] request merge vapoursynth-git into vapoursynth
by danielwallace 25 Aug '13

25 Aug '13

You could also keep both, and just specify the fragment in the one without -git in the name. https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines#VCS_sources Gtmanfred

2 1

Re: [aur-general] request merge vapoursynth-git into vapoursynth
by danielwallace 25 Aug '13

25 Aug '13

So, since you are using the source straight from the git repository, we should be merging into the -git version? Also, there is no need to use echo in your pkgver, just run the command in the sub shell Gtmanfred -------- Original message -------- From: SpinFlo <sl1pkn07(a)gmail.com> Date: 08/25/2013 1:36 PM (GMT-06:00) To: "Discussion about the Arch User Repository (AUR)" <aur-general(a)archlinux.org> Subject: [aur-general] request merge vapoursynth-git into vapoursynth hi please merge https://aur.archlinux.org/packages/vapoursynth-git<https://aur.archlinux.org/packages/vapoursynth/> into https://aur.archlinux.org/packages/vapoursynth/ vapursynth package use SVN (tag branch), this method not longer available. i change to GIT because this project don't use "zip" sources greetings

1 0

[aur-general] Disown request
by Iván Pulido 25 Aug '13

25 Aug '13

Hello, I'd like to request to disown the package dislin in AUR https://aur.archlinux.org/packages/dislin/ . The package has been flagged out of date for over three months now and I already sent a fix/update for the PKGBUILD (with the username "mefistofeles") and the developer has not done anything. I'd like to adopt the package if possible. Thanks.

2 1

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 25 Aug '13

25 Aug '13

=== 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 * 1 fully signed off package * 7 packages missing signoffs * 0 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] (7 total) == * devil-1.7.8-17 (i686) 0/1 signoffs * mplayer-vaapi-36265-4 (i686) 0/1 signoffs * synfig-0.64.0-7 (i686) 0/1 signoffs * devil-1.7.8-17 (x86_64) 0/2 signoffs * mplayer-vaapi-36265-4 (x86_64) 0/2 signoffs * netsurf-3.0-4 (x86_64) 1/2 signoffs * synfig-0.64.0-7 (x86_64) 0/2 signoffs == Completed signoffs (1 total) == * netsurf-3.0-4 (i686) == Top five in signoffs in last 24 hours == 1. dan - 2 signoffs

1 0

[aur-general] Delete request [Aug 24]
by Limao Luo 25 Aug '13

25 Aug '13

Can a TU delete https://aur.archlinux.org/packages/python-pylast/ ? python2-pylast is in [community], and python-pylast doesn't build a Python 3 version of the library. Thanks. - luolimao

4 3

[aur-general] Removal request: lmms-vst
by Martti Kühne 24 Aug '13

24 Aug '13

Hi list There's no point in having [0] around, since community/lmms passes -USE=vst to compilation... cheers! mar77i [0] https://aur.archlinux.org/packages/lmms-vst

2 1

[aur-general] Merging request.
by Jagmjp Janpgm 24 Aug '13

24 Aug '13

Could elementary-icons-bzr be merged into elementary-icon-theme-bzr to be in sync with elementary-icon-theme from [community] ?

4 4

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 24 Aug '13

24 Aug '13

=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 2 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 1 fully signed off package * 21 packages missing signoffs * 0 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.) == New packages in [community-testing] in last 24 hours (2 total) == * fcitx-mozc-1.11.1502.102-1 (i686) * fcitx-mozc-1.11.1502.102-1 (x86_64) == Incomplete signoffs for [community] (21 total) == * bbswitch-0.7-11 (i686) 0/1 signoffs * devil-1.7.8-17 (i686) 0/1 signoffs * fcitx-mozc-1.11.1502.102-1 (i686) 0/1 signoffs * mplayer-vaapi-36265-4 (i686) 0/1 signoffs * r8168-8.036.00-8 (i686) 0/1 signoffs * rt3562sta-2.4.1.1-41 (i686) 0/1 signoffs * synfig-0.64.0-7 (i686) 0/1 signoffs * tp_smapi-0.41-32 (i686) 0/1 signoffs * vhba-module-20130607-11 (i686) 0/1 signoffs * virtualbox-modules-4.2.16-8 (i686) 0/1 signoffs * bbswitch-0.7-11 (x86_64) 0/2 signoffs * devil-1.7.8-17 (x86_64) 0/2 signoffs * fcitx-mozc-1.11.1502.102-1 (x86_64) 0/2 signoffs * mplayer-vaapi-36265-4 (x86_64) 0/2 signoffs * netsurf-3.0-4 (x86_64) 1/2 signoffs * r8168-8.036.00-8 (x86_64) 0/2 signoffs * rt3562sta-2.4.1.1-41 (x86_64) 0/2 signoffs * synfig-0.64.0-7 (x86_64) 0/2 signoffs * tp_smapi-0.41-32 (x86_64) 0/2 signoffs * vhba-module-20130607-11 (x86_64) 0/2 signoffs * virtualbox-modules-4.2.16-8 (x86_64) 0/2 signoffs == Completed signoffs (1 total) == * netsurf-3.0-4 (i686) == Top five in signoffs in last 24 hours == 1. eric - 9 signoffs

1 0

[aur-general] Removal of AUR packages brother-mfc260c-lpr and brother-mfc260c-cupswrapper
by Tobias Böhm 23 Aug '13

23 Aug '13

Hello, today I have installed drivers for the Brother MFC260C and found two packages which might be worth to be removed. The two packages are: brother-mfc260c-lpr https://aur.archlinux.org/packages/brother-mfc260c-lpr/ brother-mfc260c-cupswrapper https://aur.archlinux.org/packages/brother-mfc260c-cupswrapper/ The reasons are that both of this packages are currently not working, as the source url is not working any more. Both packages are orphaned as well. Additionally there is a working package which provides both drivers, thus supersedes the two mentioned ones: brother-mfc-260c https://aur.archlinux.org/packages/brother-mfc-260c/ Thank you for your efforts. Best Regards, Tobias

2 1

[aur-general] Removal request: kdeplasma-applets-qstardict
by A Rojas 23 Aug '13

23 Aug '13

https://aur.archlinux.org/packages/kdeplasma-applets-qstardict/ It is in [community] now

2 1

[aur-general] Disown request : python2-logbook
by Laël Guillemenot 23 Aug '13

23 Aug '13

Please disown python2-logbook https://aur.archlinux.org/packages/python2-logbook/ The package is mark as out-of-date since 2012-11-17. No response of maintainer to mail I had send two weeks ago.

2 1

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 23 Aug '13

23 Aug '13

=== 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 * 1 fully signed off package * 19 packages missing signoffs * 0 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] (19 total) == * bbswitch-0.7-11 (i686) 0/1 signoffs * devil-1.7.8-17 (i686) 0/1 signoffs * mplayer-vaapi-36265-4 (i686) 0/1 signoffs * r8168-8.036.00-8 (i686) 0/1 signoffs * rt3562sta-2.4.1.1-41 (i686) 0/1 signoffs * synfig-0.64.0-7 (i686) 0/1 signoffs * tp_smapi-0.41-32 (i686) 0/1 signoffs * vhba-module-20130607-11 (i686) 0/1 signoffs * virtualbox-modules-4.2.16-8 (i686) 0/1 signoffs * bbswitch-0.7-11 (x86_64) 0/2 signoffs * devil-1.7.8-17 (x86_64) 0/2 signoffs * mplayer-vaapi-36265-4 (x86_64) 0/2 signoffs * netsurf-3.0-4 (x86_64) 1/2 signoffs * r8168-8.036.00-8 (x86_64) 0/2 signoffs * rt3562sta-2.4.1.1-41 (x86_64) 0/2 signoffs * synfig-0.64.0-7 (x86_64) 0/2 signoffs * tp_smapi-0.41-32 (x86_64) 0/2 signoffs * vhba-module-20130607-11 (x86_64) 0/2 signoffs * virtualbox-modules-4.2.16-8 (x86_64) 0/2 signoffs == Completed signoffs (1 total) == * netsurf-3.0-4 (i686) == Top five in signoffs in last 24 hours == 1. andyrtr - 6 signoffs 2. allan - 5 signoffs 3. lcarlier - 4 signoffs 4. jsteel - 2 signoffs 5. heftig - 2 signoffs

1 0

[aur-general] [tu-bylaws][PATCH]
by Xyne 22 Aug '13

22 Aug '13

Hi, Here's a patch for the TU-bylaws that resulted from discussion in the previous thread: https://mailman.archlinux.org/pipermail/aur-general/2013-August/024745.html I hope this is in the correct format. I haven't used git send-email because I still haven't configured it and didn't want to risk doing something stupid in a hurry. For those of you who prefer reading the resulting document, I have attached the source file and the generated HTML file. Please read through the previous thread for an explanation of the changes. Let the discussion period begin! From 8328526fc0fef469d9edb1abf0f0448c2f440e90 Mon Sep 17 00:00:00 2001 From: Xyne <xyne(a)archlinux.ca> Date: Wed, 7 Aug 2013 13:55:37 +0000 Subject: [PATCH] Following discussion on aur-general (https://mailman.archlinux.org/pipermail/aur-general/2013-August/024745.html) * remove distinction between "active" and "inactive" TUs * update all clauses affected by this change, most importantly the definition of quorum * update conditions for special removal of a TU * use abbreviations consistently through the document * add missing links to instances of "aur-general" * various changes to correct or improve English throughout the document --- tu-bylaws.txt | 122 ++++++++++++++++++++++++---------------------------------- 1 file changed, 50 insertions(+), 72 deletions(-) diff --git a/tu-bylaws.txt b/tu-bylaws.txt index 991d683..4c0699b 100644 --- a/tu-bylaws.txt +++ b/tu-bylaws.txt @@ -1,7 +1,7 @@ Trusted User Bylaws =================== Trusted Users <aur-general(a)archlinux.org> -1.2, 18 January 2011 +1.3, 2013-08-07 Summary ------- @@ -12,7 +12,7 @@ duties. Mission ------- -The Trusted Users serve the following purposes: +The Trusted Users (TUs) serve the following purposes: 1. Maintain +[community]+ as an intermediary between Archlinux's official repositories and the +unsupported+ package collection in the AUR. @@ -22,10 +22,10 @@ repositories and the +unsupported+ package collection in the AUR. Bylaws ------ -The bylaws are written to be consistent with the mission of the Trusted Users, -and to ensure that Trusted Users continue to be *Trusted* in the future. They -are also written with the intent to keep the Trusted User organization a -thriving one, fulfilling their purpose. +The bylaws are written to be consistent with the mission of the TUs, +and to ensure that TUs continue to be *Trusted* in the future. They +are also written with the intent to keep the TU organization a +thriving one, fulfilling its purpose. Standard Voting Procedure ------------------------- @@ -35,31 +35,23 @@ accept or reject proposals regarding TU affairs. SVP begins with a proposal, for example the addition of a TU or an amendment to the bylaws. The proposal should be clear and concise and it must be posted on -the aur-general mailing list (aur-general). The proposal must also be worded +the https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general mailing list] (aur-general). The proposal must also be worded unambiguously, and such that a YES or NO answer may be given. -The discussion period begins when the proposal is posted on aur-general. The +The discussion period begins when the proposal is posted on https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general]. The duration of the discussion period shall be 5 full days UNLESS otherwise stated in a section of the bylaws pertaining to the proposal. Official discussion -shall take place on aur-general. During the discussion period, votes shall not +shall take place on https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general]. During the discussion period, votes shall not be cast. The voting period begins when the discussion period ends. The duration of the voting period shall be 7 full days UNLESS otherwise stated in a section of the bylaws pertaining to the proposal. During the voting period, TUs may vote YES, -NO or ABSTAIN. Votes shall be cast under the Trusted User section of the AUR -homepage. At the end of the voting period, all votes shall be tallied. - -In the context of SVP, TUs are considered active if they are marked as active -when the voting period ends. - -Quorum shall be 66% of all active TUs and participation shall be measured by -the sum of YES, NO and ABSTAIN votes, UNLESS otherwise stated in a section of -the bylaws pertaining to the proposal. +NO or ABSTAIN. Votes shall be cast under the Trusted User section of the https://aur.archlinux.org/[AUR website]. At the end of the voting period, all votes shall be tallied. The proposal is accepted if EITHER -1. the number of YES votes is greater than half the number of active TUs OR +1. the number of YES votes is greater than half the number of TUs OR 2. quorum has been established and the number of YES votes is greater than the number of NO votes @@ -68,8 +60,7 @@ UNLESS otherwise stated in a section of the bylaws pertaining to the proposal. The proposal is rejected if EITHER -1. the number of NO votes is greater than or equal to half the number of active -TUs OR +1. the number of NO votes is greater than or equal to half the number of TUs OR 2. quorum was established and the number of NO votes is greater than or equal to the number of YES votes @@ -90,47 +81,20 @@ second SVP then it shall be rejected. Quorum ------ -This section deals with quorums, and the consequences for those that repeatedly -keep the group from meeting them. - -Quorums were established to make sure that all TUs are having a say in the -matters that they vote on, and to ensure that TUs remain active in the job that -they have taken on. All active TUs should be participating in discussions and -voting procedures in order to continue meeting the quorums. For this reason, -active TUs that keep quorum from being established on a voting procedure for -three consecutive voting procedures (they need not be on the same motion) are -automatically brought up for removal procedure, by reason of unwarranted -inactivity. - -Active vs. Inactive -------------------- - -A Trusted User will have an activity status at all times. Only two statuses -exist, +active+, and +inactive+. A TU should remain active whenever possible, -and avoid being inactive, especially without declaring it. - -An active TU participates in all TU tasks and activities normally. - -A TU may declare themselves inactive, for instance if they are going on -vacation, by sending a message to -https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general]. TUs -are expected to step down altogether if they plan on becoming inactive for a -period longer than 2 months. It is expected that while inactive, a TU is -unable to maintain packages and partake in normal TU activities. They are -exempt from quorums and in fact cannot vote. A TU becomes active again at the -stated date on their original inactivity declaration, or when they declare -themselves such. +Quorums were established to ensure that all matters decided by vote are +representative of the TU group. All TUs are expected to participate in all votes +and the preceding discussions whenever possible. -If a TU becomes inactive without declaring it, "disappears", someone must -motion for their removal for reason of unwarranted and undeclared inactivity, -and the normal procedure for the motion is followed. +Quorum shall be 66% of all TUs and participation shall be measured by +the sum of YES, NO and ABSTAIN votes, UNLESS otherwise stated in a section of +the bylaws pertaining to the proposal. Addition of a TU ---------------- -The addition of a Trusted User may occur at any time. +The addition of a TU may occur at any time. -In order to become a Trusted User, one must first find a sponsoring active TU, +In order to become a TU, one must first find a sponsoring TU, and arrange privately with them to announce their candidacy on the https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general] mailing list. Following the announcement, standard voting procedure commences with a @@ -146,32 +110,46 @@ User for a period of three months. Removal of a TU --------------- -The removal of a Trusted User may also occur at any time. +The removal of a TU may also occur at any time. -A motion must be made by at least two active Trusted Users for the removal of a -Trusted User. The motion must be sent to +A motion must be made by at least two TUs for the removal of a +TU. The motion must be sent to https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general], and contain a detailed and valid reason that the TU in question should be removed. Following the motion, standard voting procedure commences with a discussion -period of 7 days, a quorum of 75%, and a voting period of 7 days. +period of 7 days, a quorum of 75% of all TUs except for the TU being considered +for removal, and a voting period of 7 days. + ---- SVP( general_removal_of_TU, 7, 0.75, 7); ---- -The Trusted User brought up for removal may defend themselves during the -discussion period, but may not vote during the voting period, nor may they vote -on any other matters while SVP for their removal is in progress. +The TU brought up for removal may defend themselves during the +discussion period, but may not vote on the proposal. + + +Special Removal of an Inactive TU +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +A TU who has not done ANY of the following for a period of at least 2 months: + +1. added, removed or updated a package in +[community]+ or the AUR + +2. performed any action that required TU privileges on the AUR + +3. posted a message to https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general] + +OR who has not voted in a consecutive series of voting periods, the starting dates +of which span 2 months or more, shall be brought up for special removal due to +inactivity. -There is one special case for removal, removal due to unwarranted and -undeclared inactivity, for which standard voting procedure deviates from the -above. This motion is also automatically triggered by repeated quorum offenses, -as described in the <<Q,Quorum>> subsection of this document. For this special -case, SVP is followed with a discussion period of three days, a quorum of 66%, -and a voting period of 5 days. +In this special case, the motion may be made by one TU instead of two, and SVP +is followed by a discussion period of three days, a quorum of 66%, and a voting +period of 5 days. ---- -SVP( inactivity_removal_of_TU, 3, 0.66, 5 ); +SVP( removal_of_inactive_TU, 3, 0.66, 5 ); ---- Amendment of Bylaws @@ -179,7 +157,7 @@ Amendment of Bylaws These bylaws may be amended at any time. -An active Trusted User must motion for an amendment by sending an announcement +A TU must motion for an amendment by sending an announcement to https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general]. The message must either contain, or have attached, a patch against this document which accomplishes the suggested change. SVP is commenced at the time @@ -190,5 +168,5 @@ voting period of 7 days. SVP( amend_bylaws, 5, 0.75, 7); ---- -If the amendment fails, the same amendment may not be motioned for for a period +If the amendment fails, the same amendment may not be motioned for a period of three weeks. -- 1.8.3.4

5 11

[aur-general] deletion request
by Alexej Magura 22 Aug '13

22 Aug '13

Could yall please delete /nocp/, I'm the developer, and I thought that /nocp/was fully functional and ready to be packaged, but upon further testing today I realized that it's hardly functional at all, which is pretty dang disappointing. Anyway, here's a link to the AUR package page thingy. https://aur.archlinux.org/packages/nocp/ /**/ -- Alexej Magura Give a little more for a little less today. :)

2 1

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 22 Aug '13

22 Aug '13

=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 8 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 20 packages missing signoffs * 0 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.) == New packages in [community-testing] in last 24 hours (8 total) == * devil-1.7.8-17 (i686) * mplayer-vaapi-36265-4 (i686) * netsurf-3.0-4 (i686) * synfig-0.64.0-7 (i686) * devil-1.7.8-17 (x86_64) * mplayer-vaapi-36265-4 (x86_64) * netsurf-3.0-4 (x86_64) * synfig-0.64.0-7 (x86_64) == Incomplete signoffs for [community] (20 total) == * bbswitch-0.7-11 (i686) 0/1 signoffs * devil-1.7.8-17 (i686) 0/1 signoffs * mplayer-vaapi-36265-4 (i686) 0/1 signoffs * netsurf-3.0-4 (i686) 0/1 signoffs * r8168-8.036.00-8 (i686) 0/1 signoffs * rt3562sta-2.4.1.1-41 (i686) 0/1 signoffs * synfig-0.64.0-7 (i686) 0/1 signoffs * tp_smapi-0.41-32 (i686) 0/1 signoffs * vhba-module-20130607-11 (i686) 0/1 signoffs * virtualbox-modules-4.2.16-8 (i686) 0/1 signoffs * bbswitch-0.7-11 (x86_64) 0/2 signoffs * devil-1.7.8-17 (x86_64) 0/2 signoffs * mplayer-vaapi-36265-4 (x86_64) 0/2 signoffs * netsurf-3.0-4 (x86_64) 0/2 signoffs * r8168-8.036.00-8 (x86_64) 0/2 signoffs * rt3562sta-2.4.1.1-41 (x86_64) 0/2 signoffs * synfig-0.64.0-7 (x86_64) 0/2 signoffs * tp_smapi-0.41-32 (x86_64) 0/2 signoffs * vhba-module-20130607-11 (x86_64) 0/2 signoffs * virtualbox-modules-4.2.16-8 (x86_64) 0/2 signoffs == Top five in signoffs in last 24 hours == 1. thomas - 1 signoffs

1 0

[aur-general] A simple introduction
by Tanner Danzey 22 Aug '13

22 Aug '13

Since I've never really learned mailing list etiquette, I'm not sure this is the right place. Nevertheless... My name is Tanner, currently residing in strange-weathered Fargo, ND. I work as a support technician / system engineer at a local managed service provider. We use Linux for anything that we aren't paid specifically to use Windows for. I have a breadth of skill in both general IT / system tasks as well as programming (C/C++, Ruby, Python, Web Design, PHP, Haskel). I have developed a deep fondness for the Arch community as a result of lurking over the last few months. I've taken it upon myself to maintain some niche orphaned packages on the AUR (bff, 3dpong, emu65el02) and I'd like to dedicate more time helping you guys out. I'm on IRC frequently as Arkaniad, usually lurking or having it running in the background during some various task. Long story short, I like you guys and I'm gonna stick around for a while. Hello :)

1 0

[aur-general] [Delete request] - miltilame
by member graysky 21 Aug '13

21 Aug '13

https://aur.archlinux.org/packages/multilame/ This was a script I wrote a while ago but have abandoned upstream. Other packages do the same only with tagging. Please delete.

2 1