You are not logged in.
Hi,
Today I noticed this warning while updating my system
warning: dub: local (0.9.22-2) is newer than community (v0.9.22.r198.g83b2926-1)I know you get similar warnings when you install from testing and/or with custom-compiled packages with newer versions than the repos. That is the not case. I installed dub a couple of weeks ago from official repos.
$ grep dub /var/log/pacman.log
[2015-02-01 11:38] [PACMAN] Running 'pacman -S dub'
[2015-02-01 11:39] [ALPM] installed dub (0.9.22-2)I think the problem is that pacman thinks 0.9.22-2 > v0.9.22.r198.g83b2926-1 when it should be the other way around.
The commit 83b2926 is dub's latest [1], so obviously v0.9.22.r198.g83b2926-1 is the latest version. Maybe a packaging error?
Here is the full pacman output from today.
$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra 1791.5 KiB 1361K/s 00:01 [###########################################] 100%
community 2.5 MiB 1802K/s 00:01 [###########################################] 100%
multilib is up to date
infinality-bundle is up to date
infinality-bundle-fonts is up to date
infinality-bundle-multilib is up to date
:: Starting full system upgrade...
warning: dub: local (0.9.22-2) is newer than community (v0.9.22.r198.g83b2926-1)
resolving dependencies...
looking for conflicting packages...
Packages (3) ghostscript-9.15-2 python-setuptools-1:12.2-1 python2-setuptools-1:12.2-1
Total Download Size: 12.84 MiB
Total Installed Size: 64.26 MiB
Net Upgrade Size: 0.66 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
ghostscript-9.15-2-x86_64 12.8 MiB 1781K/s 00:07 [###########################################] 100%
(3/3) checking keys in keyring [###########################################] 100%
(3/3) checking package integrity [###########################################] 100%
(3/3) loading package files [###########################################] 100%
(3/3) checking for file conflicts [###########################################] 100%
(3/3) checking available disk space [###########################################] 100%
(1/3) upgrading ghostscript [###########################################] 100%
(2/3) upgrading python-setuptools [###########################################] 100%
(3/3) upgrading python2-setuptools [###########################################] 100%Bye!
[1] https://github.com/D-Programming-Langua … its/master
Last edited by a821 (2015-02-17 17:40:36)
Offline
The quick and dirty WORKAROUND would be to use -Suu which would allow downgrade (since pacman thinks the new version has lower number). However this workaround should not be taken for granted, as these things should not happen.
Offline
Hi, thanks, -Suu allowed the "downgrade" of the package. Good to know! I thought to just manually download the package and apply -U. I agree that this should not happen...
Offline
It looks like it could be a packaging bug - you could check our bugtracker and report it if it's not already there. The version number was likely parsed/convered before, but now it is not. Even if this change was intentional, it should have an incremented epoch number.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
OK. I submitted a bug report: https://bugs.archlinux.org/task/43849.
Offline
The new version "v0.9.22.r198.g83b2926-1" should not have "v" prefix. This is clearly a packaging bug.
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline
Great! I new version without the "v" prefix was pushed and the update worked. Marked as SOLVED.
Offline