On Sat, Mar 23, 2024 at 11:45:58PM +0200, Adrian Bunk wrote:
> Control: tags 1067115 + patch
> Control: tags 1067115 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for gross (versioned as 1.0.2-4.1) and uploaded
> it to DELAYED/2. Please feel free to tell me if I should cancel it.
>
On Sun, Sep 10, 2023 at 09:59:53PM +0200, Sebastian Andrzej Siewior wrote:
> Hi Antonio!
>
> On 2023-09-10 15:57:58 [+0200], Antonio Radici wrote:
> > On Sun, Sep 10, 2023 at 01:38:33PM +0200, Salvatore Bonaccorso wrote:
> > > Hi Antonio,
> > >
> > &g
On Sun, Sep 10, 2023 at 01:47:30PM +0200, Salvatore Bonaccorso wrote:
> Hi Antonio,
>
> On Sun, Sep 10, 2023 at 01:24:10PM +0200, Antonio Radici wrote:
> > On Sun, Sep 10, 2023 at 01:05:31PM +0200, Antonio Radici wrote:
> > > Thanks for raising this, I'm uploading the new
On Sun, Sep 10, 2023 at 01:38:33PM +0200, Salvatore Bonaccorso wrote:
> Hi Antonio,
>
> FWIW, I have done the bookworm-security upload already to
> security-master, and still working on the bullseye-security one (with
> plan to release the DSA tonight ideally).
Ack, thanks for the update, I
On Sun, Sep 10, 2023 at 01:05:31PM +0200, Antonio Radici wrote:
> Thanks for raising this, I'm uploading the new packages with the fixes today.
apparently someone else did a NMU with the new version and incorrectly closed
the bug.
I reopened the bug because stable needs to be addressed (whic
On Sat, Sep 09, 2023 at 10:23:32PM +0200, Salvatore Bonaccorso wrote:
> Source: mutt
> Version: 2.2.9-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi,
>
> The following vulnerabilities were
On Tue, Nov 23, 2021 at 12:36:07PM -0800, Kevin J. McCarthy wrote:
> On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote:
> > Is there any progress with this bug?
>
> Mutt 2.1.3 included the corrected sort commit referenced in my last email.
> So, for unstable/testing it would be
On Wed, Aug 25, 2021 at 10:20:17AM +0200, Vincent Lefevre wrote:
> Package: mutt
> Version: 2.0.5-4.1
> Severity: grave
> Justification: causes non-serious data loss
>
> Mutt 2.1.2 is available. From the announce: "This is an important
> bug-fix release, fixing a potential data-loss IMAP bug.
On Fri, Sep 11, 2020 at 09:54:19AM +0200, Gian Piero Carrubba wrote:
> Package: cfengine3
> Followup-For: Bug #963341
>
> Hi,
>
> just a friendly ping that
> https://salsa.debian.org/cfengine-team/cfengine3/-/merge_requests/2
> fixes this (admittely also includes not strictly needed changes,
On Sun, Jun 21, 2020 at 02:23:52PM -0600, Michael Berg wrote:
>
> First, thank you for packaging cfengine 3.15.2.
>
> Unfortunately, the new cfengine 3.15.2 package in sid/unstable is
> broken and non-functional.
Thanks for the report, I'll look into it tomorrow.
Package: gqrx-sdr
Version: 2.12.1-1+b3
Severity: grave
Justification: renders package unusable
gqrx does not start in testing, this renders the package unusable.
The problem is reproducible by spinning up a testing chroot (as of today) and
trying to start gqrx
This is the stacktrace:
***
On Wed, Jan 09, 2019 at 12:03:03AM +0100, Moritz Mühlenhoff wrote:
> On Wed, Dec 19, 2018 at 11:56:47PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote:
> > > Source: cfengine2
> > > Severity: serious
> > >
> > > This is replaced by
On Tue, Aug 07, 2018 at 11:08:36AM +0200, Salvatore Bonaccorso wrote:
> Hi Antonio,
>
> On Tue, Aug 07, 2018 at 09:55:59AM +0100, Antonio Radici wrote:
> > Package: mutt
> > Version: 1.7.2-1
> > Severity: grave
> > Tags: security upstream
> > Justification
Package: mutt
Version: 1.7.2-1
Severity: grave
Tags: security upstream
Justification: security update
Tracking bug for security updates for mutt in stretch.
Details on https://security-tracker.debian.org/tracker/source-package/mutt
Patches are already provided by robe...@debian.org for jessie
On Wed, Nov 08, 2017 at 09:52:06AM +, Jonathan Dowland wrote:
> On Thu, Aug 03, 2017 at 10:21:51PM +0000, Antonio Radici wrote:
> > as I said on the original thread I'm planning to fix this, and as you
> > can see there have been no new releases until the fix is in place
On Thu, Aug 03, 2017 at 09:33:09AM -0700, Kevin McCarthy wrote:
> Package: mutt
> Version: 1.8.3+neomutt20170609-2
> Severity: serious
> Justification: Policy 2.3
>
> Dear Maintainer,
>
> I am the upstream project maintainer of Mutt. Your version of the
> "mutt" package in unstable and testing
On Sun, Jun 25, 2017 at 06:02:43AM +, Jamie Heilman wrote:
> It goes beyond just the tmpdir setting; for those of us who start our
> mutt configs with "reset all" we wind up with a more or less unusable
> mail client. In my case it screwed up decoding my aliases with
> "Warning: Bad IDN" for
@@ -3,7 +3,7 @@
> Priority: optional
> Maintainer: Antonio Radici <anto...@debian.org>
> Build-Depends: debhelper (>= 7.0.50), autoconf, automake, autotools-dev,
> - bison, dh-autoreconf, flex, libdb-dev, libssl-dev, libtool, perl (>= 5),
> + bison, dh-autoreconf, flex,
On Tue, Nov 15, 2016 at 08:05:59AM +0100, Petter Reinholdtsen wrote:
> [Antonio Radici]
> > the version in experimental builds fine with 1.1.0, I'll upload it to
> > unstable tonight.
>
> Thank you. Would you be willing to provide a backport of the package
> for jessie?
On Mon, Nov 14, 2016 at 12:29:04PM +0100, Petter Reinholdtsen wrote:
> Hi. Any news on fixing cfengine3 in time for the Stretch release? Is
> the problem reported upstream? Fixed in newer versions?
>
> The problem caused cfengine3 to be removed from testing three days ago.
Hi Peter,
the
Control: fixed -1 1.36-3
1.36-3 has the fix for this, have you tried to run that?
On Fri, Aug 26, 2016 at 08:11:22PM +0200, Sébastien Villemot wrote:
> Control: severity -1 serious
> Control: retitle -1 default config dir change from /etc/postgrey to
> /etc/postfix not handled
>
> Le vendredi 26 août 2016 à 19:19 +0200, Sébastien Villemot a écrit :
>
> > The postgrey package
On Wed, Aug 24, 2016 at 06:53:56PM +0100, Santiago Vila wrote:
> > > Version 1.6.2-2 depends on
> > >
> > > libgnutls30 (>=3.5.0)
> > > libnotmuch4 (>=0.21~rc1)
> > >
> > > These should be correct.
> >
> > yes, this was my fault, I've already asked a binNMU for amd64, the other
> > arch
> >
tag 835341 +pending
thanks
On Wed, Aug 24, 2016 at 02:48:00PM +, Viktor Jägersküpper wrote:
> Package: mutt
> Version: 1.6.2-3
> Severity: serious
>
> Dear Maintainer,
>
> the latest version of mutt has somehow got wrong dependencies (from an
> older version I guess) and so is not
tag 834818 +pending
thanks
On Fri, Aug 19, 2016 at 03:18:55PM +0100, Richard Russon wrote:
> This is fixed in commit:
> https://github.com/neomutt/neomutt/commit/9f06971bc0a1de06ef2db8d3d3f51baf0a2370dc
>
> This will be included in the next release of NeoMutt.
> The release was planned for
On Thu, Nov 27, 2014 at 02:49:27PM +1100, Murray McAllister wrote:
Good morning,
Jakub Wilk reported a crash in mutt:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771125
Looking in mutt-1.5.23-2.fc20.x86_64:
[...]
I'll have a patch/solution ready for this by tonight; thanks for
Hi,
this patch fixes the buffer overflow + RCE in the mutt version that is
currently in stable; I have already got the packages built and ready to be
uploaded.
Bug: http://bugs.debian.org/771125
CVE: CVE-2014-9116
Debdiff of the *dsc against the current version in stable is attached; let me
know
And the attachment is now, actually, attached :)
On Thu, Nov 27, 2014 at 10:13:39PM +, Antonio Radici wrote:
Hi,
this patch fixes the buffer overflow + RCE in the mutt version that is
currently in stable; I have already got the packages built and ready to be
uploaded.
Bug: http
A better debdiff is included, this does not include two vim artifacts at the
end of the first patch, sorry for the inconvenience.
On Thu, Nov 27, 2014 at 10:26:37PM +, Antonio Radici wrote:
And the attachment is now, actually, attached :)
On Thu, Nov 27, 2014 at 10:13:39PM +, Antonio
notfound 771125 mutt/1.5.23-1.1
thanks
It seems that the bug is not reproducible on the latest version in
unstable/testing.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thu, Nov 27, 2014 at 10:42:35PM +, Antonio Radici wrote:
A better debdiff is included, this does not include two vim artifacts at the
end of the first patch, sorry for the inconvenience.
Again, another debdiff; this time the patch has been modified to correctly skip
the case where end
On Fri, Nov 28, 2014 at 08:08:11AM +0100, Salvatore Bonaccorso wrote:
Control: found -1 1.5.23-1.1
Hi Antonio
On Thu, Nov 27, 2014 at 11:09:08PM +, Antonio Radici wrote:
notfound 771125 mutt/1.5.23-1.1
thanks
It seems that the bug is not reproducible on the latest version
On Wed, Jun 11, 2014 at 04:13:28PM +0200, Axel Beckert wrote:
Control: tag -1 + fixed-upstream
Hi,
Geoff Crompton wrote on 22 May 2014:
A fresh install of postgrey on two Wheezy machines fails to start. Much like
was the case in debian bug #722136, starting the postgrey daemon on the
On Mon, Oct 21, 2013 at 10:42:23AM +0200, Petter Reinholdtsen wrote:
As for options on how to move on, I suspect rewriting battery-stat as
a script and dropping the C daemon as I suggested in bug #720338 is
the best way forward. The task at hand do not really need much code.
I'll check what's
On Mon, Jun 17, 2013 at 10:01:28AM +0100, Iain Lane wrote:
Hi,
Since I was fixing this in Ubuntu I thought I'd help out and fix it
directly in Debian too.
I've prepared an NMU for mutt (versioned as 1.5.21-6.3) and uploaded it
to DELAYED/5. Please feel free to tell me if I should delay
tag 701864 +accepted
thanks
On Thu, Feb 28, 2013 at 09:41:42AM +0200, Damyan Ivanov wrote:
Package: cfengine3
Version: 3.0.5+dfsg-1
Severity: serious
The copyright file of cfengine3 version 3.0.5+dfsg-1 misses the full text of
the Frontier Artistic License, violating Debian Policy 12.5. A
tag 626294 +moreinfo
severity 626294 important
thanks
On Tue, May 10, 2011 at 05:52:01PM +0200, Jonas Meurer wrote:
Package: mutt
Version: 1.5.21-5
Severity: grave
Hello,
Since the upgrade to mutt 1.5.21-5, mutt occasionally crashes with a
segmentation fault at opening a IMAP maildir
tags 556496 + pending
tags 609115 + patch
tags 609115 + pending
thanks
Dear maintainer,
I've prepared an NMU for tokyocabinet (versioned as 1.4.37-6.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Cheers,
Antonio Radici
diff -Nru tokyocabinet-1.4.37
fixed 610191 1.5.21-4
thanks
I uploaded a version that fixes this yesterday night but unfortunately I
put the wrong bug to close in the debian/changelog, this should be fine
now.
Cheers
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
tag 610191 +confirmed
severity 610191 serious
thanks
On Mon, Apr 11, 2011 at 11:48:06AM +0200, Stefano Zacchiroli wrote:
Friendly ping about this bug report.
Any patch we users could test to help you out?
Cheers.
PS In the meantime the bugged mutt-patched has hit testing, which is
On Tue, Mar 22, 2011 at 12:57:17PM +1100, david b wrote:
Package: mutt
Version: 1.5.20-9+squeeze1
Severity: grave
Tags: security
Justification: user security hole
The gnutls implementation of ssl found in mutt, in mutt_ssl_gnutls.c, appears
to not validate
the common name of a remote
severity 619216 normal
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sun, Mar 06, 2011 at 07:20:20AM -0600, James Bottomley wrote:
The patch below is what I'm running.
Hi James,
thanks for the patch, I will integrate it and release later on today,
let's see if it improves the situation for Joey and anyone else who is
experiencing the problem.
Cheers
Antonio
On Thu, Feb 24, 2011 at 01:42:23PM -0400, Joey Hess wrote:
Seems that #441069 was about the same problem.
So, I've been bitten by this twice now. postgrey should not break
this badly when libdb is upgraded. If it's going to remain this crashy,
I will need to find some other greylister.
Hi
On Fri, Jan 14, 2011 at 02:35:04PM +0100, Julien Cristau wrote:
That doesn't sound grave to me. Just because you have to modify
/etc/init.d/cfengine3 instead of /etc/default/cfengine3 doesn't make the
package unusable, does it?
Hi Julien,
thanks for your quick answer; I thought this could be
severity 602404 important
severity 605044 important
reopen 605044
reopen 602404
thanks
On Fri, Jan 14, 2011 at 03:20:36PM +0100, Julien Cristau wrote:
[snip]
Then set it back to important, and fix it in 6.0.1 if you like.
OK!
Cheers
Antonio
--
To UNSUBSCRIBE, email to
On Tue, Jan 11, 2011 at 09:20:41AM +0100, Julien Cristau wrote:
On Tue, Jan 11, 2011 at 06:47:47 +0100, Christian PERRIER wrote:
Quoting Cyril Brulebois (k...@debian.org):
Crap. Yet another victim of this bug in mutt (I guess this is a bug in
mutt, I'm not sure of this), which I try to
It seems that the procedure has changed, I have created version 1.32-6 and
uploaded it to unstable, then submitted #606533 with an unblock request to
release.debian.org.
Cheers
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
tags 594451 +confirmed pending
thanks
On Tue, Nov 16, 2010 at 02:33:10PM +0200, Stefano Rivera wrote:
severity 575581 important
tags 575581 -patch
severity 594451 serious
tags 594451 +patch
thanks
Russell's report, bug 575581, says:
Program version 4.7 doesn't match environment version
tag 575581 +pending
thanks
On Tue, Nov 16, 2010 at 12:48:52PM +0200, Stefano Rivera wrote:
severity 575581 serious
thanks
Raising to RC, this broke an upgrade for me.
I will submit a fix for this tonight.
Cheers
Antonio
--
To UNSUBSCRIBE, email to
Hi Pierre,
is this fixed? if it is then the bug should be closed, otherwise, I suppose, the
package in testing won't be upgraded.
We, as mutt maintainers, would like to switch from gdbm to tokyocabinet but we
need a stable and up-to-date version in testing to do so :-)
Cheers
Antonio
--
To
On Fri, Dec 11, 2009 at 08:12:00AM +0100, Max Kellermann wrote:
Package: libv8-2.0.3
Version: 2.0.3-1
Severity: grave
Contrary to the package description, there is no shared library.
There is nothing except /usr/share/doc/libv8-2.0.3. Same is true for
the -dbg package. The symlink
Hi Kurt,
sorry for the late reply but I've been very busy at work, I've now got my free
time back :-)
I'm working on releasing version 2.0.3 on the library and I will check that it
builds fine in amd64 before uploading.
Thanks for your bug report.
Cheers
Antonio
--
To UNSUBSCRIBE, email to
tag 548467 +upstream confirmed pending
forwarded 548467 http://code.google.com/p/v8/issues/detail?id=429
thanks
On Sat, Sep 26, 2009 at 04:21:42PM +0200, Kurt Roeckx wrote:
Note that it's using -m32 and V8_TARGET_ARCH_IA32. I'm not sure
this is intentional or not.
Hi Kurt,
thanks for your bug
severity 546884 important
thanks
Hi Artur,
I've downgraded the severity to important and I hope we can reach an agreement
before upgrading it again :-) I'll explain what I think to you and then you can
tell me if I'm right or wrong.
First of all the severity: based on [0] the severity 'serious'
tag 519707 +confirmed pending
thanks
Hi James,
thanks for your report, I wrote a preinst script which is running a
db4.7_upgrade if we are upgrading from a version less than 1.31-1.
This is fixed in the git repo in collab-maint and it will be included in the
next release.
Cheers
Antonio
--
tag 521964 +patch
thanks
Hi,
this problem is due to the fact that the module uses the up-to-date APR calls
only if the APR_VERSION is 1.2.2, since we are using a version which is newer
than this the module belives that it is older (because it is 1.2.2) and it uses
the old API.
Removing the
tag 531737 moreinfo
thanks
Hi Peter,
thanks for your report, this seems really weird to me, I did not change anything in the localization
and it is failing with msgfmt; the bulgarian translation was added in 1.5.19-3 which built fine on MIPS.
Is there any way I can access the system and
Antonio Radici wrote:
Hi Peter,
thanks for your report, this seems really weird to me, I did not change
anything in the localization and it is failing with msgfmt; the
bulgarian translation was added in 1.5.19-3 which built fine on MIPS.
Sorry, let me clarify this, teh bulgarian
Hi Peter,
can you please relaunch the build of mutt 1.5.19-4 on mips? It looks to me as a
transient failure.
Cheers
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tag 530670 +pending
thanks
Hi,
debian/rules was modified with the following git commit:
08a1fabd9dc8a68cf09fa2df03e63f0402a5acc5
tokyocabinet is now excluded by default.
Cheers
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Hi Syd,
within this evening I will create a new package and ask my sponsor to
upload it.
Thanks a lot for the report.
Cheers
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
package ready, waiting for the sponsor to upload it
info for any DD who wants to do the upload for me
---
Your upload of the package 'cfengine2' to mentors.debian.net was
successful. Sponsors can now download it. The URL of your package is:
http://mentors.debian.net/debian/pool/main/c/cfengine2
63 matches
Mail list logo
