Re: cvsup/csup servers stale?

Good luck with employing full discombobulation! I think this is the main requirement for _cloud computing_. -- View this message in context: http://freebsd.1045724.n5.nabble.com/cvsup-csup-servers-stale-tp5761290p5761389.html Sent from the freebsd-current mailing list archive at Nabble.com.

Re: cvsup/csup servers stale?

On 11/15/2012 12:58 PM, Eitan Adler wrote: On 15 November 2012 13:47, Ian FREISLICH wrote: Hi Has the svn->cvs exporter died? Or have the cvsup/csup servers been retired as threatened in a previous thread (I might have missed the headsup)? The FreeBSD cluster is undergoing maintenance. In

Re: cvsup/csup servers stale?

On 15 November 2012 13:47, Ian FREISLICH wrote: > Hi > > Has the svn->cvs exporter died? Or have the cvsup/csup servers > been retired as threatened in a previous thread (I might have missed > the headsup)? The FreeBSD cluster is undergoing maintenance. In particular the main machines were rece

Re: cvsup broken on amd64?

On 10/06/2011 01:41, Thomas Mueller wrote: > Anyway, from what I read, csup is better, and I think I can use the same > supfile and same server that I would use for cvsup? Yes. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth

Re: cvsup broken on amd64?

On Wed, Oct 05, 2011 at 03:21:45PM -0700, David O'Brien wrote: > On Fri, Sep 09, 2011 at 06:00:02PM +0300, Kostik Belousov wrote: > > --- libs/m3core/src/thread/POSIX/ThreadPosix.m3.orig2011-09-09 > > 17:58:12.867431639 +0300 > > +++ libs/m3core/src/thread/POSIX/ThreadPosix.m3 2011-09-

Re: cvsup broken on amd64?

> cvsup is a port, so you would need to install that to have cvsup. csup > and cvsup are totally different code bases in different languages. > (csup is C and cvsup is Modula-3.) You probably want to install cvsup > as a package as installing the port also requires building all of the > Modula-3 co

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 06:00:02PM +0300, Kostik Belousov wrote: > --- libs/m3core/src/thread/POSIX/ThreadPosix.m3.orig 2011-09-09 > 17:58:12.867431639 +0300 > +++ libs/m3core/src/thread/POSIX/ThreadPosix.m3 2011-09-09 > 17:58:30.380428486 +0300 > @@ -180,7 +180,7 @@ >pausedThreads : T

Re: cvsup broken on amd64?

On Wed, Oct 5, 2011 at 1:34 AM, Thomas Mueller wrote: >> Hi all, > >> I've committed this to -head. > >> I'd appreciate it if csup users would give this a thorough testing and >> report back to the list with results. >> I won't submit this as a merge candidate this to stable/9 without a >> whole l

Re: cvsup broken on amd64?

> Hi all, > I've committed this to -head. > I'd appreciate it if csup users would give this a thorough testing and > report back to the list with results. > I won't submit this as a merge candidate this to stable/9 without a > whole lot of testing. :) > Thanks, > Adrian I am now in 9.0-

Re: cvsup broken on amd64?

Hi all, I've committed this to -head. I'd appreciate it if csup users would give this a thorough testing and report back to the list with results. I won't submit this as a merge candidate this to stable/9 without a whole lot of testing. :) Thanks, Adrian ___

Re: cvsup broken on amd64?

On Tue, Oct 4, 2011 at 2:19 AM, Adrian Chadd wrote: > On 4 October 2011 05:53, Maxime Henrion wrote: > >> Great, that's a relief. I knew the pthread library was free to wake a >> thread up even if it hadn't been signaled, which is why one always has >> to call pthread_cond_wait() inside of a whil

Re: cvsup broken on amd64?

On 4 October 2011 05:53, Maxime Henrion wrote: > Great, that's a relief. I knew the pthread library was free to wake a > thread up even if it hadn't been signaled, which is why one always has > to call pthread_cond_wait() inside of a while() loop checking for the > condition, but wasn't sure abou

Re: cvsup broken on amd64?

On Mon, Oct 3, 2011 at 11:30 PM, Jilles Tjoelker wrote: > On Mon, Oct 03, 2011 at 06:15:41PM +0200, Maxime Henrion wrote: >> Knowing all that, what's happening seems quite clear. If >> fixups_close() is called while there was still fixup requests pending, >> those should be processed by the detail

Re: cvsup broken on amd64?

On Mon, Oct 03, 2011 at 06:15:41PM +0200, Maxime Henrion wrote: > Knowing all that, what's happening seems quite clear. If > fixups_close() is called while there was still fixup requests pending, > those should be processed by the detailer thread before it returns. > Subsequent fixups_get() call sh

Re: cvsup broken on amd64?

On Mon, Sep 19, 2011 at 8:26 AM, Adrian Chadd wrote: > 2011/9/19 Alexander Zagrebin : > >> I've tried this patch. Now csup "hangs" before handling fixups. >> So there is no message "Applying fixups..." at all. > > Wow. Hm. Where's the author when one needs them.. Well that's quite a strange coinc

Re: cvsup broken on amd64?

2011/9/19 Alexander Zagrebin : > I've tried this patch. Now csup "hangs" before handling fixups. > So there is no message "Applying fixups..." at all. Wow. Hm. Where's the author when one needs them.. Adrian ___ freebsd-current@freebsd.org mailing lis

RE: cvsup broken on amd64?

Hi! > So I've taken a look at the csup source. > > The problem here is the updater thread setting the "closed" state > (fixups_closed()) before calling updater_batch() again to handle > fixups. > > Checking for size != 0 at that point may not be valid at the list size > may actually be 0 for a s

Re: cvsup broken on amd64?

On Sun, Sep 18, 2011 at 02:46:24PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >Did you saw the message with the patch for tzcode I mailed to you ? > > Mmmh... no didn't reached my mailbox - can you resend it please? See the "Segfault in libthr.so on 9.0-BETA2 (with stunnel FW

Re: cvsup broken on amd64?

Kostik Belousov wrote: Did you saw the message with the patch for tzcode I mailed to you ? Mmmh... no didn't reached my mailbox - can you resend it please? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/free

Re: cvsup broken on amd64?

Ah, you're the one with the csup problem. Would you mind trying csup again, and if it doesn't work, try this patch: Index: updater.c === --- updater.c (revision 224905) +++ updater.c (working copy) @@ -240,9 +240,9 @@ *

Re: cvsup broken on amd64?

On Sun, Sep 18, 2011 at 12:22:53PM +0200, Oliver Lehmann wrote: > > Adrian Chadd wrote: > > >So I've taken a look at the csup source. > > > >[...] > > > >What about this patch: > > > >[...] > > > >Oliver, would you please try that? > > I have a problem with cvsup, not csup - Alexander mentioned

Re: cvsup broken on amd64?

Adrian Chadd wrote: So I've taken a look at the csup source. [...] What about this patch: [...] Oliver, would you please try that? I have a problem with cvsup, not csup - Alexander mentioned a csup problem. ___ freebsd-current@freebsd.org maili

Re: cvsup broken on amd64?

Hi, So I've taken a look at the csup source. The problem here is the updater thread setting the "closed" state (fixups_closed()) before calling updater_batch() again to handle fixups. Checking for size != 0 at that point may not be valid at the list size may actually be 0 for a short period of t

Re: cvsup broken on amd64?

On Thu, Sep 15, 2011 at 9:30 AM, Garrett Cooper wrote: > On Thu, Sep 15, 2011 at 8:19 AM, Adrian Chadd wrote: >> On 15 September 2011 18:05, Mark Linimon wrote: Usually rather quite later than sooner. >>> >>> A perfect opportunity for src committers to dive in and make a >>> difference :-)

Re: cvsup broken on amd64?

On Thu, Sep 15, 2011 at 8:19 AM, Adrian Chadd wrote: > On 15 September 2011 18:05, Mark Linimon wrote: >>> Usually rather quite later than sooner. >> >> A perfect opportunity for src committers to dive in and make a >> difference :-) > > I hate you. :) > > Ok. Some third person test/verify that t

Re: cvsup broken on amd64?

On 15 September 2011 18:05, Mark Linimon wrote: >> Usually rather quite later than sooner. > > A perfect opportunity for src committers to dive in and make a > difference :-) I hate you. :) Ok. Some third person test/verify that this patch (a) does what it's supposed to do, and (b) is correct, a

Re: cvsup broken on amd64?

> Usually rather quite later than sooner. A perfect opportunity for src committers to dive in and make a difference :-) mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any m

Re: cvsup broken on amd64?

on 15/09/2011 12:16 Alexander Zagrebin said the following: >> Pester the maintainer? > > I've thought that if an opened PR exists, then it have to be > reviewed sooner or later... > Usually rather quite later than sooner. There are about 5000 non-ports PRs and there are only a few dozen active

RE: cvsup broken on amd64?

> Pester the maintainer? I've thought that if an opened PR exists, then it have to be reviewed sooner or later... -- Alexander Zagrebin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubsc

Re: cvsup broken on amd64?

On Wed, Sep 14, 2011 at 11:19 PM, Adrian Chadd wrote: > Pester the maintainer? The maintainer is alumni. -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "fr

Re: cvsup broken on amd64?

Pester the maintainer? Adrian 2011/9/15 Alexander Zagrebin : >> I'm also using cvsup again, due to a problem I had with csup >> back in February >> 2011 >> > 813.html> . >> >> I didn't open a PR; I was under some time pressure and

RE: cvsup broken on amd64?

> I'm also using cvsup again, due to a problem I had with csup > back in February > 2011 > 813.html> . > > I didn't open a PR; I was under some time pressure and cvsup worked. There is a solution of the csup problem: http://www.f

Re: cvsup broken on amd64?

On Fri, 09 Sep 2011 13:47:37 +0200 Oliver Lehmann wrote: > > Kostik Belousov wrote: > > > For start, you should provide the information what exactly is the > > instruction that caused the fault. Show the disassembly from gdb > > for the function that caused the fault. > > Ok, I'm trying. I re

Re: cvsup broken on amd64?

On 09/08/11 14:52, b. f. wrote: I have an Atom 330 with 9.0-BETA2/amd64 installed. I did a pkg_add -r cvsup-without-gui at first after installation. Using cvsup, resulted in a core dump (illegal instruction). I then removed all ports, and installed cvsup-without-gui from source. Started cvsup..

Re: cvsup broken on amd64?

Kostik Belousov wrote: On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote: (gdb) run Starting program: /usr/obj/amd64/usr/ports/net/cvsup-without-gui/work/cvsup-snap-16.1h/client/FBSD_AMD64/cvsup -g /usr/share/examples/cvsup/9-supfile Connected to cvsup.de.FreeBSD.org Updating

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote: > > >>Ok, please do the following: > >>run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do: > >>1. info registers

Re: cvsup broken on amd64?

Kostik Belousov wrote: On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote: Ok, please do the following: run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do: 1. info registers $rsp 2. info program This should print you the pid of the process, then do

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote: > On Fri, Sep 09, 2011 at 04:34:54PM +0200, Oliver Lehmann wrote: > > > > Kostik Belousov wrote: > > > > >On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: > > > > >>(gdb) bt > > >>#0 0x004d24c6 in tzload ()

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 04:34:54PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: > > >>(gdb) bt > >>#0 0x004d24c6 in tzload () > > > >Try to do "disas 0x4d24c6 0x4d24c6+30" from gdb prompt with the loaded >

Re: cvsup broken on amd64?

Kostik Belousov wrote: On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: (gdb) bt #0 0x004d24c6 in tzload () Try to do "disas 0x4d24c6 0x4d24c6+30" from gdb prompt with the loaded core. (gdb) disas 0x4d24c6 0x4d24c6+30 Dump of assembler code from 0x4d24c6 to 0x4d2

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >I do not know, I was curious about 'illegal instruction' signal, > >which would indicate a problem in the compilation environment. > >Now you get segmentation violation, that is usually caused by a bu

Re: cvsup broken on amd64?

Kostik Belousov wrote: I do not know, I was curious about 'illegal instruction' signal, which would indicate a problem in the compilation environment. Now you get segmentation violation, that is usually caused by a bug in the program itself. running it outside gdb still results in an 'illega

Re: cvsup broken on amd64?

On 09/09/11 01:33, Oliver Lehmann wrote: Mike Tancsa wrote: Just curious as to why you need cvsup and not instead use csup that is in the base ? I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a st

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 01:47:37PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >For start, you should provide the information what exactly is the > >instruction that caused the fault. Show the disassembly from gdb > >for the function that caused the fault. > > Ok, I'm trying. I

Re: cvsup broken on amd64?

Kostik Belousov wrote: For start, you should provide the information what exactly is the instruction that caused the fault. Show the disassembly from gdb for the function that caused the fault. Ok, I'm trying. I recompiled cvsup for purpose with -DSTATIC How do I continue from the gdb outpu

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 11:30:46AM +0200, Oliver Lehmann wrote: > > Chris Rees wrote: > > >On 9 September 2011 06:33, Oliver Lehmann wrote: > >>I got used to it in the past 12 years? But this is not realy the question. > >>If it is "BROKEN" it should be marked as BROKEN or there should be a > >

Re: cvsup broken on amd64?

Chris Rees wrote: On 9 September 2011 06:33, Oliver Lehmann wrote: I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a statement that it will not work with FreeBSD 9 on at least amd64 or we will have

Re: cvsup broken on amd64?

On 9 September 2011 06:33, Oliver Lehmann wrote: > > Mike Tancsa wrote: > >> Just curious as to why you need cvsup and not instead use csup that is >> in the base ? > > I got used to it in the past 12 years? But this is not realy the question. > If it is "BROKEN" it should be marked as BROKEN or

Re: cvsup broken on amd64?

Mike Tancsa wrote: Just curious as to why you need cvsup and not instead use csup that is in the base ? I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a statement that it will not work with FreeBSD

Re: cvsup broken on amd64?

> I have an Atom 330 with 9.0-BETA2/amd64 installed. > > I did a pkg_add -r cvsup-without-gui at first after installation. > Using cvsup, resulted in a core dump (illegal instruction). > > I then removed all ports, and installed cvsup-without-gui from source. > Started cvsup... core dump again. > >

Re: cvsup servers broken?

Gavin Atkinson wrote: > On Sat, 2 Jul 2011, Ian FREISLICH wrote: > > Matt wrote: > > > On 07/01/11 09:34, Ian FREISLICH wrote: > > > > It looks like the server is just exiting. I've tested cvsup4 and > > > > cvsup5 as well. Is cvsup deprecated these days or has something > > > > else broken it? >

Re: cvsup servers broken?

On Sat, 2 Jul 2011, Ian FREISLICH wrote: > Matt wrote: > > On 07/01/11 09:34, Ian FREISLICH wrote: > > > It looks like the server is just exiting. I've tested cvsup4 and > > > cvsup5 as well. Is cvsup deprecated these days or has something > > > else broken it? > > > > > Try csup instead of cvsup

Re: cvsup servers broken?

Matt wrote: > On 07/01/11 09:34, Ian FREISLICH wrote: > > It looks like the server is just exiting. I've tested cvsup4 and > > cvsup5 as well. Is cvsup deprecated these days or has something > > else broken it? > > > Try csup instead of cvsup...I've found it works better. Any possibility > of ne

Re: cvsup servers broken?

On 07/01/11 09:34, Ian FREISLICH wrote: Hi I've been seeing this all day: # cvsup -L2 /root/supfile-cvs Parsing supfile "/root/supfile-cvs" Connecting to cvsup6.freebsd.org Connected to cvsup6.freebsd.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collecti

Re: cvsup sites are all at capacity?

I spoke too soon. Suddenly it all works. >It never got above 10 clients before today. How about a few >people switch to my server for regular updates? Thanks. :) > >Regards, >-- >wca Oh, alright! Andrew Lankford ___ [EMAI

Re: cvsup sites are all at capacity?

On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote: > I've tried various cvsup sites (normally cvsup2 or cvsup16 ) > and each site returns this message: > > Rejected by server: Access limit exceeded; try again later > > I've gotten that before but never with all of the hosts out th

Re: cvsup sites are all at capacity?

On Tue, Sep 16, 2003 at 05:11:02PM -0500, Dan Nelson wrote: > In the last episode (Sep 16), Andrew Lankford said: > > I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and > > each site returns this message: > > > > Rejected by server: Access limit exceeded; try again later > > > > I'

Re: cvsup sites are all at capacity?

In the last episode (Sep 16), Andrew Lankford said: > I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and > each site returns this message: > > Rejected by server: Access limit exceeded; try again later > > I've gotten that before but never with all of the hosts out there. > Is eve

Re: cvsup sites are all at capacity?

On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote: > I've tried various cvsup sites (normally cvsup2 or cvsup16 ) > and each site returns this message: > > Rejected by server: Access limit exceeded; try again later > > I've gotten that before but never with all of the hosts out th

Re: cvsup failing with "ASSERT failed"

On Fri, 29 Aug 2003, David Rhodus wrote: > > On Wednesday, August 27, 2003, at 12:48 PM, Peter Wemm wrote: > > Oh, that *is* interesting. I get this 100% of the time when trying to > > run the i386 binary on my amd64 boxes. Hmm. Maybe I dont have an > > emulation > > bug then? > > > > [EMAIL P

Re: cvsup failing with "ASSERT failed"

On Wednesday, August 27, 2003, at 12:48 PM, Peter Wemm wrote: Oh, that *is* interesting. I get this 100% of the time when trying to run the i386 binary on my amd64 boxes. Hmm. Maybe I dont have an emulation bug then? [EMAIL PROTECTED]:46am]~-99> ./cvsup -gL2 cvs-supfile Parsing supfile "cvs-su

Re: cvsup failing with "ASSERT failed"

Ummm, well, when you have a hidden ELF who keeps multiplying all of those ridiculus numbers by 10, of course! ;) It should have been 2GB - oh well. On 27 Aug, Peter Jeremy wrote: > On Tue, Aug 26, 2003 at 11:02:08PM -0500, [EMAIL PROTECTED] wrote: >>A couple of times, now, on both FBSD-5.1-CURR

Re: cvsup failing with "ASSERT failed"

[EMAIL PROTECTED] wrote: > A couple of times, now, on both FBSD-5.1-CURRENT and FBSD-4.8-STABLE whilst > running with 2MB of RAM, cvsup has "croaked" with the following error: > > *** > *** runtime error: > ***ASSERT failed > ***file "/usr/ports/lang/ezm3/work/ezm3-1.0/libs/m3core/src/run

Re: cvsup failing with "ASSERT failed"

On Tue, Aug 26, 2003 at 11:02:08PM -0500, [EMAIL PROTECTED] wrote: >A couple of times, now, on both FBSD-5.1-CURRENT and FBSD-4.8-STABLE whilst >running with 2MB of RAM, cvsup has "croaked" with the following error: Out of interest, how do you get either 4.x or 5.x to run in 2MB? I found running

Re: CVSUP problems

On Thu, 31 Jul 2003 16:09:56 -0700 (PDT), Rus Foster <[EMAIL PROTECTED]> wrote: Kind of.. :-) Where did you learn that 5.x already have the -STABLE branch? We only have -RELEASE and -CURRENT branches right now, but should have - STABLE branch after 5.2 released. So CURRENT_5? No, if you want -CU

Re: CVSUP problems

> > Kind of.. :-) Where did you learn that 5.x already have the -STABLE branch? > We only have -RELEASE and -CURRENT branches right now, but should have - > STABLE branch after 5.2 released. So CURRENT_5? Rus -- www: http://jvds.com | Virtual Servers from just $15/mo MSNM: [EMAIL PROTECTED] |

Re: CVSUP problems

On Thu, 31 Jul 2003 15:57:45 -0700 (PDT), Rus Foster <[EMAIL PROTECTED]> wrote: Hi all I'm trying to pull the 5.1 source with the following cvsup file *default host=cvsup8.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5 *default compress src-all Doing cvsup i

Re: CVSUP

On Sat, 14 Jun 2003, Blaise Takoudjou wrote: > hello, > i make my cvsup last week und cannot install my ports again. > I do cvsup today again but the problem still there. Wenn i "make install > clean" the error says: > > u-2.05b# make install clean > /usr/bin/sed: 1: Syntax error: "(" unexpe

Re: cvsup 06/05/2003 breaks nvidia driver

Thanks for the suggestion about recompiling the nvidia driver, but I do after each kernel compile and install, so that isn't the answer, though not a bad idea. Recompiles of both the Linux-nvidia-port and the standalone-nvidia driver failed, so I am in the process, now, of backing out of everything

Re: cvsup 06/05/2003 breaks nvidia driver

If you started X (by itself) and the screen flickered on and off, then I would suspect that it is being told to use a video mode that your card, or more likely - monitor, won't support. If that is true, then you could be in danger of damaging your monitor. 1) Got all available documentation avail

Re: cvsup 06/05/2003 breaks nvidia driver

After having installed 5.1-RC1, the nvidia driver, and named, are back in full operation. Yeah! On Thu, 5 Jun 2003 [EMAIL PROTECTED] wrote: > Thanks for the suggestion about recompiling the nvidia driver, but I do after > each kernel compile and install, so that isn't the answer, though not a b

Re: cvsup 06/05/2003 breaks nvidia driver

On Thu, 5 Jun 2003, 18:56-0500, [EMAIL PROTECTED] wrote: > Thanks for the suggestion about recompiling the nvidia driver, but I do after > each kernel compile and install, so that isn't the answer, though not a bad > idea. Recompiles of both the Linux-nvidia-port and the standalone-nvidia > driver

Re: cvsup 06/05/2003 breaks nvidia driver

[EMAIL PROTECTED] wrote: I am not on my 5.1-BETA2 system right now, so I don't have any useful details, but after CVSuping /usr/src early 05/06/2003 (after midnight), then build world and recompiling and installing "my" kernel, the nvidia driver "checks out" when X is loaded with a failure to initi

Re: cvsup to RC2

On (22/12/02 13:58), Gernot A. Weber wrote: > it's my first upgrade of a FreeBSD box. So I copied stable-supfile from > /usr/share/examples/cvsup to /etc/cvsup and changed the following line: > > *default release=cvs tag=5.0-RC2 > > When I start cvsup /etc/cvsup it wants to delete all src files.

Re: cvsup weird problem

Fri, Dec 06, 2002 at 13:11:51, osa (Sergey A. Osokin) wrote about "Re: cvsup weird problem": SAO> Any other idea? :-) Remove src/contrib/gcc/INSTALL/ and sup checkouts directory simultaneously, this usually fixes such errors ;) > > > >> Delete src/contrib/gcc/IN

Re: cvsup weird problem

On 2002-12-06 10:05, Sean LeBlanc <[EMAIL PROTECTED]> wrote: > In any case, my installworld doesn't work, and I wonder if that's why. > I did the following: > > make buildworld > make buildkernel > make installkernel > rebooted, > and did mergemaster -p > and make installworld > > as defined in han

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 05:22:50PM +0200, Giorgos Keramidas wrote: > On 2002-12-05 21:33, leafy <[EMAIL PROTECTED]> wrote: > > On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > > > Delete src/contrib/gcc/INSTALL > > > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory no

Re: CVSup Delete failures

Michael Sierchio writes: | Forrest Aldrich wrote: | > FYI, over the last few days, I've been seeing this error while doing a | > CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: | > | > Delete src/contrib/gcc/INSTALL | > Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTA

Re: CVSup Delete failures

eally changes manually > here in the src directories. FWIW, this is a "me too." I cvsup-ed the sources yesterday and got complaints about the same directory. I manually deleted it and re-cvsup-ed and the directory and all its contents were restored as before. Run again and the comp

Re: CVSup Delete failures

Forrest Aldrich wrote: FYI, over the last few days, I've been seeing this error while doing a CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: Delete src/contrib/gcc/INSTALL Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL": Directory not empty If I manually delet

Re: cvsup weird problem [gcc-3.2.1 commit problem?]

On Fri, Dec 06, 2002 at 01:18:57AM +0800, leafy wrote: > On Thu, Dec 05, 2002 at 07:13:23PM +0200, Giorgos Keramidas wrote: > > > Been there, done that - several times :) > > > > Hmmm, try a different cvsup server then. I just updated from > > cvsup.gr.freebsd.org and all seems fine. The files a

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 07:13:23PM +0200, Giorgos Keramidas wrote: > > Been there, done that - several times :) > > Hmmm, try a different cvsup server then. I just updated from > cvsup.gr.freebsd.org and all seems fine. The files are still there, > but nothing breaks... Connected to cvsup.gr.fre

Re: cvsup weird problem

On 2002-12-06 00:14, leafy <[EMAIL PROTECTED]> wrote: > On Thu, Dec 05, 2002 at 05:22:50PM +0200, Giorgos Keramidas wrote: > > Remove your src/contrib/gcc/INSTALL directory and try cvsup'ing again. > > The files in that directory were imported yesterday, and I think that > > David O'Brien didn't me

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 05:22:50PM +0200, Giorgos Keramidas wrote: > > Remove your src/contrib/gcc/INSTALL directory and try cvsup'ing again. > The files in that directory were imported yesterday, and I think that > David O'Brien didn't mean to import them at all: > > Giorgos. > Been there, done

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 06:20:05PM +0300, Sergey A. Osokin wrote: > Updating collection src-all/cvs > Edit src/bin/sh/bltin/echo.1 > Add delta 1.11 2002.12.05.08.49.59 ru > Delete src/contrib/gcc/INSTALL > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > Edit src/lib/libc/ge

Re: cvsup weird problem

On 2002-12-05 21:33, leafy <[EMAIL PROTECTED]> wrote: > On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > > Delete src/contrib/gcc/INSTALL > > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > > > > > It's weird... Remove your src/contrib/gcc/INSTALL dire

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 09:33:45PM +0800, leafy wrote: > On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > > Delete src/contrib/gcc/INSTALL > > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > > > > > It's weird... > > > > Looks like a strange, yesterda

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > Delete src/contrib/gcc/INSTALL > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > > > It's weird... > > Looks like a strange, yesterday i'm successfuly cvsuped my 5.0 box > (in vmware under 4.7-S). > -rw

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 09:21:09PM +0800, leafy wrote: > On Thu, Dec 05, 2002 at 11:25:14AM +0800, JY wrote: > > I did as you suggested and it's still complaining :( > > > > JY > I was cvsupping from cvsup2.freebsd.org. At first it complains about > gcc/INSTALL not being empty, so I manually delet

Re: cvsup weird problem

On Thu, Dec 05, 2002 at 11:25:14AM +0800, JY wrote: > I did as you suggested and it's still complaining :( > > JY I was cvsupping from cvsup2.freebsd.org. At first it complains about gcc/INSTALL not being empty, so I manually deleted everything under it, but not the dir itself. Then I cvsupped: C

Re: CVSup vs inttypes.h,v

Julian Elischer wrote: > Well it's a pitty whoever moved it didn't grep for > it.. my builds fail because of it. It is present as src/include/inttypes.h. You have stale .depend files or are doing something silly like make -DNOCLEAN. peter@daintree[5:45pm]~src-151> find . -type f -print | grep -

Re: CVSup vs inttypes.h,v

Julian Elischer <[EMAIL PROTECTED]> writes: > Well it's a pitty whoever moved it didn't grep for > it.. my builds fail because of it. I did indeed grep for occurences of it and fixed them. The only remaining instance appears in sys/dev/bktr/bktr_core.c which is in a `#if defined(__NetBSD__) || d

Re: CVSup vs inttypes.h,v

Well it's a pitty whoever moved it didn't grep for it.. my builds fail because of it. On Mon, 31 Dec 2001, Mike Makonnen wrote: > It's been moved to the Attic. From what I can gather most of what was in there was >moved to sys/sys/stdint.h and whatever files *it* includes. > > > > Cheers,

Re: CVSup vs inttypes.h,v

In article <[EMAIL PROTECTED]>, Julian Elischer <[EMAIL PROTECTED]> wrote: > > CVSup is refusing to give me a inttypes.h,v in sys/sys > > I sup from cvsup14 as it's very close. > How do I work out where the problem is? Give me some details (supfile + command line), and I'll help you figure it

Re: CVSup vs inttypes.h,v

It's been moved to the Attic. From what I can gather most of what was in there was moved to sys/sys/stdint.h and whatever files *it* includes. Cheers, mikem On Mon, 31 Dec 2001 21:32:17 -0800 (PST) Julian Elischer <[EMAIL PROTECTED]> wrote: > > CVSup is refusing to give me a inttypes.h,v

Re: cvsup-devel port build problem (pm3-base)

John Polstra <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, > Brian Somers <[EMAIL PROTECTED]> wrote: > > I sent John Polstra a similar patch some time ago Any news about > > getting this committed John (P) ? > > There is already an open PR with a patch. I think Mark Murray

Re: cvsup-devel port build problem (pm3-base)

In article <[EMAIL PROTECTED]>, Brian Somers <[EMAIL PROTECTED]> wrote: > I sent John Polstra a similar patch some time ago Any news about > getting this committed John (P) ? There is already an open PR with a patch. I think Mark Murray is working on committing it. I don't have the syste

Re: cvsup-devel port build problem (pm3-base)

I sent John Polstra a similar patch some time ago Any news about getting this committed John (P) ? > Hi, > > I ran into some problems building the cvsup-devel > port. In one of it's dependants, the c file is attempting > to include which is nolonger valid. > > /usr/ports/lang/pm3-bas

Re: CVSup package for -current

On Wed, Sep 12, 2001 at 01:16:14PM -0700, Brooks Davis wrote: > On Wed, Sep 12, 2001 at 09:19:28AM -0700, Adam Kranzel wrote: > > I did not see one annouced by jdp, sorry for the redundancy if > > there is already one available :) > > There are 4.x, 3.5, and 2.2 binaries on jdp's page. Unfortuna

Re: CVSup package for -current

Hi... This is indeed a -current binary, built on -current of september third. I will leave it up just in case someone finds it useful, as disk space is not much of an issue. thanks -Adam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the messag

  1   2   >