Dear all
I have recently exchanged the previous SSL certificates that were signed with a
DAS-NETZWERKTEAM CA certificate for with new certificates signed by Let's Encrypt.
Additionally, all HTTP requests, with the limitation of accessing Jenkins
directly, should be getting automatically redirected to a HTTPS location.
This measure fixes the annoying "insecure connection" errors.
Of course, previous HTTPS connections were never truly insecure - the CA
certificate just was not trusted by browsers.
If you encounter trouble accessing Japsand-based services like the wiki, please
file a bug report with X2Go BTS[1].
Mihai
[1] http://wiki.x2go.org/doku.php/wiki:bugs
Dear all
I am happy to announce that from now on the X2Go package archive that provides
Raspbian packages of X2Go[1] also offers X2Go packages that have been built
against Raspbian Stretch - the new Raspbian release version.
Additionally, the pseudo code names have been reset. "stable" now maps to
"stretch" and "oldstable" maps to "jessie". Users are strongly encouraged to use
the actual code names (i.e., not the pseudo code names) in order to not trigger
unwanted upgrades and to avoid incompatibilities, since pseudo code name changes
are typically not carried out in tandem with Debian.
We hope this makes our package archive more useful.
If you encounter dependency problems when installing X2Go release or
nightly packages under Raspbian Stretch, please file a bug report with X2Go BTS[3].
For setup information, refer to the Debian packages info wiki article[3].
Mihai
[1] https://packages.x2go.org/raspbian
[2] http://wiki.x2go.org/doku.php/wiki:bugs
[3]
http://wiki.x2go.org/doku.php/wiki:repositories:raspbian
Dear all
I am happy to announce that from now on the X2Go package archive that provides
Debian packages of X2Go[1] also offers X2Go packages that have been built
against Debian Buster - the new Debian testing version.
Additionally, the pseudo code names have been reset. "stable" now maps to
"stretch", "oldstable" maps to "jessie", "oldoldstable" maps to "wheezy" and
"testing" maps to "buster". Users are strongly encouraged to use the actual code
names (i.e., not the pseudo code names) in order to not trigger unwanted
upgrades and to avoid incompatibilities, since pseudo code name changes are
typically not carried out in tandem with Debian.
We hope this makes our package archive more useful.
If you encounter dependency problems when installing X2Go release or
nightly packages under Debian Buster, please file a bug report with X2Go BTS[3].
For setup information, refer to the Debian packages info wiki article[3].
Mihai
[1] https://packages.x2go.org/debian
[2] http://wiki.x2go.org/doku.php/wiki:bugs
[3]
http://wiki.x2go.org/doku.php/wiki:repositories:debian
Dear all
I am happy to announce that from now on the X2Go package archive that provides
OpenSUSE packages of X2Go[1] also offers X2Go packages that have been built
against OpenSUSE Leap 42.3 - the new OpenSUSE Leap release version.
We hope this makes our package archive more useful.
If you encounter dependency problems when installing X2Go release or
nightly packages under OpenSUSE Leap 42.3, please file a bug report with X2Go
BTS[3].
For setup information, refer to the SUSE-based packages info wiki article[3].
Mihai
[1] https://packages.x2go.org/opensuse
[2] http://wiki.x2go.org/doku.php/wiki:bugs
[3]
http://wiki.x2go.org/doku.php/wiki:repositories:suse#adding_the_x2go_reposiā¦
Dear all
a few weeks ago I took the opportunity and updated our build host to Debian Stretch.
Build failures of *SUSE packages due to a newer version of obs-build were fixed
subsequently. We're now running a customized version with backported fixes and
commits from the upstream obs-build repository pulled in.
The environment powering wiki.x2go.org has also been updated.
All systems should be working normally.
As always, if you encounter broken packages or inconsistencies in repositories,
please file a bug report with X2Go BTS[1].
Mihai
[1] http://wiki.x2go.org/doku.php/wiki:bugs