Bug#666396: openexr: New upstream: 1.7.0
Probably the compile issue will be solved in the near future release. See openexr issue 67: https://github.com/openexr/openexr/issues/67 IRIE Shinsuke 13/07/12, Andreas Metzler wrote: On 2013-06-29 IRIE Shinsuke wrote: Hi, I experienced the same error in testBox.cpp with libilmbase 2.0.0. It seems that the error was caused by bad optimization, because the build succeeds when changing the optimization level as follows: [...] Anyway, please update openexr/ilmbase to v2.0.0. Blender will move to OpenEXR v2.0.0 in 2.68 release. Hello, I have just requested an adopter for OpenEXR and ILMbase. http://bugs.debian.org/716766 http://bugs.debian.org/716768 These seem to need somebody with better C++ knowledge than me. cu Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666396: openexr: New upstream: 1.7.0
Hi, I experienced the same error in testBox.cpp with libilmbase 2.0.0. It seems that the error was caused by bad optimization, because the build succeeds when changing the optimization level as follows: diff -ur debian/rules ilmbase-2.0.0/debian/rules --- debian/rules2012-12-08 19:46:56.0 +0900 +++ ilmbase-2.0.0/debian/rules 2013-06-29 21:14:26.698123494 +0900 @@ -10,8 +10,13 @@ NO_MAKE_CHECK_ARCHS := arm ifeq (,$(filter $(DEB_BUILD_ARCH),alpha)) +ifeq (,$(filter $(DEB_BUILD_ARCH),i386)) export DEB_CFLAGS_MAINT_APPEND=-Wall export DEB_CXXFLAGS_MAINT_APPEND=-Wall +else + export DEB_CFLAGS_MAINT_APPEND=-Wall -O1 + export DEB_CXXFLAGS_MAINT_APPEND=-Wall -O1 +endif else export DEB_CFLAGS_MAINT_APPEND=-Wall -mieee export DEB_CXXFLAGS_MAINT_APPEND=-Wall -mieee Anyway, please update openexr/ilmbase to v2.0.0. Blender will move to OpenEXR v2.0.0 in 2.68 release. Thanks -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692429: libpython3.3-dev: fatal error: pyconfig.h: No such file or directory
Thanks, I have reported this issue in Blender developers ML. -- IRIE Shinsuke 12/11/06, Matthias Klose wrote: > reassign 692429 blender > severity 692429 important > thanks > > Am 06.11.2012 07:10, schrieb IRIE Shinsuke: >> Package: libpython3.3-dev >> Version: 3.3.0-2 >> Severity: grave >> >> I attempted to build Blender trunk using python3.3-dev but got the >> following error: >> >> [ 58%] Building C object >> source/blender/python/intern/CMakeFiles/bf_python.dir/gpu.c.o >> In file included from >> /home/irie/Subversion/Blender/blender/source/blender/python/intern/gpu.c:40:0: >> /usr/include/python3.3m/Python.h:8:22: fatal error: pyconfig.h: No such file >> or directory >> compilation terminated. >> >> >> '#include "pyconfig.h"' in Python.h assumed that pyconfig.h is in >> /usr/include/python3.3m, but it's actually placed in >> /usr/include/x86_64-linux-gnu/python3.3m. >> >> Probably most of all programs using libpython3.3 cannot be built for >> this bug. > > no, only these which use home-grown configure tests. Please use > python3.3-config > --includes or pkgconfig. > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692429: libpython3.3-dev: fatal error: pyconfig.h: No such file or directory
Package: libpython3.3-dev Version: 3.3.0-2 Severity: grave I attempted to build Blender trunk using python3.3-dev but got the following error: [ 58%] Building C object source/blender/python/intern/CMakeFiles/bf_python.dir/gpu.c.o In file included from /home/irie/Subversion/Blender/blender/source/blender/python/intern/gpu.c:40:0: /usr/include/python3.3m/Python.h:8:22: fatal error: pyconfig.h: No such file or directory compilation terminated. '#include "pyconfig.h"' in Python.h assumed that pyconfig.h is in /usr/include/python3.3m, but it's actually placed in /usr/include/x86_64-linux-gnu/python3.3m. Probably most of all programs using libpython3.3 cannot be built for this bug. -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687060: dh_python3: TypeError when maximum version is specified
12/10/09, Piotr Ożarowski wrote: ">= 3.2, << 3.3" is equal to "3.2" so please use the later one before I will fix it Using the latter also causes the same error... -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687060: dh_python3: TypeError when maximum version is specified
Each element of vr[] in depends.py is a tuple of the major and minor
versions such as (3, 2), not an integer, so this error can be avoided
by modifying the line 158 as follows:
self.depend("python3 (<< %s)" % vrepr((vr[1][0], vr[1][1] + 1)))
However, I'm not sure if this code produces the intended results.
--
IRIE Shinsuke
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687060: dh_python3: TypeError when maximum version is specified
I forgot to mention that I'm using dh_python3 only for private modules, not for public modules. -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687060: dh_python3: TypeError when maximum version is specified
Package: python3-defaults
Version: 3.2.3-5
I attempted to build a deb package using dh_python3 but got an error:
Traceback (most recent call last):
File "/usr/bin/dh_python3", line 490, in
main()
File "/usr/bin/dh_python3", line 422, in main
dependencies.parse(stats, options)
File "/usr/share/python3/debpython/depends.py", line 158, in parse
self.depend("python3 (<< %s)" % vrepr(vr[1] + 1))
TypeError: can only concatenate tuple (not "int") to tuple
I specified the python3 version in debian/control as follows:
X-Python3-Version: >= 3.2, << 3.3
The same error happens when I use -V command line option like:
dh_python3 -V 3.2-3.3
--
IRIE Shinsuke
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683078: l10n UI unreadable at all (can't load international font)
Package: blender Version: 2.63a-1 When starting Blender, I get many annoying warnings as follows: Can't load font: default from memory!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! Warning: Can't found default font!! And indeed UI is not displayed with "Droid Sans Regular" font. Especially, if I attempt to use UI translated into Japanese, all Japanese characters appear as unreadable blank squares. I investigated 0009-look_for_droid_ttf_with_fontconfig.patch and found that BLI_file_to_mem() in fileops.c doesn't work. fread() in this function returns 0 or 1, not actual readsize, so the font file cannot be read to memory area properly. To fix this bug, readsize= fread(mem+size, chunk_size,1,file); has to be modified as follows: readsize= fread(mem+size, 1, chunk_size, file); -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683046: Thumbnailer is not registered automatically
The thumbnailer should work with the following .thumbnailer file: START === [Thumbnailer Entry] TryExec=/usr/lib/blender/scripts/blender-thumbnailer.py Exec=/usr/lib/blender/scripts/blender-thumbnailer.py %i %o MimeType=application/x-blender; E N D === -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683046: Thumbnailer is not registered automatically
Oops, sorry, the thumbnailer is installed in /usr/lib/blender/scripts/. -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683046: Thumbnailer is not registered automatically
Package: blender Version: 2.63a-1 blender-thumbnailer.py is installed in /usr/bin, but not working unless we manually register it by creating .thumbnailer file in ~/.local/share/thumbnailers. I think deb package should make system-wide setting for it, so please install /usr/share/thumbnailers/blender.thumnailer as follows: START === [Thumbnailer Entry] TryExec=blender-thumbnailer.py Exec=blender-thumbnailer.py %u %o MimeType=application/x-blender; E N D === -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683042: debian/copyright: No information of embedded external libraries
Package: blender Version: 2.63a-1 debian/copyright doesn't include the copyright information of the external libraries such as libmv, Eigen3, and Bullet Physics which are included in orig.tar.bz2 file and will be statically linked. Also, there are some codes partially imported from external projects. For example, functions for detecting a pen tablet device were copied from Wine 1.1.13 (See intern/ghost/intern/GHOST_WindowX11.cpp). -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682948: Incorrect versioning scheme disturbs upgrading
Hi, 12/07/27, Matteo F. Vescovi wrote: I'm not going to use SVN revisions other than the stable releases. So Debian Blender package is not going to face this issue at all. Since I'm actually the only active maintainer for this package, I don't see any issue in naming using upstream's version numbering. Hmm... I see, that is what I have worried about. What about another numbering scheme using "." between the minor version and the version character as follows? 2.63, 2.63.a, 2.63.b, ... This scheme is very similar to the upstream version numbering, and should never cause the upgrade issue even if a version suffix is necessary. -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682948: Incorrect versioning scheme disturbs upgrading
I forgot to say that actually there were official deb packages using "+cvs" suffix in the past (ex. 2.25b+cvs.2003.02.17-1). So, "+svn" suffix might be used for the future versions of the official packages. I mean the versioning scheme like 2.63.1 is generally necessary, not only for my PPA's packages. -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682948: Incorrect versioning scheme disturbs upgrading
Package: blender Version: 2.63a-1 Severity: important Please don't change the versioning scheme, and don't use upstream version string "a", "b", etc. Old blender package for 2.49b used the package version "2.49.2" to avoid the upgrade issue. Changelog of 2.49.2~dfsg-1 says: This is actually 2.49b, but using a "+dfsg" suffix breaks comparing 2.49+dfsg and 2.49b+dfsg. Use ".2" instead of "b" accordingly. And switch to using a "~dfsg" suffix. So, 2.63a should be translated into 2.63.1 for the same reason. In my PPA in Launchpad, I have maintained blender trunk package for Ubuntu and the package version uses "+svn" suffix like 2.63.1+svn49102-0irie1~precise1. Since Debian package system compares the versions as 2.63a+svn < 2.63+svn < 2.63.1+svn, if the official Debian/Ubuntu package uses the wrong versioning scheme such as 2.63a, I can no longer provide the trunk packages having a version suffix "+svn". -- IRIE Shinsuke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673504: [Pkg-phototools-devel] Bug#673504: Manpages need updating
Hi, 12/05/19, Matteo F. Vescovi wrote: As soon as I'll be able to prepare a new revision (or even better, a new upstream release since 1.0.4 is out now), I'll upload the library with new manpages. I checked them again for 1.0.4, then found some small changes/typos. Attached newer ones. -- IRIE Shinsuke oiio_1.0.4_manpages.tar.gz Description: GNU Zip compressed data
Bug#673504: Manpages need updating
Package: openimageio-tools Version: 1.0.3+dfsg0-1 Existing manpages were written by me for 0.10.5 and including some mistakes. Some command line options were added/deleted/changed after that, so please update them for 1.0.3. I attached new manpages. BTW, txt2man in Build-Depends is unnecessary unless using auto-generated manpages. -- IRIE Shinsuke oiio_1.0.3_manpages.tar.gz Description: GNU Zip compressed data
Bug#622708: dh_python3 generates incorrect prerm script which cannot remove .pyc files
Package: python3-defaults
Version: 3.2-2
Severity: important
Tag: patch
When building deb package which uses python3 and includes only private
modules, dh_python3 incorrectly inserts prerm-pyclean into the prerm
scripts instead of prerm-py3clean:
#!/bin/sh
set -e
# Automatically added by dh_python3:
if which pyclean >/dev/null 2>&1; then
pyclean -p blender2.5
else
dpkg -L blender2.5 | grep \.py$ | while read file
do
rm -f "${file}"[co] >/dev/null
done
fi
# End automatically added section
So, when upgrading my package using dh_python3, I got many warnings as
follows and many unnecessary files remained in my system:
$ LANG=C sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
blender2.5 blender2.5-gnome-support
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/18.1MB of archives.
After this operation, 98.3kB of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
blender2.5 blender2.5-gnome-support
Install these packages without verification [y/N]? y
(Reading database ... 391612 files and directories currently installed.)
Preparing to replace blender2.5 2.56.1+svn36098-0irie1~maverick1 (using
.../blender2.5_2.57+svn36144-0irie1~maverick1_amd64.deb) ...
Unpacking replacement blender2.5 ...
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/modules/bpy': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/modules/console': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/modules': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/startup/bl_operators': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/startup/bl_ui': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/startup': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_export_anim_mesh_xna': Directory not
empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_curve_svg': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/space_view3d_math_vis': Directory not
empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/modules/extensions_framework':
Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/modules': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/light_field_tools': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_mesh_ply': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_anim_bvh': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_shape_mdd': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/object_fracture': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify/metarigs': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify/rigs/biped/arm': Directory not
empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify/rigs/biped/leg': Directory not
empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify/rigs/biped': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify/rigs/misc': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify/rigs': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/rigify': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_scene_fbx': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/netrender': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_scene_m3': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/share/blender/2.56/scripts/addons/io_convert_image_to_mesh_img':
Directory not empty
dpkg: warning: unable to delete old direc
Bug#617358: python3-defaults: dh_python3 causes error if private modules include no .so files
Package: python3-defaults
Version: 3.2~rc1-2
Severity: important
Tag: patch
I tried building deb package which requires Python 3.2 and has private
modules (.py files), but received error as follows:
dh_python3 -V 3.2-3.3 /usr/share/blender/2.56/scripts
D: dh_python3:359: argv: ['/usr/bin/dh_python3', '-V', '3.2-3.3',
'/usr/share/blender/2.56/scripts']
D: dh_python3:360: options: {'recommends': None, 'verbose': False, 'package':
None, 'regexpr': None, 'guess_deps': True, 'skip_private': False, 'O': None,
'suggests': None, 'depends': None, 'vrange': ((3, 2), (3, 3)), 'no_package':
None, 'arch': None}
D: dh_python3:361: args: ['/usr/share/blender/2.56/scripts']
D: dh_python3:371: processing package blender2.5-gnome-support...
D: dh_python3:285: package blender2.5-gnome-support details = {'compile':
False, 'requires.txt': set(), 'shebangs': set(), 'private_dirs': {}, 'ext':
set()}
D: dh_python3:371: processing package blender2.5...
D: dh_python3:285: package blender2.5 details = {'compile': False,
'requires.txt': set(), 'shebangs': set(), 'private_dirs':
{'/usr/share/blender/2.56/scripts': {'compile': True}}, 'ext': set()}
Traceback (most recent call last):
File "/usr/bin/dh_python3", line 438, in
main()
File "/usr/bin/dh_python3", line 378, in main
dependencies.parse(stats, options)
File "/usr/share/python3/debpython/depends.py", line 111, in parse
if details['ext']:
KeyError: 'ext'
make[1]: *** [override_dh_python3] Error 1
make[1]: Leaving directory `/tmp/buildd/blender2.5-2.56.1+svn35400'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
The following patch should fix the bug.
diff -ur python3-defaults-3.2.orig/debpython/depends.py
python3-defaults-3.2/debpython/depends.py
--- python3-defaults-3.2.orig/debpython/depends.py 2010-12-24
04:47:49.0 +0900
+++ python3-defaults-3.2/debpython/depends.py 2011-03-08 20:14:12.981253997
+0900
@@ -108,7 +108,7 @@
# no hardcoded versions, but there's something to compile
self.depend(MINPYCDEP)
args = ''
-if details['ext']:
+if details.get('ext', False):
# use smallest and largest version to set range
extensions = sorted(details['ext'])
vr = (extensions[0], extensions[-1])
@@ -116,7 +116,7 @@
vr = options.vrange
if vr:
args += "-V %s" % vrange_str(vr)
-if details['ext']:
+if details.get('ext', False):
self.depend('|'.join("python%s" %\
vrepr(i) for i in details['ext']))
else: # pure modules only
IRIE
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#587144: (no subject)
I found a typo in dh_make file. Please check my patch. IRIE Shinsuke diff -ur dh-make-0.55.orig/dh_make dh-make-0.55/dh_make --- dh-make-0.55.orig/dh_make 2010-05-31 20:54:03.0 +0900 +++ dh-make-0.55/dh_make2010-12-20 15:28:36.982904997 +0900 @@ -519,7 +519,7 @@ } } # Figure out where documentation is -our @DOCS= split / |\n/, qx(ls -1 N[Ee][Ww][Ss] *[Ff][Aa][Qq]* *.[Tt][Xx][Tt] README* *.README [rR]eadme* *.[rR]eadme [Bb][Uu][Gg][Ss] *[tT][oO][dD][oO]* 2>/dev/null | grep -v '^CMakeList.txt'); +our @DOCS= split / |\n/, qx(ls -1 N[Ee][Ww][Ss] *[Ff][Aa][Qq]* *.[Tt][Xx][Tt] README* *.README [rR]eadme* *.[rR]eadme [Bb][Uu][Gg][Ss] *[tT][oO][dD][oO]* 2>/dev/null | grep -v '^CMakeLists.txt'); # What are our info files our @INFOS= split / |\n/, qx(find . -regex '.*\\.info\\(-[0-9]+\\)?'); # Figure out where is the first changelog, assign other similar files to docs
Bug#573969: emacsen-startup doesn't work
Package: scim-bridge-el Version: 0.7.5-1 Though scim-mode is minor mode, emacsen-startup file included in this package seems to be written considering scim-mode as major mode. Furthermore, an invalid command `scim-bridge-el-mode' is registered to autoload and the sub directory l10n will not be added to load-path. Please import the file included in original author's deb package, or replace with the equivalent of it. -- IRIE Shinsuke irieshins...@yahoo.co.jp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
