Bug#900546: dput: display the body of http error responses
Hello, Would you consider the patch that I have submitted on salsa? - https://salsa.debian.org/debian/dput-ng/merge_requests/1 Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#804579: Ncurses
Ncurses dep must be set by swi prolog compiler, when creating a binary from logol prolog files. Logol itself does nothing related to this lib. If compiler adds some unused deps, can't really fix that. Why setting this to serious? Olivier
Bug#900525: savi FTCBFS: uses the build architecture compiler
Control: tags -1 pending Hi Helmut, Thanks for the patch, I've applied it in git and will be included in the next upload to unstable. Kind Regards, Bas
Bug#900546: dput: display the body of http error responses
Package: dput-ng Severity: wishlist Hello, I am building a service that accepts uploads via dput. My service does a number of checks when it receives uploads. For example, it only accepts source uploads. If you upload a .deb, my service returns a 400 error with a message: - "Only source uploads are accepted" Or: - "this file was signed with an unrecognized key" Etc... I would love it if these messages made it to the user! Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#900545: dput: display the body of http errors responses
Package: dput Severity: wishlist Hello, I am building a service that accepts uploads via dput. My service does a number of checks when it receives uploads. For example, it only accepts source uploads. If you upload a .deb, my service returns a 400 error with a message: - "Only source uploads are accepted" Or: - "this file was signed with an unrecognized key" Etc... I would love it if these messages made it to the user! Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#896706: pcbnew: crashes with a failed assertion on i386, starts fine on amd64
Hi, On Fri, Jun 01, 2018 at 01:55:40AM +0200, Mirko Parthey wrote: > It happens in both situations. When pcbnew is started from the manager, > the same message is printed and the manager also aborts. o.k. That leads to an issue in pcbnew only. > > This is no crash? > > Well, what do you consider a crash? > pcbnew does not display any GUI before terminating. That's something I'd calling a crash. The difference to an assertation is the termination of the program without any chance for saving my workspace. KiCad uses some techniques to not segfaulting in circumstances and shows a assert message then. So there is one more thing you could provide then. Please create a gdb backtrace, this is helpful for the developers as they can see some useful information mostly what's the reason for the segfault. https://wiki.debian.org/HowToGetABacktrace PS: Due the curl transition the packages from experimental aren't usable anymore as thy are using Curl3. I uploaded yesterday KiCad into unstable, now with using Curl4 instead. You will probbaly need to pull the newer packages from there. > > I opened a new upstream bug report about this. > > > > https://bugs.launchpad.net/kicad/+bug/1774316 > > > > Please check if the system information is correct so far within the bug > > report. > > Looks OK to me. > This is the diff from your bugreport to my version info: > > --- kicad-bugreport.txt 2018-06-01 01:35:35.095539211 +0200 > +++ kicad-versioninfo.txt 2018-06-01 01:37:18.614939232 +0200 > @@ -5,2 +5,2 @@ > -libcurl/7.58.0 OpenSSL/1.0.2o zlib/1.2.11 libidn2/2.0.4 libpsl/0.20.1 > (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.31.1 librtmp/2.3 > -Platform: Linux 4.16.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK > +libcurl/7.60.0 OpenSSL/1.0.2o zlib/1.2.11 libidn2/2.0.4 libpsl/0.20.1 > (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.32.0 librtmp/2.3 > +Platform: Linux 4.16.0-1-686-pae i686, 32 bit, Little endian, wxGTK Yep, as expected, the only difference here is the used kernel. Regards Carsten
Bug#896667: transition: r-base-3.5
On Thu, May 31, 2018 at 09:25:50AM +0200, Emilio Pozuelo Monfort wrote: > > Cool, it's almost built everywhere now. Question: The arch:all packages are not yet marked green despite I've uploaded more then 50% more than 8 hours ago. Is there any reason for a delay in the display? BTW, I'd consider the table more logical if the arch:all packages would get a single column - that would also have the advantage that these are easier to spot. Kind regards Andreas. -- http://fam-tille.de
Bug#900544: flowblade: Segfaults on startup
Package: flowblade Version: 1.12-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed flowblade. sudo apt-get install flowblade * What exactly did you do (or not do) that was effective (or ineffective)? Ran flowblade. * What was the outcome of this action? Segfault. Output and dmesg report attached after these questions. * What outcome did you expect instead? A running program or a graceful exit. [charlie@dicke:~]$ flowblade FLOWBLADE MOVIE EDITOR 1.12 --- Launch script dir: /usr/bin Running from installation... modules path: /usr/share/flowblade/Flowblade MLT found, version: 6.8.0 (flowblade:22604): dbind-WARNING **: 20:20:25.971: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. OS: Debian GNU/Linux buster/sid Python 2.7.15 (default, May 1 2018, 05:55:50) [GCC 7.3.0] GTK+ version: 3.22.29 User dir: /home/charlie/.flowblade/ Locale: en_US Translations at /usr/share/locale were not found, using program root directory translations. Use OS locale language. 1920 1080 Small height: False Small width: False Detecting environment... --- video_codecs: - a64multi - a64multi5 - alias_pix - amv - apng - asv1 - asv2 - avrp - avui - ayuv - bmp - cinepak - cljr - dnxhd - dpx - dvvideo - ffv1 - ffvhuff - fits - flashsv - flashsv2 - flv - gif - h261 - h263 - h263p - hap - huffyuv - jpeg2000 - jpegls - ljpeg - mjpeg - mpeg1video - mpeg2video - mpeg4 - msmpeg4v2 - msmpeg4 - msvideo1 - pam - pbm - pcx - pgm - pgmyuv - png - ppm - prores - prores_aw - prores_ks - qtrle - r10k - r210 - rawvideo - roqvideo - rv10 - rv20 - sgi - snow - sunrast - svq1 - targa - tiff - utvideo - v210 - v308 - v408 - v410 - vc2 - wrapped_avframe - wmv1 - wmv2 - xbm - xface - xwd - y41p - yuv4 - zlib - zmbv - libopenjpeg - libtheora - libvpx - libvpx-vp9 - libwebp_anim - libwebp - libx264 - libx264rgb - libx265 - libxvid - h264_nvenc - h264_omx - h264_vaapi - nvenc - nvenc_h264 - nvenc_hevc - hevc_nvenc - hevc_vaapi - mjpeg_vaapi - mpeg2_vaapi - vp8_vaapi - vp9_vaapi ... --- audio_codecs: - comfortnoise - s302m - aac - ac3 - ac3_fixed - alac - dca - eac3 - flac - g723_1 - mlp - mp2 - mp2fixed - nellymoser - opus - real_144 - sonic - sonicls - truehd - tta - vorbis - wavpack - wmav1 - wmav2 - pcm_alaw - pcm_f32be - pcm_f32le - pcm_f64be - pcm_f64le - pcm_mulaw - pcm_s8 - pcm_s8_planar - pcm_s16be - pcm_s16be_planar - pcm_s16le - pcm_s16le_planar - pcm_s24be - pcm_s24daud - pcm_s24le - pcm_s24le_planar - pcm_s32be - pcm_s32le - pcm_s32le_planar - pcm_s64be - pcm_s64le - pcm_u8 - pcm_u16be - pcm_u16le - pcm_u24be - pcm_u24le - pcm_u32be - pcm_u32le - roq_dpcm - adpcm_adx - g722 - g726 - g726le - adpcm_ima_qt - adpcm_ima_wav - adpcm_ms - adpcm_swf - adpcm_yamaha - libgsm - libgsm_ms - libmp3lame - libopus - libshine - libspeex - libtwolame - libvorbis - libwavpack ... --- formats: - a64 - ac3 - adts - adx - aiff - amr - apng - asf - ass - ast - asf_stream - au - avi - avm2 - bit - caf - cavsvideo - crc - dash - data - daud - dirac - dnxhd - dts - dv - eac3 - f4v - ffm - ffmetadata - fifo - filmstrip - fits - flac - flv - framecrc - framehash - framemd5 - g722 - g723_1 - g726 - g726le - gif - gsm - gxf - h261 - h263 - h264 - hash - hds - hevc - hls - ico - ilbc - image2 - image2pipe - ipod - ircam - ismv - ivf - jacosub - latm - lrc - m4v - md5 - matroska - matroska - microdvd - mjpeg - mlp - mmf - mov - mp2 - mp3 - mp4 - mpeg - vcd - mpeg1video - dvd - svcd - mpeg2video - vob - mpegts - mpjpeg - mxf - mxf_d10 - mxf_opatom - null - nut - oga - ogg - ogv - oma - opus - alaw - mulaw - f64be - f64le - f32be - f32le - s32be - s32le - s24be - s24le - s16be - s16le - s8 - u32be - u32le - u24be - u24le - u16be - u16le - u8 - psp - rawvideo - rm - roq - rso - rtp - rtp_mpegts - rtsp - sap - scc - segment - stream_segment,ssegment - singlejpeg - smjpeg - smoothstreaming - sox - spx - spdif - srt - sup - swf - tee - 3g2 - 3gp - mkvtimestamp_v2 - truehd - tta - uncodedframecrc - vc1 - vc1test - voc - w64 - wav - webm - webm_dash_manifest - webm_chunk - webp - webvtt -
Bug#900543: RFS: qtox/1.15.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "qtox" * Package name: qtox Version : 1.15.0-1 Upstream Author : John Smith * URL : https://github.com/tux3/qTox * License : GPL Section : net It builds those binary packages: qtox - Powerful Tox client that follows the Tox design guidelines To access further information about this package, please visit the following URL: https://mentors.debian.net/package/qtox Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/q/qtox/qtox_1.15.0-1.dsc More information about hello can be obtained from https://www.example.com. Regards, Yangfl
Bug#898391:
What is the state of this? I am on stretch backports trying to upgrade from 390.48-2~bpo9+1 (everything working fine) to 390.48-2~bpo9+3. I am experiencing something which is another symptom of this bug. Many packets are held back. I believe the fundamental problem lies with nvidia-driver : Depends: nvidia-driver-libs (= 390.48-2~bpo9+3) but it is not going to be installed or nvidia-driver-libs-nonglvnd (= 390.48-2~bpo9+3) but it is not going to be installed I am on stretch backports trying to upgrade from 390.48-2~bpo9+1 (everything working fine) to 390.48-2~bpo9+3
Bug#900542: winbind: Can't upgrade winbind to 2:4.5.12+dfsg-2+deb9u2(stretch) or 2:4.7.4+dfsg-2(buster)
Package: winbind Version: 2:4.7.4+dfsg-2 Severity: normal Tags: a11y Dear Maintainer, When I try to apt-get upgrade, winbind can't complete its process. There are some problems. 1) Launch script can't work error: /lib/security/pam_winbind.so not found. However, /lib/x86_64-linux-gnu/security/pam_winbind.so exists. 2) Post install script couldn't work and apt-get upgrade failed. When samba-ad-dc was launched, winbind is already in process and the upgrade script try to launch winbind duplicately and failed upgrade. 3) winbind vendor preset: enable Samba-ad-dc launch winbind as its child. It means there is no need to launch winbind again, should be disable. I confirmed the problem in both stretch and buster (2018-05-31) -- Package-specific info: * /etc/samba/smb.conf present, but not attached * /etc/samba/dhcp.conf not present -- System Information: Debian Release: buster/sid APT prefers stable APT policy: (101, 'stable'), (100, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages winbind depends on: ii libbsd0 0.9.1-1 ii libc6 2.27-3 ii libldap-2.4-2 2.4.46+dfsg-5 ii libpopt0 1.16-11 ii libtalloc22.1.11-2 ii libtdb1 1.3.15-4 ii libtevent00.9.36-2 ii libwbclient0 2:4.7.4+dfsg-2 ii lsb-base 9.20170808 ii samba-common 2:4.7.4+dfsg-2 ii samba-common-bin 2:4.7.4+dfsg-2 ii samba-libs2:4.7.4+dfsg-2 winbind recommends no packages. Versions of packages winbind suggests: ii libnss-winbind 2:4.7.4+dfsg-2 ii libpam-winbind 2:4.7.4+dfsg-2 -- no debconf information
Bug#900541: RFS: deepin-screenshot/4.0.14-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "deepin-screenshot" * Package name: deepin-screenshot Version : 4.0.14-1 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/deepin-screenshot * License : GPL-3+ Section : utils It builds those binary packages: deepin-screenshot - Advanced screen shoting tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/deepin-screenshot Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/deepin-screenshot/deepin-screenshot_4.0.14-1.dsc More information about hello can be obtained from https://salsa.debian.org/pkg-deepin-team/deepin-screenshot Changes since the last upload: deepin-screenshot (4.0.14-1) unstable; urgency=medium * New upstream version 4.0.14 * d/control: Add new uploader Yanhao Mo . * d/control: Use pkg-deepin-de...@lists.alioth.debian.org in Maintainer field. -- Yanhao Mo Fri, 01 Jun 2018 08:46:25 +0800 -- Yanhao Mo signature.asc Description: PGP signature
Bug#900540: RFS: deepin-voice-recorder/1.3.7-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "deepin-voice-recorder" * Package name: deepin-voice-recorder Version : 1.3.7-1 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/deepin-voice-recorder * License : GPL-3+ Section : sound It builds those binary packages: deepin-voice-recorder - Deepin's Voice recorder To access further information about this package, please visit the following URL: https://mentors.debian.net/package/deepin-voice-recorder Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/deepin-voice-recorder/deepin-voice-recorder_1.3.7-1.dsc More information about hello can be obtained from https://salsa.debian.org/pkg-deepin-team/deepin-voice-recorder Changes since the last upload: deepin-voice-recorder (1.3.7-1) unstable; urgency=medium * New upstream version 1.3.7 + Feature: Add manual ID. * d/control: Add new uploader Yanhao Mo . * d/control: Use pkg-deepin-de...@lists.alioth.debian.org in Maintainer field. -- Yanhao Mo Fri, 01 Jun 2018 08:50:26 +0800 -- Yanhao Mo signature.asc Description: PGP signature
Bug#900539: Can no longer watch any YouTube movie
Package: chromium
Version: 67.0.3396.62-1
Can no longer watch any YouTube movie
[12124:12562:0601/093720.859119:ERROR:object_proxy.cc(617)] Failed to call
method: org.freedesktop.DBus.Properties.Get: object_path=
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.UPower was not provided by any .service files
[12124:12562:0601/093720.859690:ERROR:object_proxy.cc(617)] Failed to call
method: org.freedesktop.UPower.GetDisplayDevice: object_path=
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.UPower was not provided by any .service files
[12124:12562:0601/093720.859985:ERROR:object_proxy.cc(617)] Failed to call
method: org.freedesktop.UPower.EnumerateDevices: object_path=
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.UPower was not provided by any .service files
[96:111:0601/093721.548419:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[96:96:0601/093721.549182:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[96:111:0601/093722.346231:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[96:96:0601/093722.347816:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
Bug#900538: virt-manager: Please allow ability to set vlan tag in GUI for SR-IOV pools.
Package: virt-manager Version: 1:1.4.3-1 Severity: wishlist Dear Maintainer, I want to use an SR-IOV-capable NIC to provide different interfaces to a VM using KVM. I have set up a network: eno1-pool and have allocated a NIC from the pool for virt-manager. I can use virsh edit to add a vlan tag: but: -- there's no way to view or change the vlan tag in virt-manager -- virt-manager adds a bogus `model' tag --- the actual model of NIC is passed through from the virtual function. Please: 1. Add ability to change the VLAN tag for this kind of interface. 2. Grey out or otherwise disable the `device model' UI element, and don't add the tag to the XML description (it's confusing) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/56 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.28.0-2 ii gir1.2-gtk-3.0 3.22.29-3 ii gir1.2-gtk-vnc-2.0 0.7.2-1 ii gir1.2-libosinfo-1.0 1.1.0-1 ii gir1.2-libvirt-glib-1.0 1.0.0-1 ii gir1.2-vte-2.91 0.52.0-1 ii librsvg2-common 2.40.20-2 ii python 2.7.15~rc1-1 ii python-dbus 1.2.8-2 ii python-gi3.28.2-1 ii python-gi-cairo 3.28.2-1 ii python-libvirt 4.0.0-1 ii python-requests 2.18.4-2 ii python2.72.7.15-1 ii virtinst 1:1.4.3-1 Versions of packages virt-manager recommends: ii gir1.2-spiceclientglib-2.0 0.34-1.1 ii gir1.2-spiceclientgtk-3.0 0.34-1.1 ii libvirt-daemon-system 4.3.0-1 Versions of packages virt-manager suggests: pn gir1.2-secret-1 pn gnome-keyring pn python-guestfs pn ssh-askpass ii virt-viewer 6.0-2 -- no debconf information -- Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group Data61, CSIRO (formerly NICTA)
Bug#900034: libtickit: Please pass compiler flags to testsuite build
On Thu, May 24, 2018 at 03:58:54PM -0700, Steve Langasek wrote: > Hi James, > > Thanks for the fix to bug #895268. > > We are carrying another additional patch in Ubuntu which I apparently failed > to forward previously. No, I just failed to pick it up in the last upload. I was trying not to backport more than needed and didn't realize the significance of it. Thanks for the prod. I'll upload with the additional patch soon. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64
Package: src:linux Version: 4.16.5-1~bpo9+1 Severity: important May 31 18:31:39 vhost004 kernel: qemu-system-x86: page allocation failure: order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null) May 31 18:31:39 vhost004 kernel: qemu-system-x86 cpuset=/ mems_allowed=0-1 May 31 18:31:39 vhost004 kernel: CPU: 9 PID: 30989 Comm: qemu-system-x86 Tainted: G I 4.16.0-0.bpo.1-amd64 #1 Debian 4.16.5-1~bpo9+1 May 31 18:31:39 vhost004 kernel: Hardware name: HP ProLiant DL380 G6, BIOS P62 08/16/2015 May 31 18:31:39 vhost004 kernel: Call Trace: May 31 18:31:39 vhost004 kernel: dump_stack+0x5c/0x85 May 31 18:31:39 vhost004 kernel: warn_alloc+0xfc/0x180 May 31 18:31:39 vhost004 kernel: __alloc_pages_slowpath+0xded/0xe00 May 31 18:31:39 vhost004 kernel: ? _cond_resched+0x16/0x40 May 31 18:31:39 vhost004 kernel: __alloc_pages_nodemask+0x212/0x250 May 31 18:31:39 vhost004 kernel: kmalloc_order+0x14/0x40 May 31 18:31:39 vhost004 kernel: kmalloc_order_trace+0x1d/0xa0 May 31 18:31:39 vhost004 kernel: kvm_dev_ioctl+0xb4/0x680 [kvm] May 31 18:31:39 vhost004 kernel: do_vfs_ioctl+0xa2/0x620 May 31 18:31:39 vhost004 kernel: SyS_ioctl+0x74/0x80 May 31 18:31:39 vhost004 kernel: do_syscall_64+0x6c/0x130 May 31 18:31:39 vhost004 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 May 31 18:31:39 vhost004 kernel: RIP: 0033:0x7f191acd7dd7 May 31 18:31:39 vhost004 kernel: RSP: 002b:7ffd8b3f6368 EFLAGS: 0246 ORIG_RAX: 0010 May 31 18:31:39 vhost004 kernel: RAX: ffda RBX: ae01 RCX: 7f191acd7dd7 May 31 18:31:39 vhost004 kernel: RDX: RSI: ae01 RDI: 000c May 31 18:31:39 vhost004 kernel: RBP: R08: 55e881f9bb78 R09: 0050 May 31 18:31:39 vhost004 kernel: R10: 7f191af90b58 R11: 0246 R12: 55e882cf6010 May 31 18:31:39 vhost004 kernel: R13: 0001 R14: 0120 R15: May 31 18:31:39 vhost004 kernel: Mem-Info: May 31 18:31:39 vhost004 kernel: active_anon:11478 inactive_anon:14864 isolated_anon:0 active_file:24 inactive_file:894406 isolated_file:0 unevictable:16419 dirty:87216 writeback:297 unstable:0 slab_reclaimable:65632 slab_unreclaimable:302508 mapped:26941 shmem:9717 pagetables:5763 bounce:0 free:76490 free_pcp:0 free_cma:0 May 31 18:31:39 vhost004 kernel: Node 0 active_anon:30116kB inactive_anon:40212kB active_file:920716kB inactive_file:1484008kB unevictable:3580kB isolated(anon):0kB isolated(file):0kB mapped:44432kB dirty:26804kB writeback:540kB shmem:4772kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no May 31 18:31:39 vhost004 kernel: Node 1 active_anon:15796kB inactive_anon:19244kB active_file:190380kB inactive_file:2093616kB unevictable:62096kB isolated(anon):0kB isolated(file):0kB mapped:63332kB dirty:322060kB writeback:648kB shmem:34096kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 16384kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no May 31 18:31:39 vhost004 kernel: Node 0 DMA free:15892kB min:20kB low:32kB high:44kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB May 31 18:31:39 vhost004 kernel: lowmem_reserve[]: 0 3486 30139 30139 30139 May 31 18:31:39 vhost004 kernel: Node 0 DMA32 free:125192kB min:5204kB low:8772kB high:12340kB active_anon:27312kB inactive_anon:38456kB active_file:897800kB inactive_file:1459052kB unevictable:576kB writepending:25920kB present:3643520kB managed:3577952kB mlocked:576kB kernel_stack:3216kB pagetables:10464kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB May 31 18:31:39 vhost004 kernel: lowmem_reserve[]: 0 0 26653 26653 26653 May 31 18:31:39 vhost004 kernel: Node 0 Normal free:40504kB min:39784kB low:67076kB high:94368kB active_anon:2944kB inactive_anon:1728kB active_file:22860kB inactive_file:25152kB unevictable:3004kB writepending:704kB present:27787264kB managed:27292884kB mlocked:3004kB kernel_stack:1576kB pagetables:400kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB May 31 18:31:39 vhost004 kernel: lowmem_reserve[]: 0 0 0 0 0 May 31 18:31:39 vhost004 kernel: Node 1 Normal free:124372kB min:45096kB low:76032kB high:106968kB active_anon:15780kB inactive_anon:19244kB active_file:190380kB inactive_file:2093408kB unevictable:62096kB writepending:322068kB present:31457276kB managed:30943772kB mlocked:62096kB kernel_stack:4744kB pagetables:12188kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB May 31 18:31:39 vhost004 kernel: lowmem_reserve[]: 0 0 0 0 0 May 31 18:31:39 vhost004 kernel: Node 0 DMA: 1*4kB (U) 0*8kB
Bug#900537: Build NanoPi Neo 2 in u-boot-sunxi arm64
Package: u-boot Severity: wishlist Tags: patch thanks Attached is a patch to add a nanopi_neo2 u-boot binary in the u-boot-sunxi package. I'm in the middle of modifying `u-boot-install-sunxi64` to be a bit more generic; but it's worked successfully with a bit of hacking. Paul -- :wq nanopi-neo-2 Description: Binary data
Bug#900460: ephoto: fails to start
Hi Ross, thanks for coming back .. > Can you provide the output of "dpkg -l | grep libevas1-engine"? It ii libevas1-engines-wayland:amd64 1.20.7-4 amd64Evas module providing the Wayland engine > looks like ephoto can't find a working evas engine. Probably you're > using X11 but the dependencies only installed the wayland engine, or > vice versa. What else do I need to check? All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#900536: mdadm does not auto assemble array with write-journal on boot
Package: mdadm Version: 3.4-4+b1 Severity: important Kernel: Debian Stretch 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux Hello, mdadm seems to hang while auto assembling array with write journal on boot. After boot mdadm array is not visible on lsblk and cannot be mounted. Looking at: “mdadm --query --detail /dev/md0” Shows: “State : inactive” Also: “cat /proc/mdstat” Shows: “md0 : inactive sdf1[4](S) sdd1[0](S) sde1[1](S) nvme0n1p1[3](S)” Running “mdadm --assemble /dev/md0” hangs unless array (which appears to not be running) is stopped first “mdadm –stop /dev/md0”. After assembling manually array works normally. Tested with raid 5 & 6 arrays on fresh minimal installs Array created: “mdadm --verbose --create /dev/md0 --level=6 --raid-devices=5 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 --write-journal /dev/nvme0n1p1” Config saved: “mdadm --detail --scan /dev/md0 >> /etc/mdadm/mdadm.conf” “ARRAY /dev/md0 metadata=1.2 name=twin-02:0 UUID=0a12f609:3d7fa535:6b7055d2:459c4f02” “update-initramfs -u” This looks like a bug as the array should be auto assembled at boot. Creating array without write-journal option works normally. Doing some research came across this on a mailing list: https://lists.debian.org/debian-user/2017/11/msg00204.html Some Information just after boot on raid 5 array: --- mdadm.conf HOMEHOST MAILADDR root ARRAY /dev/md0 metadata=1.2 name=twin-02:0 UUID=0a12f609:3d7fa535:6b7055d2:459c4f02 --- /etc/default/mdadm AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS="--syslog" VERBOSE=false --- /proc/mdstat: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : inactive sde1[1](S) sdf1[4](S) sdd1[0](S) nvme0n1p1[3](S) 2213973558 blocks super 1.2 unused devices: --- /proc/partitions: major minor #blocks name 259 0 244198584 nvme0n1 259 1 16777216 nvme0n1p1 8 32 732574584 sdc 8 33 732573543 sdc1 8 48 732574584 sdd 8 49 732573543 sdd1 8 0 117220824 sda 8 1 19530752 sda1 8 2 97688576 sda2 8 64 732574584 sde 8 65 732573543 sde1 8 16 732574584 sdb 8 17 732573543 sdb1 8 80 732574584 sdf 8 81 732573543 sdf1 -- Kind Regards, Chris
Bug#845297: Debian website git repo in Salsa (Bug #845297)
Hi! On Thu, 2018-05-31 at 06:14:56 +0200, Laura Arjona Reina wrote: > the conversion went well and we have a working repo in: > > https://salsa.debian.org/webmaster-team/webwml First of all, thanks much for this conversion! This was one of the last repos using CVS I had commit access to, and a reason I had stopped committing some time ago. :) BTW, I mentioned this already on IRC to Laura, but wanted to mention it here again, because this might be a “now or never” kind of thing. I noticed the Authors do not include the domain in the email part. Laura mentioned that there were privacy concerns, and I can understand that for the -guest accounts, but for the Debian ones, it's just an uniform @debian.org. If there's agreement this will stay, then I guess I'll try to provide at least a .mailmap file for the @debian.org ones, which while not ideal, at least restores the information for some git commands, such as «git shortlog». > Working with the repository > === > > You need to install git to work with the repository and configure your > user and email (please refer to general git documentation). Once this is > done, clone the repo with: > > $ git clone g...@salsa.debian.org:webmaster-team/webwml.git Something not many might be aware, is that you do not need to checkout the entire repo, and we can partially emulate what many of us were doing with CVS. For example, I only want the base files, english, catalan and spanish translations: $ git clone --no-checkout g...@salsa.debian.org:webmaster-team/webwml.git $ cd webwml $ git config core.sparseCheckout true $ cat >.git/info/sparse-checkout <
Bug#896706: pcbnew: crashes with a failed assertion on i386, starts fine on amd64
Hello Carsten, On Thu, May 31, 2018 at 05:55:09AM +0200, Carsten Schoenert wrote: > just for clarity, this issue is happen if you running pcbnew in > standalone mode or is this happen also if start pcbnew from the kicad > manager? It happens in both situations. When pcbnew is started from the manager, the same message is printed and the manager also aborts. > This is no crash? Well, what do you consider a crash? pcbnew does not display any GUI before terminating. > I opened a new upstream bug report about this. > > https://bugs.launchpad.net/kicad/+bug/1774316 > > Please check if the system information is correct so far within the bug > report. Looks OK to me. This is the diff from your bugreport to my version info: --- kicad-bugreport.txt 2018-06-01 01:35:35.095539211 +0200 +++ kicad-versioninfo.txt 2018-06-01 01:37:18.614939232 +0200 @@ -5,2 +5,2 @@ -libcurl/7.58.0 OpenSSL/1.0.2o zlib/1.2.11 libidn2/2.0.4 libpsl/0.20.1 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.31.1 librtmp/2.3 -Platform: Linux 4.16.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK +libcurl/7.60.0 OpenSSL/1.0.2o zlib/1.2.11 libidn2/2.0.4 libpsl/0.20.1 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.32.0 librtmp/2.3 +Platform: Linux 4.16.0-1-686-pae i686, 32 bit, Little endian, wxGTK Regards Mirko
Bug#899154: Acknowledgement (console switching broken on Polaris11 hardware with amdgpu.dc=1)
On 05/24/2018 11:54 PM, Richard B. Kreckel wrote: > Aha! The problem goes away when upgrading to Xorg 1.20. Oh, the problem has re-surfaced after a recent burst of debian/testing upgrades. :(
Bug#859213: marked as done (x11vnc: stack smashing detected: x11vnc terminated)
On Wed, 9 May 2018 00:54:58 +0200 Bernhard Ehlers wrote: Just build x11vnc/0.9.13-6 in Stretch and it indeed solves the issue. Good job Nikita. As my private build is obsolete now, I will delete them from my server. Best regards Bernhard In the Stretch repository, I am still seeing the 0.9.13-2. -6 is in Testing. Can someone advise how to request this fix be pushed into Stable (or Backports)? Last time I mixed stuff from testing, I got thoroughly told off ;-) Thanks much! Mark
Bug#900535: Binary Independent build seems to have FTBFS
Package: src:python3-stdlib-extensions Version: 3.6.4-4 Severity: serious X-Debbugs-CC: debian-pyt...@lists.debian.org Hello, python3-distutils is currently unavailable in unstable, it appears that python3-stdlib-extensions was intended to provided it, but the all architecture package is failing to build because of a missing dependency on distutils. https://buildd.debian.org/status/fetch.php?pkg=python3-stdlib-extension s=all=3.6.5-4=1527781937=0 Thank you, Diane signature.asc Description: This is a digitally signed message part
Bug#900534: sshguard: Parser ignores new ssh log format
Package: sshguard
Version: 1.7.1-1
Severity: important
Tags: patch
Dear maintainer,
Quite a long ago, I've noticed that sshguard stopped detecting one of the
most popular lines in auth.log for ssh, which looks like that:
Jun 1 00:02:59 server sshd[15980]: Failed password for invalid user student
from 119.28.7.243 port 60902 ssh2
Not being able to detect these lines renders sshguard pretty much
useless for detecting ssh attacks.
Until now I managed to mitigate that via rsyslog rewriting template, but
now I decided to do things properly and send you a patch that makes
sshguard detect lines like these. I'm not very good with flex, but I've
tested it on sshguard debug mode, and it seems to work OK.
Please see the patch enclosed. It should be applied to the file
src/parser/attack_scanner.l. Is it possible that it will be accepted
in stretch? Thanks in advance!
-- System Information:
Debian Release: 9.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-6-686 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages sshguard depends on:
ii init-system-helpers 1.48
ii iptables 1.6.0+snapshot20161117-6
ii libc62.24-11+deb9u3
ii lsb-base 9.20161125
sshguard recommends no packages.
sshguard suggests no packages.
-- no debconf information
--- attack_scanner.orig.l 2016-10-11 19:22:37.0 +0300
+++ attack_scanner.l2018-06-01 01:35:52.0 +0300
@@ -38,7 +38,7 @@
/* Start Conditions */
/* for Login services */
-%s ssh_notallowed ssh_loginerr ssh_reversemap ssh_disconnect ssh_badproto
ssh_badkex
+%s ssh_invaluser ssh_notallowed ssh_loginerr ssh_reversemap ssh_disconnect
ssh_badproto ssh_badkex
/* for Mail services */
%s dovecot_loginerr cyrusimap_loginerr exim_esmtp_autherr sendmail_relaydenied
sendmail_authfailure postfix_loginerr
/* for FTP services */
@@ -124,6 +124,8 @@
/* SSH: invalid or rejected user (cross platform [generated by openssh]) */
[Ii]"nvalid user ".+" from "{ return
SSH_INVALUSERPREF; }
+"Failed password for "?[Ii]"nvalid user ".+" from " {
BEGIN(ssh_invaluser); return SSH_INVALUSERPREF; }
+"port "{NUMBER}" ssh".? {
BEGIN(INITIAL); }
/* match disallowed user (not in AllowUsers/AllowGroups or in
DenyUsers/DenyGroups) on Linux Ubuntu/FreeBSD */
/* "User tinydns from 1.2.3.4 not allowed because not listed in AllowUsers" */
"User ".+" from " {
BEGIN(ssh_notallowed); return SSH_NOTALLOWEDPREF; }
Bug#823556: Package repository at Salsa
I've created repository for the official package: https://salsa.debian.org/go-team/packages/mattermost-server -- Cheers, Dmitry Smirnov --- "For every complex problem there is an answer that is clear, simple, and wrong. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#577597: Still happens with util-linux 2.32-0.1 and Linux 4.17-rc7
found 577597 2.32-0.1 thanks This issue still happens with util-linux 2.32-0.1 and on self compiled Linux 4.17-rc7 with Debian Sid. The work-around hwclock --systohc --utc hwclock --hctosys --utc mentioned by Michael still works. Thanks, -- Martin
Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work
Package: chromium
Version: 67.0.3396.62-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Can't use video on youtube. Gif's no longer work. And I cannot get media to
play. This started after upgrading from 66.0.3359.181-1 to 67.0.3396.62-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Reverting the package was the only solution I could find. It appears the app
build may be missing some flags in the build. I found this that had similar
errors to my situation
https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ
* What was the outcome of this action?
chromium 66.0.3359.181-1 was reinstalled, video is working again.
* What outcome did you expect instead?
chromium 67.0.3396.62-1 video should work after install.
Chromium Log while trying to play files
[129:160:0531/181749.318090:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.320645:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.352209:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.354280:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.551754:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181749.559473:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[129:160:0531/181750.431299:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181750.433293:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
libpng warning: iCCP: known incorrect sRGB profile
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 67.0.3396.62-1
ii libasound2 1.1.6-1
ii libatk-bridge2.0-0 2.26.2-1
ii libatk1.0-0 2.28.1-1
ii libavcodec57 7:3.4.2-2+b1
ii libavformat577:3.4.2-2+b1
ii libavutil55 7:3.4.2-2+b1
ii libc62.27-3
ii libcairo21.15.10-3
ii libcups2 2.2.7-5
ii libdbus-1-3 1.12.8-2
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat12.2.5-3
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.1.0-4
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libglib2.0-0 2.56.1-2
ii libgtk-3-0 3.22.30-1
ii libharfbuzz0b1.7.6-1+b1
ii libicu60 60.2-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.19-3
ii libnss3 2:3.37.1-1
ii libopenjp2-7 2.3.0-1
ii libopus0 1.3~beta+20180518-1
ii libpango-1.0-0 1.42.1-1
ii libpangocairo-1.0-0 1.42.1-1
ii libpng16-16 1.6.34-1
ii libpulse011.1-5
ii libre2-4 20180301+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.1.0-4
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux20.6.1-2
ii libwebpmux3 0.6.1-2
ii libx11-6 2:1.6.5-1
ii libx11-xcb1 2:1.6.5-1
ii libxcb1 1.13-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-1
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-7
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.32-2
ii libxss1 1:1.2.2-1+b2
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-7
ii libgl1-mesa-dri 18.0.4-1
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
-- no debconf information
Bug#900532: ITP: estscan -- ORF-independent detector of coding DNA sequences
Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: estscan Version : 3.0.3 * URL : http://estscan.sourceforge.net/ * License : non-free custom Programming Lang: C, Fortran Description : ORF-independent detector of coding DNA sequences Continues packaging seeded by Bio-Linux, package is team maintained at https://salsa.debian.org/med-team/estscan
Bug#900530: RM: clementine [armel armhf] -- ANAIS; FTBFS on armel and armhf
El jueves, 31 de mayo de 2018 19:13:18 -03 Thomas Pierson escribió: > Package: ftp.debian.org > Severity: normal > > Hello, > > I was unable to resolve the FTBFS issues for now with armel and armhf. > I request the removal of these architectures from this package in unstable. The technical side of this is that Qt 5 does not supports Desktop OpenGL on those archs, and as clementine has switched to Qt5 and requires Desktop OpenGL stuff it can't be built anymore there. Thanks in advance! -- The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. George Bernard Shaw Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#900530: RM: clementine [armel armhf] -- ANAIS; FTBFS on armel and armhf
Package: ftp.debian.org Severity: normal Hello, I was unable to resolve the FTBFS issues for now with armel and armhf. I request the removal of these architectures from this package in unstable. Thanks, Thomas Pierson signature.asc Description: OpenPGP digital signature
Bug#900531: ITP: tinyjsd -- Lightweight JavaScript Debugger for Thunderbird and Firefox
Package: wnpp Severity: wishlist Owner: Daniel Kahn Gillmor * Package name: tinyjsd Version : 1.2 Upstream Author : Patrick Brunschwig * URL : https://sourceforge.net/u/pbrunschwig/tinyjsd * License : MPL 2.0 Programming Lang: JavaScript Description : Lightweight JavaScript Debugger for Thunderbird and SeaMonkey TinyJSD is a JavaScript debugger for Mozilla products (Firefox, Thunderbird, SeaMonkey). The key differences to debuggers like Firebug and the debugger built into Firefox are: * focused on debugging privileged code such as extensions and the application itself * simple user interface for easier use than complex debugger tools --- This is a recommended extension for the development and testing of Enigmail
Bug#900519: unscd: Please add systemd notification support for startup error reporting
On Thu, 31 May 2018, Ferenc Wágner wrote: > If (for example) one sets "server-user" to an invalid user name in the > config file, unscd fails to start up but "systemctl start unscd" does > not report this failure. This is a shortcoming of Type=simple services. > Please consider switching to Type=notify to remedy this. Please refer > to https://github.com/wferi/unscd for my idea of the implementation. > That repo also contains 5 other patches on top of that fixing various > info level issues reported by Lintian. Please let me know if you'd > prefer getting the patches by some other means. Thanks for the patches; I've gone ahead and added them. I'll upload after testing. -- Don Armstrong https://www.donarmstrong.com Some pirates achieved immortality by great deeds of cruelty or daring-do. Some achieved immortality by amassing great wealth. But the captain had long ago decided that he would, on the whole, prefer to achieve immortality by not dying. -- Terry Pratchet _The Color of Magic_
Bug#900398: [debian-mysql] Bug#900398: Bug#900398: mariadb-server-10.1: postinst fails since official rebuild
Paul, can you try to rename the tc.log file? Do you know which version of mariadb-server you are upgrading from?
Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected
Anton Zinoviev, le ven. 01 juin 2018 00:48:18 +0300, a ecrit: > If a bug makes a package totally unusable, but otherwise harmless, > then this bug is (usually) not going to be fixed in the stable > release. Mmm, I believe that sentence enters the "important" area, or even more: 4 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. while 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. Samuel
Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected
Hello guys, Thanks for your valuable input, and for shedding more light on the inners of the current localisation approach. The layouts from the 'kbd' package do not work with UTF-8 input. I've used them in the past with 1-byte input forced in the kernel by adding the 'vt.default_utf8=0' boot parameter.. Anton, thanks for suggesting the workaround. However, adding the kmap "snapped" with ckbcomp and hand-modified afterwards as a value to 'KMAP=' in the /etc/default/keyboard is not really a workaround, since this overrides whatever that the user may have set in the XKBOPTIONS (such as grp switching/toggling), effectively leaving her/him with only the localised KMAP loaded. Nevertheless, the hand-modification you've suggested for me was the missing key in the puzzle - please see further. With all the above said, I've been able to create a (hopefully) complete set of all the missing compose defs for the czech letters. Please see the attached file. If you could append this to the /etc/console-setup/compose.ISO-8859-2.inc file. This will add all the missing definitions, enabling the user to input all the czech letters on a cz keyboard layout, provided that (s)he has defined either 'Lat2' or 'ISO-8859-2' for the 'CODESET=' in the /etc/default/console-setup . I think this could be fixed right in the Stretch. With kind regards, Jan compose '^' 'C' to U+010C compose '^' 'c' to U+010D compose '^' 'D' to U+010E compose '^' 'd' to U+010F compose '^' 'E' to U+011A compose '^' 'e' to U+011B compose '^' 'L' to U+013D compose '^' 'l' to U+013E compose '^' 'N' to U+0147 compose '^' 'n' to U+0148 compose '^' 'R' to U+0158 compose '^' 'r' to U+0159 compose '^' 'S' to U+0160 compose '^' 's' to U+0161 compose '^' 'T' to U+0164 compose '^' 't' to U+0165 compose '^' 'Z' to U+017D compose '^' 'z' to U+017E compose ''' 'A' to U+00C1 compose ''' 'E' to U+00C9 compose ''' 'I' to U+00CD compose ''' 'O' to U+00D3 compose ''' 'U' to U+00DA compose ''' 'Y' to U+00DD compose ''' 'a' to U+00E1 compose ''' 'e' to U+00E9 compose ''' 'i' to U+00ED compose ''' 'o' to U+00F3 compose ''' 'u' to U+00FA compose ''' 'y' to U+00FD compose ''' 'C' to U+0106 compose ''' 'c' to U+0107 compose ''' 'L' to U+0139 compose ''' 'l' to U+013A compose ''' 'N' to U+0143 compose ''' 'n' to U+0144 compose ''' 'R' to U+0154 compose ''' 'r' to U+0155 compose ''' 'S' to U+015A compose ''' 's' to U+015B compose ''' 'Z' to U+0179 compose ''' 'z' to U+017A
Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected
On Thu, May 31, 2018 at 11:12:43PM +0300, Anton Zinoviev wrote: > > only important bugs are fixed I realised the word 'important' was very inapropriate in this context. What is unimportant for one user can be very important for another. So by 'important' bugs I meant things about unauthorized access or corruption/deletion of data. If a bug makes a package totally unusable, but otherwise harmless, then this bug is (usually) not going to be fixed in the stable release. Anton Zinoviev
Bug#833692: pinot: links GPLv2+ code with OpenSSL
On Thu, May 31, 2018 at 12:22:58AM +0200, Sebastian Andrzej Siewior wrote: > pinot has currently two RC bugs and failed to build during the curl4 > transition / binNMU. > Does it make sense to add the two patches (Olly pointed to) and upload > it or would a RM make sense? Popcon suggests pinot usage is low: https://qa.debian.org/popcon.php?package=pinot I'm not sure there's really a direct equivalent though, so it seems worth uploading with at least the RC fixes. I can prepare an upload (or happy for someone else to). Jonas: Are you still interested in maintaining pinot? I ask because it's had RC bugs open for a long time without any maintainer response, and the last maintainer upload was over five years ago now. Let me know and if not I can orphan or adopt in my upload. Cheers, Olly
Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected
On Mon, May 28, 2018 at 12:25:04PM +0200, Jan Rafaj wrote: > > Anton, thanks for suggesting the workaround. However, adding the kmap > "snapped" with ckbcomp and hand-modified afterwards as a value to 'KMAP=' in > the /etc/default/keyboard is not really a workaround, since > this overrides whatever that the user may have set in the XKBOPTIONS (such > as grp switching/toggling), effectively leaving her/him with only the > localised KMAP loaded. Instead of the command ckbcomp cz >cz.kmap which I suggested in my previous message, you can use something like ckbcomp cz dvorak-ucw grp:win_menu_switch lv3:menu_switch >cz.kmap See `ckbcomp -help` or `man ckbcomp`. > With all the above said, I've been able to create a (hopefully) complete > set of all the missing compose defs for the czech letters. Thanks, this will be useful. > I think this could be fixed right in the Stretch. When I have time I will upload a fixed package to Unstable. I am not sure, but I think only important bugs are fixed in the stable releases of Debian. Unless there is some change in the policies of Debian of which I am not aware (which is not impossible, to be honest...). Anton Zinoviev
Bug#827844: git: man git: dead link
Bug 827844 seems to have been fixed upstream. The link now in the man-page is: https://git.github.io/htmldocs/git.html Using git version 1:2.17.1-1. It looks like it was fixed by Jonathan: commit f79358279c4b447b1318a922e15705d2a00fc5a2 (origin/jn/preformatted-doc-url) Author: Jonathan Nieder Date: Wed Jun 22 10:38:25 2016 -0700 doc: git-htmldocs.googlecode.com is no more
Bug#900527: scribus: PDF files can't be imported any more
Mattia Rizzolo, le jeu. 31 mai 2018 22:45:49 +0200, a ecrit: > On Thu, May 31, 2018 at 10:21:49PM +0200, Samuel Thibault wrote: > > After some upgrade in testing (no earlier than around february, it did > > work at the time), I can't import PDF files in scribus any more > … > > I tried to downgrade scribus to 1.4.6+dfsg-4, but that didn't help. I > > also tried to downgrade libgs9 to 9.22~dfsg-2 and 9.22~dfsg-1, and that > > didn't help either, so I'm out of ideas. > > According to another report (just merged) this is due to ghostscript, I > believe it could be useful if you confirm downgrading to even older > version (9.20) makes scribus work again. Mmm, downgrading to 9.20~dfsg-3.2 didn't help either. Samuel
Bug#900526: testing of modules which rely on entry points is broken
Seemed to work like a charm, thank you Piotr! Feel free to close if you think this should be done manually (and not by default) On Thu, 31 May 2018, Piotr Ożarowski wrote: > [Yaroslav Halchenko, 2018-05-31] > > I will meanwhile provide a workaround one way (skipping tests) or another > > (symlinking .egg-info may be), but it would be nice if pybuild --test > > handled > > those usecases smoother > is debian/pybuild.testfiles smooth enough? > (just put file/dir name there and pybuild will copy it to build > directory before tests and remove them before installing files) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#900529: ITP: jsunit -- A suite to perform unit tests for JavaScript in Thunderbird and Firefox
Package: wnpp Severity: wishlist Owner: Daniel Kahn Gillmor * Package name: jsunit Version : 0.1.4 Upstream Author : Patrick Brunschwig * URL : https://sourceforge.net/u/pbrunschwig/jsunit * License : MPL 2.0 Programming Lang: JavaScript Description : A JavaScript unit test framework for Thunderbird and Firefox JSUnit is a Mozilla addon targeted for addon authors to allow for unit testing of JavaScript components. It provides a command line interface to run unit tests in installed applications like Firefox and Thunderbird. Please note: JSUnit is a test tool; it is not recommended for production environments, as it modifies various configuration settings that slow down your application for daily use! --- This is useful for running the full test suite for Enigmail (e.g. during build time, or in autopkgtest). It is not something that a normal user will want to have installed on their machine.
Bug#888349: linphone: FTBFS with FFmpeg 3.5
On 29.05.2018 11:20, James Cowgill wrote: Hi James, > > On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote: >> Source: linphone >> Version: 3.6.1-3 >> Severity: important >> User: debian-multime...@lists.debian.org >> Usertags: ffmpeg-3.5-transition >> >> Hi, >> >> Your package FTBFS with the upcoming version 3.5 of FFmpeg. > > This is fixed in 3.12.0-2 in experimental. Since I want to use these > bugs to track what needs doing for the transition, please don't close it > until the fix is in unstable. Thanks. Unfortunately uploading a current version of linphone into unstable is currently blocked by #891620. Bernhard
Bug#894480: ps.1: Some tidying of the manual
On Thu, May 31, 2018 at 09:24:52PM +1000, Craig Small wrote: > Hello Bjarni, > Thankyou for your three bug reports. I have applied two, but the ps one > was not the patch, just a text file showing the problems again. > So, most of the changes have been applied to the upstream procps > repository[1], if you wanted to look at ps.1 again and send a patch either > there or to the Debian bug tracker, that would be fine. > The patch (compressed) is in the attachment as it is rather big. > Also, where is test-groff found? My test is the same as lintians: > "test-groff" is only in the repostitory, and without the additional check for two-fonts macros with a single argument. The additional check is in the bug-groff list nr. 53043 (savannah.gnu.org/bugs/?group=groff). N.B. My mail server has been (is being) blocked by "freelists.org" with: Diagnostic-Code: SMTP; 554 5.7.1 Service unavailable; Client host [130.208.165.104] blocked using b.barracudacentral.org; Client host blocked using Barracuda Reputation, see http://www.barracudanetworks.com/reputation/?r=1=130.208.165.104 -- Bjarni I. Gislason
Bug#803013: [bts-link] source package systemd
debian-bts-l...@lists.debian.org wrote: ... # remote status report for #803013 (http://bugs.debian.org/803013) # Bug title: systemd should not destroy application created cgroups # * https://github.com/systemd/systemd/issues/1872 # * remote status changed: (?) -> closed # * closed upstream tags 803013 + fixed-upstream usertags 803013 + status-closed ... It is not fixed upstream, but simply closed; this Debian bug should not be closed. Please note again: this "confusion" or "lack of sanity check" bug in systemd prevents package cgroup-tools from working. Oh well, I will keep using my "manually patched" systemd. Cheers, Paul -- Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia
Bug#900527: scribus: PDF files can't be imported any more
Control: reassign -1 ghostscript Control: forcemerge 897407 -1 On Thu, May 31, 2018 at 10:21:49PM +0200, Samuel Thibault wrote: > After some upgrade in testing (no earlier than around february, it did > work at the time), I can't import PDF files in scribus any more … > I tried to downgrade scribus to 1.4.6+dfsg-4, but that didn't help. I > also tried to downgrade libgs9 to 9.22~dfsg-2 and 9.22~dfsg-1, and that > didn't help either, so I'm out of ideas. According to another report (just merged) this is due to ghostscript, I believe it could be useful if you confirm downgrading to even older version (9.20) makes scribus work again. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#896550: kazam: Binding 'R' failed!
Control: severity -1 important Control: retitle -1 kazam does not work under Wayland Hi everyone, I did some digging on this issue in a VM running buster/testing + GNOME, only to find that Kazam does not work at all on Wayland. The keybinding errors are caused by Keybinder not supporting Wayland[1][2], but I've also found several other problems. Some of these can be worked around by running kazam with GDK_BACKEND=x11 set, but others are not. - Screenshots fail under Wayland unless GDK_BACKEND=x11 is set: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/kazam/app.py", line 567, in cb_counter_finished self.grabber.grab() File "/usr/lib/python3/dist-packages/kazam/backend/grabber.py", line 146, in grab c_picbuf.composite(self.pixbuf, 0, 0, w - 1, h - 1, AttributeError: 'NoneType' object has no attribute 'composite' - Choosing to record a window under Wayland fails because libwnck only supports X11 (worked around with GDK_BACKEND=x11): (kazam:3789): Wnck-WARNING **: 13:08:48.693: libwnck is designed to work in X11 only, no valid display found Traceback (most recent call last): File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 111, in cb_button_press_event screen.force_update() AttributeError: 'NoneType' object has no attribute 'force_update' - Screen recording under Wayland shows a black screen with only the cursor, even when GDK_BACKEND=x11 is set In this case, no explicit errors are shown. All of these issues are Wayland specific and do not affect GNOME on Xorg or other X11-based desktops. I'm therefore lowering the severity. Best, James [1]: https://github.com/kupferlauncher/keybinder/issues/11 [2]: https://github.com/Guake/guake/issues/1109 signature.asc Description: OpenPGP digital signature
Bug#900528: does not install in buster
Package: elpa-ghub+ Version: 0.2.1-1 Severity: serious postinst fails: In ghubp-base-html-url: ghub+.el:240:8:Warning: ‘(host (magit-get "github" "host"))’ is a malformed function ghub+.el:243:65:Warning: reference to free variable ‘host’ ghub+.el:745:1:Error: :condition-case must be a list of error handlers; see the documentation: ((ghub-404 nil)) ERROR: install script from elpa-ghub+ package failed dpkg: error processing package elpa-ghub+ (--configure): installed elpa-ghub+ package post-installation script subprocess returned error exit status 1 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-ghub+ depends on: ii elpa-apiwrap0.4-1 ii elpa-ghub 2.0.0-1 ii emacsen-common 2.0.8 Versions of packages elpa-ghub+ recommends: ii emacs 47.0 elpa-ghub+ suggests no packages. -- no debconf information
Bug#900527: scribus: PDF files can't be imported any more
Package: scribus Version: 1.4.7+dfsg-1 Severity: important Hello, After some upgrade in testing (no earlier than around february, it did work at the time), I can't import PDF files in scribus any more, for instance the attached pdf file: - run scribus - create new document - click on insert image frame button, create frame - double-click on frame to select the attached test.pdf file - the result is a red cross and the file name in the frame, instead of the content of the file and exporting to PDF shows a blank page. I tried to downgrade scribus to 1.4.6+dfsg-4, but that didn't help. I also tried to downgrade libgs9 to 9.22~dfsg-2 and 9.22~dfsg-1, and that didn't help either, so I'm out of ideas. I'm unable to use scribus without the PDF import feature. Samuel -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scribus depends on: ii ghostscript 9.22~dfsg-2.1 ii libc62.27-3 ii libcairo21.15.10-3 ii libcups2 2.2.7-5 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.1.0-3 ii libhyphen0 2.8.8-5 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-1 ii libpodofo0.9.5 0.9.5-9 ii libpython2.7 2.7.15-1 ii libqt4-network 4:4.8.7+dfsg-17 ii libqt4-xml 4:4.8.7+dfsg-17 ii libqtcore4 4:4.8.7+dfsg-17 ii libqtgui44:4.8.7+dfsg-17 ii libstdc++6 8.1.0-3 ii libtiff5 4.0.9-5 ii libxml2 2.9.4+dfsg1-6.1 ii python-tk2.7.15-1 ii scribus-data 1.4.7+dfsg-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages scribus recommends: ii cups-bsd2.2.7-5 ii fonts-dejavu2.37-1 ii fonts-liberation1:1.07.4-6 ii gsfonts-x11 0.25 ii hyphen-en-us [hyphen-hyphenation-patterns] 2.8.8-5 ii hyphen-fr [hyphen-hyphenation-patterns] 1:6.0.3-3 ii hyphen-sh [hyphen-hyphenation-patterns] 1:3.3.0-4+deb8u1 ii icc-profiles-free 2.0.1+dfsg-1 ii xfonts-scalable 1:1.0.3-1.1 Versions of packages scribus suggests: pn icc-profiles pn scribus-doc pn scribus-template ii texlive-latex-recommended 2018.20180505-1 -- no debconf information -- Samuel jr> J'ai fait. Ne bougez pas, l'aide soignante va venir nettoyer. -+- FF in GNU - Le vieil homme et la merde -+- test.pdf Description: Adobe PDF document
Bug#900526: testing of modules which rely on entry points is broken
[Yaroslav Halchenko, 2018-05-31] > I will meanwhile provide a workaround one way (skipping tests) or another > (symlinking .egg-info may be), but it would be nice if pybuild --test handled > those usecases smoother is debian/pybuild.testfiles smooth enough? (just put file/dir name there and pybuild will copy it to build directory before tests and remove them before installing files)
Bug#900526: testing of modules which rely on entry points is broken
Package: dh-python
Version: 3.20180326
Severity: normal
My use case is datalad. In upcoming release we will rely on entry points more
and our tests verify that entry points could be correctly loaded etc.
For the "scripts" we just provided a custom workaround, but now we will use
pkg_resources.iter_entry_points which seems to rely on having
module.egg-info/entry_points.txt available. But testing is launched from under
.pybuild/ directory so those entry points aren't found and thus tests fail.
mkdir -p build; \
export
HOME=/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/build;
\
git config --global user.name "TESTING"; \
git config --global user.email "test...@example.com"
# Skipping a failing test for now: https://github.com/datalad/datalad/issues/357
# Since pybuild overrides HOME for its own purposes, we will rely on our
# setup_package placing it back into HOME
GIT_HOME=/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/build
PATH=/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/bin:$PATH
\
PYBUILD_TEST_ARGS="-s -v --pdb datalad.metadata.extractors.tests" \
WRAPT_DISABLE_EXTENSIONS=1 \
dh_auto_test -- --test-nose
pybuild --test --test-nose -i python{version} -p 2.7 --test-nose
I: pybuild base:217: cd
'/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/.pybuild/cpython2_2.7_datalad/build';
python2.7 -m nose -s -v --pdb datalad.metadata.extractors.tests
datalad.metadata.extractors.tests.test_audio.test_audio ... >
/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/.pybuild/cpython2_2.7_datalad/build/datalad/metadata/metadata.py(462)_get_metadata()
-> extractors = {ep.name: ep for ep in
iter_entry_points('datalad.metadata.extractors')}
(Pdb) p list(iter_entry_points('datalad.metadata.extractors'))
[]
(Pdb) os.getcwd()
'/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/.pybuild/cpython2_2.7_datalad/build'
(Pdb)
[2] + 25084 suspended fakeroot debian/rules clean binary
$> ls
/home/yoh/proj/datalad/build-area/datalad-0.10.0~rc4+git167-g88f3ea8f/.pybuild/cpython2_2.7_datalad/build
datalad/
$> cat datalad.egg-info/entry_points.txt
[datalad.metadata.extractors]
annex = datalad.metadata.extractors.annex:MetadataExtractor
audio = datalad.metadata.extractors.audio:MetadataExtractor
datacite = datalad.metadata.extractors.datacite:MetadataExtractor
datalad_core = datalad.metadata.extractors.datalad_core:MetadataExtractor
datalad_rfc822 = datalad.metadata.extractors.datalad_rfc822:MetadataExtractor
exif = datalad.metadata.extractors.exif:MetadataExtractor
frictionless_datapackage =
datalad.metadata.extractors.frictionless_datapackage:MetadataExtractor
image = datalad.metadata.extractors.image:MetadataExtractor
xmp = datalad.metadata.extractors.xmp:MetadataExtractor
$> find -iname entry_points*
./datalad.egg-info/entry_points.txt
I will meanwhile provide a workaround one way (skipping tests) or another
(symlinking .egg-info may be), but it would be nice if pybuild --test handled
those usecases smoother
Cheers
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (600, 'unstable'), (300, 'experimental'), (100,
'unstable-debug'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dh-python depends on:
ii python3 3.6.5-3
Versions of packages dh-python recommends:
ii python3-distutils 3.6.5-3
Versions of packages dh-python suggests:
ii dpkg-dev 1.19.0.5
ii libdpkg-perl 1.19.0.5
-- debconf-show failed
Bug#900525: savi FTCBFS: uses the build architecture compiler
Source: savi Version: 1.5.1-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap savi fails to cross build from source, because it uses the build architecture compiler. The easiest way to pass cross tools to make is using dh_auto_build with the makefile buildsystem. Since savi has a configure file (that is explicitly ignored by the packaging), the build system must be passed explicitly to do so. The attached patch implements that and makes savi cross buildable. Please consider applying it. Helmut diff --minimal -Nru savi-1.5.1/debian/changelog savi-1.5.1/debian/changelog --- savi-1.5.1/debian/changelog 2017-07-02 17:38:28.0 +0200 +++ savi-1.5.1/debian/changelog 2018-05-31 06:17:39.0 +0200 @@ -1,3 +1,11 @@ +savi (1.5.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_build --buildsystem=makefile pass cross tools +to make. (Closes: #-1) + + -- Helmut Grohne Thu, 31 May 2018 06:17:39 +0200 + savi (1.5.1-1) unstable; urgency=medium * Team upload. diff --minimal -Nru savi-1.5.1/debian/rules savi-1.5.1/debian/rules --- savi-1.5.1/debian/rules 2017-06-13 20:50:04.0 +0200 +++ savi-1.5.1/debian/rules 2018-05-31 06:17:37.0 +0200 @@ -4,12 +4,10 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all %: - dh $@ --parallel + dh $@ --parallel --buildsystem=makefile -override_dh_auto_configure: - override_dh_auto_build: - make ARCH=ubuntu + dh_auto_build -- ARCH=ubuntu override_dh_auto_install:
Bug#897218: Acknowledgement (apache2: mod_http2 (32-bit, i386) segmentation fault while delivering large (2+ GiB) file)
This is still broken in apache2 2.4.25-3+deb9u4 (the Debian stable version).
Bug#900524: prosody: CVE-2018-10847: insufficient stream header validation
Source: prosody Version: 0.9.7-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 0.10.1-1 Control: forwarded -1 https://issues.prosody.im/1147 Hi, The following vulnerability was published for prosody. CVE-2018-10847[0]: insufficient stream header validation If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-10847 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10847 [1] https://issues.prosody.im/1147 [2] https://blog.prosody.im/prosody-0-10-2-security-release/ Regards, Salvatore
Bug#900523: plasma-widgets-addons: System load viewer depends on ksysguard
Package: plasma-widgets-addons Version: 4:5.12.5-1 Severity: minor Dear Maintainer, Without KSysGuard, the system load widget does not display any value. The package plasma-widgets-addons should recommand or suggest ksysguard package. Regards, Benoit
Bug#900522: gitlab: Security Release: 10.8.2, 10.7.5, and 10.6.6
Source: gitlab Version: 10.6.5+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 10.7.3+dfsg-1 Hi There was a new gitlab security update, as per https://about.gitlab.com/2018/05/29/security-release-gitlab-10-dot-8-dot-2-released/ (Unfortunately, there are no CVE assigned yet, which would ease the tracking in any case). Regards, Salvatore
Bug#900521: [dia] The application hangs when "help()" is entered in the Python console
Package: dia
Version: 0.97.3+git20160930-6
Severity: important
--- Please enter the report below this line. ---
The Python console works perfectly fine except when a user attempts to
invoke `help()` -- without arguments.
In this case Dia freezes, and there's no obvious way to revert it to the
normal state (so any unsaved work is essentially lost). The problem is
caused by the fact that `help()` is interactive: it starts its own
subshell and is waiting for user input (or ^D).
Non-interactive invocations such as `help("topics")` or
`help("keywords")` complete normally.
The backtrace (from gdb) is as follows:
> #0 0x740666d0 in __read_nocancel () at
> ../sysdeps/unix/syscall-template.S:84
> #1 0x73ffea30 in _IO_new_file_underflow (fp=0x743248c0
> <_IO_2_1_stdin_>) at fileops.c:600
> #2 0x73fffb32 in __GI__IO_default_uflow (fp=0x743248c0
> <_IO_2_1_stdin_>) at genops.c:413
> #3 0x7fffe88b0666 in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #4 0x7fffe88b15a5 in PyFile_GetLine () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #5 0x7fffe87edf96 in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #6 0x7fffe87eb091 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #7 0x7fffe87e9390 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #8 0x7fffe87e9390 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #9 0x7fffe895229c in PyEval_EvalCodeEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #10 0x7fffe88a676d in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #11 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #12 0x7fffe88fbdfc in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #13 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #14 0x7fffe88fc2c4 in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #15 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #16 0x7fffe87e6247 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #17 0x7fffe895229c in PyEval_EvalCodeEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #18 0x7fffe88a6670 in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #19 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #20 0x7fffe88fbdfc in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #21 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #22 0x7fffe88c313a in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #23 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #24 0x7fffe87e7e10 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #25 0x7fffe895229c in PyEval_EvalCodeEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #26 0x7fffe87e29c9 in PyEval_EvalCode () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #27 0x7fffe889a196 in PyRun_StringFlags () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #28 0x7fffe87ef1af in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #29 0x7fffe87eb091 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #30 0x7fffe895229c in PyEval_EvalCodeEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #31 0x7fffe87e925d in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #32 0x7fffe87e9390 in PyEval_EvalFrameEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #33 0x7fffe895229c in PyEval_EvalCodeEx () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #34 0x7fffe88a6670 in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #35 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #36 0x7fffe88fbdfc in ?? () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #37 0x7fffe883e5c3 in PyObject_Call () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #38 0x7fffe89516c7 in PyEval_CallObjectWithKeywords () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #39 0x7fffe7bcf9e9 in ?? () from
> /usr/lib/python2.7/dist-packages/gobject/_gobject.so
> #40 0x75a7cf75 in g_closure_invoke () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #41 0x75a8ef82 in ?? () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #42 0x75a9767f in g_signal_emit_valist () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #43 0x75a97fbf in g_signal_emit () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #44 0x777278ac in ?? () from
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> #45
Bug#900459: dask: Debci regression
Hello, Allow me to first say oops, sorry about that. Unfortunately there's something going on with python3-distutils and packages that depend on it (like sphinx) are not installable right now, so I can't test my fixes. Also when I was running the tests locally they'd sometimes throw an exception on shutdown. (Though pytest reports that all of the tests passed.) Diane On Thu, 2018-05-31 at 08:26 +0200, Graham Inggs wrote: > Source: dask > Version: 0.17.4-1 > User: debian...@lists.debian.org > Usertags: regression > > Hi Maintainer > > Since the upload of 0.17.4-1, dask has been failing its own > autopkgtest [1] with the following error: > > ERROR collecting dask/bytes/tests/test_http.py > > ImportError while importing test module > '/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py:3: in > > import requests > E ModuleNotFoundError: No module named 'requests' > !!! Interrupted: 1 errors during collection > > > Regards > Graham > > > [1] https://ci.debian.net/packages/d/dask/unstable/amd64/ >
Bug#900520: RFS: node-abbrev/1.1.1-1 (Team Upload)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the package "node-abbrev". I am uploading this as a team upload. * Package name: node-abbrev Version : 1.1.1-1 Section : javascript It builds those binary packages: node-abbrev - Get unique abbreviations for a set of strings - Node.js module You can find the updated sources from salsa with: git clone https://salsa.debian.org/js-team/node-abbrev.git I have verified that the reverse-depends still work with the new version. Changes since the last upload: node-abbrev (1.1.1-1) unstable; urgency=medium * Team upload. * New upstream release * debian/control: + Switch VCS-Uri to salsa + Switch to dh compat level 11 + Priority is optional + Compliant with Policy 4.1.4 + add node-tap and node-util for running testsuite * debian/copyright: + Switch to https-Url + Update copyright years * debian/install: + Install to /usr/lib/nodejs/abbrev/ instead directly to /usr/lib/nodejs + Also install package.json * debian/rules: + Run testsuite during build * debian/tests: + Add autopkgtest to run basic "require" test and run testsuite Thanks for sponsoring! Regards, Andreas Moog -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 signature.asc Description: PGP signature
Bug#900519: unscd: Please add systemd notification support for startup error reporting
Package: unscd Version: 0.53-1 Severity: minor Tags: patch Dear Maintainer, If (for example) one sets "server-user" to an invalid user name in the config file, unscd fails to start up but "systemctl start unscd" does not report this failure. This is a shortcoming of Type=simple services. Please consider switching to Type=notify to remedy this. Please refer to https://github.com/wferi/unscd for my idea of the implementation. That repo also contains 5 other patches on top of that fixing various info level issues reported by Lintian. Please let me know if you'd prefer getting the patches by some other means. -- Thanks, Feri.
Bug#900505: segfault at 21c1, error 4 in tmux[559568e28000+84000]
Hi, On Thu, May 31, 2018 at 5:12 PM Helen Koike wrote: > I got this error: > > tmux: server[2747]: segfault at 21c1 ip 559568e52a5a sp 7ffefc121c68 > error 4 in tmux[559568e28000+84000] > > I'm not entirely sure how to reproduce it, I am filing this report in > case anyone else has the same issue. I'll add more information if I > manage to reproduce it. Thanks for the report. Just to make sure that we can get more info about the next crash, can you install systemd-coredump or similar so that we can get a usable coredump? You can also install the debugging symbols just in case: https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols As it stands, there's not enough info in this report to do anything, unfortunately.
Bug#787774: giving up on packaging OpenPGP.js
Control: retitle 896846 RFP: node-compressjs -- fast pure-JavaScript compression/decompression algorithms Control: unclaim 896846 d...@fifthhorseman.net Control: noowner 896846 Control: retitle 894753 RFP: node-asmcrypto -- JavaScript Cryptographic Library Control: unclaim 894753 d...@fifthhorseman.net Control: noowner 894753 Control: retitle 894752 RFP: node-rusha -- high-performance pure-javascript SHA1 implementation Control: unclaim 894752 d...@fifthhorseman.net Control: noowner 894752 Control: retitle 787774 RFP: node-openpgp -- OpenPGP JavaScript Implementation (OpenPGP.js) Control: unclaim 787774 d...@fifthhorseman.net Control: noowner 787774 I have tried to package OpenPGP.js for debian, but i don't think i have the capacity to do it responsibly, so i'm releasing these tickets in the hope that someone else with more stamina (or more confidence/understanding of the node/npm ecosystem) can take the process over. I still want OpenPGP.js in debian, but i won't be the one maintaining it in its current form. I would be very grateful to anyone who steps up to this task. What i've found in trying to package it is that each attempt to package turns up several additional missing dependencies, and this process is recursive. Including the packages necessary to actually build each package from source (rather than just redistributing the blobs) and run the package's unit tests adds even more dependencies. (i'm basing this understanding on the output of npm2deb more than anything else -- if that tool is incorrect, i'd love to hear more about it!) i don't currently have the time to maintain dozens of new node packages, unfortunately. Furthermore, it seems that OpenPGP.js uses some slight variants of other packages. for example, it uses a variant of compressjs that builds a deployable version of bzip2, rather than either making that deployable version as part of the openpgpjs build process, or getting that change upstreamed into compressjs. in another example, the 3.0.x branch of OpenPGP.js uses git master of https://github.com/indutny/elliptic, rather than relying on a released version. There are several tools that depend on OpenPGP.js that would be really good to have in debian, and in general having another implementation of OpenPGP built with the attention to software freedom, distributability, and reproducibility that are the hallmarks of debian would be healthy for the OpenPGP ecosystem. So i hope someone else can pick up this packaging work. If you're interested and have questions about it, i'm happy to try to consult with you, but i can't do it myself. Many thanks to the folks on #debian-js who helped me understand just how far over my head i'd need to go! --dkg signature.asc Description: PGP signature
Bug#900518: plymouth-start.service: Start request repeated too quickly
Package: plymouth Version: 0.9.3-3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? boot the PC * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? error displayed by journalctl -xb -p err mai 31 14:45:31 debian systemd[1]: Failed to start Show Plymouth Boot Screen. -- Subject: L'unité (unit) plymouth-start.service a échoué -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- L'unité (unit) plymouth-start.service a échoué, avec le résultat RESULT. bad status of the service ystemctl status plymouth-start.service -l ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-start.service; static; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Thu 2018-05-31 14:45:30 CEST; 3h 59min ago Process: 884 ExecStartPost=/bin/plymouth show-splash (code=exited, status=0/SUCCESS) Process: 876 ExecStart=/sbin/plymouthd --mode=boot --pid- file=/run/plymouth/pid --attach-to-session (code=exited, status=0/S Main PID: 880 (code=exited, status=0/SUCCESS) mai 31 14:45:30 debian systemd[1]: Starting Show Plymouth Boot Screen... mai 31 14:45:30 debian systemd[1]: Started Show Plymouth Boot Screen. mai 31 14:45:31 debian systemd[1]: plymouth-start.service: Start request repeated too quickly. mai 31 14:45:31 debian systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. mai 31 14:45:31 debian systemd[1]: Failed to start Show Plymouth Boot Screen. * What outcome did you expect instead? no errors *** End of the template - remove these template lines *** Thanks to https://www.hiroom2.com/2017/02/18/linux-systemd-s-start-request- repeated-too-quickly-for-xxx-service/ I add StartLimitBurst=0 and now the behavior a boot is that one journalctl -xb | grep plymouth -- Subject: L'unité (unit) plymouth-start.service a commencé à démarrer -- L'unité (unit) plymouth-start.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-start.service a terminé son démarrage -- L'unité (unit) plymouth-start.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) systemd-ask-password-plymouth.path a terminé son démarrage -- L'unité (unit) systemd-ask-password-plymouth.path a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-start.service a commencé à démarrer -- L'unité (unit) plymouth-start.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-start.service a terminé son démarrage -- L'unité (unit) plymouth-start.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-start.service a commencé à démarrer -- L'unité (unit) plymouth-start.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-start.service a terminé son démarrage -- L'unité (unit) plymouth-start.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-start.service a commencé à démarrer -- L'unité (unit) plymouth-start.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-start.service a terminé son démarrage -- L'unité (unit) plymouth-start.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-start.service a commencé à démarrer -- L'unité (unit) plymouth-start.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-start.service a terminé son démarrage -- L'unité (unit) plymouth-start.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-read-write.service a commencé à démarrer -- L'unité (unit) plymouth-read-write.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-read-write.service a terminé son démarrage -- L'unité (unit) plymouth-read-write.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-quit.service a commencé à démarrer -- L'unité (unit) plymouth-quit.service a commencé à démarrer. -- Subject: L'unité (unit) plymouth-quit-wait.service a commencé à démarrer -- L'unité (unit) plymouth-quit-wait.service a commencé à démarrer. mai 31 19:36:30 debian systemd[1]: Received SIGRTMIN+21 from PID 155 (plymouthd). -- Subject: L'unité (unit) plymouth-quit.service a terminé son démarrage -- L'unité (unit) plymouth-quit.service a terminé son démarrage, avec le résultat RESULT. -- Subject: L'unité (unit) plymouth-quit-wait.service a terminé son démarrage -- L'unité (unit) plymouth-quit-wait.service a terminé son démarrage, avec le résultat RESULT. systemctl status plymouth-start.service -l ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-start.service; static; vendor preset: enabled) Active: inactive (dead) since Thu 2018-05-31 19:36:11 CEST; 2min 7s ago Process: 947 ExecStartPost=/bin/plymouth show-splash
Bug#900517: courier-imap: Doesn't start: imapd/etc/init.d/courier-imap: xrealloc: .././print_cmd.c:1557: cannot allocate 512 bytes (376832 bytes allocated)
Package: courier-imap Version: 4.15-1.6 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? apt-get update apt-get -y -V upgrade apt-get -V -y install ntpdate wget sudo dnsutils aptitude apt-utils lsb-release bash-completion aptitude -V -y install telnet psmisc fuse tcpdump open-vm-tools iptables-persistent aptitude -V -y install putty-tools p7zip p7zip-full pbzip2 pigz apt-transport-https ntpdate aptitude -y -V install heirloom-mailx apt-show-versions curl make mysql-client sshpass bc unrar-free aptitude install -V -P courier-imap courier-pop courier-webadmin couriergraph * What exactly did you do (or not do) that was effective (or ineffective)? Use the latest Debian 8.x stable version with latest updates till May 31,2018 Increase RAM upto 32GB - was ineffective Increase CPU core upto 4 - was ineffective Our filesystem is XFS (LVM). Might not be related * What was the outcome of this action? Starting Courier IMAP server: imapd/etc/init.d/courier-imap: xrealloc: .././print_cmd.c:1557: cannot allocate 512 bytes (376832 bytes allocated) * What outcome did you expect instead? Start service normaly. -- System Information: Debian Release: 8.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages courier-imap depends on: ii courier-authlib 0.66.1-1+b1 ii courier-base0.73.1-1.6 ii debconf 1.5.56+deb8u1 ii libc6 2.19-18+deb8u10 ii libfam0 2.7.0-17.1 ii libgdbm31.8.3-13.1 ii postfix [mail-transport-agent] 2.11.3-1+deb8u2 courier-imap recommends no packages. Versions of packages courier-imap suggests: pn courier-doc pn courier-imap-ssl ii heirloom-mailx [imap-client] 12.5-4 -- no debconf information
Bug#900210: thunderbird: Thunderbird AppArmor config disables ability to send entirely
I've reproduced it. This is yet another sign how we need use more variables in AppArmor, and it needs to be fixed not only for Thunderbird, as $TMPDIR change will affect other confined applications too. I'll continue discussion in AppArmor mailing list to see how to approach it better. P.S. Also, waiting for AppArmor 2.13 in Debian ;)
Bug#680784: progress
Hi is there any news on this? Best,
Bug#900460: ephoto: fails to start
Control: tags -1 moreinfo Hello, Can you provide the output of "dpkg -l | grep libevas1-engine"? It looks like ephoto can't find a working evas engine. Probably you're using X11 but the dependencies only installed the wayland engine, or vice versa. Thanks, Ross On Thu, May 31, 2018 at 03:43:25PM +0900, Norbert Preining wrote: > Package: ephoto > Version: 1.5-1 > Severity: grave > Justification: renders package unusable > > Bot invocations > ephoto > or > ephoto foo.jpg > end with > > ERR<25953>:ecore_evas lib/elementary/efl_ui_win.c:5005 > _elm_win_finalize_internal() Cannot create window. > ## Copy & Paste the below (until EOF) into a terminal, then hit Enter > > eina_btlog << EOF > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd406cc 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd413f1 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd427c3 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b38956c 0x7fb89b109000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b38b470 0x7fb89b109000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b630e 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8ae9ac 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b385142 0x7fb89b109000 > /usr/bin/ephoto0x55b70128b564 0x55b70126f000 > /usr/bin/ephoto0x55b701278a4f 0x55b70126f000 > /usr/bin/ephoto0x55b70127873c 0x55b70126f000 > /lib/x86_64-linux-gnu/libc.so.60x7fb898e3ba87 0x7fb898e1a000 > /usr/bin/ephoto0x55b70127877a 0x55b70126f000 > EOF > > ERR<25953>:eo lib/eo/eo.c:949 _efl_add_internal_end() Object of class > 'Efl.Ui.Win' - Not all of the object constructors have been executed. > ## Copy & Paste the below (until EOF) into a terminal, then hit Enter > > eina_btlog << EOF > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd406cc 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd413f1 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd427c3 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8aea8c 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b385142 0x7fb89b109000 > /usr/bin/ephoto0x55b70128b564 0x55b70126f000 > /usr/bin/ephoto0x55b701278a4f 0x55b70126f000 > /usr/bin/ephoto0x55b70127873c 0x55b70126f000 > /lib/x86_64-linux-gnu/libc.so.60x7fb898e3ba87 0x7fb898e1a000 > /usr/bin/ephoto0x55b70127877a 0x55b70126f000 > EOF > > ERR<25953>:evas_main lib/evas/canvas/evas_object_smart.c:646 > _efl_canvas_group_efl_object_destructor() efl_canvas_group_del() was not > called on this object: 0x400105da (Efl.Ui.Win) > ## Copy & Paste the below (until EOF) into a terminal, then hit Enter > > eina_btlog << EOF > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd406cc 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd413f1 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd427c3 0x7fb89cd19000 > /usr/lib/x86_64-linux-gnu/libevas.so.1 0x7fb89c71a237 0x7fb89c689000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b36ee44 0x7fb89b109000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8ae8a4 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b5642 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8aeaa7 0x7fb89b8a6000 > /usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b385142 0x7fb89b109000 > /usr/bin/ephoto0x55b70128b564 0x55b70126f000 > /usr/bin/ephoto0x55b701278a4f 0x55b70126f000 > /usr/bin/ephoto0x55b70127873c 0x55b70126f000 > /lib/x86_64-linux-gnu/libc.so.60x7fb898e3ba87 0x7fb898e1a000 > /usr/bin/ephoto0x55b70127877a 0x55b70126f000 > EOF > > > > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.16.11 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ephoto depends on: > ii libc6 2.27-3 > ii libecore-con1 1.20.7-4 > ii libecore-evas11.20.7-4 > ii libecore-file11.20.7-4 > ii libecore-imf1 1.20.7-4 > ii libecore-input1 1.20.7-4 > ii libecore-ipc1 1.20.7-4 > ii libecore1 1.20.7-4 > ii libedje1 1.20.7-4 > ii libeet1 1.20.7-4 > ii
Bug#900516: ruby-psych: Package 3.0.2 or a more recent release
Package: src:ruby-psych Version: 2.2.4-6 Severity: wishlist Owner: Miguel Landaeta As title says. JRuby 9.2.0.0 is compatible with Ruby 2.5 and that requires psych 3.0.0. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#900515: ITP: ruby-fileutils -- Ruby gem providing a namespace for several file utility methods for copying, moving, removing, etc.
Package: wnpp Severity: wishlist Owner: Miguel Landaeta * Package name: ruby-fileutils Version : 1.1.0 Upstream Author : Minero Aoki * URL : https://github.com/ruby/fileutils * License : BSD Programming Lang: Ruby Description : Ruby gem providing a Namespace for several file utility methods for copying, moving, removing, etc. Its main use case in Debian at the present time is as a JRuby dependency and it will be maintained under Debian Ruby Team umbrella. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Bug#900513: libmpdclient2: New version available
Package: libmpdclient2 Version: 2.9-1 Severity: normal Dear Maintainer, Version 2.14 of libmpdclient is available. I had to build it to fix an issue with DB proxing and artist sorting command (support added in 2.12). Upstream switched to meson, but it builds fine with debhelper (>= 11), meson (>= 0.40.1). I made a plain package out of it, I'll try to polish it and rebase it on your packaging if I can. Cheers -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libmpdclient2 depends on: ii libc6 2.24-11+deb9u3 libmpdclient2 recommends no packages. libmpdclient2 suggests no packages. -- no debconf information
Bug#900514: nmu: gnucobol_2.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Another case of a package which was uploaded before the ncurses transition and got stuck in NEW for too long. nmu gnucobol_2.2-1 . amd64 . unstable . -m "Rebuild against libncurses6."
Bug#900512: Changing domain from www.openspf.net to www.openspf.org
Package: postfix-policyd-spf-perl
Version: 2.010-2
Severity: minor
tags: wheezy jessie stretch buster sid
Per the Internet Archive, the domain http://www.openspf.net has been
replaced by http://www.openspf.org as of March, 2012:
http://web.archive.org/web/20120305084430/http:/www.openspf.net:80/
There’s a workaround for this in the Debian logwatch package for postfix:
https://sources.debian.org/patches/logwatch/7.4.3+git20161207-2/0005-postfix-Support-also-openspf.net-in-pattern-not-only.patch/
I’m wondering if you would be willing to change:
postfix-policyd-spf-perl-2.010/debian/control
From:
+ SPF project web site is http://www.openspf.net/.
To:
+ SPF project web site is http://www.openspf.org/.
postfix-policyd-spf-perl-2.010/postfix-policyd-spf-perl
From:
+ 'Please see
http://www.openspf.net/Why?s=%{_scope};id=%{S};ip=%{C};r=%{R}'
To:
+ 'Please see
http://www.openspf.org/Why?s=%{_scope};id=%{S};ip=%{C};r=%{R}'
I’m not sure if it makes sense to change
postfix-policyd-spf-perl-2.010/debian/copyright as I’m not an expert in
Debian policy
Thanks,
Josh Soref
Bug#900173: git-annex: internal error: evacuate: strange closure type 4325404
I've tried to reproduce on a newly-installed Buster VM, but haven't been able to get it to crash. I guess that at least explains why only I'm complaining — probably something weird about my two workstations that cause it. Going to see if I can find it, but welcome any suggestions as to what it might be.
Bug#900334: transition: gloox
Hi Emilio, On Wed, May 30, 2018 at 2:41 PM, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 29/05/18 11:00, Emilio Pozuelo Monfort wrote: >> On 29/05/18 10:49, Vincent Cheng wrote: >>> Package: release.debian.org >>> User: release.debian@packages.debian.org >>> Usertags: transition >>> Severity: normal >>> >>> Hi, >>> >>> I'd like to request a transition slot for src:gloox. This is a >>> relatively small transition, with only 2 source packages affected >>> (tested builds against newer gloox, currently in experimental, results >>> are as follows): >>> >>> 0ad (build ok, needs binNMU) >>> uwsgi (build ok, needs binNMU) >> >> Let's wait for the curl transition to finish. > > curl has migrated to testing today. Go ahead. I've uploaded gloox to sid and have confirmed that it's built on all release archs. Please go ahead and schedule binNMUs, thanks! Regards, Vincent
Bug#858851: debarchiver: [INTL:de] updated German man page translation
Hello Ola, On Wed, Jun 07, 2017 at 08:16:40AM +0200, Ola Lundqvist wrote: > Sorry for very late response. I did a brief check and yes it looks > odd. I'll have a look at this more as soon I can find the time. There > are some other odd sentences as well if I remember correctly. > > Best regards > > // Ola > > On 31 March 2017 at 17:47, Helge Kreutzmann wrote: > > Hello Ola, > > this one new string does not make sense: > > "The verify command. @vrfycmd is set to the list ($vrfycmd) just before the > > " > > "verify command is executed is the array is empty. It was made like this > > for " > > "backwards compatibility reasons." > > > > The second sentence is somehow broken, can you check it? Is there any news on this? If you plan an upload, please provide the de.po beforehand so that I can update it before your upload. Thanks! Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#900511: libcurl4 Conflicts: libcurl3
Package: libcurl4 Version: 7.60.0-2 Severity: serious libcurl4 conflicts with libcurl3, which violates the stated purpose of the "must" clause at Policy 8.1 (to allow multiple versions of a shared library to be co-installable), even though it doesn't violate the letter of the must (binary package name must change when SONAME changes). Without the second sentence at Policy 8.1, the MUST requirement serves no purpose, so I have given this severity serious. This means that, regardless of what Debian does with packages depending on libcurl, libcurl4 cannot be installed if the user has third party or home brew software that requires libcurl3. I found this because I have netsurf-gtk installed, which Depends: libcurl3. netsurf-gtk is currently the same version in stable and unstable, but has been removed from testing. ...Marvin -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (200, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Bug#899422: Jessie behavior
Sorry, the behavior with Jessie is not the same as that with Stretch. dmsetup.static and lvm.static require $(PTHREAD_LIBS) and -lpcre in any order If --disable-selinux is also given then dmsetup.static and lvm.static require $(PTHREAD_LIBS)
Bug#900510: squidguard: SIGHUP crashes squidGuard instead of reloading it
Package: squidguard
Version: 1.5-4
Severity: normal
Tags: upstream
Dear Maintainer,
squidGuard seems to support the SIGHUP signal to reload its
configuration, as is common for daemons. Though this doesn't seem to be
documented as far as I can tell, from the code it's obvious that it
should be supported - main.c at several points checks for sig_hup and calls
sgReloadConfig, for example:
if(sig_hup) {
sgReloadConfig();
}
sgReloadConfig is defined like this:
void sgReloadConfig()
{
struct LogFileStat *sg;
struct Source *src;
struct Destination *dest;
sig_hup = 0;
sgLogWarn("WARN: Received sigHUP, reloaded configuration");
for(sg = LogFileStat; sg != NULL; sg = sg->next){ /* closing logfiles */
if(sg->fd == stderr || sg->fd == stdout) {
continue;
}
fclose(sg->fd);
}
for(src = Source; src != NULL; src = src->next){
if(src->domainDb != NULL && src->domainDb->dbp != NULL) {
(void)src->domainDb->dbp->close(src->domainDb->dbp,0);
}
if(src->userDb != NULL && src->userDb->dbp != NULL) {
(void)src->userDb->dbp->close(src->userDb->dbp,0);
}
}
for(dest = Dest; dest != NULL; dest = dest->next){
if(dest->domainlistDb != NULL && dest->domainlistDb->dbp != NULL) {
(void)dest->domainlistDb->dbp->close(dest->domainlistDb->dbp,0);
}
if(dest->urllistDb != NULL && dest->urllistDb->dbp != NULL) {
(void)dest->urllistDb->dbp->close(dest->urllistDb->dbp,0);
}
}
sgFreeAllLists();
execve(*globalArgv,globalArgv, globalEnvp);
fprintf(stderr,"error execve: %d\n",errno);
exit(1);
}
Unfortunately, this doesn't work as expected when squidGuard is used as
url_rewrite_program in squid - sending SIGHUP to squidGuard will crash
it instead of reloading it. To reproduce:
1. strace squidGuard (works best when only a single instance is
running):
strace -p $(pidof '(squidGuard)')
2. Send SIGHUP:
pkill -SIGHUP squidGuard
3. Observe in strace that squidGuard has received the SIGHUP, but
nothing bad has happened yet:
host ~ # strace -p $(pidof '(squidGuard)')
Process 5598 attached
read(0, 0xf7779000, 4096) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGHUP {si_signo=SIGHUP, si_code=SI_USER, si_pid=8385, si_uid=0} ---
sigreturn() (mask []) = 3
read(0,
4. Send a request to squid:
http_proxy=http://localhost:3128 GET google.de > /dev/null
5. Observe in strace that squidGuard crashes:
host ~ # strace -p $(pidof '(squidGuard)')
Process 8452 attached
read(0, 0xf7737000, 4096) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGHUP {si_signo=SIGHUP, si_code=SI_USER, si_pid=8503, si_uid=0} ---
sigreturn() (mask []) = 3
read(0, "http://google.de/ 127.0.0.1/loca"..., 4096) = 71
time(NULL) = 1527782365
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
write(5, "2018-05-31 17:59:25 [8452] WARN:"..., 73) = 73
close(4)= 0
munmap(0xf7745000, 4096)= 0
close(6)= 0
munmap(0xf7743000, 4096)= 0
close(11) = 0
munmap(0xf7742000, 4096)= 0
close(14) = 0
munmap(0xf7741000, 4096)= 0
close(17) = 0
munmap(0xf774, 4096)= 0
close(20) = 0
munmap(0xf773f000, 4096)= 0
close(23) = 0
munmap(0xf773e000, 4096)= 0
close(26) = 0
munmap(0xf773d000, 4096)= 0
close(29) = 0
munmap(0xf773c000, 4096)= 0
close(32) = 0
munmap(0xf773b000, 4096)= 0
close(35) = 0
munmap(0xf773a000, 4096)= 0
close(38) = 0
munmap(0xf7739000, 4096)= 0
close(41) = 0
munmap(0xf7738000, 4096)= 0
close(5)= 0
munmap(0xf7744000, 4096)= 0
close(7)= 0
close(8)= 0
close(9)= 0
close(10) = 0
close(12) = 0
close(13) = 0
close(15) = 0
close(16) = 0
close(18) = 0
close(19) = 0
close(21) = 0
Bug#900196: dcmtk: wrongly assumes that CMAKE_SYSTEM_VERSION to be non-empty
Hi Joerg, On Thu, May 31, 2018 at 04:11:21PM +0200, Jörg Riesmeier wrote: > Instead of adding quotation marks, I would rather recommend to use the > variable name in the IF() statements and not the string value. See attached > patch (based on the current development version of the DCMTK). Thank you for the quick followup. > I just tested it and it seems to work. What do you think? I fear that I lack CMake experience and I didn't know that this was possible. Still if it works at all, it looks like the better solution indeed. It seems that the one thing to avoid is $-expanded, unquoted variables. Please go ahead. Helmut
Bug#888370: avifile: FTBFS with FFmpeg 4.0
Control: tags -1 patch
Hi,
On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote:
> Source: avifile
> Version: 1:0.7.48~20090503.ds-20
> Severity: important
> User: debian-multime...@lists.debian.org
> Usertags: ffmpeg-3.5-transition
>
> Hi,
>
> Your package FTBFS with the upcoming version 3.5 of FFmpeg.
The attached patch fixes this.
James
Description: Fix FTBFS with FFmpeg 4.0
Author: James Cowgill
Bug-Debian: https://bugs.debian.org/888370
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/lib/aviread/FFReadStream.cpp
+++ b/lib/aviread/FFReadStream.cpp
@@ -69,7 +69,7 @@ FFReadStream::FFReadStream(FFReadHandler
AVCodec* codec = avcodec_find_decoder(avs->codec->codec_id);
if (codec && avcodec_open2(m_pAvContext, codec, NULL) == 0)
{
- m_pAvContext->flags |= CODEC_FLAG_TRUNCATED;
+ m_pAvContext->flags |= AV_CODEC_FLAG_TRUNCATED;
m_pAvContext->skip_frame = AVDISCARD_NONKEY;
//printf("Opened hurryup decoder %p %p\n", codec, m_pAvContext->codec->decode);
}
--- a/plugins/libffmpeg/FFVideoDecoder.cpp
+++ b/plugins/libffmpeg/FFVideoDecoder.cpp
@@ -38,7 +38,7 @@ FFVideoDecoder::FFVideoDecoder(AVCodec*
if (0 && m_pFormat->biCompression == fccHFYU)
{
// for now disabled
- m_pAvCodec->capabilities &= ~(CODEC_CAP_DRAW_HORIZ_BAND | CODEC_CAP_DR1);
+ m_pAvCodec->capabilities &= ~(AV_CODEC_CAP_DRAW_HORIZ_BAND | AV_CODEC_CAP_DR1);
AVM_WRITE(m_Info.GetPrivateName(), "if you have troubles - use Win32 codec instead\n");
m_Caps = (CAPS) (m_Caps | CAP_YUY2);
}
@@ -191,7 +191,7 @@ int FFVideoDecoder::DecodeFrame(CImage*
const char* drtxt = "doesn't support";
m_bDirect = false;
- if (m_pAvCodec->capabilities & CODEC_CAP_DR1)
+ if (m_pAvCodec->capabilities & AV_CODEC_CAP_DR1)
{
drtxt = "not using";
if (pImage)
@@ -296,7 +296,7 @@ int FFVideoDecoder::DecodeFrame(CImage*
// try using draw_horiz_band if DR1 is unsupported
m_pAvContext->draw_horiz_band =
(!m_bDirect && pImage && pImage->Format() == IMG_FMT_YV12
- && (m_pAvCodec->capabilities & CODEC_CAP_DRAW_HORIZ_BAND)
+ && (m_pAvCodec->capabilities & AV_CODEC_CAP_DRAW_HORIZ_BAND)
&& !pImage->Direction() && render) ? draw_slice : 0;
m_pAvContext->opaque = this;
@@ -330,7 +330,7 @@ int FFVideoDecoder::DecodeFrame(CImage*
av_frame_unref(pic);
return hr;
}
-if (!(m_pAvContext->flags & CODEC_FLAG_TRUNCATED))
+if (!(m_pAvContext->flags & AV_CODEC_FLAG_TRUNCATED))
{
hr = (int)size;
//m_bUsed = true;
signature.asc
Description: OpenPGP digital signature
Bug#900509: nyx: Missing dependency on python3-distutils
Package: nyx
Version: 2.0.4-4
Severity: important
Dear Maintainer,
After installing several system updates, nyx failed to start:
=
Traceback (most recent call last):
File "/usr/bin/nyx", line 11, in
load_entry_point('nyx==2.0.4', 'console_scripts', 'nyx')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
480, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2691, in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2322, in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2328, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/nyx/__init__.py", line 46, in
import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'
=
After installing python3-distutils, nyx resumed functioning as normal.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (700, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nyx depends on:
ii python3 3.6.5-3
ii python3-stem 1.6.0-1
nyx recommends no packages.
Versions of packages nyx suggests:
ii tor 0.3.3.6-1
-- no debconf information
Bug#896667: transition: r-base-3.5
On 31/05/18 16:59, Dirk Eddelbuettel wrote: > > On 31 May 2018 at 16:17, Emilio Pozuelo Monfort wrote: > | > (Out of nerdy curiousity because we sometimes drive rebuilds of [generally > | > much smaller] subsets, where is the code that "walks" the dependency > graph? > | > Is that in libapt by chance [as I happen to have a package getting from R > to > | > libapt via Rcpp] or is it another tool I could milk for this? [ We also > have > | > something a decade old in the cran2deb repo but that is another story ... > ] > | > | Do you mean the one that generates > | https://release.debian.org/transitions/html/r-base-3.5.html ? If so, that'd > be > | ben (which is packaged). > > Not the page in the "how do I create a table in html" sense, but the "logic" > in finding out first, second, third, .. "wave". Which is probably what you > meant. But when I 'apt-cache show ben' I am no longer sure. > > So to rephrase: given a package (or set of packages), what computes the > ordered set (or "graph" in the dependency sense) of their depends (or > build-depends) ? It's ben indeed. It also creates the html page, but before doing that it calculates all the affected packages based on the .ben file (i.e. this one https://release.debian.org/transitions/config/ongoing/r-base-3.5.ben) and whether they are good, bad, both (partial) or none (unknown), and the dependency levels (the ordered set). Cheers, Emilio
Bug#896667: transition: r-base-3.5
On 31/05/18 16:56, Dirk Eddelbuettel wrote: > > On 31 May 2018 at 16:15, Emilio Pozuelo Monfort wrote: > | Hi, > | > | On 31/05/18 15:45, Emilio Pozuelo Monfort wrote: > | > On 31/05/18 15:09, Dirk Eddelbuettel wrote: > | >> > | >> Emilio, Seb, > | >> > | >> Can you confirm that now that we have > | >> a) "green light" on the transition, and > | >> b) the r-base package is in unstable > | >> we should see binary: any packages being rebuilt -- which I do not yet > | >> see. When will this start? > | > > | > I will start the rebuilds soon (i.e. later today). > | > | Scheduled now (it will take some time as it's 320 arch:any packages). > | > | By the way there was a problem with my suggested jdk change: the > architecture > | restriction is applied first, and then the first alternative is taken, so > for > | e.g. m68k, openjdk-10-jdk is taken as it's the first valid alternative for > that > | architecture. But we don't want jdk there at all. So there are two good > options: > | > | default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] > > There must be something that makes this form not preferred as I had been > using the "concretePackage | virtualPackage" form for many years. > > If we did this, I would not have to jump through hoops updating the package > ... > | > | i.e. drop the openjdk-10-jdk alternative, or > | > | default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] | > | openjdk-10-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] > > ... yet the other day I needed the form with openjdk-10 (as r-cran-rjava > failed with with given that "its" r-base has still used openjdk-9. > > So I think the second form is better. I can do a quick rebuild if you concur. Yes, that sounds good. Thanks! Emilio
Bug#900508: jabber-querybot: error in preinst
Package: jabber-querybot Version: 0.1.0-1 Severity: important User: trei...@debian.org Usertags: colis-shparser Hi, preinst contains: if [ /etc/jabber-querybot/Querymodule.pm -ef /usr/share/doc/jabber-querybot/examples/Testbot.pm ]; this will not work, due to the missing line continuation in the bracket test (add a backslash before the line break). This preinst will fail on upgrade. -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#900507: mailgraph: preinst has wrong test operator
Package: mailgraph Version: 1.14-15 User: trei...@debian.org Usertags: colis-shparser Hi, preinst contains if [ "$2" \< "1.13-1.1" ]; then "<" is not even a POSIX test operator, even though it exists in dash. Anyway, please use "dpkg --compare-versions" to compare debian versions as the order on versions is not the same as the string order. -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#900506: libmtp9: wrong bracket test in preinst
Package: libmtp9 Version: 1.1.13-1 Serious: important User: trei...@debian.org Usertags: colis-shparser Hi, preinst contains (line 41) : if [ "$name" = "libmtp6" -a ! "$version" = ""]; then there is a space missing before the closing bracket of the last test, which may make the script fail like this: [: missing ] -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#900505: segfault at 21c1, error 4 in tmux[559568e28000+84000]
Package: tmux Version: 2.7-1+b1 Severity: normal Dear Maintainer, I got this error: tmux: server[2747]: segfault at 21c1 ip 559568e52a5a sp 7ffefc121c68 error 4 in tmux[559568e28000+84000] I'm not entirely sure how to reproduce it, I am filing this report in case anyone else has the same issue. I'll add more information if I manage to reproduce it. I was using tmux with several panes and with fish shell, I had just copied something to one of the panels and tmux crashed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tmux depends on: ii libc6 2.27-3 ii libevent-2.1-6 2.1.8-stable-4 ii libtinfo6 6.1+20180210-4 ii libutempter01.1.6-3 tmux recommends no packages. tmux suggests no packages. -- no debconf information
Bug#900504: gnuplot-qt: wrong bracket test in postinst
Package: gnuplot-qt Version: 5.2.2+dfsg1-2 Severity: important User: trei...@debian.org Usertags: colis-shparser iHi, postinst contains if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" != "upgrade"]; then there is a space missing before the closing bracket of the last test, which may make the postinst fail like this: [: missing ] -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#900503: xbacklight: Packagely solve the case of intel_backlight
Package: xbacklight
Version: 1.2.1-1+b2
Severity: normal
Dear Maintainer,
hello, i have an
asus x55v (intel video) and wanted to use xbacklight.
I got many case of failures :
xbacklight -inc 1
-> No outputs have backlight property
DISPLAY=`xrandr | grep ' connected primary' | awk '{print $1};'`
xbacklight -d $DISPLAY -inc 1
-> RANDR Query Version returned error -1
Therefore i search around internet, and there is 2 solutions which
doesn't imply to change the code of xbacklight.
1 - using xbacklight from https://github.com/wavexx/acpilight (or
some fork), which rely on /sys/class/backlight/*.
To use write on /sys/class/backlight/*/brightness, simple udev
rules have to be added in /etc/udev/rules.d/ (these rules are in the git)
2 - finding a way to setup automatically intel card backlight option
in xorg script.
Section "Device"
Identifier "Card0"
Driver "intel"
Option "Backlight" "intel_backlight"
BusID "PCI:0:2:0"
EndSection
(In fact i had 3 asus computers and every time the same things was
to reconfigure again and again. I stopped to use xbacklight and used
a sudo script just for myself... )
Hope these elements could help for intel video card computers.
Have a nice day.
-- System Information:
Debian Release: 9.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xbacklight depends on:
ii libc6 2.27-3
ii libxcb-randr0 1.12-1
ii libxcb-util0 0.3.8-3+b2
ii libxcb11.12-1
xbacklight recommends no packages.
xbacklight suggests no packages.
-- no debconf information
--
_luffah_
Bug#896667: transition: r-base-3.5
On 31 May 2018 at 16:17, Emilio Pozuelo Monfort wrote: | > (Out of nerdy curiousity because we sometimes drive rebuilds of [generally | > much smaller] subsets, where is the code that "walks" the dependency graph? | > Is that in libapt by chance [as I happen to have a package getting from R to | > libapt via Rcpp] or is it another tool I could milk for this? [ We also have | > something a decade old in the cran2deb repo but that is another story ... ] | | Do you mean the one that generates | https://release.debian.org/transitions/html/r-base-3.5.html ? If so, that'd be | ben (which is packaged). Not the page in the "how do I create a table in html" sense, but the "logic" in finding out first, second, third, .. "wave". Which is probably what you meant. But when I 'apt-cache show ben' I am no longer sure. So to rephrase: given a package (or set of packages), what computes the ordered set (or "graph" in the dependency sense) of their depends (or build-depends) ? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#900501: gnuplot-x11: wrong bracket test in postinst
Package: gnuplot-x11 Version: 5.2.2+dfsg1-2 Severity: important User: trei...@debian.org Usertags: colis-shparser Hi, postinst contains if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" != "upgrade"]; then there is a space missing before the closing bracket of the last test, which may make the postinst fail like this: [: missing ] -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#896667: transition: r-base-3.5
On 31 May 2018 at 16:15, Emilio Pozuelo Monfort wrote: | Hi, | | On 31/05/18 15:45, Emilio Pozuelo Monfort wrote: | > On 31/05/18 15:09, Dirk Eddelbuettel wrote: | >> | >> Emilio, Seb, | >> | >> Can you confirm that now that we have | >> a) "green light" on the transition, and | >> b) the r-base package is in unstable | >> we should see binary: any packages being rebuilt -- which I do not yet | >> see. When will this start? | > | > I will start the rebuilds soon (i.e. later today). | | Scheduled now (it will take some time as it's 320 arch:any packages). | | By the way there was a problem with my suggested jdk change: the architecture | restriction is applied first, and then the first alternative is taken, so for | e.g. m68k, openjdk-10-jdk is taken as it's the first valid alternative for that | architecture. But we don't want jdk there at all. So there are two good options: | | default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] There must be something that makes this form not preferred as I had been using the "concretePackage | virtualPackage" form for many years. If we did this, I would not have to jump through hoops updating the package ... | | i.e. drop the openjdk-10-jdk alternative, or | | default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] | | openjdk-10-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] ... yet the other day I needed the form with openjdk-10 (as r-cran-rjava failed with with given that "its" r-base has still used openjdk-9. So I think the second form is better. I can do a quick rebuild if you concur. | | i.e. add the architecture restriction to openjdk-10-jdk as well. | | I'd go with the former, but both should work. If you can apply one of those | changes that'd help. | | Sorry for not realising that earlier. No worries. It's just cycles :) Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#900500: python3-ironic-ui: wrong test in postrm
Package: python3-ironic-ui Version: 3.1.0-1 Severity: important User: trei...@debian.org Usertags: colis-shparser Hi the postrm contains: if [ "$1" = "remove" ] || [ "$1" = "disappear" ] [ "$1" = "purge" ] ; then there is a || missing between the last two tests. This may make the postrm fail. -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#900499: python3-heat-dashboard: wrong test in postrm
Package: python3-heat-dashboard Version: 1.0.2+dfsg1-2 Severity: important User: trei...@debian.org Usertags: colis-shparser Hi the postrm contains: if [ "$1" = "remove" ] || [ "$1" = "disappear" ] [ "$1" = "purge" ] ; then there is a || missing between the last two tests. This may make the postrm fail. -Ralf. -- Ralf Treinen Institut de Recherche en Informatique Fondamentale Équipe Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.irif.fr/~treinen/
Bug#898561: libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures)
On Thu, 31 May 2018 13:57:04 +0200, Tina Müller wrote: > It seems that MARC::Transform itself is fine, and only its test suite > needs a tiny patch. Nodes containing '#' just need to be quoted. > I attached the patch to this email. Thanks! Patch applied, package uploaded. Cheers, greor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Red Hot Chili Peppers: Parallel Universe signature.asc Description: Digital Signature
Bug#900498: TP: pypette -- Ridiculously simple flow controller for building complex pipelines
Package: wnpp Severity: wishlist Owner: Josue Ortega *Package name: pypette Version: 0.0.9 Upstream Author: Vishwas B Sharma *URL: https://csurfer.github.io/pypette *Licence: MIT Programming Lang: Python Description: pypette (to be read as pipette) is a module which makes building pipelines ridiculously simple, allowing users to control the flow with minimal instructions. *Features* - Ridiculously simple interface. - Ability to view pipeline structure within the comfort of a terminal. - Run pipeline in exception resilient way if needed. - Create dependencies on pipelines easily. - Generate a easy to view/understand report within the comfort of a terminal. -- Josue Ortega «Happy Hacking» http://josueortega.org signature.asc Description: PGP signature
Bug#900497: libgl1-mesa-dri: Causes random freezes in plasmashell
Package: libgl1-mesa-dri Severity: critical Tags: patch upstream Justification: breaks unrelated software Dear Maintainer, Currently, with the mesa driver and xorg 1.20, plasmashell randomly freezes every few seconds. The bug has been reported as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900352 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900149 but it is actually a bug in mesa. It is fixed by this upstream commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=fe2edb25dd5628c395a65b60998f11e839d2b458 I just applied said patch locally and rebuilt mesa, and I can confirm that it fixes the issue. Best regards, Vivia Nikolaidou -- Package-specific info: glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2) (0x161e) Version: 18.1.0 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.0 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, GL_ARB_conditional_render_inverted,
Bug#888367: qtav: FTBFS with FFmpeg 4.0
Control: tags -1 patch fixed-upstream
Hi,
On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote:
> Source: qtav
> Version: 1.12.0+ds-4
> Severity: important
> User: debian-multime...@lists.debian.org
> Usertags: ffmpeg-3.5-transition
>
> Hi,
>
> Your package FTBFS with the upcoming version 3.5 of FFmpeg.
The following two upstream commits (also attached) fix this:
https://github.com/wang-bin/QtAV/commit/7f6929b49c25ca475a08f87e8b52aa1642d109dd
https://github.com/wang-bin/QtAV/commit/1633f2962e195eb2a013072e694a2e1c701613a8
James
From 7f6929b49c25ca475a08f87e8b52aa1642d109dd Mon Sep 17 00:00:00 2001
From: Felix Matouschek
Date: Sat, 11 Nov 2017 10:13:06 +0100
Subject: [PATCH] Make QtAV build with newer versions of FFmpeg
Some defines changed their name in newer versions of FFmpeg, this
patch uses preprocessor instructions in AVCompat.h to use the
correct define names. Also filter names retrieved by
'avfilter_get_by_name' should be used as const variables in
libavfilter versions starting at 7.0.0.
---
src/AVMuxer.cpp | 2 +-
src/QtAV/private/AVCompat.h | 12
src/codec/audio/AudioEncoderFFmpeg.cpp | 4 ++--
src/codec/video/VideoEncoderFFmpeg.cpp | 2 +-
src/filter/LibAVFilter.cpp | 8 +++-
src/subtitle/SubtitleProcessorFFmpeg.cpp | 2 +-
6 files changed, 24 insertions(+), 6 deletions(-)
diff --git a/src/AVMuxer.cpp b/src/AVMuxer.cpp
index 2f0b40d0..d2eb3dde 100644
--- a/src/AVMuxer.cpp
+++ b/src/AVMuxer.cpp
@@ -124,7 +124,7 @@ AVStream *AVMuxer::Private::addStream(AVFormatContext* ctx, const QString
c->time_base = s->time_base;
/* Some formats want stream headers to be separate. */
if (ctx->oformat->flags & AVFMT_GLOBALHEADER)
-c->flags |= CODEC_FLAG_GLOBAL_HEADER;
+c->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
// expose avctx to encoder and set properties in encoder?
// list codecs for a given format in ui
return s;
diff --git a/src/QtAV/private/AVCompat.h b/src/QtAV/private/AVCompat.h
index e387868a..6c38596d 100644
--- a/src/QtAV/private/AVCompat.h
+++ b/src/QtAV/private/AVCompat.h
@@ -456,3 +456,15 @@ const char *get_codec_long_name(AVCodecID id);
} } while(0)
#endif //QTAV_COMPAT_H
+
+#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56,33,0)
+#define AV_CODEC_FLAG_GLOBAL_HEADER CODEC_FLAG_GLOBAL_HEADER
+#endif
+
+#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56,56,100)
+#define AV_INPUT_BUFFER_MIN_SIZE FF_MIN_BUFFER_SIZE
+#endif
+
+#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56,56,100)
+#define AV_INPUT_BUFFER_PADDING_SIZE FF_INPUT_BUFFER_PADDING_SIZE
+#endif
diff --git a/src/codec/audio/AudioEncoderFFmpeg.cpp b/src/codec/audio/AudioEncoderFFmpeg.cpp
index a74f4f31..3811e11a 100644
--- a/src/codec/audio/AudioEncoderFFmpeg.cpp
+++ b/src/codec/audio/AudioEncoderFFmpeg.cpp
@@ -151,8 +151,8 @@ bool AudioEncoderFFmpegPrivate::open()
} else {
buffer_size = frame_size*format_used.bytesPerSample()*format_used.channels()*2+200;
}
-if (buffer_size < FF_MIN_BUFFER_SIZE)
-buffer_size = FF_MIN_BUFFER_SIZE;
+if (buffer_size < AV_INPUT_BUFFER_MIN_SIZE)
+buffer_size = AV_INPUT_BUFFER_MIN_SIZE;
buffer.resize(buffer_size);
return true;
}
diff --git a/src/codec/video/VideoEncoderFFmpeg.cpp b/src/codec/video/VideoEncoderFFmpeg.cpp
index 7c5ed42d..671efa7d 100644
--- a/src/codec/video/VideoEncoderFFmpeg.cpp
+++ b/src/codec/video/VideoEncoderFFmpeg.cpp
@@ -245,7 +245,7 @@ bool VideoEncoderFFmpegPrivate::open()
applyOptionsForContext();
AV_ENSURE_OK(avcodec_open2(avctx, codec, ), false);
// from mpv ao_lavc
-const int buffer_size = qMax(qMax(width*height*6+200, FF_MIN_BUFFER_SIZE), sizeof(AVPicture));//??
+const int buffer_size = qMax(qMax(width*height*6+200, AV_INPUT_BUFFER_MIN_SIZE), sizeof(AVPicture));//??
buffer.resize(buffer_size);
return true;
}
diff --git a/src/filter/LibAVFilter.cpp b/src/filter/LibAVFilter.cpp
index 19151204..8993a91f 100644
--- a/src/filter/LibAVFilter.cpp
+++ b/src/filter/LibAVFilter.cpp
@@ -120,7 +120,10 @@ public:
// pixel_aspect==sar, pixel_aspect is more compatible
QString buffersrc_args = args;
qDebug("buffersrc_args=%s", buffersrc_args.toUtf8().constData());
-AVFilter *buffersrc = avfilter_get_by_name(video ? "buffer" : "abuffer");
+#if LIBAVFILTER_VERSION_INT >= AV_VERSION_INT(7,0,0)
+const
+#endif
+AVFilter *buffersrc = avfilter_get_by_name(video ? "buffer" : "abuffer");
Q_ASSERT(buffersrc);
AV_ENSURE_OK(avfilter_graph_create_filter(_filter_ctx,
buffersrc,
@@ -128,6 +131,9 @@ public:
filter_graph)
, false);
/* buffer video sink: to terminate the filter chain. */
+#if LIBAVFILTER_VERSION_INT >= AV_VERSION_INT(7,0,0)
+const
+#endif
AVFilter *buffersink =
