- Aur-general - lists.archlinux.org

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

17 Sep '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 * 0 fully signed off packages * 8 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] (8 total) == * cinelerra-cv-1:2.2-18 (i686) 0/1 signoffs * gdal-1.10.0-3 (i686) 0/1 signoffs * python-pytables-3.0.0-4 (i686) 0/1 signoffs * vtk-5.10.1-10 (i686) 0/1 signoffs * cinelerra-cv-1:2.2-18 (x86_64) 0/2 signoffs * gdal-1.10.0-3 (x86_64) 0/2 signoffs * python-pytables-3.0.0-4 (x86_64) 0/2 signoffs * vtk-5.10.1-10 (x86_64) 0/2 signoffs == Top five in signoffs in last 24 hours == 1. heftig - 6 signoffs 2. pierre - 4 signoffs 3. tpowa - 2 signoffs

1 0

[aur-general] Disown request : teamdrive
by Matthieu Froment 16 Sep '13

16 Sep '13

Hello all, Can you please disown the actual maintainer of the package : teamdrive https://aur.archlinux.org/packages/teamdrive/ I marked it as out-of-date the 19th of june, with a short message at the attention of the maintainer : No answer ! Actually, 6 months without an update. I wrote this mail, without any answer. > Date: Fri, 6 Sep 2013 19:45:13 +0200 > From: thieume2(a)hotmail.com > To: ch.assfalg(a)gmx.de > Subject: [Archlinux AUR] Teamdrive > > Hello, > > I've seen that you are actually the maintainer of the teamdrive package > on AUR. You may don't have time to take care of this package (and some > release have been missed). I can propose you to take the maintenance of > the pkgbuild to my hand. > Possible to transfer the maintenance ? > Thanks for your answer, > > Regards, > Matthieu. I've got a pkgbuild ready to be uploaded. Thanks in advance, Regards, Matthieu.

2 2

[aur-general] Disown Request: qtiplot-opj
by v1c70r 16 Sep '13

16 Sep '13

Please disown qtiplot-opj: https://aur.archlinux.org/packages/qtiplot-opj/ Not updated in more than a year despite the package doesn't build anymore. The current maintainer doesn't reply to comments or emails. Victor

2 1

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

16 Sep '13

=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 14 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 (14 total) == * bbswitch-0.7-14 (i686) * cinelerra-cv-1:2.2-18 (i686) * r8168-8.036.00-11 (i686) * rt3562sta-2.4.1.1-44 (i686) * tp_smapi-0.41-35 (i686) * vhba-module-20130607-14 (i686) * virtualbox-modules-4.2.18-3 (i686) * bbswitch-0.7-14 (x86_64) * cinelerra-cv-1:2.2-18 (x86_64) * r8168-8.036.00-11 (x86_64) * rt3562sta-2.4.1.1-44 (x86_64) * tp_smapi-0.41-35 (x86_64) * vhba-module-20130607-14 (x86_64) * virtualbox-modules-4.2.18-3 (x86_64) == Incomplete signoffs for [community] (20 total) == * bbswitch-0.7-14 (i686) 0/1 signoffs * cinelerra-cv-1:2.2-18 (i686) 0/1 signoffs * gdal-1.10.0-3 (i686) 0/1 signoffs * python-pytables-3.0.0-4 (i686) 0/1 signoffs * r8168-8.036.00-11 (i686) 0/1 signoffs * rt3562sta-2.4.1.1-44 (i686) 0/1 signoffs * tp_smapi-0.41-35 (i686) 0/1 signoffs * vhba-module-20130607-14 (i686) 0/1 signoffs * virtualbox-modules-4.2.18-3 (i686) 0/1 signoffs * vtk-5.10.1-10 (i686) 0/1 signoffs * bbswitch-0.7-14 (x86_64) 0/2 signoffs * cinelerra-cv-1:2.2-18 (x86_64) 0/2 signoffs * gdal-1.10.0-3 (x86_64) 0/2 signoffs * python-pytables-3.0.0-4 (x86_64) 0/2 signoffs * r8168-8.036.00-11 (x86_64) 0/2 signoffs * rt3562sta-2.4.1.1-44 (x86_64) 0/2 signoffs * tp_smapi-0.41-35 (x86_64) 0/2 signoffs * vhba-module-20130607-14 (x86_64) 0/2 signoffs * virtualbox-modules-4.2.18-3 (x86_64) 0/2 signoffs * vtk-5.10.1-10 (x86_64) 0/2 signoffs == Top five in signoffs in last 24 hours == 1. foutrelis - 10 signoffs 2. allan - 2 signoffs

1 0

Re: [aur-general] Merge request: python2-pyside -> python-pyside
by danielwallace 16 Sep '13

16 Sep '13

Replaces should never be in aur packages. It is only used by Pacman when searching the repository. There is nothing that searches replaces in the aur. Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone -------- Original message -------- From: Hugo Osvaldo Barrera <hugo(a)osvaldobarrera.com.ar> Date: 09/15/2013 6:16 PM (GMT-06:00) To: "Discussion about the Arch User Repository (AUR)" <aur-general(a)archlinux.org> Subject: Re: [aur-general] Merge request: python2-pyside -> python-pyside On 2013-09-13 09:57, Bartłomiej Piotrowski wrote: > On 09/07/2013 10:24 AM, Chris “Kwpolska” Warrick wrote: > > In recent shenanigans[0], python-pyside became a split package, > > building Python 3 and 2 versions simultaneously. python2-pyside still > > exists in the AUR. Please merge python2-pyside[1] into > > python-pyside[2]. > > > > [0]: https://mailman.archlinux.org/pipermail/aur-general/2013-September/025115.h… > > [1]: https://aur.archlinux.org/packages/python2-pyside/ > > [2]: https://aur.archlinux.org/packages/python-pyside/ > > > > Done, thank you. > > -- > Bartłomiej Piotrowski > http://bpiotrowski.pl/ > As maintainer of python2-pyside shouldn't I have gotten a notification about this? At least an automated one from the AUR? Also, since the PKGBUILD states "replaces=(python2-pyside...", shouldn't searching the AUR for python2-pyside yield python-pyside as one of the results? Finally, why does this merge make sense? It merges two *different* libraries into one; I maintained python2-pyside, but have no interest in installing the python3 version, so why is the original package deleted? -- Hugo Osvaldo Barrera A. Because it breaks the logical sequence of discussion Q. Why is top posting bad?

2 1

[aur-general] merge request: vapoursynth-plugin-ffmpegsource-git into vapoursynth-plugin-ffms2
by SpinFlo 15 Sep '13

15 Sep '13

Hi (again) please merge (again xd) https://aur.archlinux.org/packages/vapoursynth-plugin-ffmpegsource-git/ into https://aur.archlinux.org/packages/vapoursynth-plugin-ffms2-git/ for better name convention (upstream) greetings

2 1

[aur-general] merge request: vapoursynth-plugin-ffmpegsource-svn into vapoursynth-plugin-ffmpegsource-git
by SpinFlo 15 Sep '13

15 Sep '13

hi please merge https://aur.archlinux.org/packages/vapoursynth-plugin-ffmpegsource-svn/ into https://aur.archlinux.org/packages/vapoursynth-plugin-ffmpegsource-git/ upstream code move to github greetings

2 1

[aur-general] Únete a mi red en LinkedIn
by Hector Martinez-Seara a través de LinkedIn 15 Sep '13

15 Sep '13

LinkedIn ------------ Hector Martinez-Seara ha solicitado añadirte como contacto en LinkedIn: ------------------------------------------ Me gustaría añadirte a mi red profesional en LinkedIn. Aceptar invitación de Hector Martinez-Seara http://www.linkedin.com/e/sx2w4t-hlm1jgod-45/7RQslQ8A75pgsbqd60wsrtZ775qszD… Ver el perfil de Hector Martinez-Seara http://www.linkedin.com/e/sx2w4t-hlm1jgod-45/rso/287791434/La0a/name/228295… ------------------------------------------ Estás recibiendo invitaciones por correo electrónico. Este mensaje de correo electrónico estaba dirigido a Jorge Barroso Barea. Averigua la razón por la que incluimos esto: http://www.linkedin.com/e/sx2w4t-hlm1jgod-45/plh/http%3A%2F%2Fhelp%2Elinked… (c) 2012, LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, EE.UU.

1 0

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

15 Sep '13

=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 6 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 18 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 (6 total) == * gdal-1.10.0-3 (i686) * python-pytables-3.0.0-4 (i686) * vtk-5.10.1-10 (i686) * gdal-1.10.0-3 (x86_64) * python-pytables-3.0.0-4 (x86_64) * vtk-5.10.1-10 (x86_64) == Incomplete signoffs for [community] (18 total) == * bbswitch-0.7-13 (i686) 0/1 signoffs * gdal-1.10.0-3 (i686) 0/1 signoffs * python-pytables-3.0.0-4 (i686) 0/1 signoffs * r8168-8.036.00-10 (i686) 0/1 signoffs * rt3562sta-2.4.1.1-43 (i686) 0/1 signoffs * tp_smapi-0.41-34 (i686) 0/1 signoffs * vhba-module-20130607-13 (i686) 0/1 signoffs * virtualbox-modules-4.2.18-2 (i686) 0/1 signoffs * vtk-5.10.1-10 (i686) 0/1 signoffs * bbswitch-0.7-13 (x86_64) 0/2 signoffs * gdal-1.10.0-3 (x86_64) 0/2 signoffs * python-pytables-3.0.0-4 (x86_64) 0/2 signoffs * r8168-8.036.00-10 (x86_64) 0/2 signoffs * rt3562sta-2.4.1.1-43 (x86_64) 0/2 signoffs * tp_smapi-0.41-34 (x86_64) 0/2 signoffs * vhba-module-20130607-13 (x86_64) 0/2 signoffs * virtualbox-modules-4.2.18-2 (x86_64) 0/2 signoffs * vtk-5.10.1-10 (x86_64) 0/2 signoffs == Top five in signoffs in last 24 hours == 1. dreisner - 1 signoffs

1 0

[aur-general] linux-next naming convention
by Dennis Borisevich 15 Sep '13

15 Sep '13

Hello, I have just become the maintainer of my first package in AUR,'linux-next'. It's name lacks -git prefix, though it is using git to fetch source code. I figure out that I have these courses of action: 1)Ask for the deletion of 'linux-next' package in favor of 'linux-next-git'; 2)Create a separate package 'linux-next-git' which uses git by fetching sources like described in Wiki page "VCS PKGBUILD Guidelines", but keep 'linux-next' and use prepare() mechanism, which will utilize 'git clone --depth=1' (less to download, useful for one-time building); 3) Don't create any new packages and just update 'linux-next' PKGBUILD like in 1). Thanks, denspirit.

2 1