Package Details: mylar3 0.5.3-1

Git Clone URL: https://aur.archlinux.org/mylar3.git (read-only, click to copy)
Package Base: mylar3
Description: Comic book download automation for usenet and torrents.
Upstream URL: https://github.com/mylar3/mylar3
Licenses: GPL3
Submitter: fryfrog
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 5
Popularity: 0.000020
First Submitted: 2020-05-06 18:19
Last Updated: 2021-05-19 00:47

Latest Comments

1 2 Next › Last »

nhrjr commented on 2021-03-31 15:30

I made a mistake while copying, if you look closely the first digit (5) is missing from the second line of my previous post. :( So at least your and my "new" hash still match.

Maybe they are overwriting their release inadvertently, even though thinking otherwise? I have seen some browsers decompressing tar.gz files automatically, without renaming them, but why this kind of problem should happen just with mylar is unclear to me, too.

fryfrog commented on 2021-03-31 13:59

There's no script, I just have a bash one liner that runs mksrcinfo which is a function in my .bashrc that does...

mksrcinfo () {
  makepkg --printsrcinfo > .SRCINFO
}

I think the sum is changing. Its different now too...

sha256sum mylar3-0.5.0.tar.gz
5274515fb90cf49db1e48c28e6fe808434dd6818bdf5b57ba217faa0379dc28a  mylar3-0.5.0.tar.gz

Edit: I made issue #690 to ask about it.

nhrjr commented on 2021-03-31 11:20

Hey @fryfrog I'm back at the same problem again. I don't know what happens to the sums? I'm getting:

sha256sum mylar3-0.5.0.tar.gz

274515fb90cf49db1e48c28e6fe808434dd6818bdf5b57ba217faa0379dc28a mylar3-.5.0.tar.gz

I crosschecked with one your other packages (Jackett), where the sha256sums match. Maybe something in your update script went wrong?

fryfrog commented on 2021-03-02 15:44

@mhrjr: Thanks for the report, both done.

nhrjr commented on 2021-03-02 10:28

Hey @fryfrog Could you update the upstream url tag in .SRCINFO to specify github.com? It's giving gitlab, but the repo does not exist.

Also I consistently get sha256sum errors. On my machine with a fresh retrieved mylar source file:

~/.cache/yay/mylar3:> sha256sum mylar3-0.4.9.5.tar.gz
d4b173b233b0bb1a7119f9d2144244d49a633d94761dc6e1e7362702c5319716 mylar3-0.4.9.5.tar.gz

while PKGBUILD states: cf750c27d240c9bacbe13125acadb019671c0cc3cd8a2021e589d072006e92e9

Same happens with a manually downloaded source file. Maybe the upstream binary changed without a version increase?

fryfrog commented on 2020-01-05 00:53

AUR git packages don't get updated for commits, they get updated when the package needs changing. When you build it locally, it'll use the most recent version from git.

That error looks like the updater just doesn't know what branch or version you're on, which doesn't matter because you're not using their updating. If you want to catch up, just re-run it. Maybe AUR helpers have a --devel type option that will rebuild any -git packages.

liqiud commented on 2020-01-04 20:10

We're a few commits behind, should think about updating the package. Also, when doing the update, please resolve this error:

WARNING :: mylar.getVersion.153 : MAIN : No branch specified within config - will attempt to poll version from mylar

mlandgren commented on 2019-03-30 17:37

This will not run without python2-setuptools, you might want to add it to the dependencies.

fryfrog commented on 2018-03-19 17:01

Hey @niekez, I never saw your comment, sorry!

I just moved it from /etc/ to /var/lib, along with doing that to a few others. :)

niekez commented on 2017-09-19 08:46

thanks for the patch @fryfrog

But the excec line should be:

ExecStart=/usr/bin/python2 /usr/share/mylar/Mylar.py --nolaunch --config /var/lib/mylar/config.ini --datadir /var/lib/mylar

Since /etc/ is a root dir, the config should be mantained in /var/lib

Otherwise, the maintainer should apply the patch to the package as it is good practice to run a webservice with it's own user.