Bug#772635: incompatible with Firefox 34
Package: xul-ext-flashblock Version: 1.5.17-1 Severity: important After upgrading iceweasel to 34, flashblock no longer works. Problem is being discussed at https://addons.mozilla.org/ru/firefox/addon/flashblock/reviews/, fix is available there (although not from upstream). -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (650, 'stable-updates'), (650, 'stable'), (620, 'testing'), (600, 'unstable'), (580, 'experimental'), (540, 'oldstable-updates'), (540, 'oldstable'), (520, 'oldstable') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash xul-ext-flashblock depends on no packages. Versions of packages xul-ext-flashblock recommends: ii iceweasel 34.0-1~bpo70+1 xul-ext-flashblock suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694018: (no subject)
Nor it needs bluetooth signature.asc Description: This is a digitally signed message part.
Bug#678970: libetpan: new upstream version available
> Package: libetpan > Severity: wishlist > > Hi Nikita, > > Seems a new version of libetpan is available (1.1), would be nice > to have it package for Debian, and even more to have it packaged > before freeze (which is 5 days away ;) > > best regards, Since I can't promise I'll do that within 5 days, I don't object an NMU Or maybe you should just take over libetpan. I'm not anyhow active in Debian already for years, and that's unlikely to change anytime soon; you seem to be the main user of the library; it has very low maintaine cost. Nikita signature.asc Description: This is a digitally signed message part.
Bug#656148: libgeo-ip-perl: please package new version
> Package: libgeo-ip-perl > Version: 1.38-1 > Tags: ipv6 > Severity: wishlist > > > Hi, > > Last year two new versions were released. They include the C API (XS) > and along with it, support for the IPv6 database. Please update the > packaged version. Thanks for the reminder. I will try to update package soon. If that's really urgent then feel free to NMU. Nikita signature.asc Description: This is a digitally signed message part.
Bug#654931: gcc-4.6: missing manpage
> > I was hoping to ship at most one package per version. There's simply > > no way that ftpmasters are going to allow shipping a single manpage in > > each package. My original thought was gcc-manpages, but if you'd > > prefer a single package per version, I can do that, too. > > fine too. but ftp-masters did already accept the packaging of the > non-free man-pages (and docs). as long as it is fine to have a manpage > without a binary. otoh we could merge the existing non-free doc packages > to one as well. gcc-doc packages used to have *.info files as well - and those are pretty large... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655001: storeBackupRecover: fails to recover hidden directory
> Hi Nikita, > > can you double check if the version appended fixes the problem for you? > It will be there next bug fix version of storeBackup. I'm not a perl expert... How to test it without installation to system directories? I guess some env var must be set so modules from lib/ are found and used? Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655001: storeBackupRecover: fails to recover hidden directory
Package: storebackup Version: 3.2-1 Severity: important If storeBackupRecover command is requested to recover a hidden directory, it fails to do so: nikita@blacky:/tmp/x> sudo storeBackupRecover -r /backup/home/dst/2012.01.07_04.33.06/nikita/.ssh -t . nikita@blacky:/tmp/x> ls -aR .: ./ ../ nikita/ ./nikita: ./ ../ Although files are there in backup: nikita@blacky:/tmp/x> ls /backup/home/dst/2012.01.07_04.33.06/nikita/.ssh authorized_keys.bz2 id_dsa_debian.pub id_dsa_lc_svn id_rsa_debian.pub config.bz2 id_dsa_homeid_dsa_libdev.pub known_hosts.bz2 id_dsa@ id_dsa_home.pubid_dsa_lvk.pub known_hosts.old.bz2 id_dsa_debianid_dsa_ipaq.pubid_rsa_debian.bz2 mama_id_dsa.pub Similar command for non-hidden directory works as expected: nikita@blacky:/tmp/x> sudo storeBackupRecover -r /backup/home/dst/2012.01.07_04.33.06/nikita/u-boot -t . nikita@blacky:/tmp/x> ls -aR .: ./ ../ nikita/ ./nikita: ./ ../ u-boot/ ./nikita/u-boot: ./ ../ console-diff ramboot-diff -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (680, 'stable-updates'), (680, 'stable'), (600, 'unstable'), (580, 'experimental'), (520, 'oldstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages storebackup depends on: ii bzip2 1.0.5-6 high-quality block-sorting file co ii debianutils3.4 Miscellaneous utilities specific t ii perl 5.10.1-17squeeze2 Larry Wall's Practical Extraction Versions of packages storebackup recommends: ii libio-compress-bzip2-p 2.024-1 Transitional dummy package for IO: ii perl [libio-compress-b 5.10.1-17squeeze2 Larry Wall's Practical Extraction storebackup suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654931: gcc-4.6: missing manpage
> On 01/07/2012 05:36 PM, brian m. carlson wrote: > > On Sat, Jan 07, 2012 at 07:53:25AM +0100, Matthias Klose wrote: > >> won't fix in the gcc-4.6 package; clearly these "skeletal" pages are > >> not part of the upstream sources. please package those as a separate > >> package if you intend to maintain these on a regular basis. > > > > Lots of Debian packages include manpages that are not part of the > > upstream source, and Policy mandates a manpage *in the same package*. > > I'd like you to reconsider, especially since having some manpage, even > > if it isn't complete, is a lot better for users than having no manpage > > at all. > > we have the original man pages in non-free (at least we had these > packaged for earlier versions [1]; feel free to package these, I assume > Nikita would welcome the help). Sure I will welcome help on updating gcc-doc packages. I have very limited resource these days so I'm not sure when I will be able to update gcc-doc myself (although I hope that will happen before it is too late for wheezy). Nikita signature.asc Description: This is a digitally signed message part.
Bug#651728: RM: gcc-4.3-doc-non-dfsg -- ROM; gcc-4.3 no longer in unstable
Package: ftp.debian.org Severity: normal gcc-4.3-doc-non-dfsg package provides GFDL documentation for gcc-4.3 version. Since gcc-4.3 was removed from unstable, gcc-4.3-doc-non-dfsg should be removed as well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643185: libetpan: FTBFS: dpkg-buildpackage: error: dpkg-source -b libetpan-1.0 gave error exit status 2
> Source: libetpan > Version: 1.0-4 > Severity: important > Tags: wheezy sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20110923 qa-ftbfs > Justification: FTBFS on amd64 Hello. Thanks for your report. I've reproduced the issue in my environment. I've try to fix it soon. Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624071: libetpan: Uses deprecated _set_priority GnuTLS functions
forwarded 624071 https://sourceforge.net/tracker/?func=detail&aid=3295850&group_id=41064&atid=429696 thanks > Package: libetpan > Version: 1.0-4 > Severity: normal > User: ametz...@downhill.at.eu.org > Usertags: deprecated-gnutls-2.12 > > This package is using some functions which are marked deprecated in > newer versions of GnuTLS (>=2.12.x). (They are not yet removed, though.) > These functions will be removed in future releases. GnuTLS 2.12.x is > already available in experimental. Hi Thanks for your bug report. I've forwarded it upstream. Hopefully they will update the library. Nikita signature.asc Description: This is a digitally signed message part.
Bug#558389: Status?
> Squeeze is frozen and won't be updated before release. I do aim to have > Python 3 support available for PyQt in Unstable soon after it releases. Squeeze is released months ago. What is the status of this issue? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#621382: Still uses libdb4.7
> Package: libetpan > Version: 1.0-4 > Severity: normal > User: pkg-db-de...@lists.alioth.debian.org > Usertags: db5.1 > > Your package currently still uses Berkeley DB version 4.7 (libdb4.7). Huh? blacky:/# apt-cache show libetpan15 | egrep 'Version|libdb' Version: 1.0-4 Depends: libc6 (>= 2.3.6-6~), libcurl3-gnutls (>= 7.16.2-1), libdb5.1, libexpat1 (>= 1.95.8), libgcc1 (>= 1:4.1.1), libgnutls26 (>= 2.9.11-0), liblockfile1 (>= 1.0), libsasl2-2, libstdc++6 (>= 4.1.1) blacky:/# ldd /usr/lib/libetpan.so.15 | grep libdb libdb-5.1.so => /usr/lib/libdb-5.1.so (0xf74da000) That's on i386 Nikita signature.asc Description: This is a digitally signed message part.
Bug#618965: libetpan15: Breaks build system on Debian Sid
> On Sun, 20 Mar 2011 09:35:40 +0300 > > "Nikita V. Youshchenko" wrote: > > *) libetpan15 is linked against libdb4.8, but libetpan-dev depends on > > libdb5.1-dev > > This is a real issue since building packages against libetpan15 pulls > in a dependency for libdb5.1-dev but at the same time since libetpan15 > is build against libdb4.8 other builds will then require libdb4.8-dev. > The consequences is that other builds fails since you cannot fulfill > the requirements of libdb4.8-dev and libdb5.1-dev at the same time. I've just uploaded 1.0-4 with libetpan linked against libdb5.1 and libetpan-dev depending in libdb5.1-dev But you still won't be able to install libetpan-dev together with libdb4.x-dev. Nikita signature.asc Description: This is a digitally signed message part.
Bug#618965: libetpan15: Breaks build system on Debian Sid
[CCing -devel because there are several questions below] > Package: libetpan15 > Version: 1.0-3 > Severity: critical > Justification: breaks unrelated software > > Installing libetpan15(-dev) causes libdb-4.8 libdb-4.7 libdb-4.6 to be > removed since libetpan depends on libdb-5.1. libdb5.1-dev cannot > coexists with libdb > libdb-5.1. Package should always be build against > latest version in Sid. There are actually several separate issues here. *) libdb*-dev packages do conflict with each other. As soon as any package depends on one of libdb*-dev, none of others could be installed, and none of package depending on one of others. Don't know if it is a bug or a feature. #618965 is just an example of this. At least I doubt it is of severity critical. *) Generic question about dependences of libdev packages. If libfoo is linked against libbar, should libfoo-dev depend on libbar-dev? It is a question of policy. In old days, there was a requirement for such a dependency, to support static linking. But today very few people care about static linking. Is current policy on this documented anywhere? A pointer will be helpful... *) libetpan15 is linked against libdb4.8, but libetpan-dev depends on libdb5.1-dev This is a real bug (although not of severity critical!), and is caused by: - libetpan's configure script is not aware of libdb5.1, but knows about 4.8 and previous versions - in build environment, libdb4.8 package is pushed by some recursive dependences, - libdb4.8 provides libdb-4.8.so - so build successfully finishes against libdb-4.8, although libdb4.8-dev is not installed in build chroot - as for libetpan-dev dependency, it is computed by checking libdb-dev dependency [this was once implemented to support backporting], which currently is libdb5.1-dev So at least - I will fix libetpan to become aware of libdb5.1 - I will fix how libetpan-dev dependency is computed, to check actually used libdb instead of using libdb5.1 package dependeny Open question is - isn't it a bug in libdb4.8 that link against libdb4.8 suceeds when libdb4.8-dev is not installed? I don't know One more question: is it safe to have package linked against libdb4.8, and then re-link against libdb5.1? Won't that break things because of incompatible database format? [but AFAIK in case of libetpan this should be safe because libdb is used to cache things only] signature.asc Description: This is a digitally signed message part.
Bug#618965: libetpan15: Breaks build system on Debian Sid
> Package: libetpan15 > Version: 1.0-3 > Severity: critical > Justification: breaks unrelated software > > Installing libetpan15(-dev) causes libdb-4.8 libdb-4.7 libdb-4.6 to be > removed since libetpan depends on libdb-5.1. libdb5.1-dev cannot > coexists with libdb > libdb-5.1. Package should always be build against > latest version in Sid. I once implemented some logic in libetpan package to automatically compute libdbX-dev dependeny. For some reason it failed for the latest build, and I overlooked it. Sorry. Now looking at it, will upload fix ASAP. Nikita signature.asc Description: This is a digitally signed message part.
Bug#591554: libetpan-dev: Please stop depending on /usr/lib/libsasl2.la in .la file
> On Tue, Aug 10, 2010 at 11:06:09PM +0400, Nikita V. Youshchenko wrote: > > > The libetpan-dev package ships an .la file that that expresses a > > > dependency on /usr/lib/libsasl2.la. Please either clear the > > > dependency or stop shipping the .la file (c.f. Policy 10.2) so that > > > cyrus-sasl2 can do the same and also be policy compliant. > > > > Hi, > > > > this is fixed in 1.0-2, just uploaded to experimental. > > > > Unfortunately I can't upload that to unstable now, because of library > > soname change. I've discussed that with release team, and they have > > given me a window, but I happened to be away from computers at that > > time, and now it's late :( > > Nikita, > > Now that Squeeze was released last month, do you plan to upload again to > unstable? Thanks for reminder. Just uploaded it. It was ready months ago, I just forgot. Sorry. Nikita signature.asc Description: This is a digitally signed message part.
Bug#617360: aptitude: a race causes "package failed to install" message on some hosts
Package: aptitude Version: 0.6.3-3.2 Severity: minor On several amd64 squeeze hosts, I'm getting this: vedi:~# LANG=C /usr/bin/aptitude dist-upgrade -d -y No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. A package failed to install. Trying to recover: dpkg: status database area is locked by another process ... and aptitude exist with non-zero exit status, causing cron-apt to mail errors. I'm not getting this on other hosts. I've also found that error disappears when running in ru_RU.UTF-8 locale, and also if adding '--log-file=/dev/null --log-level=debug' to command line (in LANG=C locale). So it is a clear indication of a race somewhere. I realize that the above information is likely not enough to explore this bug, however I may provide more information on request. I just don't know what to check. Tried to look through strace -f logs of runs with bug reproduced, but could not find any hints. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605912: runit package changes /etc/inittab ?
While we are on topic. Maintainer scripts of runit package modify /etc/inittab Although looks like /etc/inittab is not owned by any package, so policy is not violated, this IMO still looks strange in debian context. Is modifying /etc/inittab from postinst ok for random debian package these days? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#608582: lenny -> squeeze upgrade fails because of file conflict between irb1.8 and libruby1.8
Package: libruby1.8 Version: 1.8.7.302-2 Severity: important File /usr/lib/ruby/1.8/irb/completion.rb was previously in irb1.8, and now is in libruby1.8. Because of that, lenny -> squeeze upgrade may fail, with dpkg error about file conflict. This just happened for me. A Contlicts: or Replaces: entry is likely required in libruby1.8 package. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (680, 'testing'), (620, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libruby1.8 depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libgdbm31.8.3-9 GNU dbm database routines (runtime ii libncurses5 5.7+20100313-4 shared libraries for terminal hand ii libreadline55.2-7GNU readline and history libraries ii libssl0.9.8 0.9.8o-4 SSL shared libraries ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libruby1.8 recommends no packages. libruby1.8 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591554: libetpan-dev: Please stop depending on /usr/lib/libsasl2.la in .la file
> The libetpan-dev package ships an .la file that that expresses a > dependency on /usr/lib/libsasl2.la. Please either clear the dependency > or stop shipping the .la file (c.f. Policy 10.2) so that cyrus-sasl2 can > do the same and also be policy compliant. Hi, this is fixed in 1.0-2, just uploaded to experimental. Unfortunately I can't upload that to unstable now, because of library soname change. I've discussed that with release team, and they have given me a window, but I happened to be away from computers at that time, and now it's late :( Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#584411: [pkg-fso-maint] Bug#584411: mention network security
> | |-Xorg :0 vt7 vt7 -nolisten tcp This means X is started with host-based auth enabled, but without mit-magic-cookie auth enabled. Any client from localhost will be able to connect. No remote client will be able to connect unless explicitly allowed with 'xhost +' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573362: file: wrong report on UBI images
Package: file Version: 5.04-1 Severity: wishlist When 'file' utility is used on UBI image, it is reported as something else: > file rootfs-RX-51_2009SE_3.2010.02-8_PR_MR0 rootfs-RX-51_2009SE_3.2010.02-8_PR_MR0: HIT archive data -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (640, 'stable'), (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages file depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libmagic1 5.04-1File type determination library us ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime file recommends no packages. file suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534124: Could you test again with unstable version?
> Hello Nikita, Hi > Could you test later upload to unstable? > Version: 0.0.6-2 > > Kind regards && thanks, Just re-tested with freerunner:~# LANG=C apt-cache policy xserver-xorg-input-tslib libts-0.0-0 xserver-xorg-core xserver-xorg xserver-xorg-input-tslib: Installed: 0.0.6-2 Candidate: 0.0.6-2 Version table: *** 0.0.6-2 0 500 http://blacky.home unstable/main Packages 100 /var/lib/dpkg/status libts-0.0-0: Installed: 1.0-7 Candidate: 1.0-7 Version table: *** 1.0-7 0 500 http://blacky.home unstable/main Packages 100 /var/lib/dpkg/status xserver-xorg-core: Installed: 2:1.7.4-2 Candidate: 2:1.7.4-2 Version table: *** 2:1.7.4-2 0 500 http://blacky.home unstable/main Packages 100 /var/lib/dpkg/status xserver-xorg: Installed: 1:7.5+3 Candidate: 1:7.5+3 Version table: *** 1:7.5+3 0 500 http://blacky.home unstable/main Packages 100 /var/lib/dpkg/status Result is the same - hundreds of events with the same coordinates. Nikita signature.asc Description: This is a digitally signed message part.
Bug#521918: ubuntu's patch is broken
tags 521918 -patch thanks Patch suggested by ubuntu is broken: build target mush build everything, including arch-independed part. See Debian Policy, sec. 4.9. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#518049: I considered NMU a fix for this bug, but ...
...but decided not to do so. Package looks very dirty: autotools-based build system is broken and can't be restored with autoreconf & co because if dirty tricks used in configure.ac, there are subversion temporary files left, etc NMUing this particular bug with suggested workaround won't help much. Package should be either properly maintained, or removed. signature.asc Description: This is a digitally signed message part.
Bug#551725: paplay does not work with lenny version of libsndfile1, and does not depend on later version
Package: pulseaudio-utils Version: 0.9.19-1 Severity: normal Hi. Current dependences allow pulseaudio-utils 0.9.19-1 to be installed into mixed lenny/testing/unstable system where libsndfile1 package is at 1.0.17-4+lenny2 version. However, in such installation attempt to play any wav file with 'paplay' results in > nik...@desktopvm:~> paplay /usr/share/sounds/KDE_Startup.wav > Failed to determine sample specification from file. This may be workarounded by installing later version of libsndfile1. I think that pulseaudio-utils should depend on libsndfile1 version that it actually works with :). -- System Information: Debian Release: 5.0.3 APT prefers proposed-updates APT policy: (640, 'proposed-updates'), (640, 'stable'), (620, 'testing'), (600, 'unstable'), (580, 'oldstable'), (580, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-xen-686 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pulseaudio-utils depends on: ii libasyncns0 0.3-1 Asyncronous name service query lib ii libavahi-client3 0.6.23-3lenny1 Avahi client library ii libavahi-common3 0.6.23-3lenny1 Avahi common library ii libc6 2.9-25 GNU C Library: Shared libraries ii libcap2 2.11-2 support for getting/setting POSIX. ii libdbus-1-3 1.2.1-5+lenny1 simple interprocess messaging syst ii libflac8 1.2.1-1.2 Free Lossless Audio Codec - runtim ii libgdbm3 1.8.3-3GNU dbm database routines (runtime ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libogg0 1.1.3-4Ogg Bitstream Library ii libpulse-browse0 0.9.19-1 PulseAudio client libraries (zeroc ii libpulse0 0.9.19-1 PulseAudio client libraries ii libsm62:1.0.3-2 X11 Session Management library ii libsndfile1 1.0.20-3 Library for reading/writing audio ii libvorbis0a 1.2.3-3The Vorbis General Audio Compressi ii libvorbisenc2 1.2.3-3The Vorbis General Audio Compressi ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii libx11-6 2:1.1.5-2 X11 client-side library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension pulseaudio-utils recommends no packages. Versions of packages pulseaudio-utils suggests: ii avahi-daemon 0.6.23-3lenny1 Avahi mDNS/DNS-SD daemon -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
> > Is there any chance to get this fix into lenny? AFAIU, this bug may > > affect both i386 and amd64, both dom0 and domU [if domU is running > > -xen flavour], almost on any hardware with >1 CPUs, and cause system > > crash... > > Yes, I have added it to the lenny branch. Hi I don't see any mention of this fix in the changelog of linux-2.6 2.6.26-19 package, included in the just-released lenny update. Is that for a reason? I'm asking because if 2.6.26-19 still contains #542250, I should not allow it into our servers. Nikita signature.asc Description: This is a digitally signed message part.
Bug#544681: mplayer: please add libmad support
> For the freerunner you should simply prefer ffmp3 over mp3lib. That really works. signature.asc Description: This is a digitally signed message part.
Bug#544681: mplayer: please add libmad support
Package: mplayer Version: 1.0~rc3+svn20090405-1 Severity: normal Hi Debian mplayer package is built without libmad support. Libmad is a fixed-point audio mpeg decoder.1 Without libmad support, mplayer can't be used on slow armel devices that lack hardware FPU, such as the Freerunner. Package from debian-multimedia.org is built with libmad support, and it works in Freerunner much better. Since libmad is available in debian main, please enable libmad support in the official debian mplayer package. Thanks. signature.asc Description: This is a digitally signed message part.
Bug#544104: readline-common depends on dpkg version not in archive
Package: readline-common Version: 6.0-3 Severity: serious Justification: not installable readline-common 6.0-3, currently in unstable, depends on dpkg (>= 1.15.4), while unstable contains dpkg 1.15.3.1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
> Re-tagging it as 'patch' then. > > Is there any chance to get this fix into lenny? AFAIU, this bug may > affect both i386 and amd64, both dom0 and domU [if domU is running -xen > flavour], almost on any hardware with >1 CPUs, and cause system crash... For now, I've placed amd64 and i386 debs with fix applied to http://yoush.homelinux.org:8079/nikita/xenfix/ Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
tags 542250 +patch thanks > > That means, do_IRQ can't be called on the same CPU before previous > > invocation returns. So multiple levels of "hard-interrupt contexts" > > just can't exist. > > > > Then even 2 spinning-state structures per cpu should be enough. No > > need to have more. > > > > And then my fix looks correct. It still leaves some overkill (3rd > > spinning-state), but it should reliably avoid the original crash. > > OK, agreed. Re-tagging it as 'patch' then. Is there any chance to get this fix into lenny? AFAIU, this bug may affect both i386 and amd64, both dom0 and domU [if domU is running -xen flavour], almost on any hardware with >1 CPUs, and cause system crash... Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
> There are three spinning-state structures (per CPU) here, allowing for > spinning in process context, in bottom-half (softirq) context, and in > hard-interrupt context. There is an interrupt flag (called IRQF_DISABLED in 2.6.26, it was SA_NODELAY at some point in the past AFAIR) that controls if irq handler is called immediately with interrupts disabled, or a bit later with this irq masked and interrupts enabled. Most interrupt handlers don't set this flag, so they are called with interrupts enabled. If already spinning, softrq context can't be entered other way that from after hardirq processing. From this POV, spinlock taken in irq handler and spinlock taken in softrq handler are equivalent. And I've just checked, in_interrupt() actually checks for both. > Since interrupts are generally enabled during > interrupt handlers, there need to be multiple levels of hard-interrupt > contexts (one per IRQ), if I'm not mistaken. The code in SLE 11 and XCI > appears to implement this. I've just looked into code. In Xen, hard interrupts are delivered to kernel not by hardware, but by Xen hypervisor through Xen event channels. At code level, that corresponds to (async) call to evtchn_do_upcall(). But that routine has explicit protection against double-entry on the same cpu, see the code for details. That means, do_IRQ can't be called on the same CPU before previous invocation returns. So multiple levels of "hard-interrupt contexts" just can't exist. Then even 2 spinning-state structures per cpu should be enough. No need to have more. And then my fix looks correct. It still leaves some overkill (3rd spinning-state), but it should reliably avoid the original crash. Nikita P.S. Btw, server still works without crashes :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
> On Wed, 2009-08-19 at 22:36 +0400, Nikita V. Youshchenko wrote:
> > tags 542250 +patch
> > thanks
> >
> > > ... I may guess that line 74 should check for in_interrupt() instead
> > > of in_softirq().
> >
> > I've tried that and it really fixed the problem. Server already runs
> > the same backup procedure for several hours. Previously it crashed
> > within 15 minutes.
> >
> > Here is the patch I've applied:
> >
> > --- a/drivers/xen/core/spinlock.c 2009-08-19 16:20:17.0
> > +0400 +++ b/drivers/xen/core/spinlock.c 2009-08-19
> > 17:36:55.0 +0400 @@ -71,7 +71,7 @@
> > BUG_ON(__get_cpu_var(spinning_bh).lock ==
> > lock); spinning = &__get_cpu_var(spinning_irq); } else {
> > - BUG_ON(!in_softirq());
> > + BUG_ON(!in_interrupt());
> > spinning = &__get_cpu_var(spinning_bh);
> > }
> > BUG_ON(spinning->lock);
>
> I'm glad it works for you, but it isn't a proper fix.
Could you please explain? How that code line cod hit if not in interrupt
handler?
Here is my understanding of the logic of that code. They try to track
spinlocks CPU currently spins at. CPU spinning may be interrupted only by
irq. There "normal" (not SA_NODELAY) interrupt handlers can't be active at
the same CPU at the same time. That leads to maximum 3 spinings:
- one from process context,
- one from "normal" irq handler that interrupted that process context,
- and one from SA_NODELAY irq handler that interrupted normal irq handler.
This one can't be interrupted since it runs with interrupts disabled.
If such, the code path in question corresponds to "normal" interrupt
handler starting to spin. Thus it should be in_interrupt().
How this is wrong?
Perhaps softirq handler could be activated at exit of the "normal" handler?
Maybe better check is BUG_ON(!in_interrupt() && !in_softrq()). Need to
check the code ...
Nikita
signature.asc
Description: This is a digitally signed message part.
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
tags 542250 +patch
thanks
> ... I may guess that line 74 should check for in_interrupt() instead of
> in_softirq().
I've tried that and it really fixed the problem. Server already runs the
same backup procedure for several hours. Previously it crashed within 15
minutes.
Here is the patch I've applied:
--- a/drivers/xen/core/spinlock.c 2009-08-19 16:20:17.0 +0400
+++ b/drivers/xen/core/spinlock.c 2009-08-19 17:36:55.0 +0400
@@ -71,7 +71,7 @@
BUG_ON(__get_cpu_var(spinning_bh).lock == lock);
spinning = &__get_cpu_var(spinning_irq);
} else {
- BUG_ON(!in_softirq());
+ BUG_ON(!in_interrupt());
spinning = &__get_cpu_var(spinning_bh);
}
BUG_ON(spinning->lock);
signature.asc
Description: This is a digitally signed message part.
Bug#542250: Another backtrace of the same
Here is one more backtrace of the same crash.
[ 9199.462928] Call Trace:
[ 9199.462928][] ? _spin_lock+0x3a/0x42
[ 9199.462928] [] ? :sata_sil:sil_interrupt+0x2b/0x275
[ 9199.462928] [] ? handle_IRQ_event+0x47/0x8e
[ 9199.462928] [] ? handle_level_irq+0xae/0x116
[ 9199.462928] [] ? do_IRQ+0x4e/0x9a
[ 9199.462928] [] ? evtchn_do_upcall+0x13c/0x1fc
[ 9199.462928] [] ? do_hypervisor_callback+0x1e/0x30
[ 9199.462928][] ? dummy_inode_permission+0x0/0x3
[ 9199.462928] [] ? xen_poll_irq+0x67/0x74
[ 9199.462928] [] ? xen_spin_wait+0xfa/0x139
[ 9199.462928] [] ? lock_kernel+0x4f/0x63
[ 9199.462928] [] ? :nfs:nfs_permission+0xb0/0x15f
[ 9199.462928] [] ? permission+0xb5/0x118
[ 9199.462928] [] ? __link_path_walk+0x145/0xdfa
[ 9199.462928] [] ? :nfs:nfs_sync_mapping_wait+0x151/0x33f
[ 9199.462928] [] ? path_walk+0x46/0x8b
[ 9199.462928] [] ? do_path_lookup+0x158/0x1ce
[ 9199.462928] [] ? __path_lookup_intent_open+0x56/0x97
[ 9199.462928] [] ? do_filp_open+0x9c/0x7c4
[ 9199.462928] [] ? get_unused_fd_flags+0x74/0x13f
[ 9199.462928] [] ? do_sys_open+0x46/0xc3
[ 9199.462928] [] ? system_call+0x68/0x6d
[ 9199.462928] [] ? system_call+0x0/0x6d
What is similar in all instances - it enters
... -> lock_kernel() -> xen_spin_wait() -> xen_poll_irq(),
then gets an interrupt, then enters
... -> :sata_sil:sil_interrupt() -> _spin_lock()
and gets kernel BUG at drivers/xen/core/spinlock.c:74
which is xen_spin_wait():
...
66 /* announce we're spinning */
67 spinning = &__get_cpu_var(spinning);
68 if (spinning->lock) {
69 BUG_ON(spinning->lock == lock);
70 if(raw_irqs_disabled()) {
71 BUG_ON(__get_cpu_var(spinning_bh).lock == lock);
72 spinning = &__get_cpu_var(spinning_irq);
73 } else {
74 BUG_ON(!in_softirq());
75 spinning = &__get_cpu_var(spinning_bh);
76 }
77 BUG_ON(spinning->lock);
78 }
...
So code thies to take BKL and spins there.
While spinning, interrupt arrives.
Interrupt handler tries to take another lock.
But xen_spin_wait() is not expecting attempt to take another lock when
not raw_irqs_disabled() and not in_softirq().
Here we are in interrupt handler, bit hard irq are not disabled.
Looks like check in line 70 is wrong.
Nikita
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: Looks like same issue as #516479
This looks like the same issue as reported in #516479 - although not sure. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
Package: linux-image-2.6.26-2-xen-amd64 Version: 2.6.26-17lenny2 Severity: normal I'm running several servers (Dual Core AMD Opteron, 16G of ram) with Xen. Dom0 is debian lenny adm64. Today I tried to run a large backup in dom0 - copy NFS-mounted partition to a local volume group. buki:~# cd backup/ buki:~/backup# mount homes:/srv/homes src buki:~/backup# mount /dev/vg/homes-backup dst buki:~/backup# (cd src && tar cpf - .) | (cd dst && tar xpf -) This resulted into server crash in a few minutes. Crash is reproducible - if after reboot I try the same, same crash happens soon with similary-looking backtrace. [ 712.450538] [ cut here ] [ 712.450538] kernel BUG at drivers/xen/core/spinlock.c:74! [ 712.450538] invalid opcode: [1] SMP [ 712.450538] CPU 0 [ 712.450538] Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs sctp libcrc32c ipv6 lock_dlm gfs2 dlm configfs bridge 8021q dm_emc dm_round_robin dm_multipath loop psmouse pcspkr serio_raw k8temp i2c_amd8111 i2c_amd756 i2c_core button amd_rng rng_core shpchp pci_hotplug evdev reiserfs dm_mirror dm_log dm_snapshot dm_mod raid456 async_xor async_memcpy async_tx xor raid1 md_mod ide_cd_mod cdrom ide_pci_generic sd_mod amd74xx ide_core floppy lpfc scsi_transport_fc scsi_tgt tg3 e100 mii sata_sil ata_generic ohci_hcd libata scsi_mod dock thermal processor fan thermal_sys [ 712.450538] Pid: 5636, comm: tar Not tainted 2.6.26-2-xen-amd64 #1 [ 712.450538] RIP: e030:[] [] xen_spin_wait+0x90/0x139 [ 712.450538] RSP: e02b:80595e38 EFLAGS: 00010246 [ 712.450538] RAX: 88001b1adfd8 RBX: 880001bbda20 RCX: 88008162e000 [ 712.450538] RDX: ff5f7000 RSI: 8483 RDI: [ 712.450538] RBP: 0103 R08: dc38d979 R09: [ 712.450538] R10: R11: 0246 R12: [ 712.450538] R13: 88001fe7f698 R14: 88001fe7f698 R15: [ 712.450538] FS: 7f3ef40eb6e0() GS:80539000() knlGS: [ 712.450538] CS: e033 DS: ES: [ 712.450538] DR0: DR1: DR2: [ 712.450538] DR3: DR6: 0ff0 DR7: 0400 [ 712.450538] Process tar (pid: 5636, threadinfo 88001b1ac000, task 88001e270280) [ 712.450538] Stack: 88001da47480 88001fe7f698 8483 [ 712.450538] 0013 80435886 88001d8f8700 [ 712.450538] a00854f4 c201ac00 [ 712.450538] Call Trace: [ 712.450538][] ? _spin_lock+0x3a/0x42 [ 712.450538] [] ? :sata_sil:sil_interrupt+0x2b/0x275 [ 712.450538] [] ? handle_IRQ_event+0x47/0x8e [ 712.450538] [] ? handle_level_irq+0xae/0x116 [ 712.450538] [] ? do_IRQ+0x4e/0x9a [ 712.450538] [] ? evtchn_do_upcall+0x13c/0x1fc [ 712.450538] [] ? do_hypervisor_callback+0x1e/0x30 [ 712.450538][] ? dummy_inode_setattr+0x0/0x3 [ 712.450538] [] ? xen_poll_irq+0x67/0x74 [ 712.450538] [] ? xen_spin_wait+0xfa/0x139 [ 712.450538] [] ? lock_kernel+0x4f/0x63 [ 712.450538] [] ? :reiserfs:reiserfs_setattr+0x25/0x27d [ 712.450538] [] ? __up_read+0x13/0x8a [ 712.450538] [] ? :reiserfs:reiserfs_getxattr+0xa9/0xbe [ 712.450538] [] ? notify_change+0x174/0x2f5 [ 712.450538] [] ? chown_common+0x8c/0xa1 [ 712.450538] [] ? mnt_want_write+0x31/0x86 [ 712.450538] [] ? sys_chown+0x4b/0x6f [ 712.450538] [] ? dput+0x35/0x13e [ 712.450538] [] ? sys_futimesat+0x88/0x9e [ 712.450538] [] ? system_call+0x68/0x6d [ 712.450538] [] ? system_call+0x0/0x6d [ 712.450538] [ 712.450538] [ 712.450538] Code: 30 fa 58 80 4c 39 2c 08 75 04 0f 0b eb fe 48 c7 c0 40 fa 58 80 eb 1f 65 48 8b 04 25 10 00 00 00 66 f7 80 44 e0 ff ff 00 ff 75 04 <0f> 0b eb fe 48 c7 c0 30 fa 58 80 48 8d 1c 08 48 83 3b 00 74 04 [ 712.450538] RIP [] xen_spin_wait+0x90/0x139 [ 712.450538] RSP [ 712.450538] ---[ end trace 73e60cdc01c1f34c ]--- [ 712.450538] Kernel panic - not syncing: Aiee, killing interrupt handler! Server info: buki:~# cat /proc/version Linux version 2.6.26-2-xen-amd64 (Debian 2.6.26-17lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Aug 14 10:19:53 UTC 2009 buki:~# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 33 model name : Dual Core AMD Opteron(tm) Processor 280 stepping: 2 cpu MHz : 2391.532 cache size : 1024 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good pni lahf_lm cmp_legacy bogomips
Bug#542190: please adjust automake build-dependency version
Package: libtool Version: 2.2.6a-4 Severity: minor Currently, libtool package's debian/control declares build dependency on automake (>= 1:1.10). However, it does not build with automake 1.10: ... autoreconf: running: automake --add-missing --copy --force-missing configure.ac:125: require Automake 1.10.1, but have 1.10 ... configure: creating ./config.status config.status: error: cannot find input file: Makefile.in make: *** [config-stamp] Error 1 I've facing this while doing some local backporting work, which included building libtool 2.2.6a-4 for etch. Please adjust build-dependency to automake (>= 1.10.1). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#475092: Bug#460288: Bug#475092: works for me in 3.1.0-5
> Viktor Horvath wrote: > > The original bug report seems to me a duplicate of #460288. > > Might be, yes. (Ccing that bug and its submitter...) > > > I had the same problem using 2.4.1-7, but I just upgraded to 3.1.0-5 > > and it works there! > > Too bad the submitter of #475092 never saw your mail because you didn't > send the mail to him at all. ;-) > > (n...@bugs.debian.org just goes to the maintainer and the bug log, *NOT* > to the submitter). CCing. > > Can you confirm that 1:3.1.0-5 works? Hi! I'm the submitter of #460288. Unfortunately I can't test original bug condition now since I've converted all my systems to utf8 long ago. With OOo 1:3.1.0-5~bpo50+1 and ru_RU.UTF-8 locale, files with cyrillic symbols open ok both when OOo is already running and if it is not already running. But that does not mean that things work correctly with koi8r locale. Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534328: [Pkg-e-devel] Bug#534328: Bug#534328: libeina-svn-01 causes broken e17 start-up
> Hi > > 2009/6/23 Albin Tonnerre > > > On Tue, Jun 23, 2009 at 06:39:33PM +0200, Niklas wrote : > > > Package: libeina-svn-01 > > > Version: 0.0.2.061-1 > > > Severity: important > > > > > > > > > Hi, > > > > Hi, > > > > > after updateing libeina-svn-01 today, e17 does not start anymore, I > > > get a flickering black screen after startx. No errors in > > > /var/log/Xorg.0.log. > > > > Does ~/.xsession-errors say anything ? > > Xsession: X session started for piknik at Tue Jun 23 13:05:49 CEST 2009 > enlightenment: error while loading shared libraries: > libeina-ver-pre-svn-01.so.0: cannot open shared object file: No such \ > file or directory > > :~$ ls -l /usr/lib/libeina-ver-pre-01.so.0* > > lrwxrwxrwx 1 root root27 2009-06-23 19:16 > /usr/lib/libeina-ver-pre-01.so.0 -> libeina-ver-pre-01.so.0.0.2 > -rw-r--r-- 1 root root 81496 2009-06-22 00:37 > /usr/lib/libeina-ver-pre-01.so.0.0.2 So looks like upgraded package brings library with a changed soname? For my best knowledge, this is not allowed in debian packaging :) signature.asc Description: This is a digitally signed message part.
Bug#534177: [pkg-fso-maint] Bug#534177: Please provide single-precision library as well
> > > on some hardware like the Openmoko FreeRunner, using libode built > > > with double precision is not possible, as it it just too slow. This > > > can be worked around with building ode with single precision. Having > > > such a package in Debian would enable the use of mokomaze. > > > ... > > > > Make sence, but how will you switch between the two different lib > > since they don't share the same ABI? Maybe we can disable double > > precision on the slow archs (armel, mips, m68k). I don't know if it's > > an acceptable solution? > > hmm, right, didn’t think of the ABI incompatibility. > > Making this dependent on the architecture sounds like a good compromise > to me, at least until someone else complains. Why not just make two libs with different sonames? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534124: xserver-xorg-input-tslib: reports lots of same MotionEvents
Package: xserver-xorg-input-tslib Version: 0.0.5-8 Severity: normal Hi I have a Neo Freerunner running Debian. It uses xserver-xorg-input-tslib to drive touchscreen device. Using xev, I've found that while stylus is kept touched, there are lots of MotionEvent's generated, mostly with even the same coordinates. This is not good. Devices like freerunner are slow, and applications that try to handle MotionEvent (like a drawing application) just can't keep. I believe that at least MotionEvent should not be generated if coordinates did not change from the last MotionEvent. And maybe even if coordinates change only from 1-2 pixels (may be a parameter). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534118: bluez: /etc/dbus-1/system.d/bluetooth.conf references possibly non-existant netdev group
Package: bluez Version: 4.40-2 Severity: minor Hi. bluez package provides /etc/dbus-1/system.d/bluetooth.conf file, that (as of bluez 4.40-2) mentions "netdev" group: ... ... However bluez postinst does not create this group, and it is not guaranteed to exist (currently is gets created on most desktop systems by avahi, but bluez may be installed e.g. on embedded system that does not have avahi installed). This at least results in ugly error messages on system boot. Please consider adding something like # Add the netdev group unless it's already there if ! getent group netdev >/dev/null; then addgroup --quiet --system netdev || true fi to bluez postinst. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532243: (no subject)
Sorry, I've sent incomplete bug report text - with deleted problem description... With previous (0.8.x) versions, I was able to scroll book with fingers. With the current version, I can't. And that is the problem I'm trying to solve. In the current version of fbreader, tap scrolling more or less works with stylus, but does not with fingers. More particular, "sometimes" it works even with fingers, and "sometimes" it does not work even with stylus. As per http://www.fbreader.org/docs/maemoIssues.php, it looks like fbreader tries to distinguish between stylus taps and finger taps, and behave differently. And the result is unwanted. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532244: arora: Please provide a setting for default page font size/scale
Package: arora Version: 0.7.0-1 Severity: wishlist Hi I'm trying to use Arora web browser on Neo Freerunner phone (running Debian). Freerunner has a 285 dpi screen. That causes obvious 'tiny font' issues. To make web pages in Arora readable, I have to select 'Increase size' from menu 4-5 times. It's very annoying to do that every time :). Could you please provide a configuration option that will set the default scale and reuse it in new windows/tabs? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532243: fbreader: tap scrolling Cmade difficult?
Package: fbreader Version: 0.10.7dfsg-2 Severity: normal Hi, I've upgraded fbreader package on Neo Freerunner from 0.8.x to 0.10.7dfsg-2, and now tap scrolling with fingers is somewhat difficult to use. Previously, touching the screent near the bottom caused page down, and touching screen near the top caused page up. Looks like the issue is similar to what ia described at http://www.fbreader.org/docs/maemoIssues.php Is it possible to get the options mentioned there in the debian package? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532236: [Pkg-e-devel] Bug#532236: libedje-svn-01: small fonts on Openmoko GTA01 Neo 1973
> Hi there! > > E17 shows small fonts on the Openmoko GTA01 Neo 1973 (fbdev at 96 dpi, > while the real ones for this touchscreen are 285): This may be workarounded at e17 config level, in Look => Scaling, try to lower Relative. signature.asc Description: This is a digitally signed message part.
Bug#532214: [Pkg-e-devel] Bug#532214: libefreet-svn-01: does not show applications in Utility category
> Both efreet and the E17 XDG menu [1] are not *fully* conform to the > freedesktop.org Desktop Menu Specification v1.0 since they do not > support all the Main Categories [2]. > > [1] /etc/xdg/menus/enlightenment-applications.menu > [2] > http://standards.freedesktop.org/menu-spec/menu-spec-1.0.html#category-r >egistry > > - Audio and Video alone are not supported, while they are if the > .desktop file contains the AudioVideo category as well (this is > required by the specs, thus this is not really a bug, but still). > > - For the Settings category, the specs specify that "entries may appear > in a separate menu or as part of a 'Control Center'". > > FWIW, from a quick analysis on a default Debian lenny, I found that > most of the application in the Settings category specify the System > category as well, like synaptic or update-manager. > > - Education and Utility are not supported at all, thus applications like > gedit or matchbox-keyboard are not shown on the Illume desktop "Application" is not included as well, which leaves out tangogps. As for matchbox-keyboard - does it work under e17/illume at all? It does not for me (process starts, but nothing is shown). But it is not a big problem, since illume's own keyboard now works :) I even suggest to add Category: MB to Exclude, to avoid polluting illume launcher with icons for non-working-under-illume things. Also openmoko-panel-plugin.desktop may be excluded - although it may be better to fix openmoko-panel-plugin itself to move it out of Office: category. signature.asc Description: This is a digitally signed message part.
Bug#527998: [pkg-fso-maint] Bug#527998: nodm: [INTL:ru] Russian debconf templates translation
> Russian debconf templates translation is attached. > Small correction: "Embedded systems" should be translated to russian as "Встроенные системы". ru.po Description: application/gettext
Bug#520637: grub-common: grub-probe tries to scan raid physical volume as lvm physical volume and segfaults because of that
Package: grub-common Version: 1.96+20080724-16 Severity: normal Today, while installing security updates on a server running Debian Lenny (amd64), I faced an issue with linux-image-2.6.26-1-amd64 package being unable to configure. That was caused by grub-update failure, which in turn was caused by executeon of 'grub-probe --device-map=/boot/grub/device.map -t device /' resulting into a segfault. Program received signal SIGSEGV, Segmentation fault. 0x00406199 in grub_strchr (s=0x0, c=125) at kern/misc.c:241 241 while (*s) (gdb) where #0 0x00406199 in grub_strchr (s=0x0, c=125) at kern/misc.c:241 #1 0x004229fa in grub_lvm_scan_device (name=0x17210c0 "hd0,2") at disk/lvm.c:524 #2 0x004046ed in iterate_partition (disk=0x1721030, partition=0x7fff18bc04d0) at kern/device.c:132 #3 0x0041f341 in pc_partition_map_iterate (disk=0x1721030, hook=0x7fff18bc064f) at partmap/pc.c:155 #4 0x004080cb in grub_partition_iterate (hook=0x7fff18bc064f) at kern/partition.c:124 #5 0x00404781 in iterate_disk (disk_name=0x1721270 "hd0") at kern/device.c:101 #6 0x00401ea8 in grub_util_biosdisk_iterate (hook=0x7fff18bc0638) at util/biosdisk.c:139 #7 0x00404bde in grub_disk_dev_iterate (hook=0x7fff18bc0638) at kern/disk.c:205 #8 0x00404640 in grub_device_iterate ( hook=0x421ed0 ) at kern/device.c:138 #9 0x00422b08 in grub_mod_init (mod=0x0) at disk/lvm.c:588 #10 0x00422af0 in grub_lvm_init () at disk/lvm.c:586 #11 0x00423d05 in grub_init_all () at grub_probe_init.c:45 #12 0x00401d40 in main (argc=5, argv=0x7fff18bc07e8) at util/grub-probe.c:366 I've tried to debug the problem and found that it happens while grub-probe parses lvm metadata read from /dev/sda2. However, on my system, /dev/sda2 is used as a physical volume for raid5! There indeed is an LVM physical volume over that raid array, so reading sda2 as a raw device at some offsets may return data that looks like LVM data. However, reading at different offset won't return data expected by grub-probe's LVM metadata parser. So segfault. Interesting, numerous previous runs of grub-update (and underlying grub-probe) did not segfault. Don't know what and where changed such that this issue was triggered. For now, I was able to workaround the issue this way: --- ./grub_probe_init.c.orig2009-03-21 17:01:49.0 +0300 +++ ./grub_probe_init.c 2009-03-21 16:34:20.0 +0300 @@ -42,8 +42,8 @@ grub_pc_partition_map_init (); grub_apple_partition_map_init (); grub_gpt_partition_map_init (); - grub_lvm_init (); grub_raid_init (); + grub_lvm_init (); } void grub_fini_all (void) @@ -68,6 +68,6 @@ grub_pc_partition_map_fini (); grub_apple_partition_map_fini (); grub_gpt_partition_map_fini (); - grub_lvm_fini (); grub_raid_fini (); + grub_lvm_fini (); } So if raid module is initialized before lvm, grub-probe somehow detects that sda2 is a raid physical volume, and does not try to parse lvm metadata from there. I'm unsure that this workaround is the solution, since both lvm-over-raid and raid-over-lvm is possible. Although lvm-over-raid is much more common :). -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (640, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub-common depends on: ii base-files5 Debian base system miscellaneous f ii libc6 2.7-18 GNU C Library: Shared libraries grub-common recommends no packages. Versions of packages grub-common suggests: pn multiboot-doc (no description available) -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#514018: [Pkg-e-devel] Bug#514018: e17: I would also like to raise severity...
> got tired with all opkg mess, decided to get back to Debian ;) > especially since there is e17 package! THANKS! FYI, I've just uploaded updated e17 stack to pkg-fso ... but it does not fix no-icons problem :( But what about font? Could you get a reasonable (i.e. readable without a microscope) font in illume's window title? Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519371: [Pkg-e-devel] Bug#519371: e17: missing builds for anything else but i386
> Package: e17 > Version: 0.16.999.050+svn20090203-1 > Severity: important > > > Sorry for a lame report but I can't install e17 on my amd64 box ;) Please wait while all required components will go out of NEW. Then autobuilders will do the job. While those are in NEW, package can't be installed even on i386 because of missing dependences. It is somewhat disappointiong to have packages in NEW for more than 2 months, bit that's out of pkg-e team's control. Nikita signature.asc Description: This is a digitally signed message part.
Bug#514018: [Pkg-e-devel] [pkg-fso-maint] Updated pkg-e packages
> I'm looking forward to seeing your answer to my last mail on #514018 > > OTOH, there's an e17-applications.menu provided with e17 > > that you might want to try - it does work way better here (well, at > > least it displays most icons). I'd be interested in the result you get > > when using it My test is: remove ~/.e/ completely, then start X with e17. First a dialog appears that asks me for language. Btw, "Russian" is the only choice there - but that could be related to the fact that I don't have other locales generated. Second, I'm asked for "module" (or something similar, don't remember and can't test right now) and I choose Illime from the option list. Then, I get a two-choice question with "debian-menu.menu" and "e17-applications.menu" choices. Then, I get a question abouth what to include into quick launcher, with icons for currently installed programs and a checkbox near each. Then, illume desktop appears. With the current package set, I get no icons regardless of what I answer to the last two questions. Tried both "debian-menu.menu" and "e17-applications.menu" in the former. Tried to select nothing, or some, or all on the later question. But perhaps something got broken in my filesystem during larse number of package installs/uninstalls/upgrades? What should I check (other than removing ~/.e/) to ensure a "clean startup"? P.S. I think I can provide remote access to my FR over a fast connection if that will help to find out what is going wrong. Nikita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#518801: lintian: postinst-does-not-call-installdocs is obsolete
Package: lintian Version: 2.2.6~bpo50+1 Severity: normal Looks like debhelper no longer adds calls to installdocs. This is from debhelper 7.2.3 changelog: * dh_installdocs: No longer add maintainer script code to call doc-base, as it supports triggers in stable. I've checked and yes - although there are no installdocs calls in packages generated by this debhelper version, doc-base triggers do the job of documents (un)registration. So likely postinst-does-not-call-installdocs and prerm-does-not-call-installdocs are now obsolete. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (640, 'stable'), (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lintian depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii diffstat1.45-2 produces graph of changes introduc ii dpkg-dev1.14.25 Debian package development tools ii file4.26-1 Determines file type using "magic" ii gettext 0.17-4 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1Help i18n of RFC822 compliant conf ii libdigest-sha-perl 5.47-1 Perl extension for SHA-1/224/256/3 ii libipc-run-perl 0.80-2 Perl module for running processes ii libparse-debianchan 1.1.1-2 parse Debian changelogs and output ii libtimedate-perl1.1600-9 Time and date functions for Perl ii liburi-perl 1.35.dfsg.1-1Manipulates and accesses URI strin ii man-db 2.5.2-4 on-line manual pager ii perl [libdigest-sha 5.10.0-19Larry Wall's Practical Extraction lintian recommends no packages. Versions of packages lintian suggests: ii binutils-multiarch 2.18.1~cvs20080103-7 Binary utilities that support mult ii libtext-template-pe 1.44-1.2 Text::Template perl module ii man-db 2.5.2-4 on-line manual pager -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512952: thoughts
> - dpkg refuses to convert normal directory to a symlink on upgrade, so I > can't provide an upgrade path. There is a standard solution for this. Add to preinst something similar to if [ -d /usr/share/FBReader/default/ ]; then mkdir -p /etc/FBreader mv /usr/share/FBReader/default/* /etc/FBreader rmdir /usr/share/FBReader/default/ ln -s /etc/FBreader /usr/share/FBReader/default/ fi > - fbreader is not a system service/program/daemon, it's a end-user > program, and different users may want to use different layouts; > > I would suggest introducing reading some settings from user home > directory. I have just forwarded this suggestion to upstream BTS. Although you are probably correct, having system-wide default will not hurt. And it has an advantage that it could be done at packaging level now, without any code altering. Btw, systems in question, where default settings are not good (phones, etc) are commonly single user. Nikita signature.asc Description: This is a digitally signed message part.
Bug#515854: libetpan-dev: just rebuild fixes the bug
> Package: libetpan-dev > Followup-For: Bug #515854 > > Hi again Nikita, > > Only rebuild is needed to fix this. > Also, uploading to sid would be appreciated. > > If you don't have time right now I can prepare a NMU, just tell me. > > Thanks in advance, I'd prefer to do it myself on the weekend. Could you wait before than? If not, then please proceed with NMU -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514018: This is related to menu-xdg and/or menu package not installed
Hi After installing menu and menu-xdg packages (btw, why e17 does not depend on those?), and removing ~/.e, my desktop was not empty. It contained xman launcher, that really launched xman. But nothing more. Nikita signature.asc Description: This is a digitally signed message part.
Bug#514249: History of the change
Hi > Nikita - can you shed some more light on this change and why it was > necessary? As far as I can remember, there have been some moment when -$arch-cross created by "older" version of dpkg-cross became incompatible with -$arch-cross packages created by "newer" version. So something was needed to stop -$arch-cross packages created by "older" dpkg-cross from satisfying dependences of the -$arch-cross packages created by "newer" dpkg-cross. To solve that, "layout versions" have been introduced. I can't remember all the details now - too many time passed :). Nikita signature.asc Description: This is a digitally signed message part.
Bug#514018: [Pkg-e-devel] Bug#514018: [pkg-fso-maint] Bug#514018: e17: missing Illume launcher icons
> I do not know which SVN snapshot the FreeSmartphone.Org images uses, > sorry. FSO packages are exactly the same packages as Albin prepared for experimental, and that are in NEW already for a month. The only differennce is ~fr.1 suffix at version strings. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#489233: Same with OOo3 from experimental
severity 489233 important found 489233 1:3.0.1~rc2-1 thanks Same is happenning with OOo3 packages currently in experimental. Bad. Especially when pasting from document into shell command line. This really may cause data loss - when absolutely unexpected ... :(. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513072: update-initramfs: please support running external hooks
> right those hooks should be set up by linux-2.6 not initramfs-tools. > kernel-package uses /etc/kernel and linux-2.6 should use that > structure too. > > closing as this has no relation with initramfs-tools Sorry, but what linux-2.6 has to do with initramfs update trigged by e.g. mdadm (or random kernel module) package upgrade? Those do call update-initramfs, not whatever linux-2.6 hooks ... signature.asc Description: This is a digitally signed message part.
Bug#513072: update-initramfs: please support running external hooks
Package: initramfs-tools Version: 0.92o Severity: wishlist There are different things that could be required to do after initramfs image was created or updated, depending on system setup. That may include copying initramfs to xen dom0 (or external bootserver), updating non-standard bootloader (think all sorts of embedded systems), or whatever. Currently run_bootloader() routine tries to guess what it should do. But it does not (and it can not) cover all posible cases. It would be better to just add a hooks, configured in /etc/kernel-img.conf or whereever else, that will run before and after image create, update or remove. Hooks should get information about action, kernel version, and initramfs filename. Hooks may coexist with current run_bootloader(), or eventually replace it. -- Package-specific info: -- /proc/cmdline root=/dev/mapper/vg-root ro -- /proc/filesystems reiserfs iso9660 ext3 -- lsmod Module Size Used by nls_utf86272 1 ext3 125072 0 jbd51240 1 ext3 mbcache12804 1 ext3 isofs 35880 1 nls_base 12932 2 nls_utf8,isofs tun14084 1 kvm_amd29580 1 kvm 127464 1 kvm_amd ppdev 11656 0 lp 14724 0 autofs424200 1 ppp_deflate 9216 0 zlib_deflate 23960 1 ppp_deflate zlib_inflate 18944 2 isofs,ppp_deflate bsd_comp9600 0 nfsd 248360 17 auth_rpcgss47520 1 nfsd exportfs8704 1 nfsd nfs 251696 1 lockd 68560 2 nfsd,nfs nfs_acl 7552 2 nfsd,nfs sunrpc197480 17 nfsd,auth_rpcgss,nfs,lockd,nfs_acl ipt_ULOG 13736 2 xt_state6656 1 ipt_MASQUERADE 7296 1 xt_TCPMSS 8448 1 xt_tcpmss 6656 1 ipt_REJECT 7552 3 xt_tcpudp 7680 144 iptable_nat 9872 1 nf_nat 23192 2 ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 19352 4 iptable_nat,nf_nat nf_conntrack 71440 5 xt_state,ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4 iptable_filter 7424 1 ip_tables 21520 2 iptable_nat,iptable_filter x_tables 25224 9 ipt_ULOG,xt_state,ipt_MASQUERADE,xt_TCPMSS,xt_tcpmss,ipt_REJECT,xt_tcpudp,iptable_nat,ip_tables bridge 53544 0 ppp_async 13056 1 crc_ccitt 6528 1 ppp_async ppp_generic27816 7 ppp_deflate,bsd_comp,ppp_async slhc 10112 1 ppp_generic ipv6 288328 70 loop 19468 2 psmouse42268 0 parport_pc 31016 1 parport41776 3 ppdev,lp,parport_pc pcspkr 7040 0 k8temp 9216 0 button 11680 0 i2c_nforce210752 0 i2c_core 27936 1 i2c_nforce2 evdev 14208 3 reiserfs 211072 5 dm_mirror 20608 0 dm_log 13956 1 dm_mirror dm_snapshot19400 2 dm_mod 58864 31 dm_mirror,dm_log,dm_snapshot raid456 125984 1 async_xor 8448 1 raid456 async_memcpy6912 1 raid456 async_tx 11764 3 raid456,async_xor,async_memcpy xor 9744 2 raid456,async_xor raid1 24192 1 md_mod 80164 4 raid456,raid1 ide_cd_mod 36360 0 cdrom 37928 1 ide_cd_mod sd_mod 29376 12 amd74xx13448 0 [permanent] ide_pci_generic 9220 0 [permanent] ide_core 128284 3 ide_cd_mod,amd74xx,ide_pci_generic sata_nv27528 8 8139cp 23808 0 ata_generic10116 0 libata165472 2 sata_nv,ata_generic scsi_mod 160760 2 sd_mod,libata forcedeth 54032 0 ohci1394 32564 0 dock 14112 1 libata 8139too28288 0 ieee1394 93816 1 ohci1394 ehci_hcd 36108 0 mii 9856 2 8139cp,8139too ohci_hcd 25092 0 thermal22688 0 processor 42304 1 thermal fan 9352 0 thermal_sys17728 3 thermal,processor,fan -- /etc/kernel-img.conf Do_Symlinks = no do_initrd = Yes postinst_hook = update-grub postrm_hook = update-grub do_bootloader = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: L
Bug#512965: util-linux: rtcwake does not work on neo freerunner
Package: util-linux Version: 2.13.1.1-1 Severity: normal rtcwake from util-linux 2.13.1.1-1 (arch armel) does not work on Neo Freerunner running debian: freerunner:~# rtcwake -s 30 rtcwake: /dev/rtc0 not enabled for wakeup events However, in [1] thread people show example programs that provide rtcwake-like functionality on Freerunner. So likely rtcwake from util-linux has some bug and needs a fix. [1] http://lists.openmoko.org/pipermail/community/2009-January/040562.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512955: fbreader: please provide finger-friendly "far-scrolling"
Package: fbreader Version: 0.8.17-12 Severity: wishlist With fbreader on Neo Freerunner, it is currently hard to do "far-scrolling" (that means, more than several pages up or down). Although there is a scrollbar near window bottom, it is too thin to be used with a finger, and even with a stylus tapping on that scrollbar gives accuracy of +/- 50 screen pages :(. I think it would be good to extend current "tap scrolling" as follows. If user just taps at bottom part of the screen, then do page down - as now. If user puts finger on bottom part of the screen and does not remove it, the text should scroll forward at increasing speed. Similar for top part of screen and scrolling backward. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512952: fbreader: please make files in /usr/share/FBReader/default/ conffiles
Package: fbreader Version: 0.8.17-12 Severity: wishlist Files in /usr/share/FBReader/default/ are actually configuration files that could be customized. For example, default toolbar.xml defines a toolbar that does not fit on screen on Neo Freerunner. Please move that files to /etc/fbreader (you may just symlink /usr/share/FBReader/default there), so changes in those files will be preserved on package upgrades. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512663: When logging to remote, hostname gets doubled
Package: rsyslog Version: 3.18.6-3 Severity: normal Looks like fresh lenny installs come with rsyslog instead of old syslogd. In our network, logs from all hosts are sent to one server, called loghost, using remote logging. There, logs are checked by logcheck. Most of the net, including loghost, currently runs etch. But there are several new hosts with lenny. On these hosts, I've added this to /etc/rsyslogd.conf: # Send all logs to loghost *.* @loghost.lvknet This works, however on loghost (running syslogd from etch), all lines got from lenny hosts have hostname doubled: Jan 22 19:20:22 buki.lvknet buki /USR/SBIN/CRON[31333]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Here, hostname (buki) is written twice. This is not good, since that breaks all logcheck rules that come from various packages. Btw, in local log files, hostname is not doubled. Any possibility to make rsyslogd not to double hostname when sending logs to remote? -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (580, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-xen-686 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#511561: /usr/bin/kstart from kdebase-runtime-bin-kde4 incompatible with kde3
Package: kdebase-runtime-bin-kde4 Version: 4:4.1.0-2 Severity: normal As far as I understand, lenny kdebase-runtime-bin-kde4 package is supposed to be compatible with lenny's KDE3 desktop. However, /usr/bin/kstart from kdebase-runtime-bin-kde4 misbehaves. I like to run 'xload' embedded into KDE's panel. To start it, I use the follwoing command: kstart --windowclass XLoad --tosystray /usr/X11R6/bin/xload -bg black -fg green -hl red -update 1 -nolabel This used to work until I installed okular package (from lenny), which pulled kdebase-runtime-bin-kde4 by dependences. Now the above does not work as expected. Instead, it causes bad misconfiguration of running session - all windows are moved to the current virtual desktop, panel no longer exists on desktop other than current. Also kstart process does not terminate, and xload is started as a normal window. Restoring kdebase-bin-kde3 makes start working again. But removes okular... -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kdebase-runtime-bin-kde4 depends on: ii kdebase-runtime 4:4.1.0-2 runtime components from the offici ii kdelibs5 4:4.1.0-3 core libraries for all KDE 4 appli ii libc6 2.7-16 GNU C Library: Shared libraries ii libqt4-dbus 4.4.3-1Qt 4 D-Bus module ii libqtcore44.4.3-1Qt 4 core module ii libqtgui4 4.4.3-1Qt 4 GUI module ii libstdc++64.3.2-1.1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-2 X11 client-side library Versions of packages kdebase-runtime-bin-kde4 recommends: ii hal 0.5.11-8 Hardware Abstraction Layer ii pmount0.9.18-2 mount removable devices as normal kdebase-runtime-bin-kde4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#511459: openoffice.org-kde: open dialog does not appear
Package: openoffice.org-kde Version: 1:3.0.1~rc1-2 Severity: normal In OOo 3 from experimental, if OOo is configured to use KDE native dialogs, open dialog does not appear when "Open" is selected from menu or toolbar. Also, if then writer window is closed, process does not terminate, and on attempt to start writer again, window does not appear. If OOo is not configured to use KDE native dialogs, these problems are not there, and OOo works as expected. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openoffice.org-kde depends on: ii kdelibs4c2a 4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for al ii libc62.7-16 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1 GCC support library ii libqt3-mt3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.2-1 The GNU Standard C++ Library v3 ii libstlport4.6ldb 4.6.2-3.2 STLport C++ class library ii libx11-6 2:1.1.5-2 X11 client-side library ii openoffice.org-c 1:3.0.1~rc1-2 OpenOffice.org office suite archit ii openoffice.org-s 1:3.0.1~rc1-2 Crystal symbol style for OpenOffic ii ure 1.4+OOo3.0.1~rc1-2 UNO runtime environment openoffice.org-kde recommends no packages. Versions of packages openoffice.org-kde suggests: ii kmail 4:3.5.9-5KDE Email client ii konqueror 4:3.5.9.dfsg.1-6 KDE's advanced file manager, web b pn openoffice.org-kab (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#511412: clocksource/0: Time went backwards
Package: linux-image-2.6.26-1-xen-686 Version: 2.6.26-12 Severity: normal After upgrading a domU from etch to lenny kernel, I've faced a hard domU lockup that very looks like http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1098 after severak hours f running. I've applied the workaround descried there at comment 13, and since then domU worked several days under high load without issues. Maybe make debian kernels not to use xen clocksource until the issue is fixed? -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#501383: This bug is not there with hypervisor/dom0 from lenny
Hello. At last we upgraded hypervisor and dom0 of our servers to lenny/amd64. Now our 32bit domUs correctly see more than 4G of memory. So this bug may be closed. signature.asc Description: This is a digitally signed message part.
Bug#511190: qemubuilder: builds hang because pseudo-fs are not mounted
> > > Trying to reproduce with 2.6.24-1-versatile doesn't cause that > > > error. What distribution version did you try using with which > > > kernel? > > > > > > I'd like to reproduce the problem before trying to fix it. > > > > I used 2.6.26-1-versatile > > Where did you get that image from? The official package has no > built-in filesystem support, so it would need an initrd. I've downloaded pre-built qemu armel system [1], and used it to build an armel kernel from lenny's linux-source-2.6.26. Starting with lenny's default config-2.6.26-1-versatile, I've changed from M to Y minimum things needed to work within qemu without initrd: - SCSI device support (under Device drivers : SCSI support) - SCSI disk support (under Device drivers : SCSI support) - SYM53C8XX Version 2 SCSI support (under Device drivers : SCSI support : SCSI low-level drivers) - SMC 91C9x/91c1xxx support (under Device drivers : Network drivers : Ethernet (10 or 100 Mbit) - Ext3 journalling file system support (under File systems) Resulting config and kernel image are at [2]. [1] http://people.debian.org/~aurel32/qemu/armel/ [2] http://yoush.homelinux.org:8079/nikita/armel-qemubuilder/ signature.asc Description: This is a digitally signed message part.
Bug#511190: qemubuilder: builds hang because pseudo-fs are not mounted
> At Thu, 8 Jan 2009 15:08:28 +0300, > > Nikita V. Youshchenko wrote: > > > > ... > > > > mount -n proc /proc -t proc > > > > mount -n sysfs /sys -t sysfs > > > > mount -n devpts /dev/pts -t devpts > > > > ... > > > > > > > > Please fix qemubuilder --create to add these lines automatically > > > > when creating a new environment, and also add some documentation > > > > to help people update already exiwting environments. > > > > > > in line 706 of Git tree: > > > > > >"mount -n /proc /proc -t proc\n" > > > > > > is already there for second-stage. > > > > > > Do you mean, sysfs and devpts mount is required in addition ? > > > > I don't know what exactly causes the hang. > > However, with mounted sysfs and devpts it does not hang, while without > > those it does. > > Trying to reproduce with 2.6.24-1-versatile doesn't cause that error. > What distribution version did you try using with which kernel? > > I'd like to reproduce the problem before trying to fix it. I used 2.6.26-1-versatile All details are at http://yoush.homelinux.org:8079/tech/setting-up-armel-qemubuilder signature.asc Description: This is a digitally signed message part.
Bug#511190: qemubuilder: builds hang because pseudo-fs are not mounted
> > ... > > mount -n proc /proc -t proc > > mount -n sysfs /sys -t sysfs > > mount -n devpts /dev/pts -t devpts > > ... > > > > Please fix qemubuilder --create to add these lines automatically when > > creating a new environment, and also add some documentation to help > > people update already exiwting environments. > > in line 706 of Git tree: > >"mount -n /proc /proc -t proc\n" > > is already there for second-stage. > > Do you mean, sysfs and devpts mount is required in addition ? I don't know what exactly causes the hang. However, with mounted sysfs and devpts it does not hang, while without those it does. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#511190: qemubuilder: builds hang because pseudo-fs are not mounted
Package: qemubuilder Version: 0.48 Severity: important I've tried to use qemubuilder to build armel packages on i386 host, and (after some struggle to get a working kernel image) found that any attempt to build a package hangs just after build-depends are installed. After some experiments I found that hang is caused by pseudo filesystems not being mounted inside qemu. The problem disappeared after I edited /pbuilder-run script inside qemu filesystem, such that now it contains ... mount -n proc /proc -t proc mount -n sysfs /sys -t sysfs mount -n devpts /dev/pts -t devpts ... Please fix qemubuilder --create to add these lines automatically when creating a new environment, and also add some documentation to help people update already exiwting environments. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash Versions of packages qemubuilder depends on: ii kvm 72+dfsg-4 Full virtualization on x86 hardwar ii libc6 2.7-16 GNU C Library: Shared libraries ii pbuilder 0.181 personal package builder for Debia hi qemu 0.9.1-10 fast processor emulator qemubuilder recommends no packages. qemubuilder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#511152: dpkg-dev: dpkg-buildpackage -v0 does not work
Package: dpkg-dev
Version: 1.14.23
Severity: normal
I've just found that if I pass '-v0' to dpkg-buildpackage (meaning 'include
changelog since version 0'), then -v0 parameter is not passed to
dpkg-genchanges.
This is caused by the line
if ($since) { push @change_opts, "-v$since" }
because if $since is 0, condition is false. Better to write
if (defined($since)) { push @change_opts, "-v$since" }
dpkg-genchanges also has exactly the same issue processing '-v0'.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg-dev depends on:
ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii bzip2 1.0.5-1 high-quality block-sorting file co
ii cpio2.9-13 GNU cpio -- a program to manage ar
ii dpkg1.14.23 Debian package management system
ii libtimedate-perl1.1600-9 Time and date functions for Perl
ii lzma4.43-14 Compression method of 7z format in
ii make3.81-5 The GNU version of the "make" util
ii patch 2.5.9-5 Apply a diff file to an original
ii perl [perl5]5.10.0-18Larry Wall's Practical Extraction
ii perl-modules5.10.0-18Core Perl modules
Versions of packages dpkg-dev recommends:
ii build-essential 11.4 Informational list of build-essent
ii gcc [c-compiler] 4:4.3.2-2 The GNU C compiler
ii gcc-4.1 [c-compiler] 4.1.2-23 The GNU C compiler
ii gcc-4.3 [c-compiler] 4.3.2-1The GNU C compiler
Versions of packages dpkg-dev suggests:
pn debian-keyring (no description available)
ii gnupg 1.4.9-3GNU privacy guard - a free PGP rep
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508697: [Pkg-e-devel] About updating python-evas package
> On Sat, Dec 20, 2008 at 7:51 PM, Nikita V. Youshchenko wrote: > > > I have heard that a newer release/snapshot of python-evas will work > > > with the new cython. The source is in > > > http://trac.enlightenment.org/e/browser/trunk/BINDINGS/python/python > > >-eva s and the commit commends indicate that it works better with > > > cython now. The setup.py says that the latest version is 0.3.1. > > > > Looks like that versions depends on eina library, that is not packaged > > for Debian yet. > > Although it is packaged, it still requires sponsorship and getting > through NEW, so I guess that will need a bit of time. > You can see http://git.debian.org/?p=pkg-e/libs/eina.git;a=summary if > you're interested. I may sponsor the upload if you wish. If you are interested, could you please comment on the following: - why you decided to put version into libdev package name? I.e. why it is libeina-0.0.1a-dev and not libeina-dev? Is there really any value in supporting installations of several versions of -dev package at a time? Btw you put headers into /usr/include/eina-0, and pkgconfig file is also called eina-0.pc. So you will have issues providing other libeina-0*-dev anyway... - it may be a good idea to put a short note on what eina is into Abatract field of doc-base file - that abstract is shown in tools like dhelp near unrelated things, so being a bit verbose there is better Nikita signature.asc Description: This is a digitally signed message part.
Bug#508697: About updating python-evas package
> I have heard that a newer release/snapshot of python-evas will work with > the new cython. The source is in > http://trac.enlightenment.org/e/browser/trunk/BINDINGS/python/python-eva >s and the commit commends indicate that it works better with cython now. > The setup.py says that the latest version is 0.3.1. Looks like that versions depends on eina library, that is not packaged for Debian yet. And that dependency appeared in svn near commit 37310 in late October. Cython fixes have been committed later. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508697: [Debian][Zhone] Fresh install gives SystemError
> I have heard that a newer release/snapshot of python-evas will work with > the new cython. The source is in > http://trac.enlightenment.org/e/browser/trunk/BINDINGS/python/python-evas > and the commit commends indicate that it works better with cython now. > The setup.py says that the latest version is 0.3.1. Albin, would you > mind adding this to your TODO? I’ll sponsor it :-) I wanted to look on this, and meanwile found an issue with git repo holding debian packaging for pyton-evas: nik...@blacky:~/openmoko/python-evas/package> git clone git://git.debian.org/pkg-e/proto/python-efl/python-evas.git Initialized empty Git repository in /home/nikita/openmoko/python-evas/package/python-evas/.git/ fatal: The remote end hung up unexpectedly nik...@blacky:~/openmoko/python-evas/package> git clone http://git.debian.org/git/pkg-e/proto/python-efl/python-evas.git Initialized empty Git repository in /home/nikita/openmoko/python-evas/package/python-evas/.git/ warning: remote HEAD refers to nonexistent ref, unable to checkout. Althowus repo may be browsed ok at http://git.debian.org/?p=pkg-e/proto/python-efl/python-evas.git signature.asc Description: This is a digitally signed message part.
Bug#501383: domU with 2.6.26 does not see more than 4G of RAM
> > Hypervisor version is 3.2.0-3~bpo4+2 (from backports.org). > > xen-utils-3.2-1 in dom0 is 3.2.0-3~bpo4+2. > > This version is not supported. At least upgrade the hypervisor to 3.2.1 > from Lenny. Thanks for your reply. I can't upgrade now, since system in question is running several domUs that are used in production. I will search for an upgrade window. Cristmas holidays is the most likely possibility. Nikita signature.asc Description: This is a digitally signed message part.
Bug#502007: libetpan: please package 0.57 for unstable
> Package: libetpan > Severity: wishlist > > Hi, > > Subject says it all :) > New claws-mail packages (3.6.1) require libetpan 0.57, so it would be > nice to be able to upload them to unstable. > > thanks in advance, I've just uploaded 0.57-1 to experimental (but not to unstable because of the freeze). signature.asc Description: This is a digitally signed message part.
Bug#501383: domU with 2.6.26 does not see more than 4G of RAM
Package: linux-image-2.6.26-1-xen-686 Version: 2.6.26-5 Severity: normal I've just tried to start kernel from linux-image-2.6.26-1-xen-686 instead of etch xen kernel in a domU. Since that domU runs an application server with >50 KDE session nortmally active, it required much RAM. Current setup is 15G. That works with etch 2.6.18-6-xen kernel. However, kernel from linux-image-2.6.26-1-xen-686 recognized only 4G. Hypervisor version is 3.2.0-3~bpo4+2 (from backports.org). xen-utils-3.2-1 in dom0 is 3.2.0-3~bpo4+2. Both hypervisor and domU are 32bit. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (640, 'stable'), (620, 'testing'), (600, 'unstable'), (580, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500458: git-buildpackage: can't import history of native package into empty git repo
> Nikita V. Youshchenko schrieb: > > Package: git-buildpackage > > Version: 0.4.39 > > Severity: normal > > > > I've tried to import previous releases of debian native package (no > > orig.tag.gz) into an empty git repo. > > No need to create a git repo first, just pass the dsc to git-import-dsc > and it will do all the rest (including repository creation). Does this > produce the expected result? Yes, this works. But anyway if repo already exists then operation fails, which is not good :) signature.asc Description: This is a digitally signed message part.
Bug#500458: git-buildpackage: can't import history of native package into empty git repo
Package: git-buildpackage Version: 0.4.39 Severity: normal I've tried to import previous releases of debian native package (no orig.tag.gz) into an empty git repo. It failed. [EMAIL PROTECTED]:~/git/gcc-doc-defaults> git-import-dsc ~/debian/pbuilder/result/gcc-doc-defaults_4.1.1.nf1.dsc Debian Native Package Version: 4.1.1.nf1 Epoch: 4 Repository has uncommitted changes, commit these first: # On branch master # # Initial commit # nothing to commit (create/copy files and use "git add" to track) Looks like a bug (although it may be workarounded by making dummy initial commit to the repository). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-xen-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash Versions of packages git-buildpackage depends on: ii devscripts 2.10.35 scripts to make the life of a Debi ii git-core 1:1.5.6.5-1 fast, scalable, distributed revisi ii python 2.5.2-2 An interactive high-level object-o ii python-dateutil 1.4-1 powerful extensions to the standar ii python-support 0.8.4 automated rebuilding support for P git-buildpackage recommends no packages. Versions of packages git-buildpackage suggests: pn git-load-dirs (no description available) pn pristine-tar (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498790: libetpan: mailmessage_get_bodystructure fails for cached IMAP
> When using the cached IMAP storage, the second call to > mailmessage_get_bodystructure returns a NULL mime structure. > > The problem is that the return variable is not being set, see > the attached patch for a fix. Thanks. Upstream confirmed that the patch is ok. How serious is the problem? Does it cause user applocation crashes or data loss? Should I try to push the fix into lenny? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475571: Faced the same issue as reported in #475571
> > I tried to import one of my packages, namely libetpan, into a git > > repo, and faced the exact situation described in #475571. After > > importing released package versions, new orig.tar.gz failed to merge > > because git attempted to apply old changes in upsteam branch to debian > > branch while those have already been there. > > My debian packaging does not touch anything outside of debian/ but > > still merge failed because (as far as I understand) while merging, > > patch from upstream version A to upstream version B failed to apply on > > master branch because it already contained change from version B to > > version C touching same file parts. > > Please provide a way to reproduce this. Please dowload http://yoush.homelinux.org:8079/nikita/libetpan-packages.tar.bz2 (11M) It contains several previously-released vesions of libetpan debian source packages in libetpan/old/, and a new upstream tarball in libetpan/new/ Then run: tar xjf libetpan-packages.tar.bz2 cd libetpan git-import-dscs old/*.dsc This will create a git repo in libetpan/ and import previous packages there. All upstream versions will reside in 'upstram' branch, all debian packages will reside on 'master' branch. Then run cd libetpan git-import-orig ../new/libetpan-0.56.tar.gz This will result into lots of conflicts. I was able to workaround this by replacing signle 'git-import-dscs old/*.dsc' command with the following procedule: - import first upstream tarball (0.45) using git-import-orig, - import debian packages created for that upstream version (0.45-1 .. 0.45-4) one-by-one using git-import-dsc, - importing next upstream tarball (0.46) using git-import-orig, - manually merge upstream branch into master branch, - import debian packages created for that upstream version (0.46-1 .. 0.46-4) one-by-one using git-import-dsc, - repeat last 3 steps for all next upstream versions. After this procedure, git-import-orig successfully imported the new upstream tarball, without any conflicts. I believe git-import-dscs should do something similar. WBR, Nikita P.S. Please notify me when I may delete libetpan-packages.tar.bz2 from the above URL. signature.asc Description: This is a digitally signed message part.
Bug#475571: Faced the same issue as reported in #475571
Hi I tried to import one of my packages, namely libetpan, into a git repo, and faced the exact situation described in #475571. After importing released package versions, new orig.tar.gz failed to merge because git attempted to apply old changes in upsteam branch to debian branch while those have already been there. My debian packaging does not touch anything outside of debian/ but still merge failed because (as far as I understand) while merging, patch from upstream version A to upstream version B failed to apply on master branch because it already contained change from version B to version C touching same file parts. After thinking a bit, I was going to suggest a solution similar to one by Matej Vela suggested in this bug, but not exactly the same. I suggest to automatically merge upstream into debian, but not after importing each dsc, but after importing of each new orig. Which is probably the same, but not 100% sure. Btw, please fix this issue - there are already at least two maintainers (Matej Vela and myself) who faced it :) Regards, Nikita signature.asc Description: This is a digitally signed message part.
Bug#483464: Same here
Same here with aptitude 0.4.11.8-1 and ru_RU.KOI8-R locale signature.asc Description: This is a digitally signed message part.
Bug#484339: gcc-doc can't be installed in Debian lenny 64 bits
tags 484339 +pending thanks > Package: gcc-doc > Version: ~ gcc-4.2-doc > > When I try to install gcc-doc apt tells me that gcc-doc package > depends of "gcc-4.2-doc (>= 4.2.3.nf1-1)" , but this package isn't > installable. This is because of dependency on gcc-doc-base, which is being moved from gcc-4.2-doc-non-dfsg to gcc-4.3-doc-non-dfsg source, and is temporary unavailable because of that. Stay tuned :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472848: This package should be removed
reassign 472848 ftp.debian.org retitle 472848 RM: libcompress-lzo-perl -- RoM: bindings to a library to be removed thanks Ok, reassigning this bug to ftp.debian.org In short, package libcompress-lzo-perl is a perl library for liblzo1; upstream looks dead for years, there is no interest in porting the bindings to liblzo2, and liblzo1 is being removed. signature.asc Description: This is a digitally signed message part.
Bug#466373: This package should be removed
reassign 466373 ftp.debian.org retitle 466373 RM: libcompress-lzo-perl: bindings to a library being removed thanks Ok, reassigning this bug to ftp.debian.org In short, package libcompress-lzo-perl is a perl library for liblzo1; upstream looks dead for years, there is no interest in porting the bindings to liblzo2, and liblzo1 is being removed. signature.asc Description: This is a digitally signed message part.
Bug#466373: This package should be removed
reassing 466373 ftp.debian.org retitle 466373 RM: libcompress-lzo-perl: bindings to a library being removed thanks Ok, reassigning this bug to ftp.debian.org In short, package libcompress-lzo-perl is a perl library for liblzo1; upstream looks dead for years, there is no interest in porting the bindings to liblzo2, and liblzo1 is being removed. signature.asc Description: This is a digitally signed message part.
Bug#467166: This is not gcc-doc-defaults bug
[forwarding this to bug log - it is missing there] > hmm, I do see a gcc-4.2-doc-non-dfsg source package, but not a > gcc-4.3-doc-non-dfsg package, and at least on powerpc gcc-doc is not > available. IMO this report doesn't belong to gcc. Yes, I did not upload 4.3 version yet, packages are more or less ready but still untested, real life suxx. However, I think that bug report is not about 4.3 documentation not available. Reporter claims that 'man gcc' shows nothing. However, 'man gcc' will show gcc manual page (4.2 one) if gcc-doc is installed. I believe submitter's issue is that he is unaware of separate gcc-doc package. Nikita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#467166: This is not gcc-doc-defaults bug
reassign 467166 gcc thanks Matthias, This is not a bug in gcc-doc-defaults package. If gcc-doc is installed, 'man gcc' works as expected. The issue is in 'gcc' package, that it does not provide the man page (for those ugly licensing reasons), and does not give any hints to user on how to find the documentation. Not sure if it should be fixed or not. We may add obvious diversion-based trick (packages from main add stub man pages that reference the non-free packages, package from non-free divert those with real man pages) if you think it is appropriate. Nikita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473569: DBusViewer tries to run /usr/lib/jvm/java-gcj/bin/java, but does not depend on package providing it
> On Mon Mar 31 16:06, Nikita V. Youshchenko wrote: > > Package: dbus-java-bin > > Version: 2.4-1 > > Severity: serious > > > > After running 'apt-get install dbus-java-bin', when I try to start > > DBusViewer, I get > > /usr/bin/DBusViewer: line 10: /usr/lib/jvm/java-gcj/bin/java: No such > > file or directory > > /usr/bin/DBusViewer: line 10: exec: /usr/lib/jvm/java-gcj/bin/java: > > cannot execute: No such file or directory > > Hmm, yes, I appear to have introduced a regression. The dbus-java stuff > builds with gcj, but doesn't run with it. Unfortunately, the build VM > flag also sets the runtime flag, so it's even worse. If you did install > java-gcj-compat, it would fail to run! > > Recent gcj uploads may have fixed it, so will test and either put the > correct line in the wrapper script, or depend on the correct VM. Or, > what I should do, is sort the wrapper script to run with whatever VM is > installed, once that actually works. > > I'll test and upload a fix shortly, thanks for the heads up. For the > moment a fix is to edit the wrapper script to say JAVA=/usr/bin/java at > the top. You may also need to add dependency on libdbus-java - running DBusViewer would fail if that library is not installed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473569: DBusViewer tries to run /usr/lib/jvm/java-gcj/bin/java, but does not depend on package providing it
Package: dbus-java-bin Version: 2.4-1 Severity: serious After running 'apt-get install dbus-java-bin', when I try to start DBusViewer, I get /usr/bin/DBusViewer: line 10: /usr/lib/jvm/java-gcj/bin/java: No such file or directory /usr/bin/DBusViewer: line 10: exec: /usr/lib/jvm/java-gcj/bin/java: cannot execute: No such file or directory I have a java VM installed: [EMAIL PROTECTED]:~> LANG=C apt-cache policy sun-java5-jre sun-java5-jre: Installed: 1.5.0-14-1etch1 Candidate: 1.5.0-14-1etch1 Version table: 1.5.0-15-1 0 600 file: unstable/non-free Packages 1.5.0-14-3 0 620 file: testing/non-free Packages *** 1.5.0-14-1etch1 0 640 file: etch/non-free Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~> which java /usr/bin/java [EMAIL PROTECTED]:~> ls -l /usr/bin/java lrwxrwxrwx 1 root root 22 2007-06-25 17:14 /usr/bin/java -> /etc/alternatives/java* [EMAIL PROTECTED]:~> ls -l /etc/alternatives/java lrwxrwxrwx 1 root root 40 2008-02-18 08:33 /etc/alternatives/java -> /usr/lib/jvm/java-1.5.0-sun/jre/bin/java* -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (640, 'stable'), (620, 'testing'), (600, 'unstable'), (580, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages dbus-java-bin depends on: ii sun-java5-jre1.5.0-14-1etch1 Sun Java(TM) Runtime Environment ( dbus-java-bin recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472848: switch to liblzo2
> Package: libcompress-lzo-perl > Version: 1.08-3 > Severity: normal > > Please replace your use of liblzo by the newer version liblzo2, so we > can get rid of the old library. You might need to talk to upstream or > patch some of the build infrastructure. Since libcompress-lzo-perl package has no reverse depends in debian, and has very low popularity, and upstream never ported it to lzo2, it could be a better idea to remove this package together with liblzo1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#467297: Please make your package more backport-friendly
> I found 2 problems when backporting libetpan: > 1st: if build-depends and depends on libcurl4-gnutls-dev but there is > only libcurl3-gnutls-dev in Etch. This could not be fixed as simple as you propose, because of dependency for libetpan-dev package. It should be not libcurl4-gnutls-dev | libcurl3-gnutls-dev, but exactly one of those two, used by package build. Because of this issue, I won't add "| libcurl3-gnutls-dev" alternative for now. > 2nd problem is that your shlibs version is 0.52-1, but should be 0.52 This one is "fixed" in 0.54 Btw, backporting of never libetpan 0.54 will be even more "difficult" because of introduced support for 'symbols' file that was not there in etch times, and because of using libdb-dev instead of libdb4.4-dev (which has exactly same issue as libcurl4 regarding to adding alternative). signature.asc Description: This is a digitally signed message part.
Bug#464953: ptpatch2008.c does not work
> but seems to be another solution which apparently compiles to a kernel > module which will catch and report attempts to (ab)use vmsplice at > http://home.powertech.no/oystein/ptpatch2008/ptpatch2008.c I've just tried to compile this module. It successfully insmod'ed: Feb 11 12:54:29 zigzag kernel: ptpatch2008: init, (c) 2008 [EMAIL PROTECTED] Feb 11 12:54:29 zigzag kernel: ptpatch2008: syscalls c02ea3c0 Feb 11 12:54:29 zigzag kernel: hooked sys_vmsplice However exploit code from the top of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464953 still works: [EMAIL PROTECTED]:~/adm/hotfix> ./exploit --- Linux vmsplice Local Root Exploit By qaaz --- [+] mmap: 0x0 .. 0x1000 [+] page: 0x0 [+] page: 0x20 [+] mmap: 0x4000 .. 0x5000 [+] page: 0x4000 [+] page: 0x4020 [+] mmap: 0x1000 .. 0x2000 [+] page: 0x1000 [+] mmap: 0xb7d97000 .. 0xb7dc9000 [+] root [EMAIL PROTECTED]:~/adm/hotfix> whoami root -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
