From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Roman Schnider <R.Schnider@cab.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2] pureftpd: version bump 1.0.36 -> 1.0.52
Date: Wed, 11 Jun 2025 10:32:10 +0200 [thread overview]
Message-ID: <aEk_Coy2CIZI-CGZ@pengutronix.de> (raw)
In-Reply-To: <aea5028e-1ee8-412a-b6d2-42de489cb9e6@cab.de>
On Wed, Jun 11, 2025 at 08:07:18AM +0000, Roman Schnider wrote:
> On 06.06.25 17:36, Michael Olbrich wrote:
> > On Mon, May 26, 2025 at 08:36:09AM +0200, Roman Schnider via ptxdist wrote:
> >> Various bug fixes and improvements:
> >> https://www.pureftpd.org/project/pure-ftpd/news/
> >>
> >> Added license
> >>
> >> Signed-off-by: Roman Schnider <r.schnider@cab.de>
> >> ---
> >> v2:
> >> keep download URL for older releases
> >> ---
> >> rules/pureftpd.make | 6 ++++--
> >> 1 file changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/rules/pureftpd.make b/rules/pureftpd.make
> >> index 8f447b528..80b333133 100644
> >> --- a/rules/pureftpd.make
> >> +++ b/rules/pureftpd.make
> >> @@ -13,8 +13,8 @@ PACKAGES-$(PTXCONF_PUREFTPD) += pureftpd
> >> #
> >> # Paths and names
> >> #
> >> -PUREFTPD_VERSION := 1.0.36
> >> -PUREFTPD_MD5 := 7899c75c1fed7dbad0352eb31080e066
> >> +PUREFTPD_VERSION := 1.0.52
> >> +PUREFTPD_MD5 := 6fdd75053b7aaa0f45089a7bf7fcd0b4
> >> PUREFTPD := pure-ftpd-$(PUREFTPD_VERSION)
> >> PUREFTPD_SUFFIX := tar.bz2
> >> PUREFTPD_URL := \
> >> @@ -22,6 +22,8 @@ PUREFTPD_URL := \
> >> http://download.pureftpd.org/pub/pure-ftpd/releases/obsolete/$(PUREFTPD).$(PUREFTPD_SUFFIX)
> >> PUREFTPD_SOURCE := $(SRCDIR)/$(PUREFTPD).$(PUREFTPD_SUFFIX)
> >> PUREFTPD_DIR := $(BUILDDIR)/$(PUREFTPD)
> >> +PUREFTPD_LICENSE := ISC AND BSD-3-Clause
> >> +PUREFTPD_LICENSE_FILES := file://COPYING;md5=5138d4a8a877b32de6a78cf7e9e99c25
> >
> > This file does not contain the BSD-3-Clause license text. Please add
> > src/bsd-glob.c as another file with the appropriate startline/endline.
> >
>
> Looking at the other src/bsd-* files, I would also add
> - src/bsd-getopt_long.c (BSD-2-Clause) and
> - src/bsd-getopt_long.h (BSD-4-Clause)
>
> Fine with this?
Yes, absolutely.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-06-11 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 6:36 Roman Schnider via ptxdist
2025-06-06 15:36 ` Michael Olbrich
2025-06-11 8:07 ` Roman Schnider via ptxdist
2025-06-11 8:32 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aEk_Coy2CIZI-CGZ@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=R.Schnider@cab.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox