Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Daniel Baumann daniel.baum...@progress-technologies.net (07/02/2013): On 02/07/2013 08:12 AM, Michael Biebl wrote: This list is getting longer with each email. Seeing that syslinux 5 has been in sid for less then 10 days, I'm worried what other issues might show up. apart from the two obvious things (debian-installer and debian-cd) that do need to be updated to copy in the additionally required c32 modules when using vesamenu.c32, there's only vbox broken. So obvious that you didn't submit any patches against the reverse build-dependencies you broke unilaterally, without any prior notice? I always thought of Debian as something which included “team work” and people interacting with each others to build a nice operating system. Apparently I was wrong all along. while i can see that one is inclined to jump to the conclusion that now each and every package in debian needs an update, it really isn't so. no package is directly interacting with a bootloader, except those that create images (debian-installer, debian-cd), or boot images *and* have bugs fixed-upstream-long-time-ago-but-not-in-debian (vbox). That's nowhere like anything which could qualify with something starting with “no package except […]”. again, note that any other virtualization software, be it in wheezy directly (qemu, kvm) or otherwise (parallels, vmware) which i've tested with, has no bugs with syslinux 5. it's an isolated thing that vbox still has that bug in debian. That's called a showstopper. Last I checked, we have nothing to gain with syslinux 5 apart losing accumulated testing, having to include patches you can't even come up with a full list of, hitting known-and-unfixed regressions, and having to bother tech-ctte instead of just releasing a new d-i. Thank you so much. Not. KiBi. signature.asc Description: Digital signature
Bug#700001: chromium: Several new errors: `[ERROR:object_proxy.cc] Failed to get name owner. …`
Package: chromium Version: 24.0.1312.68-1 Severity: normal Control: forwarded -1 http://code.google.com/p/chromium/issues/detail?id=174859 Dear Debian folks, upgrading from 22.0.1229.94~r161065+dfsg-0.1 to 24.0.1312.68-1, I see the following messages printed to the Terminal window running `chromium`. [15572:15594:0207/085606:ERROR:object_proxy.cc(608)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [15572:15594:0207/085606:ERROR:object_proxy.cc(608)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [15572:15572:0207/085606:ERROR:object_proxy.cc(513)] Failed to call method: org.chromium.Mtpd.EnumerateStorage: object_path= /org/chromium/Mtpd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.Mtpd was not provided by any .service files I did not get these messages with the earlier version 22.0.1229.94~r161065+dfsg-0.1. Upstream this is tracked under the ID 174859 [1]. Thanks, Paul [1] http://code.google.com/p/chromium/issues/detail?id=174859 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages chromium depends on: ii chromium-inspector 24.0.1312.68-1 ii gconf-service 3.2.5-1.1 ii libasound2 1.0.25-4 ii libatk1.0-0 2.4.0-2 ii libbz2-1.0 1.0.6-4 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libcups21.5.3-2.14 ii libdbus-1-3 1.6.8-1 ii libevent-2.0-5 2.0.19-stable-3 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgcc1 1:4.8-20121218-1 ii libgconf-2-43.2.5-1.1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgnome-keyring0 3.4.1-1 ii libgtk2.0-0 2.24.10-2 ii libjpeg88d-1 ii libnspr42:4.9.4-2 ii libnss3 2:3.14.1.with.ckbi.1.93-1 ii libnss3-1d 2:3.14.1.with.ckbi.1.93-1 ii libpango1.0-0 1.30.0-1 ii libpulse0 2.0-6 ii libspeex1 1.2~rc1-7 ii libstdc++6 4.8-20121218-1 ii libudev0175-7.1 ii libvpx1 1.1.0-1 ii libx11-62:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.8.0+dfsg1-7 ii libxrandr2 2:1.3.2-2 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-14 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Hi, On Wed, 06 Feb 2013, Bdale Garbee wrote: two at a time. Holding d-i's build dependencies static in unstable for more than half a year is just nuts to me! Sure seems like d-i is something we should build using the components of the release it will be contained in and not unstable... but I haven't tried to think hard about what that might imply that's problematic. And I certainly don't think this is something we should even consider changing at this late date in for wheezy release cycle! Technically d-i point release updates are built in stable-proposed-updates and build dependencies are satisfied in stable (+ s-p-u maybe). Similarly it should be possible to build d-i for wheezy in testing-proposed-updates right now (and have build-deps satisfied in wheezy). t-p-u is frowned upon for normal packages because the release team like the testing packages get in unstable, but in the case of d-i the only thing that needs to be tested are the installer images which end up on the mirror and not in the package repository (the installer directories are shared between wheezy and sid). That said this was never done yet and we're not sure what dak would do with the by-hand archive containing the installer images. Maybe some ftpmasters could answer on this point? I discussed this with Cyril and Julien and they were (rightfully IMO) not keen on trying this at this point of the release. That said this whole discussion is interesting and might even help up in the long term but the real problem is that Daniel is just actively working against the release team wishes and this is unacceptable to me. We all know the limitations of our processes, any help to improve them is welcome, but working against them is not acceptable. But judging the social behaviour of a developer is not really in the realm of the tech-ctte and the best technical outcome might not be in line with the release team's plans. Thus I would subject to word a resolution along the line of The tech-ctte suggests the release team to try out this because bar, but if the release team doesn't wish to try it out, then the release team has the right to upload an older version of syslinux to unstable (given that the maintainer deliberately ignored recommendations of the release team).. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700002: curl: CVE-2013-0249
Package: curl Severity: grave Tags: security Justification: user security hole http://curl.haxx.se/docs/adv_20130206.html Remember we're in freeze, so please upload only the minimal security fix. 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#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
i'm not commenting on unfair accusations, so only to the relevant part: On 02/07/2013 09:00 AM, Cyril Brulebois wrote: again, note that any other virtualization software, be it in wheezy directly (qemu, kvm) or otherwise (parallels, vmware) which i've tested with, has no bugs with syslinux 5. it's an isolated thing that vbox still has that bug in debian. That's called a showstopper. you're aware that regardless of syslinux version in sid, the current vbox version in wheezy will not be able to boot any post-wheezy image at all? so, again, the vbox bug is entirely unrelated to what version of syslinux is in sid now and probably should be fixed anyway, even in wheezy. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700003: [ipython] Resizing terminal garbles up the output
Package: ipython Version: 0.13.1-2 Severity: normal --- Please enter the report below this line. --- When I resize my (gnome-)terminal, for example make it bigger while ipython is running and do something like: import numpy as np np? the screen is completely garbled up. And it is not possible to read the help texts any more. As far as I know there is no way of restoring it to a normal state. With the normal python interpreter this problem does not exist. Cheers, Bastian --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: 7.0 500 unstableftp.de.debian.org 500 stable repository.spotify.com 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+-== python-configobj | 4.7.2+ds-4 python-decorator | 3.3.3-1 python-pexpect | 2.4-1 python-simplegeneric | 0.8.1-1 python (= 2.6.6-7~) | 2.7.3-3 python( 2.8) | 2.7.3-3 Package's Recommends field is empty. Suggests (Version) | Installed ===-+-== ipython-doc | ipython-notebook| 0.13.1-2 ipython-qtconsole | python-argparse | 1.2.1-2 python-matplotlib | 1.1.1~rc2-1 python-numpy| 1:1.6.2-1 python-profiler | python-zmq(= 2.0.10.1) | 2.2.0-1 -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Daniel Baumann daniel.baum...@progress-technologies.net (07/02/2013): i'm not commenting on unfair accusations, so only to the relevant part: On 02/07/2013 09:00 AM, Cyril Brulebois wrote: again, note that any other virtualization software, be it in wheezy directly (qemu, kvm) or otherwise (parallels, vmware) which i've tested with, has no bugs with syslinux 5. it's an isolated thing that vbox still has that bug in debian. That's called a showstopper. you're aware that regardless of syslinux version in sid, the current vbox version in wheezy will not be able to boot any post-wheezy image at all? so, again, the vbox bug is entirely unrelated to what version of syslinux is in sid now and probably should be fixed anyway, even in wheezy. I don't disagree. Having a fixed virtualbox would be nice. That doesn't mean we should be keeping syslinux 5 in sid in the meanwhile, especially since that's preventing us from releasing d-i wheezy rc1. KiBi. signature.asc Description: Digital signature
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/07/2013 09:59 AM, Cyril Brulebois wrote: That doesn't mean we should be keeping syslinux 5 in sid in the meanwhile, especially since that's preventing us from releasing d-i wheezy rc1. (ftr) which is where i disagree, with the mentioned patch against d-i and debian-cd, you can release d-i wheezy rc1, even with syslinux 5.x in sid. even more so: since steve uses a local copy of syslinux anyway (judging from debian-cd sources as unfortunately the setup of debian-cd on the buildhost is not documented) when invoking debian-cd, it doesn't matter at all what version of syslinux is in sid. therefore, right now, even without any patches, the only actually affected things are the images within the debian-installer-images tarball built by src:debian-installer, which i believe should be possible to fix without too much of a hassle. let me know if you want me to come up with a patch for that too. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700003: Acknowledgement ([ipython] Resizing terminal garbles up the output)
I already found the solution. Apparently the lesspipe was enabled in my .bashrc which caused the problem. If I remember correctly this was the default behavior a while ago, but currently the lesspipe is disabled in /etc/skel/.bashrc. So I assume other users are also affected, but not all. Hope that helps, Cheers, -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 07.02.2013 08:31, Raphael Hertzog wrote: Technically d-i point release updates are built in stable-proposed-updates and build dependencies are satisfied in stable (+ s-p-u maybe). Similarly it should be possible to build d-i for wheezy in testing-proposed-updates right now (and have build-deps satisfied in wheezy). For reference, it would also require an otherwise no-op upload of the debian-installer package to unstable, to ensure that testing = unstable. t-p-u is frowned upon for normal packages because the release team like the testing packages get in unstable, but in the case of d-i the only thing that needs to be tested are the installer images which end up on the mirror and not in the package repository (the installer directories are shared between wheezy and sid). I believe they once were shared; that's no longer the case - to the extent that there's a dak copy-installer command to migrate the non-package elements. 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#699911: [Pkg-postgresql-public] Bug#699911: postgresql-common: init.d start script quits if a pg cluster cannot be started so clusters after this pg cluster will also not start
Re: Frank Baalbergen 2013-02-06 51128026.7080...@mendix.com To test this, i changed the unix_socket_directory of the postgresql 9.0 cluster (second cluster). -unix_socket_directory = '/var/run/postgresql' # (change requires restart) +unix_socket_directory = '/var/run/postgresql-thisdoesnotexist' # (change requires restart) Actually that part should be fixed, too. (I ran into that yesterday myself. We have 2 clusters on the same machine both using 5432, but in different /var/run/postgresql/* directories, listening on different IPs.) Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699935: texlive-binaries: pdftex does not respect texconfig paper-size specification
On 07.02.13 Norman Ramsey (n...@cs.tufts.edu) wrote: Hi, I'm running plain TeX using 'pdftex', and it's producing A4 PDF. But I have configured it to use US letter paper both using texconfig interactively and by texconfig pdftex paper letter Something is wrong with the configuration. The whole paper stuff has been implemented in 2009-12 and later. Do you have the chance to test on Debian unstable system? H. -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Thu, 07 Feb 2013, Raphael Hertzog wrote: on the mirror and not in the package repository (the installer directories are shared between wheezy and sid). Cyril pointed out to me that this specific point is wrong, while wheezy/main/installer-* and unstable/main/installer-* have the same content right now, they are not the same (and thus not shared). There's a dak copy-installer involved to copy the installer from unstable to wheezy. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699913: Memory hotplug (VMware) often fails
Attached /proc/iomem of the situation with VMware tools - : reserved 0001-0009f3ff : System RAM 0009f400-0009 : reserved 000a-000b : PCI Bus :00 000c-000c7fff : Video ROM 000ca000-000cbfff : reserved 000ca000-000cafff : Adapter ROM 000cb000-000cbfff : Adapter ROM 000cc000-000ccfff : Adapter ROM 000d-000d3fff : PCI Bus :00 000d4000-000d7fff : PCI Bus :00 000d8000-000dbfff : PCI Bus :00 000dc000-000f : reserved 000f-000f : System ROM 0010-3fed : System RAM 0100-01356915 : Kernel code 01356916-016946ff : Kernel data 01729000-01806fff : Kernel bss 3fee-3fefefff : ACPI Tables 3feff000-3fef : ACPI Non-volatile Storage 3ff0-3fff : System RAM c000-febf : PCI Bus :00 c000-c0007fff : :00:0f.0 d000-d0001fff : :00:07.7 d020-d03f : pnp 00:0d d080-d0ff : :00:0f.0 d080-d0ff : vmwgfx stealth probe d190-d23f : PCI Bus :02 d240-d24f : PCI Bus :03 d240-d2407fff : :03:00.0 d240-d2407fff : vmw_pvscsi d250-d25f : PCI Bus :0b d250-d2501fff : :0b:00.0 d2503000-d2503fff : :0b:00.0 d2503000-d2503fff : vmxnet3 d2504000-d2504fff : :0b:00.0 d2504000-d2504fff : vmxnet3 d260-d26f : PCI Bus :13 d260-d2601fff : :13:00.0 d2603000-d2603fff : :13:00.0 d2603000-d2603fff : vmxnet3 d2604000-d2604fff : :13:00.0 d2604000-d2604fff : vmxnet3 d270-d27f : PCI Bus :1b d2702000-d2703fff : :1b:00.0 d2704000-d2704fff : :1b:00.0 d2704000-d2704fff : vmxnet3 d2705000-d2705fff : :1b:00.0 d2705000-d2705fff : vmxnet3 d280-d28f : PCI Bus :04 d290-d29f : PCI Bus :0c d2a0-d2af : PCI Bus :14 d2b0-d2bf : PCI Bus :1c d2c0-d2cf : PCI Bus :05 d2d0-d2df : PCI Bus :0d d2e0-d2ef : PCI Bus :15 d2f0-d2ff : PCI Bus :1d d300-d30f : PCI Bus :06 d310-d31f : PCI Bus :0e d320-d32f : PCI Bus :16 d330-d33f : PCI Bus :1e d340-d34f : PCI Bus :07 d350-d35f : PCI Bus :0f d360-d36f : PCI Bus :17 d370-d37f : PCI Bus :1f d380-d38f : PCI Bus :08 d390-d39f : PCI Bus :10 d3a0-d3af : PCI Bus :18 d3b0-d3bf : PCI Bus :20 d3c0-d3cf : PCI Bus :09 d3d0-d3df : PCI Bus :11 d3e0-d3ef : PCI Bus :19 d3f0-d3ff : PCI Bus :21 d400-d40f : PCI Bus :0a d410-d41f : PCI Bus :12 d420-d42f : PCI Bus :1a d430-d43f : PCI Bus :22 d440-d44f : PCI Bus :03 d440-d440 : :03:00.0 d450-d45f : PCI Bus :0b d450-d450 : :0b:00.0 d460-d46f : PCI Bus :13 d460-d460 : :13:00.0 d470-d47f : PCI Bus :1b d470-d470 : :1b:00.0 d480-d48f : PCI Bus :04 d490-d49f : PCI Bus :0c d4a0-d4af : PCI Bus :1c d4b0-d4bf : PCI Bus :0d d4c0-d4cf : PCI Bus :1d d4d0-d4df : PCI Bus :0e d4e0-d4ef : PCI Bus :1e d4f0-d4ff : PCI Bus :0f d500-d50f : PCI Bus :1f d510-d51f : PCI Bus :10 d520-d52f : PCI Bus :20 d530-d53f : PCI Bus :11 d540-d54f : PCI Bus :21 d550-d55f : PCI Bus :12 d560-d56f : PCI Bus :22 d800-dbff : :00:0f.0 d800-d80b : vesafb dc40-dc9f : PCI Bus :02 dca0-dcaf : PCI Bus :14 dcb0-dcbf : PCI Bus :05 dcc0-dccf : PCI Bus :15 dcd0-dcdf : PCI Bus :06 dce0-dcef : PCI Bus :16 dcf0-dcff : PCI Bus :07 dd00-dd0f : PCI Bus :17 dd10-dd1f : PCI Bus :08 dd20-dd2f : PCI Bus :18 dd30-dd3f : PCI Bus :09 dd40-dd4f : PCI Bus :19 dd50-dd5f : PCI Bus :0a dd60-dd6f : PCI Bus :1a e000-efff : PCI MMCONFIG [bus 00-ff] e000-efff : reserved e000-efff : pnp 00:0d fec0-fec0 : reserved fec0-fec003ff : IOAPIC 0 fed0-fed003ff : HPET 0 fed0-fed003ff : pnp 00:08 fee0-fee00fff : Local APIC fee0-fee00fff : reserved fffe- : reserved -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Daniel Baumann daniel.baum...@progress-technologies.net (07/02/2013): (ftr) which is where i disagree, with the mentioned patch against d-i and debian-cd, you can release d-i wheezy rc1, even with syslinux 5.x in sid. even more so: since steve uses a local copy of syslinux anyway (judging from debian-cd sources as unfortunately the setup of debian-cd on the buildhost is not documented) when invoking debian-cd, it doesn't matter at all what version of syslinux is in sid. That means at least broken mini.iso, which is totally unacceptable. therefore, right now, even without any patches, the only actually affected things are the images within the debian-installer-images (wrong) tarball built by src:debian-installer, which i believe should be possible to fix without too much of a hassle. let me know if you want me to come up with a patch for that too. We're not going to patch various things to cope with syslinux 5 “just because”. Especially when the list of said things is growing over time. It's time to realize that we had working things, and that you broke athem. Patching reverse dependencies isn't what is going to happen here. KiBi. signature.asc Description: Digital signature
Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/07/2013 09:31, Raphael Hertzog wrote: Technically d-i point release updates are built in stable-proposed-updates and build dependencies are satisfied in stable (+ s-p-u maybe). Similarly it should be possible to build d-i for wheezy in testing-proposed-updates right now (and have build-deps satisfied in wheezy). t-p-u is frowned upon for normal packages because the release team like the testing packages get in unstable, but in the case of d-i the only thing that needs to be tested are the installer images which end up on the mirror and not in the package repository (the installer directories are shared between wheezy and sid). That said this was never done yet and we're not sure what dak would do with the by-hand archive containing the installer images. Maybe some ftpmasters could answer on this point? Uploading d-i images to wheezy (or t-p-u) should work as far as dak is concerned. They should end in t-p-u and could be copied from there to wheezy (dak copy-installer), similar to stable updates. However I'm not sure if this has ever been tested and the RC images of d-i might not be the best time to try. I also spotted a bug when uploads would go to t-p-u instead of wheezy in the .changes (which should be fixed now)... As Adam already pointed out we would still need another d-i upload to unstable to make sure unstable has a higher-or-equal version compared to testing. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700004: src:chicken: FTBFS on x32: wrongly assumes that __x86_64__ implies 64 bits
Package: src:chicken Version: 4.8.0-1 Severity: normal Tags: patch Justification: fails to build from source In chicken.h, the following line: # if defined (__alpha__) || defined(__ia64__) || defined(__x86_64__) || defined(__LP64__) || defined(__powerpc64__) contains both a zoology of systems, and the actual feature it is looking for. The zoology is wrong: if the CPU is capable of 64 bit code, this does not mean that the architecture you're building for has 64 bit pointers. Because of compatibility with plenty of code that assumes sizeof(long) == sizeof(void*), x32 has longs of only 32 bits. What you want to check here, is whether longs are 64 bit. A fix: change that line to: # ifdef __LP64__ This lets chicken build on both amd64 and x32. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: x32 (x86_64) Kernel: Linux 3.7.1-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700005: [package:infiniband-diags] Wrong path in IBPATH prefix: /usr/local/sbin
Package: package:infiniband-diags Version: 1.6.1-1 Severity: normal --- Please enter the report below this line. --- Hi there! Regarding the package in experimental: all the scripts in /usr/sbin that include the prefix IBPATH have a wrong path. Specifically: /usr/sbin/ibhosts /usr/sbin/ibnodes /usr/sbin/ibrouters /usr/sbin/ibswitches should contain /usr/sbin as their IBPATH instead of /usr/local/sbin Thanks for your work! E --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: 7.0 900 unstableftp.debian.org 900 unstableftp.deb-multimedia.org 500 testing ftp.deb-multimedia.org 500 stable-updates ftp.es.debian.org 500 stable-updates ftp.debian.org 500 stable security.debian.org 500 stable ftp.rediris.es 500 stable ftp.es.debian.org 500 stable ftp.debian.org 500 stable ftp.deb-multimedia.org 1 experimentalftp.debian.org 1 experimentalftp.deb-multimedia.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/07/2013 10:27 AM, Cyril Brulebois wrote: That means at least broken mini.iso, which is totally unacceptable. broken without the patch i send for debian-installer, yes. therefore, right now, even without any patches, the only actually affected things are the images within the debian-installer-images (wrong) hm? We're not going to patch various things to cope with syslinux 5 “just because”. Especially when the list of said things is growing over time. i already commented on 'growing' and why that's wrong. It's time to realize that we had working things, and that you broke athem. Patching reverse dependencies isn't what is going to happen here. as elaborated, i disagree. to repeat, again, at minimum, it needs one (confirming working[0]) patch (to d-i), and steve using the wheezy local-copy of syslinux on the cdbuilder for debian-cd. not more, not less. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699385: unblock: package quantum/2012.1-5 [pre-approval]
Hi Jonathan Now the files are uploaded. Thanks for your help. // Ola Uploading to ftp-master (via ftp to ftp.upload.debian.org): Uploading quantum_2012.1-5+deb70u1.dsc: done. Uploading quantum_2012.1-5+deb70u1.debian.tar.gz: done. Uploading quantum-server_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-cisco_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-openvswitch_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-sample_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-nicira_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-linuxbridge_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-openvswitch-agent_2012.1-5+deb70u1_all.deb: done. Uploading quantum-plugin-linuxbridge-agent_2012.1-5+deb70u1_all.deb: done. Uploading python-quantum_2012.1-5+deb70u1_all.deb: done. Uploading quantum_2012.1-5+deb70u1_i386.changes: done. On Sat, Feb 02, 2013 at 10:56:05PM +, Jonathan Wiltshire wrote: On Sat, Feb 02, 2013 at 10:31:06PM +, Jonathan Wiltshire wrote: -Original Message- From: Adam D. Barratt a...@adam-barratt.org.uk To: Ola Lundqvist o...@debian.org, 699...@bugs.debian.org Sent: ons, 30 jan 2013 21:53 Subject: Re: Bug#699385: pu: package quantum/2012.1-5 user release.debian@packages.debian.org usertags 699385 = unblock retitle 699385 unblock: quantum/2012.1-5 [pre-approval] severity 699385 normal thanks On Wed, 2013-01-30 at 21:44 +0100, Ola Lundqvist wrote: Please note! This is a TESTING proposed update request. Not a stable proposed update request. The reason for this is explained below. You can go ahead with this upload to tpu but please use version 2012.1-5+deb70u1. Please ping this bug when it's uploaded. My mistake, that should be deb7u1. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Thu, Feb 07, 2013 at 07:52:13AM +0100, Daniel Baumann wrote: consider such a misfeature to be in critical need of a fix (iirc steve puts a local copy of the 'to be used' syslinux version to be used by debian-cd for release images manually on the local fs; not sure about the same that ends up in the final release copy of debian-installer-images, will check later on)). Correcting - that used to be the case several years ago, but debian-cd now explicitly extracts files from the syslinux(-common) package in the main archive at CD build time, using the same suite as used in d-i for consistency. -- Steve McIntyre, Cambridge, UK.st...@einval.com Every time you use Tcl, God kills a kitten. -- Malcolm Ray -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Daniel Baumann daniel.baum...@progress-technologies.net (07/02/2013): On 02/07/2013 10:27 AM, Cyril Brulebois wrote: That means at least broken mini.iso, which is totally unacceptable. broken without the patch i send for debian-installer, yes. If that can't be used with virtualbox (and we already established that, thanks to Michael's testing), that means it's broken with your patch too. i already commented on 'growing' and why that's wrong. That… It's time to realize that we had working things, and that you broke athem. Patching reverse dependencies isn't what is going to happen here. as elaborated, i disagree. to repeat, again, at minimum, it needs and “at minimum” doesn't exactly play along very well. one (confirming working[0]) patch (to d-i), and steve using the wheezy local-copy of syslinux on the cdbuilder for debian-cd. not more, not less. I'm going to repeat it again for you: - that's already too much - that would still mean known regressions (which you'll try to blame on virtualbox, but not going to syslinux 5 means no problem, so just let's just not use that) - and above all: that wouldn't gain us anything at all. KiBi. signature.asc Description: Digital signature
Bug#699742: Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Thu, Feb 07, 2013 at 10:15:42AM +0100, Daniel Baumann wrote: On 02/07/2013 09:59 AM, Cyril Brulebois wrote: That doesn't mean we should be keeping syslinux 5 in sid in the meanwhile, especially since that's preventing us from releasing d-i wheezy rc1. (ftr) which is where i disagree, with the mentioned patch against d-i and debian-cd, you can release d-i wheezy rc1, even with syslinux 5.x in sid. even more so: since steve uses a local copy of syslinux anyway (judging from debian-cd sources as unfortunately the setup of debian-cd on the buildhost is not documented) when invoking debian-cd, it doesn't matter at all what version of syslinux is in sid. Already corrected elsewhere (repeating for clarity for people who may not read all of the thread here) - debian-cd uses syslinux from the archive at build time. -- Steve McIntyre, Cambridge, UK.st...@einval.com Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast. Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html -- 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.0+r2361-1 [ITP]
Hi Xiangfu, I thought you'd already be a maintainer. Can we not get you update your packages without assistance? I am a bit swamped, but of course still available for sponsoring.emails hiding between other emails if I am not responsive. Best, Steffen Original-Nachricht Datum: Thu, 07 Feb 2013 14:31:53 +0800 Von: Xiangfu Liu xian...@openmobilefree.net An: 694...@bugs.debian.org CC: Paul Wise p...@debian.org Betreff: Bug#694940: RFS: toped/0.0+r2361-1 [ITP] A new toped(0.0+r2361-1, latest trunk build) have been upload to https://mentors.debian.net/package/toped Any feedback will be great. Removed: tpd_common/glf.* tiger.pnm.gz and wnf_logo.pnm.gz Fixed: add BSD license files to debian/copyright build-dep on zlib add get-orig-source to debian/rules Vcs-* fields are for the Debian packaging VCS run wrap-and-sort debhelper (= 9) fix missing full-stops in debian/control remove gds2vrml fix fails to build twice in a row (debuild debuild) fix dpkg-gencontrol warnings -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51134a59.9060...@openmobilefree.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/07/2013 10:53 AM, Cyril Brulebois wrote: If that can't be used with virtualbox (and we already established that, thanks to Michael's testing), that means it's broken with your patch too. as already elaborated, the bug in vbox needs to be fixed anyway, regardless what version of syslinux is in the archive.. and if you wait until the end of the day, that problem is gone anyway. - and above all: that wouldn't gain us anything at all. which is not an argument.. any package that i don't use/care about doesn't give any benefits to me when it get any upload. with that in mind, from my point of view, for any package that i don't use, they should be never ever touched at all to prevent bringing any (potential) bug that could affect me indirectly. i'm argueing for either an explicit unfrozen sid or an explicit frozen sid. since it's neither right now, and you intend to overwrite the maintainers decision via CTTE to upload newer syslinux to sid, you need to argue against it, not 'doesn't gain anything'. i've already made the case why i want newer syslinux in sid, and have provided patches for the two packages that needs an update for that (plus the third and only remaining one, vbox, is in the works). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700006: Fix for bug #699906: python-django-horizon: Launch from volume broken
Package: release.debian.org
Severity: normal
Hi,
I would like to upload a fix for:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699906
The diff file is attached. If the release team thinks it is suitable for
Wheezy, please let me know, and I will upload, rename this bug and tag
accordingly.
Cheers,
Thomas Goirand (zigo)
diff -Nru horizon-2012.1.1/debian/changelog horizon-2012.1.1/debian/changelog
--- horizon-2012.1.1/debian/changelog 2012-11-18 23:10:33.0 +0800
+++ horizon-2012.1.1/debian/changelog 2013-02-07 17:59:58.0 +0800
@@ -1,3 +1,10 @@
+horizon (2012.1.1-10) unstable; urgency=low
+
+ * Added patch: Launch from volume with valid volume size. Thanks to Julien
+Cristau julien.cris...@logilab.fr for reporting (Closes: 699906).
+
+ -- Thomas Goirand z...@debian.org Thu, 07 Feb 2013 17:50:55 +0800
+
horizon (2012.1.1-9) unstable; urgency=high
* Re-uploading with urgency=high.
diff -Nru horizon-2012.1.1/debian/patches/launch-from-volume-with-valid-volume-size.patch horizon-2012.1.1/debian/patches/launch-from-volume-with-valid-volume-size.patch
--- horizon-2012.1.1/debian/patches/launch-from-volume-with-valid-volume-size.patch 1970-01-01 08:00:00.0 +0800
+++ horizon-2012.1.1/debian/patches/launch-from-volume-with-valid-volume-size.patch 2013-02-07 17:59:58.0 +0800
@@ -0,0 +1,72 @@
+Description: Launch from volume with valid volume size
+Author: Sascha Peilicke sasc...@suse.de
+Origin: upstream, https://review.openstack.org/gitweb?p=openstack/horizon.git;a=patch;h=fd2291bd28a5a4331d9a7baf961c76effd17b85a
+Bug-Debian: http://bugs.debian.org/699906
+Bug-Ubuntu: https://launchpad.net/bugs/1047568
+Date: 2012-10-18
+
+diff --git a/AUTHORS b/AUTHORS
+index 4110431..677253f 100644
+--- a/AUTHORS
b/AUTHORS
+@@ -41,6 +41,7 @@ Monty Taylor mord...@inaugust.com
+ Neil Johnston onewheeldrive@gmail.com
+ Paul McMillan paul.mcmil...@nebula.com
+ Sam Morrison sorri...@gmail.com
++Sascha Peilicke sasc...@suse.de
+ Stephane Angot s...@hydre.org
+ termie git...@anarkystic.com
+ Thierry Carrez thie...@openstack.org
+diff --git a/horizon/dashboards/nova/images_and_snapshots/images/forms.py b/horizon/dashboards/nova/images_and_snapshots/images/forms.py
+index bc4851d..a6cdbad 100644
+--- a/horizon/dashboards/nova/images_and_snapshots/images/forms.py
b/horizon/dashboards/nova/images_and_snapshots/images/forms.py
+@@ -164,7 +164,7 @@ class LaunchForm(forms.SelfHandlingForm):
+ else:
+ delete_on_terminate = 0
+ dev_mapping = {data['device_name']:
+-(%s::%s % (data['volume'], delete_on_terminate))}
++(%s:%s % (data['volume'], delete_on_terminate))}
+ else:
+ dev_mapping = None
+
+diff --git a/horizon/dashboards/nova/images_and_snapshots/images/tests.py b/horizon/dashboards/nova/images_and_snapshots/images/tests.py
+index aa02325..3615288 100644
+--- a/horizon/dashboards/nova/images_and_snapshots/images/tests.py
b/horizon/dashboards/nova/images_and_snapshots/images/tests.py
+@@ -118,8 +118,8 @@ class ImageViewTests(test.TestCase):
+ sec_group = self.security_groups.first()
+ USER_DATA = 'user data'
+ device_name = u'vda'
+-volume_choice = %s:vol % volume.id
+-block_device_mapping = {device_name: u%s::0 % volume_choice}
++volume_choice = %s:vol:%s % (volume.id, volume.size)
++block_device_mapping = {device_name: u%s:0 % volume_choice}
+
+ self.mox.StubOutWithMock(api, 'image_get_meta')
+ self.mox.StubOutWithMock(api, 'flavor_list')
+@@ -269,7 +269,7 @@ class ImageViewTests(test.TestCase):
+ sec_group = self.security_groups.first()
+ USER_DATA = 'user data'
+ device_name = u'vda'
+-volume_choice = %s:vol % volume.id
++volume_choice = %s:vol:%s % (volume.id, volume.size)
+
+ self.mox.StubOutWithMock(api, 'image_get_meta')
+ self.mox.StubOutWithMock(api, 'flavor_list')
+diff --git a/horizon/dashboards/nova/images_and_snapshots/images/views.py b/horizon/dashboards/nova/images_and_snapshots/images/views.py
+index 1803f97..0b6ec5c 100644
+--- a/horizon/dashboards/nova/images_and_snapshots/images/views.py
b/horizon/dashboards/nova/images_and_snapshots/images/views.py
+@@ -117,7 +117,7 @@ class LaunchView(forms.ModalFormView):
+ else:
+ vol_type = vol
+ visible_label = _(Volume)
+-return ((%s:%s % (volume.id, vol_type)),
++return ((%s:%s:%s % (volume.id, vol_type, volume.size)),
+ (%s - %s GB (%s) % (volume.display_name,
+ volume.size,
+ visible_label)))
+--
+1.7.9.5
+
diff -Nru horizon-2012.1.1/debian/patches/series horizon-2012.1.1/debian/patches/series
--- horizon-2012.1.1/debian/patches/series 2012-11-18 23:10:33.0 +0800
+++
Bug#694473: Fix doesn't work for me
Hello on my testing system which also updated yesterday and today I get the same error again. So for me it isn't solved. Kind regards Mechtilde signature.asc Description: OpenPGP digital signature
Bug#687442: success with 3.2.0-4.drm-amd64 on a Thinkpad T530
I too had several system freezes each week when running the default kernel in wheezy. I upgraded to 3.2.0-4.drm-amd64 over a week ago, and my machine (a Thinkpad T530 Ivy Bridge with Intel HD Graphics 4000) has worked flawlessly ever since. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Daniel Baumann, le Thu 07 Feb 2013 11:08:55 +0100, a écrit : i've already made the case why i want newer syslinux in sid, I must have missed that, and I can't find it on either bug #699382, 699742 or 699808. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699938: apt-cacher: debug error log: Failed to reopen content: No such file or directory at /usr/sbin/apt-cacher line 1671 | Response: 502 apt-cacher internal error (died)
- Original message - Package: apt-cacher Version: 1.7.6 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** It is very difficult for me to help without you completing even basic information about what has happened. Please answer these: * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Also, is this error on every request? Every time or occasional? -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32.12 Is this a stock kernel or your own? Do you have /dev/fd? Are you running udev? Which version? -- debconf information: * apt-cacher/mode: manual How is apt-cacher invoked? Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694473: [php-maint] Bug#694473: Fix doesn't work for me
Please provide a backtrace. And if you can please test with PHP from experimental. Thanks, Ondrej On Thu, Feb 7, 2013 at 11:11 AM, Mechtilde o...@mechtilde.de wrote: Hello on my testing system which also updated yesterday and today I get the same error again. So for me it isn't solved. Kind regards Mechtilde ___ pkg-php-maint mailing list pkg-php-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/07/2013 11:17 AM, Samuel Thibault wrote: I must have missed that, and I can't find it on either bug #699382, 699742 or 699808. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699808#10 -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699852: syncevolution-http: sync from nokia e51 to syncevo-http-server not possible invalid server [ERROR] twisted: Unhandled Error
Hi, following the advice of Patrick Ohly, I compiled the latest version of syncevolution (1.3.99.2) on this machine and the issue is resolved. Please upgrade syncevolution to this version. Regards Christof -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part.
Bug#700007: netpbm: please mark Multi-Arch: foreign
Package: netpbm
Version: 2:10.0-15
Severity: wishlist
Tags: patch
User: crossbu...@debian.org
Usertags: cross
Hi,
Enough source packages (41 in unstable) Build-Depend on netpbm that it
would be very helpful to have it marked as Multi-Arch: foreign, on the
basis that even though it's Architecture: any it doesn't matter which
architecture you get on a multiarch system as long as you can execute
the binary. This would make it easier to cross-build those packages.
The patch is trivial, but it follows in case it helps. Note that this
is independent of adding multiarch support to libnetpbm*.
* Make netpbm Multi-Arch: foreign, so that it can satisfy
cross-build-dependencies.
diff -u netpbm-free-10.0/debian/control netpbm-free-10.0/debian/control
--- netpbm-free-10.0/debian/control
+++ netpbm-free-10.0/debian/control
@@ -11,6 +11,7 @@
Package: netpbm
Architecture: any
+Multi-Arch: foreign
Depends: libnetpbm10 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
Recommends: ghostscript
Conflicts: netpbm-nonfree (= 1:19940301.1-3), pnmtopng, pbmwbmp, netpbm-dev
(= 2:9.10), ucbmpeg (= 1r2-6)
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#692381: yafaray: FTBFS against python3.3
Hi Dmitrijs! Sad to be said, but I've tested your patch and it fails to recognize python3.3 in Debian; so it builds fine... but keeps using python3.2 ;-( I need to investigate further on this issue. Anyhow, thanks for your efforts in solving this problem. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 83B2CF7A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Thu, Feb 07, 2013 at 11:08:55AM +0100, Daniel Baumann wrote: i'm argueing for either an explicit unfrozen sid or an explicit frozen sid. since it's neither right now, and you intend to overwrite the maintainers decision via CTTE to upload newer syslinux to sid, you need to argue against it, not 'doesn't gain anything'. Daniel, I don't think this is the place for such a broad discussion. I believe we would all agree that a frozen distro development (no matter the suite where it happens) is a PITA that we could all live without. But at present, this is what our release processes and technologies offer. Like it or not. It would be very nice to improve them, and I've high hopes that dak based personal package archives would help a lot with that, but this is not the time for this kind of changes. More importantly, it is arguably false that sid is not explicitly frozen. The freeze policy [1], which has been repeatedly announced on d-d-a, reads: Please also note that since many updates (hopefully, the vast majority) will still be going in through unstable, major changes in unstable right now can disrupt efforts to get RC bugs fixed. We don't ask you not to make changes in unstable, but we do ask that you be aware of the effects your changes can have -- especially if you maintain a library. Please continue to keep disruptive changes out of unstable and continue making use of experimental where appropriate. Note that you can stage NEW uploads in experimental to avoid disruption in unstable. [1]: http://release.debian.org/wheezy/freeze_policy.html by evidence, your change to unstable has been disruptive. I understand (better, I trust your claim on that, but I haven't checked) that experimental is not a viable path for syslinux development. But that is no justification for getting in the way of a release, going explicitly against the freeze policy. Please put back in sid the syslinux version that the release team wants to see in there. Ideally, it wouldn't be for long, and an action of that kind will avoid burning cycles of all the people participating in this thread. I'm pretty sure we can all use those cycles to the betterment of Wheezy instead. As soon as Wheezy is out of the door, please re-raise this topic in a project-wide place, where we can work on solutions to avoid this kind of frustrating long freezes. That would be the appropriate time and place for this kind of discussions. Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » signature.asc Description: Digital signature
Bug#700008: FTBFS: strip.c:24:28: fatal error: linux/if_strip.h: No such file or directory
Package: src:net-tools Version: 1.60-24.2 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Apparently, STRIP support is now an unthing, and kernel headers no longer have it. Ubuntu have already patched it; from their patch: diff -pruN 1.60-24.2/debian/config.h 1.60-24.2ubuntu1/debian/config.h --- 1.60-24.2/debian/config.h 2012-12-04 01:05:53.0 + +++ 1.60-24.2ubuntu1/debian/config.h2012-12-04 01:05:54.0 + @@ -49,8 +49,8 @@ #define HAVE_HWSLIP 1 #define HAVE_HWPPP 1 #define HAVE_HWTUNNEL 1 -#define HAVE_HWSTRIP 1 -#define HAVE_HWTR 1 +#define HAVE_HWSTRIP 0 +#define HAVE_HWTR 0 #define HAVE_HWAX25 1 #define HAVE_HWROSE 1 #define HAVE_HWNETROM 1 diff -pruN 1.60-24.2/debian/config.make 1.60-24.2ubuntu1/debian/config.make --- 1.60-24.2/debian/config.make2012-12-04 01:05:53.0 + +++ 1.60-24.2ubuntu1/debian/config.make 2012-12-04 01:05:54.0 + @@ -16,8 +16,8 @@ HAVE_HWARC=1 HAVE_HWSLIP=1 HAVE_HWPPP=1 HAVE_HWTUNNEL=1 -HAVE_HWSTRIP=1 -HAVE_HWTR=1 +HAVE_HWSTRIP=0 +HAVE_HWTR=0 HAVE_HWAX25=1 HAVE_HWROSE=1 HAVE_HWNETROM=1 which makes net-tools build again. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.1-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699936: PTS: clang archive recompilation links
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2013 02:09, Paul Wise wrote: Package: qa.debian.org Severity: normal User: qa.debian@packages.debian.org Usertags: pts X-Debbugs-CC: Sylvestre Ledru sylves...@debian.org The PTS should link to clang.debian.net for packages that fail to build with LLVM/Clang. More information about clang.d.n is here: http://sylvestre.ledru.info/blog/sylvestre/2013/02/06/rebuild_of_debian_using_clang_3_2 Requirements from the clang.d.n site: Per-source-package pages with predictable URLs and links to build logs. A list of source packages which the PTS should link to. This can just be a new-line separated list of packages. If more than just a link is needed, machine-readable info about what should be presented will be needed. I can do that this week end. :) We had this discussion a while ago: http://lists.debian.org/debian-qa/2012/02/msg00089.html At this time, you didn't had any preference on the format. Is it still the case ? I write some various formats if you want. Thanks again, Sylvestre -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlETidMACgkQiOXXM92JlhByHwCgsy2PJHXgNUwXAz7uZ48p1Noo EsMAoLBpiQzFXEj8TzPHLdKr7PKBSOjy =Ju8b -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#693822: Add multiarch metadata
[I didn't write the wiki page in question here, but perhaps I can help to clarify it.] On Thu, Jan 24, 2013 at 08:09:25PM +0100, Sandro Tosi wrote: On Thu, Jan 17, 2013 at 5:13 AM, Wookey woo...@wookware.org wrote: That's not what that paragraph says. Sorry if it's confusing. You shouldn't add M-A: foreign if the package isn't arch-independent in it's _effects_ (i.e you should set M-A: foreign if the package's _effect_ is arch-independent). Whether the package itself is arch :any or not is not relevent. So fdupes will find duplicate files just the same if you run the arm version or the sparc version or the i386 version. That makes it M-A: foreign. I don't get why it wouldn't find duplicate files. The same I don't get why it would need to add that, in particular because you skipped the part about apt solution, would would avoid to fix (?) several packages. The bit in that page about apt is not relevant to fdupes anyway, since fdupes is Architecture: any, not all. Here's the deal given apt's current behaviour (I'm simplifying a bit to avoid boredom, but this at least covers any/all and foreign/not): 1) Architecture: any, not M-A: foreign These packages contain architecture-dependent code, and also have architecture-dependent effects: that is, you need to pick the build of the package for the correct architecture. For example, libraries are generally like this, as are some tools that only operate on objects of the same architecture (say, binutils). This is a safe conservative default for Architecture: any packages, since it's how all such packages worked before multiarch came along. 2) Architecture: any, M-A: foreign These packages contain architecture-dependent code, but it really doesn't matter which architecture you get as long as you can execute the binaries. Many simple tools are like this, although we can't safely assume that any given tool will be like this without being told; failing to cross-build something because we can't satisfy its cross-build-dependencies is better than cross-building it incorrectly, and likewise for run-time uses of multiarch. 3) Architecture: all, not M-A: foreign These packages contain architecture-independent code, but they may only satisfy dependencies of packages of the primary architecture or of other packages that are also Architecture: all. The reason for this restrictions is to avoid breaking pre-multiarch assumptions of packages that depend on Architecture: all packages and assume that *their* (transitive) dependencies will be resolved using the native architecture. A package that contained an architecture-independent tool but that also depended on libfoo-dev might be in this category. 4) Architecture: all, M-A: foreign These packages contain architecture-independent code, and they may satisfy dependencies of packages of any architecture. Most architecture-independent packages fall into this category. Steve's proposal in #666772 is to say that we don't need to be ultra-conservative for cross-build-dep handling, and for that purpose we can treat 3) like 4). Based on my experience with cross-building, I tend to agree that that makes sense - but it doesn't have any effect on this bug either way. It would not make sense to extend #666772 to Architecture: any packages, because very many of those *do* have architecture-dependent effects; all that this would achieve would be having to add a roughly similar number of Multi-Arch: tags to packages in the other direction. If you could explain why you misunderstood the When shouldn't I add M-A: foreign?, I'll try and improve the wording. Well, if you start a paragraph saying When the package is not arch-independent that means to me it's arch:any, short-cut, that package is not requires a M-A: foreign. The full sentence you're quoting is: When the package is not arch-independent in its effects, i.e if you run the wrong-arch version it will operate on the wrong files or produce the wrong output. The in its effects matters here. That is, binutils is architecture-dependent in its effects, because (for example) the armhf version of nm operates only on armhf objects while the i386 version of nm operates only on i386 objects; but the effects of fdupes are architecture-independent, even though it happens to be a compiled executable. Architecture: any packages are precisely those which are rather evenly divided between those where the architecture you get matters and those where it doesn't. A substantial number of them have already correctly had Multi-Arch: foreign added to them, and fdupes should too. Does this help? -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700009: redmine: Rest-API in redmine 1.4.4 does not work see http://www.redmine.org/issues/11298
Package: redmine
Version: 1.4.4+dfsg1-1.1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages redmine depends on:
ii bundler 1.1.4-6
ii dbconfig-common 1.8.47+nmu1
ii debconf [debconf-2.0] 1.5.49
ii redmine-mysql 1.4.4+dfsg1-1.1
ii ruby 4.9
ii ruby-coderay 1.0.6-2
ii ruby-fastercsv1.5.5-1
ii ruby-net-ldap 0.3.1-2
ii ruby-rack 1.4.1-2
ii ruby-rails-2.32.3.14-4
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-5
redmine recommends no packages.
Versions of packages redmine suggests:
pn bzr none
pn cvs none
pn darcs none
ii git 1:1.7.10.4-1+wheezy1
ii mercurial 2.2.2-1
pn ruby-openid none
pn ruby-rmagick none
ii subversion1.6.17dfsg-4
-- debconf information:
redmine/instances/default/db/app-user: redmine
redmine/instances/default/passwords-do-not-match:
* redmine/instances/default/default-language: en
redmine/instances/default/remote/newhost:
redmine/instances/default/db/basepath:
redmine/notify-migration:
redmine/old-instances:
redmine/instances/default/upgrade-error: abort
redmine/instances/default/pgsql/changeconf: false
redmine/instances/default/missing-db-package-error: abort
redmine/instances/default/db/dbname: redmine_default
redmine/instances/default/purge: false
* redmine/current-instances: default
redmine/instances/default/remote/host:
redmine/default-language: ${defaultLocale}
redmine/instances/default/dbconfig-upgrade: true
redmine/instances/default/pgsql/no-empty-passwords:
redmine/instances/default/internal/reconfiguring: true
redmine/instances/default/upgrade-backup: true
redmine/instances/default/pgsql/method: unix socket
redmine/instances/default/install-error: abort
redmine/instances/default/mysql/admin-user: root
* redmine/instances/default/database-type: mysql
redmine/instances/default/pgsql/manualconf:
redmine/instances/default/pgsql/authmethod-admin: ident
redmine/instances/default/mysql/method: unix socket
redmine/instances/default/internal/skip-preseed: true
redmine/instances/default/pgsql/admin-user: postgres
redmine/instances/default/remove-error: abort
redmine/instances/default/dbconfig-remove:
redmine/missing-redmine-package:
redmine/instances/default/remote/port:
redmine/instances/default/pgsql/authmethod-user: password
* redmine/instances/default/dbconfig-install: true
* redmine/instances/default/dbconfig-reinstall: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699936: PTS: clang archive recompilation links
On Thu, Feb 7, 2013 at 7:02 PM, Sylvestre Ledru wrote: I can do that this week end. :) Great :) We had this discussion a while ago: http://lists.debian.org/debian-qa/2012/02/msg00089.html Woops! At this time, you didn't had any preference on the format. Is it still the case ? I write some various formats if you want. Lets start with a newline separated list of source packages that the PTS should link to. It will link to the clang source package URLs with the text clang build issues. If you want to add TODO items we can switch to something else later. -- bye, pabs http://wiki.debian.org/PaulWise -- 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.0+r2361-1 [ITP]
Xiangfu Liu xian...@openmobilefree.net writes:
A new toped(0.0+r2361-1, latest trunk build) have been upload to
https://mentors.debian.net/package/toped
1) Minor spelling errors in description, patch attached
(0001-toped-improve-package-description.patch).
2) Vcs-Git points to a repository that actually has packaging for three
different packages. The policy is not too clear on this but you might
want to browse around at http://anonscm.debian.org/gitweb/ to get an
overview of all the different ways people use vcs-git :) (I have written
an automated tool that clones the repository of a package and assumes
that debian/copyright exists, in your case it'd need to somehow guess
that it needs to access toped/debian/copyright.)
3) lintian complains
W: toped-libs: package-name-doesnt-match-sonames libtpd-DB0 libtpd-GL0
libtpd-bidfunc0 libtpd-common0 libtpd-ifaces0 libtpd-parser0
Does
Shared object files (often `.so' files) that are not public
libraries, that is, they are not meant to be linked to by third
party executables (binaries of other packages), should be
installed in subdirectories of the `/usr/lib' directory. Such
files are exempt from the rules that govern ordinary shared
libraries, except that they must not be installed executable and
should be stripped.
from policy 10.2 apply here? I don't know what
./usr/lib/x86_64-linux-gnu/libtpd_GL.so.0.0.0
does but since there is no -dev package surely third party executables
can be linked against them?
From 7d7b06e10f9e576af2e8af1a6a207e02cfea60a6 Mon Sep 17 00:00:00 2001
From: Timo Juhani Lindfors timo.lindf...@iki.fi
Date: Thu, 7 Feb 2013 13:19:44 +0200
Subject: [PATCH] toped: improve package description
---
toped/control | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/toped/control b/toped/control
index 54992a0..2d92003 100644
--- a/toped/control
+++ b/toped/control
@@ -28,13 +28,13 @@ Depends:
${shlibs:Depends}
Description: Open source IC layout editor
Toped is a cross-platform IC layout editor supporting GDS,
- OASIS and CIF formats. it is an open source project licensed
- under the GNU General Public License. the project is under
+ OASIS and CIF formats. It is an open source project licensed
+ under the GNU General Public License. The project is under
active development.
.
- Toped is driven by a build-in script interpreter. the script
+ Toped is driven by a build-in script interpreter. The script
is designed to code and facilitate the layout generation and
- is used also for configuration. automatic session recovery,
+ is used also for configuration. Automatic session recovery,
undo with unlimited depth and customizable GUI are among the
product features.
.
@@ -53,8 +53,8 @@ Depends:
${shlibs:Depends}
Description: libraries of toped
Toped is a cross-platform IC layout editor supporting GDS,
- OASIS and CIF formats. it is an open source project licensed
- under the GNU General Public License. the project is under
+ OASIS and CIF formats. It is an open source project licensed
+ under the GNU General Public License. The project is under
active development.
.
This package provides a shared library for toped.
@@ -66,11 +66,11 @@ Depends:
${misc:Depends}
Description: tell libs of toped
Toped is a cross-platform IC layout editor supporting GDS,
- OASIS and CIF formats. it is an open source project licensed
- under the GNU General Public License. the project is under
+ OASIS and CIF formats. It is an open source project licensed
+ under the GNU General Public License. The project is under
active development.
.
- This package provides tell libs for toped.
+ This package provides tll libs for toped.
Package: toped-utils
Architecture: any
@@ -79,8 +79,8 @@ Depends:
${misc:Depends}
Description: some utils work with toped
Toped is a cross-platform IC layout editor supporting GDS,
- OASIS and CIF formats. it is an open source project licensed
- under the GNU General Public License. the project is under
+ OASIS and CIF formats. It is an open source project licensed
+ under the GNU General Public License. The project is under
active development.
.
This package provides some utils work with toped.
--
1.7.2.5
Bug#700006: Fix for bug #699906: python-django-horizon: Launch from volume broken
On 2013-02-07 10:05, Thomas Goirand wrote: Package: release.debian.org Severity: normal Hi, I would like to upload a fix for: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699906 The diff file is attached. If the release team thinks it is suitable for Wheezy, please let me know, and I will upload, rename this bug and tag accordingly. The diff looks fine in principle, let's see how it gets on in sid. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- 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.0+r2361-1 [ITP]
Timo Juhani Lindfors timo.lindf...@iki.fi writes: does but since there is no -dev package surely third party executables can be linked against them? ^^^ Meant cannot here of course. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690192: python-zookeeper truncates paths with more than 255 characters.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Paul On 11/10/12 01:43, Paul Dwerryhouse wrote: There appears to be a problem with python-zookeeper's handling of nodes with that have a total path length that is greater than 255 characters. It can be demonstrated with this simple test program, which creates a node with path length of 302 characters. The return value from zookeeper.create should be exactly the same, in this case, but instead, it is trucated at 255 characters: Digging into the python source code reveals that the buffer used to hold the path returned from zookeeper is only 256 bytes; the zookeeper C code truncates the path to fit the buffer resulting in the shortened return path. I agree that this does appear to be odd behaviour - I'll dig a bit deeper. - -- James Page Ubuntu Core Developer Debian Maintainer james.p...@ubuntu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRE5WyAAoJEL/srsug59jDPrUP/iGwJFNeU9lAIg5hfZW6Rtlx b8U6nr4yb168SNB+dRJoBBtKO+dr9UqU0Rt2uGDa7aTKI6PT2zoKI4J3PgMpRwcH s7f8mgF/k0f1SHF9N7drSl2ewMinkVf9BWD1GdG/1l2E8PFmsflsQsY5UQAdEaBQ PfJuOlp6kfHCPEMCtaFCPghNE8Fbu+hQy49LeAzDTkKXzOkEW+QACtsP+ZCDEUxD I0UlT0IW2HK+flNIaR4neS40e1ENJWBuZLqKM4S4M3VXMG3NQL3T3jx2CUtLLBg3 UokAuAD45pMcGSFtAVaCO3FB6gQHv6jEfg3kRTdGEltwrLIb9Wd8RobVQ396H5Nc 53kjbLRpW0b6Ys53eY6bQafS+KaEfv0ZztJyfiCkkrkmFb8rWfQ2IN80t69M7UpF 860XZVUYtTzSW264m1ZI6tT4mDZDltAFY412+oqKgHfP5RGBfSBe600K0L8Y9Q8O sLdGCI0k0nkCpb2kki7zgNcR+pQCb+UMpBX4FMgArzoC90tKdrTkM6p99Q2PzBo4 RYQZLHxkHq/FjM/3QFg1mp0KM5d5Tp+VySXH04Q8UJvDfo6rDtL/gq5ROsTLrd/o GJwhOUphWStSad98VPpZGe3vlL0XuJh/fcUJlv7lOYPFD50dd/FBQZnzAe3MsmzF G2QcqkaeM80ARu5cyb9u =E3sy -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#700010: src:xorg: FTBFS on x32: no debian/scripts/vars.x32
Package: src:xorg Version: 1:7.7+1 Severity: normal Tags: patch Hi! xorg fails to build on x32, as it requires a definition for every new architecture. In this case, instead of copying, it'd be better to symlink vars.amd64, as these architectures can't go out of sync: the list of available hardware will be always exactly the same. There's no such thing as an x32 kernel -- it's merely an amd64 one with CONFIG_X86_X32=y, that makes it capable of running binaries from both architectures. So, the patch: (cd debian/scripts ln -s vars.amd64 vars.x32) -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: x32 (x86_64) Kernel: Linux 3.7.1-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700011: xaaa.tif: Compression scheme 33005 tile decoding is not implemented.
Package: libtiff-tools Version: 3.9.4-5+squeeze7 Severity: important Tags: upstream tiffcp has a surprising behavior upon failure. When converting a TIFF with an unsupported Compression scheme, tiffcp simply returns '0'. $ tiffcp -8 -c none xaaa.tif xaaa_none.tif xaaa.tif: Compression scheme 33005 tile decoding is not implemented. xaaa.tif: Compression scheme 33005 tile decoding is not implemented. xaaa.tif: Compression scheme 33005 tile decoding is not implemented. xaaa.tif: Compression scheme 33005 tile decoding is not implemented. xaaa.tif: Compression scheme 33005 tile decoding is not implemented. xaaa.tif: Compression scheme 33005 tile decoding is not implemented. ... $ echo $? 0 The resulting image is all black, which is of very little interest if none. Thanks -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libtiff-tools depends on: ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libtiff43.9.4-5+squeeze8 Tag Image File Format (TIFF) libra ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libtiff-tools recommends no packages. Versions of packages libtiff-tools suggests: pn libtiff-openglnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700012: bible-kjv: FTBFS on x32: assumes sizeof(time_t) == sizeof(long)
Package: bible-kjv
Version: 4.26
Severity: normal
Tags: patch
Hi! I'm afraid your package fails to build on an upcoming architecture,
x32, because of its assumption about time_t size.
Patch:
--- makeindex.c~2011-06-25 12:30:53.0 +
+++ makeindex.c 2013-02-07 11:55:33.091069052 +
@@ -94,7 +94,7 @@
int main(int argc,char **argv)
{
FILE *fp;
-long t;
+time_t t;
long cur_line;
long offset;
char textbuff[TBSIZE];
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Kernel: Linux 3.7.1-x32 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bible-kjv depends on:
ii bible-kjv-text 4.26
ii libc6 2.16-0experimental1
ii libreadline66.2+dfsg-0.1
bible-kjv recommends no packages.
Versions of packages bible-kjv suggests:
pn verse none
-- 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#700013: libxcb1: libxcb crashes on systems with Mali graphics
Package: libxcb1
Version: 1.8.1-2
Severity: important
Hello,
running es2_info on a system with mali graphics causes crash.
The Mali EGL library uses thread internally.
The interface to the user program should be single-threaded, however.
ldd es2_info
libGLESv2.so = /usr/lib/arm-linux-gnueabihf/libGLESv2.so (0xb6f12000)
libm.so.6 = /lib/arm-linux-gnueabihf/libm.so.6 (0xb6ea6000)
libX11.so.6 = /usr/lib/arm-linux-gnueabihf/libX11.so.6 (0xb6dbd000)
libXext.so.6 = /usr/lib/arm-linux-gnueabihf/libXext.so.6 (0xb6dab000)
libc.so.6 = /lib/arm-linux-gnueabihf/libc.so.6 (0xb6cc6000)
libUMP.so = /usr/lib/arm-linux-gnueabihf/libUMP.so (0xb6cb9000)
libpthread.so.0 = /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6c9d000)
libdl.so.2 = /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6c92000)
libgcc_s.so.1 = /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb6c6e000)
/lib/ld-linux-armhf.so.3 (0xb6fe1000)
libxcb.so.1 = /usr/lib/arm-linux-gnueabihf/libxcb.so.1 (0xb6c53000)
libdri2.so.1 = /usr/lib/arm-linux-gnueabihf/libdri2.so.1 (0xb6c49000)
libdrm.so.2 = /usr/lib/arm-linux-gnueabihf/libdrm.so.2 (0xb6c38000)
libXfixes.so.3 = /usr/lib/arm-linux-gnueabihf/libXfixes.so.3
(0xb6c2c000)
libXau.so.6 = /usr/lib/arm-linux-gnueabihf/libXau.so.6 (0xb6c22000)
libXdmcp.so.6 = /usr/lib/arm-linux-gnueabihf/libXdmcp.so.6 (0xb6c17000)
librt.so.1 = /lib/arm-linux-gnueabihf/librt.so.1 (0xb6c09000)
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1.
[xcb] Unknown request in queue while appending request
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
[New Thread 0xb6c0d470 (LWP 11163)]
[New Thread 0xb640d470 (LWP 11164)]
[New Thread 0xb5c0d470 (LWP 11165)]
Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=0xb6dab258, bytes=100) at malloc.c:4439
4439malloc.c: No such file or directory.
#0 _int_malloc (av=0xb6dab258, bytes=100) at malloc.c:4439
iters = optimized out
nb = 104
idx = 13
bin = optimized out
victim = 0x18308
size = 16392
victim_index = optimized out
remainder = optimized out
remainder_size = optimized out
block = optimized out
bit = optimized out
map = optimized out
fwd = optimized out
bck = 0x10004
errstr = 0x0
__func__ = _int_malloc
#1 0xb6d1fd68 in __GI___libc_malloc (bytes=100) at malloc.c:3660
ar_ptr = 0xb6dab258
victim = optimized out
hook = optimized out
__func__ = __libc_malloc
#2 0xb6d1560e in _IO_vasprintf (result_ptr=0xbefff9e4, format=0xb6d93008
%s%s%s:%u: %s%sAssertion `%s' failed.\n, args=...) at vasprintf.c:52
string = optimized out
sf = {_sbf = {_f = {_flags = 1298088780, _IO_read_ptr = 0x41535345
Address 0x41535345 out of bounds, _IO_read_end = 0x2f534547 Address
0x2f534547 out of bounds, _IO_read_base = 0x6362696c Address 0x6362696c out
of bounds, _IO_write_base = 0x6f6d2e Address 0x6f6d2e out of bounds,
_IO_write_ptr = 0xb6cea723 F\327\370\224, _IO_write_end = 0xb6dad2e8
U\200\312\266, _IO_buf_base = 0x Address 0x out of bounds,
_IO_buf_end = 0xbeff0043 , _IO_save_base = 0xb6cea9c7
\346\376\367\364\373\003x\004FC+\030\277\064F\177\364\257\256cx,
_IO_backup_base = 0xb6ff548c symbol=%s; lookup in file=%s [%lu]\n,
_IO_save_end = 0xb6dc4df8 , _markers = 0x0, _chain = 0x0, _fileno = 0,
_flags2 = 357, _old_offset = -1224756536, _cur_column = 11, _vtable_offset = 0
'\000', _shortbuf = , _lock = 0x4, _offset = 3070194880, _codecvt = 0x0,
_wide_data = 0x0, _freeres_list = 0xb6d92ea8, _freeres_buf = 0xb6d92ec0,
_freeres_size = 3204446448, _mode = -1227186176, _u
nused2 =
\\000\000\000\250.\331\266\005\000\000\000\020\371\377\276\377\377\377\377\000\000\000\000\\000\000\000\005\000\000\000\b0\331\266\000\000\000},
vtable = 0xb6ff74c0}, _s = {_allocate_buffer = 0x5, _free_buffer = 0xa4}}
ret = optimized out
needed = optimized out
allocated = optimized out
#3 0xb6d01858 in ___asprintf (string_ptr=optimized out, format=0xb6d93008
%s%s%s:%u: %s%sAssertion `%s' failed.\n) at asprintf.c:37
arg = {__ap = 0xbefff9c0}
done = 268435456
#4 0xb6ce9224 in __GI___assert_fail (assertion=0xb6e369b4
!xcb_xlib_unknown_req_pending, file=0xb6e368b0 ../../src/xcb_io.c,
line=164, function=optimized out) at assert.c:59
buf = optimized out
#5 0xb6deaee4 in append_pending_request (dpy=0xb6e36770, sequence=optimized
out) at ../../src/xcb_io.c:162
xcb_xlib_unknown_req_pending = 1
node = optimized out
__PRETTY_FUNCTION__ = append_pending_request
#6 0xb6deb7a0 in _XReply (dpy=0x12008, rep=0xbefffa40, extra=0, discard=1) at
../../src/xcb_io.c:584
error = optimized out
Bug#699596: syslinux-common: vesamenu.c32 is not a valid com32 image
On jeu., 2013-02-07 at 08:37 +0100, Daniel Baumann wrote: On 02/06/2013 10:03 PM, Yves-Alexis Perez wrote: There's no such thing as libcom32.c32 in /boot so that'd explain why. you might want to look at the bug it was merged with, specifically: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699382#40 And? I'm not especially saying it's not the same bug, just that: - my system is not unbootable - I have no idea if it's syslinux or syslinux-themes-debian fault - the bug is still present in 2:5.01+dfsg-1 / 12-1.1 If it needs manual tuning in some scripts to port it to the new syslinux, then fine, you seem to be the de factor maintainer of both packages so everything's under your control. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#693208: Bug#699899: tpu: clang/3.0-6.1+deb7u0
Hi Adam, Adam D. Barratt a...@adam-barratt.org.uk writes: I wasn't particularly suggesting re-introducing 3.0 to unstable. However, given that packages from tpu get essentially no testing at all (no pun intended) before hitting testing, being able to prove a patch in unstable first avoids a number of (admittedly not all) potential issues. Now I understand what your point was, thanks for clarifying. Looking at the proposed tpu diff and the 3.0 - 3.1 diff, it looks like the armhf changes should apply as is to 3.1; has anyone tried that? I have ported the patches from 3.0 to 3.1 and successfully built the package on amd64, where it works. Therefore, I will now build it on armhf, which will take around a day. Sylvestre: Are you okay with me NMUing clang 3.1-8.1 to unstable in order to expose my changes to a wider audience before we do the fix via t-p-u? -- 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#699596: syslinux-common: vesamenu.c32 is not a valid com32 image
On 02/07/2013 01:02 PM, Yves-Alexis Perez wrote: - I have no idea if it's syslinux or syslinux-themes-debian fault did you read the other bug? usually, opening a duplicate bug doesn't mean that the maintainer will re-tell the whole story again, and that pointing to the first bug about the same issue should be enough, so that the bug reporter would read it there when being pointed at it. - the bug is still present in 2:5.01+dfsg-1 / 12-1.1 that's why it's open and not closed yet. If it needs manual tuning in some scripts to port it to the new syslinux, then fine, you seem to be the de factor maintainer of both packages so everything's under your control. look at the live-build commit and replicate it in /usr/share/syslinux/theme/$your_theme, or wait until the theme in debian is fixed. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700014: keepassx: If file changed file is not locked on timeout
Package: keepassx Version: 0.4.3-2 Severity: normal Dear Maintainer, If you change a database and do not save it the Lock database after inactivity does not work. If the file is saved or no changes were made, it works. If changes are not saved, instead of locking, KeepassX puts up a dialog asking if you want to save changes - Yes, No or Cancel. At this point a user could press Cancel and see the DB. The security of Lock database after inactivity has been bypassed! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages keepassx depends on: ii libc6 2.13-37 ii libgcc1 1:4.7.2-4 ii libqt4-xml 4:4.8.2+dfsg-2 ii libqtcore4 4:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libstdc++6 4.7.2-4 ii libx11-62:1.5.0-1 ii libxtst62:1.2.1-1 keepassx recommends no packages. keepassx 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#699596: syslinux-common: vesamenu.c32 is not a valid com32 image
On jeu., 2013-02-07 at 13:19 +0100, Daniel Baumann wrote: On 02/07/2013 01:02 PM, Yves-Alexis Perez wrote: - I have no idea if it's syslinux or syslinux-themes-debian fault did you read the other bug? Actually yes, even without being bitten by the bug it'd be hard to miss. usually, opening a duplicate bug doesn't mean that the maintainer will re-tell the whole story again, and that pointing to the first bug about the same issue should be enough, so that the bug reporter would read it there when being pointed at it. - the bug is still present in 2:5.01+dfsg-1 / 12-1.1 that's why it's open and not closed yet. Yeah, I was merely pointing out that version tracking was definitely confusing here (because of the reassigns) If it needs manual tuning in some scripts to port it to the new syslinux, then fine, you seem to be the de factor maintainer of both packages so everything's under your control. look at the live-build commit and replicate it in /usr/share/syslinux/theme/$your_theme, Actually it's $your_theme, but eh. or wait until the theme in debian is fixed. I'm waiting. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#699596: syslinux-common: vesamenu.c32 is not a valid com32 image
On 02/07/2013 01:25 PM, Yves-Alexis Perez wrote: Actually it's $your_theme, but eh. i ment '$your_theme' as in 'the one you've chosen from the ones that are available in the package', but whatever. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693208: Bug#699899: tpu: clang/3.0-6.1+deb7u0
Le 02/07/13 13:15, Michael Stapelberg a écrit : Hi Adam, Adam D. Barratt a...@adam-barratt.org.uk writes: Looking at the proposed tpu diff and the 3.0 - 3.1 diff, it looks like the armhf changes should apply as is to 3.1; has anyone tried that? I have ported the patches from 3.0 to 3.1 and successfully built the package on amd64, where it works. Therefore, I will now build it on armhf, which will take around a day. Sylvestre: Are you okay with me NMUing clang 3.1-8.1 to unstable in order to expose my changes to a wider audience before we do the fix via t-p-u? Please go ahread. :) Thanks again, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700016: vim-runtime: mason syntax highlighting broken
Package: vim-runtime
Version: 2:7.3.429-2ubuntu2.1
Severity: normal
Hi, Mason syntax highlighting doesn't seem to be working properly anymore. Even
in the simple example below things don't look right. Thanks!
-- test.mason:
%init
if (1) {
;
}
/%init
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise'), (100, 'precise-backports')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-37-generic-pae (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
vim-runtime depends on no packages.
Versions of packages vim-runtime recommends:
ii vim 2:7.3.429-2ubuntu2.1
ii vim-tiny 2:7.3.429-2ubuntu2.1
vim-runtime 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#694031: mr: an option to make mr quiet for commands that produce no output
And a new version that does the right thing for output to non-terminals.
--
bye,
pabs
http://wiki.debian.org/PaulWise
From 11169c0f9c1a32b5f066f889a4561d62473ab77a Mon Sep 17 00:00:00 2001
From: Paul Wise p...@debian.org
Date: Sat, 2 Feb 2013 13:41:58 +0800
Subject: [PATCH] Make quiet mode show output if there is some. Closes: #694031
---
debian/changelog | 4
debian/control | 2 +-
mr | 64 +++-
3 files changed, 45 insertions(+), 25 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 1c93976..80e813a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
mr (1.14) UNRELEASED; urgency=low
+ [ Joey Hess ]
* Added a fetch command. Closes: #480580
* status: Now includes information about unpushed changes,
for git, git-svn, hg, and bzr. Closes: #693021
+ [ Paul Wise ]
+ * Make quiet mode show output if there is some. Closes: #694031
+
-- Joey Hess jo...@debian.org Sun, 11 Nov 2012 11:33:05 -0400
mr (1.13) unstable; urgency=low
diff --git a/debian/control b/debian/control
index 7189dc4..2700380 100644
--- a/debian/control
+++ b/debian/control
@@ -12,7 +12,7 @@ Architecture: all
Section: vcs
Depends: ${misc:Depends}
Suggests: subversion, git-core | git (= 1:1.7), cvs, bzr, mercurial, darcs, fossil, vcsh, liburi-perl, curl
-Recommends: libwww-perl, libhtml-parser-perl, perl
+Recommends: libwww-perl, libio-pty-easy-perl, libhtml-parser-perl, perl
Description: Multiple Repository management tool
The mr(1) command can checkout, update, or perform other actions on
a set of repositories as if they were one combined respository. It
diff --git a/mr b/mr
index 7cce39f..6de6ce2 100755
--- a/mr
+++ b/mr
@@ -240,9 +240,8 @@ Be verbose.
=item --quiet
-Be quiet. This suppresses mr's usual output, as well as any output from
-commands that are run (including stderr output). If a command fails,
-the output will be shown.
+Be quiet. This suppresses mr's usual output. If a command fails or there is any
+output then the usual output will be shown.
=item -k
@@ -692,6 +691,32 @@ sub fulldir {
return $subdir =~ /^\// ? $subdir : $topdir.$subdir;
}
+sub terminal_friendly_spawn {
+ my $actionmsg = shift;
+ my $sh = shift;
+ my $output = ;
+ if (-t STDOUT eval{use IO::Pty::Easy;1;} eq 1) {
+ my $pty = IO::Pty::Easy-new;
+ $pty-spawn($sh);
+ while ($pty-is_active) {
+ my $data = $pty-read(0);
+ $output .= $data if defined $data;
+ }
+ $pty-close;
+ } else {
+ $output = qx/$sh 21/;
+ }
+ my $ret = $?;
+ if ($ret != 0) {
+ print $actionmsg\n if $actionmsg;;
+ print STDERR $output;
+ } elsif ($output) {
+ print $actionmsg\n if $actionmsg;
+ print $output;
+ }
+ return ($ret, $output ? 1 : 0);
+}
+
sub action {
my ($action, $dir, $topdir, $subdir, $force_checkout) = @_;
my $fulldir=fulldir($topdir, $subdir);
@@ -790,17 +815,12 @@ sub action {
my $hookret=hook(pre_$action, $topdir, $subdir);
return $hookret if $hookret != OK;
- my $ret=runsh $action, $topdir, $subdir,
+ my ($ret, $out)=runsh $action, $topdir, $subdir,
$command, \@ARGV, sub {
my $sh=shift;
if ($quiet) {
- my $output = qx/$sh 21/;
- my $ret = $?;
- if ($ret != 0) {
- print $actionmsg\n;
- print STDERR $output;
- }
- return $ret;
+ return terminal_friendly_spawn($actionmsg, $sh);
+
}
else {
system($sh);
@@ -838,7 +858,7 @@ sub action {
return FAILED;
}
- my $ret=hook(post_$action, $topdir, $subdir);
+ my ($ret, $hook_out)=hook(post_$action, $topdir, $subdir);
return $ret if $ret != OK;
if ($is_checkout || $is_update) {
@@ -852,7 +872,7 @@ sub action {
return $ret if $ret != OK;
}
- return OK;
+ return (OK, $out || $hook_out);
}
}
}
@@ -862,15 +882,10 @@ sub hook {
my $command=$config{$topdir}{$subdir}{$hook};
return OK unless defined $command;
- my $ret=runsh $hook, $topdir, $subdir, $command, [], sub {
+ my ($ret,$out)=runsh $hook, $topdir, $subdir, $command, [], sub {
my $sh=shift;
if ($quiet) {
-my $output = qx/$sh 21/;
-my $ret = $?;
-if ($ret != 0) {
- print STDERR $output;
-}
-return $ret;
+return terminal_friendly_spawn(undef, $sh);
}
else {
system($sh);
@@ -890,7 +905,7 @@ sub hook {
}
}
- return OK;
+ return (OK, $out);
}
# run actions on multiple repos, in parallel
@@ -918,7 +933,7 @@ sub mrs {
close CHILD_STDERR;
close $outfh;
close $errfh;
-exit action($action, @$repo);
+exit +(action($action, @$repo))[0];
}
close CHILD_STDOUT;
close CHILD_STDERR;
@@ -966,10 +981,11 @@ sub mrs {
sub record {
my $dir=shift()-[0];
my $ret=shift;
+ my $out=shift;
if ($ret == OK) {
push @ok, $dir;
- print \n unless $quiet;
+ print \n unless $quiet !$out;
}
elsif ($ret == FAILED) {
if ($interactive) {
@@ -978,7 +994,7 @@ sub record {
system((getpwuid($))[8], -i);
Bug#699794: [Popcon-developers] Bug#699794: Bug#699794: popularity-contest: should work without a local SMTP/sendmail
2013/2/5 Petter Reinholdtsen p...@hungry.com: It should try to connect to popcon.debian.org. See SUBMITURLS in /usr/share/popularity-contest/default.conf for the default URLs, and /etc/cron.daily/popularity-contest for the program deciding how to submit the information. Looking at that script I see that I can disable email reporting by adding MAILTO= in /e/p-c.conf. I've re-enabled popcon on all Debian hosts. How can I monitor if popcon via HTTP fails from now on? Does it write anything to syslog? Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679214: grub-pc: Grub2 fails to boot from a degraded mdraid RAID6
Package: grub-pc
Version: 2.00-13
Followup-For: Bug #679214
This bug still exists in grub 2.00 on Debian.
The trigger cause seems to be 'extra' devices in mdraid arrays.
RAID1 2
RAID5 3
RAID6 4
Can anyone else reproduce this with a 6 disk array and / on LVM?
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sr0 /cdrom iso9660 ro,relatime 0 0
/dev/array/root / ext4 rw,relatime,user_xattr,barrier=1,stripe=256,data=ordered
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-VBOX_HARDDISK_VB9e4c9476-26d9eb65
(hd1) /dev/disk/by-id/ata-VBOX_HARDDISK_VB28ec1605-6c9ea282
(hd2) /dev/disk/by-id/ata-VBOX_HARDDISK_VB7a7f5ef7-5322a996
(hd3) /dev/disk/by-id/ata-VBOX_HARDDISK_VBfedcbcc6-834bf48c
(hd4) /dev/disk/by-id/ata-VBOX_HARDDISK_VB7c34e4d8-4fada505
(hd5) /dev/disk/by-id/ata-VBOX_HARDDISK_VB0c575cba-2bb136b3
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod raid5rec
insmod lvm
insmod ext2
set root='lvm/array-root'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvm/array-root'
b382c897-f9ce-4eea-b075-3546c5d4fe19
else
search --no-floppy --fs-uuid --set=root b382c897-f9ce-4eea-b075-3546c5d4fe19
fi
font=/usr/share/grub/unicode.pf2
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=C
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-b382c897-f9ce-4eea-b075-3546c5d4fe19' {
load_video
insmod gzio
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod raid5rec
insmod lvm
insmod ext2
set root='lvm/array-root'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvm/array-root'
b382c897-f9ce-4eea-b075-3546c5d4fe19
else
search --no-floppy --fs-uuid --set=root
b382c897-f9ce-4eea-b075-3546c5d4fe19
fi
echo'Loading Linux 3.2.0-4-amd64 ...'
linux /boot/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/array-root ro
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-4-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option
'gnulinux-advanced-b382c897-f9ce-4eea-b075-3546c5d4fe19' {
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian
--class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.2.0-4-amd64-advanced-b382c897-f9ce-4eea-b075-3546c5d4fe19' {
load_video
insmod gzio
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod raid5rec
insmod lvm
insmod ext2
set root='lvm/array-root'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvm/array-root' b382c897-f9ce-4eea-b075-3546c5d4fe19
else
search --no-floppy --fs-uuid --set=root
Bug#699808: tech-ctte: syslinux vs the wheezy release
Bdale Garbee wrote: Sure seems like d-i is something we should build using the components of the release it will be contained in and not unstable... but I haven't tried to think hard about what that might imply that's problematic. And I certainly don't think this is something we should even consider changing at this late date in for wheezy release cycle! This is not desirable outside the freeze because packages in unstable that are used to build d-i then don't get tested until they land in testing. It might be desirable during the freeze. wiggle the d-i build processing to fetch syslinux from testing This can be done easily, just upload d-i to t-p-u. d-i uploads are already built with udebs from testing, for similar reasons. There seems to be an unholy fear of using t-p-u for anything these days, which I don't really understand. Even when not using it causes massive and unnecessary logjams in unstable during the freeze. -- see shy jo signature.asc Description: Digital signature
Bug#699742: Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
Steve McIntyre wrote: On Thu, Feb 07, 2013 at 07:52:13AM +0100, Daniel Baumann wrote: consider such a misfeature to be in critical need of a fix (iirc steve puts a local copy of the 'to be used' syslinux version to be used by debian-cd for release images manually on the local fs; not sure about the same that ends up in the final release copy of debian-installer-images, will check later on)). Correcting - that used to be the case several years ago, but debian-cd now explicitly extracts files from the syslinux(-common) package in the main archive at CD build time, using the same suite as used in d-i for consistency. Howver, that is not the only image provided by Debian that uses syslinux. The d-i mini.iso is another one, which uses the syslinux provided by d-i's Build-Depedency, ie the one from unstable. -- see shy jo signature.asc Description: Digital signature
Bug#700017: python-pyo: 10 second lag before playing
Package: python-pyo Version: 0.6.1-1 Severity: normal Dear Maintainer, Running pyo in my system works fine but I have about a 10 second lag before anything happens. An example: #!/usr/bin/python2.7 from pyo import * s = Server().boot() s.start() #a = PinkNoise(.1).mix(2).out() b = BrownNoise(.4).mix(2) c = Sine([random.uniform(80,160) for i in range(50)], mul=.02).mix(2) #d = Mix(a, voices=2) sum=(.2*b+c) sum.out() s.gui(locals()) I get this in the console: /tmp/bn.py pyo version 0.6.1 (uses single precision) Failed to stat home directory /home/nicolas/pyo_rec.wav: No such file or directory PortMidi warning: Something wrong with midi device! Portmidi closed ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side Failed to stat home directory /home/nicolas/pyo_rec.wav: No such file or directory ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused Failed to stat home directory /home/nicolas/pyo_rec.wav: No such file or directory ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream Expression 'ioctl( devHandle, SNDCTL_DSP_CHANNELS, temp )' failed in 'src/hostapi/oss/pa_unix_oss.c', line: 405 Then, I see the small window with the controls and the two sounds play mixed correctly. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686-bigmem (SMP w/3 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-pyo depends on: ii libc6 2.13-37 ii liblo7 0.26~repack-7 ii libportaudio2 19+svn2021-1 ii libportmidi0 1:184-2.1 ii libsndfile11.0.25-5 ii python 2.7.3~rc2-1 ii python2.6 2.6.8-1.1 ii python2.7 2.7.3-6 Versions of packages python-pyo recommends: ii python-imaging-tk 1.1.7-4 ii python-tk 2.7.3-1 ii python-wxgtk2.82.8.12.1-12 python-pyo 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#694031: mr: an option to make mr quiet for commands that produce no output
Another one to use blocking reads so it doesn't use tons of CPU.
--
bye,
pabs
http://wiki.debian.org/PaulWise
From 397307eaed520909113225a89fe323917a7f1350 Mon Sep 17 00:00:00 2001
From: Paul Wise p...@debian.org
Date: Sat, 2 Feb 2013 13:41:58 +0800
Subject: [PATCH] Make quiet mode show output if there is some. Closes: #694031
---
debian/changelog | 4
debian/control | 2 +-
mr | 64 +++-
3 files changed, 45 insertions(+), 25 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 1c93976..80e813a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
mr (1.14) UNRELEASED; urgency=low
+ [ Joey Hess ]
* Added a fetch command. Closes: #480580
* status: Now includes information about unpushed changes,
for git, git-svn, hg, and bzr. Closes: #693021
+ [ Paul Wise ]
+ * Make quiet mode show output if there is some. Closes: #694031
+
-- Joey Hess jo...@debian.org Sun, 11 Nov 2012 11:33:05 -0400
mr (1.13) unstable; urgency=low
diff --git a/debian/control b/debian/control
index 7189dc4..2700380 100644
--- a/debian/control
+++ b/debian/control
@@ -12,7 +12,7 @@ Architecture: all
Section: vcs
Depends: ${misc:Depends}
Suggests: subversion, git-core | git (= 1:1.7), cvs, bzr, mercurial, darcs, fossil, vcsh, liburi-perl, curl
-Recommends: libwww-perl, libhtml-parser-perl, perl
+Recommends: libwww-perl, libio-pty-easy-perl, libhtml-parser-perl, perl
Description: Multiple Repository management tool
The mr(1) command can checkout, update, or perform other actions on
a set of repositories as if they were one combined respository. It
diff --git a/mr b/mr
index 7cce39f..e47834d 100755
--- a/mr
+++ b/mr
@@ -240,9 +240,8 @@ Be verbose.
=item --quiet
-Be quiet. This suppresses mr's usual output, as well as any output from
-commands that are run (including stderr output). If a command fails,
-the output will be shown.
+Be quiet. This suppresses mr's usual output. If a command fails or there is any
+output then the usual output will be shown.
=item -k
@@ -692,6 +691,32 @@ sub fulldir {
return $subdir =~ /^\// ? $subdir : $topdir.$subdir;
}
+sub terminal_friendly_spawn {
+ my $actionmsg = shift;
+ my $sh = shift;
+ my $output = ;
+ if (-t STDOUT eval{use IO::Pty::Easy;1;} eq 1) {
+ my $pty = IO::Pty::Easy-new;
+ $pty-spawn($sh);
+ while ($pty-is_active) {
+ my $data = $pty-read();
+ $output .= $data if defined $data;
+ }
+ $pty-close;
+ } else {
+ $output = qx/$sh 21/;
+ }
+ my $ret = $?;
+ if ($ret != 0) {
+ print $actionmsg\n if $actionmsg;;
+ print STDERR $output;
+ } elsif ($output) {
+ print $actionmsg\n if $actionmsg;
+ print $output;
+ }
+ return ($ret, $output ? 1 : 0);
+}
+
sub action {
my ($action, $dir, $topdir, $subdir, $force_checkout) = @_;
my $fulldir=fulldir($topdir, $subdir);
@@ -790,17 +815,12 @@ sub action {
my $hookret=hook(pre_$action, $topdir, $subdir);
return $hookret if $hookret != OK;
- my $ret=runsh $action, $topdir, $subdir,
+ my ($ret, $out)=runsh $action, $topdir, $subdir,
$command, \@ARGV, sub {
my $sh=shift;
if ($quiet) {
- my $output = qx/$sh 21/;
- my $ret = $?;
- if ($ret != 0) {
- print $actionmsg\n;
- print STDERR $output;
- }
- return $ret;
+ return terminal_friendly_spawn($actionmsg, $sh);
+
}
else {
system($sh);
@@ -838,7 +858,7 @@ sub action {
return FAILED;
}
- my $ret=hook(post_$action, $topdir, $subdir);
+ my ($ret, $hook_out)=hook(post_$action, $topdir, $subdir);
return $ret if $ret != OK;
if ($is_checkout || $is_update) {
@@ -852,7 +872,7 @@ sub action {
return $ret if $ret != OK;
}
- return OK;
+ return (OK, $out || $hook_out);
}
}
}
@@ -862,15 +882,10 @@ sub hook {
my $command=$config{$topdir}{$subdir}{$hook};
return OK unless defined $command;
- my $ret=runsh $hook, $topdir, $subdir, $command, [], sub {
+ my ($ret,$out)=runsh $hook, $topdir, $subdir, $command, [], sub {
my $sh=shift;
if ($quiet) {
-my $output = qx/$sh 21/;
-my $ret = $?;
-if ($ret != 0) {
- print STDERR $output;
-}
-return $ret;
+return terminal_friendly_spawn(undef, $sh);
}
else {
system($sh);
@@ -890,7 +905,7 @@ sub hook {
}
}
- return OK;
+ return (OK, $out);
}
# run actions on multiple repos, in parallel
@@ -918,7 +933,7 @@ sub mrs {
close CHILD_STDERR;
close $outfh;
close $errfh;
-exit action($action, @$repo);
+exit +(action($action, @$repo))[0];
}
close CHILD_STDOUT;
close CHILD_STDERR;
@@ -966,10 +981,11 @@ sub mrs {
sub record {
my $dir=shift()-[0];
my $ret=shift;
+ my $out=shift;
if ($ret == OK) {
push @ok, $dir;
- print \n unless $quiet;
+ print \n unless $quiet !$out;
}
elsif ($ret == FAILED) {
if ($interactive) {
@@ -978,7 +994,7 @@ sub record {
system((getpwuid($))[8], -i);
}
Bug#699808: tech-ctte: syslinux vs the wheezy release
Bdale Garbee wrote: patch d-i to build successfully against the syslinux in sid syslinux is GPL'd, so this would result in shipping d-i images in wheezy which contain a GPL'd binary for which there is no source in wheezy. -- see shy jo signature.asc Description: Digital signature
Bug#286356: [php-maint] Bug#576218: Bug#576218: Bug#576218: (no subject)
Just FYI: I am going to NMU this bug as soon we are unfrozen again. The fix has been available for two years now and the interactive mode is requested feature by many of our PHP users. Ondrej On Tue, Feb 21, 2012 at 8:31 PM, Lior Kaplan kap...@debian.org wrote: 2012/2/21 Ondřej Surý ond...@debian.org Can't we apply the same patches to the Debian packages? Are we waiting for the upstream maintainers to take action? We can, but you are barking up the wrong tree here. You need to speak with libedit maintainer. Anibal, could you take a look at #286356 ? Kaplan -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699808: tech-ctte: syslinux vs the wheezy release
Joey Hess jo...@debian.org (07/02/2013): This can be done easily, just upload d-i to t-p-u. d-i uploads are already built with udebs from testing, for similar reasons. There seems to be an unholy fear of using t-p-u for anything these days, which I don't really understand. Even when not using it causes massive and unnecessary logjams in unstable during the freeze. fdf81293a6165c5d51397bb855d29...@mail.adsl.funky-badger.org Mraw, KiBi. signature.asc Description: Digital signature
Bug#700018: ntpd 4.2.6.p5+dfsg-2 crashes when -I is used to specify the source interface in Debian testing
Package: ntp Version: 4.2.6.p5+dfsg-2 Problem: when -I eth1 (or your_interface_here (which is not part of the default route)) is specified -- ntpd crashed after about 10 minutes # cat /etc/default/ntp NTPD_OPTS='-g' #NTPD_OPTS='-g -I eth1' [334743.074156] ntpd[31953]: segfault at 737c ip 0040f3f4 sp 7fffee7ee990 error 4 in ntpd[40+7c000] No debugging symbols in this binary however.. [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `/usr/sbin/ntpd -p /var/run/ntpd.pid -g -I eth1 -u 110:117'. Program terminated with signal 11, Segmentation fault. #0 0x0040f3f4 in ?? () (gdb) bt #0 0x0040f3f4 in ?? () #1 0x00412bfe in ?? () #2 0x00405fa9 in ?? () #3 0x7fb54ce43ead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00405fd5 in ?? () #5 0x7fffee7ef738 in ?? () #6 0x001c in ?? () #7 0x0008 in ?? () #8 0x7fffee7efe52 in ?? () #9 0x7fffee7efe61 in ?? () #10 0x7fffee7efe64 in ?? () #11 0x7fffee7efe76 in ?? () #12 0x7fffee7efe79 in ?? () #13 0x7fffee7efe7c in ?? () #14 0x7fffee7efe81 in ?? () #15 0x7fffee7efe84 in ?? () #16 0x in ?? () (gdb)
Bug#700006: Fix for bug #699906: python-django-horizon: Launch from volume broken
On 02/07/2013 07:45 PM, Jonathan Wiltshire wrote: The diff looks fine in principle, let's see how it gets on in sid. Thanks, Uploaded. Release team bug retitled and usertaged accordingly. Thanks. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699742: Bug#699808: Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On 02/07/2013 02:14 PM, Joey Hess wrote: Howver, that is not the only image provided by Debian that uses syslinux. The d-i mini.iso is another one, which uses the syslinux provided by d-i's Build-Depedency, ie the one from unstable. that has already been discussed in earlier messages. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700019: src:mtdev: FTBFS on x32: breaks when getconf ARG_MAX returns undefined (-1)
Package: src:mtdev Version: 1.1.3-1~exp1 Severity: normal Hi! The mtdev package fails to build on x32. It turns out, getconf ARG_MAX returns undefined, which is not a valid integer, causing more and more obscure breakage as the build proceeds. Actually, things are a bit weird: when called from a command line, getconf ARG_MAX returns 2097152, yet from your ./configure, it's somehow -1, which the getconf tool returns as undefined. Code that fails to cope with this value is in aclocal.m4: lt_cv_sys_max_cmd_len=`(getconf ARG_MAX) 2 /dev/null` if test -n $lt_cv_sys_max_cmd_len; then lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \/ 4` lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \* 3` else After making it take that -1 literally (like on Hurd), build succeeds. Sadly, you use cdbs which sabotages autotoolage and fails to rebuild ./configure from source. I admit I didn't research how to work around this bug in cdbs (similar to --disable-maintainer-mode), I just edited ./configure manually in my tests, which worked. I did not bother even looking at unstable's version, as you clearly intend to upload 1.1.3 once wheezy releases, and x32 is not included in wheezy. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: x32 (x86_64) Kernel: Linux 3.7.1-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700020: chromium: About Chromium has old copyright date
Package: chromium Version: 24.0.1312.68-1 Severity: minor The About Chromium page (chrome://chrome/) has Copyright 2012 The Chromium Authors. All rights reserved. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694473: [php-maint] Bug#694473: Fix doesn't work for me
Hello Ondrej, Can you provide me an exact description what you need as backtrace. then I will send you the data I have. I I repeated the test under an actual Sid with php5 from experimental in the same virtual machine as I did the first test writing this bugreport. I get the same error message as before. Kind regards Mechtilde Am 07.02.2013 11:21, schrieb Ondřej Surý: Please provide a backtrace. And if you can please test with PHP from experimental. Thanks, Ondrej On Thu, Feb 7, 2013 at 11:11 AM, Mechtilde o...@mechtilde.de wrote: Hello on my testing system which also updated yesterday and today I get the same error again. So for me it isn't solved. Kind regards Mechtilde signature.asc Description: OpenPGP digital signature
Bug#699527: Solved, my bad
The order of the certificate chain that I configured in my web server was wrong: I put the CA root first, and then the intermediate cert. The SSL spec says that the SSL server should send its own cert first, next (in order) all higher-level certs up to the root CA. Reordering certs in the Apache SSLCertificateChainFile did the trick. Apparently GnuTLS adheres more strictly to the SSL spec than OpenSSL. What happened to 'Be conservative in what you send, liberal in what you accept' (Postel's law) and RFC1122? I'll close this bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700021: override: burgerspace:games/optional
Package: ftp.debian.org Severity: normal Dear ftp-masters, i have recently adopted the game burgerspace. The actual priority is too low. It neither conflicts with another package nor it has specialized requirements. (Policy 2.5) Please adjust the override from priority extra to optional. Thanks, Markus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700022: override:libflatzebra-dev:libdevel/optional, libflatzebra-0.1-2:libs/optional
Package: ftp.debian.org Severity: normal Dear ftp-masters, i have recently adopted the library package flatzebra. The actual priority is too low. It neither conflicts with another package nor it has specialized requirements. (Policy 2.5) Please adjust the override from priority extra to optional. Thanks, Markus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700023: override: openyahtzee:games/optional
Package: ftp.debian.org Severity: normal Dear ftp-masters, i have recently adopted the game openyahtzee. The actual priority is too low. It neither conflicts with another package nor it has specialized requirements. (Policy 2.5) Please adjust the override from priority extra to optional. Thanks, Markus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699808: tech-ctte: syslinux vs the wheezy release
Cyril Brulebois wrote: Joey Hess jo...@debian.org (07/02/2013): This can be done easily, just upload d-i to t-p-u. d-i uploads are already built with udebs from testing, for similar reasons. There seems to be an unholy fear of using t-p-u for anything these days, which I don't really understand. Even when not using it causes massive and unnecessary logjams in unstable during the freeze. fdf81293a6165c5d51397bb855d29...@mail.adsl.funky-badger.org Yes, that's a good example of spreading FUD aboput using t-p-u, rather than just using it and dealing with any breakage. -- see shy jo signature.asc Description: Digital signature
Bug#700013: libxcb1: libxcb crashes on systems with Mali graphics
close 700013 thanks I occasionaly get memory corruption error from libc when running this binary repeatedly so the crash is probably due to some error the might be unrelated to libxcb. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700015: libx11-6: crashes on systems using Mali graphics
Package: libx11-6 Version: 2:1.5.0-1 Followup-For: Bug #700015 Hello, it seems this problem is fixed by calling XInitThreads(). This is probably very platfrom specific problem, however. Drivers for this platform not available in Debian. Starting program: /usr/bin/gnome-shell [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1. Breakpoint 1, 0x9704 in main () (gdb) XInitThreads() Undefined command: XInitThreads. Try help. (gdb) call XInitThreads() $1 = 1 (gdb) c Continuing. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 3.4.24+ (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libx11-6 depends on: ii libc6 2.13-37 ii libx11-data2:1.5.0-1 ii libxcb11.8.1-2 ii multiarch-support 2.13-37 libx11-6 recommends no packages. libx11-6 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#286356: [php-maint] Bug#576218: Bug#576218: Bug#576218: (no subject)
Fair enough... maybe uploading to experimental in the meantime ? Kaplan On Thu, Feb 7, 2013 at 3:27 PM, Ondřej Surý ond...@debian.org wrote: Just FYI: I am going to NMU this bug as soon we are unfrozen again. The fix has been available for two years now and the interactive mode is requested feature by many of our PHP users. Ondrej On Tue, Feb 21, 2012 at 8:31 PM, Lior Kaplan kap...@debian.org wrote: 2012/2/21 Ondřej Surý ond...@debian.org Can't we apply the same patches to the Debian packages? Are we waiting for the upstream maintainers to take action? We can, but you are barking up the wrong tree here. You need to speak with libedit maintainer. Anibal, could you take a look at #286356 ? Kaplan -- Ondřej Surý ond...@sury.org
Bug#699794: [Popcon-developers] Bug#699794: Bug#699794: popularity-contest: should work without a local SMTP/sendmail
On Thu, Feb 07, 2013 at 02:54:08PM +0200, Teodor MICU wrote: 2013/2/5 Petter Reinholdtsen p...@hungry.com: It should try to connect to popcon.debian.org. See SUBMITURLS in /usr/share/popularity-contest/default.conf for the default URLs, and /etc/cron.daily/popularity-contest for the program deciding how to submit the information. Looking at that script I see that I can disable email reporting by adding MAILTO= in /e/p-c.conf. I've re-enabled popcon on all Debian hosts. How can I monitor if popcon via HTTP fails from now on? Does it write anything to syslog? Yes it does. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699808: tech-ctte: syslinux vs the wheezy release
On 07.02.2013 14:46, Joey Hess wrote: Cyril Brulebois wrote: Joey Hess jo...@debian.org (07/02/2013): This can be done easily, just upload d-i to t-p-u. d-i uploads are already built with udebs from testing, for similar reasons. There seems to be an unholy fear of using t-p-u for anything these days, which I don't really understand. Even when not using it causes massive and unnecessary logjams in unstable during the freeze. fdf81293a6165c5d51397bb855d29...@mail.adsl.funky-badger.org Yes, that's a good example of spreading FUD aboput using t-p-u, rather than just using it and dealing with any breakage. If you want to describe being concerned with dak refusing to import the result of a britney run due to the version constraints being broken FUD, sure. Note that I didn't say it was a reason not to use tpu, just a pre-condition in this case. 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#696192: RFS: matanza/0.13+ds1-3 [updated] -- Space ascii war game
Hi, Four weeks passed since our discussion. Any progress on this? Maybe it would be better to postpone additional changes for future uploads. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700024: librdf-storage-postgresql: PostgreSQL storage data retrieval doesn't work
Package: librdf-storage-postgresql Version: 1.0.15-1+b1 Severity: important Tags: upstream Hi. As already reported upstream (http://bugs.librdf.org/mantis/view.php?id=530), the postgresql storage seems broken in 1.0.15. This seems to be fixed in 1.0.16 though. It's too bad this is shipped in wheezy, but probably too late for a proper fix. Will probably deserve a point release or backports in between. Hope this helps. Best regards, P.S.: I've spent hours trying to make it work, so hopefully, this report will save others some time. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages librdf-storage-postgresql depends on: ii libc6 2.13-37 ii libdb5.1 5.1.29-5 ii libpq59.1.7-1 ii librdf0 1.0.15-1+b1 librdf-storage-postgresql recommends no packages. librdf-storage-postgresql 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#700025: munin/apache.conf: misleading and inconsistent comments for cgi html rendering
Package: munin Version: 2.0.1-1 Severity: whishlist The apache configuration shipped by munin claims a number of incompatible configurations. At some point /munin-cgi is used and at another point /cgi-bin/munin-cgi-html. Both variants are non-obviously intermixed. The /munin-cgi variant might work as long as one does not try to enable fcgid execution, cause the SetHandler for /munin-cgi apparently cannot be undone by a SetHandler None for /munin-cgi/static resulting in http status 403 for static files. The other variant of /cgi-bin/munin-cgi-html does not work for a lack of the static directory which needs to be mapped to a directory below due to the design of munin. In either case the fastcgi html rendering will not work. (Please tell me that I overlooked something.) It basically boils down to the problem that the cgi needs to be responsible for a base url and the static directory needs to reside immediately below that base url. This is notoriously hard to achieve with apache. TTBOMK the only working solution[1] involves mod_rewrite. This aspect is hard coded in at least the head.tmpl and HTMLConfig.pm files and needs upstream support for being sorted out in the long run. I therefore suggest to remove all mentioning of fastcgi html from the sample apache configuration and reducing the variants in the url space to just one. (Maybe the /munin-cgi one for it works with plain old cgi.) Please note that the suggested snippets for cgi graphing do work quite well. Helmut [1] http://munin-monitoring.org/wiki/CgiHowto2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699808: tech-ctte: syslinux vs the wheezy release
On Tue, Feb 05, 2013 at 01:48:22PM +0100, Julien Cristau wrote: the background for this request can be found in bug#699382. Here are the highlights: - the debian-installer source package, which builds the installer images for debian's releases, build-depends on syslinux - the release freeze for wheezy started in June 2012, and is now in its final stages - one of the prerequisites for the release is a release candidate for the installer - the syslinux maintainer uploaded new upstream versions of his package to unstable, which were unsuitable for wheezy, in November 2012, and again at the end of January 2013 - the latest of these uploads breaks the installer, making it impossible to build and upload the planned wheezy release candidate, since build-dependencies are fetched from unstable - when asked to revert this change, the syslinux maintainer refused, and said disagreements should be referred to the technical committee The submitters consider this disregard for the Debian release process not acceptable, and ask that the technical committee - overrule the syslinux maintainer, and decide that the syslinux package in unstable should be reverted to the version currently in wheezy (or a version compatible with the release team's freeze policy), until the wheezy release - rule that the syslinux package maintainer should be willing to collaborate with maintainers of its reverse-dependencies (and in particular the Debian Installer team) in a way that's compatible with Debian's release processes, and not against them. Even if the process is broken (and I can see arguments either way on that), now is not the time to rearrange it. If it was known in advance that d-i et al would break, at the very least patches for that should have been landed first. If it was not known, then what makes us think that the three problems identified to date (d-i, debian-cd, virtualbox) are a complete list? At the very least, it puts into question a considerable amount of the installer testing done to date. I would not wish to rule that the syslinux package maintainer should be willing to collaborate etc.; this is the type of assuming-bad-faith element of rulings that I think has not generally gone well when the TC has attempted it in the past, and it's at best questionable whether it's within our power anyway. But I do think that the syslinux maintainer should revert to 4.x in unstable; I'd rather that be voluntary but I'd be willing to vote to overrule if need be. As for the reasoning Daniel gave for putting 5.x in unstable in the first place, my recommendation would be to put 5.x in experimental and 6.x in some other archive; they are hardly difficult to set up and I'm quite sure Daniel's already familiar with what's involved there. The additional marketing gained by having 6.x in the Debian archive proper doesn't justify indirectly causing problems for wheezy, even if one disagrees with the process by which those problems are caused. On a personal note, this is exactly the kind of reason I deliberately kept GRUB 1.99 in unstable and 2.00 in experimental, even though it would have been more convenient and rather more pleasing to be able to ship wheezy with 2.00. There are certainly cases where new upstream versions in unstable during a freeze don't cause a practical problem and needn't involve any fuss - I've uploaded some such myself - but once it's clear they do cause a practical problem the proper course of action is surely to revert and let everyone get on with pre-existing problems. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690206: Fixing mixmaster on ARM
Hi!
According to http://www.arm.linux.org.uk/docs/faqs/signedchar.php,
char is unsigned on ARM, but signed on e.g. i386.
Hence, the loop
char c;
while (c = 0) {
/* foo */
c--;
}
wraps around (0-1 == 255) and produces undesired results. The assertion
then aborts the program, triggering the segfault.
The attached patch explicitly asks for a signed char, thus fixing the
problem.
HTH
From: Adrian Knoth a...@drcomp.erfurt.thur.de
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690206
Forwarded: no, but needed
Description: Fix segmentation fault on ARM.
--- a/Src/menustats.c
+++ b/Src/menustats.c
@@ -307,7 +307,7 @@ static int download_list() {
/* Displays the choice of stats sources */
#define MAXPING (26 * 2)
void update_stats() {
- char c;
+ signed char c;
BUFFER *inifile;
BUFFER *pingernames;
BUFFER *goodpingers;
Bug#315277: [bug #13593] The windows are drawed slowly on remote displays
Update of bug #13593 (project gnustep): Open/Closed:Open = Closed ___ Reply to this item at: http://savannah.gnu.org/bugs/?13593 ___ Message sent via/by Savannah http://savannah.gnu.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699776: RFS: pycdio/0.18-1 [ITP]
(I don't intend to sponsor this package, sorry.) * Benjamin Eltzner b.eltz...@gmx.de, 2013-02-04, 22:27: http://mentors.debian.net/debian/pool/main/p/pycdio/pycdio_0.18-1.dsc The package FTBFS when built in a minimal environment: |dh_python2 -O--buildsystem=python_distutils | E: dh_python2:145: extension for python2.6 is missing. Build extensions for all supported Python versions (`pyversions -vr`) or adjust X-Python-Version field or pass --no-guessing-versions to dh_python2 lintian4python emits: e: pycdio source: python-module-but-no-python-depends python-pycdio e: python-pycdio: missing-dependency-on-byte-compilation-helper pycompile = python (= 2.6.5) i: pycdio source: python-stdeb-boilerplate debian/rules:3 This file was automatically generated by stdeb 0.6.0+git e: python-pycdio: pyflakes-undefined-name usr/share/pyshared/cdio.py:844: d e: python-pycdio: pyflakes-undefined-name usr/share/pyshared/iso9660.py:197: pycdio e: python-pycdio: pyflakes-undefined-name usr/share/pyshared/iso9660.py:203: stat_array_to_href e: python-pycdio: pyflakes-undefined-name usr/share/pyshared/iso9660.py:431: stat_array_to_href Please ask upstream to include full license text in their tarballs. This is required by GPLv3 (§4). pycdio.py in the binary package has the following comment: # This file was automatically generated by SWIG (http://www.swig.org). # Version 1.3.40 This is not the version of SWIG that is in unstable, which means that the file hasn't been rebuilt from source. Please fix that. Upstream provides some tests. Tests love to be run at build time. :) -- 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#699934: bind9: on upgrading bind, it never tells me that a new /etc/default/bind9 is going to be installed
On Thu, Feb 07, 2013 at 01:50:22AM +0100, Christoph Anton Mitterer wrote: I have a modified /etc/default/bind9. Everytime bind packages are upgraded, I end up having a /etc/default/bind9.dpkg-dist, which by itself is fine, but dpkg never queries me with the usual dialog on whether I want to take the new file or not. Could it be that somehting is wrongly marked? The package actually goes to great effort to see what you may have done, and to only prompt you if there is something that needs to be added to the default file. One might argue that it shouldn't generate the dpkg-dist file in the general case. lamont -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700026: maybe should have a Build-Depends: syslinux
Package: debian-installer Version: 20121114 Severity: normal Hi, in [1] it was mentioned that d-i embeds syslinux on some architectures, but the current version does not include syslinux in its Build-Using field. It might be helpful to include it there to ensure we always keep the source for the embedded version around. Ansgar [1] http://bugs.debian.org/699808#253 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700027: kfreebsd-kernel-headers: Redefinition of struct termios
Package: kfreebsd-kernel-headers
Version: 0.82
Severity: serious
Control: affects -1 inetutils
Hi!
I just uploaded a new inetutils version (with a minimal change) which
FTBFS, but it built fine before. Just for reference, here's the build
log:
https://buildd.debian.org/status/fetch.php?pkg=inetutilsarch=kfreebsd-amd64ver=2%3A1.9-2stamp=1360207021
The problem is a redefinition of struct termios, that can be
reproduced with something like:
,--- termios.c
#include sys/tty.h
#include termios.h
int main() { return 0; }
`---
I'm filing this to track the issue, and because I have to do some
other stuff, if no one else has dealt with it by then I'll look into
fixing and uploading the package.
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#699805: pam_env: Unterminated expandable variable raises a critical error
tags 699805 upstream thanks On Tue, Feb 05, 2013 at 08:26:55PM +0900, Morita Sho wrote: When this function found an unterminated expandable variable, it returns PAM_ABORT, and it will raises a critical error. I think unterminated expandable variable is a small error, not so critical. I suggest to change the function to return BAD_LINE instead of PAM_ABORT. I don't know the reason for making this a critical error rather than BAD_LINE, but I do think that we shouldn't diverge from upstream on this. Can you please report this issue upstream? https://fedorahosted.org/linux-pam/newticket -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#699742: Bug#699808: tech-ctte: syslinux vs the wheezy release
On Thu, Feb 07, 2013 at 01:55:11AM +0100, Cyril Brulebois wrote: On a personal note, I'm unsure how we came up with a situation where a single maintainer can *actively* stall a release… Not caring about the release process put into place years ago is a thing. Stopping people from fixing problems created by such carelessness is another one… Speaking as an ex-RM, I think the answer here is that it used to be that when a maintainer made such an upload (and it did happen), we would revert it without hesitation and without apology. I'm having a hard time deciding, with my TC member hat on, if I think this is actually an ok thing to do. But whether or not it's ok, I do think I would still do it today if I were in your position on the grounds that it's easier to ask forgiveness than to ask permission, and asking explicit permission from every maintainer who is in a position to become a critical blocker for the release is a good way to make sure releases don't happen. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#699832: vlc lib directory is inferred from /proc/*/maps, with no (documented?) way to override
Rémi Denis-Courmont r...@remlab.net writes: Le mardi 5 février 2013 19:44:17, Ivan Shmakov a écrit : […] Obviously, there should be a way for the user to override the ‘lib’ directory location inferred from the ‘maps’ file contents. (Ideally, such a feature is to be activated automagically when VLC is used on a Debian Live system.) You can override/extend the paths that VLC searches for plugins using the VLC_PLUGIN_PATH environment variable. ACK, thanks! I've just checked it, and the issue goes away with an explicit VLC_PLUGIN_PATH=/usr/lib/vlc/plugins. Shouldn't such variables be prominently documented in either the vlc(1) (cvlc(1)) manual page, or in the --help text? Note that adding plugins while running is not supported (they will be ignored). If that's not enough, I don't really see any alternative to patching VLC in Debian. It's my understanding that using /usr/lib/vlc/plugins as the default plugins location is a sensible behavior for the Debian package. (I don't know if it makes sense to allow for such an “autodetection” to be activated explicitly by the user.) Union FS is a hack … Even if initially derived from Union FS, Aufs is a separate project for quite some years now. (And it's an exceptionally usefull hack, BTW.) and TBH, I have no plan to support this in upstream VLC especially not unless it gets accepted in the upstream Linux kernel. -- 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#699808: tech-ctte: syslinux vs the wheezy release
Colin Watson writes (Bug#699808: tech-ctte: syslinux vs the wheezy release): But I do think that the syslinux maintainer should revert to 4.x in unstable; I'd rather that be voluntary but I'd be willing to vote to overrule if need be. From what I've read so far I tend to agree. In Julien's referral mail: | - the debian-installer source package, which builds the installer | images for debian's releases, build-depends on syslinux For the avoidance of any doubt, I take this to mean that the version of the syslinux binary from unstable is actually copied into debian-installer's outputs. The observed problem is that the newer syslinux in sid has new bugs. Daniel seems to be proposing that we deal with these by patching the various other programs which don't work with the new syslinux. I think that approach is out of the question at this stage of the release. There is a wider problem which is that of course we want wheezy's installer to ship with the version of syslinux in the wheezy suite of the archive. I'm sympathetic to the argument that fetching sid's syslinux is not a sensible approach for d-i, at least during the freeze. From what I've read so far it would be good for this to be changed. But such a process fix should have been implemented and deployed _before_ the new syslog entered sid. How about this for a disposal: The Technical Committee notes that: 1. The syslinux maintainer has uploaded syslinux 5 to unstable. 2. The Release Managers intend to release wheezy with syslinux 4. 3. debian-installer even in wheezy and even now during the freeze uses syslinux binaries from unstable when building installers. Our view is that: 4. Updating to syslinux 5 at this stage of the release (whether in the installer, or generally) is out of the question. 5. It is arguable that arrangements should be made so that during the freeze debian-installer builds using testing's syslinux. Similar considerations may apply to shared libraries. 6. However now is not the time for these kind of process improvements. We therefore state no definite conclusion on this question. 7. The new syslinux should not have been uploaded to unstable, before the corresponding process improvements (if indeed they are improvements) are in place. Accordingly we decide as follows, overruling the syslinux maintainer: 9. The version of syslinux in wheezy should be re-uploaded to unstable. 9. No other updates should be made to syslinux in unstable, unless one of the following applies: (i) wheezy has been released and jessie opened and unfrozen; (ii) the Release Managers give their consent; or (iii) the debian-installer maintainers confirm that arrangements have been put in place to avoid this problem. 10. The syslinux maintainer should state ASAP what package version number they would like to be used for this re-upload. Any NMU of syslinux should honour such a statement, and in the absence of such a statement should not be made before 2013-02-10 17:00+. And we make the following (non-binding) statements of our opinion: 11. We request that everyone involved in this issue cordially discuss possible process improvements, preferably after the release of wheezy. 12. Whenever changes to Debian's software and processes are required, deployment should occur in a planned and cooperative way. Maintainers should be reluctant to upload changes which break other packages. If such breakage is necessary to move forward, it should only occur after obtaining rough consensus amongst the relevant contributors or the project as a whole. Ian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699277: linux-image-3.6-trunk-amd64: OOM killer running loose on system with lots of memory
Package: src:linux Version: 3.7.3-1~experimental.1 Followup-For: Bug #699277 Hello, with current kernel I triggered the issue with cp(1). Copying a file to exteernal USB disk killed Iceweasel. -- Package-specific info: ** Version: Linux version 3.7-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.7.3-1~experimental.1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.7-trunk-amd64 root=UUID=3b8f6a64-5899-462a-aec0-6ddefd878ecf ro fbcon=rotate:3 quiet ** Not tainted ** Kernel log: [773518.533786] init cpuset=/ mems_allowed=0 [773518.533790] Pid: 1, comm: init Not tainted 3.7-trunk-amd64 #1 Debian 3.7.3-1~experimental.1 [773518.533791] Call Trace: [773518.533802] [81373554] ? dump_header+0x70/0x1aa [773518.533807] [8103fbff] ? put_online_cpus+0x1f/0x66 [773518.533811] [810a0dd4] ? rcu_oom_notify+0xc6/0xd8 [773518.533815] [810c428b] ? oom_kill_process+0x72/0x2c5 [773518.533819] [810612eb] ? should_resched+0x5/0x23 [773518.533821] [810c49ca] ? out_of_memory+0x384/0x3d5 [773518.533825] [810c8873] ? __alloc_pages_nodemask+0x5c0/0x74c [773518.533829] [810f9e4e] ? kmem_getpages+0x54/0x124 [773518.533832] [810fa778] ? fallback_alloc+0x125/0x1ed [773518.533834] [810fb3a2] ? kmem_cache_alloc+0x7b/0xfd [773518.533838] [8111099d] ? getname_flags.part.23+0x22/0x10a [773518.533841] [81113523] ? user_path_at_empty+0x35/0xa8 [773518.533845] [81372269] ? __bad_area_nosemaphore+0x95/0x1ec [773518.533849] [8137b4f4] ? __do_page_fault+0x2fa/0x376 [773518.533851] [810612eb] ? should_resched+0x5/0x23 [773518.533854] [813778f2] ? _cond_resched+0x6/0x1b [773518.533857] [8110bc9c] ? cp_new_stat+0x11d/0x130 [773518.533861] [81042e59] ? timespec_add_safe+0x1e/0x4d [773518.533864] [8110ba31] ? vfs_fstatat+0x2d/0x63 [773518.533867] [81115973] ? poll_select_copy_remaining+0xea/0xff [773518.533869] [8110bd46] ? sys_newstat+0x12/0x2d [773518.533872] [81378918] ? page_fault+0x28/0x30 [773518.533875] [8137d6e9] ? system_call_fastpath+0x16/0x1b [773518.533877] Mem-Info: [773518.533879] Node 0 DMA per-cpu: [773518.533882] CPU0: hi:0, btch: 1 usd: 0 [773518.533883] CPU1: hi:0, btch: 1 usd: 0 [773518.533885] CPU2: hi:0, btch: 1 usd: 0 [773518.533887] CPU3: hi:0, btch: 1 usd: 0 [773518.533888] Node 0 DMA32 per-cpu: [773518.533890] CPU0: hi: 186, btch: 31 usd: 0 [773518.533891] CPU1: hi: 186, btch: 31 usd: 0 [773518.533893] CPU2: hi: 186, btch: 31 usd: 0 [773518.533895] CPU3: hi: 186, btch: 31 usd: 0 [773518.533896] Node 0 Normal per-cpu: [773518.533898] CPU0: hi: 186, btch: 31 usd: 0 [773518.533899] CPU1: hi: 186, btch: 31 usd: 0 [773518.533901] CPU2: hi: 186, btch: 31 usd: 0 [773518.533902] CPU3: hi: 186, btch: 31 usd: 0 [773518.533907] active_anon:439845 inactive_anon:131886 isolated_anon:0 active_file:611682 inactive_file:680137 isolated_file:0 unevictable:1641 dirty:680244 writeback:0 unstable:0 free:25754 slab_reclaimable:80416 slab_unreclaimable:7512 mapped:9807 shmem:11579 pagetables:4334 bounce:0 free_cma:0 [773518.533911] Node 0 DMA free:15904kB min:128kB low:160kB high:192kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15680kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes [773518.533917] lowmem_reserve[]: 0 2998 7921 7921 [773518.533920] Node 0 DMA32 free:45188kB min:25528kB low:31908kB high:38292kB active_anon:16040kB inactive_anon:127684kB active_file:1324868kB inactive_file:1352336kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3070172kB mlocked:0kB dirty:1352548kB writeback:0kB mapped:1360kB shmem:15220kB slab_reclaimable:165324kB slab_unreclaimable:1936kB kernel_stack:8kB pagetables:808kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:5267308 all_unreclaimable? yes [773518.533927] lowmem_reserve[]: 0 0 4923 4923 [773518.533929] Node 0 Normal free:41924kB min:41924kB low:52404kB high:62884kB active_anon:1743340kB inactive_anon:399860kB active_file:1121860kB inactive_file:1368212kB unevictable:6564kB isolated(anon):0kB isolated(file):0kB present:5041920kB mlocked:6564kB dirty:1368428kB writeback:0kB mapped:37868kB shmem:31096kB slab_reclaimable:156340kB slab_unreclaimable:28112kB kernel_stack:2376kB pagetables:16528kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:10328235 all_unreclaimable? yes [773518.533936] lowmem_reserve[]: 0 0 0 0 [773518.533938] Node 0 DMA: 0*4kB 0*8kB 0*16kB 1*32kB 2*64kB 1*128kB 1*256kB 0*512kB
Bug#700028: ITP: qtweetlib -- qtweetlib is a QT library for talking to twitter
Package: wnpp Severity: wishlist Owner: rm jonas.erlands...@gmail.com * Package name: qtweetlib Version : 1.0.0 Upstream Author : Jonas Erlandsson jonas.erlands...@gmail.com * URL : https://github.com/minimoog/QTweetLib.git * License : LGPL Programming Lang: C++, QT Description: qtweetlib - Supports only XAuth protocol (if there is need for PIN based OAuth I will include it) - OAuth tokens must be set in oauth.cpp line 27 and 28 to work properly - Uses QJson library by Flavio Castelli for parsing JSON responses - JSON parsing is done in multithreaded way using QThreadPool - User Streams support is not completed (fetches responses correctly, JSON parsing is not full implemented) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700029: fs2ram: Fs2ram 0.3.10 doesn't keep filecontent, please pull 0.3.12 to debian testing.
Package: fs2ram Version: 0.3.10 Severity: important Dear Maintainer, * What led up to the situation? fs2ram on debian stable and testing is unusable. Files are not kept after a reboot. * What exactly did you do (or not do) that was effective (or ineffective)? My config is attached. * What was the outcome of this action? No files in i.e. /var/log remains after a boot. * What outcome did you expect instead? To keep my logfiles. I have tested with 0.3.12 from unstable. Works just fine. I would like you to get that into testing. -- System Information: Debian Release: 7.0 Architecture: armhf (armv6l) Kernel: Linux 3.2.27+ (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Configuration Files: /etc/fs2ram/fs2ram.conf changed: none/var/lock - - tmpfs none/var/logkeep_file_content - tmpfs none/var/run- - tmpfs none/var/tmp- - tmpfs none/tmp- - tmpfs none/var/lib/puppet keep_file_content - tmpfs -- 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
