I've been going through my 400+ AUR packages updating the license to match SPDX license requirements. xiota has decided a pkgrel bump is required if one updates the license. He has begun spamming the same comment on 9 of my AUR packages so far. I've already told him to stop here: https://aur.archlinux.org/pkgbase/qtscrcpy#comment-952888. I imagine he's doing it on other packages as well if he's doing it for mine. This is not the first time someone has complained about xiota's behavior. I've had quite enough of it. His email is private, so I can't CC him here. Sent with [Proton Mail](https://proton.me/) secure email.
Changing the license does indeed change the package, as it means that different license files are installed, though I'm not sure whether that warrants bumping the pkgrel, and spamming the same comment across several packages by the same maintainer is certainly disruptive. That said, I've only seen one comment by them, and I have not seen any other valid complaints about xiota. Could you link to the other pkgbases they've commented on? Also, welcome to the aur-general mailing list! Familiarize yourself with [the mailing list guidelines][1]. Highlights include using plain text emails. [1]: https://wiki.archlinux.org/title/General_guidelines#Mailing_lists -- Cheers, Aᴀʀᴏɴ
Changing the license does indeed change the package, as it means that different license files are installed, though I'm not sure whether that warrants bumping the pkgrel, Here it is not question of changing the license but simply switching the current license to SPDX identifiers [1] in the license array. The installed license files (if there are) are not changed. So, unless the
and spamming the same comment across several packages by the same maintainer is certainly disruptive. That said, I've only seen one comment by them, and I have not seen any other valid complaints about xiota. Could you link to the other pkgbases they've commented on? I'm gonna remove "cluttering" comments from the package listed in Mark Wagie's initial mail.
Also, welcome to the aur-general mailing list! Familiarize yourself with [the mailing list guidelines][1]. Highlights include using plain text emails. For what it's worth, the ML guidelines also include to quote parts of
On 1/22/24 00:47, Aaron Liu wrote: license itself changed, simply switching to an SPDX identifier as Mark Wagie did does not change the package and I think it's fine not bumping the pkgrel _just_ for that. the email you're responding to [2]. It's better to be able to respond to both you and Mark in the same email :)
[1]: https://wiki.archlinux.org/title/General_guidelines#Mailing_lists
[1] https://spdx.org/licenses/ [2] https://wiki.archlinux.org/title/General_guidelines#Quoting -- Regards, Robin Candau / Antiz
On Mon, 22 Jan 2024 09:24:04 +0100 Robin Candau <antiz@archlinux.org> wrote:
Changing the license does indeed change the package, as it means that different license files are installed, though I'm not sure whether that warrants bumping the pkgrel, Here it is not question of changing the license but simply switching the current license to SPDX identifiers [1] in the license array. The installed license files (if there are) are not changed. So, unless the
On 1/22/24 00:47, Aaron Liu wrote: license itself changed, simply switching to an SPDX identifier as Mark Wagie did does not change the package and I think it's fine not bumping the pkgrel _just_ for that.
Changing package metadata does change the package, though.
On 1/22/24 14:43, Doug Newgard wrote:
On Mon, 22 Jan 2024 09:24:04 +0100 Robin Candau <antiz@archlinux.org> wrote:
Changing the license does indeed change the package, as it means that different license files are installed, though I'm not sure whether that warrants bumping the pkgrel, Here it is not question of changing the license but simply switching the current license to SPDX identifiers [1] in the license array. The installed license files (if there are) are not changed. So, unless the
On 1/22/24 00:47, Aaron Liu wrote: license itself changed, simply switching to an SPDX identifier as Mark Wagie did does not change the package and I think it's fine not bumping the pkgrel _just_ for that.
Changing package metadata does change the package, though.
But when it's not in a way that would be impacting for the end users (like it's the case here) there's no _need_ to trigger a rebuild for users simply because of that. The point is, in that specific case, bumping the pkgrel is fine, not bumping it is fine either. Such a change can totally wait for the next pkgver bump (or _required_ pkgrel bump). -- Regards, Robin Candau / Antiz
participants (4)
-
Aaron Liu
-
Doug Newgard
-
Mark Wagie
-
Robin Candau