Skip to main content ↑ ↓
Topic: Another update FAIL. (Read 1237 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Another update FAIL.

Today I updated system and got this error:
"warning: /etc/locale.gen installed as /etc/locale.gen.pacnew"

Should I manually intervene? Are any localizations are now broken? Why is it like this? What is the fix?

Its getting more and more annoying. A lot of updates start to fail now.

Re: Another update FAIL.

Reply #1 –
What error do you get when the update fails?

Also that warning is normal, I get it for stuff like the pacman mirrorlist file.

The localizations aren't broken, its just that now there is a newer locale.gen file which you can either ignore or copy it over the older locale.gen and use it.

Re: Another update FAIL.

Reply #2 –
That's completely normal pacman behavior. See the archwiki on this.

Re: Another update FAIL.

Reply #3 –
Thank you for the answers and the link to Archwiki. I was aware of pacnew but never about  "new locale", which I don't recall ever touching (Although I had removed all locales leaving 2 or 3 locales).

Anyway I will override the old one with the new.

P.S. Is there any way to tell pacman to ignore locales (when I don't have them, because I had removed them) while updating so it doesn't spill out endless errors that locales are missing (while doing pacman -Syu)?
 

Re: Another update FAIL.

Reply #4 –
Ouch! I also found THIS:

/etc/default/grub.pacnew

Since it being GRUB, I am scared to touch it. ( I have my own config in GRUB, i.e some lines and specific setups I did during installation whan it was generated).

What would be the CORRECT PRCEDURE now, not to f... it up!

Re: Another update FAIL.

Reply #5 –
Quote from: Runner – on

What would be the CORRECT PRCEDURE now, not to f... it up!

Quite frankly, to read up on some basics, such as pacman.

https://wiki.archlinux.org/title/Pacman

https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave

https://wiki.archlinux.org/title/Pacman/Rosetta



You ask so many questions in one thread, you could really answer them yourself by just reading these.
That's the point of a wiki.

If the wikis don't help with a problem, kind artix users will surely try to help.
But please read up.

Re: Another update FAIL.

Reply #6 –
There is nothing about grub.pacnew  in those wiki links. And its grub. Touching GRUB for most times breaks the system. There is always 99% of chance to break the system and not being able to boot it, hence my question. What DID YOU do on YOUR system with GRUB.PACNEW?

There are linux default loads UUIDs etc. You would like me to break it? Should I delete old one and leave the new one with the old one's name? Wouldn't that break the system?

Re: Another update FAIL.

Reply #7 –
OP it doesn't sound like you've had a update fail at all.
There's already been one link posted https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave
Which explains why .pacnew files are created. This is pacman working as intended not pacman failing.

As you've said you've made changes to /etc/default/grub .
I'd hazard a guess you'd be even more annoyed if due to the default packaged version of /etc/default/grub changing in the package pacman just replaced your customised version with its new version.
So it doesn't, it saves it with a .pacnew extension so that you can compare the changes at your leisure.

I've just had a look and I've 8 .pacnew files under /etc. The oldest of which have been there since December 2021 (I'm lazy I guess).

Let's take one of these /etc/pacman.conf.pacnew
Code: [Select]
diff -u /etc/pacman.conf /etc/pacman.conf.pacnew
Code: [Select]
--- /etc/pacman.conf    2022-06-02 10:17:24.816749191 +0100
+++ /etc/pacman.conf.pacnew     2022-05-09 18:24:23.000000000 +0100
@@ -22,7 +22,7 @@
 Architecture = auto
 
 # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
-IgnorePkg   = linux linux-headers
+#IgnorePkg   =
 #IgnoreGroup =
 
 #NoUpgrade   =
@@ -30,7 +30,7 @@
 
 # Misc options
 #UseSyslog
-Color
+#Color
 #NoProgressBar
 CheckSpace
 #VerbosePkgLists
@@ -90,46 +90,11 @@
 #[lib32-gremlins]
 #Include = /etc/pacman.d/mirrorlist
 
-[lib32]
-Include = /etc/pacman.d/mirrorlist
+#[lib32]
+#Include = /etc/pacman.d/mirrorlist
 
 # An example of a custom package repository.  See the pacman manpage for
 # tips on creating your own repositories.
 #[custom]
 #SigLevel = Optional TrustAll
 #Server = file:///home/custompkgs
-
-[universe]
-Server = https://universe.artixlinux.org/$arch
-
-
-### Arch
-
-
-#[testing]
-#Include = /etc/pacman.d/mirrorlist-arch
-
-
-[extra]
-Include = /etc/pacman.d/mirrorlist-arch
-
-
-#[community-testing]
-#Include = /etc/pacman.d/mirrorlist-arch
-
-
-[community]
-Include = /etc/pacman.d/mirrorlist-arch
-
-
-#[multilib-testing]
-#Include = /etc/pacman.d/mirrorlist-arch
-
-
-[multilib]
-Include = /etc/pacman.d/mirrorlist-arch
-
-#[home_post-factum_kernels_Arch]
-#Server = https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/$arch
I can easily see from that the the only changes are my own and I can simply delete the .pacnew file.

So just compare the files (you can use a gui diff tool if you prefer). If there are differences you don't understand come back and ask about them specifically.

Re: Another update FAIL.

Reply #8 –
"What DID YOU do on YOUR system with GRUB.PACNEW?"
Ignore them mostly, personally. If I'm feeling bored I might merge in my mods to the new files once in a while, or if it throws up any problems. /etc/nanorc will often eventually cause complaints from nano when it starts about unsupported options if you ignore the pacnew's for long enough, for example. You can get packages to auto-merge them on updates I think. This is not best practice obviously, you should  ideally diff the new files and add in your changes, potentially you might update into problems. But generally, 99.99% of the time, who cares if there's a new locale option for some weird Martian language or whatever, I'm not using it anyway, it won't matter.  ;D

Re: Another update FAIL.

Reply #9 –
>>There is nothing about grub.pacnew  in those wiki links.

Because you still haven't understood the concept of pacnew files.

>> Touching GRUB for most times breaks the system. There is always 99% of chance to break the system and not being able to boot it, hence my question. What DID YOU do on YOUR system with GRUB.PACNEW?

Either:
  • Run diff(1) and see if the differences are harmless
or
  • Ignore it

>>You would like me to break it?

Not if you actually listen to what we say.

Re: Another update FAIL.

Reply #10 –
Thanks for the answers. My best tool is Kate plugin. It has nice colors. For the time being I don't need to merge those GRUBs.

I'd rather have automatic tools to do it for me while keeping my settings intact (e.g. UUIDs for booting the system). I had some troubles with profiles on Gentoo in the past. Some long time ago I also merged manually something on Artix (can't remeber what).

 I like to have my systems to be kept neat and in order, even if its a rolling distro. Anyway there is a tool from Gentoo for merging and its compatible with Arch. I might look into it. For the time being kdiff3 plugin for Kate will do it. Manually :(.

Here how its handled on DEBIAN:
You don't update with new packages, you update with "--with-new-pkgs" at your convenience. When you do it and  there is a new GRUB, for example, (update for security reasons) you get nice blue reconfiguration "pop-up" in terminal. You can use arrows and space and do the reconfiguration, so the system will NOT fail at boot :). Some services with apt-get also had some reconfiguration "popups".  Pacman should have similar functionality. It would be a much nicer way, because some day old config files will break software and will not be compatible. Perks of rolling.

Re: Another update FAIL.

Reply #11 –
Quote from: Runner – on
Thanks for the answers. My best tool is Kate plugin. It has nice colors. For the time being I don't need to merge those GRUBs.

I'd rather have automatic tools to do it for me while keeping my settings intact (e.g. UUIDs for booting the system). I had some troubles with profiles on Gentoo in the past. Some long time ago I also merged manually something on Artix (can't remeber what).

 I like to have my systems to be kept neat and in order, even if its a rolling distro. Anyway there is a tool from Gentoo for merging and its compatible with Arch. I might look into it. For the time being kdiff3 plugin for Kate will do it. Manually :(.

Here how its handled on DEBIAN:
You don't update with new packages, you update with "--with-new-pkgs" at your convenience. When you do it and  there is a new GRUB, for example, (update for security reasons) you get nice blue reconfiguration "pop-up" in terminal. You can use arrows and space and do the reconfiguration, so the system will NOT fail at boot :). Some services with apt-get also had some reconfiguration "popups".  Pacman should have similar functionality. It would be a much nicer way, because some day old config files will break software and will not be compatible. Perks of rolling.




Well this is arch after all, not debian.  Arch typically has an entry point that 'you must be this tall to ride this ride' requirement.  That means you have to learn to do things differently.  Arch is not debian.  That much is a fact.  Arch should be like debian is not a philosophical ideal in the minds of most arch users.  I wish you luck though in trying to persuade the arch devs to make a product more like debian.  Have a wonderful day.
Cat Herders of Linux

Re: Another update FAIL.

Reply #12 –
Quote from: cat herders of linux – on

Well this is arch after all, not debian.  Arch typically has an entry point that 'you must be this tall to ride this ride' requirement.  That means you have to learn to do things differently.  Arch is not debian.  That much is a fact.  Arch should be like debian is not a philosophical ideal in the minds of most arch users.  I wish you luck though in trying to persuade the arch devs to make a product more like debian.  Have a wonderful day.

You could tell him why he's wrong instead of espousing elitism and gatekeeping

I do agree with him, its a neat little feature, even though at its core its a simple diff.

It doesn't even have to be part of pacman, you could call in an external program everytime pacman leaves behind .pacnew file.

Still, since there isn't a whole lot of demand for this feature, you have to be willing to create this sort of functionality yourself.

Re: Another update FAIL.

Reply #13 –
Quote from: Lancia – on
You could tell him why he's wrong instead of espousing elitism and gatekeeping

I do agree with him, its a neat little feature, even though at its core its a simple diff.

It doesn't even have to be part of pacman, you could call in an external program everytime pacman leaves behind .pacnew file.

Still, since there isn't a whole lot of demand for this feature, you have to be willing to create this sort of functionality yourself.


I was being elitist?  Ok.  Sorry Runner for coming off elitist.

I do not think it is a lot to ask to read the screen when things are being updated and look at what's being done.  One can adjust the scroll on most terminals so that it's infinite or nearly so, that a person can review all that was done.  Clearly this was explained to them several times what .pacnew meant.  It seemed plain to me that they were choosing wilful ignorance and simply pouting that arch isn't debian.

Sorry for misunderstanding all that i read in the thread and for expecting someone to hear what's being said to them.  Clearly i'm just too intolerant.  Thank you for pointing that out.
Cat Herders of Linux

Re: Another update FAIL.

Reply #14 –
Don't be condescending when you hear another distro name. Scientists look at each other work all the time. It makes the world go forward. Making admins work easier is not a stupid request. If you add up all the nooks and crannies you get a pile as big as Mount Everest. Simply pointing to a neat solution will get me banned from here. Thank you very much for making me go crazy.

I stand by my words:

I would like not to deal with updates error post updates. I would like them to go smoothly. First I update, then I get bunch of errors. Instead of errors it would be nice to give me some "popup" to reconfigure stuff. Some see the issue, some don't. Let there be errors, deal with them after you update, we will not tell you anything. Shouldn't package maintainer know there will be an error when users update the system. He knows! But tell user nothing. I don't care I put a package that breaks your system. Deal with it. Its Arch. It should break the system. NO IT SHOULDN'T.  If the package maintainer gives you new package, he knows it breaks the system, but he chooses to ignore it. And yes Debian people found the solution. Why is it wrong to point to solutions? Isn't that the normal point of conversation? To exchange ideas and point to a solution? I don't understand your attack on me?
Second solution: gentoo people found the solution for Arch (yet to be tested, but I  believe should be native). But we don't talk to them right? We Arch/Artix people hate other people who make other distros.