[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#718256: marked as done (edbrowse: Wrong URL in control file for Subversion-Repository.)

Your message dated Sat, 25 Oct 2014 13:14:30 +0200
with message-id <20141025111430.GA3823@type.youpi.perso.aquilenet.fr>
and subject line Re: Bug#718256: edbrowse: Wrong URL in control file for Subversion-Repository.
has caused the Debian Bug report #718256,
regarding edbrowse: Wrong URL in control file for Subversion-Repository.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

718256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718256
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: edbrowse
Version: 3.4.9-1
Severity: minor
Tags: patch

Dear Maintainer,

Typo in Vcs-Svn-URL. Please see my attached patch. 

Regards, Simon

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- control.orig	2013-07-29 12:56:57.947908330 +0200
+++ control	2013-07-29 12:57:04.708120642 +0200
@@ -7,7 +7,7 @@
 Maintainer: Jean-Philippe MENGUAL <texou@accelibreinfo.eu>
 Build-Depends: debhelper (>= 9), libreadline-dev, libpcre3-dev, libssl-dev,
  libcurl4-openssl-dev, libmozjs185-dev
-Vcs-Svn: svn://anoncsm.debian.org/collab-maint/deb-maint/edbrowse
+Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/edbrowse
 Homepage: http://the-brannons.com/edbrowse
 Standards-Version: 3.9.4

--- End Message ---
--- Begin Message ---

Thanks for the report, it seems to have been fixed.


--- End Message ---

Reply to: