Bug#795474: hydrogen: please install SVG icon to correct location
Package: hydrogen Version: 0.9.6.1-1 Severity: minor Tags: patch The hydrogen icon looks very blurry on desktops with large icons (e.g. GNOME). I noticed that there is an SVG icon in the hydrogen package but it is not installed to the correct location. This can be fixed with a tiny change to the debian links file (see attached patch). This adds a symlink to the installed icon at the correct location. Now the hydrogen icon looks very clear also in GNOME. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.1.0-trunk-686-pae (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hydrogen depends on: ii libarchive13 3.1.2-11 ii libasound21.0.28-1 ii libc6 2.19-18 ii libgcc1 1:4.9.2-10 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libportaudio2 19+svn20140130-1 ii libportmidi0 1:184-2.2 ii libpulse0 5.0-13 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-xmlpatterns4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii librubberband21.8.1-6 ii libsndfile1 1.0.25-9.1 ii libstdc++64.9.2-10 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages hydrogen recommends: ii hydrogen-drumkits 0.9.3.20070703-3 pn rubberband-cli none hydrogen suggests no packages. -- no debconf information --- hydrogen-0.9.6.1_orig/debian/links 2014-10-21 13:56:30.0 +0200 +++ hydrogen-0.9.6.1/debian/links 2015-08-14 12:11:37.822946809 +0200 @@ -1 +1,2 @@ usr/share/hydrogen/data/demo_songs usr/share/doc/hydrogen/examples/demo_songs +usr/share/hydrogen/data/img/gray/h2-icon.svg usr/share/icons/hicolor/scalable/apps/h2-icon.svg
Bug#795060: Latest Wheezy backport kernel prefers Infiniband mlx4_en over mlx4_ib, breaks existing installs
On Fri, 2015-08-14 at 13:45 +0900, Christian Balzer wrote: [...] So I decided to downgrade the Mellanox firmware of mbx09. After building a current version of mstflint (the one in Wheezy is ancient and not particular justified) I got the oldest firmware (2.32.5100) on the Supermicro FTP site for that mainboard and flashed it. Lo and behold, no more vanishing acts of the ib0: interface, no more need to blacklist/fake install the mlx4_en module. While moderately happy with the outcome, I still consider this a kernel bug. All the described behavior is not only very unexpected and unwelcome, the fact that a remote card reboot can make your network stack vanish (and not re-appear unless done manually) is just wrong. [...] This sounds rather more like a firmware bug than a kernel bug. Please ask Mellanox technical support about this. If they can identify a fix in the driver then I'll be happy to apply that. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#795471: kdegames: no possibility to launch kdegames
On Friday 14 August 2015 12:27:37 Pascal Raton wrote: *** 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 *** Well, that was an informative bug report... It's likely caused by bug #794419 and adding '/usr/games/' back onto your $PATH will probably fix it. signature.asc Description: This is a digitally signed message part.
Bug#791456: obfs4proxy: Unable to install/configure obfs4proxy
Control: reassign -1 adequate Control: forcemerge 762615 -1 Control: notfound -1 obfs4proxy/0.0.5-2 Control: affects -1 + obfs4proxy Hi, shirish शिरीष wrote (05 Jul 2015 04:54:38 GMT) : ─[$] sudo aptitude install obfs4proxy=0.0.5-2 [...] ldd -r: failed at /usr/bin/adequate line 813, $ldd line 4. E: Problem executing scripts DPkg::Post-Invoke 'adequate --help /dev/null 21 || exit 0; DEBIAN_FRONTEND=readline exec adequate --debconf --user nobody --pending' In a clean Jessie pbuilder chroot, I could successfully install obfs4proxy (with both `apt' and `aptitude', in both cases with adequate already installed on the system), and then: # ldd -r /usr/bin/obfs4proxy linux-gate.so.1 (0xf77c) libpthread.so.0 = /lib/i386-linux-gnu/libpthread.so.0 (0xf779e000) libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xf762d000) /lib/ld-linux.so.2 (0x565e6000) # adequate obfs4proxy ldd -r: failed at /usr/bin/adequate line 812, $ldd line 4. # echo $? 1 This looks like the bug #762615 (in adequate), that was fixed in testing/sid already, and is itself caused by a bug in ldd (#710521) = merging and reassigning accordingly. Cheers, -- intrigeri
Bug#795475: Make the tor AppArmor abstraction extensible by other packages
Package: tor Version: 0.2.6.10-1 Severity: wishlist Owner: intrig...@debian.org X-Debbugs-Cc: lu...@debian.org Hi, a common source of problems with little-t-tor's AppArmor confinement has been the hard-coded list of pluggable transports in /etc/apparmor.d/abstractions/tor: whenever someone creates a new PT implementation and people start using it, the tor service fails to start on AppArmor-enabled systems until 1. we add that new PT to the tor AppArmor abstraction; and 2. end-users upgrade their tor package to a version that contains the update. I remember seeing too many bug reports filed on the Tor bug tracker (mostly by Ubuntu users) about it: they install whatever PT is currently best for their use case from deb.torproject.org, but they still have a tor package from some stable Debian or derivative distro that hasn't seen the (1) update yet. Fixing this would improve UX and lower our maintenance workload. To fix this, I propose that we: a) add #include tor.d to abstractions/tor b) move each already present PT-related rules from abstractions/tor to abstractions/tor.d/PT, that would be shipped in the corresponding PT package. I'm willing to implement this (with low/moderate priority) and submit patches to the tor, obfsproxy and obfs4proxy packages. Sounds good? Any foreseeable issue with it? Better ideas? Cheers, -- intrigeri
Bug#795476: icedove: Can NOT retreive messages from a server with self-signed certificate
Package: icedove Version: 31.8.0-1~deb7u1 Severity: normal Dear Maintainer, * What led up to the situation? Since 2018-August-13th my Icedove don't retreive new messages... I think it's due to self-signed certificate (I use to work with security login ON: ports 995, etc.). SMTP is still OK at port 465. * What exactly did you do (or not do) that was effective (or ineffective)? - Disabling security (using port 110), I can retreive my mail OK. - Config change from here: https://wiki.debian.org/Icedove#Iceowl- extension_does_not_remember_credentials is NOT effective -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.3.2 ii fontconfig2.9.0-7.1 ii libasound21.0.25-4 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38+deb7u8 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1+deb7u6 ii libdbus-glib-1-2 0.100.2-1 ii libevent-2.0-52.0.19-stable-3+deb7u1 ii libffi5 3.0.10-3 ii libfontconfig12.9.0-7.1 ii libfreetype6 2.4.9-1.1+deb7u1 ii libgcc1 1:4.7.2-5 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libhunspell-1.3-0 1.3.2-4 ii libpango1.0-0 1.30.0-1 ii libpixman-1-0 0.26.0-4+deb7u1 ii libsqlite3-0 3.7.13-1+deb7u2 ii libstartup-notification0 0.12-1 ii libstdc++64.7.2-5 ii libx11-6 2:1.5.0-1+deb7u2 ii libxext6 2:1.3.1-2+deb7u1 ii libxrender1 1:0.9.7-1+deb7u2 ii libxt61:1.1.3-1+deb7u1 ii psmisc22.19-1+deb7u1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages icedove recommends: ii hunspell-en-us [hunspell-dictionary] 20070829-6 ii myspell-ca [myspell-dictionary] 0.20111230b-4 ii myspell-es [myspell-dictionary] 1.11-4 Versions of packages icedove suggests: ii fonts-lyx 2.0.3-3 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3 -- no debconf information
Bug#755989: german cfdisk manpage problems, reassigning to manpages-de
Control: reassign -1 manpages-de Hello. Since the german cfdisk manpage is shipped in the manpages-de package I'm reassigning this bug report to that package. Hopefully this issue is already fixed and this bug report can just be closed but I'll let someone with german knowledge verify this Regards, Andreas Henriksson
Bug#795479: autoconf-archive: AX_CHECK_GLU trashes the LIBS variable
Package: autoconf-archive Version: 20150224-2.1 Severity: normal Tags: patch Hi, There is a typo in m4/ax_check_glu.m4 and m4/ax_check_glx.m4 which causes the LIBS (and some other) variables to be trashed. This contributed to the FTBFS in #791540. I've attached a patch which fixes this for me (and fixes the FTBFS in the other bug). Thanks, James -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, '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 autoconf-archive depends on: ii dpkg 1.18.2 Versions of packages autoconf-archive recommends: ii autoconf 2.69-8 autoconf-archive suggests no packages. -- no debconf informationdiff -u -r a/m4/ax_check_glu.m4 b/m4/ax_check_glu.m4 --- a/m4/ax_check_glu.m4 2015-02-23 23:00:00.0 + +++ b/m4/ax_check_glu.m4 2015-08-14 12:18:29.064421280 +0100 @@ -316,7 +316,7 @@ [ax_check_glu_have_headers=yes;break], [ax_check_glu_have_headers_headers=no], [_AX_CHECK_GLU_INCLUDES_DEFAULT()]) -_AX_CHECK_GL_RESTORE_FLAGS() +_AX_CHECK_GLU_RESTORE_FLAGS() AC_LANG_POP([C]) AC_CACHE_CHECK([for OpenGL Utility (GLU) headers],[ax_cv_check_glu_have_headers], [ax_cv_check_glu_have_headers=${ax_check_glu_have_headers}]) diff -u -r a/m4/ax_check_glx.m4 b/m4/ax_check_glx.m4 --- a/m4/ax_check_glx.m4 2015-02-23 23:00:00.0 + +++ b/m4/ax_check_glx.m4 2015-08-14 12:18:48.260513289 +0100 @@ -259,7 +259,7 @@ [ax_check_glx_have_headers=yes;break], [ax_check_glx_have_headers_headers=no], [_AX_CHECK_GLX_INCLUDES_DEFAULT()]) -_AX_CHECK_GL_RESTORE_FLAGS() +_AX_CHECK_GLX_RESTORE_FLAGS() AC_LANG_POP([C]) AC_CACHE_CHECK([for OpenGL Utility (GLX) headers],[ax_cv_check_glx_have_headers], [ax_cv_check_glx_have_headers=${ax_check_glx_have_headers}]) signature.asc Description: This is a digitally signed message part
Bug#795478: src:angband: use autotools-dev to fix FTBFS on ppc64el
Package: src:angband Version: 1:3.5.1-2 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Really use autotools-dev. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2015-08-14 12:08:12.977386255 +0200 +++ b/debian/rules 2015-08-14 12:09:08.977383279 +0200 @@ -23,7 +23,7 @@ include /usr/share/dpkg/buildflags.mk %: - dh $@ + dh $@ --with autotools_dev override_dh_auto_clean:
Bug#791019: cxxtools library transition needed, patch attached
On Mon, 20 Jul 2015 at 22:54:13 +0300, Kari Pahula wrote: Cxxtools uses std::string as a part of its API, which causes Cxxtools to expose libstdc++ via its ABI. Patch attached for a 9v5 version. cxxtools does not appear to build-depend on anything lower down the libstdc++ transition stack, and the maintainer (cc'd here) has provided a patch. Release team: is this ready for a maintainer upload to unstable? S
Bug#795361: [Pkg-mozext-maintainers] Bug#795361: Info received (Bug#795361: Acknowledgement (xul-ext-tabmixplus: Quiting and searching fail to work with iceweasel from security.debian.org))
Control: severity -1 serious Hi, Le 13/08/2015 14:49, Helge Kreutzmann a écrit : Could you provide a backport and forward the current version to the next point release? Sure, thank you for your report and your investigations. Bumping the severity since these regressions break significantly a normal workflow. Regards David signature.asc Description: OpenPGP digital signature
Bug#747927: qemu-utils: qemu-nbd blocks
Package: linux-image Version: 3.16.0-4-amd64 Control: found 747927 linux/3.16.0-4
Bug#632401: Raid with MDAM
I similar problem and this post solves it: http://serverfault.com/questions/688207/how-to-auto-start-degraded-software-raid1-under-debian-8-0-0-on-boot
Bug#792002: lvm2-monitor service causes long delay at boot (encrypted root/swap)
* On Fri, Aug 07, 2015 12:08PM +0200 I wrote: Package: lvm2 Version: 2.02.126-2 Followup-For: Bug #792002 I found that changing ExecStart=/sbin/lvm vgchange --monitor y --ignoreskippedcluster to ExecStart=/sbin/lvm vgchange --activate y --monitor y --ignoreskippedcluster The problem seems to have resolved with the latest unstable version (2.02.126-3). Thanks, Michael -- PGP-Key-ID: EEE7D043 Jabber: in...@jabber.de
Bug#795457: audit: CVE-2015-5186: log terminal emulator escape sequences handling
Source: audit Version: 1:2.4.2-1 Severity: important Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for audit. CVE-2015-5186[0]: log terminal emulator escape sequences handling If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-5186 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1251621 [2] https://fedorahosted.org/audit/changeset/1122 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#410695: zope2.7 causqe upgrade failure
Hi, On Thu, Aug 13, 2015 at 02:22:41PM +0200, Bill Allombert wrote: Nevertheless, please always CC the original submitter when replyng or closing bug reports, otherwise they do not get your email. Mhhh, my interpretation of the documentation is different: | The person closing the bug, the person who submitted it and the | debian-bugs-closed mailing list will each get a notification about the | change in status of the report. The submitter and the mailing list | will also receive the contents of the message sent to nnn-done. Source: https://www.debian.org/Bugs/Developer#closing Sounds for me like the submitter gets a mail automatically… Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#795380: krb5-config: default krb5.conf has other people's domains
Sure. Whatever. Feel free to close the ticket.
Bug#795424: virtualbox-guest-x11: KDM causes vboxvideo driver to crash on assertion at login time.
Control: tags -1 pending Hi David I'm submitting this for 4.3.30-dfsg-1, but 5.0.0-dfsg-1 is also affected. KDM (at least) uses the generations extension in the XServer to avoid reloading it. This triggers an assertion in the vboxvideo driver causing a black screen usually right after login. There's a patch fixing this (and more information that I requested) at https://www.virtualbox.org/ticket/14341. I'll cherry-pick it and add it to the 4.3.x branch. Additionally, virtualbox 4.3 cannot be compiled with gcc-5.2, the default in unstable right now. :-) thanks for the bug report, however I just packaged 5.0.2 on git, that contains this fix (and wrote a gcc-5.2 patch) Ritesh, how do you feel about going for unstable? Cheers, Gianfranco
Bug#778981:
HI Adnan, On 14 August 2015 at 06:43, Adnan Hodzic ad...@hodzic.org wrote: Hi Felipe, I have the same problem. My wireless headphones aren't detected by bluetooth. Apparently, running pactl load-module module-bluetooth-discover fixes the problem for a lot of people. But in my case this command just returns: Failure: Module initialization failed. This seems to happen because your device is correctly detected: ( 0.143| 0.000) D: [pulseaudio] bluez5-util.c: Device /org/bluez/hci0/dev_6C_2F_F5_2B_19_66 found ( 0.143| 0.000) D: [pulseaudio] bluez5-util.c: Address: 6C:2F:F5:2B:19:66 ( 0.143| 0.000) D: [pulseaudio] bluez5-util.c: Alias: 6C-2F-F5-2B-19-66 ( 0.143| 0.000) D: [pulseaudio] bluez5-util.c: Adapter: /org/bluez/hci0 ( 0.143| 0.000) D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Properties found, skipping ( 0.143| 0.000) D: [pulseaudio] backend-native.c: Bluetooth Headset Backend API support using the native backend ( 0.143| 0.000) D: [pulseaudio] backend-native.c: Registering Profile /Profile/HSPAGProfile ... ( 1.629| 0.000) E: [pulseaudio] module.c: Module module-bluetooth-discover should be loaded once at most. Refusing to load. ( 1.629| 0.000) I: [pulseaudio] client.c: Freed 1 pactl You can't have bluetooth loaded twice. But in your log it seems your wireless headset is not getting detected. I fear your problem is on the bluetooth side, not pulse. Please try checking if your device is really connected using bluetoothctl (use the devices command to list known devices, and the info command to show the status information for that device. -- Saludos, Felipe Sateler
Bug#795404: cups-backend-bjnp: stops printing after some lines
severity 795404 important thanks Hello Björn. Thank you for your report. I think it is reasonable to assume that having printed on one occasion you will be able to do it again. Hence reducing severity. On Thu 13 Aug 2015 at 19:48:29 +0200, Björn Siebke wrote: * What led up to the situation? Yesterday I newly installed my Canon Pixma MG6650 - it worked. I successfully printed some pages. Today, after having changed nothing, I tried it again. * What exactly did you do (or not do) that was effective (or ineffective)? Clicked on print in LOWriter. Rather than having to take into account what an application does I'd do test printing with a small text file or PDF using the lp command. * What was the outcome of this action? The printer started with the first lines of the document and then stopped. The printer's display showed a printing process going on. The queue told me there was no connection (printer connected?). I used the troubleshooting dialogue (protocol attached). Even though it looks like the printer was found 'device-id': 'MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:BJNP2,BJNPe;MDL:MG6600 series;CLS:PRINTER;DES:Canon MG6600 series;VER:3.010;STA:10;FSI:00;HRI:D;MSI:AOFF,B015,DAT,E3,HFSF,JOFF,K21000700,LOFF;PDR:4;PSE:ADMM96370;CID:CA_IVEC1TYPE4_IJP;', 'device-info': 'Canon MG6600 series db-printer.fritz.box', 'device-make-and-model': 'Canon MG6600 series'}} and there was some printing it wouldn't do any harm to look at the network setup first. Switching db-printer.fritz.box and the printer off for a few minutes before reconnecting the power is worth a go. You could also consider using a fixed address and putting it in the device-uri when the queue is created. Pinging the server while printing would test it doesn't disappear. The message 'printer-state-message': uNetwork host 'db-printer.fritz.box' is busy; will retry in 15 seconds..., comes from the bjnp backend. Let's see how you go with that before we move on to other things. Regards, Brian.
Bug#795485: librostlab-blast: please make the build reproducible
Source: librostlab-blast Version: 1.0.1-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that librostlab-blast could not be built reproducibly. The attached patch removes timestamps from the documentation. Once applied, librostlab-blast can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/lib/Doxyfile.in b/lib/Doxyfile.in index a7619f7..938fa93 100644 --- a/lib/Doxyfile.in +++ b/lib/Doxyfile.in @@ -838,7 +838,7 @@ HTML_COLORSTYLE_GAMMA = 80 # page will contain the date and time when the page was generated. Setting # this to NO can help when comparing the output of multiple runs. -HTML_TIMESTAMP = YES +HTML_TIMESTAMP = NO # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, # files or namespaces will be aligned in HTML using tables. If set to
Bug#793745: I have solved...
I have the same bug. I have resolved with these commands: mkdir /home/ntp chown -R ntp:ntp /home/ntp Now my ntp start properly... Thank you to all the debian community... Best regards Mirko signature.asc Description: OpenPGP digital signature
Bug#795468: Files not printable if they have german umlauts (latin1) in name
Hello Klaus. Thank you for your report. On Fri 14 Aug 2015 at 10:19:10 +0100, Klaus Ethgen wrote: I have pdf files which have german umlauts in name. If I try to print them, I get the error lp: Error - unable to access ... - Datei oder Verzeichnis nicht gefunden My filesystem is, as all of my system, proper encoded with ISO-8859-1. I believe, that lp is doing wrong character encoding internally for no need. Please change it to use the name, the user is giving on the command line and not some interpreted one. Isn't this the same as #623269? Regards, Brian.
Bug#779406: replace gift usertag with newcomer
On Thu, 13 Aug 2015, Christophe Siraut wrote: Please pull 7b3d5e7. Please attach patches for easy review and comments. The newcomer is a first-class tag, not a usertag, so you should not only s/gift/newcomer/ but also adjust for this difference: index 96ad6d7..5a00276 100644 --- a/distro_tracker/vendor/debian/rules.py +++ b/distro_tracker/vendor/debian/rules.py @@ -385,9 +385,9 @@ def get_bug_tracker_url(package_name, package_type, category_name): ('pend-exc', 'fixed'), ('pend-exc', 'done'), ), -'gift': ( +'newcomer': ( ('users', 'debian...@lists.debian.org'), -('tag', 'gift'), +('tag', 'newcomer'), Here, handle it like the help tag except s/help/newcomer/. li class=list-group-item div class=list-item-key -{% if category.display_name == gift %} +{% if category.display_name == newcomer %} a href=https://wiki.debian.org/qa.debian.org/GiftTag; {% endif %} bspan class=has-tooltip data-title={{ category.description }} data-toggle=tooltip{{ category.display_name }}:/span/b -{% if category.display_name == gift %} +{% if category.display_name == newcomer %} /a {% endif %} /div Not your fault, but here the category link should come from the data (category.link ?) and not be hardcoded like this. diff --git a/distro_tracker/vendor/debian/tracker_tasks.py b/distro_tracker/vendor/debian/tracker_tasks.py index 59b3878..4a078b1 100644 --- a/distro_tracker/vendor/debian/tracker_tasks.py +++ b/distro_tracker/vendor/debian/tracker_tasks.py @@ -470,13 +470,14 @@ class UpdatePackageBugStats(BaseTask): except: logger.exception(Could not get bugs tagged help) -# Add in gift bugs from the BTS SOAP interface +# Add in newcomer bugs from the BTS SOAP interface try: -gift_bugs = self._get_tagged_bug_stats('gift', - 'debian...@lists.debian.org') -self._extend_bug_stats(bug_stats, gift_bugs, 'gift') +newcomer_bugs = self._get_tagged_bug_stats( +'newcomer', +'debian...@lists.debian.org') +self._extend_bug_stats(bug_stats, newcomer_bugs, 'newcomer') Here again you should adjust by dropping the second parameter to self._get_tagged_bug_stats() Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Bug#795380: krb5-config: default krb5.conf has other people's domains
I'm sorry. I'm still not seeing a harm here. I absolutely agree that setting a default realm to something unexpected would be problematic. However simply having a realm listed in krb5.conf doesn't have any affect unless you try to use that realm. It's not like settind the default URI for ldapsearch or adding relay configuration to main.cf. what it means is that if you try to use that realm (and the information is correct) then it will work. I'll definitely remove the cruft, because you're right that krb5-config has bitrotted a bit. However, I consider making it so that using a particular kerberos realm will *work* if a user tries to do that consistent with the principle of least surprise. If something is causing a Kerberos realm to get used unintentionally as a result of this, I'd consider that a bug, although I'd suspect it would probably not be a bug in krb5-config.
Bug#793745: Fwd: I have solved...
Ooops... I have found that resetting my config file with dpkg file solve the problem not the home dir of ntp. Sorry. Mirko Messaggio Inoltrato Oggetto:I have solved... Data: Fri, 14 Aug 2015 15:34:49 +0200 Mittente: Mirko panc...@gmail.com A: 793...@bugs.debian.org I have the same bug. I have resolved with these commands: mkdir /home/ntp chown -R ntp:ntp /home/ntp Now my ntp start properly... Thank you to all the debian community... Best regards Mirko signature.asc Description: OpenPGP digital signature
Bug#795484: ruby-rmagick: please make the build reproducible
Source: ruby-rmagick Version: 2.13.2-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that ruby-rmagick could not be built reproducibly. This is due to: - Inherent randomness in some of the documentation images. For example, using fractals and/or random noise. - Examples using timestamps as image captions. In order to fix the former, I needed to expose ImageMagick's SeedPseudoRandomGenerator method via the RMagick interface itself and then ensure it is called in the right documentation fragments. To fix the later, I simply hardcoded the image captions. Patch attached. Once applied, ruby-rmagick can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/doc/ex/add_noise.rb b/doc/ex/add_noise.rb index 4756efe..1fff60d 100644 --- a/doc/ex/add_noise.rb +++ b/doc/ex/add_noise.rb @@ -1,5 +1,6 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 # Demonstrate the Image#add_noise method NOISE_TYPES = [Magick::UniformNoise, Magick::GaussianNoise, diff --git a/doc/ex/enhance.rb b/doc/ex/enhance.rb index fd76795..e9daac3 100644 --- a/doc/ex/enhance.rb +++ b/doc/ex/enhance.rb @@ -1,5 +1,6 @@ #!/usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 # Demonstrate the Image#enhance method diff --git a/doc/ex/matte_fill_to_border.rb b/doc/ex/matte_fill_to_border.rb index 3ae1a15..05a2412 100644 --- a/doc/ex/matte_fill_to_border.rb +++ b/doc/ex/matte_fill_to_border.rb @@ -1,6 +1,7 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 img = Magick::Image.new(200,200) img.compression = Magick::LZWCompression diff --git a/doc/ex/matte_floodfill.rb b/doc/ex/matte_floodfill.rb index e528d11..b101024 100644 --- a/doc/ex/matte_floodfill.rb +++ b/doc/ex/matte_floodfill.rb @@ -1,6 +1,7 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 img = Magick::Image.new(200,200) img.compression = Magick::LZWCompression diff --git a/doc/ex/matte_replace.rb b/doc/ex/matte_replace.rb index fa047cd..655bd0f 100644 --- a/doc/ex/matte_replace.rb +++ b/doc/ex/matte_replace.rb @@ -1,6 +1,7 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 img = Magick::Image.new(200,200) img.compression = Magick::LZWCompression diff --git a/doc/ex/median_filter.rb b/doc/ex/median_filter.rb index 70dc899..7202b4e 100644 --- a/doc/ex/median_filter.rb +++ b/doc/ex/median_filter.rb @@ -1,5 +1,6 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 # Demonstrate the Image#median_filter method diff --git a/doc/ex/polaroid.rb b/doc/ex/polaroid.rb index 026af47..23f3ebc 100644 --- a/doc/ex/polaroid.rb +++ b/doc/ex/polaroid.rb @@ -5,7 +5,7 @@ require 'date' # Demonstrate the Image#polaroid method img = Magick::Image.read('images/Flower_Hat.jpg').first -img[:Caption] = \nLosha\n + Date.today.to_s +img[:Caption] = \nLosha\nPlus hat begin picture = img.polaroid do diff --git a/doc/ex/reduce_noise.rb b/doc/ex/reduce_noise.rb index 05615e4..b139c2d 100644 --- a/doc/ex/reduce_noise.rb +++ b/doc/ex/reduce_noise.rb @@ -1,5 +1,6 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 # Demonstrate the Image#reduce_noise method diff --git a/doc/ex/sketch.rb b/doc/ex/sketch.rb index f4e7eda..f263c86 100644 --- a/doc/ex/sketch.rb +++ b/doc/ex/sketch.rb @@ -1,6 +1,7 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 img = Magick::Image.read('images/Flower_Hat.jpg').first diff --git a/doc/ex/spread.rb b/doc/ex/spread.rb index 7bf9d96..fd4d86d 100644 --- a/doc/ex/spread.rb +++ b/doc/ex/spread.rb @@ -1,5 +1,6 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 # Demonstrate the Image#spread method diff --git a/doc/ex/transparent.rb b/doc/ex/transparent.rb index 3280021..8fdc887 100644 --- a/doc/ex/transparent.rb +++ b/doc/ex/transparent.rb @@ -1,5 +1,6 @@ #! /usr/local/bin/ruby -w require 'RMagick' +Magick::seed_pseudo_random_generator 0 # Demonstrate the Image#transparent method. # Change all black pixels in the image to transparent. diff --git a/ext/RMagick/rmagick.c b/ext/RMagick/rmagick.c index 661f95f..5c81108 100644 --- a/ext/RMagick/rmagick.c +++ b/ext/RMagick/rmagick.c @@ -392,3 +392,24 @@ Magick_set_log_format(VALUE class, VALUE format) return class; } + +/** + * Sets the pseudo-random number generator secret key + * + * Ruby usage: + * - @verbatim Magick.seed_pseudo_random_generator(seed) @endverbatim + * + *
Bug#791540: FTBFS: undefined reference to symbol 'SDL_UnlockSurface'
Hi, On Fri, Aug 14, 2015 at 01:46:06PM +0100, James Cowgill wrote: This was intriguing me so I had a bit of a look at it :) Cool! However, autoconf-archive also has a (different) implementation of AX_CHECK_GLU which gets used instead if the package is installed. This version has a bug in it which trashes the LIBS variable (#795479) where -lSDL had already been specified. Indeed, installing autoconf-archive triggers the FTBFS for me. -C_DEFUN([AX_CHECK_GLU], +AC_DEFUN([AX_CHECK_GLU], Looks sane, I'd upload that to unstable if noone objects in the next days. Thanks a lot for your debugging! Evgeni -- Bruce Schneier can read and understand Perl programs.
Bug#795462: ogre-1.9: please make the build reproducible
2015-08-14 9:12 GMT+01:00 Chris Lamb la...@debian.org: Source: ogre-1.9 Version: 1.9.0+dfsg1-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that ogre-1.9 could not be built reproducibly. The attached patch removes timestamps from the documentation system. Once applied, ogre-1.9 can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Thanks. I uploaded yesterday new versions for the GCC-5 transition, so it is a bit early to upload yet another one now, but I will apply this in the near future once the transitions are over. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com
Bug#795458: dahdi-linux: have debian/README.source
Package: dahdi-linux Severity: wishlist - Forwarded message from Debian testing autoremoval watch nore...@release.debian.org - Date: Fri, 14 Aug 2015 04:39:14 + From: Debian testing autoremoval watch nore...@release.debian.org To: dahdi-li...@packages.debian.org Subject: dahdi-linux is marked for autoremoval from testing dahdi-linux 1:2.10.0.1~dfsg-1 is marked for autoremoval from testing on 2015-09-14 It is affected by these RC bugs: 794313: dahdi-source: dahdi: DAHDI-modules build fails ___ Pkg-voip-maintainers mailing list pkg-voip-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-voip-maintainers - End forwarded message - Neither https://buildd.debian.org/status/logs.php?pkg=dahdi-source nor https://buildd.debian.org/status/logs.php?pkg=dahdi-linux did show ( 2015-08-14 07:40 UTC ( 09:40 CEST)) any logs. Doing `debcheckout dahdi-linux` got me the dahdi source plus debian directory. But what to do after that? Please provide a debian/README.source that tells how to build the dahdi-linux package Cheers Geert Stappers
Bug#765724: git-buildpackage: patch to relax syntax to accept pbuilder syntax
Hi Russ, On Sat, Oct 18, 2014 at 12:02:48AM +0900, Osamu Aoki wrote: Package: git-buildpackage Version: 0.6.19 Severity: wishlist Tags: patch pbuilder and cowbuilder accept first option with -- or without --. (with -- as the main syntax in manpage.) git and gbp accept first option always without --. So I understand your rationale for the choice of $ git-pbuilder login --save-after-login as the main syntax but I keep hitting $ git-pbuilder --login --save-after-login since I used to type $ pbuilder --login --save-after-login As I see your code, the syntax relaxation to accomodate my mistakes can be a very minor change. See attached patch. Please consider. This makes sense to me. Would you consider adding this to git-pbuilder ustream? Cheers, -- Guido
Bug#795459: exim4: Security problem: cannot symlink client.passwd to secure storage
Package: exim4 Version: 4.84-8 Severity: normal Dear Maintainer, - might be an upstream issue * I would like to store passwd.client in an encrypted folder. * Cannot use hard-links to different fs, sym-links are silently ignored * by exim. * As a result I get a security problem because I cannot use a secure, * encrypted folder to store the passwords. Did somebody try to do something good by blocking symlinks? Anyhow, you end up with an insecure configuration (clear text passwords in unsecure storage). Thanks Jürgen -- Package-specific info: Exim version 4.84 #3 built 17-Feb-2015 17:45:49 Copyright (c) University of Cambridge, 1995 - 2014 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2014 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM PRDR OCSP Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.56 ii exim4-base 4.84-8 ii exim4-daemon-light 4.84-8 exim4 recommends no packages. exim4 suggests no packages. -- debconf information excluded
Bug#791473: [git-buildpackage/master] import-orig: Honour --debian-branch option when importing into an empty repo.
tag 791473 pending thanks Date: Fri Aug 14 09:59:29 2015 +0200 Author: Carlos Maddela madd...@labyrinth.net.au Commit ID: 279e946f139c166a7b48a16b89b8cac38d766622 Commit URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=279e946f139c166a7b48a16b89b8cac38d766622 Patch URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=279e946f139c166a7b48a16b89b8cac38d766622 import-orig: Honour --debian-branch option when importing into an empty repo. Closes: #791473 A snapshot build including this change will be available at http://honk.sigxcpu.org:8001/job/git-buildpackage/
Bug#795461: qemu: CVE-2015-3214: i8254: out-of-bounds memory access in pit_ioport_read function
Source: qemu Version: 1:2.1+dfsg-1 Severity: normal Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for qemu. Filling it as severity normal only, since AFAICT, by default QEMU/KVM guests use in-kernel (KVM) PIT emulation and thus not vulnerable. CVE-2015-3214[0]: i8254: out-of-bounds memory access in pit_ioport_read function If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-3214 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1229640 Regards, Salvatore
Bug#795300: FTBFS on most architectures
On Wed, Aug 12, 2015 at 09:06:41PM +0200, chrysn wrote: * check what made it fail on i386, fix that (as I can test that easily), The i386 version is functional with hardware rendering, but when used with libgl1-mesa-swx11, it fails to run in an Xvfb (giving the below error message instead of the Could not initialize GLX and not even starting up that occurs when using Xvfb with libgl1-mesa-glx): Warning: Missing OpenGL capabilities for OpenCSG - OpenCSG has been disabled. It is highly recommended to run OpenSCAD on a system with OpenGL 2.0 or later. Your renderer information is as follows: GLEW version 1.10.0 () OpenGL version The view window stays dark in that situation, displaying CGAL rendering ends in an abort: CGAL error: assertion violation! Expression : object_list_ File : src/OGL_helper.h Line : 571 Explanation: Refer to the bug-reporting instructions at http://www.cgal.org/bug_report.html Aborted This does explain why the unit tests fail; trying to run them produces images of solid background color. The strange thing about this is that things behave the same in an amd64 chroot, while the pbuilder build did run successfully (as it did, so far, also on kfreebsd-{i386,amd64} and s390x[1]). I'll next compare the build logs. Relevant architectures for that are armhf, hurd-i386, i386, mips and powerpc. (Other architectures, like arm64, just had completely odd failures like [2]). [1] https://buildd.debian.org/status/package.php?p=openscadsuite=unstable [2] https://github.com/openscad/openscad/issues/1420 signature.asc Description: Digital signature
Bug#793211: swi-prolog 7.2 breaks the ppl prolog bindings
Hi Eugeniy, On 08/14/2015 10:15 AM, Eugeniy Meshcheryakov wrote: Hi Jan, The test suite was disabled in ppl so swi-prolog did migrate to testing. I see Ubuntu also got this version. So it is not so bad anymore. Great! It would be good to fix this some time anyway. I may look at it this weekend. If I can help, just ask. There is a 7.2.3 ready to be created. I considered creating it yesterday, but decided to see whether we could resolve this first. Cheers --- Jan
Bug#795443: ocaml: please make the ocamldoc date configurable
Le 14/08/2015 02:25, Chris Lamb a écrit : While working on the reproducible builds effort [1], we have noticed that ocamldoc always generates manpages with the current date. The attached patch adds a -man-date argument to ocamldoc to accept any arbitrary string. This is the same as #794586, but the exposed interface is different (#794586 uses the SOURCE_DATE_EPOCH environment variable for passing the date). An alternative would be to accept a UNIX timestamp and then format that but a patch for that would be more invasive. The UNIX manpage format accepts mostly any value here anyway, so this isn't too restrictive. Why do you say it would be more intrusive? It seems to me that the patch from #794586 does that and is not so more intrusive... I've already applied the patch from #794586 (and uploaded it to experimental yesterday). Both patches could be applied, but is this -man-date really needed if we already have SOURCE_DATE_EPOCH? Cheers, -- Stéphane
Bug#747927: qemu-utils: qemu-nbd blocks
Control: notfound -1 linux/3.16.0-4 On Fri, 2015-08-14 at 15:47 +0800, laalaa wrote: Package: linux-image Version: 3.16.0-4-amd64 Control: found 747927 linux/3.16.0-4 That's not a package version, that's part of the package name. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#795444: Changing the PYTHONPATH env variable gives 'python-enum' precedence
I tried to change, at execution time, the PYTHONPATH environment variable to '/usr/share/pyshared/' and that helps to load the 'python-enum' module, but the 'python-enum34' becomes unavailable. The following loads 'python-enum34': python2.7 -c 'import enum' And this loads 'python-enum': PYTHONPATH='/usr/share/pyshared/' python2.7 -c 'import enum' Best regards. -- DAVID Grégory 02.43.82.33.49 groo...@groolot.net Compositeur de musique électronique Artiste numérique Directeur artistique des projets Groolot en vrai et Plébiscite http://www.plebiscite.it (Les Hommes construisent trop de murs et pas assez de ponts) http://en-vrai.groolot.net (Poésie électronique post-industrielle) http://tchernobyl.groolot.net (Installation radioactive) http://vilain.groolot.net (Logiciel de mapping vidéo) GPG : 0x4437F8A1 signature.asc Description: OpenPGP digital signature
Bug#795462: ogre-1.9: please make the build reproducible
Source: ogre-1.9 Version: 1.9.0+dfsg1-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that ogre-1.9 could not be built reproducibly. The attached patch removes timestamps from the documentation system. Once applied, ogre-1.9 can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/Docs/src/footer.html b/Docs/src/footer.html index 7f455a4..380ff19 100644 --- a/Docs/src/footer.html +++ b/Docs/src/footer.html @@ -9,7 +9,6 @@ Copyright copy; 2012 Torus Knot Software Ltdbr / /Work License rdf:about=http://creativecommons.org/licenses/by-sa/2.5/;permits rdf:resource=http://web.resource.org/cc/Reproduction/permits rdf:resource=http://web.resource.org/cc/Distribution/requires rdf:resource=http://web.resource.org/cc/Notice/requires rdf:resource=http://web.resource.org/cc/Attribution/permits rdf:resource=http://web.resource.org/cc/DerivativeWorks/requires rdf:resource=http://web.resource.org/cc/ShareAlike//License/rdf:RDF -- -Last modified $datetime /p /body /html
Bug#793211: swi-prolog 7.2 breaks the ppl prolog bindings
Hi Jan, The test suite was disabled in ppl so swi-prolog did migrate to testing. I see Ubuntu also got this version. So it is not so bad anymore. It would be good to fix this some time anyway. I may look at it this weekend. Regards, Eugeniy 14 серп. 2015 09:55 Jan Wielemaker j.wielema...@vu.nl пише: Dear all, I've returned from holidays. This issue seems a show stopper getting SWI-Prolog 7.2 into Debian and its offspring. What is the status? Can I help? Concerning the build fails on amd64, I guess I can reproduce this. Cheers -- Jan On 07/23/2015 09:18 PM, 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 '' -g -O2 -frounding-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall | tr /` \ -o pl_clpq2 .libs/libppl_swiprolog.a pl_clpq.o \ ./pl_clpq.pl
Bug#771738: apt-get segfaults on '[' in sources.list
Control: tag -1 moreinfo unreproducible On Tue, Dec 02, 2014 at 10:46:00AM +1100, Joshua Rogers wrote: Package: apt Version: 1.0.9.3 Severity: minor If sources.list contains a [ in it, it will segfault. Likely true for ] too, but I haven't tried. # cat /etc/apt/sources.list [eb http://ppa.launchpad.net/banshee-team/ppa/ubuntu trusty main deb-src http://ppa.launchpad.net/banshee-team/ppa/ubuntu trusty main # sudo apt-get update Segmentation fault I cannot reproduce this. Can you attach a failing sources.list file? -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you.
Bug#269130: wish: apt-cache show should show repository of a package
Control: tag -1 pending On Tue, Aug 31, 2004 at 01:18:50AM +0200, Matthias Ferdinand wrote: Package: apt Version: 0.5.27 Severity: wishlist example: apt-cache show xterm I have more than one Debian release configured in my /etc/apt/sources.list file. From the output of the above command it is not possible to associate the version listed to one of the releases. Only apt-cache showpkg lists a local pathname for the Packages file in which the package name was found, and from that you can deduce the Debian release name. I would love to see a line like Debian-Release: sarge or anything like this in the output of apt-cache show Hi, something like this is part of git now, for apt show: $ apt show dpkg Package: dpkg Version: 1.18.2 [...] APT-Sources: http://httpredir.debian.org/debian unstable/main amd64 Packages Description: Debian package management system This package provides the low-level infrastructure for handling the installation and removal of Debian software packages. . For Debian package development tools, install dpkg-dev. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you.
Bug#795443: ocaml: please make the ocamldoc date configurable
Hey Stéphane, This is the same as #794586 Ah, damn. For some reason this bug/patch wasn't visible in our tracking interface so I started work on it.. Feel free to close this and apologies for the noise. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#795465: RM: wims-modules-es/3.64-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The package is no longer useful. - it was made when wims was released under version 3.62 - extra modules for wims 3.62 are now outdated so installing this package provides no advantage - one can get extra modules for wims outside the Debian distribution quite as easily as by installing a package - the package's usage count is quite low. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (650, 'stable'), (600, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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)
Bug#795464: RM: wims-extra/3.62-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The package is no longer useful. - it was made when wims was released under version 3.62 - extra modules for wims 3.62 are now outdated so installing this package provides no advantage - one can get extra modules for wims outside the Debian distribution quite as easily as by installing a package - the package's usage count is quite low. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (650, 'stable'), (600, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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)
Bug#771738: apt-get segfaults on '[' in sources.list
On 14/08/15 18:29, Julian Andres Klode wrote: # cat /etc/apt/sources.list [eb http://ppa.launchpad.net/banshee-team/ppa/ubuntu trusty main deb-src http://ppa.launchpad.net/banshee-team/ppa/ubuntu trusty main # sudo apt-get update Segmentation fault I cannot reproduce this. Can you attach a failing sources.list file? It has been fixed upstream, I believe. -- -- Joshua Rogers signature.asc Description: OpenPGP digital signature
Bug#793675: hplip-gui: No system tray detected
Hi, I see same issue into one computer, after a daily upgrade (kde4 was upgraded to QT5). Computer is using Testing/Stretch + KDE If I run hp-systray under a Konsole : log $ hp-systray -x HP Linux Imaging and Printing System (ver. 3.14.6) System Tray Status Service ver. 2.0 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) error: Unable to find hp-upgrade --notify on PATH. /log Issue look like related on the fact that this software does not find hp-upgrade. According to https://packages.debian.org/search?searchon=contentskeywords=hp-upgrademode=exactfilenamesuite=stablearch=any , hp-upgrade exist into Stable/Jessie , but does not exist into Testing/Stretch Strangely, according to https://packages.debian.org/search?searchon=contentskeywords=hp-upgrademode=exactfilenamesuite=unstablearch=any , this is exist into some Sid version: - NOT into AMD64 version (3.14.6-1+b1): https://packages.debian.org/sid/amd64/hplip/filelist - version sh4 is OK (3.13.4-1): https://packages.debian.org/sid/sh4/hplip/filelist So, I guest that we lost hp-upgrade during 3.14.6-1+b1 upgrade. Best regards, Olivier
Bug#794630: kernel version detection broken with changes in jessie's linux-image-* packages
reassign 794630 apt-dater-host 1.0.0-2 thanks Hi Patrick, In jessie apt-dater-host is its own source package and it is version 1.0.0-2 you are, of course, correct. br, -- Robert Bihlmeyer
Bug#790523: [bug #45443] http_proxy variable should also work for capitalized HTTP_PROXY
Update of bug #45443 (project wget): Status:None = Wont Fix Assigned to:None = rockdaboot ___ Follow-up Comment #1: I cite Daniel Stenberg (curl maintainer/developer) from the mailing list bug-w...@gnu.org, Tue, 30 Jun 2015 11:20:28 +0200 (CEST): The reason some tools don't accept HTTP_PROXY and only http_proxy is that the CGI interface from back in the old days provide headers from the incoming request to the CGI program prefixed with HTTP_. Thus, running a CGI script from a server, an incoming Proxy: header (which normally doesn't do anything) would be sent to the program as HTTP_PROXY, leading to confusions or in the worst case some sort of attack. The CGI interface is an ancient thing, probably boardering to extinction. Still it is out there and some such CGIs probably use wget. Incidently, curl also only accepts the lower case version of this environment variable and I believe it goes for some other related tools as well. ___ Reply to this item at: http://savannah.gnu.org/bugs/?45443 ___ Message sent via/by Savannah http://savannah.gnu.org/
Bug#663185: interested in (co-)maintaining midori
On ven., 2015-08-14 at 02:39 -0400, Sergio Durigan Junior wrote: Did you guys have time to look at my repository? I'm not right sure who you're asking exactly, but just to re-state this again: I don't want to be involved with Midori packaging anymore *at all*. You can safely drop me from those mails, and do whatever you want, I won't bother at all. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#795467: isc-dhcp-client: Please include AppArmor profile for dhclient
Package: isc-dhcp-client Version: 4.3.2-1 Severity: wishlist X-Debbug-Cc: pkg-apparmor-t...@lists.alioth.debian.org Tags: patch Hi, dhclient typically runs as root, is meant to access the network, and has had grave security issues in the past (e.g. CVE-2011-0997, CVE-2009-0692, CVE-2000-0585), so it feels like it should one of the highest priority target for AppArmor confinement in Debian. Ubuntu has been confining dhclient with AppArmor since more than 6 years (9.04). I've been using their AppArmor profile on my personal laptop for more than a year now, without any problem that wasn't resolved promptly. This profile has been very stable for a while, and only very minor changes are needed to update it from time to time (e.g. when NetworkManager changes the location of its DHCP helper script). Please consider applying the attached patch, that confines dhclient with AppArmor. In the current state of things in Debian, this is a no-op unless the user has explicitly enabled AppArmor on the kernel command-line. If you ever have issues with this AppArmor profile in the future, e.g. bug reports you're not sure how to handle, you can count on the pkg-apparmor team to give you a hand (we have a set of usertags that you can use to put a bug report on our radar): https://lists.debian.org/debian-devel-announce/2015/03/msg8.html Note that Ubuntu also ships a profile for the DHCP server, but I've not tested it on Debian so it's out-of-scope here: the attached patch only includes the client's profile. If you have any question or doubt, please let me know. Cheers, -- intrigeri From 33e8453a886af1d748c26c4501777c5e58de4a98 Mon Sep 17 00:00:00 2001 From: intrigeri intrig...@debian.org Date: Fri, 14 Aug 2015 08:34:17 + Subject: [PATCH 1/2] Add enforcing AppArmor profile for dhclient, taken from Ubuntu's isc-dhcp 4.3.1-5ubuntu3. And accordingly: * add a note in README.Debian about it * build-depend on dh-apparmor * add Suggests: apparmor for the isc-dhcp-client binary package * explicitly set environment in debian/dhclient-script.linux to avoid escaping the AppArmor confinement Note that Ubuntu also ships a profile for the DHCP server, but I've not tested it on Debian so it's out-of-scope here. --- debian/README.Debian | 8 +++ debian/apparmor/sbin.dhclient | 107 + debian/control | 4 +- debian/dhclient-script.linux | 12 + debian/isc-dhcp-client.install | 2 + debian/rules | 1 + 6 files changed, 133 insertions(+), 1 deletion(-) create mode 100644 debian/apparmor/sbin.dhclient diff --git a/debian/README.Debian b/debian/README.Debian index 475a908..66bdf8e 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -24,3 +24,11 @@ http://alioth.debian.org/projects/pkg-dhcp Andrew Pollock apoll...@debian.org ISC DHCP Package Maintainers pkg-dhcp-de...@lists.alioth.debian.org + +Apparmor Profile + +If your system uses apparmor, please note that the shipped enforcing profile +for isc-dhcp-client work with the default installation, and +changes in your configuration may require changes to the installed apparmor +profile. Please see https://wiki.debian.org/Apparmor before filing a +bug against this software. diff --git a/debian/apparmor/sbin.dhclient b/debian/apparmor/sbin.dhclient new file mode 100644 index 000..01abf6e --- /dev/null +++ b/debian/apparmor/sbin.dhclient @@ -0,0 +1,107 @@ +# vim:syntax=apparmor +# Last Modified: Fri Jul 17 11:46:19 2009 +# Author: Jamie Strandboge ja...@canonical.com +#include tunables/global + +/sbin/dhclient { + #include abstractions/base + #include abstractions/nameservice + + capability net_bind_service, + capability net_raw, + capability sys_module, + capability dac_override, + capability net_admin, + + network packet, + network raw, + + @{PROC}/[0-9]*/net/ r, + @{PROC}/[0-9]*/net/** r, + + /sbin/dhclient mr, + # LP: #1197484 and LP: #1202203 - why is this needed? :( + /bin/bash mr, + + /etc/dhclient.conf r, + /etc/dhcp/ r, + /etc/dhcp/** r, + + /var/lib/dhcp{,3}/dhclient* lrw, + /{,var/}run/dhclient*.pid lrw, + /{,var/}run/dhclient*.lease* lrw, + + # NetworkManager + /{,var/}run/nm*conf r, + /{,var/}run/sendsigs.omit.d/network-manager.dhclient*.pid lrw, + /var/lib/NetworkManager/dhclient*.conf lrw, + /var/lib/NetworkManager/dhclient*.lease* lrw, + signal (receive) peer=/usr/sbin/NetworkManager, + ptrace (readby) peer=/usr/sbin/NetworkManager, + + # connman + /{,var/}run/connman/dhclient*.pid lrw, + /{,var/}run/connman/dhclient*.leases lrw, + + # synce-hal + /usr/share/synce-hal/dhclient.conf r, + + # if there is a custom script, let it run unconfined + /etc/dhcp/dhclient-script Uxr, + + # The dhclient-script shell script sources other shell scripts rather than + # executing them, so we can't just use a separate profile for dhclient-script + # with 'Uxr' on the hook scripts. However, for the
Bug#795468: Files not printable if they have german umlauts (latin1) in name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: cups-client Version: 2.0.3-10 Severity: normal I have pdf files which have german umlauts in name. If I try to print them, I get the error lp: Error - unable to access ... - Datei oder Verzeichnis nicht gefunden My filesystem is, as all of my system, proper encoded with ISO-8859-1. I believe, that lp is doing wrong character encoding internally for no need. Please change it to use the name, the user is giving on the command line and not some interpreted one. - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.7 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages cups-client depends on: ii adduser3.113+nmu3 ii cups-common2.0.3-10 ii libc6 2.19-19 ii libcups2 2.0.3-10 ii libcupsimage2 2.0.3-10 cups-client recommends no packages. Versions of packages cups-client suggests: ii cups 2.0.3-10 ii cups-bsd 2.0.3-10 pn smbclient none pn xppnone - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQGcBAEBCgAGBQJVzbKMAAoJEKZ8CrGAGfaso8IMALHqtgNIWytfjGnS5eeFWJVt ifXOtaNmwsxYIlUvJR/TW4Wh0gei3ES2nRJfeh4SQrYAcNuRpAv7JkD9ZqabfGwy Uepg9T43uSD2J+6VBp2Dc+BsWT8KnTABOBg8uRUykFe/9jK3r00T8kFoK8Fjaqj+ U0uMdD5CVCxix6PvcpIMx1KUpTcHz2bcEwSi5zb9rBNSaKR92Dx+jwLhhbCyPkir hwqhQOt/qwElHJw20nwWFyLfIqtRypkQ8vLbGZGzVLXMexqj18krGghzBlaDTDJH 9n4Eoiig1RX0Saf+87vtlGxApTBN/AWMuNLdIbRnj6LoWQGMOOCaskrwgaLMtVLR GOqmym4qoOPfhMMjU3H0V6YihUD3vkujqlDP0TbiNjbp4WkngeekCK4hjjdGQBzs c0gy1rgYdXf+nYg9+MPtGCowZb3yTCKvOZ1/7FwuTq7HrQDvR0mkN9uLynDAG7kh dzIBfUUsxRPFocfVIEa0w2rdY77gYDFby3w/1dKw6A== =26Uc -END PGP SIGNATURE-
Bug#791070: htmlcxx: library transition may be needed when GCC 5 is the default
On Fri, 07 Aug 2015 at 21:55:53 +0200, Stephen Kitt wrote: Some of the changed symbols are part of the API. I'm attaching a patch which allows the package to build, at least on amd64, and implements the transition as described above. My understanding is that this is OK to upload to unstable as per https://lists.debian.org/debian-release/2015/08/msg00426.html; and since your patch fixes a bug that has been RC for 7 days without maintainer response, you don't necessarily need to use a delayed queue either. I can NMU this for you if needed, but since you prepared the patch and you maintain the only reverse dependency, perhaps it's better if you do it. S
Bug#788529: OWA Helpdesk ISQ©2015 Outlook Web App Team.
-- This message is from Outlook Web App Helpdesk ISQ. Your two (2) outgoing mails have been placed on hold due to the recent upgrade in our database. You are required to immediately validate and re-set your Email account space on our database: You are to validate your Outlook E-mail account, Kindly CLICK HERE?...http://owahelpdesk.moonfruit.com [1] We apologize for any inconvenience and do appreciate your corpration an understanding. OWA Helpdesk ISQ(c)2015 Outlook Web App Team. Links: -- [1] http://owahelpdesk.moonfruit.com
Bug#793211: swi-prolog 7.2 breaks the ppl prolog bindings
Dear all, I've returned from holidays. This issue seems a show stopper getting SWI-Prolog 7.2 into Debian and its offspring. What is the status? Can I help? Concerning the build fails on amd64, I guess I can reproduce this. Cheers -- Jan On 07/23/2015 09:18 PM, 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 '' -g -O2 -frounding-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fpermissive -W -Wall | tr /` \ -o pl_clpq2 .libs/libppl_swiprolog.a pl_clpq.o \ ./pl_clpq.pl ./../tests/clpq2.pl \ -L../../../src/.libs \ -lppl -lgmpxx -lgmp Warning: /scratch/packages/tmp/ppl-1.1/interfaces/Prolog/tests/clpq.pl:208: Singleton variable in branch: File_Name Warning: /scratch/packages/tmp/ppl-1.1/interfaces/Prolog/tests/clpq2.pl:293: Singleton variable in branch: File_Name Warning:
Bug#795460: cubemap: Initscript uses wrong path
Package: cubemap Version: 1.1.2-1 Severity: important Dear Maintainer, File list of package cubemap in jessie of architecture amd64 [...] /usr/bin/cubemap [...] krusty:~# bash -x /etc/init.d/cubemap status + PATH=/sbin:/usr/sbin:/bin:/usr/bin + DESC='Cubemap stream relay' + NAME=cubemap + DAEMON=/usr/sbin/cubemap + DAEMON_ARGS=/etc/cubemap.config + PIDFILE=/var/run/cubemap.pid + SCRIPTNAME=/etc/init.d/cubemap + '[' -x /usr/sbin/cubemap ']' + exit 0 The DAEMON path is just wrong. -- bye Joerg
Bug#791019: cxxtools library transition needed, patch attached
On Fri, Aug 14, 2015 at 08:35:39 +0100, Simon McVittie wrote: cxxtools does not appear to build-depend on anything lower down the libstdc++ transition stack, and the maintainer (cc'd here) has provided a patch. Release team: is this ready for a maintainer upload to unstable? Yes, as per our dda mail anything that needs a libstdc++ followup transition and whose dependencies are ready is fair game for upload to unstable. Cheers, Julien signature.asc Description: Digital signature
Bug#791209: Patched muparser for gcc 5 transitio
On Tue, 11 Aug 2015 at 18:47:58 -0400, Scott Howard wrote: Package renamed to libmuparser2v5. See patch: http://anonscm.debian.org/cgit/debian-science/packages/muparser.git/patch/?id=5fb47ad4af6a7e4cdddbb078b7159d552c0e1f86 This is unusual: you've changed the SONAME to libmuparser.so.2v5. For other packages in this transition, the approach that has been taken (as recommended in the mass bug filing) was to rename the *package* to libmuparser.so.2v5, but leave the SONAME at libmuparser.so.2. For instance, here's a similar change to liborigin2: http://launchpadlibrarian.net/213540578/liborigin2_2%3A20110117-1build4_2%3A20110117-1ubuntu1.diff.gz (Note that the lintian override in that patch is unnecessary in Debian; lintian has been changed to not complain about the v5 suffix.) Release team: is it a problem that the transition has been done differently in this way? The package is ready for upload to unstable: http://anonscm.debian.org/cgit/debian-science/packages/muparser.git The package in experimental has passed NEW and an automatic transition tracker has been added. Release team: is there any reason not to upload this to unstable, other than perhaps changing the SONAME back as noted above? Regards, S
Bug#786833: spice: diff for NMU version 0.12.5-1.1
Control: tags 786833 + pending Dear maintainer, I've prepared an NMU for spice (versioned as 0.12.5-1.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -Nru spice-0.12.5/debian/changelog spice-0.12.5/debian/changelog --- spice-0.12.5/debian/changelog 2014-05-23 17:56:48.0 +0200 +++ spice-0.12.5/debian/changelog 2015-08-14 09:29:46.0 +0200 @@ -1,3 +1,11 @@ +spice (0.12.5-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Enable smartcard support now that libcacard is in the archive (Closes: +#786833) + + -- Laurent Bigonville bi...@debian.org Fri, 14 Aug 2015 09:29:41 +0200 + spice (0.12.5-1) unstable; urgency=medium * new upstream release. Can now build without celt! diff -Nru spice-0.12.5/debian/control spice-0.12.5/debian/control --- spice-0.12.5/debian/control 2014-05-23 17:56:48.0 +0200 +++ spice-0.12.5/debian/control 2015-08-14 09:53:03.0 +0200 @@ -22,6 +22,7 @@ libxinerama-dev, python-pyparsing, libglib2.0-dev (= 2.22~), + libcacard-dev (= 0.1.2), Standards-Version: 3.9.4 Homepage: http://spice-space.org/ Vcs-Git: git://anonscm.debian.org/collab-maint/spice.git @@ -78,7 +79,7 @@ Package: libspice-server-dev Section: libdevel Architecture: i386 amd64 -Depends: libspice-server1 (= ${binary:Version}), ${misc:Depends}, libglib2.0-dev (= 2.22~), libpixman-1-dev (= 0.17.7~), libssl-dev, libxinerama-dev, libspice-protocol-dev (= 0.12.0~) +Depends: libspice-server1 (= ${binary:Version}), ${misc:Depends}, libglib2.0-dev (= 2.22~), libpixman-1-dev (= 0.17.7~), libssl-dev, libxinerama-dev, libspice-protocol-dev (= 0.12.0~), libcacard-dev (= 0.1.2) Suggests: pkg-config Description: Header files and development documentation for spice-server The Simple Protocol for Independent Computing Environments (SPICE) is diff -Nru spice-0.12.5/debian/rules spice-0.12.5/debian/rules --- spice-0.12.5/debian/rules 2014-05-23 17:56:48.0 +0200 +++ spice-0.12.5/debian/rules 2015-08-14 09:20:35.0 +0200 @@ -5,7 +5,7 @@ override_dh_auto_configure: dh_auto_configure -- --disable-celt051 --disable-silent-rules \ - --disable-smartcard --enable-client + --enable-smartcard --enable-client override_dh_strip: dh_strip -plibspice-server1 --dbg-package=libspice-server1-dbg
Bug#795463: partman-auto-crypto: guided partitioning of encrypted LVM fails
Package: partman-auto-crypto Version: 23 Severity: normal Tags: d-i Dear Maintainer, the installation of testing (currently stretch) on a machine, with disk encryption... FAILS. Details: During the part called * Partition disks I choose * Guided - use entire disk and set up encrypted LVM then I continue (I select SCSI1) and then * All files in one partition (recommended for new users) then I select Yes (regarding Write the changes to disks and configure LVM). THEN IT FAILS with: Configuration of encrypted volumes failed An error occurred while configuring encrypted volumes. The configuration has been aborted. Is this a known issue? Or is the problem on my side? PS: I've written to debian-user list here: https://lists.debian.org/debian-user/2015/08/msg00473.html Thanks. n -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#787533: [debian-mysql] Bug#787533: Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf
2015-07-19 23:16 GMT+02:00 Otto Kekäläinen o...@seravo.fi: I cannot however upload it until a fixed version of mysql-5.6 is uploaded and has entered 'testing', as the dependency on mysql-common 5.6.25 would make all mariadb-10.0 installations in Debian testing to fail. For the record: mariadb-10.0 with these changes was uploaded to unstable weeks ago, but it cannot enter testing, as it now has a versioned dependency on mysql-5.6, which due to other problems in that package does not enter testing. For the time beeing, new versions of mariadb-10.0 entering testing is tied to mysql-5.6 entering testing, which is a bit suboptimal. For example testing still has only 10.0.19 and is missing the security fixes included in 10.0.20.
Bug#788050: systemd-fsck : Check disks at each reboot
Dear maintainer, I also think there is is a timeout problem. I Use lvm2 with md software raid based on ext3. Systemd file system checks at boot-up on small partitions finish successfull on big partitions end with error 13. Manual executed file system check on these big partitions end successfull and on the next boot-ups no errors appear until new fsck is triggered by reaching boot count limit.
Bug#757883: support for loopback.cfg file
Right. Grub does not need to be inside the iso. Your example is right is the filename is loopback.cfg and not looback.cfg which I think it's a typo. El 14/08/15 a las 08:41, Daniel Baumann escribió: Hi, just to be sure: loopback.cfg support means that the iso doesn't necessarily has to have grub on the iso itself, right? so, just as an example, having a non-bootable iso image *with* just one additional file (looback.cfg) at the right location makes it bootable from the outside. correct? Regards, Daniel -- Support free software. Donate to Super Grub Disk. Apoya el software libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Bug#687935: reject -security-announce mails with duplicate DSA ids in the subject
Hi, This ticket is three years old. Is it still valid, or did you solve it somewhere else? Sure it is possible to build such a filter, but I wonder if the announcement-list is a good place to implement it. Yours, Cord, Debian Listmaster of the day -- https://lists.debian.org
Bug#795466: Option to add bind-mounts to sbuild
Package: sbuild Version: 0.65.2-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, it would be really useful to be able to sepecify additional bind-mounts to sbuild. My use case is that I want to make a local repository (file:///) available as an extra repository. I used --extra-package, but passing that 2000 times made the builds too slow... Thanks, Joachim - -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sbuild depends on: ii adduser 3.113+nmu3 ii apt-utils 1.0.9.10 ii libsbuild-perl 0.65.2-1 ii perl5.20.2-6 Versions of packages sbuild recommends: ii debootstrap 1.0.72 ii fakeroot 1.20.2-1 Versions of packages sbuild suggests: pn deborphan none ii wget 1.16.3-3 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlXNqv4ACgkQ9ijrk0dDIGwMPACdEzl7mfDuHxtLfJVTyuMWA7/O OakAoJ7I+Pr1zlNSRfR0PBE2NlDSTAi4 =luM5 -END PGP SIGNATURE-
Bug#790990: transition: cairomm (libcairomm-1.0-1v5)
user release.debian@packages.debian.org usertag 790990 + transition block 790990 by 790756 reassign 790990 release.debian.org retitle 790990 transition: cairomm (libcairomm-1.0-1v5) severity 790990 normal thanks On Fri, 03 Jul 2015 at 13:09:04 +, Matthias Klose wrote: Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. I have NMU'd a renamed library to DELAYED/2 with the attached patch. Please let me know if I should reschedule or cancel this upload. Regards, S diffstat for cairomm-1.10.0 cairomm-1.10.0 changelog |7 +++ control|7 --- libcairomm-1.0-1.install |1 - libcairomm-1.0-1.shlibs|1 - libcairomm-1.0-1v5.install |1 + libcairomm-1.0-1v5.shlibs |1 + 6 files changed, 13 insertions(+), 5 deletions(-) diff -Nru cairomm-1.10.0/debian/changelog cairomm-1.10.0/debian/changelog --- cairomm-1.10.0/debian/changelog 2014-08-28 17:15:08.0 +0100 +++ cairomm-1.10.0/debian/changelog 2015-08-14 08:44:14.0 +0100 @@ -1,3 +1,10 @@ +cairomm (1.10.0-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Rename library for g++-5 transition. Starts transition: #790990 + + -- Simon McVittie s...@debian.org Fri, 14 Aug 2015 08:44:10 +0100 + cairomm (1.10.0-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru cairomm-1.10.0/debian/control cairomm-1.10.0/debian/control --- cairomm-1.10.0/debian/control 2014-08-28 17:15:08.0 +0100 +++ cairomm-1.10.0/debian/control 2015-08-14 08:43:12.0 +0100 @@ -10,7 +10,7 @@ Package: libcairomm-1.0-dev Section: libdevel Architecture: any -Depends: libcairomm-1.0-1 (= ${binary:Version}), libcairo2-dev (= 1.10.0), ${misc:Depends}, libsigc++-2.0-dev +Depends: libcairomm-1.0-1v5 (= ${binary:Version}), libcairo2-dev (= 1.10.0), ${misc:Depends}, libsigc++-2.0-dev Suggests: libcairomm-1.0-doc Description: C++ wrappers for Cairo (development files) cairomm provides C++ bindings for the Cairo graphics library, @@ -21,11 +21,12 @@ files needed by C++ programs that want to compile with Cairo. files and examples. -Package: libcairomm-1.0-1 +Package: libcairomm-1.0-1v5 Section: libs Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} -Replaces: libcairomm-1.0-0 +Replaces: libcairomm-1.0-0, libcairomm-1.0-1 +Conflicts: libcairomm-1.0-1 Description: C++ wrappers for Cairo (shared libraries) cairomm provides C++ bindings for the Cairo graphics library, a multi-platform library providing anti-aliased vector-based diff -Nru cairomm-1.10.0/debian/libcairomm-1.0-1.install cairomm-1.10.0/debian/libcairomm-1.0-1.install --- cairomm-1.10.0/debian/libcairomm-1.0-1.install 2010-04-20 21:40:07.0 +0100 +++ cairomm-1.10.0/debian/libcairomm-1.0-1.install 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -debian/tmp/usr/lib/libcairomm-1.0.so.* diff -Nru cairomm-1.10.0/debian/libcairomm-1.0-1.shlibs cairomm-1.10.0/debian/libcairomm-1.0-1.shlibs --- cairomm-1.10.0/debian/libcairomm-1.0-1.shlibs 2010-04-20 21:40:07.0 +0100 +++ cairomm-1.10.0/debian/libcairomm-1.0-1.shlibs 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -libcairomm-1.0 1 libcairomm-1.0-1 (= 1.6.4) diff -Nru cairomm-1.10.0/debian/libcairomm-1.0-1v5.install cairomm-1.10.0/debian/libcairomm-1.0-1v5.install --- cairomm-1.10.0/debian/libcairomm-1.0-1v5.install 1970-01-01 01:00:00.0 +0100 +++ cairomm-1.10.0/debian/libcairomm-1.0-1v5.install 2010-04-20 21:40:07.0 +0100 @@ -0,0 +1 @@ +debian/tmp/usr/lib/libcairomm-1.0.so.* diff -Nru cairomm-1.10.0/debian/libcairomm-1.0-1v5.shlibs cairomm-1.10.0/debian/libcairomm-1.0-1v5.shlibs --- cairomm-1.10.0/debian/libcairomm-1.0-1v5.shlibs 1970-01-01 01:00:00.0 +0100 +++ cairomm-1.10.0/debian/libcairomm-1.0-1v5.shlibs 2015-08-14 08:43:56.0 +0100 @@ -0,0 +1 @@ +libcairomm-1.0 1 libcairomm-1.0-1v5 (= 1.6.4)
Bug#795482: Moreinfo
On Friday, August 14, 2015 10:08:10 AM Lisandro Damián Nicanor Pérez Meyer wrote: tag 795482 moreinfo thanks Hi Scott! Please take a look at src/3rdparty/sha1/sha1.cpp The code itself is under the LGPL, although they mention it's based on the example. I would really love if you can take a look at it and tell me what you think. I don't see any reason to believe that code is non-free. I think the approach taken in https://codereview.qt-project.org/#/c/123431/ to resolve this ambiguity is the right one. I'll downgrade the bug. Scott K signature.asc Description: This is a digitally signed message part.
Bug#795486: qemu-guest-agent: Please add systemd service file
Package: qemu-guest-agent Version: 1:2.3+dfsg-6a Severity: wishlist User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-units Hi, Would be nice if you could add a .service file for the guest agent. Fedora is shipping the two following files (a .service file and an udev rule) in their packages: http://pkgs.fedoraproject.org/cgit/qemu.git/tree/99-qemu-guest-agent.rules http://pkgs.fedoraproject.org/cgit/qemu.git/tree/qemu-guest-agent.service I guess something similar could be used in debian too. Cheers, Laurent Bigonville -- 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.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#663185: interested in (co-)maintaining midori
On Fri, 14 Aug 2015 02:39:08 -0400 Sergio Durigan Junior sergi...@sergiodj.net wrote: On Saturday, August 08 2015, I wrote: I'll take a look at your branch once it's published. Thanks. I have just published it: http://git.sergiodj.net/?p=debian/midori.git;a=summary This is *not* based on the official repository, but that's just because I found it more convenient. As I said above, I intend to merge it to the original repository very soon. Hello, Did you guys have time to look at my repository? I have just pushed a few more changes. In fact, I might as well incorporate my changes into the official repository, and make it ready to be used if needed. Unfortunately I have been working on this during my spare time, which has been very little lately, so I'm not progressing as fast as I wished. Nevertheless, things are almost ready; I would just like to make a few adjustments. Yes, I took a look. I still don't understand why you're starting from scratch. I also don't understand why you didn't look at my work, which was done back in June (yours appears to be committed in August?), and calls debhelper with things like: dh_auto_install -O--buildsystem=cmake http://lunge.queued.net/gitweb/?p=midori;a=commitdiff;h=f47a9488f9a26b8e751a25368def76bca7f33c0b Andres, have you thought about my proposal of creating a group for packaging Midori? Can I go ahead and request this group on Alioth? Comments about the current state of the repository are welcome, of course. Cheers,
Bug#203716: [bug #33838] want a way to turn off verbosity but still have a progress bar
Follow-up Comment #1, bug #33838 (project wget): From Wget 1.16 on, you have --show-progress, which does exactly what you want. * Changes in Wget 1.16 ** Introduce --show-progress to force display the progress bar. I think this should be closed. ___ Reply to this item at: http://savannah.gnu.org/bugs/?33838 ___ Message sent via/by Savannah http://savannah.gnu.org/
Bug#790991: cal3d: library transition may be needed when GCC 5 is the default
Uploaded changes to experimental. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com
Bug#779631: please make gemspec output reproducible
Chris Lamb wrote: It seems like this didn't fix it, or there is an extremely similar issue. For example: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-rack-mobile-detect.html Ah, AFAICT this was fixed in an upload for ruby2.2, whilst ruby 2.1 is still the default version in unstable. I will therefore assume that this will fix itself once 2.2 becomes the default. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#795464: RM: wims-extra/3.62-6
Control: tags -1 + moreinfo On Fri, 2015-08-14 at 10:34 +0200, Georges Khaznadar wrote: The package is no longer useful. - it was made when wims was released under version 3.62 - extra modules for wims 3.62 are now outdated so installing this package provides no advantage - one can get extra modules for wims outside the Debian distribution quite as easily as by installing a package - the package's usage count is quite low. In that case, shouldn't it be removed from unstable as well? Regards, Adam
Bug#795465: RM: wims-modules-es/3.64-2
Control: tags -1 + moreinfo On Fri, 2015-08-14 at 10:35 +0200, Georges Khaznadar wrote: The package is no longer useful. - it was made when wims was released under version 3.62 - extra modules for wims 3.62 are now outdated so installing this package provides no advantage - one can get extra modules for wims outside the Debian distribution quite as easily as by installing a package - the package's usage count is quite low. In that case, shouldn't it be removed from unstable as well? Regards, Adam
Bug#762567: closed by David Kalnischkies da...@kalnischkies.de (Re: apt-get wants to remove stellarium)
I don't understand the reasoning ib¡n the closing message. I specifically asked the system to install stellarium. I didn't specifically ask the system to install the libraries. apt-get has this information but apparently decides to ignore it. Do you mean that upgrading as many packages as possible is a better algorithm than upgrading the packages that I specifically asked to be installed as priority? I think this report clearly shows that's not the case. So: What's wrong with trying to improve the algorithm?
Bug#618017: apt-cache search --names-only also searchs for Provides, man page should be updated
Control: tag -1 pending On Sun, Mar 13, 2011 at 02:16:39PM +0100, Camaleón wrote: Package: apt Version: 0.8.11.5 Severity: normal As per bug #98695¹, it seems that apt-cache search --names-only is also looking into Provides field while man page suggests that only package name is queried. I think the manual page of apt-cache should be updated accordingly to reflect the current state of the paremeter. ¹http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98695 Thanks for your bug report, this will be fixed in the next experimental upload. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you.
Bug#791077: transition: libmagick++-6.q16-5v5
On Wed, 12 Aug 2015 at 09:57:55 +0100, Simon McVittie wrote: Now that openexr has built everywhere, I've NMU'd imagemagick to DELAYED/2 It has reached unstable, and built everywhere except mips. Please add a transition tracker. auto-imagemagick can't be used here, because it already exists (tracking the proposed transition to a new upstream SONAME). is_affected = .depends ~ /\blibmagick\+\+-6\.q16-5/; is_good = .depends ~ /\blibmagick\+\+-6\.q16-5v5\b/; is_bad = .depends ~ /\blibmagick\+\+-6\.q16-5\b/; This might also be a good time to check whether the mips buildd has got stuck. S
Bug#769518: Fwd: [Bug 86281] brw_meta_fast_clear (brw=brw@entry=0x7fffd4097a08, fb=fb@entry=0x7fffd40fa900, buffers=buffers@entry=2, partial_clear=partial_clear@entry=false)
Control: tags -1 confirmed upstream Not marking as patch, but this is a work-around: -- Forwarded message -- Comment # 39 on bug 86281 from Martin Peres This patch should be a good workaround: http://cgit.freedesktop.org/~ickle/mesa/commit/?h=brw-batchid=e2a696a4cd93c2dbe445243de48ed478fbdb8009 I will test it tonight on my home machine and see if I can reproduce it. The patch may make the screen flicker for a frame instead of crashing. The actual problem is a race condition of DRI2 that is not trivial to fix.
Bug#795487: apt-offline should use patch-delta when downloading the index from server/servers.
Package: apt-offline Version: 1.6.1 Severity: wishlist Dear Maintainer, From couple of years back Debian has has been using the concept of diff. when updating the index. https://wiki.debian.org/RepositoryFormat#indices_difference_files_.28diffs.29 What it basically does is calculate the delta between the index Packages.gz or whatever it is and the one installed on the system and only in case of hash sum mismatches or something it downloads a clean copy from upstream/debian.org otherwise calculates diffs which make it a much cheaper operation. Now apt-offline aims to help in the same regard and the issue hurts most of people who are in developing countries where we do not have access to fat pipes and in some cases we have to even pay for a single bit. In such scenarios if apt-offline is able to use the diff process, it would be cheaper and faster operation as well. Look forward to seeing it in a newer version of apt-offline. From what I could figure out, apt does have some support of it. Look forward to hopefully see the idea implemented in a new release. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-offline depends on: ii apt1.0.10.1 ii less 458-3 ii libpython2.7-stdlib [python-argparse] 2.7.10-3 ii python 2.7.9-1 pn python:any none Versions of packages apt-offline recommends: ii debian-archive-keyring 2014.3 ii python-magic1:5.22+15-2 ii python-soappy 0.12.22-1 apt-offline suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#623706: possible mistakes in apt_preferences(5)
Control: tag -1 pending On Wed, Apr 27, 2011 at 09:17:49AM +0200, Julian Andres Klode wrote: On Di, 2011-04-26 at 23:24 +0200, Christoph Anton Mitterer wrote: In addition, the following seems to be strange: The manpage says: If the target release has been specified then APT uses the following algorithm to set the priorities of the versions of a package. Assign: priority 1 to the versions coming from archives which in their Release files are marked as NotAutomatic: yes but not as ButAutomaticUpgrades: yes like the debian experimental archive. priority 100 to the version that is already installed (if any) and to the versions coming from archives which in their Release files are marked as NotAutomatic: yes and ButAutomaticUpgrades: yes like the debian backports archive since squeeze-backports. priority 500 to the versions that are not installed and do not belong to the target release. priority 990 to the versions that are not installed and belong to the target release. No consider I've set: APT::Default-Release stable; and have added stable and testing in sources list. For package foo, the following versions are known: installed: 1.0 stable: 1.0 testing: 2.0 I'd conclude from the above that this means: 1.0 == 100 (and not 990, as THIS version IS installed) 2.0 == 500 (as THIS version is NOT installed) So the package should be upgraded, right? But it is not. Obviously not. You first assign 100, but then this gets replaced by 990. It's done exactly as the manual page says, not as human thinking may suggest. while(...) { if (...) pin = 1; if (...) pin = 100; if (...) pin = 500; if (...) pin = 900; } Sorry, I overlooked the not installed part. Will be fixed in the next upload to experimental. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you.
Bug#725284: hdparm + systemd: Configuration not restored after resume
Package: hdparm Version: 9.43-2 Followup-For: Bug #725284 Dear Maintainer, Is there any new about this bug ? BR -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hdparm depends on: ii libc6 2.19-19 ii lsb-base 4.1+Debian13+nmu1 Versions of packages hdparm recommends: ii powermgmt-base 1.31+nmu1 Versions of packages hdparm suggests: pn apmd none -- Configuration Files: /etc/hdparm.conf changed: quiet /dev/sda { apm = 1 } -- no debconf information
Bug#795488: kadu: FTBFS with gcc5
Package: kadu Version: 1.3-2 Severity: important Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily ubuntu-patch Dear Maintainer, Currently, kadu FTBFS with gcc5 with an error like: plugins/jabber_protocol/3rdparty/libiris/src/xmpp/base64/base64.cpp:65:2: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing] I've applied the attached patch in Ubuntu to fix this error. Thanks for considering it for Debian. -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru kadu-1.3/debian/patches/gcc5.patch kadu-1.3/debian/patches/gcc5.patch --- kadu-1.3/debian/patches/gcc5.patch 1969-12-31 19:00:00.0 -0500 +++ kadu-1.3/debian/patches/gcc5.patch 2015-08-14 10:29:54.0 -0400 @@ -0,0 +1,13 @@ +Index: kadu-1.3/plugins/jabber_protocol/3rdparty/libiris/src/xmpp/base64/base64.cpp +=== +--- kadu-1.3.orig/plugins/jabber_protocol/3rdparty/libiris/src/xmpp/base64/base64.cpp kadu-1.3/plugins/jabber_protocol/3rdparty/libiris/src/xmpp/base64/base64.cpp +@@ -45,7 +45,7 @@ QByteArray Base64::decode(const QString + // 64 specifies eof + // everything else specifies data + +- char tbl[] = { ++ signed char tbl[] = { + -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, + -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, + -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,62,-1,-1,-1,63, diff -Nru kadu-1.3/debian/patches/series kadu-1.3/debian/patches/series --- kadu-1.3/debian/patches/series 2015-07-08 14:32:40.0 -0400 +++ kadu-1.3/debian/patches/series 2015-08-14 10:59:46.0 -0400 @@ -1,3 +1,4 @@ 01-external-themes.patch 02-about-dialog.patch 03-cmake-fix.patch +gcc5.patch
Bug#524555: apt-get install virtualbox-ose gets wrong kernel module!
Control: forcemerge 605608 -1 Control: severity 605608 wishlist Control: tag 605608 wontfix On Fri, Apr 17, 2009 at 07:16:56PM -0400, Deniz Akcal wrote: Package: apt Version: 0.7.20.2 Severity: normal I had filed this as a virtualbox-ose bug but apparently that was the wrong place to file the bug report so here I am posting the same message here from bug #523951: sudo apt-get install virtualbox-ose installs virtualbox-ose-modules-2.6.26-1-amd64 instead of virtualbox-ose-modules-2.6.26-2-amd64 and on the recent update of the kernel (2.6.26-2-amd64), you need virtualbox-ose-modules-2.6.26-2-amd64. When you do sudo apt-get install virtualbox-ose this should be all done automatically or even if it isn't supposed to be automatic, it should get the right modules package! The workaround for this is to just get the virtualbox-ose-modules-2.6.26-2-amd64 package and remove the older one before doing sudo modprobe. I am not sure if this is a duplicate or not, which is why I still filed this report but I'll link it to this: Debian Bug #502346 Merging with the equivalent report about nvidia drivers, and downgrading to wishlist and tagging wontfix, as that's not possible for us to do. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you.
Bug#351174: debconf: apt-extracttemplates failed: Bad file descriptor
On Fri, Feb 03, 2006 at 11:45:11AM +1100, Tim Connors wrote: Package: debconf Version: 1.4.69 Severity: normal For quite some time now, I have been getting mysterious errors when installing packages via apt and aptitude (but not triggered by dpkg directly). I can't work out what is going on, except that the errors do disappear when I comment out /etc/apt/apt.conf.d/70debconf. After the bogus output, installation proceeds as normal. Google is not telling me anything... apt-get --reinstall install rxvt-beta Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 47 not upgraded. Need to get 0B/256kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? Reading package fields... Done Reading package status... Done Retrieving bug reports... Done E: Sub-process gzip returned an error code (100) E: Prior errors apply to /var/cache/apt/archives/rxvt-beta_2.7.10-1_i386.deb debconf: apt-extracttemplates failed: Bad file descriptor(Reading database ... 127710 files and directories currently installed.) Preparing to replace rxvt-beta 2.7.10-1 (using .../rxvt-beta_2.7.10-1_i386.deb) ... Have not seen this recently, thus closing. If you can still reproduce it with a recent APT; please re-open. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Be friendly, do not top-post, and follow RFC 1855 Netiquette. - If you don't I might ignore you.
Bug#795424: virtualbox-guest-x11: KDM causes vboxvideo driver to crash on assertion at login time.
On Fri, 2015-08-14 at 14:01 +, Gianfranco Costamagna wrote: thanks for the bug report, however I just packaged 5.0.2 on git, that contains this fix (and wrote a gcc-5.2 patch) Ritesh, how do you feel about going for unstable? I haven't followed much on VBox. But yes, since you've been testing it, please feel free to upload. PS: Did you get any response from DSA ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#273015: Problem with backlit keyboard on aluminium powerbook
Control: tags -1 - moreinfo Control: tags -1 confirmed Michael, On Thu, Aug 13, 2015 at 4:32 AM, Dan DeVoto dand1...@yahoo.com wrote: Hi, On Jessie with version 0.7.9-5 I still have to manually add i2c-dev to /etc/modules to get the keyboard backlight working. You mentionned earlier working on a patch. Can you prepare something for udev ? Thanks.
Bug#203716: [bug #33838] want a way to turn off verbosity but still have a progress bar
Update of bug #33838 (project wget): Status:None = Fixed Open/Closed:Open = Closed Release:1.12 = 1.16 ___ Reply to this item at: http://savannah.gnu.org/bugs/?33838 ___ Message sent via/by Savannah http://savannah.gnu.org/
Bug#790523: [bug #45443] http_proxy variable should also work for capitalized HTTP_PROXY
tags 790523 + wontfix thanks Hello, upstream will not fix this: Am Freitag, den 14.08.2015, 08:58 + schrieb Tim Ruehsen: Update of bug #45443 (project wget): Status:None = Wont Fix Assigned to:None = rockdaboot ___ Follow-up Comment #1: I cite Daniel Stenberg (curl maintainer/developer) from the mailing list bug-w...@gnu.org, Tue, 30 Jun 2015 11:20:28 +0200 (CEST): The reason some tools don't accept HTTP_PROXY and only http_proxy is that the CGI interface from back in the old days provide headers from the incoming request to the CGI program prefixed with HTTP_. Thus, running a CGI script from a server, an incoming Proxy: header (which normally doesn't do anything) would be sent to the program as HTTP_PROXY, leading to confusions or in the worst case some sort of attack. The CGI interface is an ancient thing, probably boardering to extinction. Still it is out there and some such CGIs probably use wget. Incidently, curl also only accepts the lower case version of this environment variable and I believe it goes for some other related tools as well. ___ Reply to this item at: http://savannah.gnu.org/bugs/?45443 -- Noël Köthe noel@ ebian.org Debian GNU/Linux, www.debian.org
Bug#794321: codespell manpage: inconsistent formatting of options
Hi Jakub! This inconsistency comes from using the combination of python's argparse and help2man. The alternative would be to generate it once and fix the errors, but than additionally options might be out of sync with the program. Using sed to fix the errors would make the manpage creation kind of complicated. What do you think? How could we best fix the error? Thanks and Greetings Peter
Bug#795506: alsa-utils: mute on change from headphone to speaker
Package: alsa-utils Version: 1.0.29-1 Severity: normal Dear Maintainer, when i change audio output from headphone to speakers it usually leads to mute the sound and i need to manually change it from alsamixer. Regards -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-1-amd64 (SMP w/2 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) Versions of packages alsa-utils depends on: ii kmod21-1 ii libasound2 1.0.29-1 ii libc6 2.19-19 ii libncursesw55.9+20150516-2 ii libsamplerate0 0.1.8-8 ii libtinfo5 5.9+20150516-2 ii lsb-base4.1+Debian13+nmu1 ii whiptail0.52.18-1 alsa-utils recommends no packages. alsa-utils suggests no packages. -- no debconf information
Bug#795505: selinux-basics: reccommends a non-existant package
Package: selinux-basics Version: 0.5.2 Severity: grave Tags: security Justification: renders package unusable Either instructions for setting up SELinux(enabled by default on Fedora) are wrong and need to be changed or selinux-policy-default package needs to be built for debian as a whole. Seems no distro has this package according to a web package search but setting up SELinux seems to depend on it. Did the policies get put into another package? They are pretty much required to setup SELinux. Tomoyo and apparmor may work as alternates but the reccommended course of action is SELinux.It is also more common method. There is also no reason to not have it installed and basic config setup by default(either on install media or live media). Ignore this hardening reccomendation at your own peril. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages selinux-basics depends on: ii checkpolicy 2.3-1 ii policycoreutils 2.3-1 pn python:any none ii selinux-utils2.3-2+b1 Versions of packages selinux-basics recommends: pn selinux-policy-default none ii setools 3.3.8-3.2 Versions of packages selinux-basics suggests: pn logchecknone pn syslog-summary none -- no debconf information
Bug#795504: RM: kde-style-polyester -- ROM; dead upstream, incompatible with Plasma 5
Package: ftp.debian.org Severity: normal Hi, Please remove the kde-style-polyester source and binary package. It's dead upstream and incompatible with KDE Plasma 5. Thanks, Felix
Bug#778594: [git-buildpackage/master] import-orig: Add new --merge-mode=replace
tag 778594 pending thanks Date: Fri Aug 14 11:08:40 2015 +0200 Author: Guido Günther a...@sigxcpu.org Commit ID: 035b179b047951f6eb354e748ea0daf7a3221cb9 Commit URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=035b179b047951f6eb354e748ea0daf7a3221cb9 Patch URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=035b179b047951f6eb354e748ea0daf7a3221cb9 import-orig: Add new --merge-mode=replace This allows one to not merge upstream versions into the debian branch but rather replace the content of the debian branch and only preserve the debian/ dirs content. Closes: #778594 A snapshot build including this change will be available at http://honk.sigxcpu.org:8001/job/git-buildpackage/
Bug#792692: [git-buildpackage/master] buildpackage: in overlay mode remove debian/ from unpacked tarball
tag 792692 pending thanks Date: Fri Aug 14 17:25:04 2015 +0200 Author: Guido Günther a...@sigxcpu.org Commit ID: 3d86432d4509e5b30f2c0f5e2fa303630e5017c9 Commit URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=3d86432d4509e5b30f2c0f5e2fa303630e5017c9 Patch URL: https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=3d86432d4509e5b30f2c0f5e2fa303630e5017c9 buildpackage: in overlay mode remove debian/ from unpacked tarball We don't have a way to influence the upstream tarball in overlay mode so remove debian/ after unpack if the source format expects this. Closes: #792692 A snapshot build including this change will be available at http://honk.sigxcpu.org:8001/job/git-buildpackage/
Bug#795510: llvm-toolchain-snapshot FTBFS, apparent version number handling issues.
Package: llvm-toolchain-snapshot Version: 1:3.7~svn239806-1 Severity: serious dpkg-buildpackage: host architecture arm64 fakeroot debian/rules clean dpkg-query: no packages found matching g++-5.2 dpkg: error: --compare-versions takes three arguments: version relation version --snip many similar errors-- dpkg-architecture: warning: couldn't determine gcc system type, falling back to default (native compilation) Using gcc: gcc-5.2 -v make[1]: gcc-5.2: Command not found make[1]: *** [override_dh_auto_configure] Error 127 AIUI from gcc/g++ 5 onwards the package names and binary names only use the first component of the version numer (where before they used the first two components). I belive this is due to a change in versioning practices upstream.
Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt
On Thu, Aug 13, 2015 at 03:52:11PM +0200, intrigeri wrote: I've prepared an initial, untested packaging of vagrant-libvirt and its only missing dependency: https://git-tails.immerda.ch/intrigeri/vagrant-libvirt https://git-tails.immerda.ch/intrigeri/ruby-fog-libvirt It would not be reasonable of me to add these packages to my plate, but perhaps the pkg-ruby-extras team could? Awesome, if nobody beats me to it I could take a look at them and upload them soon. Thanks! -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#795363: more debcherry noise
While experimenting with debcherry for use in pkg-perl and discussing things with David, I noticed two related sources of noise in the generated patches: - the Subject line contains [PATCH] with a number (like [PATCH 2/3]), which causes noise in all patches if another patch is added or dropped. This is simple to fix by adding --no-numbered to the two lower calls of git format-patch - the diff contains an index line with short hashes from the temporary repository (meaningless, volatile). I'm currently filtering it out with the line next if /^diff --git a/../^--- a/ and /^index /; in a post-processing script that adds the content of git notes to the generated patches. Florian
Bug#795507: installation-reports: Fans are running at 90% for 5-10 minutes after boot
Package: installation-reports Severity: important Dear Maintainer, After installing Jessie laptop fans are running crazy for 5-10 minutes and then everything is back to normal. I have installed Linux-Firmware as suggested but for some reason the problem exists. I have done all the suggestions (clean dust, powertop modification etc) but result to nothing. -- Package-specific info: Boot method: CD Image version: debian-testing-amd64-DVD-1.iso Date: Date and time of the install Machine: HP LAPTOP Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=9 (stretch) - installer build 20150718 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux bagginsDK 4.0.0-2-amd64 #1 SMP Debian 4.0.8-1 (2015-07-11) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3076] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3074] lspci -knn:
Bug#795515: toxiproxy: Uses non-deterministic timing information in testsuite
Package: toxiproxy Version: 1.2.1+dfsg1-1 Severity: serious Dear Maintainer, toxiproxy's testsuite appears to use method timing information -- ie. the time taken for method to execute -- as part of an actual testcase: === RUN TestLatencyToxicBandwidth --- FAIL: TestLatencyToxicBandwidth (0.13s) toxic_test.go:80: [Latency toxic bandwidth] Time was more than 12ms off: got 25.093814ms expected 0 This makes the success of the package build non-determinstic, hence the RC-severity. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-