Bug#855544: gitsome: embedded code copy of xonsh in source package + file conflict on installation: trying to overwrite '/usr/bin/xonsh', which is also in package xonsh 0.5.5+dfsg-1

Hi, SZ Lin (林上智) wrote: > Since xonsh version in gitsome (0.2.2) varies greatly from the version of > SID (0.5.5+dfsg-1), I think it might have potential compatibility issues by > using the SID version. Questions are: * Is it necessary that it varies, i.e. that the old version of xonsh is

Bug#855491: marked as done (texlive-latex-recommended: emph macro is broken in fontspec 2.5c; please update to 2.5d)

Your message dated Mon, 20 Feb 2017 06:35:26 + with message-id and subject line Bug#855491: fixed in texlive-base 2016.20170123-4 has caused the Debian Bug report #855491, regarding texlive-latex-recommended: emph macro is broken in fontspec 2.5c; please

Bug#853769: marked as done (opendkim: Default systemd service does not read the configuration file)

Your message dated Mon, 20 Feb 2017 00:03:26 -0500 with message-id <5334532.MmRNLRdGih@kitterma-e6430> and subject line Re: opendkim: Default systemd service does not read the configuration file has caused the Debian Bug report #853769, regarding opendkim: Default systemd service does not read

Bug#834921: marked as done (python-ws4py FTBFS: WSManagerTest fails)

Your message dated Mon, 20 Feb 2017 04:07:58 + with message-id and subject line Bug#834921: fixed in python-ws4py 0.3.4-4 has caused the Debian Bug report #834921, regarding python-ws4py FTBFS: WSManagerTest fails to be marked as done. This means that you

Bug#851043: marked as done (python-ws4py FTBFS: WSManagerTest fails)

Your message dated Mon, 20 Feb 2017 04:07:58 + with message-id and subject line Bug#834921: fixed in python-ws4py 0.3.4-4 has caused the Debian Bug report #834921, regarding python-ws4py FTBFS: WSManagerTest fails to be marked as done. This means that you

Bug#855544: gitsome: embedded code copy of xonsh in source package + file conflict on installation: trying to overwrite '/usr/bin/xonsh', which is also in package xonsh 0.5.5+dfsg-1

Hi Abe, Since xonsh version in gitsome (0.2.2) varies greatly from the version of SID (0.5.5+dfsg-1), I think it might have potential compatibility issues by using the SID version. Perhaps it is more proper to rename the bundled copies of the xonsh executable rather than build-depend on it. Do

Bug#855484: marked as done (unbound: Missing trust anchor for root KSK-2017 key)

Your message dated Mon, 20 Feb 2017 01:51:52 + with message-id and subject line Bug#855484: fixed in unbound 1.6.0-3 has caused the Debian Bug report #855484, regarding unbound: Missing trust anchor for root KSK-2017 key to be marked as done. This means

Bug#855548: marked as done (hdmi2usb-fx2-firmware: --mode serial doesn't work)

Your message dated Mon, 20 Feb 2017 01:34:55 + with message-id and subject line Bug#855548: fixed in hdmi2usb-fx2-firmware 0.0.0~git20151225-1 has caused the Debian Bug report #855548, regarding hdmi2usb-fx2-firmware: --mode serial doesn't work to be

Bug#855529: marked as done (chromium-widevine: dbgsym package in contrib causes src package to also go into contrib)

Your message dated Mon, 20 Feb 2017 01:21:15 + with message-id and subject line Bug#855529: fixed in chromium-browser 56.0.2924.76-4 has caused the Debian Bug report #855529, regarding chromium-widevine: dbgsym package in contrib causes src package to

Processed: hdmi2usb-fx2-firmware: --mode serial doesn't work

Processing control commands: > affects -1 hdmi2usb-mode-switch Bug #855548 [hdmi2usb-fx2-firmware] hdmi2usb-fx2-firmware: --mode serial doesn't work Added indication that 855548 affects hdmi2usb-mode-switch -- 855548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855548 Debian Bug Tracking

Bug#855548: hdmi2usb-fx2-firmware: --mode serial doesn't work

Package: hdmi2usb-fx2-firmware Version: 0.0.0~git20151018-1 Severity: grave Justification: renders package unusable Control: affects -1 hdmi2usb-mode-switch hdmi2usb-mode-switch usually needs to put an opsis into serial mode, before it'll successfully flash an image. Currently, the uart image

Processed: found 855544 in 0.6.0-1

Processing commands for cont...@bugs.debian.org: > # Forgot to add version number of not-installed package > found 855544 0.6.0-1 Bug #855544 [gitsome] gitsome: embedded code copy of xonsh in source package + file conflict on installation: trying to overwrite '/usr/bin/xonsh', which is also in

Bug#855547: gitsome: fails to run

Package: gitsome Version: 0.6.0-1 Severity: grave Justification: renders package unusable $ gh configure Traceback (most recent call last): File "/usr/bin/gh", line 11, in load_entry_point('gitsome==0.6.0', 'console_scripts', 'gh')() File

Bug#855544: gitsome: embedded code copy of xonsh in source package + file conflict on installation: trying to overwrite '/usr/bin/xonsh', which is also in package xonsh 0.5.5+dfsg-1

Package: gitsome Severity: serious Hi, trying to install gitsome while xonsh is already installed fails as follows: Unpacking gitsome (0.6.0-1) ... dpkg: error processing archive /var/cache/apt/archives/gitsome_0.6.0-1_all.deb (--unpack): trying to overwrite '/usr/bin/xonsh', which is also in

Bug#855545: gitsome: uses old bundled xonsh (0.2.2 vs. 0.5.5)

Package: gitsome Version: 0.6.0-1 Severity: serious Justification: Policy 4.13; 6.6(4) gitsome uses a bundled copy of xonsh 0.2.2, and is thereby impossible to install alongside Debian's separate xonsh package: Unpacking gitsome (0.6.0-1) ... dpkg: error processing archive

Bug#855540: marked as done (bind9: CVE-2016-8864 causes more regressions)

Your message dated Mon, 20 Feb 2017 00:18:32 + with message-id and subject line Bug#855540: fixed in bind9 1:9.10.3.dfsg.P4-12 has caused the Debian Bug report #855540, regarding bind9: CVE-2016-8864 causes more regressions to be marked as done. This

Bug#855520: marked as done (bind9: CVE-2017-3135: Assertion failure when using DNS64 and RPZ can lead to crash)

Your message dated Mon, 20 Feb 2017 00:18:32 + with message-id and subject line Bug#855520: fixed in bind9 1:9.10.3.dfsg.P4-12 has caused the Debian Bug report #855520, regarding bind9: CVE-2017-3135: Assertion failure when using DNS64 and RPZ can lead to

Bug#820381: rar crashes.

control: tag -1 moreinfo I tried rar on up to date i386 and amd64 stretch systems. Versions 5.3 and 5.4 both work fine for me. I am not sure if this is related or not, but linux 4.8.15-1 changes vsyscall, which was mentioned in message #25. Has anyone else tested this lately? Best wishes,

Processed: Re: Bug#820381: rar crashes.

Processing control commands: > tag -1 moreinfo Bug #820381 [rar] rar crashes. Bug #849546 [rar] rar t - segmentation fault Added tag(s) moreinfo. Added tag(s) moreinfo. -- 820381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820381 849546:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 851066 851819 Bug #851066 [flashplugin-nonfree] flashplugin-nonfree: Mismatch between detected and available versions (Download file not available at people.debian.org) Bug #853095 [flashplugin-nonfree] flashplugin-nonfree: Unable to

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 854657 wishlist Bug #854657 [flashplugin-nonfree] allow users to create the .asc files themselves Severity set to 'wishlist' from 'normal' > severity 855175 wishlist Bug #855175 [flashplugin-nonfree] add option to bypass security checks

Bug#855541: purple-matrix: Not ready for release yet

Package: purple-matrix Version: 0.0.0+git20170105-1 Severity: serious Hi, I think this version shouldn't be shipped with the next release. Like the description says, it's "somewhat alpha". It works some times, but then stops working, it crashes, and so on. Kurt

Bug#855540: bind9: CVE-2016-8864 causes more regressions

package: src:bind9 severity: grave version: 1:9.10.3.dfsg.P4-11 The fix for this issue causes more regressions.

Processed: fix version for 816699

Processing commands for cont...@bugs.debian.org: > found 816699 ga/5.3+dfsg-1 Bug #816699 [src:ga] libga-dev and libarmci-mpi-dev: error when trying to install together Marked as found in versions ga/5.3+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#855324: pdfsam fails to start

On Sun, 19 Feb 2017 18:09:22 +0100, Philip Rinn wrote: > On 19.02.2017 at 04:56, gregor herrmann wrote: > > After this change, pdfsam starts for me and shows me an empty white > > window (or grey-ish) with nothing in it. > Uh, strange. So this seems not to be a general fix :( > Gregor, could you

Processed (with 1 error): reassign 816699

Processing commands for cont...@bugs.debian.org: > reassign 816699 src:ga Bug #816699 [src:ga,libarmci-mpi-dev] libga-dev and libarmci-mpi-dev: error when trying to install together Bug reassigned from package 'src:ga,libarmci-mpi-dev' to 'src:ga'. No longer marked as found in versions

Bug#794856: fixed in opencv 3.0.0+dfsg-1~exp1

Hi Nobuhiro, I've pushed a new OpenCV version excluding the Lenna images to delayed/5 and the vcs. Please tell me, if I should delay it further. I will take care of the unblock request once it's true, as well. Cheers Jochen signature.asc Description: PGP signature

Bug#816699: [Debichem-devel] Bug#816699: libga-dev and libarmci-mpi-dev: error when trying to install together

Control: reassign -1 src:ga/5.3+dfsg-1 Hi, On Fri, Mar 04, 2016 at 08:12:10PM +0100, Michael Banck wrote: > Thanks for the report. I guess it makes sense considering armci-mpi is > a reimplementation oft the libarmci.a library in GA. > > The mid-term plan is to build GA against libarmci-dev, I

Bug#851060: marked as pending

Hello Axel This compiler flag (-fno-strict-aliasing) is needed in libnids. You are right. I will revert this change in dsniff. I added the other flag (-g) in order to avoid creating an empty dbgsym package. I cannot reproduce this bug in amd64 with the current libnids package version

Bug#854849: Pending fixes for bugs in the golang-github-mattn-go-sqlite3 package

tag 854849 + pending thanks Some bugs in the golang-github-mattn-go-sqlite3 package are closed in revision 6b12265985334d09d9ee7b5460541953262b521c in branch ' debian/jessie-backports' by Martín Ferrari The full diff can be seen at

Processed: Pending fixes for bugs in the golang-github-mattn-go-sqlite3 package

Processing commands for cont...@bugs.debian.org: > tag 854849 + pending Bug #854849 {Done: Martín Ferrari } [golang-github-mattn-go-sqlite3] sqlite3.go's bind func causes cgo pointer panic. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you

Bug#854535: uwsgi: dpkg-buildpackage fails due to open with O_TMPFILE

Quoting Jonas Smedegaard (2017-02-12 21:30:32) > Hi Nobuhiro, > > Quoting Nobuhiro Iwamatsu (2017-02-09 05:09:39) > >>> This error is caused by updated libc6. > >>> The changelog in libc6(2.19-18+deb8u6) says as follows. > >>> > >>> - Fix open and openat functions with O_TMPFILE. Closes:

Bug#855529: chromium-widevine: dbgsym package in contrib causes src package to also go into contrib

package: chromium-widevine severity: serious version: 55.0.2883.75-6 Just like #824169, the contrib dbgsym binary package causes the source package to be duplicated in contrib. Best wishes, Mike

Bug#852732: marked as done (torbrowser-launcher: upon upggrade 6.0.8 to 6.5: "SIGNATURE VERIFICATION FAILED: You might be under attack ...")

Your message dated Sun, 19 Feb 2017 19:35:53 + with message-id and subject line Bug#852732: fixed in torbrowser-launcher 0.2.7-1 has caused the Debian Bug report #852732, regarding torbrowser-launcher: upon upggrade 6.0.8 to 6.5: "SIGNATURE VERIFICATION

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 855522 important Bug #855522 [torbrowser-launcher] torbrowser-launcher: torbrowser won't start because of apparmor Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#855522: [Pkg-privacy-maintainers] Bug#855522: torbrowser-launcher: torbrowser won't start because of apparmor

Hi, Julien AUBIN: > Package: torbrowser-launcher > Version: 0.2.6-3 > Severity: grave Thanks for your bug report. Instead of working around this by disabling the profile, here is the modification which was done upstream:

Bug#812574: grub-pc: wants to overwrite admin configuration on each upgrade

On Mon, Jan 02, 2017 at 12:37:32PM +0100, Thorsten Glaser wrote: > On Sat, 31 Dec 2016, Colin Watson wrote: > > The current postinst is certainly trying to use ucf in such a way, so > > let's try to debug this. Please could you: > > Oh ok. Let me check that this system is affected first…

Bug#826216: marked as done (w3c-sgml-lib: inconsistencies in copyright file)

Your message dated Sun, 19 Feb 2017 18:03:35 + with message-id and subject line Bug#826216: fixed in w3c-sgml-lib 1.3-2 has caused the Debian Bug report #826216, regarding w3c-sgml-lib: inconsistencies in copyright file to be marked as done. This means

Processed: Bug#855478 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 855478 pending Bug #855478 [src:x265] x265: Incomplete debian/copyright? Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 855478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855478

Bug#855478: marked as pending

tag 855478 pending thanks Hello, Bug #855478 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://anonscm.debian.org/git/pkg-multimedia/x265.git/commit/?id=65d0e08 --- commit

Bug#855522: torbrowser-launcher: torbrowser won't start because of apparmor

Package: torbrowser-launcher Version: 0.2.6-3 Severity: grave Justification: renders package unusable Hi, As of now the AppArmor profile for torbrowser-launcher renders it unusable. Workaround consists in launching this command : sudo aa-disable torbrowser.start-tor-browser If you don't do so,

Bug#855521: lxpanel: freezes all the desktop environment if started or lauch no matter desktop are used

Package: lxpanel Version: 0.7.2-1 Severity: grave Justification: renders package unusable lxpanel complety freezes the environment desktop no matter what desktop are used how to reproduce: install debian LXDE and then when completed and start firts sesions logout and install compelte MATE

Processed: retitle 855520 to bind9: CVE-2017-3135: Assertion failure when using DNS64 and RPZ can lead to crash

Processing commands for cont...@bugs.debian.org: > # fix subject > retitle 855520 bind9: CVE-2017-3135: Assertion failure when using DNS64 and > RPZ can lead to crash Bug #855520 [src:bind9] bind9: CVE-2017-3135: Changed Bug title to 'bind9: CVE-2017-3135: Assertion failure when using DNS64

Bug#855520: bind9: CVE-2017-3135:

Source: bind9 Version: 1:9.9.5.dfsg-9 Severity: grave Tags: patch security upstream Hi, the following vulnerability was published for bind9. CVE-2017-3135[0]: Assertion failure when using DNS64 and RPZ can lead to crash If you fix the vulnerability please also make sure to include the CVE

Bug#855324: pdfsam fails to start

Hi, On 19.02.2017 at 04:56, gregor herrmann wrote: > After this change, pdfsam starts for me and shows me an empty white > window (or grey-ish) with nothing in it. Uh, strange. So this seems not to be a general fix :( Gregor, could you try '0'? > And now it gets weird: I tried

Bug#855324: pdfsam fails to start

Hi Tony, On 19.02.2017 at 03:25, tony mancill wrote: > As a work-around, would you mind trying to following to see if it > resolves the problem for you? > > Change the value in the element ~/.pdfsam/config.xml to '1': > > ... > > > 1 >^ >| > ... This

Bug#855514: closed by Michael Biebl <bi...@debian.org> (Re: Bug#855514: MATE does'n save settings if using gconf gsettings backend and gstreamer: DEPENDS of DCONF not are solved)

https://packages.debian.org/jessie/libs/libdconf-dbus-1-0 the problem are that i not installed dconf-gsettings-backend i installed gconf-gsettings-backend and mate related packages not take care if those depends on dconf-service and libdconf-dbus-1-0 Lenz McKAY Gerardo (PICCORO)

Processed: Re: Bug#814030: Security flaw fixed in version 6.2.0

Processing control commands: > retitle -1 tcpdf: CVE-2017-6100: LFI posting internal files externally > abusing default parameter Bug #814030 {Done: Raphael Hertzog } [php-tcpdf] Security flaw fixed in version 6.2.0 Changed Bug title to 'tcpdf: CVE-2017-6100: LFI posting

Bug#855514: marked as done (MATE does'n save settings if using gconf gsettings backend and gstreamer: DEPENDS of DCONF not are solved)

Your message dated Sun, 19 Feb 2017 17:40:57 +0100 with message-id <27ac0cf8-4181-e52e-80ea-35df19f6c...@debian.org> and subject line Re: Bug#855514: MATE does'n save settings if using gconf gsettings backend and gstreamer: DEPENDS of DCONF not are solved has caused the Debian Bug report #855514,

Bug#814030: Security flaw fixed in version 6.2.0

Control: retitle -1 tcpdf: CVE-2017-6100: LFI posting internal files externally abusing default parameter Hi, On Mon, Jan 09, 2017 at 09:39:30PM +0100, Raphael Hertzog wrote: > On Thu, 05 Jan 2017, Raphael Hertzog wrote: > > CCing upstream author for confirmation. Nicola we are trying to

Processed: Re: Bug#854866: solaar: Solaar did not have permissions to open my receiver

Processing control commands: > severity -1 important Bug #854866 [solaar] solaar: Solaar did not have permissions to open my receiver Severity set to 'important' from 'grave' -- 854866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854866 Debian Bug Tracking System Contact

Bug#854866: solaar: Solaar did not have permissions to open my receiver

Control: severity -1 important Hi, On Sun, 12 Feb 2017 23:31:02 +0100, Stephen Kitt wrote: > On Sat, 11 Feb 2017 12:07:45 +0100, gregory bahde > wrote: > >* What led up to the situation? > > installing it > >* What exactly did you do (or not

Bug#842208: mozart-stdlib: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: mozart (>= 1.4.0)

mozart will not build on 64 bit architectures. amd64 should run the i386 binaries. On Fri, 10 Feb 2017 at 22:15 Hans Joachim Desserud wrote: > I looked a bit at this issue and it seems the reason it fails on > amd64 is that mozart isn't built for this architecture > (see

Bug#828511: marked as done (pound: FTBFS with openssl 1.1.0)

Your message dated Sun, 19 Feb 2017 15:04:22 + with message-id and subject line Bug#828511: fixed in pound 2.7-1.3 has caused the Debian Bug report #828511, regarding pound: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the

Bug#855514: MATE does'n save settings if using gconf gsettings backend and gstreamer: DEPENDS of DCONF not are solved

Package: dconf-gsettings-backend Version: 0.22.0-1 Severity: serious How reproducible: Always - If "libdconf-dbus" and "dconf-service" not installed, so gconf cannot comunicate by itself to dbus, that's grave! due package gsettings-backend are offers by two flavors: dconf-gsettings-backend and

Bug#855510: python-slimit: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/python2.7/dist-packages/slimit/__init__.py

Package: python-slimit Version: 0.8.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'sid' fails because it tries to overwrite other

Processed: pound: diff for NMU version 2.7-1.3

Processing control commands: > tags 828511 + patch Bug #828511 [src:pound] pound: FTBFS with openssl 1.1.0 Added tag(s) patch. -- 828511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#828511: pound: diff for NMU version 2.7-1.3

Control: tags 828511 + patch Dear maintainer, I've prepared an NMU for pound (versioned as 2.7-1.3). The diff is attached to this message. Regards. Sebastian diff -Nru pound-2.7/debian/changelog pound-2.7/debian/changelog --- pound-2.7/debian/changelog 2016-07-31 11:40:52.0 +0200 +++

Bug#816699: libga-dev and libarmci-mpi-dev: error when trying to install together

Followup-For: Bug #816699 Neither src:armci-mpi nor src:ga have rdepends or reverse build-depends in stretch, so removing them both from stetch would be OK if this file conflict is not solved. Andreas

Bug#855509: golang-cfssl: /usr/bin/mkbundle already used by mono-devel

Package: golang-cfssl Version: 1.2.0+git20160825.89.7fb22c8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Since mono-devel uses this binary name

Processed: severity of 835546 is serious, found 835546 in 1:5.0~svn294894-1

Processing commands for cont...@bugs.debian.org: > # and once again with 5.0 vs. 4.0 ... > severity 835546 serious Bug #835546 [src:llvm-toolchain-snapshot] llvm-toolchain-snapshot: use Provides/Conflicts/Replaces on a some packages Severity set to 'serious' from 'normal' > found 835546

Processed: Re: Bug#855480: examl: FTBFS with bash as /bin/sh

Processing commands for cont...@bugs.debian.org: > tags 855480 pending Bug #855480 [src:examl] examl: FTBFS with bash as /bin/sh Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 855480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855480

Bug#855376: marked as done (php7.1-readline: Unmet dependencies in jessie-backports)

Your message dated Sun, 19 Feb 2017 10:48:39 +0100 with message-id <1487497719.630056.885713176.10aaf...@webmail.messagingengine.com> and subject line Re: [php-maint] Bug#855376: php7.1-readline: Unmet dependencies in jessie-backports has caused the Debian Bug report #855376, regarding

Processed: Re: Bug#855491: texlive-latex-recommended: emph macro is broken in fontspec 2.5c; please update to 2.5d

Processing commands for cont...@bugs.debian.org: > severity 855491 serious Bug #855491 [texlive-latex-recommended] texlive-latex-recommended: emph macro is broken in fontspec 2.5c; please update to 2.5d Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact

Bug#855494: mgltools-pmv: runPmv does not start

Package: mgltools-pmv Version: 1.5.7-1 Severity: grave Justification: renders package unusable Hi, I intended to reproduce #855485 but I was running into a different problem: $ runPmv Run PMV from /usr/lib/python2.7/dist-packages/Pmv Traceback (most recent call last): File