On Thu, Aug 10, 2017 at 09:41:39AM -0500, Doug Newgard wrote:
> On Thu, 10 Aug 2017 10:26:09 -0400
> Eli Schwartz wrote:
>
> > pkgrel is supposed to monotonically increase on each rebuild of the
> > package.
>
> Which is completely invalid in the AUR. How is the maintainer supposed to keep
> the
Eli Schwartz wrote:
>pkgrel is supposed to monotonically increase on each rebuild of the
>package.
When releasing a binary package, the pkgrel needs to be bumped if the resulting
package's signature and/or checksums change (without changing the pkgver).
When releasing a PKGBUILD the requirement
On Thu, 10 Aug 2017 10:26:09 -0400
Eli Schwartz wrote:
> pkgrel is supposed to monotonically increase on each rebuild of the
> package.
Which is completely invalid in the AUR. How is the maintainer supposed to keep
the user from doing rebuilds in between?
On 08/10/2017 06:33 AM, justus-...@piater.name wrote:
> Hi -
>
> I keep running into problems caused by stale installations from the AUR,
> such as upgraded, ABI-incompatible dependencies or Python packages still
> installed under /usr/lib/python3.5/ where they are no longer found since
> the move
Am 10.08.2017 12:33, schrieb justus-...@piater.name:
Hi -
I keep running into problems caused by stale installations from the
AUR,
such as upgraded, ABI-incompatible dependencies or Python packages
still
installed under /usr/lib/python3.5/ where they are no longer found
since
the move to pyt