Arch Linux User Repository

Done.

Thanks Xavion, good points all around. Can you open Issues on the GitHub repo for these two things?

Regarding my second suggestion, your implementation idea sounds good but would require a fair bit of work. I think it'd be easier for you to just list the dates alongside the packages in the 'downgrade' output. In fact, I think this should be done even if you do decide to create the second tool.

I Xavlon,

For the first one (sort by most-recent-first), I can't reproduce what you're seeing, they sort by recency for me (as intended)

% downgrade firefox
Available packages:

1) firefox-53.0.3-1-x86_64.pkg.tar.xz (remote)
...snip...
103) firefox-23.0.1-1-x86_64.pkg.tar.xz (remote)
104) firefox-23.0.1-1-x86_64.pkg.tar.xz (local)

select a package by number:

Can you report this issue on GitHub with more details (exact invocation, exact output, system locale, etc)?

---
EDIT: I'm sorry, I misread that you wanted to see most recent sorted *last*. I had never actually considered this, but your reasoning makes sense! I don't know when, but I agree that the other sort would be better and will probably make that change.
--

For the second suggestion, this has been requested once or twice and I agree it sounds useful. I wonder if a better solution would be a second tool, one that takes a package name and rough date and parses pacman.log to find out what version of that package you had installed around that time. The output of this tool could be passed directly to downgrade (it accepts {package}-{version}, and will even skip the prompts if there's a single result). Something like:

dowgrade $(package-when firefox "last saturday")

WDYT?

I have two requests to make.

Firstly, please reverse the order of the list. In other words, the most recent editions of packages should be shown at the bottom of the screen. It makes sense that people looking for earlier versions should have to scroll back further!

Secondly, it would be good to have the creation/upload date listed next to each entry in the list. If I want to roll back to a package I know I installed two Saturdays ago (but don't remember the version number), I have to go by its date-stamp.

Great package.
It works fine and its well thought.
Very easy and intuitive.
Elixir was broken with new erlang 20rc-1 and I fixed in a minute with this tool.
No other solution suit me as this.
Very useful the IgnorePkg? [y/n] option.

Thanx

I just tested and everything seems to be working here. I've never seen that message and don't know anything about it unfortunately. If this persists, please open an Issue on GitHub with the full output of

bash -x downgrade ...

Thanks.

hi I´m getting this error

"A.L.A. disabled see https://wiki.archlinux.org/index.php/downgrading_packages for more details"

downgrader is working

FadeMind, I'm a little unclear: is there something here I need to fix?

I just did `pacman -Rsn downgrade && aurget -S downgrade` and did not receive any warnings.

warning: could not get file information for foo/bar.mo just mean:

FILE foo/bar.mo is included in package foobar-12.01-2 BUT pacman can't find it during upgrading proccess.

tl;dr:

IF You using bleachbit for removing not needed language files, then this will show up as warning.