Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDABE109A4 for ; Wed, 5 Feb 2014 17:07:36 +0000 (UTC) Received: (qmail 86012 invoked by uid 500); 5 Feb 2014 17:07:36 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 85990 invoked by uid 500); 5 Feb 2014 17:07:36 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 85982 invoked by uid 99); 5 Feb 2014 17:07:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Feb 2014 17:07:36 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Feb 2014 17:07:30 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=k4FbkPig7ie/lCyhjLdPLMbVwkWB+HA5G3LVcvqjCwU=; b=pKR0aVWZ5aQXI4XaZW+wfy1QSwbf+iuTs+kJRXX9+kXPTSNrHNPZEyE0XRRo3fozd859Bfx382ODl7zItRF6vF5Y/NntnSHTVfxK3jL+yrEdmHfyjy41otDsqaSwErA+plaxFVzGMWom7jANwj70+VMRkCbynfhlZ8A5ECjj5bM=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-4.v29.ch3.sourceforge.com) by sfs-alluradaemon-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WB5wL-0000Iy-AH for allura-dev@incubator.apache.org; Wed, 05 Feb 2014 17:07:09 +0000 Content-Type: multipart/related; boundary="===============3243366426385403471==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6952@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6952 404 on specific Git branch [ss6144] Message-ID:

In-Reply-To: <52a1dfcc81b24b727f360bd2.tickets@allura.p.sourceforge.net> References: <52a1dfcc81b24b727f360bd2.tickets@allura.p.sourceforge.net> Date: Wed, 05 Feb 2014 17:07:09 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============3243366426385403471== Content-Type: multipart/alternative; boundary="===============7292322530571347807==" MIME-Version: 1.0 --===============7292322530571347807== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Looks like the root cause of this is [#7021]. We'll see if we can address that soon. --- ** [tickets:#6952] 404 on specific Git branch [ss6144]** **Status:** open **Labels:** support p3 **Created:** Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai **Last Updated:** Wed Feb 05, 2014 01:51 PM UTC **Owner:** nobody [forge:site-support:#6144] >On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch. https://sourceforge.net/p/hummstrumm/code/ Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============7292322530571347807== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Looks like the root cause of this is [#7021]. We'll see if we can address that soon.

[tickets:#6952] 404 on specific Git branch [ss6144]

Status: open
Labels: support p3
Created: Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai
Last Updated: Wed Feb 05, 2014 01:51 PM UTC
Owner: nobody

[forge:site-support:#6144]

On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch.

https://sourceforge.net/p/hummstrumm/code/

Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked.

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============7292322530571347807==-- --===============3243366426385403471==--