Re: Vacation from the Subversion project

[kf...@collab.net]

"Jostein Chr. Andersen" <jo...@josander.net> writes:
> I have a problem: I'm over worked and I'm hitting the wall. The result
> is that I have to step back and find my power again. I will probably
> not have some real quiet time before the New Year 2005/2006.

Completely understood.

> I can, if wanted, continue to make the Windows Installer, but I will
> not develop it further at the moment.
> 
> If it's a big demand to develop the installer further, then I can try
> to get some help from the Inno Setup Community. I think they are eager
> to help and they are dealing with people's demands of an installer on
> daily bases. Branko and a lot of the people who's on the dev list are
> capable to do any needed work as well. The scripting language of Inno
> Setup is an object oriented Pascal, known by many people, very similar
> to Delphi.
> 
> Also, I ask for help to get rid of the branches I made and/or merge
> them into their respective release branches; I don't have nerves to
> even look at them in a browser at the moment.

Thanks for all your work so far!

Unless someone's going to pick up those branches and work on them
actively, I suggest we just remove them.  They can always be restored
later, after all.

Jostein, it's these two, right?

   innosetup-hsuninsfix-4x-1.1.x/
   innosetup-hsuninsfix-5x-1.2.x/

> I will monitor the lists and the #svn*'s and respond and participate
> when I feel for it. However: I will try to keep my heartbeat frequency
> below 60 bpm's as much as possible.

Good luck!

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Vacation from the Subversion project

["Jostein Chr. Andersen" <jo...@josander.net>]

On Monday 23 May 2005 22.01, kfogel@collab.net wrote:
...
> In the trunk, it's 'windows-innosetup' instead of 'win32-innosetup'.
> Should I make trunk naming reflect branch?  Or just manually adjust
> the patch to apply to trunk, which would be equally easy.  Let me
> know.  I'm happy to take care of it, just need a little guidance.

The name "windows-innosetup" is the right one for the trunk and the 
future. I changed the name to that because the installer system doesn't 
care if its 32 or 64 bit. The win32-innosetup name has never made any 
sense here.


Jostein


-- 
http://www.josander.net/en/contact/

Re: Vacation from the Subversion project

[kf...@collab.net]

"Jostein Chr. Andersen" <jo...@josander.net> writes:
> > Karl: The 1.2.x branch should probably just be committed to trunk
> > (there have been no changes to the files concerned since 1.2.x
> > forked). At that point, the existing branch becomes a standard
> > temporary backport branch. (Branch necessary due to some renaming on
> > trunk).
> 
> Agree, +1 on committing it to the trunk. The uninstall capabilities of 
> the Windows installer is broken without it. This fixes is already 
> included in svn-1.2.0-rc4-setup.exe (had to do what it takes in order to 
> deliver a working installer) and everyone seems to be happy about it; I 
> don't know how many downloads the rc4 got (the stats.tigris.org is not 
> updated anymore), but it's probably many thousands; in other words: 
> tried and tested.

Okay.  I tried to do the merge, and got this error:

   $ svn info
   [...]
   URL: http://svn.collab.net/repos/svn/trunk
   [...]
   $ svn merge -r14707:14716 \
     http://svn.collab.net/repos/svn/branches/innosetup-hsuninsfix-5x-1.2.x .
   Skipped missing target: 'packages/win32-innosetup/svn.iss'
   Skipped missing target: 'packages/win32-innosetup'   
   $ 

In the trunk, it's 'windows-innosetup' instead of 'win32-innosetup'.
Should I make trunk naming reflect branch?  Or just manually adjust
the patch to apply to trunk, which would be equally easy.  Let me
know.  I'm happy to take care of it, just need a little guidance.

Thanks,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Vacation from the Subversion project

["Jostein Chr. Andersen" <jo...@josander.net>]

On Monday 23 May 2005 20.26, Max Bowsher wrote:
> kfogel@collab.net wrote:
...
> > Unless someone's going to pick up those branches and work on them
> > actively, I suggest we just remove them.  They can always be
> > restored later, after all.
> >
> > Jostein, it's these two, right?
> >
> >   innosetup-hsuninsfix-4x-1.1.x/
> >   innosetup-hsuninsfix-5x-1.2.x/

Yes, this is the ones, but additionally, I have some comments to Max' 
posting below:

> >> I will monitor the lists and the #svn*'s and respond and
> >> participate when I feel for it. However: I will try to keep my
> >> heartbeat frequency below 60 bpm's as much as possible.
>
> Jostein: Without doing any further work on the branches, could you
> comment on whether you did not +1 the changes in STATUS yourself
> because you were uncertain about their correctness, or just because
> you didn't realize you could vote?

I think it was because I forgot it under the stress and the noise or 
something. I have voted for my own items in the STATUS file before if i 
recall it right. Right now, I don't want to even touch the Subversion 
repository with latex glows and a "read only capable subversion client" 
if such a thing exists.

> Also, is there any further description of what exactly the bug that
> these changes fix is - perhaps somewhere in the mail archives? If you
> got any information about the bug solely in private email, could you
> post details to the list?

It's from one or two complaints on the user list. It was the author of 
the the extended uninstall program (UninsHs), which adds" add/repair" 
capabilities to the installation system that emailed me the fixes 
(independent of the postings on the user list).

The problem was that the UninsHs (which is called from the start menu or 
the controlpanel's add/remove programs entry) often could not find the 
installer's remove program (unins000.exe) when the user's decision was 
to remove the Subversion installation.


> Karl: The 1.2.x branch should probably just be committed to trunk
> (there have been no changes to the files concerned since 1.2.x
> forked). At that point, the existing branch becomes a standard
> temporary backport branch. (Branch necessary due to some renaming on
> trunk).

Agree, +1 on committing it to the trunk. The uninstall capabilities of 
the Windows installer is broken without it. This fixes is already 
included in svn-1.2.0-rc4-setup.exe (had to do what it takes in order to 
deliver a working installer) and everyone seems to be happy about it; I 
don't know how many downloads the rc4 got (the stats.tigris.org is not 
updated anymore), but it's probably many thousands; in other words: 
tried and tested.

Jostein

-- 
http://www.josander.net/en/contact/

Re: Vacation from the Subversion project

[Max Bowsher <ma...@ukf.net>]

kfogel@collab.net wrote:
> "Jostein Chr. Andersen" <jo...@josander.net> writes:
>> Also, I ask for help to get rid of the branches I made and/or merge
>> them into their respective release branches; I don't have nerves to
>> even look at them in a browser at the moment.
>
> Thanks for all your work so far!
>
> Unless someone's going to pick up those branches and work on them
> actively, I suggest we just remove them.  They can always be restored
> later, after all.
>
> Jostein, it's these two, right?
>
>   innosetup-hsuninsfix-4x-1.1.x/
>   innosetup-hsuninsfix-5x-1.2.x/
>
>> I will monitor the lists and the #svn*'s and respond and participate
>> when I feel for it. However: I will try to keep my heartbeat frequency
>> below 60 bpm's as much as possible.

Jostein: Without doing any further work on the branches, could you comment 
on whether you did not +1 the changes in STATUS yourself because you were 
uncertain about their correctness, or just because you didn't realize you 
could vote?

Also, is there any further description of what exactly the bug that these 
changes fix is - perhaps somewhere in the mail archives? If you got any 
information about the bug solely in private email, could you post details to 
the list?

Thanks.


Karl: The 1.2.x branch should probably just be committed to trunk (there 
have been no changes to the files concerned since 1.2.x forked). At that 
point, the existing branch becomes a standard temporary backport branch. 
(Branch necessary due to some renaming on trunk).

The 1.1.x is a branch-only-bugfix, so its existence is not against project 
policy - it is only a two line change, so perhaps we should let it remain in 
STATUS for a while, in the hope that someone will review it?


Max.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org