Bug#760176: libapache2-mod-perl2: SNMP process name for apache is wrong when modperl is enabled
Package: libapache2-mod-perl2 Version: 2.0.7-3 Severity: normal Tags: patch Dear Maintainer, I was trying to monitor apache2 process status using the hrSWRunTable on a server with modperl enabled. I installed apache2 and libapache2-mod-perl2 packages, then I enabled the perl module. The only way to resolve this issue was disabling perl module with a2dismod perl, but now, my application which needs modperl doesn't work, so for now, I can't monitor apache2 through SNMP. When the perl module is enabled, apache2 process name in SNMP (and in /proc/*/status) is /usr/sbin/apach (/usr/sbin/apache2 trimmed to 15 characters), when perl module is disabled, apache2 process name in SNMP (and in /proc/*/status) is apache2, which is the correct one. I found a bug openned on Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=782369) which explains the whole issue and gives a patch to resolve this issue. I tried the patch on the source package for stable and testing, and it seems to patch well. I didn't test the build and running apache2 with this patched module. I will try it tomorrow. I took a quick look at the source packages for stable, testing and experimental, and they all seems to have the issue. I hope I was clear enough, don't hesitate to contact me if you need further information. Thanks. -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760176: [DUPLICATE] 754702
Hello. Apparement, this issue was already declared in the bug #754702. Sorry for the noise caused by this bug openning. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715269: Same issue with bpo kernel
Hello. With hopes to fix this issue, I tried to install the linux-image-3.9-0.bpo.1-amd64 (3.9.6-1~bpo70+1) package, but it stayed the same. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712989: nginx: Please define fastcgi_param HTTPS same as upstream default
On 06/21/2013 05:13 PM, Peter De Wachter wrote: Package: nginx Version: 1.4.1-3 Severity: normal Dear Maintainer, The Debian config file /etc/nginx/fastcgi_params has the following line fastcgi_param HTTPS $https; But the upstream version of that file (nginx-1.4.1/conf/fastcgi_params) defines that parameter as fastcgi_param HTTPS $https if_not_empty; The difference is that the upstream config will leave HTTPS undefined for plain http connections, while the Debian config will define it as an empty string. I've found this change causes problems with some applications. For example, the CodeIgniter framework assumes https is in use if HTTPS is defined and not equal to 'off'. As far as I can tell, the HTTPS variable was first introduced by Apache mod_ssl, which has the same behavior as the upstream nginx config (defined if https is in use, undefined otherwise). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx depends on: ii nginx-full 1.4.1-3 nginx recommends no packages. nginx suggests no packages. -- no debconf information Hello Peter. Thanks for this report. The fix is applied in the GIT repository so it will be fixed with the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712445: nginx-common: conffiles not removed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/16/2013 08:42 AM, Paul Wise wrote:
Package: nginx-common
Version: 1.4.1-2
Severity: normal
Usertags: conffile
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate
The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by dh_installdeb
to remove these obsolete conffiles on upgrade.
http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
http://manpages.debian.net/man/1/dh_installdeb
This bug report brought to you by adequate:
http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/
$ pkg=nginx-common
$ adequate $pkg
nginx-common: obsolete-conffile /etc/nginx/naxsi-ui.conf
$ dpkg-query -W -f='${Conffiles}\n' $pkg | grep obsolete
/etc/nginx/naxsi-ui.conf 6be82259836cb8fad0afde03ebf101d4 obsolete
-- System Information:
Debian Release: jessie/sid
APT prefers experimental
APT policy: (1900, 'experimental'), (1800, 'unstable'), (1700,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-rc4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nginx-common depends on:
ii lsb-base 4.1+Debian12
Versions of packages nginx-common suggests:
pn fcgiwrap none
pn nginx-doc none
Hello Paul.
Thanks for this report.
Actually, it's more complicated than that.
Before nginx 1.4.1 packages, naxsi-ui used the MySQL backend, so the
/etc/nginx/naxsi-ui.conf file was generated using dbconfig.
But not, it has switched to SQLite. This file becoming more or less
static (from the maintainer point of view), we wanted to include it
directly is the package nginx-common, but this wasn't right (see bug
#707291).
So I wrote preinst and postinst scripts for nginx-naxsi-ui package which
is checking the version of the package previously installed and
performing the right tasks to perform the backend change.
Now, the /etc/nginx/naxsi-ui.conf doesn't belong to any package, because
the postinst script copies the file /etc/nginx/naxsi-ui.conf.1.4.1 to
/etc/nginx/naxsi-ui.conf if needed.
The only thing I think I can do is removing the /etc/nginx/naxsi-ui.conf
file when removing nginx-common (using a postrm script).
I need to see what checks are performed by adequate to see if there are
more issues we need to fix.
Thanks.
- --
Cyril Davromaniak Lavier
KeyID 59E9A881
http://www.davromaniak.eu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRvYfFAAoJEOcAaEhZ6aiB9TYP/2AUE6jiUX9c2GV8NURHXLJR
GuK6G+a3UdZGKt0+s7u0Vkm1cR5xslAEtzS6QjaU1KVYdf7S8XLewgNyjzxVbH5U
F74MdARzMldVahwsGV2HumeG5Ob0644R3EBE9GdCRoMY5saIvkbX5wTeyx9N9FwI
Bo9pXNbNCglNSE08rDY7nYkNZz+cNGxAd5Tb6WJQk39X632X4rEFOZ1/db6PeT7/
0/Q+37aVsJGrT1bdHGbZSon+i/ZN8DEgPhS7AZQFgj6ZFHssRau/U+0cwuiN5ID0
bpKLdzST+D8xBaK8uEbM7f44ng26YMvha+eJAOyGWMRAaXqez1Ps/Kff4bhMGm50
eGLfFAEps98PCGwJVj+22cXvz1SwevTnzmpgKlCzT6Aq8tF342Kc062ZqggVJX/r
PPD37OiYCu4lNGnfF+x9AjTGuF7I7X1sKry1PMovSgIa7hgjnRUwln0wJRzQ7CgX
E/CAoE9FBffDcC/EziHLMz3ZhvahTeqjEbHavqJ1FTXWemYG8nQYf+5GCjFxdYoL
+AnHTQB+g4DN2sd7zTbXsDf1cuOt2ZGvYUWREcIlx9CdkbIHcwwFe7rlu8qW1NRK
ABad2IAHdGazMY/Kk4q4z9D/IgUSYYoS5bpHuPvQNbxJ7XGQErCZM3vg2/4gJoZB
74HH6obU8VynL5ZIWoR8
=sjbJ
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712445: nginx-common: conffiles not removed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/2013 11:56 AM, Paul Wise wrote: On Sun, 2013-06-16 at 11:39 +0200, Cyril Lavier wrote: Actually, it's more complicated than that. I see, sounds complicated. I'm not familiar with this case but maybe one of these links helps. http://lists.debian.org/debian-devel/2006/12/msg00647.html http://bugs.debian.org/672945 I need to see what checks are performed by adequate to see if there are more issues we need to fix. It simply asks dpkg which conffiles are installed for the package and then reports the files that dpkg reports as obsolete. Thanks for your help. I will try to figure out what to do exactly, as we also plan to replace the nginx-naxsi-ui package by nginx-nx-util package, because naxsi-ui is deprecated in favor of nx_util, so there's a lot of packaging work to do. - -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRvZguAAoJEOcAaEhZ6aiBddsP/35Z28Qu5iB8SpVmanwsnkxQ tc/3ZwBwObPuMyCsxLE5NNXF9eQZVAsOdk/vO9ZaR5BOtY18cnF6N6dhikAhlqX6 Z/Xn/3AY8ogvrT81S9++4vc2pByeESFpfDsjWk/NPpQfzablA2e3CewVNfghpZxE 8G9pU208Gay5EtRZ8Qel6tuHfo2/mT0s544e92ZU+J65KjxlPnR4g5oIsAwCuPWR 6MAb2WWsSnXVHE0PxCLtLw6+of2H4JD2d4ubREMQq20qjROzYUIpXI8grU6GD0sp RrG/3sc2qzW5pfClcM5KrtMlM+1yUSr6LdHGczhSgueYCi6vD7cWIJ3LbWEAcL1r kgC5uh9+qh717MhQI+imbMa3uC+4WWQukgQAH5STA61FCsuqPAmTU/wy/QZO27Og SUsK3+/fpgxUdGVl7LbH83+8ArFF5FxhCfkV9R2p0ceHiweD2hx0tBIZOmz+Vf+g zjXuDqaDN50IdnAYV/WlX41nJ7hJXx+mdCkRgxisbtp2UQfgwh2WzwZu6IrLmmaw quzrz0RObHS1LonHdPp3wrdPcvYEhuPW9ZFv77xW8ajaKN8/co4DpxuKsLsjRIxg 0Yv0NB8dvIcXbF3FFLt+HO/kTpKjR5lGT6Fu1a3UXHbnv8s6YbW3qz9k8gUgU9ZM 641HVpiEMgTw0sc2YXP8 =CTOQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695119: Normal behavior as stated by upstream
Hello. As said here (http://marc.info/?l=nginxm=121186699326604w=2), Igor (one of the nginx developers) said this is a normal behavior. I agree with him, because if you run nginx -t to test your config file before a reload on a production server, it's not good to have the pidfile removed. So I think we should not try to fix this issue as it's a normal behavior. Kartik, Michael, what do you think ? Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711590: nginx-naxsi-ui: fails to install: preinst called with unknown argument `install'
On 06/08/2013 10:25 AM, Andreas Beckmann wrote: Package: nginx-naxsi-ui Version: 1.4.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package nginx-naxsi-ui. (Reading database ... 11899 files and directories currently installed.) Unpacking nginx-naxsi-ui (from .../nginx-naxsi-ui_1.4.1-2_all.deb) ... preinst called with unknown argument `install' dpkg: error processing /var/cache/apt/archives/nginx-naxsi-ui_1.4.1-2_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/nginx-naxsi-ui_1.4.1-2_all.deb cheers, Andreas Hello Andreas. Thank you for this report. The fix is commited to the git repository. It will be fixed with the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708164: nginx proxy_pass buffer overflow (CVE-2013-2070)
On 05/13/2013 09:15 PM, Florian Weimer wrote: * Thijs Kinkhorst: A buffer overflow in the proxy_pass module has been reported by Nginx upstream, and a patch made available. Please see: http://www.openwall.com/lists/oss-security/2013/05/13/3 The issue is already fixed in the version in sid, and as far as I can see the code is not present in squeeze. Can you ensure that (a) the RC bug against nginx in sid is dealt with so the fixed package can migrate to jessie, and (b) prepare an update to wheezy? Note that the upstream patch is not 100% correct C (the overflow check can be optimized by the compiler). Therefore, the generated assembly has to be inspected to ensure that the check is actually in place. Here's a bit of background information: http://cert.uni-stuttgart.de/ticker/advisories/c-integer-overflow.html https://www.securecoding.cert.org/confluence/display/seccode/INT32-C.+Ensure+that+operations+on+signed+integers+do+not+result+in+overflow Hello Florian. Except the patch is not 100% correct C, does it sounds risky on the security side to patch nginx stable (1.2.1-2.2) ? Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708522: src:nginx: running debian/rules binary is not enough to build a binary package
On 05/16/2013 12:03 PM, Ansgar Burchardt wrote: Package: src:nginx Version: 1.4.1-1 Severity: serious Calling debian/rules' binary target is not enough to build the package as required by Policy 4.9: The binary target must be all that is necessary for the user to build the binary package(s) produced from this source package. % fakeroot make -f debian/rules binary dh_testdir dh_testroot dh_prep dh_installdirs dh_install cp: cannot stat ‘./debian/build-full/objs/nginx’: No such file or directory dh_install: cp -a ./debian/build-full/objs/nginx debian/nginx-full/usr/sbin/ returned exit code 1 make: *** [install] Error 2 Ansgar Hello Ansgar. The fix is commited and pushed to the GIT repository. This issue should be fixed with the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711234: minidlna: New upstream (1.1.0) version available
Package: minidlna Severity: wishlist Tags: upstream Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** The 1.1.0 release of minidlna was released in last April. In case you don't have time to update the package, I'm willing to help you maintaining minidlna and thus performing this update. Thanks. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707291: nginx-common: prompting due to modified conffiles which were not modified by the user
Hello Andreas. Thanks for this report. I completely messed up the last update on the naxsi-ui part. I'm deeply sorry for this and I'm currently working on an update. If it goes well, it should arrive on wednesday. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699678: Changes pushed to GIT repo
Hello again. I pushed the needed changes to the GIT repo. So the engine switch will be effective with the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706456: nginx: add http_substitutions_filter module
Le 2013-04-30 13:59, Pierre Mavro a écrit : Package: nginx Severity: wishlist Hello, I would like Debian to integrate that module as it's really better than the classic substitution module. I tried to integrate it in Wheezy and experimental package version and it works like a charm. This module does the same things as the substitution one, but is able in addition to : - Do multiple subsitutions (instead of only one with substitution module) - Use regex in filters You can find the full description of it there : https://github.com/yaoweibin/ngx_http_substitutions_filter_module So to integrate it easily in Debian packages, here is what I did on deb-src nginx package : 1. in debian/modules, I get the sources :git clone git://github.com/yaoweibin/ngx_http_substitutions_filter_module.git 2. in debian/rules, I added a line in config.status.extras : --add-module=$(MODULESDIR)/ngx_http_substitutions_filter_module \ That's all, after rebuild it just works :-) Thanks Hello Pierre. Thanks for this suggestion. IMHO, this module is usefull and deserves to figure in the Debian packages. The maintainer is active and trustable. I'm working on adding this module in the -full and -extras flavours. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699678: Changing database engine for nginx-naxsi-ui
Hello. Thanks for your report. Actually, I decided to go on with the MySQL engine because the naxsi developers told me the SQLite support wasn't completely stable. But with the last update (pushed in experimental and using naxsi 0.50), the SQLite support is more reliable and they consider it stable. So I think we might change the database engine in the next uploads. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700426: vulnerable to CRIME SSL attack (CVE-2012-4929)
Le 2013-02-12 16:27, Thijs Kinkhorst a écrit : Package: nginx Version: 0.7.67-3 Severity: grave Tags: security patch Hi, nginx in squeeze and wheezy is vulnerable to the SSL attack CVE-2012-4929 dubbed 'CRIME'. The attack is related to SSL compression. The popular solution to the attack is to disable SSL compression. This is what Apache has done and also what nginx upstream has done in 1.2.2. Attached patch does that, works for us and we've verified that it solves the problem. Upstream info is here: http://forum.nginx.org/read.php?2,231067,231068 I'd gladly hear your view on this patch. Barring any objections I'm planning to release this as a DSA after the weekend, and also make an upload to wheezy. Cheers, Thijs Hello Thijs. Thanks for this report. I think we have to include this patch in the nginx packages (stable and unstable). I don't actually know if you already prepared an upload, so I did it by myself (and it was a great time to relearn how to use quilt). The packages are here : * Stable : http://sources.davromaniak.eu/nginx/nginx_0.7.67-3+squeeze3.dsc * Unstable : http://sources.davromaniak.eu/nginx/nginx_1.2.1-3.dsc In case you already prepared an upload, just ignore the last lines ;). When the 1.2.1 package will arrive on the unstable repo, I will backport it to squeeze. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700426: vulnerable to CRIME SSL attack (CVE-2012-4929)
Le 2013-02-13 15:36, Thijs Kinkhorst a écrit : Hi Cyril, On Wed, February 13, 2013 14:55, Cyril LAVIER wrote: Thanks for this report. I think we have to include this patch in the nginx packages (stable and unstable). I don't actually know if you already prepared an upload, so I did it by myself (and it was a great time to relearn how to use quilt). The packages are here : * Stable : http://sources.davromaniak.eu/nginx/nginx_0.7.67-3+squeeze3.dsc * Unstable : http://sources.davromaniak.eu/nginx/nginx_1.2.1-3.dsc In case you already prepared an upload, just ignore the last lines ;). When the 1.2.1 package will arrive on the unstable repo, I will backport it to squeeze. Thanks! Unstable however is already fixed, according to my information, in 1.2.2. See http://forum.nginx.org/read.php?2,231067,231068 So it does need to be fixed in wheezy, which has 1.2.1, and in stable indeed. Your package for stable looks good. I'll upload that to security master so it can get built. Can you take care of the process of updating wheezy? I think you need to sollicit input from the release team before you can upload to testing-proposed-updates. Cheers, Thijs Actually, when I typed Unstable : or unstable, I meant Testing : or testing. I don't know why I mistyped a big part of this mail :(. So the nginx_1.2.1-3.dsc source package is for testing (wheezy). Sorry for this mistake. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652108: Some news about these scripts
Hello. First, thanks Thomas for relaying the bug in Ubuntu. I will try to update both bugs when giving updates. The project is still alive (here : https://github.com/davromaniak/nginx_ensite). First, we wanted to add them before the freeze of debian wheezy, but we thought the scripts where too green for that and we delayed their inclusion. We schedule to include the scripts for Wheezy+1, and after the freeze of Ubuntu Raring, as we don't want to risk adding severe bugs in a stable (even not LTS) release of Ubuntu. By the way, if anybody wants to grab the script and test it, don't hesitate to do so and open issues on github if needed. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660681: (pas de sujet)
Hello. If it's still needed, I can give a hand on maintaining this package. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668658: qemu-debootstrap on mips, mipsel and powerpc broken
On 12/16/2012 05:22 PM, Michael Tokarev wrote: Control: tag -1 + moreinfo On 25.05.2012 04:05, Vagrant Cascadian wrote: tags 668658 confirmed retitle 668658 qemu-user-static: mips, mipsel and powerpc broken thanks On Sat, Apr 21, 2012 at 10:20:52AM +0200, Cyril Lavier wrote: On 04/14/2012 01:58 AM, Loïc Minier wrote: On Fri, Apr 13, 2012, Cyril Lavier wrote: I'm trying to use qemu-debootstrap to build packages for other architectures. But I'm facing problems when building mips, mipsel and powerpc packages (works only with armel) with pbuilder using a chroot made by qemu-debootstrap. If it works with armel and not other architectures, it doesn't sound like a pbuilder problem but like a qemu one? This broke again somewhere around qemu 1.0... i think it was working for the 0.15.x versions. Version 1.1.0-rc3 seems to at least (mostly) fix mipsel and maybe mips. will be uploading that to experimental soon, and hopefully unstable once 1.1.0 comes out. Guys, do we still have this issue now, when 1.1.2 were in testing for several months? Is there some more or less easy reproducer for it for me to verify, maybe a step-by-step instruction (I for one never used pbuilder with non-native arch before)... Thanks, /mjt Hello Michael. If you want to perform a quick test, grab the pbuilderrc here (https://github.com/davromaniak/scriptomaniak/blob/master/pbuilderrc), then create a chroot for powerpc, mips or mipsel. Then, try to build a package (nginx for example ;)). I don't have access to my build machine right now, but I will try to test it on Tuesday or Wednesday. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693302: Fixed in git
Hello Pablo. Thank you for the report and for using nginx-naxsi. I forgot to add the Real IP on the nginx-naxsi because I thought its main use will be in a reverse proxy. I performed the needed changes in the git repository to have it available in Debian Unstable. As Wheezy is frozen now, I don't know if we will be able to add the module in the wheezy packages and then performing a backport. Kartik, Michael, do you have any ideas on this ? Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678910: nginx: [INTL:gl] Galician debconf templates translation
On 06/25/2012 01:24 AM, Jorge Barreiro wrote: Package: nginx Version: 1.2.0-2 Severity: wishlist Tags: l10n patch Galician debconf templates translation is attached. Thanks. Hello Jorge. The po file is now included in the git repository. Thank you for your work. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678915: nginx: [INTL:es] Spanish debconf translation for nginx
On 06/25/2012 07:22 AM, Fernando C. Estrada wrote: On Mon, Jun 25, 2012 at 06:48:27AM +0200, Christian PERRIER wrote: This translation is apparetly based on what is currently in the package. However, the templates have been reviewed and slightly changed. Attached it the es.po file synced with the new templates. Could you update it (apparently from what I read, your translation still applies but also uses the passive form which we dropped from English). Thanks for the advice, here's the updated translation. Regards, Hello Fernando. The po file is now included in the git repository. Thank you for your work. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu
Bug#678659: [l10n:cs] Updated Czech translation of PO debconf template for package nginx 1.2.0-2
On 06/23/2012 04:37 PM, Michal Simunek wrote: Package: nginx Version: 1.2.0-2 Severity: wishlist Tags: l10n, patch In attachment there is updated Czech translation of PO debconf template (cs.po) for package nginx, please include it. Hi Michal. Thanks for this work. The cs.po file as been updated in the git repository. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678060: Configuration should be purged in nginx-common
On 06/18/2012 10:35 PM, Jeroen Dekkers wrote: Package: nginx Version: 1.2.0-1 Severity: serious Tags: patch The nginx-light, nginx-full and nginx-naxsi packages delete the /etc/nginx and /var/log directory when they are purged, but the configuration files are owned by nginx-common. This can give all sort of problems, for example if you do apt-get install nginx-light, then apt-get install nginx-full and dpkg --purge nginx-light you end up with a sytem that doesn't have an /etc/nginx or /var/log/nginx. Attached patch moves the purging to the nginx-common package where it belongs. -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-25-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Hello Jeroen. Thanks for reporting us this issue. We applied your patch in the git repository. It will be fixed in the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673787: nginx-naxsi-ui: unowned files after purge (policy 6.8, 10.8): /etc/dbconfig-common/nginx-naxsi-ui.conf
On 05/22/2012 01:43 PM, Andreas Beckmann wrote: On 2012-05-21 19:36, Cyril Lavier wrote: On 05/21/2012 03:16 PM, Andreas Beckmann wrote: This very much looks like dbconfig-common is not used properly in the postinst, otherwise this configuration would have been removed during purge. Ok. In the next days, I will make some search on this way. At first sight, I thought I had to add a postrm script for the nginx-naxsi-ui package, but I will follow your advice first. Check the dbconfig-common documentation, it should have a few examples: /usr/share/doc/dbconfig-common/ Andreas Hello Andreas. On my last try, I launched the piuparts tests manually, the only error remaining was : FAIL: Package purging left files on system: /etc/dbconfig-common owned by: dbconfig-common I think it's good now. We will see when the next upload will be tested with the official piuparts system. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677128: nginx-full: Package description suggests HTTP SSL module is not included
On 06/11/2012 09:32 PM, Gunnlaugur Thor Briem wrote: Package: nginx-full Version: 1.1.19-1~bpo60+1 Severity: minor The Optional HTTP Modules list for nginx-full (squeeze-backports) does not contain SSL, but the corresponding list for nginx-extras does contain it. This suggested (to me) that nginx-full lacked that module; I had to install nginx-full and check `nginx -V` to find out that it does have it. -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx-full depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii libgd2-noxpm 2.0.36~rc1~dfsg-5 GD Graphics Library version 2 (wit ii libgeoip1 1.4.7~beta6+dfsg-1A non-DNS IP-to-country resolver l ii libpam0g 1.1.1-6.1+squeeze1Pluggable Authentication Modules l ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii libxml22.7.8.dfsg-2+squeeze4 GNOME XML library ii libxslt1.1 1.1.26-6 XSLT 1.0 processing library - runt ii nginx-common 1.1.19-1~bpo60+1 small, but very powerful and effic ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime nginx-full recommends no packages. nginx-full suggests no packages. -- no debconf information Hello Gunnlaugur. Thanks for your report. Sometimes we miss some modules in the list. I commited the needed changes in the git repository. It will be fixed in the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657825: Processed: tagging 657825
On 06/14/2012 10:33 PM, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: tags 657825 + wontfix Bug #657825 [wnpp] ITP: umegaya -- Umegaya is a MEtadata GAtherer using YAml Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. Sorry for the wrong tag. I misstyped the bug number. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674188: nginx: [INTL:ru] Russian debconf templates translation
On 05/23/2012 07:10 PM, Yuri Kozlov wrote: Package: nginx Version: 1.2.0-1 Severity: wishlist Tags: l10n patch Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Russian debconf templates translation is attached. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Hi Yuri. The po file is now added in the GIT repo. It will be included in the next upload. Thanks for your contribution. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673861: nginx: [INTL:de] Initial German debconf translation
On 05/21/2012 08:36 PM, Chris Leick wrote: Package: nginx Version: 1.2.0-1 Severity: wishlist Tags: l10n patch Hi, please find attached the new German debconf translation of nginx. Kind regards, Chris Hi Chris. The po file is now added in the GIT repo. It will be included in the next upload. Thanks for your contribution. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu
Bug#673787: nginx-naxsi-ui: unowned files after purge (policy 6.8, 10.8): /etc/dbconfig-common/nginx-naxsi-ui.conf
On 05/21/2012 03:16 PM, Andreas Beckmann wrote: Package: nginx-naxsi-ui Version: 1.2.0-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, Hi Andreas during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. I completely understand. From the attached log (scroll to the bottom...): 0m38.2s ERROR: FAIL: Package purging left files on system: /etc/dbconfig-common/nginx-naxsi-ui.conf not owned This very much looks like dbconfig-common is not used properly in the postinst, otherwise this configuration would have been removed during purge. Ok. In the next days, I will make some search on this way. At first sight, I thought I had to add a postrm script for the nginx-naxsi-ui package, but I will follow your advice first. I hope to fix it by the end of the week. cheers, Thanks Andreas -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673120: [l10n:cs] Initial Czech translation of PO debconf template for package nginx 1.2.0-1
On 05/16/2012 11:39 AM, Michal Simunek wrote: Package: nginx Version: 1.2.0-1 Severity: wishlist Tags: l10n, patch In attachment there is initial Czech translation of PO debconf template (cs.po) for package nginx please include it. Hi Michal. Thanks for your contribution. Kartik added your translation in the GIT repo. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672998: nginx-naxsi: Stub Status -module is not working
On 05/15/2012 01:02 PM, Johannes Brummer wrote:
Package: nginx-naxsi
Version: 1.1.19-1
Severity: normal
Dear Maintainer,
nginx-naxsi -package is compiled without --with-http_stub_status_module,
and is not working. My experiences so far:
# aptitude install nginx-naxsi
The following NEW packages will be installed:
nginx-naxsi{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 358 kB of archives. After unpacking 705 kB will be used.
The following packages have unmet dependencies:
nginx-full : Conflicts: nginx-naxsi but 1.1.19-1 is to be installed.
nginx-naxsi : Conflicts: nginx-full but 1.1.19-1 is installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) nginx
2) nginx-full
Accept this solution? [Y/n/q/?] y
The following NEW packages will be installed:
nginx-naxsi
The following packages will be REMOVED:
nginx{a} nginx-full{a}
0 packages upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 358 kB of archives. After unpacking 282 kB will be freed.
Do you want to continue? [Y/n/?] y
Get: 1 http://ftp.fi.debian.org/debian/ wheezy/main nginx-naxsi i386 1.1.19-1
[358 kB]
Fetched 358 kB in 0s (1,200 kB/s)
(Reading database ... 42644 files and directories currently installed.)
Removing nginx ...
Removing nginx-full ...
Stopping nginx: nginx.
Selecting previously unselected package nginx-naxsi.
(Reading database ... 42632 files and directories currently installed.)
Unpacking nginx-naxsi (from .../nginx-naxsi_1.1.19-1_i386.deb) ...
Setting up nginx-naxsi (1.1.19-1) ...
# nano -w /etc/nginx/sites-enabled/default
insert following to the server-block
location /nginx_status {
stub_status on;
access_log off;
allow 127.0.0.1;
deny all;
}
# service nginx restart
Restarting nginx: nginx: [emerg] unknown directive stub_status in
/etc/nginx/sites-enabled/default:82
nginx: configuration file /etc/nginx/nginx.conf test failed
How i fixed the situation?
apt-get source nginx, open debian/rules, search config.status.naxsi
-
add --with-http_stub_status_module \ to the configuration options before
$(CONFIGURE_OPTS) $@
after recompiling with dpkg-buildpackage -rfakeroot:
# dpkg -i ../nginx-naxsi_1.1.19-1_i386.deb
(Reading database ... 46518 files and directories currently installed.)
Preparing to replace nginx-naxsi 1.1.19-1 (using
.../nginx-naxsi_1.1.19-1_i386.deb) ...
Unpacking replacement nginx-naxsi ...
Setting up nginx-naxsi (1.1.19-1) ...
# service nginx restart
Restarting nginx: nginx.
# lynx -dump http://127.0.0.1/nginx_status
Active connections: 1
server accepts handled requests
1 1 1
Reading: 0 Writing: 1 Waiting: 0
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nginx-naxsi depends on:
ii libc6 2.13-32
ii libpcre3 1:8.30-5
ii libssl1.0.0 1.0.1c-1
ii nginx-common 1.1.19-1
ii zlib1g1:1.2.7.dfsg-1
nginx-naxsi recommends no packages.
nginx-naxsi suggests no packages.
-- no debconf information
Hi Johannes.
Thanks for this report.
I commited the needed changes to the GIT repository.
Sorry for the inconvenience caused by this bug.
Thanks.
--
Cyril Davromaniak Lavier
KeyID 59E9A881
http://www.davromaniak.eu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664271: RE : nginx: Please allow IPv6 localhost access /doc/ location in default, virtualhost
Hi Andriy. Michael Lustfield commited the needed changes to the GIT repo. The bug will be resolved in the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670306: new upstream version available (1.2)
On 04/24/2012 09:03 PM, Antoine Beaupré wrote: Package: nginx Severity: wishlist The 1.2 release is now available! At last we can fix the issue I noted in #645019 where the dev release is the one available in testing and backports. Hopefully this can be uploaded to sid and migrated to testing and bpo? Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Hi Antoine. The 1.2.0 release is scheduled to hit Unstable by the end of this week, or beginning of next week. But first, I will try to take enough time to update all the third party to their last stable release and other things to have a 1.2.0-1 package fully functionnal. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668658: pbuilder: Builds hangs when used with qemu-debootstrap on mips, mipsel and powerpc
On 04/14/2012 01:58 AM, Loïc Minier wrote: On Fri, Apr 13, 2012, Cyril Lavier wrote: I'm trying to use qemu-debootstrap to build packages for other architectures. But I'm facing problems when building mips, mipsel and powerpc packages (works only with armel) with pbuilder using a chroot made by qemu-debootstrap. If it works with armel and not other architectures, it doesn't sound like a pbuilder problem but like a qemu one? Yes, you are right. I will reaffect the bug to the qemu-user-static. Sorry for the useless noise. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668953: RE : lists.debian.org: please create debian-nginx
Hi Michael. Thanks for requesting this mailing list. The most important part of using a mailing list would be the archiving of our conversations. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668403: audacious: workaround for sparc ICE is no longer needed
On 04/11/2012 06:18 PM, peter green wrote: Package: audacious Version: 3.2-2 Severity: normal Tags: patch In version 3.2-2 the optimisation level was dropped on sparc to work arround a compiler bug. This compiler bug has now been fixed and i've confirmed the package builds without the workaround so please remove it in the next upload (I don't think it's worth making a special upload over). ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers Hi Peter. Thanks for this information. I updated the rules file in the GIT repo. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668658: pbuilder: Builds hangs when used with qemu-debootstrap on mips, mipsel and powerpc
Package: pbuilder Version: 0.210 Severity: normal Dear Maintainer, I'm trying to use qemu-debootstrap to build packages for other architectures. But I'm facing problems when building mips, mipsel and powerpc packages (works only with armel) with pbuilder using a chroot made by qemu-debootstrap. I tried numerous packages, like nginx, apache2, mysql-5.1, and I still have the same result. When doing the fakeroot debian/rules clean, it hangs, I've waited for hours, and I finished by hitting the CTRL+C buttons (the ^C) in the log. Here is the full log for the last nginx 1.1.19-1 build I tried : http://paste.davromaniak.eu/index.php?show=82 The pbuilderrc file I use is here (I use ftp.de.debian.org instead of ftp.fr.debian.org because my server is located in Germany) : https://raw.github.com/davromaniak/scriptomaniak/c7f40d98dcf81dc925f169b6331ab5a44d761c52/pbuilderrc If you want or need more logfiles or If you want me to do some debugging work, don't hesitate to ask. Thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pbuilder depends on: ii coreutils 8.13-3.1 ii debconf [debconf-2.0] 1.5.42 ii debianutils4.3 ii debootstrap1.0.39 ii dpkg-dev 1.16.2 ii wget 1.13.4-2 Versions of packages pbuilder recommends: ii devscripts 2.11.4 ii fakeroot1.18.2-1 ii sudo1.8.3p2-1 Versions of packages pbuilder suggests: pn cowdancer 0.68 pn gdebi-corenone pn pbuilder-uml none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667894: nginx-light: debug output in maintainer script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/07/2012 12:36 PM, Paul Wise wrote: Package: nginx-light Version: 1.1.18-1 Severity: minor There isn't any need to output this debug information in the maintainer script, please remove it: Setting up nginx-light (1.1.18-1) ... Trying a soft restart PID IS RIGHT WAITING QUIT Setting up nginx (1.1.18-1) ... -- System Information: Debian Release: wheezy/sid APT prefers experimental APT policy: (1900, 'experimental'), (1800, 'unstable'), (1700, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx-light depends on: ii libc6 2.13-27 ii libpcre3 1:8.30-4 ii libssl1.0.0 1.0.1-4 ii nginx-common 1.1.18-1 ii zlib1g 1:1.2.6.dfsg-2 Hi Paul. Thanks for reporting this bug. I just commited the needed changes in the SVN. So this bug will be resolved in the next upload. Thanks. - -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPgpzJAAoJEOcAaEhZ6aiBx9oQAIL4mM4Isoq7yaeb3fzsZzEk FsoFMy6ax9uGBItrgBrC7RjXf5tWOfUjddzYUceZSR3P5Kh+etatA751cBU1ZTxt TcMW8Dy4Ccur+141qZh/KpFAfAeCjibkBJvnKOfLAtR/wZXpxKC1qzSx/Twfhw23 Yv5+oQvOIabQSTGgMOmLb2YwcrfBPpx3UuFKebF6M9FgMceKSqKK6fermFW+E8xA 2BnEZY5DmeUFI0pk2eLezJNf6H3RHE6nnQEO99VMqpIQbfXFSAEE+vV1jp73rKhY NOiNIS1+zPJ7E+5pmdUua9Ej2qZHKST9ReIWisv0QRHUigXBcN2VFqA2vHAZJr/j YpCk+/6aT6HUjWJLBi2G1kefEGTid3bEci73oURB99jmJtbcuklF4TIPikx7lFTa eUOR8YVCS8OFo1Rg+qRbd2UEVjX5vwJi3J3W4iDxEv2IPMdDRkq048N6Qu3NY2QF ERoWG0MOL3uciiirHo/NTMrANATEQypyEja2NQE4Dbr1/Hkbr5oFoUJXLRpSL8pS GLJvF9se3ockDnsJdko40QghQwIoGjpdYIZvh9GijCIv/ID9nZaZJ1ynTwOQ5S66 NOGZSDkIBtbBPeWA5n9cb1qZeusy1nnD1E9ZMJxXa8tt7J94zE5xNU8E+/Rc0Wzt p6RuUSks6hMclLOwTCVh =1UnN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667908: nginx-full: Add 3rd party module nginx-dav-ext-module
On 04/07/2012 01:43 PM, Chris wrote: Package: nginx-full Severity: wishlist Dear Maintainer, the nginx webdav module are missing the PROPFIND OPTIONS commands for full WebDAV support. This two commands are available in a 3rd party module available here: https://github.com/arut/nginx-dav-ext-module Are there any chances to add this ext module to the nginx-full package? Thanks in advance Hi Chris. It seems to build fine, and working fine as far as I tested. So I commited the needed changes. The module will be present in nginx-full, nginx-extras and nginx-passenger in the next upload. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/28/2012 04:33 PM, Cyril Lavier wrote: On 03/26/2012 12:38 AM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 21:49:13 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : All is commited to the SVN. I'm tagging this bug as pending. The package is working fine :) But I had to add in the http section of the config: passenger_root /usr; passenger_ruby /usr/bin/ruby; maybe this could be added by default for the -passenger flavor? Cheers Laurent Bigonville Hi Laurent. I added it in the nginx.conf. Thanks. Hi Laurent. We decided to delay the inclusion of ruby-passenger in nginx as it makes the build fail under hurd-i386 and it doesn't seems to be supported by the community. For the moment, it's delayed, but it can be cancelled in the next weeks. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666115: ruby-passenger: FTBFS with NGINX on hurd-i386
On 03/28/2012 10:11 PM, Cyril Lavier wrote: On 03/28/2012 10:01 PM, Adam D. Barratt wrote: severity 666115 important thanks On Wed, 2012-03-28 at 21:49 +0200, Cyril Lavier wrote: Package: ruby-passenger Version: 3.0.11 Severity: serious Justification: fails to build from source Nope. hurd-i386 isn't a release architecture, so a failure to build that's specific to that architecture isn't release critical. (Even if it were a release architecture, the package has never built there, so the bug again wouldn't be release-critical.) Regards, Adam Thanks for these explanations. I didn't know the exact differences between serious and important on severity. Hi. Just for information, we decided to delay the inclusion of this module into nginx. The main reason being this build fail (as the nginx without passenger succeeds). The second reason is passenger in nginx doesn't seems to be supported by the community. For the moment, we decided to delay the inclusion, but it can become a complete cancellation in the next weeks. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/26/2012 12:38 AM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 21:49:13 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : All is commited to the SVN. I'm tagging this bug as pending. The package is working fine :) But I had to add in the http section of the config: passenger_root /usr; passenger_ruby /usr/bin/ruby; maybe this could be added by default for the -passenger flavor? Cheers Laurent Bigonville Hi Laurent. I added it in the nginx.conf. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666115: ruby-passenger: FTBFS with NGINX on hurd-i386
Package: ruby-passenger Version: 3.0.11 Severity: serious Justification: fails to build from source Dear Maintainer, I tested the nginx 1.1.18 build under hurd-i386, and here is the error log for nginx-passenger : (in /root/compile/nginx-1.1.18/debian/modules/ruby-passenger) mkdir -p ext/common/libboost_oxt g++ -Iext -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -o ext/common/libboost_oxt/aggregate.o -c ext/common/libboost_oxt/aggregate.cpp mkdir -p ext/common/libboost_oxt rm -rf ext/common/libboost_oxt.a ar cru ext/common/libboost_oxt.a ext/common/libboost_oxt/aggregate.o ranlib ext/common/libboost_oxt.a mkdir -p ext/common/libpassenger_common g++ -Iext -Iext/common -I/usr/include/libev -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -o ext/common/libpassenger_common/aggregate.o -c ext/common/libpassenger_common/aggregate.cpp In file included from ext/common/ServerInstanceDir.h:42:0, from ext/common/AccountsDatabase.h:33, from ext/common/AccountsDatabase.cpp:31, from ext/common/libpassenger_common/aggregate.cpp:5: ext/common/Utils.h: In constructor ‘Passenger::BufferedUpload::BufferedUpload(const string, const char*)’: ext/common/Utils.h:403:14: error: ‘PATH_MAX’ was not declared in this scope ext/common/Utils.h:406:12: error: ‘templ’ was not declared in this scope In file included from ext/common/libpassenger_common/aggregate.cpp:10:0: ext/common/Utils.cpp: In function ‘std::string Passenger::resolveSymlink(const string)’: ext/common/Utils.cpp:240:11: error: ‘PATH_MAX’ was not declared in this scope ext/common/Utils.cpp:243:32: error: ‘buf’ was not declared in this scope ext/common/Utils.cpp: In function ‘void Passenger::removeDirTree(const string)’: ext/common/Utils.cpp:531:15: error: ‘PATH_MAX’ was not declared in this scope ext/common/Utils.cpp:534:11: error: ‘command’ was not declared in this scope In file included from ext/common/libpassenger_common/aggregate.cpp:13:0: ext/common/Utils/IOUtils.cpp: In function ‘ssize_t Passenger::gatheredWrite(int, const Passenger::StaticString*, unsigned int, std::string)’: ext/common/Utils/IOUtils.cpp:732:61: error: ‘IOV_MAX’ was not declared in this scope ext/common/Utils/IOUtils.cpp:785:61: error: ‘IOV_MAX’ was not declared in this scope ext/common/Utils/IOUtils.cpp: In function ‘void Passenger::gatheredWrite(int, const Passenger::StaticString*, unsigned int, long long unsigned int*)’: ext/common/Utils/IOUtils.cpp:874:69: error: ‘IOV_MAX’ was not declared in this scope rake aborted! Command failed with status (1): [g++ -Iext -Iext/common -I/usr/include/libe...] Tasks: TOP = nginx = agents/nginx/PassengerHelperAgent = ext/common/libpassenger_common.a = ext/common/libpassenger_common/aggregate.o (See full trace by running task with --trace) make: *** [config.status.passenger] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1350: dpkg-buildpackage -rfakeroot -D -us -uc failed Apparently, ruby-passenger uses PATH_MAX, which does not exists under hurd-i386. Thanks for taking time to work on this bug. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666115: ruby-passenger: FTBFS with NGINX on hurd-i386
On 03/28/2012 10:01 PM, Adam D. Barratt wrote: severity 666115 important thanks On Wed, 2012-03-28 at 21:49 +0200, Cyril Lavier wrote: Package: ruby-passenger Version: 3.0.11 Severity: serious Justification: fails to build from source Nope. hurd-i386 isn't a release architecture, so a failure to build that's specific to that architecture isn't release critical. (Even if it were a release architecture, the package has never built there, so the bug again wouldn't be release-critical.) Regards, Adam Thanks for these explanations. I didn't know the exact differences between serious and important on severity. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/25/2012 03:54 PM, Laurent Bigonville wrote: Le Sat, 24 Mar 2012 19:17:34 +0100, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : Hi Laurent. Hi, I was starting to work on a nginx-passenger flavour, and there's something I don't understand. The ruby-passenger package doesn't contains any module source NGINX can build with --add-module. So for now, I'm unable to build such a package. In the patch I've attached to this bug I've embedded the passenger source tree. I'm actually afraid that nginx will create files outside its build directory (next to the passenger sources). Laurent Bigonville You are right, I completely forgot that. So I just tried to build the new package, and here is the error : --- cd /tmp/buildd/nginx-1.1.17/debian/build-passenger CFLAGS=`dpkg-buildflags --get CFLAGS` -Wall `dpkg-buildflags --get CPPFLAGS` CORE_LINK=`dpkg-buildflags --get LDFLAGS` ./configure \ --prefix=/etc/nginx \ --conf-path=/etc/nginx/nginx.conf \ --error-log-path=/var/log/nginx/error.log \ --http-client-body-temp-path=/var/lib/nginx/body \ --http-fastcgi-temp-path=/var/lib/nginx/fastcgi \ --http-log-path=/var/log/nginx/access.log \ --http-proxy-temp-path=/var/lib/nginx/proxy \ --http-scgi-temp-path=/var/lib/nginx/scgi \ --http-uwsgi-temp-path=/var/lib/nginx/uwsgi \ --lock-path=/var/lock/nginx.lock \ --pid-path=/var/run/nginx.pid \ --with-debug \ --with-http_addition_module \ --with-http_dav_module \ --with-http_geoip_module \ --with-http_gzip_static_module \ --with-http_image_filter_module \ --with-http_realip_module \ --with-http_stub_status_module \ --with-http_ssl_module \ --with-http_sub_module \ --with-http_xslt_module \ --with-ipv6 \ --with-sha1=/usr/include/openssl \ --with-md5=/usr/include/openssl \ --with-mail \ --with-mail_ssl_module \ --add-module=/tmp/buildd/nginx-1.1.17/debian/modules/nginx-echo \ --add-module=/tmp/buildd/nginx-1.1.17/debian/modules/nginx-upstream-fair \ --add-module=/tmp/buildd/nginx-1.1.17/debian/modules/ruby-passenger/ext/nginx \ config.status.passenger (in /tmp/buildd/nginx-1.1.17/debian/modules/ruby-passenger) mkdir -p ext/common/libboost_oxt g++ -Iext -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -o ext/common/libboost_oxt/aggregate.o -c ext/common/libboost_oxt/aggregate.cpp mkdir -p ext/common/libboost_oxt rm -rf ext/common/libboost_oxt.a ar cru ext/common/libboost_oxt.a ext/common/libboost_oxt/aggregate.o ranlib ext/common/libboost_oxt.a mkdir -p ext/common/libpassenger_common g++ -Iext -Iext/common -Iext/libev -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -o ext/common/libpassenger_common/aggregate.o -c ext/common/libpassenger_common/aggregate.cpp rm -rf ext/common/libpassenger_common.a ar cru ext/common/libpassenger_common.a ext/common/libpassenger_common/aggregate.o ranlib ext/common/libpassenger_common.a mkdir -p agents/nginx g++ ext/nginx/HelperAgent.cpp -o agents/nginx/PassengerHelperAgent -Iext -Iext/common -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS ext/common/libpassenger_common.a ext/common/libboost_oxt.a -lpthread -rdynamic g++ ext/common/Watchdog.cpp -o agents/PassengerWatchdog -Iext -Iext/common -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS ext/common/libpassenger_common.a ext/common/libboost_oxt.a -lpthread -rdynamic cd ext/libev/ sh /tmp/buildd/nginx-1.1.17/debian/modules/ruby-passenger/ext/libev/configure --disable-shared --enable-static configure: error: C compiler cannot create executables See `config.log' for more details. rake aborted! Command failed with status (77): [cd ext/libev/ sh /tmp/buildd/nginx-1.1] Tasks: TOP = nginx = agents/PassengerLoggingAgent = libev = ext/libev/.libs/libev.a = ext/libev
Bug#651441: passenger: Please create nginx passenger module
On 03/25/2012 06:47 PM, Cyril Lavier wrote: On 03/25/2012 03:54 PM, Laurent Bigonville wrote: Le Sat, 24 Mar 2012 19:17:34 +0100, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : Hi Laurent. Hi, I was starting to work on a nginx-passenger flavour, and there's something I don't understand. The ruby-passenger package doesn't contains any module source NGINX can build with --add-module. So for now, I'm unable to build such a package. In the patch I've attached to this bug I've embedded the passenger source tree. I'm actually afraid that nginx will create files outside its build directory (next to the passenger sources). Laurent Bigonville You are right, I completely forgot that. So I just tried to build the new package, and here is the error : --- cd /tmp/buildd/nginx-1.1.17/debian/build-passenger CFLAGS=`dpkg-buildflags --get CFLAGS` -Wall `dpkg-buildflags --get CPPFLAGS` CORE_LINK=`dpkg-buildflags --get LDFLAGS` ./configure \ --prefix=/etc/nginx \ --conf-path=/etc/nginx/nginx.conf \ --error-log-path=/var/log/nginx/error.log \ --http-client-body-temp-path=/var/lib/nginx/body \ --http-fastcgi-temp-path=/var/lib/nginx/fastcgi \ --http-log-path=/var/log/nginx/access.log \ --http-proxy-temp-path=/var/lib/nginx/proxy \ --http-scgi-temp-path=/var/lib/nginx/scgi \ --http-uwsgi-temp-path=/var/lib/nginx/uwsgi \ --lock-path=/var/lock/nginx.lock \ --pid-path=/var/run/nginx.pid \ --with-debug \ --with-http_addition_module \ --with-http_dav_module \ --with-http_geoip_module \ --with-http_gzip_static_module \ --with-http_image_filter_module \ --with-http_realip_module \ --with-http_stub_status_module \ --with-http_ssl_module \ --with-http_sub_module \ --with-http_xslt_module \ --with-ipv6 \ --with-sha1=/usr/include/openssl \ --with-md5=/usr/include/openssl \ --with-mail \ --with-mail_ssl_module \ --add-module=/tmp/buildd/nginx-1.1.17/debian/modules/nginx-echo \ --add-module=/tmp/buildd/nginx-1.1.17/debian/modules/nginx-upstream-fair \ --add-module=/tmp/buildd/nginx-1.1.17/debian/modules/ruby-passenger/ext/nginx \ config.status.passenger (in /tmp/buildd/nginx-1.1.17/debian/modules/ruby-passenger) mkdir -p ext/common/libboost_oxt g++ -Iext -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -o ext/common/libboost_oxt/aggregate.o -c ext/common/libboost_oxt/aggregate.cpp mkdir -p ext/common/libboost_oxt rm -rf ext/common/libboost_oxt.a ar cru ext/common/libboost_oxt.a ext/common/libboost_oxt/aggregate.o ranlib ext/common/libboost_oxt.a mkdir -p ext/common/libpassenger_common g++ -Iext -Iext/common -Iext/libev -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS -o ext/common/libpassenger_common/aggregate.o -c ext/common/libpassenger_common/aggregate.cpp rm -rf ext/common/libpassenger_common.a ar cru ext/common/libpassenger_common.a ext/common/libpassenger_common/aggregate.o ranlib ext/common/libpassenger_common.a mkdir -p agents/nginx g++ ext/nginx/HelperAgent.cpp -o agents/nginx/PassengerHelperAgent -Iext -Iext/common -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS ext/common/libpassenger_common.a ext/common/libboost_oxt.a -lpthread -rdynamic g++ ext/common/Watchdog.cpp -o agents/PassengerWatchdog -Iext -Iext/common -D_REENTRANT -I/usr/local/include -DHASH_NAMESPACE=__gnu_cxx -DHASH_NAMESPACE=__gnu_cxx -DHASH_FUN_H=hash_fun.h -DHAS_ALLOCA_H -DHAS_SFENCE -DHAS_LFENCE -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers -g -DPASSENGER_DEBUG -DBOOST_DISABLE_ASSERTS ext/common/libpassenger_common.a ext/common/libboost_oxt.a -lpthread -rdynamic cd ext/libev/ sh /tmp/buildd/nginx-1.1.17/debian/modules/ruby-passenger/ext/libev/configure --disable-shared --enable-static configure: error: C compiler cannot create executables See `config.log' for more details. rake aborted! Command failed with status (77): [cd
Bug#651441: passenger: Please create nginx passenger module
On 03/25/2012 08:32 PM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 18:47:25 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : For the moment, I'm not committing anything to the SVN, as the build fails. If you have any idea on this error, don't hesitate to ask. mmmh looks like it's missing 2 build-dependencies: libev-dev and libcurl4-openssl-dev, adding these to my patch fix the FTBFS. Laurent Bigonville These 2 build-deps already are in the source package I tried to build. I uploaded the source package I'm working here : http://sources.davromaniak.eu/nginx/nginx_1.1.17-3.dsc Maybe you will find something. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/25/2012 09:13 PM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 21:07:24 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : On 03/25/2012 08:32 PM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 18:47:25 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : For the moment, I'm not committing anything to the SVN, as the build fails. If you have any idea on this error, don't hesitate to ask. mmmh looks like it's missing 2 build-dependencies: libev-dev and libcurl4-openssl-dev, adding these to my patch fix the FTBFS. Laurent Bigonville These 2 build-deps already are in the source package I tried to build. I uploaded the source package I'm working here : http://sources.davromaniak.eu/nginx/nginx_1.1.17-3.dsc Maybe you will find something. You are missing this in debian/rules: # export to avoid building embedded libev for # passenger flavour export USE_VENDORED_LIBEV = false For some reason they are trying to build a embedded version of libev, this is preventing the build. Laurent Bigonville Thanks, it builds well now. I still don't know why I missed this lines in the debian/rules file. I'm doing the needed commits to the SVN. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/25/2012 09:22 PM, Cyril Lavier wrote: On 03/25/2012 09:13 PM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 21:07:24 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : On 03/25/2012 08:32 PM, Laurent Bigonville wrote: Le Sun, 25 Mar 2012 18:47:25 +0200, Cyril Lavier cyril.lav...@davromaniak.eu a écrit : For the moment, I'm not committing anything to the SVN, as the build fails. If you have any idea on this error, don't hesitate to ask. mmmh looks like it's missing 2 build-dependencies: libev-dev and libcurl4-openssl-dev, adding these to my patch fix the FTBFS. Laurent Bigonville These 2 build-deps already are in the source package I tried to build. I uploaded the source package I'm working here : http://sources.davromaniak.eu/nginx/nginx_1.1.17-3.dsc Maybe you will find something. You are missing this in debian/rules: # export to avoid building embedded libev for # passenger flavour export USE_VENDORED_LIBEV = false For some reason they are trying to build a embedded version of libev, this is preventing the build. Laurent Bigonville Thanks, it builds well now. I still don't know why I missed this lines in the debian/rules file. I'm doing the needed commits to the SVN. Thanks. All is commited to the SVN. I'm tagging this bug as pending. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/23/2012 02:17 PM, Laurent Bigonville wrote: Package: src:nginx Followup-For: Bug #651441 Hi, I've just uploaded a new version of passenger in unstable which contains ruby-passenger package. I'm not sure this is mandatory, but I guess you maybe want to add a version against ruby-passenger, something like: ruby-passenger ( 3.0.11debian), ruby-passenger ( 3.0.11debian-z) To be sure the same upstream version is installed. Cheers Laurent Bigonville -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Hi Laurent. I was starting to work on a nginx-passenger flavour, and there's something I don't understand. The ruby-passenger package doesn't contains any module source NGINX can build with --add-module. So for now, I'm unable to build such a package. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664090: Hardening flags still missing
On 03/16/2012 09:51 PM, Cyril Lavier wrote: On 03/16/2012 09:42 PM, Simon Ruderich wrote: reopen 664090 thanks Hello Kartik, The hardening flags are still missing because you forgot to commit the patch attached to my original report. The build system (src/http/modules/perl/Makefile.PL) needs to be patched (just putting the patch in debian/patches/ and adding the name to debian/patches/series is enough). $ hardening-check /usr/lib/perl5/auto/nginx/nginx.so /usr/lib/perl5/auto/nginx/nginx.so: Position Independent Executable: no, regular shared library (ignored) Stack protected: no, not found! Fortify Source functions: no, only unprotected functions found! Read-only relocations: no, not found! Immediate binding: no not found! Regards, Simon Oh Sorry. I applied your patch for the debian/rules but I forgot to import the Makefile.PL patch. I will perform this in the next days (maybe sunday). Thanks. Hi. I just commited the needed changes. Here is the output of hardening-check : root@grunthos:/tmp/nginx-extras/usr/lib/perl5/auto/nginx# hardening-check nginx.so nginx.so: Position Independent Executable: no, regular shared library (ignored) Stack protected: no, not found! Fortify Source functions: no, only unprotected functions found! Read-only relocations: yes Immediate binding: no not found! Apparently, it seems good. If you see anything strange, don't hesitate to answer. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662697: nginx-extras: Package removes nginx.conf and other config files on upgrade.
On 03/10/2012 06:59 PM, Kartik Mistry wrote: On Sat, Mar 10, 2012 at 6:29 PM, Cyril Lavier cyril.lav...@davromaniak.eu wrote: I just tried to upgrade nginx-extras to 1.1.16-1 on my debian Sid machine, and I didn't had this issue. Could you explain us clearly what you did to upgrade nginx-extras ? To the other maintainers : could you take time to try to reproduce this bug, maybe one of ourselves will be able to reproduce it and therefor, trying to produce a fix. I upgraded from nginx-full -- nginx-extras and it didn't removed any of my configuration too. As all the nginx maintainers tried and were not able to reproduce this issue (I tried again twice this morning), I'm closing this bug. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664212: nginx: debian/rules file is using dpkg-buildflags without defining build-dependency on dpkg-dev (= 1.15.7)
On 03/16/2012 07:09 PM, Laurent Bigonville wrote: Package: nginx Version: 1.1.14-1 Severity: serious Hi, debian/rules file is using dpkg-buildflags. This tool has been introduced in dpkg 1.15.7, but the package is not defining any build-dependency on this version of dpkg. The build is not failing but this definitly should be fixed. Cheers Laurent Bigonville -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Hi Laurent. Thanks for this report, it makes the package cleaner. I just commited the fix in the SVN. It will be fixed in the next upload (probably for 1.1.18). Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
Hi. I think the best solution for us nginx maintainers would be a passenger-src package. We add it in the build-deps, then we add a --add-module=/path/to/the/passenger/module/sources in the debian/rules, and we build. After, I think it has its place in nginx-extras, because I don't think usefull to add it in -full as it's a very particular module. Also, I don't know what is the best solution for passenger's maintainers. So we can discuss it. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651441: passenger: Please create nginx passenger module
On 03/16/2012 09:13 PM, Laurent Bigonville wrote: Le Fri, 16 Mar 2012 19:46:57 +0100, Laurent Bigonvillebi...@debian.org a écrit : Hi, I'm reassigning this to ngnix package. I'm not too sure how this could be solved. One solution would be to embed the code of passenger (or a part of it) in debian/modules directory. But code duplication is bad(tm) I actually have a package that is compiling with this solution, it's how ever not tested yet. Cheers Laurent Bigonville HI Laurent. Can you upload it anywhere ? Maybe I will find some time tomorrow to adapt it to the 1.1.17 package. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664090: Hardening flags still missing
On 03/16/2012 09:42 PM, Simon Ruderich wrote: reopen 664090 thanks Hello Kartik, The hardening flags are still missing because you forgot to commit the patch attached to my original report. The build system (src/http/modules/perl/Makefile.PL) needs to be patched (just putting the patch in debian/patches/ and adding the name to debian/patches/series is enough). $ hardening-check /usr/lib/perl5/auto/nginx/nginx.so /usr/lib/perl5/auto/nginx/nginx.so: Position Independent Executable: no, regular shared library (ignored) Stack protected: no, not found! Fortify Source functions: no, only unprotected functions found! Read-only relocations: no, not found! Immediate binding: no not found! Regards, Simon Oh Sorry. I applied your patch for the debian/rules but I forgot to import the Makefile.PL patch. I will perform this in the next days (maybe sunday). Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664137: [CVE-2012-1180] nginx fix for malformed HTTP responses from upstream servers
On 03/15/2012 08:54 PM, Luciano Bello wrote: Package: nginx Severity: grave Tags: security patch The following vulnerability had been reported against nginx: http://seclists.org/oss-sec/2012/q1/644 The patch can be found in the report. Please use CVE-2012-1180 for this issue. Can you check if the stable version is affected? Cheers, luciano Hi Luciano. The 1.1.17 will be uploaded tomorrow, we already done the needed test for the upload (build and functionality). Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664137: [CVE-2012-1180] nginx fix for malformed HTTP responses from upstream servers
On 03/15/2012 09:28 PM, Luciano Bello wrote: On Thursday 15 March 2012, Cyril Lavier wrote: The 1.1.17 will be uploaded tomorrow, we already done the needed test for the upload (build and functionality). Great! Can you check if stable is affected? The bug looks quite important. Do you think that stable should be updated by a DSA? Thanks, -l Apparently, stable (and oldstable) are affected by the issue. I'm working on adapting the upstream patch to the nginx stable package. I think stable should be updated by a DSA, and Kartik scheduled it when we talk about uploading the 1.1.17 to unstable. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664137: [CVE-2012-1180] nginx fix for malformed HTTP responses from upstream servers
On 03/15/2012 09:34 PM, Cyril Lavier wrote: On 03/15/2012 09:28 PM, Luciano Bello wrote: On Thursday 15 March 2012, Cyril Lavier wrote: The 1.1.17 will be uploaded tomorrow, we already done the needed test for the upload (build and functionality). Great! Can you check if stable is affected? The bug looks quite important. Do you think that stable should be updated by a DSA? Thanks, -l Apparently, stable (and oldstable) are affected by the issue. I'm working on adapting the upstream patch to the nginx stable package. I think stable should be updated by a DSA, and Kartik scheduled it when we talk about uploading the 1.1.17 to unstable. Thanks. So I just finished adapting the patch. It builds and works well. It's here : http://paste.davromaniak.eu/index.php?show=71 The source package including the patch is here (use dget to download it ;)): http://sources.davromaniak.eu/nginx/nginx_0.7.67-3+squeeze2.dsc For old-stable, I don't have time tonight, so if anybody is willing to do it, don't hesitate :). Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662997: nginx: /var/run/php5-fpm.sock
On 03/11/2012 06:13 PM, Olaf van der Spek wrote: On Sat, Mar 10, 2012 at 7:55 PM, Cyril Lavier cyril.lav...@davromaniak.eu wrote: We are not providing any sample conf to use PHP-FPM (only fastcgi), so there's no need to update the sample conf files. FPM is FastCGI. Your are right. I misspoke. But we can run PHP via fastcgi alone (this is what I use), and in the sample config file, we don't talk about FPM, only the fastcgi alone. But now, it's fixed in my last commit (and I messed up updating the tags, grrr). Isn't FPM the recommended way to run PHP via FastCGI? I don't know, but that's a good question, and we (the maintainers) may decide to recommend one technology. Olaf Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662799: nginx: please include systemd packaging
On 03/06/2012 02:50 PM, Michael Stapelberg wrote: Package: nginx Severity: wishlist Tags: patch Hi, attached you can find a systemd service file for nginx along with the corresponding Debian packaging. systemd is a sysvinit replacement (see [1] for more information). I tested these changes on my system and, to the best of my knowledge, they work just like the initscript. If you have any questions, please do not hesitate to contact me. Thanks! Best regards, Michael [1] http://en.wikipedia.org/wiki/Systemd For Debian-specific documentation, see also http://wiki.debian.org/systemd Hi Michael. Thanks for this useful help. I just applied the patch to the SVN and commited the changes. So now, nginx is ready to use systemd :). Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662697: nginx-extras: Package removes nginx.conf and other config files on upgrade.
On 03/05/2012 09:43 PM, Gasper Zejn wrote: Package: nginx-extras Version: 1.1.16-1 Severity: grave Justification: renders package unusable Dear Maintainer, while upgrading (via apt-get upgrade), the package removes its configuration files. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=sl_SI.UTF-8, LC_CTYPE=sl_SI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx-extras depends on: ii libc6 2.13-27 ii libgd2-xpm 2.0.36~rc1~dfsg-6 ii libgeoip1 1.4.8+dfsg-3 ii liblua5.1-0 5.1.4-12 ii libpcre38.12-4 ii libperl5.14 5.14.2-9 ii libssl1.0.0 1.0.0g-1 ii libxml2 2.7.8.dfsg-7 ii libxslt1.1 1.1.26-8 ii nginx-common1.1.16-1 ii perl5.14.2-9 ii perl-base [perlapi-5.14.2] 5.14.2-9 ii zlib1g 1:1.2.6.dfsg-2 nginx-extras recommends no packages. nginx-extras suggests no packages. -- no debconf information Hi Gasper. Thanks for reporting this bug. I just tried to upgrade nginx-extras to 1.1.16-1 on my debian Sid machine, and I didn't had this issue. Could you explain us clearly what you did to upgrade nginx-extras ? To the other maintainers : could you take time to try to reproduce this bug, maybe one of ourselves will be able to reproduce it and therefor, trying to produce a fix. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662997: nginx: /var/run/php5-fpm.sock
On 03/07/2012 10:52 PM, Olaf van der Spek wrote: Package: nginx Version: 1.1.16-1 Severity: normal Hi, PHP FPM now uses /var/run/php5-fpm.sock instead of TCP. Could you update the default conf? Greetings, Olaf -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx depends on: ii nginx-full 1.1.16-1 nginx recommends no packages. nginx suggests no packages. -- no debconf information Hi Olaf. Thanks for this report. We are not providing any sample conf to use PHP-FPM (only fastcgi), so there's no need to update the sample conf files. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641701: audacious-plugins: Plugin ffaudio vanished, no plugin for wma
On 02/23/2012 10:14 PM, Дмитрий wrote: Hi everybody This bug is NOT fixed (or reappeared) in 3.2.1-1 (and Ubuntu's 3.2.1-1ubuntu1). From build logs (https://buildd.debian.org/status/fetch.php?pkg=audacious-pluginsarch=i386ver=3.2.1-1stamp=1329773883): checking for FFMPEG... no ... Input Plugins - MPEG-1 Layer I/II/III (mpg123): yes MPEG-2/4 AAC (aac): yes FFaudio (ffaudio): no Module decoder (modplug): yes The same thing with Ubuntu's packages. Logs from my Ubuntu Precise box (config.log): configure:10910: checking for FFMPEG configure:10917: $PKG_CONFIG --exists --print-errors libavcodec= 53.40.0 libavformat= 53.5.0 libavutil= 50.42.0 Requested 'libavcodec= 53.40.0' but version of libavcodec is 53.34.0 configure:10920: $? = 1 configure:10934: $PKG_CONFIG --exists --print-errors libavcodec= 53.40.0 libavformat= 53.5.0 libavutil= 50.42.0 Requested 'libavcodec= 53.40.0' but version of libavcodec is 53.34.0 configure:10937: $? = 1 configure:10951: result: no Requested 'libavcodec= 53.40.0' but version of libavcodec is 53.34.0 It seems that 'configure' script was not updated after applying ffaudio.so, as after doing 'autoreconf' I have: configure:10572: checking for FFMPEG configure:10579: $PKG_CONFIG --exists --print-errors libavcodec= 52.64.0 libavformat= 52.110.0 libavutil= 50.42.0 configure:10582: $? = 0 configure:10596: $PKG_CONFIG --exists --print-errors libavcodec= 52.64.0 libavformat= 52.110.0 libavutil= 50.42.0 configure:10599: $? = 0 configure:10637: result: yes Hi. Thanks for reporting this issue. I think it's related with dh $@ --parallel -Sautoconf, which doesn't perform the autoreconf needed, in the debian/rules. If I have time tomorrow, I will try to work on this. If not, I will do it on Saturday. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660408: nginx-light: Please add Auth PAM module
On 02/20/2012 04:58 PM, Peter Colberg wrote:
Hi Cyril, hi Jamie,
On Mon, Feb 20, 2012 at 09:12:56AM -0600, Jamie wrote:
This would be a fantastic feature-add for us as it allows custom
cloud-auth PAM modules too; for example, we can authenticate
against Amazon IAM, Simple DB, Secure Remote Protocol, or anything
else we could imagine using pam_redirector. This might require an
unacceptable combination of dependencies for the build process, but
for us, at least, this would be an incredible feature.
Thanks for advocating the Auth PAM module :-).
This is exactly my selling point. While the auth_ldap module is
restricted to LDAP, and even then may only cover a subset of LDAP
authentication scenarios (since it has to implement each one of them),
the auth_pam module should allow anything supported by a PAM module.
Hmm, interesting.
So with only the Auth PAM module, we can cover any auth system from LDAP
to a SQL database (don't know if pam_mysql still exists) and local users.
On 02/20/2012 01:54 AM, Cyril LAVIER wrote:
Honestly, I don't think using PAM is a good way to perform a LDAP
authentication with NGINX, mainly because it requires further
configuration in other packages than NGINX.
Consider it from a different angle: All the nasty implementation
details of LDAP authentication are handled outside of nginx, e.g.
by libpam-ldap or libpam-ldapd, so you as a maintainer do not have
to worry about getting bug reports on memory leaks and such.
Before nginx, I was using lighttpd. It contains an LDAP authentication
module, which worked well, but unsurprisingly, given the complexity of
LDAP, had bugs as well, e.g. “mod_auth leaks ldap connections” [1].
The bug(s) were of course fixed, but this requires active upstream
developers as in the case of lighttpd (and nginx itself).
[1] http://redmine.lighttpd.net/issues/1066
Further, I would consider the Auth PAM module feature-complete.
You convinced me. It's better to have a single module which can enable
authentication on PAM, and leave PAM do what he knows best.
I would not worry about the configuration too much. There would be no
configuration shipped with the nginx-* packages anyway, since there
is no default scenario. I would rather include a few examples in
the README.Debian or other file. For example, a user comfortable with
handling LDAP will be more than capable of configuring a PAM service.
This is my configuration right now:
#
# /etc/nginx/sites-available/example.org
#
location / {
auth_pam example.org;
auth_pam_service_name nginx;
}
#
# /etc/pam.d/nginx - LDAP authentication for nginx webserver
#
auth required pam_ldap.so config=/etc/nginx/pam_ldap.conf
account required pam_ldap.so config=/etc/nginx/pam_ldap.conf
#
# /etc/nginx/pam_ldap.conf
#
base ou=redmine,dc=example,dc=org
uri ldapi:///
ldap_version 3
binddn cn=httpd,dc=example,dc=org
bindpw *
scope sub
pam_password md5
Ok, that's not so complicated.
In case we need another base for another vhost, does something like this
work ?
#
# /etc/nginx/sites-available/vhost1.example.org
#
location / {
auth_pam whost1.example.org;
auth_pam_service_name nginx_vhost1;
}
#
# /etc/pam.d/nginx_vhost1 - LDAP authentication for nginx webserver
#
auth required pam_ldap.so config=/etc/nginx/pam_ldap_vhost1.conf
account required pam_ldap.so config=/etc/nginx/pam_ldap_vhost1.conf
#
# /etc/nginx/pam_ldap_vhost1.conf
#
base ou=othervhost,dc=example,dc=org
uri ldapi:///
ldap_version 3
binddn cn=httpd,dc=example,dc=org
bindpw *
scope sub
pam_password md5
In the case it's working, this would be more efficient and flexible.
Also, did you tried to build/use the module against libpam-ldapd,
which is used by some people in place of libpam-ldap.
I did not test libpam-ldapd yet, but I see no reason why it should not
work. The choice of pam_ldap module should not affect the interface
between nginx and pam.
Ok. I was asking because I recently had issues with thunderbird and
pam_ldap, and I had to switch to pam_ldapd.
Even if I'm not convinced, I let you a chance to sell me (and
maybe us, the whole maintaining team) this module, and the
advantage of using PAM instead of directly connecting to a LDAP
directory with NGINX.
By the way, adding a module for LDAP authentication is one of the
tasks on our goals for the Wheezy freeze. We found this module
(https://github.com/kvspb/nginx-auth-ldap) which directly connects
to a LDAP directory, and I have been using it over the last
months, and I didn't had any instabilities with it.
It's good to know that nginx-auth-ldap is being tested. I was already
aware of the module before, but refrained from using it. I assume that
LDAP auth adds a lot more complexity to nginx than the PAM auth.
With the other module, it's not complicated, but what you presented is
easier to manage.
Also, the other module doesn't seems to be actively maintained, and this
is why it's not included
Bug#660408: nginx-light: Please add Auth PAM module
Le 18.02.2012 23:35, Peter Colberg a écrit : Package: nginx-light Version: 1.1.14-1 Severity: wishlist Tags: patch Dear Maintainer, Currently upstream nginx only supports authentication based on a htpasswd file. Authentication based on, e.g., an LDAP or PostgreSQL database is not possible without resorting to custom FastCGI backend software, which in some cases is excessively complex, e.g. when serving password-protected static content. I have been using a version of the nginx Debian package patched with the ngx_http_auth_pam_module, together with libpam-ldap, for years now, and found it to be a simple and stable solution for LDAP authentication. http://web.iti.upv.es/~sto/nginx/ It would be nice to have Auth PAM included in the nginx-* Debian packages. If so, I could help with writing a README example for LDAP authentication. Thanks, Peter Hi Peter. Thanks for this report. Honestly, I don't think using PAM is a good way to perform a LDAP authentication with NGINX, mainly because it requires further configuration in other packages than NGINX. Also, did you tried to build/use the module against libpam-ldapd, which is used by some people in place of libpam-ldap. Even if I'm not convinced, I let you a chance to sell me (and maybe us, the whole maintaining team) this module, and the advantage of using PAM instead of directly connecting to a LDAP directory with NGINX. By the way, adding a module for LDAP authentication is one of the tasks on our goals for the Wheezy freeze. We found this module (https://github.com/kvspb/nginx-auth-ldap) which directly connects to a LDAP directory, and I have been using it over the last months, and I didn't had any instabilities with it. Talking about the inclusion of a LDAP auth module in nginx-light (and all other flavours), I don't see any issues, as the light flavour already has the auth-basic, it's logical to have the ldap-auth in it. Kartik, Michael, Dmitry, Jose and Fabio, what are your thoughts about this module ? Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659820: audacious FTBFS on sparc with ICE
Le 13.02.2012 23:07, peter green a écrit : Source: audacious Version: 3.2-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) audacious FTBFS on sparc with an internal compiler error. This has been reported to the gcc maintainers at http://bugs.debian.org/659793 but past experinace has taught me that it takes quite some time for them to resolve such issues In the meantime I have prepared the attatched patch which drops the optimisation level to -O1 on sparc and also makes a small fix to debian/rules clean. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: sparc (sparc64) Kernel: Linux 2.6.32-5-sparc64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Hi Peter. Thanks for this patch. I just applied it, and I'm working on a 3.2-2 package. Thanks. -- Cyril Davromaniak Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641701: A patch for ffaudio with audacious 3.2
On 01/28/2012 10:32 PM, Cyril Lavier wrote:
On 01/28/2012 07:51 PM, Reinhard Tartler wrote:
On Sa, Jan 28, 2012 at 18:41:06 (CET), Cyril Lavier wrote:
[...]
Hi.
I didn't choose anything, I just took the patch which Andrei did, just
rewrote it and applied it to the sources. But I agree with your
comment,
as I don't know why he chose those particular version.
I see. Can you ask him to clarify? I guess that clarification is best
documented by a source-code comment.
I just asked him, let's wait until he answers.
I will work on reducing these requirements for easing the making of a
squeeze-backport (as I'm the backporter, I won't have to work twice on
the patch).
Since libav 0.7 (and soon 0.8) is available in squeeze-backports, I
wouldn't spend too much time on that. Just build against libav in
squeeze-backports and be done with that.
You are right.
I just made a quick build of audacious and audacious-plugins on a
squeeze-backports pbuilder, and the only issues I had are with others
libs (libbs2b-dev for audacious-plugins, libguess-dev and
libuchardet-dev for audacious which are not available in stable). The
build went well.
I just tested the packages on a Squeeze laptop, and he plays wma files
like a charm, so it confirms the well done build :).
I completely understand that upgrading the needed libs is quite risky
and won't be done in the next days/weeks without risking to break
a lot
of packages.
What libraries would require updates? Currently, we do ship up-to-date
packages.
Sorry, I completely messed this paragraph, I was writing 2 mails at the
same time and my colleagues might think I'm crazy now, after talking
about audacious in a corporate mail about an off-hours product update
which turned bad :/.
no problem :-)
So I would like to know what do you think about this patch, if
this can
be a good solution, and then I will perform the needed changes and
push
it to the git repo or if you think it's not a good solution, we won't
have the plugin working for now.
The configure part can be dropped if you run the autofoo toolchain on
the buildds (cf. dh-autoreconf or similar).
Thanks for this idea.
The ffaudio-core part looks reasonable to me on the first sight. It
could probably simplified a bit by requiring libav{codec,format}= 53
Cheers,
Reinhard
Thanks for this quick review.
I will focus on making this patch working for debian squeeze and more
testing with this patch activated.
see above wrt squeeze-backports.
Cheers,
Reinhard
Thanks.
Hi Reinhard.
I got the answer right here :
http://redmine.audacious-media-player.org/boards/1/topics/89?r=121#message-121
So apparently, the versions choosed were the last specified before they
increased version requirements.
Also, John Lindgren explains why the libavcodec 52.64.0 is required (an
API change in FFMPEG).
Sorry for the late answer, I had a busy week working on nginx packaging
(fixing the last goals for the wheezy freeze, and starting to make
people work as a team).
Thanks.
--
Cyril Davromaniak Lavier
KeyID 59E9A881
http://www.davromaniak.eu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650847: No TTA (True Audio) support.
Hi. Thanks for pointing us this error. I made the change, so it will be fixed in the next upload. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645347: Seems to be fixed in the 3.2 release
Hi. I justed tested Audacious with an audio CD, and I didn't have any issue. I plan to close this bug with the next upload. Could you confirm you can play CDs with the 3.2 release ? Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644554: Unable to reproduce with 3.2
Hi. Thanks for reporting this bug. I just tested performing repeat and shuffle on a single playlist containing only mp4 files, and I was not able to recreate the issue with audacious 3.2. Could you try this on your side (with the 3.2) to confirm this issue has been resolved ? Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589756: Roaraudio support removed from 3.2
Hi. The roaraudio plugin has been removed from Audacious with a commit on December 21st 2011. So this bug is not applicable anymore. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636847: Fixed in 3.2
Hi. As the libnotify-dev package is now a build-dependency of audacious-plugins, I consider this bug fixed. It will be closed in the next upload. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654593: nginx-extras: Please add upload module
On 01/04/2012 07:18 PM, Antti Kaihola wrote: 2012/1/4 Kartik Mistry kartik.mis...@gmail.com mailto:kartik.mis...@gmail.com Ok. adding it with next commit. But: https://github.com/vkholodkov/nginx-upload-module/issues/26#issuecomment-3357444 so, holding off upload until upstream resolves issue. Makes sense. On the surface it looks like a simple issue. Let's hope nothing nasty is hiding behind it :) Despite their similar names, the upload and uploadprogress modules serve indeed very different purposes. Uploadprogress is for tracking conventional uploads with AJAX polling, whereas the upload module handles the entire file transfer procedure before handing the resulting uploaded file to the web application. Thanks for accepting this proposal! Good evening. Apparently, upstream was doing nothing. But I decided to go on and apply the fix I proposed. Maybe this will motivate him to apply a fix in the GIT repo. I also took this decision because I tested the module over the last 2 weeks (with nginx 1.1.13) on an internal service in my company, no issues were reported by users, and nothing bad in the log files, so I consider the build issue was minor, and thus not affecting the overall functioning of the module. I also answered in the issue on github. Thanks. -- Cyril Davromaniak Lavier
Bug#641701: A patch for ffaudio with audacious 3.2
Hi.
On the audacious forum, Andrei Alin proposed a patch for this.
I tried to include it in the audacious-plugins source package (I rewrote
it, using autoconf for regenerate the configure file). It builds fine
and the ffaudio plugin is enabled again (not enabled in the 3.2-1).
I don't know if I will include it in the next upload (I don't even know
if I will push it in the GIT repo), as it's a quite big patch. But
audacious developers are not going to make the plugin compatible with
older versions of ffmpeg.
I completely understand that upgrading the needed libs is quite risky
and won't be done in the next days/weeks without risking to break a lot
of packages.
So I would like to know what do you think about this patch, if this can
be a good solution, and then I will perform the needed changes and push
it to the git repo or if you think it's not a good solution, we won't
have the plugin working for now.
Thanks.
--
Cyril Davromaniak Lavier
Description: Make audacious work with current unstable version of FFAUDIO
Author: Andrei Alin and...@webupd8.org
Last-Update: 2012-01-28
--- a/configure.ac
+++ b/configure.ac
@@ -549,7 +549,7 @@
if test $enable_ffaudio = yes ; then
PKG_CHECK_MODULES([FFMPEG],
- [libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0],
+ [libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0],
[have_ffaudio=yes], [have_ffaudio=no])
fi
--- a/configure
+++ b/configure
@@ -10914,12 +10914,12 @@
pkg_cv_FFMPEG_CFLAGS=$FFMPEG_CFLAGS
elif test -n $PKG_CONFIG; then
if test -n $PKG_CONFIG \
-{ { $as_echo $as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0\; } 5
- ($PKG_CONFIG --exists --print-errors libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0) 25
+{ { $as_echo $as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0\; } 5
+ ($PKG_CONFIG --exists --print-errors libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0) 25
ac_status=$?
$as_echo $as_me:${as_lineno-$LINENO}: \$? = $ac_status 5
test $ac_status = 0; }; then
- pkg_cv_FFMPEG_CFLAGS=`$PKG_CONFIG --cflags libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0 2/dev/null`
+ pkg_cv_FFMPEG_CFLAGS=`$PKG_CONFIG --cflags libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0 2/dev/null`
test x$? != x0 pkg_failed=yes
else
pkg_failed=yes
@@ -10931,12 +10931,12 @@
pkg_cv_FFMPEG_LIBS=$FFMPEG_LIBS
elif test -n $PKG_CONFIG; then
if test -n $PKG_CONFIG \
-{ { $as_echo $as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0\; } 5
- ($PKG_CONFIG --exists --print-errors libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0) 25
+{ { $as_echo $as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0\; } 5
+ ($PKG_CONFIG --exists --print-errors libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0) 25
ac_status=$?
$as_echo $as_me:${as_lineno-$LINENO}: \$? = $ac_status 5
test $ac_status = 0; }; then
- pkg_cv_FFMPEG_LIBS=`$PKG_CONFIG --libs libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0 2/dev/null`
+ pkg_cv_FFMPEG_LIBS=`$PKG_CONFIG --libs libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0 2/dev/null`
test x$? != x0 pkg_failed=yes
else
pkg_failed=yes
@@ -10957,9 +10957,9 @@
_pkg_short_errors_supported=no
fi
if test $_pkg_short_errors_supported = yes; then
- FFMPEG_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0 21`
+ FFMPEG_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0 21`
else
- FFMPEG_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0 21`
+ FFMPEG_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0 21`
fi
# Put the nasty error message in config.log where it belongs
echo $FFMPEG_PKG_ERRORS 5
--- a/src/ffaudio/ffaudio-core.c
+++ b/src/ffaudio/ffaudio-core.c
@@ -40,6 +40,14 @@
#endif
#include libaudcore/audstrings.h
+#if ! CHECK_LIBAVFORMAT_VERSION (53, 5, 0)
+#define avformat_find_stream_info(i, o) av_find_stream_info (i)
+#endif
+
+#if ! CHECK_LIBAVCODEC_VERSION (53, 8, 0)
+#define avcodec_open2(a, c, o) avcodec_open (a, c)
+#endif
+
static GMutex *ctrl_mutex = NULL;
static GCond *ctrl_cond = NULL;
static gint64 seek_value = -1;
@@ -423,8 +431,11 @@
AVCodecContext *c = NULL;
AVStream *s = NULL;
AVPacket pkt = {.data = NULL};
+guint8
Bug#641701: A patch for ffaudio with audacious 3.2
On 01/28/2012 05:26 PM, Reinhard Tartler wrote:
On Sa, Jan 28, 2012 at 11:46:46 (CET), Cyril Lavier wrote:
Hi.
On the audacious forum, Andrei Alin proposed a patch for this.
I tried to include it in the audacious-plugins source package (I rewrote
it, using autoconf for regenerate the configure file). It builds fine
and the ffaudio plugin is enabled again (not enabled in the 3.2-1).
I don't know if I will include it in the next upload (I don't even know
if I will push it in the GIT repo), as it's a quite big patch. But
audacious developers are not going to make the plugin compatible with
older versions of ffmpeg.
Well, the patch *reduces* the requirements on libavformat and libavcodec
considerably (libavcodec53 - libavcodec52, and libavformat53 -
libavformat52:
--- a/configure.ac
+++ b/configure.ac
@@ -549,7 +549,7 @@
if test $enable_ffaudio = yes ; then
PKG_CHECK_MODULES([FFMPEG],
- [libavcodec= 53.40.0 libavformat= 53.5.0 libavutil= 50.42.0],
+ [libavcodec= 52.64.0 libavformat= 52.110.0 libavutil= 50.42.0],
[have_ffaudio=yes], [have_ffaudio=no])
fi
Note that these requirements do not suffice for squeeze, which ships
libavformat with these library version numbers:
24 #define LIBAVFORMAT_VERSION_MAJOR 52
25 #define LIBAVFORMAT_VERSION_MINOR 31
26 #define LIBAVFORMAT_VERSION_MICRO 0
and libavcodec with:
32 #define LIBAVCODEC_VERSION_MAJOR 52
33 #define LIBAVCODEC_VERSION_MINOR 20
34 #define LIBAVCODEC_VERSION_MICRO 1
I therefore wonder why you've chosen those particular version
requirements, since there is an updated libav package set in
squeeze-backports.
Hi.
I didn't choose anything, I just took the patch which Andrei did, just
rewrote it and applied it to the sources. But I agree with your comment,
as I don't know why he chose those particular version.
I will work on reducing these requirements for easing the making of a
squeeze-backport (as I'm the backporter, I won't have to work twice on
the patch).
I completely understand that upgrading the needed libs is quite risky
and won't be done in the next days/weeks without risking to break a lot
of packages.
What libraries would require updates? Currently, we do ship up-to-date
packages.
Sorry, I completely messed this paragraph, I was writing 2 mails at the
same time and my colleagues might think I'm crazy now, after talking
about audacious in a corporate mail about an off-hours product update
which turned bad :/.
So I would like to know what do you think about this patch, if this can
be a good solution, and then I will perform the needed changes and push
it to the git repo or if you think it's not a good solution, we won't
have the plugin working for now.
The configure part can be dropped if you run the autofoo toolchain on
the buildds (cf. dh-autoreconf or similar).
Thanks for this idea.
The ffaudio-core part looks reasonable to me on the first sight. It
could probably simplified a bit by requiring libav{codec,format}= 53
Cheers,
Reinhard
Thanks for this quick review.
I will focus on making this patch working for debian squeeze and more
testing with this patch activated.
Thanks
--
Cyril Davromaniak Lavier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657739: nginx: Regression after squeeze: no longer listens for IPv6 connections by default.
On 01/28/2012 02:14 PM, Simon Iremonger wrote: Package: nginx Version: 1.1.12-1 Severity: normal Tags: ipv6 Hi Simon. The version of nginx in Squeeze [0.7.67-3], without any reconfiguration, [in particular, without adding any explicit listen configuration], happily creates both a 0.0.0.0:80 IPv4-only and a [::]:80 IPv6-only socket. However, BOTH the nginx wheezy [1.1.12-1] and squeeze-backports [1.1.8-2~bpo60+1] versions, have the default behaviour (with similar default-config, no listen lines) of listening ONLY for Legacy IPv4 connections!! This is bad when you have a dual-stacked host with both A and pointers. For example, squid3 on the same host, connecting to the host itself by its' own name, gets 'connection refused' over IPv6 and doesn't seem to fall back to IPv4 at all. This can currenty be worked around by manually overriding the 'listen' entries in the config, to have either an IPv4 socket AND an IPv6-only-IPv6-listen-socket, or a single IPv6-with-IPv4- compatibility listen socket. We could, change the, default config file included, which creates complexity in updating, though this may be needed to make the comments in the file clear as to what is expected by default. The listen lines are already commented, but maybe we can add some words to make a more clear comment, like ## uncomment this line to listen for ipv6 and ipv4 instead of ## listen for ipv6. I also use dual stack and frankly, I don't understand why this a bad bug. Everytime I upgrade a service which is in dual stack, I test both connectivity. So it's just a matter of uncommenting a line and restart the service. And when I perform this kind of action on a production server, I always test it on another server (even a virtual machine). I would think, a neater thing to do would be to patch the code to default to IPv4+IPv6 sockets, unless the user overrides it in the config-file... I don't agree with you. IPv6 is not actually widespread, as many servers only operate with IPv4. So this could lead to other issues. Also I think it's not the aim of the Debian packaging to change such function in a packaged software. As the official documentation won't be applicable on this nginx build. But if you think you are right, you can still fill a bug directly to the nginx project (or send a mail to the mailing list). --Simon Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641701: A patch for ffaudio with audacious 3.2
On 01/28/2012 07:51 PM, Reinhard Tartler wrote:
On Sa, Jan 28, 2012 at 18:41:06 (CET), Cyril Lavier wrote:
[...]
Hi.
I didn't choose anything, I just took the patch which Andrei did, just
rewrote it and applied it to the sources. But I agree with your comment,
as I don't know why he chose those particular version.
I see. Can you ask him to clarify? I guess that clarification is best
documented by a source-code comment.
I just asked him, let's wait until he answers.
I will work on reducing these requirements for easing the making of a
squeeze-backport (as I'm the backporter, I won't have to work twice on
the patch).
Since libav 0.7 (and soon 0.8) is available in squeeze-backports, I
wouldn't spend too much time on that. Just build against libav in
squeeze-backports and be done with that.
You are right.
I just made a quick build of audacious and audacious-plugins on a
squeeze-backports pbuilder, and the only issues I had are with others
libs (libbs2b-dev for audacious-plugins, libguess-dev and
libuchardet-dev for audacious which are not available in stable). The
build went well.
I just tested the packages on a Squeeze laptop, and he plays wma files
like a charm, so it confirms the well done build :).
I completely understand that upgrading the needed libs is quite risky
and won't be done in the next days/weeks without risking to break a lot
of packages.
What libraries would require updates? Currently, we do ship up-to-date
packages.
Sorry, I completely messed this paragraph, I was writing 2 mails at the
same time and my colleagues might think I'm crazy now, after talking
about audacious in a corporate mail about an off-hours product update
which turned bad :/.
no problem :-)
So I would like to know what do you think about this patch, if this can
be a good solution, and then I will perform the needed changes and push
it to the git repo or if you think it's not a good solution, we won't
have the plugin working for now.
The configure part can be dropped if you run the autofoo toolchain on
the buildds (cf. dh-autoreconf or similar).
Thanks for this idea.
The ffaudio-core part looks reasonable to me on the first sight. It
could probably simplified a bit by requiring libav{codec,format}= 53
Cheers,
Reinhard
Thanks for this quick review.
I will focus on making this patch working for debian squeeze and more
testing with this patch activated.
see above wrt squeeze-backports.
Cheers,
Reinhard
Thanks.
--
Cyril Davromaniak Lavier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657592: xmp: FTBFS with audacious 3.2
Source: xmp Version: 3.4.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Audacious was recently updated with the 3.2 release, and now, XMP doesn't build anymore. I also tried with the 3.4.1 upstream version, and the build also fails. So I created a bug on the upstream bug tracker : http://freecode.com/projects/xmp/tickets/cd2770b6cd4 Thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657596: wmauda: FTBFS with audacious 3.2
Package: wmauda Version: 0.7-5 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Audacious was recently updated with the 3.2 release, and now wmauda doesn't build anymore. Here is the build log : CFLAGS=-Wall -g -O2 /usr/bin/make PREFIX=/usr make[1]: Entering directory `/tmp/buildd/wmauda-0.7' cc -Wall -g -O2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -c -o wmauda.o wmauda.c wmauda.c:19:21: fatal error: gtk/gtk.h: No such file or directory I already contacted the upstream about this issue. Let's wait until they answer. Thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657592: A patch seems to be available.
Hi. After some research a patch seems to be available for having XMP working with audacious 3.2. It's available here : http://pkgs.fedoraproject.org/gitweb/?p=xmp.git;a=blob_plain;f=xmp-3.4.0-audacious-3.1.patch;h=250ae80a04c53e0aeedc9a5483a637039754b7f5;hb=HEAD This patch was made for the fedora project by Michael Schwendt I'm pretty sure I won't have time to test it this weekend, so in case anybody wants to give it a try, go on :). Maybe there will be adjustments to be made in the patch, as it was written for the 3.1 release (and modified for the 3.2beta). Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657081: audacious: FTBFS on hurd-i386
On Tue, 24 Jan 2012 18:27:35 -0500, John Lindgren wrote: On 01/24/2012 08:51 AM, Cyril LAVIER wrote: Hi John. As stated in bug #639374, I'm working on packages for audacious 3.2. I hope I will be the modifications to the git repository next week (damn otitis and headaches). Thanks. Thank you, Cyril! So I just tested to build the 3.2 release under a hurd-i386 system. It builds fine, so when the packages will be ready, users of hurd-i386 will be able to use audacious and it's plugins :). I still have some work to do on checking if other bugs are resolved with the 3.2, so it will take some time. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632303:
Hi. I just tried to build the 3.2 release, and it's building well under kfreebsd-amd64. So this bug might be resolved in the next weeks. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657095: bug #657095
Hi. I just tried to build the 3.2 release, and it's building well under hurd-i386. So this bug might be resolved in the next weeks. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657081: audacious: FTBFS on hurd-i386
On Tue, 24 Jan 2012 08:39:55 -0500, John Lindgren wrote: tags 657081 fixed-upstream thanks Hi, As upstream maintainer I would much rather you simply updated Audacious in Debian to the current version, which doesn't use PATH_MAX and therefore should not have any problem building on HURD. -- John Lindgren Hi John. As stated in bug #639374, I'm working on packages for audacious 3.2. I hope I will be the modifications to the git repository next week (damn otitis and headaches). Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639374: New upstream release 3.2
Good morning. So the first tests on wheezy are now done. Audacious runs well, but apparently, it requires a newer version of ffmpeg, so for the moment, he can't decode MP3 files. Runs fine with OGG. On the forum, a developer proposed a patch for using older version of ffmpeg, but it don't seems to work on wheezy (either with sources directly patched or included in the packaging process with quilt). On unstable, I'm not able to make it work with quilt. I'm installing an unstable VM to see if the patch works directly on the sources. As the forum is down now (502 Bad Gateway error from nginx ^^), so I can't post the link of the thread containing this. So that's all for now, I will take some time later to merge my modification with the git tree, and maybe push it later next week. I think it's a not so bad start for audacious 3.2 as I don't want to rush ffmpeg maintainers to upgrade packages and maybe break a lot of stuff. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639374: New upstream release 3.2
On 01/21/2012 10:28 AM, Cyril Lavier wrote:
Good morning.
So the first tests on wheezy are now done.
Audacious runs well, but apparently, it requires a newer version of
ffmpeg, so for the moment, he can't decode MP3 files. Runs fine with OGG.
On the forum, a developer proposed a patch for using older version
of ffmpeg, but it don't seems to work on wheezy (either with sources
directly patched or included in the packaging process with quilt).
On unstable, I'm not able to make it work with quilt. I'm installing
an unstable VM to see if the patch works directly on the sources.
As the forum is down now (502 Bad Gateway error from nginx ^^), so I
can't post the link of the thread containing this.
So that's all for now, I will take some time later to merge my
modification with the git tree, and maybe push it later next week.
I think it's a not so bad start for audacious 3.2 as I don't want to
rush ffmpeg maintainers to upgrade packages and maybe break a lot of
stuff.
Thanks.
Hi again.
I sadly confirm, even with the patch applied directly to the sources on
debian sid, still no MP3 support.
For information, the patch is attached to this mail.
Thanks.
--
Cyril Davromaniak Lavier
--- ./configure.ac
+++ ./configure.new.ac
@@ -544,7 +544,7 @@ AC_ARG_ENABLE(ffaudio,
if test $enable_ffaudio = yes ; then
PKG_CHECK_MODULES([FFMPEG],
- [libavcodec = 53.40.0 libavformat = 53.5.0 libavutil = 50.42.0],
+ [libavcodec = 52.64.0 libavformat = 52.110.0 libavutil = 50.42.0],
[have_ffaudio=yes], [have_ffaudio=no])
fi
--- ./src/ffaudio/ffaudio-core.c
+++ ./src/ffaudio/ffaudio-core.new.c
@@ -40,6 +40,14 @@
#endif
#include libaudcore/audstrings.h
+#if ! CHECK_LIBAVFORMAT_VERSION (53, 5, 0)
+#define avformat_find_stream_info(i, o) av_find_stream_info (i)
+#endif
+
+#if ! CHECK_LIBAVCODEC_VERSION (53, 8, 0)
+#define avcodec_open2(a, c, o) avcodec_open (a, c)
+#endif
+
static GMutex *ctrl_mutex = NULL;
static GCond *ctrl_cond = NULL;
static gint64 seek_value = -1;
@@ -417,8 +425,11 @@ static gboolean ffaudio_play (InputPlayback * playback, const gchar * filename,
AVCodecContext *c = NULL;
AVStream *s = NULL;
AVPacket pkt = {.data = NULL};
+guint8 *outbuf = NULL, *resbuf = NULL;
gint i, stream_id, errcount;
-gboolean codec_opened = FALSE;
+gint in_sample_size, out_sample_size, chunk_size;
+ReSampleContext *resctx = NULL;
+gboolean codec_opened = FALSE, do_resampling = FALSE;
gint out_fmt;
gboolean seekable;
gboolean error = FALSE;
@@ -454,14 +465,37 @@ static gboolean ffaudio_play (InputPlayback * playback, const gchar * filename,
codec_opened = TRUE;
+/* Determine if audio conversion or resampling is needed */
+in_sample_size = av_get_bytes_per_sample (c-sample_fmt);
+out_sample_size = av_get_bytes_per_sample (SAMPLE_FMT_S16);
+
+chunk_size = out_sample_size * c-channels * (c-sample_rate / 50);
+
switch (c-sample_fmt) {
case SAMPLE_FMT_U8: out_fmt = FMT_U8; break;
case SAMPLE_FMT_S16: out_fmt = FMT_S16_NE; break;
case SAMPLE_FMT_S32: out_fmt = FMT_S32_NE; break;
case SAMPLE_FMT_FLT: out_fmt = FMT_FLOAT; break;
-default:
-fprintf (stderr, ffaudio: Unsupported audio format %d\n, (int) c-sample_fmt);
-goto error_exit;
+default: do_resampling = TRUE; break;
+}
+
+if (do_resampling)
+{
+/* Initialize resampling context */
+out_fmt = FMT_S16_NE;
+
+AUDDBG(resampling needed chn=%d, rate=%d, fmt=%d - chn=%d, rate=%d, fmt=S16NE\n,
+c-channels, c-sample_rate, c-sample_fmt,
+c-channels, c-sample_rate);
+
+resctx = av_audio_resample_init(
+c-channels, c-channels,
+c-sample_rate, c-sample_rate,
+SAMPLE_FMT_S16, c-sample_fmt,
+16, 10, 0, 0.8);
+
+if (resctx == NULL)
+goto error_exit;
}
/* Open audio output */
@@ -475,6 +509,10 @@ static gboolean ffaudio_play (InputPlayback * playback, const gchar * filename,
playback-set_gain_from_playlist(playback);
+/* Allocate output buffer aligned to 16 byte boundary */
+outbuf = av_malloc(AVCODEC_MAX_AUDIO_FRAME_SIZE);
+resbuf = av_malloc(AVCODEC_MAX_AUDIO_FRAME_SIZE);
+
AUDDBG(setting parameters\n);
if (pause)
@@ -547,6 +585,9 @@ static gboolean ffaudio_play (InputPlayback * playback, const gchar * filename,
memcpy(tmp, pkt, sizeof(tmp));
while (tmp.size 0 !stop_flag)
{
+gint len, out_size = AVCODEC_MAX_AUDIO_FRAME_SIZE;
+guint8 *outbuf_p;
+
/* Check for seek request and bail out if we have one */
g_mutex_lock(ctrl_mutex);
if (seek_value != -1)
@@ -564,25 +605,59 @@ static gboolean ffaudio_play (InputPlayback * playback, const gchar * filename,
}
g_mutex_unlock(ctrl_mutex);
-AVFrame * frame
Bug#639374: New upstream release 3.2
On 01/21/2012 11:51 AM, Reinhard Tartler wrote: On Sat, Jan 21, 2012 at 10:40 AM, Cyril Lavier cyril.lav...@davromaniak.eu wrote: On 01/21/2012 10:28 AM, Cyril Lavier wrote: Good morning. So the first tests on wheezy are now done. Audacious runs well, but apparently, it requires a newer version of ffmpeg, so for the moment, he can't decode MP3 files. Runs fine with OGG. On the forum, a developer proposed a patch for using older version of ffmpeg, but it don't seems to work on wheezy (either with sources directly patched or included in the packaging process with quilt). On unstable, I'm not able to make it work with quilt. I'm installing an unstable VM to see if the patch works directly on the sources. That's a fairly large patch. I guess we should wait until upstream has integrated the patch properly in a way that actually works and released a new version. I agree with you, the patch is large and doesn't actually resolve the issue. I will keep an eye on their bugtracker and git repo in case they add compatibility with ffmpeg 0.7 or 0.8. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639374: New upstream release 3.2
On 01/21/2012 12:07 PM, Reinhard Tartler wrote: On Sat, Jan 21, 2012 at 11:59 AM, Cyril Lavier cyril.lav...@davromaniak.eu wrote: That's a fairly large patch. I guess we should wait until upstream has integrated the patch properly in a way that actually works and released a new version. I agree with you, the patch is large and doesn't actually resolve the issue. I will keep an eye on their bugtracker and git repo in case they add compatibility with ffmpeg 0.7 or 0.8. We'd require compatibility with libav 0.8, which is a few weeks later than ffmpeg 0.9(!) I just succeed on enabling the MP3 support for audacious 3.2. So no patch, just needed to add some build-deps (libmpg123-dev and libmp3lame-dev). Just tested on testing, reads MP3 like a charm. So now, I will clean the packaging, maybe there are other things to clean before considering any upload to unstable. Thanks -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639374: New upstream 3.0.1 release
On 01/20/2012 09:24 PM, John Lindgren wrote: retitle 639374 audacious: New upstream release (3.2) unblock 639374 by 590064 forcemerge 639374 653173 thanks Dear Debian maintainers of Audacious, The Audacious packages in Debian are (still) sorely out of date. Please package Audacious 3.2. Waiting for a newer version of libmowgli is no longer necessary as Audacious 3.2 does not depend on the library any more. -- John Lindgren Hi. As I did it for the alpha, I just did it for the beta. It builds fine under unstable and testing, I uploaded them to mentors. - http://mentors.debian.net/package/audacious - http://mentors.debian.net/package/audacious-plugins Later this weekend, I will try to do extended tests on my debian testing laptop, to see if there's no big issue with this version. I hope my work will help the maintaining team updating audacious/audacious-plugins packages. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639374: New upstream 3.0.1 release
On 01/20/2012 11:12 PM, Benjamin Drung wrote: Am Freitag, den 20.01.2012, 22:51 +0100 schrieb Cyril Lavier: On 01/20/2012 09:24 PM, John Lindgren wrote: retitle 639374 audacious: New upstream release (3.2) unblock 639374 by 590064 forcemerge 639374 653173 thanks Dear Debian maintainers of Audacious, The Audacious packages in Debian are (still) sorely out of date. Please package Audacious 3.2. Waiting for a newer version of libmowgli is no longer necessary as Audacious 3.2 does not depend on the library any more. -- John Lindgren Hi. As I did it for the alpha, I just did it for the beta. It builds fine under unstable and testing, I uploaded them to mentors. - http://mentors.debian.net/package/audacious - http://mentors.debian.net/package/audacious-plugins Later this weekend, I will try to do extended tests on my debian testing laptop, to see if there's no big issue with this version. I hope my work will help the maintaining team updating audacious/audacious-plugins packages. Do you want to join the Debian Multimedia team and become an co-maintainer of audacious? The audacious package lacks an maintainer with enough time. Hi Benjamin. Thank you for this proposal which I accept. As I'm a newcomer with co-maintaining official debian packages (I have some personal repositories and I also give some help on nginx official packages), I may need some time to be efficient with this task. But I will do my best for having a audacious/audacious 3.2 in Debian Testing before the freeze next June. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654593: nginx-extras: Please add upload module
Hi Anti. Thanks for submitting this bug. As far as I understand, the demand for the upload module in the bug #618306 was not clearly written, and I think Michael Lustfield didn't see this request (me neither, I had to read the bug 2-3 times to finally understand there was 2 modules requested). So, as it's an external module (and it causes extra work for maintainers to keep the module up to date), could tell us why you think this module need inclusion in the debian packaging of Nginx ? Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654593: nginx-extras: Please add upload module
On Wed, 4 Jan 2012 21:05:08 +0530, Kartik Mistry wrote: On Wed, Jan 4, 2012 at 8:13 PM, Cyril LAVIER cyril.lav...@davromaniak.eu wrote: As far as I understand, the demand for the upload module in the bug #618306 was not clearly written, and I think Michael Lustfield didn't see this request (me neither, I had to read the bug 2-3 times to finally understand there was 2 modules requested). So, as it's an external module (and it causes extra work for maintainers to keep the module up to date), could tell us why you think this module need inclusion in the debian packaging of Nginx ? nginx-extras already has upload progress module :) Yes. I had the same thought at first sight, but there's an other module called upload, which is the one requested here. :) -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653952: FTBFS on Testing
Source: koffice Version: 1:2.3.3-2 Tags : Wheezy Hi. I was building koffice from the source package, and apparently, it failed to build. Here is the log. -- root@grunthos:~/compile# ARCH=amd64 DIST=wheezy pbuilder build koffice_2.3.3-2.dsc I: using fakeroot in build. I: Current time: Sun Jan 1 21:53:06 CET 2012 I: pbuilder-time-stamp: 1325451186 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/wheezy-amd64-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /dev/pts filesystem I: Mounting /var/cache/pbuilder/ccache I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Setting up ccache I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: cdbs, debhelper (= 7), cmake (= 2.6.2), pkg-kde-tools (= 0.9), kdelibs5-dev (= 4:4.4.3), kdepimlibs5-dev (= 4:4.4.3), libkdcraw-dev (= 4:4.4.3), libphonon-dev (= 4:4.6.0really4.4.0), shared-mime-info, libboost-dev, libopenexr-dev, libeigen2-dev (= 2.0~beta6), libqimageblitz-dev, libqca2-dev, libglew-dev, libexiv2-dev, libpng12-dev, liblcms1-dev, libtiff4-dev, libjpeg-dev, libgif-dev, libopenjpeg-dev, libwv2-dev (= 0.4.1), libmysqlclient-dev, libpoppler-dev, libpoppler-qt4-dev, libgsl0-dev, libwpd-dev (= 0.9.1), libwpg-dev (= 0.2.0), libxslt1-dev, libqt4-opengl-dev (= 4.5.0), libqtwebkit-dev, pstoedit, libgmm++-dev, libfftw3-dev, libsqlite3-dev, libpq-dev, libpqxx3-dev, libxbase2.0-dev dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 10955 files and directories currently installed.) Unpacking pbuilder-satisfydepends-dummy (from .../pbuilder-satisfydepends-dummy.deb) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on cdbs; however: Package cdbs is not installed. pbuilder-satisfydepends-dummy depends on debhelper (= 7); however: Package debhelper is not installed. pbuilder-satisfydepends-dummy depends on cmake (= 2.6.2); however: Package cmake is not installed. pbuilder-satisfydepends-dummy depends on pkg-kde-tools (= 0.9); however: Package pkg-kde-tools is not installed. pbuilder-satisfydepends-dummy depends on kdelibs5-dev (= 4:4.4.3); however: Package kdelibs5-dev is not installed. pbuilder-satisfydepends-dummy depends on kdepimlibs5-dev (= 4:4.4.3); however: Package kdepimlibs5-dev is not installed. pbuilder-satisfydepends-dummy depends on libkdcraw-dev (= 4:4.4.3); however: Package libkdcraw-dev is not installed. pbuilder-satisfydepends-dummy depends on libphonon-dev (= 4:4.6.0really4.4.0); however: Package libphonon-dev is not installed. pbuilder-satisfydepends-dummy depends on shared-mime-info; however: Package shared-mime-info is not installed. pbuilder-satisfydepends-dummy depends on libboost-dev; however: Package libboost-dev is not installed. pbuilder-satisfydepends-dummy depends on libopenexr-dev; however: Package libopenexr-dev is not installed. pbuilder-satisfydepends-dummy depends on libeigen2-dev (= 2.0~beta6); however: Package libeigen2-dev is not installed. pbuilder-satisfydepends-dummy depends on libqimageblitz-dev; however: Package libqimageblitz-dev is not installed. pbuilder-satisfydepends-dummy depends on libqca2-dev; however: Package libqca2-dev is not installed. pbuilder-satisfydepends-dummy depends on libglew-dev; however: Package libglew-dev is not installed. pbuilder-satisfydepends-dummy depends on libexiv2-dev; however: Package libexiv2-dev is not installed. pbuilder-satisfydepends-dummy depends on libpng12-dev; however: Package libpng12-dev is not installed. pbuilder-satisfydepends-dummy depends on liblcms1-dev; however: Package liblcms1-dev is not installed. pbuilder-satisfydepends-dummy depends on libtiff4-dev; however: Package libtiff4-dev is not installed. pbuilder-satisfydepends-dummy depends on libjpeg-dev; however: Package libjpeg-dev is not installed. pbuilder-satisfydepends-dummy depends on libgif-dev; however: Package libgif-dev is not installed. pbuilder-satisfydepends-dummy depends on libopenjpeg-dev; however: Package libopenjpeg-dev is not installed. pbuilder-satisfydepends-dummy depends on libwv2-dev (= 0.4.1); however: Package libwv2-dev is not installed.
Bug#653173: audacious: new upstream 3.2-alpha1 (bye bye libmowgli!)
On 12/24/2011 06:38 PM, Cyril Lavier wrote: On 12/24/2011 06:23 PM, Patrice Duroux wrote: Package: audacious Version: 2.4.4-1 Severity: wishlist Hi, This is still an alpha1 version but no more libmowgli dependency (regarding http://audacious-media-player.org/news/7-audacious-3-2-alpha1-released and a compilation try), so may be a good experimental target! Regards, Patrice. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages audacious depends on: ii audacious-plugins2.4.4-1+b2 ii dbus 1.5.8-1 ii dbus-x11 1.5.8-1 ii gtk2-engines-pixbuf 2.24.8-2 ii libaudclient22.4.4-1 ii libaudcore1 2.4.4-1 ii libc62.13-23 ii libdbus-1-3 1.5.8-1 ii libdbus-glib-1-2 0.98-1 ii libgdk-pixbuf2.0-0 2.24.0-2 ii libglib2.0-0 2.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libice6 2:1.0.7-2 ii libmcs1 0.7.2-2 ii libmowgli2 0.7.1-1 ii libsm6 2:1.2.0-2 Versions of packages audacious recommends: ii unzip 6.0-5 audacious suggests no packages. -- no debconf information Hi Patrice. I agree, I think a 3.2-alpha1 could land on experimental as a preparation for the 3.2 stable version to be (we hope) included in Debian Testing before the freeze in July 2012. Thanks. Hi again. Tonight, just for fun, I tried to make packages for audacious and audacious-plugins. I sent them to mentors : - http://mentors.debian.net/package/audacious - http://mentors.debian.net/package/audacious-plugins I will try to test them tomorrow on a Debian Sid machine. By the way, if somebody wants to try them : http://devpkg.davromaniak.eu/ (add deb http://devpkg.davromaniak.eu/ sid main to your sources.list). As it's a first try at the updating, and as audacious 3.2 is still in alpha, so be carefull with these packages. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653160: nginx: missing slash in alias /usr/share/doc
On 12/24/2011 02:47 PM, Dmitry Borodaenko wrote:
Package: nginx
Version: 1.1.11-1
Severity: normal
Current default site configuration causes direct access to documents
under /usr/share/doc to produce 404 errors like this:
2011/12/24 16:36:08 [error] 30139#0: *1
/usr/share/docgit-buildpackage/manual-html/index.html is not found (2: No such
file or directory), client: 127.0.0.1, server: localhost, request: GET /doc/gi
t-buildpackage/manual-html/ HTTP/1.1, host: localhost
I believe this is caused by changes done in 1.1.8-1 (a slash was added
to location, but not to the alias), adding a slash to the end of the
alias makes the problem go away:
location /doc/ {
alias /usr/share/doc/;
Thanks,
Dmitry Borodaenko
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (70, 'testing'), (50, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nginx depends on:
ii nginx-full 1.1.11-1
nginx recommends no packages.
nginx suggests no packages.
-- no debconf information
Hi Dmitry.
Thank you for submitting this bug, and you are right this bug appeared
in the 1.1.8-1 when the alias for /doc was changed.
I made the correction on the SVN.
I think this can wait until the next upstream version to be resolved in
the actual package, no need for a 1.1.11-2 package version.
Thanks.
--
Cyril Davromaniak Lavier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653173: audacious: new upstream 3.2-alpha1 (bye bye libmowgli!)
On 12/24/2011 06:23 PM, Patrice Duroux wrote: Package: audacious Version: 2.4.4-1 Severity: wishlist Hi, This is still an alpha1 version but no more libmowgli dependency (regarding http://audacious-media-player.org/news/7-audacious-3-2-alpha1-released and a compilation try), so may be a good experimental target! Regards, Patrice. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages audacious depends on: ii audacious-plugins2.4.4-1+b2 ii dbus 1.5.8-1 ii dbus-x11 1.5.8-1 ii gtk2-engines-pixbuf 2.24.8-2 ii libaudclient22.4.4-1 ii libaudcore1 2.4.4-1 ii libc62.13-23 ii libdbus-1-3 1.5.8-1 ii libdbus-glib-1-2 0.98-1 ii libgdk-pixbuf2.0-0 2.24.0-2 ii libglib2.0-0 2.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libice6 2:1.0.7-2 ii libmcs1 0.7.2-2 ii libmowgli2 0.7.1-1 ii libsm6 2:1.2.0-2 Versions of packages audacious recommends: ii unzip 6.0-5 audacious suggests no packages. -- no debconf information Hi Patrice. I agree, I think a 3.2-alpha1 could land on experimental as a preparation for the 3.2 stable version to be (we hope) included in Debian Testing before the freeze in July 2012. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652108: Why not adding a a2ensite/a2dissite like script for Nginx ?
Package: nginx Hi. I just discovered there a github project with a a2ensite/a2dissite like script for Nginx. As it lacked some functionalities (like displaying a list of sites to enable/disable when no site in given from the command line), I decided to fork it :https://github.com/davromaniak/nginx_ensite The script is working, but I think it needs more work to make it reliable. So I would like to know what you think about the possibility of adding such a script in the nginx packages (maybe nginx-common) ? If needed, I can go on, and take responsibilities on maintaining this script under debian, or I can ask the original author if he's interested in this. So I open this bug to have your opinions about this, and see if it's actually useful. Thanks. -- Cyril Davromaniak Lavier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
