Programs won't auto-build after 11072021 Testing updates

I have a handful of programs that have to be built and then installed. Now ever since the Testing updates on the 7th I’ll get ask if I want to preview the changes. I tell it no and get asked if I want to try again instead of it building and installing. Was this a deliberate change or did the updates from the 7th break something?

    ~  inxi -Fxxxza                                                         ✔ 
System:
  Kernel: 5.15.2-2-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
  parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.15-x86_64
  root=UUID=0e474eb0-4b46-41af-8757-51221e62c250 rw rootflags=subvol=@ quiet
  apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
  Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
  Mobo: ASUSTeK model: ROG STRIX B550-F GAMING v: Rev X.0x serial: <filter>
  UEFI: American Megatrends v: 2423 date: 08/10/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter>
  charge: 55% (should be ignored) rechargeable: yes status: Discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360
  serial: <filter> charge: 100% (should be ignored) rechargeable: yes
  status: Discharging
CPU:
  Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2
  family: 17 (23) model-id: 71 (113) stepping: 0 microcode: 8701021 cache:
  L2: 3 MiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 86272
  Speed: 3468 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz):
  1: 3468 2: 3862 3: 2195 4: 2197 5: 2094 6: 2196 7: 2201 8: 2195 9: 2165
  10: 3910 11: 2035 12: 2193
  Vulnerabilities: Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
  mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:
  conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: eVga.com.
  driver: nvidia v: 495.44 alternate: nouveau,nvidia_drm bus-ID: 08:00.0
  chip-ID: 10de:2187 class-ID: 0300
  Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver:
  loaded: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1080 s-dpi: 97 s-size: 670x283mm (26.4x11.1")
  s-diag: 727mm (28.6")
  Monitor-1: HDMI-0 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2")
  diag: 730mm (28.8")
  OpenGL: renderer: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2
  v: 4.6.0 NVIDIA 495.44 direct render: Yes
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: eVga.com.
  driver: snd_hda_intel v: kernel bus-ID: 08:00.1 chip-ID: 10de:1aeb
  class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel
  v: kernel bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.2-2-MANJARO running: yes
  Sound Server-2: sndio v: N/A running: no
  Sound Server-3: JACK v: 1.9.19 running: no
  Sound Server-4: PulseAudio v: 15.0 running: yes
  Sound Server-5: PipeWire v: 0.3.40 running: yes
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
  port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 20.82 TiB used: 11.51 TiB (55.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Seagate model: XPG GAMMIX S11 Pro
  size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
  lanes: 4 type: SSD serial: <filter> rev: 32B3T8EB temp: 33.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Patriot model: Viper M.2 VPN100
  size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
  lanes: 4 type: SSD serial: <filter> rev: ECFM22.6 temp: 30.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Seagate
  model: ST8000AS0002-1NA17Z size: 7.28 TiB block-size: physical: 4096 B
  logical: 512 B type: HDD rpm: 5980 serial: <filter> scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate
  model: ST3000DM 001-1E6166 size: 2.73 TiB block-size: physical: 4096 B
  logical: 512 B type: N/A serial: <filter> rev: 7101 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-5: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: ST330006 51NS
  size: 2.73 TiB block-size: physical: 4096 B logical: 512 B type: N/A
  serial: <filter> rev: 7101 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-6: /dev/sdd maj-min: 8:48 type: USB vendor: Seagate model: Expansion HDD
  size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: N/A
  serial: <filter> rev: 1801 scheme: GPT
  ID-7: /dev/sde maj-min: 8:64 type: USB vendor: PNY model: USB 3.0 FD
  size: 115.38 GiB block-size: physical: 512 B logical: 512 B type: N/A
  serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
  used: 93.54 GiB (19.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
  used: 568 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:2
  ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
  used: 93.54 GiB (19.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
  used: 93.54 GiB (19.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
  file: /swap/swapfile
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 400 Uptime: 3h 41m wakeups: 43 Memory: 31.33 GiB
  used: 7.27 GiB (23.2%) Init: systemd v: 249 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: 1701 pacman: 1657 lib: 446 flatpak: 33 snap: 11
  Shell: Zsh v: 5.8 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.08

What are you talking about?
Your own packages? Packages in the AUR I suppose?
But how do you mean - in your AUR helper like yay, or pamac ?
You may need to be a bit more descriptive with the ‘issue’ here.

I launch pamac from the systray to check what updates are available when it indicates there are updates, then I launch Konsole and run Topgrade to update everything. Since the updates from the 7th for programs that get built and then installed I get asked if I want to preview differences, I tell it no and get asked if I want to try again instead of the program being built and installed, and if I tell it yes it runs through the differences and still doesn’t autobuild and install the update. Now if I turn around and run yay -Sy it will build and install.

Maybe report an issue at topgrade GitHub then? Try to downgrade topgrade from the previous package in your cache to see if problem comes from its last version?

Then thats a problem with topgrade.
If it doesnt work … then consider using something else.

Really - such a tool is not really encouraged.

Dont use yay like this.
Or anything really … always upgrade when you sync.
(arguably dont use aur helpers for repo upgrades at all, ex: sudo pacman -Syu && yay -Sua)

I’m sure it’s a Manjaro issue since just before the testing updates on the 7th the issue didn’t exist, and I personally don believe in coincidences. I just reinstalled Topgrade and will see if the problem persist. If it does I downgrade it and see.

cscs not sure why I posted yay -Sy when I actually used just yay. As for Topgrade it’s a great and reliable program.

Topgrade now uses Paru by default if it’s installed. If you want to use Yay instead, either remove Paru or add the following to ~/.config/topgrade.toml:

arch_package_manager = "yay"
1 Like

That is not how logic works. What version was topgrade before the update? I see it is version 7 on Stable branch, and version 8 on Testing branch. The issue appearing on the Testing branch update does absolutely not mean it is a Manjaro issue, it could absolutely mean it is a topgrade update issue. I gave you an easy way to test the theory, now if you don’t want to do the logical thing and assume because you personally don’t believe in coincidences, as you wish but there was one step to do and you would have your answer.

4 Likes

Thanks, I’ll give that a try and see if it fixes the issue before actually rolling TG back.

As for the post by omano it is incorrect.

What do you mean it’s incorrect?

If Topgrade changed how it works from version 7 to version 8, then it’s a Topgrade problem. What makes it a Manjaro problem?

1 Like

20 days ago it went from 8.0.2 to 8.0.3 not from version 7 to 8.0.3. up till the updates of the 7th it was downloading the build files for programs that need to be built , building the program and installing it without issue. After the 7th this was no longer the case. I’m not saying Manjaro deliberately messed up Topgrade some how. What I am saying is something in the Testing updates from the 7th must of changed something causing Topgrade to to perform normally.

In the testing branch it went from 7.1.0 → 8.0.3 as of of the 2021-11-07 Testing Update.

Again, what changed is Topgrade started using Paru as default and apparently you didn’t notice.

Now there is some info that is actually useful. Now I went to change “arch_package_manager = “paru”” to “arch_package_manager = “yay”” but not seeing that at all in the file.

# Don't ask for confirmations
#assume_yes = true

# Disable specific steps - same options as the command line flag
#disable = ["system", "emacs"]

# Ignore failures for these steps
#ignore_failures = ["powershell"]

# Run specific steps - same options as the command line flag
#only = ["system", "emacs"]

# Do not ask to retry failed steps (default: false)
#no_retry = true

# Run inside tmux
#run_in_tmux = true

# List of remote machines with Topgrade installed on them
#remote_topgrades = ["toothless", "pi", "parnas"]

# Arguments to pass SSH when upgrading remote systems
#ssh_arguments = "-o ConnectTimeout=2"

# Path to Topgrade executable on remote machines
#remote_topgrade_path = ".cargo/bin/topgrade"

# Arguments to pass tmux when pulling Repositories
#tmux_arguments = "-S /var/tmux.sock"

# Do not set the terminal title
#set_title = false

# Cleanup temporary or old files
#cleanup = true

[git]
#max_concurrency = 5
# Additional git repositories to pull
#repos = [
#    "~/src/*/",
#    "~/.config/something"
#]

# Don't pull the predefined git repos
#predefined_repos = false

# Arguments to pass Git when pulling Repositories
#arguments = "--rebase --autostash"

[composer]
#self_update = true

# Commands to run before anything
[pre_commands]
#"Emacs Snapshot" = "rm -rf ~/.emacs.d/elpa.bak && cp -rl ~/.emacs.d/elpa ~/.emacs.d/elpa.bak"

# Custom commands
[commands]
#"Python Environment" = "~/dev/.env/bin/pip install -i https://pypi.python.org/simple -U --upgrade-strategy eager jupyter"

[brew]
#greedy_cask = true

[linux]
# Arguments to pass yay when updating packages
#yay_arguments = "--nodevel"
#trizen_arguments = "--devel"
#enable_tlmgr = true
#emerge_sync_flags = "-q"
#emerge_update_flags = "-uDNa --with-bdeps=y world"
#redhat_distro_sync = false
#rpm_ostree = false

[windows]
# Manually select Windows updates
#accept_all_updates = false
#open_remotes_in_new_terminal = true

# Causes Topgrade to rename itself during the run to allow package managers
# to upgrade it. Use this only if you installed Topgrade by using a package
# manager such as Scoop to Cargo
#self_rename = true

[npm]
# Use sudo if the NPM directory isn't owned by the current user
#use_sudo = true

[firmware]
# Offer to update firmware; if false just check for and display available updates
#upgrade = true

[flatpak]
# Use sudo for updating the system-wide installation
#use_sudo = true

The arch_package_manager value is not in the default config, it must be added manually. It should go in the [linux] section.

Thanks I just uninstalled Paru.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.