Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61745 - [mongodb-tools] Does license change require drop to AUR?

Attached to Project: Community Packages
Opened by James Harvey (jamespharvey20) - Wednesday, 13 February 2019, 11:20 GMT
Last edited by Felix Yan (felixonmars) - Thursday, 14 February 2019, 16:06 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I'm unable to post to arch-dev-public, so I'm submitting a reply here.

On 2019/1/18 22:12, Felix Yan via arch-dev-public wrote:
> On 2019/1/16 10:35, Allan McRae via arch-dev-public wrote:
>> Drop the package.
>
> I have dropped the two packages (mongodb and wiredtiger) to the AUR,
> since I did not use MongoDB for quite some time anyway.
>
> Thanks for all the input here.

Should mongodb-tools also be dropped to AUR?

I'm thinking the same licensing issue applies to it.

I also think it's important for the same person to maintain mongodb and mongodb-tools, so their versions can easily stay in sync.

frealgagu picked up mongodb in AUR, and added me as a co-maintainer. I'd be willing to maintain/co-maintain the mongodb-tools package, if dropped to the AUR, but if any Trusted Users wanted either of them, that's fine too.



BTW, is there a specific reason why community MongoDB wasn't upgraded to the 4.1 series? 4.1.0 was tagged 5/22/2018. Community was on 4.0.5, tagged 12/19/2018. 4.0.6 was tagged 8 days ago, and 4.1.8 today.

I am asking this as the co-maintainer of the AUR package, since it was dropped there, not as an inpatient user. Not having touched maintenance of this package before, if there's a specific problem, like how upgrading to the latest mariadb branch on Arch was really delayed, I don't want to lose that knowledge, and just bump it up to 4.1.8.
This task depends upon

Closed by  Felix Yan (felixonmars)
Thursday, 14 February 2019, 16:06 GMT
Reason for closing:  None
Additional comments about closing:  Dropped.
Comment by Chih-Hsuan Yen (yan12125) - Wednesday, 13 February 2019, 13:58 GMT
Just FYI: mongo-tools appears to be still licensed Apache2 https://github.com/mongodb/mongo-tools/blob/master/LICENSE.md.
Comment by James Harvey (jamespharvey20) - Thursday, 14 February 2019, 00:19 GMT
yan12125, you're right. I still think this should be dropped, to keep versions in sync and to prevent potential data loss. There's no current issue that I'm aware of, but I could easily see a future risk of corruption if the AUR mongodb and community mongodb-tools versions mismatch, especially if it's a larger mismatch than the current 4.0.6 vs 4.0.5.
Comment by Felix Yan (felixonmars) - Thursday, 14 February 2019, 16:05 GMT
The even number branches are stable branches (listed as current in its website) and 4.1.x are development versions. You can find this on the official website very easily.

I have dropped mongodb-tools as you wish.

Loading...