Pigeonhole 0.5.11 released
We are pleased to release pigeonhole 0.5.11. You can download it from locations below:
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11... https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11... Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot
Aki Tuomi Open-Xchange oy
- managesieve: managesieve_max_line_length setting is now a "size" type instead of just number of bytes. This allows using e.g. "64k" as the value.
- lib-sieve: When folding white space is used in the Message-ID header, it is not stripped away correctly before the message ID value is used, causing e.g. garbled log lines at delivery.
On 2020-08-12 09:02, Aki Tuomi wrote:
We are pleased to release pigeonhole 0.5.11. You can download it from locations below:
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11... https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11...
Unfortunately you broke all build systems (rpm, deb, ...) with that release name.
.11 should have neve been included in the name. As you can see from previous releases the dovecot patch number was never in the pigeonhole tarball release name.
Cheers, K. C.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
FreeBSD ports as well:
I] ➜ make makesum ===> License LGPL21 accepted by the user ===> License LGPL21 accepted by the user ===> dovecot-pigeonhole-0.5.11 depends on file: /usr/local/sbin/pkg - found => dovecot-2.3-pigeonhole-0.5.11.tar.gz doesn't seem to exist in /home/ler/FreeBSD/ports/distfiles/. => Attempting to fetch http://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.tar... fetch: http://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.tar...: Not Found => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/dovecot-2.3-pigeonhole-0.5.11.t... fetch: http://distcache.FreeBSD.org/ports-distfiles/dovecot-2.3-pigeonhole-0.5.11.t...: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /home/ler/FreeBSD/ports/distfiles/ and try again. *** Error code 1
Stop. make[1]: stopped in /home/ler/FreeBSD/ports/mail/dovecot-pigeonhole *** Error code 1
Stop. make: stopped in /home/ler/FreeBSD/ports/mail/dovecot-pigeonhole
ler in ports/mail/dovecot-pigeonhole at borg took 3s [I] ➜
On Wed, Aug 12, 2020 at 2:48 PM Helmut K. C. Tessarek tessarek@evermeet.cx wrote:
On 2020-08-12 09:02, Aki Tuomi wrote:
We are pleased to release pigeonhole 0.5.11. You can download it from locations below:
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11...
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11...
Unfortunately you broke all build systems (rpm, deb, ...) with that release name.
.11 should have neve been included in the name. As you can see from previous releases the dovecot patch number was never in the pigeonhole tarball release name.
Cheers, K. C.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
On 13/08/20 7:48 am, Helmut K. C. Tessarek wrote:
On 2020-08-12 09:02, Aki Tuomi wrote:
We are pleased to release pigeonhole 0.5.11. You can download it from locations below:
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11... https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11...
Unfortunately you broke all build systems (rpm, deb, ...) with that release name.
.11 should have neve been included in the name. As you can see from previous releases the dovecot patch number was never in the pigeonhole tarball release name.
Yes, please fix in future releases. I already have to define the 2.3 separately from the 11.3 in my spec file, with this change I either have to rename the file or have three definitions: 2.3, 11 and 3 (I renamed the file).
Peter
On 12/08/2020 23:39 Peter peter@pajamian.dhs.org wrote:
On 13/08/20 7:48 am, Helmut K. C. Tessarek wrote:
On 2020-08-12 09:02, Aki Tuomi wrote:
We are pleased to release pigeonhole 0.5.11. You can download it from locations below:
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11... https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11...
Unfortunately you broke all build systems (rpm, deb, ...) with that release name.
.11 should have neve been included in the name. As you can see from previous releases the dovecot patch number was never in the pigeonhole tarball release name.
Yes, please fix in future releases. I already have to define the 2.3 separately from the 11.3 in my spec file, with this change I either have to rename the file or have three definitions: 2.3, 11 and 3 (I renamed the file).
Peter
Hi!
Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course we will do our best to ensure this won't happen again.
Would it fix your build systems if we simply rename the file?
Regards, Aki
On 2020-08-12 17:16, Aki Tuomi wrote:
Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course we will do our best to ensure this won't happen again.
Would it fix your build systems if we simply rename the file?
Renaming the file won't help, since it will still create the wrong directory name upon decompressing.
Cheers, K. C.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
Oops. Your right. :(
On Wed, Aug 12, 2020 at 4:19 PM Helmut K. C. Tessarek tessarek@evermeet.cx wrote:
On 2020-08-12 17:16, Aki Tuomi wrote:
Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course we will do our best to ensure this won't happen again.
Would it fix your build systems if we simply rename the file?
Renaming the file won't help, since it will still create the wrong directory name upon decompressing.
Cheers, K. C.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
On 13/08/2020 00:19 Helmut K. C. Tessarek tessarek@evermeet.cx wrote:
On 2020-08-12 17:16, Aki Tuomi wrote:
Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course we will do our best to ensure this won't happen again.
Would it fix your build systems if we simply rename the file?
Renaming the file won't help, since it will still create the wrong directory name upon decompressing.
Cheers, K. C.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
I've added symlink for dovecot-2.3-pigeonhole-0.5.11.tar.gz, if it helps someone's build system.
I'll discuss this with our team if there is something we can do at this point.
Aki
On 2020-08-12 17:22, Aki Tuomi wrote:
I've added symlink for dovecot-2.3-pigeonhole-0.5.11.tar.gz, if it helps someone's build system.
I'll discuss this with our team if there is something we can do at this point.
The problem is, they are not "our" build systems, but all build systems. The ones used by Fedora, Redhat, Debian, FreeBSD, ArchLinux, ...
I really meant all build systems. Or at least all build systems that depend on a correect naming srtucture, which most systems do.
The only fix is to release a new tarball (that also includes the correct directory name) with a new signature. It doesn't mean you have to remove the old one. Just add the new one to the download site: https://pigeonhole.dovecot.org/releases/2.3/
Cheers, K. C.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
On 13/08/20 9:16 am, Aki Tuomi wrote:
Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course we will do our best to ensure this won't happen again.
Would it fix your build systems if we simply rename the file?
As K. C. pointed out, it doesn't because the files still unpack into the wrong directory. I've managed to work around it for now with a tweak to the spec file, though.
Peter
participants (5)
-
Aki Tuomi
-
Aki Tuomi
-
Helmut K. C. Tessarek
-
Larry Rosenman
-
Peter