Bug#910900: emacs-goodies-el: Upgrade to latest emacs-goodies-el fails in postinst: tsort complains about loops
Dima Kogan writes: > Sven Joachim writes: > >> Almost surely >> /usr/share/emacs-snapshot/site-lisp/emacs-goodies-el/all.el is a >> dangling symlink to /usr/share/emacs/site-lisp/emacs-goodies-el/all.el, >> but I don't know why it has been left over. The prerm script of >> emacs-goodies-el should have called >> /usr/lib/emacsen-common/packages/remove/emacs-goodies-el which removes >> the whole /usr/share/emacs-snapshot/site-lisp/emacs-goodies-el >> directory. > > Yep! The broken symlinks in that directory were indeed the problem. > Thanks! I still get tsort complaints, but those are apparently not > fatal. Does any of that make sense? Yes, the tsort complaints are an (apparently harmless?) generic problem with emacsen-common. I guess the real question is why the symlinks are dangling. d
Bug#911066: python-black-doc: broken symlink: /usr/share/doc/python-black-doc/html/_static/underscore.js -> ../../../../javascript/jquery/underscore.js
Package: python-black-doc Version: 18.9b0-1-3 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m31.3s ERROR: FAIL: Broken symlinks: /usr/share/doc/python-black-doc/html/_static/underscore.js -> ../../../../javascript/jquery/underscore.js (python-black-doc) ^^ That should be .../underscore/underscore.js ^^ cheers, Andreas python-black-doc_18.9b0-1-3.log.gz Description: application/gzip
Bug#911065: nouveau: On boot MMIO read error
Package: xserver-xorg-video-nouveau Version: 1:1.0.15-3 Severity: important File: nouveau Tags: a11y Dear Maintainer, On boot in dmesg I found this errors. Sometimes when launching certains application (e.g. libreoffice) X Server crashes. Boot dmesg: [2.221446] nouveau: detected PR support, will not use DSM [2.221498] nouveau :01:00.0: enabling device (0406 -> 0407) [2.221884] nouveau :01:00.0: NVIDIA GM108 (1180d0a2) [2.285456] nouveau :01:00.0: bios: version 82.08.73.00.20 [2.394227] nouveau :01:00.0: fb: 2048 MiB GDDR5 [2.394315] nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ IBUS ] [2.411625] nouveau :01:00.0: bus: MMIO read of FAULT at 10ac08 [ IBUS ] [3.690460] nouveau :01:00.0: DRM: VRAM: 2048 MiB [3.690461] nouveau :01:00.0: DRM: GART: 1048576 MiB [3.690464] nouveau :01:00.0: DRM: Pointer to TMDS table invalid [3.690484] nouveau :01:00.0: DRM: DCB version 4.0 [3.691274] nouveau :01:00.0: DRM: MM: using COPY for buffer copies [3.691281] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 1 [4.914014] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ IBUS ] dmesg error on X server crash. Sometimes crashed also with matlab sw, last line is the same (nouveau :01:00.0: bus: MMIO read of FAULT at 619444) [18266.049204] kauditd_printk_skb: 19 callbacks suppressed [18266.049204] audit: type=1400 audit(1539010923.604:47): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/nicola/.cache/mesa_shader_cache/index" pid=6859 comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000 [18266.142172] audit: type=1400 audit(1539010923.696:48): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/local/share/fonts/.uuid.TMP-1K2Yod" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142247] audit: type=1400 audit(1539010923.696:49): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/fonts/cMap/.uuid.TMP-J6rugr" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142809] audit: type=1400 audit(1539010923.696:50): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/fonts/X11/util/.uuid.TMP-iXd47E" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142811] audit: type=1400 audit(1539010923.696:51): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/poppler/cMap/Adobe-CNS1/.uuid.TMP-2ifEZS" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142880] audit: type=1400 audit(1539010923.696:52): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/poppler/cMap/Adobe-GB1/.uuid.TMP-mMpeR6" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142882] audit: type=1400 audit(1539010923.696:53): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/poppler/cMap/Adobe-Japan1/.uuid.TMP-JhNOIk" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142883] audit: type=1400 audit(1539010923.696:54): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/poppler/cMap/Adobe-Japan2/.uuid.TMP-XMkpAy" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142930] audit: type=1400 audit(1539010923.696:55): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/poppler/cMap/Adobe-Korea1/.uuid.TMP-IM6ZrM" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18266.142931] audit: type=1400 audit(1539010923.696:56): apparmor="ALLOWED" operation="mknod" profile="libreoffice-soffice" name="/usr/share/fonts/opentype/ipafont-gothic/.uuid.TMP-1C3Aj0" pid=6858 comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [18268.987056] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ IBUS ] -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 20 -rw-r--r-- 1 root root 1350 Sep 10 17:52 10-quirks.conf -rw-r--r-- 1 root root 267 Sep 10 18:02 30-gpu.conf -rw-r--r-- 1 root root 584 Sep 10 17:52 40-libinput.conf -rw-r--r-- 1 root root 113 Sep 10 17:52 50-multitouch.conf -rw-r--r-- 1 root root 1608 Sep 10 17:52 70-synaptics.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version):
Bug#911064: python-vcr: SyntaxError in /usr/lib/python2.7/dist-packages/vcr/cassette_yf.py
Package: python-vcr Version: 2.0.1-1 Severity: important When upgrading to python-vcr 2.0.1, i get: E: Sub-process /usr/bin/dpkg returned an error code (1) Paramétrage de python-vcr (2.0.1-1) ... File "/usr/lib/python2.7/dist-packages/vcr/cassette_yf.py", line 7 yield from coroutine ^ SyntaxError: invalid syntax Jérémy -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-vcr depends on: ii python2.7.15-3 ii python-six1.11.0-2 ii python-wrapt 1.10.11-1 ii python-yaml 3.12-1+b2 python-vcr recommends no packages. python-vcr suggests no packages. -- no debconf information
Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))
Hi Andreas, On 10/15/2018 12:54 PM, Andreas Tille wrote: > when I tried last time we had antlr 4.5. I now tried with 4.6 but it > seems 4.7 is really needed. Any chance to get this soon? I am interested in packaging antlr 4.7 (with Cpp support, needed for #902798), I am working on it right now. Best, Andrius -- Andrius Merkys Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325 LT-10257 Vilnius, Lithuania
Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))
Hi, when I tried last time we had antlr 4.5. I now tried with 4.6 but it seems 4.7 is really needed. Any chance to get this soon? Kind regards Andreas. On Sat, Aug 04, 2018 at 11:23:42AM +0200, Andreas Tille wrote: > On Thu, Jul 19, 2018 at 09:44:30AM +0200, Emmanuel Bourg wrote: > > Hi Andreas, > > > > Le 19/07/2018 à 08:56, Andreas Tille a écrit : > > > > > [javac] > > > /build/beast2-mcmc-2.5.0+dfsg/src/beast/util/TreeParser.java:353: error: > > > cannot find symbol > > > [javac] CharStream charStream = > > > CharStreams.fromString(newick); > > > [javac] ^ > > > [javac] symbol: variable CharStreams > > > [javac] location: class TreeParser > > > [javac] > > > /build/beast2-mcmc-2.5.0+dfsg/src/beast/util/treeparser/NewickLexer.java:98: > > > error: method does not override or implement a method from a supertype > > > [javac] @Override > > > [javac] ^ > > > > It looks like these errors are related to ANTLR [1]. > > You'll need the version 4.7. > > Upstream confirmed this[2] - and suggests to use antlr 4.7. > So my question is: Can we expect this version of antlr in Debian > in the foreseeable future? > > Kind regards > > Andreas. > > > [1] https://github.com/CompEvol/beast2/commit/deacdc96 > [2] https://github.com/CompEvol/beast2/issues/797 > > -- > http://fam-tille.de -- http://fam-tille.de
Bug#910446: NMU diff (substantive patches in git-format-patch form)
Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in
git-format-patch form)"):
> It's not that much trouble for me but rather sad that people spent time
> on (in this case) just tedious work while they could fix other stuff
> in the same time since the maintainer is already on it.
Ah. Well, then, thanks for your consideration.
I hope you are able to use most of what I did. I expect if you rebase
my series onto your master with a conflict strategy of just taking
master's version, you'll have most of it done.
As an aside, I looked for a way to *extend* rather than *specify* the
flake8 ignore list. I found that it is possible to fish the existing
list out of the relevant python module, but I didn't know how to write
such a programmatic thing in setup.cfg.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#911063: sawfish: file-error "Resource temporarily unavailable"
Package: sawfish Version: 1:1.11.90-1.1 Severity: normal Dear Maintainer, When I tried to bring up the configure window by clicking the middle mouse button, no window showed up. Then I tried sawfish-config at the command line, and got the following error message: *** Remote sawfish error: (file-error "Resource temporarily unavailable" "/usr/lib/x86_64-linux-gnu/sawfish/DOC") I guess there is a bug? Thanks in advance for your help! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=zh_CN.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 sawfish depends on: ii libatk1.0-0 2.30.0-1 ii libc62.27-6 ii libcairo21.15.12-1 ii libfontconfig1 2.13.1-1 ii libfreetype6 2.8.1-2 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6 ii libglib2.0-0 2.58.1-2 ii libgmp10 2:6.1.2+dfsg-3 ii libgtk2.0-0 2.24.32-3 ii libice6 2:1.0.9-2 ii libpango-1.0-0 1.42.4-3 ii libpangocairo-1.0-0 1.42.4-3 ii libpangoft2-1.0-01.42.4-3 ii libpangoxft-1.0-01.42.4-3 ii librep16 0.92.5-3+b4 ii libsm6 2:1.2.2-1+b3 ii libx11-6 2:1.6.6-1 ii libxext6 2:1.3.3-1+b2 ii libxft2 2.3.2-2 ii libxinerama1 2:1.1.4-1 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxtst6 2:1.2.3-1 ii rep 0.92.5-3+b4 ii rep-gtk 1:0.90.8.2-3 ii sawfish-data 1:1.11.90-1.1 ii xterm [x-terminal-emulator] 337-1 sawfish recommends no packages. Versions of packages sawfish suggests: pn gnome-control-center pn menu pn yelp -- Configuration Files: /etc/X11/sawfish/site-init.d/00debian.jl changed: ; load the sawfish defaults (require 'sawfish-defaults) ; load gnome support ;(require 'gnome) /etc/X11/sawfish/site-init.d/00menu.jl changed: ; load the debian menu ;(require 'debian-menu) ; install it ;(setq apps-menu debian-menu) -- no debconf information
Bug#911062: dpkg-dev-el: update metadata comments to help melpa
Package: dpkg-dev-el Version: 37.4 Severity: wishlist Tags: newcomer Jonas Bernoulli asks for a license statement and commentary section in dpkg-dev-el.el. This is apparently needed by the melpa machinery, -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dpkg-dev-el depends on: ii elpa-dpkg-dev-el 37.4 dpkg-dev-el recommends no packages. dpkg-dev-el suggests no packages. -- no debconf information
Bug#910846: No packages.
On 2018-10-14 6:53 a.m., Gong S. wrote: > There is no "xserver-xorg-video-radeon-dbgsym" or > "xserver-xorg-core-dbgsym" in the repo. They're in a separate repository: deb https://deb.debian.org/debian-debug/-debug main contrib non-free Replace with the name of the suite you're using in your main repository entry. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer signature.asc Description: OpenPGP digital signature
Bug#908553: pcb-rnd: Fail to launch
Hi, Sorry for the delay, I didn't receive any notification from the bug tracker and completely forgot to manually check. It is a locate thing as Dima points out. Setting LANG=C makes pcb-rnd run without problems. El mar., 11 sept. 2018 a las 1:18, Fabian Inostroza () escribió: > > Package: pcb-rnd > Version: 2.0.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > > Trying to launch pcb-rnd I get the following output on the terminal: > > Error in lihata node /usr/share/pcb-rnd/pcb-conf.lht:119.0:Invalid numeric > value: 2.2 > Error in lihata node /usr/share/pcb-rnd/pcb-conf.lht:119.0:Invalid numeric > value: 2.2 > Error in lihata node /usr/share/pcb-rnd/pcb-conf.lht:119.0:Invalid numeric > value: 2.2 > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:39.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:40.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:38.0: Invalid coord > value: '25.0mil' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:39.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:40.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:38.0: Invalid coord > value: '25.0mil' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:39.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:40.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:38.0: Invalid coord > value: '25.0mil' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:39.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:40.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:38.0: Invalid coord > value: '25.0mil' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:39.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:40.0: Invalid coord > value: '0.0' > io_lihata parse error at /usr/share/pcb-rnd/default4.lht:38.0: Invalid coord > value: '25.0mil' > Can't create an empty layout, exiting > > > -- System Information: > Debian Release: buster/sid > APT prefers testing-debug > APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8), > LANGUAGE=es_CL.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages pcb-rnd depends on: > ii libatk1.0-0 2.28.1-1 > ii libc6 2.27-6 > ii libcairo2 1.15.12-1 > ii libfontconfig1 2.13.0-5 > ii libfreetype62.8.1-2 > ii libgd3 2.2.5-4 > ii libgdk-pixbuf2.0-0 2.36.12-2 > ii libgl1 1.1.0-1 > ii libglib2.0-02.56.1-2 > ii libglu1-mesa [libglu1] 9.0.0-2.1 > ii libgtk2.0-0 2.24.32-3 > ii libgtkglext11.2.0-9 > ii libice6 2:1.0.9-2 > ii libpango-1.0-0 1.42.4-1 > ii libpangocairo-1.0-0 1.42.4-1 > ii libpangoft2-1.0-0 1.42.4-1 > ii libpangox-1.0-0 0.0.2-5+b2 > ii libsm6 2:1.2.2-1+b3 > ii libstroke0 0.5.1-9 > ii libx11-62:1.6.6-1 > ii libxinerama12:1.1.4-1 > ii libxm4 2.3.8-2 > ii libxml2 2.9.4+dfsg1-7+b1 > ii libxmu6 2:1.1.2-2 > ii libxrender1 1:0.9.10-1 > ii libxt6 1:1.1.5-1 > > pcb-rnd recommends no packages. > > Versions of packages pcb-rnd suggests: > pn geda-gnetlist > > -- no debconf information
Bug#910581: confirmed
I cab confirm this bug. Exact same situation here. I could also fix it by downgrading libkf5kontactinterface5 to 17.12.3-1. -- Johan Spee "Eve Ryth in Gisgon na Beal Right"
Bug#911054: workrave: desktop instability in multimonitor (3) setup
I don't have other desktop problems, ie with other programs drivers being used: ii libdrm-nouveau2:amd64 2.4.74- 1amd64Userspace interface to nouveau-specific kernel DRM services -- runtime ii xserver-xorg-video-nouveau1:1.0.13- 3 amd64X.Org X server -- Nouveau display driver hth, Wim Van: Francois Marier Verzonden: maandag 15 oktober 2018 09:31 Aan: Wim Bertels; 911...@bugs.debian.org Onderwerp: Re: Bug#911054: workrave: desktop instability in multimonitor (3) setup On 2018-10-15 at 09:03:54, wim wrote: > in about 80% of the cases, whenever workrave tries to "intervene" with a > break or other notice, > the desktop flickers and needs reloading, > sometimes the desktop needs to be restarted > > this could be related to #503684 ? I just closed that old bug. It's been working fine for me for many years. I would be surprised if workrave was able to cause that much trouble to your X session. Perhaps Xorg drivers are the problem? Francois -- https://fmarier.org/
Bug#906305: [debian-mysql] Bug#906305: galera-3: FTBFS on hurd-i386
Hello! Thanks for the report and patch. Can you please report this upstream and get their opinion on this? Or even make a pull request on https://github.com/codership/galera/issues ? This package follows upstream very carefully and we don't have any Debian-only patches around at the moment. If upstream thinks this is correct, it would most likely be included in next upstream release.
Bug#881034: Galera-3 default configuration; nodes beyond primary will not connect
Hello! I can see in the logs: 2017-11-06 17:10:13 139930521723456 [Warning] WSREP: access file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory) This issue might ultimately be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874025 or upstream https://github.com/codership/galera/issues/313 I don't think this is related to the Debian packaging in any way. You hypothesis of issues with systemd script are not supported by any evidence. You workaround does not sound like something that would be recommended to do, and I don't understand why killing the original process even can help, interesting. I suggest you seek support from the upstream mailing list or buy support from Codership, the company behind Galera.
Bug#906081: Fwd: [debian-mysql] Bug#906081: galera-3: FTBFS on non-linux systems
Hello! Teemu's reply never got recorded to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906081, so forwarding this now. Since upstream is positive, please make a PR directly on upstream at https://github.com/codership/galera/? This package follows upstream very carefully and we don't have any Debian-only patches around at the moment. If upstream thinks this is correct, it would most likely be included in next upstream release. ti 14. elok. 2018 klo 12.09 teemu.olla...@galeracluster.com kirjoitti: > > > Hi Otto, > > The patch looks safe for me. It does not change any logic, just deals > with differences in ifreq struct member naming between different > OS/kernel implementations. > > - Teemu > > On 2018-08-14 11:49, Otto Kekäläinen wrote: > > Hello! > > > > Patch received in Debian. What do you think about it? > > > > -- Forwarded message - > > From: Svante Signell > > Date: ti 14. elok. 2018 klo 1.15 > > Subject: [debian-mysql] Bug#906081: galera-3: FTBFS on non-linux > > systems > > > > > > Source: galera-3 > > Version: > > Severity: important > > Tags: ftbfs, patch > > User: debian-h...@lists.debian.org, debian-k...@lists.debian.org > > Usertags: hurd-i386, kfreebsd-any > > > > Hello, > > > > Currently galera-3 FTBFS on GNU/Hurd and GNU/kFreeBSD-any due to > > ambiguities on members of struct ifreq. Attached is a patch to fix > > this. This patch is enough to make galera-3 build properly on kfreebsd- > > anny, while some tests still have to be modified since GNU/Hurd lacks > > implementations of: posix_fadvise, msync and pthread_setschedparam.
Bug#856237: [debian-mysql] Bug#856237: galera-3 testcase failure due to monotonic clock
Hello! Thanks for the report and patch. Can you please report this upstream and get their opinion on this? Or even make a pull request on https://github.com/codership/galera/issues ? This package follows upstream very carefully and we don't have any Debian-only patches around at the moment. If upstream thinks this is correct, it would most likely be included in next upstream release.
Bug#874025: [debian-mysql] Bug#874025: garbd does not start
Forwarded: https://github.com/codership/galera/issues/313 Hello! This looks like a duplicate of upstream bug https://github.com/codership/galera/issues/313 This is not something we should fix on packaging level in Debian. Please contribute upstream to get this fixed once and for all.
Bug#889033: #889033 smartmontools: New upstream version (6.6) is available
Hi Dmitry, On Mon, Oct 15, 2018 at 06:30:06PM +1100, Dmitry Smirnov wrote: Would you trust me to prepare a new upstream release of the "smartmontools"? Help is always welcome, although in this case it's basically almost done. I started and SZ Lin (林上智) has finished it, I just need to review: https://salsa.debian.org/jmtd/smartmontools/merge_requests/1 I'll take a look at that MR this morning, and if it's not immediately ready for upload I'll ping this bug. -- Jonathan Dowland
Bug#911061: ukui-control-center depends on nonexisting package gnome-control-center-faces
Package: ukui-control-center Version: 1.1.6-1 Severity: serious The following packages have unmet dependencies: ukui-control-center : Depends: gnome-control-center-faces but it is not installable
Bug#911056: chromium,webext-browserpass: impossible to install chromium and webext-browserpass together
On 2018-10-15 10:12 +0200, Jonas Smedegaard wrote: > Package: chromium,webext-browserpass > Severity: serious > Justification: 7 > > With chromium 70.0.3538.54-1 and webext-browserpass 2.0.11+dfsg-2 installed, > attempting to upgrade to chromium 70.0.3538.54-2 fails: > > Gør klar til at udpakke .../chromium_70.0.3538.54-2_amd64.deb ... > Udpakker chromium (70.0.3538.54-2) over (70.0.3538.54-1) ... > dpkg: advarsel: chromium: konfigurationsfil '/etc/chromium' er hverken en > almindelig fil eller symbolsk lænke (= '/etc/chromium') > dpkg: fejl under behandling af arkivet > /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack): > forsøger at overskrive kataloget '/etc/chromium' i pakken webext-browserpass > 2.0.11+dfsg-2 med ikke-katalog > dpkg-deb: fejl: indsæt subprocess was killed by signal (Kanalen blev brudt) > dpkg: overvejer at afkonfigurere chromium, som ville være i konflikt med > installation af chromium-common ... > dpkg: ja, vil afkonfigurere chromium (ødelagt af chromium-common) > Gør klar til at udpakke .../chromium-common_70.0.3538.54-2_amd64.deb ... > Afkonfigurerer chromium (70.0.3538.54-1) ... > Udpakker chromium-common (70.0.3538.54-2) over (70.0.3538.54-1) ... > Der opstod fejl under behandlingen: > /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > Sætter chromium-common (70.0.3538.54-2) op ... > dpkg: afhængighedsproblemer forhindrer konfiguration af chromium: > chromium afhænger af chromium-common (= 70.0.3538.54-1); men: > Version af chromium-common på systemet er 70.0.3538.54-2. > chromium-common (70.0.3538.54-2) ødelægger chromium (<< 70.0.3538.54-2) og > er installeret. > Versionen af chromium, der skal sætte op, er 70.0.3538.54-1. > > Above is in danish, but I guess the essence is noticable for english speakers: > /etc/chromium is somehow "owned" by both packages, > which causes trouble (now that chromium adds a conffile, I guess). Actually the problem is that chromium 70.0.3538.54-2 introduces /etc/chromium as a conffile while webext-browserpass (and other packages) ship it as a directory. , | $ apt-file search etc/chromium/ | chrome-gnome-shell: /etc/chromium/native-messaging-hosts/org.gnome.chrome_gnome_shell.json | debian-edu-config: /etc/chromium/policies/managed/chromium-networked-prefs | plasma-browser-integration: /etc/chromium/native-messaging-hosts/org.kde.plasma.browser_integration.json | webext-browserpass: /etc/chromium/native-messaging-hosts/com.dannyvankooten.browserpass.json ` Cheers, Sven
Bug#911025: Transition to postgresql-11
Re: Jeremy Bicha 2018-10-15 > How soon do you need this issue fixed? I'm ok with glom being removed > from Testing if that helps. At the moment the biggest blocker is that llvm-toolchain-7 is not in testing (OOM when stripping on mips(el)), so it's not urgent anyway. But that could change anytime. Can I help with the transition? Christoph
Bug#911060: Fwd: the homepage https://tablelayout.dev.java.net/ is no longer available
Package: libtablelayout-java Version: 20090826-4 Severity: minor The homepage given https://tablelayout.dev.java.net/ is no longer available. I did get https://www.oracle.com/technetwork/java/tablelayout-141489.html but dunno if that is the right place. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (100, 'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#911059: reportbug: Behaviour on lowercase and UPPERCASE package names is inconsistent
Package: reportbug Version: 7.1.7+deb9u2 Severity: normal Control: found -1 reportbug/7.5.0 reportbug does rather not work consistently when using UPPERCASE package names, e.g.: # reportbug -p WNPP Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: us-ascii Please change your locale if this is incorrect. Using 'Daniel Lange ' as your from address. Getting status for WNPP... W: Unable to locate package WNPP No matching source or binary packages. A package named "WNPP" does not appear to be installed; do you want to search for a similar-looking filename in an installed package [Y|n|q|?]? [..] vs. the intended behaviour on lowercase "wnpp". # reportbug -p wnpp Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: us-ascii Please change your locale if this is incorrect. Using 'Daniel Lange ' as your from address. Will send report to Debian (per lsb_release). What sort of request is this? (If none of these things mean anything to you, or you are trying to report a bug in an existing package, please press Enter to exit reportbug.) 1 ITP This is an `Intent To Package'. Please submit a package description along with copyright and URL in such a report. 2 OThe package has been `Orphaned'. It needs a new maintainer as soon as possible. 3 RFA This is a `Request for Adoption'. Due to lack of time, resources, interest or something similar, the current maintainer is asking for someone else to maintain this package. They will maintain it in the meantime, but perhaps not in the best possible way. In short: the package needs a new maintainer. 4 RFH This is a `Request For Help'. The current maintainer wants to continue to maintain this package, but they need some help to do this because their time is limited or the package is quite big and needs several maintainers. 5 RFP This is a `Request For Package'. You have found an interesting piece of software and would like someone else to maintain it for Debian. Please submit a package description along with copyright and URL in such a report. Choose the request type: [..] Now the Pseudo-package name is WNPP, not wnpp. Similar problem: # reportbug -p Reportbug # notice the uppercase R Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Daniel Lange ' as your from address. Getting status for Reportbug... Checking for newer versions at madison... Will send report to Debian (per lsb_release). Querying Debian BTS for reports on Reportbug (source)... 216 bug reports found: Bugs with severity important 1) #709862 reportbug: GTK interface crashes on continue from package selection 2) #711404 reportbug's GTK interface crashes if spelling dictionaries for the current locale are missing 3) #717563 reportbug: web access thru proxy not available 4) #848208 GUI segfaults when trying to collect system information [RESOLVED] 5) #849124 Reportbug 7.1.1 doesnt start (ValueError: Namespace Vte not available + another error) [RESOLVED] 6) #850733 Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)" [RESOLVED] [..] vs. # reportbug -p reportbug # notice the lowercase r Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Daniel Lange ' as your from address. Getting status for reportbug... Checking for newer versions at madison... Your version (7.1.7+deb9u2) of reportbug appears to be out of date. The following newer release(s) are available in the Debian archive: testing: 7.5.0 unstable: 7.5.0 Do you still want to file a report [y|N|q|?]? [..] Reportbug should do the right thing, regardless of case. So probably lowercasing package names given before processing.
Bug#911058: RM: amcheck -- ROM; not needed with postgresql-11
Package: ftp.debian.org Severity: normal Hi, amcheck is a backport to PostgreSQL 10 of the contrib module with the same name in postgresql-11. Now that PG11 is in unstable, amcheck should be removed. Christoph
Bug#911057: iwd: Switch to using packaged ell instead of bundled version
Package: iwd Severity: wishlist Apparently ell (ITP #895584) is now available in the archive: https://tracker.debian.org/pkg/ell At some point iwd should switch from using its bundled ell to building with against the packaged version. I asked upstream who said that ell will not provide any ABI guarantees until 1.0, thus it seems less than perfect for iwd to use it at this point (atleast without a extremely strict build- and runtime-dependency). There is currently no support in iwd to even build against a system ell instead of the bundled version. The build system magic should be implemented to make this a configure switch (unless it's at some point determined shipping the bundled version isn't needed at all and the build system could just be changed to only support building against a system version of ell ofcourse). (It also seems ell releases atleast currently are driven to be made for the sole benefit of being used in iwd, and since packaging of new ell releases are lagging behind a bit that means using them would have a negative impact of being able to provide newer iwd versions in Debian.) Filing this mostly for the record and as a reminder at this point, so it can be reconsidered at some future point. (Hopefully we'll see ell 1.0 at some point, but I have no idea how far away that is.) Regards, Andreas Henriksson
Bug#911056: chromium,webext-browserpass: impossible to install chromium and webext-browserpass together
Package: chromium,webext-browserpass Severity: serious Justification: 7 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 With chromium 70.0.3538.54-1 and webext-browserpass 2.0.11+dfsg-2 installed, attempting to upgrade to chromium 70.0.3538.54-2 fails: Gør klar til at udpakke .../chromium_70.0.3538.54-2_amd64.deb ... Udpakker chromium (70.0.3538.54-2) over (70.0.3538.54-1) ... dpkg: advarsel: chromium: konfigurationsfil '/etc/chromium' er hverken en almindelig fil eller symbolsk lænke (= '/etc/chromium') dpkg: fejl under behandling af arkivet /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack): forsøger at overskrive kataloget '/etc/chromium' i pakken webext-browserpass 2.0.11+dfsg-2 med ikke-katalog dpkg-deb: fejl: indsæt subprocess was killed by signal (Kanalen blev brudt) dpkg: overvejer at afkonfigurere chromium, som ville være i konflikt med installation af chromium-common ... dpkg: ja, vil afkonfigurere chromium (ødelagt af chromium-common) Gør klar til at udpakke .../chromium-common_70.0.3538.54-2_amd64.deb ... Afkonfigurerer chromium (70.0.3538.54-1) ... Udpakker chromium-common (70.0.3538.54-2) over (70.0.3538.54-1) ... Der opstod fejl under behandlingen: /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Sætter chromium-common (70.0.3538.54-2) op ... dpkg: afhængighedsproblemer forhindrer konfiguration af chromium: chromium afhænger af chromium-common (= 70.0.3538.54-1); men: Version af chromium-common på systemet er 70.0.3538.54-2. chromium-common (70.0.3538.54-2) ødelægger chromium (<< 70.0.3538.54-2) og er installeret. Versionen af chromium, der skal sætte op, er 70.0.3538.54-1. Above is in danish, but I guess the essence is noticable for english speakers: /etc/chromium is somehow "owned" by both packages, which causes trouble (now that chromium adds a conffile, I guess). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlvES+gACgkQLHwxRsGg ASFPSg//dJyfUQDj6noxTQtxCNNR8dCW1YOw4OTRUUnGRsxfMdxnbV5+XRCJMmxI VExT3IHQq+FZ2AVP5DYisI/w1cfhQJjSYuuCikURkgZMruony/Rz96vTNP/sHx0E iswlJcWElPGokMNLk6DQr5Jkwn1bMVM1V0WDdW4P+8PkTPfQx3q4s9c9nvw8mbgn Er4y+yIHxQdT+rpz6eP4sb2aymsKV2dnLqzBzIRVQBGkuuEtPhCixCqe4lm7bcYL 1uvDDMkCIfOiYK4UR8mqya/ns1A5z8EtPTT7b2wE8WaI9RuHBGxnktpBO4bBNgN9 PaZ0qtt2jVwgXgNTmZp2SpDCTvDzhfw2SiOMp2OV8MGI5di9cV9VDSSmpj7PxVlR Qh+PL8Wj/vBSbwBULe40xXqXVGo2DznLXMA5WCH1CH3BScW4QloxcU2jhKMemK2f K/hPpvPa9dMBLKvcpHyud15feckqWmFIahlkc1xbYxmYwDP//whoKnn5YiOMoeKk I/czfAQ6+xSQV4W0kFf0TzA814ME1w7J6xmGtee/qFQ6/TuORWmxivDtmXqvaaLi nxAbeLiNE9Rv/hDWg/oL7TEymYEEleLz3raLPfArA/kFFT7pKAMZjhi7gj7KMrOh YavYvJk/j+uhfSWFBgEiQXTMQRJYijZDq8HxasFVuvC8EK6/k5c= =MA/A -END PGP SIGNATURE-
Bug#838522: dahdi-linux: Please announce supported hardware using AppStream
On 21/09/16 23:43, Petter Reinholdtsen wrote:
> Package: dahdi-linux
> Version: 2.11.1-1
> Severity: wishlist
> User: p...@hungry.com
> Usertags: appstream-modalias
>
> Hi.
>
> The dahdi-linux package is one of the packages in the Debian archive
> that should be proposed for installation when a given hardware dongle is
> inserted or available. Thanks to the appstream system, this can now be
> announced in a way other tools can use and act on. I've written the
> isenkram system to ask the current user if hardware specific packages
> should be installed when a new dongle is installed or already present on
> a machine, and isenkram now uses appstream as one source for hardware to
> package mappings.
>
> You can read more about this on my blog,
> http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
> >.
>
> Instructions on how to create the metadata XML file can be found in
> https://wiki.debian.org/AppStream/Guidelines >.
>
> It would be great if you could add an appstream metainfo file to the
> dahdi-linux package, with content similar to this:
>
>
>
>[...]
>
> pci:ve159d0001sv*
> lkmodule:dahdi
>
>
>
> If there are other hardware ids also supported by the package, please
> add those too. :)
DAHDI supports mostly PCI devices. There is a single type of USB
devices: the Xorcom Astribanks. The relevant PCI IDs are e4e4:11[3456]2
, although 1132 and 1142 are probably not around anymore, and 1152
should also be quite rate.
As for PCI devices (assuming you want them too):
Looking at /usr/share/misc/pci.ids , I see also:
Basically all of Digium's cards (vendor ID d161) are supported.
e159:0001 is an ISDN modem card. its chip was used by Digium for its
first cards. Thus it should not be used without the sub (vendor/product)
IDs. e159:0001 8086:0003 is the one of the old X100P/X101P or one of its
many clones (a modem reprogrammed as a Zaptel card). It does not show on
the pci.ids list but the wctdm driver (old fxs/fxo card. Not sold
anymore for a long time) uses a bunch of vendor sub-IDs under e159:0001.
static DEFINE_PCI_DEVICE_TABLE(wctdm_pci_tbl) = {
{ 0xe159, 0x0001, 0xa159, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xe159, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xb100, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xb1d9, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xb118, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xb119, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xa9fd, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xa8fd, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xa800, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xa801, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xa908, PCI_ANY_ID, 0, 0, (unsigned long)
},
{ 0xe159, 0x0001, 0xa901, PCI_ANY_ID, 0, 0, (unsigned long)
},
under the vendor ID 10b5 (PLX Technology, Inc) there is 10b5:0557 10b5
9030, the tor2 card, and then near-by a bunch of Atcom (and other)
clones, most of which I believe we don't support. Another one is (the
original tor2 card) 10b5:d00d 10b5:9030 and a bunch of near-by (and
unsupported) clones (that did not notice 'd00d' was supposed to spell
'dude').
-- Tzafrir
Bug#911018: 7.1 also
dpkg: warning: while removing php7.1-cli, directory '/etc/php/7.1/cli/conf.d' not empty so not removed dpkg: warning: while removing libapache2-mod-php7.1, directory '/etc/php/7.1/apache2/conf.d' not empty so not removed $ find /etc/php/7.1 /etc/php/7.1 /etc/php/7.1/mods-available /etc/php/7.1/mods-available/shmop.ini /etc/php/7.1/mods-available/dom.ini /etc/php/7.1/mods-available/gettext.ini... /etc/php/7.1/apache2 /etc/php/7.1/apache2/conf.d /etc/php/7.1/apache2/conf.d/10-pdo.ini /etc/php/7.1/apache2/conf.d/20-gettext.ini /etc/php/7.1/apache2/conf.d/20-mysqli.ini /etc/php/7.1/apache2/conf.d/10-mysqlnd.ini /etc/php/7.1/apache2/conf.d/20-sysvsem.ini... /etc/php/7.1/cli /etc/php/7.1/cli/conf.d /etc/php/7.1/cli/conf.d/10-pdo.ini /etc/php/7.1/cli/conf.d/20-gettext.ini /etc/php/7.1/cli/conf.d/20-mysqli.ini /etc/php/7.1/cli/conf.d/10-mysqlnd.ini /etc/php/7.1/cli/conf.d/20-sysvsem.ini /etc/php/7.1/cli/conf.d/20-xsl.ini...
Bug#911055: homepage of libjava3d-java is no longer valid
Package: libjava3d-java Version: 1.5.2+dfsg-15 Severity: minor Dear Maintainer, The homepage shared http://java3d.java.net redirects to http://www.oracle.com/splash/java.net/maintenance/index.html which says the projects have moved elsewhere. Please share the new link for the homepage. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (100, 'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libjava3d-java depends on: ii libjava3d-jni1.5.2+dfsg-15 ii libvecmath-java 1.5.2-7 libjava3d-java recommends no packages. Versions of packages libjava3d-java suggests: pn libjava3d-java-doc -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#910446: NMU diff (substantive patches in git-format-patch form)
Hi,
On Sun, Oct 14, 2018 at 10:55:10PM +0100, Ian Jackson wrote:
> Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in
> git-format-patch form)"):
> > On Sun, Oct 14, 2018 at 03:36:49PM +0100, Ian Jackson wrote:
> > > Hi. I fixed this bug, and some other FTBFS, and am about to upload
> > > the result. I'm doing this myself, right away, because this is an RC
> > > bug which has triggered the autoremover to want to remove dgit.
> > >
> > > Following the recommendation in dev ref 5.11.1, I have not use
> > > DELAYED; and because I doubt that actually uploading it now will cause
> > > you any difficulty. I hope that's OK.
> > >
> > > The patches I made are attached. You can also find this as a git
> > > branch, here:
> ...>
> > That's actually not what I prefer since I
>
> Sorry about that. But,
>
> I did look in the bug [1] before starting work, this lunchtime UK
> time, and there was no response there.
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910446
>
> I have just checked the bug again, and your message to it crossed with
> my decision to go ahead with the upload. The timestamp on the
> relevant .changes file shows that I did my formal build-for-upload at
> 14:28 UTC. I and evidently spent a few minutes getting my NMU diff
> email into shape and I sent that email at 14:36 and did the actual
> dgit push at 14:37.
>
> Your message to the bug was at 14:31 UTC. I confess didn't check the
> bug again in the 9 minutes between `dgit sbuild' and `dgit push'.
>
> To be honest, if you had said any time in the past week, in the bug,
> that you were intending to fix it I would have been quite happy to
> leave the work to you. But there was nothing from you in the bug and
> the upstream git server (which I was able to see via http, even if the
> git interface was giving me trouble) showed no recent activiy.
To be honest I saw that bug but forgot about it until I saw the
autoremoval mail. I then notified the BTS so reverse dependencies don't
need to worry.
> > - there's plenty of time until the autoremoval hits us
>
> I'm generally quite busy and I had time and headspace to do this
> technical work now. I wasn't confident that that would occur again in
> the next few weeks.
>
> I'm sorry to be told that I have engaged in "sub par interaction". I
> was trying to help. Can you explain to me what concrete problem my
> action has caused you ?
It's not that much trouble for me but rather sad that people spent time
on (in this case) just tedious work while they could fix other stuff
in the same time since the maintainer is already on it.
> I appreciate that being the recipient, several times a year, of
> autoremoval notifications (not just from gbp) is a hazard of sitting
> on top of a large dependency stack. But it would be nice to be able
> to at least fix these things oneself without being criticised.
>
> It would be really helpful if people would respond to RC bugs *before*
> their entire reverse dependency stack has received an `autoremoval'
> email.
Yept, that's totally true but I think the reverse holds as well: if
things are flagged check with the maintainer(s) how this happened
(in this case it was just an oversight). They might either be working on
a fix or might be happy about an NMU.
> I guess I can be criticised for not emailing the bug before starting
> work. Looking at my irc transcript it looks like I started at 12:00
> UTC or so. Of course once one has started on something like this it
> is very discouraging to be told to stop and throw one's work away -
> and I guess your message to the bug was prompted by the autoremoval
> mail which had been sent ovrnight, so an additional mail from me would
> have waited anyway. So probably in this case if I had emailed the bug
> at 12:00ish UTC it would have made no difference.
That's why I at least check with maintainers before starting work on
things. Even then it doesn't always help to avoid duplicated work (since
some times there's more than two parties involved) but most of the time
it does.
I should have used better words in my previous mail. Sorry if this came
over rougher than it meat to be.
Cheers,
-- Guido
Bug#911054: workrave: desktop instability in multimonitor (3) setup
On 2018-10-15 at 09:03:54, wim wrote: > in about 80% of the cases, whenever workrave tries to "intervene" with a > break or other notice, > the desktop flickers and needs reloading, > sometimes the desktop needs to be restarted > > this could be related to #503684 ? I just closed that old bug. It's been working fine for me for many years. I would be surprised if workrave was able to cause that much trouble to your X session. Perhaps Xorg drivers are the problem? Francois -- https://fmarier.org/
Bug#889033: #889033 smartmontools: New upstream version (6.6) is available
Hi Jonathan, Would you trust me to prepare a new upstream release of the "smartmontools"? -- Cheers, Dmitry Smirnov. --- Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#891096: planet-venus: python-beautifulsoup is replaced with python-bs4
Quoting Paul Wise (2018-10-15 05:49:46) > On Tue, 02 Oct 2018 00:57:59 +0200 Jonas Smedegaard wrote: > > > planet-venus only reference BeautifulSoup in a vendor dir which is fully > > patched out and therefore irrelevant. > > In that case the Recommends should be removed, reopening. Oh, indeed. Silly me! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#909110: serious
Control: notfixed -1 7.3.0~rc2-2 Control: fixed -1 7.3.0~rc3-1 No, I am sorry, you are right, it was correctly fixed in 7.3.0~rc2-3, and it’s also included in 7.3.0~rc3-1 that I just uploaded. Ondrej -- Ondřej Surý ond...@sury.org > On 15 Oct 2018, at 08:55, Kunal Mehta wrote: > > Hi, > > On 10/14/18 11:45 PM, Ondřej Surý wrote: >> Version: 7.3.0~rc2-2 >> >> This had been already fixed in version in both unstable and testing. > > That's not what I see... > > $ php -v > PHP 7.3.0RC2 (cli) (built: Oct 14 2018 10:21:01) ( NTS ) > Copyright (c) 1997-2018 The PHP Group > Zend Engine v3.3.0-dev, Copyright (c) 1998-2018 Zend Technologies >with Zend OPcache v7.3.0RC2, Copyright (c) 1999-2018, by Zend > Technologies > $ dpkg -l | grep php7.3-dev > ii php7.3-dev 7.3.0~rc2-2+b1 > amd64Files for PHP7.3 module development > > $ phpize7.3 > Configuring for: > PHP Api Version: 20180731 > Zend Module Api No: 20180731 > Zend Extension Api No: 320180731 > cp: cannot stat 'run-tests*.phpL': No such file or directory > > Looking at the file directly, I can see the L: > $ grep "\"L" /usr/bin/phpize7.3 > FILES="acinclude.m4 Makefile.global config.sub config.guess ltmain.sh > run-tests*.php"L > > > Am I missing something? > > -- Kunal >
Bug#911054: workrave: desktop instability in multimonitor (3) setup
Package: workrave Version: 1.10.16-1 Severity: normal Hallo, in about 80% of the cases, whenever workrave tries to "intervene" with a break or other notice, the desktop flickers and needs reloading, sometimes the desktop needs to be restarted this could be related to #503684 ? hth, Wim -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages workrave depends on: ii libatk1.0-0 2.22.0-1 ii libatkmm-1.6-1v5 2.24.2-2 ii libc6 2.24-11+deb9u3 ii libcairo-gobject2 1.14.8-1 ii libcairo2 1.14.8-1 ii libcairomm-1.0-1v51.12.0-1+b1 ii libdbusmenu-glib4 12.10.2-2 ii libdbusmenu-gtk3-412.10.2-2 ii libfontconfig12.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgdk-pixbuf2.0-02.36.5-2+deb9u2 ii libgdome2-0 0.8.1+debian-6 ii libglib2.0-0 2.50.3-2 ii libglibmm-2.4-1v5 2.50.0-1 ii libgstreamer1.0-0 1.10.4-1 ii libgtk-3-03.22.11-1 ii libgtk2.0-0 2.24.31-2 ii libgtkmm-3.0-1v5 3.22.0-1 ii libice6 2:1.0.9-2 ii libindicator3-7 0.5.0-3+b1 ii libmate-panel-applet-4-1 1.16.2-1 ii libpanel-applet0 3.20.1-1+b2 ii libpango-1.0-01.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libpangomm-1.4-1v52.40.1-3 ii libpulse-mainloop-glib0 10.0-1+deb9u1 ii libpulse0 10.0-1+deb9u1 ii libsigc++-2.0-0v5 2.10.0-1 ii libsm62:1.2.2-1+b3 ii libstdc++66.3.0-18+deb9u1 ii libx11-6 2:1.6.4-3 ii libxfce4util7 4.12.1-3 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.3-1 ii workrave-data 1.10.16-1 ii xfce4-panel 4.12.1-2 workrave recommends no packages. Versions of packages workrave suggests: pn gnome-panel ii gnome-shell 3.22.3-3 -- no debconf information
Bug#911053: vitetris: vitetirs is not available by used "vitetris command"
Package: vitetris Version: 0.57.2-1 Severity: normal Hi lyknode, Could you please change weather to call vitetris from cli. vitetris is vitetris, so why we must call "tetris". And tetris is under TradeMark no ? I don't think dfsg soit aggree with that. Cheers -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/8 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 vitetris depends on: ii libc6 2.27-6 vitetris recommends no packages. vitetris suggests no packages. -- no debconf information
Bug#909110: serious
Hi, On 10/14/18 11:45 PM, Ondřej Surý wrote: > Version: 7.3.0~rc2-2 > > This had been already fixed in version in both unstable and testing. That's not what I see... $ php -v PHP 7.3.0RC2 (cli) (built: Oct 14 2018 10:21:01) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.0-dev, Copyright (c) 1998-2018 Zend Technologies with Zend OPcache v7.3.0RC2, Copyright (c) 1999-2018, by Zend Technologies $ dpkg -l | grep php7.3-dev ii php7.3-dev 7.3.0~rc2-2+b1 amd64Files for PHP7.3 module development $ phpize7.3 Configuring for: PHP Api Version: 20180731 Zend Module Api No: 20180731 Zend Extension Api No: 320180731 cp: cannot stat 'run-tests*.phpL': No such file or directory Looking at the file directly, I can see the L: $ grep "\"L" /usr/bin/phpize7.3 FILES="acinclude.m4 Makefile.global config.sub config.guess ltmain.sh run-tests*.php"L Am I missing something? -- Kunal
Bug#894260: Fwd: Bug#910913 closed by Bart Martens (closing RFS: ghostwriter/1.7.3-1 [ITP])
Okay Ghost, thanks again for everything you did. Best regards Le 15 oct. 2018 04:15, "ghost" a écrit : So it's now pending in the NEW queue and you can mark "needs sponsor = no" on mentors.d.n. Cheers. Forwarded Message Subject: Bug#910913 closed by Bart Martens (closing RFS: ghostwriter/1.7.3-1 [ITP]) Date: Mon, 14 Oct 2018 22:21:05 UTC From: Debian Bug Tracking System Reply-To: 910...@bugs.debian.org To: ghost This is an automatic notification regarding your Bug report which was filed against the sponsorship-requests package: #910913: RFS: ghostwriter/1.7.3-1 [ITP] It has been closed by Bart Martens . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Bart Martens < ba...@quantz.debian.org> by replying to this email. -- 910913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Package ghostwriter version 1.7.3-1 is in NEW now, and the package at mentors is not newer (2018-10-14) than the package in NEW (2018-10-14), so there is currently no package to sponsor. https://ftp-master.debian.org/new/ghostwriter_1.7.3-1.html https://mentors.debian.net/package/ghostwriter Please remove the package from mentors or mark it "needs sponsor = no". If for some reason you need to replace the package in NEW, then you can upload an updated package to mentors and feel free to reopen this RFS 910913 or open a new RFS.
Bug#911052: libkscreenlocker5: Missing psmisc dependency trigger 'killall: not found' in postinst
Package: libkscreenlocker5 Version: 4:5.13.5-1 Severity: important The piuparts testing in https://piuparts.debian.org/stretch2buster/pass/plasma-workspace_4:5.13.5-1.log > report the following problem: /var/lib/dpkg/info/libkscreenlocker5:amd64.postinst: 12: /var/lib/dpkg/info/libkscreenlocker5:amd64.postinst: killall: not found The fix is probably to depend on psmisc, which contain the 'killall' program. Setting the severity to important, as this causes the postinst to not behave as expected for any user without the psmisc package installed. -- Happy hacking Petter Reinholdtsen
Bug#911043: rng-tools does not perform as expected ...
Here is the workaround. I don't know what the fix is. I was never able to get systemd to enable the service (or subsequently start the service). Nothing I attempted would get the service out of the "generated" status. $ cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. if [ -e /usr/sbin/rngd ]; then /usr/sbin/rngd -r /dev/hwrng -f fi exit 0
Bug#909110: serious
severity serious affects php-wikidiff2 php-luasandbox thanks With the transition to PHP 7.3, the lack of run-tests.php causes wikidiff2 and luasandbox to FTBFS since "make test" fails. -- Kunal
Bug#910900: emacs-goodies-el: Upgrade to latest emacs-goodies-el fails in postinst: tsort complains about loops
Sven Joachim writes: > Almost surely > /usr/share/emacs-snapshot/site-lisp/emacs-goodies-el/all.el is a > dangling symlink to /usr/share/emacs/site-lisp/emacs-goodies-el/all.el, > but I don't know why it has been left over. The prerm script of > emacs-goodies-el should have called > /usr/lib/emacsen-common/packages/remove/emacs-goodies-el which removes > the whole /usr/share/emacs-snapshot/site-lisp/emacs-goodies-el > directory. Yep! The broken symlinks in that directory were indeed the problem. Thanks! I still get tsort complaints, but those are apparently not fatal. Does any of that make sense?
Bug#911051: libetpan-doc: broken symlink: /usr/share/doc/libetpan17/API -> ../libetpan-doc/API
Package: libetpan-doc Version: 1.9.1-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m27.2s ERROR: FAIL: Broken symlinks: /usr/share/doc/libetpan17/API -> ../libetpan-doc/API (libetpan-doc) The target should rather be ../libetpan-dev/API This is likely caused by a behavioral change of dh_installdocs in debhelper compat level 11. cheers, Andreas libetpan-doc_1.9.1-1.log.gz Description: application/gzip
Bug#911050: aom: FTBFS - do not like 'kFreeBSD' obj format
Package: aom Version: 1.0.0-3 The package fail to build on kfreebsd-i386. This block vlc from building on kfreebsd-i386. This is the build error as reported on https://buildd.debian.org/status/fetch.php?pkg=aom=kfreebsd-i386=1.0.0-3=1539463725=0 >: -- Looking for pthread_create in pthread - found -- Found Threads: TRUE --- aom_configure: Detected CPU: x86 CMake Error at build/cmake/aom_optimization.cmake:103 (message): Unknown obj format: kFreeBSD Call Stack (most recent call first): build/cmake/aom_configure.cmake:147 (get_asm_obj_format) CMakeLists.txt:77 (include) -- Happy hacking Petter Reinholdtsen
Bug#911049: libcmark-gfm{,-extensions}-dev: missing Depends: libcmark-gfm{,-extensions}0 (= ${binary:Version})
Package: libcmark-gfm-dev,libcmark-gfm-extensions-dev Version: 0.28.3.gfm.17-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m27.1s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libcmark-gfm.so -> libcmark-gfm.so.0.28.3.gfm.17 (libcmark-gfm-dev) 0m27.7s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libcmark-gfm-extensions.so -> libcmark-gfm-extensions.so.0.28.3.gfm.17 (libcmark-gfm-extensions-dev) cheers, Andreas libcmark-gfm-dev_0.28.3.gfm.17-1.log.gz Description: application/gzip
