Bug#664867: libapr1: after upgrade to libapr1 1.4.6-1, properties in svn dump are in a random order
Package: libapr1 Version: 1.4.6-1 Severity: important After the upgrade to libapr1 1.4.6-1, the properties in the svn dump output are now in a random order. I don't think their order is specified, but IMHO, they should be in a consistent order to allow conventional tools like diff, MD5 checking on a dump, rsync[*] and so on to work nicely. [*] rsync will still work, but obviously less efficiently. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libapr1 depends on: ii libc6 2.13-27 ii libuuid1 2.20.1-4 libapr1 recommends no packages. libapr1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120321141450.ga8...@xvii.vinc17.org
Bug#664761: apache2/conf.d migration: what should webapp packagers do?
On Wednesday 21 March 2012, Paul Wise wrote: On Wed, Mar 21, 2012 at 1:18 AM, Jonathan Nieder wrote: Upgrading apache2 to the version in experimental breaks my local gitweb installation. Gitweb ships the following snippet in /etc/apache2/conf.d/gitweb: Alias /gitweb /usr/share/gitweb That looks like a highly inappropriate thing for gitweb to be doing. There is no way for the package to know what URL and filesystem paths (for data/config) the sysadmin wants gitweb to be installed at. The package needs to ask the sysadmin if they want to setup any instances, prompt them for the relevant data and run any scripts needed to create those instances. I think its not that bad. For a significant part of the users, /gitweb as urlpath is ok. And the apache config snippet is a conf file, so changing the URL path is very easy. What is bad is that it is visible in all vhosts, but that's something we intend to make configurable in the apache2 2.4 packages. About the repository paths, those are configured in /etc/gitweb.conf. I don't think that a web app as simple as gitweb needs to ask things during installation. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203212203.13735...@sfritsch.de
Re: Bits from the Apache Maintainers / Upcoming apache2 2.4 transition
On Thu, Mar 22, 2012 at 01:05:16AM +0100, Stefan Fritsch wrote: Beware: The ITK MPM is not included for the time being. This may or may not change until the freeze. Just to make sure; you are aware that there is a 2.4 patch for mpm-itk out, right? Having it in experimental would be a great way to increase testing coverage. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120322003713.ga19...@uio.no
