Processed: retitle 725142 to pu: package totem-plugin-arte/3.1.2-1+deb7u1

2014-10-09 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 725142 pu: package totem-plugin-arte/3.1.2-1+deb7u1
Bug #725142 [release.debian.org] pu: package totem-plugin-arte/3.2.1-1~wheezy1
Changed Bug title to 'pu: package totem-plugin-arte/3.1.2-1+deb7u1' from 'pu: 
package totem-plugin-arte/3.2.1-1~wheezy1'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
725142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.141292043621781.transcr...@bugs.debian.org

Bug#764540: wheezy-pu: package glibc/2.13-38+deb7u5

2014-10-09 Thread Aurelien Jarno 
On Thu, Oct 09, 2014 at 10:29:25PM +0100, Adam D. Barratt wrote:
> On Thu, 2014-10-09 at 01:16 +0200, Aurelien Jarno wrote:
> > On Wed, Oct 08, 2014 at 11:27:30PM +0100, Adam D. Barratt wrote:
> > > Control: tags -1 + confirmed
> > > 
> > > On Wed, 2014-10-08 at 23:49 +0200, Aurelien Jarno wrote:
> > > > I would like to do an update of eglibc in wheezy, with the patches we
> > > > have accumulated in the SVN over the last months. I understand that
> > > > it's a bit late with the stable release schedule, that said all this
> > > > patches have been upstream and in jessie/sid for months.
> [...]
> > > Please go ahead; thanks.
> > > 
> > 
> > Thanks! I have just uploaded it.
> 
> A few other changes appear to have been included:
> 
>  debian/TODO |   33 
>  debian/debhelper.in/glibc-doc.install   |4 
>  debian/debhelper.in/glibc-doc.links |   17 
>  debian/debhelper.in/glibc-doc.manpages  |8 
> 
> were those intentional?

Oh I prepared my diff using the SVN and didn't notice that. It wasn't
intentional to add them, but on the other hand they have been removed by
mistake in the security team uploads deb7u3 and deb7u4. This means the
current glibc-doc is missing most of the documentation compared to
deb7u2, strange that we haven't got any bug report for that.

So we should keep these files to restore the documentation as it was
before. Should I do another upload mentioning in the changelog these
files have been added back?

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141010050651.gk24...@hall.aurel32.net

Bug#763278: gcc 4.9 wheezy-pu?

2014-10-09 Thread Adam D. Barratt 
On Thu, 2014-10-09 at 23:01 -0400, Michael Gilbert wrote:
> Note that the window for the next stable update is closing in about a
> week, so there isn't a lot of time.

Actually, the /point release/ is in about a week. The advertised window
for getting updates in to it closes this weekend.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1412915973.1325.22.ca...@jacala.jungle.funky-badger.org

Bug#763278: gcc 4.9 wheezy-pu?

2014-10-09 Thread Michael Gilbert 
Hi,

I would like to ask for your opinion about uploading a newer gcc
version to wheezy?

This is to be able to continue building chromium security updates,
which has been discussed with the release team [0].  They've requested
that I discuss it with gcc maintainers, which is the reason for this
message.

I would be responsible for building and maintaining it.

Anyway, any thoughts?

Note that the window for the next stable update is closing in about a
week, so there isn't a lot of time.

Best wishes,
Mike

[0] http://bugs.debian.org/763278


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CANTw=MNYx9hQTv1bC=5LsZDFGSJ=y9ws0dqfleufuvencgc...@mail.gmail.com

Bug#760518: marked as done (transition: gnome 3.14)

2014-10-09 Thread Debian Bug Tracking System 
Your message dated Fri, 10 Oct 2014 01:31:20 +0200
with message-id <54371ac8.6090...@debian.org>
and subject line Re: Bug#760518: transition: gnome 3.14
has caused the Debian Bug report #760518,
regarding transition: gnome 3.14
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.)


-- 
760518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

We've been working on GNOME 3.14 during the summer, with the intention
of trying to get it into Jessie. Most of the core packages are in
experimental or in svn by now. It is my intention to get the final bits
into experimental over the weekend and then deciding whether to go for
it right after that, depending on how things look.

So far it seems pretty easy compared to e.g. the 3.8 -> 3.12 upgrade,
as there are very few internal SONAME bumps (that shouldn't affect
non-GNOME modules) and we won't block on external bits, like we did
with upower and bluez for the previous upgrade.

Anyway I'll post a more detailed summary later on and then we can
decide whether this is feasible for Jessie. If we go for it, I expect
we can do it after the current ongoing transitions and have it done
in 5 to 10 days (the time to upload a few packages, scheduled binNMUs
and wait for everything to settle and transition). I think everything
could be done by mid-September.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---

On 16/09/14 23:58, Emilio Pozuelo Monfort wrote:

Control: tags -1 confirmed pending

On 05/09/14 00:07, Emilio Pozuelo Monfort wrote:

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

Hi,

We've been working on GNOME 3.14 during the summer, with the intention
of trying to get it into Jessie. Most of the core packages are in
experimental or in svn by now. It is my intention to get the final bits
into experimental over the weekend and then deciding whether to go for
it right after that, depending on how things look.

So far it seems pretty easy compared to e.g. the 3.8 -> 3.12 upgrade,
as there are very few internal SONAME bumps (that shouldn't affect
non-GNOME modules) and we won't block on external bits, like we did
with upower and bluez for the previous upgrade.

Anyway I'll post a more detailed summary later on and then we can
decide whether this is feasible for Jessie. If we go for it, I expect
we can do it after the current ongoing transitions and have it done
in 5 to 10 days (the time to upload a few packages, scheduled binNMUs
and wait for everything to settle and transition). I think everything
could be done by mid-September.


The only library transition we have so far is libmutter0d -> libmutter0e (with
only one rdep, gnome-shell, which will be updated as well). The core packages
(glib, gtk+, mutter, gnome-shell, ...) are all in experimental already, built
everywhere and working fine. I thus think we can get this done pretty quickly,
so I'm acking it. The 3.14 RC is scheduled for tomorrow, so we'll start
uploading that and we should be finished by next week.


This is done. Closing.

Emilio--- End Message ---

Bug#754988: Bug#763360 closed by Ondřej Surý

2014-10-09 Thread Julien Cristau 
On Fri, Oct 10, 2014 at 00:46:42 +0200, Bill Allombert wrote:

> On Tue, Oct 07, 2014 at 10:31:45AM +0200, Ondřej Surý wrote:
> > On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote:
> > > > Version: 1:1.3.1-4
> > > >
> > > > My understanding is that this bug can be now closed as
> > > > the libjpeg-progs are not built from src:libjpeg-progs and
> > > > libjpeg62* binary package names has been accepted now.
> > > 
> > > Excellent news! When do you plan to upload a version libjpeg-turbo that
> > > does not hijack libjpeg62 anymore ?
> > 
> > JFTR I will list the consequences of any renaming that would happen:
> > 
> > 1. libjpeg-turbo62 (as an example) would still contain shared library
> > libjpeg.so.62, thus it needs to "Conflicts/Provides: libjpeg62", same
> > applies for the libjpeg62-dev package vs libjpeg-turbo62-dev
> > ("Conflicts/Provides: libjpeg62-dev)
> 
> You are painting a bleaker picture than what is really required.
> Since the package are fully compatible, the conflict is easily avoided by
> moving some files a bit and then using the alternative system. 
> 
They're not fully compatible, as libjpeg-turbo's libjpeg.so.62 provides
additional entry points.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#754988: Bug#763360 closed by Ondřej Surý

2014-10-09 Thread Bill Allombert 
On Tue, Oct 07, 2014 at 10:31:45AM +0200, Ondřej Surý wrote:
> On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote:
> > > Version: 1:1.3.1-4
> > >
> > > My understanding is that this bug can be now closed as
> > > the libjpeg-progs are not built from src:libjpeg-progs and
> > > libjpeg62* binary package names has been accepted now.
> > 
> > Excellent news! When do you plan to upload a version libjpeg-turbo that
> > does not hijack libjpeg62 anymore ?
> 
> JFTR I will list the consequences of any renaming that would happen:
> 
> 1. libjpeg-turbo62 (as an example) would still contain shared library
> libjpeg.so.62, thus it needs to "Conflicts/Provides: libjpeg62", same
> applies for the libjpeg62-dev package vs libjpeg-turbo62-dev
> ("Conflicts/Provides: libjpeg62-dev)

You are painting a bleaker picture than what is really required.
Since the package are fully compatible, the conflict is easily avoided by
moving some files a bit and then using the alternative system. 

When do you plan to operate the renaming ?

I need to reupload libjpeg62 with a bumped epoch before the freeze.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141009224642.GA12136@yellowpig

NEW changes in stable-new

2014-10-09 Thread Debian FTP Masters 
Processing changes file: apt_0.9.7.9+deb7u6_amd64.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_armel.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_armhf.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_i386.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_ia64.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_kfreebsd-i386.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_mips.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_mipsel.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_powerpc.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_s390.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_s390x.changes
  ACCEPT
Processing changes file: apt_0.9.7.9+deb7u6_sparc.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_amd64.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_armel.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_armhf.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_i386.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_ia64.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_kfreebsd-i386.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_mips.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_mipsel.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_powerpc.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_s390.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_s390x.changes
  ACCEPT
Processing changes file: rsyslog_5.8.11-3+deb7u2_sparc.changes
  ACCEPT


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xclyw-0003si...@franck.debian.org

Bug#764540: wheezy-pu: package glibc/2.13-38+deb7u5

2014-10-09 Thread Adam D. Barratt 
On Thu, 2014-10-09 at 01:16 +0200, Aurelien Jarno wrote:
> On Wed, Oct 08, 2014 at 11:27:30PM +0100, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Wed, 2014-10-08 at 23:49 +0200, Aurelien Jarno wrote:
> > > I would like to do an update of eglibc in wheezy, with the patches we
> > > have accumulated in the SVN over the last months. I understand that
> > > it's a bit late with the stable release schedule, that said all this
> > > patches have been upstream and in jessie/sid for months.
[...]
> > Please go ahead; thanks.
> > 
> 
> Thanks! I have just uploaded it.

A few other changes appear to have been included:

 debian/TODO |   33 
 debian/debhelper.in/glibc-doc.install   |4 
 debian/debhelper.in/glibc-doc.links |   17 
 debian/debhelper.in/glibc-doc.manpages  |8 

were those intentional?

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1412890165.1325.20.ca...@jacala.jungle.funky-badger.org

Bug#725142: pu: package totem-plugin-arte/3.2.1-1~wheezy1

2014-10-09 Thread Nicolas Delvaux 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

A year later, the package is still broken in Stable.

Here is, yet again, a new debdiff.
Compared to the previous one, I edited a regex in order to be
compatible with a change that recently happened on the Arte Website.


Can someone finally upload this?

Thanks.
Nicolas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUNt63AAoJEF5mTbNeG1+eBLwQAImsNXN3WJgsYaydEPyyICew
GZS/2juauQ2P+aWQiWlyShTN8Qhn6EiD3mN0/K9k8x69ao+0O004m8lEhTGXrs2u
4L3VKRu3kzjtZ39Ign0oU19SkC4xB8JSMX55LBxyyzDoADSt3kgkYFoRbAa+h6v2
6/pLEXVZuTVELOLlYgx0K0O5L3DzgWw5mo5QpZNtPRDf59XSq1k6c92EObadNFMZ
ua8NidLdDLfNzA73UH7Rzc/oG+6eeUA3mz4mt5EVqlEZPFhHijpm4HZX4vTx3fgG
cI8AdtRy5GSXcwj0YSF4zJF2fYjIkT7tuKQdphKFYB7FDPZlGTfyc7p8wI90CwdW
9pRoUlDQxTSOoBa2u9CsRi4Sb3qkDXp1i9b3nhKJ7qc38nkhh7Z7HjcryidvjF5v
hko3GecxuhalhMKqtsMiuL+kpGqCDRPs8aaxCwfhS0v5SRrnXw7MJE+X63RN266K
sHMzNRNXO3ufyHbB8cwa6WXISVXujvbz+3QRwy+5GWl6CnMJWCdUy20MVawC8FMk
9WRv6+6hQEdQK/fsCvuOOf5FHF/1BWf8Y4dr0irnCqOayPBGvJFj93LZzMMUexoj
FSazFfwre5KHKdWAr2eT0daAmYzfPpaJzHvg+WP+S7syFP7YPx8+/BvmEpwupn51
ZVbvZDdsGKhKJ7mmgsJy
=oQ6g
-END PGP SIGNATURE-
diff -Nru totem-plugin-arte-3.1.2/debian/changelog totem-plugin-arte-3.1.2/debian/changelog
--- totem-plugin-arte-3.1.2/debian/changelog	2012-09-15 14:15:20.0 +0200
+++ totem-plugin-arte-3.1.2/debian/changelog	2014-10-09 16:22:42.0 +0200
@@ -1,3 +1,10 @@
+totem-plugin-arte (3.1.2-1+deb7u1) stable; urgency=low
+
+  * Update the video URL extractor
+  * Add a JSON parsing method and update the XML parser links
+
+ -- Nicolas Delvaux   Tue, 09 Oct 2014 14:22:42 +
+
 totem-plugin-arte (3.1.2-1) unstable; urgency=medium
 
   * New upstream bug-fix only release
diff -Nru totem-plugin-arte-3.1.2/debian/control totem-plugin-arte-3.1.2/debian/control
--- totem-plugin-arte-3.1.2/debian/control	2012-05-06 13:41:04.0 +0200
+++ totem-plugin-arte-3.1.2/debian/control	2014-10-09 16:22:42.0 +0200
@@ -8,6 +8,7 @@
libgtk-3-dev,
libsoup2.4-dev,
libpeas-dev (>= 1.2.0),
+   libjson-glib-dev,
gettext
 Standards-Version: 3.9.3
 Homepage: http://gitorious.org/totem-plugin-arte
diff -Nru totem-plugin-arte-3.1.2/debian/patches/parsers_update.patch totem-plugin-arte-3.1.2/debian/patches/parsers_update.patch
--- totem-plugin-arte-3.1.2/debian/patches/parsers_update.patch	1970-01-01 01:00:00.0 +0100
+++ totem-plugin-arte-3.1.2/debian/patches/parsers_update.patch	2014-10-09 17:51:34.0 +0200
@@ -0,0 +1,207 @@
+Description: Add a JSON parsing method and update the XML parser links
+ This change is backported from the 3.2.1 upstream version.
+ This patch will hopefully harden the plugin against more Arte website updates.
+Author: Nicolas Delvaux 
+
+---
+
+Origin: vendor
+Forwarded: not-needed
+Last-Update: 2013-12-19
+
+Index: totem-plugin-arte-3.1.2/arteparser.vala
+===
+--- totem-plugin-arte-3.1.2.orig/arteparser.vala	2014-10-09 17:51:13.806886723 +0200
 totem-plugin-arte-3.1.2/arteparser.vala	2014-10-09 17:51:13.802886723 +0200
+@@ -28,6 +28,7 @@
+ 
+ using GLib;
+ using Soup;
++using Json;
+ 
+ public abstract class ArteParser : GLib.Object
+ {
+@@ -55,7 +56,7 @@
+ return has_data;
+ }
+ 
+-public unowned GLib.SList parse (Language lang) throws MarkupError, IOError
++public virtual unowned GLib.SList parse (Language lang) throws MarkupError, IOError
+ {
+ videos = new GLib.SList ();
+ 
+@@ -105,36 +106,127 @@
+ }
+ }
+ 
++public class ArteJSONParser : ArteParser
++{
++private string json_url_fr = "http://www.arte.tv/guide/fr/plus7.json";;
++private string json_url_de = "http://www.arte.tv/guide/de/plus7.json";;
++
++public ArteJSONParser ()
++{
++reset ();
++}
++
++public override void reset ()
++{
++has_data = true;
++}
++
++public override uint get_error_threshold ()
++{
++return 1; // no errors are tolerated
++}
++
++public override unowned GLib.SList parse (Language lang) throws MarkupError, IOError
++{
++videos = new GLib.SList ();
++
++Soup.Message msg;
++if (lang == Language.GERMAN) {
++msg = new Soup.Message ("GET", json_url_de);
++} else {
++msg = new Soup.Message ("GET", json_url_fr);
++}
++
++Soup.SessionAsync session = create_session ();
++
++session.send_message (msg);
++
++if (msg.status_code != Soup.KnownStatusCode.OK) {
++throw new IOError.HOST_NOT_FOUND ("videos.arte.tv could not be accessed.");
++}
++
++var parser = new Json.Parser ();
++
++try {
++parser.load_from_data ((string) msg.response_body.flatten ().data, -1);
++} catch (GLib.Error e) {
++throw new GLib.MarkupError.PARSE ("Json parsing failed: '%s'", e.message);
++}
++
++

Bug#764534: wheezy-pu: package libplack-perl/0.9989-1+deb7u1

2014-10-09 Thread gregor herrmann 
On Wed, 08 Oct 2014 23:19:47 +0100, Adam D. Barratt wrote:

> > 0.9989-1+deb7u1 contains one cherry-picked upstream commit as a quilt
> > patch, which effectively changes one line (or more precisely: one
> > regexp) in the code. The patch also adds a test, and has a rather
> > long upstream commit message :)
> You weren't kidding. :-)

:)
 
> Please go ahead; thanks.

Thanks! Uploaded.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Mark Knopfler: Silvertown Blues


signature.asc
Description: Digital Signature

Bug#764525: marked as done (nmu: libalien-wxwidgets-perl_0.65+dfsg-4 libwx-perl_1:0.9923-3)

2014-10-09 Thread Debian Bug Tracking System 
Your message dated Thu, 09 Oct 2014 09:54:58 +0200
with message-id <54363f52.2090...@debian.org>
and subject line Re: Bug#764525: nmu: libalien-wxwidgets-perl_0.65+dfsg-4 
libwx-perl_1:0.9923-3
has caused the Debian Bug report #764525,
regarding nmu: libalien-wxwidgets-perl_0.65+dfsg-4 libwx-perl_1:0.9923-3
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.)


-- 
764525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

libalien-wxwidgets-perl and libwx-perl are uninstallable in sid
due to wxwidgets3.0 update to 3.0.2-1.

No dep-waits needed afaics as wxwidgets3.0 is already built on
all release architectures (just not on sparc.)

Note that libwx-perl will need libalien-wxwidgets-perl to be built
first, but I understand wanna-build handles that fine.

nmu libalien-wxwidgets-perl_0.65+dfsg-4 . ALL . -m "rebuild against wxWidgets 
3.0.2"
nmu libwx-perl_1:0.9923-3 . ALL . -m "rebuild against wxWidgets 3.0.2"

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

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---

On 08/10/14 21:34, Niko Tyni wrote:

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

libalien-wxwidgets-perl and libwx-perl are uninstallable in sid
due to wxwidgets3.0 update to 3.0.2-1.

No dep-waits needed afaics as wxwidgets3.0 is already built on
all release architectures (just not on sparc.)

Note that libwx-perl will need libalien-wxwidgets-perl to be built
first, but I understand wanna-build handles that fine.

nmu libalien-wxwidgets-perl_0.65+dfsg-4 . ALL . -m "rebuild against wxWidgets 
3.0.2"
nmu libwx-perl_1:0.9923-3 . ALL . -m "rebuild against wxWidgets 3.0.2"


Scheduled.

Emilio--- End Message ---