Bug#861870: Requesting unblock
Hi Tomasz, GitLab package co-maintainer here. We will be uploading the fix to unstable and requesting an unblock, hopefully by Monday. In the mean time, there is already an unblock request open[0] for the latest version in unstable, 8.13.11+dfsg1-5. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861293 Regards, Balasankar C signature.asc Description: PGP signature
Bug#858377: libblkmaker outdated in Debian
BFGMiner should work just fine with the git version of libblkmaker, and doesn't require libblkmaker to work correctly in many common cases. The simplest solution would be to simply bump libblkmaker.
Bug#859660: Bug#859660: artemis running issue
Control: severity -1 important Control: tags -1 moreinfo Hi Tony, On Fri, Apr 28, 2017 at 08:11:52AM -0700, tony mancill wrote: > This does sound like an issue we had in the past with jarwrapper and > binfmt-support. IIRC, Colin Watson was able to track down the source of > this, but at the moment I cannot locate the details of that exchange. It > was something along the lines of there being multiple interpreters > registered for the given binfmt. Thanks for ths info. > If we know that the user's kernel supports binfmt_misc, then we should be > able to figure out what's happening. The output of "sudo update-binfmts > --display jarwrapper" (should point to jarwrapper) and "sudo update-binfmts > --display jar" (should point to jexec) might be informative. I'll try to > reproduce locally and report back. I've reduced the severity of this bug from grave to important and have added the tag moreinfo. Jerome, could you please provide the said info? Kind regards Andreas. -- http://fam-tille.de
Bug#861263: debian-installer: zfs support
On 06/05/2017, Nicholas D Steeveswrote: > I would recommend the second of the following options: > > 1. Install using the non-free media with "Advanced options" -> "Expert > install" > 2. Install using the non-free media, then cleanup [...] > > It's faster than an "Advanced > options" -> "Expert install", where I believe it is also possible to > install a system which pulls uniquely from main and contrib. Thank you for reminding me of the existence of the "Expert install" option in the Debian Installer! :) My understanding of this feature request (#861263) is that it would be satisfied when a Debian Installer exists in which: the user can install Debian by simply click through the ncurses interface pretty much as usual, but in addition to the current guided[1] and manual[2] partitioning options, the user would have the option to select guided or manual partitioning with ZFS. Ideally, that would also include the option for encrypted ZFS using either a LUKS container or native ZFS encryption.[3] So, between your two options, I think the "Expert install" would probably be a better fit for resolving this feature request. However, although "Expert install" would be appropriate, it might not be necessary to use an unofficial installer. See below. On 05/05/2017, Ben Hutchings wrote: > On Fri, 2017-05-05 at 14:26 +0100, Sam Kuper wrote: >> If the Debian Installer were instead to ship with, or to download at >> runtime, the ZFS on Linux source code, would that be acceptable from a >> licensing standpoint? > > I imagine this would be acceptable (though not in the default > installer, which only uses and installs packages from main). > > [...] there is already an (officially unofficial) installer that > includes non-free firmware. I have just run an *official* Jessie NetInst CD, using "Expert install" mode. Fairly late in the process, there is a step titled "Configure the package manager".[4] This step asks the user if they want software from "non-free" and/or "contrib" to be available to the system. So, it seems that there is no need in principle to use an unofficial installer just to be presented with the option to enable "contrib". One piece of work that would need to be done to the Debian Installer to enable it to download, compile and run ZFS before partitioning the HDD/SSD, is for the "Configure the package manager" step to be moved to an earlier point in the installation process. Let me explain. In my Jessie NetInst CD, the "Configure the package manager" step occurs *after* the Debian Installer has partitioned the drive and installed Debian to it: too late to make a difference, from the perspective of enabling ZFS root! I would suggest that the "Configure the package manager" step should be placed immediately *before* the "Detect disks" step. This means the "Configure the package manager" step would have to be modified. Rather than straight away writing to /etc/apt/sources.list and handing over to the following step (as it currently seems to do), it would instead: - record the user's selections to memory; - enable guided and manual ZFS options to become available in the "Partition disks" step (but only if the user chose to enable "contrib"); and - write the user's selections to /etc/apt/sources.list *after* the target drive has been formatted and populated. Additionally, of course, the Debian Installer would need to have code incorporated to perform the download-compile-run steps for ZFS. I can see that these are not trivial changes, but I also can see no reason in principle why they should not be made to the Debian Installer at some point during the Stretch lifecycle. Even if they end up taking many months to bring up to release quality, they would be very valuable additions to the Debian Installer. I would be very grateful if the "wontfix" label could be removed from this feature request. Thanks again to both of you; and Ben, I really did mean no offence to you by mentioning Moglen. I'm sorry if that came across as supercilious. I really was just trying to explain the basis of my understanding. [1] https://www.debian.org/releases/stable/amd64/ch06s03.html.en#partman-auto [2] https://www.debian.org/releases/stable/amd64/ch06s03.html.en#partman-manual [3] AFAIK, native ZFS encryption with Linux is not stable enough to make sense for a stable distribution. Until it is, ZFS-on-LUKS seems to be the best substitute. [4] https://www.debian.org/releases/stable/amd64/ch06s03.html.en#apt-setup
Bug#861938: XeTeX chokes if fontconfig returns a WOFF file to them
Package: fontconfig Version: 2.11.94-0ubuntu1.1 Severity: normal Dear Maintainer, I have seen reports of problems on XeTeX on Ubuntu not handling WOFF files, both told to me in person and also on the web [1]. The expectation was if a font name (not a pathname to a font) is given to XeTeX, fontconfig will return a .ttf or .otf font that XeTeX can use. If a WOFF font is returned, XeTeX aborts with an error message. Here are the steps I took to see this. $ sudo apt-get install texlive texlive-binaries texlive-xetex $ sudo apt-get install fonts-sil-andikanewbasic Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: fonts-sil-andikanewbasic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,033 kB of archives. After this operation, 2,136 kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 fonts-sil-andikanewbasic all 5.500-1 [1,033 kB] Fetched 1,033 kB in 1s (723 kB/s) Selecting previously unselected package fonts-sil-andikanewbasic. (Reading database ... 241863 files and directories currently installed.) Preparing to unpack .../fonts-sil-andikanewbasic_5.500-1_all.deb ... Unpacking fonts-sil-andikanewbasic (5.500-1) ... Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... Setting up fonts-sil-andikanewbasic (5.500-1) ... $ cat fontconfig.tex \font\text="Andika New Basic/OT" at 12pt \nopagenumbers \obeylines \text Now is the time for all good men to come to the aid of their country. \bye $ xetex fontconfig.tex This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) (preloaded format=xetex) restricted \write18 enabled. entering extended mode (./fontconfig.tex [1] xdvipdfmx:fatal: Cannot proceed without the font: /usr/share/fonts/woff/andikanewbasic/AndikaNewBasic-R.woff Output file removed. ) Error 256 (driver return code) generating output; file fontconfig.pdf may not be valid. Transcript written on fontconfig.log. $ cat fontconfig.log This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) (preloaded format=xetex 2017.5.5) 5 MAY 2017 21:52 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **fontconfig.tex (./fontconfig.tex [1] ) Error 256 (driver return code) generating output; file fontconfig.pdf may not be valid. $ sudo mv /usr/share/fonts/woff/andikanewbasic/AndikaNewBasic-R.woff /usr/share/fonts/woff/andikanewbasic/AndikaNewBasic-R.woff_ $ fc-cache $ xetex fontconfig.tex This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) (preloaded format=xetex) restricted \write18 enabled. entering extended mode (./fontconfig.tex [1] ) Output written on fontconfig.pdf (1 page). Transcript written on fontconfig.log. $ cat fontconfig.log This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) (preloaded format=xetex 2017.5.5) 5 MAY 2017 21:54 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **fontconfig.tex (./fontconfig.tex [1] ) Output written on fontconfig.pdf (1 page). The above steps where run on Ubuntu Xenial 16.04.2 amd64 texlive-binaries 2015.20160222.37495-1 texlive-xetex 2015.20160320-1 -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-77-generic (SMP w/1 CPU core) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fontconfig depends on: ii dpkg 1.18.4ubuntu1.2 ii fontconfig-config 2.11.94-0ubuntu1.1 ii libc6 2.23-0ubuntu7 ii libfontconfig1 2.11.94-0ubuntu1.1 ii libfreetype6 2.6.1-0.1ubuntu2.2 fontconfig recommends no packages. fontconfig suggests no packages. -- debconf-show failed A fix is to not install WOFF files below /usr/share/fonts/, as fontconfig looks at this directory. I tested this by renaming the WOFF file, and then xetex ran correctly. However, the Debian Pkg-fonts-devel list feels that applications such as XeTeX should filter out fontconfig returning a WOFF file[2] or maybe fontconfig should not return WOFF files[3], even if they are installed under /usr/share/fonts/. The author of both XeTeX and the WOFF spec, Jonathan Kew, feels that the installed WOFF files should not be found by fontconfig[4]. I wonder if there has been some confusion in these discussions between the use of fonts in a desktop GUI environment, and for use on a server. It seems to me that the server environment is really two different cases, one where a server might be used XeTeX or CUPS to provide a service (as mentioned in [5]) or an HTTP server serving a WOFF font to a client. IIUC, WOFF files were designed only to be used by a HTTP server. Maybe a
Bug#861937: preload fails due to missing preload.state file
Package: preload Version: 0.6.4-2+b1 Severity: important Dear Maintainer, I installed preload and checked the status of preload.service using systemctl and it was running. I checked /var/log/preload.log and found that it was complaining about being unable to access /var/lib/preload/preload.state. As this file did not exist, I created it using sudo touch. Then I restarted preload.service using systemctl and rechecked the log at which point preload started working. I would request that the package be checked as it is clearly not creating the preload.state file which is essential for it to work. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages preload depends on: ii libc6 2.24-10 ii libglib2.0-0 2.50.3-2 preload recommends no packages. preload suggests no packages. -- no debconf information
Bug#861838: ldap-utils: ldapsearch and ldapwhoami cannot connect to ldaps server
Control: tag -1 = confirmed Control: found -1 2.4.44+dfsg-4 Control: retitle -1 long list of acceptable CA names breaks libldap OK, I have reproduced this. On Debian: apt-get install ldap-utils slapd ssl-cert adduser openldap ssl-cert sed -i 's,^SLAPD_SERVICES=.*,SLAPD_SERVICES="ldap:// ldapi:// ldaps://",' /etc/default/slapd service slapd restart ldapmodify -H ldapi:// -Y EXTERNAL << EOF dn: cn=config add: olcTLSVerifyClient olcTLSVerifyClient: allow - add: olcTLSCACertificateFile olcTLSCACertificateFile: /etc/ssl/certs/ca-certificates.crt - add: olcTLSCertificateFile olcTLSCertificateFile: /etc/ssl/certs/ssl-cert-snakeoil.pem - add: olcTLSCertificateKeyFile olcTLSCertificateKeyFile: /etc/ssl/private/ssl-cert-snakeoil.key EOF # prints a long list of acceptable CA names openssl s_client -CAfile /etc/ssl/certs/ssl-cert-snakeoil.pem -connect localhost:636 -showcerts # should succeed, but fails LDAPTLS_CACERT=/etc/ssl/certs/ssl-cert-snakeoil.pem ldapwhoami -ZZ -x I should note that I rebuilt libldap and clients against OpenSSL and the same works. However, gnutls-cli also works for me, so this problem appears to be specific to libldap's GnuTLS support.
Bug#861936: Subject: RFS: golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for package "golang-github-seccomp-libseccomp-golang" * Package name: golang-github-seccomp-libseccomp-golang Version : 0.0~git20150813.0.1b506fc-2 Section : devel It builds those binary packages: golang-github-seccomp-libseccomp-golang-dev - golang bindings for libseccomp To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-seccomp-libseccomp-golang Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-seccomp-libseccomp-golang/golang-github-seccomp-libseccomp-golang_0.0~git20150813.0.1b506fc-2.dsc tested to build on DoM: http://debomatic-i386.debian.net/distribution#unstable/golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2/buildlog http://debomatic-amd64.debian.net/distribution#unstable/golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2/buildlog Commits are pushed to mentors branch: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-seccomp-libseccomp-golang.git -b mentors Changes since the last upload: golang-github-seccomp-libseccomp-golang (0.0~git20150813.0.1b506fc-2) unstable; urgency=medium * Team upload. [ Paul Tagliamonte ] * Use a secure transport for the Vcs-Git and Vcs-Browser URL [ Roger Shimizu ] * debian/patches: - Add a patch to fix FTBFS on 32-bit platforms. Thanks to upstream author Matthew Heon(Closes: #860618). Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpQVYr5ky90n.pgp Description: PGP signature
Bug#860618: golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test
releasing commit pushed to branch mentors. package is uploaded to mentors for RFS. tested to build on DoM: http://debomatic-i386.debian.net/distribution#unstable/golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2/buildlog http://debomatic-amd64.debian.net/distribution#unstable/golang-github-seccomp-libseccomp-golang/0.0~git20150813.0.1b506fc-2/buildlog Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpiQF7UY67r5.pgp Description: PGP signature
Bug#861935: mirror listing update for debian.redlibre.cl
Package: mirrors Severity: minor User: mirr...@packages.debian.org Usertags: mirror-list Submission-Type: update Site: debian.redlibre.cl Type: leaf Archive-architecture: amd64 armhf i386 mips mipsel powerpc s390x Archive-http: /debian/ Archive-upstream: mirrors.kernel.org Updates: four Maintainer: Pablo UmanzorCountry: CL Chile Location: Santiago - Las Condes Comment: hello! we've added new architectures Trace Url: http://debian.redlibre.cl/debian/project/trace/ftp-master.debian.org Trace Url: http://debian.redlibre.cl/debian/project/trace/debian.redlibre.cl
Bug#860618: Pending fixes for bugs in the golang-github-seccomp-libseccomp-golang package
tag 860618 + pending thanks Some bugs in the golang-github-seccomp-libseccomp-golang package are closed in revision 3a57e3da7652c610f631d5bf62d7448046fd66e2 in branch 'master' by Roger Shimizu The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-seccomp-libseccomp-golang.git/commit/?id=3a57e3d Commit message: debian/patches: Add a patch to fix FTBFS on 32-bit platforms Thanks to upstream author Matthew HeonCloses: #860618
Bug#861934: tasksel: Please update default Chinese font dependency
Package: tasksel Version: 3.39 Severity: wishlist Tags: l10n According to the dicision made by the Chinese Team [1], we are seeking the switch of default Chinese fonts. The first (and the most important) change would be the switch from fonts-wqy-* to Noto CJK fonts (or Source Han Sans) for Sans fonts. The patch is provided as below. This task should at least be finished in the Buster cycle so the severity is kept as "wishlist" now. Will bump severity accordingly with the development pace of Buster cycle. P.S. I added "Recommends: fcitx-frontend-qt5" as well for task-chinese-s-kde- desktop since Qt5 is replacing Qt4. * * * >From cc867eb80c904543c314d4a6ff83482ad5c5c9a2 Mon Sep 17 00:00:00 2001 From: Boyuan Yang <073p...@gmail.com> Date: Sat, 6 May 2017 11:04:07 +0800 Subject: Update Chinese deps for tasksel packages As per the decision of the Chinese Team [1], we are switching default Chinese Sans fonts into Noto Sans CJK. [1]: https://lists.debian.org/debian-chinese-gb/2017/05/msg0.html . Signed-off-by: Boyuan Yang <073p...@gmail.com> --- debian/control | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/debian/control b/debian/control index 2fd82944..d1ae29d9 100644 --- a/debian/control +++ b/debian/control @@ -724,8 +724,7 @@ Recommends: fonts-arphic-ukai, fonts-arphic-uming, fonts-noto, - fonts-wqy-microhei, - fonts-wqy-zenhei, + fonts-noto-cjk, # Software help and localization libreoffice-l10n-zh-cn, libreoffice-help-zh-cn, @@ -735,6 +734,10 @@ Recommends: # poppler-data is needed to display # Chinese on poppler applications. poppler-data +Suggests: +# Deprecated font option, downgraded to suggestion + fonts-wqy-zenhei, + fonts-wqy-microhei, Package: task-chinese-s-kde-desktop Architecture: all @@ -744,6 +747,7 @@ Depends: ${misc:Depends}, Recommends: kde-l10n-zhcn, fcitx-frontend-qt4, + fcitx-frontend-qt5, kde-config-fcitx Package: task-chinese-t @@ -770,14 +774,17 @@ Recommends: fonts-arphic-uming, # seems openjdk needs this to display Chinese. fonts-noto, - fonts-wqy-microhei, - fonts-wqy-zenhei, + fonts-noto-cjk, libreoffice-l10n-zh-tw, libreoffice-help-zh-tw, firefox-esr-l10n-zh-tw | firefox-l10n-zh-tw, # poppler-data is needed to display # Chinese on poppler applications. poppler-data +Suggests: +# Deprecated font option, downgraded to suggestion + fonts-wqy-zenhei, + fonts-wqy-microhei, Package: task-chinese-t-kde-desktop Architecture: all -- 2.11.0 [1] https://lists.debian.org/debian-chinese-gb/2017/05/msg0.html -- Sincerely, Boyuan Yang -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tasksel depends on: ii apt 1.4.1 ii debconf [debconf-2.0] 1.5.60 ii liblocale-gettext-perl 1.07-3+b1 ii perl-base 5.24.1-2 ii tasksel-data3.39 tasksel recommends no packages. tasksel suggests no packages. -- debconf information: tasksel/title: tasksel/first: tasksel/desktop: tasksel/tasks:
Bug#861933: gnome-shell-timer: changing defaults or presets does not change menu until GNOME shell restarts
Package: gnome-shell-timer Version: 0.3.12+20140924-5 Severity: normal Changing default timer values (Manual tab in configuration) or adding, changing or removing presets (Presets tab in configuration) does not change the menu in the GNOME shell until the shell is restarted. -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell-timer depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii gnome-shell 3.22.3-3 pn python:any gnome-shell-timer recommends no packages. gnome-shell-timer suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#861932: tasksel: Please update Vcs-* fields in debian/control
Package: tasksel Version: 3.39 Severity: minor According to https://lintian.debian.org/tags/vcs-field-not-canonical.html, A patch is provided here to update Vcs-Git and Vcs-Browser fields in debian/control. >From 4c30cefb9f2b186d1ecee102385b66b7266596d0 Mon Sep 17 00:00:00 2001 From: Boyuan Yang <073p...@gmail.com> Date: Sat, 6 May 2017 10:45:24 +0800 Subject: d/control: replace git/http protocol with https; bump Std-Ver --- debian/control | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/debian/control b/debian/control index 2fd82944..4cad7e2e 100644 --- a/debian/control +++ b/debian/control @@ -3,10 +3,10 @@ Section: tasks Priority: optional Maintainer: Debian Install System TeamUploaders: Christian Perrier -Standards-Version: 3.9.5 +Standards-Version: 3.9.8 Build-Depends: po-debconf, debhelper (>= 9), gettext, dpkg-dev (>= 1.9.0) -Vcs-Git: git://git.debian.org/git/tasksel/tasksel.git -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=tasksel/tasksel.git +Vcs-Git: https://anonscm.debian.org/git/tasksel/tasksel.git +Vcs-Browser: https://anonscm.debian.org/git/tasksel/tasksel.git Package: tasksel Section: admin -- 2.11.0 -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tasksel depends on: ii apt 1.4.1 ii debconf [debconf-2.0] 1.5.60 ii liblocale-gettext-perl 1.07-3+b1 ii perl-base 5.24.1-2 ii tasksel-data3.39 tasksel recommends no packages. tasksel suggests no packages. -- debconf information: tasksel/tasks: tasksel/title: tasksel/desktop: tasksel/first:
Bug#861919: fusioninventory-for-glpi: not installable in sid
Hi, On Fri, May 05, 2017 at 10:54:05PM +0200, david hannequin wrote: > Hi, > > Sorry, i no longer maintain this package. And i no longer contribute i > am disappointed with the project. > > Feel free to fix. I am sorry to hear that. Thanks anyway for your reply. -Ralf.
Bug#861931: initramfs-tools: Takes more than 30 seconds longer to boot up
Package: initramfs-tools Version: 0.128 Severity: normal Dear Maintainer, It takes more than 30 seconds longer to boot up with several "Begin: Running /scripts/local-block ... done." messages from initramfs-tools 0.128. Reverting 25837a143420c217416e662771993ca7405cd109 can avoid this problem. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 20M May 6 10:27 /boot/initrd.img-4.11.0-trunk-amd64 -rw-r--r-- 1 root root 19M Apr 26 21:21 /boot/initrd.img-4.9.0-2-amd64 -rw-r--r-- 1 root root 19M May 5 00:39 /boot/initrd.img-4.9.0-3-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.11.0-trunk-amd64 root=UUID=1605c8d8-254d-4ac0-b040-8c3b527e6db3 ro quiet -- resume RESUME=/dev/mapper/sda4_crypt -- /proc/filesystems btrfs vfat ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by fuse 98304 3 rfcomm 77824 2 ctr16384 6 ccm20480 9 cmac 16384 1 bnep 20480 2 binfmt_misc20480 1 ext4 589824 1 jbd2 106496 1 ext4 fscrypto 28672 1 ext4 ecb16384 0 mbcache16384 1 ext4 algif_skcipher 20480 0 af_alg 16384 1 algif_skcipher nls_ascii 16384 1 nls_cp437 20480 1 vfat 20480 1 fat65536 1 vfat dm_crypt 28672 2 arc4 16384 2 dm_mod114688 5 dm_crypt iTCO_wdt 16384 0 iTCO_vendor_support16384 1 iTCO_wdt uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo intel_rapl 20480 0 videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 24576 1 uvcvideo x86_pkg_temp_thermal16384 0 videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2 intel_powerclamp 16384 0 coretemp 16384 0 videodev 167936 3 uvcvideo,videobuf2_core,videobuf2_v4l2 media 40960 2 uvcvideo,videodev kvm_intel 196608 0 kvm 585728 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 btusb 45056 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel16384 1 btusb ghash_clmulni_intel16384 0 bluetooth 544768 31 btrtl,btintel,bnep,btbcm,rfcomm,btusb iwlmvm253952 0 crc16 16384 2 bluetooth,ext4 snd_hda_codec_hdmi 49152 1 mac80211 667648 1 iwlmvm intel_cstate 16384 0 efi_pstore 16384 0 intel_uncore 118784 0 intel_rapl_perf16384 0 iwlwifi 151552 1 iwlmvm joydev 20480 0 evdev 24576 19 snd_hda_codec_conexant24576 1 sg 32768 0 snd_hda_codec_generic69632 1 snd_hda_codec_conexant serio_raw 16384 0 pcspkr 16384 0 efivars20480 1 efi_pstore intel_pch_thermal 16384 0 thinkpad_acpi 86016 1 i915 1257472 16 snd_hda_intel 36864 8 rtsx_pci_ms20480 0 cfg80211 585728 3 iwlmvm,iwlwifi,mac80211 nvram 16384 1 thinkpad_acpi memstick 16384 1 rtsx_pci_ms snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_codec_generic wmi16384 0 rfkill 24576 8 bluetooth,thinkpad_acpi,cfg80211 battery20480 0 ac 16384 0 snd_hda_core 77824 5 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic drm_kms_helper143360 1 i915 snd_hwdep 16384 1 snd_hda_codec snd_pcm 102400 4 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi drm 344064 7 i915,drm_kms_helper snd_timer 32768 1 snd_pcm video 40960 2 thinkpad_acpi,i915 snd77824 25 snd_hda_intel,snd_hwdep,snd_hda_codec_conexant,snd_hda_codec,snd_timer,thinkpad_acpi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_pcm mei_me 40960 0 i2c_algo_bit 16384 1 i915 lpc_ich24576 0 soundcore 16384 1 snd button 16384 1 i915 mei 102400 1 mei_me shpchp 36864 0 parport_pc 28672 0 ppdev 20480 0 lp 20480 0 parport49152 3 lp,parport_pc,ppdev efivarfs 16384 1 ip_tables 24576 0 x_tables 36864 1 ip_tables autofs440960 2 btrfs1077248 1 crc32c_generic 16384 0 xor24576 1 btrfs
Bug#855380: reportbug: UI offers "Back", but doesn't allow to edit the data
Control: severity -1 important Control: found -1 7.1.6 Dear maintainers, This bug is quite problematic IMO because it allows reportbug to get into a state where all useful UI elements are disabled, including the buttons on the final navigation screen (e.g. "Submit the bug report via email"). At this point, reportbug is unusable and all info inputed in the current session is essentially lost to the average user. I found this bug specifically by clicking the "Choose a mailer to edit the report" button on the final navigation screen and then hitting Back. (In my case, I tried that option only to learn that my mail client isn't in the mailers list, and in the process broke the bug reporter!) Best, James signature.asc Description: OpenPGP digital signature
Bug#861930: pidgin: Pidgin sounds causes other applications sounds to jump
Package: pidgin Version: 2.12.0-1 Severity: normal Dear Maintainer, When sounds play in pidgin, the audio playing from youtube in firefox gets suddenly louder for a short duration. Also the pidgin sounds can feel crackly. I don't know if the problem coems from pidgin, pulseaudio, firefox, or somewhere else entirely, but this seems like a good enough place to start. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (650, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pidgin depends on: ii libatk1.0-0 2.22.0-1 ii libc6 2.24-10 ii libcairo2 1.14.8-1 ii libdbus-1-3 1.10.18-1 ii libdbus-glib-1-20.108-2 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype62.6.3-3.2 ii libgadu31:1.12.1-4 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-02.50.3-2 ii libgstreamer1.0-0 1.10.4-1 ii libgtk2.0-0 2.24.31-2 ii libgtkspell02.0.16-1.1 ii libice6 2:1.0.9-2 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libpurple0 2.12.0-1 ii libsm6 2:1.2.2-1+b3 ii libx11-62:1.6.4-3 ii libxss1 1:1.2.2-1 ii perl-base [perlapi-5.24.1] 5.24.1-2 ii pidgin-data 2.12.0-1 Versions of packages pidgin recommends: ii gstreamer1.0-libav 1.10.4-1 ii gstreamer1.0-plugins-base 1.10.4-1 ii gstreamer1.0-plugins-good 1.10.4-1 ii gstreamer1.0-pulseaudio1.10.4-1 Versions of packages pidgin suggests: ii libsqlite3-0 3.16.2-3 -- no debconf information
Bug#861929: furiusisomount: please demote the nautilus dependency
Control: found -1 0.11.3.1~repack1-1 Control: notfound -1 0.11.3.1~repack1-1utopia1 Hi again, Sorry for the noise, but ignore the spurious "0.11.3.1~repack1-1utopia1" version - this happened because I applied the attached patch and rebuilt with a version bump locally. On 05/05/17 06:16 PM, James Lu wrote: > Package: furiusisomount > Version: 0.11.3.1~repack1-1utopia1 > Severity: wishlist > Tags: patch > > Dear maintainer, > > furiusisomount lists nautilus as a dependency, but doesn't actually require it > to work. Please consider demoting nautilus to either suggests or enhances, as > it's otherwise quite inconvenient to use furiusisomount on non-GNOME desktops. > > Best, > James > > > > -- System Information: > Debian Release: 9.0 > APT prefers testing > APT policy: (700, 'testing'), (500, 'unstable-debug'), (500, > 'testing-debug'), (500, 'unstable'), (101, 'experimental') > Architecture: amd64 > (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages furiusisomount depends on: > ii fuseiso20070708-3.2+b1 > ii fuseiso96600.3-1.1+b1 > ii python-glade2 2.24.0-5.1 > ii python-gtk22.24.0-5.1 > pn python:any > > furiusisomount recommends no packages. > > Versions of packages furiusisomount suggests: > ii brasero 3.12.1-4 > pn nautilus > > -- no debconf information > signature.asc Description: OpenPGP digital signature
Bug#861929: furiusisomount: please demote the nautilus dependency
Package: furiusisomount Version: 0.11.3.1~repack1-1utopia1 Severity: wishlist Tags: patch Dear maintainer, furiusisomount lists nautilus as a dependency, but doesn't actually require it to work. Please consider demoting nautilus to either suggests or enhances, as it's otherwise quite inconvenient to use furiusisomount on non-GNOME desktops. Best, James -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (700, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages furiusisomount depends on: ii fuseiso20070708-3.2+b1 ii fuseiso96600.3-1.1+b1 ii python-glade2 2.24.0-5.1 ii python-gtk22.24.0-5.1 pn python:any furiusisomount recommends no packages. Versions of packages furiusisomount suggests: ii brasero 3.12.1-4 pn nautilus -- no debconf information >From b74aa14b58f1852e9cbf8d59ab9e6d8803f44893 Mon Sep 17 00:00:00 2001 From: James LuDate: Fri, 5 May 2017 18:12:31 -0700 Subject: [PATCH] d/control: demote nautilus to suggests --- debian/control | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/debian/control b/debian/control index 35bcde3..cfa6799 100644 --- a/debian/control +++ b/debian/control @@ -18,8 +18,7 @@ Depends: ${python:Depends}, fuseiso9660, python-gtk2, python-glade2, - nautilus -Suggests: brasero +Suggests: brasero, nautilus Description: ISO, IMG, BIN, MDF and NRG image management utility Furius ISO Mount is a simple application for mounting ISO, IMG, BIN, MDF and NG image files even without burning them to disk. -- 2.11.0
Bug#861928: lv2 plugin directory
Package: amsynth Version: 1.6.4-1 Dear maintainers, This package installes lv2 plugins to /usr/lib/x86_64-linux-gnu/lv2, but Ardour can not scan the directory except setting "LV2_PATH" environment variable. Considering that Debian Policy says "a program must not depend on environment variables to get reasonable defaults", and that most of other packages install lv2 plugins to /usr/lib/lv2 at this moment, I think it's better to install the plugin of this pacakge also to there.
Bug#861927: How to change /proc mount options is undocumented
Package: base Severity: normal There is no documentation within the procps package or the wiki on how to modify /proc mount options on Jessie. There is no /proc entry in /etc/fstab. The correct way appears to be to add the /proc entry to fstab. Please add documentation that describes the official way to modify /proc mount options. This will be especially important once /proc is being mounted with hidepid by default, as a lot of users will probably want to know how to go back to the old behavior. root@localhost /usr/share/doc/procps# zgrep -i hidepid * root@localhost /usr/share/doc/procps# zgrep -i hidepid */* root@localhost /usr/share/doc/procps# zgrep -i mount * changelog.Debian.gz:before /usr/ is mounted (Closes: #548802). changelog.Debian.gz: * Doesn't segfault if /proc not mounted Closes: #172735 changelog.Debian.gz: * - stop crashes with unmounted /proc Closes: #63512, #55177 changelog.Debian.gz: * Stop crashes with umounted /proc Closes: #63512, #55177 changelog.gz: libproc-ng: prettyfy proc mount messages changelog.gz:ps: detect broken OS install w/o /proc mounted#172735 README.top.gz: . 378695, seg fault if "/proc" is not mounted TODO.gz:code as much as the kernel can support. Make sure that memory amounts are in root@localhost /usr/share/doc/procps# zgrep -i fstab * root@localhost /usr/share/doc/procps#
Bug#861263: debian-installer: zfs support
On 5 May 2017 at 15:27, Sam Kuperwrote: > On 05/05/2017, Ben Hutchings wrote: >>On Fri, 2017-05-05 at 19:50 +0100, Sam Kuper wrote: > >>> 2. Add ZFS to a Debian Installer that is not the *default* Debian >>> Installer. Does Debian distribute such an installer, to which the >>> facility to compile and run ZFS could be added? >> >> Yes, there is already an (officially unofficial) installer that >> includes non-free firmware. > > Thanks for the information. Can the non-free aspect of that installer > be disabled by the user during installation? If not, then it would be > no use to anyone I know who would be interested in running ZFS under > Debian. That is because a key reason to use Debian in preference to > other distros is that Debian's blob-free kernel and DFSG-compliant > main and contrib repositories make it easy to avoid installing > non-free software. If a person doesn't mind the risk of installing > non-free firmware then they may as well just skip Debian and use > Ubuntu or FreeBSD instead, which ship with ZFS in the installer by > default. > I would recommend the second of the following options: 1. Install using the non-free media with "Advanced options" -> "Expert install" 2. Install using the non-free media, then cleanup #!/bin/sh apt-get install aptitude sed -i 's/ non-free//' /etc/apt/sources.list apt-get update aptitude search ?obsolete -F '%p' --disable-columns \ | apt-get purge ...and the non-free packages should be gone. And if you don't want aptitude you can purge that too. It's faster than an "Advanced options" -> "Expert install", where I believe it is also possible to install a system which pulls uniquely from main and contrib. There are a more reasons to use Debian than just default package selection... eg: updates policy, minimal sysadmin headaches, smooth upgrades even from major version to major version, very high quality packaging standards, etc. These are pragmatic reasons to prefer Debian. In my opinion embracing CDDL constitutes ideological compromise, because it forbids "mixing" with with GPL--the most socioally conscious and not neoliberal license. And if Debian isn't 'pure' enough, there are always these: https://www.gnu.org/distros/free-distros.html Cheers, Nicholas
Bug#861926: jessie-pu: package php-tcpdf/6.0.093+dfsg-1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu I request permission to upload a fix of package php-tcpdf to fix security bug CVE-2015-3935 #814030 https://sourceforge.net/p/tcpdf/bugs/1005/ Fix is as simple as the following patch. Non regression tested with success on package "dolibarr" and "phpmyadmin". Description: Set default value of K_TCPDF_CALLS_IN_HTML to false. Author: Laurent DestailleurForwarded: not-needed Last-Update: 2013-07-29 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ --- a/config/tcpdf_config.php +++ b/config/tcpdf_config.php @@ -210,7 +210,7 @@ * If true allows to call TCPDF methods using HTML syntax * IMPORTANT: For security reason, disable this feature if you are printing user HTML content. */ -define('K_TCPDF_CALLS_IN_HTML', true); +define('K_TCPDF_CALLS_IN_HTML', false); /** * If true and PHP version is greater than 5, then the Error() method throw new exception instead of terminating the execution. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-46-generic (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#712612: gcr: diff for NMU version 3.20.0-5.1
Am 06.05.2017 um 00:00 schrieb Christoph Biedl: > Control: tags 712612 + patch > Control: tags 712612 + pending > > Chris Lamb wrote... > there are two files under a BSD license in build/valgrind/*. In addition the ocumentation has its own license in docs/reference/COPYING. > > Seems the license is rather bzip, at least it matches > https://spdx.org/licenses/bzip2-1.0.5.html > >>> Let's turn this into a bug report, so this issue is not forgotten. >> >> (June 2013). Raising to RC to ensure this gets fixed :) > > So here we go: > > Dear maintainer, > > I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to > DELAYED/5 will follow in a few hours. Please feel free to tell me if I > should delay it longer. > Seems to be missing doc/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#861925: cron-apt: Consider cooperating with apt
Package: cron-apt Severity: normal APT already provides a carefully planned cron job and systemd timers that do careful things like spreading updates around the entire day, not blocking cron jobs by sleeping (if using systemd) and perform unattended upgrades using unattended-upgrades. This is used by default in all Ubuntu installations. It would be better to work on the apt one together instead of having two cron jobs that each have their own shortcomings (maybe we can add some hooks to the apt cron job / systemd timers?). -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500, 'testing-proposed-updates'), (500, 'buildd-unstable'), (500, 'testing'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you.
Bug#861263: debian-installer: zfs support
On 05/05/2017, Ben Hutchingswrote: > I shall not share my opinion of Eben Moglen, because I don't want to > get sued. But I would say that "Eben Moglen says X" is not going to > convince me of X. > > And, the FTP team has made its decision. > > I'm not going to argue this further. Apologies if I offended you. I wasn't trying to argue the merits of the FTP team's decision (which I respect and agree with!), or of your opinion about distributing ZFSonLinux binaries. I was just trying to explain the background to my question. I would be very grateful if you (or anybody else with the relevant knowledge) would answer the question I posted: Does Debian distribute a Debian Installer that will (either by default, or at the user's request) install source or binary packages from no repositories other than "main" and "contrib"? If so, is there any reason in principle why that installer could not in future be distributed with the capability to (download and) compile and run ZFS, and to provide the user with the option to install Debian onto a ZFS root partition?
Bug#702976: fixed in xautolock 1:2.2-5
FWIW I fixed this upstream three years ago. I know Wheezy was affected, but the version of Epiphany in Jessie should be fine. (That said, I don't recommend using the version of Epiphany in Stretch, let alone Jessie.)
Bug#712612: gcr: diff for NMU version 3.20.0-5.1 (was: Incomplete debian/copyright)
Control: tags 712612 + patch Control: tags 712612 + pending Chris Lamb wrote... > > > there are two files under a BSD license in build/valgrind/*. In addition > > > the ocumentation has its own license in docs/reference/COPYING. Seems the license is rather bzip, at least it matches https://spdx.org/licenses/bzip2-1.0.5.html > > Let's turn this into a bug report, so this issue is not forgotten. > > (June 2013). Raising to RC to ensure this gets fixed :) So here we go: Dear maintainer, I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to DELAYED/5 will follow in a few hours. Please feel free to tell me if I should delay it longer. Regards. diff -Nru gcr-3.20.0/debian/changelog gcr-3.20.0/debian/changelog --- gcr-3.20.0/debian/changelog 2017-02-05 12:01:17.0 +0100 +++ gcr-3.20.0/debian/changelog 2017-05-05 23:37:29.0 +0200 @@ -1,3 +1,10 @@ +gcr (3.20.0-5.1) unstable; urgency=high + + * Non-maintainer upload. + * Fix copyright attribution for the valgrind files. Closes: #712612 + + -- Christoph BiedlFri, 05 May 2017 23:37:29 +0200 + gcr (3.20.0-5) unstable; urgency=medium * Brown paper bag release. diff -Nru gcr-3.20.0/debian/copyright gcr-3.20.0/debian/copyright --- gcr-3.20.0/debian/copyright 2016-05-26 23:42:36.0 +0200 +++ gcr-3.20.0/debian/copyright 2017-05-05 23:35:57.0 +0200 @@ -26,3 +26,39 @@ On Debian systems, the complete text of the GNU Library General Public License version 2.1 can be found in "/usr/share/common-licenses/LGPL-2.1". + +Files: build/valgrind/* +Copyright: 2000-2013 Julian Seward +License: bzip2-1.0.5 + +License: bzip2-1.0.5 + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + . + 1. Redistributions of source code must retain the above copyright +notice, this list of conditions and the following disclaimer. + . + 2. The origin of this software must not be misrepresented; you must +not claim that you wrote the original software. If you use this +software in a product, an acknowledgment in the product +documentation would be appreciated but is not required. + . + 3. Altered source versions must be plainly marked as such, and must +not be misrepresented as being the original software. + . + 4. The name of the author may not be used to endorse or promote +products derived from this software without specific prior written +permission. + . + THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS + OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY + DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE + GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS + INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, + WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING + NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. signature.asc Description: Digital signature
Bug#861263: debian-installer: zfs support
On Fri, 2017-05-05 at 22:52 +0100, Sam Kuper wrote: > On 05/05/2017, Ben Hutchingswrote: > > On Fri, 2017-05-05 at 21:40 +0100, Sam Kuper wrote: > > > I am not sure why you say that ZFSonLinux binaries are non-free. > > > Please could you explain? > > > > I was referring specifically to the binary kernel modules, which > > have a > > mixture of CDDL and GPLv2 code. These licences are incompatible so > > the > > binaries cannot be distribured, thus are non-free. > > I see. Thanks for explaining your view. > > Eben Moglen's take is more nuanced: [...] I shall not share my opinion of Eben Moglen, because I don't want to get sued. But I would say that "Eben Moglen says X" is not going to convince me of X. And, the FTP team has made its decision. I'm not going to argue this further. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#861263: debian-installer: zfs support
P.S. Ben, thank you again for taking the time on this. It is providing a great deal of clarity to me, and I hope that other people who also desire a ZFS-capable Debian Installer will also find it helpful.
Bug#861924: matrix-synapse: [INTL:fr] French debconf translation
Package: matrix-synapse Severity: wishlist Tags: patch l10n Hi! Please find attached the french translation, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. Kind Regards jipege fr.po.gz Description: application/gzip
Bug#861263: debian-installer: zfs support
On 05/05/2017, Ben Hutchingswrote: > On Fri, 2017-05-05 at 21:40 +0100, Sam Kuper wrote: >> I am not sure why you say that ZFSonLinux binaries are non-free. >> Please could you explain? > > I was referring specifically to the binary kernel modules, which have a > mixture of CDDL and GPLv2 code. These licences are incompatible so the > binaries cannot be distribured, thus are non-free. I see. Thanks for explaining your view. Eben Moglen's take is more nuanced: "If [Linux kernel copyright holders] prefer the literal meaning to the equity of the license, the copyright holders can, at their discretion, object to the distribution of such combinations. ... If they do not[, then] the equity of the license will eventually come to be seen as the measuring rod [i.e. distributions will be legally permissible]." Moglen also notes that there are, "good reasons for [Linux kernel developers] not to object [to distribution]".[1] In other words, right now and for as long as the Linux developers do not object en masse to the distribution of such binaries, there is nothing in law to prevent a person from distributing such binaries. But there *is* a risk that at some point in the future the Linux developers will raise such an objection. If they do so successfully, then the binaries would indeed become non-free. I understand that Debian is erring on the side of caution on this matter, whereas Canonical is being less cautious and is evidently hoping the binaries remain legal to distribute. > That is why > ZFSonLinux module source is in the 'contrib' section, not 'main'. Yes, I understand that now from Neil's comment. Let me rephrase my earlier question again: Does Debian distribute a Debian Installer that will (either by default, or at the user's request) install source or binary packages from no repositories other than "main" and "contrib"? If so, is there any reason in principle why that installer could not in future be distributed with the capability to (download and) compile and run ZFS, and to provide the user with the option to install Debian onto a ZFS root partition? [1] https://softwarefreedom.org/resources/2016/linux-kernel-cddl.html
Bug#861923: openvpn: arbitrary process limit
Package: openvpn Version: 2.4.0-4 Severity: normal The systemd unit files for openvpn set LimitNPROC=10. This process limit applies to all processes started by a particular unit, so (for example) if there are 11 server .conf files the last one won't run. Or, with a smaller number of .conf files, subprocesses (scripts) could randomly fail. There is a note about this in README.Debian, but that note doesn't mention a likely error message associated with nproc issues (generally something about a fork error). I'd suggest adding a mention of fork errors as a symptom of the nproc limit being too low, but I'd also suggest a much higher default limit. It is not clear to me what problem a limit of 10 solves that wouldn't be solved by a limit of 1000, while a higher limit is much less likely to be hit through legitimate use. Mike Stone
Bug#861523: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED
Christoph Biedl wrote: > tags 861523 moreinfo unreproducible > thanks > > Chris Lamb wrote... > > > ! t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 > > latest' FAILED > > I was unable to reproduce your report. Can you please re-check? > > Christoph Hi, Chris: I can't reproduce this either. I tried building with root and non-root users, and with the timezone set to Europe/London. Could you share more details about the build environment? (Especially what filesystem is being used.) -- Robert Edmonds edmo...@debian.org
Bug#830482: [Pkg-clamav-devel] Bug#830482: Fresh installation causes freshclam to to fail
On 2017-05-04 22:11:02 [+0200], To T. Joseph Carter wrote: > I will try to reproduce this myself over the weekend. The original > reported never came back to me. Just for the record: You run stable or > testing? And all you did was just a plain install? And you do have > systemd as default. You replied that you were using `sid' but didn't Cc the bug so here I add this detail for the protocol. All you say is that once you have the "UpdateLogFile" entry then freshclam won't work. Then you remove that line (or add # in front of it) and it works. So this is something I can't reproduce. It worked well here. What is the error message that you face? Sebastian
Bug#860443: bbrun fails to execute (Segment Violation)
Hello, I tried to reproduce the crash. It happens just after trying to execute something. History handling uses an array of pointer to char. Unfortunately it is stored in a pointer to a 32-bit integer. Therefore pointer get truncated. gcc is tries to warn about this: bbrun.c: In function ‘readHistory’: bbrun.c:202:19: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] *histTOC2 = (u32) item; coredumpctl gdb (gdb) bt #0 strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x7f0d9be2ed78 in _IO_vfprintf_internal (s=0x55586cdd4d20, format=, ap=ap@entry=0x7ffca6fb9568) at vfprintf.c:1637 #2 0x7f0d9be35157 in __fprintf (stream=, format=) at fprintf.c:32 #3 0x55586bcc0cdf in writeHistory () at bbrun.c:312 #4 0x55586bcc0f36 in execDialogInformation () at bbrun.c:346 #5 0x55586bcc1063 in callback (widget=, data=) at bbrun.c:326 #6 0x7f0d9c994f75 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ... (gdb) frame 3 #3 0x55586bcc0cdf in writeHistory () at bbrun.c:312 312 fprintf(fp, "%s\n", (char *) *histTOC2); (gdb) print histTOC2 $1 = (u_int32_t *) 0x55586ccd7e50 (gdb) print/x *histTOC2 $3 = 0x6cdd4c10 Attached dpatch tries to use proper pointer types avoiding casts. Kind regards, Bernhard #! /bin/sh /usr/share/dpatch/dpatch-run ## ## All lines beginning with `## DP:' are a description of the patch. ## ##From 62373247b1a4cc58d9066bb976bff8df96ae0a73 Mon Sep 17 00:00:00 2001 ##From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?=##Date: Fri, 5 May 2017 23:01:38 +0200 ##Subject: Use pointer type instead of 32bit integer to store history. ## ##https://bugs.debian.org/860443 ##--- ## bbrun/bbrun.c | 21 ++--- ## 1 file changed, 10 insertions(+), 11 deletions(-) @DPATCH@ diff --git a/bbrun/bbrun.c b/bbrun/bbrun.c index 46bf6c3..a52026e 100644 --- a/bbrun/bbrun.c +++ b/bbrun/bbrun.c @@ -20,7 +20,6 @@ #define ADVANCED_WINDOW_ROWS 3 #define ADVANCED_WINDOW_COLS 10 -#define u32 u_int32_t #define __DEBUG__ 0 #define VERSION "1.6" @@ -38,8 +37,8 @@ char historyFilename[MAXPATHLEN + 1];// The path to the history file, +1 is // TOC = Table Of Contents, it is a dynamically allocated array of pointers to dynamically // allocated history items. -u32 *histTOC; // Always keep track of the beginning, this one is NEVER incremented. -u32 *histTOC2; // We increment this one for each item +char* *histTOC; // Always keep track of the beginning, this one is NEVER incremented. +char* *histTOC2;// We increment this one for each item void parseArguments(int, char **); void execDialogInformation(); @@ -170,7 +169,7 @@ void readHistory(void) { char *item; FILE *fp; - histTOC = malloc(sizeof(u32) * 1); + histTOC = malloc(sizeof(*histTOC) * 1); histTOC2 = histTOC; if ((fp = fopen(historyFilename, "r")) == 0) { @@ -192,14 +191,14 @@ void readHistory(void) { if (buf != NULL) { historyLength++; - histTOC = realloc(histTOC, sizeof(u32) * historyLength); + histTOC = realloc(histTOC, sizeof(*histTOC) * historyLength); histTOC2 = histTOC + historyLength - 1; item = malloc(strlen(buf)); strncpy(item, buf, strlen(buf)); item[strlen(buf)- 1] = 0x0; // Remove the newline char - *histTOC2 = (u32) item; + *histTOC2 = item; } else { // sc...@furt.com, This is a NULL line, which should NEVER happen. Stop any further processing, // because chances are very good that the rest of the file is corrupt too. @@ -232,7 +231,7 @@ void updateHistory(char *newHistoryItem) int duplicate = -1; int historyIndex; char *item; - u32 *histTransit;// Before, we would copy the data around, now we play around + char *histTransit; // Before, we would copy the data around, now we play around // with the pointers, which should be more efficient. if (__DEBUG__) @@ -256,7 +255,7 @@ void updateHistory(char *newHistoryItem) fprintf(stderr, " duplicate of item [%02d].\n", duplicate); if (duplicate != (historyLength - 1)) {// If the duplicate entry is not at the end - histTransit = (u32 *) (histTOC + duplicate); + histTransit = *(histTOC + duplicate); // Shift each entry forward for (historyIndex = duplicate; historyIndex < historyLength - 1; historyIndex++) { @@ -266,7 +265,7 @@ void updateHistory(char *newHistoryItem) // put duplicate at the end histTOC2 = histTOC + historyLength - 1; - *histTOC2 = (u32) histTransit; + *histTOC2 = histTransit; } } else { // The command is NOT in the history already, so add it @@ -276,14 +275,14 @@ void updateHistory(char *newHistoryItem) historyLength++; // Set the last item of
Bug#861263: debian-installer: zfs support
On Fri, 2017-05-05 at 21:40 +0100, Sam Kuper wrote: [...] > So, I am not sure why you say that ZFSonLinux binaries are non-free. > Please could you explain? I was referring specifically to the binary kernel modules, which have a mixture of CDDL and GPLv2 code. These licences are incompatible so the binaries cannot be distribured, thus are non-free. That is why ZFSonLinux module source is in the 'contrib' section, not 'main'. I assume, though I haven't checked, that the userland packages are CDDL-only (and dynamically linked to LGPL libraries) which is fine. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#861263: debian-installer: zfs support
On 05/05/2017, Sam Kuperwrote: > On 05/05/2017, Ben Hutchings wrote: >> The legal status of ZFSonLinux was discussed by the FTP team and DPL >> over a long period, with input from legal counsel, resulting in a >> decision to put it in the 'contrib' section. That decision is unlikely >> to be revisited soon. > > Thanks. I have searched for such a discussion but have not yet found > it. Do you have a link to the discussion? Did its conclusions > definitely cover source distribution, or only binaries? I still have not found the discussion, but I have found a helpful summary by Neil McGovern. In a comment thread there, Neil summarises the reason to put the ZFS DKMS into "main", even though it is distributed as source:[1] Martin (February 28, 2017 at 6:14 pm): > I understand the decision to distribute ZFS as source > only, but could you elaborate on why the package is > going into contrib rather than main? Neil McGovern (February 28, 2017 at 6:26 pm): > Sure – it’s about the promise that Debian makes to > the end user. Basically, by it being in main you’re > legally able to redistribute the end product (along with > source). With a CDDL module and a GPL2+ kernel, > that becomes – at best – unclear. I would still like to see the original discussion, but for the time being, this comment of Neil's adequately answer my question about Debian's rationale re: source vs binary and "contrib" vs "main". However, there is another comment thread on Neil's summary that seems very pertinent to this bug (Bug#861263):[2] Bill McGrath (March 12, 2016 at 1:27 am): > [...] If source is the only option, might I > suggest building a script into the installer to do the > downloading and compiling so that installation will still > be a breeze. Neil McGovern (March 14, 2016 at 9:11 am): > This is what’ll happen already, we’re using DKMS In other words, Bill McGrath's request matches my suggestion above[3], and Neil McGovern's reply suggests it is already on Debian's roadmap. Why, then, is this bug (Bug#861263) marked as wontfix? Did something change Neil's mind after that comment was posted? Or was Neil wrong at the time to suggest that the Debian Installer will include a script to download and compile ZFS? [1] https://blog.halon.org.uk/2016/01/on-zfs-in-debian/#comment-13678 [2] https://blog.halon.org.uk/2016/01/on-zfs-in-debian/#comment-9055 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861263#17
Bug#861486: Re: Bug#861486: julia: FTBFS on mips64el (segmentation fault)
Hi, On 05/05/17 12:10, Graham Inggs wrote: > Control: reassign -1 src:openblas 0.2.19-2 > Control: retitle -1 openblas: random segfaults on mips64el > Control: affects -1 src:julia > > Hi Sébastien > > I was able to reproduce this on eller.debian.org by running > utest/openblas_utest repeatedly: I submitted this PR upstream which fixes some MIPS threading issues in I found. Applying it to upstream git fixes the simple shlibdeps segfaults discussed earlier in the bugreport. I haven't tested julia or this specific test yet though. https://github.com/xianyi/OpenBLAS/pull/1178 James signature.asc Description: OpenPGP digital signature
Bug#853441: hexcurse: ftbfs with GCC-7
I've sent upstream a pull request with fixes for this FTBFS: https://github.com/LonnyGomes/hexcurse/pull/24
Bug#861919: fusioninventory-for-glpi: not installable in sid
Hi, Sorry, i no longer maintain this package. And i no longer contribute i am disappointed with the project. Feel free to fix. Best regards 2017-05-05 22:13 GMT+02:00 Ralf Treinen: > Package: fusioninventory-for-glpi > Version: 2.4.0-1 > Severity: serious > User: trei...@debian.org > Usertags: edos-uninstallable > > Hello, > > fusioninventory-for-glpi is not installable in sid since 2016-12-21, on > any architecture, since it depends on glpi (>= 0.78). However, glpi > only exists in stable and oldstable. > > -Ralf. -- David Hannequin
Bug#861922: ITP: haskell-posix-pty -- pseudoterminal interaction with subprocesses
Package: wnpp Severity: wishlist Owner: Sean Whitton* Package name: haskell-posix-pty Version : 0.2.1.1 Upstream Author : Merijn Verstraaten * URL : https://bitbucket.org/merijnv/posix-pty * License : BSD-3-clause Programming Lang: Haskell Description : pseudoterminal interaction with subprocesses Haskell library permitting programs to interact with ptys by means of subprocesses: provides functions to read and write to the terminals, as well as resizing them. I am packaging this as a dependency of debug-me, another ITP of mine. I intend to maintain this under the Debian Haskell Group. -- Sean Whitton signature.asc Description: PGP signature
Bug#861523: bup: FTBFS: t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' FAILED
tags 861523 moreinfo unreproducible thanks Chris Lamb wrote... > ! t/test-ls.sh:64 '1977-09-05-135600 latest' = '1977-09-05-125600 latest' > FAILED I was unable to reproduce your report. Can you please re-check? Christoph signature.asc Description: Digital signature
Bug#861921: ITP: haskell-protobuf -- Google Protocol Buffers for Haskell
Package: wnpp Severity: wishlist Owner: Sean WhittonControl: block 861920 by -1 * Package name: haskell-protobuf Version : 0.2.1.1 Upstream Author : Steve Severance, Nathan Howell * URL : https://github.com/alphaHeavy/protobuf * License : BSD-3-clause Programming Lang: Haskell Description : Google Protocol Buffers for Haskell A library for Google's Protocol Buffers for Haskell. I am packaging this as a dependency of debug-me, another ITP of mine. -- Sean Whitton signature.asc Description: PGP signature
Bug#860051: praat: Crashes on any attempt to run
Does the following work for you? praat --run getPitchTier.Praat Rafael * Alex Hedges[2017-05-05 11:46]: The problem persists using the testing version of the package. I believe the problem with running praat is that my system lacks a monitor. I can only access it through the terminal, but it crashes, even when I only try to run a script that has no GUI-based IO. For a specific instance, I ran the command praat --open "getPitchTier.Praat", where getPitchTier.Praat contains the following contents: Read from file: "sentence.wav" selectObject: "Sound sentence" To Manipulation: 0.01, 75, 600 Extract pitch tier Save as PitchTier spreadsheet file: "oldPitchTier.PitchTier" However, praat crashes regardless of input given. - Alex On Fri, May 5, 2017 at 8:21 AM, Rafael Laboissière wrote: Control: tags -1 + moreinfo unreproducible Thank you for the bug report. I cannot reproduce it in my system and I am hereby requesting Assistance in diagnosing the cause of the problem. Could you please check whether the problem persists using the testing or the experimental versions of the package ? Best, Rafael Laboissière * Alex Hedges [2017-04-10 16:33]: Package: praat Version: 5.4.0-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** When I invoke `praat' without arguments from an ordinary shell prompt, it crashes and displays error messages. Here is a transcript: $ praat (praat:9464): GLib-GObject-WARNING **: invalid (NULL) pointer instance (praat:9464): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (praat:9464): Gtk-WARNING **: Screen for GtkWindow not set; you must always set a screen for a GtkWindow before using the window (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed (praat:9464): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion 'GDK_IS_COLORMAP (colormap)' failed (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN (screen)' failed (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN (screen)' failed (praat:9464): Gdk-CRITICAL **: IA__gdk_window_new: assertion 'GDK_IS_WINDOW (parent)' failed Segmentation fault -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.4.30-ti-r64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages praat depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-18+deb8u7 ii libcairo2 1.14.0-2.1+deb8u2 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.42.1-1+b1 ii libgtk2.0-0 2.24.25-3+deb8u1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libstdc++6 4.9.2-10 ii oss-compat 6 ii python 2.7.9-1 Versions of packages praat recommends: ii xfonts-100dpi 1:1.0.3 ii xfonts-75dpi 1:1.0.3 praat suggests no packages. -- no debconf information
Bug#861263: debian-installer: zfs support
On 05/05/2017, Ben Hutchingswrote: > On Fri, 2017-05-05 at 20:27 +0100, Sam Kuper wrote: >> On 05/05/2017, Ben Hutchings wrote: >> > On Fri, 2017-05-05 at 19:50 +0100, Sam Kuper wrote: >> > > 1. Move ZFS *source* into "main". Would this be possible without >> > > compromising Debian's "obviously prudent" arrangement?[1] Should I CC >> > > debian-legal? >> > >> > This will not happen. >> >> Forgive my ignorance, but why will it not happen? > > The legal status of ZFSonLinux was discussed by the FTP team and DPL > over a long period, with input from legal counsel, resulting in a > decision to put it in the 'contrib' section. That decision is unlikely > to be revisited soon. Thanks. I have searched for such a discussion but have not yet found it. Do you have a link to the discussion? Did its conclusions definitely cover source distribution, or only binaries? > [...] >> If it can't be disabled, then let me rephrase my earlier question. >> Does Debian distribute a Debian Installer that will install only >> DFSG-compliant software, to which the facility to compile and run ZFS >> could in principle be added? (After all, everything in "contrib" is >> DFSG-compliant,[1] including the ZFS-related packages.) If so, please >> could you provide me with a link to it? > [...] > > ZFSonLinux binaries are non-free. Your remark is surprising to me. It seems to contradict the information I have encountered. For example, see: https://packages.debian.org/search?keywords=zfs=names=all=all Some of the packages listed there are in main, and are therefore DFSG compliant.[0] The remainder are marked "[contrib]", and so must also be DFSG-compliant,[0] albeit not necessarily GPLv2-compatible. None of them are marked "[non-free]". Additionally: - The FSF regards the CDDL as a free software license.[1] - Debian regards the MPL (to which the CDDL is very similar[2]) as a DFSG-compliant license.[3] So, I am not sure why you say that ZFSonLinux binaries are non-free. Please could you explain? Thank you again for answering my questions and for helping to provide clarity about the prospect of Debian distributing an Installer with some kind of ZFS on root option. [0] https://www.debian.org/doc/debian-policy/ch-archive.html [1] https://www.gnu.org/licenses/license-list.html#CDDL [2] http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:9125:200412:dmcacncfamieofeochbn [3] https://wiki.debian.org/DFSGLicenses#Mozilla_Public_License_.28MPL.29
Bug#861920: ITP: debug-me -- secure remote debugging
Package: wnpp Severity: wishlist Owner: Sean Whitton* Package name: debug-me Version : 1.20170505 Upstream Author : Joey Hess * URL : http://debug-me.branchable.com/ * License : AGPL-3 Programming Lang: Haskell Description : secure remote debugging > Debugging a problem over email/irc/BTS is slow, tedious, and hard. The > developer needs to see the your problem to understand it. Debug-me aims > to make debugging fast, fun, and easy, by letting the developer access > your computer remotely, so they can immediately see and interact with > the problem. Making your problem their problem gets it fixed fast. > > A debug-me session is logged and signed with the developer's GnuPG > key, producing a chain of evidence of what they saw and what they > did. So the developer's good reputation is leveraged to make debug-me > secure. -- Sean Whitton signature.asc Description: PGP signature
Bug#782294: asciidoc: make timestamps reproducible adding the flag --use-utc-timezone
On Sat, 10 Dec 2016, Anders Kaseorg wrote: > Now that we have SOURCE_DATE_EPOCH, consider this PR as a replacement. > It allows software that builds with AsciiDoc to build reproducibly > without being patched to pass additional flags: > > https://github.com/asciidoc/asciidoc/pull/106 This has been merged upstream. Anders
Bug#861736: python-nxs: Cannot save files with nxs python module
Control: tag -1 + confirmed Control: user debian-rele...@lists.debian.org Control: usertag -1 + bsp-2017-05-ch-zurich Hi, Marc Rosanes wrote: >import nxs >e = nxs.NXentry(name= "NXtomo") >e.save("filenamenxs.h5", 'w5') [...] > /usr/lib/python2.7/dist-packages/nxs/tree.pyc in save(self, > filename, format) > 866 root = NXroot(NXentry(self)) > 867 if root.nxfile: root.nxfile.close() > --> 868 file = NeXusTree(filename, format) > 869 file.writefile(root) > 870 file.close() > > /usr/lib/python2.7/dist-packages/nxs/napi.pyc in __init__(self, > filename, mode) > 318 else: > 319 op = 'create' > --> 320 raise NeXusError, "Could not %s %s"%(op,filename) > 321 self.isopen = True > 322 I can reproduce this on Sid/Stretch, but not on Jessie, so this is a regression from Jessie to Stretch. The same happens if you don't specify the file format (as HDF5 seems to be the default file format). Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#861919: fusioninventory-for-glpi: not installable in sid
Package: fusioninventory-for-glpi Version: 2.4.0-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hello, fusioninventory-for-glpi is not installable in sid since 2016-12-21, on any architecture, since it depends on glpi (>= 0.78). However, glpi only exists in stable and oldstable. -Ralf.
Bug#861263: debian-installer: zfs support
On Fri, 2017-05-05 at 20:27 +0100, Sam Kuper wrote: > On 05/05/2017, Ben Hutchingswrote: > > On Fri, 2017-05-05 at 19:50 +0100, Sam Kuper wrote: > > > 1. Move ZFS *source* into "main". Would this be possible without > > > compromising Debian's "obviously prudent" arrangement?[1] Should I CC > > > debian-legal? > > > > This will not happen. > > Forgive my ignorance, but why will it not happen? The legal status of ZFSonLinux was discussed by the FTP team and DPL over a long period, with input from legal counsel, resulting in a decision to put it in the 'contrib' section. That decision is unlikely to be revisited soon. [...] > If it can't be disabled, then let me rephrase my earlier question. > Does Debian distribute a Debian Installer that will install only > DFSG-compliant software, to which the facility to compile and run ZFS > could in principle be added? (After all, everything in "contrib" is > DFSG-compliant,[1] including the ZFS-related packages.) If so, please > could you provide me with a link to it? [...] ZFSonLinux binaries are non-free. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#861918: unblock: cacti/0.8.8h+ds1-10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package cacti Yesterday I discovered that when I removed the embedded JavaScript that is now available in the new libjs-jquery-jstree package in version 0.8.8h+ds1-8, I forgot that dpkg doesn't handle convertion of directories to symlinks on its own. I reported this in bug #861858. This means that people upgrading from jessie will be left with a regression if this isn't fixed (the link contains CSS files needed to properly navigate their network tree). Please find the debdiff of version 0.8.8h+ds1-10 attached, that I just uploaded and that has been build (arch:all). unblock cacti/0.8.8h+ds1-10 - -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'experimental'), (200, 'testing'), (50, 'experimental'), (50, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlkM2r4ACgkQnFyZ6wW9 dQo7EAf+KXDHam87StwRFwlJA58LnRzX/KMsmg+sbbu9wQBvdCmBUSaHpgLpwsUT nFLs84Zx2Zfdi3aEUSmpjPdyiGY90tCWWVSrudDN6hCy8+3oFlJKdvTFWwwGMoZ6 v6jNtpJFEiYf2yW8wr4gzcGmZdaPtx+adSp8nrNZ3DhGAXv3KaS/+nttDp5oLoFj jYGdF39s8blcdzb0uNHE875FqWn3khvMP+VrML9nIdbxkJM1BBCv8vDeihpEsABF R8Tfz/3u6buE2top7VPWMoQg3l2PYkTowtffRUNJ2d+T7tkXV6RTWNhbYnixMvUc LlfIl57lcyerPALy2iNTF3MBaX52fQ== =jsis -END PGP SIGNATURE- diff -Nru cacti-0.8.8h+ds1/debian/cacti.maintscript cacti-0.8.8h+ds1/debian/cacti.maintscript --- cacti-0.8.8h+ds1/debian/cacti.maintscript 1970-01-01 01:00:00.0 +0100 +++ cacti-0.8.8h+ds1/debian/cacti.maintscript 2017-05-05 13:55:33.0 +0200 @@ -0,0 +1 @@ +dir_to_symlink /usr/share/cacti/site/include/js/themes /usr/share/javascript/jstree/themes 0.8.8h+ds1-10~ cacti diff -Nru cacti-0.8.8h+ds1/debian/cacti.preinst cacti-0.8.8h+ds1/debian/cacti.preinst --- cacti-0.8.8h+ds1/debian/cacti.preinst 1970-01-01 01:00:00.0 +0100 +++ cacti-0.8.8h+ds1/debian/cacti.preinst 2017-05-05 13:55:33.0 +0200 @@ -0,0 +1,5 @@ +#!/bin/sh + +set -e + +#DEBHELPER# diff -Nru cacti-0.8.8h+ds1/debian/changelog cacti-0.8.8h+ds1/debian/changelog --- cacti-0.8.8h+ds1/debian/changelog 2017-04-13 22:05:30.0 +0200 +++ cacti-0.8.8h+ds1/debian/changelog 2017-05-05 13:55:33.0 +0200 @@ -1,3 +1,11 @@ +cacti (0.8.8h+ds1-10) unstable; urgency=medium + + * Fix upgrades from before 0.8.8h+ds1-8; that version started to ship +symlinks to directories in libjs-jquery-jstree without making sure +dpkg handled that properly during upgrades (Closes: #861858) + + -- Paul GeversFri, 05 May 2017 13:55:33 +0200 + cacti (0.8.8h+ds1-9) unstable; urgency=medium * Add enable_faster_polling_than_cron.patch to replace the use of the
Bug#861917: debbugs package: not installable in sid
Package: debbugs Version: 2.4.1.1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hello, the debbugs package is not installable in sid since it depends on libmime-perl, which does not exist. -Ralf.
Bug#861916: apt: Better document CMake scripts
Source: apt Version: 1.3~pre3+cmake1 Severity: minor I need to document this better, there's quite a bit of scripting in CMake/ that nobody understands otherwise. -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you.
Bug#853370: deal.ii: ftbfs with GCC-7
It seems that upstream is working on those GCC-7 errors and warnings. At least they have fixed the -Wimplicit-fallthrough warnings: https://github.com/dealii/dealii/pull/4230
Bug#861915: wpa 2:2.6-4 FTBFS on amd64 due to not finding pkg-config
Source: wpa Version: 2:2.6-4 Severity: normal https://buildd.debian.org/status/fetch.php?pkg=wpa=amd64=2%3A2.6-4=1487953962=0 shows a build failure. the final error message is: ../src/drivers/driver_nl80211.c:17:31: fatal error: netlink/genl/genl.h: No such file or directory however, the problem is likely actually because the build isn't finding the native pkg-config. there are dozens of these reports: make[2]: x86_64-linux-gnu-pkg-config: Command not found It looks like it's looking for the cross-compiling toolchain rather than trying to build it natively. --dkg -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.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)
Bug#851877: fails every time
On 04/05/17 04:47, Adam Borowski wrote: > [...] I cannot reproduce these failures. I've built in my stretch sbuild around 15 times, and succedeed every time. I use: gbp buildpackage --git-builder='sbuild --source-only-changes -v -As --build-dep-resolver=apt --dist=stretch -j4' "$@" Tomasz signature.asc Description: PGP signature
Bug#855179: debian-reference-it: Disable Weblate for currently .po and git maintaned Italian translation
Wow .. On Sat, Apr 29, 2017 at 02:37:05PM +0200, Holger Wansing wrote: > Hi, > > atzlinuxwrote: > > Hi, > > > > I'm sorry for just read this bug report. > > > > I imported debian-reference to weblate at last year. > > > > After weblate update,I merge and push weblate's git brach to git.debian.org. > > > > debian-reference's many language translate had already finished,so they > > not need to translate in weblate. > > > > To aovid the distrub from weblate for already finished language,I plan > > to do this: Please do so I am not familiar with weblate > > after I pull from weblate'git,I not change their po files.I'll reserver > > their newest copy from git.debian.org in my local. > > > > de.po fr.po it.po ja.po pt.po ,if these five po files has any > > error now,please help fixed in git. > > zh-cn.po zh-tw.po es.po fi.po nb.po ,these language will continuous use > > weblate. zh-cn.po zh-tw.po es.po Yes please fi.po nb.po Are they real translation? I see no real activity. Weblate is too easy on creating new translation without someone looking at it. Is there way to make new language addition a bit more careful? > > Is this OK? > > Yes, that would be fine. > > As Beatrice already wrote, there are translations in the Debian Reference > project, which are actively maintained by a translator, and importing them > into Weblate is _definitely_hijacking_!!! True. > And that's a absolute NO-GO!!! > Why import those up-to-date translations into Weblate at all? Those > translations do not need any help from help! They have a translator, which > does it job perfectly fine! > > Moreover: when looking at the above mentioned Weblate contributions, I > see absolutely no reason, why Weblate is an option at all! > The above contribution makes me think, that the Weblate is a robot-based > translation process which goes totally crazy. That's why I see Weblate > absolutely as a NO-GO, sorry. My personally opinion. Weblate seems to be more like simple web interface to PO. But its ease of use without knowing PO building process make s XML tg errors undetected and probably makes some other errors introduced by un-experienced user. Ease of use to get more contributor and getting accountable contributor is tough decision. > Holger > > > > > > atzlinux > > > > 在 2017年04月29日 03:38, Holger Wansing 写道: > > > Hi, > > > > > > Beatrice Torracca wrote: > > >> Package: debian-reference-it > > >> Version: 2.64 > > >> Severity: wishlist > > >> > > >> Hi, > > >> > > >> I am (was? since I am not the Last-Translator) the current Italian > > >> translator of the Debian Reference. I always kept it up to date (to > > >> the best of my capabilities, of course). > > >> > > >> I saw that a recent change was made via Weblate (changing the > > >> translator assignement, as I said). > > > I just noticed this commit: > > > https://anonscm.debian.org/cgit/ddp/debian-reference.git/commit/ > > > and I assume that this should be reverted. > > > > > > This makes me scary about the quality of weblate contributions ... > > > > > > Does anyone watches/prooves that weblate contributions? > > > > > > > > > I doubt that such contribution is of any help. > > > So, weblate should be disabled here. > > > > > > > > > Holger > > > > > > > > > > > > > -- > > Created with Sylpheed 3.5.0 under > D E B I A N L I N U X 8 . 0 " J E S S I E " . > > Registered Linux User #311290 - https://linuxcounter.net/ >
Bug#861914: unblock: gitlab/8.13.11+dfsg1-4
On 05/05/17 21:36, Tomasz Buchert wrote: > [...] Let me add that the bug in question is https://bugs.debian.org/861870. signature.asc Description: PGP signature
Bug#861914: unblock: gitlab/8.13.11+dfsg1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gitlab The attached debdiff fixes CVE-2017-8778. unblock gitlab/8.13.11+dfsg1-4 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Bug#861870: gitlab: CVE-2017-8778
On 05/05/17 20:46, Tomasz Buchert wrote: > On 05/05/17 06:19, Salvatore Bonaccorso wrote: > > [...] > > Hi Salvatore, > the fix for this issue seems to be here: > https://gitlab.com/winniehell/gitlab-ce/commit/dd944bf14f4a0fd555db32d5833325fa459d9565 > > I'll try to apply it to stretch's gitlab. > Tomasz Interestingly, the CVE has been fixed for unstable just an hour ago or so: https://anonscm.debian.org/cgit/pkg-ruby-extras/gitlab.git/commit/?id=7241318db49ec356f31dac96345a4ff730d313f0 I've reapplied this for the stretch version and I attach the debdiff. I'm going to request an unblock for this. For some reason I couldn't push my branch to ssh://git.debian.org/git/pkg-ruby-extras/gitlab.git. Probably I should become ruby-extras team member or something. For this reason I also attach the commits from my branch. Cheers, Tomasz diff -Nru gitlab-8.13.11+dfsg1/debian/changelog gitlab-8.13.11+dfsg1/debian/changelog --- gitlab-8.13.11+dfsg1/debian/changelog 2017-04-21 12:32:25.0 +0200 +++ gitlab-8.13.11+dfsg1/debian/changelog 2017-05-05 21:23:50.0 +0200 @@ -1,3 +1,9 @@ +gitlab (8.13.11+dfsg1-4) testing-proposed-updates; urgency=medium + + * Fix CVE-2017-8778 + + -- Tomasz BuchertFri, 05 May 2017 21:23:50 +0200 + gitlab (8.13.11+dfsg1-3) unstable; urgency=medium * Quote variable in test -n (Thanks to Benjamin Drung) diff -Nru gitlab-8.13.11+dfsg1/debian/patches/cve-2017-8778.patch gitlab-8.13.11+dfsg1/debian/patches/cve-2017-8778.patch --- gitlab-8.13.11+dfsg1/debian/patches/cve-2017-8778.patch 1970-01-01 01:00:00.0 +0100 +++ gitlab-8.13.11+dfsg1/debian/patches/cve-2017-8778.patch 2017-05-05 21:14:50.0 +0200 @@ -0,0 +1,99 @@ +From: Debian Ruby Extras Maintainers + +Date: Fri, 5 May 2017 21:00:42 +0200 +Subject: cve-2017-8778 + +--- + app/uploaders/file_uploader.rb | 2 +- + app/uploaders/uploader_helper.rb| 8 + spec/controllers/uploads_controller_spec.rb | 22 ++ + spec/factories/notes.rb | 6 +- + 4 files changed, 36 insertions(+), 2 deletions(-) + +diff --git a/app/uploaders/file_uploader.rb b/app/uploaders/file_uploader.rb +index 3ac6030..407606a 100644 +--- a/app/uploaders/file_uploader.rb b/app/uploaders/file_uploader.rb +@@ -36,7 +36,7 @@ class FileUploader < CarrierWave::Uploader::Base + escaped_filename = filename.gsub("]", "\\]") + + markdown = "[#{escaped_filename}](#{self.secure_url})" +-markdown.prepend("!") if image_or_video? ++markdown.prepend("!") if image_or_video? || dangerous? + + { + alt: filename, +diff --git a/app/uploaders/uploader_helper.rb b/app/uploaders/uploader_helper.rb +index b10ad71..5a9c0b7 100644 +--- a/app/uploaders/uploader_helper.rb b/app/uploaders/uploader_helper.rb +@@ -7,11 +7,19 @@ module UploaderHelper + # on IE >= 9. + # http://archive.sublimevideo.info/20150912/docs.sublimevideo.net/troubleshooting.html + VIDEO_EXT = %w[mp4 m4v mov webm ogv] ++ # These extension types can contain dangerous code and should only be embedded inline with ++ # proper filtering. They should always be tagged as "Content-Disposition: attachment", not "inline". ++ DANGEROUS_EXT = %w[svg] ++ + + def image? + extension_match?(IMAGE_EXT) + end + ++ def dangerous? ++extension_match?(DANGEROUS_EXT) ++ end ++ + def video? + extension_match?(VIDEO_EXT) + end +diff --git a/spec/controllers/uploads_controller_spec.rb b/spec/controllers/uploads_controller_spec.rb +index 69124ab..8ea9c71 100644 +--- a/spec/controllers/uploads_controller_spec.rb b/spec/controllers/uploads_controller_spec.rb +@@ -4,6 +4,28 @@ describe UploadsController do + let!(:user) { create(:user, avatar: fixture_file_upload(Rails.root + "spec/fixtures/dk.png", "image/png")) } + + describe "GET show" do ++context 'Content-Disposition security measures' do ++ let(:project) { create(:empty_project, :public) } ++ ++ context 'for PNG files' do ++it 'returns Content-Disposition: inline' do ++ note = create(:note, :with_attachment, project: project) ++ get :show, model: 'note', mounted_as: 'attachment', id: note.id, filename: 'image.png' ++ ++ expect(response['Content-Disposition']).to start_with('inline;') ++end ++ end ++ ++ context 'for SVG files' do ++it 'returns Content-Disposition: attachment' do ++ note = create(:note, :with_svg_attachment, project: project) ++ get :show, model: 'note', mounted_as: 'attachment', id: note.id, filename: 'image.svg' ++ ++ expect(response['Content-Disposition']).to start_with('attachment;') ++end ++ end ++end ++ + context "when viewing a user avatar" do + context "when signed in" do + before do +diff --git a/spec/factories/notes.rb b/spec/factories/notes.rb +index a10ba62..b60b9f6 100644 +---
Bug#861263: debian-installer: zfs support
On 05/05/2017, Ben Hutchingswrote: >On Fri, 2017-05-05 at 19:50 +0100, Sam Kuper wrote: >> 1. Move ZFS *source* into "main". Would this be possible without >> compromising Debian's "obviously prudent" arrangement?[1] Should I CC >> debian-legal? > > This will not happen. Forgive my ignorance, but why will it not happen? >> 2. Add ZFS to a Debian Installer that is not the *default* Debian >> Installer. Does Debian distribute such an installer, to which the >> facility to compile and run ZFS could be added? > > Yes, there is already an (officially unofficial) installer that > includes non-free firmware. Thanks for the information. Can the non-free aspect of that installer be disabled by the user during installation? If not, then it would be no use to anyone I know who would be interested in running ZFS under Debian. That is because a key reason to use Debian in preference to other distros is that Debian's blob-free kernel and DFSG-compliant main and contrib repositories make it easy to avoid installing non-free software. If a person doesn't mind the risk of installing non-free firmware then they may as well just skip Debian and use Ubuntu or FreeBSD instead, which ship with ZFS in the installer by default. If it can't be disabled, then let me rephrase my earlier question. Does Debian distribute a Debian Installer that will install only DFSG-compliant software, to which the facility to compile and run ZFS could in principle be added? (After all, everything in "contrib" is DFSG-compliant,[1] including the ZFS-related packages.) If so, please could you provide me with a link to it? Thanks again :) Please CC me, as I am still not subscribed to the mailing list. [1] https://www.debian.org/doc/debian-policy/ch-archive.html
Bug#861913: mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4
Package: mariadb-client-10.1 Version: 10.1.22-3 Severity: normal Hi, Not sure how mytop ended up in mariadb-client.. # apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: mariadb-client-10.1 The following packages will be upgraded: mariadb-client-10.1 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 38 not fully installed or removed. Need to get 0 B/5,816 kB of archives. After this operation, 21.5 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 64666 files and directories currently installed.) Preparing to unpack .../mariadb-client-10.1_10.1.23-3_amd64.deb ... Unpacking mariadb-client-10.1 (10.1.23-3) over (10.1.22-3) ... dpkg: error processing archive /var/cache/apt/archives/mariadb-client-10.1_10.1.23-3_amd64.deb (--unpack): trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/mariadb-client-10.1_10.1.23-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Gr, Olaf -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mariadb-client-10.1 depends on: ii debianutils 4.8.1.1 ii libc6 2.24-10 ii libstdc++66.3.0-16 iu mariadb-client-core-10.1 10.1.23-3 pn perl:any ii zlib1g1:1.2.8.dfsg-5 Versions of packages mariadb-client-10.1 recommends: ii libdbd-mysql-perl 4.041-2 ii libdbi-perl 1.636-1+b1 ii libterm-readkey-perl 2.37-1 mariadb-client-10.1 suggests no packages. -- no debconf information
Bug#857749: Fixed
I recently upgraded another machine to Stretch and, voilà!, Neo 2 works perfectly. Fault on my computer. No bug.
Bug#861263: debian-installer: zfs support
On Fri, 2017-05-05 at 19:50 +0100, Sam Kuper wrote: > > On 05/05/2017, Ben Hutchingswrote: > > On Fri, 2017-05-05 at 14:26 +0100, Sam Kuper wrote: > > > On Wed, 2017-04-26 at 19:51:23 +0100, Ben Hutchings wrote: > > > > On Wed, 2017-04-26 at 18:20 +0200, Timo Haas wrote: > > > > > do you plan to support zfs as root filesystem in the installer? > > > > > > > > ZFS binaries are not distributable due to the licence conflict, so this > > > > is unlikely to happen. > > > > > > If the Debian Installer were instead to ship with, or to download at > > > runtime, the ZFS on Linux source code, would that be acceptable from a > > > licensing standpoint? > > > > I imagine this would be acceptable (though not in the default > > installer, which only uses and installs packages from main). > > Good point. Potential avenues: > > 1. Move ZFS *source* into "main". Would this be possible without > compromising Debian's "obviously prudent" arrangement?[1] Should I CC > debian-legal? This will not happen. > 2. Add ZFS to a Debian Installer that is not the *default* Debian > Installer. Does Debian distribute such an installer, to which the > facility to compile and run ZFS could be added? Yes, there is already an (officially unofficial) installer that includes non-free firmware. Ben. > Thanks :) > > (Please CC me, as I am still not subscribed to the mailing list.) > > [1] https://softwarefreedom.org/resources/2016/linux-kernel-cddl.html -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#861263: debian-installer: zfs support
On 05/05/2017, Ben Hutchingswrote: > On Fri, 2017-05-05 at 14:26 +0100, Sam Kuper wrote: >> On Wed, 2017-04-26 at 19:51:23 +0100, Ben Hutchings wrote: >> > On Wed, 2017-04-26 at 18:20 +0200, Timo Haas wrote: >> > > do you plan to support zfs as root filesystem in the installer? >> > >> > ZFS binaries are not distributable due to the licence conflict, so this >> > is unlikely to happen. >> >> If the Debian Installer were instead to ship with, or to download at >> runtime, the ZFS on Linux source code, would that be acceptable from a >> licensing standpoint? > > I imagine this would be acceptable (though not in the default > installer, which only uses and installs packages from main). Good point. Potential avenues: 1. Move ZFS *source* into "main". Would this be possible without compromising Debian's "obviously prudent" arrangement?[1] Should I CC debian-legal? 2. Add ZFS to a Debian Installer that is not the *default* Debian Installer. Does Debian distribute such an installer, to which the facility to compile and run ZFS could be added? Thanks :) (Please CC me, as I am still not subscribed to the mailing list.) [1] https://softwarefreedom.org/resources/2016/linux-kernel-cddl.html
Bug#860689: blockdiag: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Control: retitle -1 double free or corruption when loading unhandled SVG from BytesIO Control: reassign -1 python-wand Control: affects -1 blockdiag Hi, * Lucas Nussbaum[170505 18:36]: > During a rebuild of all packages in stretch (in a stretch chroot, not a > sid chroot), your package failed to build on i386. > > Relevant part (hopefully): > > f73d6000-f73d7000 r--p 00022000 ca:02 6950262 > > /lib/i386-linux-gnu/ld-2.24.so > > f73d7000-f73d8000 rw-p 00023000 ca:02 6950262 > > /lib/i386-linux-gnu/ld-2.24.so > > f73d8000-f7733000 r-xp ca:02 6822683 > > /usr/bin/python2.7 > > f7733000-f7734000 rwxp 00:00 0 > > f7734000-f7735000 r--p 0035b000 ca:02 6822683 > > /usr/bin/python2.7 > > f7735000-f7795000 rw-p 0035c000 ca:02 6822683 > > /usr/bin/python2.7 > > f7795000-f77aa000 rw-p 00:00 0 > > f90e4000-f96dc000 rw-p 00:00 0 > > [heap] > > ff8b3000-ff8d4000 rw-p 00:00 0 > > [stack] > > Aborted I've reduced this to a simple test case: import io import wand.image s = io.BytesIO() s.write('\nhttp://www.w3.org/2000/svg;>\n circle\n \n\n') s.seek(0) wand.image.Image(file=s) Result on i386: (stretch_i386-dchroot)zeha@barriere:~$ python ~/test.py Traceback (most recent call last): File "/home/zeha/test.py", line 7, in wand.image.Image(file=s) File "/usr/lib/python2.7/dist-packages/wand/image.py", line 2740, in __init__ self.read(file=file, resolution=resolution) File "/usr/lib/python2.7/dist-packages/wand/image.py", line 2822, in read self.raise_exception() File "/usr/lib/python2.7/dist-packages/wand/resource.py", line 222, in raise_exception raise e wand.exceptions.MissingDelegateError: no decode delegate for this image format `SVG' @ error/blob.c/BlobToImage/353 Exception TypeError: TypeError("object of type 'NoneType' has no len()",) in > ignored *** Error in `python': double free or corruption (!prev): 0xf90daf40 *** === Backtrace: = /lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xf71d437a] /lib/i386-linux-gnu/libc.so.6(+0x6dfb7)[0xf71dafb7] /lib/i386-linux-gnu/libc.so.6(+0x6e776)[0xf71db776] python(PyMem_Free+0x18)[0xf74f7fe8] /usr/lib/python2.7/lib-dynload/_ctypes.i386-linux-gnu.so(+0xf249)[0xf7054249] python(+0x10f97d)[0xf74f897d] python(+0x10f485)[0xf74f8485] python(+0xeb29e)[0xf74d429e] python(+0xf1cbd)[0xf74dacbd] python(+0xf1c88)[0xf74dac88] python(PyDict_SetItem+0x44a)[0xf749cfea] python(PyDict_SetItemString+0x58)[0xf74a04d8] python(PyImport_Cleanup+0x118)[0xf74fd488] python(Py_Finalize+0x99)[0xf74fb439] python(Py_Main+0x4d3)[0xf749a2a3] python(main+0x26)[0xf7499db6] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf7185276] python(+0xb0c50)[0xf7499c50] Note that blockdiag is not even involved in this code anymore. Therefore reassigning to wand, which appears to be the running code. Involved versions: ii libmagickcore-6.q16-3:i3868:6.9.7.4+dfsg-6 i386 low-level image manipulation library -- quantum depth Q16 ii libmagickcore-6.q16-3-dbgsym:i386 8:6.9.7.4+dfsg-6 i386 Debug symbols for libmagickcore-6.q16-3 ii libmagickwand-6.q16-3:i3868:6.9.7.4+dfsg-6 i386 image manipulation library -- quantum depth Q16 ii libmagickwand-6.q16-3-dbgsym:i386 8:6.9.7.4+dfsg-6 i386 Debug symbols for libmagickwand-6.q16-3 ii python-wand 0.4.4-1.1all Python interface for ImageMagick library (Python 2 build) Best, C.
Bug#861870: gitlab: CVE-2017-8778
On 05/05/17 06:19, Salvatore Bonaccorso wrote: > [...] Hi Salvatore, the fix for this issue seems to be here: https://gitlab.com/winniehell/gitlab-ce/commit/dd944bf14f4a0fd555db32d5833325fa459d9565 I'll try to apply it to stretch's gitlab. Tomasz signature.asc Description: PGP signature
Bug#861912: general: turning off bluetooth in upper toolbar in Gnome 3 doesn't keep it off (Wheezy)
Package: general Severity: important Dear Maintainer, I tried turning off bluetooth via the icon in the upper toolbar in Gnome 3 in Wheezy oldstable, which I run WITH hardware acceleration on PowerMac G5 Quad, a feature I obtained easily without troubleshooting kernel recompiles in Stable. It's nouveau on a Quadro FX 4500. :) Besides that "nudge" or "hint" on improving nouveau on stables and testings, I'd like to notify that turning off the bluetooth via the feature up top only disables for the running session. Upon rebooting, it's back on. This is a request to implement that turning off the bluetooth is remembered for the respective user. Thank you -- System Information: Debian Release: 7.11 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: powerpc (ppc64) Kernel: Linux 3.2.0-4-powerpc64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#578787: the International Bank Credit Analyst
I am miss Betty Alexandre of the International Bank Credit Analyst, I have important information to relate with you, contact me via: bettyalexander.pre...@yahoo.com
Bug#859883: ycmd: Don't hardcode path to tern for JavaScript completion
Control: tags -1 pending Thanks for reporting and sorry for late reply. I found out about ~/.npm-packages (by default `npm install -g tern` is using this directory, ~/.npm-global is just used as an example in the documentation you linked), but I forgot to update patch. I applied your revisited patch but ycmd in Debian is always trying to use tern with nodejs (installed by Debian package manager). I hope this will do the trick. On 2017-04-08, Mirosław Zalewski wrote: > Package: ycmd > Version: 0+20161219+git486b809-1 > Severity: normal > > Dear Maintainer, > > ycmd currently looks for tern (needed for JavaScript completion) in > ~/node_modules/tern. As README.Debian states, this is what users would > get if they run `npm install tern`. > > However, npm in Debian is in so bad shape, that it outright fails to > install some packages (see e.g. 780789). It has prompted discussion of > removal of npm from Debian altogether (see 857986). It is very likely > that people will use npm outside of Debian. > > It seems that upstream currently prefers to install user-wide npm > modules into `~/.npm-global` (see [1]). ycmd users who follow upstream > instruction (i.e. majority of them) will fail to get tern running inside > ycmd, as paths diverge. > > Please consider modifying package to allow for tern to be placed outside > of `~/node_modules/`. > > Attached is revised 05-tern-support.patch that will look for tern in > $PATH and resort to ~/node_modules if it was not found. > > Best regards, > Mirosław Zalewski > > [1] https://docs.npmjs.com/getting-started/fixing-npm-permissions > > *** debian/patches/05-tern-support.patch > Description: Debian doesn't have node-tern. This patch is making ycmd to > use locally installed tern with `npm install tern` command. > > Index: ycmd-0+20161219+git486b809/ycmd/completers/javascript/tern_completer.py > === > --- > ycmd-0+20161219+git486b809.orig/ycmd/completers/javascript/tern_completer.py > +++ ycmd-0+20161219+git486b809/ycmd/completers/javascript/tern_completer.py > @@ -36,20 +36,14 @@ from ycmd.completers.completer_utils imp > > _logger = logging.getLogger( __name__ ) > > -PATH_TO_TERN_BINARY = os.path.abspath( > - os.path.join( > -os.path.dirname( __file__ ), > -'..', > -'..', > -'..', > -'third_party', > -'tern_runtime', > -'node_modules', > -'tern', > -'bin', > -'tern' ) ) > +PATH_TO_TERN_BINARY = utils.PathToFirstExistingExecutable( [ 'tern' ] ) > +if not PATH_TO_TERN_BINARY: > + PATH_TO_TERN_BINARY = os.path.join( > +os.path.expanduser('~'), > +'node_modules', > +'tern') > > -PATH_TO_NODE = utils.PathToFirstExistingExecutable( [ 'node' ] ) > +PATH_TO_NODE = utils.PathToFirstExistingExecutable( [ 'nodejs' ] ) > > # host name/address on which the tern server should listen > # note: we use 127.0.0.1 rather than localhost because on some platforms > > > -- System Information: > Debian Release: 9.0 > APT prefers testing > APT policy: (990, 'testing'), (400, 'unstable'), (102, 'experimental'), > (10, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to pl_PL.UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ycmd depends on: > ii libboost-filesystem1.62.0 1.62.0+dfsg-4 > ii libboost-python1.62.0 1.62.0+dfsg-4 > ii libboost-regex1.62.0 1.62.0+dfsg-4 > ii libboost-system1.62.0 1.62.0+dfsg-4 > ii libc6 2.24-9 > ii libclang1-3.9 1:3.9.1-5 > ii libgcc11:6.3.0-11 > ii libpython2.7 2.7.13-2 > ii libstdc++6 6.3.0-11 > ii python-bottle 0.12.13-1 > ii python-frozendict 0.5-1 > ii python-future 0.15.2-4 > ii python-jedi0.10.0~git1+f05c071-1 > ii python-requests2.12.4-1 > ii python-waitress1.0.1-1 > ii python2.7 2.7.13-2 > pn python:any > > Versions of packages ycmd recommends: > pn libclang-common-3.9-dev > pn node-typescript > ii vim-youcompleteme0+20161219+git194ff33-1 > > ycmd suggests no packages. > > -- no debconf information -- regards, Onur Aslan GPG Key : E5EF 3C2C 67BC 6F76 DAB3 A40E 7B96 C7AF EB16 673C .''`. Website : https://onur.im: :' : Github: https://github.com/onur`. `'` Debian QA : https://qa.debian.org/developer.php?login=o...@onur.im `- signature.asc Description: Digital signature
Bug#861112: xsane: always crashes on start
On 05/05/2017 07:16 PM, Aaro Koskinen wrote: > I think Jörg Frings-Fürst has analyzed and fixed this bug already - he > provided me test packages (libsane_1.0.25-4~test1_amd64.deb etc.) offline > for testing and they seemed to fix the issue. No, he didn't "fix" the issue. He completely removed a feature from sane-backends and called it a fix, assuming that no one in Debian or Ubuntu or any of the derived distributions wants to use Avahi with SANE. > I'm currently away from my machines, but next week I'll recheck the > situation again with up-to-date Debian testing, If the problem is still > present I will provide the full backtrace etc. Yes, please. I am not going to accept such a rather big cut in functionality without proper testing and error analysis first. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#861834: libtirpc: diff for NMU version 0.2.5-1.2
Dear maintainer, I've prepared an NMU for libtirpc (versioned as 0.2.5-1.2). The diff is attached to this message. Regards, Salvatore diff -Nru libtirpc-0.2.5/debian/changelog libtirpc-0.2.5/debian/changelog --- libtirpc-0.2.5/debian/changelog 2016-12-21 23:12:21.0 +0100 +++ libtirpc-0.2.5/debian/changelog 2017-05-05 17:24:41.0 +0200 @@ -1,3 +1,11 @@ +libtirpc (0.2.5-1.2) unstable; urgency=high + + * Non-maintainer upload. + * CVE-2017-8779: Memory leak when failing to parse XDR strings or bytearrays +(Closes: #861834) + + -- Salvatore BonaccorsoFri, 05 May 2017 17:24:41 +0200 + libtirpc (0.2.5-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libtirpc-0.2.5/debian/patches/11-CVE-2017-8779.diff libtirpc-0.2.5/debian/patches/11-CVE-2017-8779.diff --- libtirpc-0.2.5/debian/patches/11-CVE-2017-8779.diff 1970-01-01 01:00:00.0 +0100 +++ libtirpc-0.2.5/debian/patches/11-CVE-2017-8779.diff 2017-05-05 17:24:41.0 +0200 @@ -0,0 +1,255 @@ +Description: CVE-2017-8779: Memory leak when failing to parse XDR strings or bytearrays +Origin: vendor +Bug-Debian: https://bugs.debian.org/861834 +Forwarded: not-needed +Author: Guido Vranken +Reviewed-by: Salvatore Bonaccorso +Last-Update: 2017-05-05 + +--- a/src/rpc_generic.c b/src/rpc_generic.c +@@ -620,6 +620,9 @@ __rpc_taddr2uaddr_af(int af, const struc + + switch (af) { + case AF_INET: ++ if (nbuf->len < sizeof(*sin)) { ++ return NULL; ++ } + sin = nbuf->buf; + if (inet_ntop(af, >sin_addr, namebuf, sizeof namebuf) + == NULL) +@@ -631,6 +634,9 @@ __rpc_taddr2uaddr_af(int af, const struc + break; + #ifdef INET6 + case AF_INET6: ++ if (nbuf->len < sizeof(*sin6)) { ++ return NULL; ++ } + sin6 = nbuf->buf; + if (inet_ntop(af, >sin6_addr, namebuf6, sizeof namebuf6) + == NULL) +@@ -673,6 +679,8 @@ __rpc_uaddr2taddr_af(int af, const char + + port = 0; + sin = NULL; ++ if (uaddr == NULL) ++ return NULL; + addrstr = strdup(uaddr); + if (addrstr == NULL) + return NULL; +--- a/src/rpcb_prot.c b/src/rpcb_prot.c +@@ -41,6 +41,7 @@ + #include + #include + #include ++#include "rpc_com.h" + + bool_t + xdr_rpcb(xdrs, objp) +@@ -53,13 +54,13 @@ xdr_rpcb(xdrs, objp) + if (!xdr_u_int32_t(xdrs, >r_vers)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >r_netid, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_netid, RPC_MAXDATASIZE)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >r_addr, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_addr, RPC_MAXDATASIZE)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >r_owner, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_owner, RPC_MAXDATASIZE)) { + return (FALSE); + } + return (TRUE); +@@ -159,19 +160,19 @@ xdr_rpcb_entry(xdrs, objp) + XDR *xdrs; + rpcb_entry *objp; + { +- if (!xdr_string(xdrs, >r_maddr, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_maddr, RPC_MAXDATASIZE)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >r_nc_netid, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_nc_netid, RPC_MAXDATASIZE)) { + return (FALSE); + } + if (!xdr_u_int32_t(xdrs, >r_nc_semantics)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >r_nc_protofmly, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_nc_protofmly, RPC_MAXDATASIZE)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >r_nc_proto, (u_int)~0)) { ++ if (!xdr_string(xdrs, >r_nc_proto, RPC_MAXDATASIZE)) { + return (FALSE); + } + return (TRUE); +@@ -292,7 +293,7 @@ xdr_rpcb_rmtcallres(xdrs, p) + bool_t dummy; + struct r_rpcb_rmtcallres *objp = (struct r_rpcb_rmtcallres *)(void *)p; + +- if (!xdr_string(xdrs, >addr, (u_int)~0)) { ++ if (!xdr_string(xdrs, >addr, RPC_MAXDATASIZE)) { + return (FALSE); + } + if (!xdr_u_int(xdrs, >results.results_len)) { +@@ -312,6 +313,11 @@ xdr_netbuf(xdrs, objp) + if (!xdr_u_int32_t(xdrs, (u_int32_t *) >maxlen)) { + return (FALSE); + } ++ ++ if (objp->maxlen > RPC_MAXDATASIZE) { ++ return (FALSE); ++ } ++ + dummy = xdr_bytes(xdrs, (char **)&(objp->buf), + (u_int *)&(objp->len), objp->maxlen); + return (dummy); +--- a/src/rpcb_st_xdr.c b/src/rpcb_st_xdr.c +@@ -38,6 +38,7 @@ + #include + + #include ++#include "rpc_com.h" + + /* Link list of all the stats about getport and getaddr */ + +@@ -59,7 +60,7 @@ xdr_rpcbs_addrlist(xdrs, objp) + if (!xdr_int(xdrs, >failure)) { + return (FALSE); + } +- if (!xdr_string(xdrs, >netid, (u_int)~0)) { ++ if (!xdr_string(xdrs, >netid, RPC_MAXDATASIZE)) { + return (FALSE); + } + +@@ -110,7 +111,7 @@ xdr_rpcbs_rmtcalllist(xdrs, objp) + IXDR_PUT_INT32(buf, objp->failure); + IXDR_PUT_INT32(buf, objp->indirect); + } +- if (!xdr_string(xdrs, >netid, (u_int)~0)) { ++ if (!xdr_string(xdrs, >netid, RPC_MAXDATASIZE)) { + return (FALSE); + } + if (!xdr_pointer(xdrs, (char **)>next, +@@ -148,7 +149,7 @@ xdr_rpcbs_rmtcalllist(xdrs, objp) + objp->failure = (int)IXDR_GET_INT32(buf); + objp->indirect =
Bug#861835: rpcbind: diff for NMU version 0.2.3-0.6
Dear maintainer, I've prepared an NMU for rpcbind (versioned as 0.2.3-0.6). The diff is attached to this message. Regards, Salvatore diff -Nru rpcbind-0.2.3/debian/changelog rpcbind-0.2.3/debian/changelog --- rpcbind-0.2.3/debian/changelog 2016-06-17 17:54:27.0 +0200 +++ rpcbind-0.2.3/debian/changelog 2017-05-05 19:46:00.0 +0200 @@ -1,3 +1,14 @@ +rpcbind (0.2.3-0.6) unstable; urgency=high + + * Non-maintainer upload. + * CVE-2017-8779: Memory leak when failing to parse XDR strings or bytearrays +(Closes: #861835) + * Bump runtime dependency on libtirpc1. +Bump Depends on libtirpc1 (>= 0.2.5-1.2~) to pull the fixes on libtirpc1 +for CVE-2017-8779. + + -- Salvatore BonaccorsoFri, 05 May 2017 19:46:00 +0200 + rpcbind (0.2.3-0.5) unstable; urgency=medium * Non-maintainer upload. diff -Nru rpcbind-0.2.3/debian/control rpcbind-0.2.3/debian/control --- rpcbind-0.2.3/debian/control 2016-05-30 17:59:16.0 +0200 +++ rpcbind-0.2.3/debian/control 2017-05-05 19:46:00.0 +0200 @@ -8,7 +8,7 @@ Package: rpcbind Architecture: any -Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 4.1+Debian3), libtirpc1 (>= 0.2.4-2~) +Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 4.1+Debian3), libtirpc1 (>= 0.2.5-1.2~) Conflicts: portmap Provides: portmap Breaks: libc-bin (<< 2.16) diff -Nru rpcbind-0.2.3/debian/patches/08-CVE-2017-8779.patch rpcbind-0.2.3/debian/patches/08-CVE-2017-8779.patch --- rpcbind-0.2.3/debian/patches/08-CVE-2017-8779.patch 1970-01-01 01:00:00.0 +0100 +++ rpcbind-0.2.3/debian/patches/08-CVE-2017-8779.patch 2017-05-05 19:46:00.0 +0200 @@ -0,0 +1,29 @@ +Description: CVE-2017-8779: Memory leak when failing to parse XDR strings or bytearrays +Origin: vendor +Bug: https://bugs.debian.org/861835 +Forwarded: not-needed +Author: Guido Vranken +Reviewed-by: Salvatore Bonaccorso +Last-Update: 2017-05-05 + +diff --git a/src/rpcb_svc_com.c b/src/rpcb_svc_com.c +index 5862c26..e11f61b 100644 +--- a/src/rpcb_svc_com.c b/src/rpcb_svc_com.c +@@ -48,6 +48,7 @@ + #include + #include + #include ++#include + #include + #include + #include +@@ -432,7 +433,7 @@ rpcbproc_taddr2uaddr_com(void *arg, struct svc_req *rqstp /*__unused*/, + static bool_t + xdr_encap_parms(XDR *xdrs, struct encap_parms *epp) + { +- return (xdr_bytes(xdrs, &(epp->args), (u_int *) &(epp->arglen), ~0)); ++ return (xdr_bytes(xdrs, &(epp->args), (u_int *) &(epp->arglen), RPC_MAXDATASIZE)); + } + + /* diff -Nru rpcbind-0.2.3/debian/patches/series rpcbind-0.2.3/debian/patches/series --- rpcbind-0.2.3/debian/patches/series 2015-11-10 13:01:01.0 +0100 +++ rpcbind-0.2.3/debian/patches/series 2017-05-05 19:46:00.0 +0200 @@ -4,3 +4,4 @@ run-migration CVE-2015-7236.patch 07-Delete-the-unix-socket-only-if-we-have-created-it.patch +08-CVE-2017-8779.patch
Bug#861212: the certificates file for the LDAP server that causes this bug
This is the large CA-bundle.crt file that when configured as the certificate bundle for the LDAP server, causes ldap-utils to fail with tls_read want/got mismatches early in the negotiation https://csde.washington.edu/~mbw/hide/ca-bundle.crt I'll leave this link up for at least 1 year Matt
Bug#861911: e-mem: FTBFS on non-x86: unrecognized command line option '-mpopcnt'
Source: e-mem Version: 0.0+20160706-1 Severity: important Tags: upstream Justification: fails to build from source Hi, me again. :-) Builds of e-mem for non-x86 architectures have been failing. The immediate error is g++: error: unrecognized command line option '-mpopcnt' but I suspect there may be deeper portability issues. Please take a look and either fix non-x86 builds or explicitly restrict the package to Architecture: any-amd64 any-i386 any-x32 so that other architectures' autobuilders know not to bother with it. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#861910: maradns-deadwood: deadwood is labeled stable by upstream, how about a full package?
Package: maradns-deadwood Version: 2.0.13-1.2 Severity: wishlist Hello, deadwood was released as stable by upstream. However the Debian package only provides a bare-bone binary without infrastructure (init-script/systemd support files). While the package description documents this no reason is given why. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#861112: xsane: always crashes on start
Hi, On Fri, May 05, 2017 at 03:33:34PM +0200, John Paul Adrian Glaubitz wrote: > There previously has been a race condition in the sane-backends net code > which Laurent Vivier found [1]. He had come up with a suggested patch to > address the issue, but the patch was never merged to the Debian package > or upstream, it seems. > > So, before we go ahead and completely remove a feature that some people > might be using, I would like to ask that we actually test the patch that > Laurent suggested and see it helps with the problem. Not having verified > that we have actually properly fixed the related bug #743420 [2], we cannot > be exclude this particular bug as the problem Aaro is seeing here. > > @Aaro: It would be nice if you could provide us with the backtrace of your >crash. sane-backends still has a dedicated -dbg package, for the >Avahi debug packages you will probably have to use Debian's debug >repository [2]. I think Jörg Frings-Fürst has analyzed and fixed this bug already - he provided me test packages (libsane_1.0.25-4~test1_amd64.deb etc.) offline for testing and they seemed to fix the issue. I'm currently away from my machines, but next week I'll recheck the situation again with up-to-date Debian testing, If the problem is still present I will provide the full backtrace etc. Thanks, A.
Bug#861903: groovy: Do not depend on junit4
Hi Mykola, Le 5/05/2017 à 17:33, Mykola Nikishov a écrit : > It seems junit4 is not required for package to function correctly, Recommends > or Suggests should be fine (like with dependency on testng). The groovy-test artifact depends on junit, so the dependency on the junit4 package must be preserved (unless we split the groovy package). testng is never used at runtime, so we could drop it from the recommended dependencies. Emmanuel Bourg
Bug#861909: postgrey: Please add whitelist entry for mail.alibaba.com
Package: postgrey Version: 1.35-1 Severity: normal Dear Maintainer, aliexpress.com and alibaba.com outgoing mail are handled by a large pool of outgoing MTA of the form mail123-456.mail.alibaba.com. I kindly request an appropriate entry be made for them in the default whitelist. Regards Rolf
Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test
Hi again Sorry wrong context. It is the problem for sure: Since it is used by AgsAutomationEditor, too. Joël On Fri, May 5, 2017 at 6:31 PM, Joël Krähemannwrote: > Hi > > The flag was set. However it is not that beautiful. > So it can't be the problem. > > https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/ags/X/ags_editor.c#n222 > > Bests, > Joël > > > On Fri, May 5, 2017 at 6:09 PM, James Cowgill wrote: >> Hi, >> >> On 05/05/17 13:36, Joël Krähemann wrote: >>> Hi >>> >>> finally I got a stack-trace >>> >>> Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1". >>> Core was generated by >>> `/home/jkraehemann/gsequencer-0.8.0/.libs/ags_xorg_application_context_test'. >>> Program terminated with signal SIGSEGV, Segmentation fault. >>> #0 0x75e2af68 in IA__gtk_widget_show_all (widget=0x7280b790) at >>> ./gtk/gtkwidget.c:3376 >>> 3376 ./gtk/gtkwidget.c: No such file or directory. >>> (gdb) >>> (gdb) bt >>> #0 0x75e2af68 in IA__gtk_widget_show_all (widget=0x7280b790) at >>> ./gtk/gtkwidget.c:3376 >>> #1 0x7677b6c8 in ags_machine_selector_popup_new >>> (machine_selector=0x728104c0) at >>> ags/X/editor/ags_machine_selector.c:569 >>> #2 0x766b60a4 in ags_automation_editor_init >>> (automation_editor=0x7276f238) at ags/X/ags_automation_editor.c:222 >>> #3 0x75660948 in g_type_create_instance () from >>> /usr/lib/mipsel-linux-gnu/libgobject-2.0.so.0 >>> Backtrace stopped: frame did not save the PC >> >> I ran this test in gdb on a real mips machine. When tracing through >> ags_machine_selector_popup_new it seems that the "keys" variable is >> never initialized and a garbage pointer is passed to gtk_widget_show_all. >> >> The variable is never initialized because this condition is false: >> (AGS_MACHINE_SELECTOR_SHOW_SHIFT_PIANO & (machine_selector->flags)) != 0 >> >> Thanks, >> James >>
Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test
Hi The flag was set. However it is not that beautiful. So it can't be the problem. https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/ags/X/ags_editor.c#n222 Bests, Joël On Fri, May 5, 2017 at 6:09 PM, James Cowgillwrote: > Hi, > > On 05/05/17 13:36, Joël Krähemann wrote: >> Hi >> >> finally I got a stack-trace >> >> Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1". >> Core was generated by >> `/home/jkraehemann/gsequencer-0.8.0/.libs/ags_xorg_application_context_test'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 0x75e2af68 in IA__gtk_widget_show_all (widget=0x7280b790) at >> ./gtk/gtkwidget.c:3376 >> 3376 ./gtk/gtkwidget.c: No such file or directory. >> (gdb) >> (gdb) bt >> #0 0x75e2af68 in IA__gtk_widget_show_all (widget=0x7280b790) at >> ./gtk/gtkwidget.c:3376 >> #1 0x7677b6c8 in ags_machine_selector_popup_new >> (machine_selector=0x728104c0) at >> ags/X/editor/ags_machine_selector.c:569 >> #2 0x766b60a4 in ags_automation_editor_init >> (automation_editor=0x7276f238) at ags/X/ags_automation_editor.c:222 >> #3 0x75660948 in g_type_create_instance () from >> /usr/lib/mipsel-linux-gnu/libgobject-2.0.so.0 >> Backtrace stopped: frame did not save the PC > > I ran this test in gdb on a real mips machine. When tracing through > ags_machine_selector_popup_new it seems that the "keys" variable is > never initialized and a garbage pointer is passed to gtk_widget_show_all. > > The variable is never initialized because this condition is false: > (AGS_MACHINE_SELECTOR_SHOW_SHIFT_PIANO & (machine_selector->flags)) != 0 > > Thanks, > James >
Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test
Hi, On 05/05/17 13:36, Joël Krähemann wrote: > Hi > > finally I got a stack-trace > > Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1". > Core was generated by > `/home/jkraehemann/gsequencer-0.8.0/.libs/ags_xorg_application_context_test'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x75e2af68 in IA__gtk_widget_show_all (widget=0x7280b790) at > ./gtk/gtkwidget.c:3376 > 3376 ./gtk/gtkwidget.c: No such file or directory. > (gdb) > (gdb) bt > #0 0x75e2af68 in IA__gtk_widget_show_all (widget=0x7280b790) at > ./gtk/gtkwidget.c:3376 > #1 0x7677b6c8 in ags_machine_selector_popup_new > (machine_selector=0x728104c0) at > ags/X/editor/ags_machine_selector.c:569 > #2 0x766b60a4 in ags_automation_editor_init > (automation_editor=0x7276f238) at ags/X/ags_automation_editor.c:222 > #3 0x75660948 in g_type_create_instance () from > /usr/lib/mipsel-linux-gnu/libgobject-2.0.so.0 > Backtrace stopped: frame did not save the PC I ran this test in gdb on a real mips machine. When tracing through ags_machine_selector_popup_new it seems that the "keys" variable is never initialized and a garbage pointer is passed to gtk_widget_show_all. The variable is never initialized because this condition is false: (AGS_MACHINE_SELECTOR_SHOW_SHIFT_PIANO & (machine_selector->flags)) != 0 Thanks, James signature.asc Description: OpenPGP digital signature
Bug#861908: gsequencer: testsuite crashes if AddressSanitizer is enabled
Source: gsequencer Version: 0.8.0-1 Severity: important Hi, While looking at #861645 I noticed that the gsequencer testsuite crashes on x86 with a heap buffer overflow when AddressSanitizer (-fsanitize=address) is enabled. FAIL: ags_midi_buffer_util_test === CUnit - A unit testing framework for C - Version 2.1-3 http://cunit.sourceforge.net/ Suite: AgsMidiBufferUtilTest Test: test of ags_midi_buffer_util.c get varlength size ...passed Test: test of ags_midi_buffer_util.c put varlength ...passed Test: test of ags_midi_buffer_util.c get varlength ...passed Test: test of ags_midi_buffer_util.c put int16 ...passed Test: test of ags_midi_buffer_util.c get int16 ...passed Test: test of ags_midi_buffer_util.c put int24 ...passed Test: test of ags_midi_buffer_util.c get int24 ...passed Test: test of ags_midi_buffer_util.c put int32 ...passed Test: test of ags_midi_buffer_util.c get int32 ...passed Test: test of ags_midi_buffer_util.c put header ... ** (process:4236): WARNING **: invalid chunk length ** (process:4236): WARNING **: invalid chunk length FAILED 1. ags/test/audio/midi/ags_midi_buffer_util_test.c:518 - success == TRUE 2. ags/test/audio/midi/ags_midi_buffer_util_test.c:535 - success == TRUE Test: test of ags_midi_buffer_util.c get header ...passed Test: test of ags_midi_buffer_util.c put track ...passed Test: test of ags_midi_buffer_util.c get track ...passed Test: test of ags_midi_buffer_util.c put key on ...passed Test: test of ags_midi_buffer_util.c get key on ...passed Test: test of ags_midi_buffer_util.c put key off ...passed Test: test of ags_midi_buffer_util.c get key off ...passed Test: test of ags_midi_buffer_util.c put key pressure ...passed Test: test of ags_midi_buffer_util.c get key pressure ...passed Test: test of ags_midi_buffer_util.c put change parameter ...passed Test: test of ags_midi_buffer_util.c get change parameter ...passed Test: test of ags_midi_buffer_util.c put change pitch bend ...passed Test: test of ags_midi_buffer_util.c get change pitch bend ...passed Test: test of ags_midi_buffer_util.c put change program ...FAILED 1. ags/test/audio/midi/ags_midi_buffer_util_test.c:1044 - success == TRUE Test: test of ags_midi_buffer_util.c get change program ...= ==4236==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020dff6 at pc 0x7f0b047bfd7b bp 0x7fff86d9a050 sp 0x7fff86d99800 WRITE of size 3 at 0x6020dff6 thread T0 #0 0x7f0b047bfd7a (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x5cd7a) #1 0x5618bff665ad in memcpy /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 0x5618bff665ad in ags_midi_buffer_util_test_get_change_program ags/test/audio/midi/ags_midi_buffer_util_test.c:1073 #3 0x7f0b03741396 (/usr/lib/x86_64-linux-gnu/libcunit.so.1+0x4396) #4 0x7f0b037416cf (/usr/lib/x86_64-linux-gnu/libcunit.so.1+0x46cf) #5 0x7f0b03741a1d in CU_run_all_tests (/usr/lib/x86_64-linux-gnu/libcunit.so.1+0x4a1d) #6 0x5618bff63203 in main ags/test/audio/midi/ags_midi_buffer_util_test.c:3257 #7 0x7f0b00fdb2b0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b0) #8 0x5618bff63269 in _start (/build/gsequencer-8YtPr4/gsequencer-0.8.0/.libs/ags_midi_buffer_util_test+0x7269) 0x6020dff6 is located 0 bytes to the right of 6-byte region [0x6020dff0,0x6020dff6) allocated by thread T0 here: #0 0x7f0b04824d28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28) #1 0x5618bff663ff in ags_midi_buffer_util_test_get_change_program ags/test/audio/midi/ags_midi_buffer_util_test.c:1057 SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x5cd7a) Shadow bytes around the buggy address: 0x0c047fff9ba0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9bb0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9bc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9bd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff9be0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c047fff9bf0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa[06]fa 0x0c047fff9c00: fa fa 00 00 fa fa 06 fa fa fa 07 fa fa fa 07 fa 0x0c047fff9c10: fa fa 07 fa fa fa 07 fa fa fa 07 fa fa fa 07 fa 0x0c047fff9c20: fa fa 07 fa fa fa 07 fa fa fa 07 fa fa fa 07 fa 0x0c047fff9c30: fa fa 00 fa fa fa 00 00 fa fa fd fa fa fa fd fa 0x0c047fff9c40: fa fa 00 00 fa fa 00 07 fa fa 00 07 fa fa 04 fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global
Bug#661954: ssmtp: ssmtp.conf is world readable
Package: ssmtp Version: 2.64-8+b2 Followup-For: Bug #661954 Dear Maintainer, Just sending a "me too" in hopes that the patch will accepted and this bug will go away. We're up to Debian 9 now. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-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 ssmtp depends on: ii debconf [debconf-2.0] 1.5.60 ii libc6 2.24-10 ii libgnutls-openssl273.5.8-5 ssmtp recommends no packages. ssmtp suggests no packages. -- Configuration Files: /etc/logcheck/ignore.d.server/ssmtp [Errno 13] Permission denied: '/etc/logcheck/ignore.d.server/ssmtp' /etc/ssmtp/revaliases changed [not included] -- debconf information excluded
Bug#860735: CVE-2017-7942: memory leak in avs does not affect old version
control: notfound -1,8:6.6.0.4-3 control: notfound -1 8:6.7.7.10-5 control: notfound -1 8:6.8.9.9-5 control: notfound -1 8:6.8.9.9-5+deb8u8 control: notfound -1 8:6.7.7.10-5+deb7u13 > > Due to code change not affected
Bug#861907: scrot not supporting multiple displays
Package: scrot Version: 0.8-18 Severity: normal Dear Maintainer, Trying to use scrot -m or --multidisp doesn't appear to work. Man page says it should grab a shot from each display and then merge the image, however it only appears to be taking a shot from one. Is there something else that has to be configured/installed to allow this to work? -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-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 scrot depends on: ii giblib11.2.4-11 ii libc6 2.24-10 ii libimlib2 1.4.8-1 ii libx11-6 2:1.6.4-3 scrot recommends no packages. scrot suggests no packages. -- no debconf information
Bug#861906: courier-maildrop: Documentation typo
Package: courier-maildrop Severity: minor During the installation of courier-maildrop package a dialog appears that warns the user with the following sentence: Default mail deliver location in the maildrop package is /var/spool/mail and to change it back again to ~/Maildrop you need to uncomment following line in the /etc/maildroprc: DEFAULT="$HOME/Maildir" It should read: Default mail deliver location in the maildrop package is /var/spool/mail and to change it back again to ~/Maildir you need to uncomment following line in the /etc/maildroprc: DEFAULT="$HOME/Maildir" instead. Please note the difference between "~/Maildrop" and "~/Maildir". -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (998, 'testing'), (994, 'unstable'), (700, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#861905: unblock: pyosmium/2.11.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pyosmium Upstream has only fixed bugs for this release in line with the freeze policy. unblock pyosmium/2.11.1-1 Kind Regards, Bas diff -Nru pyosmium-2.11.0/CHANGELOG.md pyosmium-2.11.1/CHANGELOG.md --- pyosmium-2.11.0/CHANGELOG.md2017-01-15 15:39:17.0 +0100 +++ pyosmium-2.11.1/CHANGELOG.md2017-05-04 23:36:03.0 +0200 @@ -13,6 +13,19 @@ ### Fixed +## [2.11.1] - 2017-05-04 + +### Added + +### Changed + +### Fixed + +- prevent unnecessary calls to callbacks +- correctly throw KeyError in taglist accessor +- fix output type of index.map_types() function +- don't overgrow writer buffers over requested size + ## [2.11.0] - 2017-01-15 ### Changed @@ -123,7 +136,8 @@ - Exception not caught in test. -[unreleased]: https://github.com/osmcode/pyosmium/compare/v2.11.0...HEAD +[unreleased]: https://github.com/osmcode/pyosmium/compare/v2.11.1...HEAD +[2.11.1]: https://github.com/osmcode/pyosmium/compare/v2.11.0...v2.11.1 [2.11.0]: https://github.com/osmcode/pyosmium/compare/v2.10.2...v2.11.0 [2.10.2]: https://github.com/osmcode/pyosmium/compare/v2.9.0...v2.10.2 [2.9.0]: https://github.com/osmcode/pyosmium/compare/v2.8.0...v2.9.0 diff -Nru pyosmium-2.11.0/debian/changelog pyosmium-2.11.1/debian/changelog --- pyosmium-2.11.0/debian/changelog2017-01-17 18:45:04.0 +0100 +++ pyosmium-2.11.1/debian/changelog2017-05-05 09:51:21.0 +0200 @@ -1,3 +1,15 @@ +pyosmium (2.11.1-1) unstable; urgency=medium + + * New upstream bugfix release. +- Prevent unnecessary calls to callbacks +- Correctly throw KeyError in taglist accessor +- Fix output type of index.map_types() function +- Don't overgrow writer buffers over requested size + * Update branch in gbp.conf & Vcs-Git URL. + * Limit watch file to 2.11.x releases. + + -- Bas CouwenbergFri, 05 May 2017 09:51:21 +0200 + pyosmium (2.11.0-1) unstable; urgency=medium * Move from experimental to unstable. diff -Nru pyosmium-2.11.0/debian/control pyosmium-2.11.1/debian/control --- pyosmium-2.11.0/debian/control 2017-01-15 21:46:51.0 +0100 +++ pyosmium-2.11.1/debian/control 2017-05-05 09:48:33.0 +0200 @@ -23,7 +23,7 @@ zlib1g-dev Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/pyosmium.git/ -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/pyosmium.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/pyosmium.git -b stretch Homepage: http://osmcode.org/pyosmium/ Package: python-pyosmium diff -Nru pyosmium-2.11.0/debian/gbp.conf pyosmium-2.11.1/debian/gbp.conf --- pyosmium-2.11.0/debian/gbp.conf 2016-11-27 10:29:05.0 +0100 +++ pyosmium-2.11.1/debian/gbp.conf 2017-05-05 09:48:33.0 +0200 @@ -2,11 +2,11 @@ # The default name for the upstream branch is "upstream". # Change it if the name is different (for instance, "master"). -upstream-branch = upstream +upstream-branch = upstream-2.11 # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru pyosmium-2.11.0/debian/watch pyosmium-2.11.1/debian/watch --- pyosmium-2.11.0/debian/watch2016-10-26 21:36:51.0 +0200 +++ pyosmium-2.11.1/debian/watch2017-05-05 09:48:33.0 +0200 @@ -4,4 +4,4 @@ uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\ filenamemangle=s/(?:.*\/)?(?:rel|v|pyosmium)[\-\_]?(\d[\d\-\.]+)\.(tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))/pyosmium-$1.$2/ \ https://github.com/osmcode/pyosmium/releases \ -(?:.*/)?(?:rel|v|pyosmium)[\-\_]?(\d[\d\-\.]+)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) +(?:.*/)?(?:rel|v|pyosmium)[\-\_]?(2\.11\.\d[\d\-\.]*)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) diff -Nru pyosmium-2.11.0/lib/generic_handler.hpp pyosmium-2.11.1/lib/generic_handler.hpp --- pyosmium-2.11.0/lib/generic_handler.hpp 2017-01-15 15:39:17.0 +0100 +++ pyosmium-2.11.1/lib/generic_handler.hpp 2017-05-04 23:36:03.0 +0200 @@ -104,45 +104,46 @@ struct SimpleHandlerWrap: BaseHandler, wrapper { void node(const osmium::Node& node) const { -if (override f = this->get_override("node")) -f(boost::ref(node)); -} +if (!(m_callbacks & osmium::osm_entity_bits::node)) +return; -void default_node(const osmium::Node&) const { +if (override f = this->get_override("node")) { +f(boost::ref(node)); +} } void way(const osmium::Way& way) const { +if (!(m_callbacks & osmium::osm_entity_bits::way)) +return; + if (override f = this->get_override("way"))
Bug#860051: praat: Crashes on any attempt to run
The problem persists using the testing version of the package. I believe the problem with running praat is that my system lacks a monitor. I can only access it through the terminal, but it crashes, even when I only try to run a script that has no GUI-based IO. For a specific instance, I ran the command praat --open "getPitchTier.Praat", where getPitchTier.Praat contains the following contents: Read from file: "sentence.wav" selectObject: "Sound sentence" To Manipulation: 0.01, 75, 600 Extract pitch tier Save as PitchTier spreadsheet file: "oldPitchTier.PitchTier" However, praat crashes regardless of input given. - Alex On Fri, May 5, 2017 at 8:21 AM, Rafael Laboissièrewrote: > Control: tags -1 + moreinfo unreproducible > > Thank you for the bug report. I cannot reproduce it in my system and I am > hereby requesting Assistance in diagnosing the cause of the problem. > > Could you please check whether the problem persists using the testing or > the experimental versions of the package ? > > Best, > > Rafael Laboissière > > * Alex Hedges [2017-04-10 16:33]: > > > Package: praat >> Version: 5.4.0-1 >> Severity: important >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >> * What led up to the situation? >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> * What was the outcome of this action? >> * What outcome did you expect instead? >> >> *** End of the template - remove these template lines *** >> >> When I invoke `praat' without arguments from an ordinary shell prompt, it >> crashes and displays error messages. Here is a transcript: >> >> $ praat >> >> (praat:9464): GLib-GObject-WARNING **: invalid (NULL) pointer instance >> >> (praat:9464): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion >> 'G_TYPE_CHECK_INSTANCE (instance)' failed >> >> (praat:9464): Gtk-WARNING **: Screen for GtkWindow not set; you must >> always set a screen for a GtkWindow before using the window >> >> (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: >> assertion 'GDK_IS_SCREEN (screen)' failed >> >> (praat:9464): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion >> 'GDK_IS_COLORMAP (colormap)' failed >> >> (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: >> assertion 'GDK_IS_SCREEN (screen)' failed >> >> (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion >> 'GDK_IS_SCREEN (screen)' failed >> >> (praat:9464): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion >> 'GDK_IS_SCREEN (screen)' failed >> >> (praat:9464): Gdk-CRITICAL **: IA__gdk_window_new: assertion >> 'GDK_IS_WINDOW (parent)' failed Segmentation fault >> >> >> -- System Information: Debian Release: 8.7 APT prefers stable-updates >> APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf >> (armv7l) >> >> Kernel: Linux 4.4.30-ti-r64 (SMP w/1 CPU core) >> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> >> Versions of packages praat depends on: ii libatk1.0-0 2.14.0-1 >> ii libc62.19-18+deb8u7 ii libcairo2 >> 1.14.0-2.1+deb8u2 ii libfontconfig1 2.11.0-6.3+deb8u1 ii >> libfreetype6 2.5.2-3+deb8u1 ii libgcc1 1:4.9.2-10 ii >> libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.42.1-1+b1 >> ii libgtk2.0-0 2.24.25-3+deb8u1 ii libpango-1.0-0 1.36.8-3 >> ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii >> libstdc++6 4.9.2-10 ii oss-compat 6 ii python >>2.7.9-1 >> >> Versions of packages praat recommends: ii xfonts-100dpi 1:1.0.3 ii >> xfonts-75dpi 1:1.0.3 >> >> praat suggests no packages. >> >> -- no debconf information >> >> >>
Bug#861904: qtikz: Strange leading character added to newly created file.
Package: qtikz Version: 0.11~git20161122-1 Severity: normal Dear Maintainer, I have been noticing a strange behavior in qtikz when adding the tikzpicture environment to new tikz files. * qtikz * Add tikzpicture environment * Save as e.g. test.tikz Saved file (attached as "test.tikz") contains an spurious leading character. This seems to only happen first time new file is written, no matter what command is put by qtikz (not only tikzpicture). Note that this char is not easily seen in all editors, I can see it in joe and mc viewer. To make this more clear I have also attached as "test-stripped.tikz" " the same file, but with that char removed. Regards, -- Agustin \begin{tikzpicture} \end{tikzpicture}\begin{tikzpicture} \end{tikzpicture}
Bug#861903: groovy: Do not depend on junit4
Package: groovy Version: 2.4.8-1 Severity: minor It seems junit4 is not required for package to function correctly, Recommends or Suggests should be fine (like with dependency on testng). -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (70, 'unstable'), (60, 'testing'), (50, 'experimental'), (40, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) 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 groovy depends on: ii antlr2.7.7+dfsg-7 ii default-jre-headless [java6-runtime-headless]2:1.8-58 ii ivy 2.4.0-3 ii junit4 4.12-4 ii libasm-java 5.2-2 ii libbsf-java 1:2.4.0-5 ii libcommons-cli-java 1.3.1-3 ii libcommons-logging-java 1.2-1 ii libjansi-java1.14-1 ii libjline2-java 2.11-4 ii libqdox-java 1.12.1-2 ii libservlet3.1-java 8.5.12-1 ii libxstream-java 1.4.9-1 ii openjdk-8-jre-headless [java6-runtime-headless] 8u131-b11-1 Versions of packages groovy recommends: ii ant 1.9.9-1 ii ant-optional 1.9.9-1 pn libgpars-groovy-java pn libjcommander-java pn testng Versions of packages groovy suggests: ii groovy-doc 2.4.8-1 -- no debconf information
Bug#861781: www.debian.org: updating Debian memberships in other organisations information
If you want to, I can apply. On Fri, May 05, 2017 at 09:41:29AM +0800, Paul Wise wrote: > On Fri, 2017-05-05 at 09:38 +0800, Raphael Hertzog wrote: > > On Thu, 04 May 2017, Paul Wise wrote: > > > Reconfirm the involvement of these representatives: > > > SchoolForge (representatives: Ben Armstrong*, Raphaël Hertzog) > > > > You can drop me as representative here. > > Since Ben is retired from Debian and Raphaël has said he is no longer > involved in SchoolForge, are any of the DebianEdu folks interested in > having Debian re-join SchoolForge and representing Debian there? > > http://www.schoolforge.net/ > https://www.debian.org/misc/memberships > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise -- José Gatica A. ParrotSec Ambassador - Debian Wiki https://docs.parrotsec.org/doku.php/user/josegatica https://wiki.debian.org/JoseGatica www.josegatica.cl --- Libérate de los grilletes digitales del software privativo. --- USA SOFTWARE LIBRE --- Más info en http://www.fsf.org y en http://www.gnu.org También puedes visitar http://www.stallman.org - No imprimas este mensaje a menos que sea estrictamente necesario. Tenemos una inmensa deuda con nuestro Medio Ambiente.
Bug#850440: jessie-pu: package w3m/0.5.3-19+deb8u2
On April 28, 2017 at 7:18PM +0100, adam (at adam-barratt.org.uk) wrote: >> >> w3m (0.5.3-19+deb8u2) jessie; urgency=medium >> >> >> >> * Fix multiple vulnerabilities (closes: #850432) > > Thanks. If you're still interested in doing this, please feel free to > upload. Uploaded. Thanks, -- Tatsuya Kinoshita pgpumae_9MF_d.pgp Description: PGP signature
Bug#861872: Tomcat fails to serve png images
>What Connector protocol do you use? The default of protocol="HTTP/1.1". The APR libraries are available and the startup logs say Starting ProtocolHandler ["http-apr-8080"]. Interestingly if I change the config to explicitly set protocol="org.apache.coyote.http11.Http11Protocol" or protocol="org.apache.coyote.http11.Http11NioProtocol" or protocol="org.apache.coyote.http11.Http11AprProtocol" the bug doesn’t appear. May 05, 2017 3:51:32 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-apr-8080"] May 05, 2017 3:51:32 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8082"] May 05, 2017 3:51:32 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-nio-8083"] May 05, 2017 3:51:32 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-apr-8084"] May 05, 2017 3:51:32 PM org.apache.catalina.startup.Catalina start INFO: Server startup in ^C # wget http://localhost:8080/path/to/image.png --2017-05-05 15:51:53-- http://localhost:8080/path/to/image.png Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... 200 OK Length: 249343 (243K) [image/png] Saving to: `image.png.1' 91% [==> ] 229,376 --.-K/s eta 1s ^C # wget http://localhost:8084/path/to/image.png --2017-05-05 15:52:10-- http://localhost:8084/path/to/image.png Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8084... connected. HTTP request sent, awaiting response... 200 OK Length: 249343 (243K) [image/png] Saving to: `image.png.2' 100%[===>] 249,343 --.-K/s in 0.001s 2017-05-05 15:52:10 (164 MB/s) - `image.png.2' saved [249343/249343] # wget http://localhost:8083/path/to/image.png --2017-05-05 15:52:18-- http://localhost:8083/path/to/image.png Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8083... connected. HTTP request sent, awaiting response... 200 OK Length: 249343 (243K) [image/png] Saving to: `image.png.3' 100%[===>] 249,343 --.-K/s in 0.005s 2017-05-05 15:52:18 (46.7 MB/s) - `image.png.3' saved [249343/249343] # wget http://localhost:8082/path/to/image.png --2017-05-05 15:52:26-- http://localhost:8082/path/to/image.png Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8082... connected. HTTP request sent, awaiting response... 200 OK Length: 249343 (243K) [image/png] Saving to: `image.png.4' 100%[===>] 249,343 --.-K/s in 0.001s 2017-05-05 15:52:26 (214 MB/s) - `image.png.4' saved [249343/249343] -- This e mail and any attachments are confidential. If you are not the intended recipient, please notify us immediately by replying to the sender by e mail and delete it from your system. E mail messages sent via the internet may not be secure and may be susceptible to data corruption, interception and unauthorised amendment, over which we have no control. The recipient is responsible for ensuring that the transmission, opening or use of this message and any attachments will not adversely affect its systems or data. We do not accept liability for any errors arising from transmission or for any loss or damage suffered as a result of this email and/or its attachments being communicated to anyone other than the intended recipient. eValue Limited, company number 7382500 Advisa Centa Limited, company number 7528200 Moneybee Limited, company number 7604100 Each company is registered in England and Wales with its registered office at Benyon House, Newbury Business Park, Newbury, Berks., RG14 2PZ. Moneybee Limited is authorised and regulated by the Financial Conduct Authority.
Bug#861834: libtirpc: CVE-2017-8779
Hi Anibal, Moritz prepared corresponding updates for jessie-security, I might help preparing updates for sid -> stretch. Regards, Salvatore
Bug#861736: Bug on NeXus library
Additional information: Storing using 'w' format (hdf4), instead of using 'w5' format (hdf5); the error does not appear: import nxs e = nxs.NXentry(name= "NXtomo") e.save("filenamenxs.h5",*'**w**'*)
Bug#861754: libpll: FTBFS on non-x86: x86intrin.h: No such file or directory
Control: tags -1 pending On Fri, May 05, 2017 at 09:44:46AM -0400, Aaron M. Ucko wrote: > Please try moving #include up to before the check for > HAVE_X86INTRIN_H, which will otherwise still be undefined at that point. Thanks, patch updated, pending upload after discussing #861755 with upstream. Andreas. -- http://fam-tille.de
Bug#861902: [gnome-core] Installing gnome-core precises apache2-bin and libapache2-mod-dnssd
Package: gnome-core Version: 1.3.22+2 Severity: minor --- Please enter the report below this line. --- Installing the gnome-core package in debian SID forces to install apache2-bin and libapache2-mod-dnssd. Both packages shouldn't be needed for a full gnome shell session. --- System information. --- Architecture: Kernel: Linux 4.9.0-2-amd64 Debian Release: 9.0 500 unstable ftp.debian.org 500 stable dl.google.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.