RE: setup all ok now....
> -Original Message- > From: Gerrit P. Haase [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 28, 2002 7:54 AM > There is no checking whether the package with the correct > size is already there. Gerrit, such checking IS is in place, or I'd see the same behaviour. You seem to have identified how to reproduce a bug, and I will be trying to get the same result - which I can then correct - later today. Rob
Re: setup all ok now....
Pavel, Mittwoch, 27. März 2002 21:29:08, du schriebst: > Hello Gerrit, > Wednesday, March 27, 2002, 3:25:56 PM, you wrote: > [snip] GPH>> Now I got mean and fetched some packages (category test), download only. GPH>> It offers me automake-1.6 and tetex and some others. GPH>> I didn't changed the selection and setup.exe fetched the packages. GPH>> Now I looked into the tetex directory: please see the attached GPH>> screenshot. tetex-beta-20001218-4 was fetched though I have GPH>> the package already there! Note that I have already fetched it GPH>> some weeks ago but never installed it. GPH>> Now I have two packages there: GPH>> tetex-beta-20001218-4.tar.bz2.tmp and GPH>> tetex-beta-20001218-4.tar.bz2 GPH>> Is there a chance that I can tell setup.exe what is already present GPH>> in the repository? Shouldn't be there some little tool which parses GPH>> the repository and makes a list of all locally present packages? > I noticed this a while ago also but wasnt able to reproduce it cleanly > again so I haven't reported it. > Do you have a mix from the old contrib + latest dir and the new mirror > named subdirectories ? I fetched only the setup.ini script at the first run. Then I moved my contrib & latest directories where all the stuff is in under the new created subdirectory. The fresh downloads went into the right places as I expected. It happens if you: 1. Have tetex-current installed 2. Have already downloaded tetex-test 3. Have choosen radio button 'Exp' & start another download Or: 1. Have tetex-test installed 2. Have already downloaded tetex-current 3. Have choosen radio button 'Curr' & start another download Tetex gets downloaded again and again and again and again... (tetex-current now two times for me today;) $ ls -l total 33722 -r-xr-xr-x1 Administ Kein 307 Jan 30 05:48 md5.sum* -r-xr-xr-x1 Administ Kein 412 Jan 30 05:45 setup.hint* -r-xr-xr-x1 Administ Kein 6225385 Jan 7 19:36 tetex-beta-20001218-1-src.tar.gz* -r-xr-xr-x1 Administ Kein 4248088 Jan 7 19:36 tetex-beta-20001218-1.tar.gz* -rwxrwxrwx1 Administ Kein 4136960 Mar 27 21:42 tetex-beta-20001218-1.tar.gz.tmp* -r-xr-xr-x1 Administ Kein 5038651 Jan 9 01:50 tetex-beta-20001218-2-src.tar.bz2* -r-xr-xr-x1 Administ Kein 3177419 Jan 9 04:08 tetex-beta-20001218-2.tar.bz2* -r-xr-xr-x1 Administ Kein 5040669 Jan 23 03:35 tetex-beta-20001218-4-src.tar.bz2* -r-xr-xr-x1 Administ Kein 3329878 Jan 23 07:03 tetex-beta-20001218-4.tar.bz2* -rwxrwxrwx1 Administ Kein 3329878 Mar 27 15:08 tetex-beta-20001218-4.tar.bz2.tmp* The second time the first tetex-beta-20001218-1.tar.gz.tmp got clobbered. To reproduce, just run setup on a repository tree where all the packages are already at their place, *every* package gets downloaded again. (E.g. if you have the current version of all packages installed and already downloaded the test versions of these packages too, then just click on the 'test' radio button and you'll see the setup.exe chooses all the uninstalled test packages and loads them down). There is no checking whether the package with the correct size is already there. Gerrit -- =^..^=
Re: setup all ok now....
Robert, Mittwoch, 27. März 2002 15:15:36, du schriebst: > I think we've done it. So Chuck, feel free to break everyone who's > lagging behind :}.. Hmmm, I'm not sure... I tried the first time today. At first I let setup just fetch the setup.ini files from several mirrors to see this feature. Nice;) I moved my repository below my favorite mirror dir. Now I got mean and fetched some packages (category test), download only. It offers me automake-1.6 and tetex and some others. I didn't changed the selection and setup.exe fetched the packages. Now I looked into the tetex directory: please see the attached screenshot. tetex-beta-20001218-4 was fetched though I have the package already there! Note that I have already fetched it some weeks ago but never installed it. Now I have two packages there: tetex-beta-20001218-4.tar.bz2.tmp and tetex-beta-20001218-4.tar.bz2 Is there a chance that I can tell setup.exe what is already present in the repository? Shouldn't be there some little tool which parses the repository and makes a list of all locally present packages? Gerrit -- =^..^= tetex_wrong_download.png Description: PNG image
Re: setup all ok now....
Christopher Faylor wrote: > On Wed, Mar 27, 2002 at 03:15:53PM +1100, Robert Collins wrote: > >>I think we've done it. So Chuck, feel free to break everyone who's >>lagging behind :}.. >> > > Shouldn't we wait a day or two and let the new setup.exe work its > way through the system? don't worry -- I saw the invisible tags. I won't do anything rash. --Chuck
RE: setup all ok now....
> -Original Message- > From: Christopher Faylor [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 27, 2002 3:20 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: setup all ok now > > > On Wed, Mar 27, 2002 at 03:15:53PM +1100, Robert Collins wrote: > >I think we've done it. So Chuck, feel free to break everyone who's > >lagging behind :}.. > > Shouldn't we wait a day or two and let the new setup.exe work > its way through the system? I thought I saw one problem > mentioned today but I wasn't sure if it was the new setup.exe > or the old. I think that waiting a day or two is essential, because otherwise Chuck's packages will cause havoc. I forgot to avoid the use of sarcasm - sorry. > And then there's that twice (thrice?) reported bug where > setup.exe "accidentally" create a separate mirror directory. > Don't you hate it when your code creates additional directory > levels without your consent? > :-) Lol. Yeah, we should look at that. I've some ideas about random rude names we could add! Seriously though, I don't' recall bug reports, just many 'is this intentional', and 'will it use the old stuff', and 'how do I downgrade'. Rob
Re: setup all ok now....
On Wed, Mar 27, 2002 at 03:15:53PM +1100, Robert Collins wrote: >I think we've done it. So Chuck, feel free to break everyone who's >lagging behind :}.. Shouldn't we wait a day or two and let the new setup.exe work its way through the system? I thought I saw one problem mentioned today but I wasn't sure if it was the new setup.exe or the old. And then there's that twice (thrice?) reported bug where setup.exe "accidentally" create a separate mirror directory. Don't you hate it when your code creates additional directory levels without your consent? :-) cgf
