Bug#964334: segfault repeatedly
Package: chromium Version: 83.0.4103.116-1~deb10u2 Followup-For: Bug #964334 Like said before, Chromium keeps crashing within a few minutes maximum. It has also becomes very very slow since the last update. Happening to me on stable with a few packages from the backports (kernel 5.4 + nvidia-driver). Thanks for maintaining this package, JB System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-0.bpo.2-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common83.0.4103.116-1~deb10u2 ii libasound2 1.1.8-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-02.30.0-2 ii libatspi2.0-0 2.30.0-7 ii libavcodec-extra58 [libavcodec58] 7:4.1.4-1~deb10u1 ii libavformat58 7:4.1.4-1~deb10u1 ii libavutil567:4.1.4-1~deb10u1 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libcups2 2.2.10-6+deb10u3 ii libdbus-1-31.12.16-1 ii libdrm22.4.97-1 ii libevent-2.1-6 2.1.8-stable-4 ii libexpat1 2.2.6-2+deb10u1 ii libflac8 1.3.2-3 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgbm118.3.6-2+deb10u1 ii libgcc11:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libharfbuzz0b 2.3.1-1 ii libicu63 63.1-6+deb10u1 ii libjpeg62-turbo1:1.5.2-2+b1 ii libjsoncpp11.7.4-3 ii liblcms2-2 2.9-3 ii libminizip11.1-8+b1 ii libnspr4 2:4.20-1 ii libnss32:3.42.1-1+deb10u2 ii libopenjp2-7 2.3.0-2+deb10u1 ii libopus0 1.3-1 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-01.42.4-8~deb10u1 ii libpng16-161.6.36-6 ii libpulse0 12.2-4+deb10u1 ii libre2-5 20190101+dfsg-2 ii libsnappy1v5 1.1.7-1 ii libstdc++6 8.3.0-6 ii libvpx51.7.0-3+deb10u1 ii libwebp6 0.6.1-2 ii libwebpdemux2 0.6.1-2 ii libwebpmux30.6.1-2 ii libx11-6 2:1.6.7-1 ii libx11-xcb12:1.6.7-1 ii libxcb-dri3-0 1.13.1-2 ii libxcb11.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor11:1.1.15-2 ii libxdamage11:1.1.4-3+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml22.9.4+dfsg1-7+b3 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxslt1.1 1.1.32-2.2~deb10u1 ii libxss11:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages chromium recommends: ii chromium-sandbox 83.0.4103.116-1~deb10u2 Versions of packages chromium suggests: pn chromium-driver ii chromium-l10n83.0.4103.116-1~deb10u2 pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+4 ii xdg-utils 1.1.3-1+deb10u1 Versions of packages chromium-common recommends: ii chromium-sandbox83.0.4103.116-1~deb10u2 ii dunst [notification-daemon] 1.3.2-1 ii fonts-liberation1:1.07.4-9 ii gnome-shell [notification-daemon] 3.30.2-11~deb10u1 ii libgl1-mesa-dri 18.3.6-2+deb10u1 ii libu2f-udev 1.1.9-1 ii mate-notification-daemon [notification-daemon] 1.20.2-1 ii notification-daemon 3.20.0-4 ii plasma-workspace [notification-daemon] 4:5.14.5.1-1 ii upower
Bug#954080: marked as done (tbsync: broken by new thunderbird, please prepare new version for stable-updates)
Your message dated Mon, 6 Jul 2020 07:14:07 +0200 with message-id <1f538569-2429-7d2c-41a0-a587d1e96...@debian.org> and subject line Close Bug #954080 has caused the Debian Bug report #954080, regarding tbsync: broken by new thunderbird, please prepare new version for stable-updates 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.) -- 954080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tbsync Version: 1.7-1 Severity: important Hi Mechthilde, it looks like the current tbsync in buster is not directly usable anymore, after thunderbird has been upgraded from 60.x to 68.x. I assume, that just using a newer version in stable might work, but I didn't try yet. First, I just downgraded thunderbird, lightning, and enigmail to their original buster versions: thunderbird 60.9.0-1~deb10u1 lightning 60.9.0-1~deb10u1 enigmail 2.0.12+ds1-1~deb10u1 This works and might be a good workaround for most users. Second, I did an adhoc, local backport of tbsync. This works with the latest thunderbird in buster, as expected. Cheers & stay healthy! --- End Message --- --- Begin Message --- Package: webext-tbsync Version: 2.11-1 Comment: Closing after upload to buster-pu too -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#964366: bashtop: insecure use of /tmp
Package: bashtop
Version: 0.9.19-1
Severity: grave
Tags: security
bashtop creates a Python script in /tmp and runs it. But Python adds the
directory containing the script to the module search path¹, and /tmp is
world-writable, so this in insecure. A local user could plant malicious
Python module in /tmp, which would be executed by bashtop.
Proof of concept:
$ install -m 644 /path/to/psutil.py /tmp
$ bashtop
___
< pwned >
---
\ ^__^
\ (oo)\___
(__)\ )\/\
||w |
|| ||
Aborted
¹ https://docs.python.org/3/using/cmdline.html#cmdarg-script
-- System Information:
Architecture: i386
Versions of packages bashtop depends on:
ii bash5.0-6
ii gawk1:5.0.1+dfsg-1
ii procps 2:3.3.16-5
Versions of packages bashtop recommends:
ii lm-sensors 1:3.6.0-2
un sysstat
ii python3-psutil 5.7.0-1
ii curl7.68.0-1
--
Jakub Wilk
import os; os.system('(tput reset && cowsay pwned) >/dev/tty; kill -ABRT %s' % os.getppid())
Bug#962221: Fixes for CVE-2020-13696 (#962221)
Hi Jeremy! Thanks for contributing the security release! I checked your changes and pushed them to the team repo. I do not have an upload rights, so CCing Sebastian and Mattia. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 signature.asc Description: PGP signature
Bug#952227: marked as done (golang-gopkg-gcfg.v1: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 gopkg.in/gcfg.v1 gopkg.in/gcfg.v1/scanner gopkg.in/gcfg.v1/token gopkg.in/gcfg.v1/ty
Your message dated Mon, 06 Jul 2020 02:33:41 +
with message-id
and subject line Bug#952227: fixed in golang-gopkg-gcfg.v1 1.2.3-2
has caused the Debian Bug report #952227,
regarding golang-gopkg-gcfg.v1: FTBFS: dh_auto_test: error: cd _build && go
test -vet=off -v -p 4 gopkg.in/gcfg.v1 gopkg.in/gcfg.v1/scanner
gopkg.in/gcfg.v1/token gopkg.in/gcfg.v1/types returned exit code 1
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.)
--
952227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gopkg-gcfg.v1
Version: 1.2.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp -rv testdata _build/src/gopkg.in/gcfg.v1/
> 'testdata/gcfg_test.gcfg' ->
> '_build/src/gopkg.in/gcfg.v1/testdata/gcfg_test.gcfg'
> 'testdata/gcfg_unicode_test.gcfg' ->
> '_build/src/gopkg.in/gcfg.v1/testdata/gcfg_unicode_test.gcfg'
> 'testdata/issue12.gcfg' -> '_build/src/gopkg.in/gcfg.v1/testdata/issue12.gcfg'
> 'testdata/notepad.ini' -> '_build/src/gopkg.in/gcfg.v1/testdata/notepad.ini'
> dh_auto_test
> cd _build && go test -vet=off -v -p 4 gopkg.in/gcfg.v1
> gopkg.in/gcfg.v1/scanner gopkg.in/gcfg.v1/token gopkg.in/gcfg.v1/types
> === RUN TestGoogleCodeIssue1
> --- PASS: TestGoogleCodeIssue1 (0.00s)
> issues_test.go:46: 0 pass: failed to parse "X" as int: expected integer
> at section "section", variable "int"
> issues_test.go:46: 1 pass: failed to parse "" as int: EOF at section
> "section", variable "int"
> issues_test.go:46: 2 pass: failed to parse "1A" as int: extra characters
> "A" at section "section", variable "int"
> issues_test.go:46: 3 pass: failed to parse "X" as big.Int: number has no
> digits at section "section", variable "bigint"
> issues_test.go:46: 4 pass: failed to parse "" as big.Int: unexpected EOF
> at section "section", variable "bigint"
> issues_test.go:46: 5 pass: failed to parse "1A" as big.Int: extra
> characters "A" at section "section", variable "bigint"
> === RUN TestGoogleCodeIssue2
> --- PASS: TestGoogleCodeIssue2 (0.00s)
> read_test.go:308: issue2:0 pass: got value
> {Main:struct { Foo string }{Foo:"bar"}}
> read_test.go:308: issue2:1 pass: got value
> {Main:struct { Foo string }{Foo:"bar"}}
> === RUN TestIssue11
> --- PASS: TestIssue11 (0.00s)
> issues_test.go:91: 0 pass: failed to parse bool `x` at section "Sect",
> variable "Var"
> issues_test.go:91: 1 pass: failed to parse bool `x` at section "Sect",
> variable "Var"
> === RUN TestIssue12
> --- PASS: TestIssue12 (0.00s)
> === RUN TestReadStringInto
> --- PASS: TestReadStringInto (0.00s)
> read_test.go:308: scanning:0 pass: got value
> {Section:gcfg.cBasicS1{Name:"value", Int:0,
> PName:(*string)(nil)}, Hyphen_In_Section:gcfg.cBasicS2{Hyphen_In_Name:""},
> unexported:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Exported:gcfg.cBasicS3{unexported:""}, TagName:gcfg.cBasicS1{Name:"", Int:0,
> PName:(*string)(nil)}}
> read_test.go:308: scanning:1 pass: got value
> {Section:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Hyphen_In_Section:gcfg.cBasicS2{Hyphen_In_Name:"value"},
> unexported:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Exported:gcfg.cBasicS3{unexported:""}, TagName:gcfg.cBasicS1{Name:"", Int:0,
> PName:(*string)(nil)}}
> read_test.go:308: scanning:2 pass: got value
> {Section:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Hyphen_In_Section:gcfg.cBasicS2{Hyphen_In_Name:""},
> unexported:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Exported:gcfg.cBasicS3{unexported:""}, TagName:gcfg.cBasicS1{Name:"", Int:0,
> PName:(*string)(nil)}}
> read_test.go:308: scanning:3 pass: got value
> {Section:gcfg.cBasicS1{Name:" ", Int:0, PName:(*string)(nil)},
> Hyphen_In_Section:gcfg.cBasicS2{Hyphen_In_Name:""},
> unexported:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Exported:gcfg.cBasicS3{unexported:""}, TagName:gcfg.cBasicS1{Name:"", Int:0,
> PName:(*string)(nil)}}
> read_test.go:308: scanning:4 pass: got value
> {Section:gcfg.cBasicS1{Name:"value", Int:0,
> PName:(*string)(nil)}, Hyphen_In_Section:gcfg.cBasicS2{Hyphen_In_Name:""},
> unexported:gcfg.cBasicS1{Name:"", Int:0, PName:(*string)(nil)},
> Exported:gcfg.cBasicS3{unexported:""}, TagName:gcfg.cBasicS1{Name:"", Int:0,
>
Bug#964047: marked as done (golang-github-src-d-gcfg: FTBFS: TestScanFully failure)
Your message dated Mon, 06 Jul 2020 02:25:28 + with message-id and subject line Bug#964047: fixed in golang-github-src-d-gcfg 1.4.0-2 has caused the Debian Bug report #964047, regarding golang-github-src-d-gcfg: FTBFS: TestScanFully failure 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.) -- 964047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-src-d-gcfg Version: 1.4.0-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: === RUN TestEnumParserBool TestEnumParserBool: enum_test.go:26: "tRuE": got true, TestEnumParserBool: enum_test.go:26: "False": got false, TestEnumParserBool: enum_test.go:26: "t": got false, failed to parse bool `t` --- PASS: TestEnumParserBool (0.00s) === RUN TestParseInt TestParseInt: int_test.go:63: ParseInt(int, "0", IntMode(Dec)): pass; got 0, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "-10", IntMode(Dec)): pass; got -10, error TestParseInt: int_test.go:63: ParseInt(int, "x", IntMode(Dec)): pass; got 0, error failed to parse "x" as int: expected integer TestParseInt: int_test.go:63: ParseInt(int, "0xa", IntMode(Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "a", IntMode(Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Hex)): pass; got 16, error TestParseInt: int_test.go:63: ParseInt(int, "-0xa", IntMode(Hex)): pass; got -10, error TestParseInt: int_test.go:54: ParseInt(int, "0x", IntMode(Hex)): fail; got error failed to parse "0x" as int: strconv.ParseInt: parsing "0x": invalid syntax, want ok TestParseInt: int_test.go:54: ParseInt(int, "-0x", IntMode(Hex)): fail; got error failed to parse "-0x" as int: strconv.ParseInt: parsing "-0x": invalid syntax, want ok TestParseInt: int_test.go:63: ParseInt(int, "-a", IntMode(Hex)): pass; got -10, error TestParseInt: int_test.go:63: ParseInt(int, "-10", IntMode(Hex)): pass; got -16, error TestParseInt: int_test.go:63: ParseInt(int, "x", IntMode(Hex)): pass; got 0, error failed to parse "x" as int: expected integer TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "-10", IntMode(Oct)): pass; got -8, error TestParseInt: int_test.go:63: ParseInt(int, "-010", IntMode(Oct)): pass; got -8, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec|Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Dec|Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Dec|Hex)): pass; got 16, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec|Oct)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Dec|Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Dec|Oct)): pass; got 0, error failed to parse "0x10" as int: extra characters "x10" TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Hex|Oct)): pass; got 0, error ambiguous integer value; must include '0' prefix TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Hex|Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Hex|Oct)): pass; got 16, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec|Hex|Oct)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Dec|Hex|Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Dec|Hex|Oct)): pass; got 16, error --- FAIL: TestParseInt (0.00s) === RUN TestScanFully TestScanFully: scan_test.go:32: ScanFully(*int, "a", 'v') = failed to parse "a" as int: expected integer; *ptr==0 TestScanFully: scan_test.go:23: ScanFully(*int, "0x", 'v'): want ok, got error failed to parse "0x" as int: strconv.ParseInt: parsing "0x": invalid syntax TestScanFully: scan_test.go:32: ScanFully(*int, "0x", 'd') = failed to parse "0x" as int: extra characters "x"; *ptr==0 --- FAIL: TestScanFully (0.00s) FAIL FAIL github.com/src-d/gcfg/types 0.016s FAIL dh_auto_test: error:
Processed: Bug#952227 marked as pending in golang-gopkg-gcfg.v1
Processing control commands: > tag -1 pending Bug #952227 [src:golang-gopkg-gcfg.v1] golang-gopkg-gcfg.v1: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 gopkg.in/gcfg.v1 gopkg.in/gcfg.v1/scanner gopkg.in/gcfg.v1/token gopkg.in/gcfg.v1/types returned exit code 1 Added tag(s) pending. -- 952227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952227: marked as pending in golang-gopkg-gcfg.v1
Control: tag -1 pending Hello, Bug #952227 in golang-gopkg-gcfg.v1 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/go-team/packages/golang-gopkg-gcfg.v1/-/commit/162c60c3cf494e6a317536d6d397420f854c6791 d/patches/fix-tests-go1.13.patch: fix tests that fail with changed strconv.ParseInt behavior in Go 1.13. (Closes: #952227) (this message was generated automatically) -- Greetings https://bugs.debian.org/952227
Processed: Bug#964047 marked as pending in golang-github-src-d-gcfg
Processing control commands: > tag -1 pending Bug #964047 [src:golang-github-src-d-gcfg] golang-github-src-d-gcfg: FTBFS: TestScanFully failure Added tag(s) pending. -- 964047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964047: marked as pending in golang-github-src-d-gcfg
Control: tag -1 pending Hello, Bug #964047 in golang-github-src-d-gcfg 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/go-team/packages/golang-github-src-d-gcfg/-/commit/fcdd8230a2f295ed61cabd75e46dd755cf8cb4af d/patches/fix-tests-go1.13.patch: fix tests that fail with changed strconv.ParseInt behavior in Go 1.13. (Closes: #964047) (this message was generated automatically) -- Greetings https://bugs.debian.org/964047
Bug#964360: libghc-doctemplates-doc: depends on unavailable haddock-interface-33
Package: libghc-doctemplates-doc Version: 0.2.2.1-4 Severity: serious Justification: uninstallable Hi seems that libghc-doctemplates-doc is not installable. $ sudo apt install libghc-doctemplates-doc Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libghc-doctemplates-doc : Depends: haddock-interface-33 but it is not installable Recommends: ghc-doc but it is not going to be installed Recommends: libghc-aeson-doc but it is not going to be installed Recommends: libghc-blaze-html-doc but it is not going to be installed E: Unable to correct problems, you have held broken packages. Best Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.7 (SMP w/4 CPU cores) Kernel taint flags: 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libghc-doctemplates-doc depends on: pn haddock-interface-33 Versions of packages libghc-doctemplates-doc recommends: pn ghc-doc pn libghc-aeson-doc pn libghc-blaze-html-doc ii libjs-mathjax 2.7.8+dfsg-1 libghc-doctemplates-doc suggests no packages.
Bug#964124: marked as done (therion FTBFS: test failures)
Your message dated Sun, 05 Jul 2020 23:48:38 + with message-id and subject line Bug#964124: fixed in therion 5.5.1ds1-1 has caused the Debian Bug report #964124, regarding therion FTBFS: test failures 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.) -- 964124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: therion Version: 5.5.0ds1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=therion=sid ... ./utest ~~~ utest is a Catch v2.11.3 host application. Run with -? for options --- projections: JTSK03 -- utm, auto=true --- utest-proj.cxx:82 ... utest-proj.cxx:85: FAILED: CHECK( coord_equal(x, p1_utm_e, 0.01) ) with expansion: false utest-proj.cxx:86: FAILED: CHECK( coord_equal(y, p1_utm_n, 0.01) ) with expansion: false utest-proj.cxx:87: FAILED: CHECK( coord_equal(z, p1_utm_h, 0.1) ) with expansion: false === test cases: 17 | 16 passed | 1 failed assertions: 41 | 38 passed | 3 failed make[2]: *** [Makefile:191: tests] Error 3 --- End Message --- --- Begin Message --- Source: therion Source-Version: 5.5.1ds1-1 Done: Wookey We believe that the bug you reported is fixed in the latest version of therion, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wookey (supplier of updated therion 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: SHA256 Format: 1.8 Date: Fri, 03 Jul 2020 22:08:06 +0100 Source: therion Architecture: source Version: 5.5.1ds1-1 Distribution: unstable Urgency: medium Maintainer: Wookey Changed-By: Wookey Closes: 964124 Changes: therion (5.5.1ds1-1) unstable; urgency=medium . * New upstream release * Fixes test failure due to proj 7.1 (Closes: #964124) * Show deprecation warnings * Use system catch2 Checksums-Sha1: 491ae8a45d257428f54693d76cdcfe1e60786bda 2198 therion_5.5.1ds1-1.dsc ce91c3de8ba8f50449a4a5d2e74b9825f65f7bdf 2340360 therion_5.5.1ds1.orig.tar.gz 2b20fa8c53a9f1aeda0b263486fb605b3a3e 20904 therion_5.5.1ds1-1.debian.tar.xz d93b56155c0521b81e0b3f02585424454da093ec 20829 therion_5.5.1ds1-1_amd64.buildinfo Checksums-Sha256: 4b5129235c93467b7ba6d6c8801a3022aa8b02adbfad8d81efbe7134efe8 2198 therion_5.5.1ds1-1.dsc 2af5ce10c09654cd3da921dbb924fc7b3c0b521806fa691eab6f059de320491a 2340360 therion_5.5.1ds1.orig.tar.gz b352b17c63883ef39d1f86706c693cb46a61d5ab4965702c284f9e23de0515b2 20904 therion_5.5.1ds1-1.debian.tar.xz 0dd5caa4baa17cb8cf435dfef28e856b83a54630b48c1712bb405069f2ebb0f0 20829 therion_5.5.1ds1-1_amd64.buildinfo Files: d5189ef80e8072d9016aff3404762a3b 2198 science optional therion_5.5.1ds1-1.dsc 45d2dbd89b3600da7d0fd1b85aeadefc 2340360 science optional therion_5.5.1ds1.orig.tar.gz d178b7f234e8d091c74e7b5757be30a9 20904 science optional therion_5.5.1ds1-1.debian.tar.xz a8d00cbd004ad1c0c00c77c4c618519f 20829 science optional therion_5.5.1ds1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAl8CY0oACgkQ+4YyUahv nkdx+hAApVirNWFMWShcPoNyYSlbekxCRSxIpkpm6VWytRzg4BeheeQG2u5OCPPT mhwHMgJsNQemqQl2TwCFzFdbyQXwlyDPp9kTc3Syv763oc3k0FIA+JdOFEYZ5ys4 vyd4RBLqeFx1f7PL9oWrjLMKzkWewExCdYayw0XRivZIvAFobyTBrIs8uRs+Ogsp SFGJBcGqJ0zGh9eK9eE2C4B6q+JgqS0N2Bc8y7NeO4juTCS7b4Q8L6dMw1X/A6yL eDIv72fqR2vjYfdnOs5LYGhXu3uWpbmCb2PU3Cc79UKHt37qr/33DHJ/v1kSv1d2 u2J/9zkpWGIa4LufXBtb7NsLmwSPrbjXNexFERQ2shel+opIEYoCDqOF0mKW420U rtCvi+UHSc3d3Qf8voSmWDjUPHOQJjC1Z8w5Fc4Kba5QNB9pGR/VRtpbGWu2sTlt Wn/F8+cmZX71oZKhxTDousgMjaxZ2kHqJ5VMtLKPt3il2nE//ctbhEWjOqbCD6EZ zLEHUhAYDDTr+lD0ipfzdzpQgXoCkcmvHG7/LzYPQBuQc3oBXbs5amCHAzKTMmsl 48FsoyyQsNo46AINNB4ZVaR01MIUARIa4n5s6hqyk+6pTEjGN2fxE7npJm2l0fxX
Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr
Hi Adrian On Sun, 5 Jul 2020 at 19:02, Adrian Bunk wrote: > This is #962550. Are you sure? The failing test was with ligclib1 0.11.8-1 from testing and gff2aplot 2.0-13 from unstable. Regards Graham
Bug#964136: marked as done (glewlwyd build-depedencies unsatisfiable on armel)
Your message dated Sun, 05 Jul 2020 22:34:05 + with message-id and subject line Bug#964136: fixed in glewlwyd 2.3.1-7 has caused the Debian Bug report #964136, regarding glewlwyd build-depedencies unsatisfiable on armel 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.) -- 964136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glewlywd Version: 2.3.1-2 Severity: serious The new glewlywd package cannot be built on armel, mipsel or mips64el due to unsatisfiable build-dependencies. Specifically nodejs/npm on armel and librhonabwy-dev on mipsel/mips64el Generally there are three possible ways forward with this sort of issues, listed in descending order of preference. 1. Fix the packages that your package build-depends on so that they build on the architectures in question. 2. Adjust the build so it can build without those dependencies on the affected architectures 3. Declare that your package cannot reasonably be supported on those architectures and file a removal request with the ftpmasters. --- End Message --- --- Begin Message --- Source: glewlwyd Source-Version: 2.3.1-7 Done: Nicolas Mora We believe that the bug you reported is fixed in the latest version of glewlwyd, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Mora (supplier of updated glewlwyd 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: SHA256 Format: 1.8 Date: Sun, 05 Jul 2020 18:00:58 -0400 Source: glewlwyd Architecture: source Version: 2.3.1-7 Distribution: unstable Urgency: medium Maintainer: Nicolas Mora Changed-By: Nicolas Mora Closes: 964136 Changes: glewlwyd (2.3.1-7) unstable; urgency=medium . * Upload to unstable (Closes: #964136) Checksums-Sha1: 86931cb63a2403d339e89e9c83d91bc680fb73f7 2531 glewlwyd_2.3.1-7.dsc 1b97fd60cd208f01a8c1e40545c492301602d2bd 18724 glewlwyd_2.3.1-7.debian.tar.xz d9ef2761d26be05a371c9076ee026cdabd1581ee 18865 glewlwyd_2.3.1-7_amd64.buildinfo Checksums-Sha256: 05bc235e7524a98381c756a28a9655617b2f71634121e9eefb9ae0f0896fa06c 2531 glewlwyd_2.3.1-7.dsc 6f8547983938303c3f3a468273b0fdfe53e57e1c4dbeec6db3e3dc732d67 18724 glewlwyd_2.3.1-7.debian.tar.xz d25eb1f75e6b491ae936be71b8d53805d7897026c97f57e4bde7c29d541f3fac 18865 glewlwyd_2.3.1-7_amd64.buildinfo Files: b137cd25b75f10931d319e8918b9b36c 2531 web optional glewlwyd_2.3.1-7.dsc 8d704ca4d1656fe8a8257744657b10c7 18724 web optional glewlwyd_2.3.1-7.debian.tar.xz 0265cf6279b3f8a424cd01aff41d9e7f 18865 web optional glewlwyd_2.3.1-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAl8CUCMACgkQ/oITlEC9 IrkzMw//UoOOU/v7FNc250Hh/BXX8Af9+NlxWUcZi0vvS780FFs+b+7/Un4PlLzQ xMF4pSkCYN5Jv65nFyLozbzEForvtojHbJ2knqRDL/x7Xstq7W4vf+GVsBxpZUto Xa91RpBFyLOsGXgqDRKg47VoQp6mUbm3PtNnXRbTXe7DRUEbECid8F74F9LwO3ng W3F07b3gbdhfzHCmDjInpRTRP4UcMZVDTyJY5FORzY0Akp5zx4iFGYA6o5pKlxWg P7rsvC0m5xyOAWcWB/3vTvTelKN+1GmJjGh2mshPqVwZv2GOlRD0NxCBcP3i6Jn2 eg5uiABd8cEKwNl/FPThUARDUX/WqLBHbFE4XRV0RCO2UErtwCxiYh9dlxA0r905 lxSL1KrFWXHWimiScvjJp1snmE37z+8dYkBAfCtYWUjJ+51nfJkT9Qle31MzIZ5P tBdRz5I1Gszx8HMPh/V7zI4G35f7TU/Rf5YUfQ4vq4OYQkNs5/8pZu1ixRZK6Tw2 R0Q/1/wUw5LwtXdDPE6WCy4KW6KKNNLNrkD+Y9LagfMao6A4s+tRHm+uK7j6JGjp agrmjFRVq9pnVVoB5ARMClVsRmpih89E6PVo2W7fJ6SJutnXdIevOOryRBNHUhbk CXfK1kERPd+70E/RgkagDYsAOVWxsbPVrTBfSl7si7WbT5zhojU= =60rW -END PGP SIGNATURE End Message ---
Bug#964356: libcoarrays-{mpich,openmpi}-dev: not co-installable due to usr/lib/x86_64-linux-gnu/libcaf_mpi.a
Package: libcoarrays-mpich-dev,libcoarrays-openmpi-dev Version: 2.9.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files ... >From the attached log (scroll to the bottom...): Selecting previously unselected package libcoarrays-openmpi-dev:amd64. Preparing to unpack .../38-libcoarrays-openmpi-dev_2.9.0-1_amd64.deb ... Unpacking libcoarrays-openmpi-dev:amd64 (2.9.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-wpbcvq/38-libcoarrays-openmpi-dev_2.9.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcaf_mpi.a', which is also in package libcoarrays-mpich-dev:amd64 2.9.0-1 Errors were encountered while processing: /tmp/apt-dpkg-install-wpbcvq/38-libcoarrays-openmpi-dev_2.9.0-1_amd64.deb cheers, Andreas
Bug#964293: hubicfuse: error while loading libssl.so.1.0.0
Control: tag -1 + stretch Control: fixed -1 3.0.1-1 On Sun, 5 Jul 2020 11:51:43 +0200, Stephen Kitt wrote: > On Sun, 05 Jul 2020 11:42:08 +0200, rpnpif wrote: > > The command hubicfuse /mnt/hubic -o noauto_cache,sync_read > > get the result : > > hubicfuse: error while loading shared libraries: libssl.so.1.0.0: cannot > > open shared object file: No such file or directory > > > > but libssl1.1 was needed. > > What does > > command -v hubicfuse > > show? Also, do you have libssl1.0.2 installed? libcurl3 depends on it in Stretch so it should be available if you have hubicfuse installed... Regards, Stephen pgpOl8PDXk0ws.pgp Description: OpenPGP digital signature
Processed: Re: Bug#964293: hubicfuse: error while loading libssl.so.1.0.0
Processing control commands: > tag -1 + stretch Bug #964293 [hubicfuse] hubicfuse: error while loading libssl.so.1.0.0 Added tag(s) stretch. > fixed -1 3.0.1-1 Bug #964293 [hubicfuse] hubicfuse: error while loading libssl.so.1.0.0 Marked as fixed in versions hubicfuse/3.0.1-1. -- 964293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964353: libpappsomspp FTBFS: Boost not yet found
Source: libpappsomspp Version: 0.7.5-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpappsomspp.html https://buildd.debian.org/status/package.php?p=libpappsomspp ... -- CMAKE_CURRENT_BINARY_DIR: /<>/obj-aarch64-linux-gnu -- Compiling in release mode. -- [1;33mCMAKE_BUILD_TYPE: Release.[m -- Boost not yet found. Searching for it. CMake Error at /usr/lib/aarch64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:117 (find_package): Could not find a package configuration file provided by "boost_filesystem" (requested version 1.71.0) with any of the following names: boost_filesystemConfig.cmake boost_filesystem-config.cmake Add the installation prefix of "boost_filesystem" to CMAKE_PREFIX_PATH or set "boost_filesystem_DIR" to a directory containing one of the above files. If "boost_filesystem" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): /usr/lib/aarch64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component) /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) CMakeLists.txt:172 (find_package) -- Configuring incomplete, errors occurred!
Bug#964208: marked as done (wsjtx: FTBFS without internet access)
Your message dated Sun, 05 Jul 2020 21:21:38 + with message-id and subject line Bug#964208: fixed in wsjtx 2.2.2+repack-2 has caused the Debian Bug report #964208, regarding wsjtx: FTBFS without internet access 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.) -- 964208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wsjtx Version: 2.2.1+repack-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. I suppose it's xsltproc calling out for external resources or something like that. This is probably the cause for the 2.2.2+repack-1 armhf build failure too; I think the conova buildds only have IPv6 connectivity. >From the build log: make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/wsjt_fort_autogen.dir/DependInfo.cmake --color= a2x: ERROR: "xsltproc" -param man.endnotes.list.enabled 0 -param man.endnotes.are.numbered 0 --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 "/etc/asciidoc/docbook-xsl/manpage.xsl" "/<>/obj-x86_64-linux-gnu/manpages/man/man1/wsjtx.1.xml" returned non-zero exit status 5 make[3]: *** [manpages/CMakeFiles/manpages.dir/build.make:73: manpages/man/man1/wsjtx.1.gz] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:2390: manpages/CMakeFiles/manpages.dir/all] Error 2 -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: wsjtx Source-Version: 2.2.2+repack-2 Done: tony mancill We believe that the bug you reported is fixed in the latest version of wsjtx, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated wsjtx 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: Sun, 05 Jul 2020 13:25:05 -0700 Source: wsjtx Architecture: source Version: 2.2.2+repack-2 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: tony mancill Closes: 964208 Changes: wsjtx (2.2.2+repack-2) unstable; urgency=medium . * Team upload. * Add patch to pass --nonet to xsltproc for manpages and add docbook-xml to Build-Depends. (Closes: #964208) * Add patch for spelling typo in the wsjtx manpage. Checksums-Sha1: 86e60cf1a88412540fc3fe61cefa540384b7e340 2546 wsjtx_2.2.2+repack-2.dsc 492aa890d4d72c99e29939bb077174b47db5744f 16000 wsjtx_2.2.2+repack-2.debian.tar.xz 5a76ec1e593f410e8d90f3fa851c6539a7dc55cc 15286 wsjtx_2.2.2+repack-2_amd64.buildinfo Checksums-Sha256: 6a46fd14250f8d8848ad8518c4c98e24bfd9d9007a08d9ca7295a8acce2dd439 2546 wsjtx_2.2.2+repack-2.dsc 37162204bb5d1021392e98777d019fdffc618b9bbf0530a39f0f62ae7114a379 16000 wsjtx_2.2.2+repack-2.debian.tar.xz 3cd9cc59bf89d87119ee03170f007e3aa194d712d3d9795b2ce2ff154d4bf071 15286 wsjtx_2.2.2+repack-2_amd64.buildinfo Files: f6180ba85a8c9bc57ad1afe0f76cb207 2546 hamradio optional wsjtx_2.2.2+repack-2.dsc 9efb1a20ba608a1de9df317783cd0378 16000 hamradio optional wsjtx_2.2.2+repack-2.debian.tar.xz 50db2e0f7b9cd2264600060764bdb64b 15286 hamradio optional wsjtx_2.2.2+repack-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8CPmUUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpa2exAAqcRt2ugDAPoUcztNXfZAK2D6qVlR 5HXLnVu45IHAluSYWataYQdkrJlEpxDuTIenpBUL7GlVmZCzavZEen0KJAtDhwRZ JWg6bkAetE4KoKX06js7Q27o5FJY7zQNPlt7lkcMI04XWUOk6VopzQKtS7ngqA6M pKeRqMt/yQzagS5YjEyOG4G8qElnskF1uLU+/uz+LpKBHzSlCOnCO1SulHZaCXh3 4naSBnsRYgY81qVn6GZzHzE2LkF6p6GLMmj7SpAih6cHq9oU5+LJfLSW61C7Eg0X mOVKgKlce/Ko5KIF7KVCVmYsOCczUfHQQj/bkF4zyeAL0Fwc+nuz7FX6FaV9qZyw MysM8n0pBPgFyRKH5bGYPE93sOsrYqubzeZ+BeUz1fWXbv3/oeMb6Q6uWeu234rc vBHUCldIu0LCCsjP9FiNbqV0GV+Y++TciKwByoy7JUWeKx5JZMx7/bi6+23EYenU fYKxYMDx+W8nNXBfZOF5zse7lMaVp+yNUgKtGDaspEZJusEbnQotB7dpjPeaL7gy
Processed: Bug#964208 marked as pending in wsjtx
Processing control commands: > tag -1 pending Bug #964208 [src:wsjtx] wsjtx: FTBFS without internet access Added tag(s) pending. -- 964208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964208: marked as pending in wsjtx
Control: tag -1 pending Hello, Bug #964208 in wsjtx 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/debian-hamradio-team/wsjtx/-/commit/593ef0e259121b3035722b6db6b6985043bf88af Add patch to pass --nonet to xsltproc for manpages (Closes: #964208) (this message was generated automatically) -- Greetings https://bugs.debian.org/964208
Processed: severity of 962533 is important
Processing commands for cont...@bugs.debian.org: > severity 962533 important Bug #962533 [src:mlpack] mlpack FTBFS on mips64el: relocation truncated to fit Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 962533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964348: bbhash: Missing test dependencies
Source: bbhash Version: 1.0.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/b/bbhash/5910297/log.gz ... autopkgtest [21:08:27]: test run-unit-test: [--- g++ -o Bootest bootest.cpp -O3 -std=c++11 -lpthread make: g++: Command not found make: *** [makefile:29: Bootest] Error 127
Bug#964208: wsjtx: FTBFS without internet access
Re: tmanc...@debian.org > For now I'll add docbook-xsl to the B-D for wsjtx > and upload with the patch for XSLTPROC_OPTS to add --nonet. That's the best option, I think. Thanks! Christoph
Bug#964208: wsjtx: FTBFS without internet access
On Sun, Jul 05, 2020 at 09:55:30PM +0200, Christoph Berg wrote: > Re: tmanc...@debian.org > > > I/O error : Attempt to load network entity > > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > > warning: failed to load external entity > > > "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; > > > compilation error: file /etc/asciidoc/docbook-xsl/manpage.xsl line 12 > > > element import > > > xsl:import : unable to load > > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > > ... > > > > So I propose that we reassign this to asciidoc, since any package that > > build-depends on asciidoc and uses the manpage stylesheet should fail in > > the same manner. I don't have any experience with XSL stylesheets, but > > I assume that the asciidoc package can be updated to include the > > necessary components such that xsl files need not be fetched from the > > network during the build. > > > > Does that sound reasonable to folks? > > The primary problem is that we are missing a build-dependency on > docbook-xsl and possibly more packages of the xsl family which contain > the necessary files. > > I can't say if that is actually a bug in asciidoc to not depend on > the bunch. (I guess at least a Recommends or Suggests there is in > order, but that wouldn't fix the B-D problem.) Ooh, thank you for the tip about docbook-xsl! That gives us a path forward for wsjtx. I see what you're saying about this maybe not being a bug for asciidoc. For now I'll add docbook-xsl to the B-D for wsjtx and upload with the patch for XSLTPROC_OPTS to add --nonet. Thanks, tony
Processed: src:fastqc: fails to migrate to testing for too long: B-D on package that fails to migrate
Processing control commands:
> close -1 0.11.9+dfsg-4
Bug #964344 [src:fastqc] src:fastqc: fails to migrate to testing for too long:
B-D on package that fails to migrate
Marked as fixed in versions fastqc/0.11.9+dfsg-4.
Bug #964344 [src:fastqc] src:fastqc: fails to migrate to testing for too long:
B-D on package that fails to migrate
Marked Bug as done
> block -1 by 959955
Bug #964344 {Done: Paul Gevers } [src:fastqc] src:fastqc:
fails to migrate to testing for too long: B-D on package that fails to migrate
964344 was not blocked by any bugs.
964344 was not blocking any bugs.
Added blocking bug(s) of 964344: 959955
--
964344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964344: src:fastqc: fails to migrate to testing for too long: B-D on package that fails to migrate
Source: fastqc Version: 0.11.9+dfsg-3 Severity: serious Control: close -1 0.11.9+dfsg-4 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 959955 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:fastqc in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=fastqc signature.asc Description: OpenPGP digital signature
Bug#959579: adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1
Hello Sudip and Franciscarlos, I'm writing this email as I help Franciscarlos by sponsoring his uploads and we had discussed the state of adapta-gtk-theme upstream and this issue privately before. Thanks for the patch and the delayed upload. I cancelled the upload for now so we can have this discussion. adapta-gtk-theme's upstream archived the project about 2 years ago, and we are not sure if the current version of gnome on testing/unstable works without issues with it. We had agreed to fill a package removal request because of that, and I haven't replied to this bug before because I was going to fill the RoM as the next step (I should have done it earlier). I believe the way forward (to have this package on Debian), for someone interested in it, is to contact upstream and see if they're willing to let someone else assume the maintenance, especially since this patch should be there. Once there's a new upstream and guarantee that the project is working with the latest gnome release, we will be able to ship adapta-gtk-theme again. The next step from our side is to fill the RoM removal request, I will help Franciscarlos with that. Please feel free to give your inputs. Thanks, -- Samuel Henrique
Bug#964341: src:connectagram: fails to migrate to testing for too long: maintainer build arch:all
Source: connectagram Version: 1.2.10-1 Severity: serious Control: close -1 1.2.11-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:connectagram in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=connectagram signature.asc Description: OpenPGP digital signature
Processed: src:connectagram: fails to migrate to testing for too long: maintainer build arch:all
Processing control commands: > close -1 1.2.11-1 Bug #964341 [src:connectagram] src:connectagram: fails to migrate to testing for too long: maintainer build arch:all Marked as fixed in versions connectagram/1.2.11-1. Bug #964341 [src:connectagram] src:connectagram: fails to migrate to testing for too long: maintainer build arch:all Marked Bug as done -- 964341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964339: node-expat: autopkgtest regression: Cannot find module 'iconv'
Source: node-expat
Version: 2.3.18+ds-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Thank you for fixing bug #963060, however with the upload fixing that
issued the autopkgtest of node-expat fails in testing when that
autopkgtest is run with the binary packages of node-expat from unstable.
It passes when run with only packages from testing. In tabular form:
passfail
node-expat from testing2.3.18+ds-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=node-expat
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-expat/6151675/log.gz
autopkgtest [16:26:52]: test command2: vows --spec ./test/**/*.js
autopkgtest [16:26:52]: test command2: [---
internal/modules/cjs/loader.js:969
throw err;
^
Error: Cannot find module 'iconv'
Require stack:
- /tmp/autopkgtest-lxc.wq1g4b2f/downtmp/build.zVe/src/test/index.js
- /usr/share/nodejs/vows/bin/vows
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:966:15)
at Function.Module._load (internal/modules/cjs/loader.js:842:27)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object.
(/tmp/autopkgtest-lxc.wq1g4b2f/downtmp/build.zVe/src/test/index.js:4:13)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/tmp/autopkgtest-lxc.wq1g4b2f/downtmp/build.zVe/src/test/index.js',
'/usr/share/nodejs/vows/bin/vows'
]
}
autopkgtest [16:26:52]: test command2: ---]
signature.asc
Description: OpenPGP digital signature
Bug#964208: wsjtx: FTBFS without internet access
Re: tmanc...@debian.org > > I/O error : Attempt to load network entity > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > warning: failed to load external entity > > "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; > > compilation error: file /etc/asciidoc/docbook-xsl/manpage.xsl line 12 > > element import > > xsl:import : unable to load > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > ... > > So I propose that we reassign this to asciidoc, since any package that > build-depends on asciidoc and uses the manpage stylesheet should fail in > the same manner. I don't have any experience with XSL stylesheets, but > I assume that the asciidoc package can be updated to include the > necessary components such that xsl files need not be fetched from the > network during the build. > > Does that sound reasonable to folks? The primary problem is that we are missing a build-dependency on docbook-xsl and possibly more packages of the xsl family which contain the necessary files. I can't say if that is actually a bug in asciidoc to not depend on the bunch. (I guess at least a Recommends or Suggests there is in order, but that wouldn't fix the B-D problem.) Christoph
Bug#963317: marked as done (python-urwidtrees: FTBFS: locale.Error: unsupported locale setting)
Your message dated Sun, 05 Jul 2020 19:34:14 +
with message-id
and subject line Bug#963317: fixed in python-urwidtrees 1.0.3.dev0-1
has caused the Debian Bug report #963317,
regarding python-urwidtrees: FTBFS: locale.Error: unsupported locale setting
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.)
--
963317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-urwidtrees
Version: 1.0.1.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:217: python3.8 setup.py clean
> Traceback (most recent call last):
> File "setup.py", line 4, in
> import urwidtrees.version as v
> File "/<>/urwidtrees/__init__.py", line 6, in
> from .decoration import DecoratedTree, CollapsibleTree
> File "/<>/urwidtrees/decoration.py", line 4, in
> import urwid
> File "/usr/lib/python3/dist-packages/urwid/__init__.py", line 26, in
>
> from urwid.widget import (FLOW, BOX, FIXED, LEFT, RIGHT, CENTER, TOP,
> MIDDLE,
> File "/usr/lib/python3/dist-packages/urwid/widget.py", line 27, in
> from urwid.util import (MetaSuper, decompose_tagmarkup, calc_width,
> File "/usr/lib/python3/dist-packages/urwid/util.py", line 61, in
> detected_encoding = detect_encoding()
> File "/usr/lib/python3/dist-packages/urwid/util.py", line 58, in
> detect_encoding
> locale.setlocale(locale.LC_ALL, initial)
> File "/usr/lib/python3.8/locale.py", line 608, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
> python3.8 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.8 returned exit
> code 13
> make: *** [debian/rules:7: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/python-urwidtrees_1.0.1.1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-urwidtrees
Source-Version: 1.0.3.dev0-1
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
python-urwidtrees, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated python-urwidtrees
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: Sun, 05 Jul 2020 16:14:38 +
Source: python-urwidtrees
Architecture: source
Version: 1.0.3.dev0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Nilesh Patra
Closes: 963317
Changes:
python-urwidtrees (1.0.3.dev0-1) unstable; urgency=medium
.
* Team Upload.
* New upstream version 1.0.3.dev0 (Closes: #963317)
* Update Build-Deps
* Bump compat version to 13
* Bump standards version to 4.5.0
* Add upstream/metadata
* Add "Rules-Requires-Root:no"
* Harden dependency on python3-urwid
Checksums-Sha1:
40c212cd54cf4819ca6425b4028a431aa69b1fc1 2215
python-urwidtrees_1.0.3.dev0-1.dsc
67c144c2a5a457ee1fd8ce63fff84fc3aee29bf8 13355
python-urwidtrees_1.0.3.dev0.orig.tar.gz
20c6d8834dd3fa7075e1d749e51a7aba87a2ef21 2200
python-urwidtrees_1.0.3.dev0-1.debian.tar.xz
2c090c12d9e03e1406c43e372720b944ff086584 6262
Bug#964208: wsjtx: FTBFS without internet access
On Sat, Jul 04, 2020 at 01:08:32PM +0200, Christoph Berg wrote: > Ideally we should add some --nonet flag to make the failure both more obvious > and reproducible. Here's an update on this bug... There is a "--nonet" option that can be passed to xsltproc, but the build fails when that option is used, returning error code 5; from the xsltproc manpage: 5 Error in the stylesheet The issue lies in the asciidoc package when the manpage stylesheet is used in conjunction with --nonet. I tweaked the autopkgtest to show the failure and pushed a branch and created a merge request [1]. From the verbose output of the now failing test: > ... > creating dictionary for stylesheet > reusing dictionary from /etc/asciidoc/docbook-xsl/manpage.xsl for stylesheet > xsltParseStylesheetProcess : found stylesheet > xsltPreprocessStylesheet: removing ignorable blank node > Reusing dictionary for document > I/O error : Attempt to load network entity > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > warning: failed to load external entity > "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; > compilation error: file /etc/asciidoc/docbook-xsl/manpage.xsl line 12 element > import > xsl:import : unable to load > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > ... So I propose that we reassign this to asciidoc, since any package that build-depends on asciidoc and uses the manpage stylesheet should fail in the same manner. I don't have any experience with XSL stylesheets, but I assume that the asciidoc package can be updated to include the necessary components such that xsl files need not be fetched from the network during the build. Does that sound reasonable to folks? Thanks, tony [1] https://salsa.debian.org/debian/asciidoc/-/merge_requests/1 signature.asc Description: PGP signature
Bug#964334: segfault repeatedly
Package: chromium Version: 83.0.4103.116-2 Severity: grave I've upgraded chromium to the current version in testing, and it segfaults repeatedly (and very "reliably"! :-)) after usually ~1 minute of runtime, even when not used in foreground, with a stack trace like this one: - $ chromium (chromium:1480721): Gtk-WARNING **: 21:03:45.963: Theme parsing error: gtk.css:6:20: The 'gtk-key-bindings' property has been renamed to '-gtk-key-bindings' [1480760:1480760:0705/210346.245467:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [1480764:1480779:0705/210348.465499:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile Received signal 11 SEGV_MAPERR 7f01744946c7 #0 0x557d36628c69 (/usr/lib/chromium/chromium+0x52b3c68) #1 0x557d36587ef3 (/usr/lib/chromium/chromium+0x5212ef2) #2 0x557d366287f1 (/usr/lib/chromium/chromium+0x52b37f0) #3 0x7f1a95d8d110 (/usr/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f) #4 0x7f1a90e78d3c (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b) #5 0x7f1a90e7af33 (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32) #6 0x7f1a90e7cbf9 __libc_malloc #7 0x557d366409be operator new() #8 0x7f1a91103a2c std::__cxx11::basic_string<>::reserve() #9 0x7f1a910f9498 std::__cxx11::basic_stringbuf<>::overflow() #10 0x7f1a9110204a std::basic_streambuf<>::xsputn() #11 0x7f1a910f4714 std::__ostream_insert<>() #12 0x557d36628d39 (/usr/lib/chromium/chromium+0x52b3d38) #13 0x557d36629054 (/usr/lib/chromium/chromium+0x52b4053) #14 0x557d3659a412 (/usr/lib/chromium/chromium+0x5225411) #15 0x557d3659c548 (/usr/lib/chromium/chromium+0x5227547) #16 0x557d34ce212a (/usr/lib/chromium/chromium+0x396d129) #17 0x557d34ce217e (/usr/lib/chromium/chromium+0x396d17d) #18 0x557d34337387 (/usr/lib/chromium/chromium+0x2fc2386) #19 0x557d34c9b3d9 (/usr/lib/chromium/chromium+0x39263d8) #20 0x557d34c9b61e (/usr/lib/chromium/chromium+0x392661d) #21 0x557d34ce5967 (/usr/lib/chromium/chromium+0x3970966) #22 0x557d34d114c7 (/usr/lib/chromium/chromium+0x399c4c6) #23 0x557d34d1177e (/usr/lib/chromium/chromium+0x399c77d) #24 0x557d34ce213f (/usr/lib/chromium/chromium+0x396d13e) #25 0x557d34ce217e (/usr/lib/chromium/chromium+0x396d17d) #26 0x557d34337387 (/usr/lib/chromium/chromium+0x2fc2386) #27 0x557d345fa7a3 (/usr/lib/chromium/chromium+0x32857a2) #28 0x557d349690bc (/usr/lib/chromium/chromium+0x35f40bb) #29 0x557d3675a45f (/usr/lib/chromium/chromium+0x53e545e) #30 0x557d36760a24 (/usr/lib/chromium/chromium+0x53eba23) #31 0x557d3675eb62 (/usr/lib/chromium/chromium+0x53e9b61) #32 0x557d3675d82d (/usr/lib/chromium/chromium+0x53e882c) #33 0x557d36756213 (/usr/lib/chromium/chromium+0x53e1212) #34 0x557d36771abb (/usr/lib/chromium/chromium+0x53fcaba) #35 0x557d36771de0 (/usr/lib/chromium/chromium+0x53fcddf) #36 0x557d36771370 (/usr/lib/chromium/chromium+0x53fc36f) #37 0x557d345e3c46 (/usr/lib/chromium/chromium+0x326ec45) #38 0x557d345e376c (/usr/lib/chromium/chromium+0x326e76b) #39 0x557d345dfeed (/usr/lib/chromium/chromium+0x326aeec) #40 0x557d345d674b (/usr/lib/chromium/chromium+0x326174a) #41 0x557d345c9044 (/usr/lib/chromium/chromium+0x3254043) #42 0x557d345c8d75 (/usr/lib/chromium/chromium+0x3253d74) #43 0x557d345e7426 (/usr/lib/chromium/chromium+0x3272425) #44 0x557d366460e0 (/usr/lib/chromium/chromium+0x52d10df) #45 0x7f1a94b42b0f (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.7.0.0+0x23b0e) #46 0x7f1a94b4324f event_base_loop #47 0x557d3664638e (/usr/lib/chromium/chromium+0x52d138d) #48 0x557d365e65d5 (/usr/lib/chromium/chromium+0x52715d4) #49 0x557d365be670 (/usr/lib/chromium/chromium+0x524966f) #50 0x557d349043b3 (/usr/lib/chromium/chromium+0x358f3b2) #51 0x557d365fc2a9 (/usr/lib/chromium/chromium+0x52872a8) #52 0x557d36638c9e (/usr/lib/chromium/chromium+0x52c3c9d) #53 0x7f1a95d81f27 start_thread #54 0x7f1a90ef031f clone r8: 0077 r9: 0050 r10: 0004 r11: 007c r12: 7f1a7420 r13: 7f1a7430 r14: 7f1a74736850 r15: 0020 di: 0021 si: 0004 bp: 0020 bx: 7f01744946bf dx: 7f1a7480 ax: 7f1a742d4d90 cx: 7f01744946bf sp: 7f1a826d3440 ip: 7f1a90e78d3c efl: 00010202 cgf: 002b0033 erf: 0004 trp: 000e msk: cr2: 7f01744946c7 [end of stack trace] Calling _exit(1). Core file will not be generated. - Thanks a lot for maintaining chromium in Debian, Hope this helps -- System Information: Debian
Processed: Re: Bug#964242: bsdmainutils: depends on non-existing version of bsdextrautils
Processing commands for cont...@bugs.debian.org: > affects 964242 debootstrap Bug #964242 [bsdmainutils] bsdmainutils: depends on non-existing version of bsdextrautils Added indication that 964242 affects debootstrap > thanks Stopping processing here. Please contact me if you need assistance. -- 964242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964242: bsdmainutils: depends on non-existing version of bsdextrautils
affects 964242 debootstrap thanks On Sun, 5 Jul 2020 12:52:54 +0200 Michael Meskes wrote: > On Sat, Jul 04, 2020 at 10:52:04AM +0200, Rene Engelhard wrote: > > But that bsdextrautils (>= 2.35.2-7) doesn't exist: > > Yes, as already communicated we had to wait with the next util-linux upload > until bsdmainutils made it out of NEW. Now that it has, Chris will upload as > soon as he finds the time. Because debootstrap follows Recommends and bsdmainutils is Recommended by bsdutils in Priority: required, this bug means debootstrap can't currently create sid bases. Sincerely, -- Harlan Lieberman-Berg ~hlieberman
Bug#964335: linux-headers-amd64: cannot upgrade to 5.7.6-1
Package: linux-headers-amd64
Version: 5.6.14-2
Severity: serious
Try to upgrade linux-headers-amd64, linux-image-amd64 and linux-perf to
version 5.7.6-1 results in the following errors:
Preparing to unpack .../15-linux-headers-amd64_5.7.6-1_amd64.deb ...
dpkg-maintscript-helper: error: file
'/usr/share/doc/linux-headers-amd64/copyright' not owned by package
'linux-headers-amd64'
dpkg-maintscript-helper: error: file
'/usr/share/doc/linux-headers-amd64/changelog.gz' not owned by package
'linux-headers-amd64'
dpkg-maintscript-helper: error: directory
'/usr/share/doc/linux-headers-amd64' contains files not owned by package
linux-headers-amd64, cannot switch to symlink
dpkg: error processing archive
/tmp/apt-dpkg-install-zTcKDN/15-linux-headers-amd64_5.7.6-1_amd64.deb
(--unpack):
new linux-headers-amd64 package pre-installation script subprocess
returned error exit status 1
Preparing to unpack .../16-linux-image-amd64_5.7.6-1_amd64.deb ...
dpkg-maintscript-helper: error: file
'/usr/share/doc/linux-image-amd64/NEWS.Debian.gz' not owned by package
'linux-image-amd64'
dpkg-maintscript-helper: error: file
'/usr/share/doc/linux-image-amd64/copyright' not owned by package
'linux-image-amd64'
dpkg-maintscript-helper: error: file
'/usr/share/doc/linux-image-amd64/changelog.gz' not owned by package
'linux-image-amd64'
dpkg-maintscript-helper: error: directory
'/usr/share/doc/linux-image-amd64' contains files not owned by package
linux-image-amd64, cannot switch to symlink
dpkg: error processing archive
/tmp/apt-dpkg-install-zTcKDN/16-linux-image-amd64_5.7.6-1_amd64.deb (--unpack):
new linux-image-amd64 package pre-installation script subprocess returned
error exit status 1
Preparing to unpack .../17-linux-perf_5.7.6-1_amd64.deb ...
dpkg-maintscript-helper: error: file '/usr/share/doc/linux-perf/copyright'
not owned by package 'linux-perf'
dpkg-maintscript-helper: error: file
'/usr/share/doc/linux-perf/changelog.gz' not owned by package 'linux-perf'
dpkg-maintscript-helper: error: directory '/usr/share/doc/linux-perf'
contains files not owned by package linux-perf, cannot switch to symlink
dpkg: error processing archive
/tmp/apt-dpkg-install-zTcKDN/17-linux-perf_5.7.6-1_amd64.deb (--unpack):
new linux-perf package pre-installation script subprocess returned error
exit status 1
Note that the dependencies linux-headers-5.7.0-1-{amd64,common},
linux-image-5.7.0-1-amd64, linux-perf-5.7 have all been upgrade to
5.7.6-1, it's only the versionless one that fail.
(I'm not sure how to tag this as also affecting the linux-image-amd64 and
linux-perf packages, sorry.)
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-headers-amd64 depends on:
ii linux-headers-5.6.0-2-amd64 5.6.14-2
linux-headers-amd64 recommends no packages.
linux-headers-amd64 suggests no packages.
-- no debconf information
Processed: severity of 922396 is serious
Processing commands for cont...@bugs.debian.org: > severity 922396 serious Bug #922396 [webext-noscript] webext-noscript: version out of date -- does not work with current Firefox Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 922396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954080: marked as done (tbsync: broken by new thunderbird, please prepare new version for stable-updates)
Your message dated Sun, 5 Jul 2020 21:16:46 +0300 with message-id <20200705181646.GA5923@localhost> and subject line Re: Bug#954080: tbsync: broken by new thunderbird, please prepare new version for stable-updates has caused the Debian Bug report #954080, regarding tbsync: broken by new thunderbird, please prepare new version for stable-updates 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.) -- 954080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tbsync Version: 1.7-1 Severity: important Hi Mechthilde, it looks like the current tbsync in buster is not directly usable anymore, after thunderbird has been upgraded from 60.x to 68.x. I assume, that just using a newer version in stable might work, but I didn't try yet. First, I just downgraded thunderbird, lightning, and enigmail to their original buster versions: thunderbird 60.9.0-1~deb10u1 lightning 60.9.0-1~deb10u1 enigmail 2.0.12+ds1-1~deb10u1 This works and might be a good workaround for most users. Second, I did an adhoc, local backport of tbsync. This works with the latest thunderbird in buster, as expected. Cheers & stay healthy! --- End Message --- --- Begin Message --- Version: 2.11-1 tbsync (2.11-1~deb10u1) buster; urgency=medium * Built for Buster -- Mechtilde Stehmann Sun, 26 Apr 2020 22:31:26 +0200--- End Message ---
Processed: severity of 954080 is serious
Processing commands for cont...@bugs.debian.org: > severity 954080 serious Bug #954080 [src:tbsync] tbsync: broken by new thunderbird, please prepare new version for stable-updates Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 954080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: xul-ext-exteditor <= 1.0.3-1 is not working or installable with Thunderbird 68
Processing control commands: > fixed -1 2.0.2-1~exp1 Bug #964329 [xul-ext-exteditor] xul-ext-exteditor <= 1.0.3-1 is not working or installable with Thunderbird 68 Marked as fixed in versions xul-ext-exteditor/2.0.2-1~exp1. -- 964329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964329: xul-ext-exteditor <= 1.0.3-1 is not working or installable with Thunderbird 68
Package: xul-ext-exteditor Version: 1.0.0-1 Severity: serious Control: fixed -1 2.0.2-1~exp1 The version in stable must be updated to the version in unstable.
Bug#964327: src:docker-systemctl-replacement: fails to migrate to testing for too long: unresolved RC bug
Source: docker-systemctl-replacement Version: 1.4.4147-1 Severity: serious Control: close -1 1.4.4181-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 959828 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:docker-systemctl-replacement in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=docker-systemctl-replacement signature.asc Description: OpenPGP digital signature
Processed: src:docker-systemctl-replacement: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 1.4.4181-1
Bug #964327 [src:docker-systemctl-replacement]
src:docker-systemctl-replacement: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions docker-systemctl-replacement/1.4.4181-1.
Bug #964327 [src:docker-systemctl-replacement]
src:docker-systemctl-replacement: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
> block -1 by 959828
Bug #964327 {Done: Paul Gevers }
[src:docker-systemctl-replacement] src:docker-systemctl-replacement: fails to
migrate to testing for too long: unresolved RC bug
964327 was not blocked by any bugs.
964327 was not blocking any bugs.
Added blocking bug(s) of 964327: 959828
--
964327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-javascript-devel] Bug#963425: node-terser: FTBFS: ERROR: `m` is not a supported option
Processing control commands: > tags -1 + patch Bug #963425 [node-commander] node-terser: FTBFS: ERROR: `m` is not a supported option Added tag(s) patch. -- 963425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963425: [Pkg-javascript-devel] Bug#963425: node-terser: FTBFS: ERROR: `m` is not a supported option
Control: tags -1 + patch
Le 05/07/2020 à 16:47, Jonas Smedegaard a écrit :
> Control: reassign -1 node-commander 4.1.1-1
> Control: affects -1 uglifyjs.terser
>
> Quoting Lucas Nussbaum (2020-06-21 22:24:18)
>> Source: node-terser
>> Version: 4.1.2-6
>> Severity: serious
>> Justification: FTBFS on amd64
>> Tags: bullseye sid ftbfs
>> Usertags: ftbfs-20200620 ftbfs-bullseye
>>
>> Hi,
>>
>> During a rebuild of all packages in sid, your package failed to build
>> on amd64.
>
> Thanks, Lucas.
>
> These errors are caused by node-commander upgrade to new major release
> without proper testing reverse dependencies.
Hi,
it was tested but test reports just a warning and build succeeded
locally. Here is the fix (I can't push an MR since MR are disabled in
this salsa repo!). However I pushed a branch named commander-4 with this
patch:
--- a/bin/uglifyjs
+++ b/bin/uglifyjs
@@ -28,6 +28,15 @@
program.version(info.name + " " + info.version);
program.parseArgv = program.parse;
program.parse = undefined;
+var argv = [];
+process.argv.forEach(function(arg){
+ if(arg.match(/^-([pcmbode]+)$/)) {
+argv = argv.concat(RegExp.$1.split('').map(s => { return '-'+s }));
+ }
+ else argv.push(arg);
+});
+process.argv = argv;
+
if (process.argv.includes("ast")) program.helpInformation = describe_ast;
else if (process.argv.includes("options")) program.helpInformation =
function() {
var text = [];
Bug#963425: marked as pending in node-terser
Control: tag -1 pending Hello, Bug #963425 in node-terser 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/js-team/node-terser/-/commit/f51cc5e36920dd79b1c1f01b58258d12644421f4 Add support for node-commander ≥ 4 Closes: #963425 (this message was generated automatically) -- Greetings https://bugs.debian.org/963425
Processed: Bug#963425 marked as pending in node-terser
Processing control commands: > tag -1 pending Bug #963425 [node-commander] node-terser: FTBFS: ERROR: `m` is not a supported option Added tag(s) pending. -- 963425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964136: [Debian-iot-maintainers] Bug#964136: glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el
> > I was able to whip up the attatched patch which partially splits the > arch dependent and independent > builds (an arch only build now only builds the arch stuff but an indep > only build still builds > everything) and do a succesfull arch only build on armel. > Thanks a lot Peter, I was almost there with my fix as well, you beat me. Mine was similar except for the override_dh_auto_build-indep in d/rules. I'll use this override command instead of my if [ -x "/usr/bin/webpack" ] in override_dh_auto_build
Bug#962550: libgclib breaks gffread autopkgtest: Segmentation fault
Control: reassign -1 libgclib1 0.11.9-1
Control: retitle -1 libgclib1: ABI break without soname change
Control: affects -1 src:libgclib src:gffread
On Tue, Jun 09, 2020 at 09:25:27PM +0200, Paul Gevers wrote:
>...
> line 109: 8435 Segmentation fault gffread ${gff} > /dev/null
>...
#0 0x5556e8a8 in GHash >::DefaultFreeProc (
item=0x) at /usr/include/gclib/GHash.hh:60
#1 0x77f4276f in GHash >::Clear (this=)
at GHash.hh:575
#2 GffReader::readAll (this=0x55590a40) at gff.cpp:1828
#3 0x5556a9d6 in GffLoader::load (this=0x5557b180 ,
seqdata=...,
gf_validate=0xa83c *)>,
gf_parsecomment=0xa56a )
at gff_utils.cpp:695
#4 0xc620 in main (argc=2, argv=0x7fffe698)
at gffread.cpp:1271
The root cause is that libgclib changed ABI without changing soname.
cu
Adrian
Processed: Re: Bug#962550: libgclib breaks gffread autopkgtest: Segmentation fault
Processing control commands: > reassign -1 libgclib1 0.11.9-1 Bug #962550 [src:libgclib, src:gffread] libgclib breaks gffread autopkgtest: Segmentation fault Bug reassigned from package 'src:libgclib, src:gffread' to 'libgclib1'. No longer marked as found in versions gffread/0.11.8-1 and libgclib/0.11.9-1. Ignoring request to alter fixed versions of bug #962550 to the same values previously set Bug #962550 [libgclib1] libgclib breaks gffread autopkgtest: Segmentation fault Marked as found in versions libgclib/0.11.9-1. > retitle -1 libgclib1: ABI break without soname change Bug #962550 [libgclib1] libgclib breaks gffread autopkgtest: Segmentation fault Changed Bug title to 'libgclib1: ABI break without soname change' from 'libgclib breaks gffread autopkgtest: Segmentation fault'. > affects -1 src:libgclib src:gffread Bug #962550 [libgclib1] libgclib1: ABI break without soname change Added indication that 962550 affects src:libgclib and src:gffread -- 962550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr
Processing control commands: > reassign -1 src:gff2aplot Bug #962553 [src:gffread] gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr Bug reassigned from package 'src:gffread' to 'src:gff2aplot'. No longer marked as found in versions gffread/0.11.8-1. Ignoring request to alter fixed versions of bug #962553 to the same values previously set > close -1 2.0-13 Bug #962553 [src:gff2aplot] gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr Marked as fixed in versions gff2aplot/2.0-13. Bug #962553 [src:gff2aplot] gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr Marked Bug as done -- 962553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr
Control: reassign -1 src:gff2aplot
Control: close -1 2.0-13
On Wed, Jun 17, 2020 at 05:39:43PM +0200, Graham Inggs wrote:
> Control: reopen -1
>
> Now it fails in a different way:
>
> autopkgtest [11:10:15]: test run-tests: - - - - - - - - - - results -
> - - - - - - - - -
> run-testsFAIL stderr:
> /tmp/autopkgtest-lxc.cerfkec6/downtmp/build.2n1/src/debian/tests/run-tests:
> line 109: 8512 Segmentation fault gffread ${gff} > /dev/null
> autopkgtest [11:10:15]: test run-tests: - - - - - - - - - - stderr -
> - - - - - - - - -
> /tmp/autopkgtest-lxc.cerfkec6/downtmp/build.2n1/src/debian/tests/run-tests:
> line 109: 8512 Segmentation fault gffread ${gff} > /dev/null
> /tmp/autopkgtest-lxc.cerfkec6/downtmp/build.2n1/src/debian/tests/run-tests:
> line 109: 8514 Segmentation fault gffread ${gff} > /dev/null
This is #962550.
cu
Adrian
Processed: re: glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el
Processing commands for cont...@bugs.debian.org: > Retitle 964136 glewlwyd build-depedencies unsatisfiable on armel Bug #964136 [glewlwyd] glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el Changed Bug title to 'glewlwyd build-depedencies unsatisfiable on armel' from 'glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el'. > Thanks Stopping processing here. Please contact me if you need assistance. -- 964136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964136: glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el
Retitle 964136 glewlwyd build-depedencies unsatisfiable on armel Thanks Build has been fixed for mipsel and mips64el Thanks, retitling the bug report for the remaining issue. but it remains impossible on armel since nodejs isn't available on this platform. The thing is nodejs is used during package build only, to transpile the reactjs front-end single-page-application. Then the result is the same for all architecture. If we could separate the backend build (architecture: any) and the frontend build (architecture: all), we might have Glewlwyd available for armel, alpha, ia64, m68k, ppc64, riscv64, sh4, sparc64 and x32. I was able to whip up the attatched patch which partially splits the arch dependent and independent builds (an arch only build now only builds the arch stuff but an indep only build still builds everything) and do a succesfull arch only build on armel. I am not planning to NMU this as I do not feel that I am in a position to properly test the resulting packages. diff -Nru glewlwyd-2.3.1/debian/changelog glewlwyd-2.3.1/debian/changelog --- glewlwyd-2.3.1/debian/changelog 2020-06-26 11:58:19.0 + +++ glewlwyd-2.3.1/debian/changelog 2020-07-04 23:10:28.0 + @@ -1,3 +1,10 @@ +glewlwyd (2.3.1-2.1) UNRELEASED; urgency=medium + + * Patch proposed to BTS + * Split architecture dependent and independent builds. + + -- Peter Michael Green Sat, 04 Jul 2020 23:10:28 + + glewlwyd (2.3.1-2) unstable; urgency=medium * Upload to unstable diff -Nru glewlwyd-2.3.1/debian/control glewlwyd-2.3.1/debian/control --- glewlwyd-2.3.1/debian/control 2020-06-26 11:58:19.0 + +++ glewlwyd-2.3.1/debian/control 2020-07-04 22:45:49.0 + @@ -25,8 +25,9 @@ , liboath-dev , libcbor-dev , cmake -# Front-end dependencies - , npm +Build-Depends-Indep: +# Frontend Dependencies + npm , nodejs , node-react , node-babel7 diff -Nru glewlwyd-2.3.1/debian/rules glewlwyd-2.3.1/debian/rules --- glewlwyd-2.3.1/debian/rules 2020-06-26 11:58:19.0 + +++ glewlwyd-2.3.1/debian/rules 2020-07-04 23:10:28.0 + @@ -20,8 +20,10 @@ dh_auto_configure -- $(ARGS) \ -DSKIP_BUILD_RPATH=TRUE -override_dh_auto_build: - # Build backend +override_dh_auto_build-indep: + #apparently the frontend build does depend on some compiled stuff + #so we need to run the compile process even if we are only building + #arch all. dh_auto_build -- # Build webapp cp -RL /usr/share/nodejs webapp-src/node_modules || true
Bug#963871: emacs-websocket: FTBFS without external DNS
Hi Niko, On Sun, 28 Jun 2020 at 09:06, Niko Tyni wrote: > > Source: emacs-websocket > Version: 1.12+8.g31e122a-1 > Severity: serious > Tags: ftbfs > > This package fails to build when DNS lookups are not available. > Thank you for the reminder to solve this. I've had a solution for the ftbfs on my local devel branch for some time, but I haven't merged and uploaded it, because it just skips the test...and of course it's better to find a proper solution for enabling functional tests when a network isn't available. Upstream and I are discussing Tornado and Autobahn. From what I've gathered Autobahn is the gold standard, and Tornado validates against Autobahn, so Tornado would provide 2nd-degree quality validation--which is probably good enough, no? After choosing a server to validate against I'm thinking that the fix will look like an alternate branch in the Emacs test. That branch is taken when a variable is set (elisp style boolean, but probably type string so it can also function as a URL for the server, and that variable will be set in dh_elpa_test config. Please feel free to periodically remind me to fix this. Worse-case scenario I'll skip the test and trust that all is well so long as elpa-atomic-chrome works correctly. That said, it's an excellent opportunity to be a proactive downstream! Regards, Nicholas
Bug#964321: prometheus FTBFS on 32bit: FAIL: TestHeadReadWriter_WriteChunk_Chunk_IterateChunks
Source: prometheus Version: 2.18.2+ds-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=prometheus=sid ... --- FAIL: TestHeadReadWriter_WriteChunk_Chunk_IterateChunks (0.31s) panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1260c] goroutine 22 [running]: testing.tRunner.func1.1(0x2a5cf8, 0x505278) /usr/lib/go-1.14/src/testing/testing.go:940 +0x25c testing.tRunner.func1(0x14ec1e0) /usr/lib/go-1.14/src/testing/testing.go:943 +0x364 panic(0x2a5cf8, 0x505278) /usr/lib/go-1.14/src/runtime/panic.go:969 +0x118 runtime/internal/atomic.goStore64(0x14fa0cc, 0x8, 0x0) /usr/lib/go-1.14/src/runtime/internal/atomic/atomic_arm.go:144 +0x1c github.com/prometheus/prometheus/tsdb/chunks.(*ChunkDiskMapper).cut(0x14fa0b0, 0x1, 0x0, 0x0, 0x0) /<>/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks.go:356 +0x100 github.com/prometheus/prometheus/tsdb/chunks.(*ChunkDiskMapper).WriteChunk(0x14fa0b0, 0x7fcfd52, 0x4d658221, 0x1, 0x0, 0x3e8, 0x0, 0x34a938, 0x14b02c0, 0x0, ...) /<>/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks.go:260 +0xdc github.com/prometheus/prometheus/tsdb/chunks.createChunk(0x14ec1e0, 0x0, 0x14fa0b0, 0x3ef65c62, 0x40, 0x66, 0x1cbdc, 0x71, 0x16e969, 0x2633ef, ...) /<>/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:272 +0xbc github.com/prometheus/prometheus/tsdb/chunks.TestHeadReadWriter_WriteChunk_Chunk_IterateChunks(0x14ec1e0) /<>/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:51 +0x198 testing.tRunner(0x14ec1e0, 0x2f4728) /usr/lib/go-1.14/src/testing/testing.go:991 +0xbc created by testing.(*T).Run /usr/lib/go-1.14/src/testing/testing.go:1042 +0x2b0 FAILgithub.com/prometheus/prometheus/tsdb/chunks0.450s ... Upstream version 2.19.2 seems to build.
Bug#936805: kodi: Python2 removal in sid/bullseye
Hi Nicholas! I joined Debian to package Kodi 19.0 and full archive of binary addons and I already made a significant progress on the way: 1. The build dependencies for kodi not present in Debian at the moment of my join included: - dav1d (accepted to unstable 2 days ago, maintained by Dylan Aissi), - libudfread (awaiting approval from FTP team, maintained by me), - shairplay (awaiting approval from FTP team, maintained by me) So far, after libudfread & shairplay are accepted into unstable, we'll have all dependencies within Debian. 2. The build dependencies requiring additional work were fixed: - flatbuffers (1.11.0 fixed, waiting for upstream to tag 1.12.1 closing GCC-10 build failures) - libcdio (libcdio++ / libiso9660++ added, waiting for Gabriel T. Gomez to upload the package to unstable), - libsrt (patches proposed for review) 3. The unofficial binary repository targeting buster-backports/amd64 has been published on https://basilgello.github.io/kodi-nightly-debian-repo containing no-change rebuilds of kodi build dependencies, kodi itself and binary addons gradually added as prepared. The accompanying source code is hosted on Salsa: https://salsa.debian.org/basilgello-guest 4. After Kodi upstream declares the EOL of 18.x "Leia" branch, the repositories will be pushed to multimedia team's space and on release, the whole set will be uploaded to unstable. Uploading to experimental was considered excessive by Balint Reczey as every build occupies 4GB of Debian snapshot server space forever on. On Sun, 5 Jul 2020 11:48:39 -0400 Nicholas D Steeves wrote: > Hi, > > On Fri, Aug 30, 2019 at 07:22:18AM +, Matthias Klose wrote: > > Package: src:kodi > > Version: 2:17.6+dfsg1-4 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > > > [snip] > > This bug will be solved when updating to Kodi ≥ 19, which prominently > declares it migrated to Python 3. Of course some plugins might not be > py3 ready, so it's probably time to stage the kodi-without-py2 > packages in experimental and report bugs upstream. > > The Python Team is moving ahead with making at py2 dep RC for low > popcon leaf packages this week, and while there isn't a roadmap > (afaik), I suspect this bug will become serious this fall (2020). > > Thanks, > Nicholas -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 signature.asc Description: PGP signature
Bug#936805: kodi: Python2 removal in sid/bullseye
A few people are already working on kodi 19, and packages will start to appear in a few days in experimental. Actually there are related packages in NEW: dav1d was accepted a couple days ago, shairplay and libudfread. They are not compulsory dependencies, so not strictly blocking, but they were uploaded for kodi to link against them. On Sun, 5 Jul 2020, 5:51 pm Nicholas D Steeves, wrote: > Hi, > > On Fri, Aug 30, 2019 at 07:22:18AM +, Matthias Klose wrote: > > Package: src:kodi > > Version: 2:17.6+dfsg1-4 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > > > [snip] > > This bug will be solved when updating to Kodi ≥ 19, which prominently > declares it migrated to Python 3. Of course some plugins might not be > py3 ready, so it's probably time to stage the kodi-without-py2 > packages in experimental and report bugs upstream. > > The Python Team is moving ahead with making at py2 dep RC for low > popcon leaf packages this week, and while there isn't a roadmap > (afaik), I suspect this bug will become serious this fall (2020). > > Thanks, > Nicholas >
Bug#936805: kodi: Python2 removal in sid/bullseye
Hi, On Fri, Aug 30, 2019 at 07:22:18AM +, Matthias Klose wrote: > Package: src:kodi > Version: 2:17.6+dfsg1-4 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. > [snip] This bug will be solved when updating to Kodi ≥ 19, which prominently declares it migrated to Python 3. Of course some plugins might not be py3 ready, so it's probably time to stage the kodi-without-py2 packages in experimental and report bugs upstream. The Python Team is moving ahead with making at py2 dep RC for low popcon leaf packages this week, and while there isn't a roadmap (afaik), I suspect this bug will become serious this fall (2020). Thanks, Nicholas signature.asc Description: PGP signature
Bug#963425: node-terser: FTBFS: ERROR: `m` is not a supported option
Control: reassign -1 node-commander 4.1.1-1 Control: affects -1 uglifyjs.terser Quoting Lucas Nussbaum (2020-06-21 22:24:18) > Source: node-terser > Version: 4.1.2-6 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200620 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks, Lucas. These errors are caused by node-commander upgrade to new major release without proper testing reverse dependencies. > > 231 passing (12s) > > 4 pending > > 7 failing > > > > 1) bin/uglifyjs (2) > >Should dump AST as JSON: > > Uncaught Command failed: "/usr/bin/node" bin/uglifyjs > > test/input/global_defs/simple.js -mco ast > > ERROR: ENOENT: no such file or directory, open 'ast' > > at Object.openSync (fs.js:458:3) > > at Object.readFileSync (fs.js:360:35) > > at read_file (/<>/bin/uglifyjs:353:19) > > at /<>/bin/uglifyjs:176:37 > > at Array.forEach () > > at Object. (/<>/bin/uglifyjs:175:28) > > at Module._compile (internal/modules/cjs/loader.js:1138:30) > > at Object.Module._extensions..js > > (internal/modules/cjs/loader.js:1158:10) > > at Module.load (internal/modules/cjs/loader.js:986:32) > > at Function.Module._load (internal/modules/cjs/loader.js:879:14) > > > > Error: Command failed: "/usr/bin/node" bin/uglifyjs > > test/input/global_defs/simple.js -mco ast > > ERROR: ENOENT: no such file or directory, open 'ast' > > at Object.openSync (fs.js:458:3) > > at Object.readFileSync (fs.js:360:35) > > at read_file (bin/uglifyjs:353:19) > > at /<>/bin/uglifyjs:176:37 > > at Array.forEach () > > at Object. (bin/uglifyjs:175:28) > > at Module._compile (internal/modules/cjs/loader.js:1138:30) > > at Object.Module._extensions..js > > (internal/modules/cjs/loader.js:1158:10) > > at Module.load (internal/modules/cjs/loader.js:986:32) > > at Function.Module._load (internal/modules/cjs/loader.js:879:14) > > > > at ChildProcess.exithandler (child_process.js:303:12) > > at maybeClose (internal/child_process.js:1021:16) > > at Process.ChildProcess._handle.onexit > > (internal/child_process.js:286:5) > > > > 2) bin/uglifyjs (2) > >Should mangle toplevel names with the --module option: > > Uncaught Command failed: "/usr/bin/node" bin/uglifyjs > > test/input/module/input.js --module -mc > > Supported options: > > cachenull > > eval false > > ie8 false > > keep_classnames false > > keep_fnames false > > module false > > properties false > > reserved [] > > safari10 false > > toplevel false > > ERROR: `c` is not a supported option > > at o (/<>/dist/bundle.min.js:1:551) > > at Object.Kn [as minify] (/<>/dist/bundle.min.js:1:314384) > > at run (/<>/bin/uglifyjs:228:27) > > at Object. (/<>/bin/uglifyjs:178:5) > > at Module._compile (internal/modules/cjs/loader.js:1138:30) > > at Object.Module._extensions..js > > (internal/modules/cjs/loader.js:1158:10) > > at Module.load (internal/modules/cjs/loader.js:986:32) > > at Function.Module._load (internal/modules/cjs/loader.js:879:14) > > at Function.executeUserEntryPoint [as runMain] > > (internal/modules/run_main.js:71:12) > > at internal/main/run_main_module.js:17:47 > > > > Error: Command failed: "/usr/bin/node" bin/uglifyjs > > test/input/module/input.js --module -mc > > Supported options: > > cachenull > > eval false > > ie8 false > > keep_classnames false > > keep_fnames false > > module false > > properties false > > reserved [] > > safari10 false > > toplevel false > > ERROR: `c` is not a supported option > > at o (dist/bundle.min.js:1:551) > > at Object.Kn [as minify] (dist/bundle.min.js:1:314384) > > at run (bin/uglifyjs:228:27) > > at Object. (bin/uglifyjs:178:5) > > at Module._compile (internal/modules/cjs/loader.js:1138:30) > > at Object.Module._extensions..js > > (internal/modules/cjs/loader.js:1158:10) > > at Module.load (internal/modules/cjs/loader.js:986:32) > > at Function.Module._load (internal/modules/cjs/loader.js:879:14) > > at Function.executeUserEntryPoint [as runMain] > > (internal/modules/run_main.js:71:12) > > at internal/main/run_main_module.js:17:47 > > > > at ChildProcess.exithandler (child_process.js:303:12) > > at maybeClose (internal/child_process.js:1021:16) > > at Process.ChildProcess._handle.onexit > > (internal/child_process.js:286:5) > > > > 3) bin/uglifyjs > >Should process inline source map: > > Uncaught Command failed: "/usr/bin/node" bin/uglifyjs > > test/input/issue-520/input.js -mc toplevel --source-map
Processed: Re: Bug#963425: node-terser: FTBFS: ERROR: `m` is not a supported option
Processing control commands: > reassign -1 node-commander 4.1.1-1 Bug #963425 [src:node-terser] node-terser: FTBFS: ERROR: `m` is not a supported option Bug reassigned from package 'src:node-terser' to 'node-commander'. No longer marked as found in versions node-terser/4.1.2-6. Ignoring request to alter fixed versions of bug #963425 to the same values previously set Bug #963425 [node-commander] node-terser: FTBFS: ERROR: `m` is not a supported option Marked as found in versions node-commander/4.1.1-1. > affects -1 uglifyjs.terser Bug #963425 [node-commander] node-terser: FTBFS: ERROR: `m` is not a supported option Added indication that 963425 affects uglifyjs.terser -- 963425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964147: freerdp2-x11: xfreerdp fails with symbol lookup error
Control: retitle -1 enforce same version for installed freerdp2 bin:pkgs Control: severity -1 normal Hi, On Do 02 Jul 2020 22:22:34 CEST, Michael Meier wrote: On 02.07.20 10:06, Michael Meier wrote: Package: freerdp2-x11 Version: 2.1.2+dfsg1-1 Severity: grave Justification: renders package unusable I've just updated xfreerdp. The new versions can't be executed.it fails with: xfreerdp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libfreerdp- client2.so.2: undefined symbol: msusb_msconfig_write The previous version i used: 2.0.0~git20190204.1.2693389a+dfsg1-2~bpo10+1 worked well. Propably some library version dependency which isn't correctly stated in the .deb package? so after some trying out I've foudn out that I've also had to update: libfreerdp-client2-2:amd64 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u1 -> 2.1.2+dfsg1-2 then it works. The version dependency seems to be wrong somewhere... You obviously have a half-broken setup as you seem to mix buster-backports packages and packages from unstable. This may well fail for several reasons. On the other hand, it might be sensible to enforce all freerdp2 bin:pkgs to be from the same version / build. This, I think we should enforce this via debian/control. Will look into this, but with downgraded severity. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpk3B2QKugqO.pgp Description: Digitale PGP-Signatur
Bug#964315: openms FTBFS on mipsel: cc1plus: out of memory
Source: openms Version: 2.5.0+cleaned1-2 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/logs.php?pkg=openms=mipsel ... cc1plus: out of memory allocating 1087972 bytes after a total of 105656320 bytes make[5]: *** [src/openms/CMakeFiles/OpenMS.dir/build.make:5266: src/openms/CMakeFiles/OpenMS.dir/source/ANALYSIS/ID/BayesianProteinInferenceAlgorithm.cpp.o] Error 1 Fix/Workaround: --- debian/rules.old2020-06-15 11:37:20.260388067 + +++ debian/rules2020-06-15 11:40:03.151168244 + @@ -33,6 +33,11 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 +ifneq (,$(filter $(DEB_HOST_ARCH), mipsel)) + export DEB_CXXFLAGS_MAINT_APPEND += -g1 +endif + + %: dh $@ --buildsystem=cmake --no-parallel
Bug#963346: marked as pending in golang-github-openshift-api
Control: tag -1 pending Hello, Bug #963346 in golang-github-openshift-api 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/go-team/packages/golang-github-openshift-api/-/commit/af4722b98b0504ca5e60007c1ab24aade60d6a28 Add build depends on golang-gopkg-yaml.v2-dev Fixes FTBFS Closes: #963346 (this message was generated automatically) -- Greetings https://bugs.debian.org/963346
Processed: Bug#963346 marked as pending in golang-github-openshift-api
Processing control commands: > tag -1 pending Bug #963346 [src:golang-github-openshift-api] golang-github-openshift-api: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/openshift/api github.com/openshift/api/annotations github.com/openshift/api/apps github.com/openshift/api/apps/v1 github.com/openshift/api/authorization github.com/openshift/api/authorization/v1 github.com/openshift/api/build github.com/openshift/api/build/v1 github.com/openshift/api/config github.com/openshift/api/config/v1 github.com/openshift/api/image github.com/openshift/api/image/docker10 github.com/openshift/api/image/dockerpre012 github.com/openshift/api/image/v1 github.com/openshift/api/kubecontrolplane github.com/openshift/api/kubecontrolplane/v1 github.com/openshift/api/legacyconfig/v1 github.com/openshift/api/network github.com/openshift/api/network/v1 github.com/openshift/api/oauth github.com/openshift/api/oauth/v1 github.com/openshift/api/openshiftcontrolplane github.com/openshift/api/openshiftcontrolplane/v1 github.com/openshift/api/operator github.com/openshift/api/operator/v1 github.com/openshift/api/operator/v1alpha1 github.com/openshift/api/osin github.com/openshift/api/osin/v1 github.com/openshift/api/pkg/serialization github.com/openshift/api/project github.com/openshift/api/project/v1 github.com/openshift/api/quota github.com/openshift/api/quota/v1 github.com/openshift/api/route github.com/openshift/api/route/v1 github.com/openshift/api/security github.com/openshift/api/security/v1 github.com/openshift/api/servicecertsigner github.com/openshift/api/servicecertsigner/v1alpha1 github.com/openshift/api/template github.com/openshift/api/template/v1 github.com/openshift/api/tools/genswaggertypedocs github.com/openshift/api/user github.com/openshift/api/user/v1 github.com/openshift/api/webconsole github.com/openshift/api/webconsole/v1 returned exit code 1 Added tag(s) pending. -- 963346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963060: marked as done (versions of nodejs dependencies not properly documented)
Your message dated Sun, 05 Jul 2020 13:18:46 +
with message-id
and subject line Bug#963060: fixed in node-expat 2.3.18+ds-1
has caused the Debian Bug report #963060,
regarding versions of nodejs dependencies not properly documented
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.)
--
963060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-iconv
Version: 1.19.0-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs src:node-body-parser
Control: affects -1 src:node-client-sessions src:node-express
[X-Debbugs-CC: debian...@lists.debian.org,
node-body-par...@packages.debian.org,
node-client-sessi...@packages.debian.org, node-expr...@packages.debian.org]
Dear maintainer(s),
With a recent upload of nodejs the autopkgtest of node-body-parser fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
nodejs from testing12.18.0~dfsg-3
node-body-parser from testing1.19.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. As a nodejs
non-expert, it seems to me that the version of node-iconv in testing is
not compatible with the version of src:nodejs in unstable, but the
package dependencies don't reflect that in any way. Looking at the error
message, it seems to me that nodejs has an internal versioning scheme
that should be exposed in the Debian control file. node-iconv is rebuilt
in unstable and now has a dependency on the new version of libnodejsX,
but an unversioned dependency on nodejs itself.
Ideally, to fix the current situation some binary from src:nodejs, I
think nodejs, needs to add a "Breaks: node-iconv << ", but unfortunately this shouldn't be done on binNMU versions,
so this breaks can only happen if node-iconv gets a new upload, but it
should be done in that case.
Currently this regression is blocking the migration of nodejs to testing
[1].
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
PS: there's probably more regressions (but not all) triggered by nodejs
caused by this, I'll add them as affected when I see them.
[1] https://qa.debian.org/excuses.php?package=nodejs
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-body-parser/5929967/log.gz
Launch debian/tests/pkg-js/test with sh -ex
+ mocha --require test/support/env --reporter spec --check-leaks --bail
test/
bodyParser()
1) "before all" hook for "should default to {}"
0 passing (51ms)
1 failing
1) bodyParser()
"before all" hook for "should default to {}":
Error: The module
'/usr/lib/x86_64-linux-gnu/nodejs/iconv/build/Release/iconv.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node
(internal/modules/cjs/loader.js:1188:18)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object.
(/usr/lib/x86_64-linux-gnu/nodejs/iconv/lib/iconv.js:30:14)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (/usr/share/nodejs/raw-body/index.js:17:13)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object.
(/usr/share/nodejs/body-parser/lib/read.js:15:15)
Bug#963459: marked as done (python-transitions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)
Your message dated Sun, 05 Jul 2020 12:48:39 +
with message-id
and subject line Bug#963459: fixed in python-transitions 0.8.2-1
has caused the Debian Bug report #963459,
regarding python-transitions: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8 returned exit code 13
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.)
--
963459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-transitions
Version: 0.8.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-transitions
> dpkg-buildpackage: info: source version 0.8.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Philipp Huebner
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> pybuild --clean --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: python3.8 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.8_transitions/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
> rm -rf .pybuild/
> find . -name \*.pyc -exec rm {} \;
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> rm -f -- debian/python3-transitions.substvars debian/files
> rm -fr -- debian/python3-transitions/ debian/tmp/
> find . \( \( \
> \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o
> -type f -a \
> \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
> \) -exec rm -f {} + \) -o \
> \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
> \)
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-transitions using existing
> ./python-transitions_0.8.1.orig.tar.gz
> dpkg-source: info: building python-transitions in
> python-transitions_0.8.1-1.debian.tar.xz
> dpkg-source: info: building python-transitions in
> python-transitions_0.8.1-1.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> pybuild --build --test-pytest -i python{version} -p 3.8
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> copying transitions/core.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> copying transitions/__init__.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> copying transitions/version.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions
> creating
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/diagrams_graphviz.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/__init__.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/diagrams_pygraphviz.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/locking.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying transitions/extensions/factory.py ->
> /<>/.pybuild/cpython3_3.8_transitions/build/transitions/extensions
> copying
Bug#964309: bsdmainutils: FTBFS because of missing libncurses-dev dependency
Package: bsdmainutils Version: 12.1.3 Severity: serious Justification: FTBFS Hello, bsdmainutils currently FTBFS because it is missing the libncurses-dev dependency, leading to ncal.c:46:10: fatal error: term.h: No such file or directory 46 | #include Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 bsdmainutils depends on: ii bsdutils 1:2.35.2-4 ii debianutils 4.9.1 ii libbsd0 0.10.0-1 ii libc62.30-8 ii libtinfo66.2-1 Versions of packages bsdmainutils recommends: ii bsdextrautils 2.35.2-4 Versions of packages bsdmainutils suggests: pn calendar pn vacation ii wamerican [wordlist] 2019.10.06-1 ii wfrench [wordlist]1.2.6-1 ii whois 5.5.6 -- no debconf information
Processed: closing 964144
Processing commands for cont...@bugs.debian.org: > close 964144 2.14.5+ds-3 Bug #964144 [src:ariba] ariba: spades is currently only available on amd64 Marked as fixed in versions ariba/2.14.5+ds-3. Bug #964144 [src:ariba] ariba: spades is currently only available on amd64 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 964144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964242: bsdmainutils: depends on non-existing version of bsdextrautils
On Sat, Jul 04, 2020 at 10:52:04AM +0200, Rene Engelhard wrote: > But that bsdextrautils (>= 2.35.2-7) doesn't exist: Yes, as already communicated we had to wait with the next util-linux upload until bsdmainutils made it out of NEW. Now that it has, Chris will upload as soon as he finds the time. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
Bug#964305: blender FTBFS on non-i386 32bit: BLI_STATIC_ASSERT(sizeof(struct Scene) == 6124) fails
Source: blender Version: 2.83.1+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=blender=sid ... In file included from /<>/obj-arm-linux-gnueabihf/source/blender/makesdna/intern/dna_verify.c:2: /<>/source/blender/blenlib/BLI_assert.h:102:37: error: static assertion failed: "DNA struct size verify" 102 | # define BLI_STATIC_ASSERT(a, msg) _Static_assert(a, msg); | ^~ /<>/obj-arm-linux-gnueabihf/source/blender/makesdna/intern/dna_verify.c:9269:1: note: in expansion of macro ‘BLI_STATIC_ASSERT’ 9269 | BLI_STATIC_ASSERT(sizeof(struct Scene) == 6124, "DNA struct size verify"); | ^ make[3]: *** [source/blender/makesdna/intern/CMakeFiles/bf_dna.dir/build.make:128: source/blender/makesdna/intern/CMakeFiles/bf_dna.dir/dna_verify.c.o] Error 1
Bug#938587: marked as done (sugar-etoys-activity: Python2 removal in sid/bullseye)
Your message dated Sun, 05 Jul 2020 10:50:34 + with message-id and subject line Bug#938587: fixed in sugar-etoys-activity 116-9 has caused the Debian Bug report #938587, regarding sugar-etoys-activity: Python2 removal in sid/bullseye 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.) -- 938587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sugar-etoys-activity Version: 116-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:sugar-etoys-activity If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: sugar-etoys-activity Source-Version: 116-9 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-etoys-activity, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-etoys-activity 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: Sun, 05 Jul 2020 12:37:20 +0200 Source: sugar-etoys-activity Architecture: source Version: 116-9 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 938587 Changes: sugar-etoys-activity (116-9) unstable; urgency=medium . * fix depend on python3 (not python); fix shebang to call python3 (not python); closes: bug#938587, thanks to Sandro Tosi and Adrian Bunk Checksums-Sha1: 1b708182406167ebbc71d41104493041080dfde5 2072 sugar-etoys-activity_116-9.dsc 7c06b4a83f5cb39addfa95c78a50eda159627e5a 5936 sugar-etoys-activity_116-9.debian.tar.xz ae0729e85de9b9b587529b57bb1340c3e05f50ee 10197 sugar-etoys-activity_116-9_amd64.buildinfo Checksums-Sha256: 6011b791991b553e8f4c83594c5e7ea87f3822e0bc5e614f781115c5d42f0081 2072 sugar-etoys-activity_116-9.dsc
Processed: Re: Bug#964147: freerdp2-x11: xfreerdp fails with symbol lookup error
Processing control commands: > retitle -1 enforce same version for installed freerdp2 bin:pkgs Bug #964147 [freerdp2-x11] freerdp2-x11: xfreerdp fails with symbol lookup error Changed Bug title to 'enforce same version for installed freerdp2 bin:pkgs' from 'freerdp2-x11: xfreerdp fails with symbol lookup error'. > severity -1 normal Bug #964147 [freerdp2-x11] enforce same version for installed freerdp2 bin:pkgs Severity set to 'normal' from 'grave' -- 964147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:m2crypto: fails to migrate to testing for too long: unfixed RC bug and maintainer built arch:all binaries
Processing control commands:
> close -1 0.35.2-2
Bug #964299 [src:m2crypto] src:m2crypto: fails to migrate to testing for too
long: unfixed RC bug and maintainer built arch:all binaries
Marked as fixed in versions m2crypto/0.35.2-2.
Bug #964299 [src:m2crypto] src:m2crypto: fails to migrate to testing for too
long: unfixed RC bug and maintainer built arch:all binaries
Marked Bug as done
> block -1 by 959947
Bug #964299 {Done: Paul Gevers } [src:m2crypto]
src:m2crypto: fails to migrate to testing for too long: unfixed RC bug and
maintainer built arch:all binaries
964299 was not blocked by any bugs.
964299 was not blocking any bugs.
Added blocking bug(s) of 964299: 959947
--
964299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964299: src:m2crypto: fails to migrate to testing for too long: unfixed RC bug and maintainer built arch:all binaries
Source: m2crypto Version: 0.31.0-9 Severity: serious Control: close -1 0.35.2-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 959947 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:m2crypto in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=m2crypto signature.asc Description: OpenPGP digital signature
Processed: retitle 964252 to libbluray: FTBFS if texlive is installed in non-minimal build environment
Processing commands for cont...@bugs.debian.org: > retitle 964252 libbluray: FTBFS if texlive is installed in non-minimal build > environment Bug #964252 [src:libbluray] Failure to build from source on buster Changed Bug title to 'libbluray: FTBFS if texlive is installed in non-minimal build environment' from 'Failure to build from source on buster'. > thanks Stopping processing here. Please contact me if you need assistance. -- 964252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952322: marked as done (javahelper: jh_manifest breaks on jar files with no manifest)
Your message dated Sun, 05 Jul 2020 10:03:40 +
with message-id
and subject line Bug#952370: fixed in javatools 0.74
has caused the Debian Bug report #952370,
regarding javahelper: jh_manifest breaks on jar files with no manifest
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.)
--
952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsaxon-java
Version: 1:6.5.5-12
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binary
> dh binary --with javahelper --with maven-repo-helper
>dh_testroot
>dh_prep
>dh_install
>mh_install
>jh_installjavadoc
>dh_installdocs
>dh_installchangelogs
>dh_installexamples
>dh_installman
>dh_lintian
>dh_perl
>dh_link
>jh_installlibs
>jh_classpath
>jh_manifest
> error: No member named $memberName
> at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
>
> Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x55e8dc67e1a0),
> "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
>
> main::update_jar("debian/libsaxon-java/usr/share/java/saxon-jdom-6.5.5.jar",
> undef) called at /usr/bin/jh_manifest line 209
> Could not read manifest from
> debian/libsaxon-java/usr/share/java/saxon-jdom-6.5.5.jar (2): at
> /usr/bin/jh_manifest line 298.
> make: *** [debian/rules:13: binary] Error 255
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/libsaxon-java_6.5.5-12_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: javatools
Source-Version: 0.74
Done: Emmanuel Bourg
We believe that the bug you reported is fixed in the latest version of
javatools, 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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated javatools 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: Sun, 05 Jul 2020 11:49:48 +0200
Source: javatools
Architecture: source
Version: 0.74
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Closes: 952370
Changes:
javatools (0.74) unstable; urgency=medium
.
* jh_manifest: Fix the error when the jar processed doesn't have a manifest
(Closes: #952370)
Checksums-Sha1:
57d1fb33c9748295a19564cce096733bc3695d8b 1892 javatools_0.74.dsc
327c6e8ea1e25ab9477ae3f93bd09fdda2382364 54584 javatools_0.74.tar.xz
46fda41aa8d00bb96561940476dfebc12519 10113 javatools_0.74_source.buildinfo
Checksums-Sha256:
046080749520eeaeb1fa91eed780ff4311b357853d79b739ccd01eaa8367729c 1892
javatools_0.74.dsc
e10c88d280b39372dda0f3c26db2480ad76643185f59d813010b590de674415b 54584
javatools_0.74.tar.xz
c17f27c91ee7a72d0deb69e090b80b36784513ebb98a8c2662fe07c1cc26f2ee 10113
javatools_0.74_source.buildinfo
Files:
251f90a737741d424bc22b7871f3e299 1892 java optional javatools_0.74.dsc
d8df36a6f13b6c3878660ab4e86c7c97 54584 java optional javatools_0.74.tar.xz
c92689ce729bf4bf3dd97d65d6867050 10113 java optional
javatools_0.74_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl8BoqgSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCstLMQAKi7yHP8y8M9LkaKg9jHTxFpHhfyB84S
/nqcFtib/p5FarH1PnBxkuAtHeUve/xiSn5DXCxsdzxU4Banxl7rdilkTtL+OSDz
CztPkimIyeJhO8zJAsdMl10kZK5xpIlrA7v52vcB4pfnSwnV4qgGe2+ZaAc9rwrA
P1m9A6puWyHX3/8fmkRUgcu945jknuHlFYWtFu3VNkK3k22RHA1hk+QNBLLEpRx/
BJ4vTS3CWngsulKeP9eYIoc9s2cwIhzU6GZJWCzsE7bB8zS6Ez8kY9CxuJrJOWd9
Bug#952289: marked as done (libquartz2-java: FTBFS: Could not read manifest from /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): at /usr/bin/jh_manifest line 298.)
Your message dated Sun, 05 Jul 2020 10:03:40 + with message-id and subject line Bug#952370: fixed in javatools 0.74 has caused the Debian Bug report #952370, regarding libquartz2-java: FTBFS: Could not read manifest from /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): at /usr/bin/jh_manifest line 298. 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.) -- 952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libquartz2-java Version: 2.3.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_install > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode > -Ddebian.dir=/<>/debian -Ddebian.package=libquartz2-java > -Dmaven.repo.local=/<>/debian/maven-repo -Dinstall.to.usj=true > org.debian.maven:debian-maven-plugin:2.4:install > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] quartz-parent > [pom] > [INFO] quartz-core > [jar] > [INFO] quartz-commonj > [jar] > [INFO] quartz-jobs > [jar] > [INFO] quartz-plugins > [jar] > [INFO] quartz > [jar] > [INFO] > [INFO] -< org.quartz-scheduler:quartz-parent > >- > [INFO] Building quartz-parent 2.3.0-SNAPSHOT > [1/6] > [INFO] [ pom > ]- > [INFO] > [INFO] --- debian-maven-plugin:2.4:install (default-cli) @ quartz-parent --- > [INFO] Cleaning pom file: /<>/pom.xml.save with options: > [INFO]--keep-pom-version --package=libquartz2-java > --has-package-version > [INFO]--rules=/<>/debian/maven.rules > [INFO]--ignore-rules=/<>/debian/maven.ignoreRules > [INFO]--published-rules=/<>/debian/maven.publishedRules > [INFO] > [INFO] -< org.quartz-scheduler.internal:quartz-core > >-- > [INFO] Building quartz-core 2.3.0-SNAPSHOT > [2/6] > [INFO] [ jar > ]- > [INFO] > [INFO] --- debian-maven-plugin:2.4:install (default-cli) @ quartz-core --- > [INFO] Cleaning pom file: /<>/quartz-core/pom.xml.save with > options: > [INFO]--keep-pom-version --package=libquartz2-java > --has-package-version > [INFO]--rules=/<>/debian/maven.rules > [INFO]--ignore-rules=/<>/debian/maven.ignoreRules > [INFO]--published-rules=/<>/debian/maven.publishedRules > [INFO] Install jar for quartz-core into /usr/share/java > [INFO] > [INFO] < org.quartz-scheduler.internal:quartz-commonj > > > [INFO] Building quartz-commonj 2.3.0-SNAPSHOT > [3/6] > [INFO] [ jar > ]- > [INFO] > [INFO] --- debian-maven-plugin:2.4:install (default-cli) @ quartz-commonj --- > [INFO] Cleaning pom file: /<>/quartz-commonj/pom.xml.save with
Bug#952370: marked as done (javahelper: jh_manifest breaks on jar files with no manifest)
Your message dated Sun, 05 Jul 2020 10:03:40 +
with message-id
and subject line Bug#952370: fixed in javatools 0.74
has caused the Debian Bug report #952370,
regarding javahelper: jh_manifest breaks on jar files with no manifest
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.)
--
952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tunnelx
Version: 20170928-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> uudecode -o debian/tunnelx.png debian/tunnelx.png.uu
> dh_install
> # listdir goes via hidden file to avoid race (#856257)
> set -e; for x in symbols tutorials; do \
> rm -f $x/listdir.txt; \
> ls $x | LC_ALL=C sort > $x/.listdir.txt; \
> mv $x/.listdir.txt $x/listdir.txt; \
> done
> jar uMf debian/tunnelx/usr/share/tunnelx/tunnelx.jar symbols/* tutorials/*
> make[1]: Leaving directory '/<>'
>jh_installjavadoc
>dh_installdocs
>dh_installchangelogs
>dh_installman
>dh_icons
>dh_perl
>dh_link
>jh_installlibs
>jh_classpath
>jh_manifest
> error: No member named $memberName
> at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
>
> Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x5572e4176000),
> "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
> main::update_jar("debian/tunnelx/usr/share/tunnelx/tunnelx.jar",
> Debian::Javahelper::Manifest=HASH(0x5572e41feec8)) called at
> /usr/bin/jh_manifest line 209
> Could not read manifest from debian/tunnelx/usr/share/tunnelx/tunnelx.jar
> (2): at /usr/bin/jh_manifest line 298.
> make: *** [debian/rules:8: binary] Error 255
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/tunnelx_20170928-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: javatools
Source-Version: 0.74
Done: Emmanuel Bourg
We believe that the bug you reported is fixed in the latest version of
javatools, 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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated javatools 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: Sun, 05 Jul 2020 11:49:48 +0200
Source: javatools
Architecture: source
Version: 0.74
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Closes: 952370
Changes:
javatools (0.74) unstable; urgency=medium
.
* jh_manifest: Fix the error when the jar processed doesn't have a manifest
(Closes: #952370)
Checksums-Sha1:
57d1fb33c9748295a19564cce096733bc3695d8b 1892 javatools_0.74.dsc
327c6e8ea1e25ab9477ae3f93bd09fdda2382364 54584 javatools_0.74.tar.xz
46fda41aa8d00bb96561940476dfebc12519 10113 javatools_0.74_source.buildinfo
Checksums-Sha256:
046080749520eeaeb1fa91eed780ff4311b357853d79b739ccd01eaa8367729c 1892
javatools_0.74.dsc
e10c88d280b39372dda0f3c26db2480ad76643185f59d813010b590de674415b 54584
javatools_0.74.tar.xz
c17f27c91ee7a72d0deb69e090b80b36784513ebb98a8c2662fe07c1cc26f2ee 10113
javatools_0.74_source.buildinfo
Files:
251f90a737741d424bc22b7871f3e299 1892 java optional javatools_0.74.dsc
d8df36a6f13b6c3878660ab4e86c7c97 54584 java optional javatools_0.74.tar.xz
c92689ce729bf4bf3dd97d65d6867050 10113 java optional
javatools_0.74_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl8BoqgSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCstLMQAKi7yHP8y8M9LkaKg9jHTxFpHhfyB84S
Bug#964261: marked as done (contains /usr/lib/libreoffice/share/gallery/shapes.* also in libreoffice-common since 7.0.x)
Your message dated Sun, 05 Jul 2020 10:04:05 + with message-id and subject line Bug#964261: fixed in openclipart 1:0.18+dfsg-18 has caused the Debian Bug report #964261, regarding contains /usr/lib/libreoffice/share/gallery/shapes.* also in libreoffice-common since 7.0.x 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.) -- 964261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-common Version: 1:7.0.0~rc1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi Rene, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libreoffice-common_1%3a7.0.0~rc1-1_all.deb ... Unpacking libreoffice-common (1:7.0.0~rc1-1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a7.0.0~rc1-1_all.deb (--unpack): trying to overwrite '/usr/lib/libreoffice/share/gallery/shapes.sdg', which is also in package openclipart-libreoffice 1:0.18+dfsg-17 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or directory rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or directory rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or directory rmdir: failed to remove '/var/lib/libreoffice': No such file or directory rmdir: failed to remove '/var/lib/libreoffice': No such file or directory Errors were encountered while processing: /var/cache/apt/archives/libreoffice-common_1%3a7.0.0~rc1-1_all.deb These three files are conflicting: usr/lib/libreoffice/share/gallery/shapes.sdg usr/lib/libreoffice/share/gallery/shapes.sdv usr/lib/libreoffice/share/gallery/shapes.thm openclipart-libreoffice will probably need updates as well to no longer ship these files (or rename them), it's probably easiest if you fix and upload that QA maintained package, too. cheers, Andreas openclipart-libreoffice=1:0.18+dfsg-17_libreoffice-common=1:7.0.0~rc1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openclipart Source-Version: 1:0.18+dfsg-18 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of openclipart, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated openclipart 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: Sun, 05 Jul 2020 08:13:45 + Source: openclipart Architecture: source Version: 1:0.18+dfsg-18 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Rene Engelhard Closes: 964261 964262 Changes: openclipart (1:0.18+dfsg-18) unstable; urgency=medium . * QA upload. * Build-Depend on libreoffice-dev-gui (closes: #964262) * rename shapes.* to shapes-openclipart (closes: #964261) * disable optipng usage since it hangs on stop_sign_miguel_s_nchez_.png Checksums-Sha1: 4b0dba167f3c8e394c9bb1338074b92faf0f6542 2148 openclipart_0.18+dfsg-18.dsc c027cbbd154a13e5abc749c8d570397cbb442b2a 6420 openclipart_0.18+dfsg-18.debian.tar.xz 05e8173b58901f1665cebde6f6f45d6c6d8f267e 5850 openclipart_0.18+dfsg-18_source.buildinfo Checksums-Sha256: f1682d4a217072eff7c944e0ab787b54fa7b5f5e0194ed45c2f32b81af57b3df 2148 openclipart_0.18+dfsg-18.dsc 4dbaa0eee28fd4c6cbb641e9e6e69b26da2924997d43712d1b6fccfe1e55f88e 6420 openclipart_0.18+dfsg-18.debian.tar.xz 0676f39a543a1e659b8a87a891b2a7d091b8e2c36f63ef939bdd0a6cb822d707 5850 openclipart_0.18+dfsg-18_source.buildinfo Files: 1c51e68ebed78041c1b0eec071799372 2148 graphics optional
Bug#964262: marked as done (FTBFS: needs updated build-depends; needs to build-depend on libreoffice-dev-gui)
Your message dated Sun, 05 Jul 2020 10:04:05 + with message-id and subject line Bug#964262: fixed in openclipart 1:0.18+dfsg-18 has caused the Debian Bug report #964262, regarding FTBFS: needs updated build-depends; needs to build-depend on libreoffice-dev-gui 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.) -- 964262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openclipart Version: 1:0.18+dfsg-17 Severity: serious Dear Maintainer, Hi, as discussed back then in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952347 gengal was moved to libreoffice-dev-gui for the 7.x LO packages. These got uploaded to sid now [1]. Please build-depend on (the hopefully soon available) libreoffice-dev-gui. Regards, Rene [1] unfortunately thay are BD-Uninstallable anywhere due to the bsdmainutils mess (#)964242 but.: libreoffice build-depends on: - javahelper:amd64 (>= 0.37~) javahelper depends on: - bsdmainutils:amd64 bsdmainutils depends on missing: - bsdextrautils:amd64 (>= 2.35.2-7) --- End Message --- --- Begin Message --- Source: openclipart Source-Version: 1:0.18+dfsg-18 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of openclipart, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated openclipart 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: Sun, 05 Jul 2020 08:13:45 + Source: openclipart Architecture: source Version: 1:0.18+dfsg-18 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Rene Engelhard Closes: 964261 964262 Changes: openclipart (1:0.18+dfsg-18) unstable; urgency=medium . * QA upload. * Build-Depend on libreoffice-dev-gui (closes: #964262) * rename shapes.* to shapes-openclipart (closes: #964261) * disable optipng usage since it hangs on stop_sign_miguel_s_nchez_.png Checksums-Sha1: 4b0dba167f3c8e394c9bb1338074b92faf0f6542 2148 openclipart_0.18+dfsg-18.dsc c027cbbd154a13e5abc749c8d570397cbb442b2a 6420 openclipart_0.18+dfsg-18.debian.tar.xz 05e8173b58901f1665cebde6f6f45d6c6d8f267e 5850 openclipart_0.18+dfsg-18_source.buildinfo Checksums-Sha256: f1682d4a217072eff7c944e0ab787b54fa7b5f5e0194ed45c2f32b81af57b3df 2148 openclipart_0.18+dfsg-18.dsc 4dbaa0eee28fd4c6cbb641e9e6e69b26da2924997d43712d1b6fccfe1e55f88e 6420 openclipart_0.18+dfsg-18.debian.tar.xz 0676f39a543a1e659b8a87a891b2a7d091b8e2c36f63ef939bdd0a6cb822d707 5850 openclipart_0.18+dfsg-18_source.buildinfo Files: 1c51e68ebed78041c1b0eec071799372 2148 graphics optional openclipart_0.18+dfsg-18.dsc 9af8e982e2a79f7605ea83d699638cac 6420 graphics optional openclipart_0.18+dfsg-18.debian.tar.xz 19ca3dca843de221751ea23546d71088 5850 graphics optional openclipart_0.18+dfsg-18_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAl8BoNUQHHJlbmVAZGVi aWFuLm9yZwAKCRAKoEVx0D4+cJNyD/9CKMoyYB9MQajD/YtJ6tPwIwpQneb/jIHe 5s4HIfzRrV3HhjmQj6g9nOxVXA8qH5Mn0XLQt3ncTbRLHstIgaOp+CvgBUcI/Xhw 2h/VSoL7AoixLpYezE3J6rVuF4fzByGUfb2s0TLVuQ+wGLgAiHE4Q1M1PrlhToND maYHOgrnYRiJTPIkmVuWz+kh+6rMGPjA0d6Ajn6k5rUKd/+fkVxQNPOMgqjncyD3 h2pwj4zKAYr9H2GvzP3Nuw01QyA+q59uaiVL+cUPKGqQGRmbgsqtRCEe7cJ1DlQy J0ACtUIysGQyFE8T6RhPvb8zt0VopXjA6fjqiIEHuGAaOT+Vi1hz49fE8nJ8dlZk XIMIoyqr4TW35fObCZW8q459AOfc4R114KBpHaqEtX0gGi8WGssNssLql+X/X2XF YwKk64BnHKXVZLbxE0vy+TZJJr6jPq2HtP6WHxJ+EF+WsM9gZdkyGxr86f+9lvGj K0vvIY8d/gbaCfd5s/0Ps0AjZ1NWJ0D/E0OAT2c/M5QxIkhQFUI8ie8ooeh0y9oS ORSUwRdlVRjvFJYeJSaSduKyeDcFxR/KHEvDzJasFZlHztCqVU7Hb2aLsx9naV55 a37KYl12ebykkBBLxbsl4jl0DR7DvX850YfoSgCyuxg+BFp7goSxa97dqpL84RyY ilrEx/jAvw== =Ty0R -END PGP SIGNATURE End Message ---
Bug#952317: marked as done (javahelper: jh_manifest breaks on jar files with no manifest)
Your message dated Sun, 05 Jul 2020 10:03:40 +
with message-id
and subject line Bug#952370: fixed in javatools 0.74
has caused the Debian Bug report #952370,
regarding javahelper: jh_manifest breaks on jar files with no manifest
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.)
--
952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cronometer
Version: 0.9.9+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_link usr/share/java/cronometer.jar usr/bin/cronometer
> mkdir -p debian/cronometer/usr/share/pixmaps
> cp src/img/apple-200x200.png
> debian/cronometer/usr/share/pixmaps/cronometer.png
> dh_auto_install
> make[1]: Leaving directory '/<>'
>dh_install
>jh_installjavadoc
>dh_installdocs
>dh_installchangelogs
>dh_installman
>dh_lintian
>dh_perl
>dh_link
>jh_installlibs
>jh_classpath
>jh_manifest
> error: No member named $memberName
> at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
>
> Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x5599124f4718),
> "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
>
> main::update_jar("debian/cronometer/usr/share/cronometer/usda_sr24.jar",
> undef) called at /usr/bin/jh_manifest line 209
> Could not read manifest from
> debian/cronometer/usr/share/cronometer/usda_sr24.jar (2): at
> /usr/bin/jh_manifest line 298.
> make: *** [debian/rules:7: binary] Error 255
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/cronometer_0.9.9+dfsg-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: javatools
Source-Version: 0.74
Done: Emmanuel Bourg
We believe that the bug you reported is fixed in the latest version of
javatools, 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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated javatools 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: Sun, 05 Jul 2020 11:49:48 +0200
Source: javatools
Architecture: source
Version: 0.74
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Closes: 952370
Changes:
javatools (0.74) unstable; urgency=medium
.
* jh_manifest: Fix the error when the jar processed doesn't have a manifest
(Closes: #952370)
Checksums-Sha1:
57d1fb33c9748295a19564cce096733bc3695d8b 1892 javatools_0.74.dsc
327c6e8ea1e25ab9477ae3f93bd09fdda2382364 54584 javatools_0.74.tar.xz
46fda41aa8d00bb96561940476dfebc12519 10113 javatools_0.74_source.buildinfo
Checksums-Sha256:
046080749520eeaeb1fa91eed780ff4311b357853d79b739ccd01eaa8367729c 1892
javatools_0.74.dsc
e10c88d280b39372dda0f3c26db2480ad76643185f59d813010b590de674415b 54584
javatools_0.74.tar.xz
c17f27c91ee7a72d0deb69e090b80b36784513ebb98a8c2662fe07c1cc26f2ee 10113
javatools_0.74_source.buildinfo
Files:
251f90a737741d424bc22b7871f3e299 1892 java optional javatools_0.74.dsc
d8df36a6f13b6c3878660ab4e86c7c97 54584 java optional javatools_0.74.tar.xz
c92689ce729bf4bf3dd97d65d6867050 10113 java optional
javatools_0.74_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl8BoqgSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCstLMQAKi7yHP8y8M9LkaKg9jHTxFpHhfyB84S
/nqcFtib/p5FarH1PnBxkuAtHeUve/xiSn5DXCxsdzxU4Banxl7rdilkTtL+OSDz
CztPkimIyeJhO8zJAsdMl10kZK5xpIlrA7v52vcB4pfnSwnV4qgGe2+ZaAc9rwrA
P1m9A6puWyHX3/8fmkRUgcu945jknuHlFYWtFu3VNkK3k22RHA1hk+QNBLLEpRx/
Bug#952370: marked as pending in javatools
Control: tag -1 pending Hello, Bug #952370 in javatools 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/java-team/javatools/-/commit/73afb66e2f9ff2b07c32d7518367b0998285bc06 jh_manifest: Fix the error when the jar processed doesn't have a manifest (Closes: #952370) (this message was generated automatically) -- Greetings https://bugs.debian.org/952370
Bug#964293: hubicfuse: error while loading libssl.so.1.0.0
Hi, On Sun, 05 Jul 2020 11:42:08 +0200, rpnpif wrote: > The command hubicfuse /mnt/hubic -o noauto_cache,sync_read > get the result : > hubicfuse: error while loading shared libraries: libssl.so.1.0.0: cannot > open shared object file: No such file or directory > > but libssl1.1 was needed. What does command -v hubicfuse show? Regards, Stephen pgpMaNyzVoDm6.pgp Description: OpenPGP digital signature
Processed: Bug#952370 marked as pending in javatools
Processing control commands: > tag -1 pending Bug #952370 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952289 [javahelper] libquartz2-java: FTBFS: Could not read manifest from /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): at /usr/bin/jh_manifest line 298. Bug #952317 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952322 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. -- 952289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952289 952317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952317 952322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952322 952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962653: davical: diff for NMU version 1.1.9.3-1.1
Control: tags 962653 + patch Control: tags 962653 + pending Dear maintainer, I've prepared an NMU for davical (versioned as 1.1.9.3-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru davical-1.1.9.3/debian/changelog davical-1.1.9.3/debian/changelog --- davical-1.1.9.3/debian/changelog 2020-04-13 23:11:31.0 +0300 +++ davical-1.1.9.3/debian/changelog 2020-07-05 12:34:48.0 +0300 @@ -1,3 +1,10 @@ +davical (1.1.9.3-1.1) unstable; urgency=high + + * Non-maintainer upload. + * Stop using rst2pdf that might not be in bullseye. (Closes: #962653) + + -- Adrian Bunk Sun, 05 Jul 2020 12:34:48 +0300 + davical (1.1.9.3-1) unstable; urgency=medium * New upstream release to support AWL 0.61 diff -Nru davical-1.1.9.3/debian/control davical-1.1.9.3/debian/control --- davical-1.1.9.3/debian/control 2020-04-13 23:11:31.0 +0300 +++ davical-1.1.9.3/debian/control 2020-07-05 12:34:25.0 +0300 @@ -11,7 +11,6 @@ libawl-php (>= 0.61-1~), libawl-php (<< 0.62), gettext, doxygen, - rst2pdf, php-cli | php5-cli Vcs-Git: https://gitlab.com/davical-project/davical.git Vcs-Browser: https://gitlab.com/davical-project/davical
Bug#964294: mlpack FTBFS: dh_missing: error: missing files, aborting
Source: mlpack Version: 3.3.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=mlpack ... dh_missing -a -O--buildsystem=cmake -O--max-parallel=1 dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets-none.cmake exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets.cmake exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-config-version.cmake exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-config.cmake exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: libmlpack-dev (45), libmlpack3 (2), mlpack-bin (1), mlpack-doc (37), python3-mlpack (2) * dh_installdocs: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (0), mlpack-doc (6), python3-mlpack (0) * dh_installexamples: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (0), mlpack-doc (1), python3-mlpack (0) * dh_installman: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (47), mlpack-doc (0), python3-mlpack (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built For a short-term work-around: Add the files to debian/not-installed make: *** [debian/rules:46: binary-arch] Error 25
Bug#964251: libreoffice-common: needs Breaks+Replaces against openclipart-libreoffice
Hi, Am 04.07.20 um 18:53 schrieb Rene Engelhard: >> openclipart-libreoffice will probably need updates as well to no longer >> ship these files (or rename them), it's probably easiest if you fix and >> upload that QA maintained package, too. > > No. I don't care, actually :-) That's why it is QA maintained. > > > Yoju did the last QA uploads, you can do that too. (Actually it needs an > update for the new > > libreoffice-dev-gui anyways.) Ah, well, just did that. (Needed to disable optipng since it hanged.) Regards, rene
Processed: davical: diff for NMU version 1.1.9.3-1.1
Processing control commands: > tags 962653 + patch Bug #962653 [src:davical] davical build depends on rst2pdf that might not be in bullseye Added tag(s) patch. > tags 962653 + pending Bug #962653 [src:davical] davical build depends on rst2pdf that might not be in bullseye Added tag(s) pending. -- 962653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964293: hubicfuse: error while loading libssl.so.1.0.0
Package: hubicfuse Version: 3.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, The command hubicfuse /mnt/hubic -o noauto_cache,sync_read get the result : hubicfuse: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory but libssl1.1 was needed. Regards. -- System Information: Debian Release: 9.12 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/2 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) Versions of packages hubicfuse depends on: ii libc6 2.24-11+deb9u4 ii libcurl37.52.1-5+deb9u10 ii libfuse22.9.7-1+deb9u2 ii libjson-c3 0.12.1-1.1 ii libmagic1 1:5.30-1+deb9u3 ii libssl1.1 1.1.0l-1~deb9u1 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 hubicfuse recommends no packages. hubicfuse suggests no packages. -- no debconf information
Bug#954195: fix for the issue
As it says in the error, the problem is with the object `manager` being `None`. I was able to bypass this issue by adding an `if` case to check whether `manager` is `None` or not. With that, `gnome-music` runs.
Bug#962882: marked as done (python3-djangorestframework: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd))
Your message dated Sun, 05 Jul 2020 09:33:32 + with message-id and subject line Bug#962882: fixed in djangorestframework 3.11.0-1 has caused the Debian Bug report #962882, regarding python3-djangorestframework: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) 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.) -- 962882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-djangorestframework Version: 1.4.9-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 python3-djangorestframework depends on fonts-glewlwyd, which contains the fonts font-awesome and glyphicons-halflings. Please instead depend on fonts-font-awesome and/or fonts-glyphicons-halflings as needed, so that fonts-glewlwyd can be dropped from Debian. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7neDgACgkQLHwxRsGg ASFBJg/+LMiDgBzdMKuxQK0qC80260uZrFi9pVX6GQfvFfpLSjH4aLRRsIZ3L4Ru 0oVNkrYK1bqYx8l/v/eV6b7FCSWWDPipdSvM9xk3axFNSLsmO0zo3tUOCIOxExDe P1Jn/bKKl9w2+ynGEXqw8YjY+WtZ/ODyVFVYZYSmlPP2bFn+Advny7ZRw4WDj37M L16Wlu+g1nt2/y+i6n1oKrsS4XjIkzbdx/fIHljPLx6qWMgXgrdDUKIvoGA4FGrr /yYs6+87L3mRoOmmwtVkYss1tKl4vbwskzCiQ4wkNyTy2wlMH/PJNei0sqRHirG/ YwlW3aY3XvUttJKXKSNODzHY45/n69SfnXnzdB75JKSDKmHfICYGoR4ocBxZ2hj8 ZAcRYTnIOYQeLm++GJIqyk8KnYWoY6YVZUyvgJJkR3zg5CD4YNu3q5liOIlTJKPC v8o3vpBx4s2sRXovejRknB8UN64rGpN8det1mJZrZdlvLShNl4vfR26bZcMJgxr2 SiasKhiwb6m+gMvS+xvqjeSedMVIdBaS0/3RC/fYx9Y2R/Pylkl6KJzOjTkKlpMh J1z9oIE2GXZB27khF3elhVOXLVBt3Cti2EYz7ksCjHS2bTbNKTJ/YMAQRD901Yvs St6BHX4FpmrR3eFfMBef8oTZL21l0HXGrRRrKQ6sfZTAwdlVj5o= =/EEH -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: djangorestframework Source-Version: 3.11.0-1 Done: Michael Fladischer We believe that the bug you reported is fixed in the latest version of djangorestframework, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer (supplier of updated djangorestframework 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: Sun, 05 Jul 2020 11:00:13 +0200 Source: djangorestframework Architecture: source Version: 3.11.0-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team Changed-By: Michael Fladischer Closes: 962882 Changes: djangorestframework (3.11.0-1) unstable; urgency=low . * Team upload. * New upstream release. * Refresh patches. * Rename MIT license to Expat. * Bump debhelper version to 13. * Bump Standards-Version to 4.5.0. * Use dh_link to replace assets (fonts, css, js) which are already packaged. * Depend on fonts-font-awesome and fonts-glyphicons-halflings, drop fonts-glewlwyd (Closes: #962882). * Depend on libjs-prettify. * Fixing permissions for font file no longer necessary, drop override_dh_fixperms. * Clean up files to allow two builds in a row. * Set Rules-Requires-Root: no. * Add patch to fix asset names for packaged files. * Replace glyphicons in doc package with symlinks to the packaged font. * Run wrap-and-sort -bast to reduce diff size of future changes. Checksums-Sha1: b01fc687b1cde81da592ce6d0739d21a16ea454f 2207 djangorestframework_3.11.0-1.dsc 162068b5c89a4b07f6fcf4a4e1e0ad662d61efe6 8731438 djangorestframework_3.11.0.orig.tar.gz a5dfb7bbfbf98ab9182220e48c7d587007bbf8d3 76 djangorestframework_3.11.0-1.debian.tar.xz 70afdd8e59db8299c3d0b6b2ba0c8ccf13afb940 9140 djangorestframework_3.11.0-1_amd64.buildinfo Checksums-Sha256: a361b0297f716ac610e4715419142b545f0fe94a3f591a65baee45838a07b3a8 2207 djangorestframework_3.11.0-1.dsc 09c995f86b99a7dd799de0b1b644f753aad22e75609dba1abda0ad507d0a537b 8731438 djangorestframework_3.11.0.orig.tar.gz 184783117fa40ee41ede8edf2f7d14b64c70ab55e10acb50200599e55d6f2c62 76 djangorestframework_3.11.0-1.debian.tar.xz d2419d6aa22d2f6cbc94a7de2dd994137c4df8e91ad9398e1c41d36fe3e80a30 9140 djangorestframework_3.11.0-1_amd64.buildinfo Files:
Processed: Re: libbluray: Include list_titles and bdsplice utilities
Processing control commands: > block -1 by 964242 Bug #964253 [libbluray-bin] libbluray: Include list_titles and bdsplice utilities 964253 was not blocked by any bugs. 964253 was not blocking any bugs. Added blocking bug(s) of 964253: 964242 > owner -1 ! Bug #964253 [libbluray-bin] libbluray: Include list_titles and bdsplice utilities Owner recorded as Vasyl Gello . -- 964253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959075: Still not working on Debian testing
On Sun, 05 Jul 2020 09:58:46 +0800 Paul Wise wrote: > On Sat, 2020-07-04 at 18:08 +0200, richard lucassen wrote: > > > Rereading it, I don't know if this issue was present in 2.9 or > > earlier. I just noticed it while testing the new version. > > Would you mind downgrading to 2.9 and testing it? > You can install it from Debian buster or snapshot.d.o I tried to find out which line causes this error and it is line 12 in /etc/network/if-pre-up.d/ifenslave: ip link add dev "$IFACE" type bond It has nothing to do with the ifenslave package: # modprobe -rv bonding rmmod bonding # ip link add dev bond0 type bond RTNETLINK answers: File exists And ifenslave_2.9 loads the bonding module in "add_master()": # If the bonding module is not yet loaded, load it. if [ ! -r /sys/class/net/bonding_masters ]; then modprobe -q bonding fi HTH, R. -- richard lucassen https://contact.xaq.nl/
Bug#962882: marked as pending in djangorestframework
Control: tag -1 pending Hello, Bug #962882 in djangorestframework 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/python-team/modules/djangorestframework/-/commit/0d966ed908c7e0c27270baf1d2af4403eaaf00f3 Depend on fonts-font-awesome and fonts-glyphicons-halflings, drop fonts-glewlwyd (Closes: #962882). (this message was generated automatically) -- Greetings https://bugs.debian.org/962882
Processed: Bug#962882 marked as pending in djangorestframework
Processing control commands: > tag -1 pending Bug #962882 [python3-djangorestframework] python3-djangorestframework: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Added tag(s) pending. -- 962882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959075: Still not working on Debian testing
On Sun, 05 Jul 2020 09:58:46 +0800 Paul Wise wrote: > > Rereading it, I don't know if this issue was present in 2.9 or > > earlier. I just noticed it while testing the new version. > > Would you mind downgrading to 2.9 and testing it? > You can install it from Debian buster or snapshot.d.o No message indeed: # wget http://ftp.nl.debian.org/debian/pool/main/i/ifenslave/ifenslave_2.9_all.deb # ifdown bond0 # modprobe -rv bonding # dpkg --purge ifenslave # dpkg -i ifenslave_2.9_all.deb # ifup bond0 # (no message) # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v5.7.0-1-amd64 Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth2 (primary_reselect always) Currently Active Slave: eth2 MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 ARP Polling Interval (ms): 2000 ARP IP target/s (n.n.n.n form): 10.234.0.33, 10.234.0.34 Slave Interface: eth2 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:b1:1c:33:94:d8 Slave queue ID: 0 Slave Interface: eth3 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:b1:1c:33:94:d9 Slave queue ID: 0 -- richard lucassen https://contact.xaq.nl/
Bug#963325: marked as pending in alot
Control: tag -1 pending Hello, Bug #963325 in alot 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/python-team/applications/alot/-/commit/907ff47666c29ddbb3fc8e550ed18900a2b3ae54 d/control: Add build-dep locales-all. Closes: #963325 Signed-off-by: Jordan Justen (this message was generated automatically) -- Greetings https://bugs.debian.org/963325
