Bug#990513: texlive-extra-utils: make4ht unusable because make4ht-logging.lua is missing
Package: texlive-extra-utils Version: 2018.20190227-2 Severity: grave Dear Maintainer, Because of make4ht prerequisits texlive-extra-utils should depend on texlive-luatex which should contain make4ht-logging.lua but this is not the case, at least in buster and bullseye. Cf. https://github.com/michal-h21/make4ht/issues/47 for the upstream discussion. Regards JSB -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages texlive-extra-utils depends on: ii libunicode-linebreak-perl 0.0.20190101-1 ii python 2.7.16-1 ii tex-common 6.11 ii texlive-base 2018.20190227-2 ii texlive-binaries 2018.20181218.49446-1 ii texlive-latex-base 2018.20190227-2 Versions of packages texlive-extra-utils recommends: ii ghostscript9.27~dfsg-2+deb10u4 ii libfile-homedir-perl 1.004-1 ii liblog-log4perl-perl 1.49-1 ii libyaml-tiny-perl 1.73-1 ii ruby 1:2.5.1 ii texlive-latex-recommended 2018.20190227-2 Versions of packages texlive-extra-utils suggests: pn chktex pn dvidvi pn dvipng pn fragmaster pn lacheck pn latexdiff ii latexmk 1:4.61-0.1 pn purifyeps pn xindy Versions of packages tex-common depends on: ii dpkg 1.19.7 ii ucf 3.0038+nmu1 Versions of packages tex-common suggests: ii debhelper 12.1.1 Versions of packages texlive-extra-utils is related to: ii tex-common6.11 ii texlive-binaries 2018.20181218.49446-1 -- no debconf information -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#990417: openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8
I installed on an debian stable/unstable x86_64 the vm with: sudo virt-install --name debian-s390x --disk size=20 --memory=2000 -- arch=s390x --location http://ftp.debian.org/debian/dists/stretch/main/installer-s390x/ then I upgraded to stable (using stable for installation causes the new vm to freeze during install - another bug?) and installed the openjdk- 11-jre-headless. just execution the command /usr/lib/jvm/java-11-openjdk-s390x/bin/java crashes. This is how to reproduce the bug. This happens with debian stable/unstable on x86_64 as host and/or debian stable/unstable and ubuntu bionic/groovy as guest. Am Dienstag, dem 29.06.2021 um 10:01 +0200 schrieb Matthias Klose: > Control: reassign -1 src:qemu > > works for me on a native machine. You should also provide a test > case. > > > On 6/28/21 7:28 PM, Arne Plöse wrote: > > Package: openjdk-11-jre-headless > > Version: 11.0.11+9-1~deb10u1 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > I tried tu run java in an qemu emulated s390 debian VM. > > The bug accects also unstabel and te openjdk versions 15, 16 and > > 17, but not version 1.8 > > > > The outcome is a hs_err_pid632.log. > > # > > # A fatal error has been detected by the Java Runtime Environment: > > # > > # SIGILL (0x4) at pc=0x03ff88c7e6f4, pid=587, tid=588 > > # > > # JRE version: (11.0.11+9) (build ) > > # Java VM: OpenJDK 64-Bit Server VM (11.0.11+9-post-Debian- > > 1deb10u1, mixed mode, sharing, tiered, compressed oops, g1 gc, > > linux-s390x) > > # Problematic frame: > > # C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 > > # > > # No core dump will be written. Core dumps have been disabled. To > > enable core dumping, try "ulimit -c unlimited" before starting Java > > again > > # > > # > > > > --- S U M M A R Y > > > > Command Line: > > > > Host: 2964, 2 cores, 1G, Debian GNU/Linux 10 (buster) > > Time: Mon Jun 28 19:13:29 2021 CEST elapsed time: 0.099756 seconds > > (0d 0h 0m 0s) > > > > --- T H R E A D --- > > > > Current thread is native thread > > > > Stack: [0x03ff8748,0x03ff8758], > > sp=0x03ff8757e940, free space=1018k > > Native frames: (J=compiled Java code, A=aot compiled Java code, > > j=interpreted, Vv=VM code, C=native code) > > C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 > > > > > > siginfo: si_signo: 4 (SIGILL), si_code: 5 (ILL_PRVOPC), si_addr: > > 0x03ff88c7e6f4 > > > > > > > > -- System Information: > > Debian Release: 10.10 > > APT prefers stable-updates > > APT policy: (500, 'stable-updates'), (500, 'stable') > > Architecture: s390x > > > > Kernel: Linux 4.19.0-17-s390x (SMP w/2 CPU cores) > > Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C > > (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages openjdk-11-jre-headless depends on: > > ii ca-certificates-java 20190405 > > ii java-common 0.71 > > ii libasound2 1.1.8-1 > > ii libc6 2.28-10 > > ii libcups2 2.2.10-6+deb10u4 > > ii libfontconfig1 2.13.1-2 > > ii libfreetype6 2.9.1-3+deb10u2 > > ii libgcc1 1:8.3.0-6 > > ii libharfbuzz0b 2.3.1-1 > > ii libjpeg62-turbo 1:1.5.2-2+deb10u1 > > ii liblcms2-2 2.9-3 > > ii libnss3 2:3.42.1-1+deb10u3 > > ii libpcsclite1 1.8.24-1 > > ii libstdc++6 8.3.0-6 > > ii util-linux 2.33.1-0.1 > > ii zlib1g 1:1.2.11.dfsg-1 > > > > openjdk-11-jre-headless recommends no packages. > > > > Versions of packages openjdk-11-jre-headless suggests: > > pn fonts-dejavu-extra > > pn fonts-indic > > pn fonts-ipafont-gothic > > pn fonts-ipafont-mincho > > pn fonts-wqy-microhei | fonts-wqy-zenhei > > pn libnss-mdns > > > > -- no debconf information > > >
Processed: Re: Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Processing control commands: > retitle -1 python3-expeyes: superfluous Conflicts: modemmanager causes > problems on buster->bullseye upgrades Bug #990489 [python3-expeyes] python3-expeyes: why is there a Conflicts: modemmanager ? Changed Bug title to 'python3-expeyes: superfluous Conflicts: modemmanager causes problems on buster->bullseye upgrades' from 'python3-expeyes: why is there a Conflicts: modemmanager ?'. -- 990489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Control: retitle -1 python3-expeyes: superfluous Conflicts: modemmanager causes problems on buster->bullseye upgrades On 30/06/2021 18.55, Georges Khaznadar wrote: I attach the file eyes_udev.sh, which is called upon eyes17's post-installation, as "eyes_udev.sh enable", thus creating or keeping the file /lib/udev/rules.d/99-phoenix.rules, with this content: Great, the fix seems to be already included in the package. So maybe it's sufficient to just drop all the Conflicts on modemmanager to fix this bug ;-) In all the maintainer scripts, please use invoke-rc.d udev instead of service udev s.t. this gets properly filtered via policy-rc.d (an RC bug on its own, not filing it separately because we already have this one) Lintian says this: E: maintainer-script-calls-service N: N: The maintainer script apparently runs the service command. This N: command is reserved for local administrators and must never be used by N: a Debian package. N: N: Please replace with calls to update-rc.d(8) and invoke-rc.d(8). If N: your package installs this service, this can be automated using N: dh_installinit(1) or dh_installsystemd(1). N: N: Refer to Debian Policy Manual section 9.3.3 (Interfacing with init N: systems) for details. Andreas
Processed: Re: Bug#989236: crossgrader: crashes with "Could not mark python3-apt:amd64 for install, fixing manually."
Processing control commands: > severity -1 serious Bug #989236 [crossgrader] crossgrader: crashes with "Could not mark python3-apt:amd64 for install, fixing manually." Severity set to 'serious' from 'important' -- 989236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990493: marked as done (node-babel-plugin-add-module-exports broken with babel-preset-env 7)
Your message dated Wed, 30 Jun 2021 18:33:36 + with message-id and subject line Bug#990493: fixed in node-babel-plugin-add-module-exports 1.0.4+dfsg1~cs5.8.0-1 has caused the Debian Bug report #990493, regarding node-babel-plugin-add-module-exports broken with babel-preset-env 7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 990493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-babel-plugin-add-module-exports Version: 0.2.1-3 Severity: grave Justification: creates broken build output Control: forwarded -1 https://github.com/59naga/babel-plugin-add-module-exports/issues/73 Control: block 990458 by -1 Upstream has released a fix in major update. Since we are in freeze I'm not sure how to proceed here. This affects many packages. $ reverse-depends -b node-babel-plugin-add-module-exports Reverse-Build-Depends * autosize.js * node-babel-plugin-lodash * node-colormin * node-css-loader * node-deep-for-each * node-es6-promise * node-handlebars * node-i18next-http-backend --- End Message --- --- Begin Message --- Source: node-babel-plugin-add-module-exports Source-Version: 1.0.4+dfsg1~cs5.8.0-1 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of node-babel-plugin-add-module-exports, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-babel-plugin-add-module-exports package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Jun 2021 23:21:58 +0530 Source: node-babel-plugin-add-module-exports Architecture: source Version: 1.0.4+dfsg1~cs5.8.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 990493 Changes: node-babel-plugin-add-module-exports (1.0.4+dfsg1~cs5.8.0-1) experimental; urgency=medium . [ Debian Janitor ] * Trim trailing whitespace. * Use secure copyright file specification URI. * Use secure URI in debian/watch. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Apply multi-arch hints. + node-babel-plugin-add-module-exports: Add Multi-Arch: foreign. . [ Pirate Praveen ] * Switch to lijunle's fork for babel 7 fixes * New upstream version 1.0.4 (Closes: #990493) * Use dh-sequence-nodejs auto install * Build using babeljs command * Use babel 7 modules to build * Add lintian override for false positive test data * Run upstream tests using mocha * Add babel-preset-power-assert as component * New upstream version 1.0.4+~cs2.0.0 * Add babel-plugin-empower-assert and babel-plugin-espower as components * New upstream version 1.0.4+~cs5.8.0 * Disable tests (needs core-js 2) * Update copyright for embedded components * Bump Standards-Version to 4.5.1 (no changes needed) * Exclude tests from component * New upstream version 1.0.4+dfsg+~cs5.8.0 Checksums-Sha1: 69248fcc3f8ba9b24659444aadac62c46166fe8e 3790 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0-1.dsc db944b3d7691b0795a4744161acaf71a380dfb70 4312 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0.orig-babel-plugin-empower-assert.tar.xz cfbc5113d650a60062e9eb31d2c18b638ecff682 10972 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0.orig-babel-plugin-espower.tar.xz 51195068da2fcc266841fad390e8f4ab7d396e38 2464 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0.orig-babel-preset-power-assert.tar.xz be908623de596de679077071743c4a4e6cec7681 40652 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0.orig.tar.xz fd567a8a6af2cae58ec0e46c132d79e1f28aa3d3 3504 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0-1.debian.tar.xz 88445905b697640553e8aeeb5e4824cf94fca3f3 13082 node-babel-plugin-add-module-exports_1.0.4+dfsg1~cs5.8.0-1_amd64.buildinfo Checksums-Sha256:
Bug#990458: marked as done (autosize build is broken (throws error is diaspora web console))
Your message dated Wed, 30 Jun 2021 18:33:25 +
with message-id
and subject line Bug#990458: fixed in autosize.js 4.0.2~dfsg1-6
has caused the Debian Bug report #990458,
regarding autosize build is broken (throws error is diaspora web console)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
990458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-autosize
Severity: grave
Version: 4.0.2~dfsg1-5
Control: affects -1 ruby-rails-assets-autosize,diaspora
I think during transition to babel7 something broke.
This causes diaspora ui to break,
Uncaught ReferenceError: module is not defined
at
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
at $.fn.charCount
(main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3)
at
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
This leads to,
(t((t={exports:{}}).exports),e.autosize=t.exports)}("undefined"!=typeof
globalThis?globalThis:"undefined"!=typeof
self?self:this,function(e){"use strict";function n(a){function e(){var
e=window.getComputedStyle(a,null);"vertical"===e.resize?a.style.resize="none":"both"===e.resize&&(a.style.resize="horizontal"),r="content-box"===e.boxSizing?-(parseFloat(e.paddingTop)+parseFloat(e.paddingBottom)):parseFloat(e.borderTopWidth)+parseFloat(e.borderBottomWidth),isNaN(r)&&(r=0),i()}function
o(e){var
t=a.style.width;a.style.width="0px",a.offsetWidth,a.style.width=t,a.style.overflowY=e}function
n(e){for(var t=[];e&& instanceof
Element;)e.parentNode.scrollTop&({node:e.parentNode,scrollTop:e.parentNode.scrollTop}),e=e.parentNode;return
t}function s(){var
e,t;0!==a.scrollHeight&&(e=n(a),t=document.documentElement&,a.style.height="",a.style.height=a.scrollHeight+r+"px",l=a.clientWidth,e.forEach(function(e){e.node.scrollTop=e.scrollTop}),t&&(document.documentElement.scrollTop=t))}function
i(){s();var
e=Math.round(parseFloat(a.style.height)),t=window.getComputedStyle(a,null),n="content-box"===t.boxSizing?Math.round(parseFloat(t.height)):a.offsetHeight;if(nr,l,c,u,d;a&&&"TEXTAREA"===a.nodeName&&!p.has(a)&&(c=l=r=null,u=function
u(){a.clientWidth!==l&()},d=function(t){window.removeEventListener("resize",u,!1),a.removeEventListener("input",i,!1),a.removeEventListener("keyup",i,!1),a.removeEventListener("autosize:destroy",d,!1),a.removeEventListener("autosize:update",i,!1),Object.keys(t).forEach(function(e){a.style[e]=t[e]}),p["delete"](a)}.bind(a,{height:a.style.height,resize:a.style.resize,overflowY:a.style.overflowY,overflowX:a.style.overflowX,wordWrap:a.style.wordWrap}),a.addEventListener("autosize:destroy",d,!1),"onpropertychange"in
a&&"oninput"in
a&("keyup",i,!1),window.addEventListener("resize",u,!1),a.addEventListener("input",i,!1),a.addEventListener("autosize:update",i,!1),a.style.overflowX="hidden",a.style.wordWrap="break-word",p.set(a,{destroy:d,update:i}),e())}function
t(e){e=p.get(e);e&()}function
i(e){e=p.get(e);e&()}e["default"]=void 0;var
a,o,p="function"==typeof Map?new Map:(a=[],o=[],{has:function
r(e){return-1o[a.indexOf(e)]},set:function
c(e,t){-1===a.indexOf(e)&&(a.push(e),o.push(t))},"delete":function
u(e){e=a.indexOf(e);-1m(e){return new Event(e,{bubbles:!0})};try{new
Event("test")}catch(d){m=function m(e){var
t=document.createEvent("Event");return t.initEvent(e,!0,!1),t}}var
s=null;"undefined"==typeof window||"function"!=typeof
window.getComputedStyle?((s=function s(e){return
e}).destroy=function(e){return e},s.update=function(e){return
e}):((s=function s(e,t){return
e&(e.length?e:[e],function(e){return
n(e,t)}),e}).destroy=function(e){return
e&(e.length?e:[e],t),e},s.update=function(e){return
e&(e.length?e:[e],i),e}),e["default"]=s,module.exports=exports["default"]}),$.fn.charCount=function(i)
--- End Message ---
--- Begin Message ---
Source: autosize.js
Source-Version: 4.0.2~dfsg1-6
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
autosize.js, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated autosize.js package)
(This message was generated automatically at their request; if you
believe that there is a problem
Bug#990458: [Pkg-javascript-devel] Bug#990458: Bug#990458: Bug#990458: Attaching the files from buster vs bullseye
On Wed, Jun 30, 2021 at 9:44 pm, Pirate Praveen wrote: On Wed, Jun 30, 2021 at 9:38 pm, Pirate Praveen wrote: Looks like we are already using the dist tarballs and does not involve any build, we can just take the latest 1.0.4 from npmjs.com. Scratch that, the new versions use babel to build, so I think using https://github.com/lijunle/babel-plugin-add-module-exports/ is the best option, though the latest version tagged is 1.0.2 and latest npm release is 1.0.4 (basically completely messed up release workflow). With babel-plugin-add-module-exports 1.0.4 from the above repo, $ diff -u autosize-current.js autosize.js --- autosize-current.js 2021-06-30 22:30:00.391798535 +0530 +++ autosize.js 2020-12-14 17:42:45.0 +0530 @@ -284,5 +284,5 @@ var _default = autosize; _exports["default"] = _default; - module.exports = exports["default"]; + module.exports = exports.default; }); \ No newline at end of file and this is working with diaspora. Thanks again for tracking down the issue.
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
On 30/06/2021 18.22, jithin bp wrote:
One suggestion that needs to be rigorously tested is to blacklist the
serial device of ExpEYES(VendorID:ProductID) for Modem Manager so that it
will ignore it.
https://askubuntu.com/questions/1231894/modemmanager-conflicts-with-arduino
That sounds very promising.
Corresponding ModemManager documentation is
https://www.freedesktop.org/software/ModemManager/api/latest/ref-overview-modem-filter.html
So maybe the solution is shipping in eyes17 (or a better fitting package?)
/lib/udev/rules.d/78-mm-blacklist-expeyes.rules with this content:
= 8< =
ACTION!="add|change|move", GOTO="mm_blacklist_expeyes_end"
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="00df", ENV{ID_MM_DEVICE_IGNORE}="1"
LABEL="mm_blacklist_expeyes_end"
= >8 =
(Repeat the middle line if you have multiple IDs)
Needs to be tested by someone having an expeyes board ;-)
As modemmanager already has several blacklists:
/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules
/lib/udev/rules.d/77-mm-qdl-device-blacklist.rules
/lib/udev/rules.d/77-mm-usb-device-blacklist.rules
perhaps your device should rather be added there?
Some blacklists also set the ID_MM_TTY_BLACKLIST variable instead
of ID_MM_DEVICE_IGNORE
Andreas
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Sorry, here is the forgotten attachment, on e-mail later as usual. eyes_udev.sh Description: Bourne shell script signature.asc Description: PGP signature
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Dear Jithin,
thank you for your very fast response.
I attach the file eyes_udev.sh, which is called upon eyes17's
post-installation, as "eyes_udev.sh enable", thus creating or keeping
the file /lib/udev/rules.d/99-phoenix.rules, with this content:
---8<- /lib/udev/rules.d/99-phoenix.rules --
# udev rules for expEYES interface: AVR, FT232, MCP2200 and CH340
SUBSYSTEM=="usb",ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="21ff", MODE="666"
SUBSYSTEM=="tty",ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="666"
SUBSYSTEM=="tty",ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="00df", MODE="666"
SUBSYSTEM=="tty",ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", MODE="666"
ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="21ff", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="00df", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ENV{ID_MM_DEVICE_IGNORE}="1"
# interest_eyes17
---8<-
Please can you check whether ATTRS{idVendor}=="03eb", ... "0403",
"04d8", ... "1a86" will be enough to blacklist our boxes' interfaces for
modemmanager, and eventually the interface of eyes17?
Then, please can you check that installing modemmanager will let Eyes17
boxes in peace, when such a rule is activated for udev?
Currently, my Eyes17 box is lended to a colleague who is trying the
complete list of experiments of the User Manual, while reviewing the
Spanish version, and might want to buy such boxes, for his technical
school. I can ask him to give it back, and he would do it shortly, but
he asked me two days ago whether I could lend the box some longer; I
did not know that I would get a bug report today :)
Best regards, Georges.
jithin bp a écrit :
> Dear Georges,
>
> The modem-manager probes serial ports with random AT commands causing
> communication errors in a wide range of devices which use the serial port,
> most common ones being embedded development tools such as for the Arduino ,
> PIC etc.
> This issue has been reported in many forums
> -
> https://mail.gnome.org/archives/networkmanager-list/2013-October/msg00038.html
> -
> https://askubuntu.com/questions/1231894/modemmanager-conflicts-with-arduino
> - https://github.com/ubuntu/ubuntu-make/issues/4
>
> In case of ExpEYES, random communication errors, and subsequent data loss
> occurs during data acquisition tasks if Modem Manager is running in the
> background. Perhaps there is some way to place a lock on the active serial
> port to prevent MM from probing it.
>
> One suggestion that needs to be rigorously tested is to blacklist the
> serial device of ExpEYES(VendorID:ProductID) for Modem Manager so that it
> will ignore it.
> https://askubuntu.com/questions/1231894/modemmanager-conflicts-with-arduino
>
> The user community is currently in the range of a few thousands, and is
> expected to grow, so a solution must be quickly resolved after studying
> which serial devices Modem-Manager automatically likes to probe, and to
> keep ExpEYES ( ID 04d8:00df Microchip Technology, Inc.) out of that list.
>
>
> More about ExpEYES
> - https://expeyes.in/
> - https://csparkresearch.in/expeyes17/
> - https://csparkresearch.in/expeyes17/blog
>
> Regards,
> Jithin
>
> On Wed, Jun 30, 2021 at 9:36 PM Georges Khaznadar
> wrote:
>
> > Dear Andreas,
> >
> > I added in Cc: the authors of Expeyes hardware and software.
> >
> > Hello Jithin, Ajith! the context about the bug report with serious
> > severity is below.
> >
> >
> >
> > I ignored that a statement like "Conflicts: modemmanager" would create
> > problems with buster->bullseye upgrades. Currently, binary packages
> > conflicting with modemmanager are: eyes17, python3-expeyes,
> > firm-phoenix-ware. The first one, eyes17, will be the most used.
> >
> > This statement was added because boxes of the Expeyes family do not
> > communicate correctly by their serial link when modemmanager is
> > installed. I did not investigate further, to know the precise reason of
> > the incompatibility.
> >
> > I got e-mails of some users of previous versions of expeyes packages,
> > who could not activate their boxes, and my reply was to uninstall
> > modemmanager or upgrade to the new version of eyes17 package.
> >
> > The number of Expeyes users is currently growing in Kerala (a southern
> > state of India), and they rely on *eyes17* package, some with a Debian
> > machine, most with an Ubuntu machine. This community is growing since
> > Eyes17 box has become an officially encouraged scientific device, to be
> > distributed to all high schools in the state, together with training.
> >
> > I cannot withdraw the confict statement without damaging this user
> > community in the future.
> >
> > Hence the next question:
> >
> >
> > How would it be possible to keep
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
On 30/06/2021 18.06, Georges Khaznadar wrote: I ignored that a statement like "Conflicts: modemmanager" would create problems with buster->bullseye upgrades. Currently, binary packages conflicting with modemmanager are: eyes17, python3-expeyes, firm-phoenix-ware. The first one, eyes17, will be the most used. So the current buster->bullseye upgrade outcome is not what you would desire: * eyes17 removed * modemmanager still installed * python3-expexes kept at the buster version This statement was added because boxes of the Expeyes family do not communicate correctly by their serial link when modemmanager is installed. I did not investigate further, to know the precise reason of the incompatibility. Is this incompatibility still the case with current modemmanager (1.14) in buster? The number of Expeyes users is currently growing in Kerala (a southern state of India), and they rely on *eyes17* package, some with a Debian machine, most with an Ubuntu machine. This community is growing since Eyes17 box has become an officially encouraged scientific device, to be distributed to all high schools in the state, together with training. That's a nice piece of hardware you have there ;-) However I know better the profile of users who use eyes17: they are students and teachers, wo interact inside a high school. Then, the link with Internet is generally provided by some router or some wireless box, and no modem is used. I haven't looked into modemmanager at all ... is it possible to "disable" it from the eyes17 side? Deactivating the service might be sufficient? Dropping a conffile somewhere to block it from using certain devices? Diverting the binary away? Andreas
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Dear Georges, The modem-manager probes serial ports with random AT commands causing communication errors in a wide range of devices which use the serial port, most common ones being embedded development tools such as for the Arduino , PIC etc. This issue has been reported in many forums - https://mail.gnome.org/archives/networkmanager-list/2013-October/msg00038.html - https://askubuntu.com/questions/1231894/modemmanager-conflicts-with-arduino - https://github.com/ubuntu/ubuntu-make/issues/4 In case of ExpEYES, random communication errors, and subsequent data loss occurs during data acquisition tasks if Modem Manager is running in the background. Perhaps there is some way to place a lock on the active serial port to prevent MM from probing it. One suggestion that needs to be rigorously tested is to blacklist the serial device of ExpEYES(VendorID:ProductID) for Modem Manager so that it will ignore it. https://askubuntu.com/questions/1231894/modemmanager-conflicts-with-arduino The user community is currently in the range of a few thousands, and is expected to grow, so a solution must be quickly resolved after studying which serial devices Modem-Manager automatically likes to probe, and to keep ExpEYES ( ID 04d8:00df Microchip Technology, Inc.) out of that list. More about ExpEYES - https://expeyes.in/ - https://csparkresearch.in/expeyes17/ - https://csparkresearch.in/expeyes17/blog Regards, Jithin On Wed, Jun 30, 2021 at 9:36 PM Georges Khaznadar wrote: > Dear Andreas, > > I added in Cc: the authors of Expeyes hardware and software. > > Hello Jithin, Ajith! the context about the bug report with serious > severity is below. > > > > I ignored that a statement like "Conflicts: modemmanager" would create > problems with buster->bullseye upgrades. Currently, binary packages > conflicting with modemmanager are: eyes17, python3-expeyes, > firm-phoenix-ware. The first one, eyes17, will be the most used. > > This statement was added because boxes of the Expeyes family do not > communicate correctly by their serial link when modemmanager is > installed. I did not investigate further, to know the precise reason of > the incompatibility. > > I got e-mails of some users of previous versions of expeyes packages, > who could not activate their boxes, and my reply was to uninstall > modemmanager or upgrade to the new version of eyes17 package. > > The number of Expeyes users is currently growing in Kerala (a southern > state of India), and they rely on *eyes17* package, some with a Debian > machine, most with an Ubuntu machine. This community is growing since > Eyes17 box has become an officially encouraged scientific device, to be > distributed to all high schools in the state, together with training. > > I cannot withdraw the confict statement without damaging this user > community in the future. > > Hence the next question: > > > How would it be possible to keep expeyes packages in the soon-to-come > Debian/Stable distribution? > > The package modemmanager is recommended by widely used packages, like > network-manager, while eyes17 is recommended by no package. > > I do not know how many users do really need modemmanager, or use modems. > > However I know better the profile of users who use eyes17: they are > students and teachers, wo interact inside a high school. Then, the link > with Internet is generally provided by some router or some wireless box, > and no modem is used. > > @Jitin, @Ajith: > can you give please an estimate of the user community for eyes17 now, > and in a near future? > > Best regards, Georges. > > Andreas Beckmann a écrit : > > Package: python3-expeyes > > Version: 4.8.7+repack-4 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > Control: affects -1 + eyes17 > > > > Hi Georges, > > > > while investigating incomplete buster->bullseye upgrades, I came across > > the Conflicts: modemmanager in python3-expeyes. Why was that added? > > It is not mentioned in the changelog and the git commit introducing it > > doesn't explain it either. > > Should this have been a versioned Breaks instead? > > > > The modemmanager package still exists in bullseye, so what should be the > > desired buster->bullseye upgrade outcome for buster systems with both > > modemmanager and python3-expeyes installed (that happens e.g. when > > installing eyes17/buster with --install-recommends)? > > > > > > Andreas > > -- > Georges KHAZNADAR et Jocelyne FOURNIER > 22 rue des mouettes, 59240 Dunkerque France. > Téléphone +33 (0)3 28 29 17 70 > > -- jithin
Bug#990458: [Pkg-javascript-devel] Bug#990458: Bug#990458: Attaching the files from buster vs bullseye
On Wed, Jun 30, 2021 at 9:38 pm, Pirate Praveen wrote: Looks like we are already using the dist tarballs and does not involve any build, we can just take the latest 1.0.4 from npmjs.com. Scratch that, the new versions use babel to build, so I think using https://github.com/lijunle/babel-plugin-add-module-exports/ is the best option, though the latest version tagged is 1.0.2 and latest npm release is 1.0.4 (basically completely messed up release workflow).
Bug#990458: [Pkg-javascript-devel] Bug#990458: Attaching the files from buster vs bullseye
On Wed, Jun 30, 2021 at 9:30 pm, Pirate Praveen wrote: On Wed, Jun 30, 2021 at 8:27 pm, Akshay S Dinesh wrote: Either, update this plugin in Debian to the fork that's pushed only to npm (or switch to https://github.com/lijunle/babel-plugin-add-module-exports/ I guess) I think we can take the last tagged version 1.0.0 and apply a patch to make it 1.0.2. Looks like we are already using the dist tarballs and does not involve any build, we can just take the latest 1.0.4 from npmjs.com.
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Dear Andreas, I added in Cc: the authors of Expeyes hardware and software. Hello Jithin, Ajith! the context about the bug report with serious severity is below. I ignored that a statement like "Conflicts: modemmanager" would create problems with buster->bullseye upgrades. Currently, binary packages conflicting with modemmanager are: eyes17, python3-expeyes, firm-phoenix-ware. The first one, eyes17, will be the most used. This statement was added because boxes of the Expeyes family do not communicate correctly by their serial link when modemmanager is installed. I did not investigate further, to know the precise reason of the incompatibility. I got e-mails of some users of previous versions of expeyes packages, who could not activate their boxes, and my reply was to uninstall modemmanager or upgrade to the new version of eyes17 package. The number of Expeyes users is currently growing in Kerala (a southern state of India), and they rely on *eyes17* package, some with a Debian machine, most with an Ubuntu machine. This community is growing since Eyes17 box has become an officially encouraged scientific device, to be distributed to all high schools in the state, together with training. I cannot withdraw the confict statement without damaging this user community in the future. Hence the next question: How would it be possible to keep expeyes packages in the soon-to-come Debian/Stable distribution? The package modemmanager is recommended by widely used packages, like network-manager, while eyes17 is recommended by no package. I do not know how many users do really need modemmanager, or use modems. However I know better the profile of users who use eyes17: they are students and teachers, wo interact inside a high school. Then, the link with Internet is generally provided by some router or some wireless box, and no modem is used. @Jitin, @Ajith: can you give please an estimate of the user community for eyes17 now, and in a near future? Best regards, Georges. Andreas Beckmann a écrit : > Package: python3-expeyes > Version: 4.8.7+repack-4 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + eyes17 > > Hi Georges, > > while investigating incomplete buster->bullseye upgrades, I came across > the Conflicts: modemmanager in python3-expeyes. Why was that added? > It is not mentioned in the changelog and the git commit introducing it > doesn't explain it either. > Should this have been a versioned Breaks instead? > > The modemmanager package still exists in bullseye, so what should be the > desired buster->bullseye upgrade outcome for buster systems with both > modemmanager and python3-expeyes installed (that happens e.g. when > installing eyes17/buster with --install-recommends)? > > > Andreas -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature
Bug#990458: Attaching the files from buster vs bullseye
On Wed, Jun 30, 2021 at 8:27 pm, Akshay S Dinesh wrote: This is most likely due to babel-plugin-add-module-exports being broken. See https://github.com/59naga/babel-plugin-add-module-exports/issues/72 and https://github.com/59naga/babel-plugin-add-module-exports/issues/80 and https://github.com/59naga/babel-plugin-add-module-exports/issues/73 That 73 points to a new version that's put only on npm and not on github. I'm not exactly sure how it works with fakeupstream at https://salsa.debian.org/js-team/node-babel-plugin-add-module-exports/-/tree/master/ Either way, the version in salsa seems to be 0.2.1 which is definitely outdated (as per the github description of babel-plugin-add-module-exports Two ways I see are: Either, update this plugin in Debian to the fork that's pushed only to npm (or switch to https://github.com/lijunle/babel-plugin-add-module-exports/ I guess) I think we can take the last tagged version 1.0.0 and apply a patch to make it 1.0.2. OR Try removing this plugin altogether and changing the "export default autosize" statement in the last line of autosize.js to "module.exports = autosize" It looks like many packages build depend on this module and those are also likely broken. I opened https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990493 to track this. I'm NOT sure whether either of these will work. Thanks for the pointers, at least we know what is broken and what the fix is. We just have to figure out the best way to include it.
Processed: bug 990493 is forwarded to https://github.com/59naga/babel-plugin-add-module-exports/issues/73
Processing commands for cont...@bugs.debian.org: > forwarded 990493 > https://github.com/59naga/babel-plugin-add-module-exports/issues/73 Bug #990493 [node-babel-plugin-add-module-exports] node-babel-plugin-add-module-exports broken with babel-preset-env 7 Set Bug forwarded-to-address to 'https://github.com/59naga/babel-plugin-add-module-exports/issues/73'. > thanks Stopping processing here. Please contact me if you need assistance. -- 990493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): node-babel-plugin-add-module-exports broken with babel-preset-env 7
Processing control commands: > forwarded -1 Unknown command or malformed arguments to command. > block 990458 by -1 Bug #990458 [libjs-autosize] autosize build is broken (throws error is diaspora web console) 990458 was not blocked by any bugs. 990458 was not blocking any bugs. Added blocking bug(s) of 990458: 990493 -- 990458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990458 990493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990493: node-babel-plugin-add-module-exports broken with babel-preset-env 7
Package: node-babel-plugin-add-module-exports Version: 0.2.1-3 Severity: grave Justification: creates broken build output Control: forwarded -1 https://github.com/59naga/babel-plugin-add-module-exports/issues/73 Control: block 990458 by -1 Upstream has released a fix in major update. Since we are in freeze I'm not sure how to proceed here. This affects many packages. $ reverse-depends -b node-babel-plugin-add-module-exports Reverse-Build-Depends * autosize.js * node-babel-plugin-lodash * node-colormin * node-css-loader * node-deep-for-each * node-es6-promise * node-handlebars * node-i18next-http-backend
Bug#973791: marked as done (qiskit-aer: FTBFS: collected 0 items / 25 errors)
Your message dated Wed, 30 Jun 2021 15:48:21 +
with message-id
and subject line Bug#973791: fixed in qiskit-aer 0.4.1-2
has caused the Debian Bug report #973791,
regarding qiskit-aer: FTBFS: collected 0 items / 25 errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
973791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qiskit-aer
Version: 0.4.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
qiskit-aer fails to build everywhere:
| pybuild --test -i python{version} -p "3.9 3.8"
| I: pybuild base:232: cd
/<>/.pybuild/cpython3_3.9_qiskit-aer/build; python3.9 -m pytest
/<>/.pybuild/cpython3_3.9_qiskit-aer/build/test/terra -k "not
TestNoiseTransformer"
| = test session starts
==
| platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
| rootdir: /<>
| collected 0 items / 25 errors
|
| ERRORS
| _ ERROR collecting
.pybuild/cpython3_3.9_qiskit-aer/build/test/terra/test_python_to_cpp.py _
| ImportError while importing test module
'/<>/.pybuild/cpython3_3.9_qiskit-aer/build/test/terra/test_python_to_cpp.py'.
| Hint: make sure your test modules/packages have valid Python names.
| Traceback:
| test/terra/test_python_to_cpp.py:16: in
| from qiskit.providers.aer.pulse.qutip_lite.qobj import Qobj
| qiskit/providers/aer/__init__.py:64: in
| from .aerprovider import AerProvider
| qiskit/providers/aer/aerprovider.py:20: in
| from .backends.qasm_simulator import QasmSimulator
| qiskit/providers/aer/backends/__init__.py:17: in
| from .qasm_simulator import QasmSimulator
| qiskit/providers/aer/backends/qasm_simulator.py:23: in
| from .controller_wrappers import qasm_controller_execute
| E ImportError: Python version mismatch: module was compiled for Python 3.8,
but the interpreter version is incompatible: 3.9.0+ (default, Oct 19 2020,
09:51:18)
| E [GCC 10.2.0].
… and many more errors. See
https://buildd.debian.org/status/fetch.php?pkg=qiskit-aer=amd64=0.4.1-1%2Bb2=1604514054=0
for the full list.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: qiskit-aer
Source-Version: 0.4.1-2
Done: Diego M. Rodriguez
We believe that the bug you reported is fixed in the latest version of
qiskit-aer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Diego M. Rodriguez (supplier of updated qiskit-aer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 17 May 2021 16:19:44 +0200
Source: qiskit-aer
Architecture: source
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Diego M. Rodriguez
Closes: 973791
Changes:
qiskit-aer (0.4.1-2) unstable; urgency=medium
.
* Use scikit-build instead of manual cmake. (Closes: #973791)
* d/control: add autopkgtest.
* d/control: bump Standards-Version.
* d/control: depend on python3-all-dev.
Checksums-Sha1:
88d671a204b0b7e12e1bb5b5557ad0f3fcc610a0 2235 qiskit-aer_0.4.1-2.dsc
71c3f7186e3efc312341a8d23f6fb09e02743b22 8572 qiskit-aer_0.4.1-2.debian.tar.xz
8e6ada2cbbab449a8dc0e253e6c1e1a8b13fd9db 8955
qiskit-aer_0.4.1-2_amd64.buildinfo
Checksums-Sha256:
fbc3d0dee7c704f015398f89cae122b5c5d686cccfbbca9d15fc83d5dbd02469 2235
qiskit-aer_0.4.1-2.dsc
718029d17413bbb59ef5b1c091ed794390fee3d9bff1f3d3a721b6f3de06fda0 8572
qiskit-aer_0.4.1-2.debian.tar.xz
a4ee2c64e3c67439e9ddceb0a34c470d052d76b9e7e5d9c8bb37e3ea6f3de7b2 8955
qiskit-aer_0.4.1-2_amd64.buildinfo
Files:
e6e3a58722e465c8a9d2d559710e383c 2235 science optional qiskit-aer_0.4.1-2.dsc
57ec2314346f3b2d2b06df894ecab49d 8572 science optional
qiskit-aer_0.4.1-2.debian.tar.xz
84e53425b37bc701d76aaf47698deb1f 8955 science optional
qiskit-aer_0.4.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
Bug#990458: Attaching the files from buster vs bullseye
This is most likely due to babel-plugin-add-module-exports being broken. See https://github.com/59naga/babel-plugin-add-module-exports/issues/72 and https://github.com/59naga/babel-plugin-add-module-exports/issues/80 and https://github.com/59naga/babel-plugin-add-module-exports/issues/73 That 73 points to a new version that's put only on npm and not on github. I'm not exactly sure how it works with fakeupstream at https://salsa.debian.org/js-team/node-babel-plugin-add-module-exports/-/tree/master/ Either way, the version in salsa seems to be 0.2.1 which is definitely outdated (as per the github description of babel-plugin-add-module-exports Two ways I see are: Either, update this plugin in Debian to the fork that's pushed only to npm (or switch to https://github.com/lijunle/babel-plugin-add-module-exports/ I guess) OR Try removing this plugin altogether and changing the "export default autosize" statement in the last line of autosize.js to "module.exports = autosize" I'm NOT sure whether either of these will work.
Bug#990489: python3-expeyes: why is there a Conflicts: modemmanager ?
Package: python3-expeyes Version: 4.8.7+repack-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + eyes17 Hi Georges, while investigating incomplete buster->bullseye upgrades, I came across the Conflicts: modemmanager in python3-expeyes. Why was that added? It is not mentioned in the changelog and the git commit introducing it doesn't explain it either. Should this have been a versioned Breaks instead? The modemmanager package still exists in bullseye, so what should be the desired buster->bullseye upgrade outcome for buster systems with both modemmanager and python3-expeyes installed (that happens e.g. when installing eyes17/buster with --install-recommends)? Andreas
Processed: python3-expeyes: why is there a Conflicts: modemmanager ?
Processing control commands: > affects -1 + eyes17 Bug #990489 [python3-expeyes] python3-expeyes: why is there a Conflicts: modemmanager ? Added indication that 990489 affects eyes17 -- 990489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990488: statsvn: Package in stable does not work
Package: statsvn Version: 0.7.0.dfsg-9 Severity: grave Justification: renders package unusable Dear Maintainer, When trying to use the statsvn utility, this fatal error message is encountered: SEVERE: Subversion binary is incorrect version. Found: 1.10.4, required: 1.3.0 This makes the utility broken on both stable and testing. It appears that FreeBSD has a patch for this, that disables the version check: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229325 -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldoldstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/2 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 statsvn depends on: ii default-jre [java-runtime] 2:1.11-71 ii java-wrappers 0.3 ii libsvnkit-java 1.8.14-3 ii openjdk-11-jre [java-runtime] 11.0.11+9-1~deb10u1 ii statcvs1:0.7.0.dfsg-7 ii subversion 1.10.4-1+deb10u2 statsvn recommends no packages. statsvn suggests no packages. -- no debconf information
Bug#990458: Attaching the files from buster vs bullseye
On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen wrote: > I can confirm libjs-autosize from buster works fine with diaspora. So workaround is to install the buster version from snapshot.debian.org http://snapshot.debian.org/archive/debian/20190209T090056Z/pool/main/a/autosize.js/libjs-autosize_4.0.2~dfsg1-3_all.deb
Bug#990458: Attaching the files from buster vs bullseye
On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen
wrote:
> I can confirm libjs-autosize from buster works fine with diaspora.
>
> Buster version has this,
>
> (function (global, factory) {
> if (typeof define === "function" && define.amd) {
> define(['module', 'exports'], factory);
>
> But bullseye version is missing definition for module,
>
> (function (global, factory) {
> if (typeof define === "function" && define.amd) {
> define(["exports"], factory);
Akshay,
Any ideas about this? Basically it is a behavior change from babel 6 to
babel 7 and we'd like to restore the babel 6 behavior.
Bug#984760: grub-pc: upgrade works, boot fails (error: symbol `grub_is_lockdown` not found)
I have something to add to this. This morning I was writing up a document on how to convert an existing Debian amd64 AWS VM to arm64 without reinstalling, which is something I was interested in doing in the future to a fairly complex system install that I wasn't excited about trying to reinstall/migrate. Everything worked with the conversion, except for the grub stage, grub failed to start on the ARM instance and was stuck at the grub-rescue prompt. When typing "insmod normal", it shows the "symbol `grub_is_lockdown` not found" error. I managed to get it working by copying grub modules from an existing Debian ARM VM over to it, I did that because I noticed that the modules were of a newer version and a different size. I'm not sure if the "grub-install" step was needed, but after investigating I found that when I ran grub-install a standard Debian-provided ARM AWS community instance and rebooted, the instance fails to boot in the same way. This is my document if you were interested, I mention the error in it: https://ryan.thoryk.com/linux/arm_convert.html -- Ryan Thoryk r...@thoryk.com r...@tliquest.net
Processed: tagging 987360
Processing commands for cont...@bugs.debian.org: > tags 987360 - pending Bug #987360 [swaylock] swaylock: Occassional unlock without password entered Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 987360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989878: marked as pending in horizon
Control: tag -1 pending Hello, Bug #989878 in horizon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/horizon/-/commit/0afb85c802d76eda139cb24422bc5649d39aff98 * Fix handling of openstack_dashboard/local/enabled in prerm of openstack-dashboard (Closes: #989878). (this message was generated automatically) -- Greetings https://bugs.debian.org/989878
Processed: Bug#989878 marked as pending in horizon
Processing control commands: > tag -1 pending Bug #989878 [openstack-dashboard] openstack-dashboard: fails to remove: rm: cannot remove '/usr/lib/python3/dist-packages/openstack_dashboard/local/enabled': Is a directory Added tag(s) pending. -- 989878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench
Hi, On Tue, 22 Jun 2021 11:23:51 +0200 Sebastian Ramacher wrote: > 1.3.4-1 would have needed to rename the package to libopenscap25 and > start a library transition. The library package also contains a bunch of > binaries and other files that do not look like the should be part of a > library package. In any case, raising the severity to serious is the > current packaging of the library is broken. Can we have a chance to put splitted packages (openscap-scanner as tools binary as other distros do and openscap-common for /usr/share files) for bullseye release? If so, I'll try to do so. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#989799: psmisc: Undeclared file conflict with manpages-de
Hello Hideki, On Wed, Jun 30, 2021 at 01:46:37PM +0900, Hideki Yamane wrote: > from buster-backports > Message-Id: <20210630134637.d8e6f92027ef11aeb9a09...@iijmio-mail.jp> > In-Reply-To: <20210627060424.GA7522@Debian-50-lenny-64-minimal> > X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) > Mime-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > On Sun, 27 Jun 2021 08:04:24 +0200 Helge Kreutzmann > wrote: > > manpages-l10n (4.10.0-1~bpo10+1) buster-backports; urgency=medium > > > > * Rebuild for buster-backports. > > * Properly conflict with future versions of psmisc and procps so that > > upgrades to bullseye will work without file conflicts. Closes: #989799 > > > > -- Helge Kreutzmann Sun, 20 Jun 2021 10:27:10 +0200 > > > > Also tracker.debian.org does not show (yet), that it has been accepted. > > Have it reached to buster-backports repo? As far as I can see, no. I'll check in depth later. 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: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 982794 +moreinfo Bug #982794 [firefox-esr] firefox-esr: illegal instruction in libxul.so on armhf Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 982794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
