Re: Bug#387396: subversion: depend libapr0 = 2.0.55-4.2 (libdb-4.4 problem)

2006-09-15 Thread Peter Samuelson

[Karl Chen]
 $ svnadmin --version
 svnadmin: Bad database version: compiled with 4.4.20, running against 4.3.29

This is a symptom of the ABI change between libapr0 2.0.55-4.1 and
2.0.55-4.2, since the latter uses Berkeley DB 4.4.  Can you please do
the following to libapr0:

- Conflicts: libsvn0 ( 1.4.0)
- libaprutil-0 0 libapr0 (= 2.0.55-4.2) in the shlibs file

These two things address the incompatibility from both directions.  The
shlibs change would have prevented bug #387396.

Thanks,
Peter


signature.asc
Description: Digital signature


Re: Bug#387396: subversion: depend libapr0 = 2.0.55-4.2 (libdb-4.4 problem)

2006-09-15 Thread Adam Conrad
Peter Samuelson wrote:
 
 - Conflicts: libsvn0 ( 1.4.0)
 - libaprutil-0 0 libapr0 (= 2.0.55-4.2) in the shlibs file
 
 These two things address the incompatibility from both directions.  The
 shlibs change would have prevented bug #387396.

Probably not worth having the conflict, since we're pretty sure that SVN
will be rebuilt between now and release, but the missing shlibs bump was
definitely an oops.

... Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#387396: subversion: depend libapr0 = 2.0.55-4.2 (libdb-4.4 problem)

2006-09-15 Thread Peter Samuelson

[Adam Conrad]
  - Conflicts: libsvn0 ( 1.4.0)
  - libaprutil-0 0 libapr0 (= 2.0.55-4.2) in the shlibs file
  
  These two things address the incompatibility from both directions.  The
  shlibs change would have prevented bug #387396.
 
 Probably not worth having the conflict, since we're pretty sure that SVN
 will be rebuilt between now and release, but the missing shlibs bump was
 definitely an oops.

I think the conflict is worth it for people who upgrade libapr0 but do
not upgrade subversion from sarge.


signature.asc
Description: Digital signature


Bug#387625: please split up the configuration files

2006-09-15 Thread Wessel Dankers
Package: apache2-common
Version: 2.2.3-1~exp.r170
Severity: wishlist
Tags: patch

Hi,

I noticed that a limited effort has been made to split up the apache2
config, resulting in a limping modular/monolithic configuration system.

As a systems administrator I find myself changing a few common things
in the config whenever I set up an apache2 server. When the number of
apache2 installations is sufficiently large, it becomes *extremely*
useful to have the common changes in one file, and per-host changes in
a different file. A modular configuration system would help a lot with
such an approach.

It makes it easier for an administrator to decide which parts to leave
at defaults and which parts to customize.

A modular configuration system also helps when upgrading: unchanged
configuration files can be simply replaced. A single large config file
is unlikely to remain unmodified.

I made a straightforward split of the configuration files of both
version 2.0 and version 2.2 (from experimental), which you may find at:

http://www.fruit.je/download/apache2-modular-configs.tar.gz

The splits are fairly basic, no statements were added or removed and
almost all stanzas are left intact (the charsets stuff was mixed with
some random filetype statements in the configuration file, had to
untangle that).

Obviously I'll be more than happy to adjust this thing if you have
any comments.

The included README replicated here for convenience:

Notes:

- ports.conf was moved to conf.d/

- conf.d/charset was renamed to conf.d/charset.conf

- All config files must be named *.conf; this to prevent
  problems when dpkg creates a foo.conf.dpkg-old file.
  The postinst script might want to offer to rename existing
  files.


-- System Information:
Debian Release: unstable/experimental
  APT prefers experimental
  APT policy: (500, 'experimental'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8-p4-uvt
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)

Versions of packages apache2-common depends on:
ii  apache2-utils   2.2.3-1~exp.r170 utility programs for webservers
ii  libmagic1   4.17-3   File type determination library us
ii  lsb-base3.1-15   Linux Standard Base 3.1 init scrip
ii  mime-support3.37-1   MIME files 'mime.types'  'mailcap
ii  net-tools   1.60-17  The NET-3 networking toolkit

apache2-common recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



apache override disparity

2006-09-15 Thread Debian Installer
There are disparities between your recently accepted upload and the
override file for the following file(s):

libapache-mod-perl_1.29.0.3-6sarge3_i386.deb: package says section is web, 
override says perl.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please reply to this mail and explain why.

[NB: this is an automatically generated mail; if you replied to one
like it before and have not received a response yet, please ignore
this mail.  Your reply needs to be processed by a human and will be in
due course, but until then the installer will send these automated
mails; sorry.]

--
Debian distribution maintenance software

(This message was generated automatically; if you believe that there
is a problem with it please contact the archive administrators by
mailing [EMAIL PROTECTED])


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]