Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50023 - [glusterfs] glusterfs 3.8 got revoked?
Attached to Project:
Community Packages
Opened by Tim (bastelfreak) - Tuesday, 12 July 2016, 08:26 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 14 July 2016, 14:42 GMT
Opened by Tim (bastelfreak) - Tuesday, 12 July 2016, 08:26 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 14 July 2016, 14:42 GMT
|
DetailsDescription:
Hi, glusterfs3.8 package got released and then revoked. There isn't any explanation in the git repo about it: https://git.archlinux.org/svntogit/community.git/log/trunk?h=packages/glusterfs Could you please explain why you did this? I upgraded my cluster during your revocation, which led to inconsistent version numbers across the nodes. Is it save to upgrade the other nodes as well? Do I have to downgrade? |
This task depends upon
Comment by Sergej Pupykin (sergej) -
Thursday, 14 July 2016, 14:41 GMT
Yes, there is major bug in upstream, developers ask to wait for 3.8.1