Bug#704115: whois: please update whois server for *.id TLD
Package: whois Version: 5.0.20 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, I can use whois for id LTD domain, seems like they change whois server from whois.pandi.or.id to whois.idnic.net.id. debian:~$ whois udienz.web.id Not found: -V Md5.0 udienz.web.id debian:~$ whois -h whois.idnic.net.id udienz.web.id Whois Results for udienz.web.id. Domain Name: udienz.web.id Creation Date: 2011-06-06T00:00:00.0Z Last Updated On: 2013-03-19T08:19:43.0Z Expiration Date: 2015-06-07T00:00:00.0Z Sponsoring Registrar: Rahajasa Media Internet Status: serverTransferProhibited Registrant ID: mahyu2 Admin Contact ID: mahyu2 Billing Contact ID: mahyu2 Tech Contact ID: mahyu2 Name Server: ns1.radsby.net Name Server: ns2.radsby.net Name Server: ns.sby.rad.net.id Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided for informational purposes only without any accuracy guarantee. Please update whois to use whois.idnic.net.id - -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages whois depends on: ii libc6 2.13-38 ii libidn11 1.25-2 whois recommends no packages. whois suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRU+JqAAoJELmHbrCQs2xbRDIP/0B8xAoc52L6DwQq1Kg7gKG6 90SxRGN/AA3ZIO1X8Zjbmrny4dO1Zl2QoRG8CFqyIcZOXS97enb8iq+r0McwcyFm u/pFAhxKxdTmdThDaOzk6cmzZX9LmBA/hioSIIkj4o//1xvd6fw+Bi06KQlD9emz Ns3fZm7L0aYBcAA/5guqxDO/CY5kKWTlTdfQnRjJWNjAN3mPfwOJ8BklBqdRtc47 hYzDxgnexZVsjqc7VZcxSElfRAGYg06imz3tvxChi6NCXMpmQuD9VdEI71/Hws/T l2bh/oW8i7S5BrfSPtfzsjBzjuSeFG2U+ELYmoXA8EEF1IGYYF3yLg5DBC/pOox/ GwxBr2S5Y8KUL18t6jjrN/T67p5zppIEKT6f9Ql1MNvqwkFfLgWoqLbst38MQSRH k0kUarJTSVkZ3L5YjluL7BNMqW5qa3WUHfuVTaRfyxmMP60S3ZcVERj0ZhS7lbFb zNxFYrRPTzq5qCB50w5u+dx+vZ6PuO4g4ncl+WYEXbwx52YtmBs0OK1//FWPR5FY WqDwYKmP543ZpxtlChbHdRFSKY+Nt037x83leDLwKTT+WYNrpy82pEy3tmarNGf4 hcEI6YJCHHLgPDpb83wqHHVkaAdF+e9M3IcpNzqdqnVFWsrQJzz0AdLxkUfOEaaN aJhIQJ4WVlsjYf2nGBZR =TDZd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703444: Fixed by ecere-sdk 0.44.06-1
This problem has been resolved in version 0.44.06.1. Uploaded to mentors: http://mentors.debian.net/package/ecere-sdk Regards, Jerome -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704116: kernel-package: [make-kpkg] manpage not uptodate
Package: kernel-package Version: 12.036+nmu3 Severity: minor I am using Kubuntu 12.10 32bit in a german version. The manpage (german) of make-kpkg is from 2002 and have one wrong and some incomplete informations. I am not sure but I think the english version of the manpage has the same state. 1. wrong information The man-page tell that there is a need to run make-kpkg as root (what is extrem risky!), with fakeroot or to tell him by parameter how to become (fakeroot) root. I tested it myself. From userside there is no need to tell make-kpkg how to become root or to run it as (fake)root. Because make-kpkg handle it for itself. I checked it. All files in my created deb are with root-rights without running make-kpkg as (fake)root. And I was able to install the deb without any errors. Just cancle this information. 2. missing and incomplite configuration Two usual usecases for make-kpkg: a) The configuration of the kernel is completely missing. b) The configuration is from an older kernel-version and some new-options there are unset. So the config is incomplete. How does make-kpkg behave in such situations? The man-page-described behaviour is unclear and maybe wrong. (I need more time to test it myself.) The author or code-maintainer should be contacted to clearing this questions and bring the man-page to a real state. Because of missunderstandig the communication ways I opened a similary bug- report on the Ubuntu-BugTracking-System lunchpad. https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly0.10/+bug/1160735 -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal-proposed'), (500, 'quantal'), (100, 'quantal-backports') Architecture: i386 (i686) Kernel: Linux 3.5.0-27-generic (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kernel-package depends on: ii binutils 2.22.90.20120924-0ubuntu2 ii build-essential11.5ubuntu3 ii debianutils4.3.4 ii file 5.11-2 ii gettext0.18.1.1-9ubuntu1 ii make 3.81-8.2ubuntu2 ii module-init-tools 3.16-1ubuntu6 ii po-debconf 1.0.16+nmu2ubuntu1 ii util-linux 2.20.1-5.1ubuntu2 Versions of packages kernel-package recommends: ii cpio 2.11-8ubuntu3 Versions of packages kernel-package suggests: pn btrfs-tools none ii bzip2 1.0.6-4 pn docbook-utils none ii e2fsprogs 1.42.5-1ubuntu2 pn grub | grub2none ii initramfs-tools [linux-initramfs-tool] 0.103ubuntu0.2 pn jfsutilsnone ii libncurses5-dev [libncurses-dev]5.9-10ubuntu1 ii linux-source3.5.0.27.43 ii linux-source-3.5.0 [linux-source] 3.5.0-27.46 pn mcelog none pn oprofilenone ii pcmciautils 018-8 ii ppp 2.4.5-5ubuntu2 ii procps 1:3.3.3-2ubuntu3 pn quota none pn reiserfsprogs none pn squashfs-tools none ii udev175-0ubuntu13 pn xfsprogsnone ii xmlto 0.0.25-2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704115: tagging
tags 704115 patch Attached patch to fix this bug -- Mahyuddin Susanto tld-id.diff Description: Binary data
Bug#462049: tpb: seems to consume lots of memory and CPU
Control: severity -1 minor Hi Giridhar, TPB is one of those processes in my 'top' that seems to consume very large amounts of memory and considerable CPU. IMO, tpb doesn't consume large memory and CPU tpb used 1.6 MB and 0.3 % of CPU top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22997 root 20 0 46636 1624 1188 S 0.3 0.1 0:08.96 tpb Powertop: Usage Events/sCategory Description 2.6 ms/s 4.9Process/usr/bin/tpb -d Regrads -- Prach Pongpanich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704087: unattended-upgrades: Crashes on codename matching
On Wed, Mar 27, 2013 at 11:02:38AM -0700, Nikolaus Rath wrote:
Package: unattended-upgrades
Version: 0.79.5
Severity: normal
Thanks for your bugreport.
Dear Maintainer,
Recently, unattended-upgrades has started crashing with:
Traceback (most recent call last):
File /usr/bin/unattended-upgrade, line 1011, in module
main(options)
File /usr/bin/unattended-upgrade, line 793, in main
allowed_origins=allowed_origins)
File /usr/bin/unattended-upgrade, line 75, in __init__
self.adjust_candidate_versions()
File /usr/bin/unattended-upgrade, line 92, in adjust_candidate_versions
if is_allowed_origin(pkg.candidate, self.allowed_origins):
File /usr/bin/unattended-upgrade, line 364, in is_allowed_origin
if match_whitelist_string(allowed, origin):
File /usr/bin/unattended-upgrade, line 272, in match_whitelist_string
what, token))
__main__.UnknownMatcherError: Unknown whitelist entry for macher 'n'
(token 'n=wheezy')
I haven't touched the configuration at all, so I'm pretty sure
this is a regression.
This might be related to #703401, where codename matching also results
in a crash (but with a different exception).
There are two issues here:
- unattended-upgrades does not support codename based matching (n=)
because python-apt does not export this (fixed in experimental)
- unattended-upgrades silently ignored codenames it did not know
about which makes a matcher like o=Debian,n=wheezy to o=Debian
internally
The new version now complains on unknown matchers and the combination
with the old config file where n=wheezy was part of the example config
is now casing this problem.
I wonder what I can do to help avoiding this confusion? Instead of a
error, just log a warning maybe? This could lead to overly broad
matching.
Cheers,
Michael
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages unattended-upgrades depends on:
ii apt0.9.7.8
ii apt-utils 0.9.7.8
ii debconf [debconf-2.0] 1.5.49
ii lsb-base 4.1+Debian8
ii lsb-release4.1+Debian8
ii python 2.7.3-4
ii python-apt 0.8.8.2
ii ucf3.0025+nmu3
ii xz-utils 5.1.1alpha+20120614-2
unattended-upgrades recommends no packages.
Versions of packages unattended-upgrades suggests:
ii bsd-mailx 8.1.2-0.2006cvs-1
ii exim4-daemon-light [mail-transport-agent] 4.80-7
-- Configuration Files:
/etc/apt/apt.conf.d/50unattended-upgrades changed:
// Automatically upgrade packages from these origin patterns
Unattended-Upgrade::Origins-Pattern {
// Codename based matching:
// This will follow the migration of a release through different
// archives (e.g. from testing to stable and later oldstable).
// o=Debian,n=squeeze;
// o=Debian,n=squeeze-updates;
// o=Debian,n=squeeze-proposed-updates;
// o=Debian,n=squeeze,l=Debian-Security;
// Archive or Suite based matching:
// Note that this will silently match a different release after
// migration to the specified archive (e.g. testing becomes the
// new stable).
// o=Debian,a=stable;
// o=Debian,a=stable-updates;
// o=Debian,a=proposed-updates;
// origin=Debian,archive=stable,label=Debian-Security;
o=${distro_id},n=${distro_codename};
o=${distro_id},n=${distro_codename}-updates;
o=${distro_id},n=${distro_codename},l=Debian-Security;
};
// List of packages to not update
Unattended-Upgrade::Package-Blacklist {
//vim;
//libc6;
//libc6-dev;
//libc6-i686;
};
// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run // dpkg --force-confold
--configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg false;
// Split the upgrade into the smallest possible chunks so that
// they can be interrupted with SIGUSR1. This makes the upgrade
// a bit slower but it has the benefit that shutdown while a upgrade
// is running is possible (with a small delay)
//Unattended-Upgrade::MinimalSteps true;
// Install all unattended-upgrades when the machine is shuting down
// instead of doing it in the background while the machine is running
// This will (obviously) make shutdown slower
//Unattended-Upgrade::InstallOnShutdown true;
// Send email to this address for problems or packages upgrades
// If empty or unset then no email is sent, make sure that you
// have a working mail setup on your system. A package
Bug#703431: Annoying GPG error message
Hi, On Tue, 19 Mar 2013, Steve McIntyre wrote: On Tue, Mar 19, 2013 at 04:41:08PM +0200, Robert Spencer wrote: There's a long standing error that I've seen even in on-line official Debian CD build logs. W: GPG error: file: squeeze Release: No keyring installed in /home/idms/tmp/apt/squeeze-amd64/apt/trusted.gpg.d/. Attached please find a patch file that fixes the error. Cool, looks good. I've applied this in svn straight away, and it'll make it into the next upload shortly. Robert, would it be possible to add some parameters to use something else than debian-archive-keyring ? debian-cd ought to be usable to build CD images of Debian derivatives and they don't reuse debian-archive-keyring, instead they provide their own keyring package. Thanks in advance! -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704114: asterisk: asterisk security advisories: AST-2013-001 / AST-2013-002 / AST-2013-003
On Thu, Mar 28, 2013 at 06:23:32AM +0100, Salvatore Bonaccorso wrote: Package: asterisk Severity: grave Tags: security patch upstream Hi, the following vulnerabilities were published for asterisk. CVE-2013-2685[0]: Buffer Overflow Exploit Through SIP SDP Header CVE-2013-2686[1]: Denial of Service in HTTP server CVE-2013-2264[2]: Username disclosure in SIP channel driver For CVE-2013-2685 the tracker[3] mentions only 1.11.x. Could you doublecheck that squeeze, testing and wheezy are not affected? According to the Upstream advisories, both are in effect for 1.8 . Didn't yet check backporting it (to our 1.8 in Testing/Unstable) and to 1.6.2 in Stable. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] http://security-tracker.debian.org/tracker/CVE-2013-2685 http://downloads.asterisk.org/pub/security/AST-2013-001.html [1] http://security-tracker.debian.org/tracker/CVE-2013-2686 http://downloads.asterisk.org/pub/security/AST-2013-002.html [2] http://security-tracker.debian.org/tracker/CVE-2013-2264 http://downloads.asterisk.org/pub/security/AST-2013-003.html [3] https://issues.asterisk.org/jira/browse/ASTERISK-20901 Please adjust the affected versions in the BTS as needed. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: external cam works, builtin fails
Hi, indeed, a USB attached cam works fine here whereas the builtin laptop camera fails completely: I have exactly the symptoms described here -- no cheese at all, process hanging. If I run cheese with the USB cam pluged in and switch to the builtin cam within the cheese preferences menu, the application locks up. Best regards, Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704117: Please upload 2.7 to experimental
Package: tortoisehg Version: 2.6-1 Mercurial 2.5+, recently uploaded to unstable, requires TortoiseHg 2.7 or newer. Please upload TortoiseHg 2.7.1 or newer to experimental. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.
On 28/03/2013 06:31, peter green wrote: Ok I just had a discussion with adam conrad about this on IRC. According to him clang currently does assume that armv7 means coretex a8 and that coretex a8 mean full vfpv3 and neon. There is a patch in ubuntu precise/quantal to fix this (26-armv7-not-neon.patch) but it's a pretty big patch and is self-described as a hideous hack. I doubt the release team would accept such a patch at this stage. Therefore it seems the only reasonable thing to do is to select armv6 for clang on armhf in wheezy. He also alerted me to a patch that disables altivec by default on powerpc since not all powerpc hardware debian supports has altivec. I intend to include this in the proposed NMU, a copy of it is attached. Since I now have confirmation on what clang does i'll prepare the NMU diff in a day or two. No need to do a NMU here. I can upload it right now. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704111: [cfe-dev] Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.
Hi Peter,
1: What does the coretex-a8 CPU setting imply for clang/llvm? in
particular does it imply neon and the extra vfp registers?
At the LLVM level, the options that have to be enabled are NEON and
restrict to 16 registers. Looking at (Clang's) lib/Basic/Targets.cpp
from 3.0 (and current). Cortex-A8 defaults to NEON enabled and using
all registers.
The option you ideally want to be using is -mfpu. In current Clang,
this can have the value vfpv3-d16, which disables NEON and restricts
to 16 registers, which sounds like exactly what you want.
Unfortunately this doesn't seem to exist in 3.0.
Backporting it would be a relatively simple feat. The following block
in addFPUArgs in lib/Driver/Tools.cpp implements it:
} else if (FPU == vfp3-d16 || FPU == vfpv3-d16) {
CmdArgs.push_back(-target-feature);
CmdArgs.push_back(+vfp3);
CmdArgs.push_back(-target-feature);
CmdArgs.push_back(+d16);
CmdArgs.push_back(-target-feature);
CmdArgs.push_back(-neon);
}
The one risk I see is that trunk LLVM contains two references to
hasD16, but 3.0 only refers to it once. The common reference is the
obvious place to implement the limit in LLVM. The second could mean
extra functionality was added which relies on the extra registers, or
it could mean there was a latent bug in 3.0 (around lowering
ConstantFPs). I can't really tell without more detailed investigation.
Hope this helps.
Tim.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691923: New upstream (1.8.2)
Hi, since 1.8.2 is now available, and 1.8.2-rc3 is in experimental, can this bug be closed and perhaps 1.8.2 final be uploaded? Regards, Vedran -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704101: devscripts: rc-alert doesn't know about testing-proposed-updates
block 704101 by 544726 kthxbye Hi, James McCoy wrote: On Wed, Mar 27, 2013 at 11:10:45PM +0100, Axel Beckert wrote: rc-alert doesn't seem to be able to take testing-proposed-updates into account: $ rc-alert -d TU -o and --exclude-tags I includes #697676 and possibly others which are currently fixed in t-p-u, but not in testing. BTW, the same can be observed with #680824, too. Neither does the site[0] that we extract the data from, [...] [0]: http://bugs.debian.org/release-critical/other/all.html Indeed. or the original bug report for that matter The bug report knows about it (Fixed in version lvm2/2.02.95-7), but doesn't seem to know about the corresponding package. (note that there are no fixed versions in the bug graph). ... but not the version graph, yes. Not knowning about $dist-proposed-updates for version tracking looks like a bug in the BTS. And already reported: http://bugs.debian.org/544726 -- Cc'ing that bug. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704118: kamailio version 4.0 is out; it is a significant improvement.
Package: kamailio Version: 3.3.0-1 Severity: normal Please update sid to kamailio 4.0 sooner rather than later. The support for websockets and the completion of the merger with ser significantly improve kamailio’s value and capabilities. According to http://packages.debian.org/search?keywords=kamailio it is only in sid, so the wheezy freeze should not have to affect the schedule for updating. Please see http://www.kamailio.org/w/2013/03/kamailio-v4-0-0-released/ for the release announcement. Upstream also announced some packages (http://www.kamailio.org/w/2013/03/packages-for-v4-0-0/) which might be helpful for writing deb’s. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Versions of packages kamailio depends on: ii adduser3.113+nmu3 ii libc6 2.13-38 ii libncurses55.9-10 ii libpcre3 1:8.31-2 ii libreadline6 6.2+dfsg-0.1 ii libtinfo5 5.9-10 ii multiarch-support 2.13-38 ii python 2.7.3-4 kamailio recommends no packages. Versions of packages kamailio suggests: pn kamailio-berkeley-modules none ii kamailio-carrierroute-modules 3.3.0-1 pn kamailio-cpl-modules none pn kamailio-ldap-modules none pn kamailio-lua-modules none pn kamailio-mono-modules none pn kamailio-mysql-modules none ii kamailio-perl-modules 3.3.0-1 ii kamailio-postgres-modules 3.3.0-1 ii kamailio-presence-modules 3.3.0-1 pn kamailio-python-modulesnone pn kamailio-radius-modulesnone pn kamailio-redis-modules none pn kamailio-snmpstats-modules none pn kamailio-unixodbc-modules none ii kamailio-xml-modules 3.3.0-1 ii kamailio-xmpp-modules 3.3.0-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704111: [cfe-dev] Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.
2: If noone can provide an answer to the above question then taking into the account how late we are in the freeze should we play it safe and specify a lower (armv6) CPU version to make sure that neon and the extra vfp registers don't get accidently used. I personally think that the answer is yes but I'm open to arguments. Given that 3.0 is pretty old (~1.5 year) LLVM version you can do with debian-provided version whatever you want. I doubt anyone cares here now about that old version. ARM (especially hardware FP) support is known to contain many problems in that old version. The recent LLVM 3.2 release provides proper hardware FP support out of the box. cortex-a8 indeed by default implies full vfp and NEON. This seems to be reasonable default for ARMv7. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704119: RM: kolab-webadmin/2.2.3-20091217-4
Package: release.debian.org User: release.debian@packages.debian.org Usertags: rm Severity: normal kolab-webadmin is obsolete, and not usefull without the kolabd package in testing. Regards Mathieu Parent -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning
On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: could anyone who is seeing the issue with Cheese freezing try to disconnect their webcam In my case I don't think so- it's built into the frame of my laptop screen. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703581: unblock: e2fsprogs/1.42.5-1.1
Jonathan Wiltshire j...@debian.org (24/03/2013): Indeed; tagging and CCing accordingly. Should be safe as far as the udeb is concerned, please go ahead. Mraw, KiBi. signature.asc Description: Digital signature
Bug#702167: unblock: lvm2/2.02.95-7
Julien Cristau jcris...@debian.org (24/03/2013): Approved, but will need an udeb ack. Still not touching the udeb part AFAICT; ack. Mraw, KiBi. signature.asc Description: Digital signature
Bug#696727: some more device informations
Hi again, I collected a bit more information about the device: andi@fuzi:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000 = works fine Bus 002 Device 002: ID 5986:01a6 Acer, Inc Lenovo Integrated Webcam = fails Attached is the detailed output of lsusb -v for the cams. I had the integrated cam working some time ago, but no idea when it failed the first time, as I do not need it usually. Kernel issue? Best regards, Andi Bus 003 Device 004: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x045e Microsoft Corp. idProduct 0x00f7 LifeCam VX-1000 bcdDevice1.01 iManufacturer 0 iProduct1 USB camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 382 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 100 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x0080 1x 128 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 100 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 2 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor:
Bug#703146: debootstrap patch disabling InRelease handling
Hi Julien, FYI, I have tested the patch disabling InRelease handling as pushed to debootstrap's git in two situations: * standard package; debootstrap a wheezy chroot: OK * d-i environment (built mini.iso, installed debootstrap-udeb in it): OK Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704120: ltsp-server: serveral ltsp clients freezed at the same instant
Package: ltsp-server Version: 5.4.2-5 Severity: important Dear all, Yesterday morning I had a severe problem with some ltsp-clients: All clients at a specific ltsp-server (the machine I was writing this bug report on) froze at the same instant. Only mouse was moving in gnome3, nothing else worked, not even text-console at ctrl-alt-F1. We had to hard-reset the clients, causing data loss for some users. My guess is that package ltsp-server is the cause since it happened to several clients on the same server, but maybe I am wrong. Please feel free to reassign to another package. Regarding logs, unfortunately I did not find any relevant information on the servers var/log/syslog nor any other logfile that could give hints about this problem. The logfiles at the clients are gone, due to the complete freeze I could not copy them anywhere before resetting. Please give information on whether I can provide further information to narrow down this bug. Best, Jürgen PS: Sorry if this is sent twice, I first sent this message yesterday using sendmail but this did not seem to work so I now try again using Thunderbird. -- Package-specific info: chroot information: /opt/ltsp/wheezy -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ltsp-server depends on: ii debconf [debconf-2.0] 1.5.49 ii debconf-utils 1.5.49 ii debootstrap1.0.44 ii gettext-base 0.18.1.1-9 ii iproute20120521-3+b3 ii lsb-release4.1+Debian8 ii openssh-client 1:6.0p1-4 ii python 2.7.3-4 ii tcpd 7.6.q-24 ii update-inetd 4.43 Versions of packages ltsp-server recommends: ii nbd-server1:3.2-2 ii nfs-kernel-server 1:1.2.6-3 ii openbsd-inetd [inet-superserver] 0.20091229-2 ii openssh-server1:6.0p1-4 ii squashfs-tools1:4.2-5 ii tftpd-hpa 5.2-4 Versions of packages ltsp-server suggests: pn audioossnone ii gnome-session [x-session-manager] 3.4.2.1-3 ii gnome-session-fallback [x-session-manager] 3.4.2.1-3 ii isc-dhcp-server [dhcp3-server] 4.2.2.dfsg.1-5+deb70u3 ii ldm-server 2:2.2.11-2 ii libasound2-plugins 1.0.25-2 ii ltsp-docs 1.1-1 ii ltspfs 1.1-2 ii metacity [x-window-manager] 1:2.34.3-4 ii pulseaudio 2.0-6 pn qemu-user-staticnone pn sdm none ii x11-utils 7.7~1 ii xauth 1:1.0.7-1 -- debconf information: ltsp-server/build_client: false signature.asc Description: OpenPGP digital signature
Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.
Sylvestre Ledru wrote:
No need to do a NMU here.
Ok I've attached a diff. Note: i'm currently running a test build of
this version i'll follow up later with results from that test to confirm
things are ok (I don't see why they wouldn't be)
diff -urN clang-3.0/debian/changelog clang-3.0.new/debian/changelog
--- clang-3.0/debian/changelog 2013-02-10 14:47:29.0 +
+++ clang-3.0.new/debian/changelog 2013-03-28 09:06:53.0 +
@@ -1,3 +1,15 @@
+clang (1:3.0-6.2) unstable; urgency=low
+
+ * 29-set-default-cpu-for-armhf.diff increase default cpu for armhf builds.
+Previous absurdly low default did not work correctly with
+-mfloat-abi=hard leading to broken code.
++ Use armv6 as new default because in clang 3.0 armv7 implies features that
+ we don't require in debian armhf (extra fpu registers and neon)
+ * 30-powerpc-no-altivec.patch disable altivec by default on powerpc because
+debian powerpc does not require altivec (patch cherry picked from ubuntu)
+
+ -- Peter Michael Green plugw...@debian.org Thu, 28 Mar 2013 09:02:01 +
+
clang (1:3.0-6.1) unstable; urgency=low
* Non-maintainer upload.
diff -urN clang-3.0/debian/patches/29-set-default-cpu-for-armhf.diff clang-3.0.new/debian/patches/29-set-default-cpu-for-armhf.diff
--- clang-3.0/debian/patches/29-set-default-cpu-for-armhf.diff 1970-01-01 00:00:00.0 +
+++ clang-3.0.new/debian/patches/29-set-default-cpu-for-armhf.diff 2013-03-28 08:47:26.0 +
@@ -0,0 +1,39 @@
+Description: Fix CPU type default for armhf
+ Without this patch clang defaults to a CPU type of arm7tdmi which
+ does not work correctly with -mfloat-abi=hard leading to broken
+ code.
+
+ Use armv6 because as far as I can tell clang 3.0 does not properly
+ support an armv7 setting without neon or the extra floating point
+ registers. It may be possible to patch it to add support but I feel
+ such a Patch would likely be considered unacceptable at this stage in
+ The release process.
+Author: Peter Michael Green plugw...@debian.org
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: vendor|upstream|other, url of original patch
+Bug: url in upstream bugtracker
+Bug-Debian: http://bugs.debian.org/bugnumber
+Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
+Forwarded: no|not-needed|url proving that it has been forwarded
+Reviewed-By: name and email of someone who approved the patch
+Last-Update: -MM-DD
+
+Index: clang-3.0/tools/clang/lib/Driver/Tools.cpp
+===
+--- clang-3.0.orig/tools/clang/lib/Driver/Tools.cpp 2013-03-27 19:50:18.0 +
clang-3.0/tools/clang/lib/Driver/Tools.cpp 2013-03-27 19:53:28.0 +
+@@ -442,6 +442,9 @@
+ if (Arg *A = Args.getLastArg(options::OPT_march_EQ)) {
+ // Otherwise, if we have -march= choose the base CPU for that arch.
+ MArch = A-getValue(Args);
++ } else if (Triple.getEnvironment() == llvm::Triple::GNUEABIHF) {
++// Use armv6 for armhf (raspbian version of patch)
++MArch = armv6;
+ } else {
+ // Otherwise, use the Arch from the triple.
+ MArch = Triple.getArchName();
diff -urN clang-3.0/debian/patches/30-powerpc-no-altivec.patch clang-3.0.new/debian/patches/30-powerpc-no-altivec.patch
--- clang-3.0/debian/patches/30-powerpc-no-altivec.patch 1970-01-01 00:00:00.0 +
+++ clang-3.0.new/debian/patches/30-powerpc-no-altivec.patch 2013-03-28 09:00:48.0 +
@@ -0,0 +1,20 @@
+Description: Make sure PowerPC doesn't default to altivec on
+Author: Adam Conrad adcon...@ubuntu.com
+Forwarded: no
+Reviewed-By: Colin Watson cjwat...@ubuntu.com
+Last-Update: 2012-04-24
+
+Index: b/tools/clang/lib/Lex/Makefile
+===
+--- a/tools/clang/lib/Lex/Makefile
b/tools/clang/lib/Lex/Makefile
+@@ -16,9 +16,5 @@
+
+ LIBRARYNAME := clangLex
+
+-ifeq ($(ARCH),PowerPC)
+-CXX.Flags += -maltivec
+-endif
+-
+ include $(CLANG_LEVEL)/Makefile
+
diff -urN clang-3.0/debian/patches/series clang-3.0.new/debian/patches/series
--- clang-3.0/debian/patches/series 2013-02-06 12:53:12.0 +
+++ clang-3.0.new/debian/patches/series 2013-03-28 09:01:26.0 +
@@ -9,3 +9,5 @@
26-set-correct-float-abi.diff
27-dynamic-linker.diff
28-gcc-4.7.diff
+29-set-default-cpu-for-armhf.diff
+30-powerpc-no-altivec.patch
Bug#704121: Debian cpio info pages totally gone
X-debbugs-Cc: bug-c...@gnu.org Package: cpio Version: 2.11+dfsg-0.1 The Debian cpio info pages are totally gone. So one turns to http://www.gnu.org/software/cpio/manual/cpio.html to find out what cpio -o returning exit code $?=2 means, but that isn't there either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704122: ndiswrapper-dkms: Fails to build module because of missing BUILT_MODULE_NAME
Package: ndiswrapper-dkms Version: 1.57-1 Severity: serious Tags: patch Hi, the module fails to build with dkms, because BUILT_MODULE_NAME is not defined in the dkms.conf, here is a patch: diff -Naur ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in --- ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in 2012-03-05 16:49:17.0 +0100 +++ ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in2013-03-28 10:32:28.520623214 +0100 @@ -1,4 +1,5 @@ PACKAGE_NAME=ndiswrapper PACKAGE_VERSION=@VERSION@ +BUILT_MODULE_NAME[0]=$PACKAGE_NAME DEST_MODULE_LOCATION[0]=/updates AUTOINSTALL=yes -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657987: icedove: exception when trying to setup account
On Thu, Mar 28, 2013 at 09:58:41AM +0100, Uwe Kleine-König wrote: Hello Carsten, (BTW, I added -safe-mode with only a single leading dash.) Yes you are right, a typical typo depended on this various options with zero to two hyphen in front. I'd be surprised if the problem didn't reproduce for you. Don't get me wrong, I'm willing to help, but I think it would be easier and faster for you to have gdb run yourself instead of directing me via mail what to do. That's simple, I can't reproduce it. Im not a profi in setting up mail servers so I need help for readjusting this constellation. Also I'm not so deeply dived into the source like Guido or Christoph, but can help in collecting the needed infos. But I will ask Guido and Christoph in one of the next hacking events to go further. But now it is easier for us to comparsing the ouput, so thank you very much for work! On 12d to 14d April we are at the Linuxhotel on the Debian Groupware Meeting [1], so there are some continuous we can work on that issue. You wrote you are reachable in #debian-devel, we will read us I think. [1] http://wiki.debian.org/GroupwareMeeting2013-04-12to14 Regards and thanks for your valuable preliminary work! Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.
On 28/03/2013 10:16, peter green wrote: Sylvestre Ledru wrote: No need to do a NMU here. Ok I've attached a diff. Note: i'm currently running a test build of this version i'll follow up later with results from that test to confirm things are ok (I don't see why they wouldn't be) OK. Looks like you have all things set. Don't hesitate to upload without any DELAY. I will sync that into the svn. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#236227: mozilla-firefox: /etc/papersize should be consulted for the default paper size for printing
Package: iceweasel-l10n-sk Version: 1:10.0.12esr-1 Followup-For: Bug #236227 Bug still occurs with Debian Wheezy. Very annoying, since nobody prints letter format here in SK, thus papersize must be manually changed to A4 every time one is printing from Iceweasel. Otherwise printer hangs up with some kind of bad paper size error, stopping the whole print queue, with obvious problems connected to cancelling the print job, You all know what I'm talking about... Furthermore, Iceweasel ignores not only /etc/papersize, but also the environment locale settings, such as LC_PAPER=sk_SK.UTF-8 I'm not sure, whether should I fill another, separate bug for the instance, or this one is enough. I think this is also matter of localization package, because the wrong paper size (letter) is visible in about:config page and I hope the localization package should take care of all aspects of localization. :~$ locale LANG=sk_SK.UTF-8 LANGUAGE= LC_CTYPE=sk_SK.UTF-8 LC_NUMERIC=sk_SK.UTF-8 LC_TIME=sk_SK.UTF-8 LC_COLLATE=sk_SK.UTF-8 LC_MONETARY=sk_SK.UTF-8 LC_MESSAGES=sk_SK.UTF-8 LC_PAPER=sk_SK.UTF-8 LC_NAME=sk_SK.UTF-8 LC_ADDRESS=sk_SK.UTF-8 LC_TELEPHONE=sk_SK.UTF-8 LC_MEASUREMENT=sk_SK.UTF-8 LC_IDENTIFICATION=sk_SK.UTF-8 LC_ALL= -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=sk_SK.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iceweasel-l10n-sk depends on: ii iceweasel 10.0.12esr-1 Versions of packages iceweasel-l10n-sk recommends: ii myspell-sk 0.5.5a-2.3 iceweasel-l10n-sk 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#590135: php-text-diff
retitle 590135 RFP: php-text-diff -- Engine for performing and rendering text diffs noowner 590135 thanks Text_Diff moved to horde channel . http://packages.qa.debian.org/p/php-horde-text-diff.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#455769: same problem on wheezy + Thinkpad X220T
I recently updated a Lenovo X220T to wheezy I am using the standard wheezy kernel and gnome desktop $ dpkg --list | grep gnome-power ii gnome-power-manager 3.4.0-2amd64power management tool for the GNOME desktop Here are my settings: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' So, it should always suspend when I close the lid - but sometimes it does not suspend e.g. I have the laptop on my desk. I remove the AC cable and close the screen, put the laptop in my backpack. Walk to the train station, sit on the train, take out the laptop, it is extremely hot. On one occasion, it was so hot that the screen had gone off and was non-responsive, I had to poweroff completely by holding the power button for 10 seconds and let it cool before I could use it again. I am raising this bug to critical, as it meets the definition makes unrelated software on the system (or the whole system) break -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#455769: same problem on wheezy + Thinkpad X220T
Control: severity -1 important On Thu, Mar 28, 2013 at 11:01:10 +0100, Daniel Pocock wrote: I recently updated a Lenovo X220T to wheezy I am using the standard wheezy kernel and gnome desktop $ dpkg --list | grep gnome-power ii gnome-power-manager 3.4.0-2amd64power management tool for the GNOME desktop Here are my settings: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' So, it should always suspend when I close the lid - but sometimes it does not suspend e.g. I have the laptop on my desk. I remove the AC cable and close the screen, put the laptop in my backpack. Walk to the train station, sit on the train, take out the laptop, it is extremely hot. On one occasion, it was so hot that the screen had gone off and was non-responsive, I had to poweroff completely by holding the power button for 10 seconds and let it cool before I could use it again. I am raising this bug to critical, as it meets the definition makes unrelated software on the system (or the whole system) break No, it does not. hw will shut itself off before getting damaged. Cheers, Julien signature.asc Description: Digital signature
Bug#704123: virtualbox-ose: my debian desktop will be shutdown after i click some links.
Package: virtualbox-ose Version: 3.2.10-dfsg-1+squeeze1 Severity: grave Tags: upstream Justification: causes non-serious data loss hi, After i installed virtualbox in squeeze,it has comflict with the NVIDIA drivers(Version304.43), some links are broken! when i click some links like virtualbox's network setup ,some WINE soft url, or other software setup (such as rhythmbox ),my debian will be shut down, there is something horrible, i was listenning the music with rhythmbox, my earplug receiver a loudly beeper sounds like BBU!!! : ( , it scared me ! -- System Information: Debian Release: 6.0.7 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-ose depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcurl3 7.21.0-2.1+squeeze2 Multi-protocol file transfer libra ii libgcc11:4.4.5-8 GCC support library ii libpng12-0 1.2.44-1+squeeze4 PNG library - runtime ii libpython2.6 2.6.6-8+b1Shared Python runtime library (ver ii libsdl1.2debian1.2.14-6.1Simple DirectMedia Layer ii libssl0.9.80.9.8o-4squeeze14 SSL shared libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libvncserver0 0.9.7-2+b1API to write one's own vnc server ii libx11-6 2:1.3.3-4 X11 client-side library ii libxcursor11:1.1.10-2X cursor management library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxml22.7.8.dfsg-2+squeeze7 GNOME XML library ii libxmu62:1.0.5-2 X11 miscellaneous utility library ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library ii python 2.6.6-3+squeeze7 interactive high-level object-orie ii python-central 0.6.16+nmu1 register and build utility for Pyt ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages virtualbox-ose recommends: ii libgl1-mesa-glx [ 7.7.1-5A free implementation of the OpenG ii libqt4-opengl 4:4.6.3-4+squeeze1 Qt 4 OpenGL module ii libqtcore44:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii virtualbox-ose-dk 3.2.10-dfsg-1+squeeze1 x86 virtualization solution - kern ii virtualbox-ose-qt 3.2.10-dfsg-1+squeeze1 x86 virtualization solution - Qt b Versions of packages virtualbox-ose suggests: ii libasound2 1.0.23-2.1shared library for ALSA applicatio ii libpulse0 0.9.21-3+squeeze1 PulseAudio client libraries ii vde2 2.2.3-3 Virtual Distributed Ethernet pn virtualbox-guest-addit none(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#704124: codename 'rc-buggy' not handled correctly
Package: ftp.debian.org Severity: normal Hi, it seems that apt is handling the codename 'rc-buggy' for experimental not correctly. zobel@kvasir:~% sudo apt-get update [...] Fetched 26.4 MB in 9s (2,923 kB/s) Reading package lists... Done W: Conflicting distribution: http://ftp.debian.org rc-buggy Release (expected rc-buggy but got experimental) sudo apt-get update 13.97s user 0.99s system 94% cpu 15.864 total zobel@kvasir:~% When looking closer, it seems that rc-buggy is only a symlink in the filesystem but not a codename in the 'Release' file. Please fix this behaviour. Putting debian-devel@l.d.o on CC for this bug report, as this change might have larger impact on installations, so discussing this first might be a good idea. Cheers, Martin PS: I like the idea, that the remote controlled buggy from Toy Story is the code name for experimental. I just dislike above warning. -- Martin Zobel-Helas zo...@debian.orgDebian System Administrator Debian GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B signature.asc Description: Digital signature
Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning
On 03/28/2013 09:55 AM, Jonathan Dowland wrote: On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: could anyone who is seeing the issue with Cheese freezing try to disconnect their webcam In my case I don't think so- it's built into the frame of my laptop screen. How about unloading the kernel module then? I guess it's probably an UVC camera, so modprobe -r uvcvideo should do the trick for most cameras (as most of them are UVC). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704125: parallel: stdout of commands is not deterministic
Package: moreutils Version: 0.41 I have a huge number of files in a directory (which is tmpfs mounted) ls |wc -l 9010 du -sh 12G ls *.out |wc -l 5003 This is a 96GB RAM dual CPU hexacore machine, so I have 12 cores in all. Now I like to compute the md5sum of all files *.out in parallel and write them to a file. My first attempt: rm -f /tmp/list ; parallel.moreutils md5sum -- *.out /tmp/list ; wc -l /tmp/list 4666 /tmp/list I repreat the command several times: rm -f /tmp/list ; parallel.moreutils md5sum -- *.out /tmp/list ; wc -l /tmp/list 4656 /tmp/list rm -f /tmp/list ; parallel.moreutils md5sum -- *.out /tmp/list ; wc -l /tmp/list 4660 /tmp/list rm -f /tmp/list ; parallel.moreutils md5sum -- *.out /tmp/list ; wc -l /tmp/list 4687 /tmp/list rm -f /tmp/list ; parallel.moreutils md5sum -- *.out /tmp/list ; wc -l /tmp/list 4683 /tmp/list Adding -n100 or reducing the number of parallel jobs using -j3 does not help. It's a non-deterministic behaviour. GNU parallel 20120322 does the same job perfect. It always has 5003 lines in the output file. I wonder why adding a pipe and a cat command to parallel.moreutils fixes this ? rm -f /tmp/list ; parallel.moreutils -n100 md5sum -- *.out | cat /tmp/list ; wc -l /tmp/list 5003 /tmp/list Is this a lack of documentation or a bug? -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704047: unblock: kvpm/0.8.6-3
Control: tags -1 + moreinfo On 27.03.2013 10:32, John Paul Adrian Glaubitz wrote: the upstream author of kvpm who also happens to be the Debian maintainer of the package recently found a critical bug when moving partitions [1]. I have reviewed his package and I'm attaching the Debdiff. I have to admit that I'm really not overly happy about the use of urgency=critical here; that implies that the package should immediately transition to testing with no time in unstable and there are _very_ few cases where it would be justified - as far as I can tell from the bug report, this is an issue that only affects an operation which I'd at least be very cautious about trying on a drive containing live data, and even the maintainer says only happens sometimes. In any case, this will either have to go via t-p-u or wait for a point release, as it's picked up a depedency on liblvm2app2.2 (= 2.02.98), which isn't satisfiable in wheezy. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
On Thu, Mar 28, 2013 at 11:13:34AM +0100, John Paul Adrian Glaubitz wrote: How about unloading the kernel module then? I guess it's probably an UVC camera, so modprobe -r uvcvideo should do the trick for most cameras (as most of them are UVC). Thanks for the tip. It is indeed uvcvideo, and unloading it means cheese draws its UI (No device found). Interesting stuff. I'm going to try splicing some debug statements into the code to see at what point it reaches and whether that helps get any further. FWIW some earlier verison of cheese worked with this webcam on this laptop. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657987: icedove: exception when trying to setup account
Hello Carsten, On Thu, Mar 28, 2013 at 10:35:14AM +0100, Carsten Schoenert wrote: On Thu, Mar 28, 2013 at 09:58:41AM +0100, Uwe Kleine-König wrote: Hello Carsten, (BTW, I added -safe-mode with only a single leading dash.) Yes you are right, a typical typo depended on this various options with zero to two hyphen in front. I'd be surprised if the problem didn't reproduce for you. Don't get me wrong, I'm willing to help, but I think it would be easier and faster for you to have gdb run yourself instead of directing me via mail what to do. That's simple, I can't reproduce it. Im not a profi in setting up mail Note this only happens for me in the initial config dialog. So to reproduce I do: mv .icedove .icedove.precious icedove Maybe that helps you to reproduce ... maybe not. Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: codename 'rc-buggy' not handled correctly
On Thu, Mar 28, 2013 at 11:02:11 +0100, Martin Zobel-Helas wrote: Package: ftp.debian.org Severity: normal Hi, it seems that apt is handling the codename 'rc-buggy' for experimental not correctly. zobel@kvasir:~% sudo apt-get update [...] Fetched 26.4 MB in 9s (2,923 kB/s) Reading package lists... Done W: Conflicting distribution: http://ftp.debian.org rc-buggy Release (expected rc-buggy but got experimental) sudo apt-get update 13.97s user 0.99s system 94% cpu 15.864 total zobel@kvasir:~% When looking closer, it seems that rc-buggy is only a symlink in the filesystem but not a codename in the 'Release' file. Please fix this behaviour. Putting debian-devel@l.d.o on CC for this bug report, as this change might have larger impact on installations, so discussing this first might be a good idea. rc-buggy is not a codename, it's a bad joke. Don't use it? Cheers, Julien signature.asc Description: Digital signature
Bug#704126: RM: python-bcrypt/0.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hello, as discussed with Julien Cristau on #debian-security today, please remove the package python-bcrypt from testing. The package currently has one RC bug [1]. While there is a patch available from upstream attached in [1], the general shape of the package is very bad (just one upload, 5 years ago), so it was suggested to remove the package. Cheers, Adrian [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704030 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704041: procps: Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report
On Wed, Mar 27, 2013 at 01:14:53PM +0100, Thorsten Glaser wrote: Can you run strace on it? It looks like libproc doesn't like something found in the kernel /proc filesystem but strace will tell us which one. typescript attached. Thanks for that trace and the report. Just in case you don't follow the bug tracker to closely I have raised the level of the bug report and the one its merged with to serious. The reason for this is that a lot of other people will cop this bug if they have larger than normal set of groups for processes. I have prepared a minimal patch for wheezy and asked for procps 3.3.3-3 to be unblocked so this bug can not be in wheezy. While I feel pretty bad giving the release team more work at this important time, ps crashing is a pretty bad bug. So, cross your fingers and hope they let the patch through! Again, thanks for the report. It has basically (hopefully) stopped a bad ps going into the wheezy release. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704047: unblock: kvpm/0.8.6-3
On 03/28/2013 11:20 AM, Adam D. Barratt wrote: I have to admit that I'm really not overly happy about the use of urgency=critical here; that implies that the package should immediately transition to testing with no time in unstable and there are _very_ few cases where it would be justified - as far as I can tell from the bug report, this is an issue that only affects an operation which I'd at least be very cautious about trying on a drive containing live data, and even the maintainer says only happens sometimes. Hmm, valid point. These changes and the urgency were made by the original maintainer of the package who also happens to be the upstream author, so I am putting him into CC of this mail. In any case, this will either have to go via t-p-u or wait for a point release, as it's picked up a depedency on liblvm2app2.2 (= 2.02.98), which isn't satisfiable in wheezy. That's too bad. But I would go ahead now, build 0.8.6-3+wheezy1 with urgency=high (or medium, low), if you agree. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704127: unblock: procps/3.3.3-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package procps
ps crashes when processes have larger than normal groups, essentially
it is because the /proc/PID/status file is larger than 1024 bytes. This
is NOT a buffer overflow but the parser gets all sad because it runs out
of things to parse.
The fix is a rather simple bump up the buffer from 1024 to 4096.
This fixes bug #702965 which is merged with another.
We (upstream) have a permanent fix in later versions that is much more
intrusive.
Strictly speaking, the bug is in libproc0 not procps, it is just that
the binary ps crashes because of it.
unblock procps/3.3.3-3
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru procps-3.3.3/debian/changelog procps-3.3.3/debian/changelog
--- procps-3.3.3/debian/changelog 2012-06-17 18:06:28.0 +1000
+++ procps-3.3.3/debian/changelog 2013-03-28 21:14:02.0 +1100
@@ -1,3 +1,9 @@
+procps (1:3.3.3-3) UNRELEASED; urgency=low
+
+ * 3.3.3-3 Fix ps crash with large process groups Closes: #702965
+
+ -- Craig Small csm...@debian.org Thu, 28 Mar 2013 21:03:15 +1100
+
procps (1:3.3.3-2) unstable; urgency=low
* Fixes for kFreeBSD Closes: #674785
diff -Nru procps-3.3.3/debian/patches/bts702965-biggerbuff procps-3.3.3/debian/patches/bts702965-biggerbuff
--- procps-3.3.3/debian/patches/bts702965-biggerbuff 1970-01-01 10:00:00.0 +1000
+++ procps-3.3.3/debian/patches/bts702965-biggerbuff 2013-03-28 21:17:28.0 +1100
@@ -0,0 +1,47 @@
+Description: ps: allow large list of groups
+ ps crashes when the information exceeds 1024 bytes in files such as
+ /proc/PID/status.
+Origin: https://www.gitorious.org/procps/procps/commit/7933435584aa1fd75460f4c7715a3d4855d97c1c
+Author: Eric Dumazet eric.duma...@gmail.com
+Reviewed-by: Craig Small csm...@debian.org
+Bug-Debian: http://bugs.debian.org/702965
+--- a/proc/readproc.c
b/proc/readproc.c
+@@ -353,7 +353,9 @@
+ P-vm_swap = strtol(S,S,10);
+ continue;
+ case_Groups:
+-{ int j = strchr(S, '\n') - S;// currently lines end space + \n
++{ char *nl = strchr(S, '\n');
++int j = nl ? (nl - S) : strlen(S);
++
+ if (j) {
+ P-supgid = xmalloc(j+1); // +1 in case space disappears
+ memcpy(P-supgid, S, j);
+@@ -723,7 +725,7 @@
+ // room to spare.
+ static proc_t* simple_readproc(PROCTAB *restrict const PT, proc_t *restrict const p) {
+ static struct stat sb; // stat() buffer
+-static char sbuf[1024];// buffer for stat,statm,status
++static char sbuf[4096];// buffer for stat,statm,status
+ char *restrict const path = PT-path;
+ unsigned flags = PT-flags;
+
+@@ -827,7 +829,7 @@
+ // path is a path to the task, with some room to spare.
+ static proc_t* simple_readtask(PROCTAB *restrict const PT, const proc_t *restrict const p, proc_t *restrict const t, char *restrict const path) {
+ static struct stat sb; // stat() buffer
+-static char sbuf[1024];// buffer for stat,statm,status
++static char sbuf[4096];// buffer for stat,statm,status
+ unsigned flags = PT-flags;
+
+ if (unlikely(stat(path, sb) == -1))/* no such dirent (anymore) */
+@@ -1368,7 +1370,7 @@
+ * and filled out proc_t structure.
+ */
+ proc_t * get_proc_stats(pid_t pid, proc_t *p) {
+- static char path[32], sbuf[1024];
++ static char path[32], sbuf[4096];
+ struct stat statbuf;
+
+ sprintf(path, /proc/%d, pid);
diff -Nru procps-3.3.3/debian/patches/series procps-3.3.3/debian/patches/series
--- procps-3.3.3/debian/patches/series 2012-06-17 18:00:06.0 +1000
+++ procps-3.3.3/debian/patches/series 2013-03-28 21:14:25.0 +1100
@@ -2,3 +2,4 @@
bts676239-pkill-u-option
watch_8bit
uptime_test
+bts702965-biggerbuff
Bug#696727: Info received (Bug#696727: cheese does not start with Gtk-Warning)
I've just noticed that cheese is busy looping and mallocing whilst it's seemingly doing nothing: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 18958 jon 20 0 7513m 6.2g 3236 R 92.1 80.0 20:03.57 cheese -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: codename 'rc-buggy' not handled correctly
On 03/28/2013 11:21 AM, Julien Cristau wrote: rc-buggy is not a codename, it's a bad joke. Don't use it? I actually never noticed the pun but very much like the idea as it would be equivalent to the pun used for unstable (=sid), the pun fits perfect. Why not make rc-buggy the official code name for experimental? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701150: debsums backport installed on piatti
Hi, debsums 2.0.51~bpo60+1 has been installed on piatti now, shall we close #701150? Reschedule some logs? cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704073: [multipath-tools-boot] error when update-initramfs
reassign 704073 multipath-tools-boot thanks * Ritesh Raj Sarraf [Thu Mar 28, 2013 at 10:58:20AM +0530]: On Wednesday 27 March 2013 10:03 PM, Guy Roussin wrote: I get this error when upgrading from squeeze to wheezy on a boot on san (ibm ds4700) update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 /var/tmp/mkinitramfs_aO0QW9/scripts/init-top/multipath: 5: .: Can't open /scripts/functions I copy and paste /usr/share/initramfs-tools/scripts/functions in /usr/share/initramfs-tools/scripts/init-top/multipath and the error is gone ... I can't see a reason why this would fail. I suspect it to be an initramfs problem. Looks like /usr/share/initramfs-tools/scripts/init-top/multipath is missing the PREREQ/prereqs header (see e.g. initramfs-tools(8)), so set this up (so the script works also outside the initramfs) and *then* use . /scripts/functions. Reassigning back to multipath-tools-boot. regards, -mika- signature.asc Description: Digital signature
Bug#704047: unblock: kvpm/0.8.6-3
Control: tags -1 +confirmed -moreinfo On 28.03.2013 10:33, John Paul Adrian Glaubitz wrote: On 03/28/2013 11:20 AM, Adam D. Barratt wrote: In any case, this will either have to go via t-p-u or wait for a point release, as it's picked up a depedency on liblvm2app2.2 (= 2.02.98), which isn't satisfiable in wheezy. That's too bad. But I would go ahead now, build 0.8.6-3+wheezy1 That would be higher than the version in unstable. :) Please use 0.8.6-2+deb7u1. with urgency=high (or medium, low), if you agree. From britney's point of view t-p-u uploads always transition asap (once they're approved, built, etc) so the urgency is largely only for users in this case; high would be fine. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#455769: same problem on wheezy + Thinkpad X220T
On 28/03/13 11:06, Julien Cristau wrote: Control: severity -1 important I am raising this bug to critical, as it meets the definition makes unrelated software on the system (or the whole system) break No, it does not. hw will shut itself off before getting damaged. Would you provide a guarantee to all users of wheezy that you will pay for their laptop repair if this issue causes damage? Having the hardware shutdown like that is also a nasty thing that involves the user losing unsaved work, maybe corrupting preferences for their desktop if they are unlucky. This problem happens regularly enough that Debian should not be promoted for laptops if it is not taken seriously as an RC issue. Users will get a very bad impression if basic things like this aren't working in a stable release. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455769 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704047: unblock: kvpm/0.8.6-3
On 03/28/2013 11:44 AM, Adam D. Barratt wrote: Control: tags -1 +confirmed -moreinfo On 28.03.2013 10:33, John Paul Adrian Glaubitz wrote: On 03/28/2013 11:20 AM, Adam D. Barratt wrote: In any case, this will either have to go via t-p-u or wait for a point release, as it's picked up a depedency on liblvm2app2.2 (= 2.02.98), which isn't satisfiable in wheezy. That's too bad. But I would go ahead now, build 0.8.6-3+wheezy1 That would be higher than the version in unstable. :) Please use 0.8.6-2+deb7u1. True, the moment I sent the mail, I had a dejavu regarding this [1] :). with urgency=high (or medium, low), if you agree. From britney's point of view t-p-u uploads always transition asap (once they're approved, built, etc) so the urgency is largely only for users in this case; high would be fine. True, when you're already in testing, there's not point to transition from. Will upload the package now. Adrian [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697957 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704127: unblock: procps/3.3.3-3
Control: tags -1 + moreinfo On 28.03.2013 10:24, Craig Small wrote: Please unblock package procps ps crashes when processes have larger than normal groups, essentially it is because the /proc/PID/status file is larger than 1024 bytes. This is NOT a buffer overflow but the parser gets all sad because it runs out of things to parse. This doesn't appear to have made it to the archive yet as far as I can see. If the attached debdiff was created from the final package then that's possibly due to: --- procps-3.3.3/debian/changelog 2012-06-17 18:06:28.0 +1000 +++ procps-3.3.3/debian/changelog 2013-03-28 21:14:02.0 +1100 @@ -1,3 +1,9 @@ +procps (1:3.3.3-3) UNRELEASED; urgency=low ^^ unstable already has 3.3.4-2, so a fix for this in wheezy would need to go via testing-proposed-updates. In such cases, we'd generally be looking at getting the fix in to unstable first though. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673724: New Upstream
New upstream source URL: https://github.com/jshint/jshint Also see Hompage http://jshint.com/. Current stable version is 1.1.0 Also see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559969 for the RFP for jslint -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99 http://www.univention.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: rc-buggy is a nice pun
Hi, I also think that rc-buggy is a nice pun and I also like that its in the same spirit as sid+unstable too. Just that if it exists at all, it should be supported / be usuable the same as sid/unstable is. So either remove all occurances of rc-buggy or use the experimental/rc-buggy combo everywhere like unstable/sid and so on. cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704128: nodm: please add support for NODM_X_TIMEOUT via debconf
Package: nodm Version: 0.11-1.3 Severity: wishlist Tags: patch Hello, Please consider the following patch that allows NODM_X_TIMEOUT to be configured via debconf variable. diff -u nodm-0.11/debian/nodm.postinst nodm-0.11/debian/nodm.postinst --- nodm-0.11/debian/nodm.postinst +++ nodm-0.11/debian/nodm.postinst @@ -39,6 +39,8 @@ NODM_MIN_SESSION_TIME=$RET db_get nodm/xsession NODM_XSESSION=$RET + db_get nodm/x_timeout + NODM_X_TIMEOUT=$RET if [ -s /etc/default/nodm ] ; then sed -i -r -e s,^NODM_ENABLED=.*,NODM_ENABLED=$NODM_ENABLED, \ @@ -47,6 +49,7 @@ -e s,^NODM_X_OPTIONS=.*,NODM_X_OPTIONS='$NODM_X_OPTIONS', \ -e s,^NODM_MIN_SESSION_TIME=.*,NODM_MIN_SESSION_TIME=$NODM_MIN_SESSION_TIME, \ -e s,^NODM_XSESSION=.*,NODM_XSESSION=$NODM_XSESSION, \ + -e s,^NODM_X_TIMEOUT=.*,NODM_X_TIMEOUT=$NODM_X_TIMEOUT, \ /etc/default/nodm else cat EOF /etc/default/nodm @@ -70,6 +73,10 @@ # If an X session will run for less than this time in seconds, nodm will wait an # increasing bit of time before restarting the session. NODM_MIN_SESSION_TIME=$NODM_MIN_SESSION_TIME + +# Timeout (in seconds) to wait for X to be ready to accept connections. If X is +# not ready before this timeout, it is killed and restarted. +NODM_X_TIMEOUT=$NODM_X_TIMEOUT EOF fi fi diff -u nodm-0.11/debian/nodm.init nodm-0.11/debian/nodm.init --- nodm-0.11/debian/nodm.init +++ nodm-0.11/debian/nodm.init @@ -25,13 +25,14 @@ NODM_X_OPTIONS=-nolisten tcp NODM_USER=root NODM_MIN_SESSION_TIME=60 +NODM_X_TIMEOUT=300 if [ -f /etc/default/$NAME ] then . /etc/default/$NAME fi -export NODM_XINIT NODM_XSESSION NODM_X_OPTIONS NODM_USER NODM_MIN_SESSION_TIME NODM_FIRST_VT +export NODM_XINIT NODM_XSESSION NODM_X_OPTIONS NODM_USER NODM_MIN_SESSION_TIME NODM_FIRST_VT NODM_X_TIMEOUT # If you change the user to a non-root user, make sure you # set allowed_users=anybody in /etc/X11/Xwrapper.config diff -u nodm-0.11/debian/nodm.config nodm-0.11/debian/nodm.config --- nodm-0.11/debian/nodm.config +++ nodm-0.11/debian/nodm.config @@ -57,6 +57,9 @@ if [ -n $NODM_XSESSION ]; then db_set nodm/xsession $NODM_XSESSION fi + if [ -n $NODM_X_TIMEOUT ]; then + db_set nodm/x_timeout $NODM_X_TIMEOUT + fi fi db_input medium nodm/enabled || true @@ -81,4 +84,7 @@ db_input low nodm/xsession || true db_go + + db_input low nodm/x_timeout || true + db_go fi only in patch2: unchanged: --- nodm-0.11.orig/README +++ nodm-0.11/README @@ -46,7 +46,7 @@ * Configuration -Configuration is made via 5 environment variables: +Configuration is made via these environment variables: NODM_USER Controls the user that is used to automatically log in. Regards, Hector Oron -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.8-trunk-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nodm depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libpam0g 1.1.3-9 ii libx11-6 2:1.5.0-1 ii x11-common 1:7.7+2 ii x11-xserver-utils 7.7~3 nodm recommends no packages. nodm suggests no packages. -- debconf information: * nodm/xsession: /etc/X11/Xsession * nodm/x_options: -nolisten tcp * nodm/first_vt: 7 * nodm/min_session_time: 60 * nodm/enabled: true * nodm/user: zumbi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699922: ITP: pyobfsproxy -- pluggable transport proxy for Tor (Python implementation)
reassign 699922 obfsproxy retitle 699922 Please update with the new Python implementation thanks pyobfsproxy is a tool that attempts to circumvent censorship by transforming the Tor traffic between the client and the bridge. This way censors, who usually monitor traffic between the client and the bridge, will see innocent-looking transformed traffic instead of the actual Tor traffic. It is written in Python and is compliant with the Tor pluggable transports specification. Upstream has decided to supersede the C implementation of obfsproxy with the Python one. The latter is going to keep the name obfsproxy and so we can also keep the same source and binary package names. -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#455769: same problem on wheezy + Thinkpad X220T
On 03/28/2013 11:47 AM, Daniel Pocock wrote: Would you provide a guarantee to all users of wheezy that you will pay for their laptop repair if this issue causes damage? Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. This problem happens regularly enough that Debian should not be promoted for laptops if it is not taken seriously as an RC issue. Users will get a very bad impression if basic things like this aren't working in a stable release. I have heard of that problem for the very first time now and I have been using Debian on a laptop since around 2004, on various machines like the Thinkpad 240X, X40, T42, T60, T23. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: codename 'rc-buggy' not handled correctly
Hi, On Thu Mar 28, 2013 at 11:21:29 +0100, Julien Cristau wrote: On Thu, Mar 28, 2013 at 11:02:11 +0100, Martin Zobel-Helas wrote: Putting debian-devel@l.d.o on CC for this bug report, as this change might have larger impact on installations, so discussing this first might be a good idea. rc-buggy is not a codename, it's a bad joke. Don't use it? well, removing it now that it is already used will also break installations, so i would suggest we make it a codename now. Cheers, Martin -- Martin Zobel-Helas zo...@debian.orgDebian System Administrator Debian GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654787: can somebody from the kde team take a look at this ?
Control: retitle -1 [ITP] oxygen-transparent -- KDE Oxygen style and decoration with support for transparency Control: owner -1 ! As discussed on IRC, I'll work on this. Regards, Daniele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615492: Users connected to server cannot hear each other
Hi, just wanted to confirm that the bug still exists in current 1.2.3-349-g315b5f5-2.2 (armel). Best regards, Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702965: Fixed in 3.3.4-1
Package: procps Version: 1%3.3.4-1 Upstream commit at https://www.gitorious.org/procps/procps/commit/7933435584aa1fd75460f4c7715a3d4855d97c1c fixed this which appeared in upstream version 3.3.4. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704130: virtualbox-guest-dkms: Module build fails on kernel 3.2 - please apply upstream patch
Package: virtualbox-guest-dkms Version: 4.0.10-dfsg-1~bpo60+1 Severity: important MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Andrew Gallagher andr...@andrewg.com To: Debian Bug Tracking System sub...@bugs.debian.org Subject: virtualbox-guest-dkms: module build fails on kernel 3.2 - please implement upstream patch Message-ID: 20130328110730.6268.72127.reportbug@itchy X-Mailer: reportbug 4.12.6 Date: Thu, 28 Mar 2013 11:07:30 + Package: virtualbox-guest-dkms Version: 4.0.10-dfsg-1~bpo60+1 Severity: important There is an error building utils.o under kernel 3.2 - this has been fixed upstream for some time and a patch is available: https://www.virtualbox.org/changeset/39224/vbox Transcript: agallagher@itchy:~$ sudo apt-get install --reinstall virtualbox-guest-dkms Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libbase-java-openoffice.org libxerces2-java fonts-opensymbol mesa-common-dev libxerces2-java-gcj libserializer-java-openoffice.org libjaxp1.3-java-gcj Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/547 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 142544 files and directories currently installed.) Preparing to replace virtualbox-guest-dkms 4.0.10-dfsg-1~bpo60+1 (using .../virtualbox-guest-dkms_4.0.10-dfsg-1~bpo60+1_all.deb) ... -- Deleting module version: 4.0.10 completely from the DKMS tree. -- Done. Unpacking replacement virtualbox-guest-dkms ... Setting up virtualbox-guest-dkms (4.0.10-dfsg-1~bpo60+1) ... Loading new virtualbox-guest-4.0.10 DKMS files... Building only for 3.2.0-0.bpo.4-rt-amd64 Building initial module for 3.2.0-0.bpo.4-rt-amd64 Error! Bad return status for module build on kernel: 3.2.0-0.bpo.4-rt-amd64 (x86_64) Consult the make.log in the build directory /var/lib/dkms/virtualbox-guest/4.0.10/build/ for more information. agallagher@itchy:~$ tail -20 /var/lib/dkms/virtualbox-guest/4.0.10/build/make.log LD [M] /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxguest/vboxguest.o LD /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/built-in.o CC [M] /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/vfsmod.o CC [M] /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/dirops.o CC [M] /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/lnkops.o CC [M] /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/regops.o CC [M] /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.o /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.c: In function ‘sf_init_inode’: /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.c:112: error: assignment of read-only member ‘i_nlink’ /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.c:121: error: assignment of read-only member ‘i_nlink’ /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.c:131: error: assignment of read-only member ‘i_nlink’ /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.c: In function ‘sf_nlscpy’: /var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.c:562: warning: passing argument 3 of ‘utf8_to_utf32’ from incompatible pointer type /usr/src/linux-headers-3.2.0-0.bpo.4-common-rt/include/linux/nls.h:53: note: expected ‘unicode_t *’ but argument is of type ‘wchar_t *’ make[4]: *** [/var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf/utils.o] Error 1 make[3]: *** [/var/lib/dkms/virtualbox-guest/4.0.10/build/vboxsf] Error 2 make[2]: *** [_module_/var/lib/dkms/virtualbox-guest/4.0.10/build] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 make: Leaving directory `/usr/src/linux-headers-3.2.0-0.bpo.4-rt-amd64' -- System Information: Debian Release: 6.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-guest-dkms depends on: ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram ii virtualbox-guest-u 4.0.10-dfsg-1~bpo60+1 x86 virtualization solution - non- virtualbox-guest-dkms recommends no packages. virtualbox-guest-dkms suggests no packages. -- no debconf information -- System Information: Debian Release: 6.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-guest-dkms depends on: ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram ii virtualbox-guest-u
Bug#455769: same problem on wheezy + Thinkpad X220T
On 28-03-13 11:47, Daniel Pocock wrote: On 28/03/13 11:06, Julien Cristau wrote: Control: severity -1 important I am raising this bug to critical, as it meets the definition makes unrelated software on the system (or the whole system) break No, it does not. hw will shut itself off before getting damaged. Would you provide a guarantee to all users of wheezy that you will pay for their laptop repair if this issue causes damage? Oh please. I've never seen a laptop that will not cause a poweroff in hardware if the operating system isn't doing its job. This is also not a critical issue. If gnome-power-manager were to go berserk and do the equivalent of rm -rf /, or kill -9 on all processes on the system, or something similar, that would be a critical bug in the makes the whole system break sense. As it is, gnome-power-manager just *doesn't* do something it's supposed to do. It's not even close to being critical in that sense. I agree that it's probably a problem, and that it'd be good if we were to fix it before the release; but anything above important strikes me as unnecessary severity inflation. (on a more personal note, why oh why would you ever want the system to suspend when you close the lid? That's what a suspend button is for. If my laptop is compiling something, I do *not* want it to suspend when I close the lid, thankyouverymuch. Oh well) -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704127: unblock: procps/3.3.3-3
On Thu, Mar 28, 2013 at 10:51:47AM +, Adam D. Barratt wrote: This doesn't appear to have made it to the archive yet as far as I can see. If the attached debdiff was created from the final package I thought the debdiff needed to be sent first, anyhow its now uploaded to testing-proposed-updates. unstable already has 3.3.4-2, so a fix for this in wheezy would need to go via testing-proposed-updates. In such cases, we'd generally be looking at getting the fix in to unstable first though. Thanks for the tip, 3.3.4-1 had this same fix so I've let the BTS know about that too. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704122: ndiswrapper-dkms: Fails to build module because of missing BUILT_MODULE_NAME
Control: reassign -1 dkms Control: forcemerge 690747 -1 Control: affects 690747 ndiswrapper-dkms On Thu, Mar 28, 2013 at 10:35:04AM +0100, Patrick Matthäi wrote: Package: ndiswrapper-dkms Version: 1.57-1 Severity: serious Tags: patch Hi, the module fails to build with dkms, because BUILT_MODULE_NAME is not defined in the dkms.conf, here is a patch: diff -Naur ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in --- ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in 2012-03-05 16:49:17.0 +0100 +++ ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in2013-03-28 10:32:28.520623214 +0100 @@ -1,4 +1,5 @@ PACKAGE_NAME=ndiswrapper PACKAGE_VERSION=@VERSION@ +BUILT_MODULE_NAME[0]=$PACKAGE_NAME DEST_MODULE_LOCATION[0]=/updates AUTOINSTALL=yes The configuration file is fully specified as defined by the dkms manual page and worked previously. As such, dkms should be considered broken; not ndiswrapper. It is not my task to work around third party mistakes. I asked the dkms maintainers in the other bug on 2013-03-03, but have not received any explanation for the breakage. I just noticed that I cannot even reproduce this problem; so whatever you do to get this breakage, please discuss this with the dkms maintainers. -- Log showing that it works for me: Get:1 http://localhost/debian/ sid/main dkms all 2.2.0.3-1.2 [77.4 kB] Get:2 http://localhost/debian/ sid/main linux-headers-3.2.0-4-common amd64 3.2.41-2 [3,547 kB] Get:3 http://localhost/debian/ sid/main linux-kbuild-3.2 amd64 3.2.17-1 [238 kB] Get:4 http://localhost/debian/ sid/main linux-headers-3.2.0-4-amd64 amd64 3.2.41-2 [598 kB] Get:5 http://localhost/debian/ sid/main linux-headers-amd64 amd64 3.2+46 [4,450 B] Get:6 http://localhost/debian/ sid/main ndiswrapper-dkms all 1.57-1 [192 kB] Fetched 4,657 kB in 7s (623 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of ndiswrapper-dkms (- 1.57-1) unfixed Summary: ndiswrapper-dkms(1 bug) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y Selecting previously unselected package dkms. (Reading database ... 201512 files and directories currently installed.) Unpacking dkms (from .../dkms_2.2.0.3-1.2_all.deb) ... Selecting previously unselected package linux-headers-3.2.0-4-common. Unpacking linux-headers-3.2.0-4-common (from .../linux-headers-3.2.0-4-common_3.2.41-2_amd64.deb) ... Selecting previously unselected package linux-kbuild-3.2. Unpacking linux-kbuild-3.2 (from .../linux-kbuild-3.2_3.2.17-1_amd64.deb) ... Selecting previously unselected package linux-headers-3.2.0-4-amd64. Unpacking linux-headers-3.2.0-4-amd64 (from .../linux-headers-3.2.0-4-amd64_3.2.41-2_amd64.deb) ... Selecting previously unselected package linux-headers-amd64. Unpacking linux-headers-amd64 (from .../linux-headers-amd64_3.2+46_amd64.deb) ... Selecting previously unselected package ndiswrapper-dkms. Unpacking ndiswrapper-dkms (from .../ndiswrapper-dkms_1.57-1_all.deb) ... Processing triggers for man-db ... Setting up dkms (2.2.0.3-1.2) ... Setting up linux-headers-3.2.0-4-common (3.2.41-2) ... Setting up linux-kbuild-3.2 (3.2.17-1) ... Setting up linux-headers-3.2.0-4-amd64 (3.2.41-2) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-4-amd64 Setting up linux-headers-amd64 (3.2+46) ... Setting up ndiswrapper-dkms (1.57-1) ... Loading new ndiswrapper-1.57 DKMS files... First Installation: checking all kernels... Building only for 3.2.0-4-amd64 Building initial module for 3.2.0-4-amd64 Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.2.0-4-amd64/updates/dkms/ depmod -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpfyazMg5gfh.pgp Description: PGP signature
Bug#704131: RFS: php-calendar/0.5.5-1 [ITA]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package php-calendar * Package name: php-calendar Version : 0.5.5-1 * URL : http://pear.php.net/package/Calendar * License : BSD-3-clause Section : php It builds those binary packages: php-calendar - PHP PEAR package for building Calendar data structures To access further information about this package, please visit the following URL: http://mentors.debian.net/package/php-calendar Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/php-calendar/php-calendar_0.5.5-1.dsc Changes since the last upload: php-calendar (0.5.5-1) experimental; urgency=low * Initial release. (Closes: #605271) Regards, Prach Pongpanich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704128: nodm: please add support for NODM_X_TIMEOUT via debconf
On Thu, Mar 28, 2013 at 11:57:37AM +0100, Hector Oron wrote: Package: nodm Version: 0.11-1.3 Severity: wishlist Tags: patch Apparently the proposed patch causes installability issues and needs to be improved. I'll submit updated patch once found the issue. -- Hector Oron signature.asc Description: Digital signature
Bug#704124: codename 'rc-buggy' not handled correctly
Just as unstable has sid, experimental is rc-buggy, the rc car from toy story. Hilarious joke :) T On Mar 28, 2013 6:36 AM, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: On 03/28/2013 11:21 AM, Julien Cristau wrote: rc-buggy is not a codename, it's a bad joke. Don't use it? I actually never noticed the pun but very much like the idea as it would be equivalent to the pun used for unstable (=sid), the pun fits perfect. Why not make rc-buggy the official code name for experimental? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.**debian.orgdebian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/**51541d12.6040...@physik.fu-**berlin.dehttp://lists.debian.org/51541d12.6040...@physik.fu-berlin.de
Bug#704093: libcurl4-openssl-dev: Please ship uncompress pdf
tags 704093 pending
kthxbye
On mer, mar 27, 2013 at 04:40:43 +0100, Sylvestre Ledru wrote:
Package: libcurl4-openssl-dev
Version: 7.26.0-1
Severity: minor
Hello,
A few PDFs (34) are compressed in the package:
$ dpkg -L libcurl4-openssl-dev |grep pdf.gz
It would be easier if they were unpacked (or moved in a dedicated doc
package).
I'm already working on moving the pdf and html files to a -doc package but I
don't see how this would help in this case. Anyway, it makes sense to have the
pdfs uncompressed so I'll just do it.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Bug#704132: mediathekview: Please fix StartupWMClass in desktop file
Package: mediathekview Version: 3.1.0-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: * Fix StartupWMClass in desktop file. Otherwise Unity fails to associate the launched java process with the desktop file. Thanks for considering the patch. diff -Nru mediathekview-3.1.0/debian/changelog mediathekview-3.1.0/debian/changelog diff -Nru mediathekview-3.1.0/debian/mediathekview.desktop mediathekview-3.1.0/debian/mediathekview.desktop --- mediathekview-3.1.0/debian/mediathekview.desktop 2012-10-03 20:08:18.0 +0200 +++ mediathekview-3.1.0/debian/mediathekview.desktop 2013-03-28 12:56:03.0 +0100 @@ -11,7 +11,7 @@ MimeType= Path= StartupNotify=true -StartupWMClass=MediathekView +StartupWMClass=mediathek-Main Terminal=false Type=Application Version=1.0
Bug#704020: gcc-4.8: FTBFS on hppa
On 28-Mar-13, at 1:25 AM, Matthias Klose wrote: Am 26.03.2013 23:14, schrieb Dave Anglin: Package: gcc-4.8 Version: 4.8.0-1 Severity: normal There is a config problem building the hppa64 package: David, I'm applying this patch, however I don't see much sense anymore in having a current compiler without at least an unstable chroot. Back in Jan/ Feb I did ask about the state of it, asked Aurelian to re-send open issues about ports.debian.org, but didn't get any reply. Thanks for applying the patch and trying to query Aurelian. Regarding ports, I also never got any replies. Helge Deller and myself would still like to get a hppa buildd going. Had a couple of emails with Bdale on the subject. It appears that it may be possible to setup a wanna build server outside Debian although Helge favours using the existing Debian setup. Helge has setup a package upload system to parisc-linux.org. So, to access the packages that we have, one just has to add the following to /etc/apt/ sources.list: deb ftp://ftp.de.debian.org/debian-ports unstable main deb ftp://ftp.parisc-linux.org/debian-ports/unstable unstable main There are a thousand or so packages there. Uploaded gcc-4.8 package set last night. Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704133: ekiga: CVE-2013-1864
Package: ekiga Severity: important Tags: security Please see http://www.openwall.com/lists/oss-security/2013/03/15/6 for details. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#455769: same problem on wheezy + Thinkpad X220T
On 03/28/2013 07:32 AM, Wouter Verhelst wrote: (on a more personal note, why oh why would you ever want the system to suspend when you close the lid? That's what a suspend button is for. If my laptop is compiling something, I do *not* want it to suspend when I close the lid, thankyouverymuch. Oh well) If nothing else, for symmetry. If a laptop will wake up from suspend when you open the lid (which mine at least will), having it go to sleep when you close it would be an intuitive behavior. For some people, having that intuitive symmetry broken produces enough mental dissonance that they are more comfortable with it present, even at the cost you describe. It's also a matter of convenience; if you *do* want to both suspend and close the lid in a particular case, with suspend-on-lid-close you can get the job done with just one action, but with suspend-only-on-button-press you have to take two. You pay for that convenience by sacrificing the convenience of being able to close the lid *without* suspending, but which inconvenience is the greater depends on your usage patterns, and different people may well prefer to sacrifice different ones. -- The Wanderer Warning: Simply because I argue an issue does not mean I agree with any side of it. Every time you let somebody set a limit they start moving it. - LiveJournal user antonia_tiger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#455769: my experience
I have a thinkpad E520, I don't use GNOME, I use KDE but I run my own power manager written in python (long story). Anyway, to get the events my script reads from /var/run/acpid.socket, and sometimes I have the same problem, so I guess this rules out gnome/kde completely? On a side note, it is a well known and common problem of laptops that sometimes they do that, the same problem was also reported on macbook pro using osX. Users are supposed to *check* before they put the laptop in the bag. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Bug#704134: libnet-http-perl: SSL broken for some servers
Package: libnet-http-perl Version: 6.03-2 I use LWP::UserAgent and observed very bad performance with https. I finally found the fix here (already fixed on CPAN): https://rt.cpan.org/Public/Bug/Display.html?id=81073 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696564: unblock: fusioninventory-agent/2.2.3-5
On Tue, Mar 26, 2013 at 04:17:00PM +0100, Gonéri Le Bouder wrote: Hi, -7 looks fine in principle. Please upload it with urgency=medium so it can get a final review. The package has been uploded. I'm sorry not to have spotted it earlier, but this change in prerm: +# remove the configuration file itself +rm -f /etc/fusioninventory/agent.cfg +rm -r /etc/fusioninventory Apart from the redundancy, what happens if the directory isn't there? Won't the purge abort? -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits signature.asc Description: Digital signature
Bug#704136: lintian: treat git-dch --snapshot packages as local packages to avoid NMU warnings
Package: lintian Version: 2.5.10.4 Severity: wishlist The jenkins-debian-glue uses git-dch --snapshot to increase the version number before building. Unfortunately it also changes the email address in the topmost changelog entry, so lintian believes such a package to be a NMU. Now lintian already has some logic to avoid this for local packages. I'd like lintian to tread git-dch --snapshot packages the same. A typical changelog looks like his: $package ($origversion~$unixseconds~1.gbp$abbrevcommitid) … ** SNAPSHOT build @$longcommitid ** $origchangelog -- $changedmaintainer I suggest to also set the $changelog_mentions_local variable in checks/nmu if the first line contains the words /\bsnapshot\s+build\b/i. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690367: problem with wheezy fresh install
Carsten - Sorry don't know what you mean by top posting. I don't have icedove. But for me the issue is resolved since installing Wheezy RC1. I checked there are no l10n packages installed on my end. Perhaps they were being installed by default and are no longer installed by default. I cannot confirm regarding icedove.
Bug#455769: same problem on wheezy + Thinkpad X220T
On 28/03/13 12:32, Wouter Verhelst wrote: On 28-03-13 11:47, Daniel Pocock wrote: On 28/03/13 11:06, Julien Cristau wrote: Control: severity -1 important I am raising this bug to critical, as it meets the definition makes unrelated software on the system (or the whole system) break No, it does not. hw will shut itself off before getting damaged. Would you provide a guarantee to all users of wheezy that you will pay for their laptop repair if this issue causes damage? Oh please. I've never seen a laptop that will not cause a poweroff in hardware if the operating system isn't doing its job. I agree laptops usually power down by themselves (my old X60 did that many times even with lid open) - it is just not something that we should fall back on to downgrade a bug severity This is also not a critical issue. If gnome-power-manager were to go berserk and do the equivalent of rm -rf /, or kill -9 on all processes on the system, or something similar, that would be a critical bug in the makes the whole system break sense. As it is, gnome-power-manager just *doesn't* do something it's supposed to do. It's not even close to being critical in that sense. The severity guidelines don't say whether the definition of `system' includes hardware. A broad definition of system could include the backpack carrying the laptop, and the bottle of wine that heats up because it is in there with the laptop. Some organisations have multiple metrics for each bug, e.g. an impact metric to measure how many users suffer. Non-technical users are likely to suffer and have a bad impression of Debian when their laptop heats up in their backpack. I agree that it's probably a problem, and that it'd be good if we were to fix it before the release; but anything above important strikes me as unnecessary severity inflation. (on a more personal note, why oh why would you ever want the system to suspend when you close the lid? That's what a suspend button is for. If my laptop is compiling something, I do *not* want it to suspend when I close the lid, thankyouverymuch. Oh well) a) many users expect that - I'm thinking about it from the perspective of people who don't compile things and aren't actively involved in this list b) it is the Gnome way apparently: https://help.gnome.org/users/gnome-help/3.3/power-closelid.html.en and these are more specific: http://justinstories.wordpress.com/2011/09/15/ready-for-gnome-3-2-no-more-suspend-on-laptop-lid-close/ http://blogs.gnome.org/hughsie/2011/02/02/is-gnome-3-going-to-melt-your-laptop/ In wheezy, the power control panel does not give the user the option to change this behavior and the user must use gsettings to request anything other than suspend when lid closes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700169: non-free license: requires to obey US export regulation even, when not in the US
Hi Mattia, Mattia Dongili malat...@debian.org writes: I don't see a valid reason to get a newer version in wheezy at this stage of the freeze. I agree. Adam, here is the diffstat between the version currently in wheezy (upstream git commit f07ee8aa562b7cee0138a88219169f501fd9c041) and the version which is in the NEW queue (upstream commit 4fddab2e860aa7e14bd543aef6ed808be4b04aa2): git clone git://github.com/acpica/acpica.git cd acpica git diff --stat f07ee8aa562b7cee0138a88219169f501fd9c041..4fddab2e860aa7e14bd543aef6ed808be4b04aa2 … 1694 files changed, 109757 insertions(+), 45915 deletions(-) Can we just ignore this bug for wheezy? To me, the licensing intention seems very clear. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704137: /usr/bin/update-manager: update-manager only starts when run as root or with sudo
Package: update-manager-gnome Version: 0.200.5-2.1 Severity: important File: /usr/bin/update-manager Hello, according on how I run update-manager, it actually starts, works well, and returns success after quitting, or it just exits with a nonzero return value: $ gksu -k update-manager; echo $? 1 $ gksu update-manager; echo $? 1 $ sudo update-manager; echo $? 0 $ gksudo update-manager; echo $? 0 $ update-manager; echo $? 1 I suppose just update-manager by default runs gksu, because it asks for the password then quits with an error. This means that the launcher icon for update-manager on this system is currently nonfunctional, and it needs to be run by hand with sudo from a terminal. Ciao, Enrico -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages update-manager-gnome depends on: ii gconf2 3.2.5-1+build1 ii gksu 2.0.2-6 ii python 2.7.3-4 ii python-dbus 1.1.1-1 ii python-gconf 2.28.1+dfsg-1 ii python-gobject 3.2.2-2 ii python-gtk2 2.24.0-3+b1 ii python-support 1.0.15 ii python-vte 1:0.28.2-5 ii update-manager-core 0.200.5-2.1 update-manager-gnome recommends no packages. Versions of packages update-manager-gnome suggests: ii software-properties-gtk 0.82.7.1debian1 ii update-notifier 0.99.3debian11 -- no debconf information Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: codename 'rc-buggy' not handled correctly
On Thu, Mar 28, 2013 at 11:56:52 +0100, Martin Zobel-Helas wrote: Hi, On Thu Mar 28, 2013 at 11:21:29 +0100, Julien Cristau wrote: On Thu, Mar 28, 2013 at 11:02:11 +0100, Martin Zobel-Helas wrote: Putting debian-devel@l.d.o on CC for this bug report, as this change might have larger impact on installations, so discussing this first might be a good idea. rc-buggy is not a codename, it's a bad joke. Don't use it? well, removing it now that it is already used will also break installations, so i would suggest we make it a codename now. What makes you think it's used? The codename for experimental is experimental, and changing that would also break stuff... Cheers, Julien signature.asc Description: Digital signature
Bug#704138: No disk drive was detected during install
Package: installation-reports Boot method: How did you boot the installer? CD? floppy? network? Network/ pxe boot Image version: Full URL to image you downloaded is best http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/ Date: Date and time of the install March 28, 2013 Machine: Description of machine (eg, IBM Thinkpad R32) Custom build Processor: i3-2120 lspci Memory: Partitions: df -Tl will do; the raw partition table is preferred Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0100] (rev 09 Subsystem: Intel Corporation Device [8086:2017] 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09 Subsystem: Intel Corporation Device [8086:2017] 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04 Subsystem: Intel Corporation Device [8086:2017] 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 05 Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Co00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0100] (rev 09 Subsystem: Intel Corporation Device [8086:2017] 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09 Subsystem: Intel Corporation Device [8086:2017] 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04 Subsystem: Intel Corporation Device [8086:2017] 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 05 Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 05 Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: ehci hcd 00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 05 Subsystem: Intel Corporation Device [8086:2017] 00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b5 Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 05 Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: ehci hcd 00:1f.0 ISA bridge [0601]: Intel Corporation Cougar Point LPC Controller [8086:1c5c] (rev 05 Subsystem: Intel Corporation Device [8086:2017] 00:1f.2 SATA controller [0106]: Intel Corporation Cougar Point 6 port SATA AHCI Controller [8086:1c02] (rev 05 Subsystem: Intel Corporation Device [8086:2017] 00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 05 Subsystem: Intel Corporation Device [8086:2017] 01:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8892] (rev 30 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [-] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Tried pxe install using netinst and 6.0.7 cd image. Detect disks fail with : No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list. Tried on two similar systems, one with raw disk without any FS and no partitions, another with a vfat partition. It failed with both. (Seagate Barracuda 500 GB SATA) /var/log/syslog says: hw-detect:Loading PCMCIA bridge driver module: i82365 FATAL:Module i82365 not found check-missing-firmware: no missing firmware .. related board: http://kmuto.jp/debian/hcl/Intel/Desktop+Boards+DH61WW/ regards Anshu Prateek
Bug#704139: zynaddsubfx -U or --no-gui parameter doesn't seem to work, I get Can't Open Display: error
Package: zynaddsubfx Version: 2.4.3-3 Severity: important Dear Maintainer, I have just compiled and installed ZynAddSubFx, It returns an error with --no-gui option. zynaddsubfx --no-gui -Ialsa -Oalsa -L /usr/share/zynaddsubfx/banks/Organ/0001-Organ\ 1.xiz ZynAddSubFX - Copyright (c) 2002-2011 Nasca Octavian Paul and others Compiled: Mar 28 2013 00:51:07 This program is free software (GNU GPL v.2 or later) and it comes with ABSOLUTELY NO WARRANTY. Sample Rate = 44100 Sound Buffer Size = 256 samples Internal latency = 5.8 ms ADsynth Oscil.Size =1024 samples Instrument file loaded. Starting Audio: ALSA Audio Started Starting MIDI: ALSA MIDI Started Can't open display: -- System Information: Debian Release: 7.0 Architecture: armhf (armv6l) Kernel: Linux 3.6.11+ (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zynaddsubfx depends on: ii libasound21.0.25-4 ii libc6 2.13-38+rpi2 ii libfftw3-33.3.2-3.1 ii libfltk1.11.1.10-14 ii libgcc1 1:4.7.2-5+rpi1 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libglu1-mesa [libglu1]8.0.5-3 ii libice6 2:1.0.8-2 ii libjack0 [libjack-0.116] 1:0.121.3+20120418git75e3e20b-2.1 ii liblo70.26~repack-7 ii libmxml1 2.6-2 ii libsm62:1.2.1-2 ii libstdc++64.7.2-5+rpi1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii zlib1g1:1.2.7.dfsg-13 zynaddsubfx recommends no packages. zynaddsubfx 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#704020: gcc-4.8: FTBFS on hppa
Am 28.03.2013 13:02, schrieb John David Anglin: On 28-Mar-13, at 1:25 AM, Matthias Klose wrote: Am 26.03.2013 23:14, schrieb Dave Anglin: Package: gcc-4.8 Version: 4.8.0-1 Severity: normal There is a config problem building the hppa64 package: David, I'm applying this patch, however I don't see much sense anymore in having a current compiler without at least an unstable chroot. Back in Jan/Feb I did ask about the state of it, asked Aurelian to re-send open issues about ports.debian.org, but didn't get any reply. Thanks for applying the patch and trying to query Aurelian. therese seems to be a misunderstanding. Please look for an email to you sent on 2013-02-06, subject: [aurel...@aurel32.net: Re: hppa unstable buildd] referring to open questions mentioned in https://lists.debian.org/debian-hppa/2011/04/msg00026.html forwarding this email again to you and Helge this time. Regarding ports, I also never got any replies. Helge Deller and myself would still like to get a hppa buildd going. Had a couple of emails with Bdale on the subject. It appears that it may be possible to setup a wanna build server outside Debian although Helge favours using the existing Debian setup. Helge has setup a package upload system to parisc-linux.org. So, to access the packages that we have, one just has to add the following to /etc/apt/sources.list: deb ftp://ftp.de.debian.org/debian-ports unstable main deb ftp://ftp.parisc-linux.org/debian-ports/unstable unstable main There are a thousand or so packages there. Uploaded gcc-4.8 package set last night. Dave -- John David Anglindave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: codename 'rc-buggy' not handled correctly
Hi, On Thu Mar 28, 2013 at 14:32:12 +0100, Julien Cristau wrote: On Thu, Mar 28, 2013 at 11:56:52 +0100, Martin Zobel-Helas wrote: Hi, On Thu Mar 28, 2013 at 11:21:29 +0100, Julien Cristau wrote: On Thu, Mar 28, 2013 at 11:02:11 +0100, Martin Zobel-Helas wrote: Putting debian-devel@l.d.o on CC for this bug report, as this change might have larger impact on installations, so discussing this first might be a good idea. rc-buggy is not a codename, it's a bad joke. Don't use it? well, removing it now that it is already used will also break installations, so i would suggest we make it a codename now. What makes you think it's used? My grep on access logs on ftp.d.o mirrors. -- Martin Zobel-Helas zo...@debian.orgDebian System Administrator Debian GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704140: lynx-cur: lynx ignores encoding from meta for the title if title appears before in the HTML file
Package: lynx-cur Version: 2.8.8dev.15-2 Severity: normal In a HTML file, if the UTF-8 encoding is specified only with a meta line that appears after the title, e.g. titleTitle with entity (#233;) and UTF-8 (é)/title meta http-equiv=Content-Type content=text/html; charset=UTF-8 in an HTML file (see attachment[*]), then this encoding is not taken into account for the title. The title appears as: Title with entity (é) and UTF-8 (é) The body is not affected. Note: The HTML4 spec says META declarations should appear as early as possible in the HEAD element. but that's only a should, and it seems that there's nothing like that in the current HTML5 draft. [*] I've used the application/octet-stream MIME type to avoid automatic charset conversion by Mutt. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lynx-cur depends on: ii libbsd0 0.4.2-1 ii libbz2-1.01.0.6-4 ii libc6 2.13-38 ii libgcrypt11 1.5.0-5 ii libgnutls26 2.12.20-5 ii libidn11 1.25-2 ii libncursesw5 5.9-10 ii libtinfo5 5.9-10 ii zlib1g1:1.2.7.dfsg-13 Versions of packages lynx-cur recommends: ii mime-support 3.52-2 lynx-cur suggests no packages. -- debconf information: lynx-cur/defaulturl: http://www.lip.ens-lyon.fr/ lynx-cur/etc_lynx.cfg: lynx-title.html Description: Binary data
Bug#666877: it is working with older cups
2013/3/28 Brian Potkin claremont...@gmail.com: Are you still on 1.5.2-5 or have you progessed to the packages in testing or unstable? If so, how are you going on with printing? I'm on 1.5.3-5 now and printing is working fine now. -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688571: bash: [l10n:de] Error in German translation
Hello Nils et al., Am 27.03.2013 12:02, schrieb Helge Kreutzmann: Hallo Nils, On Sun, Mar 03, 2013 at 08:27:03PM +0100, Nils Naumann Die korrigierte Version befindet sich seit geraumer Zeit upstream: http://translationproject.org/PO-files/de/bash-4.2.de.po In English: The corrected version is upstream for a quite long time already. Unfortunately inclusion in Wheezy is no longer possible, at least not during the freeze. Matthias, could you ship the corrected version in case you make an stable upload during the lifetime of Wheezy? Thanks! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#693921: fails to resolve gnome-shell/experimental dependencies
Any update on this? It also affects gnome-shell/experimental now. + totem and gnome-contacts right now. There are several others I have FAIL-ed in wanna-build before as well Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704025: olsrd does not connect with others on amd64
found 704025 0.6.3-5 thanks According to the discussion [1], the version in unstable is affected as well. Therefore tagging the bug report as such. I just did the NMU for testing, would also do it for unstable by packaging upstream 0.6.4 if no one steps up. Will file an unblock request now first. Cheers, Adrian [1] https://lists.olsr.org/pipermail/olsr-dev/2013-March/006718.html -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
Package: cheese Version: 3.4.2-2 Followup-For: Bug #696727 I didn’t use Cheese before, but to test this bug I installed cheese from wheezy on my machine (which is running mostly experimental GNOME), and it segfaults. A full gdb stacktrace is attached. -- Dmitry Shachnev -- System Information: Debian Release: 7.0 APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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/dash Versions of packages cheese depends on: ii cheese-common 3.4.2-2 ii gnome-video-effects 0.4.0-1 ii libc6 2.13-38 ii libcanberra-gtk3-00.28-6 ii libcheese-gtk21 3.4.2-2 ii libcheese33.4.2-2 ii libclutter-1.0-0 1.13.10-1 ii libclutter-gtk-1.0-0 1.4.4-2 ii libgdk-pixbuf2.0-02.28.0-1 ii libgee2 0.6.4-2 ii libglib2.0-0 2.36.0-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgstreamer0.10-00.10.36-1.1 ii libgtk-3-03.8.0-1 Versions of packages cheese recommends: ii gnome-icon-theme3.7.91-1 ii gvfs1.12.3-4 ii hicolor-icon-theme 0.12-1 pn nautilus-sendto none ii yelp3.4.2-1+b1 cheese suggests no packages. -- no debconf information (gdb) run Starting program: /usr/bin/cheese [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [New Thread 0xb3923b70 (LWP 20056)] (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkGrid to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkLabel [New Thread 0xb30edb70 (LWP 20057)] Program received signal SIGSEGV, Segmentation fault. 0xb6cef18e in cogl_onscreen_add_frame_callback (onscreen=0x8571198, callback=callback@entry=0xb7d4f340 frame_cb, user_data=user_data@entry=0x83f1c80, destroy=destroy@entry=0) at ./cogl-onscreen.c:370 370 ./cogl-onscreen.c: No such file or directory. (gdb) bt full #0 0xb6cef18e in cogl_onscreen_add_frame_callback (onscreen=0x8571198, callback=callback@entry=0xb7d4f340 frame_cb, user_data=user_data@entry=0x83f1c80, destroy=destroy@entry=0) at ./cogl-onscreen.c:370 closure = 0x8566580 #1 0xb7d502f8 in clutter_stage_cogl_realize (stage_window=0x83f1c80) at ./cogl/clutter-stage-cogl.c:163 stage_cogl = 0x83f1c80 backend = optimized out framebuffer = optimized out error = 0x0 #2 0xb7d49c7f in clutter_stage_x11_realize (stage_window=0x83f1c80) at ./x11/clutter-stage-x11.c:609 stage_x11 = 0x83f1c80 stage_cogl = 0x83f1c80 backend = 0x8087800 backend_x11 = 0x8087800 device_manager = optimized out event_flags = optimized out width = 682 height = 450 #3 0xb7dd0573 in _clutter_stage_window_realize (window=0x83f1c80) at ./clutter-stage-window.c:88 No locals. #4 0xb7dc989d in clutter_stage_realize (self=0x84f17f0) at ./clutter-stage.c:761 priv = optimized out is_realized = optimized out #5 0xb755628a in g_cclosure_marshal_VOID__VOIDv (closure=0x84f04e0, return_value=0x0, instance=0x84f17f0, args=0xbfffe72c \241\062C\267\364?T\267@\nW\b\001, marshal_data=0xb7dc9850, n_params=0, param_types=0x0) at /tmp/buildd/glib2.0-2.36.0/./gobject/gmarshal.c:115 cc = 0x84f04e0 data1 = optimized out data2 = 0x84eb4a0 callback = 0xb7dc9850 clutter_stage_realize #6 0xb7552df7 in g_type_class_meta_marshalv (closure=closure@entry=0x84f04e0, return_value=return_value@entry=0x0, instance=instance@entry=0x84f17f0, args=args@entry=0xbfffe72c
Bug#704141: liballegro5.0: upstream has upgraded to allegro 5.1.6, can somebody package it.
Package: liballegro5.0 Version: 2:5.0.9-1 Severity: wishlist Dear Maintainer, Liballegro has been updated/upgraded to allegro 5.1.6, can somebody package it. http://sourceforge.net/projects/alleg/files/allegro-unstable/5.1.6/allegro-5.1.6.tar.gz/ This version is needed to play the game Eruta https://github.com/beoran/eruta -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (10, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liballegro5.0 depends on: ii libc6 2.17-0experimental2 ii libgl1-mesa-glx [libgl1] 8.0.5-4 ii libx11-6 2:1.5.0-1 ii libxcursor1 1:1.1.13-1 ii libxinerama1 2:1.1.2-1 ii libxrandr22:1.4.0-1 ii multiarch-support 2.17-0experimental2 liballegro5.0 recommends no packages. liballegro5.0 suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
On Thu, Mar 28, 2013 at 10:21:30AM +, Jonathan Dowland wrote:
UI (No device found). Interesting stuff. I'm going to try splicing some
debug statements into the code to see at what point it reaches and whether
that helps get any further.
I've poked around a little, attached is a backtrace taken when interrupting the
spinning process. It shows the last routine executed in cheese code as
cheese_camera_play. Poking around in the C,
cheese_camera_play (CheeseCamera *camera)
{
…
gst_element_set_state (priv-camerabin, GST_STATE_PLAYING);
^^
That's as far as cheese gets. So, is this a gstreamer bug? (or
gstreamer0.10-plugins-bad)? Seems it uses 'camerabin', which has been
deprecated in favour of 'camerabin2' in gst 0.10, and dropped by 1.0.
Cheese moved to camerabin2 between 3.5.5 and 3.5.091.
#0 type_check_is_value_type_U (type=optimized out)
at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:4098
#1 g_type_check_value (value=value@entry=0x1dddfb0)
at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:4140
#2 0x77769d9c in gst_value_init_and_copy (dest=0x1e33520,
src=0x1dddfb0) at gstvalue.c:4007
#3 0x7776a03f in copy_garray_of_gstvalue (
src=error reading variable: Unhandled dwarf expression opcode 0xfa,
src=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:230
#4 0x7776a130 in gst_value_copy_list_or_array (src_value=optimized
out,
dest_value=0x7fffd8b0) at gstvalue.c:241
#5 0x7776d35f in gst_value_list_append_value
(value=value@entry=0x7fffd970,
append_value=append_value@entry=0x7fffd8f0) at gstvalue.c:314
#6 0x7776da4b in gst_value_intersect_list (dest=0x7fffd970,
value2=0x1a40460,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2752
#7 0x7776d999 in gst_value_intersect_list (dest=0x7fffd9f0,
value2=0x1a40460,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#8 0x7776d999 in gst_value_intersect_list (dest=0x7fffda70,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#9 0x7776d999 in gst_value_intersect_list (dest=0x7fffdaf0,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#10 0x7776d999 in gst_value_intersect_list (dest=0x7fffdb70,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#11 0x7776d999 in gst_value_intersect_list (dest=0x7fffdbf0,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#12 0x77750a73 in gst_structure_intersect_field1 (id=3915,
val1=0x1a3d4a8, data=0x7fffdc60)
at gststructure.c:2981
#13 0x77750fc1 in gst_structure_foreach (structure=0x1a5fb90,
func=0x77750a20 gst_structure_intersect_field1,
user_data=0x7fffdc60) at gststructure.c:1097
#14 0x77753c00 in gst_structure_intersect
(struct1=struct1@entry=0x1a5fb90, struct2=0x1c88330)
at gststructure.c:3030
#15 0x7770f3a4 in gst_caps_intersect_first (caps2=0x19d1e80,
caps1=0x198ce40) at gstcaps.c:1423
#16 gst_caps_intersect_full (caps1=caps1@entry=0x198ce40,
caps2=caps2@entry=0x19d1e80,
mode=mode@entry=GST_CAPS_INTERSECT_FIRST) at gstcaps.c:1454
#17 0x7fffefff4c94 in gst_base_transform_getcaps (pad=0x19c9d90) at
gstbasetransform.c:768
#18 0x7772cf96 in gst_pad_get_caps_unlocked (pad=pad@entry=0x19c9d90)
at gstpad.c:2254
#19 0x777305b5 in gst_pad_get_caps_reffed (pad=pad@entry=0x19c9d90) at
gstpad.c:2338
#20 0x7776148b in gst_element_get_compatible_pad
(element=element@entry=0x1b8e240,
pad=pad@entry=0x19c9d90, caps=caps@entry=0x0) at gstutils.c:1146
#21 0x7776216a in gst_element_link_pads_full (src=src@entry=0x1a16090,
srcpadname=srcpadname@entry=0x0, dest=dest@entry=0x1b8e240,
destpadname=destpadname@entry=0x0,
flags=flags@entry=GST_PAD_LINK_CHECK_CAPS) at gstutils.c:1799
#22 0x7fffe16020ea in gst_camerabin_try_add_element
(bin=bin@entry=0x196e020,
new_elem=new_elem@entry=0x1b8e240) at camerabingeneral.c:99
#23 0x7fffe160228f in gst_camerabin_add_element (bin=bin@entry=0x196e020,
new_elem=new_elem@entry=0x1b8e240) at camerabingeneral.c:56
#24 0x7fffe160247d in gst_camerabin_create_and_add_element
(bin=bin@entry=0x196e020,
elem_name=optimized out, elem_name@entry=0x7fffe16043fd videoscale,
instance_name=instance_name@entry=0x7fffe16043f9 src-videoscale) at
camerabingeneral.c:146
#25 0x7fffe15f67a0 in camerabin_create_src_elements (camera=0x196e020) at
gstcamerabin.c:623
#26 camerabin_create_elements (camera=0x196e020) at gstcamerabin.c:779
#27 gst_camerabin_change_state (element=0x196e020,
Bug#704142: iceweasel: Doodle not working anymore
Package: iceweasel Version: 10.0.12esr-1 Severity: normal Dear all, I have problems with www.doodle.com: Focus is lost in text fields so I cannot enter any text. Problem is reproducible just try to enter text at http://doodle.com/rbidiqkgvv5ma5g5 I cannot enter any text there, can you? Chromium works for the same site. Problem is reproducible on other machine's iceweasels. Problem did not go away when starting in safe-mode Best, Jürgen -- Package-specific info: -- Addons package information -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iceweasel depends on: ii debianutils 4.3.2 ii fontconfig 2.9.0-7.1 ii libc6 2.13-38 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libnspr42:4.9.2-1 ii libnspr4-0d 2:4.9.2-1 ii libsqlite3-03.7.13-1 ii libstdc++6 4.7.2-5 ii procps 1:3.3.3-2 ii xulrunner-10.0 10.0.12esr-1 iceweasel recommends no packages. Versions of packages iceweasel suggests: ii fonts-stix [otf-stix] 1.1.0-1 ii libgssapi-krb5-2 1.10.1+dfsg-4+nmu1 pn mozplugger none Versions of packages xulrunner-10.0 depends on: ii libasound21.0.25-4 ii libatk1.0-0 2.4.0-2 ii libbz2-1.01.0.6-4 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100.2-1 ii libevent-2.0-52.0.19-stable-3 ii libfontconfig12.9.0-7.1 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.7.2-5 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8d-1 ii libmozjs10d 10.0.12esr-1 ii libnotify40.7.5-1 ii libnspr4-0d 2:4.9.2-1 ii libnss3-1d2:3.14.3-1 ii libpango1.0-0 1.30.0-1 ii libpixman-1-0 0.26.0-4 ii libreadline6 6.2+dfsg-0.1 ii libsqlite3-0 3.7.13-1 ii libstartup-notification0 0.12-1 ii libstdc++64.7.2-5 ii libvpx1 1.1.0-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxrender1 1:0.9.7-1 ii libxt61:1.1.3-1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages xulrunner-10.0 suggests: ii libcanberra0 0.28-6 ii libgnomeui-0 2.24.5-2 -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#691191: rspec-rails is packaged now
Hi Nandaja, rspec-rails 2.10.1 is packaged and new (it available in boutil's repo - http://people.debian.org/~boutil/diaspora/README). Option 1: You may try an older version of cucumber-rails compatible with the rspec and rspec-rails versions in unstable. Option 2: Jeremy has uploaded newer version of rspec in experimental and I will try to update rspec-rails as well. You may directly target experimental too once I'm able to upload a newer rspec-rails package there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704124: codename 'rc-buggy' not handled correctly
On Thu, Mar 28, 2013 at 02:41:36PM +0100, Martin Zobel-Helas wrote: What makes you think it's used? My grep on access logs on ftp.d.o mirrors. But as you see, it's not actually useable and shows that warning. It was a joke that was never announced, to keep the RT from picking the last name left in Toy Story 1. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#704079: Acknowledgement (ITP: libweakref-php5 -- Implementation of weak references for PHP 5)
Control: retitle -1 ITP: php5-weakref -- Implementation of weak references for PHP 5 On 27 March 2013 17:15, Debian Bug Tracking System ow...@bugs.debian.org wrote: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): w...@debian.org If you wish to submit further information on this problem, please send it to 704...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 704079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704143: unblock: olsrd/0.6.2-2.1
Package: release.debian.org
Severity: normal
Tags: patch
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
both olsrd 0.6.2-2 (testing) and 0.6.3-5 (unstable) suffer from
corrupted data on amd64 platforms [1].
I have performed NMUs both for testing-proposed-updates and unstable
and would like to have the version for t-p-u unblocked.
Attaching debdiff.
Adrian
unblock olsrd/0.6.2-2.1
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru olsrd-0.6.2/debian/changelog olsrd-0.6.2/debian/changelog
--- olsrd-0.6.2/debian/changelog 2012-02-19 16:18:18.0 +0100
+++ olsrd-0.6.2/debian/changelog 2013-03-28 04:31:12.0 +0100
@@ -1,3 +1,11 @@
+olsrd (0.6.2-2.1) testing-proposed-updates; urgency=low
+
+ * Non-maintainer upload.
+ * Include upstream patch to fix stack corruption in
+net output (Closes: #704025).
+
+ -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Thu, 28 Mar 2013 04:29:10 +0100
+
olsrd (0.6.2-2) unstable; urgency=low
* debian/control: Build-Depends: debhelper (= 9) (Closes: #658330)
diff -Nru olsrd-0.6.2/debian/patches/300-fix-stack-corruption-in-net-output.patch olsrd-0.6.2/debian/patches/300-fix-stack-corruption-in-net-output.patch
--- olsrd-0.6.2/debian/patches/300-fix-stack-corruption-in-net-output.patch 1970-01-01 01:00:00.0 +0100
+++ olsrd-0.6.2/debian/patches/300-fix-stack-corruption-in-net-output.patch 2013-03-28 04:27:03.0 +0100
@@ -0,0 +1,57 @@
+From f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba Mon Sep 17 00:00:00 2001
+From: Jo-Philipp Wich j...@openwrt.org
+Date: Fri, 22 Jun 2012 03:17:59 +0200
+Subject: [PATCH] olsrd: fix stack corruption in net_output()
+
+The net_output() function indirectly uses the stack variables dst and dst6
+outside of the scope they're declared in, this might leads to olsr_sendto()
+being called with a corrupted destination sockaddr_in.
+
+This failure condition can be observed in the log, olsrd will continuosly
+print sendto(v4): Invalid Argument or a similar message. On ARM it has been
+reported to result in Unsupported Address Family.
+
+This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
+Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
+target as well.
+
+The offending code seems to be unchanged since 2008 and it does not cause
+issues on 32bit systems and/or with older (Linaro) GCC versions, but the
+compiler used in our tests seems to perform more aggressive optimizations
+leading to a stack corruption.
+---
+ src/net_olsr.c |4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/net_olsr.c b/src/net_olsr.c
+index 7d85f4f..66e103d 100644
+--- a/src/net_olsr.c
b/src/net_olsr.c
+@@ -336,6 +336,8 @@ net_output(struct interface *ifp)
+ {
+ struct sockaddr_in *sin = NULL;
+ struct sockaddr_in6 *sin6 = NULL;
++ struct sockaddr_in dst;
++ struct sockaddr_in6 dst6;
+ struct ptf *tmp_ptf_list;
+ union olsr_packet *outmsg;
+ int retval;
+@@ -354,7 +356,6 @@ net_output(struct interface *ifp)
+ outmsg-v4.olsr_packlen = htons(ifp-netbuf.pending);
+
+ if (olsr_cnf-ip_version == AF_INET) {
+-struct sockaddr_in dst;
+ /* IP version 4 */
+ sin = (struct sockaddr_in *)ifp-int_broadaddr;
+
+@@ -365,7 +366,6 @@ net_output(struct interface *ifp)
+ if (sin-sin_port == 0)
+ sin-sin_port = htons(olsr_cnf-olsrport);
+ } else {
+-struct sockaddr_in6 dst6;
+ /* IP version 6 */
+ sin6 = (struct sockaddr_in6 *)ifp-int6_multaddr;
+ /* Copy sin */
+--
+1.7.9.5
+
diff -Nru olsrd-0.6.2/debian/patches/series olsrd-0.6.2/debian/patches/series
--- olsrd-0.6.2/debian/patches/series 2012-02-19 16:07:42.0 +0100
+++ olsrd-0.6.2/debian/patches/series 2013-03-28 04:27:57.0 +0100
@@ -6,3 +6,4 @@
270-gui-linux-gtk-align-olsr_ip_addr-to-olsr-definition-of-it.patch
280-fix-linux-gtk-build.patch
290-hardcode-etc-olsrd-olsrd-conf.patch
+300-fix-stack-corruption-in-net-output.patch
Bug#704132: mediathekview: Please fix StartupWMClass in desktop file
On 28.03.2013 13:01, Benjamin Drung wrote: Package: mediathekview Version: 3.1.0-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: * Fix StartupWMClass in desktop file. Otherwise Unity fails to associate the launched java process with the desktop file. Thanks for considering the patch. Thanks for the patch. My original intention was to clean the .desktop file from not strictly required keys like StartupNotify and StartupWMClass in the next release. Do you prefer your patch for StartupWMClass or can you live without the aforementioned keys on Unity, too? Regards, Markus signature.asc Description: OpenPGP digital signature
