Am Wed, Mar 03, 2021 at 08:33:57PM +0100 schrieb Matthias Klose:
> >> gnumed-client depends on python3-pip. Why?
> >>
> >> The only use is in external-tools/check-prerequisites.py trying to
> >> download the
> >> pysvg module last updated in 2012, and not ported to Python3 ...
> >
> > The helper
Am Wed, Mar 03, 2021 at 07:49:29PM +0100 schrieb Matthias Klose:
> gnumed-client depends on python3-pip. Why?
>
> The only use is in external-tools/check-prerequisites.py trying to download
> the
> pysvg module last updated in 2012, and not ported to Python3 ...
The helper script external-tools/
Package: gnumed-client
Version: 1.7.8+dfsg-1
Followup-For: Bug #936630
Upstream has released 1.8.0 which supports python3 (and needs wxpython4).
Please make python3-psycopg2 a 2.7 versioned dependency as
python3-psycopg2 2.8 seems to have some problems.
Karsten
-- System Information:
Debian Rel
On Wed, Feb 05, 2020 at 11:17:39AM -0500, Scott Talbert wrote:
> BTW, the gnumed website seems to be having some problems.
I'm working on it.
https://www.gnumed.de/
Suitable for the watch file could be
https://www.gnumed.de/downloads/gnumed-versions.txt
or
https://www
It's done, there's even a release 1.8.rc3.
I need to convince myself to release 1.8.0 proper :-)
Karsten
> Gesendet: Donnerstag, 30. Januar 2020 um 17:25 Uhr
> Von: "Scott Talbert"
> An: "Moritz Mühlenhoff"
> Cc: "Karsten Hilbert" , &qu
Package: gnumed-client
Version: 1.7.7+dfsg-1
Followup-For: Bug #936630
Upstream (me) has py3 support available but it needs to be
polished and released.
Karsten
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable-debug'), (500,
'stable
On Thu, Feb 02, 2017 at 10:52:24PM +0900, Norbert Preining wrote:
>> W: APT had planned for dpkg to do more than it reported back (20 vs 24).
>> Affected packages: tex-common:i386
>
> That is something of dpkg,
I know, just wanted to point it out.
> not related to anything in TeX L
Package: orthanc-postgresql
Followup-For: Bug #818757
Dear Maintainer,
I can report that resolving
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811141
also resolved this bug (#818757) for me !
Thanks,
Karsten
-- System Information:
Debian Release: stretch/sid
APT prefers testing
On Wed, Jun 29, 2016 at 08:07:17AM +0200, Sebastien Jodogne wrote:
> What I would need would be a full backtrace of the C++ code. This requires a
> fresh build in debug mode, with static linking, of both Orthanc 1.1.0 and
> PostgreSQL plugin 2.0. Static linking allows to become independent of a
>
On Mon, Jun 27, 2016 at 11:03:36AM +0200, Sébastien Jodogne wrote:
> > - I would not have guessed that adding --upgrade might have made
> > a difference to a failure that tells me "stack smashing detected"
> > at the console :-)
>
> Just to be sure: Is your issue an immediate crash with "stac
On Sun, Mar 27, 2016 at 01:13:03PM +0200, Karsten Hilbert wrote:
> Is there anything else I can provide to get this bug looked at ?
Even if I risk to be a pain in the behind - since this
package is of such importance to responsible Medical Care
I allow myself to re-inquire about the state
Hi Sébastien,
welcome back.
> I am back from vacations. I will look at the upgrade problem as soon as
> possible.
I don't think it is an upgrade problem.
> As a quick hack to unblock you,
Fortunately, this is on a testing machine. No production data
at risk - that instance still runs on sqlit
Is there anything else I can provide to get this bug looked at ?
Thanks,
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
On Sun, Mar 20, 2016 at 06:55:50PM +0100, Andreas Tille wrote:
> > > Have you added the "--upgrade" option so that Orthanc would automatically
> > > upgrade the database schema?
>
> I wonder whether this should be done in a postinst script.
Only if the database upgrade does not make a differenc
On Sun, Mar 20, 2016 at 05:55:10PM +0100, Sébastien Jodogne wrote:
> > 4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg
> > 2.0)
>
> Have you added the "--upgrade" option so that Orthanc would automatically
> upgrade the database schema?
I now did run Orthanc with --
On Sun, Mar 20, 2016 at 05:55:10PM +0100, Sébastien Jodogne wrote:
> > 4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg
> > 2.0)
>
> Have you added the "--upgrade" option so that Orthanc would automatically
> upgrade the database schema?
I have not because
- it's no
Package: orthanc-postgresql
Version: 2.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Orthanc does not start when the backend is set to PostgreSQL.
1) I can successfully
su - orthanc
psql -d orthanc_db
2) Orthanc will start if set to using the sqlite
Package: clinica
Version: 0.3.0-1
Followup-For: Bug #787877
For what it is worth: GNUmed (gnumed-client) offers code to import a
Clinica database.
Karsten
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stab
On Mon, Oct 27, 2014 at 11:48:37AM +0100, Christoph Berg wrote:
> > If so that'd solve the apparent problem. It won't prevent
> > the following scenario though:
> >
> > - Jessie is released with PG 9.4.betaX
> > - PG releases 9.4.betaX+1 which requires a dump/restore
> > cycle due to a catalog
On Mon, Oct 27, 2014 at 11:48:37AM +0100, Christoph Berg wrote:
> > If so that'd solve the apparent problem. It won't prevent
> > the following scenario though:
> >
> > - Jessie is released with PG 9.4.betaX
> > - PG releases 9.4.betaX+1 which requires a dump/restore
> > cycle due to a catalog
Package: postgresql
Version: 9.4+163
Severity: serious
Tags: upstream
Justification: 5.a)
Hi,
since it is now less than 10 days from Nov 5th and upstream hasn't
released PostgreSQL 9.4 just yet
http://www.postgresql.org/docs/9.4/static/release-9-4.html
I wonder what the rationale is for
On Thu, Oct 11, 2012 at 10:05:48PM +0200, Andreas Tille wrote:
> > Hi Andreas,
> >
> > is there anything I can do to help make this happen ?
> >
> > 687702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687702
>
> I'm *way* *more* worried about #685351
I thought #685351 got fixed ?!?
>
On Thu, Sep 20, 2012 at 06:54:50AM +0200, Andreas Tille wrote:
> In case no other team member will upload or somebody will
> NMU I'll upload not before 5.10.2012 because I'm on vac.
Is there any risk of 1.1.19 not getting considered for a
freeze exception simply because of that (IOW, the 5th of O
On Thu, Sep 20, 2012 at 06:54:50AM +0200, Andreas Tille wrote:
> just to keep a record: I commited the JS sources in question to gnumed
> packaging SVN.
Thanks so much for taking care of this "issue".
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E4
On Tue, Dec 28, 2010 at 11:51:46PM +0900, Charles Plessy wrote:
> > Just to clear this up: this bug applies to GNUmed 0.7.10-1
> > from Squeeze and NOT to 0.8.5 from sid.
>
> I hope the above control commands will correctly summarise the situation in
> the
> BTS.
Looks right to me.
@Release tea
On Tue, Nov 30, 2010 at 05:25:00PM +0100, Andreas (Debian) wrote:
> thanks to the support of upstream there is a new release which fixes the
> issue. However, the issue does not even really exist in *effective*
> upstream code - it is just contained in a *comment* which is simlpy
> activated in a
Fixed upstream in 0.7.10 and 0.8.5.
Please consider 0.7.10 for migration to squeeze.
Changelog:
0.7.10
FIX: exception on trying to create hospital stay w/o episode [thanks
devm]
FIX: properly set PYTHONPATH [thanks JB and Debian Squeeze (#605159)]
Download:
ht
Package: kdebase-workspace-bin
Severity: grave
Justification: renders package unusable
After an
apt-get update
apt-get dist-upgrade
today KDE will not start anymore because this package is not installable
due to the libxklavier15 dependancy.
Due to this the apt-get dist-upgrade
On Mon, Nov 23, 2009 at 04:01:18PM +0100, Andreas Tille wrote:
> I realised that there are all in all three packages in Debian which
> are acceccing a CT-API and providing a file ctapi.h:
>
> $ apt-file search ctapi.h
> libctapimkt0-dev: /usr/include/ctapi.h
> libopenct1-dev: /usr/include/openct/
Package: alsa-utils
Version: 1.0.20-2
Severity: serious
Justification: stops machine boot
This happens during boot and triggers a stop asking for the root
password for maintenance or Ctlr-D to continue rebooting anyway:
merkur:~# /etc/init.d/alsa-utils restart
Shutting down ALSA...done.
Setting u
On Sat, Oct 18, 2008 at 04:57:04PM +, Debian Bug Tracking System wrote:
> #497382: libchipcard-tools: kvkcard segfaults when reading eGK
This seems fixed now.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
To UNSUBSCRIBE, email to
Package: linux-image-2.6.26-1-686
Followup-For: Bug #494374
This bug is fixed on my ASUS L2000D, too. Great.
Karsten
-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-8) ([EMAIL PROTECTED]) (gcc version
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Oct
On Sat, Sep 06, 2008 at 08:38:52PM +0200, Micha Lenk wrote:
> > I installed libchipcard-dev but even that didn't give much
> > better results than this:
>
> Indeed, the backtrace isn't very helpful. Can you please try again to
> get a backtrace with these packages from [1] installed? Those packag
On Tue, Sep 02, 2008 at 12:43:31AM +0200, Micha Lenk wrote:
> can you please provide a backtrace of kvkcard?
Sure :-)
I installed libchipcard-dev but even that didn't give much
better results than this:
merkur:~# gdb --args kvkcard read -v -v
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software
Package: python-imaging-sane
Version: 1.1.5-10
Severity: serious
Justification: renders package unusable in certain circumstances
It segfaults (?) due to not finding numarray -- which does not seem to be
listed as a dependancy. It seems it previously used numpy instead.
[EMAIL PROTECTED]:~$ pytho
Package: libextractor-python
Version: 0.5.1-2
Severity: grave
Justification: renders package unusable
Script started on Mi 21 Dez 2005 22:06:12 CET
[EMAIL PROTECTED]:~/tmp$ python ./extract.py
Traceback (most recent call last):
File "./extract.py", line 27, in ?
xtract = extractor.Extractor(
36 matches
Mail list logo
