Arch Website Notification | 24 Oct 10:07 2014

Signoff report for [community-testing]

=== 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
* 14 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] (9 total) ==

* freevo-1.9.0-14 (any)
    0/2 signoffs
* cinnamon-control-center-2.2.11-2 (i686)
    0/1 signoffs
* cinnamon-settings-daemon-2.2.4-3 (i686)
    0/1 signoffs
* mate-applets-1.8.1-2 (i686)
    0/1 signoffs
* mate-power-manager-1.8.1-3 (i686)
    0/1 signoffs
* cinnamon-control-center-2.2.11-2 (x86_64)
    0/2 signoffs
* cinnamon-settings-daemon-2.2.4-3 (x86_64)
(Continue reading)

Arch Website Notification | 23 Oct 10:07 2014

Signoff report for [community-testing]

=== 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
* 14 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] (9 total) ==

* freevo-1.9.0-14 (any)
    0/2 signoffs
* cinnamon-control-center-2.2.11-2 (i686)
    0/1 signoffs
* cinnamon-settings-daemon-2.2.4-3 (i686)
    0/1 signoffs
* mate-applets-1.8.1-2 (i686)
    0/1 signoffs
* mate-power-manager-1.8.1-3 (i686)
    0/1 signoffs
* cinnamon-control-center-2.2.11-2 (x86_64)
    0/2 signoffs
* cinnamon-settings-daemon-2.2.4-3 (x86_64)
(Continue reading)

Antonio Rojas | 23 Oct 09:24 2014
Picon

TU application

Hello Arch Linux community,

 This is my application to become an Arch trusted user. My name is Antonio 
Rojas, I'm a mathematician and professor from Spain. Andrea Scarpino has 
kindly encouraged me to apply and agreed to sponsor my application. 

 I started using Linux in grad school in 1999 (Red Hat). I 
quickly got to like it, but since it was preinstalled I was missing all the 
fun of installing and configuring it. Around 2004 I finally decided to install 
it in my own computers, first in virtual machines and then as the main OS. 
After trying a few distros I settled with Mandriva, and kept using it until 
the company started going downhill. Then I moved briefly to Fedora, until I 
discovered Arch around 2008 and I haven't left since then. It requires the 
perfect ammount of fiddling to make it work (for my taste) and I love always 
having the latest software available. 

 In the last few years I've been an active user in the forum [1] (mostly 
helping people with KDE issues) and bug tracker [2], both in Arch and in 
upstream KDE. Despite not being a programmer, I've occasionally sent small 
patches to fix some issues. 

 I've been maintaining packages in AUR for a few years, some of them have been 
moved to the repos. Currently I maintain close to 200 packages [3], most of 
them KDE related. I maintain the git versions of KDE Frameworks and Plasma, 
and created and maintained the first version of the Plasma 5 packages that 
were moved to [extra] last week. I think the next few months are going to be 
very exciting in the KDE world, with apps being ported to Frameworks and new 
apps popping up that could be moved to [community] when they become popular.

Among the KDE apps that I would like to maintain in community are some that 
(Continue reading)

Karol Blazewicz | 22 Oct 19:01 2014
Picon

How are AUR statistics computed?

https://aur.archlinux.org/ says 'Packages added in the past 7 days -
172', but I've got over 200 new AUR package notification through the
rss feed since Oct 18th. What exactly is being counted? Unique package
bases?

Arch Website Notification | 22 Oct 10:07 2014

Signoff report for [community-testing]

=== 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
* 38 packages missing signoffs
* 18 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) ==

* cinnamon-control-center-2.2.11-2 (i686)
* cinnamon-settings-daemon-2.2.4-3 (i686)
* mate-applets-1.8.1-2 (i686)
* mate-power-manager-1.8.1-3 (i686)
* cinnamon-control-center-2.2.11-2 (x86_64)
* cinnamon-settings-daemon-2.2.4-3 (x86_64)
* mate-applets-1.8.1-2 (x86_64)
* mate-power-manager-1.8.1-3 (x86_64)

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

* freevo-1.9.0-14 (any)
    0/2 signoffs
(Continue reading)

Arch Website Notification | 21 Oct 10:07 2014

Signoff report for [community-testing]

=== 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
* 32 packages missing signoffs
* 18 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] (27 total) ==

* freevo-1.9.0-14 (any)
    0/2 signoffs
* acpi_call-1.1.0-14 (i686)
    0/1 signoffs
* acpi_call-lts-1.1.0-12 (i686)
    0/1 signoffs
* bbswitch-0.8-18 (i686)
    0/1 signoffs
* bbswitch-lts-0.8-3 (i686)
    0/1 signoffs
* kadu-1.1-1 (i686)
    0/1 signoffs
* r8168-8.039.00-3 (i686)
(Continue reading)

Arch Website Notification | 20 Oct 10:07 2014

Signoff report for [community-testing]

=== 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
* 0 fully signed off packages
* 68 packages missing signoffs
* 3 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) ==

* kadu-1.1-1 (i686)
* kadu-1.1-1 (x86_64)

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

* freevo-1.9.0-14 (any)
    0/2 signoffs
* 0ad-a17-2 (i686)
    0/1 signoffs
* acpi_call-1.1.0-14 (i686)
    0/1 signoffs
* acpi_call-lts-1.1.0-12 (i686)
    0/1 signoffs
(Continue reading)

stef204 | 19 Oct 13:57 2014

Upgrading PKGBUILD to new version

Hi,

Newbie to maintaining packages in AUR--I only have the one right now (but getting more done soon.)

Quick question: I need to upload a new version of my package (to follow upstream).  I have made the changes to
PKGBUILD already and tested it.

How do I proceed to upgrade on the AUR?  Just upload it "on top" of previous package, using the regular AUR
upload page?

When looking it up, I've seen guys complaining in the forums about having 2 builds on AUR instead of the same
one having been upgraded; just trying to avoid mistakes here.

Thanks for feedback.

Arch Website Notification | 19 Oct 10:07 2014

Signoff report for [community-testing]

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

There are currently:
* 36 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 67 packages missing signoffs
* 3 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 (36 total) ==

* 0ad-a17-2 (i686)
* aegisub-3.2.1-2 (i686)
* calibre-2.6.0-1 (i686)
* couchdb-1.6.1-2 (i686)
* dwdiff-2.0.9-3 (i686)
* fcitx-4.2.8.5-3 (i686)
* gnustep-base-1.24.6-2 (i686)
* gnustep-gui-0.24.0-3 (i686)
* ibus-qt-1.3.3-2 (i686)
* libfbclient-2.5.3.26778-1 (i686)
* mapnik-2.2.0.620.gad76838-1 (i686)
* open-vm-tools-6:9.4.6-2 (i686)
* openttd-1.4.3-2 (i686)
(Continue reading)

Karol Blazewicz | 19 Oct 05:54 2014
Picon

Is it OK to submit a package that is a dozen of one-line scripts?

Is it OK to submit a package that is a dozen of one-line scripts, like
https://aur.archlinux.org/packages/b2b/ ->
https://github.com/iorbitearth/b2b/tree/master/scripts ?

If it's frowned upon, maybe
https://wiki.archlinux.org/index.php/Arch_packaging_standards should
be explicit about it?

Arch Website Notification | 18 Oct 10:07 2014

Signoff report for [community-testing]

=== 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
* 31 packages missing signoffs
* 3 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] (26 total) ==

* freevo-1.9.0-14 (any)
    0/2 signoffs
* acpi_call-1.1.0-14 (i686)
    0/1 signoffs
* acpi_call-lts-1.1.0-12 (i686)
    0/1 signoffs
* bbswitch-0.8-18 (i686)
    0/1 signoffs
* bbswitch-lts-0.8-3 (i686)
    0/1 signoffs
* kadu-1.0-2 (i686)
    0/1 signoffs
* r8168-8.039.00-3 (i686)
(Continue reading)


Gmane