Package Details: python-projectq 0.8.0-4

Git Clone URL: (read-only, click to copy)
Package Base: python-projectq
Description: Open-source framework for quantum computing
Upstream URL:
Licenses: Apache-2.0
Submitter: flacks
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 2
Popularity: 0.000000
First Submitted: 2018-07-23 23:18 (UTC)
Last Updated: 2024-05-06 16:08 (UTC)

Latest Comments

MarsSeed commented on 2024-01-27 12:25 (UTC)

You are right in your feedback to me. I appreciate it. Next time I will be mindful of it, and communicate in more appropriate ways. Cheers.

iyanmv commented on 2024-01-27 12:10 (UTC)

MarsSeed: Thank you for your comment. Just so I'm 100% clear, I really appreciate when someone tells me that something is not working. I don't have (currently) a CI pipeline that regularly builds all my AUR packages so if something breaks after I created and tested the package, I will not be aware of it. However, I do use nvchecker to get notifications when there are newer versions and I try my best to keep my packages up to date.

So in this case, a simple: "Hey! check() is not working for me." would have been perfect, more appropriate than flagging the package as out-of-date (when is not).

Hope this interaction with me helps you outreach AUR maintainers in a more effective way ;)

MarsSeed commented on 2024-01-27 12:00 (UTC)

Sorry, I've misunderstood the AUR comments notification email when replying to it.

Please don't be hostle to me. I always act with good intentions. I have ADHD, and sometimes (many times) I am too hasty. But I try to compensate by being meticulous and double-triple-checking myself. I also always try to heed constructive feedback.

Btw by checking packages for errors, I am actually doing the job that AUR Package Maintainers have as a duty, stated in Package Maintainer guidelines. 80% of Package Maintainers on AUR do nothing on AUR, maybe due to many other commitments in their lives. Still, if I am prompting package owners to take care of some issues, it actually benefits the whole community, as it leads to higher number of correct, working packages that users can install.

But I know that pushing maintainers to do their job can be felt as unwelcome. I am sorry for the inconvenience that I might have caused you. I appreciate your dedication to the AUR and for caring for your packages. I am asking for your kind patience and understanding. Thank you.

iyanmv commented on 2024-01-27 11:39 (UTC)

MarsSeed: only the tests are broken, the package works as expected. Feel free to send here or in Github a patch to fix the check() or upstream if it's not a packaging issue. But please, stop flagging AUR packages like a brainless bot, it's not useful and it's, honestly, quite annoying specially when I can guess you have never used this Python package, but you only tried to build it.

I only write this because you've been told several times in the past that your "contributions" are not useful. So please, step back, read what you've been told many times already, and change this behavior.


iyanmv commented on 2024-01-27 11:16 (UTC)

MarsSeed: You just had your account suspended some days ago and you continue with the same attitude... Can you chill and stop flagging packages as out of date (when they are not)? If something is broken, leave a comment here so I can have a look.