[SOLVED] urxvt and Git/SVN commit problem

I have a problem where SVN and Git cant see that the EDITOR variable is set on my system when I go to make a commit, they both error out because the EDITOR variable (as well as other variables are blank).  This is the error that I get from SVN:
┌─(vendion@Tyre Fri, 02 Sep 11)───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(08:48)──┘
└─(/srv/http/juice38)─> sudo svn ci
svn: Commit failed (details follow):
svn: Could not use external editor to fetch log message; consider setting the $SVN_EDITOR environment variable or using the --message (-m) or --file (-F) options
svn: None of the environment variables SVN_EDITOR, VISUAL or EDITOR are set, and no 'editor-cmd' run-time configuration option was found
┌─(vendion@Tyre Fri, 02 Sep 11)───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(08:48)──┘
└─(/srv/http/juice38)─> echo $EDITOR
vim
Git acts the same way but with its own error message (sorry don't have an example of this currently), is there a way to fix this so that Git and SVN will see that I do have an EDITOR set and use it with out having to change terminals (works fine in xterm...)
Last edited by vendion (2011-09-02 16:08:48)

Sorry over looked that, when I run sudo to check the EDITOR variable it also has vim set
┌─(vendion@Tyre Fri, 02 Sep 11)───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(09:42)──┘
└─(/home/vendion/Projects/TickIt)─> sudo echo $EDITOR
Password:
vim

Similar Messages

  • [Solved] $LANG and zsh prompt color problems

    Hi,
    I recently discovered, trying to use Newsbeuter, that, in X, certain parts of my profile aren't set. Until now it only seemed to be $LANG, which is empty if I echo it from urxvt in XMonad, but yields the correct setting if I do the same in a tty.
    To make things worse now, my zsh seems to be acting up. I have differently colored prompts for my normal user and root. But since a few days ago, the root colors aren't applied unless I source .zshrc again after sudo-ing.
    I updated a lot recently and it's gotten hard to track these issues, especially the $LANG one, to a specific update. The only thing I know is that my desktop, running Kdemod, doesn't have these problems.
    I'm using Slim and XMonad. Neither issue is limited to a certain terminal.
    Most of my configs can be found in my GitHub dotfiles repository. If anything's missing to get a clear picture, ask for it.
    My rc.conf can be found here [Gist].
    Last edited by count-corrupt (2010-08-22 13:33:06)

    jac wrote:
    I finally went through the new sudoers file and got mine to work, see this thread for details. Using that, and using a workaround for libetc, your prompt works for me.
    You appear not to use libetc, but if you do and don't also have root set up to use libetc, you will need to create a link to/from ~/.zshrc from/to ~/.config/zshrc
    I actually just solved it in another way. Your original point, that sudo changed it's default behavior was the key. In the official zsh documentation somewhere it says that all settings that are wanted for root should be put into /root/.zshrc. I just did that and it works.
    Your solution works too by the way. Just enabling
    Defaults env_keep += "HOME"
    does the trick and also (logically) re-enables other things that I hadn't even realized were gone yet like syntax highlighting in vim. I guess I should read into the nature of said privilige escalation problems. Maybe there's a way to selectively keep parts of HOME.
    So thank you very much for the help.

  • [solved]URxvt and Xdefaults configurations not used

    Yesterday I noticed that my middle-mouse button paste from URxvt had stopped working, and today I noticed that seemingly all my configurations (besides fonts) aren't being used in URxvt.  If I run "source .Xdefaults" from a running URxvt, I get the error "no matches found: <option>".  This error is returned for the first line of the configuration, and the following settings were moved from the top to the bottom to see if any other configurations work:
    URxvt*perl-ext-common: default,matcher,clipboard
    URxvt*perl-ext: xim-onthespot
    urxvt*urlLauncher: /usr/bin/firefox
    urxvt*matcher.button: 1
    The only changes I can think of is adding the xim-onthespot line, the recent update to perl (however, since it occurs on non-perl lines as well, I'm not sure this is important), and the update to rxvt-unicode itself about 8 days ago (the problems could have been present thereafter, I just hadn't noticed).
    Has the syntax changed, or is there something blatantly obvious I overlooked?  I have also tried replacing the asterisk with a period (which results in a command not found error).  It seems to me that no one else has posted this problem here yet, but I may have missed it somewhere, and if so, a link would be nice.
    #urxvt*perl-lib: /usr/lib/urxvt/perl
    urxvt*termName: rxvt-unicode
    urxvt*internalBorder: 1
    urxvt*loginShell: true
    urxvt*background: rgba:0000/0000/0000/cccc
    urxvt*background: [70]#000000
    urxvt*foreground: white
    urxvt*transparent: 1
    urxvt*colorMode: on
    urxvt*cursorBlink: 0
    urxvt*depth: 32
    urxvt*color0: #000000
    urxvt*color1: #9e1828
    urxvt*color2: #aece92
    urxvt*color3: #968a38
    urxvt*color4: #414171
    urxvt*color5: #963c59
    urxvt*color6: #418179
    urxvt*color7: #bebebe
    urxvt*color8: #666666
    urxvt*color9: #cf6171
    urxvt*color10: #c5f779
    urxvt*color11: #fff796
    urxvt*color12: #4186be
    urxvt*color13: #cf9ebe
    urxvt*color14: #71bebe
    urxvt*color15: #ffffff
    urxvt*fading: 40
    #urxvt*tintColor: white
    urxvt*shading: 0
    urxvt*inheritPixmap: 0
    urxvt*scrollBar: 0
    urxvt*geometry: 81x22
    urxvt*saveLines:1000
    urxvt*font: xft:Inconsolata:pixelsize=12:antialias=true:hinting=true
    urxvt*boldFont: xft:Inconsolata:pixelsize=12:antialias=true:bold:hinting=true
    urxvt*italicFont: xft:Inconsolata:pixelsize=12:antialias=true:italic:autohint=true:hinting=true
    urxvt*bolditalicFont: xft:Inconsolata:pixelsize=12:antialias=true:bold:italic:autohint=true:hinting=true
    URxvt*preeditType: OnTheSpot,None
    URxvt*perl-ext-common: default,matcher,clipboard
    URxvt*perl-ext: xim-onthespot
    urxvt*urlLauncher: /usr/bin/firefox
    urxvt*matcher.button: 1
    Xcursor.theme: Vanilla-DMZ-AA
    Xcursor.size: 16
    Last edited by lswest (2010-08-12 00:28:29)

    lswest wrote:If I run "source .Xdefaults" from a running URxvt, I get the error "no matches found: <option>".
    "source" is a bash builtin to execute bash code in the context of the current shell session. The errors you get are due to the fact that it's actually bash trying to run the contents of your .Xdefaults as shell commands. To make changes to an Xdefaults file take effect, use
    xrdb -merge ~/.Xdefaults
    Changes to Xdefaults should take effect in any case if you restart X, though. Maybe there's something else amiss, but at least sourcing the file is definitely wrong.

  • [solved] DWM and Volti tray icon problem....

    I have a problem with the tray icon of dwm.
    I set up Faenza dark as icon theme, and all the tray appear white (correctly). Only the volti icons appear black and  I not understand why.
    Everyone can help me?
    Thanks.
    Last edited by monotiz (2011-03-03 11:53:49)

    monotiz wrote:
    I have a problem with the tray icon of dwm.
    I set up Faenza dark as icon theme, and all the tray appear white (correctly). Only the volti icons appear black and  I not understand why.
    Everyone can help me?
    Thanks.
    What you use for system tray in dwm?

  • [SOLVED] sudo and "command not found" problems

    Ok, the problem I've got is this: sudo has suddenly started acting real strange. It can't find any programs. For example, if i type
    sudo echo
    It just goes
    sudo: echo: command not found
    And another problem I've got, is that as a regular user, it can't find programs in /sbin, or other "exotic" places. For example it can't find firefox, because it's not in /usr/bin or /bin, but in /opt/mozilla/bin.
    Please, help me!
    Last edited by mrpedroxx (2008-06-14 13:23:49)

    sudo -V outputs this
    Sudo version 1.6.9p15
    $PATH outputs
    bash: /usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.: No such file or directory
    pacman -Q firefox outputs
    firefox 2.0.0.7-1
    Yeah, maybe I should update it anyway
    And /var/log/errors.log does contain stuff about hard disks, but it's just me mounting my iPod and the Windows partition on my hd

  • [solved] urxvt and .Xdefaults

    edit: I totally forgot about
    xrdb -load ~/.Xdefaults
    Last edited by dax965 (2008-01-19 23:34:58)

    lswest wrote:If I run "source .Xdefaults" from a running URxvt, I get the error "no matches found: <option>".
    "source" is a bash builtin to execute bash code in the context of the current shell session. The errors you get are due to the fact that it's actually bash trying to run the contents of your .Xdefaults as shell commands. To make changes to an Xdefaults file take effect, use
    xrdb -merge ~/.Xdefaults
    Changes to Xdefaults should take effect in any case if you restart X, though. Maybe there's something else amiss, but at least sourcing the file is definitely wrong.

  • [SOLVED] SPA122 and Siemens Gigaset CLI problem

    Hi, I'm trying to configure my SPA122 to be used with a couple of Gigaset cordless, it's almost all working fine except the CLI that it's not displayed.
    This is my ATA version:
    Model:
    SPA122, LAN, 2 FXS
    Hardware Version:
    1.0.0
    Boot Version:
    1.0.1 (Oct 6 2011 - 20:04:00)
    Firmware Version:
    1.3.2 (014) May 9 2013
    Recovery Firmware:
    1.0.2 (001)
    WAN MAC Address:
    88:75:56:07:66:66
    Host Name:
    SPA122
    Domain Name:
    (none)
    Serial Number:
    CCQ164105A3
    Current Time:
    Thu, 04 Jul 2013 17:30:32
    Could someone point me in the right direction?
    Thanks in advance,
    Andrea

    Solved,
    I tryed some configuration until found the right working:
    Caller ID Method:   
    Bellcore(N.Amer,China)DTMF(Finland,Sweden)DTMF(Denmark)ETSI DTMFETSI DTMF With PRETSI DTMF After RingETSI FSKETSI FSK With PR(UK)DTMF(Denmark) With PR
    Caller ID FSK Standard:   
    bell 202v.23
    BTW, I'm in Italy, I don't know if it works in others country.
    Regards,
    Andrea

  • [Solved]urxvt does not search the font for emojis while gnome-terminal

    Hi, I'm using urxvt and am having some problems setting up fonts. These are my URxvt parameters specifying the fonts
    URxvt*font: xft:Inconsolata-dz for Powerline:style=Semibold:pixelsize=14:antialias=true:hinting=slight, \
    xft:PowerlineSymbols:pixelsize=14:antialias=true:hinting=slight, \
    xft:Symbola:pixelsize=14:antialias=true:hinting=slight
    Now, the emojis from Symbola does not appear and it only appears as a box
    The same thing when opened in Gnome-terminal properly displays the emojis
    Also, I have tried starting urxvt with the following options
    urxvt -fn "xft:Symbola"
    and it works but as you see Symbola is not a font for your terminal.
    What am I doing wrong here? I've check my previous lines and it is right. Do you guys have any ideas? Much appreciated. I have also tried with other posts stating that Urxvt cannot display symbols properly and have tried them all. If I've missed any please let me know. The strange thing is that it works for Gnome-terminal and Urxvt with only Symbola fonts
    Last edited by decryptedepsilon (2014-07-12 02:40:24)

    bch24 wrote:
    Make sure the System Locale is set to utf-8 locale.
    This sometimes is the issue.
    Many thanks for your reply, I've checked the system locale is proper. I think I have found the solution.
    I think the official rxvt-unicode faq and documentation here states that rxvt-unicode drops pixels while showing some fonts because different fonts use different height and width. In this particular case, Symbola font is too wide and the default letterSpace does not allow it to display correct. If -letsp parameter is set to 4, it is displaying but with about a half pixel missing
    The specific parameters for .Xresources
    URxvt*font: xft:Inconsolata-dz for Powerline,xft:Symbola
    URxvt*letterSpace: 4
    And this gives this which technically solves the issue
    The documentation clearly states the following
    All of this requires that fonts do not lie about character sizes, however: Xft fonts often draw glyphs larger than their acclaimed bounding box, and rxvt-unicode has no way of detecting this (the correct way is to ask for the character bounding box, which unfortunately is wrong in these cases).
    I guess the first thing one should do is to check the documentation thoroughly of the official project page rather than searching countless forums where people have discussed stuff based on trial and error. I guess that's a classic rookie mistake and I feel very good that I'm moving past the rookie phase

  • [SOLVED]mplayer and urxvt problems after update

    Hello to all fellow archers!
    Couple of days back, I updated xorg-server, like most of the people around here, so I asume that issues I`m going to describe, could be related to xorg-server being recently updated.
    First issue is related to mplayer not playing movies in fullscreen format, despite being told to do so. The image size of a video is about 20% of screen resolution size, while the rest of the screen is just black.
    MPlayer 1.0rc2-4.3.2 (C) 2000-2007 MPlayer Team
    CPU: AMD Athlon(tm) Processor (Family: 6, Model: 6, Stepping: 2)
    CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
    Compiled with runtime CPU detection.
    115 audio & 237 video codecs
    mplayer: could not connect to socket
    mplayer: No such file or directory
    Failed to open LIRC support. You will not be able to use your remote control.
    Playing Death.Proof[2007][Unrated.Editon]DvDrip[Eng]-aXXo.avi.
    AVI file format detected.
    [aviheader] Video stream found, -vid 0
    [aviheader] Audio stream found, -aid 1
    VIDEO: [DX50] 664x280 12bpp 23.976 fps 741.7 kbps (90.5 kbyte/s)
    Clip info:
    Software: VirtualDubMod 1.5.10.1 (build 2366/release)
    SUB: Detected subtitle file format: microdvd
    SUB: Read 1877 subtitles.
    SUB: Added subtitle file (1): ./Death.Proof[2007][Unrated.Editon]DvDrip[Eng]-aXXo.srt
    [VO_XV] It seems there is no Xvideo support for your video card available.
    [VO_XV] Run 'xvinfo' to verify its Xv support and read
    [VO_XV] DOCS/HTML/en/video.html#xv!
    [VO_XV] See 'mplayer -vo help' for other (non-xv) video out drivers.
    [VO_XV] Try -vo x11.
    ==========================================================================
    Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
    Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
    ==========================================================================
    ==========================================================================
    Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
    AUDIO: 48000 Hz, 2 ch, s16le, 112.0 kbit/7.29% (ratio: 14000->192000)
    Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
    ==========================================================================
    AO: [oss] 48000Hz 2ch s16le (2 bytes per sample)
    Starting playback...
    VDec: vo config request - 664 x 280 (preferred colorspace: Planar YV12)
    VDec: using Planar YV12 as output csp (no 0)
    Movie-Aspect is 2.37:1 - prescaling to correct movie aspect.
    VO: [x11] 664x280 => 664x280 Planar YV12
    [swscaler @ 0x89d5f50]SwScaler: using unscaled yuv420p -> rgb32 special converter
    A: 67.6 V: 67.6 A-V: -0.001 ct: 0.114 1621/1621 7% 12% 1.0% 0 0
    Exiting... (Quit)
    I tried switching between many different video out drivers, the only one that plays video normaly is x11, but the image size is very small.
    I`m using vesa driver and my video card is
    lspci | grep VGA
    01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev 01)
    xorg.conf http://pastebin.com/f314eaaed
    Xorg.0.log http://pastebin.com/f570dbcf5
    I found a partial solution to mplayer problem in this tread http://bbs.archlinux.org/viewtopic.php?id=60054 where patroclo7 stated, that from this update on, X is using autodetection and doesn`t need xorg.conf anymore.
    Anyways I followed the advice deleted my xorg.conf and rebooted arch without xorg.conf. Everything works, even the video in mplayer is running at normal size, however the default screen resolution is a bit to high.
    I would like to set it to 1024x768 (monitor, philips 107E5) but don`t have a clue how to change screen resolution without xorg.conf being present. I`m using openbox as a standalone wm.
    I still have a backup of my working xorg.conf file, so I can switch between xorg.conf and the other config.
    Just for the record, video files are displayed properly using vlc as media player on both described configurations.
    To sum everything up, how to set screen resolution at 1024x 768 without xorg.conf being present or how to fix mplayer displaying movies in a very small screen/box, despite running in fullscreen mode (using xorg.conf).
    My second problem is regarding urxvt and its borderless. If I set it to true urxvt hangs on start everytime. The terminal is displayed in top left corner of the screen but it`s frozen and can`t be used, while being set to false works like a charm.
    Xdefaults
    #####Urxvt Config#####
    URxvt.termName: rxvt
    URxvt.transparent: true
    URxvt.inheritPixmap: true
    URxvt.imLocale: en_US.utf8
    URxvt.scrollBar: false
    URxvt.saveLines: 5000
    URxvt.urlLauncher: kazehakase
    URxvt.cursorBlink: true
    URxvt.fading: 15%
    URxvt.shading: 50
    !URxvt*background: [80]#ece9e2
    !URxvt.foreground: [80]#3d352a
    urxvt.depth: 24
    urxvt*background: rgba:0000/0000/0000/aaaa
    urxvt*foreground: rgba:ffff/ffff/ffff/aaaa
    URxvt.tintColor: #d9d7d1
    URxvt.borderLess: false
    !URxvt.InternalBorder: .5
    URxvt.externalBorder: .5
    URxvt.borderColor: #acacac
    ######Urxvt Colors######
    *foreground: rgba:0000/0000/0000/dddd
    *background: rgb:10/10/10
    !black
    *color0: rgb:20/20/20
    *color8: rgb:75/77/73
    !red
    *color1: rgb:cc/00/00
    *color9: rgb:ef/29/29
    !green
    *color2: rgb:4e/9a/06
    *color10: rgb:8a/e2/34
    !brown/yellow
    *color3: rgb:c4/a0/00
    *color11: rgb:fc/e9/4f
    !blue
    *color4: rgb:34/65/a4
    *color12: rgb:72/9f/cf
    !magenta
    *color5: rgb:75/50/7b
    *color13: rgb:ad/7f/a8
    !cyan
    *color6: rgb:06/98/9a
    *color14: rgb:34/e2/e2
    !white
    *color7: rgb:d3/d7/cf
    *color15: rgb:ee/ee/ec
    ! #####Xterm Config#####
    XTerm*background: black
    XTerm*foreground: gray
    XTerm*highlightColor: orange
    ######Stjerm Config######
    stjerm.key: f12
    stjerm.opacity: 50
    ######Stjerm colors######
    stjerm.color0: #202020
    stjerm.color1: #cc0000
    stjerm.color2: #4e9a06
    stjerm.color3: #c4a000
    stjerm.color4: #3465a4
    stjerm.color5: #75507b
    stjerm.color6: #06989a
    stjerm.color7: #d3d7cf
    stjerm.color8: #757773
    stjerm.color9: #ef2929
    stjerm.color10: #8ae234
    stjerm.color11: #fc394f
    stjerm.color12: #729fcf
    stjerm.color13: #ad7fa8
    stjerm.color14: #34e2e2
    stjerm.color15: #eeeeec
    ######Mouse Cursor Theme######
    Xcursor.theme:Neutral_Plus_Inv
    Any advice is highly appreciated.
    Regards,
    bandito
    Last edited by bandito (2008-12-05 21:35:11)

    The solution for mplayer using xorg.conf file as follows:
    To get fullscreen video working just add
    zoom = yes
    to /.mplayer/config
    In case if you are using gui for mplayer and get the following error trying to play a video file
    Error opening/initializing the selected video_out (-vo) device
    Open /.mplayer/gui.conf and change vo_driver from "xv" to "x11".
    Urxvt solution is described here http://bbs.archlinux.org/viewtopic.php?pid=457421 but also check this for explanation http://comments.gmane.org/gmane.comp.wi … enbox/3947
    regards
    Bandito
    Last edited by bandito (2008-12-05 21:34:31)

  • Solve this and you're a genious: Port problems with SRW2016

    Equipment:
    One SRW2016 fresh out of the box and set to factory default settings
    One Dell Laptop running Windows XP
    One custom network appliance running a full TCP/IP stack but limited to 10M half duplex.
    Setup:
    The laptop has a static IP address. The network appliance has a static IP address. The switch has the factory default static IP address.  All three devices are on the same subnet.
    The laptop is plugged into port 1 on the switch, and the network appliance is plugged into various ports as described below.  The laptop is set to continuously ping the network appliance using the ping –t command.
    Problem:
    When the network appliance is plugged into switch port 2 I am unable to ping the device from the laptop.  When I plug it into port 3 I get the same result.  In fact I am unable to ping the network appliance on any of the switch ports EXCEPT for ports 7, 8, 15, and 16.  As soon as I plug the network appliance into any one of those four ports, the pings are replied to. 
    My question is - why am I unable to communicate with the network appliance on any ports other then ports 7, 8, 15, and 16? What makes these four ports different then the others?
    Other Notes:
    I have a second Linksys SRW2016 and notice the exact same behavior.
    I’ve also tried a Linksys SLM2008 8-Port switch and experience NO communication problems on any ports.
    I’ve tried a hub and it works 100%
    I notice that after trying to ping the network appliance on a non-working port, I can see the device properly listed in the ARP table on both the switch AND laptop. So I am unable to ping the device yet it somehow makes it into the ARP table.
    Any help with this issue would be greatly appreciated.
    Best regards,
    Rob

    Hi,
    Thanks for explanation that not all ports are the same.
    I've just had a similar issue with a Siemens C470IP ip phone. It worked fine with my Dlink 8-port DES3010F switch which I've just replaced with the SRW2016, and also when plugged into my Draytek 2820n ADSL router's LAN ports. I'm a bit disappointed that I happened to plug the device into port 3 and suddenly my monitoring showed that things were not working properly. I checked cables and then remembered that auto-negotiation sometimes can cause problems.
    On the SRW2016 if I leave the port with auto-negotiate on I see:
                                  Flow  
    Port   Enable   Link  Spd/Dpx Ctrl  
    g3      ENABLE   UP    10H     Off
    Yet inspite this pinging the device does not work properly. That is I get from ping:
    64 bytes from 192.168.0.36: icmp_seq=431 ttl=128 time=7.357 ms
    Request timeout for icmp_seq 432
    64 bytes from 192.168.0.36: icmp_seq=433 ttl=128 time=8.956 ms
    Request timeout for icmp_seq 434
    64 bytes from 192.168.0.36: icmp_seq=435 ttl=128 time=5.920 ms
    Request timeout for icmp_seq 436
    Request timeout for icmp_seq 437
    Request timeout for icmp_seq 438
    Request timeout for icmp_seq 439
    Request timeout for icmp_seq 440
    64 bytes from 192.168.0.36: icmp_seq=441 ttl=128 time=9.242 ms
    Request timeout for icmp_seq 442
    Request timeout for icmp_seq 443
    Request timeout for icmp_seq 444
    Request timeout for icmp_seq 445
    Doing the explicit configuration of 10Mb Half duplex as suggested does not help either. In fact it's worse as I get no responses from a ping and it does not make any difference if I enable flow control or not.
    So must be the Siemens device? Well plugging into port 16 as suggested makes all the difference:
    Auto negotiation works and the link comes up and works fine:
    That is:
                    Auto          Flow  
      Port   Enable  Neg.  Spd/Dpx Ctrl  
    g13      ENABLE   On   Auto    Off 
    g14      ENABLE   On   Auto    Off 
    g15      ENABLE   On   Auto    Off 
    g16      ENABLE   On   Auto    Off 
    and
                                    Flow  
      Port   Enable   Link  Spd/Dpx Ctrl  
      g14     ENABLE   DOWN  -----   ---
    g15     ENABLE   DOWN  -----   ---
    g16     ENABLE   UP    10H     Off
    and ping shows what I expect:
    64 bytes from 192.168.0.36: icmp_seq=353 ttl=128 time=5.918 ms
    64 bytes from 192.168.0.36: icmp_seq=354 ttl=128 time=6.675 ms
    64 bytes from 192.168.0.36: icmp_seq=355 ttl=128 time=8.052 ms
    64 bytes from 192.168.0.36: icmp_seq=356 ttl=128 time=5.430 ms
    64 bytes from 192.168.0.36: icmp_seq=357 ttl=128 time=6.763 ms
    64 bytes from 192.168.0.36: icmp_seq=358 ttl=128 time=7.861 ms
    64 bytes from 192.168.0.36: icmp_seq=359 ttl=128 time=9.996 ms
    64 bytes from 192.168.0.36: icmp_seq=360 ttl=128 time=5.526 ms
    64 bytes from 192.168.0.36: icmp_seq=361 ttl=128 time=6.374 ms
    64 bytes from 192.168.0.36: icmp_seq=362 ttl=128 time=4.750 ms
    64 bytes from 192.168.0.36: icmp_seq=363 ttl=128 time=2.305 ms
    64 bytes from 192.168.0.36: icmp_seq=364 ttl=128 time=4.748 ms
    64 bytes from 192.168.0.36: icmp_seq=365 ttl=128 time=7.279 ms
    64 bytes from 192.168.0.36: icmp_seq=366 ttl=128 time=6.359 ms
    64 bytes from 192.168.0.36: icmp_seq=367 ttl=128 time=6.536 ms
    64 bytes from 192.168.0.36: icmp_seq=368 ttl=128 time=8.089 ms
    64 bytes from 192.168.0.36: icmp_seq=369 ttl=128 time=8.797 ms
    So why is this broken? Is it a firmware issue or a hardware issue?  The firmware I'm using is I believe the latest though it looks rather old:
      Boot Version:          1.0.1 (Date:  11-Jun-2006, Time:  18:43:59)
      Software Version:      1.2.2b (Date:  28-Feb-2008, Time:  16:47:37)
      Hardware Version:      00.03.00
    If this affects me it's likely to affect others and I really wanted to buy the switch to add to the number of "managed ports" I have. This current behaviour is rather disappointing and I would have hoped that perhaps a firmware upgrade would solve this, or the documentation would be clearer that some devices do not work properly (auto-negotiation seems to be rather a troublesome subject).  Is such a fix available?

  • How to solve illustrator cs6 save as cs5 problem about the stroke(when the stroke with clipping mask and color is gradient, save as cs5 will change to embed ).

    how to solve illustrator cs6 save as cs5 problem about the stroke(when the stroke with clipping mask and color is gradient, save as cs5 will change to embed ).

    Because it was not possible to apply a gradient to a stroke in CS5. When you open the file in CS5, it is reduced to something that can be rendered in CS5.

  • I want a solution to my problem and i hope to see any number to contact you for information i'm from saudi arabia and the problem has not been solved so far and i sent my problem via a Email twice before

    I want a solution to my problem and i hope to see any number to contact you for information i'm from saudi arabia and the problem has not been solved so far and i sent my problem via a Email twice before

    Most of the people on these forums, including myself, are fellow users - you aren't talking to iTunes Support here.
    Have you contacted iTunes Support as was suggested on your duplicate posts :
    https://discussions.apple.com/message/22178793#22178793
    https://discussions.apple.com/message/22178411#22178411

  • I bought a new iphone 4s and I have a problem with the service. How can it be solved? the SIM card is new and was working perfect withe iPhone 4G

    I bought a new iphone 4s and I have a problem with the service. How can it be solved? the SIM card is new and was working perfect withe iPhone 4G

    Under the answer you want to mark as correct you should see a box that says Correct with a green symbol to the left and a box with Helpful with an orange star to the left. Click on the one you want.
    And thanks for thinking about that, it is appreciated.

  • How do I investigate and solve Pages, Notes, Mail intermittent 'offline' and failure to synchronise problems with Mountain Lion after waking from Sleep

    When I wake up my iMac after sleep, i get a variety of intermittent - but mostly FREQUENT and FRUSTRATING problems including:
    Notes app is offline - as stated by a message in the window bar. If I close Notes and reopen, the app appears to be online. However, Notes does NOT update with items I know are on my iPad or in the web iCloud. Furthermore, if I create a new note on my iMac, the new Note does not upload to iCloud. This is IRRITATING!
    Pages and Numbers - similar situation. I can edit a Pages or Numbers document on my iMac (stored on the iCloud). But then the Pages doc doesn't ALWAYS get uploaded to the iCloud. Then I end up with conflicted versions of the file in the cloud, my iPad, and the two iMacs I use. Then I get CONFUSED and FRUSTRATED. For example, consider these steps:
    Open Pages on my iMac, edit an iCloud file, then save and close file
    Pages/File/Open/iCloud - I note in the iCloud file list the edited file has a little 'cloud' icon against its name. From experience this warns me of TROUBLE - namely that the file has NOT yet been uploaded to the iCloud. However, I just checked the new Beta iCloud on the web, and to my surprise, the file edited on my iMac is apparently in the icloud. But now, I edit the iCloud version, and the changes DO NOT appear on my iMac pages version. OK I realise its in Beta version...
    So now, I open my iPad, open Pages. I note the iCloud version of my edited document updates to my iPad, as indicated by a blue download line. 'It just works' as Steve Jobs claimed at Apple Developers Conference a couple of years back. Again, the edited version form my iPad is now 'up in the cloud' correctly....
    Oh - and now mysteriously the Pages version on my Imac has become synchronised with my iPad/iCloud version! Luck ... but that's about all I can say. It doesn't always happen. I'm LUCKY today.
    Meanwhile, the Note I created on my iMac (Item 1 above) has still not yet appeared on my iPad or iCloud... even though I HOPE it would be given that Pages on my iMac, iPad and iCloud are chatting nicely now! The Note says it's in my iCloud - but  NOT. Similarly, notes updated or added on my iPad, which appear in iCloud, are NOT on my iMac.
    Mail - last but NOT LEAST! and MOST INFURIATING!!! My Gmail, Vodafone NZ and Orcon accounts (in Mail) are all active and receiving after the night's sleep. However, my iCloud mail account has the dreaded offline.
    The message on Mail is "There may be a problem with the mail server or network. Verify the settings for account “ICloud - [email protected]” or try again. The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993." Despite the message, mail was received this morning at 8:59 am ... some time before I woke-up my computer (a late start this morning).
    If I sent an email FROM my .me iCloud account TO my Vodafone account, the message whooshes away, it's in my SENT box. But it doesn't get delivered to my Vodafone account on my iMac Mail, or anywhere else, Despite the message being listed in my 'Sent' mailbox!!!
    In contrast, a message sent from my Gmail account to my Vodafone account (in Mail) gets sent and received almost instantly on  my iMac and iPad.
    All of the above mishaps are extremely frustrating, as I rush off from working on my iMac at home, get to my iMac at work and find documents I have been updating on my home iMac not available correctly on my work iMac ... or even my iPad. I expect these things from Apple to 'just work'. Furthermore, emails I THINK I have sent (as indicated by them appearing in the Sent folder on my home iMac) ... have not actually been despatched.
    Frankly, I can no longer rely or recommend the Apple iCloud stuff, so I am converting more and more to relying on DropBox and Google.
    These problems only became apparent since I updated to one of the Mountain Lion versions... I can't say when.
    Oh - if I shutdown and restart the computer my Mail works OK. Guess what, I don't want to do that each time I want to use Mail!
    Technicals:
    My iMac is connected by Ethernet cable to my Apple TimeCapsule. The TimeCapsule is connected by Ethernet cable to my Orcon Genius Modem.
    Obviously, my internet connection is A-OK, as I am able to use Firefox to make this posting!
    Mountain Lion 10.8.4
    iMac 27 inch, mid 2010, Intel Core i5 16 Gb

    I've returned to my sleeping iMac after a few days away. Tis time, ALL MAIL accoiunts are offline. I will follow you next set of instructions. In the meantime, here is the DETAIL from MAIL CONNECTION DOCTOR:
    LevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    19.10827 STATUS [Gmail]/Trash (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.179 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    20.10827 STATUS INBOX (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.202 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    21.10827 STATUS "Sent Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.226 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    22.10827 STATUS "Deleted Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    READ Sep 30 08:35:11.254 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/All Mail" (HIGHESTMODSEQ 561701 UIDNEXT 1666 UNSEEN 105)
    13.10827 OK Success
    READ Sep 30 08:35:11.494 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Drafts" (HIGHESTMODSEQ 561701 UIDNEXT 1 UNSEEN 0)
    14.10827 OK Success
    READ Sep 30 08:35:11.514 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Important" (HIGHESTMODSEQ 561701 UIDNEXT 731 UNSEEN 8)
    15.10827 OK Success
    * STATUS "[Gmail]/Sent Mail" (HIGHESTMODSEQ 561701 UIDNEXT 532 UNSEEN 2)
    16.10827 OK Success
    * STATUS "[Gmail]/Spam" (HIGHESTMODSEQ 561701 UIDNEXT 16 UNSEEN 2)
    17.10827 OK Success
    * STATUS "[Gmail]/Starred" (HIGHESTMODSEQ 561701 UIDNEXT 19 UNSEEN 0)
    18.10827 OK Success
    * STATUS "[Gmail]/Trash" (HIGHESTMODSEQ 561701 UIDNEXT 546 UNSEEN 0)
    19.10827 OK Success
    * STATUS "INBOX" (HIGHESTMODSEQ 561701 UIDNEXT 603 UNSEEN 64)
    20.10827 OK Success
    * STATUS "Sent Messages" (HIGHESTMODSEQ 561701 UIDNEXT 138 UNSEEN 0)
    21.10827 OK Success
    * STATUS "Deleted Messages" (HIGHESTMODSEQ 561701 UIDNEXT 89 UNSEEN 0)
    22.10827 OK Success
    WROTE Sep 30 08:35:11.537 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    23.10827 IDLE
    READ Sep 30 08:35:11.927 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    + idling
    READ Sep 30 08:35:15.472 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    220 st11p00mm-asmtp002.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013))
    WROTE Sep 30 08:35:24.784 [kCFStreamSocketSecurityLevelNone]  -- host:mail.orcon.net.nz -- port:25 -- socket:0x7fc3161a1b00 -- thread:0x7fc315d05050
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:24.822 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x7fc316e72a70 -- thread:0x7fc31850bec0
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:34.080 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    EHLO [10.1.1.4]
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316fc30e0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc31a6fa8a0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316197890
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316e813d0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0350
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3185c0410
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315ded870
    INITIATING CONNECTION Sep 30 08:35:47.193  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:35:47.198  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:35:47.377  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31617f290
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31615a390
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e3bbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e0cfa0
    INITIATING CONNECTION Sep 30 08:36:40.368  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:36:40.403  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.412  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.565  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.595  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.633  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.687  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.708  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.729  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3183339e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3186f07e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315a9b630
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172f6e70
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31616b9d0
    INITIATING CONNECTION Sep 30 08:37:33.323  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.336  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:37:33.462  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.463  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.509  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.528  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.557  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.624  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.646  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:38:26.315  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31686fa30
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316fcc7d0
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc318521490
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e81b30
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316fdf410
    INITIATING CONNECTION Sep 30 08:38:26.318  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d3a890
    INITIATING CONNECTION Sep 30 08:38:26.320  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.495  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.538  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.591  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.619  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.642  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.666  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:39:19.257  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31662a980
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3182e6150
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31605c330
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3184b79c0
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31658f5b0
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3160d8c80
    INITIATING CONNECTION Sep 30 08:39:19.265  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316073530
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.420  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.457  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.505  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.552  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.573  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:40:11.346  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3161c6e50
    INITIATING CONNECTION Sep 30 08:40:11.347  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316becee0
    INITIATING CONNECTION Sep 30 08:40:11.348  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31679c620
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3144ad030
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc3158e5b50
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:40:11.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315c576d0
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.548  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.568  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.597  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.638  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.660  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.683  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:41:06.173  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318297540
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc314144080
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d435e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3167306a0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31680f3e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:41:06.197  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31671e630
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.376  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.396  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.431  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.475  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.503  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.527  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:59.159  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e16c90
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3161e71f0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3170d94c0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3174bc990
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31820b7d0
    INITIATING CONNECTION Sep 30 08:41:59.174  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162884e0
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.344  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.409  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.430  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.450  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:42:51.209  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31a613830
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3168ae8d0
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3161d6110
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315de6190
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316482400
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:42:51.224  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3159e76e0
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.402  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.421  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.466  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.492  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.514  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.536  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc315d40d90
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc315ad1930
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc316c27e30
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315adf230
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d49010
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159a1ea0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc318691eb0
    INITIATING CONNECTION Sep 30 09:43:23.250  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e1b2d0
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.427  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.524  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.547  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.574  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 10:06:17.592  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:17.596  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3174e7bd0
    INITIATING CONNECTION Sep 30 10:06:17.598  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315e08640
    INITIATING CONNECTION Sep 30 10:06:18.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.483  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318462600
    INITIATING CONNECTION Sep 30 10:06:19.539  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162d4270
    INITIATING CONNECTION Sep 30 10:06:19.564  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:19.582  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.653  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.725  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.747  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:07:19.496  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.523  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3144bad30
    INITIATING CONNECTION Sep 30 10:07:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.534  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172b7640
    INITIATING CONNECTION Sep 30 10:07:19.550  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315cbb960
    INITIATING CONNECTION Sep 30 10:07:19.626  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315842910
    INITIATING CONNECTION Sep 30 10:07:19.665  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.715  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.805  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.854  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.892  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.915  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:08:19.527  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.553  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3162e8510
    INITIATING CONNECTION Sep 30 10:08:19.555  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315ac9950
    INITIATING CONNECTION Sep 30 10:08:19.564  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.582  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3146b1020
    INITIATING CONNECTION Sep 30 10:08:19.685  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3163d82c0
    INITIATING CONNECTION Sep 30 10:08:19.705  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.756  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.800  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.852  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.876  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.898  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0

  • Git/svn/cvs "versions"

    Hi,
    on the AUR, it looks like when you upload a package that already existed (but another version) the other package gets replaced by the newly uploaded one.  This seems reasonable because usually people upload a newer version and the older one is not needed anymore.
    But for git/svn/cvs "versions" this raises a problem: When dealing with 'bleeding edge' packages we usually want to keep the 'stable release' packages as well, but this doesn't work:  when package foo v1 exists and you upload foo-git it will also replace.
    I see that most people solve this problem by giving a package a different name instead of another version, eg the package becomes foo-git with version <current date>, which doesn't replace foo version 1.
    1) Is there any reason for the <current date> version?  Or is this just because the version variable cannot be empty?  I don't see much semantic meaning in a version like that, because the user will build the package himself anyway (so he will build the _current_ latest version, not the one dated from the version string of the packagename), at least for packages in unsupported.
    2) Isn't this more a workaround than a solution?  I mean, isn't having different package names a bit ugly because it's actually the same software, just another version? (eg the git/svn/cvs part should be in the version string, not the package name)
    This is a rather theoretical subject (especially question 2), and in true Arch spirit I do think it's better to have a workaround that is simple and works just fine then having the 'theoretically correct' but more complicated solution.
    OTOH, assuming agreement with me:  I think it's easy to the implement the 'correct way':   Basically the AUR code should just check if the version of the package matches a knows VCS system ('git','svn',...) and allow it as an additional package, otherwise replace the previous package.  (and if you upload foo-git and foo-git exists already, also replace it of course)

    I think there are some misunderstandings in this thread -- maybe on my side.
    To be clear: $pkgname, $pkgver and $pkgrel are required fields in a PKGBUILD. Since there is no real version number in packages that are build upon a VCS, often the date is taken as $pkgver (but e.g. svn gives a revision number apart from the date, so that s taken instead). So for example in tuxpaint-cvs-20081116-1, tuxpaint-cvs is the $pkgname, 20081116 is the $pkgver (when you check out CVS packages, the current date of last upstream upload is given as version) and 1 is the $pkgrel (not of much use here). Uploading a tarball for tuxpaint-cvs will not delete an existing tarball for tuxpaint, since tuxpaint-cvs is another name than tuxpaint. If you some day later download the tarball for tuxpaint-cvs, makepkg will generate a package with the current date as $pkgver, unless you say makepkg --holdver, in which case it would take the upload date as $pkgver.
    Last edited by Stefan Husmann (2008-11-16 19:17:51)

Maybe you are looking for