Bug#793659: RFS: ori/0.8.1+ds1-1 [ITP]
I am looking for a sponsor for my package ori Hi! I'm not a DD, so I can't sponsor your package, but I had a look, and here are some notes: d/changelog: -The only point you really need is the Initial release line d/copyright: -For the Source: field, you accidentally wrote http://http://ori.scs.stanford.edu/ -You forgot to add a license section for the MIT license. d/patches: -Some patches don't have author/last-update information. -You should forward to upstream the patches that they can use. General: -Your chances of finding a sponsor will greatly increase if you use a VCS for the Debian packaging. You can then reference this using the Vcs-Browser/Vcs-Git sections in d/control. Good luck getting ori into Debian, Riley Baird pgpd4wzpSALng.pgp Description: PGP signature
Bug#787582: VDPAU needed
On Sun, 26 Jul 2015 00:14:01 -0700 Vincent Cheng vch...@debian.org wrote: Hi Julien, On Sat, Jul 25, 2015 at 11:50 PM, Julien Aubin jul.au...@laposte.net wrote: Hi, In that case could you please also put the libvdpau1 and libvdpau1:i386 packages in experimental ? No, because AFAIK packages in experimental can't share the same version as a package already uploaded to sid (because packages belonging to the latter suite supersede packages in experimental with the same/older versions). They're actually required to install nvidia-driver 352 and the only way we currently have to install these updates is to pin these packages from testing. (And actually we'd need them in backports) If it helps, I can upload src:libvdpau to jessie-backports. Regards, Vincent Hi Vincent, Yes this would be really great as it breaks recent versions of the NVidia driver and it will be needed anyway. Rgds
Bug#792614: RM: Haskell package spring cleanup
Control: tag -1 - moreinfo Dear Scott, Am Sonntag, den 26.07.2015, 00:33 -0400 schrieb Scott Kitterman: On Thursday, July 16, 2015 08:04:08 PM Joachim Breitner wrote: Package: ftp.debian.org Severity: normal Dear ftp-masters, the Debian Haskell Group has identified a set of 106 packages that are probably not worth keeping in Debian. I hope you don’t mind me not opening 106 separate bug reports about that :-) ... According to dak rm -R -n, with my dak patch from #792578 applied, there are no reverse dependency problems. Thanks, Joachim ¹ a few packages, like haskell-cgi, cannot be removed at that point yet, but will follow soon. Did your check include build-depends? According to dak the following issues remain: As I said, I checked it with the dak patch #792578 applied. What you are seeing is lots of false positive due to old source packages still lying around. I guess you can either apply the patch, or remove sparc and decruft the archive to verify that :-) yi: libghc-cautious-file-dev (= 1.0.1) libghc-cautious-file-doc libghc-cautious-file-prof libghc-data-accessor-template-dev ( 0.2.2) libghc-data-accessor-template-dev (= 0.2.1.3) libghc-data-accessor-template-doc libghc-data-accessor-template-prof libghc-rosezipper-dev ( 0.3) libghc-rosezipper-dev (= 0.1) libghc-rosezipper-doc libghc-rosezipper-prof libghc-vte-dev libghc-vte-doc libghc-vte-prof Just to spot check, I checked yi and some, if not all, of that seems to be valid. Please remove the moreinfo bug once this is investigated/resolved. Are you sure? $ apt-cache showsrc yi|grep-dctrl -s Version . Version: 0.7.1-2 Version: 0.7.1-5 Version: 0.12.0-1 $ apt-cache showsrc yi|grep-dctrl -F Build-Depends -r 'rosezipper\|cautios-file\|data-accessor-template\|vte' -s Version Version: 0.7.1-2 Version: 0.7.1-5 Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#762950: Now hide,f
Wharton Sent from my iPad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793668: angband-audio: maintainer scripts mishandle angband-data's /usr/share/angband/xtra/sound/sound.cfg
Package: angband-audio Version: 1:3.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts TL;DR: Use dpkg-divert. No Replaces. No manual moving. Be idempotent. Hi, during a test with piuparts I noticed your package does something wrong since angband-data loses ownership of /usr/share/angband/xtra/sound/sound.cfg Looking at the maintainer scripts, what you want to accomplish is the perfect task for dpkg-divert. Adding Replaces is wrong. Also the maintainer script actions are not idempotent, but they are performed (nearly) each time the script is called, so after apt-get install angband-audio apt-get install --reinstall angband-audio the sound.cfg.orig is gone. Once this is fixed in angband-audio, angband-data needs to add versioned Breaks against the buggy angband-audio version. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789975: FTBFS: CMake Error at doc/doxygen .. INSTALL cannot find .. doc/doxygen/deal.tag
On 26.07.2015 10:03, Philipp Huebner wrote: It looks like a tiny patch to doc/doxygen/CMakeLists.txt could fix this. And it does indeed. Regards, -- .''`. Philipp Huebner debala...@debian.org : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- Index: deal.ii-8.1.0/doc/doxygen/CMakeLists.txt === --- deal.ii-8.1.0.orig/doc/doxygen/CMakeLists.txt +++ deal.ii-8.1.0/doc/doxygen/CMakeLists.txt @@ -144,7 +144,7 @@ ADD_CUSTOM_TARGET(doxygen ALL ADD_DEPENDENCIES(documentation doxygen) INSTALL(FILES - ${CMAKE_CURRENT_BINARY_DIR}/deal.tag + ${CMAKE_CURRENT_BINARY_DIR}/deal.II/deal.tag DESTINATION ${DEAL_II_DOCHTML_RELDIR}/doxygen COMPONENT documentation ) signature.asc Description: OpenPGP digital signature
Bug#793557: clamtk in testing
Control: severity -1 important Control: tags -1 = unreproducible moreinfo Hi Carlos, On 25.07.2015 04:10, Carlos Kosloff wrote: * Specs Using KDE desktop, on a Toshiba laptop with amd64 architecture. Much more useful would be the information collected by reportbug: $ reportbug --template clamtk * What caused the problem After a dist-upgrade on 2015/07/24 clamtk does not launch. What packages were upgraded? Can you post the relevant parts of /var/log/dpkg.log from that upgrade? * Steps taken to resolve the problem Reinstalled. Rebooted computer. Attempted to launch from CLI. As user: command clamtk reports illegal instruction. This works fine here, thus I'm downgrading the severity. clamtk is just a perl program, so any illegal instruction error is probably caused by perl. What instructions does your CPU support? Please provide the output of: $ cat /proc/cpuinfo A backtrace of the crash would most certainly be helpful as well. Please provide the output of the following command (after installing gdb): $ gdb --batch -ex r -ex 'bt full' -ex q --args perl /usr/bin/clamtk As root: No protocol specified Gtk-WARNING **: cannot open display: :0 at /usr/lib/x86_64-linux-gnu/perl5/5.20/Gtk2.pm line 126. I don't think running clamtk as root is a good idea. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793651: Quick review
Hi, I can't yet sponsor your package, but I can give you a quick review. I honestly do not like custom makefiles, because even if you handle the build flags, you do not handle e.g. the install DESTDIR variable and prefix one correctly. This is why you overridden the dh_auto_install variable. I suggest you to create an easy CMakeLists.txt file and use it, allowing to easily use the dh calls without any override. $ cat CMakeLists.txt add_executable(hdump hdump.c) install(TARGETS hdump DESTINATION bin) this way you can just add cmake to build dependencies, remove the install file and the override in your rules file. this will avoid also having an hdump binary file in your source directory (I don't know, I built it and it didn't disappear from the source directory, giving a lintian warning) cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778192: zeitgeist: ftbfs with GCC-5
Control: tags -1 + patch Robert Ancell fixed this in Ubuntu using 0.9.16 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793374: [PATCH] Copy *.link files from /etc/systemd/network to initramfs
Am Sat, 25 Jul 2015 12:24:02 +0200 schrieb martin f krafft madd...@debian.org: You could also just use find /etc/systemd/network --name \*.link --exec cp -pt $DESTDIR/lib/systemd/network/ {} + But that would assume, that findutils is installed. I do not known if this is always the case. Cheers, Julian pgpt5n2N_IQez.pgp Description: Digitale Signatur von OpenPGP
Bug#793651: RFS: hdump/2.3-1 [ITP] -- Hexadecimal and ASCII dumper for binary files
I don't intend to upload this package, but here's my review: * Paulo kretc...@gmail.com, 2015-07-25, 21:16: http://mentors.debian.net/debian/pool/main/h/hdump/hdump_2.3-1.dsc The package description reads: Description: Hexadecimal and ASCII dumper for binary files The synopsis is not a sentence, so no need to start it with a capital letter. (Developer's Reference §6.2.2) Fast and simple hexadecimal/ASCII dumper for binary files, OTOH, the long description should consist of full sentences. (Developer's Reference §6.2.3) written in ANSI C. That's not something end users care, so I don't think it should belong in the package description. - Multi-platform (tested on GNU/Linux and Windows). Again, not relevant for end users. - Specify the initial byte (-b). Supports hex notation. Huh, what? There's no such option. (Not that I know what it would be useful for...) - Define numbers of bytes (-n). Multiple of the number of columns. I don't understand what the second sentence is supposed to mean. The patch header reads: Description: fix some issues in upstream Makefile to hardening. That's not very informative. I would have no idea what this patch does without reading the actual diff. Also, please forward the patch upstream. The Makefile passes both -W and -Wextra to gcc, even though -W is just an obsolete alias for -W. I think fsprintf might be a typo. debian/manpage/genallman.sh ignores all errors. (Although you don't use it debian/rules, so meh...) The manpage, like the package description, says something about ANSI C, the mysterious -b option, and multiple of the number of columns. man-pages(7) strongly discourages AUTHORS sections, and so do I. I find the for the Debian project (but may be used by others) part particularly silly. Upstream changelog reads: - Fixed compilation failure due misuse of fsprintf() function. Lintian says: X: hdump: binary-file-built-without-LFS-support usr/bin/hdump And indeed, the program doesn't support files bigger an 2GB on 32-bit architectures: $ truncate -s 3G foo $ hdump foo file not found or not readable The program ignores read and write errors: $ hdump README.md /dev/full $ echo $? 0 $ hdump /proc/self/mem $ echo $? 0 If you provide an option, but not the path, it treats the last argument as path: $ hdump -c 0 file not found or not readable You can't dump non-seekable files: $ echo foo | hdump /dev/stdin unable to seek through file [ This review was written for the debian-mentors mailing list (but may be read by others). ;-) ] -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793678: CUPS management through LDAP group printer-admins
Package: debian-edu-config Severity: wishlist For Debian Edu stretch, we should add a group printer-admins to GOsa². This group should then by granted SystemGroup privileges in /etc/cups/cups-files.conf. We do that for our customers already and it allows us to delegate printer management to a larger group of IT affine people. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpClFnJxvj6s.pgp Description: Digitale PGP-Signatur
Bug#793677: make Nagios accessible for LDAP admins
Package: debian-edu-config Severity: wishlist For Debian Edu stretch, we should add a group admins to LDAP/GOsa² that allows us putting users with administrative privileges on the Edu site in there. This group should then be granted access to Nagios pages via authnz_ldap. With local customers we deploy such a setup already and it works really nice. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpOk6bD6cNb2.pgp Description: Digitale PGP-Signatur
Bug#792759: setup instructions unclear, refusing to run with writable root?
Hello Eduard, thank you for spending your time helping to make Debian better with this bug report. Feel free to write a patch with your annotations for the FAQ. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#793671: dgit clone python-numpy experimental fails
Control: tags 793671 + patch pending Ian Jackson writes (Re: Bug#793671: dgit clone python-numpy experimental fails): dgit needs to get rid of things like this. (Currently it bails if it finds .git in the package toplevel, but I think it would be better if it removed this, and .git anywhere else too. Perhaps with a warning.) A fix for this is here, or in the patch below. http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=shortlog;h=refs/heads/fix.793671 (NB that is the result of a rebase onto 1.0, so the future history will not descend from that.) Ian. diff --git a/Debian/Dgit.pm b/Debian/Dgit.pm index edb338c..ba3e688 100644 --- a/Debian/Dgit.pm +++ b/Debian/Dgit.pm @@ -25,7 +25,7 @@ BEGIN { initdebug enabledebug enabledebuglevel printdebug debugcmd $debugprefix *debuglevel *DEBUG - shellquote printcmd); + shellquote printcmd messagequote); # implicitly uses $main::us %EXPORT_TAGS = ( policyflags = [qw(NOFFCHECK FRESHREPO)] ); @EXPORT_OK = @{ $EXPORT_TAGS{policyflags} }; @@ -73,6 +73,16 @@ sub printdebug { print DEBUG $debugprefix, @_ or die $! if $debuglevel0; } +sub messagequote ($) { +local ($_) = @_; +s{\\}{}g; +s{\n}{\\n}g; +s{\x08}{\\b}g; +s{\t}{\\t}g; +s{[\000-\037\177]}{ sprintf \\x%02x, ord $ }ge; +$_; +} + sub shellquote { my @out; local $_; diff --git a/debian/changelog b/debian/changelog index e9b934b..e77e8f9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +dgit (1.1~~) UNRELEASED; urgency=low + + * When source package contains things called .git (even files, and even +in subdirectories), remove them. Closes:#793671. + + -- + dgit (1.0) unstable; urgency=medium Improvements: diff --git a/dgit b/dgit index 9e2e66e..109f79c 100755 --- a/dgit +++ b/dgit @@ -1146,7 +1146,21 @@ sub mktree_in_ud_from_only_subdir () { $dirs[0] =~ m#^([^/]+)/\.$# or die; my $dir = $1; changedir $dir; -fail source package contains .git directory if stat_exists '.git'; + +my @gitscmd = qw(find -name .git -prune -print0); +debugcmd |,@gitscmd; +open GITS, -|, @gitscmd or failedcmd @gitscmd; +{ + local $/=\0; + while (GITS) { + chomp or die; + print STDERR $us: warning: removing from source package: , + (messagequote $_), \n; + rmtree $_; + } +} +$!=0; $?=0; close GITS or failedcmd @gitscmd; + mktree_in_ud_here(); my $format=get_source_format(); if (madformat($format)) { -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793684: rsnapshot incorrectly merges per-backup rsync_short_args
Package: rsnapshot Version: 1.3.1-4 Severity: normal Hi. rsnapshot from Jessie incorrectly merges per-backup '+rsync_short_args=' rsync short options. Version from Wheezy works fine. How to reproduce: 1. Build 1.3.1-4.. $ git clone git://anonscm.debian.org/collab-maint/rsnapshot.git $ git checkout debian/1.3.1-4 $ quilt push -a Applying patch debian/patches/01_rsnapshot_conf.diff patching file rsnapshot.conf.default.in patching file rsnapshot-program.pl patching file rsnapshot-program.pl Applying patch debian/patches/03_pod_missing_back.diff patching file rsnapshot-program.pl Applying patch debian/patches/05_backup_pgsql.diff patching file utils/backup_pgsql.sh Applying patch debian/patches/06_fix_random_file_verify.diff patching file utils/random_file_verify.sh Applying patch debian/patches/08_manpage_hourly_to_daily.diff patching file rsnapshot-program.pl Applying patch debian/patches/09_strip_backtick.diff patching file rsnapshot-program.pl Applying patch debian/patches/10_space_destdir.diff patching file rsnapshot-program.pl Applying patch debian/patches/11_lvm_snapshots.diff patching file rsnapshot.conf.default.in Hunk #2 succeeded at 202 (offset 6 lines). Hunk #3 succeeded at 235 (offset 6 lines). patching file configure.ac Applying patch debian/patches/12_include_conf_with_arguments.diff patching file rsnapshot-program.pl Applying patch debian/patches/13_print_warn.diff patching file rsnapshot-program.pl Now at patch debian/patches/13_print_warn.diff $ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking for perl... /usr/bin/perl checking for rsync... /usr/bin/rsync checking for cp... /bin/cp checking for rm... /bin/rm checking for ssh... /usr/bin/ssh checking for logger... /usr/bin/logger checking for du... /usr/bin/du configure: creating ./config.status config.status: creating Makefile config.status: creating rsnapshot config.status: creating rsnapshot-diff config.status: creating rsnapshot.conf.default config.status: creating t/support/etc/configtest.conf config.status: creating t/support/etc/rsync.conf config.status: creating t/support/etc/gnu_cp.conf config.status: creating t/support/etc/relative_delete_bugfix.conf config.status: creating t/configtest.t config.status: creating t/rsync.t config.status: creating t/gnu_cp.t config.status: creating t/relative_delete_bugfix.t Now type make testto run the regression test suite. Then type make install to install the program. After rsnapshot is installed, don't forget to copy /usr/local/etc/rsnapshot.conf.default to /usr/local/etc/rsnapshot.conf $ make cd . /bin/bash /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing --run aclocal-1.9 /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing: line 52: aclocal-1.9: command not found WARNING: `aclocal-1.9' is missing on your system. You should only need it if you modified `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd . /bin/bash /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing --run automake-1.9 --gnu /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing: line 52: automake-1.9: command not found WARNING: `automake-1.9' is missing on your system. You should only need it if you modified `Makefile.am', `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd . /bin/bash /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing --run autoconf /bin/bash ./config.status --recheck running /bin/bash ./configure --no-create --no-recursion checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for perl... /usr/bin/perl checking for rsync... /usr/bin/rsync checking for cp... /bin/cp checking for rm... /bin/rm checking for ssh... /usr/bin/ssh checking for lvcreate... no checking for lvremove... no checking for mount... /bin/mount checking for umount... /bin/umount checking for logger... /usr/bin/logger checking for du... /usr/bin/du configure: creating ./config.status Now type make testto run the regression test suite. Then
Bug#793623: u-boot-sunxi: Reading kernel from sdcard fails with certain cards on Banana Pi
Hi, I ordered a SanDisk Ultra 32GB SDHC microSD card w/ adapter today, will report back if it works once it arrives. Thanks, Markus On 26.07.2015, at 11:58, Karsten Merker mer...@debian.org wrote: On Sat, Jul 25, 2015 at 05:33:14PM +, Markus Kasten wrote: Package: u-boot-sunxi Version: 2014.10-2015.04 (stable/testing/unstable) Severity: important Tags: d-i upstream Dear Maintainer, I was trying to use the debian installer SD-card netboot image to install a fresh copy of debian on my Banana Pi (the ones from http://ftp2.de.debian.org/debian/dists/stability/main/installer-armhf/current/images/netboot/SD-card-images/). The image boots the u-boot bootloader properly, but fails to load vmlinuz off my sdcard. Loading and booting the installer via tftp works without problems. The same thing happens after installing debian: u-boot boots up properly, but fails to load the kernel (ext2 instead of fat this time). Listing files on the sdcard with fatls/ext2ls gives me the correct list of files without error. Here is the output of u-boot with the netboot image: U-Boot 2014.10+dfsg1-5 (Apr 07 2015 - 22:00:53) Allwinner Technology [...] Found U-Boot script /boot.scr reading /boot.scr 1451 bytes read in 44 ms (31.3 KiB/s) ## Executing script at 4310 Mainline u-boot / new-style environment detected. reading vmlinuz Error reading cluster ** Unable to read file vmlinuz ** SCRIPT FAILED: continuing... ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** Output after installing debian, booting the installation: [...] Found U-Boot script /boot.scr 2120 bytes read in 78 ms (26.4 KiB/s) ## Executing script at 4310 Mainline u-boot / new-style environment detected. ** ext4fs_devread read error - block SCRIPT FAILED: continuing... I tried this with a couple of different cards: * SanDisk Ultra II 2GB: does not work * SanDisk Ultra II 2GB (another one): does not work * SanDisk Ultra II 1GB: does not work I also pulled the images off the card again to check the md5sum, it's correct. This applies to stable, testing and unstable (from 25.07.2015) images. Interestingly, it works with an SanDisk Extreme 16GB SDHC card, so this might be a timing issue (as suggested in IRC). I currently don't have any other cards laying around to test this with, so I can't provide info on other cards and manufacturers. Hello, I cannot reproduce the problem here, but looking at which cards work and which cards do not work for you makes me wonder whether this might be an issue of SD vs. SDHC. All cards that do not work for you are classic SD cards while the one that works for you is an SDHC one. I have only SDHC cards (which work for me without problems) and no classic SD cards, so I unfortunately cannot test the latter. Do you perhaps have the chance to try another SDHC card? HTH, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung.
Bug#793574: systemsettings lost options, what's there working incorrectly
I had the same problem. I am fairly certain the upgrade to systemsettings caused it. The problem can be temporarily resolved by downgrading to systemsettings/stable. I am holding the old version for now. On Sat, 25 Jul 2015 10:12:16 +0100 Tony Green dddeb...@web-brewer.co.uk wrote: Package: systemsettings Version: 4:5.3.2-2 Severity: important Dear Maintainer, * What led up to the situation? Installed systemsettings 4:5.3.2-2 as part of routine installing of available updates. It appears that systemsettings for KDE5 has been installed in place of the correct version as /usr/bin/systemsettings has been replaced by /usr/bin/systemsettings5. * What exactly did you do (or not do) that was effective (or ineffective)? Launched systemsettings from icon. * What was the outcome of this action? Only four options showing on systemsettings - Application Style, Applications, Network settings, Display Monitor. In addition, these options open incorrect configuration settings: Application style - opens Widget style of GNOME/GTK applications. Applications - opens Configure file associations Network settings - opens SSL Versions Certificates Display Monitor - crashes systemsettings. The following error messages are generated: --- Couldn't start kded5 from org.kde.kded5.service: QDBusError(org.freedesktop.DBus.Error.ServiceUnknown, The name org.kde.kded5 was not provided by any .service files) , falling back to running kbuildsycoca5 kf5.kservice.sycoca: Trying to open ksycoca from /home/tony/.cache/ksycoca5 LOAD kscreen: launcherDataAvailable: org.kde.KScreen.Backend.XRandR kscreen: Launcher finished with exit code 1 , status 0 kscreen: Service for requested backend already running file:///usr/share/kcm_kscreen/qml/main.qml:20:1: module QtQuick.Controls is not installed import QtQuick.Controls 1.1 as Controls ^ file:///usr/share/kcm_kscreen/qml/main.qml:21:1: module org.kde.plasma.core is not installed import org.kde.plasma.core 2.0 as PlasmaCore ^ file:///usr/share/kcm_kscreen/qml/main.qml:22:1: module org.kde.kquickcontrols is not installed import org.kde.kquickcontrols 2.0 ^ file:///usr/share/kcm_kscreen/qml/main.qml:19:1: module QtQuick is not installed import QtQuick 2.1 ^ file:///usr/share/kcm_kscreen/qml/main.qml:20:1: module QtQuick.Controls is not installed import QtQuick.Controls 1.1 as Controls ^ file:///usr/share/kcm_kscreen/qml/main.qml:21:1: module org.kde.plasma.core is not installed import org.kde.plasma.core 2.0 as PlasmaCore ^ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775456: ITP: sankore -- interactive whiteboard interface
Hi David, Georges, Andrea, Miriam, On Fr 20 Feb 2015 19:43:19 CET, David Prévot wrote: Hi, [ The last two messages didn’t make it to the bug log. My mistake, sorry, copying them after reordering. ] Le 13/02/2015 13:39, Miriam Ruiz a écrit : 2015-02-13 17:58 GMT+01:00 David Prévot taf...@debian.org: On Fri, Feb 13, 2015 at 05:29:22PM +0100, Miriam Ruiz wrote: 2015-02-13 16:48 GMT+01:00 David Prévot taf...@debian.org: The first challenging bit might be to get rid of the sankore-ThirdParty code copy from the build system, I’ll start working on that now. The sankore-ThirdParty stuff hasn't changed since 2012 Noticed that. That’s one of the reason I’d like to get rid of it. Have you already mixed them or do you prefer for me to prepare a working package from those sources and the current git repo? I’d highly prefer to be able to use the dependencies already in the archive (quazip trolltech xpdf), and eventually package them if needed, rather than depending on old (and potentially security-flawed) convenient code copies. If really needed, we may use the multiple tarball feature of format 3.0 (quilt) to add back the missing bits. Yeah forget about the 3rd party, I agree with you. I meant mixing in the changes in the main program. Sure, feel free to start on getting rid of the ThirdParty tricks in order to make the package buildable again (I’m looking at it too, but have still no clear view/understanding of the program yet, so you’ll probably be a lot more efficient). I’ll push my work in progress in a separate branch in case I can make any progress, do not hesitate to do the same (I mean, even if it’s not working yet, something is better than nothing ;). I just updated my sankore.git packaging repo working copy to check progress on sankore packaging. Can someone update me / this ITP with the current packaging status? I will be working for schools over the summer and may be available for do more work on sankore. Thanks for status updates! Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpqM7lQ3LmgN.pgp Description: Digitale PGP-Signatur
Bug#793356: apt-cacher-ng: Maintenance URLs not correct, leading to 404
Hallo, * Mark De Souza [Thu, Jul 23 2015, 05:30:02PM]: Package: apt-cacher-ng Version: 0.8.0-3~bpo70+1 Severity: important Dear Maintainer, It appears that there is a problem with the way apt-cacher-ng conducts its maintence of volitile files. I think this shouldn't be a problem if you use a more recent version. Like: https://packages.debian.org/wheezy-backports-sloppy/apt-cacher-ng Please try and provide some feedback. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778112: [buildd-tools-devel] Bug#778112: Bug#778112: Bug#778112: schroot: ftbfs with GCC-5
On 26/07/2015 08:50, Matthias Klose wrote: On 07/26/2015 12:09 AM, Roger Leigh wrote: On 25/07/2015 22:07, Roger Leigh wrote: On 25/07/2015 21:45, Roger Leigh wrote: OK, some further investigation has shown what the exact error is. It looks like a GCC bug. Please see the attached source file testcase. This regex is failing: std::regex(^[a-z0-9][a-z0-9-]*$, std::regex::extended); however this one works: std::regex(^[a-z0-9][-a-z0-9]*$, std::regex::extended); In the same vein, the attached sample using basic rather than extended expressions fails in the opposite way. In this case both compile but the latter expression fails to match correctly. Since the expression should be valid and behave the same in both cases, it looks like there are two bugs here, the first being unable to compile a valid extended regex, the second here being unable to match (which is likely also a compile failure, but not a fatal one). Note this latter issue is seen with GCC 4.9 but appears to work with GCC 5. now forwarded as https://gcc.gnu.org/PR67015 however I can't see different behaviour with 4.9 and 5 (making sure to use the corresponding library using -static-libstdc++). Also I see regex2.cc always succeeding. Note I used GCC 4.9.2 in jessie. This fails every time with or without -static-libstdc++. GCC 4.9.3 in sid does not exhibit this behaviour, so it was likely just fixed with the 4.9.3 release. Regards, Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793548: [pkg-wine-party] Bug#793548: wine: Unimplemented function OpenAL32.dll.alGenFilters
Le 26/07/2015 06:09, Michael Gilbert a écrit : control: tag -1 upstream control: severity -1 minor control: reassign -1 src:wine-development On Fri, Jul 24, 2015 at 7:11 PM, Pierre Rudloff wrote: I am trying to run the Titan Souls Demo from Steam with Wine, but it crashes with this error: Have you tried the wine-development package? If also doesn't work there, please submit a winehq bug since this isn't a packaging problem. Best wishes, Mike Oh, I didn't know about the wine-development package. It does not work either so I will report it upstream. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778063: pinot: ftbfs with GCC-5
Control: tags -1 + confirmed building with rebuilt dependencies you get the following failure. looks like glibmm insists on c++11. test -x debian/rules mkdir -p . if test -e /usr/share/misc/config.guess ; then \ for i in ./config.guess ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.guess $i ; \ fi ; \ done ; \ fi if test -e /usr/share/misc/config.sub ; then \ for i in ./config.sub ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.sub $i ; \ fi ; \ done ; \ fi /usr/bin/make -C . make[1]: Entering directory '/scratch/packages/tmp/pinot-1.05' /usr/bin/make all-recursive make[2]: Entering directory '/scratch/packages/tmp/pinot-1.05' Making all in po make[3]: Entering directory '/scratch/packages/tmp/pinot-1.05/po' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/scratch/packages/tmp/pinot-1.05/po' Making all in Utils make[3]: Entering directory '/scratch/packages/tmp/pinot-1.05/Utils' /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -DUSE_CURL -DUSE_SSL -DUSE_GIO -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -DXDG_PREFIX=pinot_xdg -DUNAC_VERSION=\1.0.7\ -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG -c -o CommandLine.lo CommandLine.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -DUSE_CURL -DUSE_SSL -DUSE_GIO -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -DXDG_PREFIX=pinot_xdg -DUNAC_VERSION=\1.0.7\ -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG -c CommandLine.cpp -fPIC -DPIC -o .libs/CommandLine.o In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23:0, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:23, from /usr/include/glibmm-2.4/glibmm/shell.h:25, from CommandLine.cpp:37: /usr/include/glibmm-2.4/glibmm/refptr.h:238:3: warning: identifier 'nullptr' is a keyword in C++11 [-Wc++0x-compat] src.pCppObject_ = nullptr; ^ In file included from /usr/include/glibmm-2.4/glibmm/error.h:23:0, from /usr/include/glibmm-2.4/glibmm/variant.h:30, from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:25, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:23, from /usr/include/glibmm-2.4/glibmm/shell.h:25, from CommandLine.cpp:37: /usr/include/glibmm-2.4/glibmm/exception.h:34:3: warning: identifier 'noexcept' is a keyword in C++11 [-Wc++0x-compat] virtual ~Exception() noexcept = 0; ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23:0, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:23, from /usr/include/glibmm-2.4/glibmm/shell.h:25, from CommandLine.cpp:37: /usr/include/glibmm-2.4/glibmm/refptr.h:73:23: error: expected ',' or '...' before '' token inline RefPtr(RefPtr src); ^ /usr/include/glibmm-2.4/glibmm/refptr.h:73:29: error: invalid constructor; you probably meant 'Glib::RefPtrT_CppObject (const Glib::RefPtrT_CppObject)' inline RefPtr(RefPtr src); ^ /usr/include/glibmm-2.4/glibmm/refptr.h:93:34: error: expected ',' or '...' before '' token inline RefPtr operator=(RefPtr src); ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23:0, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:23, from /usr/include/glibmm-2.4/glibmm/shell.h:25, from CommandLine.cpp:37: /usr/include/glibmm-2.4/glibmm/refptr.h:234:35: error: expected ',' or '...' before '' token RefPtrT_CppObject::RefPtr(RefPtr src) ^ /usr/include/glibmm-2.4/glibmm/refptr.h:234:1: error: prototype for 'Glib::RefPtrT_CppObject::RefPtr(Glib::RefPtrT_CppObject)' does not match any in class 'Glib::RefPtrT_CppObject' RefPtrT_CppObject::RefPtr(RefPtr src) ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23:0,
Bug#778162: vera++: ftbfs with GCC-5
builds with the rebuilt boost1.58 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793374: [PATCH] Copy *.link files from /etc/systemd/network to initramfs
also sprach Julian Wollrath jwollr...@web.de [2015-07-26 14:06 +0200]: But that would assume, that findutils is installed. I do not known if this is always the case. It's essential, meaning we can rely on it. -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems oh what a tangled web we weave, when first we practice to deceive. but my how we improve the score, as we practice more and more. -- sir walter scott digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#793674: hhvm: leaves alternatives after purge: php - /usr/bin/hhvm
Package: hhvm Version: 3.2.0+dfsg1-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see https://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. unpacked but not configured packages or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove name path'. Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 1m15.6s ERROR: WARN: Broken symlinks: /usr/share/man/man1/php.1.gz - /etc/alternatives/php.1.gz /usr/bin/php - /etc/alternatives/php /etc/alternatives/php.1.gz - /usr/share/man/man1/hhvm.1.gz /etc/alternatives/php - /usr/bin/hhvm 1m17.7s ERROR: FAIL: Package purging left files on system: /etc/alternatives/php - /usr/bin/hhvm not owned /etc/alternatives/php.1.gz - /usr/share/man/man1/hhvm.1.gznot owned /usr/bin/php - /etc/alternatives/php not owned /usr/share/man/man1/php.1.gz - /etc/alternatives/php.1.gz not owned cheers, Andreas hhvm_3.2.0+dfsg1-2.log.gz Description: application/gzip
Bug#793675: hplip-gui: No system tray detected
Package:hplip-gui Version:3.14.6 Severity:normal Dear Maintainer, When I launch plasma desktop, after few seconds a pop-up appears with an error about hplip. see capture. $ dpkg --status hplip-gui Package: hplip-gui Status: install ok installed Priority: optional Section: utils Installed-Size: 163 Maintainer: Debian HPIJS and HPLIP maintainers pkg-hpijs-de...@lists.alioth.debian.org Architecture: all Source: hplip Version: 3.14.6-1 Replaces: hplip ( 3.12.4-2) Depends: hplip (= 3.14.6-1), dbus-x11, python-qt4, python-qt4-dbus, gksu | kdebase-bin ( 4:4.4.0-1) | kde-runtime | kdebase-runtime | kdesudo | ktsuss Recommends: xsane | simple-scan | skanlite, python-notify Breaks: hplip ( 3.12.4-2) Conffiles: /etc/xdg/autostart/hplip-systray.desktop 0d646597b465477263ec14d1ccbab7bf Description: HP Linux Printing and Imaging - GUI utilities (Qt-based) The HP Linux Printing and Imaging System provides full support for printing on most HP SFP (single function peripheral) inkjets and many LaserJets, and for scanning, sending faxes and for photo-card access on most HP MFP (multi-function peripheral) printers. . This package contains utilities with graphical user interface (GUI) for HPLIP: HP Toolbox, HP Fax, ... . Note that all GUI utilities are based on the Qt GUI environment. There are currently no equivalent utilities based on GTK+. Homepage: http://hplipopensource.com/hplip-web/index.html -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hplip-gui depends on: ii dbus-x11 1.8.20-1 ii gksu 2.0.2-9 ii hplip3.14.6-1+b2 ii kde-runtime 4:4.14.2-2 ii python-qt4 4.11.4+dfsg-1 ii python-qt4-dbus 4.11.4+dfsg-1 Versions of packages hplip-gui recommends: ii python-notify 0.1.1-4 ii xsane 0.999-2 hplip-gui suggests no packages.
Bug#792945: authbind : please make the build reproducible
Johannes Schauer writes (Bug#792945: authbind : please make the build reproducible): since you expressed that an NMU would be welcome I just uploaded one to DELAYED/5. Notice, that this is not using akira's original patch which makes use of $BUILD_DATE but instead $SOURCE_DATE_EPOCH which was later agreed to become the cross-distribution environment variable for this kind of purpose. You can find the debdiff attached. Thank you. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793374: [PATCH v3] Copy .link interface naming definitions to initramfs
I addressed your remarks and now I find based approach is used. I also got rid of the explicit copying of 01-mac-usb.link and 99-default.link, since this is now also done by find. Cheers, Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793374: [PATCH] Copy .link interface naming definitions to initramfs
Currently, only the default .link files from /lib/systemd/network are copied to the initramfs, meaning, that additional (local) .link naming definitions will be ignored when the system is still controlled by the initramfs and interfaces might get wrong names. Fix this by copying all .link files from /lib/systemd/network and /etc/systemd/network into the initramfs, with the files from /etc/systemd/network taking precedence over files with the same name from /lib/systemd/network, as stated in the systemd.link manpage. Signed-off-by: Julian Wollrath jwollr...@web.de --- debian/changelog| 3 +++ debian/extra/initramfs-tools/hooks/udev | 9 ++--- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/debian/changelog b/debian/changelog index 7cb36aef4f44..c756afb225c3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -10,6 +10,9 @@ systemd (222-3) UNRELEASED; urgency=medium * Enable GNU EFI support and add gnu-efi build dep. This enables/ships the systemd EFI boot loader. (Closes: #787720) + [ Julian Wollrath ] + * Copy all .link interface naming definitions to initramfs. (Closes: 793374) + -- Michael Biebl bi...@debian.org Tue, 21 Jul 2015 22:24:51 +0200 systemd (222-2) unstable; urgency=medium diff --git a/debian/extra/initramfs-tools/hooks/udev b/debian/extra/initramfs-tools/hooks/udev index cfe5085ae079..71e597bca128 100755 --- a/debian/extra/initramfs-tools/hooks/udev +++ b/debian/extra/initramfs-tools/hooks/udev @@ -32,14 +32,9 @@ cp -a /sbin/udevadm $DESTDIR/sbin/udevadm mkdir -p $DESTDIR/etc/udev cp -p /etc/udev/udev.conf $DESTDIR/etc/udev/ +# copy .link files containing interface naming definitions mkdir -p $DESTDIR/lib/systemd/network/ -for link in 01-mac-for-usb.link 99-default.link; do - if [ -e /etc/systemd/network/$link ]; then -cp -p /etc/systemd/network/$link $DESTDIR/lib/systemd/network/ - elif [ -e /lib/systemd/network/$link ]; then -cp -p /lib/systemd/network/$link $DESTDIR/lib/systemd/network/ - fi -done +find /lib/systemd/network /etc/systemd/network -name \*.link -execdir cp -pt $DESTDIR/lib/systemd/network/ '{}' + mkdir -p $DESTDIR/lib/udev/rules.d/ for rules in 50-firmware.rules 50-udev-default.rules 60-persistent-storage.rules \ -- 2.4.6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789778: fusionforge-db-local: unconditionally starts systasksd upon install
Followup-For: Bug #789778 Control: found -1 6.0.2-1 On Wed, 24 Jun 2015 13:14:06 +0200 Andreas Beckmann a...@debian.org wrote: during a test with piuparts I noticed your package left processes running after the package has been removed and/or purged. This has been worked around in 6.0.2-1 with * Stop fusionforge-systasksd on uninstall (closes: #789778) The real problem is in the postinst which unconditionally starts this service, i.e. without using incoke-rc.d. But this has not been addressed at all. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712938: sni-qt -- Indicator support for Qt
On Sunday 26 July 2015 17:56:19 Tsu Jan wrote: On Sun, 26 Jul 2015 12:47:03 + 1...@o2o2.tk wrote: I can't compile qt after applying above patch from ubuntu... Most probably, you don't need to recompile Qt4. Just get: libqtgui4_4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1_amd64.deb and/or libqtgui4_4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1_i386.deb from the Ubuntu Vivid repository, extract them, and overwrite 'usr/lib/x86_64- linux-gnu/libQtGui.so.4.8.6' and/or /usr/lib/i386-linux-gnu/libQtGui.so.4.8.6' AFTER BACKING THEM UP. That's the perfect way to break your system. There is no way to ensure the compilations are compatible. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#791795: plasma-sdk seems to be the only package without an epoch
Hi Bogdan! Thanks for spotting the inconsistency in our package versioning. I had a look around, and plasma-sdk seems to be the exception and not the norm, the following packages *do* have an epoch (4:) : - bluedevil - plasma-desktop - plasma-nm - plasma-workspace - powerdevil Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712938: Info received (sni-qt -- Indicator support for Qt)
On Sun, 26 Jul 2015 13:42:51 + 1...@o2o2.tk wrote: It's actually not possible, because Debian includes qt 4_4.8.7 (in sid). So I can't replace files with older version, most likely it won't work. How do you have 4.8.6 in Debian? The system on which I did so still has Qt-4.8.6. Sorry that I didn't check that! On my laptop, I have qt 4_4.8.7 but I haven't updated KDE. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712938: No change?
On Sun, 26 Jul 2015 10:52:13 -0300 Lisandro =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com wrote: On Sunday 26 July 2015 12:42:56 MichaÅ Milanowski wrote: Can't any debian dev see his stupidity regarding to this issue? There are tons of qt4 apps that are widely used and will be probably never ported to qt5, like Skype for example, but many others too. Hi! I'm the Qt maintainer, and yes, I understand your arguments, but again: do you really want to push dead-upstream code and support it trough the whole life of Stretch? I don't. Your argument is that of principles against usability. People USE Debian. The principles are important, of course, but as far as they don't interfere with usability. You speak about dead code as if Qt4 has totally disappeared. As you know, there are and will be so many Qt4 apps. Porting to Qt5 is a good advice but, here again, an advice against usability?! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793661: crashes the server
Package: nfs-kernel-server Version: 1:1.2.8-9 Severity: serious Ever since upgrading the server from wheezy to jessie, I've been having crashes every couple of weeks. Running wheezy, it had been stable and running continuously for over a year. NFS configuration was not changed when upgrading. Typically, the crash would occur when the screen was blank and I haven't previously been able to see any console output from the crashes. Yesterday, I had the crash twice within 10 minutes and I observed the messages: INFO: rcu_sched detected stalls on CPUs/tasks: {} (detected by 1, t=5252 jiffies, g=14894, c=14893, q=583) INFO: Stall ended before state dump start BUG: soft lockup - CPU#0 stuck for 23s! [nfsd:1781] BUG: soft lockup - CPU#1 stuck for 23s! [nfsd:1785] I found that this crash was repeatable, every time a particular NFS client ran git checkout master in a particular project. The project in question is quite big, it is on an NFS v3 mount and the filesystem on the NFS server is btrfs. The client is also running jessie. This crash happened about five times yesterday. I logged into the server using ssh and went to the same directory and ran git checkout master and there was no crash. Then I tried again on the client, checkout out a branch and then checking out master again and it seems to work now from the client without a crash. I had been in the same directory a few days ago, checking out different branches, without any crashes. I have edited /etc/kbd/config setting BLANK_TIME=0 so that I can see any messages on the screen when it crashes again. I've also added kdump-tools on this machine and will try to obtain further details. Please let me know if there is any specific data I should try to obtain next time it crashes. The kernel I am running: $ uname -a Linux srv1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux It was also crashing with previous jessie kernels. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791803: abook: diff for NMU version 0.6.0~pre2-4.1
Hi Rhonda, hi Denis, I've prepared an NMU for abook (versioned as 0.6.0~pre2-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -Nru abook-0.6.0~pre2/debian/changelog abook-0.6.0~pre2/debian/changelog --- abook-0.6.0~pre2/debian/changelog 2015-07-07 17:39:52.0 +0200 +++ abook-0.6.0~pre2/debian/changelog 2015-07-26 08:29:38.0 +0200 @@ -1,3 +1,15 @@ +abook (0.6.0~pre2-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Quote argument to -x test when testing for update-menus. +Postinst switched from testing existence and execution permissions for +hardcoded /usr/bin/update-menus to testing the path returned by `which +update-menus`. +Fixes abook: fails to install: abook.postinst: update-menus: not +found. (Closes: #791803) + + -- Salvatore Bonaccorso car...@debian.org Sun, 26 Jul 2015 08:19:44 +0200 + abook (0.6.0~pre2-4) unstable; urgency=medium [ Rhonda D'Vine ] diff -Nru abook-0.6.0~pre2/debian/postinst abook-0.6.0~pre2/debian/postinst --- abook-0.6.0~pre2/debian/postinst 2015-07-06 17:35:05.0 +0200 +++ abook-0.6.0~pre2/debian/postinst 2015-07-26 08:29:38.0 +0200 @@ -54,6 +54,6 @@ # menu entry -if [ $action = 'configure' ] [ -x `which update-menus` ]; then +if [ $action = 'configure' ] [ -x `which update-menus` ]; then update-menus fi
Bug#793665: claws-mail: New upstream version (3.12.0) / managesieve plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: claws-mail Version: 3.12.0-0.1 Severity: wishlist Dear Maintainer, the new upstream version of claws mail (3.12.0) introduces a plugin to manage sieve scripts. Since this is useful for me, I updated the packaging (in a quick and dirty way), so that I can use this new version and the plugin. Maybe my local changes to the packaging could be useful for the actual packaging of the new version, therefore I included the diff for my changes below. With best regards, Julian Wollrath - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.3 (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 Init: systemd (via /run/systemd/system) Versions of packages claws-mail depends on: ii libatk1.0-0 2.16.0-2 ii libc62.19-19 ii libcairo21.14.2-2 ii libcompfaceg11:1.5.2-5 ii libdb5.3 5.3.28-9 ii libdbus-1-3 1.8.20-1 ii libdbus-glib-1-2 0.102-1 ii libenchant1c2a 1.6.0-10.1 ii libetpan17 1.5-2 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgdk-pixbuf2.0-0 2.31.5-1 ii libglib2.0-0 2.44.1-1.1 ii libgnutls-deb0-283.3.16-1 ii libgtk2.0-0 2.24.28-1 ii libice6 2:1.0.9-1+b1 ii libldap-2.4-22.4.41+dfsg-1 ii liblockfile1 1.09-6 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libpisock9 0.12.5-dfsg-1 ii libsasl2-2 2.1.26.dfsg1-13 ii libsm6 2:1.2.2-1+b1 ii xdg-utils1.1.0~rc1+git20111210-7.4 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages claws-mail recommends: pn aspell-en | aspell-dictionary none ii claws-mail-i18n 3.12.0-0.1 pn xfonts-100dpi | xfonts-75dpi | xfonts-100dpi-transcoded | xfont none Versions of packages claws-mail suggests: pn claws-mail-doc none pn claws-mail-tools none ii iceweasel [www-browser] 40.0~b3-1 ii kwrite 4:4.14.2-2 ii w3m [www-browser]0.5.3-23 - -- no debconf information - --- diff --git a/changelog b/changelog index ad973e66a9fe..acd8493b6fc8 100644 - --- a/changelog +++ b/changelog @@ -1,3 +1,15 @@ +claws-mail (3.12.0-0.1) UNRELEASED; urgency=medium + + * Non maintainer-upload. + * New upstream version: +- Do not depend on plugin libraries anymore (Closes: #779824). +- New plugin to manage sieve filters. +- Drop patches applied upstream. + * Update debian/watch. + * Update VCS-URL's. + + -- Julian Wollrath jwollr...@web.de Sun, 26 Jul 2015 10:15:44 +0200 + claws-mail (3.11.1-3) unstable; urgency=medium * patches/15fix_crash_open_folder.patch, patches/series diff --git a/claws-mail-managesieve-plugin.install b/claws-mail-managesieve-plugin.install new file mode 100644 index ..2ff2f4914485 - --- /dev/null +++ b/claws-mail-managesieve-plugin.install @@ -0,0 +1 @@ +usr/lib/*/claws-mail/plugins/managesieve.so diff --git a/control b/control index c92e14395c8c..544c6a0678e9 100644 - --- a/control +++ b/control @@ -22,8 +22,8 @@ Build-Depends: debhelper (= 9), libcompfaceg1-dev, libsm-dev, libcurl4-gnutls-dev, libexpat-dev, libkrb5-dev Standards-Version: 3.9.6 Homepage: http://www.claws-mail.org - -Vcs-Git: git://anonscm.debian.org/users/mones/claws-mail.git - -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=users/mones/claws-mail.git +Vcs-Git: https://anonscm.debian.org/git/users/mones/claws-mail.git +Vcs-Browser: https://anonscm.debian.org/cgit/users/mones/claws-mail.git Package: claws-mail Architecture: any @@ -378,6 +378,13 @@ Description: mbox format mailboxes handler for Claws Mail . Once added, these files appear like mailer's native mail folders. +Package: claws-mail-managesieve-plugin +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends}, + claws-mail (= ${binary:Version}) +Description: sieve filter handler for Claws Mail + Manage sieve filters on a server using the ManageSieve protocol. + Package: claws-mail-multi-notifier Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends}, diff --git a/patches/12fix_manpage_header.patch b/patches/12fix_manpage_header.patch index c51bc95e34c5..5b3b5671346f 100644 - --- a/patches/12fix_manpage_header.patch +++ b/patches/12fix_manpage_header.patch @@ -11,4 +11,4 @@ diff -ur claws-mail-3.7.6.orig//doc/man/claws-mail.1 claws-mail-3.7.6//doc/man/c +claws\-mail \- a GTK+ based fast email and news client .SH SYNOPSIS - - .B claws-mail + .B claws\-mail diff --git a/patches/13desktop_file_categories.patch b/patches/13desktop_file_categories.patch deleted file mode 100644 index 35c381955b76.. - --- a/patches/13desktop_file_categories.patch +++ /dev/null @@ -1,15
Bug#793572: dolphin-emu: FTBFS in buildd environment: No suitable display platform found
Control: tags 793572 + patch upstream fixed-upstream Control: forwarded 793572 https://github.com/dolphin-emu/dolphin/pull/2203 This seems to have been caused by a cmake change (perhaps between the time Dolphin was uploaded and the time it left the NEW queue), rather than an unclean build environment: see https://github.com/dolphin-emu/dolphin/pull/2203. I've backported the relevant change, and it has built successfully in my local sbuild. I'm not going to NMU this right now, because it would be better if someone who already uses Dolphin could test the result; but I'm aware that it's blocking at least one transition, so I'll NMU if necessary. S diffstat for dolphin-emu-4.0.2+dfsg dolphin-emu-4.0.2+dfsg changelog | 10 ++ patches/10_find-x11.patch | 25 + patches/series|1 + 3 files changed, 36 insertions(+) diff -Nru dolphin-emu-4.0.2+dfsg/debian/changelog dolphin-emu-4.0.2+dfsg/debian/changelog --- dolphin-emu-4.0.2+dfsg/debian/changelog 2015-02-09 10:51:55.0 + +++ dolphin-emu-4.0.2+dfsg/debian/changelog 2015-07-26 12:19:45.0 +0100 @@ -1,3 +1,13 @@ +dolphin-emu (4.0.2+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * d/p/10_find-x11.patch: backport patch from upstream to invoke FindX11 +explicitly. It looks as though this used to be pulled in implicitly +by FindOpenGL but this is no longer the case, causing FTBFS. +(Closes: #793572) + + -- Simon McVittie s...@debian.org Sun, 26 Jul 2015 11:54:16 +0100 + dolphin-emu (4.0.2+dfsg-1) unstable; urgency=medium * Initial release (Closes: #535073) diff -Nru dolphin-emu-4.0.2+dfsg/debian/patches/10_find-x11.patch dolphin-emu-4.0.2+dfsg/debian/patches/10_find-x11.patch --- dolphin-emu-4.0.2+dfsg/debian/patches/10_find-x11.patch 1970-01-01 01:00:00.0 +0100 +++ dolphin-emu-4.0.2+dfsg/debian/patches/10_find-x11.patch 2015-07-26 12:21:41.0 +0100 @@ -0,0 +1,25 @@ +From: Maxime Gauduin aluc...@gmail.com +Date: Fri, 13 Mar 2015 12:58:08 +0100 +Subject: Include the FindX11 module + +Bug-Debian: https://bugs.debian.org/793572 +Origin: upstream, https://github.com/dolphin-emu/dolphin/commit/148ce85b26925e38ced2f196475086eb7884fb62 +[smcv: backported to 4.0.2] +--- + CMakeLists.txt | 3 +-- + 1 file changed, 1 insertion(+), 2 deletions(-) + +diff --git a/CMakeLists.txt b/CMakeLists.txt +index 5903eca..421e224 100644 +--- a/CMakeLists.txt b/CMakeLists.txt +@@ -413,8 +413,7 @@ if(NOT ANDROID) + add_definitions(-DHAVE_WAYLAND=0) + endif(USE_WAYLAND AND WAYLAND_FOUND) + +- # Note: We do not need to explicitly check for X11 as it is done in the cmake +- # FindOpenGL module on linux. ++ include(FindX11) + if(USE_X11 AND X11_FOUND) + set(USE_X11 1) + add_definitions(-DHAVE_X11=1) diff -Nru dolphin-emu-4.0.2+dfsg/debian/patches/series dolphin-emu-4.0.2+dfsg/debian/patches/series --- dolphin-emu-4.0.2+dfsg/debian/patches/series 2015-02-09 10:51:17.0 + +++ dolphin-emu-4.0.2+dfsg/debian/patches/series 2015-07-26 12:19:09.0 +0100 @@ -7,3 +7,4 @@ 07_cmake-sfml-fixes.patch 08_sfml-use-2.1.patch 09_arm-use-gl.patch +10_find-x11.patch
Bug#793670: mount: bad optical disk can place mount command into uninteruptable sleep
Package: mount Version: 2.26.2-6 Severity: normal Tags: upstream Dear Maintainer, I've found trying to mount an optical disk that turns out to be bad, (this is the case I've encountered, may possibly happen with other media) can cause the mount command to go into a noninteruptable sleep state, waiting for response from the hardware that never arrives. This latter can interfere in placing the computer in hibernate or performing a clean shutdown. My understanding is that the command could alternatively be implimented to use a killable state, similar to the uninteruptable sleep, except that the process can be killed. If there are reason's the noninteruptable sleep must be used most of the time, perhaps providing a switch to enforce killable when the media is of unproven quality would be possible. Thanks for any consideration. Regards, Dallas E. Legan II / le...@acm.org / aw...@lafn.org http://isthereanotherquestion.blogspot.com Tekeli-li! Tekeli-li! - At the Mountains of Madness, H.P. Lovecraft *** 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 *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages mount depends on: ii libblkid1 2.25.2-6 ii libc6 2.19-17 ii libmount1 2.25.2-6 ii libselinux12.3-2 ii libsmartcols1 2.25.2-6 mount recommends no packages. Versions of packages mount suggests: ii nfs-common 1:1.2.2-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793407: adequate: check perl/python module dependencies
* Jakub Wilk jw...@debian.org, 2015-07-24, 14:46: I started playing with checking Python imports here: https://github.com/jwilk/adequate-imports I've implemented Perl import checker, too. DebConf modules were troublesome, because they tried to spawn a frontend, but I implemented a work-around. Unfortunately, importing some Python modules have unwanted side effects. For example: import antigravity spawns a web browser. I blacklisted this one. import quodlibet.commands segfaults. Filed as #793673. Now I import each module in a separate process, so this is no longer a big deal. import imdb.locale.generatepot calls sys.exit(). I catch SystemExit to work around this. import pychecker2.VariableChecks fails; but import pychecker.checker; import pychecker2.VariableChecks starts checking your code. oO I don't run into the latter behavior now that I import each module separately. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762340: [Aptitude-devel] Bug#762340: Bug#762340: aptitude: [INTL:de] partially updated German man page translation
Control: tag -1 - moreinfo + pending Hi Helge and Mario, Axel Beckert wrote: Helge Kreutzmann wrote: Please find the partial updated German man page translation for aptitude at http://www.helgefjell.de/data/aptitude_0.6.10-1_de.po.bz2 This looks rather like a complete rewrite than something partial: My fault: I diffed it against the program translation instead of the man page translation. Of course that gives a huge diff. ;-) Sorry for the noise. Will apply it in the git repository soon. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792466: nginx-extras: auth_pam fails to require authentication
I owe you guys an apology. Turns out that Apple Safari, when a basic auth password is saved in the keychain, doesn't even prompt you to send your saved password; it just sends it automatically. So I didn't see an authentication prompt because safari was silently authenticating on my behalf. :/ Your advice to check auth.log was spot on, and I don't know how I missed it before. (It was pretty late, so I'll blame it on lack of sleep.) Seeing that successful authentication was happening behind-the-scenes led me to track down where the invisible authentication credentials were coming from. Thanks for your help. ~jonathon On Sat, Jul 25, 2015 at 8:40 PM, Jonathon Anderson jander...@civilfritz.net wrote: I've definitely already been checking /var/log/auth.log, and haven't been able to discern the problem; but I'll duplicate your testcase in my environment to see if it works correctly for me, and then do a binary-search from there. Thanks for your responsiveness, and sorry for my delay in getting back to you. ~jonathon On Thu, Jul 16, 2015 at 2:05 AM, Christos Trochalakis yati...@ideopolis.gr wrote: On Wed, Jul 15, 2015 at 02:45:48AM +, Jonathon Anderson wrote: Package: nginx-extras Version: 1.6.2-5 Severity: normal Dear Maintainer, * What led up to the situation? I recently upgraded to debian 8 and, after doing so, realized that auth_pam in nginx no longer prompted me for a password to edit my internal wiki. I noticed that auth_pam appears to have been moved to nginx-extras, so I installed that (replacing nginx-full) but the problem persists. * What exactly did you do (or not do) that was effective (or ineffective)? I've checked my config, and can't find anything wrong with it. I've added allow/deny rules for the time being, and those have successfully isolated access to my IP for now. I thought that perhaps the default for auth_pam_service_name had changed, so I set it explicitly, but to no avail. ldd reveals that nginx *is* linked against pam. nginx -V reveals --add-module=/tmp/buildd/nginx-1.6.2/debian/modules/nginx-auth-pam * What was the outcome of this action? Navigating to a path protected by this config: location /auth { auth_pam example.net; auth_pam_service_name nginx; include fastcgi_params; fastcgi_pass unix:/var/run/fcgiwrap.socket; fastcgi_index ikiwiki.cgi; fastcgi_param REMOTE_USER $remote_user; } Does not prompt for any username or password. * What outcome did you expect instead? I expect it to prompt for a username and password. -- System Information: Hello Jonathon, I am not able to reproduce your case, here is my setup: # grep /private -A 4 /etc/nginx/sites-enabled/reprepro location /private { auth_pam example; auth_pam_service_name nginx; proxy_pass http://IP/; } # cat /etc/pam.d/nginx authrequiredpam_permit.so account requiredpam_permit.so # curl -o /dev/null -v localhost/private/resource * Connected to localhost (127.0.0.1) port 80 (#0) GET /private/resource HTTP/1.1 User-Agent: curl/7.38.0 Host: localhost Accept: */* HTTP/1.1 401 Unauthorized * Server nginx/1.6.2 is not blacklisted Server: nginx/1.6.2 Date: Thu, 16 Jul 2015 07:49:22 GMT Content-Type: text/html Content-Length: 194 Connection: keep-alive WWW-Authenticate: Basic realm=example { [data not shown] * Connection #0 to host localhost left intact # curl -o /dev/null -v localhost/private/resource -u username:pass * Connected to localhost (127.0.0.1) port 80 (#0) * Server auth using Basic with user 'username' GET /private/resource HTTP/1.1 Authorization: Basic dXNlcm5hbWU6cGFzcw== User-Agent: curl/7.38.0 Host: localhost Accept: */* HTTP/1.1 404 Not Found * Server nginx/1.6.2 is not blacklisted Server: nginx/1.6.2 Date: Thu, 16 Jul 2015 07:49:29 GMT Content-Type: text/html Content-Length: 168 Connection: keep-alive { [data not shown] * Connection #0 to host localhost left intact # nginx -V nginx version: nginx/1.6.2 ... I am getting a 401 ana a 'WWW-Authenticate' header on the first request which is valid. Perhaps there is something else going on with your setup. You could also check /var/log/auth.log for relevant messages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793664: base: network interface eth0 is missing its IPv4 address after reboot
Package: base Severity: important Tags: ipv6 Dear Maintainer, after starting up the system the network interface eth0 is up but has got only its IPv6 address, while it is missing its IPv4 address. Therefore, I cannot reach the internet. Workaround: I have to open a terminal and do the following as root: ifconfig eth0 down ifconfig eth0 up Then I have to wait some seconds and the problem is gone as long as the system is not rebooted again. After applying the workaround you can with ifconfig -a that now the IPv4 address has appeared. Kind regards, Michael *** 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 *** -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (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 Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792945: authbind : please make the build reproducible
Hi, On Mon, 20 Jul 2015 12:00:25 +0100 Ian Jackson ijack...@chiark.greenend.org.uk wrote: FAOD I did not understand your covering note to say that you were actually doing an NMU. But, such an NMU would be welcome. If you don't do an NMU I will fold this patch in at some point, but maybe not particularly soon. I may rewrite the build system instead. since you expressed that an NMU would be welcome I just uploaded one to DELAYED/5. Notice, that this is not using akira's original patch which makes use of $BUILD_DATE but instead $SOURCE_DATE_EPOCH which was later agreed to become the cross-distribution environment variable for this kind of purpose. You can find the debdiff attached. Thanks! cheers, josch diff -Nru authbind-2.1.1/debian/changelog authbind-2.1.1+nmu1/debian/changelog --- authbind-2.1.1/debian/changelog 2012-06-11 00:17:19.0 +0200 +++ authbind-2.1.1+nmu1/debian/changelog 2015-07-26 11:23:38.0 +0200 @@ -1,3 +1,11 @@ +authbind (2.1.1+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix mtimes before building binary packages to produce reproducible output +Based on patch by akira (Closes: #792945) + + -- Johannes Schauer jo...@debian.org Sun, 26 Jul 2015 11:23:35 +0200 + authbind (2.1.1) unstable; urgency=low * Manpage has an example of which files will be checked and read diff -Nru authbind-2.1.1/debian/rules authbind-2.1.1+nmu1/debian/rules --- authbind-2.1.1/debian/rules 2012-06-03 02:45:04.0 +0200 +++ authbind-2.1.1+nmu1/debian/rules 2015-07-26 11:18:57.0 +0200 @@ -29,6 +29,8 @@ arch = $(shell dpkg --print-architecture) +export SOURCE_DATE_EPOCH = $(shell date -d $$(dpkg-parsechangelog --count 1 -SDate) +%s) + INSTALL = install INSTALL_FILE= $(INSTALL) -p-o root -g root -m 644 INSTALL_PROGRAM = $(INSTALL) -p-o root -g root -m 755 @@ -90,6 +92,8 @@ dpkg-gencontrol -isp chown -R root.root debian/tmp chmod -R g-ws debian/tmp + find debian/tmp -newermt @$$SOURCE_DATE_EPOCH -print0 | \ + xargs -0r touch --no-dereference --date=@$$SOURCE_DATE_EPOCH dpkg --build debian/tmp .. binary: binary-indep binary-arch signature.asc Description: signature
Bug#791803: abook: diff for NMU version 0.6.0~pre2-4.1
On Sun, Jul 26, 2015 at 10:00:21AM +0200, Salvatore Bonaccorso wrote: Hi Rhonda, hi Denis, I've prepared an NMU for abook (versioned as 0.6.0~pre2-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Salvatore Hello Salvatore, Thank you for your NMU, your help is welcome but a new version using debhelper is pending (check 'dh' git branch). It's not complete but, I would like to finish it in the next week (patchs to help us to finish it are welcome). IMHO, I prefere to wait few days this clean 'dh' new version than an NMU who fix only one thing with the old system. Best regards Denis Briand signature.asc Description: Digital signature
Bug#777955: liblas: ftbfs with GCC-5
Control: severity -1 normal Control: retitle -1 liblas: should update symbols files for GCC 5 this builds with boost1.58, but could use an update for the symbols files -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762340: [Aptitude-devel] Bug#762340: aptitude: [INTL:de] partially updated German man page translation
Control: tag -1 + moreinfo Hi Helge, Helge Kreutzmann wrote: Please find the partial updated German man page translation for aptitude at http://www.helgefjell.de/data/aptitude_0.6.10-1_de.po.bz2 This looks rather like a complete rewrite than something partial: → git diff --stat po/de.po | 27013 +++-- 1 file changed, 18992 insertions(+), 8020 deletions(-) → wc -l po/de.po 9373 po/de.po I'm especially concerned because it removes copyright statements of some of the previous translators. I'd expect either no removal at all or the removal of all previous translators if the file has been rewritten from scratch. diff --git a/po/de.po b/po/de.po index 2bffb38..18028f6 100644 --- a/po/de.po +++ b/po/de.po @@ -1,9373 +1,20346 @@ -# Deutsche Übersetzung zu Aptitude -# Copyright (c) 2002 Daniel Burrows -# Copyright (c) 2002 Erich Schubert er...@debian.org -# Copyright (c) 2004 Sebastian Kapfer sebastian_kap...@gmx.net -# Copyright (c) 2004 Dennis Stampfer se...@debian.org -# Copyright (c) 2006, 2008 Jens Seidel jenssei...@users.sf.net -# Copyright (c) 2010-2013 Holger Wansing li...@wansing-online.de -# Copyright (c) 2013 Benjamin Weis benjamin.w...@gmx.com +# German translation of aptitude's documentation. +# This file is distributed under the same license as the aptitude package. +# Sebastian Kapfer sebastian_kap...@gmx.net, 2004. +# Jens Seidel jenssei...@users.sf.net, 2009. +# Mario Blättermann mario.blaetterm...@gmail.com, 2014. I'd be happy if you or Mario could explain these changes. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712938: Info received (sni-qt -- Indicator support for Qt)
It's actually not possible, because Debian includes qt 4_4.8.7 (in sid). So I can't replace files with older version, most likely it won't work. How do you have 4.8.6 in Debian? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793683: fusionforge-db-local: unowned directories after purge: /var/lib/fusionforge/*
Package: fusionforge-db-local Version: 6.0.2+20150708-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned directories on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. Manual directory removal may be not appropriate as this directory is shared between several packages. If the package would ship these as empty directories, dpkg would take care of the creation and removal (if they are empty). From the attached log (scroll to the bottom...): 1m41.8s ERROR: FAIL: Package purging left files on system: /var/lib/fusionforge/docman/ not owned /var/lib/fusionforge/forum/not owned /var/lib/fusionforge/forum/pending/not owned /var/lib/fusionforge/tracker/ not owned cheers, Andreas fusionforge-db-local_6.0.2+20150708-1.log.gz Description: application/gzip
Bug#792362: cloud.debian.org: http://http.debian.net/ should be updated to http://httpredir.debian.org/ in /etc/apt/sources.list
On 07/14/2015 10:05 AM, Paweł Różański wrote: Package: cloud.debian.org Severity: minor Dear Maintainer, http://http.debian.net/ should be updated to http://httpredir.debian.org/ in /etc/apt/sources.list in cloud images, for example http://cdimage.debian.org/cdimage/openstack/8.1.0/debian-8.1.0 -openstack-amd64.qcow2 Kind regards, Paweł Hi, cloud.debian.org is *not* the correct package name. Please use openstack-debian-images from now on. Also, note that I don't think this kind of change will happen during the life of Debian 8 (aka Jessie), and may be fixed for the Stretch release. 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#298734: [PATCH] Add by-site group policy
Hi, Daniel Hartwig wrote in 2011: tags 298734 + patch block 603269 by 298734 thanks Attached patch contains a group policy named `site' for grouping packages according to their origin site (server). [...] - packages available from multiple sites appear *once* under each Sounds good to me. apt_preferences refers to this data using the keyword `origin', however, I have decided to use `site' for the group policy as I intend to now work on an equivilent search term and `?origin' is already in use. Using the keyword `origin' for this data seems more descriptive to me. I think that the group policy could be `origin' and the search term `?origin-site', any opinions on this? Why not just ?site? I consider the patch to be fairly complete, however opinions and naming suggestions are welcome. Looks fine to me. I though would prefer the shorter search term ?site. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793685: `yesod devel` fails without non-lo IPv4 address
Package: yesod Version: 1.4.11-1 Severity: normal Hi! Running `yesod devel` on a IPv6-only system (only the loopback device has a IPv4 address) fails. It stays in the state of applications hasn't finished building). As soon as I add some (even some invalid) IPv4 address to the outer interface it instantly works (and keeps working) Christoph -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yesod depends on: ii libc62.19-19 ii libffi6 3.2.1-3 ii libgmp10 2:6.0.0+dfsg-7 ii libyaml-0-2 0.1.6-3 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages yesod recommends: ii ghc7.8.4-9 ii libghc-aeson-dev 0.8.0.2-2+b4 ii libghc-classy-prelude-conduit-dev 0.11.1-1+b1 ii libghc-classy-prelude-dev 0.11.1.1-1+b1 ii libghc-classy-prelude-yesod-dev0.11.1-1 ii libghc-conduit-dev 1.2.4.2-1+b1 ii libghc-data-default-dev0.5.3-3+b3 ii libghc-fast-logger-dev 2.3.1-2+b4 ii libghc-file-embed-dev 0.0.8.2-2+b3 ii libghc-hjsmin-dev 0.1.4.7-5+b4 ii libghc-hspec-dev 2.1.7-2 ii libghc-http-conduit-dev2.1.5-1+b1 ii libghc-monad-control-dev 1.0.0.4-1 ii libghc-monad-logger-dev0.3.13.1-3+b6 ii libghc-persistent-dev 2.1.6-1+b2 ii libghc-persistent-sqlite-dev 2.1.4.2-1+b1 ii libghc-persistent-template-dev 2.1.3.4-1+b1 ii libghc-resourcet-dev 1.1.5-1+b1 ii libghc-safe-dev0.3.9-1 ii libghc-shakespeare-dev 2.0.5-1+b1 ii libghc-text-dev1.2.0.6-1 ii libghc-unordered-containers-dev0.2.5.1-2+b4 ii libghc-vector-dev 0.10.12.3-2+b4 ii libghc-wai-extra-dev 3.0.7.1-1+b1 ii libghc-wai-logger-dev 2.2.4.1-1+b1 ii libghc-warp-dev3.0.13.1-1+b1 ii libghc-yaml-dev0.8.11-1+b1 ii libghc-yesod-auth-dev 1.4.5.1-1+b1 ii libghc-yesod-core-dev 1.4.11-2 ii libghc-yesod-dev 1.4.1.5-1+b1 ii libghc-yesod-form-dev 1.4.4.1-3+b6 ii libghc-yesod-static-dev1.4.0.4-1+b6 ii libghc-yesod-test-dev 1.4.3.1-3+b6 yesod 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#793660: libsss-sudo: breaks sudo's default entry / floods root inbox with many SECURITY information emails.
Package: libsss-sudo Version: 1.12.5-1 Severity: normal Control: affects -1 sudo As reported in * https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777 * https://bugzilla.redhat.com/show_bug.cgi?id=879633 libsss-sudo breaks sudo's default entry in such way that sudo sends *** SECURITY information email with problem with defaults entries on every invocation of `sudo`. On my system `sudo` is actively used by several services so I'm getting hundred (or more) of such emails to root's inbox every hour. Uninstalling libsss-sudo stopped flood of emails. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: stretch/sid 500 testing-updates httpredir.debian.org 500 testing security.debian.org 500 testing httpredir.debian.org 333 unstablehttpredir.debian.org 1 experimentalhttpredir.debian.org -- Cheers, Dmitry Smirnov signature.asc Description: This is a digitally signed message part.
Bug#762054: [Pkg-fonts-devel] Bug#762054: d-i.debian.org: investigate ttf-* vs. fonts-* for udebs?
Quoting Cyril Brulebois (k...@debian.org): Hi Fabian, Fabian Greffrath fab...@debian.org (2015-07-10): Hi Cyril, Am Freitag, den 10.07.2015, 04:07 +0200 schrieb Cyril Brulebois: fonts-dejavu and fonts-freefont maintainers, do you concur? This would post-alpha 1. speaking as an Uplaoder for both fonts-freefont and fonts-dejavu, I'd concur that it should be safe and even recommended to switch to the new font packages and use the new package naming scheme. Many thanks for the swift reply+confirmation! I had this mail lying around in my TODO list and nwo I'm mostly ready to give this a try. Guys, do you think we want to manage a transition for, say ttf-freefont-udeb-fonts-freefont-udeb (with transitional package, etc. as we did for the ttf-fonts transitions)or will we just replace the package (given that only the installer is using the udeb) ? -- signature.asc Description: Digital signature
Bug#793666: /usr/bin/debsign: debsign should refuse to sign a changes file with Distribution: UNRELEASED by default
Package: devscripts Version: 2.15.5 Severity: wishlist File: /usr/bin/debsign Hi, when running dpkg-buildpackage in a source with UNRELEASED in the latest changelog entry, then I will get: dpkg-buildpackage: warning: not signing UNRELEASED build; use --force-sign to override I think this is sensible behaviour which debsign should copy. I.e. I propose that debsign also not sign changes files with Distribution: UNRELEASED by default but instead would require a --force-sign argument if the user really insists that they want this. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793667: gosa-plugin-netgroups not pulled-in when upgrading from Debian Edu squeeze mainserver
Package: education-main-server Severity: important Version: 1.812 When upgrading a Debian Edu mainserver from Debian squeeze to Debian jessie (via wheezy) the debian-edu-config-gosa-netgroups package gets removed (which is intended), but the gosa-plugin-netgroups package does not get pulled in. The reason is that gosa-* packages are listed under Recommends: of this bin:package rather than under Depends:. IMHO, we should consider moving some of the really required packages from Recommends: to Depends: to make sure the upgrade paths for the main server works fine. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpFyN2LbfN_A.pgp Description: Digitale PGP-Signatur
Bug#793606: always builds on all architectures
severity #793606 wishlist retitle #793606 please don't upload build requests to archs that don't need build thanks Hi Stephan, On Sun, Jul 26, 2015 at 11:04:45AM +0200, Stephan Sürken wrote: Fwiw, currently, mini-buildd just uploads build requests to all builders and completely relies on sbuild. This *is* a nice solution, as sbuild knows best, and no extra/duplicated code/dsc knowledge at all is needed in mini-buildd. So it is sbuild that does not honor the Architecture field? Should help me when returning to it ;). I guess it depends how simple it is to implement whether I am considering this... Done, thanks! Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793647: systemd: missing build conflict vs autoconf2.13 - AM_COND_IF: no such condition ARCH_IA32
Control: reassign -1 autoconf2.13 Am 26.07.2015 um 02:55 schrieb Ben Pfaff: On Sun, Jul 26, 2015 at 01:25:03AM +0200, Michael Biebl wrote: Am 25.07.2015 um 23:45 schrieb Alban Browaeys: Package: systemd Version: 222-2 Severity: normal Dear Maintainer, Building systemd from package source, on arm 32 bits, I get : configure.ac:1135: error: AM_COND_IF: no such condition ARCH_IA32 /usr/share/aclocal-1.15/cond-if.m4:23: AM_COND_IF is expanded from... configure.ac:1135: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 debian/rules:257: recipe for target 'autoreconf' failed make[2]: *** [autoreconf] Error 1 make[2]: Leaving directory '/home/prahal/Projects/Admin/systemd-222' dh_autoreconf: debian/rules autoreconf returned exit code 2 debian/rules:261: recipe for target 'override_dh_autoreconf' failed make[1]: *** [override_dh_autoreconf] Error 2 make[1]: Leaving directory '/home/prahal/Projects/Admin/systemd-222' debian/rules:281: recipe for target 'build' failed make: *** [build] Error 2 From similar issue against gummiboot : https:bugs.debian.org/cgi-bin/bugreport.cgi?bug=754911 there is a missing conflict with autoconf2.13. I'm not convinced this makes sense. My gut feeling is, that we have several thousand source packages which have AC_PREREQ([2.50]) in the archive and many packages nowadays run autoreconf during build [1]. Adding a Build-Conflicts against autconf2.13 to all of those packages seems like busy work without real gain. I think, autoconf2.13 should stop diverting /usr/bin/autoconf and related binaries (autoheader, autoreconf). dak finds only 14 packages which require autoconf2.13. It makes much more sense to me, if those packages are updated to call /usr/bin/autoconf2.13 directly. CCed the autoconf2.13 maintainer for their input. The wrapper in the autoconf2.13 package is supposed to automatically determine which version of Autoconf is necessary. I see a bug, however, which makes it fail to do that correctly with gummiboot. I can fix that, but I can't reproduce the same problem with systemd. With gummiboot, I just had to type autoreconf -f -i to get the error reported in bug #754911. I don't see that error, though, when I do the same with systemd (or if I run dpkg-buildpackage). Alban or Michael, how do you see the problem? (I tested against a slightly older systemd version, 215-17+deb8u1, not version 222-2. If there's been some important change since then, let me know, and I'll retest.) It might be time to remove the autoconf2.13 wrapper, since there is so little software that still uses Autoconf 2.13, but I'd prefer to know more about the bug first. Given Ben's explanation, the autoconf wrapper in autoconf2.13 should be able to detect if autoconf2.50 is supposed to be used. Either that wrapper is fixed, or the diversions are removed. In both cases, I this is something which needs to be addressed in autoconf2.13, thus reassigning. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#777983: Different problem in 0.10.2.2
Which is the case since 5.4.2 reached unstable on june 22. What that message is telling you is that you need to build litecoin with -fPIC. #if !defined(QT_BOOTSTRAPPED) defined(QT_REDUCE_RELOCATIONS) defined(__ELF__) \ (!defined(__PIC__) || (defined(__PIE__) defined(Q_CC_GNU) Q_CC_GNU = 500)) # error You must build your code with position independent code if Qt was built with -reduce-relocations. \ Compile your code with -fPIC (-fPIE is not enough). #endif looks like you can't use -fPIE? but yes, -fPIC is missing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793211: swi-prolog 7.2 breaks the ppl prolog bindings
Hi Eugeniy, No real clue. The stacktrace is definitely completely broken, I guess because too much symbol data is missing. I guess the simplest step is to make sure the compile flags include -g and possibly drop -O2 and symbols are not stripped. Then we might get a stacktrace that indicates the real problem. The type of error is typically caused by calls from C to Prolog that ignore the (FALSE) return value. The vital API functions do have the gcc attribute that causes gcc to warn on ignored return values, so inspecting the build log may give a clue. I can't do much right now as I'm travelling with only a small chromebook If you manage to produce a proper stack trace, please sent it. Might take a few days for me to respond. I'm back at the office as of August 10. Cheers --- Jan On 07/23/15 21:18, Eugeniy Meshcheryakov wrote: Hello Jan, I've got the following bug report from a Debian developer. Do you have any idea how to fix it? This issue prevents swi-prolog from migrating to Debian testing. The original bug report for PPL is available here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787486 This bug report is archived here (also contains the log file): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793211 Regards, Eugeniy Meshcheryakov 22 липня 2015 о 15:09 +0200 Matthias Klose написав(-ла): Package: src:swi-prolog Version: 7.2.0-2 Severity: important swi-prolog 7.2 breaks the ppl prolog bindings, such that ppl has to be built with -fpermissive. However running the tests reveals that these are then broken. swi-prolog 6 works fine. See #787486 for the ppl issue. [...] Making check in Prolog make[4]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog' /usr/bin/make check-recursive make[5]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog' Making check in . make[6]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog' make[6]: Nothing to be done for 'check-am'. make[6]: Leaving directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog' Making check in tests make[6]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog/tests' /usr/bin/make check-local make[7]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog/tests' /usr/bin/m4 --prefix-builtin -I../.. \ -I. -I./.. -I./../.. \ ./ppl_interface_generator_prolog_generated_test_pl.m4 \ ppl_prolog_generated_test_blob ../../../utils/cm_cleaner.sh ./ppl_prolog_generated_test_blob ../../../utils/cm_splitter.sh ./ppl_prolog_generated_test_blob rm -f ppl_prolog_generated_test_blob echo timestamp ppl_prolog_generated_test.stamp make[7]: Leaving directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog/tests' make[6]: Leaving directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog/tests' Making check in SWI make[6]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog/SWI' /usr/bin/make ppl_pl pl_clpq pl_clpq2 make[7]: Entering directory '/scratch/packages/tmp/ppl-1.1/interfaces/Prolog/SWI' x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../interfaces -I../../../interfaces/Prolog -I/interfaces/Prolog -I../../../src -I/usr/lib/swi-prolog/include -I/usr/include/pl -D_FORTIFY_SOURCE=2 -g -O2 -frounding-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall -MT ppl_pl.o -MD -MP -MF .deps/ppl_pl.Tpo -c -o ppl_pl.o ppl_pl.cc x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../interfaces -I../../../interfaces/Prolog -I/interfaces/Prolog -I../../../src -I/usr/lib/swi-prolog/include -I/usr/include/pl -D_FORTIFY_SOURCE=2 -g -O2 -frounding-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall -MT pl_clpq.o -MD -MP -MF .deps/pl_clpq.Tpo -c -o pl_clpq.o pl_clpq.cc mv -f .deps/ppl_pl.Tpo .deps/ppl_pl.Po mv -f .deps/pl_clpq.Tpo .deps/pl_clpq.Po /usr/bin/swipl-ld -pl /usr/bin/swipl -cc x86_64-linux-gnu-gcc -c++ x86_64-linux-gnu-g++ -ld x86_64-linux-gnu-g++ \ -ld-options`echo '' -g -O2 -frounding-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall | tr /` \ -o ppl_pl .libs/libppl_swiprolog.a ppl_pl.o \ -L../../../src/.libs \ -lppl -lgmpxx -lgmp /usr/bin/swipl-ld -pl /usr/bin/swipl -cc x86_64-linux-gnu-gcc -c++ x86_64-linux-gnu-g++ -ld x86_64-linux-gnu-g++ \ -ld-options`echo '' -g -O2 -frounding-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall | tr /` \ -o pl_clpq .libs/libppl_swiprolog.a pl_clpq.o \ ./pl_clpq.pl ./../tests/clpq.pl \ -L../../../src/.libs \ -lppl -lgmpxx -lgmp /usr/bin/swipl-ld -pl /usr/bin/swipl -cc x86_64-linux-gnu-gcc -c++ x86_64-linux-gnu-g++ -ld x86_64-linux-gnu-g++ \ -ld-options`echo ''
Bug#736831: cortina: dont change wallpaper
tag 736831 - patch thank you -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#257102: phpBB support
Hello, phpBB 3.1.5 is now available , please be sure to backup your forum before staring in the update process . we are happy to help you in updating your forum safely, please reply to this email if you are interested in our paid sevices . Thank you -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787582: VDPAU needed
Hi, In that case could you please also put the libvdpau1 and libvdpau1:i386 packages in experimental ? They're actually required to install nvidia-driver 352 and the only way we currently have to install these updates is to pin these packages from testing. (And actually we'd need them in backports) Thanks a lot ! Julien.
Bug#787582: VDPAU needed
Hi Julien, On Sat, Jul 25, 2015 at 11:50 PM, Julien Aubin jul.au...@laposte.net wrote: Hi, In that case could you please also put the libvdpau1 and libvdpau1:i386 packages in experimental ? No, because AFAIK packages in experimental can't share the same version as a package already uploaded to sid (because packages belonging to the latter suite supersede packages in experimental with the same/older versions). They're actually required to install nvidia-driver 352 and the only way we currently have to install these updates is to pin these packages from testing. (And actually we'd need them in backports) If it helps, I can upload src:libvdpau to jessie-backports. 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#790856: please consider shipping key in keyring package as /fragment in trusted.gpg.d
On Do, 2015-07-02 at 14:12 +0200, Marc Haber wrote: (...) the debian-archive-keyring package has - starting with wheezy - changed to ship the archive keys in dedicated files in /etc/apt/trusted.gpg.d instead of using apt-key. In my opinion, it would be a good idea if mini-buildd did the same in its keyring packages. fwiw, when trying to solve this, we need to keep in mind that the keyring package (i.e., both src and deb) needs to be compatible to (at least) all distributions mini-buildd claims to support via it's wizards. Hth, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790056: please consider a shorter or a configurable origin in reprepro config
On Fr, 2015-06-26 at 18:55 +0200, Marc Haber wrote: (...) the rather terse Debian in the normal Debian archives. This leads to pin lines like Pin: release n=sid-test-unstable, o=Mini-Buildd archive zg on spinturn.zugschlus.de which is like asking for trouble in my opinion regarding the spaces in the origin value. Do I need to quote the string? No. You even must not. Do I need to quote the spaces? No. You even must not. Will it work when the o= part is not last in the line? Yes. Will it work when I use an additional space before the comma separating the next pin item in the pin line? Yes ;). I cannot proof this with actual documentaion ;), but is has worked so for years and years: it seems apt splits the string on ,, and then removes leading and tailing whitespaces on the items. All this could be avoided by using a much shorter default value for Origin, or making the Origin configurable. As far as I understand the new mini-buildd logic, this field should be part of the distribution object inside mini-buildd's configuration. Agreed anyway (that this should be configurable). The default value needs to be more complicated, as we want to generate a different Origin by default for any mini-buildd instance. Hth, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793491: ITP: rocksdb -- A persistent key-value store for fast storage environments
retitle 793491 ITP: rocksdb -- A persistent key-value store for fast storage environments owner 793491 ! thanks The package is ready, quick local testing shows it's working. But its self test fails: [ RUN ] ColumnFamilyTest.ReadDroppedColumnFamily db/column_family_test.cc:1101: Failure Value of: kKeysNum * ((i == 2) ? 1 : 2) Actual: 1 Expected: count Which is: 9231 terminate called after throwing an instance of 'testing::internal::GoogleTestFailureException' what(): db/column_family_test.cc:1101: Failure Value of: kKeysNum * ((i == 2) ? 1 : 2) Actual: 1 Expected: count Which is: 9231 Aborted -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789837: FTBFS: all tests error with LoadError: cannot load such file -- rubyeventmachine
the rack handler automaticaly with a simple rack app - sets default rack handler to thin when in ruby and WEBrick when in jruby with a launch path specified as a proc - evaluates the proc in the context of the runner with a launch path specified as string - launches to the specific path without environment - should be ok with --app-dir - should raise an exception without --app-dir 26 specifications (26 requirements), 0 failures, 0 errors /usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner ┌──┐ │ Run tests for ruby2.2 from debian/ruby-tests.rb │ └──┘ RUBYLIB=/«PKGBUILDDIR»/debian/ruby-vegas/usr/lib/ruby/vendor_ruby:. ruby2.2 debian/ruby-tests.rb *** Mocha deprecation warning: Test::Unit or MiniTest must be loaded *before* `require 'mocha/setup'`. *** Mocha deprecation warning: If you're integrating with a test library other than Test::Unit or MiniTest, you should use `require 'mocha/api'` instead of `require 'mocha/setup'`. /«PKGBUILDDIR»/test/test_vegas_runner.rb:166: warning: already initialized constant Vegas::Runner::ROOT_DIR /«PKGBUILDDIR»/test/test_vegas_runner.rb:5: warning: previous definition of ROOT_DIR was here Vegas::Runner creating an instance basic usage - sets app - sets app name - sets quoted app name - sets filesystem friendly app name - stores options - puts unparsed args into args - parses options into @options - writes the app dir - writes a url with the port - knows where to find the pid file basic usage with a funky app name - sets app - sets app name - sets quoted app name - sets filesystem friendly app name - stores options - puts unparsed args into args - parses options into @options - writes the app dir - writes a url with the port - knows where to find the pid file with a sinatra app using an explicit server setting - sets the rack handler automaticaly with a simple rack app - sets default rack handler to thin when in ruby and WEBrick when in jruby with a launch path specified as a proc - evaluates the proc in the context of the runner with a launch path specified as string - launches to the specific path without environment - should be ok with --app-dir - should raise an exception without --app-dir 26 specifications (26 requirements), 0 failures, 0 errors ┌──┐ │ dh_ruby --install finished │ └──┘ dh_installdocs -O--buildsystem=ruby dh_ruby_fixdocs -O--buildsystem=ruby dh_installchangelogs -O--buildsystem=ruby dh_perl -O--buildsystem=ruby dh_link -O--buildsystem=ruby dh_compress -X.rb -O--buildsystem=ruby dh_fixperms -O--buildsystem=ruby dh_installdeb -O--buildsystem=ruby dh_gencontrol -O--buildsystem=ruby dpkg-gencontrol: warning: Depends field of package ruby-vegas: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe dh_md5sums -O--buildsystem=ruby dh_builddeb -O--buildsystem=ruby dpkg-deb: building package 'ruby-vegas' in '../ruby-vegas_0.1.11-2_all.deb'. dpkg-genchanges ../ruby-vegas_0.1.11-2_i386.changes dpkg-genchanges: not including original source code in upload dpkg-source --after-build ruby-vegas-0.1.11 dpkg-buildpackage: binary and diff upload (original source NOT included) Build finished at 20150726-1518 Finished I: Built successfully ┌──┐ │ Post Build Chroot│ └──┘ lintian ─── Merged Build-Depends: lintian Filtered Build-Depends: lintian dpkg-deb: building package 'sbuild-build-depends-lintian-dummy' in '/«BUILDDIR»/resolver-jhkADo/apt_archive/sbuild-build-depends-lintian-dummy.deb'. gpg: WARNING: unsafe permissions on homedir `/«BUILDDIR»/resolver-jhkADo/gpg' OK Ign file: ./ InRelease Get:1 file: ./ Release.gpg [299 B] Get:2 file: ./ Release [2119 B] Ign file: ./ Translation-en Reading package lists... Reading package lists... ┌──┐ │ Install lintian build dependencies (aptitude-based resolver) │ └──┘ Reading package lists... Building dependency tree... Reading state
Bug#793682: yakuake: Should conflict with konsole in experimental
Package: yakuake Version: 2.9.9-1 Severity: normal Dear Maintainer, installing the version of konsole currently in experimental: 4:15.04.3-1 will break yakuake. Perhaps it would be better to change the control file to reflect this. Best -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.8j (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yakuake depends on: ii kde-runtime4:14.12.3-1 ii konsole4:4.14.2-1 ii libc6 2.19-19 ii libgcc11:5.1.1-14 ii libkdecore54:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkio54:4.14.2-5 ii libknewstuff3-44:4.14.2-5 ii libknotifyconfig4 4:4.14.2-5 ii libkparts4 4:4.14.2-5 ii libnepomuk44:4.14.2-5 ii libnepomukutils4 4:4.14.2-5 ii libqt4-dbus4:4.8.7+dfsg-1 ii libqt4-network 4:4.8.7+dfsg-1 ii libqt4-svg 4:4.8.7+dfsg-1 ii libqt4-xml 4:4.8.7+dfsg-1 ii libqtcore4 4:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libsoprano42.9.4+dfsg-1.1 ii libstdc++6 5.1.1-14 ii libx11-6 2:1.6.3-1 yakuake recommends no packages. yakuake 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#712938: sni-qt -- Indicator support for Qt
On Sun, 26 Jul 2015 10:48:07 -0300 Lisandro =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com wrote: That's the perfect way to break your system... I was cautious when doing that and my system works well. The compilation were compatible, otherwise my Qt4 apps wouldn't work. My Debian is Testing. And I emphasized on backing up the original files. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755303: RFA: remmina -- remote desktop client for GNOME desktop environment
Hello, what is the current status of the adoption? My offer for adoption is still true. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#793606: always builds on all architectures
On So, 2015-07-26 at 11:22 +0200, Marc Haber wrote: (...) On Sun, Jul 26, 2015 at 11:04:45AM +0200, Stephan Sürken wrote: Fwiw, currently, mini-buildd just uploads build requests to all builders and completely relies on sbuild. This *is* a nice solution, as sbuild knows best, and no extra/duplicated code/dsc knowledge at all is needed in mini-buildd. So it is sbuild that does not honor the Architecture field? No, sbuild would run fine and result with status skipped (which is a successful build). In your setup mini-buildd does not find any builder for the your arch (to eventually run sbuild on) in the first place. Htei, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd
I found a serverfault answer that led me down the path of reasoning below. Have a look: http://serverfault.com/a/706494 If sshd is configured with UsePAM yes, then after installing libpam -systemd to a remote system and rebooting, ssh sessions are cleanly terminated… Given the above and that: * openssh-server comes configured _out of the box_ with UsePAM=yes enabled * Openssh-server's installation default is as a systemd service * libpam-systemd adds functionality to openssh-server in that connections are properly terminated upon shutdown (while the ‘maintain connections’ behavior if the sshd process is stopped/restarted is preserved) * There is no mention of the package libpam-systemd as being related in any way at all to openssh-server on https://packages.debian.org/jessie/openssh-server (rec/sug/enh, much less as a hard dependency) …My feeling is, I’d construe THAT to be the real bug here. I don’t know enough about debian’s package relationships to say what relationship libpam-systemd should have to openssh-server, but I’m pretty sure that ‘none whatsoever’ is not the answer. Similarly, I still see the issue from time to time, even though I have PAM enabled. E.g. just a few minutes ago it happened again with: # reboot PolicyKit daemon disconnected from the bus. We are no longer a registered authentication agent. 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. here it hangs As suggested in the serverfault answer, and possibly by the above error, does dbus need a relationship either to systemd or openssh-server? ArchLinux and FedoraCore both list dbus as a _requirement_ for systemd. Debian does not AFAICT, and I’m wondering if that should change. [Yes, this is me saying ‘Others do it, why don’t we?’, but I think it’s a fair question to ask here. If dbus would provide information to systemd to manage openssh-server client connections more effectively, shouldn’t it be a dependency to one or the other?] Best, R.S. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793663: [unattended-upgrades] Unsupported operand type(s) for %: 'bytes' and 'tuple'
Package: unattended-upgrades Version: 0.86.2 Severity: normal --- Please enter the report below this line. --- Dear maintainers: APT complains on some operand error due to unattended-upgrades: /etc/cron.daily/apt: Exception: unsupported operand type(s) for %: 'bytes' and 'tuple' Traceback (most recent call last): File /usr/bin/unattended-upgrade, line 1435, in module main(options) File /usr/bin/unattended-upgrade, line 1382, in main pkgs, pkg_install_success, pkgs_kept_back, mem_log, log_content) File /usr/bin/unattended-upgrade, line 816, in send_summary_mail body = _(Unattended upgrade returned: %s\n\n) % res TypeError: unsupported operand type(s) for %: 'bytes' and 'bool' Regards, Antonio --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 900 testing security.debian.org 900 testing ftp.es.debian.org 800 stable update.devolo.com 800 stable kxstudio.linuxaudio.org 800 stable dl.google.com 500 trusty ppa.launchpad.net 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#793205: Hitting the same bug
Hi, I can report I'm hitting the same bug. Since upgrading to the last version of virtualbox on SID, each time I start my windows 7 x64 guest it crashes during the start, if the scanner is on. If I switch the scanner off and start, all is ok. If I switch the scanner on when the guest is started, it crashes. If I deactivate the USB 2.0 (EHCI) controller, all is ok (but I can't access my scanner so ...) I'll see if I can test VB 5 from experimental, but that bug is pretty annoying (personnally, I'm using that W7 guest ONLY for scanning ...) Bye. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793609: dh-python: pybuild incorrectly parses Build-Depends
On Sun, Jul 26, 2015 at 08:12:35AM +0200, Raphael Hertzog wrote: On Sat, 25 Jul 2015, James McCoy wrote: Attached patch should fix the issue. It also introduces another regression in that it ignores Build-Depends-Indep and Build-Depends-Arch now. Indeed. I knew the Build-Depends match looked odd, but it didn't click why. Updated patch attached. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org From 60cffaf3f787a40c5b69c7d2f6401768e33c514f Mon Sep 17 00:00:00 2001 From: James McCoy james...@debian.org Date: Sat, 25 Jul 2015 14:49:54 -0400 Subject: [PATCH] pybuild: Use Dpkg::Control to parse debian/control The manual parsing failed to handle comment lines in the Build-Depends field. Using Dpkg::Control avoids this since the resulting string already has comments removed. --- debian/control | 4 ++-- dh/pybuild.pm | 14 -- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/debian/control b/debian/control index 2666816..8325f33 100644 --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Section: python Priority: optional Maintainer: Piotr Ożarowski pi...@debian.org Uploaders: Stefano Rivera stefa...@debian.org, Barry Warsaw ba...@debian.org -Build-Depends: debhelper (= 9), python3-minimal, libpython3-stdlib, +Build-Depends: debhelper (= 9), python3-minimal, libpython3-stdlib, libdpkg-perl, # provides rst2man command (python3-docutils not used to avoid circular deps): python-docutils Standards-Version: 3.9.6 @@ -14,7 +14,7 @@ X-Python3-Version: = 3.2 Package: dh-python Architecture: all Multi-Arch: foreign -Depends: ${misc:Depends}, ${python3:Depends} +Depends: libdpkg-perl, ${misc:Depends}, ${python3:Depends} Breaks: # due to /usr/bin/dh_python3 and debhelper files python3 ( 3.3.2-4~) diff --git a/dh/pybuild.pm b/dh/pybuild.pm index eef5818..ef1810b 100644 --- a/dh/pybuild.pm +++ b/dh/pybuild.pm @@ -8,6 +8,7 @@ package Debian::Debhelper::Buildsystem::pybuild; use strict; +use Dpkg::Control; use Debian::Debhelper::Dh_Lib qw(error doit); use base 'Debian::Debhelper::Buildsystem'; @@ -155,15 +156,16 @@ sub python_build_dependencies { my $this=shift; my @result; - open (CONTROL, 'debian/control') || error(cannot read debian/control: $!\n); - foreach my $builddeps (join('', CONTROL) =~ - /^Build-Depends[^:]*:.*\n(?:^[^\w\n#].*\n)*/gmi) { - while ($builddeps =~ /[\s,](pypy|python[0-9\.]*(-all)?((-dev)|(-dbg))?)[\s,]|$/g) { - if ($1) {push @result, $1}; + my $c = Dpkg::Control-new(type = CTRL_INFO_SRC); + if ($c-load('debian/control')) { + for my $field (grep /^Build-Depends/, keys %{$c}) { + my $builddeps = $c-{$field}; + while ($builddeps =~ /(?:^|[\s,])(pypy|python[0-9\.]*(-all)?((-dev)|(-dbg))?)(?:[\s,]|$)/g) { +if ($1) {push @result, $1}; + } } } - close CONTROL; return @result; } -- 2.4.6 signature.asc Description: Digital signature
Bug#791651: Does not run chroot hooks
this is already fixed in git Not quite, see [1] Cheers Daniel [1] http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=2a400dc63ec7305c80dd072984a14839aed74501 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793671: dgit clone python-numpy experimental fails
Package: dgit Version: 1.0 Severity: normal Dear Maintainer, $ dgit clone python-numpy experimental starting new git history downloading http://ftp.debian.org/debian//pool/main/p/python-numpy/python- numpy_1.9.2-1.dsc... last upload to archive has NO git hash % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3892k 100 3892k0 0 2069k 0 0:00:01 0:00:01 --:--:-- 2068k % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 136k 100 136k0 0 793k 0 --:--:-- --:--:-- --:--:-- 796k dpkg-source: info: extracting python-numpy in python-numpy-1.9.2 dpkg-source: info: unpacking python-numpy_1.9.2.orig.tar.gz dpkg-source: info: unpacking python-numpy_1.9.2-1.debian.tar.xz dpkg-source: info: applying 02_build_dotblas.patch dpkg-source: info: applying 03_force_f2py_version.patch dpkg-source: info: applying 10_use_local_python.org_object.inv_sphinx.diff dpkg-source: info: applying python3-soabi.patch dpkg-source: info: applying adapt_swig_docs_to_debian.patch Format `3.0 (quilt)', checking/updating patch stack fatal: Not a git repository: /home/vagrant/repos/numpy/.git/modules/doc/sphinxext dgit: failed command: git add -Af dgit: subprocess failed with error exit status 128 Note that on the system where I ran this command, /home/vagrant does not exist. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dgit depends on: ii ca-certificates20150426 ii coreutils 8.23-4 ii curl 7.43.0-1 ii devscripts 2.15.5 ii dpkg-dev 1.18.1 ii dput 0.9.6.4 ii git [git-core] 1:2.4.6-1 ii libdpkg-perl 1.18.1 ii libjson-perl 2.90-1 ii libwww-perl6.13-1 ii perl [libdigest-sha-perl] 5.20.2-6 Versions of packages dgit recommends: ii openssh-client [ssh-client] 1:6.7p1-6 Versions of packages dgit suggests: pn sbuild 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#793672: how-can-i-help: output gets slightly messed up when using dpkg progress bar
Package: how-can-i-help Version: 11 Severity: minor Dear Maintainer, if I enable the dpkg progress bar, the last progress status still shows up below the output of how-can-i-help, like this: == How can you help? (doc: https://wiki.debian.org/how-can-i-help ) == - Show old opportunities as well as new ones: how-can-i-help --old -.] Premere Invio per continuare. In order to reproduce this behavior, enable the dpkg fancy output and then let the output of how-can-i-help show after installing or updating some packages. Dpkg fancy output (available since apt 1.0, see [1]) can be enabled with this command issued as root: # echo 'Dpkg::Progress-Fancy 1;' /etc/apt/apt.conf.d/99progressbar Maybe clearing lines before writing them may help, I know there are ANSI escape sequences for that but I am not sure how portable they are. Or maybe this is an apt issue? Thanks, Antonio [1] https://mvogt.wordpress.com/2014/04/04/apt-1-0/ -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-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/bash Init: systemd (via /run/systemd/system) Versions of packages how-can-i-help depends on: ii ruby 1:2.1.5.1 ii ruby-debian 0.3.9+b1 ii ruby-json1.8.3-1 how-can-i-help recommends no packages. how-can-i-help suggests no packages. -- no debconf information -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793673: exfalso: import quodlibet.commands segfaults if DISPLAY is unset
Package: exfalso Version: 3.4.0-1 $ env -u DISPLAY python -c 'import quodlibet.commands' ** (-c:737): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused (-c:737): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Segmentation fault (See bug #793407 for context.) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages exfalso depends on: ii gir1.2-gtk-3.0 3.16.6-1 ii libjs-sphinxdoc 1.3.1-2 ii python 2.7.9-1 ii python-gi3.16.2-1 ii python-gi-cairo 3.16.2-1 ii python-mutagen 1.28-2 pn python:any none -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712938: No change?
On Sunday 26 July 2015 12:42:56 Michał Milanowski wrote: Can't any debian dev see his stupidity regarding to this issue? There are tons of qt4 apps that are widely used and will be probably never ported to qt5, like Skype for example, but many others too. Hi! I'm the Qt maintainer, and yes, I understand your arguments, but again: do you really want to push dead-upstream code and support it trough the whole life of Stretch? I don't. You decided to drop support for them just like that (90% actually used linux apps) and you are providing the only solution Port your app to qt5. Or someone to step up and become a sni-qt upstream, fix it's bugs and we can reconsider. All workarounds decrived here look like a joke, not real solution. Yes, sadly they failed to me too :( Ubuntu provided this patch, Arch provided too. Every known distro has workaround built in by patching qt to make their users live easier. But not Debian. For the reasons I have already stated. Shame and f you (sorry!). That was definitely too much. Please refrain from that kind of comments in the future. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#789187: moarvm finally works for me on mipsel
Tags: pending Hello, I just push the master branch of pkg-moarvm for 2015.07-1. This release include libffi support. I asked upstream if we should use libffi for all architectures but they prefer to only use it for dyncall unsupported ones. The libffi support may open new architectures, but I think we should test them before enabling them. Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF signature.asc Description: PGP signature
Bug#761368: Need to wait for graywolf
Hi Ruben, I think we need to wait until graywolf has passed NEW until this package canbe built in unstable. Please ping me once this has happened. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777983: Different problem in 0.10.2.2
On Sunday 26 July 2015 12:45:58 Matthias Klose wrote: [snip] looks like you can't use -fPIE? but yes, -fPIC is missing. It seems that yes, when -Bsymbolics-functions is used -fPIC is needed in order to avoid copy relocations bugs. Seems that all this time we got away with an unspecified behaviour of gcc, which changed with gcc5 on amd64. Other archs suffered the problem before, but we never received a crash report from them (like armhf, for example), so we realized this when it started popping up on amd64/i386+gcc5. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#793671: dgit clone python-numpy experimental fails
Control: severity 793671 serious Christopher Baines writes (Bug#793671: dgit clone python-numpy experimental fails): Package: dgit Format `3.0 (quilt)', checking/updating patch stack fatal: Not a git repository: /home/vagrant/repos/numpy/.git/modules/doc/sphinxext I have reproduced this. The problem is: $ egrep . python-numpy-1.9.2/doc/sphinxext/.git gitdir: /home/vagrant/repos/numpy/.git/modules/doc/sphinxext $ dgit needs to get rid of things like this. (Currently it bails if it finds .git in the package toplevel, but I think it would be better if it removed this, and .git anywhere else too. Perhaps with a warning.) I have set the severity to serious because this is in principle a sort-of-exploitable vulnerability. DDs and DMs can cause your dgit to look in strange places and maybe do bad things to some of your other git repos. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789340: libio-stty-perl: diff for NMU version 0.03-1.1
On Fri, Jul 24, 2015 at 12:04:39PM +, Damyan Ivanov wrote: Dear maintainer, I've prepared an NMU for libio-stty-perl (versioned as 0.03-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Go ahead, thanks. Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793662: incomplete snapshots per interval
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: rsnapshot Version: 1.4.0-1 The new version seems to silently skip over unreachable hosts. Sample session (using the old hourly, daily, etc interval names): {root@sylvester:rsnapshot () 698} ls -al hourly.* daily.* daily.0: total 20 drwxr-xr-x 5 root root 4096 Jul 23 18:28 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 23 05:39 cecil drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester daily.1: total 16 drwxr-xr-x 4 root root 4096 Jul 24 18:19 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 22 17:39 cecil drwxr-xr-x 14 root root 4096 May 29 18:25 marvin daily.2: total 32 drwxr-xr-x 8 root root 4096 Jul 22 02:13 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 18 05:45 cecil drwxr-xr-x 17 root root 4096 Apr 7 19:45 daffy drwxr-xr-x 26 root root 4096 Dec 14 2014 elmer drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 25 root root 4096 Jan 31 20:06 porky drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester daily.3: total 32 drwxr-xr-x 8 root root 4096 Jul 21 02:13 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 18 05:45 cecil drwxr-xr-x 17 root root 4096 Apr 7 19:45 daffy drwxr-xr-x 26 root root 4096 Dec 14 2014 elmer drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 25 root root 4096 Jan 31 20:06 porky drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester daily.4: total 32 drwxr-xr-x 8 root root 4096 Jul 20 02:14 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 18 05:45 cecil drwxr-xr-x 17 root root 4096 Apr 7 19:45 daffy drwxr-xr-x 26 root root 4096 Dec 14 2014 elmer drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 25 root root 4096 Jan 31 20:06 porky drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester daily.5: total 32 drwxr-xr-x 8 root root 4096 Jul 19 02:13 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 18 05:45 cecil drwxr-xr-x 17 root root 4096 Apr 7 19:45 daffy drwxr-xr-x 26 root root 4096 Dec 14 2014 elmer drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 25 root root 4096 Jan 31 20:06 porky drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester daily.6: total 32 drwxr-xr-x 8 root root 4096 Jul 18 02:15 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 17 04:11 cecil drwxr-xr-x 17 root root 4096 Apr 7 19:45 daffy drwxr-xr-x 26 root root 4096 Dec 14 2014 elmer drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 25 root root 4096 Jan 31 20:06 porky drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester hourly.0: total 16 drwxr-xr-x 4 root root 4096 Jul 26 06:18 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxr-xr-x 14 root root 4096 Jul 25 18:42 marvin drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester hourly.1: total 16 drwxr-xr-x 4 root root 4096 Jul 26 02:09 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxr-xr-x 14 root root 4096 Jul 25 18:42 marvin drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester hourly.2: total 24 drwxr-xr-x 6 root root 4096 Jul 25 18:30 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 23 05:39 cecil drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 25 root root 4096 Jan 31 20:06 porky drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester hourly.3: total 20 drwxr-xr-x 5 root root 4096 Jul 25 06:32 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 23 05:39 cecil drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester hourly.4: total 16 drwxr-xr-x 4 root root 4096 Jul 25 02:10 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester hourly.5: total 20 drwxr-xr-x 5 root root 4096 Jul 24 06:38 . drwxr-xr-x 21 root root 4096 Jul 26 06:16 .. drwxrwxrwt 40 root root 4096 Jul 23 05:39 cecil drwxr-xr-x 14 root root 4096 May 29 18:25 marvin drwxr-xr-x 33 root root 4096 Oct 22 2014 sylvester See all the missing host directories in hourly.? and daily.[01]? Using the new rsnapshot version they fell behind. I am highly concerned that they won't be included into the weekly and monthly interval, either. This is *highly* painful. The hosts are turned off on purpose, and yet I could rely upon Jessie's rsnapshot to not forget about these hosts, making sure there is always a copy. For the new rsnapshot this is gone :-(. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVtJasAAoJEAqeKp5m04HLeCIH/3lscRjAmAU0PGVpa3KhFtzy i6haOa4+OK7oF3oNOT7wd5HCVjoDTYxkh4QbRkEoAPZxC1cVixV3niZ/TqKDYU8E +ZKcP/0+oYNJ4WhmaWgDJd5vZFJ94nWNxEo0yOA2rJdvT9Tdsh5Oqw+H45Eq9vVB 1orbmGC5G1lNX0YF7oBspEV8Bw4PniJNEJCucy8gwBvA1dCXJsi34CtD+yKp6cdE
Bug#778112: [buildd-tools-devel] Bug#778112: Bug#778112: Bug#778112: schroot: ftbfs with GCC-5
On 07/26/2015 12:09 AM, Roger Leigh wrote: On 25/07/2015 22:07, Roger Leigh wrote: On 25/07/2015 21:45, Roger Leigh wrote: OK, some further investigation has shown what the exact error is. It looks like a GCC bug. Please see the attached source file testcase. This regex is failing: std::regex(^[a-z0-9][a-z0-9-]*$, std::regex::extended); however this one works: std::regex(^[a-z0-9][-a-z0-9]*$, std::regex::extended); In the same vein, the attached sample using basic rather than extended expressions fails in the opposite way. In this case both compile but the latter expression fails to match correctly. Since the expression should be valid and behave the same in both cases, it looks like there are two bugs here, the first being unable to compile a valid extended regex, the second here being unable to match (which is likely also a compile failure, but not a fatal one). Note this latter issue is seen with GCC 4.9 but appears to work with GCC 5. now forwarded as https://gcc.gnu.org/PR67015 however I can't see different behaviour with 4.9 and 5 (making sure to use the corresponding library using -static-libstdc++). Also I see regex2.cc always succeeding. $ cat run.sh g++-4.8 -static-libstdc++ -std=c++0x regex.cc ./a.out g++-4.9 -static-libstdc++ -std=c++0x regex.cc ./a.out g++-5 -static-libstdc++ -std=c++0x regex.cc ./a.out /usr/lib/gcc-snapshot/bin/g++ -static-libstdc++ -std=c++0x regex.cc ./a.out clang++-3.5 -stdlib=libc++ -std=c++0x regex.cc ./a.out clang++-3.6 -stdlib=libc++ -std=c++0x regex.cc ./a.out g++-4.8 -static-libstdc++ -std=c++0x regex2.cc ./a.out g++-4.9 -static-libstdc++ -std=c++0x regex2.cc ./a.out g++-5 -static-libstdc++ -std=c++0x regex2.cc ./a.out /usr/lib/gcc-snapshot/bin/g++ -static-libstdc++ -std=c++0x regex2.cc ./a.out clang++-3.5 -stdlib=libc++ -std=c++0x regex2.cc ./a.out clang++-3.6 -stdlib=libc++ -std=c++0x regex2.cc ./a.out + g++-4.8 -static-libstdc++ -std=c++0x regex.cc + ./a.out E0: regex_error a.out: regex.cc:24: int main(): Assertion `std::regex_match(test, debian_cron_namespace)' failed. Aborted (core dumped) + g++-4.9 -static-libstdc++ -std=c++0x regex.cc + ./a.out E1: regex_error + g++-5 -static-libstdc++ -std=c++0x regex.cc + ./a.out E1: regex_error + /usr/lib/gcc-snapshot/bin/g++ -static-libstdc++ -std=c++0x regex.cc + ./a.out E1: regex_error + clang++-3.5 -stdlib=libc++ -std=c++0x regex.cc + ./a.out + clang++-3.6 -stdlib=libc++ -std=c++0x regex.cc + ./a.out + g++-4.8 -static-libstdc++ -std=c++0x regex2.cc + ./a.out E0: regex_error E1: regex_error E2: regex_error + g++-4.9 -static-libstdc++ -std=c++0x regex2.cc + ./a.out + g++-5 -static-libstdc++ -std=c++0x regex2.cc + ./a.out + /usr/lib/gcc-snapshot/bin/g++ -static-libstdc++ -std=c++0x regex2.cc + ./a.out + clang++-3.5 -stdlib=libc++ -std=c++0x regex2.cc + ./a.out + clang++-3.6 -stdlib=libc++ -std=c++0x regex2.cc + ./a.out -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793606: always builds on all architectures
Moin, On Sa, 2015-07-25 at 15:28 +0200, Marc Haber wrote: (...) my mini-buildd is configured to have architectures amd64, i386 and armhf. The armhf arch was just recently added so that I could poke locally built packages into the repository using direct reprepro calls and to be prepared to have mini-buildd actually build armhf packages. I do not yet have an armhf builder since my only armhf system is running jessie and does not have enough storage to support a sid chroot, and I would like to spare myself from backporting mini-buildd to jessie. ftra, I am always doing ports for jessie (via Debian Backports) or even wheezy (via my own repo). When mini-buildd builds a package now, the build fails because there is no armhf builder. With one build failing like that, the packages resulting from the successful builds on i386 and amd64 are not uploaded to the archive. (...) I tried my package now with Architecture: amd64 in all binary (...) Despite this, mini-buildd attempted to build the package for i386 (successful) and armhf (failed, no builder available), and didn't upload the amd64 package to the archive. (...) I think that mini-buildd should honor the Architecture: field in uploaded packages and refrain from trying to build on arches that the packager doesn't want. hmm ok, for that special setup (having no builder at all for a required arch), it would be a nice to have. Fwiw, currently, mini-buildd just uploads build requests to all builders and completely relies on sbuild. This *is* a nice solution, as sbuild knows best, and no extra/duplicated code/dsc knowledge at all is needed in mini-buildd. As this case is already covered by confing the arch as optional, can we put that to wishlist and rename it to please don't upload build requests to archs that don't need build? Should help me when returning to it ;). I guess it depends how simple it is to implement whether I am considering this... Thx! S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748944: [Pkg-xfce-devel] Processed: Re: Processed (with 1 errors): on how lightdm does not like it when /etc/X11/Xsession is not executable
reopen 748944 thanks On Fri, Jul 24, 2015 at 10:55:12PM +0200, Julien Cristau wrote: On Thu, Jul 23, 2015 at 10:06:42 +0200, Josip Rodin wrote: reassign 748944 x11-common retitle 748944 lightdm relies on the executability of /etc/X11/Xsession, please enforce it thanks x11-common installs /etc/X11/Xsession executable. Anything beyond that is not its responsibility. I'm sure all of our users who hit this bug will be thrilled to see this kind of behavior. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778034: ogre-1.9 needs a library transition for GCC 5
retitle 778034 ogre-1.9: library transition is needed when GCC 5 is the default user debian-...@lists.debian.org usertag 778034 + libstdc++-cxx11 usertag 778034 - ftbfs-gcc-5 tags 778034 + confirmed thanks the package builds ok, but introduces new symbols, so it's likely to need a proper library transition. $ objdump -T debian/libogre-1.9.0/usr/lib/x86_64-linux-gnu/libOgre*|grep cxx11 |wc -l 1871 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793669: FTBFS when python 3.5 is supported
Package: pyside Version: 1.2.2-1 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily ubuntu-patch Hiya, In Ubuntu we've added py3.5 as a supported version. This makes python packages build python 3.5 extensions, which contain the multiarch triplet in their filename. https://bugs.python.org/issue22980 For pyside, this means that it can't find the ShibokenConfig cmake file for 3.5. shiboken is a BD of pyside, and after it is rebuilt for 3.5, it produces the files -rw-r--r-- root/root 1317 2015-07-23 17:46 ./usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cpython-34m.cmake -rw-r--r-- root/root 1402 2015-07-23 17:45 ./usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cpython-35m-x86_64-linux-gnu.cmake pyside looks up the cmake file by making use of an unversioned file ShibokenConfig.cmake which uses a user-provided suffix to find ShibokenConfig.cpython-suffix.cmake for the particular python version you're asking for. So either callers need to know that the suffix has to contain the triplet for ≥ 3.5 (the attached patch), or shiboken needs to be fixed somehow - for example by renaming the file back or giving it more smarts to figure it out. Any fix in shiboken probably wants to take care to preserve multiarch compatibility that is improved with this change in 3.5, assuming you care about that. There's not so many reverse-BDs of shiboken though, so it might be easiest to fix them directly. Cheers, Iain diff -Nru pyside-1.2.2/debian/rules pyside-1.2.2/debian/rules --- pyside-1.2.2/debian/rules 2014-04-30 11:54:27.0 +0100 +++ pyside-1.2.2/debian/rules 2015-07-25 17:16:11.0 +0100 @@ -17,6 +17,12 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +# the python version we are being called on atm, in the form 34 (for 3.4) +PYVER=$(subst .,,$*) +# python ≥ 3.5 append the multiarch triplet to module names (in particular this +# is reflected in ShibokenConfig.cmake) +PYMODULESUFFIX=$(if $(shell test $(PYVER) -ge 35 echo yes),-$(DEB_HOST_MULTIARCH),) + ifneq (,$(filter debug,$(DEB_BUILD_OPTIONS))) BD_DEBUG = python-all-dbg (= 2.6.6-3~), python3-all-dbg, shiboken-dbg (= 1.2.2), endif @@ -89,14 +95,14 @@ dh_auto_configure -a --builddirectory=build-$*-dbg -- \ $(CMAKE_COMMON_OPTIONS) \ -DCMAKE_BUILD_TYPE:STRING=Debug \ - -DPYTHON_SUFFIX=.cpython-$(subst .,,$*)dm + -DPYTHON_SUFFIX=.cpython-$(PYVER)dm$(PYMODULESUFFIX) override_dh_auto_configure_3-%: mkdir -p build-$* dh_auto_configure -a --builddirectory=build-$* -- \ $(CMAKE_COMMON_OPTIONS) \ -DCMAKE_BUILD_TYPE:STRING=Release \ - -DPYTHON_SUFFIX=.cpython-$(subst .,,$*)m \ + -DPYTHON_SUFFIX=.cpython-$(PYVER)m$(PYMODULESUFFIX) \ -DDEFAULT_PYTHON_BASENAME=-python${DEFAULT_PY} BUILD
Bug#793676: pike8.0-core: unowned directories in /usr/local after purge (policy 6.8 and 9.1.2): /usr/local/lib/pike8.0/*
Package: pike8.0-core Version: 8.0.28-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails From the attached log (scroll to the bottom...): 0m37.5s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpxwVfk6', 'dpkg', '--purge', 'pike8.0-core'] 0m37.6s DUMP: (Reading database ... 7750 files and directories currently installed.) Removing pike8.0-core (8.0.28-2) ... Purging configuration files for pike8.0-core (8.0.28-2) ... rmdir: failed to remove '/usr/local/lib/pike7.8/modules': No such file or directory rmdir: failed to remove '/usr/local/lib/pike7.8/include': No such file or directory rmdir: failed to remove '/usr/local/lib/pike7.8': No such file or directory 0m37.6s DEBUG: Command ok: ['chroot', '/tmp/piupartss/tmpxwVfk6', 'dpkg', '--purge', 'pike8.0-core'] 0m37.6s INFO: Running scripts post_purge 0m42.3s ERROR: FAIL: Package purging left files on system: /usr/local/lib/pike8.0/not owned /usr/local/lib/pike8.0/include/not owned /usr/local/lib/pike8.0/modules/not owned Leaving directories in /usr/local after purge is also a violation of a should-directive in https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 cheers, Andreas pike8.0-core_8.0.28-2.log.gz Description: application/gzip
Bug#793679: sddm: unowned files after purge (policy 6.8, 10.8): /var/log/sddm.log
Package: sddm Version: 0.11.0-3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 4m43.8s ERROR: FAIL: Package purging left files on system: /etc/systemd/system/display-manager.service - /lib/systemd/system/sddm.servicenot owned /var/log/sddm.log not owned Leaving the dangling display-manager.service symlink seems to be a problem with init-system-helpers since all *dm packages have this problem. Any further analysis would be welcome, though! cheers, Andreas sddm_0.11.0-3.log.gz Description: application/gzip
Bug#686817: grub-pc: Add option to change keyboard layout
In principle, GRUB2 allows you to change the keyboard layout through its 'at_keyboard' input terminal. You can use the 'grub-mklayout' utility to create a GRUB keyboard layout, e.g., for dvorak: ckbcomp dvorak | grub-mklayout -o dvorak.gkb Create a 'layouts' subdirectory under your 'grub' directory, and copy the GRUB keyboard layout to it, e.g.: mkdir /boot/grub/layouts cp dvorak.gkb /boot/grub/layouts The 'keymap' command under GRUB (e.g., in your 'grub.cfg') will then load the keymap: keymap dvorak To actually use the keymap, you will have to switch the the 'at_keyboard' input terminal: terminal_input at_keyboard Trouble is, under a PC BIOS system, the 'at_keyboard' input terminal is broken. It is unclear to me how (or even, whether) it can be fixed. Since I, too, got frustrated that I couldn't change the keyboard layout, I decided to try and create my own 'ext_kbd' input terminal, for personal use. The 'ext_kbd' input terminal implements something akin to the 'setkey' command that was available under what is now known as GRUB Legacy. It won't go into upstream, since it deviates from the infrastructure that GRUB already provides for changing the keyboard layout. In any case, I'll attach a patch that will add support for my 'ext_kbd' module to GRUB, in case anyone is interested enough to try it. If you decide to apply the patch, then you will subsequently have to run './autogen.sh' before you run './configure'. Otherwise, the build process will not pick up the definition of the 'ext_kbd' module that the patch adds to the 'grub-core/Makefile.core.def' file. I'm afraid that this is the best that I can do for now. -- Luc. diff -Naur grub.orig/docs/grub.texi grub/docs/grub.texi --- grub.orig/docs/grub.texi 2015-07-23 12:11:11.0 +0200 +++ grub/docs/grub.texi 2015-07-26 14:10:24.956277000 +0200 @@ -3660,13 +3660,57 @@ Commands usable anywhere in the menu and in the command-line. @menu +* keymap:: Load a keyboard layout * serial:: Set up a serial device +* setkey:: Change the keyboard map +* setnumpad:: Change the numeric keypad behavior * terminal_input:: Manage input terminals * terminal_output:: Manage output terminals * terminfo::Define terminal type @end menu +@node keymap +@subsection keymap + +@deffn Command keymap LAYOUT +Load a keyboard layout. + +If @var{LAYOUT} is just the identifier of a keyboard layout, then GRUB will +look for file @file{$prefix/layouts/@var{LAYOUT}.gkb}. +Alternatively, @var{LAYOUT} may be the full path to a GRUB keyboard layout file. + +This command will have no effect unless and until you use the +@command{terminal_input} command to activate either the @samp{at_keyboard} +input terminal: + +@example +terminal_input at_keyboard +@end example + +or the @samp{usb_keyboard} input terminal: + +@example +terminal_input usb_keyboard +@end example + +@table @asis +@item Creating a GRUB keyboard layout file: + +To generate a GRUB keyboard layout file, you can use the @command{grub-mklayout} +command-line utility, which takes a Linux console keyboard layout description +as input, and converts it to a format that GRUB can understand. + +For instance, if you use the @samp{dvorak} keyboard layout, then the following +command will create the @file{dvorak.gkb} file for use with GRUB: + +@example +ckbcomp dvorak | grub-mklayout -o dvorak.gkb +@end example +@end table +@end deffn + + @node serial @subsection serial @@ -3689,6 +3733,112 @@ @end deffn +@node setkey +@subsection setkey + +@deffn Command setkey [[TO_KEY] FROM_KEY] +Change the keyboard map. + +With no arguments, reset the keyboard map to its default U.S. layout. + +When only the @var{FROM_KEY} argument is given, or when @var{TO_KEY} is equal to +@var{FROM_KEY}, the mapping entry for the specified key will be cleared. +Keep in mind that @var{FROM_KEY} identifies the position of the key under the default +U.S. layout. + +With two unequal arguments, the key @var{FROM_KEY} will be mapped to @var{TO_KEY}. +In effect, the @var{FROM_KEY} argument identifies the position of the key under the +default U.S. layout, and @var{TO_KEY} specifies how the key should behave under your +local keyboard layout. + +A key must be: +@itemize @bullet +@item +a lowercase letter; +@item +an uppercase letter; +@item +a decimal digit; +@item +a function key---i.e., @kbd{F1} through @kbd{F12}; +@end itemize + +or one of the following: + +@verbatim + ampersandbarx delete less question + asterisk braceleftdollar minusquote + at braceright doublequote numbersign semicolon + backslashbracketleft enterparenleftslash + backslashx bracketright equalparenright space + backquotecaretescape percent tab + backspacecolonexclam period
Bug#785057: wiki.debian.org: unblock IPredator VPN
ilf: I've just hit this again, this time using Tor with exit node 198.50.128.236: https://atlas.torproject.org/#details/6546C565A53F09673F2D4BDF12AAE25551D79EC2 And another Tor exit node banned: 5.39.94.152 https://atlas.torproject.org/#details/7EA3162354CA86E1AE3CDDF35BCCBFC2F5265500 -- ilf Über 80 Millionen Deutsche benutzen keine Konsole. Klick dich nicht weg! -- Eine Initiative des Bundesamtes für Tastaturbenutzung signature.asc Description: Digital signature
Bug#793376: su-to-root: higher priority for kdesudo and gksudo
On Sat, Jul 25, 2015 at 12:28:20AM +, Patrick Schleizer wrote: %sudo -n true sudo: sorry, a password is required to run sudo But it does not block? It's non-interactive? It exits with error 1, so the test fails. If yes, then that's supposed to be that way. It's used as test to figure out whether the user is allowed to use sudo [and by extension, kdesudo] or not. In my case, the user is allowed to use sudo bu they need to enter their password, something kdesudo/gksudo can do of course, but the test fails. I suggest you try it yourself. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712938: No change?
Sorry, both are dead: qt4 and that patch. I can't understand your arguments, why can't you include that patch into qt4? I don't even mean sni-qt, but please apply patch that will make possible to use sni-qt. Most of people are able to compile sni-qt by theirself (or risk and install ubuntu deb). This patch is quite small and should not break stability. I understand you principles, but this case is huge usability issue. Too huge to be able to be accepted. On Sun, 26 Jul 2015 10:52:13 -0300 Lisandro =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer wrote: On Sunday 26 July 2015 12:42:56 MichaŠMilanowski wrote: Can't any debian dev see his stupidity regarding to this issue? There are tons of qt4 apps that are widely used and will be probably never ported to qt5, like Skype for example, but many others too. Hi! I'm the Qt maintainer, and yes, I understand your arguments, but again: do you really want to push dead-upstream code and support it trough the whole life of Stretch? I don't. You decided to drop support for them just like that (90% actually used linux apps) and you are providing the only solution Port your app to qt5. Or someone to step up and become a sni-qt upstream, fix it's bugs and we can reconsider. All workarounds decrived here look like a joke, not real solution. Yes, sadly they failed to me too :( Ubuntu provided this patch, Arch provided too. Every known distro has workaround built in by patching qt to make their users live easier. But not Debian. For the reasons I have already stated. Shame and f you (sorry!). That was definitely too much. Please refrain from that kind of comments in the future. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#793687: rsnapshot incorrectly handles quotes in per-backup rsync_long_args option
Package: rsnapshot Version: 1.3.1-4 Severity: normal Hi. rsnapshot from Jessie incorrectly handles quotes in per-backup '+rsync_long_args' option (in wheezy it works fine) - it does not remove them. Though, quotes are required, if e.g. i want to add per-backup '--filter' option. How to reproduce: 1. Build.. $ git checkout debian/1.3.1-4 Previous HEAD position was 773afb8... Enable GNU cp and document stop_on_stale_lockfile option HEAD is now at 324f3d7... Bump to Standards-Version 3.9.4, change Vcs-{Git,Browse} and avoid rsnapshot-HOWTO.en.html duplication $ quilt push -a Applying patch debian/patches/01_rsnapshot_conf.diff patching file rsnapshot.conf.default.in patching file rsnapshot-program.pl patching file rsnapshot-program.pl Applying patch debian/patches/03_pod_missing_back.diff patching file rsnapshot-program.pl Applying patch debian/patches/05_backup_pgsql.diff patching file utils/backup_pgsql.sh Applying patch debian/patches/06_fix_random_file_verify.diff patching file utils/random_file_verify.sh Applying patch debian/patches/08_manpage_hourly_to_daily.diff patching file rsnapshot-program.pl Applying patch debian/patches/09_strip_backtick.diff patching file rsnapshot-program.pl Applying patch debian/patches/10_space_destdir.diff patching file rsnapshot-program.pl Applying patch debian/patches/11_lvm_snapshots.diff patching file rsnapshot.conf.default.in Hunk #2 succeeded at 202 (offset 6 lines). Hunk #3 succeeded at 235 (offset 6 lines). patching file configure.ac Applying patch debian/patches/12_include_conf_with_arguments.diff patching file rsnapshot-program.pl Applying patch debian/patches/13_print_warn.diff patching file rsnapshot-program.pl Now at patch debian/patches/13_print_warn.diff $ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking for perl... /usr/bin/perl checking for rsync... /usr/bin/rsync checking for cp... /bin/cp checking for rm... /bin/rm checking for ssh... /usr/bin/ssh checking for logger... /usr/bin/logger checking for du... /usr/bin/du configure: creating ./config.status config.status: creating Makefile config.status: creating rsnapshot config.status: creating rsnapshot-diff config.status: creating rsnapshot.conf.default config.status: creating t/support/etc/configtest.conf config.status: creating t/support/etc/rsync.conf config.status: creating t/support/etc/gnu_cp.conf config.status: creating t/support/etc/relative_delete_bugfix.conf config.status: creating t/configtest.t config.status: creating t/rsync.t config.status: creating t/gnu_cp.t config.status: creating t/relative_delete_bugfix.t Now type make testto run the regression test suite. Then type make install to install the program. After rsnapshot is installed, don't forget to copy /usr/local/etc/rsnapshot.conf.default to /usr/local/etc/rsnapshot.conf $ make cd . /bin/bash /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing --run aclocal-1.9 /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing: line 52: aclocal-1.9: command not found WARNING: `aclocal-1.9' is missing on your system. You should only need it if you modified `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd . /bin/bash /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing --run automake-1.9 --gnu /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing: line 52: automake-1.9: command not found WARNING: `automake-1.9' is missing on your system. You should only need it if you modified `Makefile.am', `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd . /bin/bash /home/sgf/Documents/rsnapshot/src/3rd/t/rsnapshot/missing --run autoconf /bin/bash ./config.status --recheck running /bin/bash ./configure --no-create --no-recursion checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for perl... /usr/bin/perl checking for rsync... /usr/bin/rsync checking for cp... /bin/cp checking for rm... /bin/rm checking for ssh... /usr/bin/ssh checking for lvcreate... no checking for lvremove... no