starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #1258] License question for packaging in debian #889

New issue

Closed

opened 2026-05-07 00:28:29 +02:00 by BreizhHardware · 7 comments

BreizhHardware commented

2026-05-07 00:28:29 +02:00

Owner

Originally created by @thekhalifa on GitHub (Jan 17, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1258

❓ Question

Hi, I'm trying to package ntfy for debian and a question came up about the license for ntfy.

It's stated as "dual license" but also "Apache-2.0 and GPL-2" - minor question here, is it AND or OR?
Should we use "Apache-2.0 AND GPL-2" meaning subject to both, or "Apache-2.0 OR GPL-2" meaning subject to either.

Originally created by @thekhalifa on GitHub (Jan 17, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1258  :question: **Question**  Hi, I'm trying to package ntfy for debian and a question came up about the license for ntfy. It's stated as "**dual** license" but also "Apache-2.0 **and** GPL-2" - minor question here, is it **AND** or **OR**? Should we use "Apache-2.0 AND GPL-2" meaning subject to both, or "Apache-2.0 OR GPL-2" meaning subject to either.

BreizhHardware

2026-05-07 00:28:29 +02:00

closed this issue
added the
question
label

BreizhHardware commented

2026-05-07 00:28:30 +02:00

Author

Owner

@rodber commented on GitHub (Apr 6, 2025):

Despite our best efforts, the FSF has never considered the Apache License to be compatible with GPL version 2, citing the patent termination and indemnification provisions as restrictions not present in the older GPL license. The Apache Software Foundation believes that you should always try to obey the constraints expressed by the copyright holder when redistributing their work.

https://www.apache.org/licenses/GPL-compatibility.html

@rodber commented on GitHub (Apr 6, 2025): > Despite our best efforts, the **FSF has never considered the Apache License to be compatible with GPL version 2**, citing the patent termination and indemnification provisions as restrictions not present in the older GPL license. The Apache Software Foundation believes that you should always try to obey the constraints expressed by the copyright holder when redistributing their work. https://www.apache.org/licenses/GPL-compatibility.html

BreizhHardware commented

2026-05-07 00:28:30 +02:00

Author

Owner

@binwiederhier commented on GitHub (Apr 6, 2025):

Oh I see what you mean. The wording is ambiguous. It was always meant to be OR, as in you pick a license you're happy with.

@binwiederhier commented on GitHub (Apr 6, 2025): Oh I see what you mean. The wording is ambiguous. It was always meant to be OR, as in you pick a license you're happy with.

BreizhHardware commented

2026-05-07 00:28:30 +02:00

Author

Owner

@thekhalifa commented on GitHub (Apr 18, 2025):

Sounds right, I had assumed that's what you meant and used "OR" in the debian copyright file.
https://tracker.debian.org/pkg/ntfy

Thanks for confirming.

@thekhalifa commented on GitHub (Apr 18, 2025): Sounds right, I had assumed that's what you meant and used "OR" in the debian copyright file. https://tracker.debian.org/pkg/ntfy Thanks for confirming.

BreizhHardware commented

2026-05-07 00:28:31 +02:00

Author

Owner

@binwiederhier commented on GitHub (Apr 18, 2025):

This is the greatest achievement ever. I'm gonna be in Debian🥳🎂🎉

Thanks for packaging!

@binwiederhier commented on GitHub (Apr 18, 2025): This is the greatest achievement ever. I'm gonna be in Debian🥳🎂🎉 Thanks for packaging!

BreizhHardware commented

2026-05-07 00:28:31 +02:00

Author

Owner

@thekhalifa commented on GitHub (Apr 18, 2025):

And by extension, Ubuntu too: https://packages.ubuntu.com/plucky/ntfy
Thanks for the really useful app you built and maintain.

@thekhalifa commented on GitHub (Apr 18, 2025): And by extension, Ubuntu too: https://packages.ubuntu.com/plucky/ntfy Thanks for the really useful app you built and maintain.

BreizhHardware commented

2026-05-07 00:28:31 +02:00

Author

Owner

@binwiederhier commented on GitHub (May 29, 2025):

@thekhalifa I just saw the patch series. That's looks like a terrible set of changes to make. Can I help make these changes easier? I could move all the stripe stuff behind build flags so you can disable it, for instance

@binwiederhier commented on GitHub (May 29, 2025): @thekhalifa I just saw the patch series. That's looks like a terrible set of changes to make. Can I help make these changes easier? I could move all the stripe stuff behind build flags so you can disable it, for instance

BreizhHardware commented

2026-05-07 00:28:31 +02:00

Author

Owner

@thekhalifa commented on GitHub (May 29, 2025):

Hi @binwiederhier, definitely, any help would be highly appreciated here.

Stripe is pretty huge, so I doubt it would ever get packaged. The other missing dependencies were Firebase and SherClockHolmes, those were too big to package if I remember correctly. So any way to tag them out would be great.

I was planning on seeing if I can compile the webapp too, but that had missing nodejs dependencies.

There was also a minor incompatibility with golang-github-emersion-go-smtp where you pinned it to a lower version in your go.mod. Had to patch that to compile it with debian's 0.21.2.

Also while we're on the topic, would you consider adding a manpage? You can copy the debian one or I can submit a PR. Alternatively, you can generate one from a MD page if you prefer something else (e.g. md2man or scdoc) :)
Debian repo in use is this -> https://salsa.debian.org/go-team/packages/ntfy

Thanks a lot for offering here.

PS, there is a release freeze now, so it will be released as-is for debian Trixie, and we have time until the next release.

@thekhalifa commented on GitHub (May 29, 2025): Hi @binwiederhier, definitely, any help would be highly appreciated here. Stripe is pretty huge, so I doubt it would ever get packaged. The other missing dependencies were Firebase and SherClockHolmes, those were too big to package if I remember correctly. So any way to tag them out would be great. I was planning on seeing if I can compile the webapp too, but that had missing nodejs dependencies. There was also a minor incompatibility with golang-github-emersion-go-smtp where you pinned it to a lower version in your go.mod. Had to patch that to compile it with debian's 0.21.2. Also while we're on the topic, would you consider adding a manpage? You can copy the debian one or I can submit a PR. Alternatively, you can generate one from a MD page if you prefer something else (e.g. md2man or scdoc) :) Debian repo in use is this -> https://salsa.debian.org/go-team/packages/ntfy Thanks a lot for offering here. PS, there is a release freeze now, so it will be released as-is for debian Trixie, and we have time until the next release.