Second bug report.
As select all package is problematic… 
I returned to the software center and select only the two firsts packages.
When applied, it seem ok… But it not give me installation successfull:
Third bug report:
This software center needs actually some little fixes.
So I go to visit the duc
The time problem still here:
1 Like
Ok, got it.
Thank you for testing, I didn’t want to waste your time.
Let’s try to develop a plan.
It’s not easy for me walking in your shoes, I need feedback.
My proposal:
- release NethServer 7-alpha2 next week
- provide a faq page to list known problems
- define clear testing targets for alpha2
- define a way to report issues
Decisions to take before release:
- do we need an ISO cd or can we ask to install CentOS to test alpha2?
@Jim, ntopng packages have problems, I think I’ll remove it from the repos. The timezone/utc time in duc is cosmetic, we’ll work on it before beta.
I don’t think you should be using time to create iso’s for alpha, CentOS is fine to me but it seems much better if all testers are using the same iso, the link that’s on the howtoforge page that’s linked from our wiki is no good, so our wiki should have a more direct link, example, I think I remember that I eventually used this one because it looked close to me, I didn’t reverse dns the ip and geolocate but it looked like it was close to me. http://mirror.chpc.utah.edu/pub/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso
Then install http://packages.nethserver.org/nethserver/7.2.1511/base/x86_64/Packages/nethserver-release-7-0.1.11.g66e6835.ns7.noarch.rpm I guess ? but not mock ? unfortunately, I had to wget, which mean installing wget…
Then nethserver-install
Then go to town by logging into the gui and installing packages…
Right?
I really wish I could say, 'ok, I’m going to sit down for three hours and test, but I can’t, I try to spin up a vm while doing other work but when the initial install doesn’t work, I get distracted from my other work to get the core to where it should be to see if an installed package is going to work like the end user expects and bam, the morning is gone and boom.
But we want to waste our time, don’t worry about it.
I think about one thing.
You must have a repository to develop.
We need a reposytory to test.
Is this repository can be the same?
Or it must be split in two? and synchornize by day or two days or week?
Thank for the specific way to report issue… Because with an alpha version, it can be a flood 
I would have the ISO. At least unattended is known to work since alpha1! See below:
Sure! After alpha2 is released we freeze the base repository and add fixes to testing and updates, as usual.
A wiki page, discussions here and possibly github issues
I support these steps, @giacomo @filippo_carletti how much time requires a new ISO? IMHO it’s easier to test, to share and publicize.
I’d like to write down new release notes for this version and send them to the media as well 
Is the timezone problem only cosmetic?
If “the cosmetic” have a problem, what about more complex stuff under the hood?
If trivial stuff have problem, a Nethserver newcomer can imagine more problems under the hood, not trust the system… By consequence, it’s not only a cosmetic problem, it’s a question of confidence.
It’s trusty, or not trusty?
Yes, it is only cosmetic: the time is always displayed in GMT timezone.
I can change the behavior in two different ways:
- add a “GMT” label inside the GUI
- return the time accordingly to the current timezone configured in PHP. In this case, if the PHP timezone is different from the system timezone, also the displayed times will be different.
What do you prefer?
Yes, you ought 
Please, look at
I’ll add issue tracker bookmarks there
It’s not fair…
Or you put all times in the system in GMT
Or you put all times in the system in localtime.
But a mixed bag not give a good feeling
Jim
I didn’t have the time to do the modification, do you prefer this fix?
So what do you think to not display the time 
Done.
I just added a new landing page for nethserver-httpd.
Anyone is welcome to improve it! (/cc @robb @alefattorini)
4 Likes
Love it, it will be definitely inserted into the next alpha2 release notes!