DEV Community: Motouom Victor

apt error: unable to use apt on ubuntu.

Motouom Victor — Fri, 09 Aug 2024 08:15:45 +0000

You get an error like this or similar to this when you run any apt command.

E: Conflicting values set for option Signed-By regarding source https://apt.postgresql.org/pub/repos/apt/ noble-pgdg: /usr/share/postgresql-common/pgdg/apt.postgresql.org.asc != /usr/share/postgresql-common/pgdg/apt.postgresql.org.gpg
E: The list of sources could not be read.

- What is the error message telling us?
The error message indicates a conflict with the Signed-By option regarding the source https://apt.postgresql.org/pub/repos/apt/. Specifically, it states that the GPG key used to sign the repository (/usr/share/postgresql-common/pgdg/apt.postgresql.org.asc) is different from the one it expects (/usr/share/postgresql-common/pgdg/apt.postgresql.org.gpg).

- This could be due to a few possible reasons:
The GPG key used to sign the PostgreSQL repository has been changed or updated, but the system's configuration has not been updated accordingly.
There is a conflict or issue with the system's package management configuration, potentially caused by other repositories or packages.

- Here is how to go about it. There are several ways to fix it, but I'll give the one that best works for me and is always sure to work.

Steps

- cd into the **sources.list.d directory.**

cd /etc/apt/sources.list.d

- list all the files found in the directory

ls

alexlarsson-ubuntu-flatpak-noble.sources
archive_uri-https_packages_microsoft_com_repos_vscode-noble.list
flatpak-ubuntu-stable-noble.sources
google-chrome.list
hashicorp.list
pgdg.list
pgdg.sources
touchegg-ubuntu-stable-noble.sources
ubuntu-esm-apps.sources
ubuntu-esm-infra.sources
ubuntu.sources
ubuntu.sources.curtin.orig
vscode.list

Note: The list of the files will vary depending on what causes your error to appear. You then need to open the files and delete any file that has to do with gpg. In my case, it was the PostgreSQL files that were causing those errors

- cat the files one after another if you do not know which one to look into in my case I had to delete any file that has to do with gpg in the sources.list.d directory.

cat pgdg.sources

result

Types: deb
URIs: https://apt.postgresql.org/pub/repos/apt
Suites: noble-pgdg
Components: main
Signed-By: /usr/share/postgresql-common/pgdg/apt.postgresql.org.gpg

sudo rm pgdg.sources

cat pgdg.list

result

deb [signed-by=/usr/share/postgresql-common/pgdg/apt.postgresql.org.asc] https://apt.postgresql.org/pub/repos/apt noble-pgdg main

 sudo rm pgdg.list

- After removing all the files, you can now try running the update command or any apt command again.

sudo apt update

result

Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease         
Hit:3 https://apt.releases.hashicorp.com noble InRelease       
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease  
Hit:5 https://esm.ubuntu.com/apps/ubuntu noble-apps-security InRelease
Hit:6 http://archive.ubuntu.com/ubuntu noble-updates InRelease 
Hit:7 https://packages.cloud.google.com/apt cloud-sdk InRelease
Ign:8 https://ppa.launchpadcontent.net/alexlarsson/flatpak/ubuntu noble InRelease
Hit:9 https://esm.ubuntu.com/apps/ubuntu noble-apps-updates InRelease
Hit:10 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu noble InRelease
Hit:11 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Hit:12 https://packages.microsoft.com/repos/vscode stable InRelease
Hit:13 https://esm.ubuntu.com/infra/ubuntu noble-infra-security InRelease
Hit:14 https://ppa.launchpadcontent.net/touchegg/stable/ubuntu noble InRelease
Hit:15 https://packages.microsoft.com/repos/code stable InRelease
Hit:16 https://esm.ubuntu.com/infra/ubuntu noble-infra-updates InRelease
Err:17 https://ppa.launchpadcontent.net/alexlarsson/flatpak/ubuntu noble Release
  404  Not Found [IP: 185.125.190.80 443]
Reading package lists... Done

Burn ISO to USB on Mac all versions - ALWAYS WORKS

Motouom Victor — Thu, 01 Aug 2024 10:17:41 +0000

On Mac, it is not possible to download and install power iso and burn images so to do this easily, we can do it on the terminal which is faster, easier, and convenient.
Below are the steps that you need to follow to accomplish this.

1. Before plugging in the drive, you need to see the available ones on the device first. To do that, run the command

 diskutil list

you should have an output that resembles this

❯ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         500.1 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.1 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume APPLE SSD SM0512G Me... 170.9 GB   disk1s1
   2:                APFS Volume Preboot                 447.3 MB   disk1s2
   3:                APFS Volume Recovery                1.1 GB     disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
   5:                APFS Volume APPLE SSD SM0512G Media 15.4 GB    disk1s5
   6:              APFS Snapshot com.apple.os.update-... 15.4 GB    disk1s5s1

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +6.1 GB     disk3
   1:       Microsoft Basic Data                         6.1 GB     disk3s1
   2:                        EFI ESP                     5.2 MB     disk3s2
   3:       Microsoft Basic Data                         307.2 KB   disk3s3

2. Insert the drive and run the command again.

❯ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         500.1 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.1 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume APPLE SSD SM0512G Me... 170.9 GB   disk1s1
   2:                APFS Volume Preboot                 447.3 MB   disk1s2
   3:                APFS Volume Recovery                1.1 GB     disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
   5:                APFS Volume APPLE SSD SM0512G Media 15.4 GB    disk1s5
   6:              APFS Snapshot com.apple.os.update-... 15.4 GB    disk1s5s1

_**/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *61.9 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:       Microsoft Basic Data Untitled                61.7 GB    disk2s2**_

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +6.1 GB     disk3
   1:       Microsoft Basic Data                         6.1 GB     disk3s1
   2:                        EFI ESP                     5.2 MB     disk3s2
   3:       Microsoft Basic Data                         307.2 KB   disk3s3

You will notice that there is an additional disk on the list of disk. Take note of the drive since you will use it in the process. For me, the drive is /dev/disk2

3. unmount the disk to begin the process. For this, you have various commands and can try any of them if the others give you an error like

zsh: command not found: unmount
zsh: command not found: unmountDisk
or a similar error

unmount /dev/disk2

unmountDisk /dev/disk2

 diskutil unmountDisk /dev/disk2

4. After unmounting the drive, you now burn the iso file into the drive using the command

sudo dd bs=1m if=~/Users/gis/Downloads/ubuntu-24.04-desktop-amd64.iso of=/dev/rdisk2

NB: ~/Users/gis/Downloads/ubuntu-24.04-desktop-amd64.iso is the path to the image you wish to burn and /dev/rdisk2 is the drive in which you are burning it into

after running the above command, you wait for about 5 - 10 minutes then you will see a message like

5831+1 records in
5831+1 records out
6114656256 bytes transferred in 579.370318 secs (10553969 bytes/sec)

5. After completion, run the command

diskutil eject /dev/disk2

This will eject the drive from your machine. remove the drive and then insert it again.

And there we go, you now have a flash drive burnt in a mac device.

npm run dev gives an error.

Motouom Victor — Sat, 27 Jul 2024 09:27:03 +0000

We often encounter the error below when trying to start our react app.


packit-frontend@0.0.0 dev
vite

file:///home/ariel/Desktop/PackIt/PackIt-frontend/node_modules/vite/bin/vite.js:7
    await import('source-map-support').then((r) => r.default.install())
    ^^^^^

SyntaxError: Unexpected reserved word
    at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
    at async link (internal/modules/esm/module_job.js:42:21)

This error is often caused by your node version being below the expected version. Below are some guides to help you fix that:

check your node version.

node -v

if your node version is lower than version 21, I will recommend you install node 21 or greater.

nvm install 21

After the installation is done, you can now use the version 21.

nvm use 21

Run the app again with

npm run dev

and the expected result should be:


> packit-frontend@0.0.0 dev
> vite


  VITE v5.3.4  ready in 222 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help