How to merge .pacnew files?

Support
1

   ~  pacnew file found for /etc/default/grub  :heavy_check_mark:
zsh: command not found: pacnew
   ~  sudo DIFFPROG=diff pacdiff|result=  127 ✘
[sudo] password for alexbespik:
   ~  sudo DIFFPROG=diff pacdiff|result=  PIPE ✘
==> pacnew file found for /etc/default/grub
zsh: = not found
   ~   PIPE ✘

2

  1. Install pacnew-chaser from the AUR. It integrates well with Plasma and it’s a lot easier to use than the command-line variants.

  2. When posting command-line output when your system is not installed in English, prepend your commands with “LC_ALL=C”. This will make it more readable to other forum members. :wink:

3

:bangbang: Tip: :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

1 Like
4

My system is in English

5

In that case, see @Mirdarthos’ post above. :point_up_2:

6

manjaro-pacnew-checker also works pretty well

1 Like
7

The command is actually

pacdiff -s

and sudo is handled automatically. If you want a gui you can install meld for example, then it will be
DIFFPROG=meld pacdiff -s

And compare very carefully the 2 files before making changes and ask first if unsure. And then run sudo update-grub

8

You need no other App

DIFFPROG=sdiff pacdiff -s
9

And if folks set the environment variable then DIFFPROG would not be needed as a preface.
(if unset then it defaults to vim -d)

10

Curios fact: not everybody likes to work with vim. Especially inexperienced users.

1 Like
11

Related curiosity.

12

Oh somehow I’ve missed the never-remarked upon “how do I exit vim?” and other such things. Its even better since manjaro doesnt ship vim by default so it would just fail. :wink:

The point wasnt to suggest using vim. But rather to suggest users configure environment variables.
ex:
/etc/environment

#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
# Editors
EDITOR=/usr/bin/micro
SUDO_EDITOR=/usr/bin/micro
DIFFPROG=/usr/bin/meld
# Portals
GTK_USE_PORTAL=1
GDK_DEBUG=portals
# Less Debug Logging
QT_LOGGING_RULES="*.debug=false"
# Some hidpi stuff for QT
QT_AUTO_SCREEN_SCALE_FACTOR=1
QT_ENABLE_HIGHDPI_SCALING=1
# If enabled (along with above) things get huge
#PLASMA_USE_QT_SCALING=1
# HW-accel for gstreamer by ignoring white-list
GST_VAAPI_ALL_DRIVERS=1
# wine stuff 
WINEDLLOVERRIDES="mscoree=d;mshtml=d;winemenubuilder.exe=d"
# Disable GNOME Accessibility bus
NO_AT_BRIDGE=1

Then things like sudoedit and pacdiff dont need the extra ENV=VAR syntax … it will use your choice.

4 Likes