Bug#1076223: tcputils,libbpf-tools: install program with same name (tcpconnect)

Hi, Thanks Andreas for following up on this bug report which has sat in my inbox far too long. I think that it could be of interest to mention what Fedora has chosen: * tcputils installs the programs without prefix or suffix in /usr/bin. * libbpf-tools installs the programs with a bpf- prefix i

Bug#1062810: Update

On Sun, Feb 4, 2024, at 13:04, Pushkar Kulkarni wrote: > Do you plan on doing a new upstream release? Yes, that's what I plan to do tomorrow in addition to uploading a new Debian package. -- Joel

Bug#1062810: ccache fails to run it's autopkg tests

I hope to find time to fix this tomorrow. -- Joel

Bug#1059468: defsubst with &rest leads to "Optimizer error: too much on the stack"

Package: emacs-gtk Version: 1:29.1+1-5 As noted in Debian bug report #1058739, Emacs fails to byte-compile code like this: (defsubst bar (a &rest b) nil) (defun foo () (bar 1 2 3 4)) Result: $ emacs -Q --batch -f batch-byte-compile repro.el In toplevel form: repro.el:2

Bug#1058739: lyskom-elisp-client: fails to install with Emacs 29: lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack

This looks like an Emacs bug. Reduced reproducer: $ cat repro.el (defsubst bar (a &rest b) nil) (defun foo () (bar 1 2 3 4)) $ emacs -Q --batch -f batch-byte-compile repro.el In toplevel form: repro.el:2:2: Error: Optimizer error: too much on the stack I'll see if I

Bug#1033349: unblock: ccache/4.8+really4.7.5-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: affects -1 + src:ccache Please unblock package ccache [ Reason ] Ccache versions 4.7 - 4.7.4 by default enable a feature called the inode cache which shares information between pro

Bug#1033191: ccache: Solution to address the deadlocking issue with ccache 4.7 on Debian Bookworm.

On Sun, Mar 19, 2023, at 11:42, David Heidelberg wrote: > The authors of ccache have mentioned that this version includes a rewrite > that addresses serious issues, such as deadlocks [2]. Just to clarify: the rewritten locking solution in 4.8 was not done to fix any known bug - it was done for p

Bug#1033267: Upload ccache bookworm fix via testing-proposed-updates?

On Tue, Mar 21, 2023, at 20:55, Paul Gevers wrote: > I'm wondering where you are reading that. The text says: If there are > unrelated changes in unstable, we ask you to revert these changes > instead of making an upload to testing-proposed-updates. > > What's unclear in that phrase? I think tha

Bug#1033267: Upload ccache bookworm fix via testing-proposed-updates?

+35,7 @@ Copyright (C) 2002-2007 Andrew Tridgell -Copyright (C) 2009-2022 Joel Rosdahl and other contributors +Copyright (C) 2009-2023 Joel Rosdahl and other contributors diff -Nru ccache-4.7.4/cmake/CcacheVersion.cmake ccache-4.7.5/cmake/CcacheVersion.cmake --- ccache-4.7.4/

Bug#1022704: ccache: broken in cross-architecture chroot

Thanks! Now I understand the problem and will work on a fix. The issue is sharing the inode cache file between architectures. A workaround is to either use separate temporary directories for the architectures (or different cache directories when the temporary directory defaults to the cache direc

Bug#1022704: ccache: broken in cross-architecture chroot

On Mon, Oct 24, 2022, at 21:31, Raphaël Halimi wrote: > I don't know how to use strace. Could you please direct me ? If you find the process that hangs (likely a ccache process in this case) with PID P, use strace -p P to attach to it and see which system call it is waiting for. > The file

Bug#1022704: ccache: broken in cross-architecture chroot

On Mon, Oct 24, 2022, at 15:26, Raphaël Halimi wrote: > Install pbuilder on an amd64 host and prepare an i386 chroot. Then, try to > build a package in it (I was rebuilding timidity). It should hang during the > configure phase. I've never used pbuilder before, but I've tried creating an i386 chro

Bug#1022704: ccache: broken in cross-architecture chroot

On Mon, Oct 24, 2022, at 13:40, Raphaël Halimi wrote: > I also tested it, it's broken too. Thanks. Can you give me more some detailed hints on how I can reproduce the issue? Regards, Joel

Bug#1022704: ccache: broken in cross-architecture chroot

Hi Raphaël, Could you test if ccache 4.7.1-1 improves the situation? Regards, Joel

Bug#987328: unblock: lyskom-elisp-client/0.48+git.20200923.ec349ff4-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package lyskom-elisp-client 0.48+git.20200923.ec349ff4-3 fixes two important/release critical bugs: #985871 and #987260. Changes: 1. Only support Emacs flavor "emacs", i.e.

Bug#984674: ccache: clang links missing in /usr/lib/ccache

On Sat, 6 Mar 2021 at 22:51, Joachim Wuttke wrote: > Package ccache installs a number of symbolic links to /usr/lib/ccache, among > them clang-11 and clang++-11, but not clang and clang++. May I kindly suggest > you add these two? The problem is that /usr/bin/clang is created (via the alternative

Bug#972256: ccache: please add symlink for emcc (emscripten)

Hi Jonas, I've had a quick look at emcc now. I don't feel comfortable adding a ccache symlink for it without some kind of evaluation of how emcc's options interact when using the "-c" mode -- a symlink in /usr/lib/ccache would signal that ccache officially supports emcc, which it doesn't (yet). >

Bug#965271: ccache: Doesn't cache anymore C++ files

Hi Christian, Thanks for the bug report. ccache works for me for C++ files (I use it all the time) so I need more information than "it doesn't work" to have any chance of doing anything. For example what you do to draw the conclusion that ccache doesn't cache C++ files anymore. Here is some gene

Bug#938192:

I think that it's time to remove python-sqlite from Debian: it's a module for the obsolete SQLite 2 API and there's (understandably) no upstream activity.

Bug#938099:

I think that it's time to remove python-pysqlite2 from Debian: Python has had support for SQLite 3 since version 2.5 and there is (understandably) no upstream activity for the Python wrapper.

Bug#947607: O: egenix-mx-base -- eGenix mx Base Distribution for Python

Package: wnpp Severity: normal thanks

Bug#944399: ccache: Building aosp-10 bionic leads to ld.lld: error: undefined symbol: strcpy_a9

Thanks for the bug report. On Sat, 9 Nov 2019 at 08:06, Stefan Rücker wrote: > I can provide you files or infos from the failing build if you need those, the > problem is reproducible. Yes, I will need assistance to investigate this. From https://github.com/sonyxperiadev/bug_tracker/issues/492 I

Bug#942686: fix the installation of 3.8 extensions

reopen 942686 thanks I applied the patch too quickly (see #943506) – it doesn't work with the Python 3.7 filenames in current Debian unstable. Python 3.8 apparently produces apsw.cpython-38-x86_64-linux-gnu.so apsw.cpython-38d-x86_64-linux-gnu.so but Python 3.7 produces apsw.cpytho

Bug#928929: ccache: please add support for gcc/g++ 9

On Mon, 13 May 2019 at 11:21, Cyril Brulebois wrote: > Even if gcc-9 only appears in experimental for now (where gcc-defaults > defaults to it), it'd be nice to have ccache have support for it. With support, do you mean a symlink in /usr/lib/ccache? ccache should pick up gcc-9 automatically by lo

Bug#835812: jessie-pu: package ccache/3.1.12-2

esn't work for me. :-( -- Joel On 27 June 2017 at 20:39, Cyril Brulebois wrote: > Joel Rosdahl (2017-06-27): > > Isn't it in jessie already? See <https://packages.debian.org/ > jessie/ccache>. > > Jessie has: > ccache | 3.1.12-1 | oldstable | so

Bug#835812: jessie-pu: package ccache/3.1.12-2

016-09-10): > > On Sun, 2016-08-28 at 16:59 +0200, Joel Rosdahl wrote: > > > To fix #829088 ("ccache don't stop immediately on SIGINT and > SIGTERM"), I > > > propose to upgrade ccache from 3.1.12-1 to 3.1.12-2 in > stable-proposed-updates. > > >

Bug#855500: unblock: ccache/3.3.4-1

statistics counters to the + man page. + + -- Joel Rosdahl Fri, 17 Feb 2017 23:02:40 +0100 + ccache (3.3.3-1) unstable; urgency=medium * New upstream release 3.3.3 diff -Nru ccache-3.3.3/AUTHORS.txt ccache-3.3.4/AUTHORS.txt --- ccache-3.3.3/AUTHORS.txt2016-10-26 23:31:19.0 +0200

Bug#853834: Ccache storing and restoring file paths that may no longer be correct

On 18 February 2017 at 00:54, Ben Hutchings wrote: > I've also found that disabling direct mode (CCACHE_NODIRECT=1) is a workaround, > at least in this case. Yes. When the direct mode is disabled, dependency files are created fresh by the preprocessor instead of taken from the cache. > The probl

Bug#853834: Ccache storing and restoring file paths that may no longer be correct

Hi, Upstream release 3.3.4 contains a fix for this problem. I uploaded a Debian package of it to unstable just now and will look into requesting a freeze unblock. Regards, -- Joel

Bug#835460: ccache don't stop immediately on SIGINT and SIGTERM

Thanks for the bug report. I have submitted a request to fix this in stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835812 -- Joel On 26 August 2016 at 00:22, Zavadovsky Yan wrote: > Package: ccache > Version: 3.1.10-1 > Severity: important > Tags: patch > > ccache 3.1.10 have regres

Bug#835812: jessie-pu: package ccache/3.1.12-2

a regression in ccache 3.1.10 leading to ccache not dying +properly when interrupted by a signal. + + -- Joel Rosdahl Sun, 28 Aug 2016 15:45:26 +0200 + ccache (3.1.12-1) stable; urgency=medium * New upstream release 3.1.12 containing important bug fixes (and only diff -Nru ccache-3.1.12

Bug#831426: jessie-pu: package ccache/3.1.12-1

On 29 July 2016 at 14:18, Julien Cristau wrote: > It doesn't look like you're doing any error checking from lstat; is there no > way it'll fail here? Hm, right, not checking the error code is a mistake I made when backporting the fix. However, I don't think it will cause any problem in practice.

Bug#829088: Jessie

For reference: I have requested to include ccache 3.1.12 in Jessie in #831426 . -- Joel

Bug#831426: jessie-pu: package ccache/3.1.12-1

+version 3.1.12 Table of Contents JavaScript must be enabled in your browser to display the table of contents. @@ -776,7 +776,7 @@ Copyright (C) 2002-2007 Andrew Tridgell - Copyright (C) 2009-2011 Joel Rosdahl + Copyright (C) 2009-2016 Joel Rosdahl @@ -1210,8 +1210,9 @@

Bug#829088: ccache may silently miscompile symlinked source files

On 15 July 2016 at 07:55, Jaap Keuter wrote: > Don't the release notes of the next version address this? > https://ccache.samba.org/releasenotes.html#_ccache_3_2_6 Yes, it's a fix for this bug. I also made a 3.1.12 release especially for Debian stable. I just haven't had time to make a Debian pac

Bug#815585: ccache: Incomplete link list for mingw-w64

On 22 February 2016 at 19:17, Andreas Metzler wrote: > installing mingw-w64 adds the following links to /usr/lib/ccache: > i686-w64-mingw32-gcc-5.3-posix > i686-w64-mingw32-gcc-5.3-win32 > x86_64-w64-mingw32-gcc-5.3-posix > x86_64-w64-mingw32-gcc-5.3-win32 > > However with "./configure --host i686

Bug#784681: ccache: mednafen fails to build with ccache

I would say that this is a GCC bug - g++ can't compile its own preprocessed source code. The problem can be reproduced without ccache by building src/hash/sha1.cpp with -save-temps: % cd src % /usr/bin/g++ -save-temps -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I../include -I../inclu

Bug#766604: ccache: C++ compiler does not support C++11 standard

Hi Jérémy, Have you tried reproducing the problem with the mentioned steps? Regards, -- Joel On 27 October 2014 at 21:39, Joel Rosdahl wrote: > Hi, > > > Is it a bug or an unsupported feature ? > > It's a bug in something, but it's hard to say where with the give

Bug#778388: ccache: scanner confused by comment signs in strings

of the relevant code. -- Joel On 16 February 2015 at 21:41, Oswald Buddenhagen wrote: > On Mon, Feb 16, 2015 at 09:26:02PM +0100, Joel Rosdahl wrote: > > Yes, a reduced testcase would be much appreciated. I don't have access to > > https://codereview.qt-project.org/105039 a

Bug#778388: ccache: scanner confused by comment signs in strings

Yes, a reduced testcase would be much appreciated. I don't have access to https://codereview.qt-project.org/105039 and I wouldn't know what to do anyway. :-) (BTW: You did clear the cache before you compiled the changed source code, right? Otherwise a cache hit is expected from the previous experi

Bug#778388: ccache: scanner confused by comment signs in strings

Hi Oswald, I can't reproduce this problem. Here is what I did: % ccache -C Cleared cache % sh debian-bug-778388.sh cache miss % sh debian-bug-778388.sh cache hit (direct) % sed -i s/16/17/ debian-bug-778388.sh % sh debian-bug-778388.sh cache miss % sh debian-bug-778388.sh cache hit (direct) Not

Bug#766604: ccache: C++ compiler does not support C++11 standard

Hi, > Is it a bug or an unsupported feature ? It's a bug in something, but it's hard to say where with the given information. It could be in ccache, the compiler or mapnik's configure logic. I can't reproduce the problem by simply running mapnik's configure with ccache. Here's what I did: 1. Do

Bug#736301: python-sqlite-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

look at the log, that's because it didn't even try to install python-sqlite-dbg since it apparently doesn't work to run piuparts in a chroot. -- Joel On 5 February 2014 17:50, Sebastian Ramacher wrote: > Hi Joesl > > On 2014-02-01 11:45:44, Joel Rosdahl wrote: > >

Bug#736301: python-sqlite-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

Hi Andreas, Thanks for the bug report! As far as I can tell, neither python-sqlite-dbg nor python-sqlite in neither wheezy nor jessie contain symlinks for (or in) /usr/share/doc and don't create any symlinks in preinstall/postinstall scripts. Therefore I don't understand what needs to be done, if

Bug#666525: trying to disable ccache locally, failing

Hi, > ccache seems to ignore the request [...] Is there some ccache subtlety I'm missing? ccache doesn't ignore the request, it just happens to make sure that the ccache directory exists before reacting to CCACHE_DISABLE (or CCACHE_READONLY)... Looks like it has been that way since day one (well,

Bug#718830: python-apsw: Required dependencies missing due to incorrect python:Depends expansion

Thanks! I'm fine either way - you can upload it if you like. -- Joel On 6 August 2013 00:34, Scott Kitterman wrote: > Package: python-apsw > Version: 3.7.17-r1-1 > Severity: serious > Tags: patch > Justification: Policy 3.5 > > Both python-apsw and python3-apsw are missing depends on the corre

Bug#706992: python-apsw: Please provide Python 3 package

Thanks, I'll apply the patch and upload soon. -- Joel On 15 June 2013 23:13, Nikolaus Rath wrote: > On 06/15/2013 01:52 PM, Nikolaus Rath wrote: > > I've attached a debdiff for building Python 3 packages. It also fixes > > bug #710049. Please let me know if that's acceptable, or if you would >

Bug#624589: clang support

RESOLVED/FIXED in the upstream ccache case means "a fix has been committed to some branch", and Target Milestone says which version the fix will be in. When the version has been releated, the bug is set to CLOSED/FIXED. -- Joel On 9 May 2013 22:52, Ben Longbons wrote: > That upstream bug is no

Bug#672570: ccache: Does not handle nonwriteable/not-a-directory HOME gracefully, breaks autogen

Hi, On 12 May 2012 09:22, Andreas Metzler wrote: > it is not possible to build GNU autogen with ccache installed and in > PATH. Afaict this caused by autogen setting HOME=/dev/null. > [...] > ccache should be able to handle this more gracefully and not try to write to > nonwriteable/not-a-directo

Bug#465324: Random preprocessor errors

On 10 May 2012 12:54, wrote: > I still can reproduce it using ccache 3.1.7-1 and gcc 4.4.7-1 Thanks! The root cause is a bug in preprocessor. Since ccache by default runs the preprocessor and then compiles its output, the error shows up when using ccache. Here's a reduced test case: % cat bug4

Bug#671929: ccache: trigger not multi-arch safe, prevents proper gcc upgrade

Hi, I don't see anything in the triggered ccache postinst script that could cause this. Can you reproduce the problem? Could it be that something other than ccache's trigger that causes this? See for instance bug#665727. -- Joel On 8 May 2012 11:10, Yann Dirson wrote: > Package: ccache > Vers

Bug#639223: ccache: Please install symlinks in /usr/bin as alternatives

On 2011-12-18 17:27, Reuben Thomas wrote: > Here's another suggestion: how about having a dpkg configuration item? > This way, the user gets to choose at install time whether to enable > it, and has an easy way to switch it on/off via dpkg-reconfigure. That sounds OK to me. -- Joel -- To UNSU

Bug#652582: override: python-pysqlite1.1:python/extra

Package: ftp.debian.org Severity: normal "python-pysqlite1.1_1.1.8a-5_amd64.deb: package says priority is extra, override says optional." As per bug #641322, python-pysqlite1.1 should have priority extra because it conflicts with the optional package python-sqlite. -- Joel -- To UNSUBSCRIBE,

Bug#639223: ccache: Please install symlinks in /usr/bin as alternatives

On 2011-12-18 11:44, Reuben Thomas wrote: > I agree with all of the above, but why not s/enable/install/? I think that it's not uncommon to want to use ccache only explicitly, but that's mostly speculation. Another example of where it could be bad is that if the ccache package gets installed on a

Bug#639223: ccache: Please install symlinks in /usr/bin as alternatives

On 2011-08-25 07:41, Reuben Thomas wrote: > For the majority of users of ccache, it would be nice if installing it > simply installed alternatives symlinks for gcc, so that no user > configuration is necessary. While I can understand the wish for this, my opinion is that enabling ccache by default

Bug#632779: cc and c++ symlinks aren't updated when installing gcc or g++ before ccache

On 2011-07-06 00:23, José Manuel Santamaría Lema wrote: > [...] > So ... if the gcc maintainers accept the gcc-defaults patch, would you > accept the ccache one? If yes, I would open a new bug report against > src:gcc-defaults with the patch and mark this one as blocked. A reply just > saying "go a

Bug#630352: ccache: inoperative with multiarchized compilers

On 2011-06-14 13:06, Adam Borowski wrote: > For an actual break, you'd need a more complex setup with extra layers like > colorgcc or distcc, and in that case it might be argued to be an user > configuration error (except that there's no proper configuration in such > cases other than creating the

Bug#630352: ccache: inoperative with multiarchized compilers

On 2011-06-13 12:02, Adam Borowski wrote: > I'm afraid that ccache will break compilation of anything that specifies the > full name of the compiler ("x86_64-linux-gnu-gcc" rather than "gcc"). It > does still work with non-multiarch ones. Thanks for the bug report! I'm afraid I don't understand i

Bug#624589: clang support

On 2011-04-29 23:33, Peter Eisentraut wrote: > Please add integration for the clang compiler suite. You'd just need to add > > /usr/bin/clang > /usr/bin/clang++ > /usr/bin/llvm-clang > > into update-ccache-symlinks and add some dpkg triggers. I don't think that this should be done u

Bug#465324: Random preprocessor errors

Has anyone been able to reproduce this problem lately? I've never seen it. -- Joel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#349315: Please list gcc-snapshot

I think we should close this bug. Any objections? -- Joel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#349315: Too intrusive

I don't think this is a good idea -- it's too intrusive. Another much simpler way of accomplishing it is this: export CCACHE_PATH=/usr/lib/gcc-snapshot/bin This of course requires some action by the user, but I think that's a good thing in this case. -- Joel -- To UNSUBSCRIBE, email to d

Bug#580944: Please update to 3.0 from upstream

Hi, I've just released version 3.0 of ccache. See http://ccache.samba.org/news-3.0.html for a list of changes. Since I'm also a Debian developer, I'm glad to help with the Debian package if wanted. -- Joel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject o

Bug#565868: python-apsw: too strong dependency on libjs-jquery

On Mon, 18 Jan 2010 23:53:59 -0600 Raphael Geissert wrote: > While it is reasonable for python-apsw to depend on libjs-jquery, > making it a strong dependency is overly exaggerating it. > Only the rare users who happen to use the search functionality of the > already few users who happen to read

Bug#564791: --git-export doesn't work when specified version's upstream version != HEAD's upstream version

Package: git-buildpackage Version: 0.4.63 Tags: patch git-buildpackage fails when --git-export specifies a version whose upstream version is not the same as HEAD's upstream version. Transcript: # head -1 debian/changelog python-pysqlite2 (2.5.5-3) unstable; urgency=low # git-buildpac

Bug#547826: Not fixed, FTBFS when building with Python2.6 present

On Wed, 21 Oct 2009 18:50:34 +0200 Roderich Schupp wrote: > debian/movefiles.sh still references names with hard-coded "site-packages", > e.g. Crap. OK, uploaded 3.1.2-5 now. Thanks! -- Regards, Joel Rosdahl Key BB845E97 (9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84

Bug#547826: Not fixed, FTBFS when building with Python2.6 present

kg-buildpackage: error: fakeroot debian/rules binary gave error exit status > 2 Thanks! Could you please try version 3.1.2-4? -- Joel Rosdahl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#508683: python-pysqlite2: .txt Documentation has include statements rather than real code snippet.

Junichi Uekawa writes: > Joel Rosdahl wrote: >> >> I agree that the text version isn't very useful in its current >> form. There doesn't seem to be a way of automatically expanding the >> code-block directives other than what's already done in the HT

Bug#508683: python-pysqlite2: .txt Documentation has include statements rather than real code snippet.

version in the package. On the other hand: The documentation is in an another (HTML only) format in python-pysqlite2 2.5.0-1 and later. -- Regards, Joel Rosdahl Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@l

Bug#500425: python-pysqlite2: depends on libjs-jquery

depending on jquery > and let people who do not need jquery/documentation install the > binary package ? > [...] Yes, that seems reasonable. Will fix shortly. -- Regards, Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5

Bug#469644: python-pysqlite2: unicode bug while processing non-unicode text

ite and that > latter would break compatibility with existing code. Thus, this > should be discussed with the authors. I agree with you. I have created a ticket about this: http://oss.itsystementwicklung.de/trac/pysqlite/ticket/229 -- Regards, Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E9

Bug#456500: python-apsw

", (toUnicode(path), > dum > ps(ls))) > File "apsw.c", line 3518, in resetcursor > ConstraintError: ConstraintError: not an error Thanks for your bug report. Do you have any runnable example of code that I can use to reproduce this error? Regards, Joel -- Joel Rosdah

Bug#454424: other arch

Thomas Guebels <[EMAIL PROTECTED]> writes: > Can you please upload the fix for other architectures than amd64 as > well ? Thanks. That's the job of the auto-builders. They should upload binary packages for the other architectures soon. Regards, Joel -- Joel Rosdahl <[E

Bug#436003: preinst fails when /proc/mounts doesn't exist

ub-process /usr/bin/dpkg returned an error code (1) -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#430557: mx.DateTime.Date constructor regression (Debuan bug #430557)

active high-level object-o ii python2.5 2.5.1-1An interactive high-level object-o python-egenix-mxdatetime recommends no packages. -- no debconf information --- End Message --- -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97

Bug#429512: RFP: python2.5-pysqlite2 -- python interface to SQLite 3

Michael Mende <[EMAIL PROTECTED]> writes: > Shouldn't python2.5-pysqlite2 provided by python-pysqlite2? - See > http://wiki.debian.org/DebianPython/NewPolicy Yes. python-pysqlite2 2.3.4-1, which I uploaded yesterday, will provide Python 2.5 modules too. -- Regards, Joe

Bug#427338: Type affinity broken

e returned as Unicode. I've filed a bug in APSW's bug tracker. See <http://initd.org/tracker/pysqlite/ticket/199>. -- Regards, Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [EMAIL PR

Bug#406363: python-egenix-mxdatetime: import using python2.5 fails

on/debian_defaults.) When support has been added, I (or someone else) can rebuild the python-egenix-mxdatetime package to get 2.5 support. -- Regards, Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [

Bug#373829: Please add BLOB support

Hello Florian, Joel Rosdahl <[EMAIL PROTECTED]> writes: > Florian Weimer <[EMAIL PROTECTED]> writes: > >> Package: python2.3-apsw >> Version: 3.3.5r1-1 >> Severity: wishlist >> >> Currently, it is not possible to store arbitrary 8-bit data in t

Bug#373829: Please add BLOB support

uot;:memory:") c = db.cursor() c.execute("CREATE TABLE test (a BLOB)") c.execute("INSERT INTO test VALUES (?)", (buffer("\377"),)) c.execute("INSERT INTO test VALUES (?)", (buffer("\000A"),)) print list(c.execute("SELECT * FROM test&quo

Bug#372656: python-irclib 0.4.6 available

Package: python-irclib Version: 0.4.4-1 Severity: wishlist python-irclib 0.4.6 is available. Please consider packaging it. Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to

Bug#365222: python-apsw: please package new upstream release (3.3.5)

package it in the beginning of next week. Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361507: python2.4-pysqlite1.1: hangs on execute()

x27;) > > the program hangs in execute() with high system load. this does > happen with libsqlite3-0_3.3.5-0.1 but not with > libsqlite3-0_3.2.8-1. Thanks for the report. I just uploaded python-pysqlite1.1_1.1.7-1. Please let me know whether the new version fixes the problem. Reg

Bug#361097: python-pysqlite2 and new sqlite3 packages

ion 2.0.7] Fixed an API misuse that made pysqlite 2.0.x > unusable with SQLite versions 3.3.3 or later. So please package and > upload it due to #361097 . Okay. I will upload python-pysqlite2_2.2.0-1 shortly. Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; f

Bug#341092: python2.3-sqlite: Python2.3 package uses decorators

Hi Kevin, Joel Rosdahl <[EMAIL PROTECTED]> writes: > [...] > Thanks for the bug report! However, I think you are mistaken. The > only thing python2.3-sqlite does in its postinstall script is to run > /usr/lib/python2.3/compileall.py on each directory found in > /usr/lib/py

Bug#341092: python2.3-sqlite: Python2.3 package uses decorators

-packages. It also does not use or install any Python egg or formencode module. The only conclusion I can draw is that the egg comes from some other package or module that you have installed by other means. Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; f

Bug#327128: ITP: python-pysqlite1.1 -- python interface to SQLite 3

Package: wnpp Severity: wishlist Owner: Joel Rosdahl <[EMAIL PROTECTED]> By request (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304067), I intend to package pysqlite 1.1 so that SQLite 3 can be used while using the old pysqlite API. The package will conflict with python-sqlite (wh

Bug#304067: Closing

an appropriate name for the PySQLite 1.1 package? Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#323619: typo in python-egenix-stack dependency

Hi! > Package: python-egenix-stack > Version: 2.0.6-1 > Severity: serious > > missing comma. Hm, I fail to see where the comma is missing. Please elaborate. > maybe you can drop the 2.1 and 2.2 packages? Yes, I guess it's about time to do that. Regards,

Bug#309371: ITP: python-pysqlite2 -- python interface to SQLite

ch, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97

Bug#304067: python-sqlite: Please package pysqlite 1.1 (SQLite 3.x)

this? (Are there other solutions?) You might also want consider using python-apsw, which now is part of unstable. Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [EMAIL

Bug#296652: ITP: python-apsw -- another Python SQLite wrapper

cumentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. -- Joel Rosdahl <

Bug#290734: please support python2.4

.4 support. I uploaded new packages January 16th, but they seem to be stuck in the "new queue". Regards, Joel -- Joel Rosdahl <[EMAIL PROTECTED]> Key BB845E97; fingerprint 9F4B D780 6EF4 5700 778D 8B22 0064 F9FF BB84 5E97 -- To UNSUBSCRIBE, email to [EMAI