Control: forwarded -1 https://bugs.launchpad.net/hugin/+bug/2041687
On 2023-10-17 Michael Deegan wrote:
> Package: hugin
> Version: 2023.0~beta1+dfsg-1
> Severity: normal
> Hello, like in #799730, I encountered a case where stitching would abort,
> and the user would be left wondering why, with
Control: forwarded -1 https://bugs.launchpad.net/hugin/+bug/2041687
On 2023-10-17 Michael Deegan wrote:
> Package: hugin
> Version: 2023.0~beta1+dfsg-1
> Severity: normal
> Hello, like in #799730, I encountered a case where stitching would abort,
> and the user would be left wondering why, with
On 2023-10-26 Thomas Andrews via Exim-users wrote:
> On 10/25/23 23:09, Jeremy Harris via Exim-users wrote:
[...]
> > For use in a command line for a pipe transport, you'll need de-tainted
> > versions of those. Which means full verification of both components
> > against a local source of
On 2023-10-26 Vincent Lefevre wrote:
> On 2023-10-26 02:03:49 +0200, Vincent Lefevre wrote:
[...]
> Hmm... This seems to be due to a bug in the BTS when the bug was
> reopened for stable. At
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051563#25
> "Bug reopened Request was from
On 2023-10-23 SerNet Support Kevin Ivory wrote:
[...]
> That binary does not fix the problem of quote with space included:
> # /usr/sbin/exim4 -be '${run{/usr/bin/echo ${quote:hello world}}}'
> Failed: Expansion of "${quote:hello" from command "/usr/bin/echo
> ${quote:hello world}" in ${run}
On 2023-10-23 SerNet Support Kevin Ivory wrote:
> Hello Andreas,
> thanks for the info.
> I am not familiar with the Repository format at
> https://salsa.debian.org/exim-team/exim4/-/tree/12_bookworm?ref_type=heads
> Is there a binary or a package that I can test or do
> I have to patch and
On 2023-10-18 SerNet Support Kevin Ivory wrote:
> Hello Andreas,
> I just realized Debian Bug #1025420 is closed even though
> we are still running into it in exim 4.96-15+deb12u2
> Please try:
> # /usr/sbin/exim4 -be '${run{/usr/bin/echo ${quote:hello world}}}'
> Failed: Expansion of
On 2023-10-23 Jeremy Harris via Exim-users wrote:
> On 23/10/2023 06:37, Andreas Metzler via Exim-users wrote:
> > Exim's default setting for dkim_sign_headers is
> > extremely conservative and imho does not make sense.
> It's also as per RFC 6376 Section 5.4.1. "Recomm
On 2023-10-23 Ian Z via Exim-users wrote:
[...]
> I wonder what the fabulous debian configuration daoes in this respect.
We have a open bug about it
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939808 but have not
yet overridden exim's default.
cu Andreas
--
`What a good friend you are to
On 2023-10-22 Jeremy Harris via Exim-users wrote:
[...]
> If (and there's the question) you think that a DKIM signature should
> detect when a message has been modified, do you not think that
> adding headers is a modification?
Hello,
I think it depends on which the header would be added. Some
On 2023-10-21 Jonathan Kamens wrote:
> On 10/21/23 12:24, Andreas Metzler wrote:
> > However I still do not get it.
> > * Is there a useful scenario where someone would set save_seen=none in
> >the apt stanza?
> *shrug* I don't know. That design decision was mad
On 2023-10-21 Jonathan Kamens wrote:
> I just noticed this:
> On 10/21/23 01:39, Andreas Metzler wrote:
[...]
> > *save_seen=none*
> How did you end up with "save_seen=none" here? That's not the default, or at
> least it shouldn't be if everything is working as it s
On 2023-10-20 Jeremy Stanley wrote:
> It looks to me like the default Exim config in Debian explicitly
> calls /usr/bin/spfquery.mail-spf-perl from the spf-tools-perl
> package, not the libspf2 implementation supplied by the spfquery
> package. Also spf-tools-perl is suggested by exim4-base,
On 2023-10-20 Jeremy Stanley wrote:
> It looks to me like the default Exim config in Debian explicitly
> calls /usr/bin/spfquery.mail-spf-perl from the spf-tools-perl
> package, not the libspf2 implementation supplied by the spfquery
> package. Also spf-tools-perl is suggested by exim4-base,
On 2023-10-20 Mihamina RKTMB via Exim-users wrote:
> Hi all,
> Running Archlinux, I installed exim 4.96.2.
> I want to implement server side PLAIN and LOGIN auth against PAM.
[...]
> I think there is a problem with my "server_condition" in each authenticator,
> bu tI cannot figure out what is
Package: apt-listchanges
Version: 4.4
Severity: normal
Hello,
I had tested 4.0 and 4.1 and had seen old changelogs. Upgrading to 4.2
did not fix this (although it should have) so I purged apt-listchanges,
manually removed /var/lib/apt/listchanges* and reinstalled
apt-listchanges. Things seemed
On 2023-10-20 Backwoods BC wrote:
> On Fri, Oct 13, 2023 at 7:55 AM Andreas Metzler wrote:
> > On 2023-10-13 Backwoods BC wrote:
> > [...]
[...]
> TFM says:
> -atime n
> File was last accessed less than, more than or exactly n*24 hours ago.
> When find figures out h
On 2023-10-16 Larry Doolittle wrote:
> Control:
> found 941804 4.94.2-7+deb11u1
> found 941804 4.96-15+deb12u2
> found 941804 4.97~RC1-2
> severity 941804 normal
> thanks
> This exim4 bug has taken on increased importance now that gmail requires DKIM
> on all (?) incoming messages.
> I checked
On 2023-10-15 Wookey wrote:
[...]
> OK. So I read all that, and learned a whole load of stuff I was quite
> happy not knowing about.
> However despite reading it all, and especially this bit:
> "Whenever I've maintained man pages in roff I tend to be precise in
> > the usage of - and \-, but TBH
On 2023-10-15 Wookey wrote:
[...]
> OK. So I read all that, and learned a whole load of stuff I was quite
> happy not knowing about.
> However despite reading it all, and especially this bit:
> "Whenever I've maintained man pages in roff I tend to be precise in
> > the usage of - and \-, but TBH
On 2023-10-15 Wookey wrote:
[...]
> OK. So I read all that, and learned a whole load of stuff I was quite
> happy not knowing about.
> However despite reading it all, and especially this bit:
> "Whenever I've maintained man pages in roff I tend to be precise in
> > the usage of - and \-, but TBH
On 2023-10-01 Samuel Thibault wrote:
> Package: p11-kit
> Version: 0.25.0-4
> Severity: important
> Tags: patch
> Hello,
> p11-kit's build-dependency on gtk-doc-tools introduces an ample
> dependency loop. This can be avoided by adding a nodoc profile, as the
> attached patch does (chmod +x
Package: apt-listchanges
Version: 4.2
Severity: normal
Hello,
root@argenau:~# dpkg --purge apt-listchanges
(Reading database ... 181039 files and directories currently installed.)
Removing apt-listchanges (4.2) ...
Purging configuration files for apt-listchanges (4.2) ...
Processing triggers
On 2023-10-13 Backwoods BC wrote:
[...]
> find ./ -mtime +0 -mtime -1
> but this found nothing. When I changed it to:
> find ./ -mtime 0 -mtime -1
> it worked as desired and found all files less than a day old and not
> future-dated.
> Can someone tell me, please, if this is a bug or the
Control: tags -1 pending
On 2023-10-11 Eugene Berdnikov wrote:
> Package: exim4-config
> Version: 4.97~RC1-2
> Severity: normal
> Hello.
> Systemd unit "exi4.service" have "EnvironmentFile=-/etc/default/exim4",
> while post-install script generates /etc/default/exim (without "4").
[...]
>
On 2023-10-08 Hugh McMaster wrote:
[...]
> Try this in your d/watch file:
[...]
> # netpbm-free user guide
> opts="mode=svn, pgpmode=none, \
> component=userguide" \
> https://svn.code.sf.net/p/netpbm/code/userguide \
> HEAD ignore
>
> You want to match against HEAD to download the
On 2023-10-06 "Carlos Eduardo G. Carvalho (Cartola)"
wrote:
> Is there an Ubuntu or generic linux binary available?
The Debian package should work on recent enough Ubuntu.
cu Andreas
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You
Hello,
I would like to convert netpbm-free to a multiple component package, one
for the main code
http://netpbm.svn.code.sourceforge.net/p/netpbm/code/release_number/
which is versioned
and the docs from
http://netpbm.svn.code.sourceforge.net/p/netpbm/code/userguide/
with HEAD as
On 2023-10-07 Jonathan Wiltshire wrote:
[...]
> The version number in this request matches one we've had via a DSA (5512);
> are they the same or does the proposed upload supercede it?
[...]
Hello,
I will need to rebase the proposed changes version on top of the DSA. I
got early notice that a
On 2023-10-07 Jonathan Wiltshire wrote:
[...]
> The version number in this request matches one we've had via a DSA (5512);
> are they the same or does the proposed upload supercede it?
[...]
Hello,
I will need to rebase the proposed changes version on top of the DSA. I
got early notice that a
On 2023-10-06 Slavko via Exim-users wrote:
[...]
> hmm, i still cannot get how "network adjacent" is related to root
> privileges. But my head never was good for attacks...
Hello,
Afaiui the attack will require special DNS packets that would not be
sent out by a real recursive resolver. i.e. the
On 2023-10-02 Christof Meerwald via Exim-users
wrote:
> On Sun, 01 Oct 2023 20:35:48 +, Slavko via Exim-users wrote:
> > Dňa 1. októbra 2023 20:07:45 UTC používateľ Christof Meerwald via
> > Exim-users napísal:
> >>This was only officially confirmed today (which is very unfortunate),
> >
>
On 2023-10-01 Andreas Metzler wrote:
> On 2023-10-01 Rainer Dorsch wrote:
[...]
> > It would help if there would be a statement by the Debian exim
> > maintainer team, by when updates are expected to arrive.
> > This would at least help to judge, if I should migrate my s
On 2023-10-01 Andreas Metzler wrote:
> On 2023-10-01 Rainer Dorsch wrote:
[...]
> > It would help if there would be a statement by the Debian exim
> > maintainer team, by when updates are expected to arrive.
> > This would at least help to judge, if I should migrate my s
On 2023-10-01 Rainer Dorsch wrote:
> Package: exim4-base
> Version: 4.94.2-7
> Severity: critical
> Justification: breaks the whole system
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where appropriate ***
> There are various CVE report with a rating of 9.8/10.
On 2023-10-01 Rainer Dorsch wrote:
> Package: exim4-base
> Version: 4.94.2-7
> Severity: critical
> Justification: breaks the whole system
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where appropriate ***
> There are various CVE report with a rating of 9.8/10.
On 2023-09-26 Andreas Metzler wrote:
> On 2023-09-25 "T. Modes" wrote:
>> bruno...@gmail.com schrieb am Sonntag, 24. September 2023 um 19:37:10 UTC+2:
>>> I see this on fedora, this look a bit messed-up:
>>> $ pkg-config flann --libs
>>&g
On 2023-09-27 Helmut Grohne wrote:
> Source: exim4
> Version: 4.97~RC0-3
> Tags: ftbfs patch
> User: helm...@debian.org
> Usertags: dep17m2
> We want to change dh_installsystemd to install units to /usr. The exim4
> packaging also wants this and performs the change that we want in
> debhelper.
On 2023-09-25 "T. Modes" wrote:
> Hi Bruno and Andreas,
> bruno...@gmail.com schrieb am Sonntag, 24. September 2023 um 19:37:10 UTC+2:
> I see this on fedora, this look a bit messed-up:
> $ pkg-config flann --libs
> -L/usr/lib64\;-llz4 -lflann -lflann_cpp
> Is there something we can
On 2023-09-24 Bruno Postle wrote:
[...]
> I see this on fedora, this look a bit messed-up:
> $ pkg-config flann --libs
> -L/usr/lib64\;-llz4 -lflann -lflann_cpp
Hello,
I see similar breakage on Debian (hugin nevertheless built), and have
submitted a bug report
Package: libflann-dev
Version: 1.9.2+dfsg-1
Severity: serious
flann.pc looks broken:
Libs: -L${libdir} -L/usr/lib/x86_64-linux-gnu;-llz4 -lflann -lflann_cpp
^^^
cu Andreas
Package: libflann-dev
Version: 1.9.2+dfsg-1
Severity: serious
flann.pc looks broken:
Libs: -L${libdir} -L/usr/lib/x86_64-linux-gnu;-llz4 -lflann -lflann_cpp
^^^
cu Andreas
--
debian-science-maintainers mailing list
Package: libflann-dev
Version: 1.9.2+dfsg-1
Severity: serious
flann.pc looks broken:
Libs: -L${libdir} -L/usr/lib/x86_64-linux-gnu;-llz4 -lflann -lflann_cpp
^^^
cu Andreas
On 2023-09-24 Andreas Metzler wrote:
[...]
> * Does it make sense to have keyboxd as separate package that is
> depended on by gnupg? i.e. is other software than gnupg itselft
> supposed to use it?
Nevermind, I misread debian/control (gnupg metapackage vs gpg binary).
Should hit
On 2023-09-24 Andreas Metzler wrote:
> On 2023-09-22 Daniel Kahn Gillmor wrote:
> [...]
> > What do y'all think about uploading this into debian's experimental
> > repository for wider testing and consideration?
> I intend to work on that. (Both GIT and uploading).
H
On 2023-09-22 Daniel Kahn Gillmor wrote:
[...]
> What do y'all think about uploading this into debian's experimental
> repository for wider testing and consideration?
I intend to work on that. (Both GIT and uploading).
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other
On 2023-09-23 "T. Modes" wrote:
> Hi all,
> today we are releasing beta 1 of Hugin 2023.0.0
It is available in Debian/unstable for testing now.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time,
Thank you - fix confirmed.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/2037164
Title:
2023.0 beta1 assert after klick on [Stitch]
Status in Hugin:
Fix Committed
Bug description:
Hello,
Thank you - fix confirmed.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/2037164
Title:
2023.0 beta1 assert after klick on [Stitch]
Status in Hugin:
Fix Committed
Bug description:
Hello,
Public bug reported:
Hello,
klicking Stitch! on the Stitcher tab yields assert errors like this one:
-
ASSERT INFO:
/usr/include/wx-3.2/wx/strvararg.h(484): assert "(argtype &
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer():
format specifier doesn't match
Public bug reported:
Hello,
klicking Stitch! on the Stitcher tab yields assert errors like this one:
-
ASSERT INFO:
/usr/include/wx-3.2/wx/strvararg.h(484): assert "(argtype &
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer():
format specifier doesn't match
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler wrote:
[...]
> > Looking at the changelog entry
> > * Drop specify-timestamp.patch, applied upstream in binutils 2.41
> > (Closes: #1042734)
> > changing the rdeps does not m
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler wrote:
[...]
> > Looking at the changelog entry
> > * Drop specify-timestamp.patch, applied upstream in binutils 2.41
> > (Closes: #1042734)
> > changing the rdeps does not m
Control: tags 1052219 moreinfo
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu wrote:
> > Package: binutils-mingw-w64-i686
> > Version: 2.41-4+11+nmu1
[...]
>> The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
>> It causes libgcrypt20,
Control: tags 1052219 moreinfo
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu wrote:
> > Package: binutils-mingw-w64-i686
> > Version: 2.41-4+11+nmu1
[...]
>> The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
>> It causes libgcrypt20,
Package: libconfig-model-dpkg-perl
Version: 3.001
Severity: normal
Hello,
something in libconfig-model-dpkg-perl seems to have changed, when
upgrading guile-gnutls with "cme update dpkg-copyright" the generated
file moved from
Files: doc/gnutls-guile.texi
Copyright: @copyright{} 2001-2023, Free
On 2023-09-15 "László Böszörményi (GCS)" wrote:
[...]
> There's still a font issue, you will get something like:
> fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
> need installing?
> I don't know why this is happening, as if I check the intermediate dot
> file then only
On 2023-09-15 "László Böszörményi (GCS)" wrote:
[...]
> There's still a font issue, you will get something like:
> fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
> need installing?
> I don't know why this is happening, as if I check the intermediate dot
> file then only
On 2023-09-14 Marc Haber wrote:
> Package: exim4-base
> Version: 4.96-22
> Severity: normal
> Hi,
> in README.Debian we are documenting that MAIN_TLS_ENABLE is needed to
> make exim advertise STARTTLS. This is implemented in the configuration
> by bracketing the TLS configuration in an .ifdef
On 2023-09-11 debian...@sgt.at wrote:
> Package: exim4-daemon-heavy
[...]
>exim -be '${reduce {<\n
> 1.1.1.1\n2.2.2.2\n3.3.3.3\n4.4.4.4\n4.4.4.4\n}{}{${if !inlisti{$item}{<\n
> $value}{$value$item\n}{$value'
>output is :
> 4.4.4.4 -> last 4.4.4.4 not matched in list and last
On 2023-09-12 Philipp Marek via Pkg-gnutls-maint
wrote:
> > Are you actually testing /usr/bin/p11tool as shipped by gnutls-bin?
> > Please doublecheck.
> I believe I do?
> location:
> $ which p11tool
> /usr/bin/p11tool
[...]
Thank you.
I suspect the culprit might be one of pkcs11
On 2023-09-12 Peng Yu wrote:
> Hi,
> How to find directories that only contain a certain type of files (e.g.,
> .txt)?
> One idea that I have is to just search for all files' paths. Then use
> a post-processing script to analyze which directories only contain
> files of a certain type (e.g.,
On 2023-09-12 Philipp Marek via Pkg-gnutls-maint
wrote:
> Package: gnutls-bin
> Version: 3.8.1-4+b1
> Severity: normal
> X-Debbugs-Cc: phil...@marek.priv.at
> After removing libssl1.1:amd64=1.1.1o-1 I can't run p11tool any more:
> # LD_DEBUG=libs p11tool
>1708431: find
Hello,
I tried to do a test build of enblend against graphviz 8.1.0 from
experimental. I had no luck, since dot seems to be built without support
for png output:
/usr/bin/m4 --fatal-warnings --prefix-builtins --synclines
--define='dot_output_type=png' ../../doc/uml-dot.m4
Hello,
I tried to do a test build of enblend against graphviz 8.1.0 from
experimental. I had no luck, since dot seems to be built without support
for png output:
/usr/bin/m4 --fatal-warnings --prefix-builtins --synclines
--define='dot_output_type=png' ../../doc/uml-dot.m4
On 2023-08-09 Bastian Germann wrote:
> Control: notfound -1 gpgme1.0/1.18.0-3
> Control: tags -1 wontfix - ftbfs moreinfo
> Control: severity -1 minor
> Tagging this according to the conversation.
Was there something off-BTS?
The on-BTS discussion ended with finding the cause in
On 2023-09-07 Jeremy Harris via Exim-users wrote:
[...]
> Notable changes:
> - The internal (but exposed in logs, Received: headers and Message-ID:
> headers)
>identifier used for messages is longer than in the previous release
[...]
Hello,
there is typo/missing word in exim_id_update
On 2023-09-08 Jasen Betts via Exim-users wrote:
[...]
> https://packages.debian.org/search?keywords=libfile-fcntllock-perl
> seems to exist and have existed for several years.
> It's a dependancy of debhelper and dpkg-dev both of which are needed
> to build the debian packages for exim so it
Control: reassign -1 graphviz 2.42.2-7
On 2023-08-27 Aurelien Jarno wrote:
> Source: enblend-enfuse
> Version: 4.2-10
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Dear maintainer,
> enblend-enfuse fails to build from
Control: reassign -1 graphviz 2.42.2-7
On 2023-08-27 Aurelien Jarno wrote:
> Source: enblend-enfuse
> Version: 4.2-10
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Dear maintainer,
> enblend-enfuse fails to build from
Control: reassign -1 graphviz 2.42.2-7
On 2023-08-27 Aurelien Jarno wrote:
> Source: enblend-enfuse
> Version: 4.2-10
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Dear maintainer,
> enblend-enfuse fails to build from
On 2023-08-16 Andreas Metzler wrote:
[...]
> I would like to push another round of cherry-picked upstream fixes to
> bookworm. They have been part of the uploads to sid up to and including
> 4.96-19.
[...]
Hello,
I had to update the update since 75_78-Fix-free-of-value-after-run.pa
On 2023-08-16 Andreas Metzler wrote:
[...]
> I would like to push another round of cherry-picked upstream fixes to
> bookworm. They have been part of the uploads to sid up to and including
> 4.96-19.
[...]
Hello,
I had to update the update since 75_78-Fix-free-of-value-after-run.pa
On 2023-09-01 Ansgar wrote:
> Hi,
> a practical thing with usrmerge and legacy layout[1] is the following:
> assume you do not want programs to find a specific program via PATH
> lookup or even a fully-qualified path.
> Then a user can just divert that single program away (or just remove
> it,
On 2023-09-01 Ansgar wrote:
> Hi,
> a practical thing with usrmerge and legacy layout[1] is the following:
> assume you do not want programs to find a specific program via PATH
> lookup or even a fully-qualified path.
> Then a user can just divert that single program away (or just remove
> it,
On 2023-09-01 Slavko via Exim-users wrote:
[...]
> You have several options:
> + use forking type unit (not appropriate in all cases)
> + disable kill in unit (not very good idea)
> + setup sendwait in mailx (not with bsd-mailx)
> + use exim directly with -odf
> + use cron for repeated tasks
+
On 2023-08-28 Slavko via Exim-users wrote:
[...]
> The only changes which i did, are -- i add path option to transport:
> path = /my/scripts/path
Hello,
So you tell it to search *exclusively* there.
> I changed command name to relative (without path) in redirect router:
> data =
On 2023-08-23 Erik Huelsmann wrote:
> On Tue, Aug 22, 2023 at 10:17 AM Andreas Metzler wrote:
[...]
>> What do the logfiles say for this delivery?
> $ zgrep 1qTkmU-00F3DW-2D /var/log/exim4/mainlog*
> /var/log/exim4/mainlog.10.gz:2023-08-13 00:10:02 1qTkmU-00F3DW-2D int
On 2023-08-23 Andreas Metzler wrote:
> On 2023-08-22 Bill Brelsford via Exim-users wrote:
>> Under Exim 4.96-19 in Debian unstable/testing, ${run fails to put
>> standard output into $value. E.g., in a .forward file,
[...]
> This is recent breakage - Checking the
On 2023-08-22 Bill Brelsford via Exim-users wrote:
> Under Exim 4.96-19 in Debian unstable/testing, ${run fails to put
> standard output into $value. E.g., in a .forward file,
> if "${run{/bin/echo -n foo}{}}$runrc" is not 99
> then save /tmp/exim-$runrc-$value endif
> creates file
On 2023-08-21 Erik Hulsmann wrote:
> Package: exim4
> Version: 4.96-19
> Severity: important
> Dear Maintainer,
> we've got a setup with users' .forward files.
> Handling these seems broken to me - strace shows this:
[...]
Hello,
is thisv reproducible for you? What do the logfiles say for
On 2023-08-19 Diederik de Haas wrote:
> [please CC me as I'm not subscribed to debian-devel]
> On Mon, 17 Jul 2023 at 21:45:13 +1000, Hugh McMaster wrote:
> > On Mon, 17 Jul 2023 at 00:07, Simon McVittie wrote:
> > > On Sun, 16 Jul 2023 at 22:38:20 +1000, Hugh McMaster wrote:
> > > > Currently,
On 2023-07-24 Andreas Metzler via Exim-users wrote:
> I am currently playing around with shipping a native systemd service
> file for exim.
[...]
I have now uploaded to Debian/experimental.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful
.-Bug-3014.patch: Fix on-demand
+ TLS cert expiry date. Closes: #1043233
+ (Upstream bug 3014)
+
+ -- Andreas Metzler Wed, 16 Aug 2023 15:12:39 +0200
+
exim4 (4.96-15+deb12u1) bookworm; urgency=medium
* 75_42-Fix-run-arg-parsing.patch (From upstream GIT master, backported by
diff
.-Bug-3014.patch: Fix on-demand
+ TLS cert expiry date. Closes: #1043233
+ (Upstream bug 3014)
+
+ -- Andreas Metzler Wed, 16 Aug 2023 15:12:39 +0200
+
exim4 (4.96-15+deb12u1) bookworm; urgency=medium
* 75_42-Fix-run-arg-parsing.patch (From upstream GIT master, backported by
diff
On 2023-08-16 Jeff Welty wrote:
> I just went through and cleaned up all the warnings on rc2 (thanks to
> @Robert Clausecker for pointing them out).
> What I didn't clean up are the warnings for strncpy() and snprint() about
> truncation of strings.
> There appear to be a couple of logical bugs
On 2023-08-15 Boyuan Yang wrote:
[...]
> where .po file that contains translation is updated every time, causing dpkg-
> source to complain the diff and quit when building twoce in a row.
> Take https://tracker.debian.org/pkg/ibus-array as an example. The upstream
> project does not include .pot
On 2023-08-15 Daniel Kahn Gillmor wrote:
[...]
> The libgpg-error packaging Andreas as produced for experimental looks to
> me like it should probably be uploaded to unstable directly, as that's
> useful work regardless of what version of GnuPG is in the archive.
[...]
I will do that.
cu
Control: tags -1 pending
On 2023-08-13 Lucas Nussbaum wrote:
> Source: gnutls28
[...]
> This package fails to build a source package after a successful build
> (dpkg-buildpackage ; dpkg-buildpackage -S).
[...]
Thanks, now fixed in Git.
cu Andreas
signature.asc
Description: PGP signature
Control: tags -1 patch
On 2023-08-13 Lucas Nussbaum wrote:
> Source: byacc
> Version: 1:2.0.20221106-1
> Severity: minor
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
> User: debian...@lists.debian.org
> Usertags: qa-doublebuild
> Hi,
On 2023-04-30 Andreas Metzler wrote:
[...]
> However I have updated the GIT branches to 2.4.1 today.
Now at 2.4.3.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
signature.asc
Descript
On 2023-08-11 Bruno Postle wrote:
> libpano13 is the PanoTools library for panoramic imaging.
> A libpano13-2.9.22 rc2 tarball has been uploaded to sourceforge, this is
> a release candidate for testing that may become the final release:
[...]
Thank you, looks good. (Uploaded to
On 2023-08-10 "Torrance, Douglas" wrote:
[...]
> I've applied the patch that you submitted upstream [1] to the package. I
> think this should fix the issue. See the latest draft in Salsa [2].
> Does this look okay?
Thank you, yes. (As you are no doubt aware) there is a functionally
identally
On 2023-08-10 "Torrance, Douglas" wrote:
[...]
> I've applied the patch that you submitted upstream [1] to the package. I
> think this should fix the issue. See the latest draft in Salsa [2].
> Does this look okay?
Thank you, yes. (As you are no doubt aware) there is a functionally
identally
Good morning,
guile-gnutls was uploaded almost a week ago to sid, but the unstable
autobuilders seem to ignore it.
https://buildd.debian.org/status/package.php?p=guile-gnutls
Is there anything I can do? The experimental uploads were picked up
seamlessly.
cu Andreas
--
`What a good friend you
Package: libwraster6
Version: 0.96.0-1
Severity: grave
Tags: upstream
Justification: Policy 8.6.2
Hello,
already communicated upstream, lets add a blocker bug. The new release
bumped the symbol version of all symbols from LIBWRASTER6 to
LIBWRASTER7, i.e. we have got total ABI breakage, none of
Package: libwraster6
Version: 0.96.0-1
Severity: grave
Tags: upstream
Justification: Policy 8.6.2
Hello,
already communicated upstream, lets add a blocker bug. The new release
bumped the symbol version of all symbols from LIBWRASTER6 to
LIBWRASTER7, i.e. we have got total ABI breakage, none of
Control: tags -1 confirmed
Control: found -1 4.95~RC0-1
Control: forwarded -1 https://bugs.exim.org/show_bug.cgi?id=3014
Control: tags -1 patch
On 2023-08-07 Björn Wiberg wrote:
> Package: exim4-base
> Version: 4.96-15+deb12u1
> Severity: normal
> Hello,
> When using built-in on-connect
On 2023-08-01 Helmut Grohne wrote:
[...]
> In moving crontab_setgid from lib to libexec, you effectively evade the
> moratorium and are entitled to also move from / to /usr. This is an
> action you can do right now. The move from /lib to /usr/libexec prevents
> the file loss scenario that spurred
Package: guile-gnutls
Version: 3.7.12
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
I have already forwarded this upstream
https://gitlab.com/gnutls/guile/-/issues/15
301 - 400 of 13410 matches
Mail list logo
