Package Details: libg15 1.3.1-2

Git Clone URL: https://aur.archlinux.org/libg15.git (read-only, click to copy)
Package Base: libg15
Description: Provides low-level access to the Logitech G15 and G11 keyboards and Z10 speakers
Upstream URL: https://github.com/vividnightmare/libg15
Licenses: GPL
Conflicts: libg15-git
Submitter: None
Maintainer: vivnet
Last Packager: vivnet
Votes: 0
Popularity: 0.000000
First Submitted: 2021-05-11 02:16 (UTC)
Last Updated: 2024-11-30 18:39 (UTC)

Latest Comments

1 2 Next › Last »

vivnet commented on 2024-11-30 18:26 (UTC)

Indeed the chmod should be +x configure. I'll update that.

Not sure what you're referencing on removing contributors.

Could you describe and reference the improvements in the fork you're linking? I've heard this mentioned before but never anything explicitly stated or defined. Ignoring the version number for a later discussion, does this source not work? Is there some issue? If you didn't look at the version or source, could you tell any difference?

Lucki commented on 2024-11-30 18:14 (UTC) (edited on 2024-11-30 18:14 (UTC) by Lucki)

Thank you for making sure this package was able to build while the fork with improvements wasn't available. It's now back online as it seems, so please bring this back to the latest version, which is 3.0.7a from this fork: https://gitlab.com/menelkir/libg15/-/tags

If that source ever goes offline again there's another fork of the fork by Eli Schwartz (Arch TU) here: https://gitlab.com/eschwartz/libg15

Some points to your single commit since taking over this package:

  • Removing previous package contributors seems very disrespectful and is usually discouraged.
  • chmod -R 777 ${srcdir} seems very wrong.

vivnet commented on 2024-07-06 23:01 (UTC)

https://gitlab.com/menelkir/g15daemon/-/archive/3.0.4/g15daemon-3.0.4.tar.bz2

Evenfall commented on 2024-06-27 23:11 (UTC)

The repository is there, g15daemon is broken because YOU broke the libs out of a childish behavior because your patch wasn't accepted. The devices are brooken because you're incapable of look behind your own belly to realize how much fixes and new devices he brought to libg15. You took maintainership because you're a spoiled child and wanted attention. Isn't an ad hominem attack, is the reality, you're a kid wanting attention and now the package is broken because instead of maintaining something USEFUL, you brought back and old package without the fixes and support.
You know what is funny? It works everywhere else, in gentoo is a matter of unmask the package and my device works, wanna guess why? But don't worry, I dished my Arch install, Menelkir is right, arch shouldn't be used by anyone doing anything serious, it's just a matter of look what is happening here. This is my final comment as well, enjoy your sad behavior. Perhaps when you hit 18 you'll feel sorry by yourself.

vivnet commented on 2024-06-19 20:41 (UTC)

g15daemon on AUR is broken because the maintainer and owner of the source repository deleted the tags. You still decline to open a bug, file a bug report, or submit a pull request. I took maintainership of an orphaned package and updated it from the same source until that source was deleted. This is my final comment, I will not engage in or be the recipient of ad hominem attacks.

Evenfall commented on 2024-06-19 20:27 (UTC) (edited on 2024-06-19 20:27 (UTC) by Evenfall)

You're being extremely dishonest to defend the fact that you took over a AUR package that was abandoned due to a childish tantrum. I don't have only one device but TWO broken devices that worked just fine with the "unreliable" source. No, it didn't broke "a number of other packages", stop lying. You're creating an entire problem out of a childish tantrum and break users, including myself. It's fine to maintain something that works just for YOURSELF, but breaking users relying on a package that used to work out of a tantrum is new to me. But don't worry, I'm not the only one leaving Arch, I'm tired of seeing trolls on AUR. I have to confess that stealing a project out of tantrum to keep a broken decade old is new to me.

vivnet commented on 2024-06-19 19:21 (UTC)

No issue, bug report, or pull request has been filed. The source repository was not changed until the package was broken by the preceding source repository being deleted. This apparently is again available, but archived, and seems unreliable. After inspecting the code I'm not able to identify the fixes you're mentioning, maybe you could supply some evidence to back the claim, and/or create an issue and submit a merge request. Additionally, the preceding source repository deleted releases and tags which broke a number of other packages that I do not maintain.

Evenfall commented on 2024-06-19 09:05 (UTC)

You broke the package by using a very old release, the G11 is broken and the M keys doesn't work properly because you didn't cared to apply the fixes. When I investigated further, you just stole the project out of a childish behavior. Why this is here? Why AUR moderation permits this behaviro?

vivnet commented on 2024-06-08 21:03 (UTC)

Previous source repository was deleted.

vivnet commented on 2024-05-27 19:45 (UTC)

Does this actually need maintenance? There is no functional difference between 3.0.7 and 3.0.7a.

1 2 Next › Last »