Source: aide
Version: 0.17.3-4
Severity: wishlist
In autopkkgtest, we should see which hashes libmhash supports and check
whether have all of them enabled.
Or does upstream have to explicitly support a new hash?
Greetings
Marc
Note, a workaround for the issue is to place a space character after the
last '|' character on the table rows with empty fields in the right
column.
--
Happy hacking
Petter Reinholdtsen
Package: gnu-smalltalk-browser
Version: 3.2.5-1.3+b3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: be...@fams.de
Dear Maintainer,
* What led up to the situation?
Tried to run the GNU Smalltalk Browser application.
* What exactly did you do (or not do) that was
Control: reassign -1 src:linux
Control: tags -1 + moreinfo
On Wed, Dec 22, 2021 at 06:27:58AM +0100, Maxime Chambonnet wrote:
> Package: linux-base
> Version: 4.6
> Severity: normal
> X-Debbugs-Cc: max...@maxzor.eu
>
> Dear Debian maintainers,
>
> I've had quite regular crashes with 5.10, 5.15
It's maybe link to the "send windows flying automagically when hovering"
feature. I had it on and off and it was on when freezing.
The mouse does not freeze, only the compositing mode.
I do have dash-to-dock (v69?) installed for gnome-shell 3.38.6.
Package: linux-base
Version: 4.6
Severity: normal
X-Debbugs-Cc: max...@maxzor.eu
Dear Debian maintainers,
I've had quite regular crashes with 5.10, 5.15 and now 5.15PREEMPT-RT
what do I do out of it?
Is there an utility to report data onto? I can send dmesg and other logs.
I won't have the
Package: gnome-session
Version: 40.1.1-3
Severity: normal
X-Debbugs-Cc: max...@maxzor.eu
Dear Maintainer,
* What led up to the situation?
Moving my cursor in the top left corner I believe, happened twice
tonight.
* What exactly did you do (or not do) that was effective (or
Package: electrum
Followup-For: Bug #1000688
X-Debbugs-Cc: ri...@ulrichard.ch
Since the upgrade of python3-aiohttp:amd64 (3.7.4-2+b1, 3.8.1-4) electrum works
again. Thanks for fixing.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (100,
Hi,
在 2021/12/22 02:31, Boyuan Yang 写道:
Hi,
Using the filename "changelog-upstream" is not a standard practice. Why not
just keep using the old filename /usr/share/doc/liblunar-date-dev/changelog?
The upstream NEWS file is the upstream changelog in fact,
I rename it before:
NEWS =>
Hi Bastian,
Thank you for supporting it. I hope you are well.
Best regards,
Seunghun
On Tue, Dec 21, 2021 at 10:06 AM Debian Bug Tracking System
wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the sponsorship-requests package:
>
> #997016: RFS:
Howdy,
Can you retry that build? I'm not getting any error during build, but recently
there was a problem with one of the development headers this package depends on,
it did not depend on all packages listed in the .pc file.
Can you ensure you try with libayatana-appindicator3-dev 0.5.90-5?
Hi Andreas,
在 2021/12/22 03:53, Andreas Beckmann 写道:
Hi,
another issue I noticed in liblunar-date-3.0-1: It is missing a
corresponding Breaks to the existing Replaces. Without it the
following sequence
install liblunar-date-2.0-0
install liblunar-date-3.0-1
remove liblunar-date-3.0-1
This is working to remove both warnings.
I'm 99% sure the real problem is that upsmon is trying to do things that are
now systemd's job.
You can see the "kill" log even there which suggests upsmon remains derp.
# Trying to fix these warnings:
#nut-monitor.service: Can't open PID file
Christi Scarborough wrote:
> Jun 14 11:29:51 yaga systemd[1]: /lib/systemd/system/nut-monitor.service:6:
> PIDFile= references path below legacy directory /var/run/, updating
> /var/run/nut/upsmon.pid → /run/nut/upsmon.pid; please update the unit file
> accordingly.
> Jun 14 11:32:46 yaga
Package: less
Version: 551-2
Severity: normal
Tags: patch
Dear Maintainer,
* What led up to the situation?
I wanted to add support for another binary format and ended up looking
at the lesspipe script in the process.
* What exactly did you do (or not do) that was effective (or
Package: lld-13
Version: 1:13.0.0-9+b2
Severity: normal
X-Debbugs-Cc: max...@maxzor.eu
Dear Maintainer,
I am on testing only.
To be noted, the package 'lld' still points to lld-11 here. I vaguely tried to
make my meta-package llvm-is-llvm13 without success.
The cmake config is installed at:
Andreas Tille writes:
> I've never seen this before and I wonder whether this is something
> I should be concerned about before uploading.
Yes, it looks like the build system is set up to produce "thin" archives
that can't stand on their own; please try patching the Makefile to drop
the T flag
Package: wnpp
Severity: wishlist
Owner: Ruffin White
X-Debbugs-Cc: debian-de...@lists.debian.org, roxfox...@gmail.com
* Package name: python3-dirhash
Version : 0.2.1
Upstream Author : Anders Huss
* URL : https://github.com/andhus/dirhash
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Ruffin White
X-Debbugs-Cc: debian-de...@lists.debian.org, roxfox...@gmail.com
* Package name: python3-scantree
Version : 0.0.1
Upstream Author : Anders Huss
* URL : https://github.com/andhus/scantree
* License : MIT
Package: wnpp
Severity: wishlist
* Package name: rime-wubi
Version : 0.0~git20200908.f1876f0-1
Upstream Author : Gong Chen
* URL : https://github.com/rime/rime-wubi
* License : Apache-2.0
Programming Lang: N/A
Description : Rime Input Method Engine
Hello Mattia,
Thanks for the patch.
On Sun 12 Dec 2021 at 06:47PM +01, Mattia Rizzolo wrote:
> |--- a/policy/ch-controlfields.rst
> |+++ b/policy/ch-controlfields.rst
> |@@ -652,9 +654,14 @@ orderings. [#]_
> | ~~~
> |
> | In a source or binary control file, the ``Description``
Hi,
在 2021-11-28星期日的 20:51 +0100，Piotr Ożarowski写道：
> [Boyuan Yang, 2021-11-28]
> > Thanks for the info and sorry for the breakage; obviously I should have
> > uploaded it into Experimental first. I am looking into fixing the issue
> > (ideally through upgrade of all related packages) but this
Thanks for reporting!
It looks like there are now libc calls to `newfstatat` which is not in Rumur’s
sandbox’s list of safe allowed syscalls. I’ll fix this upstream and then
package a new release for Debian.
Package: keepassx
Version: 2.0.3-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation? I attempted to access my passwords,
* and couldn't access them because the program expanded horizontally
Hello,
On Sat 23 Oct 2021 at 09:50PM +02, Lucas Nussbaum wrote:
>> make[2]: Entering directory '/<>/docs'
>> sphinx-build -b html -d build/doctrees source build/html
>> Running Sphinx v4.2.0
>>
>> Exception occurred:
>> File "/<>/docs/source/_ext/progress.py", line 147, in setup
>>
On Mon, 20 Dec 2021 09:55:09 +0100 Fabien Steinmetz
wrote:
Done, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002004
That is not an ITP for synkron.
Control: tags -1 + pending
Hi,
Version 0.5 of dh-haskell was uploaded to the NEW queue. [1]
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/new/dh-haskell_0.5.html
Hello GTK/Gnome experts,
Would you be able to help with #1000200? Reportbug's GTK UI does not
close properly any more. It works fine in bullseye, and there was no
change in reportbug that could have caused this change in behaviour.
On 20.11.2021 13.07, nis.marten...@web.de wrote:
>
> Michael
Package: po4a
Version: 0.62-1
I ran into something while setting up po4a in the LinuxCNC project,
which I suspect is a bug in po4a handling of AsciiDoc tables.
This set of test files demonstrate the problem, where the translated
table format is messed up (lacking newlines). Note, adding '.'
Package: fakeroot
Version: 1.26-1
Severity: normal
Greetings,
while trying to fix #995393, I noticed to things in openat that
deserve attention:
* "mode" should be initialized, possibly to 0.
* The second parameter to va_arg should be "mode_t", not "int".
Unfortunately, changing this is not a
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: mirth.hickf...@gmail.com
* Package name: git-credential-manager
* URL :
https://github.com/GitCredentialManager/git-credential-manager
* License : MIT
Programming Lang: C#
Description : Provides multi-factor
Had the same issue.
Patch above didn't work.
This lin added to /etc/uwsgi/apps-available/graphite.ini did it, though:
pymodule-alias = graphite.local_settings=/etc/graphite/local_settings.py
and set ownership of /etc/graphite/local_settings.py to _graphite:_graphite
(going with the 0400
Control: reassign -1 dh-python
Control: forcemerge 1002290 -1
Control: found -1 5.20211213
Control: found -1 5.20211217
Control: affects -1 + qutebrowser python-anyio
Hi Florian,
thanks for your analysis of what I found out about the recent
dh-python changes!
I tried to extract the IMHO
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-hask...@lists.debian.org
* Package name: dh-haskell
Version : 0.5
Upstream Author : Felix Lechner
* URL : https://salsa.debian.org/lechner/dh-haskell
* License : GPL-3+
Programming Lang: Perl
Am 21.12.21 um 12:10 schrieb Ansgar:
reassign 1002064 procps 2:3.3.17-5
On Tue, 2021-12-21 at 11:49 +0100, Daniel Feuchtinger wrote:
Debian 11 introduces a new feature, that prevents users from writing
to files that they don't own ignoring the file permissions
(see
Control: tags -1 pending
Am Tue, Dec 21, 2021 at 05:33:32PM +0100 schrieb Lucas Nussbaum:
> Source: libatomic-queue
> Version: 0.0+git20201108.d9d66b6-4
> Severity: serious
> Justification: FTBFS
This is solved in Git. However, when I try to build the status in Git I
get:
E:
Package: ftp.debian.org
Severity: normal
The 'int64' package for R was one of two approaches to 'retro-fit' an int64_t
into R (which has a limited set of basetypes). It failed and as
https://cran.r-project.org/package=int64
was orphaned in 2012 and formally archived in 2013. We kept it
Hi Jorge, Niels, all,
I prepare patch for Debian packaging files that increases debhelper
compatibility and makes clean of build rules. This should completely
address this bug. See attachment.
Cheers
--
Slávek
diff -ruN a/debian/changelog b/debian/changelog
--- a/debian/changelog 2021-12-21
Package: python3-peewee
Version: 3.14.4+dfsg-1+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
python3-peewee recommends python-peewee-doc.
The common relationship for a non-development library is to only suggest
its documentation, since common use of the package is to link
On 21/12/2021 10.07, Jochen Sprickerhof wrote:
While I agree that both packages conflict, I'm not sure if proposing a
Breaks+Replaces is the proper solution here (and in general). Normally
we want to have the library packages to be coinstallable and thus the
packages only provide non
* Andreas Beckmann [2021-12-21 21:19]:
On 21/12/2021 10.07, Jochen Sprickerhof wrote:
While I agree that both packages conflict, I'm not sure if proposing
a Breaks+Replaces is the proper solution here (and in general).
Normally we want to have the library packages to be coinstallable
and
❦ 1 November 2021 14:27 +01, Yuri D'Elia:
> cron-failure@ is using DynamicUser=yes, however this causes a silent
> delivery failure when using exim4:
>
> systemd[1]: Starting cron-failure@cron-monthly.service...
> mail_on_failure[328561]: 2021-11-01 14:11:23 1mhX5v-001NTN-LU Failed
> to create
Hi Nick,
On 21-12-2021 20:52, nick black wrote:
well, as i noted above, this use case certainly isn't the
standard way growlight will be used (although it's a valid one,
and one worth fixing -- this was a valuable exercise, and i
appreciate autopkgtests spotting this regression!). so it's not
Hi David,
Thank you for replying quickly, and sorry for the tardiness of mine.
Holiday season, you know? ;-)
David Bremner writes:
> Nicholas D Steeves writes:
>
[snip]
>>
>> I've noticed that these questions are still coming up on
>> #debian-emacs, so I thought I'd work on a documentation
Package: node-babel7
Version: 7.16.6+~cs215.259.185-2
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 filea.
If node-babel-plugin-add-module-exports is to
Hi,
another issue I noticed in liblunar-date-3.0-1: It is missing a
corresponding Breaks to the existing Replaces. Without it the following
sequence
install liblunar-date-2.0-0
install liblunar-date-3.0-1
remove liblunar-date-3.0-1
will result in liblunar-date-2.0-0 having lost all its
well, as i noted above, this use case certainly isn't the
standard way growlight will be used (although it's a valid one,
and one worth fixing -- this was a valuable exercise, and i
appreciate autopkgtests spotting this regression!). so it's not
very important to users...but at the same time, it
Hi,
On Tue, Dec 21, 2021 at 07:12:26PM +0100, Axel Beckert wrote:
> > That seems like a false-positive: The dataclasses backport is only
> > required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)"
> > already.
> […]
> > That smells like a bug in dh-python.
>
> I tried downgrading
I've only seen this bug 2 or 3 times in the last year, but here is the
fix I used to avoid the warning.
--- /usr/bin/jdresolve 2018-01-04 18:21:09.0 +
+++ jdresolve 2021-11-14 00:28:17.725549514 +
@@ -783,6 +783,8 @@
my $type = $socks{fileno($socket)}{TYPE};
Hi Nick,
On 21-12-2021 19:52, nick black wrote:
well, if you have an older version of notcurses, you're going to
run into this growlight problem, so "solving" this problem for
Debian would seem to me to require the versioned dep?
The problem exist only in unstable, and to have the problem,
Source: bpfcc
Version: 0.22.0+ds-2
Severity: important
Tags: ftbfs
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Dear Maintainer,
bpfcc is failing to build with the latest release of libbpf.
Reported error:
In file included from /<>/src/cc/bcc_libbpf_inc.h:5,
from
Control: retitle -1 gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR:
"install_dir" must be specified when installing a target
On Tue, 21 Dec 2021 at 16:53:41 +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
[meson-logs/meson-log.txt follows]
This doesn't look like the reason
I have discovered a workaround.
KDE Settings > Applications > File Associations
Search for jpeg in the filename pattern.
The Filename Patterns in the results bog starts with *.jpe
What happens, I wondered, if I click Remove and Accept?
What happens is that Gwenview no longer defaults to
Package: dh-python
Version: 5.20211217
Severity: grave
python-anyio package is supposedly broken (bug #1002179), but the build
log makes me think it's a problem with dh-python:
>dh_python3 -O--buildsystem=pybuild
> I: dh_python3 pydist:313: Cannot find package that provides
contextvars.
Package: plasma-discover
Version: 5.23.4-1
Discover installs an old version of widget Webslice and the old
version of Webslice does not work.
Discover: "Webslice - Plasma Widgets" is not in the "Plasma Widgets"
tree, but you can find it to write "webslice" in the Search field.
I installed
Source: mesa
Version: 21.2.6-1
Severity: normal
This bug also affects 21.3.0~rc5-1 in experimental.
Llvm-toolchain-13 now appears to be ready for armel, i386, mipsel,
mips64el, which were a problem the last time migration was attempted
(Bug #995835).
if i don't need the versioned dep, there is -- so far as i can
tell -- no reason to upload a new growlight at all, unless i
need do so to retrigger the autopkgtests and allow a transition
to testing.
(sorry for my ignorance--i'm still applying for DD)
signature.asc
Description: PGP signature
> I don't think you need the versioned depends really. Or did I miss
> something?
well, if you have an older version of notcurses, you're going to
run into this growlight problem, so "solving" this problem for
Debian would seem to me to require the versioned dep? i'm sure
you're much more
Hi Nick,
On 21-12-2021 14:53, nick black wrote:
the growlight bug: https://github.com/dankamongmen/growlight/issues/153
it was determined that this was a flaw in Notcurses when > input was redirected
from a file. it has been resolved,
So, I would reassign the bug to notcurses, mark it as
Hi,
在 2021-12-21星期二的 22:17 +0800，xiao sheng wen写道：
> Control: tags -1 pending
>
>
> Hi Andreas,
>
> Thanks for your bugreport.
>
> I do rename upstream NEWS to changelog-upstream to fix this bug.(In
> 3.0.1-1, it rename to changelog :-( )
>
> In old upstream version 2.4.0, there is a
Package: wnpp
Severity: wishlist
Owner: Roland Mas
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: freesas
Version : 0.9.0
Upstream Author : Jérôme Kieffer
* URL : https://github.com/kif/freesas
* License : MIT
Programming Lang: Python
The problems should be fixed by resolving the transition from experimental
to unstable of the whole Ignition family:
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002286
On Tue, Dec 21, 2021 at 5:34 PM Lucas Nussbaum wrote:
> Source: ignition-transport
> Version: 8.0.0+dfsg-3
>
Hi.
Graham Inggs writes:
> numpy 1:1.21.4-2 in testing is already built for python3.9 and 3.10
> [1]. Search for 'cpython-3' and you should find files like:
>
> /usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-310-x86_64-linux-gnu.so
>
Hi Lucas,
This isn't a schroot bug. It's actually down to a behaviour change in
"fakeroot". If you run "dpkg-buildpackage" by hand, then "cd debian/build" and
then run "fakeroot ctest -V", you'll see this:
3: 1) test: test_config::test_construction_file (E)
3: setUp() failed
3: - uncaught
Hi,
Florian Bruhin wrote:
> On Tue, Dec 21, 2021 at 05:15:47PM +0100, Lucas Nussbaum wrote:
> > > I: dh_python3 pydist:313: Cannot find package that provides
> > > dataclasses. Please add package that provides it to
> > > Build-Depends or add "dataclasses python3-dataclasses" line to
> > >
> File "/usr/lib/python3/dist-packages/scipy/spatial/kdtree.py", line 5, in
>
> from .ckdtree import cKDTree, cKDTreeNode
> File "ckdtree.pyx", line 1, in init scipy.spatial.ckdtree
> ValueError: numpy.ndarray size changed, may indicate binary incompatibility.
> Expected 88 from C header,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello:
The motivation for this bug is to manage the join transition from experimental
of the packages corresponding to gazebo and the following ignition/sdformat
libraries which are
Hi,
On Tue, Dec 21, 2021 at 05:15:47PM +0100, Lucas Nussbaum wrote:
> > I: dh_python3 pydist:313: Cannot find package that provides dataclasses.
> > Please add package that provides it to Build-Depends or add "dataclasses
> > python3-dataclasses" line to debian/py3dist-overrides or add proper
Source: jersey1
Version: 1.19.3-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: node-agent-base
Version: 6.0.2+~cs5.4.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: gromit-mpx
Version: 1.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
Source: polymake
Version: 4.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: prometheus-tplink-plug-exporter
Version: 0.2.0+git20200622.cc4a731-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Source: node-neo-async
Version: 2.6.2+~cs3.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: node-ts-jest
Version: 27.0.7+~cs0.2.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: tiles-request
Version: 1.0.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Source: schroot
Version: 1.6.10-12
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering
Source: nmh
Version: 1.7.1-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering
Source: smartlist
Version: 3.15-25
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: zeroinstall-injector
Version: 2.16-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: rclone
Version: 1.53.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
Source: kdump-tools
Version: 1:1.6.9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: libquartz2-java
Version: 2.3.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Source: node-https-proxy-agent
Version: 5.0.0+~cs8.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
Source: prometheus-homeplug-exporter
Version: 0.3.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: libvt-ldap-java
Version: 3.3.8-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Source: node-y18n
Version: 5.0.8-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: jaxws
Version: 2.3.0.2-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: hcloud-cli
Version: 1.13.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Source: node-trust-webcrypto
Version: 0.9.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]:
On Tue, Dec 21, 2021 at 05:09:44PM +0100, Lucas Nussbaum wrote:
> > The following packages have unmet dependencies:
> > librust-signal-hook-dev : Depends:
> > librust-signal-hook-registry-1.2+default-dev but it is not installable
> > E: Unable to correct problems, you have held broken packages.
Source: httpcomponents-core5
Version: 5.1.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: golang-github-go-openapi-analysis
Version: 0.21.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part
Source: rust-os-info
Version: 1.3.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Source: nodejs
Version: 12.22.7~dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]:
Source: libatomic-queue
Version: 0.0+git20201108.d9d66b6-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part
Source: lookatme
Version: 2.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering
Source: node-gulp-sourcemaps
Version: 3.0.0+~cs4.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: node-mqtt-connection
Version: 4.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: pcb-rnd
Version: 3.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering
1 - 100 of 309 matches
Mail list logo
