pacman database archive

[Efreets]

I still can't use the old archive pacman soft database?
Did it work like archive.archlinux.org, but I can't find the archive website Url,
I need download and use the old software before 2022-04-01, so can you help me for this?

[lazka]

No work has started on this yet.

The old package files are still there (we keep them for 1.5+ years) : https://repo.msys2.org/mingw/mingw64/

# example:
pacman -U https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-glib2-2.66.1-1-any.pkg.tar.zst

[Efreets]

I think the soft archives cost expensive, maybe you just can git version the soft database like msys.db and mingw64.db in convenient , unless to classify the soft version by years which more waste vigour and cloud storage.

[Efreets]

Just versioning the database may help lots people with they only can download and install soft one by one assigned version,
it waste lots of time to attention the soft version one by one,
so can you version the database? many thanks

[Efreets]

I need the database between 2022-03-28 to 2022-4-1, so can you help me, and send me the database in C:\msys64\var\lib\pacman\sync\ with filename clang32.db clang64.db clangarm.db mingw32.db mingw64.db msys.db and ucrt64.db with their signature files.

[lazka]

You could extract them from the older installer releases:
https://github.com/msys2/msys2-installer/releases

That's all we have..

[Efreets]

The installer didn't have clang32.db files, and the April month database didn't have, can you more efficiently backup the soft version database by weekend, one times or two times was too little in month, and we just need the soft version database with various date

[jeremyd2019]

Assuming that you haven't been saving sync dbs since... What if, moving forward, you save the sync dbs somewhere. Heck, maybe a release (or new releases each time) on this repo. It could even be automated as part of your scripts (from msys2-devtools, msys2-db{add,remove}) to use gh release create with a date/timestamp as the release name and the repo files. Then at least when we get around to making instructions or mechanisms to use them, we'll have them. (and if the old dbs were available, the really adventurous could probably manage to inject them into /var/lib/pacman/sync and refrain from using -Sy)

[Efreets]

Thanks for your efforts.

[jeremyd2019]

If you (@lazka) like, I could make a script to pull sync dbs out of old installers and push them to github releases named by date/timestamp of the sync db files, if I had rights to this repo. Or I could just make a big tarball of them with directories named by date/timestamp and upload it somewhere if that would be easier to deal with.