[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#694099: marked as done (unblock: gammu/1.32.0-1)

Your message dated Fri, 28 Dec 2012 21:42:43 +0100
with message-id <20121228204243.GB13945@ugent.be>
and subject line Re: Bug#694099: Re[2]: unblock: gammu/1.32.0-1
has caused the Debian Bug report #694099,
regarding unblock: gammu/1.32.0-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
694099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694099
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: wishlist
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package gammu.

The main changes are provided in the changelog:

gammu (1.32.0-1) unstable; urgency=low

   * New upstream release.
     - Fixes encoding of diverts (Closes: #677023).
     - Fixed typo in GSM encoding (Closes: #666924).
   * Adjust watch file to xz compressed files.
   * Use dpkg build flags.
   * Bump standards to 3.9.3.

 -- Michal Čihař <nijel@debian.org>  Wed, 27 Jun 2012 11:22:02 +0200

DebDiff is attached.

unblock gammu/1.32.0-1

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)

Attachment: gammu_1.32.0-1.diff.bz2
Description: Binary data


--- End Message ---
--- Begin Message --- 
Hi,

On Sat, Dec 29, 2012 at 12:32:28AM +0400, Bob Bib wrote:
> Ivo De Decker:
> > gammu didn't build on s390x (which is why it didn't migrate in
> > the first place). This needs to be fixed.
> Yes, it needs to be done...
> but s390x & mobile phone management... it sounds funny :)

Well, It's just a technical issue which will prevent migration to jessie in
the future, so it needs to be done somehow anyway.

> > Can you explain how this request matches the freeze policy?
> > http://release.debian.org/wheezy/freeze_policy.html
> It really doesn't, and this request has a wishlist severity.
> Don't care, I don't insist on it ;)

OK, I'm closing this bug.

Cheers,

Ivo

--- End Message ---
Reply to: