There are known server issues currently which will be addressed as soon as humanly possible. We have team members on three continents in various time zones, so please bear with us.
FYI, as of about 10 minutes ago, all new kernels and modules are now available. It may take some time for all mirrors to update.
EDIT: Server issues were resolved and itâs even responding faster.
Manjaro Tools linux66-nvidia is no longer in the repoâs ,but it is still in Packages-Mhwd.
Removing this affects lib32-nvidia-utils. Removing both makes the tools build though I suspect lib32-nvidia-utils Is very much needed?
$ mbn info linux66-nvidia -q
Branch : unstable
Name : linux66-nvidia
Version : 560.35.03-6
Repository : extra
Build Date : Fri 13 Sep 2024 08:32:00
Packager : Philip Mueller <philm@manjaro.org>
Branch : testing
Name : linux66-nvidia
Version : 550.107.02-5
Repository : extra
Build Date : Fri 13 Sep 2024 06:13:01
Packager : Philip Mueller <philm@manjaro.org>
Branch : stable
Name : linux66-nvidia
Version : 550.107.02-4
Repository : extra
Build Date : Mon 26 Aug 2024 19:02:05
Packager : Philip Mueller <philm@manjaro.org>
I searched for Linux66-nvidia in pamac and it was not there, just checked now and it is back. no Idea what happened? But it was manjaro-tools that could not find it.
As the comment by @Yochanan says - there has been an issue with the package deployment service - I donât know - that may have caused some issues - perhaps missing packages - in any case it should be solved now.
Not sure if it matters but I have had no issues with updating into this from Stable. Also, this or one of the last few Nvidia driver updates in this branch seems to have mostly fixed my weird stuttering/flickering in some games.
No, it wasnât. The original grub.cfg was backed up as grub.cfg.pacsave, however during the update process, grub.cfg wonât exist until the hooks complete and itâs regenerated. That happens during a grub package update regardless, so whatever issue you had is not related to the Pacsave at all.
The original grub.cfg was backed up as grub.cfg.pacsave
At the filesystem level, a move is the same as a rename. pacman âbacks upâ the old file, and to do so it moves (renames) it. Same result
⌠however during the update process, grub.cfg wonât exist until the hooks complete and itâs regenerated. That happens during a grub package update regardless, so whatever issue you had is not related to the Pacsave at all.
For some reason, this didnât happen in this instance. Itâs not clear why, but only the 90-mkinitcpio-install.hook ran. If youâre curious, hereâs the pacman log.
For what itâs worth, I saved the grub.cfg.pacsave and compared it with the new one generated with sudo update-grub, just to see if anything changed. It turns out, they were identical:
Virtualbox upgrade to 7.1.0-1 went well. All modules have been updated to 7.1.
Upon starting a VM, I get the following:
Display Error:
Failed to change display parameter.
The console is not powered up (setVideoModeHint).
Result Code:
E_ACCESSDENIED (0x80070005)
Component:
DisplayWrap
Interface:
IDisplay {4680b2de-8690-11e9-b83d-5719e53cf1de}
This occurs with all my VMâs upon start. Closing the Notification and all works just fine.
Updated to pacman-6.1.0-8 and merged the pacdiff for /etc/pacman.conf (specifically, the SyncFirst option).
Iâm using rebuild-detector, and during the post-hook it reports that the SyncFirst option is unknown:
(3/3) Checking which packages need to be rebuilt
warning: config /etc/pacman.conf line 20: unknown option 'SyncFirst'
warning: config /etc/pacman.conf line 20: unknown option 'SyncFirst'
[...]
Taking a look into it, it seems that the output is from pacconf.
Ping at @philm, since he did the pacman patches for SyncFirst yesterday.
I was just coming here to report that. I can confirm the issue since I updated today. The setting exists in the package default config file pacman.conf.
