Re: setup.exe handles same packages in multiple mirrors badly
Greetings, Corinna Vinschen! >> > So, if anybody wants to take a stab at setup and revamp it, feel free. >> > The only requirements are, it should still be able to utilize the >> > setup.ini file created on cygwin.com, it should still be able to work >> > the mirror list provided by cygwin.com, and it should still provide a >> > GUI and a command line. Everything else is open for renewal. >> >> You might add "should be native application" and "should compile with Cygwin >> provided toolchain". >> Else it'll be an unbearable nightmare to support. > Doesn't that go without saying? Just for completeness. Not everyone is familiar with intricacies of Cygwin's setup. -- WBR, Andrey Repin (anrdae...@yandex.ru) 26.08.2014, <14:48> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe handles same packages in multiple mirrors badly
On Aug 26 13:53, Andrey Repin wrote: > > So, if anybody wants to take a stab at setup and revamp it, feel free. > > The only requirements are, it should still be able to utilize the > > setup.ini file created on cygwin.com, it should still be able to work > > the mirror list provided by cygwin.com, and it should still provide a > > GUI and a command line. Everything else is open for renewal. > > You might add "should be native application" and "should compile with Cygwin > provided toolchain". > Else it'll be an unbearable nightmare to support. Doesn't that go without saying? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpOjipnSz34p.pgp Description: PGP signature
Re: setup.exe handles same packages in multiple mirrors badly
Greetings, Corinna Vinschen! >> If you ask me, Setup is long overdue for a complete replacement. >> It "don't have" so many things other package managers allow, that I don't >> even >> know, where to start. Meta dependencies? Suggestions? Virtual packages? > The problem is not that we don't know this, the problem is, as so often, > that we only have a handful of active developers at all, and nobody > having the time nor inclination to work on setup to keep it ahead of > time. Apology again. :( At 5am brain want only one thing. And it's not "writhing comprehensive posts". I was intent on clarifying your point, but brain said "BED!" and legs followed. > Setup was a wonderful idea, way back when it has been created, but the > vintage charm of its Y2K roots are a bit depressing these days. > So, if anybody wants to take a stab at setup and revamp it, feel free. > The only requirements are, it should still be able to utilize the > setup.ini file created on cygwin.com, it should still be able to work > the mirror list provided by cygwin.com, and it should still provide a > GUI and a command line. Everything else is open for renewal. You might add "should be native application" and "should compile with Cygwin provided toolchain". Else it'll be an unbearable nightmare to support. -- WBR, Andrey Repin (anrdae...@yandex.ru) 26.08.2014, <13:49> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Fwd: setup.exe handles same packages in multiple mirrors badly
> Greetings, Bjorn Kautler! > > > But first things first, it is Bjorn or Bjoern, not Bjorn. :-) > > Apology. My current locale does not include western diacritics. Sure, that is why you can say Bjoern, which is the correct transliteration. But NOT Bjorn, that is not my name, so please stop using it. :-) > > Now I only wanted to update the git packages, so I selected "Keep" in > > the upper right corner, > > That's the worst thing you could possible do. > It changes so many states on so many packages at once, that the result is > hardly predictable. Oh, ok. Could you maybe elaborate more on this? What else does this do, except selecting "Keep" for all packages and thus doing nothing more than I select it manually to do? What does it different than changing all unwanted updates to "Keep" manually in the package list? > If you ask me, Setup is long overdue for a complete replacement. > It "don't have" so many things other package managers allow, that I don't even > know, where to start. Meta dependencies? Suggestions? Virtual packages? Indeed, no objection here. But still I find it strange that "Cur" selects 2.0.4, while it is not selectable manually in the "New" column. > Select "pending" list and remove checkboxes from binary packages you don't > want to install. Sure, that is what I described. But I don't update the packages often, as I always have open a dozen bashes or so, and don't want to close all because of update of files in use. So there are a lot of packages to deselect. But --packages ftw. :-) > P.S. > Please don't https://cygwin.com/acronyms/#TOFU Sorry Regards Björn -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe handles same packages in multiple mirrors badly
On Aug 26 05:35, Andrey Repin wrote: > Greetings, Bjorn Kautler! > > > But first things first, it is Bjorn or Bjoern, not Bjorn. :-) > > Apology. My current locale does not include western diacritics. > > > Now I only wanted to update the git packages, so I selected "Keep" in > > the upper right corner, > > That's the worst thing you could possible do. > It changes so many states on so many packages at once, that the result is > hardly predictable. > > > filtered for "git" in the upper left and then > > cycled in the "New" column and only got the entries "Keep", > > "1.8.5.5-1" and "Uninstall". > > If I now instead select "Curr" in the upper right, the git packages > > have "2.0.4-1" selected in "New" column. > > > If I now cycle through the possibilities I still keep only getting > > "Keep", "1.8.5.5-1" and "Uninstall". The only way to get 2.0.4-1 back in > > that column is to deselect "Curr" and select "Curr" again. > > If you ask me, Setup is long overdue for a complete replacement. > It "don't have" so many things other package managers allow, that I don't even > know, where to start. Meta dependencies? Suggestions? Virtual packages? The problem is not that we don't know this, the problem is, as so often, that we only have a handful of active developers at all, and nobody having the time nor inclination to work on setup to keep it ahead of time. Setup was a wonderful idea, way back when it has been created, but the vintage charm of its Y2K roots are a bit depressing these days. So, if anybody wants to take a stab at setup and revamp it, feel free. The only requirements are, it should still be able to utilize the setup.ini file created on cygwin.com, it should still be able to work the mirror list provided by cygwin.com, and it should still provide a GUI and a command line. Everything else is open for renewal. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpth3VODjbu0.pgp Description: PGP signature
Re: setup.exe handles same packages in multiple mirrors badly
Greetings, Bjorn Kautler! > But first things first, it is Bjorn or Bjoern, not Bjorn. :-) Apology. My current locale does not include western diacritics. > Now I only wanted to update the git packages, so I selected "Keep" in > the upper right corner, That's the worst thing you could possible do. It changes so many states on so many packages at once, that the result is hardly predictable. > filtered for "git" in the upper left and then > cycled in the "New" column and only got the entries "Keep", > "1.8.5.5-1" and "Uninstall". > If I now instead select "Curr" in the upper right, the git packages > have "2.0.4-1" selected in "New" column. > If I now cycle through the possibilities I still keep only getting > "Keep", "1.8.5.5-1" and "Uninstall". The only way to get 2.0.4-1 back in > that column is to deselect "Curr" and select "Curr" again. If you ask me, Setup is long overdue for a complete replacement. It "don't have" so many things other package managers allow, that I don't even know, where to start. Meta dependencies? Suggestions? Virtual packages? > So to just update Git to the newest version I would currently have to > select "Cur" and then manually change all other packages to "Keep", as > this seems the only way to get 2.0.4-1 selected as "New" version. Select "pending" list and remove checkboxes from binary packages you don't want to install. > Now comes the even more interesting part. > Now I started setup.exe with > setup-cygwin.exe --site ftp://ftp.hawo.stw.uni-erlangen.de/cygwin/ > --only-site --root D:\\cygwin --package-manager - -local-package-dir > D:\\cygwin-packages --no-shortcuts --pubkey > http://cygwinports.org/ports.gpg > which is the same command but only the cygwinports mirror removed. > What I see now is the same as before, just that the "New" column > entries reduced to "Keep" and "Uninstall" and selecting "Curr" is > still the only possibility to get 2.0.4-1 into the "New" column of the > git packages. > So this doesn't seem quite right, even with only one mirror selected. :-/ Indeed. That's quite interesting. P.S. Please don't https://cygwin.com/acronyms/#TOFU -- WBR, Andrey Repin (anrdae...@yandex.ru) 26.08.2014, <05:05> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe handles same packages in multiple mirrors badly
Hm,
now that's interesting.
But first things first, it is Björn or Bjoern, not Bjorn. :-)
Now to the interesting part.
If I call setup.exe like the following:
setup-cygwin.exe --site
ftp://mirrors.kernel.org/sourceware/cygwinports/ --site
ftp://ftp.hawo.stw.uni-erlangen.de/cygwin/ --only-site --root
D:\\cygwin --package-manager - -local-package-dir D:\\cygwin-packages
--no-shortcuts --pubkey http://cygwinports.org/ports.gpg
from the console, the console brings amongst other things the message
package git comparing versions 2.0.4-1 and 1.8.5.5-1, result was 1
Now I only wanted to update the git packages, so I selected "Keep" in
the upper right corner, filtered for "git" in the upper left and then
cycled in the "New" column and only got the entries "Keep",
"1.8.5.5-1" and "Uninstall".
If I now instead select "Curr" in the upper right, the git packages
have "2.0.4-1" selected in "New" column.
If I now cycle through the possibilities I still keep only getting
"Keep", "1.8.5.5-1" and "Uninstall".
The only way to get 2.0.4-1 back in that column is to deselect "Curr"
and select "Curr" again.
So to just update Git to the newest version I would currently have to
select "Cur" and then manually change all other packages to "Keep", as
this seems the only way to get 2.0.4-1 selected as "New" version.
Now comes the even more interesting part.
Now I started setup.exe with
setup-cygwin.exe --site ftp://ftp.hawo.stw.uni-erlangen.de/cygwin/
--only-site --root D:\\cygwin --package-manager - -local-package-dir
D:\\cygwin-packages --no-shortcuts --pubkey
http://cygwinports.org/ports.gpg
which is the same command but only the cygwinports mirror removed.
What I see now is the same as before, just that the "New" column
entries reduced to "Keep" and "Uninstall" and selecting "Curr" is
still the only possibility to get 2.0.4-1 into the "New" column of the
git packages.
So this doesn't seem quite right, even with only one mirror selected. :-/
Actually I found a less cumbersome workaround than deselecting all
other packages after selecting "Curr".
Using --packages works, so either calling
setup-cygwin.exe --site
ftp://mirrors.kernel.org/sourceware/cygwinports/ --site
ftp://ftp.hawo.stw.uni-erlangen.de/cygwin/ --only-site --root
D:\\cygwin --package-manager --local-package-dir D:\\cygwin-packages
--no-shortcuts --pubkey http://cygwinports.org/ports.gpg --packages
git --packages git-completion --packages git-cvs --packages git-gui
--packages git-svn --packages gitk
or directly
setup-cygwin.exe --site
ftp://mirrors.kernel.org/sourceware/cygwinports/ --site
ftp://ftp.hawo.stw.uni-erlangen.de/cygwin/ --only-site --root
D:\\cygwin --local-package-dir D:\\cygwin-packages --no-shortcuts
--pubkey http://cygwinports.org/ports.gpg --packages git --packages
git-completion --packages git-cvs --packages git-gui --packages
git-svn --packages gitk --quiet-mode
works in selecting only the git packages and updating them to the
current version.
Now that 2.0.4-1 is installed, it lets me select "Keep", "Reinstall",
"Source", "1.7.9-1", "1.8.5.5-1" and "Uninstall", so setup.exe
obviously already supports versions from different mirrors (repos) as
1.7 is previous version on normal mirror and 1.8 is from cygwin-ports.
Best regards
Björn
2014-08-25 22:39 GMT+02:00 Andrey Repin :
> Greetings, Bjorn Kautler!
>
>> I usually start setup.exe like "setup.exe -K
>> http://cygwinports.org/ports.gpg"; and select the cygwinports mirror
>> and a "normal" mirror in the mirror selection page to have the
>> packages from both mirrors readily available, selectable and
>> updatable.
>
>> Unfortunatley, setup.exe seems to not handle this properly if a
>> package is present on both mirrors. When I look at the available
>> versions for the git packages, then I only see the 1.8 versions from
>> cygwinports, not the newly released ones from the normal mirror. (yes,
>> I made sure I selected a mirror where the packages are already
>> available)
>
>> In such a case I think setup.exe should provide the versions of all
>> the mirrors for selection and auto-select the newest version
>> cross-mirror for update.
>
> Never had a problem.
>
> P.S.
> run ./setup-${ARCH}.exe -K http://cygwinports.org/ports.gpg -O -s
> http://mirrors.kernel.org/sourceware/cygwin/ -s
> http://mirrors.kernel.org/sourceware/cygwinports/
>
>
> --
> WBR,
> Andrey Repin (anrdae...@yandex.ru) 26.08.2014, <00:37>
>
> Sorry for my terrible english...
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe handles same packages in multiple mirrors badly
Greetings, Bjorn Kautler!
> I usually start setup.exe like "setup.exe -K
> http://cygwinports.org/ports.gpg"; and select the cygwinports mirror
> and a "normal" mirror in the mirror selection page to have the
> packages from both mirrors readily available, selectable and
> updatable.
> Unfortunatley, setup.exe seems to not handle this properly if a
> package is present on both mirrors. When I look at the available
> versions for the git packages, then I only see the 1.8 versions from
> cygwinports, not the newly released ones from the normal mirror. (yes,
> I made sure I selected a mirror where the packages are already
> available)
> In such a case I think setup.exe should provide the versions of all
> the mirrors for selection and auto-select the newest version
> cross-mirror for update.
Never had a problem.
P.S.
run ./setup-${ARCH}.exe -K http://cygwinports.org/ports.gpg -O -s
http://mirrors.kernel.org/sourceware/cygwin/ -s
http://mirrors.kernel.org/sourceware/cygwinports/
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 26.08.2014, <00:37>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe handles same packages in multiple mirrors badly
On 08/25/2014 01:33 PM, Björn Kautler wrote: Hi, I usually start setup.exe like "setup.exe -K http://cygwinports.org/ports.gpg"; and select the cygwinports mirror and a "normal" mirror in the mirror selection page to have the packages from both mirrors readily available, selectable and updatable. Unfortunatley, setup.exe seems to not handle this properly if a package is present on both mirrors. When I look at the available versions for the git packages, then I only see the 1.8 versions from cygwinports, not the newly released ones from the normal mirror. (yes, I made sure I selected a mirror where the packages are already available) In such a case I think setup.exe should provide the versions of all the mirrors for selection and auto-select the newest version cross-mirror for update. Sure, a feature like this could be added to setup*.exe. No doubt anyone that wants to offer a patch to support this would receive a thoughtful review of it. :-) A few thoughts and points of clarification. 1. cygwinports, while a commonly referred to site on this list, is not a site supported by cygwin.com or this list. 2. cygwinports is more akin to a repository than a mirror. All Cygwin (current, up-to-date, and valid) mirrors contain the same packages. cygwinports contains, typically, packages that are not distributed by cygwin.com and vice-versa. 3. setup*.exe currently has a design to support Cygwin mirrors. It's currently flexible (or dumb? ;-) ) enough to consider other repositories as well but this is not its primary function and doing so may reveal some of its limitations (as you've found). -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
setup.exe handles same packages in multiple mirrors badly
Hi, I usually start setup.exe like "setup.exe -K http://cygwinports.org/ports.gpg"; and select the cygwinports mirror and a "normal" mirror in the mirror selection page to have the packages from both mirrors readily available, selectable and updatable. Unfortunatley, setup.exe seems to not handle this properly if a package is present on both mirrors. When I look at the available versions for the git packages, then I only see the 1.8 versions from cygwinports, not the newly released ones from the normal mirror. (yes, I made sure I selected a mirror where the packages are already available) In such a case I think setup.exe should provide the versions of all the mirrors for selection and auto-select the newest version cross-mirror for update. Regards Björn -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
