Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 690081 grave Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'grave' from 'wishlist' tag 690081 +experimental Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Added tag(s) experimental. thanks Stopping processing here. Please contact me if you need assistance. -- 690081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
Package: debian-installer Version: wheezy Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I tried to do a clean install of wheezy i386 using my pxe boot server, as I allways do. * What exactly did you do (or not do) that was effective (or ineffective)? I switched mirrors to bypass this warnings: in-target: Warning! the following packages cannot be authenticated! busybox in-target:base-installer:error:exiting on error base-installer/kernel/failed- package-install * What was the outcome of this action? Switching mirrors got me past this problem, but caused new authentication problems down the road * What outcome did you expect instead? Cleanly finishing the installation. *** End of the template - remove these lines *** -- 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=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: update
I finaly have a working system, but I had to switch mirrors twice during installation. After the reboot, I still could not use my system. I had to remove debian-archive-keyring (witch is not allowed unless you force it to) and replace it with the proper one, reinstall apt, etc. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702087: UDD: vcs importer broken since PET moved to alioth
Hi, in the past I did some investigation into this and here is the status quo: In 2012-10, PET was migrated from a private machine to an Alioth machine. Since that migration, UDD (on ullmann.d.o) cannot access PET (on wagner.d.o) A solution consisting of adding the following entries into pg_hba.conf has been proposed [1]: # access as guest to pet from udd.debian.org hostpet guest 206.12.19.141/32trust hostpet guest 2607:f8f0:610:4000:6564:a62:ce0c:138d/128 trust but it turns out that this is only part of the proglem. The Alioth administrators have identified the root cause to be firewall rules implemented by the hosting partner hosting wagner.d.o. The Alioth administrators have contacted the hosting partner to seek modification of the firewall rules but do not know when the partner will execute the necessary modifications. It might make sense to consider different means to inject PET data into UDD than relying on the direct postgresql connection (some intermediate data file copied via rsync comes to mind.) The intention of this bug report it to record the existence of the connection problem between UDD and PET as it pertains to the QA project. Alternative solutions are welcome to be registered against this bug so that we may discuss them. Kind regards Andreas. [1] http://lists.debian.org/debian-qa/2012/10/msg00048.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703265: lletters: crashes on most buttons on non-OSS3 systems
On Mon, Mar 18, 2013 at 09:15:16PM +0100, Stephen Kitt wrote:
Hi,
On Mon, Mar 18, 2013 at 02:47:47PM +, Steven Chamberlain wrote:
On 17/03/13 19:35, Adam Borowski wrote:
On systems that don't have OSS installed and configured, pressing any
button that has an attached sound, causes a crash.
Another option might be to disable sound on Linux, then at least we'd
keep something that works.
Alternatively, oss-compat is supposed to be used by packages such as
this one with a requirement for OSS. Adam, could you try installing it
to see if the modules it sets up allow lletters to work? It may not
play all that nicely with pulseaudio...
Works, but only after a reboot (I tested on a Debian-provided kernel in a
fresh wheezy install as well, to be sure). Having to reboot just to check
out a simple child game is not nice.
For Jessie we'll have osspd, but oss-compat or disabling audio as
Steven suggested seem to me to be the only options for Wheezy.
Here's another solution:
Depends: sox
if (!fork())
{
const char* arg[4];
arg[0] = /usr/bin/play;
arg[1] = -q;
arg[2] = the_file_to_play;
arg[3] = 0;
execve(arg[0], arg, environ);
exit(127);
}
Works on all sound systems, doesn't crash if no sound is available, doesn't
hang on 64 bit architectures (and I guess big-endian too), supports formats
other than .wav (in case someone localizes sounds). And doesn't use that
ridiculous code with more leaks than ${SOME_MICROSOFT_SLUR}.
One could use, say, SDL_sound to avoid the fork(), but come on, let's be
serious.
--
ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703371: libharminv-dev: harminv build stale on i386
Le lundi 18 mars 2013 à 17:02 -0400, Andreas Kloeckner a écrit : Package: libharminv-dev Version: 1.3.1-8 Severity: grave Justification: renders package unusable It appears as though the harminv package has become unusable in i386. It refers to libcblas.3gf.so, which is no longer available in testing/unstable. Can you please provide the output of the following command: $ update-alternatives --display libblas.so.3 It looks like the i386 binary has been built on an non-minimal chroot, and was therefore linked against ATLAS. This creates missing shared library dependencies when the BLAS alternative does not point to ATLAS (which I guess is the case for the reporter). A binNMU of the package should fix the problem. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: This is a digitally signed message part
Bug#703411: file - Needs a decent test suite
Package: file Version: 5.11-2 Severity: serious The file package needs a decent test suite. The file command is used in several dpkg and debhelper tools to detect certain ELF attributes. Failure to detect ELF or internal errors results in broken binary packages. So file _must_ not fail to detect them. Bastian -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 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 file depends on: ii libc6 2.13-38 ii libmagic1 5.11-2 ii zlib1g 1:1.2.7.dfsg-13 file recommends no packages. file suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700620: [Openstack-devel] Bug#700620: Bug#700620: Bug#700620: Rewriting the .ini parsing bit of openstack-pkg-tools
On Tue, Mar 19 2013, Thomas Goirand wrote: Who's problem then? I don't know -- I'm not sure it's a even problem. Maybe dpkg's problem? I thought like you first. Then I realized that we have no choice but to implement something anyway, because the upstream library doesn't have a feature to actually write the configuration, it only can read it. That's a good point indeed. Still, I think it'd be better to contribute to oslo.config and add write support, which could even be useful to others, than hack something in Debian's corner. Well, if we're writing some debconf stuff, it is so it can be used. I don't believe it is reasonable to say bha... people are going to preseed anyway, so why should we care. I do care! Also, I believe that my final solution, based on regular expression, is easy to change if there was any trouble with the parsing. The fact that I use a unique logic to both read and write values also helps maintainability. As I said, I think you're wrong, but the decision is up to you anyway. :-) -- Julien Danjou // Free Software hacker / freelance consultant // http://julien.danjou.info pgpCwMFI2IsjY.pgp Description: PGP signature
Bug#678979: request freeze exception for slony1-2
user debian-rele...@packages.debian.org usertags 678979 wheezy-will-remove thanks On Sat, Mar 16, 2013 at 12:44:15PM -0400, Peter Eisentraut wrote: On Sat, 2013-03-16 at 11:38 +, Adam D. Barratt wrote: On Sun, 2012-10-07 at 14:30 +0200, Mehdi Dogguy wrote: On 21/09/2012 04:58, Peter Eisentraut wrote: According to bug #678979 [0], which was submitted by the lead upstream developer, slony 2.0 does not work well with postgresql 9.1. Therefore, we had to resolve to making an upgrade to slony version 2.1, and I request that that be allowed into wheezy now. [...] Unfortunately, we are not able to accept such large changes at this stage of the freeze. [2] Since slony in Debian have little popcon, does it make sense to skip the Wheezy release? iow, remove slony from wheezy (since it doesn't work and we are not able to accept the new one). Alternatively, we could very well accept a targeted fix based on current Wheezy's version… (correct me if I'm wrong), the discussion in #678979 made me think that it was not possible to extract a minimal patch. Ping? As far as I'm concerned, the matter is closed. The above doesn't actually help, as I generally don't like trying to read maintainers minds. In the absence of further action, I'm tagging this wheezy-will-remove. Neil -- signature.asc Description: Digital signature
Processed: Re: Bug#703371: libharminv-dev: harminv build stale on i386
Processing control commands: tags -1 + patch Bug #703371 [libharminv-dev] libharminv-dev: harminv build stale on i386 Added tag(s) patch. -- 703371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703371: libharminv-dev: harminv build stale on i386
Control: tags -1 + patch Le mardi 19 mars 2013 à 10:23 +0100, Sébastien Villemot a écrit : A binNMU of the package should fix the problem. Actually a Build-Conflicts is a more robust solution. The attached patch implements this. Thorsten: does that sound fine to you? I can do the upload if this helps. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 diff -Nru harminv-1.3.1/debian/changelog harminv-1.3.1/debian/changelog --- harminv-1.3.1/debian/changelog 2011-12-09 15:11:38.0 +0100 +++ harminv-1.3.1/debian/changelog 2013-03-19 11:06:34.0 +0100 @@ -1,3 +1,14 @@ +harminv (1.3.1-8.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * debian/control: add Build-Conflicts against libatlas-base-dev. If the +latter is installed, the build system detects and links against some +ATLAS-specific shared libraries. In turn, this makes libharminv.so +unusable when the BLAS alternative does not point to ATLAS. +(Closes: #703371). + + -- Sébastien Villemot sebast...@debian.org Tue, 19 Mar 2013 11:04:38 +0100 + harminv (1.3.1-8) unstable; urgency=low * debian/control: moved to dh 8 diff -Nru harminv-1.3.1/debian/control harminv-1.3.1/debian/control --- harminv-1.3.1/debian/control 2011-12-08 15:33:08.0 +0100 +++ harminv-1.3.1/debian/control 2013-03-19 11:06:51.0 +0100 @@ -6,6 +6,7 @@ autotools-dev, liblapack-dev, gfortran +Build-Conflicts: libatlas-base-dev Standards-Version: 3.9.2 Homepage: http://ab-initio.mit.edu/wiki/index.php/Harminv DM-Upload-Allowed: yes signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#703411: file - Needs a decent test suite
Processing commands for cont...@bugs.debian.org: retitle 703411 file: testsuite for readelf Bug #703411 [file] file - Needs a decent test suite Changed Bug title to 'file: testsuite for readelf' from 'file - Needs a decent test suite' tag 703411 upstream Bug #703411 [file] file: testsuite for readelf Added tag(s) upstream. severity 703411 wishlist Bug #703411 [file] file: testsuite for readelf Severity set to 'wishlist' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 703411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703415: code-aster{, -mpi}-engine: fails to install: code-aster-engine.postinst: cannot create /etc/codeaster/aster: Directory nonexistent
Package: code-aster-engine,code-aster-mpi-engine Version: 11.3.0-2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package code-aster-engine. (Reading database ... 8592 files and directories currently installed.) Unpacking code-aster-engine (from .../code-aster-engine_11.3.0-2-2_amd64.deb) ... Setting up code-aster-engine (11.3.0-2-2) ... + CODEASTER_VERSION=STA11.3 + pyversions -d + perl -pi -e s|python||g + dc_pyvers=2.7 + ln -sf /usr/lib/codeaster/STABLE/config-py2.7.txt /usr/lib/codeaster/STABLE/config.txt + ln -sf /usr/lib/codeaster/STABLE /usr/lib/codeaster/STA11.3 + ln -sf /var/lib/codeaster/STABLE /var/lib/codeaster/STA11.3 /var/lib/dpkg/info/code-aster-engine.postinst: 18: /var/lib/dpkg/info/code-aster-engine.postinst: cannot create /etc/codeaster/aster: Directory nonexistent + /usr/sbin/update-codeaster-engines dpkg: error processing code-aster-engine (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: code-aster-engine The missing directory should be shipped as an empty directory in the package s.t. dpkg will handle creation and removal. Don't forget to disable the set -x noise. cheers, Andreas code-aster-engine_11.3.0-2-2.log.gz Description: GNU Zip compressed data
Processed: Re: Bug#703290: davical: possible code insertion or XSS
Processing commands for cont...@bugs.debian.org: severity 703294 important Bug #703294 [src:davical] davical: fopen mess in caldav.php Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 703294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Tagging all -done bugs
Processing commands for cont...@bugs.debian.org:
user debian-rele...@packages.debian.org
Setting user to debian-rele...@packages.debian.org (was ne...@debian.org).
usertags 699848 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 678979 wheezy-will-remove
Usertags were: wheezy-will-remove.
Usertags are now: wheezy-will-remove.
usertags 702523 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 690500 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 677565 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 682353 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 674226 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 684855 wheezy-will-remove
There were no usertags set.
Usertags are now: wheezy-will-remove.
usertags 684645 wheezy-is-blocker
There were no usertags set.
Usertags are now: wheezy-is-blocker.
usertags 702131 wheezy-is-blocker
There were no usertags set.
Usertags are now: wheezy-is-blocker.
usertags 694352 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
usertags 700809 wheezy-is-blocker
There were no usertags set.
Usertags are now: wheezy-is-blocker.
usertags 696041 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
usertags 692053 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
tags 688792 wheezy-ignore
Bug #688792 {Done: Nicholas Bamber nicho...@periapt.co.uk} [mysql-server-5.5]
mysql-server-5.5: error in SQL syntax in postinst
Bug #692871 {Done: Nicholas Bamber nicho...@periapt.co.uk} [mysql-server-5.5]
mysql-server-5.5: Regression in privileges of mysql debian-sys-maint user
Added tag(s) wheezy-ignore.
Added tag(s) wheezy-ignore.
usertags 695001 wheezy-is-blocker
There were no usertags set.
Usertags are now: wheezy-is-blocker.
usertags 675462 wheezy-is-blocker
There were no usertags set.
Usertags are now: wheezy-is-blocker.
usertags 701868 wheezy-is-blocker
There were no usertags set.
Usertags are now: wheezy-is-blocker.
usertags 696642 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688792
692871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692871
696642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
I have exactly the same problem, as described. Is there away to specify (in preseeding) to skip installing busybox ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
19.03.2013 15:04, Konrad Vrba пишет: I have exactly the same problem, as described. Is there away to specify (in preseeding) to skip installing busybox ? Busybox is used in regular initramfs. While techincally initramfs might work without busybox, no one really test things that way. So basically you'll end up with unbootable system. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
On 3/19/13, Michael Tokarev m...@tls.msk.ru wrote: 19.03.2013 15:04, Konrad Vrba пишет: I have exactly the same problem, as described. Is there away to specify (in preseeding) to skip installing busybox ? Busybox is used in regular initramfs. While techincally initramfs might work without busybox, no one really test things that way. So basically you'll end up with unbootable system. /mjt I see, but custom kernel without initramfs should work. If there is a way to skip installing busybox, I would appreciate. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
19.03.2013 15:29, Konrad Vrba wrote: I see, but custom kernel without initramfs should work. If there is a way to skip installing busybox, I would appreciate. That appears to be a wrong solution to a wrong problem. Something is wrong with the archive mirror system apparently, or with the signing keys, I dunno for now. Any random package might be at fault here (what if it was one of the core packages, such as glibc?). The solution is to fix the network not avoid apparently broken (which are actually not broken) packages. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703419: release-notes: Need updating / finalising for wheezy
Package: release-notes Severity: serious User: release.debian@packages.debian.org Usertags: wheezy-is-blocker As $SUBJECT. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698955: xsltproc: symbol xsltMaxVars, version LIBXML2_1.0.24 not defined in file libxslt.so.1 reference
Package: libxslt1.1 Version: 1.1.27-1 Followup-For: Bug #698955 Hi, I also ran into this bug today. Looking at the sources (the git of the packaging), I see that the bug is probably due to an upstream mistake. Upstream introduce the xsltMaxVars symbol in 1.1.27 and (as it is related), it put it nearby the xsltMaxDepth in most files. And, in libxslt/libxslt.syms, this is probably an error. It should go into the new LIBXML2_1.1.27 instead of the old LIBXML2_1.0.24 section. As the Debian packaging uses the upstream versionning to class all symbols (relying on a good upstream pratice), in this case, it fails. The bug should probably be quickly forwarded upstream so that they can fix this if they want (but, if they just correct the mistake, they will need to bump the soname when they remove the xsltMaxVars@LIBXML2_1.0.24 symbol). They can also choose to correct the mistake but still provide the xsltMaxVars@LIBXML2_1.0.24 symbol to keep binary compatibility (and avoid soname bump) On the Debian side, the xsltMaxVars symbol must be handle manually (ie explicitly, not relying on wildcard and/or symver option) in the debian/libxslt1.1.symbols file to mark this symbols as coming from 1.1.27. And all reverse dependencies must be rebuilt if they have been built against libxslt-dev 1.1.27-1. = the quicker the correction and upload is done, the lesser number of packages you will have to ask for rebuild. Regards, Vincent -- 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 armel mipsel Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxslt1.1:amd64 depends on: ii libc6 2.17-0experimental2 ii libgcrypt111.5.0-5 ii libxml22.8.0+dfsg1-7+nmu1 ii multiarch-support 2.13-38 libxslt1.1:amd64 recommends no packages. libxslt1.1:amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [xml/sgml-pkgs] Bug#698955: xsltproc: symbol xsltMaxVars, version LIBXML2_1.0.24 not defined in file libxslt.so.1 reference
Processing commands for cont...@bugs.debian.org: forwarded 698955 https://bugzilla.gnome.org/show_bug.cgi?id=696136 Bug #698955 [xsltproc] xsltproc: symbol xsltMaxVars, version LIBXML2_1.0.24 not defined in file libxslt.so.1 reference Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=696136'. End of message, stopping processing here. Please contact me if you need assistance. -- 698955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703423: colord: unbuildable on !linux archs
Source: colord
Version: 0.1.31-1
Severity: serious
Tags: patch
Justification: fails to build from source
Hi,
the new colord 0.1.31-1 cannot be built on non-Linux archs because of
the libsystemd-login-dev B-D (built from systemd, which is
Linux-specific).
Other than that, there are other issues, which my patch fixes in
(I hope) a clean way:
- as said already, limit the libsystemd-login-dev B-D as linux-any
- gusb and systemd-login are Linux-specific, so explicitly enable or
disable them on Linux archs or not
- since the udev directory cannot be detected, on non-Linux archs the
installation path of the udev rules would result as /rules.d.
To avoid this, I've explicitly set the udevdir to configure (also on
Linux); of course, if this seems notdesiderable, the udevdir can be
passed only on non-Linux archs
- the colorhug stuff depends on gusb, so all the colorhug packages are
now linux-any instead of any
- there seem to be no colord-plugins compiled, so its line in
colord.install would result in a dh_install error; I've grouped it
with the colord-sensors line that follows in that .install file,
I hope it is not too generic now
Thanks,
--
Pino
--- a/debian/control
+++ b/debian/control
@@ -21,7 +21,7 @@ Build-Depends:
dh-autoreconf,
gtk-doc-tools,
autopoint,
- libsystemd-login-dev,
+ libsystemd-login-dev [linux-any],
Standards-Version: 3.9.4
XS-Testsuite: autopkgtest
Section: graphics
@@ -101,7 +101,7 @@ Description: GObject introspection data
Package: libcolorhug-dev
Section: libdevel
-Architecture: any
+Architecture: linux-any
Depends:
libcolorhug1 (= ${binary:Version}),
libglib2.0-dev,
@@ -119,7 +119,7 @@ Description: library to access the Color
Package: libcolorhug1
Section: libs
-Architecture: any
+Architecture: linux-any
Depends:
${shlibs:Depends},
${misc:Depends},
@@ -135,7 +135,7 @@ Description: library to access the Color
Package: gir1.2-colorhug-1.0
Section: introspection
-Architecture: any
+Architecture: linux-any
Depends: ${gir:Depends},
${shlibs:Depends},
${misc:Depends}
--- a/debian/rules
+++ b/debian/rules
@@ -21,12 +21,13 @@ confflags = \
--disable-volume-search \
--with-daemon-user=colord \
--with-systemdsystemunitdir=/lib/systemd/system \
+ --with-udevrulesdir=/lib/udev/rules.d \
--enable-vala
ifeq ($(DEB_HOST_ARCH_OS),linux)
- confflags += --enable-gudev --enable-sane
+ confflags += --enable-gudev --enable-sane --enable-gusb --enable-systemd-login
else
- confflags += --disable-gudev --disable-sane
+ confflags += --disable-gudev --disable-sane --disable-gusb --disable-systemd-login
endif
override_dh_auto_configure:
--- a/debian/colord.install
+++ b/debian/colord.install
@@ -2,8 +2,7 @@ debian/tmp/etc/
lib/udev/rules.d/
usr/bin/
usr/lib/colord*
-usr/lib/*/colord-plugins
-usr/lib/*/colord-sensors
+usr/lib/*/colord-*
usr/share/color
usr/share/colord
usr/share/glib-2.0/schemas
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
19.03.2013 15:29, Konrad Vrba wrote: I see, but custom kernel without initramfs should work. If there is a way to skip installing busybox, I would appreciate. That appears to be a wrong solution to a wrong problem. Something is wrong with the archive mirror system apparently, or with the signing keys, I dunno for now. Any random package might be at fault here (what if it was one of the core packages, such as glibc?). The solution is to fix the network not avoid apparently broken (which are actually not broken) packages. Thanks, /mjt Hello, I've got the exact same problem when installing Wheezy on a virtual machine powered by KVM on a Wheezy host. What's strange is that the physical host installation works fine (using a bootable net-install USB key), no busybox installation failure whatsoever. I use KVM and libvirt packages shipped with debian wheezy and create my vm using virt-install through the french debian mirror. It works perfectly for squeeze VMs but fails every time with wheezy since march 14th. I hope it helps. Thanks, Ben -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: (no subject)
I did not have this busybox problem (actualy an authentication problem) a few days ago, using pxe boot, maybe you installed your host like last week? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
I came across this problem too today. I believe this bugreport is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703146 In my case it all starts with this warning in my logs: base-installer: W: GPG error: http://ftp.nl.debian.org wheezy Release: The following signatures were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) After this the installer isn't able to install locales, busybox.. etc. -- Regards, Pim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703429: FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared
Source: rsyslog Version: 7.3.8-1 Severity: serious Current version of rsyslog from experimental FTBFS on kfreebsd [1] debug.c: In function 'dbgOutputTID': debug.c:309:22: error: 'SYS_gettid' undeclared (first use in this function) debug.c:309:22: note: each undeclared identifier is reported only once for each function it appears in make[3]: *** [librsyslog_la-debug.lo] Error 1 make[3]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8/runtime' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 Would be great if the porters can have a look. Michael [1] https://buildd.debian.org/status/package.php?p=rsyslogsuite=experimental -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703429: FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared
On Tue, 2013-03-19 at 15:28 +0100, Michael Biebl wrote: Source: rsyslog Version: 7.3.8-1 Severity: serious Current version of rsyslog from experimental FTBFS on kfreebsd [1] debug.c: In function 'dbgOutputTID': debug.c:309:22: error: 'SYS_gettid' undeclared (first use in this function) debug.c:309:22: note: each undeclared identifier is reported only once for each function it appears in make[3]: *** [librsyslog_la-debug.lo] Error 1 make[3]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8/runtime' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 I think it is rsyslog's fault here. I probably do no correctly check for the availablity of gettid. Will look into that soon (it's minor debug-aid functionality which can be disabled without any issues, even during debugging). Rainer
Bug#702753: marked as done (spandsp: Downloads external files at build time (through xsltproc) -- missing Build-Depends?)
Your message dated Tue, 19 Mar 2013 14:49:33 + with message-id e1uhxr3-0006xc...@franck.debian.org and subject line Bug#702753: fixed in spandsp 0.0.6~pre20-3.1 has caused the Debian Bug report #702753, regarding spandsp: Downloads external files at build time (through xsltproc) -- missing Build-Depends? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 702753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: spandsp Version: 0.0.6~pre20-3 Severity: serious When I recently did a full build of spandsp in pbuilder, it happened that my net connection went down momentarily, and I noticed this in the build log: ... cd t38_manual ; xsltproc ../wrapper.xsl ../t38_manual.xml error : connection refused ../t38_manual.xml:3: warning: failed to load external entity http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd; http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd; ^ Writing ch01.html for chapter(what-is-t38) Writing ch02.html for chapter(the-basics-of-a-t38-entity) Writing ch03s02.html for sect1 Writing ch03.html for chapter(the-core-elements-of-a-t38-implementation) Writing ch04.html for chapter(the-elements-of-a-t38-terminal) Writing ch05s02.html for sect1 Writing ch05s03.html for sect1 Writing ch05s04.html for sect1 Writing ch05.html for chapter(the-elements-of-a-t38-gateway) Writing ch06.html for chapter(testing-an-implementation-of-t38) Writing ch07s02.html for sect1 Writing ch07s03.html for sect1 Writing ch07s04.html for sect1 Writing ch07s05.html for sect1 Writing ch07s06.html for sect1 Writing ch07.html for chapter(living-with-real-world-t38-entities) Writing index.html for book make[3]: Leaving directory `/tmp/buildd/spandsp-0.0.6~pre20/doc' Making all in test-data make[3]: Entering directory `/tmp/buildd/spandsp-0.0.6~pre20/test-data' ... Though the package continued building and the build completed successfully, downloading external files during the build process is a serious issue (as it violates the reasonable expectation that source packages shouldn't act as spyware when you build them). Not to mention that if the docs come out differently depending on whether the build machine has net access or not, that's another serious issue -- I didn't check whether this was the case or not for this package. If I add docbook-xml and docbook to the Build-Depends, that seems to resolve this issue, if I do a test rebuild with the network connection temporarily disabled. I'm not sure if both of those are needed... -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: spandsp Source-Version: 0.0.6~pre20-3.1 We believe that the bug you reported is fixed in the latest version of spandsp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated spandsp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Mar 2013 15:23:49 +0100 Source: spandsp Binary: libspandsp2 libspandsp-dev libspandsp-doc Architecture: source amd64 all Version: 0.0.6~pre20-3.1 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libspandsp-dev - Telephony signal processing library - development headers libspandsp-doc - Documentation for the spandsp signal processing library libspandsp2 - Telephony signal processing library Closes: 702753 Changes: spandsp (0.0.6~pre20-3.1) unstable; urgency=low . * Non-maintainer upload. * Fix Downloads external files at build time (through xsltproc) -- missing Build-Depends?: Add build dependency on docbook-xml. (Closes: #702753) Checksums-Sha1: ae458985422b5edbebcdfd46186001199e779791 2402 spandsp_0.0.6~pre20-3.1.dsc 3bc5e7f1e21c08a8ee0a7b752282094e7cb0df67 10668 spandsp_0.0.6~pre20-3.1.debian.tar.gz 1b7c9509a027cc700a302157f00b88ab27a06974 330958 libspandsp2_0.0.6~pre20-3.1_amd64.deb
Bug#703429: FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared
Michael, On Tue, 2013-03-19 at 14:35 +, Rainer Gerhards wrote: I think it is rsyslog's fault here. I probably do no correctly check for the availablity of gettid. Will look into that soon (it's minor debug-aid functionality which can be disabled without any issues, even during debugging). This patch should fix the issue: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=aef0be0c1799fbb20955fc1dc014cb9c9772af88 I would appreciate if you could give it a try. Will be included in 7.3.9. Rainer
Bug#703371: libharminv-dev: harminv build stale on i386
Sébastien Villemot sebast...@debian.org writes: Le lundi 18 mars 2013 à 17:02 -0400, Andreas Kloeckner a écrit : Package: libharminv-dev Version: 1.3.1-8 Severity: grave Justification: renders package unusable It appears as though the harminv package has become unusable in i386. It refers to libcblas.3gf.so, which is no longer available in testing/unstable. Can you please provide the output of the following command: $ update-alternatives --display libblas.so.3 It looks like the i386 binary has been built on an non-minimal chroot, and was therefore linked against ATLAS. This creates missing shared library dependencies when the BLAS alternative does not point to ATLAS (which I guess is the case for the reporter). A binNMU of the package should fix the problem. FYI: libblas.so.3 - auto mode link currently points to /usr/lib/openblas-base/libopenblas.so.0 /usr/lib/libblas/libblas.so.3 - priority 10 slave libblas.so.3gf: /usr/lib/libblas/libblas.so.3 /usr/lib/openblas-base/libopenblas.so.0 - priority 40 slave libblas.so.3gf: /usr/lib/openblas-base/libopenblas.so.0 Current 'best' version is '/usr/lib/openblas-base/libopenblas.so.0'. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703429: marked as done (FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared)
Your message dated Tue, 19 Mar 2013 15:48:13 + with message-id e1uhylp-0005hl...@franck.debian.org and subject line Bug#703429: fixed in rsyslog 7.3.8-2 has caused the Debian Bug report #703429, regarding FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rsyslog Version: 7.3.8-1 Severity: serious Current version of rsyslog from experimental FTBFS on kfreebsd [1] debug.c: In function 'dbgOutputTID': debug.c:309:22: error: 'SYS_gettid' undeclared (first use in this function) debug.c:309:22: note: each undeclared identifier is reported only once for each function it appears in make[3]: *** [librsyslog_la-debug.lo] Error 1 make[3]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8/runtime' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-rsyslog_7.3.8-1-kfreebsd-amd64-1l58ej/rsyslog-7.3.8' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 Would be great if the porters can have a look. Michael [1] https://buildd.debian.org/status/package.php?p=rsyslogsuite=experimental -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information ---End Message--- ---BeginMessage--- Source: rsyslog Source-Version: 7.3.8-2 We believe that the bug you reported is fixed in the latest version of rsyslog, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 703...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated rsyslog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Mar 2013 16:40:58 +0100 Source: rsyslog Binary: rsyslog rsyslog-doc rsyslog-mysql rsyslog-pgsql rsyslog-mongodb rsyslog-gssapi rsyslog-gnutls rsyslog-relp Architecture: source amd64 all Version: 7.3.8-2 Distribution: experimental Urgency: low Maintainer: Michael Biebl bi...@debian.org Changed-By: Michael Biebl bi...@debian.org Description: rsyslog- reliable system and kernel logging daemon rsyslog-doc - documentation for rsyslog rsyslog-gnutls - TLS protocol support for rsyslog rsyslog-gssapi - GSSAPI authentication and encryption support for rsyslog rsyslog-mongodb - MongoDB output plugin for rsyslog rsyslog-mysql - MySQL output plugin for rsyslog rsyslog-pgsql - PostgreSQL output plugin for rsyslog rsyslog-relp - RELP protocol support for rsyslog Closes: 703429 Changes: rsyslog (7.3.8-2) experimental; urgency=low . * Cherry pick patch from upstream which fixes the build on architectures which don't have SYS_gettid. (Closes: #703429) Checksums-Sha1: be437c8dd2418d6acf2bf0c5cb43e928aee09090 2422 rsyslog_7.3.8-2.dsc f54f90e2dd77d1756510ff1d77fdc95681ebb369 29985 rsyslog_7.3.8-2.debian.tar.gz 7353b9c2b4affa5e7826f90b548470d9430f2856 689282 rsyslog_7.3.8-2_amd64.deb a81377502ef45bbe6f58d332eaf2f36b1e03ddb9 1190346 rsyslog-doc_7.3.8-2_all.deb 67faf2a5a004f5d87661746b6f9b83ebdbe28161 144484 rsyslog-mysql_7.3.8-2_amd64.deb d3fdd87a0e910d161a400d99cc3ba79400d2e1d6 142686 rsyslog-pgsql_7.3.8-2_amd64.deb 8be249a6f7a87a67386cb50b654d9cb3801efc3a 144816 rsyslog-mongodb_7.3.8-2_amd64.deb 312f1448f9113d1b7b03f2615bc7277acb037de5 150908 rsyslog-gssapi_7.3.8-2_amd64.deb e8540ac56c8223376b0bd3dd0f1ce5772fba4093 149620 rsyslog-gnutls_7.3.8-2_amd64.deb 7ac08e8e4fc0e983413376a39393e3c29f94fb24 145414 rsyslog-relp_7.3.8-2_amd64.deb Checksums-Sha256: 151333609ae71dc7cb236f23848a07510f3889ada421c65af1cae6f2677f0025 2422 rsyslog_7.3.8-2.dsc 9690012e4cd022528d6c74e36564e1faacc2ab11e3029fc994384d3e7963fa3d
Bug#703094: owncloud: diff for NMU version 4.0.8debian-1.6
tags 703094 + pending
thanks
Dear maintainer,
I've prepared an NMU for owncloud (versioned as 4.0.8debian-1.6) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Various Artists: Scorn Not His Simplicity
diff -Nru owncloud-4.0.8debian/debian/changelog owncloud-4.0.8debian/debian/changelog
--- owncloud-4.0.8debian/debian/changelog 2013-02-28 19:15:56.0 +0100
+++ owncloud-4.0.8debian/debian/changelog 2013-03-19 17:05:15.0 +0100
@@ -1,3 +1,18 @@
+owncloud (4.0.8debian-1.6) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix multiple vulnerabilities (oC-SA-2013-009, oC-SA-2013-010):
+add patches taken from upstream git:
++ debian/patches/16_oc-sa-2013-010.patch
+ CVE-2013-1851: user_migrate: Local file disclosure
+ oC-SA-2013-010, commit edf7162 in stable4 branch
++ debian/patches/17_oc-sa-2013-009.patch
+ CVE-2013-1850: Contacts: Bypass of file blacklist
+ oC-SA-2013-009, commit fae5bd3 in stable4 branch
+(Closes: #703094)
+
+ -- gregor herrmann gre...@debian.org Tue, 19 Mar 2013 17:05:08 +0100
+
owncloud (4.0.8debian-1.5) unstable; urgency=low
* Non-maintainer upload.
diff -Nru owncloud-4.0.8debian/debian/patches/16_oc-sa-2013-010.patch owncloud-4.0.8debian/debian/patches/16_oc-sa-2013-010.patch
--- owncloud-4.0.8debian/debian/patches/16_oc-sa-2013-010.patch 1970-01-01 01:00:00.0 +0100
+++ owncloud-4.0.8debian/debian/patches/16_oc-sa-2013-010.patch 2013-03-15 22:14:28.0 +0100
@@ -0,0 +1,39 @@
+From edf7162762fc425df1ec2ce7149c18a0af82a3b8 Mon Sep 17 00:00:00 2001
+From: Lukas Reschke lu...@statuscode.ch
+Date: Mon, 11 Mar 2013 16:21:26 +0100
+Subject: [PATCH] Check if username is valid and remove slashes from filename
+
+Backport of #2236 to stable45
+---
+ lib/migrate.php | 11 ++-
+ 1 file changed, 10 insertions(+), 1 deletion(-)
+
+diff --git a/lib/migrate.php b/lib/migrate.php
+index 8d3610c..8465eed 100644
+--- a/lib/migrate.php
b/lib/migrate.php
+@@ -234,11 +234,20 @@ class OC_Migrate{
+ OC_Log::write( 'migration', 'User doesn\'t exist', OC_Log::ERROR );
+ return json_encode( array( 'success' = false ) );
+ }
++
++// Check if the username is valid
++if( preg_match( '/[^a-zA-Z0-9 _\.@\-]/', $json-exporteduser )) {
++ OC_Log::write( 'migration', 'Username is not valid', OC_Log::ERROR );
++ return json_encode( array( 'success' = false ) );
++}
++
+ // Copy data
+ $userfolder = $extractpath . $json-exporteduser;
+ $newuserfolder = $datadir . '/' . self::$uid;
+ foreach(scandir($userfolder) as $file){
+- if($file !== '.' $file !== '..' is_dir($file)){
++ if($file !== '.' $file !== '..' is_dir($file)) {
++ $file = str_replace(array('/', '\\'), '', $file);
++
+ // Then copy the folder over
+ OC_Helper::copyr($userfolder.'/'.$file, $newuserfolder.'/'.$file);
+ }
+--
+1.7.10.4
+
diff -Nru owncloud-4.0.8debian/debian/patches/17_oc-sa-2013-009.patch owncloud-4.0.8debian/debian/patches/17_oc-sa-2013-009.patch
--- owncloud-4.0.8debian/debian/patches/17_oc-sa-2013-009.patch 1970-01-01 01:00:00.0 +0100
+++ owncloud-4.0.8debian/debian/patches/17_oc-sa-2013-009.patch 2013-03-15 22:15:52.0 +0100
@@ -0,0 +1,84 @@
+From fae5bd363b4cc3bd00d1a983ca5aff4a0eb86408 Mon Sep 17 00:00:00 2001
+From: Thomas Tanghus tho...@tanghus.net
+Date: Sat, 9 Mar 2013 19:26:31 +0100
+Subject: [PATCH] Contacts: Backport filename sanitation and blacklist
+ checking to stable4.
+
+---
+ apps/contacts/ajax/uploadimport.php |8
+ apps/contacts/import.php| 15 ++-
+ 2 files changed, 18 insertions(+), 5 deletions(-)
+
+diff --git a/apps/contacts/ajax/uploadimport.php b/apps/contacts/ajax/uploadimport.php
+index 4c3f5ea..56a966b 100644
+--- a/apps/contacts/ajax/uploadimport.php
b/apps/contacts/ajax/uploadimport.php
+@@ -35,7 +35,11 @@ $tmpfile = md5(rand());
+
+ // If it is a Drag'n'Drop transfer it's handled here.
+ $fn = (isset($_SERVER['HTTP_X_FILE_NAME']) ? $_SERVER['HTTP_X_FILE_NAME'] : false);
++$fn = strtr($fn, array('/' = '', \\ = ''));
+ if($fn) {
++ if(OC_Filesystem::isFileBlacklisted($fn)) {
++ bailOut($l10n-t('Upload of blacklisted file:') . $fn);
++ }
+ if($view-file_put_contents('/'.$tmpfile, file_get_contents('php://input'))) {
+ OCP\JSON::success(array('data' = array('path'='', 'file'=$tmpfile)));
+ exit();
+@@ -66,6 +70,10 @@ $file=$_FILES['importfile'];
+
+ $tmpfname = tempnam(get_temp_dir(), occOrig);
+ if(file_exists($file['tmp_name'])) {
++ $filename = strtr($file['name'], array('/' = '', \\ = ''));
++ if(OC_Filesystem::isFileBlacklisted($filename)) {
++ bailOut($l10n-t('Upload of
Processed: owncloud: diff for NMU version 4.0.8debian-1.6
Processing commands for cont...@bugs.debian.org: tags 703094 + pending Bug #703094 [owncloud] owncloud: multiple vulnerabilities (oC-SA-2013-009, oC-SA-2013-010) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 703094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 703429 in 7.3.8-2, retitle 703429 to wtp.c:386:22: error: 'thrdName' undeclared
Processing commands for cont...@bugs.debian.org:
found 703429 7.3.8-2
Bug #703429 {Done: Michael Biebl bi...@debian.org} [src:rsyslog] FTBFS on
!Linux: debug.c:309:22: error: 'SYS_gettid' undeclared
Marked as found in versions rsyslog/7.3.8-2; no longer marked as fixed in
versions rsyslog/7.3.8-2 and reopened.
retitle 703429 wtp.c:386:22: error: 'thrdName' undeclared
Bug #703429 [src:rsyslog] FTBFS on !Linux: debug.c:309:22: error: 'SYS_gettid'
undeclared
Changed Bug title to 'wtp.c:386:22: error: 'thrdName' undeclared' from 'FTBFS
on !Linux: debug.c:309:22: error: 'SYS_gettid' undeclared'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
703429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703444: ecere-sdk: Must build-dep on and use libgif-dev instead of included libungif
Package: ecere-sdk Severity: serious Version: 0.44.03-1 libungif has been removed from debian in favour of libgif. ecere-sdk should build-dep on libgif-dev use that instead of the included copy of code. Also it would be preferred for ecere-sdk to not have /deps/ - external copies of code included in the release tarball Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690081: Processed: your mail
Control: severity 690081 wishlist On Tue, Mar 19, 2013 at 08:45:13 +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: severity 690081 grave Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'grave' from 'wishlist' No, this bug is in no way grave. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Processed: your mail
Processing control commands: severity 690081 wishlist Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'wishlist' from 'grave' -- 690081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
severity 703404 important thanks Quoting Tycho Lursen (tycholur...@gmail.com): Package: debian-installer Version: wheezy Severity: critical Tags: d-i Justification: breaks the whole system No, it doesn't. :-). Hence lowering the severity. signature.asc Description: Digital signature
Processed: Re: Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
Processing commands for cont...@bugs.debian.org: severity 703404 important Bug #703404 [debian-installer] debian-installer: wheezy (PXE boot) failes to install busybox and kernel Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 703404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678979: request freeze exception for slony1-2
Since the original bug was opened we've figured out why adding PG 9.1 support to slony 2.0.x was causing occasional test failures. The fixes for PG 9.1 (upstream bugs #255) along with the fixes for the MOVE SET issue caused by the #255 fix (upstream bug #285) I think will produce a working slony 2.0.x against 9.1. If Debian would like I can assemble assemble these two patches and run it through the testing suite. Upstreams interest in maintaining 2.0.x going forward is limited since we feel that the effort in upgrading a cluster to to 2.1 isn't that much more than upgrading from a 2.0.x and 2.1.x works with all versions of PG that 2.0.x does. Steve -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 703419
Processing commands for cont...@bugs.debian.org: tags 703419 + wheezy Bug #703419 [release-notes] release-notes: Need updating / finalising for wheezy Added tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 703419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703371: marked as done (libharminv-dev: harminv build stale on i386)
Your message dated Tue, 19 Mar 2013 18:47:47 + with message-id e1ui1zb-0001fz...@franck.debian.org and subject line Bug#703371: fixed in harminv 1.3.1-9 has caused the Debian Bug report #703371, regarding libharminv-dev: harminv build stale on i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libharminv-dev Version: 1.3.1-8 Severity: grave Justification: renders package unusable Dear Maintainer, It appears as though the harminv package has become unusable in i386. It refers to libcblas.3gf.so, which is no longer available in testing/unstable. Any help would be much appreciated. Thanks, Andreas -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: harminv Source-Version: 1.3.1-9 We believe that the bug you reported is fixed in the latest version of harminv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 703...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz deb...@alteholz.de (supplier of updated harminv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 19 Mar 2013 19:00:38 +0100 Source: harminv Binary: harminv libharminv2 libharminv-dev Architecture: source amd64 Version: 1.3.1-9 Distribution: unstable Urgency: low Maintainer: Thorsten Alteholz deb...@alteholz.de Changed-By: Thorsten Alteholz deb...@alteholz.de Description: harminv- extraction of complex frequencies and amplitudes from time series libharminv-dev - Library for using harminv, development version libharminv2 - Library for using harminv Closes: 703371 Changes: harminv (1.3.1-9) unstable; urgency=low . * debian/control: add Build-Conflicts against libatlas-base-dev. If the latter is installed, the build system detects and links against some ATLAS-specific shared libraries. In turn, this makes libharminv.so unusable when the BLAS alternative does not point to ATLAS. Thanks a lot to Sebastien Villemot for analysing the problem and providing the solution. (Closes: #703371). Checksums-Sha1: 1f13075431fdc684bfe872b57b7385d74255b39f 1272 harminv_1.3.1-9.dsc ce583e71a12f942adb38817803cb9ec10eda744f 6975 harminv_1.3.1-9.debian.tar.gz b30a70cee7dcc8d49d0e7a9913d32c8fb330d3aa 22604 harminv_1.3.1-9_amd64.deb e29fb2ae29e4dc4bfbd12a683e92c1c286864514 18402 libharminv2_1.3.1-9_amd64.deb 9e2612857470501a8bc6ce82dbb1e732e4f83298 7122 libharminv-dev_1.3.1-9_amd64.deb Checksums-Sha256: 358dcc623cd4a4372819f1eaed14823a98b27340d7347abc3d378acaf98875fb 1272 harminv_1.3.1-9.dsc 24334c0b76721c974f23cfc5d7cc158339f39241a16f565ef0ebe4f073af8163 6975 harminv_1.3.1-9.debian.tar.gz 3768ff6c70461f66757899039f67f8f9e0dc31efa37422d7f1d63de1e5fb1d1a 22604 harminv_1.3.1-9_amd64.deb 13641ab8a692ff1c27b6c4eabf5ef3bc4c8607029d99674cb2ec857dec9a4811 18402 libharminv2_1.3.1-9_amd64.deb 77b0762b238389b58676c3794c5da0525c0dd998a3c93a071b6a02644f3c5628 7122 libharminv-dev_1.3.1-9_amd64.deb Files: 689d43f0a45c900c30b214af881b1440 1272 science optional harminv_1.3.1-9.dsc 08d7aaab9a804effb1f192db23df4ea6 6975 science optional harminv_1.3.1-9.debian.tar.gz 5a2cac455e645342f9043195cd6846da 22604 science optional harminv_1.3.1-9_amd64.deb cf991a9aefa037a0e0fde04c29b1acf3 18402 libs optional libharminv2_1.3.1-9_amd64.deb 20c3ccc0c72a6e484b9d1c918e21c17b 7122 libdevel optional libharminv-dev_1.3.1-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlFIw6gACgkQ02K2KlS5mJAOpACfS9k5qeifRxOEcu+3gz2x9riD XkcAmwXBkeM96gr2IcYe4Yz62QkwIF8I =N6zB -END PGP SIGNATUREEnd Message---
Bug#703448: undistract-me: uses xprop without dependency on x11-utils
Package: undistract-me Version: 0.1.0+bzr19-1 Severity: serious Justification: missing dependency Dear Clint, after installing undistract-me on a system where x11-utils is not installed and which I only access via ssh -Y, before and after the output of every command I get error messages like the following one: $ echo foobar -bash: xprop: command not found foobar -bash: xprop: command not found $ xprop is part of the x11-utils, but there's no dependency on x11-utils and no safe-guard around xprop's invocation either. After installing x11-utils the error messages vanished, but no popups appeared though. But since notify-send foobar didn't show anything via SSH with tunneled X display either, I suspect that's more a libnotify-issue than a undistract-me issue. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (600, 'testing'), (200, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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 undistract-me depends on: ii libnotify-bin 0.7.5-1 undistract-me recommends no packages. undistract-me suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Processed: your mail
Processing control commands: severity 690081 grave Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'grave' from 'wishlist' -- 690081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690081: Processed: your mail
On Tue, Mar 19, 2013 at 19:57:17 +0100, Erich Schubert wrote: Control: severity 690081 grave No, this bug is in no way grave. Sure it is, by definition of grave: http://www.debian.org/Bugs/Developer#severities grave makes the package in question unusable or mostly so [...] The package is *unusable* (as in: *uninstallable*) on multiarch. Absolutely not. Policy has no requirement that a library package be multiarch-compatible. libwayland0 is installable and working on every arch where it exists, it's just not compatible with multiarch, has never been, and making it so is a wishlist bug. Cheers, Julien signature.asc Description: Digital signature
Bug#703371: libharminv-dev: harminv build stale on i386
On Tue, 19 Mar 2013, Sébastien Villemot wrote: A binNMU of the package should fix the problem. Actually a Build-Conflicts is a more robust solution. The attached patch implements this. Great, thanks a lot. Thorsten: does that sound fine to you? I can do the upload if this helps. Yes, I am impressed by this quick solution. You already did most of the work, so I will take care of the upload (just done) and the unblock request. Thorsten
Processed: severity of 690081 is wishlist
Processing commands for cont...@bugs.debian.org: # stop fucking with my bugs kthxbye severity 690081 wishlist Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'wishlist' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 690081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699852: Proposed debdiff
On Sat, Mar 9, 2013 at 17:30:19 +0100, Tino Keitel wrote: On Fri, Mar 08, 2013 at 07:39:32 +0100, Yves-Alexis Perez wrote: I've built a package including the patch pointed by Josselin. Could someone test it and report back as I don't have an http-based syncevolution setup. Hi, I already prepared a -2 version with several fixes, including the autosync issue, but got interrupted due to the birth of a baby girl. I'll try to push it to the alioth git repository, and would appreciate some help getting it reviewed/accepted for wheezy or wheezy-updates. Looks like the alioth git repo mentions the autosync issue in the changelog, but doesn't actually include the change? Also it adds hardening, which is too invasive for the current freeze stage. Cheers, Julien signature.asc Description: Digital signature
Bug#703330: missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile
Control: tags -1 + moreinfo On Mon, Mar 18, 2013 at 10:42:02AM -0430, PICCORO McKAY Lenz wrote: the tk-dev package on upgrades not install correctly.. this are due some non present conflics, said : Desempaquetando el reemplazo de tcl-dev ... dpkg: error al procesar ./tcl-dev_8.5.0-1vnz1_all.deb (--install): intentando sobreescribir `/usr/include/tcl', que está también en el paquete tk-tile 0.8.2-2.1 What is tcl-dev_8.5.0-1vnz1_all.deb? The vnz1 part suggests it is not an official Debian package. -- WBR, wRAR signature.asc Description: Digital signature
Processed: Re: Bug#703330: missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile
Processing control commands: tags -1 + moreinfo Bug #703330 [src:tcltk-defaults] missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile Added tag(s) moreinfo. -- 703330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702791: confirmed in a not extremely slow box
Control: tag -1 -pending Untagging as it's been pending for over a week. FWIW I've reproduced the issue in a reasonably modern laptop (lenovo x201): Ran 2173 tests in 600.905s FAILED (skips=21, failures=1, errors=2, successes=2149) -- Every great idea is worthless without someone to do the work. --Neil Williams -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: confirmed in a not extremely slow box
Processing control commands: tag -1 -pending Bug #702791 [juju] FTBFS: test suite errors Removed tag(s) pending. -- 702791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703330: missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile
this king of stupid responce are the cause of late fixeds on debian unstable.. ok the package its not comming from debian, cos i must repackaged .. thingking that are broken in unstable!!! see files for both packages and its obviosly this tk-dev must have a conflicts/break field. ufff... On Tue, Mar 19, 2013 at 2:47 PM, Andrey Rahmatullin w...@wrar.name wrote: Control: tags -1 + moreinfo On Mon, Mar 18, 2013 at 10:42:02AM -0430, PICCORO McKAY Lenz wrote: the tk-dev package on upgrades not install correctly.. this are due some non present conflics, said : Desempaquetando el reemplazo de tcl-dev ... dpkg: error al procesar ./tcl-dev_8.5.0-1vnz1_all.deb (--install): intentando sobreescribir `/usr/include/tcl', que está también en el paquete tk-tile 0.8.2-2.1 What is tcl-dev_8.5.0-1vnz1_all.deb? The vnz1 part suggests it is not an official Debian package. -- WBR, wRAR -- Lenz McKAY Gerardo (PICCORO) http://qglochekone.blogspot.com
Bug#702633: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
reopen 702633 thanks The changelog entry for krb5 1.10.1+dfsg-4+nmu1 mentions the CVE number 2013-1016; this vulnerability is actually cve-2012-1016 (note 2012 instead of 2013). I don't see a debian-security-announce mail yet, so hopefully the typo will not be promulgated there. -Ben Kaduk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
Processing commands for cont...@bugs.debian.org:
reopen 702633
Bug #702633 {Done: Sebastian Ramacher sramac...@debian.org} [src:krb5]
CVE-2012-1016: NULL pointer dereference (DoS) in
plugins/preauth/pkinit/pkinit_srv.c
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.10.1+dfsg-4+nmu1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
702633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702633: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
On Tue, 2013-03-19 at 15:47 -0400, Benjamin Kaduk wrote: reopen 702633 Why? Do you believe that the 1.10.1+dfsg-4+nmu1 package does not contain a fix for this bug? If the answer to my first question is because it's not fixed in stable yet, then the re-opening was incorrect, as the actual effect was to mark it as not fixed in _unstable_. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703330: missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile
On 2013-03-19 20:43 +0100, PICCORO McKAY Lenz wrote: this king of stupid responce are the cause of late fixeds on debian unstable.. ok the package its not comming from debian, cos i must repackaged .. thingking that are broken in unstable!!! Well, I think they actually are, see #612264 (reported over two years ago and never fixed). While tk-tile has been removed from testing because of that problem, it will still bite users who upgrade from squeeze, hence tcl-dev needs to declare a Conflicts: tk-tile. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703330: missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile
obvously a replace too, due files are present and similar fuctions i revised the pacakge and compared.. well this last not necesary but .. who kowns On Tue, Mar 19, 2013 at 3:27 PM, Sven Joachim svenj...@gmx.de wrote: On 2013-03-19 20:43 +0100, PICCORO McKAY Lenz wrote: this king of stupid responce are the cause of late fixeds on debian unstable.. ok the package its not comming from debian, cos i must repackaged .. thingking that are broken in unstable!!! Well, I think they actually are, see #612264 (reported over two years ago and never fixed). While tk-tile has been removed from testing because of that problem, it will still bite users who upgrade from squeeze, hence tcl-dev needs to declare a Conflicts: tk-tile. Cheers, Sven -- Lenz McKAY Gerardo (PICCORO) http://qglochekone.blogspot.com
Bug#702633: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
On Tue, 19 Mar 2013, Adam D. Barratt wrote: On Tue, 2013-03-19 at 15:47 -0400, Benjamin Kaduk wrote: reopen 702633 Why? Do you believe that the 1.10.1+dfsg-4+nmu1 package does not contain a fix for this bug? The changelog entry for 1.10.1+dfsg-4+nmu1 mentions the wrong CVE number, and as such the purpoted fix for this bug is incomplete, as the documentation of the change is incorrect. Now, it may be that the package maintainer or the security team may decide that a version bump is not necessary to correct this error, but such a decision should be explicitly made (IMHO). If the answer to my first question is because it's not fixed in stable yet, then the re-opening was incorrect, as the actual effect was to mark it as not fixed in _unstable_. My action of reopening the bug reflects the contents of the package in unstable. -Ben Kaduk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#702633: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
Processing control commands: fixed -1 1.10.1+dfsg-4+nmu1 Bug #702633 [src:krb5] CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c Marked as fixed in versions krb5/1.10.1+dfsg-4+nmu1. -- 702633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702633: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
Control: fixed -1 1.10.1+dfsg-4+nmu1 On Tue, 2013-03-19 at 16:04 -0400, Benjamin Kaduk wrote: On Tue, 19 Mar 2013, Adam D. Barratt wrote: On Tue, 2013-03-19 at 15:47 -0400, Benjamin Kaduk wrote: reopen 702633 Why? Do you believe that the 1.10.1+dfsg-4+nmu1 package does not contain a fix for this bug? The changelog entry for 1.10.1+dfsg-4+nmu1 mentions the wrong CVE number, and as such the purpoted fix for this bug is incomplete, as the documentation of the change is incorrect. Now, it may be that the package maintainer or the security team may decide that a version bump is not necessary to correct this error, but such a decision should be explicitly made (IMHO). This bug is about CVE-2012-1016. If the package contains a fix for CVE-2012-1016 then the bug is fixed, whether or not the changelog correctly indicates that. Yes, the changelog should be corrected, but that doesn't change the fact that the package includes the fix for the security issue discussed in this bug report. Regards, Adam (Not that it should matter, but with a Release Manager hat on; the maintainer / security team are of course free to disagree...) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703330: diff for NMU 8.5.0-2.1
tags 703330 + pending
thanks
Dear maintainer,
I've prepared an NMU for tcltk-defaults (versioned as 0.7.1-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer. Debdiff is attached.
Cheers,
Anton
diff -Nru tcltk-defaults-8.5.0/debian/changelog
tcltk-defaults-8.5.0/debian/changelog
--- tcltk-defaults-8.5.0/debian/changelog 2011-02-06 15:27:56.0
+0100
+++ tcltk-defaults-8.5.0/debian/changelog 2013-03-19 21:32:16.0
+0100
@@ -1,3 +1,10 @@
+tcltk-defaults (8.5.0-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add Replaces/Conflicts to tcl-dev against tk-tile. (Closes: #703330)
+
+ -- Anton Gladky gl...@debian.org Tue, 19 Mar 2013 21:30:26 +0100
+
tcltk-defaults (8.5.0-2) unstable; urgency=low
* Upload of 8.5 to unstable (closes: #515984).
diff -Nru tcltk-defaults-8.5.0/debian/control
tcltk-defaults-8.5.0/debian/control
--- tcltk-defaults-8.5.0/debian/control 2011-02-06 15:29:23.0 +0100
+++ tcltk-defaults-8.5.0/debian/control 2013-03-19 21:30:15.0 +0100
@@ -42,6 +42,8 @@
Priority: optional
Architecture: all
Depends: tcl8.5-dev (= 8.5.0-1), tcl (= ${binary:Version}), ${misc:Depends}
+Replaces: tk-tile
+Conflicts: tk-tile
Suggests: tcl-doc
Description: The Tool Command Language (default version) - development files
Tcl is a powerful, easy-to-use, embeddable, cross-platform interpreted
signature.asc
Description: OpenPGP digital signature
Processed: diff for NMU 8.5.0-2.1
Processing commands for cont...@bugs.debian.org: tags 703330 + pending Bug #703330 [src:tcltk-defaults] missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 703330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702633: CVE-2012-1016: NULL pointer dereference (DoS) in plugins/preauth/pkinit/pkinit_srv.c
Hi Benjamin On Tue, Mar 19, 2013 at 04:04:59PM -0400, Benjamin Kaduk wrote: On Tue, 19 Mar 2013, Adam D. Barratt wrote: On Tue, 2013-03-19 at 15:47 -0400, Benjamin Kaduk wrote: reopen 702633 Why? Do you believe that the 1.10.1+dfsg-4+nmu1 package does not contain a fix for this bug? The changelog entry for 1.10.1+dfsg-4+nmu1 mentions the wrong CVE number, and as such the purpoted fix for this bug is incomplete, as the documentation of the change is incorrect. Now, it may be that the package maintainer or the security team may decide that a version bump is not necessary to correct this error, but such a decision should be explicitly made (IMHO). If the answer to my first question is because it's not fixed in stable yet, then the re-opening was incorrect, as the actual effect was to mark it as not fixed in _unstable_. My action of reopening the bug reflects the contents of the package in unstable. Thank you for noticing this. To track this I opened http://bugs.debian.org/703457 Hope that helps, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694352: marked as done ([lcdf-typetools] lcdf-typetool include non free adobe data; glyph list)
Your message dated Tue, 19 Mar 2013 21:19:00 + with message-id e1ui3vw-0005d1...@franck.debian.org and subject line Bug#694352: fixed in lcdf-typetools 2.92+dfsg1-0.1~deb7u1 has caused the Debian Bug report #694352, regarding [lcdf-typetools] lcdf-typetool include non free adobe data; glyph list to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 694352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lcdf-typetools Version: 2.92-1+b1 Severity: serious Your package include the old adobe glyphlist that is all right reserved adobe. Please use during the build the aglfn package that include the relicenced free one (preferally using a build depend and symlink during install) Thanks ---End Message--- ---BeginMessage--- Source: lcdf-typetools Source-Version: 2.92+dfsg1-0.1~deb7u1 We believe that the bug you reported is fixed in the latest version of lcdf-typetools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 694...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg stapelb...@debian.org (supplier of updated lcdf-typetools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Mar 2013 21:53:30 +0100 Source: lcdf-typetools Binary: lcdf-typetools Architecture: source amd64 Version: 2.92+dfsg1-0.1~deb7u1 Distribution: testing-proposed-updates Urgency: low Maintainer: C.M. Connelly c...@debian.org Changed-By: Michael Stapelberg stapelb...@debian.org Description: lcdf-typetools - Programs to manipulate OpenType and multiple-master fonts Closes: 694352 Changes: lcdf-typetools (2.92+dfsg1-0.1~deb7u1) testing-proposed-updates; urgency=low . * Non-maintainer upload. * Repackage without non-free glyphlist.txt, use aglfn package instead (Closes: #694352) Checksums-Sha1: 02a5d6f052b6c44c10a9b64ec3b478bc3dcb0b1b 1854 lcdf-typetools_2.92+dfsg1-0.1~deb7u1.dsc cc55d204e7da8f34025d9376416668ba20855548 571294 lcdf-typetools_2.92+dfsg1.orig.tar.gz c21b8548848dda92e5616431ee357360c9635709 7412 lcdf-typetools_2.92+dfsg1-0.1~deb7u1.debian.tar.gz 825267f8b11e32655b76d7a17501fa6e032d8408 1676742 lcdf-typetools_2.92+dfsg1-0.1~deb7u1_amd64.deb Checksums-Sha256: e7811bd238cd732b6329dd8e594b5c0803817c1cc0181fd334a1b031473c0fca 1854 lcdf-typetools_2.92+dfsg1-0.1~deb7u1.dsc be1a867133eadc4f307d99a57959149dc9b7a0c796a85b636683947c9aadba3c 571294 lcdf-typetools_2.92+dfsg1.orig.tar.gz 75f3b528b4cce932779c77fa381ea7ba9b8fe0d9c2c977aabc316b0dc4cb00f9 7412 lcdf-typetools_2.92+dfsg1-0.1~deb7u1.debian.tar.gz 696e29a339bfcffa67c5432105875331581c77d0ab986082b9733bdadc228524 1676742 lcdf-typetools_2.92+dfsg1-0.1~deb7u1_amd64.deb Files: 504fa0bdf30ddfb825b57fcb56742c00 1854 text optional lcdf-typetools_2.92+dfsg1-0.1~deb7u1.dsc 1f951df3991a72eccd2a75ab6e5647e0 571294 text optional lcdf-typetools_2.92+dfsg1.orig.tar.gz 5db22f14c60541b8a16b7de6672951aa 7412 text optional lcdf-typetools_2.92+dfsg1-0.1~deb7u1.debian.tar.gz cda761acd74cbd00177274e0002e9442 1676742 text optional lcdf-typetools_2.92+dfsg1-0.1~deb7u1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRSNH+AAoJEE5xYO1KyO4dEr8P/3Cz2TtCiciB/eEseSDKAciw bFbbRZIbYq8/lqBPK8js65jaxkd2qyH8ifvEzYDwK+4/ReerqLowx6/B/30AZhXR X7qSk1/U2rpLfdJwYhgKlOBPczQFqy5q7KxgMtkDawx7ZwEJps28OItqLpraXQH7 9bS2pZgwrV3GSmG4pw9q+n2dVjvpocV92IRcgIGTOCNeSLa5UiBxX2bld248MZpx mgIjJFaJszSqvGol6npqkZ7rMSCVxlPY9r2A7g/ik1FLa8LQ4PG6yTR+23OOUTSy OSpvEQ1T5bzn2zGAXcceFmDxkqsRjAkPwgY1HgLFCUrARtvWK+LZ/NwlGYi8lhJv hZUmEj5D2PIgiPXlZh855E1vtwXzzaHt/WoNrbzDF8Tp4hhSWIIoWZWzzyXBbQzG Y/S7wNONEtRvkj5zqWiQzT/1Z8CD8wOFQrij3XqYn/CKm7sIs16tsVUV8xNWmg6U qxBNbDQpII3weWqrwXY8kT/AcOFO9gAOCDk9rb1iXfzqCFNGQ49BR7+UO1ilJKGz 23LW1u/1Dx9d7rkjjDiwE3+o36t50+auQ5ki9LRcyc7ZgQxX+jCsu4otnphXPTuj zXesWtMUCGL0PepC2C1LUPjIiZU7rF99Zuz4xDYrMDclj1F5cYs1HMdX5LB3tQF9 uBcCRCoutXG7usI4UW3v =TJT0 -END PGP SIGNATUREEnd Message---
Bug#702775: marked as done (ganglia: limiting security support)
Your message dated Tue, 19 Mar 2013 22:18:17 + with message-id e1ui4rj-0002rl...@franck.debian.org and subject line Bug#702775: fixed in ganglia 3.3.8-1+nmu1 has caused the Debian Bug report #702775, regarding ganglia: limiting security support to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 702775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ganglia Version: 3.3.8-1 Severity: grave Tags: security Control: clone -1 -2 Control: reassign -2 src:ganglia-web 3.5.2-1 X-Debbugs-cc: t...@security.debian.org Hi again, Given the recent issues in Ganglia's web frontend and a review of some portions of the code we, as in the security team, have decided to limit ganglia's security support to installations behind a trusted HTTP zone. Any vulnerability that is only relevant when exposing ganglia's web frontend to a non-secure zone will therefore be treated as a non-issue by the security team. They could still be fixed via a SPU, however. As such, please add a README.Debian.security file briefly mentioning the limited security support, effective for the version in wheezy and newer. Thanks in advance. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net ---End Message--- ---BeginMessage--- Source: ganglia Source-Version: 3.3.8-1+nmu1 We believe that the bug you reported is fixed in the latest version of ganglia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated ganglia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Mar 2013 18:52:40 + Source: ganglia Binary: ganglia-monitor ganglia-monitor-python gmetad libganglia1 libganglia1-dev ganglia-webfrontend Architecture: source all amd64 Version: 3.3.8-1+nmu1 Distribution: unstable Urgency: medium Maintainer: Stuart Teasdale s...@debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: ganglia-monitor - cluster monitoring toolkit - node daemon ganglia-monitor-python - cluster monitoring toolkit - python modules ganglia-webfrontend - cluster monitoring toolkit - web front-end gmetad - cluster monitoring toolkit - Ganglia Meta-Daemon libganglia1 - cluster monitoring toolkit - shared libraries libganglia1-dev - cluster monitoring toolkit - development libraries Closes: 702775 Changes: ganglia (3.3.8-1+nmu1) unstable; urgency=medium . * Non-maintainer upload by the Security Team. * Add a README.Debian.security file discussing limited security support for this package (closes: #702775). Checksums-Sha1: 2cd1fe01ec91bd55fc3b199f8c75a8bc5f98 3039 ganglia_3.3.8-1+nmu1.dsc 2b5a4ce9714a9cd8fa755cf44c40610176b35339 21108 ganglia_3.3.8-1+nmu1.debian.tar.gz b2006ef3e1c8e0226e2a969d1584b57d5afa6334 57560 ganglia-monitor-python_3.3.8-1+nmu1_all.deb 6ebf3cb475cfbb56335967027e2bc6cac70fbc1a 662978 ganglia-webfrontend_3.3.8-1+nmu1_all.deb 9a7df6b3a62bf5c77aff7af9870d68f53973f601 81706 ganglia-monitor_3.3.8-1+nmu1_amd64.deb ab4375cbe9839ab2e81de875aa32051d2be98c45 37186 gmetad_3.3.8-1+nmu1_amd64.deb 2621e839a129ad7ec679aa9ecfd97025fb95545d 140108 libganglia1_3.3.8-1+nmu1_amd64.deb 8420d38b0da27048f0afab98f972afc0f503f063 48194 libganglia1-dev_3.3.8-1+nmu1_amd64.deb Checksums-Sha256: e3885e51fdc6d31b45442fc9eb0df6ca17711e04c3412df909ed5ae0f54cd43b 3039 ganglia_3.3.8-1+nmu1.dsc 89a4b9a346f6eaff8569d14f4871bbcdbf2bc49bdcf79a7edd78773cf9296b8a 21108 ganglia_3.3.8-1+nmu1.debian.tar.gz 0e279ee20971eccc9a06d03cbfccea2e6e4ba8c6e782c4fdce3498656eaeb488 57560 ganglia-monitor-python_3.3.8-1+nmu1_all.deb 32371be92ff385370e591732d21e1c2ae6c4ad7797d2fd8739a5fe74add1d967 662978 ganglia-webfrontend_3.3.8-1+nmu1_all.deb 393ae1790acd203bd9f0d9e4a1d5ee5aae91e828176cf50a9a7a1d54ef203c06 81706 ganglia-monitor_3.3.8-1+nmu1_amd64.deb 7dbbb1571c210f37bd84c32b3458df66b13e437668e38c1264f907a241d6a5c9 37186 gmetad_3.3.8-1+nmu1_amd64.deb a3c8f69f3ccf1a8a1c2ca6c9ba1dc65f3d1494cb0dc5888688b56a10e67cb2f1 140108
Bug#701936: Bug#701956: btrfs can't fsck /run/rootdev on boot
On Sun, Mar 17, 2013 at 01:56:22PM +0100, Nis Martensen wrote: On Fri, Mar 01, 2013 at 07:50:37AM +0100, Daniel Baumann wrote: works with systemd, it's sysvinit specific. Systemd skips the root file system check if the major device number of the root file system is 0 (which is what btrfs reports): http://cgit.freedesktop.org/systemd/systemd/tree/src/fsck/fsck.c#n297 The same could be done in sysvinit. Possible (untested) patch attached. Thanks for the patch. This will have to be deferred until after wheezy is released, but if we have to work around the btrfs fsck issues in this way, it looks like a reasonable approach. I would hope however that this would not be necessary, and that the btrfs fsck will become compatible with the standard /sbin/fsck options and behaviour, including being able to fsck a read-only mount, or else some users of btrfs won't be able to check their filesystems. Daniel, if you haven't done do already, it would be great if these issues could be brought to the attention of the upstream developers. As it stands, fsck.btrfs is not a compatible fsck, and this will break any tool expecting it to work like /sbin/fsck, not just sysvinit. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703265: lletters: crashes on most buttons on non-OSS3 systems
Hi Adam,
On Tue, 19 Mar 2013 10:14:35 +0100, Adam Borowski kilob...@angband.pl wrote:
On Mon, Mar 18, 2013 at 09:15:16PM +0100, Stephen Kitt wrote:
Alternatively, oss-compat is supposed to be used by packages such as
this one with a requirement for OSS. Adam, could you try installing it
to see if the modules it sets up allow lletters to work? It may not
play all that nicely with pulseaudio...
Works, but only after a reboot (I tested on a Debian-provided kernel in a
fresh wheezy install as well, to be sure). Having to reboot just to check
out a simple child game is not nice.
OK, thanks for checking; having to reboot is a bug, I'll look into it...
For Jessie we'll have osspd, but oss-compat or disabling audio as
Steven suggested seem to me to be the only options for Wheezy.
Here's another solution:
Depends: sox
if (!fork())
{
const char* arg[4];
arg[0] = /usr/bin/play;
arg[1] = -q;
arg[2] = the_file_to_play;
arg[3] = 0;
execve(arg[0], arg, environ);
exit(127);
}
Works on all sound systems, doesn't crash if no sound is available, doesn't
hang on 64 bit architectures (and I guess big-endian too), supports formats
other than .wav (in case someone localizes sounds). And doesn't use that
ridiculous code with more leaks than ${SOME_MICROSOFT_SLUR}.
One could use, say, SDL_sound to avoid the fork(), but come on, let's be
serious.
Indeed, that seems better all around!
Regards,
Stephen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694870: Bug#699109: unblock (pre-approval): initramfs-tools-tcos/0.89.91
user release.debian@packages.debian.org usertag 699109 + wheezy-will-remove usertag 694870 + wheezy-will-remove thanks On Fri, Mar 01, 2013 at 02:14:58PM +0100, Julien Cristau wrote: On Mon, Jan 28, 2013 at 09:22:35 +, Manuel A. Fernandez Montecelo wrote: 2013/1/27 Julien Cristau jcris...@debian.org: On Sun, Jan 27, 2013 at 17:42:48 +, Manuel A. Fernandez Montecelo wrote: Could Release Team please say if the changes proposed in #694870 to fix an RC bug are OK to go? Please include an actual diff in this bug instead of a pointer to $somewhere_else. Attached. According to the discussion in that bug report, the patch does need to be so big to fix three separate issues, and without the fixes it seems that the software will not be functional. I'm not overly happy with this patch. The multiarch fixes just hardcode two paths in an arch:all package with no apparent x86 dependency. And the /etc/console-setup stuff looks like it'd break if two files match the glob. I'm more tempted by a removal at this point to be honest. Is there any progress on this? With a low popcon, maintainer seemingly unresponsive, RC buggy and never in a stable release, please note that removal will happen in a few days if this can't be resolved a better way. Thanks, -- 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#703468: linux-image-3.2.0-4-amd64 fails to boot on apple iMac
Package: src:linux Version: 3.2.39-2 Severity: grave Dear Maintainer, I upgraded to the 3.2.39-2 package last night, and this morning my system wouldn't boot. I used Marco's advice in #551798 to set init=/bin/bash, and found the boot stopped after running /etc/rcS.d/S02udev. Sometimes there would be a screen full of kernel messages, that ended in a message like: fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Sorry I can't provide more details, I didn't take a photo of the screen. Using by init=/bin/bash shell I downgraded the kernel package to the 3.2.35-2 package (which was what I was running prior to yesterdays upgrade), and my system booted successfully. The attached linux-image-reportbugoutput file was generated by running: $ reportbug -q --template -T none -s none -S normal -b --list-cc none -q linux-image-3.2.0-4-amd64 ~/tmp/linux-image-reportbugoutput Please note that this reportbug run was while running on the 3.2.35-2 package of the kernel, so some of the details will be misleading. Include network configuration and status from this computer? Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Geoff Crompton geo...@trinity.unimelb.edu.au To: Debian Bug Tracking System sub...@bugs.debian.org Subject: linux-image-3.2.0-4-amd64: none X-Debbugs-Cc: none Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=UUID=7de8ea19-10bf-4b66-a1e3-a14e6ac34d80 ro quiet ** Not tainted ** Kernel log: [ 11.154250] ATOM BIOS: Apple [ 11.154260] [drm] GPU not posted. posting now... [ 11.172389] radeon :01:00.0: VRAM: 512M 0x - 0x1FFF (512M used) [ 11.172391] radeon :01:00.0: GTT: 512M 0x2000 - 0x3FFF [ 11.174594] [drm] Detected VRAM RAM=512M, BAR=256M [ 11.174596] [drm] RAM width 128bits DDR [ 11.174675] [TTM] Zone kernel: Available graphics memory: 2019148 kiB. [ 11.174677] [TTM] Initializing pool allocator. [ 11.174711] [drm] radeon: 512M of VRAM memory ready [ 11.174713] [drm] radeon: 512M of GTT memory ready. [ 11.174726] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 11.174727] [drm] Driver supports precise vblank timestamp query. [ 11.174765] radeon :01:00.0: irq 50 for MSI/MSI-X [ 11.174770] radeon :01:00.0: radeon: using MSI. [ 11.174814] [drm] radeon: irq initialized. [ 11.174817] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 11.175157] [drm] Loading TURKS Microcode [ 11.264106] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 11.264325] usbcore: registered new interface driver btusb [ 11.338630] platform radeon_cp.0: firmware: agent loaded radeon/TURKS_pfp.bin into memory [ 11.526432] platform radeon_cp.0: firmware: agent loaded radeon/TURKS_me.bin into memory [ 11.612326] platform radeon_cp.0: firmware: agent loaded radeon/BTC_rlc.bin into memory [ 11.662351] platform radeon_cp.0: firmware: agent loaded radeon/TURKS_mc.bin into memory [ 11.665046] [drm] PCIE GART of 512M enabled (table at 0x0004). [ 11.665170] radeon :01:00.0: WB enabled [ 11.681439] [drm] ring test succeeded in 2 usecs [ 11.681532] [drm] radeon: ib pool ready. [ 11.681635] [drm] ib test succeeded in 0 usecs [ 11.683096] [drm] Radeon Display Connectors [ 11.683097] [drm] Connector 0: [ 11.683098] [drm] eDP [ 11.683099] [drm] HPD3 [ 11.683101] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c [ 11.683102] [drm] Encoders: [ 11.683104] [drm] LCD1: INTERNAL_UNIPHY2 [ 11.683105] [drm] Connector 1: [ 11.683106] [drm] DisplayPort [ 11.683107] [drm] HPD1 [ 11.683108] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [ 11.683109] [drm] Encoders: [ 11.683110] [drm] DFP1: INTERNAL_UNIPHY1 [ 11.683112] [drm] Connector 2: [ 11.683112] [drm] DisplayPort [ 11.683113] [drm] HPD2 [ 11.683115] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [ 11.683116] [drm] Encoders: [ 11.683117] [drm] DFP2: INTERNAL_UNIPHY1 [ 11.683118] [drm] Connector 3: [ 11.683119] [drm] DisplayPort [ 11.683120] [drm] HPD5 [ 11.683121] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c [ 11.683123] [drm] Encoders: [ 11.683124] [drm] DFP3: INTERNAL_UNIPHY2 [ 11.683125] [drm] Connector 4: [
Bug#703472: iceweasel freezes on some site due to bad handling of mailcap file
Package: iceweasel
Version: 19.0.2-1
Severity: grave
Justification: causes non-serious data loss
Iceweasel freezes in a futex syscall on some site; it doesn't redraw
anything and doesn't take CPU time. Unfortunately this occurs on a
private page (I just try to download my latest EDF invoice). This
problem is reproducible.
Iceweasel-related processes given by ps -aef:
UIDPID PPID C STIME TTY TIME CMD
vinc17 29321 29161 28 02:49 pts/13 00:02:55 iceweasel
vinc17 29650 29321 0 02:54 pts/13 00:00:00 [sh] defunct
and in the terminal:
$ iceweasel
ACR (Component): component init
NOTE: child process received `Goodbye', closing down
WARNING: waitpid failed pid:29459 errno:10: file
/tmp/buildd/iceweasel-19.0.2/ipc/chromium/src/base/process_util_posix.cc, line
260
[ConvConfHandler] isPreferred contentType: application/pdf
WARNING: waitpid failed pid:29459 errno:10: file
/tmp/buildd/iceweasel-19.0.2/ipc/chromium/src/base/process_util_posix.cc, line
260
WARNING: waitpid failed pid:29459 errno:10: file
/tmp/buildd/iceweasel-19.0.2/ipc/chromium/src/base/process_util_posix.cc, line
260
WARNING: Failed to deliver SIGKILL to 29459!(3).: file
/tmp/buildd/iceweasel-19.0.2/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc,
line 118
$ strace -p 29321
Process 29321 attached - interrupt to quit
futex(0x7febc36ca3cc, FUTEX_WAIT_PRIVATE, 1, NULL
$ gdb =iceweasel 29321
[...]
(gdb) set pagination off
(gdb) bt full
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
No locals.
#1 0x7fec5514dd90 in PR_WaitCondVar (cvar=0x7febc36ca3c0,
timeout=timeout@entry=4294967295) at ptsynch.c:385
rv = optimized out
thred = 0x7fec5aa59260
#2 0x7fec55156384 in _MD_WaitUnixProcess (process=0x7fec05fca080,
exitCode=0x7fff136bb234) at uxproces.c:824
pRec = 0x7febbeb2d260
retVal = PR_SUCCESS
interrupted = 0
#3 0x7fec595bce0c in nsProcess::Monitor (arg=arg@entry=0x7febd99e27f0) at
/tmp/buildd/iceweasel-19.0.2/xpcom/threads/nsProcessCommon.cpp:264
process = {mRawPtr = 0x7febd99e27f0}
exitCode = -1
#4 0x7fec595bcfc9 in nsProcess::RunProcess
(this=this@entry=0x7febd99e27f0, blocking=blocking@entry=true,
my_argv=my_argv@entry=0x7fec225c13c0, observer=observer@entry=0x0,
holdWeak=holdWeak@entry=false, argsUTF8=argsUTF8@entry=false) at
/tmp/buildd/iceweasel-19.0.2/xpcom/threads/nsProcessCommon.cpp:512
ptrProc = optimized out
#5 0x7fec595bd212 in nsProcess::CopyArgsAndRunProcess
(this=0x7febd99e27f0, blocking=true, args=0x7fff136bb468, count=optimized
out, observer=0x0, holdWeak=false) at
/tmp/buildd/iceweasel-19.0.2/xpcom/threads/nsProcessCommon.cpp:357
my_argv = 0x7fec225c13c0
rv = optimized out
#6 0x7fec592add37 in
nsOSHelperAppService::GetHandlerAndDescriptionFromMailcapFile (aFilename=...,
aMajorType=..., aMinorType=..., aTypeOptions=..., aHandler=...,
aDescription=..., aMozillaFlags=...) at
/tmp/buildd/iceweasel-19.0.2/uriloader/exthandler/unix/nsOSHelperAppService.cpp:1102
testCommand = {nsFixedCString = {nsCString = {nsACString_internal
= {mData = 0x7fff136bb508 test -n \$DISPLAY\, mLength = 18, mFlags =
65553}, No data fields}, mFixedCapacity = 63, mFixedBuf = 0x7fff136bb508
test -n \$DISPLAY\}, mStorage = test -n
\$DISPLAY\\000Y\354\177\000\000\270\265k\023\377\177\000\000w\303*Y\354\177\000\000\200a[\034\354\377\372\377\270\265k\023\377\177\000\000`P\\\034\354\377\372\377}
process = {nsCOMPtr_base = {mRawPtr = 0x7febd99e27f0}, No data
fields}
file = {nsCOMPtr_base = {mRawPtr = 0x7febd03310c0}, No data fields}
exitValue = 0
args = {0x7fec59a68ddc -c, 0x7fff136bb508 test -n \$DISPLAY\}
optionName = {nsAString_internal = {mData = 0x7febcee9d5b0, mLength =
4, mFlags = 0}, No data fields}
match = optimized out
end_executable_iter = optimized out
start_option_iter = optimized out
end_optionname_iter = {mStart = optimized out, mEnd = optimized
out, mPosition = 0x7febcee9d5b8}
equal_sign_iter = optimized out
equalSignFound = false
semicolon_iter = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654,
mPosition = 0x7febcee9d5de}
end_iter = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654, mPosition =
0x7febcee9d654}
majorTypeEnd = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654,
mPosition = 0x7febcee9d58e}
minorTypeEnd = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654,
mPosition = 0x7febcee9d596}
start_iter = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654, mPosition
= 0x7febcee9d59a}
majorTypeStart = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654,
mPosition = 0x7febcee9d578}
minorTypeStart = {mStart = 0x7febcee9d578, mEnd = 0x7febcee9d654,
mPosition = 0x7febcee9d590}
rv = 4294966784
file = {nsCOMPtr_base = {mRawPtr = 0x7febcf2a4e80}, No data fields}
Processed: re: Kill local user processes on logout
Processing control commands: severity -1 important Bug #701916 [ltsp-client-core] Kill local user processes on logout Severity set to 'important' from 'grave' -- 701916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 703330 patch Bug #703330 [src:tcltk-defaults] missing Conflict/Repleace files `/usr/include/tcl', also in package deprecated tk-tile Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 703330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: close 656877 Bug #656877 [flash-kernel] flash-kernel is not being run for kernel upgrades with unchanged ABI version Bug #673418 [flash-kernel] flash-kernel is not being run for kernel upgrades with unchanged ABI version Bug #701781 [flash-kernel] linux-image-2.6.32-5-kirkwood: Cannot load usbcore kernel module Marked Bug as done Marked Bug as done Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 656877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656877 673418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673418 701781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
