Source: rust-csv
Version: 1.1.5-1
Severity: serious
- Forwarded message from Debian FTP Masters
-
From: Debian FTP Masters
To: mips64el Build Daemon
Date: Fri, 04 Dec 2020 01:51:38 +
Subject: rust-csv_1.1.5-1_mips64el-buildd.changes REJECTED
Message-Id:
Your message dated Fri, 04 Dec 2020 07:49:12 +
with message-id
and subject line Bug#976191: fixed in texlive-base 2020.20201203-1
has caused the Debian Bug report #976191,
regarding texlive-latex-base: Fails to build formats for LaTeX
to be marked as done.
This means that you claim that the
Am 04.12.2020 um 01:07 teilte Norbert Preining mit:
Hi,
But be aware, that there might be further moves coming again reverting
this change (yes, I know the pain), since LaTeX upstream is doing this:
https://github.com/latex3/latex2e/issues/450
I guess you rather meant
First of all, thank you for including me on replies.
Regarding the subject, I think that the best way to proceed would be to,
essentially, create a task force to maintain chromium properly.
I don't think that I have the computational means to compile chromium
frequently (I hope that using
Your message dated Fri, 04 Dec 2020 06:18:20 +
with message-id
and subject line Bug#975900: fixed in aria2 1.35.0-3
has caused the Debian Bug report #975900,
regarding aria2: autopkgtest needs update for new version of python3-defaults:
output to stderr
to be marked as done.
This means that
Processing control commands:
> affects -1 sway
Bug #976366 [systemd] Upgrade to 247 broke keyboard input on Wayland session
Added indication that 976366 affects sway
--
976366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: systemd
Version: 247.1-3
Severity: critical
Justification: breaks graphical session input
Control: affects -1 sway
Quack,
After upgrade from 246.6-5 to 247.1-3 I experienced impossibility to use
my keyboard after login on graphical session.
I'm using Lightdm + Sway and could input
Your message dated Fri, 04 Dec 2020 04:08:33 +
with message-id
and subject line Bug#973802: fixed in magma 2.5.4+ds-1
has caused the Debian Bug report #973802,
regarding magma: pathname 'magma-2.5.2+ds/debian/alternatives/libblas.so.3'
points outside source root (to '/usr/lib/libmagma.so.2')
Your message dated Fri, 04 Dec 2020 00:52:35 +
with message-id
and subject line Bug#962803: fixed in rust-csv 1.1.5-1
has caused the Debian Bug report #962803,
regarding rust-csv: autopkgtest failure: could not compile `csv`
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 04 Dec 2020 00:33:28 +
with message-id
and subject line Bug#975467: fixed in psignifit 2.5.6-7
has caused the Debian Bug report #975467,
regarding psignifit: autopkgtest failure on !x86: input stream is too big
to be marked as done.
This means that you claim that the
Your message dated Fri, 04 Dec 2020 00:33:48 +
with message-id
and subject line Bug#976072: fixed in topydo 0.13-5
has caused the Debian Bug report #976072,
regarding topydo: Fails to upgrade: update-alternatives: error: alternative
todo can't be master: it is a slave of todo.txt
to be
Your message dated Fri, 04 Dec 2020 00:33:21 +
with message-id
and subject line Bug#974058: fixed in polymake 4.1-5
has caused the Debian Bug report #974058,
regarding polymake: FTBFS on arm64: internal compiler error: canonical types
differ for identical types
to be marked as done.
This
Hi Hilmar,
> > filemove;texlive-latex-recommended;texlive-latex-base;2020.20201203
> >
> Done.
Thanks.
> Source packages are here, I'll upload tomorrow just texlive-base, changes
> are on github. I can confirm that the change solves the issue.
Perfect, thanks for testing.
But be aware,
Control: fixed -1 0.2+bzr42+repack1-11
Control: close -1
On Mo 30 Apr 2018 12:56:17 CEST, Mike Gabriel wrote:
I really need a way to reproduce the test failures on my local setup
(sbuild).
This bug (#879937) has finally been resolved. By bumping DH compat
level to version 13 (and thus
Am 03.12.2020 um 06:21 teilte Norbert Preining mit:
Hi Norbert,
@Norbert: could fix this in upstream?
l3packages has moved from collection-latexrecommended to
collection-latex in svn 57048.
Great, thanks!
Thus, a new checkout with the respective
Control: tag -1 pending
Hello,
Bug #975467 in psignifit 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 #975467 [src:psignifit] psignifit: autopkgtest failure on !x86: input
stream is too big
Added tag(s) pending.
--
975467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> block 972272 by 976355
Bug #972272 [src:liquidsoap] liquidsoap FTBFS on bytecode architectures
972272 was not blocked by any bugs.
972272 was not blocking any bugs.
Added blocking bug(s) of 972272: 976355
> thanks
Stopping processing here.
Your message dated Thu, 03 Dec 2020 22:38:27 +0100
with message-id <874kl2k1t8.fsf@localhost>
and subject line Re: Bug#976221: blender: gpu hang when working
has caused the Debian Bug report #976221,
regarding blender: gpu hang when working
to be marked as done.
This means that you claim that the
Source: liquidsoap
Version: 1.4.3-1
Severity: serious
Hi, liquidsoap fails to compile on an up-to-date amd64 sid machine:
OCAMLOPT -c stream/frame.ml
File "stream/frame.ml", line 363, characters 25-59:
363 | contents = [(!!size, create_content (type_of_kind kind))];
Processing control commands:
> tags -1 pending
Bug #974168 [src:bioperl-run] bioperl-run: autopkgtest failure
Added tag(s) pending.
> tags -1 help
Bug #974168 [src:bioperl-run] bioperl-run: autopkgtest failure
Added tag(s) help.
--
974168:
Package: git
Version: 1:2.29.2-1
Severity: serious
Some of the tests fail with dash, which is the default /bin/sh in
Debian.
Example:
| bbl@debian-sid:~/git-2.29.2+next.20201030/t$ bash ./t3070-wildmatch.sh | tail
-n 3
| # still have 40 known breakage(s)
| # passed all remaining 1850 test(s)
|
Your message dated Thu, 03 Dec 2020 21:18:41 +
with message-id
and subject line Bug#966439: fixed in clickhouse 18.16.1+ds-7.2
has caused the Debian Bug report #966439,
regarding clickhouse ftbfs with gcc-10
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 03 Dec 2020 21:19:28 +
with message-id
and subject line Bug#975205: fixed in rmlint 2.9.0-2.2
has caused the Debian Bug report #975205,
regarding rmlint: FTBFS: rm: cannot remove './.sconf_temp': Is a directory
to be marked as done.
This means that you claim that the
Control: tags -1 pending
Control: tags -1 help
Hi,
while the original issue of this bug report is fixed by adding the
missing libfile-sort-perl dependency it has a new build time error
in t/BEDTools.t.
Any help to fix this is welcome
Andreas.
--
http://fam-tille.de
Control: reopen -1
Control: reassign -1 gitlab
On Thu, Dec 3, 2020 at 10:14, Xavier wrote:
Does gitlab use `npm install` ? If so, we just have to fix
node-compression-webpack-plugin/package.json
This is indeed caused by mix of schema-utils 2 and 3. Version 2 is
pulled by yarn and version 3
Processing control commands:
> reopen -1
Bug #976310 {Done: Xavier Guimard }
[node-compression-webpack-plugin] node-compression-webpack-plugin: TypeError:
(0 , _schemaUtils.validate) is not a function
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions
Your message dated Thu, 03 Dec 2020 20:47:21 +
with message-id
and subject line Bug#973769: fixed in spice-vdagent 0.20.0-2
has caused the Debian Bug report #973769,
regarding spice-vdagent: CVE-2020-25650 CVE-2020-25651 CVE-2020-25652
CVE-2020-25653
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> reassign 976351 node-request-promise-core
Bug #976351 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
Bug reassigned from package 'node-request' to 'node-request-promise-core'.
No longer marked
Processing commands for cont...@bugs.debian.org:
> clone 956423 -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
Bug 956423 cloned as bug 976351
976351 was blocked by: 958690 958687 958689 958694 958692 958683 958693 958682
958684
Processing commands for cont...@bugs.debian.org:
> forwarded 973786 https://github.com/kapitainsky/RcloneBrowser/pull/126
Bug #973786 [src:rclone-browser] rclone-browser FTBFS due to
-Werror=deprecated-declarations
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> found 972457 git/1:2.29.2-1
Bug #972457 [git] FTBFS - not ok 3 - progress display breaks long lines #1
Marked as found in versions git/1:2.29.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972457:
Processing control commands:
> reopen -1
Bug #973789 {Done: Paul Gevers } [src:parsinsert]
src:parsinsert: fails to migrate to testing for too long: FTBFS on armel,
armhf, mips64el and ppc64el
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be
Control: reopen -1
Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 David Knox
Hi David,
as you can see in the Debian bug the Build logs for mips64el[1] and
others[2] the build time tests for parsinsert are failing. From my
naive perspective its basically a matter of
Processing control commands:
> fixed -1 0.2+bzr42+repack1-11
Bug #879937 [src:libqtdbustest] libqtdbustest: FTBFS: unit test fails with
BadAddress DBusException
Marked as fixed in versions libqtdbustest/0.2+bzr42+repack1-11.
> close -1
Bug #879937 [src:libqtdbustest] libqtdbustest: FTBFS: unit
Processing commands for cont...@bugs.debian.org:
> forwarded 972767 https://github.com/FRRouting/frr/pull/6598
Bug #972767 [src:frr] frr ftbfs with python3.9
Set Bug forwarded-to-address to 'https://github.com/FRRouting/frr/pull/6598'.
> thanks
Stopping processing here.
Please contact me if you
Your message dated Thu, 03 Dec 2020 19:07:34 +
with message-id
and subject line Bug#974733: fixed in q2-quality-filter 2020.11.0-1
has caused the Debian Bug report #974733,
regarding q2-quality-filter: unsatisfiable build-dependencies
to be marked as done.
This means that you claim that the
Preparing to unpack topydo_0.13-5_all.deb ...
Unpacking topydo (0.13-5) over (0.13-2) ...
Setting up topydo (0.13-5) ...
update-alternatives: using /usr/bin/topydo to provide /usr/bin/todo.txt
(todo.txt) in auto mode
update-alternatives: using /usr/bin/topydo to provide /usr/bin/todo (todo)
in
Your message dated Thu, 03 Dec 2020 18:49:37 +
with message-id
and subject line Bug#966883: fixed in procenv 0.51-0.1
has caused the Debian Bug report #966883,
regarding procenv: FTBFS: platform/linux/platform.c:1266:21: error: ‘%s’
directive writing up to 1017 bytes into a region of size 16
Processing control commands:
> tags -1 patch pending
Bug #966883 [src:procenv] procenv: FTBFS: platform/linux/platform.c:1266:21:
error: ‘%s’ directive writing up to 1017 bytes into a region of size 16
[-Werror=format-overflow=]
Added tag(s) patch and pending.
--
966883:
Hi Andreas,
On Thu, 3 Dec 2020 14:18:08 +0100 Andreas Tille wrote:
> ==
> ERROR: test_q_score (q2_quality_filter.test.test_filter.FilterTests)
> --
> Traceback
Processing commands for cont...@bugs.debian.org:
> tags 959571 - pending
Bug #959571 [src:ruby-psych] ruby-psych: FTBFS: LoadError: no such file to load
-- psych
Removed tag(s) pending.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
959571:
Package: ruby-diaspora-federation
Severity: serious
Version: 0.2.6-2
ruby-diaspora-federation ftbfs/fails autopkgtest with ruby-faraday 1.0
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday' (< 0.18.0, >= 0.9.0) - did find: [faraday-1.1.0]
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:php-pear
> # 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
Package: adb
Followup-For: Bug #976007
X-Debbugs-Cc: pitsior...@gmail.com
Fixed in v10.x that finally reached unstable earlier for amd64 and i386!
$ adb devices
List of devices attached
ABCDEF1234567890device
The same applies to #975707.
Thank you very much.
-- System Information:
On Thu, 03 Dec 2020, Rafael Laboissière wrote:
> Dear Yaroslav and Michael,
> Are you aware of the problem related in Bug#976325, regarding the email
> address t...@neuro.debian.net?
thanks Rafael. I think that elderly mail server didn't re-emerge from
the dead upon recent power outage. I
Hello,
I wonder if some collaboration would be possible with the ungoogled-chromium
people, and linux mint (#975060)?
In the case of linux-mint, they seem to have given up in Debian being their
upstream for this package, and ungoogled-chromium seems to be held back,
adhering to Debian as
Your message dated Thu, 3 Dec 2020 17:45:12 +0100
with message-id
and subject line Re: pytango: FTBFS: api_util.cpp:13:10: fatal error: tango.h:
No such file or directory
has caused the Debian Bug report #975150,
regarding pytango: FTBFS: api_util.cpp:13:10: fatal error: tango.h: No such
file
Your message dated Thu, 03 Dec 2020 16:19:23 +
with message-id
and subject line Bug#975344: fixed in libapache-mod-auth-kerb 5.4-2.5
has caused the Debian Bug report #975344,
regarding FTBFS with krb5 1.18: significant use of internal
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #958912 in devscripts 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 #958912 [devscripts] devscripts: missing ubuntu release info breaks
autopkgtest
Added tag(s) pending.
--
958912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 03 Dec 2020 15:49:45 +
with message-id
and subject line Bug#973131: fixed in python-nss 1.0.1-1
has caused the Debian Bug report #973131,
regarding python-nss: FTBFS: src/py_nss.h:126:3: error: conflicting types for
‘RSAPublicKey’
to be marked as done.
This means
Your message dated Thu, 03 Dec 2020 15:25:01 +
with message-id
and subject line Bug#971829: fixed in pyopencl 2020.2.2-1
has caused the Debian Bug report #971829,
regarding python3-pyopencl: Random runtime error in the C++ layer (crash the
program)
to be marked as done.
This means that you
Dear Yaroslav and Michael,
Are you aware of the problem related in Bug#976325, regarding the email
address t...@neuro.debian.net?
Best,
Rafael Laboissière
- Forwarded message from Ansgar -
From: Ansgar
Subject: Bug#976325: src:libgdf: invalid maintainer address
Date: Thu, 03 Dec
Processing commands for cont...@bugs.debian.org:
> reassign 935081 timidity
Bug #935081 [alsa-utils] Intel sound not working after upgrade to Debian 10
Bug reassigned from package 'alsa-utils' to 'timidity'.
No longer marked as found in versions alsa-utils/1.1.8-2 and alsa-utils/1.2.2-1.
Ignoring
Processing commands for cont...@bugs.debian.org:
> forwarded 975825 https://github.com/CrossNox/m2r2/issues/13
Bug #975825 [src:python-m2r] python-m2r: FTBFS: AttributeError: 'str' object
has no attribute 'supported'
Set Bug forwarded-to-address to 'https://github.com/CrossNox/m2r2/issues/13'.
>
Processing commands for cont...@bugs.debian.org:
> forcemerge 901148 935081
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via
pulseaudio
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via
pulseaudio
Bug #904652 [timidity] pulseaudio: looses device and
Am 01.12.20 um 18:53 schrieb Elimar Riesebieter:
> What happens if you stop timidity daemon:
> # systemctl stop timidity
>
> ?
>
> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901148
>
> Elimar
Yes - timidity is the reason. Thank you very much!
Stopping timidity activates the intern
Your message dated Thu, 03 Dec 2020 14:48:13 +
with message-id
and subject line Bug#976079: fixed in todo.txt-base 2.1
has caused the Debian Bug report #976079,
regarding todo.txt-base fails both autopkg tests
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 03 Dec 2020 14:44:51 +
with message-id
and subject line Bug#976022: fixed in mupdf 1.17.0+ds1-1.2
has caused the Debian Bug report #976022,
regarding mupdf-dev: install pkgconfig file in wrong directory
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> severity 963311 important
Bug #963311 [src:telepathy-glib] telepathy-glib: FTBFS: E: Build killed with
signal TERM after 150 minutes of inactivity
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me
severity 963311 important
thanks
The package builds fine on all release architectures, I don't think that
bug is RC anymore
Your message dated Thu, 03 Dec 2020 13:33:34 +
with message-id
and subject line Bug#975212: fixed in jss 4.8.0-2
has caused the Debian Bug report #975212,
regarding jss: FTBFS: test failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 3 Dec 2020 14:33:12 +0100
with message-id <20201203133312.gj31...@an3as.eu>
and subject line Closed in latest upload
has caused the Debian Bug report #974840,
regarding qa-feature-table: unsatisfiable build-dependencies
to be marked as done.
This means that you claim that
Processing control commands:
> block -1 by 962717
Bug #974839 [src:q2-feature-classifier] q2-feature-classifier: unsatisfiable
build-dependency
974839 was not blocked by any bugs.
974839 was not blocking any bugs.
Added blocking bug(s) of 974839: 962717
> block -1 by 932050
Bug #974839
Control: block -1 by 962717
Control: block -1 by 932050
Your message dated Thu, 03 Dec 2020 13:18:45 +
with message-id
and subject line Bug#974717: fixed in q2-demux 2020.11.0-1
has caused the Debian Bug report #974717,
regarding q2-demux: unsatisfiable build-dependency
to be marked as done.
This means that you claim that the problem has been
Control: tags -1 help
Hi,
I upgraded q2-quality-filter to the latest upstream version in Git. The
build time tests were disabled as for other QIIME modules that need
registering in QIIME which is not possible at build time. However, also
the autopkgtest fails with:
autopkgtest [13:08:01]:
Processing control commands:
> tags -1 help
Bug #974733 [src:q2-quality-filter] q2-quality-filter: unsatisfiable
build-dependencies
Added tag(s) help.
--
974733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 03 Dec 2020 13:04:04 +
with message-id
and subject line Bug#954559: fixed in golang-gopkg-go-playground-colors.v1
1.2.0-3
has caused the Debian Bug report #954559,
regarding golang-gopkg-go-playground-colors.v1: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu &&
Hi, I think I should have some time for q2-quality-filter this
evening (UTC+1), unless someone else beats me at it... :)
--
Étienne Mollier
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.
signature.asc
Description: PGP
Am 01.12.20 um 07:56 schrieb Herbert Xu:
On Tue, Dec 01, 2020 at 05:06:18PM +1100, Herbert Xu wrote:
For some reason this is causing the final two tee's to be created
as children of debian/tests/timedated rather than the bash shell.
An alternative to changing the parent is of course to do
Control: tag -1 pending
Hello,
Bug #954559 in golang-gopkg-go-playground-colors.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:
Processing control commands:
> tag -1 pending
Bug #954559 [src:golang-gopkg-go-playground-colors.v1]
golang-gopkg-go-playground-colors.v1: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 4
gopkg.in/go-playground/colors.v1 returned exit code 1
Added tag(s) pending.
Your message dated Thu, 03 Dec 2020 12:34:50 +
with message-id
and subject line Bug#971997: fixed in xrdesktop 0.15.1-5
has caused the Debian Bug report #971997,
regarding libxrdesktop-0.15-0 also needs Breaks+Replaces: libxrdesktop-0.13-0
to be marked as done.
This means that you claim that
Am 02.12.20 um 00:26 schrieb Herbert Xu:
On Wed, Dec 02, 2020 at 12:21:52AM +0100, Michael Biebl wrote:
I'll update the timedated test accordingly.
Incidentally we already have
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/110
Thanks.
Hm, so I applied this change and
Your message dated Thu, 03 Dec 2020 12:10:59 +
with message-id
and subject line Bug#967220: fixed in telepathy-ring 2.3.24-2
has caused the Debian Bug report #967220,
regarding telepathy-ring: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Thu, 03 Dec 2020 11:35:36 +
with message-id
and subject line Bug#967215: fixed in telepathy-glib 0.24.1-3
has caused the Debian Bug report #967215,
regarding telepathy-glib: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Source: psychtoolbox-3
Version: 3.0.17.3.dfsg1-1
Severity: serious
X-Debbugs-Cc: Yaroslav Halchenko
The maintainer address is invalid, see below.
Ansgar
Forwarded Message
Subject: Mail delivery failed: returning message to sender
Date: Fri, 27 Nov 2020 16:50:50 +
> This
Source: numad
Version: 0.5+20150602-6
Severity: serious
X-Debbugs-Cc: gustavo panizzo
The maintainer address is invalid, see below.
Ansgar
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients.
Source: datalad
Version: 0.13.5-1
Severity: serious
X-Debbugs-Cc: Yaroslav Halchenko
The maintainer address is invalid, see below.
Ansgar
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of
> its recipients. This
Source: libgdf
Version: 0.1.3-5
Severity: serious
X-Debbugs-Cc: Rafael Laboissière
The maintainer address is invalid, see below.
Ansgar
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients.
Source: pynpoint
Version: 0.8.3-2
Severity: serious
X-Debbugs-Cc: Gürkan Myczko , ba...@debian.org
The maintainer address is invalid, see below.
Ansgar
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
>
On Wed, Dec 2, 2020 at 2:03 AM Thorsten Glaser wrote:
>
> Package: src:linux
> Version: 5.9.9-1
> Severity: critical
> Justification: causes serious data loss
> X-Debbugs-Cc:
> t...@mirbsd.de,reply+aagshfu5klm2qb2dozdxppf5z5jydevbnhhcvex...@reply.github.com
>
> A bit of backstory, since this is
Your message dated Thu, 3 Dec 2020 12:03:15 +0100
with message-id <20201203110315.gf31...@an3as.eu>
and subject line Fixed with last upload
has caused the Debian Bug report #974716,
regarding q2-cutadapt: unsatisfiable build-dependency
to be marked as done.
This means that you claim that the
Package: searx
Version: 0.17.0+dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
recent python3 packages upgrade for bullseye, made searx unusable. can't
perform any search. uwsgi log filling up with :
pid: 1625924|app: 0|req: 20/60] ipaddress () {76 vars in
Your message dated Thu, 03 Dec 2020 10:33:59 +
with message-id
and subject line Bug#973226: fixed in python-django-celery-beat 2.1.0-1
has caused the Debian Bug report #973226,
regarding python-django-celery-beat: FTBFS: ModuleNotFoundError: No module
named 'celery.five'
to be marked as
Hi Andrius,
On Mon, Nov 30, 2020 at 01:00:46PM +0200, Andrius Merkys wrote:
> Hello,
>
> On 2020-11-29 18:59, Wouter Verhelst wrote:
> > This bug is still present. Additionally, the URL for the OpenAPI JSON
> > scheme now returns a 404 error, which means that any software using
> > OpenAPI on
Your message dated Thu, 03 Dec 2020 10:20:27 +
with message-id
and subject line Bug#967217: fixed in telepathy-idle 0.2.2-1
has caused the Debian Bug report #967217,
regarding telepathy-idle: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #973226 in python-django-celery-beat 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 #973226 [src:python-django-celery-beat] python-django-celery-beat: FTBFS:
ModuleNotFoundError: No module named 'celery.five'
Added tag(s) pending.
--
973226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973226
Debian Bug Tracking System
Your message dated Thu, 03 Dec 2020 09:49:22 +
with message-id
and subject line Bug#973403: fixed in softether-vpn
5.01.9674+git20200806+8181039+dfsg2-2
has caused the Debian Bug report #973403,
regarding softether-common: hamcore.se2 broken
to be marked as done.
This means that you claim
Hi,
On Mon, 23 Nov 2020 09:56:37 +0100 Tomas Safarik wrote:
> Package: softether-vpnclient
> Version: 5.01.9674+git20200806+8181039+dfsg2-1
> Followup-For: Bug #973403
>
> Hello
>
> I still have problem with hamcore.se2 even that the changelog says it should
> be fixed. The message is
Your message dated Thu, 03 Dec 2020 09:33:27 +
with message-id
and subject line Bug#976310: fixed in node-compression-webpack-plugin 3.0.1-4
has caused the Debian Bug report #976310,
regarding node-compression-webpack-plugin: TypeError: (0 ,
_schemaUtils.validate) is not a function
to be
Your message dated Thu, 03 Dec 2020 09:33:35 +
with message-id
and subject line Bug#967221: fixed in telepathy-salut 0.8.1-7
has caused the Debian Bug report #967221,
regarding telepathy-salut: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #976310 in node-compression-webpack-plugin 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 #976310 [node-compression-webpack-plugin] node-compression-webpack-plugin:
TypeError: (0 , _schemaUtils.validate) is not a function
Added tag(s) pending.
--
976310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976310
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> reopen 973403
Bug #973403 {Done: Andrej Shadura } [softether-common]
softether-common: hamcore.se2 broken
Bug reopened
Ignoring request to alter fixed versions of bug #973403 to the same values
previously set
> thanks
Stopping processing here.
On Thu, Dec 3, 2020 at 10:13, Xavier wrote:
_schemaUtils.validate *is* a function when using schema-utils ≥ 3.
Problem is probably somewhere else
I think it is because css-loader is installed from npm which would pull
node-schema-loader 2.x. I could not get node-css-loader working last
On Thu, Dec 3, 2020 at 10:14, Xavier wrote:
_schemaUtils.validate *is* a function when using schema-utils ≥
3.
Problem is probably somewhere else
Does gitlab use `npm install` ? If so, we just have to fix
node-compression-webpack-plugin/package.json
yes, it uses yarnpkg install. Can
1 - 100 of 106 matches
Mail list logo
