Bug#694048: havoc and distruption ^_^
Some explanation why you see different behaviour between sysvinit and systemd: systemd internally translates restart to stop + start, i.e. it calls /etc/init.d/foo stop /etc/init.d/foo start. That's why the sleep 1 hack is only active under sysvinit. I bet, if you removed the sleep 1 in restart), you'd run into the same problem under sysvinit. Hm it makes sense... In the end, those are just bugs in the sysv init scripts which are papered over by sprinkling a sleep here and there. Well since bash programming isn't C or Python and there are no callbacks, usually in bash functions (which are executable files) should be synchronous rather than asynchronous. Start-stop-daemon terminates when the signal has been sent, not when the process has terminated, waiting for the process to terminate would make the scripts easier. After all they are trying to stop a daemon not to send a signal, so they are interested in the effective termination of the process. In alternative all the scripts should do the following: start-stop-daemon --stop (waitpid; start-stop-daemon --start) Which is quite unreadable as pseudo-bash-code, it would be even worst as real working bash. The sleep is just a poor workaround for a problem in start-stop-daemon, by putting a waitpid in it, all those sleeps during the restart could be safely eliminated. -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Bug#694872: Why was this bug closed?
Hi Mike, On Sun, Dec 02, 2012 at 03:20:25PM -0500, Michael Gilbert wrote: Well, I thought this was only the case when there is no other option, because the version has to be smaller than the one in unstable (when testing has 4.3.6-1 and unstable has 4.3.6-2 with unacceptable changes). I did a t-p-u update like this (without the deb7u suffix) yesterday (for fossil), which was approved by the release team without any remarks. But I'm happy to change the version number if you like. +debXuY is the correct suffix for updates to wheezy and all future stable releases. See: http://bugs.debian.org/542288 Well, the discussion is about what the suffix should be, not when it should be used. And there isn't really any sign of consensus about '+debXuY' in the bug report. Several possibilities are mentioned, but +debXuY is only mentioned twice, both times by you. That consensus was probably reached elsewhere. If you read the proposed policy text, it only talk about the non-native package was uploaded by someone other than the maintainer, which is the case in my upload. It doesn't talk about proposed updates (in the entire bug report, proposed updates is only mentioned once, in reference to a change in the upload checks). In fact, if you read the proposed policy text strictly, it forces the use of '.1' (non-native) or +nmu1 (native or non-native) on ALL NMU's, without exceptions for proposed updates (or even security updates). I don't know if that's the intention of the proposal. This is also what dch currently does, even with '--security'. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694978: RFP: liblinux-prctl-perl -- Perl interface to Linux's prctl(2) call
Package: wnpp Severity: wishlist * Package name: liblinux-prctl-perl Version : 1.5.0 Upstream Author : Dennis Kaarsemaker den...@kaarsemaker.net * URL : http://search.cpan.org/~seveas/Linux-Prctl/ * License : GPLv3 or later Programming Lang: Perl Description : Perl interface to Linux's prctl(2) call The reason I need this is to use the PR_SET_PDEATHSIG functionality (see prctl(2)), which is exposed through set_pdeathsig in this Perl module, but most of prctl(2)'s functionality appears to be made available to Perl by this module. The application in which I'm using set_pdeathsig is sigtr - see https://github.com/tomgjones/sigtr. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505924: cwm
James, Thanks. I have downloaded and I will look. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694872: Why was this bug closed?
On Sun, Dec 2, 2012 at 4:31 PM, Ivo De Decker wrote: Hi Mike, On Sun, Dec 02, 2012 at 03:20:25PM -0500, Michael Gilbert wrote: Well, I thought this was only the case when there is no other option, because the version has to be smaller than the one in unstable (when testing has 4.3.6-1 and unstable has 4.3.6-2 with unacceptable changes). I did a t-p-u update like this (without the deb7u suffix) yesterday (for fossil), which was approved by the release team without any remarks. But I'm happy to change the version number if you like. +debXuY is the correct suffix for updates to wheezy and all future stable releases. See: http://bugs.debian.org/542288 Well, the discussion is about what the suffix should be, not when it should be used. And there isn't really any sign of consensus about '+debXuY' in the bug report. Several possibilities are mentioned, but +debXuY is only mentioned twice, both times by you. That consensus was probably reached elsewhere. Yes. I don't have a link to the final decision, but you can easily verify the veracity of that statement by looking at the versioning of packages that have gone through tpu recently (e.g. cdbs, underscore, etc.). Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694979: debbugs: get_bugs() should allow specifying binary versions of packages
Package: debbugs Severity: wishlist Hello, as discussed via private e-mail with Don Armstrong, I would need the following enhancement in the BTS SOAP interface, in order to enhance apt-listbugs (which I maintain). Currently, one of the procedures that apt-listbugs calls via SOAP is get_bugs(), with arguments like (in Ruby): ('severity', [critical, grave], 'package', [pkg1, pkg2, pkg3]) which results in the following SOAP request: ?xml version=1.0 encoding=utf-8 ? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; env:Body n1:get_bugs env:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:n1=Debbugs/SOAP/ keyvalue xmlns:n2=http://schemas.xmlsoap.org/soap/encoding/; n2:arrayType=xsd:anyType[4] xsi:type=n2:Array item xsi:type=xsd:stringseverity/item item n2:arrayType=xsd:anyType[2] xsi:type=n2:Array item xsi:type=xsd:stringcritical/item item xsi:type=xsd:stringgrave/item /item item xsi:type=xsd:stringpackage/item item n2:arrayType=xsd:anyType[3] xsi:type=n2:Array item xsi:type=xsd:stringpkg1/item item xsi:type=xsd:stringpkg2/item item xsi:type=xsd:stringpkg3/item /item /keyvalue /n1:get_bugs /env:Body /env:Envelope This returns an array with all the (unarchived) bug-numbers that are assigned to one of the mentioned binary packages and have one of the mentioned severities. In order to get over a limitation of apt-listbugs (which gets confused [1] about version tracking info whenever the source version of a package differs from the corresponding binary version) and in order to fix another bug (apt-listbugs gets confused [2] about version tracking info in certain cases where a bug is assigned to more than one package), I would need to call the procedure differently, as explained below. [1] http://bugs.debian.org/257873#24 [2] http://bugs.debian.org/693291 I would need to call get_bugs() so that it returned an array with all the (unarchived) bug-numbers that apply to the specified binary version of one of the mentioned binary packages and have one of the mentioned severities. Something like: get_bugs('severity', [critical, grave], 'package', [pkg1/x.y-z, pkg2, pkg3/a.b.c-d]) which would request the bugs that apply to binary version x.y-z of binary package pkg1, the bugs that apply to any version of binary package pkg2, and the bugs that apply to binary version a.b.c-d of binary package pkg3. Or some other way to obtain the same result with a single procedure call. Of course, when I say that a bug applies to a given package version, I mean that the bug is present in that binary version, as long as the BTS version tracking knows. I am convinced that the BTS has all the information needed to determine which bugs apply to a given binary version of a binary package, and hence it should be possible to ask it through the SOAP interface. It would be really really great, if you could implement a way to obtain what I described with one single get_bugs() SOAP request. Please, please, think about it! Thanks for your time, I really hope this can be implemented... Bye. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694980: dpkg: start-stop-daemon should wait when stopping the daemon
Package: dpkg Version: 1.16.9 Severity: normal Dear Maintainer, after inspecting start-stop-daemon's source, i couldn't find any wait/waitpid calls, and they should exist. Stopping a daemon usually consists in sending a message to the right pid, but after that it would be better to do a waitpid so that the command terminates when the daemon has really stopped, not just when the signal has been sent. This would allow scripts to be simpler because they would know that after a start-stop-daemon --stop, the daemon has in fact stopped; and it's not the case right now. This leads maintainers to insert sleeps in the scripts to hope that in the meanwhile the daemon will terminate (the correct approach would be to insert wait on the pid); but the even more correct approach would be to fix start-stop-daemon so that when it exits the daemon has stopped. Bash programming isn't usually event-based, so when a command terminates it is supposed to be done with its job. Bye -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.8a-1000-preemptive (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-4 ii libc62.13-37 ii liblzma5 5.1.1alpha+20120614-2 ii libselinux1 2.1.9-5 ii tar 1.26-4 ii zlib1g 1:1.2.7.dfsg-13 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.9.7.6 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: Current options for resolving 688772 [Re: Bug#688772: gnome Depends network-manager-gnome]
On Sun, 02 Dec 2012, Russ Allbery wrote: Don Armstrong d...@debian.org writes: This is the current text of the options for #688772. I'd like to vote on this before the 9th if at all possible. If anyone has any comments, changes, or would like to propose different options, please do so now. After considering this and following the discussion, I'm not willing to vote for either A or B, and would end up voting further discussion. I'd like to add an option C, along the lines of: [...] Ok, so this option C would involve not overriding the maintainer, coupled with requesting documentation in the release notes, and would also supplant 5 and 6 in the A and B versions. I've gone ahead and updated the current don_draft.txt with this text as written with the other options. In other words, my *preferred* option is B with the fix to the network-manager package, but B as phrased has consequences for not getting that fix done in time that I'm not comfortable with. I believe that the fixes outlined in option B are going to get implemented regardless of how the CTTE rules; the primary goal of B is to make the gnome dependency on NM conditional on those fixes being implemented. [And if that's not clear from the text of B, that's something that I would like to resolve.] Don Armstrong -- He was wrong. Nature abhors dimensional abnormalities, and seals them neatly away so that they don't upset people. Nature, in fact, abhors a lot of things, including vacuums, ships called the Marie Celeste, and the chuck keys for electric drills. -- Terry Pratchet _Pyramids_ p166 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694872: Why was this bug closed?
Mike, On Sun, Dec 02, 2012 at 04:36:23PM -0500, Michael Gilbert wrote: Yes. I don't have a link to the final decision, but you can easily verify the veracity of that statement by looking at the versioning of packages that have gone through tpu recently (e.g. cdbs, underscore, etc.). Sure, I'm not disputing that. I'm just saying that the bug report doesn't really help. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683554: php-kolab-...
2012/12/1 Mathieu Parent math.par...@gmail.com: # Broken Depends: php-kolab-filter: php-kolab-filter php-kolab-freebusy: php-kolab-freebusy Should I remove kolabd too? It's a reverse dependency of both packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693291: apt-listbugs: doesn't show a serious bug
Control: block -1 by 694979 Control: severity -1 normal On Mon, 19 Nov 2012 23:16:17 +0100 Francesco Poli wrote: [...] I really need to figure out a different approach... The only sane way I could think of requires a new feature in the BTS SOAP interface. I've just opened a wishlist bug [1] to request this enhancement for the BTS. [1] http://bugs.debian.org/694979 I hope this may be implemented soon, so that I can modify apt-listbugs to take advantage of it... Bye. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpPUk4EqM8UE.pgp Description: PGP signature
Bug#694872: Why was this bug closed?
On Sun, Dec 2, 2012 at 4:41 PM, Ivo De Decker wrote: Mike, On Sun, Dec 02, 2012 at 04:36:23PM -0500, Michael Gilbert wrote: Yes. I don't have a link to the final decision, but you can easily verify the veracity of that statement by looking at the versioning of packages that have gone through tpu recently (e.g. cdbs, underscore, etc.). Sure, I'm not disputing that. I'm just saying that the bug report doesn't really help. It helps because it has the origin, reasoning, history, and context for the move to +dsomething for stable updates. Although I really don't understand why this needs debating... Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694302: icedove: crashes at creating new account.
Hello Alexey, On Sun, Nov 25, 2012 at 01:46:20PM +0600, Alexey Gunyakov wrote: Package: icedove Version: 3.0.11-1+squeeze14 Severity: important I'm trying to add new mail account to the IceDove v3.0.11 File, New, Mail account... After I typed in my name, e-mail address and managed to press Continue button incoming mail server and outgoing server were successfully fullfilled automatically. Create account button leads to crash without any mistakes. Icedove windows just dissapear. is there a deeper reason not to use the latest version from backports or the current version 10.0.11 from mozilla.debian.net? If this happen in newer version too or you not willing to update your version please provide some logs as decribed in the wiki how to get them. http://wiki.debian.org/Icedove#Debugging Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: Current options for resolving 688772 [Re: Bug#688772: gnome Depends network-manager-gnome]
Don Armstrong d...@debian.org writes: Ok, so this option C would involve not overriding the maintainer, coupled with requesting documentation in the release notes, and would also supplant 5 and 6 in the A and B versions. Ah, yes, indeed, it would. I've gone ahead and updated the current don_draft.txt with this text as written with the other options. Thanks! I believe that the fixes outlined in option B are going to get implemented regardless of how the CTTE rules; the primary goal of B is to make the gnome dependency on NM conditional on those fixes being implemented. [And if that's not clear from the text of B, that's something that I would like to resolve.] If that does happen, of course, I'm happy to support B. I don't know how much progress has already been made on that. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617613: Granting wheezy-ignore tag bug
Just for the record. The bug #694975 against release.debian.org for granting a wheezy-ignore tag has been filed. Thanks. Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694395: libshell-command-perl: missing Breaks+Replaces: libextutils-command-perl
On Sun, 2012-12-02 at 08:47 +0100, Salvatore Bonaccorso wrote: @Adam, the unblock hint for 0.06-2 get's invalid thus, sorry about that. Updated for -3; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660525: [PATCH] Fix libffi on m68k-linux-gnu, completely
Dixi quod… Hello Debian libffi maintainer, you will receive patches in a separate message against unstable (3.0.10) and experimental (3.0.11) as well as gcc-4.7 (uses something close to 3.0.10 but not quite). OK, attached are: • Patch against libffi from unstable ‣ symbols file change: --- debian/libffi5.symbols.m68k (libffi5_3.0.10-3+m68k.4_m68k) +++ dpkg-gensymbolsKl0ncP 2012-12-02 22:08:22.0 + @@ -14,6 +14,7 @@ ffi_prep_args@Base 3.0.4 ffi_prep_cif@Base 3.0.4 ffi_prep_cif_machdep@Base 3.0.4 + ffi_prep_cif_var@Base 3.0.10-3+m68k.4 ffi_prep_closure@Base 3.0.4 ffi_prep_closure_loc@Base 3.0.4 ffi_prep_java_raw_closure@Base 3.0.4 • Patch against libffi from experimental (with the caveat that I believe some testcases to be broken; the patch adds no new failures) • Drop-in replacement for debian/patches/libffi-m68k.diff in gcc-4.7_4.7.2-12 I’m keeping the gcc-4.6 patch separate, as I’m currently juggling a larger m68k related patchset, which I’ll post occasionally to #694112 to be applied after the unfreeze. Andreas, I think you can commit the GCC side of the patch as well, so I’ll keep debian-68k on Cc for the followup message with them. See above ;) bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh--- a/src/libffi/src/m68k/ffi.c +++ b/src/libffi/src/m68k/ffi.c @@ -107,6 +107,8 @@ ffi_prep_args (void *stack, extended_cif #define CIF_FLAGS_POINTER 32 #define CIF_FLAGS_STRUCT1 64 #define CIF_FLAGS_STRUCT2 128 +#define CIF_FLAGS_SINT8256 +#define CIF_FLAGS_SINT16 512 /* Perform machine dependent cif processing */ ffi_status @@ -120,6 +122,13 @@ ffi_prep_cif_machdep (ffi_cif *cif) break; case FFI_TYPE_STRUCT: + if (cif-rtype-elements[0]-type == FFI_TYPE_STRUCT + cif-rtype-elements[1]) +{ + cif-flags = 0; + break; +} + switch (cif-rtype-size) { case 1: @@ -163,6 +172,14 @@ ffi_prep_cif_machdep (ffi_cif *cif) cif-flags = CIF_FLAGS_DINT; break; +case FFI_TYPE_SINT16: + cif-flags = CIF_FLAGS_SINT16; + break; + +case FFI_TYPE_SINT8: + cif-flags = CIF_FLAGS_SINT8; + break; + default: cif-flags = CIF_FLAGS_INT; break; @@ -261,7 +278,8 @@ ffi_prep_closure_loc (ffi_closure* closu void *user_data, void *codeloc) { - FFI_ASSERT (cif-abi == FFI_SYSV); + if (cif-abi != FFI_SYSV) +return FFI_BAD_ABI; *(unsigned short *)closure-tramp = 0x207c; *(void **)(closure-tramp + 2) = codeloc; --- a/src/libffi/src/m68k/ffitarget.h +++ b/src/libffi/src/m68k/ffitarget.h @@ -34,8 +34,8 @@ typedef signed longffi_sarg; typedef enum ffi_abi { FFI_FIRST_ABI = 0, FFI_SYSV, - FFI_DEFAULT_ABI = FFI_SYSV, - FFI_LAST_ABI = FFI_DEFAULT_ABI + 1 + FFI_LAST_ABI, + FFI_DEFAULT_ABI = FFI_SYSV } ffi_abi; #endif --- a/src/libffi/src/m68k/sysv.S +++ b/src/libffi/src/m68k/sysv.S @@ -2,6 +2,7 @@ sysv.S - Copyright (c) 1998, 2012 Andreas Schwab Copyright (c) 2008 Red Hat, Inc. + Copyright (c) 2012 Thorsten Glaser m68k Foreign Function Interface @@ -153,8 +154,22 @@ retstruct1: retstruct2: btst#7,%d2 - jbeqnoretval + jbeqretsint8 move.w %d0,(%a1) + jbraepilogue + +retsint8: + btst#8,%d2 + jbeqretsint16 + extb.l %d0 + move.l %d0,(%a1) + jbraepilogue + +retsint16: + btst#9,%d2 + jbeqnoretval + ext.l %d0 + move.l %d0,(%a1) noretval: epilogue: @@ -186,8 +201,10 @@ ffi_closure_SYSV: lsr.l #1,%d0 jne 1f jcc .Lcls_epilogue + | CIF_FLAGS_INT move.l -12(%fp),%d0 .Lcls_epilogue: + | no CIF_FLAGS_* unlk%fp rts 1: @@ -195,6 +212,7 @@ ffi_closure_SYSV: lsr.l #2,%d0 jne 1f jcs .Lcls_ret_float + | CIF_FLAGS_DINT move.l (%a0)+,%d0 move.l (%a0),%d1 jra .Lcls_epilogue @@ -209,6 +227,7 @@ ffi_closure_SYSV: lsr.l #2,%d0 jne 1f jcs .Lcls_ret_ldouble + | CIF_FLAGS_DOUBLE #if defined(__MC68881__) || defined(__HAVE_68881__) fmove.d (%a0),%fp0 #else @@ -227,17 +246,31 @@ ffi_closure_SYSV: jra .Lcls_epilogue 1: lsr.l #2,%d0 - jne .Lcls_ret_struct2 + jne 1f jcs .Lcls_ret_struct1 + | CIF_FLAGS_POINTER move.l (%a0),%a0 move.l %a0,%d0 jra .Lcls_epilogue .Lcls_ret_struct1: move.b (%a0),%d0 jra .Lcls_epilogue -.Lcls_ret_struct2:
Bug#660525: [PATCH] Fix libffi on m68k-linux-gnu, completely
Note: Doko and Andreas, you’re mentioned further below. Andreas Schwab dixit: Alan Hourihane al...@fairlite.co.uk writes: Fixed the test, as it was broken. No, it isn't. Hi you two, I’ve seen you fixed all failures than the (above discussed) return_sc. I took care of that one today. (If I get my hands on the person responsible for the lsr.l codepath, when the other routine uses something so much easier to spot, thus being so temptingly easy, making me not look harder… this cost me quite some time today!) Hello libffi developers upstream, please do apply the attached patch against git master, and then mark m68k-linux-gnu as working/tested platform. I’m getting a full testsuite pass for both 3.0.10 with the m68k code updated, and no new failures for 3.0.11 with the patch applied although I believe some 3.0.11 checks to be broken: The cls_uchar.c test has: static void cls_ret_uchar_fn(ffi_cif* cif __UNUSED__, void* resp, void** args, void* userdata __UNUSED__) { *(ffi_arg*)resp = *(unsigned char *)args[0]; The cls_uchar_va.c test has (T expanded): static void cls_ret_T_fn(ffi_cif* cif __UNUSED__, void* resp, void** args, void* userdata __UNUSED__) { *(unsigned char *)resp = *(unsigned char *)args[0]; Now, on big endian platforms, the result is quite different: Assuming we call them with args[0]=0x7F, then: Before: *(unsigned long *)resp = { 0x??, 0x??, 0x??, 0x?? } After1: *(unsigned long *)resp = { 0x00, 0x00, 0x00, 0x7F } After2: *(unsigned long *)resp = { 0x7F, 0x??, 0x??, 0x?? } The failing tests are contributed by ARM, who are using Little Endian, or so I’m told, so it’s no surprise they didn’t notice. What’s the correct method to access *resp in a closure, casting to the “real” return type or to an ffi_arg pointer (the latter is used by all other/older tests, i.e. all those predating arm64 support). The failing tests (both before and after my patch) are: libffi.call/cls_uchar_va.c cls_ushort_va.c va_1.c The following exemplary patch makes one of them pass: --- cls_uchar_va.c 2012-12-02 21:34:19.0 + +++ cls_uchar_va2.c 2012-12-02 22:26:37.0 + @@ -12,9 +12,9 @@ static void cls_ret_T_fn(ffi_cif* cif __UNUSED__, void* resp, void** args, void* userdata __UNUSED__) { - *(T *)resp = *(T *)args[0]; + *(ffi_arg *)resp = *(T *)args[0]; - printf(%d: %d %d\n, *(T *)resp, *(T *)args[0], *(T *)args[1]); + printf(%d: %d %d\n, (int)(*(ffi_arg *)resp), *(T *)args[0], *(T *)args[1]); } typedef T (*cls_ret_T)(T, ...); And, WTF: Why is there a .pc directory in the git repository? Hello Debian libffi maintainer, you will receive patches in a separate message against unstable (3.0.10) and experimental (3.0.11) as well as gcc-4.7 (uses something close to 3.0.10 but not quite). Andreas, I think you can commit the GCC side of the patch as well, so I’ll keep debian-68k on Cc for the followup message with them. bye, //mirabilos -- Darwinism never[…]applied to wizardkind. There's a more than fair amount of[…] stupidity in its gene-pool[…]never eradicated[…]magic evens the odds that way. It's[…]harder to die for us than[…]muggles[…]wonder if, as technology[…]better […]same will[…]happen there too. Dursleys' continued existence indicates so.From 9dd3345b2ef98b1fc18a1381cfe46b0381d71777 Mon Sep 17 00:00:00 2001 From: Thorsten Glaser t...@mirbsd.org Date: Sun, 2 Dec 2012 20:11:37 + Subject: [PATCH] Fix 8-bit and 16-bit signed calls on m68k Note: return_sc only tests 8-bit calls; I wrote myself a small return_ss testcase which is the same except using signed short TODO: src/m68k/sysv.S uses two different styles, one uses a bit test command and simple jumps, the other rather convoluted right-shifts through carry by two and three-way jumps. This should be unified and documented better; also, the label naming differs greatly between the call and the closure function. Signed-off-by: Thorsten Glaser t...@mirbsd.org --- src/m68k/ffi.c | 10 ++ src/m68k/sysv.S | 39 --- 2 files changed, 46 insertions(+), 3 deletions(-) diff --git a/src/m68k/ffi.c b/src/m68k/ffi.c index 37a0784..0dee938 100644 --- a/src/m68k/ffi.c +++ b/src/m68k/ffi.c @@ -123,6 +123,8 @@ ffi_prep_args (void *stack, extended_cif *ecif) #define CIF_FLAGS_POINTER 32 #define CIF_FLAGS_STRUCT1 64 #define CIF_FLAGS_STRUCT2 128 +#define CIF_FLAGS_SINT8256 +#define CIF_FLAGS_SINT16 512 /* Perform machine dependent cif processing */ ffi_status @@ -200,6 +202,14 @@ ffi_prep_cif_machdep (ffi_cif *cif) cif-flags = CIF_FLAGS_DINT; break; +case FFI_TYPE_SINT16: + cif-flags = CIF_FLAGS_SINT16; + break; + +case FFI_TYPE_SINT8: + cif-flags = CIF_FLAGS_SINT8; + break; + default: cif-flags = CIF_FLAGS_INT; break; diff --git a/src/m68k/sysv.S b/src/m68k/sysv.S index f6f4ef9..42f520b 100644 --- a/src/m68k/sysv.S
Bug#672972: Wheezy: VLC player can't play videos
I am having a similar problem here using Debian (Sid/Unstable) using an ATI Radeon 9000 on a 32 bit IBM compatible computer. The VLC player shows the first frame and does not proceed any further. On the same machine mplayer2 works just fine and plays the same video. There must be something different in the way that the vlc player and mplayer2 handle the video. Maybe it would be useful if vlc could be configured to use the mplayer2 video handling code.
Bug#281639: sed: documentation is non-free
* Clint Adams sch...@debian.org, 2004-11-17, 11:43: The manual is free as long as there are no invariant sections, isn't it? I think there was a consensus previously that the GNU FDL was free as long as there were no Invariant Sections or Cover Texts. Indeed. So the bug should be closed... If the documentation could be relicensed under the GPL, or dual-licensed under the GPL and FDL, I think everyone might be satisfied. ...or, if someone still cares about dual-licensing, retitled. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664611: Source package contains non-free IETF RFC/I-D
* Simon Josefsson si...@josefsson.org, 2012-03-21, 12:17: clone 664611 -1 -2 retitle -1 Source package contains non-free IETF RFC/I-D severity -1 serious Both #665937... retitle -2 asterisk: private copy of libilbc (license issue) thanks ...and #665938 have been fixed. I'm not sure what _this_ (#664611) bug is about. It has the very same title as #665937. Should it be closed? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668740: 668740 not release critical
severity 668740 important thanks Hi, checking with http://release.debian.org/wheezy/rc_policy.txt I still don't see why this bug is serious or above. Please note that the mentioned document is the canoncial definition of release critical bugs. Setting the bug to important only means I don't think it is serious or above. Otherwise, as always it is the maintainers decision to set the bug to an appropriate severity (and of course, the maintainer is free to set the bug to serious again, if he thinks the package is unfit for release). Anyone disagreeing with the maintainer may try to convince him, search for other people convincing the maintainer, or escalate the topic to the tech ctte - as always. Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694892: tvtime: package installation creates /root/.tvtime
tags 694892 + patch thanks On Sat, 01 Dec 2012 21:36:19 +0100 Andreas Beckmann deb...@abeckmann.de wrote: 0m34.1s ERROR: FAIL: Package purging left files on system: /root/.tvtime/ not owned This is due to tvtime-configure being called in the postinst script. tvtime-configure uses config_new() which in turn contains this code: /* Make the ~/.tvtime directory every time on startup, to be safe. */ if( asprintf( temp_dirname, %s/.tvtime, getenv( HOME ) ) 0 ) { /* FIXME: Clean up ?? */ return 0; } mkdir_and_force_owner( temp_dirname, ct-uid, getgid() ); free( temp_dirname ); Therefore, tvtime-configure creates $HOME/.tvtime everytime you run it, even when the invocation is something like tvtime-configure -F /etc/tvtime/tvtime.xml I have attached a patch which will fix the bug (that is, not create $HOME/.tvtime on every run) but will still work correctly by creating dirname(config_filename) before saving. I tested it by changing the deinterlacing setting. -- Best regards, Michael --- O/src/tvtimeconf.c 2005-09-08 06:07:56.0 +0200 +++ N/src/tvtimeconf.c 2012-12-02 23:53:09.119478245 +0100 @@ -34,6 +34,7 @@ #include errno.h #include libxml/parser.h #include math.h +#include libgen.h #ifdef HAVE_CONFIG_H # include config.h #endif @@ -512,6 +513,13 @@ xmlDocPtr doc; xmlNodePtr top; int create_file = 0; +char *temp_config; + +if ((temp_config = strdup(config_filename)) == NULL) { +return 0; +} +mkdir_and_force_owner( dirname(temp_config), getuid(), getgid() ); +free( temp_config ); doc = xmlParseFile( config_filename ); if( !doc ) { @@ -844,14 +852,6 @@ ct-buttonmapmenu[ 4 ] = TVTIME_MENU_UP; ct-buttonmapmenu[ 5 ] = TVTIME_MENU_DOWN; -/* Make the ~/.tvtime directory every time on startup, to be safe. */ -if( asprintf( temp_dirname, %s/.tvtime, getenv( HOME ) ) 0 ) { -/* FIXME: Clean up ?? */ -return 0; -} -mkdir_and_force_owner( temp_dirname, ct-uid, getgid() ); -free( temp_dirname ); - /* First read in global settings. */ asprintf( base, %s/tvtime.xml, CONFDIR ); if( file_is_openable_for_read( base ) ) {
Bug#694981: paperkey: new upstream version
Package: paperkey Version: 1.2-1 Severity: wishlist Hi. David made a new version (1.3) which also supports ECC keys. http://www.jabberwocky.com/software/paperkey/paperkey-1.3-devel.tar.gz Might be a beta version for now though. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694873: django-tables: Can't locate django_tables2
On 3 December 2012 06:51, Chris Johnston chrisjohns...@ubuntu.com wrote: I'm on 12.10. So I determined that it seems to work fine when I'm not using a python virtualenv, but when I am in a virtualenv I get the following error: Oh, ok, I don't use virtualenv myself, but maybe I should move it up my priority list. Can I please confirm details however, just to make absolutely sure: * Are you sure your virtualenv is configured correctly to use django_tables? * Could this somehow be an issue with the upstream django_tables code somehow being incompatible with virtualenv? Thanks Brian May
Bug#694982: libreoffice: automatically raises windows upon receiving focus
Package: libreoffice Version: 1:3.5.4+dfsg-4 Severity: normal Libreoffice raises windows on receiving focus. This makes it pretty much unusable with a focus-follows-mouse window manager focus policy. Apparently it is also problematic in many situations with a click-to-focus policy. There is not a good reason for any application to behave like this. I'm not aware of other applications that behave like this, though I seem to remember I have encountered proprietary apps in the past that have done. Upstream bug reports span almost a decade: - http://forum.openoffice.org/en/forum/viewtopic.php?f=16t=1390 - https://issues.apache.org/ooo/show_bug.cgi?id=19489 - https://issues.apache.org/ooo/show_bug.cgi?id=17810 - http://lists.freedesktop.org/archives/libreoffice- bugs/2011-March/008311.html -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libreoffice depends on: ii fonts-sil-gentium-basic [ttf-sil-gentium-basic] 1.1-5 ii liblucene2-java 2.9.4+ds1-4 ii libreoffice-base 1:3.5.4+dfsg-4 ii libreoffice-calc 1:3.5.4+dfsg-4 ii libreoffice-core 1:3.5.4+dfsg-4 ii libreoffice-draw 1:3.5.4+dfsg-4 ii libreoffice-filter-mobiledev 1:3.5.4+dfsg-4 ii libreoffice-impress 1:3.5.4+dfsg-4 ii libreoffice-java-common 1:3.5.4+dfsg-4 ii libreoffice-math 1:3.5.4+dfsg-4 ii libreoffice-report-builder-bin 1:3.5.4+dfsg-4 ii libreoffice-writer 1:3.5.4+dfsg-4 ii ttf-dejavu 2.33-3 ii ttf-sil-gentium-basic1.1-5 Versions of packages libreoffice recommends: ii libpaper-utils 1.1.24+nmu2 ii ttf-liberation 1.07.2-6 Versions of packages libreoffice suggests: pn cups-bsd none ii default-jre [java5-runtime]1:1.6-47 ii gstreamer0.10-ffmpeg 0.10.13-5 ii gstreamer0.10-plugins-bad 0.10.23-7 ii gstreamer0.10-plugins-base 0.10.36-1 ii gstreamer0.10-plugins-good 0.10.31-3+nmu1 ii gstreamer0.10-plugins-ugly 0.10.19-2+b2 ii hunspell-en-us [hunspell-dictionary] 20070829-6 pn hyphen-hyphenation-patternsnone ii iceweasel 10.0.11esr-1 ii imagemagick8:6.7.7.10-5 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libldap-2.4-2 2.4.31-1 ii libreoffice-filter-binfilter 1:3.5.4+dfsg-4 ii libreoffice-gnome 1:3.5.4+dfsg-4 pn libreoffice-grammarcheck none ii libreoffice-help-en-gb [libreoffice-help-3.5] 1:3.5.4+dfsg-4 ii libreoffice-help-en-us [libreoffice-help-3.5] 1:3.5.4+dfsg-4 ii libreoffice-l10n-en-gb [libreoffice-l10n-3.5] 1:3.5.4+dfsg-4 pn libreoffice-officebean none ii libsane1.0.22-7.4 ii libxrender11:0.9.7-1 ii myspell-en-gb [myspell-dictionary] 1:3.3.0-4 ii mythes-en-us [mythes-thesaurus]1:3.3.0-4 pn openclipart-libreofficenone ii openjdk-6-jre [java5-runtime] 6b24-1.11.5-1 ii pstoedit 3.60-2+b1 pn unixodbc none Versions of packages libreoffice-core depends on: ii fontconfig 2.9.0-7 ii fonts-opensymbol 2:102.2+LibO3.5.4+dfsg-4 ii libc62.13-37 ii libcairo21.12.2-2 ii libcmis-0.2-00.1.0-1+b1 ii libcurl3-gnutls 7.26.0-1 ii libdb5.1 5.1.29-5 ii libexpat12.1.0-1 ii libexttextcat0 3.2.0-2 ii libfontconfig1 2.9.0-7 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.2-4 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgraphite2-2.0.0 1.1.3-1 ii libgstreamer-plugins-base0.10-0 0.10.36-1 ii libgstreamer0.10-0 0.10.36-1 ii libhunspell-1.3-01.3.2-4 ii libhyphen0 2.8.3-2 ii libice6 2:1.0.8-2 ii libicu48 4.8.1.1-10 ii libjpeg8 8d-1 ii libmythes-1.2-0
Bug#684604: eclipse-rcp: eclipse 3.8 hangs on splash screen with Loading Workbench after update from 3.7.2
On Sat, 25 Aug 2012 20:27:35 +0200 Felix Natter fnat...@gmx.net wrote: http://www2.inf.fh-brs.de/~fnatte2s/testRefactoring-sample-workspace.tar.bz2 This file is no longer online. Could you re-upload please? On Mon, 24 Sep 2012 21:55:56 +0200 Ulrich Van Den Hekke ulrich@shadoware.org wrote: I have the same problem. I start eclipse configure some project, install ADT plugin to work, after a few restart, i have this bug (splash screen hang on Loading Workbench). Removing .eclipse resolve the problem, but i need to reinstall plugin, and configuration, until the next hang. Could you provide a sample workspace with which eclipse crashes please? -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694940: RFS: toped/0.9.8.1-r2211-1 [ITP]
I don't intend to sponsor this package but here is a review. If you are contacting upstream as a result of this review, please point them at our upstream guide: http://wiki.debian.org/UpstreamGuide This package is not suitable for Debian main yet, here are the blockers: tpd_common/glf.* have a non-free license preventing commercial use. Upstream needs to contact the copyright holder (Romka Graphics) and get them to change it to GPL or these files need to be removed. tll/user_functions/tools/logos/examples/README suggests that tiger.pnm.gz and wnf_logo.pnm.gz are non-free and thus need to be removed since the author is unknown. fonts/*.glf look like they are derived from non-free fonts from Microsoft Windows and other places. Please ask upstream to remove them and switch to using the fonts already installed on the system. Something like pango or quesoglc can be used to render to OpenGL from system fonts. debian/copyright does not document the copyright and license information for all upstream files. The package fails to build from source in pbuilder/cowbuilder (missing build-dep on zlib): checking for gzsetparams in -lz... no configure: error: zlib library not found The following are things that would be nice to fix: tpd_common/avl.* are generated from some other files by texiweb, it would be good to generate them at build time if texiweb were in Debian. The src package is missing a watch file: http://wiki.debian.org/debian/watch The src package is missing a get-orig-source rule in debian/rules: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules Please get the patch and manual pages included upstream. The patch is missing proper DEP-3 headers (the patch header documents common ones): http://dep.debian.net/deps/dep3/ Please remove the comments from debian/rules since they serve no purpose. The upstream README file doesn't add much that isn't in the manual page or the package metadata, I would suggest it should not be listed in debian/docs. The Vcs-* fields are for the Debian packaging VCS, not the upstream VCS. I would suggest running wrap-and-sort -sa once now and every time the debian/control file is changed or other files touched by wrap-and-sort. The sentences in the Description: in debian/control are missing full-stops at the end. The debhelper build-dep probably doesn't need to be so specific, debhelper (= 9) is probably better. I would suggest build-depending on dh-autoreconf and adding --with autoreconf to the debian/rules dh line. This will ensure that the build system is still buildable on Debian. You will also need to build-depend on autoconf-archive and autoconf-gl-macros for this. The upstream ChangeLog file is empty, you might want to ask them to remove it from SVN and use svn2cl to generate it when they are building tarballs. toped includes MemTrack, which is meant as a drop-in pair of files. If this package gets sponsored, please notify the security team about it: http://wiki.debian.org/EmbeddedCodeCopies I guess gds2vrml was forked from gds2pov? It would be nice if those two projects could be re-aligned and merged. http://www.atchoo.org/gds2pov/ Some files contain an incorrect address for the FSF. You might want to ask upstream to fix that. There are lots of fixmes, hacks and todos in the source. The package fails to build twice in a row (debuild debuild), which potentially makes it annoying for the security team and NMUers to make uploads: make[3]: Entering directory `/tmp/buildd/toped-0.9.8.1-r2211/tll/user_functions/tools/logos/examples' make[3]: *** No rule to make target `distclean'. Stop. Automatically found issues: gcc: glf.cpp: In function 'int ReadFont(const char*, glf_font*)': glf.cpp:206:30: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:220:40: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:223:40: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:227:50: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:233:32: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:234:33: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:235:33: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:236:31: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] glf.cpp:263:37:
Bug#694983: dput-ng: FTBFS: a2x call → missing build dependency on docbook-xsl
Package: dput-ng Version: 1.0 Severity: serious Justification: fails to build from scratch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The dput-ng source package (grabbed from incoming.d.o) fails to build: debian/rules override_dh_installman make[1]: Entering directory `/tmp/buildd/dput-ng-1.0' mkdir debian/man a2x --doctype manpage --format manpage -D debian/man/ \ docs/man/dcut.1.man a2x: ERROR: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 /etc/asciidoc/docbook-xsl/manpage.xsl /tmp/buildd/dput-ng-1.0/debian/man/dcut.1.xml returned non-zero exit status 5 make[1]: *** [debian/man/dcut.1] Error 1 make[1]: Leaving directory `/tmp/buildd/dput-ng-1.0' make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 More info, if I call a2x with -v: # a2x -v --doctype manpage --format manpage -D debian/man/ docs/man/dcut.1.man a2x: args: ['-v', '--doctype', 'manpage', '--format', 'manpage', '-D', 'debian/man/', 'docs/man/dcut.1.man'] a2x: resource files: [] a2x: resource directories: ['/etc/asciidoc/images', '/etc/asciidoc/stylesheets'] a2x: executing: /usr/bin/asciidoc --backend docbook -a a2x-format=manpage --doctype manpage --verbose --out-file /tmp/buildd/dput-ng-1.0/debian/man/dcut.1.xml /tmp/buildd/dput-ng-1.0/docs/man/dcut.1.man asciidoc: reading: /etc/asciidoc/asciidoc.conf asciidoc: reading: /etc/asciidoc/asciidoc.conf asciidoc: reading: /tmp/buildd/dput-ng-1.0/docs/man/dcut.1.man asciidoc: reading: /etc/asciidoc/docbook45.conf asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf asciidoc: reading: /etc/asciidoc/lang-en.conf asciidoc: writing: /tmp/buildd/dput-ng-1.0/debian/man/dcut.1.xml a2x: executing: xmllint --nonet --noout --valid /tmp/buildd/dput-ng-1.0/debian/man/dcut.1.xml a2x: chdir /tmp/buildd/dput-ng-1.0/debian/man a2x: executing: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 /etc/asciidoc/docbook-xsl/manpage.xsl /tmp/buildd/dput-ng-1.0/debian/man/dcut.1.xml warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; compilation error: file /etc/asciidoc/docbook-xsl/manpage.xsl line 12 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl a2x: ERROR: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 /etc/asciidoc/docbook-xsl/manpage.xsl /tmp/buildd/dput-ng-1.0/debian/man/dcut.1.xml returned non-zero exit status 5 a2x: chdir /tmp/buildd/dput-ng-1.0 And after installing docbook-xsl it works. (Verified also by putting it into d/control and rebuilding from scratch.) Cheers, gregor - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQu+QIAAoJELs6aAGGSaoGRmUP/2O4aqLl8Gg01UB6iYSRkIP9 U68U5nXTS+S1ZucKzkn/7WAbYGMH8+xzohzf8kndOZDrBe/VBkQ+p4Tpb0+ySil9 DwWi7x3lPYfED6vS1p1J9lxhaRVdqjMP6k3onWXMV9YQ96gfpHtFsTcD2kpiUie5 Uri8tY0FE3QyA1xpNZn3aEwltZjEbNKQWjcGqlFdTv5wVohgBHxZKsk9Czx08FRn T3PlVtbhHuxLBiLFxVvgev9F2RlumjdPIL49TxGvDZfjyjH1Qb80fGQDe+hesfBx y5Z+J8QUVQNc44WIP4d+7nKls4M4UG0OVAy68o3mWKgLfL37Iz3phLjV6IpTOfBS Q2rsdcYrMHCztOI69ivn2jroUViy7+sLjPGPcBc34q7bRIS6FjmIRQ22B+medNjq +Agz3Aj7f7n3et9LDN2gd0DRDYJGpSCVW61L9VLk1uZZTNfcBps6orwwMUfEmGF6 RH59n1vHNMkBIB5HNQBQzENLAL4Oyy+7J3ifz8rF5rPyG0X+mGqKN+pdbANFoNfX Y4QUnXR5ccI74hGTTHhLkX72VBRsnXiSu1FPzaKZMGqNGFJx/Y76G/HcTSPqHPEs QkaCSNH9DuTRNPGxqZIo4ziOIb9qIktgAxUCyOnPNVzfnp7ESXOQhJJJLZUqUdX1 kWbto+D/7NQ7PVPfdsWF =Iz8p -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694984: znc-dev does not depend on the compilers for building, should depend on build-essential
Package: znc Version: 1.0-1 Severity: minor The znc-dev package contains the required data to build external modules for ZNC. One thing it does not do, however, is depend on the compiler(s) for such modules. Perhaps it would be prudent to have `build-essential` (or equivalent script) set as a dependency. (Ubuntu bug for this: https://bugs.launchpad.net/bugs/1085742) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692821: gnome-shell: defines wrong pam service for gdm greeter
reassign 692821 gnome-shell 3.6.2-1 retitle 692821 gnome-shell: defines wrong pam name for gdm greeter affects 692821 gdm3 service thanks Hi, It seems that the gnome-shell greeter is defining the wrong pam service in js/gdm/util.js const PASSWORD_SERVICE_NAME = 'gdm-password'; Changing this to gdm3 fix this issue. I'm wondering, why is gdm using different pam service name (gdm3 vs gdm-password) as the one that upstream is using? The gdm(2) package is using gdm as pam service name. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694985: byacc: Please mark Multi-Arch: foreign
Package: byacc Version: 20121003-1 Severity: wishlist Tags: patch User: crossbu...@debian.org Usertags: cross byacc is Architecture: any, but on a multiarch system it doesn't matter which architecture you get as long as you can execute its binaries. It's also a build-dependency of 18 packages in unstable. Accordingly, it would be helpful to mark it Multi-Arch: foreign, which is generally appropriate for this kind of program, to avoid blocking cross-builds of those packages. * Mark byacc Multi-Arch: foreign. diff -Nru byacc-20121003/debian/control byacc-20121003/debian/control --- byacc-20121003/debian/control 2012-03-11 15:38:21.0 + +++ byacc-20121003/debian/control 2012-12-02 23:43:07.0 + @@ -8,6 +8,7 @@ Package: byacc Architecture: any +Multi-Arch: foreign Depends: ${shlibs:Depends}, ${misc:Depends} Description: public domain Berkeley LALR Yacc parser generator This package provides a parser generator utility that reads a grammar Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694961: initscripts: Boot hangs cause of Init: job_process_handler ignored event 1 ....
reassign 694961 upstart thanks On Sun, Dec 02, 2012 at 08:14:00PM +0100, Peschae wrote: Package: initscripts Version: 2.88dsf-34 Severity: critical Justification: breaks the whole system Dear Maintainer, after an update, I got the error message Init: job_process_handler ignored event 1 on three different system. But I´m not really shure if the problem is in initscripts or an other package. One (this here) i386 , two amd64 - all Debian testing. One of the amd64 is brand new after a Netinstall. Then I made an update and got the error (boot stops). i386: upstart 0.6.6-2 amd64: upstart 0.6.6-2 amd64 (brand new): sysvinit here´s the aptitude log of the update (brand new system): [AKTUALISIERUNG] initscripts:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] klibc-utils:amd64 2.0.1-3 - 2.0.1-3.1 [AKTUALISIERUNG] libc-bin:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] libc6:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] libgnutls26:amd64 2.12.20-1 - 2.12.20-2 [AKTUALISIERUNG] libklibc:amd64 2.0.1-3 - 2.0.1-3.1 [AKTUALISIERUNG] liblzma5:amd64 5.1.1alpha+20120614-1 - 5.1.1alpha+20120614-2 [AKTUALISIERUNG] libusb-0.1-4:amd64 2:0.1.12-20 - 2:0.1.12-20+nmu1 [AKTUALISIERUNG] locales:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] multiarch-support:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] sysv-rc:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] sysvinit:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] sysvinit-utils:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] xz-utils:amd64 5.1.1alpha+20120614-1 - 5.1.1alpha+20120614-2 My workaround is: update the systems to upstart upstart 1.6.x Please let me know if you need additonal information. I´ve also got an other system (upstart 0.6.6-2) which I can kill. Reassigning the bug to upstart. The actual error message (job_process_handler) is definitely upstart. If there's anything initscripts-related then I'll certainly look further into that, but I don't personally have the expertise to investigate the upstart side of things further. 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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694624: /usr/sbin/xfs_freeze: freezes under lying (root)
Well it's your call, but I'll make my case for changing it. - I think it is very dangerous default behaviour, particularly in scripts as it can prevent the possibility of logging in to unfreeze a frozen root. - The docs all strongly imply that it operates on mountpoints, so surely not many people would have diliberately used it on general paths? xfs_freeze -f | -u mount-point The mount-point argument is the pathname of the directory where the file system is mounted. - Because of the name and the wording of the man page, you don't expect xfs_freeze to freeze an ext4 file system that isn't even mounted on the path you pass to it?! - It's logical to have it work on mountpoints only. You wouldn't expect umount or fdisk to work the same way? Do any other partition level tools work this way? - At the very least I would expect it to require a 'force' option if it was going to freeze the root system. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694984:
Given current info I received in Ubuntu, it may be prudent to at least set it as dependent on the gcc / g++ compilers for modules rather than build-essential -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
clone 694928 -1 reassign -1 initscripts thanks On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote: Please find attached an example patch for flash-kernel to support old and new (rcS and fsck) locations for FSCKFIX as discussed on #debian-devel earlier. Please don't apply it just yet--we'll presumably need to get approval from the release team to change this in initscripts at the same time. I'll have a patch for initscripts shortly; might be a bit later in the week to allow for comprehensive testing. Thanks, 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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
On Sun, Dec 02, 2012 at 11:47:37PM +, Roger Leigh wrote: clone 694928 -1 reassign -1 initscripts thanks On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote: Please find attached an example patch for flash-kernel to support old and new (rcS and fsck) locations for FSCKFIX as discussed on #debian-devel earlier. Hmm, actually attached now. -- .''`. 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 From 300eb0dcd6abc4ced0596f87a33d3165d46779e5 Mon Sep 17 00:00:00 2001 From: Roger Leigh rle...@debian.org Date: Sun, 2 Dec 2012 23:34:57 + Subject: [PATCH] debian: Update /etc/default/fsck in flash-kernel-installer postinst --- debian/changelog | 10 ++ debian/flash-kernel-installer.postinst |7 ++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 68c673b..526f1ec 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +flash-kernel (3.4) UNRELEASED; urgency=low + + [ Roger Leigh ] + * flash-kernel-installer postinst: Update FSCKFIX in +/etc/default/fsck as well as /etc/default/rcS for backward +compatibility. The purpose is to use /etc/default/fsck for +new installations. + + -- Roger Leigh rle...@debian.org Sun, 02 Dec 2012 23:33:24 + + flash-kernel (3.3) unstable; urgency=low * Replace XC-Package-Type by Package-Type diff --git a/debian/flash-kernel-installer.postinst b/debian/flash-kernel-installer.postinst index c07dee5..311615d 100755 --- a/debian/flash-kernel-installer.postinst +++ b/debian/flash-kernel-installer.postinst @@ -35,7 +35,12 @@ db_progress INFO flash-kernel-installer/prepare # Stop fsck from prompting the user for input since most users don't # have a serial console. -sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +if [ -e /target/etc/default/rcS ]; then + sed -i -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +fi +if [ -e /target/etc/default/fsck ]; then + sed -i -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/fsck || true +fi if ! apt-install flash-kernel; then error apt-install flash-kernel failed -- 1.7.10.4
Bug#694873: django-tables: Can't locate django_tables2
On 12/02/2012 06:06 PM, Brian May wrote: Can I please confirm details however, just to make absolutely sure: * Are you sure your virtualenv is configured correctly to use django_tables? It should, AFAIK. I am using other packages that are installed on the system through apt-get instead of pip. * Could this somehow be an issue with the upstream django_tables code somehow being incompatible with virtualenv? The version in pypi works fine in a virtualenv. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694260: [Bug-freedink] Bug#694260: freedink: Stack corruption
You should probably send that MIDI file to the SDL_Mixer developers as well so that they can look over it for something that would cause this type of fault. On Sun, Dec 2, 2012 at 2:20 PM, Bas Wijnen wij...@debian.org wrote: Hi, What I have found out so far: - It crashes when it makes the call to play the midi file. - It doesn't crash when 20.mid is not present, nor when it is replaced by a different midi file. (even though 20.mid plays without a problem with timidity). However, a really slim test case with only calls to make that file play is not enough to make it crash. Thanks, Bas On 02-12-12 20:01, Sylvain wrote: Additional info : - No crash when run with '-s' (no sound), so looks like this comes from SDL_Mixer indeed. - I think I tested this D-Mod already during the FreeDink development, as I remembered it was a good test case for bug-compatibility (ahem), abeilt maybe only the Lava part. - Sylvain On Sun, Dec 02, 2012 at 06:39:40PM +, Sylvain wrote: Hi, According to the backtrace, it looks like it's in the SDL_mixer thread indeed. Cheers! Sylvain On Sat, Dec 01, 2012 at 12:38:17AM +0100, Bas Wijnen wrote: After a lot of debugging, the problem seems to be in libSDL instead. If I manage to get a simple test program triggering the bug, I'll report it there and close this bug. Until I do, I'll leave it open on freedink, because I'm still not entirely sure. Thanks, Bas On 24-11-12 21:08, Bas Wijnen wrote: Package: freedink Version: 1.08.2012042 The dmod Eternal suicide is full of bugs which are nicely handled by the engine (and which don't really affect gameplay). However, there is one problem which causes the engine to abort with the attached message. I'm having trouble debugging this, as there is no mention of what really is the problem, except that some fortify check fails. I attached a save file with which you can reproduce it. It brings you in front of a cave. Enter it and it crashes. Thanks, Bas ___ Bug-freedink mailing list bug-freed...@gnu.org https://lists.gnu.org/mailman/listinfo/bug-freedink -- - Luiji Maryo mail: lu...@users.sourceforge.net blog: http://brainboyblogger.blogspot.com/ corp: http://www.entertainingsoftware.com/ fun: http://www.secretmaryo.org/
Bug#689634: texlive-latex-extra: cweb-latex doesn't work: a missing file and a necessary patch
tags 689634 + pending fixed-upstream thanks On Do, 04 Okt 2012, Javier M Mora wrote: ! LaTeX Error: File `cwebbase.tex' not found. ... If I apply patch from original author (taken from: Thanks for the report. I have now fixed both errors in upstream TeX Live, that means the next upload of TeX Live to experimental or unstable will bring in these fixes. Tagging as pending and fixed-upstream Thanks. Norbert Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 TWEMLOW GREEN (n.) The colour of some of Nigel Rees's trousers, worn in the mistaken belief that they go rather well with his sproston green (q.v.) jackets. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673790: Status update?
reassign 673790 python-cloudservers retitle 673790 broken: doesn’t use the python-prettytable = 0.6 API thanks On Sat, 24 Nov 2012 16:06:05 +0100 (CET) Dominik George n...@naturalnet.de wrote: What is the current state? I did one obvious test and found that in testing, the example script works. Yes, due to the 0.6.1-1 upload, which contains the following changelog entry: debian/prettytable-example.py - update for new 0.6 release Does this issue still break other packages? Please report un an understandable manner what is still broken and what isn't. Following up on message #36: • weboob is fixed in 0.c-4.1 • python-novaclient is fixed in 1:2012.1-2 • python-keystoneclient is fixed in 2012.1-2 • python-cloudservers: still broken (from looking at the code and trying to run shell.py:print_list()) I am re-assigning this bug to python-cloudservers as it is the only remaining package which is broken. The only alternative, which is changing python-prettytables to include compatiblity code is a non-trivial task AFAICT. Thomas: Since you have previously NMU'd python-cloudservers, could you maybe have a look at it and port it to the new API? If not, please tell me ASAP so that we can move forward in some other way :-). -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694980: dpkg: start-stop-daemon should wait when stopping the daemon
Hi! On Sun, 2012-12-02 at 22:40:04 +0100, Salvo Tomaselli wrote: Package: dpkg Version: 1.16.9 Severity: normal after inspecting start-stop-daemon's source, i couldn't find any wait/waitpid calls, and they should exist. That's because those calls only apply to child processes which is not the case with s-s-d --stop. Stopping a daemon usually consists in sending a message to the right pid, but after that it would be better to do a waitpid so that the command terminates when the daemon has really stopped, not just when the signal has been sent. That behaviour is already supported with the --retry option. But this might not cover the case that a parent process in the daemon has terminated but not some of its worker childs for example, and that's a daemon's issue. This would allow scripts to be simpler because they would know that after a start-stop-daemon --stop, the daemon has in fact stopped; and it's not the case right now. Then those init scripts are buggy, and should be fixed. This leads maintainers to insert sleeps in the scripts to hope that in the meanwhile the daemon will terminate (the correct approach would be to insert wait on the pid); but the even more correct approach would be to fix start-stop-daemon so that when it exits the daemon has stopped. This is either a problem in the daemon, or in the init script, I don't really see any issue here with s-s-d. If no further information to the contrary is provided I'll be closing this report. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694987: obexfs: depends on transitional package fuse-utils
Package: obexfs Version: 0.11-1 obexfs depends on fuse-utils, which has been replaced by the fuse package. Please update the dependency! Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694980: dpkg: start-stop-daemon should wait when stopping the daemon
That's because those calls only apply to child processes which is not the case with s-s-d --stop. There are alternative safe ways to detect it, like using ptrace or [1]. A cycle with kill(0) is not safe, another process with the same pid could be started between two iterations. That behaviour is already supported with the --retry option. But this might not cover the case that a parent process in the daemon has terminated but not some of its worker childs for example, and that's a daemon's issue. Agreed, but the kill(0) thing is an hack itself which could not work in all the situations. Then those init scripts are buggy, and should be fixed. Yes, they should use the --retry instead of the wait. Bye [1] http://netsplit.com/2011/02/09/the-proc-connector-and-socket-filters/ -- Salvo Tomaselli -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694988: libkrb5-3: select on set of invalid fds, leads to infinite loop in sshd
Package: libkrb5-3 Version: 1.10.1+dfsg-3 Severity: normal Dear Maintainer, sshd randomly ran into 100% cpu-usage. debugging revealed a endless poll-loop in libkrb5-3, further debugging and an upstream bugreport led to the attached patch. please apply the patch to wheezy. we have tested the patch on about 200 machines for several days now and can confirm it fixes the bug and has no adverse effects. link to patch: https://github.com/krb5/krb5/commit/9eb2b4dfc136da326e54081ae18cb4d648c6500d link to upstream bugtracker: http://krbdev.mit.edu/rt/Ticket/Display.html?id=7454 regards, johannes -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1051, 'testing'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.0.31 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592463: [lenny] domU kernel freeze on xfs location
Hi, In 2010, sysad...@campbell-lange.net wrote: Yesterday we had a domU PV host freeze up in a file location. The following log was received: [20108008.237603] BUG: soft lockup - CPU#0 stuck for 61s! [smbd:16411] [...] [20108008.237603] Pid: 16411, comm: smbd Not tainted 2.6.26-2-xen-amd64 #1 [...] [20108008.237603] Call Trace: [20108008.237603] [a00550d7] ? :xfs:xfs_bmap_search_multi_extents 0x78/0xda [20108008.237603] [a0055194] ? :xfs:xfs_bmap_search_extents 0x5b/0xe6 [20108008.237603] [a005b1df] ? :xfs:xfs_bmapi 0x26e/0xf76 [20108008.237603] [80436b47] ? error_exit 0x0/0x69 [20108008.237603] [80436b47] ? error_exit 0x0/0x69 [20108008.237603] [a0096441] ? :xfs:xfs_zero_eof 0xc0/0x16a [20108008.237603] [a0096b0e] ? :xfs:xfs_write 0x344/0x722 [20108008.237603] [8028a1ef] ? do_sync_write 0xc9/0x10c [20108008.237603] [8020e7bc] ? get_nsec_offset 0x9/0x2c [20108008.237603] [802992dc] ? __posix_lock_file 0x3c1/0x3f6 [...] This domU could not be rebooted, and had to be xm destroy then recreated again before the filesystem was accessible again. Thanks for reporting it, and sorry for the slow response. Did this only happen once, or was it reproducible? If it happened again, on which kernel? Sincerely, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684883: [www.debian.org] French Ports page claims Debian is
reopen 684883 thanks On 2012-11-27 04:42, Francesca Ciceri wrote: On Mon, Nov 26, 2012 at 06:28:31PM -0500, Filipus Klutiero wrote: In any case, please do not close report of bugs until they are solved. This is not a bug, this is a divergence of opinions about the translation of a specific phrase and the proper place to discuss it is the l10n-french mailing list. I don't know what you're referring to, but what I am referring to is the fact that, as reported, our French Ports page claims that Debian is ported to all Linux architectures, which is certainly not a divergence of opinions, but a divergence with reality, and therefore a bug. Feel free to discuss on a mailing list if you wish. For my part, my goal is not to discuss the problem but to solve it, and mailing lists are neither repositories nor bug trackers. In any case, please respect the judgement of the maintainer of the package about the bug status. What? This bug is in the website. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
On Sun, Dec 02, 2012 at 11:49:44PM +, Roger Leigh wrote: On Sun, Dec 02, 2012 at 11:47:37PM +, Roger Leigh wrote: clone 694928 -1 reassign -1 initscripts thanks On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote: Please find attached an example patch for flash-kernel to support old and new (rcS and fsck) locations for FSCKFIX as discussed on #debian-devel earlier. Hmm, actually attached now. Slight update to cope with commented-out lines (as provided by default). -- .''`. 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 From 4db3a50a7bd6b11f3a4fa425e5e2c9b7cf1c9673 Mon Sep 17 00:00:00 2001 From: Roger Leigh rle...@debian.org Date: Sun, 2 Dec 2012 23:34:57 + Subject: [PATCH] debian: Update /etc/default/fsck in flash-kernel-installer postinst --- debian/changelog | 10 ++ debian/flash-kernel-installer.postinst |7 ++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 68c673b..526f1ec 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +flash-kernel (3.4) UNRELEASED; urgency=low + + [ Roger Leigh ] + * flash-kernel-installer postinst: Update FSCKFIX in +/etc/default/fsck as well as /etc/default/rcS for backward +compatibility. The purpose is to use /etc/default/fsck for +new installations. + + -- Roger Leigh rle...@debian.org Sun, 02 Dec 2012 23:33:24 + + flash-kernel (3.3) unstable; urgency=low * Replace XC-Package-Type by Package-Type diff --git a/debian/flash-kernel-installer.postinst b/debian/flash-kernel-installer.postinst index c07dee5..e9b88c7 100755 --- a/debian/flash-kernel-installer.postinst +++ b/debian/flash-kernel-installer.postinst @@ -35,7 +35,12 @@ db_progress INFO flash-kernel-installer/prepare # Stop fsck from prompting the user for input since most users don't # have a serial console. -sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +if [ -e /target/etc/default/rcS ]; then + sed -i -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true +fi +if [ -e /target/etc/default/fsck ]; then + sed -i -e s/^#FSCKFIX=no$/FSCKFIX=yes/ -e s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/fsck || true +fi if ! apt-install flash-kernel; then error apt-install flash-kernel failed -- 1.7.10.4
Bug#694945: foomatic: cannot get PPD for Canon-PIXMA-iP3000 and many others
On Sun, Dec 02, 2012 at 04:45:07PM +0100, Yann Dirson wrote: Package: foomatic-db-engine Version: 4.0.8-3 Severity: normal There are apparently 3 CUPS drivers in Debian for the Pixma iP3000: gutenprint.5.2://bjc-PIXMA-iP3000/expert foomatic:Canon-PIXMA-iP3000-gutenprint-ijs.5.2.ppd foomatic:Canon-PIXMA-iP3000-gutenprint-ijs-simplified.5.2.ppd I have no idea why CUPS is using foomatic drivers here. The native CUPS driver is preferred. Do you have the ijsgutenprint package installed? I'm afraid I can't help with the specifics of the foomatic issue itself since I'm not a foomatic expert. [Given the pain they cause, it might be best to remove the gutenprint foomatic packages entirely for jessie.] 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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688813: bitcoind: CVE-2012-4683 and CVE-2012-4682, fixed in 0.7r1
Fixed in version 0.7r1 https://bitcointalk.org/index.php?topic=104173.70;wap2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694989: postgres ($pid): /proc/$pid/oom_adj is deprecated, please use /proc/$pid/oom_score_adj instead.
Package: postgresql-9.2 Version: 9.2.1-1 Severity: minor The above kernel complaint is generated when postgres starts up. Presumably, it would be nice to shut it up. (Kernel is 3.6.7, i686, FWIW.) The PID does not correspond to any running process, but is in the range: PID TTY STAT TIME COMMAND $pid-6 ?S 0:00 /usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c config_file=/etc/postgresql/9.2/main/postgresql.conf $pid+3 ?Ss0:00 \_ postgres: checkpointer process $pid+4 ?Ss0:00 \_ postgres: writer process $pid+5 ?Ss0:00 \_ postgres: wal writer process $pid+6 ?Ss0:00 \_ postgres: autovacuum launcher process $pid+7 ?Ss0:00 \_ postgres: stats collector process -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694990: RFA: sandboxgamemaker -- 3D game maker and 3D game design program
Package: wnpp Severity: normal I request an adopter for the sandboxgamemaker package. Good and useful package, however I'm busy with other packages/job and interest has waned. This is a contrib package and licensing is difficult: upstream insists on using a custom license with is kind of confusing, but then releases the engine under a generous ZLIB license. The content is mostly free and they have put a strong effort into making it DFSG, but the attribution and license of some of the content is unclear. Some content requests that the author is notified when used, not be used for commercial purposes, or other restrictions that makes it unfree. However, upstream has been trying to work out all those issues. For now we distribute the ZLIB engine and have a downloader to grab content. The package description is: Platinum Arts Sandbox is an open source, easy-to-use, standalone 3D game maker and 3D game design program. It is currently based on the Cube 2 engine used in schools around the world that allows kids and adults to create their own video games, worlds, levels, adventures, and quests, even cooperatively. The goal is to make it accessible to kids but also powerful enough for full game projects. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694873: django-tables: Can't locate django_tables2
On 3 December 2012 10:51, Chris Johnston chrisjohns...@ubuntu.com wrote: It should, AFAIK. I am using other packages that are installed on the system through apt-get instead of pip. Unfortunately, I am still having problems reproducing this. Are you able to give me a list of instructions (or shell script) on how to create a virtualenv environment that has this problem? Thanks -- Brian May br...@microcomaustralia.com.au
Bug#694991: wmaker: recognize the windows keys
Package: wmaker Version: 0.92.0-8.2+b1 Severity: wishlist Standard PC keyboards have two keys assigned to the MS-Windows logo. They are dead under wmaker. Whould be nice to activate them. They could be binded to some usefull actions, eg. windows list etc. Hint: enlightenment (e16) assigns them as super-left and super-right. Window Maker is better, but even the best can be better... my regards, Niklaus -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) 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 wmaker depends on: ii cpp4:4.4.5-1 The GNU C preprocessor (cpp) ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libwraster30.92.0-8.2+b1 Shared libraries of Window Maker r ii libx11-6 2:1.3.3-4 X11 client-side library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxft22.1.14-2 FreeType-based font drawing librar ii libxinerama1 2:1.1-3 X11 Xinerama extension library wmaker recommends no packages. Versions of packages wmaker suggests: ii menu 2.1.44 generates programs menu for all me ii terminal.app [x-term 0.9.4+cvs20051125-6 Terminal Emulator for GNUstep ii wmaker-data 0.9~3-4 several free icons for use with Wi ii x11-apps 7.5+5 X applications pn xosview none (no description available) ii xterm [x-terminal-em 261-1 X terminal emulator -- Configuration Files: /etc/X11/WindowMaker/appearance.menu changed: /* Automatically generated file. Do not edit. */ Appearance MENU Background OPEN_MENU background.menu Icon Sets OPEN_MENU -noext LOCAL_ICON_SETS_DIR ICON_SETS_DIR USER_ICON_SETS_DIR WITH seticons Styles OPEN_MENU -noext LOCAL_STYLES_DIR STYLES_DIR USER_STYLES_DIR WITH setstyle Themes OPEN_MENU -noext LOCAL_THEMES_DIR THEMES_DIR USER_THEMES_DIR WITH setstyle Save IconSet EXEC geticonset USER_ICON_SETS_DIR/%a(IconSet name) Save Theme EXEC getstyle -t USER_THEMES_DIR/%a(Theme name) Appearance END -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668109: Bug #668109: gstreamer: shuffle mode - ogg and flac files freeze at 0:00
fixed 668109 gst-plugins-base1.0/1.0.3-1 tags 668109 + fixed-upstream thanks The upstream developers of gstreamer have decided to close the bug report because several people reported the problem is gone in version 1.0 of gstreamer (see https://bugzilla.gnome.org/show_bug.cgi?id=680252). Furthermore, they were never able to pin point the cause, so NO patch is available. Unfortunately Debian wheezy still doesn't have gstreamer1.0. Can we expect an update this late in the freeze? This bug affects lots of software (rhythmbox, quodlibet, totem, etc), across several desktop environments. Please consider updating to 1.0.x in wheezy thanks Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694947: bind9: package upgrade overwrites gid owner of /etc/bind/named.conf.local
On Sun, Dec 02, 2012 at 10:14:43PM +0100, Ond??ej Surý wrote: On Sun, Dec 2, 2012 at 3:30 PM, Paul Witt paul.w...@oxix.org wrote: Package: bind9 Version: 1:9.7.3.dfsg-1~squeeze8 Severity: normal After a recent bind9 security upgrade (and probably after previous upgrades too), our config management system reported that /etc/bind/named.conf.local had had its group owner changed from the one we'd configured to the group bind. Presumably it was the package upgrade that caused this. I have just tried the upgrade in clean pbuilder and the changed permissions were kept during the upgrade. The chgrp happens only on a condition where rndc.key has root as an owner (which I presume is to detect first installation) and only in that case the inital permissions are setup. See the snipet from postinst script: uid=$(ls -ln /etc/bind/rndc.key | awk '{print $3}') if [ $uid = 0 ]; then [ -n $localconf ] || chown bind /etc/bind/rndc.key chgrp bind /etc/bind chmod g+s /etc/bind chgrp bind /etc/bind/rndc.key /var/run/named /var/cache/bind chgrp bind /etc/bind/named.conf* || true chmod g+r /etc/bind/rndc.key /etc/bind/named.conf* || true chmod g+rwx /var/run/named /var/cache/bind fi Is there a change that your rndc key was owned by the root user? Yes, it is owned by the root user. Since we have managed configuration files for bind, $localconf will be y, so the chown bind /etc/bind/rndc.key won't get executed. Because we don't start the service until the package is installed and the config files are all in place, we don't put an ordering constraint on whether the config files or the package gets installed first. So it's likely that the config files were already in place the first time that the postct was run. The logic in the script then ensures that /etc/bind/rndc.key is never chown'd, and that all the other changes are made repeatedly. Perhaps that whole block could be wrapped in a localconf check something like: if [ $uid = 0 ]; then if ! [ $localconf ] ; then chown bind /etc/bind/rndc.key chgrp bind /etc/bind chmod g+s /etc/bind chgrp bind /etc/bind/rndc.key /var/run/named /var/cache/bind chgrp bind /etc/bind/named.conf* || true chmod g+r /etc/bind/rndc.key /etc/bind/named.conf* || true chmod g+rwx /var/run/named /var/cache/bind fi fi In any case there definitely seems to be a bug with the current postinst in the case of a sysadmin installing [some of] the config files before they install the package. cheers, Paul. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694992: mutt: hangs indefinitely with No authenticators available if smtp_authenticators = 'gssapi' and fails
Package: mutt Version: 1.5.21-6.2 Severity: important Dear Maintainer, I have: set smtp_authenticators = 'gssapi' and when the authentication fails, mutt will sometimes say No authenticators available in its bottom row, and never return control to the user. An example reason for the authentication failing is that the tgt has expired. The bug doesn't happen every time. Sometimes the error message will be displayed and control returned to the user. For me at the moment, it's around 3 in 4 times that the bug is seen when the conditions are as described above. When a similar situation occurs with imap_authenticators, it displays the same error message, but seems to always nicely return control to the user instead of hanging. As a workaround, an additional mechanism can be added. Even if there is no intention of using the other mechanism, it seems to allow control to pass more reliably back to the user. For example: set smtp_authenticators = 'gssapi:login' -- Package-specific info: Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 3.2.0-4-amd64 (x86_64) ncurses: ncurses 5.9.20110404 (compiled with 5.9) libidn: 1.25 (compiled with 1.25) hcache backend: tokyocabinet 1.4.47 Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh MIXMASTER=mixmaster To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. misc/am-maintainer-mode features/ifdef features/xtitles features/trash-folder features/purge-message features/imap_fast_trash features/sensible_browser_position features-old/patch-1.5.4.vk.pgp_verbose_mime features/compressed-folders features/compressed-folders.debian debian-specific/Muttrc debian-specific/Md.etc_mailname_gethostbyname.diff debian-specific/use_usr_bin_editor.diff debian-specific/correct_docdir_in_man_page.diff debian-specific/dont_document_not_present_features.diff debian-specific/document_debian_defaults debian-specific/assumed_charset-compat debian-specific/467432-write_bcc.patch debian-specific/566076-build_doc_adjustments.patch misc/define-pgp_getkeys_command.diff misc/gpg.rc-paths misc/smime.rc upstream/531430-imapuser.patch upstream/537818-emptycharset.patch upstream/543467-thread-segfault.patch upstream/542817-smimekeys-tmpdir.patch upstream/548577-gpgme-1.2.patch upstream/553321-ansi-escape-segfault.patch upstream/568295-references.patch upstream/547980-smime_keys-chaining.patch upstream/528233-readonly-open.patch upstream/228671-pipe-mime.patch upstream/383769-score-match.patch upstream/578087-header-strchr.patch upstream/603288-split-fetches.patch upstream/537061-dont-recode-saved-attachments.patch upstream/608706-fix-spelling-errors.patch upstream/620854-pop3-segfault.patch upstream/611412-bts-regexp.patch upstream/624058-gnutls-deprecated-set-priority.patch upstream/624085-gnutls-deprecated-verify-peers.patch upstream/584138-mx_update_context-segfault.patch upstream/619216-gnutls-CN-validation.patch upstream/611410-no-implicit_autoview-for-text-html.patch upstream/path_max misc/579967-fixes-german-translation.patch mutt.org -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mutt depends on: ii libc6 2.13-37 ii libcomerr21.42.5-1 ii libgnutls26 2.12.20-2 ii libgpg-error0 1.10-3.1 ii libgpgme111.2.0-1.4 ii libgssapi-krb5-2 1.10.1+dfsg-3 ii libidn11 1.25-2 ii libk5crypto3 1.10.1+dfsg-3 ii libkrb5-3 1.10.1+dfsg-3 ii libncursesw5 5.9-10 ii libsasl2-22.1.25.dfsg1-6 ii libtinfo5 5.9-10 ii libtokyocabinet9 1.4.47-2 Versions of packages mutt recommends: ii libsasl2-modules2.1.25.dfsg1-6 ii locales 2.13-37 ii mime-support3.52-1 ii postfix [mail-transport-agent] 2.9.3-2.1
Bug#694955: git-import-orig: support workflow with upstreams history on upstream branch
On Sun, Dec 02, 2012 at 12:03:24PM -0800, Russ Allbery wrote: Thomas Koch tho...@koch.ro writes: I like to fork my git packaging repo from upstream and merge upstreams history in my upstream branch from time to time. When upstream makes a release, they hopefully tag the git commit from which their release was made or I need to identify it manually. Then there are three cases: a) Upstreams release tarball has identical content to one git commit. (Maybe it was even created via git-archive.) b) Upstreams release tarball has slightly other content then any git commit. (b) is common for projects that don't check in generated files, but which include them in tarball releases. c) Upstreams release tarball has a totally different structure then any git commit. In case a) I can just create a signed git tag upstream/$VERSION and pristine-tar commit the tarball. In case b) I'd create a new commit containing the tarballs content with the release commit as its parent, tag it and merge it into master. In case c) I'm doomed. It would be nice, if git-import-orig would support this workflow somehow. Well, I don't see any way to support (c) other than don't base your upstream branch on upstream's Git repository, since it doesn't bear any relationship to the release. But for (a) and (b), I think the --upstream-vcs-tag option to git-import-orig will do exactly what you want. (b) was the workflow for which I originally requested it. Also the --git-pristine-tar-commit option might help with a) since it saved the extra step of comitting the pristine-tar delta. I don't see any actual way we can improve (c) either but am open to suggestions. Cheers, -- Guido -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694993: opencc: Ship opencc.py in src/wrapper/python/
Package: opencc Version: 0.3.0-3 Severity: normal Dear Maintainer, Please package the python binding for the libopencc1. Either as a stand alone package like python-opencc or just ship the file with libopencc1. The wrapper make use of ctypes, so no extra build time dependent is required. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.5-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages opencc depends on: ii libc6 2.13-35 ii libopencc1 0.3.0-3 opencc recommends no packages. opencc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693710: COPYRIGHT file for X2Go logos
Hi Heinz, may I ask you to update the COPYRIGHT file and the README in x2go-logos.tar.gz a little? README (typo fix plus considering that the tarball is not a tarball anymore): --- README 2012-12-03 04:28:04.0 +0100 +++ README.orig 2012-12-03 04:29:18.0 +0100 @@ -8,15 +8,15 @@ The files -x2go-logo.svs +x2go-logo.svg x2go-logo-colored.svg x2go-logo-rotated.svg x2go-mascot.svg are used to build the program icon files for the use on desktop environments. -You may use the mksizedsymbols.sh (part of this tar.gz) script to generate PNG -icons in different sized. +You may use the mksizedsymbols.sh (part of this tar.gz / in this folder) script +to generate PNG icons in different sized. # Changelog COPYRIGHT: There are some inconsistencies in this file: 1. in the head line you write GPL-2+, the license header is GPL-3+ 2. please add the CC-share-alike license to the copyright file and I'd be happy if you could be a little more verbose about the dual licensing in that file (see [1] for an example) I will prepare a new revision after the update x2go-logo.tar.gz right away. Thanks a lot!!! Mike [1] http://anonscm.debian.org/gitweb/?p=collab-maint/python-gpyconf.git;a=blob;f=LICENSE -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpR2vJ0SmrJC.pgp Description: Digitale PGP-Unterschrift
Bug#671437: closed by Mark Brown broo...@debian.org (Re: Bug#671437: src:zlib: Please support building mingw-w64 packages)
Control: reopen -1 You've reopened this without addressing the concerns I had, especially the fact that we don't have any win32 stuff in the archive. This isn't helpful or useful. Um, that's what stuff like block and tag -1 wontfix are for. (I'm not actually doing it here because I did that before realizing I needed to explain the reopen.) After all, * This is not, in fact, done * It's more likely that someone will report a dupe if this bug is closed * It's easier to find the related bugs this way -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694873: django-tables and virtualenv
On Mon, Dec 03, 2012 at 01:00:44PM +1100, Brian May wrote: Hello, Can I please have some advice on the following bug? [1]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694873 Is everyone looking for toggleglobalsitepackages ? BTW, I was able to dupe this issue before chris filed it, but I can't recall if I was in a venv or not. Something wonky was going on, but the package looked OK. I tried switching to dh short syntax (in d/rules) and it was working fine. I didn't go much farther then that. I'll look into it later, I swear. Unfortunately I don't know virtualenv well enough to be able to explain why it is working fine for me, but not for the reporter. Every test I have performed seems to work perfectly. Please CC responses to me. Thanks -- Brian May [2]br...@microcomaustralia.com.au References Visible links 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694873 2. mailto:br...@microcomaustralia.com.au Greets, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature
Bug#668109: Bug #668109: gstreamer: shuffle mode - ogg and flac files freeze at 0:00
It seems that Ubuntu precise has no this problem. Maybe we can find different these 2 version. On Mon, Dec 3, 2012 at 9:49 AM, Andres Cimmarusti acimmaru...@gmail.comwrote: fixed 668109 gst-plugins-base1.0/1.0.3-1 tags 668109 + fixed-upstream thanks The upstream developers of gstreamer have decided to close the bug report because several people reported the problem is gone in version 1.0 of gstreamer (see https://bugzilla.gnome.org/show_bug.cgi?id=680252). Furthermore, they were never able to pin point the cause, so NO patch is available. Unfortunately Debian wheezy still doesn't have gstreamer1.0. Can we expect an update this late in the freeze? This bug affects lots of software (rhythmbox, quodlibet, totem, etc), across several desktop environments. Please consider updating to 1.0.x in wheezy thanks Andres -- YunQiang Su
Bug#694994: nautilus-open-terminal: Please update to work with Gnome 3.6
Package: nautilus-open-terminal Version: 0.19-2+b1 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Updating to Gnome 3.6 (gnome-desktop3-data 3.6.1-1) breaks nautilus-open-terminal. * What exactly did you do (or not do) that was effective (or ineffective)? Installed gnome-desktop3-data 3.6.1-1 * What was the outcome of this action? removal of nautilus-open-terminal * What outcome did you expect instead? I have been using nautilus-open- terminal for some time now without installing gnome-desktop3-data 3.6.1-1, so I can state that a simple change of depends will continue the application. -- System Information: Debian Release: Experimental APT prefers experimental APT policy: (950, 'experimental'), (850, 'unstable'), (800, 'testing'), (775, 'stable'), (500, 'testing-proposed-updates'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nautilus-open-terminal depends on: ii gconf2 3.2.5-1+build1 ii libc62.16-0experimental1 ii libgconf2-4 3.2.5-1+build1 ii libglib2.0-0 2.34.3-1 pn libgnome-desktop-3-2 none ii libgtk-3-0 3.6.1-1 ii libnautilus-extension1a 3.6.1-2 nautilus-open-terminal recommends no packages. nautilus-open-terminal suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694995: Nautilus-Open-Terminal needs depends update.
Package: nautilus-open-terminal Version: 0.19-2+b1 When I install gnome-desktop3-data, nautilus-open-terminal is un-installed. I have avoided installing gnome-desktop3-data due to the depends problem. I have used Gnome 3.6 for about a month now with the new version of Nautilus without any problems. I would suggest just updating the depends submit to Sid/Experimental for testing. I am using Debian GNU/Linux, kernel 3.6.8-1~experimental.1 (experimental), Nautilus 3.6.1-2 and libc6 2.16-0experimental1 -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#694996: lfm: move not working or broken way
Package: lfm Version: 2.2-1 Severity: important Hi, I have discovered that it is preferable not to use 'move' of lfm it is dangerous since it does copy the data differently than any linux mv function. lfm leaves chances for desaster of some data is the networking is failing when one copy over samba or nfs. It is highly recommended that lfm uses 'mv' for moving directories. Example: lfm move dvd01 /samba move dvd02 /samba with lfm it will takes ages, and it will copy bit per bits. with mv (utils of bin of linux), it will take 2sec since it simply tell linux to change the dir position. I hope it helped sincerely -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages lfm depends on: ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-support 1.0.10 automated rebuilding support for P lfm recommends no packages. lfm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694994: Mistakenly filed 2 bug reports.
Seems that I've submitted this bug report 694995 on the same topic. Please disregard 694995. It seems that if libgnome-desktop-3-4 (3.6.1-1) becomes the depend it will work -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#693874: convmv can delete data on case-insensitive filesystems
Quoting Bjoern Jacke (debianb...@j3e.de): As probably an update to 1.15 is against Debian policies: If you diff 1.14 against 1.15 the fix for this bug is the hunk that starts with # the following is to handle case-insensitive filesystems: ... I would appreciate if you could provide a patch. I looked at what you suggest but, not being a deep Perl wizard, I'm reluctant to simply add the said hunk without confirmation that it doesn't need something else. For instance, it seems to refer to the --upper and --lower command line options, but arethese supported in 1.12? With a patch, I could easily consider asking for a freeze exception for this bug. -- signature.asc Description: Digital signature
Bug#694997: After installing e16 bottom panel and title bars of all aplications have disappeared in Gnome session.
Package: e16 Version: 1.0.0-4 Severity: important Without touching anything in Gnome the problem happened after login and logout in e16. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693181: qpsmtpd: sender_permitted_framework plugin hangs on IPv6 clients
tags 693181 + wheezy security severity 693181 serious quit Thanks for the report. I'll roll a release and see if the release team will grant a freeze exemption. -- Devin \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2 signature.asc Description: Digital signature
Bug#687016: Upstart support
On Tue, 27 Nov 2012 21:17:55 Dmitrijs Ledkovs wrote: Upstart is an init system that can be used on debian instead of sysvinit. Many other packages already provide support for systemd and upstart in Debian. Since upstart integration has improved in Debian recently, upstart jobs in your package is a benefit on Debian. [1] Can you please reconsider your position and remove wontfix tag? Reconsideration requires motivation and time. At the moment I posses neither of them. I know little about upstart and I will not reconsider until I learn more, which is not a priority for now. [1] http://web.dodds.net/~vorlon/wiki/blog/Upstart_in_Debian/ This link reaffirmed my position to avoid integrating upstart for now. The article mention a little decrease in boot time which is nice however by itself probably is not enough to justify the work needed to introduce upstrat support. More important the same essay says that OpenSUSE switched from upstart to systemd which I interpret as evidence that upstart may not be suitable because of some problems with it. (Otherwise why would they stop using it?) Finally Ubuntu's decision to use upstart could be politically motivated and therefore we have to think twice about the pros and cons for Debian. So far I've seen upstart advocacy only from people affiliated with Ubuntu. Is there are any independent reviews made by people (preferably by DDs) without obvious connections to Ubuntu? Regards, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619355: lynx fails to stop on SIGTSTP (C-z)
Thomas Dickey dic...@his.com writes: I've not been able to reproduce this. Neither have been I, both on the original system (now fully upgraded to Debian Squeeze), and a recent Debian Wheezy (lynx-cur 2.8.8dev.12-2.) -- FSF associate member #7257 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693103: qpsmtpd: Missing dependency for IPv6 support
severity 693103 important quit Marking 'important' -- this doesn't meet Debian guidelines for 'serious,' quite. -- Devin \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2 signature.asc Description: Digital signature
Bug#694998: mediawiki: CVE-2012-5391 CVE-2012-5395
Package: mediawiki Severity: grave Tags: security Justification: user security hole Please see http://www.gossamer-threads.com/lists/wiki/mediawiki/316419 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694999: cityhash: CVE-2012-6051
Package: cityhash Severity: grave Tags: security Justification: user security hole Hi, please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6051 I'm not sure if/when this was fixed upstream, so better contact upstream. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690791: build process fails on Ubuntu
Hi, I am trying to build doc-debian on ubuntu, but the build process fails. Seems that the package cannot retrieves the missing files, and also it cannot find ~/debian/www/webwml/english Here are some infos build log on ubuntu: http://pastebin.ubuntu.com/1397805/ makefile: http://pastebin.ubuntu.com/1397706/ debian/rules: http://pastebin.ubuntu.com/1397802/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695000: ITP: ostinato -- Packet/Traffic Generator and Analyzer
Package: wnpp Severity: wishlist Owner: Kartik Mistry kar...@debian.org * Package name: ostinato Version : 0.5.1 Upstream Author : Srivats P. * URL : https://code.google.com/p/ostinato * License : GPL3+ Programming Lang: C++ Description : Packet/Traffic Generator and Analyzer Ostinato is an open-source, cross-platform network packet crafter/traffic generator and analyzer with a friendly GUI. Craft and send packets of several streams with different protocols at different rates. . Ostinato aims to be Wireshark in Reverse and become complementary to Wireshark. -- Kartik Mistry | IRC: kart_ {0x1f1f, kartikm}.wordpress.com signature.asc Description: Digital signature
Bug#685256: icedove: No way to add RSS feed account
Hi, Thanks for your reply. On 02-12-12 22:18, Carsten Schoenert wrote: yes it's a little bit tricky in current versions because Mozilla removed the name RSS from the menu. I can assure you that is not the problem I used http://kb.mozillazine.org/Thunderbird_:_FAQs_:_RSS_Basics and had success with version 10.0.11. The trick is to take Blog News Feed in Step 2 of the manual. If you follow the rest of this tutorial you will get your desired RSS Feed into icedove. Things already go wrong in the first step. I do not have a New - Account option in icedove. Neither do I have an Add Account option in the Tools menu. Please read in the original bug report what I found instead and how that not helped... In the mean time I have 10.0.10, and all of it still applies. -- Grtjs, Manuel PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ ) PPS: Visit my homepage at http://manuel.msxnet.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695001: mysql-5.5: New MySQL issues
Package: mysql-5.5 Severity: grave Tags: security Justification: user security hole Exploits for new MySQL issues have been posted to the full-disclosure mailing list. This mail summarises the current state of affairs: CVE-2012-5611 (formerly tracked as CVE-2012-5579) Exploit: http://seclists.org/fulldisclosure/2012/Dec/4 Patch already available through mariadb. CVE-2012-5612 Exploit: http://seclists.org/fulldisclosure/2012/Dec/5 mariadb bug: https://mariadb.atlassian.net/browse/MDEV-3908 CVE-2012-5613 Exploit: http://seclists.org/fulldisclosure/2012/Dec/6 This was discussed to be intended behaviour: http://seclists.org/oss-sec/2012/q4/388 CVE-2012-5614 Exploit: http://seclists.org/fulldisclosure/2012/De mariadb bug: https://mariadb.atlassian.net/browse/MDEV-3910 CVE-2012-5615 Exploit: http://seclists.org/fulldisclosure/2012/Dec/9 mariadb bug: https://mariadb.atlassian.net/browse/MDEV-3909 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org