Bug#1010351: O: osdsh -- overlays your screen with various system information

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the osdsh package.

The package description is:
 OSDsh is a little program that overlays system information using
 the XOSD library. OSDsh was originally based on osdd and provides
 features like:
 .
  * It is able to display a clock.
  * Shows the volume levels of the soundcard when changing.
  * Tells you if you are on- or off-line, and the time you were connected.
  * Shows the battery status and
  * shows any message you want it to.

Bug#1008880: O: unicode-screensaver -- screensaver displaying unicode characters

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the unicode-screensaver package.

The package description is:
 The unicode-screensaver is a simple screensaver application that repeatedly
 randomly picks an unicode character and displays it in a very large font
 size together with its unicode code point and the character name.
 .
 It works with xscreensaver or gnome-screensaver.

Bug#1008879: O: pidgin-blinklight -- Blinks your ThinkPad's ThinkLight upon new messages

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the pidgin-blinklight package.

The package description is:
 This plugin for Pidgin will blink your laptops when you get
 new messages, so you notice them even if the conversation window is not up
 front and you don't have or don't see the window list.
 .
 To use this with an Thinkpad's ThinkLight, you need to have the ibm-acpi
 kernel module loaded.
 .
 To use this with an ASUS laptop, you need to have the asus_acpi kernel
 module loaded.

Bug#1008878: O: local-apt-repository -- Ready to use local apt repository

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the local-apt-repository package.

The package description is:
 With this package installed, every Debian package (i.e. a *.deb file) dropped
 into /srv/local-apt-repository (which you need to create first) will be
 available to apt.
 .
 This package does not provide an apt repository to be used by other hosts. For
 that, look at more serious repository solutions like reprepro and
 apt-ftparchive.

Bug#1008877: O: screen-message -- Displays a short text fullscreen

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the screen-message package.

The package description is:
 Screen Message will display a given multi-line message as large as
 possible, fullscreen and black on white. You can specify the text either
 when launching sm, or edit it while the program is running.
 .
 It is useful to send messages across a room, e.g. during an university
 lecture. For fast startup, it is recommended to bind it to a key in your
 Desktop Environment.

Bug#1008876: O: arbtt -- Automatic Rule-Based Time Tracker

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the arbtt package.

The package description is:
 The program arbtt, the automatic rule-based time tracker, allows you to
 investigate how you spend your time, without having to manually specify what
 you are doing. arbtt records what windows are open and active, and provides
 you with a powerful rule-based language to afterwards categorize your work.

Bug#1008875: O: libnss-gw-name -- nss module that names the current gateway’s IP address

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the libnss-gw-name package.

The package description is:
 This Name Service Switch (NSS) module resolves the name “gateway.localhost” to
 the IP of the current default gateways of the system. This allows easy access
 to router configuration and to check if connectivity problems are local or
 not.

Bug#1008874: O: gtk-vector-screenshot -- takes screenshots of applications as PDF or SVG files

[Joachim Breitner]

Package: wnpp
Severity: normal

I intend to orphan the gtk-vector-screenshot package.

The package description is:
 This gtk module allows you to take a screenshot of a running gtk-3 application
 as a vector image, with fully scalable graphics and selectable text. It
 supports rendering the application to PDF, SVG and PostScript.

Bug#999100: pidgin-blinklight: missing required debian/rules targets build-arch and/or build-indep

[Joachim Breitner]

Hi,

Am Dienstag, dem 09.11.2021 um 22:28 +0100 schrieb Lucas Nussbaum:
> Please note that this is also a sign that the packaging of this software
> could benefit from a refresh.

indeed. I wonder if anyone is still using this (I am not). If you do,
please speak up!

Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  

Bug#990888: libnss-gw-name FTCBFS: builds for the build architecture

[Joachim Breitner]

Hi,

thanks for the patch. Feel free to NMU the package to be unblocked, I
am not sure when I’ll get around to do an upload (recently re-set up my
laptop and not fully working yet).

Cheers,
Joachim

Am Samstag, dem 10.07.2021 um 17:41 +0200 schrieb Helmut Grohne:
> Source: libnss-gw-name
> Version: 0.3-2
> Tags: patch
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
> 
> libnss-gw-name fails to cross build from source, because debian/rules
> does not pass cross tools to make. The easiest way of doing so - using
> dh_auto_build - is not sufficient as the upstream Makefile hard codes
> pkg-config. It has to be made substitutable as well. Please consider
> applying the attached patch.
> 
> Helmut


-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#979697: unicode-screensaver: exit abnormally

[Joachim Breitner]

Hi Tormod,

Am Samstag, den 23.01.2021, 10:37 +0100 schrieb Tormod Volden:
> Thanks for the report. I was unaware of the other packages using
> /usr/lib/xscreensaver . Is there a way I can have these listed?

Hmm, I was expecting that 
https://packages.debian.org/search?mode=filename=buster=all=any=contents=%2Fusr%2Flib%2Fxscreensaver
lists them, after all unicode-screensaver has a file there:
https://packages.debian.org/buster/amd64/unicode-screensaver/filelist

Is that broken?

> Getting this hack upstream sounds like a good idea! Unless it has any
> use independent of xscreensaver.

Do you want to try? You probably have a better connection to upstream,
and know more about the requirements etc.

Cheers,
Joachim
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#980435: osdsh: Silent SIGSEGV at startup

[Joachim Breitner]

Control: tag -1 + help

thanks for the report! This patch is 13 years old, oh wey. I might need
help from someone who nows C, X11 and dynamic linking better than I do.

Also happy to pass on maintainership of this package to someone else, I
am not using it myself anymore.

Cheers,
Joachim 

Am Dienstag, den 19.01.2021, 06:40 +0100 schrieb Celelibi:
> Package: osdsh
> Version: 0.7.0-10.4
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Nowadays, osdsh crashes without a message.
> The cause I identified is that it looks for a symbol "mixerdevice" in
> the shared library libosdshmixer.so which doesn't exist.
> Since the return of dlsym isn't checked, it dereferences a NULL pointer.
> 
> In the function load_plugin in src/osdsh/controlsh.c:
>   mod_mixerdev = dlsym(module, "mixerdevice");
>   *mod_mixerdev = mixerdevice;
> 
> These lines seems to have been added by the debian patch
> 06-fix-m-option.patch.
> 
> I guess this patch could be reworked to work with the new version.
> 
> Best regards,
> Celelibi
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-1-amd64 (SMP w/2 CPU threads)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages osdsh depends on:
> ii  libc6 2.31-9
> ii  libxosd2  2.2.14-2.1+b1
> ii  tk8.6.10
> 
> osdsh recommends no packages.
> 
> osdsh suggests no packages.
> 
> -- no debconf information
> 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#979697: unicode-screensaver: exit abnormally

[Joachim Breitner]

Hi,

so, none of the other xscreensaver hackas have a full path in there,
and it worked before… so I maybe the reason is this change in the
xscreensaver package itself, in 5.45+dfsg1-1:

  * Ship hacks under /usr/libexec instead of /usr/lib (thanks jwz)

And indeed, xscreensaver-data moved all files from /usr/lib to
/usr/libexec. So I guess I’ll have to do the same…

Maybe xscreensaver itself should have a “Breaks:” against all packages
that still use /usr/lib/xscreensaver/? What do you think, Tormod?

(Or maybe unicode-screensaver should just become part of the
xscreensaver distribution… :-))

Cheers,
Joachim



-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#979697: unicode-screensaver: exit abnormally

[Joachim Breitner]

Hi,

Am Donnerstag, den 14.01.2021, 22:02 +0100 schrieb gregor herrmann:
> On Sun, 10 Jan 2021 10:34:45 +0100, Guillonneau Jean-Paul wrote:
> 
> > this message appears on the screen for xscreensaver :
> > usage : unicode (options) arg
> > unicode : error : no such options : -t
> > xscreensaver : signal : 0 : child pid 6434 (unicode) exit abnormally (code 
> > 2)
> 
> Same here.
> 
> I changed (in xscreensaver-demo -> Settings -> Advanced) the command
> line to the absolute path, i.e. "/usr/lib/xscreensaver/unicode …"
> instead of just "unicode …".

ah, and there is a /usr/bin/unicode in the unicode package. That might
explain it, right?

Now, I wonder, how would I change 
/usr/share/xscreensaver/config/unicode.xml
in the package to fix that…

Cheers,
Joachim
-- 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#799323: local-apt-repository: Uninstallable without systemd despite that seems supported according to the package description

[Joachim Breitner]

Hi,

Am Mittwoch, den 19.08.2020, 06:21 + schrieb Job Bautista:
> Hi, any update here? I rebuilt the 0.6 package to remove the dependency on 
> systemd
> and it works fine in my systemd-less system (though I had to manually run the
> rebuild script everytime I add new packages to the repository).

I consider this (not having to manually run the rebuild script) central
functionality of local-apt-repository: The goal is that the user has to
worry about nothing but dropping apt files in the right directory. I
only know how to achieve this easily with systemd.

That said, I am not using it myself these days and am happy to yield
upstream and debian maintenance to anyone who cares more about this
package.

Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#968031: take-vector-screenshot: crash (SIGSEGV) under GNOME Wayland

[Joachim Breitner]

Control: tag -1 help

Hi Paul,

thanks for the bug report.

gtk-vector-screenshot is quite old, long before there was Wayland etc,
and honestly is quite a big hack (injecting some code into every gtk
program etc.).

It demonstrates that this is possible and useful, but really such a
feature would have to be built-in in (or at least officially supported
by) gtk.

I don’t think I’ll be able to develop it a lot further at this point.
Patches are welcome of course, as are offers to take over (upstream &
Debian) maintenance. 

Cheers,
Joachim

Am Freitag, den 07.08.2020, 09:08 +0800 schrieb Paul Wise:
> Package: gtk-vector-screenshot
> Version: 0.3.2.1-2+b1
> Severity: normal
> File: /usr/bin/take-vector-screenshot
> Usertags: crash wayland
> 
> When I try to take a screenshot under GNOME Wayland I get a crash.
> Other programs like xkill that query the pointer seem to work.
> 
> $ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex 
> 'thread apply all bt full' --args take-vector-screenshot
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x70516700 (LWP 679312)]
> [New Thread 0x7fffefd15700 (LWP 679313)]
> [New Thread 0x7fffef46e700 (LWP 679314)]
> [New Thread 0x7fffeec44700 (LWP 679315)]
> 
> (take-vector-screenshot:679270): GLib-GObject-WARNING **: 08:59:24.716: The 
> property GtkSettings:gtk-button-images is deprecated and shouldn't be used 
> anymore. It will be removed in a future version.
> Gdk-Message: 08:59:24.854: Window 0x55a96270 is a temporary window 
> without parent, application will not be able to position it on screen.
> 
> (take-vector-screenshot:679270): Gdk-WARNING **: 08:59:33.365: Window 
> 0x55a96270 is already mapped at the time of grabbing. gdk_seat_grab() 
> should be used to simultanously grab input and show this popup. You may find 
> oddities ahead.
> 
> Thread 1 "take-vector-scr" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> #0  0x in  ()
> #1  0x770b02a0 in XQueryPointer (dpy=0x55776810, w=1374389535210, 
> root=0x7fffd098, child=0x7fffd090, root_x=0x7fffd088, 
> root_y=0x7fffd088, win_x=0x7fffd088, win_y=0x7fffd088, 
> mask=0x7fffd08c) at ../../src/QuPntr.c:46
> #2  0x5a10 in pdfscreenshot_window_selected 
> (grab_window=grab_window@entry=0x557b07e0 [GtkWindow], event= out>, button=) at take-vector-screenshot.c:52
> #7  0x77313edf in  [GtkWindow]> (instance=instance@entry=0x557b07e0, signal_id= out>, detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
> #3  0x77bc60fb in _gtk_marshal_BOOLEAN__BOXED 
> (closure=closure@entry=0x559c7b80, 
> return_value=return_value@entry=0x7fffd2e0, 
> n_param_values=n_param_values@entry=2, 
> param_values=param_values@entry=0x7fffd340, 
> invocation_hint=invocation_hint@entry=0x7fffd2c0, 
> marshal_data=marshal_data@entry=0x0) at gtkmarshalers.c:83
> #4  0x772f4fd2 in g_closure_invoke (closure=0x559c7b80, 
> return_value=0x7fffd2e0, n_param_values=2, param_values=0x7fffd340, 
> invocation_hint=0x7fffd2c0) at ../../../gobject/gclosure.c:810
> #5  0x77308784 in signal_emit_unlocked_R (node=, 
> detail=detail@entry=0, instance=instance@entry=0x557b07e0, 
> emission_return=emission_return@entry=0x7fffd460, 
> instance_and_params=instance_and_params@entry=0x7fffd340) at 
> ../../../gobject/gsignal.c:3742
> #6  0x77313078 in g_signal_emit_valist (instance=, 
> signal_id=, detail=, 
> var_args=var_args@entry=0x7fffd510) at ../../../gobject/gsignal.c:3508
> #8  0x77b71f12 in gtk_widget_event_internal (event=0x55a660d0, 
> widget=0x557b07e0 [GtkWindow]) at ../../../../gtk/gtkwidget.c:7808
> #9  gtk_widget_event_internal (widget=0x557b07e0 [GtkWindow], 
> event=0x55a660d0) at ../../../../gtk/gtkwidget.c:7677
> #10 0x77a31c98 in propagate_event_up (topmost=, 
> event=, widget=0x557b07e0 [GtkWindow]) at 
> ../../../../gtk/gtkmain.c:2597
> #11 propagate_event (widget=, event=0x55a660d0, 
> captured=, topmost=0x0) at ../../../../gtk/gtkmain.c:2700
> #12 0x77a33e5b in gtk_main_do_event (event=0x55a660d0) at 
> ../../../../gtk/gtkmain.c:1920
> #13 gtk_main_do_event (event=) at 
> ../../../../gtk/gtkmain.c:1690
> #14 0x7772f815 in _gdk_event_emit (event=event@entry=0x55a660d0) 
> at ../../../../gdk/gdkevents.c:73
> #15 0x7778c872 in gdk_event_source_dispatch (base=, 
> callback=, data=) at 
> ../../../../../gdk/wayland/gdkeventsource.c:124
> #16 0x7720b5fd in g_main_dispatch (context=0x55783c20) at 
> ../../../glib/gmain.c:3309
> #17 g_main_context_dispatch (context=context@entry=0x55783c20) at 
> ../../../glib/gmain.c:3974
> #18 0x7720b880 in g_main_context_iterate (context=0x55783c20, 
> block=block@entry=1, 

Bug#966207: RM: infon -- ROM; No longer actively maintained

[Joachim Breitner]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

while requesting removal of `metainit` I noticed that this is still used
by the `infon` package. This, too, has probably little value these days
and I don’t mind if it is removed.

Cheers,
Joachim


-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXxsciBMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsaI0Anii60ChD3xat2tZv/8lG6U/XrzBAAKCz
Tx4yj9JieitEn7wjGfHgAP1HSg==
=DDD+
-END PGP SIGNATURE-

Bug#966206: RM: metainit -- ROM; Obsolete, unused

[Joachim Breitner]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nudged by #965722 I think it’s probably best to remove metainit. I wrote
that 13 years ago to alleivate the pains during the init system wars,
but it never caught on, and is quite obsolete now.

If someone disagrees feel free to take over the package.

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXxsbsxMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsV80AnRMMeHtJDmyCgmOyTbucLidMekwgAJ9M
CseFz5s5B9crRe3BzOZMwZTgVA==
=TsU9
-END PGP SIGNATURE-

Bug#933107: ruby-rubymail: Deprecation warnings with Ruby 2.4 (constant ::Fixnum is deprecated)

[Joachim Breitner]

HI,

On Fri, 26 Jul 2019 11:55:47 -0700 Gerald Turner  wrote:
> Executing feed2imap (feed2imap package) produces the following error
> output:
> 
>   /usr/lib/ruby/vendor_ruby/rmail/header.rb:142: warning: constant ::Fixnum 
> is deprecated

after upgrading to Debian buster, I now get this in my crontab mails;
quite annoying.

Would this fix qualify for a buster backport?

Cheers,
Joachim


-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#924440: ghc8.6.3.so: undefined symbol: gtk_cell_accessible_parent_get_row_header_cells

[Joachim Breitner]

On Wed, 13 Mar 2019 00:47:43 +0100 Roy Sindre Norangshol 
 wrote:
> While trying to compile latest taffybar using stack as explained in
> https://github.com/taffybar/taffybar/issues/365#issuecomment-394188834 ,
> it seems to be greeted with missing unexported symbols from this library.

I can confirm the issue, also trying to build taffybar (with cabal, not
stack, so that choice does not seem to affect it.)



-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  

Bug#940136: aqbanking-tools: Transaction fails with 9075::Starke Kundenauthentifizierung notwendig.

[Joachim Breitner]

Hi,

thanks for the instructions!

Finally got around to trying this.

Am Freitag, den 25.10.2019, 21:26 +0200 schrieb Micha Lenk:
> # Entry for your sources.list
> deb https://people.debian.org/~micha/PSD2/ buster-experimental-backports/


for those following along from home, it should be:

   deb https://people.debian.org/~micha/PSD2/ experimental-buster-backports/


But trying to fetch my transactions I still get this error:

   AqBanking v5.99.40.0beta
   Sende Aufträge an die Bank(en)
   Sorting commands by account
   Sorting commands by account
   Sorting commands by provider
   Send commands to providers
   Send commands to provider "AQHBCI"
   Exklusiver Zugriff auf Benutzer
   Locking customer "576"
   HBCI-Aufträge werden ausgeführt
   AqHBCI gestartet
   Selecting iTAN mode "chipTAN manuell" (910, version 3, process 2)
   Öffne Dialog mit dem Server
   Aufträge werden kodiert
   Sending message
   Mit Server verbinden...
   Hostname "banking-bw5.s-fints-pt-bw.de" wird aufgelöst...
   IP-Adresse ist "62.181.154.196"
   Verbindung zu "banking-bw5.s-fints-pt-bw.de" wird aufgebaut
   Verbunden mit "banking-bw5.s-fints-pt-bw.de"
   Using GnuTLS default ciphers.
   TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
   Verbunden.
   Nachricht senden...
   Nachricht gesendet.
   Message sent
   Queue sent
   Warte auf Antwort
   Antwort wird empfangen...
   HTTP-Status: 200 (OK)
   Antwort empfangen.
   Beenden der Verbindung zum Server...
   Verbindung beendet.
   Antwort erhalten
   HBCI: 9050 - Die Nachricht enthält Fehler. (M)
   HBCI: 9075 - Banking-Programm nicht PSD2-fähig, bitte aktualisieren. (M)
   HBCI: 9800 - Dialog abgebrochen (M)

It seems to use the right version of aqbanking…

So I tried to configure the “user” again in the in Onlinebanking
configuration daemon. There is an odd UI error where I cannot see the
progress it is making when I click on any of the buttons. Similar, the
drop down menus have problems. Maybe a local issue with my installation
here, though…

But ignoring the UI glitches, re-adding the account seems to have
worked. Thanks!

The only regression found so far is that although I associated the
aqbanking account with a specific Gnucash account, if I then go that
gnucash account and fetch my balance or transactions, it asks me again
every time to select with Gnucash account this should be associated
with.

Cheers,
Joachim


-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#940136: aqbanking-tools: Transaction fails with 9075::Starke Kundenauthentifizierung notwendig.

[Joachim Breitner]

Hi,

On Thu, 03 Oct 2019 21:38:53 +0200 Martin Steigerwald  
wrote:
> Dear Micha.
> 
> Micha Lenk - 03.10.19, 20:27:48 CEST:
> > I started to look into updating AqBanking in Debian again. It all
> > starts with uploading Gwenhywfar, which I did a few days ago. As
> > usual when binary package names change (in this case required due to
> > the soname bump), the package is currently stalled in the NEW queue.
> > https://ftp-master.debian.org/new/libgwenhywfar_4.99.19rc3-1.html
> > 
> > So we will need some patience now.
> 
> Thank you very much. Looking forward to it.

I see that libaqbanking has made it into experimental. Great!

But I guess more needs to happen for gnucash to be able to use it,
right? Gnucash depends on libaqbanking35-plugins.

Cheers,
Joachim
 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#934905: libaqbanking35: libaqbanking not ready for PSD2, will not work after 14 September 2019

[Joachim Breitner]

Hi,


On Fri, 4 Oct 2019 22:46:14 +0200 Micha Lenk  wrote:
> But before we get there, I need to update the packages. The current 
> state is always available in Git on 
> https://salsa.debian.org/aqbanking-team in the respective experimental 
> branch.
> 
> As soon as I have the packaging fixed locally, I will make an APT 
> repository available with all the packages I created so far. So, this 
> isn't blocked by ftp-master, but I need to find the time to work on it.

I am checking that space regularly, and am very much looking forward to
these packages :-)

Cheers,
Joachim
 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#941893: RFA: pam-dbus

[Joachim Breitner]

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

pam-dbus (which allows you to configure a guest account where people can
log in when you approve it by approving a notification popup) was a fun
experiment from me years ago, but I never used it, and have not touched
it in a while. Since this is somewhat security-related, this really
shouldn’t be in the archive without an active maintainer. The UI part
needs porting to gtk3 (this kicks it off testing right now).

Is anyeone interest in taking it over (upstream and packaging)? Else
I’ll ask for its removal at some point in the future.


Cheers,
Joachim


-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXZrynhMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsBQ0AoMieNUq0xpL03WQClQexpuyZbZ/AAJsG
3ItfHjbETUarrkS4tXmbPNFDKg==
=nTJc
-END PGP SIGNATURE-

Bug#940136: gnucash: HBCI/FinTS module not ready for PSD2, will not work after 14 September 2019

[Joachim Breitner]

Dear Felix,
 
> I have already pushed libaqbanking 5.8.2 to unstable.
> gnucash 3.7 has been released containing the mentioned commit.
> It would be nice to get 3.7 into unstable soon since having the fix available
> in testing is a perquisite to fixing it in stable.

thanks for that! But September 14 has passed and now the bank is
refusing to work with gnucash. According to
https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/PSD2
version 5.99.25beta of aqbanking can fix this.

I don't see tarball releases of beta release on the webpage, else I’d
try it myself, but my Debian-packagig-foo has become rusty – would you
consider adding the packaging for that beta release to a branch of the
packaging git repo? Or maybe even upload to experimental?

Not being able to fetch my bank statements is quite annoying,
unfortunately.

Cheers,
Joachim

-- 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#935503: gnucash: HBCI/FinTS module not ready for PSD2, will not work after 14 September 2019

[Joachim Breitner]

Dear Felix,b
 
> I have already pushed libaqbanking 5.8.2 to unstable.
> gnucash 3.7 has been released containing the mentioned commit.
> It would be nice to get 3.7 into unstable soon since having the fix available
> in testing is a perquisite to fixing it in stable.

thanks for that! But September 14 has passed and now the bank is
refusing to work with gnucash. According to
https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/PSD2
version 5.99.25beta of aqbanking can fix this.

I don't see tarball releases of beta release on the webpage, else I’d
try it myself, but my Debian-packagig-foo has become rusty – would you
consider adding the packaging for that beta release to a branch of the
packaging git repo? Or maybe even upload to experimental?

Not being able to fetch my bank statements is quite annoying,
unfortunately.

Cheers,
Joachim

-- 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#930871: arbtt: unsupported tags leads to error

[Joachim Breitner]

Hi,

Am Samstag, den 22.06.2019, 17:54 +0200 schrieb Tollef Fog Heen:
> ]] Joachim Breitner 
> 
> Hi!
> 
> > I was young and naive when I designed the file format, and sometimes
> > when arbtt-stats is killed at the wrong moment, invalid (partial) data
> > is written. You can recover most using the arbtt-recover tool.
> 
> Thanks, that helped a lot.  It would be useful if this was referenced in
> the error output, could you consider adding that, since it won't recover
> by itself?

oh, yes, that’s an obviously good idea. Will be in the next release.

Cheers,
Joachim
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#930871: arbtt: unsupported tags leads to error

[Joachim Breitner]

Hi,

Am Freitag, den 21.06.2019, 21:06 +0200 schrieb Tollef Fog Heen:
> Package: arbtt
> Version: 0.10.1-1
> Severity: important
> 
> arbtt seems to have written data which it is unable to read back for me:
> 
> $ arbtt-stats -t 
> Processing data 
> [===>.]  
> 11%arbtt-stats: Unsupported TimeLogEntry version tag 0
> CallStack (from HasCallStack):
>   error, called at src/Data.hs:90:15 in main:Data
> 
> I'm unable to get it to output anything from the stream, it always stops
> at what seems to be the same place.

I was young and naive when I designed the file format, and sometimes
when arbtt-stats is killed at the wrong moment, invalid (partial) data
is written. You can recover most using the arbtt-recover tool.

Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#903960: gnucash: segfaults in QubesOS VM

[Joachim Breitner]

Hi,

this crash happens also without QubesOS, at least to me, and I think it
is in correct to mark this as fixed upstream (probably a confusion with
bts-link and the upstream bug being closed as a duplicate.)

The real bug seems to be in gtk:
https://gitlab.gnome.org/GNOME/gtk/issues/61

Cheers,
Joachim


-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#906115: gnucash: Crash when press key on new entry in account

[Joachim Breitner]

Hi,

does unsetting GTK_IM_MODULE help?

Then this is likely caused by 
https://gitlab.gnome.org/GNOME/gtk/issues/61
and has been bothering me for a few months now :-(

Cheers,
Joachim


-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#929264: Segmentation fault in grdpaste

[Joachim Breitner]

Package: gmt
Version: 5.4.5+dfsg-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

this sequence of commands causes a segementation fault. This is a
regression; this is from a project from a few years back and worked
then:

wget -c 
http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N45E0{06,07}.hgt.zip
unzip N45E006.hgt.zip
gmt xyz2grd N45E006.hgt -R6/7/45/46 -I3s -di-32768 -ZTLhw -GN45E006.grd
gmt grd2xyz N45E006.grd >N45E006.txt
gmt surface N45E006.txt -RN45E006.grd -T0.35 -GN45E006.grd
unzip N45E007.hgt.zip
gmt xyz2grd N45E007.hgt -R7/8/45/46 -I3s -di-32768 -ZTLhw -GN45E007.grd
gmt grd2xyz N45E007.grd >N45E007.txt
gmt surface N45E007.txt -RN45E007.grd -T0.35 -GN45E007.grd
cp N45E006.grd 45tmp.grd
gmt grdpaste 45tmp.grd N45E007.grd -G45tmp.grd
ERROR: Caught signal number 11 (Segmentation fault) at
/usr/lib/x86_64-linux-gnu/libnetcdf.so.13(NC_check_nulls+0xc7)[0x7f9dbb8af9a7]
[0x0]
Stack backtrace:
/usr/lib/x86_64-linux-gnu/libgmt.so.5(sig_handler+0x2ac)[0x7f9dbb9f006c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12670)[0x7f9dbb4c9670]
/usr/lib/x86_64-linux-gnu/libnetcdf.so.13(NC_check_nulls+0xc7)[0x7f9dbb8af9a7]
/usr/lib/x86_64-linux-gnu/libnetcdf.so.13(+0x2df9f)[0x7f9dbb8aff9f]
/usr/lib/x86_64-linux-gnu/libnetcdf.so.13(nc_get_varm_float+0xf)[0x7f9dbb8b133f]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(+0x91c24)[0x7f9dbba54c24]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(gmt_nc_read_grd+0x826)[0x7f9dbba55bb6]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(gmtlib_read_grd+0x9e)[0x7f9dbba37ede]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(+0x488e8)[0x7f9dbba0b8e8]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(GMT_Read_Data+0x4c3)[0x7f9dbba0d213]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(GMT_grdpaste+0x3e0)[0x7f9dbbbaddc0]
/usr/lib/x86_64-linux-gnu/libgmt.so.5(GMT_Call_Module+0xc0)[0x7f9dbb9faf50]
gmt(main+0x5c6)[0x55ef48806716]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f9db8ca709b]
gmt(_start+0x2a)[0x55ef48806cda]

Cheers,
Joachim

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gmt depends on:
ii  gmt-common   5.4.5+dfsg-1
ii  libatlas3-base [liblapack.so.3]  3.10.3-8
ii  libblas3 [libblas.so.3]  3.8.0-2
ii  libc62.28-5
ii  libcurl3-gnutls  7.63.0-1
ii  libfftw3-single3 3.3.8-2
ii  libgdal202.4.0+dfsg-1+b1
ii  libgmt5  5.4.5+dfsg-1
ii  libhdf5-103  1.10.4+repack-9
ii  liblapack3 [liblapack.so.3]  3.8.0-2
ii  libnetcdf13  1:4.6.2-1
ii  libpcre3 2:8.39-11
ii  libsz2   1.0.2-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gmt recommends:
ii  gmt-dcw  1.1.4-2
ii  gmt-doc  5.4.5+dfsg-1
ii  gmt-gshhg-full [gmt-gshhg-data]  2.3.7-4
ii  gmt-gshhg-high [gmt-gshhg-data]  2.3.7-4
ii  gmt-gshhg-low [gmt-gshhg-data]   2.3.7-4

Versions of packages gmt suggests:
pn  gmt-examples  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHAEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXOJxyRMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsZHwAmKLZL5/EiajG0KVywiooW7s3zYEAoI48
ZmEUs8WoHiwXYLmO1DFc0Nb8
=O9GL
-END PGP SIGNATURE-

Bug#916800: phybin: FTBFS with newer GHC

[Joachim Breitner]

Hi,

Am Dienstag, den 18.12.2018, 23:35 +0100 schrieb Andreas Tille:
> Hi Joachim,
> 
> On Tue, Dec 18, 2018 at 10:57:15PM +0100, Joachim Breitner wrote:
> > Would not be hard to fix, but is there a chance that upstream could just 
> > release a version that works with a current compiler?
> 
> I'm afraid upstream is not very active but would be happy about a patch.

I submitted a patch to upstream, feel fee to get it from github if you
need it earlier:
https://github.com/rrnewton/PhyBin/pull/13

https://patch-diff.githubusercontent.com/raw/rrnewton/PhyBin/pull/13.patch

Cheers,
Joachim
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#916800: phybin: FTBFS with newer GHC

[Joachim Breitner]

Hi,

Would not be hard to fix, but is there a chance that upstream could just 
release a version that works with a current compiler?

Cheers, Joachim



Am 18. Dezember 2018 22:36:26 MEZ schrieb Andreas Tille :
>Control: tags -1 help
>
>Hi,
>
>unfortunately I have no idea how to fix this.
>
>Kind regards, Andreas.
>
>On Tue, Dec 18, 2018 at 08:32:22PM +0200, Ilias Tsitsimpis wrote:
>> Package: phybin
>> Version: 0.3-2
>> Severity: serious
>> Justification: fails to build from source (but built successfully in
>the past)
>> 
>> Dear maintainer,
>> 
>> phybin FTBFS with newer versions of GHC (>= 8.4) with the following
>error:
>> 
>>  [1 of 9] Compiling Bio.Phylogeny.PhyBin.CoreTypes (
>Bio/Phylogeny/PhyBin/CoreTypes.hs,
>dist-ghc/build/test-phybin/test-phybin-tmp/Bio/Phylogeny/PhyBin/CoreTypes.o
>)
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:112:35: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  112 | displayDefaultTree orig = loop tr <> ";"
>>  |   ^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:120:27: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  120 |  Just val -> base <> text ":[" <> text (show val) <>
>text "]"
>>  |   ^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:120:40: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  120 |  Just val -> base <> text ":[" <> text (show val) <>
>text "]"
>>  |^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:120:59: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  120 |  Just val -> base <> text ":[" <> text (show val) <>
>text "]"
>>  |   ^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:121:47: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>> 

Bug#916283: No "Varying the domain and host names"

[Joachim Breitner]

Package: reprotest
Version: 0.7.8
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

the manpage says

> see "Varying the domain and host names" for details.

but I see no such section anywhere.

Cheers,
Joachim

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reprotest depends on:
ii  apt-utils  1.8.0~alpha2
ii  diffoscope 107
ii  libdpkg-perl   1.19.2
ii  procps 2:3.3.15-2
ii  python33.7.1-2
ii  python3-debian 0.1.33
ii  python3-distro 1.3.0-1
ii  python3-pkg-resources  40.6.2-1
ii  python3-rstr   2.2.6-1

Versions of packages reprotest recommends:
ii  diffoscope   107
ii  disorderfs   0.5.5-1
ii  faketime 0.9.7-3
ii  locales-all  2.28-2
ii  sudo 1.8.26-2

Versions of packages reprotest suggests:
ii  autodep8 0.15
ii  qemu-system  1:2.12+dfsg-3+b1
ii  qemu-utils   1:2.12+dfsg-3+b1
ii  schroot  1.6.10-6+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXBEmoBMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBszlcAn1vr9aXhFgelEAPz/Sxx+FFBUgQ+AKCG
K8gHl/dzp+YNplHSbR/98JjtdQ==
=77Ar
-END PGP SIGNATURE-

Bug#915713: ghc-testsuite build depends on ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be installed

[Joachim Breitner]

Hi team,

Am Donnerstag, den 06.12.2018, 13:22 +0200 schrieb Adrian Bunk:
> Source: ghc-testsuite
> Version: 8.2.2-2
> Severity: serious
> Tags: ftbfs
> 
> The following packages have unmet dependencies:
>  builddeps:ghc-testsuite : Depends: ghc (< 8.2.2+) but 8.4.4+dfsg1-1 is to be 
> installed

the ghc-testsuite package somehow never was really useful. Shall we
just kick it?

Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#910480: ghc: missing Breaks+Replaces+Provides for newly bundled libraries

[Joachim Breitner]

Hi,

Am Donnerstag, den 18.10.2018, 22:45 +0300 schrieb Ilias Tsitsimpis:
> On Thu, Oct 18, 2018 at 08:43PM, Joachim Breitner wrote:
> > Am Donnerstag, den 18.10.2018, 12:56 +0300 schrieb Ilias Tsitsimpis:
> > > There seems to exist the debian/provided_substvars script which tries to
> > > add Provides+Conflicts for ghc's bundled libraries, but for some reason
> > > mtl is explicitly ignored. I am not sure why this (as well as other
> > > packages) are being ignored, so I have CC-ed Joachim who wrote that
> > > script.
> > 
> > I think these are packages that come with the GHC source (e.g. to build
> > other included tools), but that we do not want to provide from the ghc
> > package, as there is a separate stand-alone package doing that.
> 
> I think I may be missing something, so let me take libghc-mtl-dev as an
> example. GHC-8.4.3 includes the mtl library which was not included in
> GHC-8.0.2. The Debian package for ghc-8.4.3 does not provide
> libghc-mtl-dev, because, as you said, there is a separate, stand-alone
> package doing that. But then, libghc-mtl-dev fails to install with:
> 
>trying to overwrite '/var/lib/ghc/package.conf.d/mtl-2.2.2.conf',
>which is also in package libghc-mtl-dev 2.2.2-2
> 
> as the mtl library is already provided by ghc (see #910008).
> 
> It seems to me that the Debian ghc package needs to Provides+Conflicts
> with libghc-mtl-dev as it does with libghc-cabal-dev. Is there anything
> special with mtl or any of the other packages that are excluded by that
> list?

there are two ways of solving the problem:
 * ghc starts to Provide+Conflict libghc-mtl-dev
 * ghc stops shipping /var/lib/ghc/package.conf.d/mtl-2.2.2.conf

Judging from
https://ghc.haskell.org/trac/ghc/wiki/Commentary/Libraries/VersionHistory
mtl is indeed now shipped “officially” with GHC. So yes, remove it from
@ignored. The mtl has been in @ignored since 6.12.1, long before I got
involved, so don’t assume it is all up-to-date.

The commit messages in
$ git log -p debian/provided_substvars
are somewhat helpful.

> > >  * Remove all ignored libraries except for ghc, although I believe we
> > > can safely remove that too, and Provide/Conflict libghc-ghc-dev.
> > > @nomeata please comment on whether this is the right approach.
> > 
> > If you start actually providing them with ghc, then yes. But it would
> > mean that you cannot upgrade them independently any more.
> 
> How can I choose which libraries are provided by ghc? Taking mtl again
> as an example, how can I tell ghc to not install the mtl library, and
> provide it through a separate package?

If mtl is now a dependency of, say, ghc or another library provided by
GHC, then you can’t really. I thought there might have been some code
in debian/ to control that, but I don’t see it right now.

> Also, wouldn't we be able to upgrade them independently, if we used
> versioned Conflicts (as has been previously be done for libghc-cabal-dev)?
> Take libghc-stm-dev as an example. GHC-8.4.3 provides stm-2.4.5.0 but
> the user should be able to install libghc-stm-dev-2.4.5.1 if the Debian
> ghc package Conflicts with libghc-stm-dev (<< 2.4.5.1).

Oh, yes, that might work indeed.

> Again, thank you very much for you input, this is all new to me.

It’s very old to me, which is not much better :-)

Cheers,
Joachim
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#910480: ghc: missing Breaks+Replaces+Provides for newly bundled libraries

[Joachim Breitner]

Hi,

Am Donnerstag, den 18.10.2018, 12:56 +0300 schrieb Ilias Tsitsimpis:
> There seems to exist the debian/provided_substvars script which tries to
> add Provides+Conflicts for ghc's bundled libraries, but for some reason
> mtl is explicitly ignored. I am not sure why this (as well as other
> packages) are being ignored, so I have CC-ed Joachim who wrote that
> script.

I think these are packages that come with the GHC source (e.g. to build
other included tools), but that we do not want to provide from the ghc
package, as there is a separate stand-alone package doing that.

>  * Remove all ignored libraries except for ghc, although I believe we
> can safely remove that too, and Provide/Conflict libghc-ghc-dev.
> @nomeata please comment on whether this is the right approach.

If you start actually providing them with ghc, then yes. But it would
mean that you cannot upgrade them independently any more.


Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#906815: arbtt: "index too large" when running arbtt-stats

[Joachim Breitner]

Hi,

Am Dienstag, den 25.09.2018, 11:39 +0100 schrieb Chris Lamb:
> Hi,
> 
> > Not sure if this is similar to #751279 (which appears to be more of a
> > wishlist request), but I am getting a fatal:
> 
> […]
> >  arbtt-stats: Prelude.!!: index too large
> 
> Gentle ping on this?

thanks for the point.

The log file occasionally gets corrupted upon unclean shutdown. You
should be able to recover with much data loss using arbtt-recover:
http://arbtt.nomeata.de/doc/users_guide/arbtt-recover.html

Cheers,
Joachim

-- 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


signature.asc
Description: This is a digitally signed message part

Bug#898220: ITP: imv -- A command line image viewer intended for use with tiling window managers

[Joachim Breitner]

Hi,

Am Dienstag, den 08.05.2018, 22:28 +0200 schrieb Paride Legovini:
> Package: wnpp
> Severity: wishlist
> Owner: Paride Legovini 
> 
> * Package name: imv

heads-up: there is a very useful binary called imv in the package
renameutils.


Cheers,
Joachim
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  

signature.asc
Description: This is a digitally signed message part

Bug#886222: LTS 11?

[Joachim Breitner]

Hi,

Am Montag, den 02.04.2018, 03:07 + schrieb Clint Adams:
> On Sun, Apr 01, 2018 at 09:52:52PM -0400, Joachim Breitner wrote:
> > I know that given that _could_ just do it myself, so it is a bit
> > hypocritical to send this mail to the list, but … well, you know how it
> > is. Anyways, is anyone here on the team going to tackle getting 8.2.2
> > and LTS-11 into unstable soon? We are now so far behind that one cannot
> > build GHC HEAD on unstable any more...
> 
> We've been waiting for #886222 to get fixed, though I suspect uploading
> GHC 8.2 would make it more likely for that to happen.

hmm, would it be too bad to remove Haskell on mips from testing during
the transition? This way the transition can happen in parallel to the
linker fix being implemented, and mips can catch up once they are
ready.

Or maybe the non-gold linker can be used on mips?

Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  

signature.asc
Description: This is a digitally signed message part

Bug#892004: Please adapt to gnome-settings-daemon 3.28 by March 15

[Joachim Breitner]

Hi,

I am unable to do something this week. Could someone else apply the
change and upload the package?

Thanks,
Joachim

Am Samstag, den 10.03.2018, 21:47 -0500 schrieb Jeremy Bicha:
> Please make your upload on or before March 15. Otherwise, we will need
> to NMU your package for the gnome-settings-daemon 3.28 transition.
> 
> On behalf of the Debian GNOME Team,
> Jeremy Bicha
> 
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#892004: Please adapt to gnome-settings-daemon 3.28 by March 15

[Joachim Breitner]

Hi,

I am unable to do something this week. Could someone else apply the
change and upload the package?

Thanks,
Joachim

Am Samstag, den 10.03.2018, 21:47 -0500 schrieb Jeremy Bicha:
> Please make your upload on or before March 15. Otherwise, we will need
> to NMU your package for the gnome-settings-daemon 3.28 transition.
> 
> On behalf of the Debian GNOME Team,
> Jeremy Bicha
> 
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#892004: xmonad: Adapt to gnome-settings-daemon 3.28

[Joachim Breitner]

Hi Haskellers,

is anyone here using xmonad with GNOME and can test this?

Otherwise I’ll just apply the suggested change blindly, I guess.

Cheers,
Joachim

Am Samstag, den 03.03.2018, 22:11 -0500 schrieb Jeremy Bicha:
> Package: xmonad
> Version: 0.13-6
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: gsd328
> 
> xmonad includes a GNOME Flashback session file for easy login to a
> GNOME Flashback session using xmonad. gnome-settings-daemon 3.28
> has removed one of its plugins (functionality is provided by mutter instead)
> and the session file will no longer work.
> 
> Please modify debian/gnome-flashback-xmonad.session to remove
> org.gnome.SettingsDaemon.A11yKeyboard;
> 
> Please make this change soon or else we will need to NMU your package
> when we upload gnome-settings-daemon 3.28. We have not set a date for
> that upload yet, but gnome-settings-daemon 3.27.91 is in experimental
> now if you want to test your package with it.
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha
> 
> ___
> Pkg-haskell-maintainers mailing list
> pkg-haskell-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#881753: stretch update for local-apt-repository

[Joachim Breitner]

Hi,

Am Dienstag, den 27.02.2018, 21:59 +0200 schrieb Adrian Bunk:
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.

please go ahead, and thanks a lot!

Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#603157: ITP: ttf-ubuntu-font-family

[Joachim Breitner]

Hi Jeremy,


On Tue, 28 Nov 2017 09:05:22 -0500 Jeremy Bicha  wrote:
> Control: owner -1 Jeremy Bicha 
> Control: retitle -1 ITP: fonts-ubuntu -- sans-serif font set from Ubuntu
> 
> I will finally be uploading this to non-free soon. Packaging is at
> 
> https://anonscm.debian.org/git/pkg-fonts/fonts-ubuntu.git
>

how soon is soon? :-)

Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#890337: Disabling Trackpoint Scrolling via xorg.conf freezes screen/input

[Joachim Breitner]

Package: xserver-xorg-core
Version: 2:1.19.6-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I have upgraded xserver-xorg-core and xserver-xorg-legacy from
2:1.19.5-1 to 2:1.19.6-1. When I rebooted, the system (a T460s Thinkpad)
would start, but as soon as the X server is started, the screen would
turn black and no input would be accepted -- not even switching to the
text terminal.

The problem disappeared once I removed the file
/etc/X11/xorg.conf.d/30-scoll.conf with this content:

Section "InputClass"
Identifier "TPPS/2 IBM TrackPoint"
Driver "libinput"
Option "ScrollMethod" "none"
EndSection


I have added the corresponding xorg log to the list of log files below,
note how it stops abruptly at

[   187.857] (II) event9  - (II) Integrated Camera: Integrated C: (II) is 
tagged by udev as: Keyboard
[   187.857] (II) event9  - (II) Integrated Camera: Integrated C: (II) device 
is a keyboard
[   187.858] (II) config/udev: Adding input device (unnamed) (/dev/ttyS0)
[   187.858] (**) (unnamed): Applying InputClass "TPPS/2 IBM TrackPoint"
[   187.858] (II) Using input driver 'libinput' for '(unnamed)'
[   187.858] (**) (unnamed): always reports core events
[   187.858] (**) Option "Device" "/dev/ttyS0"
[   187.858] (**) Option "_source" "server/udev"

Cheers,
Joachim



- -- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
- --
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 
[8086:1916] (rev 07)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
- -
total 8
- -rw-r--r-- 1 root root 168 Oct  6  2016 20-backlight.conf
- -rw-r--r-- 1 root root 316 Feb 13 10:00 30-scoll.conf-disabled

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
- ---
Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14)

Xorg X server log files on system:
- --
- -rw-r--r-- 1 root root 38435 Feb 13 10:02 /var/log/Xorg.0.log
- -rw-r--r-- 1 root root 15114 Feb 13 10:01 /var/log/Xorg.0.log.old

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
- -
[21.106] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[21.106] X Protocol Version 11, Revision 0
[21.106] Build Operating System: Linux 4.9.0-5-amd64 x86_64 Debian
[21.106] Current Operating System: Linux kirk 4.14.0-3-amd64 #1 SMP Debian 
4.14.13-1 (2018-01-14) x86_64
[21.106] Kernel command line: BOOT_IMAGE=/vmlinuz-4.14.0-3-amd64 
root=/dev/mapper/kirk--vg-root ro single
[21.106] Build Date: 26 January 2018  04:30:21PM
[21.106] xorg-server 2:1.19.6-1 (https://www.debian.org/support) 
[21.106] Current version of pixman: 0.34.0
[21.106]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[21.106] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[21.106] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 13 10:02:31 
2018
[21.107] (==) Using config directory: "/etc/X11/xorg.conf.d"
[21.107] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[21.107] (==) No Layout section.  Using the first Screen section.
[21.107] (==) No screen section available. Using defaults.
[21.107] (**) |-->Screen "Default Screen Section" (0)
[21.107] (**) |   |-->Monitor ""
[21.108] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[21.108] (**) |   |-->Device "card0"
[21.108] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[21.108] (==) Automatically adding devices
[21.108] (==) Automatically enabling devices
[21.108] (==) Automatically adding GPU devices
[21.108] (==) Max clients allowed: 256, resource mask: 0x1f
[21.109] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[21.109]Entry deleted from font path.
[21.109] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[21.109]Entry deleted from font path.
[21.109] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[21.109]Entry deleted from font path.
[21.110] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[21.110]Entry deleted from font path.
[21.110] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[21.110]Entry deleted from font path.
[21.110] (==) FontPath set to:

Bug#885360: pam-dbus-notify: Depends on unmaintained pygtk

[Joachim Breitner]

Hi,

I am not sure if pam-dbus-notify is used by anyone. Feel free to remove
it along with pygtk unless someone else complains (and wants to take
over this package.)

Opening an RFA for it…

Greetings,
Joachim

Am Dienstag, den 26.12.2017, 10:13 -0500 schrieb Jeremy Bicha:
> Package: pam-dbus-notify
> Version: 0.2.1-3
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs pygtk
> Tags: sid buster
> 
> pygtk is unmaintained upstream. It has not had a release since GNOME 3
> was released in 2011.
> 
> The way forward is to port your app to use GObject Introspection
> bindings (and gtk3).
> 
> For more information on GObject Introspection see [1] and [2].
> 
> Please try to do this before the Buster release as we're going to
> try to remove pygtk this cycle.
> 
> If you have any question don't hesitate to ask.
> 
> [1] https://wiki.gnome.org/Projects/GObjectIntrospection
> [2] https://wiki.gnome.org/Projects/PyGObject
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#885399: RFA: pam-dbus -- Handler for the pam-dbus module, using notification-daemon

[Joachim Breitner]

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I request an adopter for the pam-dbus package. It uses pygtk and needs
to be ported to gtk3. I am not using this package, so if anyone find
this useful, please take it over. If not, it will be removed together
with pygtk.

Cheers,
Joachim

The package description is:
 pam-dbus-notify is a per-session daemon that displays requests from
 libpam-dbus-notify, using notification daemon popups.

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCWkKVYBMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsORcAoL+bvG7SX84MkB14y10eqH0VJMzBAKDJ
FXOt5Q106iKmwhd5v50yOujEMg==
=x0hr
-END PGP SIGNATURE-

Bug#884377: Missing the sejda-console

[Joachim Breitner]

Package: libsejda-java
Version: 3.2.38-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

according to https://github.com/torakiki/sejda/wiki/Getting-Started
sejda comes with a console for command line use, and I would have
expected this in this package, or in a separate package. Is there a good
reason for its absence?

Thanks,
Joachim

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libsejda-java depends on:
ii  libbcmail-java1.57-1
ii  libbcprov-java1.57-1
ii  libcommons-io-java2.5-2
ii  libcommons-lang3-java 3.5-1
ii  libgeronimo-validation-1.0-spec-java  1.1-3
ii  libimgscalr-java  4.2-1
ii  libmetadata-extractor-java2.10.1-3
ii  libslf4j-java 1.7.25-2
ii  libtwelvemonkeys-java 3.3.2-2

libsejda-java recommends no packages.

libsejda-java suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCWjKz4hMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsJwcAnib0GKHVGsUj/zjZ9cLYgrjg3NerAJ9w
Pzwzbd/GFaloEPTqGUsgACBJQQ==
=dZ2o
-END PGP SIGNATURE-

Bug#883977: *** stack smashing detected ***: evolution terminated

[Joachim Breitner]

Hi,

rebuilding evolution fixes the problem for me.

Maybe re-assign to evolution?

Joachim

On Sat, 09 Dec 2017 17:38:48 -0500 Joachim Breitner <nome...@debian.org> wrote:
> Package: evolution-data-server
> Version: 3.26.2.1-1.1
> Severity: grave
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> marking this as grave under the assumption that I am not the only one
> affected, please downgrade if it is specific to my setup for some
> reason.
> 
> I just upgraded evolution-data-server from 3.26.2.1-1 to 3.26.2.1-1.1,
> and now evolution will not start again: Even before a windows appears, I
> get the backtrace further down.  The various eds components start
> successfully. Removing ~/.cache/evolution does not help.
> 
> I have no idea what went wrong, but obviously things are failing quite
> badly…
> 
> Cheers,
> Joachim
> 
> 
> 
> ~ $ evolution
> *** stack smashing detected ***: evolution terminated
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x7230b)[0x7f6ac43b630b]
> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f6ac4441957]
> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f6ac4441920]
> /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19(+0x3d30c)[0x7f6ab799b30c]
> /usr/lib/evolution/libevolution-calendar.so.0(+0x97163)[0x7f6a90318163]
> /usr/lib/evolution/libevolution-calendar.so.0(+0x9d197)[0x7f6a9031e197]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
> /usr/lib/evolution/libevolution-calendar.so.0(e_cal_model_set_time_range+0xe1)[0x7f6a902d2b91]
> /usr/lib/evolution/modules/module-calendar.so(+0x20a49)[0x7f6a8ea16a49]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_get_shell_view+0xb7)[0x7f6ac93a5797]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_set_active_view+0x42)[0x7f6ac93a6692]
> /usr/lib/evolution/libevolution-shell.so.0(+0x27176)[0x7f6ac93a7176]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_setv+0x23e)[0x7f6ac79f8a4e]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_set_property+0x1e)[0x7f6ac79f99de]
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10dcc3)[0x7f6ac7d42cc3]
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind_with_mapping+0x311)[0x7f6ac7d459c1]
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind+0x2a)[0x7f6ac7d45cea]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_private_constructed+0x49b)[0x7f6ac93a880b]
> /usr/lib/evolution/libevolution-shell.so.0(+0x250bc)[0x7f6ac93a50bc]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x157a0)[0x7f6ac79f67a0]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0)[0x7f6ac79f8460]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0x99)[0x7f6ac79f87d9]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_new+0x3b)[0x7f6ac93a51ab]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_create_shell_window+0xd5)[0x7f6ac9395765]
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#883977: *** stack smashing detected ***: evolution terminated

[Joachim Breitner]

Package: evolution-data-server
Version: 3.26.2.1-1.1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

marking this as grave under the assumption that I am not the only one
affected, please downgrade if it is specific to my setup for some
reason.

I just upgraded evolution-data-server from 3.26.2.1-1 to 3.26.2.1-1.1,
and now evolution will not start again: Even before a windows appears, I
get the backtrace further down.  The various eds components start
successfully. Removing ~/.cache/evolution does not help.

I have no idea what went wrong, but obviously things are failing quite
badly…

Cheers,
Joachim



~ $ evolution
*** stack smashing detected ***: evolution terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7230b)[0x7f6ac43b630b]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f6ac4441957]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f6ac4441920]
/usr/lib/x86_64-linux-gnu/libecal-1.2.so.19(+0x3d30c)[0x7f6ab799b30c]
/usr/lib/evolution/libevolution-calendar.so.0(+0x97163)[0x7f6a90318163]
/usr/lib/evolution/libevolution-calendar.so.0(+0x9d197)[0x7f6a9031e197]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
/usr/lib/evolution/libevolution-calendar.so.0(e_cal_model_set_time_range+0xe1)[0x7f6a902d2b91]
/usr/lib/evolution/modules/module-calendar.so(+0x20a49)[0x7f6a8ea16a49]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_get_shell_view+0xb7)[0x7f6ac93a5797]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_set_active_view+0x42)[0x7f6ac93a6692]
/usr/lib/evolution/libevolution-shell.so.0(+0x27176)[0x7f6ac93a7176]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_setv+0x23e)[0x7f6ac79f8a4e]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_set_property+0x1e)[0x7f6ac79f99de]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10dcc3)[0x7f6ac7d42cc3]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind_with_mapping+0x311)[0x7f6ac7d459c1]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind+0x2a)[0x7f6ac7d45cea]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_private_constructed+0x49b)[0x7f6ac93a880b]
/usr/lib/evolution/libevolution-shell.so.0(+0x250bc)[0x7f6ac93a50bc]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x157a0)[0x7f6ac79f67a0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0)[0x7f6ac79f8460]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0x99)[0x7f6ac79f87d9]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_new+0x3b)[0x7f6ac93a51ab]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_create_shell_window+0xd5)[0x7f6ac9395765]
evolution(+0x432f)[0x55d1949af32f]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7f6ac7717e15]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4b1e0)[0x7f6ac77181e0]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xc2)[0x7f6ac77184f2]
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main+0x85)[0x7f6ac8200345]
evolution(main+0x6d4)[0x55d1949af144]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f6ac4364561]
evolution(_start+0x2a)[0x55d1949af1fa]
=== Memory map: 
55d1949ab000-55d1949b2000 r-xp  fd:01 12719680   
/usr/bin/evolution
55d194bb2000-55d194bb3000 r--p 7000 fd:01 12719680   
/usr/bin/evolution
55d194bb3000-55d194bb4000 rw-p 8000 fd:01 12719680   
/usr/bin/evolution
55d1955c2000-55d196b22000 rw-p  00:00 0  [heap]
7f6a5000-7f6a50022000 rw-p  00:00 0 
7f6a50022000-7f6a5400 ---p  00:00 0 
7f6a5400-7f6a54022000 rw-p  00:00 0 
7f6a54022000-7f6a5800 ---p  00:00 0 
7f6a5800-7f6a58022000 rw-p  00:00 0 
7f6a58022000-7f6a5c00 ---p  00:00 0 
7f6a5e7fd000-7f6a5e7fe000 ---p  00:00 0 
7f6a5e7fe000-7f6a5effe000 rw-p  00:00 0 
7f6a5effe000-7f6a5efff000 ---p  00:00 0 
7f6a5efff000-7f6a5f7ff000 rw-p  00:00 0 
7f6a5f7ff000-7f6a5f80 ---p  00:00 0 
7f6a5f80-7f6a6000 rw-p  00:00 0 
7f6a6000-7f6a60022000 rw-p  00:00 0 
7f6a60022000-7f6a6400 ---p  00:00 0 
7f6a6400-7f6a64022000 rw-p  00:00 0 
7f6a64022000-7f6a6800 ---p  00:00 0 
7f6a6800-7f6a68022000 rw-p  00:00 0 
7f6a68022000-7f6a6c00 ---p  00:00 0 

Bug#883278: Offer non-linear stepping

[Joachim Breitner]

Package: xbacklight
Version: 1.2.1-1+b2
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

at least on my device, the perceived brightness is rather non-linear:
Going from 100 to 95 is almost not noticable, but going from 10 to 5 is
a big step, where I wish there were steps in between.

I would appreciate options (`-relinc`, `-reldec`) that change the
brightness on a logarithmic (or similar) scale, so that each steps
“feels” the same.

Joachim

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xbacklight depends on:
ii  libc6  2.24-17
ii  libxcb-randr0  1.12-1
ii  libxcb-util0   0.3.8-3+b2
ii  libxcb11.12-1

xbacklight recommends no packages.

xbacklight suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCWiFsFhMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBs+y4AoMSi6uGRQ05SprSy334sBrtnO5eZAKCl
6p46ocUUx6FmrCJ6TD/dz0gAqg==
=NTao
-END PGP SIGNATURE-

Bug#881753: closed by Joachim Breitner <nome...@debian.org> (Bug#881753: fixed in local-apt-repository 0.5)

[Joachim Breitner]

Hi,

Am Dienstag, den 14.11.2017, 23:49 +0100 schrieb Andreas Beckmann:
> On 11/14/2017 11:24 PM, Debian Bug Tracking System wrote:
> >* Make sure /etc/apt/sources.list.d/ exists only when package is 
> > installed
> >  (but not removed but not purged) (Closes: #881753)
> 
> That sounds like postrm remove: 'rm -rf /etc/apt/sources.list.d/' which
> made me curious :-) (Good, it doesn't do *that* rm)
> 
> I think your postinst wants a 'ln -sf' (otherwise it may fail on
> reinstall/upgrade if the link exists already).
> And you may want a .maintscript to rm_conffile the old conffile properly.

thanks for the suggestions, they are now in 0.6

Cheers,
Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#881753: local-apt-repository: breaks apt operation if removed

[Joachim Breitner]

Hi Felipe,

this just came in. Since you last worked on this package, would you be
interesting in fixing this bug?

Thanks,
Joachim

Am Dienstag, den 14.11.2017, 20:30 +0100 schrieb Andreas Beckmann:
> Package: local-apt-repository
> Version: 0.4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package can cause problems.
> 
> If local-apt-repository is removed (but not purged) from stretch,
> /etc/apt/sources.list.d/local-apt-repository.list is left behind.
> 
> Subsequent 'apt-get update' will fail since the repository is no longer
> available:
> 
> 4m5.4s ERROR: Command failed (status=100): ['chroot', 
> '/tmp/piupartss/tmpeMVqg3', 'apt-get', 'update']
>   Get:1 file:/var/lib/local-apt-repository ./ InRelease
>   Ign:1 file:/var/lib/local-apt-repository ./ InRelease
>   Get:2 file:/var/lib/local-apt-repository ./ Release
>   Ign:2 file:/var/lib/local-apt-repository ./ Release
>   Get:3 file:/var/lib/local-apt-repository ./ Sources
>   Ign:3 file:/var/lib/local-apt-repository ./ Sources
>   Get:4 file:/var/lib/local-apt-repository ./ Packages
>   Ign:4 file:/var/lib/local-apt-repository ./ Packages
>   Get:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Get:3 file:/var/lib/local-apt-repository ./ Sources
>   Ign:3 file:/var/lib/local-apt-repository ./ Sources
>   Get:4 file:/var/lib/local-apt-repository ./ Packages
>   Ign:4 file:/var/lib/local-apt-repository ./ Packages
>   Get:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Get:3 file:/var/lib/local-apt-repository ./ Sources
>   Ign:3 file:/var/lib/local-apt-repository ./ Sources
>   Get:4 file:/var/lib/local-apt-repository ./ Packages
>   Ign:4 file:/var/lib/local-apt-repository ./ Packages
>   Get:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Get:3 file:/var/lib/local-apt-repository ./ Sources
>   Ign:3 file:/var/lib/local-apt-repository ./ Sources
>   Get:4 file:/var/lib/local-apt-repository ./ Packages
>   Ign:4 file:/var/lib/local-apt-repository ./ Packages
>   Get:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Get:3 file:/var/lib/local-apt-repository ./ Sources
>   Ign:3 file:/var/lib/local-apt-repository ./ Sources
>   Get:4 file:/var/lib/local-apt-repository ./ Packages
>   Ign:4 file:/var/lib/local-apt-repository ./ Packages
>   Get:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
>   Get:3 file:/var/lib/local-apt-repository ./ Sources
>   Err:3 file:/var/lib/local-apt-repository ./ Sources
> File not found - /var/lib/local-apt-repository/./Sources (2: No such file 
> or directory)
>   Get:4 file:/var/lib/local-apt-repository ./ Packages
>   Ign:4 file:/var/lib/local-apt-repository ./ Packages
>   Get:6 http://ftp.de.debian.org/debian buster InRelease [136 kB]
>   Get:7 http://ftp.de.debian.org/debian buster/main amd64 Packages [7258 kB]
>   Get:8 http://ftp.de.debian.org/debian buster/main Translation-en [5553 kB]
>   Fetched 12.9 MB in 18s (696 kB/s)
>   Reading package lists...
>   E: Failed to fetch file:/var/lib/local-apt-repository/./Sources  File not 
> found - /var/lib/local-apt-repository/./Sources (2: No such file or directory)
>   E: Some index files failed to download. They have been ignored, or old ones 
> used instead.
> 
> 
> Andreas
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#880683: Should not start system-wide tor server

[Joachim Breitner]

Package: ricochet-im
Version: 1.1.4-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

thanks for packaging ricochet-im. As far as I can tell, it depends on
`tor` because it starts, as the user and on-demand, a tor process. But
installing the `tor` package will start a system-wide tor process, which
is probably not the intention of someone installing ricochet.

A solution might be to provide a `tor-bin` package that both `tor` and
`ricochet-bin` can depend upon, and `tor` ships the system-wide settings
(systemd file etc.).

Thanks,
Joachim


- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ricochet-im depends on:
ii  libc62.24-17
ii  libgcc1  1:7.2.0-11
ii  libgl1   0.2.999+git20170802-5
ii  libprotobuf103.0.0-9.1
ii  libqt5core5a 5.9.1+dfsg-12
ii  libqt5gui5   5.9.1+dfsg-12
ii  libqt5multimedia55.9.1-3
ii  libqt5network5   5.9.1+dfsg-12
ii  libqt5qml5   5.9.1-6
ii  libqt5quick5 5.9.1-6
ii  libqt5widgets5   5.9.1+dfsg-12
ii  libssl1.11.1.0f-5
ii  libstdc++6   7.2.0-11
ii  libubsan07.2.0-11
ii  qml-module-qtmultimedia  5.9.1-3
ii  qml-module-qtquick-controls  5.9.1-2
ii  qml-module-qtquick-dialogs   5.9.1-2
ii  tor  0.3.1.7-1

ricochet-im recommends no packages.

ricochet-im suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCWfyy5hMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsWBMAmwUgk0DmXQhWbOD2so5eT4j4NfQHAJwM
v1Sh2LAvRbqthqv2Gonpkn8XaQ==
=mMNV
-END PGP SIGNATURE-

Bug#846500: Please move the canonical bug urls from /cgi-bin/bugreport.cgi?bug=X → /X

[Joachim Breitner]

Hi,

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631480
sorry, I mean https://bugs.debian.org/631480
for the corresponding bug against debbugs.

Greetings,
Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#871216: debian/bin/test-patches does not build arch-indep packages

[Joachim Breitner]

Package: src:linux
Version: 4.12.2-1~exp1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

following the advice on
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html
under “Simple patching and building” I used debian/bin/test-patches to
apply some patches I need to test. Unfortunately, this produces only the
arch dependent file:
../linux-headers-4.12.0-trunk-amd64_4.12.2-1~exp1a~test_amd64.deb
../linux-image-4.12.0-trunk-amd64_4.12.2-1~exp1a~test_amd64.deb
../linux-image-4.12.0-trunk-amd64-dbg_4.12.2-1~exp1a~test_amd64.deb
and linux-headers-4.12.0-trunk-amd64 depends on
linux-headers-4.12.0-trunk-common (= 4.12.2-1~exp1a~test)
which does not exist. Since the package version was adjusted, I cannot
just use the version of the archive.

I believe debian/bin/test-patches should also build the arch independent
packages, to produce an actually installable set of .debs.

Thanks,
Joachim



- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iHAEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCWYeoMRMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBswD8AljP9fp1cG0WLpCsxjjwGFJcQAzkAmwZb
uXg4dDzM0ZrLDdR7u2si9kLP
=635T
-END PGP SIGNATURE-

Bug#864256: unblock: lhs2tex/1.19-5

[Joachim Breitner]

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

Please unblock package lhs2tex

it fixes the seroius bug #864225

unblock lhs2tex/1.19-5

Patch below:

diff -Nru lhs2tex-1.19/debian/changelog lhs2tex-1.19/debian/changelog
--- lhs2tex-1.19/debian/changelog   2016-10-27 18:37:21.0 -0400
+++ lhs2tex-1.19/debian/changelog   2017-06-05 12:29:08.0 -0400
@@ -1,3 +1,9 @@
+lhs2tex (1.19-5) unstable; urgency=high
+
+  * Depend on texlive-science (closes: #864225)
+
+ -- Joachim Breitner <nome...@debian.org>  Mon, 05 Jun 2017 12:28:59 -0400
+
 lhs2tex (1.19-4) unstable; urgency=medium
 
   * Upload to unstable as part of GHC 8 transition.
diff -Nru lhs2tex-1.19/debian/control lhs2tex-1.19/debian/control
--- lhs2tex-1.19/debian/control 2016-10-27 18:37:21.0 -0400
+++ lhs2tex-1.19/debian/control 2017-06-05 14:01:10.0 -0400
@@ -21,7 +21,7 @@
 Multi-Arch: foreign
 Depends:
  texlive-latex-base,
- texlive-math-extra,
+ texlive-science,
  ${misc:Depends},
  ${shlibs:Depends},
 Description: Generates LaTeX code from literate Haskell sources


Thanks,
Joachim


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#862056: sm: please make it at least easier…

[Joachim Breitner]

Hi,

Am Dienstag, den 09.05.2017, 11:39 + schrieb Holger Levsen: 
> > I certainly don’t mind adding a short-hand flag for "-f white -b
> > black"
> 
> yay!

ok, I’ll implement that right away, as --invert / -i.
>  
> > I am playing with the idea (mostly independent) of adding Ctrl-I as
> > a shortcut to invert the colors. You can use that to flash the
> > audience, or to drum rhythmically to music…
> 
> I guess that would be sufficient to me, I could live well with
> starting sm and pressing a key-combo to bring it into the mode I
> like… 

Great! And you have the choice of using "sm -i" or "sm" and then Ctrl-I
> 
> (but maybe then, CTRL-F for flash and CTRL-I for invert? better for
> actual
> flashing ;-)

Nah, Flash is simply CTRL-I CTRL-I, no need for a separate keybinding.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#862056: sm: please make it at least easier…

[Joachim Breitner]

Hi,

I feel like a Republican Senator suddenly getting calls about changing
his mind about AHCA…

I certainly don’t mind adding a short-hand flag for "-f white -b black"
(note that you can use named colors there).

I tried it briefly right now. One annoying thing – with my setup at
least – is that the text field in the bottom is still in the colors of
my usual theme, which has a bright background.

The best way forward would be to figure out how to get rid of the
separate text field altogether and simply edit the large text (hiding
the caret after a short timeout).

The argument that an alias is impractical cannot be brought in favor of
a certain setting (unless there is a very clear majority for one
particular flavor); it is just moving the onus of doing this work to
other people. And why is it unfeasible to configure your 30 computer or
so? Don’t we all have our ways of shoving our ~/.bashrc to our many
users and computers? 

~ $ grep alias projekte/environment/skel/.bashrc 
alias ls='ls --color=auto'
alias grep='grep --color=auto'

Should sm start to read a configuration file?

I am playing with the idea (mostly independent) of adding Ctrl-I as a
shortcut to invert the colors. You can use that to flash the audience,
or to drum rhythmically to music…

Joachim


Am Montag, den 08.05.2017, 14:54 + schrieb Holger Levsen:
> Hi,
> 
> while I totally agree with lamby that the default should be changed
> (because I think it's actually the better default and not only the
> more better looking default) I'm not surprised that you (Joachim) as
> the author of this wonderful tool consider your taste and preferences
> to be a weighting factor, to say at least :-)
> 
> Still, I would suggest you try it (as default) for a few days… when I
> first saw the meeting with the inverse sm I was sceptical but after a
> short time I really liked it (more than the other way round.
> 
> And then, finally, please make it at least easier to swap the
> default, whatever it is or will be. "sm -f '#fff' -b '#000'" is not
> at all trivial to type and one of the very nice aspects of sm is how
> easy it is to use. 
> 
> And sure, one can alias that, but then I would need to alias this on
> 30 computers or so and this becomes impractical. So, please, add "sm-
> backwards", "ms" or something like this as an alias to the package
> (whether you change the default now or not).
> 
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#862056: screen-message: please invert the default colours

[Joachim Breitner]

Dear Chris,

Am Sonntag, den 07.05.2017, 22:47 +0100 schrieb Chris Lamb:
> Please invert the default colours for screen-message; a large white
> background is not very "hacker friendly" and almost physically
> painful to experience very late into the early hours…


the choice of default colors is obvious a contestable one, and there is
no single right answer. I prefer it this way (I mostly use sm during
talks, where the background tends to be bright). I think I’ll play the
“I wrote this, so I make the call” and also the “Changing a default
will upset a few people” card and not apply the patch.

I recommend you to use the bash alias feature to make sm behave the way
you prefer – just like people have been configuring their unix tools
for decades.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#862064: unblock: haskell-glut/2.7.0.10-4

[Joachim Breitner]

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

Please unblock package haskell-glut, to fix a rc problem with raincat:


diff -Nru haskell-glut-2.7.0.10/debian/changelog 
haskell-glut-2.7.0.10/debian/changelog
--- haskell-glut-2.7.0.10/debian/changelog  2016-10-27 18:33:52.0 
-0400
+++ haskell-glut-2.7.0.10/debian/changelog  2017-05-06 16:56:46.0 
-0400
@@ -1,3 +1,10 @@
+haskell-glut (2.7.0.10-4) unstable; urgency=medium
+
+  * Use extra-libraries: GLUT so that this properly links against libglut
+(Closes: 861976)
+
+ -- Joachim Breitner <nome...@debian.org>  Sat, 06 May 2017 16:56:46 -0400
+
 haskell-glut (2.7.0.10-3) unstable; urgency=medium
 
   * Upload to unstable as part of GHC 8 transition.
diff -Nru haskell-glut-2.7.0.10/debian/patches/series 
haskell-glut-2.7.0.10/debian/patches/series
--- haskell-glut-2.7.0.10/debian/patches/series 1969-12-31 19:00:00.0 
-0500
+++ haskell-glut-2.7.0.10/debian/patches/series 2017-05-06 16:54:24.0 
-0400
@@ -0,0 +1 @@
+use-extra-libraries
diff -Nru haskell-glut-2.7.0.10/debian/patches/use-extra-libraries 
haskell-glut-2.7.0.10/debian/patches/use-extra-libraries
--- haskell-glut-2.7.0.10/debian/patches/use-extra-libraries1969-12-31 
19:00:00.0 -0500
+++ haskell-glut-2.7.0.10/debian/patches/use-extra-libraries2017-05-06 
16:56:44.0 -0400
@@ -0,0 +1,25 @@
+Index: haskell-glut/GLUT.cabal
+===
+--- haskell-glut.orig/GLUT.cabal   2016-05-12 12:47:38.0 -0400
 haskell-glut/GLUT.cabal2017-05-06 16:55:16.164611101 -0400
+@@ -103,6 +103,7 @@
+   else
+ cpp-options: "-DCALLCONV=ccall"
+ cc-options: "-DUSE_DLSYM"
++extra-libraries: glut
+ 
+ executable BOGLGP01-OnYourOwn1
+   if !flag(BuildExamples)
+Index: haskell-glut/cbits/HsGLUT.c
+===
+--- haskell-glut.orig/cbits/HsGLUT.c   2016-05-12 12:47:38.0 -0400
 haskell-glut/cbits/HsGLUT.c2017-05-06 16:56:30.898637798 -0400
+@@ -66,7 +66,7 @@
+   handle = dlopen("/System/Library/Frameworks/GLUT.framework/GLUT", 
RTLD_LAZY | RTLD_GLOBAL);
+ }
+ #else
+-handle = dlopen("libglut.so", RTLD_LAZY | RTLD_GLOBAL);
++handle = dlopen(NULL, RTLD_LAZY | RTLD_GLOBAL);
+ #endif
+   }
+ 

unblock haskell-glut/2.7.0.10-4

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3

[Joachim Breitner]

Hi,

Am Samstag, den 06.05.2017, 21:09 +0100 schrieb James Cowgill:
> In haskell-glut 2.7.0.10 the behavior of loading libglut changed
> significantly. Before, it was linked in directly (using
> "extra-libraries") and dlopen(NULL) was used to access functions in
> it.
> In 2.7.0.10 the direct linking was removed and the loading is now
> done
> using dlopen("libglut.so").
> 
> This is bad because:
> - libglut.so is the wrong library (should be libglut.so.3)
> - Debian packages have lost the automatic dependency on freeglut3
> 
> This has caused raincat to stop working after it was binNMUed (see
> #861957). While it could be worked around by adding a "Depends:
> freeglut3-dev", this is a bit of a hack so it would be better of
> haskell-glut was fixed instead.

upstream has since then changed to code to try both libglut.so and
libglut.so.3:
https://github.com/haskell-opengl/GLUT/commit/a386914280dbc7e027e8ebbfe07774cde697e38d

Normal linking would indeed be preferable. This is the commit that removed it:
https://github.com/haskell-opengl/GLUT/commit/1b47ba6c8074dc163886baf5f3d5b1809501f19c
I inquired about the reason here:
https://github.com/haskell-opengl/GLUT/commit/1b47ba6c8074dc163886baf5f3d5b1809501f19c#commitcomment-22044194

Is this bug relevant for the release?

Greetings,
Joachim 

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#861806: ghc: Please add platform support for powerpcspe

[Joachim Breitner]

Hi,

thanks. Due to the freeze this will not happen immediately.

JFTR: The patch is not in 8.0.2 or 8.2 either, but might be in 8.4.

Greetings,
Joachim

Am Donnerstag, den 04.05.2017, 11:11 +0200 schrieb John Paul Adrian
Glaubitz:
> Source: ghc
> Version: 8.0.1-17
> Severity: normal
> Tags: patch
> User: debian-powe...@lists.debian.org
> Usertags: powerpcspe
> 
> Hi!
> 
> The attached patch adds support for powerpcspe. It builds GHC with --
> enable-
> unregisterised and adds a patch from upstream [1] which disables some
> PPC
> FPU code on powerpcspe.
> 
> Thanks,
> Adrian
> 
> > [1] https://ghc.haskell.org/trac/ghc/ticket/12075
> 
> --
>  .''`.  John Paul Adrian Glaubitz
>  : :' :  Debian Developer - glaub...@debian.org
>  `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>    `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#859845: yarssr: Segmentation Fault on Quit

[Joachim Breitner]

Dear Sebastian,

thanks for reporting this bug. I have not used yarssr myself in years,
and I believe upstream is not active either. If you (or someone else)
wants to get this bug fixed, a patch would be required.

I’d also be happy to let someone else take over this package.

Greetings,
Joachim

Am Freitag, den 07.04.2017, 13:18 -0400 schrieb Sebastian Wyngaard:
> Package: yarssr
> Version: 0.2.2-9
> Severity: normal
> 
> Dear Maintainer,
> 

> * What led up to the situation?
> I started yarssr from the command-line. Once started, if I quit yarssr through
> the context menu (right click) the application segfaults.
> 
> I was trying to debug why yarssr loses all my configuration settings and feeds
> after rebooting sometimes and noticed this segfault. I will submit a separate
> bug report for that since I'm not sure if it is related.
> 
> This is the output when I run "yarssr --debug" and then quit:
> 
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() called on: at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Encoding raw at /usr/share/yarssr/Yarssr.pm
> line 37,
>  line 1.
> GdkPixbuf-LOG **:   Dimensions: 24 x 24 at
> /usr/share/yarssr/Yarssr.pm line
> 37,  line 1.
> GdkPixbuf-LOG **:   Rowstride: 96, Length: 2328 at
> /usr/share/yarssr/Yarssr.pm line 37,  line 1.
> GdkPixbuf-LOG **:   Copy pixels == false at
> /usr/share/yarssr/Yarssr.pm
> line 37,  line 1.
> GdkPixbuf-LOG **: gdk_pixbuf_from_pixdata() 

Bug#839840: ghci segfaults on armel, related to doctest failure

[Joachim Breitner]

Hi,

Am Mittwoch, den 05.04.2017, 11:01 + schrieb Niels Thykier:
> 
> We got a double RC buggy ghc on armel (this bug plus #851373, which also
> affects armhf).  Unfortunately, I cannot see any progress on these bugs
> (this one has been without updates since Oct 2016 and the other one
> since Jan 2017).
> 
> It would be very unfortunate to release with packages we cannot compile
> (any longer), so I would prefer this being fixed or as a last resort,
> drop of ghc and all rdeps on armel+armhf.
> 
> Ideally, this resolution should happen fairly soon, so it does not end
> up stalling the release.

doctest (and more general, the interpreter) has been plaguing us since
years, and it has never worked flawless. Unfortunately, only very few
of us know about arm-specific compiler details (I don’t), so given that
we do not even know the precise cause, I don’t expect a quick fix.

Maybe erikd can give a better assessment.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#841401: chromium: doesn't update extensions

[Joachim Breitner]

Hi,

On Thu, 20 Oct 2016 11:08:14 +0200 Bruno Bierbaumer 
 Debian's Chromium package doesn't seem to be able to update the
installed extensions.
> Both the automatic update mechanism and manually triggering "Update
extensions now" in chrome://extensions/ don't work.
> 
> The raw Chromium build from https://download-chromium.appspot.com/ is
able to update the extensions.

I can confirm this behaviour.

Joachim
-- 

Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#840777: ITP: hotdoc -- documentation tool using CommonMark

[Joachim Breitner]

Hi,

Am Freitag, den 14.10.2016, 19:44 +0200 schrieb Andrew Shadura:
> It was previously based on pandoc, and a pandoc backend will be
> available again soon, but the dependency tree with a hard pandoc
> dependency was just too deep.

pandoc (the binary package) seems to have a reasonable set of
dependencies:
Depends: libc6 (>= 2.14), libffi6 (>= 3.0.4), libgmp10, liblua5.1-0, 
libluajit-5.1-2, libpcre3, libyaml-0-2, zlib1g (>= 1:1.1.4), pandoc-
data (>= 1.17.2~dfsg-1), pandoc-data (<< 1.17.2~dfsg-1.~)
What tree are you referring to?


Greetings,
Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#840561: pidgin-blinklight: Please announce supported hardware using AppStream

[Joachim Breitner]

Hi,

JFTR: I am happy to apply patches here, but do not plan to work on this
soonish.

(I no longer have hardware supported by pidgin-blinklight, and am happy
to share responsibilities.)

Greetings,
Joachim


Am Mittwoch, den 12.10.2016, 21:12 +0200 schrieb Petter Reinholdtsen:
> Package: pidgin-blinklight
> Version: 0.11.1-3
> Severity: wishlist
> User: p...@hungry.com
> Usertags: appstream-modalias
> 
> Hi.
> 
> The pidgin-blinklight package is one of the packages in the Debian
> archive that
> should be proposed for installation when a given hardware dongle is
> inserted or available.  Thanks to the appstream system, this can now
> be
> announced in a way other tools can use and act on.  I've written the
> isenkram system to ask the current user if hardware specific packages
> should be installed when a new dongle is installed or already present
> on
> a machine, and isenkram now uses appstream as one source for hardware
> to
> package mappings.
> 
> You can read more about this on my blog, 
> http://people.skolelinux.org/pere/blog/Using_appstream_with_ise
> nkram_to_install_hardware_related_packages_in_Debian.html >.
> 
> Instructions on how to create the metadata XML file can be found in
> https://wiki.debian.org/AppStream/Guidelines >.
> 
> It would be great if you could add an appstream metainfo file to the
> pidgin-blinklight package, with content similar to this:
> 
>   
>   
>    [...]
>    
>   dmi:*:pn*:pvrThinkPad*:rvn*
>    
>   
> 
> If there are other hardware ids or kernel modules also supported by
> the
> package, please add those too. :)
> 
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#840371: ITP: git-repo -- CLI utility to manage git services from your workspace

[Joachim Breitner]

Hi,

Am Dienstag, den 11.10.2016, 09:28 +0800 schrieb ChangZhuo Chen:
>  git-repo is a CLI tool to manage git services likes GitHub, GitLab,
> and
>  Bitbucket. It provides several commands to handle clone, gist, pull
>  request.

this looks nice, thanks for packaging.

Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#839940: RFP: ponymix -- CLI volume control for PulseAudio

[Joachim Breitner]

Package: wnpp
Severity: wishlist

* Package name: ponymix
  Version : 5
  Upstream Author : Dave Reisner
* URL : https://github.com/falconindy/ponymix
* License : MIT
  Programming Lang: C++
  Description : CLI volume control for PulseAudio

Ponymix is a command line mixer for PulseAudio.

I found that this is the most viable solution for scripting pulse
audio,
e.g. toggling volume and mic via keyboard shortcuts in my window
manager. I have been using it for a while now, and would like to see it
packaged in Debian, but I believe someone else might be more suited to
maintain a C++ package than me.

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#780578: Default retry configuration unsuitable and dangerous on i.e. laptops

[Joachim Breitner]

Hi,

On Mon, 16 Mar 2015 10:15:38 +0100 Joachim Breitner <nome...@debian.org
> wrote:
> I have been a hit a few times by a deficiency in the default retry
> configuration, that prevents any mail from being sent in this not
> uncommon situation:

just to indicate that this is still a problem for me: I just lost
another bunch of sent mails because of this (and noticed only a week
later).

Greetings,
Joachim

-- 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#837186: Loading certain (SSL?) sites like google.com and facebook.com aborts

[Joachim Breitner]

Package: firefox-esr
Version: 45.3.0esr-2
Severity: important
Control: notfound it 45.3.0esr-1

Hi,

after upgrading from 45.3.0esr-1 to 45.3.0esr-2 (and not any more after
downgrading from 45.3.0esr-2 to 45.3.0esr-1), when I try to navigate to
google.com or facebook.com, after about a second or so, the page loading
aborts. No error message shown -- just as if I pressed the abort button.

No extensions enabled.

Other SSL enabled pages work, so while judging from the changelog,
something TLS relatedis possible, I am not quite sure.

Greetings,
Joachim



-- Package-specific info:

-- Extensions information
Name: Deutsch (DE) Language Pack locale
Location: 
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-de
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: user-disabled

Name: Open in Browser
Location: ${PROFILE_EXTENSIONS}/openinbrow...@www.spasche.net.xpi
Status: enabled

Name: Perspectives
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/perspecti...@cmu.edu
Package: xul-ext-perspectives
Status: user-disabled

Name: Standard theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: user-disabled

Name: Web Developer
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{c45c406e-ab73-11d8-be73-000a95be3b12}
Package: xul-ext-webdeveloper
Status: user-disabled

Name: Yahoo Mail service
Status: enabled

-- Plugins information
Name: Evince Browser Plugin
Location: /usr/lib/mozilla/plugins/libevbrowserplugin.so
Package: browser-plugin-evince
Status: enabled

Name: GNOME Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled

Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled

Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled

Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3))
Location: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-8-plugin:amd64
Status: enabled

Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: enabled

Name: MozPlugger 1.14.5 handles QuickTime and Windows Media Player Plugin 
(1.14.5)
Location: /usr/lib/mozilla/plugins/mozplugger.so
Package: mozplugger
Status: enabled

Name: Shockwave Flash (11.2.202.632)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled


-- Addons package information
ii  browser-plugin 3.21.4-1 amd64plugin for web browsers to displa
ii  firefox-esr45.3.0esr-1  amd64Mozilla Firefox web browser - Ext
ii  firefox-esr-l1 45.3.0esr-1  all  German language package for Firef
ii  gnome-shell3.20.3-1+b1  amd64graphical shell for the GNOME des
ii  google-talkplu 5.41.3.0-1   amd64Google Talk Plugin
ii  icedtea-8-plug 1.6.2-3  amd64web browser plugin based on OpenJ
ii  mozplugger 1.14.5-2 amd64Plugin allowing external viewers 
ii  rhythmbox-plug 3.4-1amd64plugins for rhythmbox music playe
ii  xul-ext-perspe 4.6.4-1  all  verify HTTPS sites through notary
ii  xul-ext-webdev 1.2.5+repack all  web developer extension

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firefox-esr depends on:
ii  debianutils   4.8
ii  fontconfig2.11.0-6.7
ii  libasound21.1.2-1
ii  libatk1.0-0   2.21.90-2
ii  libc6 2.24-2
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.10-1
ii  libdbus-glib-1-2  0.108-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.2.0-3
ii  libgdk-pixbuf2.0-02.35.4-4
ii  libglib2.0-0  2.49.6-1
ii  libgtk2.0-0   2.24.30-4
ii  libhunspell-1.4-0 1.4.1-2
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.25-1
ii  libpango-1.0-0

Bug#834026: libghc-yi-rope-dev: links against libicu but doesn't depend on it

[Joachim Breitner]

Hi,

Am Montag, den 15.08.2016, 20:22 -0700 schrieb Sean Whitton:

> > But no dependency against libicu55.
> 
> libghc-yi-rope-dev depends on libghc-text-icu-dev (by means of a virtual
> package the latter provides), and libghc-text-icu-dev depends on
> libicu57.  If libicu57 went through a SONAME change and
> libghc-text-icu-dev was binNMU'd, we would also have to binNMU
> libghc-yi-rope-dev because there is no Haskell ABI stability.  So I
> believe that all required shared library dependency relationships are in
> place.

The problem is that the rebuilt libghc-text-icu-dev has, from the point
of view of the Haskell compiler, the same ABI. So no rebuilds of
libghc-yi-dev are triggered by our tools.

I believe the problem is the following: When linking libghc-yi-rope-
dev, ghc (or Caba?) will look at all its dependencies, and their
"extra-libraries" fields ("icuuc icui18n icudata" for text-icu) and
pass that to the linker (as "-licuuc -licui18n -licudata"). This is how
we get this unwanted dependency.

But since yi-rope does itself not actually use any of these symbols,
this is probably not required! And not passing these libraries here
should solve the problem.

Only when a haskell _program_ is (statically) linked, we want to do
this.

This seems to be done by
ppHsc2hs :: BuildInfo -> LocalBuildInfo -> ComponentLocalBuildInfo -> 
PreProcessor
in Cabal/Distribution/Simple/PreProcess.hs.

I only found one relevant upstream ticket, see
https://ghc.haskell.org/trac/ghc/ticket/9498
which talks about related problems, but might fix this one.
https://ghc.haskell.org/trac/ghc/wiki/LinkingHaskell is also a good
read.

If someone feels bold he could change the Cabal code to pass linker
flags on for direct C dependencies and see if that works.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#834368: gnupg: update to gnupg2 broke gpg-agent autostart

[Joachim Breitner]

Hi,

On Mon, 15 Aug 2016 07:57:43 +0900 Norbert Preining 
wrote:
> Do you have any idea on how to fix this complete misbehaviour?

I stumbled over the same problem. I tried to fix this using
$ systemctl --user enable gpg-agent
and
$ systemctl --user start gpg-agent
and indeed it would start the gpg-agent, but using it failed with

sign_and_send_pubkey: signing failed: agent refused operation

I did not further debug it, but one guess is that there is no DISPLAY
variable set, so pinentry fails?

Then I found in gpg-agent(1) an entry that says

In  case  you want to use the included Secure Shell Agent you may
start the agent using:

 gpg-connect-agent /bye

So I added that to my session file, but I’m not sure if it is the right
way of doing it.

Greetings,
Joachim


-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Joachim Breitner]

Hi,

Am Mittwoch, den 10.08.2016, 15:38 + schrieb Mattia Rizzolo:
> On Wed, Aug 10, 2016 at 02:44:00PM +, Clint Adams wrote:
> > 
> > On Wed, Aug 10, 2016 at 07:44:25AM +, Mattia Rizzolo wrote:
> > > 
> > > : can't load .so/.DLL for: /usr/lib/haskell-
> > > packages/ghc/lib/x86_64-linux-ghc-7.10.3/pandoc-citeproc-0.9.1.1-
> > > H4nKjmy3LdhAeupsyJYDB0/libHSpandoc-citeproc-0.9.1.1-
> > > H4nKjmy3LdhAeupsyJYDB0-ghc7.10.3.so (libicuuc.so.55: cannot open
> > > shared object file: No such file or directory)
> > 
> > Looks like haskell-pandoc-citeproc needs to be rebuilt against the
> > new libicu-dev and then haskell-blogliterately can be given back.
> 
> umh, usually don't you have complex dependency chains preventing this
> kind of failures?

we do have that for Haskell ABI changes, but I believe it does not
cover the names of shared C libraries. Maybe that can be considered a
bug, and something that can be fixed on the GHC side. If someone wants
to dig deeper, I’ll happily assist.

Greetings,
Joachim



-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Joachim Breitner]

Hi,

Am Mittwoch, den 10.08.2016, 14:44 + schrieb Clint Adams:
> On Wed, Aug 10, 2016 at 07:44:25AM +, Mattia Rizzolo wrote:
> > 
> > : can't load .so/.DLL for: /usr/lib/haskell-
> > packages/ghc/lib/x86_64-linux-ghc-7.10.3/pandoc-citeproc-0.9.1.1-
> > H4nKjmy3LdhAeupsyJYDB0/libHSpandoc-citeproc-0.9.1.1-
> > H4nKjmy3LdhAeupsyJYDB0-ghc7.10.3.so (libicuuc.so.55: cannot open
> > shared object file: No such file or directory)
> 
> Looks like haskell-pandoc-citeproc needs to be rebuilt against the
> new libicu-dev and then haskell-blogliterately can be given back.

just nmu’ed haskell-pandoc-citeproc on all architectures.

Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#833536: pkg-haskell-tools: dht should allow uploading by FTP

[Joachim Breitner]

Hi,

Am Samstag, den 06.08.2016, 11:47 +0200 schrieb Sven Bartscher:
> On Fri, 05 Aug 2016 19:19:47 -0400
> Anyways, "dht upload" should simply allow passing a parameter
> > > > to dput
> > > > as HOST. Any maybe anyone who wants a non-default HOST should figure
> > > > out how to change dput’s defaults…  
> > > 
> > > It seems wrong that I should define ssh-upload to actually upload to FTP
> > > in my ~/.dput.cf.  Anyway, yes, passing a parameter to override the
> > > default seems like the right solution.  
> > 
> > With "someone" I meant me, not you: "dht upload" should just call dput,
> > and I should be able to tell dput to use ssh-upload by default.
> 
> You can set the default host by settings default_host_main in the
> [DEFAULT] section to ssh-upload in you dput.cf.

perfect! I have no qualms any more about dht _not_ setting any host
whatsoever, and possibly supporting an option to set the host.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#833536: pkg-haskell-tools: dht should allow uploading by FTP

[Joachim Breitner]

Hi,

Am Freitag, den 05.08.2016, 15:47 -0700 schrieb Sean Whitton:
> Hello,
> 
> On Fri, Aug 05, 2016 at 03:04:06PM -0400, Joachim Breitner wrote:
> > 
> > the reason is that I have had many FTP uploads fail and partial files
> > blocking further uploaing, which is a PITA. With ssh, partial uploads
> > do not happen (I think).
> > 
> > Anyways, "dht upload" should simply allow passing a parameter to dput
> > as HOST. Any maybe anyone who wants a non-default HOST should figure
> > out how to change dput’s defaults…
> 
> It seems wrong that I should define ssh-upload to actually upload to FTP
> in my ~/.dput.cf.  Anyway, yes, passing a parameter to override the
> default seems like the right solution.

With "someone" I meant me, not you: "dht upload" should just call dput,
and I should be able to tell dput to use ssh-upload by default.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#833536: pkg-haskell-tools: dht should allow uploading by FTP

[Joachim Breitner]

Hi,

Am Freitag, den 05.08.2016, 09:47 -0700 schrieb Sean Whitton:
> Package: pkg-haskell-tools
> Version: 0.10.3
> Severity: normal
> 
> Hello,
> 
> Is there some reason that dht's upload subcommand uploads to ftp-
> master
> with SSH rather than FTP?  This prevents Debian Maintainers from
> using
> the command to upload.
> 
> If there is no good reason, we could change it to use FTP.
> Alternatively, we could add a command line flag to select FTP or SSH
> --
> not sure what the default should be.

the reason is that I have had many FTP uploads fail and partial files
blocking further uploaing, which is a PITA. With ssh, partial uploads
do not happen (I think).

Anyways, "dht upload" should simply allow passing a parameter to dput
as HOST. Any maybe anyone who wants a non-default HOST should figure
out how to change dput’s defaults…

Greetings,
Joachim


-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#724629: [Pkg-fonts-devel] Package for Fira Sans and Fira Mono

[Joachim Breitner]

Hi,

On Mon, 23 Jun 2014 09:45:38 +0800 Paul Wise  wrote:
> On Mon, 2014-06-23 at 00:26 +0200, Rüdiger Sonderfeld wrote:
> 
> > They have now added the UFO files to the github repo.  I haven't updated 
> > the 
> > package yet.  But it should now be good enough for Debian main, right?
> > 
> > * https://github.com/mozilla/Fira/issues/25#issuecomment-46699424
> > * https://github.com/mozilla/Fira/tree/master/source/UFO%20%28Beta%29
> 
> It sounds like the author is still using the Glyphs app but saving and
> loading UFO instead of the Glyphs format. That seems acceptable.
> 
> http://dev.carrois.com/fira-3-1/
> 
> However, we are missing a way to build the fonts from the UFO sources.

it’s been two years… Is still someone trying to get this into Debian?

(I’ll use https://github.com/eddelbuettel/pkg-fonts-fira for now.)

Thanks,
Joachim


-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#832263: hledger: Section should not be “haskell”

[Joachim Breitner]

Hi,

the package meta data is correct since at least a year. I guess someone
just has to do the bureaucratic act with the override file.

Greetings,
Joachim

Am Samstag, den 23.07.2016, 23:23 +1000 schrieb Ben Finney:
> Package: hledger
> Version: 0.27-1+b2
> Severity: minor
> 
> Dear Maintainer,
> 
> The section “haskell” is for packages that install the Haskell
> programming language or libraries. Its packages are primarily of
> interest only to Haskell programmers.
> 
> The package ‘hledger’ installs primarily an application, of interest
> regardless of the programming language. It should not be in the
> “haskell” section.
> 
> By the section descriptions, this package may belong in section
> “utils”.
> 
> Please set the field “Section” appropriately on this package.
> 
> 
> Since the package is already in Debian with a different section, you
> will also need to submit a request to override the existing section
>  html#override-file>;.
> 
> Then mark this bug report as blocked by that new one, and be sure not
> to close this one until that new one is completed.
> 
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#832144: cabal-install: built inconsistently across different platforms

[Joachim Breitner]

Dear Apollon,



Am Freitag, den 22.07.2016, 22:45 +0300 schrieb Apollon Oikonomopoulos:
> Package: cabal-install
> Version: 1.22.9.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> It looks like cabal-install has been built inconsistently on different 
> architectures wrt. libghc-cabal-dev: on amd64 it has been built using 
> libghc-cabal-dev 1.22.8.0, while on i386 (and presumably the rest of the 
> autobuilder archs) it has been built using libghc-cabal-dev 1.22.5.0 
> which is provided by ghc 7.10.
> 
> As a result, cabal install produces different dist/setup-config output 
> depending on the architecture, requiring different versions of 
> libghc-cabal-dev to parse. This currently breaks the build of ganeti on 
> most architectures except amd64[1].

do you use "cabal install" in Debian packaging scripts? This is usually
not required and not recommended.

But yes, we should reliably build cabal-install with libghc-cabal-dev,
I guess.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#831662: Git sh prompt expands glob in commit message

[Joachim Breitner]

Hi,

Am Montag, den 18.07.2016, 11:44 +0200 schrieb Joachim Breitner:
> A fix is probably to put quotes around $(git log ...).

Possibly not, the script seems to rely on the shell’s splitting of
words here, which would be prevented by quotes.

> This might be security relevant.

I could not make it execute arbitrary code so far, but a denial of
service using
/*/*/*/*/*/
in the commit message works.


Greetings,
Joachim

-- 

Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#831662: Git sh prompt expands glob in commit message

[Joachim Breitner]

Package: git
Version: 1:2.8.1+next.20160414-1
Severity: normal
File: /usr/lib/git-core/git-sh-prompt

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I run bash with "failglob", so I notice when scripts process data
involving ? or * without proper escaping. I noticed that this snipped in
/usr/lib/git-core/git-sh-prompt
is vulnerable:

# get the upstream from the "git-svn-id: ..." in a commit 
message
# (git-svn uses essentially the same procedure internally)
local -a svn_upstream
svn_upstream=($(git log --first-parent -1 \
--grep="^git-svn-id: 
\(${svn_url_pattern#??}\)" 2>/dev/null))
if [[ 0 -ne ${#svn_upstream[@]} ]]; then
svn_upstream=${svn_upstream[${#svn_upstream[@]} - 2]}
svn_upstream=${svn_upstream%@*}
local n_stop="${#svn_remote[@]}"
for ((n=1; n <= n_stop; n++)); do
svn_upstream=${svn_upstream#${svn_remote[$n]}}
done

if [[ -z "$svn_upstream" ]]; then
# default branch name for checkouts with no 
layout:
upstream=${GIT_SVN_ID:-git-svn}
else
upstream=${svn_upstream#/}
fi
elif [[ "svn+git" = "$upstream" ]]; then
upstream="@{upstream}"
fi
;;

If the commit message in question contains a ? or *, then bash complains.

A fix is probably to put quotes around $(git log ...).

This might be security relevant.

Greetings,
Joachim

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git depends on:
ii  git-man   1:2.8.1+next.20160414-1
ii  libc6 2.23-1
ii  libcurl3-gnutls   7.47.0-1
ii  liberror-perl 0.17-1.3
ii  libexpat1 2.2.0-1
ii  libpcre3  2:8.38-3.1
ii  perl-modules-5.22 [perl-modules]  5.22.2-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages git recommends:
ii  less 481-2.1
ii  openssh-client [ssh-client]  1:7.2p2-5
ii  patch2.7.5-1
ii  rsync3.1.1-3

Versions of packages git suggests:
ii  gettext-base  0.19.8.1-1
pn  git-arch  
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
pn  git-email 
pn  git-gui   
pn  git-mediawiki 
ii  git-svn   1:2.8.1+next.20160414-1
pn  gitk  
pn  gitweb

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAleMpPQACgkQ9ijrk0dDIGyE6ACaA8ygj1gOFt535YBdNeB3Eny4
vWEAoMJxCdyU4gzdoNLyokg8Ve2wgq90
=N+fZ
-END PGP SIGNATURE-

Bug#404082: Share data beween frontend and real package

[Joachim Breitner]

Hi,

JFTR, I have no need for this feature any more, and nothing to comment here. Do 
as you think is best.

Joachim 

Am 30. Juni 2016 16:39:23 MESZ, schrieb Paul Gevers <elb...@debian.org>:
>Control: tags -1 moreinfo
>
>Hi Joachim,
>
>Sorry that it took so long to get back to this issue. I took over
>dbconfig-common a while ago and are now at the stage where I can
>comment
>on this request.
>
>On Thu, 21 Dec 2006 17:50:45 + Joachim Breitner
><nome...@debian.org>
>wrote:
>> it would be nice if this scenario were supported:
>> 
>> Two package, one a frontend and one a real dbconfig package, should
>be
>> able to share the configuration by setting the same package name in
>the
>> calls to dbc_go.
>
>Close. What if you leave the package name as they really are, but
>provide the same dbname and dbuser in the config file of you
>(hypothetical) package?
>
>> Currently it seems to fail when the frontend package is purged,
>> confusing the other package.
>
>Yes, that is because the package name is the same, while that is not
>really true. It probably fails on the debconf templates being removed.
>
>> Note that I do not have that setup any more with my packages, so I
>don’t
>> have a developing test case. But it’s still a nice to have item :-)
>
>So I think this bug can be closed as already supported. Would be great
>if somebody could check this (maybe I need a example package in this
>area).
>
>Paul

Bug#828136: RM: agda [armel armhf] -- ROM; Too heavy to be built on arm*

[Joachim Breitner]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

in the latest version, agda is not reasonably buildable on weaker
architectures. In order to unblock the testing migration of Haskell
packages, please remove the binaries produced by the agda source
packages on armel and armhf.

Thanks,
Joachim

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlduX2QACgkQ9ijrk0dDIGzYSgCgmYcA101qb+PUI3NEvCx8ZnYd
NyEAoKOT+4x8Y4I+I1dHPYKPTxyDf+Zz
=Hgx0
-END PGP SIGNATURE-

Bug#827555: ITP: circle -- Show byte statistics as an ascii circle graph

[Joachim Breitner]

Hi,

Am Freitag, den 17.06.2016, 21:24 +0200 schrieb Roberto S. Galende:
> ok, maybe bytes-circle...
> That also means to change the name of the command, 
> or could I just change the name of the package?
> thanks

I would suggest to also change the command name, in order to avoid
conflicts with a future circle command that could come up.

Greetings,
Joachim

-- 

Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#827555: ITP: circle -- Show byte statistics as an ascii circle graph

[Joachim Breitner]

Hi,

Am Freitag, den 17.06.2016, 19:38 +0200 schrieb Roberto S. Galende:
> circle is a program that shows statistics about bytes contained
> in a file as an ascci circle graph of deviations from mean in sigma
> increments.

sounds like a fun tool, but in the interest of keeping the package name
space sane, I suggest to look for a less generic name. Maybe "ascii-
circle" or "bytes-circle"?

Greetings,
Joachim
-- 

Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#784316: Please do not remove hoauth

[Joachim Breitner]

Hi John,

nice to hear from you again.

Am Montag, den 30.05.2016, 15:40 -0500 schrieb John Goerzen:
> Hello folks,
> 
> I know I have had no time to work on my Haskell packages in awhile - but
> I am working to get them all into shape.
> 
> Bug 784316 requested twidge upgrade to hoauth2.  Unfortunately, twitter
> is still using OAuth 1.0A [1].  A request to support it in the hoauth2
> library was rejected for this reason. [2]   Therefore, hoauth is still
> required for building a twitter client, and therefore is still required
> for twidge.
> 
> The other fixes required are mostly trivial and I hope to fix the
> remaining items and add a number of features in the coming days as well.
> 
> Can we, therefore, keep hoauth in sid?

hmm, according to https://packages.qa.debian.org/h/hoauth.html you are
5 days too late to ask this.

Of course it can still be added back. I would be happier, though, if it
(hand twidge) were to enter stackage as well, as this gives us better
QA. It’s easy to do: http://www.stackage.org/authors

Greetings,
Joachim

PS: Happy landings from a fellow air-traveler (though unmotorized –
paragliding).


-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

signature.asc
Description: This is a digitally signed message part

Bug#788324: Unsupported on arches besides i386 and amd64

[Joachim Breitner]

Hi,

Am Samstag, den 14.05.2016, 07:10 + schrieb Jurica Stanojkovic:
> Removing assembly was discussed in previous posts here.
> 
> Please do note that new upstream patch is using assembly just for
> amd64 but not for i386 arch.
> That assembly code does work on i386 to, we just need to enable i386
> to use this part of code.
> 
> If we are using assembly on amd64, could we change upstream patch to
> use it on i386 to?

I’d say we should not change the upstream code without need. If you
think that the package would be better without assembly, or with
assembly also for i386, I suggest you discuss this with upstream.

Gruß,
Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#788324: Unsupported on arches besides i386 and amd64

[Joachim Breitner]

Hi,

Am Freitag, den 13.05.2016, 18:40 + schrieb Jurica Stanojkovic:
> There is a solution proposed on upstream.
> https://github.com/bos/criterion/commit/0673606c70ba22234b8908a8f30e8
> ea588c6d776
> 
> With solution proposed on upstream I was able to build package
> successfully on mips, mipsel, amd64 and i386.

thanks for testing.

> However this solution is using assembly code on amd64 and not for
> i386 and other archs.
> 
> If you think that we could remove assembly code completely, 
> I am sending a patch that use proposed solution but does not include
> assembly code.

Why do you want to remove the (presumably faster) code on amd64? I
don’t see a reason to diverge from upstream here.

We should simply upgrade the package to 1.1.1.0 to get the fix.

Greetings,
Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#823689: hlibrary.mk: libghc-*-doc.links files not respected

[Joachim Breitner]

Hi,

Am Samstag, den 07.05.2016, 16:31 -0700 schrieb Sean Whitton:
> hlibrary.mk doesn't appear to do anything directly with
> changelogs.  So
> I think that something else it does is breaking CDBS's standard call to
> dh_installchangelogs.  But looking at
> /usr/share/cdbs/1/rules/debhelper.mk I can't see what that would be.

it runs
    run rm -f debian/libghc-${CABAL_PACKAGE}-doc.links 
debian/libghcjs-${CABAL_PACKAGE}-doc.links
which in clean, which explains the problem, and writes to the file in
the install target for the -dev package.

    if [ "${DEB_ENABLE_HOOGLE}" = "yes" ]
then
run find debian/${PKG}/${htmldir} -name "*.txt" \
-printf "%p ${hoogle}/${PKG}.txt\n" >> 
debian/lib${hc}-${CABAL_PACKAGE}-doc.links
run sed -i s,^debian/lib${hc}-${CABAL_PACKAGE}-doc,, 
debian/lib${hc}-${CABAL_PACKAGE}-doc.links
fi

What is a saner way of doing this? Calling dh_link directly with all
required links as arguments?

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#823757: sm: fails to set background color with the -b option

[Joachim Breitner]

Dear Francesco,

Am Sonntag, den 08.05.2016, 17:30 +0200 schrieb Francesco Poli
(wintermute):
> Today I upgraded a number packages on a Debian testing box.
> After that, sm became unable to set the background color requested
> by the user with the -b option:
> 
>   $ sm -f lawngrenn -b black
> 
> currently results in lawngreen text on *white* background. No matter
> which color I pass as argument to the -b or --background= option,
> the background color stays white.
> 
> Since sm has not been upgraded, I think that this new misbehavior
> is due to some library upgrade.
> The only sm dependency among the upgraded packages is:
> 
>   [UPGRADE] libgtk-3-0:amd64 3.18.9-1 -> 3.20.3-2
> 
> As a consequence, I consider it the prime suspect.
> 
> I don't know whether this is a bug in libgtk-3-0 or something that
> needs to be adapted in sm. Please investigate and forward my report
> upstream or reassign it, as appropriate.
> 

I can confirm it; since probably that upgrade, I see unconditionally
grey background here. It seems that with that version of gtk, the theme
takes precedent over how I set the color, and I likely set it wrongly.

Would you be interested in tracking that down, and come up with a
patch?

Thanks,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#823689: hlibrary.mk: libghc-*-doc.links files not respected

[Joachim Breitner]

Hi,

Am Samstag, den 07.05.2016, 11:03 -0700 schrieb Sean Whitton:
> hlibrary.mk invokes dh_link to create symlinks specified in files
> matching debian/libghc-*-{dev,prof}.links, but it seems to ignore
> files matching debian/libghc-*-doc.links.
> 
> For a package displaying this problem please see the branch debian of
> git repository https://git.spwhitton.name/propellor

thanks for the report. Do you have a proposed fix?

(hlibrary.mk is a mess where everyone meddles; feel free to meddle
yourself.)

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#777158: Text functions segfault on i386

[Joachim Breitner]

Version: 8:6.8.9.9-5+deb8u1

Hi,

On Fri, 08 May 2015 15:23:47 +0200 Bas van Sisseren  
wrote:
> Package: libimage-magick-perl
> Version: 8:6.8.9.9-5
> Severity: normal
> 
> The PerlMagick/quantum/Makefile.PL was using the wrong
> magick/magick-baseconfig.h file. I've attached a patch to fix this problem.

this bug affects stable and, and given that the text editing features
of imagemagick are relatively important, I wonder if it warrants a
stable update? I’ve just built 8:6.8.9.9-5+deb8u1 with this patch
applied, and it solves the problem.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#822673: RM: infon-devel -- ROM; Unmaintained, depends on obsolete pygtksourceview2

[Joachim Breitner]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

see subject and #822587.

Thanks,
Joachim

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlcfQNwACgkQ9ijrk0dDIGwOFgCfWk5+4Gvs8mb4k9ZmSur9sqg8
ZGcAnj+vC+S/tFlZvLLUZIZjBqqjKlVl
=LMbU
-END PGP SIGNATURE-

Bug#819585: local-apt-repository: add a "suite" name to local-apt-repository.list

[Joachim Breitner]

Dear Marintxo,

thanks for the suggestion! Maybe the Release file can have a suite
entry. Or alternatively, the local-apt-repository documentation can
give instructions on how to use apt-pinning to prefer packages from the
local repository? Or maybe even do that by default?

I don’t think I’ll do a deep investigation into the possibilities soon,
but I’m happy to review and merge tested patches!

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part

Bug#818483: nmu: haskell-network-protocol-xmpp_0.4.8-2

[Joachim Breitner]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

in order to fix #814055 and #813078, and prevent auto-removal of
git-annex in testing, without waiting for the current Haskell
transition, I believe it should help to binNMU
haskell-network-protocol-xmpp in testing:

nmu haskell-network-protocol-xmpp_0.4.8-2 . ANY . stretch . -m "rebuild against 
libgnutls30"

Thanks,
Joachim

- -- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlbqwl0ACgkQ9ijrk0dDIGxXaQCgjolWPuNlRYGBsUCD3+8xG572
YlYAoKWu6krw/4yAwr6id0Q9AMkFsb6N
=jRoK
-END PGP SIGNATURE-

Bug#818354: RM: kicad [kfreebsd-amd64 kfreebsd-i386] -- RoQA; B-D recursively unavailable on kfreebsd

[Joachim Breitner]

Hi,

On Fri, 18 Mar 2016 17:07:37 + Steven Chamberlain  
wrote:
> Control: block -1 by 815519
> 
> Steven Chamberlain wrote:
> > Actually please hold off on that...  the issue that led to pandoc
> > removeal already has a patch in the BTS, though I forget which package
> > was the root cause of this.
> 
> That was http://bugs.debian.org/815519 in haskell-mockery
> 
thanks for the ping, uploading with that patch as I speak.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


signature.asc
Description: This is a digitally signed message part