I didn't receive any updates for weeks

Hi,

I've replaced my Windows with Manjaro on my laptop for say two weeks.

For me it comes into the spotlight that it seems I don't receive any updates since 20 aprils.
Likely I'm just unpatient.

Is there a RSS feed out there which could inform me when I should run pacman?

you should check mirrors & sync

sudo pacman-mirrors -c Netherlands,Germany

then

sudo pacman -Syy

then

sudo pacman -Syu

https://wiki.manjaro.org/index.php?title=Pacman-mirrors

Yes there is:
Manjaro Forums RSS Feeds – and Why You Might Want it

However, depending on which DE you chose, you SHOULD have notifiers built into Manjaro that run in the Tray and notify you about updates: pacmac-tray-appindicator or octopi-notifier.

2 Likes

In addition, if you don't use any gui updater you can use

or

checkupdates

But possible there is something wrong with your mirrors?

2 Likes

Seems to me that running off to github for your copy of pacman rather than using what came with the distro is probably a bad idea. Best to keep a consistent version that your distro ships and depends on.

Then link No.1 should do.

@all Ok, It seems this forum software doesn't allow me to put up a signature, otherwise I'd link you to Dump your "inxi -Fxxxza --no-host" here and bookmark it

Anyway, I'm running the XFCE distro. I figured out @ https://github.com/manjaro/packages-community that I missed some critical updates. The commands given by @stephane didn't help unfortunately.

Are the repo.stdout-links in this wiki page still up to date? Because once Pamac keep complaining about archive format on and on and I decided to automate it a bit.

#!/bin/bash

fix-pacman-archive-complaining()
{
    MANJARO_PACKAGE=$( curl -s http://repo.stdout.net/manjaro/pool/overlay/ | grep -P -o "manjaro-keyring-\d{8}-\d-any.pkg.tar.xz" | uniq)
    MANJARO_PACKAGE_URL="http://repo.stdout.net/manjaro/pool/overlay/$MANJARO_PACKAGE"
    pacman -U $MANJARO_PACKAGE_URL
    
    ARCH_PACKAGE=$( curl -s http://repo.stdout.net/manjaro/pool/sync/ | grep -P -o "archlinux-keyring-\d{8}-\d-any.pkg.tar.xz" | uniq)
    ARCH_PACKAGE_URL="http://repo.stdout.net/manjaro/pool/sync/$ARCH_PACKAGE"
    pacman -U $ARCH_PACKAGE_URL
    
    rm -fv /var/lib/pacman/sync/*
    pacman -Sy
    pacman -Sy
}

fix-pacman-archive-complaining

try with interactive

sudo pacman-mirrors -gi
select one mirror

then

sudo pacman -Syy

then

sudo pacman -Syu

I've selected the closest one (Netherlands: ftp://ftp.snt.utwente.nl/pub/linux/manjaro/stable) but afterappling sudo pacman -Syy and sudo pacman -Syu pacman still says nothing to do.

Would it help when I post some contents of the conf & log files here? I'll just do it:

/etc/pacman.d/gnupg/gpg.conf

no-greeting
no-permission-warning
lock-never
keyserver hkp://pool.sks-keyservers.net
keyserver-options timeout=10

/etc/pacman.conf

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg      = pacman glibc manjaro-system
# If upgrades are available for these packages they will be asked for first
SyncFirst    = manjaro-system archlinux-keyring manjaro-keyring
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#TotalDownload
# We cannot check disk space from within a chroot environment
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Manjaro Linux
# packagers with `pacman-key --populate archlinux manjaro`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[community]
SigLevel = PackageRequired
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

/etc/pamac.conf

### Pamac configuration file

## When removing a package, also remove those dependencies
## that are not required by other packages (recurse option):
#RemoveUnrequiredDeps

## How often to check for updates, value in hours (0 to disable):
RefreshPeriod = 6

## When there are no updates available, hide the tray icon:
#NoUpdateHideIcon

## Allow Pamac to search and install packages from AUR:
EnableAUR

## When AUR support is enabled search in AUR by default:
#SearchInAURByDefault

## When AUR support is enabled check for updates from AUR:
#CheckAURUpdates

## Do not ask for confirmation when building packages:
#NoConfirmBuild

/etc/yaourtrc

#    yaourtrc  - Configuration for yaourt
#
#   See yaourtrc(5) for more information
#
#

# General
#AUTOSAVEBACKUPFILE=0
#DEVEL=0
#DEVELSRCDIR=""
#FORCE=0
#NO_TESTDB=0

# Environment variables
#EDITOR="$EDITOR"
#TMPDIR="/tmp"
#VISUAL="$VISUAL"

# SUDO
#SUDONOVERIF=0      # Avoid multiple sudo checks when timestamp_timeout=0
#SUDOREDIRECT=1     # Define to 0 in case you use a fingerprint device

# ABS
#USE_GIT=0
# If the package "abs" is installed, those var are parsed from abs.conf
#REPOS=()           # REPOS available at $SYNCSERVER
#SYNCSERVER=""

# AUR
#AURURL="https://aur.archlinux.org"
#AURCOMMENT=5
#AURDEVELONLY=0
#AURSEARCH=1
#AURSHOWDIFF=0
#AURUPGRADE=0
#AURVOTE=1
#AURUSEGIT=0

# Build
EXPORT=2           # Export to 1: EXPORTDIR or PKGDEST
                    # 2: pacman cache (as root)
#EXPORTSRC=0        # Need EXPORT>0 to be used
#EXPORTDIR=""       # If empty, use makepkg's configuration (see makepkg.conf)

# Prompt
#NOCONFIRM=0
#UP_NOCONFIRM=0     # No prompt while build upgrades (including -Sbu)
#BUILD_NOCONFIRM=0  # Only prompt for editing files
#PU_NOCONFIRM=0     # Add --noconfirm to $PACMAN -U
#EDITFILES=1
#NOENTER=1

# Output
#USECOLOR=1
#USEPAGER=0
#DETAILUPGRADE=1
#SHOWORPHANS=1
#TERMINALTITLE=1

# Command
#PACMAN="pacman"
#MAKEPKG="makepkg"
#DIFFEDITCMD="vimdiff"

# pacdiffviewer
#P_LOCATE=0         # Use locate instead of find
#P_SEARCHDIR=(/etc/ /boot/)
#P_SAVEDIR='/var/lib/yaourt/backupfiles'

Please check with the German Mirror Netzspielplatz. This one syncs every 5 minutes.

2 Likes

Negative, pacman still finds that it doesn't have to do anything. But I'll keep that server in mind :slight_smile:

I'll post my /var/log/pacman.log upcoming evening.

I've been having some bad luck with the Dutch mirrors (temporarily unresponsive or not fully synced) and have switched over to the German mirrors. #DeutscheGrundlichkeit

Btw, the last stable update was April 25, so it's been 2 weeks now.

1 Like

Yes, the last stable update was on the 25th of April. We are currently preparing the next one. However, this one might add some new features and might break some stuff. We are always happy to get some feedback from people using the testing branch.

2 Likes

@muvvenby Last week I had problems with Belgian servers, but that seem to be fixed.

Also I got some updates, but for example my system has not the latest version of pale moon while the version at github is even with the official source.

@philm I prefer to have a stable system. Or does packages-community require to be on the testing branch?

Anyway, my /var/log/pacman.log
https://www.zerobin.net/?c12c8e4d8dd32d48#AQDIU+bpvJhCucgo1MT0E4HtQSI5RDjHMbyD984p+mU=

Hopefully you all find some anomalies. My bell didn't rang.

I was already planning on adding two bare metal machines for testing. I need to clean out my desk (probably need to order a skip :wink: ) and buy a kvm switch. Next week hopefully!

@RoestVrijStaal Pale Moon in Git is 27.3.0. The most recent in the stable repo is 27.2.1-1. Is that what you are seeing? That seems normal to me.

@muvvenby Then the stable is outdated, because 27.3.0 is already released : https://www.palemoon.org/releasenotes.shtml And got 27.3.0 already running on my Windows desktop :X

Kinda sad because it fixes also a few CVE's. Is there a "secure" branch which doesn't put versions "on hold" but rather accept it as long as there is a CVE fixed?

The current versions is:

phil@manjaro ~ $ pacman -Q palemoon-bin
palemoon-bin 27.3.0-1

It is part of the testing branch and will soon be merged with our stable branch. You can always switch over to testing when ever you want.

You can join our mailing list to get notified, when ever we add new packages to our branches.

1 Like

Forum kindly sponsored by