Good morning all,
This evening (UTC time) I will be moving Gitlab from the current system it
is located on to a new server.
This move is being undertaken to ensure we have the most up to date
software stack, as well as take advantage of newer hardware that is both
more efficient and more
On Wed, Nov 29, 2017 at 8:11 PM, Ben Cooksley wrote:
> Hi all,
Hi everyone,
>
> Over the past 24 hours we have received initial warning notifications
> that a disk in our bulk storage server has begun to show signs of
> failure. We have now begun the process of having this
Hi all,
Over the past 24 hours we have received initial warning notifications
that a disk in our bulk storage server has begun to show signs of
failure. We have now begun the process of having this disk replaced,
following which we will need to rebuild the RAID array.
As a consequence of this at
Hi,
The server has been migrated and bugs.kde.org is now up and running.
Maybe you could find it not available for a short time until DNS gets
updated.
Thanks,
Víctor Blázquez
Víctor Blázquez
On Thu, Jul 10, 2014 at 11:39 PM, Ben Cooksley bcooks...@kde.org wrote:
Hi all,
To allow for a
Hi all,
To allow for a server move and software upgrade, bugs.kde.org will not
be accessible from 18:00 UTC on Friday 11th July.
Apologies for any inconvenience. As this will involve a DNS change,
you may not be able to access Bugzilla if your DNS has not updated
following the server move.
Hi,
In the file skrooge.rc of releaseme, I changed:
*customsrc=g...@git.kde.org:skrooge**
*
by
*customsrc=git://anongit.kde.org/skrooge*
and *I am now able to create the package*.
So, thank you for your help.
For fun, I tried to build some other packages (zanshin , tellico, ...)
Hi,
I don't know if this is linked, but now, when I use releaseme to build
a tar file, I have an error during the git clone.
Example:
If I launche:
/*git clone --branch master --depth 1 g...@git.kde.org:skrooge*/
I have the following traces:
*Cloning into 'skrooge'...*
*Enter
On Wed, Mar 27, 2013 at 10:33 AM, Stephane MANKOWSKI
steph...@mankowski.fr wrote:
Hi,
Hi Stephane,
I don't know if this is linked, but now, when I use releaseme to build a
tar file, I have an error during the git clone.
Example:
If I launche:
git clone --branch master --depth 1
On Tuesday, March 26, 2013 22:33:24 Stephane MANKOWSKI wrote:
Hi,
I don't know if this is linked, but now, when I use releaseme to build
a tar file, I have an error during the git clone.
I just tried, both your example from git.kde.org, and a full clone from
anongit.kde.org (not sure which
On Saturday 23 March 2013 03:46:21 PM Ben Cooksley wrote:
Hi all,
git.kde.org should now be online and operational again.
Our apologies for the inconvenience, we will be analysing the causes
of this to avoid repeats in the future.
You guys are awesome. I know this is a lot of work to
Hi all,
In order to allow for maintenance and updates on the physical host for
git.kde.org and svn.kde.org downtime has been scheduled for both.
This will span from 1200 UTC to 1800 UTC on Friday, 22 March.
While we will try to keep the actual period of downtime as short as
possible during this
2013/3/22 Ben Cooksley bcooks...@kde.org:
While we will try to keep the actual period of downtime as short as
possible during this period, due to the nature of the change, it may
take longer than we expect.
Hi,
both svn and git are up again.
Greetings,
Dirk
On Fri, Mar 22, 2013 at 4:36 PM, Dirk Müller muel...@kde.org wrote:
2013/3/22 Ben Cooksley bcooks...@kde.org:
While we will try to keep the actual period of downtime as short as
possible during this period, due to the nature of the change, it may
take longer than we expect.
Hi,
both
On Fri, Mar 22, 2013 at 5:33 PM, Aleix Pol aleix...@kde.org wrote:
On Fri, Mar 22, 2013 at 4:36 PM, Dirk Müller muel...@kde.org wrote:
2013/3/22 Ben Cooksley bcooks...@kde.org:
While we will try to keep the actual period of downtime as short as
possible during this period, due to the
Hi all,
git.kde.org should now be online and operational again.
As the canonical copy of the repositories stored by it was corrupted
in certain parts, we have restored all repositories from another
system.
To the best of our knowledge no commits have been lost, however it is
still possible they
Hi all,
Just a quick reminder of the previously announced downtime:
In order to allow for a move between data centers, there will be
downtime for the server cano.kde.org on Saturday 18th August.
This will begin at approximately 09:00 UTC and may last up to 12 hours
(i.e. until 19:00 UTC).
The
Hi all,
Following a request from the KDE Quality team, the downtime for
Bugzilla will be postponed until Tuesday evening, CEST time.
KDE Identity will still under go down time as scheduled.
Regards,
Ben Cooksley
KDE Sysadmin
Hi all,
In order to allow for some restructuring, there will be downtime of
KDE Bugzilla (bugs.kde.org) and KDE Identity (identity.kde.org).
Both the Identity frontend and backend will be unavailable, so please
login to any Identity authentication provided site before the downtime
begins.
This
Hi everyone,
To allow us to perform some web server configuration changes on
cano.kde.org, downtime has been scheduled for the following list of
sites. This downtime will be intermittent, and will be undertaken on
Saturday morning (GMT timezone).
The affected sites under kde.org: dot, forum,
Hi all,
The Bugzilla server move was completed successfully about 7 hours ago.
If you encounter any issues, please let Sysadmin know through the
appropriate channels noted at the top of all KDE Bugzilla pages. Some
DNS changes are still propagating unfortunately for certain people, so
you may
On Friday, June 24, 2011 19:12:50 Ben Cooksley wrote:
The Bugzilla server move was completed successfully about 7 hours ago.
If you encounter any issues, please let Sysadmin know through the
appropriate channels noted at the top of all KDE Bugzilla pages. Some
thanks for seeing this through!
Hi everyone,
(Apologies for cross posting)
As part of improvements to our infrastructure, KDE Sysadmin will be
moving Bugzilla from it's current server to a new one. This newer
server should enhance the performance of Bugzilla among other things,
and allow us to move forward in the long term
22 matches
Mail list logo