Package Details: blender-3.6-bin 3.6.231115.76cf464098be-1

Git Clone URL: https://aur.archlinux.org/blender-3.6-bin.git (read-only, click to copy)
Package Base: blender-3.6-bin
Description: A fully integrated 3D graphics creation suite
Upstream URL: https://www.blender.org
Licenses: GPL
Submitter: notfood
Maintainer: notfood
Last Packager: notfood
Votes: 7
Popularity: 0.84
First Submitted: 2023-03-14 07:26 (UTC)
Last Updated: 2023-11-17 01:03 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

snygg commented on 2024-09-16 11:26 (UTC)

As you wish, I removed the flag.

I noticed, that the flag was not correct anyways, because the package installs the newest version, but the meta data or PKGBUILD seem to be broken, so it is more like a faulty package instead of an outdated.

Blender 3.6 has a new updated release every month. https://www.blender.org/download/lts/3-6/#versions Sorry, I was under the misconception that you are pulling the official releases from the official release page, but that seems to be not the case.

notfood commented on 2024-09-16 05:40 (UTC)

Don't flag it. It updates daily, there is no way to do what you are requesting. If there is any, I'm not aware of it. You don't want me pushing daily updates, for real.

snygg commented on 2024-09-08 11:11 (UTC) (edited on 2024-09-08 11:43 (UTC) by snygg)

This package installs always the newest release for blender-3.6 from the respective upstream github repo.

Since there seems to be a new release, this AUR package causes a warning like:

blender-3.6-bin: local (3.6.240825.f612027620c9-1) is newer than AUR (3.6.231115.76cf464098be-1)

when updating the system with, e.g., yay -Su

I would like to ask, if it would be possible to update the package's metadata to match the new release from upstream? Thanks