Processed: close 485569

2009-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 485569
Bug#485569: libhk-classes-dev: python 2.4/2.5 dependency
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Laurent Bonnaud 


> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#485569: libhk-classes-dev: python 2.4/2.5 dependency

2009-11-30 Thread Laurent Bonnaud
On Sat, 2009-11-28 at 21:14 +0100, Filippo Giunchedi wrote:
> 
> they got rebuilt against python2.5 (and they will be recompiled
> against 2.6 once
> it hits unstable) so I think this bug doesn't apply anymore, what do
> you think? 

Indeed.  I am going to close this bug...  Thanks for the reminder!

-- 
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/





-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Пoчтoвaя kомaния

2009-11-30 Thread ГЕРМАН Алексеевич
Горящие Pассылки по e-майл!

{vlad1oplaty}

(495)5 8562 89
38-37-671-14




-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#521107: s-p-u: security update for xfs package

2009-11-30 Thread Adam D. Barratt
On Wed, 2009-11-18 at 01:25 -0300, Luciano Bello wrote:
> El Mar 17 Nov 2009, Adam D. Barratt escribió:
> > >From a stable-update point-of-view, I'd also prefer that it was fixed in
> >
> > unstable first.  It's a lot easier to fix sid if any unforeseen problems
> > arise. :)
> 
> So, I made the QA upload few minutes ago.

As that upload has now migrated to testing without any reported issues,
please go ahead with the upload to p-u.

Regards,

Adam



--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558868: Resolve unresolved symbols in shared libraries

2009-11-30 Thread Peter Fritzsche
Source: iterm
Version: 0.5-7
Severity: wishlist
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol XtOwnSelection used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFreeFontSet used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFillRectangle used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol TtyTerminalIO_destroy used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XtAddCallback used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XmbDrawString used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFontsOfFontSet used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol VTCore_scroll_down used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol VTCore_set_screen_view used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol VTCore_redraw used by 
debian/libxiterm1/usr/lib/libXiterm.so.1.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: 81 other similar warnings have been skipped (use -v to 
see them all).



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558859: Resolve unresolved symbols in shared libraries

2009-11-30 Thread Peter Fritzsche
Source: g2
Version: 0.72-1
Severity: wishlist
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol XCreatePixmap used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFillRectangle used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XCheckWindowEvent used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol fmod used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFreeColormap used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol gdImageRectangle used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol sincos used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XSetStandardProperties used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol floor used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: symbol gdFontGiant used by 
debian/libg20/usr/lib/libg2.so.0.72 found in none of the libraries.
dpkg-shlibdeps: warning: 58 other similar warnings have been skipped (use -v to 
see them all).



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558882: Resolve unresolved symbols in shared libraries

2009-11-30 Thread Peter Fritzsche
Source: libdockapp
Version: 1:0.5.0-3
Severity: wishlist
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol XCreatePixmap used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFillRectangle used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XInternAtom used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XChangeGC used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XCopyPlane used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XSetWMHints used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XSetWMProtocols used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XSetClassHint used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XCopyArea used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XAllocIconSize used by 
debian/libdockapp2/usr/lib/libdockapp.so.2.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: 22 other similar warnings have been skipped (use -v to 
see them all).



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558869: Resolve unresolved symbols in shared libraries

2009-11-30 Thread Peter Fritzsche
Source: knoda
Version: 0.8.3-3
Severity: wishlist
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol 
_ZNK11KIconLoader8loadIconERK7QStringN5KIcon5GroupEiiPS0_b used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZN9QTextEdit6zoomInEi used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol 
_ZN13KToggleActionC1ERK7QStringS2_RK9KShortcutPK7QObjectPKcPS6_SA_ used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZN7QStringaSEPKc used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZN2Qt3redE used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol 
_ZN13KListViewItemC1EP9QListView7QStringS2_S2_S2_S2_S2_S2_S2_ used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZNK7QObject9receiversEi used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZNK9QCheckBox9hitButtonERK6QPoint used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZN11QScrollView11removeChildEP7QObject used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol _ZN11QScrollView14resizeContentsEii used by 
debian/libhk-kdeclasses7/usr/lib/libhk_kdeclasses.so.7.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: 1581 other similar warnings have been skipped (use -v 
to see them all).



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558899: Resolve unresolved symbols in shared libraries

2009-11-30 Thread Peter Fritzsche
Source: libiphone
Version: 0.9.1-4
Severity: wishlist
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol gcry_control used by 
debian/libiphone0/usr/lib/libiphone.so.0.0.0 found in none of the libraries.



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558932: Resolve unresolved symbols in shared libraries

2009-11-30 Thread Peter Fritzsche
Source: lineakd
Version: 1:0.9-6
Severity: wishlist
User: peter.fritzs...@gmx.de
Usertags: unresolved-symbols-so

I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.

Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed

More informations can be found at
 
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:

dpkg-shlibdeps: warning: symbol dlsym used by 
debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol dlclose used by 
debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol dlopen used by 
debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the 
libraries.
dpkg-shlibdeps: warning: symbol dlerror used by 
debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the 
libraries.



-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org