Am Montag, den 03.02.2020, 18:59 +0100 schrieb Matthias Klose:
> $ dpkg -S libgcc_s.so.1
> libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
> libgcc1: /lib/libgcc_s.so.1
>
> if you need the library in /lib, make sure that you depend on
> libgcc1, else it's
> found in /usr/lib/.
>
> I'm
Processing commands for cont...@bugs.debian.org:
> forwarded 950337 https://github.com/rust-num/num-traits/issues/151
Bug #950337 [src:rust-num-traits] rust-num-traits: FTBFS on mipsel/mips64el:
assertion failed: x.max(y) == min
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> block 950337 with 950583
Bug #950337 [src:rust-num-traits] rust-num-traits: FTBFS on mipsel/mips64el:
assertion failed: x.max(y) == min
950337 was not blocked by any bugs.
950337 was blocking: 949798
Added blocking bug(s) of 950337: 950583
>
Your message dated Tue, 4 Feb 2020 06:38:02 +0100
with message-id <90d3f67e-27ac-fc53-3fcd-37aa0605e...@debian.org>
and subject line Fixed by node-chrome-trace-event 1.0.2-1
has caused the Debian Bug report #950089,
regarding node-chrome-trace-event FTBFS: error TS2300: Duplicate identifier
Package: libgcc1
Version: 1:10-20200202-1
Followup-For: Bug #950551
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
On both my systems running unstable, libgcc-s1 is installed, but I
don't have /usr/lib/x86_64-linux-gnu/libgcc_s.so.1. So, it seems
something removes it. I have no clue on
Processing commands for cont...@bugs.debian.org:
> fixed 950089 1.0.2-1
Bug #950089 [src:node-chrome-trace-event] node-chrome-trace-event FTBFS: error
TS2300: Duplicate identifier 'IteratorResult'
Marked as fixed in versions node-chrome-trace-event/1.0.2-1.
> thanks
Stopping processing here.
Your message dated Tue, 04 Feb 2020 05:17:52 +
with message-id
and subject line Bug#949894: fixed in quiterss 0.19.3+dfsg-1
has caused the Debian Bug report #949894,
regarding quiterss: Segmentation fault at start
to be marked as done.
This means that you claim that the problem has been
Actually now that guile-3.0 is in sid (though it's not yet building on
all the release architectures), I suppose we might just side-step 2.2
entirely, but either would be much appreciated.
Here this at least builds via "fakeroot debian/rules binary", but
regardless, I'd really like to resolve
Package: libgcc1
Version: 1:10-20200202-1
Followup-For: Bug #950551
Same here. Did apt dist-upgrade and rebooted, then the libgcc_s.so.1 error
message appeared.
Tried OP method and worked:
1) Boot to an Ubuntu live USB
2) sudo cryptsetup open ...
3) chroot
4) Downgrade libgcc1 from
Processing commands for cont...@bugs.debian.org:
> affects 950579 src:octomap
Bug #950579 [libgcc1] libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld:
cannot find -lgcc_s
Added indication that 950579 affects src:octomap
>
End of message, stopping processing here.
Please contact me if you
Package: python3-jupyter-sphinx
Version: 0.2.3-1
Severity: grave
Dear Maintainer,
The package is unuseable, as it relies on the `ipywidgets.embed` module,
which is unavailable in the latest sid version:
Extension error:
Could not import extension jupyter_sphinx.execute (exception: No module
Your message dated Tue, 04 Feb 2020 00:35:10 +
with message-id
and subject line Bug#950024: fixed in ruby-github-markdown 0.6.9-5
has caused the Debian Bug report #950024,
regarding ruby-github-markdown: ships /usr/bin/gfm already provided by the gfm
package
to be marked as done.
This means
Control: tag -1 pending
Hello,
Bug #950024 in ruby-github-markdown 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:
Processing control commands:
> tag -1 pending
Bug #950024 [ruby-github-markdown] ruby-github-markdown: ships /usr/bin/gfm
already provided by the gfm package
Added tag(s) pending.
--
950024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950024
Debian Bug Tracking System
Contact
Your message dated Mon, 03 Feb 2020 23:49:58 +
with message-id
and subject line Bug#937507: fixed in pypng 0.0.20+ds-2
has caused the Debian Bug report #937507,
regarding pypng: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 03 Feb 2020 23:35:07 +
with message-id
and subject line Bug#950533: fixed in systemd 244.1-3
has caused the Debian Bug report #950533,
regarding upgrade fails in a chroot without mounted /proc
to be marked as done.
This means that you claim that the problem has been
Control: tag -1 pending
Hello,
Bug #950533 in systemd 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:
Processing control commands:
> tag -1 pending
Bug #950533 [systemd] upgrade fails in a chroot without mounted /proc
Added tag(s) pending.
--
950533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 03 Feb 2020 23:07:01 +
with message-id
and subject line Bug#950565: fixed in kalgebra 4:19.12.1-2
has caused the Debian Bug report #950565,
regarding kalgebra FTBFS on architectures without qtwebengine5-dev
to be marked as done.
This means that you claim that the
Source: flang
Version: 20190329-4
Severity: serious
Tags: ftbfs
...
dh_dwz -O--buildsystem=cmake
-O--builddirectory=/tmp/flang-20190329/debian/build
install -d debian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu
dwz
I can confirm this bug. After doing an apt full-upgrade, I faced the
same issue as OP. However, I was not able to fix it by downgrading
packages, but instead used a similar approach to the way described in
the btrfs bug #950556 [1].
After chrooting into the system, I changed the following file:
Processing commands for cont...@bugs.debian.org:
> fixed 950408 1.3.7-2
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Marked as fixed in versions fwupd/1.3.7-2.
> fixed 950407 1.3.7-2
Bug #950407 [fwupd] fwupd-refresh.service contains @bindir breaking the unit
file
Marked as fixed
Your message dated Mon, 03 Feb 2020 21:21:34 +
with message-id
and subject line Bug#933441: fixed in pcsx2 1.5.0~gfc1d9aef0+dfsg-2
has caused the Debian Bug report #933441,
regarding pcsx2: Please rebuild against wxWidgets GTK 3 package
to be marked as done.
This means that you claim that
The issue seems to stem from the fact the python3 package(s) do not
provide /usr/bin/python.
I've attached a patch which should fix builds which use either the
CMakeList.txt file, or the ./configure.py script.
This is only an initial change, as I haven't been able to try it out,
but should force
This issue has been fixed in upstream version 0.10.0 (out just now).
This is caused by recent GnuTLS versions (since 3.6.11 AFAIK) listing
the peer's certificate type in the session description so they aren't
identical on anonymous client and authenticated server, so backporting
shouldn't be
Source: python-django
Version: 2:2.2.9-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1:1.11.27-1~deb10u1
Hi,
The following vulnerability was published for python-django.
CVE-2020-7471[0]:
| Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0
Processing control commands:
> found -1 1:1.11.27-1~deb10u1
Bug #950581 [src:python-django] python-django: CVE-2020-7471: Potential SQL
injection via StringAgg(delimiter)
Marked as found in versions python-django/1:1.11.27-1~deb10u1.
--
950581:
Processing commands for cont...@bugs.debian.org:
> notfound 946011 1.7.11-1+deb8u7
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version
'1.7.11-1+deb8u7' with architecture ''
Unable to make a source version for version
notfound 946011 1.7.11-1+deb8u7
close 946011 2:2.2.8-1
thanks
Your message dated Mon, 03 Feb 2020 19:49:21 +
with message-id
and subject line Bug#949759: fixed in bootcd 6.01
has caused the Debian Bug report #949759,
regarding bootcd: Missing build dependencies on python3-docutils and shellia
to be marked as done.
This means that you claim that the
Your message dated Mon, 03 Feb 2020 19:50:06 +
with message-id
and subject line Bug#949134: fixed in oasis3 3.mct+dfsg.121022-14
has caused the Debian Bug report #949134,
regarding oasis3: FTBFS (Assigning non-zero to $[ is no longer possible at
../../protex/protex line 87.)
to be marked as
Your message dated Mon, 03 Feb 2020 19:35:15 +
with message-id
and subject line Bug#950134: fixed in pyferret 7.5.0-3
has caused the Debian Bug report #950134,
regarding pyferret ftbfs with python 3.8 and pango from experimental
to be marked as done.
This means that you claim that the
On 2020-02-03 20:21, Matthias Klose wrote:
> On 2/3/20 8:14 PM, Simon McVittie wrote:
> >> Sanity check compile stderr:
> >> /usr/bin/ld: cannot find -lgcc_s
> >> collect2: error: ld returned 1 exit status
>
> this is fixed in unstable. please retry the package build.
>
That won't work. For
On 2/3/20 8:14 PM, Simon McVittie wrote:
>> Sanity check compile stderr:
>> /usr/bin/ld: cannot find -lgcc_s
>> collect2: error: ld returned 1 exit status
this is fixed in unstable. please retry the package build.
Processing control commands:
> affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex
Bug #950579 [libgcc1] libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld:
cannot find -lgcc_s
Added indication that 950579 affects src:glib2.0, src:xterm, src:hdrmerge, and
src:esorex
--
950579:
Package: libgcc1
Version: 1:10-20200202-1
Severity: serious
Justification: FTBFS
Tags: ftbfs
Control: affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex
https://buildd.debian.org/status/fetch.php?pkg=glib2.0=s390x=2.62.4-2=1580755175=log
> Package versions:
[with linebreaks added for
Control: severity -1 normal
Control: tags -1 moreinfo
Am 03.02.20 um 19:27 schrieb Eric Valette:
>
> If I let eth0 in /etc/network/interface I get my eth0 card correctly
> configured by ifplugd
> each time using full duplex and 1000Mbps
>
> ethtool eth0
> Settings for eth0:
>
Processing control commands:
> severity -1 normal
Bug #950576 [network-manager] network-manager fails to correctly configure eth0
speed and fails when autoneg is on
Severity set to 'normal' from 'critical'
> tags -1 moreinfo
Bug #950576 [network-manager] network-manager fails to correctly
Control: tags -1 moreinfo
Control: severity -1 important
Please run
reportbug --template systemd
reportbug --template kamailio
systemctl cat kamailio.service
systemctl status kamailio.service
journalctl -b -u kamailio.service
on the affected system and attach the output to this bug report.
Processing control commands:
> tags -1 moreinfo
Bug #950575 [kamailio,systemd] kamailio manual install fails die modules are
not yet in path?¡
Added tag(s) moreinfo.
> severity -1 important
Bug #950575 [kamailio,systemd] kamailio manual install fails die modules are
not yet in path?¡
Severity
Your message dated Mon, 03 Feb 2020 18:34:45 +
with message-id
and subject line Bug#950060: fixed in m2l-pyqt 1.6-3
has caused the Debian Bug report #950060,
regarding m2l-pyqt: missing build dependency on dh-python
to be marked as done.
This means that you claim that the problem has been
Package: network-manager
Version: 1.22.6-1
Severity: critical
Justification: breaks unrelated software
If I let eth0 in /etc/network/interface I get my eth0 card correctly configured
by ifplugd
each time using full duplex and 1000Mbps
ethtool eth0
Settings for eth0:
Supported ports: [
Package: kamailio,systemd
Version: kamailio/5.3.0-1
Version: systemd/230-7
Severity: grave
Another systemd related problem, (like happened with #921015 ), this
error seems does not hapened if are installed with apt.get
i try to install kamailio due other ways, like aptitude or gui others,
and in
Your message dated Mon, 03 Feb 2020 18:05:07 +
with message-id
and subject line Bug#950226: fixed in ruby-rails-timeago 2.17.1-2
has caused the Debian Bug report #950226,
regarding ruby-rails-timeago: autopkgtest needs update for new version of
gem2deb
to be marked as done.
This means that
On 2/3/20 3:46 PM, Felix Zielcke wrote:
> On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
>> Package: libgcc1
>> Version: 1:9.2.1-25
>> Severity: grave
>> Justification: renders package unusable
>>
>> hey,
>>
>> after upgrading some latest packages on sid, i can no longer unlock
>
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:neomutt
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
-By: Matthias Klose
Closes: 950525
Changes:
gcc-9 (9.2.1-28) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-9 branch.
- Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
* libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir. Closes: #950525.
* Allow
Your message dated Mon, 03 Feb 2020 17:20:38 +
with message-id
and subject line Bug#950549: fixed in requirejs-text 2.0.16-1
has caused the Debian Bug report #950549,
regarding node-requirejs-text: package.json occupies the location supposed for
node-requirejs
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package firefox-esr
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:meson
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
control: tags -1 patch
Author: Gianfranco Costamagna
Last-Update: 2020-02-03
--- gst-plugins-bad1.0-1.16.2.orig/configure.ac
+++ gst-plugins-bad1.0-1.16.2/configure.ac
@@ -1845,7 +1845,7 @@ AG_GST_CHECK_FEATURE(OPENCV, [opencv plu
HAVE_OPENCV="yes"
fi
], [
-
Processing control commands:
> tags -1 patch
Bug #922583 [src:gst-plugins-bad1.0] FTBFS against opencv 4.0.1 (exp)
Added tag(s) patch.
--
922583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #950549 [node-requirejs-text] node-requirejs-text: package.json occupies
the location supposed for node-requirejs
Severity set to 'serious' from 'normal'
--
950549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950549
Debian Bug
Control: tag -1 pending
Hello,
Bug #950549 in requirejs-text 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:
Processing control commands:
> tag -1 pending
Bug #950549 [node-requirejs-text] node-requirejs-text: package.json occupies
the location supposed for node-requirejs
Added tag(s) pending.
--
950549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950549
Debian Bug Tracking System
Contact
Your message dated Mon, 03 Feb 2020 17:05:32 +
with message-id
and subject line Bug#937533: fixed in pyserial 3.4-5.1
has caused the Debian Bug report #937533,
regarding pyserial: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Control: tags 937533 + patch
Dear maintainer,
I've prepared an NMU for pyserial (versioned as 3.4-5.1). The diff
is attached to this message.
Regards.
diff -Nru pyserial-3.4/debian/changelog pyserial-3.4/debian/changelog
--- pyserial-3.4/debian/changelog 2020-01-07 08:21:42.0 -0500
Processing control commands:
> tags 937533 + patch
Bug #937533 [src:pyserial] pyserial: Python2 removal in sid/bullseye
Added tag(s) patch.
--
937533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 3 Feb 2020 17:31:54 +0100
with message-id <20200203163154.ga28...@georges.khaznadar.fr>
and subject line Update to openbabel3 done
has caused the Debian Bug report #948774,
regarding xdrawchem: build with Open Babel 3
to be marked as done.
This means that you claim that
Source: node-copy-webpack-plugin
Version: 4.3.0-6
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-copy-webpack-plugin.html
...
5 passing (81ms)
65 failing
1) apply function
with glob in from
can use a glob to move a file
Your message dated Mon, 03 Feb 2020 15:36:51 +
with message-id
and subject line Bug#950110: fixed in octomap 1.9.3+dfsg-2
has caused the Debian Bug report #950110,
regarding liboctomap-dev,...: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This
Your message dated Mon, 03 Feb 2020 15:35:04 +
with message-id
and subject line Bug#939454: fixed in link-grammar 5.7.0-1
has caused the Debian Bug report #939454,
regarding link-grammar ftbfs (symbols file mismatches)
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
-By: Matthias Klose
Closes: 950525
Changes:
gcc-9 (9.2.1-27) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-9 branch.
- Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
* libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir. Closes: #950525.
* Allow
On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
> Package: libgcc1
> Version: 1:9.2.1-25
> Severity: grave
> Justification: renders package unusable
>
> hey,
>
> after upgrading some latest packages on sid, i can no longer unlock
luks
> partition and boot. message:
>
> "Please
Source: kalgebra
Version: 4:19.12.1-1
Severity: serious
Tags: ftbfs
Looks like a problem with the override_dh_auto_configure:
https://buildd.debian.org/status/package.php?p=kalgebra=sid
...
make[1]: Entering directory '/<>'
DMOBILE_BACKEND="none"
make[1]: Leaving directory '/<>'
Source: olive-editor
Version: 20200121-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=olive-editor=sid
...
cd /<>/obj-i686-linux-gnu/app && /usr/bin/c++
-DAPPVERSION=\"0.2.0\" -DGITHASH=\"\" -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS
-DQT_GUI_LIB
Your message dated Mon, 03 Feb 2020 14:42:15 +
with message-id
and subject line Bug#950227: fixed in ruby-mime-types 3.3.1-1
has caused the Debian Bug report #950227,
regarding ruby-mime-types: autopkgtest needs update for new version of gem2deb
to be marked as done.
This means that you
Source: acorn
Version:
6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
acorn/experimental recently started to FTBFS:
debian/rules build
dh build
Processing control commands:
> reopen -1
Bug #950099 {Done: Gürkan Myczko } [src:fonts-inter]
fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"
Bug reopened
Ignoring request to alter fixed versions of bug #950099 to the same values
previously set
--
950099:
Control: reopen -1
> Date: Mon, 03 Feb 2020 05:15:10 +0100
> From: Gürkan Myczko
> To: 950099-d...@bugs.debian.org
> Subject: fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"
>
> Same like,
> https://bugs.debian.org/950103
Does it build for you?
It still fails the same both in
Andreas Tille writes:
>> protected branches. Could you please adjust the project's permissions?
>
> Done (hopefully), Andreas.
I was able to push now, thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ |
Source: apertium-fr-es
Version: 0.9.2~r61322-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-fr-es.html
...
make -j15
make[1]: Entering directory '/build/1st/apertium-fr-es-0.9.2~r61322'
make all-am
make[2]:
Source: apertium-oc-es
Version: 1.0.6~r57551-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-oc-es.html
...
make -j16
make[1]: Entering directory '/build/1st/apertium-oc-es-1.0.6~r57551'
make all-am
make[2]: Entering
Source: apertium-mk-bg
Version: 0.2.0~r49489-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-mk-bg.html
...
make -j16
make[1]: Entering directory '/build/1st/apertium-mk-bg-0.2.0~r49489'
apertium-validate-dictionary
Processing control commands:
> tag -1 pending
Bug #950227 [src:ruby-mime-types] ruby-mime-types: autopkgtest needs update for
new version of gem2deb
Added tag(s) pending.
--
950227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950227
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #950227 in ruby-mime-types 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:
Source: apertium-eo-en
Version: 1.0.0~r63833-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-en.html
...
make -j15
make[1]: Entering directory '/build/1st/apertium-eo-en-1.0.0~r63833'
make all-am
make[2]: Entering
Source: apertium-hbs-mkd
Version: 0.1.0~r76450-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-hbs-mkd.html
...
make -j16
make[1]: Entering directory '/build/1st/apertium-hbs-mkd-0.1.0~r76450'
make all-am
make[2]: Entering
Your message dated Mon, 03 Feb 2020 13:49:19 +
with message-id
and subject line Bug#949132: fixed in cdftools 3.0.2-4
has caused the Debian Bug report #949132,
regarding cdftools: FTBFS (LaTeX Error: File 'infwarerr.sty' not found.)
to be marked as done.
This means that you claim that the
Package: btrfs-progs
Version: 5.4.1-1
Severity: critical
My system didn't boot anymore. initramfs complained that for
phread_cancel you need libgcc_s.so installed.
The btrfs hook for initramfs expects it to be in the same dir as libc6.
But that's not true anymore since libgcc1 has been updated
Source: apertium-eo-es
Version: 1:0.9.1~r60655-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-es.html
...
dh_auto_build -O--fail-missing
make -j15
make[1]: Entering directory
Source: apertium-en-gl
Version: 0.5.2~r57551-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-en-gl.html
...
make -j15
make[1]: Entering directory '/build/1st/apertium-en-gl-0.5.2~r57551'
make all-am
make[2]: Entering
Source: apertium-bel-rus
Version: 0.2.0~r81186-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-bel-rus.html
...
make -j1
make[1]: Entering directory '/build/1st/apertium-bel-rus-0.2.0~r81186'
/bin/mkdir -p .deps
touch
Package: libgcc1
Version: 1:9.2.1-25
Severity: grave
Justification: renders package unusable
hey,
after upgrading some latest packages on sid, i can no longer unlock luks
partition and boot. message:
"Please unlock disk rootfs:
libgcc_s.so.1 must be installed for pthread-cancel to work
Aborted"
Processing control commands:
> severity -1 critical
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Severity set to 'critical' from 'important'
--
950408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> block 948638 by 922583 950545
Bug #948638 [release.debian.org] transition: opencv
948638 was blocked by: 950310
948638 was not blocking any bugs.
Added blocking bug(s) of 948638: 950545 and 922583
> tags 950545 + ftbfs
Bug #950545 [src:eviacam]
Your message dated Mon, 03 Feb 2020 13:29:12 +0100
with message-id <0383080a8c0d8307cd6c912e7bf65...@phys.ethz.ch>
and subject line i don't have such an old system, but with sid it's installable
again
has caused the Debian Bug report #854596,
regarding fontmatrix: FTBFS: error: invalid
Your message dated Mon, 03 Feb 2020 13:29:12 +0100
with message-id <0383080a8c0d8307cd6c912e7bf65...@phys.ethz.ch>
and subject line i don't have such an old system, but with sid it's installable
again
has caused the Debian Bug report #854596,
regarding fontmatrix: uninstallable -at least under
Source: eviacam
Version: 2.1.4-1
Severity: serious
Dear maintainer,
eviacam FTBFS against the latest version of OpenCV:
https://buildd.debian.org/status/package.php?p=eviacam=sid
https://buildd.debian.org/status/fetch.php?pkg=eviacam=amd64=2.1.4-1%2Bb1=1580642132=0
which looks due an API change
Your message dated Mon, 03 Feb 2020 12:06:22 +
with message-id
and subject line Bug#949824: fixed in schleuder 3.4.1-3
has caused the Debian Bug report #949824,
regarding schleuder: tests fail with ruby-sqlite 1.4.2-1
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 03 Feb 2020 12:05:34 +
with message-id
and subject line Bug#950229: fixed in ruby-flipper 0.17.1-5
has caused the Debian Bug report #950229,
regarding ruby-flipper: autopkgtest needs update for new version of gem2deb
to be marked as done.
This means that you claim
Your message dated Mon, 03 Feb 2020 12:04:29 +
with message-id
and subject line Bug#950230: fixed in gitlab-shell 10.3.0+debian-3.1
has caused the Debian Bug report #950230,
regarding gitlab-shell: autopkgtest needs update for new version of gem2deb
to be marked as done.
This means that you
Package: haveged
Version: 1.9.8-2
Severity: critical
Hi,
after updating to haveged 1.9.8-3, my system hangs during boot.
The console output looks similar to the one in bug #950418.
Downgrading to 1.9.8-2 fixes the problem.
-- System Information:
Debian Release: bullseye/sid
APT prefers
Your message dated Mon, 03 Feb 2020 11:42:30 +
with message-id
and subject line Bug#950228: fixed in ruby-kaminari 1.0.1-5
has caused the Debian Bug report #950228,
regarding ruby-kaminari: autopkgtest needs update for new version of gem2deb
to be marked as done.
This means that you claim
Processing control commands:
> tag -1 pending
Bug #950228 [src:ruby-kaminari] ruby-kaminari: autopkgtest needs update for new
version of gem2deb
Added tag(s) pending.
--
950228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950228
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #950228 in ruby-kaminari 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:
Processing control commands:
> Tags -1 + confirmed upstream
Bug #949824 [src:schleuder] schleuder: tests fail with ruby-sqlite 1.4.2-1
Added tag(s) confirmed and upstream.
> Forwarded -1 https://0xacab.org/schleuder/schleuder/issues/453
Bug #949824 [src:schleuder] schleuder: tests fail with
Your message dated Mon, 3 Feb 2020 11:30:19 +0100
with message-id <20200203103019.ga23...@jadzia.comodo.priv.at>
and subject line Re: Bug#949434: licensecheck: autopkgtest failure: Can't
locate App/Licensecheck.pm in @INC
has caused the Debian Bug report #949434,
regarding licensecheck:
Control: Tags -1 + confirmed upstream
Control: Forwarded -1 https://0xacab.org/schleuder/schleuder/issues/453
Hi,
On 20-01-25 09:58:22, Antonio Terceiro wrote:
> I'm about upload ruby-sqlite3 1.4.2-1, and schleuder now fails its
> tests on the dependency resolution step.
>
> [...]
>
> I tried
1 - 100 of 105 matches
Mail list logo
