Problem with svn: cannot checkout xfburn sources
Hello, for a few days now I am trying to update the xfburn port on my Crux 2.4 system. All other ports are up to date. It always hangs while running the svn checkout command until I kill -9 the svn process. Exactly it hangs after creating the .svn directory under /usr/ports/xfce/xfburn/work/src/xfburn. I have rebuilt the subversion port and all of its dependencies without a change of the behaviour of the svn checkout command in the xfburn port. I have asked someone else with a different system (Mac OS X) to checkout the xfburn sources with the same command as in the xfburn port. He could check out the sources without a problem. I have no clue where else to search for the cause. Can anyone please help me? Regards, Markus
On Sun, 20 Apr 2008 16:58:16 +0200 Markus Heinz wrote:
Hello, Hi, Markus. for a few days now I am trying to update the xfburn port on my Crux 2.4 system. All other ports are up to date. It always hangs while running the svn checkout command until I kill -9 the svn process. Exactly it hangs after creating the .svn directory under /usr/ports/xfce/xfburn/work/src/xfburn.
pedja@deus:/usr/ports/xfce/xfburn ]$ pkgmk =======> Building `/usr/pkgmk/package/xfburn#0.3.0svn-4597-1.pkg.tar.gz'. =======> Entering fakeroot environment =======> Building `/usr/pkgmk/package/xfburn#0.3.0svn-4597-1.pkg.tar.gz'. + build + svn co -r4597 http://svn.xfce.org/svn/goodies/xfburn/trunk xfburn A xfburn/update-changelog.sh A xfburn/class diagram.zuml A xfburn/xfburn.ui <snip> A xfburn/po/zh_CN.po U xfburn Checked out revision 4597. --- It works fine here.
I have rebuilt the subversion port and all of its dependencies without a change of the behaviour of the svn checkout command in the xfburn port.
I have asked someone else with a different system (Mac OS X) to checkout the xfburn sources with the same command as in the xfburn port. He could check out the sources without a problem.
Have you tried to to use svn to checkout something else from Xfce repo i.e 'svn co http://svn.xfce.org/svn/xfce/squeeze/ trunk' or from any other project?
I have no clue where else to search for the cause. Can anyone please help me?
I uploaded xfburn sources tarball here[1], so you can build a port, and later you can check if 'svn update' works. HTH [1]http://rapidshare.com/files/109031102/xfburn.tar.gz.html Pedja -- Crux is like a good looking, really good looking, gorgeous, hot girl without any cheap perfume or makeup, waiting for you to customize her in any way you see fit. On top of that, she is free, permanent and wont make absurd and disturbing demands. - Kunal Anshu@OSNews
Predrag Ivanovic [2008-04-20 19:13]:
I have no clue where else to search for the cause. Can anyone please help me?
I uploaded xfburn sources tarball here[1], so you can build a port, and later you can check if 'svn update' works. HTH
I suggest that the port is changed to not call "svn co", but to grab a snapshot tarball off the web. Jose, what do you think? Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Tilman Sauerbeck wrote:
Predrag Ivanovic [2008-04-20 19:13]:
I have no clue where else to search for the cause. Can anyone please help me?
I uploaded xfburn sources tarball here[1], so you can build a port, and later you can check if 'svn update' works. HTH
I suggest that the port is changed to not call "svn co", but to grab a snapshot tarball off the web.
Like I have done with x264 and other ports. Snapshots are a lot better for a ports repository IMO as not everyone will want to install subversion to get that port just like i got told off for forcing LZMA in some of my ports. Regards, Romster
Jose, what do you think?
Regards, Tilman
------------------------------------------------------------------------
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Hello, On Sun, 20 Apr 2008 19:13:03 +0200 Predrag Ivanovic <predivan@nadlanu.com> wrote:
On Sun, 20 Apr 2008 16:58:16 +0200 Markus Heinz wrote:
Hello, Hi, Markus. for a few days now I am trying to update the xfburn port on my Crux 2.4 system. All other ports are up to date. It always hangs while running the svn checkout command until I kill -9 the svn process. Exactly it hangs after creating the .svn directory under /usr/ports/xfce/xfburn/work/src/xfburn. [...] It works fine here.
I have rebuilt the subversion port and all of its dependencies without a change of the behaviour of the svn checkout command in the xfburn port.
I have asked someone else with a different system (Mac OS X) to checkout the xfburn sources with the same command as in the xfburn port. He could check out the sources without a problem.
Have you tried to to use svn to checkout something else from Xfce repo i.e 'svn co http://svn.xfce.org/svn/xfce/squeeze/ trunk' or from any other project?
I have run the above command and it hang too after retrivieng the .svn folder.
I have no clue where else to search for the cause. Can anyone please help me?
I uploaded xfburn sources tarball here[1], so you can build a port, and later you can check if 'svn update' works.
Thanks. At least I could build the port with the tarball. But running an update in the xfburn folder did hang too. Here some background information: I have installed the Gnome ports from the Gnome repository in order be able to use Zattoo for which I have created some ports too. Before installing Gnome I could run the svn commands without problems. But now it does not work anymore. Until now I do not see a relation between installing Gnome and Zattoo and svn ceasing to function. Regards, Markus
Hello, On Sun, 20 Apr 2008 20:07:48 +0200 Markus Heinz <markus.heinz@uni-dortmund.de> wrote:
Hello,
On Sun, 20 Apr 2008 19:13:03 +0200 Predrag Ivanovic <predivan@nadlanu.com> wrote:
On Sun, 20 Apr 2008 16:58:16 +0200 Markus Heinz wrote:
Hello, Hi, Markus. for a few days now I am trying to update the xfburn port on my Crux 2.4 system. All other ports are up to date. It always hangs while running the svn checkout command until I kill -9 the svn process. Exactly it hangs after creating the .svn directory under /usr/ports/xfce/xfburn/work/src/xfburn. [...] It works fine here.
I have rebuilt the subversion port and all of its dependencies without a change of the behaviour of the svn checkout command in the xfburn port.
I have asked someone else with a different system (Mac OS X) to checkout the xfburn sources with the same command as in the xfburn port. He could check out the sources without a problem.
Have you tried to to use svn to checkout something else from Xfce repo i.e 'svn co http://svn.xfce.org/svn/xfce/squeeze/ trunk' or from any other project?
I have run the above command and it hang too after retrivieng the .svn folder.
I have no clue where else to search for the cause. Can anyone please help me?
I uploaded xfburn sources tarball here[1], so you can build a port, and later you can check if 'svn update' works.
Thanks. At least I could build the port with the tarball. But running an update in the xfburn folder did hang too.
Here some background information: I have installed the Gnome ports from the Gnome repository in order be able to use Zattoo for which I have created some ports too. Before installing Gnome I could run the svn commands without problems. But now it does not work anymore. Until now I do not see a relation between installing Gnome and Zattoo and svn ceasing to function.
Here is the solution of this mystery: 1. This is no problem of Crux Linux 2. This is no problem of subversion 3. This is no problem of my particular install The cause of the problem is as follows: svn needs some HTTP methods which are not supported by all proxy servers. (Thanks to Jose V Beneyto for pointing this out.) I do not have configured a proxy server on my system. But my ISP seems to force all HTTP traffic through a transparent proxy. And this transparent proxy does not support all necessary HTTP methods. I have tried to run the svn command when connected with a different ISP and it worked flawlessly. I will now contact my ISP to change his proxy settings. Regards, Markus
participants (4)
-
Danny Rawlins -
Markus Heinz -
Predrag Ivanovic -
Tilman Sauerbeck