Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1387264

Summary: RFE: DAV SVN should support backreferences & environment variables
Product: Red Hat Enterprise Linux 8 Reporter: Ondrej <ondrej.valousek.xm>
Component: subversionAssignee: Joe Orton <jorton>
Status: CLOSED MIGRATED QA Contact: rhel-cs-infra-services-qe <rhel-cs-infra-services-qe>
Severity: low Docs Contact:
Priority: low    
Version: 8.4CC: cww, dmasirka, jorton, luhliari, ondrej.valousek.xm
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 21:07:32 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1477664, 1562205, 1654421    

Description Ondrej 2016-10-20 13:42:21 UTC
It would be good if DAV_SVN could support backreferences & env variables in
SVNPATH and SVNPARENTPATH options

Comment 3 Joe Orton 2017-01-28 09:32:09 UTC
Please contact Red Hat Support if this is an issue for you in a production
deployment.

Comment 4 Ondrej 2017-01-30 07:53:52 UTC
Created RH support case #01781967

Comment 7 Joe Orton 2017-02-09 15:49:48 UTC
Thanks for opening a ticket, Ondrej.  It doesn't look like there's anything implemented upstream like this.

Can you explain exactly the kind of config you'd like to get working here?  You want a directive something like:

   SVNPathMatch <regex> <path-to-repos-using-regex-refences>

?

Comment 9 Ondrej 2017-02-09 16:15:05 UTC
Hi Joe,

I think no extra option should be (ideally) necessary.
It should basically work the way as described in:

https://httpd.apache.org/docs/2.4/sections.html

i.e. example:

<LocationMatch "^/svn/(?<SVNREPO>[^/]+)">
    DAV svn
    SVNParentPath "/proj/%{env:MATCH_SVNREPO}/svn"
    ....
</LocationMatch>

Does it make a sense?

Comment 20 RHEL Program Management 2023-09-21 20:51:29 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 21 RHEL Program Management 2023-09-21 21:07:32 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.