Package Details: minipro 0.7.2-1

Git Clone URL: https://aur.archlinux.org/minipro.git (read-only, click to copy)
Package Base: minipro
Description: Open source chip programming utility for autoelectric.cn MiniPro TL866xx series (TL866CS, TL866A, and TL866II+)
Upstream URL: https://gitlab.com/DavidGriffith/minipro
Licenses: GPL-3.0-only
Conflicts: minipro
Provides: minipro
Submitter: uffe
Maintainer: uffe
Last Packager: uffe
Votes: 4
Popularity: 0.000000
First Submitted: 2021-01-17 01:45 (UTC)
Last Updated: 2024-10-06 19:47 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

uffe commented on 2024-10-10 11:24 (UTC)

ATTENTION: read this before flagging this package out-of-date

This package "minipro" represents the stable release of the minipro project.

For bleeding edge AUR builds of minipro - go to https://aur.archlinux.org/packages/minipro-git

JPT48 commented on 2024-10-09 14:46 (UTC)

@uffe oh, you are right. I am sorry. Going to check minipro-git

uffe commented on 2024-10-07 13:45 (UTC)

@JPT48 this is a stable release it should and cannot change after the release. I guess that your post should have been at the AUR "minipro-git" bleeding-edge package ?

JPT48 commented on 2024-10-06 13:28 (UTC)

Hi there is a missing dependency: libb64

and the installer complains that algorithm.xml was missing. Looks like a recent change: https://gitlab.com/DavidGriffith/minipro/-/commit/fa88225b58e54b7edd131a3d78d47e6ffe14c0b6 thanks

CodeAsm commented on 2024-09-22 16:21 (UTC)

New release, but yes the 0.7.1 downloads and builds fine now. Thank you so much

uffe commented on 2024-09-19 13:47 (UTC)

@CodeAsm

I was not aware of the new file archive at 661.org (note in public/index.html was added yesterday)

There is some talk about the subject (and another issue) here: https://gitlab.com/DavidGriffith/minipro/-/issues/320

BTW: I've now switched the PKGBUILD to download from 661.org - should be effective now :-)

CodeAsm commented on 2024-09-19 12:15 (UTC)

I dunno why they or somehow the checksum keeps changing. now its supposed to be 714214fc4e3ee37c36ff3b9ae68f65984cba727110c1151d389559e02603654e based on https://661.org/files/minipro/checksums.txt

Can we determine if they change the files without updating the version number for some reason? this is anoying

uffe commented on 2024-09-12 08:36 (UTC) (edited on 2024-09-12 08:38 (UTC) by uffe)

@MrAureliusR:

I just tried and it passes the sha256sum here - see snip below

==> Making package: minipro 0.7.1-1 (2024-09-12T10:31:56 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found minipro.src.tgz
==> Validating source files with sha256sums...
    minipro.src.tgz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting minipro.src.tgz with bsdtar
==> Starting prepare()...
==> Sources are ready.

I know that the author was having problems about reproducable builds out of gitlab

Maybe you are using som locally cached source caught at a bad moment.

as an example I know that the aur builder yay by default caches sources etc below ~/.cache/yay/xxx

MrAureliusR commented on 2024-09-12 05:31 (UTC)

There must have been a change in the source file, as it's no longer passing checksum validation and therefore won't build.

uffe commented on 2022-07-23 15:11 (UTC)

Thanks - as v0.5 is the latest stable release - I've added a temporary hack to prevent parallel builds. The hack will be removed when a new stable release comes out...

1 2 Next › Last »