August 2013 - Pharo-dev - lists.pharo.org

auto updates from issue tracker now blocked (was: Put issues from cog issue tracker into pharo issue tracker)

by David T. Lewis

We have gotten well over 100 updates to the vm-dev list for issues being moved around between various issue trackers. This is excessive and seems to be of little relevance to the vm-dev list. As list admin for the vm-dev list, I am responsible for keeping things like this under control. Unless I hear a convincing argument to the contrary, I will disable the cog(a)googlecode.com updates 24 hours from now. Dave On Thu, Aug 08, 2013 at 04:04:44PM +0200, Henrik Johansen wrote: > > On Aug 8, 2013, at 3:03 , Igor Stasenko <siguctua(a)gmail.com> wrote: > > > On 8 August 2013 14:14, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> > >> I guess that solves the question around the fate of the cog issue tracker: I > >> didn't mean a deprecation or similar, people can continue using it as they > >> want. I put for that links so people can go back and forth between the issue > >> trackers. My unique and good intention was to make those issues more > >> visible. > > > > Thanks, Guillermo. > > I think everyone understands that your intention was for good, but > > when you don't inform > > people properly they tend to think worst (including me) > > > > :) > > > > -- > > Best regards, > > Igor Stasenko. > > > > Especially when you end up spamming VM-dev with Cog issue tracker updates saying "Moved to fogbugz". > Even with the modified updates, why you'd need to mirror an existing tracker for a related but distinct project into the Pharo tracker, with the synchronization issues that might cause, js still a bit beyond me. > > Cheers, > Henry >

Aug. 8, 2013

[update 3.0] #30328

by StÃ©phane Ducasse

Aug. 8, 2013

Re: [Pharo-dev] Put issues from cog issue tracker into pharo issue tracker

by StÃ©phane Ducasse

On Aug 8, 2013, at 7:37 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Thu, 8 Aug 2013, Esteban Lorenzano wrote: > >> that's a restriction made by the service we choose. > > So it is you, who have chosen the restriction. > >> issues are publicly visible here: >> >> http://bugs.pharo.org >> >> and there you also can register your self so you can also edit issues in fogbugz. >> so yes... is public in the "non-restricted access" meaning of the word. > > The barrier is way to high for anyone without an account to access the tracker. All links to issues on this mailing list point to fogbugz.com. Finding the matching issue on bugs.pharo.org seems to be kinda impossible. > For example can you point me to the publicly visible link for this case https://pharo.fogbugz.com/f/cases/11144 (without checking pharo.fogbugz.com ofc)? > > Also bugs.pharo.org doesn't seem to be up-to-date. For example I can't find the recently moved issues from the Cog tracker. Levente we did not take fogbuz because it forces people to log to edit bugs. We took it because google removed the script API of google code. We had really something else to do than to change a bug tracker when it was not the moment nor our wishes. Now fogbugz people nicely offered us to host and be able to use software that costs 25$ per site per month. So we decided to give a try and it has the cost that we cannot edit bugs without being log and a complex interface but we are happy that we do not have to run mantis or another bug tracker by ourselves. Now guillermo saw that squeakers use the squeak bug tracker to track Cog VM bugs so there is no point for us to have two bugtrackers to deal with. So this is simple I guess and this bug tracker stays a public one. Anybody on earth willing to have an access can get one. S. > > > Levente > >> >> Esteban >> >> On Aug 8, 2013, at 4:57 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: >> >>> Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>>> On 8 August 2013 13:35, Levente Uzonyi >>> <leves(a)elte.hu> wrote: > > On Thu, 8 Aug 2013, >>> StÃ©phane Ducasse wrote: > > g the issue on a public tracker means >>> private? > > > > > > How is that a "public tracker"? > > > > can you >>> elaborate? > https://pharo.fogbugz.com/ > is publicly accessible, no? or >>> what makes you think it is not public? > >>> >>> Take the first bug fix from the Pharo Summer release details at >>> <https://pharo.fogbugz.com/f/cases/10014/World-menu-System-Switch-User-s >>> erves-no-purpose> >>> >>> This gives a the fogbugz log in page so to get info you need to login so >>> not public (also are the bugs indexed by google?) >>> >>> >>> -- >>> Mark >>> >>> >> >>

Aug. 8, 2013

Re: [Pharo-dev] Put issues from cog issue tracker into pharo issue tracker

by Levente Uzonyi

On Thu, 8 Aug 2013, Esteban Lorenzano wrote: > that's a restriction made by the service we choose. So it is you, who have chosen the restriction. > issues are publicly visible here: > > http://bugs.pharo.org > > and there you also can register your self so you can also edit issues in fogbugz. > so yes... is public in the "non-restricted access" meaning of the word. The barrier is way to high for anyone without an account to access the tracker. All links to issues on this mailing list point to fogbugz.com. Finding the matching issue on bugs.pharo.org seems to be kinda impossible. For example can you point me to the publicly visible link for this case https://pharo.fogbugz.com/f/cases/11144 (without checking pharo.fogbugz.com ofc)? Also bugs.pharo.org doesn't seem to be up-to-date. For example I can't find the recently moved issues from the Cog tracker. Levente > > Esteban > > On Aug 8, 2013, at 4:57 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: > >> Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 8 August 2013 13:35, Levente Uzonyi >> <leves(a)elte.hu> wrote: > > On Thu, 8 Aug 2013, >> StÃ©phane Ducasse wrote: > > g the issue on a public tracker means >> private? > > > > > > How is that a "public tracker"? > > > > can you >> elaborate? > https://pharo.fogbugz.com/ > is publicly accessible, no? or >> what makes you think it is not public? > >> >> Take the first bug fix from the Pharo Summer release details at >> <https://pharo.fogbugz.com/f/cases/10014/World-menu-System-Switch-User-s >> erves-no-purpose> >> >> This gives a the fogbugz log in page so to get info you need to login so >> not public (also are the bugs indexed by google?) >> >> >> -- >> Mark >> >> > > >

Aug. 8, 2013

Re: [Pharo-dev] Put issues from cog issue tracker into pharo issue tracker

by Igor Stasenko

well, strictly speaking, being indexed by google is not synonym to being public. (and, of course, that don't means we don't miss or want it) On 8 August 2013 18:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > that's a restriction made by the service we choose. > issues are publicly visible here: > > http://bugs.pharo.org > > and there you also can register your self so you can also edit issues in fogbugz. > so yes... is public in the "non-restricted access" meaning of the word. > > Esteban > > On Aug 8, 2013, at 4:57 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: > >> Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 8 August 2013 13:35, Levente Uzonyi >> <leves(a)elte.hu> wrote: > > On Thu, 8 Aug 2013, >> StÃ©phane Ducasse wrote: > > g the issue on a public tracker means >> private? > > > > > > How is that a "public tracker"? > > > > can you >> elaborate? > https://pharo.fogbugz.com/ > is publicly accessible, no? or >> what makes you think it is not public? > >> >> Take the first bug fix from the Pharo Summer release details at >> <https://pharo.fogbugz.com/f/cases/10014/World-menu-System-Switch-User-s >> erves-no-purpose> >> >> This gives a the fogbugz log in page so to get info you need to login so >> not public (also are the bugs indexed by google?) >> >> >> -- >> Mark >> >> > > -- Best regards, Igor Stasenko.

Aug. 8, 2013

Re: [Pharo-dev] [Vm-dev] Changes in the repositories for the VM

by Igor Stasenko

I'd like to add many thanks to developers of FileTree project who made this possible. Thanks to that we can keep all VM sources in single repository, C and Smalltalk ones. -- Best regards, Igor Stasenko.

Aug. 8, 2013

Re: [Pharo-dev] Pharo VM latest on the Debian 7

by StÃ©phane Ducasse

> Are you saying the Pharo VM requires glibc version 2.15 of March 2012, and that consequently the Pharo VM as compiled won't run on any Linux distro older than 17 months? No we will support several linux versions. Stef

Aug. 8, 2013

Re: [Pharo-dev] Put issues from cog issue tracker into pharo issue tracker

by Esteban Lorenzano

that's a restriction made by the service we choose. issues are publicly visible here: http://bugs.pharo.org and there you also can register your self so you can also edit issues in fogbugz. so yes... is public in the "non-restricted access" meaning of the word. Esteban On Aug 8, 2013, at 4:57 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: > Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 8 August 2013 13:35, Levente Uzonyi > <leves(a)elte.hu> wrote: > > On Thu, 8 Aug 2013, > StÃ©phane Ducasse wrote: > > g the issue on a public tracker means > private? > > > > > > How is that a "public tracker"? > > > > can you > elaborate? > https://pharo.fogbugz.com/ > is publicly accessible, no? or > what makes you think it is not public? > > > Take the first bug fix from the Pharo Summer release details at > <https://pharo.fogbugz.com/f/cases/10014/World-menu-System-Switch-User-s > erves-no-purpose> > > This gives a the fogbugz log in page so to get info you need to login so > not public (also are the bugs indexed by google?) > > > -- > Mark > >

Aug. 8, 2013

Changes in the repositories for the VM

by Esteban Lorenzano

Hi, Ok, we finally decided to make some changes longtime postponed, to improve our way of building the VM. Squeak guys are still using the old mechanism, so this just applies to Pharo and the continuous integration under the Pharo umbrella... but please notice that ANY vm flavor can be built with this source repository. The first change was to put all sources together. No more MCZ files to keep VMMaker and plugins and platform sources as a GIT repository. We are using filetree to keep source files, so is just like a different kind of monticello repository. With this, now a commit is atomic and the platform sources will be in sync with VMMaker sources. Also, that simplifies a lot the ConfigurationOfCog file, since the commit number is the version number... now we just need the baseline (not version anymore). So now you can checkout a version of the repository and do: ConfigurationOfCog loadGit. and that's all :) (from our point of view, this simplification is an huge advantage over the older process). The second change is just a relocation. Now the VM source lives in GitHub :) The reason of this move is because GitHub has a lot more functionality than the old Gitorious, also most of the people using filetree are already using GitHub so is easier for them to fork, etc. Also, it is hyped so we wanted to be in that wave ;) The new repository can be found at: https://github.com/pharo-project/pharovm Cheers, Esteban

Aug. 8, 2013

Re: [Pharo-dev] Pharo VM latest on the Debian 7

by Esteban Lorenzano

well... no. something happened with the build, because it should be executable in a 1.5 years old linux. in the middle term, we are going to adopt an approach similar to VW (one VM for one image version), and we will support some years of backward compatibility. But not infinite, of course, because work is too much :) Now... the "latest" VM is unstable. Is not a release and of course it will be problems. When we release it, it will be version to run in several versions... it should be as simple as add a slave into our build server. cheers, Esteban On Aug 8, 2013, at 4:54 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 8 August 2013 15:40, Andres Valloud > <avalloud(a)smalltalk.comcastbiz.net> wrote: >> Are you saying the Pharo VM requires glibc version 2.15 of March 2012, and >> that consequently the Pharo VM as compiled won't run on any Linux distro >> older than 17 months? >> > > You are not forced to use latest VM, you can always download and use > 5-year old VM, which will (hopefully) > work for you. > :) > > Now if platform (linux) moves, we must follow. And that is not a question to me. > > -- > Best regards, > Igor Stasenko. >

Aug. 8, 2013