Package: synergy
Version: 1.4.16-1+deb8u1
Severity: minor
Dear Maintainer,
in the packages description text (e.g. found here:
https://packages.debian.org/sid/synergy), the link to synergy source code on
Github is wrong. It points to https://github.com/symless/synergy but this page
does not exist
On 11/22/2016 01:52 PM, Bas Couwenberg wrote:
> Control: tags -1 unreproducible moreinfo
>
> Hi Tobias,
>
> On 2016-11-22 13:36, Tobias Megies wrote:
>> for me, `cs2cs` from package `proj-bin` fails to lookup the EPSG file
>> `/usr/share/proj/epsg` from package `
initly not necessary
to manually set this path in older package versions as I was using "cs2cs" in
the same way on earlier Debian distributions (certainly in Debian squeeze, not
100% sure about Debian wheezy).
best regards,
Tobias Megies
-- System Information:
Debian Release: 8.5
Package: vino
Version: 3.14.0-2+b1
Severity: important
Dear Maintainer,
when the option "disable-background" is set to True in dconf key
>org>gnome>desktop>remote-access, the server crashes on a connection attempt,
seemingly choking up on a key "draw-background" (see attached traceback) that I
co
Source: matplotlib
Severity: grave
Justification: renders package unusable
Dear Maintainer,
in `debian/rules` for python-matplotlib-data, Bitstream Vera ttf fonts are
deliberately removed from the package (same is done for some fonts of package
`fonts-lyx`) but the package hosting those fonts (`t
odule named 'IPython'
This looks pretty odd, does it not?
regards,
Tobias Megies
On 09/18/2015 12:00 PM, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated rep
orth a change. Thus I am closing the issue.
I can really not follow your reasoning to ignore this bug.. at all. Why
deviate from the Python Policy?
regards,
Tobias Megies
On 09/04/2015 05:06 PM, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug r
ndency checking and makes the package vulnerable to
incomplete local installations of python.
=== quote end
best regards,
Tobias Megies
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
A
eter using
/usr/bin/env python or /usr/bin/env pythonX.Y. This is not advisable as it
bypasses Debian's dependency checking and makes the package vulnerable to
incomplete local installations of python.
=== quote end
best regards,
Tobias Megies
-- System Information:
Debian Release: 8.0
APT
A working fix was proposed 17 months ago. Is there a reason to not use
the proposed fix? Or should the package be considered orphaned?
best regards,
Tobias Megies
On Sun, 17 Mar 2013 17:00:24 +0700 George Fatkin
wrote:
> Package: t1-cyrillic
> Version: 4.16
>
> I changed comma (',
he
> C API:
>
> "
> If you already have it on your system, just set the environment variable
> GEOS_DIR to point to the location of libgeos_c and geos_c.h (if libgeos_c
> is in /usr/local/lib and geos_c.h is in /usr/local/include, set GEOS_DIR
> to /usr/local).
> &q
Package: libgeos-3.3.3
Version: 3.3.3-1.1
Severity: important
Dear Maintainer,
I was trying to compile matplotlib basemap
(http://sourceforge.net/projects/matplotlib/files/matplotlib-
toolkits/basemap-1.0.7/) which depends on libgeos.
The compilation fails because matplotlib basemap tries to link
Package: qgis
Version: 1.7.4+1.7.5~20120320-1.1+b1
Severity: serious
Justification: Policy 1.4.2
Dear Maintainer,
when running /usr/bin/qgis it uses the first python interpreter found in $PATH.
If a local user-space Python environment is coming first in $PATH this is bound
to fail, because module
Package: python-matplotlib
Version: 1.1.1~rc2-1
Severity: serious
Justification: Policy 5.6.10; 7.2
Dear Maintainer,
several packages that are used inside the matplotlib code seem to be missing
from "Depends/Recommends/Suggests" in "debian/control". One example is the test
suite. It can not be ru
This bug has been fixed upstream, see
https://github.com/matplotlib/matplotlib/pull/2307.
The fix will be part of the upcoming bugfix/minor release 1.3.1 of
matplotlib. I assume unstable will be updated to 1.3.1 after it is
released? After/if it is updated this bug can be closed.
best,
Tobias
-
I think this is the same problem as in issue #2320 at the matplotlib
github page:
https://github.com/matplotlib/matplotlib/issues/2320
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: eyed3
Version: 0.6.18-1
Severity: important
Dear Maintainer,
the executable that gets installed in /usr/bin/eyeD3 has a dynamic Python
interpreter lookup in the shebang (#!/usr/bin/env python). This breaks the
package ("ImportError: No module named eyeD3" when calling /usr/bin/eyeD3)
whe
17 matches
Mail list logo
