Bug#675063: Update on libextactor on sid

2012-06-20 Thread Mike Dupont
Hi there, I was not about to get his patch working, there were typos mike On Wed, Jun 20, 2012 at 6:50 PM, Bertrand Marc beberk...@gmail.com wrote: Hello, I am not sure to understand what is wrong with Harun's patch. It is already included upstream. Could you tell what is missing in his patch

Bug#675063: Update on libextactor on sid

2012-06-20 Thread Mike Dupont
There were calls to strstr where strchr should be used. This line - sym_name = strstr (prefix, _); + sym_name = strstr (prefix, libextractor_)+12; is needed for the x86_64 cause the _in the arch name. mike On Wed, Jun 20, 2012 at 7:44 PM, Mike Dupont jamesmikedup...@googlemail.com wrote

Bug#687930: shotwell: Segfault, on invalid piwigo response

2012-09-17 Thread Mike Dupont
Package: shotwell Version: 0.12.3-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? testing the plugin with a invalid piwigo server api. * What exactly did you do (or not do) that was effective

Bug#688226: f-spot: Build from apt-source but resulting binary is unusable (in chroot)

2012-09-20 Thread Mike Dupont
Package: f-spot Version: 0.8.2-5 Severity: normal Dear Maintainer, I use apt-src install, then dpkg-build package but the resulting build cannot run, in chroot evn. [Info 14:16:48.686] Initializing Mono.Addins Object reference not set to an instance of an object System.NullReferenceException:

Bug#688226: also occurs with main package

2012-09-20 Thread Mike Dupont
also the package installed with apt-get install also produces this error. Info 14:35:50.730] Initializing Mono.Addins Object reference not set to an instance of an object System.NullReferenceException: Object reference not set to an instance of an object at

Bug#675063: Update on libextactor on sid

2012-06-05 Thread Mike Dupont
Hi, I have attempted to patch the extract, the patch provided almost worked, my changes seem to work. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675063 The problem is the _ in the x86_64, so I made a hack around that. Also added in debug info, also i turned off dh_strip, because the program

Bug#718403: Same Problem

2013-08-01 Thread Mike Dupont
Hi there, I am having this problem as wel, am willing to help out. What is the status of python right now? mike -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM,

Bug#718403: Works with the standard build

2013-08-01 Thread Mike Dupont
this works with the standard build http://donate.libreoffice.org/home/dl/deb-x86_64/4.1.0/en-US/LibreOffice_4.1.0_Linux_x86-64_deb.tar.gz -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion

Bug#718403: Same Problem

2013-08-01 Thread Mike Dupont
:50AM -0500, Mike Dupont wrote: Hi there, I am having this problem as wel, am willing to help out. Then do that? :) I am still imvestigating, upstream doesn't know about a 4.0.4 - 4.1.0 regression in that area, though. What is the status of python right now? python*uno ttbomk works, same

Bug#718403: Same Problem

2013-08-01 Thread Mike Dupont
Ok, in the next days/weeks I will go through this, gotta get to work now. On Thu, Aug 1, 2013 at 7:57 AM, Rene Engelhard r...@debian.org wrote: Hi, On Thu, Aug 01, 2013 at 07:46:22AM -0500, Mike Dupont wrote: the debian packaging breaks it. I am downloading all the sources and I fear

Bug#718403: Same Problem

2013-08-02 Thread Mike Dupont
this works for me thanks so much! PYTHONPATH=/usr/lib/libreoffice/program libreoffice --writer On Fri, Aug 2, 2013 at 1:21 AM, Sébastien Kalt sk...@throka.org wrote: Hi Rene, 2013/8/1 Rene Engelhard r...@debian.org: [...] After setting PYTHONPATH=$PYTHONPATH:/usr/lib/libreoffice/program

Bug#719941: libreoffice-script-provider-python: python 3 porting issues

2013-08-16 Thread Mike Dupont
Package: libreoffice-script-provider-python Version: 1:4.1.1~rc1-1 Severity: minor Dear Maintainer, here are some patches for python 3 porting. --- /usr/lib/libreoffice/program/pythonscript.py~2013-08-16 18:51:06.865451812 -0500 +++ /usr/lib/libreoffice/program/pythonscript.py2013-08-06

Bug#719941: libreoffice-script-provider-python: python 3 porting issues

2013-08-17 Thread Mike Dupont
build, the only thing I did was turn on the logging, which I need and should be supported. On Sat, Aug 17, 2013 at 3:44 AM, Rene Engelhard r...@debian.org wrote: On Fri, Aug 16, 2013 at 07:21:50PM -0500, Mike Dupont wrote: --- /usr/lib/libreoffice/program/pythonscript.py~2013-08-16 18:51

Bug#719941: libreoffice-script-provider-python: python 3 porting issues

2013-08-17 Thread Mike Dupont
wrote: Hi, On Sat, Aug 17, 2013 at 06:12:58AM -0500, Mike Dupont wrote: encfile(msg).decode() does not work with py2.7, encfile returns bytes not a string which needs to be decoded http://docs.python.org/3.0/whatsnew/3.0.html as far as I know the latest version of libreoffice does not support

Bug#719941: libreoffice-script-provider-python: python 3 porting issues

2013-08-21 Thread Mike Dupont
On Tue, Aug 20, 2013 at 10:27 AM, Rene Engelhard r...@debian.org wrote: --- /usr/lib/libreoffice/program/pythonscript.py~2013-08-16 18:51:06.865451812 -0500 +++ /usr/lib/libreoffice/program/pythonscript.py2013-08-06 12:25:04.0 -0500

Bug#719941: libreoffice-script-provider-python: python 3 porting issues

2013-08-21 Thread Mike Dupont
resending because the mail system was confused : On Tue, Aug 20, 2013 at 10:27 AM, Rene Engelhard r...@debian.org wrote: -ret = open( systemPath , a ) +ret = file( systemPath , a ) So why is this needed? see

Bug#380731: I would like to support this effort to package phc and php-embedded in debian

2012-03-25 Thread Mike Dupont
For the packaging of phc in debian, which I would like to have packaged, we need some way to allow the embedding of php. I will look into packaging of them both together and uploading them to debian mentors. Really php embedded could be it own package like discussed. it should be possible to host

Bug#687930: shotwell: Segfault, on invalid piwigo response

2012-09-29 Thread Mike Dupont
sure, i thought i submitted that already. give me a day thanks mike On Sat, Sep 29, 2012 at 2:10 PM, Luca Falavigna dktrkr...@debian.orgwrote: Could you please try to obtain a backtrace of the crash? -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org

Bug#687930: shotwell: Segfault, on invalid piwigo response

2012-09-30 Thread Mike Dupont
in library_exec () #55 0x081e9666 in _vala_main () #56 0x080b3a58 in main () (gdb) it is pretty simple, the results are not checked. it seems to be a common problem. On Sat, Sep 29, 2012 at 4:06 PM, Mike Dupont jamesmikedup...@googlemail.com wrote: sure, i thought i submitted that already. give

Bug#687930: shotwell: Segfault, on invalid piwigo response

2012-09-30 Thread Mike Dupont
sure, how to test? i upgraded everything before i tested today. here are my apt sources : deb http://ftp.us.debian.org/debian unstable main deb-src http://ftp.us.debian.org/debian unstable main deb http://ftp.us.debian.org/debian experimental main deb-src http://ftp.us.debian.org/debian

Bug#687930: shotwell: Segfault, on invalid piwigo response

2012-09-30 Thread Mike Dupont
i had them added, but needed the -t apt-get -t experimental install shotwell same error : shotwell 0.13.0-1 Entity: line 1: parser error : Start tag expected, '' not found crash ^ Entity: line 1: parser error : Start tag expected, '' not found crash ^ Program received signal SIGSEGV,

Bug#711334: g++-4.7: internal compiler error on dump translation unit compiling boost spirit.qi

2013-06-06 Thread Mike Dupont
Package: g++-4.7 Version: 4.7.2-5 Severity: minor Dear Maintainer, See the bug in gcc here, they have not been able to reproduce http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57524 Can you please test if you have this problem and if it is related to the debian build? -- System Information: Debian

Bug#737027: please help

2014-01-29 Thread Mike Dupont
Package: fglrx-driver Version: 1:13.12-3 Severity: grave Justification: renders package unusable Please Help. my solution was to downgrade. now running with xserver-xorg-video-intel 2:2.19.0-6 -- Package-specific info: Full fglrx package list: ii fglrx-atieventsd

Bug#732975: website update

2013-12-23 Thread Mike Dupont
Package: gnome-orca Severity: wishlist Dear Maintainer, on the webpage http://packages.debian.org/sid/gnome-orca the link External Resources: Homepage [live.gnome.org] goes to http://live.gnome.org/Orca but it should be https://wiki.gnome.org/Projects/Orca There are a bunch of broken links

Bug#732976: RuntimeError: Data access methods are unsupported. Use normal Python attributes instead

2013-12-23 Thread Mike Dupont
Package: accerciser Version: 3.4.1-1 Severity: important Dear Maintainer, just using the tool crashes. RuntimeError: Data access methods are unsupported. Use normal Python attributes instead See my patch to comment out get/set data

Bug#740536: umbrello does not display or open

2014-03-02 Thread Mike Dupont
Subject: umbrello does not display or open Package: umbrello Version: 4:4.11.5-1 Justification: renders package unusable Severity: grave This does not work at all : umbrello(10901)/kdeui (kdelibs): Attempt to use QAction edit_undo with KXMLGUIFactory! umbrello(10901)/kdeui (kdelibs): Attempt to

Bug#741020: mongodb-server: Does not install

2014-03-07 Thread Mike Dupont
Subject: mongodb-server: Does not install Package: mongodb-server Version: 1:2.4.9-1 Justification: renders package unusable Severity: grave -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')

Bug#741020: mongodb-server: Does not install

2014-03-07 Thread Mike Dupont
On Fri, Mar 7, 2014 at 8:06 AM, László Böszörményi (GCS) g...@debian.org wrote: Please be more specific. Just purged - installed it on amd64. It works for me. Ok, I see the error now : Fri Mar 7 07:43:07.964 [initandlisten] ERROR: Insufficient free space for journal files Fri Mar 7

Bug#739860: ITP

2014-07-04 Thread Mike Dupont
Howdy, I started on packaging today https://github.com/h4ck3rm1k3/toxcore and then I found this ITP, is there any status on the packaging or the existing work? I have some more changes pending, lets merge efforts. mike -- James Michael DuPont Member of Free Libre Open Source Software Kosova

Bug#741335: bzr: 'latin-1' codec can't encode characters on branch command

2014-03-11 Thread Mike Dupont
Subject: bzr: 'latin-1' codec can't encode characters on branch command Package: bzr Version: 2.6.0+bzr6591-1 Severity: important bzr branch lp:a11ytesting bzr: ERROR: exceptions.UnicodeEncodeError: 'latin-1' codec can't encode characters in position 90-95: ordinal not in range(256) Traceback

Bug#767574: [PKG-Openstack-devel] Bug#767574: keystone: Does not install : dpkg: error processing package keystone (--configure):

2014-11-01 Thread Mike Dupont
Hi there, I will rerun it, did not get an error message. Am using mysql i thought. mike On Sat, Nov 1, 2014 at 6:31 AM, Thomas Goirand tho...@goirand.fr wrote: On Sat Nov 1 2014 09:42:35 AM MSK, James Michael DuPont jamesmikedup...@googlemail.com wrote: Package: keystone Version: 2014.2-1

Bug#767574: [PKG-Openstack-devel] Bug#767574: keystone: Does not install : dpkg: error processing package keystone (--configure):

2014-11-01 Thread Mike Dupont
-installation script returned error exit status 10 Errors were encountered while processing: keystone E: Sub-process /usr/bin/dpkg returned an error code (1) On Sat, Nov 1, 2014 at 6:54 AM, Mike Dupont jamesmikedup...@googlemail.com wrote: Hi there, I will rerun it, did not get an error message. Am

Bug#767574: [PKG-Openstack-devel] Bug#767574: keystone: Does not install : dpkg: error processing package keystone (--configure):

2014-11-01 Thread Mike Dupont
://192.168.2.2:35357/v2.0/OS-KSADM/services Unable to establish connection to http://192.168.2.2:35357/v2.0/OS-KSADM/services/ done! On Sat, Nov 1, 2014 at 7:44 AM, Mike Dupont jamesmikedup...@googlemail.com wrote: udo apt-get install -t experimental keystone The following NEW packages

Bug#767574: [PKG-Openstack-devel] Bug#767574: Bug#767574: Bug#767574: keystone: Does not install : dpkg: error processing package keystone (--configure):

2014-11-02 Thread Mike Dupont
I am using systemd. /var/run/keystone, already exists now. even after purging. does it make sense to install keystone standalone? here is my config dbc_install='true' dbc_upgrade='true' dbc_remove='' dbc_dbtype='mysql' dbc_dbuser='keystone' dbc_dbpass='2JnTb4mOmQQ3' dbc_dbserver='' dbc_dbport=''

Bug#785762: gcc-4.9: Segfault on llvm build

2015-05-19 Thread Mike Dupont
Package: gcc-4.9 Version: 4.9.2-16 Severity: important building with g...@github.com:llvm-mirror/llvm.git commit d70b3aca8e69e52f5683c2c0f351722482f5929f Author: Tobias Grosser tob...@grosser.es Date: Tue May 19 06:25:19 2015 + llvm[3]: Building Debug+Asserts Archive Library libLLVMipo.a

Bug#791449: fpm ini

2015-07-04 Thread Mike Dupont
I found the problem the fpm ini was broken. columns_width=150;150;150;150;150;150;150;150; columns_order=0;0;-1271480230;32577;0;0;-1248539512;32577; I dont know how it got that way. I hope someone will fix this bug, or I will if you wont because this really caused me a lot of fear of losing my

Bug#791449: Crashing when there is an existing ~.fpm2 dir

2015-07-04 Thread Mike Dupont
Subject: fpm2: Crashing when there is an existing ~.fpm2 dir Package: fpm2 Version: 0.79-3 Justification: causes non-serious data loss Severity: grave When loading an existing password file the fpm2 crashes. I cannot load my password file and this is critical for me. It occurs on this line where

Bug#791449: valgrind results

2015-07-04 Thread Mike Dupont
==21084== Command: ./src/fpm2 ==21084== ==21084== Invalid read of size 8 ==21084==at 0x12AB8A: fpm_clist_init (fpm_clist.c:151) ==21084==by 0x1148C2: fpm_init (fpm.c:384) ==21084==by 0x1115F4: main (main.c:71) ==21084== Address 0xfffda1e992f0 is not stack'd, malloc'd or (recently)

Bug#791449: Acknowledgement (Crashing when there is an existing ~.fpm2 dir)

2015-07-04 Thread Mike Dupont
This problem does occur also on debian sid, it seems to be a problem with my password file in conjunction with the other thiings. I need a way to export my passwords out of this system, I dont have a copy of some of them except in there. please help! -- To UNSUBSCRIBE, email to

Bug#802920: nodejs: Does not build out of the box test-net-connect-immediate-finish.js fails

2015-10-25 Thread Mike Dupont
Yes, I was unsure what severity to use. Feel free to change it how you think is best. On Sun, Oct 25, 2015 at 4:02 AM, Jérémy Lal <kapo...@melix.org> wrote: > > > 2015-10-25 7:45 GMT+01:00 Mike Dupont <jamesmikedup...@googlemail.com>: >> >> Subject: node

Bug#802920: nodejs: Does not build out of the box test-net-connect-immediate-finish.js fails

2015-10-25 Thread Mike Dupont
Subject: nodejs: Does not build out of the box Package: nodejs Version: 4.2.1~dfsg-1 Justification: does not build Severity: major This test is failing not ok 499 test-net-connect-immediate-finish.js # TIMEOUT -- System Information: Debian Release: stretch/sid APT prefers unstable APT

Bug#804494: patch : disable broken printf length

2015-11-11 Thread Mike Dupont
Attached a dirty patch to disable the broken printf max string length code. I dont expect it to be merged but it might be a starting point for someone experiencing the problem that I have. Take a look at _doprnt from libiberty for an implementation. I am wondering why we need these lengths in the

Bug#804494: [Ltrace-devel] patch : disable broken printf length

2015-11-11 Thread Mike Dupont
Ok petr I will make a clean patch in the next days. mike On Wed, Nov 11, 2015 at 9:32 AM, Petr Machata <pmach...@gmail.com> wrote: > 2015-11-11 14:34 GMT+01:00 Mike Dupont <jamesmikedup...@googlemail.com>: >> Attached a dirty patch to disable the broken printf max

Bug#804494: Additional information for ltrace formats string bug

2015-11-11 Thread Mike Dupont
On Tue, Nov 10, 2015 at 7:36 AM, Mike Dupont <jamesmikedup...@googlemail.com> wrote: > format_array I have looked deeper into the code. There seems to be no parsing or storage of the width field (the minimal width) it is treated as the maximum width. Only the max width (precision)

Bug#804494: ltrace: fprintf output truncated on strings with width specifiers

2015-11-08 Thread Mike Dupont
Package: ltrace Version: 0.7.3-5 Severity: important Given this test program #include #include int main() {FILE * fp; fp = fopen ("test.txt", "w+"); fprintf(fp, "%-4s: %-7s ", "body", "undefined"); fclose(fp); return(0); } Get this output : 21591 1447023907.549403 [0xae41a7]

Bug#804494: Additional information for ltrace formats string bug

2015-11-10 Thread Mike Dupont
Regarding bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804494 First of all, it seems that the version in git ( git://git.debian.org/git/collab-maint/ltrace.git) is way different than the release version. ltrace-0.7.3 So in git the strings are not printed at all, the git version

Bug#791449: fpm ini

2015-07-10 Thread Mike Dupont
Thank you for the advice, I have done this already. Ich war eine Zeitlang echt am verzweifeln! mfg, mike On 7/10/15, Dr. Tobias Quathamer to...@debian.org wrote: Am 05.07.2015 um 03:08 schrieb Mike Dupont: I found the problem the fpm ini was broken. [...] the solution was to just copy

Bug#804494: patch : disable broken printf length

2015-11-13 Thread Mike Dupont
Let me know if this is acceptable. On Wed, Nov 11, 2015 at 8:34 AM, Mike Dupont <jamesmikedup...@googlemail.com> wrote: > Attached a dirty patch to disable the broken printf max string length > code. I dont expect it to be merged but it might be a starting point > for someo

Bug#807179: nasm: Crash on ndisasm /usr/lib/gcc/x86_64-linux-gnu/5/cc1plus

2015-12-06 Thread Mike Dupont
Subject: nasm: Crash on ndisasm /usr/lib/gcc/x86_64-linux-gnu/5/cc1plus Package: nasm Version: 2.11.06-1really2.11.05-1 Severity: normal ndisasm /usr/lib/gcc/x86_64-linux-gnu/5/cc1plus . 00015F01 BE0C2Dmov si,0x2d0c 00015F04 B5FF mov ch,0xff Segmentation fault

Bug#807179: area of memory

2015-12-06 Thread Mike Dupont
If it helps any : od -x -N 32 -j 0x00015F00 /usr/lib/gcc/x86_64-linux-gnu/5/cc1plus 0257400 bef6 2d0c ffb5 1a0f 9c61 fa1a 0447 57d6 0257420 4576 787e aa00 56ff cad9 ef41 83c4 f520 mike

Bug#807183: x86dis: *** stack smashing detected ***: x86dis terminated

2015-12-06 Thread Mike Dupont
Subject: x86dis: *** stack smashing detected ***: x86dis terminated Package: x86dis Version: 0.23-6 Severity: normal x86dis -s xml -e 0 -f /usr/lib/gcc/x86_64-linux-gnu/5/cc1plus this can also be reproduced with x86dis -s xml -a 0x00CF -f /usr/lib/gcc/x86_64-linux-gnu/5/cc1plus the raw

Bug#808573: network-manager: undefined symbol: g_udev_enumerator_new

2015-12-20 Thread Mike Dupont
Subject: network-manager: undefined symbol: g_udev_enumerator_new Package: network-manager Version: 1.0.8-2 Justification: renders package unusable Severity: grave Job for NetworkManager.service failed because the control process exited with error code. See "systemctl status

Bug#808573: [Pkg-utopia-maintainers] Bug#808573: network-manager: undefined symbol: g_udev_enumerator_new

2015-12-21 Thread Mike Dupont
libudev shared library On Mon, Dec 21, 2015 at 5:27 AM, Michael Biebl <bi...@debian.org> wrote: > Am 21.12.2015 um 06:08 schrieb Mike Dupont: >> /usr/sbin/NetworkManager --no-daemon >> /usr/sbin/NetworkManager: symbol lookup error: >> /usr/sbin/NetworkManager: undef

Bug#817855: impress: crash on delete comment

2016-03-10 Thread Mike Dupont
Subject: impress: crash on delete comment Package: libreoffice-impress Version: 1:5.1.1~rc1-1 File: impress Severity: important Add comment to impress. Add new comment and then delete it. Crash. -- James Michael DuPont Kansas Linux Fest http://kansaslinuxfest.us Free/Libre Open Source and

Bug#817855: impress: crash on delete comment

2016-03-11 Thread Mike Dupont
I debated reporting this, but I use jessie 8 now and this really messed me up yesterday. I think it is relevant to debian as a usable stable platform. On Fri, Mar 11, 2016 at 5:24 AM, Rene Engelhard <r...@debian.org> wrote: > Hi, > > On Thu, Mar 10, 2016 at 06:46:59PM -0500, Mi

Bug#817855: impress: crash on delete comment

2016-03-12 Thread Mike Dupont
thanks for checking, I will upgrade. On Sat, Mar 12, 2016 at 6:49 AM, Rene Engelhard <r...@debian.org> wrote: > tag 817855 + moreinfo > tag 817855 + unreproducible > thanks > > Hi, > > On Thu, Mar 10, 2016 at 06:46:59PM -0500, Mike Dupont wrote: > >Add co

Bug#817855: impress: crash on delete comment

2016-03-19 Thread Mike Dupont
I am preparing my talk and cannot upgrade right now, you can close this if you cannot reproduce it, I will report back later thanks On Thu, Mar 17, 2016 at 6:48 PM, Rene Engelhard <r...@debian.org> wrote: > On Sat, Mar 12, 2016 at 07:31:44AM -0500, Mike Dupont wrote: > >than

Bug#902835: python3.7: segfault on pip install

2018-07-01 Thread Mike Dupont
Package: python3.7 Version: 3.7.0-1 Severity: normal Dear Maintainer, * What led up to the situation? running pip install segfaults * What exactly did you do (or not do) that was effective (or ineffective)? Using this requirements.txt python3.7 -m pip install -r requirements.txt -e