subversion-tools: Moves /usr/lib/subversion to /u/share/, because all files are sharable

[Debian Bug Importer]

Automatically imported from Debian bug report #330824 http://bugs.debian.org/330824

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #330824 http://bugs.debian.org/330824

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 29 Sep 2005 23:26:26 +0200
From: =?iso-8859-1?Q?J=F6rg?= Sommer <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: subversion-tools: Moves /usr/lib/subversion to /u/share/, because all files are sharable

Package: subversion-tools
Version: 1.2.3a-1
Severity: serious
Justification: Policy 8.1

Hi,

all files in /usr/lib/subversion are plain text files or perl/python
scripts. The FHS forces to move such files in a directory under
/usr/share/, because they can the shared among different architectures.

$ find /usr/lib/subversion/ -type f |xargs file
hook-scripts/README: ASCII English text
hook-scripts/commit-access-control.cfg.example: ASCII English text
hook-scripts/commit-access-control.pl: a perl script text execut=
able
hook-scripts/commit-email.pl: a perl script text execut=
able
hook-scripts/commit-email.rb: a ruby script text execut=
able
hook-scripts/mailer/mailer.conf.example: ASCII English text
hook-scripts/mailer/mailer.py: a /usr/bin/python2.3 scri=
pt text executable
hook-scripts/mailer/tests/mailer-init.sh: Bourne shell script text =
executable
hook-scripts/mailer/tests/mailer-t1.output: ASCII text
hook-scripts/mailer/tests/mailer-t1.sh: Bourne shell script text =
executable
hook-scripts/mailer/tests/mailer-tweak.py: a /usr/bin/python2.3 scri=
pt text executable
hook-scripts/propchange-email.pl: a perl script text execut=
able
hook-scripts/svnperms.conf.example: ASCII English text
hook-scripts/svnperms.py: a /usr/bin/python2.3 scri=
pt text executable
hook-scripts/verify-po.py: a /usr/bin/python2.3 scri=
pt text executable
hot-backup.py: a /usr/bin/python2.3 scri=
pt text executable

BTW: Maybe you can move the example files to /u/s/d/s-tools/example/

Bye, J=F6rg.

-- System Information:
Debian Release: unstable/experimental
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.13.1
Locale: LANG=3Dde_DE, LC_CTYPE=3Dde_DE (charmap=3DISO-8859-1)

Versions of packages subversion-tools depends on:
ii exim4-daemon-light [mail-tran 4.52-2 lightweight exim MTA (v4) da=
emon
ii libconfig-inifiles-perl 2.38-3 Read .ini-style configuratio=
n file
ii liburi-perl 1.35-1 Manipulates and accesses URI=
 strin
ii perl 5.8.7-5 Larry Wall's Practical Extra=
ction=20
ii python2.3 2.3.5-8 An interactive high-level ob=
ject-o
ii python2.3-subversion 1.2.3a-1 python modules for interfaci=
ng wit
ii rcs 5.7-16 The GNU Revision Control Sys=
tem
ii subversion 1.2.3a-1 advanced version control sys=
tem (a

subversion-tools recommends no packages.

-- no debconf information

[Fabio Massimo Di Nitto (fabbione)]

we will get this one in dapper..

[Peters-guest (peters-guest)]

tags 330824 pending
thanks

Author: peters-guest
Date: 2005-10-12 14:16:43 +0000 (Wed, 12 Oct 2005)
New Revision: 398

Added:
   trunk/debian/subversion-tools.postinst
   trunk/debian/subversion-tools.postrm
Modified:
   trunk/debian/changelog
   trunk/debian/rules
   trunk/debian/subversion-tools.dirs
   trunk/debian/subversion-tools.install
Log:
Move /usr/lib/subversion to /usr/share/subversion for FHS reasons.

- leave a symlink /usr/lib/subversion -> ../share/subversion,
  managed by subversion-tools.{postinst,postrm}

- move hot-backup.py to /usr/share/doc/subversion/examples/
  Actually hot-backup.py can probably go away entirely, as
  'svnadmin hotcopy' apparently can do the same thing now.

A bit more testing is needed to see whether subversion-tools.postinst
in particular can be made to Do The Wrong Thing.

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2005-10-12 13:28:39 UTC (rev 397)
+++ trunk/debian/changelog 2005-10-12 14:16:43 UTC (rev 398)
@@ -29,6 +29,10 @@
     "architectures to run full testsuite on".
   * debian/control: relax all versioned build-deps; all the versions are
     satisfied in sarge (and most of them in woody).
+ * debian/rules, debian/subversion-tools.{postinst,postrm,install}:
+ - move /usr/lib/subversion to /usr/share/subversion (Closes: #330824)
+ - move hot-backup.py to /usr/share/doc/subversion/examples
+ - create compat symlink /usr/lib/subversion

  -- Guilherme de S. Pastore <email address hidden> Sun, 11 Sep 2005 19:03:54 -0300

Modified: trunk/debian/rules
===================================================================
--- trunk/debian/rules 2005-10-12 13:28:39 UTC (rev 397)
+++ trunk/debian/rules 2005-10-12 14:16:43 UTC (rev 398)
@@ -259,18 +259,19 @@
  install contrib/client-side/svn_load_dirs.README \
   debian/subversion-tools/usr/share/doc/subversion-tools/ \

- sed -i -e 's:^#!/usr/bin/env pyth.*:#!/usr/bin/python$(PYTHON_VER):' \
- debian/subversion-tools/usr/lib/subversion/hot-backup.py
+ sed -e 's:^#!/usr/bin/env pyth.*:#!/usr/bin/python$(PYTHON_VER):' \
+ < BUILD/tools/backup/hot-backup.py \
+ > debian/subversion-tools/usr/share/doc/subversion/examples/hot-backup.py

- rm debian/subversion-tools/usr/lib/subversion/hook-scripts/*.in
+ rm debian/subversion-tools/usr/share/subversion/hook-scripts/*.in
+ rm -r debian/subversion-tools/usr/share/subversion/hook-scripts/mailer/tests

  # Fix some scripts not to use #!/usr/bin/env.
- dest=debian/subversion-tools/usr/lib/subversion/hook-scripts; \
+ dest=debian/subversion-tools/usr/share/subversion/hook-scripts; \
  for file in commit-email.pl \
              propchange-email.pl \
       commit-access-control.pl \
              mailer/mailer.py \
- mailer/tests/mailer-tweak.py \
              verify-po.py \
              svnperms.py ; do \
    sed -i \

Modified: trunk/debian/subversion-tools.dirs
===================================================================
--- trunk/debian/subversion-tools.dirs 2005-10-12 13:28:39 UTC (rev 397)
+++ trunk/debian/subversion-tools.dirs 2005-10-12 14:16:43 UTC (rev 398)
@@ -1,2 +1,3 @...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 12 Oct 2005 14:16:43 +0000
From: <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: subversion Debian ci: r398 - trunk/debian

tags 330824 pending
thanks

Author: peters-guest
Date: 2005-10-12 14:16:43 +0000 (Wed, 12 Oct 2005)
New Revision: 398

Added:
   trunk/debian/subversion-tools.postinst
   trunk/debian/subversion-tools.postrm
Modified:
   trunk/debian/changelog
   trunk/debian/rules
   trunk/debian/subversion-tools.dirs
   trunk/debian/subversion-tools.install
Log:
Move /usr/lib/subversion to /usr/share/subversion for FHS reasons.

- leave a symlink /usr/lib/subversion -> ../share/subversion,
  managed by subversion-tools.{postinst,postrm}

- move hot-backup.py to /usr/share/doc/subversion/examples/
  Actually hot-backup.py can probably go away entirely, as
  'svnadmin hotcopy' apparently can do the same thing now.

A bit more testing is needed to see whether subversion-tools.postinst
in particular can be made to Do The Wrong Thing.

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2005-10-12 13:28:39 UTC (rev 397)
+++ trunk/debian/changelog 2005-10-12 14:16:43 UTC (rev 398)
@@ -29,6 +29,10 @@
     "architectures to run full testsuite on".
   * debian/control: relax all versioned build-deps; all the versions are
     satisfied in sarge (and most of them in woody).
+ * debian/rules, debian/subversion-tools.{postinst,postrm,install}:
+ - move /usr/lib/subversion to /usr/share/subversion (Closes: #330824)
+ - move hot-backup.py to /usr/share/doc/subversion/examples
+ - create compat symlink /usr/lib/subversion

  -- Guilherme de S. Pastore <email address hidden> Sun, 11 Sep 2005 19:03:54 -0300

Modified: trunk/debian/rules
===================================================================
--- trunk/debian/rules 2005-10-12 13:28:39 UTC (rev 397)
+++ trunk/debian/rules 2005-10-12 14:16:43 UTC (rev 398)
@@ -259,18 +259,19 @@
  install contrib/client-side/svn_load_dirs.README \
   debian/subversion-tools/usr/share/doc/subversion-tools/ \

- sed -i -e 's:^#!/usr/bin/env pyth.*:#!/usr/bin/python$(PYTHON_VER):' \
- debian/subversion-tools/usr/lib/subversion/hot-backup.py
+ sed -e 's:^#!/usr/bin/env pyth.*:#!/usr/bin/python$(PYTHON_VER):' \
+ < BUILD/tools/backup/hot-backup.py \
+ > debian/subversion-tools/usr/share/doc/subversion/examples/hot-backup.py

- rm debian/subversion-tools/usr/lib/subversion/hook-scripts/*.in
+ rm debian/subversion-tools/usr/share/subversion/hook-scripts/*.in
+ rm -r debian/subversion-tools/usr/share/subversion/hook-scripts/mailer/tests

  # Fix some scripts not to use #!/usr/bin/env.
- dest=debian/subversion-tools/usr/lib/subversion/hook-scripts; \
+ dest=debian/subversion-tools/usr/share/subversion/hook-scripts; \
  for file in commit-email.pl \
              propchange-email.pl \
       commit-access-control.pl \
              mailer/mailer.py \
- mailer/tests/mailer-tweak.py \
              verify-po.py \
              svnperms.py ; do \
    sed -i \

Modified: trunk/debia...

[Peter Samuelson (peter-p12n)]

Source: subversion
Source-Version: 1.2.3dfsg1-1

We believe that the bug you reported is fixed in the latest version of
subversion, which is due to be installed in the Debian FTP archive:

libapache2-svn_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libapache2-svn_1.2.3dfsg1-1_i386.deb
libsvn-core-perl_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn-core-perl_1.2.3dfsg1-1_i386.deb
libsvn-javahl_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn-javahl_1.2.3dfsg1-1_i386.deb
libsvn0-dev_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn0-dev_1.2.3dfsg1-1_i386.deb
libsvn0_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn0_1.2.3dfsg1-1_i386.deb
python2.3-subversion_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/python2.3-subversion_1.2.3dfsg1-1_i386.deb
subversion-tools_1.2.3dfsg1-1_all.deb
  to pool/main/s/subversion/subversion-tools_1.2.3dfsg1-1_all.deb
subversion_1.2.3dfsg1-1.diff.gz
  to pool/main/s/subversion/subversion_1.2.3dfsg1-1.diff.gz
subversion_1.2.3dfsg1-1.dsc
  to pool/main/s/subversion/subversion_1.2.3dfsg1-1.dsc
subversion_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/subversion_1.2.3dfsg1-1_i386.deb
subversion_1.2.3dfsg1.orig.tar.gz
  to pool/main/s/subversion/subversion_1.2.3dfsg1.orig.tar.gz

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Samuelson <email address hidden> (supplier of updated subversion package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 18 Oct 2005 03:03:27 -0500
Source: subversion
Binary: libsvn-core-perl libapache2-svn libsvn0 libsvn-javahl python2.3-subversion subversion-tools libsvn0-dev subversion
Architecture: source i386 all
Version: 1.2.3dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Guilherme de S. Pastore <email address hidden>
Changed-By: Peter Samuelson <email address hidden>
Description:
 libapache2-svn - apache modules for Subversion (aka. svn)
 libsvn-core-perl - perl bindings for Subversion (aka. svn)
 libsvn-javahl - java bindings for Subversion (aka. svn)
 libsvn0 - shared libraries used by Subversion (aka. svn)
 libsvn0-dev - development files for Subversion (aka. svn) libraries
 python2.3-subversion - python modules for interfacing with Subversion (aka. svn)
 subversion - advanced version control system (aka. svn)
 subversion-tools - assorted tools related to Subversion (aka. svn)
Closes: 327789 329184 330824
Changes:
 subversion (1.2.3dfsg1-1) unstable; urgency=low
 .
   [ Guilherme de S. Pastore ]
   * debian/control:
     - changed section of libsvn-core-perl to perl
     - changed section of libsvn-javahl to devel
     - bump to Standards-Version 3.6.2.1 with no changes
   * debian/rules:
     - minor cleanups
     - removed remnants of control auto...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 18 Oct 2005 17:32:06 -0700
From: Peter Samuelson <email address hidden>
To: <email address hidden>
Subject: Bug#330824: fixed in subversion 1.2.3dfsg1-1

Source: subversion
Source-Version: 1.2.3dfsg1-1

We believe that the bug you reported is fixed in the latest version of
subversion, which is due to be installed in the Debian FTP archive:

libapache2-svn_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libapache2-svn_1.2.3dfsg1-1_i386.deb
libsvn-core-perl_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn-core-perl_1.2.3dfsg1-1_i386.deb
libsvn-javahl_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn-javahl_1.2.3dfsg1-1_i386.deb
libsvn0-dev_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn0-dev_1.2.3dfsg1-1_i386.deb
libsvn0_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/libsvn0_1.2.3dfsg1-1_i386.deb
python2.3-subversion_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/python2.3-subversion_1.2.3dfsg1-1_i386.deb
subversion-tools_1.2.3dfsg1-1_all.deb
  to pool/main/s/subversion/subversion-tools_1.2.3dfsg1-1_all.deb
subversion_1.2.3dfsg1-1.diff.gz
  to pool/main/s/subversion/subversion_1.2.3dfsg1-1.diff.gz
subversion_1.2.3dfsg1-1.dsc
  to pool/main/s/subversion/subversion_1.2.3dfsg1-1.dsc
subversion_1.2.3dfsg1-1_i386.deb
  to pool/main/s/subversion/subversion_1.2.3dfsg1-1_i386.deb
subversion_1.2.3dfsg1.orig.tar.gz
  to pool/main/s/subversion/subversion_1.2.3dfsg1.orig.tar.gz

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Samuelson <email address hidden> (supplier of updated subversion package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 18 Oct 2005 03:03:27 -0500
Source: subversion
Binary: libsvn-core-perl libapache2-svn libsvn0 libsvn-javahl python2.3-subversion subversion-tools libsvn0-dev subversion
Architecture: source i386 all
Version: 1.2.3dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Guilherme de S. Pastore <email address hidden>
Changed-By: Peter Samuelson <email address hidden>
Description:
 libapache2-svn - apache modules for Subversion (aka. svn)
 libsvn-core-perl - perl bindings for Subversion (aka. svn)
 libsvn-javahl - java bindings for Subversion (aka. svn)
 libsvn0 - shared libraries used by Subversion (aka. svn)
 libsvn0-dev - development files for Subversion (aka. svn) libraries
 python2.3-subversion - python modules for interfacing with Subversion (aka. svn)
 subversion - advanced version control system (aka. svn)
 subversion-tools - assorted tools related to Subversion (aka. svn)
Closes: 327789 329184 330824
Changes:
 subversion (1.2.3dfsg1-1) unstable; urgency=low
 .
   [ Guilherme de S. Pastore ]
   * debian/control:
     - changed section ...

[Micah Anderson (micah-debian)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

reopen 330824
thanks

The original bug suggests that you move the plain-text files (including
python and perl scripts) from /usr/lib/subversion to
/usr/share/subversion. This you accomplished in 1.2.3dfsg1-1.

However, the other suggestion that was put forth in the bug report was:

"BTW: Maybe you can move the example files to /u/s/d/s-tools/example/"

This did not happen with any of the example files with 1.2.3dfsg1-1,
they all still appear in /usr/share/subversion/hook-scripts. Instead,
what did happen was that hot-backup.py, a perfectly good script, was
moved to /usr/share/doc/subversion-tools/examples.

It seems to me that the hot-backup.py script should be restored to its
original useful place (as a script that some backup programs use), and
the example files that are in /usr/share/subversion/hook-scripts be
actually moved to /usr/share/doc/subversion-tools/examples.

Thanks!
micah
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDbEbR9n4qXRzy1ioRAgWIAKCjDMoHBNCze8vCxwIkChlSnEPkxQCggXlm
6NzG/GGmO0i/ooytp/Mok9M=
=1NWB
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 05 Nov 2005 00:44:49 -0500
From: micah <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: I dont believe this bug was acted on properly

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

reopen 330824
thanks

The original bug suggests that you move the plain-text files (including
python and perl scripts) from /usr/lib/subversion to
/usr/share/subversion. This you accomplished in 1.2.3dfsg1-1.

However, the other suggestion that was put forth in the bug report was:

"BTW: Maybe you can move the example files to /u/s/d/s-tools/example/"

This did not happen with any of the example files with 1.2.3dfsg1-1,
they all still appear in /usr/share/subversion/hook-scripts. Instead,
what did happen was that hot-backup.py, a perfectly good script, was
moved to /usr/share/doc/subversion-tools/examples.

It seems to me that the hot-backup.py script should be restored to its
original useful place (as a script that some backup programs use), and
the example files that are in /usr/share/subversion/hook-scripts be
actually moved to /usr/share/doc/subversion-tools/examples.

Thanks!
micah
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDbEbR9n4qXRzy1ioRAgWIAKCjDMoHBNCze8vCxwIkChlSnEPkxQCggXlm
6NzG/GGmO0i/ooytp/Mok9M=
=1NWB
-----END PGP SIGNATURE-----

[Peter Samuelson (peter-p12n)]

severity 330824 wishlist
retitle 330824 disagreement about example scripts
thanks

[micah]
> "BTW: Maybe you can move the example files to /u/s/d/s-tools/example/"

Thanks so much for not changing the severity there. I guess you
believe this is release-critical. I require a bit of convincing on
that score. I almost tagged this one wontfix just now, but I'll give
you a chance to rebut first.

> This did not happen with any of the example files with 1.2.3dfsg1-1,
> they all still appear in /usr/share/subversion/hook-scripts.

Many of the files there are usable in situ. Moved to the examples
directory, they wouldn't be (thanks to Policy about gzip). I'm not
interested in breaking people's repositories arbitrarily, which is what
would happen if people *are* using these things in situ. If I break
someone's repository with a svn upgrade I want to at least have a good
reason.

Splitting files that could be moved to the examples directory from the
ones that should be left in /usr/share/subversion would be a pointless
exercise in making files harder to find, in order to prove something
about filesystem organization. To use the script files that come with
"example config" files requires knowing where to find the latter.

> It seems to me that the hot-backup.py script should be restored to
> its original useful place (as a script that some backup programs
> use)

Did you read NEWS.Debian.gz?

  The other script affected is /usr/lib/subversion/hot-backup.py, which
  has now moved into /usr/share/doc/subversion/examples. It was never
  a supported executable (or it would live in /usr/bin). It is also no
  longer needed, because "svnadmin hotcopy" now includes the same
  functionality. Please use "svnadmin hotcopy" instead.

Peter

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 5 Nov 2005 03:10:27 -0600
From: Peter Samuelson <email address hidden>
To: micah <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#330824: I dont believe this bug was acted on properly

--H5pgEA8DvTwLpheO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

severity 330824 wishlist
retitle 330824 disagreement about example scripts
thanks

[micah]
> "BTW: Maybe you can move the example files to /u/s/d/s-tools/example/"

Thanks so much for not changing the severity there. I guess you
believe this is release-critical. I require a bit of convincing on
that score. I almost tagged this one wontfix just now, but I'll give
you a chance to rebut first.

> This did not happen with any of the example files with 1.2.3dfsg1-1,
> they all still appear in /usr/share/subversion/hook-scripts.

Many of the files there are usable in situ. Moved to the examples
directory, they wouldn't be (thanks to Policy about gzip). I'm not
interested in breaking people's repositories arbitrarily, which is what
would happen if people *are* using these things in situ. If I break
someone's repository with a svn upgrade I want to at least have a good
reason.

Splitting files that could be moved to the examples directory from the
ones that should be left in /usr/share/subversion would be a pointless
exercise in making files harder to find, in order to prove something
about filesystem organization. To use the script files that come with
"example config" files requires knowing where to find the latter.

> It seems to me that the hot-backup.py script should be restored to
> its original useful place (as a script that some backup programs
> use)

Did you read NEWS.Debian.gz?

  The other script affected is /usr/lib/subversion/hot-backup.py, which
  has now moved into /usr/share/doc/subversion/examples. It was never
  a supported executable (or it would live in /usr/bin). It is also no
  longer needed, because "svnadmin hotcopy" now includes the same
  functionality. Please use "svnadmin hotcopy" instead.

Peter

--H5pgEA8DvTwLpheO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDbHcDXk7sIRPQRh0RAqwUAJ91K13W4B1J43diHjHq4S2UAlujQACfVvOz
N2TjEe4GeiE9eFNAwWxVgC0=
=FzLL
-----END PGP SIGNATURE-----

--H5pgEA8DvTwLpheO--

[Micah Anderson (micah-debian)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Samuelson wrote:
> severity 330824 wishlist
> retitle 330824 disagreement about example scripts
> thanks
>
> [micah]
>
>>"BTW: Maybe you can move the example files to /u/s/d/s-tools/example/"
>
>
> Thanks so much for not changing the severity there.

Back-handed passive-agressive statements are not productive, but instead
provoke angry responses, but lets not get angry. I believe that we can
discuss this in a rational way, discussing the technical details, rather
than resorting to flaming. Please believe me when I say that I
re-opened this bug not to spite you or to flame you, but because it
seemed as if it wasn't actually fixed. I'm sorry if my message came
across in any other way, it was not intended to be so.

> I guess you believe this is release-critical. I require a bit of
> convincing on that score. I almost tagged this one wontfix just now,
> but I'll give you a chance to rebut first.

If you will allow me to rephrase this in a different way, "Why did you
not change the severity of the bug when you reopened it? Do you think
that it is still release-critical?"

Actually the reason why I did not change the severity of the bug was
because I did not even look at it from the beginning, I assumed the
original bug was set to a severity level that made sense, and because I
felt as if the bug had not been acted on that the original severity
level probably still applied. Had I noticed that it was set to such a
high severity level, then I probably would have noted that in my
response, suggesting that it probably should be lowered. However, I am
not a huge fan of changing the severity of someone else's bug, on
someone else's package, I prefer to instead suggest that it be changed,
rather than barge in and do it myself.

My guess is that the release-critical nature of the original severity of
the bug was due to the FHS violation, which was actually fixed. So I
agree that the severity should be lowered, and I apologize for
overlooking this.

>>This did not happen with any of the example files with 1.2.3dfsg1-1,
>>they all still appear in /usr/share/subversion/hook-scripts.
>
>
> Many of the files there are usable in situ. Moved to the examples
> directory, they wouldn't be (thanks to Policy about gzip). I'm not
> interested in breaking people's repositories arbitrarily, which is what
> would happen if people *are* using these things in situ. If I break
> someone's repository with a svn upgrade I want to at least have a good
> reason.

This makes a lot of sense. I was not aware that the example files are
actually usable in situ. I only saw that the bug was closed and the
example files were not moved as the bug suggested. This was an
indication to me that the bug report had not been acted on properly. If
you had sent a message to the report clarifying this, it would have
helped and I would not have thought that the issue had been overlooked.

>>It seems to me that the hot-backup.py script should be restored to
>>its original useful place (as a script that some backup programs
>>use)
>
>
> Did you read NEWS.Debian.gz?
>
> The other script affected is /usr/lib/subversion/hot-bac...

[Micah Anderson (micah-debian)]

tags 330824 + fixed

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 05 Nov 2005 12:12:25 -0500
From: micah <email address hidden>
To: Peter Samuelson <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#330824: I dont believe this bug was acted on properly

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Samuelson wrote:
> severity 330824 wishlist
> retitle 330824 disagreement about example scripts
> thanks
>
> [micah]
>
>>"BTW: Maybe you can move the example files to /u/s/d/s-tools/example/"
>
>
> Thanks so much for not changing the severity there.

Back-handed passive-agressive statements are not productive, but instead
provoke angry responses, but lets not get angry. I believe that we can
discuss this in a rational way, discussing the technical details, rather
than resorting to flaming. Please believe me when I say that I
re-opened this bug not to spite you or to flame you, but because it
seemed as if it wasn't actually fixed. I'm sorry if my message came
across in any other way, it was not intended to be so.

> I guess you believe this is release-critical. I require a bit of
> convincing on that score. I almost tagged this one wontfix just now,
> but I'll give you a chance to rebut first.

If you will allow me to rephrase this in a different way, "Why did you
not change the severity of the bug when you reopened it? Do you think
that it is still release-critical?"

Actually the reason why I did not change the severity of the bug was
because I did not even look at it from the beginning, I assumed the
original bug was set to a severity level that made sense, and because I
felt as if the bug had not been acted on that the original severity
level probably still applied. Had I noticed that it was set to such a
high severity level, then I probably would have noted that in my
response, suggesting that it probably should be lowered. However, I am
not a huge fan of changing the severity of someone else's bug, on
someone else's package, I prefer to instead suggest that it be changed,
rather than barge in and do it myself.

My guess is that the release-critical nature of the original severity of
the bug was due to the FHS violation, which was actually fixed. So I
agree that the severity should be lowered, and I apologize for
overlooking this.

>>This did not happen with any of the example files with 1.2.3dfsg1-1,
>>they all still appear in /usr/share/subversion/hook-scripts.
>
>
> Many of the files there are usable in situ. Moved to the examples
> directory, they wouldn't be (thanks to Policy about gzip). I'm not
> interested in breaking people's repositories arbitrarily, which is what
> would happen if people *are* using these things in situ. If I break
> someone's repository with a svn upgrade I want to at least have a good
> reason.

This makes a lot of sense. I was not aware that the example files are
actually usable in situ. I only saw that the bug was closed and the
example files were not moved as the bug suggested. This was an
indication to me that the bug report had not been acted on properly. If
you had sent a message to the report clarifying this, it would have
helped and I would not have thought that...

[Debian Bug Importer (debzilla)]

Message-Id: <20051105173348.C1BB04D8F8@pond>
Date: Sat, 5 Nov 2005 12:33:48 -0500 (EST)
From: <email address hidden> (micah)
To: <email address hidden>
Subject: tagging 330824

tags 330824 + fixed

[Micah Anderson (micah-debian)]

tags 330824 - fixed

[Debian Bug Importer (debzilla)]

Message-Id: <20051105184058.987E54D8F8@pond>
Date: Sat, 5 Nov 2005 13:40:58 -0500 (EST)
From: <email address hidden> (micah)
To: <email address hidden>
Subject: tagging 330824

tags 330824 - fixed