Your message dated Mon, 25 Nov 2013 16:05:11 +0000
with message-id <e1vkyet-0000ib...@franck.debian.org>
and subject line Bug#713118: fixed in modemmanager 0.5.2.0-2.1
has caused the Debian Bug report #713118,
regarding modemmanager: FTBFS: unsatisfiable build-dependency: automake (< 
1:1.12) but 1:1.13.3-1 is to be installed
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 ow...@bugs.debian.org
immediately.)


-- 
713118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: modemmanager
Version: 0.5.2.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Install modemmanager build dependencies (apt-based resolver)                
>  │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-modemmanager-dummy : Depends: automake (< 1:1.12) but 
> 1:1.13.3-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/modemmanager_0.5.2.0-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: modemmanager
Source-Version: 0.5.2.0-2.1

We believe that the bug you reported is fixed in the latest version of
modemmanager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 713...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balint Reczey <bal...@balintreczey.hu> (supplier of updated modemmanager 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 25 Nov 2013 16:22:58 +0100
Source: modemmanager
Binary: modemmanager modemmanager-dbg
Architecture: source amd64
Version: 0.5.2.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Alexander Sack <a...@ubuntu.com>
Changed-By: Balint Reczey <bal...@balintreczey.hu>
Description: 
 modemmanager - D-Bus service for managing modems
 modemmanager-dbg - D-Bus service for managing modems - debugging symbols
Closes: 713118
Changes: 
 modemmanager (0.5.2.0-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Don't limit automake's maximal version in build dependencies
     (Closes:  #713118)
Checksums-Sha1: 
 32f240e9f9e7052bd2385b8d25acf056d2416d53 2107 modemmanager_0.5.2.0-2.1.dsc
 4b9c8bea47ca82fdd8b4dba92f3a84ce0542e6ba 13577 
modemmanager_0.5.2.0-2.1.debian.tar.gz
 3ae3cf4f95fa14ad01ce00e683032dcd7aaf0e35 237288 
modemmanager_0.5.2.0-2.1_amd64.deb
 0f35700244a1eaccd5adc82e92c8ade1be247aa7 604528 
modemmanager-dbg_0.5.2.0-2.1_amd64.deb
Checksums-Sha256: 
 68a8eff4a56559562e3f67f7768b53c84fbaef0703c13ce9029629ba2330130a 2107 
modemmanager_0.5.2.0-2.1.dsc
 a928cc19b0d46c4aa1e12c77f552b3df4c93d21d3e7716dc7cc0406d512b05d6 13577 
modemmanager_0.5.2.0-2.1.debian.tar.gz
 ee15e39a824dce15a12403f12000831a95fab753f0601dcbaa6ac53f604003b6 237288 
modemmanager_0.5.2.0-2.1_amd64.deb
 446482951b42adcd019a4e28823b9d11ab17ca6a4af6d71cffda6508d0a168a5 604528 
modemmanager-dbg_0.5.2.0-2.1_amd64.deb
Files: 
 3ffd4a79ff4b2e8f103a86120b1412f0 2107 net optional modemmanager_0.5.2.0-2.1.dsc
 9e3c1945092ee6e5f35d959fd1487736 13577 net optional 
modemmanager_0.5.2.0-2.1.debian.tar.gz
 bb81f116035a545edeed7d7a07257bea 237288 net optional 
modemmanager_0.5.2.0-2.1_amd64.deb
 a24558ae5430891005fe84b257b96e9c 604528 debug extra 
modemmanager-dbg_0.5.2.0-2.1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJSk3IbAAoJEPZk0la0aRp90DAP/RK5qxdtW2hF1WjFPYF35pkb
I3/eQJoqaZS0A6+S+//gEUV6VK6cY+pjnhwT74Py0iWTQ0S50DXiGSdtAR3WKjuC
LYb3CXWc8IKMeC5AXLhlQ74h7w2A3cTVjZ+JOak5obTcZaOAnIdKlXM3XlEvBPG9
hQY55/23UMCn44PJ5U1rTeiHrSRsrMb+FmDd31v/TPKfxMAijXfw6f7QfLs2RtKm
ZHm4uIM4nR4X7dFj3frCs70Y9ZHBUcWyta+lzT8FdZxQcOonFPsOe+GsGbpXPE0x
Ik0+nmklrdh80YxHlhPHtJs6AtqXWyi5jb5Lcmo+0L+y8cTSC8px3yFOnEZ8oa/9
e+EFLhZ3W6dsyJywqVEZr0vFNqCKvZNHXQeVcqAt2806igrbi26WklHLluGyhQMn
2C38LPIWJ6A0/PZfxlERZR7Uekheq6FDv+yj0qBAqOmH7l0IKFW1POi/t/d2bXat
4DzWFP1pkQgOhzWEqQWfTBZvGWo1Pma8eRYAwF9ph7kr5P/+QzaFVkqOGqGo+xIR
tYseY1Yze+noctrrfXtf9qoZQz70VSmRbo1f6DHayg/+jHOdrLnQ6Nf5/Q6B4l9X
bLWC8KNEQtH+HrzV7mZECYP+Mh/oCHW9Hv6b6kbYYxf9jJn957NF7BG/Na87Jwcf
2SDN0djAwVUGH4TSTbkj
=gWIz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to