Search Criteria
Package Details: proftpd 2:1.3.9a-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/proftpd.git (read-only, click to copy) |
|---|---|
| Package Base: | proftpd |
| Description: | High-performance, scalable FTP SSL TLS and SFTP server |
| Upstream URL: | http://www.proftpd.org/ |
| Licenses: | GPL |
| Submitter: | xyproto |
| Maintainer: | severach |
| Last Packager: | severach |
| Votes: | 60 |
| Popularity: | 0.000872 |
| First Submitted: | 2013-05-16 15:03 (UTC) |
| Last Updated: | 2026-04-30 17:03 (UTC) |
Dependencies (14)
- acl (acl-gitAUR)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- hiredis (hiredis-gitAUR)
- libcap
- libldap (libldap-gnutlsAUR)
- libsodium (libsodium-gitAUR, libsodium-1.0.18AUR)
- libxcrypt (libxcrypt-gitAUR)
- mariadb-libs (libmysqlclient81AUR, libmysqlclient80AUR, libmysqlclient84AUR, libmysqlclientAUR, mariadb-lts-libs)
- ncurses (ncurses-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR, openssl-aegisAUR)
- pam (pam-selinuxAUR)
- perl (perl-gitAUR)
- postgresql-libs (postgresql-libs-12AUR, postgresql13-libsAUR, postgresql-libs-gitAUR)
- zlib (zlib-gitAUR, zlib-ng-compat-gitAUR, zlib-ng-compat)
Latest Comments
1 2 3 4 5 6 7 Next › Last »
btw_user commented on 2026-05-06 08:18 (UTC) (edited on 2026-05-06 08:20 (UTC) by btw_user)
error: failed to parse srcinfo for 'proftpd-2:1.3.9a-1': key 'makedepends' requires a value: Line 10: makedepends =
i just removed + and makepkg -si
df8oe commented on 2026-05-02 12:56 (UTC)
Can you please add aarch64 architecture? I can confirm package builds and software is working perfectly using aarch64.
severach commented on 2026-04-30 16:45 (UTC) (edited on 2026-04-30 16:46 (UTC) by severach)
As mentioned before proftpd's versioning jumping from 1.3.9 to 1.3.9a is not compatible with Arch Linux vercmp. It is a downgrade, not an upgrade. In the past the epoch had to be incremented to get this to be seen as an upgrade. I looked at different ways to avoid incrementing the epoch and the best I came up with was to change 1.3.9 to 1.3.9A which -> 1.3.9a is considered an upgrade. This causes the 1.x.xA version to be bogus and Repology knows it. In the past this wasn't a problem because 1.x.x was often updated with 1.x.xa within a few days. Now proftpd is super stable and the 1.x.x versions you'd think would be full of new bugs actually last for months.
usta commented on 2026-04-30 07:13 (UTC)
@severach : I have found another big problem. Even the package looks like 1.3.9a but it is using 1.3.9 version's tar package ( old version ) so it doesnt have related fix. So we should fix this
usta commented on 2026-04-30 06:53 (UTC)
@severach this one urgently updated due to a high risk remote code execution exploit ( - Issue 2052 - SQL injection possible via mod_sql because of is_escaped_text() logic error (CVE-2026-42167).) Related fix exist on latest release ( even it called rc1 ) : 1.3.10rc1
https://github.com/proftpd/proftpd/releases/tag/v1.3.10rc1
tee commented on 2025-06-17 11:46 (UTC)
build with
-std=gnu17eomanis commented on 2025-06-09 22:21 (UTC)
At least ProFTPD
1.3.8cand1.3.8ddo not build on Arch anymore since Arch switched to GCC 15 on April 29 2025 [1], because GCC 15 changed the default C language version from C17 to C23 [2] and those ProFTPD releases contain C code that violates C23:Version
1.3.9does build successfully with GCC 15 though.[1] https://gitlab.archlinux.org/archlinux/packaging/packages/gcc/-/commit/b6f2fc50b4e1252a47bcbd1a85a18943de07f90f
[2] https://gcc.gnu.org/gcc-15/changes.html#c
deadite66 commented on 2025-06-08 11:02 (UTC)
can we change source to
source=("v${pkgver}.tar.gz::https://github.com/proftpd/proftpd/archive/refs/tags/v${pkgver}.tar.gz"
as ftp is depreciated.
also 1.3.8d failed to compile for me but 1.3.9 was ok.
severach commented on 2024-12-26 20:00 (UTC)
@eomanis: not a yay bug. pacman vercmp also calculates the upgrade incorrectly.
vercmp 1.3.8 1.3.8awould need to be -1 to indicate an upgrade, not 1. I've added some code for improved update detection.@mmkodali: The vercmp bug elsewhere linked against OpenSSL-1.1 which crashed mod_sql. That should all be fixed.
1 2 3 4 5 6 7 Next › Last »