diff --git a/app-containers/lazydocker/metadata.xml b/app-containers/lazydocker/metadata.xml
index daf4c5d..46dec1d 100644
--- a/app-containers/lazydocker/metadata.xml
+++ b/app-containers/lazydocker/metadata.xml
@@ -1,28 +1,28 @@
-
- torokhov-s-a@yandex.ru
- Sergey Torokhov
-
-
- A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
- Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
- Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
- Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
- Right so the service must have just stopped immediately after starting.
- I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
- I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
- I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
- but now I've got one service hogging a terminal window even after I no longer care about its logs.
- I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
- Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
- What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
- Keeping track of your containers across multiple terminal windows is near impossible.
- What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
- Lazydocker's goal is to make that dream a reality.
-
-
- jesseduffield/lazydocker
-
+
+ torokhov-s-a@yandex.ru
+ Sergey Torokhov
+
+
+ A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
+ Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
+ Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
+ Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
+ Right so the service must have just stopped immediately after starting.
+ I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
+ I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
+ I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
+ but now I've got one service hogging a terminal window even after I no longer care about its logs.
+ I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
+ Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
+ What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
+ Keeping track of your containers across multiple terminal windows is near impossible.
+ What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
+ Lazydocker's goal is to make that dream a reality.
+
+
+ jesseduffield/lazydocker
+
diff --git a/app-text/calibre/calibre-7.24.0.ebuild b/app-text/calibre/calibre-7.24.0.ebuild
index fa53647..74a257a 100644
--- a/app-text/calibre/calibre-7.24.0.ebuild
+++ b/app-text/calibre/calibre-7.24.0.ebuild
@@ -215,10 +215,10 @@ src_test() {
src_install() {
# Bug #352625 - Some LANGUAGE values can trigger the following ValueError:
- # File '/usr/lib/python2.6/locale.py', line 486, in getdefaultlocale
- # return _parse_localename(localename)
- # File '/usr/lib/python2.6/locale.py', line 418, in _parse_localename
- # raise ValueError, 'unknown locale: %s' % localename
+ # File '/usr/lib/python2.6/locale.py', line 486, in getdefaultlocale
+ # return _parse_localename(localename)
+ # File '/usr/lib/python2.6/locale.py', line 418, in _parse_localename
+ # raise ValueError, 'unknown locale: %s' % localename
#ValueError: unknown locale: 46
export -n LANG LANGUAGE ${!LC_*}
export LC_ALL=C.utf8 # bug #709682
diff --git a/dev-vcs/lazygit/metadata.xml b/dev-vcs/lazygit/metadata.xml
index daf4c5d..46dec1d 100644
--- a/dev-vcs/lazygit/metadata.xml
+++ b/dev-vcs/lazygit/metadata.xml
@@ -1,28 +1,28 @@
-
- torokhov-s-a@yandex.ru
- Sergey Torokhov
-
-
- A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
- Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
- Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
- Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
- Right so the service must have just stopped immediately after starting.
- I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
- I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
- I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
- but now I've got one service hogging a terminal window even after I no longer care about its logs.
- I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
- Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
- What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
- Keeping track of your containers across multiple terminal windows is near impossible.
- What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
- Lazydocker's goal is to make that dream a reality.
-
-
- jesseduffield/lazydocker
-
+
+ torokhov-s-a@yandex.ru
+ Sergey Torokhov
+
+
+ A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
+ Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
+ Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
+ Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
+ Right so the service must have just stopped immediately after starting.
+ I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
+ I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
+ I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
+ but now I've got one service hogging a terminal window even after I no longer care about its logs.
+ I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
+ Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
+ What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
+ Keeping track of your containers across multiple terminal windows is near impossible.
+ What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
+ Lazydocker's goal is to make that dream a reality.
+
+
+ jesseduffield/lazydocker
+