Bug#732859: mutt: 1.5.22 is avilable

[Antonio Radici]

On Sun, Dec 22, 2013 at 06:07:57PM +0100, Elimar Riesebieter wrote:
> Package: mutt
> Version: 1.5.21+hg20101013-0lxtec4
> Severity: wishlist
> 
> 
> Is there a chance to package 1.5.22 in the near future?

Yes, will prepare the package in the coming days and will upload it within this
week.

Sorry for the delay.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699809: cfengine3 packaging project on github

[Antonio Radici]

On Tue, Feb 18, 2014 at 04:08:15PM +0100, Thomas Koch wrote:
> Hi,
> 
> this is a reply to the debian bug report asking for a newer cfengine version, 
> CCing the members of the debian packaging team on github.
> 
> It seems there are people working on packaging a current cfengine version at 
> github:
> https://github.com/Webhuis/Cfengine-debian/wiki
> 
> I don't know, whether there have been trials to contact the current (MIA?) 
> maintainer of cfengine3, Antonio Radici. I'll send a MIA request to debian-
> devel right after this mail
> 
> @DebianPackagingTeam: Do you need any help? I'm not a DD, so I can't sponsor 
> your packages, but I might have some experience in packaging. Do you have an 
> estimation of when there might be an upload of cfengine 3.[56] to Debian?

Thomas, I have already had several meeting on hangouts with the members of the
cfengine3 packaging team on git and we agreed on what is the path forward: i.e.:
they will solve the current issues that we discussed already and then we will
start releasing that version, after a couple of releases we will transfer the
ownership of the debian package to a cfengine3 packaging team, so that the
burden will not lie on a single person.

If you have any questions let me know.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#574678: init_acpi_acadapt() returned NOT_SUPPORTED.

[Antonio Radici]

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 involved in the script conversion ASAP


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#748918: postgrey fails to start

[Antonio Radici]

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
> > command
> > line reveals the same failure mode:
> > 
> > $ sudo postgrey --inet 10023
> > 2014/05/22-19:09:07 postgrey (type Net::Server::Multiplex) starting!
> > pid(15633)
> > Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
> > Binding to TCP port 10023 on host 127.0.0.1 with IPv4
> > Insecure dependency in bind while running with -T switch at
> > /usr/lib/perl/5.14/IO/Socket.pm line 202.
> > 
> > Applying the same patch,
> > https://github.com/yasuhirokimura/postgrey/commit/9673b54064691a5b9c295ffea340d8a1f9ee1cb8,
> > fixes this problem for me.
> 
> Despite not being mentioned in the upstream changelog[1], that patch
> has been applied[2] upstream and is part of the recent 1.35 upstream
> release[3].
> 
> [1] http://postgrey.schweikert.ch/pub/Changes
> [2] https://github.com/schweikert/postgrey/commits/master
> [3] http://postgrey.schweikert.ch/pub/postgrey-1.35.tar.gz
> 
> So packaging the new upstream release should fix the issue in Sid and
> Jessie. Maybe a stable-update with only that patch would be a good
> idea, too.
> 
> Antonio and Jon: Do you need help in maintaining postgrey in Debian?
> 
> I'm a long-time postgrey user at work as well as at home, and
> occassionally contribute to upstream's default whitelist. I also know
> postgrey's upstream developer from maintaining fping in Debian which
> has the same upstream developer. I could join you as co-maintainer.

Hi Axel,
if you have time it would be great if you could prepare an NMU for the patch at
the existing release and then I can add you as co-maintainer and we can work on
the 1.35 packaging (there is already a git, you just need to be on
collab-maint).

On the long run we should run postgrey using a team rather than a single person
(me), that should make things easier in terms of maintainership and uploads.

Does it sound good to you?

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683893: mutt: diff for NMU version 1.5.21-6.2

[Antonio Radici]

On Fri, Aug 24, 2012 at 08:55:37AM +0200, Ansgar Burchardt wrote:
> tags 683893 + pending
> thanks
> 
> Dear maintainer,
> 
> I've prepared an NMU for mutt (versioned as 1.5.21-6.2) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

It looks good to me, thanks for taking care of this!

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#654148: Please enabled hardened build flags

[Antonio Radici]

On Wed, Jun 20, 2012 at 10:20:39PM +0200, Moritz Muehlenhoff wrote:
> What's the status? The freeze is really soon now.
> 

Sorry for the continuous delay, I'll have the update ready tonight; if
this bug is not updated by tonight feel free to NMU.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#654148: Please enabled hardened build flags

[Antonio Radici]

On Wed, Jun 20, 2012 at 10:20:39PM +0200, Moritz Muehlenhoff wrote:
> On Fri, Apr 13, 2012 at 09:23:27AM +0200, Antonio Radici wrote:
> > On Fri, Apr 06, 2012 at 06:58:59PM +0200, Antonio Radici wrote:
> > > Sorry I missed this message; I'll have an upload ready for tomorrow.
> > 
> > I haven't forgotten this message, I'll have the upload ready for this
> > weekend, sorry for the delay.
> 
> What's the status? The freeze is really soon now.

Just uploaded mutt 1.5.21-6 (also tagged in the git repo).
Now waiting for ftp-master to accept it.

Sorry again for the delay.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#618425: mutt 1.5.21-5 pending

[Antonio Radici]

On Sat, Jul 21, 2012 at 12:34:37AM -0500, Jonathan Nieder wrote:
> Hi Antonio,
> 
> On Fri, Apr 15, 2011, Antonio Radici wrote:
> 
> > tag 618425 +pending
> > tag 622145 +pending
> > tag 620945 +pending
> > tag 578098 +pending
> > tag 539737 +pending
> > thanks
> 
> Do you mean that you have fixes for these bugs that are pending
> upload, or just that you are working on them?
> 
> If the latter, I'd suggest using "owner" or some other indication
> instead of 'pending', since the latter is usually used to indicate a
> bug for which a fix has been commited and just hasn't been uploaded to
> the archive yet.  That would make it easier for interested others to
> understand the current status.

Hi Jonathan,
yes I had tentative fixes on my workstation but I ended up either not
testing them or not committing them to git, I will review again the bugs
this afternoon and see which ones need to get their status reverted
(i.e. -pending).

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626294: segmentation fault at opening imap folder

[Antonio Radici]

On Tue, Jul 31, 2012 at 01:06:19AM -0500, Luis Mochan wrote:
> Package: mutt
> Version: 1.5.21-6.1
> Followup-For: Bug #626294
> 
> Dear Maintainer,
> For some unknown reason my gnome-shell session crashed. At the time I was 
> using
> mutt. The next few times I started, mutt crashed while getting headers for an
> IMAP account. The problem seems to have been solved by removing (actually,
> renaming) the cached headers' file, in this case INBOX.hcache in the
> corresponding imap:... subdirectory of my cache directory. My guess is that 
> the
> gnome crash left the header cache file in a bad state.
> Regards,
> Luis

Despite the bad state we don't expect mutt to segfault :(
have you got any core for that problem? Is it reproducible in any way?

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#701864: 'Frontier Artistic License' text missing in debian/copyright

[Antonio Radici]

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 pointer to a 
> web 
> page with the license is not a "verbatim copy of its copyright information 
> and 
> distribution license".
> 

Thanks for opening the bug, I will fix it this weekend.

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626294: Updated patch for #626294 and #584138

[Antonio Radici]

On Mon, May 13, 2013 at 07:11:58PM +0200, Evgeni Golov wrote:
> On Sun, Sep 25, 2011 at 05:16:16PM +0200, Nikolaus Schulz wrote:
> 
> > Attached is an updated version of
> > 584138-mx_update_context-segfault.patch that seems to fix the problem.
> > Copied from upstream changeset 0e4f1782ea2e.
> 
> This bug has been hitting me since the update to Wheezy.
> The updated patch solves the issue perfectly.
> 
> Can we please make sure this makes into the first point release?

Yes, sorry for the inconvenience, a new binary for this will be prepared on
Sunday evening (May 19th), then I will follow the procedure to get it into
stable-proposed-updates.

Cheers,
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#497128: gnome-power-manager: Strange behaviour on plugging in and out the power.

[Antonio Radici]

Hi,
I'm being hit by the same bug, it happens when g-p-m is running and I
either connect the PC to the power adapter or disconnect it from it
(even if the battery is FULL)

The output of gnome-power-bugreport is attached.

Cheers
Antonio
Distro version:   squeeze/sid
Kernel version:   2.6.30-2-686
g-p-m version:2.28.3
HAL version:  0.5.14
System manufacturer:  missing
System version:   missing
System product:   missing
AC adapter present:   yes
Battery present:  yes
Laptop panel present: no
CPU scaling present:  no
Battery Information:
  battery.charge_level.current = 34132  (0x8554)  (int)
  battery.charge_level.design = 48840  (0xbec8)  (int)
  battery.charge_level.last_full = 36663  (0x8f37)  (int)
  battery.charge_level.percentage = 93  (0x5d)  (int)
  battery.charge_level.rate = 11255  (0x2bf7)  (int)
  battery.is_rechargeable = true  (bool)
  battery.model = 'Internal Battery'  (string)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = true  (bool)
  battery.rechargeable.is_discharging = false  (bool)
  battery.remaining_time = 809  (0x329)  (int)
  battery.reporting.current = 3075  (0xc03)  (int)
  battery.reporting.design = 4400  (0x1130)  (int)
  battery.reporting.last_full = 3303  (0xce7)  (int)
  battery.reporting.rate = 1014  (0x3f6)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.serial = ''  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.vendor = 'Generic Charger'  (string)
  battery.voltage.current = 12541  (0x30fd)  (int)
  battery.voltage.design = 11100  (0x2b5c)  (int)
  battery.voltage.unit = 'mV'  (string)
DeviceKit data:
/usr/share/gnome-power-manager/gnome-power-bugreport: 80: devkit-power: not 
found
GNOME Power Manager Process Information:
nightolo  3261  0.0  1.5  30812  6864 ?S18:50   0:00  \_ 
gnome-power-manager
HAL Process Information:
102   2130  0.0  0.4   6660  2056 ?Ss   18:49   0:00 /usr/sbin/hald
root  2131  0.0  0.2   3328   932 ?S18:49   0:00  \_ hald-runner
root  2206  0.0  0.2   3392   976 ?S18:49   0:00  \_ 
hald-addon-input: Listening on /dev/input/event0 /dev/input/event5 
/dev/input/event1 /dev/input/event2 /dev/input/event3
root  2241  0.0  0.2   3396   960 ?D18:49   0:00  \_ 
hald-addon-storage: polling /dev/hdc (every 2 sec)
102   2246  0.0  0.2   3244   972 ?S18:49   0:00  \_ 
/usr/lib/hal/hald-addon-acpi

Bug#564529: gnome-power-manager: Lid close event triggered by plugging in AC

[Antonio Radici]

Hi,
I have already posted this in bug #497128 but it seems better described
by this bug, the output of gnome-power-bugreport is attached.

If I change the "When the lid is closed" action to blank screen then
when I connect the PC to teh power adaptor (or disconnect from it) the
action there is executed (even if I'm not touching the lid at all).

Cheers
Antonio
Distro version:   squeeze/sid
Kernel version:   2.6.30-2-686
g-p-m version:2.28.3
HAL version:  0.5.14
System manufacturer:  missing
System version:   missing
System product:   missing
AC adapter present:   yes
Battery present:  yes
Laptop panel present: no
CPU scaling present:  no
Battery Information:
  battery.charge_level.current = 34132  (0x8554)  (int)
  battery.charge_level.design = 48840  (0xbec8)  (int)
  battery.charge_level.last_full = 36663  (0x8f37)  (int)
  battery.charge_level.percentage = 93  (0x5d)  (int)
  battery.charge_level.rate = 11255  (0x2bf7)  (int)
  battery.is_rechargeable = true  (bool)
  battery.model = 'Internal Battery'  (string)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = true  (bool)
  battery.rechargeable.is_discharging = false  (bool)
  battery.remaining_time = 809  (0x329)  (int)
  battery.reporting.current = 3075  (0xc03)  (int)
  battery.reporting.design = 4400  (0x1130)  (int)
  battery.reporting.last_full = 3303  (0xce7)  (int)
  battery.reporting.rate = 1014  (0x3f6)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.serial = ''  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.vendor = 'Generic Charger'  (string)
  battery.voltage.current = 12541  (0x30fd)  (int)
  battery.voltage.design = 11100  (0x2b5c)  (int)
  battery.voltage.unit = 'mV'  (string)
DeviceKit data:
/usr/share/gnome-power-manager/gnome-power-bugreport: 80: devkit-power: not 
found
GNOME Power Manager Process Information:
nightolo  3261  0.0  1.5  30812  6864 ?S18:50   0:00  \_ 
gnome-power-manager
HAL Process Information:
102   2130  0.0  0.4   6660  2056 ?Ss   18:49   0:00 /usr/sbin/hald
root  2131  0.0  0.2   3328   932 ?S18:49   0:00  \_ hald-runner
root  2206  0.0  0.2   3392   976 ?S18:49   0:00  \_ 
hald-addon-input: Listening on /dev/input/event0 /dev/input/event5 
/dev/input/event1 /dev/input/event2 /dev/input/event3
root  2241  0.0  0.2   3396   960 ?D18:49   0:00  \_ 
hald-addon-storage: polling /dev/hdc (every 2 sec)
102   2246  0.0  0.2   3244   972 ?S18:49   0:00  \_ 
/usr/lib/hal/hald-addon-acpi

Bug#569500: Updated patch combining solutions for #572203 and #569500

[Antonio Radici]

On Fri, Apr 02, 2010 at 11:35:55AM -0400, James Vega wrote:
> Since #572203 and #569500 are both results of #528233, I figured I would
> send an updated patch combining the fixes from myself and Philipp.
> 
> Philipp or Antonio, could you forward the patch upstream?

Sure, I will do it this weekend.

It's most likely that I will do an upload for your patch and some other
patches.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626294: segmentation fault at opening imap folder

[Antonio Radici]

tag 626294 +pending
thanks

Hi,
thanks for the patch, this will be included in the next version of mutt
and I will certainly send it upstream.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626294: Updated patch for #626294 and #584138

[Antonio Radici]

On Sat, Jun 08, 2013 at 10:24:21PM +0200, Evgeni Golov wrote:
> On Wed, May 15, 2013 at 12:09:46AM +0000, Antonio Radici wrote:
> > On Mon, May 13, 2013 at 07:11:58PM +0200, Evgeni Golov wrote:
> > > On Sun, Sep 25, 2011 at 05:16:16PM +0200, Nikolaus Schulz wrote:
> > > 
> > > > Attached is an updated version of
> > > > 584138-mx_update_context-segfault.patch that seems to fix the problem.
> > > > Copied from upstream changeset 0e4f1782ea2e.
> > > 
> > > This bug has been hitting me since the update to Wheezy.
> > > The updated patch solves the issue perfectly.
> > > 
> > > Can we please make sure this makes into the first point release?
> > 
> > Yes, sorry for the inconvenience, a new binary for this will be prepared on
> > Sunday evening (May 19th), then I will follow the procedure to get it into
> > stable-proposed-updates.
> 
> Ping?
> 7.1 is planned for next weekend (says #-release) and getting this in 
> would be awesome :)
> 
> Greets
> Evgeni

Hi Evgeni,
unfortunately I missed that deadline and I didn't upload the new version, I'm
really sorry for the inconvenience; I can prepare a version tomorrow and upload
it :(

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#711786: mutt: diff for NMU version 1.5.21-6.3

[Antonio Radici]

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 it longer or
> supersede it with your own upload, etc.
> 

It's OK, thanks a lot for fixing this.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#616131: ITA: lsb -- Linux Standard Base 3.2 support package

[Antonio Radici]

retitle 616131 RFA: lsb -- Linux Standard Base 3.2 support package
noowner 616131
thanks

Sorry for answering this late but unfortunately I don't have time to
maintain this package, it was an oversight to get the ITA, so I'm
setting this back to RFA.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#619216: Fwd: Bug#619246: pu: mutt: diff for NMU version 1.5.20-9+squeeze2

[Antonio Radici]

On Thu, Dec 15, 2011 at 12:11:05PM +0100, Agustin Martin wrote:
> Seems there was a typo in bug number. Re-sending to apparently correct bug

it looks good to me, thanks for taking care of this.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#664636: cfengine3: fails to purge: rmdir: failed to remove `/var/lib/cfengine3': Directory not empty

[Antonio Radici]

tag 664636 +confirmed
thanks

On Mon, Mar 19, 2012 at 02:37:16PM +0100, Andreas Beckmann wrote:
> Package: cfengine3
> Version: 3.2.4-1
> Severity: important
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to purge.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Removing cfengine3 ...
>   Purging configuration files for cfengine3 ...
>   rmdir: failed to remove `/var/lib/cfengine3': Directory not empty
>   dpkg: error processing cfengine3 (--purge):
>subprocess installed post-removal script returned error exit status 1
>   Errors were encountered while processing:
>cfengine3

I noticed the same piuparts error from the webinterface of
packages.qa.debian.org, I'm working on it.

Thanks for reporting this.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#658945: Intent to NMU in the coming weeks

[Antonio Radici]

tag 658945 +confirmed pending
thanks

On Sun, Mar 18, 2012 at 04:22:11PM +, Dominic Hargreaves wrote:
> Dear maintainer,
> 
> As I would like to get all of the Perl4::Corelibs issues sorted out
> before wheezy releases, to ease the transition for perl 5.16 in
> wheezy+1, I intend to file NMUs for these issues, adding the dependency

Hi Dominic,
sorry for the late reply :(

Have you done this already? if not I'm planning to do it anyway tonight.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#579967: Fixes for the German translation of mutt

[Antonio Radici]

On Sat, Feb 04, 2012 at 06:43:28PM +0100, Helge Kreutzmann wrote:
> Hello Antonio,
> On Sun, May 08, 2011 at 09:58:59AM +0200, Helge Kreutzmann wrote:
> > On Thu, May 05, 2011 at 03:42:58PM +0000, Antonio Radici wrote:
> > > can you please verify my notes on #610720 and resubmit an amended .po?
> > 
> > Attached to this file. I resolved the two fuzzy strings.
> > 
> > > Once I will receive it I will submit it to the mutt upstream developers
> > > and upload it in the Debian package.
> 
> Did they accept it?
> 
> Anyway, it would be great if you could upload it to unstable so that
> it can reach Wheezy. If there are any open issues do not hesitate to
> ask of if upstream would like to discuss anything.
> 
> Thanks for maintianing mutt.

Hi Helge,
thanks for your patch, I'll prepare an upload within this week.

Sorry for the delay in getting back to you.

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#654148: Please enabled hardened build flags

[Antonio Radici]

On Fri, Apr 06, 2012 at 06:58:59PM +0200, Antonio Radici wrote:
> Sorry I missed this message; I'll have an upload ready for tomorrow.

I haven't forgotten this message, I'll have the upload ready for this
weekend, sorry for the delay.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#660860: cfengine3: segfaults when triggering some locks

[Antonio Radici]

On Sun, Apr 01, 2012 at 09:16:06PM +0200, Jimmy Thrasibule wrote:
> Hi,
> 
> What is the status of this bug? The given workaround doesn't work for me
> and I had to switch to the testing package.
> 
> We will have a solution to use the stable package?

It seems that there is a patch, I'll try to apply that and send you a
test binary; in the meantime can you please provide us with the
coredump?

Cheers
Antonio



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#654148: Please enabled hardened build flags

[Antonio Radici]

On Fri, Apr 06, 2012 at 06:48:03PM +0200, Moritz Mühlenhoff wrote:
> On Mon, Jan 02, 2012 at 02:59:28AM +0100, Moritz Muehlenhoff wrote:
> > Package: mutt
> > Version: 1.5.21-5
> > Severity: important
> > Tags: patch
> > 
> > Please enabled hardened build flags through dpkg-buildflags.
> > 
> > Patch attached. (dpkg-buildflags abides "noopt" from DEB_BUILD_OPTIONS)
> 
> What's the status? Do you plan an upload in the next weeks or
> shall I upload a NMU?

Sorry I missed this message; I'll have an upload ready for tomorrow.

Cheers
Antonio



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#763522: mutt: diff for NMU version 1.5.23-3.2

[Antonio Radici]

On Tue, Sep 15, 2015 at 12:23:03PM +0200, Matteo F. Vescovi wrote:
> Hi!
> 
> On 2015-09-02 at 10:15 (CEST), Elimar Riesebieter wrote:
> > 1.5.24 has been rolled out. So it seems not to be necessary to patch
> > 1.5.23?
> 
> Working on that right now.
> 
> I hope to get through the messy patchset quite soon and be able to
> upload the new release within this week, or maybe the next one.
> 
> Cheers.

Matteo, is the new release 1.5.24 or are you talking about the NMU?

Bug#763522: mutt: diff for NMU version 1.5.23-3.2

[Antonio Radici]

On Tue, Sep 15, 2015 at 09:17:43PM +0200, Matteo F. Vescovi wrote:
> Hi Antonio!
> 
> On 2015-09-15 at 15:50 (CEST), Antonio Radici wrote:
> > Matteo, is the new release 1.5.24 or are you talking about the NMU?
> 
> The new release 1.5.24; working on it right now.
> 

Thanks a lot!
can you make sure it's in git.debian.org afterwards?

Bug#763522: mutt: diff for NMU version 1.5.23-3.2

[Antonio Radici]

On Wed, Sep 02, 2015 at 12:08:27PM +0200, Elimar Riesebieter wrote:
> On Tue, 1 Sep 2015 09:54:56 +0000 Antonio Radici  wrote:
> > Hi,
> > sorry for the delay but I wasn't in Ireland for a while; do you need a 
> > sponsor
> > for this?
> > 
> > On Sun, Aug 23, 2015 at 03:01:33PM +0200, Ruben Undheim wrote:
> > > 
> > > Dear maintainer,
> > > 
> > > I've prepared an NMU for mutt (versioned as 1.5.23-3.2) and
> > > will soon ask a sponsor to upload it to the DELAYED queue.
> > > Please feel free to tell me if I don't need to do this.
> > > 
> > > Regards.
> 
> 1.5.24 has been rolled out. So it seems not to be necessary to patch
> 1.5.23?

This needs to be patched for the stable releases, I will upload teh NMU today or
tomorrow, sorry for the delay.

Bug#763522: mutt: diff for NMU version 1.5.23-3.2

[Antonio Radici]

On Wed, Sep 16, 2015 at 03:23:29PM +0200, Matteo F. Vescovi wrote:
> Hi!
> 
> On Wed, Sep 16, 2015 at 12:30 PM, Antonio Radici  wrote:
> > can you make sure it's in git.debian.org afterwards?
> 
> Thanks to myon, I have commit powers on mutt's git repository since 1.5.22 ;-)
> 
> I've already started working on it yesterday, fixing few cosmetic issues.
> I've already pushed the import (master, pristine-tar and upstream
> branches) of 1.5.24 and now taking care of getting the patchset apply
> smoothly against this new version.
> I hope to finish that part within the end of the week.
> 
> You'll find everything on git once it's finished.
> 

Thanks a lot Matteo!
I'll take care of the NMU as soon as I get home today

Bug#828263: cfengine3: FTBFS with openssl 1.1.0

[Antonio Radici]

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 version in experimental builds fine with 1.1.0, I'll upload it to unstable
tonight.

Bug#857687: [Pkg-mutt-maintainers] Bug#857687: mutt: Please release NeoMutt 2017-03-06

[Antonio Radici]

tag -1 +pending
thanks

On Mon, Mar 13, 2017 at 10:02:47PM +, Ivan Vucica wrote:
> Package: mutt
> Version: 1.7.2-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> Please release NeoMutt 2017-03-06 (Mutt 1.8.0 plus a few more fixes).
> 
> I strongly care about "Increase ACCOUNT.pass field size. (closes #3921)"; 
> right
> now, the password field is too short to pass through the Google OAuth2 access
> token into the libsasl2 xoauth2 authentication method.
> 
> Thanks!

I've already discussed with the NeoMutt maintainer, I was planning to release a
couple of days ago but a travel changed my plan. I'm planning to do it today.

Bug#763522: [Pkg-mutt-maintainers] Bug#763522: Bug#836254: Bug#836254: mutt: crashes when selecting private pgp key

[Antonio Radici]

On Wed, Mar 15, 2017 at 09:57:14PM +0100, Bernhard Schmidt wrote:
> On Thu, Sep 01, 2016 at 07:06:10AM +0000, Antonio Radici wrote:
> 
> Hi Antonio.
> 
> > Hi Hilmar,
> > first of all thanks for your bug report!
> > From the Debian Developer Reference [1] I see that:
> > ===
> > Basically, a package should only be uploaded to stable if one of the 
> > following
> > happens:
> > 
> > * a truly critical functionality problem
> > 
> > * the package becomes uninstallable
> > 
> > * a released architecture lacks the package
> > ===
> > 
> > One could argue that this is a functionality problem, I can try to open the 
> > bug
> > to the release team and see what they think, I'll include the patch too and 
> > a
> > brief description, I'll add the bug here as soon as it is open (hopefully 
> > this
> > evening at the latest)
> 
> I have been recently hit by this. In my experience this patch would be
> perfectly fine for a Jessie point release. I haven't seen anything
> regarding a mutt stable update, have I missed anything?
> 
> I have prepared a stable update on top of the jessie-updates git branch
> and verified that it fixes this problem (see attached git patch)
> 
> If you agree, but don't have time to discuss this with the release-team
> I'm willing to do this on your behalf.
> 
> Bernhard

Hi Bernhard,
the patch looks fine to me. if the bug is bumped to grave (and there are reasons
to do so); I have done point updates in the past and it is straightforward, if
you have already opened the bug / done the upload then OK, otherwise I can do
either of the two (for example if they are OK with teh bug I can do the upload
with your commit).

Bug#825821: ITP: neomutt -- NeoMutt is a place to gather all the patches against Mutt.

[Antonio Radici]

On Mon, May 30, 2016 at 09:11:57PM +0200, Evgeni Golov wrote:
> Hi,
> 
> > > On Mon, 2016-05-30 at 13:00 +0200, Elimar Riesebieter wrote:
> > > > * Package name: neomutt
> 
> Please don't. We don't need another mutt fork in Debian.
> 
> > > Did you talk to the current mutt maintainers about this?
> > > 
> > > The changelog for the mutt 1.6.1-1 upload to experimental includes:
> [ lots of patches taken from neomutt ]
> 
> The current plan is to replace Debian's mutt-patched patchset with neomutt. 
> [1]
> Maybe even s/mutt/neomutt/ at some point.

As mutt maintainer I second every word that Evgeni has already said, we are
already working with the neomutt maintainer and there is activity, I don't
believe there we are adding much with another mutt fork/additional package.

Additionally I'm not sure why debian-devel@ was added to this bug.

Cheers
Antonio

Bug#771674: mutt: spurious comma in From header

[Antonio Radici]

On Tue, Dec 02, 2014 at 07:05:14PM +0100, Salvatore Bonaccorso wrote:
> Hi all,
> 
> (disclaimer, not the maintainer here, just proposing a possible
> debdiff).
> 

I think this is what we should do, I'll apply the patch tonight.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#772074: unblock: mutt/1.5.23-3

[Antonio Radici]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mutt

This version includes a better patch for the mutt CVE which does not compromise
the functionality of mutt.

debdiff attached

unblock mutt/1.5.23-3

-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru mutt-1.5.23/debian/changelog mutt-1.5.23/debian/changelog
--- mutt-1.5.23/debian/changelog	2014-11-29 18:40:59.0 +
+++ mutt-1.5.23/debian/changelog	2014-12-04 21:11:02.0 +
@@ -1,3 +1,11 @@
+mutt (1.5.23-3) unstable; urgency=medium
+
+  * Fixed upstream/771125-CVE-2014-9116-jessie.patch thanks to Salvatore
+Bonaccorso; now it correctly fixes the CVE and does not affect other
+   functionalities of mutt (Closes: 771674)
+
+ -- Antonio Radici   Thu, 04 Dec 2014 21:09:07 +
+
 mutt (1.5.23-2) unstable; urgency=medium
 
   * Created upstream/771125-CVE-2014-9116-jessie.patch to address
diff -Nru mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch
--- mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch	2014-11-29 18:40:59.0 +
+++ mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch	2014-12-04 21:11:02.0 +
@@ -10,10 +10,12 @@
 The wheezy version of this patch is slightly different, therefore this patch
 has -jessie prefixed in its name.
 
-Index: mutt/lib.c
-===
 mutt.orig/lib.c
-+++ mutt/lib.c
+The sendlib.c part was provided by Salvatore Bonaccorso and it is the same as
+the upstream patch reported here:
+http://dev.mutt.org/trac/attachment/ticket/3716/ticket-3716-stable.patch
+
+--- a/lib.c
 b/lib.c
 @@ -815,6 +815,9 @@ char *mutt_substrdup (const char *begin,
size_t len;
char *p;
@@ -24,16 +26,19 @@
if (end)
  len = end - begin;
else
-Index: mutt/lib.h
-===
 mutt.orig/lib.h
-+++ mutt/lib.h
-@@ -98,7 +98,7 @@
-on some systems */
- # define SKIPWS(c) while (*(c) && isspace ((unsigned char) *(c))) c++;
- 
--#define EMAIL_WSP " \t\r\n"
-+#define EMAIL_WSP " \t\r"
- 
- /* skip over WSP as defined by RFC5322.  This is used primarily for parsing
-  * header fields. */
+--- a/sendlib.c
 b/sendlib.c
+@@ -1814,7 +1814,12 @@ static int write_one_header (FILE *fp, i
+ {
+   tagbuf = mutt_substrdup (start, t);
+   /* skip over the colon separating the header field name and value */
+-  t = skip_email_wsp(t + 1);
++  ++t;
++
++  /* skip over any leading whitespace (WSP, as defined in RFC5322) */
++  while (*t == ' ' || *t == '\t')
++t++;
++
+   valbuf = mutt_substrdup (t, end);
+ }
+ dprint(4,(debugfile,"mwoh: buf[%s%s] too long, "

Bug#763522: mutt: SEGV when choosing pgp keyID from list (mutt/mutt-patched)

[Antonio Radici]

On Mon, Apr 27, 2015 at 09:14:51AM -0700, Kevin J. McCarthy wrote:
> I'm not a good judge of what is an RC bug, but this patch would be
> *really* nice to have in Jessie+1.  It's a very low risk patch and stops
> an easy to hit segfault.
> 
> -Kevin

I think it makes sense, I will rebuild mutt this weekend and try to apply for an
exception.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#763522: mutt: diff for NMU version 1.5.23-3.2

[Antonio Radici]

Hi,
sorry for the delay but I wasn't in Ireland for a while; do you need a sponsor
for this?

On Sun, Aug 23, 2015 at 03:01:33PM +0200, Ruben Undheim wrote:
> 
> Dear maintainer,
> 
> I've prepared an NMU for mutt (versioned as 1.5.23-3.2) and
> will soon ask a sponsor to upload it to the DELAYED queue.
> Please feel free to tell me if I don't need to do this.
> 
> Regards.

> diff -Nru mutt-1.5.23/debian/changelog mutt-1.5.23/debian/changelog
> --- mutt-1.5.23/debian/changelog  2015-08-01 13:57:01.0 +0200
> +++ mutt-1.5.23/debian/changelog  2015-08-23 09:54:19.0 +0200
> @@ -1,3 +1,11 @@
> +mutt (1.5.23-3.2) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/patches/upstream/763522-fix-segv-gpg.patch:
> +- Fixes SEGV when choosing key (Closes: #763522)
> +
> + -- Ruben Undheim   Sun, 23 Aug 2015 09:48:27 +0200
> +
>  mutt (1.5.23-3.1) unstable; urgency=low
>  
>* Non-maintainer upload.
> diff -Nru mutt-1.5.23/debian/patches/series mutt-1.5.23/debian/patches/series
> --- mutt-1.5.23/debian/patches/series 2015-08-01 13:47:26.0 +0200
> +++ mutt-1.5.23/debian/patches/series 2015-08-23 09:53:49.0 +0200
> @@ -36,6 +36,7 @@
>  translations/update_german_translation.patch
>  upstream/771125-CVE-2014-9116-jessie.patch
>  upstream/624058-gnutls-deprecated.patch
> +upstream/763522-fix-segv-gpg.patch
>  __separator__mutt.org.patch
>  mutt-patched/sidebar.patch
>  mutt-patched/sidebar-dotpathsep.patch
> diff -Nru mutt-1.5.23/debian/patches/upstream/763522-fix-segv-gpg.patch 
> mutt-1.5.23/debian/patches/upstream/763522-fix-segv-gpg.patch
> --- mutt-1.5.23/debian/patches/upstream/763522-fix-segv-gpg.patch 
> 1970-01-01 01:00:00.0 +0100
> +++ mutt-1.5.23/debian/patches/upstream/763522-fix-segv-gpg.patch 
> 2015-08-23 09:48:21.0 +0200
> @@ -0,0 +1,24 @@
> +Description: This fixes a SEGV when choosing pgp keyID from list
> +Author: Ruben Undheim 
> +Origin: http://dev.mutt.org/hg/mutt/rev/5a86319adad0
> +
> +Index: mutt-1.5.23/pgpkey.c
> +===
> +--- mutt-1.5.23.orig/pgpkey.c2014-03-12 16:03:44.0 +
>  mutt-1.5.23/pgpkey.c 2015-08-23 07:10:41.445078707 +
> +@@ -985,13 +985,13 @@
> +   pgp_remove_key (&matches, k);
> + 
> + pgp_free_key (&matches);
> +-if (!p[l-1])
> ++if (l && !p[l-1])
> +   p[l-1] = '!';
> + return k;
> +   }
> + 
> + out:
> +-  if (!p[l-1])
> ++  if (l && !p[l-1])
> + p[l-1] = '!';
> +   return NULL;
> + }

Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP

[Antonio Radici]

On Tue, Dec 01, 2015 at 02:31:41PM +0100, Marco Balmer wrote:
> Hi,
> 
> I can confirm exactly described behaviour in my mutt environment.
> 
> $ dpkg -l mutt
> ii  mutt   1.5.23-3 amd64
> 
> $ mutt -d 5
> [2015-12-01 14:03:00] 5< a0064 OK Fetch completed.
> [2015-12-01 14:03:00] IMAP queue drained
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] WEED is Not
> [2015-12-01 14:03:00] IMAP queue drained
> >> HERE IT HANGS <

can we get a stacktrace through gdb?

Cheers
Antonio

Bug#722322: mutt hangs occassionally while fetching (big) message via IMAP

[Antonio Radici]

On Wed, Dec 02, 2015 at 02:12:30PM +0100, Marco Balmer wrote:
> 
> Special in this part, the e-mail was only 3KiB. But I think it is the same 
> case.
> I can reproduce it every time.
> Let me know, if necessary, how I can help.

Can you reproduce always with the same mail? Or do you need a big mailbox to
reproduce it? does it always happen at the same email?

Cheers
Antonio

Bug#763522: mutt: diff for NMU version 1.5.23-3.2

[Antonio Radici]

On Mon, Oct 19, 2015 at 07:55:52AM +, Matteo F. Vescovi wrote:
> Hi Antonio!
> 
> On Wed, Sep 16, 2015 at 3:42 PM Antonio Radici  wrote:
> 
> > Thanks a lot Matteo!
> > I'll take care of the NMU as soon as I get home today
> >
> 
> I see no update of the stable package wrt this issue.
> Do you still manage to provide it in the next days or should I talke care
> of it?
> Let me know.
> 

Sorry, I'm currently out of Ireland for another 7 days, if it's urgent you can
take care of it otherwise I'll do it as soon as I get home.

Bug#766873: release.debian.org: Please unblock cfengine3

[Antonio Radici]

reopen 766873
retitle 766873 Please unblock cfengine 3.6.2-4
thanks

Reopening this bug, it seems that the package didn't make the freeze, despite
that the fact that the calculation in the previous correspondence seems to be
correct; can you please unblock it?

Thanks!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#766873: Processed: Re: Bug#766873: release.debian.org: Please unblock cfengine3

[Antonio Radici]

close 766873
thanks

Nevermind, it's in testing already, it seems that today I'm unable to read the
content of packages.debian.org.

On Thu, Nov 06, 2014 at 10:09:15AM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > reopen 766873
> Bug #766873 {Done: Antonio Radici } [release.debian.org] 
> release.debian.org: Please reduce age for cfengine3
> Bug reopened
> Ignoring request to alter fixed versions of bug #766873 to the same values 
> previously set
> > retitle 766873 Please unblock cfengine 3.6.2-4
> Bug #766873 [release.debian.org] release.debian.org: Please reduce age for 
> cfengine3
> Changed Bug title to 'Please unblock cfengine 3.6.2-4' from 
> 'release.debian.org: Please reduce age for cfengine3'
> > thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
> -- 
> 766873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766873
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#766798: mutt spam detection fails when header_cache is enabled

[Antonio Radici]

On Sat, Oct 25, 2014 at 02:57:20PM -0700, Matt Rechkemmer wrote:
> Package: mutt
> Version: 1.5.21-6.2+deb7u2
> Severity: normal
> 
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
> 
>* What led up to the situation? I was attempting to use mutt's spam
>detection to mass delete spam messages in mutt.  When header cache is
>enabled, spam headers are never identified and tagged within mutt.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)? I tested against mutt.org's version of mutt.  In that
>  version, mutt works as expected.  When I use the stable version in
>  wheezy, the spam detection fails.
>* What was the outcome of this action? Spam headers are properly identified
>and tagged.
>* What outcome did you expect instead? Using Debian's version, mutt's spam
>detection mechanism fails when header cache (set header_cache) is enabled.

Hi Matt,
can you also provide a mutt -v output of the mutt.org package that you compiled
yourself and where the spam detection works fine?

thanks!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#766873: release.debian.org: Please reduce age for cfengine3

[Antonio Radici]

Package: release.debian.org
Severity: normal
Usertags: unblock

Hi,
I recently packages the latest version of cfengine3 (3.6.2) and I uploaded it in
time before freeze (more than 10 days), unfortunately this version did not build
on sparc and kfreebsd so I spent the past two days on porterboxes trying to get
it to build.

The latest version (3.6.2-4) is building everywhere and it will be really great
if you could reduce its age to 6 days so that we can have it in Jessie, since
the existing version is quite old.

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#766873: release.debian.org: Please reduce age for cfengine3

[Antonio Radici]

On Sun, Oct 26, 2014 at 08:07:45PM +, Steven Chamberlain wrote:
> Hi,
> 
> Antonio Radici wrote:
> > The latest version (3.6.2-4) is building everywhere and it will be really 
> > great
> > if you could reduce its age to 6 days so that we can have it in Jessie, 
> > since
> > the existing version is quite old.
> 
> I think this will already migrate in time for the freeze?
> 
> The freeze is at 23:59 UTC on 2014-11-05, which is 10 days from now.

Perfect then, I'll close the bug!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#814658: mutt wrongly complains about Unmatched ( or \( in hook regular explession

[Antonio Radici]

On Sat, Feb 13, 2016 at 07:45:02PM +0100, Christian Böhme wrote:
> Writing a configuration file (/the/config/file) containing
> 
> send-hook  '~t (ab|cd)$''set my_var = xyz'
> 
> at line 123.
> 
>* What was the outcome of this action?
> 
> Upon startup, mutt complains
> 
> Error in /the/config/file, line 123: '(ab': Unmatched ( or \(
> 
>* What outcome did you expect instead?
> 
> Mutt starting up and properly compiling the regular expression.

>From the mutt manual available here:
http://www.mutt.org/doc/manual/manual-4.html#regexp

"""
Note that if a regular expression contains parenthesis, or a veritical bar 
("|"), you must enclose the expression in double or single quotes since those 
characters are also used to separate different parts of Mutt's pattern 
language. For example,

~f "me@(mutt\.org|cs\.hmc\.edu)"

Without the quotes, the parenthesis would truncate the regular expression to 
simply me@, which is probably not what you want.
"""

I'm closing this bug as wontfix because this is not a bug.

Cheers
Antonio

Bug#695263: mutt: segfault on synchronizing imap mailbox after joining threads

[Antonio Radici]

tag 695263 +moreinfo
thanks

On Thu, Dec 06, 2012 at 12:29:57PM +0200, Eugene V. Lyubimkin wrote:
> Package: mutt
> Version: 1.5.21-6.2
> Severity: normal
> 
> Hello,
> 
> Here is what I did:
> 
> 1) Opened IMAP mailbox.
> 2) Joined two threads (with one message in each of them and different
> subjects) by pressing 't' on one message and then '&' on another.
> 3) Synced the mailbox by pressing '$'. Mutt segfaulted shortly after
> printing 'Sorting mailbox'.

Hi Eugene,
this does not seem reproducible anymore on 1.5.24-1, could you please check if
that's still the case?

Bug#695263: mutt: segfault on synchronizing imap mailbox after joining threads

[Antonio Radici]

Ok thanks, closing as agreed.

Bug#695220: mutt -H should modify the draft , not create a copy

[Antonio Radici]

tag 695220 +pending
thanks

The upstream patch was added in commit 1d7c7740987a77eb3281a260b5decc73cb96dff5.

This will be shipped with the next version of mutt in Debian.

Bug#741213: mutt: pgpring displays an incorrect length for DSA and Elgamal keys

[Antonio Radici]

tag 741213 +pending
thanks

On Mon, Mar 10, 2014 at 01:25:10AM +0100, Guilhem Moulin wrote:
> Dear Maintainer,
> 
> As signing-party's pgpring, Mutt's does not look at the right field as
> key lengh for DSA and Elgamal keys, which results to an incorrect
> output similar to that reported in #602284.  The attached patch, adapted 
> from Fabrizio Tarizzo's, fixes the issue; see
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602284
> 
> for details.

Thanks for the patch, I'll report this bug upstream this evening if it's not
already fixed there.
In any case this will be fixed with the next Debian release of mutt.

Cheers
Antonio

Bug#678596: mutt: Why mutt.desktop:NoDisplay=true ? No gnome-shell menu...

[Antonio Radici]

tag 678596 +pending
thanks

On Sat, Jun 23, 2012 at 10:08:11AM +0900, Osamu Aoki wrote:
> Anyway, there is no reason for mutt to set NoDisplay=true by the file
> provided by the packaging at /debian/extra/mutt.desktop
> 
> As the same reason as discussed for evince below, we should not use
> this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427576
> 
> Please drop this NoDisplay=true line.

It makes sense to set it to true, this will be shipped starting from mutt
1.5.24-2.

Bug#803405: does not properly restore console colors on exit anymore

[Antonio Radici]

tag 803405 +pending
thanks

On Thu, Oct 29, 2015 at 01:57:20PM -0400, Joey Hess wrote:
> Package: mutt
> Version: 1.5.24-1
> Severity: normal
> 
> Before upgrading to mutt 1.5.24, I could run mutt, press 'q' and 
> the shell prompt was the same color as it was before mutt ran.
> Now, after quitting mutt, the color setting is apparently left at
> light grey on black. I have to run `reset` to fix it.

I also noticed this and it is very annoying, I'll have it fixed in the next
version.

Bug#694992: mutt: hangs indefinitely with "No authenticators available" if smtp_authenticators = 'gssapi' and fails

[Antonio Radici]

tag 694992 +moreinfo
thanks

On Mon, Dec 03, 2012 at 03:07:49AM +, Tom Jones wrote:
> Package: mutt
> Version: 1.5.21-6.2
> Severity: important
> 
> Dear Maintainer,
> 
> I have:
> 
> set smtp_authenticators = 'gssapi'

Hi Christian && Tom,
do you have a way to reproduce this for me? Christian in particular confirmed
that this bug is still happening in 1.5.24-1, which is particularly worrying.

Unfortunately I don't use gssapi anywhere so I can't reproduce this problem, can
you suggest me a way to do so?

Cheers
Antonio

Bug#815414: git-buildpackage incorrectly drop "Gbp-Pq: Topic " strings

[Antonio Radici]

Package: git-buildpackage
Version: 0.7.2
Severity: important

This problem compromises our ability to use git-buildpackage to manage quilt
patches.

It seems that "gbp pq export" incorrectly drops the "Gbp-Pq: Topic" strings that
are set in the patches.

Additionally if a new patch is created and it contains
"Gbp-Pq: Topic misc" in the commit message, then the new patch is not placed on
the misc directory.
Let me know if you want me to file another bug for this second problem.

To reproduce:

git clone git://anonscm.debian.org/pkg-mutt/mutt.git
gbp pq import
git checkout master
gbp pq export
git status

Cheers
Antonio

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-buildpackage depends on:
ii  devscripts2.15.10
ii  git   1:2.7.0-1
ii  man-db2.7.5-1
ii  python-dateutil   2.4.2-1
ii  python-pkg-resources  18.8-1
ii  python-six1.10.0-2
pn  python:any

Versions of packages git-buildpackage recommends:
ii  pbuilder 0.223
ii  pristine-tar 1.33
ii  python-requests  2.9.1-2

Versions of packages git-buildpackage suggests:
pn  python-notify  
ii  sudo   1.8.15-1.1
ii  unzip  6.0-20

-- no debconf information

Bug#545814: Mutt count strlen in bytes != symbols

[Antonio Radici]

forwarded 545814 http://bugs.mutt.org/3807
severity 545814 wishlist
tag 545814 -pending
thanks

On Wed, Sep 09, 2009 at 02:48:32PM +0400, Dmitry E. Oboukhov wrote:
> Package: mutt
> Version 1.5.20-2
> Tags: l10n
> 
> Now I've attached at LDAP-address-book and added instruction
> set query_command = "lbdbq '%s'"
> 
> It works fine only if address name contains only latin1 symbols.
[...]

Hi Dmitry,
I had another run at this but it seems a bit tricky to patch, snprintf can
handle wide characters but I believe that some other things are done in the
caller of query_format_str.

I've reported it upstream as an enhancement, I'll change the severity of this
bug to wishlist accordingly, I'll have another look at it next week, I might be
able to patch it.

Bug#434235: mutt -H ignores Content-Type:

[Antonio Radici]

tag 434235 +pending
thanks

On Thu, Mar 03, 2016 at 03:14:54PM -0800, Kevin J. McCarthy wrote:
> FYI.  This is fixed upstream in https://dev.mutt.org/hg/mutt/rev/a4d885bb36ab

Thanks Kevin, we have the patch ready to ship for 1.5.24-2

Bug#771125: CVE request: mutt: heap-based buffer overflow in mutt_substrdup()

[Antonio Radici]

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 reporting it.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771125: please review mutt-1.5.21-6.2+deb7u3

[Antonio Radici]

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 if you need anything else.

Cheers
Antonio


signature.asc
Description: Digital signature

Bug#771125: please review mutt-1.5.21-6.2+deb7u3

[Antonio Radici]

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://bugs.debian.org/771125
> CVE: CVE-2014-9116
> 
> Debdiff of the *dsc against the current version in stable is attached; let me
> know if you need anything else.
> 
> Cheers
> Antonio


diff -u mutt-1.5.21/debian/changelog mutt-1.5.21/debian/changelog
--- mutt-1.5.21/debian/changelog
+++ mutt-1.5.21/debian/changelog
@@ -1,3 +1,10 @@
+mutt (1.5.21-6.2+deb7u3) wheezy-security; urgency=high
+
+  * Fix buffer overflow caused by an incorrect parsing of whitespace
+characters; also address CVE-2014-0467 (Closes: 771125)
+
+ -- Antonio Radici   Thu, 27 Nov 2014 21:10:23 +
+
 mutt (1.5.21-6.2+deb7u2) wheezy-security; urgency=high
 
   * Non-maintainer upload.
diff -u mutt-1.5.21/debian/patches/series mutt-1.5.21/debian/patches/series
--- mutt-1.5.21/debian/patches/series
+++ mutt-1.5.21/debian/patches/series
@@ -54,6 +54,7 @@
 upstream/611410-no-implicit_autoview-for-text-html.patch
 upstream/path_max
 upstream/CVE-2014-0467.patch
+upstream/771125-CVE-2014-9116.patch
 
 misc/579967-fixes-german-translation.patch
 
only in patch2:
unchanged:
--- mutt-1.5.21.orig/debian/patches/upstream/771125-CVE-2014-9116.patch
+++ mutt-1.5.21/debian/patches/upstream/771125-CVE-2014-9116.patch
@@ -0,0 +1,40 @@
+This patches solves the issue raised by CVE-2014-9116 in bug 771125.
+The sendlib patch is incorporated from upstream commit:
+http://dev.mutt.org/trac/changeset/897dcc62e4aa
+
+The lib.c part was written by Antonio Radici  to prevent
+crashes due to this kind of bugs from happening again.
+
+Index: mutt/sendlib.c
+===
+--- mutt.orig/sendlib.c
 mutt/sendlib.c
+@@ -1815,6 +1815,11 @@ static int write_one_header (FILE *fp, i
+   tagbuf = mutt_substrdup (start, t);
+   ++t; /* skip over the colon separating the header field name and value */
+   SKIPWS(t); /* skip over any leading whitespace */
++
++  /* skip over any leading whitespace (WSP, as defined in RFC5322) */
++  while (*t == ' ' || *t == '\t')
++t++;
++
+   valbuf = mutt_substrdup (t, end);
+ }
+ dprint(4,(debugfile,"mwoh: buf[%s%s] too long, "
+
+:xa
+ls
+Index: mutt/lib.c
+===
+--- mutt.orig/lib.c
 mutt/lib.c
+@@ -814,6 +814,9 @@ char *mutt_substrdup (const char *begin,
+   size_t len;
+   char *p;
+
++  if (end < begin)
++return NULL;
++
+   if (end)
+ len = end - begin;
+   else


signature.asc
Description: Digital signature

Bug#771125: please review mutt-1.5.21-6.2+deb7u3

[Antonio Radici]

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 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://bugs.debian.org/771125
> > CVE: CVE-2014-9116
> > 
> > Debdiff of the *dsc against the current version in stable is attached; let 
> > me
> > know if you need anything else.
> > 
> > Cheers
> > Antonio
diff -u mutt-1.5.21/debian/changelog mutt-1.5.21/debian/changelog
--- mutt-1.5.21/debian/changelog
+++ mutt-1.5.21/debian/changelog
@@ -1,3 +1,10 @@
+mutt (1.5.21-6.2+deb7u3) wheezy-security; urgency=high
+
+  * Fix buffer overflow caused by an incorrect parsing of whitespace
+characters; also address CVE-2014-0467 (Closes: 771125)
+
+ -- Antonio Radici   Thu, 27 Nov 2014 21:10:23 +
+
 mutt (1.5.21-6.2+deb7u2) wheezy-security; urgency=high
 
   * Non-maintainer upload.
diff -u mutt-1.5.21/debian/patches/series mutt-1.5.21/debian/patches/series
--- mutt-1.5.21/debian/patches/series
+++ mutt-1.5.21/debian/patches/series
@@ -54,6 +54,7 @@
 upstream/611410-no-implicit_autoview-for-text-html.patch
 upstream/path_max
 upstream/CVE-2014-0467.patch
+upstream/771125-CVE-2014-9116.patch
 
 misc/579967-fixes-german-translation.patch
 
only in patch2:
unchanged:
--- mutt-1.5.21.orig/debian/patches/upstream/771125-CVE-2014-9116.patch
+++ mutt-1.5.21/debian/patches/upstream/771125-CVE-2014-9116.patch
@@ -0,0 +1,38 @@
+This patches solves the issue raised by CVE-2014-9116 in bug 771125.
+The sendlib patch is incorporated from upstream commit:
+http://dev.mutt.org/trac/changeset/897dcc62e4aa
+
+The lib.c part was written by Antonio Radici  to prevent
+crashes due to this kind of bugs from happening again.
+
+Index: mutt/sendlib.c
+===
+--- mutt.orig/sendlib.c
 mutt/sendlib.c
+@@ -1815,6 +1815,11 @@ static int write_one_header (FILE *fp, i
+   tagbuf = mutt_substrdup (start, t);
+   ++t; /* skip over the colon separating the header field name and value 
*/
+   SKIPWS(t); /* skip over any leading whitespace */
++
++  /* skip over any leading whitespace (WSP, as defined in RFC5322) */
++  while (*t == ' ' || *t == '\t')
++t++;
++
+   valbuf = mutt_substrdup (t, end);
+ }
+ dprint(4,(debugfile,"mwoh: buf[%s%s] too long, "
+
+Index: mutt/lib.c
+===
+--- mutt.orig/lib.c
 mutt/lib.c
+@@ -814,6 +814,9 @@ char *mutt_substrdup (const char *begin,
+   size_t len;
+   char *p;
+
++  if (end < begin)
++return NULL;
++
+   if (end)
+ len = end - begin;
+   else


signature.asc
Description: Digital signature

Bug#771125: notfound mutt/1.5.23-1.1

[Antonio Radici]

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-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771125: please review mutt-1.5.21-6.2+deb7u3

[Antonio Radici]

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 == NULL, which is handled later in the function; if that case
is not used instead, then mutt will segfault frequently.

I expect this to be the last and final debdiff; please disregard the two
previous ones.
diff -u mutt-1.5.21/debian/changelog mutt-1.5.21/debian/changelog
--- mutt-1.5.21/debian/changelog
+++ mutt-1.5.21/debian/changelog
@@ -1,3 +1,10 @@
+mutt (1.5.21-6.2+deb7u3) wheezy-security; urgency=high
+
+  * Fix buffer overflow caused by an incorrect parsing of whitespace
+characters; also address CVE-2014-0467 (Closes: 771125)
+
+ -- Antonio Radici   Thu, 27 Nov 2014 21:10:23 +
+
 mutt (1.5.21-6.2+deb7u2) wheezy-security; urgency=high
 
   * Non-maintainer upload.
diff -u mutt-1.5.21/debian/patches/series mutt-1.5.21/debian/patches/series
--- mutt-1.5.21/debian/patches/series
+++ mutt-1.5.21/debian/patches/series
@@ -54,6 +54,7 @@
 upstream/611410-no-implicit_autoview-for-text-html.patch
 upstream/path_max
 upstream/CVE-2014-0467.patch
+upstream/771125-CVE-2014-9116.patch
 
 misc/579967-fixes-german-translation.patch
 
only in patch2:
unchanged:
--- mutt-1.5.21.orig/debian/patches/upstream/771125-CVE-2014-9116.patch
+++ mutt-1.5.21/debian/patches/upstream/771125-CVE-2014-9116.patch
@@ -0,0 +1,37 @@
+This patches solves the issue raised by CVE-2014-9116 in bug 771125.
+The sendlib patch is incorporated from upstream commit:
+http://dev.mutt.org/trac/changeset/897dcc62e4aa
+
+The lib.c part was written by Antonio Radici  to prevent
+crashes due to this kind of bugs from happening again.
+
+Index: mutt/sendlib.c
+===
+--- mutt.orig/sendlib.c
 mutt/sendlib.c
+@@ -1815,6 +1815,11 @@ static int write_one_header (FILE *fp, i
+   tagbuf = mutt_substrdup (start, t);
+   ++t; /* skip over the colon separating the header field name and value */
+   SKIPWS(t); /* skip over any leading whitespace */
++
++  /* skip over any leading whitespace (WSP, as defined in RFC5322) */
++  while (*t == ' ' || *t == '\t')
++t++;
++
+   valbuf = mutt_substrdup (t, end);
+ }
+ dprint(4,(debugfile,"mwoh: buf[%s%s] too long, "
+Index: mutt/lib.c
+===
+--- mutt.orig/lib.c
 mutt/lib.c
+@@ -814,6 +814,9 @@ char *mutt_substrdup (const char *begin,
+   size_t len;
+   char *p;
+ 
++  if (end != NULL && end < begin)
++return NULL;
++
+   if (end)
+ len = end - begin;
+   else


signature.asc
Description: Digital signature

Bug#771125: notfound mutt/1.5.23-1.1

[Antonio Radici]

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 in
> > unstable/testing.
> 
> It should, the reproducer works here for me, have you 'set weed=no'
> set?
> 
> It is the same issue also still in unstable. Upstrem originally
> addressed the fix in http://dev.mutt.org/trac/changeset/897dcc62e4aa
> but then with the introduction of skip_email_wsp() the problem
> reappers, as newlines are skipped again:
> 
> http://dev.mutt.org/trac/changeset/f251d523ca5a
> 
> EMAIL_WSP is '\t\r\n' there.

Yes, it seems correct; in this case, apart from backporting the lib.c fix that
you saw already, I think that the correct course of action is to remove the
newlien form EMAIL_WSP, as newlines are not defined as whitespace characters in
the RFC; does that sound ok to you?

Cheers
Antonio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771595: unblock: mutt/1.5.23-2

[Antonio Radici]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mutt

This version addessses DSA-3083 and CVE2014-9116.
Tracking bug: 771125

Debdiff against 1.5.23-1.1 attached

unblock mutt/1.5.23-2

-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru mutt-1.5.23/debian/changelog mutt-1.5.23/debian/changelog
--- mutt-1.5.23/debian/changelog	2014-08-17 12:43:01.0 +0100
+++ mutt-1.5.23/debian/changelog	2014-11-29 18:40:59.0 +
@@ -1,3 +1,11 @@
+mutt (1.5.23-2) unstable; urgency=medium
+
+  * Created upstream/771125-CVE-2014-9116-jessie.patch to address
+CVE-2014-9116; the patch prevent mutt_substrdup from being used in a way
+that can lead to a segfault.
+
+ -- Antonio Radici   Sat, 29 Nov 2014 18:13:56 +
+
 mutt (1.5.23-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mutt-1.5.23/debian/patches/series mutt-1.5.23/debian/patches/series
--- mutt-1.5.23/debian/patches/series	2014-03-16 15:06:06.0 +
+++ mutt-1.5.23/debian/patches/series	2014-11-29 18:40:59.0 +
@@ -34,6 +34,7 @@
 upstream/611410-no-implicit_autoview-for-text-html.patch
 upstream/path_max.patch
 translations/update_german_translation.patch
+upstream/771125-CVE-2014-9116-jessie.patch
 __separator__mutt.org.patch
 mutt-patched/sidebar.patch
 mutt-patched/sidebar-dotpathsep.patch
diff -Nru mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch
--- mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch	1970-01-01 01:00:00.0 +0100
+++ mutt-1.5.23/debian/patches/upstream/771125-CVE-2014-9116-jessie.patch	2014-11-29 18:40:59.0 +
@@ -0,0 +1,39 @@
+This patch solves the issue raised by CVE-2014-9116 in bug 771125.
+
+We correctly redefine what are the whitespace characters as per RFC5322; by
+doing so we prevent mutt_substrdup from being used in a way that could lead to
+a segfault.
+
+The lib.c part was written by Antonio Radici  to prevent
+crashes due to this kind of bugs from happening again.
+
+The wheezy version of this patch is slightly different, therefore this patch
+has -jessie prefixed in its name.
+
+Index: mutt/lib.c
+===
+--- mutt.orig/lib.c
 mutt/lib.c
+@@ -815,6 +815,9 @@ char *mutt_substrdup (const char *begin,
+   size_t len;
+   char *p;
+ 
++  if (end != NULL && end < begin)
++return NULL;
++
+   if (end)
+ len = end - begin;
+   else
+Index: mutt/lib.h
+===
+--- mutt.orig/lib.h
 mutt/lib.h
+@@ -98,7 +98,7 @@
+on some systems */
+ # define SKIPWS(c) while (*(c) && isspace ((unsigned char) *(c))) c++;
+ 
+-#define EMAIL_WSP " \t\r\n"
++#define EMAIL_WSP " \t\r"
+ 
+ /* skip over WSP as defined by RFC5322.  This is used primarily for parsing
+  * header fields. */

Bug#864024: mutt: Please update to Mutt 1.8.3, NeoMutt 2017-06-02

[Antonio Radici]

On Sat, Jun 03, 2017 at 01:19:41PM +0200, Julian Andres Klode wrote:
> Package: mutt
> Version: 1.8.0-1
> Severity: wishlist
> 
> A new neomutt is out, featuring a fix for a mildly annoying bug in nntp 
> support:
> 
> "Do not try to create Maildir if it is an NNTP URI"
> 
> (it always asks to create news:// directories at start because they don't
>  exist...)
> 
> Please update (the 1.8.0 does not enter stretch anyway, so updating unstable
> is fine).

I'm going to update by the end of this week, there were some discussion about
switching the source package and I think we came up to a conclusion

Bug#837584: mutt: crash while navigating through inbox

[Antonio Radici]

On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote:
> Package: mutt
> Version: 1.7.0-3
> Severity: normal
> 
> Since the last update, I repeatedly get SIGSEGVs while going through some 
> unseen
> mails in my inbox:
> 
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x55596b73f69a in update_index (menu=0x0, ctx=0x55596d883090, 
> check=1, oldcount=26756, index_hint=0) at ../../curs_main.c:371
> 371 ../../curs_main.c: No such file or directory.
> (gdb) bt
> #0  0x55596b73f69a in update_index (menu=0x0, ctx=0x55596d883090, 
> check=1, oldcount=26756, index_hint=0) at ../../curs_main.c:371
> #1  0x55596b772e7d in mutt_pager (banner=banner@entry=0x0, 
> fname=fname@entry=0x7ffc75f98e70 
> "/tmp/mutt-jupiter-1000-22076-6547043317620087410", flags=, 
> flags@entry=66, extra=extra@entry=0x7ffc75f98e40) at ../../pager.c:2031
> #2  0x55596b734045 in mutt_display_message (cur=0x55596f740ed0) at 
> ../../commands.c:225
> #3  0x55596b74464b in mutt_index_menu () at ../../curs_main.c:1902
> #4  0x55596b7247aa in main (argc=1, argv=) at 
> ../../main.c:877
> 

I believe this has been solved in 1.8.3+neomutt20170609-1; I've removed all
pager.c patches and we moved to neomutt upstream.

Could you tell me if this is still happening for you?

Bug#859652: mutt: Crashes when trying to display (or fetch) a specific S/MIME-signed message

[Antonio Radici]

Tags: moreinfo

On Wed, Apr 05, 2017 at 04:42:51PM +0200, Axel Beckert wrote:
> Package: mutt
> Version: 1.7.2-1
> Severity: important
> Tags: security
> 
> Dear Maintainer,
> 
> for the first time since upgrading to Stretch a few months ago, mutt
> crashed when I pressed enter on mail -- both when viewing locally as
> well as via IMAP). Starting up mutt again and trying to display that
> mail again crashes again, i.e. it seems to be reproducible.
> 
> Here's a backtrace made from the coredump:

Hi Axel,
could you send the mail in private assuming that this is still reproducible in
1.8.3+neomutt20170609-1? thanks!

Bug#865822: mutt: Enter key disabled with latest upgrade

[Antonio Radici]

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 every single alias I had, ment that I didn't
> start in my inbox as defined by my $MAIL environment variable, and
> couldn't decode html email despite having set a tmpdir ... and so
> forth.  It behaves like all the sane compile time defaults were
> replaced with something unusable.
> 
> -- 
> Jamie Heilman http://audible.transient.net/~jamie/
> 

mutt should fall back to "/tmp" if $TMPDIR is not set, that code is in init.c,
compile time defaults were not touched by this release. I'll investigate this
problem today.

Bug#857945: mutt: IMAP login fails for mail host using TLS1.2 (ECDHE-RSA/AES-256-GCM/AEAD)

[Antonio Radici]

Tags: moreinfo

On Thu, Mar 16, 2017 at 03:35:52PM +0100, Armin Haas wrote:
> Package: mutt
> Version: 1.8.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> after upgrading mutt from version 1.7.2-1 to 1.8.0-1, I can no longer access
> my mail with IMAP on a mailhost which uses TLS1.2 
> (ECDHE-RSA/AES-256-GCM/AEAD).
> The mailhost claims I use a wrong username or password.
> 
> Reverting to mutt 1.7.2-1 fixes this and the IMAP login to the same mailhost
> using the same TLS1.2 setup works fine.
> 
> (In both cases, username and password are read from the same file, so there is
> no possibility of a typo.)
> 
> As a sidenote: I use another mail account on another host, which offers
> IMAP with TLS1.2 (RSA/AES-256-CBC/SHA1). Access to that one works fine
> with both versions.
> 

Hi,
does it work if you set imap_authenticators="login" in your config file?

Bug#838720: [Pkg-mutt-maintainers] Bug#838720: closed by Sebastian Ramacher (Re: Bug#837584: mutt: crash while navigating through inbox)

[Antonio Radici]

On Sun, Jun 25, 2017 at 12:14:29PM -0400, Peter Colberg wrote:
> Control: reopen -1
> Control: found -1 1.7.2-1
> Control: tags -1 stretch
> 
> > On 2017-06-24 18:49:55, Antonio Radici wrote:
> > > On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote:
> > > 
> > > I believe this has been solved in 1.8.3+neomutt20170609-1; I've removed 
> > > all
> > > pager.c patches and we moved to neomutt upstream.
> > > 
> > > Could you tell me if this is still happening for you?
> > 
> > I haven't seen the crash since upgrading to 1.8.0-1, so let's close it with 
> > that
> > version.
> 
> Could you please backport the fix(es) for inclusion in the next stable
> point release? mutt in stable is still segfaulting on a regular basis.
> 

Hi Peter,
I would happily do it but unfortunately I've been unable to identify the
culprit, despite me spending a lot of time in pager.c

In mutt 1.8.0 upstread did completely rewrite the pager, and neomutt also put
some patches on the top on that, to clean up the code, so the problem is fixed. 

I will try to investigate a bit more and try to write a patch for stretch but it
will require some more time unfortunately.

Bug#860122: [Pkg-mutt-maintainers] Bug#860122: mutt: SIGSEGV when saving a file to sshfs dir

[Antonio Radici]

Tags: +moreinfo

On Tue, Apr 11, 2017 at 06:43:54PM +0200, Kim Alvefur (Zash) wrote:
> Package: mutt
> Version: 1.7.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Attempt to save an email into a directory mounted via FUSE / sshfs
> causes a segmentation fault.
> 
> The file is created, but empty. Due to lack of debug symbols in stretch,
> all I get from gdb is the following:
> 
> #0  __GI___fileno (fp=0x0) at fileno.c:35
> 35  fileno.c: No such file or directory.
> 

Could you please install the debug symbols and send the stacktrace again?
Thanks!

More info on how to do so are here:
https://wiki.debian.org/AutomaticDebugPackages

Bug#854127: mutt: Please provide higher resolution icon

[Antonio Radici]

On Sat, Feb 04, 2017 at 12:46:35PM +0100, Laurent Bigonville wrote:
> Package: mutt
> Version: 1.7.2-1
> Severity: wishlist
> 
> Hi,
> 
> Mutt is providing a .desktop file which uses the mutt.xpm icon as
> fallback as there are not higher resolution icon.
> 
> This icon is way too small and is pixelated in desktop environment like
> GNOME.
> 
> Could you please provide .png image with higher resolution of this icon
> too? It must be installed in /usr/share/icons/hicolor/.
> 
> Regards,
> 
> Laurent Bigonville

I've forwarded this issue upstream.

Bug#838720: [Pkg-mutt-maintainers] Bug#838720: closed by Sebastian Ramacher (Re: Bug#837584: mutt: crash while navigating through inbox)

[Antonio Radici]

On Sun, Jun 25, 2017 at 07:50:00PM +, Antonio Radici wrote:
> On Sun, Jun 25, 2017 at 12:14:29PM -0400, Peter Colberg wrote:
> > Control: reopen -1
> > Control: found -1 1.7.2-1
> > Control: tags -1 stretch
> > 
> > > On 2017-06-24 18:49:55, Antonio Radici wrote:
> > > > On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote:
> > > > 
> > > > I believe this has been solved in 1.8.3+neomutt20170609-1; I've removed 
> > > > all
> > > > pager.c patches and we moved to neomutt upstream.
> > > > 
> > > > Could you tell me if this is still happening for you?
> > > 
> > > I haven't seen the crash since upgrading to 1.8.0-1, so let's close it 
> > > with that
> > > version.
> > 
> > Could you please backport the fix(es) for inclusion in the next stable
> > point release? mutt in stable is still segfaulting on a regular basis.
> > 
> 
> Hi Peter,
> I would happily do it but unfortunately I've been unable to identify the
> culprit, despite me spending a lot of time in pager.c
> 
> In mutt 1.8.0 upstread did completely rewrite the pager, and neomutt also put
> some patches on the top on that, to clean up the code, so the problem is 
> fixed. 
> 
> I will try to investigate a bit more and try to write a patch for stretch but 
> it
> will require some more time unfortunately.
> 

Hi Peter,
I've tried to reproduce the problem and the procedure outlined in the message
sent by Hannes on Mon, 12 Sep 2016 21:37:10 +0200 does not make it reproducible.

Could you please post a stacktrace of your issue? it seems to me that it
might not be related to this bug (maybe it's the imap ssl problem)

Bug#530584: mutt: should use /var/tmp for mail drafts by default

[Antonio Radici]

Control: tags -1 + pending

Time to revisit this bug, probably worth changing the default at this point.

Bug#836779: [Pkg-mutt-maintainers] Bug#836779: mutt: fails to display the correct count of message in the virtual folder index

[Antonio Radici]

Control: tag -1 + moreinfo

On Mon, Sep 05, 2016 at 06:38:32PM +0200, Nicolas Évrard wrote:
> Package: mutt
> Version: 1.7.0-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I use mutt with notmuch and I bound a key to change-vfolder.
> When this key is pressed if I use '?' insead of switching to a vfolder, you
> will go to a screen displaying all the vfolders with the mail and unread
> counts.
> 
> Both counts are 0 when they should be different (although in some situation 
> the
> unread count is correct but I haven't found yet a pattern).

Hi there!
are you still able to reproduce the bug with 1.8.3+neomutt20170609-2?

Bug#845067: mutt: Crash when scrolling past the end of a message

[Antonio Radici]

Control: tag -1 + moreijnfo

On Sun, Nov 20, 2016 at 01:47:14AM +, Sam Morris wrote:
> Package: mutt
> Version: 1.7.1-3
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I triggered this by pressing space while at the end of a message.
> Backtrace attached...

Any chance you could send us a copy of that message? Feel free to remove any
confidential information, I know some people are having segfaults with similar
backtraces but I've been unable to reproduce this so far.

Bug#866366: mutt: my index_format setting is corrupted with newer (neo)mutts

[Antonio Radici]

On Thu, Jun 29, 2017 at 05:02:55PM +0100, Jonathan Dowland wrote:
> tags 866366 +patch
> thanks
> 
> fd852e5556dc6c9194d5e72acce734321defe2f8 from upstream's repo (branch
> devel/expando, also attached) fixes this and applies cleanly on top of the
> package sources (I dropped it into debian/patches/applyme and modified series
> and all was well)

Thanks a lot for this (and thanks to Richard).
This will be released shortly, even this weekend if I manage to fix a
couple of segfaults that are still around.

Bug#866312: [Pkg-mutt-maintainers] Bug#866312: mutt: mailspell uses deprecated POSIX::tmpnam()

[Antonio Radici]

Control: tags -1 + confirmed pending

On Wed, Jun 28, 2017 at 10:49:14PM +0300, Niko Tyni wrote:
> Package: mutt
> Version: 1.8.3+neomutt20170609-2
> Severity: normal
> User: debian-p...@lists.debian.org
> Usertags: perl-5.26-transition
> 
> The mailspell helper uses POSIX::tmpnam(), which was deprecated in
> Perl 5.22.and is removed in Perl 5.26 (currently in experimental.)
> 
>   % /usr/lib/mutt/mailspell /dev/null
>   Calling POSIX::tmpnam() is deprecated at /usr/lib/mutt/mailspell line 37.
> 
> Please use File::Temp instead.
> -- 

Fixed in git, will be part of the next upload.

Bug#867201: postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204."

[Antonio Radici]

On Tue, Jul 04, 2017 at 09:38:35PM +0200, Julien Cristau wrote:
> Control: severity -1 normal
> 
> On Tue, Jul  4, 2017 at 19:27:09 +0200, Julien Cristau wrote:
> 
> > Source: postgrey
> > Version: 1.36-3
> > Severity: grave
> > User: debian-ad...@lists.debian.org
> > Usertags: needed-by-DSA-Team
> > X-Debbugs-Cc: debian-ad...@lists.debian.org
> > 
> > After upgrading one of our mail relays to stretch, postgrey regularly
> > crashes with the error is $subject.
> > 
> > This might or might not be fixed upstream with
> > https://github.com/schweikert/postgrey/commit/95a2cd8f7f132aae8c62e9706dd9459afca84a5c
> > which changed the relevant code and among other things added checks for
> > NetAddr::IP->new returning undef.
> > 
> Turns out this was most likely due to the recently-added ipv6 support in
> postgrey [0], and our exim config [1] using the ${mask:...} operator,
> which would return addresses such as
> "2a02.1600......" [2].  NetAddr::IP would then
> parse that as an ipv4 address and fail, and postgrey doesn't check for
> that condition.
> 

This is unfortunate, I will have a patch for stable-proposed-updates on
Saturday, sorry for the inconvenience :(

Bug#867201: postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204."

[Antonio Radici]

Control: tags -1 + moreinfo

On Thu, Jul 06, 2017 at 10:38:37AM +0200, Julien Cristau wrote:
> All good, at least the crash prompted me to look at this and update our
> exim config.  Might not have noticed otherwise :)
> 

Hi Julien,
this bug will be automatically closed by the 1.36-4 upload in unstable, but
obviously it's not solved for stretch so I'll reopen it.

Could you try the latest version in unstable in stretch? I can provide a
backport if needed, it builds clean without changes on a stretch pbuilder.

I've ported the new ip parsing code which should prevent this from happening,
I'm not sure if I have to resize the patch for stable-proposed-updates.

Looking forward to your feedback!

Bug#870635: mutt package is not using the official mutt tarball

[Antonio Radici]

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 is based on the NeoMutt
> tarball, not the official Mutt 1.8.3 release tarball.
> 
> If you wish to call your package "mutt", then you should be using the
> official Mutt release tarball are your "orig" tarball for the package.
> To do anything else is an unacceptable ethical and legal breach by
> Debian.
> 
> You have been aware of this issue since at least June 30th, see
> . As Erik
> Christiansen mentioned in that thread, while the GPLv2:
> 
>   "permits derivative works, it does not permit a derivative work to
>purport to be the copyrighted original work. Misrepresenting the
>"debneomutt" work as "mutt" would seem to clearly contravene the
>asserted and enforcible licence."
> 
> Even if the legal argument is not airtight, doing this is insulting
> and disrepectful to the Mutt project and to me as its maintainer.
> 
> Please correct this issue ASAP.

Hi Kevin,
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.

As I stated already this is not going to be fixed for the existing stable
distribution (because we cannot change what was already shipped), but this is
certainly going to be fixed for the current unstable/testing.

I would expect this to be done in August, it is a slight delay from what we
discussed on a mailing list but nothing has changed from my plans.

Bug#860176: [Pkg-mutt-maintainers] Bug#860176: mutt: segfaults when trying to show a progress bar

[Antonio Radici]

On Wed, Apr 12, 2017 at 05:52:33PM +0300, Alberto Garcia wrote:
> Package: mutt
> Version: 1.7.2-1
> Severity: normal
> Tags: patch
> 
> Hi,
> 
> mutt crashes when I'm trying to pipe messages through an external
> program because 228671-pipe-mime.patch (from Debian bug #569279) needs
> to be updated.
> 
> This is the code:
> 
>int imap_fetch_message (CONTEXT *ctx, MESSAGE *msg, int msgno)
>{
>  /* ... */
>  progress_t progressbar, *pbar;
>  /* ... */
>  if (!isendwin())
>  {
>mutt_progress_init (&progressbar, _("Fetching message..."),
>MUTT_PROGRESS_SIZE, NetInc, bytes);
>pbar = &progressbar;
>  }
>  else
>pbar = NULL;
>  if (imap_read_literal (msg->fp, idata, bytes, &progressbar) < 0)
>  /* ... */
>}
> 
> As you can see the code is passing &progressbar to imap_read_literal()
> but chances are that that variable has not been uninitialized.
> 
> Simply replacing &progressbar with pbar in that call and refreshing
> the patch fixes the problem.
> 

This sounds like a bug that should be fixed before stretch is released, I'll
submit your patch on Monday.

Bug#828263: cfengine3: FTBFS with openssl 1.1.0

[Antonio Radici]

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?

Yes, I'll do both things today.

Bug#846043: [Pkg-mutt-maintainers] Bug#846043: mutt: new neomutt release 2016-11-26 (1.7.1)

[Antonio Radici]

On Sun, Nov 27, 2016 at 11:56:25PM -0500, Peter Colberg wrote:
> Package: mutt
> Version: 1.7.1-3
> Severity: wishlist
> 
> Dear Maintainer,
> 
> Could you update mutt to the newest neomutt release? I would like to
> see whether it fixes the pager crash on arrival of new mail (#838720).
> 

Yes, that's planned, we are going to remove also a couple of patches that are
related, I'll have it uploaded between today and tomorrow.

Bug#845067: mutt: Crash when scrolling past the end of a message

[Antonio Radici]

Control: tag -1 +moreinfo

On Sun, Nov 20, 2016 at 01:47:14AM +, Sam Morris wrote:
> Package: mutt
> Version: 1.7.1-3
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I triggered this by pressing space while at the end of a message.
> Backtrace attached...

Hi,
could you check with 1.7.1-5 and verify if it's still reproducible?
Thanks!

Bug#843351: mutt FTCBFS: compiles build tools with the host architecture compiler

[Antonio Radici]

Control: tag -1 +pending

On Sun, Nov 06, 2016 at 09:31:42AM +0100, Helmut Grohne wrote:
> Source: mutt
> Version: 1.7.1-2
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> mutt fails to cross build from source, because it compiles build tools
> such as makedoc or mutt_md5 using the host architecture compiler. Beyond
> that, configure misdetect the permission for /var/mail causing
> mutt_dotlock to be skipped.
> 
> Using the build architecture compiler for build tools is not entirely
> trivial, because those tools include config.h. It generally contains
> test results for the host architecture, which may be different for the
> host architecture. Thus config.h must not be included when using the
> build architecture compiler. This may be considered a regression for
> native builds and thus unsuitable for upstream. I don't know a proper
> fix here.
> 
> Still the attached patch makes cross builds work on Debian. Please
> consider applying it.
> 

Thanks for the patch. I'll apply it in the next version.

Bug#842062: mutt segfaults when leaving pager view of composed message on new message

[Antonio Radici]

On Tue, Nov 01, 2016 at 11:31:54AM -0400, Ryan Kavanagh wrote:
> Hi,
> 
> On Tue, Oct 25, 2016 at 06:34:43PM +0200, Hannes von Haugwitz wrote:
> > mutt 1.7.1-2 segfaults when leaving pager view of composed message on
> > new message:
> 
> I can reproduce Hannes's bug. It doesn't happen to me every time, but it
> happens with an annoying frequency. It also happens after running ispell
> on a message. Frequently, the message in the bottom status line at
> segfault time is "Fetching headers...".
> 
> I've attached two backtraces of the segfault, which look identical
> modulo some irrelevant details like account names and FCC.
> 
> Please let me know if there's any further debugging information you can
> use.

Hi,
do you mind checking against the latest version (1.7.1-5)? I believe all pager
bugs have been fixed and I've also pulled out a patch which might be related

Bug#838720: pager crashes when maildir is modified while viewing message

[Antonio Radici]

On Tue, Dec 06, 2016 at 01:30:10AM -0500, Peter Colberg wrote:
> Control: found -1 1.7.1-5
> Control: retitle -1 mutt: pager crashes when maildir is modified while 
> viewing message
> 
> Unfortunately neomutt 2016-11-26 continues to cause the pager to crash
> frequently when the maildir is updated in the background, e.g., when
> synchronizing a new message from/to the IMAP server with mbsync.

Peter, do you have time to try neomutt standard without Debian patches? That at
least will help us to undestand if it's a rogue patch or if the problem is in
neomutt.

I can provide the debian package if you want, otherwise you could compile
yourself from the latest release.

Bug#828262: cfengine2: FTBFS with openssl 1.1.0

[Antonio Radici]

Control: severity -1 important

On Wed, Dec 07, 2016 at 11:19:20PM +0100, Petter Reinholdtsen wrote:
> Given that cfengine2 no longer get any upstream development, as far as I know,
> I guess the easiest and most sensible way to fix this is to build with
> libssl1.0-dev for now.  If cfengine2 is still needed in Stretch+1 someone 
> should
> consider to port the code to openssl 1.1.
> 
> Debian Edu still uses cfengine2, and would very much like to see it still
> available in Stretch.
> 
> If this patch is applied, this BTS report should have its severity lowered to
> important or normal.
> 
> diff -ur cfengine2-2.2.10/debian/control cfengine2-2.2.10-pere/debian/control
> --- cfengine2-2.2.10/debian/control 2016-08-21 08:24:15.0 +
> +++ cfengine2-2.2.10-pere/debian/control2016-12-07 22:14:28.911881217 
> +
> @@ -3,7 +3,7 @@
>  Priority: optional
>  Maintainer: Antonio Radici 
>  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, libdb-dev, libssl1.0-dev, libtool, perl (>= 5),
>   po-debconf, texinfo, quilt, libselinux1-dev [linux-any]
>  Standards-Version: 3.9.8
>  Homepage: http://www.cfengine.org/

I concur with this assessment, I'll downgrade the severity of this bug to
important, unfortunately there is no upstream development of cfengine2, Peter
has submitted a patch to modify the dependency for 2.2.10-7.

If I have time I might consider to patch it for 1.1 (I did it for cfengine3 in
the past).

Bug#664249: mutt: Error allocating SASL connection when using imaps

[Antonio Radici]

Control: tag -1 moreinfo

Hi,
I was wondering if you can still reproduce this bug against 1.7.0-1

Bug#666189: "fopen: File exists (errno = 17)" error when saving attachment to sshfs

[Antonio Radici]

severity 778801 normal
merge 664249 778801
reassign 664249 sshfs
retitle -1 sshfs unable to handle hardlinks properly
thanks

On Thu, Aug 25, 2016 at 04:31:26PM +0200, Louis-David Mitterrand wrote:
> On Thu, Aug 25, 2016 at 06:20:42AM +0000, Antonio Radici wrote:
> > tag 666189 +moreinfo
> > thanks
> 
> Yes it still happens with mutt 1.6.2-2 (haven't been able to install 1.6.2-3) 
> 
> In order to save an attachement on a sshfs mount with mutt I have to
> use "sshfs -odisable_hardlink"

I believe this is due to a bad interaction between sshfs and mutt, mutt is using
hardlinks to save files to the maildir but it seems that the inode number of the
hardlinks on sshfs is not the same as the original file and this causes problem:
https://sourceforge.net/p/fuse/mailman/message/33475658/

I've also merged 778801 with this bug and I'm reassigning this bug to the sshfs
maintainer to check what is that it is going wrong. For what it concerns mutt
everything is fine as we are using hardlinks are they are supposed to be used
and we are not seeing this problem on other filesystems

Bug#644992: mutt: Cannot use IPv6 address in IMAP/POP3 URL

[Antonio Radici]

Control: tag -1 +patch pending

This patch can be included in the next release.

Bug#834765: mailto_allow should include Cc, In-Reply-To, and References by default

[Antonio Radici]

Control: tag -1 +pending

On Thu, Aug 18, 2016 at 12:11:47PM -0700, Josh Triplett wrote:
> Package: mutt
> Version: 1.6.2-2
> Severity: wishlist
> Tags: upstream
> Control: forwarded -1 https://github.com/neomutt/neomutt/issues/115
> 
> Mutt's default value for mailto_allow includes only Subject and Body.
> I'd like to suggest changing the default to also include Cc,
> In-Reply-To, and References.
> 
> In-Reply-To and References allows mailing list archives to include
> mailto links that won't break threading. Debian mailing lists and the
> Debian bug-tracking system include such links. Cc allows those links to
> mail both the list and the author of the mail.
> 
> I don't see any obvious way that allowing those additional headers could
> cause harm, and I think allowing them by default would improve
> usability.

This could be added in the next release, if NeoMutt does not do it before :)

Bug#819196: mutt segfaults on scoring with ~X

[Antonio Radici]

Control: tag -1 +pending

On Thu, Mar 24, 2016 at 07:06:47PM +0100, Francesco Ariis wrote:
> Package: mutt
> Version: 1.5.23-3
> Severity: normal
> 
> Dear Maintainer,
> 
> open your .muttrc, paste this line
> 
> score "~X >1" -60
> 
> save, load mutt, enter any folder, mutt crashes with
> 
> Reading /home/user/mailfolder/folder... 0/438 (0%)Segmentation fault
> 
> Note that this pattern only crashes if used in a scoring rule (i.e.
> you can use ~X in a 'limit' pattern).
> 

backtrace FTR:

mx_open_message (ctx=ctx@entry=0x0, msgno=0) at ../../mx.c:1440
1440  if (!ctx->mx_ops->open_msg)
(gdb) bt
#0  mx_open_message (ctx=ctx@entry=0x0, msgno=0) at ../../mx.c:1440
#1  0x555c27eb in mutt_parse_mime_message (ctx=0x0, cur=0x55f08b40) 
at ../../parse.c:965
#2  0x555c29b5 in mutt_count_body_parts (ctx=, 
hdr=0x55f08b40) at ../../parse.c:1740
#3  0x555c4d6b in mutt_pattern_exec (pat=0x559f9e20, 
flags=MUTT_MATCH_FULL_ADDRESS, ctx=0x0, h=0x55f08b40) at 
../../pattern.c:1290
#4  0x555d3b33 in mutt_score_message (ctx=ctx@entry=0x559d2d60, 
hdr=hdr@entry=0x55f08b40, upd_ctx=upd_ctx@entry=0) at ../../score.c:136
#5  0x555b7735 in mx_update_context (ctx=ctx@entry=0x559d2d60, 
new_messages=) at ../../mx.c:1572
#6  0x5562cfc5 in imap_read_headers (idata=0x559df780, 
msgbegin=5220, msgend=5219) at ../../../imap/message.c:379
#7  0x55629f29 in imap_open_mailbox (ctx=0x559d2d60) at 
../../../imap/imap.c:755
#8  0x555b57b0 in mx_open_mailbox (path=, flags=0, 
pctx=0x0) at ../../mx.c:679
#9  0x5556d2d9 in main (argc=1, argv=) at 
../../main.c:869
(gdb) 

Bug#836071: postgrey: cannot be upgraded: initscript postgrey, action "stop" failed

[Antonio Radici]

Control: fixed -1 1.36-3

1.36-3 has the fix for this, have you tried to run that?

Bug#836148: [Pkg-mutt-maintainers] Bug#836148: mutt: Key bindings for e.g. notmuch features were removed

[Antonio Radici]

Control: tag -1 +pending

On Wed, Aug 31, 2016 at 07:07:53AM +0900, Mike Hommey wrote:
> Package: mutt
> Version: 1.7.0-1
> Severity: normal
> 
> Dear Maintainer,
> 
> In bug 834448, it was reported that neomutt bindings were used by
> default and changed some of the default mutt bindings.
> 
> However, it seems a result of that is that bindings that do *not*
> overlap with the default mutt bindings were lost at the same time.
> 
> In my case, this means "entire-thread" is not bound to "+" anymore,
> while "+" is bound to nothing else.
> 

See http://www.neomutt.org/feature/notmuch/

section 5:
Notmuch adds the following functions to Mutt. By default, none of them are bound
to keys.

and then there is an example configuration in section 8 (thanks to Elimar
Riesebieter for pointing this out).

What we need to do here is to add the binding to Muttrc and then we should be
fine, I'll do it in 1.7.0-2 (will submit the change to the Debian git tonight)

Bug#836339: [Pkg-mutt-maintainers] Bug#836339: mutt: segfaults shortly after tls_socket_read error on imaps

[Antonio Radici]

On Thu, Sep 01, 2016 at 10:48:41PM +0200, Samuel Hym wrote:
> Package: mutt
> Version: 1.7.0-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I use mutt with imaps servers which like to impolitely break up
> the connexion, yielding tls_socket_read errors.
> Since the update to mutt/1.7.0-1, mutt now segfaults shortly after the
> error (after the message "Mailbox closed").
> 
> I tried to launch "mutt -d 1", "mutt -d 2", ... without any muttdebug
> file showing up so I’m fairly clueless on the best way to debug this.
> Any test I could try?

This is not good, don't worry for the debug, from your description it should be
easily reproducible.

I'll update this bug once I'm able to reproduce it

Bug#836343: mutt: macro interpretation is really fragile

[Antonio Radici]

Contro: tag -1 +moreinfo

On Thu, Sep 01, 2016 at 11:50:01PM +0200, Samuel Hym wrote:
> Package: mutt
> Version: 1.7.0-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I set up mutt with some heavy macros but I ran into a very dangerous
> behaviour: if I define
> 
> macro index  ''
> 
> and press  in index, it doesn't call the postpone-message command
> (of course, because it is not available in index), but it instead runs
> the 18 commands associated with the 18 keys!

Did you notice this behavior in previous versions of mutt? Did it happen only on
this version? Does it happen in unstable?

Bug#833192: Overwrites Message-Id when using "mutt -H" or Alt-e to resend (breaks patch mail threading)

[Antonio Radici]

Control: tag -1 pending

On Mon, Aug 01, 2016 at 04:58:45PM -0700, Josh Triplett wrote:
> Related upstream bug: https://dev.mutt.org/trac/ticket/3081

Hi Josh,
the upstream bug was fixed, I've already submitted to the git repo for our
package the patch that they did, so this will be include din 1.7.0-2.

Bug#819196: mutt segfaults on scoring with ~X

[Antonio Radici]

On Thu, Mar 24, 2016 at 07:06:47PM +0100, Francesco Ariis wrote:
> Package: mutt
> Version: 1.5.23-3
> Severity: normal
> 
> Dear Maintainer,
> 
> open your .muttrc, paste this line
> 
> score "~X >1" -60
> 
> save, load mutt, enter any folder, mutt crashes with
> 
> Reading /home/user/mailfolder/folder... 0/438 (0%)Segmentation fault
> 
> Note that this pattern only crashes if used in a scoring rule (i.e.
> you can use ~X in a 'limit' pattern).
> 

Ciao Francesco,
the upstream bug has been resolved, it seems that ~X cannot be used in
message scoring, you can find more info in the forwarded bug.


I've added their change to our git repo and this will be included in 1.7.0-2