x2go-project

x2go-project@lists.x2go.org

1 participants
152 discussions

X2Go @ Linuxday.AT, Dornbirn, Austria - THIS Saturday
by Stefan Baur 23 Nov '16

23 Nov '16

Hi, this is just a quick reminder that X2Go will be present at Linuxday.AT in Dornbirn, Austria this Saturday. You can find us at Booth B2 (https://www.linuxday.at/standplan-2016) and there will be a talk (in German) about how you can use a Linux server running X2Go to protect your Microsoft Windows clients from ransom- and other malware. See https://www.linuxday.at/vortraege/2016 for the complete schedule. This event does not require signing up in advance, also, there is no entry fee. Kind Regards, Stefan Baur X2Go Project/Community Manager -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

1 0

Debian Repository Taken Offline
by Mihai Moldovan 17 Nov '16

17 Nov '16

Hi Unfortunately, nightly packages crept into the Debian "main" repositories after the build tool changes on 15 Oct 2016. The Debian repository has been taken offline for the time being pending investigation. If you have installed or updated X2Go "main" packages for Debian from our repository on 15 Oct 2016 or later, you will have to proactively remove and re-install all X2Go packages once the repository is available again. I will reply to this thread once the situation has been rectified. Best regards, Mihai

1 1

Bug#1053: [X2Go-Dev] armhf for debian jessie repo broken
by Mihai Moldovan 16 Nov '16

16 Nov '16

Control: tag -1 not-a-bug Control: close -1 On 07.07.2016 07:27 AM, Chris wrote: > As there is no comment on my report, I would recommend to disable the > jessie armhf repo altogether. > It does have unresolved dependencies and therefore is an unusable debian > repository. I'm closing up this bug report, although you're right. For any architecture other than amd64 and i386, the Debian repository is unusable. The only packages available for these architectures are noarch (i.e., binary-independent) packages and hence the repositories are broken for these architectures. On the other hand, we do not advertise support for anything other than amd64/i386 on Debian Jessie and above. This said, I also have good news: coming up we'll be serving Raspbian (not Debian) packages for armhf in a separate repository. Currently this repository is only for Raspbian Jessie and nightly X2Go packages, but I will be adding release packages later. Mihai

1 0

Upcoming Deprecation of EOL Distributions
by Mihai Moldovan 03 Nov '16

03 Nov '16

Hi In order to lower resource stress when building packages, I plan to deprecate support for distributions that have reached End Of Life on September 4th 2016. This includes the following distro versions: - Debian: o 6.0 "squeeze" - Fedora o 19 o 20 o 21 o 22 - OpenSuSE o 12.2 o 12.3 o 13.1 - SuSE Linux Enterprise Desktop (not Server!) o 11.2 o 11.3 After deprecation, no new builds will be published and existing builds will be deleted from the repositories to discourage users from installing unmaintained software. Mihai

2 6

packages.x2go.org, archives.packages.x2go.org and code.x2go.org down
by Mihai Moldovan 16 Oct '16

16 Oct '16

Dear users Due to prolonged problems with the IPv6 connectivity in the virtual machine currently providing services for packages.x2go.org, archives.packages.x2go.org and code.x2go.org, this machine has been shut down. The networking setup has to be redone. We anticipate the services to be available again on Monday or Tuesday, most likely during day time (17.10.2016 or 18.10.2016, CEST.) For now, errors in contacting these hosts are expected. No new commits can be uploaded to the source code repositories. None of these services have been deprecated. Best regards, Mihai

1 0

RfC: New Rules for X2Go: The Gathering 2017
by Stefan Baur 22 Aug '16

22 Aug '16

Hi everyone, there are a few things that I would like to mention before posting an "X2Go: The Gathering 2016 - The Aftermath" message (which will hopefully happen within the next 7 days). 1) If you're sick, then please stay at home. 2) If you've had recent contact with someone that has some contagious disease, and you are not 100% sure that you're immune - please, stay at home as well! 3) If you know that someone has a contagious disease, and you've signed up for our event, please do not seek physical contact with that person before the event. If you have anything that needs to be discussed because you need it for the event, use e-mail, phone calls, whatever, but don't visit each other, the reason being rule #2. Everyone was smart enough to follow rule #1. However, rules #2/#3 weren't followed by everyone, and thus it was only sheer luck that no one else got seriously infected but the person carrying the infection. (Seems my immune system was able to deal with it, so I'm back up to spec again.) If this had taken a turn for the worse, we would have had X2G0 as the successor to H5N1. So please avoid that in the future and act responsible with regards to your fellow participants. 4) I've received feedback that we should not be hosting the event in August, but rather before or after that month. The precursor to "X2Go: The Gathering", the X2GoHackTrain, took place in September. For "X2Go: The Gathering", we've had October/November, June, and now August. My assumption was that a lot of people would be on vacation during June and July, which is why I picked August for this year's event. Seems I was mistaken about this and people - especially, but not only in Spain - prefer August for their summer vacation. June/July still doesn't "feel" right to me, so maybe the next event should be in May 2017 already? The October/November event saw the highest participant count, but the June event was only one participant less. However, with merely three events, these numbers aren't exactly statistically significant. So what do you think which month is best suited for the 2017 event? Without further feedback, I would aim for May-June 2017, mainly due to the weather. 5) As you might have noticed, we've had some last-minute changes to the list of participants: Some had signed up - and cancelled again - after the official deadline was over, others cancelled due to time constraints or because they became sick and were responsible enough to stay at home. This turned out to be a problem for me (time=money - I'm taking time off of my day job to organize this), Linuxhotel (changing the room reservation plan over and over), and the event itself, as the Orga crew was understaffed. Also, it hits us financially, as we're wasting money from our sponsors, since Linuxhotel rightfully charges us the single room fee for a double room that has only one occupant. For X2Go: The Gathering 2016, I'm sure we'll find a way to cover these costs, but I do not want to see that happening again. My idea how to solve this would be: a) A late signup fee for everyone that we can still accomodate after the official deadline has passed. I'm thinking something between a 15% price increase and charging the regular (non-community-rebated) hotel room fees. b) Cancelling your stay less than 48 hours before the event will mean you have to pay for bed and and lunch (all the other costs can be waived). c) BIG EXCEPTION to b): No charges if you're cancelling because you're sick. This is to encourage responsible behavior and to avoid people taking part even when they're sick. I'm sure we can all pretty much agree to #1 - #3. The question is, and this is why this message is tagged "RfC", how do we deal with issues #4 and #5. I've posted my suggestions, please let me know what you think of them and what other suggestions you might have. Kind Regards, Stefan Baur (with my X2Go Event Planner hat on) -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

2 1

Bug#796: Ubuntu Server 14.04.2 PPA: Unresolvable Dependencies for x2goserver
by Mihai Moldovan 22 Aug '16

22 Aug '16

Control: close -1 On 14.08.2016 12:49 AM, Mihai Moldovan wrote: > Is this still a problem, or did whatever broke in the repository get fixed > "automatically"? I installed x2goserver successfully in a new 14.04 environment during the gathering and haven't seen any dependency problems. I'll be closing this bug report. If it's still an issue, feel free to reopen this report. Mihai

1 0

X2Go: The Gathering 2016 - Updated Info in the Wiki
by Stefan Baur 15 Aug '16

15 Aug '16

Hello, the wiki page regarding our annual Community Event has been updated quite a bit: http://wiki.x2go.org/doku.php/events:x2go-gathering-2016 Especially if you are a participant, you should take a look at the current state of things. Kind Regards & Happy Hacking Stefan Baur X2Go Event Organizer -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

1 0

new DebBugs scripts: mbox / cleanbug
by Mike Gabriel 10 Aug '16

10 Aug '16

Hi all, last night, I created to new scripts for the debbugs software underneath bugs.x2go.org. Both scripts are attached and can be found under /usr/lib/debbugs on host ymir.das-netzwerkteam.de. Especially the cleanbug script should be of interested here. I recently received various abuse notifications from my provider and they all relate to X2GO bugs containing mails with virus attachments. These need to be cleaned. I already did so for the reported URLs: http://bugs.x2go.org/128 http://bugs.x2go.org/232 http://bugs.x2go.org/496 http://bugs.x2go.org/765 But there are more... Please coordinate in the X2Go core team, who will work on cleaning up the X2Go bugtracker. Currently, these people have access: Heinz Mihai Mike You have to log into ymir.das-netzwerkteam.de (aka bugs.x2go.org) as user locadm and become root via sudo. The cleanbug script itself is easy to handle: # /usr/lib/debbugs/cleanbug <bugno> Once you triggered the script, you have to look at bug posts on the selected bug and say yes and no. At the end you get asked, if you really want to write back the changes to the bug. The answer's question defaults to "no". You should create some back before manipulating existing bugs. For this, create copies of <bugno>.log in /var/lib/debbugs/spool/db-h/ Note for archived bugs: for cleaning up archived bugs, you have to unarchive them first. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%4…

3 7

Bug#1033: IPv6 / DNS Support of japsand.x2go.org
by Mike Gabriel 08 Jul '16

08 Jul '16

Package: japsand.x2go.org Severity: important Hi Mihai, Heinz, since a couple of days (maybe since yesterday only), the host japsand.x2go.org tries to contact my mail server (which acts as a mail relay) over IPv6. I have just white-listed japsand's IPv6 address, but the next problem arises then: japsand.x2go.org does not have an AAAA record in DNS. Please add this line to x2go.org's named configuration: ``` japsand.x2go.org. IN AAAA 2a01:4f8:211:11c1::2 ``` Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%4…

1 2

← Newer
1
...
5
6
7
8
9
10
11
...
16
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

x2go-project