A user emailed me today asking if I could push out some changes to a network packet analysis and creation library that I created and maintain, Packet.Net. These changes were included in the last release packages I pushed our a few months ago but apparently weren't in the git repository on SourceForge. This didn't make a lot of sense because I use some scripts that build binary and source release zip files by doing a git export of a specified tag from the remote repository on SourceForge. Plus I'm usually pretty careful to push everything out in case something happens to my laptop.
Went to the SourceForge code browser web page where you can browse the repository from a web browser and sure enough there were tags and commits were missing, when compared to my local development repository/directory. I ran git status from my development directory and it showed up to date. Ran a push but it said the same. Even tried a force push but git didn't take any action.
I suspected that maybe the web based source browser wasn't showing me all of the latest changes so I cloned the directory again and sure enough it was missing the latest commits and matched the web based source browser. At that point I had no idea what was going on. Clearly git was communicating with the server from my development directory and not seeing anything to update. At the same time, the newly cloned repository was missing the same several commits that the web interface was so it wasn't just the web interface that was missing changes.
That's when I started thinking that maybe the repositories weren't the same. That the URL I cloned from and the web interface were showing a git repository at one location and my development directory was pointing at another. Checked in .git/config and compared the repository URL to the one on the SourceForge on the code page and sure enough, they didn't match.
Once I had updated the URL in my development directory's .git/config to match SourceForge, git status started reporting that I was ahead by several commits. This indicated that the repository shown on SourceForge was not the one I've been trying to push to.
I'm still not sure when things changed but it appears that SourceForge moved project repositories but didn't move enough for git to know something was wrong. Because I was able to push to the old path it almost appears that they copied the repository, leaving the ssh server running, and pointed the web interface at the new location without removing the old one.
Comments
Post a Comment