Mike Gilbert writes:
> On Sun, Jun 25, 2023 at 2:52 PM Michał Górny wrote:
>>
>> I think a better approach would be to always include $? in die messages
>> in Portage.
>
> It's a nice idea, but will not work in the case where die is not
> called immediately after the failing command.
>
> A coup
"Anna (cybertailor) Vyalkova" writes:
> Hi lists,
>
> You might know about the `app-portage/metagen` utility that generates
> metadata.xml files with your name and email. But there was no tool that
> autofilled upstream information, so I wrote it.
>
> Using it is as simple as:
>
> $ gentle
Hi lists,
You might know about the `app-portage/metagen` utility that generates
metadata.xml files with your name and email. But there was no tool that
autofilled upstream information, so I wrote it.
Using it is as simple as:
$ gentle foo-0.1.ebuild
You can install it as `app-portage/ge
On Sun, Jun 25, 2023 at 2:52 PM Michał Górny wrote:
>
> I think a better approach would be to always include $? in die messages
> in Portage.
It's a nice idea, but will not work in the case where die is not
called immediately after the failing command.
A couple of possible workarounds that could
On Sun, Jun 25, 2023 at 20:52:53 +0200, Michał Górny wrote:
> I think a better approach would be to always include $? in die messages
> in Portage.
>
I'm not sure the exit code is useful in the general case. Something like
rm(1) seems to give the same exit code despite failing for different
reaso
I think a better approach would be to always include $? in die messages
in Portage.
--
Best regards,
Michał Górny
Signed-off-by: Mike Gilbert
---
eclass/acct-group.eclass | 2 +-
eclass/acct-user.eclass | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/eclass/acct-group.eclass b/eclass/acct-group.eclass
index 8d2d3adb7221..a0ad86066309 100644
--- a/eclass/acct-group.eclass
+++ b/ecl
On Sun, Jun 25, 2023 at 6:54 AM Florian Schmaus wrote:
> No strong opinion, but it is often a good idea to include the exit
> status. For example:
>
> die "usermod failed (${status})"
That's a really good idea. It could also be applied to the
useradd/groupadd/groupmod comm
On Sun, 2023-06-25 at 16:58 +0300, Joonas Niilola wrote:
> Hey,
>
> these packages are up for grabs:
>
Brian was the last member of the PHP project, so most of those packages
are now unmaintained too. I'm co-maintainer on a few of them but Brian
did most of the work.
Hey,
these packages are up for grabs:
dev-db/mycli
dev-libs/judy
dev-util/imediff2
lxde-base/lxdm
mail-client/s-nail
mail-filter/amavisd-milter
net-misc/omnisync
sys-power/acpilight
They're in pretty good state. lxdm has bunch of bugs open, some others
were eligible for python-3.12 compatibility
On 24/06/2023 19.01, Mike Gilbert wrote:
usermod refuses to update the home directory for a user with running
processes. Output a more helpful message and avoid calling die for this.
For other usermod failures, output stderr as an eerror message and die.
Example output:
* Failed to update us
# James Le Cuirot (2023-06-25)
# Impossible to legally obtain the native full game now. It freezes on keyboard
# input, is incompatible with PipeWire, and requires gamescope to display under
# Wayland. In short, it's a lost cause. Removal in 30 days. Bug #436140.
games-action/descent3
games-action
12 matches
Mail list logo
