avr-{gcc,libc} warnings on lower versions

yuvadm · 2016-07-03 07:42:45

When running a full update (-Syu) I'm getting this:

:: Starting full system upgrade...
warning: avr-gcc: local (6.1.1-1) is newer than community (5.3.0-2)
warning: avr-libc: local (2.0.0-2) is newer than community (2.0.0-1)

This happens on several different mirrors after -Syyu. Any idea where this is coming from?

mis · 2016-07-03 08:27:18

Somehow you installed newer versions than available in the [community] repo.
To downgrade you can pass the 'u' option twice: -Syyuu

yuvadm · 2016-07-03 08:34:11

mis wrote:

Somehow you installed newer versions than available in the [community] repo.

But...

https://git.archlinux.org/svntogit/comm … s/avr-libc
https://git.archlinux.org/svntogit/comm … es/avr-gcc

What's going on?

mis · 2016-07-03 10:43:45

I don't know, for some reason the git versions are not in [community] yet.
https://www.archlinux.org/packages/?sor … =&flagged=

yuvadm · 2016-07-03 10:50:51

Looks weird. Opened https://bugs.archlinux.org/task/49924

bstaletic · 2016-07-03 11:26:41

Maybe the mirror you're using is out of sync?

yuvadm · 2016-07-03 11:31:10

Happens on all mirrors I tested on

mis · 2016-07-03 11:36:49

bstaletic wrote:

Maybe the mirror you're using is out of sync?

I don't think so ..

yuvadm wrote:

But...
https://git.archlinux.org/svntogit/comm … s/avr-libc
https://git.archlinux.org/svntogit/comm … es/avr-gcc

.. the last commits are about two month old

And the package search also shows the old versions.

Trilby · 2016-07-03 11:41:19

It's not a mirror issue - this is easily confirmed by checking the package database on the website here. Also you can see in the archlinux rollback machine that 6.1.1 was pushed to the repos on 9 may 2016, but more recently is was removed leaving 5.3.0 as the most recent version.

If this was intentional - e.g., there was a problem with 6.1.1 such that it needed to be pulled - then an epoch number should have been added to 5.3.0 and there likely would have been discussion of this on the mailing lists. The bug report is the right way to go. This seems like a packaging bug to me.

Allan · 2016-07-04 02:12:00

If it was only in [testing], then it can be pulled without an epoch bump (I am too lazy to check if this is the case...)

Arch Linux

#1 2016-07-03 07:42:45

avr-{gcc,libc} warnings on lower versions

#2 2016-07-03 08:27:18

Re: avr-{gcc,libc} warnings on lower versions

#3 2016-07-03 08:34:11

Re: avr-{gcc,libc} warnings on lower versions

#4 2016-07-03 10:43:45

Re: avr-{gcc,libc} warnings on lower versions

#5 2016-07-03 10:50:51

Re: avr-{gcc,libc} warnings on lower versions

#6 2016-07-03 11:26:41

Re: avr-{gcc,libc} warnings on lower versions

#7 2016-07-03 11:31:10

Re: avr-{gcc,libc} warnings on lower versions

#8 2016-07-03 11:36:49

Re: avr-{gcc,libc} warnings on lower versions

#9 2016-07-03 11:41:19

Re: avr-{gcc,libc} warnings on lower versions

#10 2016-07-04 02:12:00

Re: avr-{gcc,libc} warnings on lower versions

Board footer