Your message dated Sat, 13 Nov 2010 16:58:48 +0000
with message-id <[email protected]>
and subject line Bug#603235: fixed in midgard2-core 10.05.1.2-2
has caused the Debian Bug report #603235,
regarding midgard2-core: FTBFS: problematic build dependencies
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 [email protected]
immediately.)


-- 
603235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603235
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: midgard2-core
Version: 10.05.1.2-1
Severity: important

For some reason, midgard2-core explicitly lists libc6 in
Build-Depends, even though it's (build-)essential on the architectures
on which it's available.  (For historical reasons, a handful use a
different SONAME).

In addition, several clauses of Build-Depends favor packages such as
midgard-libgda-4.0-dev that are not (currently) available, triggering
sbuild bug #403246; although its author has uploaded a fix, it
evidently hasn't made it to the autobuilders quite yet, so you may
wish to consider working around it for now. :-/

Could you please adjust midgard2-core's build dependencies to address
at least the first of those concerns?

Thanks!



--- End Message ---
--- Begin Message ---
Source: midgard2-core
Source-Version: 10.05.1.2-2

We believe that the bug you reported is fixed in the latest version of
midgard2-core, which is due to be installed in the Debian FTP archive:

gir1.0-midgard2_10.05.1.2-2_i386.deb
  to main/m/midgard2-core/gir1.0-midgard2_10.05.1.2-2_i386.deb
libmidgard2-dev_10.05.1.2-2_i386.deb
  to main/m/midgard2-core/libmidgard2-dev_10.05.1.2-2_i386.deb
libmidgard2_10.05.1.2-2_i386.deb
  to main/m/midgard2-core/libmidgard2_10.05.1.2-2_i386.deb
midgard2-bin_10.05.1.2-2_i386.deb
  to main/m/midgard2-core/midgard2-bin_10.05.1.2-2_i386.deb
midgard2-common_10.05.1.2-2_i386.deb
  to main/m/midgard2-core/midgard2-common_10.05.1.2-2_i386.deb
midgard2-core_10.05.1.2-2.debian.tar.gz
  to main/m/midgard2-core/midgard2-core_10.05.1.2-2.debian.tar.gz
midgard2-core_10.05.1.2-2.dsc
  to main/m/midgard2-core/midgard2-core_10.05.1.2-2.dsc



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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Piotr Pokora <[email protected]> (supplier of updated midgard2-core 
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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 12 Nov 2010 10:33:31 +0100
Source: midgard2-core
Binary: libmidgard2 libmidgard2-dev midgard2-common midgard2-bin gir1.0-midgard2
Architecture: source i386
Version: 10.05.1.2-2
Distribution: unstable
Urgency: low
Maintainer: Piotr Pokora <[email protected]>
Changed-By: Piotr Pokora <[email protected]>
Description: 
 gir1.0-midgard2 - Midgard2 - GObject Introspection
 libmidgard2 - Midgard Content Repository - Runtime Library
 libmidgard2-dev - Midgard Content Repository - Development Files
 midgard2-bin - Midgard2 command line tools.
 midgard2-common - Midgard2 common files used by different midgard extensions
Closes: 603235
Changes: 
 midgard2-core (10.05.1.2-2) unstable; urgency=low
 .
   * Standards-Version set to newest one: 3.9.1
   * Removed midgard-libgda4 from build and binary dependencies
   * Removed libc6 from build dependencies. Closes: #603235
Checksums-Sha1: 
 47f3c9233563adf9239d31e12ce34bbed0b7dcde 1545 midgard2-core_10.05.1.2-2.dsc
 56f1cb1035f558f66b6d2801a55dbdb55e36d91c 2974 
midgard2-core_10.05.1.2-2.debian.tar.gz
 f2b96fd1927b79e94725f75a1829864c73d3e47c 176598 
libmidgard2_10.05.1.2-2_i386.deb
 70951449d624e293bbcb9d7d78ce66766d4b8135 233612 
libmidgard2-dev_10.05.1.2-2_i386.deb
 4fa655e9bfe8962e98a857125d4c8ac52dbabfe6 4912 
midgard2-common_10.05.1.2-2_i386.deb
 9301fd1f02e1ab9d0db5914a54e2ab7827d0185c 24568 
midgard2-bin_10.05.1.2-2_i386.deb
 768811adf52e75eed535c98a4cc09016b9ccdec3 47428 
gir1.0-midgard2_10.05.1.2-2_i386.deb
Checksums-Sha256: 
 aa523afccbfdb3a7e6e22dc98ba6839f90999abbc3a7d9346081b8765497a071 1545 
midgard2-core_10.05.1.2-2.dsc
 ba00e966777552c698b3fb4fc420ee762925c91828604149f33d104efd417659 2974 
midgard2-core_10.05.1.2-2.debian.tar.gz
 1e253e09fa5e62add1e845138c5c6a9edb4c0ec8eeb82af0164b7d3f3fae76e2 176598 
libmidgard2_10.05.1.2-2_i386.deb
 1aa5e6308fe6bbd0f5297327cde35a3adf898efb2078919c9777573aae794f2f 233612 
libmidgard2-dev_10.05.1.2-2_i386.deb
 378cc4f768c86a645b12a775bb87cb839c5fcd4b0c17ea1ecd63bb87b4004af7 4912 
midgard2-common_10.05.1.2-2_i386.deb
 7f163727e1d85aef0ca9a062acc7c374e20361c1b999b338e934873b065d2ea1 24568 
midgard2-bin_10.05.1.2-2_i386.deb
 165ab118e817e5fae9631dae199c3db25f18989aff37c9c93457bc02bd46ed73 47428 
gir1.0-midgard2_10.05.1.2-2_i386.deb
Files: 
 1e4ce6e76e2b57e500a4f352cd8e965c 1545 libs optional 
midgard2-core_10.05.1.2-2.dsc
 e4cb3f8f077b2a4a160896c0dd691dfa 2974 libs optional 
midgard2-core_10.05.1.2-2.debian.tar.gz
 2b59c2460749d2b8c5bba48c7b200d4f 176598 libs optional 
libmidgard2_10.05.1.2-2_i386.deb
 4b848cdd73348898e8fc7b344567b037 233612 libdevel optional 
libmidgard2-dev_10.05.1.2-2_i386.deb
 3c7d3266f2c74f870d6d48b91fb0a72b 4912 utils optional 
midgard2-common_10.05.1.2-2_i386.deb
 fe2305b4b41fdb97bbab88de8012cc11 24568 utils optional 
midgard2-bin_10.05.1.2-2_i386.deb
 1d18594191b6625156a8cf6574fcdbdd 47428 utils optional 
gir1.0-midgard2_10.05.1.2-2_i386.deb

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

iEYEARECAAYFAkzeviYACgkQgtffbfx/bQ9L5wCZAZjVsSzontDDAiWkr7+KE0df
2wMAnimNF5c5oUor5QrRTFiZsrKQmAFe
=ne3t
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to