Bug#767161: With XBMC from debian sid.
sudo Apt-get install xbmc xbmc-bin -t sid ... sudo systemctl start xbmc less .xbmc/temp/xbmc.log.. 19:14:26 T:140388001949760 NOTICE: Starting XBMC from Debian (13.2 Debian package version:2:13.2+dfsg1-3). Platform: x86 Linux 64-bit 19:14:26 T:140388001949760 NOTICE: Using Debug XBMC x64 build, compiled Oct 24 2014 by GCC 4.9.1 for x86 Linux 64-bit 3.16.5 19:14:26 T:140388001949760 NOTICE: Running on Linux 64-bit (Debian GNU/Linux jessie/sid, 3.16-3-amd64 x86_64) 19:14:26 T:140388001949760 NOTICE: Host CPU: Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz, 4 cores available 19:14:26 T:140388001949760 NOTICE: special://xbmc/ is mapped to: /usr/share/xbmc 19:14:26 T:140388001949760 NOTICE: special://xbmcbin/ is mapped to: /usr/lib/xbmc 19:14:26 T:140388001949760 NOTICE: special://masterprofile/ is mapped to: /home/karl/.xbmc/userdata 19:14:26 T:140388001949760 NOTICE: special://home/ is mapped to: /home/karl/.xbmc 19:14:26 T:140388001949760 NOTICE: special://temp/ is mapped to: /home/karl/.xbmc/temp 19:14:26 T:140388001949760 NOTICE: The executable running is: /usr/lib/xbmc/xbmc.bin 19:14:26 T:140388001949760 NOTICE: Local hostname: server 19:14:26 T:140388001949760 NOTICE: Log File is located: /home/karl/.xbmc/temp/xbmc.log 19:14:26 T:140388001949760 NOTICE: --- 19:14:26 T:140388001949760INFO: Selected UPower as PowerSyscall 19:14:26 T:140388001949760 ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property CanSuspend 19:14:26 T:140388001949760 ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property CanHibernate - Suspend and Hibernate are not showing in XBMC menu. If remove UPower reboot/shutdown disappears. If remove consolekit or polkit (or the custom rules) reboot/shutdown disappear too. Process 1 is systemd. Thanks for your work on it. Great to have XBMC back in Debian.
Bug#767193: mbt: 3.2.10-5 must not be in jessie
Package: mbt Version: 3.2.10-5 Severity: serious This package of mbt should not be in jessie: a library transition in the mbt/timbl/dimbl/frog/libfolia/ticcutils/ucto - suite is upcoming. This transition will take place in unstable; transitioned packages are targeted for zurg. There is no time for proper testing before the freeze of jessie. Thanks, Bye, Joost On Tue, Oct 28, 2014 at 11:04:32PM +, Debian FTP Masters wrote: Accepted: Source: mbt Binary: mbt libmbt1-dev libmbt1 Architecture: source amd64 Version: 3.2.10-5 Distribution: unstable Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Joost van Baal-Ilić joos...@debian.org Description: libmbt1- memory-based tagger-generator and tagger - runtime libmbt1-dev - memory-based tagger-generator and tagger - development mbt- memory-based tagger-generator and tagger Changes: mbt (3.2.10-5) unstable; urgency=low . * debian/control: migrated version control from Subversion to git (still on Debian's Alioth). * debian/*: change version control tags from Subversion to git. * debian/watch: more strict. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766708: Request to override gcc maintainer changes breaking unsupported way of cross-building
Matthias contended that the default method to build a gcc cross compiler works with multiarch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766708#73 On Sun, Oct 26, 2014 at 03:50:59PM +0100, Helmut Grohne wrote: Why is with_deps_on_target_arch_pkgs needed? Without this flag, gcc emits dependencies on libc*-$arch-cross. In order to satisfy these dependencies binary packages from glibc have to be repacked and renamed. When using the resulting cross toolchain to build further Debian packages there are two choices, both of which are bad: * Newly cross built packages also depend on libc6-$arch-cross. This will make them different from natively built packages and in particular makes debootstrap fail. * Newly cross built packages keep their dependency on libc6. This will make them uninstallable in the build chroot, because there is no foreign arch libc package that can be co-installed with the aforementioned libc*-$arch-cross. Either option makes the bootstrap of a new architecture fail. I do not immediately see where this rationale is flawed, but I cannot reproduce his claim: When building with the default method, the resulting packages are uninstallable, because libc6-$arch-cross is not available in the archive and not built from any source package. Thus the default method relies on out-of-archive code whereas the unsupported with_deps_on_target_arch_pkgs method does not. It looks like this issue should be addressed in a package different from gcc, but to date this hasn't happened. So it may be wise to ignore the quoted reasoning (on the grounds that it cannot be verified), because the code that makes it work has not yet arrived. This actually was the primary reason for me to start using with_deps_on_target_arch_pkgs when learning about cross compilation: I couldn't figure out where to obtain these libc*-$arch-cross packages, but when I just set that flag I wouldn't have to. I therefore argue that getting the relevant support into the glibc package could be a resolution of the complaint made to the ctte, but now we're stepping on entirely different toes. (Again this seems to be a timing thing, as Matthias and Adam Conrad are apparently working on this.) Why is DEB_CROSS_NO_BIARCH needed? There currently is a bug in rebootstrap that makes building multilib enabled cross-toolchains fail. Thus far I failed to figure out the reasons for this failure (beyond knowing that gcc looks for crti.o in the wrong directory). So in the spirit of having something working rather than nothing, this fiddle is needed to bootstrap multilib-enabled architectures now. I intend to eliminate the need DEB_CROSS_NO_BIARCH. Note that this need might be a consequence of using with_deps_on_target_arch_pkgs=yes and might be unneeded with the supported default method. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767194: util-linux upgrade synchronously starts fstrim multiple times
Package: util-linux Severity: important Version: 2.25.2-2 Upgrading util-linux to current version hangs a very long time (I waited some 10 mintues). I noticed that fstrim was running, which is apparently started by this autogenerated snippet in postinst: # Automatically added by dh_systemd_start if [ -d /run/systemd/system ]; then systemctl --system daemon-reload /dev/null || true deb-systemd-invoke start fstrim.service fstrim.timer /dev/null || true fi Even worse, as postinst doesn't check $1 this happens multiple times, each time update-initramfs gets triggered. IMHO this is undesired. fstrim ought to run in the background and not block the whole upgrade. So this probably needs some --no-start dh_installinit argument in debian/rules? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#767150: exaile: The Collection view is not updated automatically when the collection is rescanned
Control: tag -1 + moreinfo Hi Lars, On Tue, Oct 28, 2014 at 11:45 AM, Lars Luthman deb-b...@larsluthman.net wrote: Package: exaile Version: 0.3.2.2-3 Severity: normal Dear Maintainer, When adding new music files (e.g. a directory of MP3 files) in the directory used for the Exaile collection and choosing 'Rescan collection' from the 'Tools' menu, the Collection view is not updated automatically to show the newly found tracks. Changing the search terms in the collection view will not make the new tracks appear, but changing the type of view in the dropdown menu (Year - Artist, Artist - (Year - Album) etc) will. I would expect the new tracks to show up in the Collection view when they are discovered by the scan, without having to touch any of the controls. Is this bug still reproducible for you with the version of exaile in wheezy-backports (3.4.0.2; instructions on how to enable backports can be found at [1])? If so, please report the bug upstream [2]. Regards, Vincent [1] http://backports.debian.org/Instructions/ [2] https://github.com/exaile-dev/exaile/issues/new -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767109: nvidia-driver: fs-uae (Amiga Emulator) segfault with nvidia-driver installed on Jessi
Hello On Wed, 29 Oct 2014 03:44:43 +0100 Andreas Beckmann a...@debian.org wrote: Did you try the 343.22 driver from experimental? No, not yet. #0 __memmove_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:1785 #1 0x727c9d77 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.340.24 This is an upstream bug. Probably using memcpy() for overlapping arguments. memmove() must be used in this case. Please report this directly to NVIDIA: On the Upstreamwebsite i found a workaround: __GL_WRITE_TEXT_SECTION=0 fs-uae I have no clue what this variable makes, but it works. Maybe it helps to find the bug? Kind regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767195: live-boot: Encrypted persistence not possible at boot time
Package: live-boot
Version: 4.0.1-1
Severity: important
Tags: d-i
Dear Maintainer,
I tried a while getting a live system working with encrypted persistence on
boot time. When doing
live-persistence activate /dev/sdx2
it ask for password and setup the encryption, thats ok. But boot time
persistence works only for unencrypted storage.
Snippet from boot.log of live-boot:
+ LIVE_BOOT_CMDLINE=BOOT_IMAGE=/live/vmlinuz boot=live noeject keyboard-
layouts=de components persistence persistence-encryption=luks,none
initrd=/live/initrd.img debug=true
+ Cmdline_old
+ PERSISTENCE=true
+ export PERSISTENCE
+ PERSISTENCE_ENCRYPTION=luks,none
+ export PERSISTENCE_ENCRYPTION
+ [ -z ]
+ [ = /dev/nfs ]
+ [ = /dev/cifs ]
+ [ -z ]
+ MODULE=filesystem
+ export MODULE
+ [ -z ]
+ UNIONTYPE=aufs
+ export UNIONTYPE
+ [ -z luks,none ]
+ is_in_comma_sep_list luks luks,none
+ local element
+ element=luks
+ shift
+ is_in_list_separator_helper , luks luks,none
+ local sep element list
+ sep=,
+ shift
+ element=luks
+ shift
+ list=luks,none
+ echo luks,none
+ grep -qe ^\(.*,\)\?luks\(,.*\)\?$
+ modprobe dm-crypt
+ [ ! -x /lib/cryptsetup/askpass ]
+ log_warning_msg cryptsetup is unavailable
+ _log_msg Warning: cryptsetup is unavailable\n
+ [ n = y ]
+ printf Warning: cryptsetup is unavailable\n
Warning: cryptsetup is unavailable
As you can see, /lib/cryptsetup/askpass isn't executable (but installed via
package list as described in your documentation)
The configuration last used is
lb config noauto\
--apt apt\
--bootstrap debootstrap\
--binary-images iso-hybrid \
--distribution testing\
--mirror-bootstrap http://ftp.debian.de/debian/ \
--mirror-binary http://ftp.debian.de/debian/ \
--memtest memtest86+ \
--mode debian\
--linux-packages linux-image linux-headers \
--system live\
--debian-installer false\
--bootappend-live boot=live noeject keyboard-layouts=de components
persistence persistence-encryption=luks,none\
--archive-areas main contrib non-free\
--apt-options --force-yes --yes\
--debconf-frontend dialog\
--firmware-binary true\
--firmware-chroot true\
${@}
and tried it with --binary-images hdd and a lot of other options, but nothing
works. Could not execute askpass at boot time. No idea, whats going wrong here.
It should work without any hard research, encrypted live systems are essential
for sysadmins (and others). I don't know if it would work with wheezy 'cause I
didn't try it (I require the newer kernel in jessie).
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages live-boot depends on:
ii live-boot-initramfs-tools [live-boot-backend] 4.0.1-1
Versions of packages live-boot recommends:
ii live-boot-doc 4.0.1-1
ii live-tools 4.0.1-1
ii rsync 3.1.1-2
ii uuid-runtime 2.25.1-5
Versions of packages live-boot suggests:
ii cryptsetup2:1.6.6-2
pn curlftpfs none
pn httpfs2 none
pn unionfs-fuse none
ii wget 1.15-1+b1
+ tailpid=123
+ tail -f boot.log
+ cat /proc/cmdline
+ LIVE_BOOT_CMDLINE=BOOT_IMAGE=/live/vmlinuz boot=live noeject
keyboard-layouts=de components persistence persistence-encryption=luks,none
initrd=/live/initrd.img debug=true
+ Cmdline_old
+ PERSISTENCE=true
+ export PERSISTENCE
+ PERSISTENCE_ENCRYPTION=luks,none
+ export PERSISTENCE_ENCRYPTION
+ [ -z ]
+ [ = /dev/nfs ]
+ [ = /dev/cifs ]
+ [ -z ]
+ MODULE=filesystem
+ export MODULE
+ [ -z ]
+ UNIONTYPE=aufs
+ export UNIONTYPE
+ [ -z luks,none ]
+ is_in_comma_sep_list luks luks,none
+ local element
+ element=luks
+ shift
+ is_in_list_separator_helper , luks luks,none
+ local sep element list
+ sep=,
+ shift
+ element=luks
+ shift
+ list=luks,none
+ echo luks,none
+ grep -qe ^\(.*,\)\?luks\(,.*\)\?$
+ modprobe dm-crypt
+ [ ! -x /lib/cryptsetup/askpass ]
+ log_warning_msg cryptsetup is unavailable
+ _log_msg Warning: cryptsetup is unavailable\n
+ [ n = y ]
+ printf Warning: cryptsetup is unavailable\n
Warning: cryptsetup is unavailable
+ echo luks,none
+ sed -e s/\luks,\|,\?luks$//g
+ PERSISTENCE_ENCRYPTION=none
+ export PERSISTENCE_ENCRYPTION
+ [ -z ]
+ PERSISTENCE_METHOD=overlay
+ export PERSISTENCE_METHOD
+ [ -z ]
+ PERSISTENCE_STORAGE=filesystem,file
+ export PERSISTENCE_STORAGE
+ Debug
+ return 0
+ Read_only
+ return 0
+ Select_eth_device
+ egrep ^BOOT= /conf/initramfs.conf
+ tail -1
+ bootconf=
+ [ != BOOT=nfs ]
+ [ -z ]
+ [ -z ]
+ [ -z ]
+ [ -z ]
+ return
+ [ -e /conf/param.conf ]
+ [ ! -z ]
+ [ ! -z ]
+ [ ! -z ]
+ [ ! -z ]
+ [ -n ]
+ [ -n ]
+ [ -x /usr/bin/memdiskfind ]
+ i=0
+ [ 0 -lt 60 ]
+ find_livefs 0
+ timeout=0
+ [ -n ]
+ [ ! -z ]
+ removable_dev sys
+
Bug#767196: Not installable on systems with grub-legacy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: vmdebootstrap Version: 0.4-3 Severity: important The new package is not installable in a clean way as it pulls in grub2-common (what removes grub-legacy). So after that the system using legacy grub for some valid reason would not boot anymore. I have to stick with 0.3-1 at the moment and have to be really careful to not accidentally upgrade that part. - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (800, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.1 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Versions of packages vmdebootstrap depends on: ii debootstrap1.0.64 ii extlinux 3:6.03+dfsg-2 ii kpartx 0.5.0-5 ii parted 3.2-6 ii python-cliapp 1.20140719-1 pn python:any none ii qemu-utils 2.1+dfsg-5+b1 Versions of packages vmdebootstrap recommends: ii qemu-system 2.1+dfsg-5+b1 pn qemu-user-static none ii squashfs-tools1:4.2+20130409-2 vmdebootstrap suggests no packages. - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJUUJjlAAoJEKZ8CrGAGfasw+IMAKUsotEt+N2VGnDV5pURGPX/ bx9pdxmp8VS74T0hAFZoC1rxrufMR/HXdP9/yex6rR/wAQnnNPCXR1F+Or5luyUZ iLnCfhyEdC36DE5Y+4MCF3Q2h676V/zbNLhAC8/gWGfHQdFllbvZczHhQHSfAPe/ iYibjZmEHcoqET7mquXHAwcQArpZOOTMnxzhRNK3DMKzgDqlREjQdpt138ET1MJl SPHrshW194oHYeJ/5IR4u1oVo3Q0+eJsm0XCF9Rk7HPaIyINC7jDGvMpXyJ0KSmn SMxe+nHiTLD8ECkhZ4DGkzjeU75zWY9jszfc0gBzWkvyxVHb4tlSE6KTKj2l5IBB Nu99AXCVL2P/jevQEjF3+1vkt5UitSX904QDV/yq0mlrU8KZiSM0b2bsxOqDB+wl usk6af3Zomw/f3HElp0ngOIgki8D5PNYAlQCb/0rD6vTSeUTVAIbskzAhvqO0V/+ nDyfY+zoueXgpGwRXxtw5JjPPeIVUQZIfqCbDrP+Mw== =C75h -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766039: please document debug-shell.service in README.Debian
Control: tag -1 pending Hello all, I now created a first version in README: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=a635f431aff Amendments/corrections appreciated, of course! Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767197: debtags update --local fails
Package: debtags
Version: 1.12.3
Severity: normal
Hi,
debtags update --local exits with a non‐zero exit code, which causes
update and installation of the package fails:
# agi debtags
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Vorgeschlagene Pakete:
tagcoll
Die folgenden NEUEN Pakete werden installiert:
debtags
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 6 nicht aktualisiert.
Es müssen noch 0 B von 614 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 910 kB Plattenplatz zusätzlich benutzt.
etcgit: Updating configuration files in branch master...done.
etcgit: Merging new configuration files into branch local_config...done.
Vormals nicht ausgewähltes Paket debtags wird gewählt.
(Lese Datenbank ... 280914 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../debtags_1.12.3_amd64.deb ...
Entpacken von debtags (1.12.3) ...
Trigger für man-db (2.7.0.2-2) werden verarbeitet ...
debtags (1.12.3) wird eingerichtet ...
No such file or directory. Context:
writing item
dpkg: Fehler beim Bearbeiten des Paketes debtags (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
debtags
etcgit: seems installation broke; don't capturing current state of /etc
mount: / is busy
[ Rootkit Hunter version 1.4.2 ]
Looking with strace what's happening I see this:
14217 23:46:54.957741 open(/usr/share/debtags/vocabulary, O_RDONLY) = 3
0.21
14217 23:46:54.957819 fstat(3, {st_dev=makedev(8, 1), st_ino=5154,
st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=136, st_size=65984, st_atime=2014/10/14-23:44:03,
st_mtime=2014/10/05-22:27:21, st_ctime=2014/10/14-23:44:04}) = 0 0.12
14217 23:46:54.957890 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2ac49675 0.24
14217 23:46:54.957947 read(3, Facet: accessibility\nStatus: nee..., 4096) =
4096 0.22
14217 23:46:54.958596 read(3, gali\n\nTag: culture::bokmaal\nDesc..., 4096) =
4096 0.14
14217 23:46:54.959395 read(3, g: devel::lang:haskell\nDescripti..., 4096) =
4096 0.16
14217 23:46:54.960029 read(3, cs\n\nTag: field::medicine\nDescrip..., 4096) =
4096 0.001314
14217 23:46:54.962280 read(3, s lacking.\n\n\nFacet: made-of\nStat..., 4096)
= 4096 0.001124
14217 23:46:54.963746 brk(0x2b44000)= 0x2b44000 0.19
14217 23:46:54.964264 read(3, o signal the vocabulary maintain..., 4096) =
4096 0.16
14217 23:46:54.964956 read(3, n be categorised along this face..., 4096) =
4096 0.000886
14217 23:46:54.966861 read(3, here the current tag set is lack..., 4096) =
4096 0.54
14217 23:46:54.968664 read(3, e package can be categorised alo..., 4096) =
4096 0.23
14217 23:46:54.969358 read(3, \nDescription: Roxen\n\nTag: suite:..., 4096) =
4096 0.001169
14217 23:46:54.971041 read(3, sually carried\n out over the tel..., 4096) =
4096 0.17
14217 23:46:54.971460 read(3, Link: http://www.ipv6.org/\n\nTag:;..., 4096) =
4096 0.001109
14217 23:46:54.973012 read(3, e only intermittent connection t..., 4096) =
4096 0.17
14217 23:46:54.973332 read(3, emote logins.\n .\n Link: http://e;..., 4096) =
4096 0.001392
14217 23:46:54.975024 brk(0x2b65000)= 0x2b65000 0.19
14217 23:46:54.975319 read(3, facet, but the right tag for it ..., 4096) =
4096 0.16
14217 23:46:54.976098 read(3, can be categorised along this f..., 4096) =
4096 0.001114
14217 23:46:54.978124 read(3, upport\nDescription: Limited scop..., 4096) =
448 0.001370
14217 23:46:54.979683 read(3, , 4096) = 0 0.13
14217 23:46:54.979785 stat(/root/.debtags, 0x7fff3d5723a0) = -1 ENOENT (No
such file or directory) 0.21
14217 23:46:54.979875 umask(022)= 022 0.12
14217 23:46:54.979940 open(/var/lib/debtags/vocabulary.aXjIgh,
O_RDWR|O_CREAT|O_EXCL, 0600) = 4 0.000121
14217 23:46:54.980101 umask(0) = 022 0.11
14217 23:46:54.980139 umask(022)= 0 0.10
14217 23:46:54.980182 fchmod(4, 0644) = 0 0.25
14217 23:46:54.980242 fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
0.12
14217 23:46:54.980293 fstat(4, {st_dev=makedev(8, 2), st_ino=8527365,
st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2014/10/14-23:46:54,
st_mtime=2014/10/14-23:46:54, st_ctime=2014/10/14-23:46:54}) = 0 0.13
14217 23:46:54.980360 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2ac496751000 0.22
14217 23:46:54.980419 lseek(4, 0, SEEK_CUR) = 0 0.001390
14217 23:46:54.982071 write(4, Facet: accessibility\nDescription..., 4096) =
4096 0.74
14217 23:46:54.982513 write(4, signal the vocabulary maintainer..., 4096) =
4096 0.000236
14217 23:46:54.983019 write(4, escription: C Development\n\nTag: ..., 4096) =
4096 0.30
14217 23:46:54.984650 write(4, nancial software\n\nTag:
Bug#767127: service thinkfan status
Hi, On 10/29/2014 03:43 AM, HJ wrote: the problem is that the script won't enable the fan control on the acpi module eg: a simple `echo options thinkpad_acpi fan_control=1 /etc/modprobe.d/thinkpad.conf` did the trick that, and a module reload, which is most probably impossible while the system is running as the module is in use by userspace, so a reboot is needed. this is why thinkfan does not enable fan_control=1 itself (and only documents it in README.Debian). that said, thinkfan should not start after install anyways, because there are no sane defaults and the owner of the machine should adjust the configuration before starting thinkfan. greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767173: gnome-shell: Display freezes but mouse stays operational
I think this is probably the same bug that happens whenever I right-click on the desktop. Using alt+f2 r to restart gnome-shell brings it back to normal. //Marcus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767198: unblock: sqlkit/0.9.6.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sqlkit It was removed from testing because of #725372, which is fixed in this version. Apart from that, it updates the sqlalchemy version supported, fixes some (unreported) bugs and adds documentation. unblock sqlkit/0.9.6.1-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.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#767145: Re: Bug#767145: autodocktools: fails to start the GUI
Sag mal, was ist eigentlich mit Deinem hhsuite upload Verpennt? Ich habe nichts gesehen. :- On Wed, Oct 29, 2014 at 01:03:04AM +0100, Steffen Möller wrote: Hi Andreas, hi Senthil, Over here I do even get that far - I run into the missing Python Image module - which I ment to have been fixed a long time ago. Also, everything attempts to install Tk8.5, not 8.6, so ... hm. I have to reserve one of the upcoming weekends, I am afraid. Cannot immediately jump at it, sorry. With some good luck it was just an upload that never happened. Will find out. Best, Steffen Gesendet: Dienstag, 28. Oktober 2014 um 21:06 Uhr Von: Andreas Tille andr...@an3as.eu An: Senthil Kumaran style...@gmail.com, 767...@bugs.debian.org Cc: Steffen Möller steffen_moel...@gmx.de Betreff: Re: Bug#767145: autodocktools: fails to start the GUI Hi Senthil, thanks for your bug report. I can confirm that I'm able to reproduce the problem here. A web search for the string TclError: cannot use geometry manager grid inside lead to sevral autodocktools / mgltools related hints. I tried to follow one of them[1] which at the bottom says: As the latest builds are bundling tcl and tk (which is version 8.5) we cannot test for compatibility with tcl/tk-8.6 and checked where tcl/tk is actually used. As far as I can see only the module mgltools-opengltk has a tcltk dependency. I tried building this with forcing 8.5 instead of Debian's default 8.6 and tried what might happen but the error remains. So I'm a bit clueless what to do now and I wonder whether Steffen who has way more insight into this software might think. Steffen, just tell me if you are interested in my patches for mgltools-opengltk which I did not commited since they do not solve the problem. Its basically deactivating tcllib.patch and fixing the Build-Dependency. Kind regards Andreas. [1] http://mgldev.scripps.edu/bugs/show_bug.cgi?id=1346 On Tue, Oct 28, 2014 at 11:24:59PM +0530, Senthil Kumaran wrote: Package: autodocktools Version: 1.5.7~rc1+cvs.20140424-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** After installing autodocktools via apt-get, trying to start it in a machine with GNOME desktop environment fails with the following error. Hence autodocktools GUI is unusable. snip stylesen@harshu:~$ autodocktools Run ADT from /usr/lib/python2.7/dist-packages/AutoDockTools Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/AutoDockTools/__init__.py, line 433, in runADT title=title, withShell= not interactive, verbose=False, gui=gui) File /usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py, line 1026, in __init__ trapExceptions=trapExceptions) File /usr/lib/python2.7/dist-packages/ViewerFramework/VF.py, line 387, in __init__ verbose=verbose) File /usr/lib/python2.7/dist-packages/ViewerFramework/VFGUI.py, line 444, in __init__ verbose=verbose,guiMaster=VIEWER_root,) File /usr/lib/python2.7/dist-packages/DejaVu/Viewer.py, line 586, in __init__ cnf=cnf, **kw) File /usr/lib/python2.7/dist-packages/DejaVu/Viewer.py, line 285, in AddCamera c = classCamera(master, screenName, self, num, cnf=cnf, **kw) File /usr/lib/python2.7/dist-packages/DejaVu/Camera.py, line 2189, in __init__ self.AddTrackball() File /usr/lib/python2.7/dist-packages/DejaVu/Camera.py, line 2583, in AddTrackball self.trackball = Trackball(self, size, rscale, tscale, sscale, renorm ) File /usr/lib/python2.7/dist-packages/DejaVu/Trackball.py, line 88, in __init__ self.createSpinGui() File /usr/lib/python2.7/dist-packages/DejaVu/Trackball.py, line 726, in createSpinGui callback=self.setWithSpinGui, File /usr/lib/python2.7/dist- packages/mglutil/gui/BasicWidgets/Tk/vector3DGUI.py, line 90, in __init__ self.createEntries(self.frame) File /usr/lib/python2.7/dist- packages/mglutil/gui/BasicWidgets/Tk/vector3DGUI.py, line 360, in createEntries self.f.grid(column=3, rowspan=3) File /usr/lib/python2.7/lib-tk/Tkinter.py, line 2022, in grid_configure + self._options(cnf, kw)) TclError: cannot use geometry manager grid inside ..139747144006544.139747144007048.139747087050008.139747087052240 which already has slaves managed by pack hit enter to continue /snip -- System Information: Debian Release: jessie/sid APT
Bug#767199: unblock: gvb/1.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gvb This release does not add any features, it simply adapts to new gtk and python, fixes documentation, cleans some code, closes #722271. And it is excluded from the natural migration to testing by just 1 day! unblock gvb/1.4-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.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#765893: streql - Constant-time string comparison
On 29/10/14 17:00, Joel Rees wrote:
2014/10/29 4:59 Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch:
On 29/10/14 00:20, Joel Rees wrote:
On Tue, Oct 28, 2014 at 12:08 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Dear debian-security,
I am looking for a sponsor for my package streql.
In Python, the code for testing the equality of strings is susceptible
to a timing side channel attack. The package 'streql' provides a
function for comparing strings of equal length in equal time,
regardless
of the content of the strings.
* Package name: streql
Version : 3.0.2-1
Upstream Author : Peter Scott pe...@cueup.com
* URL :https://github.com/PeterScott/streql
* License : Apache 2.0
Section : python
It builds those binary packages:
python-streql - Constant-time string comparison (Python 2)
python3-streql - Constant-time string comparison (Python 3)
pypy-streql - Constant-time string comparison (PyPy)
To access further information about this package, please visit the
following
URL:
http://mentors.debian.net/package/streql
Alternatively, one can download the package with dget using this
command:
dget -x
http://mentors.debian.net/debian/pool/main/s/streql/streql_3.0.2-1.dsc
Changes since last upload:
* Initial release (Closes: #764443)
Regards,
Riley Baird
Let me try this suggestion again:
---
// The core function: test two regions of memory for bytewise equality.
static int equals_internal(const char *x, unsigned int xlen, const
char *y, unsigned int ylen) {
int minlen = ( xlen ylen ) ? ylen : xlen;
int i, result = 0;
for (i = 0; i minlen; i++) result |= x[i] ^ y[i];
return ( xlen == ylen ) ( result == 0 );
---
I haven't tested it, but I think the corner case I'm thinking about is
fairly clear.
As far as I can tell, your code ensures that even if the strings are of
different length, an equality calculation should be performed anyway,
however returning 0, on the grounds that this would make it more
difficult for an attacker to know that the two strings entered were of
different lengths. Is this right?
Yeah.
It still leaks length information, but not as obviously.
You could add a busy loop to push the leak to the other side of the sweep.
You could even play games with the busy loop to randomly extend it beyond
the place it would naturally terminate, just to reduce the incentive to
look. (Making sure your pseudo-random selection code is not data dependent,
of course.)
You could change the semantics of the API to allow making the execution
time depend on the length of attacker's guess.
Of course, it's not really hard to get true constant compare times, and
that's what I think I'd aim at.
I've taken your code, and I've also done the required Python
translation. You can see the pull request here:
https://github.com/PeterScott/streql/pull/3
I'm reluctant to make the changes that you mentioned above, because from
what I can tell, the objective of streql is to ensure that for a given
length of string, the time taken to determine equality is constant.
Of course, the changes that you mentioned could be applied only to
strings where the length is unequal, but if the same input is used
twice, and the time taken for each operation is different, then that
would alert an attacker that the strings are of different lengths, which
takes away the whole point of the exercise.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767200: munin-node: /etc/munin/plugin-conf.d/munin-node overrides some, but not all, other configuration
Package: munin-node Version: 2.0.24-1 Severity: important The current configuration file supplied by the package should be called 00-defaults, in order for users to be able to concistently override the configuration. Munin Node now reads configuration files for plugins from /etc/munin/plugin-conf.d/ alphabetically. A common pattern is to place configuration files with the same name as the plugin being configured in this directory, and in that case, the existing file would potentially override settings for all plugins with a name being sorted before munin-node. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-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 munin-node depends on: ii gawk 1:4.1.1+dfsg-1 ii init-system-helpers 1.21 ii libnet-server-perl 2.008-1 ii lsb-base 4.1+Debian13 ii munin-common 2.0.24-1 ii munin-plugins-core 2.0.24-1 ii perl 5.20.1-1 ii procps 2:3.3.9-8 Versions of packages munin-node recommends: ii libnet-snmp-perl 6.0.1-2 ii munin-plugins-extra 2.0.24-1 Versions of packages munin-node suggests: ii acpi 1.7-1 ii ethtool 1:3.16-1 ii hdparm9.43-1.1 ii libcrypt-ssleay-perl 0.58-1+b2 ii libdbd-pg-perl3.4.2-1 pn liblwp-useragent-determined-perl none pn libnet-irc-perl none pn libtext-csv-xs-perl none ii libwww-perl 6.08-1 ii libxml-simple-perl2.20-1 pn logtail none ii munin 2.0.24-1 ii munin-plugins-java2.0.24-1 pn mysql-client none ii net-tools 1.60-26 ii python2.7.8-1 ii ruby 1:2.1.0.4 pn smartmontools none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767201: virtualbox: After update to 4.3.18-dfsg-1 guests doesn't start
Package: virtualbox Version: 4.3.18-dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, After I updated to 4.3.18-dfsg-1 none of my guests starts. No error message found anywhere, just quits. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.13 ii libc62.19-12 ii libcurl3 7.38.0-2 ii libgcc1 1:4.9.1-16 ii libgsoap52.8.17-1 ii libpng12-0 1.2.50-2 ii libpython2.7 2.7.8-10 ii libsdl1.2debian 1.2.15-10 ii libssl1.0.0 1.0.1j-1 ii libstdc++6 4.9.1-16 ii libvncserver00.9.9+dfsg-6+b2 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.3-1 ii libxml2 2.9.1+dfsg1-4 ii libxmu6 2:1.1.2-1 ii libxt6 1:1.1.4-1 ii python 2.7.8-1 ii python2.72.7.8-10 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 10.3.1-1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii virtualbox-dkms 4.3.18-dfsg-1 ii virtualbox-qt 4.3.18-dfsg-1 Versions of packages virtualbox suggests: ii vde22.3.2+r586-1 ii virtualbox-guest-additions-iso 4.3.18-1 -- 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#747785: src:curtain: use dh-autoreconf to fix FTBFS on ppc64el
Package: curtain Version: 0.3-1 Followup-For: Bug #747785 Tags: patch X-Debbugs-Cc: bren...@br.ibm.com User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Dear Maintainer, In the ppc64el architecture, we need new libtool macros, and hence a full autoreconf is required. In ppc64el, the following patch was able to resolve the build issue. Thanks for considering the patch! Brahadambal Srinivasan -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-trunk-powerpc64le (SMP w/32 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash diff -ruN curtain-0.3.orig/debian/control curtain-0.3/debian/control --- curtain-0.3.orig/debian/control 2014-10-29 08:49:18.0 + +++ curtain-0.3/debian/control 2014-10-29 08:49:51.0 + @@ -4,6 +4,7 @@ Maintainer: Andrea Colangelo war...@debian.org Build-Depends: debhelper (= 9), autotools-dev, + dh-autoreconf, intltool, pkg-config, libgtk-3-dev diff -ruN curtain-0.3.orig/debian/rules curtain-0.3/debian/rules --- curtain-0.3.orig/debian/rules 2014-10-29 08:49:30.0 + +++ curtain-0.3/debian/rules2014-10-29 08:50:01.0 + @@ -2,4 +2,4 @@ #export DH_VERBOSE=1 %: - dh $@ --with autotools_dev + dh $@ --with autotools_dev,autoreconf
Bug#767063: unblock: claws-mail/3.11.1-1
Hi Niels, On Tue, Oct 28, 2014 at 09:29:58PM +0100, Niels Thykier wrote: Control: tags -1 moreinfo On 2014-10-28 09:36, Ricardo Mones wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package claws-mail This is a bugfix release to complete removal of SSLv3 usage in all protocols and broken appdata added in 3.11.0 mainly. There's no Debian bugs reported yet (3.11.0 happened last week). Further details: http://git.claws-mail.org/?p=claws.git;f=RELEASE_NOTES;hb=refs/tags/3.11.1 Thanks in advance, unblock claws-mail/3.11.1-1 [...] Hi Ricardo, The changes seems to contain quite a bit of noise. Would you be able to provide a filtered debdiff between the version in unstable and testing? This might give us a better idea of what we will be accepting. Previous unstable (3.11.0-1) would have naturally migrated to testing this week if nothing done. And that's the version to be replaced by current upload (3.11.1-1). Don't really understand why are you comparing with current testing (3.10.1-4) which by default would never have been the candidate version to be released as stable. This looks like I'm being punished with a bigger debdiff (minor version change vs micro version change) just for acting fast to avoid undesired changes in testing. Doesn't look fair :) Or do you really mean debdiff between 3.11.0-1 and 3.11.1-1? -- Ricardo Mones ~ Physics is like sex: sure, it may give some practical results, but that's not why we do it.Richard Feynman signature.asc Description: Digital signature
Bug#767127: thinkfan: won't install
Looking at thinkfan’s postinst, I see that it contains: # Automatically added by dh_installinit if [ -x /etc/init.d/thinkfan ]; then update-rc.d thinkfan defaults /dev/null invoke-rc.d thinkfan start || exit $? fi Even if thinkfan.service is not enabled, invoke-rc.d will start it. It’s that line that you need to get rid of in order to prevent the behavior you’re seeing. A more idiomatic alternative might be to add ConditionPathExists=/etc/thinkfan.conf in the .service file so that systemd will refuse to start thinkfan until you create its config file, no matter whether the unit itself is enabled or not. On Tue, Oct 28, 2014 at 7:36 PM, Evgeni Golov evg...@debian.org wrote: Hi HJ, On 10/28/2014 05:11 PM, HJ wrote: root@debtop:/home/ssf# LANG=C apt-get -y -qq install thinkfan Setting up thinkfan (0.9.2-1) ... Job for thinkfan.service failed. See 'systemctl status thinkfan.service' and 'journalctl -xn' for details. invoke-rc.d: initscript thinkfan, action start failed. dpkg: error processing package thinkfan (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: thinkfan E: Sub-process /usr/bin/dpkg returned an error code (1) root@debtop:/home/ssf# thanks for the report. This should not happen, as thinkfan should not be enabled until you have configured it properly. I am CCing Michael Stapelberg, who implemented that part for systemd, which you are running. @Michael, do you have an idea, why it tries to start thinkfan, even if it should be disabled? @HJ, can you post a service thinkfan status please? Greets Evgeni -- 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#762790: powerpc-utils: maintainer address bounces
Hi Michael, On Wed, 29 Oct 2014 08:30:15 +1300 Michael Schmitz schmitz...@gmail.com wrote: Hi, sorry about the bounce - I had been assured mail forwarding would be set up when the mailserver handling that address was retired. Shall I prepare a source-only upload to correct the address? Yes, and you can also ACK the NMU. :-) It is probably good idea to avoid big changes since the package will have to migrate to testing manually, after the freeze. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767137: RFS: bsdowl/2.2.1-1 ITP
So, with a little bit more work, I was able to produce a version passing all QA tests on mentors: https://mentors.debian.net/package/bsdowl There were more warning than lintian (called from debuild) shown me. Which tool can I use to detect at least as many QA problems as mentors did? 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#763006: [pkg-cli-apps-team] Bug#763006: Will 0.95.2 be pushed to Ubuntu 14.10 repos?
On Tue, Oct 28, 2014 at 09:34:13PM -0400, Vic Kumar wrote: ... Currently, the version in the repos is 0.95.1. I saw the issue looks to be fixed in 0.95.2. Was wondering if this will be pushed into the repo's for Ubuntu 14.10. I know, I know. It's only been 2 days since the issue was resolved, but I like gnome-do. It is already fixed there. https://launchpad.net/ubuntu/+source/gnome-do/0.95.1-1ubuntu1 -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#767163: util-linux: root partition not being fsck'd
Hi David! Just adding back the bug report to CC so we get all information recorded and available to everyone interested in investigating it. Please use reply-to-all in future followups. On Tue, Oct 28, 2014 at 06:06:39PM -0500, David Wright wrote: Quoting Andreas Henriksson (andr...@fatal.se): [...] AFAIK systemd expects filesystems to be fscked before they are mounted (eg. in initramfs). Not sure if this also applies to root filesystem. Is this true even if mounted readonly? Looks from the reportbug information at the bottom of your mail like you're running the official Debian kernel (and not a custom kernel without initramfs), right? Yes. Could you please try 'findmnt --df' and give me the output? (This should run the same libmount filesystem detection code as fsck.) $ findmnt --df SOURCEFSTYPE SIZE USED AVAIL USE% TARGET udev devtmpfs 10M 0 10M 0% /dev tmpfs tmpfs 402.8M 6.3M 396.5M 2% /run /dev/disk/by-label/john01 ext3 14.6G 10.4G3.5G 71% / tmpfs tmpfs1007.1M 68K 1007M 0% /dev/shm tmpfs tmpfs 5M4K 5M 0% /run/lock tmpfs tmpfs1007.1M 0 1007.1M 0% /sys/fs/cgroup /dev/sda2 ext4 14.6G 8.6G5.2G 59% /westw /dev/sda3 ext3 42G 36.9G 3G 88% /home tmpfs tmpfs 201.4M8K 201.4M 0% /run/user/1000 west!david 17:48 ~ [...] Verifying you see the same information in 'journalctl -u systemd-fsck-root' as the fat fsck you included in the bug report might also be useful. Looks like that's so: -- Logs begin at Tue 2014-10-28 12:48:03 CDT, end at Tue 2014-10-28 17:17:01 CDT. -- Oct 28 12:48:03 west systemd-fsck[133]: ESC[1;31mPlease pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system.ESC[0m Oct 28 12:48:03 west systemd-fsck[133]: Logical sector size is zero. Oct 28 12:48:03 west systemd-fsck[133]: fsck.fat 3.0.26 (2014-03-07) lines 1-4/4 (END) (I've only just changed shutdown -F to touch /forcefsck ; shutdown so I've yet to investigate using the kernel command line; but that's another issue.) Cheers, David. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709104: Should not Depends or Recommends gnupg-agent
Package: gnupg2 Followup-For: Bug #709104 Dear Maintainer, I just ran into the situation that I had to install gnupg2 on a couple of servers and was forced to install font-config, x11-libs and even some true-type-fonts. From Debian I am used to not having to install stuff like this if I tell apt not to install recommends. If you really really really want to keep gnupg-agent as a Depends please change the pinentry-Depends of gnupg-agent to pinentry-curses and add a Recommends to pinentry-gtk2 or whatever. I do not think that installing pinentry-curses before installing gnupg2 to keep gnupg2 from pulling those libs is really a good idea, this sounds like something I would want my package-manager to take care of. Regards, Johann Hartwig Hauschild -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE, 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#767202: pu: package sysvinit/2.88dsf-41+deb7u1: bootlogd log on multiple consoles
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Dear release team, I'm opening a bug as suggested by KiBi. I would like to close bug #181756, which contains a patch that I forward ported to Sid last summer, and uploaded in sysvinit 2.88dsf-53.4. The patch is available here (in the bug report): https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=51;filename=allow-multiple-console-output.patch;att=1;bug=181756 This patch is important because if you use a server, you may want to activate serial console boot log. It is also very important for cloud computing. For example, with OpenStack, bootlogd must log on both tty0 and ttyS0 to have both nova console-log and the interactive web terminal to work. Otherwise, it is always the last console= argument on the command line that is in use. Nobody reported any issue since my upload to Sid on the 24th of August. I also tested the patch in Wheezy on a Xen VPS, and using OpenStack on virtual machine instances. Both ran without any issue. If the release team agree that I add the patch to the Wheezy version of bootlogd, then I will prepare a package and send links to both the package itself, and the debdiff for pre-approval, before uploading to stable p-u. Please let me know your thoughts about this, Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607969: sqlite: Still useful?
Hi, On Mon, 4 Aug 2014 20:08:21 +0100 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: Control: severity -1 serious Hi, I stumbled upon this bug by chance when looking at why it did not compile in some new ports. Raising severity so at the very least it gets auto-removed from testing and thus it does not get included in the next stable release (it already was included in the last, despite opinions in this bug about the contrary). I guess that it's better to just ask FTP masters to remove the package, but I'll leave that to other people, since they were interested in doing that in the past (all in copy now). Filing bugs against reverse dependencies to migrate to sqlite 3 would be a better start IMO. Probably it is too late to convert everything for Jessie: $ apt-cache rdepends sqlite sqlite Reverse Depends: phpbb3 |movabletype-opensource sqlite:i386 sqlite-doc qsf phpbb3 lire imms-common csync2 beancounter Dear Release Team, should this package be released with Jessie? Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766708: Request to override gcc maintainer changes breaking unsupported way of cross-building
On 29 October 2014 06:32, Helmut Grohne hel...@subdivi.de wrote: Matthias contended that the default method to build a gcc cross compiler works with multiarch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766708#73 On Sun, Oct 26, 2014 at 03:50:59PM +0100, Helmut Grohne wrote: Why is with_deps_on_target_arch_pkgs needed? Without this flag, gcc emits dependencies on libc*-$arch-cross. In order to satisfy these dependencies binary packages from glibc have to be repacked and renamed. When using the resulting cross toolchain to build further Debian packages there are two choices, both of which are bad: * Newly cross built packages also depend on libc6-$arch-cross. This will make them different from natively built packages and in particular makes debootstrap fail. * Newly cross built packages keep their dependency on libc6. This will make them uninstallable in the build chroot, because there is no foreign arch libc package that can be co-installed with the aforementioned libc*-$arch-cross. Either option makes the bootstrap of a new architecture fail. I do not immediately see where this rationale is flawed, but I cannot reproduce his claim: When building with the default method, the resulting packages are uninstallable, because libc6-$arch-cross is not available in the archive and not built from any source package. Thus the default method relies on out-of-archive code whereas the unsupported with_deps_on_target_arch_pkgs method does not. It looks like this issue should be addressed in a package different from gcc, but to date this hasn't happened. So it may be wise to ignore the quoted reasoning (on the grounds that it cannot be verified), because the code that makes it work has not yet arrived. This actually was the primary reason for me to start using with_deps_on_target_arch_pkgs when learning about cross compilation: I couldn't figure out where to obtain these libc*-$arch-cross packages, but when I just set that flag I wouldn't have to. I therefore argue that getting the relevant support into the glibc package could be a resolution of the complaint made to the ctte, but now we're stepping on entirely different toes. (Again this seems to be a timing thing, as Matthias and Adam Conrad are apparently working on this.) Why is DEB_CROSS_NO_BIARCH needed? There currently is a bug in rebootstrap that makes building multilib enabled cross-toolchains fail. Thus far I failed to figure out the reasons for this failure (beyond knowing that gcc looks for crti.o in the wrong directory). So in the spirit of having something working rather than nothing, this fiddle is needed to bootstrap multilib-enabled architectures now. I intend to eliminate the need DEB_CROSS_NO_BIARCH. Note that this need might be a consequence of using with_deps_on_target_arch_pkgs=yes and might be unneeded with the supported default method. Following this bug report loosely I'm failing to see why any changes, or proposed patches are needed to the src:gcc-4.x packages. The libc*-$arch-cross packages come from rebuilds of glibc package. All of which can be compiled trivially with Build-Depends / Build-Using: linux-source, gcc-4.x-source, glibc-source. An example of doing so one can check out out of the archive armhf-cross-toolchain-base / gcc-4.8-armhf-cross packages and similar for other architectures (arm64, ppc64el, etc.) The benefit of those are that they do not rely on multiarch repositories to be present on the builders, or the users installed systems (which by the way is not yet default in Debian anywhere), allow those toolchains to be migrated by britney independent of the multi-arch scew, and allow to be rebuild/moved to default versions independent of the src:gcc-4.x / src:binutils, apply any cross specific patches, and be multilib. Current gcc packaging is complex, and it should move towards simplification that is zero base budget (remove/reduce amount of packaging code, must not increase LOC or bolt on more features). If supported cross-toolchains are desired to be in archive, they need to be stand-alone and not break when native toolchain is updated, therefore own (verified) cross-versions (rebuilds) of libc and gcc is a must. The proposed multiarched builds, are only good for one time out of the archive bootstraps, but in no way are supportable in the archive. I found it trivial to work with current cross-building support via toolcahin-base support package which leverages existing binutils/glibc/gcc cross-building support. To both perform regular cross toolchains to debian arches, and use a different libc (bionic). Instead of adding more patches to src:gcc, a stand-alone src packages should be used that build-depend on gcc-4.x-source/binutils-source/gcc-source etc. and thus independently maintained, and accumulate/deal with their own set of RC bugs, and would not block, nor be inter-locked, nor coupled with native default major release upgrades. --
Bug#767162: systemd: gdm3 and gnome broken after dist-upgrade
OKthismay havebeenmywrongreception.ThereasonwhyIthoughtonsystemd,wastheboot message A start job is running for Create Volatile Files and Directories and the log message: systemd[1]: Cannot add dependency job for unit systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service failed to load: No such file or directory. But when systemd is ok from your view that's fine. WhatshouldIdotoclarifywhysincethelastupdate, gdm3 and gnome nomoreworks? How can I provide you with the right information? best regards Ralph On 29.10.2014 01:31, Michael Biebl wrote: None of these messages point to a problem in systemd. Please elaborate why you filed the bug against the systemd package Am 28. Oktober 2014 21:15:29 MEZ, schrieb Ralph Soika ralph.so...@imixs.com: Package: systemd Version: 215-5+b1 Severity: important Dear Maintainer, I have some strange problems with my debian jessie testing release after a dist-upgrade today. I am testing jessie since more then a year. I upgrade once a week. Today I have seen a strange message during booting: A start job is running for Create Volatile Files and Directories So I decided to upgrade. This included updates of systemd (215-5+b1) and systemd-shim (as I think I can remember). After the dist-upgrade 'gdm3' and 'gnome-shell' is no longer working. Also Plymouth seem not to work during booting, because I see the boot messages. I installed lightdm and xfce to get a working desktop. But I can not figure out whats going wrong with gnome until my last upgrade. I think it could be something with systemd ore systemd-shim because I have simmilar problems for 4 or 3 weeks. During booting I now have messages like this: systemd[1]: Cannot add dependency job for unit systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service failed to load: No such file or directory. and when I try to login to gnome session (which fails) I have messages like this: gnome-session[2001]: ** (gnome-session-failed:2454): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Oct 28 19:29:52 ralpus-ultrabook systemd-udevd[193]: Network interface NamePolicy= disabled on kernel commandline, ignoring. Oct 28 19:29:53 ralpus-ultrabook gnome-session[2001]: ** (gnome-session- quit:2470): WARNING **: Failed to call logout: The name org.gnome.SessionManager was not provided by any .service files Oct 28 19:29:56 ralpus-ultrabook org.a11y.Bus[849]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Oct 28 19:29:56 ralpus-ultrabook org.a11y.atspi.Registry[855]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 Oct 28 19:29:56 ralpus-ultrabook org.a11y.atspi.Registry[855]: after 41 requests (39 known processed) with 0 events remaining. can anybody help me? Can I do anything to provide you with necessary information about my system? Thanks for any help Ralph -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.4 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.1-5 ii libc6 2.19-11 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-2 ii libgcrypt20 1.6.2-3 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii sysv-rc 2.88dsf-53.4 ii udev215-5+b1 ii util-linux 2.25.1-5 Versions of packages systemd recommends: ii dbus1.8.8-2 ii libpam-systemd 215-5+b1 Versions of packages systemd suggests: pn systemd-ui none -- no debconf information Pkg-systemd-maintainers mailing list pkg-systemd-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
Bug#763961: Pitivi doesn't start, please update from upstream
Ubuntu has a set of cherry-picked patches on top of 0.93-4 that make it usable: https://launchpad.net/ubuntu/+source/pitivi/0.93-4ubuntu1 These would be probably enough for jessie. -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767173: gnome-shell: Display freezes but mouse stays operational
Originally I wanted to reply to bug #675345, but the reportbug tool created a new bug number instead. I'm not even sure the bug is in gnome-shell. I should have filed the bug for the more general package `gnome`. I can right-click on the desktop without problems. I have been running Debian Wheezy with standard Gnome on the same laptop with all the same hardware for over 2 years, and never experienced any freeze. This issue definitely was introduced with Jessie. Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#433568: add vlan support
Hi, We're really interested in this, where should we look for a status update? I still do not see an option for it in the installer for Wheezy, so I guess it's not done yet. Will it be present for Jessie? Anything we can do to help? -- Kind regards, Met vriendelijke groet, Tim Stoop Kumina bv www.kumina.nl kvk nr 14095795 Interested in keeping up to date with Kumina? Consider subscribing to our newsletter! https://www.kumina.nl/newsletter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765371: owfs is marked for autoremoval from testing
On 29/10/2014 05:39, Debian testing autoremoval watch wrote: owfs 2.9p5-1.1 is marked for autoremoval from testing on 2014-11-13 It is affected by these RC bugs: 765371: python-ow: Import fails - error parsing version (fixed upstream) Hi, This bug is fixed in unstable. I did not take time to initially downgrade the bug severity as I did a quick upload to unstable. However, due to problem with FreeBSD, I will probably need to ask for a freeze exception. But, in any case, this bug is not a grave one. Python bindings are only a very little aspect of owfs and a such a bug do not justify such a severity. Regards, Vincent -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607969: sqlite: Still useful?
On Wed, Oct 29, 2014 at 10:33:32 +0100, Balint Reczey wrote: Dear Release Team, should this package be released with Jessie? The only way I can see us not shipping it is if we remove it along with the remaining rdeps. Now is not the time to migrate them over to sqlite3 in jessie. Cheers, Julien signature.asc Description: Digital signature
Bug#767163: util-linux: root partition not being fsck'd
On Tue, Oct 28, 2014 at 07:46:04PM -0400, Phillip Susi wrote: [...] I see, very strange. With Davids latest followup I would say things are just getting more and more strange. findmnt reports ext* in the filesystem column, which comes from case COL_FSTYPE: str = xstrdup(mnt_fs_get_fstype(fs)); break; ... and mnt_fs_get_fstype is the exact same call used by fsck. Even though it dropped the use of fsck -a, I don't think systemd ever did fsck -a and if I'm not mistaken neither does sysvinit (anymore?) (but please check to make sure if you're really interested in the details). it does still use fsck, even though it does know the proper fs fsck tool's name and checks to make sure it exists. In that case, I'd bet that blkid -p run on that device will report that it is fat because it does in fact, still contain a fat boot sector. You're right, I missed the type checking stuff in my quick glance... although the type reported by udev is never used for anything else then checking if the filesystem specific fsck is available (with a warning if not). David, could you please give us the output from: # udevadm info -n /dev/whatever1 -q property | grep ID_FS_TYPE ...and... # blkid -p /dev/whatever1 (Although I asked for findmnt since blkid doesn't seem to use libmount (as fsck) but I guess the more information we have the better.) In that case, this bug can be closed and David just needs to remove the bogus fat boot sector with wipefs. (Or surgical precision, to not lose the existing filesystem?!) Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607969: sqlite: Still useful?
On Wed, Oct 29, 2014 at 10:33 AM, Balint Reczey bal...@balintreczey.hu wrote: On Mon, 4 Aug 2014 20:08:21 +0100 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I stumbled upon this bug by chance when looking at why it did not compile in some new ports. It should compile on all of them by now. The buildd archive shows that arm64 and ppc64el are fine, even mips and sparc. I guess that it's better to just ask FTP masters to remove the package, but I'll leave that to other people, since they were interested in doing that in the past (all in copy now). Yes, I was about to ask its removal as upstream no longer supports it. But it works correctly and I got personal mails that they would still use it on low-end (embedded?) machines where sqlite3 would require more CPU and/or memory. Filing bugs against reverse dependencies to migrate to sqlite 3 would be a better start IMO. I've mailed all of them some years ago, but there are still some use it. Probably it is too late to convert everything for Jessie: It is late. Dear Release Team, should this package be released with Jessie? I'm open for everything, but please do note that the removal would mean removing the dependent packages as well. Cheers, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607969: sqlite: Still useful?
Hi Julien, 2014-10-29 10:48 GMT+01:00 Julien Cristau jcris...@debian.org: On Wed, Oct 29, 2014 at 10:33:32 +0100, Balint Reczey wrote: Dear Release Team, should this package be released with Jessie? The only way I can see us not shipping it is if we remove it along with the remaining rdeps. Now is not the time to migrate them over to sqlite3 in jessie. I fully agree. How about marking this bug jessie-ignore or decreasing the severity? I periodically look for RC bugs to fix (like hopefully many others :-)) and those would make that bug stop appearing on the list. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744753: anacron: Anacron not triggered when system resumes under systemd
Le Tue, 28 Oct 2014 13:24:53 +0100, Laurent Bigonville bi...@debian.org a écrit : severity 744753 serious thanks Hello, IMHO this bug should be serious as anacron is more or less useless without this. Do we have a consensus on a solution here? Michael was proposing another solution. Instead of waking anacron at boot and just after sleep, we could run it every hour. So it would be quite unlikely that anacron is not run at all at least once a day on the machine of the user. I personally don't have strong feeling about this. Looking at Fedora they are doing this too apparently. Any thoughts? Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767203: postfix: default install vulnerable for POODLE TLS attack
package: postfix version: 2.9.6-2 tag: upstream severity: critical Hi, The Postfix Debian package ships with a default list of supported TLS protocols which makes it vulnerable to the POODLE TLS attack: % postconf smtp_tls_mandatory_protocols smtp_tls_mandatory_protocols = !SSLv2 This is the upstream default: % postconf -d smtp_tls_mandatory_protocols smtp_tls_mandatory_protocols = !SSLv2 Other vulnerable daemon settings are: lmtp_tls_mandatory_protocols = !SSLv2 lmtp_tls_protocols = !SSLv2 smtp_tls_mandatory_protocols = !SSLv2 smtp_tls_protocols = !SSLv2 smtpd_tls_mandatory_protocols = !SSLv2 It would be nice if postfix would ship with a /etc/postfix/main.cf which features tls_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = $tls_protocols smtp_tls_mandatory_protocols = $tls_protocols lmtp_tls_protocols = $tls_protocols lmtp_tls_mandatory_protocols = $tls_protocols smtpd_tls_protocols = $tls_protocols smtpd_tls_mandatory_protocols = $tls_protocols tlsproxy_tls_protocols = $tls_protocols tlsproxy_tls_mandatory_protocols = $tls_protocols This would make the default install no longer vulnerable for POODLE. Thanks to Wessel Dankers for reporting the problem to me, and suggesting the mentioned fixes. Thanks for maintaining the Postfix package, Bye, Joost PS: this bug is somewhat related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729188#103 PPS FWIW: on https://blog.surfnet.nl/?p=3290 there's a more elaborate list of current sane defaults. Currently, tls_ciphers = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA lmtp_tls_ciphers = $tls_ciphers lmtp_tls_mandatory_ciphers = $tls_ciphers smtp_tls_ciphers = $tls_ciphers smtp_tls_mandatory_ciphers = $tls_ciphers smtpd_tls_ciphers = $tls_ciphers smtpd_tls_mandatory_ciphers = $tls_ciphers tlsproxy_tls_ciphers = $tls_ciphers tlsproxy_tls_mandatory_ciphers = $tls_ciphers is sane too (but not future-proof). signature.asc Description: Digital signature
Bug#767204: request: backport i2c-hid suspend, resume fix from 3.17 to 3.16
Package: src:linux
Version: 3.16.5-1
The touchpad (`SYN1B7D:01 06CB:2991 UNKNOWN` as reported by dmesg) of
a friend's laptop stops working after suspending and resuming the
laptop when using kernel 3.16. I cannot test older kernels as the
laptop is quite new. The problem is solved in 3.17 with commit
[109571c]. Since, AFAIK, Jessie will ship with kernel 3.16, please
consider the attached patch, which adds [109571c] to
`debian/patches/bugfix/all` and updates `debian/patches/series`.
[109571c]:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=109571cf3ec78a39477eedd6b11927f52cbcb1e8
Best regards,
Joost
diff -Naur debian.orig/patches/bugfix/all/i2c-hid-suspend-resume-fix.patch debian/patches/bugfix/all/i2c-hid-suspend-resume-fix.patch
--- debian.orig/patches/bugfix/all/i2c-hid-suspend-resume-fix.patch 1970-01-01 01:00:00.0 +0100
+++ debian/patches/bugfix/all/i2c-hid-suspend-resume-fix.patch 2014-10-11 15:35:34.774146332 +0200
@@ -0,0 +1,73 @@
+From 109571cf3ec78a39477eedd6b11927f52cbcb1e8 Mon Sep 17 00:00:00 2001
+From: Andrew Duggan adug...@synaptics.com
+Date: Fri, 11 Jul 2014 16:34:18 -0700
+Subject: [PATCH] HID: i2c-hid: call the hid driver's suspend and resume
+ callbacks
+
+Currently, the i2c-hid driver does not call the suspend, resume, and
+reset_resume callbacks in the hid_driver struct when those events occur.
+This means that HID drivers for i2c-hid devices will not be able to execute
+commands which may be needed during suspend or resume. One example is when a
+touchpad using the hid-multitouch driver gets reset by i2c-hid coming out of
+resume. Since the reset_resume callback never gets called the device is never
+put back into the correct input mode. This patch calls the suspend and resume
+callbacks and tries to duplicate the functionality of the usb-hid driver.
+
+Signed-off-by: Andrew Duggan adug...@synaptics.com
+Signed-off-by: Vincent Huang vincent.hu...@tw.synaptics.com
+Reviewed-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
+Signed-off-by: Jiri Kosina jkos...@suse.cz
+---
+ drivers/hid/i2c-hid/i2c-hid.c | 15 ++-
+ 1 file changed, 14 insertions(+), 1 deletion(-)
+
+diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
+index 21aafc8..747d544 100644
+--- a/drivers/hid/i2c-hid/i2c-hid.c
b/drivers/hid/i2c-hid/i2c-hid.c
+@@ -1054,21 +1054,29 @@ static int i2c_hid_remove(struct i2c_client *client)
+ static int i2c_hid_suspend(struct device *dev)
+ {
+ struct i2c_client *client = to_i2c_client(dev);
++ struct i2c_hid *ihid = i2c_get_clientdata(client);
++ struct hid_device *hid = ihid-hid;
++ int ret = 0;
+
+ disable_irq(client-irq);
+ if (device_may_wakeup(client-dev))
+ enable_irq_wake(client-irq);
+
++ if (hid-driver hid-driver-suspend)
++ ret = hid-driver-suspend(hid, PMSG_SUSPEND);
++
+ /* Save some power */
+ i2c_hid_set_power(client, I2C_HID_PWR_SLEEP);
+
+- return 0;
++ return ret;
+ }
+
+ static int i2c_hid_resume(struct device *dev)
+ {
+ int ret;
+ struct i2c_client *client = to_i2c_client(dev);
++ struct i2c_hid *ihid = i2c_get_clientdata(client);
++ struct hid_device *hid = ihid-hid;
+
+ enable_irq(client-irq);
+ ret = i2c_hid_hwreset(client);
+@@ -1078,6 +1086,11 @@ static int i2c_hid_resume(struct device *dev)
+ if (device_may_wakeup(client-dev))
+ disable_irq_wake(client-irq);
+
++ if (hid-driver hid-driver-reset_resume) {
++ ret = hid-driver-reset_resume(hid);
++ return ret;
++ }
++
+ return 0;
+ }
+ #endif
+--
+2.1.1
+
diff -Naur debian.orig/patches/series debian/patches/series
--- debian.orig/patches/series 2014-10-10 04:16:39.0 +0200
+++ debian/patches/series 2014-10-11 15:35:49.733657053 +0200
@@ -110,6 +110,7 @@
debian/i2o-disable-i2o_ext_adaptec-on-64bit.patch
bugfix/all/aic94xx-remove-broken-fallback-for-missing-ctrl-a.patch
bugfix/all/builddeb-put-the-dbg-files-into-the-correct-director.patch
+bugfix/all/i2c-hid-suspend-resume-fix.patch
# memfd_create() kdbus backport
features/all/kdbus/mm-allow-drivers-to-prevent-new-writable-mappings.patch
Bug#766936: [pkg-otr-team] Bug#766936: [libotr5] Extended description: Deniability is not a feature per se
On Tue, Oct 28, 2014 at 08:56:07PM -0400, Filipus Klutiero wrote: I am not convinced this is a good thing, but for sure the current phrasing is incorrect. According to the technical paper, OTR would merely send the key to the other participant, so only him could forge messages, unless someone captured the message. So the only person who can forge messages after the conversation is the other participant. Since he could already forge messages, that measure does not increase deniability in normal circumstances. No, that's not quite right; OTR sends the authentication (MAC) key *in the clear* so that anyone capturing the traffic on the wire can subsequently modify transcripts however they like. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767203: postfix: default install vulnerable for POODLE TLS attack
Control: severity -1 normal On Wed, Oct 29, 2014 at 10:45:59 +0100, Joost van Baal-Ilić wrote: package: postfix version: 2.9.6-2 tag: upstream severity: critical Hi, The Postfix Debian package ships with a default list of supported TLS protocols which makes it vulnerable to the POODLE TLS attack: The postfix debian package uses libssl, which has disabled sslv3 in 1.0.1j-1. Cheers, Julien signature.asc Description: Digital signature
Bug#682413: USB TrackPoint keyboards unusable since synaptics-usb was included
On Mon, 16 Sep 2013 03:24:45 +0100 Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2013-09-15 at 17:34 -0500, Andrew Deason wrote: [...] If anyone here would like to test these out and see how the trackpoint behaves, it would be appreciated. If you don't know how to run such patches, I can provide info on how to do that. (Providing a debian package I'm not sure would work, since we already have a synaptics_usb driver in the regular kernel package... and I don't want to have to generate an entirely new kernel package just for patching this one driver.) There are generic instructions for that here: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official I didn't tried the patch, but I've the same problem with the SK-8845 IBM/Lenovo keyboard. Still not fixed in 2014? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766902: @reboot jobs are run on package installation
It is fixed in two places: .. but newly added @reboot jobs will still be executed right away. http://www.freedesktop.org/software/systemd/man/systemd.timer.html If a timer configured with OnBootSec= or OnStartupSec= is already in the past when the timer unit is activated, it will immediately elapse and the configured unit is started. Simply creating /run/crond.reboot at the end of the generator conflicts with a work around for another non-solved bug: TL;DR: when /var is mounted separately, the generator needs to be run twice. https://github.com/systemd-cron/systemd-cron/issues/26 http://lists.freedesktop.org/archives/systemd-devel/2014-October/024239.html -- crontab will now create /run/crond.reboot too, in order to mitigate this bug https://github.com/systemd-cron/systemd-cron/commit/5da457fbd837dd6371a9858a2a4abfa8c9b495ac -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#433568: add vlan support
Tim Stoop t...@kumina.nl (2014-10-29): Hi, We're really interested in this, where should we look for a status update? I still do not see an option for it in the installer for Wheezy, so I guess it's not done yet. Will it be present for Jessie? Anything we can do to help? Philipp, any news on your side? Mraw, KiBi. signature.asc Description: Digital signature
Bug#767205: RFS: addresses-for-gnustep/0.4.7-2 -- Address framework for GNUstep [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package addresses-for-gnustep. The package has a lot of lintian warnings and is generally in a poor shape. Most issues are fixed in the master branch but they're not applicable for jessie. This release addresses only the RC bug #749721. It builds these binary packages: addresses-goodies-for-gnustep - Personal Address Manager for GNUstep (Goodies) addresses.framework - Database API backend framework for GNUstep addressmanager.app - Personal Address Manager for GNUstep addressview.framework - Address display/edit framework for GNUstep libaddresses-dev - Database API backend framework for GNUstep (development files libaddresses0 - Database API backend framework for GNUstep (library files) libaddressview-dev - Address display/edit framework for GNUstep (development files) libaddressview0 - Address display/edit framework for GNUstep (library files) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/addresses-for-gnustep Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/addresses-for-gnustep/addresses-for-gnustep_0.4.7-2.dsc Changes since the last upload: * Team upload. * Apply minimal fix to make the package usable with the current GNUstep libraries (Closes: #749721): - Fix overflow in implicit constant conversion; - Fix improper use of non-existent method; - Do not set string of a NSTextView to nil. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767206: Gtk-Message: Failed to load module canberra-gtk-module
Package: vim-gnome Version: 2:7.4.430-1 Tags: patch When opening a file in gvim, I get the following annoying warning: $ gvim AssemblyInfo.cpp Gtk-Message: Failed to load module canberra-gtk-module could you either remove the warning completely and/or mark `libcanberra-gtk-module` as `Recommends:` Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767150: exaile: The Collection view is not updated automatically when the collection is rescanned
3.4.0.2-1~bpo70+1 from wheezy-backports does not have the bug, newly added tracks appear in the collection view automatically as soon as the scan is completed. --ll -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767207: libssl-dev: unnecessary Depends: zlib1g-dev
Package: libssl-dev Version: 1.0.1j-1 Severity: normal Dear Maintainer, in Bug#728055 drop zlib then zlib1g-dev is no longer required. please remove it from debian/control. Thank you, Hiroyuki YAMAMORI -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.8.13.28p4 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libssl-dev depends on: ii libssl1.0.0 1.0.1j-1 ii zlib1g-dev 1:1.2.8.dfsg-2 Versions of packages libssl-dev recommends: pn libssl-doc none libssl-dev 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#767150: exaile: The Collection view is not updated automatically when the collection is rescanned
Control: tag -1 - moreinfo + upstream fixed-upstream Control: fixed -1 3.4.0.2-1 On Wed, Oct 29, 2014 at 3:13 AM, Lars Luthman deb-b...@larsluthman.net wrote: 3.4.0.2-1~bpo70+1 from wheezy-backports does not have the bug, newly added tracks appear in the collection view automatically as soon as the scan is completed. Great, setting tags and fixed version accordingly. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767208: unattended-upgrades: Misleading comment in /etc/apt/apt.conf.d/50unattended-upgrades
Package: unattended-upgrades
Version: 0.83
// Within lines unattended-upgrades allows 2 macros whose values are
// derived from /etc/debian_version:
// ${distro_id}Installed origin.
// ${distro_codename} Installed codename (eg, jessie)
When jessie becomes stable, /etc/debian_version will contain 8 or a
string in the form 8.x. As you can't derive jessie only from 8,
the comment is misleading, and the user will wonder if this will
continue to work when jessie becomes stable.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767209: bibletime: FTBFS on s390x (relocation truncated to fit)
Source: bibletime Version: 2.10.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the s390x buildd: /usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -ggdb -Wl,-z,relro CMakeFiles/bibletime.dir/src/backend/btmoduletreeitem.cpp.o CMakeFiles/bibletime.dir/src/backend/cswordmodulesearch.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallbackend.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallmgr.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallthread.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelffiltermodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelfmodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelftreemodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/categoryitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/indexingitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/item.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/languageitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/moduleitem.cpp.o CMakeFiles/bibletime.dir/src/backend/config/btconfig.cpp.o CMakeFiles/bibletime.dir/src/backend/config/btconfigcore.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordbiblemoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordbookmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordcommentarymoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordlexiconmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/gbftohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/osistohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/plaintohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/teitohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/thmltohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/thmltoplain.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/btosismorphsegmentation.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordkey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordldkey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordtreekey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordversekey.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cbookdisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cchapterdisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cdisplayrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/centrydisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/chtmlexportrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cplaintextexportrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/ctextrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/btstringmgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/cdisplaytemplatemgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/clanguagemgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/cswordbackend.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/referencemanager.cpp.o CMakeFiles/bibletime.dir/src/util/cresmgr.cpp.o CMakeFiles/bibletime.dir/src/util/directory.cpp.o CMakeFiles/bibletime.dir/src/util/btmodules.cpp.o CMakeFiles/bibletime.dir/src/util/geticon.cpp.o CMakeFiles/bibletime.dir/src/util/tool.cpp.o CMakeFiles/bibletime.dir/src/bibletime.cpp.o CMakeFiles/bibletime.dir/src/bibletime_dbus.cpp.o CMakeFiles/bibletime.dir/src/bibletime_dbus_adaptor.cpp.o CMakeFiles/bibletime.dir/src/bibletime_init.cpp.o CMakeFiles/bibletime.dir/src/bibletime_slots.cpp.o CMakeFiles/bibletime.dir/src/bibletimeapp.cpp.o CMakeFiles/bibletime.dir/src/btglobal.cpp.o CMakeFiles/bibletime.dir/src/main.cpp.o CMakeFiles/bibletime.dir/src/frontend/btaboutdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btaboutmoduledialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfdockwidget.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfgroupingmenu.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfview.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfwidget.cpp.o CMakeFiles/bibletime.dir/src/frontend/btmenuview.cpp.o CMakeFiles/bibletime.dir/src/frontend/btmodulechooserdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btmoduleindexdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btopenworkaction.cpp.o CMakeFiles/bibletime.dir/src/frontend/cexportmanager.cpp.o CMakeFiles/bibletime.dir/src/frontend/cinfodisplay.cpp.o CMakeFiles/bibletime.dir/src/frontend/cmdiarea.cpp.o CMakeFiles/bibletime.dir/src/frontend/cprinter.cpp.o CMakeFiles/bibletime.dir/src/frontend/crossrefrendering.cpp.o CMakeFiles/bibletime.dir/src/frontend/messagedialog.cpp.o
Bug#767212: pillow: FTBFS on mips (hang during tests)
Source: pillow Version: 2.6.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package failed to build on the mips buildd: BEGIN python2.7-dbg tests cd tmp python2.7-dbg ../debian/test-built.py --processes=1 --process-timeout=90 Tests/test_imagecolor.py Tests/test_pyroma.py Tests/test_imagesequence.py Tests/test_file_webp_alpha.py Tests/test_imagecms.py Tests/test_image_tobitmap.py Tests/test_imageqt.py Tests/test_file_ppm.py Tests/test_image_putalpha.py Tests/test_file_webp_metadata.py Tests/test_file_eps.py Tests/test_image_filter.py Tests/test_file_fli.py Tests/test_000_sanity.py Tests/test_imagefile.py Tests/test_file_icns.py Tests/test_image_array.py Tests/test_decompression_bomb.py Tests/test_image_getbands.py Tests/test_image.py Tests/test_file_tiff.py Tests/test_lib_pack.py Tests/test_image_getim.py Tests/test_image_putdata.py Tests/test_file_webp_lossless.py Tests/test_imageshow.py Tests/test_lib_image.py Tests/test_file_psd.py Tests/test_imagetk.py Tests/test_image_frombytes.py Tests/test_image_getcolors.py Tests/test_file_png.py Tests/test_image_getextrema.py Tests/test_image_getdata.py Tests/test_imageops.py Tests/test_image_getpalette.py Tests/test_image_putpalette.py Tests/test_image_transform.py Tests/test_file_jpeg2k.py Tests/test_file_libtiff.py Tests/test_format_lab.py Tests/test_locale.py Tests/test_file_gimpgradient.py Tests/test_image_thumbnail.py Tests/test_file_sgi.py Tests/test_file_xpm.py Tests/test_image_getprojection.py Tests/test_image_histogram.py Tests/test_imageops_usm.py Tests/test_file_mpo.py Tests/test_imagepalette.py Tests/test_image_mode.py Tests/test_image_copy.py Tests/test_file_pdf.py Tests/test_file_tar.py Tests/test_image_transpose.py Tests/test_file_sun.py Tests/test_imagefileio.py Tests/test_file_webp.py Tests/test_imagepath.py Tests/test_imagestat.py Tests/test_file_gif.py Tests/test_bmp_reference.py Tests/test_mode_i16.py Tests/test_file_palm.py Tests/test_imagedraw.py Tests/test_image_tobytes.py Tests/test_imageenhance.py Tests/test_image_point.py Tests/test_file_tga.py Tests/test_file_tiff_metadata.py Tests/test_file_cur.py Tests/test_imagemorph.py Tests/test_format_hsv.py Tests/test_imagefont.py Tests/test_shell_injection.py Tests/test_imagewin.py Tests/test_image_getpixel.py Tests/test_image_putpixel.py Tests/test_file_xbm.py Tests/test_image_offset.py Tests/test_image_rotate.py Tests/test_file_msp.py Tests/test_imagechops.py Tests/test_file_dcx.py Tests/test_file_spider.py Tests/test_file_iptc.py Tests/test_file_ico.py Tests/test_file_libtiff_small.py Tests/test_image_resize.py Tests/test_image_getbbox.py Tests/test_olefileio.py Tests/test_font_pcf.py Tests/test_image_draft.py Tests/test_font_bdf.py Tests/test_numpy.py Tests/test_imagegrab.py Tests/test_cffi.py Tests/test_image_split.py Tests/test_scipy.py Tests/test_util.py Tests/test_image_crop.py Tests/test_file_jpeg.py Tests/test_file_bmp.py Tests/test_image_load.py Tests/test_pickle.py Tests/test_image_convert.py Tests/test_imagemath.py Tests/test_image_quantize.py Tests/test_file_pcx.py ..S...make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Build killed with signal TERM after 300 minutes of inactivity See the build log at https://buildd.debian.org/status/fetch.php?pkg=pillowarch=mipsver=2.6.1-1stamp=1414045002 Cheers, Julien signature.asc Description: Digital signature
Bug#767211: mongodb-server: Link to mongodb.service not created on install
Package: mongodb-server Version: 1:2.4.10-2 Severity: normal Dear Maintainer, I installed mongodb and after next reboot, noticed it had not started automatically as I had expected. Digging into this, I found that the services which did start at boot (e.g. nginx), had their .service files symlinked from /etc/systemd/system/multi-user.target.wants/. However, mongodb had not. Systemd seems not to be aware of mongodb at all: `systemctl | grep -i mongo` does not show anything. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mongodb-server depends on: ii adduser 3.113+nmu3 ii libboost-filesystem1.55.0 1.55.0+dfsg-3 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libboost-thread1.55.0 1.55.0+dfsg-3 ii libc6 2.19-11 ii libgcc1 1:4.9.1-16 ii libgoogle-perftools42.2.1-0.2 ii libpcre31:8.35-3.1 ii libpcrecpp0 1:8.35-3.1 ii libsnappy1 1.1.2-3 ii libssl1.0.0 1.0.1j-1 ii libstdc++6 4.9.1-16 ii libv8-3.14.53.14.5.8-8 ii mongodb-clients 1:2.4.10-2 mongodb-server recommends no packages. mongodb-server 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#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid Cheers, Julien signature.asc Description: Digital signature
Bug#766956: postgresql: 9.4 not released upstream
On Mon, Oct 27, 2014 at 11:48:37AM +0100, Christoph Berg wrote: If so that'd solve the apparent problem. It won't prevent the following scenario though: - Jessie is released with PG 9.4.betaX - PG releases 9.4.betaX+1 which requires a dump/restore cycle due to a catalog bump (PG doesn't guarantuee catalog stability across betas as much as across released minors) - now people running PG on Debian STABLE need to dump/restore their clusters This was the last 9.4 catversion bump. Just FYI: Andrew Dunstan pushed: - Correct volatility markings of a few json functions. json_agg and json_object_agg and their associated transition functions should have been marked as stable rather than immutable, as they call IO functions indirectly. Changing this probably isn't going to make much difference, as you can't use an aggregate function in an index expression, but we should be correct nevertheless. json_object, on the other hand, should be marked immutable rather than stable, as it does not call IO functions. As discussed on -hackers, this change is being made without bumping the catalog version, as we don't want to do that at this stage of the cycle, and the changes are very unlikely to affect anyone. http://git.postgresql.org/pg/commitdiff/af2b8fd057213f4b1918b9581c63e0b00427573c So it's not like it can't happen. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767214: Garbaged in vbindiff output
Package: vbindiff Version: 3.0-beta4-1 Severity: important for some reason when using vbindiff from jessie the output contained garbage. Steps: $ wget https://www.debian.org/Pics/openlogo-50.png $ vbindiff openlogo-50.png openlogo-50.png - Hit 'Return' On wheezy nothing is displayed after: 07D0: 4E 44 AE 42 60 82 On jessie I get: 07D0: 4E 44 AE 42 60 82 ND.B`. 07E0: 0100: F6 7E 35 DE D5 B5 8D 13 97 D4 D3 26 EC 08 F4 91 .~5. ... 0110: 2F A7 FC 1A 32 91 4D 06 E6 00 EF 29 FF 46 38 5F /...2.M. ...).F8_ 0120: 43 46 7E 38 70 77 C4 8D 45 A5 54 F5 F7 07 81 2C CF~8pw.. E.T, 0130: 45 63 61 90 93 C8 54 08 74 D6 AB DD A6 AB DB DC Eca...T. t... 0140: 93 C0 4A 6F 85 6E 00 DF 54 05 55 1C 28 79 2E 90 ..Jo.n.. T.U.(y.. 0150: 07 B4 02 6E 8E 5F FB D4 91 85 C0 18 E0 84 EF DB ...n._.. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767213: flexpart: FTBFS on ppc64el with relocation truncated to fit:, R_PPC64_TOC16_HA against `.bss'
Package: flexpart Version: 9.02-9 Severity: normal Tags: patch X-Debbugs-Cc: bren...@br.ibm.com User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, The flexpart package FTBFS on ppc64el with the ... flexpart-9.02/partoutput_short.f90:145:(.text+0x6f0): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss' plumetraj.o: In function `plumetraj_': flexpart-9.02/plumetraj.f90:98:(.text+0x114): additional relocation overflows omitted from the output collect2: error: ld returned 1 exit status The patch includes the -mcmodel=large option to be enabled to get the package to build properly. Thanks for considering the patch! Thanks and regards, Brahadambal -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-trunk-powerpc64le (SMP w/32 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash --- flexpart-9.02.orig/makefile.ecmwf_gfortran +++ flexpart-9.02/makefile.ecmwf_gfortran @@ -6,7 +6,7 @@ FC = gfortran INCPATH = /usr/include LIBPATH1 = /usr/lib LIBPATH2 = -FFLAGS = $(FCFLAGS) -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) +FFLAGS = $(FCFLAGS) -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) -mcmodel=large LFLAGS = $(LDFLAGS) $(FFLAGS) -Wl,--as-needed -L$(LIBPATH2) -L$(LIBPATH1) -lgrib_api_f90 -lgrib_api -lm -ljasper MODPATH = /usr/include # --- flexpart-9.02.orig/makefile.gfs_gfortran +++ flexpart-9.02/makefile.gfs_gfortran @@ -7,7 +7,7 @@ FC = gfortran INCPATH = /usr/include LIBPATH1 = /usr/lib LIBPATH2 = -FFLAGS = $(FCFLAGS) -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) +FFLAGS = $(FCFLAGS) -O2 -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I$(INCPATH) -mcmodel=large LFLAGS:= $(LDFLAGS) $(FFLAGS) -L$(LIBPATH1) -Wl,--as-needed -lgrib_api_f90 -lgrib_api -lm -ljasper #
Bug#767197: debtags update --local fails
On Wed, Oct 29, 2014 at 08:34:38AM +0100, Jörg Sommer wrote:
debtags (1.12.3) wird eingerichtet ...
No such file or directory. Context:
writing item
Thank you for reporting the bug. That looks strange: the only exceptions
raised with a writing item context are after an fprintf, which I can't
see failing with No such file or directory. Also, in your stack trace
there are no write() calls failing.
The existence of /root/.debtags should be unrelated to that: I tried in
my system and it works fine without it:
# debtags update --local
# echo $?
0
# debtags --version
debtags version 1.12.3
# ls /root/.debtags
ls: cannot access /root/.debtags: No such file or directory
Looking with strace what's happening I see this:
I also don't see anything wrong in that strace: the only syscall that
doesn't seem to succeed is the stat() call, and the same stat() call
also fails in my system.
The difference seems to be here:
14217 23:46:55.005311 open(/var/lib/debtags/package-tags.b8J8Hh,
O_RDWR|O_CREAT|O_EXCL, 0600) = 4 0.69
14217 23:46:55.005432 fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
0.83
14217 23:46:55.005630 fstat(4, {st_dev=makedev(8, 2), st_ino=8524699,
st_mode=S_IFREG|0600, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2014/10/14-23:46:54,
st_mtime=2014/10/14-23:46:54, st_ctime=2014/10/14-23:46:54}) = 0 0.30
14217 23:46:55.005826 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2ac496751000 0.42
14217 23:46:55.005933 lseek(4, 0, SEEK_CUR) = 0 0.23
14217 23:46:55.006304 futex(0x2ac497d6f850, FUTEX_WAKE_PRIVATE, 2147483647) =
0 0.29
14217 23:46:55.006616 unlink(/var/lib/debtags/package-tags.b8J8Hh) = 0
0.000102
Where in my system it starts writing tag data after the lseek:
open(/var/lib/debtags/package-tags.VTKxIt, O_RDWR|O_CREAT|O_EXCL, 0600) = 4
fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff669665000
lseek(4, 0, SEEK_CUR) = 0
write(4, 0ad: uitoolkit::sdl, uitoolkit::..., 4096) = 4096
write(4, e::editing, use::text-formatting..., 4096) = 4096
Let's try and get a stack trace. Can you please try with gdb, like this:
export LANG=C
gdb --args debtags update --local
then in gdb:
break __cxa_throw
run
and when it stops, hopefully while trying to raise an exception:
where
quit
and send me the output of it?
Also, can you please send me the output of:
ls -la /var/lib/debtags
df /var/lib/debtags
Thanks!
Enrico
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org
signature.asc
Description: Digital signature
Bug#765176: nautilus: Nautilus shows bookmarks numerously
Package: nautilus Version: 3.14.0-1 Followup-For: Bug #765176 Dear Maintainer, the problem seems to me to be solved: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Changes in versions of packages nautilus depends on: ii libgail-3-03.14.3-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgtk-3-0 3.14.3-1 Changes in versions of packages nautilus recommends: ii gvfs-backends 1.22.1-1 ii librsvg2-common2.40.5-1 Regards WernerFP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766151: [PKG-OpenRC-Debian] Bug#766151: Bug#766151: openrc: tor service fails to start
On 10/29/2014 10:07 AM, hero...@gentoo.org wrote: Ritesh Raj Sarraf r...@researchut.com writes: On Tuesday 21 October 2014 01:35 PM, Ritesh Raj Sarraf wrote: tor |/lib/rc/sh/runscript.sh: 274: exec: /bin/bash: not found tor | * ERROR: tor failed to start The tor service works if the init script interpreter is changed from /bin/bash to /bin/sh, with /bin/sh symlinking to /bin/dash This seems to be a bug of tor. I agree. Besides, do you have /bin/bash on your system? Bash is on every Debian system, even though it may not be the default interpreter for /bin/sh. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
Hello Julien, thanks for the report. On Wed, Oct 29, 2014 at 10:38 AM, Julien Cristau jcris...@debian.org wrote: Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid I saw that happening before during the first round of 1.4.x uploads, but it seems it was fixed just by giving it back? https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=kfreebsd-i386 failed in 1.4.1~rc1 with the same error and then succeeded https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=s390x succeeded with 1.4.1~rc1 but failed in the last 2 uploads https://buildd.debian.org/status/logs.php?pkg=matplotlib 1.4.1~rc1 also failed on i386 and then went on correctly on the other upload I will look into it, but could it be something specific to those build machines and or build setup? Thanks, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767216: There is not enough free space on the device to save file
Package: bless Version: 0.6.0-4 Severity: grave AFAIK there is no way to use bless to edit and save a file. Steps from a jessie/amd64 setup: $ wget http://www.ece.rice.edu/~wakin/images/lena512.pgm $ bless lena512.pgm Directory '/home/mathieu/.config/bless/plugins' not found. Directory '/home/mathieu/.config/bless/plugins' not found. Directory '/home/mathieu/.config/bless/plugins' not found. Could not find file /home/mathieu/.config/bless/export_patterns. - Hit 'Suppr' (why not) - Hit 'Ctrl+S' A message box comes up saying: [...] Error saving file '/tmp/lena512.pgm' There is not enough free space on the device to save file 'auhnfpnt.bless' [...] Marking as grave since writing edited file, quite important for user (render package mostly unusable). Regards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657561: apt-get chokes on bad files, needs manual intervention to fix the situation
I'm chiming in, although I observed this on Ubuntu Precise (apt 0.8.16~exp12ubuntu10.21): W: GPG error: http://repo.i.bitbit.net precise Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key ftpmas...@ubuntu.com the reason for this was: root@backend:/var/lib/apt/lists# ls -l *Release* [...] -rw-r--r-- 1 root root 0 Jul 20 13:46 repo.i.bitbit.net_ubuntu_dists_precise_Release IMHO apt-get update should delete files it thinks are corrupt and retry the download before reporting the problem. alternatively apt-get clean could be more aggressive. -- kind regards, Kjetil T. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
On 29/10/14 11:54, Sandro Tosi wrote: Hello Julien, thanks for the report. On Wed, Oct 29, 2014 at 10:38 AM, Julien Cristau jcris...@debian.org wrote: Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid I saw that happening before during the first round of 1.4.x uploads, but it seems it was fixed just by giving it back? https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=kfreebsd-i386 failed in 1.4.1~rc1 with the same error and then succeeded https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=s390x succeeded with 1.4.1~rc1 but failed in the last 2 uploads https://buildd.debian.org/status/logs.php?pkg=matplotlib 1.4.1~rc1 also failed on i386 and then went on correctly on the other upload I will look into it, but could it be something specific to those build machines and or build setup? This also failed on i386 recently: https://buildd.debian.org/status/fetch.php?pkg=matplotlibarch=i386ver=1.4.1~rc1-1stamp=1413455146 It may be a race and not something specific to the buildds. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622394: Fix works on NFS clients but breaks NFS servers
Hi, I applied the fix given in message #10 to a few of our Jessie systems. I can confirm that it fixes the boot order problem on NFS clients that mount remote filesystems on boot (before the fix, it was trying to mount an NFS /home directory before rpcbind was started, which failed). However, the same fix seems to break NFS servers because it tries to start statd before rpcbind: Oct 29 09:48:49 drbl nfs-common[140]: Starting NFS common utilities: statd Oct 29 09:48:49 drbl nfs-common[140]: Not starting: portmapper is not running ... (warning). This failure to start later manifested as lockd: cannot monitor client errors. -- Chris Butler Zedcore Systems Ltd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767218: ktorrent does not gunzip IP Filter files anymore
Package: ktorrent
Version: 4.3.1-2
Severity: normal
Tags: upstream patch
Hi,
Please see attached patch this fixes the bug described at:
https://bugs.kde.org/show_bug.cgi?id=315239
.. This bug prevents the block lists in KTorrent from updating correctly.
Kitty
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (750, 'testing'), (700, 'testing'), (650, 'stable'), (600,
'stable'), (450, 'oldstable'), (400, 'oldstable'), (300, 'unstable'), (200,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ktorrent depends on:
ii kde-runtime 4:4.14.1-1+b1
ii ktorrent-data 4.3.1-2
ii libc6 2.19-12
ii libgcc1 1:4.9.1-16
ii libgeoip1 1.6.2-1
ii libkcmutils44:4.14.1-1+b1
ii libkdecore5 4:4.14.1-1+b1
ii libkdeui5 4:4.14.1-1+b1
ii libkdewebkit5 4:4.14.1-1+b1
ii libkdnssd4 4:4.14.1-1+b1
ii libkio5 4:4.14.1-1+b1
ii libknotifyconfig4 4:4.14.1-1+b1
ii libkparts4 4:4.14.1-1+b1
ii libkrosscore4 4:4.14.1-1+b1
ii libktorrent-l10n1.3.1-3
ii libktorrent51.3.1-3+b1
ii libkworkspace4abi2 4:4.11.12-2+b1
ii libnepomuk4 4:4.14.1-1+b1
ii libnepomukutils44:4.14.1-1+b1
ii libphonon4 4:4.8.0-3
ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-qt3support 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-sql 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtwebkit42.3.4.dfsg-3
ii libsolid4 4:4.14.1-1+b1
ii libsoprano4 2.9.4+dfsg-1.1
ii libstdc++6 4.9.1-16
ii libsyndication4 4:4.14.1-1
ii libtag1c2a 1.9.1-2.1
ii phonon 4:4.8.0-3
ktorrent recommends no packages.
Versions of packages ktorrent suggests:
ii krosspython 4:4.13.1-1
pn plasma-widget-ktorrent none
-- no debconf information
--- a/plugins/ipfilter/downloadandconvertjob.cpp 2013-01-15 04:12:24.0 +1100
+++ b/plugins/ipfilter/downloadandconvertjob.cpp 2014-10-25 02:22:58.300536134 +1100
@@ -94,7 +94,7 @@
active_job = 0;
if (j-error())
{
- Out(SYS_IPF|LOG_NOTICE) IP filter update failed: j-errorString() endl;
+ Out(SYS_IPF | LOG_NOTICE) IP filter update failed: j-errorString() endl;
if (mode == Verbose)
{
((KIO::Job*)j)-ui()-showErrorMessage();
@@ -104,31 +104,54 @@
QString msg = i18n(Automatic update of IP filter failed: %1, j-errorString());
notification(msg);
}
-
- setError(DOWNLOAD_FAILED);
+
+ setError(DOWNLOAD_FAILED);
emitResult();
return;
}
-
+
QString temp = kt::DataDir() + tmp- + url.fileName();
-
+
//now determine if it's ZIP or TXT file
- KMimeType::Ptr ptr = KMimeType::findByPath(temp);
- if (ptr-name() == application/zip)
+ KMimeType::Ptr ptr = KMimeType::findByFileContent(temp);
+ Out(SYS_IPF|LOG_NOTICE) Mimetype: ptr-name() endl;
+ if(ptr-name() == application/zip)
+ {
+ active_job = KIO::file_move(temp, QString(kt::DataDir() + QLatin1String(level1.zip)), -1, KIO::HideProgressInfo | KIO::Overwrite);
+ connect(active_job, SIGNAL(result(KJob*)), this, SLOT(extract(KJob*)));
+ }
+ else if(ptr-name() == application/x-7z-compressed)
{
- active_job = KIO::file_move(temp,QString(kt::DataDir() + QLatin1String(level1.zip)),-1,KIO::HideProgressInfo|KIO::Overwrite);
- connect(active_job,SIGNAL(result(KJob*)),this,SLOT(extract(KJob*)));
+ QString msg = i18n(7z files are not supported, url.prettyUrl());
+ if (mode == Verbose)
+KMessageBox::error(0, msg);
+ else
+notification(msg);
+
+ setError(UNZIP_FAILED);
+ emitResult();
}
- else if (ptr-name() == application/x-gzip || ptr-name() == application/x-bzip)
+ else if(ptr-name() == application/gzip || ptr-name() == application/x-bzip)
{
- active_job = new bt::DecompressFileJob(temp,QString(kt::DataDir() + level1.txt));
- connect(active_job,SIGNAL(result(KJob*)),this,SLOT(convert(KJob*)));
+ active_job = new bt::DecompressFileJob(temp, QString(kt::DataDir() + level1.txt));
+ connect(active_job, SIGNAL(result(KJob*)), this, SLOT(convert(KJob*)));
active_job-start();
}
+ else if(!KMimeType::isBinaryData(temp) || ptr-name() == text/plain)
+ {
+ active_job = KIO::file_move(temp, QString(kt::DataDir() + level1.txt), -1, KIO::HideProgressInfo | KIO::Overwrite);
+ connect(active_job, SIGNAL(result(KJob*)), this, SLOT(convert(KJob*)));
+ }
else
{
-
Bug#767217: please condider applying patch to fix arm64 build failure (and other things)
Package: gdcm
Version: 2.4.4-3
Severity: important
Tags: patch
Dear maintainer, this is the ubuntu delta, fixing arm64 build failure (by
disabling ACTIVIZ) and something else, like fixing python search directories
and a fix on pdf generation.
Not sure if all should be merged in debian, this is why I'm reporting the whole
diff (stripped of the changelog and some other useless-for-debian stuff).
Feel free to merge or drop at your own convenience!
diff -Nru gdcm-2.4.4/debian/control gdcm-2.4.4/debian/control
--- gdcm-2.4.4/debian/control 2014-09-24 14:41:14.0 +0200
+++ gdcm-2.4.4/debian/control 2014-10-29 12:03:37.0 +0100
@@ -9,7 +10,7 @@
uuid-dev, libz-dev, libexpat-dev, doxygen,
swig (= 2.0.7), cmake (= 2.8.9), libvtk5-dev, libcharls-dev, javahelper,
libopenjpeg-dev, default-jdk, php5-dev, php5-cli, libxml2-dev, libjson-c-dev,
- libpoppler-private-dev, libssl-dev, python-vtk, gccxml, libsocket++-dev,
libpapyrus3-dev,
+ libpoppler-private-dev, libssl-dev, python-vtk, gccxml [!arm64],
libsocket++-dev, libpapyrus3-dev,
libactiviz.net-cil [amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64
s390x],
mummy [amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x],
cli-common-dev (= 0.8~) [amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 powerpc
ppc64 s390x],
diff -Nru gdcm-2.4.4/debian/control.in gdcm-2.4.4/debian/control.in
--- gdcm-2.4.4/debian/control.in2014-09-30 13:02:57.0 +0200
+++ gdcm-2.4.4/debian/control.in2014-10-29 12:03:28.0 +0100
@@ -9,7 +10,7 @@
uuid-dev, libz-dev, libexpat-dev, doxygen,
swig (= 2.0.7), cmake (= 2.8.9), libvtk5-dev, libcharls-dev, javahelper,
libopenjpeg-dev, default-jdk, php5-dev, php5-cli, libxml2-dev, libjson-c-dev,
- libpoppler-private-dev, libssl-dev, python-vtk, gccxml, libsocket++-dev,
libpapyrus3-dev,
+ libpoppler-private-dev, libssl-dev, python-vtk, gccxml [!arm64],
libsocket++-dev, libpapyrus3-dev,
libactiviz.net-cil [@DEB_MONO_ARCHS@],
mummy [@DEB_MONO_ARCHS@],
cli-common-dev (= 0.8~) [@DEB_MONO_ARCHS@],
diff -Nru gdcm-2.4.4/debian/patches/disablepdfopt.patch
gdcm-2.4.4/debian/patches/disablepdfopt.patch
--- gdcm-2.4.4/debian/patches/disablepdfopt.patch 1970-01-01
01:00:00.0 +0100
+++ gdcm-2.4.4/debian/patches/disablepdfopt.patch 2014-10-29
11:55:34.0 +0100
@@ -0,0 +1,18 @@
+Description: disable optimizing PDF documentation
+ pdfopt is no longer available in ghostscript, see
+ http://bugs.ghostscript.com/show_bug.cgi?id=694099
+Bug: https://sourceforge.net/p/gdcm/bugs/292/
+Author: Dmitry Shachnev mity...@ubuntu.com
+Last-Update: 2013-06-02
+
+--- a/Utilities/doxygen/CMakeLists.txt
b/Utilities/doxygen/CMakeLists.txt
+@@ -96,7 +96,7 @@
+ # PDF building part:
+ # When building latex, we have to run a custom command to produce the pdf
file:
+ if(UNIX AND GDCM_PDF_DOCUMENTATION)
+-find_program(PDFOPT_EXECUTABLE pdfopt)
++find_program(PDFOPT_EXECUTABLE cp)
+ find_program(SED_EXECUTABLE sed)
+ find_package(LATEX REQUIRED)
+ mark_as_advanced(PDFOPT_EXECUTABLE SED_EXECUTABLE)
diff -Nru gdcm-2.4.4/debian/patches/fixpythonincludedirs.patch
gdcm-2.4.4/debian/patches/fixpythonincludedirs.patch
--- gdcm-2.4.4/debian/patches/fixpythonincludedirs.patch1970-01-01
01:00:00.0 +0100
+++ gdcm-2.4.4/debian/patches/fixpythonincludedirs.patch2014-10-29
11:45:36.0 +0100
@@ -0,0 +1,13 @@
+Index: gdcm-2.2.3/Wrapping/Python/CMakeLists.txt
+===
+--- gdcm-2.2.3.orig/Wrapping/Python/CMakeLists.txt 2013-05-30
15:38:42.061419753 +0200
gdcm-2.2.3/Wrapping/Python/CMakeLists.txt 2013-05-30 15:38:42.057419753
+0200
+@@ -60,7 +60,7 @@
+ else()
+ # just plain including pyconfig.h is working...until one crazy python dev
decide otherwise...
+ include_directories(
+-${PYTHON_INCLUDE_PATH}
++${PYTHON_INCLUDE_DIRS}
+ )
+ endif()
+ set_source_files_properties(gdcmswig.i PROPERTIES CPLUSPLUS ON)
diff -Nru gdcm-2.4.4/debian/patches/series gdcm-2.4.4/debian/patches/series
--- gdcm-2.4.4/debian/patches/series2014-10-06 09:08:33.0 +0200
+++ gdcm-2.4.4/debian/patches/series2014-10-29 11:48:59.0 +0100
@@ -2,3 +2,5 @@
fixhurd.patch
linkvtkdoc.patch
multiarch.patch
+fixpythonincludedirs.patch
+disablepdfopt.patch
diff -Nru gdcm-2.4.4/debian/rules gdcm-2.4.4/debian/rules
--- gdcm-2.4.4/debian/rules 2014-09-24 14:26:17.0 +0200
+++ gdcm-2.4.4/debian/rules 2014-10-29 12:03:19.0 +0100
@@ -26,6 +26,15 @@
endif
export LD_LIBRARY_PATH
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
+no_gccxml_architectures := arm64
+ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH),
$(no_gccxml_architectures)))
+ USE_ACTIVIZ = OFF
+else
+ USE_ACTIVIZ = ON
+endif
+
# deduce documentation option (build-indep target)
ifeq $(filter %-doc,$(shell dh_listpackages))
BUILDDOC = OFF
@@ -69,7 +78,7 @@
Bug#767219: Restarting NFS server while clients are connected causes locking errors
Package: src:linux Version: 3.16.5-1 Severity: normal We've been running into an issue with an NFS server running Jessie, where restarting NFS services whilst clients are connected causes locking problems, resulting in a flood of lockd: cannot monitor client errors. It appears to be the same bug that's been reported to Redhat here, which they've patched in their kernel: https://bugzilla.redhat.com/show_bug.cgi?id=1120850 Looks like that fix has been merged for upstream 3.18-1: http://git.linux-nfs.org/?p=trondmy/linux-nfs.git;a=commit;h=25641c0c8d72f3d235c022fd2c19181912c2ae8b It would be good if this could be added to Debian's 3.16 kernel if possible. -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=UUID=3075ba5f-aab4-4354-939b-46427c14d061 ro quiet ** Not tainted ** Kernel log: [0.405358] vda: vda1 vda2 vda5 [0.408876] FDC 0 is a S82078B [0.413917] virtio-pci :00:07.0: irq 45 for MSI/MSI-X [0.414016] virtio-pci :00:07.0: irq 46 for MSI/MSI-X [0.414077] virtio-pci :00:07.0: irq 47 for MSI/MSI-X [0.417719] virtio-pci :00:08.0: irq 48 for MSI/MSI-X [0.417764] virtio-pci :00:08.0: irq 49 for MSI/MSI-X [0.417804] virtio-pci :00:08.0: irq 50 for MSI/MSI-X [0.421966] virtio-pci :00:09.0: irq 51 for MSI/MSI-X [0.422028] virtio-pci :00:09.0: irq 52 for MSI/MSI-X [0.422135] virtio-pci :00:09.0: irq 53 for MSI/MSI-X [0.536863] ata2.01: NODEV after polling detection [0.537459] ata2.00: ATAPI: QEMU DVD-ROM, 1.1.2, max UDMA/100 [0.538387] ata2.00: configured for MWDMA2 [0.539403] scsi 1:0:0:0: CD-ROMQEMU QEMU DVD-ROM 1.1. PQ: 0 ANSI: 5 [0.553180] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray [0.553188] cdrom: Uniform CD-ROM driver Revision: 3.20 [0.553606] sr 1:0:0:0: Attached scsi CD-ROM sr0 [0.555803] sr 1:0:0:0: Attached scsi generic sg0 type 5 [0.632965] device-mapper: uevent: version 1.0.3 [0.633131] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com [0.672058] usb 1-1: new full-speed USB device number 2 using uhci_hcd [0.956523] usb 1-1: New USB device found, idVendor=0627, idProduct=0001 [0.956525] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5 [0.956527] usb 1-1: Product: QEMU USB Tablet [0.956528] usb 1-1: Manufacturer: QEMU 1.1.2 [0.956529] usb 1-1: SerialNumber: 42 [0.964319] hidraw: raw HID events driver (C) Jiri Kosina [0.973330] usbcore: registered new interface driver usbhid [0.973336] usbhid: USB HID core driver [0.976907] input: QEMU 1.1.2 QEMU USB Tablet as /devices/pci:00/:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input2 [0.977174] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Pointer [QEMU 1.1.2 QEMU USB Tablet] on usb-:00:01.2-1/input0 [1.304151] tsc: Refined TSC clocksource calibration: 2999.209 MHz [2.788010] raid6: sse2x1 10099 MB/s [2.856007] raid6: sse2x2 12754 MB/s [2.924008] raid6: sse2x4 14771 MB/s [2.924010] raid6: using algorithm sse2x4 (14771 MB/s) [2.924011] raid6: using intx1 recovery algorithm [2.924223] xor: measuring software checksum speed [2.964006]prefetch64-sse: 14800.000 MB/sec [3.004008]generic_sse: 10812.000 MB/sec [3.004010] xor: using function: prefetch64-sse (14800.000 MB/sec) [3.010324] Btrfs loaded [3.047866] EXT4-fs (vda5): mounted filesystem with ordered data mode. Opts: (null) [3.153991] lp: driver loaded but no devices found [3.157307] systemd-udevd[162]: starting version 215 [3.161636] ppdev: user-space parallel port driver [3.163489] fuse init (API version 7.23) [3.259575] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [3.259579] ACPI: Power Button [PWRF] [3.278429] [drm] Initialized drm 1.1.0 20060810 [3.286463] piix4_smbus :00:01.3: SMBus Host Controller at 0xb100, revision 0 [3.296689] snd_hda_intel :00:04.0: irq 54 for MSI/MSI-X [3.308307] [TTM] Zone kernel: Available graphics memory: 4098024 kiB [3.308309] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [3.308315] [TTM] Initializing pool allocator [3.308328] [TTM] Initializing DMA pool allocator [3.308904] [drm] fb mappable at 0xFC00 [3.308905] [drm] vram aper at 0xFC00 [3.308906] [drm] size 4194304 [3.308907] [drm] fb depth is 24 [3.308907] [drm]pitch is 3072 [3.308958] fbcon: cirrusdrmfb (fb0) is primary device [3.341820] Console: switching to colour frame buffer device 128x48 [3.350946] input: PC Speaker as /devices/platform/pcspkr/input/input5 [3.364262] cirrus :00:02.0: fb0: cirrusdrmfb frame buffer device [3.364262] cirrus
Bug#731815: [Pkg-libvirt-maintainers] Bug#731815: virsh: Unable to start any VM with custom cpu model
I did a fresh install from beta2 iso: http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd/debian-jessie-DI-b2-amd64-lxde-CD-1.iso Following steps to reproduce: After fresh install the /var/cache/libvirt/qemu/capabilities folder does not exist. Installed libvirt-bin and virtinst packages (without apt-get update). Then i see about 20 xml files in cache folder. virt-install --name test --memory 1024 --nodisk --pxe complains that default network is not running virsh net-start default and when i now run virt-install again, it gives me again error of CPU. I didnt touch qemu.conf and libvirtd.conf yet. couple of packages were installed from ISO, not sure which ones. apt-get update and upgrade shows that everything with libvirt is uptodate (1.2.9-3, python-libvirt 1.2.9-1). Am 29.10.2014 06:19, schrieb Guido Günther: That points to libvit no refreshing capabilities properly during the upgrade from wheezy to jessie. It should detect the changed qemu and do so. Can you add the information what versions (at least roughly) of qemu and libvirt you were ugrading from. The versions from stable or stable-backports? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767216: Alternate file ok
Control: severity -1 important
Actually I can save to a dummy file instead ('Save As') and it just
works. Would be nice to have in-place editing working though. Lowering
severity.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765448: [Pkg-libvirt-maintainers] Bug#765448:
Hi, Guido! Hmmm, almost missed the message, google spammed it. On Thu, Oct 16, 2014 at 9:52 PM, Guido Günther a...@sigxcpu.org wrote: On Thu, Oct 16, 2014 at 04:53:03PM +0300, Yauheni Kaliuta wrote: [...] In such cases responsible maintainers provide different binary packages with different features enabled. [...] What about sending patches to dlopen polkit and fall back to socket based auth if it's not available? Well, I'll have a look when get some free time. At the moment I'm not aware of the stuff. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767102: munin-plugins-core: df* plugins report warnings for special filesystems on kFreeBSD
Hi, On 28/10/14 23:38, Paul Wise wrote: On Debian wheezy kFreeBSD /sys appears to be sysfs not linsysfs. That's odd; I don't think there is such a thing as sysfs on FreeBSD. Actually what happened here is: * linsysfs gets mounted on /sys * linprocfs gets mounted on /proc And I guess because /proc/mounts is trying to emulate Linux, it pretends that /sys is sysfs - I guess some applications expect that: http://svnweb.freebsd.org/base/releng/10.1/sys/compat/linprocfs/linprocfs.c?view=annotatesortby=file#l365 But /proc/mounts still identifies /proc itself as linprocfs. If it didn't, then it would be ambiguous and even more confusing. 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#764152: assaultcube: update config.{sub,guess} to support new architectures
Package: assaultcube Followup-For: Bug #764152 Aurels' patch really ought to fix this problem, but in fact does not, because the packages runs configure in the clean target, and this happens before the config.sub/guess have been updated. The problem is the same whether autoreconf or autotools-dev is used. The problem seems to be this set of rules in src/Makefile (which is a static makefiles, not generated by automake) ../enet/Makefile: cd ../enet; ./configure --enable-shared=no --enable-static=yes clean-enet: ../enet/Makefile $(MAKE) -C ../enet/ distclean clean: clean-enet -$(RM) $(CLIENT_PCH) $(CLIENT_OBJS) $(SERVER_OBJS) $(MASTER_OBJS) ac_client$ # -$(MAKE) -C ../enet/ clean which runs configure even on clean This logic needs correcting. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730638: (no subject)
Can i have some news about this ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767220: dpkg-repack: better command line for --generate example
Package: dpkg-repack
Version: 1.38
Severity: normal
The manual states that --generate can be used to create the directory structure
for further manipulation.
However, the command line sample given to get around building a *.deb will
result in a hidden file called ..deb which is less than optimal. Here's a
better command line sample:
sudo dpkg-deb --build . ../$(echo $(grep Package DEBIAN/control | awk {'print
$2'})_$(grep Version DEBIAN/control | awk {'print $2'})_$(grep Arch
DEBIAN/control | awk {'print $2'}).deb)
You're welcome. :)
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (1001, 'testing'), (1001, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 3.16-3-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dpkg-repack depends on:
ii perl 5.20.1-2
dpkg-repack recommends no packages.
dpkg-repack 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
Archive: https://lists.debian.org/debian-bugs-dist
Bug#765327: lintian fails if the machine has a link-local IPv6 nameserver configured
Control: tags -1 patch
Here is a fix.
diff --git a/lib/Net/DNS/Resolver/Base.pm b/lib/Net/DNS/Resolver/Base.pm
index 4c963f8..8f82b62 100644
--- a/lib/Net/DNS/Resolver/Base.pm
+++ b/lib/Net/DNS/Resolver/Base.pm
@@ -249,7 +249,7 @@ sub read_config_file {
/^nameserver/ do {
my ( $keyword, @ip ) = grep defined, split;
- push @ns, map $_ eq '0' ? '0.0.0.0' : $_, @ip;
+ push @ns, map $_ eq '0' ? '0.0.0.0' : $_, grep !/%/,
@ip;
next;
};
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766802: linux-image-amd64: rt2800usb driver does not include 1b75:a200 USB id's as a supported device
Control: forwarded -1 net...@vger.kernel.org Cyril Brulebois k...@debian.org (2014-10-26): mmokr...@fold.natur.cuni.cz mmokr...@fold.natur.cuni.cz (2014-10-26): Package: linux-image-amd64 Version: 3.2+46 Severity: wishlist Dear Maintainer, I tried an old-ish OvisLink WN-200USB WiFi USB dongle but it is not picked up by linux kernel (tried initially 3.2+46 provided by Wheezy but later tried even 3.15.3 with same result. Thanks to Geoff Simmons I got it working. Below is whole recipe. Please contact linux kernel maintainers to add the missing id numbers. Hi, I don't want to stomp on anyone's toes but I have the attached patch ready to submit upstream if Debian kernel maintainers are happy with my doing so. So I've done that and Stanislaw replied[1] it would be nicer if the reporter could actually test the patch. Martin, any chance you could give it a shot to confirm? 1. http://marc.info/?l=linux-kernelm=141458072930743w=2 It seems you already built a vanilla kernel but I could probably build a patched linux-image-3.16-3-amd64 package for you if needed. Mraw, KiBi. signature.asc Description: Digital signature
Bug#767102: munin-plugins-core: df* plugins report warnings for special filesystems on kFreeBSD
On 28/10/14 23:33, Paul Wise wrote: I've now pushed this workaround to DSA's munin configs so the kFreeBSD hosts will soon disappear from the problems page. Currently, fasch.d.o is still listed there with problems; that buildd hasn't existed in months, it doesn't seem to even have a DNS entry. I guess it should be removed somewhere in the Munin master config? (not in the per-node puppet config). 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#760476: concerning 760476
Hi Nikos, hi Andreas, On Tue, 28 Oct 2014 19:11:28 +0100 Andreas Metzler wrote: On 2014-10-28 Nikos Mavrogiannopoulos n...@gnutls.org wrote: I think that the issue should be reassigned to cups and it should be modified to close the known file descriptors (stdin/stdout/stderr) instead of all open descriptors. Thanks for the explanation. re-assigning. (I will subscribe to the bug-report to keep me updated) Thanks to you two for the investigation; I've brought the issue back up to CUPS's bugtracker, where Michael Sweet wrote on https://www.cups.org/str.php?L4484 : So it looks like you also need to fix GNU TLS to only open /dev/urandom when gnutls_global_init() is called and not before. It appears there's a disagreement between CUPS and GnuTLS on how the file descriptors should be managed. It would be nice if one of you could have the conversation with Michael directly on the CUSP tracker, without me playing the messenger. Nikos: would that be imaginable? TIA, cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767102: [Packaging] Bug#767102: munin-plugins-core: df* plugins report warnings for special filesystems on kFreeBSD
Hi Steven, On Mittwoch, 29. Oktober 2014, Steven Chamberlain wrote: And I guess because /proc/mounts is trying to emulate Linux, it pretends that /sys is sysfs - I guess some applications expect that: http://svnweb.freebsd.org/base/releng/10.1/sys/compat/linprocfs/linprocfs.c ?view=annotatesortby=file#l365 But /proc/mounts still identifies /proc itself as linprocfs. If it didn't, then it would be ambiguous and even more confusing. the best way to find out is to debug+fix the plugins, which is really easy: apt-get install munin munin-node while $problems ; do munin-run df vi /etc/munin/plugins/df done (Note that /etc/munin/plugins/df is a link to /usr so unless you replace the link with a copy your fixes will get overwritten on upgrades.) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#767138: fftw3: runtime detection of NEON is perhaps broken
A few comments.
I'm not sure if the disassembly is the right one. Supposedly it is in a
function called fftwf_guru64_kosherp, but it should be in
really_have_neon.
There I would expect that the actual disassembly results in the the
signal SIGILL not being reset and return 1 always being executed. Then
the error pattern would make sense. I will check this tonight when I
have access to my ARM hardware.
Regarding the use of intrinsics: AFAICS in configure.ac --with-neon
always sets HAVE_NEON as define and adds the flag -mfpu=neon.
In addition the gcc manpage says:
If the selected floating-point hardware includes the NEON extension
(e.g. -mfpu=neon), note that floating-point operations are not generated
by GCC's auto-vectorization pass unless -funsafe-math-optimizations is
also specified.
With this in mind I would suggest the attached patch.
Best
Gert
--- simd-support/neon.c.old 2014-10-29 12:57:25.627329195 +0100
+++ simd-support/neon.c 2014-10-29 13:02:34.465717330 +0100
@@ -23,8 +23,23 @@
#if HAVE_NEON
-/* check for an environment where signals are known to work */
-#if defined(unix) || defined(linux)
+
+/* check for an environment where getauxval exists */
+#if defined(linux)
+ #include sys/auxv.h
+
+ int X(have_simd_neon)(void)
+ {
+ static int init = 0, res;
+ if (!init) {
+ res = !!(getauxval(AT_HWCAP) HWCAP_ARM_NEON);
+ init = 1;
+ }
+ return res;
+ }
+
+/* otherwise check for signals */
+#elif defined(unix)
# include signal.h
# include setjmp.h
@@ -44,10 +59,9 @@
signal(SIGILL, oldsig);
return 0;
} else {
- /* paranoia: encode the instruction in binary because the
- assembler may not recognize it without -mfpu=neon */
- /*asm volatile (vand q0, q0, q0);*/
- asm volatile (.long 0xf2000150);
+/* --with-neon sets HAVE_NEON and -mfpu=neon, so we are save */
+ asm volatile (vand q0, q0, q0);
+
signal(SIGILL, oldsig);
return 1;
}
signature.asc
Description: This is a digitally signed message part
Bug#764152: assaultcube: update config.{sub,guess} to support new architectures
Package: assaultcube Followup-For: Bug #764152 Actually aurel's patch does work. I typoed things. However the clean logic was broken so I've fixed that too. And I've also made dh-autoreconf work, as this is good policy. Attached is the patch for that, which I shall NMU to delayed/5. Hope that's OK diff -Nru assaultcube-1.1.0.4+dfsg2/debian/autoreconf assaultcube-1.1.0.4+dfsg2/debian/autoreconf --- assaultcube-1.1.0.4+dfsg2/debian/autoreconf 1970-01-01 00:00:00.0 + +++ assaultcube-1.1.0.4+dfsg2/debian/autoreconf 2014-10-29 12:03:10.0 + @@ -0,0 +1 @@ +source/enet \ No newline at end of file diff -Nru assaultcube-1.1.0.4+dfsg2/debian/changelog assaultcube-1.1.0.4+dfsg2/debian/changelog --- assaultcube-1.1.0.4+dfsg2/debian/changelog 2011-10-30 14:00:26.0 + +++ assaultcube-1.1.0.4+dfsg2/debian/changelog 2014-10-29 11:32:05.0 + @@ -1,3 +1,10 @@ +assaultcube (1.1.0.4+dfsg2-1.1) unstable; urgency=low + + * Non-maintainer upload. + * dh-autoreconf to support new architectures (Closes: 764152) + + -- Wookey woo...@debian.org Wed, 29 Oct 2014 05:01:52 + + assaultcube (1.1.0.4+dfsg2-1) unstable; urgency=low * Correct license in lintian override comment diff -Nru assaultcube-1.1.0.4+dfsg2/debian/control assaultcube-1.1.0.4+dfsg2/debian/control --- assaultcube-1.1.0.4+dfsg2/debian/control 2011-10-30 13:51:20.0 + +++ assaultcube-1.1.0.4+dfsg2/debian/control 2014-10-29 11:54:19.0 + @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Uploaders: Martin Erik Werner martinerikwer...@gmail.com -Build-Depends: debhelper (= 7.0.50~), autotools-dev, libsdl-image1.2-dev, +Build-Depends: debhelper (= 7.0.50~), dh-autoreconf, libsdl-image1.2-dev, libsdl1.2-dev, libgl1-mesa-dev, zlib1g-dev, libopenal-dev, libvorbis-dev Standards-Version: 3.9.2 Vcs-Svn: svn://svn.debian.org/svn/pkg-games/non-free/packages/trunk/assaultcube/ diff -Nru assaultcube-1.1.0.4+dfsg2/debian/patches/20-fix-clean-target.patch assaultcube-1.1.0.4+dfsg2/debian/patches/20-fix-clean-target.patch --- assaultcube-1.1.0.4+dfsg2/debian/patches/20-fix-clean-target.patch 2011-10-30 13:50:05.0 + +++ assaultcube-1.1.0.4+dfsg2/debian/patches/20-fix-clean-target.patch 2014-10-29 11:36:49.0 + @@ -7,17 +7,30 @@ Forwarded: https://sourceforge.net/tracker/?func=detailaid=3430222group_id=123597atid=697091 Last-Update: 2011-10-28 a/source/src/Makefile -+++ b/source/src/Makefile -@@ -128,9 +128,9 @@ +Index: assaultcube-1.1.0.4+dfsg2/source/src/Makefile +=== +--- assaultcube-1.1.0.4+dfsg2.orig/source/src/Makefile 2014-10-29 05:01:42.0 + assaultcube-1.1.0.4+dfsg2/source/src/Makefile 2014-10-29 11:36:30.115453061 + +@@ -127,10 +127,10 @@ + libenet: ../enet/Makefile -$(MAKE) -C ../enet all - clean-enet: ../enet/Makefile +-clean-enet: ../enet/Makefile - $(MAKE) -C ../enet/ clean -+ $(MAKE) -C ../enet/ distclean ++clean-enet: ++ -$(MAKE) -C ../enet/ distclean -clean: +clean: clean-enet -$(RM) $(CLIENT_PCH) $(CLIENT_OBJS) $(SERVER_OBJS) $(MASTER_OBJS) ac_client ac_server ac_master # -$(MAKE) -C ../enet/ clean +@@ -172,7 +172,7 @@ + + master: libenet $(MASTER_OBJS) + $(CXX) $(CXXFLAGS) -o ac_master $(MASTER_OBJS) $(SERVER_LIBS) +- ++ + client_install: client + install -D ac_client ../../bin_unix/$(PLATFORM_PREFIX)_client + #ifneq (,$(STRIP)) diff -Nru assaultcube-1.1.0.4+dfsg2/debian/rules assaultcube-1.1.0.4+dfsg2/debian/rules --- assaultcube-1.1.0.4+dfsg2/debian/rules 2011-10-28 12:45:04.0 + +++ assaultcube-1.1.0.4+dfsg2/debian/rules 2014-10-29 11:55:38.0 + @@ -6,7 +6,7 @@ dh_auto_clean %: - dh $@ --sourcedirectory=source/src + dh $@ --with autoreconf --sourcedirectory=source/src VER=$(shell dpkg-parsechangelog | sed -rne 's,^Version: ([^-+]+).*,\1,p') DEB_VER=$(shell dpkg-parsechangelog | sed -rne 's,^Version: ([^-]+).*,\1,p')
Bug#767221: RFS: zeal/0~20141027-1
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package zeal * Package name: zeal Version : 0~20141027-1 Upstream Author : 2013-2014 Jerzy Kozera * URL : http://zealdocs.org/ * License : GPL-3+, LGPL-2.1+, GPL-2+ Section : utils It builds those binary packages: zeal - Simple offline API documentation browser zeal-dbg - Debug symbols for zeal To access further information about this package, please visit the following URL: http://mentors.debian.net/package/zeal Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/z/zeal/zeal_0~20141027-1.dsc -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-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 -- ChangZhuo Chen (陳昌倬) czc...@gmail.com http://czchen.info/ Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D signature.asc Description: Digital signature
Bug#767222: preseeding of daily snapshot of debian jessie fails
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 2014-10-29 Machine: packer initiated boot of netinst.iso in vmware fusion 7 on Mac OS X 10.10) Processor: vmware (Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz) Memory: 512MB Partitions: machine doesn't get installed Output of lspci -knn (or lspci -nn): machine doesn't get installed Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: in a Packer setup we are preseeding the netinst.iso from Jessie Beta 2 - it works well until it tries to download header files to linux-3.14-something (which in beta 2 is current kernel) but no longer exists upstream. (we need the header files to build vmware-tools for the packer image) Then we try to use daily snapshot of netinst.iso http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso but our preseeding then fails and stops on “Select a language” (see attached screenshot) so something has changed? We’ve tried a lot of preseeding options without finding the right one - is this a bug, or has something changed? our preseeding file: http://pastebin.com/q1B6jwW4 the way we iniate packer (and preseeding): http://pastebin.com/gHm06TnY PS: not sure where in the above [] questions the installation stalls? So the [O]'s might not be right. PPS: The presseding file works on beta 2 still (except for the missing package kernel header package) -- Lasse Aagren DTU Library --- Technical University of Denmark Technical Information Center of Denmark Anker Engelunds Vej 1 Building 101D 2800 Kgs. Lyngby Direct +45 45257229 Mobile +45 40516542 l...@dtic.dtu.dk http://www.dtic.dtu.dk/
Bug#767223: Dont append kernel params for isolinux/deskop filesin Jessie
Package: debian-cd version: 3.1.16 Current Debian installer removed desktop folder under isolinux and merged it to head. But the debian-cd still searches for the desktop/*cfg files under isolinux folder. The attached patch removes the search of desktop folder under Jessie. -- Regards., Prema S From 05cd81c42768a93800846f3f6bd31b28f91b685c Mon Sep 17 00:00:00 2001 From: Prema S pre...@cdac.in Date: Wed, 29 Oct 2014 17:50:57 +0530 Subject: [PATCH] Do not look for isolinux/desktop/*cfg files for appending kernel params for Jessie --- tools/boot/jessie/boot-x86 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/boot/jessie/boot-x86 b/tools/boot/jessie/boot-x86 index e42dee0..bc549ac 100644 --- a/tools/boot/jessie/boot-x86 +++ b/tools/boot/jessie/boot-x86 @@ -364,7 +364,7 @@ sed -i s|built on|built $BUILD_DATE; d-i| boot$N/isolinux/f1.txt if [ -n $KERNEL_PARAMS ]; then # Substitute custom kernel params into the isolinux config file(s) - for file in boot$N/isolinux/*.cfg boot$N/isolinux/desktop/*.cfg; do + for file in boot$N/isolinux/*.cfg ; do case $(basename $file) in instsel.cfg) continue ;; -- 2.1.1
Bug#767109: nvidia-driver: fs-uae (Amiga Emulator) segfault with nvidia-driver installed on Jessi
On 2014-10-29 08:08, Carsten Stengel wrote: This is an upstream bug. Probably using memcpy() for overlapping arguments. memmove() must be used in this case. Please report this directly to NVIDIA: On the Upstreamwebsite i found a workaround: __GL_WRITE_TEXT_SECTION=0 fs-uae I have no clue what this variable makes, but it works. Maybe it helps to find the bug? I have no idea about this either. Even if there is a workaround, the issue should be brought to the attention of NVIDIA. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767224: scilab: Empty plot window when calling plot()
Package: scilab Version: 5.5.1-1 Severity: normal Tags: upstream Dear Maintainer, I recently updated my Debian install to Debian Testing (coming from Debian Stable) and I ran a scilab script which ran fine on my previous install. The script contains a couple of plot() functions at the end preceded by figure() functions. No errors or warnings are given in the Scilab console. The plot() functions are just plot(x,y) without specific options. The /var/log/messages caused by replicating the plot() command seem to indicate problems concerning OpenGL: Oct 29 12:33:00 nico-t61 gnome-session[1467]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0100f (Edit Entry) Oct 29 12:33:00 nico-t61 gnome-session[1467]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0100f (Edit Entry) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: java.lang.reflect.InvocationTargetException Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue.invokeAndWait(EventQueue.java:1276) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue.invokeAndWait(EventQueue.java:1251) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1347) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.SwingView.updateObject(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.graphic_objects.graphicController.GraphicController$2.run(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.graphic_objects.graphicController.GraphicController.objectUpdate(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.graphic_objects.graphicController.GraphicController.setGraphicObjectRelationship(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.graphic_objects.builder.Builder.cloneAxesModel(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.graphic_objects.builder.Builder.createNewFigureWithAxes(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: Caused by: javax.media.opengl.GLException: Profile GL_DEFAULT is not available on X11GraphicsDevice[type .x11, connection :0, unitID 0, handle 0x0, owner false, ResourceToolkitLock[obj 0x57285f7e, isOwner false, 1b9575e6, 716f5d2f[count 0, qsz 0, owner NULL]]], but: [] Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at javax.media.opengl.GLProfile.get(GLProfile.java:901) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at javax.media.opengl.GLProfile.getDefault(GLProfile.java:632) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at javax.media.opengl.awt.GLJPanel.init(GLJPanel.java:350) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at javax.media.opengl.awt.GLJPanel.init(GLJPanel.java:304) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at javax.media.opengl.awt.GLJPanel.init(GLJPanel.java:295) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.bridge.canvas.SwingScilabCanvasImpl$SafeGLJPanel.init(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.bridge.canvas.SwingScilabCanvasImpl$SafeGLJPanel.init(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.bridge.canvas.SwingScilabCanvasImpl.createOpenGLComponent(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.bridge.canvas.SwingScilabCanvas.init(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.bridge.tab.SwingScilabDockablePanel.addMember(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.SwingView.updateFigureChildren(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.SwingView.updateObjectOnEDT(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at org.scilab.modules.gui.SwingView$4.run(Unknown Source) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:302) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue.access$200(EventQueue.java:103) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue$3.run(EventQueue.java:694) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue$3.run(EventQueue.java:692) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.security.AccessController.doPrivileged(Native Method) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) Oct 29 12:33:35 nico-t61 scilab.desktop[15391]: at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) Oct 29
Bug#717058: Cannot set nonstandard baudrates on /dev/ttyACMn devices
Package: pyserial
Version: 2.6-1.1
Followup-For: Bug #717058
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch
*** /tmp/tmpYJUV0X/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
* Adding patch for accepting any speed (Debian #717058)
- http://sourceforge.net/p/pyserial/patches/28/
Thanks for considering the patch.
-- System Information:
Debian Release: jessie/sid
APT prefers utopic-updates
APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500,
'utopic-proposed'), (500, 'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-23-generic (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
diff -u pyserial-2.6/debian/changelog pyserial-2.6/debian/changelog
diff -u pyserial-2.6/serial/serialposix.py pyserial-2.6/serial/serialposix.py
--- pyserial-2.6/serial/serialposix.py
+++ pyserial-2.6/serial/serialposix.py
@@ -36,26 +36,25 @@
def device(port):
return '/dev/ttyS%d' % port
-ASYNC_SPD_MASK = 0x1030
-ASYNC_SPD_CUST = 0x0030
+TCGETS2 = 0x802C542A
+TCSETS2 = 0x402C542B
+BOTHER = 0o01
def set_special_baudrate(port, baudrate):
+# right size is 44 on x86_64, allow for some growth
import array
-buf = array.array('i', [0] * 32)
+buf = array.array('i', [0] * 64)
# get serial_struct
-FCNTL.ioctl(port.fd, TERMIOS.TIOCGSERIAL, buf)
-
-# set custom divisor
-buf[6] = buf[7] / baudrate
-
-# update flags
-buf[4] = ~ASYNC_SPD_MASK
-buf[4] |= ASYNC_SPD_CUST
+FCNTL.ioctl(port.fd, TCGETS2, buf)
+# set custom speed
+buf[2] = ~TERMIOS.CBAUD
+buf[2] |= BOTHER
+buf[9] = buf[10] = baudrate
# set serial_struct
try:
-res = FCNTL.ioctl(port.fd, TERMIOS.TIOCSSERIAL, buf)
+res = FCNTL.ioctl(port.fd, TCSETS2, buf)
except IOError:
raise ValueError('Failed to set custom baud rate: %r' % baudrate)
Bug#762056: d-i.debian.org: update jenkins job to use daily-build-overview
Hi, On Donnerstag, 18. September 2014, Cyril Brulebois wrote: It'd probably a good idea to update this jenkins job: https://jenkins.debian.net/view/d-i_misc/job/d-i_parse_build_logs/ to use this page instead: http://d-i.debian.org/daily-images/daily-build-overview.html Done. There are now 15 jobs like https://jenkins.debian.net/job/d-i_overview_sparc/ running at 0 * * * * * parsing the above URL. If an arch has missed or failed builds, the first time this is detected, #debian-boot is notified. I haven't set up email notification, if you want that please tell me. I hope there will be a notification too, once it's succeeds again, but as I had to change the jenkins email plugin I don't know for sure yet ;) BTW, I've noticed one glitch in the overview page, currently that page says Architectures with missing build: sparc and sparc is a link to http://d- i.debian.org/daily-images/daily-build-overview.html#sparc and there I can see three successful builds but there is no indication which build is missing Please close the bug if you think that's appropriate or tell me what's missing. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#766921: [Piuparts-devel] Bug#766921: piuparts fails with ValueError: too many values to unpack when dpkg prints a warning
Hi Simon, On Sonntag, 26. Oktober 2014, Simon Fondrie-Teitler wrote: When running piuparts, if sh or dkpg return warnings, they get included in the output that piuparts tries to parse and it prints a stack trace. indeed, thanks for your bug report! I'm not sure why gcc is not found, that may be its own bug. I have no idea neither... Further help and patches very much welcome! ;) I've noticed you're running piuparts on sid, I suspect the problem exist in wheezy (maybe just in theory..) too but dpkg behaves differently there... cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#762056: d-i.debian.org: update jenkins job to use daily-build-overview
Holger Levsen hol...@layer-acht.org (2014-10-29): It'd probably a good idea to update this jenkins job: https://jenkins.debian.net/view/d-i_misc/job/d-i_parse_build_logs/ to use this page instead: http://d-i.debian.org/daily-images/daily-build-overview.html Done. There are now 15 jobs like https://jenkins.debian.net/job/d-i_overview_sparc/ running at 0 * * * * * parsing the above URL. If an arch has missed or failed builds, the first time this is detected, #debian-boot is notified. I haven't set up email notification, if you want that please tell me. I hope there will be a notification too, once it's succeeds again, but as I had to change the jenkins email plugin I don't know for sure yet ;) Thanks, we'll see how it goes. We can probably follow up on this bug report if some tweaks are needed (so let's keep it open for a while)? BTW, I've noticed one glitch in the overview page, currently that page says Architectures with missing build: sparc and sparc is a link to http://d- i.debian.org/daily-images/daily-build-overview.html#sparc and there I can see three successful builds but there is no indication which build is missing Missing as in the last build we've got is now considered outdated and we haven't received a newer one in the meanwhile. That matches white areas on the graphs, and red timestamps. Mraw, KiBi. signature.asc Description: Digital signature
Bug#767225: regex: don't deref NULL upon heap allocation failure
Package: libc6 Version: 2.19-11 Severity: serious please backport the fix for https://sourceware.org/bugzilla/show_bug.cgi?id=17150 -- Mit freundlichen Grüßen Bernd Zeimetz Systems Engineer Debian Developer conova communications GmbH Web| http://www.conova.com/ E-Mail | b.zeim...@conova.com Zentrale Salzburg Karolingerstraße 36A 5020 Salzburg Tel | +43 (0) 662 22 00 - 313 Fax | +43 (0) 662 22 00 - 209 Es gelten die Allgemeinen Geschäftsbedingungen der conova communications GmbH, http://www.conova.com/de/agb/ smime.p7s Description: S/MIME cryptographic signature
Bug#767226: icedove: 'Checking Server Capabilities' Verification problem
Package: icedove Version: 31.1.2-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Previous apt-get upgrade on testing/jessie (standard repository) three days ago led to to the situation, that the mail server is not reachable any longer. It continiously states 'checking server capabilities' without successfully connecting - no server settings were changed from my side. * What exactly did you do (or not do) that was effective (or ineffective)? Until now, I couldn't find the issue, which might be related to icedove itself since upon deleting and creating a new account within the account manager the program states, that the password or username of the used server are not correct. Horde webmail applications with the same login work. Also testing another e-mail account on a different provider did not work, Horde webmail for the alternative mail account did work once more. Also the usage of evolution mail client with standard configuration did work. * What was the outcome of this action? None * What outcome did you expect instead? None *** Thank you for your support, best regards! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.4 ii fontconfig2.11.0-6.1 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-12 ii libcairo2 1.12.16-5 ii libdbus-1-3 1.8.8-2 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-1.1 ii libffi6 3.1-2 ii libfontconfig12.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-16 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgtk2.0-0 2.24.25-1 ii libhunspell-1.3-0 1.3.3-3 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1 ii libpango-1.0-01.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpangoft2-1.0-0 1.36.8-2 ii libpixman-1-0 0.32.6-3 ii libsqlite3-0 3.8.7-1 ii libstartup-notification0 0.12-4 ii libstdc++64.9.1-16 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxrender1 1:0.9.8-1 ii libxt61:1.1.4-1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2 Versions of packages icedove recommends: ii hunspell-de-at [hunspell-dictionary] 20131206-5 ii hunspell-de-ch [hunspell-dictionary] 20131206-5 ii hunspell-de-de [hunspell-dictionary] 20131206-5 ii hunspell-en-us [hunspell-dictionary] 20070829-6 Versions of packages icedove suggests: pn fonts-lyx none ii libgssapi-krb5-2 1.12.1+dfsg-10 -- 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#726492: normal or wishlist
control: tags -1 normal # I fail to see what's still important about this bug... signature.asc Description: This is a digitally signed message part.
Bug#760770: gcc-4.9: fails to build cross-compiler package
On 28 Oct 2014 20:00, Helmut Grohne hel...@subdivi.de wrote: Control: retitle -1 fails to cross build libphobos when setting with_deps_on_target_arch_pkgs=yes Control: tags -1 = patch Ian Jackson suggested that I should take care of this. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766708#68 On Tue, Sep 09, 2014 at 07:24:19PM +0200, Rico Rommel wrote: libphobos-cross-ma-libdir.diff corrects the installdir in libphobos and fix-rules includes the patch into rules.patch This should not be a separate patch but rather integrated into cross-ma-install-location.diff. Once it sits in that patch, it is guaranteed to not affect the native build or the supported default cross toolchain build, because neither use that patch. I am attaching the updated patch. Helmut Is this something that should be pushed upstream too? Iain.
Bug#767227: lsyncd: Crash and/or code execution on `, $, in file names
Package: lsyncd
Version: 2.0.7-3
Severity: important
Tags: security patch
cf. upstream bug report and fix at
https://github.com/axkibe/lsyncd/issues/220
This is the same patch backported to the lsyncd version in stable.
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lsyncd depends on:
ii libc62.13-38+deb7u4
ii liblua5.1-0 5.1.5-4+deb7u1
ii lua5.1 5.1.5-4+deb7u1
ii rsync3.0.9-4
lsyncd recommends no packages.
lsyncd suggests no packages.
-- no debconf information
Sanitize mv arguments:
1. Fixes crashes on file names containing `, $ or
2. Also prevents shell execution of ``, $() … in file names, which can be
used to gain remote shell access as lsyncd's (target) user.
Index: lsyncd-2.0.7/default-rsyncssh.lua
===
--- lsyncd-2.0.7.orig/default-rsyncssh.lua 2012-02-16 08:24:20.0 +0100
+++ lsyncd-2.0.7/default-rsyncssh.lua 2014-10-29 13:59:51.165553255 +0100
@@ -29,14 +29,17 @@
-- makes move local on host
-- if fails deletes the source...
if event.etype == 'Move' then
- log('Normal', 'Moving ',event.path,' - ',event2.path)
+ local path1 = event.path:gsub ('', '\\'):gsub ('`', '\\`'):gsub ('%$','\\%$')
+ local path2 = event2.path:gsub ('', '\\'):gsub ('`', '\\`'):gsub ('%$','\\%$')
+ log('Normal', 'Moving ',path1,' - ',path2)
+
spawn(event, '/usr/bin/ssh',
config.host,
'mv',
-'\' .. config.targetdir .. event.path .. '\',
-'\' .. config.targetdir .. event2.path .. '\',
+'\' .. config.targetdir .. path1 .. '\',
+'\' .. config.targetdir .. path2 .. '\',
'||', 'rm', '-rf',
-'\' .. config.targetdir .. event.path .. '\')
+'\' .. config.targetdir .. path1 .. '\')
return
end
Bug#713331: sphinxsearch: FTBFS: [automake-1.13 warning: linking libraries using a, non-POSIX]
On Tue, 21 Oct 2014 18:36:58 +0530 Brahadambal Srinivasan la...@linux.vnet.ibm.com wrote: Package: sphinxsearch Version: 2.0.4-1.1 Followup-For: Bug #713331 Tags: patch X-Debbugs-Cc: bren...@br.ibm.com User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Dear Maintainer, The package sphinxsearch fails to build on ppc64le, because of changes required in libtool, aclocal.m4 and configure.ac. This patch includes autotools-dev and a couple of changes in configure.ac to the package so that it builds correctly. Thanks for considering the patch! I tested your patch on mips64el, it works well. Thanks and regards, Brahadambal -- System Information: *** End of the template - remove these template lines *** Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-trunk-powerpc64le (SMP w/32 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) 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#766039: please document debug-shell.service in README.Debian
Hey Zbyszek, Zbigniew Jędrzejewski-Szmek [2014-10-29 13:42 +0100]: I'd change s/then immediately run... again/then immediately run... afterwards/ in the third paragraph. Some people might literally do it right after enabling it. In the fourth paragraph, I'd also advertise systemctl list-jobs. Indeed, thanks for pointing out! http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=8178d8db Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
