Bug#1062255: libcmtspeechdata: NMU diff for 64-bit time_t transition

[Sebastian Reichel]

Hi,

On Wed, 31 Jan 2024 20:27:14 + Steve Langasek  wrote:
> If you have any concerns about this patch, please reach out ASAP.  Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes available that your package should not be included in the transition,
> there is time for us to amend the planned uploads.

Enabling 64-bit time_t without any extra changes breaks this
library. The Kernel ABI is 32-bit, so the last field in
'struct cs_mmap_config_block' from kernel-headers/linux/cs-protocol.h
needs to be u32 seconds + u32 nanoseconds. I attached a patch,
which imports the latest kernel ABI (untested, since I currently
do not have enough time for it).

Note, that the kernel ABI has never been changed, since the unsigned
32 bit value only overflows in 2106 and then supporting the Nokia
N900/N950/N9 modem (which only supports GSM and UMTS) is no longer
expected to be relevant.

-- Sebastian
diff --git a/kernel-headers/linux/cs-protocol.h b/kernel-headers/linux/cs-protocol.h
index 9c23b7a..d01be14 100644
--- a/kernel-headers/linux/cs-protocol.h
+++ b/kernel-headers/linux/cs-protocol.h
@@ -87,6 +87,15 @@ struct cs_buffer_config {
 	__u32 reserved[4];
 };
 
+/*
+ * struct for monotonic timestamp taken when the
+ * last control command was received
+ */
+struct cs_timestamp {
+__u32 tv_sec;  /* seconds */
+__u32 tv_nsec; /* nanoseconds */
+};
+
 /*
  * Struct describing the layout and contents of the driver mmap area.
  * This information is meant as read-only information for the application.
@@ -107,7 +116,7 @@ struct cs_mmap_config_block {
 	 * if enabled with CS_FEAT_TSTAMP_RX_CTRL, monotonic
 	 * timestamp taken when the last control command was received
 	 */
-	struct timespec tstamp_rx_ctrl;
+	struct cs_timestamp tstamp_rx_ctrl;
 };
 
 #define CS_IO_MAGIC		'C'


signature.asc
Description: PGP signature

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Sebastian Reichel]

Hi Martin,

On Tue, Jan 24, 2023 at 10:50:52PM +, Martin wrote:
> Hi Sebastian,
> 
> I wonder, if I should upload libproxy with your github patch¹ to
> experimental. Then people affected (or not affected) by the bug can test
> easily. Or you may upload, of course! :-)
> 
> Cheers
> 
> ¹ https://github.com/libproxy/libproxy/issues/199#issuecomment-1401124997

sure, feel free to upload it to experimental. FWIW I do not
understand the root cause of this issue. I'm a bit worried,
that the patch masks a security relevant bug. It would be great
if somebody with better C++ knowledge can look into this.

The bug seems quite strange considering the segmentation fault is
happening due to the destruction of an empty vector from the standard
library and only in combination with glib-networking.

FWIW long term the problem will be solved by glib-networking
removing the libproxy dependency:

https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/205

Greetings,

-- Sebastian


signature.asc
Description: PGP signature

Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Sebastian Reichel]

Hi,

On Thu, Jan 19, 2023 at 04:12:14PM +0100, Sebastian Reichel wrote:
> On Wed, Jan 18, 2023 at 09:48:33PM +, Martin wrote:
> > Control: severity -1 grave
> > 
> > Justification for grave: Crashes Gajim for some users. RC, IMHO.

If I understood it correctly libproxy is only used by glib
networking code when not running GNOME.

> > On 2023-01-17 21:56, Sebastian Reichel wrote:
> > > I just got the new package through testing and now gajim segfaults
> > > ony my system with stacktrace pointing to libproxy. So this is not
> > > magically solved.
> > 
> > :-(
> > 
> > Could you check, if a downgrade to libproxy 0.4.15-15 helps?
> > That certainly helps to find the bug!
> 
> I tried downgrading libproxy1v5 and libproxy-tools to 0.4.15-15 and
> glib-networking to 2.66.0. This did not change anything.
> 
> With libproxy from testing gajim does work when being downgraded to
> 1.5.4-1 (which requires also downgrading python3-nbxmpp to
> 3.2.5-1 to be functional).

This has been reported upstream:

https://github.com/libproxy/libproxy/issues/199

Also these apparently describe the same bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970687
https://github.com/exaile/exaile/issues/737

Both workarounds mentioned in those bug reports (removing either
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so or
/usr/lib/x86_64-linux-gnu/libproxy.so.1.0.0) fix the crash and
gajim successfully connects.

-- Sebastian


signature.asc
Description: PGP signature

Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Sebastian Reichel]

Hi,

On Wed, Jan 18, 2023 at 09:48:33PM +, Martin wrote:
> Control: severity -1 grave
> 
> Justification for grave: Crashes Gajim for some users. RC, IMHO.
> 
> On 2023-01-17 21:56, Sebastian Reichel wrote:
> > I just got the new package through testing and now gajim segfaults
> > ony my system with stacktrace pointing to libproxy. So this is not
> > magically solved.
> 
> :-(
> 
> Could you check, if a downgrade to libproxy 0.4.15-15 helps?
> That certainly helps to find the bug!

I tried downgrading libproxy1v5 and libproxy-tools to 0.4.15-15 and
glib-networking to 2.66.0. This did not change anything.

With libproxy from testing gajim does work when being downgraded to
1.5.4-1 (which requires also downgrading python3-nbxmpp to
3.2.5-1 to be functional).

-- Sebastian


signature.asc
Description: PGP signature

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Sebastian Reichel]

Hi,

On Sat, 14 Jan 2023 21:53:59 + Martin  wrote:
> Control: severity -1 normal
> 
> The problem disappeared magically for all users who reported it before.
> I assume, that there is a hidden bug in libproxy, that only appears in
> certain circumstances. Downgrading for now.

I just got the new package through testing and now gajim segfaults
ony my system with stacktrace pointing to libproxy. So this is not
magically solved.

-- Sebastian


signature.asc
Description: PGP signature

Bug#988716: platformio 4.3.4 cannot download required frameworks

[Sebastian Reichel]

Package: platformio
Version: 4.3.4-1
Severity: grave

Dear Maintainer,

Upstream changed paths for the framework manifest files in recent
releases and did not maintain backward compatibility links resulting
in 4.3.4 no longer being able to install the frameworks.

For example this happens when I try to build the arduino-blink
hello world program:

$ platformio run -e d1_mini
Processing d1_mini (platform: espressif8266; framework: arduino; board: d1_mini)

PlatformManager: Installing espressif8266
Error: Detected unknown package 'espressif8266'

But not even native build is possible:

$ platformio platform install native
PlatformManager: Installing native
Error: Detected unknown package 'native'

There does not seem to be a way to get better error messages, but
using strace I can say it receives a 404 response for the following
query: "GET /platforms/manifest.json". The problem is fixed by
updating to latest upstream release [I tested 5.1.1], which has
already been requested in #976665.

This means the package is basically unusable for new installations
Since it did not exist in buster, it is always a new installation
in bullseye. Considering we are in late freeze phase I suggest to
drop the package from Debian testing (and upload a new upstream
release to sid).

-- Sebastian

Bug#970633: tt-rss: Packaging work for new upstream release 21.1

[Sebastian Reichel]

Hi Sunil,

On Thu, Feb 04, 2021 at 08:56:28AM +0100, Johannes Schauer Marin Rodrigues 
wrote:
> Quoting Johannes Schauer Marin Rodrigues (2021-02-04 08:50:51)
> > oh wow! Thanks a ton for all your work! This is phantastic. :)
> 
> while this still stands

Ack.

> > Do you want to do the upload yourself? Just add yourself to Uploaders as 
> > well
> > while you are at it, you seem to know what you are doing and I'd love 
> > somebody
> > to help out with packaging. Feel free to just put your commits directly into
> > the packaging repo on salsa!

That's already part of the changes :)

> let me retract this -- somehow I didn't read "tt-rss" and confused packages XD
> 
> It should of course not be me but Sebastian Reichel to make this call. :)

I had some pending work from last year doing some of these changes
and some additional things. Back then I stopped when reaching the
gettext part wondering how to be solve it (IIUIC upstream's version
has some security fixes). Anyways your solution is better than doing
nothing, so I merged everything together and just uploaded a new
version.

Your changes all looked sane and I'm mostly busy in the kernel world
these days and your help is appreciated. If I saw it correctly you are
not a DD, so I just gave you full permissions to the tt-rss repository.
Feel free to work directly in the repository without doing pull requests.

Thanks,

-- Sebastian


signature.asc
Description: PGP signature

Bug#932804: terminology-data: contains invalid arch specific file also contained in terminology package

[Sebastian Reichel]

Package: terminology-data
Version: 1.4.1-1
Severity: grave
Justification: renders package unusable

Hi,

terminology-data contains /usr/lib/x86_64-linux-gnu/terminology/tytest
in 1.4.1-1 and 1.5.0-1, which is also contained in terminology (so
package is not installable). Obviously an arch specific file does not
belong into an arch all package and should be removed from terminology-data.

-- Sebastian

Bug#923661: tt-rss: PHP Fatal error: Uncaught PDOException: SQLSTATE[22001]: String data, right truncated

[Sebastian Reichel]

Hi Helmut,

On Mon, May 20, 2019 at 08:33:10PM +0200, Helmut Grohne wrote:
> On Mon, May 20, 2019 at 06:51:57PM +0200, Sebastian Reichel wrote:
> > Did you forgot to add the attachment? FWIW both changes are with me.
> 
> Yes, sorry. I intend to move foward with a "maintainer acknowledged NMU"
> if you lack time for doing the upload.

Instead of creating an extra patch for the config change I would
prefer to have config.php-dist.patch updated. Regarding the NMU:
Please go ahead.

-- Sebastian

> diff --minimal -Nru tt-rss-18.12+dfsg/debian/changelog 
> tt-rss-18.12+dfsg/debian/changelog
> --- tt-rss-18.12+dfsg/debian/changelog2019-02-06 00:04:47.0 
> +0100
> +++ tt-rss-18.12+dfsg/debian/changelog2019-05-20 17:53:54.0 
> +0200
> @@ -1,3 +1,11 @@
> +tt-rss (18.12+dfsg-1.1) UNRELEASED; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Cherry pick JShrink PHP 7.3 compatibility patch. (Closes: #923661)
> +  * Default to using syslog as log backend rather than sql.
> +
> + -- Helmut Grohne   Mon, 20 May 2019 17:53:54 +0200
> +
>  tt-rss (18.12+dfsg-1) unstable; urgency=medium
>  
>* New upstream release
> diff --minimal -Nru tt-rss-18.12+dfsg/debian/patches/default_to_syslog.patch 
> tt-rss-18.12+dfsg/debian/patches/default_to_syslog.patch
> --- tt-rss-18.12+dfsg/debian/patches/default_to_syslog.patch  1970-01-01 
> 01:00:00.0 +0100
> +++ tt-rss-18.12+dfsg/debian/patches/default_to_syslog.patch  2019-05-20 
> 17:53:47.0 +0200
> @@ -0,0 +1,11 @@
> +--- tt-rss-18.12+dfsg.orig/config.php-dist
>  tt-rss-18.12+dfsg/config.php-dist
> +@@ -166,7 +166,7 @@
> + // Disabling auth_internal in this list would automatically disable
> + // reset password link on the login form.
> + 
> +-define('LOG_DESTINATION', 'sql');
> ++define('LOG_DESTINATION', 'syslog');
> + // Error log destination to use. Possible values: sql (uses internal 
> logging
> + // you can read in Preferences -> System), syslog - logs to system log.
> + // Setting this to blank uses PHP logging (usually to http server
> diff --minimal -Nru tt-rss-18.12+dfsg/debian/patches/jshrink_php7.3_fix.patch 
> tt-rss-18.12+dfsg/debian/patches/jshrink_php7.3_fix.patch
> --- tt-rss-18.12+dfsg/debian/patches/jshrink_php7.3_fix.patch 1970-01-01 
> 01:00:00.0 +0100
> +++ tt-rss-18.12+dfsg/debian/patches/jshrink_php7.3_fix.patch 2019-05-20 
> 17:49:53.0 +0200
> @@ -0,0 +1,32 @@
> +From 91105810dafedba0390608d7465abd602beb6410 Mon Sep 17 00:00:00 2001
> +From: Sergei Morozov 
> +Date: Fri, 14 Sep 2018 19:55:03 -0700
> +Subject: [PATCH] Fixed test failures on PHP 7.3
> +
> +1. continue in break shoud target the while loop directly 
> (php/php-src@04e3523).
> +2. strpos() doesn't longer accept non-string needles 
> (https://wiki.php.net/rfc/deprecations_php_7_3#string_search_functions_with_integer_needle).
> + src/JShrink/Minifier.php | 4 ++--
> + 2 files changed, 4 insertions(+), 3 deletions(-)
> +
> +diff --git a/src/JShrink/Minifier.php b/src/JShrink/Minifier.php
> +index 8103452..ad8157f 100644
> +--- a/vendor/JShrink/Minifier.php
>  b/vendor/JShrink/Minifier.php
> +@@ -183,7 +183,7 @@ protected function loop()
> + // new lines
> + case "\n":
> + // if the next line is something that can't stand alone 
> preserve the newline
> +-if (strpos('(-+{[@', $this->b) !== false) {
> ++if ($this->b !== false && strpos('(-+{[@', $this->b) 
> !== false) {
> + echo $this->a;
> + $this->saveString();
> + break;
> +@@ -231,7 +231,7 @@ protected function loop()
> + // check for some regex that breaks stuff
> + if ($this->a === '/' && ($this->b === '\'' || 
> $this->b === '"')) {
> + $this->saveRegex();
> +-continue;
> ++continue 3;
> + }
> + 
> + echo $this->a;
> diff --minimal -Nru tt-rss-18.12+dfsg/debian/patches/series 
> tt-rss-18.12+dfsg/debian/patches/series
> --- tt-rss-18.12+dfsg/debian/patches/series   2019-02-06 00:04:47.0 
> +0100
> +++ tt-rss-18.12+dfsg/debian/patches/series   2019-05-20 17:52:00.0 
> +0200
> @@ -1,3 +1,5 @@
>  config.php-dist.patch
>  remove-tt-rss-layer.patch
>  fix-db-updater-script.patch
> +jshrink_php7.3_fix.patch
> +default_to_syslog.patch



signature.asc
Description: PGP signature

Bug#923661: tt-rss: PHP Fatal error: Uncaught PDOException: SQLSTATE[22001]: String data, right truncated

[Sebastian Reichel]

Hi,

On Mon, May 20, 2019 at 05:59:05PM +0200, Helmut Grohne wrote:
> Control: tags -1 + patch
> 
> Hi Sebastian and Marcelo,
> 
> On Sat, May 11, 2019 at 10:41:48AM +0200, Stefan Fritsch wrote:
> > Yes, using the Minifier.php from the above commit fixes the issue (and
> > another php warning that appeared in apache error log). In order to test it,
> > one needs to delete the files from /var/cache/tt-rss/js/* first, or the
> > minifier won't be called again.
> 
> Thank you, Stefan.
> 
> I've attached a .debdiff that fixes jshrink and changes the default log
> destination to syslog (as this avoids the other bug). What do you think?
> Only fix the jshrink part? Do both?

Did you forgot to add the attachment? FWIW both changes are with me.

-- Sebastian


signature.asc
Description: PGP signature

Bug#884222: valabind: Fails to build with vala 0.38

[Sebastian Reichel]

On Tue, 30 Jan 2018 18:14:30 +0100 Rico Tzschichholz  wrote:
> On Mon, 22 Jan 2018 06:52:24 -0500 Jeremy Bicha  wrote:
> > https://salsa.debian.org/jbicha/valabind
> > 
> > Sebastian, could you take a look?
> > 
> 
> Afaics this looks good and should be uploaded asap.
> 
> This is the only bit which blocks the vala 0.38 introduction in testing.

I agree, based on a quick look. I'm currently too busy to take care
of it, though. Jeremy, could you upload your changes?

Thanks,

-- Sebastian


signature.asc
Description: PGP signature

Bug#884222: valabind: Fails to build with vala 0.38

[Sebastian Reichel]

Hi,

This has been fixed upstream, but the new bugfix release
requires vala 0.40. Reading the discussion between upstream
valabind and vala, it looks like vala 0.38 cannot be supported.

-- Sebastian


signature.asc
Description: PGP signature

Bug#840746: valac: Regression in DBus gio-2.0.vapi binding

[Sebastian Reichel]

Package: valac
Version: 0.34.0-1
Severity: serious
Tags: patch upstream
Justification: renders mdbus package completly useless
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=772902
Control: affects -1 mdbus2

Hi,

vala 0.34 has updated gio-2.0.vapi file, which removed
"array_null_terminated = true" annotation from a couple of DBus
related objects. This results in mdbus2 package being completly
useless, as it only sees empty arrays.

-- Sebastian

Bug#839128: Web UI doesn't work: "Cannot read property 'addOnLoad' of undefined"

[Sebastian Reichel]

Hi,

On Thu, Sep 29, 2016 at 11:02:02AM +0200, Andrey Rahmatullin wrote:
> Package: tt-rss
> Version: 16.8+git20160826+dfsg-3
> Severity: grave
> 
> After upgrading from 15.7+git20151123+dfsg-5 to 16.8+git20160826+dfsg-3 when
> I open the Web UI I get an error popup and the webpage stays at "Loading".
> 
> """
> Exception: TypeError: Cannot read property 'addOnLoad' of undefined
> Function: init()Ошибка будет зафиксирована в указанном логе.
> 
> Additional exception caught while trying to show the error dialog.
> 
> Exception: ReferenceError: dijit is not defined
> Function: exception_error()
> 
> The error will be reported to the configured log destination.
> """

I cannot reproduce this. Have you cleared any caches and made sure,
that your browser fetches newest javascript?

-- Sebastian


signature.asc
Description: PGP signature

Bug#838829: Try to add Generics declaration to class definition

[Sebastian Reichel]

Hi,

On Tue, Sep 27, 2016 at 06:36:12AM -0500, Daniel Espinosa wrote:
> As for bug:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=770449
> 
> Valac have started to check types in other places and if GitHub manual is
> used to check generic classes declaration, as for:
> 
> https://github.com/valadate-project/the-vala-manual/blob/master/en/generics-examples.md
> 
> then your example should be:
> 
> public abstract class basecl : Object {
>   public abstract void test(T parameter);
> }
> 
> public class inheritcl : basecl {
>   public override void test(T parameter) {
> stdout.printf("Just a test!\n");
>   }
> }
> 
> May you want to test this code and change this bug, as this may it is not,
> but a code update required due to recent additional checks in valac.

No. Your code also fails with valac 0.34.0. In vala 0.34.0 you can't
override generic methods. Note that it already has been fixed
upstream:

https://git.gnome.org/browse/vala/commit/?h=0.34=9e0e03f2ca48eeef4d16067cca21426b240cd5c5

vala 0.32.0 and vala 0.34.0 with that fix applied compiles my
testcode from above without any problems. Also the libfsoframework
no longer FTBFS.

-- Sebastian


signature.asc
Description: PGP signature

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

[Sebastian Reichel]

Hi,

On Mon, Sep 26, 2016 at 01:44:32AM +0200, Michael Biebl wrote:
> Am 26.09.2016 um 01:28 schrieb Sebastian Reichel:
> > I wonder if libvala-XY-dev should be named libvala-dev with the
> > next version increase, though. This should make binnmu based
> > transitions possible for valabind.
> 
> Would a Provides: libvala-dev be sufficient?

As long as it's guaranteed, that there is only one package providing
libvala-dev it might work. It would be a problem if libvala-0.34-dev
and libvala-0.36-dev (numbers are just examples) are both available
and providing libvala-dev. Then it's unclear which build-dependency
should be pulled.

That could be worked around by creating a transition-style
libvala-dev package, that depends on libvala-xy-dev.

> I think it makes some sense to include the API version in
> libvala-XY-dev. After all, the version is encoded in
> libvala-XY.pc and /usr/include/vala-XY.
> 
> Would we need to provide an unversioned libvala.pc as well?

No.

valabind checks which libvala-xy it has to build against
based on the valac version:

https://sources.debian.net/src/valabind/0.10.0-1/getvv/

valadoc has a list of supported libvala versions, that
it can build against:

https://sources.debian.net/src/valadoc/0.30.0~git20160518-1/configure.ac/#L83

-- Sebastian


signature.asc
Description: PGP signature

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

[Sebastian Reichel]

Hi,

On Mon, Sep 26, 2016 at 12:34:55AM +0200, Michael Biebl wrote:
> Thank you for fixing valadoc and valabind so quickly

You are welcome.

> and sorry for the short advance notice.

No harm done. I wonder if libvala-XY-dev should be named libvala-dev
with the next version increase, though. This should make binnmu
based transitions possible for valabind.

valadoc needs code adjustments for each vala release, but I can
specify Build-Depends: libvala-dev (< max-version-supported+1~).
So if I upload a valadoc release with 0.36 support before valac
is in the archive valadoc could also be binnmu'd once vala 0.36
arrives.

> I didn't expect to get a green light on the libvala transition so
> quickly. So kudos to the release team here as well.

-- Sebastian


signature.asc
Description: PGP signature

Bug#838829: valac: Feature Regression in vala 0.34

[Sebastian Reichel]

Package: valac
Version: 0.34.0-1
Severity: serious
Tags: upstream
Justification: upstream regression causes FTBFS in other package(s)

Hi,

valac no longer supports abstract functions with generics. This
construct is used by the freesmartphone.org stack, which is
packaged for Debian and FTBFS with valac > 0.34.0-1. This has
been reported in Debian Bug #838705.

The below standalone testcase, which compiles warning free
in vala 0.32, no longer works in vala 0.34 and demonstrates the
problem.

As far as I can see the regression has been introduced by the
following change:
https://mail.gnome.org/archives/commits-list/2016-July/msg02876.html

-
public abstract class basecl : Object {
public abstract void test(T parameter);
}

public class inheritcl : basecl {
public override void test(T parameter) {
stdout.printf("Just a test!\n");
}
}

int main(string[] args) {
var obj = new inheritcl();
obj.test("test");
return 0;
}
-

-- Sebastian

Bug#838705: this is a bug in libfsoframework

[Sebastian Reichel]

reassign 838705 libfsoframework 0.12.0-7
affects 838705 + fso-datad fso-audiod fso-deviced
thanks

Hi,

libfsoframework no longer builds with vala 0.34 due to the
following newly introduced error:

https://mail.gnome.org/archives/commits-list/2016-July/msg02876.html

The code in libfsoframework looks correct though. I think
it's a regression in the vala compiler.

-- Sebastian


signature.asc
Description: PGP signature

Bug#819540: valadoc: diff for NMU version 0.23.2~git20150422-3.1

[Sebastian Reichel]

Hi,

On Sun, May 29, 2016 at 12:06:32PM +0200, Tobias Frost wrote:
> Control: tags 819540 + patch
> Control: tags 819540 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for valadoc (versioned as 0.23.2~git20150422-3.1) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer.
> 
> The cherry-picked patch is this one:
> https://git.gnome.org/browse/valadoc/patch/?id=5863c16c6585be9e29621b1c061817fc8b4ef6d3
> 
> Regards.

Looks fine to me, feel free to remove the delay.

-- Sebastian


signature.asc
Description: PGP signature

Bug#799316: aegisub: Not binNMU safe - uses link-doc between arch:any and arch:all packages

[Sebastian Reichel]

Hi,

On Thu, Sep 17, 2015 at 10:51:43PM +0200, Niels Thykier wrote:
> [...]

Thanks for bringing this problem up.

> On 2015-09-17 22:37, Santiago Vila wrote:
> >> [...]

Also thanks for bringing this up on debian-devel, I would have
done so otherwise :)

> As for binNMUs: Regardless of what happens, they will not disappear over
> night.  As such, the bug against aegisub remains.

Right. I will prepare a fix. Probably a lintian test should be
written, that checks if 'dh_installdocs --link-doc' is used
to generate a :all -> :any symlink. I doubt, that aegisub is
the only package with this setup.

-- Sebastian


signature.asc
Description: Digital signature

Bug#766114: [pkg-fso-maint] Bug#766114: Aw: Re: Bug#766114: Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf

[Sebastian Reichel]

Hi,

Sorry for the long time to answer, but I had no time to dig into
this.

On Thu, Nov 06, 2014 at 10:40:39PM +0100, hikaru.deb...@web.de wrote:
  Hmm, it's a strange thing. If I recompile fso-deviced eveything works as 
  expected.
 
 But you can reproduce the problem with the packages as they are in
 Debian right now?
 I just rebuild the Jessie package (armhf) and still get the same
 startup error (as I expected).

I can verify, that the binary is broken (and thus the init script
fails, too).

  It seems, the generated .c files from vala-sources are broken.
 
 Unfortunately this is above my skills. Please let me know if I can be of any
 further assistance in solving this!

starting the binary without the init script tells us:

$ sudo fsodeviced
*** stack smashing detected ***: fsodeviced terminated
[...]

Which means, that there is a stack based buffer overflow. I could
trace the problem to the Kernel.InputDevice constructor method,
which is kernel_input_device_construct() in the plugin.c

I guess Rico does not use the -fstack-protector-strong gcc
parameter, so in his build setup the binary does not verify if the
stack has been corrupted.

Stuff I tried so far to find the stack problem:

* comparing the generated C code from current vala with the
  pregenerated C code from FSO:
  problem has not been introduced by newer vala!
* reading through the C code to find the stack problem:
  could not find it!
* runing binary without -fstack-protector-strong in valgrind:
  nothing found in the Kernel.InputDevice constructor
* building without -O2:
  works
* build using clang-3.5 without changing CFLAGS/LDFLAGS
  still broken
* build using clang-3.5 + address sanitizer:
  problem gone :( [it would have traced the error]

So I think I will enable -fno-stack-protector in the package
for now.

-- Sebastian


signature.asc
Description: Digital signature

Bug#763219: zeitgeist needs valadoc with vala 0.26 support.

[Sebastian Reichel]

On Fri, Oct 10, 2014 at 12:54:19PM +0200, Andreas Henriksson wrote:
 On Fri, Oct 10, 2014 at 03:37:00AM +0200, Sebastian Reichel wrote:
  I just uploaded valadoc 0.23.2~git20140902-2, which should include
  support for vala 0.26.
 
 Thanks for the quick upload! Would also appreciate if you'd drop
 the vala 0.24 support so we can get rid of the old vala.
 (The two remaining users are valadoc and valabind. And if both can
 drop vala 0.24 dependency before the freeze we can probably get
 down to shipping only 1 vala with jessie, instead of the current 3.)

I just uploaded valadoc with dropped 0.24 support. For valabind a
snapshot from the repository is needed for 0.26 support (there is no
build dependency on vala 0.24, it just FTBFS with valac  0.24).

-- Sebastian


signature.asc
Description: Digital signature

Bug#763219: zeitgeist needs valadoc with vala 0.26 support.

[Sebastian Reichel]

Hi Andreas,

On Thu, Oct 09, 2014 at 09:55:14PM +0200, Andreas Henriksson wrote:
 For the record I just verified that this build failure goes away
 if using a (locally built) valadoc with support for vala 0.26.
 
 (The problem here is that zeitgeist uses (the default) vala 0.26 to
 build itself and then tries to use valadoc on top of that, which still
 only supports vala 0.24. Changing this on the valadoc side is trivial
 and preferred. Just s/0.24/0.26/ in debian/control.)

I just uploaded valadoc 0.23.2~git20140902-2, which should include
support for vala 0.26.

-- Sebastian


signature.asc
Description: Digital signature

Bug#739385: aegisub: FTBFS on armel: std::future is broken

[Sebastian Reichel]

Source: aegisub
Version: 3.1.2-1
Severity: serious
Justification: fails to build from source

aegisub fails to build from source on armel, but built in the past:

g++ -MD -MP -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra 
-Wno-unused-parameter -Wno-long-long -fno-strict-aliasing -pipe -g -std=c++11 
-Wno-c++11-narrowing -Wno-unused-local-typedefs -O3 -I. -I.. -Iinclude 
-I../libaegisub/include -I../build -DAEGISUB -pthread  
-I/usr/include/arm-linux-gnueabi   -D__STDC_FORMAT_MACROS 
-I/usr/lib/arm-linux-gnueabi/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -include agi_pre.h  -c 
-o audio_timing_karaoke.o audio_timing_karaoke.cpp
audio_timing_karaoke.cpp: In member function 'void 
AudioTimingControllerKaraoke::AnnounceChanges(int)':
audio_timing_karaoke.cpp:413:13: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
  if (syl == cur_syl || syl == cur_syl + 1) {
 ^
audio_timing_karaoke.cpp:413:41: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
  if (syl == cur_syl || syl == cur_syl + 1) {
 ^
At global scope:
cc1plus: warning: unrecognized command line option -Wno-c++11-narrowing 
[enabled by default]
g++ -MD -MP -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra 
-Wno-unused-parameter -Wno-long-long -fno-strict-aliasing -pipe -g -std=c++11 
-Wno-c++11-narrowing -Wno-unused-local-typedefs -O3 -I. -I.. -Iinclude 
-I../libaegisub/include -I../build -DAEGISUB -pthread  
-I/usr/include/arm-linux-gnueabi   -D__STDC_FORMAT_MACROS 
-I/usr/lib/arm-linux-gnueabi/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -include agi_pre.h  
-I/usr/include/freetype2   -c -o auto4_base.o auto4_base.cpp
auto4_base.cpp: In member function 'virtual void 
Automation4::AutoloadScriptManager::Reload()':
auto4_base.cpp:354:6: error: invalid use of incomplete type 'class 
std::futurestd::unique_ptrAutomation4::Script '
 }));
  ^
In file included from auto4_base.cpp:59:0:
/usr/include/c++/4.8/future:113:11: error: declaration of 'class 
std::futurestd::unique_ptrAutomation4::Script '
 class future;
   ^
auto4_base.cpp:359:19: error: invalid use of incomplete type 'class 
std::futurestd::unique_ptrAutomation4::Script '
auto s = future.get();
   ^
In file included from auto4_base.cpp:59:0:
/usr/include/c++/4.8/future:113:11: error: declaration of 'class 
std::futurestd::unique_ptrAutomation4::Script '
 class future;
   ^
In file included from /usr/include/c++/4.8/bits/stl_algobase.h:67:0,
 from /usr/include/c++/4.8/algorithm:61,
 from ./../libaegisub/lagi_pre.h:38,
 from ./agi_pre.h:54,
 from command-line:0:
/usr/include/c++/4.8/bits/stl_iterator.h: In instantiation of 
'__gnu_cxx::__normal_iterator_Iterator, _Container 
__gnu_cxx::__normal_iterator_Iterator, _Container::operator++() [with 
_Iterator = std::futurestd::unique_ptrAutomation4::Script *; _Container = 
std::vectorstd::futurestd::unique_ptrAutomation4::Script  ]':
auto4_base.cpp:358:23:   required from here
/usr/include/c++/4.8/bits/stl_iterator.h:748:2: error: cannot increment a 
pointer to incomplete type 'std::futurestd::unique_ptrAutomation4::Script '
  ++_M_current;
  ^
In file included from /usr/include/c++/4.8/vector:64:0,
 from /usr/include/c++/4.8/bits/random.h:34,
 from /usr/include/c++/4.8/random:50,
 from /usr/include/c++/4.8/bits/stl_algo.h:65,
 from /usr/include/c++/4.8/algorithm:62,
 from ./../libaegisub/lagi_pre.h:38,
 from ./agi_pre.h:54,
 from command-line:0:
/usr/include/c++/4.8/bits/stl_vector.h: In instantiation of 
'std::_Vector_base_Tp, _Alloc::~_Vector_base() [with _Tp = 
std::futurestd::unique_ptrAutomation4::Script ; _Alloc = 
std::allocatorstd::futurestd::unique_ptrAutomation4::Script  ]':
/usr/include/c++/4.8/bits/stl_vector.h:249:15:   required from 
'std::vector_Tp, _Alloc::vector() [with _Tp = 
std::futurestd::unique_ptrAutomation4::Script ; _Alloc = 
std::allocatorstd::futurestd::unique_ptrAutomation4::Script  ]'
auto4_base.cpp:344:53:   required from here
/usr/include/c++/4.8/bits/stl_vector.h:161:9: error: invalid use of incomplete 
type 'class std::futurestd::unique_ptrAutomation4::Script '
 - this-_M_impl._M_start); }
 ^
In file included from auto4_base.cpp:59:0:
/usr/include/c++/4.8/future:113:11: error: declaration of 'class 
std::futurestd::unique_ptrAutomation4::Script '
 class future;
   ^
In file included from /usr/include/c++/4.8/bits/stl_tempbuf.h:60:0,
 from 

Bug#732853: radare2: FTBFS on various archs

[Sebastian Reichel]

On Sat, Dec 28, 2013 at 12:43:54AM -0800, David Martínez Moreno wrote:
 On 12/27/13 5:20 AM, Sebastian Reichel wrote:
  On Fri, Dec 27, 2013 at 04:07:39AM -0800, David Martínez Moreno wrote:
  gcc rabin2.o -L.. -o rabin2 -Wl,-z,relro
  -L/«PKGBUILDDIR»/libr/lib -L/«PKGBUILDDIR»/libr/magic
  -L/«PKGBUILDDIR»/libr/core -L/«PKGBUILDDIR»/libr/db
  -L/«PKGBUILDDIR»/libr/bin -L/«PKGBUILDDIR»/libr/egg
  -L/«PKGBUILDDIR»/libr/cons -L/«PKGBUILDDIR»/libr/config
  -L/«PKGBUILDDIR»/libr/io -L/«PKGBUILDDIR»/libr/cmd
  -L/«PKGBUILDDIR»/libr/flags -L/«PKGBUILDDIR»/libr/asm
  -L/«PKGBUILDDIR»/libr/debug -L/«PKGBUILDDIR»/libr/hash
  -L/«PKGBUILDDIR»/libr/lang -L/«PKGBUILDDIR»/libr/anal
  -L/«PKGBUILDDIR»/libr/parse -L/«PKGBUILDDIR»/libr/bp
  -L/«PKGBUILDDIR»/libr/reg -L/«PKGBUILDDIR»/libr/search
  -L/«PKGBUILDDIR»/libr/syscall -L/«PKGBUILDDIR»/libr/sign
  -L/«PKGBUILDDIR»/libr/diff -L/«PKGBUILDDIR»/libr/socket
  -L/«PKGBUILDDIR»/libr/fs -L/«PKGBUILDDIR»/libr/magic
  -L/«PKGBUILDDIR»/libr/util -lr_lib -lr_magic -lr_core -lr_db
  -lr_bin -lr_egg -lr_cons -lr_config -lr_io -lr_cmd -lr_flags
  -lr_asm -lr_debug -lr_hash -lr_lang -lr_anal -lr_parse -lr_bp
  -lr_reg -lr_s
  earch -lr_syscall -lr_sign -lr_diff -lr_socket -lr_fs -lr_magic
  -lr_util -fPIC -ldl
  /«PKGBUILDDIR»/libr/debug/libr_debug.so: undefined reference to `strlcat'
  /«PKGBUILDDIR»/libr/debug/libr_debug.so: undefined reference to `strlcpy'
  collect2: error: ld returned 1 exit status
 
 I have no idea yet on how to fix this.
  
  This seems to be a bug in kfreebsd's libc. The irony is, that both methods
  origin from the BSD world.
  
  I tried the following testcase on falla.debian.org:
  
  --
  falla% cat test.c
  #include stdlib.h
  #include string.h
  
  int main(int argc, char **argv) {
  char *foo = this is a test;
  char *bar = malloc(100);
  strlcpy(bar, foo, 5);
  return 0;
  }
  falla% gcc test.c
  /tmp/ccp6Q0It.o: In function `main':
  test.c:(.text+0x3e): undefined reference to `strlcpy'
  collect2: error: ld returned 1 exit status
  --
 
   Have you maybe opened a bug for the KFreeBSD porters?  Have you tried 
 if libbsd
 can help us here?

No. I just did a little testing if this is broken in the r2
buildsystem or if I can reproduce it without the r2 bits.

-- Sebastian


signature.asc
Description: Digital signature

Bug#732853: radare2: FTBFS on various archs

[Sebastian Reichel]

On Fri, Dec 27, 2013 at 04:07:39AM -0800, David Martínez Moreno wrote:
  gcc rabin2.o -L.. -o rabin2 -Wl,-z,relro
  -L/«PKGBUILDDIR»/libr/lib -L/«PKGBUILDDIR»/libr/magic
  -L/«PKGBUILDDIR»/libr/core -L/«PKGBUILDDIR»/libr/db
  -L/«PKGBUILDDIR»/libr/bin -L/«PKGBUILDDIR»/libr/egg
  -L/«PKGBUILDDIR»/libr/cons -L/«PKGBUILDDIR»/libr/config
  -L/«PKGBUILDDIR»/libr/io -L/«PKGBUILDDIR»/libr/cmd
  -L/«PKGBUILDDIR»/libr/flags -L/«PKGBUILDDIR»/libr/asm
  -L/«PKGBUILDDIR»/libr/debug -L/«PKGBUILDDIR»/libr/hash
  -L/«PKGBUILDDIR»/libr/lang -L/«PKGBUILDDIR»/libr/anal
  -L/«PKGBUILDDIR»/libr/parse -L/«PKGBUILDDIR»/libr/bp
  -L/«PKGBUILDDIR»/libr/reg -L/«PKGBUILDDIR»/libr/search
  -L/«PKGBUILDDIR»/libr/syscall -L/«PKGBUILDDIR»/libr/sign
  -L/«PKGBUILDDIR»/libr/diff -L/«PKGBUILDDIR»/libr/socket
  -L/«PKGBUILDDIR»/libr/fs -L/«PKGBUILDDIR»/libr/magic
  -L/«PKGBUILDDIR»/libr/util -lr_lib -lr_magic -lr_core -lr_db
  -lr_bin -lr_egg -lr_cons -lr_config -lr_io -lr_cmd -lr_flags
  -lr_asm -lr_debug -lr_hash -lr_lang -lr_anal -lr_parse -lr_bp
  -lr_reg -lr_s
 earch -lr_syscall -lr_sign -lr_diff -lr_socket -lr_fs -lr_magic
 -lr_util -fPIC -ldl
  /«PKGBUILDDIR»/libr/debug/libr_debug.so: undefined reference to `strlcat'
  /«PKGBUILDDIR»/libr/debug/libr_debug.so: undefined reference to `strlcpy'
  collect2: error: ld returned 1 exit status
 
   I have no idea yet on how to fix this.

This seems to be a bug in kfreebsd's libc. The irony is, that both methods
origin from the BSD world.

I tried the following testcase on falla.debian.org:

--
falla% cat test.c
#include stdlib.h
#include string.h

int main(int argc, char **argv) {
char *foo = this is a test;
char *bar = malloc(100);
strlcpy(bar, foo, 5);
return 0;
}
falla% gcc test.c
/tmp/ccp6Q0It.o: In function `main':
test.c:(.text+0x3e): undefined reference to `strlcpy'
collect2: error: ld returned 1 exit status
--

-- Sebastian


signature.asc
Description: Digital signature

Bug#726721: radare2: fails to upgrade

[Sebastian Reichel]

On Fri, Oct 18, 2013 at 01:11:39PM +0200, Hilko Bengen wrote:
 Package: libradare2-0.9.4
 Version: 0.9.4-1
 Severity: serious
 
 While trying to upgrade my unstable/amd64 (+i386) system, the following
 error occured:
 
 Unpacking libradare2-0.9.4:amd64 (from 
 .../libradare2-0.9.4_0.9.4-1_amd64.deb) ...
 dpkg: error processing 
 /var/cache/apt/archives/libradare2-0.9.4_0.9.4-1_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libr_search.so.0.9.4', which 
 is also in package libradare2-0.9:amd64 0.9.4-1

 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
 Unpacking libradare2-0.9.4:i386 (from .../libradare2-0.9.4_0.9.4-1_i386.deb) 
 ...
 dpkg: error processing 
 /var/cache/apt/archives/libradare2-0.9.4_0.9.4-1_i386.deb (--unpack):
  trying to overwrite '/usr/lib/i386-linux-gnu/libr_lang.so.0.9.4', which is 
 also in package libradare2-0.9:i386 0.9.4-1
 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
 
 Cheers,
 -Hilko

Where did you get libradare2-0.9:i386 (0.9.4-1) and
libradare2-0.9:amd64 (0.9.4-1)? This package version
never existed in Debian.

-- Sebastian


signature.asc
Description: Digital signature

Bug#707439: [pkg-fso-maint] Bug#707439: libphone-ui-shr: diff for NMU version 0.1+git20110827-3.1

[Sebastian Reichel]

Hi,

On Fri, Sep 13, 2013 at 05:58:00PM +0200, Luk Claes wrote:
 I've prepared an NMU for libphone-ui-shr (versioned as 0.1+git20110827-3.1) 
 and
 uploaded it to DELAYED/02. Please feel free to tell me if I
 should delay it longer.

Looks fine to me. Thanks.

-- Sebastian


signature.asc
Description: Digital signature

Bug#717268: [pkg-fso-maint] Bug#717268: libfsotransport-dbg is not installable either

[Sebastian Reichel]

On Thu, Jul 18, 2013 at 06:39:28PM +0200, Ralf Treinen wrote:
 exactly the same holds for the binary package libfsotransport-dbg.
 
 -Ralf.

Will be fixed by removal of libfsotransport source package and its
generated binary packages, once the reverse dependencies are updated.

-- Sebastian


signature.asc
Description: Digital signature

Bug#695272: [pkg-fso-maint] Bug#695272: libphone-utils0: harmful postrm purge action in M-A:same package

[Sebastian Reichel]

Hi,

On Mon, Dec 10, 2012 at 11:37:54PM +0100, Dominik George wrote:
  Is there a particular use case for such support, other than
  because we can? If not, then not having multi-arch support in
  wheezy doesn't seem a huge issue; ymmv, obviously.

The package is more or less smartphone exclusive, so basically
only interesting for ARM. Multi-Arch is helpful for armel vs armhf
vs arm64. I don't think this is important for wheezy, though.

Even more interesting is support for crosscompilers etc., but
the fso/shr related packages do not yet enable M-A for the -dev
packages, so obviously it's also irrelevant for wheezy.

= IMHO removing M-A is not a huge issue

 I can prepare another version for wheezy incorporating this.

preparing a upload for testing was what I indented to do, too.
I planed to check how to fix this without removing M-A support,
though. It should be possible to do something like this in the
postrm script:

if [ !package_is_still_installed_for_another_arch ] ; then
remove files
fi

 What about version numbering and such, now -2 has been uploaded?

It should be something like -1+wheezy1. This makes the version
bigger than the one currently in wheezy, but smaller than the one
currently in unstable.

-- Sebastian


signature.asc
Description: Digital signature

Bug#687869: [pkg-fso-maint] Bug#687869: libgsm0710: diff for NMU version 1.2.2-1.1

[Sebastian Reichel]

On Sat, Sep 22, 2012 at 09:22:53AM +0200, Salvatore Bonaccorso wrote:
 The attached patch should fix this issue. I'm only attaching the patch
 but have not done any further action. Sebastian do you have time to do
 the upload?

Thanks for the patch. I just uploaded the change as 1.2.2-2.

-- Sebastian


signature.asc
Description: Digital signature

Bug#675407: xserver-xorg-video-openchrome: openchrome relink against new xserver results in null pointer dereference

[Sebastian Reichel]

Package: xserver-xorg-video-openchrome
Version: 1:0.2.904+svn1050-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi,

It's not enough to rebuild openchrome against the new X-Server,
since the new X-Server does not run vgaHWSetStdFuncs(hwp) anymore:

http://cgit.freedesktop.org/xorg/xserver/commit/?id=4bd6579188e718654c35f95623fd4772f9e0ef06

Please update the driver to support the X-Server's ABI change.

-- Sebastian



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

Bug#673666: bug in pygobject

[Sebastian Reichel]

reassign 673666 python-gobject 3.2.0-2
forcemerge 667057 673666
thanks

Hi,

This is actually a bug in the python gtk3 binding, which has
already been fixed in unstable. Please make sure to use
python-gobject (= 3.2.1-1).

-- Sebastian


signature.asc
Description: Digital signature

Bug#672989: [pkg-fso-maint] Bug#672989: Multiple security issues

[Sebastian Reichel]

On Tue, May 15, 2012 at 09:39:06PM +0200, Julien Cristau wrote:
 On Tue, May 15, 2012 at 11:44:17 +0200, Moritz Muehlenhoff wrote:
 
  Package: connman
  Severity: grave
  Tags: security
  
  
  CVE-2012-2320:  Conman doesn't check for the origin of netlink messages 
  (from
  https://bugzilla.novell.com/show_bug.cgi?id=715172#c4)
  http://git.kernel.org/?p=network/connman/connman.git;a=commit;h=c1b968984212b46bea1330f5ae029507b9bfded9
  http://git.kernel.org/?p=network/connman/connman.git;a=commit;h=b0ec6eb4466acc57a9ea8be52c17b674b6ea0618
  
  CVE-2012-2321: Check hostname validity prior setting the hostname in 
  loopback plug-in: (from
  https://bugzilla.novell.com/show_bug.cgi?id=715172#c4)
  http://git.kernel.org/?p=network/connman/connman.git;a=commit;h=26ace5c59f790bce0f1988b88874c6f2c480fd5a
  http://git.kernel.org/?p=network/connman/connman.git;a=commit;h=a5f540db7354b76bcabd0a05d8eb8ba2bff4e911
  
  CVE-2012-2322: DHCPv6 option parsing vulnerable to DoS (endless loop): (from
  https://bugzilla.novell.com/show_bug.cgi?id=715172#c9)
  http://lists.connman.net/pipermail/connman/2012-May/009473.html
  
  Since this package is effectively unmaintained (no upload later than 2010 
  and wy behind
  upstream I suggest to simply remove it for Wheezy?)
  
 $ dak rm -Rn -s testing connman
 [...]
 
 Checking reverse dependencies...
 # Broken Build-Depends:
 fso-gsmd: connman-dev
 
 Dependency problem found.
 
 Sebastian, fso folks, is there a way to remove this build-dependency on
 connman?

Connman support is actually already disabled in fso-gsmd, since
fso-gsmd needs at least connman 0.68 and Debian has only 0.48.
Thus the build dependency can simply be removed.

Can this wait another week? Next week will be a new upstream
release of all fso components, which we plan to upload asap
to be in time for wheezy.

-- Sebastian


signature.asc
Description: Digital signature

Bug#671897: xf86-video-omap: current binary segfaults, please update to fixed 0.3.0 release

[Sebastian Reichel]

Source: xf86-video-omap
Version: 0.0.1~git20110717-1
Severity: grave
Justification: renders package unusable

The xf86-video-omap version, which is currently available through Debian
experimental, produces the following segfault:

Program received signal SIGSEGV, Segmentation fault.
xb6ef2d16 in pixman_fill1_line (v=1, width=optimized out, offs=0, 
dst=optimized out) at ../../pixman/pixman-fast-path.c:
2011../../pixman/pixman-fast-path.c: No such file or directory.
(gdb) bt
#0  0xb6ef2d16 in pixman_fill1_line (v=1, width=optimized out, offs=0, 
dst=optimized out) at ../../pixman/pixman-fast-path.c:2011
#1  pixman_fill1 (xor=4294967295, height=optimized out, width=16, y=0, x=0, 
stride=optimized out, bits=optimized out) at 
../../pixman/pixman-fast-path.c:2033
#2  fast_path_fill (imp=optimized out, bits=optimized out, 
stride=optimized out, bpp=optimized out, x=0, y=0, width=16, height=16, 
xor=4294967295)
at ../../pixman/pixman-fast-path.c:2134
#3  0xb6ef3bd8 in _pixman_implementation_fill (xor=4294967295, height=16, 
width=16, y=0, x=0, bpp=optimized out, stride=optimized out, 
bits=optimized out,
imp=optimized out) at ../../pixman/pixman-implementation.c:176
#4  delegate_fill (imp=optimized out, bits=optimized out, stride=optimized 
out, bpp=optimized out, x=0, y=0, width=16, height=16, xor=4294967295)
at ../../pixman/pixman-implementation.c:62
#5  0xb6ef3d0a in _pixman_implementation_fill (imp=optimized out, 
bits=optimized out, stride=optimized out, bpp=optimized out, x=0, y=0, 
width=16,
height=16, xor=4294967295) at ../../pixman/pixman-implementation.c:176
#6  0xb6ef3bd8 in _pixman_implementation_fill (xor=4294967295, height=16, 
width=16, y=0, x=0, bpp=optimized out, stride=optimized out, 
bits=optimized out,
imp=optimized out) at ../../pixman/pixman-implementation.c:176
#7  delegate_fill (imp=optimized out, bits=optimized out, stride=optimized 
out, bpp=optimized out, x=0, y=0, width=16, height=16, xor=4294967295)
at ../../pixman/pixman-implementation.c:62
#8  0xb6ef3d0a in _pixman_implementation_fill (imp=optimized out, 
bits=optimized out, stride=optimized out, bpp=optimized out, x=0, y=0, 
width=16,
height=16, xor=4294967295) at ../../pixman/pixman-implementation.c:176
#9  0xb6ebba96 in pixman_fill (bits=0x0, stride=0, bpp=1, x=optimized out, 
y=0, width=16, height=16, xor=4294967295) at ../../pixman/pixman.c:772
#10 0xb6b30354 in fbFill (pDrawable=optimized out, pGC=0x2a1830f8, 
x=optimized out, y=0, width=16, height=16) at ../../fb/fbfill.c:48
#11 0xb6b30808 in fbPolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nrect=optimized out, prect=optimized out) at ../../fb/fbfillrect.c:77
#12 0xb6b4c0ee in ExaCheckPolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nrect=1, prect=optimized out) at ../../exa/exa_unaccel.c:311
#13 0xb6b47e1e in exaPolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nrect=1, prect=0xbefff66c) at ../../exa/exa_accel.c:852
#14 0x2a0b71d0 in damagePolyFillRect (pDrawable=0x2a183578, pGC=0x2a1830f8, 
nRects=1, pRects=0xbefff66c) at ../../../miext/damage/damage.c:1309
#15 0x2a03ec32 in CreateDefaultStipple (screenNum=optimized out) at 
../../dix/gc.c:938
#16 0x2a028206 in main (argc=3, argv=0xbefff854, envp=optimized out) at 
../../dix/main.c:220

This problem has been fixed in the latest release (0.3.0). xf86-video-omap 0.3.0
requires the OMAP API inside of libdrm, though.

-- Sebastian



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

Bug#666874: tt-rss does not work with libjs-dojo-* anymore (since 1.7.2+dfsg-1)

[Sebastian Reichel]

Package: tt-rss
Version: 1.5.10+dfsg-1
Severity: grave
Justification: renders package unusable

tt-rss does not work anymore after upgrading libjs-dojo-* to
1.7.2+dfsg-1.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-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



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

Bug#665902: [pkg-fso-maint] Bug#665902: Bug#665902: fso-config-gta*: uninstallable in sid

[Sebastian Reichel]

On Thu, Mar 29, 2012 at 11:05:07PM +0100, Adam D. Barratt wrote:
 On Thu, 2012-03-29 at 23:52 +0200, arne anka wrote:
  solution: those are deprecated, use fso-gta0[12]
  i assume those packages will disappear in a near future.
 
 tbh, I don't want to use them.  I want them to be fixed - or removed,
 with a release management hat on. :-)  (and at the very least to not be
 in wheezy in a broken state)

I requested the removal of the src package providing them yesterday,
see Debian Bug #666039 [0].

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

-- Sebastian


signature.asc
Description: Digital signature

Bug#654497: radare: diff for NMU version 1:1.5.2-4.1

[Sebastian Reichel]

On Fri, Jan 20, 2012 at 09:48:45PM +0100, Reinhard Tartler wrote:
 I've prepared an NMU for radare (versioned as 1:1.5.2-4.1) and
 uploaded it to DELAYED/3. Please feel free to tell me if I
 should delay it longer.

Thanks for fixing this :) I added the diff to the git [0]. Feel
free to upload it directly.

[0] 
http://anonscm.debian.org/gitweb/?p=collab-maint/radare.git;a=commit;h=3f3cd170440a2f1ad30457e4cfec4e4db2d1f48b

-- Sebastian


signature.asc
Description: Digital signature

Bug#647992: chromium 14 broken with libnss3-1d from sid

[Sebastian Reichel]

Hi,

I noticed, that Chromium 14 has the same problem when libnss3-1d
from sid (3.13.1.with.ckbi.1.88-1) is used (at least the symptoms
are the same). Installing libnss3-1d from testing (3.12.11-3) it
works as expected.

Chromium 15 doesn't work with either of them, though.

-- Sebastian


signature.asc
Description: Digital signature

Bug#648821: chromium broken

[Sebastian Reichel]

Package: libnss3-1d
Version: 3.13.1.with.ckbi.1.88-1
Severity: critical

Hi,

This release breaks chromium 14 from Debian testing. It crashes
with the same symptoms described in Debian Bug #647992 [0].
Installing libnss3-1d from testing (3.12.11-3) fixes the issue.

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647992

-- Sebastian



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

Bug#648821: chromium broken

[Sebastian Reichel]

On Tue, Nov 15, 2011 at 02:46:37PM +0100, Mike Hommey wrote:
 On Tue, Nov 15, 2011 at 01:45:29PM +0100, Sebastian Reichel wrote:
  Package: libnss3-1d
  Version: 3.13.1.with.ckbi.1.88-1
  Severity: critical
  
  Hi,
  
  This release breaks chromium 14 from Debian testing. It crashes
  with the same symptoms described in Debian Bug #647992 [0].
  Installing libnss3-1d from testing (3.12.11-3) fixes the issue.
  
  [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647992
 
 I doesn't crash here. Can you get a backtrace?

(gdb) bt
#0  0x in ?? ()
#1  0x75e62491 in BalloonViewHost::UpdateActualSize 
(this=0x7942fb60, new_size=...) at 
chrome/browser/ui/gtk/notifications/balloon_view_host_gtk.cc:22
#2  0x75e62241 in BalloonViewImpl::AnimationProgressed 
(this=0x78d54d00, animation=0x7891a200) at 
chrome/browser/ui/gtk/notifications/balloon_view_gtk.cc:205
#3  0x7618cde7 in ui::LinearAnimation::Step (this=0x7891a200, 
time_now=optimized out) at ui/base/animation/linear_animation.cc:76
#4  0x7618cac5 in ui::AnimationContainer::Run (this=0x7857dde0) at 
ui/base/animation/animation_container.cc:76
#5  0x760aeaae in (anonymous namespace)::TaskClosureAdapter::Run 
(this=0x792f3b60) at base/message_loop.cc:104
#6  0x760af506 in Run (this=0x7fffb5f0) at ./base/callback.h:265
#7  MessageLoop::RunTask (this=0x783c6c00, pending_task=...) at 
base/message_loop.cc:484
#8  0x760b3aa3 in MessageLoop::DeferOrRunPendingTask 
(this=0x783c6c00, pending_task=...) at base/message_loop.cc:502
#9  0x760b3e5d in DoDelayedWork (next_delayed_work_time=0x7839e720, 
this=0x783c6c00) at base/message_loop.cc:731
#10 MessageLoop::DoDelayedWork (this=0x783c6c00, 
next_delayed_work_time=0x7839e720) at base/message_loop.cc:703
#11 0x760e60f2 in base::MessagePumpGlib::RunWithDispatcher 
(this=0x7839e700, delegate=optimized out, dispatcher=optimized out) at 
base/message_pump_glib.cc:215
#12 0x760b2ce5 in MessageLoop::RunInternal (this=0x783c6c00) at 
base/message_loop.cc:451
#13 0x760b2dcc in RunHandler (this=optimized out) at 
base/message_loop.cc:424
#14 MessageLoopForUI::Run (this=optimized out, dispatcher=optimized out) at 
base/message_loop.cc:834
#15 0x757cb112 in RunUIMessageLoop (browser_process=optimized out) at 
chrome/browser/browser_main.cc:708
#16 BrowserMain (parameters=...) at chrome/browser/browser_main.cc:2070
#17 0x757baee9 in RunNamedProcessTypeMain (main_function_params=..., 
process_type=...) at chrome/app/chrome_main.cc:552
#18 ChromeMain (argc=optimized out, argv=optimized out) at 
chrome/app/chrome_main.cc:895
#19 0x757bbc09 in main (argc=2, argv=0x7fffe438) at 
chrome/app/chrome_exe_main_gtk.cc:46

-- Sebastian


signature.asc
Description: Digital signature

Bug#648821: chromium broken

[Sebastian Reichel]

On Tue, Nov 15, 2011 at 05:18:23PM +0100, Mike Hommey wrote:
 On Tue, Nov 15, 2011 at 03:23:18PM +0100, Sebastian Reichel wrote:
  On Tue, Nov 15, 2011 at 02:46:37PM +0100, Mike Hommey wrote:
   On Tue, Nov 15, 2011 at 01:45:29PM +0100, Sebastian Reichel wrote:
Package: libnss3-1d
Version: 3.13.1.with.ckbi.1.88-1
Severity: critical

Hi,

This release breaks chromium 14 from Debian testing. It crashes
with the same symptoms described in Debian Bug #647992 [0].
Installing libnss3-1d from testing (3.12.11-3) fixes the issue.

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647992
   
   I doesn't crash here. Can you get a backtrace?
  
  (gdb) bt
  #0  0x in ?? ()
  #1  0x75e62491 in BalloonViewHost::UpdateActualSize 
  (this=0x7942fb60, new_size=...) at 
  chrome/browser/ui/gtk/notifications/balloon_view_host_gtk.cc:22
  #2  0x75e62241 in BalloonViewImpl::AnimationProgressed 
  (this=0x78d54d00, animation=0x7891a200) at 
  chrome/browser/ui/gtk/notifications/balloon_view_gtk.cc:205
  #3  0x7618cde7 in ui::LinearAnimation::Step (this=0x7891a200, 
  time_now=optimized out) at ui/base/animation/linear_animation.cc:76
  #4  0x7618cac5 in ui::AnimationContainer::Run (this=0x7857dde0) 
  at ui/base/animation/animation_container.cc:76
  #5  0x760aeaae in (anonymous namespace)::TaskClosureAdapter::Run 
  (this=0x792f3b60) at base/message_loop.cc:104
  #6  0x760af506 in Run (this=0x7fffb5f0) at ./base/callback.h:265
  #7  MessageLoop::RunTask (this=0x783c6c00, pending_task=...) at 
  base/message_loop.cc:484
  #8  0x760b3aa3 in MessageLoop::DeferOrRunPendingTask 
  (this=0x783c6c00, pending_task=...) at base/message_loop.cc:502
  #9  0x760b3e5d in DoDelayedWork 
  (next_delayed_work_time=0x7839e720, this=0x783c6c00) at 
  base/message_loop.cc:731
  #10 MessageLoop::DoDelayedWork (this=0x783c6c00, 
  next_delayed_work_time=0x7839e720) at base/message_loop.cc:703
  #11 0x760e60f2 in base::MessagePumpGlib::RunWithDispatcher 
  (this=0x7839e700, delegate=optimized out, dispatcher=optimized out) 
  at base/message_pump_glib.cc:215
  #12 0x760b2ce5 in MessageLoop::RunInternal (this=0x783c6c00) at 
  base/message_loop.cc:451
  #13 0x760b2dcc in RunHandler (this=optimized out) at 
  base/message_loop.cc:424
  #14 MessageLoopForUI::Run (this=optimized out, dispatcher=optimized 
  out) at base/message_loop.cc:834
  #15 0x757cb112 in RunUIMessageLoop (browser_process=optimized 
  out) at chrome/browser/browser_main.cc:708
  #16 BrowserMain (parameters=...) at chrome/browser/browser_main.cc:2070
  #17 0x757baee9 in RunNamedProcessTypeMain 
  (main_function_params=..., process_type=...) at 
  chrome/app/chrome_main.cc:552
  #18 ChromeMain (argc=optimized out, argv=optimized out) at 
  chrome/app/chrome_main.cc:895
  #19 0x757bbc09 in main (argc=2, argv=0x7fffe438) at 
  chrome/app/chrome_exe_main_gtk.cc:46
 
 I fail to see where nss is supposed to be involved, here...

Probably the crash is a side effect, so NSS is not involved in the
backtrace. I can reproduce this bug as follows:

chromium   | libnss3-1d  | status
-
14.0.835.202~r103287-1 | 3.12.11-3   | OK
14.0.835.202~r103287-1 | 3.13.1.with.ckbi.1.88-1 | Crash
15.0.874.106~r107270-1 | 3.12.11-3   | Crash
15.0.874.106~r107270-1 | 3.13.1.with.ckbi.1.88-1 | Crash

I guess the actual bug is in chromium, but if libnss3-1d transitions
into testing chromium will be unusable. So I suggest to leave this
open until chromium is fixed.

-- Sebastian


signature.asc
Description: Digital signature

Bug#624429: radare: diff for NMU version 1:1.5.2-3.1

[Sebastian Reichel]

On Sat, Apr 30, 2011 at 12:11:32AM +0200, Luca Falavigna wrote:
 tags 624429 - pending patch
 
 
 Il 29/04/2011 23:56, Luca Falavigna ha scritto:
  I've prepared an NMU for radare (versioned as 1:1.5.2-3.1) and
  uploaded it to DELAYED/10.
 
 Actually, no. I removed my upload as I noticed it fixes FTBFS, but
 doesn't addresss python2.5 removal. I'm going to prepare a new patch
 including fixes to handle the latter.

Thanks for taking care of this. I would appreciate, if you add your
changes to the git repository:

http://git.debian.org/?p=collab-maint/radare.git

Apart from that you can upload to DELAYED/3 next time.

-- Sebastian


signature.asc
Description: Digital signature

Bug#607568: tint2: icons disappeared

[Sebastian Reichel]

On Sun, Dec 19, 2010 at 11:48:23PM +0300, kakadu wrote:
 Package: tint2
 Version: 0.9-2
 
 I can't see icons in system tray. Psi is OK, some other programs (qutim, 
 skype,
 basket, kmix) --- not. If I try to start tint2 from console, tint2 will write

Can you check if this still happens with 0.11-2 from Debian
unstable?

-- Sebastian


signature.asc
Description: Digital signature

Bug#600374: [pkg-fso-maint] Bug#600374: #600374: NMU for Mokomaze ?

[Sebastian Reichel]

Hi,

On Wed, Dec 08, 2010 at 11:12:03AM +0100, Didier 'OdyX' Raboud wrote:
 Le Monday 29 November 2010 03:18:55 Paul Wise, vous avez écrit :
  We are just waiting on the pkg-fso team to make an upload removing the
  icons and adding the patch I sent upstream.
 
 Hi,
 
 (Removing the RM bug CC, I'll send a mail to both bugreports if/when the
 upload is done.)
 
 As there hasn't been much of an answer from the pkg-fso team, I'd like to
 propose an NMU for mokomaze, in order to get this RC bug solved in time
 for Squeeze. Its changelog entry would be: 

Sorry for the long delay, I waited for Joachim (nomeata) to
eventually answer you. The package was previously maintained
by him, but he is no longer active in pkg-fso.

  mokomaze (0.5.5+git8+dfsg0-0.1) unstable; urgency=low
  
* Non-maintainer upload.
* Repack the orig tarball to remove non-free files (Closes: #600374)
  - therefore cherry-pick two upstream commits:
+ [084f1e7] Menu icons replaced with the free ones.
+ [920fb49] Build all the images from a set of SVG files.
  - Add a librsvg2-bin B-D to build the png images from their svg source.
  - Add automake B-Ds and an autoreconf call before the build.
  - Thanks go to Paul Wise for the patches.
  
   -- Didier Raboud did...@raboud.com  Wed, 08 Dec 2010 10:23:12 +0100

Changelog looks fine to me. go on :)

 I pushed the git repository I used to prepare the orig tarball there:
 
 http://git.debian.org/?p=users/odyx-guest/mokomaze-orig.git (branch dfsg-free)
 
 and my update of the packaging git repository there:
 
 http://git.debian.org/?p=users/odyx-guest/mokomaze.git (branch debian-squeeze)
 
 I built the package and pushed it to alioth:
 
 http://alioth.debian.org/~odyx-guest/debian/unstable/mokomaze_0.5.5+git8+dfsg0-0.1.dsc

Do you want to become a member of pkg-fso and push the git stuff
into [0]?

 Now if one DD could review and upload this package for me, it'd be great. 
 After
 the upload, I'll send a mail to debian-release + the RM bug (#605205) to ask 
 the
 Release Team to choose between an unblock and a removal.

I'm currently busy, but I can check it this evening.

-- Sebastian

[0] http://git.debian.org/?p=pkg-fso/mokomaze.git;a=summary


signature.asc
Description: Digital signature

Bug#591388: gnome-dvb-daemon: segmentation fault

[Sebastian Reichel]

severity 591388 important
thanks

Hi,

Bernhard, can you test if the bug still exists in the
gnome-dvb-daemon package available from experimental?

-- Sebastian


signature.asc
Description: Digital signature

Bug#596275: phoneui-apps: not installable in sid on any architecture

[Sebastian Reichel]

Hi,

Heiko Stübner is working on the fso-deviced package. Currently it's
only available from the pkg-fso repository:

deb http://pkg-fso.alioth.debian.org/debian unstable main
deb-src http://pkg-fso.alioth.debian.org/debian unstable main

Heiko: How is the status? Do you need help with the packages?

-- Sebastian


signature.asc
Description: Digital signature

Bug#591590: Fix for #591590

[Sebastian Reichel]

Hi,

I prepared a patch, which fixes this bug. I attached it to this
mail. It adds /var/games to debian/dirs.

I also prepared a NMU for your package fixing #591590, #590208
and #328472. You can find it at [1] or in the mail's attachment:

[1] http://pkg.ring0.de/debian/pool/main/t/tint/

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

Format: 1.8
Date: Sun, 08 Aug 2010 17:54:30 +0200
Source: tint
Binary: tint
Architecture: source amd64
Version: 0.04+nmu1
Distribution: unstable
Urgency: low
Maintainer: Mario Lang ml...@debian.org
Changed-By: Sebastian Reichel elektra...@gmail.com
Description: 
 tint   - TINT Is Not Tetris(tm) ...at least the name isn't
Closes: 328472 590208 591590
Changes: 
 tint (0.04+nmu1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Create /var/games during installation (Closes: #591590)
   * Remove score file on purge (Closes: 328472)
   * Apply Guido Berhoerster's patch to fix two buffer overflows
 (Closes: 590208)
   * Bring Standards-Version up-to-date (3.9.1).
Checksums-Sha1: 
 082a0247f008f2a0eb6edf3aa8c013261a3420a2 716 tint_0.04+nmu1.dsc
 41f338e6d0ec0a29c28583b0500cab7a458d 16079 tint_0.04+nmu1.tar.gz
 eb1a9d483457e9df19626ddf35c67330ce3f4429 17550 tint_0.04+nmu1_amd64.deb
Checksums-Sha256: 
 21aa706295ab6afe9b2e74976644503def1100d7364f3275f73fb5c98658cad3 716 
tint_0.04+nmu1.dsc
 674a89087cf4c9a417288332826ce092a862ec3e3162de3bf1ad9862c0cbb993 16079 
tint_0.04+nmu1.tar.gz
 cadfd50d701c18fe622c623b2d3c647a2e126ec55c91d9dea1b677b06d89b03a 17550 
tint_0.04+nmu1_amd64.deb
Files: 
 42993f211c5a58a8c1abe44e897de396 716 games optional tint_0.04+nmu1.dsc
 a0c9079efbe64373a0e9264ac13fbb6f 16079 games optional tint_0.04+nmu1.tar.gz
 b6acc459debb9370638eee79ba43accb 17550 games optional tint_0.04+nmu1_amd64.deb

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

iEYEARECAAYFAkxe1PwACgkQH0JwilpTmKh6kwCfYHNOVPvrIZ/tXo4SFEssYUi9
4lsAn33w9690H6uzb+OuLYVRHTOI9EYm
=Nf47
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 3.0 (native)
Source: tint
Binary: tint
Architecture: any
Version: 0.04+nmu1
Maintainer: Mario Lang ml...@debian.org
Standards-Version: 3.9.1
Build-Depends: debhelper (= 7), libncurses5-dev
Checksums-Sha1: 
 41f338e6d0ec0a29c28583b0500cab7a458d 16079 tint_0.04+nmu1.tar.gz
Checksums-Sha256: 
 674a89087cf4c9a417288332826ce092a862ec3e3162de3bf1ad9862c0cbb993 16079 
tint_0.04+nmu1.tar.gz
Files: 
 a0c9079efbe64373a0e9264ac13fbb6f 16079 tint_0.04+nmu1.tar.gz

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

iEYEARECAAYFAkxe1PkACgkQH0JwilpTmKjTSACghvTxU9xIr7IQ3dfDxnOSso+P
Ek0AnR5Y60dkSVhuJBZn0Khw2vSTYRa8
=pjKa
-END PGP SIGNATURE-


tint_0.04+nmu1.tar.gz
Description: Binary data
diff -Nru tint-0.04/debian/dirs tint-0.04+nmu1/debian/dirs
--- tint-0.04/debian/dirs	2002-03-16 17:58:42.0 +0100
+++ tint-0.04+nmu1/debian/dirs	2010-08-08 17:38:24.0 +0200
@@ -1,2 +1,3 @@
 usr/games
 usr/share/man/man6
+var/games


signature.asc
Description: Digital signature

Bug#560676: patch from vcs to obsolete gtkdialog

[Sebastian Reichel]

On Thu, Apr 08, 2010 at 10:50:29AM +0100, SevenMachines wrote:
 Package: radare
 Version: 1:1.4-1
 Severity: normal
 Tags: patch
 User: ubuntu-de...@lists.ubuntu.com
 Usertags: origin-ubuntu lucid ubuntu-patch
 
 
 *** /tmp/tmpMLAY5R
 In Ubuntu, we've applied the attached patch to achieve the following:
 
   * 10_drop-gtkdialog-usage.dpatch:
 - import radare r1204, r1210, r1211 from mercurial repository to remove
 any use of gtkdialog and so allow dropping all gtkdialog dependencies
 altogether (LP: #530496)
   * Move libreadline5-dev build-dep to libreadline-dev to fix conflict with
 lua5.1 
 
 We thought you might be interested in doing the same. 

Hi,

I was the one who rewrote this in upstream to drop gtkdialog, so
yes, I am interested ;)

But I decided to upgrade to radare 2 now, which does no longer
provide the UI and does not make use of readline.

-- Sebastian


signature.asc
Description: Digital signature

Bug#529997: (no subject)

[Sebastian Reichel]

the new package still does not fix the buildproblem, although I
wrote into the Changelog it would do so (sorry, I have no access to
a mips box to test the build before).

I notified upstream of the bugs leading to build failures on mips
and the other architectures. I guess they will be fixed in the next
release.

-- Sebastian


signature.asc
Description: Digital signature

Bug#529997: missing support for architectures other than i386 and amd64

[Sebastian Reichel]

I'm already aware of this. The debugger support of radare is
architecture dependent and does not exist for all existing
architectures.

I requested to change default enabled debugger to check if debugging
is possible and enable it only if it is.

A new package is already prepared, waiting for a sponsor:
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=radare

-- Sebastian


signature.asc
Description: Digital signature