Re: Another broken Git repository
On 06/12/2012 08:39 AM, Charles Plessy wrote: > Le Tue, Jun 12, 2012 at 08:33:27AM +0200, Michael Wild a écrit : >> >> Ah, that would explain it. Just out of curiosity: where should I have >> found this information? > > http://wiki.debian.org/Alioth > > Cheers, > Thanks Michael -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fd6e518.5040...@gmail.com
Re: Another broken Git repository
Le Tue, Jun 12, 2012 at 08:33:27AM +0200, Michael Wild a écrit : > > Ah, that would explain it. Just out of curiosity: where should I have > found this information? http://wiki.debian.org/Alioth Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120612063948.gb27...@falafel.plessy.net
Re: Another broken Git repository
On 06/12/2012 08:20 AM, Charles Plessy wrote: > Le Tue, Jun 12, 2012 at 08:09:43AM +0200, Michael Wild a écrit : >> >> For some time now I can't do anything when I log in to alioth.debian.org >> since it seems that /srv/git.debian.org is mounted read-only. E.g. my >> repository (viennacl.git) is missing the cia-project hook entry, but due >> to the read-only file system I cannot change it. >> >> Any idea what's going on? > > Dear Michael, > > Alioth has been split in two machines, vasks.debian.org and wagner.debian.org. > The repositories are writable on vasks.debian.org. > > Have a nice day, > Ah, that would explain it. Just out of curiosity: where should I have found this information? Thanks for the explanation. Michael -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fd6e2b7.4080...@gmail.com
Re: Another broken Git repository
Le Tue, Jun 12, 2012 at 08:09:43AM +0200, Michael Wild a écrit : > > For some time now I can't do anything when I log in to alioth.debian.org > since it seems that /srv/git.debian.org is mounted read-only. E.g. my > repository (viennacl.git) is missing the cia-project hook entry, but due > to the read-only file system I cannot change it. > > Any idea what's going on? Dear Michael, Alioth has been split in two machines, vasks.debian.org and wagner.debian.org. The repositories are writable on vasks.debian.org. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120612062036.ga27...@falafel.plessy.net
Re: Another broken Git repository
On 06/10/2012 04:58 PM, David Bremner wrote: > Andreas Tille writes: > >> As a Git beginner I think there are many powerful features in Git but >> also many ways to end up with a broken repository. That's a bit >> frustrating, thought. Any hint? > > I guess mycae-guest did not use the setup-repository script. > > I have run > > /usr/bin/git --bare init --shared > /usr/bin/git config --add hooks.mailinglist \ >"debian-science-comm...@lists.alioth.debian.org" > /usr/bin/git config --add hooks.cia-project debian-science > > i.e., just copy pasted the relevant lines from the script. > > Hopefully that fixes it ... if so, maybe another script called > "fixup-repository" would be useful. > > d For some time now I can't do anything when I log in to alioth.debian.org since it seems that /srv/git.debian.org is mounted read-only. E.g. my repository (viennacl.git) is missing the cia-project hook entry, but due to the read-only file system I cannot change it. Any idea what's going on? Thanks Michael -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fd6dd27.5010...@users.sourceforge.net
Re: Another broken Git repository
Andreas Tille writes: > As a Git beginner I think there are many powerful features in Git but > also many ways to end up with a broken repository. That's a bit > frustrating, thought. Any hint? I guess mycae-guest did not use the setup-repository script. I have run /usr/bin/git --bare init --shared /usr/bin/git config --add hooks.mailinglist \ "debian-science-comm...@lists.alioth.debian.org" /usr/bin/git config --add hooks.cia-project debian-science i.e., just copy pasted the relevant lines from the script. Hopefully that fixes it ... if so, maybe another script called "fixup-repository" would be useful. d -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r4tnciyj.fsf@zancas.localnet
Re: Another broken Git repository
Hi, On Sun, Jun 10, 2012 at 06:27:40PM +1000, Drew Parsons wrote: > On Sun, 2012-06-10 at 10:12 +0200, Andreas Tille wrote: > > Hi, > > > > I checked out > > > >git clone > > git+ssh://git.debian.org/git/debian-science/packages/liblemon1.git > > > > and did some small cosmetic changes (Vcs fields are broken and thus the > > recently announced machine-readable gatherer stumbles upon it). Then I > > tried to push: > > > > remote: error: refusing to update checked out branch: refs/heads/master > > remote: error: By default, updating the current branch in a non-bare > > repository > > remote: error: is denied, because it will make the index and work tree > > inconsistent > > remote: error: with what you pushed, and will require 'git reset --hard' to > > match > > remote: error: the work tree to HEAD. > > remote: error: > > > As a Git beginner I think there are many powerful features in Git but > > also many ways to end up with a broken repository. That's a bit > > frustrating, thought. Any hint? > > When it refers to a "non-bare repository", that makes me think of some > experience I had setting up my repos. When it says "non-bare > repository" I think it might mean that git.debian.org holds a normal > working repo, such that if you navigate there on the filesystem (logging > on to git.debian.org) you can see all the files checked out as if they > were ready to be worked on by a normal developer. This was the normal > state of remote repos a few years back, but later they introduced the > concept of "bare repository", which contains only the .git data, nothing > checked out. > > The simplest resolution may be to move (or rename) your nonbare > repository to a different directory, then in the proper (empty) > directory create a new, bare, repository, something like "git init > --bare". (there's various group configurations you could then apply if > you need to, e.g. > http://debian-science.alioth.debian.org/debian-science-policy.html#idp16612040 > http://wiki.debian.org/DebianScience/ContributingToDebianScience > http://lists.debian.org/debian-science/2008/05/msg00118.html ) > > You should then be able to push into that new bare repo. I admit that does not sound very simple just to fix some broken Vcs fields. I wonder whether the initial maintainer D Haley might like to care for it in case he really intends to upload this package any more (It was touched the last time Sat Mar 13 21:09:47 2010). If not we might consider cleaning up our repository from this packaging at all. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120610091245.ge12...@an3as.eu
Re: Another broken Git repository
On Sun, 2012-06-10 at 10:12 +0200, Andreas Tille wrote: > Hi, > > I checked out > >git clone > git+ssh://git.debian.org/git/debian-science/packages/liblemon1.git > > and did some small cosmetic changes (Vcs fields are broken and thus the > recently announced machine-readable gatherer stumbles upon it). Then I > tried to push: > > remote: error: refusing to update checked out branch: refs/heads/master > remote: error: By default, updating the current branch in a non-bare > repository > remote: error: is denied, because it will make the index and work tree > inconsistent > remote: error: with what you pushed, and will require 'git reset --hard' to > match > remote: error: the work tree to HEAD. > remote: error: > As a Git beginner I think there are many powerful features in Git but > also many ways to end up with a broken repository. That's a bit > frustrating, thought. Any hint? When it refers to a "non-bare repository", that makes me think of some experience I had setting up my repos. When it says "non-bare repository" I think it might mean that git.debian.org holds a normal working repo, such that if you navigate there on the filesystem (logging on to git.debian.org) you can see all the files checked out as if they were ready to be worked on by a normal developer. This was the normal state of remote repos a few years back, but later they introduced the concept of "bare repository", which contains only the .git data, nothing checked out. The simplest resolution may be to move (or rename) your nonbare repository to a different directory, then in the proper (empty) directory create a new, bare, repository, something like "git init --bare". (there's various group configurations you could then apply if you need to, e.g. http://debian-science.alioth.debian.org/debian-science-policy.html#idp16612040 http://wiki.debian.org/DebianScience/ContributingToDebianScience http://lists.debian.org/debian-science/2008/05/msg00118.html ) You should then be able to push into that new bare repo. Drew -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1339316860.9487.9.ca...@schumann.anu.edu.au
