Bug#965025: Acknowledgement (gpsshogi-data: data does not seem to be provided in the preferred format for modification)

[ydirson]

close 965025
thanks

upstream clarification from Daigo:

> We (as the upstream) created an opening book file and
> evaluation files in a statistical / machine learning
> way from a large amount of data with lots of machine
> power and tuning parameters. It was not our priority
> to develop an out-of-box environment of tools and data
> for exactly mirroring what we produced. However, it
> would be capable of power programmers to customize the
> binary files by reading and using APIs defined in OSL.
> Say, they could put more weight on Bishop or ban some
> moves in an opening position.

Bug#965153: gscan2pdf: "fails to open device" for Epson NX100

[ydirson]

Package: gscan2pdf
Version: 2.8.0-1, 2.8.1-1
Severity: grave

Except for a couple of times I've been able to get it to work (without knowing
what it was that made it finally work after minutes of battle)...

* when I start gscan2pdf it claims it does not see my scanner and offers to 
rescan
  or continue without
* rescanning sometimes get me back to this window, sometimes to main screen
* from main screen when I click the scan button, I often get the same complaint
* sometimes I get to the scan dialog with "Epson NX100" properly selected, but 
then
  launching the scan it complains that it "first has to open the device" (good 
guess,
  but I'd thought it would do that for me). After which the UI is completely 
unresponsive
  and I have to kill the app

Upgrading to unstable just adds me a "restart gscan2pdf" in the initial failure 
dialog,
but that does not help either.

Downgrading to stable's 2.3.0-1 gets me back a fully working version.

Bug#963983: closed by Gianfranco Costamagna (Re: python3-pyside2.qtsvg: segfault on import)

[ydirson]

reopen 963983
thanks

The other pyside2 packages (code, gui etc) were still at 5.15.0-1~exp1.

If I just update qtsvg to 5.15.0-2 the segfault still happens.

Update the rest of pyside2 triggers a huge cascading of upgrades to Qt 5.14
which had not been done when I had installed the exp packages, and when I
updated qtsvg initially.

Among them:

 Unpacking libqt5svg5:amd64 (5.14.2-2) over (5.12.5-2) ...

With all this upgraded, I confirm there is no segfault any more.

Thus, the problem is likely caused by an undeclared versioned dependency on an
underlying lib, and libqt5svg5 looks like a good candidate.  

Not dealing with it is likely to lead to other insufficient partial updates.

Bug#963983: python3-pyside2.qtsvg: segfault on import

[ydirson]

Package: python3-pyside2.qtsvg
Version: 5.15.0-1
Severity: grave

$ gdb python3
...
Reading symbols from python3...
Reading symbols from 
/usr/lib/debug/.build-id/97/0f19629d98e5c631b44f6803fa34a5a07c3806.debug...

(gdb) r
Starting program: /usr/bin/python3 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.8.3 (default, May 14 2020, 11:03:12) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

>>> from PySide2 import QtSvg
Program received signal SIGSEGV, Segmentation fault.
0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*, char 
const*, char const*, PyType_Spec*, char const**, void (*)(void*), 
SbkObjectType*, _object*, unsigned int) ()
   from 
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15

(gdb) bt
#0  0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*, 
char const*, char const*, PyType_Spec*, char const**, void (*)(void*), 
SbkObjectType*, _object*, unsigned int)
() from 
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
#1  0x7731ec41 in ?? () from 
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#2  0x7732a6a3 in PyInit_QtSvg () from 
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#3  0x0067d0aa in _PyImport_LoadDynamicModuleWithSpec (
spec=, 
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, _set_fileattr=True, 
_cached=None) at remote 0x7760d1f0>, fp=) at 
../Python/importdl.c:164
#4  0x0067dafd in _imp_create_dynamic_impl (module=, 
file=, 
spec=, 
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, _set_fileattr=True, 
_cached=None) at remote 0x7760d1f0>) at ../Python/import.c:2221
#5  _imp_create_dynamic (module=, args=, 
nargs=) at ../Python/clinic/import.c.h:330
#6  0x005c066c in cfunction_vectorcall_FASTCALL (func=, args=, nargsf=, 
kwnames=) at ../Objects/methodobject.c:422
#7  0x005f1da9 in PyVectorcall_Call (callable=, tuple=, kwargs={}) at ../Objects/call.c:199
#8  0x0056d160 in do_call_core (kwdict={}, 
callargs=(, 
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, _set_fileattr=True, 
_cached=None) at remote 0x7760d1f0>,), func=, tstate=) at 
../Python/ceval.c:4983
#9  _PyEval_EvalFrameDefault (f=, throwflag=) at 
../Python/ceval.c:3559
#10 0x00565602 in PyEval_EvalFrameEx (throwflag=0, 
f=Frame 0x77677610, for file , line 219, 
in _call_with_frames_removed (f=, args=(, 
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, _set_fileattr=True, 
_cached=None) at remote 0x7760d1f0>,), kwds={})) at ../Python/ceval.c:741
#11 _PyEval_EvalCodeWithName (_co=, globals=, 
locals=, args=, argcount=, 
kwnames=, 
kwargs=0x776de7e0, kwcount=, kwstep=1, defs=0x0, 
defcount=0, kwdefs=0x0, closure=0x0, name='_call_with_frames_removed', 
qualname='_call_with_frames_removed')
at ../Python/ceval.c:4298
#12 0x005f12a3 in _PyFunction_Vectorcall (func=, 
stack=0x776de7d0, nargsf=, kwnames=) at 
../Objects/call.c:435
#13 0x0056c1bf in _PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x776de7d0, callable=) at 
../Include/cpython/abstract.h:127
#14 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x959e20) at ../Python/ceval.c:4963
#15 _PyEval_EvalFrameDefault (f=, throwflag=) at 
../Python/ceval.c:3469
#16 0x005f10c6 in PyEval_EvalFrameEx (throwflag=0, 
f=Frame 0x776de640, for file , 
line 1357, in create_module (self=, spec=, 
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, _set_fileattr=True, 
_cached=None) at remote 0x7760d1f0>)) at ../Python/ceval.c:741
#17 function_code_fastcall (globals=, nargs=, 
args=, co=) at ../Objects/call.c:283
#18 _PyFunction_Vectorcall (func=, stack=, 
nargsf=, kwnames=) at ../Objects/call.c:410
#19 0x005674c7 in _PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x777b2a30, callable=) at 
../Include/cpython/abstract.h:127
#20 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x959e20) at ../Python/ceval.c:4963
#21 _PyEval_EvalFrameDefault (f=, throwflag=) at 
../Python/ceval.c:3486
#22 0x005f10c6 in PyEval_EvalFrameEx (throwflag=0, 
f=Frame 0x777b28b0, for file , line 556, 
in module_from_spec (spec=, 
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, _set_fileattr=True, 
_cached=None) 

Bug#921220: xchat stops autoconnecting, complaining about "%U" and "host unknown", broken .desktop entry ?

[ydirson]

The control email got bounced before unarchiving, here are the details of new 
findings. 

- Mail original -

> unarchive 921220
> reopen 921220
> retitle 921220 xchat.desktop makes invalid use of %U, breaks at least
> lxqt and flwm
> affects 921220 + lxqt flwm
> severity 921220 grave
> thanks

> I've switched away from lxqt and forgot to follow up on this issue,
> but now I'm stumbling on a configure error of flwm,
> which qualifies as grave under the "breaks other package" rule.

> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Setting up flwm (1.02+git2015.10.03+7dbb30-6) ...
> Exec key for 'XChat IRC' contains '%F', '%U' or '%D' at the wrong
> place
> dpkg: error processing package flwm (--configure):
> installed flwm package post-installation script subprocess returned
> error exit status 255
> Errors were encountered while processing:
> flwm

> Note that the freedesktop standard [1] says "Field codes must not be
> used inside a quoted argument, the result of field code expansion
> inside a
> quoted argument is undefined", this could possibly be the reason for
> any complaint.

> If I replace the faulty line by just "Exec=xchat --existing --url %U"
> the flwm configure step does succeed, which seems to confirm this
> diagnostic.

> Probably the better solution would be to use a wrapper script, which
> could have saner behaviour (the current behaviour lauches "exec
> xchat"
> on any error of the first try, where it looks like what we really
> want is to launch it if %U is empty.

> https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s07.html

> - Mail original -

> > De: "Gianfranco Costamagna" 
> 
> > À: ydir...@free.fr, 921220-d...@bugs.debian.org
> 
> > Envoyé: Mardi 5 Février 2019 11:13:35
> 
> > Objet: Re: Bug#921220: xchat stops autoconnecting, complaining
> > about
> > "%U" and "host unknown", broken .desktop entry ?
> 

> > Hello,
> 

> > >OTOH when launched from cmdline the problem does not appear.
> 

> > >
> 

> > >And indeed the provided .desktop file shows:
> 

> > >
> 

> > >Exec=sh -c "xchat --existing --url %U || exec xchat"
> 

> > >
> 

> > >Could it be that there was a fix in a recently-dropped patch ?
> 

> > I didn't drop any patch (you didn't even tell me which was your
> > previous version, so its difficult to say)
> 
> > but looks like a network error to me
> 
> I guess at that time I made assumptions on not-so-recent "Drop old
> and useless patch" changelog entry, my bad.

Bug#939754: not found in stable

[ydirson]

notfound 939754 2.10.8-2
thanks

Downgrading to the build currently in buster works around the crash.

Bug#695873: memtest86+: Serial console does not work

[ydirson]

Hi,

Feel free do NMU - thanks much for this :)

- Mail original -
> De: "Louis-Philippe Véronneau" 
> À: 695...@bugs.debian.org
> Envoyé: Mardi 13 Août 2019 21:44:38
> Objet: Bug#695873: memtest86+: Serial console does not work
> 
> Hello!
> 
> I'd be happy to make an NMU to fix this, since:
> 
> * there is a patch
> * the patch was tested by 4 people and it seems to work
> * the patch looks trivial
> * the patch has been merged in Fedora [1]
> 
> I've emailed the maintainer directly to ask him if it would be OK
> with
> him for me to NMU this.
> 
> If I don't get an answer I'll look into fixing this by an NMU :)
> 
> Cheers,
> 
> [1]
> https://src.fedoraproject.org/rpms/memtest86+/blob/master/f/memtest86+-5.01-serial-console-fix.patch
> 
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
> 
> 

Bug#934265: qtbase5-dev: different archs ship different version of Qt-logo.png

[ydirson]

Package: qtbase5-dev
Version: 5.11.3+dfsg1-2+b1
Severity: serious

Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-01jgzV/14-qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb 
(--unpack):
 trying to overwrite shared 
'/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different 
from other instances of package qtbase5-dev:i386
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Bug#905674: proper severity

[ydirson]

Adam wrote:
> Note that parallel's functionality is also provided by moreutils and xargs
> -P, thus moving the package out of main would be just an inconvenience (four
> packages need to be adjusted: roary last-align freebayes symfony).

That may be true of the basic usage of the tool.

However, I just stumbled on this package through the "sem" tool (aka. "parallel 
--semaphore",
which seems by far the most compelling tool to prevent parallel execution of 
particular make
rules (eg. some launching git commands that require acquiring the same lock).

(that said, the fact the package cannot be installed alongside moreutils is 
another
blocker ;)

Bug#905674: Funding free software

[ydirson]

Hello Ole,

I do understand that funding Free Software is a problem of its own, but
I'm quite surprised to see a program with "GNU" in its name doing things
that way.  Is it a way of funding that is endorsed by the GNU project ?

Best regards,
-- 
Yann

Bug#900399: More good news

[ydirson]

severity 900399 normal
thanks

I suggest you get some advice from the forum[1], and as Dmitry mentionned, 
bring the issue to Lenovo.

[1] 
http://forum.canardpc.com/forums/73-Memtest86-Official-forum?s=1407c99a4da914ef85e60c32c658ba16

- Mail original -
> De: "Сергей Коган" 
> À: 900...@bugs.debian.org
> Envoyé: Jeudi 7 Juin 2018 15:26:43
> Objet: Bug#900399: More good news
> 
> Hi!
> 
> Let's lower the severity of this bug and flag it as unverified.
> 
> Given the datasheet for the TB62501 and actual board layout of the
> T500
> - the described scenario (short from the VCC3SW to GND caused by a
> stray
> write to the PMH register) is highly improbable:
> 
> - The LDO inside the RINKAN has an over-current protection set as low
> as
> 55mA and should prevent any damage even if the VCC3SW is shorted.
> After
> the single over-current/under-voltage event, RINKAN LDO is locked in
> the
> OFF state and requires a complete power-off to restart.
> 
> - Unused pins of the PMH are in fact floating
> 
> - Some RINKAN batches do show tendency to malfunction with no
> apparent
> reasons. The main board temperature could be a contributing factor.
> 
> So, we have to seriously consider the possibility that two laptops
> died
> at the same time just by a coincidence.
> 
> We do plan to run a memtest on the restored laptop using a current
> measuring/limiting circuit on the VCC3SW bus. If no excessive current
> consumption would be detected - the memtest has nothing to do with
> the
> issue. If an excessive current during the test would be observed, it
> would get us a direction to resume the investigation.
> 
> ---
> Sincerely yours,
> Sergey Kogan
> 

Bug#873642: weboob-qt: misses dependency on python-pyqt5.qtmultimedia

[ydirson]

Package: weboob-qt
Version: 1.2-1
Severity: serious

without it, qvideoob fails with:

$ qvideoob
Traceback (most recent call last):
  File "/usr/bin/qvideoob", line 24, in 
from weboob.applications.qvideoob import QVideoob
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/__init__.py", 
line 1, in 
from .qvideoob import QVideoob
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/qvideoob.py", 
line 24, in 
from .main_window import MainWindow
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/main_window.py", 
line 30, in 
from .video import Video
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/video.py", line 
23, in 
from PyQt5.QtMultimedia import QMediaContent, QMediaPlayer
ImportError: No module named QtMultimedia

Bug#864825: gammaray: crashes target program on attach

[ydirson]

Package: gammaray
Version: 2.7.0-1
severity: grave

When attaching to any Qt5 or Qt4 process, the target process crashes.
Here with a freshly-launched kwrite for demonstration:

#0  0x7f21b4fd96ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f21af8429f6 in g_main_context_poll (priority=, 
n_fds=1, fds=0x7f2194003020, timeout=, context=0x7f2194000990) 
at ././glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f2194000990, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
././glib/gmain.c:3924
#3  0x7f21af842b0c in g_main_context_iteration (context=0x7f2194000990, 
may_block=1) at ././glib/gmain.c:3990
#4  0x7f21b58ed06b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f21b58969ca in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f21b56c40f3 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f21b88b26d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f21b56c8da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f21b151e494 in start_thread (arg=0x7f21a0dfc700) at 
pthread_create.c:333
#10 0x7f21b4fe2aff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 1 (Thread 0x7f21a5b0a580 (LWP 31110)):
[KCrash Handler]
#4  0x7f219a2d65b1 in GammaRay::Server::listen() () from 
/usr/lib/libgammaray_core-qt5_7-x86_64.so.2.7.0
#5  0x7f219a294bd1 in GammaRay::Probe::delayedInit() () from 
/usr/lib/libgammaray_core-qt5_7-x86_64.so.2.7.0
#6  0x7f21b58c5499 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f21b617bb8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f21b6183341 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f21b58989e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f21b589b16d in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f21b58ecc43 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f21af8427f7 in g_main_dispatch (context=0x7f219c0016f0) at 
././glib/gmain.c:3203
#13 g_main_context_dispatch (context=context@entry=0x7f219c0016f0) at 
././glib/gmain.c:3856
#14 0x7f21af842a60 in g_main_context_iterate 
(context=context@entry=0x7f219c0016f0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3929
#15 0x7f21af842b0c in g_main_context_iteration (context=0x7f219c0016f0, 
may_block=1) at ././glib/gmain.c:3990
#16 0x7f21b58ed04f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f21b58969ca in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f21b589f13c in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x557eafc8198f in main ()

Bug#855788: 855788 severity

[ydirson]

FWIW, no such problem here. Is that high severity really warranted ?

Bug#833741: Patch updated for 1.8.3

[ydirson]

Updated Bob's patch, which was against 1.8.1, to 1.8.3.
This fixes both RC bugs, uploading a NMU hoping it's not too late...

diff --git a/debian/changelog b/debian/changelog
index e94d50a..965efd3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+pepperflashplugin-nonfree (1.8.4) unstable; urgency=medium
+
+  [ Bob Proulx ]
+  * Patched to use Adobe upstream rather than Google.
+  * Inspired by the patch provided in Bug#833741#15 by Kristian Klausen
+but rewritten.  Closes: #833741.
+  * Adds in 32-bit support.
+  
+  [ Yann Dirson ]
+  * Non-maintainer upload.
+  * Updated patch for 1.8.3
+
+ -- Yann Dirson   Sat, 14 Jan 2017 18:57:25 +0100
+
 pepperflashplugin-nonfree (1.8.3) unstable; urgency=medium
 
   * update-pepperflashplugin-nonfree:
diff --git a/debian/control b/debian/control
index 3e35edf..0e4f28d 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,6 @@ Pre-Depends: ca-certificates
 Suggests: chromium, ttf-mscorefonts-installer, ttf-dejavu, ttf-xfree86-nonfree, hal
 Conflicts: libflash-mozplugin, chromium (<< 37.0.2062.120-4)
 Description: Pepper Flash Player - browser plugin
- This package will download Chrome from Google, and unpack it to make the
+ This package will download Chrome from Adobe, and unpack it to make the
  included Pepper Flash Player available for use with Chromium.  The end user
- license agreement is available at Google.
+ license agreement is available at Adobe.
diff --git a/debian/install b/debian/install
index c4a3e4d..2b54a10 100644
--- a/debian/install
+++ b/debian/install
@@ -1,3 +1,2 @@
 update-pepperflashplugin-nonfree usr/sbin/
-pubkey-google.txt usr/lib/pepperflashplugin-nonfree/
 debian/etc/chromium.d/pepperflashplugin-nonfree etc/chromium.d/
diff --git a/debian/postinst b/debian/postinst
index 531d6dd..f7c7051 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -5,6 +5,9 @@ set -e
 case "$1" in
 configure)
 	update-pepperflashplugin-nonfree --install --fast || true
+	# Clean up the old Google debs as we are now using Adobe tar.gz files.
+	rm -rf /var/cache/pepperflashplugin-nonfree/*.deb
+	rm -rf /var/cache/pepperflashplugin-nonfree/latest-stable-verified.txt
 ;;
 
 abort-upgrade|abort-remove|abort-deconfigure)
diff --git a/update-pepperflashplugin-nonfree b/update-pepperflashplugin-nonfree
index 62aceb8..39784c6 100755
--- a/update-pepperflashplugin-nonfree
+++ b/update-pepperflashplugin-nonfree
@@ -17,12 +17,6 @@
 
 set -e
 
-return_0() {
-	return 0
-}
-
-trap "return_0" 0
-
 die_hard() {
 	echo "ERROR: $1" >&2
 	echo "More information might be available at:" >&2
@@ -30,7 +24,7 @@ die_hard() {
 	exit 1
 }
 
-[ `id -u` = "0" ] || die_hard "must be root"
+[ "$(id -u)" = "0" ] || die_hard "must be root"
 
 show_usage() {
 	echo "Usage:"
@@ -43,18 +37,16 @@ show_usage() {
 	exit 1
 }
 
-getopt_temp=`getopt -o iusfvq --long install,uninstall,status,fast,verbose,quiet,beta,unstable,unverified \
-	-n 'update-pepperflashplugin-nonfree' -- "$@"` || show_usage
-eval set -- "$getopt_temp" || show_usage
+getopt_temp=$(getopt -o iusfvq --long install,uninstall,status,fast,verbose,quiet \
+	-n 'update-pepperflashplugin-nonfree' -- "$@") || show_usage
+eval set -- "$getopt_temp"
 
 ACTION=none
 fast=no
 verbose=no
 quiet=no
-variant=stable
-verified=yes
 
-while [ true ]
+while [ $# -gt 0 ]
 do
 	case "$1" in
 		-i|--install)
@@ -81,18 +73,6 @@ do
 			quiet=yes
 			shift
 			;;
-		--beta)
-			variant=beta
-			shift
-			;;
-		--unstable)
-			variant=unstable
-			shift
-			;;
-		--unverified)
-			verified=no
-			shift
-			;;
 		--)
 			shift
 			break
@@ -109,106 +89,34 @@ done
 
 [ "$verbose" != "yes" ] || echo "options : $getopt_temp"
 
-latestfile=latest-$variant-verified.txt
-[ "$verified" != "no" ] || latestfile=latest-$variant.txt
-
-UNPACKDIR=`mktemp -d /tmp/pepperflashplugin-nonfree.XX` || die_hard "mktemp failed"
-echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia"
-cd "$UNPACKDIR" || die_hard "cd failed"
-
-[ "$verbose" != "yes" ] || echo "temporary directory: $UNPACKDIR"
-
-do_cleanup() {
-	[ "$verbose" != "yes" ] || echo "cleaning up temporary directory $UNPACKDIR ..."
-	cd /
-	echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia"
-	rm -rf "$UNPACKDIR"
-}
-
-die_hard_with_a_cleanup() {
-	return_0
-	do_cleanup
-	die_hard "$1"
-}
-
-trap "die_hard_with_a_cleanup interrupted" INT
+wgetquiet='-q'
+wgetfast='-t 3 -T 15'
+wgetprogress='-v --progress=dot:default'
+[ "$quiet" != "no" ] || wgetquiet=""
+[ "$fast" != "no" ] || wgetfast=""
+wgetoptions="$wgetquiet $wgetfast $wgetprogress"
+
+arch=""
+case $(dpkg --print-architecture) in
+	amd64)	arch="x86_64" ;;
+	i?86)	arch="i386" ;;
+	*)
+		die_hard "unsupported architectures" ;;
+esac
 
 cachedir=/var/cache/pepperflashplugin-nonfree
 
-wgetquiet=' -q '
-wgetfast='-t 3 -T 15 '
-wgetalways=' -nd -P . '
-wgetprogress=' -v --progress=dot:default '
-
-if [ "$ACTION" = "--install" -o 

Bug#833741: patch/nmu ?

[ydirson]

tags 833741 + patch
thanks

Is there any reason not to apply that patch ?

Bug#831825: clarification request

[ydirson]

severity 831825 important
tags 831825 + unreproducible moreinfo
reassign 831825 gcompris-qt
thanks


Let's lower the severity as it seems not to impact all users.

Trying to reproduce, I'm puzzled by the description, as gcompris does not
have a bottom-left menu, although gompris-qt has one.  I'm thus assuming
it is a gcompris-qt bug and reassigning.

Best regards,
Yann

Bug#830985: tulip: error while loading shared libraries: libbfd-2.26-system.so

[ydirson]

- Mail original -
> De: "Yuri D'Elia" 
> À: "Debian Bug Tracking System" 
> Envoyé: Mercredi 13 Juillet 2016 16:49:40
> Objet: Bug#830985: tulip: error while loading shared libraries: 
> libbfd-2.26-system.so
> 
> Package: tulip
> Version: 4.8.0dfsg-2+b3
> Severity: important
> 
> Seems like tulip depends on libbfd-2.26-system.so, but only
> libbfd-2.26-system.so.1 is available on my system.

You mean "libbfd-2.26.1-system.so", right ?

Looks like newer versions of binutils have broken the promise made by the
package's shlibs file ?


> % tulip
> tulip: error while loading shared libraries: libbfd-2.26-system.so:
> cannot open shared object file: No such file or directory
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (900, 'unstable'), (800, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages tulip depends on:
> ii  binutils  2.26.1-1
> ii  fonts-dejavu-core 2.35-1
> ii  fonts-font-awesome4.6.3~dfsg-1
> ii  libc6 2.23-1
> ii  libfreetype6  2.6.3-3+b1
> ii  libftgl2  2.1.3~rc5-4+nmu1+b1
> ii  libgcc1   1:6.1.1-9
> ii  libgl1-mesa-glx [libgl1]  11.2.2-1
> ii  libglew1.13   1.13.0-2
> ii  libgzstream-tulip-4.8-0   4.8.0dfsg-2+b3
> ii  libjpeg62-turbo   1:1.5.0-1
> ii  libogdf-tulip-4.8-0   4.8.0dfsg-2+b3
> ii  libpng16-16   1.6.23-1
> ii  libpython2.7  2.7.12-1
> ii  libqt5core5a  5.6.1+dfsg-3
> ii  libqt5gui55.6.1+dfsg-3
> ii  libqt5network55.6.1+dfsg-3
> ii  libqt5opengl5 5.6.1+dfsg-3
> ii  libqt5webkit5 5.6.1+dfsg-4
> ii  libqt5widgets55.6.1+dfsg-3
> ii  libqt5xml55.6.1+dfsg-3
> ii  libqt5xmlpatterns55.6.1-2
> ii  libquazip-tulip-4.8-1 4.8.0dfsg-2+b3
> ii  libqxt-tulip-4.8-04.8.0dfsg-2+b3
> ii  libstdc++66.1.1-9
> ii  libtess2-tulip-4.84.8.0dfsg-2+b3
> ii  libtulip-core-4.8 4.8.0dfsg-2+b3
> ii  libtulip-gui-4.8  4.8.0dfsg-2+b3
> ii  libtulip-ogdf-4.8 4.8.0dfsg-2+b3
> ii  libtulip-ogl-4.8  4.8.0dfsg-2+b3
> ii  libtulip-python-4.8   4.8.0dfsg-2+b3
> ii  libyajl-tulip-4.8-2   4.8.0dfsg-2+b3
> ii  zlib1g1:1.2.8.dfsg-2+b1
> 
> tulip recommends no packages.
> 
> tulip suggests no packages.
> 

Bug#830985: tulip: error while loading shared libraries: libbfd-2.26-system.so

[ydirson]

Well, I have never really felt libbfd.so-linking rejection from the project 
before,
as tulip has undergone numerous binNMU's to keep pace with libbfd.

Furthermore, the fact that the .so link is installed whenever bfd.h is installed
rather calls for linking against the shared lib.  If we want to provide them for
convenience to use cases which can't really do without, then I feel they ought 
to be
split in a separate deb, right ?

- Mail original -
> De: "Helmut Grohne" 
> À: "Yuri D'Elia" , 830...@bugs.debian.org
> Cc: "Matthias Klose" 
> Envoyé: Vendredi 15 Juillet 2016 00:11:31
> Objet: Bug#830985: tulip: error while loading shared libraries: 
> libbfd-2.26-system.so
> 
> Control: severity -1 grave
> 
> On Wed, Jul 13, 2016 at 04:49:40PM +0200, Yuri D'Elia wrote:
> > Seems like tulip depends on libbfd-2.26-system.so, but only
> > libbfd-2.26-system.so.1 is available on my system.
> 
> Linking libbfd dynamically is explicitly disallowed (see package
> description of binutils-dev). Please do not close this bug without
> removing the dynamic linking entirely. If you link libbfd statically,
> please ensure to add an appropriate Built-Using header.
> 
> Helmut
> 

Bug#826334: dget: removes existing dir by default without asking

[ydirson]

Package: devscripts
Version: 2.16.4
Severity: grave

dget unpacks the downloaded source by default, even if the target directory was
pre-existing.  Moreover, it does not just unpack it above the pre-existing dir,
but removes it first, together with all the other files it may contain !

Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade

[ydirson]

Would it be related to gcc taking advantage of the drop of i565 support ?

https://lists.debian.org/debian-devel-announce/2016/05/msg1.html

Bug#817255: cleancss: depends on material in /usr/share/doc

[ydirson]

Package: cleancss
Version: 1.0.12-1
Severity: serious

Removing /usr/share/doc should be allowed, as per policy 12.3.

but:

var packageConfig = 
fs.readFileSync('/usr/share/doc/node-clean-css/package.json');

Bug#816451: icedtea-netx: requires jre8 but still alternatively depends on jre7

[ydirson]

Package: icedtea-netx
Version: 1.6.2-2
Severity: serious

On upgrade, jre8 is not pulled, as existing jre7 fulfills the "openjdk-8-jre | 
openjdk-7-jre" dependency

Bug#788525: git-remote-https segfault involving libgnutls

[ydirson]

Package: libgnutls-deb0-28
Version: 3.3.15-5
Severity: grave
Justification: breaks other package

In my setup, a simple git ls-remote https://github.com/irmen/Pyro4.git; (or 
any https repo
I had) would silently die, with only strace revealing git-remote-https 
segfaulting.

gdb shows:

Reading symbols from /usr/lib/git-core/git-remote-https...(no debugging symbols 
found)...done.
[New LWP 26284]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1.
Core was generated by `git-remote-https origin 
https://github.com/irmen/Pyro4.git'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb73e2788 in nettle_yarrow256_update () from 
/usr/lib/i386-linux-gnu/libnettle.so.4
(gdb) bt
#0  0xb73e2788 in nettle_yarrow256_update () from 
/usr/lib/i386-linux-gnu/libnettle.so.4
#1  0xb7356641 in do_device_source (init=optimized out, event=0xbfadc770, 
ctx=0xb73becc0 rnd_ctx) at rnd.c:147
#2  0xb7356804 in wrap_nettle_rnd_init (ctx=0xb73beedc gnutls_rnd_ctx) at 
rnd.c:241
#3  0xb72bf3e6 in _gnutls_rnd_init () at random.c:49
#4  0xb72b2d6d in gnutls_global_init () at gnutls_global.c:272
#5  0xb7293534 in lib_init () at gnutls_global.c:434
#6  0xb77d086e in call_init (l=optimized out, argc=argc@entry=3, 
argv=argv@entry=0xbfadc8e4, env=env@entry=0xbfadc8f4) at dl-init.c:78
#7  0xb77d0964 in call_init (env=0xbfadc8f4, argv=0xbfadc8e4, argc=3, 
l=optimized out) at dl-init.c:36
#8  _dl_init (main_map=0xb77e2930, argc=3, argv=0xbfadc8e4, env=0xbfadc8f4) at 
dl-init.c:126
#9  0xb77c2d3f in _dl_start_user () from /lib/ld-linux.so.2
(gdb) info threads
  Id   Target Id Frame
* 1Thread 0xb6e2c700 (LWP 26284) 0xb73e2788 in nettle_yarrow256_update () 
from /usr/lib/i386-linux-gnu/libnettle.so.4
(gdb) 

... and when I downgrade to 3.3.8-6+deb8u1 from stable, the segfault does away.
Anything to do with that nettle transition that should only affect unstable ?
My testing install doesn't seem to have any stuff from unstable related to 
that...


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

Bug#742873: Patch for #742873

[ydirson]

tags 742873 + patch
thanks

Too bad it's too late for jessie...

From 18bbc237763955c150da72daf9be2b9702fefb0a Mon Sep 17 00:00:00 2001
From: Yann Dirson ydir...@free.fr
Date: Sat, 15 Nov 2014 16:45:50 +
Subject: [PATCH] Fix CVE-2013-1953

---
 debian/changelog   |  8 
 debian/patches/CVE-2013-1953.patch | 11 +++
 debian/patches/series  |  1 +
 3 files changed, 20 insertions(+)
 create mode 100644 debian/patches/CVE-2013-1953.patch

diff --git a/debian/changelog b/debian/changelog
index a12c511..42fdfc8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+autotrace (0.31.1-16+nmu1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix buffer overflow (Closes: #742873, CVE-2013-1953), patch from
+https://bugzilla.redhat.com/show_bug.cgi?id=951257.
+
+ -- Yann Dirson dir...@debian.org  Sat, 15 Nov 2014 16:45:25 +0100
+
 autotrace (0.31.1-16) unstable; urgency=low
 
   * Bumped Standards-Version to 3.9.2
diff --git a/debian/patches/CVE-2013-1953.patch 
b/debian/patches/CVE-2013-1953.patch
new file mode 100644
index 000..bcf12f6
--- /dev/null
+++ b/debian/patches/CVE-2013-1953.patch
@@ -0,0 +1,11 @@
+--- autotrace-0.31.1/input-bmp.c.orig  2002-10-10 22:44:08.0 +0200
 autotrace-0.31.1/input-bmp.c.orig  2013-06-28 10:24:58.336056959 +0200
+@@ -166,7 +166,7 @@ input_bmp_reader (at_string filename,
+ /* 36 */
+   Maps = 4;
+ }
+-  else if (Bitmap_File_Head.biSize = 64) /* Probably OS/2 2.x */
++  else if (Bitmap_File_Head.biSize = 40  Bitmap_File_Head.biSize = 64) /* 
Probably OS/2 2.x */
+ {
+   if (!ReadOK (fd, buffer, Bitmap_File_Head.biSize - 4))
+   {
diff --git a/debian/patches/series b/debian/patches/series
index cb1473f..f559677 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -10,3 +10,4 @@ output-pdf.c.patch
 output-pstoedit.c.patch
 output-pstoedit.h.patch
 README.patch
+CVE-2013-1953.patch
-- 
2.1.3


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