Re: [arch-dev-public] Nginx

2013-08-02 Thread Pierre Schmitz
Am 01.08.2013 22:59, schrieb Sébastien Luttringer: Externals modules are not often updated (e.g: auth-pam 11/2010, upstream-fair: 4/2012). Furthermore, there is no install-time dependencies added by passenger or the previous others external. Taking this in consideration, there is probably no

[arch-dev-public] Signoff report for [testing]

2013-08-02 Thread Arch Website Notification
=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 5 new packages in last 24 hours * 2 known bad packages * 0 packages not accepting signoffs * 4 fully signed off packages * 50 packages missing signoffs * 21 packages older than 14 days (Note:

Re: [arch-dev-public] Nginx

2013-08-02 Thread Bartłomiej Piotrowski
On 2013-08-02 08:41, Pierre Schmitz wrote: But more important please don't add random third party patches/modules and keep the package vanilla. There are good reasons we have the don't patch policy. They can break on nginx updates, introduce new issues etc.; esp. since they are built-in. There

Re: [arch-dev-public] Nginx

2013-08-02 Thread Pierre Schmitz
Am 02.08.2013 14:14, schrieb Bartłomiej Piotrowski: On 2013-08-02 08:41, Pierre Schmitz wrote: But more important please don't add random third party patches/modules and keep the package vanilla. There are good reasons we have the don't patch policy. They can break on nginx updates, introduce

Re: [arch-dev-public] Nginx

2013-08-02 Thread Dicebot
On 08/02/2013 02:55 PM, Pierre Schmitz wrote: In general I am not sure if there is a sane way to package these build time modules. It would be impossible to cover all the combinations and external modules a user might want. Is it a good idea to provide a separate package that has all kinds of

Re: [arch-dev-public] Nginx

2013-08-02 Thread Sébastien Luttringer
On Fri, Aug 2, 2013 at 2:55 PM, Pierre Schmitz pie...@archlinux.de wrote: Am 02.08.2013 14:14, schrieb Bartłomiej Piotrowski: On 2013-08-02 08:41, Pierre Schmitz wrote: If you abuse the split package this way, you still have to rebuild and publish both split packages if e.g. the passenger

[arch-dev-public] Integrity Check i686: core, extra, community 02-08-2013

2013-08-02 Thread repomaint
= Integrity Check i686 of core,extra,community = Performing integrity checks... == parsing pkgbuilds == parsing db files == checking mismatches == checking archs == checking dependencies == checking

[arch-dev-public] Integrity Check x86_64: core, extra, community, multilib 02-08-2013

2013-08-02 Thread repomaint
Warning : the repository multilib does not exist in /srv/abs/rsync/any === = Integrity Check x86_64 of core,extra,community,multilib = === Performing integrity checks... == parsing

Re: [arch-dev-public] Nginx

2013-08-02 Thread Pierre Schmitz
Am 02.08.2013 15:38, schrieb Sébastien Luttringer: In general I am not sure if there is a sane way to package these build time modules. It would be impossible to cover all the combinations and external modules a user might want. Is it a good idea to provide a separate package that has all