Bug#732201: Please add libnssdb.a and libnssckfw.a to libnss3-dev
On 13.01.2014 02:13, Mike Hommey wrote: > On Sun, Dec 15, 2013 at 05:37:38PM +0200, Timo Aaltonen wrote: >> Package: libnss3-dev >> Version: 2:3.15.3-1 >> Severity: wishlist >> >> Hi! >> >> I need these two files in the -dev package because libapache2-mod-rev >> build-depends on them. libapach2-mod-rev is a dependency of a Dogtag >> certificate server component. Dogtag 10.1.0 is now packaged with all the >> dependencies and I hope to get them in the archive by early January.. > > There is no libnssdb.a. There is libnssdbm.a, but there's no reason to > use it when there is libnssdbm3.so. Is libnssckfw.a enough? hah, looks like I've typoed it everywhere (other than debian/rules).. it's actually libnssb.a that I need in addition to libnssckfw.a. thanks for looking into this -- t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735142: debdelta timeouts on slow connection
Package: debdelta Version: 0.53 Severity: normal Dear Maintainer, with latest debdelta (0.53 in experimental) and other versions in testing/unstable (all have been tried). while using a very slow connection the debdelta-upgrade will repeatedly time out, meaning the run will not finish loading the debdeltas without being restarted. i consider it a minor bug as it is easily fixed by the user, and only some few people are on such slow connections any longer. this is a note for those who might experience similar timeouts. by adjusting the timeout value from 15 seconds to some larger value will help people with slow connections to get the debdeltas downloaded in fewer tries. there is only one use of the word timeout in /usr/bin/debdelta so that is easy to find and adjust. so far 600 seconds seems to work for me, but others may wish to use some other number. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debdelta depends on: ii binutils2.24-2 ii bzip2 1.0.6-5 ii libbz2-1.0 1.0.6-5 ii libc6 2.17-97 ii python 2.7.5-5 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages debdelta recommends: ii bsdiff 4.3-15 ii gnupg-agent 2.0.22-3 ii gnupg2 2.0.22-3 ii lzma 9.22-2 ii python-apt 0.9.1 ii xdelta 1.1.3-9 ii xdelta3 3.0.7-dfsg-2 ii xz-utils [lzma] 5.1.1alpha+20120614-2 Versions of packages debdelta suggests: ii debdelta-doc 0.50+2: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701989: libiptcdata: Added DEP-8 tests
Hello, Vibhav Pant [2013-03-01 16:31 +0530]: > I'm forwarding a diff that adds DEP-8 tests to the package, originally > submitted to Launchpad. These stopped working with latest sharutils due to the non-standard application of the -o option after the input file name. Attached updated debdiff. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) === modified file 'debian/changelog' --- debian/changelog2012-06-25 15:50:06 + +++ debian/changelog2013-03-01 10:26:22 + @@ -1,3 +1,10 @@ +libiptcdata (1.0.4-3ubuntu1) raring; urgency=low + + * Add simple autopkgtest to package. +- The JPEG used here for testing is a dummy 10x10 image created in GIMP. + + -- Vibhav Pant Tue, 26 Feb 2013 14:02:51 +0530 + libiptcdata (1.0.4-3) unstable; urgency=low * Incorporate patch for docbook manpage generation from Sebastian === added directory 'debian/tests' === added file 'debian/tests/build' --- debian/tests/build 1970-01-01 00:00:00 + +++ debian/tests/build 2013-03-01 10:26:22 + @@ -0,0 +1,35 @@ +#!/bin/sh +# autopkgtest check: Build and run a program against libiptcdata, to verify that +# the headers and pkg-config file are installed correctly +# (C) 2013 Vibhav Pant +# Author: Vibhav Pant + +set -e + +MYDIR=$(dirname $(readlink -f $0)) +WORKDIR=$(mktemp -d) +trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM +cd $WORKDIR +cat < libiptcdata_test.c +#include +#include +#include + +int main(void) +{ + unsigned char buf[256*256]; + FILE *file; + + file = fopen("$WORKDIR/sample.jpeg", "r"); + assert(iptc_jpeg_read_ps3(file, buf, sizeof(buf)) == 0); + assert(buf != NULL); + return 0; +} +EOF + +gcc -o libiptcdata_test libiptcdata_test.c -liptcdata -Wall -Werror +echo "build: OK" +uudecode -o $WORKDIR/sample.jpeg $MYDIR/sample.jpeg.base64 +[ -x libiptcdata_test ] +./libiptcdata_test +echo "run: OK" === added file 'debian/tests/control' --- debian/tests/control1970-01-01 00:00:00 + +++ debian/tests/control2013-03-01 10:26:22 + @@ -0,0 +1,2 @@ +Tests: build +Depends: libiptcdata0-dev, build-essential, sharutils === added file 'debian/tests/sample.jpeg.base64' --- debian/tests/sample.jpeg.base64 1970-01-01 00:00:00 + +++ debian/tests/sample.jpeg.base64 2013-03-01 10:26:22 + @@ -0,0 +1,15 @@ +begin-base64 664 sample.jpeg +/9j/4AAQSkZJRgABAQEASABIAAD//gATQ3JlYXRlZCB3aXRoIEdJTVD/2wBD +AAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsKCwsNDhIQDQ4RDgsL +EBYQERMUFRUVDA8XGBYUGBIUFRT/2wBDAQMEBAUEBQkFBQkUDQsNFBQUFBQU +FBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBT/ +wgARCAAKAAoDAREAAhEBAxEB/8QAFgABAQEAAgMI/8QA +FAEBAP/aAAwDAQACEAMQAAAByoUCE//EABcQAQEB +AQACEjH/2gAIAQEAAQUCbpXX/8QAFBEB +IP/aAAgBAwEBPwEf/8QAFBEBIP/aAAgB +AgEBPwEf/8QAFhAAAwAAABAx/9oACAEBAAY/Aiv/xAAa +EAACAgMAARARIWGR/9oACAEBAAE/IU6N3pg8f//aAAwD +AQACAAMQgk//xAAUEQEg/9oACAEDAQE/EB// +xAAUEQEg/9oACAECAQE/EB//xAAaEAEBAAID +AAABEQAQQWGh/9oACAEBAAE/EEVFHrAyerCBCF41/9k= +
Bug#650234: Use chroot's ld.so to do loading?
repen 650234 quit I guess I'm wondering whether I should be letting #650234 close and we need a separate bug for the current phase... The provided explanation of the status does not make sense. The explanation I can come up with is the wrapping is working, except around shell scripts. For shell scripts you would have the problem of arguments: /lib/ld-linux.so.2 shell.sh which won't work. I'm guessing you'll need to scan executables so the right one is invoked (the fakechroot()'s installed utility may be later than the system one). -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735141: [experimental] uninstallable with latest lintian, needs dependency bump
Package: lintian4python Version: 0.27 Severity: important Hello, current version has Build and binary depends on lintian (<< 2.5.21~), but 2.5.21 was uploaded to experimental, making lintian4python uninstallable. I verified that building lintian4python 0.27 against lintian 2.5.21 works fine (i. e. tests during package build succeed), and also its autopkgtest succeeds against current lintian, so the only thing needed is to bump the versions in debian/control. Thanks for considering, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#735138: autopkg test always failing
Hello, Matthias Klose [2014-01-13 3:02 +0100]: > This test is failing this is was introduced in 2012.10.24-6. However the log > doesn't tell what exactly is failing. > > - afaics the test is at least missing a dependency on aspcud > - sending all output to /dev/null is a bad idea for an untested >test script. Attached patch at least fixes those, and the wrong $indir directory (autopkgtests are run from the source tree root). Please don't do "2>/dev/null". If your test always writes expected stuff to stderr, then add "Restrictions: allow-stderr" to debian/tests/control. Otherwise, if the test is not supposed to write to stderr, don't redirect it (preferrable to detect unexpected regressions/warnings/etc.) But now further errors appear: | $ TMPDIR=/tmp/x sh -x debian/tests/upstream | + set -e | + indir=debian/tests/cudf | + outdir=/tmp/x | + basename debian/tests/cudf/feature.cudf | + cudf=feature.cudf | + outfile=/tmp/x/feature.sol | + checkfile=/tmp/x/feature.check | + aspcud debian/tests/cudf/feature.cudf /tmp/x/feature.sol trendy | *** ERROR: (clasp): Read Error: Line 0, Bad input stream! | | /usr/share/aspcud/encodings/misc2012.lp:46:45-46: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:74:2: error: lexer error, unexpected # | | /usr/share/aspcud/encodings/misc2012.lp:90:44-45: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:91:44-45: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:138:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:144:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:146:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:148:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:150:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:197:39-40: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:200:35-36: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:202:35-36: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:221:64-65: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:223:64-65: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:235:35-36: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:259:39-40: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:306:73-74: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:330:49-50: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:336:52-53: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:375:56-57: error: syntax error, unexpected :, expecting . or ; | | | Exception: too many messages. | + cudf-check -cudf debian/tests/cudf/feature.cudf -sol /tmp/x/feature.sol So the main problem seems to be the "bad input stream", but I have no idea about that. > so please set TMPDIR. autopkgtest does that, but for manually running the test it's indeed more convenient to just use something /tmp/aspcud-test if $TMPDIR is unset. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) --- aspcud-1.8.0/debian/tests/control 2014-01-11 09:27:53.0 +0100 +++ aspcud-1.8.0.new/debian/tests/control 2014-01-13 07:26:51.322461599 +0100 @@ -1,2 +1,2 @@ Tests: upstream -Depends: cudf-tools +Depends: @, cudf-tools --- aspcud-1.8.0/debian/tests/upstream 2014-01-11 09:27:53.0 +0100 +++ aspcud-1.8.0.new/debian/tests/upstream 2014-01-13 07:31:37.990461599 +0100 @@ -2,7 +2,7 @@ set -e -indir=cudf +indir=debian/tests/cudf outdir=$TMPDIR for infile in $indir/*.cudf @@ -10,8 +10,8 @@ cudf=$(basename $infile) outfile=$outdir/${cudf%.cudf}.sol checkfile=$outdir/${cudf%.cudf}.check -aspcud $infile $outfile trendy > /dev/null 2>&1 -cudf-check -cudf $infile -sol $outfile > $checkfile 2> /dev/null +aspcud $infile $outfile trendy +cudf-check -cudf $infile -sol $outfile > $checkfile if [ `grep -c "is_solution: true" $checkfile` -ne 1 ] then echo "Test \"legacy\" with options \"$solver\":" signature.asc Description: Digital signature
Bug#733300: [LCFC] templates://kinect-audio-setup/{templates}
On Mon, 13 Jan 2014 07:24:23 +0100 Christian PERRIER wrote: > Description: Microsoft Kinect audio sensor setup helpers > When the Kinect is first plugged in it shows up as a generic USB device > with a bulk endpoint; after the appropriate firmware is installed, a > re-enumeration takes place and a USB Audio Class device becomes available. > . > Since the firmware is not redistributable, kinect-audio-setup provides > tools to download it from the Internet at installation time, and sets up > udev rules to call the firmware loader when the device is plugged in to > finally get the USB Audio Class device (UAC). wonders why say (UAC) at the 2nd occurrence instead of the 1st -- victory no need to CC me :-) http://userscripts.org/scripts/show/102724 0.0.1.4 http://userscripts.org/scripts/show/163846 0.0.1 http://userscripts.org/scripts/show/163848 0.0.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703585: wrong fix?
Correct me if I'm wrong, but the suggested fix in comment 15 looks wrong to me: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703585#15 PyOpenGL already has a loader for numpy, this only slots numpy where "python-numeric" used to go, effectively loading it twice under two names. It avoids the warning, but I don't think that's right. The more fundamental problem is twofold: * it tries to import libraries which are highly unlikely to be found on the system (with "python-numeric" being replaced by "numpy" everywhere) * when it fails to load, it spits out those huge stacktraces that scare users, simply saying "accelerator module XYZ not installed" would be just as correct and far less likely to cause so many false problems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733300: [LCFC] templates://kinect-audio-setup/{templates}
This is the last call for comments for the review of debconf templates for kinect-audio-setup. The reviewed templates will be sent on Wednesday, January 15, 2014 to this bug report and a mail will be sent to this list with "[BTS]" as a subject tag. -- Template: kinect-audio-setup/accept_eula Type: boolean Default: false #flag:translate!:3 _Description: Do you accept the Microsoft Kinect for Windows EULA? In order to fetch the binary firmware needed by the kinect-audio-setup package, you need to agree to the End User License Agreement (EULA) of the Microsoft Kinect for Windows Software Development Kit: . http://www.microsoft.com/en-us/kinectforwindows/develop/sdk-eula.aspx Template: kinect-audio-setup/eula_not_accepted Type: error _Description: EULA not accepted You need to accept the End User License Agreement (EULA) of the Microsoft Kinect for Windows Software Development Kit in order to fetch the binary firmware needed by the kinect-audio-setup package. . You can do this later with "dpkg-reconfigure kinect-audio-setup". Source: kinect-audio-setup Maintainer: Antonio Ospite Section: contrib/sound XS-Autobuild: no Priority: extra Build-Depends: debhelper (>= 9), po-debconf, libusb-1.0-0-dev, pkg-config Standards-Version: 3.9.5 Vcs-Browser: http://git.ao2.it/kinect-audio-setup.git/ Vcs-Git: git://git.ao2.it/kinect-audio-setup.git -b debian Homepage: http://git.ao2.it/kinect-audio-setup.git/ Package: kinect-audio-setup Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, udev, wget, p7zip-full (>= 9.20) Description: Microsoft Kinect audio sensor setup helpers When the Kinect is first plugged in it shows up as a generic USB device with a bulk endpoint; after the appropriate firmware is installed, a re-enumeration takes place and a USB Audio Class device becomes available. . Since the firmware is not redistributable, kinect-audio-setup provides tools to download it from the Internet at installation time, and sets up udev rules to call the firmware loader when the device is plugged in to finally get the USB Audio Class device (UAC). . The UAC firmware is downloaded from the Microsoft Kinect Software Development Kit at http://www.kinectforwindows.org, the license of which can be found at http://www.kinectforwindows.org/download/EULA.htm signature.asc Description: Digital signature
Bug#702762: "More or less" dead upstream
Am Sonntag, den 12.01.2014, 15:14 -0500 schrieb Reinhard Tartler: > Oh I see. The dependencies are overly strict in stable. That may be true, but on the other hand we do not get any bug reports where dmo packaged caused breakage from stable. I am inclined to add back the strict dependencies in the last upload before the freeze. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735140: mirror submission for debian.asis.io
Package: mirrors Severity: wishlist Submission-Type: new Site: debian.asis.io Aliases: ftp.asis.io Type: leaf Archive-architecture: amd64 i386 Archive-ftp: /debian/ Archive-http: /debian/ Archive-rsync: debian/ IPv6: no Archive-upstream: ftp.de.debian.org Updates: four Maintainer: factoreal Country: IR Iran, Islamic Republic of Location: Tehran, Iran Sponsor: ASIS Security Group http://asis.io -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735139: linux-image-3.2.0-4-amd64: nbd crashes after resuming from suspend to ram
Control: tag -1 moreinfo On Mon, 2014-01-13 at 00:34 -0300, Ernesto wrote: > Package: src:linux > Version: 3.2.51-1 > Severity: important > > Hi, > > the problem is when I resume from suspend to ram (perhaps from disk > also) having a disk image mounted through nbd. I lose access to the > mounted image, and can't umount nor remove the module nbd. > > I have to reboot the system in order to gain access to the disk image > again. This is very annoying since I use it a lot. > > I hope you can sort this out. Any additional info, please ask. Does this work in Linux 3.12 (available from testing or wheezy-backports)? Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Bug#733007: sonata gtk client doesnt start, thats grave
control: severity -1 grave control: tags -1 + sid jessie Hi, justification: "grave - makes the package in question unusable or mostly so" - according to the package description, sonata is a gtk+ client for mpd, so the user expectation is, well to have a mpd client in gtk with a ui, which exactly is 100% broken by this bug. The patch in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728704#5 indeed fixes the problem. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#735139: linux-image-3.2.0-4-amd64: nbd crashes after resuming from suspend to ram
Package: src:linux Version: 3.2.51-1 Severity: important Hi, the problem is when I resume from suspend to ram (perhaps from disk also) having a disk image mounted through nbd. I lose access to the mounted image, and can't umount nor remove the module nbd. I have to reboot the system in order to gain access to the disk image again. This is very annoying since I use it a lot. I hope you can sort this out. Any additional info, please ask. Regards. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=e2ae9235-faee-430f-9a8f-823c77838a40 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [14853.304014] Extended CMOS year: 2000 [14853.304272] ACPI: Low-level resume complete [14853.304313] PM: Restoring platform NVS memory [14853.304922] CPU0: Thermal monitoring handled by SMI [14853.304977] Extended CMOS year: 2000 [14853.305012] Enabling non-boot CPUs ... [14853.305140] Booting Node 0 Processor 1 APIC 0x1 [14853.305142] smpboot cpu 1: start_ip = 98000 [14853.316156] Calibrating delay loop (skipped) already calibrated this CPU [14853.316169] Disabled fast string operations [14853.316183] CPU1: Thermal monitoring handled by SMI [14853.336536] NMI watchdog enabled, takes one hw-pmu counter. [14853.336817] CPU1 is up [14853.336945] Booting Node 0 Processor 2 APIC 0x2 [14853.336946] smpboot cpu 2: start_ip = 98000 [14853.347959] Calibrating delay loop (skipped) already calibrated this CPU [14853.347972] Disabled fast string operations [14853.347984] CPU2: Thermal monitoring handled by SMI [14853.368450] NMI watchdog enabled, takes one hw-pmu counter. [14853.368745] CPU2 is up [14853.368863] Booting Node 0 Processor 3 APIC 0x3 [14853.368864] smpboot cpu 3: start_ip = 98000 [14853.379876] Calibrating delay loop (skipped) already calibrated this CPU [14853.379888] Disabled fast string operations [14853.379900] CPU3: Thermal monitoring handled by SMI [14853.400461] NMI watchdog enabled, takes one hw-pmu counter. [14853.400801] CPU3 is up [14853.404167] ACPI: Waking up from system sleep state S3 [14853.444528] ehci_hcd :00:1a.0: wake-up capability disabled by ACPI [14853.444811] ehci_hcd :00:1d.0: wake-up capability disabled by ACPI [14853.445513] xhci_hcd :03:00.0: wake-up capability disabled by ACPI [14853.445643] PM: early resume of devices complete after 1.242 msecs [14853.445732] i915 :00:02.0: setting latency timer to 64 [14853.445737] ehci_hcd :00:1a.0: setting latency timer to 64 [14853.445741] snd_hda_intel :00:1b.0: setting latency timer to 64 [14853.445771] ehci_hcd :00:1d.0: setting latency timer to 64 [14853.445796] ahci :00:1f.2: setting latency timer to 64 [14853.445799] snd_hda_intel :00:1b.0: irq 48 for MSI/MSI-X [14853.445951] iwlwifi :02:00.0: RF_KILL bit toggled to enable radio. [14853.445967] xhci_hcd :03:00.0: setting latency timer to 64 [14853.445992] atl1c :04:00.0: wake-up capability disabled by ACPI [14853.446213] sd 0:0:0:0: [sda] Starting disk [14853.485305] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [14853.560228] Extended CMOS year: 2000 [14853.884058] /dev/vmmon[18734]: HostIFReadUptimeWork: detected settimeofday: fixed uptimeBase old 18445354511377719534 new 18445354505372483309 attempts 1 [14853.884063] usb 2-1.2: reset low-speed USB device number 3 using ehci_hcd [14853.887863] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [14853.893420] ata2.00: configured for UDMA/133 [14854.235820] usb 2-1.5: reset full-speed USB device number 4 using ehci_hcd [14854.330676] btusb 2-1.5:1.0: no reset_resume for driver btusb? [14854.330684] btusb 2-1.5:1.1: no reset_resume for driver btusb? [14855.853977] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [14855.854946] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded [14855.856833] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded [14855.857631] ata1.00: configured for UDMA/100 [14855.892585] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [14855.899610] iwlwifi :02:00.0: Radio type=0x2-0x2-0x1 [14855.984693] PM: resume of devices complete after 2541.523 msecs [14855.984974] PM: Finishing wakeup. [14855.984976] Restarting tasks ... done. [14856.008082] video LNXVIDEO:00: Restoring backlight state [14856.061821] usb 1-1.5: new high-speed USB device number 6 using ehci_hcd [14856.410105] usb 1-1.5: New USB device found, idVendor=0bda, idProduct=0138 [14856.410109] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [14856.410111] usb 1-1.5: Product: USB2.0-CRW [14856.410113] usb 1-1.5: Manufacturer: Generic [14856.410115] usb 1-1.5: SerialNumber: 2009051638820 [14856.436170] scsi9 : usb-storage 1-1.5:1.0 [14856.436557] usb 1-1.5: USB disconnect, device number 6 [14858.997756] ADDRCONF(NETDEV_UP): wlan0: link is
Bug#735138: autopkg test always failing
Package: aspcud Version: 1:1.8.0-1 Severity: serious This test is failing this is was introduced in 2012.10.24-6. However the log doesn't tell what exactly is failing. - afaics the test is at least missing a dependency on aspcud - sending all output to /dev/null is a bad idea for an untested test script. $ sh -x upstream 2>&1 | tee log + set -e + indir=cudf + outdir= + basename cudf/feature.cudf + cudf=feature.cudf + outfile=/feature.sol + checkfile=/feature.check + aspcud cudf/feature.cudf /feature.sol trendy so please set TMPDIR. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720902: CVE-2013-4152 XML External Entity (XXE) injection in Spring
Hi, Is there any news with this vulnerability fix? 3.0.6.RELEASE-6+deb7u1 was uploaded to security-master a week ago or so. Cheers, Miguel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735137: gnucash: Enter/double-click no longer opens account with subaccounts in 2.6.0
Package: gnucash Version: 1:2.6.0-1 Severity: normal Dear Maintainer, With the latest update of gnucash in Jessie (from 2.4.2 to 2.6.0), typing Enter or double-clicking in the account list on an account that has subaccounts no longer opens the account, but merely collapses or expands the list of subaccounts. In order to actually open the account, one must instead go via the menu (Edit->Open account), which quickly gets annoying for commonly used accounts. Perhaps I'm mistaken, but I'm imagining this was merely changed by mistake somehow, and if so, it would be nice to have the old behavior back. Perhaps this bug should be considered minor, but I do find it quite disturbing. I trust you'll change it at your own discretion. :) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 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 gnucash depends on: ii gnucash-common 1:2.6.0-1 ii guile-2.0 2.0.9+1-1 ii guile-2.0-libs 2.0.9+1-1 ii libaqbanking34 5.1.0beta-1 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libcrypt-ssleay-perl 0.58-1+b1 ii libdate-manip-perl 6.42-1 ii libdbi10.8.4-6 ii libfinance-quote-perl 1.18-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-0 2.36.4-1 ii libgnome-keyring0 3.4.1-1 ii libgnomecanvas2-0 2.30.3-2 ii libgoffice-0.8-8 0.8.17-3 ii libgtk2.0-02.24.22-1 ii libgwengui-gtk2-0 4.8.0beta-1 ii libgwenhywfar604.8.0beta-1 ii libhtml-tableextract-perl 2.11-1 ii libhtml-tree-perl 5.03-1 ii libktoblzcheck1c2a 1.43-1 ii libofx41:0.9.4-2.1 ii libpango-1.0-0 1.36.0-1+b1 ii libpangocairo-1.0-01.36.0-1+b1 ii libpython2.7 2.7.6-4 ii libwebkitgtk-1.0-0 2.2.3-1 ii libwww-perl6.05-2 ii libx11-6 2:1.6.2-1 ii libxml22.9.1+dfsg1-3 ii libxslt1.1 1.1.28-2 ii perl 5.18.1-5 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages gnucash recommends: ii gnucash-docs 2.6.0-1 ii yelp 3.10.1-1 Versions of packages gnucash suggests: pn libdbd-mysql pn libdbd-pgsql pn libdbd-sqlite3 -- 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#724010: 10-day delayed NMU uploaded
debdiff attached. -- Eric Dorland ICQ: #61138586, Jabber: ho...@jabber.com diff -u t-code-2.3.1/debian/changelog t-code-2.3.1/debian/changelog --- t-code-2.3.1/debian/changelog +++ t-code-2.3.1/debian/changelog @@ -1,3 +1,13 @@ +t-code (2:2.3.1-3.2) unstable; urgency=low + + * Non-maintainer upload. + + [ Eric Dorland ] + * debian/control: Drop unnecessary build-deps on autoconf and +automake1.4. (Closes: #724010) + + -- Eric Dorland Sun, 12 Jan 2014 19:31:28 -0500 + t-code (2:2.3.1-3.1) unstable; urgency=low * Non-maintainer upload. diff -u t-code-2.3.1/debian/control t-code-2.3.1/debian/control --- t-code-2.3.1/debian/control +++ t-code-2.3.1/debian/control @@ -4,7 +4,7 @@ Maintainer: NOSHIRO Shigeo Standards-Version: 3.8.0 Build-Depends: debhelper (>= 5) -Build-Depends-Indep: automake1.4, autoconf, emacs | emacs22 | emacs21 | xemacs21-mule | xemacs21-mule-canna-wnn +Build-Depends-Indep: emacs | emacs22 | emacs21 | xemacs21-mule | xemacs21-mule-canna-wnn Homepage: http://openlab.jp/tcode/ Package: t-code signature.asc Description: Digital signature
Bug#735136: asterisk-core-sounds: Ship ulaw/alaw files too
Package: asterisk-core-sounds Version: 1.4.22-1 Severity: wishlist Hello, Would it be possible to ship ulaw/alaw sound files as well? (probably in a separate package) Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel ça gaze ? prout -+- #ens-mim - ouvrez les fenêtres ! -+- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734465: anki: Crashes on start-up with NameError
retitle 734465 anki: Error report lost due to missing import traceback thanks On Tue, Jan 07, 2014 at 01:42:41PM +0100, Albin Stjerna wrote: > When starting Anki, the program crashes with the following output on the > console: > > Traceback (most recent call last): > File "/usr/bin/anki", line 8, in > aqt.run() > File "/usr/share/anki/aqt/__init__.py", line 247, in run > mw = aqt.main.AnkiQt(app, pm, args) > File "/usr/share/anki/aqt/main.py", line 55, in __init__ > showInfo(_("Error during startup:\n%s") % traceback.format_exc()) > NameError: global name 'traceback' is not defined Unfortunately this isn't the actual error, this just complains that the traceback module was not imported. The actual error message that triggered this is lost. I will upload a fixed package shortly (version 2.0.20+dfsg-2) which will close this bug report. Please try it and file a new bug report with the actual error which you should then be able to see. Sorry for the inconvenience. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724002: 10-day delayed NMU uploaded
Diff attached. -- Eric Dorland ICQ: #61138586, Jabber: ho...@jabber.com diff -u centerim-4.22.10/debian/changelog centerim-4.22.10/debian/changelog --- centerim-4.22.10/debian/changelog +++ centerim-4.22.10/debian/changelog @@ -1,3 +1,13 @@ +centerim (4.22.10-2.1) unstable; urgency=low + + * Non-maintainer upload. + + [ Eric Dorland ] + * debian/control, debian/rules: Drop automake1.4 build-dep and +unnecessary autoconf call. (Closes: #724002) + + -- Eric Dorland Sun, 12 Jan 2014 18:40:34 -0500 + centerim (4.22.10-2) unstable; urgency=low * Fix FTBFS with binutils-gold, closes: #624944, #554066. diff -u centerim-4.22.10/debian/rules centerim-4.22.10/debian/rules --- centerim-4.22.10/debian/rules +++ centerim-4.22.10/debian/rules @@ -32,7 +32,6 @@ putf8=$(package)-utf8 config.status: configure - autoconf -v dh_testdir cp centerim.1 centerim-fribidi.1 cp centerim.1 centerim-utf8.1 diff -u centerim-4.22.10/debian/control centerim-4.22.10/debian/control --- centerim-4.22.10/debian/control +++ centerim-4.22.10/debian/control @@ -6,7 +6,7 @@ Build-Depends: debhelper (>= 4.0), libncurses5-dev, gettext (>= 0.10), libfribidi-dev (>= 0.10.4-4), autotools-dev, libgnutls-dev, perl, libncursesw5-dev, libcurl4-gnutls-dev, - libgpgme11-dev (>= 1.0.1), automake1.4, liblzo2-dev, libtool + libgpgme11-dev (>= 1.0.1), liblzo2-dev, libtool Build-Conflicts: libglib1.2-dev, libcurl4-openssl-dev, libcurl3-openssl-dev Homepage: http://www.centerim.org/ Standards-Version: 3.8.1 signature.asc Description: Digital signature
Bug#734788: collectd: Too many dependencies
> Recommends / Suggests only includes dependencies of actual plugins. C'mon, it's about 200 Mbytes of unneeded libraries, like tokyotyrant or varnish, or libvirt etc, not counting full jdk installation and others, which most users won't need. I'm trying to use collectd in virtual environment with puppet system rollout which means that each virtual machines downloads 200 Mbytes on start. If you build it manually, at least you have an option to not to include unneeded plugins. This package forces user to install them. Check other big packages like php or python. They are broken into many pieces so I can install only needed ones. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735135: RM: libgtextutils [ia64 powerpc sparc] -- ROM; FTBFS on ia64, powerpc and sparc.
Package: ftp.debian.org Severity: normal Dear FTP team, the libgtextutils package fails to build on ia64, powerpc and sparc, which do not use GCC 4.8. Please remove libgtextutils and its dependancy fastx-toolkit, in order to ensure proper migration to testing. Have a nice day, -- Charles Plessy Debian Med packaging team Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734901: [Pkg-sysvinit-devel] Bug#734901: initscripts: More Proper Detection of "fastboot" Kernel Parameter necessary
severity 734901 grave found 734901 sysvinit/2.88dsf-13 notfound 734901 sysvinit/2.88dsf-45 thanks On Fri, 10 Jan 2014, Sebastian.Steinhuber wrote: > during boot, Debian forces checking of hard disks/partitions, what is IMHO an > important thing to do. Since fsck during boot is not performed due to the > "i915.fastboot=1" kernel parameter, it seems adequate to set a higher > importance > to the issue, feel free to change that, but not running fsck might cause > serious > data loss. Indeed. Severity grave it is, for now. Note that this is a VERY old bug, which was exposed by new kernel conventions (well, not so new... the use of . has been around for a while, but i915.fastboot, which triggers the bug, is quite recent). I will set the BTS bug information to an arbitrarily old version of initscripts that also covers oldstable (the bug was already in place in 2009). All other uses of "grep -w" to check the kernel command line are likewise buggy, and could use some pro-active fixing. Another collision is just a matter of time... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732201: Please add libnssdb.a and libnssckfw.a to libnss3-dev
On Sun, Dec 15, 2013 at 05:37:38PM +0200, Timo Aaltonen wrote: > Package: libnss3-dev > Version: 2:3.15.3-1 > Severity: wishlist > > Hi! > > I need these two files in the -dev package because libapache2-mod-rev > build-depends on them. libapach2-mod-rev is a dependency of a Dogtag > certificate server component. Dogtag 10.1.0 is now packaged with all the > dependencies and I hope to get them in the archive by early January.. There is no libnssdb.a. There is libnssdbm.a, but there's no reason to use it when there is libnssdbm3.so. Is libnssckfw.a enough? Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735043: [Pkg-owncloud-maintainers] Bug#735043: libqtkeychain0: Please update to version 0.2.0 which includes gnome keyring support
My apologies - I saw the version bump in the git changelog, and assumed that meant it was released. As an FYI, I checked out the latest version from github and compiled it, and it works just fine with the gnome keyring. On Sun, Jan 12, 2014 at 10:38:40PM +0100, Sandro Knauß wrote: > Hello, > > > Please upgrade to version 0.2.0, which includes gnome keyring support. > Either I'm blind or version 0.2.0 isn't released. According to upstream it > isn't taged: > https://github.com/frankosterfeld/qtkeychain/releases > > where did you see the release of 0.2.0? > > I only found the request for the new version at the bug report, that is not > closed: > https://github.com/frankosterfeld/qtkeychain/issues/21 > > If it is released I'll package it and will ship it. > > Regards, > > sandro -- Scott Barker Linux Consultant sc...@mostlylinux.ca http://www.mostlylinux.ca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718474: news.daily needs mawk
On Aug 01, Russ Allbery wrote: > Which of the awk implementations do you have configured as /usr/bin/awk? Any news? I can confirm that gawk works too, what are you using? -- ciao, Marco signature.asc Description: Digital signature
Bug#735134: perl: rename(1) is ancient
Package: perl Version: 5.18.1-5 Severity: normal Hi all, the rename(1) which ships with perl is located in debian/rename in the source package and stuck at a version from 1998: # $RCSfile: rename,v $$Revision: 1.5 $$Date: 1998/12/18 16:16:31 $ CPAN[1] carries a version 1.8 from 2010, but the two do not seem to share history[2]. There is at least one competing version 0.20[3], which also does not share history[4]. The former version seems to offer more features than the latter. -- Richard [1] http://search.cpan.org/~pederst/rename/ [2] http://cpansearch.perl.org/src/PEDERST/rename-1.8/Changes [3] https://metacpan.org/pod/release/RMBARKER/File-Rename-0.20/ [4] https://metacpan.org/source/RMBARKER/File-Rename-0.20/Changes -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 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 perl depends on: ii libbz2-1.01.0.6-5 ii libc6 2.17-96 ii libdb5.1 5.1.29-7 ii libgdbm3 1.8.3-12 ii perl-base 5.18.1-5 ii perl-modules 5.18.1-5 ii zlib1g1:1.2.8.dfsg-1 Versions of packages perl recommends: ii netbase 5.1 Versions of packages perl suggests: ii libterm-readline-gnu-perl 1.20-2+b2 ii make 3.81-8.3 ii perl-doc 5.18.1-4 -- 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#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)
Hello Francesco et al, On Sun, Jan 12, 2014 at 10:13:43PM +0100, Francesco Poli wrote: […] > On Sun, 12 Jan 2014 20:52:40 +0100 Ricardo Mones wrote: > > > Package: apt-listbugs > > Version: 0.1.12 > > Severity: grave > > Justification: renders package unusable > > > > Hi, > > Hello Ricardo, > thanks for reporting the issue, which is, however, already known. > > Apologies for not setting an appropriate "affects apt-listbugs" for the > previously reassigned bug reports. > I am doing so now, so that these reports will show up in > http://bugs.debian.org/apt-listbugs Thanks, no problem :) > > Since last update apt-listbugs doesn't allow to apt-get to install packages, > > it always ends like this: > > > > /usr/lib/ruby/vendor_ruby/debian.rb:24:in `require': no such file to load > > -- debian_version (LoadError) > > from /usr/lib/ruby/vendor_ruby/debian.rb:24 > > from /usr/sbin/apt-listbugs:289:in `require' > > from /usr/sbin/apt-listbugs:289 > > E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) > > E: Failure running script /usr/sbin/apt-listbugs apt > > > [...] > > Thanks in advance for any suggestion, > > > [...] > > ii ruby1.8 [ruby-interpreter] 1.8.7.358-9 > > You are still using ruby1.8 as system-wide default Ruby interpreter. > You should switch to ruby1.9.1 as default interpreter. Well, I have what it's pulled by apt-listbugs dependencies, which IMO should be able to pull the version of the interpreter necessary to run it, even if that includes switching default ruby. > The following steps should hopefully fix the issue for you: […] > At this point you should be again able to upgrade or install packages > while using apt-listbugs. > Please let me know, if something went wrong. Workaround worked fine, many thanks for the quick response. best regards, -- Ricardo Mones ~ The world will end in 5 minutes. Please log out.Unknown signature.asc Description: Digital signature
Bug#360554: hi good day
Good day am Henriette,i do pray that this email meets you well,Though we haven't met or seen each other before but i believe that nature has a way of Bringing people together for a Particular Purpose.if you need a female friend Contact me back .henriette -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726578: Ping: pwgen: Multiple vulnerabilities in passwords generation
On Sun, Jan 12, 2014 at 09:27:14PM +0100, Arne Wichmann wrote: > > This grave problem is now open for more than two months. Is there any plan > to resolve this? First, the CVE about having the unavailability of /dev/random fail hard -- sure, that should be a separate bug since that's a fix that I think is reasonable at this point. We can now guarantee that /dev/random exists everywhere. (And by that same token, if an attacker can cause /dev/random not to be present, they probably have root, so you're probably toast anyway. So I don't think it's going to really improve things to remove the drand() fallback, but I don't have strong feelings about that.) Secondly, I'll note that one of the CVE's were rejected as not a vulnerability. (In general it would have been better to have opened seperate bugs for each CVE.) Finally, whether you think the other two CVE's justify this to be serious, let alone "grave" bug really depends on what you think the goals of pwgen are. To quote from the manual page: The pwgen program generates passwords which are designed to be easily memorized by humans, while being as secure as possible. Human-memo‐ rable passwords are never going to be as secure as completely com‐ pletely random passwords. In particular, passwords generated by pwgen without the -s option should not be used in places where the password could be attacked via an off-line brute-force attack.On the other hand, completely randomly generated passwords have a tendency to be written down, and are subject to being compromised in that fashion. So we could change the defaults to be "pwgen -csy 20", in which case you would get passwords like tihs: L}U@lc_~i^>n|ro!4uI- 1`;yXlYVMW%?E9)3A&7G **}6BoBu=!~3)y?3v]Or >=>:PC;H?E7*+6$c&-QH URGgjUNG[\dSw\>p7F-] _AXZ~(HYd8Q#%b>!]'u: ~)0=>:PC;H?E7*+6$c&-QH"), but its not clear that real users would be any less likely to write "ylO3IE9B" on a sticky note which is pasted to their monitor, or just in a "passwords" file in their home directory. So ultimately, a lot of this is about an argument over defaults, and I think the higher level problem is that no matter what password policy you use, passwords are doomed as a technology. Anything which is secure against a brute force attack is impossible for a user to use, unless they share passwords across multiple sites so they only have to remember one password such as "ylO3IE9B" --- at which point they get toast once some web site screws up in some way and gets penetrated by bad guys. - Ted -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735133: p11-kit: Do not use __libc_enable_secure
Package: p11-kit Version: 0.20.1-3 Severity: important Hello, On kfreebsd-any, libp11-kit0 depends on libc0.1 (>> 2.17) and on libc0.1 (<< 2.18), i.e. libc0.1 can not be upgraded to 2.18, and libp11-kit0 can not be upgraded to a version rebuilt against 2.18 unless upgrading libc0.1 to 2.18 too. This is due to p11-kit using the __libc_enable_secure internal libc symbol: since this is an internal symbol, its presence is not supposed to be guaranteed in newer eglibc uploads, and thus the libc symbols file adds such kind of dependencies. The same happens on hurd-any with libc0.3. It doesn't happen on linux-any because p11-kit's configure uses getauxval there. p11-kit should thus not use __libc_enable_secure to avoid such tight dependencies. This can be done with the attached patch for instance, by making kfreebsd-any and hurd-any use getauxval too. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages p11-kit depends on: ii libc62.17-97 ii libffi6 3.0.13-4 ii libp11-kit0 0.20.1-3 ii libtasn1-6 3.4-2 p11-kit recommends no packages. p11-kit suggests no packages. -- no debconf information -- Samuel j'etais en train de nettoyer ma souris et le coup est parti... -+- s sur #ens-mim - et en plus c vrai... -+- --- configure.ac.orig 2014-01-12 23:04:04.0 + +++ configure.ac2014-01-12 23:05:01.0 + @@ -51,11 +51,11 @@ os_win32=yes os_unix=no ;; - *-*-linux*) + *-*-linux*|*-*-k*bsd*-gnu|*-*-gnu*) AC_DEFINE_UNQUOTED(OS_UNIX, 1, [Building for unix]) os_win32=no os_unix=yes - os_linux=yes + os_gnu=yes ;; *) AC_DEFINE_UNQUOTED(OS_UNIX, 1, [Building for unix]) @@ -83,10 +83,10 @@ # These are thngs we can work around AC_CHECK_FUNCS([getprogname getexecname basename mkstemp mkdtemp]) - if test "$os_linux" = "yes"; then + if test "$os_gnu" = "yes"; then AC_CHECK_FUNCS([getauxval issetugid getresuid]) else - # Do not use getauxval on non-linux, e.g BSD. + # Do not use getauxval on non-GNU, e.g pure BSD. AC_CHECK_FUNCS([issetugid getresuid]) fi AC_CHECK_FUNCS([strnstr memdup strndup strerror_r])
Bug#735132: RFS: burp/1.3.46-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "burp" * Package name: burp Version : 1.3.46-1 Upstream Author : Graham Keeling mailto:keel...@spamcop.net>> * URL : http://burp.grke.net/ * License : Graham Keeling mailto:keel...@spamcop.net>> Section : utils It builds those binary packages: burp - Simple cross-platform network BackUp and Restore Program burp-dbg - debugging symbols for Burp To access further information about this package, please visit the following URL: http://mentors.debian.net/package/burp Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/burp/burp_1.3.46-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New upstream stable candidate - Fixed bedup: crashes with exit status 139 (Closes: #715678) - Fixed init.d: script stop action takes a very long time (Closes: #687523) - Fixed burp: Warnings during build of packages (Closes: #675368) - Fixed burp(8) spelling error: 'overriddden' (Closes: #685568) - Fixed burp(8) error in client_can_list section (Closes: #694506) - Fixed Bug bedup crashes with exit status 139 (Closes: #715678) - Fixed burp: "Unable to set datapath" backup resume bug fixed by stable release 1.3.10 (Closes: #695641) - Removed unneeded patches from debian/patch becouse they are include in new upstream version * Added dependency on initscripts (>= 2.88dsf-13.3) to comply with 3.9.5 standards * New Standards-Version 3.9.5 * Reformatted change-log * Changed copyright in /debian/* from GPL-2 to AGPL-3 * Added Vcs-Browser to control file * Bumped dephelper to 9 * Bumped compat to 9 * Fix "Lintian reports hardening-no-relro" Fixed with bump to debhelper 9 (Closes: #735128) * Contribution from Robert Ladyman - Spell-checked and grammar-checked debian change-log * Add patches from upstrean disables test when no randomness available (Closes: #675761) * Updated debian/copyright (Closes: #735129) * Changes in burp-1.3.46: - Another bug fix for false failure notification - differentiate between not getting a lock and getting an error when trying to get a lock. - Turn off excessive logging on some restores. * Changes in burp-1.3.44: - Bug fix for false failure notification when a client tries to connect again while a backup is still in progress. * Changes in burp-1.3.42: - In backup phase 4, a 'deleteme' directory may already exist if the server was previously interrupted whilst deleting it. If so, delete it before attempting to rename anything to it. * Changes in burp-1.3.40: - Make the server request the whole file when ctime changes on Windows, otherwise changes to metadata when the file content is unchanged will not be noticed. - Add 'delete' to the client help output. - When backing up, open files and directories with O_NOATIME flag so that the access time is not changed. - Bug fix for no failure notification being sent when the backup directory cannot be created. * Changes in burp-1.3.38: - Fix long list and status monitor output when a directory argument is given. - Fix restore problem with backups containing both compressed and uncompressed files. - Bug fix for an interrupted backup causing a resume when a restore_client connects. - Bug fix for defaulting 'resume partial' to off. * Changes in burp-1.3.36: - Fix truncation of timestamps in the live status-monitor. - Default the 'resume partial' feature to being off, and add an option to turn it on. * Changes in burp-1.3.34: - Contributions from Avi Rozen: + Major autoconf cleanup. + Initial support for cross-building android targets. - On the server, indicate where logging is occurring. - Fix bedup segfault when using -m with no argument. * Changes in burp-1.3.32: - Fix status-monitor segfault. - Run timed backups with lower thread priority on Windows. - Add 'vss_drives' option, which gives the ability to specify which Windows drives get a VSS snapshot. * Changes in burp-1.3.30: - Add a warning when run on Windows without admin privileges. - Perform fewer lstat()s on systems that support d_type (ie most Linux systems), in order to speed up certain operations. - Allow _FORTIFY_SOURCE to work. - Fix problem with burp_ca.bat and repeated field-names in burp.conf. - Put registry keys back in the Windows installer. - Fix for SIGHUP reload causing the server to go into non-forking mode. - Indicate the backups that are deletable. - Add a client option for deleting deletable backups. -
Bug#707432: libexplain: FTBFS: libexplain/buffer/v4l2_buf_flags.c:43:34: error: 'V4L2_BUF_FLAG_INPUT' undeclared (first use in this function)
Package: libexplain30 Version: 0.52.D002-1 Followup-For: Bug #707432 Please use the attached patch that fixes this bug. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libexplain30 depends on: ii libc62.17-97 ii libcap2 1:2.22-1.2 ii lsof 4.86+dfsg-1 libexplain30 recommends no packages. libexplain30 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#735131: python-numexpr-dbg: Fails to install with python3-numexpr
Package: python-numexpr-dbg Version: 2.2.2-3 Severity: normal The following occurs trying to build pytables: Preparing to unpack .../python3-numexpr-dbg_2.2.2-3_hppa.deb ... Unpacking python3-numexpr-dbg (2.2.2-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-numexpr-dbg_2.2.2-3_hppa.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/numexpr/interpreter.cpython-33dm-hppa-linux-gnu.so', which is also in package python3-numexpr 2.2.2-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Debian Release: jessie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'experimental'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 3.13.0-rc7+ (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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#735112: contacts: mis-escapes X-EVOLUTION-FILE-AS
Control: forwarded -1 https://github.com/owncloud/contacts/pull/355 Control: found -1 6.0.0.a+dfsg-1 On Sun, Jan 12, 2014 at 07:23:58PM +, Simon McVittie wrote: > Patch attached (just a monkey-patch for the installed files rather than > a proper packaging patch, I'm afraid). Thanks Simon, I just “translated” your proposal into a pull request that will hopefully make it in the upcoming 6.0.1 (and intend to patch our upcoming package accordingly if it isn’t applied upstream in time). Regards David signature.asc Description: Digital signature
Bug#734829: pu: package mapserver/6.0.1-3.2+deb7u2
Control: tags -1 + pending On Sat, 2014-01-11 at 22:03 +0100, Salvatore Bonaccorso wrote: > On Sat, Jan 11, 2014 at 03:01:56PM +, Adam D. Barratt wrote: > > On Fri, 2014-01-10 at 04:51 +0100, Bas Couwenberg wrote: > > > The MapServer project has released stable updates for every major > > > release from 5.6.x up fixing a security issue which allows a potential > > > leakage of information through an SQL injection when using TIME filtering > > > in > > > conjunction with PostGIS backends. More information can be found in the > > > dedicated upstream issue: #4834 > > > > Please go ahead; thanks. > > I have uploaded Bas' package. Flagged for acceptance; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734830: opu: package mapserver/5.6.5-2+squeeze3
Control: tags -1 + pending On Sat, 2014-01-11 at 22:04 +0100, Salvatore Bonaccorso wrote: > On Sat, Jan 11, 2014 at 02:59:26PM +, Adam D. Barratt wrote: > > On Fri, 2014-01-10 at 05:07 +0100, Bas Couwenberg wrote: > > > The MapServer project has released stable updates for every major > > > release from 5.6.x up fixing a security issue which allows a potential > > > leakage of information through an SQL injection when using TIME > > > filtering in conjunction with PostGIS backends. More information can be > > > found in the > > > dedicated upstream issue: #4834 > > > > Please go ahead; thanks. > > Also uploaded Bas' package for opu. Also flagged for acceptance. :) Thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734331: RFH: mg -- microscopic GNU Emacs-style editor
Peter De Wachter wrote: > Hi Trent, > I'd like to help with mg. I'm not a DD, so I won't be able to sponsor, > but I can help with anything else. Thanks. I'm usually in #debian-mentors on irc.oftc.net from ca. 10AM to 6PM Australia/Melbourne time. The mg stuff probably still says it's maintained in darcs, but the repo (inc. history) was migrated to git, at git.debian.org:/git/collab-maint/mg.git It's a repo of just debian/, which appears to be an unusual workflow among the git people. I'm open to changing that if you feel strongly. As I said in the RFH, the next step should be to get clens into a finished state, then get it sponsored. I've rsynced what I've currently got to ~twb-guest/Desktop/mg/ on git.debian.org; you should have read access. signature.asc Description: Digital signature
Bug#645876: Nimbus Sans L condensed only in libreoffice 3.4
I don't know why but attachment was not sent. Retrying, plus file content here to be sure. $ cat 81-nimbus.conf NimbusSanL-ReguCond Nimbus Sans L Condensed Regular NimbusSanL-BoldCond Nimbus Sans L Condensed Bold NimbusSanL-ReguCondItal Nimbus Sans L Condensed Regular Italic NimbusSanL-BoldCondItal Nimbus Sans L Condensed Bold Italic 81-nimbus.conf Description: Binary data
Bug#729540: closed by Bernd Zeimetz (Bug#729540: fixed in open-vm-tools 2:9.4.0-1280544-1)
Oh, I can finally get rid of 4.7 then! Awesome, thank you. It's good to see open-vm-tools adopted again. Mihai On 01/13/2014 12:15 AM, Bernd Zeimetz wrote: hi, please use open-vm-tools 2:9.4.0-1280544-5 - not -1. Building with 3.11 should work fine with -1, but 3.12 (and gcc 4.8) needs -5. Mihai: -5 builds just fine with gcc 4.8 :) Cheers, Bernd On 01/07/2014 07:33 AM, Jim Barber wrote: Hi Bernd. I have tried this new version of open-vm-tools-dkms against the 3.12 kernel that is now in Debian testing and it failed to compile for me. The contents of the /var/lib/dkms/open-vm-tools/9.4.0/build/make.log file follows: DKMS make.log for open-vm-tools-9.4.0 for kernel 3.12-1-amd64 (x86_64) Tuesday 7 January 14:12:27 WST 2014 Using 2.6.x kernel build system. make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' make -C /lib/modules/3.12-1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules make[1]: Entering directory `/usr/src/linux-headers-3.12-1-amd64' CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/block.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c: In function ‘ExecuteBlockOp’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c:286:9: warning: assignment from incompatible pointer type [enabled by default] name = getname(buf); ^ CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default] .d_revalidate = DentryOpRevalidate, ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c: In function ‘DentryOpRevalidate’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default] return actualDentry->d_op->d_revalidate(actualDentry, nd); ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’ CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/file.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/filesystem.o CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default] .lookup = InodeOpLookup, ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function ‘InodeOpLookup’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:138:32: error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’ inode->i_uid = inode->i_gid = 0; ^ /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function ‘InodeOpFollowlink’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:224:4: error: implicit declaration of function ‘vfs_follow_link’ [-Werror=implicit-function-declaration] ret = vfs_follow_link(nd, iinfo->name); ^ cc1: some warnings being treated as errors make[4]: *** [/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o] Error 1 make[3]: *** [_module_/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.12-1-amd64' make: *** [vmblock.ko] Error 2 make: Leaving directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' Using 2.6.x kernel build system. Building vmhgfs without VMCI module symbols. make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs' make -C /lib/modules/3.12-1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules make[1]: Entering directory `/usr/src/linux-headers-3.12-1-amd64' CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.o In file included from /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.h:44:0, from /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.c:49: /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/./shared/backdoor_types.h: In function ‘BACKDOOR_STRUCT_SIZES’: /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/./shared/vm_assert.h:366:20: warning: typedef ‘AssertOnCompileFailed’ locally defined but not used [-Wunused-local-typedefs] typedef char AssertOnCompileFailed[AssertOnCom
Bug#735130: RFS: libapr-memcache/0.7.0-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libapr-memcache" * Package name: libapr-memcache Version : 0.7.0-2 Upstream Author : Paul Querna * URL : http://www.outoforder.cc/projects/libs/apr_memcache/ * License : [fill in] Section : libs It builds those binary packages: libapr-memcache-dev - memcache client library development files libapr-memcache0 - memcache client library To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libapr-memcache Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/liba/libapr-memcache/libapr-memcache_0.7.0-2.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Watch file was not working, checking wrong source file * Updated copyright file - Changed FSF address to URL - Updated copyright dates * debian.control: - Changed Standards-Version to 3.9.5 - Added debian VCS urls in control file - Changed dependency of debhelper to <= 9 * debian/compat: Changed Debhelper compatibility level to 9 * debian/rules: - Minimized rules file - Removed unneeded cp actions * debian/*.install - Removed libapr-memcache.install becouse it was not needed - Changed /usr/lib/ to usr/lib/*/ - Removed libapr_memcache.la from libapr-memcache-dev.install (Closes: #735083) * Removed libapr_memcache.la from libapr-memcache-dev package * Fix "Lintian reports hardening-no-relro" harding is done by new version of debhelper. So is fix on next rebuild automatically (Closes: #735127) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734329: denyhosts: regression in regex.py
On Sun, Jan 12, 2014 at 07:34:54PM +0100, Helmut Grohne wrote: > Control: tags -1 + patch > > Hi Vincent, > > On Mon, Jan 06, 2014 at 06:32:13AM +0100, Helmut Grohne wrote: > > A real fix seems more involved. Suggestions welcome. > > Personally I cannot reproduce this issue on any of my machines, but I > believe that I understand the cause. > > Can you test one of the attached patches? I presume that you can build > the packages yourself, if not, please contact me. > > Note that due to the very likely removal of denyhosts from sid, my patch > does not solve the regression for jessie or sid. It only works with > older openssh versions from squeeze or wheezy. The patches are also > available as branches from the collab-maint/denyhosts git repository. I've tried the patch and it works correctly. Thanks for your work on denyhosts, Vince -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735023: please relax Dependency on gdm3
On 12/01/2014 19:17, Michael Biebl wrote: > Am 12.01.2014 00:16, schrieb Robert Millan: Have you tried locking your screen? >> No. And I just rechecked, but I couldn't find any button to do that. Please >> can you provide more details on what I should try? >> >> Mind that I'm completely unfamiliar with the new GNOME UI. > > CTRL+ALT+L or > Right-upper corner -> Lock CTRL+ALT+L has no effect, and the menu in right-upper corner doesn't include a Lock command. I assume this functionality requires GDM? I think this is a graceful way of handling the "GDM is not present" case. Note that users who want screen locking can still achieve it by other means, e.g. xscreensaver-command -lock (or xlockmore, whatever happened to it??). -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734531: dh_installemacsen: can create incorrect "hybrid" packages.
Rob Browning writes: > Oh, and if there's not already, it would be handy to have some way to > opt-out of dh_installemacsen processing entirely since emacsen-common > will appear to be a likely candidate, but is in fact a special case. And finally, I just uploaded 2.0.6, which has two new requirements for add-on packages (see debian-emacs-policy 5B): --- a/debian-emacs-policy +++ b/debian-emacs-policy @@ -176,6 +176,8 @@ First, for the purposes of this policy, some terminology: fi postinst: + mkdir -p 0755 /var/lib/emacsen-common/state/package/installed + touch /var/lib/emacsen-common/state/package/installed/ if test -e /var/lib/emacsen-common/state/package/installed/emacsen-common then /usr/lib/emacsen-common/emacs-package-install --postinst @@ -186,6 +188,7 @@ First, for the purposes of this policy, some terminology: then /usr/lib/emacsen-common/emacs-package-remove --prerm fi + rm -f /var/lib/emacsen-common/state/package/installed/ The postinst call must not be made until the package is completely configured and otherwise ready for use, and the prerm This should fix a problem caused when add-on packages were being installed at the same time as emacsen-common. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645876: Nimbus Sans L condensed only in libreoffice 3.4
tags 645876 patch thanks > I am experiencing a bug that was closed long time ago: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243329 > > Nimbus Sans L offers only condensed variants. However, it happens for me > only in libreoffice (and seems like only in version 3.4). Workaround mentioned > in that old report - removing the font files of the nimbus sans condensed > fonts - "fixes" the problem. But it would be good to understand whats > wrong. Is there some more information I can provide to "debug" the problem ? I had the opposite problem: I cannot find the condensed variants in libreoffice 4.1.4.2 (Sid). It seems this is a widespread bug: https://bugs.freedesktop.org/show_bug.cgi?id=50855 I found a simple workaround for this (see attachment): using fontconfig, I made a new font family I called "Nimbus Sans L Condensed" to include the condensed variants and separate them from the normal "Nimbus Sans L" family. Place the attached file in a directory read by fontconfig (like /etc/fonts/conf.d/ for example), then rebuild font cache (with 'fc-cache -f'). I don't know why but libreoffice still won't display the changes, maybe it uses an internal font cache? I resolved the easy way by removing the ~/.config/libreoffice/ directory, but probably there's a better way to do this. The 'gsfonts' package maintainer could ponder the validity of this workaround and maybe including it in the package (or it's a fontconfig concern?). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707432: libexplain: FTBFS: libexplain/buffer/v4l2_buf_flags.c:43:34: error: 'V4L2_BUF_FLAG_INPUT' undeclared (first use in this function)
Package: libexplain30 Version: 0.52.D002-1 Followup-For: Bug #707432 Please use the attached patch to fix the FTBFS issue. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libexplain30 depends on: ii libc62.17-97 ii libcap2 1:2.22-1.2 ii lsof 4.86+dfsg-1 libexplain30 recommends no packages. libexplain30 suggests no packages. -- no debconf information Index: libexplain-0.52.D002/libexplain/buffer/v4l2_buf_flags.c === --- libexplain-0.52.D002.orig/libexplain/buffer/v4l2_buf_flags.c 2014-01-13 01:58:06.441171322 +0400 +++ libexplain-0.52.D002/libexplain/buffer/v4l2_buf_flags.c 2014-01-13 01:58:15.621422103 +0400 @@ -40,7 +40,9 @@ { "V4L2_BUF_FLAG_ERROR", V4L2_BUF_FLAG_ERROR }, #endif { "V4L2_BUF_FLAG_TIMECODE", V4L2_BUF_FLAG_TIMECODE }, +#ifdef V4L2_BUF_FLAG_INPUT { "V4L2_BUF_FLAG_INPUT", V4L2_BUF_FLAG_INPUT }, +#endif }; explain_parse_bits_print(sb, value, table, SIZEOF(table)); Index: libexplain-0.52.D002/libexplain/buffer/v4l2_buffer.c === --- libexplain-0.52.D002.orig/libexplain/buffer/v4l2_buffer.c 2012-03-04 16:46:45.0 +0400 +++ libexplain-0.52.D002/libexplain/buffer/v4l2_buffer.c 2014-01-13 02:01:17.414388563 +0400 @@ -87,8 +87,16 @@ } explain_string_buffer_puts(sb, ", length = "); explain_buffer_uint32_t(sb, data->length); +#ifdef V4L2_FLAG_BUF_INPUT explain_string_buffer_puts(sb, ", input = "); explain_buffer_uint32_t(sb, data->input); +#else + if (data->reserved2) + { + explain_string_buffer_puts(sb, ", reserved2 = "); + explain_buffer_uint32_t(sb, data->reserved2); + } +#endif if (data->reserved) { explain_string_buffer_puts(sb, ", reserved = "); Index: libexplain-0.52.D002/codegen/gram.y === --- libexplain-0.52.D002.orig/codegen/gram.y 2012-03-04 16:46:45.0 +0400 +++ libexplain-0.52.D002/codegen/gram.y 2014-01-13 02:19:17.048219297 +0400 @@ -257,7 +257,7 @@ } -static int yyparse(void); +/*static int yyparse(void);*/ static node_t *result; #if YYDEBUG extern int yydebug; Index: libexplain-0.52.D002/test/05/t0570a.sh === --- libexplain-0.52.D002.orig/test/05/t0570a.sh 2012-03-04 16:46:45.0 +0400 +++ libexplain-0.52.D002/test/05/t0570a.sh 2014-01-13 02:26:49.860788041 +0400 @@ -27,9 +27,9 @@ ioctl(fildes = 42, request = VIDIOC_QBUF, struct v4l2_buffer *data = { index = 0, type = 0, bytesused = 0, flags = 0, field = V4L2_FIELD_ANY, timestamp = { 0 seconds }, timecode = { type = 0, flags = 0, frames = 0, -seconds = 0, minutes = 0, hours = 0 }, sequence = 0, memory = 0, length = -0, input = 0 }) failed, Invalid argument (EINVAL) because the data->type -argument was incorrectly specified +seconds = 0, minutes = 0, hours = 0 }, sequence = 0, memory = 0, length = 0 +}) failed, Invalid argument (EINVAL) because the data->type argument was +incorrectly specified fubar test $? -eq 0 || no_result
Bug#733122: fatal error: Typelib file for namespace 'GnomeBluetoothApplet' (any version) not found
On 12/01/2014 17:55, Michael Biebl wrote: > Am 12.01.2014 17:47, schrieb Michael Biebl: >> In summary, the patch is not quite ready yet imho. > > Hm, looking more closely, instead of moving the files around, it might > be better to use a try {} catch {} statement like we do for NM. > > Robert, can you try the following patch: This successfully takes care of the bluetooth part. NM, however, is still a problem since not all its instances are protected by try-catch. I.e. the one in ui/sessionMode.js would need a similar hack. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729846: gnome-session: No background/wallpaper after upgrade
at bottom :- On 1/7/14, Olivier Berger wrote: > On Wed, Nov 20, 2013 at 08:33:29PM +0530, shirish शिरीष wrote: >> >> This is the reply I got from upstream :- >> >> "https://code.launchpad.net/~ubuntu-branches/ubuntu/trusty/nautilus/trusty: >> >> patches/ubuntu_revert_no_wallpaper.patch: >> - revert upstream changes to use a rgba desktop view, until the >> other >> components are ready for that change, see lp #1159430 for details " >> > > Uh... what do you mean by upstream, here ? AFAIU, the pointer above refers > to something that may well be specific to ubuntu... and given that they use > unity, etc. I doubt this applies to Debian the same way. > > Can you be more specific on what you did and who responded what ? > > AFAIU, Emilio Pozuelo Monfort provided enough details on the problem and we > should require some dedicated component for handling the background... > > Thanks in advance. > > Best regards, > > -- > Olivier BERGER > http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: > 2048R/5819D7E8 > Ingenieur Recherche - Dept INF > Institut Mines-Telecom, Telecom SudParis, Evry (France) By upstream I meant the gnome-flashback mailing list. The code is 'supposedly' a pointer for somebody wanting to something similar for GNOME here. Look forward to know/see if somebody does hack something and if needed to do some testing of the same.. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734441: link to
Am Dienstag, 7. Januar 2014, 13:33:00 schrieb jida...@jidanni.org: > file:///usr/share/doc/apache2-doc/manual/en/mod/mod_setenvif.html > mentions twice, > but does not link them to > file:///usr/share/doc/apache2-doc/manual/en/mod/core.html#if will be fixed in 2.4.8 Stefan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735121: [tulip] Non free files
On Sun, Jan 12, 2014 at 09:46:19PM +, bastien ROUCARIES wrote: > Package: tulip > Severity: serious > x-cc-debug: ftpmas...@ftp-master.debian.org > > The following file are not free: Gasp. Those bundle-everything project are a real hell to maintain... I'll nuke those fonts from the orig tarball. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729540: closed by Bernd Zeimetz (Bug#729540: fixed in open-vm-tools 2:9.4.0-1280544-1)
hi, please use open-vm-tools 2:9.4.0-1280544-5 - not -1. Building with 3.11 should work fine with -1, but 3.12 (and gcc 4.8) needs -5. Mihai: -5 builds just fine with gcc 4.8 :) Cheers, Bernd On 01/07/2014 07:33 AM, Jim Barber wrote: > Hi Bernd. > > I have tried this new version of open-vm-tools-dkms against the 3.12 kernel > that > is now in Debian testing and it failed to compile for me. > The contents of the /var/lib/dkms/open-vm-tools/9.4.0/build/make.log file > follows: > > > DKMS make.log for open-vm-tools-9.4.0 for kernel 3.12-1-amd64 (x86_64) > Tuesday 7 January 14:12:27 WST 2014 > Using 2.6.x kernel build system. > make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' > make -C /lib/modules/3.12-1-amd64/build/include/.. SUBDIRS=$PWD > SRCROOT=$PWD/. \ > MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules > make[1]: Entering directory `/usr/src/linux-headers-3.12-1-amd64' > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/block.o > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.o > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c: In function > ‘ExecuteBlockOp’: > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/control.c:286:9: > warning: > assignment from incompatible pointer type [enabled by default] > name = getname(buf); > ^ > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.o > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: > initialization from incompatible pointer type [enabled by default] > .d_revalidate = DentryOpRevalidate, > ^ > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:38:4: warning: > (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default] > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c: In function > ‘DentryOpRevalidate’: > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: warning: > passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from > pointer without a cast [enabled by default] >return actualDentry->d_op->d_revalidate(actualDentry, nd); >^ > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/dentry.c:104:7: note: > expected ‘unsigned int’ but argument is of type ‘struct nameidata *’ > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/file.o > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/filesystem.o > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: > initialization from incompatible pointer type [enabled by default] > .lookup = InodeOpLookup, > ^ > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:49:4: warning: > (near initialization for ‘RootInodeOps.lookup’) [enabled by default] > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function > ‘InodeOpLookup’: > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:138:32: error: > incompatible types when assigning to type ‘kgid_t’ from type ‘int’ > inode->i_uid = inode->i_gid = 0; > ^ > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c: In function > ‘InodeOpFollowlink’: > /var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.c:224:4: error: > implicit declaration of function ‘vfs_follow_link’ > [-Werror=implicit-function-declaration] > ret = vfs_follow_link(nd, iinfo->name); > ^ > cc1: some warnings being treated as errors > make[4]: *** [/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock/linux/inode.o] > Error 1 > make[3]: *** [_module_/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock] Error 2 > make[2]: *** [sub-make] Error 2 > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/src/linux-headers-3.12-1-amd64' > make: *** [vmblock.ko] Error 2 > make: Leaving directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmblock' > Using 2.6.x kernel build system. > Building vmhgfs without VMCI module symbols. > make: Entering directory `/var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs' > make -C /lib/modules/3.12-1-amd64/build/include/.. SUBDIRS=$PWD > SRCROOT=$PWD/. \ > MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/9.4.0/build modules > make[1]: Entering directory `/usr/src/linux-headers-3.12-1-amd64' > CC [M] /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.o > In file included from > /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.h:44:0, > from > /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/backdoor.c:49: > /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/./shared/backdoor_types.h: In > function ‘BACKDOOR_STRUCT_SIZES’: > /var/lib/dkms/open-vm-tools/9.4.0/build/vmhgfs/./shared/vm_assert.h:366:20: > warning: typedef ‘AssertOnCompileFailed’ locally defined but not used > [-Wunused-local-typedefs] >typedef char AssertOnCompileFailed[AssertOnCo
Bug#722789:
Hi didn't found the problem, If look at build log https://buildd.debian.org/status/fetch.php?pkg=libapr-memcache&arch=mips&ver=0.7.0-1&stamp=1334370101 There is no problem for mips build if look to build server. I build libapr-memcache as you can see in the rules file : %: dh $@ So to ./configure command is done by dh_au In case of amd64 system it configures like this: "./configure" \ "--build=x86_64-linux-gnu" \ "--prefix=/usr" \ "--includedir=${prefix}/include" \ "--mandir=${prefix}/share/man" \ "--infodir=${prefix}/share/info" \ "--sysconfdir=/etc" \ "--localstatedir=/var" \ "--libdir=${prefix}/lib/x86_64-linux-gnu" \ "--libexecdir=${prefix}/lib/x86_64-linux-gnu" \ "--disable-maintainer-mode" \ "--disable-dependency-tracking" \ "$@" In case of mips system it configures like this : #! /bin/sh # # Created by configure "./configure" \ "--build=mips-linux-gnu" \ "--prefix=/usr" \ "--includedir=${prefix}/include" \ "--mandir=${prefix}/share/man" \ "--infodir=${prefix}/share/info" \ "--sysconfdir=/etc" \ "--localstatedir=/var" \ "--libexecdir=${prefix}/lib/libapr-memcache" \ "--disable-maintainer-mode" \ "--disable-dependency-tracking" \ "$@" So if you still thinks this wrong for debian as multi arch system then you need to file bug against debhelper. Becouse the dh_auto_configure add's the configure options like libexecdir and libdir if he think it is needed so this is not libapr-memcache bug so I will mark it as wontfix Wontfix #722789
Bug#691576: GDB still broken with 3.11.10-1
On Sun, 2014-01-12 at 22:48 +0100, Émeric MASCHINO wrote: > 2014/1/12 Ben Hutchings : > > > > Sorry, I'm being silly. udev is built as part of systemd now, so this > > is independent of whether you use systemd as init. And systemd doesn't > > currently run as init in the initramfs. > > Uh, OK. > > How can I help further? If you have space to install wheezy on a separate partition, please can you try that. (Of course, that crash ought to be fixed in 3.2.y. But I don't know that anyone will have the time and knowledge to do so. And it's not part of this bug.) Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#734171: Network install does not work with I-217V ethernet controller
"Lennart Sorensen" writes: > On Mon, Jan 06, 2014 at 05:21:30PM +0100, Cyril Brulebois wrote: >> Lennart Sorensen (2014-01-06): >> > Debian stable means not changing things in general, so adding new >> > drivers is not something that is done. >> >> Sorry, that's wrong. >> >> The linux kernel is regularly updated in stable to add support for >> new(er) hardware. > > Well if 3.2.x updates upstream add new drivers, then sure, but I don't > recall ever seeing debian backport drivers to a stable release kernel. Look again. For example: zgrep backport /usr/share/doc/linux-image-*/changelog.Debian.gz My experience is that the Debian kernel team is more than happy to accept backported drivers. But someone has to do the job. Bjørn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734787: dh-golang: If go package is package main don't install into /usr/share/gocode/src/
Hi Sergio, Sergio Schvezov writes: > When creating a go binary package, if the go code is from package main > it shouldn't install to /usr/share/gocode Can you give me an example for this please? An example real world package would help. -- 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#734977: Some more examples with fltk-config --compile and undefined references
Andreas Weber writes: > $ dpkg -s g++ | grep '^Version:' > Version: 4:4.7.2-1 > $ type -all g++ > g++ ist /usr/bin/g++ > $ ls -l /usr/bin/g++ > lrwxrwxrwx 1 root root 7 Sep 27 2012 /usr/bin/g++ -> g++-4.7 > $ g++ -v 2>&1 | tail -n1 > gcc version 4.7.2 (Debian 4.7.2-5) OK, thanks. That all looks normal; I'm still curious as to why you specifically are encountering these errors, but will just treat it as a moot point and focus on adding the necessary symbols. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730309:
Severity whislist Working on stable canidate at the moment. When that one is in unstable, i will look in to place 1.4.x in to experimental
Bug#734785: dh-golang: Allow comments in debian/control
control: reassign -1 libparse-debcontrol-perl Hi Sergio, Sergio Schvezov writes: > Dear Maintainer, > Adding comments to debian/control break dh_golang > >dh_golang -O--buildsystem=golang -O--fail-missing >Parse error: invalid key/value stansa at line 13 of data ("# This >is a comment"). >make: *** [binary] Error 255 > > From > http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-controlsyntax > > "Lines starting with # without any preceding whitespace are comments > lines that are only permitted in source package control files > (debian/control). These comment lines are ignored, even between two > continuation lines. They do not end logical lines." This seems to be a deficiency in the Parse::DebControl Perl package. I have a note in the dh-golang source stating that we might want to switch to Dpkg::Control::Info, but I can’t remember what the rationale for/against doing that was. For the time being, I reassigned the bug to the correct package. Feel free to send a patch in order to get things going faster. -- 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#734809: [Pkg-systemd-maintainers] Bug#734809: systemd: systemctl disable/enable => Failed to issue method call: No such file or directory
Hi Christoph, Christoph Anton Mitterer writes: > # systemctl enable ssh > Synchronizing state for ssh with sysvinit using update-rc.d... > Executing /usr/sbin/update-rc.d ssh defaults > insserv: warning: current start runlevel(s) (empty) of script `ssh' overrides > LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (2 3 4 5) of script `ssh' > overrides LSB defaults (empty). > Executing /usr/sbin/update-rc.d ssh enable > Failed to issue method call: No such file or directory > > # systemctl disable ssh > Synchronizing state for ssh with sysvinit using update-rc.d... > Executing /usr/sbin/update-rc.d ssh defaults > Executing /usr/sbin/update-rc.d ssh disable > insserv: warning: current start runlevel(s) (empty) of script `ssh' overrides > LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (2 3 4 5) of script `ssh' > overrides LSB defaults (empty). > Failed to issue method call: No such file or directory > > > There is always that "Failed to issue method call: No such file or directory" > error. Not on my machine: root@midna ~ $ systemctl enable ssh Synchronizing state for ssh with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ssh enable root@midna ~ $ systemctl disable ssh Synchronizing state for ssh with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ssh disable insserv: warning: current start runlevel(s) (empty) of script `ssh' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script `ssh' overrides LSB defaults (empty). root@midna ~ $ systemctl enable ssh Synchronizing state for ssh with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ssh enable Can you run strace -f -o /tmp/strace.log -s 2048 systemctl enable ssh and provide /tmp/strace.log? Also, please run strace -f -o /tmp/strace-systemd.log -s 2048 -p 1 before that and provide that file as well. Thanks. -- 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#735129: burp: Lintian reports old-fsf-address-in-copyright-file
Package: burp Version: 1.3.26-1 Severity: normal Dear Maintainer, Lintian reports old-fsf-address-in-copyright-file -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 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#735128: burp: Lintian reports hardening-no-relro
Package: burp Version: 1.3.8-1 Severity: normal Dear Maintainer, Lintian reports hardening-no-relro usr/sbin/bedup usr/sbin/bedup usr/sbin/burp usr/sbin/burp -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 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#691576: GDB still broken with 3.11.10-1
2014/1/12 Ben Hutchings : > > Sorry, I'm being silly. udev is built as part of systemd now, so this > is independent of whether you use systemd as init. And systemd doesn't > currently run as init in the initramfs. Uh, OK. How can I help further? Emeric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735127: libapr-memcache0: Lintian reports hardening-no-relro
Package: libapr-memcache0 Version: 0.7.0-1 Severity: normal Dear Maintainer, Lintian reports W hardening-no-relro usr/lib/libapr_memcache.so.0.0.1 usr/lib/libapr_memcache.so.0.0.1 -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 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#735043: [Pkg-owncloud-maintainers] Bug#735043: libqtkeychain0: Please update to version 0.2.0 which includes gnome keyring support
Hello, > Please upgrade to version 0.2.0, which includes gnome keyring support. Either I'm blind or version 0.2.0 isn't released. According to upstream it isn't taged: https://github.com/frankosterfeld/qtkeychain/releases where did you see the release of 0.2.0? I only found the request for the new version at the bug report, that is not closed: https://github.com/frankosterfeld/qtkeychain/issues/21 If it is released I'll package it and will ship it. Regards, sandro signature.asc Description: This is a digitally signed message part.
Bug#734977: Some more examples with fltk-config --compile and undefined references
Am 12.01.2014 22:06, schrieb Aaron M. Ucko: > Could you please run the following commands, to confirm that you're > running the proper version? $ dpkg -s g++ | grep '^Version:' Version: 4:4.7.2-1 $ type -all g++ g++ ist /usr/bin/g++ $ ls -l /usr/bin/g++ lrwxrwxrwx 1 root root 7 Sep 27 2012 /usr/bin/g++ -> g++-4.7 $ g++ -v 2>&1 | tail -n1 gcc version 4.7.2 (Debian 4.7.2-5) -- Andy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734392: Error: Can't connect to unix socket
It's a hard time for me due to business work cummulation in January. Anyway the speechd problem is very interesting and a priority thing in my hobby time. I did a deciding debugging session today. Speech-dispatcher output is very limited when spd-say command is issued. This probably needs an upstream change, but that's a thing for the future. I guess the problem comes from pulse being the default audio output. When I change the configuration from pulse to alsa, spd-say starts working ok. I can't confirm, why the source compiled from speechd upstream was working better than the Debian package. Maybe because of different configuration files. /etc vs /usr/local/etc. Maybe I did not run ldconfig and the state of binaries was hard to determine. I found the logs finally, using strace -f spd-say test 2>&1|grep log [pid 14992] mkdir("/run/user/0/speech-dispatcher/log/", 0700) = -1 EEXIST (File exists) [pid 14992] mkdir("/run/user/0/speech-dispatcher/log/debug", 0700) = -1 EEXIST (File exists) [pid 14992] open("/run/user/0/speech-dispatcher/log//speech-dispatcher.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 7 [pid 14992] open("/run/user/0/speech-dispatcher/log//espeak.log", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 11 [pid 14992] open("/run/user/0/speech-dispatcher/log//cicero.log", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 14 [pid 15001] open("/var/log/speech-dispatcher/cicero-executable.log", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 15 [pid 14992] open("/run/user/0/speech-dispatcher/log//dummy.log", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 17 [pid 14992] open("/run/user/0/speech-dispatcher/log//flite.log", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 20 [pid 14992] open("/run/user/0/speech-dispatcher/log//generic.log", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 23 [pid 14992] open("/run/user/0/speech-dispatcher/log//speech-dispatcher.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 6 They seem to ask for another bug report. This one may be closed, no more grave problems :) Jarek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691576: GDB still broken with 3.11.10-1
On Sun, 2014-01-12 at 22:30 +0100, Émeric MASCHINO wrote: > 2014/1/12 Ben Hutchings : > > > > You can have sysvinit and systemd installed in parallel and then use the > > 'init' kernel parameter to switch between them. Only systemd-sysv > > conflicts/replaces sysvinit. > > So, I've reinstalled sysvinit and sysvinit-core that purged > systemd-sysv. I can't however remove systemd itself as it's required > by numerous GNOME packages. > I've rebooted my system and even reinstalled your -O1 kernel in order > to be sure that initrd is regenerated. > Still the same however! How is it that systemd-udevd still shows up? Sorry, I'm being silly. udev is built as part of systemd now, so this is independent of whether you use systemd as init. And systemd doesn't currently run as init in the initramfs. Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#733319: [psi-plus-plugins] OTR conversations between psi-plus and pidgin sometimes don't work
Hi Boris, Thanks for your patch. Today I had some time to test it and is does fix all the OTR problems I had before. So I can confirm that the patch fixes this bug. Greetings, Maxi signature.asc Description: This is a digitally signed message part.
Bug#735126: darktable: add LUA support
Package: darktable Version: 1.4-1 Severity: minor Dear Maintainer, The new version of Darktable (1.4) introduces LUA support. In fact, the release notes as shipped with this version in Debian mention that this feature is available. Is it possible to add LUA support or, if not, to put a note in somewhere mentioning that it's been disabled? Hopefully this will help anyone looking to try out this new feature. Cheers, Steve -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 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 darktable depends on: ii gtk2-engines 1:2.20.2-3 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libcolord11.0.5-1 ii libcurl3-gnutls 7.34.0-1 ii libexiv2-12 0.23-1 ii libflickcurl0 1.24-1 ii libgcc1 1:4.8.2-10 ii libgdk-pixbuf2.0-02.28.2-1+b1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglib2.0-0 2.36.4-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgnome-keyring0 3.4.1-1 ii libgomp1 4.8.2-10 ii libgphoto2-2 2.4.14-2.4 ii libgphoto2-port0 2.4.14-2.4 ii libgtk2.0-0 2.24.22-1 ii libice6 2:1.0.8-2 ii libilmbase6 1.0.1-6 ii libjpeg8 8d-2 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libjson-glib-1.0-00.16.2-1 ii liblcms2-22.2+git20110628-2.3+b1 ii liblensfun0 0.2.8-1 ii libopenexr6 1.6.1-7 ii libpango-1.0-01.36.0-1+b1 ii libpangocairo-1.0-0 1.36.0-1+b1 ii libpng12-01.2.49-5 ii librsvg2-22.40.0-1 ii libsdl1.2debian 1.2.15-8 ii libsm62:1.2.1-2 ii libsoup2.4-1 2.44.2-1 ii libsqlite3-0 3.8.2-1 ii libstdc++64.8.2-10 ii libtiff5 4.0.3-7 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxml2 2.9.1+dfsg1-3 ii zlib1g1:1.2.8.dfsg-1 darktable recommends no packages. darktable 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#691576: GDB still broken with 3.11.10-1
2014/1/12 Ben Hutchings : > > You can have sysvinit and systemd installed in parallel and then use the > 'init' kernel parameter to switch between them. Only systemd-sysv > conflicts/replaces sysvinit. So, I've reinstalled sysvinit and sysvinit-core that purged systemd-sysv. I can't however remove systemd itself as it's required by numerous GNOME packages. I've rebooted my system and even reinstalled your -O1 kernel in order to be sure that initrd is regenerated. Still the same however! How is it that systemd-udevd still shows up? Emeric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735125: RFS: spatialindex/1.8.1-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "spatialindex" Package name: spatialindex Version : 1.8.1-2 Upstream Author : Marios Hadjieleftheriou URL : http://libspatialindex.github.io/ License : MIT Section : science It builds those binary packages: libspatialindex3 - General framework for developing spatial indices libspatialindex-c3 - General framework for developing spatial indices - C library libspatialindex-dev - General framework for developing spatial indices - development files libspatialindex3-dbg - General framework for developing spatial indices - debugging symbols To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spatialindex Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spatialindex/spatialindex_1.8.1-2.dsc More information about libspatialindex can be obtained from http://libspatialindex.github.io/. Changes since the last upload: * Update pkg-config patch to remove LDFLAGS from Libs. (closes: #735039) Regards, Sebastiaan Couwenberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735124: RFS: palo/1.92-1 [ITA] -- parisc bootloader
Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "palo" * Package name: palo Version : 1.92 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : admin It builds those binary packages: palo - Linux boot loader for parisc/hppa To access further information about this package, please visit the following URL: http://mentors.debian.net/package/palo Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/palo/palo_1.92.dsc Regards, Helge Deller -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)
Control: unblock 734233 by 734256 Control: reassign 734256 ruby1.8 1.8.7.358-9 Control: forcemerge 734256 734525 Control: reassign -1 ruby1.8 1.8.7.358-9 Control: forcemerge -1 734525 Control: affects -1 + apt-listbugs On Sun, 12 Jan 2014 20:52:40 +0100 Ricardo Mones wrote: > Package: apt-listbugs > Version: 0.1.12 > Severity: grave > Justification: renders package unusable > > Hi, Hello Ricardo, thanks for reporting the issue, which is, however, already known. Apologies for not setting an appropriate "affects apt-listbugs" for the previously reassigned bug reports. I am doing so now, so that these reports will show up in http://bugs.debian.org/apt-listbugs > > Since last update apt-listbugs doesn't allow to apt-get to install packages, > it always ends like this: > > /usr/lib/ruby/vendor_ruby/debian.rb:24:in `require': no such file to load -- > debian_version (LoadError) > from /usr/lib/ruby/vendor_ruby/debian.rb:24 > from /usr/sbin/apt-listbugs:289:in `require' > from /usr/sbin/apt-listbugs:289 > E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) > E: Failure running script /usr/sbin/apt-listbugs apt > [...] > Thanks in advance for any suggestion, > [...] > ii ruby1.8 [ruby-interpreter] 1.8.7.358-9 You are still using ruby1.8 as system-wide default Ruby interpreter. You should switch to ruby1.9.1 as default interpreter. The following steps should hopefully fix the issue for you: • temporarily disable apt-listbugs: # mv /etc/apt/apt.conf.d/10apt-listbugs /root/ • upgrade ruby1.8: # apt-get update # apt-get install ruby1.8 • this should automatically also pull in ruby1.9.1, since ruby1.8/1.8.7.358-10 no longer provides "ruby-interpreter", and apt-listbugs depends on "ruby | ruby-interpreter"; otherwise, manually install it: # apt-get install ruby1.9.1 • make sure the system-wide default Ruby interpreter is ruby1.9.1: $ ruby -v ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] • re-enable apt-listbugs: # mv /root/10apt-listbugs /etc/apt/apt.conf.d/ At this point you should be again able to upgrade or install packages while using apt-listbugs. Please let me know, if something went wrong. Thanks! -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpcWhSw3DKYh.pgp Description: PGP signature
Bug#735077: Xpad v4.2 update
Hi Bart, Xpad v4.2 solves several bugs, including a Debian bug on 'your' list'. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614337 For the other Xpad bugreports in your list, I have responded a while ago. Hopefully this helps you too. If I can do anything, please let me know. Regards, Arthur Borsboom.
Bug#735123: ikiwiki: inline plugin: allow feed title distinct from page title
Package: ikiwiki Version: 3.20120629 Severity: wishlist Dear Joey, A reader of my blog asked me to alter the element of the feeds to something more descriptive than just 'blog' -- but I didn't want to alter the page title within the overall ikiwiki instance. (Nor did I particularly feel like I should be maintaining my own feed templates just for this). So, please consider adding a title parameter to the inline directive, which would override the current default title (the including page title, or the wikiname if it's the index page). If reportbug will let me, I'll attach a patch to this report to that effect (against 3.20120629, sorry; I looked at HEAD and didn't see anything that would be problematic at a glance). -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (900, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-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 --- ikiwiki-3.20120629/doc/ikiwiki/directive/inline.mdwn 2012-05-27 22:56:03.0 +0200 +++ ikiwiki-3.20120629~csr1/doc/ikiwiki/directive/inline.mdwn 2014-01-12 21:35:02.0 +0100 @@ -49,6 +49,8 @@ Set to 0 to show all matching pages. * `archive` - If set to "yes", only list page titles and some metadata, not full contents. +* `title` - Sets the title of the rss feed if one is generated. + Defaults to the name of the page. * `description` - Sets the description of the rss feed if one is generated. Defaults to the name of the wiki. * `skip` - Specify a number of pages to skip displaying. Can be useful --- ikiwiki-3.20120629/IkiWiki/Plugin/inline.pm 2012-05-17 06:31:15.0 +0200 +++ ikiwiki-3.20120629~csr1/IkiWiki/Plugin/inline.pm 2014-01-12 21:41:55.0 +0100 @@ -186,6 +186,13 @@ if (! exists $params{feedshow} && exists $params{show}) { $params{feedshow}=$params{show}; } + my $title; + if (exists $params{title}) { + $title = $params{title}; + } + else { + $title = $params{page} ne "index" ? pagetitle($params{page}) : $config{wikiname}; + } my $desc; if (exists $params{description}) { $desc = $params{description} @@ -465,7 +472,7 @@ if (! $params{preview}) { writefile($rssp, $config{destdir}, genfeed("rss", - $config{url}."/".$rssp, $desc, $params{guid}, $params{page}, @feedlist)); + $config{url}."/".$rssp, $title, $desc, $params{guid}, $params{page}, @feedlist)); $toping{$params{destpage}}=1 unless $config{rebuild}; $feedlinks{$params{destpage}}.=qq{}; } @@ -475,7 +482,7 @@ will_render($params{destpage}, $atomp); if (! $params{preview}) { writefile($atomp, $config{destdir}, - genfeed("atom", $config{url}."/".$atomp, $desc, $params{guid}, $params{page}, @feedlist)); + genfeed("atom", $config{url}."/".$atomp, $title, $desc, $params{guid}, $params{page}, @feedlist)); $toping{$params{destpage}}=1 unless $config{rebuild}; $feedlinks{$params{destpage}}.=qq{}; } @@ -614,6 +621,7 @@ sub genfeed ($@) { my $feedtype=shift; my $feedurl=shift; +my $feedtitle=shift; my $feeddesc=shift; my $guid=shift; my $page=shift; @@ -687,7 +695,7 @@ my $template=template_depends($feedtype."page.tmpl", $page, blind_cache => 1); $template->param( - title => $page ne "index" ? pagetitle($page) : $config{wikiname}, + title => $feedtitle, wikiname => $config{wikiname}, pageurl => $url, content => $content,
Bug#734977: Some more examples with fltk-config --compile and undefined references
Andreas Weber writes: > Hi Aaron, thank you for your fast reply. No problem. > If I compile it without fltk-config I get the same results, regardless > if with -O0 or -O2. Meanwhile, I tried to reproduce these errors in a wheezy (stable) chroot, but couldn't, even with optimization disabled. I do know how to force definitions of the symbols in question[1], and will go ahead and do so, but remain puzzled as to why your g++ isn't taking care of them itself. Could you please run the following commands, to confirm that you're running the proper version? dpkg -s g++ | grep '^Version:' type -all g++ ls -l /usr/bin/g++ g++ -v 2>&1 | tail -n1 Thanks! [1] Essentially, compile with -fkeep-inline-functions, though some compensatory adjustments will be necessary to avoid circularity between libfltk and libfltk_cairo. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733675: dictionaries-common: ispell-buffer misses misspellings in tex mode
Thank you for the bisection and further information. > I do not have much spare time these days, do not know when I will be > able to look at this in depth. I know the feeling. I will also try to look into it. Best, -Sanjoy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688350: getting worse
Now when I restore from sleep, the window frames around open windows in gnome3 vanish, leaving me unable to select anything, activate the actions corners, or type. I have to switch to a tty and restart gdm3 after disabling eth0. Mark
Bug#734745: graphviz: diff for NMU version 2.26.3-16.1
Dear David and Christoph, I've prepared an NMU for graphviz (versioned as 2.26.3-16.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. I have (for #734745) also packages ready for squeeze-security and wheezy-security, but I have not yet uploaded them. Regards, Salvatore diff -Nru graphviz-2.26.3/debian/changelog graphviz-2.26.3/debian/changelog --- graphviz-2.26.3/debian/changelog 2013-12-23 18:55:30.0 +0100 +++ graphviz-2.26.3/debian/changelog 2014-01-12 17:09:27.0 +0100 @@ -1,3 +1,19 @@ +graphviz (2.26.3-16.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add CVE-2014-1235.patch patch. +CVE-2014-1235: buffer overflow vulnerability in yyerror() introduced by +original fix for CVE-2014-0978. (Closes: #734745) + * Add CVE-2014-1236.patch patch. +CVE-2014-1236: buffer overflow from user input (the regexp in chkNum +would accept arbitrary long digit list) (Closes: #734745) + * Enable hardened build flags. +Thanks to Moritz Muehlenhoff (Closes: #734804) + * Add fix-missing-format-string.patch patch. +Fixes missing format strings for printf and fprintf calls. + + -- Salvatore Bonaccorso Sun, 12 Jan 2014 14:37:45 +0100 + graphviz (2.26.3-16) unstable; urgency=medium * Add patch cherry-picked from upstream's github - fixes buffer diff -Nru graphviz-2.26.3/debian/patches/CVE-2014-1235.patch graphviz-2.26.3/debian/patches/CVE-2014-1235.patch --- graphviz-2.26.3/debian/patches/CVE-2014-1235.patch 1970-01-01 01:00:00.0 +0100 +++ graphviz-2.26.3/debian/patches/CVE-2014-1235.patch 2014-01-12 17:09:27.0 +0100 @@ -0,0 +1,22 @@ +Description: Fix buffer overflow in yyerror() + CVE-2014-1235: buffer overflow vulnerability in yyerror() introduced by + original fix for CVE-2014-0978 +Origin: upstream, https://github.com/ellson/graphviz/commit/d266bb2b4154d11c27252b56d86963aef4434750 +Bug-Debian: http://bugs.debian.org/734745 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1050871 +Forwarded: not-needed +Author: Salvatore Bonaccorso +Last-Update: 2014-01-11 + +--- a/lib/cgraph/scan.l b/lib/cgraph/scan.l +@@ -203,7 +203,8 @@ + agxbput (&xb, InputFile); + agxbput (&xb, ": "); + } +- sprintf(buf," %s in line %d near '", str,line_num); ++ agxbput (&xb, str); ++ sprintf(buf," in line %d near '", line_num); + agxbput (&xb, buf); + agxbput (&xb, yytext); + agxbput (&xb,"'\n"); diff -Nru graphviz-2.26.3/debian/patches/CVE-2014-1236.patch graphviz-2.26.3/debian/patches/CVE-2014-1236.patch --- graphviz-2.26.3/debian/patches/CVE-2014-1236.patch 1970-01-01 01:00:00.0 +0100 +++ graphviz-2.26.3/debian/patches/CVE-2014-1236.patch 2014-01-12 17:09:27.0 +0100 @@ -0,0 +1,54 @@ +Description: Fix possible buffer overflow problem in chkNum of scanner + CVE-2014-1236: buffer overflow from user input (the regexp in chkNum + would accept arbitrary long digit list) +Origin: backport, https://github.com/ellson/graphviz/commit/1d1bdec6318746f6f19f245db589eddc887ae8ff +Bug-Debian: http://bugs.debian.org/734745 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1050872 +Forwarded: not-needed +Author: Salvatore Bonaccorso +Last-Update: 2014-01-11 + +--- a/lib/cgraph/scan.l b/lib/cgraph/scan.l +@@ -131,15 +131,32 @@ + * and report this to the user. + */ + static int chkNum(void) { +- unsigned char c = (unsigned char)yytext[yyleng-1]; /* last character */ +- if (!isdigit(c) && (c != '.')) { /* c is letter */ +- char buf[BUFSIZ]; +- sprintf(buf,"syntax error - badly formed number '%s' in line %d\n",yytext,line_num); +-strcat (buf, "splits into two name tokens"); +- agerr(AGWARN,buf); +-return 1; +- } +- else return 0; ++unsigned char c = (unsigned char)yytext[yyleng-1]; /* last character */ ++if (!isdigit(c) && (c != '.')) { /* c is letter */ ++ unsigned char xbuf[BUFSIZ]; ++ char buf[BUFSIZ]; ++ agxbuf xb; ++ char* fname; ++ ++ if (InputFile) ++ fname = InputFile; ++ else ++ fname = "input"; ++ ++ agxbinit(&xb, BUFSIZ, xbuf); ++ ++ agxbput(&xb,"syntax ambiguity - badly delimited number '"); ++ agxbput(&xb,yytext); ++ sprintf(buf,"' in line %d of ", line_num); ++ agxbput(&xb,buf); ++ agxbput(&xb,fname); ++ agxbput(&xb, " splits into two tokens\n"); ++ agerr(AGWARN,agxbuse(&xb)); ++ ++ agxbfree(&xb); ++ return 1; ++} ++else return 0; + } + + /* The LETTER class below consists of ascii letters, underscore, all non-ascii diff -Nru graphviz-2.26.3/debian/patches/fix-missing-format-string.patch graphviz-2.26.3/debian/patches/fix-missing-format-string.patch --- graphviz-2.26.3/debian/patches/fix-missing-format-string.patch 1970-01-01 01:00:00.0 +0100 +++ graphviz-2.26.3/debian/patches/fix-missing-format-string.patch 2014-01-12 17:09:27.0 +0100 @@ -0,0 +1,94 @@ +Description: Fix missing format string +Origin: backport, https://github.com/ellson/graphviz/commit/1b3b90cd1afd712d1d7153377531f758797a7535 +Forwarded: not-needed +Author: S
Bug#727070: xpdf: Upgrade of fontconfig from 2.10.2 to 2.11 causes xpdf to deadlock on x86 and fail mutex on x86_64
On 12/01/14 17:14, Peter wrote: > On 10/01/14 23:45, Celelibi wrote: >> Hello, >> >> On the side of fontconfig, they say the bug is on the xpdf side. Has >> this bug been forwarded upstream? >> >> Is there any news about this bug? >> A workaround that would work with the new version of fontconfig? >> >> >> Celelibi >> > I have been able to bodge it on my system by installing the Fedora package. > http://rpmfind.net//linux/RPM/fedora/20/x86_64/x/xpdf-3.03-8.fc20.x86_64.html > > Click on the large font title to get the rpm, and convert using Debian's > alien package. Then install using gdebi > > libfontconfig1 etc must be downgraded to version 2.11.0-1 as it is > version 2.11.0-2 that includes > intentional breakage of xpdf <= version -11 (The Fedora package > installs as version -9) > > I've also seen some reports of installs of the Ubuntu xpdf, but have not > tried this myself. > > Peter > One further workaround: The 32bit xpdf in the upstream precompiled binary package works fine on Jessie. http://www.foolabs.com/xpdf/download.html No install for this xpdf, eg just extract/run ./xpdf myfile.pdf I cannot run the 64bit upstream. Unsatisfiable dependency on libpng14 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735121: [tulip] Non free files
Package: tulip Severity: serious x-cc-debug: ftpmas...@ftp-master.debian.org The following file are not free: library/tulip-ogl/bitmaps/fonts/Arial/Arial.ttf usual name is arial.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Arial/Arial_Bold.ttf usual name is arialbd.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Arial/Arial_Bold_Italic.ttf usual name is arialbi.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Arial/Arial_Italic.ttf usual name is ariali.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Courier_New/Courier_New.ttf usual name is cour.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Courier_New/Courier_New_Bold.ttf usual name is courbd.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Courier_New/Courier_New_Bold_Italic.ttf usual name is courbi.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Courier_New/Courier_New_Italic.ttf usual name is couri.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Georgia/Georgia.ttf usual name is georgia.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Georgia/Georgia_Bold.ttf usual name is georgiab.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Georgia/Georgia_Bold_Italic.ttf usual name is georgiaz.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Georgia/Georgia_Italic.ttf usual name is georgiai.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Times_New_Roman/Times_New_Roman.ttf usual name is times.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Times_New_Roman/Times_New_Roman_Bold.ttf usual name is timesbd.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Times_New_Roman/Times_New_Roman_Bold_Italic.ttf usual name is timesbi.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Times_New_Roman/Times_New_Roman_Italic.ttf usual name is timesi.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Trebuchet_MS/Trebuchet_MS.ttf usual name is trebuc.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Trebuchet_MS/Trebuchet_MS_Bold.ttf usual name is trebucbd.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Trebuchet_MS/Trebuchet_MS_Bold_Italic.ttf usual name is trebucbi.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Trebuchet_MS/Trebuchet_MS_Italic.ttf usual name is trebucit.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Verdana/Verdana.ttf usual name is verdana.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Verdana/Verdana_Bold.ttf usual name is verdanab.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Verdana/Verdana_Bold_Italic.ttf usual name is verdanaz.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. library/tulip-ogl/bitmaps/fonts/Verdana/Verdana_Italic.ttf usual name is verdanai.ttf. The EULA does not allow modification, reverse engineering etc. See also http://bugs.debian.org/298545#29. Bastien -- To UNSUBSCRIBE, email to de
Bug#722540: Ping: CVE-2013-4289 CVE-2013-4290
Hi. Is there any progress on this bug? This grave issue is now open for three months. cu AW -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (a...@linux.de) signature.asc Description: Digital signature
Bug#726578: Ping: pwgen: Multiple vulnerabilities in passwords generation
Hi! This grave problem is now open for more than two months. Is there any plan to resolve this? cu AW -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (a...@linux.de) signature.asc Description: Digital signature
Bug#735122: backintime: Missing Dependencies and Package
Source: backintime Version: 1.0.34-0.1 Severity: normal Some dependencies are missing in debian/control: backintime-common: add to Depends:openssh-client, python-keyring add to Recommends: powermgmt-base, sshfs, encfs backintime-gnome: add to Depends:backintime-notify (>= ${source:Version}) add to Recommends: python-gnomekeyring backintime-kde: add to Depends:backintime-notify (>= ${source:Version}) add to Recommends: kompare, python-keyring-kwallet Package 'backintime-notify' is missing completely. Please take a look at 'notify' in src tarball. Depends: libnotify-bin, backintime-common (>= ${source:Version}) Regards, Germar, BIT dev-team -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735120: [postfix-cluebringer] Non free file
Package: postfix-cluebringer Severity: serious X-debug-cc: ftpmas...@ftp-master.debian.org The following file are non free webui/images/valid-css2.png usual name is valid-css2.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons. webui/images/valid-xhtml10.png usual name is valid-xhtml10.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons. Please remove Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735092: flash-kernel: add Raspberry Pi support
On Sun, 2014-01-12 at 21:16 +0100, Karsten Merker wrote: > On Sun, Jan 12, 2014 at 07:01:36PM +, Ian Campbell wrote: > > On Sun, 2014-01-12 at 19:24 +0100, Karsten Merker wrote: > > > On Sun, Jan 12, 2014 at 06:00:24PM +, Ben Hutchings wrote: > > > > On Sun, 2014-01-12 at 18:34 +0100, Karsten Merker wrote: > > > > > > > > The attached patch adds Raspberry Pi support to flash-kernel. > > > [SNIP] > > > > So the boot partition is mounted at /boot? Doesn't that make it > > > > impossible to install packaged kernels (as dpkg needs to create hard > > > > links)? > > > > > > Installing a kernel package (locally built using make-kpkg) with > > > a VFAT /boot does not show any problems here: > > > > The normal way of dealing with this is to not have the bootloader > > partition mounted on boot, this is described in flash-kernel via the > > Boot-Device field. I think this should be honoured for Rpi too. > > Rpi-ConfigTxt-Path would then be relative to this device. > > Having the vfat boot partition as /boot is the standard way in > Raspbian (Debian/armhf rebuild for the Pi/armv6, "official" OS > distribution for the Pi) and is described this way in all user > documentation for the Pi. This is also expected by other > software, in particular the firmware update mechanism, which > expects the firmware image to be at > /boot/bootcode.bin, as well as by the Raspberry Pi foundation's > kernel updates (which do not come as a Debian kernel package). Then I'm not sure what the point of this change is. Unpackaged kernel updates, aside from being generally a Bad Thing, presumably won't automatically call flash-kernel. > Not mounting the vfat boot partition at /boot would of course be > technically possible, but nobody actually does that on a Pi > and it would pose several problems: > > - The firmware update mechanism would have to be changed. This is > outside the scope of Debian and as installing firmware updates > is something that happens rather frequently on the Pi, that > must work without problems. ln -s boot/bootcode.bin /boot/bootcode.bin ? > - All the Pi user documentation would have to be changed, which > is also outside the scope of Debian. > > - In case the vfat boot partition is not mounted at /boot, > the firmware cannot anymore directly boot the /boot/vmlinuz-* > and /boot/initrd.img-* files from the kernel package. > That would therefore require copying the files from /boot > to the actual vfat boot partition. > > As having the vfat boot partition mounted on /boot is the > actual default case, flash-kernel would have to handle this as > well. This means either special handling depending on whether > the vfat partition is at /boot or not, or generally copying the > kernel to the vfat partition under another name. This sounds fairly easy to do and a sensible way to handle the transition. > The latter > would in the case vfat-at-/boot result in having the kernel and > initrd twice on the already quite small system vfat partition, > which is a route I would like to avoid. > > All things taken together I think that we should simply > accept that the vfat boot partition gets mounted at /boot > on the Pi and use it this way. There is obvious precedent for systems with firmware that boots from a VFAT partition. On EFI systems, starting with ia64 around 10 years ago, GNU/Linux usually mounts the firmware-supported boot partition at /boot/efi rather than /boot. Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#691576: GDB still broken with 3.11.10-1
On Sun, 2014-01-12 at 21:16 +0100, Émeric MASCHINO wrote: > 2014/1/12 Ben Hutchings : > > > > So this is a crash, not an incompatibility with the newer systemd. > > [...] > > > Can you test the 3.2 kernel with sysvinit, in case this is a bug that's > > specifically provoked by systemd? > > That's why I was saying "too old for my current Debian install" on Jan 6th. > > Since I'm running GNOME 3.8, do you think I can safely reinstall and > reboot with sysvinit or everything will be badly broken? You can have sysvinit and systemd installed in parallel and then use the 'init' kernel parameter to switch between them. Only systemd-sysv conflicts/replaces sysvinit. I don't know whether current gdm will work correctly under sysvinit but you can at least test that you can boot that system and log in on a text console. Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#729540: closed by Bernd Zeimetz
Jim, it looks like you're trying to build a modified package, not Bernd's package - is that correct? There are two issues I can see: - your CFLAGS don't seem to include -Wno-deprecated-declarations, without which the build will fail because GCC will treat the warnings as errors. Now, granted, those warnings could be patched away by using some explicit casts, but I'd rather not mask some possible subtle bugs that way - you seem to be compiling with GCC 4.8. This package will not build with 4.8 anytime soon, unfortunately, unless upstream migrates to 4.8+ as well Both issues have been dealth with both in my package and in Bernd's, are you absolutely sure you're using the correct one? Mihai
Bug#735119: [icedove] Non free file
Package: icedove Severity: serious X-Debbugs-CC: ftpmas...@ftp-master.debian.org According to lintian: mozilla/build/pgo/blueprint/valid.png usual name is valid-html401-blue.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons. Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732937: dpkg: fails somewhat regularly on kfreebsd-amd64
On 20:05, Steven Chamberlain wrote: > I think this is the interesting part: Something interesting happened before that, too. I was trying to update the 'gzip' package: 2014-01-12 19:57:56 status unpacked gzip:kfreebsd-amd64 1.6-3 2014-01-12 19:57:57 status half-configured gzip:kfreebsd-amd64 1.6-3 2014-01-12 19:57:58 status installed gzip:kfreebsd-amd64 1.6-3 but dpkg had a problem with stdout prior to that: 6637 dpkg CALL open(0x758980,0,0) 6637 dpkg NAMI "/var/lib/dpkg/diversions" 6637 dpkg RET open 7 6637 dpkg CALL fcntl(0x7,,0) 6637 dpkg RET fcntl 0 6637 dpkg CALL fcntl(0x7,,FD_CLOEXEC) 6637 dpkg RET fcntl 0 6637 dpkg CALL fstat(0x7,0x7fffcbd0) 6637 dpkg STRU invalid record 6637 dpkg RET fstat 0 6637 dpkg CALL mmap(0,0x4000,0x3,0x1002,0x,0) 6637 dpkg RET mmap 34368126976/0x80080 6637 dpkg CALL read(0x7,0x80080,0x4000) 6637 dpkg GIO fd 7 read 417 bytes [...] 6637 dpkg RET read 417/0x1a1 6637 dpkg CALL read(0x7,0x80080,0x4000) 6637 dpkg GIO fd 7 read 0 bytes "" 6637 dpkg RET read 0 6637 dpkg CALL break(0x9b4000) 6637 dpkg RET break 0 6637 dpkg CALL write(0x1,0x7fffaaf0,0x1c) 6637 dpkg RET write -1 errno 6 No such device or address and an error message about this subsequently fails to go to stderr: 6637 dpkg CALL fcntl(0x5,,0x753e20) 6637 dpkg RET fcntl 1 6637 dpkg CALL fcntl(0x5,,FD_CLOEXEC) 6637 dpkg RET fcntl 0 6637 dpkg CALL fcntl(0x5,,0xd120) 6637 dpkg RET fcntl 0 6637 dpkg CALL stat(0x753e20,0x7fffd0d0) 6637 dpkg NAMI "/var/lib/dpkg/triggers/Unincorp" 6637 dpkg STRU invalid record 6637 dpkg RET stat 0 6637 dpkg CALL fcntl(0x5,,0xd110) 6637 dpkg RET fcntl 0 6637 dpkg CALL open(0x753d80,0,0) 6637 dpkg NAMI "/usr/share/locale/en_GB/LC_MESSAGES/libc.mo" 6637 dpkg RET open -1 errno 2 No such file or directory 6637 dpkg CALL open(0x7681d0,0,0) 6637 dpkg NAMI "/usr/share/locale/en/LC_MESSAGES/libc.mo" 6637 dpkg RET open -1 errno 2 No such file or directory 6637 dpkg CALL write(0x2,0x7fffa560,0x6c) 6637 dpkg RET write -1 errno 6 No such device or address 6637 dpkg CALL write(0x2,0x800bb70a3,0x1) 6637 dpkg RET write -1 errno 6 No such device or address 6637 dpkg CALL write(0x10,0x75b500,0x57) 6637 dpkg GIO fd 16 wrote 87 bytes "status: gzip : error : error writing to '': No such file or directory " 6637 dpkg RET write 87/0x57 6637 dpkg CALL open(0x75b6a0,0x601,0x1b6<>438) 6637 dpkg NAMI "/var/lib/dpkg/status-new" 6637 dpkg RET open 8 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735118: nmu: gvfs_1.18.2-2
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: binnmu Hi, gphoto2 in unsable has an annoying bug where the gvfs gphoto2 backends segfaults (this is #625872). This bug is apparently fixed in gphoto 2.5 (in experimental) but apparently requires also gvfs to be rebuilt against gphoto2 2.5 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625872#31). Would it be possible to rebuild the gvfs version in experimental against the fixed gphoto2? nmu gvfs_1.18.2-2 . ALL . -m "Rebuild against gphoto2 2.5" Thanks in advance, -- Yves-Alexis -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (450, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735092: flash-kernel: add Raspberry Pi support
On Sun, Jan 12, 2014 at 07:32:56PM +, Ben Hutchings wrote: > On Sun, 2014-01-12 at 19:24 +0100, Karsten Merker wrote: > > On Sun, Jan 12, 2014 at 06:00:24PM +, Ben Hutchings wrote: > > > So the boot partition is mounted at /boot? Doesn't that make it > > > impossible to install packaged kernels (as dpkg needs to create hard > > > links)? > > > > Installing a kernel package (locally built using make-kpkg) with > > a VFAT /boot does not show any problems here: > [...] > > Please also test upgrading (or simply reinstalling the same package > again). Indeed, reinstalling fails: dpkg: error processing linux-image-3.12.6-rpi+_2014010201_armhf.deb (--install): unable to make backup link of `./boot/vmlinuz-3.12.6-rpi+' before installing new version: Operation not permitted Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691576: GDB still broken with 3.11.10-1
2014/1/12 Ben Hutchings : > > So this is a crash, not an incompatibility with the newer systemd. [...] > Can you test the 3.2 kernel with sysvinit, in case this is a bug that's > specifically provoked by systemd? That's why I was saying "too old for my current Debian install" on Jan 6th. Since I'm running GNOME 3.8, do you think I can safely reinstall and reboot with sysvinit or everything will be badly broken? Émeric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735092: flash-kernel: add Raspberry Pi support
On Sun, Jan 12, 2014 at 07:01:36PM +, Ian Campbell wrote: > On Sun, 2014-01-12 at 19:24 +0100, Karsten Merker wrote: > > On Sun, Jan 12, 2014 at 06:00:24PM +, Ben Hutchings wrote: > > > On Sun, 2014-01-12 at 18:34 +0100, Karsten Merker wrote: > > > > > > The attached patch adds Raspberry Pi support to flash-kernel. > > [SNIP] > > > So the boot partition is mounted at /boot? Doesn't that make it > > > impossible to install packaged kernels (as dpkg needs to create hard > > > links)? > > > > Installing a kernel package (locally built using make-kpkg) with > > a VFAT /boot does not show any problems here: > > The normal way of dealing with this is to not have the bootloader > partition mounted on boot, this is described in flash-kernel via the > Boot-Device field. I think this should be honoured for Rpi too. > Rpi-ConfigTxt-Path would then be relative to this device. Having the vfat boot partition as /boot is the standard way in Raspbian (Debian/armhf rebuild for the Pi/armv6, "official" OS distribution for the Pi) and is described this way in all user documentation for the Pi. This is also expected by other software, in particular the firmware update mechanism, which expects the firmware image to be at /boot/bootcode.bin, as well as by the Raspberry Pi foundation's kernel updates (which do not come as a Debian kernel package). Not mounting the vfat boot partition at /boot would of course be technically possible, but nobody actually does that on a Pi and it would pose several problems: - The firmware update mechanism would have to be changed. This is outside the scope of Debian and as installing firmware updates is something that happens rather frequently on the Pi, that must work without problems. - All the Pi user documentation would have to be changed, which is also outside the scope of Debian. - In case the vfat boot partition is not mounted at /boot, the firmware cannot anymore directly boot the /boot/vmlinuz-* and /boot/initrd.img-* files from the kernel package. That would therefore require copying the files from /boot to the actual vfat boot partition. As having the vfat boot partition mounted on /boot is the actual default case, flash-kernel would have to handle this as well. This means either special handling depending on whether the vfat partition is at /boot or not, or generally copying the kernel to the vfat partition under another name. The latter would in the case vfat-at-/boot result in having the kernel and initrd twice on the already quite small system vfat partition, which is a route I would like to avoid. All things taken together I think that we should simply accept that the vfat boot partition gets mounted at /boot on the Pi and use it this way. Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735105: libnss3: CVE-2013-1741 in wheezy
control: retitle 735105 CVE-2013-1741 and CVE-2013-5606 in wheezy Hi. The same applies to CVE-2013-5606. (Oops, I sent too fast.) cu AW -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (a...@linux.de) signature.asc Description: Digital signature
Bug#588177: goocanvas: New upstream release 1.9.0
On Mon, Jan 13, 2014 at 12:01:50AM +0900, Hideki Yamane wrote: > > Thanks for taking the effort to prepare this, but I think I also > > need the gobject-introspection package. I can try to add it on top > > of your work one of these days. > > Probably done it :) (I haven't fix all lintian warning, but anyway...) > Please get and check it. I think the .typelib files should go into their own gir1.2 package and the .gir files into the -dev package, e.g.: http://packages.debian.org/sid/amd64/gir1.2-anjuta-3.0/filelist http://packages.debian.org/sid/amd64/libanjuta-dev/filelist Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702762: "More or less" dead upstream
On Sun, Jan 12, 2014 at 12:25 PM, Bálint Réczey wrote: > 2014/1/12 Reinhard Tartler : >> On Sat, Jan 11, 2014 at 2:51 PM, Bálint Réczey >> wrote: >> >>> From the email [1] on the VLC list I had the impression that >>> libpostproc is broken. >> >> That is my understanding as well. That's why I wanted to hear from you >> XBMC needs libpostproc for. Did you notice any visual improvements >> from enabling the libpostproc filter in XBMC? > Now I have tried it and the results look pretty good on Jessie. > The postprocessing option is visible when playing the video. > > Please keep the package and I think this bug could be closed. > Maybe #729332 could be fixed as well. ;-) Oh, indeed, I'll have a look at that shortly. >>> So if libpostproc will stay with us could you please upload it to >>> wheezy-backports to let me upload xbmc, too? >> >> Is this really necessary? What's the problem with the libpostproc-dev >> package provided by libav 0.8 in stable? >> >> http://packages.debian.org/wheezy/libpostproc-dev > It depends on libavutil-dev, but XBMC needs newer libavutil-dev: > $ sudo apt-get install libpostproc-dev > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libpostproc-dev : Depends: libavutil-dev (= 6:0.8.9-1) but > 6:9.10-1~bpo70+1 is to be installed > E: Unable to correct problems, you have held broken packages. Oh I see. The dependencies are overly strict in stable. Well, since fixing the dependencies in stable is hard and takes lots of time, I guess you're right and we should have a backported libpostproc in stable. I'll have a look at that. Thanks for your help identifying the problem and working on the xbmc backport! -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732956: [debian-reference-en] "The apt-get and apt-cache commands are the most basic package management tool."
Hi Osamu, On 2014-01-06 09:29, Osamu Aoki wrote: control: tags 732956 pending Hi, On Sun, Dec 22, 2013 at 09:52:03PM -0500, Filipus Klutiero wrote: Package: debian-reference-en Version: 2.53 Severity: minor Section 2.2.1. |apt-get| / |apt-cache| vs. |aptitude| contains: The |apt-get| and |apt-cache| commands are the most *basic* package management tool. The subject is plural while "the most *basic* package management tool" is singular. Yes. Besides, I'd say Debian's most basic package management tool is dpkg. I would suggest removing this sentence. Not really in this intended context. It is focused on APT. By the way, one item reads: apt-get offers a robust and stable package resolver which uses the common package state data. I do not see the point of discussing common package state data here. "apt-get offers a robust and stable package resolver." would be sufficient (I would even drop one of "robust" or "stable", which seem redundant). There were some reasons why I did this but you have a point. So I updated pertinent section in the source as: `apt-get` / `apt-cache` vs. `aptitude` NOTE: The package dependency resolver of the `aptitude` command tends to suggest mass package removals when packages in `unstable` are temporarily inconsistent. This situation is a bit frightening. Usually, "`apt-get dist-upgrade`" should resolve this situation. This situation seems to be caused mostly by the version skew among packages depended or recommended by a meta-package such as `gnome-core`. The `apt-get` and `apt-cache` commands are the most **basic** APT-based package management tools. - `apt-get` and `apt-cache` offer only the commandline user interface. - `apt-get` is most suitable for the **major system upgrade** between releases, etc. - `apt-get` offers a **robust** package dependency resolver. - `apt-get` is less demanding on hardware resources. It consumes less memory and runs faster. - `apt-cache` offers a **standard** regex based search on the package name and description. - `apt-get` and `apt-cache` can manage multiple versions of packages using `/etc/apt/preferences` but it is quite cumbersome. The `aptitude` command is the most **versatile** APT-based package management tool. - `aptitude` offers the fullscreen interactive text user interface. - `aptitude` offers the commandline user interface, too. - `aptitude` is most suitable for the **daily interactive package management** such as inspecting installed packages and searching available packages. - `aptitude` is more demanding on hardware resources. It consumes more memory and runs slower. - `aptitude` offers an **enhanced** regex based search on all of the package metadata. - `aptitude` can manage multiple versions of packages without using `/etc/apt/preferences` and it is quite intuitive. Thank you very much, your changes are perfect. By the way, reviewing the above made me notice the note at the top. Do we have a ticket on aptitude's issue? If not, should the reference really be targetted to people using unstable as a default suite anyway? -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733002: [debian-mysql] Bug#733002: mariadb-5.5: FTBFS w/bison 3.x
Thanks for your effort! However I do not intend to fix 5.5.32 anymore but upgrade to .35 which includes an upstream fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org