Hi,
my last two commits, sent with "git send-email ..." (and pushed) don't show up on patchwork.ipfire.org.
Sending to development list is OK, but nothing can be seen on patchwork.
Can anyone confirm?
Best, Matthias
Hi Matthias, did send also two patches but the last entry in Patchwork is the Squid update from 2018-07-17 . So yes i can confirm it here too.
Greetings,
Erik
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
Hi,
my last two commits, sent with "git send-email ..." (and pushed) don't show up on patchwork.ipfire.org.
Sending to development list is OK, but nothing can be seen on patchwork.
Can anyone confirm?
Best, Matthias
Thanks for letting me know.
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
It's working again and I manually imported the patches.
Best, -Michael
On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
Hi Matthias, did send also two patches but the last entry in Patchwork is the Squid update from 2018-07-17 . So yes i can confirm it here too.
Greetings,
Erik
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
Hi,
my last two commits, sent with "git send-email ..." (and pushed) don't show up on patchwork.ipfire.org.
Sending to development list is OK, but nothing can be seen on patchwork.
Can anyone confirm?
Best, Matthias
And this at these temperatures...
Thanks! :-)
On 04.08.2018 15:54, Michael Tremer wrote:
Thanks for letting me know.
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
It's working again and I manually imported the patches.
Best, -Michael
On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
Hi Matthias, did send also two patches but the last entry in Patchwork is the Squid update from 2018-07-17 . So yes i can confirm it here too.
Greetings,
Erik
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
Hi,
my last two commits, sent with "git send-email ..." (and pushed) don't show up on patchwork.ipfire.org.
Sending to development list is OK, but nothing can be seen on patchwork.
Can anyone confirm?
Best, Matthias
It's lovely isn't it?
On Sat, 2018-08-04 at 18:04 +0200, Matthias Fischer wrote:
And this at these temperatures...
Thanks! :-)
On 04.08.2018 15:54, Michael Tremer wrote:
Thanks for letting me know.
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
It's working again and I manually imported the patches.
Best, -Michael
On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
Hi Matthias, did send also two patches but the last entry in Patchwork is the Squid update from 2018-07-17 . So yes i can confirm it here too.
Greetings,
Erik
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
Hi,
my last two commits, sent with "git send-email ..." (and pushed) don't show up on patchwork.ipfire.org.
Sending to development list is OK, but nothing can be seen on patchwork.
Can anyone confirm?
Best, Matthias
On 04.08.2018 19:58, Michael Tremer wrote:
It's lovely isn't it?
Hu!?
You're sitting in a fridge, right? ;-)
On Sat, 2018-08-04 at 18:04 +0200, Matthias Fischer wrote:
And this at these temperatures...
Thanks! :-)
On 04.08.2018 15:54, Michael Tremer wrote:
Thanks for letting me know.
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
It's working again and I manually imported the patches.
Best, -Michael
On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
Hi Matthias, did send also two patches but the last entry in Patchwork is the Squid update from 2018-07-17 . So yes i can confirm it here too.
Greetings,
Erik
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
Hi,
my last two commits, sent with "git send-email ..." (and pushed) don't show up on patchwork.ipfire.org.
Sending to development list is OK, but nothing can be seen on patchwork.
Can anyone confirm?
Best, Matthias
On 04.08.2018 15:54, Michael Tremer wrote:
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
Besides, since a few days loading git.ipfire.org takes about 15-20 seconds. FF shows "Transferring data from git.ipfire.org" and nothing happens...
Migration!?
Best, Matthias
Errr, no. This is not migrating any more, but has been migrated.
Since we are having some things we can do better with our many web servers, I started using haproxy on our primary firewall and everything else is now being proxies from there to the right internal server.
That means, that the git repositories are now coming directly from the server where they are hosted and are not being transferred over NFS first. Same goes for downloads. That puts quite a bit less load on the servers and makes the downloads slightly faster.
I also moved Gitweb to a new server which is now running Apache and not nginx any more. However, apache doesn't correctly cache the index page. I don't know why that is, but it is just being stupid. Hence the slight delay to render the page.
Best, -Michael
On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
On 04.08.2018 15:54, Michael Tremer wrote:
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
Besides, since a few days loading git.ipfire.org takes about 15-20 seconds. FF shows "Transferring data from git.ipfire.org" and nothing happens...
Migration!?
Best, Matthias
Hi,
On 05.08.2018 12:24, Michael Tremer wrote:
Errr, no. This is not migrating any more, but has been migrated.
As it seems - it migrated "very far away".
First try gives me:
... XML Parsing Error: no root element found Location: https://git.ipfire.org/ Line Number 27, Column 1:
^ ...
Second try: A white page with "git://git.ipfire.org" and a project search box.
Third try: Same as first: "XML Parsing error..."
Any one else?
Best, Matthias
Since we are having some things we can do better with our many web servers, I started using haproxy on our primary firewall and everything else is now being proxies from there to the right internal server.
That means, that the git repositories are now coming directly from the server where they are hosted and are not being transferred over NFS first. Same goes for downloads. That puts quite a bit less load on the servers and makes the downloads slightly faster.
I also moved Gitweb to a new server which is now running Apache and not nginx any more. However, apache doesn't correctly cache the index page. I don't know why that is, but it is just being stupid. Hence the slight delay to render the page.
Best, -Michael
On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
On 04.08.2018 15:54, Michael Tremer wrote:
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
Besides, since a few days loading git.ipfire.org takes about 15-20 seconds. FF shows "Transferring data from git.ipfire.org" and nothing happens...
Migration!?
Best, Matthias
Hello,
same here... Sometimes with, sometimes without an XML parsing error.
Best regards, Peter Müller
Hi,
On 05.08.2018 12:24, Michael Tremer wrote:
Errr, no. This is not migrating any more, but has been migrated.
As it seems - it migrated "very far away".
First try gives me:
... XML Parsing Error: no root element found Location: https://git.ipfire.org/ Line Number 27, Column 1:
^ ...
Second try: A white page with "git://git.ipfire.org" and a project search box.
Third try: Same as first: "XML Parsing error..."
Any one else?
Best, Matthias
Since we are having some things we can do better with our many web servers, I started using haproxy on our primary firewall and everything else is now being proxies from there to the right internal server.
That means, that the git repositories are now coming directly from the server where they are hosted and are not being transferred over NFS first. Same goes for downloads. That puts quite a bit less load on the servers and makes the downloads slightly faster.
I also moved Gitweb to a new server which is now running Apache and not nginx any more. However, apache doesn't correctly cache the index page. I don't know why that is, but it is just being stupid. Hence the slight delay to render the page.
Best, -Michael
On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
On 04.08.2018 15:54, Michael Tremer wrote:
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
Besides, since a few days loading git.ipfire.org takes about 15-20 seconds. FF shows "Transferring data from git.ipfire.org" and nothing happens...
Migration!?
Best, Matthias
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
I created a ticket to have a look at it later:
https://bugzilla.ipfire.org/show_bug.cgi?id=11818
- -Michael
On Sun, 2018-08-12 at 09:10 +0200, Peter Müller wrote:
Hello,
same here... Sometimes with, sometimes without an XML parsing error.
Best regards, Peter Müller
Hi,
On 05.08.2018 12:24, Michael Tremer wrote:
Errr, no. This is not migrating any more, but has been migrated.
As it seems - it migrated "very far away".
First try gives me:
... XML Parsing Error: no root element found Location: https://git.ipfire.org/ Line Number 27, Column 1:
^ ...
Second try: A white page with "git://git.ipfire.org" and a project search box.
Third try: Same as first: "XML Parsing error..."
Any one else?
Best, Matthias
Since we are having some things we can do better with our many web servers, I started using haproxy on our primary firewall and everything else is now being proxies from there to the right internal server.
That means, that the git repositories are now coming directly from the server where they are hosted and are not being transferred over NFS first. Same goes for downloads. That puts quite a bit less load on the servers and makes the downloads slightly faster.
I also moved Gitweb to a new server which is now running Apache and not nginx any more. However, apache doesn't correctly cache the index page. I don't know why that is, but it is just being stupid. Hence the slight delay to render the page.
Best, -Michael
On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
On 04.08.2018 15:54, Michael Tremer wrote:
I just spent two hours to debug this fe**cking thing. It was a configuration issue that was caused by the migration.
Besides, since a few days loading git.ipfire.org takes about 15-20 seconds. FF shows "Transferring data from git.ipfire.org" and nothing happens...
Migration!?
Best, Matthias
-
Matthias Fischer -
Michael Tremer -
Peter Müller -
ummeegge