Need help understanding package numbers from raw report in Announcements

Regarding the list of package changes in the #announcements :

I can not match the numbers in the summary with the details.

Assumptions

I assume that all packages in the listing have either been:

  • added to the Manjaro repo (never existed before) or
  • removed from the Manjaro repo (a pacman -Ss would return nothing) or
  • the version changed

A detail line consists of 3 columns:

  • package name (PACKAGE) and
  • current version (2023.01.07) and
  • new version (2023.01.17)

Those lines can contain:

  • If the current version and new version are present, the package has been updated.
  • If the current version is a “-” the package is new to the Manjaro repo.
  • If the new version is a “-” the package has been removed from the Manjaro repo.

Question

The question applies to all repos, but I’ll focus on the Community repo.

How can there be 1495 new packages and 1492 removed packages?

If I look at the Community detail sections (overlay & sync), there are a total of 1510 lines with package details.

Of those lines, there are 14 removes (not 1492) and 17 adds (not 1495).

Also, why was discord removed, but also updated?

Is a package version change (update) counted as removed and new?

(29 + 1481) - (1 + 13) = 1496

Well that’s close to the raw report’s 1495. :slight_smile:

Snippet from raw package changes

 - testing community x86_64:    1495 new and 1492 removed package(s) <==
 - testing core x86_64:           28 new and   28 removed package(s)
 - testing extra x86_64:         537 new and  546 removed package(s)
 - testing kde-unstable x86_64:  398 new and  398 removed package(s)
 - testing multilib x86_64:       17 new and   17 removed package(s)

My summary

 => Section Package Change Summary
1 :: Different overlay package(s) in repository community x86_64  Total:   29 Removed:    1 Added:    1  <==
2 :: Different sync package(s) in repository community x86_64     Total: 1481 Removed:   13 Added:   16  <==
3 :: Different overlay package(s) in repository core x86_64       Total:   10 Removed:    0 Added:    0
4 :: Different sync package(s) in repository core x86_64          Total:   18 Removed:    0 Added:    0
5 :: Different overlay package(s) in repository extra x86_64      Total:   74 Removed:    2 Added:    0
6 :: Different sync package(s) in repository extra x86_64         Total:  492 Removed:   25 Added:   18
7 :: Different overlay package(s) in repository multilib x86_64   Total:    8 Removed:    0 Added:    0
8 :: Different sync package(s) in repository multilib x86_64      Total:    9 Removed:    0 Added:    0
                                                                  Grand: 2121 Removed:   41 Added:   35

My details

:: Different overlay package(s) in repository community x86_64
   discord 0.0.24-1 -
+  manjaro-gnome-vanilla - 0.4-5
=> Section - Total: 29 Removed: 1 Added: 1

:: Different sync package(s) in repository community x86_64
   electron18 18.3.15-4 -
   php7-geoip 1.1.1-8 -
   php7-grpc 1.51.1-2 -
   php7-igbinary 3.2.12-1 -
   php7-imagick 3.7.0-2 -
   php7-memcache 8.0-3 -
   php7-memcached 3.2.0-1 -
   php7-mongodb 1.15.0-1 -
   php7-redis 5.3.7-1 -
   phppgadmin 7.13.0-3 -
   python-pyproject2setuppy 22-1 -
   python-setuptools-scm-git-archive 1.4-1 -
   uwsgi-plugin-php7 2.0.21-2 -
+  electron20 - 20.3.9-2
+  electron21 - 21.3.4-2
+  forgejo - 1.18.0.1-2
+  haskell-hls-rename-plugin - 1.0.0.1-2
+  mastodon-twitter-sync - 1.9.1-2
+  pantheon-calendar - 6.1.2-1
+  php-legacy-geoip - 1.1.1-9
+  php-legacy-grpc - 1.51.1-3
+  php-legacy-igbinary - 3.2.12-2
+  php-legacy-imagick - 3.7.0-3
+  php-legacy-memcache - 8.0-4
+  php-legacy-memcached - 3.2.0-2
+  php-legacy-mongodb - 1.15.0-2
+  php-legacy-redis - 5.3.7-2
+  python-numba - 0.56.4-2
+  uwsgi-plugin-php-legacy - 2.0.21-5
=> Section - Total: 1481 Removed: 13 Added: 16

Legend

  • First character
    • blank = removed
    • “+” = added

As I understand it — but then again, I’m just a lowly, lowly cook moderator — packages that are replaced by a more recent version (and thus updated) count as “removed”. And sometimes a package is split up into two or multiple packages, or conversely, multiple packages are merged into a single package, which could account for the discrepancy in numbers.

Yes — again, as I understand it.

We doesn’t know that, Preciousss. We thinks Orcses dids that.

:stuck_out_tongue:

All packages files have version numbers in their names, so how else would it work ?
For the human pkg-a-1 and pkg-a-2 means pkg-a-2 is an updated version of pkg-a-1, but for a computer they are two different packages…
So they remove pkg-a-1 and add pkg-a-2 :wink:

About the discrepancy i think this explained it great:

2 Likes